De-Googling LineageOS 18.1

I was looking up some information about Privacy Guard and came across this article from May this year. Searched the forum but didn’t see it already mentioned.

De-Googling LineageOS 18.1

Standard but nice set of things to do on LOS to, and I quote, “If you follow the steps below on a vanilla LineageOS 18.1 without MicroG, you will achieve feature parity with /e/OS. Check out their whitepaper regarding details.”


Disclaimer for the anti-rootists (*): Showcases root and root apps.

(*) j/k. :stuck_out_tongue_winking_eye:


thanks @marcdw … can you post the link to the article from which that quote was taken & with those steps? Right now your OP only has a link to the /e/OS product description page. :nerd_face:

edit: I can see it here; I guess this is the one? :thinking:


I read the tips and it looks like they would mostly work with rooted debugging, as most of the work is done using adb. So no need to root the phone with Magisk. I’ll do some more digging on my LOS devices

Oh, I am so sorry. I was sure I linked the article but that was elsewhere.
Fixed. Thanks.

1 Like

Reminder: @kisman172 said: So a lineage is also Google-free and uses microG services.

°Lineage for microG

°Google services that are still being requested. In contrast to  /e/OS:
Captive Portal

°Switch NTP:
adb shell settings put global ntp_server [](

°Switch DNS
adb shell settings put global captive_portal_http_url “[ ](”
adb shell settings put global captive_portal_https_url “[](”
adb shell settings put global captive_portal_fallback_url “[ ](”
adb shell settings put global captive_portal_other_fallback_urls “[ ](”

°Switch DNS
°Settings/Network/Advanced/Private DNS
[ ](

°Freely translated by author

Worth reading the guide that @Manoj linked to, about what calls to Google servers exist in /e/, why they are needed, and what data is removed before they are made.


This topic was automatically closed after 30 days. New replies are no longer allowed.