Related
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.
Possibly a noob question but since cyanogenmod7 is based off gingerbread an there is a froyo based cyanogenmod6 for the google G1 is it possible to do a port over to our phone since its froyo as well. I know drivers an such would have to be messed with but least we could have cyanogen on our phones even if its not the latest gingerbread powered version.
I don't know why people find cyanogen roms to be the be all end all of android. Not saying that I don't want them, but they're not the only thing that makes a phone good. CM6 is based off of the same kernel as CM7 which requires a newer source than we have.
Cyaongen mod roms are rubbish, they contain many bugs that are dealbreakers anyways. I know the devs are hard at work, but any current rom in these sk forums have far less bugs than cm. Cm7 on my mytouch 4g was horrible. Not belittling anyone, but just speaking from experience and hardships with those roms since the old g1 days.
Insanedrunk.....you are so ignorant if you believe Cyanogen ROMs are rubbish.
First off, the "ROMs" in the Sidekick 4G forum are nothing more than modified T-Mobile ROMs....that's all they are....nothing more.
Cyanogen and his team completely rebuild Android from scratch, that's why it's called "AOSP". Their ROMs require far more knowledge than simply zipaligning, deodexing, and deleting junk applications. If you have ever even attempted to build Android using the SDK, you would respect these guys.
You obviously are some n00b that doesn't even understand the concept of Android rooting and modding at all.
Please, if all you can do with Android is talk crap to legitimate developers, go somewhere else, you don't even deserve to type xda-DEVELOPERS into your address bar.
Sent from my stock, unlocked Sidekick 4G
Actually, AOSP stands for Android Open Source Project. It's plain vanilla android, from google's source. Yes, eventually into CM6 and 7 they got more hacky with it, but up to CM5, it was just standard google source releases patched together.
troby86 said:
Insanedrunk.....you are so ignorant if you believe Cyanogen ROMs are rubbish.
First off, the "ROMs" in the Sidekick 4G forum are nothing more than modified T-Mobile ROMs....that's all they are....nothing more.
Cyanogen and his team completely rebuild Android from scratch, that's why it's called "AOSP". Their ROMs require far more knowledge than simply zipaligning, deodexing, and deleting junk applications. If you have ever even attempted to build Android using the SDK, you would respect these guys.
You obviously are some n00b that doesn't even understand the concept of Android rooting and modding at all.
Please, if all you can do with Android is talk crap to legitimate developers, go somewhere else, you don't even deserve to type xda-DEVELOPERS into your address bar.
Sent from my stock, unlocked Sidekick 4G
Click to expand...
Click to collapse
I actually have pulled directly from source, but for mt3g, still have my linux setup ready to go, does take time, still, I don't add **** code to my roms that cause memory leaks, I'm not as ignorant to the extent that in which you think of. I'm not brown nosing any self proclaimed douche bags either.... and if you frequent this site, you wouldn't have to constantly type it in your address bar, so noob? Maybe to the sk4g scene, but not to android.
Still, I would like to say I'm sorry if my post came off as rude as you thought, but I was simply.saying I think our sk4g devs can go a diffrent direction than cm.
Cm7 for defy is amazing. Cm7 was available for the defy long before any leaked gb was available. Even with a locked bootloader. I wish somebody from that thread was here
Sent from my MB525 using XDA App
Then go find them. Don't just act helpless, if you really want someone from those threads to get over here, pay the $300 to buy a CM dev an SK4G. until then, be happy for what you have.
heard that ^
Sent from my MB525 using XDA App
Im a little confused. I dont own a Xoom by the way but am looking to buy one. Anyways, if the source code for honeycomb was never released, how did you guys make custom Roms and Kernels?
Whooo! (Cole Voice...)
knowledge561 said:
Im a little confused. I dont own a Xoom by the way but am looking to buy one. Anyways, if the source code for honeycomb was never released, how did you guys make custom Roms and Kernels?
Whooo! (Cole Voice...)
Click to expand...
Click to collapse
a little bit of reverse engineering can occur with the standard motorola files... or motorola source (just a guess with that last one)...
source generally refers to google actually putting out source... the way it was intended before other manufacturers do their own mods then the devs would build the entire thing from source it takes a significant amount of work i can assume from source because it cant just be compiled and installed u need to mod drivers/libs etc to work with the specific device... but the end result can allow for better mods to be made...
the way it is now though its still alot of work because they are playing with alot of guess work i can assume and need ALOT of knowledge to give us what they have
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
We seem to have a great selection of other ROMs, from CM, AOKP, etc. but I never see just an AOSP ROM for this device. It would be great to compare the "Nexus Experience" for the Doubleshot, I think.
Well, technically Cyanogen Mod is the greatest AOSP ROM out there. As far as I know nobody writes anything from the ground up. At least if I understand how everything all goes together. Now, someone may very well use their base code & do all their own coding for add-ons & customizations but I'm not sure who or which ROM you may be talking about. My wife has a Nexus 4 so I have been browsing their forums but that's the way it seems to me.
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
demkantor said:
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
SEE! I told ya I wasn't sure. LMAO! :laugh:
demkantor said:
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would love to try this, and I've gone far enough to setup everything on my linux box. I got to the point of downloading the source files, and I'm not sure where to go from there. Reason being that I know that most of the phone sensors and components wont work without the proprietary drivers and other required software for the phone. I don't know where to find them, and if I managed to get them, how to integrate them into the source tree. I have looked through the developers reference thread, but not sure whats needed from there to get all the stuff needed.
I think I'm in over my head lol
Fuzi0719 said:
We seem to have a great selection of other ROMs, from CM, AOKP, etc. but I never see just an AOSP ROM for this device. It would be great to compare the "Nexus Experience" for the Doubleshot, I think.
Click to expand...
Click to collapse
I gotta say, I only just got into the ROM bizness. Was running fully stock, locked GB rom on this phone until a few weeks ago. After some research and lots of reading through these forums I settled on the Unofficial CM 10.1 JB rom here, and absolutely love it. I can't believe what amazing crew of dev's we have here that are bringing new life to this great hardware, but unsupported handset!
Suffice to say it's been my ONLY other experience compared to stock, but I'm using it as a daily driver with nearly no issues, and some have even been fixed since my first flash a few weeks ago. Can't thank this forum enough. Now if only I could post in the development forums without having to make 9 more BS posts I'd be a happy camper!