Same here with E4.5 paired with infotainment of Seat Leon 2019.

@AppLee Personal reasons are exactly why it was written 🙂

@mirroronthewall open apps should not access data in background.
But dekko has a background running daemon and some other apps can use this kind of workaround like axolotl...
But as intended by UT, an app in background shouldn't use any data or CPU.

@normandc said in Simple UI documentation, need some help.:

I get the feeling that what documention there is was written by developers, not end users.

Pretty much. Yes. 🙂

I have experience writing documentation for open source projects, but as mentioned by @poVoq, a big change is due in the next big update (OTA-12), and to be honest I'm kind of taking a break after years of involvement in another (unrelated) project.

If you change your mind - we could really do with a nice and simple documentation for regular, every day usage.

Of course the design goal for the OS is to be so intuitive that everybody gets it without reading a handbook. But I think it would still be nice to have it all summarized concisely in one place. Not all the swipes are as obvious as they should be. And also, having this documentation of the obvious, would provide an indication that everything else is not (easily) possible

@ziggutas Just done that ignore the adb error message if you get it and if yours like mine is wifi you will need to pick ut yourself. Installer keeps picking LTE.
Now for the waking up bit. Mine has stopped the wake up thing. It might be down to it being on the original edge channel not sure. Moved back to dev with the edge merge. Now I had forgotten the wake up thing as mine doesn't as I said. Had it up and running now for half an hour on power and still no odd wake ups. Its currently on 2019-12-23.

Edit: When not on mains power I still get the occasional wake up. When on mains nothing. Might be worth someone else trying.

@Fla no the Android layer is not the reason, this is very little RAM usage. The problem is that unity8 was never optimized for low-memory devices without swap: It comes from a desktop world, and with it a lot of services that just like to spend RAM.

Unfortunately the core team has no resources to tackle those issues with unity8 right now, and the Yunit project, which wanted to fork and maintain unity8, has silently died away. So currently we can only be patient with that situation.

I solved this. Seems it doesn't work if it's in the Documents directory. It did work when I moved it to the Downloads directory.

@MarkG_108 Any app is useless, if you don't need it. Just because something is useless to you, doesn't mean it's useless to everyone. The "Hello World" thing is probably an example app. There are several example apps in the store. This is no different on other app stores, so there's no need to denigrate our store with such unkind words, simply because there aren't millions of apps covering up the few you don't care about.

So Release Candidate is halfway between Dev and Stable, I assume. I will stay on Dev for the moment. If I get frustrated, I'll try RC.

@lool_lauris I downloaded hh_clamor_repartition.zip and inspected its shell scripts. They are very simple if you are familiar with Linux system administration. Just usage of "dd", "parted" and "make_ext4fs" utils. Looking at current partitioning I figured out that my Nexus was affected by hh_repartition_32GB.sh script and to rollback the changes I just need to run the hh_stock_32GB.sh and that is it.
Also before that for safety I did backup of crypto and grow partitions to my laptop because those scripts do that too.

@Emphrath You could add solved to the title if you feel like it. Just click the three little dots to the right.

@poVoq I agree with you AGPS is here to improve the Time To First Fix (TTFF) but it has no influence on the positioning accuracy.
We would just need to find out what output of the Nexus 5 GNSS receiver is used in UT; most of the time a receiver offers different types of outputs, more or less accurate: GPS alone, GPS coupled with GLONASS (seems like the Nexus 5 GNSS receiver uses both constellations), GPS coupled with SBAS (WAAS over the US, EGNOS over Europe, etc.).
Maybe we should get in touch with the developers of UT regarding this specific issue in order to find a way to improve the positioning accuracy. How can we reach them on that subject?

Thanks AppLee 🙂

UT is pretty awesome. Really appreciate UBPorts taking over what Canonical started.
I've found a lot of annoying quirks in it too, since I compare everything to Android, which of course isn't fair. Some can be worked around - but then some is just to annoying. Hence my 'post of frustration'. I'm trying to get an overview github (did a post there some days ago regarding another issue, not getting any feedback - maybe posted wrongly, I don't know). It's a bit confusing navigating github/gitlabs - but ... baby steps.

Happy holidays to you too 🙂

I'm not sure. to test, I just saved a random webpage html with the folder, it does work on desktop browsers

Wow, that was quick - many thanks to you @Lakotaubp and @makeixo! Indeed, wiping the caches using twrp as suggested in the linked topic helped: The recovery did not reboot anymore and I was able to complete the installation of UBports.

Unfortunately, I got a black screen afterwards. So I did the following:

Not sure which of these did the trick, but now UBports boots up just fine.👍

Thanks for fast replay .