Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Progress on /e/, the de-Googled Android fork

itsfoss.com

Post reply on HN
Print view View original

41–49 of 49 posts

Re: Progress on /e/, the de-Googled Android fork

#41

Post by lucideer »

_bxg1 wrote: post #32

> we replace with a software layout called microG that can still receive push notifications and have geolocation data for apps (using Mozilla geolocation service) It's good that they set up microG for you; that's one of the hurdles with using Lineage this way. I'm very curious about their Maps app. That was one of the very biggest problems when I tried to use Google-free Android a couple years ago. The open-source op…

> the name "/e/" is terrible. Hard to search for, hard to meaningfully verbalize, hard to interpret.

I think I read somewhere that this is a deliberately-obscure temporary codename pre-proper-branding, during initial unstable development.

That said, they've used it a lot in their branding, so I'm not sure...

Re: Progress on /e/, the de-Googled Android fork

#42

Post by lucideer »

lucideer wrote: post #41
_bxg1 wrote: post #32

> we replace with a software layout called microG that can still receive push notifications and have geolocation data for apps (using Mozilla geolocation service) It's good that they set up microG for you; that's one of the hurdles with using Lineage this way. I'm very curious about their Maps app. That was one of the very biggest problems when I tried to use Google-free Android a couple years ago. The open-source op…

> the name "/e/" is terrible. Hard to search for, hard to meaningfully verbalize, hard to interpret. I think I read somewhere that this is a deliberately-obscure temporary codename pre-proper-branding, during initial unstable development. That said, they've used it a lot in their branding, so I'm not sure...

Update: From their FAQ page[0]:

> Why this weird, inconvenient /e/ name?

> ...

> It’s the current project codename, we will probably introduce a new and more convenient name for our mobile ROM in few months.

https://e.foundation/get-support/#faq

Re: Progress on /e/, the de-Googled Android fork

#43

Post by tracker1 »

monocasa wrote: post #25
ryukafalz wrote: post #23

Earlier quoted context omitted.

It does on Linux, where there's no stable ABI for drivers to use, right? Yes, that's a design decision on Linux's part, but it's one that seems to be working out just fine for PCs.

But that's less than 10% of the market. The rest doesn't have those problems either, despite having almost entirely proprietary drivers. Therefore it's not the propreitary drivers that are the issue.

The market is smart phones, where the market share for a linux kernel (android) is much higher.

Re: Progress on /e/, the de-Googled Android fork

#44

Post by tracker1 »

doublerabbit wrote: post #34
nekopa wrote: post #33

Earlier quoted context omitted.

Maybe because your comment didn't mention anything specific to prove wrong. Just saying Capitalism and Reasons doesn't mean anything. Could I just say "Communism" and thereby prove you wrong?

> And reasons that Google/Apple want you locked to their operating system, their hardware. Well, do they not? Locking you to their product, forcing you to use their product for their own gain. Apple won't even let you repair your phone unless you go via their own dealers. You could call communism, but there isn't any communism element to it. It's all capitalism to answer OP's question to "Why can't I install any oper…

Capitalism + IP Protectionist policy would be more apt a description. But this isn't any more or less capitalism than say Capitalism + Social welfare programs are Marxism or Socialism.

Personally, I'm hoping that some states grow a pair and actually pass meaningful right to repair legislation, then a lot of things will tumble. There are plenty of Libertarian and Capitalist supporters who do not like the corporatist status quo. That doesn't mean that Capitalism itself is the issue.

If it weren't for IP protections, there would be more interoperability most likely, or better service/support. Sharing communication breaks, and offering run-alike chip and interface replacements would be less of an issue. Not to mention, it's Corporatist IP protections that keep out competitive upstarts.

Also, Apple happens to make most of their devices in a Communist country, so how does that stand?

Re: Progress on /e/, the de-Googled Android fork

#45

Post by imnothere__ »

As other user replied and to extend it, /e/ is a rebranded LineageOS with microG integrated plus some small commits.

Also, it uses a Nextcloud fork which isn't even open source as a replacement for Google cloud service, and same as another reply, why trust /e/ over Google?

As that it's mostly stolen work in some sorts(Earn money with OSS devs effort? Seriously what a disgrace.), instead, please support LineageOS for microG[1]

[1] https://lineage.microg.org/

Re: Progress on /e/, the de-Googled Android fork

#46

Post by im3w1l »

imnothere__ wrote: post #45

As other user replied and to extend it, /e/ is a rebranded LineageOS with microG integrated plus some small commits. Also, it uses a Nextcloud fork which isn't even open source as a replacement for Google cloud service, and same as another reply, why trust /e/ over Google? As that it's mostly stolen work in some sorts(Earn money with OSS devs effort? Seriously what a disgrace.), instead, please support LineageOS for…

Last time I checked all phones with lineageos support were made by Google, China or were like 5 years old. For this reason I never got it.
Post reply on HN