@domubpkm I had to move the number back into the info string. Some translators raised issues that the separate number breaks translation in their language. So we are using this "<b>%1</b> files found, swipe an entry for file info and delete options" variation now. Still translatable and a bold number. Not perfect but should work.

@Moem After clearing the saved Wi-Fi connections, power consumption is minimal. [image: 1779434595907-8f6aae21-1785-4f50-8c3a-e94f2ba0bb02-image.jpeg]

Hi @danfro, I just wanted to point out that someone has to take on the task of porting it; it’s a huge undertaking, and there’s a chance it might not work out in the end. And, who here is willing to do the groundwork and look up the author’s questions? Greetings Mario

@Moem said: I will repeat what I've said elsewhere: I will bring this subject to the table in the next meeting of the Board of Trustees. That's what I can do and I'll do that. Until a possible workaround is found, it seems appropriate to notify users of the installer. I have therefore created the following ticket: https://github.com/ubports/ubports-installer/issues/4565 Since other countries may also be affected, it would be helpful to know which ones. I have therefore created the following thread: https://forums.ubports.com/topic/12291/internet-access-restriction-for-ubports-installer-list-your-country That's what I can do, and I did it

@arubislander Thank you for the advice, it's truly appreciated.

I've found the cause of the increased battery drain on Wi-Fi. Clear the list of saved Wi-Fi connections: Go to Wi-Fi -> Wi-Fi Settings -> Saved Networks and tap “Forget” next to all the networks. Then reconnect to your home Wi-Fi network. After that, battery drain in standby mode will return to a minimum of < 2% per hour.

@Vlad-Nirky Its not an impression, the app is inefficient in its current state, optimizations are needed. The perception will vary depending on the amount of whatsapp data you receive. Its a combination of having the backend written in python (which means that on receiving new events, a python process is created to process it on the fly) and the qml frontend re-rendering on each event that emits a qml update. So for example receiving a new chat means re-rendering the whole chat list. Not too worried about it yet, but something for me to look in the future. I'm not 100% decided on how this app will manage its data so not gonna waste time optimizing something that might change. Probably will get back to this once the app support all possible Whatsapp events / message types, which will give clarity on how to model everything.

@AntiMS The experimental Halium 12 build has two reports of succesfull VoLTE - both originating and receiving (non US), and several one way only calls with or without audio. I personally have tried it with all three US networks. Verizon has trouble, but with both T-Mobile and AT&T networks you can receive calls with audio in both directions. However, making a call fails and the dialer hangs. Logs were sent to the porter, and it is suspected that this is an ipv6 vs ipv4 issue. We can help you more efficiently if you join the ubports NA Issues Telegram channel.

@sixwheeledbeast I guess what I was pointing more toward is that there are situations or people that need a more predictable control panel. To be clear, I like the panel and the one hand scrolling. Its gorgeous to look at and most of the time its convenient. But it does mean that it is not good in emergencies. For example: say I urgently need to: Turn on wifi. I know to flick down just right of the camera notch, and the toggle is reliably about halfway down the page. access system settings. I try to flick down from the right top corner but what page I land on is a bit of a lottery. I then need to scroll to adust the pagu before I can do what I need. It is even worse for the items to the far left on the menu.

@arubislander That's the correct answer, I missed the fact that these modules may not only be completely disabled in a specific kernel, but also be built-in. In which case the desktop solution would do nothing

@MrT10001 then I guess it's not for me. Thank you all for the clarification.

@projectmoon exactly i dont mind confinement anymore as i used complain because i didnt understand now i do and i see ALOT of missing api thats why i made "workspace" --->still needs lots of testing but i have to say im not happy having to make a workaround solution ....as it kinda breaks the whole design point ..

is there a way to move to the stable channel? in the settings & wiki i can only find the daily channel..

@gpatel-fr I just tested it now with sms and it works - it uses the new selected Meesage sound. So it is only for notifications from apps (like Dekko, Greenline) that the Message sound is not updated unless a reboot. It starts to sound more like a bug?

One last update to the links in the original post. There is now sound/music with an option to turn it off. Hope you enjoy it! Not getting any more feedback, so I presume there are no more bugs? If I don't hear anything else I will release it to the open-store in the next day or two. Thanks for testing!

@shcarl276 said: It's not the matter of the devs not being ABLE to do something. Sorry, but I disagree. This is not on the dev's plate.

Ah, no. I don't think it's possible to pass an url + the appid link. The idea is to open the app...

Glad I could help, and good luck on your installation!

OK, yet another test. I just tried connecting the Quintus to my main UT phone (the Pixel 3a, Focal). during discovery, the Pixel appears in the list of neighbouring devices on the Quintus (and the Quintus on the Pixel) when I tap the Pixel in the list on the Quintus, I'm asked to confirm the PIN on both devices, which I did the Pixel then moves to the "Paired devices" section on the Quintus, shows connected for a few seconds then returns to "disconnected" on the Pixel, it remains in the list of neighbouring devices (and a notification is re-issued for the last received SMS, which was left unread) Tapping the Pixel then tapping "connect" causes the following: the Pixel shows as connected for a few seconds on the Quintus, then it returns to its "disconnected" state nothing changes on the Pixel on the Bluetooth settings page, but a notification is re-issued for the last received SMS (strange, I know, but I got that same behaviour twice).

@RJDan here is a link to the last (2023) post done by a NodeBB member about it.