Related
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!
Its been like almost three weeks since i havent seen anything new from the development area. So i guess we are left behind. What do you guys think? i remember when i used to have the mytouch 4g and the vibrant even the lg g2x and there were a lots of updates, roms, themes, like every day. But with this devices i guess we got stuck with the same things. Sucks!!!
Sent from my SGH-T959V using XDA App
I don't think we're left behind. At least, not yet Currently all the devs have to work with on a GB level are the leaked GB ROMs. That means they have no source code to work with thus what they can do is limited. Also, there has not been a new GB leak since last month, so no updates from that end, either.
I'm sure once Samsung releases GB/ICS or whatever they're planning & the guys can get their hands on source code that things will pick up.
Just my 2 cents
Also remember that there are about 3 devs for this phone. Dsexton currently has no computer. Whitehawkx said he would update Valhalla if/when 2.3.7 is released. And Raver who has a couple roms that are probably as good as they can get without source. Without source code we won't get too much more. And unfortunately by the time we see it many will have moved on to other devices and ics. This is where Samsung always drops the ball. They take forever to update Android and by the time they do the next operating system is out on several better phones so people move on to them.
Sent from my SGH-T959V using xda premium
I miss my mytouch 4g. Faux123 was the best damn dev ever.
We should send him a phone. I bet we would have CM in a week. He's the kernel king from like 4 different phones now for AOSP stuff.
Sent from my SGH-T959V using XDA App
I believe krylon is willing to pass on the phone. If faux is willing to take up the task maybe krylon will pass on the phone in that direction.
Sent from my SGH-T959V using xda premium
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
Seems my hard work has finally paid off!
https://plus.google.com/+CyanogenMod/posts/TKJdwcptRRv
I'll update my thread accordingly once the nightlies begin. Since it'll be a couple of days before the nightlies actually begin, I'll run another build in the mean time. Partly because I want to make sure the CM repo will produce good builds
Yay!
Bugs that still exist: touchkey w/ BLN that they're using is just an interim driver... I need to finish porting that. Also, the random WIFI MAC bug. Ugh.
Oh! And there's a work around for users of the official CWM in ROM Manager. Until once the new builds kick in, you should be able to install them through the official CWM, which will allow CWM to update and correct their problem. This is some serious catch 22 stuff. But it'll get worked out.
Otherwise, you people should be able to start enjoying some nightly CM goodness.
I can then go on to finish the I577 port and get them on their way as well...
dr4stic said:
Seems my hard work has finally paid off!
https://plus.google.com/+CyanogenMod/posts/TKJdwcptRRv
I'll update my thread accordingly once the nightlies begin. Since it'll be a couple of days before the nightlies actually begin, I'll run another build in the mean time. Partly because I want to make sure the CM repo will produce good builds
Yay!
Bugs that still exist: touchkey w/ BLN that they're using is just an interim driver... I need to finish porting that. Also, the random WIFI MAC bug. Ugh.
Oh! And there's a work around for users of the official CWM in ROM Manager. Until once the new builds kick in, you should be able to install them through the official CWM, which will allow CWM to update and correct their problem. This is some serious catch 22 stuff. But it'll get worked out.
Otherwise, you people should be able to start enjoying some nightly CM goodness.
I can then go on to finish the I577 port and get them on their way as well...
Click to expand...
Click to collapse
Great news ,job well done.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Congratulations guys !
First, you got ICS update from T-Mobile.
Now, official CM10 is going to be available for your device.
:good:
Congrats! This is awesome news for both Blaze and Exhilarate owners. Thanks to everyone involved for all the work put into getting us this far this fast. I'm really starting to feel good about picking this phone over the S2.
Well done. Thank you for your support.
Sent from my SGH-T769 using xda app-developers app
namaui said:
Congrats! This is awesome news for both Blaze and Exhilarate owners. Thanks to everyone involved for all the work put into getting us this far this fast. I'm really starting to feel good about picking this phone over the S2.
Click to expand...
Click to collapse
Ditto
Sent from my CM10 powered Galaxy S Blaze 4G
AWESOME NEWS! Thanks so much for all of your hard work!
Yea thanks a bunch! Funny how I have JB and my friend on his g3 has ICS I love my phone again
dispozable said:
Yea thanks a bunch! Funny how I have JB and my friend on his g3 has ICS I love my phone again
Click to expand...
Click to collapse
Next stop: key lime pie
Sent from my CM10 powered Galaxy S Blaze 4G
dispozable said:
Yea thanks a bunch! Funny how I have JB and my friend on his g3 has ICS I love my phone again
Click to expand...
Click to collapse
Hell yeah! In a couple of weeks we went from doubting whether we'd ever see ICS on our phones to official CM10 support.
Seems I've lucked out with the purchase of my last two phones thanks to the awesomeness of the folks here on XDA. A couple years ago the HD2 was the most powerful subsidized phone available from T-Mobile (Nexus One was probably the best phone but couldn't afford to buy it in full). I reluctantly bought the HD2 but wanted Android OS so bad. About a month later devs ported a stable rom over via SD card and then made it NAND flash-able.
A couple months ago I was due for an upgrade again. I had to buy two phones (my wife's MyTouch 3G just wasn't cutting it for her) so I was again on a limited budget. When I looked at the specs I chose the Blaze since it seemed like the most powerful phone for the money. I was again bummed because it was running an older OS version than my two year old WinMo phone but now here we are!
:good::victory:
Could someone explain to a newbie, like myself, how official CM is different than unoffical.
Does it mean that offical CM fixes are automatically generated for Blaze every night? Is there a different place to grab these updates, than here in the Blaze Development forum.
ltcmdrworf said:
Could someone explain to a newbie, like myself, how official CM is different than unoffical.
Does it mean that offical CM fixes are automatically generated for Blaze every night? Is there a different place to grab these updates, than here in the Blaze Development forum.
Click to expand...
Click to collapse
Yeah, CM official will be generated on their servers (which are some serious kit) vs. the 4.5 hours builds required of my home machine.
The nightlies (in theory) should begin tonight, I'll update the main thread once it's all officially there.
I've been working closely with the devs in CM to get all this committed, therefore the next nightly should be just like my 10/09 build + my BLN fix + changes within CM from 10/09-10/12 (which in theory will be the first nightly). And then every nightly after that will get the CM updates moving forward.
With CM10 being official, it might not be too far of a jump to also add official CM9 builds. The device definition is mostly the same, just a matter of different binary blobs for the video. I'll have to talk to the guys about that.
The majority of the work I did was in porting the kernel changes into the main kernel repo. This is also going to benefit the CM9 build as erikmm asked for a copy of my patches. It means he'll get my WiFi random MAC bug (until I fix it), but other stuff should work... better?
Either way... a day to celebrate
dr4stic said:
Either way... a day to celebrate
Click to expand...
Click to collapse
Yup, ok I get it now. Excellent job, that is a huge deal.
I haven't seen Erik around.. I mean i guess I know why.. but i wonder if he knows....
unicorndust98 said:
I haven't seen Erik around.. I mean i guess I know why.. but i wonder if he knows....
Click to expand...
Click to collapse
I shot Erik a message earlier to let him know. Amazing what's happened in a week's time. Great news
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Quick question... I know they're "Nightlies" but when can we possibly expect the first one to drop? (Oh my, I broke the no skiing for eta's rule xD) I was curious if they gave you a rough idea.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
I'm hoping to get an "M" release.
Just want to say thank you man. Never thought it little device would get this much attention.
Sent from my blaze using cm10
Acerbus91 said:
Quick question... I know they're "Nightlies" but when can we possibly expect the first one to drop? (Oh my, I broke the no skiing for eta's rule xD) I was curious if they gave you a rough idea.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Well, just in case you didn't check this morning.... it's up So, ETA... yeah... this morning
chjema said:
I'm hoping to get an "M" release.
Just want to say thank you man. Never thought it little device would get this much attention.
Sent from my blaze using cm10
Click to expand...
Click to collapse
We'll get an M in a Month, the M3 (hopefully about the same time I place my order for an M3 ). They specifically held the kernel patches back so they could roll out the M release first. And they did this understandably. The patches I did could have seriously affected a few other builds (T989, I727, I717), etc... So they waited till after the monthly to add the kernel patches and add us to the device tree. CM had been in a soft freeze mostly for the last week.
Acerbus91 said:
Quick question... I know they're "Nightlies" but when can we possibly expect the first one to drop? (Oh my, I broke the no skiing for eta's rule xD) I was curious if they gave you a rough idea.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I got an update notification this morning for a 10/12 build. Go to settings-about phone-cyanogenmod updates. Download the update there. It will reboot and install automatically.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Just installed. I'll keep an eye open for anything different.
Sent from my SAMSUNG-SGH-T769 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