Aplologies for the inconvenience caused. The issue was indeed a bad update causing the upgrader to clear a directory it should not have. See https://github.com/ubports/ubuntu-touch/issues/1395 If you are affected by this issue, it is now safe to reinstall Ubuntu Touch using the UBports Installer. You will not lose any data.

@natineo sadly it is an old known problem, and it seems that we didn't find any volonteer to dive into it This bug is logged here : https://github.com/ubports/ubuntu-touch/issues/239

Hi! Worked just fine, just one thing about it: in Step 7 you need cp /home/phablet/Downloads/nvram-by-skyneel.com/WIFI* . nvram-by-skyneel.com is missing in your path. Thanks a lot!

@gregb49 I had same issue on one of mine. Battery replacements are cheap enough and easy to do. Give it a go. Mine is fine now.

@markus228 said in Ubuntu touch and xa2: What happen Probably not much :man_factory_worker_light_skin_tone:

I've made a note of the tedit paths and commands and may try it at a later date. Or anyone else can try and post here if they please. For now, I prefer the uText method as described in my post here: https://forums.ubports.com/topic/3902/how-to-open-a-txt-file-that-i-copy-from-pc-to-fp2-with-ut/12?_=1583692201634 Cheers, friends.

Hi, I am still playing around with my N5 and I have tested some Android apps with Anbox. Spotify works and I can cast the music via WiFi to my stereo and via Bluetooth to a speaker.

Unfortunately, the ports.ubuntu.com repository is separate from the standard Ubuntu archive, and there are very few, if any, mirrors available that include armhf or arm64 packages. So, you can't really change the repository in this case.

@domubpkm Thanks! But I think it would be wiser to wait a little bit more, than spending money on a new phone (OPO) and then buy another new phone (Pine) after I bought already a new Nexus 5, although my CAT S60 is still kicking...

@HendriXXX Thanks, your video helped a lot!

Today, there was an update for the Recorder app. I tried again to move a recorded file to my PC - this time it worked even better - my phone was left on. No issue.

@Flohack said in Power drain, perhaps caused by app Notes: @guru Yes unfortunately dekkod is known to enter a busy-waiting loop when it cannot reach any network resources from the accounts - do you turn off your internet over night? Btw, the looping/polling proc was not dekkod but dekkod-notify. Looks like a concept flaw polling every second.

@dobey said in Install Ubuntu Touch on LG Nexus 5 with Android 4: [...] However the razor images are also the same as used on deb/flo, the first gen 2013 Nexus 7 tablets. Thanks for sorting this out. Mine says "product name: deb" in bootloader mode, but there's no such image on Google's download page. I'll use razorg then to compare firmware versions.

I was also affected by this issue after updating to version 66 today. Reinstalling via the UBports Installer resolved the issue. Install options used: Channel: 16.04/rc Wipe Userdata: No Bootstrap: Yes Format system partitions: No

@Lakotaubp Thanks, that did the job.

@Giiba said in WiFi issues on Pinephone (Braveheart): ... I found if I entered: $ nmcli r I got something like: (I couldn't get a screenshot... a different bug) WIFI-HW WIFI WWAN-HW WWAN enabled off enabled enabled Which obviously seemed wrong, a bit more poking with the 'help' function of nmcli and I found I could switch 'WIFI' to enabled by: $ nmcli r wifi on and now the the output of 'nmcli r' is: WIFI-HW WIFI WWAN-HW WWAN enabled enabled enabled enabled Then wifi worked fine, has persisted through reboots, and is still fine a few hours later. What remains unexplained is why wifi worked (I got a list of visible networks) before failing. Similar behaviour here. WiFi stopped working the first time I tried to connect to a network with WPA Enterprise security, and didn't work from then on, even when I restarted. Not sure if the WPA Enterprise part is a coincidence. I saw "disabled" where your post shows "off" in the output of nmcli r. nmcli r wifi on got it working again. Thanks!

@dobey touché

@ziggutas Maybe I'm just not understanding the quote "It's a feature which needs to be enable on the device itself. Please create a bug request against the repository of your device and mentions this commit..."? Does it simply mean make a regular bug report on git hub?

I'd like to point out that my Meizu Pro 5 on devel is not affected, while my BQ M10 FHD on rc is.