Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
okay, i'm not a dumbass (maybe). Phone keeps resetting on its own randomly still but less frequently after I overclocked.
How is your battery condition? Like how old is it? Do you have and tweaks (kobridge or phakker scripts)
Cpusleep app? And you said it happens on a few ROMs, I would say it maybe a battery or hardware issue. Also, do you check the MD5 sums before you flash the different ROMs?
Sent from my SPH-D710 using XDA
Battery condition is good, I actually have two oem batteries that I use daily and swap them when one dies.
I'm not running any tweaks currently, but when I flashed the roms recently its been through a nandroid backup of my previous working rom. But I'll try a clean install without a backup and see if that works. Thanks
Sent from my SPH-D710 using xda premium
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Subiegsr said:
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Are you using a stock battery charger? Is the charging cable damaged or loose? I had an issue with an after market charger making my phone freeze up before.
Not to my knowladge, but it never hurts to check it. I use md5sum app.
Sent from my SPH-D710 using XDA
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Subiegsr said:
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
Click to expand...
Click to collapse
No problem, just wanna find out the root cause of the reboots.
Sent from my SPH-D710 using XDA
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
cp320703 said:
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You may be right on the money with that. It could be causing script confliction. Between the ROM and the CPU app. But I do know that cpu app scripts will override the ROMs cpu scripts, but not all the time.
Sent from my SPH-D710 using XDA
Subiegsr said:
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
Click to expand...
Click to collapse
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
g_ding84 said:
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I have 3 OEM and 4 extended they all do the same thing.
Sent from my SPH-D710 using xda app-developers app
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
tysonrj said:
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
Click to expand...
Click to collapse
Thank you very much. I didnt know this was an issue with the phone.
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Does it reboot in download mode? If not..I would odin to stock and go from there see if that fixes things.
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Subiegsr said:
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Click to expand...
Click to collapse
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
milky1112 said:
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
Click to expand...
Click to collapse
Thanks man. It started doing it today and I took out the SD card and it hasn't done it since. So maybe it was the SD card this whole time?
Hopefully it is.
Sent from my SPH-D710 using xda premium
Related
So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App
I have it too. Can you boot your phone up like normal after a little while? Everyone else on this forum who gets this can't do jack with their phone. I can boot up fine afterwards, it's just extremely annoying.
It's a code for some kind of hardware failure and they all had to get a new phone. I've been told a RUU may fix everything, but that's a semi-long process for someone as ADD as me to go through. You could try it though. And if you do, shoot me a PM with the results.
Yeah that's exactly what mine does, It'll boot right away and I usually only run into the issue when I'm playing a game for more than five minutes or using my phone in a warm environment. It seems to hit 100° F and then stops itself from overheating.
I was really hoping to not have to Ruu, because its such a process and I don't want to lose the gingerbread keyboard. Maybe someone else will chime in with another idea.
Sent from my ADR6300 using XDA Premium App
So far you and I are the only 2 I know about in the internet who can still boot up like normal afterwards.
I wiped dalvik last night and I haven't had the issue today, you might give that a try. It can't hurt.
-CM7 ADR6300
Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App
This just in, rebooted while playing star wars podracing on n64oid.
I think it is a heat issue, cuz my phone is always pretty warm when it happens.
-CM7 ADR6300
I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App
Also had it on OMFGB, though not as frequently.
Also, today I've noticed my haptic feedback has been... varied in vibration intensity.
-CM7 ADR6300
thisisshep said:
Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I have an Ruu that you just place on the root of your SD and flash through hboot no adb needed if you want it pm me..... and ill give you the file and instructions
Sent from my Incredible using XDA App
Well I broke down tried the RUU and that went through fine but I cant seem to replicate the error with stock. I tried gaming for about 20 minutes and it didnt do it yet, normally it does it after like 5
Good to know.
Have you gone back to CM7 and seen if it helps out there?
-CM7 ADR6300
No I havent tried rerooting yet and reinstalling cm7 It keeps doing it only now it gets stuck in a boot loop instead of doing the five vibration thing then it boot loops about 3-5 times till it cools itself down then restarts normally like nothing ever happened
I already talked to verizon and the new ones in the mail so theres really no sense messing with it anymore now i just need to decide if i want to root the next phone or not
That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App
thisisshep said:
So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
What version of ClockWorkMod are you running? I read some problems with flashing CM7 caused by CWM 3.0.0.8 that was fixed by going to 3.0.0.7
dpwhitty11 said:
That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yeah, you've got that right !!!!
When it happened to me I couldn't do a damn thing except get into clockwork Mod, which didn't help because I couldn't access the sdcard. I called up verizon and got a new one. For the two of you that actually have a working phone after this is your phone S-ON or S-OFF?
thisisshep said:
It seems to hit 100° F and then stops itself from overheating.
Click to expand...
Click to collapse
100F is nothing for these processors. Think about it, your body is 98F and a processor is meant to handle a lot more heat than your body. I know the TI OMAP in the original droid had a failure point of 220F.
silverxbv2 said:
I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nope, not rom related since it happened to me when I was using Incredibly Re-Engineered v2.3 and flashing a custom kernel when it happened.
Mine remained rooted ans s-off throughout the issue.
I unrooted and applied s-on and reverted to the November RUU and it fixed everything.
Rerooted and reapplied s-off a few hours ago and flashed Virtuous. No more CM7 for me. That's when I started having issues.
Mine does the same thing. Vibrates once, turns off, vibrates 5 times and the LED blinks green. I think mine is related to an overheating issue. Mine reboots almost always when im plugged into the car charger, talking on the phone over bluetooth on my way to work. About a 35-45 minute commute. Even when plugged in at home, and while messing with the settings as well. The only thing that is almost always the same is the screen brightness. Thats when it gets super warm and then turns off. I'll try it out with the screen brightness settings to lower then usual. But when I let it cool off, like I do in the car in front of the A/C vent for about 30 seconds,, with the battery out of the device, it comes right back on no problems.
Mine was rooted and s off. I believe I installed cm7 using clockwork 3.0.0.7 then upgraded to 8 and still had the issue. I know 100°f is nothing for a processor but it seemed to have issues as soon as it got around 110 then if you let it sit it works again so that's what led me to thinking it was a heat issue even though it doesn't make much sense
Sent from my ADR6300 using XDA Premium App
I am using [Odin]Stock EF02 with CWM 3.1.0.1/Root/Busybox 1.18.4 and also tried EF02Plus as well. I seem to have an issue only with EF02 with overheating. I remember it was an issue with the orginial leak of GB but now my phone will say it refuses to charge when it gets too hot. I did a check and my temp reading is at 107F. Now it is about low 90's outside today and we dont have AC as we do not want to kill the planet. Is anyone else having over heating issues? I have also tried both modems ef02 and ef10... I wounder is modem ec03 may solve this... whats your thoughts?
htc_joe said:
I am using [Odin]Stock EF02 with CWM 3.1.0.1/Root/Busybox 1.18.4 and also tried EF02Plus as well. I seem to have an issue only with EF02 with overheating. I remember it was an issue with the orginial leak of GB but now my phone will say it refuses to charge when it gets too hot. I did a check and my temp reading is at 107F. Now it is about low 90's outside today and we dont have AC as we do not want to kill the planet. Is anyone else having over heating issues? I have also tried both modems ef02 and ef10... I wounder is modem ec03 may solve this... whats your thoughts?
Click to expand...
Click to collapse
I used to have that problem too... it seems to be better now... im running marcusiants acs unnamed rom rc10 with the ee03 modem... it has seemed to fix my heating problems... hope I helped you
Edit: also im using maddogins lockscreen mod... just incase that would effect it.
Sent from my SPH-D700 using XDA App
Yes, EE03 runs much cooler. I tried them all.
Sent from my SPH-D700 using XDA App
Lol im getting super overheating problems with stock efo2+eflo modem
Im think of going back to srf once 1.3 comes out
Sent from my SPH-D700 using XDA Premium App
gtuansdiamm said:
Lol im getting super overheating problems with stock efo2+eflo modem
Im think of going back to srf once 1.3 comes out
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Try marcusiants rom on the acs site and try the ee03 modem.. that should help.
Sent from my SPH-D700 using XDA App
I saw this problem go away when I switched from EF02Plus and went to decadence EF02 deodexed version.
I have had this problem on every ROM I have tried since the release of froyo.. On froyo it would shut down because of the temps and cause all sorts of corruption problems. At least on gingerbread, I am not seeing the corruption, but the overheat lockup is still there and requires a battery pull... I have posted in every thread about this issue and have not seen a real fix to the solution. And I am not sure if it is just certain phones or what as it is not a huge widespread thing, but people do have it... I may try one of the other two roms listed later this week to see if I can sort out the problem...
lilmexx said:
I have had this problem on every ROM I have tried since the release of froyo.. On froyo it would shut down because of the temps and cause all sorts of corruption problems. At least on gingerbread, I am not seeing the corruption, but the overheat lockup is still there and requires a battery pull... I have posted in every thread about this issue and have not seen a real fix to the solution. And I am not sure if it is just certain phones or what as it is not a huge widespread thing, but people do have it... I may try one of the other two roms listed later this week to see if I can sort out the problem...
Click to expand...
Click to collapse
That sounds like a hardware issue if you have it on froyo too...
Sent from my SPH-D700 using XDA App
I think if I charge via usb it stays cooler since lower amp of 500mha
Sent from my SPH-D700 using XDA Premium App
Ran in the big sprint store that has the tech center in it, just to see what they said about the problem.. They ran some tests and an hour later, they came back and said the battery was def on the bad side of things and gave me a new one. So far my battery life has been crazy good and no heat shut downs.. I havent really tested it fully yet, but hopefully my issues were purely battery..
Sent from my SPH-D700 using XDA App
I'm running on ef02 stocked with root and I also use a extended battery with 3500mah capacity ,, been using all this ever since samfirmware released it but so far not one over heat problem that I have seen
Sent from my SPH-D700 using XDA App
lilmexx said:
Ran in the big sprint store that has the tech center in it, just to see what they said about the problem.. They ran some tests and an hour later, they came back and said the battery was def on the bad side of things and gave me a new one. So far my battery life has been crazy good and no heat shut downs.. I havent really tested it fully yet, but hopefully my issues were purely battery..
Click to expand...
Click to collapse
Good to hear you didn't hae t get your whole phone replaced.
Now you should try rc10... batteries great after calibration with ee03 modem... right now I'm at 94% and my phones been off the charger for 3.5 hours and the screens been on 30 minutes... I got 3.5 hours with screen on yesterday, and that as urin the calibration process, so today it I'll probly be better .
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Yes, EE03 runs much cooler. I tried them all.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I agree. I use the EE03 modem on the EF02 rom and it work better in my opinion.
Replaced battery did not change anything... On the drive home, talking, same thing happened.. Granted is was like 100 degrees out and I have no ac in my truck... But yeah still shut down!! I guess I am gonna try unnamed and ee03. I guess I have to odin to ee03 correct??
lilmexx said:
Replaced battery did not change anything... On the drive home, talking, same thing happened.. Granted is was like 100 degrees out and I have no ac in my truck... But yeah still shut down!! I guess I am gonna try unnamed and ee03. I guess I have to odin to ee03 correct??
Click to expand...
Click to collapse
That sucks... and yeah print it it take about like a minute to set everything up.
Sent from my SPH-D700 using XDA App
lilmexx said:
Replaced battery did not change anything... On the drive home, talking, same thing happened.. Granted is was like 100 degrees out and I have no ac in my truck... But yeah still shut down!! I guess I am gonna try unnamed and ee03. I guess I have to odin to ee03 correct??
Click to expand...
Click to collapse
Everything is in my sig plus newest version should fix any issues you have
I just came from the Nokia n900 and having so many things working on the phone is a refreshing change! Ive lurked around and read a lot! As a result ive succesfully rooted my phone and have even tried out a few custom roms! However I have a question about a ROM im currently using but I cant post in the dev forum yet so I figured ill try here. Im currently using the digital warfare ROM and ive noticed that my powersave feature does not seem to work correctly. It will kick in regardless of the battery percentage I set. So ive just left it off for now. can someone help?
lvlonkey said:
I just came from the Nokia n900 and having so many things working on the phone is a refreshing change! Ive lurked around and read a lot! As a result ive succesfully rooted my phone and have even tried out a few custom roms! However I have a question about a ROM im currently using but I cant post in the dev forum yet so I figured ill try here. Im currently using the digital warfare ROM and ive noticed that my powersave feature does not seem to work correctly. It will kick in regardless of the battery percentage I set. So ive just left it off for now. can someone help?
Click to expand...
Click to collapse
First I want to give you huge props for actually reading and doing all that on your own instead of posting a ton of useless threads with questions that can easily be found! But to answer your question, the My Account app has its own power save feature, try going into that app and adjusting it from there or just disabling it all together. Hope this helps.
Sent from my GT-P7510 using xda premium
oh man it was really easy compared to what i had to deal with using the n900! well for now i suppose ill just disable it. thanks!
lvlonkey said:
oh man it was really easy compared to what i had to deal with using the n900! well for now i suppose ill just disable it. thanks!
Click to expand...
Click to collapse
Just disable the power saver in the my account app and use the power saver settings built into the phone, that's what I do.
Sent from my SGH-T989 using xda premium
Welcome to the family.
This phone is pretty beast, and it will only get better.
Thanks! I can tell! making the transition from hw Kb to all touch is kinda weird but this.phone is so capable and powerful its awesome!
Welcome dude and yea i would just disable this phone is great with battery life anyways. One suggestion tho i would freeze tmobile my account all together in titanium backup or uninstall it tgats if u have it installed it actually messes with wifi. When your on wifi it will turn on 4g signal whenever data is requested which isnt good cuz u think ur using wifi the whole time. Ever since ive disabled tgat app i have not had a problem with wifi or 4g service. I actually think its a way for tmobile to snoop on our data. I made a thread about this and other people have confirmed this app to be the culprit. I actually was gonna take my phone back because i couldnt get wifi to stay connected so thats when i started investigating and found this
Hmm I like to keep track of my data usage but if thats the case away it goes!
lvlonkey said:
Hmm I like to keep track of my data usage but if thats the case away it goes!
Click to expand...
Click to collapse
I remember someone posting some dialer codes where you can check how much data you have accumulated. I just don't know where I saw it. Post on the q&a to find put.
Sent from my SGH-T989 using Tapatalk
Ok nice ill look around for that. Ive just noticed the phone gets pretty warm/hot on some graphics intensive games. is this a cause for concern?!
novanosis85 said:
I remember someone posting some dialer codes where you can check how much data you have accumulated. I just don't know where I saw it. Post on the q&a to find put.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
It's #932# to check data on the dialer..
Sent from my SGH-T989 using XDA App
lvlonkey said:
Ok nice ill look around for that. Ive just noticed the phone gets pretty warm/hot on some graphics intensive games. is this a cause for concern?!
Click to expand...
Click to collapse
Are you overclocked?
Sent from my SGH-T989 using Tapatalk
No im running at stock speeds
It's not unusual for a phone to get warm when running cpu/gpu intensive processes like games. It only becomes a problem when it gets incredibly hot and forces the phone to reboot or the battery gets too hot to touch.
#932# for data
Sent from my SGH-T989 using XDA App
Thanks. now i'm having a new problem. My phone will just randomly shut off and I cant turn it back on until I pull the battery. It has happened twice so far
is your phone hot when this happens? try darksides kernel. haven't had an issue.
Sent from my SGH-T989 using XDA App
not hot. i just flashed his new rom/kernel combo with a clean wipe and as i was messing around with milocker it did it again. just shut off on me. only way to bring it back is to pull the battery. very strange.
You using a new ROM? I know you said new ROM/kernel combo but that could imply same ROM new,kernel. If youre on the same ROM, check the thread to see if its an issue with it I guess. Could always try a new one and see if that fixes it. Let us know if you find out anything.
Sent from my SGH-T989 using xda premium
lvlonkey said:
Hmm I like to keep track of my data usage but if thats the case away it goes!
Click to expand...
Click to collapse
I use 3G Watchdog. It's available in the market. Has a nice little widget as well.
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
Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium
cyberianrazr54 said:
Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Look in the CM 10.1 thread I pointed out which are updated and compatible with the latest.
I guarantee you this: if you have battery problems with the stock CM kernel, you will also have battery problems with another one.
Aerowinder said:
I guarantee you this: if you have battery problems with the stock CM kernel, you will also have battery problems with another one.
Click to expand...
Click to collapse
Might be the case, but the flicker is resolved for me flashing a 3rd party kernel. I was getting it really bad, like screen would go black and come back 10 times with in 2 seconds so it was nasty. Not sure why it was happening on stock and not custom...
I'm not having any battery problem. Just screen flickering and random reboots. Any fix?
Sent from my SGH-T999 using xda premium
Did you not read what I posted? http://forum.xda-developers.com/showpost.php?p=40525936&postcount=11050
Sorry. I didn't refresh the page so I didn't see what you said. But I would try to flash a new kernel now. Thx for the help.
Sent from my SGH-T999 using xda premium
cyberianrazr54 said:
Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
My Story:
Did a clean flash (as ALWAYS), and I have none of those problems. No flickers, no reboots, seems solid here, staying with stock kernel.
:good:
CodyRst said:
My Story:
Did a clean flash (as ALWAYS), and I have none of those problems. No flickers, no reboots, seems solid here, staying with stock kernel.
:good:
Click to expand...
Click to collapse
Some aren't and some are. Was like that the old days for the most part. I every single flash unless told not to, clean flash. I wipe my internal and external almost once a week, to avoid issues as well. Just how it is for some of our phones unfortunately.
mt3g said:
Some aren't and some are. Was like that the old days for the most part. I every single flash unless told not to, clean flash. I wipe my internal and external almost once a week, to avoid issues as well. Just how it is for some of our phones unfortunately.
Click to expand...
Click to collapse
Oh ok, gotcha. Kind of weird that it would happen to some and not others...
I suppose i lucked out.
CodyRst said:
Oh ok, gotcha. Kind of weird that it would happen to some and not others...
I suppose i lucked out.
Click to expand...
Click to collapse
Almost all 4.2.2 roms that have the latest merges have reports of it happening. Not alarmed at all, it may end up happening to you soon enough lol.
Would lowering the maximum CPU frequency to 1459 MHz save battery?
Sent from my SGH-T999 using xda premium
You are still ignoring the actual problem. And until you fix that, your battery life will suck. I can't be any more direct about this. I'm sure people would be happy to help you, if you would ask for it.
Aerowinder said:
You are still ignoring the actual problem. And until you fix that, your battery life will suck. I can't be any more direct about this. I'm sure people would be happy to help you, if you would ask for it.
Click to expand...
Click to collapse
I'm not having problem with battery. I just want to save more so it can last long.
And it seem like battery life on cymod10.1 with katoon kernel for me is draining pretty fast compare to stock cymod 10.1 and stock kernal
Sent from my SGH-T999 using xda premium