I've been thinking - I have a spare FP2 on my hands I don't plan on using anytime soon. I understand anbox is now based on treble and won't run on anything under Halium 9. There's a Halium 7 build for FP2. Wouldn't that be a good testing device to try and port anbox to Halium 7 ? What I'm trying to say is I'm willing to send this FP2 to Erfan it this can help the majority of UT users with Halium 7.

@cliffcoggin I am also donating. But i can't help but think this is virtue-signaling and I wish I could have avoided that - now I feel compelled to give my opinion. You haven't got straightforward answers because the answer is not straightforward. Just like @Moem I'd be glad to pay for UT. But I also believe it would crush the future of the OS if it was "mandatory". It would doom it forever. I've heard numerous times on this forum that we're trying to build a system that is NOT meant for an "ethical phone" - toting elite but rather for everyone wanting to escape mass surveillance, for one. Making UT paid-for would effectively do that. And for an open source project, losing users mean losing devs in the long run. I see that the project , and the separate dev team that compose it are in dire need of money. But making UT a service you pay for is not the way to fix this I believe. Infrastructure costs have to be able to rely on a steady flow of cash and there's no getting around a donation system. Maybe we do need to make the monthly goals more visible. It would certainly help. Now for the apps, just look at what happened with waydroid: people were hoping that sth could be made to work and paid what was needed. Some of these people most likely never donated for other UT aspects. If UT became paid-for, we might get some sort of expensive "secure phone" like some security companies are selling - only less reliable, and without the flexibility of a community that drive the OS depending on each members' separate interests.

@amy The core team is working on moving to 20.04 since quite a long time. This is heavy work, but yes, my friend, that's the plan.

@dobey I have extensively used ffmpeg for livestreaming, and with the correct flags, you can force hardware decoding on some architectures, and it drastically decreases cpu usage

@peter-gamma UT does not use Gnome, and does not use Wayland neither, so this cannot work in any way. On another hand, UT should start using Wayland as soon as it's based on Ubuntu 20.04 - then, maybe keep that link for future reference

@kugiigi Still worth it for anyone out there not having a halium 9 device...

Hello good people ! I wanted to put that into support a while ago but I thought it would eventually go away or something. Here's the thing: when someone ends a call on me, or their phone is unreachable, the dual beep that ensues never fails to pierce my eardrum, and most likely disturb wild fauna in a mile radius ^^ it's unbelievably loud, and I can't find no option to change that. The same happens for a dual call, which prevents me from hearing the actual conversation. Any ideas ? FP2 stable

Anbox integration ! YOU DID IT ! I'm so happy

@rocket2nfinity oh man i'd love this to happen but it most probably won't. Even getting a swype keyboard to run on an open source version of android (lineageos and so on) is close to impossible since Swype has been discontinued and using gboard implies copying proprietary libraries from gapps which generally results in an unstable mess if anything... So to think it could be "ported" seems unrealistic. There might be a need for an open source new swype keyboard but I don't see this happening in the near future.

I really, really don't understand why is this thread still going on. There IS an app, it works flawlessly, and once you've filled in your keys, all it asks indeed is microphone access. Now if shazaam doesn't ask you fill anything, it's probably because it uploads, uses and sell all the information it deems interesting about your person. Having different apps doing more or less the same thing is what results in the absolute clusterfuck that is the IOS appstore for example, making it pretty hard to find anything, unless you know precisely what you're looking for. And finally, I use and like the translate app, but I really don't think an app relying on a mirror of a google api is sth to look forward to.

@kugiigi nope, rc. Anyway a reboot fixed it, so I guess it's some sort of memory leak

Morph also crashing on pixel 3a as of today. A lot of webapps (Gmail for example) crash as well so it has to be related to qtwebengine. I m writing this on Waydroid browser... will reboot and report

@yk102 and use waydroid stop in the helper to fix the issues of it not restarting. Your issue with sudo is most likely you have to remount the / partition as rw because system files are not modifyable by default on UT - but not only (unless you make a daemon in upstart) you'll have to do this each restart, but also next update would wipe these scripts and permission changes

@yk102 when I have issues with morph, I use some browser in waydroid

@jojumaxx Quick answer: it may look easier, but given UT development history, it's actually much harder

@gandalf I have to say @Luksus is right. UT will give you the habit of restarting unity. It's faster than restarting the phone and solves most problems.

@zehkira maybe because of external links. Happens sometimes.

@zehkira Thank you so much for sharing your process here, despite the lack of help. I can't be of any help myself since I've never built a kernel in my life, but the process itself will be useful for a lot of people, so thanks ! Quick side note: if you plan to flash this on an actual device, bear in mind that most ubports devices are flashed aiming at a fixed partition size, dependant on the partition layout that the installer expects at first flash. There are ways to flash a bigger system image (which likely is what your hack will result in) but I don't think it's straightforward and you should research the forum before you attempt it. Good luck and keep us posted !

@rocket2nfinity linphone doesn't exist for arm64, so not a thing on pixel

@zehkira i'd say ur on the right path, providing your dongle has otp support