@Ryan_6930 Yes indeed, there is a long dial before the phone call goes through. For me it takes about 20 seconds and then the call goes through. Data and text work well for me. Text message just work right away. If the phone calls would go through right away, I could use this phone as a daily driver or even a backup phone. I see that the new update (Ubuntu touch 24.04) for the pixel 3A XL is now available, so hopefully promising updates will happen soon for VoLTE. That's really only thing that is needed to use this phone more as a daily driver or even a backup phone.

Excellent! Thanks both of you for testing. As for the keyboard and spacing, I am not a very good programmer, but unfortunately, anchoring the message field to the keyboard did not work properly, perhaps because it was written in QT creator for use on KDE environments, I added lomiri components and the code I saw in other apps for anchoring, but it doesn't follow the standard rules for anchoring to the keyboard like I have seen in other apps (by my trying their code in the Kaidan app). For better or worse, I went with the "wasted space" because I think on smaller screen phones this wasted space is less, and I wanted to make sure that it was not covered by the keyboard when it was displayed. But, I'd happily accept any input if someone could try some other keyboard code that would work. As for landscape mode, you are right, it does scroll the list of contacts, but springs back making it hard to choose contacts that are at the bottom of the list. I'll look at that for sure. For all looking to send messages with pictures or files (audio files are good too), you can send any file if your server/account supports it. For instance, jabber.sdf.org does not support sending files, but ubuntu-jabber.net and conversations.im both do, and the icon to open folder/document doesn't appear in the compose message bar unless you have an account/server that supports it. Ah, yes, the search field is wayyyyy to small! Thanks for some great feedback! I'll take a look at this, perhaps early next week.

Unfortunately last update did not improve the situation.

@projectmoon Thanks, you're completely right. It works now.

@domubpkm said in Merezhyvo browser: Problem displaying accented characters on the Azerti keyboard 'a'. On the other hand, the choices of the different accented characters do not disappear from the display if a choice is not made. will fix it, thanks for letting me know

@kugiigi Wow! T9! As somebody who still often "dials" a phone number, I always just figured those contact names that appeared as I started dialing were predictions based on the phone number.. but pretty bad predictions Finally I understand! That seems like a really useful feature! (also, I think T9 WAS the one where you only had to press each number a single time.) Kugiigi, it seems you did not create the (perhaps handy) bug. I have it in Focal, it's just in a different place - in line with where dialed numbers appear, left hand side. Again, it's the same place Create New Contact button will appear once something is dialed.

@RapidRotator said in Why does UT not have assisted GPS?: I'll look into it then you can begin with this issue You'll note that there is a privacy concern too; if UT devs were ready to trample it, it would be easier.

@erikcht I agree the offerings in this space are dire and it would be nice to see something competitive develop in the open source world. However, there is almost no overlap between Ubuntu TV and UBPorts. Some of the design ideas are the same, but the software stack is completely different from Ubuntu Touch and the codebase of Ubuntu TV is far too dated to use for rebooting the project. The only thing in the UBports portfolio that could be useful is Lomiri, but I suspect that would be overkill: Something simpler (like Ubuntu Frame) is probably enough. The real problem though is that there is too much "lock in" to propitiatory solutions in this market. On the open source side, probably the best project to look at is Kodi.

@Vlad-Nirky Hmm, not sure. Running adb root for me gives error message adb: unable to connect for root: closed, but I can use sudo inside adb shell: using that would probably let me get a step closer, by allowing me to copy data to an SD card for instance. The problem is my computer isn't an adb client so I can't just use my phone as a host and run adb root on it. Going back to the module installation, I should definitely look into that (or whatever procedure I need to enable adb root), as it sounds better than the whole hassle of the SD card (which funnily enough is one of TWRP's limitations). [UPDATE] I've been told by an admin of UT's Telegram group that adb root simply hasn't been added to UT. This shouldn't be a problem, as utilities like rsync and scp, which are meant to work over a network, can be set up to work over for example USB (or maybe even Ethernet, don't know which would be faster or in what scenario). I may test backing up and restoring a Waydroid container with SD card, SSD and PC (using sudo on UT so that I have the priviledges to save all kinds of rights). I've been told by the same admin this works: therefore, all that's left is finding the right command for the job, so that it restores a Waydroid container to a working state (although this procdeure should be applicable to any app or user data or configuration).

This is gone with the new 24.04-1.1 update and voLTE support.

@hummlbach isn't there a way to unminimize like in Ubuntu? Like, surely I don't have to install every man page manually...

@jilly For a while it helped to turn the notifications off and on again for Cinny. Greetings Charly

@wally Yes, I was adjusting the edges in UI tweaks. However as I stated in other thread I never liked swype OS navigation. Expanding the subject, I also don't like touch OS navigation. Touch screens register the touch "without my consent", i.e. when I just grab the phone. That's wrong, but it's been like that since the beginning of all mobile OSes. I'd love to see an option to enable touch-and-confirm input where you touch and have to swype a bit immediately to make the original touch point registered as touch, otherwise it's meaningless

@MarcelloTogg I have two Xiaomi Redmi Note 9 Pro M2003J6B2G (global). I use them in Belgium. Very pleasant phones to use with UT. All is working very well.

said in Enabling MAC randomization: I'll see how it works. 10 days later, I have not seen any problem running with Mac randomization, and I use Wifi every day. On the 'getting the list of stations' subject, I have noticed something new: when I go to Wifi settings and there is nothing displayed (except the access point the phone is connected to, that is), if in a (ssh) console I enter sudo iw dev wlan0 scan the phone screen displays magically the list that was scanned. I don't know what this could mean, maybe the list is cached somewhere and sometimes the cache is stale and not refreshed automatically or it's something else. The cache hypothesis is confirmed just now, I had left displayed a list of wifi stations, left the phone rest for some time, after unlocking it the list has disappeared. There is a wrinckle though: sometimes entering the refresh command, the reply of the command is 'scan aborted!'. This could also be what happens when it does not work. Unfortunately in both cases, the command is displayed in the system journal, but when something goes wrong nothing more is displayed. Sometimes the list vary from one execution to the next a few seconds later, but maybe it's because it's radio after all. Or there is a too short timeout. More investigation is needed (but I'm not giving up, this is only a follow-up). Last thing: the 'scan' command has a [randomise[=<addr>/<mask>] flag, so the randomization can be at 2 levels (scan and normal use) and can not to be done at the scan level, although I don't see why this could have 2 different results on 2 configuration that seem the same. I don't even know why there are 2 levels in the Mac randomization. The only thing I know for sure is that there are some wifi hardware/firmware/driver (?) that do not support Mac randomization (because I have read it in the configuration files for the FP5) so it could be remotely possible that some configuration don't support the randomization at the scan level while supporting it for normal use.

@gpatel-fr Perfect, thank you!

Update to 86 , not strumbled on one bug yet. Just to follow the pace of updates here , simply .

Could anyone that has that kind of issue remember the steps done ? e.g from 20.04 stable to 24.04.x daily, then back to 24.04.1 stable, then.... If there were remote calendars, etc...