Related
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
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
...well, at least here: http://www.google.com/mobile/
(must visit from desktop)
Nothing special, but it's funny how we are close to the third GNex successor and they still won't update such an important web page.
Ahahahahah very funny!
Good news!
But GN will not have Android L
smilezou said:
But GN will not have Android L
Click to expand...
Click to collapse
I have ShinyROM on my GNex, but I'm prepared for the eventuality that this trusty phone will stop getting development support when Android L hits...
Should be just in time for me to get an upgrade anyway...
rjspring said:
I have ShinyROM on my GNex, but I'm prepared for the eventuality that this trusty phone will stop getting development support when Android L hits...
Should be just in time for me to get an upgrade anyway...
Click to expand...
Click to collapse
G1 got development up until jellybean. Grant it, it was not even close to daily driver, just a proof of concept. I suspect gnex will get support until the phone refuses to boot thev latest os
md1008 said:
G1 got development up until jellybean. Grant it, it was not even close to daily driver, just a proof of concept. I suspect gnex will get support until the phone refuses to boot thev latest os
Click to expand...
Click to collapse
I'd be happy if that is the case, the phone still works great. With the main ShinyROM developer starting to concentrate on other life tasks, hoping that OmniROM or Paranoid Android continue to carry the GNex flag.
All the devs are doing an amazing work on this phone. Today, MWisBest has updated the 3.0 kernel with the latest gpu driver for the OMAP chip, and the users that tried the FML rom beta with this trick are all entusiast!
Gnex will live for a long time yet!
Cyanognen MOD ROM
smilezou said:
But GN will not have Android L
Click to expand...
Click to collapse
You can have KitKat with Cyanogen Mod 11. Works fine. I ma enjoying it.
CyanogenMod will continue to support the international version of the galaxy nexus (maguro) but it have left the support of toro and toroplus
Sent from my Galaxy Nexus using XDA Free mobile app
I always thought that was a Nexus 4... Well I guess Google is just laughing in our faces
jackie_alden said:
All the devs are doing an amazing work on this phone. Today, MWisBest has updated the 3.0 kernel with the latest gpu driver for the OMAP chip, and the users that tried the FML rom beta with this trick are all entusiast!
Gnex will live for a long time yet!
Click to expand...
Click to collapse
I was among the enthusiasts and apart from camera [which i dont use a lot] everything else seems to be working fine even xposed and viper4android , and i am using ext4 fs FYI . My daily driver , pretty smooth and doesn't crash a lot
md1008 said:
G1 got development up until jellybean. Grant it, it was not even close to daily driver, just a proof of concept. I suspect gnex will get support until the phone refuses to boot thev latest os
Click to expand...
Click to collapse
ScardracS said:
CyanogenMod will continue to support the international version of the galaxy nexus (maguro) but it have left the support of toro and toroplus
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Doesn't matter. I'm still seeing almost daily updates for my Toro
Mini victory for gnex?
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,
Hi guys,
Going to buy the Nexus 7 soon b/c I can get it at a good price and my current tab, LG G Pad 7, is running too slow. Now although I am not too fussed if it gets Android N or not I just want to know what you guys, who own the Nexus, think.
Will the Nexus 7 2013 get Android N, what are the chances?
P.S. The main reason I would like N is b/c of the split screen feature, my G Pad comes with such feature as standard-courtesy of LG.
On this website for End of Life policies for Android and Chromebooks for the education sector it says that the Nexus 7 (2013) is supported until July 2017 but this could also just mean security updates, I wouldn't count on it.
https://support.google.com/chrome/a/answer/6220366?hl=en
Must people always post these silly questions? It'll be supported by Google or it won't; nobody here would know.
officially? chances are very slim.
unofficially with a ROM....100% yes. this is still a highly used device (its aged so well hasn't it?) so it'll get updated by some of the awesome Developers here.
I'm waiting to see if the supposed Nexus 7 2016 comes to fruition. If so, I'm grabbing that, and won't care about putting N on my 2013 model.
DaveImagery said:
I'm waiting to see if the supposed Nexus 7 2016 comes to fruition. If so, I'm grabbing that, and won't care about putting N on my 2013 model.
Click to expand...
Click to collapse
If they only put 2GB Ram in the 2016 version it will suffer the awful performance of the Nexus 9 and Nexus 5x. Lets hope they don't make the same mistake. I'd like to see the SD820 in the new version as the Tegra chips don't handle memory well and the intel chips have some compatibility issues.
As google dumped the Nexus 4 for M I think there is no chance of the N7 2013 getting N. The Nexus 4 could have easily ran M so Google can't use the hardware excuse.
tehabe said:
On this website for End of Life policies for Android and Chromebooks for the education sector it says that the Nexus 7 (2013) is supported until July 2017 but this could also just mean security updates, I wouldn't count on it.
Click to expand...
Click to collapse
Masteryates said:
As google dumped the Nexus 4 for M I think there is no chance of the N7 2013 getting N. The Nexus 4 could have easily ran M so Google can't use the hardware excuse.
Click to expand...
Click to collapse
What about the N Preview tags for both the Nexus 7 (2013) and the Nexus 5 found on the Google Git?
Google Git?
Masteryates said:
If they only put 2GB Ram in the 2016 version it will suffer the awful performance of the Nexus 9 and Nexus 5x. Lets hope they don't make the same mistake. I'd like to see the SD820 in the new version as the Tegra chips don't handle memory well and the intel chips have some compatibility issues.
As google dumped the Nexus 4 for M I think there is no chance of the N7 2013 getting N. The Nexus 4 could have easily ran M so Google can't use the hardware excuse.
Click to expand...
Click to collapse
As reported here (https://source.android.com/devices/tech/power/mgmt.html#doze-reqs), Doze requires a sensor that N4 doesn't have. So maybe N4 could get Marshmallow, but without Doze. Also Google said that two years of updates are guaranteed, but this doesn't mean that further major update can't come to N7 2013 and N5, only that maybe can arrive, maybe not. also, if i remember correctly, Marshmallows was out on october 2015, N7 2013 was out on August 2013, more than two years then. But N7 2013 was updated to marshmallow. At this moment, i don't see features in android N that cannot be implemented in N5 and N7 2013.
lupohirp said:
As reported here (https://source.android.com/devices/tech/power/mgmt.html#doze-reqs), Doze requires a sensor that N4 doesn't have. So maybe N4 could get Marshmallow, but without Doze. Also Google said that two years of updates are guaranteed, but this doesn't mean that further major update can't come to N7 2013 and N5, only that maybe can arrive, maybe not. also, if i remember correctly, Marshmallows was out on october 2015, N7 2013 was out on August 2013, more than two years then. But N7 2013 was updated to marshmallow. At this moment, i don't see features in android N that cannot be implemented in N5 and N7 2013.
Click to expand...
Click to collapse
Thanks for the correction Lupo.
Doubt any Nexus 4 owners would buy in to that excuse from Google though. Its funny that with the 4's awful battery, it is the device that could benefit from M and doze the most.
Masteryates said:
Google Git?
Click to expand...
Click to collapse
I can't post links yet, but separate source and com with a period.
android.googlesourcecom/device/asus/flo/+/android-n-preview-1
khaytsus said:
Must people always post these silly questions? It'll be supported by Google or it won't; nobody here would know.
Click to expand...
Click to collapse
Yeah well I am only asking for people's opinions (I am new to this device/forum), lets be honest everyone, including you, would want the next android version.
lupohirp said:
As reported here (https://source.android.com/devices/tech/power/mgmt.html#doze-reqs), Doze requires a sensor that N4 doesn't have. So maybe N4 could get Marshmallow, but without Doze. Also Google said that two years of updates are guaranteed, but this doesn't mean that further major update can't come to N7 2013 and N5, only that maybe can arrive, maybe not. also, if i remember correctly, Marshmallows was out on october 2015, N7 2013 was out on August 2013, more than two years then. But N7 2013 was updated to marshmallow. At this moment, i don't see features in android N that cannot be implemented in N5 and N7 2013.
Click to expand...
Click to collapse
Thanks for the detailed insight. As you mention it is an old device we'll be lucky if we got the next version but if we don't it is fine, as a student I need a tab that works fast and that I can carry around with me. My current LG tab is running slow af hence the I bought the Nexus 7. There are rumours of there being a 2016 edition but nonetheless it will be way out of my price range.
tehabe said:
On this website for End of Life policies for Android and Chromebooks for the education sector it says that the Nexus 7 (2013) is supported until July 2017 but this could also just mean security updates, I wouldn't count on it.
https://support.google.com/chrome/a/answer/6220366?hl=en
Click to expand...
Click to collapse
Hmm, if I had to take a guess the consumer EoL would probably be sooner, I assume the education versions run on modified android firmware which will allow them to get further security updates. Who knows though-I may be wrong.
Edit: Should've multiquoted my previous posts.
TAG_610 said:
What about the N Preview tags for both the Nexus 7 (2013) and the Nexus 5 found on the Google Git?
Click to expand...
Click to collapse
Masteryates said:
Google Git?
Click to expand...
Click to collapse
TAG_610 said:
I can't post links yet, but separate source and com with a period.
android.googlesourcecom/device/asus/flo/+/android-n-preview-1
Click to expand...
Click to collapse
Don't go by those git tags as Google automatically generates them for currently supported devices at time of publish. Doesn't mean that they will be supported at time of final release.
For example with Marshmallow, N4, N7 (2012), and N10 all had preview tags on Git as they were supported at time the preview code was publish but did not get final releases.
Maybe / Maybe Not
Look more closelyer. The tag isn't some stub, I checked deb branch and there have been three commits to the tree that are deb specific. This doesn't mean there will be a release but it does mean someone is actually working on the project. Could be a N7 enthusiast at Google playing in their paid spare time Google gives it's employees. Honestly I doubt there will be a release but there may be more clues here than we think. I'll clone the last release and this "preview" and do a diff. If the result shows its worth a try I *might* have time to attempt a build and see if it will build or not. If it builds it's probably not just autogenerated but active.
If it won't build its probably purely a unintentional creation by a script. :angel:
bgiesing said:
Don't go by those git tags as Google automatically generates them for currently supported devices at time of publish. Doesn't mean that they will be supported at time of final release.
For example with Marshmallow, N4, N7 (2012), and N10 all had preview tags on Git as they were supported at time the preview code was publish but did not get final releases.
Click to expand...
Click to collapse
FoxysWorkplace said:
Look more closelyer. The tag isn't some stub, I checked deb branch and there have been three commits to the tree that are deb specific. This doesn't mean there will be a release but it does mean someone is actually working on the project. Could be a N7 enthusiast at Google playing in their paid spare time Google gives it's employees. Honestly I doubt there will be a release but there may be more clues here than we think. I'll clone the last release and this "preview" and do a diff. If the result shows its worth a try I *might* have time to attempt a build and see if it will build or not. If it builds it's probably not just autogenerated but active.
If it won't build its probably purely a unintentional creation by a script. :angel:
Click to expand...
Click to collapse
And the same thing happened last time also. The only code they released is what's required under GPL but doesn't automatically equal guaranteed release.
Ok so maybe they do release N for the device but the point is that the git tags themselves aren't a guarantee that we are getting N.
Sent from my BLU ENERGY X PLUS using Tapatalk
FoxysWorkplace said:
Look more closelyer. The tag isn't some stub, I checked deb branch and there have been three commits to the tree that are deb specific. This doesn't mean there will be a release but it does mean someone is actually working on the project. Could be a N7 enthusiast at Google playing in their paid spare time Google gives it's employees. Honestly I doubt there will be a release but there may be more clues here than we think. I'll clone the last release and this "preview" and do a diff. If the result shows its worth a try I *might* have time to attempt a build and see if it will build or not. If it builds it's probably not just autogenerated but active.
If it won't build its probably purely a unintentional creation by a script. :angel:
Click to expand...
Click to collapse
Project is active, but this doesn't mean anything. Also, if you download the sources with N-Preview Tag, you will obtain only Android 6.0.1. ANdroid N is not released to AOSP. Source code will be pushed with final release.So the only thing is wait. Howewer, don't worry. I'm planning to do a fake Nexus Rom for N5 and N7 2013 when Android N will be pushed to AOSP.
On a side note, today was the first day of using my Nexus 7 properly, I noticed choppiness whilst playing games-namely minecraft. Anyone else also experienced this? Mine is running the latest MM firmware.
Yes, some games are lagging in MM but not on Kit Kat.
Gesendet von meinem Nexus 5 mit Tapatalk