Related
Integrating BLN in the latest firmwares requires the XXJPU source.
Please send your request for the XXJPU sources to: http://opensource.samsung.com/reception/reception_main.do?method=inquiryView
It will not take more than 2 minutes. Consider that XXJPU is 2.2.1 - a major firmware update and without the source WE WILL NOT BE ABLE TO DO FURTHER MODS, OPTIMIZATIONS AND TWEAKS!
Please guys request what is rightfully yours from Samsung but in a nice and polite way
THANK YOU!
PS:
Please take a look at how eg Linux or Mozilla run things.
Source is available at all times for any build be it alpha beta or even the smallest update.
Please don't come with stupid arguments like "ohhh but it's not released yet".
Thanks again.
Done
Sent from my GT-I9000 using XDA App
Absolutely, it's really needed also for most Voodoo developments.
Voodoo color and sound are impossible without updated sources now.
Samsung developers are aware of the dev. effort by us even if they are quiet in forums.
Before each release, sources come through a validation process and the people who do that have obviously a lot of work.
But any gentle inquiry sent to them can only demonstrate the crucial aspect of the source releases.
They must release sources, however if you want it to be efficient, be sure your request is nice
Im not a developer, but even I know that samsung releases sources only for final fw. So why wasre time? when it is on kies samsung (as they showed severeal times) will release sources very quickly.
If I'm not wrong XXJPU isnt an official firmware yet. Would be really possible to get the sources already???
Sent from my GT-I9000 using Tapatalk
We can write standard text to send. Just copy paste. Like a petition!
Sent from my GT-I9000 using XDA App
Done.
Hopefully Samsung listens to our requests.
titooo7 said:
If I'm not wrong XXJPU isnt an official firmware yet. Would be really possible to get the sources already???
Click to expand...
Click to collapse
We got JPA and JPO a few weeks before they started rolling out as official. I'm quite sure that hosting 100 more MB win't overload their servers.
As for Samsung posting the firmwares "quick enough", that's not true.
Open source is best handled in an open repository where components are updated regularly.
dupel said:
Im not a developer, but even I know that samsung releases sources only for final fw. So why wasre time? when it is on kies samsung (as they showed severeal times) will release sources very quickly.
Click to expand...
Click to collapse
Samsung has also not released the source code from JPP!!!! They have only released the sources from jpm!
friedi100 said:
Samsung has also not released the source code from JPP!!!! They have only released the sources from jpm!
Click to expand...
Click to collapse
JPU is an incompatible update, this is why new sources are required.
done hope they'll release soon...
dupel said:
Im not a developer, but even I know that samsung releases sources only for final fw. So why wasre time? when it is on kies samsung (as they showed severeal times) will release sources very quickly.
Click to expand...
Click to collapse
This wasn't the case for many Eclair Kies release. This is why it's important tho show continuously our interest for sources.
Also did the request.
Come on Samsung!
Sent from my GT-I9000 using Tapatalk
Just did it and don't forget to say Best Regards at the end !
Request sent!
The fastest they send the sources, the fastest high quality features are added, the more likely Samsung will cooperate with us in the future.
They obviously don't care _that_ much right now, but things like better sound driver, sharpness etc "for free" are a good argument for releasing sources frequently.
(Beside all the GPL obligations that is)
I for one, would be glad to see some of these fixes go into their official release for example. (sharpness!! lol)
Request sent. I hope it will help. I really want BLN, and Samsung is obliged to supply sources. strange, that they haven't done yet so.
Thanks guys, what we do here is also very important for Sammy to know that we aren't some brain-dead sheep; the more they realize the users are ignorant the more likely they will lessen their efforts to provide quality support.
This type of communication is very important as they don't have a repository where devs can register to access the latest sources.
done Let's see how long it lasts ....
Request politely and they will release them. Maybe not tomorrow but surely within a few weeks.
Samsung has released the Android 2.2 source code for its Fascinate 3G+ for Telus. Which is basically the US Vibrant, good news?
Sent from my SGH-T959 using XDA App
I think samsung knows that vibrant owners are frustrated.. so they released the source code for the great developer to create roms off of...
Software must not be ready yet for the US variants and this is the least samsung can do, the source code as a band aid until the official froyo releases for the US vibrant..
edit.. oh samsung will release the code anyway.
Im normally not the type who nags on anyone's twitter... but after reading yesterday's maddening news/rumor about samsung flawed business practices that promotes greediness.. i did on both their twitter accounts.. lol..
So, you see headlines like this:
"Samsung Releases Conquer 4G Kernel Source Code Before The Phone Even Hits Shelves"
http://www.androidpolice.com/2011/0...urce-code-before-the-phone-even-hits-shelves/
And I can't help but think to myself..."OK, so Sammy is starting to see the benefit of getting source code out for its devices, this is good", and then I sit back and reflect upon the fact that the Epic still doesn't have the source code we're looking for (amirite?).
Now, I'm not going to piss and bemoan the fact, BUT, I am going to wonder why it is so. Is there some sort of secret sauce there? Or perhaps is there something VERY embarrassing in their source code? OR, is Sammy really that schizo?
In all, I've been pleased with the steps Sammy has taken. Sure, it would be nice to have me some GB, or even better some CM7, but hey, the Epic is still a great device despite some of the quirks that need to be straightened out.
Thoughts?
Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons
musclehead84 said:
Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons
Click to expand...
Click to collapse
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?
the reason CM7 isn't fully functional for our phones is a kernel and drivers issue. Without GB source for those, we have a hacked together partially working port.
Got it.
Well, if that didn't make your head asplode, then this surely will:
http://www.homestarrunner.com/sbzone.html
It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.
MeetFace said:
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?
Click to expand...
Click to collapse
Plus driver source isnt open source so they don't have to give it to us
it ships with GB, what do you mean it's not being built yet? I think they are not releasing source for us because our phones are reaching EOL and they want us to buy new ones.
theduce102 said:
Plus driver source isnt open source so they don't have to give it to us
Click to expand...
Click to collapse
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App
CapsLockKey said:
It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.
Click to expand...
Click to collapse
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.
mkasick said:
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.
Click to expand...
Click to collapse
This makes rational sense. Would be nice if they released those driver sources this next time around. Would be a good measure to producing goodwill & brand loyalty IMO.
No phone company has ever released driver sources and nor will they. Its open kernel source not open driver source. There is some other reasons they don't release driver source but it would be nice if all phone manufacturers did but that's a perfect world
Phone companies haven't but what about component companies like Nvidia they released Nvflash
Sent from my Transformer TF101 using XDA Premium App
xopher.hunter said:
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
No. As stated 1000 times, it is 100% possible to write drivers, a kernel and etc from scratch just much more labor intensive than using source code.
Sooo, just wondering if since the conquer 4g is VERY similar to the epic since its gb source code was released would it help us at all?
I'm just asking cause my moment ran on a frankenstein froyo port that came mostly from the transform and a little bit from the intercept and it was awesome.
Sent from my SPH-D700 using XDA Premium App
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 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