Database Users

[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)

Difficult to develop for GS4?

Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors
Sent from my aokp_tenderloin using Tapatalk 2

take a look at i9300 sgs3 development section,
then come back here with your findings

If it's anything like the Note 2 you will loss any Samsung tweaks if you go with a non-touchwiz Rom. Even GPS and bluetooth is a little hairy on Aosp or cyanogenmod Roms. But each phone/team working on the Rom is different. I'm actually sticking with a custom touchwiz Rom because I need the reliability for a business trip this upcoming week.
And it will be extreme luck if the IR sensor works without Samsung's framework. The IR port is the one thing I've been dying for to make a come back. I would actually pay $20 for a fully programmable IR app that has the same functionality of one of those expensive Logitech models.

The development scene for Samsung phones has been huge and vibrant. Samsung is nice about keeping things unlocked and releasing source code, and while it may take time for AOSP/CM/AOKP ROM's to be fully functional and stable the S4 will have plenty of custom ROM's in its future.

GGXtreme said:
The development scene for Samsung phones has been huge and vibrant. Samsung is nice about keeping things unlocked and releasing source code, and while it may take time for AOSP/CM/AOKP ROM's to be fully functional and stable the S4 will have plenty of custom ROM's in its future.
Click to expand...
Click to collapse
I have no doubt that the S4 will get AOSP/CM/AOKP roms but the OP question was about the sensors. You got temp sensor, IR sensor, hover with finger sensor, and some of the camera tweaks. I don't think those Roms will have the sensor fully functionals. That's the issue I have right now on my Note 2. I love the cleanness of a stock Android Rom but I miss it when a note automatically pops up when the s-pen is removed. And battery life on touchwiz Roms appear to be better. These are choices we're going to have to make.

cdmoore74 said:
...I miss it when a note automatically pops up when the s-pen is removed...
Click to expand...
Click to collapse
Correct me if I'm wrong, but isn't that entirely part of the launcher and TouchWiz apps rather than the ROM?

Piaband said:
Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I assure you it will be huge and vibrant, for now....
Wait 1 year later.
S3 & Note 2 users will now experience what S2 and Note users experienced for the past year. Total nightmare and hell.

cdmoore74 said:
I have no doubt that the S4 will get AOSP/CM/AOKP roms but the OP question was about the sensors. You got temp sensor, IR sensor, hover with finger sensor, and some of the camera tweaks. I don't think those Roms will have the sensor fully functionals. That's the issue I have right now on my Note 2. I love the cleanness of a stock Android Rom but I miss it when a note automatically pops up when the s-pen is removed. And battery life on touchwiz Roms appear to be better. These are choices we're going to have to make.
Click to expand...
Click to collapse
You hit the nail on the head my friend. I am looking to run stock android jelly bean on my next device.
I had a nexus s for my first android phone and I took it for granted how amazingly easy it was to flash not only roms but radios, kernels, basically anything. And I just love stock android.
I am now on an HTC rezound. While I do like it, I sorely miss stock android and flashing away at will. Already had quite a few flashing mishaps.
If I am forced to run touchwiz to use all these new features, then I'm not going to pay attention to the features when choosing my next device.
This wouldn't even be an issue if the LG nexus was released on Verizon.
Ugh, looks like I'm still waiting.
Rezound, s-off, loving it.

Livebyte said:
I assure you it will be huge and vibrant, for now....
Wait 1 year later.
S3 & Note 2 users will now experience what S2 and Note users experienced for the past year. Total nightmare and hell.
Click to expand...
Click to collapse
Explain?
Sent from my s-off Rezound

GGXtreme said:
Correct me if I'm wrong, but isn't that entirely part of the launcher and TouchWiz apps rather than the ROM?
Click to expand...
Click to collapse
Actually it depends on the feature.. Some of the features see baked into the framework apk others have individual apps... None of them are launcher dependent.. However all of these together make a ROM.. So I don't know you are referring to??
Sent from my GT-I9300 using Tapatalk 2
---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------
Piaband said:
Explain?
Sent from my s-off Rezound
Click to expand...
Click to collapse
He means all the devs will fly in droves to the new flagship device leaving the flagship devices of last year stranded..
Sent from my GT-I9300 using Tapatalk 2

Piaband said:
Explain?
Sent from my s-off Rezound
Click to expand...
Click to collapse
Most experienced developers are leaving Samsung for manufacturers that don't treat them like **** (see the Superbrick fiasco), leaving only the "me-too" smali-hack-kangs and a very small number of experienced competent developers like Andrei.
Quality, not quantity - most of the stuff in the I9100 and I9300 forums is crap, people who took a Touchwizz base, themed it, made some build.prop hacks, and called it a whole new firmware package. They're lucky in that Touchwizz is so bad that it's easy to improve upon it.
Compare to, for example, the Xperia T where there are 5-10 or more developers all contributing as a team to something that only has two threads (One for CM10, one for CM10.1) There aren't many people working with Sony stock firmwares because, honestly, it's REALLY hard to improve upon them because they're so good to begin with. Most of the few things that can be improved are achievable with simple TiBu freezes, no smali hacking required.

I think it'll make AOSP (CM/AOKP) hard to develop but there super people! I'm sure they'll figure it out and help!
However Touchwiz ROM's could be pulled and edited! We won't lose any features/it won't be hard.

Reviewers said:
I think it'll make AOSP (CM/AOKP) hard to develop but there super people! I'm sure they'll figure it out and help!
However Touchwiz ROM's could be pulled and edited! We won't lose any features/it won't be hard.
Click to expand...
Click to collapse
Project Butter in Exynos 4210 devices (eg. Note & S2) is still broken until today and will never be solved.
A technically inferior Galaxy Nexus is superior to the Note. Take that for a change.
You have no idea how frustrated and angry are we people targeting Samsung in the Note & S2 forums.
I swore never to buy anymore Exynos devices after this fiasco.

Livebyte said:
Project Butter in Exynos 4210 devices (eg. Note & S2) is still broken until today and will never be solved.
A technically inferior Galaxy Nexus is superior to the Note. Take that for a change.
You have no idea how frustrated and angry are we people targeting Samsung in the Note & S2 forums.
I swore never to buy anymore Exynos devices after this fiasco.
Click to expand...
Click to collapse
And the S3 community, count it in. We're fed up with all those broken promises too.

Piaband said:
Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Only for developers that want to wipe Samsung off the phone. Which I don't understand since most of the new hardware features require drivers Samsung rightfully will not release. For the longest time and to this day you could not get the FM radio to work on CM without buying a $10 Spirit radio app.
I'm sure there will be plenty of developers that will develop deoxed custom ROMs and great kernels with tweaks OCing etc. . Omega already to jump in. The only custom ROM's I've ever used were that of STOCK ROM development where features could be enhanced and drivers would not be a problem. CM always seems to have something missing or not working.
Why buy a Samsung device and then wipe it clean of all the great features? Just buy a Nexus 4
That said. I don't mind running an ASOP ROM on my Nexus 7 I will be glad to get rid of when Samsung releases the 6.5" Note 3.
For many a stock base is good enough with a custom launcher. This is a very very small community. I know at least 12 people with an S 3and 6 with Notes. None of them even want their phones rooted.
Sent from my GT-N7100 using xda premium

The real question I have is.. If the UK and the US get the quad core processor, Which device would have more developers....Exynos or Snapdragon?
Sent from my SGS3 using xda premium

Phoneguy589 said:
The real question I have is.. If the UK and the US get the quad core processor, Which device would have more developers....Exynos or Snapdragon?
Sent from my SGS3 using xda premium
Click to expand...
Click to collapse
Snapdragon always gets more aosp... So i assume more serious devs that are still in board will get Qualcomm
trolol and awayyy!! Expect typos this is my phone.

Piaband said:
Do all these new sensors and proprietary software (camera features, gesture features, etc) make it more difficult to develop customs ROMs for the gs4? Or will we just get ROMs that don't use all these new features and sensors
Click to expand...
Click to collapse
I think GS4 & Note3 development will be pretty similar to GS2, Note, GS3 and Note2.
AFAIK, for example, the AOSP based ROMs don't really support the S-Pen on the Notes, but that's more app specific.
Cameras have long been, and will likely continue to be a problem. Video capture rates may be lower, features like both cameras, sound in pictures, smart scroll may not be supportable.
As always, for stock features, there will be stock based ROMs. Take your choice, features or AOSP based.
As with all the other Galaxy S class devices, there will be two main variants: International Exynos Octa & US/LTE/Qualcomm. ROMs, XDA forum sections and many issues will be different for each.
I predict that many ROM devs will continue to complain about the lack of Exynos info and source code. But they will develop, as best they can. I'd like to see Samsung open up more, Sony and Qualcomm are better at open-ness.
And there will be at least one other group for the Qualcomm variants; I'd hope the US carrier variants will all be able to run the same ROMs, but previous experience is different I guess.
tbong777 said:
For the longest time and to this day you could not get the FM radio to work on CM without buying a $10 Spirit radio app.
Click to expand...
Click to collapse
1st post of my thread has links to free versions, as well as free alphas of Spirit2, with digital audio features for Galaxy S class devices.
I hope the proposed Android FM API will see success and provide more options.

howtomen said:
Snapdragon always gets more aosp... So i assume more serious devs that are still in board will get Qualcomm
trolol and awayyy!! Expect typos this is my phone.
Click to expand...
Click to collapse
Only reason I ask is that the i9300 get newer software updates vs the 8747 or t999. I was recently dead set on getting the i9500 but now it well be based more on development. The the ir blaster won't work km cm or aosp as it doesn't work on the note 10.1...Only touch wiz. Not really a big deal to me but I was Curtis as th where most devs are from that usually get the international ones. LTE to me means is reach my data cap sooner so hsdpa+ is plenty quick got me.
Sent from my SGS3 using xda premium

Entropy512 said:
Most experienced developers are leaving Samsung for manufacturers that don't treat them like **** (see the Superbrick fiasco), leaving only the "me-too" smali-hack-kangs and a very small number of experienced competent developers like Andrei.
Quality, not quantity - most of the stuff in the I9100 and I9300 forums is crap, people who took a Touchwizz base, themed it, made some build.prop hacks, and called it a whole new firmware package. They're lucky in that Touchwizz is so bad that it's easy to improve upon it.
Compare to, for example, the Xperia T where there are 5-10 or more developers all contributing as a team to something that only has two threads (One for CM10, one for CM10.1) There aren't many people working with Sony stock firmwares because, honestly, it's REALLY hard to improve upon them because they're so good to begin with. Most of the few things that can be improved are achievable with simple TiBu freezes, no smali hacking required.
Click to expand...
Click to collapse
Yeah, I guess that's just for exynos based galaxy devices. My US S2 Variant has several 4.2.2 aosp roms. Aokp, cm10.1, pac, slim, rootbox etc. I assume the USA s4 will be similar.
Sent from my SGH-T989 using xda app-developers app

[Q] new exynos, AOKP for i9500 and new linux kernel

1) lack of source codes for the previous exynos in galaxy s3 is a well known problem preventing the ability to create good, custom and clean android roms for s3. therefore, many developers have decided ditching s3 custom roms.
im afraid there will never be any good clean android roms for S4.. or it will take a long time.
what do you think? why doesnt samsung release the source code of the exynos 5?
Will exynos 5's source code be released soon???????
2) a new linux version 3.10 has been release, supporting exynos 5 core.. when it will be used in galaxy s4???
3) how will linux 3.10 improve android? will it be better/faster?
4)Ive heard that samsung is busy developing a new SoC, Exynos 5420
when it will be released and what will it do

darixtorento said:
1) lack of source codes for the previous exynos in galaxy s3 is a well known problem preventing the ability to create good, custom and clean android roms for s3. therefore, many developers have decided ditching s3 custom roms.
im afraid there will never be any good clean android roms for S4.. or it will take a long time.
what do you think? why doesnt samsung release the source code of the exynos 5?
Will exynos 5's source code be released soon???????
2) a new linux version 3.10 has been release, supporting exynos 5 core.. when it will be used in galaxy s4???
3) how will linux 3.10 improve android? will it be better/faster?
4)Ive heard that samsung is busy developing a new SoC, Exynos 5420
when it will be released and what will it do
Click to expand...
Click to collapse
1- Exynos Code are probably never to be released though i heard about this exynos octa arndale version that may help in getting additional infos about the Chip
2 and 3-this new linux version is probably to be used with newer version of android it brings big.little optimazation so it will make the exynos SOC run efficiently however it is not know how it would improve it or using which scenario .and yes i will be faster and more power efficient
4- this SOC is more likely to be used with future devices like note 3

jj9922 said:
1- Exynos Code are probably never to be released though i heard about this exynos octa arndale version that may help in getting additional infos about the Chip
2 and 3-this new linux version is probably to be used with newer version of android it brings big.little optimazation so it will make the exynos SOC run efficiently however it is not know how it would improve it or using which scenario .and yes i will be faster and more power efficient
4- this SOC is more likely to be used with future devices like note 3
Click to expand...
Click to collapse
thanks for answering
when will exynos octa arndale version be released?

So does that mean we are not going to see AOKP on i9500 soon. I love AOKPs and am cursing myself for not buying the i9505 as it was available. Smartphone is no joy without AOKP.

darixtorento said:
thanks for answering
when will exynos octa arndale version be released?
Click to expand...
Click to collapse
this might help you http://www.cnx-software.com/2013/04...lopment-board-is-now-available-for-pre-order/

jj9922 said:
this might help you http://www.cnx-software.com/2013/04...lopment-board-is-now-available-for-pre-order/
Click to expand...
Click to collapse
this is from april 2013.. pretty old dont you think?

darixtorento said:
this is from april 2013.. pretty old dont you think?
Click to expand...
Click to collapse
yes but it should give you an idea about it

We all miss AOKP!
Hello guys, an Android / xda developers n00b here...
The Octo Core GT-I9500 was the only choice here since it's the only S4 model shipped in my country so I'm a bit frustrated too about the AOKP thing - which I learned it may well be the next big thing after CyanogenMOD itself.
I'm about to flash Arrow ROM right now which seems pretty interesting and also will give Omega ROM a try, while we can't put our dirty hands on AOKP we surely have two really nice mods to play with
As such, I'm all years about your experiences - if any - with any of these two ROMs.
Cheers

so no aokp coming soon?
even GS3 got aopk faster

Comon people please help

Comon i need answersssss

Comon what goes on there are any news?
Where is aopk for s4

what goes on

learn to search and read .. sorry to offend u ..

gdonanthony said:
learn to search and read .. sorry to offend u ..
Click to expand...
Click to collapse
i did, and found nothing

darixtorento said:
i did, and found nothing
Click to expand...
Click to collapse
If there ia nothing... there is nothing.
In my country we say
A watched pot never boils.
Sent from my GT-I9500 using Tapatalk 2

Gillion said:
If there ia nothing... there is nothing.
In my country we say
A watched pot never boils.
Sent from my GT-I9500 using Tapatalk 2
Click to expand...
Click to collapse
Or what is more or less the same thing: it will not get faster no matter how much you stand still looking at it!
(and, btw, this is just what's happening to me reloading the site every 5' min awaiting for the imminent release of Arrow ROM 4.0, lol!)

In general thread of i9500 and i9505 a thread exist s about cm development for i9500 some good info there!

[Q] Support For i9100

I like the new OmniROM, looking at the posts here, and the source code it really looks exciting but I want to know, will the Galaxy SII (i9100) get OFFICIAL support? It is not very old device, plus it is a quite famous.
Thank you,
Best regards,
Ripton.

Ripton said:
I like the new OmniROM, looking at the posts here, and the source code it really looks exciting but I want to know, will the Galaxy SII (i9100) get OFFICIAL support? It is not very old device, plus it is a quite famous.
Thank you,
Best regards,
Ripton.
Click to expand...
Click to collapse
I second the request.
Best Regards

i9100
My i9100 is going to love this, and with this names on the project Chainfire, Xplodwild and Dees_Troy even more.

+1
Sent from my GT-I9100 using xda app-developers app

I would love to have this on my i9100 as well. I'm getting tired of supernexus.

Ripton said:
I like the new OmniROM, looking at the posts here, and the source code it really looks exciting but I want to know, will the Galaxy SII (i9100) get OFFICIAL support? It is not very old device, plus it is a quite famous.
Thank you,
Best regards,
Ripton.
Click to expand...
Click to collapse
OFFICIAL is not a allowed word here for all builds are offical

I second the request to i9100

+1 on this.
It's one of the most sold android devices out there, even if its 2 years-old.
Imho the most sold (S2, S3, Notes) should get auto-support, that would mean covering like 50-60% of people alone

It will be nice, but if it is not supported, I understand. (no. of developers < devices)

+1
I would kill to have this ROM in the i9100, looks AMAZING.

S2 running omni seems possible

highdiver_2000 said:
It will be nice, but if it is not supported, I understand. (no. of developers < devices)
Click to expand...
Click to collapse
I wouldn't...
Milions of S2 sold >>>>>>>>>>> Numbers of 95% of the other devices sold.
S2, S3 and all those with an VERY BIG % of android should have automatic YES.

RusherDude said:
I wouldn't...
Milions of S2 sold >>>>>>>>>>> Numbers of 95% of the other devices sold.
S2, S3 and all those with an VERY BIG % of android should have automatic YES.
Click to expand...
Click to collapse
Huge amounts of users doesn't mean that anyone who has worked with them is getting really tired of them being a pain in the ass.
These devices being marked for CM10.1.3 stable simply because they had "lots of users" and not because they were actually stable is actually one of the contributing factors to why most of the former Exynos4 maintainer team were involved with founding Omni.

I got Omni running on I9100 and N7000.
On both these devices I had to replace the kernel with a CM kernel I built from sources to get it to boot (the kernel was too small compared to what it should be). Also I had to replace the updater script and binary since the installation halted with an error about missing file_contexts.
I'm no expert on these things but thru trial and error I finally managed to get it running.
What doesn't work:
WIFI, BT, GPS, DATA, INTERNAL NOR EXTERNAL STORAGE
The rest is ok. The camera works but you cant use it since it requires storage.
GSM calls work ok. The network is correctly detected and the data transmission type is there too but data doesn't work (might be as simple as editing apns). I briefly went thru the settings and options, all of them seem to be working ok.
I cherrypicked multiwindow and it works pretty good!
I'll try to get things to work but I'm slowly out of ideas. If only I could get some hints from @Entropy512 or @XpLoDWilD, they must know what could be the cause Maybe it's something with the kernel image on s2/note which has the recovery inside it as well?
BTW. I used modified CM device trees and edited them accordingly to match the Omni specs.

Entropy512 said:
Huge amounts of users doesn't mean that anyone who has worked with them is getting really tired of them being a pain in the ass.
These devices being marked for CM10.1.3 stable simply because they had "lots of users" and not because they were actually stable is actually one of the contributing factors to why most of the former Exynos4 maintainer team were involved with founding Omni.
Click to expand...
Click to collapse
Thanks for the input Entropy
I understand that the "Exynos 4" pair of words already remembers you (devs that suffered them) the worst, but.. think that even after that, both starting facts are still true (They ocupy an high % of the android share and most of the people with them are really happy and didn't switch to another device yet, since they're still enough for most of the stuff). With this I mean, if omni objective is to gather android %, it is a must even if its still an inferno working with this.
I understand that the "auto-stable" move on CM wasn't correct at all. and I'm not asking for such a thing here, jut support.. but it's not a lie that we can't ask you to suffer with exynos again so it will depend on ya all .

Would like to see this ROM on i9100 too

+1 for Ommi in I9100

I hope there shall be an OmniROM for i9100. Hope that does not bring too much pain to the devs, as most of the hard work for Exynos4 is already completed. I might be mistaken, but thanks to the team we already have open source cam and sound. Further, there is not so much difference with i9300/Note2 in terms of CPU/GPU which may get further official updates from samsung. IMHO it is important to keep the results of all that dev hardwork on exynos4 platform and carry them forward to Omnirom, not just loose it as CM support for this device will most probably be dropped.

+1
Sent from my GT-I9100 using xda app-developers app

New rom ftw!
Sent from my GT-I9100 using xda app-developers app

[DISCUSSION] CM for the Galaxy S7 Exynos/Qualcomm

I am currently owning the Galaxy S6 but I really want to sell it and buy the s7 just because i want to use microsdcards again and whatherproofness is also very cool for me
so something what i really care about is development for the device wich i will buy...
i am pritty sure that the Qualcomm S7 will get Cm builds maybe also official builds but i live in germany where the Qualcomm variant is not sold. so i will need to stick with the exynos version.
the galaxy s6 also has CM aviable with its exynos processor... since now all Galaxy S (exynos) devices got cm in any time:
- Galaxy S2
- Galaxy S3
- Galaxy S4 exynos
- Galaxy S5 exynos (very buggy build tho)
- Galaxy S6
what do u think about cm on Galaxy S7

http://forum.xda-developers.com/galaxy-s7/how-to/developer-discussion-custom-kernels-t3338351
No custom kernel thus far.
BTW, S2~6 are official builds?
From what I gather, Samsung has nearly zero motivation to contribute to open source and custom roms, unlike Motorola, Sony, HTC, etc. Which makes it kinda hard for devs to support their phones.
If you have an inside contact at Samsung, by all means let them know.

It has been discussed on so many topics already... CM (or any aosp type of rom for that matter) is pretty much impossible on the Exynos, even if someone gets something to boot, it will always be super broken and full of bugs. As for the Snapdragon variant.. CM should be very possible I guess but the problem is, it seems like every variant that comes with the snapdragon cpu has their bootloaders locked to hell... so... Until someone figures out a way to unlock the bootloaders... No luck there either. If your reason for buying an S7 is development and AOSP projects... I suggest you buy some other phone.

-Ric- said:
It has been discussed on so many topics already... CM (or any aosp type of rom for that matter) is pretty much impossible on the Exynos, even if someone gets something to boot, it will always be super broken and full of bugs. As for the Snapdragon variant.. CM should be very possible I guess but the problem is, it seems like every variant that comes with the snapdragon cpu has their bootloaders locked to hell... so... Until someone figures out a way to unlock the bootloaders... No luck there either. If your reason for buying an S7 is development and AOSP projects... I suggest you buy some other phone.
Click to expand...
Click to collapse
the fact ist that they have said the same for galaxy s3 exynos and galaxy s6 exynos
both have pritty much stable builds.
i am using aosp or cm roms only when the phone gets outdated and getting no update from samsung.
so this isnt that important to me

<galaxylove> said:
the fact ist that they have said the same for galaxy s3 exynos and galaxy s6 exynos
both have pritty much stable builds.
i am using aosp or cm roms only when the phone gets outdated and getting no update from samsung.
so this isnt that important to me
Click to expand...
Click to collapse
* What’s working */
Basic 2D graphics
Wi-Fi
AP hotspot
Audio
Microphone
SMS/MMS/Mobile Data(3G, LTE)
Call
Sensors
NFC
LED(WIP)
MTP
Suspend(deep-sleep)
/* What’s not working */
Camera
GPS
Hardware accelerated video/audio encoding/decoding
Proper 3D graphics
Listing network operator
Everything else.
Even what’s listed on “What’s working” has room to improve and may have some serious bugs.
With 2D graphics, there are noticeable framedrops and tearing
Click to expand...
Click to collapse
is that your idea of stable?

-Ric- said:
is that your idea of stable?
Click to expand...
Click to collapse
no but the rom is at least useable...
the galaxy s3 has very good dev support this is clear...
they said also for both devices that it is fully impossible. but actually the devs made it

<galaxylove> said:
no but the rom is at least useable...
the galaxy s3 has very good dev support this is clear...
they said also for both devices that it is fully impossible. but actually the devs made it
Click to expand...
Click to collapse
no it's not usable, sorry. even 2D graphics are broken in it. Unless Samsung has a change of heart and releases the full source for Exynos phones, forget it. And Samsung having is a change of heart is never gonna happen since almost all their customers don't care about root/custom Roms. The only hope is someone figuring out how to unlock the bootloaders on the Qualcomm variants

-Ric- said:
no it's not usable, sorry. even 2D graphics are broken in it. Unless Samsung has a change of heart and releases the full source for Exynos phones, forget it. And Samsung having is a change of heart is never gonna happen since almost all their customers don't care about root/custom Roms. The only hope is someone figuring out how to unlock the bootloaders on the Qualcomm variants
Click to expand...
Click to collapse
This is the problem every year with Samsung phones. It is not Samsung Mobile division that does not release the Exynos sources, there are other divisions of Samsung which will simply not allow the Exynos sources to be released (for newer devices)

http://www.xda-developers.com/samsung-exynos-and-aosp-explained-a-story-of-betrayal/
http://www.xda-developers.com/galaxy-s7-bootloader-lock-explained-you-might-not-get-aosp-after-all/
Best bet would be someone found a hack on Snapdragons to root the phones and then install custom ROM.
For Exynos I think we can safely say goodbyes. Anything else is wishful thinking. Sorry to say that but I think that's true. (or you can start a 100-day hunger strike in front of the Samsung HQ and see how it goes.)

I am a student from china but now I study in germany and get the SD820 version from china....

007zzz said:
I am a student from china but now I study in germany and get the SD820 version from china....
Click to expand...
Click to collapse
I would get the Mi5, its has already an rather stable CM13 out.

NisseGurra said:
I would get the Mi5, its has already an rather stable CM13 out.
Click to expand...
Click to collapse
Mi5 doesn't have microSD card and uses Type-C cables.
Not to mention that the radio firmware is probably bugged by the Chinese government.

optionalmgrr.la said:
Mi5 doesn't have microSD card and uses Type-C cables.
Not to mention that the radio firmware is probably bugged by the Chinese government.
Click to expand...
Click to collapse
It has 128 GB internal storage and Type C cables thats an plus in my book.

I have this feeling where i really just like sansumg's phones hardware and in special it's new look, but then is the fact that my S5(exynos) still stuck in 5.0 bugged as hell rom and there still no 6.0. The Qualcomm counter part have great CM support but there still nothing for the S7.
I will probably have to get either a nexus(2016) or a Huawei p9 which looks really nice too, also I'm thinking about the HTC 10 mmm.