@pparent Thanks for posting that article, I hadn't heard. Low probability of success can be offset by low cost and high value of success. I think the moment we're in presents opportunity like never before. In addition to the French government looking at digital sovereignty, the Danish government is trying to get away from American tech companies. I could imagine many other governments may be considering this. We don't have the interoperability rules here in Canada, but I'm still going to be suggesting to my member of parliament and a couple of ministers that the government should be proactive in examining and acting on the threat posed by the fact that most members of our government, military, and general populace use privacy-intrusive smartphone OSes controlled by a couple USA-based tech companies whose CEOs have already demonstrated a willingness to comply with what increasingly demonstrates itself to be an aggressive and authoritarian government. (I respect the forum's rules about not getting political and hope this didn't cross any lines, but I think what I said is factual and relevant to the point I'm making. I'm not taking a position here on whether annexation is cool, just trying to explain why I think there's an opportunity for UT.) Matrix has benefited from being adopted by various governments and militaries, even if in pilot projects. The challenge is much greater with mobile OS adoption, but if the resources and the need are there, it doesn't seem impossible. My government, for example, is suddenly trying to spend vastly more than ever before on the military and routinely falls short of its spending targets. I could make the argument that a secure, private and functional mobile OS is of strategic military importance And I will! Opportunities like this don't always last very long.

Viability: hmmm, at the moment: No voice calls (no VoLTE) on Pixel 3A (which WAS a primary supported phone for UT), on UT in USA (which is the third largest phone market by country, or 4th largest by region, after Europe). [alternative: VOIP - NOT available in openstore for most recent version UT] That is pretty NON-Viable, if you want a phone you can make calls on. Is that the fault of the UT teams ? I would say NO, it is the fault of the much larger system cancelling 2G, 3G, (USA & Australia , etc, now, and changing worldwide, with plans in place over 10 years ago) and the fact that the drivers for the radio chips and most others are closed source or Android or whatever. Who would be the ones to fix it ? UT dev teams, if at all. Or, what about WiFi calling ? Not functional. Is that the fault of UT devs, or other main stream code (from the larger base) being unavailable ? OR some phone brands / models NOT supporting required radio bands in some countries. NOT Viable. I think PC's are a better analogy than cars, since we are mostly talking software here, not hardware. if using cars analogy, could mention how air bag manufacturers caused a huge recall problem for a variety of car manufacturers. Q: So, where did UT come from ? A: 1) a gigantic base of hardware and software: major players who recently CANCELLED (in some countries, and in process in others) the fundamental ability of UT to make phone calls, through changes to the larger hardware and software system. A: 2) a few dedicated, volunteer developers who are doing their best to modify code for specific devices to overcome above obstacles.

I did not try your method yet, however I debugged the problem in my method. It's something (I guess Lomiri itself) that is sending a signal when the window is paused while switching. It is killing xev. The fix is to use TweakUT to keep the terminal awake, then my method works whatever the launch mode (direct > or with starting a new task &>) So I could repro the problem you have seen. No discrepancy here. I have looked a bit at Firefox and Chrome under vanilla Linux (Kubuntu 24.04) and xev reports something very different than under UT. That is, no strange events, basically the system reports the menu being created and mapped and that's all. I have also 'packaged' a recent version of Firefox freshly downloaded from the editor's site, that is, I did env GDK_DPI_SCALE=2 MOZ_ENABLE_WAYLAND=0 DISABLE_WAYLAND=1 ./firefox and the menus in the top bar display (if no scaling were done, I'd guess that the menu would display if by a stroke of luck I could hit the minuscule screen area) So my guess is that's not a clever packaging trick, that's something that Firefox is doing differently than Chrome. I searched for a Chrome Linux arm64 build but it seems that Google has insufficient resources to generate arm64 Linux builds (it's not a joke, it's exactly what is said by a Google employee in the Chrome issue tracker). I'd say that as under UT Chrome and Firefox are hitting XWayland that is hitting Mir, the problem could be all the way down to Mir. The version of Mir in current 24.04 UT is woefully outdated. When it will be updated, the way forward will be to switch to Wayland anyway and drop XWayland.

@ChromiumOS-Guy said @oldbutndy not really it would help a lot yes but you can use standard reverse engneering software to check it, also engneering roms have unlocked bootloader so you just compare that to the oldest release if an engneering rom exists. I actually spent more time looking into this yesterday. I did sequential question search using google AI, and asked about finding a bit to change, etc. The answers sounded reasonable (AI is sometimes very good at that, so I am not sure if all were true ...) For one thing, it said the setting was in special partition. It might have said encrypted. And that the special protection firmware in the T-Mobile models check any changes to that partition. I saved the interaction to a file, but have not edited it for clarity yet. But it was convincing enough to completely give up on BE2028, and the Metro model (# ?).

@pparent I have a OnePlus Nord N10 that I could give to you if it's of any use. It's running 24.04-2.x and the battery isn't very good anymore. I would reset it to factory settings and send it to you. What do you think?

@gpatel-fr it was about a year ago, I didn't do extensive testing, but none of the .mkv I tried worked, and .mp4 were very hit-and-miss. Good to know it isn't Hallium-related, perhaps there's hope to fix it on this device. @Charly the issue w/ that is that, AFAIK, Libertine apps aren't hardware-accelerated, and video playback often gets choppy (it was one of the workarounds I tried). Didn't try the snap version though.

@projectmoon said in standard browser: is there something in the DB that allows it to select a browser without excluding apps from the list by doing a fake domain? no, that's why I did this ugly hack (that will most probably not survive an update btw). Adding a column named for example pref_order to the urls table and sorting by it instead of the row_id (that can't be changed since it's an implicit column) could allow to change dynamically the browser. It would be nice to have if alternative browsers could be used. I don't know if the packagers for alternative browsers would be motivated enough to search what is missing for that.

@developer there are some freedesktop standards we need, also flatpak integration, outside of that we need eSIM support and way way better waydroid support. outside of that we need a waydroid compatibilty chart for every major banking app in every country we also need guides to what messanger has what feature supported natively and how to set it up. also we probably want to make a public transport app and start supporting every single country we can. we also need sms forwarding (i remember people asking about it in the forums) a secure wallet for NFC, so someone needs to expose the treble APIs for hardware backed encryption so we can store credit card NFC tags safely. (to please the google/apple pay users) and much much more. we need to compile every UT feature and aspire to feature parity with vanila android (not the apps just pure android) i'd make a full comparison chart but i dont have the time

@MrT10001 thanks

@MrT10001 does it also work on 2GB/32GB version with android 10 because there isn't a update to android 11?

Interesting answers here are from Plamen, from Braxtech: Q: Will there be an easily buildable close-to-mainline Linux kernel? Will changes be upstreamed to the mainline linux kernel? A: Yes, to both. We’re getting that promise from MediaTek and the integrator they hired for the linux part. Q: Will fingerprint support work on linux? How will the camera look? Should we expect the camera to be green and blurry at the start? A: The mandate is to get everything working, as it will on Android. We will communicate a linux roadmap in due course. One of the main reasons for selecting the g720 by MediaTek (and not a way cheaper alternative such as Rockchip 3588) was the strategic importance for MediaTek to run linux on it - this is their latest high end IoT chip. Most of their customers for the chip will run Linux. Obviously, the camera won’t beat iPad, but it will not be crap.

@libremax Wow, nice! Thanks to whoever did the work and thanks for letting me know!

It's beginning now.

@Vlad-Nirky That is an issue with the device from Xenial and Focal.

@Bubu Auf welchem Softwarestand bist du denn jetzt und wo möchtest du hin?

The raspi(s) would receive the OTA updates. I already looked into Mender SWUpdate, RAUC and they all seam promising. I would actually just like to know out of curiosity how UBports handles OTA updates.

@Caedem likely not how it works. The 3.5.1 was the last xenial release. Those 9k focal devices, are those who moved from xenial to focal. So there would be a bit less than 4k xenial left with numbers shrinking. And we need to drop them for security reasons at some point. Or can you justify providing a unmaintained insecure system? Also some older devices will simply die due to hardware breaking.

Latest build fixes the vertical black lines which can be seen sometimes.

Another quick update. I'm really pleased to announce that I got the SharePlugin part of the app working as well. I successfully pushed a file from my Pixel 3a to my (Linux) laptop over BT, but even more importantly for me, I was able to push selected contacts to my car kit The user interface is still too rough for the app to be published as is (at this stage, you have to select the target device based on its MAC address, which is far from convenient), but I'm working on it.

@Lakotaubp Hello. Yes, I'll be there on Saturday.