adb - no permissions

advocatux

@gmelchett hi, I don't know why you're experiencing an issue but the normal behaviour is that the first time you run adb with your device plugged, a pop-up to allow or deny adb shows.

Lakotaubp

@gmelchett You could try re installing 16.04 with the installer I think that picks up the adb permission for you. So you would be all set to try anbox again remembering it not daily driver ready yet.

gmelchett

Thanks for your suggestions!
@advocatux Maybe I did deny adb when trying out something weeks ago..
@Lakotaubp Hmm.. The installer does "adb -P 5038 shell echo 1" in the background and it looks like you have to have adb working in order to install anything. At least that how it looks to me.

Would be a bit sad if I had to reflash android first and then ubuntu again, just to be able to enable adb.

advocatux

@gmelchett probably the easier way is to delete the adb keys in your device so you can do that process fresh from the start. You'll find them at /data/misc/adb/adb_keys

Lakotaubp

@gmelchett I ment just run it through the installer again. No need to reinstall android first, but try what @advocatux said first is the best idea.

gmelchett

@advocatux Sadly, /data/misc/adb/ is empty

advocatux

@gmelchett if it's empty, that means there aren't keys so shouldn't have any trouble running adb from scratch. Set developer mode on, and while your device screen is unlocked, plug it to your computer.

Run adb devices, that will start the adb server and trigger the auth pop-up in your device.

Using a good usb cable is also very important. Good luck!

Stefano

@gmelchett type in terminal:

sudo adb kill-server

Unlpug the phone from PC, then type in terminal

sudo adb start-server

Plug in the phone.

gmelchett

@stefano Thanks! running adb with sudo did the trick! Strangely, I've not had to do that with android phones.

Stefano

@gmelchett I was having the same issues