Reputation: 1229
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?
Upvotes: 30
Views: 41857
Reputation: 53
This happened to me, apparently another application (VideoStream in my case) was using the same port as the adb. To fix this, use the PowerShell (with elevated permissions) to look for the process that is using the port in which you get the error:
Get-Process -Id (Get-NetTCPConnection -LocalPort portNumber).OwningProcess
You will know the PID because it shows on the Id column.
Then open Task Manager and right click on the item bar on top (Name, Status...) and enable PID to view the process id. Then look for the PID that you got on the search before and kill it.
This fixed it for me.
Upvotes: 1
Reputation: 62411
I resolved it by following these steps,
I Hope it will helps you.
Upvotes: 12
Reputation: 1
Try running the emulator from the AVD Manager. Wait till you get the home screen and then run your project.
Upvotes: 0
Reputation: 39
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.
Upvotes: 3
Reputation: 2008
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.
Upvotes: 0
Reputation: 63
This worked on Linux for me:
Upvotes: 2
Reputation: 4679
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.
Upvotes: 5
Reputation: 207863
That seems to be a problem of 1.6
Upgrade to 2.1 and it shall disappear.
Upvotes: 0
Reputation: 3284
Open the Device view of Android in Eclipse IDE. Then click the Reset Adb menu item on the device menu. Then run your application again.
Upvotes: 30
Reputation: 3988
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:
Enjoy your emulator once again!
Upvotes: -3
Reputation: 1232
Restart the emulator
Select & Right Click on Android Project
Run Configurations
Go to tab Target
Enable option Wipe User Data on Emulator launch parameters
Run Application
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.
Upvotes: 11