Hi,
I started seeing 4.0.4 available in some ROMS. I have been running 4.03 on AOKP for the past couple weeks, but where is the official release of 4.03 ??
I monitor this site every day: http://code.google.com/android/nexus/images.html
Why dows people flashing 4.04 and 4.03 here and there but Google dont release officially those builds??
Thanks.
4.0.4 isn't in any ROMs, modaco is a hybrid and CDMA might have some deodexed versions of 4.0.4
4.0.3 is tagged in AOSP, so we can build that. The only 4.0.4 ROMs will be for CDMA Galaxy Nexus AFAIK, and there can't be a source built 4.0.4 ROM until it is tagged and released in the AOSP tree.
4.0.3 was released on the Nexus S and found to have a few issues so it's been pulled. Because of that, it would appear Google thought twice about releasing it on their flagship dev phone so are holding off until they get a nice build - rumoured to be 4.0.5 but nothing confirmed so far
The latest OTA update is up to 4.02 only. All other versions are unofficial leaked/custom ROMs.
MilkPudding said:
The latest OTA update is up to 4.02 only. All other versions are unofficial leaked/custom ROMs.
Click to expand...
Click to collapse
4.0.3 isn't leaked. It's in AOSP repo, yes it's in custom ROMs but you can compile a AOSP 4.0.3 only version as if it was a OTA.
just to underline what's already been said;
you can build 4.0.3 tag from aosp;
you can also build from aosp master branch: this is the bleeding edge branch of aosp. in other words, in terms of the android dev tree, master has all the latest fixes (and "features") of ics.
Sorry to come in all noob and stuff. Just a quick one, what's AOSP?? = /
Helmet321 said:
Sorry to come in all noon and stuff. Just a quick one, what's AOSP?? = /
Click to expand...
Click to collapse
Android Open Source Project.
http://lmgtfy.com/?q=What+is+AOSP?#
Related
Can anyone port ICS to our defy from aosp??
Of course we can, and of course it will be ported...if you people read a bit before posting you would learn that the next version of CyanogenMod with ICS will be CM9. The SDK was just released yesterday so leave them time to work on it . Plus, with our bootloader locked, Quarkx will probably have to make a version of CM9 with the Defy+'s Gingerbread Kernel (our actual one being the Froyo kernel, but i guess it would be too old for an ICS port)
Voilaaa
Sent from my CM7 Defy
crakeron said:
Of course we can, and of course it will be ported...if you people read a bit before posting you would learn that the next version of CyanogenMod with ICS will be CM9. The SDK was just released yesterday so leave them time to work on it . Plus, with our bootloader locked, Quarkx will probably have to make a version of CM9 with the Defy+'s Gingerbread Kernel (our actual one being the Froyo kernel, but i guess it would be too old for an ICS port)
Voilaaa
Sent from my CM7 Defy
Click to expand...
Click to collapse
I thought that CM8 will come with ICS. Where I can find this information on cyanogenmod site?
crakeron said:
Of course we can, and of course it will be ported...if you people read a bit before posting you would learn that the next version of CyanogenMod with ICS will be CM9. The SDK was just released yesterday so leave them time to work on it . Plus, with our bootloader locked, Quarkx will probably have to make a version of CM9 with the Defy+'s Gingerbread Kernel (our actual one being the Froyo kernel, but i guess it would be too old for an ICS port)
Voilaaa
Sent from my CM7 Defy
Click to expand...
Click to collapse
Ofcourse not!! As there will be no no SDK port of ICS on CM (source : CM team). We'll only get a port when the official ICS source is out.
Sent from Android 2.3.7
ryan8r said:
Ofcourse not!! As there will be no no SDK port of ICS on CM (source : CM team). We'll only get a port when the official ICS source is out.
Click to expand...
Click to collapse
And right you are.
CM8 as intended for the honeycomb version but its source never released. Thus CM8 wont be there. Hope the same wont happen with ICS. According to an old statment by google ICS source should be released
So, what's the difference between "4.0.4 merged into build" vs true 4.0.4 AOSP builds?
And the same question for kernels with "4.0.4 merged into build" vs true 4.0.4 kernels?
Will it get better when the devs are going to build from 4.0.4 source from the ground up?
Cuz until now I'm not really that impressed with the 4.0.3/4 "hybrid" builds (i.e. I find LiquidSmooth v1.2 a lot smoother/ faster/ better on battery than the AOKP b29 "4.0.4 merged" build)
Just curious
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
adrynalyne said:
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
Click to expand...
Click to collapse
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Ti2 said:
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Click to expand...
Click to collapse
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Ti2 said:
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Click to expand...
Click to collapse
There are some things in the work (besides 4.0.4) that need to be finished yet, but I would say it won't be much longer.
adrynalyne said:
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Click to expand...
Click to collapse
Have you released a 4.0.4 rom mate?
Stretlow said:
Have you released a 4.0.4 rom mate?
Click to expand...
Click to collapse
We have merged with 4.0.4, but we havent released an update yet, no.
I'm running Jelly Bean on my Verizon GN with the kernel that came with it. Is there a better one I should be using?
Sent from my Galaxy Nexus using Tapatalk 2
I was using Fanco 216 For a while and it ran great I just flashed trinity Alpha 28 and i have heard good things about it, try one of those
Stock? Havn't found a kernel yet which doesn't lag for me atleast =] i dont mean extreme lag just little stutters that i didn't noticed when using stock
I've been happy with the GlaDos 2.0RC on JB so far..
I'm happy with the stock one for now.
trinity kernel, the way google wanted jellybean to be ran. here, experimental tab http://www.derkernel.com/jbtuna.php#
Franco 216 is easily the best
Stock. Had issues with franco.
Loki047 said:
Stock. Had issues with franco.
Click to expand...
Click to collapse
Where can I get the stock version. I'm running the sprint version are you jelling rc1
sent from my SAMSUNG GALAXY NEXUS with ANDROID 4.1 JELLY BEAN
Stock. I tried some and they were horrible. Franko was always nice but on jb it made it ten times slower, i have never ever experienced so much lag before. Stock is fast, does not lag, gets nice battery consumption so why would you even consider tinkering around.
Stock. its the smoothest for me so far
Can anybody give Me a link for the stock kernel thanks in advance
sent from my SAMSUNG GALAXY NEXUS with ANDROID 4.1 JELLY BEAN
Just like any 'what kernel should I use with _____' thread, answers will never be objective and will be based on individual results which will not necessarily be reproducible on every handset. There are already multiple threads asking what the best kernel is for 4.1.
Also:
1. Android 4.1 Jelly Bean has not been released. A developer preview does not count.
2. Android 4.1 Jelly Bean sources have not been released
edgargurrola01 said:
Can anybody give Me a link for the stock kernel thanks in advance
sent from my SAMSUNG GALAXY NEXUS with ANDROID 4.1 JELLY BEAN
Click to expand...
Click to collapse
I saw a link to the stock kernel in this thread: http://forum.xda-developers.com/showthread.php?t=1738018. It should work with any galaxy nexus variant, but as always, flash at your own risk and nandroid first.
JaiaV said:
Just like any 'what kernel should I use with _____' thread, answers will never be objective and will be based on individual results which will not necessarily be reproducible on every handset. There are already multiple threads asking what the best kernel is for 4.1.
Also:
1. Android 4.1 Jelly Bean has not been released. A developer preview does not count.
2. Android 4.1 Jelly Bean sources have not been released
3. Android 4.1 Jelly Bean kernel sources have not been released. Kernel mods are done on decompiled software which is never as reliable as modifying source.
Click to expand...
Click to collapse
think you're wrong on 3. google did release source for 4.1 kernel
ceejay83 said:
think you're wrong on 3. google did release source for 4.1 kernel
Click to expand...
Click to collapse
Edit: correct. 4.1 kernel source was released. I missed it.
been running Lean kernel, and its my first "non-stock" kernel since flashing jellybean last week. gotta say I love it so far. great battery life, and just as smooth as stock as far as my use goes. I got 4 1/2 hrs of screen on time tody with it. on WiFi all day, but still happy
dschoenike
molesarecoming said:
Stock. I tried some and they were horrible. Franko was always nice but on jb it made it ten times slower, i have never ever experienced so much lag before. Stock is fast, does not lag, gets nice battery consumption so why would you even consider tinkering around.
Click to expand...
Click to collapse
My feelings exactly... I have always been a Franko kernel user previously, but I found his JB kernel to be very choppy. I then went and reflashed the ROM(didn't know where to get the actual stock kernel from) so I could go back to the stock kernel and I am happy again! lol
But it really is a personal choice which depends a lot on what you individually want to do with your phone.
JaiaV said:
Just like any 'what kernel should I use with _____' thread, answers will never be objective and will be based on individual results which will not necessarily be reproducible on every handset. There are already multiple threads asking what the best kernel is for 4.1.
Also:
1. Android 4.1 Jelly Bean has not been released. A developer preview does not count.
2. Android 4.1 Jelly Bean sources have not been released
3. Android 4.1 Jelly Bean kernel sources have not been released. Kernel mods are done on decompiled software which is never as reliable as modifying source.
Click to expand...
Click to collapse
JaiaV said:
Where?
Click to expand...
Click to collapse
kernel source was released the same day that the google io attendies received JellyBean. since google released it, they legally have to provide kernel source according to the GPL. our kernel devs here all follow GPL as well, thats one of the requirements of xda to allow them to post their custom kernels. btw, source is where it always is. please dont insult our wonderful kernel developers.
From: "Jean-Baptiste Queru" <[email protected]>
Date: Jun 27, 2012 4:29 PM
Subject: [android-building] GPL components for the Jelly Bean preview
To: <[email protected]>
As usual, Android 4.1 ("Jelly Bean") contains a few components
licensed under the GPL or similar licenses. For the preview that was
just announced at Google I/O, the source code of those components is
available in AOSP.
The JFN53F platform components are tagged android-4.1_pre1 in their
respective projects. That's the version that Nexus 7 has in the box.
The JRN84D platform components are tagged android-4.1_pre2 in their
resepctive projects. That's the automatic update for both Nexus 7 and
Galaxy Nexus.
The SDK platform components are tagged android-4.1-sdk_pre1 in their
resepctive projects.
They are available with full source history. They are fully merged
into the master branch (except webkit). They all build on top of the
current AOSP master.
The Nexus 7 kernels are in the kernel/tegra project, under SHA-1
8dd2eab (in the box) and 55edff4 (the update). The Galaxy Nexus kernel
is in the kernel/omap project, under SHA-1 e8de0e2. They all have full
source history.
JBQ
Click to expand...
Click to collapse
simms22 said:
kernel source was released the same day that the google io attendies received JellyBean. since google released it, they legally have to provide kernel source according to the GPL. our kernel devs here all follow GPL as well, thats one of the requirements of xda to allow them to post their custom kernels. btw, source is where it always is. please dont insult our wonderful kernel developers.
Click to expand...
Click to collapse
Yeah...sorry for the incorrect info. I've been checking since I was corrected, and my git was broken and not pulling the source for 4.1.
Thanks.
I am running cm10 on my galaxy s3, the d2att version which is for AT&T. Since the Jelly Bean update is being released in the US now, and should be released by att soon, is it expected that the d2att CM10 will see a very stable update shortly after its release? The reason being that the developers will maybe be able to fix any bugs in the current roms since they will have the official release to pull from. or does it not work like that? thanks!
The CyanogenMod merger of the 4.2 code base in in progress, and they will not promise any dates at this point in time. From what I understand, it seems to be moving along well.
They tend to post progress updates on Google+ at regular intervals.
https://plus.google.com/117962666888533781522/posts/Bw5N6m7dPSa
I'm wondering about the hboot incompatibility thing. Will devs over at Original Android Development start making kernels and roms for the hboot that will come with JB?
Well JB has been officially released in some parts of the world with hboot 1.36 and 1.33 and there hasn't been any issues with custom ROMs yet. Can't say the same for kernels because source hasn't been released yet.
Yes, once the source is released for the JB kernel, the kernels will be updated too.
But will HTC ever release the kernel sources for JB ?
Seelendrache said:
But will HTC ever release the kernel sources for JB ?
Click to expand...
Click to collapse
Yes, it usually takes them around 30 days, I beleive, so they should start appearing for the released Taiwanese (HTC__621) OTA pretty soon.
BenPope said:
Yes, it usually takes them around 30 days, I beleive, so they should start appearing for the released Taiwanese (HTC__621) OTA pretty soon.
Click to expand...
Click to collapse
So with this the GPS Bug in Kernels can be fixed ?
Yep
So you are saying that most of the devs at Original Android Development (CM10, AOKP, AOSP) will start making kernels for newer hboots?
Sent from my EndeavorU using xda app-developers app
ViktorN said:
So you are saying that most of the devs at Original Android Development (CM10, AOKP, AOSP) will start making kernels for newer hboots?
Click to expand...
Click to collapse
I have no idea of their intentions, but I don't see why they wouldn't.