I think what they want is a privacy protecting smart phone built on open source components. Also, Android is based on a driver and BSP model that is quickly going to be replaced with Fuchsia/Zircon
I think what they want is a privacy protecting smart phone built on open source components. Also, Android is based on a driver and BSP model that is quickly going to be replaced with Fuchsia/Zircon
> I don't think I'll ever get that in a not Android, not iOS phone.
Of course not, those apps nowadays do on-device checks in the TrustZone environment to verify with Google’s servers that you’re actually running a phone that’s approved by Google with a supported OS version in a supported configuration. Customization? Competition? Who cares!
> Street View
Considering just how much Google has tried to hurt Windows Phone by not supporting it with their own apps and services and even preventing others from making Windows Phone apps for their services, you’ll definitely never see Street View support on a non-Google non-Apple phone.
Your issue isn’t one that can be solved by open source volunteers. Your issue is one of monopolies and control.
I don't think so. If the smart phone was about protecting privacy, the amount of functionality that has to be disabled (or rather: not there) has to be insane.
That is the hard truth and the reality of it all and what is most likely going to happen.
A lot harder to degoogle if your device is nothing but google...
Of course, I have been saying that for years.
Contrary to the 'Fuchsia is only an experiment', 'Fuchsia is going to be shut down' coping crowd, in fact, Google has been much further than once thought with developing Fuchsia and it is going to start with replacing Linux with Zircon in ChromeOS next, probably in 3 to 4 years.
Also explains why they already have the Chrome browser running in Fuchsia. So there is no doubt that they are intending to use Zircon in ChromeOS.