FM radio works fine here. And I have the same image installed as you did.
Just without gapps.
FM radio works fine here. And I have the same image installed as you did.
But it did, I came here from an encrypted Fairphone Open OS .
Before I installed LineageOS for the first time, I only wiped the phone and hoped for the best, but upon first booting after installing LineageOS the encryption complained about my password being correct but the data being corrupt, hence my formatting of data (mentioned in my FM Radio post above) before I installed LineageOS again and it worked.
Anyway … I now formatted data again and restored a TWRP backup from before trying to encrypt and currently MyPhoneExplorer is restoring Internal Storage (needs some time because of GBs of downloaded Osmand maps, any form of upcoming FP3 could use USB3.0 ).
Will perhaps have a look at the OTA thread and this old possible workaround mentioned in the bug report discussion later.
Edit: Oh, look who ran into something similar before … Perhaps forgetful me should try that again.
Thanks for confirming this.
Ok, I don’t know what the pico package I installed would have to mess around in these parts, but that’s a valuable hint. I could try installing again without it or change the order next time and install the fresh modem files after Open GApps.
I don’t think, that gapps has to do anything with this. But this is the difference.
I have f-droid privileged extension and microg flashed.
Are you able to calibrate your compass? The skymap app says, that my
compass is not calibrated correctly. But I am not able to calibrate it within
the app. I can see the compass moving in the satstat app, but I am not sure,
if it is correct. I have a Xperia Z1 here with lineage. There is the same behaviour.
Funny thing, that. In Fairphone Open OS, my compass was always pointing in the wrong direction when I initially started any map App, some few seconds of swinging around for calibrating always fixed this. I thought perhaps the magnets in my flip case would cause this, but …
Now in LineageOS my compass is showing the correct direction since I installed (and now restored) it, I didn’t have to calibrate it once.
GASP! The rumours were true, Android really seems to be a proper mess …
Did the same things again and restored Fairphone Open OS 17.06.4 from a TWRP backup to establish 2 things:
FM Radio does work in the current Fairphone Open OS (I checked, because I last used it back in Android 5).
@Roboe: Fairphone Open OS has once again happily encrypted my data partition, at least both the OS and TWRP want my password and seemingly decrypt the data.
I will restore my Internal Storage for now and continue using Open OS for the time being.
When I have some time again, I will try to set the phone back to the state it was delivered in and then try to install LineageOS from scratch.
Quick update on the Bluetooth issue:
- Still reproducible when running the initial setup in the Pebble app. The phone does not instantly crash or freeze. Instead the Pebble app seems to continue the devices search just fine until I try to leave the app, open the statusbar or lock the screen.
- Other BT devices seem to work fine (mostly tested with my BT headphones) BUT I also realized that my Pebble is trying to connect in LE mode. This could make the difference.
Unfortunately nothing too obvious in there. But I’ll keep digging.
The answer is simpler than expected: Privacy Guard
Bluetooth LE was indeed the reason why other devices worked just fine. More specifically, Android requires the ACCESS_COARSE_LOCATION permission to perform BTLE scans. While ACCESS_FINE_LOCATION was allowed for the Pebble app in Privacy Guard, ACCESS_COARSE_LOCATION was set to ‘always ask’ - just that the permission pop-up never appeared. Once I set ACCESS_COARSE_LOCATION to ‘allow’ (or disable Privacy Guard for the app) and everything works.
I’m wondering if this is a potential LineageOS bug, since the pop-up to request coarse location never appears. And I’m surprised that ACCESS_COARSE_LOCATION needs to be granted specifically while ACCESS_FINE_LOCATION is already available. I’ll try to write a small test app to reproduce the problem and get a clearer picture.
I wonder why Android needs location access at all if you want to do a BTLE scan.
I just did a factory reset from within Fairphone Open OS thinking it would reset my phone to a somewhat near initial state … wrong, OS and TWRP are the same and encryption is still there, only every other user-related stuff is gone and the OS starts with the initial setup.
Dear diary, “factory reset” nowadays seems to be a funny thing not 100% related to the term I once knew, I’m feeling old …
So I wiped everything in TWRP and formatted data again to get rid of the encryption.
There are lineageos repos now for fairphone:
Code review is done through gerrit as usual:
It is not yet an official device with nightlies.
What is missing?
- CVE updates
- more code review
- switch to a better kernel source at some point (maybe not a showstopper, but would be good)
Getting the FP2 listed as an official device and official builds are a goal though? Just wondering because of the we-are-fairphone OTA etc.
Currently waiting for that, so I do get the “official” OTAs from the beginning.
Yup: The OTA server is doing the building for now (and swithing to the official repo) and when it’s official device I’ll make 2 migration zips to hop on the official release without a factory reset.
Just did a successful build with this manifest:
<manifest> <remote fetch="https://github.com/" name="github2" /> <project name="LineageOS/android_device_fairphone_FP2" path="device/fairphone/FP2" remote="github2" revision="cm-14.1" /> <project name="LineageOS/android_kernel_fairphone_msm8974" path="kernel/fairphone/msm8974" remote="github2" revision="cm-14.1" /> <project name="FairBlobs/proprietary_vendor_fairphone-fork" path="vendor/fairphone" remote="github2" revision="cm-14.1" /> <project name="lineageos/android_device_qcom_common" path="device/qcom/common" remote="github2" revision="cm-14.1" /> </manifest>
Starting a new build with the old keys (OTA signing) and OTA url, so this will work again. I will test the zip tomorrow and then push the semi-official release over OTA if everything looks great!
I have updated the modem.zip file to the latest modem firmware of Fairphone OS 17.07.6. This time I have added proper output to the installation script. This zip file also includes the official Fairphone splash image. In case you have installed a custom splash image, you might want to reflash it.
After you have flashed the zip file, you should see the version
About Phone ->
Since those are binary blobs, I have no idea what has changed since the previous release. But comparing the image files, I can see that the following files were changed:
The following files were not changed since previous release:
The following files were included in the previous release, but not in the current:
I included sdi.mbn and the unchanged files in the modem.zip file, so you can upgrade from older versions as well.
Alternatively, you can flash the latest modem firmware using fastboot. You can get the firmware images from the official Fairphone OS downloads page (scroll down to binary images). Don’t flash system.img, boot.img and recovery.img obviously.
(emphasis by me)
Yeah, you finally included
sdi.mbn in the ZIP,
… which was last updated in FPOS 1.4.2, about a year ago. Those were the days…
What is it about sdi.mbn? I tried googling it but with no success.
Thanks for the update. Sadly this update still suffers from the proximity sensor wakelock bug. Can one of the devs confirm that the old modem files that we used as workaround on FP OpenOS would work on Lineage OS, or is there a compatibility issue ?
The old modem files for Fairphone Open OS should work. However, they might contain unpatched security vulnerabilities and it is not recommended to use them.
If you run into problems with the old modem files, you can always flash the latest modem.zip from the first post of this thread.