Is it possible to port other sd845 roms to the OnePlus6? I just saw that the US Snapdragon Galaxy S9 Samsung Pie beta build has been released so their official build probably isn't far off.
I was wondering if it is possible to port other sd845 roms like this one to our phone?
What is required?
Kernel source from the other ROM I assume? (and same kernel version number?)
And someone who knows how to rebuild the kernel for the OnePlus6?
I don't really know how to do these things myself, I'm just wondering if anyone knows if it would be possible, cheers
Possible? Perhaps.. But so much work for nothing that developers just will drop the idea.
kage00 said:
Is it possible to port other sd845 roms to the OnePlus6? I just saw that the US Snapdragon Galaxy S9 Samsung Pie beta build has been released so their official build probably isn't far off.
I was wondering if it is possible to port other sd845 roms like this one to our phone?
What is required?
Kernel source from the other ROM I assume? (and same kernel version number?)
And someone who knows how to rebuild the kernel for the OnePlus6?
I don't really know how to do these things myself, I'm just wondering if anyone knows if it would be possible, cheers
Click to expand...
Click to collapse
It is nearly impossible. Especially for a Samsung rom, which are some of the most sophisticated and bloated roms in the industry.
Its nearly impossible because Samsung rom need lots of work you need to work on every single app to make it work because they made everything work with framework they made like iphones this is why no app ports available from Samsung they added lots of features & apps into their os so they also don't Know sometimes where the problem come from if you see Samsung devices work fast in Start then slow down in few weeks.
alimuhammadx said:
Its nearly impossible because Samsung rom need lots of work you need to work on every single app to make it work because they made everything work with framework they made like iphones this is why no app ports available from Samsung they added lots of features & apps into their os so they also don't Know sometimes where the problem come from if you see Samsung devices work fast in Start then slow down in few weeks.
Click to expand...
Click to collapse
You're talking about porting individual Samsung apps. Yes, it's a huge headache. I know because I've done it a long time ago on older android versions, but that wasn't my question.
My question is about porting the entire rom. This way you don't have to port each app to work on a new device, because the phone will think it IS the galaxy S9. This way the Samsung framework will be included in the rom port and the apps will all work (because they are dependent on the Samsung framework to run). The difficulty lies in getting the slightly different components (other than the sd845 processor) of the OnePlus 6 to work with the S9 rom
kage00 said:
You're talking about porting individual Samsung apps. Yes, it's a huge headache. I know because I've done it a long time ago on older android versions, but that wasn't my question.
My question is about porting the entire rom. This way you don't have to port each app to work on a new device, because the phone will think it IS the galaxy S9. This way the Samsung framework will be included in the rom port and the apps will all work (because they are dependent on the Samsung framework to run). The difficulty lies in getting the slightly different components (other than the sd845 processor) of the OnePlus 6 to work with the S9 rom
Click to expand...
Click to collapse
Since you already know about porting, and Samsung roms, shouldn't you already know the answer?
I don't remember ever seeing a Samsung rom ported to another device. But that goes back about 10 years, so maybe my memory is not good. In either case, porting a Samsung rom now would be much more difficult than 10 years ago because the complexity of their roms increases exponentially.
Appreciate if anyone is working on other skins rom!?
nabbed said:
Since you already know about porting, and Samsung roms, shouldn't you already know the answer?
I don't remember ever seeing a Samsung rom ported to another device. But that goes back about 10 years, so maybe my memory is not good. In either case, porting a Samsung rom now would be much more difficult than 10 years ago because the complexity of their roms increases exponentially.
Click to expand...
Click to collapse
Your right. It hasn't been done. Also it wouldn't be legal to Port Samsung's proprietary files. HTC shut it down when people started porting their stuff.
The chip might be the same but all the other hardware isn't
nabbed said:
Since you already know about porting, and Samsung roms, shouldn't you already know the answer?
I don't remember ever seeing a Samsung rom ported to another device. But that goes back about 10 years, so maybe my memory is not good. In either case, porting a Samsung rom now would be much more difficult than 10 years ago because the complexity of their roms increases exponentially.
Click to expand...
Click to collapse
I see your point, but just because something has never been done before doesn't mean it's not possible. Nothing in our world would have ever been invented if everyone had that mentality.
I was just saying that removing dependencies from individual apps wouldn't be necessary if the framework and whole rom was ported across to this device. I have very basic knowledge of android and I'm not a programmer but I was able to get the Samsung clock app to work on AOSP/any android device years ago, it just took a lot of trial and error and removing all the touchwiz dependencies etc. I remember playing around with the Samsung camera app trying to get it to work because the Cyanogenmod camera was so crap back then too but never got that to work. Yes I can only imagine how complex they would be making their apps and software these days.
I guess what I'm saying is that if I could manage to port the clock app and get it to work with little knowledge, I can't help but wonder what someone who knows a lot more about android development could do, this is basically what I was trying to say in my first post.
Gizmoe said:
Also it wouldn't be legal to Port Samsung's proprietary files
Click to expand...
Click to collapse
Yeah... you're probably right, and Samsung would absolutely hate it if we could run their software on a $500 phone just as well as their $1500 phones! :laugh:
crixley said:
The chip might be the same but all the other hardware isn't
Click to expand...
Click to collapse
This is what I'm saying in the first post, with my limited knowledge I understand that a lot of the hardware info and drivers are in the kernel? I assume it'd be a matter of Samsung releasing their kernel source for their pie build and then a oneplus 6 kernel being built with what's needed to boot a Samsung rom with oneplus 6 drivers built into the kernel? I guess I'm asking because I honestly don't know what is or would be involved, that and I'm just curious.
It's a bit of a hypothetical question I guess
kage00 said:
Is it possible to port other sd845 roms to the OnePlus6? I just saw that the US Snapdragon Galaxy S9 Samsung Pie beta build has been released so their official build probably isn't far off.
I was wondering if it is possible to port other sd845 roms like this one to our phone?
What is required?
Kernel source from the other ROM I assume? (and same kernel version number?)
And someone who knows how to rebuild the kernel for the OnePlus6?
I don't really know how to do these things myself, I'm just wondering if anyone knows if it would be possible, cheers
Click to expand...
Click to collapse
Nothing is impossible. The real question is who will go through with the work of actually doing it?
Most people see Samsung in particular not the greatest example of software so it's a daunting task with little to gain from it overall. Unless if you're paying someone a hefty amount I can't see it happening anytime soon. At most maybe a Samsung like theme is the best we can get
Buy a S9+ and enjoy with their ****ty UI
Yeah, thanks for your input and amazing contribution to the conversation there @DamiDev :good:
In my whole time using Android (2009) I've seen about one successful HTC port and probably five TouchWiz attempts that people gave up on. It's not worth the time or effort for a closed source system that isn't anything worthwhile to begin with
Fair point @crixley
It's annoying that OEMs take an open source project and turn it into a closed source rom
Related
Would it be possible to port this? Now that it is open. This might be a better OS for the Status/Chacha.
http://blog.openwebosproject.org/post/32462950628/open-webos-1-0-edition
atrix4g18 said:
Would it be possible to port this? Now that it is open. This might be a better OS for the Status/Chacha.
http://blog.openwebosproject.org/post/32462950628/open-webos-1-0-edition
Click to expand...
Click to collapse
Open WebOS is as open as is Android: the kernel and drivers must be supplied by the manufacturer or developer, and certain apps like 'phone', 'sms', 'mms'... are not part of the open distribution.
Think that Open WebOS must be ported to EXISTING WebOS devices...
tokafondo said:
Open WebOS is as open as is Android: the kernel and drivers must be supplied by the manufacturer or developer, and certain apps like 'phone', 'sms', 'mms'... are not part of the open distribution.
Think that Open WebOS must be ported to EXISTING WebOS devices...
Click to expand...
Click to collapse
Interesting, would be great on the ChaCha/Status because it is a very smooth OS and will work great with the keyboard.
I totally would enjoy to see this on the Chacha. Since WebOS ran on keyboard devices I hope that it will have better keyboard support than android.
I also noticed that someone was able to port WebOS to some other HTC Android device and used the drivers from Android. However, problem will be the drivers of course. :-/
Flexmaen said:
I totally would enjoy to see this on the Chacha. Since WebOS ran on keyboard devices I hope that it will have better keyboard support than android.
I also noticed that someone was able to port WebOS to some other HTC Android device and used the drivers from Android. However, problem will be the drivers of course. :-/
Click to expand...
Click to collapse
The idea of the keyboard is what I was thinking. It would be a very similar experience on the chacha/status. Plus it is very fast.
it would be interesting to see a port of a totally different OS to the phone.
http://www.mozilla.org/en-US/b2g/
for example.
but the amount of work it would entail would require a lot of very skilled developers, and a ton of research on the phone hardware as well as current available software.
I doubt it will ever happen - but it would be nice to see.
Honestly, at this point, I really wish that people would get together and make a CM10 port for the ChaCha/Status. I think it will improve performance and battery life even more than the current unofficial port of CM9.
kronflux said:
it would be interesting to see a port of a totally different OS to the phone.
http://www.mozilla.org/en-US/b2g/
for example.
but the amount of work it would entail would require a lot of very skilled developers, and a ton of research on the phone hardware as well as current available software.
I doubt it will ever happen - but it would be nice to see.
Honestly, at this point, I really wish that people would get together and make a CM10 port for the ChaCha/Status. I think it will improve performance and battery life even more than the current unofficial port of CM9.
Click to expand...
Click to collapse
CM10 should be out in the next couple of months. The problem is there are like 2 real good developers for the htc chacha/status and they have lives to live. So they don't constantly work on this stuff. Which sucks. this is a great phone and we need more devs
atrix4g18 said:
CM10 should be out in the next couple of months. The problem is there are like 2 real good developers for the htc chacha/status and they have lives to live. So they don't constantly work on this stuff. Which sucks. this is a great phone and we need more devs
Click to expand...
Click to collapse
^ couldn't agree more. it's a beautiful phone, and it has so much potential. I only wish HTC would realize this, and support it more - or better yet, develop another version of it, which has a little more power out of the box.
kronflux said:
^ couldn't agree more. it's a beautiful phone, and it has so much potential. I only wish HTC would realize this, and support it more - or better yet, develop another version of it, which has a little more power out of the box.
Click to expand...
Click to collapse
This phone, with a dual core 1ghz processor same ram but 1gb would be nice and maybe just a little better screen. But just a dual core 1ghz processor and this becomes the best android phone in my opinion. I also have an atrix 4g but for most things I prefer this phone.
Unfortunately HTC said that it will discontinue to make phones with hardware keyboards...
However, I think the people that work on porting things to the HTC Chacha are limited. We could try to support them with some donations. But even if someone is willing to work on the port for some small amount of money we don't have any guarantee if the result of WebOS for the Chacha will be what we expect since it will depend on the drivers.
Also when they port CM10 to the chacha I really would like to see someone improving the keyboard support especially for the call functions. I gut 2 calls at the same time today and you can't even use the green phone key to switch between the calls since it just will open a new dialer insted of checking what is going on in the moment.
Would be nice of one of the developers to comment this here.
I will look into WebOS once someone else ports it to a ARMV6 phone. As the current phone which has WebOS so far is Galaxy Nexus, even the port for the Nexus isn't that great at the moment.
As for all the dev work, I think what we have at the moment is great for a lowend phone as we have CM7, CM9 and CM10 soon. Plus I'm going to start finishing some ROMs which I started couple of months ago. Donate to Adlx as he's keeping the dev work going on in his free time when he has Family also.
kronflux said:
it would be interesting to see a port of a totally different OS to the phone.
http://www.mozilla.org/en-US/b2g/
for example.
but the amount of work it would entail would require a lot of very skilled developers, and a ton of research on the phone hardware as well as current available software.
I doubt it will ever happen - but it would be nice to see.
Honestly, at this point, I really wish that people would get together and make a CM10 port for the ChaCha/Status. I think it will improve performance and battery life even more than the current unofficial port of CM9.
Click to expand...
Click to collapse
I already work on B2G for Chacha, and it didn't work. Later we saw it will not work as b2g (at least in the current state) doesn't support armv6.
adlx.xda said:
I already work on B2G for Chacha, and it didn't work. Later we saw it will not work as b2g (at least in the current state) doesn't support armv6.
Click to expand...
Click to collapse
Thanks for the clarification.
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.
Just bought an S6 and if my past phones were any indication I will want to remove as much vendor android customization as possible.
I don't care about warranty and am happy to root/unlock/s-off/etc my phones.
How's development looking for the S6, has anyone produced a rom with the samsung stuff stripped out?
I don't need a ROM with gizmos, just the samsung stuff and preinstalled apps taken off.
They is a great topic , i was just talking to my coworkers from tmobile that im litterally gonna switch to the g3 or htc m8 because the development on here is so sad its driving crazy (yeah yeah, i know if i want a rom i should build it myself) well if i had the BRAINS that these developers have i would exploit my knowledge but because I dont have the knowledge then we can only depend on the developers...just imagine cm 12 running on a 64bit processor...jesus.... instant nerd boner... seriously... we need to use our phones full potential...if not then why the strong processsors for? Why all the specs... htc m8/moto X 2nd gen/Lg G3/nexus 5 (for that android M)
Any feedback? I feel like ppl are afriad to speak on this topic that they dont just so they dont get flamed... but someone has to stand up and bring it to attention...
Sent from my SM-G920T using Tapatalk
I agree. I would love to see some cm/aosp. I think about switching to another device that can run it every day
Yeah, I agree to. I'm waiting for CM or AOSP rom. I want imagine a pure stock on my phone...But I thing maybe it's difficult with Knox or Samsung bloadware to make different rom who can run on our phone. All we have actually are based on Samsung rom... So wait and see...
The s6 has the least amount of preinstaled apps ... and a lot of them you can remove ... why do you people even buy phones from Samsung if you need to change every little detail about it ... maybe the best advice is that you make your own phone at home ....
Sent from my SM-G920F using XDA Free mobile app
I don't see how stripping out most of the features and adding on a buggy CM software is "getting the full potential" of the phone.
A 64 bit processor vs 32 is negligible anyway, and Cm, really? That's like equipping Iron Man's suit with a ZX spectrum computer.
zdravkodubravec said:
The s6 has the least amount of preinstaled apps ... and a lot of them you can remove ... why do you people even buy phones from Samsung if you need to change every little detail about it ... maybe the best advice is that you make your own phone at home ....
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
Why do i buy phones from samsung? Umm lets see it has the latest hardware, camera, processor, screen display.... that was a really dumb question...smh... vs one plus one or a moto x 2014... i wanna run cm on a 64 bit processor.
Sent from my SM-G920T using Tapatalk
OP, what you are looking for is called Android Open Source Project or AOSP for Short. AOSP is the Google's Android Source Code Repository. It has a code base for your phone's Processor (SoC). There are several Developers who utilize this Google Source to create Custom Roms with Features that are not available in Samsung's Touchwiz rom. You can review this list
for currently available Roms on your Device. Essentially what is called "Play Store Edition" of a device, is basically the same thing as regular Device but has AOSP Rom.
Unfortunately this thread is a duplicate of Does Exynos = no custom ROMs? So please carry on the Discussion over there,
Thread closed.
Quite simply, from what I'm reading about S6, and Exynos, the main reason for lack of major AOSP ROMS (CM13 has been finally ported), is the idea that Exynos is not documented so coding for it is difficult.
Knowing now that Snapdragon 820 is a Qualcom chip, which apparently is the most common SoC used for phones, should we expect to see a lot of AOSP based ROMs?
I am very used to Vanilla Android, and I don't think I could deal with TouchWiz, I like CM Theme Engine, and RRO Layers, so the big reason for my question is based on the hope that the probability of non-TouchWiz ROMs is high.
Also, I had a moto x 2014 and I've come to fall in love with AMOLED, and would like to stick to a small form factor 5 to 5.1 inches, combined with healthy ROM community, I'm kind of hoping S7 with SD820 might be the phone for me.
Please don't say "If you like Stock don't buy a Samsung", I get it, but it looks like maybe that stigma might not hold up soon if the ROM cookers are supportive.
Thanks!
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
geoff5093 said:
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
Click to expand...
Click to collapse
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
I don't do carrier contracts so I'd most likely look/hope for a developer/pure edition of the S7.
The Edge does not really interest me, unless they figured out some cool things to do with the curved screen that are actually useful.
I'd much rather have a fingerprint reader, and front sensors like the Moto's, I love waving my hand in front of the display to have it wake up and tell me the time.
People go... you are a Jedi!?
Airtioteclint said:
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
Click to expand...
Click to collapse
I know AT&T and Verizon are different stories, good to know it works for T-Mobile though.
Most if not all Sprint phones have unlocked bootloaders too. At least last time I checked!
Yes. However you got something wrong there. The reason why Qualcomm has all the fancy AOSP based ROMs (I say fancy because most people consider non aosp roms boring) is because of this. This is where QCOM releases their soruce code for the platforms. This makes fixing easier because you actually have the code. However exynos and all the other ones don't give a crap about the small percentage of their users that actually flash roms etc. Infact, they only want money. And guess what? ROMs = Longer device lifespan. That's why they don't release it. Thankfully enough there are some geniuses here on XDA that still are able to do the job for exynos! However, QCOM has allot better optimization with CM in terms of performance than with any other chipset. I live in the EU, which means Exynos. After already owning 2 exynos devices, I'm tired of the work that has to be done for them. I was lucky enough that both of them had Exynos chipsets that already had allot of devs mainly from other devices which made building possible for me.
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Shemploo said:
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Click to expand...
Click to collapse
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
..
CTXz said:
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
Click to expand...
Click to collapse
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
knitler said:
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
Click to expand...
Click to collapse
Um... CM =/= Cyanogen Inc
CM is a completely separate group that is not affected in any way. It's like XDA and GOogle. XDA is for developing and still both work on android. I know some people in the official CM group, all of them very friendly and none of it is affected by Cyanogen Inc. You're making yourself lies that aren't true. It's like blaming the entire CyanogenMod team because one dev for a specific device didn't fix the issue yet.
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
barondebxl said:
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
Because some people don't want a nexus
CTXz said:
Because some people don't want a nexus
Click to expand...
Click to collapse
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
And cripple it with bad, forever-beta, with half the functionally misssing software.
Sure hope we get aosp!
Sent from my SM-N920T using Tapatalk
I thought it was primarily due to the 64 bit architecture that was the hold up with aosp on the s6. Buy I could be wrong. Been a while since I went looking.
barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
CTXz said:
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
Click to expand...
Click to collapse
Might want to get used to it as sooner or later it will only be nexus devices that are worked on.
Also what's the point of getting the device fore the hardware when aosp doesn't take advantage of the hardware? Aosp drivers don't compare to the stock ones.