Push Samsung to release Exynos Source Code! [Update 25.11.13]
- Thread starter Scarface1991
- Start date
We need help from Anonymous
Sendt fra min GT-I9100
Hahahaa true!
They helped the PS3 hacking scene a year back.
Sent from my GT-I9100 using Tapatalk 2
Links where to reach Samsung are provided in the SIII petition thread:
http://xdaforums.com/showthread.php?t=1925709
I frankly dont have twitter account.. But if my one vote can contribute and make samsung to release Exynos codes. I ll make one today.. Rite now... Is thr any count how many votes have been done??
Edit: LOL dunno how to post on twitter. But posted a letter Hope they release before DEC 21st... I want to see JB buttery smooth on my S2
Edit: LOL dunno how to post on twitter. But posted a letter Hope they release before DEC 21st... I want to see JB buttery smooth on my S2
Last edited:
Done! I really hope we get a massive amount of people to do the same and finally push Samsung to release the sources which are needed by the developers. Otherwise, I am 100% sure that my next phone will be from the Nexus series.
You can write them a personal letter here:
http://opensource.samsung.com/recept...method=inquiry
if you don`t have time to write a big letter you can use an already written one a page ago
I edited the first page with a done letter that everyone can copy and paste if someone doesn`t have the time to write one
done
send it 2 times with 2 different email's
Perfect, this thing is growing and growing. It would be awesome if you guys tip popular blogs like Engadget.com and theverge.com and maybe they write about us, so more people will know that this campaign exists
Last edited:
awesome, I did it also, maybe they write about us, that would be so awesome if we would get a little support by very popular blogs like Engadget.
Edit:
I just send a message to The Verge:
Last edited:
Done though I'm not interested about aosp roms. Still it would be great to get all working properly in custom roms.
edit. Scarface1991 I think you should put that opensource.samsung.com website and the ready answer in the first post higher to get even the most laziest to send it forward. Now they see first the text that the needed info is in sgs3 thread.
Last edited:
I updated the first page with how to contact Samsung, so people can go there directly from this thread.
Thanks for the Facebook page, included it in the first page
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
110EDIT 25.11.13
The experimental Build with the new exynos sources works fine on the S3 and improves on graphics related stuff. There are some things that are broken but I hope those issues can be ironed out.
If someone wants to try it out, it can be downloaded here (FOR S3 I9300 ONLY):
http://dl.omnirom.org/omni-4.4-20131119-i9300-EXPERIMENTAL-GRAPHICS.zip
EDIT 19.11.13
Samsung dropped an insignal Update for the Exynos 4412 devices which can be used with AOSP. It's hard to implement but thanks to the brilliant developers at XDA there is hope. Check this out from the Omni Thread:
I have been too busy with other stuff to mess with them. In theory - actual working hwcomposer and maybe TV-out. More than 6 months after when they promised, Insignal finally dropped an update, but it proved extremely difficult to integrate at that time plus none of the "old" crew had much motivation to mess with it. Clement seems to have gained motivation and has done some great stuff so far.
The initial Insignal drop was actually for Exynos 4412 devices. 4412 and 4210 are nearly identical, main differences are regarding JPEG compression and the camera interfaces.
GeeckoDev:
Ok, so now hwcomposer isn't complaining anymore. Screen is completely black now because fences are timing out (surfaces are ready to be displayed when the fence is firing). dmesg is full of derp, looks like Mali driver is complaining. That's another progress... getting closer
EDIT: sent a mail to three samsung developers.. who knows
EDIT2: xplodwild should release a test build for i9300 users tomorrow.
The Test build is going to be for the I9300 but since the S2 has an almost identical SoC it's not far behind if everything works out for the I9300. It's great news and that's what we need
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before 2013:
EDIT
Until now there was a lot of talk from Samsung but everything they released so far is useless for AOSP. They promised full availability of Exynos Source Code by the end of 2012. Let`s see if this time they can keep their promise or if it will be just talk like in the past with the eMMC Super-Brick issue.
25/10/2012 Samsung Exynos Tweets:
https://twitter.com/SamsungExynos/status/261482746101235712
https://twitter.com/SamsungExynos/status/261483932925689856
Now let`s hope they really mean it and that they don`t open up something useless...
Nevertheless I`m glad that we accomplished something.
Samsung presentation at the Big Android BBQ:
chainfire tweets:
Complete Samsung Developers Session:
This thread is the equivalent to the one in the SIII Forums and not my idea. AntonLiv92 started the thread to inform people where they can write personal concerns to Samsung, so they will release the source code and proper documentation for Exynos based devices and as you probably all know our SII is based on Samsung`s Exynos 4210 processor.
This thread will inform you people where to contact Samsung, so that we get their attention or as codeworkx said:
So our goal is to get Samsung`s attention by writing as many concerns as possible of missing source code to Samsung. Of course it`s also important what you write, so it`s not just a big noob campaign asking for the Source Code. Codeworkx made a list of what is needed:
You can find a done letter that you can copy and paste more down below.
Main Petition thread in the SIII Forums created by AntonLiv92:
[MISSION] Let's get some Exynos sources! - xda-developers
There is also a thread in the Galaxy Note N7000 section as well now created by androidindian:
[IMPORTANT] Make Samsung release "Exynos" sources! - xda-developers
Galaxy Note II:
http://xdaforums.com/showthread.php?p=32684117#post32684117
And the AT&T Samsung Galaxy S II SGH-I777 section as well:
Samsung Exynos Movement(POLL ADDED) - xda-developers
German Thread regarding this issue:
http://www.android-hilfe.de/samsung...moegliche-freigabe-der-exynos-quellcodes.html
Thread on Androidforums:
http://androidforums.com/samsung-ga...1098-push-samsung-release-exynos-sources.html
Facebook group "Polite request to Samsung to release Exynos source code":
https://www.facebook.com/ExynosSourceCode
So yes we are serious about this!
HOW TO CONTACT SAMSUNG?
Via Twitter: https://twitter.com/SamsungExynos
https://twitter.com/samsungmobile
Via Facebook: https://www.facebook.com/SamsungMobile
Via Google+: https://plus.google.com/+SamsungMobile
You can write a personal letter regarding the release of the source code to:
http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
If you don`t have time for writing a big letter, this is a already written one that you can copy and paste:
Responses from Twitter @samsungExynos
There are other signs that this might go somewhere, since this concern is reported now on several popular Android-blogs like Androidcentral and sites like XDA Developers, which will lead to even bigger popularity on this issue.
They also contacted the CM team:
XDA:
Samsung Aware of Exynos Documentation Issue – xda-developers
Androidcentral:
Samsung 'hears' Exynos community documentation concerns | Android Central
Sammobile:
Samsung Listens To Developer Concerns Over Missing Exynos Docs | SamMobile
Androidauthority:
Samsung acknowledges lack of documentation for Exynos SoC
Androidpit:
Exynos-Affäre: Entwickler setzen Samsung unter Druck - AndroidPIT
Sammyhub:
Samsung Investigating Exynos Documentation Issue - Sammy Hub
Tech-Gadget:
Samsung ‘hears’ Exynos community documentation concerns | Tech Gadget
Other links in the SIII thread.
Here is also a great video that summarizes this whole mess about Samsung and Exynos:
It is also recommended to tip popular news-blogs like Engadget or the Verge, so maybe they write about us and what we try to accomplish.
I thought that this thread might be a good idea, since we have one of the biggest userbases on the Android-platform.
Now you guys know what to do
Big thanks to AntonLiv92 for letting me use the contact links in my thread21I didn't thought that I would ever update this thread after Samsung screwed us yet again but there is hope now. Samsung released an Insignal update of their Exynos Sources and it is something that devs can actually use with AOSP although it is really hard to implement. What good comes from it? If everything goes well, a working hw-composer and even tv-out.
I have been too busy with other stuff to mess with them. In theory - actual working hwcomposer and maybe TV-out. More than 6 months after when they promised, Insignal finally dropped an update, but it proved extremely difficult to integrate at that time plus none of the "old" crew had much motivation to mess with it. Clement seems to have gained motivation and has done some great stuff so far.
The initial Insignal drop was actually for Exynos 4412 devices. 4412 and 4210 are nearly identical, main differences are regarding JPEG compression and the camera interfaces.
GeeckoDev:
Ok, so now hwcomposer isn't complaining anymore. Screen is completely black now because fences are timing out (surfaces are ready to be displayed when the fence is firing). dmesg is full of derp, looks like Mali driver is complaining. That's another progress... getting closer
EDIT: sent a mail to three samsung developers.. who knows
EDIT2: xplodwild should release a test build for i9300 users tomorrow.
The Test build is going to be for the I9300 but since the S2 has an almost identical SoC it's not far behind if everything works out for the I9300. It's great news and that's what we need16pfft, @GeeckoDev is just another frenchie...
I'm trying to teach a lesson to these old apes that thought that exynos was dead. :laugh:14
It basically enables us to use hardware overlays, which means that the GPU has less work to do because all the compositing work is managed by fimd. Better performance (butter), lower power consumption. :good:
Getting back to work :angel:
