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)
Related
While the T959 is a well built phone with great specs, I felt like it was incomplete until 2.2 ROMs came out in November. Then, when 2.3 and the Nexus S were announced, that feeling returned.. now with Cyanogenmod7 working so well, I am in love with my Vibrant once again.
Even without any further version updates (2.4, 3.0 if possible) the phone has been improved dramatically by the work of Team Whiskey, Supercurio, Eugene, and the Cyanogenmod Team.
What keeps the Vibrant apart from all the HTC and Motorola phones when it comes to Cyanogenmod - is it a driver issue? Is it because of the Hummingbird processor?
Now that CM7 is finally working well on the Vibrant, does this mean that future Cyanogenmod versions will work on the Vibrant? Have they finally "cracked the shell" so to speak?
I am curious also as to what makes CyanogenMod different to work on for our phones vs the other ones you named.
CM is actually worse for Motorola devices as they have a locked bootloader...
On the other hand, HTC is very good about releasing source for their devices when compared to Samsung, who rarely releases source code if at all (driver source). Plus, CM started on HTCs, and with every device using similar Qualcomm hardware, i can imagine it is easier to port to newer Qualcomm-equipped HTC devices. That said, it appears that HTC is beginning to implement software to prevent rooting on newer phones like the G2, so we may see more people moving towards the more open Samsung devices.
Finally, this is explained to me. Thanks!
Why do drivers need to be recompiled for each version of Android? Do they need to be recompiled for similar releases such as 2.0 and 2.1 or 2.3 and 2.4?
I'm not exactly an expert when it comes to the Linux architecture, so take the following with a grain of salt.
Anyways, I believe it has to do with the kernel, which should contain the device drivers. Now, kernels must indeed be recompiled for every android system update; this is why a 2.1 or 2.2 kernel will not work with the newer 2.3.x roms. The problem for us is that once Samsung stops releasing kernels/roms for the SGS series, devs will no longer have a base to build off of. Hopefully devs can make use of updates/drivers from the Nexus S to keep the SGS series up to date with CM.
qtilt ......... nicely explained
oka1 said:
qtilt ......... nicely explained
Click to expand...
Click to collapse
I agree!
The main difference between CM/MIUI and the rest of the roms you see here on XDA is that CM/MIUI are built directly off of a Vanilla Froyo/Gingerbread. No extra flavorings or seasonings such as TouchWiz, HTC Sense, MotoBlur, Droid UI, etc. The use of, or misuse of, causes phones to run slower and do more work (unnecessarily) while it computes extra calculations of the UI. [EDIT]When developers BASE a rom off of a leak or pre-existing firmware it does not make it Vanilla just by removing TWiz or Sense or the rest of bloatware. Vanilla is generally the most simple a firmware can be, with no added extra-pazzaz[/EDIT]
There hasn't been a solid update to MIUI for our phone in a month, but CM has nightly builds and HOPEFULLY it has "cracked the shell," so to speak. Even if Samsung STOPS upgrading our firmware (which has already happened IMO), CyanogenMod makes their own code and develops independently without the use of previous stockpiles of code...which is why it's difficult at first to come up with their own driver source (because Samsung refuses to release ALL the sources needed). Hopefully our Vibrant is covered for the next 2.4 or 3.0 (3.1) update.
Samsung needs to continue to make money. They wouldn't if they let each phone update to the newest andros os. Not just samsung, any hardware company.
Sent from my vibrant using cyanogenmod7.
boltdidit said:
Samsung needs to continue to make money. They wouldn't if they let each phone update to the newest android os. Not just Samsung, any hardware company.
Click to expand...
Click to collapse
I disagree with this because, If Samsung released the code and people updated their phones as they liked and put different operating systems, roms as they liked. customer satisfaction would skyrocket. People would be more likely to buy new phones only from Samsung because they wanted the newest available hardware, read this as faster more flexible with more options.
but alas Samsung as with most of the manufacturers suffer from penny wise and dollar stupid syndrome and they end up being fairly low on the customer satisfaction scale another words they suck
rbcamping said:
I disagree with this because, If Samsung released the code and people updated their phones as they liked and put different operating systems, roms as they liked. customer satisfaction would skyrocket. People would be more likely to buy new phones only from Samsung because they wanted the newest available hardware, read this as faster more flexible with more options.
but alas Samsung as with most of the manufacturers suffer from penny wise and dollar stupid syndrome and they end up being fairly low on the customer satisfaction scale another words they suck
Click to expand...
Click to collapse
As a hardware company customer satisfaction is one thing and making them buy more of their products is another. If your 4,5-years old phone can still upgrade to the newest OS why would you buy a new one? So there is a balance for them to keep, their want to make their customer happy with their product but not too happy so their stay with old product forever.
That's very much why samsung was hesitated about 2.3 upgrade for the galaxy line.
The future of the device has more to do with whether or not the developers stick with the device. With the SGS being an international phone there is a better chance of this happening, and samsung has started getting better with releasing their source. As mentioned earlier HTC is making devices harder to root, for example the HTC desire CDMA with 2.2 is impossible to root and the G2 was an annoyance.
Also samsung has released multiple phones that are very close to the Vibrant such as the Nexus S and the Vibrant 4g. The Nexus S will be updated for awhile and source will be released for it, so its something though not much. The Vibrant 4g will also hopefully be updated and that will hopefully be an easy port. Also 2.4 is very similar to 2.3 so that will hopefully be an easy update for the developers.
Basically as long as we have the awesome devs that we have and we dont flame everyone that the devs get tired of working with the phone then we will have a device that will be updated and beautiful.
I want a stock style gingerbread, and I hope a touchwiz themed CM7 coming out.
vvsnail said:
I want a stock style gingerbread, and I hope a touchwiz themed CM7 coming out.
Click to expand...
Click to collapse
I believe Krylon is working on Stock, as for a Twiz themed CM7 I ask why?
bearsfan85 said:
I believe Krylon is working on Stock, as for a Twiz themed CM7 I ask why?
Click to expand...
Click to collapse
Ha, this is whats to come. CM7 hasn't arrived yet and now they want it with twiz. The ridding of twiz is part of what makes it great.
Sent from my SGH-T959
joe.kerwin said:
Ha, this is whats to come. CM7 hasn't arrived yet and now they want it with twiz. The ridding of twiz is part of what makes it great.
Sent from my SGH-T959
Click to expand...
Click to collapse
+1 agree 100%
bearsfan85 said:
The future of the device has more to do with whether or not the developers stick with the device. With the SGS being an international phone there is a better chance of this happening, and samsung has started getting better with releasing their source.
...
Basically as long as we have the awesome devs that we have and we dont flame everyone that the devs get tired of working with the phone then we will have a device that will be updated and beautiful.
Click to expand...
Click to collapse
Amen. Well stated.
I hope this is a release that is worthy of development for the Fascinate I look forward to see whats next. Our devs so incredible work and i hope this will help them with future development.
This was released two days ago. The code is for international version. Can't do anything with it.
Sent from my SCH-I500 using Tapatalk
Oh my bad I thought i was looking at a new release from today perhaps i just miss read.
It was for uk galaxy s, the vibrant got it today and were stuck on 2.1 well for non rooted users
Sent from my SCH-I500 using XDA App
This really doesn't mean much of anything, just like the Froyo version didn't really help us. If Samsung's code wasn't horrible, then yeah. But it is.
(apparently even Samsung's Froyo source for our phone didn't particularly help with AOSP/CM/MIUI porting efforts... yes, Samsung's developers are that bad)
KitsuneKnight said:
(apparently even Samsung's Froyo source for our phone didn't particularly help with AOSP/CM/MIUI porting efforts... yes, Samsung's developers are that bad)
Click to expand...
Click to collapse
It didn't help because Samsung isn't required to release the source for the parts that are causing the biggest issues. They released what they had to based on the licensing, but that didn't include any of their proprietary code, which is where the problems lie.
This is the unofficial thread to find the list of developers for the Samsung Galaxy Note II.
If you are a developer and or ROM maker/cooker would like to confirm that you are going to dev on this device please send me a pm, and I will add you to the list. In past experiences these types of threads have shown to be very helpful to build dev support for a device, and also to help people decide on a device.
What, actually is the list for?
Basically its for people and devs to see all the dev support the device will have. This sometimes is the deciding factor for getting a phone. If there's huge dev support more people will come. This makes it easier for people to find information on what devs will be supporting the note 2.
To pm me and get added to the list Click Here.
Let's make this Galaxy Note II community awesome!
Confirmed Developers
1.Utacka
2.thering1975
3.DakiX
4.::indie::
5.m3dd0g
6.Crash 1976
7.g.lewarne
8.toxicthunder
9.awesomehacker
10.KashaMalaga
11.-Viperboy-
12.lennyuk
13.Dexter_nlb
14.DocRambone
15.imilka
16.f3w1n
17.kristofpetho
18.mike1986.
19.Stavr0s91i
20.wanam
21.xator91
22.Beukhof1
23.ptmr3
24.Anas M.I
25.cpu999
26.AndreiLux
27.Chainfire
28.Patrics83
29.Chenglu
30.bigbiff
Hi,
Thanks for starting this thread. I just want to ask "Do you think there be a lot of development for this phone?" Particularly for Note II, in general for future Samsung phones.
I just finished watching this video here or here and I just heard about some developers leaving Samsung altogether? Samsung locking bootloaders? Samsung getting too big for their own ego?
I currently own the Int'l N7000 and I found the development to be good for what I want. I didn't check out the i717 thread but I assume they are fair.
I'm not really experienced in rooting but I found Samsung Note to be fairly straight forward. I recently rooted an HTC Amaze 4G and the numerous steps plus the lack of info made me never to buy an HTC phone (even if I do like the HTC One X, my friend has the North American version and he said development is low there).
This is one reason why I'm holding out on the Note II until Feb 2013, maybe even Sept 2013 (in case Note 3) comes out because I want to see how the development plays out.
I know the phone just came out, but I assumed International Note development should be all hunky dory but I never know. Makes me not want to switch devices. I had an Int'l Galaxy S2 previously and development for that is great!
I hear Sony development is awesome. But then, I think I'll just go get a Nexus for ease of development (but the screen is so small!)
What do you guys think?
cincyelite22 said:
Confirmed Developers
1.Utacka
2.thering1975
3.DakiX
4.::indie::
5........
Click to expand...
Click to collapse
thanks leafsacc, I wasn't aware of this until now. I'm still not sure what's going on but I assumed there would be a way around a bootloader, as coders always find a way :highfive:
but reading the below, says it could have been verizon which was the cause of the bootloader, not samsung. so why is xdadevtv directing his video to samsung? is it because no open source was given for the s3? has it still not been released? will it be? anyone care to sum it up for some of us who aren't in the know? :>
Based on Samsung’s track record of always shipping devices with unlocked bootloaders, we can all safely deduce that Verizon is the one to blame here.
Click to expand...
Click to collapse
http://www.xda-developers.com/android/verizon-samsung-galaxy-s-iii-unlocked/
For starters cm will not support n7100 if samsung dont change their ways. atleast the current dev team in cm will not support newer samsung exynos devices. i9300/n80xx was the last. Only way to get n7100 supported is if samsung cooperate or a new dev join cm dev team.
Without cm support i cannot do my paranoidandroid from source as I do with n7000. Time will tell if some new dev join cm samsung team or samsung get their act together. Dont look good though.
Skickat från min GT-N7100 via Tapatalk 2
Utacka said:
For starters cm will not support n7100 if samsung dont change their ways. atleast the current dev team in cm will not support newer samsung exynos devices. i9300/n80xx was the last. Only way to get n7100 supported is if samsung cooperate or a new dev join cm dev team.
Without cm support i cannot do my paranoidandroid from source as I do with n7000. Time will tell if some new dev join cm samsung team or samsung get their act together. Dont look good though.
Skickat från min GT-N7100 via Tapatalk 2
Click to expand...
Click to collapse
Whoops not good news :crying: i need also sources...
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
jbounours said:
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You still need one of the dev maintaining exynos devices to buy n7100 and then maintaining it... we can hope for someone to step up but its their freetime and money. Entropy512 told me he would be buying at&t version which is nearly identical if samsung would change their behavior. All we can do for now is to sit and wait...
Skickat från min GT-N7100 via Tapatalk 2
Hi guys, my ROM is finally finished and now uploaded at 89%.
I need a tester! My Note 2 has not arrived yet
Please write via PM.
You forgot chainfire..
Sent from my HTC One X using Tapatalk 2
This is a great thread. I hope more chefs will chime in.
I am considering a Note II but it is absolutely vital that CM is developed for it, together with Paranoid Android. Especially since Key Lime Pie (CM11?) is be around the corner.
I also think it is important with AOSP/AOKP development for it.
So I hope the issue will be sorted during this month. If not, I am afraid that I have to consider a different game plan.
Buying a device without proper developer support is a no go for me.
For everyone woundering about my sources here is a statement from Entropy512:
Entropy512 said:
Not likely to happen. If CM comes to the Note 2, it will only be if a new maintainer steps up.
Most of the current Exynos maintainer team (myself, espenfjo, codeworkx) and others have all decided that our current devices will be our last non-Nexus Exynos devices. I'm not sure about xplodwild, but I have a feeling he's highly unlikely to take up another Haxxinos with the rest of us gone and given his prior experiences with it.
If Samsung changes their attitude towards developers, this might change, but their attitude lately (zero documentation, zero platform source code, a trend towards bootloader locking - Only the Verizon S3 has a locked bootloader now, but Samsung has had the infrastructure in place since the S2 and they are constantly adding more checks) has led to the current Exynos maintainer team deciding that enough is enough. I don't think any of us are going to do anything to make Samsung's Exynos devices more attractive to any particular market segment until they provide assistance (in the form of technical documentation and source code) in return. I don't know about the others, but if they offer me a free device I'll say no - I refuse to participate in a PR stunt like the I9100 donations were.
Pretty much the only way I'll go back is if I see reference platform source that is up to the same standards as CAF and omapzoom, or they actually start providing real documentation and source code for the devices I'm currently working with.
Click to expand...
Click to collapse
Skickat från min GT-N7100 via Tapatalk 2
Thanks entwicklun,
I Googled "verizon locked bootloader samsung galaxy note" and from what I understand that it was Verizon's request to lock the bootloader. Not sure what I would do if I was Samsung but my guess is, if it helps sell more phones on Verizon then lock the boot loader. Money talks, right?
But then I'm hearing news about Samsung not giving developers this and that, just like the example below.
jbounours said:
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
And I also need a phone that will have Paranoid Android (and the odd CM here and there), but it must also a 5" phablet. I guess there is nothing wrong with my current Note, but again by searching on Google there's a possibility that the "next big thing" might be the HTC Google Nexus X+. If that has an expansion card slot, that's it, I'm not getting the Note 2.
E90 Commie said:
This is a great thread. I hope more chefs will chime in.
I am considering a Note II but it is absolutely vital that CM is developed for it, together with Paranoid Android. Especially since Key Lime Pie (CM11?) is be around the corner.
I also think it is important with AOSP/AOKP development for it.
So I hope the issue will be sorted during this month. If not, I am afraid that I have to consider a different game plan.
Buying a device without proper developer support is a no go for me.
Click to expand...
Click to collapse
Thanks for all the work the dev's put in. I'm just saying, my next phone is where the developers are. Samsung doesn't own us. :laugh:
I'll be here when I get my note2 in December
For those that don't know, TW ROM, aokp and multi booting kernel (or at least 2 sesperate kernels )
Myself and utaka could probably come up with a aosp supporting kernel for the device if official CM does not materialise.
Crash Rom will be here to
Sent from my GT-N7000 using Tapatalk 2
cheers, I'm sure those browsing like me will know what's up now.
I've already ordered my note 2, but I would fully support the dev crew. even if that means selling my note 2 at a loss and buying what's being developed, pending though. I do like phablets and if the x+ doesn't have an exspansion slot then I probably wouldn't buy it.
I also hope aokp devs on the note 2. I certainly love their ROMS
leafsacc said:
Samsung getting too big for their own ego?
I currently own the Int'l N7000 and I found the development to be good for what I want. But then, I think I'll just go get a Nexus for ease of development (but the screen is so small!)
Click to expand...
Click to collapse
+ 1
g.lewarne said:
I'll be here when I get my note2 in December
For those that don't know, TW ROM, aokp and multi booting kernel (or at least 2 sesperate kernels )
Myself and utaka could probably come up with a aosp supporting kernel for the device if official CM does not materialise.
Click to expand...
Click to collapse
Are noobs like me allowed to jump in please?
Utacka sir is so kind to us all in his PA thread
Anyways, I think devving for this device would initially start with kanged TW based ROMs. With CM wary on supporting the device, it does seem a bit dark but hey, I am sure there are others to step up.
But then again, you can never be too sure.
Sent from my GT-N7000 using xda premium
---------- Post added at 08:55 AM ---------- Previous post was at 08:54 AM ----------
BTW, next nexus device is perhaps open to all OEMs.
Might be an Optimus from LG but from what I've read other manufactures are welcome to jump in and join the party.
Sent from my GT-N7000 using xda premium
I am the same, an expansion card slot is a big plus.
development support is also a big factor.
I would flash aokp right now but i'm so scared of emmc bug (which I assume will not be in the Note 2 just like it did not exist in GB ROM Notes. But who knows if "Key Lime Pie/Kandy Kane" might have a similar brick bug) on ICS kangs that I just stay far, far, away.
My ultimate fav is CassiesXtraLite so it's good to see thering1975 on the list.
entwicklun said:
I do like phablets and if the x+ doesn't have an exspansion slot then I probably wouldn't buy it.
I also hope aokp devs on the note 2. I certainly love their ROMS
Click to expand...
Click to collapse
I might bring VillainRom to the Note2, but only if/when we can get our OTA update/optional mods app up and running to a high enough standard.
Would be nice to know for wich model is going to work each developer.
- f3w1n -
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
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