13 ms·
One of the things that feels a bit problematic here - the webpage is avoiding mention of the fact that this is still Android. In essence, this is still Google's
by izacus 6y ago
One of the things that feels a bit problematic here - the webpage is avoiding mention of the fact that this is still Android. In essence, this is still Google's OS and the team has decided to start a fight against Google by taking their opensource and perpetually fight against the main developer by removing their proprietary component.
I don't think this is a fight that's sustainable - a giant graveyard of Android privacy forks shows that. In the end, the major contributor to this OS is and will remain Google.
In that respect, Purism's PureOS seems like a more sustainable effort.
- GTP 6y agoWhat about LineageOS + MicroG? It seems sustainable to me
- izacus 6y agoLineageOS has sadly been falling behind on device support these days, not sure what's going on there. :/
- nobodywasishere 6y agoWhat do you mean? LineageOS currently supports 164 devices, and LineageOS 17.1 was released a few months ago with 75%[0] of devices moved over to it currently. LineageOS 18.0 is in the works as well [1]. [0] https://docs.google.com/spreadsheets/u/0/d/1bx6RvTCEGn5zA06lW_uZGZ_dq6qQyCZC_NifmyeC1lM/htmlview# https://docs.google.com/spreadsheets/u/0/d/1bx6RvTCEGn5zA06l... [1] https://redd.it/jueya4 https://redd.it/jueya4
- joecool1029 6y agoLineageOS does not support MicroG officially, you will not receive support from them so I don't know what your benchmark for sustainability is. The officially stated reason (I'm paraphrasing) was because it allows for fudging the signatures of apps and services on the OS, and this breaks the security model.
- GTP 6y agoBut I think that in case something isn't working you would get support from MicroG, or not?
- resoluteteeth 6y ago> One of the things that feels a bit problematic here - the webpage is avoiding mention of the fact that this is still Android. I think they legally can't call it "Android" in this case so it's not really their fault that they aren't mentioning this.
- swiley 6y agoThis was the conclusion I came to after using android 4-5 for a while. Android is not designed for the community to be hacking on it. While these projects occasionally appear they don't last because of the incredible amount of work required to maintain them. You're much better off finding a normal Linux distro/phone pair that can make phone calls etc.
- speeder 6y agoJust bought a KaiOS phone, waiting for it to arrive, I will see how it will behave.
- phh 6y agoNowadays I single-handledly (well almost, I do have some contributors, thanks to them) maintain a pure unmodified Android that works on hundreds (probably thousands) of different devices. It has become a lot easier thanks to Project Treble.
- ignoramous 6y agoHi phh, Doesn't the DRM stop working once the bootloader is unlocked? That'd be a big concern since most streaming apps would refuse to install or work in that case. What other such changes is Google pushing into Android that discourages unlocking the bootloader / rooting?
- ForHackernews 6y agoI guess it depends where your priorities lie, but this effort seems _more_ sustainable to me because it can run most proprietary android apps, and everything on F-Droid right out of the box. PureOS has to try and reimplement an entire mobile app ecosystem just to get to parity with existing competitors.
- fsflover 6y agoPureOS is trying to use desktop apps instead and fit them to the phone screen ("convergence"). I think it is a viable strategy.
- Wowfunhappy 6y agoThe thing is, there aren't any desktop apps—much less Linux desktop apps—for the types of things I need to do on my phone. On an Android phone, I can buy train tickets (NJTransit), deposit checks (Chase), and have telemedecine appointments with my doctor (MyChart). I don't know if all of these would work in e.foundation, but presumably at least some would run.
- fsflover 6y agoThis may indeed be a problem. Perhaps one can use webapps for some of those use cases.
- Wowfunhappy 6y agoUnfortunately, I chose all of those examples explicitly because they can't be done on the web—they can't be done on a desktop device at all! :( The telemedecine app is a big one I think about. I don't know what I would have done if I hadn't had a modern iOS or Android device when the pandemic hit in March, and my doctor appointments suddenly moved to this remote system.
- zozbot234 6y ago> I don't know if all of these would work in e.foundation, but presumably at least some would run. Custom AOSP apps can be supported via Anbox on upstream linux.
- phh 6y agoI don't think the graveyard of Android privacy forks is that big? All I can think of is CopperheadOS which died because it was company-backed. You could argue CyanogenMod died, though really it's still well alive in LineageOS. (and CyanogenMod wasn't really privacy-focused) I have a very high respect for all the work that's been done on the various GNU/Linux mobile distributions, but it's still so far away from Android wrt usability... I agree there is something weird about fighting Google with Android, but still it makes perfect sense. From a business or engineering PoV, you want best features for the fastest MVP. Android gives you just that. Actually it goes way beyond, /e/ didn't do much of engineering, they mostly re-used what's done by the Android FLOSS community. (Honestly I don't really like /e/ because they basically don't give anything back to the community but well). If /e/ is ever successful, they can hire many engineers to actually fork Android to have their own. That's what Android did for Linux in the first place anyway! Most OEMs have a lot of changes to their Android, even though they keep using Google apps, and they are just fine. I'm pretty sure that Samsung have an order of magnitude more changes in Android than LineageOS (which /e/ is a pretty direct fork of), and they maintain it just fine.
- rst 6y agoThe original developer of CopperheadOS is continuing the work as GrapheneOS, after a split with his former business partner, over dilutions of the privacy guarantees, among other things. https://grapheneos.org/ https://grapheneos.org/
- vdfs 6y agoAlways feels like treading google for some other random developers
- SubzeroCarnage 6y ago> random developers Micay, of GrapheneOS and original creator of CopperheadOS, is not some random. They have pushed AOSP security ahead and have made many upstream contributions over the years.
- vdddv 6y ago"Since our OS runs on a totally deGoogled Android" Was that added to their site after you wrote your comment?
- megaraid999 6y agohttps://doc.e.foundation/what-s-e https://doc.e.foundation/what-s-e I think the effort is very good. The result is excellent and it's really addressing a much bigger audience that PureOS.
- javierseballos 6y agoExcept the fact that the result is VERY bad, you are right :)
- dheera 6y agoOn the other hand by being Android you get to run all the Android apps out there. What I seek in a phone is control over my privacy, not necessarily a vegan FOSS system. What that means is things like: - Fine-grained control of permissions to apps (e.g. access to rear camera only, access to only city-level accuracy of locations, access to read from only directories I specify) - For apps that insist on having permissions to things like location and wi-fi scans to use them, the ability to make the app think it got said permissions, but receives fake data. And no, Android's mock location feature doesn't work, because apps can check if the feature is enabled or not - The ability to fake IMEI, phone number, contact list, installed apps, and other identifying data - Ability to generate fake IMU, proximity, temperature, barometer, and all other sensor data that could conceivably be used for fingerprinting
- higerordermap 6y agoLineageOS is both more successful and more practical than Purism thingies.