Related
Well to be straight on point i dont think we even have as mush as development as the previous Galaxy S1 . Just look at their android development thread and on the first page itself you can find 3 ICS roms . Two of them usable for daily driver , one is CM9 which is still buggy (So is ours ), I mean to say that we are dependent only on the CM9 team for the ICS and we dont have anyother dev to do that for us .
Your views ?
anshmiester78900 said:
Well to be straight on point i dont think we even have as mush as development as the previous Galaxy S1 . Just look at their android development thread and on the first page itself you can find 3 ICS roms . Two of them usable for daily driver , one is CM9 which is still buggy (So is ours ), I mean to say that we are dependent only on the CM9 team for the ICS and we dont have anyother dev to do that for us .
Your views ?
Click to expand...
Click to collapse
simple reasong
samsung galaxy s2 is a perfec phone with perfect firmware.
reason ppl coming here is to change the looks and play around with their perfect phone when there is nothing else to do.
the reason for no ics is because ICS is still buggy on its own so there is no point making roms untill google fixes the base.
If you desporately want more ICS development, then get developing.
If I had the brains to do, I would do. But I don't, so I can't.
Its pretty hard to develop anything without code. They work with what they have and if what they have is crappy, so yeah.
The SGS1 is similar (or almost exactly the same) as the Nexus S so since source is out for that they just took some stuff there and used it on the SGS1. Makes it much easier. We don't have a phone similar to ours that we can borrow bits and pieces from. They tried that with the Galaxy 7.0 Tab Plus but didn't work out so well.
Actually this is the first Smartphone where I don´t feel the need to change much. It´s already damn good.
zabihjan said:
simple reasong
samsung galaxy s2 is a perfec phone with perfect firmware.
reason ppl coming here is to change the looks and play around with their perfect phone when there is nothing else to do.
the reason for no ics is because ICS is still buggy on its own so there is no point making roms untill google fixes the base.
Click to expand...
Click to collapse
ICS is still buggy? I had daily drivers ics Roms on my nexus s backup in october!
Sent from my GT-I9100 using xda premium
Same here best phone ive ever had so far, only things needed to change
where optical and removed the unneeded apps.
ICS seems nice once it's stable and bugfree untill then........
Not sure I would agree.
I am running the Simplistic ICS ROM RC3 as my daily driver. Everything is super smooth from my limited experience. Granted, these are based on Sammy leaks but it beats the deadlock I saw over on the RAZR forum.
Pretty happy overall.
Very happy with my current rom, so yes I am happy overall with development
Nothing really I would change. Even with ics out, I prefer the majority of stuff touchwiz has. Simple tweaking is pretty much it.
Common guys i think ur not getting me i mean to say that we have less developers
I think it's because the original Galaxy S is older and developers have more experience with the hardware. For example it took almost a year before Cyanogengenmod was available for the Galaxy S.
I have to agree with the OP. Seeing as a galaxy s2 is such a popular phone u wuld expect more aosp roms for ics :L
sent from my iPhone 4S.
haha I bet that confused ya
wurzelsepp3 said:
I think it's because the original Galaxy S is older and developers have more experience with the hardware. For example it took almost a year before Cyanogengenmod was available for the Galaxy S.
Click to expand...
Click to collapse
Damn and they got ICS so easily ?
wurzelsepp3 said:
I think it's because the original Galaxy S is older and developers have more experience with the hardware. For example it took almost a year before Cyanogengenmod was available for the Galaxy S.
Click to expand...
Click to collapse
I tend to agree, the Original Galaxy is more established.
The trouble is, the S2 is sandwiched between the Galaxy S, and The upcoming S3. (Stuck between a rock and a hard place)
A lot of Devs and Users will no doubt be waiting to upgrade to the S3 upon launch, and maybe leave the S2 in the shadow somewhat.
Also unfortunately I would imagine a lot of Developers are staying away, considering some of the Flaming that happens on here.
We shall see. But Overall I'm more than satisfied with the Development.
Regards
Judging the level of development of a device just based on ICS is utterly stupid - did you look at all at the Gingerbread development that happened on this phone?
ICS for the original Galaxy S is a FLUKE. It's almost unheard of for an AOSP bringup to succeed on a higher version of Android than what is released for the phone due to lack of compatible binary blobs for vendor-proprietary parts.
The Galaxy S is lucky and VERY unusual - it has a high number of hardware similarities with the Nexus S, which is by its definition, a phone that has as many components open-sourced as possible. As a result, much of the Nexus S source code was adaptable to the Galaxy S as part of the CM7 bringup process.
The I9100 doesn't have this hardware commonality with a Nexus device. The RIL architecture and interfaces are completely different, the GPU is completely different, etc.
Exactly what I was going to mention. Usually porting or developing on phones is easier when someone else with similar hardware has done it before. You just borrow their work and adapt it. The Galaxy S2 doesn't share its hardware with many other phones. Hell, the whole Galaxy S2 line is super fragmented anyway! You have Tegra, omap, Exynos, different cameras, different specs alltogether.
If you just think of the international version... We're pretty much set apart and in the dark with all the proprietary code that the phone has. If you want a quick development path for your phone, you'll need a phone which has generic hardware or fully opensource code... Which is far from being this phone's case sadly.
Of course a lot of the SGS 1 roms where just cut and paste jobs .
Rom +Theme A then Rom + Theme B does not make two roms .
I am more than happy and the answer has always been you want more roms donate a phone to a dev instead of expecting them to pay for your flashing habit .
jje
It must have something to do with what can be achieved; with the exception of new releases from Google the only areas of interest really are storage space and speed. Both of which are pretty good as stock on the S2 where as development for the Desire was huge as it could be faster and, as stock, had a lack of storage space.
Even if you didn't like the look of TouchWiz you could choose a new launcher rather than rooting and flashing new ROMs.
if you want a regular updates and more development then maybe the phone for you is the galaxy nexus. pure google phone and a phone to get updates straight from the Google itself. I have not gone into the forums over there but i am pretty sure you have proper roms coming out through your ears...And i mean roms probably making that phone even better than it already is..and as being so new still the development for that can only get better...
The same for the S2. once the source code is released then you will see roms coming out and development will for sure will be on the high again and you see proper ICS roms coming left right and center...So be happy with what we have here and do more tweaking to get the max out of the phone instead of wondering if the development is slow or not..
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)
Which device seems more likely to get the best development support? Cyanogen(Steve) shared on G+ that he will keep both devices so both should see official CM very soon. The Galaxy phones are way more popular but are split up into many different forums per carrier on XDA. The One seems to only have 3 different threads (why the hell does ATT have its own when it is the same as the international?) and seems like it will be more centralized. Does this split seem like it will put overall development in one phone's favor over the other? I'm so lost with trying to decide between these two phones, I just have to ask. Thoughts? Anyone come from the One X(HTC One S dev was terrible) or S3?
Closed Source Project said:
Which device seems more likely to get the best development support? Cyanogen(Steve) shared on G+ that he will keep both devices so both should see official CM very soon. The Galaxy phones are way more popular but are split up into many different forums per carrier on XDA. The One seems to only have 3 different threads (why the hell does ATT have its own when it is the same as the international?) and seems like it will be more centralized. Does this split seem like it will put overall development in one phone's favor over the other? I'm so lost with trying to decide between these two phones, I just have to ask. Thoughts? Anyone come from the One X(HTC One S dev was terrible) or S3?
Click to expand...
Click to collapse
i am not a developer. from what i know from flashing ROMs, phones that have a single chipset (like the HTC one with snapdragon, vs Galaxy S3/S4 tha thad exynos/snapdragon variants) attract more dev support b/c ROMs can be flashed across all carrier versions.
and along with official bootloader unlocking, it appears HTC would attract more devs. i think it will also depend on who releases source code quickly.
again, this is just conjecture based on experience.
I believe I read that HTC already released the source code for the one.
Sent from my HTCONE using Tapatalk 2
If I'm not mistaken the galaxy series' are easier to develop for. Having said that I think the one will receive much love just because it's a freakin awesome phone and everybody is going to have on a like Steve.
Sent from my SPH-L710 using xda app-developers app
It doesn't matter which phone will receive more development because both phones will have a great amount of development anyway.
A Galaxy series phone is always guaranteed to have a lot of dev support and from the devs already supporting the One, with more to come, this will have great continued support aswell.
Closed Source Project said:
Which device seems more likely to get the best development support? Cyanogen(Steve) shared on G+ that he will keep both devices so both should see official CM very soon. The Galaxy phones are way more popular but are split up into many different forums per carrier on XDA. The One seems to only have 3 different threads (why the hell does ATT have its own when it is the same as the international?) and seems like it will be more centralized. Does this split seem like it will put overall development in one phone's favor over the other? I'm so lost with trying to decide between these two phones, I just have to ask. Thoughts? Anyone come from the One X(HTC One S dev was terrible) or S3?
Click to expand...
Click to collapse
Really should be in the Q&A
But should receive a generous amount of dev. CM creator Steve put out a wonderful review of the unit. I would suspect this and the S4 will be the major units of 2013 dev wise.
No support for exynos devices. Team hacksung already stated that none of them will buy Samsung phones. They are frustrated due to lack of sources. They already moved to Xperia Z.
Of course, snapdragon version will get support
Sent from my LT29i using Tapatalk 2
Also Koush said on G+ apparently the AT&T and Verizon S4 will have locked bootloaders. It took a lot of work for Adam Outler and others to get the bootloader unlocked for the Note 2 & S3.
KidCarter93 said:
It doesn't matter which phone will receive more development because both phones will have a great amount of development anyway.
Click to expand...
Click to collapse
+1
Most of so called "development" is copying other people's work, changing some icons and other images and zipping it up and making a cwm file. There are very few unique and useful mods.
Once some most glaring problems with a phone are fixed, development's job is finished. The rest is photoshopping and winzipping.
I say HTC One has already recevied almost enough development support. Volume button wake is implemented to fight the stupid power button placement problem. Most ROMs have already removed the annoying menu bar. Once custom kernels solve the rest of the problems like slow charging, what else is needed?
I am coming from s3 as i lost my device was thinking to get one this time.
I am also worried about its development.
But i am sure it will get cm rom but i dont think it will get as much aosp rom as galaxy series
And proper development means aosp rom development not some mods and theming
Sent from my HTC Desire X using xda app-developers app
nitinvaid said:
I am coming from s3 as i lost my device was thinking to get one this time.
I am also worried about its development.
But i am sure it will get cm rom but i dont think it will get as much aosp rom as galaxy series
And proper development means aosp rom development not some mods and theming
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
It doesn't matter if the One has less AOSP ROMs than the S4 because as long as they're both high end phones and both have high quality ROMs to choose from, what else matters?
The One will get plenty of AOSP ROMs anyway. Any phone can be used for this following example;
CM is usually one of the first ROMs to be released on a phone, whether that be officially or unofficially. Once CM hits the device, a lot more ROMs appear because a lot of people base their ROMs right off of CM.
Even if CM isn't one of the first ROMs, the only ROMs we'll really see before it are stock based ROMs just like we have in this forum.
Quality NOT quantity!
And proper development doesn't mean AOSP because it wouldn't exactly be hard for me to make a ROM from an existing AOSP ROM. Just add a few simple features and done. That's not proper development in the slightest.
Sent from my HTC One via XDA Premium
Hi Everyone,
I just took delivery of my new S4 Exynos (Octa) and am surprised how few custom ROMS are out there for this device.
I had an S3 and so I'm kinda used to being spoilt for choice when it came to custom ROMS.
Any ideas why there's but a few for the Octa? Is it because of the chipset?
I saw Cyanogen have said they nt going to release any ROMS for the Octa
device is relatively new, exynos always gave headaches to devs of CM.....
give it time, some people said its not worth upgrading from an s3 so... yeah less custom ROMs
Really its a bitter truth...9500 has only 2 or 3 Devs till now with no update and fixes in lias 2 or 3 weeks ..that section seems like ghost busted :
9505 too has not as many Devs as HTC One has...however it has quite good dev support
I think after so many issues in s4 Devs are skipping it [probably] for note 3
lets wait and see in the near future if the outcome is bad, its hammer time !
Gboss01 said:
Hi Everyone,
I just took delivery of my new S4 Exynos (Octa) and am surprised how few custom ROMS are out there for this device.
I had an S3 and so I'm kinda used to being spoilt for choice when it came to custom ROMS.
Any ideas why there's but a few for the Octa? Is it because of the chipset?
I saw Cyanogen have said they nt going to release any ROMS for the Octa
Click to expand...
Click to collapse
To be clear - CM rarely says that a given device will NEVER be supported. The last time we did that was with the Snapdragon S1 and CM9 - That hardware was simply too weak to support ICS and later.
However, all of the CM maintainers that have worked with past Exynos variants refuse to touch it, and anyone else with maintainer experience saw what we went through with Exynos4 and also seem to be avoiding it.
There is always the possibility that someone new will pick things up - but honestly, I consider the likelihood to be very slim.
So CM support for the "Octa" is POSSIBLE - but it is HIGHLY UNLIKELY. I think that AndreiLux was the only experienced low-level (kernels, platform bringup) developer to touch the "Octa", and he's not particularly happy with it so far.
Entropy512 said:
So CM support for the "Octa" is POSSIBLE - but it is HIGHLY UNLIKELY. I think that AndreiLux was the only experienced low-level (kernels, platform bringup) developer to touch the "Octa", and he's not particularly happy with it so far.
Click to expand...
Click to collapse
Other than the CCI fiasco I'm relatively fine with the phone. I expected and was prepared to bring MP to the device but I guess that's not happening.
As for CM, I think it's more of a problem of lack of interest than actual technical feasibility. I'd happily dwell into the device platform world if I had time but that's not happening anytime soon as I have a backlog of features in the kernel space to do and finish.
AndreiLux said:
Other than the CCI fiasco I'm relatively fine with the phone. I expected and was prepared to bring MP to the device but I guess that's not happening.
As for CM, I think it's more of a problem of lack of interest than actual technical feasibility. I'd happily dwell into the device platform world if I had time but that's not happening anytime soon as I have a backlog of features in the kernel space to do and finish.
Click to expand...
Click to collapse
Why you will not bring it anymore?
Gboss01 said:
Hi Everyone,
I just took delivery of my new S4 Exynos (Octa) and am surprised how few custom ROMS are out there for this device.
I had an S3 and so I'm kinda used to being spoilt for choice when it came to custom ROMS.
Any ideas why there's but a few for the Octa? Is it because of the chipset?
I saw Cyanogen have said they nt going to release any ROMS for the Octa
Click to expand...
Click to collapse
No CM support does not equal to no dev support just to be clear. There are top.devs here ( Indie and Wanam) and there most likely be more devs to join the party. It is however a surprise that there's only a few Roms for this device at the moment.
Sent from my HTC One using Tapatalk 2
Well because most of the S4 users have the Snapdragon variant. As for CM, as Entropy said, its most probably not going to come out for our device, even if it does, it'll be broken and unusable due to lack of source code/documentation, etc. As for the custom ROMs, we'll have more of them but the best one IMO - Android Revolution HD - is very unlikely for our device.
The Octa is such a great phone yet the support seems to be lacking a little, I mean my Huawei U8800 had more development going on than this phone.
I dont get why alot of people are saying the Octa is crap compared to the S600 when the Octa beats the S600 in every benchmark I've seen.
Is the S600 an easier design to build custom ROMS for?
I have tried Doc Barebones ROM and Wanams Lite ROM. Both work well on the Octa but I found Docs ROM to the give me the highest Antutu scores, always above 30000 with the highest being 30890. Wanam's ROM didn't yield much more than the stock ROM, around 28300, same with the Omega v4 ROM.
I'm back to on the stock firmware, with bloatware removed, for now. having tried those three ROMS I'm itching to try another but alas I cant find any :crying:
Gboss01 said:
Is the S600 an easier design to build custom ROMS for?
Click to expand...
Click to collapse
Yes as Qualcomm is much more open source than Exynos. Not open source = pain in the a** to develop.
Sent from my GT-I9505 using Tapatalk 2
chickentuna said:
Yes as Qualcomm is much more open source than Exynos. Not open source = pain in the a** to develop.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Damn!
I read some where that Samsung might release the source code for the exynos. Is this true?
And if they did would that make it any easie rto develop ROMS for the Octa?
Just simply harder to develop anything for Exynos, i think.
I'd like to remind everyone that developers spend their own time and money on development.
Basically, unless the developer has a strong interest in a device he will not feel obliged to 'hack' features such as camera, noise canceling and so on.
I miss the old days of the HD2
I hope we can get CM on the 9500 because it will open the door for AOKP and Paranoid-Android and possibly MIUI.
Good luck to the developers.
RIP on i9500 haha just joking ... @AndreiLux are u giving up on i9500 ? oh please dont
As Entropy512 said, the problem is mostly because Exynos has terrible source code support. There are a lot of precompiled modules in the source, and these are tied to the Android version that the source code is for. This means that when a new version of Android comes out, you're stuck waiting for Samsung to catch up.
What the devs (like Entropy) have been trying to do is to create open-source versions of these modules, so that they're not reliant on Samsung. This has been extremely frustrating for them, requiring a lot of work for very little gain.
What would be ideal is for Samsung to provide source code and documentation for these precompiled modules. They're promised to do this several times, but so far have only delivered some code that only works for a reference board, not for the hardware configurations that any of their phones use. Even worse, the source code that is available is based on Gingerbread, and has numerous hacks applied to allow it to work with ICS. In short, it's just broken and will not work.
Qualcomm (Snapdragon), on the other hand, provide very good developer support. They and Texas Instruments (OMAP) have a very good reputation with the devs, with lots of source code and documentation available. That's why Snapdragon and OMAP phones are among the first to be supported when new versions of AOSP/AOKP/CM come out.
The I9500 may do better in the benchmarks than the I9505, but that's one of the few advantages it has.
Sent from my GT-I9505
I am not really interested in anything else but AOSP / CM on this phone. We badly need it.. I think we need to build the force on Twitter so that we can bombard their twitter account (@SamsungExynos) and force them to release at least some sorta source for Exynos.
I already started tweeting them like hell. Yes, they do reply with kind of SAFE sided replies..
Gboss01 said:
Damn!
I read some where that Samsung might release the source code for the exynos. Is this true?
And if they did would that make it any easie rto develop ROMS for the Octa?
Click to expand...
Click to collapse
If they did it would make the world of difference and Exynos would be on a level playing field in development terms as the likes of Snapdragon. Unfortunately, Samsung have been saying that since the original Galaxy S and it still hasn't happened, and it's clear they never intended to release anything and it was nothing more than lip service in an attempt to sell more handsets by appearing developer friendly. It's broken promises like this which has made reputable developers wash their hands with the Exynos chipset and any phones that use it. Unfortunately, this leaves people with the I9500 in a bit of a predicament if they're not fond of TW as it's likely to be their only option for the foreseeable, if not full stop.
Gboss01 said:
Damn!
I read some where that Samsung might release the source code for the exynos. Is this true?
And if they did would that make it any easie rto develop ROMS for the Octa?
Click to expand...
Click to collapse
Exynos open source? Highly unlikely and yes it would be much easier building roms, devs wouldn't even need to have the device to build a working ROM.
gdonanthony said:
RIP on i9500 haha just joking ... @AndreiLux are u giving up on i9500 ? oh please dont
Click to expand...
Click to collapse
He never said that, on the contrary he might be having some big plans
Sent from my GT-I9500 using Tapatalk 4 Beta
Looking at some other forums I noticed that OmniROM is a more used in nexus 5 or nexus 4 forums.. But actually something like multi windows would be awesomely great on our n7..
I've got the feeling that the development of n7 is quite dead..
Is this just a felling of mine?
Sent from my Nexus 7 using Tapatalk 4
JeanEatsWorld said:
Looking at some other forums I noticed that OmniROM is a more used in nexus 5 or nexus 4 forums.. But actually something like multi windows would be awesomely great on our n7..
I've got the feeling that the development of n7 is quite dead..
Is this just a felling of mine?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
You will ALWAYS have more development in phone forums than tablet forums. More phones are sold than tabs, just the nature of supply/demand. You also have to have some patience. 4.4 was just released & the full source isn't even available yet. Nobody is going to continue developing 4.3, so you have to wait for 4.4 to start rolling & then stabilizing a build is priority over implementing features. That said, it is open source & you are free to build whatever suits your needs. I used to do just that, but I have a real job (just like many of the devs) as a mechanical engineer which takes priority over everything, along with my other obligations.
GSLEON3 said:
You will ALWAYS have more development in phone forums than tablet forums. More phones are sold than tabs, just the nature of supply/demand. You also have to have some patience. 4.4 was just released & the full source isn't even available yet. Nobody is going to continue developing 4.3, so you have to wait for 4.4 to start rolling & then stabilizing a build is priority over implementing features. That said, it is open source & you are free to build whatever suits your needs. I used to do just that, but I have a real job (just like many of the devs) as a mechanical engineer which takes priority over everything, along with my other obligations.
Click to expand...
Click to collapse
You are right with that, for sure..
But this is one of the reasons why I bought N7 instead of others..because I was pretty sure that I would have more support.. but honestly this is making me upset... T_T
I'm a flashcoholic.. I need to flash something for my tab as I do with my N4..
I just would like Multi-Windows and Pie honestly... I wish I was able to build my own..
..Anyway you are surely right saying that is because of the "numbers" of tabs compared to the "numbers" of smartphones..