Android "Key Lime Pie" Likely Revealed 10/29

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
Set your sights on a new dessert coming out soon. Google will be serving up a tasty Key Lime Pie for Android users. The new mobile operating system will be introduced alongside of the LG Optimus, which will be the first smartphone to come with KLP preinstalled.
 
though appreciate the speed of development of android, but I honestly help but feel that with every release the older versions are left, somewhat, incomplete, lacking, and most importantly some apps now incompatible with some versions, manufacturers who drop updates for their products doesn't even help the situation, this makes Android feel like, well your really typical linux OS,lol
 
I strongly think Google needs to develop some regularity in Android releases and only have one major "named" release per year, with some minor .1 or .2 releases for small features and bug fixes. The fact that some phones released in the last year are still just getting upgrades to ICS and here we are talking about KLP means that updates will NEVER be solved.

And it really is just a naming thing too. Is Google not aware of perception?
 
A huge issue with these updates isn't through Google but through the carriers. That's why a lot of phones don't have ICS or Jelly Bean yet, manufacturers don't want to jump through hoops for months just to update one of their 50 phones they released that year.

I personally think there's just too many Android phones, but that's what happens when every manufacturer basically has two options; make their own OS and hope it works, or use Android.
 
I still don't have jelly bean on my GS3. Would be nice if someone figured out how to get these OSs to the user a little faster. I might find a bit more satisfaction in my android experience if I wasn't always one version behind because my carrier is dragging their feet getting me the new OS.

P.S. I know I can jail break the phone and install a custom rom. but for a few different reasons I don't want to.
 
I'm rocking JB on my EVO4G. KLP might be fun if people keep updating ROMs for my device.
 
android phones not getting updated is not Google's fault. it's the carrier's/manufacturer's.. my nexus s gets updated with every release like clockwork.
 
android phones not getting updated is not Google's fault. it's the carrier's/manufacturer's.. my nexus s gets updated with every release like clockwork.
Seriously. When you have hobbyists pumping out tons of stable custom roms/ports/near base roms of higher versions of android before your phone even gets one update and while trying to sort out odd drivers without help from the creators, you know it's not all Google's fault. If the carrier/manufacturers actually put in some effort they could easily keep things updated.

I'm rocking CM10 Jellybean on my Infuse. It only fairly recently got Gingerbread (!)
 
It IS Googles fault for pumping out new versions every few months. It takes a lot more time for carriers and manufacturers to put out a rom then some tweaker due to testing and regulations. That time is money, and LOTS of it. It can get very expensive for a company to port and test a new version of Android over 20+ phones over multiple nations and carriers. Then you have Android changing things up every few months? These company's are chasing there tail in a very expensive game of catch-up, and loosing it seems. One more cost of hitching up your horses to Google's "free" wagon.
 
It IS Googles fault for pumping out new versions every few months. It takes a lot more time for carriers and manufacturers to put out a rom then some tweaker due to testing and regulations. That time is money, and LOTS of it. It can get very expensive for a company to port and test a new version of Android over 20+ phones over multiple nations and carriers. Then you have Android changing things up every few months? These company's are chasing there tail in a very expensive game of catch-up, and loosing it seems. One more cost of hitching up your horses to Google's "free" wagon.

Then again, part of this is the carrier/manufacturers fault...for releasing dozens of often shitty handsets and carriers wanting to load lots of uninstallable bloatware and crap like Sense.
 
Then again, part of this is the carrier/manufacturers fault...for releasing dozens of often shitty handsets and carriers wanting to load lots of uninstallable bloatware and crap like Sense.

Sense is not a bad program. Its gotten very bloated since its Windows Mobile days, but it puts a lot of information into 1 place. I think a lot of it is the carrier demanding there own version of each phone. Instead of 1 HTC 1X for the world, HTC needs to make 50 for each carrier, each with there own unique hardware and software, and that means they need to test a new version of the Android OS on each of those. We ALL have seen how BADLY an untested Android upgrade can jack up a lot of phones really quickly. So now carriers are being really cautious, and really cheap. I frankly dont blame them.
 
A huge issue with these updates isn't through Google but through the carriers. That's why a lot of phones don't have ICS or Jelly Bean yet, manufacturers don't want to jump through hoops for months just to update one of their 50 phones they released that year.

I personally think there's just too many Android phones, but that's what happens when every manufacturer basically has two options; make their own OS and hope it works, or use Android.

Manufacturers need to get some balls like Apple. When they wanna update their iPhones, they don't need carriers permissions. If developers from Xda-Developers can ports Jelly Bean to damn near every Android phone ever made, then manufacturers need to step their ship up, or hire those guys.
 
Screw that.

I'm rockin' a custom ROM from Steel Droid ICS V3.90 pcb blue on my Nexus. Comes with the latest popcorn kernel. I'm not wasting my time with these stupid updates like that jelly bean crap.
 
Screw that.

I'm rockin' a custom ROM from Steel Droid ICS V3.90 pcb blue on my Nexus. Comes with the latest popcorn kernel. I'm not wasting my time with these stupid updates like that jelly bean crap.

JB runs better than ICS on my EVO4g IME.

That being said, manufacturers do need to grow some cajones and say enough is enough and try to keep things vanilla.
 
People blaming the carriers/oems exclusively have no idea just what is needed to get a new version of Android running on a device. Here's a very brief overview the process of getting a version of Android onto a specific device.

1. Google begins making the next version of Android. Despite being "open-source" the majority of development is locked and internal.

2. Google sources drivers for their Nexus devices to get the next version of Android running.

3. Within days of releasing the newest updates to their Nexus devices, Android is released to OEM for them to BEGIN porting to their devices. This means that no OEM would ever have an update ready at the same time as a Nexus device (NOTE: This recently changed and OEMs are now given conditional early access).

4. Now that the Nexus devices have the latest and greatest, OEMs have to source drivers to make that version of Android compatible with their specific devices, unless they are using the EXACT same hardware as a specific Nexus device. This could take months.

5. Once the OEM finishes the update for their devices, they now have to push to their unlocked devices and push to the carriers.

6. The carriers begin making their own tweaks to the firmware before releasing to the devices.

So, Google, OEMs, carriers, and even the companies behind the individual hardware (IE, Qualcomm) are all responsible for some part of the fragmentation. Hell, one of the biggest reasons the Nexus One (and other Snapdragon S1-based devices) didn't get ICS was due to Qualcomm abandoning support in drivers for the Adreno GPU used in S1, the Adreno 200 (which was just a rebadged Adreno 130, which was just a rebadged ATI Z-series mobile GPU), which was outdated more than a year before the first Snapdragon device landed.
 
Manufacturers need to get some balls like Apple. When they wanna update their iPhones, they don't need carriers permissions. If developers from Xda-Developers can ports Jelly Bean to damn near every Android phone ever made, then manufacturers need to step their ship up, or hire those guys.

+1!

I even got custom Gingerbread ROM on an old Droid 1. It's great especially with the ability to overclock (der...) to 700 mhz.
 
Why are several people claiming there are "too many" Android updates "too often?" It's simply untrue that there's a major release "every few months." ICS was in 2011. JB was 2012, and isn't even a numbered increment. KLP will be 2013. Major updates are really no more frequent than for iOS.

As for the blame game, I refuse to take it off the manufactuers' and carriers' backs. If you follow Medion's timeline, the only thing the manufacturers really *need* to do following a new release is get drivers working. All of the firmware tweaks, shittastic UI overlays and useless carrier bloat apps are their own choice -- and represent the crux of the problem. I'm not saying the drivers don't take some time in and of themselves, and I'd never expect an update on my S3 the same day as a Nexus owner sees it. But even if it took 1-2 months to scrap together some drivers for any given handset, I don't think we'd be complaining much. When I'm waiting 4-6 months beyond that so that TouchWiz/Sense and AT&T Music can be dinked around with by some intern assigned to my phone, that changes thing.
 
If Key Lime Pie is released on October 29th I'll eat my own damned shoe...

The author of that article appears to be quite full of shit and speculating wildly.

If anything is announced it will most likely be a simple point release update and will still be Jelly Bean.


Jelly Bean just came out in June, for frig's sake.
 
And as for the people bitching and moaning saying stop with the updates?

Go get a damned iPhone or a dumb phone if you want a static device. One of the best things about Android is it's upgradability and depth of customization. I love that feeling when a new version of Android comes out and I know it's going to hit my device.

It's not Google's fault if carriers or manufacturers don't do a build for your device... get a Nexus device and be assured of upgrades for a good long while. :)
 
All his complaining about carriers is why I buy nexus devices. Hell my Xoom is a nexus device now too.
 
I wish Android can become like a desktop OS in the drivers sense, as in there's one installation of Android that end-users can download and install onto their devices, standard drivers that can be obtained from Google, and specialized drivers that can be obtained from the manufacturers. Yeah, that kind of flexibility/complexity might devolve into a customer service nightmare for everyone involved, and I can understand why carriers and manufacturers would rather sell new devices versus supporting the old, but damn it, as things are now it's fucking infuriating. Older devices that can still technically run the latest versions of Android (like the first fucking Android phone ever, granted not in a fully functional state) aren't given the time of day because fuck you, and the whole "newer versions of Android can't be installed on our older phones because they'll dramatically diminish user experience" bullshit carriers and manufacturers sometimes offer up as excuses for why their months-old product can't be updated is nonsense, because often times the only thing diminishing user experience just from the get-go is the extraneous, resource-sucking bloatware that's baked into the ROM!

GAHHH!!!
 
I wish Android can become like a desktop OS in the drivers sense, as in there's one installation of Android that end-users can download and install onto their devices, standard drivers that can be obtained from Google, and specialized drivers that can be obtained from the manufacturers. Yeah, that kind of flexibility/complexity might devolve into a customer service nightmare for everyone involved, and I can understand why carriers and manufacturers would rather sell new devices versus supporting the old, but damn it, as things are now it's fucking infuriating. Older devices that can still technically run the latest versions of Android (like the first fucking Android phone ever, granted not in a fully functional state) aren't given the time of day because fuck you, and the whole "newer versions of Android can't be installed on our older phones because they'll dramatically diminish user experience" bullshit carriers and manufacturers sometimes offer up as excuses for why their months-old product can't be updated is nonsense, because often times the only thing diminishing user experience just from the get-go is the extraneous, resource-sucking bloatware that's baked into the ROM!

GAHHH!!!

This isn't Windows. The Linux kernel is designed to have all of the hardware support built into mainline.
 
This isn't Windows. The Linux kernel is designed to have all of the hardware support built into mainline.

Except last I knew all the Android code got yoinked from the mainline as the LKML couldn't get any device drivers for love or money.
 
The only way I'll believe this OS will be named "Key Lime Pie" is if it a KLP statue appears on Google's front lawn next week. Lots of other sources are pointing to Android 4.2 being a maintenance release of Jelly Bean (and it's not the first time this happened either).
 
If you follow Medion's timeline, the only thing the manufacturers really *need* to do following a new release is get drivers working.

And this is where the problem lies. I should have added this step into it. Basically, when Android get released, both the phone OEMs (Samsung, HTC, Sony, etc.) are tweaking it, as well as the hardware vendors (Qualcomm, TI, etc.). This is where Samsung has a huge leg up. For their Exynos processors, they're usually making their own drivers with input from ARM (for the Cortex A8/A9/A15 that they use, and the Mali GPUs they use). Companies like HTC and Motorola are busing waiting on Qualcomm and Texas instruments, respectively. Texas Instruments has to wait on both ARM (Cortex A8/A9, eventually A15), and NEC/PowerVR for the GPU.

So, poor Motorola is waiting on chipset drivers from a company that is waiting on subcomponent drivers from other companies. And we wonder why Moto has such a hard time on drivers? So even though Cortex A9 > Scorpion and Cortex A15 > Krait, a lot of companies would rather go with Qualcomm due to their better-than-competitor support. That's why you don't see more TI OMAP processors used (although the Galaxy Nexus using OMAP4 is a big help).
 
Yeah... on one hand, ICS is way ahead of GB. On the other hand, Moto left Droid 3 owners hopeless on a update. The faster it goes, the faster my device will get outdated, and no sight of Droid 4 being launched on my country.

In fact, most cheap Android smartphones have this curse, and many who own one of those want an iPhone even more because of that.
 
People blaming the carriers/oems exclusively have no idea just what is needed to get a new version of Android running on a device. Here's a very brief overview the process of getting a version of Android onto a specific device.

1. Google begins making the next version of Android. Despite being "open-source" the majority of development is locked and internal.

2. Google sources drivers for their Nexus devices to get the next version of Android running.

3. Within days of releasing the newest updates to their Nexus devices, Android is released to OEM for them to BEGIN porting to their devices. This means that no OEM would ever have an update ready at the same time as a Nexus device (NOTE: This recently changed and OEMs are now given conditional early access).

4. Now that the Nexus devices have the latest and greatest, OEMs have to source drivers to make that version of Android compatible with their specific devices, unless they are using the EXACT same hardware as a specific Nexus device. This could take months.

5. Once the OEM finishes the update for their devices, they now have to push to their unlocked devices and push to the carriers.

6. The carriers begin making their own tweaks to the firmware before releasing to the devices.

So, Google, OEMs, carriers, and even the companies behind the individual hardware (IE, Qualcomm) are all responsible for some part of the fragmentation. Hell, one of the biggest reasons the Nexus One (and other Snapdragon S1-based devices) didn't get ICS was due to Qualcomm abandoning support in drivers for the Adreno GPU used in S1, the Adreno 200 (which was just a rebadged Adreno 130, which was just a rebadged ATI Z-series mobile GPU), which was outdated more than a year before the first Snapdragon device landed.
Except that some developers on XDA can have the latest Android running on your device withing weeks of the source code being released. The only limitation to a working port is drivers, but that's for XDA developers. For people like Samsung, Motorola, and HTC they already have the drivers, and have no issues.
 
Honestly the major problems with android are due to the carriers. If Google threw its weight around a little like Apple, then honestly most of androids "perceived" problems would disappear.

Google -
Ok Android version x is coming out in 30 days. The following device list is supported and the update is to be pushed out same day no exceptions.
The following device list are unsupported and are not to be updated.

Problem solved. The problem is google is giving the carriers far too much control over android.
 
Except that some developers on XDA can have the latest Android running on your device withing weeks of the source code being released. The only limitation to a working port is drivers, but that's for XDA developers. For people like Samsung, Motorola, and HTC they already have the drivers, and have no issues.

Yes, those custom ROMs are great, if you don't mind the flaws. CM10 on the SGS3 and sGS2 does not support MHL or "project butter" due to driver issues. Also, as I was trying to explain, in many cases, the OEM does NOT have the drivers. Motorola is a prime example of this as they're usually waiting on Texas Instruments, who is waiting on PowerVR and ARM. Now, with OMAP4, Moto has no excuse, but there was definitely an issue with OMAP3 along those lines.
 
(1) Jellybean
(2) ????
(3) ????

Are people seriously complaining that progress is happening too quickly? Sheesh....

Yes we are. My phone has had its ICS update delayed two months now and with that I'm left with an OS unsupported by even Google's own Chrome browser. I get that Google understands the short average service life of a mobile device, so they're focused on utizing the best of the current and next gen hardware. We're still in the early stages of a mobe hardware revolution, but the Android OS update model makes victims of the users.
 
Yes we are. My phone has had its ICS update delayed two months now and with that I'm left with an OS unsupported by even Google's own Chrome browser. I get that Google understands the short average service life of a mobile device, so they're focused on utizing the best of the current and next gen hardware. We're still in the early stages of a mobe hardware revolution, but the Android OS update model makes victims of the users.

I hate to admit it, but this is what comes in to mind, what happens is we are forced to literally update our handsets in less than a year, cool, but Im not that kind of guy honestly ,lol, though I am not complaining about progress, as mentioned by another user the problem is Fragmentation, maybe its due to as mentioned by others users to the drivers of the different parts of the system that can't catch up with Google, we can blame the manufacturers all day but nothing will change, maybe Google can help by making it easy for the older drivers to integrate with newer Kernels, I don't know, my bottom line is its getting a PITA to make Apps work across multiple android versions..
 
Yes we are. My phone has had its ICS update delayed two months now and with that I'm left with an OS unsupported by even Google's own Chrome browser. I get that Google understands the short average service life of a mobile device, so they're focused on utizing the best of the current and next gen hardware. We're still in the early stages of a mobe hardware revolution, but the Android OS update model makes victims of the users.

Google makes the Nexus phones, if you want to run Android, for real, get a Nexus, from Google..... this is well known among anyone that cares to pay attention...

Android, as provided by other manufacturers, is updated at their whim, and most likely wont work as well or be nearly as updated as an Android phone provided by Google... again, well known information...

Why should Google slow down the march of progress just because other OEM's don't care to treat their customers right? I for one, love having an OS that is constantly improving... the faster the better I say, as long as it isn't just change for change's sake (which, so far, none of the Android updates have been, thankfully)
 
Seems like a lot of people are unaware of new rules coming forth from Google and opening the Nexus program, such as:

  1. They are starting the Nexus program to all vendors, if they want to make a Nexus, there will be a process to getting it certified to be a Nexus.
  2. Nexus devices can have 3rd party UI's, such as MotoBlur and Sense, but it must be installed through their new customization center and a choice offered.
  3. Updates to OS's will be done near instantly, if not outright support google updating for a predetermined period of time from launch.

Google is fixing the segmentation of the market, and the first step is opening the gates for Nexus devices by anyone who wants to make it, and slowly shift towards making it so all devices fit Nexus specifications, thus breaking segmentation.
 
People blaming the carriers/oems exclusively have no idea just what is needed to get a new version of Android running on a device. Here's a very brief overview the process of getting a version of Android onto a specific device.

1. Google begins making the next version of Android. Despite being "open-source" the majority of development is locked and internal.

2. Google sources drivers for their Nexus devices to get the next version of Android running.

3. Within days of releasing the newest updates to their Nexus devices, Android is released to OEM for them to BEGIN porting to their devices. This means that no OEM would ever have an update ready at the same time as a Nexus device (NOTE: This recently changed and OEMs are now given conditional early access).

4. Now that the Nexus devices have the latest and greatest, OEMs have to source drivers to make that version of Android compatible with their specific devices, unless they are using the EXACT same hardware as a specific Nexus device. This could take months.

5. Once the OEM finishes the update for their devices, they now have to push to their unlocked devices and push to the carriers.

6. The carriers begin making their own tweaks to the firmware before releasing to the devices.

So, Google, OEMs, carriers, and even the companies behind the individual hardware (IE, Qualcomm) are all responsible for some part of the fragmentation. Hell, one of the biggest reasons the Nexus One (and other Snapdragon S1-based devices) didn't get ICS was due to Qualcomm abandoning support in drivers for the Adreno GPU used in S1, the Adreno 200 (which was just a rebadged Adreno 130, which was just a rebadged ATI Z-series mobile GPU), which was outdated more than a year before the first Snapdragon device landed.

4.Don't use non-free drivers and this won't be a problem; the community will have it ported before you do. I have no sympathy for the hardware companies who chose to unethically use proprietary drivers for their hardware. Intel has demonstrated that it is possible to have an open development model.

6.The carriers do not need to make their own tweaks. This is not a fault of Android, this is the fault of the carriers. Google should dictate that if you want your Android device to not be blocked from the play store, that you cannot load up the device with a bunch of bloatware.
 
Go get a damned iPhone or a dumb phone if you want a static device.

The sheer irony is that iPhones at least get guaranteed, timely updates. The iPhone 3GS got updated to iOS 6 (albeit with a bunch of features missing), while the much newer Droid Bionic just got ICS.
 
The sheer irony is that iPhones at least get guaranteed, timely updates. The iPhone 3GS got updated to iOS 6 (albeit with a bunch of features missing), while the much newer Droid Bionic just got ICS.

Well, MS-DOS was easy to update as well.
 
Yes, those custom ROMs are great, if you don't mind the flaws. CM10 on the SGS3 and sGS2 does not support MHL or "project butter" due to driver issues. Also, as I was trying to explain, in many cases, the OEM does NOT have the drivers. Motorola is a prime example of this as they're usually waiting on Texas Instruments, who is waiting on PowerVR and ARM. Now, with OMAP4, Moto has no excuse, but there was definitely an issue with OMAP3 along those lines.
I'm sure if developers wanted the drivers they would eventually get them. Every time you get an update to your phone, it costs manufacturers and carriers money. That's the only real limitation, plus you now have less of a reason to upgrade your phone. Carriers want you to keep getting the latest phone to stay locked into a 2 year contract, while manufacturers want you to keep buying their phones.

BTW CM10 is just one variant of roms. There's AOSP, and MUI which are also very popular as well. Unlike manufacturers, they have to deal with people rooting and getting a recovery into their phones, not to forget certain security done like locked boot loader. Not only do they rarely update their phones, but they find the time to prevent people from installing their own roms. It's bullshit.
 
Can these guys give them more tasteful names.

All ICS, Jellybean and Key Lime pie remind me of fat fucks.
 
Back
Top