I also have a vollaphone 22 on Noble 24.04-1.0, but to me it is quite unclear if voLTE is supposed to be activated or not, because in the it just says "4G calls (VoLTE)" but without any switch and the area is not clickable, so I don't know if it is supposed to mean that it's on or off? And I have no real way to test it for sure, weather my calls are voLTE or normal. The only thing is that few month ago I received messages from my operator to encourage me to activate voLTE, but this was before latest Ubuntu Touch upgrades. I would like to know more.

@zakafx said in Input lag? Keyboard issues.: @kugiigi the word suggestions are great when available, but for some simple words like "with", "liek", just simple misspelled words, the corrected versions (or any word) are not offered for selection. I will wait a while and check back to see if anything has improved, for now I am on Lineage. I don't want to be pessimistic, but i think no one had worked on the predicitve engine since the beginning of Ubports. It requires both skills in linguistic and programming. But who knows, if a volunteer take the lead on this topic one day.

Hi @k.nacke . Just tested waydroid and it does not seem to work. I am using the latest build on GitLab. Running waydoid log complains something about not finding device sensors. Waydroid is just stuck at the LineageOS Boot Screen. I left it for approx. 4 hours to boot but it did not work. Can someone please help me?

Finally found the issue, for some reason the tls key was wrong (dont even ask, have no idea how that happened)........ @Luksus Didnt rebbot after turning volte off but doesnt seem to effect the vpn. /edit Well ping doesnt go through the tunnel but normal web traffic does, openvpn could really have a bit more clearer error messages. Like "Invalid tls key" or something instead of and obtuse " Insufficient key material or header text not found in file '[[INLINE]]' ".....

@TheTrench You need to delve deeper into 5G and what 5G is, plus what Android version supports 5G on that device. 5G falls into two categories - 5G Non Stand Alone (NSA) and 5G (SA). 5G NSA piggybacks of the 4G LTE infrastructure end to end in simple terms. 5G SA is full 5G end to end. This can be affected by available networks, service providers, Android versions and vendor BLOBs and device hardware. You cannot expect newer firmware files to work on an older version of Android without issues or just not working. I bought a 5G device when 5G was in its infancy and always got 4G LTE indicated and 4G speeds. 5G has a better infrastructure now and it still shows 4G LTE in a lot of cases. My new device is 5G and always shows 5G and is a bit quicker, but not in all cases.

but sharing about overall experience, I'm really happy with FP5. It works flawlessly with my 4k monitor and docking station. I can just plug it and use from mouse/keyboard/monitor. That's just awesome. FP4 was probably working similarly with FHD but I don't have any low resolution screen anymore, so I never tested it (I just can confirm that it couldn't drive 4k resolution). I just hope FP7 will have fully fictional USB-C again (as FP6 allows only charging, no docking capabilities!!!)

@Linuxlite76 In my experience this issue is device dependant, port dependant and different in rc, stable and daily channel sometimes, so its a liitle guess and hit

@gpatel-fr yep you were right, going down to the specific projects helped. Thanks once again

@bestenaizena No problem. Helping one another is what this forum is all about.

@RJDan Oh okay. I guess you're on Noble and only the Essentials version is available for now The full version is available from the repo but it will be released in Ambot soon

I've been having some issues using Libertine running apps and searched the forum. It seems some others are also having issues setting up a proper Libertine container on the Google Pixel 3a. I'm placing a link to here. https://forums.ubports.com/topic/11232/unable-to-create-libertine-container

from what im reading its asking me to build package sources like indicator-network and i think that is needed because i ran lomiri once i got the setup no apps worked and when i restarted it failed to run so what do i need to b

@fake-alex So what's the plan... are you offering to send these devices to people who want to try to make a port for them? Developers need to have the device in hands.

@sixwheeledbeast To use UT, you must never relock the bootloader

@Carlos said in Call for testing: Ubuntu Touch 24.04-1.1: This weekend I updated my Vollaphone22 from 24.04-1.0 to 24.04-1.1 and screen starts blinking on boot before the logo Ubuntu appears. With installer reinstalled 24.04-1.1 without wiping data and everything I use every day starts working normally until I found a serious bug on calls. Yesterday a friend calls me, I answered the call but no sound from other side. My friend repeated calling me and all answering was no sound. With other phone at hand I search the source of the error and found the Vollaphone22 was the culprit. How to reproduce is like this, make a call to other phone, wait that the other side answer the call, talk to test that audio is ok, wait that the other phone hang the call, now if you repeat process there is no sound if answered the call. Only rebooting Vollaphone works again, untill other phone terminates the call first and error returns. This error does not happens on version 20.04 stable. Thank you for the report. We're looking into this issue and will delay Ubuntu Touch 24.04-1.1 until we have this issue figure out. @mjosenhans said in Call for testing: Ubuntu Touch 24.04-1.1: I yesterday installed on my volla phone 22 Ubport 24.04-1.1 RC1 via RC channel. I had problems with incoming and outgoing voice calls without any voice being heard in both directions. Thus I reinstalled 24.04-1.x stable via stable channel. However instead of running the again the 24.04.1 software from stable, the phone is now in a reset loop. It shows the volla screen, then a black screen via backlight on, then a black screen with backling off and then again the volla screen. And so on. When going into boot loader, I was able to start the recovery mode, however it did not change, it is still in boot loop. Ubports installer is not finding the phone too. What can I do? I plan tomorrow to go to the phone service shop in berlin, which provides volla service and try to reflash the phone. We're sorry that this happen. Please try the following: Boot to bootloader by pressing Volume Up + Power (or Volume Up + plugging cable), then select "Enter fastboot menu". Do not enter recovery. Starts UBports Installer, then manually select "Volla Phone 22" (the Installer currently cannot auto-detect device model in bootloader mode). Select "24.04-1.x Stable" channel and ensure "Bootstrap" option is checked. Leave "Wipe Userdata" unchecked. Follow further instructions from the Installer.

Even better news: The wipe won't be needed. Existing v1 policies continue working and should even be compatible with Waydroid once they're stored in the filesystem keyring. Even if they're not, that's not a blocker for v2 to land early, as existing users can enjoy their devices with the same feature set as before. I'll go ahead and merge this.

@FixOne Very cool.