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).
1 Like
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.)
3 Likes
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.
1 Like
You can list and execute all the available “hidden menu” codes with Secret Codes (Secret code scanner).
2 Likes
Chris’s goal is to have a clean port of LineageOS to the FP2 that can be submited as official (which is the best way to go, IMO). Any change to the OS itself is not allowed.
But… surely it can be done on the community build, 
2 Likes
Who needs them to release source code when you can decompile the app I have a re-compiled version running on my phone (Lineage of course) but there are still a few permission problems due to the app not being a system app. (have never developed an app that uses superuser stuff 
but I have to put that into the app to work properly probably)
EDIT: It’s harder than it seems… I’ll probably not spend the time doing it, sorry 
Developing a system app seems to be not really possible easily and it’s also way too complicated with su 
2 Likes
I can relate to your arguments so I changed the wiki accordingly. If there is anyone who is unhappy with that solution, please feel free to edit…
1 Like
I actualy don’t know how it happend, but suddenly works my proximity sensor during calls. I cleaned it, so I removed once tbe display. I’m on version 14.1.3.
Encryption and FM radio should be fixed now.
I can currently not upload a new build (due to my ADSL line down), but I guess most people rely on the wearefairphone builds that should get the changes soon.
Chris
19 Likes
What’s missing to make FP2 an official LOS device? 
3 Likes
Thank you for managing PRs and merges to WAF repos yourself, 
This port is feature-full now! 
Does f3fb37 solve the wrong MAC address issue? (Not yet on WeAreFairphone builds)
2 Likes
The WiFi Mac problem should also be fixed now thanks to Luca.
Chris
6 Likes
A cleaner device tree history, a cleaner kernel history, some kernel features like scheduler and cpusets and other stuff.
Cheers
Chris
11 Likes
With the OTA update from 7th July, the MAC address is correct again.
Big thx!
3 Likes
Just FYI the Calibration tool isn’t easily installed because the tool needs to be installed as privileged system app which can only be done by the manufacturer/rom maker or with root permissions. But yes, a flashable zip should be possible (but that’s also possible with a non-open source .apk)
1 Like
Actually will the tool be enough?
FP OS 17.04.8 had the tool, but the OS wasn’t able to use the data provided by the tool if I understood it right.
Hey everyone,
Finally got a new screen and found time to test the latest source. First impression was that it runs better than some of the stock ROMs I’ve used in the past. Great work!
That being said, I did run into some issues after using it for a few days.
- Pairing Bluetooth can crash the device. It first becomes unresponsive and eventually reboots. I can reproduce it by running the pairing wizard in the Pebble app with a Pebble Time. I’ll look into it, but pointers in the right direction are welcome in case you’ve already observed.
Logcat: https://pastebin.com/rGd2YC3Q
- Some (probably related) battery drain that occurs occasionally. Couldn’t pinpoint it yet but the phone gets really hot. So most likely a process that runs into some kind of loop.
Cheers
1 Like