By 
It looks like a new build for KitKat could be coming our way soon, as new evidence suggests Google is well underway on build KTU65. The evidence appeared in a Google Code bug report for Chromium by a Googler who seems to be testing the build on their Nexus 5.
So what could it be? Well, going by what we know about the way Google does build numbers, it’s most certainly part of the KitKat family, and is a build that is made as recently as earlier this month.
The number at the end of it are just a date identifier, so whatever this ends up being might not have that exact build number whenever Google gets around to taking it out of the oven. There’s no telling what, exactly, is inside the build, though we know Google still has a lot of kinks to work out in Android 4.4 KitKat.
Specifically, we know there’s a harrowing camera bug that causes excessive battery drain in Android 4.4.2. Most users probably haven’t noticed, but those with Skype running in the background are more likely to see the bug rear its ugly head than anyone else.
Thankfully Skype has already issued a fix that should make it much less likely for their app to trigger the bug, though Google hasn’t yet patched the issue on their end.
Google says they’ve already identified the issue, though, and have already confirmed a fix for a future release. There’s no telling if that fix will be in the build mentioned above, but we imagine this is one issue Google isn’t dragging their feet on. We’ll just have to wait until Google feels this one is ready to roll out to the masses to see what it’s all about.
[via MYCE]
The real issue is when the manufacturers will be able to implement the fix in their builds
Yup. Which at the rate some of them have been moving, some of us will not see this until the next Nexus is announced.
Instead of whining about it, vote with your dollars.
Only by spending money on devices like the Nexus line and similarly updated devices will this ever change.
Uh, no. Whining about it causes new buyers to shy away from all the phones that need carrier approval for android version updates.
Cheers on encouraging Nexus purchases, h4, but the world would be a better place if the carriers and makers figured out a better way to compete with Nexus devices.
Which is why google play devices exist.
As well as some devices that get updates quite well like the Moto X.
Vote with your dollars buy devices that get updated. Carriers and OEMs care only about money, not your complaints.
I’ve bought two Nexuses in large part due to the complaints I’ve seen on the competition. A “Google Play Experience” device is high on my list for my next phone. Nexus’ exclusion of a micro-SD slot and their crippling of mounting USB Mass Storage devices just makes them far less usable (a point driven home to many by people complaining on forums and to their friends).
People complaining tells others to look for alternatives. Complaining about complainers serves little purpose, in my opinion.
Crippling?
MTP is better, it is an improvement.
SD cards are slow, and lead users to believe their smartphone is slow.
Money talks and BS walks. That is what the OEMs know.
But you whine about it but still buy their product, why would they care?
Well, that’s a nice theory but it locks you down to just a few devices and those devices don’t support all of the services my carrier offers. I know this because I own a few Nexus devices from “as far back as” the Nexus One.
It is not a theory, if you buy devices that do not get updates you are voting with your dollars for that to continue.
Would be nice if it fixes the bluetooth problem. My N7 is my audio player in my vehicle and I really can’t use it anymore in that fashion since the 4.4.2 update.
Is this a known issue? Bluetooth on my Nexus 5 has been SUPER screwy lately…
Yes. I’ve seen a few articles about after searching. I’ve mentioned it to them on twitter and on the Google forum for the N7 with no responses. I’ve seen a few fixes that have worked for others but none of them have worked for me. I stopped using it for a couple months in my vehicle then a couple weeks a that I’d give it try and it work perfectly. The next day…back to not working.
Hopefully this new version supports HCE for NXP NFC chipsets.
I hope it fixes the stock email app problem as well.
Never heard about this problem. What is it?
Ever since the 4.4.2 update a number of users are having trouble setting up any type of email account on the stock email app, even their own gmails. I have had this problem day one with my N5 since it came out the box 4.4.2 and have to resort to using Aquamail, which gets the job done but it’s no stock app.
I didn’t even know people used the stock e-mail app, haha.
This problem, for one: http://code.google.com/p/android/issues/detail?id=62805 .
Ever since I got my day-one Nexus 5 (and subsequently after my N7 updated to KitKat), I have not been able to download my attachments in the stock email client. Worked perfectly in Android 4.3 (in fact my G’Nex on stock Android 4.3 still works perfectly in this regard), but not in Android 4.4.x. It’s really annoying. Also the 5MB limit imposed on attachments in Android 4.4.x is ridiculous and should be AT LEAST adjustable.
would be nice if verizon actually updated my g2 to kitkat.I know it`s only been 6 months since it was released.Usually it takes verizon a decade to update their phones.
Nah, you don’t want it. At least not 4.4.2 with the battery draining bug. Better to wait (request) for this new KTU65 build. You’re dodging a bullet!
Does anybody know if the bug where mytracks eats up all your battery life is related to the Camera bug with Kitkat? Or is it just something screwy with the mytracks app? :-