I set it to 1G now and running for nearly 11 days just fine. Regarding my tests and your experience I’d say between 1G and 2G is the optimal value. Next reboot will try 1.5G
1 Like
Is there any news or any development at all regarding the NFC reader? I’m still unable to use it on the FP3+, neither reading my ID card nor using the phone for payments work.
I would ask you to open an issue on the official LOS site, link in the forum header. If the NFC reader works on the stock OS or /e/ then we will likely solve this.
Thank you for this information. I have long wondered why the app won’t work on LOS, this rootbeer seems to be a bit of a pest.
I don’t know if it works in /e/, but it works on iodé 2.1 (based on A11). At least I can use my yubikey via NFC for encrypting mails.
Done, see here: Unable to use NFC interface (#4132) · Issues · LineageOS / issues / android · GitLab
I’m also starting to get warning messages about having a rooted device, although I’ve never rooted this particular device. I installed LineageOS, OpenGApps pico, and relocked the bootloader. E.g., the official german Corona notification app complains about root.
1 Like
I assume the App detects a custom ROM and just names it incorrectly as root…however there is a fork available in F-Droid which should work Corona Contact Tracing Germany | F-Droid - Free and Open Source Android App Repository
1 Like
Also, i opened an issue on cwa’s git repo asking to be able to acknowledge the message for good which resulted in a feature request from the team itself. So, it may be able to deactivate that popup in the near future
Thanks, but at least for me personally, the false positive root detections are not really an issue. I just mentioned them to give an additional data point for the discussion of the issue above.
1 Like
Hi together,
some posts above I complained about wifi-crashes which happen all the time while I am connected. I think I found out the reason for that.
It seems to have something to do with 5 GHz. If I disable my 5GHz wifi with the same SSID, the crashes do not happen any more. If I rename the 5GHz band to a seperate SSID, I can’t connect to that network - only to the 2.4GHz one.
That’s a bit odd,
- does it show
- what frequency band do you have the phone set to?
Settings > Network and Internet > Wi-Fi >Wi-Fi preferences > Advanced > Wi-Fi frequency band
Sorry my Settings are for default A10
Factory reset. Huge difference. Phone is responsive. Guess something went wrong during the last major LOS update. Happy to finally have this issue resolved.
3 Likes
Finally took some time to upgrade from LOS17 with locked bootloader. No data loss, everything went great, thanks devs! 
Question: does Galileo GNSS work for anybody here?
When using Gpstest, I see Galileo sats listed but never get a C/N0 for them, but do get values for the other sats (GPS. GLONASS, BeiDou)
I did notice the same on LOS17.1 just before upgrading. Couldn’t find any LOS bugs about GNSS or Galileo.
Latest update: has anyone’s torch started to flicker when on via the notification shade? Only noticed it recently so may have been an older issue
Update: I think this was fixed by changing the performance from the middle option to high
Anyone happen to use the ProtonVPN app?
I noticed the app is not visible in the android VPN settings, and therefore I cannot enable its killswitch. But using a different vpn app like ‘OpenVPN for Android’ and ‘OpenVPN Connect’ are actually showing up in the VPN settings. No sure if this is a ProtonVPN bug or LOS bug.
ProtonVPN user on LineageOS 18.1 here (!Not Fairphone 3/3+, but Samsung Galaxy S5!):
I see ProtonVPN in the android settings and I would be able to enable the kill switch.
Seems that it might be connected to the LineageOS build for Fairphone or how you’ve installed the app itself.
Thank you for the reply. I tried the official .apk, fdroid version and Aurora store version, but no luck. I’ll guess for now I’ll stick to the OpenVPN app.
Upgraded to latest version. Now all my launcher shortcuts are gone and I can’t add new ones!
This has happened before. My factory reset solved that too, but I don’t want to do that again…