The (better) Android vendors seem to think it is worthwhile... and Google is using it in their flagship phones I think. But yeah just a suggestion, might end up to be not worth the effort.

True some phones might have space issue. But in the end we are talking about what? 400 Vs 800 mb or so? Most phones will be fine with that easily. But anyways, could be optional, and A/B booting would definitely make RW hacking much easier as the video presenter also explains. But my main though is that this has a high chance of being more standardized as a normal way of booting Linux (Since Collabora and Valve are working on it), so it might be worth considering for Ubports to get behind this effort and thus build on upstream components in the future.

Ok, I have now a fresh flashed Oneplus 3t dev and I installed the GStreamer-droid based camera. In the camera app I see always a 2:2 layout but the pictures I shoot are in the layout I set (16:9 in my example). Screenshot: [image: 1604927264339-screen.png] Picture from the same position: [image: 1604927275434-bild.png] Anybody else with this problem? How could I fix this?

Not only the above but also, ARM doesnt work like that, even with arm mini computers, arm based laptops, and eventually arm based desktops, need a image purposefully designed for the hardware. You cant boot generic Ubuntu on the raspberry pi, you have to download ubuntus specific raspberry pi image.

@cliffcoggin said in What were scopes?: namely a way to arrange apps into folders or categories on the desktop: communications into one, maps & navigation into another, utilities into a third and so on. This is not what they did. To arrange apps the app drawer will be the place for such evolution. Scopes brought content arrangement, actual images or audio files, they acted more like a search engine for various kind of content. A scope for Yelp could return restaurants nearby. a scope for foursquare was able to search for restaurants, monuments or hotels...

Hi @Fla, It is unfortunate that we didn't find that in time for OTA-13, but since it is already in stable I don't believe it is a reason to cancel this update.

@domubpkm I'm not sure what it's doing exactly, but a quick look at the code looks like it could certainly be transitioned to Morph.Web and QtWebEngine, perhaps it also needs to use webchannels or websockets for what it's doing.

@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]