Oneplus 5T not detected by my pc ( Linux ) since ota-7

stanwood

@vince-vs I think you did duplicate your question here:

https://forums.ubports.com/topic/10627/focal-ota-7-available-today/5?_=1733418376741

vince.vs

@stanwood
It was well ticked.
So I unchecked it then restarted the phone, then checked MTP then restarted the phone, and unfortunately that didn't change anything.
Kind regards

vince.vs

@Keneda
It was well ticked.
So I unchecked it then restarted the phone, then checked MTP then restarted the phone, and unfortunately that didn't change anything.
Kind regards

Keneda

@vince-vs
Did you try with another USB cable ?

MrT10001

@vince-vs Have you done all system updates on the PC and updated ADB and Fastboot drivers?

vince.vs

@Keneda
Yes, however, the one I use every day is an original Oneplus cable.

vince.vs

@MrT10001
It's true that I haven't reinstalled adb and fastboot on this version of opensuse Slowroll that I've been using for 4 months ( experimental but quite accomplished, soft version of Tumbleweed ). I'm going to do it, but I don't see why it has anything to do with device detection ( adb fastboot necessary of course for reinstallation or whatever ), since it worked fine with rc ota-6 then ota-6 stable, the problem occurred after ota-7 stable.

MrT10001

@vince-vs have found that upgrades sometimes change the interaction between device and pc. I don't know why, but could be a kernel change or something in the update.

stanwood

@vince-vs So I guess it's device specific since I've got no issue on my Redmi Note 9S.
Perhaps something you could try is to reinstall using UBports Installer (don't check wipe nor bootstrap options).

arubislander

@MrT10001 When you say upgrades, you mean on the PC side, right? So then re-installing the OS would not help.

@vince.vs. Could you boot up a live version of Ubuntu and see if your device is recognized in that? If so, then you know it has nothing to do with the OTA, but with an update on OpenSuse.

MrT10001

@arubislander Can confirm on Windows 11. OP5T updated to OTA7 from OTA6. Appears in the file manager and I can transfer files back and forward. In the CLI, ADB shows no device detected. Running the latest version of Platform Tools, Win 11 updates all done.

The OP5T doesn't get the dialogue asking permission for "USB debugging". Devices shows as charging. This is a known working USB port and cable.

EDIT:

Solved my issue on Windows by elevating the command with ./ in front of the adb devices, i.e.:

./ adb devices

ADB picked up my OP5T fine and can tell it to reboot bootloader.

@vince-vs Try with an elevated command i.e. use sudo in front of adb. Sudo is not usually installed by default on opensuse from my memory so you may have to install it.

vince.vs

@MrT10001
There has been no new kernel for at least 15 days.
I remind you that other devices (USB sticks, e/os and others are detected).
What I can do with opensuse Slowroll is go back to an earlier version with snapshot, to 2024-11-17 and see if it works on this.

vince.vs

@stanwood
Yes, I just reinstalled “android-tools” to find adb and fastboot, but still need my pc to detect my phone and Ubuntu touch ....
it's an option I'll try after the one I mentioned to @MrT10001

vince.vs

@arubislander
@arubislander said " Could you boot up a live version of Ubuntu and see if your device is recognized in that? If so, then you know it has nothing to do with the OTA, but with an update on OpenSuse "

This is an option I'm considering after those explained above ....
So I need a little time to try out these options and I'll get back to you as soon as I can.

vince.vs

@MrT10001

the various options you suggest, dear helpers, will be tested, starting with a openSuse Slowroll image version 2024-11-17.
I'll need some time to come back and talk about it.
Thank you

James T

I am seeing somewhat the same issue on Manjaro.

When I plug the phone in is starts charging (in the appropriate mode according to its on/off state at the time).
But if plugged in while the device is on, it does not appear in the USB devices menu in the KDE toolbar.

It does however appear to be recognized by the OS as the dmesg output is sensible:

[489387.766340] usb 2-1.3: new high-speed USB device number 10 using ehci-pci
[489387.865961] usb 2-1.3: New USB device found, idVendor=1209, idProduct=0002, bcdDevice= 4.04
[489387.865971] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[489387.865974] usb 2-1.3: Product: 5T
[489387.865976] usb 2-1.3: Manufacturer: OnePlus
[489387.865978] usb 2-1.3: SerialNumber: d7dfe97c

and it shows up in the list of USB devices in the system info tool. It also appears in the dolphin "Places" sidebar, but when I try to access it via that, I get an error:

Could not access device. Make sure it is unlocked, and tap "Allow" on the popup on its screen. If that does not work, make sure MTP is enabled in its USB connection settings.

I do not see (and never have seen) an allow popup on the screen, but according to the UT tweaks tool MTP is enabled (and it does not allow me to disable it).

FWIW, on the PC:

$ pacman -Qs android
local/android-tools 35.0.2-7
    Android platform tools
local/android-udev 20241109-1
    Udev rules to connect Android devices to your linux box
local/gvfs-mtp 1.56.1-1 (gnome)
    Virtual filesystem implementation for GIO - MTP backend (Android, media
    player)

(Omitting a few libcamera related matches)

vince.vs

@James-T
Hello,
Sorry I've only just got back.
I'm reacting to your observation because I think it's a bug in kde 6.2.4 :
https://forums.opensuse.org/t/android-now-detected-as-portable-media-player-and-cannot-access/180896/20
https://bugs.kde.org/show_bug.cgi?id=497605
https://bugs.kde.org/show_bug.cgi?id=497539

I, for one, noticed that when installing 6.2.4, changes had to be accepted and some items were deleted, which could have caused a problem.
The small difference with your distribution is that I can't even see the device in the Dolphin pane.
I'll be patient and wait for a possible change for the kde plasma 6.2.5 version available at the beginning of 2025.
Happy holidays!

James T

@vince.vs Definitely working again now.