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

I can give you some feedback if you'd like. On a dual-screen setup, a physical mouse isn't recognized, or is poorly recognized, for vertical scrolling, which makes using Morph nearly impossible, especially since the manual scroll bar on the right side of the page is too small to be truly usable. strength to you

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

@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer): AuthorizePush this is denied; I never dabbled much with Apparmor, and certainly not with UT; I notice with some dismay that there are no apparmor logs and I have no clear idea on the better way to enable them unfortunately. For now, I have only one positive thing to say: in the application that worked with 16.04, the template was set to 'unconfined'; while this is not generally a great idea, to advance your testing maybe it could be worth a try to add it to the apparmor profile ?

Is it my bad math, or should +131 -1 = +130, not +129 in the very first paragraph?

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

@Voorstad just so you know, if you have not seen it already, Indra is on the OpenStore. And no, it does not do MeshCore, at least not yet. I have a vague plan of adding at some point this year. I found a Rust MeshCore library.

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!

@pparent good point. I wonder how that is arranged.

I can see them in the old store. https://open-store.io/app/pure-maps.jonnius/versions I cannot see them in the new store. https://next.open-store.io/app/pure-maps.jonnius/versions/ It looks like an error in the new store.

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

I think he's saying he wants to forward SMS from his primary phone to his UT phone - Which I know you can do with VoIP providers, but don't know any cell carriers that will do that, with the exception of T-Mobile. They used to have a feature for that. Don't know if they do now.

@kugiigi NDK is basically a set of C APIs Android exposes to applications, allowing apps written in native code to get access to certain functionalities without calling Java APIs through JNI (Java Native Interface). The good news is that these APIs should largely be usable on Halium-based UT devices as well. So the advantage is that we don't have to rely on bespoke APIs libhybris exposes, which allows us to share more code with upstream which already supports Android (in this case GStreamer). This is not relevant to mainline devices.

@MrT10001 I don't quite remember what the installer did when I flashed my phone (happy memories... not ) but from browsing v2/checkDownloads.ts I'd say that the installer is saving stuff in a sub-directory called 'download' from the current directory when it was launched.