Android Question After updating to version 13 I can't start debugging via USB

Sagenut said:

Did you updated configuration paths to new SDK folder and Java?
Also try Restart ADB server from Tools menu.

Click to expand...

teddybear said:

1.Show your Paths Configuration
2.Could you start debugging on an emulator?

Click to expand...

Sagenut said:

You could the procedure at this link
https://www.b4x.com/android/forum/t...nger-recognized-by-the-ide.139867/post-885842
It will force the phone to pair again requesting a new RSA key.

Click to expand...

B4A Version: 13.00
Parsing code.    (0.06s)
    Java Version: 19
Building folders structure.    (0.73s)
Compiling code.    (0.12s)
Compiling layouts code.    (0.01s)
Organizing libraries.    (0.00s)
    (AndroidX SDK)
Compiling resources    (0.06s)
Linking resources    (1.25s)
    build tools: 34.0.0, android jar: android-34
Compiling debugger engine code.    (0.01s)
Compiling generated Java code.    (0.17s)
Finding libraries that need to be dexed.    (0.01s)
Dex code    (0.84s)
Dex merge    (3.69s)
Copying libraries resources    (3.29s)
ZipAlign file.    (0.05s)
Signing package file (private key).    (0.51s)
Installing file to device.    Error
* daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
adb.exe: failed to check server version: cannot connect to daemon

teddybear said:

1.Run cmd and then Go C:\Android\platform-tools folder
2.Run adb devices and see what happes

Click to expand...

Sagenut said:

Maybe ADB is getting blocked by firewall?

Click to expand...

teddybear said:

Try to download the version platform-tools, then rename C:\Android\platform-tools fold and extract the zip to C:\Android\platform-tools

Click to expand...