i installed bluestacks on my windows 10 laptop (HP elitebook ) , it worked well the first time , i installed whatsapp on it ,it worked properly for few minitues messages started flowing but i couldnt get the chance to read them because my laptop frozes for seconds so i restarded it, the next time i started bluestacks after opening the laptop i found that it went back to initializing phase, i'm forever stuck there.
i'm not sure if it needs a good internet to initialize
for the second time?
if not , why it stucks in initializing , i tried multiple suggestions i found on internet (like compatibility solution) but didnt work out.
if there is nothing to do, how can i extract whatsapp database so i can read my chats on another device.
if i installed whatsapp on another device, i won't get the messages i recieved once on bluestack again,right?
please help me whatsapp chats are so important to me.
you can't able to restore those chats again
if you are using windows 10 directly download whats app to your lap directly from store or go to link https://www.whatsapp.com/download/
Related
Whenever I try to create a firebase project in the console it won't let me continue and just endlessly tries to generate my project ID. I've tried many times but it just won't work. It is very frustrating.
Edit - So I tried on my Samsung phone and it worked, I think it may of had to do with the fact that I'm on a macbook. However, it still won't let me open the project on my mac even once I created it on my phone.
after I (tried to) flash twrp i got stock in bootloops. I had lineageOS 19.1 running and wanted twrp to install e.g. supersu. I still can access fastboot mode but from here I have no success, no matter what i try for many hours now.
Strange thing i dont understand:
with heimdall i was able to flash twrp (3.6.1) when in fastboot but with adb or odin im never able to detect my phone. I tried a lot of cables and drivers already
when in twrp i cant make a factory reset or wipe cache because it always brings the error "Permission denied" mainly for "/data"
Im able to flash lineage os from twrp but then i stuck in bootloop again. I hope someone can help. Device is a Galaxy S10e
My app is using Firebase Analytics and I believe starting in iOS 13.2 started getting the errors described here: Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?
I guess it wasn't a big deal
Since I planned for my app to go live in January, I began bigger tests in physical devices. I noticed after a while the app started to behave erratically, specially after receiving a [general] Connection to daemon was invalidated error. This doesn't occur in the simulator
Searching the internet I found a post that describes the same problem: https://forums.developer.apple.com/thread/124306
In my case, only Firebase seems to be calling WKWebView, but every time I open the UIMenuController I get the error described in the console and the app appears to be missing inputs. This is specially troublesome with UIScrollViews, which my app uses a lot. The pinch gesture seems to work at will. On an iPhone 6s, the issue isn't as noticeable, on an iPad, it's like a 50% chance the pinch gesture will work properly
Outside of removing Firebase, is there a way to mitigate this issue?
1 June 2020: The console message still persists, however, I have seemed to resolve the UIScrollView issue by deactivating delaysContentTouches, now the pinch gesture seems to work most of the time
23 October 2020 If anyone notices their app starting to behave erratically with no apparent reason I HIGHLY suggest to test it on an iOS 13 physical device if possible. Seems that Apple removed the warning from iOS 14, but testing it on iOS 13 you can pin point the exact reason after the warning appears in the console
Upon further testing, I've reduced the view down to a dead-simple UI view with a single SwiftUI TextField and the 'Connection to daemon was invalidated' still appears after I type the first character into the field. Soon thereafter the app crashes with a sigAbort. (So I don't think the reason is the UITextView wrapper I was using in the previous post). Once the invalidated message appears the app is doomed to crash, not right away but soon thereafter.
I have no idea what causes the 'invalidate' message and a Google search seems to imply that no-one else does either. Some folks appear to have made (experimental?) changes to their UI that stops the message but it appears to be impossible to determine a definite cause. (and like before it only occurs on a real phone)
Same issue without using Firebase at all. What I did: Delete build folder and compile again. Issue does not appears again.
On Xcode:
Clean the Build Folder
This will delete all of the products and intermediate files in the build folder. To clean the build folder you can use the shortcut Command+Option+Shift+K or Menu Bar → Product → Hold Option Key → Clean build Folder.
On Flutter:
Just delete build folder.
I have used Expo a few times successfully before, but for a few days now, I am unable to get into the Expo App. Whenever I open it, I see the Expo icon for a few seconds up to even minutes, and then it redirects me to the blue "Something went wrong" screen, as if I had tried to open an app.
But I didn't! It doesn't even let me scan a QR code, it just always shows this error. If I click the back button in the app, it simply terminates. I have ensured that it is the latest version and already reinstalled it once.
It seems like it somehow had locked itself onto an old, now non-existant server, and kept at it after reinstalling the app. Here is how I solved the problem:
In the metro bundler, choose connection type "Tunnel" and copy and send the URL to your phone. If you then click on it on your phone, it should redirect to the expo app. After that it got unstuck and I could finally use it normally with the QR code again!
The tools sometimes do get locked into this state.
Close and restart all components (Expo cli, browser tabs and clients) making sure to:
Kill any stray processes on the server (you need to check Activity Monitor / Process Explorer or similar depending on your platform)
Force quit all client devices and simulators using the correct method for each platform. To verify that the client process has actually been killed, check that the app splash screen is displayed for a short while when invoking it.
Clear the Expo cache when starting again: $ expo start --clear
I ran into the same issue. Solved it by going to the left sidebar in the Metro Bundler and sending a link via email!
I've tried many of the solutions and only one worked for me (which i found trying random things). I already had 'allow display over other apps' turned on (Android/OnePlus 6t) and didn't think it had anything to do with that. But I tried this...
Close the Expo app, go the the app settings and turn off 'allow display over other apps', open the expo app and [when prompted] turn on 'allow display over other apps' again.
That seems to work in my case - at least until the next time.
I tried rooting my S2 but something obviously went wrong. When i was finished rooting and tried rebooting it, it was just stuck on the bootscreen with the yellow triangle. I went to sleep and the next day it was still like that, so I went on the internet to find some help. I found the stock rom and kernel and tried booting that. Now what happens is that the boot screen comes and after 10 seconds the phone just turns off. When i tried unrooting it, i couldnt because Odin wont recognice my phone. I have also tried using Heimdall, but that wont find my phone either.
I have the international version, think it's called something like I900 etc.
I tried asking on Reddit and when they couldnt help me, they sent me here. I also discovered that i forgot to put the phone in debugging mode.
I can still acces the download and recovery mode, and yesterday i ordered a USB jig, that will be coming in the mail soon.
What should i do?
It seems you flash a wrong kernel/Image. Try to get a Orginal Kernel and a Orginal Rom.
Together with the correct PIT File.
Be sure to check if you have a 9100 or a 9100G .. this is different processor.
If you get into the Download Mode... all can be fixed.
If you get an Screen with 3 Symbols (Phone, Triangle, PC)
You are in the First Stage Bootloader, and must repartition Flash.
Odin should always detect your Phone.
Please search for Recovery Flash, or unbrick in some Android-Forums...
I don't want to link because there were many good sites.
Hope this helps.
PS: Flashing isn't automatically Illegal.
I'm Software-Developer and need sometimes to root Smart-phones, with custom kernels for different Projects.
For rooting There are 2 apps which will help you to have superuser permission on your device-one is superuser and the other one is
I recommend supersu over superuser.
Supersu also has an option to install via clockworkmod recovery(can be installed via rom manager) So it becomes an system app.