Develop Bugs

[Q] Android 4.4 KitKat

Hello everyone,
We all know Android 4.4 KitKat was released today(1/11/2013). Since the source will be availible, is it possible to port it to the kindle fire(1st gen)? If yes, please make a stable rom.
Thank you and have a nice day
(Wanna get rid of CM 10.1)

It will take at least a week I am guessing, because the update "will be rolling out over the following weeks" as Google said, and then people will have to port it, so just have a little bit of patience. Also, why don't you switch to CM10.2 if you don't like what your on, or AOSP for that matter, as that runs better I personally think.
Sent from my Nexus 7 using Tapatalk

Not very likely since TI (the chip maker for the KF) won't be supporting android any more... or that's at least what I read. I'm hoping that I'm wrong though.

swaarley said:
Not very likely since TI (the chip maker for the KF) won't be supporting android any more... or that's at least what I read. I'm hoping that I'm wrong though.
Click to expand...
Click to collapse
Google said it can run on low end devices, and we do have Hashcode's 3.4 Kernel

jma9454 said:
It will take at least a week I am guessing, because the update "will be rolling out over the following weeks" as Google said, and then people will have to port it, so just have a little bit of patience. Also, why don't you switch to CM10.2 if you don't like what your on, or AOSP for that matter, as that runs better I personally think.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I cannot change too quickly. Mom allowed me only for CM 10.1, and now for CM 11(It will come, right?). Cannot do CM 10.2.

That kernel is not ready for primetime, also there is code that the chip maker will have to release code for it. See hash and others posting about it:
http://forum.xda-developers.com/showthread.php?t=1591850&page=276

Google says that kitkat can run on devices that have as low as 512mb RAM. We can sure overclock our processor to 1.2 GHz
Sent from my air powered ceiling fan

swaarley said:
That kernel is not ready for primetime, also there is code that the chip maker will have to release code for it. See hash and others posting about it:
http://forum.xda-developers.com/showthread.php?t=1591850&page=276
Click to expand...
Click to collapse
You know, hash doesn't say anything about not getting it to work. In my opinion he clearly stated that he is really trying to get 4.4 to work. It was others that were being sceptical.
Sent from my Nexus 7 using Tapatalk

True, the first ROM for any android version for our device is done by hash. Same case for 4.1,4.2,4.3,4.3.1
Sent from my air powered ceiling fan

As was previously stated, Texas Instruments is out of the microprocessor chip game and they have stopped supporting the binaries for newer versions of Android. It wasn't directly stated by Google but it's very likely that it was for that reason that they chose not to support the Galaxy Nexus in the newest iteration of Android, as it also uses a TI chip. I'd like to think that it would be possible to run Android 4.4 on the old Kindle Fire, especially since it lags pretty badly on stock, but I am afraid that the likelihood is fairly low.

True that it also what is written on hash's thread for the new kernel. He sure I trying hard and so my hopes are pretty much alive
Sent from my air powered ceiling fan

sparkplugDev said:
As was previously stated, Texas Instruments is out of the microprocessor chip game and they have stopped supporting the binaries for newer versions of Android. It wasn't directly stated by Google but it's very likely that it was for that reason that they chose not to support the Galaxy Nexus in the newest iteration of Android, as it also uses a TI chip. I'd like to think that it would be possible to run Android 4.4 on the old Kindle Fire, especially since it lags pretty badly on stock, but I am afraid that the likelihood is fairly low.
Click to expand...
Click to collapse
They already have 4.4 Roms for the Verizon galaxy nexus...it won't get official Google support but they have gotten Roms for it:
Example:http://forum.xda-developers.com/showthread.php?t=2508073
So,is it possible? Yes. Will it take a while? Probably....don't expect it soon but as others have said hashcode is working on
It...keep your fingers crossed

Jacobloveskindles said:
They already have 4.4 Roms for the Verizon galaxy nexus...it won't get official Google support but they have gotten Roms for it:
Example:http://forum.xda-developers.com/showthread.php?t=2508073
So,is it possible? Yes. Will it take a while? Probably....don't expect it soon but as others have said hashcode is working on
It...keep your fingers crossed
Click to expand...
Click to collapse
4.3 binaries can be hacked for 4.4.
Sent from my SGH-T959 using xda app-developers app

Hey guys! The wait is almost over.
There is already a build, no WiFi
Sent from my air powered ceiling fan

Stable build of cm 11 released, I think we can close this thread.
http://forum.xda-developers.com/showthread.php?p=47706499#post47706499
Moral: Lets always be optimistic (At least when its sensible)!
Sent from my air powered ceiling fan

Galaxy Nexus Gets Updated GPU Binaries, To Breath Life into the Two-Year Old Phone

As always, XDA is up to some good stuff with a new release of Android now available. Some developers are finding what appears to be updated binaries for the GPU that’s inside the Galaxy Nexus. KitKat was announced last week, and surprisingly, Google decided to drop support for the Galaxy Nexus. It’s surprising because KitKat can run on devices with 256MB of RAM, which the Galaxy Nexus has a full gigabyte of RAM available. We’ve already seen numerous custom ROMs flowing out for KitKat on the Galaxy Nexus. And it’s not just for the GSM Galaxy Nexus, but also the Verizon (Toro) and Sprint (Toroplus) versions.
It appears that Texas Instruments have updated the GPU binaries for the Galaxy Nexus. Now, Google may not have known that TI was going to update it or Google may not have told TI that they had given up on the two-year old device. But either way, developers are hard at work building an updated kernel that might help solve some of the graphical issues with KitKat on the Galaxy Nexus.
If you’re one of those many people out there still rocking the Galaxy Nexus, and not wanting to give it up just yet. It looks like you might get Christmas a bit early. As the new GPU binaries should definitely help out the Galaxy Nexus. Although, if you’ve held onto it this long, you’re probably due for an upgrade, since the device was released in November 2011. Hopefully this will help people get a long a bit more until the device finally chokes.
This is another reason why we love the developer community around Android. You won’t find a developer community like this behind the iPhone or anything iOS related. Back before I started here at AH, I had a couple of devices in which the manufacturer had given up on the device, but developers had continued to support it for years. Which was quite nice.

Is it real? It would be a big deal !
Do any ROM developers confirm it yet?

arshum said:
Is it real?
Click to expand...
Click to collapse
I sure hope its real!

Haven't heard much lately on this just what hashcode said and he didn't sound too promising. One ROM developer I seen tried it but was beyond his skills
Sent from my Galaxy Nexus using Tapatalk

Nothing is impossible ...
Sent from my Galaxy Nexus using xda app-developers app

I'm still very much active on this , its true its beyond my skill but that's how I learn . I'm hands on all the way , my nexus stays with the battery cover off 50% of the time lol , so don't fret , there might be hope yet .......
Sent from my Galaxy Nexus using Tapatalk

Will they solve glitches totaly?

krialix said:
Will they solve glitches totaly?
Click to expand...
Click to collapse
No one knows that

I would like to thank everyone that is working to make this happen!

this is outdated news
http://www.xda-developers.com/andro...possibly-aid-galaxy-nexus-kitkat-development/
please read the hashcode's reply
http://forum.xda-developers.com/showpost.php?p=47160722&postcount=309
new drivers are for Jellybean and not for KitKat

Well, even if it's only for Jelly Bean, i would want that. An Update is better than no-update

Spoderman said:
Well, even if it's only for Jelly Bean, i would want that. An Update is better than no-update
Click to expand...
Click to collapse
I would prefer updated Jellybean with updated drivers and with no WiFi/GPS/connectivity issues... hope Google will release a more stable Jellybean

Spoderman said:
Well, even if it's only for Jelly Bean, i would want that. An Update is better than no-update
Click to expand...
Click to collapse
I was thinking same thing.
Even of they ARE only good for4.2/4.3 improvements, I'd love to see them incorporated

[Q] When is it released? The Kitkat for Note 8.0

I'm really looking forward to KITKAT..

Nobody knows when or even if KitKat will be released for this tablet. Samsung does not provide timelines, the only way we know is through leaks. There haven't been any to my knowledge.

I doubt we will get it since we didn't get 4.3. Last time I buy a Samsung tablet
Sent from my HTCONE using Tapatalk

Samsung already forgot this machine.
Sent from my GT-N5120 using XDA Premium 4 mobile app

I think you guys are being a bit melodramatic. You have a perfectly functional tablet that doesn't have any outwardly obvious bugs or other problems. I bet you use it with no problems. Sure, it's nice to have the latest update, but it's not like you have significantly outdated software that limits your usage of the tablet. And should 4.4 land on this tab (for the record, I think it will), you guys will be happy for all of about 5 minutes and move on with your day. And of course as soon as a new minor update drops, the *****fest will begin again.
I am running custom build 4.4.2 on my Galaxy S4. Outside of some UI tweaks and ART, it brings nothing significant to the table.

Thats the attitude HTC had just before they started losing tons of money
Sent from my HTCONE using Tapatalk

FrozenRiff said:
Thats the attitude HTC had just before they started losing tons of money
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
There are many reasons why HTC is failing, but if this is even a reason, it's an insignificant one. Samsung has never been truly up to date on updates, yet they are second only to Apple in the amount of high-end devices sold. Most people, myself included don't really care whether we are on the latest version. We just care that our devices perform well and do what we need them to do. I only complain if an update screws something up.
And lets be honest here: you are running the latest version of all of the Google Apps. It's not like you are stuck on Gingerbread and being on Jelly Bean does not limit you in any way. KitKat will not boost your battery life, will likely not make your device faster, and does not add any significant features that would make a difference in your usage of the device. So what's the real issue? Because it's not that you are unhappy with your tablet.

sputnik767 said:
I think you guys are being a bit melodramatic. You have a perfectly functional tablet that doesn't have any outwardly obvious bugs or other problems. I bet you use it with no problems. Sure, it's nice to have the latest update, but it's not like you have significantly outdated software that limits your usage of the tablet. And should 4.4 land on this tab (for the record, I think it will), you guys will be happy for all of about 5 minutes and move on with your day. And of course as soon as a new minor update drops, the *****fest will begin again.
I am running custom build 4.4.2 on my Galaxy S4. Outside of some UI tweaks and ART, it brings nothing significant to the table.
Click to expand...
Click to collapse
I wish that was the case but it's not. I'm on the AT&T variant, and I'm still on 4.1.2. I have screen freezes (real and documented) and battery life isn't great. With that said, I haven't piled on the *****fest. But no matter what, this device really needs to get upgraded. I blame AT&T more than Sammy, but there is no reason why I should still be on 4.1.2 with a device that was announced in June 2013 with absolutely no word on when we'll get an update (either to 4.2, 4.3, or KK). That's pretty shameful. And with no releases of any kinds of source code or device info, we have no unlocked bootloader or custom ROMs. So, I'm basically on 2013 hardware with 2012 code.

esoh said:
I wish that was the case but it's not. I'm on the AT&T variant, and I'm still on 4.1.2. I have screen freezes (real and documented) and battery life isn't great. With that said, I haven't piled on the *****fest. But no matter what, this device really needs to get upgraded. I blame AT&T more than Sammy, but there is no reason why I should still be on 4.1.2 with a device that was announced in June 2013 with absolutely no word on when we'll get an update (either to 4.2, 4.3, or KK). That's pretty shameful. And with no releases of any kinds of source code or device info, we have no unlocked bootloader or custom ROMs. So, I'm basically on 2013 hardware with 2012 code.
Click to expand...
Click to collapse
I fully understand your concern. I have the Wifi-only tab and am on 4.2. I did not experience your issues with 4.1 but I do know that others have. The thing is, problems have to get fixed, and it's a shame that you are still dealing with them. I don't know if it's AT&T or Samsung in your case that's at fault though. My point was more to the effect that I don't care for software updates just for the sake of having a slight bump in version number.

esoh said:
I wish that was the case but it's not. I'm on the AT&T variant, and I'm still on 4.1.2. I have screen freezes (real and documented) and battery life isn't great. With that said, I haven't piled on the *****fest. But no matter what, this device really needs to get upgraded. I blame AT&T more than Sammy, but there is no reason why I should still be on 4.1.2 with a device that was announced in June 2013 with absolutely no word on when we'll get an update (either to 4.2, 4.3, or KK). That's pretty shameful. And with no releases of any kinds of source code or device info, we have no unlocked bootloader or custom ROMs. So, I'm basically on 2013 hardware with 2012 code.
Click to expand...
Click to collapse
Agreed. I am on the At&t Note 8.0 variant also and I too have freezes and lag. With that being said I know that At&t and Samsung don't have the best business relationship dye At&t loyalty to Apple. So an update may or may not come. If it does let's hope that At&t don't block or rip it up like they do with all Samsung updates
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

I got wifi only and I get freezes. The way to unfreeze is to turn the orientation of the note to landscape from horizontal and vice versa. I really wish for an update to fix that. And Yes htc has tons of problems but I believe the slow ass updates were the biggest driver of their customers (at least those who root their devices) to Samsung. Those people are also quite influential with their peers on recommendations
Sent from my HTCONE using Tapatalk

How much life is left on this device?

I am considering a new tablet and Amazon has a refurbished 8.4 for less than $200. It is the right size tab for my needs and the specs are better than my Asus TF700.
Does this device have any limits on what bootloaders can be unlocked? I don't want to be stuck with a safestrap device… I want a custom recovery that allows TWRP and custom ROMs.
Not seeing any 5.x ROMs for this device.
Should I consider this device, or is it nearing its "end of life" for support and development?

TWRP is easy with Odin. I've successfully installed CM11, SlimKat, and a couple of ROM posted on XDA. Lollypop - no idea.

I bought 8.4 Wifi from BestBuy and bootloader is easily unlocked.
I would expect Samsung to release one last update of Lollipop seeing as how it's only 1 year old, but you never know.
There is CM12 Lollipop Nightly in Original Development section. It's really stable for a nightly. It works flawlessly for me.

Does OTG work on this device on custom ROMs like the CM12 nightly?

duckredbeard said:
Does OTG work on this device on custom ROMs like the CM12 nightly?
Click to expand...
Click to collapse
Yes OTG works on cm12
Verstuurd vanaf mijn Nexus 5 met Tapatalk

IMO this is a dead device. only get if you plan to switch it to a custom rom like CM11 or CM12
check sammobile firmware list... there hasn't been anything new for this device since November (5 months) and even THAT was 4.4.2, which is an already out-of-date version of android
if you look in this forum history, there are various gullible people who were saying we would have already had a major update (or 2) by now... i say "ha-ha!" to them, they were so wrong

Another vote for CM12. It runs faster than TouchWiz, and looks nicer as well. Who need stock software when you have CM?
All Android tablets are unfortunately considered "disposable" by the manufacturers. They crank out a new version every year (or less), sell a few tablets, then rinse and repeat. Even if you moved onto something else, it would also be obsolete in less than a year.
The hardware works fine, and I plan to use it for some time yet. I don't expect any dazzling new tablets in the near future. Just incremental updates on what we already have. Cranking out "more of the same" is pretty much the name of the game in tablets for now.

Already got the tab. Second time it booted up I had it rooted. Third time booted had twrp installed. Fourth time booted had cm12.
Still getting settled in and it is soo much faster than my tf700.

Cyanogenmod has team up with qualcomm. They are supporting snapdragon 400,600,800 with future cyanogen mod and their own store. So i see some hope here . Correct me if i m wrong

6.0 port

NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious

cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.

cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.

Source already available
We should wait for devs to build it ?

AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.

Yap, waiting for you too @joel.maxuel for working on it

allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.

Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0

Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk

The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,