@cliffcoggin said in Xompass not working: If you are real old school all you should need is a paper map and a magnetic needle in a glass case. (Which incidentally I still have and use.) Nevertheless I am happy to have GPS mapping and navigation in addition. I carry an analog compass always in backpack (along with other useful stuff). But sometimes when I need really quick to know here north is, it's always hiding buried under other (in this situation unuseful) stuff. During my android times the phone was quicker. Yes, GPS navigation is grat to have. I'm grateful for that. But I also think compass is good to have too, so I'm just trying to raise some awareness, so it is not forgotten.

@arturo2bodegas That is indeed the goal of most of the things in UTTT. It's like a platform for features that are a bit experimental.

@Keneda I do it outside because I want my phone to get line of site radio communication with the satellites. Fun Fact: you can contact astronauts on the ISS with 3 watts of rms power on a handheld when they are over head. :beaming_face_with_smiling_eyes: Also, if you want to talk me with audio, I have been known to monitor 27.32500 megahertz on double side band amplitude modulation from time to time. I may or may not be able to get out with 500 watts. Heck of a time when the sunspots are in line. Sorry, its Friday and I'm on a rabbit trail.

So it's really a hardware issue : https://wiki.pine64.org/index.php?title=PinePhone_v1.2#Backlight Backlight LED current regulation depends on gpio0-ldo voltage stability due to feedback voltage from current sensing resistor being modified via SoC's PWM pin and pullup resistor to gpio0-ldo. gpio0-ldo also powers the CTP controller and light/proximity sensor, among other things. When backlight brightness is very low and the CTP controller actively communicates on the I2C bus the backlight blinks heavily.

@cliffcoggin said in Home setting in PureMaps: Done. What an odd menu arrangement. Thanks. I think that's just how the plugin works and not up for customization.

@AppLee said in Manually choose "LTE only", "WCDMA only", "LTE and WCDMA", etc.: @Keneda Fair point but imagining how you can use some feature doesn't make it useful for most. Most may not imagine that kind of solutions for battery life issue, but lot complain about battery life issue ^^ Many setting in the drop down menu are useless for me and make it less easy for me to get the useful stuff. That probably makes the two of us I don't think that how most people want to use their phone: always manually switching network. Most people are carrying charger with them (i see them at work plugged everywhere), i prefer switching and plugging at home. And maybe people would much more do that if it was in dropdown menu, who knows. And not sure it is even usefull because searching for antenas nearby is power hundry... Test needed As i told on another topic, 48hrs mini in iddle in 3G, 24hrs maxi in iddle in 4G, approx, with my MX4, switching network never killed my battery. Oh and in your case you can keep the settings page open: easy fast access I wanna go home Don't misunderstand, i just said that would be great to have choice in dropdown quick menu, it's been five years i launch setting to do it, never killed me.

I can't help, but I encourage you to keep digging. There is a running history of vague issues with mms on UT with no resolutions. There is probably something wrong that is not obvious, so you might be on to something.

@cliffcoggin said in Space bar/key in search: the rubber edged case I bought prevents swiping from any edge. Damn. I'll have to get something else. I think, un UTTT, you can adjust the swipe area. Maybe it helps.

@yeke_yoke Thanks for the flowers. We are all in the same boat, and the boat is not so huge, so yes, now and then it will happen that we engage like this

Thank you!

Indeed please do not confuse things: The stable Nexus 5 on Legacy 5.1 porting is super-stable. This thread you mentioned is about an alpha stage build for upgrading to an Android 7.1 base. Its fairly unstable but will become better and better over time. However for daily use only use the installer-provided stable image.

is there a bug tracker I could follow to see when this bug is fixed. I really don't want to fork out for a Bluetooth keyboard for one sign in. Sorry new to Ubports not familier with everything yet

@AppLee Nice. thx

@Lakotaubp well done to you for the work you put in on the forum - I've read a lot of installation problem posts over the past few days where you are helping out. I've installed Ubports on a family member's phone and they have been using it successfully as a daily driver for the last couple of years, and have contributed to the foundation, so it's great to see the project go from strength to strength with the pinephone and everything else.

Hi @CAnoop, The only thing I think about regarding your question is that one of your folder has not been properly converted in ext4 Make sure you try them 1 by 1 using "Repair" or "Change" functions If you have an error message saying you can't convert, then try using other functions of TWRP, you should be able to convert them all 3. Also, According to what I read in this forum, the "Android actions-> Full Factory Reset -> Wipe data" action is not always necessary. Good luck !

@Abuabdellah I found that : Alternatively there is the old Ubuntu SDK IDE. Be aware that it is no longer supported by Canonical, and UBports has chosen to not support it either due to lack of manpower. also mentioned on telegram by @dobey [image: 1591554216323-74097283-fe4f-45f7-9179-7bac1e3cbd59-image.png]

@domubpkm Thanks for posting that - it seems a few of us are having trouble with the installer and having a manual install option is valuable. I ran the command in fastboot mode and got the following message: Get https//system-image.ubports.com/channels.json: unsupported protocol scheme "" Could you point me in the right direction?

The issue seems fixed now.