Related
I have a Samsung Galaxy SIII from AT&T (d2att ), and I have it rooted, running task650's AOKP, and TWRP 2.4.1.0 for recovery. It works fantastic, and I love it I have, however, been trying everything I can think of to try and get ktoonsez's kernel to work on it, for the features that his kernel offers. I am having a funky issue, which according to task, kt, and a few others on the boards, is device-related. It seems that my phone, individually, is the problem. This leads me to my question.
How feasible is it to get AT&T (or Samsung?) to replace my phone, based on the fact that there is something different hardware-wise between mine and the vast majority of other peoples?
It seems that nearly everyone who runs this combination of task and ktoonsez has nothing but good things to say, and I have yet to see anyone gripe about the same issues that I have had, and not be able to fix them, usually by a simple full wipe. I have tried to do full wipes with and without letting Google initialize/restore my account. I have tried going back to stock everything, and trying again. I have made sure to turn off Performance Control, so there should be no conflict there. I have tried setting up my phone in its entirety, restoring information, restoring apps with TiBu, and then installing the kernel. I have tried with and without deleting mpdecision. I am following all of the directions posted per OP for both threads, and with the gapps posted by task himself. Nothing works, and I end up in a glitchy boot loop almost immediately after flashing the kernel, even if my phone was running buttery stable before the flash.
I have come up with a couple things to try tonight, but if they don't work, I would like to pursue getting a new phone to replace this one. Is that an option?
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
task650 said:
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
Click to expand...
Click to collapse
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
drinfernoo said:
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
Click to expand...
Click to collapse
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
task650 said:
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
Click to expand...
Click to collapse
Time to get creative lol
Sent from my SGH-I747 using xda app-developers app
Settling In
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
bsam55 said:
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
Click to expand...
Click to collapse
I suppose that is possibly what's going on with mine, I'll give it a couple more tries
Sent from my SGH-I747 using xda app-developers app
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
pcshano said:
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do not intentionally brick your device. That could be just as bad as leaving your phone rooted when you take it in (depending if Samsung can see any part of the storage). As far as warranty exchange "excuse" that is on you to decide. Follow the post quoted below to help your chance at warranty exchange. This has been discussed quite a bit all over the place.
hednik said:
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
G-Man. said:
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I completely agree. I'm on tasks currently using his underwear kernel provided. I've also tried KT's kernel as well. Yes you can get more customization with KT's and his custom governor, but is it worth it to go through all the hassle to get a new device? I would say no. Like I said I've tried both kernels, I'm currently using tasks underwear kernel, I may try KT's again, may not. When I did before, I didn't notice a drastic difference between the two, esp not enough to warrant going through a device replacement.
Consider this. You are running tasks rom with absolutely no issues with the kernel he provides. Is that not good enough? I know it is for me. His rom is absolutely the most stable rom I've ever tried on any device. Remember it's just a phone. Just some food for thought.
Sent from my SGH-I747 using xda app-developers app
Probably right, but i don't always run task's ROM, either. My favorite ROM so far has actually been ParanoidKANGDroid, but I wanted 4.2.1, so I went to task. I'm actually running PACman right now, and for the time being, even his PC is broken
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
G-Man. said:
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Of course, but if it allows me more flexibilities and control over my phone and what it does, I'm all over that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
G-Man. said:
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
When the s3$ first come out, a lot of people were bricking them. Trying to root or installing an international ROM. I'm pretty sure Samsung staff was aware of that but they still gave free replacement. Some people even got a replacement from att or others carriers for free.
Sent from my SGH-I747 using xda app-developers app
If I do end up getting a replacement, can I take a nandroid, and restore it to the new phone?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It appears that Samsung has disabled root at the kernel level on new kernels for the 9500 and 9505. It looks like Samsung is going back on developer community support in favor of enterprise security.
http://forum.xda-developers.com/showthread.php?t=2263788
I hope they don't do that to us in the states - originally I thought it was because of the Exynos exploits but the 9505 is a Snapdragon 600 device.
Sent from my SGH-T999
EtherealRemnant said:
It appears that Samsung has disabled root at the kernel level on new kernels for the 9500 and 9505. It looks like Samsung is going back on developer community support in favor of enterprise security.
http://forum.xda-developers.com/showthread.php?t=2263788
I hope they don't do that to us in the states - originally I thought it was because of the Exynos exploits but the 9505 is a Snapdragon 600 device.
Sent from my SGH-T999
Click to expand...
Click to collapse
How can I get this phone, but I do not know if I like it very much
not have enough money to
http://www.youtube.com/watch?v=8EY3B5qG-hg&feature=youtu.be
What??
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
EtherealRemnant said:
It appears that Samsung has disabled root at the kernel level on new kernels for the 9500 and 9505. It looks like Samsung is going back on developer community support in favor of enterprise security.
http://forum.xda-developers.com/showthread.php?t=2263788
I hope they don't do that to us in the states - originally I thought it was because of the Exynos exploits but the 9505 is a Snapdragon 600 device.
Sent from my SGH-T999
Click to expand...
Click to collapse
bbobarino said:
What??
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
this is also a very nice woman told
but I do not have money to take them
http://www.youtube.com/watch?v=1_HdFLYH1Vg
What?
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
bbobarino said:
What?
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
choto what ?
What do you think caused by continuous:cyclops:
Can we get on topic please?
This is worrisome stuff - it may not affect those of you with a device right now but if it ends up being enacted across the board, you better hope that you never break it.
This is the first time I've seen this implemented on the kernel level. It is by far the most effective way to prevent root as it keeps you from being able to switch to the root user. Without the ability to do that, all software exploits are worthless. And good luck exploiting the kernel itself.
Sent from my SGH-T999
EtherealRemnant said:
Can we get on topic please?
This is worrisome stuff - it may not affect those of you with a device right now but if it ends up being enacted across the board, you better hope that you never break it.
This is the first time I've seen this implemented on the kernel level. It is by far the most effective way to prevent root as it keeps you from being able to switch to the root user. Without the ability to do that, all software exploits are worthless. And good luck exploiting the kernel itself.
Sent from my SGH-T999
Click to expand...
Click to collapse
Do they do this with a firmware upgrade? If so, would avoiding any OTA updates and only flashing Modded ROM's be a way to avoid it?
gaww said:
Do they do this with a firmware upgrade? If so, would avoiding any OTA updates and only flashing Modded ROM's be a way to avoid it?
Click to expand...
Click to collapse
I would assume yes.. and once youre rooted, you dont gotta worry about OTAs anyways....
OP suggested in another thread that this can be an issue if god forbid you need a replacement device..
I then stated that if we saved the backtostock file for the current firmware, this could possibly be avoided by flashing it through odin on a new device, but if samsung doesnt allow that by some means, were screwed
They're barring root at the kernel level on the i9500/i9505, but the difference with those models is that they have unlocked bootloaders and custom recovery with kernel source. It's possible to just install a custom recovery with ODIN and make a modified kernel (both of which are common practice in rooting anyway). They're just making it so that if you want to obtain root, you have to have physical access to the device to flash through ODIN, which is a lot safer in the long run. All this means is that Sally can't be exploited by running an APK or a malicious file to get root without her consent. (It also means that her "techy" boyfriend will have to understand ODIN to get root from now on,)
Are the phones shipping now locked?
Sent from my Galaxy Nexus using xda app-developers app
nitrogen618 said:
Are the phones shipping now locked?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
The T-Mo S4 has an unlocked bootloader. This is much ado about nothing. Read the last few pages of the thread.
i think we are flipping out over nothing. this is probably just for government phones. I think samsung is smart enough to know the heat they will get if they implement this across the board.
Worse comes to worse, carriers start to implement this, and tmobile doesnt seem interested in doing anything of the sort. the verizon and at&t guys are the ones that should be worried then.
but like i said before. making a mountain out of a molehill
It's for security reasons. You will still be able to install a custom kernel and have root. One minute people complain about an exploit the next they complain about not being secure.. it really isnt a big deal. Well I'm not a dev so I can't really say it's not a big deal but it is what it is and you'll still be able to have root.
Sent from my SGH-M919 using xda app-developers app
Mr. bird said:
I'm not a dev so I can't really say it's not a big deal
Click to expand...
Click to collapse
I am, I can, and I did. Truly nothing to see here folks. Mr. bird here read the thread and gets it right.
s4 is the best
For rooting purpose, not S4 but Sony Z1.
Send from my C6903 using TapatalkPro
my device: Sony Z1C6903
Samsung I9506
xxhorseriderxxx said:
They're barring root at the kernel level on the i9500/i9505, but the difference with those models is that they have unlocked bootloaders and custom recovery with kernel source. It's possible to just install a custom recovery with ODIN and make a modified kernel (both of which are common practice in rooting anyway). They're just making it so that if you want to obtain root, you have to have physical access to the device to flash through ODIN, which is a lot safer in the long run. All this means is that Sally can't be exploited by running an APK or a malicious file to get root without her consent. (It also means that her "techy" boyfriend will have to understand ODIN to get root from now on,)
Click to expand...
Click to collapse
Come on now. How tech savvy does one have to be to use ODIN. Honestly, my MyTouch 3G was more difficult to root than this thing with ODIN. Point, click, profit. I'm sure all those "techy" boyfriends will be rooting Sammy phones just as easily as they do now. At some point someone will figure out a one click solution anyway.
I agree 100% though, this really is nothing to worry about. I welcome it honestly. Its a great bump for security. Given the current state of things with the NSA and whatever else trying to siphon data like damn vampires and hack everything in sight like Jason. Though I'd say this is more for businesses, we need all we can get. As it sits, we're about as bad off as Windows 95 would be on today's internet surfing warez sites.
Sent from my SGH-M919 using xda app-developers app
Odin Is pretty easy. I'm not that tech savvy with phones but when I had to use Odin I caught on quick.
Sent from my SGH-M919 using Tapatalk
its a better discussion for all.....Samsung is locking out root at the kernel level
This is the first time I've seen this implemented on the kernel level. It is by far the most effective way
to prevent root as it keeps you from being able to switch to the root user. Without the ability to do that,
all software exploits are worthless. And good luck exploiting the kernel itself.
This is worrisome stuff - it may not affect those of you with a device right now but if it ends up being enacted
across the board, you better hope that you never break it.
Can any one tell me if there are roms for note 10.1 2014 edition? thanks!
ZFlip_1301 said:
Can any one tell me if there are roms for note 10.1 2014 edition? thanks!
Click to expand...
Click to collapse
Check the "Android Development" section... you'll find em' there. (You might want to try searching as most topics already have threads and you can get the info a lot faster)
Sent from my SM-P600 using xda app-developers app
ZFlip_1301 said:
Can any one tell me if there are roms for note 10.1 2014 edition? thanks!
Click to expand...
Click to collapse
Do a search through the forums, and you will find your answer. Android Development has the ROMs and Original Android Development has the custom recovery needed.
Problem is that most users are skeptical about rooting since they will lose their warranty support from Samsung (trip counter). Until a root work around is found, I wouldn't expect any spectacular Roms or support..
Sent from my SM-P600 using xda app-developers app
sameer1807 said:
Problem is that most users are skeptical about rooting since they will lose their warranty support from Samsung (trip counter). Until a root work around is found, I wouldn't expect any spectacular Roms or support..
Sent from my SM-P600 using xda app-developers app
Click to expand...
Click to collapse
CleanROM is on version 2.0 for this tablet and is great. Much smoother and quicker than stock, and is de-odexed so all the cool Wanam add-ons can be applied.
[ROM][1/10/14][P600] - CleanROM 2.0 R2 -★| ML1 | Aroma | Smooth | Stable | Clean |★
http://forum.xda-developers.com/showthread.php?t=2577389
Read through the thread and you will see plenty of members that rooted just for that ROM, and are very happy they did.
sameer1807 said:
Problem is that most users are skeptical about rooting since they will lose their warranty support from Samsung (trip counter). Until a root work around is found, I wouldn't expect any spectacular Roms or support..
Sent from my SM-P600 using xda app-developers app
Click to expand...
Click to collapse
This is not true. You "might" not get warranty repair for software problems. If you brick your device because you don't know what you what you're doing... Do you really expect them to fix it any way?
Knox tripped or not, you will still have warranty service for hard ware related defects. Most common problems are physical buttons going bad, defective screen, etc.
Development on this device is fine, it's an expensive tab, not a ton of people have it. When the US let version comes out, my bet is you will see a lot more development
Sent from my SM-P600 using Tapatalk
Serinety said:
This is not true. You "might" not get warranty repair for software problems. If you brick your device because you don't know what you what you're doing... Do you really expect them to fix it any way?
Knox tripped or not, you will still have warranty service for hard ware related defects. Most common problems are physical buttons going bad, defective screen, etc.
Development on this device is fine, it's an expensive tab, not a ton of people have it. When the US let version comes out, my bet is you will see a lot more development
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I don't know, compadre, this is a really slow start. I'm thinking that I may have bought into a flop device and that most people will be going for the PRO line.
I've also never had to warranty out any of my Sammy devices, of which I've had many. I did have to RMA my Note 10.1 due to superbrick - emmc bug though, it was so knackered they didn't even care to check the flash counter. Glad I got the new one from BB, pretty sure they wont know how or be inclined to check the Knox bit.
There is very little risk in solely rooting and installing a custom recovery, unless there is something like the aforementioned emmc bug. Voiding the manufacturer's warranty should be of little consequence and more of a forgone conclusion when modifying your device. You break it, you buy it. Everyone who mods their device, especially from the kernel down, should know and accept that responsibility.
hi masters. Reset method for p601 knox. Do not know?
Once tripped you can't undo
Impossible.
http://omegadroid.co/wanted-knox-void-warranty-0x1/
Sent from my GT-I9505 using Tapatalk
No one knows
Sent from my SM-N9005 using Tapatalk
tata_brada said:
Impossible.
http://omegadroid.co/wanted-knox-void-warranty-0x1/
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Not impossible. Just unknown right now. Unfortunately this device has little developer support, so we don't draw big talent like Chainfire who could probably hack it back to 0.
GldRush98 said:
Not impossible. Just unknown right now. Unfortunately this device has little developer support, so we don't draw big talent like Chainfire who could probably hack it back to 0.
Click to expand...
Click to collapse
We will wait and see.
Some light in the tunnel
I have recently aqcuired a P600- and despite of being fascinated about the custom roms on other devices, loosing warranty right in the first week is still way too costly. Therefore I was wondering if KNOX could be reset- I am not sure if this has been discussed or tried on our device:
http://forum.xda-developers.com/showthread.php?p=52329946
There has been some progress to reset the KNOX temporarily until booting on the Note 3-- It looks promising..
Any thoughts?
Can anyone tell me if and when we will be seeing custom Roms like CM12 , MIUI, or Pac Rom? I'm not asking for dates I'm just asking if someone has development in the works, is there a reason we haven't seen anything yet. Is there something in the firmware or software that is preventing development? I just got my s6 a few weeks ago and before that I had a lg g3 but I remember from previous samsung phones I've had that we had to be s-off in order to keep root. With the OFE update in the development section it has a
Sent from my SM-G920P using Tapatalk
Place where u can shut off s-off. So if anyone can answer my questions I'd really appreciate it. Sorry about the 2 different posts. I sent the first part on accident so I had to finish it with another post.
Sent from my SM-G920P using Tapatalk
S-OFF is for HTC phones.
Oh ok. What I meant then was OEM unlocking. It says it unlocks the bootloader. Does that mean anything as far as development purposes. Is that a good thing. What early will that mean for our phones. Sorry about my first post. I've had many different kinds of phones. Each had different ways to root and tweak the phones.
Sent from my SM-G920P using Tapatalk
In before the burn...
I suggest putting this in the q&a section
Sent from my SM-G920P using XDA Free mobile app
I suggest not posting this at all and just getting it removed.....
Thanks for the nice comments people. It was just a question. You don't have to be so rude. Just delete it then.
Sent from my SM-G920P using Tapatalk
Actually, i thought this was a good question. No asking for a hard date or anything, just an honest question asking if there is a technical hurdle delaying development on this device. I was also curious about this.
It's because we're on an Exynos chip this time around, not a Qualcomm.
dpwhitty11 said:
It's because we're on an Exynos chip this time around, not a Qualcomm.
Click to expand...
Click to collapse
That has nothing to do with it. That only means it'll be hard as hell getting an AOSP ROM (CM, Pacman, etc.).
JoeFCaputo113 said:
That has nothing to do with it. That only means it'll be hard as hell getting an AOSP ROM (CM, Pacman, etc.).
Click to expand...
Click to collapse
Yup nothing to do with the chip. It's the fact that 5.1.1 is a pain in the a$$ for devs but I have no doubt they will figure some out soon.
Thanks guys for the responses. My next question is how come all the other s6 phones from different carriers have all kinds of roms? Aren't those s6's the same as sprints?
Sent from my SM-G920P using Tapatalk
BREWGIRL03 said:
Thanks guys for the responses. My next question is how come all the other s6 phones from different carriers have all kinds of roms? Aren't those s6's the same as sprints?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
No, almost each variant is different. The sprint variant is a little trickier.
I was wondering if you can tell me the difference? Is this something that sprint did or something samsung did to the phone. Don't they all have that new chip in the instead of the qualcom or however it's spelled chip? Does the sprint phone being trickier to get custom Roms for mean that one carriers phone is better than anothers. I'm just curious. I like to know what's up with my phone so if someone asks me I can tell them and I sound like I know what im talking about.
Sent from my SM-G920P using Tapatalk
BREWGIRL03 said:
I was wondering if you can tell me the difference? Is this something that sprint did or something samsung did to the phone. Don't they all have that new chip in the instead of the qualcom or however it's spelled chip? Does the sprint phone being trickier to get custom Roms for mean that one carriers phone is better than anothers. I'm just curious. I like to know what's up with my phone so if someone asks me I can tell them and I sound like I know what im talking about.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
It has nothing to do with one carrier being better than any other. I'm positive it's a couple of factors such as the fact that 5.1.1 is a butthead for devs. Also, the previously mentioned development knowledge of exynos but along with that Sprint is as CDMA carrier which tends to be as little trickier for porting/development.
Sent from my SM-G920P using Tapatalk