By 
It’s been a littler over a year since Android 4.1 Jelly Bean first made its way to Nexus devices. Not quite a huge leap from the Ice Cream Sandwich that debuted in the Galaxy Nexus, Jelly Bean merely patched up and addressed some of Android’s UI inconsistencies, improving the user experience overall. When it comes to the next big jump in Google’s mobile OS, all eyes are pointed to the next Nexus device which, going by Google’s current track record, will most likely release towards the end of this year.
Never officially announced, it’s looking like Google’s next Android dessert will be named Key Lime Pie. The upcoming version of the Android OS just got a little more real today after build number KRS36B was caught running on both the Nexus 4 and Nexus 7. Developer “dknandiraju” posted a list of his devices used in testing Chromium, where a few Galaxy devices running Jelly Bean were mentioned, along with the Nexus 4 and 7 running this mysterious new build number.
For those unaware, Jelly Bean builds start with the letter designation of J, with the most recent being JWR66V (Android 4.3). This means these devices could have been running Key Lime Pie (the specific Android number has yet to be determined), and other than that… well, not much else. Guess it’s just exciting to catch a glimpse of Key Lime Pie, no matter how small. Then again, perhaps we need to get out more.
[CNET]
I’m afraid to see what the little Android mascot is evolving into… Skynet?
Do not be afraid. Assimilate. Resistance is futile.
As long as Google doesn’t release a device named the Nexus T1000, I wouldn’t worry…….;P
..
“Guess it’s just exciting to catch a glimpse of Key Lime Pie, no matter how small. Then again, perhaps we need to get out more.” -Chris
I don’t know about you, but I take my phone outside all the time!
Really bro? You bring your blow-up doll outside too??? We should double date…..
Heard that!!!
Why did this make me bust out laughing at work?
It shows how nerdy the users of phandroid are when stating that you merely have a girlfriend is bragging.
I hope it fixes all the lag and broken features on my S4.
tell that to samsung
Uhhhhh yeah, not an Android problem, but most definitely a Touchwiz problem.
Not even a touchwiz problem, its a Samsung problem, they go overboard with the features, just the system itself takes up like 6-7gb of internal storage, it’s running 3 times the background procceses of a stock Android device. The Note 3 benchmarks seem to indicate the same thing, it’s using the same hardware as the Lg G2 but scoring 8,000 less on antutu, probably because its getting all the s4 features + all the new S-pen capabilities, talk about bloat. Samsung needs to go back to the drawing board and get rid of some of the stuff nobody uses.
Like I said, Touchwiz.. What do you think all those features are? (-_-)
Touchwiz would be fine if Samsung did enough kernel dev and QA to make it run smoothly. This isn’t 2010 anymore, and phone today are long since powerful enough to blow through any extra features that OEM’s pack into them. The problem is testing the device as a whole and working the bugs.
Yea it’s touchwiz, I have a S4 running a Google Edition rom and it’s amazingly fast. Dumped the Samsung touchwiz bloat, I had all their useless features turned off anyway.
In order to get rid of the lag, you will have to get rid of all the features running in the background that you don’t use. There’s only one way I can think of to access ROOT programs and features and remove them.
That emphasis, though. LoL!!
You can uninstall all the ones you installed. The rest you can just go to the manage app in the settings and disable any built in ones.
No root needed.
I’m so used to how Android used to be I forgot you can disable apps. LoL!! You’re right. At this point in time, you really don’t need to root to get rid of things.
That has nothing to do with the o/s, and a new Google release won’t help. Your S4 issues are due to Samsung not spending enough time testing their modified version of Android to work on their hardware.
Key Lime Pie. You keep using that word. I don’t think it means what you think it means.
princess bride?
we do need to get out more…
The little Android is going to get diabetes
Lmao. This was hilarious to me
:-)
yeah 4.1 was just a failed attempt to fix that classic android lag
sad really
Whats going to be after KLP? All I can think of that starts with an L is licorice…
lollipop?
Then muffin… anyone?
APPLE Pie. :-)
Lime Pie?
Hey Chris, what ever happened to Android Overload? ‘Twas my favorite weekly android news thingy :p
Guess Ios 9 now can catch up to key lime pie
мy coυѕιɴ ιѕ мαĸιɴɢ $51/нoυr oɴlιɴe. υɴeмployed ғor α coυple oғ yeαrѕ αɴd prevιoυѕ yeαr ѕнe ɢoт α $1З619cнecĸ wιтн oɴlιɴe joв ғor α coυple oғ dαyѕ. ѕee мore αт… ViewMore——————————————.qr.net/kAgk
In order to get rid of the lag, you will have to get rid of all the
features running in the background that you don’t use. There’s only one
way I can think of to access ROOT programs and features and remove them.
I think this article belittles the relevance of Project Butter.
Still not a fan of the name Key lime Pie. Jelly Bean sounded so much better. If there’s no good-sounding K-desserts they should just use something else.
Agreed. Even Kandy Kane would have been better.
Android “Kitchen”. It stocks the ingredients for any recipe :)
Still wondering when the android update ” diabetes ” is coming :)
I think that’s release 7.x, pretty sure Android 6.x is Sugar Coma.
The MotoX debate has brought about some interesting news and maybe Google should stop thinking their new OS for a bit and rethink what its doing. If Motorola could increase performance by such a great deal just by optimizing the software and using some OLD dual core cpu then there is a MAJOR mess up in the Android OS.
From what I have read manufacturers are not optimizing drivers for their phones and just tossing on fancy hardware. But the basic I/O programs talk to for a system is controlled by Android isnt it? So if MotoX can do so well by optimizing then all other phones are working poorly and could give the users a much better overall experience if they had optimized drivers for the chip sets. Maybe Google should give that problem a think. Because sooner or later there will be no reason to upgrade the fancy phone because the OS drivers are so bad.
First of all have you used a motoX, or seen a benchmark? Nope we haven’t because we are still at the marketing and initial impressions. All of the initial reviews are based on how it feels, using a brand new device. And quite a few have admitted that if you put it head to head against a HTC One or S4, the MotoX will lose every time. I’ve seen it said numerous times that it’s not the fastest device, but it’s fast enough.
Jelly bean 4.1 actually improved performance a great deal on slower hardware, I don’t think this conclusion you’ve jumped to from a few first impressions of the motoX holds water. It’s a dual core S4 clocked at 1.7Ghz with 2GB of ram, that’s hardly ancient and as most people know many apps are still single threaded or at best dual threaded and don’t feel much faster with more than 2 cores.
I’ve never ran a benchmark on any phone but i do use my phone to do phone things.
Old dual core using the same core as the US Galaxy S4. Yea its real old alright.
Samsung has a quad core in theirs and has a higher resolution screen which helps for clarity of small print like we all have on a phone. It has several unique features that i find attractive and I don’t even own a S4. What I meant by old tech when compared to the htc one and G2. How much better a smart phone could this be with 2.3ghz quad core and internal software optimized to use it?
You’re slightly still wrong as you’re still comparing devices with the same core. 2 more cores doesn’t make a bit difference except in benchmarking..
I also doubt it’d be any better, as you’d never use all 4 of those cores. Also it’s a slightly well known fact that 1080p screens on a phone are pointless because after a certain point your eyes are no longer able to tell a difference. 720p is the start of that level, especially on a 4.7 inch screen.
Your eyes can resolve up around 2000 dpi or ppi in this case. The smaller the print the more you need the res for clarity. I worked in photo typography. As far as not using 4 cores, that is googles issue isn’t it? Process distribution among cores is for the OS to decide and if you ever used task killer you’d know there its a lot more than one task running.
its not an old dual core cpu, its a new dual core cpu. Not the same s4 that’s in the gs3/One X
I thought JSS was the latest, 4.3.0.1 ?