@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.
When I plug my 6T into charge from a low state (same USB-A port on the computer, same cable each time), there seem to be two different rates of charging:
I've not been able to spot any obvious factor controlling this.
While it's not a problem, I'm just curious whether anyone has any idea what drives this. (Or indeed whether anyone else has seen it).
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.
@yuu-ä3 System settings offered the upgrade and unwisely I applied it only to find the phone more-or-less bricked. After a few false starts (see my posts) I was able to restore 20.04.
My advice:
DON'T TOUCH 24.04 on OP6 or 6T until there is an announcement about the port (Unless you are able to contribute to the porting work)
Managed to do it -- there's an option below "Erase user data", to enable/disable flashing the system (sorry, I wasn't careful enough to note exactly what it said) disabling that allowed the install to proceed and the system to reboot. It all looks the same as it was before the ill-advised foray int0 24.0.1.
@MrT10001 Thanks for that reminder I have had issues with Ubports install from certain ports in the past, I'll try a different one.
Just hope that charging works without a working OS since it's now saying the battery is too low 
On attempting to downgrade (installer V0.11.2, binary install from AUR) , booted to fastboot mode then:
info: Welcome to the UBports Installer version 0.11.2!
info: device detected: sdm845
warn: The device sdm845 is not supported!
info: device selected: enchilada
info: Installing Ubuntu Touch on your OnePlus 6/6T (enchilada)
info: configuring...
info: settings: {"bootstrap":true,"channel":"20.04/arm64/android9plus/stable"}
error: Error: fastboot:flash: Error: Flashing failed: {"error":{"code":1},"stderr":"fastboot: error: Failed to find AVB_MAGIC at offset: 0"}
stack trace: Error: Flashing failed: {"error":{"code":1},"stderr":"fastboot: error: Failed to find AVB_MAGIC at offset: 0"}
at /usr/lib/ubports-installer/app.asar.unpacked/node_modules/promise-android-tools/lib/module.cjs:1121:15
at /usr/lib/ubports-installer/app.asar.unpacked/node_modules/promise-android-tools/node_modules/cancelable-promise/dist/CancelablePromise.js:27:18
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Any pointers please.
@Vlad-Nirky I don't think so.
I have WiFi enabled/connected and Bluetooth off whenever I'm at home.
There's not normally any apps running (at least not visible ones).
I've not installed waydroid on this phone (I know it can get into odd states where the waydroid window isn't visible but it's not in the start menu either).
When I plug my 6T into charge from a low state (same USB-A port on the computer, same cable each time), there seem to be two different rates of charging:
I've not been able to spot any obvious factor controlling this.
While it's not a problem, I'm just curious whether anyone has any idea what drives this. (Or indeed whether anyone else has seen it).
@vince.vs Definitely working again now.
I've been setting up a 1+ 6T to replace my 5T which has a cracked screen.
After installing and setting everything up, I shut down the 6T and the 5T and moved the SIM card to the 6T. But when I tried to power up the 6T nothing happened (even holding the power button for well over 15s).
Remove SIM, boots OK, replace it no boot.
Then I powered down and left it for a few hours. then put the SIM in and it booted no problem.
Since it seems to be behaving OK now, I don't think there is anything wrong with the system. The only thing I can think is that the actual shutdown takes longer than it appears so effectively I was installing a SIM in a running system.
Just thought I'd bring it up in case anyone else encounters a similar issue.
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.