@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:
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?
I'm not sure if this is the best place to raise this, but there's no obvious place for discussing the main web page.
It seems a good idea to remove devices not supported under 20.04 from the "promoted devices" page. It doesn't look so good when you click on the Nexus 5 only to get a page that says it's not supported by the current versions.
I've had a closer look now.
Though the style is similar to a FastBoot screen, it's actually a warning screen basically saying
"You've been naughty and installed a new OS on the phone, don't blame us if anything goes wrong.",
and it times out after a few seconds.
@lakotaubp OK. I'll leave it till I'm not trying to do two things at once since the phone appears usable other than the extra button press in booting.
I've just installed ubports on a OnePlus 5T (seemed like one of the best options to be able to go forward to Fossa for under £100).
After a few glitches, I got the system installed and running, but whenever I reboot it always goes to the FastBoot screen and then I have to press power again to complete the boot. Is there any way to prevent this? I never saw a similar issue with the Nexus 5.
Thanks to everyone for the updates/clarifications.
While there is a nice list of devices that are currently supported under Focal, I have not been able to find any indications of which devices are under development, which are not and which cannot be ported.
Is that information available anywhere?
FWIW, I'm currently running a Nexus 5, so that is of particular interest.
@Flohack Indeed, after the recent testing update, the unwanted unstable one has gone.
@Rondarius said in Delete unapplied update:
Open settings/Updates, swipe the unapplied update to the right, hit the trashbin and it is gone.
I think that will only work for app updates, at any rate when I try to swipe it to the right, there is no waste bin.
A little while ago I downgraded my second Nexus 4 from the Development channel to the RC channel.
The process was basically seamless apart from one thing:
There was an OTA update for Ubuntu Touch on the Dev channel that downloaded automatically, but which I did not apply. That update is now just sitting there and (presumably) uninstallable, since it is an update to a version that is not installed.
So: is there a way to delete it? The UT Tweak app that allowed other incompatibilities to be resolved doesn't offer any help. I'd be quite happy to dig in with the file manager if I knew where to look.