Anyone else experiencing a reboot issue and overheat with the newest OTA and 1.77 pri, or am i the only one?
numus said:
Anyone else experiencing a reboot issue and overheat with the newest OTA and 1.77 pri, or am i the only one?
Click to expand...
Click to collapse
no probs....used calks and fresh's, rooted of course, with the latest 1.77, all is well
numus said:
Anyone else experiencing a reboot issue and overheat with the newest OTA and 1.77 pri, or am i the only one?
Click to expand...
Click to collapse
No everything has been ok here using MYA ROM
No such thing
WORKING GOOD ON FRESH Rom. One reboot when i used the camera. Cleared the cache no issues.
Sent from my PC36100 using XDA App
I do have a rebooting issue. My phone will just randomly reboots and gets stuck in a rebooting cycle where it keeps rebooting when its at the boot screen or as soon as it boots upand I just have to pull the battery to fix it. It's not related to the new OTA or PRI for me. I've had this problem before and after root, tried different rom's, radio's, pri's etc., replaced my sdcard. I've tried many different things and can't figure it out. I've read on other forums that others are having the same problem and both Sprint and HTC know that many are having problems. Supposedly HTC is working on a fix, but can't determine what the cause is yet. The only thing I can think of is it's related to a heat issue, but have no idea.
Wrong section
acc49ers said:
I do have a rebooting issue. My phone will just randomly reboots and gets stuck in a rebooting cycle where it keeps rebooting when its at the boot screen or as soon as it boots upand I just have to pull the battery to fix it. It's not related to the new OTA or PRI for me. I've had this problem before and after root, tried different rom's, radio's, pri's etc., replaced my sdcard. I've tried many different things and can't figure it out. I've read on other forums that others are having the same problem and both Sprint and HTC know that many are having problems. Supposedly HTC is working on a fix, but can't determine what the cause is yet. The only thing I can think of is it's related to a heat issue, but have no idea.
Click to expand...
Click to collapse
Might be a hardware issue
No issues here either, i'm rooted with Fresh ROM. Sucks to hear though!
I've had them both happen intially on the 1st day but its fine now. Not sure why it did.
It overheated to 50c+. Still even at the norm, its 4c higher than the 3.26 roms which averaged at 37c, This ROM varies from 40c-42c.
Only using Celsius because I look at the (deactivated) Wifi Tether's temp gauge.
Sprint sent me out another EVO and battery.. Said it might be an issue with hardware rev 003 but hell if i know...
i had this happen twice yesterday, only when i was forcing roam though.
When my phone's temperature hits 46 Celcius it will reboot. Got to let it cool down before it work stay on. This is just surfing the internet on warm/hot summer days. Very disappointed, I am.
Related
My girlfriend's HW003 Nova EVO is in a state of random reboot. I have run out of ideas.
It is not OS dependent, meaning I have gone through 3 different ROMS including stock rooted.
There are 6 log files below. They are logcat files right before the phone kills the connection.
Knowing that the ROM is not the cause, I am down to Radio, WIMAX, GPS, WIFI, or CPU/MoBo.
I executed the gpsclrx command and it had no effect on the random reboots.
Is anyone else having the same issue? Have you exchanged your phone at a Sprint location? What have you done?
http://www.andrewdefilippis.com/uploads/Documents/Restart_1.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_2.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_3.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_4.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_5.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_6.txt
Sent from my HTC EVO via XDA App
003 / Nova
I have some random reboots as well, thought it was related to temp but after a while that seems to not be the case. Happens on every ROM and seems to happen 9/10 times when browsing. Stock Browser / Dolphin HD. Reason I thought it was a temp thing was I started noticing a light spot on the screen, evidently above the processor, and so I figured something had to be happening with it all.
Have been meaning to start calling around about it and see if it's something Sprint can replace or not. Am more than prepared to pay the deductible, but I haven't really made steps to get to the bottom of it.
It's strange because when I think I realize what is doing it, it ends up not really seeming to be the case. It all started happening when I had a bad wipe / flash (clockwork) and it started happening then. Lost my RSA Certs (not a huge thing, obviously something I'll need to address at some point but currently using CM6 so I'm not really "missing it." But that's when it all started happening. So I guess in that regard, the WiMax shouldn't necessarily be an issue ... or so I would think. Happens when on WiFi and off, happens whether GPS has even been turned on at any point or not so I figured it had to be some CPU issue but not necessarily due to heat.
Know this probably doesn't help, but I thought I'd post.
have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?
Exchange the phone?
Sent from my PC36100 using XDA App
Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC
just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.
conqu1stador said:
Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC
Click to expand...
Click to collapse
If you have setcpu installed, I need you to go to the info tab, scroll down and tell me what value is next to memtotal. It should be 425000.
Let me know what yours is.
Sent from my HTC EVO via XDA App
omegasun18 said:
have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?
Click to expand...
Click to collapse
This issue is ROM/APP independent. There is no connection to 3rd party software or os.
Sent from my HTC EVO via XDA App
No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC
lgevo said:
just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.
Click to expand...
Click to collapse
Gah, just saw this sorry for double post. Issues all starred after bad flash after bad wipe with clockwork. Using amon now, 1.7. Have yet to update to 1.8.
sent from my SUPASONIC
conqu1stador said:
No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC
Click to expand...
Click to collapse
The reason why I was asking you to check the info tab for the memtotal value, is because on my phone, currently I am not having a problem and the value is 425000kB , but on my girlfriend's phone, it registers only 424840kB.
Sent from my HTC EVO via XDA App
Alright, will look for the one on these boards.
Hate to even go here, but I really never used a logcat before; but my phone just rebooted and I went immediately into the logcat and just like when I launched it at first there is just a wealth of information. I see it says ;
D/alogcat ( 521): stopping ...
D/alogcat ( 521): resumed
Might sound dumb, but am I to assume that's the point the log stopped and began again, due to the reboot? Would think it is .... on to that setcpu I guess.
edit: seeing that stopping and resuming in multiple spaces, guess that's not it. =/
setCPU - memtotal; 424828 kB
conqu1stador said:
setCPU - memtotal; 424828 kB
Click to expand...
Click to collapse
Alright. I need more people with HW003 Nova EVOs to check the same, and say if they are having reboots. This could be corrupted or bad memory.
Sent from my HTC EVO via XDA App
i have hw 02 but my memtotal is 424832... does that matter?
????
i have hw 02 but my memtotal is 424832... does that matter?
I think this may be a HARDWARE issue...
Hello xda folks,
Long time reader, first time posting...
I'll try and condense this down, everytime I try to post something xda says I'm not logged in, so I'm keeping it short out of re-writing frustration.
I'm HW003, I lack setcpu, so I can't really check my memtotal, but I believe that in short the flash mem/nand memory may be getting damaged or corrupted by flashaholics like myself. I'm curious to see in any non-root users have experienced the completely random reboots like some of us here.
Let me be clear about one thing, I'm describing random rebooting, not consistent bootloops, at least they weren't at first.
Initially, I thought this problem was a byproduct of OC'ing, or overheating the unit, but I have flashed every combination of rom, kernel, OC/stock, hboot ver, etc, virtually anything I have some control over, and the phone still reboots. Ive even rolled back to stock unrooted, and tried bone stock 2.2 but the phone keeps throwing a fit.
Everything on this phone hardware wise screams "I was manufactured on the cheap, and put out to stores on the quick", so it stands to reason there is some kind of failure taking place.
I'm no expert, but I've flashed this thing A LOT. Probably around 100 times.
It also seems to be getting worse, as it often sticks in bootloops now, not just random reboots. Causing me to have to flash it on an even more arbitrary basis!
Next step for me, is rolling back to stock 2.2{Again}, and sending this bad boy back to where it came from, and wait for my POS replacement and its new set of shenanigans. I will root the new one once, pick one rom, and flash it once...
It will be difficult, but I will be attending Flashaholics Anonymous.
We can do this together.
Anyone have a more logical answer?
I honestly cannot find the cause of this. I Have tried everything in my power to try to fix this problem but absolutely nothing seems to work. When using my phone regularly (only on froyo) my phone will get very very hot and then start a reboot loop where it keeps rebooting and rebooting and rebooting. I have the official 2.2 update. Currently not rooted but S-OFF. I wanted to see if the root was causing any problems but im still getting the reboots. I Love my Inc. and i love the AMOLED screen. I want to be able to fix this problem so i dont get stuck with a ****ty replacement. PLEEZ HELP MEEZ
first thing would be to tell everyone what ROM you're on and if you're running setCPU.
Sent from my ADR6300 using XDA App
mzmartipants said:
first thing would be to tell everyone what ROM you're on and if you're running setCPU.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
He said that he is using the stock ota update already
But if your using setcpu this is a great time to stop
Sent from my ADR6300 using XDA App
nope im running completely stock no rooting apps
I get them everyone in awhile when I recieve a text message in the background. Like if I'm in foursquare, or the internet browser for example. And recieve a text, it'll lock up and restart, sometimes it doesn't clear my uptime which is weird...
Sooooo no one can help?
Sent from my ADR6300 using XDA App
Pleez
Sent from my ADR6300 using XDA App
I get this problem all of the time and I will tell you it has nothing to do with root. In fact, I'm not sure it is even a software issue. I have done multiple factory resets to try to troubleshoot the problem.
There is a thread at AndroidForums about it that I am currently running, but I can't link to it evidently. Look in the Support section for the Incredible.
How did you update? You're running a 2.xx radio, right?
If your problems are surviving a full wipe + RUU, the most likely culprit is that your hardware is failing.
It's a full wipe stock 2.2 and yes I have the newest radio
I was having the same issue with my phone on Stock 2.1, Stock 2.2, custom ROMs, etc. No software updates/configurations would make the random reboots stop. Anything that taxed the CPU seemed to cause my reboots. The easiest way to reproduce was to just start GPS'ing somewhere. Within minutes, the phone would go into a reboot loop that would usually only stop after a battery pull.
I took the phone into VZW while it was doing a reboot loop, showed it to them, and they put in a replacement order for me. The replacement (yes, it's a refurb) has been rock solid over a few days of heavy use. I read that if you had an AMOLED screen, then you're replacement will also be AMOLED.
tl;dr; - random reboots on stock ROM with no mods is probably a hardware failure. Go with a refurb.
Decided to go to VZW and order a replacement. They told me it would be a new phone and not a refurb but I don't trust them. Anyways it comes Thursday. I shall report back my friends. I still find this problem to be so odd
Well ive been having serious issues with my evo, i swore it was the kernels i been using, but now its constant, ive restored a nandroid, flashed different roms and kernels, and same thing happens, phone boots, but as soon as it gets to home screen it reboots, ive done it all, wiped data, reflashed, u name it, it has to be something physically wrong with the phone.
what should i do from here?
should i flash the newest stock rooted 3.30 OR should i just use the stock unrooted one for when i go into the store?
there was a thread started about this. a lot of people are experiencing it, i would imagine its software related.
intheb0x said:
Well ive been having serious issues with my evo, i swore it was the kernels i been using, but now its constant, ive restored a nandroid, flashed different roms and kernels, and same thing happens, phone boots, but as soon as it gets to home screen it reboots, ive done it all, wiped data, reflashed, u name it, it has to be something physically wrong with the phone.
what should i do from here?
should i flash the newest stock rooted 3.30 OR should i just use the stock unrooted one for when i go into the store?
Click to expand...
Click to collapse
I was having the same issues. I unrooted and took it in to Sprint. They gave me their only refurb on hand as a replacement.
It was a pretty easy process of proving that it would happen any time.
Sent from my PC36100 using XDA App
Pretty common problem. Do what the last poster did.
Same thing just started happening to me. I thought it was the 2.3.4 nightlies, but maybe not... Has anyone came up with a different solution? FYI, I found when I can't get it it boot, putting it in the freezer for a while works. Seriously.
Hello,
I had random reboot before with my leedroid 2.3b, and I had one also 30 minutes ago with AuraxTSense, so I'm asking if the cause is the rom or not.
When he reboot, he's not hot, I see it reboot sometimes and the phone was at normal temperature (approximately with my hands lol). it reboots max 1 time per day.
So I'm tellng myself that's it could be due to:
- radio
- S-OFF
- one app
For radio, I try tu update from 32.48.00.32U_5.11.05.14 to 32.47.00.32U_5.10.05.23, and I'll see.
For apps, the problem is that I would have not to restore all my apps, to see if one app cause it.
What do you think of it?
Thanks
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
Or as fnotsje said, could be hardware related
fnotsje said:
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Click to expand...
Click to collapse
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
eden2812 said:
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
It's installed but not configured in smatass mode, you advise me to uninstall it and to test?
Or as fnotsje said, could be hardware related
Click to expand...
Click to collapse
What is surprising, that if it's that, i t should reboot many more times than one time per day no?
Thanks
thierry_b said:
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
Click to expand...
Click to collapse
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
fnotsje said:
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
Click to expand...
Click to collapse
Yes and always only one time per day, just one time maybe 2.
I desinstalled SetCPU, it changes nothing.
What do you advise me to do?
Wipe and install minimum apps, and see if I've that, and little by lttile, reinstall one new app...test few days again...?, it will be long :-(
Thanks.
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
GoogleJelly said:
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
Click to expand...
Click to collapse
With the minimum of apps, for example to see if it reboot or not?
Because if t's an hardware problem due to the radio, it censed to reboot even with few apps no?
For carrier as I'm at Orange like you, I think, they could change fastly my phone maybe. I will try that if anything works. You think that if I do that, I've to find an orange rom? I'm asking myself if they accept an HTC even restored with RUU.
Thanks
I have the same issue and ITS DRIVING ME MAD!!!!!!!!!!!!
I never experienced this with my stock ROM... so I firstly tried a gingerbread ROM... when it started... i then moved to a Sense Rom and still reboots occured... I'm now on my 2nd cooked sense ROM and still having reboots!!
WTF? is there a quick sollution?
thank you!
SO MANY follks seem to be having problems with [email protected]! Is there seriously no sollution to this or a common cause..?
had the same problem & is with HTC getting fixed
there are a few posts about it if you search - the only fix seems to be to send it to HTC for a new motherboard as some presume that it's overheating.
11 march still waiting on return of my Desire
I can relate to your issues. Mine kept rebooting when I tried to use the GPS. Like you I had mine rooted, S-off and was using a custom ROM.
After many tests, I downloaded a stock RUU, installed a different navigation app and once again, it rebooted.
Bottom Line: take it back. Its probably defective. Just make sure you're running a stock ROM. Download an RUU.
Ok, I'm finally reporting this Uber annoying problem.
My phone will just lock up for anywhere between 2 and 15 seconds. I thought this was maybe a bad backup from titanium, so I stopped using it. I cleared my SD card, I've tried multiple roms, I'm formatted everything including SYSTEM during each different ROM install.
It seems the issue happens after I use SMSBACKUP+ to restore my txt messages. *EDIT But I've had it happen without installing SMSBACKUP+ EDIT* Handcent has been force closing on me for weeks as well. I just removed Handcent, and installed ChompSMS. The problem is still happening.
It happens very randomly, and without any cause that I can tell. I'll hit the power button, and unlock the screen, and then the touchscreen is completely unresponsive for seconds at a time. The touch buttons (home,back,etc) are also unresponsive. Then all the sudden, the phone will try to catch up to every one of my touchs.
Also, whatever it is is killing my battery. Yesterday I installed MikFroyo, and the phone was good for over 12-15 hours. Then I charged it, and something in the past 2 hours caused the issue and completely drained my battery in those 2 hours.
I've had this problem with
FreshEVO (multiple versions)
SprintLovers
Burnt Droid (multiple versions)
Ava-Froyo
OMJ's EVO
BakedSnack
I've also tried ASOP mods like MIUI and Cyanongen Mod, and as far as I can remember, the problem didn't happen with them, but I really would like to have my 4g work.
I just want my phone back!!!!
Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.
First backup your apps and data. Then flash calkulins format all, then flash your rom and start from there it should work
Sent from my PC36100 using XDA App
I've been using calkulins format all for the past 2 weeks (7 flashs)
teh roxxorz said:
Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.
Click to expand...
Click to collapse
I've used every kernel I could get my hands on, thinking it was the problem. I've been using stock kernels for the past 2 months now with the same problems.
I just haven't heard anything else bad about SMSBACKUP+, but I have read some issues with locking up, freezing etc regarding SMS in general.
Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App
davidc23 said:
Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Been there, done that about 50 times too. I'm just gonna go without HandCent for a few days and a new ROM install and see what happens.
Have you had any other complaints about this?
None, what's your hardware version
Sent from my PC36100 using XDA App
davidc23 said:
None, what's your hardware version
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Current
HW: 0003
MikFroYo 4.5
2.6.32-17-gee557fd [email protected] #15
3.70.651.1
Are u using setcpu
Sent from my PC36100 using XDA App
Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
EDIT: Also, what PRI version and Radio/baseband version do you currently have? The latest? 1.90 PRI and 2.15.00.11.19? If you are on the 1.90 PRI, try downgrading it to the 1.77. The 1.90 PRI is definitely known to cause issues that you speak of on some phones. Just anothing thing to double check. Here is an attatchment of the 1.77 PRI. It sounds like you don't have anything to lose by trying. Everyone's phone acts differently with different software and what not.
davidc23 said:
Are u using setcpu
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Nope... Complete stock roms, with little to no apps. I can only think to point at bad hardware, the base sms operation, smsbackup+, handcent, or titanium backup. All of which I'd had issues without one or the other installed.
k2buckley said:
Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
Click to expand...
Click to collapse
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.
4g still scans
Sent from my PC36100 using XDA App
mintee said:
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.
Click to expand...
Click to collapse
Check the Edit in my previous post as well
k2buckley said:
Check the Edit in my previous post as well
Click to expand...
Click to collapse
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.
mintee said:
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.
Click to expand...
Click to collapse
Dang!! That's an old radio / pri combo! I've never rolled back that far, so can't say much about it, but are you sure that's not contributing to the issue? Maybe it doesn't like the 3.70 build.
Sent from my PC36100 using XDA App