When I start my android emulator it takes some times then it will show the emulator-5554 disconnected message. Can anyone tell me what the problem is?
相关问题
- How can I create this custom Bottom Navigation on
- Bottom Navigation View gets Shrink Down
- How to make that the snackbar action button be sho
- Listening to outgoing sms not working android
- How to create Circular view on android wear?
相关文章
- android开发 怎么把图片放入drawable的文件夹下
- android上如何获取/storage/emulated/下的文件列表
- androidStudio有个箭头不认识
- SQLite不能创建表
- Windows - Android SDK manager not listing any plat
- Animate Recycler View grid when number of columns
- Why is the app closing suddenly without showing an
- Android OverlayItem.setMarker(): Change the marker
That seems to be a problem of 1.6
Upgrade to 2.1 and it shall disappear.
The problem as I discovered lays in the fact the the project has no appropriate Virtual Device defined for it in the AVD manager.
So the recommended steps in eclipse are:
Remember the target platform number that appears in the selected line.
Enjoy your emulator once again!
Restart the emulator
If you are using other IDE, you can restart your emulator using -wipe-data flag to delete all the temporary files that the emulator created in previous runs.
Goto-->Prefrencess-->Android-->DDMS--> 1.visible the checkbox Use ADBHost, 2.ADB Connection timeout to 1000000, 3.Method Profile Buffer size change from 8MB into 20MB.
This is Solution the Developer whom have the lower end machine will face this Problem. Kindly check it.
Note that to find the "reset adb" option you have to click the downward pointing arrow next to the camera on the right of the devices view. The arrow may appear greyed out like everything else on the devices toolbar. It used to take hours sometimes for a successful emulator launch because of the constant disconnects until i discovered this option and where it was buried.
I've faced the same situation today: started emulator from AVD manager, and after start it appeared offline in DDMS, resetting ADB didn't help - it attempted to start several times and resulted the same way, with offline status. Another symptom was that emulator didn't react on clicking on it. After all I realized that the reason was that emulator has saved the last execution state, which possibly crashed. To fix it I unchecked the 'Launch from snapshot' option on start of emulator. And this worked for me.