@fuseteam said in Snap Crackle and Pop! Readwrite rootfs is overrated: When i first heard of ubuntu touch i was pretty excited to see a OS i could be in control of, as i never like how android worked and such. like many the idea of using my phone as a "PC" really fascinated me, especially since at the time i had a laptop with 3GB of RAM and smartphone were beginning to get just as much RAM. you can imagine my disappointment when canonical announced the drop..... +1 my brother! sooo what packages already work? according reports and my own (crude) tests the following packages appear to work: vim nmap htop mc curl tmux tree sshfs NICE! :beaming_face_with_smiling_eyes: Thank you for this awesome tool/project and I will keep an eye on it in the future!

When these "modern" OS-es start, the clean desktop is shown, meaning the user knows it is there, and for some reason the starting state is off limits if there is one or more programs open. elementaryOS also does this. Even the keyboard shortcut to show the desktop is removed. The section isn't even there anymore. Would be interesting to see what kind of problems people think they are solving by implementing this. It is 100% against convention of anyone touching a computer or device the last 30 years. The upside seems to be not accidentally minimizing something you are working on. It is also not how the system the user is familiar with and is using has functioned in the past. For my own sake I will say this makes me think of something I know I can use, into something where I think I can't figure it out and no change was needed. And no, it just isn't possible anymore. No explanation. The mind compartmentalizes information in structural hierarchies, and the spatial awareness to keep track of this is something you can do with cognition, but the ability to look at a clean slate actually has function. It is the closest thing you get to seeing where your files are by default. Yes, that place someone decided no files are to be shown, before they decided file hierarchy is something the user shouldn't do. There is a serenity to having just a clean slate to go back to. It is as familiar, and not having what you are doing visible on the screen is useful. It also has the benefit of vested interest and familiarity in that the user often changes the desktop. Thus making it their machine.

@aarontheissueguy Bear in mind that this how-to might contain some steps that are no longer necessary. Installing Qt 5 for instance is not needed. Clickable downloads the requisite container images with everything installed necessary for the tutorial.

@GizmoChicken said in 2019: Time to make Unity8 great again?: Given recent progress, how about 2020Q1: Time to make Unity8 great again? I like it! Maybe we can just rename this thread?

@tricky there is a lot of issues and not a lot of people or time to implement them. If you are able to help out in any way, I would encourage you and anyone else who is able to, to do so.

@Taiga-Woods I experienced that today, too. At the end I deleted and reinstalled OSM Scout Server (rebooted in between). Everything worked again afterwards and the maps I had downloaded were still there. But I'm also interested if there's another solution...

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

I like it

@travisfw this is an interesting question. Are you looking to fill that role, or get in contact with someone who fills that role?

@Dunbrokin

@peat_psuwit I overlayed touch.pa for two reasons: to make bluetooth calls work more reliable. So this one maybe get fixed by the MR. to make wired headphones work. For this it was needed to explicitly add the rate=48000 parameter to the load-module command: https://gitlab.com/ubports/porting/community-ports/android10/fairphone/fairphone_fp3/-/blame/halium-10.0-focal/overlay/system/etc/pulse/touch.pa?ref_type=heads#L55

There is No update after February 25 for noble next.

Updated the OP with links to the postmarket versions. Question for @PINE64 : right now (2020-07-15 16:11 UTC), both versions say the packing contents include "USB-C Docking Bar – 2x USB Type A ports, digital video port, and 10/100Mbps Ethernet port" Does this mean that the board in both versions is 1.2a? (Apologies if I've missed the monthly update. Right now all Pine64 sites seem to be deluged with traffic. ) Edit: from reading the Pine64 July update, it seems that both versions of the phone have the 1.2a board with the USB fix (hurrah!), but only the 3GB/32GB Convergence Package has the Docking Bar. Please correct me if I'm wrong about that. Edit 2: the page in the store is now correct.

@libremax said in UBports and UT stats: the number of supported devices which jumped by more than 20% this quarter Amazing!

@Capsia Please let me and @NeoTheThird squash this dat in a more useful representation. The current maturity is a gut feeling value and need to be replaced with a better value from the actual test results. However, it will be still a bit hard to compare devices with each other, aas we have fully to rely on what porters think its working. There is no good QA process when we do not have a single QA team that can test all devices side by side. Also, my I know, who talked with you from the foundation side to actually work on this page?

@danfro Use our CI, install it with ubports-qa - I let most of the stuff be built via CI, completly avoid crossbuilder.