Database Users

HTC Evo Kernel Source to be released soon

I have been contacting HTC and different departments and contacts to find out when all the backlog source data will be released...
This is specific to:
3.29.651.5 updated kernel to 2.6.32.15-ge2fb08e [email protected]
3.30.651.2 updated kernel to 2.6.32-15-g0f673ed kernel #10
3.70.651.1 updated kernel to 2.6.32-17-gee557fd kernel #15
I finally got the final confirmation e-mail back from my contact.
All information about the contact has been removed due to confidentiality statements at the bottom of the e-mail.
So keep your eyes peeled on the HTC source site for these releases. If i get anymore info i will let you know
We are in the final Stages of releasing the data, as soon as we know an exact date we will let you know.
******
Technical Support Specialist
T +1 xxx.xxx.xxxx
13920 SE Eastgate Way Suite 400
Bellevue, WA 98005

Yea sounds like its coming sometime in 2011....not holding my breath

Have you really been bugging these people for this?
Sent from my PC36100 using XDA App

I was asked to by some Evo Developers who want the source code updates to look at. I have experience with getting manufacturers (specifically Samsung in the past) to actually commit and release the opensource code protected by the GNU GPL v2.

DirtyShroomz said:
Have you really been bugging these people for this?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
most developers are curious how HTC removed the 30 fps cap (took methods developers here created or some alternative way).
also, having the real drivers from HTC for the new hardware 4 phones, basically diff hardware camera is used and i dont think anybody has released a working custom kernel with the correct drivers for the hw 4 camera. it would be nice to see the source code to know for sure whether or not any other hardware changed in ver 4.
among other things, its always great to have the latest source code for the kernel they release as it allows us to keep creating custom kernels either based on HTC's latest drivers or at least be able to use their source code as reference.
hope that helps satisfy your curiosity as to why we are very very happy to finally hear a response from HTC, who hasnt released any of their linux modified kernel source code which falls under the GPL v2 license, for the last few months.

Glad to see you're on it numus I've been wondering what's taking them so long and why more people haven't been complaining about it.

^ 5 bru!!!!!

numus said:
I have been contacting HTC and different departments and contacts to find out when all the backlog source data will be released...
This is specific to:
3.29.651.5 updated kernel to 2.6.32.15-ge2fb08e [email protected]
3.30.651.2 updated kernel to 2.6.32-15-g0f673ed kernel #10
3.70.651.1 updated kernel to 2.6.32-17-gee557fd kernel #15
I finally got the final confirmation e-mail back from my contact.
All information about the contact has been removed due to confidentiality statements at the bottom of the e-mail.
So keep your eyes peeled on the HTC source site for these releases. If i get anymore info i will let you know
We are in the final Stages of releasing the data, as soon as we know an exact date we will let you know.
******
Technical Support Specialist
T +1 xxx.xxx.xxxx
13920 SE Eastgate Way Suite 400
Bellevue, WA 98005
Click to expand...
Click to collapse
They are Tech Support....they will tell you what you want to hear. Don't hold your breath on this one.

twin001 said:
They are Tech Support....they will tell you what you want to hear. Don't hold your breath on this one.
Click to expand...
Click to collapse
I actually talked to some developers at HTC... they wont directly email anything to me tho so they are using this guy as the relay.

Good job. This its essential.
Sent from my PC36100 using XDA App

"Soon" in HTC or Valve Time usually translates to "three to eighteen months."

Looks like it's finally out!
http://developer.htc.com/
HTC EVO 4G (Sprint) – Froyo MR2.5 – 2.6.32 release
HTC EVO 4G (Sprint) – Froyo MR2.51 – 2.6.32 release
HTC EVO 4G (Sprint) – Froyo MR3 – 2.6.32 release

Yea yea.....yea for beer.
Sent from my PC36100 using XDA App

Wonder how long before rom devs start incorporating this into their kernels and roms

Samsung conforms to source 100% better than HTC now. But HTC actually updates their software

I hope soon. I need some custom kernels on my evo. I got that new cam in mine.
Sent from my PC36100 using XDA App

WHo you telling. I'm living without my camera now because I NEED the better battery life.

This is awesome! Been waiting to oc to see what this thing can do.
Sent from my PC36100 using XDA App

I am amazed 50 threads have not been posted.
Sent from my iPhone with the bigger Gee Bees.

Been on a security detail the past few days.. Glad to see they finally released!

Samsung 2.2 source

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

Samsung source code for galaxy S phones gingerbread released today

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.

I see news like this, and my brain explodes

So, you see headlines like this:
"Samsung Releases Conquer 4G Kernel Source Code Before The Phone Even Hits Shelves"
http://www.androidpolice.com/2011/0...urce-code-before-the-phone-even-hits-shelves/
And I can't help but think to myself..."OK, so Sammy is starting to see the benefit of getting source code out for its devices, this is good", and then I sit back and reflect upon the fact that the Epic still doesn't have the source code we're looking for (amirite?).
Now, I'm not going to piss and bemoan the fact, BUT, I am going to wonder why it is so. Is there some sort of secret sauce there? Or perhaps is there something VERY embarrassing in their source code? OR, is Sammy really that schizo?
In all, I've been pleased with the steps Sammy has taken. Sure, it would be nice to have me some GB, or even better some CM7, but hey, the Epic is still a great device despite some of the quirks that need to be straightened out.
Thoughts?

Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons

musclehead84 said:
Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons
Click to expand...
Click to collapse
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?

the reason CM7 isn't fully functional for our phones is a kernel and drivers issue. Without GB source for those, we have a hacked together partially working port.

Got it.
Well, if that didn't make your head asplode, then this surely will:
http://www.homestarrunner.com/sbzone.html

It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.

MeetFace said:
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?
Click to expand...
Click to collapse
Plus driver source isnt open source so they don't have to give it to us

it ships with GB, what do you mean it's not being built yet? I think they are not releasing source for us because our phones are reaching EOL and they want us to buy new ones.

theduce102 said:
Plus driver source isnt open source so they don't have to give it to us
Click to expand...
Click to collapse
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App

CapsLockKey said:
It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.
Click to expand...
Click to collapse
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.

mkasick said:
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.
Click to expand...
Click to collapse
This makes rational sense. Would be nice if they released those driver sources this next time around. Would be a good measure to producing goodwill & brand loyalty IMO.

No phone company has ever released driver sources and nor will they. Its open kernel source not open driver source. There is some other reasons they don't release driver source but it would be nice if all phone manufacturers did but that's a perfect world

Phone companies haven't but what about component companies like Nvidia they released Nvflash
Sent from my Transformer TF101 using XDA Premium App

xopher.hunter said:
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
No. As stated 1000 times, it is 100% possible to write drivers, a kernel and etc from scratch just much more labor intensive than using source code.

Sooo, just wondering if since the conquer 4g is VERY similar to the epic since its gb source code was released would it help us at all?
I'm just asking cause my moment ran on a frankenstein froyo port that came mostly from the transform and a little bit from the intercept and it was awesome.
Sent from my SPH-D700 using XDA Premium App

[Discussion] Exynos to be open source!

After months of speculation, there is finally something clear about the Samsung Exynos processor…
Samsung will open Source the Mali codes Exynos Codes they will provide binaries all most everything.
This appears from the Samsung Developers Session in America. Samsung who hold today.
The entire information Samsung makes clear later but this is very good news for developers. This Samsung creates a big boost in their community.
They say there will be more information in the coming weeks!!!
SamMobile we keep you informed.
Share your thoughts, speculations
Source
http://www.sammobile.com/2012/10/21...nos-will-go-open-source/#.UIRNmGlUJEg.twitter

great news
LastStandingDroid said:
After months of speculation, there is finally something clear about the Samsung Exynos processor…
Samsung will open Source the Mali codes Exynos Codes they will provide binaries all most everything.
This appears from the Samsung Developers Session in America. Samsung who hold today.
The entire information Samsung makes clear later but this is very good news for developers. This Samsung creates a big boost in their community.
They say there will be more information in the coming weeks!!!
SamMobile we keep you informed.
Share your thoughts, speculations
Source
http://www.sammobile.com/2012/10/21...nos-will-go-open-source/#.UIRNmGlUJEg.twitter
Click to expand...
Click to collapse
Happy to hear that
n more happy to own a *SAMSUNG* galaxy S2.. :good:

Everyone calm down.
This is not done yet.
Yes, Samsung will release Exynos source code. "Hurraay!!!" ??? No!
What they mean by releasing Exynos source code, is that they will release source code for hardware modules for Exynos development boards. We had this for months on insignal website (which is down since a few weeks/months, but used to be up), which contains outdated source code for Exynos boards. We had some bits of Ice Cream Sandwich code back in March or April iirc, that helped Galaxy S II hwcomposer, but that's it. Most of the things were stuck at Gingerbread version, and they don't contain any device-related code.
What does this mean ? For instance, Galaxy S III camera will stay closed, because it is NOT part of Exynos development boards. Galaxy S II audio is still Yamaha proprietary crap, and we will NOT get source code. RIL interface will also remain closed, so all exynos phones will keep on having broken/semi-functional GSM connection (broken Sim Toolkit, unstable data connection, unstable roaming). TV Out will still remain undocumented, and Android interface won't be opensourced (as it is part of TouchWiz on official ROMs). Same applies for FM Radio.
Moreover, Insignal code drops were delayed as hell. As of today, we still haven't got anything from official Samsung Jelly Bean, beside kernel source code because they legally have to. As I said, most of the things on Insignal were old, hwcomposer sources for example weren't working on Galaxy S III (exynos4412), and so on.
Now, I could be wrong and MAYBE they will make this A BIT better (faster code drops), but I'm NOT putting my hopes up on things like Sensors HAL source code, Audio source code, RIL interface documentation, or Camera HAL source code. IMO they just spoke like this to calm down community flood, and make everyone happy and make Samsung look like they're the new holy grail of developers. I'm not trusting this until I actually SEE those improvements.
So, users, be careful, and we'll see how it's going to get.
http://forum.xda-developers.com/showpost.php?p=33092439&postcount=10618

anshmiester78900 said:
Everyone calm down.
This is not done yet.
Yes, Samsung will release Exynos source code. "Hurraay!!!" ??? No!
What they mean by releasing Exynos source code, is that they will release source code for hardware modules for Exynos development boards. We had this for months on insignal website (which is down since a few weeks/months, but used to be up), which contains outdated source code for Exynos boards. We had some bits of Ice Cream Sandwich code back in March or April iirc, that helped Galaxy S II hwcomposer, but that's it. Most of the things were stuck at Gingerbread version, and they don't contain any device-related code.
What does this mean ? For instance, Galaxy S III camera will stay closed, because it is NOT part of Exynos development boards. Galaxy S II audio is still Yamaha proprietary crap, and we will NOT get source code. RIL interface will also remain closed, so all exynos phones will keep on having broken/semi-functional GSM connection (broken Sim Toolkit, unstable data connection, unstable roaming). TV Out will still remain undocumented, and Android interface won't be opensourced (as it is part of TouchWiz on official ROMs). Same applies for FM Radio.
Moreover, Insignal code drops were delayed as hell. As of today, we still haven't got anything from official Samsung Jelly Bean, beside kernel source code because they legally have to. As I said, most of the things on Insignal were old, hwcomposer sources for example weren't working on Galaxy S III (exynos4412), and so on.
Now, I could be wrong and MAYBE they will make this A BIT better (faster code drops), but I'm NOT putting my hopes up on things like Sensors HAL source code, Audio source code, RIL interface documentation, or Camera HAL source code. IMO they just spoke like this to calm down community flood, and make everyone happy and make Samsung look like they're the new holy grail of developers. I'm not trusting this until I actually SEE those improvements.
So, users, be careful, and we'll see how it's going to get.
http://forum.xda-developers.com/showpost.php?p=33092439&postcount=10618
Click to expand...
Click to collapse
it was never told to be anything more than Exynos code to be released

If I learnt one thing from buying a samsung was:
Never buy a samsung, unless is a nexus!
I'm not sure what will be the usage of those docs though, most of the developers already migrated from samsung, atleast teamhacksung did

What about Galaxy note 2 AOSP, cm10, aokp ect. roms? Will that be any useful to them as in maybe s pen functionality?

D4rKn3sSyS said:
If I learnt one thing from buying a samsung was:
Never buy a samsung, unless is a nexus!
I'm not sure what will be the usage of those docs though, most of the developers already migrated from samsung, atleast teamhacksung did
Click to expand...
Click to collapse
+1

anshmiester78900 said:
Everyone calm down.
This is not done yet.
Yes, Samsung will release Exynos source code. "Hurraay!!!" ??? No!
What they mean by releasing Exynos source code, is that they will release source code for hardware modules for Exynos development boards. We had this for months on insignal website (which is down since a few weeks/months, but used to be up), which contains outdated source code for Exynos boards. We had some bits of Ice Cream Sandwich code back in March or April iirc, that helped Galaxy S II hwcomposer, but that's it. Most of the things were stuck at Gingerbread version, and they don't contain any device-related code.
What does this mean ? For instance, Galaxy S III camera will stay closed, because it is NOT part of Exynos development boards. Galaxy S II audio is still Yamaha proprietary crap, and we will NOT get source code. RIL interface will also remain closed, so all exynos phones will keep on having broken/semi-functional GSM connection (broken Sim Toolkit, unstable data connection, unstable roaming). TV Out will still remain undocumented, and Android interface won't be opensourced (as it is part of TouchWiz on official ROMs). Same applies for FM Radio.
Moreover, Insignal code drops were delayed as hell. As of today, we still haven't got anything from official Samsung Jelly Bean, beside kernel source code because they legally have to. As I said, most of the things on Insignal were old, hwcomposer sources for example weren't working on Galaxy S III (exynos4412), and so on.
Now, I could be wrong and MAYBE they will make this A BIT better (faster code drops), but I'm NOT putting my hopes up on things like Sensors HAL source code, Audio source code, RIL interface documentation, or Camera HAL source code. IMO they just spoke like this to calm down community flood, and make everyone happy and make Samsung look like they're the new holy grail of developers. I'm not trusting this until I actually SEE those improvements.
So, users, be careful, and we'll see how it's going to get.
http://forum.xda-developers.com/showpost.php?p=33092439&postcount=10618
Click to expand...
Click to collapse
Nice POW I didn't knew all this background before
Sent from my GT-I9100 using xda app-developers app

Samsung actually didnt want its customers to go for custom. Thats why they put so many features as a part of touchwiz in note 2 rather than independent apps. Its because they want to gather their users to be their advertisement material in future. They want to be the next apple. I heard a rumor that samsung is working on its own OS. they only wanted the developers in their bad times. When they were unable to port the ics to their devices. They actually used the dev community. When their stock roms are delayed its he devs that keep us silent by giving us the custom rom. Plus samsung didnt really want to release the source because most of the features of its new flagship phone will be ported to older devices. Like multi screen multitasking on note 2 will be ported to s3 and note 1. They are scared of this. They just want to sell new devices each year.
Sent from my GT-N7000 using xda app-developers app

Be careful man because as I know from past experience that some people like the phrase "never was heard a discouraging word" on here. You never know, you might be accused of making "false statements"!!!!
Sent from my GT-I9100 using xda premium

samsung is a real motherf***er if they will not release the code me and 15 friends will nerver buy any samsung stuff we all 15 friends have s2 s3 and samsung glaxy nexus
here if the samsung will not release the code 15 customer will leave the samsung

Here's Entropy512's take on the recent events:
Entropy512 said:
Ok quick checkin from BABBQ. After this post I'm putting my BT keyboard away and getting drunk, and likely won't return to XDA until Monday or Tuesday evening.
The official announcement was kinda "meh". It's really what's going on behind the scenes that is mattering.
There are multiple devrel people at Samsung, many of whom weren't even aware of each others' existence. They now are, and I have quite a few new contacts. Now, requests from us are probably going to go through multiple chains. Whether this makes a difference, who knows - but it is a potential step forward.
They also had an engineer from LSI that I talked to personally. It was a bit difficult due to the language barrier, but I sort of got the impression that the problems with current Insignal source on our phones aren't phone-specific - some of this **** is broken even on the OrigenBoard itself. Same case for libcamera - it sounds like the current Insignal one is pretty low-quality/broken, and the "new" source may be improved. It won't be directly usable on our devices, but it may represent a significant step forward. e.g. instead of "it's totally and completely broken", it may be "sorta working and needs some tweaking for each camera module" - See, for example, use of the Nexus S libcamera on Aries-family devices - each one has needed device-specific work, but instead of being an insurmountable task, it may be feasible. However, please keep reading regarding maintainer exhaustion...
I also got the impression that future Insignal drops are going to be more aggressively managed by LSI. Again... none of this is official.
November is likely to be another ICS tarball, however, one that is actually working. The engineer I spoke to said that the actual JB differences are minimal. (As in, I know what they are, and in fact we have an implementation of the JB differences in Gerrit already. The problem is the underlying hwcomposer is apparently broken even for OrigenBoard+ICS with the current Insignal source. Functional ICS HWC shouldn't be too hard to JB-ify. (Look at the Nexus S HWC as an example of what needs to be done to go from ICS to JB.)
The new source drop might also allow us to finally fix HDMI.
The problem is - Thanks to the lack of documentation for the past few months, the team of CM maintainers for Exynos are exhausted and far behind on other non-Exynos-specific stuff. So this isn't going to be a magic bullet. It alone probably won't get us M builds.
However the other "behind the scenes" item is that a bunch of Samsung people were here, and they're probably going to be writing trip reports to management. This trip reports are going to likely include the massive amount of pwnsauce Sony dished out. Speaking of that - Espenfjo, xplodwild, and codeworkx, Y U NO FLY HERE? Chainfire, Jerpelea, and Supercurio were all here. U NO GET SMARTWATCH!
So Samsung Mobile might be more receptive to community requests in the future. Our contacts are likely to be in a MUCH better position to facilitate things than before.
So it's a step forward... But it's likely to be months before any of us consider a new Exynos device, and our current devices are likely to always be behind others because we're just too far behind as it is. But if Samsung keeps on improving, after a few months users might see definitive improvements.
With all of that said, I'm off to party and feast. You won't see any more from me until Monday evening at the absolute earliest.
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
His post is a little more optimistic than xplodwild's, but we should wait and see like he said!

i think this is a step in the right direction
dont let your hope down i think something amazing is coming

bluefa1con said:
i think this is a step in the right direction
dont let your hope down i think something amazing is coming
Click to expand...
Click to collapse
Yeah, at this point it's better to be optimistic. Though we should still keep pressuring them until we have something concrete.

What does it mean for common user? Will that add some extra features for SGS II example or what?

LastStandingDroid said:
After months of speculation, there is finally something clear about the Samsung Exynos processor…
Samsung will open Source the Mali codes Exynos Codes they will provide binaries all most everything.
This appears from the Samsung Developers Session in America. Samsung who hold today.
The entire information Samsung makes clear later but this is very good news for developers. This Samsung creates a big boost in their community.
They say there will be more information in the coming weeks!!!
SamMobile we keep you informed.
Share your thoughts, speculations
Source
http://www.sammobile.com/2012/10/21...nos-will-go-open-source/#.UIRNmGlUJEg.twitter
Click to expand...
Click to collapse
That's most probably useless unless they have a significant changes about exynos docs because that news was for Origen board which so different h/w with s2.
Sent from my GT-I9100 using xda app-developers app

Burgscheinkerkdeiktraast said:
What does it mean for common user? Will that add some extra features for SGS II example or what?
Click to expand...
Click to collapse
This will make CM stable(its already stable for me but not stable for some samsung rom users here) and we will get future android versions without the help of samsung(if they release the correct sources which are required to cm devs)