Related
http://www.engadget.com/2013/06/28/android-4-3-spotted-on-samsung-galaxy-s-4-available-now/
http://www.sammobile.com/2013/06/28...05-ported-from-google-play-edition-gt-i9505g/
It's been ported to a Snapdragon processor so I figure that opens at least some opportunity for a port to the U.S S3. Just wondering if it was possible.
Cool will see
My guess would be no, but who knows. I know things like hardware files, libs, kernel, etc. Would have to be worked on because that is a quad core processor. Our US S3's are only dual core.
It would be easier to port to a US S4, since the hardware is the same.
NightxFall said:
http://www.engadget.com/2013/06/28/android-4-3-spotted-on-samsung-galaxy-s-4-available-now/
http://www.sammobile.com/2013/06/28...05-ported-from-google-play-edition-gt-i9505g/
It's been ported to a Snapdragon processor so I figure that opens at least some opportunity for a port to the U.S S3. Just wondering if it was possible.
Click to expand...
Click to collapse
If you have read both articles it is meant for the s4 so no it won't be on our phones. It takes way more time and skills to port a quad core optimized 4.3 to a dual core device for that the devs should get paid for the time spent. It makes sense for the devs to spend what little free time they have on a 4.1.2 Touchwiz and 4.2.2 stock Android made especially for our device.
Why wait for a port of 4.3 when the actual source comes out it will be better. Not a big rush to get 4.3 not much a different
Sent from my SCH-I535 using Tapatalk 4 Beta
Off topic but can anyone get the camera from this working on d2vzw without crashing on normal pictures?
Sent from my SCH-I535 using Tapatalk 4 Beta
Can't see anyone wasting time crow barring this into our phone. I see nothing that makes me want it. Seems like it should be 4.2.3 not 4.3.
Sent from my SCH-I535 using xda premium
soapinmouth said:
Off topic but can anyone get the camera from this working on d2vzw without crashing on normal pictures?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
My phone restarts when I take a picture with the front camera.
rmg88888888 said:
My phone restarts when I take a picture with the front camera.
Click to expand...
Click to collapse
try a different Kernel. That issue resolved itself by doing that.
I used http://forum.xda-developers.com/showthread.php?t=1853816
Peace
wwonka69 said:
try a different Kernel. That issue resolved itself by doing that.
I used http://forum.xda-developers.com/showthread.php?t=1853816
Peace
Click to expand...
Click to collapse
I tried that and it still crashed
To get back on topic of this thread...
Will a 4.3 firmware ever be ported to the galaxy s3? Ive researched on this topic for about a half hour now and have only came acoss the CM build that has 4.3 for the dual core s3....
I apologize if this has been answered elsewhere in a different thread
I don't know what u guys are waiting for, I guess u guys really love TW but the Aosp 4.3 Roms that are available are amazing. I'm on Eclipse now and its easily a DD. Not 1 issue to report. Try it and I bet u won't care when 4.3 officially drops.
RealMuphukkinG said:
To get back on topic of this thread...
Will a 4.3 firmware ever be ported to the galaxy s3? Ive researched on this topic for about a half hour now and have only came acoss the CM build that has 4.3 for the dual core s3....
I apologize if this has been answered elsewhere in a different thread
Click to expand...
Click to collapse
No as no one wants to crow bar firmware meant for a higher end version of the phone.
Samsung is pushing wearable devices (e.g. its Smartwatch) which uses Bluetooth's new low-powered features in Android 4.3. Because the Smartwatch requires being connected to one's phone for optimal use, can we assume that Samsung will want to release a 4.3 version of Touchwiz for the Galaxy S3?
Comp625 said:
Samsung is pushing wearable devices (e.g. its Smartwatch) which uses Bluetooth's new low-powered features in Android 4.3. Because the Smartwatch requires being connected to one's phone for optimal use, can we assume that Samsung will want to release a 4.3 version of Touchwiz for the Galaxy S3?
Click to expand...
Click to collapse
Yes you can assume that but you won't find out until next month.
TokedUp said:
I don't know what u guys are waiting for, I guess u guys really love TW but the Aosp 4.3 Roms that are available are amazing. I'm on Eclipse now and its easily a DD. Not 1 issue to report. Try it and I bet u won't care when 4.3 officially drops.
Click to expand...
Click to collapse
Personally, I have yet to find a 4.3 ROM/Kernel combination where I can get all of the features I want.
1. Photosphere camera that doesn't FC. Either FFC or FFVC always locks me up. I have a 4 year old daughter and I can't be messing around with reboots if I need to cath her doing something silly.
2. Group SMS. (PAC ROM has this, but I haven't seen any others.) I am not interested in GoSMS or Handsent.
TW gives me the Samsung Camera, and I can install the Photosphere camera and use with no issues.
TW gives me reliable Group SMS.
If you know of a 4.3 ROM/Kernel combination that will allow me to use ALL features of the Photophere enabled camera, please advise me.
Hi guys Happy 4th of July!
Question is: I am liking the Galaxy S4 a lot and I don't have an upgrade available until Oct/2014. Is there any ROM for the S3 that is similar to the Galaxy S4? or does anyone knows of any specials anywhere where I can upgrade now instead of waiting so long?
Best,
M
Remember you can only get so close to the s4 software, as the hardware is entirely different, the software is usually based on the hArdware.but there is the s4 voice,s4 launcher, there's a couple of roms similar to the s4 can't think of any rite now but it's very easily found in the forum.
clean Rom/xda powerd by zero-lemon & tweaked out Guided by the power of Zeus kernel!!
Hulk0069 said:
Remember you can only get so close to the s4 software, as the hardware is entirely different, the software is usually based on the hArdware.but there is the s4 voice,s4 launcher, there's a couple of roms similar to the s4 can't think of any rite now but it's very easily found in the forum.
clean Rom/xda powerd by zero-lemon & tweaked out Guided by the power of Zeus kernel!!
Click to expand...
Click to collapse
Thanks
I think the major issue is the S4 is 4.2 based and our devices are still on 4.1. I remember when I was on my Incredible we got sense 3 and 3.5 ROMs once our gingerbread leak came out, so I'm guessing we'd need a 4.2 based touchwiz kernel for our device before we could get the S4's 4.2 based ROM ported to our device.
Even if we get 4.2 (it would be about 8-9 months from now) there's no guarantee it would work out that way. Many of our devs have already moved on to the S4 or other devices so they might not be interested in porting that for us. It may not even be possible - consistencies don't always apply in the technology world, even if we have a 4.2 kernel there might be some other reason why a port isn't possible.
Sent from my SCH-I535 using Tapatalk 4 Beta
Div033 said:
I think the major issue is the S4 is 4.2 based and our devices are still on 4.1. I remember when I was on my Incredible we got sense 3 and 3.5 ROMs once our gingerbread leak came out, so I'm guessing we'd need a 4.2 based touchwiz kernel for our device before we could get the S4's 4.2 based ROM ported to our device.
Even if we get 4.2 (it would be about 8-9 months from now) there's no guarantee it would work out that way. Many of our devs have already moved on to the S4 or other devices so they might not be interested in porting that for us. It may not even be possible - consistencies don't always apply in the technology world, even if we have a 4.2 kernel there might be some other reason why a port isn't possible.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
So what ROM would be the most similar to the one on the S4? I am running CleanRom 6.2 and I like it but is there any other option?
Div033 said:
I think the major issue is the S4 is 4.2 based and our devices are still on 4.1. I remember when I was on my Incredible we got sense 3 and 3.5 ROMs once our gingerbread leak came out, so I'm guessing we'd need a 4.2 based touchwiz kernel for our device before we could get the S4's 4.2 based ROM ported to our device.
Even if we get 4.2 (it would be about 8-9 months from now) there's no guarantee it would work out that way. Many of our devs have already moved on to the S4 or other devices so they might not be interested in porting that for us. It may not even be possible - consistencies don't always apply in the technology world, even if we have a 4.2 kernel there might be some other reason why a port isn't possible.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It is not as simple as having 4.2 kernel plus you have to better your explanation as we have Google AOSP 4.2 just not touchwiz 4.2. It is more to do with the hardware as it is easier to port from phones with similar hardware then it is to port from a phone with different specs. The best alternative is to port the apps and make an app like windows 8 launcher and Xperia Z launcher. So there isn't a "might be " there is another reason and that is hardware inconsistencies.
docmarioce said:
So what ROM would be the most similar to the one on the S4? I am running CleanRom 6.2 and I like it but is there any other option?
Click to expand...
Click to collapse
Your best bet is to use a stock-ish MF1 based rom (cleanrom isn't up to date) and find + install a S4 apps package compatible with the S3. The S4 launcher and clock works fairly well on our phones. I don't think there are any roms that aim to mimic the S4 experience exclusively. They all have different theming elements with S4 apps here and there.
jmxc23 said:
It is not as simple as having 4.2 kernel plus you have to better your explanation as we have Google AOSP 4.2 just not touchwiz 4.2. It is more to do with the hardware as it is easier to port from phones with similar hardware then it is to port from a phone with different specs. The best alternative is to port the apps and make an app like windows 8 launcher and Xperia Z launcher. So there isn't a "might be " there is another reason and that is hardware inconsistencies.
Click to expand...
Click to collapse
Sure, no problem.
The reason we're able to have a working 4.2 kernel for AOSP is because we're not reliant on Samsung's kernel source for that side of development. AOSP is completely open source as opposed to touchwiz which has proprietary framework that's closed source.
You mention hardware differences. I know things have changed drastically since GB, so perhaps the argument I'm about to make is invalid. On the Incredible we got roms from the Runnymede which had 100% completely different hardware. It had a chipset which was many generations ahead yet devs still managed to get Sense 3.5 roms running on a device which was not intended to run anything beyond Sense 1.0. It wasn't possible til we had a GB leak made for our phone (still sense 1.0). This is due to proprietary sense framework built in at the kernel level which the devs relied on for porting - they needed the updated 2.3 version of the sense bits. I know touchwiz isn't sense, so I could be making a bad comparison here, but saying "the hardware is too different" isn't a valid reason for porting to not be possible. It could be a very similar setup. I'm not familiar enough with touchwiz to be able to make that distinction though.
These Sense 3.5 roms were marred with several issues which ultimately made them impractical to use as a daily driver. This was mainly due to how outdated the incredible was and that it simply didn't have the resources to run the software adequately. They did get it working really well considering the limitations. It's also interesting to note that the development of the incredible still continues to this day with unofficial CM 10.1 roms. It's pretty amazing what these devs are actually capable of. It's just about getting the right dev interested enough to invest the time doing it.
Div033 said:
Your best bet is to use a stock-ish MF1 based rom (cleanrom isn't up to date) and find + install a S4 apps package compatible with the S3. The S4 launcher and clock works fairly well on our phones. I don't think there are any roms that aim to mimic the S4 experience exclusively. They all have different theming elements with S4 apps here and there.
Sure, no problem.
The reason we're able to have a working 4.2 kernel for AOSP is because we're not reliant on Samsung's kernel source for that side of development. AOSP is completely open source as opposed to touchwiz which has proprietary framework that's closed source.
You mention hardware differences. I know things have changed drastically since GB, so perhaps the argument I'm about to make is invalid. On the Incredible we got roms from the Runnymede which had 100% completely different hardware. It had a chipset which was many generations ahead yet devs still managed to get Sense 3.5 roms running on a device which was not intended to run anything beyond Sense 1.0. It wasn't possible til we had a GB leak made for our phone (still sense 1.0). This is due to proprietary sense framework built in at the kernel level which the devs relied on for porting - they needed the updated 2.3 version of the sense bits. I know touchwiz isn't sense, so I could be making a bad comparison here, but saying "the hardware is too different" isn't a valid reason for porting to not be possible. It could be a very similar setup. I'm not familiar enough with touchwiz to be able to make that distinction though.
These Sense 3.5 roms were marred with several issues which ultimately made them impractical to use as a daily driver. This was mainly due to how outdated the incredible was and that it simply didn't have the resources to run the software adequately. They did get it working really well considering the limitations. It's also interesting to note that the development of the incredible still continues to this day with unofficial CM 10.1 roms. It's pretty amazing what these devs are actually capable of. It's just about getting the right dev interested enough to invest the time doing it.
Click to expand...
Click to collapse
True the sense 3 and 3.5 wasn't really good. We do have a Note 2,MIUI, and Sense 5 port for our devices and will likely to get ubuntu touch as soon as it is stable. Problem is that most of the developers don't have that much free time to attempt an international S3 or an US S4 port so they do what they can with the time they have.
jmxc23 said:
True the sense 3 and 3.5 wasn't really good. We do have a Note 2,MIUI, and Sense 5 port for our devices and will likely to get ubuntu touch as soon as it is stable. Problem is that most of the developers don't have that much free time to attempt an international S3 or an US S4 port so they do what they can with the time they have.
Click to expand...
Click to collapse
I definitely agree; time is a huge issue. I'm assuming it's much more work porting a 4.2 based rom than it is a 2.3 based one. There's a good chance it's not worth the time investment considering the potentially buggy outcome.
Also, I apologize for assuming you didn't have any experience with earlier phones. Your join date threw me off
Div033 said:
I definitely agree; time is a huge issue. I'm assuming it's much more work porting a 4.2 based rom than it is a 2.3 based one. There's a good chance it's not worth the time investment considering the potentially buggy outcome.
Also, I apologize for assuming you didn't have any experience with earlier phones. Your join date threw me off
Click to expand...
Click to collapse
I learn fast as the S3 is my first android device and within 3 days of buying the phone I rooted it and started flashing roms. I had ample opportunities to root/jailbreak my previous phones but waited until developers come up with better methods. As for the opening poster's question he will have to get the S4 launcher app and flash some of the S4 apps.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
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.
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.
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