Still I can’t change the wallpaper. It’s only my issue?
Yes. Me and my SailfishOS guys have no problems with wallpapers. THe PNG FIle need to be 1080x1920
Flashed on FPOpen using mechanismen of plain delivered Fairphone with onboard tools
I had last update on 16.12 at beginning of 2017 via intern updater.
I added openGapps using this post: ✏ Install OpenGAPPS (Step-by-step guide)
Everything fine, battery lasted round about a day, FP2 “struggled” with highconsuming apps while charging.
Then I didn’t any update until yesterday.
Changed to 17.06.xxx
these effects appear:
- Now I can literally watch decreasing battery on front screen
- every minute “Google play services has stopped”
- on “top” line the message is “google play services needs to be updated”
- I turned FP2 off and started charging over night. But next morning it was only 21 %, I plugged in at 9 %. Battery history shows “nothing happend during night”.
- recalibrating distance sensor - did nothing
- apps battery optimization is “all apps optimized”
- cannot uninstall “google play services”
As I want to keep openGapps “out” for next month, I hoped it just got lost using fpOpen update, but it did not.
- trying backup-apps, but not so important, save my data anyway
- will try to use TWRP to install 16.12 again using https://code.fairphone.com/projects/fp-osos/dev/fp2-blobs-download-page.html
- surprise here: current release is called 17.03 instead 17.06 - why?
- if it works, will go same way step by step to 17.01 etc.
- if it not works, I will start to flash / wipe FP2 entirely for clean install
Because I assume Gapps will stay with intern mechanism.
Will report later, is my first real disappointment, “regular” restarts … I got used to it.
That is the BLOBs page. Those ZIPs are not flashable.
oh, thanks, I was still on my way to understand the technical part of my next steps.
How do I get flashable older versions?
It appears part of opengapps survive a system update (or installed apps assume it is there because it was at setup time, and freak out if it isn’t). Previously this had led to bootloops if opengapps wasn’t installed immediately after installing the FP openOS update package, as described here.
Why does this matter: I’d say there’s a fair chance that if you flash the old system without either installing opengapps or wiping your data or doing something smart that I don’t know about, you’ll still end up with a misbehaving phone. You might not run into that problem, but if you do, reflashing opengapps might solve it. If you do the latter, remember to download the latest version of opengapps for whichever android version you’re installing it (different versions for Android 5 and Android 6).
Chances are that your battery issues are related to the malfunctioning gapps installation.
Try the forum topics for the respective versions, IIRC there’s a request for a direct link for the manual install version in most of them. There is at least a direct link for 16.12, which you mentioned you were on before. You will need to use fastboot to install those images. No need for installing intermediate versions.
ota and you got the flashable ZIP: https://storage.googleapis.com/fairphone-updates/a3f25298-dd8e-430a-a198-2be103ae710c/fp2-sibon-16.12.0-ota-userdebug.zip
No need to flash intermediate versions neither, it is a complete release, not partial.
Thanks for detailed explanation, will now start with new openGapps just to get a usable phone and try “resetting” to without openGapps later.
I read my way through this complete topic, but I’m still confused what I have to-do to smoothly update my
FP2 to 17.06.4 (currently running: FP Open 17.03, no-Gapps, Xposed, TWRP 3.1.0-0, F-Droid as normal App). When I flashed the last few updates I simply followed the instructions here: ✏ Update Guide for a modified FP Open OS (with Gapps, Xposed and more)
But it seems that this is not the recommended way to update to this A6 version?
I’m afraid of running into boot-loops (or brick it completely), destroy my contacts-data (or other app data) or have to downgrade as worst case.
So is there any recommended straight forward procedure which minimize the risk of any of the mentioned problems?
Thanks in advance.
I have dared to upgrade as well. Of course after a backup with Titanium Backup…
So far my experiences are:
- Update (using the standard updater-notice) went smooth
- Installing Xposed (new version) was without problems (GravityBox also needed new Version MM)
- No data losses
- I did have froozen screens, when I tried to open amaze. Reinstalled it and so far it did not freeze any more and did not reboot by itself
- The phone got extremely hot during the upgrade!
- I like that the lockscreen is more simple now with just the time. I did not like the old “you own your phone since…”-stuff
- Battery life seems (subjectivly) longer
- Some apps work now, that did not work before. For example “outdooractive”. This app had a problem with the fused provider. Now this issue is gone
- I tried to restart the phone in airplane mode and it seems that it remembers the time now. This would be a great success for me, because I am often in areas without reception and it was a pain not having the time any more.
- SD-card seems to work better no. You have write permission (if it is kept “external/portable”) and can use it for backups with Titanium Backup without changing the platform.xml. Nice! I did format the SD as internal storage, but then I could not access it from a computer any more and the additional storage was recognized. I think then it can only be accessed by the phone, which makes no sense to me…
I do have a few quesions, which are not answered for me clearly yet (I have not found a solution yet):
- The edge-swipe is gone. Is it possible to get it back with gravitybox? Is it possible to disable the “hot seat” (line with the 4 apps and launcher) with gravity box?
- Is it possibe to reactivate the differnt options of the powerbutton (restart, boot to recovery) with GravityBox?
I’ve updated my FP2 with the update app and I get pretty much the same problem as described above: screen freezes as soon as I try to do something and the phone rebooting in loop. The phone is encrypted and doesn’t use fancy apps like Exposed.
Booting with TWRP, it can’t mount the
mounting /dev/block/mmcrblk0p20 on /data failed: Invalid argument. Mounting manually through the terminal gives the same result. Thus, I can’t backup the
So far, I’m not sure what I should do to fix this up. Many answers have been proposed, but I don’t know if they’re related to my case. Moreover, there are several conversations running simultaneously on this thread, which makes things worse. Since a lot of people suffers from the same problem, what about creating a new thread for this? Or wouldn’t it be nice to have a howto from the devs?
These two sentence correlate.
Bug has been reported to the bugtracker here. No official response yet.
No hacky solution worked for me neither, although some people were able to unblock their situation. I suggest to contact Support, linking to the official bugreport. Don’t forget to add your (possible) data loss and time loss as well figuring out what to do.
What you would like to have is another launcher. I do not know much about gravitybox but it is not likely that you get what you want that way.
The hot seat is part of the preinstalled launcher app and you can get rid of it by installing another launcher app and setting that as the default one. I’m not entirely sure but I think the fairphone launcher 3 is being adapted to android 6 by some community members but not yet available. There is also an inofficial version of the original fairphone launcher used on fairphone 1/1U.
It is a whole world of launchers out there (one of my personal favourites: T-UI, a geeky terminal-like launcher). I’m pretty sure you will find something you like.
Hmmm, again I’m not sure but wasn’t there an xposed module to add options to the power off menu? A little search revealed this one to me, but it is obviously discontinued…
A post was split to a new topic: :nl: Fairphone Open 17.06.4
Same situation here as some wrote already. I’m not familiar with techie topics, I’ve struggled through FP Open too much already and I’m definitely not going to update to FP Open 17.06.4 if there is a risk of bricking the device, getting stuck in endless loops, having to downgrade & upgrade or anything the like.
I’m using FP Open 17.04.0 with openGapps: no encryption, no Xposed. I couldn’t deduce from this topic if my Fairphone will be affected by the dreaded bug. Is someone on the position of stating if I will be able to update smoothly?
Otherwise, I’ll switch to regular FP OS so I can get an OS that works out of the box, ready for muggles, and switch back some other time. Is there a guide to switch back to FP OS with FP Open + openGapps? I guess it’s not straight forward…
If you are anxious to damage your phone when an update is applied, you should not update at all. Potentially there always is a minimal risk something gets wrong during a flash.
Some stores might do the work for you if you do not want to try. Maybe even someone from the Fairphone community within your country can help you.
Good point, but an updated phone is more secure than staying with an outdated one, and normally the updates go smooth, so taking the risk normally pays off.
But this time:
- this is a major update, so it is riskier than usual
- many users reported a very bad state after the update, which is what specially worries me.
You are absolutely right that I could seek help on my surroundings, I’ll try as well, thanks.
Now I have “time” to read and understand next steps to exclude openGapps again.
btw: forgot to write that I updated earlier from 16.11 to 16.12 while openGapps was installed, but maybe to few apps relied on that, because this time no drain or anything else than just “aCalender did not show anything”.
I absolutly agree with @Neus . I’m not generally afraid of the upgrade. I write my questions here at this topic as I want to upgrade, but I would like to know if
–> minimize does not mean that I will not going to do it in general , as I know that it is important to apply at least security fixes. (apart from that which the german government would like to keep open for their “Staatstrojaner” )
This makes sense. I thought it could be a side problem.
So, I’m waiting for an official workaround and keep my phone in safe mode.