Hello Sensation users.
I have a problem with HTC Sensation on MIUI v5 3.6.7 from miuiandroid.com. (I have tried most ICS and JB Roms and Kernels however and this did not solve the problem) .
My phone does not go to deep sleep. From BBS (Better battery stats) I can only see that unknown_wakeups and kworkers are the cause but I cannot find app or process responsible.
Please let me know if anyone has a solution to this.
I allready tried:
1) Reinstalling the ROM
2) Factory reset and not installing any apps
3) Tried different kernels
4) calibrating the battery
5) I also tried different Radios - but i am still not sure this is not whats causing the problem.
Nothing helped so far. Something prevents the phone from going into deep sleep. And this something does not seem to be an app I use cause I tried to fresh install a ROM without instaling any apps at all - but still same result.
Sometimes the phone goes to deep sleep fpor 5 to 25 minutes but that is it.
Thank you for your help
Screen of BBS and BBS log / dsmeg / logcat and Json is attached in zip file
Related
Delete.
I have the same problem except that if i were restarting, it had been continuing the same boot loop.
Meh, back to insert coin 2.2.5
mandroid25 said:
I've installed the Revolution 3.5.2 ROM for my phone (upgrade to 3.6.0 possible, but experienced the problem also with previous versions):
http://forum.xda-developers.com/showthread.php?t=1098849
My problem is, after charging the phone for some hours (usually in docking station) or after using the phone for an hour or so, my phone suddenly crashed in a boot animation loop (meaning HTC logo), freezes - nothing happens anymore. I need to remove the battery and put it back in, can continue using my phone afterwards.
As I'm quite new to Android development (not even allowed to post in forums there), I'm interested what's causing it (too much CPU adjustments) and how can I fix my problem. (Actually I suppose there might be the solution somewhere here, but I couldn't find it - so even a link to a solution might help me).
Click to expand...
Click to collapse
Hi,
The most common cause of bootloops and freezes are incompatible mods.
Have you installed anything other than the ROM?
Did you wipe data,cache partition and dalvik before ROM installation?
Did you reinsatall titanium backup "SYSTEM" data?
More info needed,please
I am also having the same problem. Random reboots, but just hanging at the bootscreen.
It happens very often if i am running Gameboid (a gameboy emulator).
I still have ARHD 3.0.1 with Thyparency Theme.
Hello Peeps,
I was trying to flash a rom yesterday and had something strange happen to me.
The rom featured Aroma installer and I had flashed this particular rom roughly 5 or 6 times with no issues.
Yesterday, I did a full wipe and tried to do a new install of this rom.
There was an option screen in aroma that allows you to choose your own mods and features or use the developers defaults.
I was on this screen trying to choose the developers defaults option and Aroma simply froze up.
It would not let me choose with version to flash.
The touch screen wouldnt respond and I didnt know what to do.
I searched google and found nothing.
I decided to do a battery pull.
I know that a batter pull during a flash is something we should never do as it will brick our phones.
In this case, as the flash had not actually started yet I decided to try it.
I pulled battery and booted into recovery and was able to restore a nanroid.
I am just curious if anyone else has had this issue?
How dangerous was it to pull my battery?
Could I have bricked my phone?
Phone has been working just fine, I am just wondering if there is another way to resolve an issue with Aroma like that?
Thank you,
I never had that problem as for the pull battery it is fine as long as you're not flashing.
I was installing a ROM on my sister's s3 when the aroma installer completely froze. I pulled the battery and it boot looped but wouldn't go into recovery until around the 10th or so time (vol up + home + power). Flashed it again and it worked fine...really weird.
As for bricking your phone I agree with above poster, it should be fine if you aren't flashing anything.
Sent from my SCH-I535 using Tapatalk 2
I've had this same issue happen a couple of times. It usually happens when I try to install the Jelly 'Beans' rom...sometimes it will work, sometimes it will freeze. I usually have to do a battery pull and recovery will come right back up. I've noticed this seems to happen the most when the phone has grown hot...so maybe it has something to do with RAM, etc.
Hello,
I'm running out of ideas to solve my problem with my Sensation, maybe you can help. I was on my beloved ViperS5 ROM and it crashed while browsing due to memory overload or something. After several boot attempts and removing the battery I managed at least to get into bootloader/recovery (ended up with a black screen or freeze 8/10 times). Reinstalled the ROM and it kept crashing at the configuration screen, resulting in a boot loop. So I tried a few other ROM's, exactly the same results.
My last hope was going back to stock using RUU, same problem at the configuration screen, but I managed to boot after few reboots. The phone still crashes after few minutes, when I try to start any app, resulting in a boot loop/black screen/HTC logo freeze. (tried to remove the SD card, it didn't help)
Any ideas how to fix this?
did you leave the device switched off for a long time?
if not do it and then try to switch it on
probably it is still overheated when you are trying to boot it
leave it for 10-15 minutes
best wishes
Maybe it's really damaged from overheat, cause it even crashed in recovery once, so I guess I'm ****ed. I will try to leave it switched off for a few hours, but I doubt it will help. Thanks so far.
Now I get random crashes even in recovery (4EXT, also tried TWRP), I managed to install some custom ROM's, but can't even boot properly after flashing (keeps freezing or restarting in the boot process). My Sensation is JuopunutBear S-OFF, had no problems with flashing ROM's before that. So I guess it is a hardware failure.
frgntz said:
Now I get random crashes even in recovery (4EXT, also tried TWRP), I managed to install some custom ROM's, but can't even boot properly after flashing (keeps freezing or restarting in the boot process). My Sensation is JuopunutBear S-OFF, had no problems with flashing ROM's before that. So I guess it is a hardware failure.
Click to expand...
Click to collapse
If memory serves correctly you should be able to get a logcat from the phone while its in recovery. it might shed come light on what is producing the failures, but its definitely sounding like a hardware failure. Were you overclocked?
How do I get a logcat?
I'm able to stay in recovery for enough time to wipe data, then it randomly crashes or when I try to flash a rom (-> black screen, remove battery to get it back on).
I couldn't even install stock RUU at the first attempt - freezing the whole installation process. No overclocking, also tried the original battery (bought a new one), with/without sdcard/sim -> still crashing.
Edit: Ok, there's a guide for logcat on xda. I will post results after work as soon as I get back home .
How is your sensation going on?
frgntz said:
How do I get a logcat?
I'm able to stay in recovery for enough time to wipe data, then it randomly crashes or when I try to flash a rom (-> black screen, remove battery to get it back on).
I couldn't even install stock RUU at the first attempt - freezing the whole installation process. No overclocking, also tried the original battery (bought a new one), with/without sdcard/sim -> still crashing.
Edit: Ok, there's a guide for logcat on xda. I will post results after work as soon as I get back home .
Click to expand...
Click to collapse
hello, may i know how is your sensation device condition? recently my device having the same issue as yours and out of idea to solve it. before i send device to repair i hope can get some other solution which i miss. thanks in advance if able to provide further infomation.
I was running a custom rom ( SlimKat ) and i went back to stock
i followed these instructions :
http://forum.xda-developers.com/showthread.php?t=2542219
but my phone has a very bad battery drain
some how it never goes into a deep sleep and google service Consume a lot of battery
i re-flased it many times and i also wiped cache and data but nothing works !
any help please ?
Hi,
Since lollipop was not available in India, I installed the russian 5.1.1 rom in feb 2016. Everything was smooth and I had no problems with it. Immediately after flashing the rom, I rooted it and put twrp recovery. I also uninstalled all the bloatware using ES file manager. I didn't have any problems with this russian (the rom's title ends in SER) rom till August.
In August, the phone started losing battery rapidly, the smaller (1300mhz) CPU would not goto deep sleep for some reasons. The phone would be shown as awake constantly in the battery graph on few days. I couldn't find any culprit from the battery graph, even wake detector apps didn't find the reason.
I knew the problem must be rom related, so I downloaded the Indian version of 5.1.1 and installed it. I again put twrp and rooted it, removed bloatware using ES file manager. No battery problems anymore, the phone would goto deep sleep always, as expected. BUT, as soon as I finished doing some root level activity, the next reboot (done manually, it would never crash on its own) would result in bootloop.
The bootloop goes like this, First the "samsung note 3 neo" logo appears (as expected), then the Samsung logo flashes BUT the samsung jingle doesn't start with this animation, the logo keeps flashing for around 5-8 seconds, THEN the samsung jingle starts, which only plays halfway when it reboots, this loop keeps repeating unless I pull out the battery!
I can/could always solve this bootloop by restoring my previous twrp DATA backup. Occasionally I would restore the system as well, but a basic twrp data restore is enough to end the bootloop problem temporarily.
I uninstalled the Indian rom and put the russian rom again 2 weeks back. For the battery problem, I installed "kernel aduitor" app and put the smaller cpu on powersave profile. This solved the battery problem.
Yesterday, after killing tasks in "ES task manager" (I don't remember doing anything else specifically root related), I restarted it manually and again got the bootloop! Earlier I never got bootloop with the russian version, this was the first time.
What could be the CAUSE of bootloop? I'm tired of twrp data restores repeatedly, I need a cause and/or solution badly!
I suspect it to be a hardware problem. I do wish to downgrade it to 4.4 stock rom to see if the bootloop is lollipop rom related or not, but I couldn't find decent stock 4.4 rom sources. Also there's the risk of losing EFS/IMEI while downgrading.
Hello
We are same problem. Have you resolved it already? I hope We can fix it.