@egregiousecan won't boot at all? Can you boot to the bootloader (fastboot)?

@libremax Spain when there's football on the tv (I'm not joking)

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

Hi, I am back again. I didn't want to bother you with my long posts until I made it. Still working on it, though. @wally, as I said, my phone sent the SMS but get no response. I hadn't yet updated anything. I was chatting with the Xiaomi customer service and told me two things: Clear data/caché from "Settings" --> "Apps" --> "Manage apps" --> "Xiaomi SIM Activaton Service". Change "Settings" --> "Additional settings" --> "Languages and input" to other language, in my case to "English (UK)". You can try it. I don't know if both are necessary, but were simple to accomplish and so did I. Tried again, SMS sent and paid, and MIXiaomi account was linked to my phone number. Next step, was linking the account to "Settings" --> "Additional settings" --> "Developer options" --> "MIUnlockStatus". For this to work I had to turned off the "Find Device" option: "Settings" --> "MIAccount" --> "Xiaomi Cloud" --> "Find Device" --> Off. And it did the trick. This is all like a puzzle, a jigsaw, an escape room ... Still no luck, though. The device is still "deactivated". Again Xiaomi customer service said that this matters are part of the "Xiaomi Community" and that I should asked there. I found an interesting post, that maybe everybody is aware of, but me. I asked it here before, but it seems that, yes, the unlock request must be made within this app. I made a Google account just to download the "Xiaomi Community" app. In the left lower icon, "ME, go to "Set up" and "Change region" to "Global". Go back to "ME" and "Unlock bootloader" will now be visible. Click on it and mine says "Account must be registered over 30 days". I have mi fresh Xiaomi account, my fresh Google account and one week still to go ...

At a suggestion from @sander I implemented the Content Hub to select the local fallback audio file. The API of https://www.radio-browser.info is great, and also already implemented by the Radio app as far as I can tell from a quick glance. So I would rather ask Patrick Fial (does he have an account on this forum?) to add something like a 'copy URL'-button to the station in the favorites-list of his app. Or create a merge request for this myself, of course. @vlad-nirky Classic2 yes! Not waking up too gently though ;-).

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

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

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.

Buddy, is anyone already working on this device? What’s still missing, and how can I help?

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

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

@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

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

Yesterday all of our SIP in Germany stated, that they will shutdown MMS at the end of June. So it's important to have an alternative as RCS for people who need this kind of service.

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

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