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
Ok, before I get crucified, I have searched and I haven't found anyone having anywhere close to the same issues as I. My last phone lost 4g after rooting. I couldn't get it back till I restored to stock. Flashed radios, roms, and wiped cache, data, and davik cache. Well, I finally raised enough of a stink to get an NIB thunderbolt. Rooted then had the same issues with 4g going out. So finally I tried something I didn't try before, I reflashed the mr1 upgrade rom from J's root thread. I got 4g back, but now I have issues with it shutting down randomly. It's not a reboot, it's more like a sleep of death. I can only fix it with a battery pull and reboot. I'm not overclocked, and I haven't even used setcpu on the mr1 rom. Is anyone else having these issues? Also, when I first received the phone and used it unrooted for two days until I had time to root it, it was plagued with random reboots every hour or so. I loved my new phone and didn't mind it until I started having major usability issues. I can't deal with a phone that can't stay on all day and I'm not sure what to do at this point. Does anyone have any possible explanations for what I'm experiencing?
I have this issue but I am pretty sure it's hardware related. Sometimes if I put pressure on both ends of the phone and bend it a tiny bit, it will shut off. Might not be the same thing as you but that is what is causing it for me.
1454 said:
Ok, before I get crucified, I have searched and I haven't found anyone having anywhere close to the same issues as I. My last phone lost 4g after rooting. I couldn't get it back till I restored to stock. Flashed radios, roms, and wiped cache, data, and davik cache. Well, I finally raised enough of a stink to get an NIB thunderbolt. Rooted then had the same issues with 4g going out. So finally I tried something I didn't try before, I reflashed the mr1 upgrade rom from J's root thread. I got 4g back, but now I have issues with it shutting down randomly. It's not a reboot, it's more like a sleep of death. I can only fix it with a battery pull and reboot. I'm not overclocked, and I haven't even used setcpu on the mr1 rom. Is anyone else having these issues? Also, when I first received the phone and used it unrooted for two days until I had time to root it, it was plagued with random reboots every hour or so. I loved my new phone and didn't mind it until I started having major usability issues. I can't deal with a phone that can't stay on all day and I'm not sure what to do at this point. Does anyone have any possible explanations for what I'm experiencing?
Click to expand...
Click to collapse
Sleep of death? Haha, yeah, I've got the same issue. Screen refuses to turn back on, but I know the device is still running since my notification light keeps blinking. Only solution is a battery pull. Happened twice today.
I'm running dasBAMF 2.0-5.
Ok, well I guess its good to know that I'm not alone.
Well, I guess if its hardware I will whine a little more to Verizon.
Sent from my ADR6400L using XDA App
1454 said:
Ok, well I guess its good to know that I'm not alone.
Well, I guess if its hardware I will whine a little more to Verizon.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Yep. I too have experienced the sleep of death at least half a dozen times. I experienced it a lot on MRs. at the time I was running Gingeritis beta CO and Imoseyans kernel OC to 1403mhz.
I've been running on MR2 for a week now with Gingeritis final and Imoseyans kernel.... and haven't had one spasm.
Rooting doesn't disable 4G. Did you make sure your original TB radio wasn't set to CDMA auto (prl) in settings/network before returning it?
Sent from my ADR6400L using XDA App
Had the "sleep of death" happen today for the first time. Rooted on candy rom 2.0.3. Happened as soon as I got into a 4g area while driving.
sleep of death aswell here. Not often.
there is a new gb radio out MR2.5 ...running great so far..
Sent from my ADR6400L using XDA Premium App
I am running MR2.5 with The Perfect Storm 1.5 with no reboots or problems!!
TwistedX
I've been getting SOD occasionally as well. Happened once on stock rooted, several times on gingerBAMF, and on BAMF 1.7 as well. Often it has happened while asleep to find phone unwakeable in morning, but still on. The last day or so I've had market downloads seemingly trigger it as well. At least it did it while updating apps....No physical triggers have caused it. It's never frozen in my hand as previous poster mentioned.
I'm scared it's increasing in frequency. Guess I'll see how MR 2.5 works when I get a chance next.
I didn't say that rooting was the cause. Just the series of events. It wasn't until I flashed new roms that I started having issues. I have gone back to mr1 upgrade and gotten 4G back, but now I have the sleep of death issue.
Sent from my ADR6400L using XDA App
I may try this setup and see if I still have issues. Thanks for the feedback.
Sent from my ADR6400L using XDA App
Mine has only frozen while using once. Most of my issues with the sod have been after being in sleep for a while.
Thanks for all the responses, maybe one of the devs can chime in with some advice as to what we need to do to fix it.
Sent from my ADR6400L using XDA App
I did have a simi random reboot issue this morning or o think so. I was making coffee and heard the phone vibrate than screen. Went off and rebooted. I was running gingerits with twisted and imo kernel at 1400/184 smartass extreme. I think that was the issue cause I set it to 1400/240 interactivex and have had no issues and got 16hrs outta of my 1700 batt with heavy usage.
Sent from my ADR6400L using XDA App
+1 sleep of death
^_^_^
It's happened to me twice, once yesterday and once today. I have never had it happen until I flashed MR2.5.
i'm 3 days free of any more SODs after wiping to death and flashing MR 2.5 radio. happy days again. I hope. Probably just the wipe and not restoring any app data at all that made it better.
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.
So i have a rooted tbolt with MR2 radio and ive used gingeritis and the newest shooter leak. Every once in a while the screen just wont turn back on. Unresponsive, ive let it sit nights fine and it turns back on no problem. But when its unresponsive the only solution is to do a battery pull and reboot the phone. It sucks cause theres no telling if the phones just sleep or if its dead lol. Has anyone else had this problem?
For what its worth, i do underclock it to 184mhz but never overclock it. Also the voltage is pretty low at 750 when underclocked. Could this be the reason for the freezes? Any insight would b helpful. Thanks all
Sent from my ADR6400L using XDA Premium App
I would do a full 3x wipe and reload the new GB radio and ROM again. I have had some issues that were odd/sporadic like yours and this seems to be the fix.
thanks ill give that a shot
I had that problem too with MR2 and an older radio also. between wiping everything and doing MR2.5 it got better.
That is called the sleep of death coined by some other member that started a similar thread. I've had that problem on mr2. Haven't had it on mr2.5.
Well it did occur for me again this morning 7 days after wipe/update to mr2.5. Very frustrating. At least it's not happening every day like it was prior to this...
Sorry if this has already been addressed or asked, and I can't post in the dev thread cause of my post count. I recently (Saturday) flashed BAMF RC3 from stock along with the MR2 Radio update. Currently using stock kernel.
Since then when the phone is not connected to a Charger/USB it'll randomly hard lock requiring a battery pull to come back up. It happens at random times while unplugged. I've set the CPU to 1.2~/368 as suggested with no change.
I flashed MR2.5 and seems like instead of the hard lock I'm getting random reboots now. Which IMO is a lot less annoying since a battery pull is PITA.
Anyone have similar issues or suggestions on a fix?
I've had much of the same problems. Things I've tried : full wipe and restoring minimal data, increasing min to 368, turning off fast boot, various roms/radios ...
Hard freezes seemed to be stopped on gingerbamf for me after the fast boot/clock speeds adjusted. Reboots still happen (on mr2 and 2.5)
Sent from my ADR6400L using XDA Premium App
Thanks for replying least I know I'm not the only one...
So i tried CM7 RC1.1 on MR2.5 and it's rebooting as well. I'll try and disable to fast boot to see if it clears the hard locks. So far I've managed to hard lock CM7, BAMF2.1 and BAMF RC3.
you can try cm7 with the original radios if it gets really bothersome.. have you tried wiping dalvik when you wipe everything else? What kernels have you been using?
Sent from my ThunderBolt using XDA Premium App
I have been doing wipe data x3, and dalvik x3. I'm using stock kernels