Linked by fran on Sat 24th Dec 2011 10:09 UTC
Linux "Android drivers are returning to the Linux kernel. Kernel maintainer Greg Kroah-Hartman has retrieved the Android drivers removed from the staging area of Linux 2.6.33 in the spring of 2010 andput them back into his development branch for version 3.3 of the Linux kernel. [...] The plan is for a Linux 3.3 kernel to be able to boot on an Android device without further patches."
Thread beginning with comment 501238
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by kaiwai
by WorknMan on Sun 25th Dec 2011 03:15 UTC in reply to "Comment by kaiwai"
WorknMan
Member since:
2005-11-13

Imagine a whole community making nightly builds and stable builds for a variety of phones - buy a phone, rip off the OEM version to load on a nice and clean vanilla version knowing you're going to have years of updates in front of you rather than the current situation of Samsung users left high and drive with Samsung's refusal to provide ICS for Galaxy S users.


Kind of the way it works now, except:

1. It's really a crapshoot whether the custom rom you're trying out is going to be stable or not.

2. The shelf life of an Android phone is probably going to be artificially limited by the hardware, and whether or not it can handle the latest version of Android.

I'm not real sure how this change is going to affect either one of the above.

Reply Parent Score: 2

RE[2]: Comment by kaiwai
by Seaborgium on Sun 25th Dec 2011 05:27 in reply to "RE: Comment by kaiwai"
Seaborgium Member since:
2011-09-17

That is the exact experience I had with the Samsung Captivate. For the first few months after its release, there were only methods to root the phone and a few Eclair builds, which all generally worked well, but were all based from a few leaked Samsung builds. The first Froyo build was also a leaked Samsung build (which supposedly was released in Canada), and all of the proceeding builds were also of good quality. When 2.3 was released, there was a period of pseudo-Gingerbread builds (Froyo core with Gingerbread applications and themes) followed by a sole Gingerbread port from the Nexus S. There was a Cyanogenmod 6 experimental build released around this time, and the Captivate gained official Cyanogenmod status with version seven. I must say that this rom was impeccable by the stable release, and it has had comparison in neither features nor customization. I am currently testing an Ice Cream Sandwhich beta, which is somewhat slower than previous roms, whether it be the system itself or the quality of the rom, but it is still excellent for everyday use. It would not surprise me if this phone is completely up-to-date after two years.

Reply Parent Score: 1

RE[2]: Comment by kaiwai
by kaiwai on Mon 26th Dec 2011 01:40 in reply to "RE: Comment by kaiwai"
kaiwai Member since:
2005-07-06

Kind of the way it works now, except:

1. It's really a crapshoot whether the custom rom you're trying out is going to be stable or not.

2. The shelf life of an Android phone is probably going to be artificially limited by the hardware, and whether or not it can handle the latest version of Android.

I'm not real sure how this change is going to affect either one of the above.


It is a crapshoot these days because the current situation rests on leaked builds and trying to put together the various custom patches that OEM's make but never merge with the mainline kernel - thus provide the patches but all hell breaks loose later on when a particular patch is based on kernel xyz and a newer version has been released.

Regarding the hardware shelf life - I doubt it greatly. The changes made in recent version have made Android more efficient (memory and CPU) with any addition features being centred around new hardware being added thus disable if not present. It really is a game that these phone vendors play where they sucker end users in as the 'anti-iPhone' only for the end user to find after 2 years of neglectful non-existent update that their phone is a ticking privacy time bomb waiting to explode. I mean, take the iPhone 3GS, over 2 years of support and still counting, something you'll never see when it comes to Android handset vendors.

There is a reason also why handset vendors are luke warm to Windows Phone 7 - because like the iPhone, Microsoft maintains as much control over the OS as possible thus they cannot do their shifty-dodgy behaviour by refusing to provide updates. End of the day carriers don't care if you don't have the latest phone because it means milking more profits off you as the consumer by signing you up on another contract. The biggest losers are the handset vendors building in planned obsoleteness as part of their over all business plan - why create a compelling product that people will buy when you can literally force them off their existing device by removing all support from them the moment the customer leaves the store.

Edited 2011-12-26 01:43 UTC

Reply Parent Score: 0