I think this just prevents hijacking of the OTA, if I read that correctly: https://source.android.com/devices/tech/ota/sign_builds#sign-ota-packages
i.e. only someone with the keys I’ve generated now is able to create a build, that the updater will accept for updating. this does not affect any other functionality. The update to someone else’s builds (like officials) usually has to be done via TWRP anyways…
Thank you @fodinabor ! Your e-0.7-p-20191003-UNOFFICIAL-FP2 build works perfectly !
I had 0.7-n, I dirty-flashed 0.7-o over it (causing a bootloop), then dirty-flashed your 0.7-p directly over again, and my phone booted fine ! I’m now curious to see how the OTA updates behave.
update is up, you should get notified or manually search for updates.
p.s.: I’m trying to not build unnecessarily if no changes have been made, so I’m usually looking whether the official nougat images are updated and build afterwards.
Hey guys,
As of two days ago (6.2.) there are official pie builds for the FP2: https://images.ecloud.global/dev/FP2/
I encourage you to switch to official builds, by manually flashing the provided images.
That said: I will probably continue providing my builds, providing you with easy OTA updates until you find the time to manually flash the official builds.
EDIT: keep in mind to download an image with -p- in it and not -n- … Seems like they still build nougat and publish the links in the same place… That’s somewhat confusing…
Great! Thank you! Did you already try the switch? In the testing phase of the official build I always ram into problems when I just flashed the official on top your unofficial one.
Wiping data partition helped, restoring a backup of it caused problems…
