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.

[Q) ICS Port

So it has been announced that the SGS2 line will be updated to ICS Saturday. Will a port be possible to the infuse? I know its different chip sets, and all the other goodies, but will it still be possible?

If I were you, I'd don a flak jacket quick!
Sent from my SAMSUNG-SGH-I997 using xda premium

maybe if it was i9000 ( sgs1 ) we just use linuxbozo's tool

jason4962 said:
maybe if it was i9000 ( sgs1 ) we just use linuxbozo's tool
Click to expand...
Click to collapse
No go, tried. Aosp only way, and porting is extremely hard because ics uses completely new drivers. If the gingerbread and ics kernels are woven together, it would work. Part of the reason why ICS is hard to come by is it is so different. Btw, be ready to be told no infuse devs will do it, i do not blame them. Sammy loves sacrificing peoples thoughts with money.... like apple does. Seems to gather the most people too lol....

So is once a week the expected occurrence of these type of threads now-a-days??
Even the flamers are gave up haha

jason4962 said:
maybe if it was i9000 ( sgs1 ) we just use linuxbozo's tool
Click to expand...
Click to collapse
lb's tool doesnt magically compile a kernel for operating systems the came out after the creation of the tool. that would be cool though.....
what hellraiser is is a normal infuse kernel and a collection of hardware libs pulled directly from an infuse rom to interface with the kernel. it only does gb and was only possible because gingerbread was already available on the rogers infuse.
but an i9000 ics release could potentially help an infuse port but we would need a kernel dev in on it that had some knowledge of the differences between ics and gingerbread. but in reality the biggest thing holding up an aosp version (with some things broken of coarse) is a lack of a dev familiar with aosp ports on galaxy s phones. much of the major hardware is the same as the nexus s, even tha galaxy nexus has the gpu of our phone. the cpu, gpu, audio, ect are not nessessarily a problem. wifi, gps, bluetooth, mhl, and cell connection/data could be problems but wifi and gps work in cm7 so its posible they'd also work in ics.

Oh God here we go again
Sent from my SAMSUNG-SGH-I997 using xda premium

xIC-MACIx said:
So is once a week the expected occurrence of these type of threads now-a-days??
Even the flamers are gave up haha
Click to expand...
Click to collapse
more than. it seems atleast once every other day...

:banghead:
Sent from my SAMSUNG-SGH-I997 using xda premium

Alright cool. So it's a no go. That's all. And for you with the ignorant comment, what do you get out of them? nothing. I laugh at you more than the ignorance thrown out there.

Idk where you get your info at but no... the sgs2 line is not updating to ics that soon. Since Samsung decided to touch whiz the hell out if it, its nothing but a damn mess. Weve been working with it for weeks and its crap. Aosp is your best bet. As I will have aosp booted on the note soon

dman - +1 The update is currently available in Europe and Asia. If it comes to the US, it will likely be months. In the meantime Entropy512 has done a very nice job with CM9 for the Infuse (development thread)

dman3285 said:
Idk where you get your info at but no... the sgs2 line is not updating to ics that soon. Since Samsung decided to touch whiz the hell out if it, its nothing but a damn mess. Weve been working with it for weeks and its crap. Aosp is your best bet. As I will have aosp booted on the note soon
Click to expand...
Click to collapse
Um, get your facts straight before posting. XXLPQ (official ICS for I9100) was released over a month ago.

Anyone trying to port the ICS for us yet? :)

Sent from my SGH-T769 using xda premium

I wish lol. Likely not anytime soon. At least we're getting the official update if nothing. Funny enough, I bought this phone thinking we would get lots of ported ROMs, being so close related to the S2 series, but boy was I wrong
Sent from my SGH-T769 using xda premium

Bulletblitz27 said:
I wish lol. Likely not anytime soon. At least we're getting the official update if nothing. Funny enough, I bought this phone thinking we would get lots of ported ROMs, being so close related to the S2 series, but boy was I wrong
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
like in the other ics thread u started I said i would but sorta/extremely difficult without the device lol

I have been making efforts, but trying to keep them generally quiet. I am trying to build us an ICS kernel based on the kernel sources from the T989 release. It has most all of the bits that we need for our variant (our LCD panel code, earjack, etc), but it's obvious from attempting to build the thing that Samsung wasn't finished yet. At least, they weren't finished with the T769 code when they packaged up the T989 sources. I've already fixed a number of simple errors in the kernel code, but bigger ones are now holding me back.
I am not a programmer (and I keep saying this) but I am confident that with my other bits of experience, I'll be able to get a working kernel. Based on that, I am hoping that the architecture of CM9 and it's more official samsung_msm8660 base (thank you, T989 team and contributors) will make it easier to put together a build once we have a working kernel.
This phone is not without love. In as much as no one hears about it, I probably spend 50-60% of my free time trying to get something together for this phone, hitting dead ends or massive missing pieces down each road I take. An ICS kernel, which is what I am trying to build now, would be a massive bridge to get me much closer to point B from point A.

Complete CM7 & MIUI

Hi everybody!
Maybe I can seem really annoying but, since we're waiting for kernel 3, cannot devs focus on CM7 or miui in order to let camera record videos?
I think it is a good idea and it won't oblige anybody to upgrade to ics if they simply dont want! (for example I dont like the "speed" of ics and prefer gb actually)
I hope this tread will mean something for someone
Regards.
Sent from my GT-I9003 using XDA

Siso93 said:
Hi everybody!
Maybe I can seem really annoying but, since we're waiting for kernel 3, cannot devs focus on CM7 or miui in order to let camera record videos?
I think it is a good idea and it won't oblige anybody to upgrade to ics if they simply dont want! (for example I dont like the "speed" of ics and prefer gb actually)
I hope this tread will mean something for someone
Regards.
Sent from my GT-I9003 using XDA
Click to expand...
Click to collapse
That's a nice thought there. CM9 still has a lot of bugs in it and there is still a lot of work to be done. The ICS roms need kernel 3.x as you know and hillbeast is doing great. It I have been following the kernel 3.x development thread and it seems that hillbeast would have a the device booting soon. For devs like dhiru it would be too tedious to work on CM7 as he is already working on CM9 and the kernel. CM9 is pretty smooth and the camera occasionally force closes.
Yes I do agree with you when you say users should not be pushed to use ICS. Hope cm7 finds devs working on the camera.

CM9 is the future.. It will take the same effort to fix bugs on CM7 as on CM9..
Asking a dev to work on CM7 with CM9 development at its current state is pretty unnecessary, and I don't think any dev would even be interested. Why would anybody work on something that's supposed to be fizzing out..

As dhiru said,working on CM7 is double works for him.He is also busy with his life now.And yes,who don't want a fully complete rom? But developers are human like we too.You cannot say that now they are waiting for kernel 3.0,therefore they have time now. No, they need to spend time to their friends, family, their study etc..Lastly, the most important is they work for the community with no salary. We should appreciate their work rather than keep demand to them.

quan815 said:
As dhiru said,working on CM7 is double works for him.He is also busy with his life now.And yes,who don't want a fully complete rom? But developers are human like we too.You cannot say that now they are waiting for kernel 3.0,therefore they have time now. No, they need to spend time to their friends, family, their study etc..Lastly, the most important is they work for the community with no salary. We should appreciate their work rather than keep demand to them.
Click to expand...
Click to collapse
so you think that once kernel 3.0 will be out, they don't have any kind of "life"?
i said that, it's a good choice to complete cm7 and this period of "tranquillity" is the best one, since it's "freer" than once kernel out.

Siso93 said:
Hi everybody!
Maybe I can seem really annoying but, since we're waiting for kernel 3, cannot devs focus on CM7 or miui in order to let camera record videos?
I think it is a good idea and it won't oblige anybody to upgrade to ics if they simply dont want! (for example I dont like the "speed" of ics and prefer gb actually)
I hope this tread will mean something for someone
Regards.
Sent from my GT-I9003 using XDA
Click to expand...
Click to collapse
+1 all the way for u man ! i honestly thought of this before and even asked dhiru and hes completely into ics development, so thats a no . anyways its wonderful having him work on ics i wish sum1 fixes those in cm7

shriomman said:
+1 all the way for u man ! i honestly thought of this before and even asked dhiru and hes completely into ics development, so thats a no . anyways its wonderful having him work on ics i wish sum1 fixes those in cm7
Click to expand...
Click to collapse
getting a fully stable aosp rom is like a dream which will never come true for us. I know I am saying in a very negative way but its a fact guys that we have very few developers who also want some help from other top developers of other community who are damn busy with their development & they even dont know that a phone whose name is "galaxy SL" exist in mobile world. My friends also said me many times that they know galaxy s, s2, s3, ace & many more phones but they haven't heared anything about galaxy SL phone.
Its all about plenty of developers needed for good development which we are lacing from 1st day of release of this phone. I am emotinally attached with this phone & our community members, developers & thats why I use my phone with full of interest Otherwise I would have sold it so many days ago.
Regarding cm7, cm9, miui or any aosp rom I will only say this much that if any develoer will make hd video recording working then just within a week we will get official cm7, cm9...etc. But in my opinion it will never happen. We have to always live with a phone having good aosp rom but with lots bugs....ALWAYS...!

Agree with the essence of this topic.
We, i9003 users, don't have a custom ROM, that is bugfree.
I am willing to donate to whoever would spend time and effort to make "video recording" work on a custom ROM. Again, I'm not a developer and am not sure if this is even possible. I used to be a good c and java programmer about 12 years ago, but haven't been coding since then.
On the other hand, I'm also willing to wait for kernel 3 and make sure we have the latest stuff for our phones.
JMHO

I honestly think OP is right. We need to have a Rom that is bugfree. That way, many people won't feel bad going back to those stock ROMs which are nothing but a headache being slow and awful to work with and to look at. Most people just want a bugfree AOSP ROM.
On another note, it will be a pain for the devs (Dhiru), who promised us CM9. Nobody wants to do those things which they weren't supposed to. It will also be a pain for the community to donate a device to another dev. Seeing the chance of the Sense 4.0 donation request from many people, i don't think there are so many people in this community who can make it up for donating 2 phones in really short intervals, or at similar time.
And for the blow, Jellybean 4.1 is gonna be here anytime. SDK (And Sources too, i think) will be released today (Remember, first CM9 started with SDK builds), and update will be pushed to phones such as Nexus and Galaxy S3 in Mid July. So now, should the devs should still concentrate on fixing GB bugs? Or should the fix the CM9 bugs first? Or should they start porting Jellybean?
Just my POV.

I guess pushing for jellybean would be pushing too far(unless a dev dares to differ). I'll be content with a bugfree ICS ROM.

vishal24387 said:
getting a fully stable aosp rom is like a dream which will never come true for us. I know I am saying in a very negative way but its a fact guys that we have very few developers who also want some help from other top developers of other community who are damn busy with their development & they even dont know that a phone whose name is "galaxy SL" exist in mobile world. My friends also said me many times that they know galaxy s, s2, s3, ace & many more phones but they haven't heared anything about galaxy SL phone.
Its all about plenty of developers needed for good development which we are lacing from 1st day of release of this phone. I am emotinally attached with this phone & our community members, developers & thats why I use my phone with full of interest Otherwise I would have sold it so many days ago.
Regarding cm7, cm9, miui or any aosp rom I will only say this much that if any develoer will make hd video recording working then just within a week we will get official cm7, cm9...etc. But in my opinion it will never happen. We have to always live with a phone having good aosp rom but with lots bugs....ALWAYS...!
Click to expand...
Click to collapse
^
That's so negative.
CM9 is nearly bug free, (Except current known bugs), so no it's not a dream..
I kinda agree with OP, but not only hllbeast is working on kernel 3.x, dhiru and crack(-can't remember) are working on it too, so they're not "free".

Skander1998 said:
^
That's so negative.
CM9 is nearly bug free, (Except current known bugs), so no it's not a dream..
I kinda agree with OP, but not only hllbeast is working on kernel 3.x, dhiru and crack(-can't remember) are working on it too, so they're not "free".
Click to expand...
Click to collapse
Sorry for my negative thinking but I have seen development of this device from very start & I am pretty disappointed with it. Anyway if I become wrong in future & if my dream come true then I'll be the most happiest person on earth

vishal24387 said:
Sorry for my negative thinking but I have seen development of this device from very start & I am pretty disappointed with it. Anyway if I become wrong in future & if my dream come true then I'll be the most happiest person on earth
Click to expand...
Click to collapse
I think it will come true, the number of developers increased, that can be only good

Skander1998 said:
I think it will come true, the number of developers increased, that can be only good
Click to expand...
Click to collapse
agree with skander here...the number if devs have increased a lot since the cm7 days
.
Sent from my GT-I9003 using xda app-developers app

CM7 bugs could be a very little one... But if no developer does anything we cannot do anything.
Gb is very very very good for our phone and without 3.0 ics is pretty unstable...
If developers can do CM7 why spend time with ics that needs 3.0?
First finish CM7 then, once kernel out, ics!
Sent from my GT-I9003 using XDA

Siso93 said:
CM7 bugs could be a very little one... But if no developer does anything we cannot do anything.
Gb is very very very good for our phone and without 3.0 ics is pretty unstable...
If developers can do CM7 why spend time with ics that needs 3.0?
First finish CM7 then, once kernel out, ics!
Sent from my GT-I9003 using XDA
Click to expand...
Click to collapse
"Once kernel out"
Lol, who is developing the kernel? developers, and everyone not only hillbeast, so they're busy already.
Just wait don't be a pain in the ars.

Siso93 said:
CM7 bugs could be a very little one... But if no developer does anything we cannot do anything.
Gb is very very very good for our phone and without 3.0 ics is pretty unstable...
If developers can do CM7 why spend time with ics that needs 3.0?
First finish CM7 then, once kernel out, ics!
Sent from my GT-I9003 using XDA
Click to expand...
Click to collapse
Developers here, do this development for the sheer excitement of it, not for money.
I can see people are very excited about CM9 and ICS. Developers are people too, and do what excites them or what feels like a challenge.
It's quite similar to what happens when you get a new phone. I had a nokia E63, which i used to love and did use/try every feature/app for that phone. But, I rarely do anything except make phone calls from that device now. All my excitement is for my first android 9003.
Just an analogy to explain why excitement has died. Hope it makes sense.

Happy new year guys

Less than 5 mins to go on the east coast hope 2013 is a good one guys.
Sent from my biscuit

Happy New Year, dude. This section of xda is almost dead....lol. I feel like that old, crusty hermit in that popular sci-fi movie.

Happy New Year to all Sidekick users and developers! Let's hope development won't die completely in this year...

Development might be rising in this section

Well, let's hope that Sidekick won't die generally. OK?

Happy new year to dead phone users include me.
Sent from my SGH-T839 using xda app-developers app

Khizar hayyat said:
Happy new year to dead phone users include me.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Classic....lmao. True though.
Sent from my SGH-T839 using xda app-developers app

Khizar hayyat said:
Happy new year to dead phone users include me.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Nah. I got this phone from TheLastSidekick right at a weird turning point in my life.
I've been gone for a little while, trying to repair what I can, and giving in on what I cant.
I haven't forgot about my forum friends, patiently waiting for something... anything... I know you, flashaholics.
I've finally gotten a job and the work is behind, and deliverables due in feburary. Makes it a little hard to squeeze in any kernel dev work for now.
Hang tight. Get a new phone, but don't drop your sk4g. We'll have some fun with it yet. I'm thinking march or april, I hope to have time to get a cm7 kernel port. I'll disappear for a little more time may - july (another sprint for another trade show, product progress) and if no one has ported cm7 using my kernel (I'd be disappointed with team acid... ), I'd have some time then to do that.
If anyone else wants to take a crack, it's really not that hard.
Get the froyo kd1 (update1) source for sgs4g.
Get the froyo kg1 (?) source for sk4g.
compare those two with meld or other favorite merge tool.
You'll notice there is lots of space difference, and code just moved around.
Realign the code and fix the space damage in the sk4g froyo source.
Get the GB source for sgs4g. Port the sk4g bits from the froyo kg1 source. Some of the drivers for sk4g are still around, but with different names, and you'll also find some nice CONFIG_S5PC110_BOARD_SIDEKICK defines lying around, but not board definition or defconfig in the sgs4g gb kernel.
Then I use the usb uart to test porting, first steps is to get usb, pmic, and the fsa9480 drivers working, so usb uart works correctly in the first place.
Then go from there.
Anyways, I'll be back with an update in a little while. I'm just super busy.

bhundven said:
Nah. I got this phone from TheLastSidekick right at a weird turning point in my life.
I've been gone for a little while, trying to repair what I can, and giving in on what I cant.
I haven't forgot about my forum friends, patiently waiting for something... anything... I know you, flashaholics.
I've finally gotten a job and the work is behind, and deliverables due in feburary. Makes it a little hard to squeeze in any kernel dev work for now.
Hang tight. Get a new phone, but don't drop your sk4g. We'll have some fun with it yet. I'm thinking march or april, I hope to have time to get a cm7 kernel port. I'll disappear for a little more time may - july (another sprint for another trade show, product progress) and if no one has ported cm7 using my kernel (I'd be disappointed with team acid... ), I'd have some time then to do that.
If anyone else wants to take a crack, it's really not that hard.
Get the froyo kd1 (update1) source for sgs4g.
Get the froyo kg1 (?) source for sk4g.
compare those two with meld or other favorite merge tool.
You'll notice there is lots of space difference, and code just moved around.
Realign the code and fix the space damage in the sk4g froyo source.
Get the GB source for sgs4g. Port the sk4g bits from the froyo kg1 source. Some of the drivers for sk4g are still around, but with different names, and you'll also find some nice CONFIG_S5PC110_BOARD_SIDEKICK defines lying around, but not board definition or defconfig in the sgs4g gb kernel.
Then I use the usb uart to test porting, first steps is to get usb, pmic, and the fsa9480 drivers working, so usb uart works correctly in the first place.
Then go from there.
Anyways, I'll be back with an update in a little while. I'm just super busy.
Click to expand...
Click to collapse
He lives...he finally lives. Idk I might beat you to it. Just waiting for my laptop from gateway.

Exit_Only said:
He lives...he finally lives. Idk I might beat you to it. Just waiting for my laptop from gateway.
Click to expand...
Click to collapse
Multiple efforts means multiple as many successes. In different ways can be integrated into a more functional kernel. To use the least words

I may take a crack at it, then. I have zero experience with porting code like this, though.
Sent from my SGH-T839 using xda app-developers app

RicAndroid said:
I may take a crack at it, then. I have zero experience with porting code like this, though.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Just use my device tree. It will make a boot able cm7. The kernel is kinda iffy but it will boot.

Exit_Only said:
Just use my device tree. It will make a boot able cm7. The kernel is kinda iffy but it will boot.
Click to expand...
Click to collapse
I mean, don't get me wrong, we can make the froyo sk4g kernel work with cm7, I think the goal of the plan I laid out is to get the sk4g device ported to the teamacid kernel, which has cm7 and cm9 ports, and is 2.6.35.7 based.
At the same time as porting sk4g to that kernel, I'm trying to port sgs4g to the teamhacksung aries kernel. This will get sgs4g to 3.0.8 on ICS, and that will make porting to JB easier.
So if we can port sk4g to the teamacid cm7 or cm9 kernel, that would be the best path to getting sk4g to ics and jb.
Just sayin

bhundven said:
I mean, don't get me wrong, we can make the froyo sk4g kernel work with cm7, I think the goal of the plan I laid out is to get the sk4g device ported to the teamacid kernel, which has cm7 and cm9 ports, and is 2.6.35.7 based.
At the same time as porting sk4g to that kernel, I'm trying to port sgs4g to the teamhacksung aries kernel. This will get sgs4g to 3.0.8 on ICS, and that will make porting to JB easier.
So if we can port sk4g to the teamacid cm7 or cm9 kernel, that would be the best path to getting sk4g to ics and jb.
Just sayin
Click to expand...
Click to collapse
I'm with ya 100%. I just used what was available