Thanks. Creating another Google account to run Raccoon worked on one computer. But when I tried to use it with Raccoon on a different PC I have the same isssue again.
Titanium Backup is available from apkmirror.com or from the developers site.
This is the direct link for the latest version: http://matrixrewriter.com/android/files/TitaniumBackup_latest.apk
No idea! Sorry. You could describe your error in xda-forum. There is a thread about it:
I don’t know if I have the same errors in code but my WiFi gets disconnected from time to time even when the signal is strong like 60-80%. There is the exclamation mark issue again as in FP OS 1.7. Not sure if it’s the same issue like yours…
I think that’s the same issue. But as I’m using tasker to switch wlan off if disconnected from my home network (on the assumption I’m leaving home…) I don’t have the exclamation mark
I am using a similar application called “Smarter Wi-Fi Manager” which saves the approximate location of my WiFi via UMTS location. But when I am home it gets the exclation mark.
I’ve lost track. After the 1.3.6 update, which source code branch of FP2 Open OS is now available at http://code.fairphone.com/?
1 Like
I don’t know about the sources but there is a new release since today:
FP2 Open 16.05.0 includes all the fixes found in Fairphone OS 1.3.6. Further, we added a Setup Wizard to fix the time issue on first boot and it is now possible to use the unified location provider.
There are no download links on code.fairphone.com yet, but the Updater offered 16.05 to me and the update went well 
5 Likes
True. The last time I checked, the code (= all the different gits you pull with repo) on code.fairphone was not matching the code/fixes included in the released binaries. But I’m too lazy to check any longer. If a howto gets posted on how to checkout the code that matches a release, good. If not, I just have to way. Not a big problem for me right now.
hello,
I have the same problem as you… Would you like to explain to me what is your solution because I dont understand “I long hold/click the zipped folder” because it seems impossible to find Updater and to open the applications…
Thanks
Nano920
Hi
I tried to install the OS os (dated 16.06) using the OTA method but it failed, apparently because I have a more recent update of the “regular” OS on my FP2…
Is there a solution?
Thanks
Vero
I think this issue will probably solving itself automatically when the new version of OpenOS (16.08) is released.
2 Likes
Have a look at this:
1 Like
Thanks for your replies @freibadschwimmer and @Stanzi 
I had a look at this discussion…
The latest OS version (1.5.1) arrived late June, so I guess the corresponding OSos (16.07) will come very soon now…
Happy Sunday, fairphoners!
Vero
Actually 16.07 is being skipped and 16.08 will come soon:
Just publishing the code would help, so people would know what is going on. That’s the main idea … of publishing the code in the first place. It is doesn’t compile, people can help fixing it, talking about it. There’s not a lot of sense in publishing the code once the rom is released.
Maybe there is such a repo somewhere, but nobody ever explained the whole process. Too busy, I assume.
1 Like
!
I was already wondering why there is no repo similar to what you find on GitHub, where people can see the commits and where you have a dedicated issue tracker to manage bugs. Some may even try to compile the code, test and report bugs. The other thing I am missing is betas: Try it, test it and give valuable feedback.
If more people get involved with testing more bugs will probably get discovered and fixed.
I do not know if my assumption is true, but just food for thought: I wonder actually if that nasty “clock reset on reboot” bug just slipped through because most of the development happens in urban locations with strong signals, probably WiFi all the time etc. So the clock will sync almost immediately and it takes a close look to discover the bug. On the other hand people like myself who live in “weak signal conditions” and do not have their WiFi enabled all the time notice such an abnormality immediately.
I understand that everybody is busy, but I wonder how much such an infrastructure would actually offload stress from support and developers and actually help them on their mission to create a great OS.
1 Like
I think they think it will add even more to their workload. And maybe they are right.
Most the discussions are not happening in the open forum and only beta-rom releases are discussed in smaller groups. There is no discussion about the code, as far as I know. The code is published a long time after the official google rom is out and was tested by google. I don’t know the reasons for this, also I don’t understand the whole workflow, or how people can get involved. I know there is a tracker for patches, but this is also unofficial somehow.