Related
i was hoping to get some ideas on ways to set up my phone to minimize random reboots on the new radio, I tried changing kernels but had no luck. Any info would be greatly appreciated. Rom/kernel version and if you are OC and if yes up to what? 4g/3g? And if on cdma or something else Thank you
Sent from my ADR6400L using XDA App
gemitero said:
i was hoping to get some ideas on ways to set up my phone to minimize random reboots on the new radio, I tried changing kernels but had no luck. Any info would be greatly appreciated. Rom/kernel version and if you are OC and if yes up to what? 4g/3g? And if on cdma or something else Thank you
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I read that it isn't so much the phone, but rather the cell towers that were causing the random reboots (this was over in the TB General Forum)
nerozehl said:
I read that it isn't so much the phone, but rather the cell towers that were causing the random reboots (this was over in the TB General Forum)
Click to expand...
Click to collapse
That sux...guess im **** out of luck since the cell tower near me seem to suck and give me random reboots...hopefully the issues get resolved soon...thanks for the info
Sent from my ADR6400L using XDA App
I have found most reboots occur when over clocking past 1.3ghz due to voltage spikes or inadequate overvolting at 1.45 and up.
On cm7 and bamf I never had a reboot with either radio using imo kernels keeping oc under 1.42 and using smartass governor
Hope this helps
Usual location: West Los Angeles area
I have tried all combinations of radios and several roms available on XDA. I've never experienced a random reboot.
Baseband verison: 1.16.00.0402w_1
Kernel: bamf_4.4.7
build: Das Bamf 1.6.2 Remix
Software Number: 1.13.605.7
PRI Version: 1.41_002, 1.64_002 <- dunno if this matters for anything.
No overclock.
Can't think of anything else. I think I've been lucky.
Bone Stock and has never rebooted on me as of yet. I live in the outskirts of a 4G tower and it flips in and out. I do have a slightly better battery life compared to before the update.
I've also tried a bunch of combos with no reboots, but I mostly run leankernel "normal" and das bamf remix. Never a reboot.
I've never had a reboot using the latest radio (both the LTE and CDMA ones). Im just using BAMF Stripped and adrynalyne's 4.4.7 kernel without voice recording. No overclocking and ondemand governor. I think most of the reboots are probably just caused by overclocking/overheating.
i am running the BAMF roms. I upgraded my radio when it came out. I didnt have reboots for a week or so then i had random reboots and even had my phone just shut off a couple of times. I only have 3G and have the phone set to CDMA auto.
I changed the radio to the .7CDMA and .6LTE and havent had a reboot since?
In that time i also changed kernels and roms also, but did have a couple of days with the same rom/kernel after changing the radio to the .7/.6 combo.
I also did notice that my phone was on 3g revA even though it was set to use eHPRD. Verizon was messing with things and maybe that caused the reboots. Now that they turned eHPRD back on and pushed the update maybe they were the cause of the reboots and maybe it is fixed now?
I'm running the latest stock everything.. no random reboots in over 3 days.
I'm running the new firmware and radio, rooted and crapware removed, but otherwise stock. No reboots in my local area.
Having said that, running the same stuff, I was getting reboots last week when I was in the Indy area. Based on that, and the timeline of events, I think this is what's happening (I posted basically this yesterday? in another thread):
VZW started rolling out the update, and recognized an issue. That issue was caused by an incompatibility between the software on some cell sites (VZW uses at least Nortel, Motorola and Lucent 3G BSSs, Ericsson and Lucent for LTE, maybe others) and the new TB radio firmware. They believed the root cause to be with the eHRPD software on some cell sites.
So, they stopped the update rollout. They turned off eHRPD. They upgraded the software on the problematic cell sites. They turned eHRPD back on. They restarted the update rollout. That all fits with what we've seen.
I wasn't getting reboots before at home, and I'm not getting them now. I think I'm on a Nortel BSS. When I was getting the reboots in Indy, they stopped when I reverted to the older radio firmware. From that, I assume that VZW uses a different BSS vendor to cover the area of Indy I was in, and the problem was with interoperability of the new TB radio with that vendor's BSS.
People are apparently still getting reboots. It may be Verizon didn't really fix what they needed. It may be that they only fixed one type of BSS, and need to address the issue on another type. They may have only fixed one of multiple issues. It may actually be an issue with the phone's firmware. eHRPD/LTE are new, and this is just some pain they're going through. You find problems when you have 100,000 users that you don't when you have a few hundred.
I don't know whether I'd get reboots today if I went back to Indy and tried again with the new radio firmware. I didn't have any problems switching between old and new radio f/w running my mostly stock image - YMMV if you're running someone's "ROM."
You can get just the radio firmware in this thread.
Finally, I suspect the reboot is caused by something like: phone tries to switch modes or negotiate something with the BSS (we know they're trying to make transitions work better, and that was the claimed reason for the radio upgrade). BSS doesn't respond as the phone expects. Phone retries unsuccessfully X times, then finally gives up and reboots.
The reboots would not have been to bad because it was occasional but the battery drain that happens is what I didn't like. Thank you everyone for their feedback.
Sent from my ADR6400L using XDA App
Heh, I just switched from BAMF 1.6.2 to CM7 alpha. Using latest radio leak and leanKernel extreme and I have had absolutely no reboots since switching ROMs.
(In no way should one infer from the previous statement that BAMF and/or Adrynalyne's kernels in any way definitively contributed to reboots. - I changed ROMs a day or so after the new firmware was pushed to unrooted phones.)
Literally, everything stock. I flashed the PB file flashboot, that's it. No reboots, and killer battery life. Half a battery got me through the day.
This is a replacement Thunderbolt...
I had two reboots and both happend when my phone was running hot I live in AZ
Sent from my ThunderBolt using XDA App
Bamf 1.6.2 imoseyon lean kernel latest one not overclocked extended battery and in middle tn
Im in a 4g area at all times from home to work and town and I have never had any random reboots
My radio settings have always been on preferred 4g lte only
On new radio
Sent from my ADR6400L using XDA App
Leankernel 2.4, bamf 1.6.3 remix with leaked OTA, live in LTE area but go into 3G frequently. No reboots ever. Not sure if this matters but I exchanged my phone a week ago due to the wireless radio getting stuck off. New one is working great so far.
I have been overclocked dice day one on this thunderbolt and started noticing random reboots and I'm not on the newest radio. The weird thigh is I got a random reboot each time I go to my parents place where the signal isn't great by at the same time the other day I returned to stock clock speeds and haven't had a random reboot yet. So its kinda hard to narrow it down. But I'm going with lack of voltage during overlcocming to be the cause. Besides I can't tell a real world difference in performabce when overclocked anyways. Btw I'm using 4.4.5 kernel by adrynalyn.
No root. Before the update I had to do a factory reset because I had to data making my phone basically be a paper weight.
Sent from my Thunderbolt using XDA App
So I flashed the leaked radio the other night after 2 early reboots everything settled down and was going good. I was using PS1.4 rom and ziggys 5/3 kernel and its default max1036/122 min and no OC app. Changed the setting to cdma(prl) cuz I dont live in a 4g area and shortly after I started getting reboots again. Then I changed it back to evdo/cdma auto then no reboots. But the searching for 4g was affecting battery life and I didn't see much of a difference between stock and leaked radio except the battery drain. Gps and everything seemed to be the same so I decided to flash back to the stock radio which has been more stable for me and I could keep it at the cdma(prl) setting which is better battery life for me...so ill probably stick to the stock radio until we get 4g. And that is my experience
Sent from my ADR6400L using XDA App
As the title implies, I have had an outrageous number of reboots since flashing the MR 2.5 radio. I want to know if anyone else has experienced this and if so, how was your phone set up. Mine was slightly overclocked and undervolted using SWAP and custom voltages
Can't fault the radio before you do the process of elimination. If it was happening with stock, sure you can fault the radio off the bat but don't jump to conclusions before eliminating any variables like overclocking and custom ROMS.
Sent from my ThunderBolt using XDA Premium App
I had reboots with MR1 but not MR2 or 2.5. Das Bamf 2.0-5. I agree that you should look at other reasons too..
Sent from my ADR6400L using XDA App
jharris0221 said:
I had reboots with MR1 but not MR2 or 2.5. Das Bamf 2.0-5. I agree that you should look at other reasons too..
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Yea...I know not to jump to conclusions about any radio...Having said that. I have had random reboots in three cases.
1) extremely undervolted- so I stopped doing this...plain and simple.
2) Using the straight MR1 radio...I fixed this issue by using the MR1 CDMA, Stock LTE hybrid radio.
3) On the MR 2.5 radio...reverted back to MR 2 for now, but I didn't have any reboots on the initial GB leaked radio.
With reboot cases 2 and 3, I was running the same overclock/undervolt and I just don't think this is the issue. One strange thing I noticed, and pointed out with the initial MR1 leak, my reboots really happened most frequently and could be repeated when going from wifi to 3g when listening to music. And the MR2.5 radio started rebooting in the same situation and when I just got out of range of my house wifi while on a walk.
I've never had a reboot on MR2/2.5, though I only had maybe one on MR1 as well.
Using BAMF 2.0 + Imoseyon's latest kernel for about a week or so now.
Using LTE 50% of the time, wifi 45% of the time and 3G/1x the rest.
CPU is on InteractiveX and overclocked to 1.4ghz and extremely undervolted
I do have most of the sense crap that wont break the phone ripped out, but that wont make a huge difference (using go launcher as well over rosie).
Maybe try running a logcat in the background, capturing data until it reboots again and then examining? That could be a rather huge file, but you could pipe it through awk/sed or something and filter out some of the obvious crap you know will always show.
I can count on 1 hand how many reboots I have had since I purchased this phone back in the beginning of April. I've been rooted since day 1 and have used all stock rooted roms, MR1, MR2 and MR2.5 radios. Started at baseband 1.12, used 1.13 and am now currently on 1.66.
Shawn haz root said:
I can count on 1 hand how many reboots I have had since I purchased this phone back in the beginning of April. I've been rooted since day 1 and have used all stock rooted roms, MR1, MR2 and MR2.5 radios. Started at baseband 1.12, used 1.13 and am now currently on 1.66.
Click to expand...
Click to collapse
Well consider yourself lucky...my sisters is completely stock and hers has rebooted more times than mine, and mine has gone through everything, including being dropped in a toilet
dhemke17 said:
As the title implies, I have had an outrageous number of reboots since flashing the MR 2.5 radio. I want to know if anyone else has experienced this and if so, how was your phone set up. Mine was slightly overclocked and undervolted using SWAP and custom voltages
Click to expand...
Click to collapse
I had a random reboot. Went back to MR2, and all is good now
ProTekk said:
Can't fault the radio before you do the process of elimination. If it was happening with stock, sure you can fault the radio off the bat but don't jump to conclusions before eliminating any variables like overclocking and custom ROMS.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
disagree. I was not over clocked, or running anything other than the normal.
dhemke17 said:
Well consider yourself lucky...my sisters is completely stock and hers has rebooted more times than mine, and mine has gone through everything, including being dropped in a toilet
Click to expand...
Click to collapse
Sounds like build quality issues then and/or just bad exception catching/checking in the software. I don't know what else could account for it really. However, I guess the greater question is, what component in the hardware is causing it and what part of the code is mishandling things so bad it resorts to just rebooting.
I have mr2.5 and flashed ginger remix beta 6 last night. Had 2 reboots within 5 minutes of flashing rom and radio. No other reboots after that. I'm using the kernel that came with the rom.
Sent from my ADR6400L using XDA App
herbiehusker2608 said:
I had a random reboot. Went back to MR2, and all is good now
Click to expand...
Click to collapse
same here. i had not had a reboot since going to GB over a month ago. then i put MR2.5 on mine and had 2 reboots in less than 6 hours, so i went back to [email protected] and have been fine.
I had one. Was first time I used gps while driving, it had some trouble loading up maps that first time and bam reset. then again right as it started from first reboot. Then all good for subsequent uses for 5 days now. *shrug*
I had a few reboots on the stock Thunderbolt (not rooted, maybe rebooted 3 times total in a 3 week time span). I rooted to das BAMF 1.7 and didn't have any reboots for the 2 weeks I was using it.
I just updated to the MR2.5 with das BAMF 2.0-6 a few nights back and had a reboot last night. I'm considering going back to 1.7 and MR1...
First I was one of the people that had reboot problems with 1.5. When I switched to 2.0 it went to random shutdowns, now on 2.5 no problems since I switched. With that said remember every Tbolt is different. I would suggest a few things"
the first is go back to what was stable and worked, if you dont really care about having 2.5.
second, try a different kernel, or max/min settings on the processor speed.
third, I would do a full wipe and try again from scratch. Sometimes certain things just dont take for some reason, anyway thats my thought process.
infinite012 said:
I had a few reboots on the stock Thunderbolt (not rooted, maybe rebooted 3 times total in a 3 week time span). I rooted to das BAMF 1.7 and didn't have any reboots for the 2 weeks I was using it.
I just updated to the MR2.5 with das BAMF 2.0-6 a few nights back and had a reboot last night. I'm considering going back to 1.7 and MR1...
Click to expand...
Click to collapse
Double check your processor settings also. I used to get random reboots on my OG droid because it couldn't handle the maximum and sometimes minimum settings I, or the kernel by default, had set up for it.
Okay so I'm not 100% sure if this is a sure fix, but it seems to have worked for myself and my wife. We both were getting random reboots like crazy and it was getting very annoying. I remembered back in my windows mobile TP2 days that a lot of stuff gets stored on the SD card after constant flashing and tweaks. So in order to get a proper flash u normally would have to reformat ur SD card, wipe, wipe, wipe, and then flash ur ROM. That is exactly what I did with my phone as well as my wife's phone. I formatted our SD cards after backing everything up of course. I backed it up on an external harddrive, formatted, put everything back, formatted the phone with a super wipe zip I found somewhere in the development forum, installed a custom stock Rom I have been tweaking and then booted up my phone and have not had a single random reboot since. So as the title says, it is a possible fix. If u try it then please post so that other users can know if it is actually stopping the reboots or if It's just a placebo effect. Thanks and I hope I've helped someone who is extremely frustrated as I was with their 500 dollar phone randomly rebooting.
Sent from my Beastly EVO.. And did I mention it has 3D?
I fixed mine with a buisness card as a shim for the battery lol
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
Yeah my battery wasn't loose at all. My phone would also sometimes freeze up and when I rebooted it would just be a black screen. I had to pull the battery to get it working again. I tried the auto brightness fix bit my screen would go black sometimes and rebooting did not fix. I actually had to pull the battery out.
Sent from my Beastly EVO.. And did I mention it has 3D?
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Truth. I've never had random reboots and the only reboots I've done were solely manual because of these hardlocks from custom kernels.
If only my phone played nicely with kernels...
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
sgt. slaughter said:
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm leaning more towards HTC's screwed up source. As this problem wasn't present in their 2.3.3 source, at least with netarchy's kernel. There weren't nearly as many kernels to choose from but still.
I've heard a few people say the source was either incomplete or messed up somehow. We can only hope that HTC releases an updated software version with a new kernel so that they're obligated to release the source as well, and this time hopefully it will be complete.
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
I used a gum wrapper for mine
Sent from my PG86100 using xda premium
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Lucentio said:
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Click to expand...
Click to collapse
Ur on the exact setup as I am. Kernel and ROM. Stock kernel still did exactly what u mentioned above as well. After formatting my SD card I have yet to have it happen. It's been about 8 days since I formatted. After reading the posts I don't think formatting my SD card is a fix, but I too am leaning towards HTC kernel being messed up. I think sooner or later my phone is going to do it. My phone was doing exactly as u stated. Booting into the splash screen and not going past it. On some occasions my phone would either freeze up or just go black. The hard buttons would light up but not my screen. Hope this gets figured out soon.
Sent from my Beastly EVO.. And did I mention it has 3D?
Mine resets between the hours of 71-80 of being on
I'm having the same problem and I do not know how to solve it! I am so close to selling my Evo 3D and going to the SG II.
I have ran CleanRom and currently running Fresh. I have tried Mwalts kernel, Bcblends kernel, and stock kernel from Fresh stock. No matter what I tried, my phone ALWAYS resets between the hours of 71-80 of being on.
The reset happens only when I try to turn on the phone. It turns on, off really quick, then I hit the power button again, the lock screen comes on, then the phone resets. It is getting really annoying as I love having stability and this phone isn't stable at all.
Any ideas? I have exhausted everything I know. I'm running the exact same programs as I have on the Evo 4G and since it is resetting at the same hours always at the same time on different ROMS/Kernels, I'm pretty sure its not app issue. I also tried changing between the 3 radios and no change there. The only other option now is to do a fresh install of Fresh and use it stock and see what happens.
Rytt
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
ifly4vamerica said:
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
Click to expand...
Click to collapse
already try that
no luck it still keep rebooting while screen off
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
chad.goodman said:
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
Click to expand...
Click to collapse
He said that before you found the magic fix I'm pretty sure. Notice that was back from November. Lol
Sent from my PG86100 using xda premium
Huge Thanks
thank you so much for sharing your information my evo 3d was rebooting about every 30 min and i have just been dealing with it because i had took my evo4g into the sprint store because it was rebooting aboutevery 5-10min so they looked at it and couldnt figure it out so the gave me the evo3d for free and i put the sdcard that was in my evo 4g into my evo3d without having any idea that it was the sdcard causing all of my problems so the same thing started to happen to my new evo 3d started off about every day and eventually started to reboot every 30min and i just decided that all htc devices were like this so i have been dealing with it but today i said enough is enough and looked online and saw this thread and wiped my sdcard and sure enough no reboots yet its been about 3 hours so i think its fixed
i cant thank you enough i think it got corrupt from all of the flashing i was doing
son of a ***** right as i was about to hit post the mother ****er rebooted so its not my sdcard after all should i take it in to sprint what do you think ahhh i should have never posted anything it was going so well FML!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ps hboot 1.4 is the **** no more going to the computer to flash a rom stupid hboot 1.5
I've sometimes had trouble running custom kernels (reboots and strange behaviors) that were fixed when running the stock kernel. But, the stock kernel leaves a lot to be desired in overall performance, so I continue to kernel hop. But, from my lurking on the different ROM forums, it seems that stock is the way to go for stability at the sacrifice of performance.
I had problems with evo rebooting and that in a loop. Very annoying. For that i've changed several roms just to find out that it could probably be because of widgetsoid.
At first the rebooting after some time of use, 1-2 days. And if flashing a different kernel than the one with rom. I was going mad, the last reboot or series of constant reboot after the evo has turned itself on, has occured after i set the brightness to lowest value, it was late so i wanted a darker screen. Interesting it when i set lowest value in system or via leedroid tweaks in widgetsoid widget popup - value im at 12 %. Maybe i got the restarts because i went below 12? Since my brightness im above 12 in widgetsoid and minimal in system, my evo didn't reboot a single time.
Currently i'm at shawn3d rom. Later i'll try some other kernel and rom again and see if the reboots occured.
U get random reboots while using any brightness widget with custom roms. I've narrowed my 3d threshold for the reboots to be anything less than 5%.
No reboots if kept at or above 5% for me...
Sent from my PG86100 using Tapatalk 2
i have had success after formatting system/data/cache to ext4 in the ext4 recovery, i had random reboots and lockups while using twrp and not formatting to ext4, (in all honesty i doubt the twrp was too blame)
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
brando56894 said:
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
Click to expand...
Click to collapse
still you might want to check the rom and kernel just in case, either re-flash or change.
if the problem still happens, use your warranty and get a new phone.
what rom, kernel, and recovery are you using?
I actually just happened earlier again. Got a text from a friend that she was here, so I went down and let her in, came back up and went to check my phone a few minutes later and it was off. WTF.
I'm currently using Nils newest business sense with the OC'd ICS kernel and the latest Amon Ra recovery. This used to happen on GB also so it's not a rom/kernel problem IMO.
It happens so sporadically (except for tonight apparently) that it's maybe happened 5 times since I got it on release day.
Maybe I have the governor in cpu master set too low? I have it at the lowest of 384 MHz, I've always wondered this: whats the difference between conservative and powersave?
did it happen while you were on stock GB or on a custom rom and kernel? maybe try relocking and running stock for a while and see what happens?
I honestly don't remember, it's been too long lol. It's not worth it to go back to stock and relock considering I like ICS too much.
brando56894 said:
I actually just happened earlier again.
I'm currently using the OC'd ICS kernel
Click to expand...
Click to collapse
that's the issue right there, run the stock kernel at stock speeds.
How could it be the ICS kernel when it's happened on GB also?
Which OC? I've read that the 1.8 causes random stuff like this, but 1.7 doesn't.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
3.0.16-g4a9c8a3 SebastianFM #1 is what the kernel info says
The zip name is Overclocked_kernel_v1.20_1836_MHz_by_sebastianFM.zip
Not all phones can handle overclocking.
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
brando56894 said:
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
Click to expand...
Click to collapse
9x out of 10 random reboots are from either undervolting too low or overclocking too high.
I went back to the stock kernel since it seemed to be a little choppy with the oc'd kernel. That may have been the problem after all.
Sent from my Transformer TF101 using Tapatalk
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
sharky17 said:
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
Click to expand...
Click to collapse
I recently had the same problem. It would overheat constantly, especially when playing a game, and if you charged the phone and tried to use it at the same time, it would only overheat faster. I got my phone when it first came out as well. The tech made up something about a short in the power button, but they did end up replacing the phone for me. You'll have to go back to complete stock of course before bringing it into the sprint store. If you need any assistance getting your phone backed up or back to stock, shoot me a message.
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
sharky17 said:
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
Click to expand...
Click to collapse
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
chris674 said:
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
Click to expand...
Click to collapse
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
sharky17 said:
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
Click to expand...
Click to collapse
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
DXtremz said:
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
Click to expand...
Click to collapse
I would flash with the stock Rom and bring it back to Sprint. If u guys underclocked it and it still overheats, then I would think it is a manufacturer's defect. It doesn't make sense that the phone will still overheat with the cpu being underclocked.
Chris