@gpatel-fr You are correct. "How to enable developer mode" states enable USB debugging (<- me bad - didn't see correctly), ADB, or Android D... Bridge". Sheng-Cheih P.s. i'll try again after shower nap - so sleepy now.

@gpatel-fr I can't see the difficulty. Instructions for clickable installation are the same for 8.7 version: https://clickable-ut.dev/en/latest/install.html (just use pipx command instead of pip3, as proposed also in the book)

@Moem yeah ... that is why I replied to MarcelloTogg - to see if cups WORKED for them, or they WANTED cups to work for them.

@Vlad-Nirky Yeah, there is only daily at the moment. I have researched this issue and albeit not common, it is there and something to be aware of.

@kugiigi Hello So I dont have another phone with display out so I cant test that unfortunately. I do agree that the hub seems to be what determines what issues I have. I dont have major issues using any hubs with my asus laptop to charge and display out and the laptop draws more power than the phone. What hub do you use?

You can't install a phone that hasn't been ported. Porting means creating the unique installation files that a specific device needs. The Pixel 4a has not been ported, so there is nothing you can install, as far as Ubuntu Touch goes. If you might be interested in porting it, please see https://docs.ubports.com/en/latest/porting

@oldbutndy said: @Leroy_Linux Running 24.04.1n (daily - but randomly doing the updates), MVNO USMobile > T-Mobile Good to know. I'm running 24.04-1.2 stable and T-Mobile. I misread your post. Somehow I interpreted the phone wasn't working well, but you clearly stated that it's just not a daily driver unless WiFi calling or native VOIP. (neither of which I've used... my requirements are just for the working phone which it has done well thus far). Thanks and sorry for my confusion. Hope you find a way to meet your requirements!

@lduboeuf First there was the alert-message (I don't know which message-id was used right now) and after 30 minutes there was there clear-message for this alert which says, that the alert is over. I only received the second message (clear) but not the first one (alert). Is there an option to get the subscribed message-ids? The above mentioned test-cbs-script doesn't work for me.

@ma Thank you, I will try that!

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.

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

@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

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.

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.