@Keneda Yes, thank you! That fixed it. Even after all this elapsed time.

So for those playing at home:
-1 + 1 = 1
-1 + -1 = 0
Simple. ; )

@RayCulp Short answer, there is not a repo for the main website, but there is acknowledgement it needs to be easier for community contribitions. The Github Issues page is the best place to log issues with the website, though it seems to be checked infrequently.

My suspicion is that wiki.ubports is dead, and is replaced by docs.ubports.com, though there is still the occasional dead link.

https://docs.ubports.com/en/latest/contribute/bugreporting.html is not quite a perfect replacement, but contains some guidelines about halfway down the page.

@MrT10001 You forgot to say, "You might as well stop using UT and install Android." Keep in mind that not everyone who locks their house when they leave, sets a pincode/passphrase on their device, or adds UBlockOrigin to Firefox is wearing a tinfoil hat. Most people freely give away the digital footprints of their physical life, but it doesn't mean we all should give up and join in.

@WQ6Z8X4U Thanks for keeping us in the loop! I totally appreciate your efforts here. This definitely captured my attention. I am itching to get my hands dirty with systemd timers myself... but also short on time.

@MrT10001 said in Bacon goes focal!:

r61 installs fine - ensure you clear the downloads queue or it will reboot to recovery and not install (tested a few times).

Thank you for that tip! I was stuck on R56. Had this issue trying to jump to R60, and just now R62. All good now.

Noticed an issue with Morph on R56 and 62. The first window I open won't load a page - progress bar gets stuck at ~10% - but additional windows/tabs work fine.

@TheVancedGamer But. If I am on R98, and then update to R99, which only includes changes to say, the camera, how do I know to focus my attention on testing the camera and not waste time trying to test the SIM, and spamming the thread about how the SIM doesn't work? I don't see any sense in continually testing features that won't have had any changes, and I am sure the community doesn't need to keep hearing about them.

@MrT10001 I don't disagree, it may be impossible to live in modern society without being seen by Fourteen Eyes. It doesn't mean we can't or shouldn't try to keep ourselves under the radar of individuals and other organisations who have something to gain from people who are lax with their privacy.

Reply with your full name, residential address and credit card details, you will see what I mean. (There's no point trying to hide these details from anyone, your bank already has them.)

@MrT10001 You forgot to say, "You might as well stop using UT and install Android." Keep in mind that not everyone who locks their house when they leave, sets a pincode/passphrase on their device, or adds UBlockOrigin to Firefox is wearing a tinfoil hat. Most people freely give away the digital footprints of their physical life, but it doesn't mean we all should give up and join in.

@arubislander That is a lot closer, but unfortunately I have ended up lost in a maze of repositories at GitLab several times, and given up. I imagine there would be page somewhere, even if it was manually maintained, linking a Release number with all the Merge Requests that went into it.

@Dunbrokin said in Bacon goes focal!:

@prophanetes I think a standard list of things to test (probably for each device) would be quite useful.

I wish I had've found this sooner myself, but https://docs.ubports.com/en/latest/contribute/quality-assurance.html contains a link to a spreadsheet which explains how to test each feature. (I can't tell when it was last updated/reviewed. The way everything is laid out into a grid for recording test results almost looks like it was meant to be submitted somewhere once complete... but the instructions are to head to the issue tracker on GitHub.)

@arubislander Dude. If I am offered a 130MB update, more is changing on my device than just a version number. I am quite clear that not all of it is the work of the porter for my particular device. If you do not know where the information exists about what is changing between releases, please don't feel the need to quote responses that don't answer the question.

@arubislander Understood, but still doesn't tell me where to find what are the differences between releases.

@TheVancedGamer Aha. Cool, thanks. Makes sense, but wasn't obvious.

So, what changed today when I updated from R62 to R78? What goes into a release is surely documented somewhere? Where do I find that?

@arubislander All fair points.

But from my experience switching from Xenial to Focal, adding hardware support to a ROM is slow and difficult. Removing or disabling hardware support at that level should be very easy. With all the hardware options, it would be messy to provide ROMs with every possible combination, but it should be relatively easy to ship a ROM with minimalist features by design. If I we offered a no-GPS version, I'm sure it would be popular.

Testing the feature is actually disabled would not to be too difficult for the user. Open Source apps which are designed to use that hardware, e.g. GPS, will honestly report it is not working, and it could be verified by testing multiple apps by different authors. They can't ALL be in collusion with the device porter to deceive users about telemetry...

@arubislander said in doubts more than problems:

If you are so concerned about these things, it would be a good idea to learn to read source code, so you can audit the code of the apps running on your device to your own satisfaction.

In general I thought your response was great, but I find this part a little dismissive. I wholly agree it is a "nice idea" to be able to inspect source code, but it is far easier said than done. It takes years to become semi-proficient in a single language, and I don't know anyone who learnt a programming language by reading it alone, and not actually writing with it. It would be far simpler to just know the hardware was disabled, than expect the user (any user) to read and understand the code of every single application that could possibly want to use that hardware, in any language it may be written in.

@TheVancedGamer But. If I am on R98, and then update to R99, which only includes changes to say, the camera, how do I know to focus my attention on testing the camera and not waste time trying to test the SIM, and spamming the thread about how the SIM doesn't work? I don't see any sense in continually testing features that won't have had any changes, and I am sure the community doesn't need to keep hearing about them.

Feels like this should be obvious, so apologies if I missed it. But I will try to take comfort that if I am unaware of something "everybody knows", then it's possible I am not the only one.

It is not a good use of time to test and report 'feature X still does not work' with each update, if no work has been done on feature X.

Where do we look up which features we should be testing with each release? (And could this information, or a link to it, be added to the opening post of each future 'open for testing' thread?)