Below is my info from my main thread int he HTC One Q and A section thought I should post here since I wasn't getting anywhere with help.
I
have succesfully gained s-off and super cid between now and then also updated my firmware to the latest and still keep getting the sleep of death on CM based roms. i've tried vanilla rootbox and cm 10.1 nightlies, tried Ady's MIUI and illusion rom and a few others all keep on giving me the Sleep Of Death right after the screen goes off when not in use.
I can note that I can use the roms without a single problem at all if I do not let the screen go off...
So i've posted on a number of threads and I thought I'd sum up everything or all the information here and hope I can get some more help.
So here's the info
- - - -
Logs from rootbox
LOG CAT - http://www.mediafire.com/download/7b.../important.txt
KERNEL LOG/dmesg - http://www.mediafire.com/download/hh...toql/dmesg.txt
- - - -
It is an Australian OPTUS HTC One with the Optus_001 CID or whatever it is exactly.
Bootloader - Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.020
eMMC-boot
Mar 11 2013,22:16:05:-1
ClockworkMod Recovery v6.0.3.2 installed
The back of my device says its Model is an PN07140
On stock rom (only rooted and unlocked bootloader) My software info is as follows:
Android Version 4.1.2
HTC Sense is 5.0
Software Number is 1.29.980.2
The HTC SDK API level is 5.12
The kernel version is: 3.4.10-g42e6c45
[email protected] #1
SMP PREEMPT
Baseband: 4A.14.3250.13_10.33.1150.01L
Build number: 1.29.980.2 C:164689 release-keys
Browser version: WebKit/534.30
Phone name - HTC_PN071
- - - - - - - - - -
I have talked with codeworkx about the issue being CM based and gave logcat and kernel logs to him from rootbox rom in which he thinks the sleep of death is caused by a kgsl derp (honestly have no clue what the hell it really is at all)
I've attempted Clean installs, Patches if any and attempts at clearing the cache, dalvik etc etc to try and get the rom to work.
- - - - - - -
I have come across a weird factor while running Ady's MIUI rom that if I set the theme to the Superman theme with the animated Lockscreen I can SOMETIMES wake the phone within 3-5 or so seconds of pressing the power button.
I haven't been able to actually re-produce the rare occasion firmly but I found it happened with that theme applied.
I've tried the swipe2wake things without any luck.
- - - - - - - - - - -
So I'll keep this thread going to try and get help. I was told to update my firmware or try to but I search for optus firmware and find none, not to mention there hasn't been an update as of yet (that I have received or know off) from optus yet for my HTC One.
Hopefully I will be able to get this fixed and Use CM based roms...
- - - - -
ADDITIONAL INFO I FORGOT - I don't mess with CPU/performance settings and leave them all stock/default.
It's possible that you have more problems, but I'd try doing the battery pull while plugged into the PC again. Be sure to not put it back in until after the notification/charge light turns off. If it starts blinking red and green, start over again. If it doesn't work then you'll need to send the phone into htc.
CyanogenMod has the "trackball wake" and volume rocker wake" already on it.
Diablo67 said:
It's possible that you have more problems, but I'd try doing the battery pull while plugged into the PC again. Be sure to not put it back in until after the notification/charge light turns off. If it starts blinking red and green, start over again. If it doesn't work then you'll need to send the phone into htc.
CyanogenMod has the "trackball wake" and volume rocker wake" already on it.
Click to expand...
Click to collapse
You can't remove the battery from an HTC one...
Bump
Bump!
If anyone cares to help
this is part of a logcat http://i.imgur.com/f5ERkQI.png
from me running MIUI
while trying to wake from sleep of death...
Anything you can see in it that could help? (I have no idea what I'm looking for or how to fix)
Related
Hi,
I looked in the noob guide to see if I could understand, but can someone please explain what the ROM abbreviations mean.
Please correct the ones I have wrong and answer the ones I don't know. Thanks for taking the time to help me.
CM7 - Cyanogen Mod 7
TW - Touch Wiz or Team Whiskey
AOSP -Android...
FFC - Front Facing Camera
EDT - Einherjar Development Team
RC# - ?
V# - Version #
UV - ?
CIFS - ?
BLN - ?
OC - Overclocked?
CWM - Clockwork Mod?
I think that's all I can think of, please feel free to add any I missed. Thanks for the help and understanding.
Respectfully,
Vahdyx
CM7 - Cyanogen Mod 7
TW - Touch Wiz or Team Whiskey
AOSP - Android Open Source Project
FFC - Front Facing Camera
EDT - Einherjar Development Team
RC# - Release Canidate
V# - Version #
UV - Under Volt
CIFS - Common Internet File System
BLN - BackLight Notification
OC - Overclocked
CWM - Clockwork Mod
Thank you, I clicked thanks as well.
One more thing, when resetting battery stats, should that be done on a full battery or near empty?
It should be done when the battery is fully charged.
These are the steps I follow (I have CWM):
1. Charge to 100%.
2. With Vibrant plugged in, boot to recovery.
3. Go to advanced > wipe battery stats > select ‘yes’
4. go back > reboot phone (unplug after phone has rebooted).
5. Use phone until battery dies.
6. Charge to 100% with the phone off. (Not sure if the charging with the phone off is really necessary)
7. With Vibrant plugged in, turn on phone and wait for media scanner and launcher to finish loading before unplugging.
You will find different steps/techniques, this is what I do and it seems to work well.
I always charge to 100% before flashing a new ROM, that way I don't have to reset the battery.
creeve4 said:
BLN - BackLight Notification
Click to expand...
Click to collapse
I've always thought it was Button Light Notification !
I'm so tired I can't verify which one is correct
طوني تبولة said:
I've always thought it was Button Light Notification !
I'm so tired I can't verify which one is correct
Click to expand...
Click to collapse
You could be right, I'm not 100% sure. Button Light does sound more correct.
First let me talk about how I got into this mess. I had used the thunderbolt as my phone previously and had rooted it, installing custom roms often. After getting a new phone, I decided to unroot my thunderbolt and give it to a family member. At first, everything was working fine; I had no problems unrooting the phone. However, a month or so later it started having problems.
Upon booting, the phone goes straight to hboot where it displays a security warning. But this only happens occasionally. Sometimes it will actually boot but take about 20+ minutes to start up where it come to the homescreen with a solid black background, soon to freeze and turn off.
I have tried fixing the phone based off methods others used to fix similar issues, but to no avail. For example, I have tried flashing the 2.11.605.19 firmware through hboot only to have the same problems occur. Perhaps I did not use the right version. Do you guys have any idea on how I can fix this? Could flashing an ruu (if there is one) for the latest ics build solve this?
When I try to unlock the bootloader through htcdev, everything works fine up until the confirmation screen on my phone asking if I want to unlock the bootloader or not. For some reason, the power button won't work to press yes. It does work normally for saying no and everything else though. I have tried using the adb to force it to use the power button, but in its "unlock the bootloader" state it isnt connected.
some relevant info for the phone:
hboot version - 1.05.0000
radio - 1.49.00.0406w_1 - should be the radio from 2.11.605.19
Hi XDA-Devs,
I recently upgraded my HTC EVO 3D to Android 4.3 via CM 10.2 from Android 4.0.3 KingCobra3D-ICS-1.5. Everything upgraded smoothly except that when I let my phone idle for ~5min while unplugged, it will begin a perpetual reboot cycle until I stop letting it idle - it just turns on and off endlessly. As long as it's doing something it won't reboot (e.g., playing music with the screen off). Any ideas of what's wrong, or how to resolve this problem?
Here are the steps I took:
Relocked phone
Restored stock ROM and kernel using RUU (revolutionary wouldn't work with an ICS ROM already installed - had to downgrade to GB)
Used Revolutionary to change phone to S-OFF
Flashed Superuser
Flashed CM 10.2 ROM
Flashed 4.3 GAAPS
Created backup
Minor other problems
1) My Contact card cannot be linked with the Google Contact I've created for myself. I had it set that way on 4.0.3. How can I fix that?
2) Holding Power + Home button does not let me screenshot any more. How do I fix that?
I have a droid razr that was on 2.3.5 and i wanted to put the JB on it. so i got the bat utility and put the phone into fastboot, did the software on there with the wipe. Now when the phone screen is one it goes crazy, it flickers and the bottom half of the screen has like these checkered things on it. if i click the home key or the back key it will go away for a second then come back.
I have a feeling when i did the update maybe something was not compatible with the SW? maybe the radio vs the boot? or radio vs the S/W? but the bat utility installed the new radio on there. Has anyone has this issue?
another weird thing i notice is that the volume down + power key does not force a shut down, but it takes a screen shot instead. And i know its not the screen issue, because in fastboot mode, the phone does not freak out.
System Version - 98.72.16.xt912.Verizon.en.US
Android - 4.1.2
Baseband - CDMA_N_05.21.00RLTEDC_U_09.1D.00
webtop version - wt-3.0.0
Kernel - 3.0.8gbacb1cf / [email protected] #1
build number - 9.8.2O-72_VZW-16
thanks
eric303 said:
I have a droid razr that was on 2.3.5 and i wanted to put the JB on it. so i got the bat utility and put the phone into fastboot, did the software on there with the wipe. Now when the phone screen is one it goes crazy, it flickers and the bottom half of the screen has like these checkered things on it. if i click the home key or the back key it will go away for a second then come back.
I have a feeling when i did the update maybe something was not compatible with the SW? maybe the radio vs the boot? or radio vs the S/W? but the bat utility installed the new radio on there. Has anyone has this issue?
another weird thing i notice is that the volume down + power key does not force a shut down, but it takes a screen shot instead. And i know its not the screen issue, because in fastboot mode, the phone does not freak out.
System Version - 98.72.16.xt912.Verizon.en.US
Android - 4.1.2
Baseband - CDMA_N_05.21.00RLTEDC_U_09.1D.00
webtop version - wt-3.0.0
Kernel - 3.0.8gbacb1cf / [email protected] #1
build number - 9.8.2O-72_VZW-16
thanks
Click to expand...
Click to collapse
Have some issue on NorthEU phone (XT910). But on previous one (XT910 DE) do not have this issue. It looks like hardware issue.
eric303 said:
I have a droid razr that was on 2.3.5 and i wanted to put the JB on it. so i got the bat utility and put the phone into fastboot, did the software on there with the wipe. Now when the phone screen is one it goes crazy, it flickers and the bottom half of the screen has like these checkered things on it. if i click the home key or the back key it will go away for a second then come back.
I have a feeling when i did the update maybe something was not compatible with the SW? maybe the radio vs the boot? or radio vs the S/W? but the bat utility installed the new radio on there. Has anyone has this issue?
another weird thing i notice is that the volume down + power key does not force a shut down, but it takes a screen shot instead. And i know its not the screen issue, because in fastboot mode, the phone does not freak out.
System Version - 98.72.16.xt912.Verizon.en.US
Android - 4.1.2
Baseband - CDMA_N_05.21.00RLTEDC_U_09.1D.00
webtop version - wt-3.0.0
Kernel - 3.0.8gbacb1cf / [email protected] #1
build number - 9.8.2O-72_VZW-16
thanks
Click to expand...
Click to collapse
You should flash 4.1.2 full fastboot package with rsd lite. It will be fine if it's software issues.
I've been troubleshooting this issue for a few days now and haven't had any luck.
The issue started after I updated to Android Revolution HD 7.1 by mike1989 -- which had issues because I hadn't upgraded my firmware yet -- so I attempted to upgrade to HTC One 1.40.401.5 (WWE) firmware, however I couldn't get the firmware to flash, so I reverted back to Android Revolution HD 5.2 by mike1989, and now I have this issue.
Here's the issue step by step:
Phone is off, turn on and boot to home screen
Hit power button to turn display off, display turns off
Hit power button to turn display on, display turns on
Hit power button to turn display off, phone reboots
And here's what I'm running:
android version: 5.0.2
rom: Android Revolution HD 5.2 by mike1986
kernel version: 3.10.49-g4ee4c46 [email protected] #1 SMP PREEMPT
baseband version: 01.01_U11440221_60.04.50305G_F
build number: 1.32.401.17.CL506785 release-keys
cid: 11111111
mid: PJA11000
S-OFF
OS-1.32.502.9
Hopefully someone on XDA can point me in the right direction. Thanks.
chardy52 said:
I've been troubleshooting this issue for a few days now and haven't had any luck.
The issue started after I updated to Android Revolution HD 7.1 by mike1989 -- which had issues because I hadn't upgraded my firmware yet -- so I attempted to upgrade to HTC One 1.40.401.5 (WWE) firmware, however I couldn't get the firmware to flash, so I reverted back to Android Revolution HD 5.2 by mike1989, and now I have this issue.
Here's the issue step by step:
Phone is off, turn on and boot to home screen
Hit power button to turn display off, display turns off
Hit power button to turn display on, display turns on
Hit power button to turn display off, phone reboots
And here's what I'm running:
android version: 5.0.2
rom: Android Revolution HD 5.2 by mike1986
kernel version: 3.10.49-g4ee4c46 [email protected] #1 SMP PREEMPT
baseband version: 01.01_U11440221_60.04.50305G_F
build number: 1.32.401.17.CL506785 release-keys
cid: 11111111
mid: PJA11000
S-OFF
OS-1.32.502.9
Hopefully someone on XDA can point me in the right direction. Thanks.
Click to expand...
Click to collapse
It looks like to me that you are running the new kernel (3.10.49-g4ee4c46) from the new firmware with the older version of the rom that is causing your reboots. You should start from the beginning and try to flash the 1.40 firmware and then install the new rom version and you shouldn't have any problems.
Ended up having the exact issue, but on a different ROM and upgrading to a newer firmware but the issue is the same, the fix is just to flash the firmware you were on previously
kash20 said:
Ended up having the exact issue, but on a different ROM and upgrading to a newer firmware but the issue is the same, the fix is just to flash the firmware you were on previously
Click to expand...
Click to collapse
What if I want to upgrade the firmware? Should I wipe down to scratch and start over in that case¿?
rpimentel1 said:
What if I want to upgrade the firmware? Should I wipe down to scratch and start over in that case¿?
Click to expand...
Click to collapse
If you want to upgrade the firmware, you just need a ROM that supports it, the issue is some custom ROMs use a different kernel meaning there are issues like the one mentioned above, upgrading firmware is a really easy process, just grab one from the following threads
http://forum.xda-developers.com/one-m9/development/ota-1-32-401-15-firmware-noredtext-t3072571
http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678
Make sure your device is S-OFF and you've got the right firmware for your device, then it's just a matter of running two commands (both of which are found in the threads linked)
kash20 said:
Make sure your device is S-OFF and you've got the right firmware for your device, then it's just a matter of running two commands (both of which are found in the threads linked)
Click to expand...
Click to collapse
Brilliant! Thanks a lot - I was really scratching my head at this problem.