Progress on /e/, the de-Googled Android fork
itsfoss.com
Progress on /e/, the de-Googled Android fork
1–10 of 49 posts
Re: Progress on /e/, the de-Googled Android fork
#2> the/e/ name will be abandonned for something else quite soon.
Good to know; a word that's more easily duckduckgoable may help with branding.
Re: Progress on /e/, the de-Googled Android fork
#3> the/e/ name will be abandonned for something else quite soon. Good to know; a word that's more easily duckduckgoable may help with branding.
Wanted to comment on the name too.. slash-e-slash???
Re: Progress on /e/, the de-Googled Android fork
#4> the/e/ name will be abandonned for something else quite soon. Good to know; a word that's more easily duckduckgoable may help with branding.
It's a very funny and perhaps unfortunate from the perspective of 4chan users.
Re: Progress on /e/, the de-Googled Android fork
#5Are these de-Googlification changes going to be upstreamed into LineageOS?
Re: Progress on /e/, the de-Googled Android fork
#6> We are also announcing this week an “/e/ easy installer” that will make the flashing process much more easier, by pluging the smartphone to a PC and launching a dedicated application that will make most of the job.
Why do phones require device-specific builds and ROM flashing just to install a different OS? Why isn't there a phone out there with a normal boot loader that allows me to install whatever OS I want like I can on a PC?
I have a perfectly good phone, but I know I'm going to have to buy a new one eventually just because the manufacturer will stop supporting the hardware. Meanwhile, I have decades-old PCs that are running just fine.
Privacy is important. Removing Google from the picture is great. But I don't see this, LineageOS, or anything else taking off until we have a more accessible solution for installing mobile operating systems. An application that streamlines the flashing process is nice, but I don't think that's enough.
Re: Progress on /e/, the de-Googled Android fork
#7Direct link (since it's not easy to find in the article):
Re: Progress on /e/, the de-Googled Android fork
#8> We are also announcing this week an “/e/ easy installer” that will make the flashing process much more easier, by pluging the smartphone to a PC and launching a dedicated application that will make most of the job. Why do phones require device-specific builds and ROM flashing just to install a different OS? Why isn't there a phone out there with a normal boot loader that allows me to install whatever OS I want like…
>Why do phones require device-specific builds and ROM flashing just to install a different OS?
Capitalism. And reasons that Google/Apple want you locked to their operating system, their hardware.
Prove me wrong.
Re: Progress on /e/, the de-Googled Android fork
#9> We are also announcing this week an “/e/ easy installer” that will make the flashing process much more easier, by pluging the smartphone to a PC and launching a dedicated application that will make most of the job. Why do phones require device-specific builds and ROM flashing just to install a different OS? Why isn't there a phone out there with a normal boot loader that allows me to install whatever OS I want like…
The problem's not the bootloader (pretty much all Android kernels use the same bootloader format), it's that the hardware introspectable by software, and the device tree passed in to make up for that isn't designed to be used by anybody other than the OEM in the first place.
It's like the days of when Linux didnt support ACPI well, but now everything is behind ACPI tables instead of PCI config space.
Re: Progress on /e/, the de-Googled Android fork
#10Um... so how are they making money if we are not the product?