Just send this letter to: http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
done
send it 2 times with 2 different email's
Just send this letter to: http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
Just send this letter to: http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
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??
Can somebody write letter and twitter comment how we will all send same message to Samsung and update them on first topic?
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.
i just sent message to Engadget hope they will do something :fingers-crossed:
HI, first of all I am a daily reader of your blog and I think it`s one of the best. Your articles are always up to date and great written.
I am a member of the famous XDA-Developers.com site and in the last days the community started a campaign to ask Samsung to release the Source Code and proper documentation for their Exynos based devices. Without this Source Code it`s very hard to impossible for great developers inside the Android community to develop stable ROMs like the CyanogenMod, that adds additional features to Android and makes it possible to be on the newest Google Vanilla-Android version before the manufacturer releases it to the public or even when the manufacturer doesn`t support the phone anymore.
Without Samsung`s help we will loose great developers as they will leave to other companies which provide the source code, like Qualcomm or Texas Instruments.
It`s already happening as a great developer named codeworkx left the Galaxy SIII because of the above stated issues.
There is a petition thread on XDA-Developers.com where people can look up where to contact Samsung about this issue:
http://xdaforums.com/showthread.php?t=1925709
A couple of days later Samsung responded with this:
http://104.imagebam.com/download/RbncvKyotH6-SI6zjN6uNQ/21436/214356937/CM10.png
and this:
http://106.imagebam.com/download/o6jfPwJIu_R3ehPKzopo0w/21436/214356779/CM.png
So they are aware of this issue and other popular Android blogs and sites started to write about us:
Androidcentral:
http://www.androidcentral.com/samsung-hears-exynos-community-documentation-concerns
and of course XDA-developers:
http://www.xda-developers.com/android/samsung-aware-of-exynos-documentation-issue/
just to name a few.
Other petition threads regarding this issue:
Galaxy Note N7000:
http://xdaforums.com/showthread.php?p=32622901#post32622901
Galaxy SII:
http://xdaforums.com/showthread.php?t=1929188
AT&T Samsung Galaxy S II SGH-I777:
http://xdaforums.com/showthread.php?p=32624976#post32624976
I don`t know if it`s worth a news for you but I really hope that you support us a little by making this more public, so maybe we can make a difference in Samsung`s arrogant behavior.
Just send this letter to: http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
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.
Hi guys,
I am a member of the famous XDA-Developers site and I`ve been following the CyanogenMod progress for some time now and a big problem for CM developers is to bring a stable and bugfree version of Jelly Bean to Samsung Exynos based devices because there is no source code and no proper documentation. Now people from the XDA community including myself created numerous petition threads. Goal of those threads is that Samsung releases the Source Code and proper documentation for their Exynos based devices. We had our first "success" and got their attention:
http://104.imagebam.com/download/RbncvKyotH6-SI6zjN6uNQ/21436/214356937/CM10.png
and
http://106.imagebam.com/download/o6jfPwJIu_R3ehPKzopo0w/21436/214356779/CM.png
Now more and more people are asking Samsung the same thing and our goal is to make this as popular as possible.
Other Android blogs and sites already reported about this
XDA:
http://www.xda-developers.com/android/samsung-aware-of-exynos-documentation-issue/
Androidcentral:
http://www.androidcentral.com/samsung-hears-exynos-community-documentation-concerns
TalkAndroid:
http://www.talkandroid.com/135667-s...loper-community-concerns-about-documentation/
just to name a few.
Links to the petition threads:
Galaxy SII I9100:
http://xdaforums.com/showthread.php?t=1929188
Galaxy SIII:
http://xdaforums.com/showthread.php?t=1925709
Galaxy Note N7000:
http://xdaforums.com/showthread.php?p=32622901#post32622901
AT&T Samsung Galaxy S II SGH-I777:
http://xdaforums.com/showthread.php?p=32624976#post32624976
People from Samsung already contacted the CyanogenMod Team and they told them what we want to have.
Here is what one of the main CM developers codeworkx wrote:
Seems you got korea's attention because of the "flooding" the community is currently doing via opensource.samsung.com. twitter, facebook and so on. They contacted us and we told them again what the community wants to have.
I don`t know if it`s worth a news here but I thought I try it and let you know about this.
Dear Sir or Madam,
Thanks for your continuous interest in our products.
We received your request on OSRC.
We will provide the response ASAP, if your request is related to FOSS.
(This site is just for providing source code of FOSS Software we have used in our product.
You could contact with other types - ex. firmware - on your local Samsung support homepage.)
Thank you.
Sincerely yours,
In collaboration with geecko, here's a test build with the updated graphics stuff.
======== Don't expect it to be working 100% correctly that's not the goal. This build is exclusively to get your feedback on graphics and overall performance of the ROM. It is known that Camera and video playback might be both broken partially in this build.
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:
I found those 2 interesting commits:
https://gerrit.omnirom.org/#/c/2431/
https://gerrit.omnirom.org/#/c/2436/
What's with the insignal exynos4 update? Does it actually do any good? (I would be very surprised if Samsung would actually do something positive for the developer community ^^)
And also will the second commit when implemented enable tv-out on the I9100? Will this be usable on other Exynos devices especially the I9300?
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.
Yes, we are opening up HAL source code for the platform, which includes HWC, camera, gralloc, audio and light.
https://twitter.com/SamsungExynos/status/261482746101235712Developers: Expect full availability of integrated source code for #Exynos 4 family of processors on OrigenBoard by the end of 2012!
https://twitter.com/SamsungExynos/status/261483932925689856Git server access will also be available to the public in Nov. 2012
It seems Samsung is saying there will be sourcecode for the needed Exynos parts... I'm not sure it's everything TeamHacksung needs, ...
... but I'm sure they'll let us know. It all sounds very promising though. First stuff should be seen in weeks, complete before 2013.
Originally Posted by codeworkx
If they don't know that there are a lot of users out who are pissed because of the bad exynos support, then they'll not change anything.
If 10 users are crying -> just 10 users, ignore them.
If 1000 users are crying -> ok, let's think a few minutes about it.
If 100.000 users are crying -> holy ****, we have to do something
If you stop crying, they'll stop paying attention and you've achieved nothing like in the past.
Originally Posted by codeworkx
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Requester: Enter your name.
ID (E-mail): Enter your email address.
Country: Select your country.
Inquiry Type: Select "Request for Source Codes".
Model: Enter "Samsung I9100 Galaxy S II".
Message: Copy & Paste the following...
Dear Samsung,
without a doubt you build the best phones on the market and I really enjoy using the Galaxy SII I9100 but there is a problem. A lot of people like to use mods like the popular CyanogenMod on your flagship
devices. Without the source code and proper documentation great developers like codeworkx who is a device maintainer for Samsung phones at XDA-Developers.com start to turn their back on Samsung
phones like the Galaxy SIII because they are based on the Exynos processor due to the fact that there is a lack of source code and proper documentation. Since developers are the lifeblood of Android it`s
not a good sign to see them leave to other companies who provide proper source code and documentation. Qualcomm and Texas Instruments understand that and they released their source code and
developers are using it to do great things.
With this letter I ask you to release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 and in the best case it should include the following:
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Thank you for your great phones and I really hope that you will release the above stated things.
Seems you got korea's attention because of the "flooding" the community is currently doing via opensource.samsung.com. twitter, facebook and so on. They contacted us and we told them again what the community wants to have.
You know that bad press for samsung is our most effective weapon to make things changing.
So if you want to make samsung to continue paying attention, you know what to do...
Fight till you got what you want to have.
I found those 2 interesting commits:
https://gerrit.omnirom.org/#/c/2431/
https://gerrit.omnirom.org/#/c/2436/
What's with the insignal exynos4 update? Does it actually do any good? (I would be very surprised if Samsung would actually do something positive for the developer community ^^)
And also will the second commit when implemented enable tv-out on the I9100? Will this be usable on other Exynos devices especially the I9300?
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.
I don't have the link right now for the insignal stuff but on the first post you can see the commits used in the Omni experimental build. Many Users said it improved graphic related performance stuff (like UI scrolling, 2D, 3D) noticeably.