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.
1 Like
I’m not sure if we need a bug report
1 Like
@marvin24: Yes, I think a bug report would be a good idea to make this problem known to fp devs. How can we file a bug report?
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.
1 Like
Isn’t that the exact same problem as discussed here:
1 Like
I was told that there will be a fix for that. Unfortunately, I don’t know when that will be.
Hi I’m trying to install the OS but get stuck at this point:
‘enabling USB debugging in the developer settings on your device’
Where can I find these?
Go to settings > about your phone.
Tap the build number 10 times.
Now you’ll have the developer options in your settings app.
2 Likes
Wow, for real? How does one figure out this stuff?
Thanks!
1 Like
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.
I’m trying to fastboot with the terminal, but it doesn’t seem to see my phone when I check it with the ./adb devices command
I get: List of devices attached
then nothing…
Before:
Ive set my phone to developer mode
Turned on USB debugging
Installed Android Studio
Put it in recovery mode
connected it to my computer
changed the directory to the platform-tools folder
what am I missing?
Same problem for me, after installing ADB and Fastboot on Ubuntu 16.04, enabling USB debugging, my FP2 is not found …
Any idea why and what should be done ?
Did you make sure that all connecting options on the phone (like MTP, charging mode etc.) are unchecked?
Are you in fastboot mode already? then
adb devices
will not work, but you need to check connection with
fastboot devices
2 Likes
Unfortunately I never got it to work and I installed the normal Fairphone OS again, the Open OS was not for me!
1 Like
I had similar problems. My phone showed up in ADB, but fastboot did not recognize it. The solution was sudo:
sudo fastboot…
…and it worked.
2 Likes
This tutorial starts with the word “installing” and not “updating”, so it’s no wonder that you got a clean install. Try a search with the words “update” and “twrp” next time you want to update.
Right, I have unchecked MTP and now my FP2 is found by my computer. I just have to connect my FP2 with USB cable, and not in the Fastboot mode, and I use the “adb devices” command.
Unfortunately, “fastboot device” (without S) indicates < waiting for devices >, in normal and fastboot mode.
I’d like to know if my FP2 will be exactly the same after the installation, or if something will change from the original installation ?
So I re confirm (just tried it) that the FP2 shall be in Fastboot mode and the right command is “sudo fastboot devices” with the “s” at the end of “devices”, this way fastboot gives the FP2 reference.
(“Fastboot device” (or devices) command only gives a message and get stuck.)
So I’ve launched the installation from Ubuntu 16.04 with no root privilege.
1 Like
Just a remark concerning installing FP Open OS: you will need the installation by fastboot if you have a newer FP2, as apparently the build of the directly downloadable OTA package is older and cannot be installed over a newer build (Method 1). While with fastboot (Method 2) all went fine.
2 Likes