How to Android without Google
bytemybits.gitlab.io
bytemybits.gitlab.io
I run Android without Google. I bought a new phone, and when I powered it up, it tried to get me to "sign into Google". I declined. I downloaded F-Droid. Then I disabled every Google thing that could be disabled.After that, all apps came from F-Droid. Mail is via K-9 mail and an IMAP server. Browsing is Fennec F-Droid, which is Firefox minus some unwanted Mozilla-calling stuff. Mapping is ZANavi. Location provider is Mozilla. Works fine.
I hope i'm wrong here, but as far as I can tell. You need either google services or unifiedNLP from microG to achieve that.
I say this, because I run LineageOS without Gapps and I could never make it work with Mozilla's location provider.
The lack of geolocation is the only thing bothering me to be honest.
[1] https://f-droid.org/en/packages/org.microg.nlp.backend.ichna...
As one simple issue, I'm pretty sure Android uses Google's DNS and that is hard to change.
Sorry to be vague; I wish I had more details but don't have time to look them up right now. The basic message is: It's not sufficient, depending on your goals. to rely on settings in the GUI and to avoid Google applications.
Example usage:
iptables -t nat -A OUTPUT -p tcp --dport 53 -j DNAT --to-destination 1.2.3.4
iptables -t nat -A OUTPUT -p udp --dport 53 -j DNAT --to-destination 1.2.3.4DNS66 from the fdroid store. Doesn't require root either.
I'm pretty sure it runs the DNS you specify though your ISP might mangle the packets to their own DNS (Vodafone NL used to do this and also tunnel HTTP traffic into their transparent proxy; not sure if they still do).
However this is a non-issue if you're OK running a VPN server. I use WireGuard to use my home network's Pi-Hole which applies filtering. I also get insight on data traffic from the device via DPI feature on my router. Though the WireGuard Android package isn't complete yet the good part of the story is WireGuard doesn't take many resources. When I did this with OpenVPN in the past my phone would get so hot it hurted to touch it at some spots (granted though it was in summer but still not good for battery).
RTM. From the article:
"If you read the purpose of microG you’ll understand it mainly serves as a proxy, something that still communicates with Google servers. The fact is, there is no way around that. The whole Android ecosystem is dependent of Google, either because of Google Play services or Play Store"
(Emphasis added that Google is still required with microG)
Avoiding their location services is harder but micro-g does actually support other location services backends.
Push notifications is the problem child. When people "send" you push notifications, they actually send them direct to google and rely on google to send them to you. Installing micro-g can disconnect google at your end, but not at the app vendors end. It's likely that they will do this in many cases even if your phone actually lacks the software to receive the push from google.
You have to be on nightlies for this though.
https://www.reddit.com/r/CopperheadOS/comments/77i687/microg...
Thus microG maintains its own fork of LineageOS; the microG team would need to fork Copperhead.
Rebuilding Android surely isn't that difficult (it's been on my todo list for some time, I've just never gotten around to it due to insufficient RAM).
Complete AOSP upto Oreo requires about 95GiB for just the sources + 40-50GiB for each version build.
But most of that repo history is not necessary if all you want to do is build one version. Just clone that one version to depth 1. Nougat weighed in at around 13-14GiB. Add the 40-50GiB for build, and about 70GiB is enough.
Write them a GDPR message requesting what info they have on you!
> Removed 14.1 devices > Samsung Galaxy S7 (herolte) and S7 Edge (hero2lte) due to licensing issues of the device trees
> due to licensing issues of the device trees
I believe you have knowledge their concerns are unfounded?
Well I call bullshit:
https://www.lineageos.org/Changelog-16/
As for why the device was dropped, go ask the maintainer. They're probably volunteers and it might be that one of them just stopped having time to do that. I don't think they're actually paid for porting LOS.
Because of this most people don't contribute to android ROM projects anymore. For a lot of people it just isn't worth the effort those that do care tend to keep up with new tech and buy the latest and greatest tech so they aren't maintaining old devices as much anymore unless they were major hits or a personal preference of the maintainer.
As for why a lot of features have disappeared, through the whole process of surviving the Cyanogen Inc. issues, it took everything the community had to keep basic android supported let alone all the extra features considering how many devices they support. Now that Treble has been deployed, this shouldn't be so much of an issue but maintaining so many old devices that have long been deprecated isn't easy.
Also, as for why the S7 is no longer maintained, apparently there was some bs issue with the software license on the S7 binaries.
Every off-brand android distro does the same thing: they get the kernel+drivers from the OEM image, and repackage the rest (the rest being AOSP).
besides the android libraries, nothing is visible. It is all a binary blob picked from the OEM image. So if the android version X is release by OEM, the off-brand android distros will pick up version X for that phone by just building AOSP on top of that kernel+drivers. When a new version for android comes up and it depends on a newer kernel version, that phone won't be updated no matter what! ...exception is if the phone's kernel+drivers are shared with another model that did received the update, but you guess how rare that is.
bottom line, no matter how may hours an off-brand android distro use, it will NEVER support anything newer than what is supported by the OEM.
In some cases, even if they claim they are releasing android security patch X for your phone, if that patch bundle included kernel fixes, you can be guaranteed that they will not be included.
Seems worse than Google maps to me.
This is an appeal to pity. [1]
As someone who knew Android before it was bought by Google I'd like to disagree on that one:
"In July 2005, Google acquired Android Inc. for at least $50 million." [2] Yes, Andy Rubin had money issues, but OTOH it was seen as a competitor already at that point. Some details with sources on that in [2] as well.
Furthermore, if Android did not became popular perhaps Maemo did or Symbian remained and Nokia didn't die. Who knows.
[1] https://en.wikipedia.org/wiki/Appeal_to_pity
[2] https://en.wikipedia.org/wiki/Android_(operating_system)
https://f-droid.org/app/net.osmand.plus
https://f-droid.org/app/com.github.axet.maps
https://f-droid.org/app/com.junjunguo.pocketmaps
https://f-droid.org/app/com.zoffcc.applications.zanavi
Either specify why you think Google Maps is so irreplacable or don't make such a blanket statement.
They offer an official bootloader unlock too.
I have Nokia 3 and it's perfectly OK. No thrill, just works and stays updated. Nokia 6 is $230 in the US.
Edit: Sadly it will not work with Sprint so I can't get it.
https://www.xda-developers.com/no-official-bootloader-unlock...
SIM unlock is carrier dependent if you are from the US.
If you strip away all the hype and marketing, they offer pretty solid phones.
Here are some notes on building and installing Lineage OS on the Essential PH-1:
https://headthirst.com/building-and-installing-lineageos.htm...
And some notes about setting up a phone without Google Play Services:
The only thing I am really missing is Google Maps and its precise, actual traffic augmented, predictions.
I've tried Waze, Bing and OSM, but there is always something missing.