The reboot fix package is not yet available for download (only through updater). Also, if the fix is really only in modem (NON-HALOS image), it would not be distributed with lineage but must be flashed separately.
That’s a rare occurrence - most of the Q3 20017 and later devices will also have the new display module, which doesn’t play nicely with Lineage yet.
(In case people otherwise think Lineage isn’t affected by the reboot issue fixed in FPOS with the new blobs)
Nevermind… time for me to get some more sleep (see below)
Baseband version: 4437.1-FP2-0-08 (Settings - About phone)
° Because Fairphone OS 18.03.1 was released with modem file changes but there was no new modem.zip at the time of writing, I booted up a Linux and downloaded the shell script from How to make your own modem.zip.
Because there were no new OTA and manual files for Fairphone OS at the time of writing, which the script would normally use, I simply entered the already available new Fairphone Open OS URLs and checksums into the script and thus got my own new modem.zip.
Seems to be working until now … I’ll update here when my phone suddenly combusts .
Question, since I seem to have approached this a little too casually:
The way I read the script the required manual OS file delivers the modem blobs, and the only thing the required OTA file delivers to the process is the META-INF\com\google\android\update-binary.
Now I noticed (i.e. WinMerge says) that the update-binary the (updated) script pulls from Fairphone OS 18.02.0 is different from the update-binary my adaptation pulled from Fairphone Open OS 18.03.1.
Is there a specific reason the update-binary of Fairphone OS is used instead of the update-binary of Fairphone Open OS?
(Hopefully not )
I updated my FP2 to the actual LOS 14.1, but after the update the display was very dark, hardly to recognice with the setting 'Adaptiv brightness is ON".
I had to set it to “Off” and it is normal again. When I put it back to “ON”, it is dark again. Does anybody else have this experience after the update to LOS14.1-20180328? If it is not the update, what else could de the cause for this strange behavier?
I have adaptive brightness enabled, too, and it works as intended.
Even with adaptive brightness enabled you can still change the overall brightness of the screen, did you accidentally slide the setting to dark?
It’s hard to think it’s not the update, when the problem suddenly occurs right after the update. But the same update did not cause this problem on my phone.
So there’s still the brightness sensor.
You could use an App for reading out the sensor (I use Sensors, but that’s from the Play Store) … What does the brightness sensor say to dark and bright surroundings? An automatically always dark screen should mean the sensor gives a “wow, it’s totally dark, we don’t need a bright screen” reading to the system regardless of any brightness around it.
In this case … The brightness sensor should be the same part as the proximity sensor, this post has some cleaning tips for the area (just expand the “archived text” bit) …