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)
Related
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
I am currently working on an Android project but I have a problem.
I'm using Android Studio and the Android Emulator and every time I place a GSM call to the emulator, ADB loses connection to the device and I have to restart ADB to get the device detected again. The call does get placed to the emulator though.
It's causing me problems as I am trying to debug a bit of code that I have written that is fired when a call is detected but because ADB disconnects the emulator every time I can't step through the code in debug mode.
This is an extremely annoying problem, and I've been wrestling with it, ESPECIALLY since the app I am writing initializes upon receipt of a call.
The quickest way to get back up and running, without restarting the emulator, is to have a second terminal window open (or exit the telnet session for a few seconds) and run:
adb kill-server
adb start-server
Or, alternatively:
adb kill-server;adb start-server
...if you'd like to run it at once.
After a few seconds, you'll be reconnected. I've spent several hours searching for a way to actually PREVENT the disconnect in the first place, but I don't think it's possible until they fix the bug.
Have you tried to update your Android SDK? Update it and create new virtual device. Maybe that can help you.
Perhaps try genymotion? Much better emulator than the standard one. http://www.genymotion.com/ At least that way you can rule out the standard emulator, narrow it down to adb
Man,
I was having the same problem. The Genymotion would be a great option but they don't support mobile networking (gsm calls) now.
The first API working for was not 18 neither 19 (both updated) but 16.
So try it with 16 and it is working like charm. I am goin to try 17 too.
Good luck!
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 really need some help with this..i have done a lot of search and googling but none of the solutions worked out for me..
until 2-3 months ago i could get the emulator running at a decent time..but lately the emulator won't start..it will stay forever in the "android" screen..
i ve uninstalled and reinstalled sdk 2-3 times
after uninstall i also had system checked and restarted for potential errors..but no result
i ve installed all the necessary files, images etc..
i ve tried cmd launching no difference..disabling boot aniumation, still nothing..
i even left the emulator all night long to load but still no success..
the only solution left that i can think of is fresh install of the windows from the scratch.. :(
can you run
adb -e logcat
Command, try to see if there's anything meaningful displayed there?
That command accesses the log for the currently running emulator.
It might shed more light on the boot loop.
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/