@lduboeuf We are not using systemd itself on 16.04, and the kernel version requirement is a bit of a misunderstanding. This update still doesn't mean we're using systemd for the init system. However, the systemd source provides many things which we do need, such as udev. Newer kernels are only required for some features of systemd, and newer versions of systemd may require newer kernels, hence the comments relating those two as a concern, along with the need to upgrade to 20.04.

It is not like a global back command would suddenly solve this problem; every app would need to implement what 'back' means to it. The inconsistent nature of what back means on an Android system is always a frustration to me, and I think it solves fewer problems than it causes. Sure in Morph it would be very obvious what back does, but I'd argue that an option to move the navigation bar to the bottom edge would be more useful. Half of the apps I regularly use don't have an obvious 'back' action; what should 'back' do when I'm viewing maps in Pure Maps, or when typing into the calculator? I agree with others that each app should consider this as oppsed to forcing a global option. Back and Home are UI hangovers that have been improved away by the Lomiri UI.

Maybe a box with title “Daily Tip”, in the box something like: “(HOW-TO) Take a screenshot“, next line “(click to visit user guide)” Text would be a link pointing to the relevant item. A Daily Tip would reveal hidden features, but also be a great way to make people aware of a guide!

@mardy Yes, this is not a regression caused by the new media hub. This behavior was present from the start.

@arubislander Thank you very much for clarification

Music shouldn't stop when locking the screen. That was a bug that is supposedly fixed in dev channel

@alan_g it sure is. Now that the issue is public though, it makes it even more important to release OTA13 to bring the patch to stable users.

I will note that for those that like a slightly cleaner look for their lock screen, that you can disable the circle thingy that displays usage stats by going into Settings and then Security & Privacy and unchecking Stats on welcome screen. Best regards, Steve Berson

Any androïd based device is already with "custom kernel" containing poprietary blobs, any porting is nut breaking because of those "things". Don't you think porters would do anything they can to squeeze the best hardware performance and the longer lifetime from any of the device they are porting UT to?

@AppLee said in [Feature Request] Meetings / Events from calendar on lockscreen: In order to move forward, I'd say a good way to improve the user experience would be to add a customization feature to the circle indicator (sorry I don't remember it's proper name). I dont think thats the best way to do things, to my understanding the circle will only be viewable in future, if you dont have any notifications on your welcome screen, i think maybe adding calender events that are happening today in the circle would be fine, but the original idea from canonical was to have events show up in a notification bubble on the welcome screen. [image: 27794976-37da4388-5ffc-11e7-85b5-c9a1370b1764.jpg]

@Fla Yes already got in touch with him thx

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