@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.

@advocatux Thanks, it's working now.

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.

@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.

I've a feeling that the USB-C port on my oneplus 5T may be wearing out,

Symptoms:

• If I plug it into my charging brick (when turned off) it boots up and the battery level appears, flashes a couple of times but then the phone appears to shut down.
• Similarly when plugged into a USB port on my PC. N.B. I've been using different USB-C cables in the two cases.
• When booted up, it (usually) fails to charge from the brick. It does charge sometimes (but not always) from the USB ports on the PC [I've not done a detailed enough investigation to be sure whether it's really sometimes or some ports, though I suspect the latter].
• There is never a message in dmesg on the PC (Manjaro / KDE) and nothing appears in the USB devices list.

Since my old Nexus 5 was still lying around I was able to verify that that is detected as expected (though as was always the case accessing it from the PC is tricky).

It seems unlikely that there is a software issue that could cause this, but has anyone seen anything similar?

Also I've forgotten which protocol is used by the 5T when accessing on a Linux box, can someone remind me please, so that I can go onto the Manjaro forums to see if there are any issues with that protocol and Plasma 6?