@egregiousecan There's some bug that causes random bootloop, forcing shutdown by holding all phone buttons simultaneously helps. I was also not able to boot into Ut 24.04 after upgrading from 20.04, I had to reflash the device with Android to do that.

@brenno.almeida so a premenantly temporary solution. yeah just make sure to refactor at some point. great client as is but i recommend you structure the client around the data not the other way, that way lies pain suffering and keyboard bashing.

@developerbayman i know it is dangerous to talk in behalf of others, but from my understanding the normal "users" are looking for a easy understandable no techy solution for installing ubuntu touch locally without any knowledge of terminal commands. either a good instructed guide, either a ubports kinda installer that manages to make grandma install ubuntu touch locally during her process of making her Russian salad for the family dinner. to add, this seems to become more and more relevant due restrictions and rules that are slowly being pushed by our gouverments worldwide.

this is sweet

@mihael yes it's a bug and probably in the push service. I tried to kill the service process (I don't know any other way to restart a service activated by d-bus) and after an initial failure (it seems that when the service is restarted it don't take in account the task that started it), the second time I sent a mail message the notification used the new sound. To be continued.

@hlbkv said: the device is the Lenovo M10 tablet. Which one from supported devices, X306 or X605 ?

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

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