http://www.engadget.com/2010/12/17/android-2-3-gingerbreads-source-code-now-available/
Looks like the devs can get to it now.
Samsung has released the Android 2.2 source code for its Fascinate 3G+ for Telus. Which is basically the US Vibrant, good news?
Sent from my SGH-T959 using XDA App
I think samsung knows that vibrant owners are frustrated.. so they released the source code for the great developer to create roms off of...
Software must not be ready yet for the US variants and this is the least samsung can do, the source code as a band aid until the official froyo releases for the US vibrant..
edit.. oh samsung will release the code anyway.
Im normally not the type who nags on anyone's twitter... but after reading yesterday's maddening news/rumor about samsung flawed business practices that promotes greediness.. i did on both their twitter accounts.. lol..
Don't start a flame war.
I wont be dealing with it.
Any news on when Samsung will be releasing their source code?
Wasn't there a certain amount of time they have to release the codes after they release the rom? Was it 60 days?
I heard they released it for the captivate, ours can't be too far behind.
I didn't see the US captivate source unless I just entered in the wrong model number.
They must release it in like 30 days.
They dont have any othr choice
eunkipark92 said:
Don't start a flame war.
I wont be dealing with it.
Any news on when Samsung will be releasing their source code?
Wasn't there a certain amount of time they have to release the codes after they release the rom? Was it 60 days?
Click to expand...
Click to collapse
From what I get out of this, I have been told I am wrong.... and I honestly hope I am... but this is how I see it.
They have 60days according to the what ever open source agreement I don't feel like remembering what its called right now, ha. AFTER and OFFICIAL update to let the source code go.
HOW EVER! When they announced that they WILL let the source out... they said with in 60days of the OFFICIAL OTA, its all in the wording. Someone else pointed out that an update through Kies is NOT an official update, the only way it is official is if Tmobile pushes it through an OTA... and if you think about it that true.
But they pissed everyone off once and there was a backlash against them.... do you really think they will mess up like that again?
ipeench said:
From what I get out of this, I have been told I am wrong.... and I honestly hope I am... but this is how I see it.
They have 60days according to the what ever open source agreement I don't feel like remembering what its called right now, ha. AFTER and OFFICIAL update to let the source code go.
HOW EVER! When they announced that they WILL let the source out... they said with in 60days of the OFFICIAL OTA, its all in the wording. Someone else pointed out that an update through Kies is NOT an official update, the only way it is official is if Tmobile pushes it through an OTA... and if you think about it that true.
But they pissed everyone off once and there was a backlash against them.... do you really think they will mess up like that again?
Click to expand...
Click to collapse
Yes. Source code doesn't look like it will be released soon. When it finally is, I'm pretty sure we will have 2.3.2 working.
CM 7 for Galaxy S is pretty close to done. Codeworkx just posted a video of CM 7 Gingerbread running on the I9000 pretty flawlessly.
It's here.
http://www.youtube.com/watch?v=C2DsF7VT3ms
Krylon360 is working out the bugs on a TW build of Gingerbread as well (its working, just buggy). And Eugene seems to have figured out the battery drain from the I9000 kernels so if he has indeed, a LOT of I9000 things will be ported. This coming month is my expectation we will see fully functional Gingerbread on the Vibrant.
The source code for Froyo won't be relevant soon really. . .
Official isn't how the copyright is worded. Its 60 days from when you release. Putting something on Kies, an official source of software from Samsung counts as a release. Doesn't have to be OTA, doesn't have to be delivered by UPS, all that matters is it is released through an official channel, which it has been.
zharptitza said:
I didn't see the US captivate source unless I just entered in the wrong model number.
Click to expand...
Click to collapse
I think I read the rogers captivate, and the armani branded captivate source were released.
How long did it take for the i9000 2.2 Source to be released?
ipeench said:
From what I get out of this, I have been told I am wrong.... and I honestly hope I am... but this is how I see it.
They have 60days according to the what ever open source agreement I don't feel like remembering what its called right now, ha. AFTER and OFFICIAL update to let the source code go.
HOW EVER! When they announced that they WILL let the source out... they said with in 60days of the OFFICIAL OTA, its all in the wording. Someone else pointed out that an update through Kies is NOT an official update, the only way it is official is if Tmobile pushes it through an OTA... and if you think about it that true.
But they pissed everyone off once and there was a backlash against them.... do you really think they will mess up like that again?
Click to expand...
Click to collapse
Ka6 has to be the official cause I remember sammy saying that they released the official 2.2 update on fb
Sent from my SGH-T959 using XDA App
I hope this is a release that is worthy of development for the Fascinate I look forward to see whats next. Our devs so incredible work and i hope this will help them with future development.
This was released two days ago. The code is for international version. Can't do anything with it.
Sent from my SCH-I500 using Tapatalk
Oh my bad I thought i was looking at a new release from today perhaps i just miss read.
It was for uk galaxy s, the vibrant got it today and were stuck on 2.1 well for non rooted users
Sent from my SCH-I500 using XDA App
This really doesn't mean much of anything, just like the Froyo version didn't really help us. If Samsung's code wasn't horrible, then yeah. But it is.
(apparently even Samsung's Froyo source for our phone didn't particularly help with AOSP/CM/MIUI porting efforts... yes, Samsung's developers are that bad)
KitsuneKnight said:
(apparently even Samsung's Froyo source for our phone didn't particularly help with AOSP/CM/MIUI porting efforts... yes, Samsung's developers are that bad)
Click to expand...
Click to collapse
It didn't help because Samsung isn't required to release the source for the parts that are causing the biggest issues. They released what they had to based on the licensing, but that didn't include any of their proprietary code, which is where the problems lie.
With the release of ICS next week, does anyone know if the source code will be released for it as well? I know a while back that they said they would release the code when it was ready after Honeycomb launched.
Google say it will be open sourced, so it should be.
Oh, and we don't KNOW that ICS is released next week. So far it's just rumour.