It is configurable with lineageos, at least “notifications settings” have a setting call “akku-LED” (in German).
I know, but unfortunately it doesn’t work, at least not for me
It’s high priority to get encryption working but it’s lower priority than other stuff I currently have to do in life. If someone knows how to fix it, my sources are on GitHub.
Is it maybe a idea to call this version 1.0 and work from there?
Why not call it 14.1.0 or something, cause … dunno Its from 14.1 and so on (-:
Awesome work everyone. Stock Android (although much better than most OEM ROMs) feels kinda unfinished and missing many features, if you come from CyanogenMod. Will try it on the weekend.
I currently move house, so I won’t be able to work on this for a few weeks.
New release available here: https://www.androidfilehost.com/?fid=673368273298963946
- Kernel update to FPOS 17.04.0
- Kernel hiding SU - thx to z3ntu
- Lineage upgrade to latest source and June AOSP sec bulletin
- Tethering should be fixed
BTW: regarding security bulletin / kernel updates. The prima wifi driver updates are still missing. And also I guess that latest sec bulletin updates for kernel are not there. I also have not gone through the full list of CVEs to see if something is missing…
So watch out chaps: dont use this fairphone rom for your top secret work missions. AND I also have NOT tested emergency calls.
Tethering works! Good job @chrmhoffmann !
I can also confirm, no charging LED and no UPnP.
And there’s the wrong MAC, but that is already known.
The system runs pretty good.
Do you plan to add the patches for UnifiedNLP?
I have updated the modem firmware to 17.06.4 release from Fairphoen Open. I have not added any output to the script this time, so don’t worry if it says something like “script result was [t]”.
See first post for download links.
Does it look as if I would plan anything?
I don’t know. CM supported it in the past. Lineage doesn’t. The patches are there, but they did not apply them. Can’t you apply them, or has this to be done in the Lineage maintree?
Just a modest proposal: Wouldn’t it be more accurate to split “sensors” in the first post of this thread instead of just generally ticking them? I think quite a few people are having issues with the proximity sensor and dead screens during phone calls in Lineage OS. I know that this also used to be a problem on FPOS and FP Open, however, the problem seemed to be resolved in later versions… Opinions?
Fairphone should release the source code of their sensor recalibration tool so it can be e.g. released on F-Droid.
I absolutely agree with @paulakreuzer , however, that still does not solve the problem that the wiki post is somehow misleading. For me it is one of the major annoyances, so, wouldn’t it be fair to warn users in advance? Perhaps we could add something like: “due to missing recalibration tool”?
It’s a wiki, so you can add the bug to the list yourself.
I wouldn’t change the entry that says that the Sensors are working though. They are all working in general. And just like with FP (Open) OS the proximity sensor bug doesn’t affect everyone (I never had the issue on any OS).
According to this there are Android devices which do a proximity sensor test after dialing *#*#0588#*#* … with Fairphone OpenOS 17.06.4 nothing happens (while *#*#4636#*#* indeed gives a test menu).
Perhaps there’s something to find in the AOSP sources that does the proximity sensor test that way, but Fairphone don’t implement it? (Yes, I have no clue at all, it’s my mischief and mayhem day.)
Added the issue to the list of known bugs…
I disagree. The proximity sensor bug is not specific to the LineageOS port but a general firmware/hardware issue that affects all OSes. It is not a thing porters should fix, so it shouldn’t be there.
It should be mentioned in a warning and linked to the issue thread in the forum, though.
You can list and execute all the available “hidden menu” codes with Secret Codes (Secret code scanner).