> 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.
> 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?
A few reasons:
1. Proprietary drivers are the norm for mobile devices, whereas (with a few exceptions) this is not the case for desktops/laptops.
2. Even when the drivers are free, standard practice among device manufacturers seems to be forking the kernel for each device and working off that fork. These things don’t and can’t run on mainline Linux/Android.
See the Librem 5 and PinePhone for what are probably the only two devices attempting to fix the above problems. And even if you fixed those:
3. ARM devices typically don’t have the same device enumeration capabilities as x86 PCs, meaning you need a separate device tree for each one. I believe there are also efforts underway to improve this situation, but that’s where we are at the moment.
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.
> 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 options at the time were bad. If they've made a decent alternative, that would truly be a game-changer.
One other random thought: the name "/e/" is terrible. Hard to search for, hard to meaningfully verbalize, hard to interpret.
Some osm apps have good navigation, but they don't have the same data, e.g. on traffic. 'Here' isn't bad. And in doubt there's always Google maps by browser.
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]
Binary blobs dont have trackers and snoops? Phones have FPGA and need binary blobs. Certified RF segments for regulatory permitted operation in the mobile telephony world.
[+] [-] CivBase|6 years ago|reply
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.
[+] [-] ac29|6 years ago|reply
Unlocked bootloaders aren't terribly common though outside of Google's devices.
[+] [-] ryukafalz|6 years ago|reply
A few reasons:
1. Proprietary drivers are the norm for mobile devices, whereas (with a few exceptions) this is not the case for desktops/laptops.
2. Even when the drivers are free, standard practice among device manufacturers seems to be forking the kernel for each device and working off that fork. These things don’t and can’t run on mainline Linux/Android.
See the Librem 5 and PinePhone for what are probably the only two devices attempting to fix the above problems. And even if you fixed those:
3. ARM devices typically don’t have the same device enumeration capabilities as x86 PCs, meaning you need a separate device tree for each one. I believe there are also efforts underway to improve this situation, but that’s where we are at the moment.
[+] [-] monocasa|6 years ago|reply
It's like the days of when Linux didnt support ACPI well, but now everything is behind ACPI tables instead of PCI config space.
[+] [-] doublerabbit|6 years ago|reply
Capitalism. And reasons that Google/Apple want you locked to their operating system, their hardware.
Prove me wrong.
[+] [-] _bxg1|6 years ago|reply
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 options at the time were bad. If they've made a decent alternative, that would truly be a game-changer.
One other random thought: the name "/e/" is terrible. Hard to search for, hard to meaningfully verbalize, hard to interpret.
[+] [-] lucideer|6 years ago|reply
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...
[+] [-] pergadad|6 years ago|reply
[+] [-] imnothere__|6 years ago|reply
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/
[+] [-] im3w1l|6 years ago|reply
[+] [-] petecox|6 years ago|reply
Good to know; a word that's more easily duckduckgoable may help with branding.
[+] [-] jfax|6 years ago|reply
[+] [-] thiht|6 years ago|reply
Not a thing.
Duckable might be better?
[+] [-] netsharc|6 years ago|reply
[+] [-] ghgr|6 years ago|reply
https://e.foundation/
[+] [-] BuildTheRobots|6 years ago|reply
> ensure that you have an /e/ account (for /e/ online services such as mail, drive, calendar…). You can register for a free /e/ acount here
right - and I should trust E over Google why?
https://doc.e.foundation/devices/
[+] [-] mqus|6 years ago|reply
[+] [-] jmakov|6 years ago|reply
[+] [-] timbit42|6 years ago|reply
[+] [-] terrycody|6 years ago|reply
[+] [-] DonCopal|6 years ago|reply
https://www.kickstarter.com/projects/volla/volla-phone-desig...
[+] [-] throwaway9d0291|6 years ago|reply
[+] [-] lern_too_spel|6 years ago|reply
[+] [-] ggm|6 years ago|reply
What about the TPM and keystore?