Live data from Hacker News

Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

arstechnica.com

121–130 of 226 posts

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#121
post #27

What about Google? The issues fairphone mention are passing Google certification suites. They should be relaxed to help those cases. As far as I know the major issues are around GLES. It passed older CTS, so GLES was good enough back then. Surely it could be good enough now.

Isn’t gles replaced by vulkan since about 5 years ago? Google wouldn’t want so much fragmentation for app developers to deal with.

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#122
post #62

I don't blame Qualcomm one bit. Why would they want to support old hardware long after 99% of people aren't using it?

People aren't using it because it is no longer receiving updates. 2-3 year old hardware should not be considered "old", or obsolete.

Android hardware ages really poorly. I have an iPad and a few android tablets from around 2014 and the iPad is on the latest version of iOS 14 and feels almost new while the android tablets are basically unusable and on 2015 versions of android.

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#123

Earlier quoted context omitted.

Didn't some Linux maintainers had very clear legal words for NVidia when they tried to make a kernel HAL/ABI?

NoyesNo, Nvidia tried to make a doggy legally questionable workaround for license aspects, so it's not quite the same. Also as far as I remember (I might be wrong) the google HAL isn't a abstraction/redirection in the low level kernel module layer it lives on a higher abstraction level and was meant to make the amount of ways braking less but never planed to add abstractions on top of which you could build a graphics…

Still not as a bad as Linuxant: https://lwn.net/Articles/82305/

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#124
post #91

Earlier quoted context omitted.

> have strangled Linux in its early years. And likely would still do so toady. I mean we are speaking about the kernel internal API (not the syscall API, which is stable). Even systems which pride themself for internal kernel API stability do change the API every view years, while often having much less internal (feature/platform support) changes then Linux . Furthermore in android Linux LTS versions are often used w…

Why? WDDM drivers written for Windows Vista can still work on Windows 10. And Windows is not a "niche" system.

Because Windows is a (very broken) Micro-Kernel system which did very little changes to it's kernel (as far as I know) in the last many years, in difference to that Linux is a macro kernel with constant changes and improvements to it.

Are the improvements worth the cost? I don't know. (For server applications likely yes, but for desktop likely not).

What I do know is that there are clear benefits of micro kernel architectures, even if they are kinda messed up (for a micro kernel) hybrids like windows has.

Lastly the way the kernel API's are designed can also make a major difference independent of the rest. Honestly the Linux kernel API feels much more raw then the windows API, but I only have every written a single dummy driver for each platform and that was quite a while ago.

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#125
post #91

Earlier quoted context omitted.

Why? WDDM drivers written for Windows Vista can still work on Windows 10. And Windows is not a "niche" system.

Because Windows is a (very broken) Micro-Kernel system which did very little changes to it's kernel (as far as I know) in the last many years, in difference to that Linux is a macro kernel with constant changes and improvements to it. Are the improvements worth the cost? I don't know. (For server applications likely yes, but for desktop likely not). What I do know is that there are clear benefits of micro kernel arch…

Windows NT is not a microkernel - Windows CE was, however.

NT has been shifting towards running more driver-code in user-space, as has macOS as well, especially with UMDF (especially for USB devices) and for graphics drivers, which are historically the #1 cause of BSODs - however just because the kernel passes control to user-space for the bulk of the driver's number-crunching doesn't mean that architecturally the kernel is still responsible for huge swathes of the computer's functionality. With a true micro-kernel there isn't any third-party code in the kernel space - not even a stub.

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#126
post #61

Earlier quoted context omitted.

Are you implying the 'no stable binary ABI' policy is responsible for a lot of e-waste?

I mean, that seems to be the result, yes? The intent is to compel device manufacturers to release the source of their drivers, but at this point, I think we have to admit that's not a great description of what's happening in the mobile space.

I dunno, seems a stretch to blame the kernel for e-waste when theres tons of other well funded parties creating the waste in the first place with zero intention of supporting the device beyond a year, let alone enabling anyone else to support it.

The android ecosystem is already better than the completely proprietary feature phones of before.

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#127
post #91

Earlier quoted context omitted.

Why? WDDM drivers written for Windows Vista can still work on Windows 10. And Windows is not a "niche" system.

Because Windows is a (very broken) Micro-Kernel system which did very little changes to it's kernel (as far as I know) in the last many years, in difference to that Linux is a macro kernel with constant changes and improvements to it. Are the improvements worth the cost? I don't know. (For server applications likely yes, but for desktop likely not). What I do know is that there are clear benefits of micro kernel arch…

This comment feels like it was written by someone who hasn't done much Windows development (which is fine!). The kernel changes a lot over time, introducing entirely new driver models (see https://en.wikipedia.org/wiki/Windows_Display_Driver_Model#H... for an example), OS-wide features, etc. Things like thread scheduling or timer granularity can and will change (see https://randomascii.wordpress.com/2020/10/04/windows-timer-r... for a recent example)

Let's not forget about massive stuff like the whole Windows Subsystem For Linux, which was literally an entire separate process type alongside Win32 processes, with its own set of syscalls etc. Added and then deprecated (and probably eventually removed entirely) over the span of years.

Maintaining a stable kernel ABI is no doubt a big investment, but it's possible and doesn't have much to do with whether your kernel is a microkernel or not. Lots of Windows drivers these days are user-space which helps maintain compatibility and stability.

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#128

Earlier quoted context omitted.

That's more or less what happens already.

It is but if the radio driver was open source then the interface with the radio SoC would be documented. Right now it is the worst of both worlds. Closed interface for a closed undocumented chip able to execute arbitrary code.

The interface isn't closed anymore, is it? [1]

[1] https://www.kernel.org/doc/html/latest/mhi/mhi.html

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#129
post #21
post #5

Qualcomm is only able to obstruct in this way because Linux doesn’t keep the kernel driver ABI stable for any fixed period of time. If Android used FreeBSD and Qualcomm shipped drivers for the latest build when the SoC was released, you’d have up to five years of support from that kernel release. Windows Phone 10 was actually in a position to support phones for years and even got Qualcomm onboard. It’s a shame the pl…

I’m going to reply to a few sibling comments at once: Yes, they could upstream drivers, but they won’t. It’s not in their best interest. I’m taking about what could be done in spite of this. Given that they won’t upstream drivers, if the blobs they release keep working for the reasonable life of your device, your phone can get other software updates, including major OS updates. I don’t expect or need the camera or ra…

Qualcomm upstreams tons of support for their SoCs.

Re: Fairphone suggests Qualcomm is the biggest barrier to long-term Android support

#130
post #115

Earlier quoted context omitted.

Android should have been GPL

The part of Android that talks to the Qualcom drivers is the Linux kernel, which is GPL already.

You can read the patented algorithm in the patent, and even implement it, but you cannot legally distribute it, until the parent expires.
Post reply on HN