@uxes Well I guess this type of gouvernemental organization will not be interested in individual feedback of individual, but it is consulting some associations, so with a lot of luck fondations like Ubports might have a word to say.

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

@ChromiumOS-Guy said in OnePlus just informed me they will NOT unlock bootloader for a device on bought on Ebay.: i dont think a port will just happen somebody needs to activly work on it That's true, but from what I heard, that is happening. Well, at least for the 8 and 8t. Haven't heard about the 8 Pro.

can you point me to the repos

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

Notifications are available in version v7.86.0-1 ! In order to get notifications you need to keep the application opened. Somehow you don't need to un-suspend the application in Ubuntu Tweaks, it seems the Xwayland apps are not suspended by the system. So note it might affect a bit battery life. Next version will focus on corrections of main remaining bugs or things that display not well in the UI, because not adapted to responsive design ( left menu, search message, medias of a group ), and if possible fix bugs with contentHub.

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

@PhAndersson Right, while searching for another problem, I just stumbled on something that looks like an answer. there is in this directory: /etc/dbus-1/system.d a bunch of files configuring the authorizations for dbus; for example (taken for its brevity): cat com.lomiri.UserMetrics.conf <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <policy user="usermetrics"> <allow own="com.lomiri.UserMetrics"/> </policy> <policy context="default"> <allow send_destination="com.lomiri.UserMetrics"/> <allow receive_sender="com.lomiri.UserMetrics"/> </policy> Now, it's sure that the system.d directory does not seem the right place for a user level service. At the moment I have no clue where a file configuring the dbus authorization for the org.bluez.obexd service should be created. But I tend to think that creating one is the proper thing to do because I don't see a reason why obexd should be forbidden to send message to its agents. It should be allowed whatever security reason there is to block general message sending. So this could be the proper way (TM) for your application to run confined.

v0.2.0 is released Changelog: Battery status sync: added kdeconnect.battery support. Multimedia controls (MPRIS). Theme settings: new Settings page with Bright/Dark/System themes and consistent readable palette across surfaces/text. Notification improvements: IDs standardized to strings with backward-compatible conversions on receive; new “keep on remote devices” toggle (skips cancel sends);. Find‑My‑Phone: ringing support with notification and volume boost. UI polish: service install prompt simplified (“Daemon is installed.”) and layout fixes.