Lineage 17.1 - FP2

[TeamB58]

But the blobs package is from A6.

[ulath]

I can confirm that the 20210129-nightly update of LOS 17.1 fixed my 4G connection issues! Thanks a lot @ everyone involved in solving this!

[Norry]

Thanks, so far it is OK, without latest official modem files.

[Alex.A]

@fapsi4

Note: As far as I understand, there could be different behaviour if you install the latest official modem files provided from fairphone here after the lineageos install, but I think that this would be out of scope of lineageos and there surely will be other incompatibilities.

Note: this modem zip isn’t provided by Fairphone and isn’t official but was pulled by the community from each latest FPOS release.
As the last update of the modem files was with the last update of A6, i.e more than two years ago, and LOS should already contain this latest version if you had a FPO(O)S version installed before installing LOS which was higher or equal to the latest A6 FPO(O)S, you already have the latest version of the modem files, and there isn’t any reason for which flashing the latest zip should change anything.

Edit: Corrected my statements, thanks to @chrmhoffmann for the correction

[chrmhoffmann]

Lineage does NOT contain any modem files.

Chris

[Alex.A]

Right, I edited my post accordingly.

[fapsi4]

@Alex.A @chrmhoffmann thanks for the clarification, didn’t understand that correctly

[Azimoth]

Hi, the LTE connection is coming back reliably again on my phone as well. Yet I have another problem now. Since it seemed a little too much to put it in here, I created a separate topic for it, yet I’ll leave a link here, just in case it’s acutally related to LOS:

Black screen Problem (LineageOS 17.1 (post-Jan 2021-version))

Hi, after the LineageOS update at the end of January finally resolved the crashing LTE issue, I switched back from /e/ to LOS (preferring an OS without microG). In order to do that I reinstalled everything from scratch. A new problem has emerged: If a call comes in while the screen is switched off, it remains black. I can answer the call using the volume buttons (I activated this feature in the dev settings), pressing the power button silences the call and turns on the screen, but I did not …

Any help/thoughts/input is appreciated.

[oli.sax]

@TeamB58

@chrmhoffmann any hope for LOS 18.1 on FP2?

Lineage-18.1: Unofficial test build

Hi folks, it’s THAT time of the year. ROM 8th-Feb-'21 (2nd version) sha256: afde7113288a0ebdca3d9a03a13387509818044fa590cec1d5fec99bc143a17e Recovery 8th-Feb-'21 sha256: 0fccea36937fa9196c3639a740cc3097634ee272289936acf49a25ad4b18ef60 Gapps 3rd-Jan-'21 If someone can mirror the dropbox link… androidfilehost.com seems not working for me. Few notes: Google has dropped support for legacy keystore in 18.1 (so if your device does not boot, you might want to wipe): ** You might want to rem…

[d2w]

I just recently switched from LOS 16 to LOS 17.1, so I am almost late to the party.
The upgrade worked well, big thanks to the developers and everyone who contributed to the release.

[Alex.A]

@Alex.A

I had problems with my system, which probably led me to not applying the patch correctly. I will detail them in a later post.

Now doing it, a bit late, but better late than never!

I can confirm the “Rooted debugging option” didn’t appear for me either, and never had in the past. I had already noticed this when my brother installed LOS on his own device, he had this option, and I didn’t (although having our devices under the same build). A few other options were a bit different (mainly a difference in the name, some contained capital letters on my phone and not on his).
I reinstalled the system on a second FP2 and copied my data, and now the “Rooted debugging” option appears, though there are still options that are named differently on our two devices.
It seems some options on the device remain in the same state as their when they the system was originally installed, and don’t update when the system is updated. Strange…

[chrmhoffmann]

@Alex.A

I reinstalled the system on a second FP2 and copied my data, and now the “Rooted debugging” option appears, though there are still options that are named differently on our two devices.

Don’t forget that general lineage questions could (or should) be asked to the lineage team on IRC or reddit.

Chris

[Martin_Anderseck]

I’m running the latest build of LOS 17.1 and I’m using apps like Conversations or Signal for calls sporadically. Now I had to learn that people that I’m calling experience a very strong echo. I have called via those two apps from time to time in the past already and cannot remember having had this issue so strong after most of the apps switched to the software echo cancellation. I’ve checked the LOS change log if I can find any suspicious changes but didn’t find any. I have checked the issue with the phone alone (strong echo especially in Signal), with the Fairphone headset (almost identical to phone alone) and with another headset I had lying around (almost no echo at all). The echo disappears with the Fairphone headset if I remove the ear plugs from the cable btw, but that is most probably just the way electricity works
Can anyone confirm these issues in LOS especially in Signal, is this the same in other OSes and can anyone tell if that has ever been better (what I do think but cannot say for sure)?

[Alex.A]

I can confirm this issue, and have experienced it just not long ago. I have done a few tests, it seems some apps (VOIP or videoconferencing tools) record the sound with the primary as well as with the secondary microphone (located in the top module). This is what leads to this echo, while it should record only with one microphone.
IIRC this issue doesn’t happen on FPO(O)S for some reason, but does happen on custom ROMs. And I have no clue how to tell these apps to use the microphone correctly.

[Martin_Anderseck]

Although I want to believe your explanation with the two microphones, there are a few things that speak against this: From what you write it sounds like “your” echo means that the person I’m calling can hear me twice (with echo thus). In my case the other person can hear himself/herself taking with a small delay again. And if it was really about the two mikes then it should disappear completely with whatever headset. But that’s not the case.
For Conversations I even opened an issue some time ago and that was fixed and that fix used to work not only in FPOS but also in LOS:

Echo when calling some specific devices

Maybe it has to make with WebRTC having been updated… I probably should open a new thread to find out if people on other OSes have the same issue lately again…

[Alex.A]

The FP2 offers to test my theory very simply: let’s just remove the top or the bottom module and see (well, hear ).

@Martin_Anderseck

I probably should open a new thread to find out if people on other OSes have the same issue lately again…

Echo in VOIP calls?

[yvmuell]

@Martin_Anderseck my brother lives in New Zeeland since a year and we always used Signal for calls without issues. 1-2 weeks ago I installed 17.1 (due to the mobile data issues I still had 16.0 installed) and yesterday I had the first Signal call since the Update and it was very bad in terms of Echos when having the speaker loud. My brother heard himself twice and I could hear a very nasty sound/back coupling…so seems this is really connected to LOS17.1

[chrmhoffmann]

You should try the next build.

Chris

[chrmhoffmann]

I guess we can close this topic.

17.1 is no longer built nor supported. Please save your data and upgrade.

Chris