Conversation
Notices
-
@danipozo lineage-microg ftw
-
@danipozo That's probably still easier with Lineage-MicroG than with LineageOS proper.
-
@danipozo The summary of the thread (I haven't read anything except the initial post and the summary) is pretty disheartening:
https://www.reddit.com/r/LineageOS/comments/83wqdp/project_fi_and_gapps_inside_lineageos/dvuo8m7/
Sounds like the free and non-free parts of Android are more intertwined than ever, and that Google is leveraging attractive apps to argue for intrusive core modules. No news there, but it's really challenging Hanlon's Razor and looking more nefarious than just cavalier.
https://fi.google.com/ looks like a really smart move from Google to further secure their grip around the consumer/product.
Multi-network roaming at home, same-price roaming abroad. It's like a dream come true. But apparently it comes with strong strings attached.
-
@danipozo Sounds like the heart of the thing is:
1) LineageOS is made with the expectation that most people would run the Gapps package on it (and most people do).
2) Gapps is (mostly?) device-independent.
3) Anything Gapps needs to function that is device-dependent will be included in LineageOS for that device.
4) They are not interested in putting in the additional effort so modularize this further.
So it really sounds like people interested in Android without Google need to go full Replicant now.
-
@clacke @danipozo Now if only Replicant would attract more developers and support more devices... IIRC it still requires third-party Wi-Fi dongles in order to avoid using binary blobs.
I'm afraid postmarkedOS might be the more viable solution, at least in the long run.
-
@hfaust @danipozo Yes, but the wedging seems more intense than ever. As it always does, I suppose. It won't go back.
-
@hfaust @danipozo Yes.
-
@danipozo Yeah, seems the balanced direction to go.