As always, I updated with the
manual zip file. No problem so far, it feels stable (ignoring the fatal clock bug…).
Also, it fixed the light sensor lag when turning on the screen, so I’m happy for now. It seems it was just a placebo effect, unfortunately
As always, I updated with the
Hey @Roboe, last time I also installed with the manual zip file, as it wouldn’t work over the air (download okay, restart to install and then booted w/o installing as if nothing happened). However, why do you always do it, what’s the advantage to an OTA update?
I don’t like the Updater app, because it creates a confusing
userdata folder on the storage (which in fact is a mistake), and I had bad experiences in the past with my former Nexus 4 storage being wiped out accidentaly via MTP for that reason.
But anyway, I need to have a computer near when I update, because I patch the system with Needle/Tingle for faking signatures, which is needed by microG to impersonate Google Mobile Services.
Besides, I change emojis to the EmojiOne set, increment DPI settings (add
build.prop, instead of 480) and apply AdAway adblocker, and I like to make a backup of
system and store it on my computer in case anything crash and I need a quick restore.
Yes, I have a complex update procedure, I have to automate this process sometime.
Thanks for the insight. It’s a bit similar for me regarding the laptop close during an update, as I’m also always flashing the latest OpenGAPPS and xposed on it. I haven’t really figured out a good backup routine, but your way does make a lot of sense, I guess. And I love the idea regarding the smileys - I’ll certainly have to look into that soon!
Thanks for the Update, worked like a charm using the update guide.
Just wanted to let you know that I really appreciate you providing security updates so quickly… Great job, keep up the good work!
With your setup, it seems easy enough. I’d do the following when an update pops out from the Updater:
- Download latest Xposed Installer
- Download latest OpenGApps package
- Download the FP Open update from the Updater (if it’s not possible just to do this, then download the OTA package from the web)
- Reboot to recovery (Reboot from the power menu and keep Vol + pressed)
- Flash the three zips in a row, first the OTA and then the rest
- Reboot and enjoy
You can take a look at this great @freibadschwimmer for further options:
It seems this all connects to the SD-card not being writeable. I thought I updated the platform.xml properly, but I had two “” instead of one ". I corrected that, now the app can be reinstalled.
Can the platform.xml be updated from TWRP before the reboot?
Glad this worked for you ! You could build a custom .zip to flash from TWRP but the most simple would probably be to backup your platform.xml on your computer as platform.xml and write a small script that does the following :
adb shell cp /system/etc/permissions/platform.xml /storage/sdcard0/permissions.xml adb remount adb push platform.xml /system/etc/permissions/platform.xml
And run it from your computer each time you upgrade. Another way would be to use a shell script on the phone (that could actually be fun oneliner using
The first line allows for backup of your platform.xml at the root of your internal storage, thus it’s not exactly mandatory
Beware of file permissions. You may need to run
adb shell chmod 644 /system/etc/permissions/platform.xml
The update to FP Open 16.10.0 went smoothly for me (my phone is encrypted, does not have the Google apps, or the Xposed framework).
plain build in updater user - no real trouble during the update - just no real “visible results” - I do get the reported “clock time error” and I still have trouble with the calendar. It would help me a lot to know at least where to pose that kind of question - as apparently that place is not here on the forum.
[no random reboots so far, so the wrong time setting isn’t causing trouble - yet]
This two strange screens at the update module are gone and it looks o. k. now. But I didn’t change anything to get it right. Quite mysterious, this change!
I didn’t find any solution with problems with Google Play Store and F-Droid store, I described before. What I have found is another store “APKPure”, which offers a lot of apps you find at the Google Play Store, but not at F-Droid. But I don’t know at all, how trustworthy this store is. It also shows updates, if there are newer versions of installed apps, but I can’t update all of it. May be, that is because I installed these apps from other stores originally?
When I try to open the Google Play Store, now I always get the message “Google Play Store wurde beendet (= has closed)” and I can’t use it.
With F-Droid it’s the same as before. When I try to download an app, I always get the message “F-Droid ist abgestürzt (= has crashed)”, but with answering “OK” and a second try it works.
Any suggestions, what could be the source for this behave??? I already cleared the app cache and reinstalled the store apps, without success.
Try this. May be helps…
Try to uninstall F-Droip app and Download/ install a new file of F-Droid app.
I uninstalled F-Droid, loaded it down again at the desktop computer, transferred it via USB to the FP2 and installed it again. Result: Same error, behaves as before.
I’m also currently using Apkpure and, even though I’m quite happy with it, it would appreciate if someone could confirm it’s safety.
Since the update, I can’t connect my phone to my PC anymore. It only works, if I choose the “Mount SD Card” option, but then I can’t get to the internal storage anymore. Does anybody know what to do?
This usually happens to me when my OpenGApps version doesn’t match. Flashing the latest available version helped every time.
Thank you very much, verasiegrid!!! What you recommended, I am shure, I did before, but without success. Today however it worked!
Again, it is better now, but not o.k… F-Droid works, but Google Play Store doesn’t: I can see and choose any of all the apps, but I can’t download or update any of it. The download process starts, runs and runs and runs and ends with an error message: “Download not possible” or something like that. Deleting the cache didn’t help.
On the other side: APKPure works.
Any other suggestions what I could try to get the Play Store running?