Its the lack of openness and standards on hardware, drivers, and boot sequence for ARM chipsets and phone hardware that’s the problem. x86/x86_64 hardware had standards that the industry settled on so the Linux adoption was fairly quick, with phone hardware, every phone, android kernel, camera hardware and driver, display hardware and driver, etc is slightly different so the hardware is so hard to adopt when literally every device has to be blackbox reverse engineered because the hardware manufacturers don’t make anything open or standard.
Well then ya have a chicken and egg problem, if hardware manufacturers don’t care to do things ‘correctly’ because of lack of interest in Linux adoption, but there’s no Linux adoption because of the lack of ‘correctly’ done hardware.
Basically Canonical was like 15 years too early on this one. They created phones capable of running Ubuntu Touch, but the price tag and lack of supported apps probably killed interest in it. With Waydroid, now, you can supplement the apps with android apps until the Linux phone app ecosystem catches up.
We need a large funded Linux project to foot the bill on making the correct hardware to get the Linux adoption, but Canonical already tried that and failed back in 2012. 15 years later, I think the world is finally ready now, for a Linux phone.
It is not ready for a Linux phone. It’s barely ready for Linux on PC. The phone market would be much smaller. I’d love a Linux phone but I would need a android auto or carplay equivalent or compatible interface.
Not sure but waydroid might be able to run android auto, I have a device running postmarketOS and Waydroid, unfortunately my vehicle is too old for android auto but if I’m around any friend’s vehicles, I’ll try it out and see if it works.
–edit–
just checked my device, I think android auto comes installed with the android image that waydroid boots, which at the current time is Android 13, based on LineageOS 20 it looks like.
Its the lack of openness and standards on hardware, drivers, and boot sequence for ARM chipsets and phone hardware that’s the problem. x86/x86_64 hardware had standards that the industry settled on so the Linux adoption was fairly quick, with phone hardware, every phone, android kernel, camera hardware and driver, display hardware and driver, etc is slightly different so the hardware is so hard to adopt when literally every device has to be blackbox reverse engineered because the hardware manufacturers don’t make anything open or standard.
That’s an adoption problem. The manufacturers don’t care for it, they have no reason to.
Well then ya have a chicken and egg problem, if hardware manufacturers don’t care to do things ‘correctly’ because of lack of interest in Linux adoption, but there’s no Linux adoption because of the lack of ‘correctly’ done hardware.
Basically Canonical was like 15 years too early on this one. They created phones capable of running Ubuntu Touch, but the price tag and lack of supported apps probably killed interest in it. With Waydroid, now, you can supplement the apps with android apps until the Linux phone app ecosystem catches up.
We need a large funded Linux project to foot the bill on making the correct hardware to get the Linux adoption, but Canonical already tried that and failed back in 2012. 15 years later, I think the world is finally ready now, for a Linux phone.
It is not ready for a Linux phone. It’s barely ready for Linux on PC. The phone market would be much smaller. I’d love a Linux phone but I would need a android auto or carplay equivalent or compatible interface.
Not sure but waydroid might be able to run android auto, I have a device running postmarketOS and Waydroid, unfortunately my vehicle is too old for android auto but if I’m around any friend’s vehicles, I’ll try it out and see if it works.
–edit–
just checked my device, I think android auto comes installed with the android image that waydroid boots, which at the current time is Android 13, based on LineageOS 20 it looks like.