Adb (android debug bridge) after OSX Yosemite update

I upgraded my 13-inch Macbook in 2011 to yosemite.

Now I am having problems with the adb tool (1.0.31, 1.0.32), for example. when installing the assembly on the device, copying the file via ddms. From eclipse, android studio and the command line, the same performance, about 80 kb / s. 85 KB / s (68736634 bytes in 788.742 seconds)

Tested with samsung and htc device, no big differences.

Copying files to devices with the Android File Transfer App behaves fine!

Is anyone here where this works correctly, or is someone experiencing the same thing? Thinking of dropping to the Mavericks.

Thanks in advance!

Edit: with a clean new yosemite installation, I don't have this problem. After migrating my Time Machine backup, it appears again, even deleting all sdks, eclipse, android studio still did not allow it.

+5
source share
2 answers

I had the same problem on my Macbook 2012 after upgrading to Yosemite. It turned out that the problem was caused by the old version of VMWave Fusion, but, unfortunately, just removing it did not help. I did a clean install (first removing the disk) from Yosemite and installed all the applications (separately from VMWare) manually - recovering the time machine did not help.

If you have VMWare / VirtualBox or similar, perhaps you can try to remove them.

+1
source

Deleting adbkey and adbkey.pub files fixed for me. You may need to restart the adb server in order to recover the keys (in my case, Android studio did this for me).

+1
source

Source: https://habr.com/ru/post/1205222/


All Articles