I can't connect ADB inside a Fedora 32 Toolbox

Ask Fedora Ask in English
, ,
1

I installed the android-tools via dnf install android-tools inside a Fed32 toolbox then I connect my phone into the computer and run adb devices, So I expect the permission modal to appear on the phone, but it never happened, even when I remove and reconnect the USB cable, and even worst, every time I reconnect the USB cable, my phone ID appears again and again in the device list, see the screenshot bellow:

b4ac90c056b14434608bc2b1a79ea2f54ca61cce.png

Some infos:

  • I’m using Fedora Silverblue 32 in a Toolbox of Fedora 32.
  • USB debug is properly enabled on the phone.
  • USB cable is properly connected to the phone and computer.
  • Every time I connect the phone to the computer the ID of the phone appears again in the adb devices list.
  • The access permission modal never appears in the phone.
2

Hi, I have the same problem recently. I think is due to an update, maybe the kernel. The current solution (hope it will be fixed) is to run adb with administrative privileges. If you already have the service running, execute:
sudo adb kill-service
Then, from now on, you have to start adb with:
sudo adb start-service
Then, you can use adb with your regular user:
adb devices
Will show correctly and with permissions.
If you are going to develop with Android Studio, remember to launch first the adb with:
sudo adb start-service
Then start Android Studio with the service running in that way. And remember that when closing Android Studio, it also kills the adb service, so you have to launch it again with sudo if want to use adb or start Android Studio again.

2 Likes
3

Running Android Studio 4.0.1 on Fedora 32

$ sudo dnf install android-tools
Last metadata expiration check: 2:26:42 ago on Thu 01 Oct 2020 09:40:57 AM PDT.
Package android-tools-20180828gitc7815d675-5.fc32.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
$ sudo adb start-service
adb: usage: unknown command start-service

Is there another way to shut down the packaged in Android Studio?

FWIW, when I run AS as root, the built in adb works just fine. It’s an ugly fix, but at least I’m not blocked.

I’d really love to be able to run it as myself.

4

Is there another way to shut down the packaged in Android Studio?
FWIW, when I run AS as root, the built in adb works just fine. It’s an ugly fix,
but at least I’m not blocked.
I’d really love to be able to run it as myself.

yep, you have to do it once:

dnf install android-tools -y
systemctl enable --now  adb.service