Database Info

[Dev] AOSP Gingerbread

Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...

Here's my 2.6.36 kernel zImage file and .config build if anyone is curious.

My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board. With the Nexus S source out, some things shouldn't be TOO hard, but I think porting the CDMA stuff is probably a huge challenge.

plapczyn said:
My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board.
Click to expand...
Click to collapse
id jump on board if i knew what i was doing

Glad your focusing on this! I don't think we have to finish froyo to start gingerbread. Not sure how much I can help but hit me up if you need anything done.
Sent from my SPH-D700 using Tapatalk

I glad too see that someone is taking initiative here. My thinking all along is the drivers for froyo will most likely work in someway for gingerbread but without kernel source for froyo yet, I would think you would have to start from ground up. But good luck to you regardless.
Sent from my SPH-D700 using XDA App

This is delicious. Now it only needs sauce.
Everyone can learn from the OP's example. Less posturing more action.

msponsler said:
Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...
Click to expand...
Click to collapse
About time!

Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App

I have it just about booting(;
Sent from my SPH-D700 using XDA App

somedude0608 said:
Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I agree, I had froyo on my hero long before I even thought about switching to the epic.... and they've made so much progress on gingerbread... I often wonder whether I made the right choice or not going with the epic. Although the evo doesn't have a keyboard and is really square, it gets a lot of attention and has had many official updates. I wish samsung would get off of their asses and just release the source.

I'd love to help out any way I can. I'm not a programmer, but I hve a great understanding on what the issue is. I had a hero before the epic, and they have fully functional froyo despite never having kernel source. One would have to be built, cause I don't think samsung is going to really support us that much longer (if at all) and give us any hope for gingerbread source. The trickiest part is the cdma/wimax radios (wimax still not supported in cyanogenmod for evo).
Sent from my SPH-D700 using XDA App

bubby323 said:
I have it just about booting(;
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Did you build gingerbread from source?
What kernel are you using?
I built a 2.6.36 last night...but the more I thought about it, the more I realized it doesn't do me any good as it is right now.
I've downloaded samsung's kernel source for 2.6.29 and I'm trying to get the modules for the video, radio, etc... to compile with 2.6.36.
The nexus s is using 2.6.35, which is fine when it comes to the video drivers, wifi, and such....but it doesn't do us any good when it comes to 3G because tmobile doesn't use CDMA, so it wouldn't have the same radio kernel modules.
I'm currently running noobnl's cyanogenmod (froyo) on my epic, and that has a 2.6.32.9 kernel. I'll have to take a closer look at how you built that kernel.

Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App

nerdtaco said:
Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Seconded! I know nothing about developing software but I'm a pretty good test dummy =)

This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.

furysama said:
This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.
Click to expand...
Click to collapse
At this point I don't necessarily need any assistance. But thanks for all the offers!
If I have any questions / requests I'll sure to let everyone know!
Thanks!

The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?

furysama said:
The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?
Click to expand...
Click to collapse
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel

daryelv said:
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel
Click to expand...
Click to collapse
The reason it took the CM team so long is because they developed their own drivers from the ground up. I'm willing to bet that it's much easier to rip the drivers out of the kernel we already have than to replicate the work that the CM team did.
The GPL licensing is *why* the CM team developed their own drivers; not because its impossible to get Samsung's code, but because doing so would have violated the licensing terms of Samsung's code and of Cyanogenmod.

Do you need source code to build a custom rom?

I know a good one needs source, but can't it be done without source?
Edit: crap don't even know what this has to do with a g2x, sorry...

No. You do not need source to create a ROM. If you plan on basing it off of cm7 then you would likely want to compile your own copies to work with. But in general, no.
Sent from my LG-P999 using Tapatalk

smashpunks said:
I know a good one needs source, but can't it be done without source?
Edit: crap don't even know what this has to do with a g2x, sorry...
Click to expand...
Click to collapse
You can manipulate android however you want without source. However, you'll more or less be stuck within the confines of the OEM. Likewise, without source for things like HTC sense, ROMs based on that for the G2X for example are very difficult to get fully functional. We really don't know what in HTC sense to change to get that working with the device based on our hardware. More or less a custom ROM not based on source is still very similar to the original ROM you created it from, where as AOSP roms can be completely different. That's really a very generalized explanation, but that sums it up pretty well I think.

AOKP vs. AOSP

What are the differences between these two sources or whatever they are? Still confused what differentiates whitehawkx's AKOP based rom from the Eaglesblood AOSP rom?
Sent from my LG-P999 using XDA

AOSP = Android open source project.
source from google. Nothing added other then what is needed to make it work on the phone. (drivers)​
AOKP = Android open kang project
Close to aosp but with many enhancements added behind what is needed to make it work on the phone.​
Cyanogen mod would fall into the same category as AOKP.
Hope this helps.

painter_ said:
AOSP = Android open source project.
source from google. Nothing added other then what is needed to make it work on the phone. (drivers)​
AOKP = Android open kang project
Close to aosp but with many enhancements added behind what is needed to make it work on the phone.​
Cyanogen mod would fall into the same category as AOKP.
Hope this helps.
Click to expand...
Click to collapse
Thank you, that cleared up alot.
Sent from my LG-P999 using XDA

That's what i thought thanks for the confirmation

painter_ said:
AOSP = Android open source project.
source from google. Nothing added other then what is needed to make it work on the phone. (drivers)​
AOKP = Android open kang project
Close to aosp but with many enhancements added behind what is needed to make it work on the phone.​
Cyanogen mod would fall into the same category as AOKP.
Hope this helps.
Click to expand...
Click to collapse
as would all the other ROMs on here? hellfire, eaglesblood? they are made from CM7/9 correct? unless otherwise noted?

dodgefan67 said:
as would all the other ROMs on here? hellfire, eaglesblood? they are made from CM7/9 correct? unless otherwise noted?
Click to expand...
Click to collapse
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.

this explains alot

Klathmon said:
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.
Click to expand...
Click to collapse
binded2 said:
this explains alot
Click to expand...
Click to collapse
yeah it does, thanks Klathmon!!

thanks alot its so cleared now

Klathmon said:
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.
Click to expand...
Click to collapse
That's almost true. Even though it's AOSP and all from Google's Android source, they still used CM's source tree because they put everything together. No point in spending an enormous amount of time to put it together yourself if CM already did it. So technically it's still a large portion of CM's work.

ok, i got it...

Klathmon said:
not really, AOKP uses some CM9 stuff, but its definitely a proper ROM on its own.
Any rom that says AOSP in its name is generally Built from google source code, with little to nothing from CM7/9 other than what might be necessary to get things running.
MIUI is another rom that, while built from CM7/9 is VERY different.
ROM's like Hellfire, and others similar to it, are mostly just a proper CM7/9 ROM with tweaks, and small fixes put into it, and more recently (to my annoyance) other kernels too.
Overall, CyanogenMod was probably the greatest thing to happen to android modding as a whole, they provide a base for most things to branch off from (and they don't even complain when everyone and everything uses their source!) The only reason its in everything is because if its something that the user will not see, and it works, why spend the days/weeks/months to develop it when its sitting right on CyanogenMod's GIT.
Click to expand...
Click to collapse
Thanx for this information but i need to know more about the layers of the ROM that are there in AOSP and AOKP (i heard this from a friend that AOSP have 7 layers and AOKP has about 10 is that true? and the AOSP makes the interaction easier then that of the AOKP).

miku3191 said:
Thanx for this information but i need to know more about the layers of the ROM that are there in AOSP and AOKP (i heard this from a friend that AOSP have 7 layers and AOKP has about 10 is that true? and the AOSP makes the interaction easier then that of the AOKP).
Click to expand...
Click to collapse
What do you mean by "layers"?
Sent from my Nexus 7 using xda app-developers app

OG dev ROM v OG dev based ROM

Ok, so I'm not a tech pro. But molding my gadgets is becoming a hobby. I've learned unlocking and rooting.. I've started flashing ROMs and mods to stock roms.
Now I'm wondering, what's the difference between ROMs like pure AOKP vs ROMs based on other original roms like AOKP?
For example, I'm using Smoothrom on my grouper nexus 7 to boost performance/reduce lag/etc. It is a 4.3 Jellybean ROM based on AOKP. What is the difference v the AOKP ROM? added features baked in? Bugs within Aokp fixed?
This is question is just for knowledge sake, so please don't criticize any biases or wrong assumptions apparent in the language of the question. Please do address any inaccuracies or biases/assumptions that you notice. Like I said, this is just for me to better understand the motivation/benefits/risks/purposes behind roms like AOKP v AOKP Based (slimrom).
Sent from my Nexus 7 using Tapatalk

Okay basically everything that's made from scratch or source is pure. Roms that mention they are based on these so called "aosp" "aokp" is pretty much the same thing as the one built from source but its been modified, for example cyanogenmod is built from source, if you download it and modify the ROM, enhance it a bit more, add more features you will have to say it is based on cm as you didn't build it from source or scratch. You used the ROM as a base for your project. Like something you can start from.
Its like a car. A person that owns a car and modifies it, but its based on the original. The original is initially made by scratch. I hope I made sense. Sounded better in my head
Sent from my Nexus 5 using Tapatalk

krishneelg3 said:
Okay basically everything that's made from scratch or source is pure. Roms that mention they are based on these so called "aosp" "aokp" is pretty much the same thing as the one built from source but its been modified, for example cyanogenmod is built from source, if you download it and modify the ROM, enhance it a bit more, add more features you will have to say it is based on cm as you didn't build it from source or scratch. You used the ROM as a base for your project. Like something you can start from.
Its like a car. A person that owns a car and modifies it, but its based on the original. The original is initially made by scratch. I hope I made sense. Sounded better in my head
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you. Completely makes sense. I guess that's why forums usually have two sections "original development" and Android based development."
Question for anyone:
Are those that are based on something like CM usually and improvement on CM in terms of bugs, etc or is it more just a preference in terms of features?
Sent from my Nexus 5 using Tapatalk

yogi217 said:
Thank you. Completely makes sense. I guess that's why forums usually have two sections "original development" and Android based development."
Question for anyone:
Are those that are based on something like CM usually an improvement on CM in terms of bugs, etc or is it more just a preference in terms of features?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It really depends, some add in more features, some remove features and make is clean. In you way you could say its an improvement but its up to the user as they are the ones that judge it themselves. Some bugs get fixed in the nodded Roms that use cm as base, like I said its all up to the user that mods the ROM. If they want to fix it themselves or wait for a new release.
Sent from my Nexus 5 using Tapatalk

krishneelg3 said:
It really depends, some add in more features, some remove features and make is clean. In you way you could say its an improvement but its up to the user as they are the ones that judge it themselves. Some bugs get fixed in the nodded Roms that use cm as base, like I said its all up to the user that mods the ROM. If they want to fix it themselves or wait for a new release.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you. That's what I was thinking, but wanted to make sure. I'm digging this culture. I'm a teacher and interested in independent learning and the support of the online community in mobile software modding and development is very interesting from a learning perspective.
Sent from my Nexus 5 using Tapatalk

@yogi217 It actually is quite interesting. I'm sure you'll understand quite a bit about android development in some time. It isn't that hard, just explore and youll come to a point and find out how easy it is. And good luck on your android/mobile development journey!
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.

A question about stock vs. Custom ROM on a nexus device

I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app

bbabiuk said:
I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.

rootSU said:
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.
Click to expand...
Click to collapse
Very thorough. I do have one other question then...
Then AOSP ROMs for Nexus devices should by the nature of the build process have everything working similarly to the stock ROMs. Things like Bluetooth not working quite right or green tints to cameras should not occur.
Sent from my Nexus 5 using XDA Premium 4 mobile app

*should* yes, but not guaranteed. Pure aosp should work immediately after compile. However, new functions are added by developers to the aosp code base to make the roms more functional and these commits can break each other or even existing functionality
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app

air2k57 said:
I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the update. The nice thing about nexus devices is it is so simple to go back to stock. It was a real pain on my HTC one.
Sent from my Nexus 5 using XDA Premium 4 mobile app

No problem. I had htc one and it was indeed a pain. While I liked sense, I felt a need to root because of annoying apps it came with, or power saver notification that was always there. Not to mention, T-Mobile variant took ages to get updated, and when it did, it was buggy. The whole S-Off thing was a nightmare.
I've always found other devices, even nexus 4, to function better with custom ROMs and kernel. It took me awhile to root n5 though, simply because I was happy with everything. I did like ability to have center clock, or circle battery with %. However, in order to have those, you need aosp or gravity box that doesn't work with art due to xposed. Oh yea, pie I liked too, I like having more screen space.
Other than that, I am very happy stock. I ended up finding a really good mix with purity ROM and elementalx kernel. I liked elemental on HTC one a lot as well. And, it has cooler colors option, I do like the way it makes display look.
Last night I ended up unrooting and going stock to compare. Reason being, I got annoyed with bright back key in landscape and text on quick toggles in portrait ended up being cut off some. Performance wise, I am thinking that lure stock is still A bit quicker. Battery? Not sure yet, I got woken up at 7am by stupid weather alert, ended up unplugging my phone and leaving it on nightstand. It dropped from 99% to 95% in 4 hours idle. So about a % an hour. I remember Franco and elemental having better idea battery life though.
Sent from my Nexus 5 using xda app-developers app