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.
Related
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Kid_Cudi said:
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Click to expand...
Click to collapse
I like Kid Cudi as well first of all.
What I mean is and I'm probably not going to use the right term here but the RIL or perhaps SDK.. Bear with me here I'm good at trouble shooting stuff but not programming.
I was googling it didn't help me get the right term lol. Chime in who ever knows what the hell I'm talking about here lol.
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
ProTekk said:
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
Click to expand...
Click to collapse
Yeah I think it's RIL. It's what the Cookers keep stating they're waiting for to finish their ROMs like CM7 for instance. The developer for it states that he's waiting for RIL to be able to officially finish his work. We really need to get this released from HTC so we can fix some of the issues people are having with CM7 and the leak for GB. I went back to Froyo because of the issues the leaks having with charging etc..
thewebsiteisdown said:
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Click to expand...
Click to collapse
HTC and google do not have to release any of the android source if they don't want to because the source (NOT THE KERNEL) uses the apache license, which is very permissive like the BSD/MIT licenses. It lets you use any code additions you make to the source for commercial projects without having to give it back unless you choose to http://en.wikipedia.org/wiki/Apache_license. This is why google doesnt have to release the Honeycomb source as long as they didn't make any additions/modifications to the kernel itself.
Google went through lots of effort as well to make sure they would not be bound by the GPL by writing their own clibs based off of code from various BSD ports. See here for an interesting article on some of the low level features of android (it's a bit old, but most of it is still relevant). http://codingrelic.geekhold.com/2008/11/six-million-dollar-libc.html
The kernel (like all linux kernels) is GPL and must be released.
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I think there is a misunderstanding here. The RIL from Slayher is not the same as the RIL from HTC/Qualcomm.
Slayher will merge his "source" into the public CyanogenMod repo once he deems it's ready.
On the other hand, the "source" from HTC/Qualcomm is a whole different subject. We won't be getting a drop of it from them. Not now, not ever.
miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
thewebsiteisdown said:
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
Click to expand...
Click to collapse
No the RIL source and Sense source run under the apache license which states that the software developer can use the open source code but does NOT have to repost anything he or she produces.
So it is up to our dev's to do that and make it readily available.
so i got bored and tried flashing a samsung galaxy s 4g leaked 2.3.4 rom... i did it thru odin everything went fine after it got done flashing, sound booted up but screen did not turn on for me... i tried taking the battery out and turning it back on... nothing but the sound coming on, then i tried going into download mode it wouldnt let me. so i guess i bricked it. but anyways went to tmobile got a new sidekick. so my question is if im able to flash thru odin successfully and the boot sound comes on, is it possible to flash a samsung galaxy s 4g rom if a dev put some work into it?
It shoulb be possible but first the would have to still get a. Ginger kernel that works with our hardware
Sent From My Rooted Sidekick 4g XDA Premium App
Odin flashing is nothing but a special way of writing data to the flash memory on the phone. It in no way means the software being flash works on the platform it was copied to.
just because the sound driver works, doesn't mean that anything that actually matters would work.
You could use JIG to force it into download
2.6.35 kernel source for Galaxy S Series phones was released by Samsung. So someone good enough to do it should be able to now. Its just finding a developer good enough to do it.
Sent from my Sidekick 4G using XDA Premium App!
Although it's technically possible, our phone has entirely different modules and drivers from every other Galaxy S phone. So although yes, there is technically a source for the Galaxy S, there's no source for our specific phone.
Shouldnt matter. The Dream and Sapphire didnt. They were never meant to have GB. Same with some other phones. It needs build for our phones using those sources.
Sent from my Sidekick 4G using XDA Premium App!
The dream and sapphire have a team of the best devs that exist on Android, including Cyan himself. Half of those devs work for HTC or Samsung. Building the general Galaxy s source for our phone wouldn't even boot correctly, as it wouldn't have any drivers to make any of the hardware work.
sduvick said:
The dream and sapphire have a team of the best devs that exist on Android, including Cyan himself. Half of those devs work for HTC or Samsung. Building the general Galaxy s source for our phone wouldn't even boot correctly, as it wouldn't have any drivers to make any of the hardware work.
Click to expand...
Click to collapse
They do have the best developers. Cyanogen is not one of them anymore. And hasn't been in quite a while. None of them work for any companys like that except for Cyanogen. I didn't say to just build the source. I said to use the source to tweak and build for the sidekick. It can be done. I wish I could do it.
Sent from my Sidekick 4G using XDA Premium App!
There's a reason that there's no CM7 on the Dream/Sapphire, and that's because CM quit developing for it. there's plenty of them that work for companies. the hardware changes for the sidekick require much more than just minimal tweaks, that would require essentially rewriting drivers to be a part of a new kernel.
sduvick said:
There's a reason that there's no CM7 on the Dream/Sapphire, and that's because CM quit developing for it. there's plenty of them that work for companies. the hardware changes for the sidekick require much more than just minimal tweaks, that would require essentially rewriting drivers to be a part of a new kernel.
Click to expand...
Click to collapse
There is CM 7.1 for the Dream/Sapphire because me and a few others have built it. Cyanogen only quit developing for it officially. And i didnt say minimal tweaks. I said tweak. I understand its a lot of work thats why i said we need some developers here good enough and willing to do it.
Sent from my Sidekick 4G using XDA Premium App!
Then go find some. If you're not going to appreciate the devs who are here, who try their best to work on this phone, then do it yourself. If you can't do it, then find other devs, or be grateful for the time we put into our work on this phone, rather than constantly telling us that we are inadequate.
sduvick said:
Then go find some. If you're not going to appreciate the devs who are here, who try their best to work on this phone, then do it yourself. If you can't do it, then find other devs, or be grateful for the time we put into our work on this phone, rather than constantly telling us that we are inadequate.
Click to expand...
Click to collapse
Never once did i say you guys were inadequate. I appreciate your guys work. I was just saying we need a developer that knows how to bring us CM. No reason to get mean. I never said the roms here were bad. We need these roms. A variety is good. Not everyone wants CM. But some do. How did you take anything i said as being directed to you? And if you want to be truthful. You guys are constantly taking shots at revolutions work. So calm down just a bit. We all appreciate the work you do. And if i could bring CM to the Sidekick, trust me, i would. And also trust that i have been trying to find other devs to bring CM to the Sidekick.
Sent from my Sidekick 4G using XDA Premium App!
I work with Revolution on things that he needs help with, I haven't been taking shots at him. Some do, but I don't. My apologies if it was misplaced, I guess I had lumped you in with all the kids who were so used to having CM that they expected it to be done within a month of the phone release, and got super upset when it wasn't done, my bad.
If nothing else, this has made me want to try porting the kernel again, I'm gonna give it another shot, to see if I can come up with another way to do it. We'll see what happens, once again, my bad, I'm sorry.
sduvick said:
I work with Revolution on things that he needs help with, I haven't been taking shots at him. Some do, but I don't. My apologies if it was misplaced, I guess I had lumped you in with all the kids who were so used to having CM that they expected it to be done within a month of the phone release, and got super upset when it wasn't done, my bad.
If nothing else, this has made me want to try porting the kernel again, I'm gonna give it another shot, to see if I can come up with another way to do it. We'll see what happens, once again, my bad, I'm sorry.
Click to expand...
Click to collapse
I didnt mean to come off as a prick. I definetely know it will take time. Of course i want it, but i can wait. Good luck with the kernel. Hope you get it. Im sorry also.
Sent from my Sidekick 4G using XDA Premium App!
I know you're still actively working on the CM 7.1 project for the D/S, did you have any interest in working with us on projects for the Sidekick?
sduvick said:
I know you're still actively working on the CM 7.1 project for the D/S, did you have any interest in working with us on projects for the Sidekick?
Click to expand...
Click to collapse
Id love to. But, right now my internet is off. As soon as its back up and running then id be glad to do what i can to help when im not working on the Dream/Sapphire. I want to try to keep CM alive for them. Ill let you know as soon as its back up and running.
Sent from my Sidekick 4G using XDA Premium App!
As far as kernels for ICS if Samsung releases source code for kernel does it have to be solely for our device or can it be (ported so to speak) from another device as long as it's a samsung
Sent from my SGH-T959V using XDA
anoymonos said:
As far as kernels for ICS if Samsung releases source code for kernel does it have to be solely for our device or can it be (ported so to speak) from another device as long as it's a samsung
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Team kick ass is working on it (mostly Erik)... Be patient...
Sent from my BAMF SGH-T959V!
Well I just read that samsung has released source for ICS kernel for the new Note just wondering if this can be used for our device. Also I read this from engagement.com source was from Open Source Market
Sent from my SGH-T959V using XDA
Ok I am personally going to start a new trend of not talking about ICS, CM9, or heck even Jelly Bean. If I can see that the Devs are starting to get annoyed with the constant onslaught of ICS, CM9, and CM7 questions and soon next month if it is released Jelly Bean. I guess if you can't help Develop, then you really have absolutely no place to complain about how long things are taking this is not a "customer Service" situation. Devs are here because they want to improve their own phones, or this is their hobby. They are not here to develop you a product. That's what Samsung is for in our case. If you are honestly angry about how long it is taking for us to get ICS then write T-mobile and Samsung not the Devs here that are spending their free time in order to eventually bring these awesome ROMS to our phones. Since I joined a year ago I watched Devs and entire teams leave (when is the last time you saw a Team Whiskey ROM?)So I for one am going to Back off on all the ICS business and let the Devs do their thing Without Having to stop constantly and answer the same questions over and over again. We have limited Devs that can at any sell off their SGS4g's and say "screw this" and move on to another phone. Guys seriously instead of constantly asking the Devs lets try something new ( or old to some of us) and ask Google, Yahoo, Ask.com, and or any other search engine you so choose and let the Devs concentrate on Developing.
One day people will learn how to ignore annoying posts. One day..........
i say "TEAM WHISKEY ROM" haha. lol
airfluip1 said:
i say "TEAM WHISKEY ROM" haha. lol
Click to expand...
Click to collapse
LOL thanx I didn't even see the typo, fixed it
thomas.raines said:
Team kick ass is working on it (mostly Erik)... Be patient...
Sent from my BAMF SGH-T959V!
Click to expand...
Click to collapse
Lol thanks thomas
thomas.raines said:
Team kick ass is working on it (mostly Erik)... Be patient...
Click to expand...
Click to collapse
I go away for a few days and now we're working on an ICS kernel. I should go away more often. lol
hechoen said:
I go away for a few days and now we're working on an ICS kernel. I should go away more often. lol
Click to expand...
Click to collapse
now that's comedy! !
My question had still not been answered a
Sent from my SGH-T959V using XDA
The answer( as I have come to understand, but I maybe wrong) is well parts can but for the most part the linux kernel is the part of the OS that houses all the device, and processor specific drivers. To make matters worse is some of those drivers are also OS specific. meaning Froyo versions won't work with a Ginger bread distro and so on. To port an Android distro you have one of two choices to make it work. Recompile some or all of the libs to work with the older kernel. Or create a kernel from scratch by finding other devices the have the same hardware that have been upgraded to ICS. Often many devices have pieces of the same hardware as your phone. Sometimes it takes scouring different phones to find phones that share pieces of your hardware.
Sent from my SGH-T959V
@ bot42
You are precisely correct. We at Team Kick Ass have found a way to do just that. Unfortunately, it is a very time consuming process as we have to pull many of the information, files, and things from source. I said this once and I will say it agian. Everything is in the process of being worked on. Please be patient.
Thanks sorry if I sounded rude but all the comments that were posted were way off topic that's all I'm in no hurry for ics just seen that Samsung released source for it was trying to be helpful
Sent from my SGH-T959V using XDA
it's taking me forever to properly port voodoo sound into CM7. Precisely as thomas and bot said. If it takes so long to properly port a little thing, think about how long it's gonna take to port a whole kernel.
airfluip1 said:
it's taking me forever to properly port voodoo sound into CM7. Precisely as thomas and bot said. If it takes so long to properly port a little thing, think about how long it's gonna take to port a whole kernel.
Click to expand...
Click to collapse
Yep to port a feature from one device to the next is hard a kernel/whole rom requires a lot of time and that is where my free time is being spent between reading and trying a lot of stuff
So, there are two efforts going on.
The first is what TeamKickAss is working on. I haven't seen what they are doing or any plans posted.
The second is what I'm working on over in the aosp port thread.
This port is a little more ambitious to port to three different versions.
first port sgs4g specific parts to android-samsung-2.6.35-gingerbread
then port that set of changes to android-samsung-3.0-ics branch (both branches originate from the upstream aosp samsung kernel)
the last port I will do will be to Linus's tree at whatever version it is when I get to this step.
So in the end, we'll have:
a stock kj6 kernel
the various kernels that forked from my bml and mtd kernels
aosp gb port
a couple ics kernel ports (one by teamacid, and one by teamkickass)
3.6 kernel port(or maybe 3.7)?
So, there is a peek in the crystal ball I have.
The future's so bright, gotta wear shades
Hi Bryan
Wassup?
I have a friend with SGS i9000, (which didn't get official ICS) nevertheless he installed an ICS 4.04 AOSP ROM on it, working flawlessly.
So my question is, once kernel port will reach its purpose, will we be able to successfully port such ROM ? (PS. I downloaded that ROM and saw some MTD_over_BML stuff inside)
Sent from my SGH-T959V using xda premium
i bet kickass can port it within a few days of an ICS kernel, but ports aren't always the most reliable/stable/fast. It'd be easier just to build from source. That way, we'd have a stable rom, and easier bug fixing.
itzik2sh said:
Hi Bryan
Wassup?
I have a friend with SGS i9000, (which didn't get official ICS) nevertheless he installed an ICS 4.04 AOSP ROM on it, working flawlessly.
So my question is, once kernel port will reach its purpose, will we be able to successfully port such ROM ? (PS. I downloaded that ROM and saw some MTD_over_BML stuff inside)
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Yea, with so many developers on teamhacksung... they can WORK TOGETHER and port their Aries kernel to any Aries phone. Our phone is kinda funky and we have very few developers.
Sent from my SAMSUNG-SGH-I717 using xda premium
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
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!