Hi everyone. I didn't have to wait long to see it. This morning I turned on my phone, and now I'm getting the time zone error on version 24.04-1.3 (rc). I shut down the phone again to see if the error would occur after a quick restart. Yes, it did. I would have been surprised myself if the error had only occurred in the stable version. But we’re leaving no stone unturned. I’ve now sporadically resolved the issue by setting the location to Dubai (UTC+4) instead of Berlin. However, that shouldn’t be the permanent solution.

@gpatel-fr Great find! I don't know where to search but maybe we need to inspect the code in the OS for handling the bubble. Some time ago I had to write a service worker for browsers and I had to specifically program what it is done when a notification is clicked.

@fischer.poco said: zBsp.: Xiaomi Poco X3 NFC / X3 da fehlt im Netz dann das "/ X3" Damit wird gemeint: Xiaomi Poco X3 NFC oder Xiaomi Poco X3. Oneplus Nord n10 5g ist aber eine gute Wahl!

@rocket2nfinity if someone can donate the hardware I am willing to give it a go.

@mariogrip Thanks for the work done Mario, Audio seems to work video playback, internet itself works fine, Teleports/Firefox/Greenline work fine. gps seems to work, first connection on bluetooth works. For some weird cause i cant seem to hold click the "kde connect" app in the drawer to open it in openstore, seems to work for other apps, so not sure if its this update... But uhm which version of Morph browser am i supposed to open now? the normal one keeps loading, and the Qt6 beta crashes it seems to miss some files QT6 browser: libxml2.so.2 (no file or directory) Morph: missing EGLConfig, QRhiGles2, context is lost. .qml:417 cannot ready property 'count' of undefined Other then maybee the biggest 'daily driver upgrade' all works fine xD?

@MrT10001 I ran whatever update was available. Didn't say it was 24.04. It seems to have broken the installation. I'm back to the lenovo logo boot loop. Will I have to go back to factory or do you think I could run the installer again to redo the 20.04 installation?

Your BE2015 install path was useful prior art for cracking the BE2012 (T-Mobile US, not Metro) variant — same chipset, slightly different blockers. Sharing in the spirit of reciprocity. Full BE2012 installer up at https://github.com/dcherrera/n100-be2012-crossflash. macOS-native EDL flash (no MSMDownloadTool needed), plus a small binary patch to /usr/sbin/ofonod that fixes a SIM-init blocker which leaves Modem.Features stuck at ['sim'] on first boot — same modem firmware family, may be relevant to BE2015 users on certain SIMs too. README has the offset table if anyone wants to verify against their build. Also confirms your "T-Mobile SIM works, Verizon SIM doesn't" observation on the BE82CB modem firmware — same outcome on our end, since the modem firmware is T-Mobile-band tuned.

I successfully flashed ubuntu touch on it. I bought this model not knowing it wouldn't work. So I spent a few day putting together a work around because honestly it just sounded like a fun challenge. You can look through my findings here. https://github.com/dcherrera/n100-be2012-crossflash. Just a heads up, you should be able to clone this and claude code should be able to orient itself and help you get it done. i tried very hard to make sure the documentation was complete.

@Linus67 said: 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. Did that and it seems to work. Battery drain is in normal levels again. Weird quirk, though...