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...
Related
After booting with the *fixed* charging issue, I opened up ROM Manager and was prompted to update to the latest version. 5.0.0.10 I believe.
**********DO NOT DO THIS UPDATE AS IT WILL KILL CHARGING**************
I only escaped because I had a spare battery from my previous Sensation that luckily had enough charge left to turn on the device.
************DO NOT UPDATE UNLESS THE DEVS SAY SO***********
You may lose the ability to charge your phone! Meaning - if it dies, the phone is dead. End of the line. The only reason I could bring my own phone back was because I had another Sensation battery that fortunately had enough juice to boot up and for me to flash the image here: http://forum.xda-developers.com/showthread.php?t=1192300
Do not make the same mistake I did or you risk a **************************************BRICK*********************************
Please do not do any updates !!!!! Koush or not, the charging issue is a very REAL threat! I tried everything and if I did not have a spare battery, I would be completely screwed right now!
i did that, and i have NO PROBLENS ...
strange
and even if you were right.. it woulndt be a brick.. there is always this option:
solution
I've had the newest version from Rom Manager for awhile now, and it works fine. Charges while off and everything. We've already got discussions on the new CWR in http://forum.xda-developers.com/showthread.php?t=1242522 and http://forum.xda-developers.com/showthread.php?t=1242942
No problems here either
I updated to v5.0.1.0 and got no problems with it. I got 3 battieries so no worries! You wont brick your phone either if you run out of juice, theres a micky mouse way to "jump starting" your dead battery posted above. You guys should really invest $15 for an external charger and anker battery from ebay. The investment is so little for piece of mind.
EtherealRemnant said:
After booting with the *fixed* charging issue, I opened up ROM Manager and was prompted to update to the latest version. 5.0.0.10 I believe.
**********DO NOT DO THIS UPDATE AS IT WILL KILL CHARGING**************
I only escaped because I had a spare battery from my previous Sensation that luckily had enough charge left to turn on the device.
************DO NOT UPDATE UNLESS THE DEVS SAY SO***********
You may lose the ability to charge your phone! Meaning - if it dies, the phone is dead. End of the line. The only reason I could bring my own phone back was because I had another Sensation battery that fortunately had enough juice to boot up and for me to flash the image here: http://forum.xda-developers.com/showthread.php?t=1192300
Do not make the same mistake I did or you risk a **************************************BRICK*********************************
Please do not do any updates !!!!! Koush or not, the charging issue is a very REAL threat! I tried everything and if I did not have a spare battery, I would be completely screwed right now!
Click to expand...
Click to collapse
No issues here either.
I think you, sir, need to get yourself a new charger
External charger? Since when would a dead battery = a brick? It's not an iPhone with internal battery that can't be removed.
You aren't even on the latest version of CWM. 5.0.1.0 is the latest and 100% stable.
Please change the thread name to something not as scary, specially when you are the only person that has that kind of issues.
Updated yesterday, charged last night with no problems.
Sent from my HTC Sensation Z710e using xda premium
Dude this is old news. I learnt the hard way. The newest version of cwm works great
Sent from my HTC Sensation 4G using XDA App
Mod needs to delete this thread.
BlackElvis79 said:
Updated yesterday, charged last night with no problems.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Some for me, yesterday update today charching...
Works great, it's ok also battery calibration...
lollo1927 said:
Some for me, yesterday update today charching...
Works great, it's ok also battery calibration...
Click to expand...
Click to collapse
I did today morning and no any trouble!
If you have some new in your phone pls charge your phone to 100% and keep on charger after you must make battery wipe across cwm your phone will work perfectly! My advise if something went wrong search the mistake inside yourself!
Sent from my HTC Sensation Z710e using XDA Premium App
I have always been afraid of upgrading after the last fiasco. I remember the problem occurred when you uncheck fastboot. But when fastboot was unchecked the phone would not charge. Knowing that fastboot is default on many ROMs, are you guys sure the issue has been resolved in the update? Did you try checking to see charging was happening when you actually uncheck the fastboot?
BlackVision said:
Well it works when when fastboot is checked. Meaning the phone actually is not off. But does the update allow charging when you uncheck fastboot?
Click to expand...
Click to collapse
Yes. To prove to yourself, pull battery put back hook up to computer and...
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
result is "charging"
bml5631 said:
Yes. To prove to yourself, pull battery put back hook up to computer and...
adb shell cat /sys/devices/platform/htc_battery/power_supply/battery/status
result is "charging"
Click to expand...
Click to collapse
You right the devs make for us the best!
Sent from my HTC Sensation Z710e using XDA Premium App
good here
I updated and charging is fine.
Same here no problem at all!
YOU NEED TO CHANGE THE TREAD TITLE
Hi my name is DloBrown and Im A nightly addict i've been sober for 1 month now ='(
vladnosferatu said:
i did that, and i have NO PROBLENS ...
strange
Click to expand...
Click to collapse
+1 I updated to 5.0.1 as well and have no charging issue.
need some help it just reboots randomly and is getting quite annoying :/
toxicpaulution said:
need some help it just reboots randomly and is getting quite annoying :/
Click to expand...
Click to collapse
With all the great info you provided I am sure someone will be able to help
well i read earlier that someone had problems with the android.process.media has stopped... thats the problem about after a minute of it pooping up my phone just resets. no need to be a **** about it
Without info you aren't going to get any good help. A rebooting phone could be caused by many issues. So far you have given us an error. This is still very little to go on. And now since you resorted to name calling I doubt you will get much help.
toxicpaulution said:
well i read earlier that someone had problems with the android.process.media has stopped... thats the problem about after a minute of it pooping up my phone just resets. no need to be a **** about it
Click to expand...
Click to collapse
That error could be cause by no less then 100 different things. Welcome to a development site. You have to provide all the needed info before we can help. With the info you gave me I would suggest to flash to a stock rom and stay there until you understand a little bit more about what your doing. I see no rom, radio, ril, mods, recovery, it flashing info at all.
zelendel said:
That error could be cause by no less then 100 different things. Welcome to a development site. You have to provide all the needed info before we can help. With the info you gave me I would suggest to flash to a stock rom and stay there until you understand a little bit more about what your doing. I see no rom, radio, ril, mods, recovery, it flashing info at all.
Click to expand...
Click to collapse
That's what i was thinking, but i was accused of flaming by a guy in the Captivate forums today, so i bit my tongue
i just flashed the absolution rom and it again crashed on me and i did wipe the cache and system before installing the custom rom.
and it reboots in the middle of typing or on standby >.< it is quite irritating to be honest
Rebooting
This is caused with a bad flash, radio/ril mismatch, and other programs that have been reinstalled from a backup. I would also suggest re-flashing to a stock rom, and see if it still does it, and if not I would look at getting a new rom. You also can reinstall the one you are running and then add the apps back one at a time to see if it is generated by them. Also I suggest going back to the dev thread and make sure you have the correct radio-ril combo. Search-Research and you will find the root cause.
toxicpaulution said:
and it reboots in the middle of typing or on standby >.< it is quite irritating to be honest
Click to expand...
Click to collapse
The absolution Rom was having some issues with battery and themes tweaks in the absolution tools. If you happened to change any of those that is probably the problem.
Random Reboot
well instead of starting a new thread I'll tap onto this one. I am also experiencing random reboots. My phone will reboot regardless if you are using it or not.The reboots can be as far apart as a couple of days or as frequent as 4 times a day. I am running a stock Gingerbread OS.(AT&T) The phone is not rooted. The phone is as stock as possible. The only apps on the phone are the ones that are pre-loaded by AT&T. I have changed the battery with a new OEM HTC battery. I replaced the SD card. I have also replaced the battery door.
Any ideas would be greatly appreciated.
Thanks
Its the battery. I had mine reboot at 96% and 48%. Replace the battery.
Sent from my Inspire 4G using xda premium
I changed the battery twice
Why are our sensations rebooting like crazy these days?At first, I thought it was just my phone,but soon realized everyone has the same issue.
No matter what ROM I install, my phone turns off randomly. Whats going on? Someone please help if they have a solution cos I am seriously beginning to hate my sensation.
It has been about a year since most sensations were bought...
That's 500 charging cycles and for some batteries that's enough
Take your battery out and see if it got swollen or some liquid oily marks are visible, or even tiny silvery cracks.. those indicate the battery is dying.
Sent from my HTC Sensation using xda premium
Raven2k said:
It has been about a year since most sensations were bought...
That's 500 charging cycles and for some batteries that's enough
Take your battery out and see if it got swollen or some liquid oily marks are visible, or even tiny silvery cracks.. those indicate the battery is dying.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Could this reboots be caused by bad radio or firmware? I am getting them too, pretty often and the story is same - different roms, nothing changed.
Have you tried This or This?
bosslabs said:
Why are our sensations rebooting like crazy these days?At first, I thought it was just my phone,but soon realized everyone has the same issue.
No matter what ROM I install, my phone turns off randomly. Whats going on? Someone please help if they have a solution cos I am seriously beginning to hate my sensation.
Click to expand...
Click to collapse
Need more information. Are you overclocking too high? Undervolting? Flashing back and forth between kernels without reverting some of the files they change? Mixing 3.32/3.33 firmwares and ROMs? Matching radio/RIL combos? Restoring old data through Titanium Backup? There's a whole bunch of stuff that could cause reboots TBH.
Have you tried running stock (firmware, kernel, ROM, radio) for a few days to see if the reboots keep coming? If they do, then it's your hardware and you should look into warranty if you still have one. If not, then it's something you're doing during your setup process.
I've just been running rooted stock ICS lately and my phone has been incredibly stable. I did get some reboots last week, but it turns out they were caused by the recent update to Google Maps. I uninstalled the updates and the problem went away.
Had mine a year and never had reboot issues!
You know what I love most about this thread?
The complete lack of usefull information like logcats, last_kmsg, and other logs as well as kernel info, firmware info, UV status/OC status.
@OP get those things then we can help more
My guess is you've updated your gmaps. Anything that uses any oart of gmaps/location service is fubared on the last update.
Thanks guys for the replies. Well as suggested I have formated my sd card,super wiped (using ARHD superwipe script) and installed the viper 1.1 ROM.So far no reboots, and I will not update google maps.Have been changing ROM's like crazy, so this must have messed up my phone. I will post logcats and other info if I get reboots now.
Again thanks for all your inputs guys, was about to throw away my phone.
Upgrade your battery to the anker battery. Its like £11 from amazon.co.uk
Sent from my HTC Sensation using xda app-developers app
8 quid, received today. Anker from Amazon UK.
Sent from my HTC Sensation using Tapatalk 2
That problem was driving me nuts every time I used maps or navigation. Uninstalled the update and all was well again.
-I updated latest Gmap and my xe reboot issue too, i use titanium backup restore to previous Gmap and problem is gone..
-Anyway it's time for me get an Anker Battery as spare...
So, my wifes phone (which is set up identical to mine, minus the apps) seems to reboot itself everyday. During the day, the phone only reboots once every now and then. Every night between 1am and 5am it reboots and goes into a boot loop. It loops 8 times and then continues normal operation and loads the OS.
To date we have tried 2 different ROMs (Elegancia and ARHD), 2 different kernels (faux and Sebastian). I have done 9 or 10 Super Wipes within the last month and wiped/formatted the SD card. I changed Ril yesterday to a matched one for the baseband and it boot looped last night.
I'm willing to do anything (but return the phone to Tmobile) as it is driving her nuts. I have a theory that one of the apps that she is downloading may be trying to do something during these times and it's malfunctioning and rebooting the phone. Especially considering it happens every night.
Are there any logging applications or fault logs that I could get to see what's going on?
Anybody have any suggestions? I was thinking of doing a Super Wipe and a generic load of Elegancia. Run for 2 days or so and see if it reboots. Afterwards load one or two apps a day until one faults out, unless somebody else can think of a better way of finding this rat in the phone.
Elegancia Sense 4.1 V2.2.0
Kernel 3.0.16-v1.5.2 SebastianFM #1 SMP PREEMPT
Baseband Version 11.76A.3504.00P_11.24A.3504.31_M
Build Number 2.31.401.5.CL90817 release-keys
Browser version WebKit/534.30
Please answer a couple questions. Is your phone S off or S on? If your s on did you flash boot image? Or enable smart flash in recovery? This is only for flashing roms with S on. Are you using 4 ext recovery?
Are you S on or S off? ? Also you can use a logcat and have someone here take a look to see what they can find.
Sent from my HTC Sensation using xda premium
realsis said:
Please answer a couple questions. Is your phone S off or S on? If your s on did you flash boot image? Or enable smart flash in recovery? This is only for flashing roms with S on. Are you using 4 ext recovery?
Are you S on or S off? ? Also you can use a logcat and have someone here take a look to see what they can find.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
S off.
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-V05.6.0.2226.00.0418
eMMC-boot
Could be a battery or under volt issue...
If it rebooted randomly it could be a battery issue check to see if battery is lose at all in it's housing if yes put a small wedge of paper on top to stabilize the battery. This will solve the issue if it's battery related. Let me know how it goes. This had solved the reboot issue for many people. I really hope it also solves your issue. Best of luck. Keep us posted.
Sent from my HTC Sensation using xda premium
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Also if your under volted at all change the CPU back to normal this under volt could cause reboots also.
Sent from my HTC Sensation using xda premium
hardball 45 said:
Could be a battery or under volt issue...
Click to expand...
Click to collapse
realsis said:
If it rebooted randomly it could be a battery issue check to see if battery is lose at all in it's housing if yes put a small wedge of paper on top to stabilize the battery. This will solve the issue if it's battery related. Let me know how it goes. This had solved the reboot issue for many people. I really hope it also solves your issue. Best of luck. Keep us posted.
Sent from my HTC Sensation using xda premium
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Also if your under volted at all change the CPU back to normal this under volt could cause reboots also.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I'm decided to run on this theory last night and put a wedge of paper on top of the battery. Unfortunately, I started rebooting an hour later. Then it dawned on me that I have an Anker aftermarket battery installed. So I'm running a test right now with the factory battery back in the phone to possibly see if the Anker was faulty. Will keep you posted.
realsis said:
Please answer a couple questions. Is your phone S off or S on? If your s on did you flash boot image? Or enable smart flash in recovery? This is only for flashing roms with S on. Are you using 4 ext recovery?
Are you S on or S off? ? Also you can use a logcat and have someone here take a look to see what they can find.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I was attempting last night to get a logcat going for hours. I downloaded 2 programs (which failed miserably), used the adb interface (system write-protected and unable to locate file) and an Android Terminal Emulator (same problem as the adb interface). Being in the technical field, I love to use logs to figure out what's wrong, but just couldn't get it to run.
Did you tried the battery fix as given by this thread?
http://forum.xda-developers.com/showthread.php?p=25387074
Sent from my HTC Sensation using xda premium
nsblum said:
I'm decided to run on this theory last night and put a wedge of paper on top of the battery. Unfortunately, I started rebooting an hour later. Then it dawned on me that I have an Anker aftermarket battery installed. So I'm running a test right now with the factory battery back in the phone to possibly see if the Anker was faulty. Will keep you posted.
Click to expand...
Click to collapse
ganeshp said:
Did you tried the battery fix as given by this thread?
http://forum.xda-developers.com/showthread.php?p=25387074
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Yes. I tried that already.
Is the phone plugged into a charger whenever you see the bootloops? And if so, have you tried plugging it in with another charger? It could be as simple as the USB cord not playing nice with the phone. Because for me, I have a Seidio dock which does not like to be touched when docked/charging and does a double click on the screen. Meaning if I wanted to check email, the touch would register down towards the lower part of the screen. I think there is a grounding issue with the dock, but it doesn't negatively affect the use of the phone off the dock in my case. I just use the dock to charge it overnight. I do recall that the Seidio dock has the auto-docking feature which I disable it via no-dock app. And no it doesn't happen with my other chargers at work. So it's only the Seidio charger and the ghost clicks do not happen if I use a different usb cord.
And I saw you are on the sebastian kernel. Have you tried different kernels or even the bundled ones included in the rom (aka leave the kernel alone)?
putting paper on the wedge always worked for me.... but everytime i face dthis problem again, i had to increase the thickness of paper. No issues for me now.
kpjimmy said:
Is the phone plugged into a charger whenever you see the bootloops? And if so, have you tried plugging it in with another charger? It could be as simple as the USB cord not playing nice with the phone. Because for me, I have a Seidio dock which does not like to be touched when docked/charging and does a double click on the screen. Meaning if I wanted to check email, the touch would register down towards the lower part of the screen. I think there is a grounding issue with the dock, but it doesn't negatively affect the use of the phone off the dock in my case. I just use the dock to charge it overnight. I do recall that the Seidio dock has the auto-docking feature which I disable it via no-dock app. And no it doesn't happen with my other chargers at work. So it's only the Seidio charger and the ghost clicks do not happen if I use a different usb cord.
And I saw you are on the sebastian kernel. Have you tried different kernels or even the bundled ones included in the rom (aka leave the kernel alone)?
Click to expand...
Click to collapse
I wish it were that simple...The bootloops have happened both when charging and not.
I too use the Seidio dock. I like it a lot, except for when the phone just randomly lights up in the middle of the night. Last night, from dock mode, while I was sleeping, it was apparent that the phone wanted me to see what was going on with CNN.com. It opened up the internet browser and navigated to it all by itself. I don't even have the CNN app on the phone. It was weird, but whatever.
My wife doesn't use the dock, she's a just plug it in type of gal.
The sebastian kernel is the default one for rom. But I have tried a variety of kernels, see many posts on certain kernels causing restarts.
After a discussion with her this morning, she said that her phone did not restart last night and didn't do any bootloops. Hopefully, I got this one nailed.
Well replacing the battery with a stock one didn't work. It bootlooped this morning at 4:30am. Tonight I think I'm going to Superwipe and reload the ROM and leave it at it's stock load to see if it bootloops again tonight. Unless anybody else has an idea?
Just out of curiosity did you try the paper tick to stabilize the battery? Very strange it's only rebooting in that certain time? Wish I could be of more help but I'm at a loss. And you have tried different roms? Still reboot? So strange. Keep us posted on how it goes. I'd give a different rom a try. Maybe it might help? But if you already did that? Don't know;? And your sure your not under volted
Or over volted on your cpu? Best wishes
Sent from my HTC Sensation using xda premium
realsis said:
Just out of curiosity did you try the paper tick to stabilize the battery? Very strange it's only rebooting in that certain time? Wish I could be of more help but I'm at a loss. And you have tried different roms? Still reboot? So strange. Keep us posted on how it goes. I'd give a different rom a try. Maybe it might help? But if you already did that? Don't know;? And your sure your not under volted
Or over volted on your cpu? Best wishes
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Yeah I've tried the paper trick already...that didn't last an hour. I wish I could get the Logcat to work and then I could find out what is happening at that time. I suspect it's a program, but can't verify that yet. Everytime I get going with the Logcat, it says that the log file is missing on the phone.
I'm going to load the Viper ROM tonight. Anybody have any experience with that particular ROM? I've been reading up on it and it seems pretty stable. I'm going to leave it stock for a night to see if it reboots.
When I loaded the latest version of Elegancia I wasn't given an option to undervolt or overvolt. So I assume that it's at stock settings.
I'll get you posted on tonights proceedings.
Hi yeah I used to run viper before jelly bean and it's stable and a good rom. It has lots of customisation. Hope it does the trick for you as I imagine your pretty frustrated by now. Good luck
Sent from my HTC Sensation using xda premium
nsblum said:
I was attempting last night to get a logcat going for hours. I downloaded 2 programs (which failed miserably), used the adb interface (system write-protected and unable to locate file) and an Android Terminal Emulator (same problem as the adb interface). Being in the technical field, I love to use logs to figure out what's wrong, but just couldn't get it to run.
Click to expand...
Click to collapse
I'm interested in why logcat won't play the game...for starters you should be able to just run 'adb logcat' from command prompt and see the output in cmd without writing to a file.
Something else you could check. Have a look through your init.d scripts for something like
Code:
#remove main log
if [ -e /dev/log/main ]
then
rm -f /dev/log/main
fi
This will give you the "no log file" error. You can delete this or comment it out and that should get logcat working. Provided there aren't any other issues that is
goatee84 said:
I'm interested in why logcat won't play the game...for starters you should be able to just run 'adb logcat' from command prompt and see the output in cmd without writing to a file.
Something else you could check. Have a look through your init.d scripts for something like
Code:
#remove main log
if [ -e /dev/log/main ]
then
rm -f /dev/log/main
fi
This will give you the "no log file" error. You can delete this or comment it out and that should get logcat working. Provided there aren't any other issues that is
Click to expand...
Click to collapse
I was looking through the scripting and it looks to me like the log is in the wrong place. It was extremely difficult to read the scripting itself.
Either way...I've loaded the latest Viper rom onto her phone and loaded all the apps that she had on there and her log each of them in. I tested the logcat to make sure it works and it was running solid.
The only question that I have is...if I start logcat on the phone itself and start it recording and then go to bed....recreating the same scenario....IF the phone starts going into a bootloop, will the logcat capture what happened or will it not record it?
nsblum said:
I was looking through the scripting and it looks to me like the log is in the wrong place. It was extremely difficult to read the scripting itself.
Either way...I've loaded the latest Viper rom onto her phone and loaded all the apps that she had on there and her log each of them in. I tested the logcat to make sure it works and it was running solid.
The only question that I have is...if I start logcat on the phone itself and start it recording and then go to bed....recreating the same scenario....IF the phone starts going into a bootloop, will the logcat capture what happened or will it not record it?
Click to expand...
Click to collapse
The logcat might capture an Error or Fatal or something that could be related, however another option in your situation is last_kmsg since you're looking for the cause of a reboot. The kernel writes to last_kmsg when it crashes and that can give a better idea of what it's trying to do when it crashes. You just need to find someone who can decipher it, the dev of your ROM or something.
If you want, have a read here and here.
goatee84 said:
The logcat might capture an Error or Fatal or something that could be related, however another option in your situation is last_kmsg since you're looking for the cause of a reboot. The kernel writes to last_kmsg when it crashes and that can give a better idea of what it's trying to do when it crashes. You just need to find someone who can decipher it, the dev of your ROM or something.
If you want, have a read here and here.
Click to expand...
Click to collapse
Excellent advice. Thanks for the tips. I already ran a check to make sure last_kmsg was accessible and everything ran clear. I hope that it doesn't happen again and that the ROM change fixed it....but I want it to happen again to bring attention to it with the dev.
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 :-\