My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App
The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...
SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?
I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.
I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.
Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..
Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...
I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.
This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.
And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...
I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?
Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.
I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.
Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.
Hi,
I Recently updated my HTC Desire S for the new version 2.10.401.5, with Android 2.3.5 and Sense 3.0.
I still have the stock rom and S-ON, the update run without problems, every thing works ok but i found a little big problem.
When my phone lost ratio signal for a couple of secons he doesn't recover it , i need put the phone in plane mode on and off to restart the connection.
This is really bad because on my work station a have low signal for my phone operator
Any one can help please ?
Regars
Have you tried reformatting your phone? Restore factory default? I suggest you to make a clean setup to your phone.
If that doesn't helps, it would probably your carrier problem, try contacting them. That's all I can help you here.
i think its prblem with latest radio..i had problems with wifi..or maybe is just carrier as nodeffect suggest
Hello i have a big problem.
Since i updated my HTC HD7 to the last update available i received it yesterday in Portugal , i have to take off the battery and reboot my phone because my phone losts wi fi conection and freezes many times!!! this is anoying! for example y already reseted my phone and to install all the apps i had installed from Marketplace i had to reboot 15 times because wi-fi stoped working or phone freezed !
anyone knows what is going on and can help please?
Thank you very much!
in your signature it says your using the NextGen Rom? actually my phone started freezing on me after installing the latest next gen.. however ive gone back to the original TMOUS rom and i still get the locking up and freezing. if fanct it doesnt matter which rom i switch to the freezing is still there. i have been unable to find any information as the freezing seems to be completly random. but ive had my HD7 for just about a year and havent had any of these problems until i flashed NextGen.. i wonder if its just a coinceidence??
Things tried:
Flashing to Stock Rom - Fail
Flashing to stock rom and getting updates up to the latest - Fail
Tried Several Different Radios - Fail
Tried other custom roms - Seemes to be worse on custom roms? -Big Fail
Tried low level format of sdcard - Fail
replaced sd card - Fail
Cleaned phone cuz ya never know - Fail
the freezing also seems to be completly random. but is more common when recieving calls. and manually using the power buton to lock and unlock the phone.
im not sure if any of your problems are similar to mine.
Hello!
My problems are exactly like yours!!! and they begun some time before i installed nextgen, i installed nextgen because i thoght it was a rom problem
I have a gess that is a problem with the battery a already bought two new batteryes from ebay i will let you know if that solved my problems
finaly i resolved my issue it was a radio problem!!! just that! i flashed the Radio_5.69.09.29a_22.50.50.21 and everything is working fine nowww!!!
Hey Guys!!!
I just wanna know the solution for this......
I am running RunnyRom 7.02 in my Desire.The problem is whenever I install Custom ROM on my Desire it often when down to off.I just can't switch ON my device. except. I have to pull out the Battery and put back in for switching ON the Device.This thing couldn't happen when i ran Official Stock GB 2.33.Some people suggested me to change Sleep and Wake voltages MIN and Max level in Demon Controller. I tried this but No use.I cant understand where is the problem.I already used SenseEvolution and Runnymade ROMs before, this is the same problem forced me to go back to official Rom.I am not willing to stuck into it. i am willing to use this ROM as my Daily Drive. But this thing is frustrating me...Can anyone Help me to get out this thing..............??????
HINT:I changed different Kernals also like snq,baandwaz,droidzone.I changed my Network mode into GSM only mode.....:fingers-crossed:c
My device Details
HTC Desire with S-Off (used Revolutionary)
Stock HBOOT A2SD
Radio-32.56.00.32U_5.17.05.23
GingerBread 2.3.5 with Sense 3.5 (RunnyRom)
Transcend 8GB( Fat32+EXT4)
Hi,
i happened to update my os to the 4.4 kitkat cm version and i am just getting a light blue screen with some purple stuff in it, right after the htc logo. Same thing happens with the Beanstalk version, but the colors are a bit different.
After going back to the cm 10.3 version it all works fine, except that my sim card aint beeing recognized no more .
So how come i cant get the kitkat versions to work ? got the 2.15 hboot gapps and did all kind of resets before updating.
Hoping for some help
Ok, that no problem thing was a lie cant get my sim card to work, even though it workes with no problems before those updating and i didnt change anything hardware wise.
Solved: ok i thought i had a s-off device, turns out i dont so flashing the boot.img fixed the problems