Related
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the OPP ships with cm11, does this mean that it uses open source drivers that will work well with any open source ROM?
I'm not dev, but my guess is not entirely. Qualcomm is extremely protective of it's IP, which is why the Nexus 7 2013 source got pulled momentarily I think. This device run their SOC do I assume it'll use their drivers.
But as you can see there are a good number of roms for it already, so it's still a dev friendly device. They released their kernel source so it's useful for making AOSP roms and regular CM11, but certain features from CM11S is not available. CM isn't fully open source either from what I understand.
If the device was running pure AOSP with no Google services and using Texus Instruments OMAP chips, then it'll probably be more open.
But probably don't take what I say seriously.
eksasol said:
I'm not dev, but my guess is not entirely. Qualcomm is extremely protective of it's IP, which is why the Nexus 7 2013 source got pulled momentarily I think. This device run their SOC do I assume it'll use their drivers.
But as you can see there are a good number of roms for it already, so it's still a dev friendly device. They released their kernel source so it's useful for making AOSP roms and regular CM11, but certain features from CM11S is not available. CM isn't fully open source either from what I understand.
If the device was running pure AOSP with no Google services and using Texus Instruments OMAP chips, then it'll probably be more open.
But probably don't take what I say seriously.
Click to expand...
Click to collapse
Well I appreciate your honesty lol you've given me some interesting things to research. In the future I may be avoiding Qualcomm devices, I'm sick of having to decide between stability and crappy ui and features, vs the awesome of cyanogenmod or other community Roms with unstable reverse engineered drivers.
Hardware manufacturers have got to quit messing with android so much, Samsung makes great hardware but pretty crappy software, I'm tired of having to choose.
My next phone will either be an OPP or a Nexus 5 I think. On that magical day that I have cash to blow....
eksasol said:
I'm not dev, but my guess is not entirely. Qualcomm is extremely protective of it's IP, which is why the Nexus 7 2013 source got pulled momentarily I think. This device run their SOC do I assume it'll use their drivers.
But as you can see there are a good number of roms for it already, so it's still a dev friendly device. They released their kernel source so it's useful for making AOSP roms and regular CM11, but certain features from CM11S is not available. CM isn't fully open source either from what I understand.
If the device was running pure AOSP with no Google services and using Texus Instruments OMAP chips, then it'll probably be more open.
But probably don't take what I say seriously.
Click to expand...
Click to collapse
TI OMAP left the mobile market for SoC.
Well I appreciate your honesty lol you've given me some interesting things to research. In the future I may be avoiding Qualcomm devices, I'm sick of having to decide between stability and crappy ui and features, vs the awesome of cyanogenmod or other community Roms with unstable reverse engineered drivers.
Hardware manufacturers have got to quit messing with android so much, Samsung makes great hardware but pretty crappy software, I'm tired of having to choose.
My next phone will either be an OPP or a Nexus 5 I think. On that magical day that I have cash to blow....
Click to expand...
Click to collapse
You can't avoid Qualcomm, they pretty much own the market share when it comes to SoC. They're not bad people, their SoC are undoubtedly the best on the market. And there aren't many phones at all that offer other system on chips. The only others being NVIDIA Tegra but they're not really on phones anymore, Samsung Exynos is on international devices... if you buy a international Samsung Note/S5 then chances are it won't support U.S. LTE bands (unless you live outside of the U.S./NA).
At the end of the day, the factory images are there. And yes the N7 were pulled but its back and has been there for awhile.
The real difference is that aosp is built and tested on Nexus devices and CM uses aosp (google) to build there platform from.
So any other device is for lack of better words is a port from android nexus development aka android built for and test on nexus.
So in a way the one plus is just like any other non nexus device. You can't just repo sync a Google aosp repo and build for this phone. Without changes being made to make it work.
Not knocking the One it's a really nice piece of hardware.
Is there any hope for custom ROMs with Exynos chipsets? Or is it that that actually means the death of the custom ROM industry for Samsung phones?
There are some roms for the Note 4 Exynos. So don't give up the hope for the S6.
Aqua1ung said:
Is there any hope for custom ROMs with Exynos chipsets? Or is it that that actually means the death of the custom ROM industry for Samsung phones?
Click to expand...
Click to collapse
Lol don't believe of what you read on other blog or forum written by users that absolute don't know the truth.
Exynos absolutely doesn't mean the end of custom ROM.
Give a look on S3 (it's exynos) forum. Only in first page there are about 20 Roms and this for 37 pages.
20x37= 740. And this without the original development section. Is that enough for you?
The disadvantage about using Exynos instead of Snapdragon about modding is only one: AOSP ROM (google stock based). This not mean you'll not see any google pure ROM on S6; but means that they will be more unstable and with more bug due to missing source of the CPU. No other. If devs are really "powerful" they could make a better Aosp rom for a Exynos than a Snapdragon device.And for me, buy an S6 to install only Cyanogen or a ROM like that it's a suicide.
A part of this there is no other problem.
Be happy and don't worry about modding ^^
Aqua1ung said:
Is there any hope for custom ROMs with Exynos chipsets? Or is it that that actually means the death of the custom ROM industry for Samsung phones?
Click to expand...
Click to collapse
My favorite Android phone was the Note 2 and it was Exynos powered and still has a ton of roms, aosp and stock.
Sent from my A0001 using XDA Free mobile app
Yes it's dead end... If you goto Note4 original Dev section... Rayman is still trying to boot cm12....
And me on nexus 5 can run any freaking thing... Had Ubuntu running without bugs a couple of week back.... So HTC one m9 it is
As a galaxy s4 user (i9500 - Exynos powered) I can tell you that all AOSP roms are a mess. The devs need to work extra hard and there are still plenty of small (and until recently - big) bugs present.
About a few months after purchasing this device I strongly regretted it due to TW lags and inability to change to AOSP roms, and promised myself I will never buy another Exynos powered device.
Hope this answers your question.
Jhonys said:
As a galaxy s4 user (i9500 - Exynos powered) I can tell you that all AOSP roms are a mess. The devs need to work extra hard and there are still plenty of small (and until recently - big) bugs present.
About a few months after purchasing this device I strongly regretted it due to TW lags and inability to change to AOSP roms, and promised myself I will never buy another Exynos powered device.
Hope this answers your question.
Click to expand...
Click to collapse
Pretty much this.
The Exynos will mean that custom ROMS are very hard to get done right on the S6. The sheer audience base though might make the developers try, but I don't think it's going to get any better than the previous Galaxy S phones.
The only way that is going to change is if Samsung opens up their information around the Exynos or if perhaps we get a Nexus version (kind of like the Nexus S and what it did for the Galaxy S i9000 variants).
Exynos = closed source
closed source = no developer interest
S6 = locked bootloader
Exynos + Locked Bootloader = double whammy
Exynos + Locked Bootloader + small non-removable battery = Disposable device with 2 year max lifespan & low re-sale value
Bugs on custom roms?? really?! thats the excuse? custom roms, specially aosp ones are full of bugs and random reboots here and there, they are by no means perfect. I'm sure the S6 will have dedicated developers just like the exynos S3 does. No worries
sauron0101 said:
Pretty much this.
The Exynos will mean that custom ROMS are very hard to get done right on the S6. The sheer audience base though might make the developers try, but I don't think it's going to get any better than the previous Galaxy S phones.
The only way that is going to change is if Samsung opens up their information around the Exynos or if perhaps we get a Nexus version (kind of like the Nexus S and what it did for the Galaxy S i9000 variants).
Click to expand...
Click to collapse
Then why you guys buying the S6 and not the snapdragon S5 901F?
This makes no sense, CM support the S4 exynos but not the 901F snapdragon? all because of userbase?
allendj81 said:
Bugs on custom roms?? really?! thats the excuse? custom roms, specially aosp ones are full of bugs and random reboots here and there, they are by no means perfect. I'm sure the S6 will have dedicated developers just like the exynos S3 does. No worries
Click to expand...
Click to collapse
I have a snapdragon powered S4 and I have no random reboots or any bugs with an AOSP rom. So yeah, it does help to have a snapdragon vs an exynos which is still giving developers problems with AOSP roms.
Love how "custom rom" immediately = AOSP in most people's eyes.
Goldie said:
Love how "custom rom" immediately = AOSP in most people's eyes.
Click to expand...
Click to collapse
Well, it is more-or-less the holy grail for custom roms. If you get that working for a phone you can do a lot of customization done.
I want the latest android version whenever it is possible. Waiting for an OEM to release it can take a long time. Also I don't like the custom skin over android by a lot of OEM's. I hate touchwiz for example so I flashed AOSP and used another launcher.
I think if the chip is made by the phone's company, it is most likely to get a very low support. I mean, there is a load of ROMs for my Xperia P, but every single one which is not based on a stock ROM has some kind of bug (no BT working, no NFC, no FM radio, and that goes for all).
Albe95 said:
Lol don't believe of what you read on other blog or forum written by users that absolute don't know the truth.
Exynos absolutely doesn't mean the end of custom ROM.
Click to expand...
Click to collapse
It means the end (practically) of stable AOSP roms - roms based on the source code of Android released by Google.
That is a very significant drawback for many users.
Albe95 said:
Give a look on S3 (it's exynos) forum. Only in first page there are about 20 Roms and this for 37 pages.
20x37= 740. And this without the original development section. Is that enough for you?
Click to expand...
Click to collapse
These are generally modified or modded stock roms i.e. roms created by modifying the binary files that comprise the manufacturer's stock roms. At best, they are poor cousins of true AOSP custom roms due to lack of source files. Look up the FPBug and emmc brickbug fiascos to see how limited these modded roms are. One needs source-based roms to be able to effect real change.
Albe95 said:
The disadvantage about using Exynos instead of Snapdragon about modding is only one: AOSP ROM (google stock based). This not mean you'll not see any google pure ROM on S6; but means that they will be more unstable and with more bug due to missing source of the CPU. No other. If devs are really "powerful" they could make a better Aosp rom for a Exynos than a Snapdragon device.And for me, buy an S6 to install only Cyanogen or a ROM like that it's a suicide.
A part of this there is no other problem.
Be happy and don't worry about modding ^^
Click to expand...
Click to collapse
It doesn't matter how "powerful" a developer is.....no developer(s) can create a stable, bug-free AOSP rom for Exynos platforms without technical information and assistance that Samsung is intentionally witholding (and has been since the Galaxy S2/Note2 days).
If you care about AOSP roms for your device, the general advice is to avoid the Exynos platform for now.
MiyagiSan said:
...
If you care about AOSP roms for your device, the general advice is to avoid the Exynos platform for now.
Click to expand...
Click to collapse
This is exactly the main point! What I want to explain to other users is that AOSP ROMS =/ (not equals) ALL ROMS
Albe95 said:
This is exactly the main point! What I want to explain to other users is that AOSP ROMS =/ (not equals) ALL ROMS
Click to expand...
Click to collapse
Why would anyone care for anything but AOSP ROMs? A real ROM is an AOSP-based one. All the others are just frills and laces. At best.
Aqua1ung said:
Why would anyone care for anything but AOSP ROMs? A real ROM is an AOSP-based one. All the others are just frills and laces. At best.
Click to expand...
Click to collapse
Completely wrong. If a real ROM is only an Aosp then buy a Nexus. No need to but a Samsung to install only an empty ROM.
Albe95 said:
Completely wrong. If a real ROM is only an Aosp then buy a Nexus. No need to but a Samsung to install only an empty ROM.
Click to expand...
Click to collapse
Believe you me, I would buy a Nexus today. Unfortunately, Nexus 5 is yesterday's news, and the next Nexus is expected in early fall at best. Not much choice for someone who needs a phone with good hardware before summer. Otherwise, if Samsung and the carriers guarantee the newest Android in no longer than one week from publication by Google, I'd be very much open to non-AOSP-supporting handsets. That, however, ain't gonna happen.
Aqua1ung said:
Believe you me, I would buy a Nexus today. Unfortunately, Nexus 5 is yesterday's news, and the next Nexus is expected in early fall at best. Not much choice for someone who needs a phone with good hardware before summer. Otherwise, if Samsung and the carriers guarantee the newest Android in no longer than one week from publication by Google, I'd be very much open to non-AOSP-supporting handsets. That, however, ain't gonna happen.
Click to expand...
Click to collapse
And what is the point on having latest Android in one week more than google? I may understand only if you're a developer, that you need to develop on latest build everytime otherwhise there's no need on having immediately latest version of Android.
hello
i just pre order my S6 this week end
i quit my HTC one M7 and the M9 dont interest me in term of design and fonctionality
so it my first Samsung , i always have HTC phone
so i want to know if the dev comunity is active on Samsung device (custom roms , etc.... ) ????
thx in advance for reply :good:
Off course my friend just wait till its officially released and ull see the development for this beast
demmo81 said:
Off course my friend just wait till its officially released and ull see the development for this beast
Click to expand...
Click to collapse
I have a M7 currently, and I will most likely get a SGS6. Modding HTC (unlocking/rooting/custom roms & kernels) is fairly easy. How does Sammy compare to HTC? I read it's a bit more difficult for you guys. True?
I've read Sammy's with Qualcomm chips are easier to mod than the Exynos variants. True?
I've also read Samsung takes awhile to release latest kernel sources. True?
Hopefully someone can answer these questions. First Samsung TW device. My previous smartphones are in my sig.
I wouldn't really count on the development on S6 being active. You can at the very least take a look at the Galaxy S5 G900H which is the exynos variant of the S5 which barely recieve any support from developers.
Well there are ROM chefs at least but developers are close to nil.
Riyal said:
I wouldn't really count on the development on S6 being active. You can at the very least take a look at the Galaxy S5 G900H which is the exynos variant of the S5 which barely recieve any support from developers.
Well there are ROM chefs at least but developers are close to nil.
Click to expand...
Click to collapse
Difference is that the S6 will ONLY be Exynos, so everyone will have the Exynos version (more users/devs), of course. With the S5, most ppl had the Qualcomm variant correct? So more users/devs for the Qualcomm version.
In the last few years, generally speaking Samsung devices with Exynos SoCs have only had fully-functional custom ROMs based on TouchWiz, but ROMs based on AOSP or CyanogenMod have had unsolvable problems with the camera, sound driver's, etc. The bottom line is, if you buy a Samsung, make sure you are perfectly content with TouchWiz or broken ROMs.
Well I heard that samsung is also planning on releasing snapdragon based s6 sometime in the future? I'm not sure as I lost my interest in s6 after they confirmed that there's no sdcard in s6. Also if development is really a big deal for you when purchasing the S6 then I say better wait first before jumping. We don't know yet if there are indeed devs willing to take on the galaxy s6 for development. For now so far I haven't heard anyone willing to unlike on HTC and other devices devs are already swarming the forums even if the device is not yet released. So if I were you... Wait a couple of weeks and observe the development progress here in the forums. If it recieves enough to get your interest then purchase one and if you're lucky enough a price drop might happen before you get your device.
J-Hop2o6 said:
Difference is that the S6 will ONLY be Exynos, so everyone will have the Exynos version (more users/devs), of course. With the S5, most ppl had the Qualcomm variant correct? So more users/devs for the Qualcomm version.
Click to expand...
Click to collapse
Yes this is what I'm talking about... There are only ROM chefs(those who specialize in modifying the stock ROM) rather than developers(those who develop custom ROMs from source code) The problem here is that Samsung won't release the "full" source code of their exynos chipsets hence any drivers that's communicating in the SoC can't be recompiled against other ROMs.
As far as I know only 1 custom kernel has been released on the G900H S5 and that barely even got any progress at all even if it's just a plain TW kernel.
CafeKampuchia said:
In the last few years, generally speaking Samsung devices with Exynos SoCs have only had fully-functional custom ROMs based on TouchWiz, but ROMs based on AOSP or CyanogenMod have had unsolvable problems with the camera, sound driver's, etc. The bottom line is, if you buy a Samsung, make sure you are perfectly content with TouchWiz or broken ROMs.
Click to expand...
Click to collapse
Look at s3 for closest example
Sent from my SM-G900F using Tapatalk
Ave666 said:
Look at s3 for closest example
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Is the s3 a exynos only device also?
Riyal said:
Is the s3 a exynos only device also?
Click to expand...
Click to collapse
Yes, exynos 4412
CafeKampuchia said:
In the last few years, generally speaking Samsung devices with Exynos SoCs have only had fully-functional custom ROMs based on TouchWiz, but ROMs based on AOSP or CyanogenMod have had unsolvable problems with the camera, sound driver's, etc. The bottom line is, if you buy a Samsung, make sure you are perfectly content with TouchWiz or broken ROMs.
Click to expand...
Click to collapse
I mostly use roms which the devices was made for. Like the M7, I stuck with Sense roms. If I get the SGS6, I will stick with TW. The reason I stick with what the phone was made for is because of less bugs, and the camera is always better on the original sw, etc. So modded stock roms is what I usually go for. Hopefully some good stuff for the SGS6 in the near-future, especially since it will be a popular device.
Riyal said:
Well I heard that samsung is also planning on releasing snapdragon based s6 sometime in the future? I'm not sure as I lost my interest in s6 after they confirmed that there's no sdcard in s6. Also if development is really a big deal for you when purchasing the S6 then I say better wait first before jumping. We don't know yet if there are indeed devs willing to take on the galaxy s6 for development. For now so far I haven't heard anyone willing to unlike on HTC and other devices devs are already swarming the forums even if the device is not yet released. So if I were you... Wait a couple of weeks and observe the development progress here in the forums. If it recieves enough to get your interest then purchase one and if you're lucky enough a price drop might happen before you get your device.
Yes this is what I'm talking about... There are only ROM chefs(those who specialize in modifying the stock ROM) rather than developers(those who develop custom ROMs from source code) The problem here is that Samsung won't release the "full" source code of their exynos chipsets hence any drivers that's communicating in the SoC can't be recompiled against other ROMs.
As far as I know only 1 custom kernel has been released on the G900H S5 and that barely even got any progress at all even if it's just a plain TW kernel.
Click to expand...
Click to collapse
Yea, i'm patiently waiting for some big news on the 3rd party support. Modded stock rom is what I was going for, not AOSP roms. I always like using what the device was made for. In this case, TW. Same with my M7, Sense. So is it still difficult for the Chefs to work on the stock rom because of Exynos (and other reasons?). Or is it sort of painless? And that does suck about the S5 (Exynos varient?) kernel situation =(
elia222 said:
Yes, exynos 4412
Click to expand...
Click to collapse
Also with Legendary S2
Ave666 said:
Also with Legendary S2
Click to expand...
Click to collapse
Also note 2
Sent from my SM-N910C using XDA mobile app
J-Hop2o6 said:
I mostly use roms which the devices was made for. Like the M7, I stuck with Sense roms. If I get the SGS6, I will stick with TW. The reason I stick with what the phone was made for is because of less bugs, and the camera is always better on the original sw, etc. So modded stock roms is what I usually go for. Hopefully some good stuff for the SGS6 in the near-future, especially since it will be a popular device.
Yea, i'm patiently waiting for some big news on the 3rd party support. Modded stock rom is what I was going for, not AOSP roms. I always like using what the device was made for. In this case, TW. Same with my M7, Sense. So is it still difficult for the Chefs to work on the stock rom because of Exynos (and other reasons?). Or is it sort of painless? And that does suck about the S5 (Exynos varient?) kernel situation =(
Click to expand...
Click to collapse
If it's just modded stock ROM you're after then you shouldn't have any problems then...
I have to admit I'm a little jealous going over to the m9 forum and seeing it full of roms already
I highly doubt the bootloader will be unlockable on the S6, greatly limiting options. No one has figured out how to unlock the S5 yet.
Unless they release a developer edition on the S6, I would prepare to have root, and possibly SafeStrap, at best.
cambunch said:
I highly doubt the bootloader will be unlockable on the S6, greatly limiting options. No one has figured out how to unlock the S5 yet.
Unless they release a developer edition on the S6, I would prepare to have root, and possibly SafeStrap, at best.
Click to expand...
Click to collapse
Tmobile version and international have unlockable bootloaders. This phone is the reason why I switched to tmobile from at&t.
NJGSII said:
Tmobile version and international have unlockable bootloaders. This phone is the reason why I switched to tmobile from at&t.
Click to expand...
Click to collapse
Oh, I wasn't aware of that. I'm on Verizon's user-unfriendly network.
NJGSII said:
Tmobile version and international have unlockable bootloaders. This phone is the reason why I switched to tmobile from at&t.
Click to expand...
Click to collapse
Sprint on the S5 is unlocked as well. The locked bootloader is usually the carrier being difficult, Verizon/AT&T.
My bet is 3-4 months for a patchwork AOSP.
cambunch said:
Oh, I wasn't aware of that. I'm on Verizon's user-unfriendly network.
Click to expand...
Click to collapse
Yeah you have those versions you'll mostly sol when it comes to development.
It's been a month plus and there isn't any signs of cyanogenmod development going on? what the big deal? No sources? or are there sources and devs can't figure out the complications? like it happened with the exynos 4 platform. I had a Galaxy S3 and there was reasonable support from the devs. Looks like the devs are just frustrated with the Exynos source.
Siddheshpatil said:
It's been a month plus and there isn't any signs of cyanogenmod development going on? what the big deal? No sources? or are there sources and devs can't figure out the complications? like it happened with the exynos 4 platform. I had a Galaxy S3 and there was reasonable support from the devs. Looks like the devs are just frustrated with the Exynos source.
Click to expand...
Click to collapse
I'm waiting for this myself.. hope they release soon because in all phones I had CM was running.
Didn't even care. I have sd801 on my klte return to stock rom after join cm bugwagon since it out till tw lp comes out. My n9505, and previous phone also got the same fate. Yeah, yesteryear is the last cm I used. My 920f is the first phone that I didn't even root. This is my opinion. Ignore it if hurt you. ?
Sent from my SM-G900F
I haven't been paying attention for a while, but last I knew, exynos sources are closed, as they are proprietary to Samsung. This is why there was a bunch of discussion prior to release of the device that CM would likely be very late to the party, if it shows up at all, because there would be a lot of reverse engineering required. This was also expected to make CM run comparatively poorly vs. Stock based ROMs.
Not sure if anything has changed in this regard in the last 6 weeks..
Ave666 said:
Didn't even care. I have sd801 on my klte return to stock rom after join cm bugwagon since it out till tw lp comes out. My n9505, and previous phone also got the same fate. Yeah, yesteryear is the last cm I used. My 920f is the first phone that I didn't even root. This is my opinion. Ignore it if hurt you. ?
Sent from my SM-G900F
Click to expand...
Click to collapse
Exynos is a very "proprietory" platform, the sources are most likely not made available and if they are , its not maintained like Qualcomm does. My point being, sooner or later by december this year samsung will out hints for the next flagship, and thus our updates will be killed. My s3 never got a taste of kitkat or lollipop officially. The sooner the source is available, the better it is. Devs can start working on it.
dandrumheller said:
I haven't been paying attention for a while, but last I knew, exynos sources are closed, as they are proprietary to Samsung. This is why there was a bunch of discussion prior to release of the device that CM would likely be very late to the party, if it shows up at all, because there would be a lot of reverse engineering required. This was also expected to make CM run comparatively poorly vs. Stock based ROMs.
Not sure if anything has changed in this regard in the last 6 weeks..
Click to expand...
Click to collapse
Even if it is proprietary they do release source. They did release code for Exynos 5. ( galaxy alpha is getting some cm treatment). The s3 had so many roms, yes the reverse engineering Codeworkx, Andrew and gokhanmoral had to do was messed up but amazing.
Popular question:
http://forum.xda-developers.com/galaxy-s6/help/curious-rom-development-t3108196
http://forum.xda-developers.com/galaxy-s6/help/question-exynos-rom-development-t3093581
http://forum.xda-developers.com/galaxy-s6/help/dev-s6-t3075461
BTW, per the sticky in the General section, questions should be posted there.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G920 we do have the source
Siddheshpatil said:
Even if it is proprietary they do release source. They did release code for Exynos 5. ( galaxy alpha is getting some cm treatment). The s3 had so many roms, yes the reverse engineering Codeworkx, Andrew and gokhanmoral had to do was messed up but amazing.
Click to expand...
Click to collapse
Thanks for this info. I've been very much out of the Samsung scene for a couple years - last Sammy device I had was an SGS2. Good to know there is hope for decent CM support. It's cool to see some of the same awesome devs in this community that i remember from the S2.
dandrumheller said:
Thanks for this info. I've been very much out of the Samsung scene for a couple years - last Sammy device I had was an SGS2. Good to know there is hope for decent CM support. It's cool to see some of the same awesome devs in this community that i remember from the S2.
Click to expand...
Click to collapse
The kind of effort andrew and codeworkx put to fix the emmc bug in s2 is amazing.. Hope something like that doesn't show up on the s6..
Hello
For over one year we have the S6 . We still expect that developers lay us an AOSP ROM. CyanogenMod but we dodge ! And AOKP ? It's over?
Have you any news? Thank you in advance!
I think I'll leave Galaxy for Nexus !
Why bother for a cm full of bugs..just use a tw rom debloated and with a custom launcher.
S6 wont get any stable cm even in a few years. So just move on
just change title mate, it's against the rules do something like this.
no opensource = no cyano. it's like trying to build a rom without codes.
slawl said:
Hello
For over one year we have the S6 . We still expect that developers lay us an AOSP ROM. CyanogenMod but we dodge ! And AOKP ? It's over?
Have you any news? Thank you in advance!
I think I'll leave Galaxy for Nexus !
Click to expand...
Click to collapse
Any device utilizing a Exyenos CPU is always a no-go for CM and never-ever good for any bug-free modding. Always & forever. I believe any rom Dev would tell you this.
Samsung's hardware imo is superior to Nexus, say what you will, but Samsung knows how to produce a quality handset. Too bad about the mod-ability! But hey, as you pointed out, there's always Nexus
The exynos chipset is always difficult to get a cyanogen build for, mainly cos Samsung never release sources which makes development very hard.
Sent from my SM-G920F using XDA-Developers mobile app
thundastruck said:
Any device utilizing a Exyenos CPU is always a no-go for CM and never-ever good for any bug-free modding. Always & forever. I believe any rom Dev would tell you this.
Samsung's hardware imo is superior to Nexus, say what you will, but Samsung knows how to produce a quality handset. Too bad about the mod-ability! But hey, as you pointed out, there's always Nexus
Click to expand...
Click to collapse
Except for the Nexus 10 which has an Exynos aswell.
Officially it has 5.1.1 but unofficial cm13, maybe Android N in the future.
XxM4tzexX said:
Except for the Nexus 10 which has an Exynos aswell.
Officially it has 5.1.1 but unofficial cm13, maybe Android N in the future.
Click to expand...
Click to collapse
I never argued Exyenos can't/won't run/didn't have decent builds of CM; simply said it's a no-go meaning the end-user experience is inferior to devices that run it well e.g. devices with Qualcomm's CPU's.
Devices with Qualcomm/Snapdragon CPU's are usually the ones to go for. Look at the thread and compare rom's/cm of i9500 vs i9505 - BIG difference! :highfive: