Android Error – The Log Shows Nothing
Is your Android Log empty even though the emulator or device is connected? Learn how to fix this common Eclipse error with a quick restart.
The Log appears empty even though the emulator or the physical device (phone, tablet, etc.) is correctly connected. In the Eclipse console you can see the emulator making several attempts.
Solution
If it’s the emulator, try restarting it. If it’s a physical device, disconnect it and connect it again.
If that doesn’t work, restarting Eclipse will fix it.
“Android Error – The Log Shows Nothing” by Ramón Invarato at jarroba.com, licensed under Creative Commons Attribution-NonCommercial-ShareAlike 3.0. Registered at Safe Creative.
You may also like
Android Error – The Emulator Disconnects and Doesn’t Launch the App
Does Eclipse show "Emulator-XXXX disconnected" even though the Android emulator works fine? Find out why it happens and how to fix it quickly.
Android Error – Eclipse Throws an Error That Doesn’t Exist Anywhere
Eclipse shows a red X on your Android project but no error anywhere? Follow these step-by-step solutions to fix the phantom error and the R.java problem.
Android Error – The Connection to adb Is Down and a Severe Error Has Occurred
Getting the Eclipse error "The connection to adb is down, and a severe error has occured"? Here are two simple ways to restart adb and fix it.
Android Error – Android SDK Not Found
Fix the Android error "Location of the Android SDK has not been setup in the preferences" that appears when you create a new Eclipse workspace.
Comments
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Leave a comment