By safety measure I will make a release based on V8.2.0 tomorow Edit: It seems Signal-Desktop was safe from 7.74.x so the latest version of the app seems safe in regards to these bugs.

Just as @applee, I suspect that this thread possibly discusses several different bugs. Notably, I believe the problem described in reply #3, and maybe by @kristatos are the same as the one I described in this other topic. The issue in that other topic is related to how UBports interfaces with the android gps drivers and it affects all apps using gps on all ported android phones released since around 2020, but possibly with app-dependent symptoms : freezing, crashing, or just going on with a frozen location. The good news is that the other topic's bug has a working fix which should hopefully land in an upcoming OTA.

@ma said: The private DNS must be disabled, and the network connection needs to be restarted. Doesn't work for me.

@gpatel-fr ahaha I am running a dualboot setup as of right now mostly cuz I need it for college work, though I don't switch back to it that often cuz usually Waydroid does the job just fine. I don't mind using the web app via morph but my current setup is quite snappy so I don't think that should be an issue!

@slowcyclist Interesting find, thanks for the effort. @slowcyclist said: never use their gps for extended periods Yes that's the case for me, although these last days I just tried that, and I got effectively 2 occurences of GPS not updating any more (launched Puremaps and Gps app together to make it more interesting). For me the reason is that the FP5 is gulping energy at such a rate that I try to stop services when not actually in use. The only difference is that the GPS service (lomiri-location-service) never stopped for me (according to systemctl status) so no crash with unaligned errors, although I got the second time (did not think to check for that first time) segfaults and several restarts of sensorfwd service, maybe caused by this problem.

@Leroy_Linux yep, it was.

@jagdtigger I had the same problem twice. After multiple restarts of bluetooth and the phone itself, my headphones were detected again. A couple of days later it happened again and after multiple restarts it worked again. Now I did not have any problems for at least a week

@projectmoon said: contact form The problem with this is that there is no automatic acknowledgment, so one cannot be sure that the message has been received or will be acknowledged.

@pparent Much appreciated! I think these will be super useful.

@MrT10001 Thanks for your reply. I actually had UT running on another x306f which unfortunately slipped out of my hand and fell from the balcony of a hotel room on the 4th floor (true story ). Rúben doesn't mention EDL on https://gitlab.com/ubports/porting/community-ports/android11/lenovo-tab-m10-hd/lenovo-m10-hd/-/blob/main/README.md?ref_type=heads

Thank you ! for all the apps

A list of whats working on noble rc 24.04-1.2: Manual brightness working Torchlight working Vibration working Flashlight working Photo working Video working Switching between cameras dont know how Carrier info, signal strength working Data connection working Dual SIM functionality dont know Incoming, outgoing calls working LTE calling (VoLTE) working sometimes sometimes not as far as I can say MMS in, out dont know PIN unlock working SMS in, out working Change audio routings dont know Voice in calls what does that mean? I can hear the other person and the orther person does hear me: yes Volume control in calls working 24+ hours battery lifetime depends of use 7+ days stability no way, have to restart twice a week at least to get lost features back like i.e. proper change between wifi and mobile data Boot into UI working Hardware video playback working AppArmor patches working Battery percentage working Offline charging working Online charging working Recovery image I am pretty shure its there Reset to factory defaults did not try yet RTC time working Shutdown / Reboot working Wireless External monitor dont know Waydroid dont know Bluetooth working in sense of using another loudspeaker, not in sense of transferring data Flight mode working Hotspot working NFC dont know WiFi working Automatic brightness working Fingerprint reader not working GPS working Proximity working Rotation working Touchscreen working Double touch to wake working Earphones working Loudspeaker working Microphone working Volume control working MTP access working ADB access working

@bunchy7s Note that the Oneplus 3 port isn't even listed on the main devices page. The page @moem dug up says that the last work on it was in 2021 and is for UT 16.04, which is quite out of date. And the video you followed is four years old. I can't say that your issues are definitely caused by how out of date it is, but I can say that you're unlikely to have a good experience of Ubuntu Touch on that device. Unless you want to take up the reins and bring the Oneplus 3 port up to date, I'd say your best bet to try UT is to read around on the forum and device pages and try to find a supported device that suits your needs and is affordable and available in your area. Also of note: some people have difficulty with putting a phone back to android, so do your homework on that before attempting.. people have bricked their devices.

Ah- and Sidenote on "bricking"/restoring device: Lenovo offers an good "Software fix" software on their webiste that can restore your Lenovo device. You can install that, connect the tab via USB, give it the serial of your device, and it downloads the latest firmware and resets everything..the only thing tricky- as usual- I believe you might need fastboot mode at some point- which is POWER + VOLUME DOWN buttons at the same (USB disconnected) and then the lenovo enters fastboot mode and is ready a) to get out of this endless loops and b) receive the firmware. For me, it restored Android 11, the right one for UBports.

I apologies- got it working! I had two important obstacles, one related to the UBport: 1.Win10 somehow has a problem with talking to tablets and seems to require an extra driver, "MTK Driver"- I haven't verified this myself, but switched to Linux mint, where adb worked nicely and found the devices always. Anyway odd is that adb showed the device before I started Ubports, but later lost the connection somehow. 2.The TB-X306F could not get unlocked as described in the docu with "fastboot flashing unlock" but "Fastboot flashing unlock_critical". It seems, that command has changed somehow- my latest firmware before Ubports came was from 2024. No one talked about this parameter in the forums, but I found finally, that it seems to be an old syntax- may be Lenovo reused an old firmware, so that this came back. This changed command should be noted in the related documentation, not a problem of Ubport itself- it's just difficult to find, as there's no clear feedback that the unlocking failed partially, and Ubport itself only realizes it late in the process. I have now Ubuntu 20.04 on it. Impressed, that I got it working, but it was not trivial.

I forgot generic carddav and cups support.

The Indicator Upower now supports battery charging limit on MTK and other devices - don't forget to reinstall indicator if this feature didn't work in older releases.

The opposite works as well. You can use your phone as remote mic using ssh pactl load-module module-pipe-source source_name=virtualmic file=/tmp/virtualmic format=s16le rate=44100 channels=1 ssh phablet@'phone-ip' [-i identity_file] "arecord -f S16_LE -r 44100" |cat > /tmp/virtualmic

okay. great. I update. previous version, less stable on 24.04-2.x. better on 24.04-1.2

@chaosmaou T-Mobile works well for me. I tried Ting first, but had issues. I didn't bother to troubleshoot knowing from others that T-Mobile worked. So, I just switched and happy with the results. Good luck!