Earlier quoted context omitted.
But Qualcomm doesn't have a monopoly on the market. There's Apple too. Sure, Android mostly uses Qualcomm in higher end models, but that is not the reason why Qualcomm can do anything they want. The reason things are the way they are is simple - users doesn't care. Users will happily throw cash the for next groundbreaking, awesome possum camera innovation that is just so totally worth the $1000 upgrade, because fabul…
Ok an oligopoly, does that make it better. Apple has a monopoly on Apple silicon.
Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
51–60 of 226 posts
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#52Earlier quoted context omitted.
>Compare that to the PC processor space, how much does AMD/Intel provide? 10 years? More? They don't "provide" anything. It's the software (eg. linux/windows) that's providing backwards compatible support. Vendor support for pc hardware lasts a few years at most.
Amd and Intel CPUs are still 100% backwards compatable with 40 year old chips. Not just their own chips but also nearly all the features of their competitor's chip too.
The CPUs might be, but the chipset drivers definitely aren't. You'll have a hard time booting windows 95 on a ryzen system, for instance. Hell, ryzen doesn't officially support windows 7. Still, I get your point, standardization in the PC space (mainly stemming from the "IBM compatible" standard) has made backwards/forwards compatibility much easier.
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#53It's not just Qualcomm it's closed source driver blobs in general. Even if your CPU might still be supported your other hardware might not. A common offender is camera drivers as far as I know and while you sometimes can still make the camera work it often comes with noticeable decreased quality (as the special patent encumbered closed source image post processing sausage is missing). Besides that potential but as fa…
What I don't understand (due to my ignorance, please explain if you can)... what keeps the driver blobs from continuing to work from one version of Android to the next? What prevents people from using the same drivers for a device on Android 7 and upgrading the OS to 9 or 10? I always understood that drivers would continue to allow the OS to recognize the component that the drivers are for unless something drasticall…
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#54It's mind-boggling to me that Qualcomm only guarantees 2-3 years of support for their chipset. Compare that to the PC processor space, how much does AMD/Intel provide? 10 years? More? Somehow people seem to be running on 15 year-old Thinkpads without a problem, yet a $1000 phone apparently can't scrape by for more than three years due to vendor support?
>Compare that to the PC processor space, how much does AMD/Intel provide? 10 years? More? They don't "provide" anything. It's the software (eg. linux/windows) that's providing backwards compatible support. Vendor support for pc hardware lasts a few years at most.
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#55It's mind-boggling to me that Qualcomm only guarantees 2-3 years of support for their chipset. Compare that to the PC processor space, how much does AMD/Intel provide? 10 years? More? Somehow people seem to be running on 15 year-old Thinkpads without a problem, yet a $1000 phone apparently can't scrape by for more than three years due to vendor support?
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#56Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#57Chipset support from the manufacturer is not, strictly speaking, essential. What we need is support in the mainline Linux kernel. Many of the custom hardware blocks that a kernel has to support via its drivers are shared across chipsets generations anyway, so they end up being supported a lot longer than any single HW platform.
Right, and we're not going to get support in the mainline kernel without chipset manufacturer support. Namely in the form of open sourcing all the binary blobs, because those aren't going to be accepted into the mainline kernel. Qualcomm just doesn't want to do this. I'm not sure if it's because they don't feel like spending the developer time (money) to do so, or if they believe 2-year obsolescence is better for the…
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#58If you want lifetime updates for your phone, consider Librem 5 [0] or Pinephone [1] instead. They do no rely on Android but use GNU/Linux as OS. [0] https://en.wikipedia.org/wiki/Librem_5 [1] https://en.wikipedia.org/wiki/PinePhone
IIRC there are still some binary blobs on there which might not work after some breaking change down the line, right?
The only thing that could break are the radios (wifi,bt,modem) becoming incompatible with the networks they communicate with but they're separate components anyway and the modem speaks a standard protocol so I'm sure it could be replaced.
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#59Earlier quoted context omitted.
Amd and Intel CPUs are still 100% backwards compatable with 40 year old chips. Not just their own chips but also nearly all the features of their competitor's chip too.
>Amd and Intel CPUs are still 100% backwards compatable with 40 year old chips The CPUs might be, but the chipset drivers definitely aren't. You'll have a hard time booting windows 95 on a ryzen system, for instance. Hell, ryzen doesn't officially support windows 7. Still, I get your point, standardization in the PC space (mainly stemming from the "IBM compatible" standard) has made backwards/forwards compatibility m…
Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support
#60Chipset support from the manufacturer is not, strictly speaking, essential. What we need is support in the mainline Linux kernel. Many of the custom hardware blocks that a kernel has to support via its drivers are shared across chipsets generations anyway, so they end up being supported a lot longer than any single HW platform.
Right, and we're not going to get support in the mainline kernel without chipset manufacturer support. Namely in the form of open sourcing all the binary blobs, because those aren't going to be accepted into the mainline kernel. Qualcomm just doesn't want to do this. I'm not sure if it's because they don't feel like spending the developer time (money) to do so, or if they believe 2-year obsolescence is better for the…