are you sure about your USB cable’s data capability ?
I can transfer data with it as I just did to post a screenshot here - so it should.
Interestingly ~$ sudo mtp-detect gives
libmtp version: 1.1.21
Listing raw device(s)
Device 0 (VID=18d1 and PID=4ee1) is a Google Inc Nexus/Pixel (MTP).
Found 1 device(s):
Google Inc: Nexus/Pixel (MTP) (18d1:4ee1) @ bus 1, dev 6
Attempting to connect device(s)
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
In fact it is the FP3+ though.
Still there is
$ adb devices
List of devices attached
an empty list.
Astoungingly after adding adbusers to the groups of my user ~$ lsusb still gives
[...]
Bus 001 Device 006: ID 18d1:4ee1 Google Inc. Nexus/Pixel Device (MTP)
[...]
When I started using FP6 I also had difficulties, also Linux. Had to use USB-A cable and maybe also have the newest fastboot installed, from app stores it sometimes isn’t. And also use a USB-Port on the back of PC and the newest on the Laptop.
1 Like
I always use an USB-A-USB-C cable on the PC.
My fastboot version was 34.0.4-debian. I downloaded the latest version (36.0.2-14143358), according to ubuntuusers.de it should run out of the box, but it doesn’t, ./adb.sh does not wake it up, and I’m too tired now.
This page Installing adb and fastboot on a Linux PC prefers non system install of platform-tools.
Thank you.
Now - after passing on the path and sleeping a little - everything is working so far. fastboot is v36.0.2-14143358 now. But still ~$ adb devices gives an empty list.
Just looking at the device, any chance you are missing sight of (or some variation of) a notification to change the default “use USB for” when you connect the live_to_PC USB cable?
In case it gives a clue … we expect not to be able to adjust USB Preferences without a live_to_PC USB cable. You do see this change on the phone at that event?
Only as you are mixing adb/fastboot in your message, you know that only
fastboot devices
will work at bootloader level?
adb devices
Normal phone and Recovery.
Thanks for the hints.
I’ve set default to (put it in brackets before) “data transfer” in the developers options already.
The phone always starts to charge and displays the directiories of the phone once the cable is connected.
The difference between adb and fastboot is well aware to me, I have refered to @mihi by pointing out that my platform tools are now the latest. adb is v1.0.41.
“no data transfert” should be choosed there
Am I missing something? If I prohibit data transfer, the phone will not be available, as far as I understand.
you are right, “data transfert” or “no data transfert” make no difference,
adb devices is able to find my device (booted in normal mode) in both cases.
what is the output for
adb --version
Gives
Android Debug Bridge version 1.0.41
Version 36.0.2-14143358
on my side, it give more information :
piero@HP-p6-2038fr:~$ adb --version
Android Debug Bridge version 1.0.41
Version 36.0.0-13206524
Installed as /home/piero/platform-tools/adb
Running on Linux 6.8.0-90-generic (x86_64)
/home/piero/ is “in my path”, so no problem…
Ah, you meant the whole output. Allright, here we go:
Android Debug Bridge version 1.0.41
Version 36.0.2-14143358
Installed as /home/mungo/.local/bin/platform-tools/adb
Running on Linux 6.8.0-90-generic (x86_64)
1 Like
My suggestion was to try to divide the problem; device or PC?
Is there any chance you are missing sight of the notification – more specifically pull down Notifications that a live_to_PC USB cable has been connected? There is the need to see the Notification which includes 
Always accept from this computer.
As you know: we expect not to be able to adjust USB Preferences without a live_to_PC USB cable.
You do see this change on the phone when the cable connects?
I feel that these specific answers would help you define that the phone was behaving as expected.
I am using an USB A-USB-C cable to connect to the PC that always had worked. I even downloaded the backup over it recently; quite slow (~5MB/s), but successfully.
No notifications so far, but I can’t tell whether there had been one before and I accepted it, which is very likely.
Connecting to the PC via the cable results in a PC popup of the directories available on the phone and the phone loading as well.
As this seems such an odd situation you might try
On phone Developer options > Revoke USB debugging authorisations.
On the PC adb kill-server && adb start-server , be sure to look for the notification
and try adb devices
Edit. I am not sure you actually confirmed that you have Developer options > USB debugging turned on.
1 Like
Yes, I have dev options active.
Well, I fumbled around with adb a little and decided to reinstall the Debian version:
Android Debug Bridge version 1.0.41
Version 34.0.4-debian
Installed as /usr/lib/android-sdk/platform-tools/adb
Running on Linux 6.8.0-90-generic (x86_64)
At least I have a clean install now.
Then I revoked permissions, the phone asked again and I granted them.
That did the trick, as ~$ adb devices now gives
List of devices attached
A30A63K70201 device
Now I can get going again.
So now I am on the FP6.
Nearly all is working safe Signal.
And I miss my background pic since I can’t find where it had been saved.
On Signal it says that there were no connection possible to my telephone number though calls work perfectly, and it is neither possible to create a QR code.
Additionally the app won’t update (133 MB to go, nothing happens on App lounge.
So I’m stuck.
Does somebody know where the backgrounds are saved?
Any hints?
So, now all is running, including Signal. Only my Matrix-Messenger will not encrypt, as it doens’t accept the safety number, no matter how often I try to set a new one. Maybe will fix that along the way.
I miss the long screenshot option on Android 15. Is there any workaround?