I'll try to answer base on what I know. Note I might be wrong though Just check the update page and make sure to install all app updates. If it shows no update then you're most likely in the latest version. If you're on stable channel, I believe push notification is enabled so you'll get one if there's a new update. If you mean the link below, then no they're unrelated. That's just a job that builds the same image (or stable) over and over again and it was daily before so the number got really big. Just ignore these builds. You'll only need it if you want to reflash. https://ci.ubports.com/job/rootfs/job/rootfs-pinephone-systemimage/ No I'm not in stable channel on my pinephone right now so I can't see it myself and refer but in the OS build details page, you'll see different values such as UBports Image part and Device image part. OS Build number shows your current build number. Not sure if the pinephone shows "OTA" label or just build number for now. UBports image part is the build number/date for the rootfs or the actual OS. Device image part is the build number/date of the device specific software such as kernel. I'm not completely sure on this but this is what I know

@Flohack I get symlink errors with pull user-data, but I found this solution and it works: Consider this my "log" how I've transferred data from phone to phone (worked between two nexus 5 devices) without SD card I hope it will be helpful for somebody - but I've basically used combination of two methods described before plus some man pages NOTE: both devices have ubports image installed and are prepared for adb access () SOURCE DEVICE After connecting source device on PC commands in terminal as follows: Reboot phone into recovery: adb reboot recovery Acquire root: adb root Activate shell: adb shell (command prompt will change to # sign) Backup system-data (this will also create log files, that can be examined for possible errors) : tar -czpv -f /system-data.tgz /data/system-data/ >/system-data.out 2>/system-data.err NOTE: I've just put these files into root directory and it went just fine and pulled just one file into connected computer since adb has much better chance to transfer one big file without errors than many small ones logout from shell to your terminal (Ctrl+D) NOTE: I am assuming computer is linux with root access etc. this sub-step can be done before step 3 5.1 go to directory where backup data are to be stored in PC (using cd and mkdir commands) transfer data from phone to PC adb pull /system-data.tgz 6.1 it is good idea to have logs copied too adb pull /system-data.out and adb pull /system-data.err but it is not necessary steps 3. to 6. repeat but with user-data instead of system-data excluding .cache folder (so commands will look like tar -czpv -f /user-data.tgz /data/user-data/ --exclude='data/user-data/phablet/.cache' >/user-data.out 2>/user-data.err, adb pull /user-data.tgzetc.) NOTE: data which can be transferred by MTP should be moved that way since process of packing can take quite long for user data and may even stop/fail (e.g. not stopping process, just waiting and overheating battery, because all outputs are transferred to log files) if there is not enough space for package DESTINATION DEVICE Reboot phone into recovery: adb reboot recovery Acquire root: adb root Push archived data from PC to phone (root folder) adb push ./system-data.tgz / and adb push ./user-data.tgz / NOTE: in case of failure pushing both files and then unpacking both in adb shell it is possible to work the process "per partes" so following steps 4. and 5. will be done after each push and removing archive from phone (rm ./system-data.tgz in adb shell and then returning by Ctrl+D to PC shell) Activate shell: adb shell (command prompt will change to # sign) Extract archives tar -xzv -f /system-data.tgz and tar -xzv -f /user-data.tgz Restart phone, unplug, recharge (battery will be probably rather low ) check data and switch SIM card PS: After finishing and documenting the process, I'we found out that WiFi settings has not been transferred to destination device those must be somewhere in .cache folder then (I don't really mind, messages, apps, contacts and other settings are quite enough for me). It's form this thread: https://forums.ubports.com/topic/1683/migrate-data-from-device-to-device/21?_=1595872454998

If you think there is an issue, and aren't a developer, then simply open an issue in the issue tracker, and let the developers deal with it. Constantly repeating and making nonsense analogies in some attempt to try to force others isn't helping anyone. There is no "Home" in this respect, and having NTP and a connectivity check hosted at an Ubuntu sub-domain are not threats to your privacy. If you think they are, then block the connections yourself on your own system and be done with it. Make merge proposals to make it more configurable. Do something other than just sitting here repeating the same tired analogy trying to force us into your point of view.

Thank you, but I'm not so sure... The Ubports version is changed compared to standard version... Particularly when it come to this function's return value... So I'm hoping the ubports change is what I need. So I'm now trying to compile ubports version of mir... And the try it (but it's a lot to compile and there are include files missing)... So it takes a while.... So I try that first, before venturing into the kernel.

@CiberSheep Yes, thank you!

@Flohack @peat_psuwit I believe I got this new version in the rc update from this morning. Thanks to everyone for the amazing job pursuing this... I'm still patiently waiting for my Pro5 to work without noise for bluetooth calls... Again, great job!

@db579 Some informations are here : https://github.com/orgs/ubports/projects

@wdehoog Podbird on OnePlus One I guess it could be app specific - will double check with other apps to see if it's the same behavior

@dobey said in Compass in Device Checklist: @jezek said in Compass in Device Checklist: Abstraction on what level are you talking about? In qtubuntu-sensors. Thank you for reminding me. I forgot, there is already an issue opened on this.

There are many issues around being able to support snaps or flatpaks. For appimage, it could perhaps work via libertine depending on the app, at least on a very basic level. You likely would need to manually create a .desktop file inside libertine container, to get proper icon and launch the app from the app drawer, though.

@potet said in UT and maps program/GPS in the USA.: GPS providers Not here to correct anything, just to share The GPS providers are providing the GPS chips in our phones. For cartography, you there are several providers for: maps (vector data representing features: roads, buildings, etc.) tiles (the visual components of maps). geocodes (names for features like addresses or road names which allows to search something in a map) The first one is served by OSM, the second one is usually a third party service provider and the last one can be nominatim which is a services provided by OSM but can also be part of the third party provider. Navigation is another service that third party can offer and is able to resolve how to join two different locations. Hope it can help someone to figure things out or better understand this complex world.

https://www.phoronix.com/scan.php?page=news_item&px=Generic-USB-Display-Driver-V3 Looks like this is actually happening and coming to Linux Kernel 5.9 / 5.10 Sadly unlikely that it could be backported to ancient 3.x kernels though.

@ell1e said in Any plans to have encryption as an option in future Ubuntu Touch installers?: All I'm hearing is excuses, to be honest. "It's not perfect, so that makes it fair to not provide it." No, I don't think it does. Sounds like you might want to get some hearing aids then Home folder encryption would already help a lot as you say, but is that in the installer? It should be then You're more than welcome to work on it

@kugiigi yeah that's what I'm referring to. I couldn't think of the phrase.

Maybe it would be a good thing LM and Sprint dudes to work together.

@TobsEnd I also have this problem since a few months in devel.

@lduboeuf I dont think anything is in upstream for that, because they never supported RIL properly there. That was the reason for the fork but the ril driver was never upstreamed then. So I think we need to hack into this on our own...

Short feedback: Power button works as expected with 2020-W16 snapshot. Thank you!

@dobey Ok, thanks. Then I'll have to wait 'til someone fixes this.