Hi,
Now I did search as much as possible on the interwebs, like tiamat's blog, xda, miui forums etc. So I guess I'll go ahead and ask this sorta noob question eek: oh no he didn't ).
Why are there no 3.0 kernels and what would be the advantage of them? On a tangent, I note that even the transformer prime has no 3.0 kernel...
Sent from my Incredible 2 using XDA
What in the name of balls is a 3.0 kernel?
Amphibliam said:
What in the name of balls is a 3.0 kernel?
Click to expand...
Click to collapse
Linux kernel version 3.x. As in we are currently using kernel version 2.6.35.x.. Galaxy nexus has 3.08 kernel or something.
Sent from my Incredible 2 using XDA
We're currently using modified gingerbread kernels (the 2.6 ones i think?) because we havent received kernel source from HTC yet
This phone is slated for an ICS update, once we get that and kernel source i'm pretty sure a 3.0 kernel will follow
It's because we don't have an official update yet. That's what all the ICS roms are pretty much waiting for - an offical ICS kernel from HTC.
dirkdigles said:
It's because we don't have an official update yet. That's what all the ICS roms are pretty much waiting for - an offical ICS kernel from HTC.
Click to expand...
Click to collapse
Okay. So as I understand the kernel will have several proprietary modules and therefore we can't compile our own 3.0 kernel yet? As it may cause several incompatibilities, am I right?
Sent from my Incredible 2 using XDA
litetaker said:
Okay. So as I understand the kernel will have several proprietary modules and therefore we can't compile our own 3.0 kernel yet? As it may cause several incompatibilities, am I right?
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
No, we just can't compile one because we don't have source.
Swyped From My MikRunny'd Superphone Using TapaTalk 2
tylerlawhon said:
No, we just can't compile one because we don't have source.
Swyped From My MikRunny'd Superphone Using TapaTalk 2
Click to expand...
Click to collapse
I am confused. The linux kernel is open source. So the Source code for the 3.0 kernel is available. So, what do you mean by "we don't have source"? Are you referring to any drivers whose modules we may not have as they are proprietary? Or something else?
Anyway, I just realized thanks to this article that the 3.0 kernel is no big deal and has no new, "awesome" features and is not a major jump like the GB to ICS, or gnome 2 to gnome 3, or the KDE 3 to KDE 4 jump... Just a new numbering scheme. So, may be the kernel we have now is more than enough to run ICS (except for the camera glitch though...)
Thanks for the responses guys!
litetaker said:
I am confused. The linux kernel is open source. So the Source code for the 3.0 kernel is available. So, what do you mean by "we don't have source"? Are you referring to any drivers whose modules we may not have as they are proprietary? Or something else?
Anyway, I just realized thanks to this article that the 3.0 kernel is no big deal and has no new, "awesome" features and is not a major jump like the GB to ICS, or gnome 2 to gnome 3, or the KDE 3 to KDE 4 jump... Just a new numbering scheme. So, may be the kernel we have now is more than enough to run ICS (except for the camera glitch though...)
Thanks for the responses guys!
Click to expand...
Click to collapse
The Linux kernel is, yes. However, a kernel is very device specific. So, without having one from an OTA or better yet, HTC releasing kernel source code for this device specifically, we can't make any. So far (as stated before), all our ics ROMs are using hacked up gingerbread kernels (which is an incredible feat in itself). We have basic kernel source code, sure, but what we're lacking is the proprietary drivers, libs, and other stuff that makes this device run.
Hope this all made sense.
Swyped From My MikRunny'd Superphone Using TapaTalk 2
Each kernel is device specific with the oem s specific changes....it is possible to build one without the.exact source...but you would need some similar source for reference like teamhacksung using the nexus s as a base for sgs phones
tylerlawhon said:
The Linux kernel is, yes. However, a kernel is very device specific. So, without having one from an OTA or better yet, HTC releasing kernel source code for this device specifically, we can't make any. So far (as stated before), all our ics ROMs are using hacked up gingerbread kernels (which is an incredible feat in itself). We have basic kernel source code, sure, but what we're lacking is the proprietary drivers, libs, and other stuff that makes this device run.
Hope this all made sense.
Swyped From My MikRunny'd Superphone Using TapaTalk 2
Click to expand...
Click to collapse
Yes, this helps me understand it better. Anyway, I'm not really waiting for the 3.0 kernel anymore as I learned it was just a renumbering scheme! I was expecting I could launch a space shuttle with it, like I can drive my car supersonic with ICS (hehehe..) But it apparently has just the usual dose of bug fixes compared to our current kernel.
Thanks y'all!
Related
I know the 2.3 SDK is out and some builds have popped up showcasing some basic gingerbread features. I am curious as to when we can expect to see stable builds of gingerbread appear that can be used as a daily ROM.
I wasnt in the root and ROM game when Froyo was released so i have no concept of what to expect. Does the release of the Nexus S bring us closer? Will we have to wait for Verizon devices to receive the update?
A few weeks after source is released.
I would say shortly after the source code is released; exactly how fast depends on how much has to be done for it to be made compatible. You will see stock OS and kernels first.. sense will follow much later.
do we know when the source code will be released?
I am pretty sure source the source was releases today for the N 1
Sent from my Incredible using XDA App
Kernel sources are different from the android system that we need
Patience, OP, patience.
If you can't wait, get to work on it!
I am not a huge fan of vanilla android, but I will try out some gingerbread, but I would prefer gingerbread with sense!
I don't think its out of the question to see a daily driver after a system dump of the nexus one/s is pulled.
Sent from my ADR6300 using XDA App
thehoovie said:
was releases today for the N 1
Click to expand...
Click to collapse
it was just the kernel, and from nexus s
What is an aosp kernel? How is it different from the kernels we have like Genocide or even stock? What is different between CM7's kernel and our EF02 kernel?
ugothakd said:
What is an aosp kernel? How is it different from the kernels we have like Genocide or even stock? What is different between CM7's kernel and our EF02 kernel?
Click to expand...
Click to collapse
Asop Colonel?.......
Sent from my SPH-D700 using XDA Premium App
Roughly, it's the Nexus kernel ported to the Epic. Though, I believe they need the GB source for Epic to figure out what to alter to make it work properly. The other option is to build it from the ground up, which they're also attempting.
ugothakd said:
What is an aosp kernel? How is it different from the kernels we have like Genocide or even stock? What is different between CM7's kernel and our EF02 kernel?
Click to expand...
Click to collapse
Aosp means android open source project. An aosp kernel, or rom, is one built from googles source, not samsungs.. and lacks proprietary drivers and/or software...
Cm7 is basicaly an aosp kernel, but with attempts to boot on epic.. it also includes changes made by cyanogenmod team
Sent from my SPH-D700 using XDA App
So its a kernel from android source, from google. But doesn't have drivers that samsung's source has? Why aren't samsung's sources merged/included/whatever into google's source?
ugothakd said:
So its a kernel from android source, from google. But doesn't have drivers that samsung's source has? Why aren't samsung's sources merged/included/whatever into google's source?
Click to expand...
Click to collapse
Htc and moto would be mad at google for bricking their customers phone.
They are merged when Samsung releases its version.
Sent from Godot's place.
ugothakd said:
So its a kernel from android source, from google. But doesn't have drivers that samsung's source has? Why aren't samsung's sources merged/included/whatever into google's source?
Click to expand...
Click to collapse
Depending on what you meant, the would be. Ultimately they COULD start over if they wanted to, I imagine, but they don't. It's google's kernel + how to actually work this specific hardware. People are waiting for the "work this specific hardware" changes, not really the google part.
Mainly they're waiting because it's not worth investing 2 months into figuring out something that's going to be handed to you in 2 months.
vita10gy said:
Mainly they're waiting because it's not worth investing 2 months into figuring out something that's going to be handed to you in 2 months.
Click to expand...
Click to collapse
+1
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx
So I know what AOKP and AOSP both stand for, but I'm not quite sure what they are. What makes it so that some ROMs called themselves AOSP but others don't? I thought AOSP just meant Android Open Source Project... so wouldn't every ROM be an AOSP that isn't the stock Sprint ROM?
Another question I have is about Android 4.0.4. From my understanding, most ROMs are Android 4.0.3. But if the Sprint leaks are all 4.0.3, where are people getting 4.0.4 from? What are the major differences anyways?
Sorry for the noob questions. I've just been wondering for awhile and whenever I search, I can never find a good description asides from what the acronyms AOKP and AOSP stand for.
Most roms that call themselves AOSP are made to look as close as possible to stock android. Also, the reason we are able to have Android 4.0.4 roms is because those roms are ports from other devices rather than built straight from the leaks. The only noticeable difference between 4.0.3 and 4.0.4 is better battery life.
faceyourfaces said:
Most roms that call themselves AOSP are made to look as close as possible to stock android. Also, the reason we are able to have Android 4.0.4 roms is because those roms are ports from other devices rather than built straight from the leaks. The only noticeable difference between 4.0.3 and 4.0.4 is better battery life.
Click to expand...
Click to collapse
Ohh makes sense, thanks. What about AOKP then? Would that be everything else? I always heard that Kang meant to either improve on someone's ideas or steal it.
AOSP is straight up Android, no manufacturer over lay (TouchWiz, Sense, Blur). The AOSP roms tend to have a lot more tweaks and customizability since they are built from Android source, and our devs, as generous as they are, like to include goodies for us to make our phones as cool as possible.
AoSP (aokp,cm9,codename) are built from Google's source repos. This is also where 4.0.4 is from, its the next update for ICS with many bug fixes including video(Netflix,YouTube) and video in browser working, as well as many other numerous bug fixes within the code. The manufacturers have 4.0.3 have already put alot of work into it and will continue using it as their base until they have the initial release out then will start merging 4.0.4 into their upstream, to be included I'm the next round of OTA's. Anything 4.0.4 is AOSP meaning pure android no 3rd party manufacturer UI such as TouchWiz(Samsung),Blur(Motorola),or Sense(HTC). AOSP is what ships on the Nexus line, also called the Google experience.
Sent from my SPH-D710 using xda premium
iniz94 said:
Ohh makes sense, thanks. What about AOKP then? Would that be everything else? I always heard that Kang meant to either improve on someone's ideas or steal it.
Click to expand...
Click to collapse
Kang does mean stolen code. AOKP is a rom built by a group that likes to call themselves Team Kang.
Makes a lot of sense, thanks everyone! Never knew that aosp was a customized vanilla rom
Sent from my SPH-D710 using XDA
faceyourfaces said:
Kang does mean stolen code. AOKP is a rom built by a group that likes to call themselves Team Kang.
Click to expand...
Click to collapse
Stolen? Like from other programmers Roms? Does the scene support this?
Sent from my Epic 4g Touch running Blazer 4.1 using xda premium
Android is open source meaning no one owns anything, its all shared under the Apache license. So technically no one is stealing anything, a Kang is using other developers code and either adding your own onto it or combining multiple sources to make the existing code better
Sent from my SPH-D710 using xda premium
I have a quick question, why do I have to go back to a rooted EL26 to flash AOKP/AOSP? Why can't I use the current recovery like rouge recovery? Is it not the same?
abusedcloth said:
I have a quick question, why do I have to go back to a rooted EL26 to flash AOKP/AOSP? Why can't I use the current recovery like rouge recovery? Is it not the same?
Click to expand...
Click to collapse
I believe it is to avoid bricking of phones. Ics rouge is known to brick phones so that's why you can't flash using well not recommended
Sent from my SPH-D710 using Tapatalk 2 Beta-5
daniel4653 said:
I believe it is to avoid bricking of phones. Ics rouge is known to brick phones so that's why you can't flash using well not recommended
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
What about EL29 rouge recovery?
Sent from my SPH-D710 using xda premium
EL29 is a repacked version of CWM, ICS flashes are most successful on bare CWM. You go to EL26 (a stock CWM) to help prevent issues, its the safest route to (and from) ICS
CyberpodS2 said:
Stolen? Like from other programmers Roms? Does the scene support this?
Click to expand...
Click to collapse
-EViL-KoNCEPTz- said:
Android is open source meaning no one owns anything, its all shared under the Apache license. So technically no one is stealing anything, a Kang is using other developers code and either adding your own onto it or combining multiple sources to make the existing code better
Click to expand...
Click to collapse
I never said anything about how the word Kang applies to Android. In general it means stolen code but in this case it means improving on the source code.
Will The Droid Inc Ever Get a 3.0.X.X. Kernel?
Officially? Highly doubtful. That doesn't stop someone from porting it, though.
PonsAsinorem said:
Officially? Highly doubtful. That doesn't stop someone from porting it, though.
Click to expand...
Click to collapse
Official Is Over rated xDD.
I'm talking about a dev compiling a 3.0.X Kernel, it'll make everything else run smoother.
ericerk said:
Official Is Over rated xDD.
I'm talking about a dev compiling a 3.0.X Kernel, it'll make everything else run smoother.
Click to expand...
Click to collapse
It wouldn't be worth the work. I have been told by a few kernel devs that it would create more problems.
Sent from my Nexus 7 using XDA Premium HD app
Albinoman said:
It wouldn't be worth the work. I have been told by a few kernel devs that it would create more problems.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
The Droid 3 has kexec 3.0.8 Kernel.
We have an unlocked boot loader with 2.6.x.x. its kinda sad.
Then again this phone is 2 years old. But i just don't want to see this little device die.
A hybrid 2.6.38/3.0.x kernel might be possible, although it still wouldn't be a pure 3.0.x kernel. One of the problems is that we don't have 3.0.x kernel drivers for the HTC incredible.
jellybellys said:
A hybrid 2.6.38/3.0.x kernel might be possible, although it still wouldn't be a pure 3.0.x kernel. One of the problems is that we don't have 3.0.x kernel drivers for the HTC incredible.
Click to expand...
Click to collapse
Wouldn't that help performance in ics roms and higher?
ericerk said:
Wouldn't that help performance in ics roms and higher?
Click to expand...
Click to collapse
Possibly. The jellybean interactive governor could improve performance with a small drop in battery life or you could just use the performance governor to help smooth things out. Newer version does not always mean better or faster especially with old devices.
Sent from my Galaxy Nexus using Tapatalk 2
With all this talk about how the gnex can't run 4.4 because ti no longer releases drivers for android and the 3.4 kernel being required, it's making my head spin. I've also heard my phone has always been on 3.4....wait what? Shouldn't all devices with the same android version run the same kernel? Now I'm hearing it's possible to build kitkat with the old kernel.... I'm going to go throw up and pass out...
Really just want some clarification on this subject
Sent from my Nexus 4 using Tapatalk
Cor-master said:
With all this talk about how the gnex can't run 4.4 because ti no longer releases drivers for android and the 3.4 kernel being required, it's making my head spin. I've also heard my phone has always been on 3.4....wait what? Shouldn't all devices with the same android version run the same kernel? Now I'm hearing it's possible to build kitkat with the old kernel.... I'm going to go throw up and pass out...
Really just want some clarification on this subject
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
1) Our phone's always been on 3.0 kernel, which was announced End Of Life this October.
2) Not necessarily new Android versions need new kernel versions. Even 2.6 kernel can run Android 4.1, which typically requires 3.0 or 3.4 kernel.
Sent from Samsung Galaxy Nexus @ CM10.2
Cor-master said:
With all this talk about how the gnex can't run 4.4 because ti no longer releases drivers for android and the 3.4 kernel being required, it's making my head spin. I've also heard my phone has always been on 3.4....wait what? Shouldn't all devices with the same android version run the same kernel? Now I'm hearing it's possible to build kitkat with the old kernel.... I'm going to go throw up and pass out...
Really just want some clarification on this subject
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
At the basic, the KERNEL is the low level base code on which all instructions are set. Lets say is in charge of dictate how things are done, again, at the very low level.
Thus Kernel is only needed if your phone has functions or features that are only found in that Kernel version. Lets say that kernel 3.4 has rules on how manage bluetooth 4.0 LE, but our Galaxy Nexus doesnt have Bluetooth 4.0.(Isnt ???). Those that kernel is not really required.
Things become more complex as you add more variables like memory managment, I/O managment, and those thing that improve over each update and maybe are needed in order to work with newer OS version.
I cant really tell you features that are needed in KitKat 4.4 against Kernel 3.4 not found in Kernel 3.0, so I'm not the man that can tell you if bringin(or the lack of) 4.4 to our GNex is a middle finger from Google or not.
Yeah I got curious about some stuff so I decided to manually look at what kernal every device is running. My 4 is 3.4 now, nexus 7 first gen is 3.1, my wife's nook with cm10.2 is 3.0, and my buddies gnexes are also 3.0, while the kitkat kernal is actually 3.8
Sent from my Nexus 7 using Tapatalk 4
Cor-master said:
Yeah I got curious about some stuff so I decided to manually look at what kernal every device is running. My 4 is 3.4 now, nexus 7 first gen is 3.1, my wife's nook with cm10.2 is 3.0, and my buddies gnexes are also 3.0, while the kitkat kernal is actually 3.8
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
But all AOSP KitKat builds (not ports) for Nexus 4 runs on 3.4. 3.8 is merely a speculation I've seen somewhere.
Sent from Samsung Galaxy Nexus @ CM10.2
AndyYan said:
But all AOSP KitKat builds (not ports) for Nexus 4 runs on 3.4. 3.8 is merely a speculation I've seen somewhere.
Sent from Samsung Galaxy Nexus @ CM10.2
Click to expand...
Click to collapse
Crazy. So is there any hope for the developer community to build kitkat Roms that fully work for the galaxy nexus or is development dead beyond 4.3 other than experimental builds that stuff like the front camera/GPS/Bluetooth doesn't work?
Sent from my Nexus 4 using Tapatalk
They'll have to hack it like jt did for the galaxy S.
Sent from my Galaxy Nexus using Tapatalk 2