@danfro nope! Apparently it should have been -2 instead of -1. I've updated it in the original post.

@James-T It worked for me, but I used Win11 executable. Try changing the USB port, then the USB cable if that fails. For others, the OP6 and 6T is being worked on so Noble will work.

@Moem lol

@PhAndersson Great ! have happy file exchanges with your car

@oldbutndy download the EU firmware (EOL) and the real firmware for your version for EOL, then copy the identifers in the scatter xml file from that version to the EU one, then flash through EOL phone will check see T-mobile or whatever it is you have pass the check and flash EU rom with unlockable bootloader worked on my N100

@Bolly thanks, but i tried it... and doesn't works. The version 3.1.0 accept to be installed... but shutdown each time. same after reboot.

@garsbenjoe This has been reported. Mouse scrolling has improved in Noble but it's still not perfect. Scrolling speee is normal in webapps/browsers but scrolling only works on the first tab/webbiew you scroll, others won't work. It may also stop working on that tab for some unknown event/trigger.

@gpatel-fr after thinking about it i think i would side with the others .....im talking about the equivalent of including the bootloader in any linux or windows install ....currently you must bring your own bootloader .....very not typical also all source code is verifiable ...i do think your concerns are unjustified ....however they are valid concerns

@Voorstad i plan on three in one actually im developing a custom firmware will feature meshnet but also have compatibility with meshtastic and meshcore protocols as well ...the goal when im done in a brand new esp32 s3 /p4 firmware thats is the most advanced and feature complete ....however im hitting alot of bumps in the road ....and money! ...each prototype modem estimated cost will be around $520 ....once i bang out a prototype i wanna raise money to mass produce sbc's for it hopefully bring the cost down to $100 per modem .......i currently work at burger king ...so this is a financial nightmare moving at a snails pace ..unfortunately ...but yeah will be apps within the firmware

@lolo I would say that the ROM depends on the Redmi Note 9 Pro model. The model is usually printed on the back of the phone under Redmi. This phone has had many variations depending on where it is sold. (Global, Turkey, India, etc.) The global model is M2003J6B2G and need joyeuse_global_images_V12.0.3.0.QJZMIXM_20210419.0000.00_10.0_global_0801ff7d09 You can get info with adb shell getprop | grep incremental adb shell getprop ro.product.name In fastboot mode (Power and Volume down until Xiaomi rabbit) fastboot getvar product Tell us wich model and which phone you have and I'll try to find the right ROM to install before install UT.

@klh said in My Ubuntu Touch devices participated in Thailand nationwide cell broadcast test: @peat_psuwit do you have a spec for the Thai EBS? Looks like they require a working SIM card? I have no idea where to look for that. I tried searching on web for it, but nothing that look like it. The only thing I can go by is Android's config file. I still maintain that we'll need a CB topic database from e.g. Android and should not not rely on hardcoded set of topics from a non-regional specification. In theory we should only need the table from 9.4.1.2.2 of 3GPP TS 23.041. Hmm interesting. That spec does indeed list all topics I've seen on my Android phone. I think I've seen a different spec cited earlier that doesn't include some of them. (For reference, I've seen the following topics: 4370, 4371, 4372, 4384, 4396) Still, it doesn't seem to provide a grouping of topics for settings (or maybe I miss something). And it would also be useful to have a database for notification heading (e.g. in US the title for 4370 should be "Presidential alert", but that obviously won't fly for Thailand). Unfortunately, the test today is inconclusive on whether we need to explicitly subscribe to topic "4370" or not. We don't already? According to the same table, 4370 is not supposed to be settable by the user and always subscribed (I'm kind of extending the 3GPP definition of MMI here) so this shouldn't be a question - since afaik it's not required to be implemented at modem level, we should check what ofono reports and subscribe to the missing ones. It's not supposed to be settable, but this doesn't seem to be enforced by oFono. Currently our settings pane doesn't subscribe to this topic, but apparently Fairphone 5 subscribes to this topic anyway. Still, I reckon that we should be on the safe side and always add 4370 to the list of subscribed topics. Also, currently there's no boot-time component which will subscribe to mandatory topics automatically (and on some region e.g. Thailand this doesn't seem to be limited to 4370 only; see the linked Android config). The settings pane is the only component which sets the topics. This is problematic because oFono don't have a set of initial topics (besides a small number of built-in ones from ETWS).

(SOLVED)i forgoted to flash vbmeta and now config works

@danfro I'm not sure what exactly this would look like, or where this would display. If you have a screenshot it could help!

Hi all, Home(assistant)... Howdo I get my password in this app... I think I miss something becouse there seems only a place for the browser addres and tis is not enough... EJ

https://next.open-store.io/app/indra.projectmoon/ Indra is now available on the OpenStore, with all the fixes in Alpha 4 and a few more tweaks! From this point forward, the database will be treated as something that needs to be migrated instead of wiped on every update. (The setting in the menu to wipe the database does not actually do anything, and will be removed).

@pparent As I like it so far I'm going to do my best. It's quite a challange and I like challenges even if they are hard... EJ

For the record, here are some test feedback from Ratchanan : https://forums.ubports.com/topic/11888/my-ubuntu-touch-devices-participated-in-thailand-nationwide-cell-broadcast-test

@Sentinel Hi All, I'm just now running the install from within the waydroid helper app. Back on the stable OS it shows me that the dowload speed is around 200KB/s, the is about 900MB to download. So yes, a verry slow connection for this app... EJ

@pparent Good point, will do!

@DJac said in changing camera - not recognized: i will try lineageOS If the problem is my point 2 (different hardware working but not 100% compatible) it could work since it may use a different driver version, since as far as I know this OS use native drivers (not Android) to access hardware. If it's another of the 4 possible problems I enumerated, nothing you can do at the software level will change anything.