Yes, I saw that post too. However, by using the Fairphone OSOS we directly flash the image to our phone without compiling anything. So there is nothing we can resign. So it’s up to the fairphone devs to sign the apps with the correct certificate.
I think one can use https://fairphone.zendesk.com/hc/en-us/requests/new . It seems to me that there are several problems related to the locating service and I’m not sure how they are related. So I don’t feel qualified to submit a bug report myself. Someone with a deeper understand should do it (if he hasn’t done yet).
The “official way” to report bugs is to create a topic (e.g. in …help) with a detailed description of the issue and if possible a fool-proof way to reproduce it, and if us moderators decide it’s really a bug we move the topic to #software:bug-reports and add the issue to the #bugslist::tag.
TBH I don’t really understand what you talk about so I’ll probably have to rely on others to decide whether it’s a bug in this case.
Can I use this tutorial to update my current Fairphone Open OS 16.04 to Fairphone Open OS 16.05? Or will this completely remove all of my apps and bring me back to a clean install of Fairphone Open OS 16.05?
I tried it. The answer is NO. If you follow this tutorial, you get a clean install.
The reason I tried this tutorial instead of the ‘updater’ is that the ‘updater’ doesn’t work in my case. It boots into TWRM and than does nothing.