Since some users reported to have problems with their banking apps after installing open Gapps with magisk, I decided to go for the disable-verity solution with a non-rooted LOS. I can say that ALL of my banking- and similar apps are working perfectly fine. I am an experienced user of LOS on a variety of devices (with root and without root) and know which of my apps are the typical ‘troublemakers’. NONE of these apps had any problems when installing open Gapps with the disable-verity solution. I would therefore recommend to anyone planning to use this LOS with open Gapps to FIRST try the disable-verity solution and only if this does not work go for the magisk solution (except if you want to root your phone anyway).
In case you wonder how to use the disable-verity solution: Install the SDK Platform tools on your PC (minimal adb/fastboot is not enough) and then perform the commands
adb disable-verity
adb reboot ‘dm-verity enforcing’
from your PC directly after installing open Gapps, while your phone is still in TWRP.
I made sure that my phone was NOT rooted (I even flashed Magisk uninstaller to be on the safe side). Also, some banking apps check if developer options are enabled and do not work if this is the case. Therefore, I would always recommend to disable developer options when installing one of these picky apps.
Please note that there is a reason why many banks make sure that their apps can only be run on ‘secure’ phones, so perform any of these steps on your own risk!
If other users can confirm my experiences, it might make sense to update the open Gapps instructions in the introduction text.
@Max_S, @dk1978 and all other who helped to make this possible: and a very big thank you for your dedication.
I received my FP3 (needed after my FP2 was lost-in-space) and immediately followed the instructions to install LO16 on it.
It’s my first time with a phone that has these A/B slots and a locked bootloader. So I have some questions:
My situation is, if I followed well, as follows:
bootloader is unlocked.
FP16 flashed to slot A
TWRP installed on the system
What I now notice, is that the message about the phone about the bootloader being unlocked and the phone being vulnerable appears every time.
When I lock the bootloader, the bootup sequence doesn’t get beyong this message it seems. However, at that time it seem that system was booting from slot B (containing the stock FPOS?) and with TWRP installed. So I’m not clear whether that was the problem (TWRP cannot be used with the stock FPOS) or the fact that the bootloader was locked again.
I now have some questions:
is the requirement to unlock the bootloader needed until the build is done through the lineageos build system (which will then sign it) ?
do we really need to keep the bootloader unlocked at the moment ?
does it harm to have TWRP installed ? I later read that it’s not really needed to install it.
unlocking the bootloader wipes the data partition. Will that be a requirement for every install until OTA updates work ? If so, is the procedure explained in [ROM][UNOFFICIAL] LineageOS 16.0 for FP3 (user-data dance) the one to use in order to prevent loss of the user data ?
I’m a bit hesitation to fully configure the phone if I would have to redo that on every update.
Hi folks, I just wanted to ask if there is a way to see the progress of the audit by the lineage devs? I’m really curious how fast we can expect FP3 do be supported officially.
Same here. I have been following this thread for a while and can’t wait for the official release. @Max_S and @dk1978 can you tell how far the progress is?
I can confirm that all my banking apps are working with LOS and Open Gapps. I installed LOS and Open Gapps via ADB sideload and then used the commands suggested by Parkhaus while still being in TWRP. I can also confirm that Android Auto is working flawlessly with LOS.
The review process is tracked on Gitlab but does not appear to be publicly viewable, perhaps for good reasons. At the moment we have been tasked with cleaning up the project’s commit history and fix some odd settings.
What camera app are people using on their FP3 with LineageOS?
In my case the standard LineageOS camera app produces very noisy images when lighting conditions are not perfect, same for OpenCamera. I managed to overcome this issue by installing one of the GoogleCamera ports, in particular this one: cstark27’s PXv4.5_GoogleCamera_7.2.014, since an earlier version of it was recommended in the camera app thread here on this forum.
For those that are interested, I wrote a small blog-post on how to reduce the presence of Google on my FairPhone using this LineageOS build (thanks again for the efforts!). It might contain some useful app-tips for some of you new to these topics, but is maybe less of interest that are familiar with this already. Anyway, here it is: https://nnk.tweakblogs.net/blog/19000/a-practical-guide-on-de-googling-your-phone
Maybe for some people interesting, that also that custom Rom does not support the FP3+ camera and speaker (yet). Somehow, I was assuming, that it would be possible to get an alternative OS for the FP3+.
due to /e/'s strange delaying in updating microG to include the exposure notification framework and thus preventing users to use the Corona-Apps, I am considering switching to this Lineage rom, where apparently microG can just be updated by the user. (Now that’s what I consider “owning my data”)
However, as I am just recently discovering Android (coming from many years of using iOS) I am unsure as to what I will have to expect from LineageOS. I sometimes hear, it is more difficult to use than /e/, however I am not sure, why this would be the case.
Can someone maybe enlighten me about the differences between /e/ and lineage and what would make the use of one more difficult than the other?
Probably the difference making/e/ “easier” is the installer and more infrastructure (like e.mail and so on). as you already noticed LOS apparently gives you more flexibility and this might be considered more complicated. After installation and setup, i don’t think one is “easier” than the other, but that’s my personal opinion with not much (and ancient) /e/ experience.
Btw, I’m running this rom with opengapps and (the German) covid app just fine
In my opinion the “easiness” of /e/ compared to LOS is based on
comes with microG automatically
comes with an app store automatically
comes with more/better (probably depending on personal taste) default apps
if you use an /e/ account it automatically syncs things like pictures (also from old device to new one IIRC) so you don’t need to put them on your PC manually (they are also working to integrate a backup solution that’s as easy as the google drive cloud backup)
Most of that can be done by the user with LOS but some people wouldn’t know they have to do that when they wish to change to an alternative OS. And they would wonder why so much things “don’t work” (as expected naively).
Edit: the installer is very new, it might become something that makes /e/ more easy than LOS but at the moment it only supports around 10% of the phones generally supported by /e/ (and still is beta or even alpha)
and a very big thank you for your dedication.
.