Linked by Radio on Mon 2nd Jul 2012 19:15 UTC
Google It was time somebody cleared that up: the oft-decried skins put by OEM and operators on Android are not responsible for the lateness or lack of updates. The truth is that skins are easy, hardware drivers are hard. That is not to say skins do not have other problems, or that the problem is unsolvable, but asking for "stock" Android OS is not going to help on the update front.
Thread beginning with comment 524801
To read all comments associated with this story, please click here.
GPL to the rescue!
by tidux on Mon 2nd Jul 2012 19:46 UTC
tidux
Member since:
2011-08-13

Ever notice that it's only the proprietary hardware drivers that have this problem? If your code is included in AOSP, it'll ship day and date with a new release.

Reply Score: 3

RE: GPL to the rescue!
by _txf_ on Mon 2nd Jul 2012 22:13 in reply to "GPL to the rescue!"
_txf_ Member since:
2008-03-17

Ever notice that it's only the proprietary hardware drivers that have this problem? If your code is included in AOSP, it'll ship day and date with a new release.


If there was ever an argument for in kernel tree drivers this is it.

The hardware oems have the power to tell their suppliers to work with the kernel devs. Any porting efforts between versions are somewhat shared.

Unfortunately there is also the problem that the linux kernel arm tree complete mess ( I assume aosp shares the same problem) . With massive amounts of duplicated functionality and code...

Reply Parent Score: 4

RE[2]: GPL to the rescue!
by Radio on Tue 3rd Jul 2012 07:39 in reply to "RE: GPL to the rescue!"
Radio Member since:
2009-06-20

Unfortunately there is also the problem that the linux kernel arm tree complete mess ( I assume aosp shares the same problem) . With massive amounts of duplicated functionality and code...
Which shows that the problem is not "open vs close" drivers. The real root of the "problem" is hardware diversity. (It is more of a trade-off though; I do like the diversity and fast progress we see.)

Hardware changes are generally wide; getting open drivers would not help much, you can seldom iterate code from one CPU (or GPU, or the camera chip, or any other chip) to its next version or variant.

Reply Parent Score: 3

RE: GPL to the rescue!
by 0brad0 on Mon 2nd Jul 2012 22:29 in reply to "GPL to the rescue!"
0brad0 Member since:
2007-05-05

Ever notice that it's only the proprietary hardware drivers that have this problem? If your code is included in AOSP, it'll ship day and date with a new release.


The license itself is irrelevant for the situation. The drivers simply need to not be binary blobs but open and included upstream.

Reply Parent Score: 4

RE[2]: GPL to the rescue!
by tidux on Tue 3rd Jul 2012 12:40 in reply to "RE: GPL to the rescue!"
tidux Member since:
2011-08-13

It's not irrelevant, since only GPLv2 drivers can be included into the Linux kernel tree.

Reply Parent Score: 2