Android Emulator is completely dead - running telnet control command, emulator crash

Question

Good evening, friends, I'm new to android. My problem is that when I started the emulator, it showed the battery as nil and the message showed connect to charger . While I am looking for this over the Internet, I have come across using Telnet commands. I used the following commands:

 telnet localhost 5554 power capacity 100 

This is a failure of my application. Not only the power command, but other commands besides help . I tried to change the power to 99, 70, 20, etc., nothing has changed in the output.

For this, I tried the suggestion given in this article.

I also tried the solution given in this question.

This question may look like a duplicate of existing questions. But I tried all these solutions,

I have

• reinstall eclipse
• reinstalled android-sdk
• reinstalled avd manager
• recreated existing AVD

I am using an Intel Atom emulator (x86). The goal is Android 4.3 with API level 18.

I also followed the instructions and suggestions given here as changing the hw.battery parameter in the config.ini file in .android\avd\ .

Answer 1

The solution is to set hw.battery=yes in the config.ini AVD file, as described here:

stack overflow

• Go to the Android Virtual Devices folder. On Windows 7, this is a folder, for example:
  C:\Users\{yourUserName}\.android\avd\{yourAVDName}.avd

• Open the config.ini file

• Set the battery option to yes: hw.battery=yes
• Restart your virtual device and be happy :-)

Answer 2

Atlast, I was able to run the emulator exactly the way I wanted. I checked the list of devices using adb devices . At first I didn’t get anything on the list. Then I run this adb connect <ip address of the VirtualMachine> . Then I opened Run configurations . I saw the virtual device on the list. I selected it and started to run my application.

Answer 3

This may be an emulator error when using telnet, and by the way, this is a problem with an independent OS, it can appear on Microsoft Windows or Linux. see page with questions:

https://code.google.com/p/android/issues/detail?id=39959

I tried many solutions, but all failed, however, when I delete the AVD and create a new one, the problem disappeared.

Yours faithfully,

Answer 4

I am using Window 7 and I had the same problem with the emulator. When I opposed the config.ini file, I had to put the backspace character on each line, because the entire contents of the file were on the same line as follows:

 avd.ini.encoding=ISO-8859-1hw.dPad=nohw.lcd.density=240hw.cpu.arch=armhw.device.hash=499058361 

..... etc.

after formatting it looks like this:

 avd.ini.encoding=ISO-8859-1 hw.dPad=no hw.lcd.density=240 hw.cpu.arch=arm hw.device.hash=499058361 

This works for me. Now the emulator accepts almost all commands.