Hi all!
After start AVD manager in B4A I see window:
Starting emulator for AVD '320_240'
createRenderThread failed to connect
And if I run Compile & Debug I see window:
Parsing code. 0.00
Compiling code. 0.22
Using existing AndroidManifest.xml.
(Project - Do Not Overwrite Manifest option is checked)
AndroidManifest-Example.xml file will be created instead.
Compiling layouts code. 0.00
Generating R file. 0.73
Compiling generated Java code. 1.13
Convert byte code - optimized dex. 2.31
Optimized dexer failed. Switching to Standard dexer.
Packaging files. 0.22
Copying libraries resources 0.00
Signing package file (debug key). 0.95
ZipAlign file. 0.30
Installing file to device. Error
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Restarting ADB Server may solve this problem.
Tools - Restart ADB Server.
If I run emulation by adt-bundle-windows-x86(java) - all OK.
Is it common problem? I need advice!!
I have PC- WinXPSP3 & B4A2.50
After start AVD manager in B4A I see window:
Starting emulator for AVD '320_240'
createRenderThread failed to connect
And if I run Compile & Debug I see window:
Parsing code. 0.00
Compiling code. 0.22
Using existing AndroidManifest.xml.
(Project - Do Not Overwrite Manifest option is checked)
AndroidManifest-Example.xml file will be created instead.
Compiling layouts code. 0.00
Generating R file. 0.73
Compiling generated Java code. 1.13
Convert byte code - optimized dex. 2.31
Optimized dexer failed. Switching to Standard dexer.
Packaging files. 0.22
Copying libraries resources 0.00
Signing package file (debug key). 0.95
ZipAlign file. 0.30
Installing file to device. Error
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Restarting ADB Server may solve this problem.
Tools - Restart ADB Server.
If I run emulation by adt-bundle-windows-x86(java) - all OK.
Is it common problem? I need advice!!
I have PC- WinXPSP3 & B4A2.50