Thanks for all your answers. Seems mostly like the difference is in the details of the code (/e/ does seem to have advantages, privacy-wise) and in terms of a simpler day to day use. The difference that /e/ comes with microG seems to not really be a difference at all anymore, since there are Lineage builds including it by now. If undestand it correctly at least.
I guess, if by the end of the week there is no update for /e/ I’ll do the switch, even though I’m not really partial towards setting up the whole OS from the top. With a TWRP backup I could probably switch back, when they resolved thier inner disputing about the COVID-API (which to me seems pretty ridiculus tbh and is starting to make me question this whole project…)
I tried /e/, lineageos and stock rom and hope that I can give some advice here.
I am a really privacy-focussed user (e.g. I would not consider installing a contract tracing app), but still /e/ was too much for me. It strictly blocks nearly all of the google services and many apps did not run on my device. Also, you can only install free apps, and not the ad-free Pro versions you might have bought. So if you go for /e/, the idea is basically to install it and then see which apps are working on it.
Stock rom ovbiously works out of the box and you can run any app on it, but also gives you less flexibility e.g. on how much data you want to share with Google.
If you are willing to try to install Lineageos, you might consider using it with Open GApps Pico rather than MicroG. This way, you get a slim version of the original Google Play services, all Apps are working on your device (jncluding paid ones), but you still have the customizability of Lineageos.
If the LOS installation fails, you should be able to switch back to stock rom fairly easily.
TBH, the now established contact tracing technology (DP-3T) is decentralized and probably one of the most privacy-focussed apps you could install. Except for countries like France and some others that somehow still rely on a centralized technology which works much less reliable and is much less privacy preserving…
And if you - as a privacy concerned user -
this is probably a much higher risk in this regard.
BTW: MicroG has already implemented the Exposure Notification API. So there’s no more need to install the Google Services in regard of using this technology
I am really fine with microG and also really liked /e/, despite the limitations. Don’t really need GApps
One quick question. I guess the install instructions are assuming, one comes from stock rom. Would it be about the same when I come from /e/OS?
Edit: And… Is this instruction to install Magisk also working for LOS? /e/ for FP3 (Google free OS) (I know I don’t really need it but I’m kinda curious)
I think whether you come from /e/OS or from another ROM shouldn’t change anything. You might want to install the stock OS before switching to LOS just to be sure, but I don’t think it matters much. Someone else may have a better advice than me though.
The instructions to install magisk given on the /e/ thread work for the /e/ recovery, which obviously you don’t have under LOS, so it’ll be through TWRP instead. Why don’t you just follow the official instructions?
I asked about Magisk, because trying to install it with the instructions from your link caused a system failure in /e/. Also, /e/ actually uses Lineage recovery. But if it works the normal way under LOS, I will try that.
I can confirm, that the install works like a charm coming from /e/ and installing Magsik, as well as updating microG to include the exposure notification API worked like a charm.
Now got some work to do setting up the phone. Yay… First impression is that the whole interface of LOS seems more appealing and “rounded” that that of /e/. However, Google does make it’s presence known fairly quickly, of course not as effectively as in the stock ROM.
Sorry if I ask a question which has already been answered and that I am just not aware of (because of the 288 posts in this thread). In this case please point me to the right posting.
is there any progress and/or an ETA for official ROM? Will it be possible to change to official from the unofficial version without data loss?
Thanks.
The post is one month old, maybe there was made some progress in between.
But maybe it is not that important, maybe it is more important whether an update to the (hopefully) official LOS will work without data loss.
I am in the same position as other people here: I have been using /e/ but due to their strange politics regarding microG I temporarily switched back to Stock. Now I have found out that there is a native LOS for FP3, but I don’t want to configure my phone five times until I have found one ROM which I can use for the next few months…
Hi Juri,
the review process took much longer than expected, but I expect the release to be available in 1-2 weeks. I also expect that you will be able to migrate user data pain- and losslessly between unofficial and official LineageOS ROMs.
I cannot guarantee support for FP3+ yet, since I don’t know if and how I will get the necessary information needed for a building our kernel and using proprietary vendor code. You might want to ask the /e/ developers for their plans as well.
According to @Alex.A FP3+ should run with your LOS 16 too, since the core architecture should be the same. I guess the new parts like the better camera should make no problems. Can you confirm that?
You only cannot guarantee the support of LOS 17.1 for FP3+, your LOS 16 should work for it out of the box, right?
LOS will run on the core-module of a FP3+. But it has to be adapted for the new camera modules and speaker, whether it is a FP3+ or a FP3 with the new modules, in the same way as /e/ can’t run with the new camera modules for the moment (though it is scheduled for end october).
Edit: I think I omitted this when answering you the first time…
In case anyone’s wondering: updating MicroG seperately from 0.2.11 to 0.2.12 via the APK provided on their website works like a charm. I’m running the 20200818 build of LOS and was missing Exposure Notifications functionality (for Covid apps), got it fixed with this update
I finally got the time to try the ROM. Thanks to all people involved! It works great so far. Just some remarks from my experience:
I were not able to get swipe typing going using the libraries, e.g. from shadow53. That is less of a problem as there are other cool swipe keyboards out there.
If you use microG and a Google compatible store like Aurora Store, take care so you don’t accidentally update their (=Google’s) gsmCore onto your system…
