@gpatel-fr said in standard browser: @kugiigi said in standard browser: At the moment, it's a bit random which browser will open in every boot of the device Is not it ruled by the order of rows in the configfiles table of urls-1.db ? It's not changing by itself. For fun, I tried to hack the urls table with instruction like: update urls set domainsuffix='nothing.org' where sourcefile != 27 and protocol='https' and length(domainsuffix)==0; where 27 is the rowid of the morph browser qt6 for my phone. It worked, I could start the new fangled browser from a link. Restarting the phone did not revert to standard Morph for links. At the moment I don't know if it has bad consequences but I'd say that extending UT to allow for a browser choice can't be impossible. Sadly you are right for browsers not prepared for that, Min did not start when I used its rowid instead of the Morph Qt6 one. Firefox and Chromium do not even expose http and https handlers. Maybe it could be hacked around but given that Min does not even start I could not be bothered to try. How did you determine that the row id is 27 for Morph QT6? I want to do this so I can actually open links in the modernized browser.

@MrT10001 thanks

@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 Would it be helpful for you to have a second phone?

@pparent Shouldn't this franco-frenchy thread better be in https://forums.ubports.com/category/133/french-francais section of the forum ?

@Moem Sent email. Waiting to hear back. I'm guessing you're right, cheap provider.

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

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

@wally i had this same question, i looked at the repo for the site there is an MR from maintainer with VoLTE support documentation, its just sitting there I think. I don't remember exactly why its not being merged but you can ask in that MR I bet you'll get an answer at minimum.

@messayisto I currently have UBtouch on my second B3. right now volte does not work and neither does the camera. But it recognized my mint mobile sim right away and sms,mms,data all work. Overall out of the devices I have used with UBtouch it is great. But sadly until volte works I will continue daily driving my furiphone flx1s am considering trying UBtouch on it but it works great and I don't want to lose a linux daily driver.

@oldbutndy Yeah, this topic has been raised a few times on the forum. To me, it does seem like at this point the website's Devices page may be out of date on this issue. I've made a post in the Design section of the forum, where I've seen the Website team post before.

@gpatel-fr Huh! A challenge like that. I'll try my best...

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

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.

@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

Uhmm.... I'll be honest, I don't know how to take your last few posts. I'm not sure what you are trying to tell me.