English

Updating LineageOS 14.1 via TWRP + feature test

Hi, no it does not include the reboot fix.

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.

Chris

3 Likes

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)

A somewhat current TWRP version would be needed, all right, but do you really mean LineageOS?

You’re right, I must be confusing lineage and (probably) sailfish. Sorry about that!

1 Like

Yep, Sailfish OS it is (soon: was).

Update installed via TWRP 3.2.1-0 (Releases)

The following things work for me so far:

  • call / be called
  • send SMS / receive SMS
  • internet via WiFi
  • internet via mobile network
  • location
  • compass
  • screenshot
  • main camera (new module)
  • selfie camera (new module)
  • USB connection to PC / MTP
  • alarm (incl. swiping it off)
  • MyPhoneExplorer
  • root (via already installed addonsu-14.1-arm-signed.zip, not installed again)
  • USB OTG
  • WiFi hotspot
  • Bluetooth (music playback, data connection)
  • FM radio

For things that might not work there’s a bugtracker.

1 Like

Update installed via TWRP 3.2.1-0 (Releases)

The following things work for me so far:

  • call / be called
  • send SMS / receive SMS
  • internet via WiFi
  • internet via mobile network
  • location
  • compass
  • screenshot
  • main camera (new module)
  • selfie camera (new module)
  • USB connection to PC / MTP
  • alarm (incl. swiping it off)
  • MyPhoneExplorer
  • root (via already installed addonsu-14.1-arm-signed.zip, not installed again)
  • USB OTG
  • WiFi hotspot
  • Bluetooth (music playback, data connection)
  • FM radio

For things that might not work there’s a bugtracker.

3 Likes
  • Encrypted phone

Update installed via TWRP 3.2.1-0 (Releases)

The following things work for me so far:

  • call / be called
  • send SMS / receive SMS
  • internet via WiFi
  • internet via mobile network
  • location
  • compass
  • screenshot
  • main camera (new module)
  • selfie camera (new module)
  • USB connection to PC / MTP
  • alarm (incl. swiping it off)
  • MyPhoneExplorer
  • root (via already installed addonsu-14.1-arm-signed.zip, not installed again)
  • USB OTG
  • WiFi hotspot
  • Bluetooth (music playback, data connection)
  • FM radio

For things that might not work there’s a bugtracker.

3 Likes

I just saw that in the changelog there is nothing new for the update today. Does it still make sense to update everytime?

1 Like

Well spotted :+1: … I just don’t bother to read the changelog :slight_smile: .

Cool! I didn’t know that Fairphone published it already on the code.fairphone.com site. Will update the modem.zip now.

Edit: Done! As always, you can get instructions and download links at #modemfiles

3 Likes

Good question i was also pondering. Are there really no updates, or are there only no device specific updates, but all other committed LOS changes are included?

On GitHub there are no commits in LineageOS’ master branch so I guess there haven’t been anychanges at all.

1 Like

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 :slight_smile: )

Update installed via TWRP 3.2.1-0 (Releases)

The following things work for me so far:

  • call / be called
  • send SMS / receive SMS
  • internet via WiFi
  • internet via mobile network
  • location
  • compass
  • screenshot
  • main camera (new module)
  • selfie camera (new module)
  • USB connection to PC / MTP
  • alarm (incl. swiping it off)
  • MyPhoneExplorer
  • root (via already installed addonsu-14.1-arm-signed.zip, not installed again)
  • USB OTG
  • WiFi hotspot
  • Bluetooth (music playback, data connection)
  • FM radio

For things that might not work there’s a bugtracker.

4 Likes

Update installed via TWRP 3.2.1-0 (Releases)

The following things work for me so far:

  • call / be called
  • send SMS / receive SMS
  • internet via WiFi
  • internet via mobile network
  • location
  • compass
  • screenshot
  • main camera (new module)
  • selfie camera (new module)
  • USB connection to PC / MTP
  • alarm (incl. swiping it off)
  • MyPhoneExplorer
  • root (via already installed addonsu-14.1-arm-signed.zip, not installed again)
  • USB OTG
  • WiFi hotspot
  • Bluetooth (music playback, data connection)
  • FM radio

For things that might not work there’s a bugtracker.

3 Likes

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?

Edit: solved

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) …

2 Likes

And it works at my FP2 as well! I just didn’t realise, that I can adjust the brightness as well, when the display is on ‘autmatic brightness ON’. I must have displaced it myself!

1 Like

Update installed via TWRP 3.2.1-0 (Releases)

The following things work for me so far:

  • call / be called
  • send SMS / receive SMS
  • internet via WiFi
  • internet via mobile network
  • location
  • compass
  • screenshot
  • main camera (new module)
  • selfie camera (new module)
  • USB connection to PC / MTP
  • alarm (incl. swiping it off)
  • MyPhoneExplorer
  • root (via already installed addonsu-14.1-arm-signed.zip, not installed again)
  • USB OTG
  • WiFi hotspot
  • Bluetooth (music playback, data connection)
  • FM radio

For things that might not work there’s a bugtracker.

4 Likes