I mean, you can still install one of the ROMs that implement a custom root-of-trust (CalyxOS, DivestOS, iodéOS … ), or build LOS yourself and sign it with your own keys, then that issue doesn’t really concern you.
My guess is, the reason for the bootloader using test keys is /e/OS, they sign their releases with test keys as well.
If Fairphone had used private keys, they would either have to share them with Murena, or sign every release themselves. With a custom root-of-trust people would get a nice yellow screen, warning them that their device is “loading a different operating system”, and customers who bought their phones from Murena might understandably get freaked out by that.
But, as mentioned in the topic you linked, having the keys doesn’t actually help you without an EDL loader / firehose files available. As long as those don’t get leaked, even a phone running stock FPOS with a locked bootloader is reasonably secure.
Following up from my post on Jan 16 about the issue with outgoing audio…
I’ve posted a logcat file on github.
As I described previously, after a reboot the person on the other end of the call will not here any outgoing audio from the FP4. Switching the FP4 to speakerphone immediately causes the outgoing audio to start working, and then it continues to work after speakerphone is witched off, and on subsequent calls, until the phone is rebooted. I have tested this with the stock phone app, and also the Google Phone app, and with bluetooth off and on.
The logcat file starts with the call being placed, and 17 seconds later, after the call connected, and the outgoing audio issue was verified, the audio is switched to speakerphone. About 22 seconds in speakerphone is switched off.
Testing now, I can’t reproduce. 20230122 nightly, MindTheGapps 13 20221025_100653. I rebooted immediately before making an outbound call, in case previous speaker use would prevent the problem from occurring. I had no problems with outbound audio. I tested this with a 3G connection, and 4G connection that seems to have used VoLTE. I can try testing with a 5G connection in a few days. I do see a 4G status, and have 4G calling on. This is on Vodafone IE.
Yes, I am in the US,. I switched from the stock OS to LOS after reading the reports in the “Fairphone owners in the US” forum in December indicating that VoLTE was working properly for phones running LOS and e/OS, and after the first official LOS build supporting FP4 was released in January.
Previously, with the stock OS, I did not have this issue with outgoing audio, but the phone was apparently using 3G (or even 2G) for voice calls.
I am using Mint (T-mobile).
Let me try disabling 5G and 4G and checking whether the issue still occurs…
I don’t know if you LOS users would see my question in the other thread. So I’m linking it here in hopes that someone might answer in the other thread. Thanks!
Hey! Just a few months later and now there is an official LineageOS 20 for FP4. I’m using it for a few weeks now and I just have some quality issues but no essentials for me.
-the NFC stops working after some time, you have to switch off/on again
-the camera is limited to 12MP
-USB headphones doesn’t work
My banking app works well which surprises me cause I read from other OS’ that safetyNet is not supported. On the other hand it seems my banking app lacks safety.
Does anyone using LOSofficial experience same issues or has a solution for mine? Your welcome to keep this thread alive!
This is not a specific LOS issue. We have been waiting for Fairphone to provide this capability for third party apps for about a year now. In the first post of Camera & Camera2 API - missing features & bugs all problems regarding third party camera apps are mentioned. E.G.:
Maybe this is the problem and Fairphone has to solve it:
This applies to stock ROM as well as all custom ROMs. CalyxOS has developed a patch that bypasses the SYSTEM_CAMERA permission check. This has also been adopted in LOS and iodéOS. Therefore, thanks to Calyx, at least the wide-angle camera now works. But all other problems seem to persist. Fairphone has unfortunately given up working on solutions for this in the meantime. Only with a lot of luck will they find the time and energy to work on it again sometime in the future:
I’ve been using LOS for a while now, and I seem to recall the FP4 being able to switch to the wifi signal automatically.
Now on LOS, this doesn’t really seem to happen unless you completely lost the weakest wifi signal.
I have a wifi repeater in my house, since the signal gets really bad upstairs, but I always have to manually switch wifi even though the wifi indicator clearly shows its weak.
Worst, when opening the wifi settings while already connected to a router, it generally takes about 30 seconds, sometimes more to display the wifi list and allow me to switch.
Now I’m not sure how this behaved on FPOS but I don’t recall this process to be that painful. Anyone else having similar issue?
Hello, I am using lineageos 20 on my fairphone 4 and I’m very happy with it.
But I bought the Fairphone 4, because of the HDMI USB C port.
Now I bought the ViewSonic TD1655 portable display with touch.
When I connect my phone with the monitor, the touch function is rotated 90°. So when I swipe left to right, it swipes top to bottom.
If I choose desktop mode in developer options it works fine. However, I think the standard environment is perfect for me. maybe that can be changed?
@rca I can report that I’m having the same issue on my brand new FP4 using lineage. My first call, yesterday, was using my BT integrated car audio system and it worked fine – so I thought I wasn’t having the issue. However, this morning I made a call with my handset and the person receiving the call couldn’t hear anything. Toggling the speaker phone setting worked, just as you reported. I’ll add a comment to your bug report. Hopefully an extra comment will generate some developer interest.
@2allseew Thanks for sharing that info here and also for commenting on the bug report. I’m sorry to hear that you’re also having the problem, but also relieved that I’m not alone and hopeful that additional reports will increase the visibility of the issue and the likelihood that it gets attention and gets fixed soon, as you said.
Hi, do you guys know how the install of Lineage for microG from lineage.microg.org works? I always did it like the normal lineage install but now I found a boot image in the folder for the fairphone and there is no description how that’s supposed to be used
You don’t really need to use the boot image, unless you want to patch it with Magisk for rooting. In a new Lineage or (Lineage for Microg) installation, all you really need are the main zip and the recovery zip. The basic installation steps are the same for both Lineage and Lineage for Microg. Where they differ are people installing Lineage may also plan to install Gapps.
I’m running Lineage OS for Microg which uses the Lineage OS code. I’m currently running a Lineage 4 Microg rom that was built on March 8th, 2023. That build has the February 5th Android security updates and the January 5th FP vendor security updates.
