@arubislander Reinstalled Waydroid + Fortitoken, and got new key from our IT folks and now it connects again.
Not clear though whether a glitch with the server (resulting in an unacceptable level of failed logins) or an OTA-5/Waydroid problem was the root cause.
@Eric-H
I'm not exactly a heavy or sophisticated phone user, so I don't need many of those features, just something that can call, text and play music and NOT deliver an endless stream of ads.
Hello everyone.
From reading the forum and webpage, I am getting somewhat mixed messages about the usability of UBports on the Nexus 4.
I am currently still running the "Official" Ubuntu system on it which works fine but clearly is unsupported. However since the N4 is my only phone (well there's an old OpenMoko in a drawer somewhere), I am rather hesitant to dive in and re-install without at least a few reports of success. Equally, since I am a very light user I don't feel inclined to pay large sums for a newer phone (and I find Android's barrage of unwanted marketing guff unbearable).
The original Ubuntu install was done using the ubuntu-device-flash tools installed on Manjaro Linux, which would be my intended route again (the only Ubuntu machine I have is my work PC which is still on 14.04).
The things that I need to be able to do, aren't that extensive: Install, make & receive calls, receive & send texts and run the stopwatch app. I wouldn't regard other limitations as showstoppers.
Experiences please.
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)
@arubislander Reinstalled Waydroid + Fortitoken, and got new key from our IT folks and now it connects again.
Not clear though whether a glitch with the server (resulting in an unacceptable level of failed logins) or an OTA-5/Waydroid problem was the root cause.
Is it possible to revert a stable-branch phone from OTA-5 to OTA-4? And if so how?
Why? See this post, so I would like to be able to test if it is an issue between Waydroid & OTA-5, or a problem at the server end.
To connect to my work VPN, I use the FortiToken Client (from Playstore) running in Waydroid to authorize connections. However since the OTA-5 update, I've not been able to get an authorization prompt, not sure if it's a problem with OTA-5/Waydroid or at the lab.
Any ideas for how to test?
@MrT10001 Thanks,
I've been using the OnePlus 5T, only issue is that the USB socket has had to be replaced, so it seemed sensible to have a backup in case of hardware problems (I'm not young). I have ordered a 6T and returned the Xiaomi; even with secondhand things I don't like supporting systems that make you jump through hoops to do what you need.
To be absolutely honest, if it was supported on the current version, I'd be quite happy with the Nexus 5 (or even 4).
I was able to get the USB-C socket replaced and it works again.
@Eric-H
I'm not exactly a heavy or sophisticated phone user, so I don't need many of those features, just something that can call, text and play music and NOT deliver an endless stream of ads.
@MrT10001 Thanks, but I think it's time to return it and try a oneplus 6t instead.
I've been trying to unlock the bootloader on this phone in order to install UBPORTS.
The only unlocker that the installer offers to download is for Windows. And while I can run the miflash-unlock.exe file using wine with the phone booted in fastboot mode and connected to a USB port, the program complains that the phone is not connected.
I have tried the suggestion on Winehq of adding the line:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", MODE="0666"
to a high-numbered file in /etc/udev/rules, and restarting udev using
sudo udevadm control --reload-rules
sudo udevadm trigger
but to no avail.
Does anybody have any workarounds/solutions? I do NOT have a Windows machine available.
I am running Manjaro on the PC.
@MrT10001 said in Hardware dying? Or software issue?:
usually usb c port on its way out.
@wally said in Hardware dieing? Or software issue?:
Sounds like hardware, in my inexpert opinion.
Thanks both, that's rather what I thought. Taking a look at the internet I suspect that trying to replace it myself is probably asking for trouble. There is a mobile phone repair shop in town so I think I'll see what they might be able to do.