Related
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)
Hi
I'm Asking If There Are Any Custom Roms Like CM, Aokp...etc. For i9500 Will Be Release In The Next Months When Samsung Release Source Code For Exynos 5 Octa
Sent from my GT-I9500 using Tapatalk 4 Beta
Samsung are not going to release the source code for any Exynos chipset, or at least not properly. It's something they have been promising for years and never have. Seriously, don't hold your breath.
Sent from my Qualcomm Galaxy S4
Why CyanogenMod still not released for i9500?
Did i9500 that son of a *****?
No one wants to deal with exynos anymore... its been a pain in the @$$ BUT still some managed to run it on other phones the real issue is the lack of sources and documentation from samsung, them not being sharing made the devs go "goto hell" so no futhur development for exynos chips frankly I dont know if it will be anyway near 2013 perhaps next year more will have courage or sammy will be thankful to share documentation.
Sent from my GT-I9500 using Tapatalk 4 Beta
Today.. Android kitkat is unveil..
Will be updating omnirom?
Sent from my LG-P880 using xda app-developers app
scweeny said:
Today.. Android kitkat is unveil..
Will be updating omnirom?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Just guess
https://developers.google.com/android/nexus/images
Sent from my SGH-I337M using Tapatalk 2
2Tone5 said:
https://developers.google.com/android/nexus/images
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
While the factory images are nice, until the actual source code gets released, not much is going to happen on the development front.
Source code has been released
https://android.googlesource.com/platform/art/+/kitkat-release
Omni+Slim-4.3.1Dorimanx|i9100¬Tapa2
Source and required blobs released by Google, omnirom on the nexus 5 coming up?
SHAWDAH said:
Source and required blobs released by Google, omnirom on the nexus 5 coming up?
Click to expand...
Click to collapse
Yup
All repos are in already : https://github.com/mithun46?tab=repositories
Problem right now is that with a few exceptions, no one has a Nexus 5, and we don't have blobs for any other Nexus devices.
It's a bit silly to waste time on hackjobbing old blobs on a Nexus device when you know there will be blobs within a week. So plodey is working on getting things merged with a different non-Nexus device which we know isn't going to see updated blobs for eternity, if ever, for the moment. It's probably one of the last devices you'd expect any of us to prioritize for those who know our device histories well.
Entropy512 said:
Problem right now is that with a few exceptions, no one has a Nexus 5, and we don't have blobs for any other Nexus devices.
It's a bit silly to waste time on hackjobbing old blobs on a Nexus device when you know there will be blobs within a week. So plodey is working on getting things merged with a different non-Nexus device which we know isn't going to see updated blobs for eternity, if ever, for the moment. It's probably one of the last devices you'd expect any of us to prioritize for those who know our device histories well.
Click to expand...
Click to collapse
The blobs which I've used is the newest from the latest system dump and I think that will have no problems [I may be wrong]
I'll get my nexus5 in a week. Also many people I know have it so I can get it tested in that way too
I know which device is plodey working with
Entropy512 said:
Problem right now is that with a few exceptions, no one has a Nexus 5, and we don't have blobs for any other Nexus devices.
It's a bit silly to waste time on hackjobbing old blobs on a Nexus device when you know there will be blobs within a week. So plodey is working on getting things merged with a different non-Nexus device which we know isn't going to see updated blobs for eternity, if ever, for the moment. It's probably one of the last devices you'd expect any of us to prioritize for those who know our device histories well.
Click to expand...
Click to collapse
i should have n5 in hand monday, so let me know what you'll need!
Go XplodWilD and Entropy512, we all know what and that you can haxxynos! Okay, before the rumours start, as I don't have any clue what you're about to hack and do, I just want to thank all of you what you've done so far. I highly appreciate it
Btw I really enjoy it on the good old N7000,pretty straight forward, fast and fluid.
GALAXY NOTE N7000 // OMNI ROM // JLS36I
Yes it will come as xplodwild twit
mithun46 said:
All repos are in already : https://github.com/mithun46?tab=repositories
Click to expand...
Click to collapse
Did you try to build? Seems like a lot of stuff is not yet completely merged.
How does this merging works normally? Just merge the 4.4 to the main branch? (@XpLoDWilD the merge on libhardware_legacy is not compilable, you missed parts of 24af9ec380e138f24864cd9359c6901b8b29e5ee). Or cherry-pick each commit from 4.3? And upload each cherrypick to gerrit?
Hey everyone. So, kernel source isn't out yet. That is a bit disturbing to me... So because of the sheer popularity of this device, everyone submit a request for all models of the m8 Kernel source. A forum letter would be as follows
Hello, my name is _____. I own the HTC one M8. As required by copyright law, htc is required to release the Linux kernel source code the day of release. The lack of kernel source is therefore breaking copyright laws, and I hereby request all Linux kernel sources be released for all released models of the HTC One M8. Many people desire this kernel source. These are all your paying customers too.
thank you, (name)
Now another thing to know is they will likely tell you "htc releases all legally required sources" do not take this answer. Require that your case be elevated, and help us get the development going properly.
Link:
http://www.htcdev.com/contact
EDIT:
GPE leaked sources:
http://www.androidfilehost.com/?fid=23329332407583185
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
123421342 said:
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
Click to expand...
Click to collapse
Actually the exact wording is released along side of the release of a kernel. I have talked with many Linux kernel maintainers who all agree this is equal to the same day. (Linux Kernels are my specialty, as such I've met great people along the way who worked very close with Linus)
Sent from my C525c using Tapatalk
123421342 said:
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
Click to expand...
Click to collapse
Not only that it's not release day yet, official release is somewhere in April no?
xReaper7x said:
Not only that it's not release day yet, official release is somewhere in April no?
Click to expand...
Click to collapse
Release date was Tuesday. For sprint, AT&T, Verizon, gsm unlocked and the developer edition. Google play is 2 weeks from last Tuesday. Other carriers come on at different times.
Sent from my C525c using Tapatalk
This par for the course with HTC. They have never been good about releasing kernel source in a timely fashion.
According to the GPL, kernel source must be available as soon as the accompanying software is in use by the public. The "in a timely manner" aspect provides some flexibility in delivering the source, as far as distribution. Within 24 hours is acceptable, time to upload the file and make it available on the site. It needs to be available day 1. 90-120 days later is not even close to complying.
What's even more annoying than having to wait, is that there is absolutely no reason to hold it back. They obviously have it before the device is released. All they do is annoy their LOYAL customers. It's just stupid and bad business at this point.
Sent from my HTC One using xda app-developers app
Surely it's not copyright law, but the licence under which the Linux source is released, i.e., GPL v2.
BenPope said:
Surely it's not copyright law, but the licence under which the Linux source is released, i.e., GPL v2.
Click to expand...
Click to collapse
The GPL license is a form of a copyright. This makes it part of copyright laws
Sent from my C525c using Tapatalk
thats the only thing stopping me from going back to HTC.. they are horrible at releasing kernel source.. sad cause i have seem many users and kernel devs leave HTC because of this issue..
it will come in time. we don't even have s-off yet.
Pretty sure they have 90 days to comply
~Jflteusc runnin' latest Carbon Nightly
Latest KToonsez Kernel 2.1;189;480
Pegasusq
Row
Thermald:
Mpdecision:
You don't need soff to unlock. Just a unprotected unlock partition or one that's exploitable
Also they do not. If you don't agree ask any Linux mantainter. Most even see it offensively that oems do this
Sent from my HTC M8WHL
Done.
Sent from my 831C using XDA Premium 4 mobile app
The phone hasn't even been out a week... Kernel source for the M7 has been released releatively quickly after updates.
The phone has been out for 5 days...
Sent from my HTC One using Tapatalk
That doesnt matter. Kernel source should be released within 24 hours of it being public.
HTC always releases source immediately for the Google Play Edition, which means a couple weeks. They always take forever to release source for their Sense kernels.
flar2 said:
HTC always releases source immediately for the Google Play Edition, which means a couple weeks. They always take forever to release source for their Sense kernels.
Click to expand...
Click to collapse
Google told them that they had to do that if they wanted to call it a Google play device. It may be something we can work with. Let's hope that HTC senses, no pun intended, the desire.
Sent from my HTC M8WHL
MassStash said:
Pretty sure they have 90 days to comply
Click to expand...
Click to collapse
Pretty sure that is stated NOWHERE in the GPL.
Sent from my HTC One using xda app-developers app
c5satellite2 said:
Pretty sure that is stated NOWHERE in the GPL.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh for sure, definitely not in the stated license, not sure where the hell I heard that. Then n that note, 1) really pain in ? there isn't a time frame stated in the license to high source needs to be made available for person requesting, and 2) pretty sure these companies could charge us for distrbuting source to us, so that's kool they don't at least.
~S-Off LTEvo; Back on the Always Solid Viper4G Latest;
Expletive Deleted Kernel
cpu0/1: 1.5ghz ¦ 384mhz ¦ sleep: 486mhz max
ondemand
fiops
thermald: dynamic
With tapatalk4