Related
Forgive me if this is answered somewhere, I did search.
So Eugene got his hands on the 2.2 source code. It was apparently leaked to him by a contact he has. So Sammy hasn't officially released the 2.2 source code?
So my second part of this question is this:
If Eugene has a leaked source code, why are there so many tests in his thread? I mean if it's the source code shouldn't it just work perfect once compiled?
I'm obviously no developer so that's why I have these "noob" questions. I just wanted to get some info on this subject of this source code Eugene has is all. Just don't understand all these tests if its the actual source and if it is the actual source code, why aren't the rest of the devs, including Cyanogen , jumping all over this and making ROMS based off it?
Thanks for any help regarding these questions of mine
The source that most are using is from either Euro9000 but then Samsung released the Captivate 959D (ATT) 2.2 source code. It is pretty close to our T-959 (TMO) and since that release in the last 10 days or so, every Dev has gone through this source code and updated their ROMS. The captivate and Vibrant are almost the same in build but not exactly the same.
To the second part, since they are not exactly the same... then testing to tweak it correctly for the Vibrant platform is necessary. That is why all the testing
Hope that helps
From what I've read source had only been mentioned in regards to the kernel, nothing else. I've also read that some of samsung's changes to the kernel have resulted in greater battery drain than the 2.1 kernel.
Sent from my SGH-T959 using XDA App
Thanks for your help and answers!
Sent from my SGH-T959 using XDA App
Just curious as to which dev you think will put out the first stable rom based on t959 source? Not that first or fast is best, but i am sure they are all runnin on hyper-speed. My guess is dfa. I am a fan of all the big 3, but Masters updates are on point. Obviously Eugene killed the kernel race(nice job).
Blue 32 in the 4th.
My guess is Whitehawxx and or untermensch will have a deodex version out today
Then Einherjar/trigger/TW and Master team will get something out who know between those 3
I think they are all more surprised how much the leaks were right......
Isn't trigger part of the enjijar team?
And trigger is by bricked?
What the hell? it's kernel source, not Rom source....
Sent from my SGH-T959 using XDA App
No it's the entire FroYo source.
The ROMs here are fine, the kernels are the ones we needed the source for as they used to be based on the i9000 JPX FroYo source which hogged battery.
Our source is based on KA6 FroYo which should equal to better life!
Alanrocks15 said:
No it's the entire FroYo source.
The ROMs here are fine, the kernels are the ones we needed the source for as they used to be based on the i9000 JPX FroYo source which hogged battery.
Our source is based on KA6 FroYo which should equal to better life!
Click to expand...
Click to collapse
NO, no it's not. It's KERNEL SOURCE. the only rom source we have is from google.
It's source for a froyo kernel build KA6. Nothing more.
Can a experienced user please respond and tell us if its kernel source or froyo source???
i know what i'm talking about. it's kernel source. nothing more.
If it was rom source, then the GT-i9000 would have had rom source for a while. they've only had kernel source. And that's what we have now. kernel source.
If you don't believe me, then download the source and try to compile it yourself. you'll only end up with a kernel.
the only rom source we have is the AOSP source from google.
Time to set everyone straight.
It's Just KERNEL SOURCE!
The Platform dir within the source has NOTHING to do with a ROM, hell, doesn't even have anything to do with the kernel either.
Yes kernel code, but an intergeated kernel in one of these roms first was my poll question, not a flashable kernel. Thats all. Sorry to confuse.
feckmu said:
Yes kernel code, but an intergeated kernel in one of these roms first was my poll question, not a flashable kernel. Thats all. Sorry to confuse.
Click to expand...
Click to collapse
It's already done
You guys really crack me up.lol Not everyone even if they read tutorials, actually understand some of the foreign (Technical/Terms) language that some of you guys speak. Some of you have unbelievable arrogance to assume that everyone speaks geek. I do understand most of what I have read here and have been able to make my Vibrant really preform much better than stock. But not all are able to. Some in fact do need to be hand held a little. But if that is not your thing then ignore them when they ask for help. But to belittle demean and flat out act an ass on a public forum is ghetto fabulous. I'm in healthcare and I know that even when I am trying to speak in simplistic terms that I still talk over most patient's heads. It's up to me to try to help them understand the best way I know how. So why don't some of you get your asses off of your shoulders and stop trippin'
FAIL hahahaha
So I had always heard that we would see CM development ramp up after the 2.2 source was out. I went over to http://cmsgs.com/mediawiki/index.php?title=Main_Page to see how things were going. This place is almost dead except for git updates and a little irc discussion. I was thinking it may just be because so few of the developers on XDA know about CMSGS. Well its a project to put AOSP builds of cyanogen on SGS phones like the Vibrant. If you dont know about the project head over and stur up some conversation, and maybe some code.
Forum http://cmsgs.com/phpbb/
Twitter http://twitter.com/#!/CMSGSTeam
Wiki http://cmsgs.com/mediawiki/index.php?title=Main_Page
Building for the Vibrant http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Setup_Directories
The code https://github.com/cmsgs
On a serious note, I think everybody really does know about Cyanogenmod (CM7) and if they had the capabilities and want to do so, they would be helping. I knew about CM before I discovered XDA. Somebody correct me if I'm wrong, but from my understanding, the reason CM7 is a slow going process right now is that the source to the drivers have not been released... That is unless the latest source release contains those...
ahronzombi said:
So I had always heard that we would see CM development ramp up after the 2.2 source was out. I went over to http://cmsgs.com/mediawiki/index.php?title=Main_Page to see how things were going. This place is almost dead except for git updates and a little irc discussion. I was thinking it may just be because so few of the developers on XDA know about CMSGS. Well its a project to put AOSP builds of cyanogen on SGS phones like the Vibrant. If you dont know about the project head over and stur up some conversation, and maybe some code.
Forum http://cmsgs.com/phpbb/
Twitter http://twitter.com/#!/CMSGSTeam
Wiki http://cmsgs.com/mediawiki/index.php?title=Main_Page
Building for the Vibrant http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Setup_Directories
The code https://github.com/cmsgs
Click to expand...
Click to collapse
Do you have a vibrant? Stupid question I know but its confusing when you have Nexus One and G1 on you signature. Anyhow how do you make a signature lol sorry? Well hopefully more people help the dev thats porting CM7.
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
BlackVision said:
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
Click to expand...
Click to collapse
We don't NEED source for CM7. Considering almost no phones have Gingerbread source, they wouldn't even be working on CM7 like they are if this was a deal breaker. You know the saying "don't knock it 'till you've tried it"? Maybe you should adhere to this as CM7 actually runs pretty well on the Vibrant already.
Now, to respond to the OP. I realize a lot of people were expecting some change in development speed for CM7 with the release of source, but there was no reason for this. Nothing has changed or should change. The source we have now is barely applicable if at all to CM7.
Honestly, though, if you look at the list of bugs, it's not that long or severe. The only real non-issue issue is the complicated installation, which they have no reason to improve until they're satisfied with the rom.
MWBehr said:
Honestly, though, if you look at the list of bugs, it's not that long or severe. The only real non-issue issue is the complicated installation, which they have no reason to improve until they're satisfied with the rom.
Click to expand...
Click to collapse
Can you point me in the direction or post a "how to" to the installation of CM7?
kaizasoshi said:
Can you point me in the direction or post a "how to" to the installation of CM7?
Click to expand...
Click to collapse
Go to the i9000 android development forums, it will explain everything.
Sent from my SGH-T959 using XDA App
Or go to the Vibrant General section for some more CM7 info..
@dumdidum on twitter said he ordered a Vibrant so Im sure he will help port it to the Vibrant once he receives it.
they already started adding the vibrant to the source the other day but i been running it fine from the i9000 plus what scrizz said for the modem and a toggle headset widget
BlackVision said:
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
Click to expand...
Click to collapse
I think thats a good place to start, i would prefer CM6over any existing vibrant rom (sorry not a insult to existing roms)
If their were any dev's that really wanted CM on their Vibrant it would have been done by now or there is something that is really holding them back. I don't know why anyone would want to lose functionality for a little extra speed. Side by side CM7 on the Nexus S is almost identical to the Vibrant running BionixV, why would you want to give up video codec's and a better UI for that? I would love to get Bionix V on my Nexus over CM or stock Gingerbread any day.
I use to see Cyanogen as a god of android back when I had the G1. His ROM was the ONLY thing I ever put on my G1.
I know that the Cyanogen team really only does a lot with HTC handsets since HTC is AWESOME with giving out the source to their drivers. And I was so hoping to see it on my Vibrant, but in all honesty I've given up the dream of seeing a stable build for the Vibrant.
Samsung don't play nice like HTC with what sources they release so I know it's tough for CM team go get a 100% stable rom for Vibrant.
The devs we have here that do make roms for our phones are the greatest. Team Whiskey, Team Einherjar, Eugene, Master... They all do such great work and also calaborate and make my Vibrant so awesome and sleek. So honestly I am not holding my breath for a stable and easy to install CM Mod ROM for our phones. Tho I would like to see one, I'm totally happy with the ROMS we do have to pick from..
Anyways, Good luck to all of you devs who are working on porting CM over or working on an actual CM ROM for our phones.
But for now, I'm loving those ROMS we do have.
Ill help as soon as I can get a new motherboard for my pc
Sent from my SGH-T959 using Tapatalk
Im working on building a update.zip from CM source, but i cant promise ill succeed as there isnt a lot of documentation for this device due to the lack of people working on this branch of cyanogen. If i get a flashable update ill post it, maybe that will inspire someone who can actually dev and not just build existing source code.
Okay this is where im stuck, its a documentation issue look at http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Configure_Build
when i get to lunch cyanogen_vibrant-eng i get this error
Code:
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/samsung/vibrant/full_vibrant.mk]]: "build/target/product/full_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_vibrant'
** Do you have the right repo manifest?
Im sure its a simple config fix, if someone can figure this out and update the code or the wiki we may have fixed the one part of the build process that scares devs away. Im too stupid to fix this
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Ill b up and running soon working on a vibrant specific build once I'm completely done with ToXic 1.0 =3
Sent from my SGH-T959 using Tapatalk
Why is it difficult to get CM7 on SGS phones if Samsung doesn't lock bootloader ?
Was going to post in QA, but I think this question might be better suited in dev section. Feel free to move if needed.
StDevious said:
Why is it difficult to get CM7 on SGS phones if Samsung doesn't lock bootloader ?
Was going to post in QA, but I think this question might be better suited in dev section. Feel free to move if needed.
Click to expand...
Click to collapse
I think its cuz the drivers are proprietery but I know for sure its cuz Samsung jumbles up the source code so it makes it harder to combine the cm7 code with the Samsung code
Sent from my SCH-I500 using XDA App
I've wondered the same thing.. perhaps has something to do with the framework? Still no 'official' leak of the Gingerbread source for the Samsung Fascinate.. maybe someone can fill us in?
It has nothing to do with the bootloader. All an unlocked bootloader does is allows you to install custom ROMs and kernels without having to use elaborate workarounds like they use for the Droid X (and even then, there's no way to install custom kernels). The problem, as stated before, is with the proprietary code Samsung uses for its device drivers.
Incidentally, all questions belong in the Q&A section, even those having to do with development. The Development section is for posting ROMs, kernels, and mods, along with the occasional step-by-step guide.
Another Fascinating post by my XDA app...
jbarcus81 said:
I've wondered the same thing.. perhaps has something to do with the framework? Still no 'official' leak of the Gingerbread source for the Samsung Fascinate.. maybe someone can fill us in?
Click to expand...
Click to collapse
Well, considering that cm7 is gingerbread and that means .35 kernels (GB kernels). And our current functioning cm7's are using hacked. 32 kernels (froyo kernels), I'm amazed any of it functions. Jt and kaos have done an amazing job combining something that wasn't supposed to be together.
Sent from my SCH-I500 using Tapatalk
jmcintire said:
It has nothing to do with the bootloader. All an unlocked bootloader does is allows you to install custom ROMs and kernels without having to use elaborate workarounds like they use for the Droid X (and even then, there's no way to install custom kernels). The problem, as stated before, is with the proprietary code Samsung uses for its device drivers.
Incidentally, all questions belong in the Q&A section, even those having to do with development. The Development section is for posting ROMs, kernels, and mods, along with the occasional step-by-step guide.
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
As others have said, it's Samsung's proprietary code and stuff. But I have a question for you? Is that the case with the Galaxy S2 as well? I know they didn't use their proprietary RFS file system, is it the same with everything else?
GoogleAndroid said:
As others have said, it's Samsung's proprietary code and stuff. But I have a question for you? Is that the case with the Galaxy S2 as well? I know they didn't use their proprietary RFS file system, is it the same with everything else?
Click to expand...
Click to collapse
If you jump on over to the Galaxy S II Android Development forum and scroll down far enough, you'll find a thread for an AOSP ROM. In the OP you'll find a very familiar list of things that don't work. That tells me that Samsung has still not repented of its wayward ways and is still using proprietary code for its device drivers.
Another Fascinating post by my XDA app...
jmcintire said:
If you jump on over to the Galaxy S II Android Development forum and scroll down far enough, you'll find a thread for an AOSP ROM. In the OP you'll find a very familiar list of things that don't work. That tells me that Samsung has still not repented of its wayward ways and is still using proprietary code for its device drivers.
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
All OEM manufacturers use proprietary code, even HTC does. What really matters is how much did they change from the stock AOSP code, and how easy is it to reverse engineer the stuff that they did change that is needed. Samsung made a lot of stupid changes in our AOSP code that are unique to the Fascinate (like padding data) which makes trying to get AOSP working that much harder.
I am considering buying the SGS2 very soon. I am going to root it but here is my question. If I wait to get pushed the ATT update to 4.0 ICS do I have to flash back to stock just to root it? I want to wait for the stock push of 4.0 and just wipe off the bloatware and not have to worry about custom ROMs etc. Thanks for the help.
Currently running captivate with cognition 4.5.3 froyo.
Sent from my SAMSUNG-SGH-I897 using XDA App
Re: Root sgs2 after ATT update to ICS
Sent from my SAMSUNG-SGH-I897 using XDA App
You should be able to root after the update. But we don't know yet for sure.
Way too early to tell. You aren't going to see an official AT&T ICS OTA update for many months - if the Captivate is any indicator, not for at least a year.
Just wait for a Rom to be made , im sure one will be as soon as the sources are avail... I stopped doing the Ota upgrades when i realized its easier to just change the Rom.... So root... imo
Entropy512 said:
Way too early to tell. You aren't going to see an official AT&T ICS OTA update for many months - if the Captivate is any indicator, not for at least a year.
Click to expand...
Click to collapse
I'm hoping ATT/Samsung push it sooner because it's still one of ATT's highest end phones.
Of course, this is just wishful thinking.
Sent from my A500 using xda premium
Reading this thread, suddenly triggering me asking this question, I don't know why I haven't asked before: is there any ongoing development for ICS ROM?
I assume most of the custom ROMs surface in here are Gingerbread based OS.
votinh said:
Reading this thread, suddenly triggering me asking this question, I don't know why I haven't asked before: is there any ongoing development for ICS ROM?
I assume most of the custom ROMs surface in here are Gingerbread based OS.
Click to expand...
Click to collapse
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
eep2378 said:
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
There is development
Sent from my SGH-I777 using XDA App
eep2378 said:
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Google did release ICS source codes about a month ago, I'm sure you know that.
Alright, so only CM dev. team currently working on this then.
Thanks
votinh said:
Google did release ICS source codes about a month ago, I'm sure you know that.
Alright, so only CM dev. team currently working on this then.
Thanks
Click to expand...
Click to collapse
That's base platform source for Nexus devices with not a single bit of source for anything specific to the I9100 or I777.
You really need to educate yourself on what source has and has not been released, and what that source means and is used for, before posting crap like this.
Basically, I could spend a few hundred hours trying to port the 2.6.35.x drivers for Samsung-specific items to a vanilla Linux 3.0 kernel - only to have a halfassed buggy release ready after Samsung releases official ICS with kernel source for the I9100, which can be ported to the I777 in a matter of a few hours of work.
The CM dev team is not working on ICS for the I777 either - to get anything even working on the I9100 they had to resort to something they almost NEVER do, which is an initramfs repack of a binary kernel. Getting an I9100 binary kernel to work properly on an I777 is simply not possible - you can repack the initramfs all you want, the audio routing code will be different and so will the touchkey mapping code.
The only ICS development that will occur on the I777 prior to I9100 kernel source getting released (or an I777-specific leak showing up) is some basic reverse engineering efforts (mainly focused in audio routing), since the library swap Hellraiser uses can't be done with ICS (depends on audio blobs extracted from an I777 device.)
Entropy512 said:
That's base platform source for Nexus devices with not a single bit of source for anything specific to the I9100 or I777.
Click to expand...
Click to collapse
Did i ever mention about Nexus devices which running ICS, ehhh?
You really need to educate yourself on what source has and has not been released, and what that source means and is used for, before posting crap like this.
Click to expand...
Click to collapse
Wowww!!!
Just posted once sentence and being tagged with "crap like this"? LOL
By reading my English, do you understand that I just said Google has released ICS source codes? Did you see I am saying Google has released ICS source codes for I9100 or this specific i777, huh? Did you read and understand or just premature assumption?
Or you are telling me that you never know Google has release ICS source code?
Basically, I could spend a few hundred hours trying to port the 2.6.35.x drivers for Samsung-specific items to a vanilla Linux 3.0 kernel - only to have a halfassed buggy release ready after Samsung releases official ICS with kernel source for the I9100, which can be ported to the I777 in a matter of a few hours of work.
Click to expand...
Click to collapse
Are you the one who create Entropy512 DD kernel? If yes, every minute you spent is well appreciated, left alone a few hundred of hours.
If so, yes, you seem to be very smart in Android field but in life, learn to grow up and act nicely, politely to others. Get some love, kiddo.
The CM dev team is not working on ICS for the I777 either - to get anything even working on the I9100 they had to resort to something they almost NEVER do, which is an initramfs repack of a binary kernel. Getting an I9100 binary kernel to work properly on an I777 is simply not possible - you can repack the initramfs all you want, the audio routing code will be different and so will the touchkey mapping code.
Click to expand...
Click to collapse
Again, I don't know who is working on what so I asked. One of the poster mentioned about CM, so I just repeat it.
If they currently do it, great.
If they currently do not do it, it's ok.
I am just asking, 'cuz in B&N NOOKcolor forum, a lot of XDA dev. is WORKING on ICS ROM from ICS source code that released a while a go.
I thought XDA dev. in this room will also do the same.
The only ICS development that will occur on the I777 prior to I9100 kernel source getting released (or an I777-specific leak showing up) is some basic reverse engineering efforts (mainly focused in audio routing), since the library swap Hellraiser uses can't be done with ICS (depends on audio blobs extracted from an I777 device.)
Click to expand...
Click to collapse
Good too know.
I've learnt something.
Thanks
votinh said:
Did i ever mention about Nexus devices which running ICS, ehhh?
Wowww!!!
Just posted once sentence and being tagged with "crap like this"? LOL
By reading my English, do you understand that I just said Google has released ICS source codes? Did you see I am saying Google has released ICS source codes for I9100 or this specific i777, huh? Did you read and understand or just premature assumption?
Or you are telling me that you never know Google has release ICS source code?
Click to expand...
Click to collapse
Another poster said we were waiting for source.
You replied to him saying Google posted source over a month ago. Thus implying that you thought that Nexus platform source would actually be sufficient on its own to get our device running ICS - it isn't, it's nowhere close.
I'm sick and tired of repeated "WHERE'S ICS? GOOGLE POSTED SOURCE OVER A MONTH AGO!" posts.
Entropy512 said:
Another poster said we were waiting for source.
You replied to him saying Google posted source over a month ago. Thus implying that you thought that Nexus platform source would actually be sufficient on its own to get our device running ICS - it isn't, it's nowhere close.
I'm sick and tired of repeated "WHERE'S ICS? GOOGLE POSTED SOURCE OVER A MONTH AGO!" posts.
Click to expand...
Click to collapse
"Another poster" I assume you meant "eep2378, one that posted right above my "crappy post"?
Firstly, if eep not getting itchy, why you?
Secondly, I don't know what he meant about ICS for Nexus, and even if he meant that, he didn't spell out so I thought he meant the general ICS source code. In his next sentence, he actually mentioned about CM team working on it, even not fully function, w/o waiting for this specific phone ICS source code, so I thought he meant they, CM team are using the general source code, just like XDA dev. in B&N NOOKcolor room.
Thirdly, and if eep irritated about my post, I apologize him.
Now back to you, let's square and clear up all confuse, hardness.
You're a talented kid, good, keep it up. If you know something, teach us, I'm sure a lot of others will learn from you and quietly appreciate.
Be socialize with people around you, in real life or in cyber.
To the ICS related questions, if you don't want to answer, DO NOT answer, there's no one forces you to do so. There is no point to irritate about it.
votinh said:
"Another poster" I assume you meant "eep2378, one that posted right above my "crappy post"?
Firstly, if eep not getting itchy, why you?
Secondly, I don't know what he meant about ICS for Nexus, and even if he meant that, he didn't spell out so I thought he meant the general ICS source code. In his next sentence, he actually mentioned about CM team working on it, even not fully function, w/o waiting for this specific phone ICS source code, so I thought he meant they, CM team are using the general source code, just like XDA dev. in B&N NOOKcolor room.
Thirdly, and if eep irritated about my post, I apologize him.
Now back to you, let's square and clear up all confuse, hardness.
You're a talented kid, good, keep it up. If you know something, teach us, I'm sure a lot of others will learn from you and quietly appreciate.
Be socialize with people around you, in real life or in cyber.
To the ICS related questions, if you don't want to answer, DO NOT answer, there's no one forces you to do so. There is no point to irritate about it.
Click to expand...
Click to collapse
Ok let me try to clear up some confusion:
1) Nexus source code has nothing to do with I9100 or I777
2) I didn't mention anything about ICS for Nexus because(see #1) and this is the I777 forum NOT Nexus(another reason why I didn't mention it)
3)I mentioned CM9 because(RIGHT NOW) its the only thing that even approaches getting ICS on I9100 forget the I777. And Even Codeworkx(OP for CM9 aka Dev) is WAITING for ICS SOURCE to drop FOR THE I9100.
Only then, as Entropy said, are we able to get it working on the I777
4)I'm not "itchy" or irritated in the least and there is no need for an apology. Having said that I am fairly tired of reading posts about ICS source code being dropped/when are we getting ICS?/ Can ICS run on my I777?, etc.
Finally, ICS source code dropped FOR THE GALAXY NEXUS!! What does that mean for us?? SEE #1!!
@Entropy, I responded to you in another thread(in Q&A) Porting Bezke ICS KP8(yeah I know another one lol) regarding comments you made on Captivate and I9000 kernels being similar but I9100 and I777 not sharing the same similarities.
I'm sure you never went back to that thread, but didn't want bother you via pm
---------- Post added at 04:01 PM ---------- Previous post was at 03:44 PM ----------
Nick281051 said:
There is development
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
For the I777? Where?
I don't want to sound ignorant, but Samsung always releases the kernel source along with the ROM?