I tried to compile the application but in the emulator I get the message "pixel launcher isn t responding". I changed the performance in Software, but still it appears.plzzzz help, i ve tried 3 days to resolve this but with no results
I had the same problem. I opened the AVD manager, I wiped the data of the emulator, then I did a cold boot and the error went away. Now it works fine.
1- Try wipe data, i have faced this problem before and this was the solution.
2- Check if there is any update from SDK Manager.
3- Deleting this emulated device and recreate a new one may help you.
clearing launcher app data may help,
adb shell pm clear com.google.android.apps.nexuslauncher
I hope it would helpful for you
Related
I just installed Android Studio, and I am very new with this program.
So when I run the Android Emulator it says: "To Start Android, enter your password", although I have never set a password. When I just enter a word with 4 letters it says "The Password you entered is correct, but unfortunately your data is corrupt".
After that, I have to Reset the Phone, but when I do that the same menu with "To Start Android, enter your password" appears.
Maybe it is just an easy mistake, but as I said I am new with this. I also did some research on the internet but I did not find anything useful.
this is the 2 images that it showe me:
1)
2)
and after i clicked on reset phone, nothing happened.
I would be very glad if someone has an answer for this.
This is a late response, but thought this simple fix might help anyone else who comes across this problem in the future. What worked for me is the following:
In VS2017 ==> Tools ==> Android ==> Select: Android Device Manager
In the Android Device Manager window, you'll see your Android Emulator.
Make sure the far right column contains the button "Start" (if "Stop" appears, click "Stop")
Right Click the device, and select the "Factory Reset" option in the menu.
Your emulator should now be working. Good luck.
open AVD and right click on the emulator choose ->Wipe data option.
Check that your avd folder path doesn't include national symbols (in my case it looked like C:\Users\Пользователь\.android).
After I changed this path everything is working.
See this post of how to change path:
Possible to change where Android Virtual Devices are saved?
Check out "Viewing and managing your Avds" part. Try wiping data of your emulator or create a new emulator for yourself.
https://developer.android.com/studio/run/managing-avds.html
enable GoogleAPIs and Google Play Store
Change the Android version. I was creating an emulator with Oreo 8.1 and got stuck in with the same issue.
I created another with Marshmallows 6.0 and no more asking for password.
Then if you are using Oreo 8.1 try with antoher.
I created a virtual device, and after, I had to reinstall the emulator.
When I booted the virtual device, I got this issue.
I deleted it and made a new one, and it worked fine.
Just go the AVD Manager and Wipe Data. The problem will be solved.
Here are the steps I followed after my device corrupted.
Close your emulator
Open AVD manager, right click on your device and click "Cold Boot Now" button.
Sorry for a very Late Answer. But you can't create a x64 Virtual Device on x64 System. Your device needs to be x86.
Just a warning to anyone getting this error on an emulator instance that was working and you cold booted or something. I got this error and just stopped and cold booted again and it was gone! So try that first before wiping your emulator instance unnecessarily.
Deleted the device in the Device Manager and created a new one with a higher OS version (Oreo -> Pie). The error disappeared. Did not find the real reason yet.
Logcat output is emtpy in Intellij IDEA - what to do?
An application is running (live wallpaper), log level is Verbose, device is chosen correctly, ADB and USB debugging are enabled.
Pressing the following button always fixes it for me.
I often see this problem with eclipse IDE, restart IDE (or ADB by command line) is my solution.
to restart ADB:
sudo adb kill-server
sudo adb start-server
It seems that adb sometimes gets disconnected from Intellij. You could restart the server or Intellij, but it's easier to just go to:
Tools -> Android
and then turn "Enable ADB Integration" off and then back on.
Just restart your logging in IntelliJ. My version is 15.
I have same problem as well.
But temporary solution is from menu go to "tools>Android>Monitor (DDMS included)"
It will be displayed Android Debug Monitor and you will be able to see your logs.
Make sure that Eclipse/ADT is not running in parallel and accessing the phone.
It's not a direct answer to your question but a possible solution if you're willing to migrate:
I kept on having this problem, sometimes a restart worked temporarily. After a while I decided to give Android Studio's a try (which is build upon Intellij). I haven't had the problem for a while and Android Studio's feels a lot like Intellij, love it!
In my situation "Resume" (see: Run -> Resume in AndroidStudio) was colored. After clicking the lable Locgat did it's job...
I really don't know what messed up my phone (running Lollipop) the last hour - but I never had such a fight to get adb / logcat running.
It seems that the system had stored the state of the application through a reboot oO Is this possible, at all? I don't know why AndroidStudio showed the resume-entry "highlighted", after the rebooting my device I didn't run the app...
If you are newbie to android like me, I was pulling my hairs out for not being able to debug. It so just happened to be that i 'accidentally' pressed that little button which hides this screen. Click it again and it will come back.
I hope this answer will be useful for you, and for many others.
I read all threads about this problem but the mentioned answers in the threads don't work for me. Can I find out which is the timeoutproblem with the help of a logfile? Is it possible that on my pc are drivers which have problems with the adb? How the adb works in detail if i start the debug process? Can anybody help me with this problem? I spent 16 hours of finding out what the problem is, but the only things I found out are that the problem has nothing to do with the installation of the eclipse, the adt plugin or the android sdk installation. Something with the connection between the emulator or my real device dont work.
If i create a new project and only change the appname or the text in the standard textview, then the app can be launched on the devices. If i do more changes for example create a new layout or something then the app wont work anymore. I am very frustrating in finding out whats wrong with the adb but till now i dont have luck to solve the problem. I hope someone can help me and others with the same problem. thanks.
In eclipse, you can increase the timeout. In Eclipse, Go to preferences>In the dialog select android>DDMS>increase the timeout value
you could also try to reboot your phone, or restart your adb server
adb kill-server
adb start-server
it worked for me :)
(increasing timeout value didn't work for me)
I got several times the same INSTALL_FAILED_INSUFFICIENT_STORAGE error.
I deleted and recreated a new AVD but it's the same.
To have it running normal I have to start from the shell because if I start from SDK and AVD manager or just pressing Run in Eclipse it start but gives me this error.
I tried to change cache partition size in the hardware options but nothing happen.
Is there a way to increase the emulator storage permanently without to use the shell every time?
thanks a lot!
Might this be the solution you are looking for?
Solution to INSTALL_FAILED_INSUFFICIENT_STORAGE error on Android
I have a problem with the Android emulator. After I run my application on a device it disappear from DDMS at some moment with no reason, even if it is still started. The only way to run again is to close the previous emulator and reopen it by running my application.
Do you have any solution for this strange error ? I must say that I can't deactivate my firewall if that is the problem. Also I tried to reset ADB but still doesn't work.
An answer for others that will come here looking for a solution.
You just need to restart ADB (kill-server and then start-server).
More details on how to do so: http://developmentality.wordpress.com/2010/09/13/android-disappearing-emulator-restart-adb-server/