CVE-2017-7541 is for broadcom wifi. FP2 is not affected by this, even though FP might have fixed this in the kernel.
Hi,
I am trying to go through the CVEs. But it’s a lot of stuff and work. But: I merge the FP open kernel source, that means that we have the same protection as FP Open.
I’d even be bold and claim that the lineage kernel has more CVEs fixed than the FPopen, as I have merged more CVEs that are not covered in FP open or from Qualcomm CAF.
I’d have only one advice: if you are really concerned by security fixes, the only viable option at the moment is to buy a Pixel phone. That’s sad, but true.
MSM8974 does not get support anymore from qualcomm (for a while now). So who knows what problems the modem, blobs, or other closed source components have, that neither QCOM, nor FP can fix.
Lineage is doing best they can, but…
Chris
9 Likes
Didn’t know that that much is on your shoulders… But thinking about it, these are not LOS CVEs but kernel’s, and so it’s your burden… Can’t thank you enough, and I think with some conscious usage patterns one can at least try to minimize the exposure… In the end, there are probably still lots of undetected bugs, at least undetected by the “good side”. So, thanks again, and don’t let you get frustrated by the amount of work and naive “consumers” 
4 Likes
No problem. I just wanted to clarify, that this is a constant work-in-progress and I try to do my best in my spare time.
Chris
PS: I was not joking about buying a Pixel. At the moment, the only guys who are to some extend on top of the security stuff is unfortunatly google.
1 Like
No, I know, the Pixel is indeed first in line, and then there’s a certain amount of man power available at Google… Probably I even would use a Google device, if I hadn’t found the FP2, in 2015…
3 Likes
Update installed via TWRP (Edit: still 3.1.1-1 before I saw that 3.1.1-2 is out):
- lineage-14.1-20171107-nightly-FP2-signed.zip
- modem-17.11.2.zip
- open_gapps-arm-7.1-pico-20171107.zip
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
Would that result in the Baseband version being unchanged (4437.1-FP2-0-07)?
1 Like
I’m glad you’re asking this… I haven’t got a clue about any of this, it’s all new to me. I’m just glad there are people like @jnsp and @chrmhoffmann around 
Thanks for all the work you’re all doing!!
1 Like
Does anybody else have the problem, that when the phone is off and charging, it won’t boot? I have to unplug it, boot it and then replug it.
2 Likes
Yes, I do have the problem too…
My Problem was not any more getting Access to the system at all. I failed the moment I tried to enter the PIN for the SIM. I did not have access to the settings anymore.
Try new lineage from today.
Chris
Yes, the baseband blob hasn’t changed.
1 Like
To apply this week update we need to update modem file right? in that case I just queue it in the TWRP install? First the LOS upload followed by the modem?
Thanks
The modem.zip is completely independent from the operating system.
It is not required to flash the modem.zip file, it is only recommended in order to get the latest security fixes for the proprietary qcom modem firmware (that is stored on a seperate partition).
It does not matter in which order you flash LOS and the modem.zip ;).
5 Likes
Just remove your back camera, boot, encrypt, plug the cam back in. It worked for me.
2 Likes
Hi Chris, I just also experienced that the mobile data no longer connected. So I managed to install ADB and capture logcat and dmesg. Where should I supply these files to (I am running the latest nightly)?
Thanks, Christian
Just go to bugtracker.fairphone.com and navigate to the lineageos project. There you’ll find the issue re losing mobile date
1 Like
Thanks, I added my logs to https://bugtracker.fairphone.com/project/fairphone-lineageos-on-fairphone/issue/11
I just upgraded from the old OTA and everything went fine.
It’s even better, as I noticed that the call volume issue (LineageOS 14.1 with OTA updates for FP2) seems to be fixed in the official builds. I am not sure whether a reflash of the old OTA would have fixed it anyway.
Just one question: How do I change the name of the device?
Jottacloud now has my phone identified as FP2 and my girlfriends’ phone as FP2(1) and I cannot change this manually in the application/website… So I am wondering how to change the name of the device to make these names somewhat more clear.
I saw an option in the developer options, but that doesn’t seem to be the correct one.
I justed checked, a bug was already opened for this issue.
1 Like