Database Info

Taking the risk of GB radiofor the sake of science.

Just talked to a friend from vzw, he told me that if something happened he will hook me up with a replacement for my tbolt.
I've been using gb radio since the 1st day it was leaked, i have no problems on my phone, just some random FCs but that's given.
Since we don't have a solid demographics on how many people got bricked, Im going to take the risk and see if i get bricked.
This morning i just got into a bootloop but looks like its just the battery giving false stats. Its been more than 6 hours now in my external charger and i assume battery doesn't hold charge anymore, Im going tommorow to vzw to have it replaced.
Question is, will logcat be enough to monitor my phone in case i got bricked so i can pull some important data regarding how it happen?, that way we can find a clue on how to fix a radio-bricked tbolt.

Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App

Wow. Very cool that you're willing to do this. Looking forward to seeing what you find out.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
From what I've read, that's not possible as the bootloop happens even booting into recovery.

kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yes i have cleared my battery stats. My previous battery is now dead. I think i discharged it too much, now its not holding any charge. My phone still runs on gb bamf and loving my lockscreen. Will let you know if i get bricked.
Sent from my ADR6400L using XDA App

i too am sticking it through, im too in love with this to revert back.

yakitori2 said:
kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.
Click to expand...
Click to collapse
Lol you obviously didn't read his post. No risk involved.

I hope someone could shed a light to my questions.
1st. How does the radio firmware work on our phone? Does it work like a driver where it acts a mediator between the roms(software) to the phone's hardware.
2nd. What are the possible trigger to recreate the bootloop of death? There are some cases that my phone overheats because of non responsive apps and ever since i flashed on GB rom there i times i can feel my phone hot, which could be the case from some of the boot loop victim that they fried something inside their phone.
3rd. What are the chances that same bootloop of death could also occur in froyo radio? Just because vzw officially released the radio doesn't mean it has same risk like the leaked GB radio. It is like how HTC manufactured the phone, they tested most of it but some are still lemons.
Everything is in theory right now, there are no fix because it happens in random and the reason is still unknown. I'd choose to participate for the fix instead of waiting for someone to figure out the fix. We all do take a bold step in rooting our phone, flashing different roms, putting our faith on the battery that it wouldn't fail during the flashing process. Once we modified our phone from its stock settings we acknowledge the risk, and that risk is the one of the few factors the fuels the development of the rom/kernel community.
I've noticed several repacks of the GB radio:
http://www.multiupload.com/HU471CMQI0 ----
MD5: EE2A824E51CB148A2256F93E30A3B9F9
http://www.worldofjohnboy.com/dhemke17/ROMFiles/PG05IMGGB.zip ---- MD5: fda2a314975dd829b4e3611ecc8cfa13
PG05IMG_gingerradio.zip <- from http://forum.xda-developers.com/showthread.php?t=1082001 links alread removed. This is the same radio from androidpolice.com----
MD5: 52DD83AA40E30186C9FBEFAFD1BAB534
For the record, i flashed mine with the MD5: EE2A824E51CB148A2256F93E30A3B9F9
right now im using das bamf 2.0-5 running on imoseyon_leanKernel_v2.5.4GBtest6
Im keeping a close watch on my temp running on "extreme settings" 1.4ghz extremely undervolt.
SetCPU profile set to minimum setting when temp goes more than 97F

I just called verizon 611. My phone is not bricked and still functioning properly, but i told the operator that my phone constantly reboots( I pretended that my phone was bricked), i was passed to higher level tier support and they said they will be sending a new phone to me and there will be an extra envelop where i need to put my old phone to return to them. The call only took me 10-15 minutes and I believe VZW is aware that Tbolt has this issue even if its GB or the stock froyo rom.

i reverted back last night but i will def be back once things are more stable.. i already miss it

S.o.d(screen of death)

So I just got my g2x, rooted,nv and cwm. Flashed cm7 and I keep getting s.o.d(screen of death). I thought was rom problem so I.changed rom and im on xdblasters 1.1.0 and keep on getting them. Any solution orhelp would be appreciated.
Sent from my LG-P999 using XDA App

Not sure I know of a rom for g2x called xdblasters.
Also, what kernal are you using? Are you overclocking or undervolting? Are you using setcpu or pimpmycpu? What is your max and min cpu settings? When you flashed, what was your procedure for wiping? Did you fix permissions after flashing? Did you use a program to restore apps? Did you use that program to restore system settings? Did you choose to restore apps and settings from google account?
The answers to all of these questions could help determine what you've got going on.

I apologize, its x boarders. And well I am using fauxs newest kernel currently using 1.1 overclock but it would also happen while at stock cpu with previous rom.i don't restore with google but I use titanium backup for batch. When I do new roms I always follow the clean slate rule;Wipe data,cache,dalvik,bat stats. occasionally I forget fixing permissions but I do when I get alot of force closes.
Sent from my LG-P999 using XDA App

I didnt' see you mention formatting /system under mounts and storage. This is a critical step.
If it were me, I would try to keep everything as basic as I could each step of the way so that i could try to pinpoint the issue. Start by wiping everything (including sd card...just backup your user added stuff to your pc) and install a stock rom/kernal. See if it occurs stock...who knows? It's possible your phone is bad. Then if it doesn't misbehave with stock, then I would wipe everything again, including sd cards (interal and external), and flash cm7 (keeping cm7 kernal). I would try manually installing apps again, rather than using titanium backup or google restore. Just hook up to wi-fi (so you don't waste your data mileage) and go to market/myapps and redownload (hopefully you have a list of what you have).
But something to point out. On my phone, when I use CM7 (with stock kernal), I have to increase my minimum cpu frequency to either 312 or 456 instead of the default 216....216 seems to cause my phone to get stuck with the black screen also. The same thing happens when I run an undervolt kernal. So I've learned that my phone simply doesn't like undervolting, overclocking, or lettign the cpu run lower than 400MHz. Maybe that might help you out.

i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate

what should my mounts look like when i do a system format?

thrashingdeth said:
i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate
Click to expand...
Click to collapse
I just traded my sensation for a g2x off CL, sure glad mines had no reboots or sod, actually the best g2x if had out of my 4..

Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App

thrashingdeth said:
Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Awesome, hope it stays good.

guess i spoke to soon. Was running fine all day till around 2 i installed setcpu and configured it. Or so i think, so i uninstalled and reset but when i am charging it it keeps turning off. AHHHH headache with this phone. When it runs, its smooth and so fast, i love it, but i dont know whats wrong with it.

I think I'm done with this. Can't figure out a away around this. Awesome phone but overwhelming problems. Appreciate the help everybody.
Sent from my LG-P999 using XDA App

have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.

Black6spdZ said:
have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.
Click to expand...
Click to collapse
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App

What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?

I always fully charge and discharge battery for proper calibration. Doesn't seem to be helping in any matter. I also stopped using any CPU management because I thought that was.
bshakil said:
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

The problem is when phone sleeps and doesn't wake up. I have not pulled one, been thinking its hardware related.
AdamHart612 said:
What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

Only happened. Twice today. Bahamas improvement I guess.
Sent from my LG-P999 using XDA App

Its hardware defect. No matter what ROM you put on the phone, it will continue. Youve gotta call TMO and get a replacement. Sorry if thats not what you wanted to hear.

I agree with the battery theory. I purchased two generic batteries from ebay and they last 3 times as long and have resolved many of the resetting and SOD issues that I was having. Also, updated ROMS seemed to help, and not letting it fall asleep while you are playing games or something memory intensive.

Well I bought a battery, hoping that helps a bit. So far its a lil better than usual. Using stock voltage kernel. When I get new battery I will test
Sent from my LG-P999 using XDA App

[Q] Anyone have success fixing restart issues?

I've had my G2X for about a month, and have been experiencing the common issue where my phone randomly shuts off and the only way to get it to turn back on is to pull the battery.
I've installed the GB update, that didn't fix it. Factory reset didn't help either.
Has anyone successfully fixed this issue on their phone? If so, what'd you do? Is there any chance that rooting my phone would correct the problem?
Sorry if there was a post about this, I couldn't find anything talking about if anyone's been able to fix the problem.
Thanks

yes... the onlyhh way to fix the problem is to root! nvflash clock work mod recovery, then flash eagle blood 2.3.3 rom and it is perfect...

Thanks, this did indeed seems to do the trick. Not a single reboot so far after 2.5 days.
Sent from my LG-P999 using XDA App

My G2X actually restarted on its own today. It was the first time since the first few days I had the phone over a month-month and a half ago. Wasn't really a big deal, lol. It comes back on.

Have been playing with this phone for 3 days now and haven't had any issues (I did install xboarder's stock rooted version). Minor screen bleed is the only issue.
Sent from my LG-P999 using XDA Premium App

Finally, someone (dmaniscool) who can say they switched to an xda dev'ed ROM and got rid of the lock ups. I've posted many times asking if anybody ACTUALLY FIXED a problem (specifically the battery pull lock up); I got no responses, and someone finally stated it. Great. Next time my wife's G2x locks up, I'm rooting and putting a ROM on it.
Thank you dmaniscool
-Bob

so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob

namklak said:
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
Click to expand...
Click to collapse
Will do, so far so good! I had no experience with rooting, and was able to figure it out looking at the guides available on the forum. It kind of looks intimidating, but it's not actually very difficult.

By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App

RZJZA80 said:
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine did both actually, shut down and restarts. But mostly just shut downs, which required a battery pull to power back on.

My 2 will do both - but I think the "shut-off" is a lock up, because the longer I leave it locked up, the less battery I'll have after I do a battery pull.
8 days of both phones not locking up by doing one restart per day per phone.

Since I raised the minimum CPU speed to 389 from 216, I have far fewer sleeps of death
You don't wanna know where this was sent from.

I've tried every ROM and kernel combination possible and nothing actually fixes these problems for me.

Wow this post was scary at first, I had a thunderbolt and no matter what. RUU, Different ROMS, Stock, Kernels, Radios. Changing all that didn't matter it still turns off constantly and doesn't turn back on till I do it meaning no text or calls, basically same as having a phone on silent all the time without even having the luck chance of pulling it out while ringing.....

I am on miui x.26 (whatever kernal that comes with it) and have over 40 hours of uptime. I haven't had a crash yet, I just manually restart every couple of days because I'm weird like that.
Sent from my LG-P999

Well 6 days into it and I've had a total of 2 shutdowns. I don't know if it was a coincidence, but both times were after being outside when it was ~90 degrees out.
This is still much improved, I used to get 3-4 per day on average.
I'm using Eaglesblood 2.3.3. I'm thinking of trying MIUI because it's so nice looking.

For me I did a battery replacement the first time directly from T-Mobile and the phone continued restarting on me. I was just about to request a replacement phone from T-Mobile until I recently purchased a different brand of battery containing the same specs as the stock battery and to my surprise no overheating and definitely no restarts. I feel that the restarts and lockups are due to faulty batteries shipped out with the phones. I'm suprised no one has mentioned this.
Sent from my LG-P999 using Tapatalk

Do you mind sharing what brand battery you purchased?
Sent from my LG-P999 using XDA App

Wow, I told the CostCo kiosk girl I was having lock up problems and I had my grandkids with me. She took my phone and pulled the battery - at the same time my grandson stated he had to go to the bathroom NOW. She either looked at the battery or something on the phone under the battery. I didn't have time to ask. She didn't really comment and gave me my phone back.
Hmmmmmm........
-Bob

ok so do they know what exactly is causing the shut downs or reboot on this phone? i just got mine today and it was pre installed with gingerbread and idk if there is root for the gingerbread build yet. i just want root but no custom rom for me. i love the stock rom. it kicked the crap out of my sensation 4g as far as speed goes in everyday use.

[Q] HTC Sensation Keeps Shutting Off by Itself

A very good day to everyone.
I have been using my HTC Sensation for a year and a half already and recently it's starting to crank up.
It started last week when I was using my phone when suddenly it just switched off by itself and no matter how I attempted to switch it back on again it would boot up to the lock screen page and baam, it shuts off again. It doesn't restarts by itself or anything, it just simply switches off and no, I am unable to switch it on again. The only time I am able to do so again is when I plug it into a power source, that is when it would finally be able to start up.
At first I thought that it wasn't something big until recently it started occuring more frequently and I noticed that it only occurs whenever I have my 3G switched on. If I'm plugged in, my phone would still be working without switching off even though I have my 3G switched on. But when I unplug it from its power source, I'll be able to use it with 3G on for a good 20-30mins or even lesser at times and there it goes shutting off by itself again. What actually got me dumbfounded is how I can be having 80% of battery power when this happens.
I have tried the using a card/paper as a wedge for the battery so that it connects better but to no avail even though I have noticed that indeed, my battery seems to have some extra allowance for it to fidget about within the confinements of the spot which is allocated for the battery. I have tried the switching the phone's data usage to GSM only as well as switching it to WCDMA only but both still didn't work. I have also done a factory wipe which didn't work, super wiped it before flashing ARHD once again which didn't work as well.
To make things worse, my phone is not covered under warranty anymore and my only last hope is that the problem lies with my phone's battery rather than the PCB board which is why I'm putting all my hope on the Anker battery which stocks would only come in next Monday which I don't wanna spend on only to find out that it's not gonna be able to save my phone from its miserable plight...
This is my phone's setup:
Android Version 4.0.3
Sense Version 3.6
Software Number - Android Revolution HD 6.8.0 XE by mik1986
Kernel Version - 3.0.16-g31a4fc7 [email protected] #1 SMP PREEMPT
Baseband Version - 11.76A.3504.00P_11.24A.3504.31_M
I'm really desperate to find a solution to this so if there's anyone of you who has faced this issue/solved this issue please enlighten me as to what I can do, any/all help would be greatly appreciated.

Try other Roms..yrs might be unstable...
Sent from my HTC Sensation XE with Beats using xda-titanium app

I've tried other ROMS already but it still force shuts itself whenever my phone's 3G is switched on. Any solutions?

seems like a radio problem ..reflash the firmware you are having or ..flash 3.33/3.32 universal firmware from kohr-ah firmware thread in sensation development section
once done ..get getril app ..open it and flash proper ril for the firmware if you not having matching ril

I've been using the 3.33 firmware for quite a while already but it's still not working. :/

Sorrowed said:
I've been using the 3.33 firmware for quite a while already but it's still not working. :/
Click to expand...
Click to collapse
Reflash it and see ...
Sent from my Nexus 7 using xda premium

ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.

I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon

It would help a lot of we had your last_kmsg file. To get the file, you can use this app: https://play.google.com/store/apps/details?id=net.solarnz.apps.lumberjack. Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it

ganeshp said:
Reflash it and see ...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried reflashing the 3.33 firmware but it keeps telling me that the installation has been aborted.
Skipjacks said:
I'd add to that to reflash it using a fresh download of the firmware file. It's possible (though slightly unlikely) that you have a tiny corruption of your existing firmware file so reflashing it might just put the same error back. I say that's unlikely because errors in the radio file of firmware would likely be causing you bigger problems than you are saying. But a new download and fresh flash won't hurt.
Or try switching to the 3.32 firmware (They aren't much different) just to see if it makes a difference. If not you can at least rule that out.
Just a head's up though, after you flash a new firmware file, reboot into recovery and wipe cache and dalvik or you will likely just get a bootloop at the boot animation when trying to start it the first time.
Click to expand...
Click to collapse
I've tried this method of yours as well but apparently it tells me the same thing when I try to flash the firmware. "Installation aborted" and I don't know why is this happening...
stanix.de said:
I had the same problem - the battery was broken, had to buy a new one, search for "Anker" on amazon
Click to expand...
Click to collapse
I've found a seller over here in my country who I'm going to be meeting tomorrow and finally test it out as to whether has it been my battery's problem or is it just my hardware being faulty. Will test it out and let you know of the end results, thanks mate!
android1234567 said:
It would help a lot of we had your last_kmsg file. To get the file, you can use this app: LumberJack(Had to change due to my account lacking the minimum requirement of 10 posts before I can post a link) Get the last_kmsg file RIGHT AFTER your phone shuts down and turns back on so we can see what made it shut down. Then, attach the file to your first post so we can see it
Click to expand...
Click to collapse
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?

Sorrowed said:
But after it shuts down I have to connect it to a charger before I can switch it on again, would that affect the log?
Click to expand...
Click to collapse
No, it would not.

Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.

Sorrowed said:
Thanks for all the help guys, got myself a new Anker battery and apparently that seems to have solved the problem so far... It has yet to shut off on me or anything for the past 6 hours with my 3G switched on throughout.
Click to expand...
Click to collapse
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:

TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
Definitely! Thank goodness it was just the battery otherwise there goes a great phone. Not to mention that with the anker battery it has a greater and better lifespan!

TTime_007 said:
Same here! Just got mine today.. Had axactly the same problems! No shutdowns so far! Mine was also 1.5 years old! Happy it was only the battery!:laugh:
Click to expand...
Click to collapse
My situation is identical to yours. 1,5 years old, constantly rebooting, after reboot the battery power drops to 4%. If it's connected to the power cord it works normally. Already ordered Anker battery and I'll see what happens.
If I look closely, I can see that my battery is a little bloated and not completely flat. Did anybody else noticed that?
So I guess all of this should be written on HTC Sensation FAQ page since it's not a bug, but a feature...

Senstaion Keeps Turning off?

Phone keep randomly turning off, even with a full charge? Tried different Roms, but nothing changes? New battery doesn't do the trick? Me too, until I found a post on a Vodaphone site that said that multiple copies of HTC Sense was to blame, and that if you go into SETTINGS, then APPS, then select the ALL tab, scroll down to HTC SENSE and Disable the oldest one, then reboot, all my problems would be solved.....
And they have
Hope this helps somebody else and hope it's easier to find than the original post

Another thing that may be the culprit is that the battery is not connecting to the pins correctly. In which case a piece of paper can do the trick! Just lodge it above the battery so that it presses it firmly down onto the pins and you should see no more reboots!
Did the trick for me on several occasions

Did the pack the battery thing at first, and it did seem to work until I upgraded the battery to an Anker.....
Also, ROFL at my spelling mistake in the title. Was definately meant to say Sensation :nod:

XR33 said:
Phone keep randomly turning off, even with a full charge? Tried different Roms, but nothing changes? New battery doesn't do the trick? Me too, until I found a post on a Vodaphone site that said that multiple copies of HTC Sense was to blame, and that if you go into SETTINGS, then APPS, then select the ALL tab, scroll down to HTC SENSE and Disable the oldest one, then reboot, all my problems would be solved.....
And they have
Hope this helps somebody else and hope it's easier to find than the original post
Click to expand...
Click to collapse
Disabled it, see how it works.
Can you link to the original post on the Vodafone site?
Thanks

mardum said:
Disabled it, see how it works.
Can you link to the original post on the Vodafone site?
Thanks
Click to expand...
Click to collapse
Took some finding the second time round too lol - http://forum.vodafone.co.uk/t5/HTC/HTC-Sensation-crashing-constantly/td-p/1163449
Post 9 :thumbs:

Anyway, i disabled it since yesterday.
Everything fine so far.

Just had a random restart, the first one since I disabled old sense.
ARHD 7.3 stock kernel.
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 4 Beta

Had a couple more today.
Don't think disabling old htc sense does the trick bro

mardum said:
Had a couple more today.
Don't think disabling old htc sense does the trick bro
Click to expand...
Click to collapse
Only had two shutdowns in the last week and both those were after long gaming sessions in the mornings. That's quite an improvement compared to the 7 or 8 I was getting a day. Sorry it hasn't worked for you though.

Had a few more today too.
I am desperate and willing to try anything.
Maybe, I'll enable it and compare to how it was before.
I should probably get another phone (one S, one mini)

My brother has this problem as well. If you find a fix please tell me.
Sent from my HTC Sensation using xda app-developers app

Randomly restarting of Sensation it's Snapdragon problem, not software. Sometime it's PowerManager IC problem, but then You should see problem with battery level. Once- it's full, and while ago -almost empty etc. Same problem is with Amaze 4G and other with same CPU.

A friend of mine just started having this issue, after upgrading ROM.
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 4 Beta

My wife's used to have constant reboots daily, stock, rooted,then soff. All rebooted. Then I tried flashing in a certain order the worked with no more reboots.
1.full wipe
2.flash firmware(only once of course)
3.boot into recovery full wipe
4.flash rom
Sent from my T-Mobile myTouch 4G using xda premium

I only flash ROM, as I don't need to flash firmware every time.
I like ARHD ROMs. It happens even when I do full wipe and it laso started happening to a friend, who didn't have this problem before, same ROM as me.

kwaku85 said:
Randomly restarting of Sensation it's Snapdragon problem, not software. Sometime it's PowerManager IC problem, but then You should see problem with battery level. Once- it's full, and while ago -almost empty etc. Same problem is with Amaze 4G and other with same CPU.
Click to expand...
Click to collapse
Anyway to fix this?
Sent from my HTC Sensation using xda app-developers app

My post says to only flash firmware once but if u flash firmware then go back to recovery you'll notice it has an error mounting a partition and to perform full wipe. Also phone doesn't boot until wiping cache and dalvik. I'm just saayong what worked for me when I thought all was lost and tried every ROM
Sent from my GT-P3110 using xda app-developers app

I tried wiping cache and dalvik without any benefit regarding restarts/turn-offs.
Anyway, depending on the ROM I am using, sometimes I get random restarts, sometimes turn offs.

Well I suggest trying the method I posted. I know sounds like it won't do much but I'm I'm telling u I had reboots like crazy everyday and once I flashed in that order it stopped COMPLETLY. So make a back up and try to start all over with firmware and everything.
Sent from my Dark Unicorn Resurrected v4.1 using xda premium

OK, I will try that.
Anyway, I was on stock kernel and now I just flashed SebastianFM, see how this works, better or worse.
I'm also thinking about trying another ROM.
//LE: with SebastianFM's Overclocked Kernel, I already had a few restarts :-\