Thank you @piero. I have only recovery-e available.
Using the recovery-e
go to -->settings -->system-updater, select the previous version 3 dot menu, and choose “export”
In settings->updater I have a “…” menu showing me “Preferences” and “Version information”. I’ve selected (I would assume it’s the default) to remove installed sources. So that’s maybe why I cannot find an “export” there?
Reboot into recovery mode, and “apply the update” from the location you choosed (internal or external storage)
I’ve done this and tried to sideload via adb the 1.12.3 eOS file. But it refuses install with the message “Denying OTA because it’s SPL downgrade”.
Humm… I was thinking come back to previous version was possible…
Not 100% sure that works because not tested, but installing TWRP in place of recovery-e, then install previous version and reinstall the recovery-e (for future update compatibility) could do the thing.
I have to test and come back here in about an hour to edit this post…
I have e-1.13 and TWRP already installed, so i tested this :
It worked for me. I come back to e-1.12.3
So, i redo the update (this time with recovery overwrite selected), i am now in your configuration. (e-1.13 and recovery-e)
I rebooted to the recovery-e and choose apply from internal storage (where i have stored the e-1.12.3.zip) and it worked too, i came back to e-1.12.3
So, i redo the update and i am one more time in your configuration. (e-1.13 and recovery-e)
I rebooted to the recovery-e and choose adb sideload (as you did), it also worked, i came back to e-1.12.3
So i redo the update, uncheck the recovery-overwite feature and reinstall TWRP to recover my original state
I don’t have the same device as you,
mine for the test is a Samsung Galaxy s4active using latest “R” /e/build on top of latest stock firmware based on android 5
Have a try using TWRP,
make a backup, and install previous /e/
If you still have a SPL relative error message, wipe /system (trying to avoid anti-SPL-rollback), eventually wipe /cache and wipe /davilk, before another install attemp.
Version 1.13 is not yet available. Instead of hitting refresh I suggest periodically checking the downloads. When 1.13 shows up there then more than likely it will show up in the updater.
The team did extract a list from the image servers of all builds that did not get v1.13. Will share the information as to how we will be handling these builds… Releasing with v1.13 or v1.14.
Hi, thanks for the update. On my FP4 it fixed an issue I was having with in-app maps, which basically @!!#@$-up my car-sharing app. (com.goodmoovs.goodmoovs) This happens every so many updates, which kills my mobility options. Probably there is no other way to check the functioning of an app in a new update than installing it?
Why are there dips and rises in your battery graph?
Fully charge your phone. If it behaves properly the battery stats should reset (100% straight line). After that there should only be a decline, whether steady or drastic, doesn’t matter as long as it is going down.
When it reaches a low point like 15% or less you can see actual app battery usage in that particular cycle.
/e/OS 1.13 has been running quiet good for the last couple of days on my device. For some reason the permissions for some apps were reset during the update and need to be granted again. I can’t remember all the apps/permissions but here are some them:
VLC: Files and Media
Shelter: Files and Media, Display over other apps
NewPipe: Display over other apps
AnyConnect: VPN Connection/VPN Provider
Strangely the same permissions were not reset for some other apps:
Yes. To me it implies periodic plugging in of the charger. So let’s say battery usage from some app shows a rather high percentage. A user may complain that app drains badly.
But the graph will show a series of dips and rises indicating charging. Not fully charged, stats are not reset, no point to start measuring. No clearly defined start of a battery cycle so the app’s perceived high usage may be an accumulation over a period of plugging/unplugging.
