Database Info

Verizon Touch Pro 2 - Will Not Enter Sleep Mode!

Hey everyone,
I need your help figuring out why my Touch Pro 2 will not enter sleep mode on it's own. For some reason, the back light will dim, but the screen will stay on even though I have all my settings correct in the power management settings. Has anyone experienced this before? I think the fact my phone will not sleep automatically really impacts my battery life as I can barley make it from 7AM-5PM with barely using it much. It use to work fine, but now it doesn't. I've even done a format of the device twice, but still that doesn't seem to fix the issue.
Any help or advice is appreciated.

Not sure what programs you have loaded but try cold boot, see if works. Then check as you add one program at a time.
There is also an option under settings/battery/advanced to force the device to sleep after a period of time.

@ Aspesi4
Did you ever find a solution for this? I'm having the same issue.
I'm not sure when it started as I have a habit of putting the phone to sleep manually before I holster it.
If I lock the phone, the screen will dim, and at intervals, get bright again on its own. If I leave it at the TF Home Screen, it will stay bright and never dim.
I just can't bring myself to hard reset this phone right now . . lol. Maybe when I have more time. For now, I'll keep manually putting the phone to sleep .. . . sort of a muscle memory thing anyway. I wouldn't mind fixing it though, either.

Nope, never solved this problem. Sorry, I think you're on your own on this one.

I have also been experiencing this problem. I just got my Verizon Touch Pro 2 about two weeks ago. I have only added a handful of apps (WinMo MarketPlace, NetFlix Mobile manager, AP Mobile News, WeatherBug, and Shazam. I am pretty sure it was doing this before Shazam.) I think the phone was doing this even before I installed anything on it, but not certain. This is what I noticed;(I had T-Mobile's version and it did not have this issue.) I was amazed that my new Verizon Touch Pro2 was draining its battery life much more quickly than my TMobile version. Then I figured it out; when ever I get any notice on my phone (missed call, text message, phone notification)the screen lights up. This is normal. However, what is not normal is that the screen stays on until I manually acknowledge the notification or I manually hit the sleep button. I have the power management settings to turn off the backlight if not used for 30 sec and to put the phone to sleep after 1 minute. I tested it a few times to see if it would eventually turn off, 1 minute, 3 minute, up to 15 minutes and it still stayed on. . .

htc touch pro 2 won't enter sleep mode
It's the weather program that keeps it awake ...Slider Bar -> Settings -> Data Download Weather -> Uncheck download weather automatically

htc touch pro 2 won't enter sleep mode
"It's the weather program that keeps it awake ...Slider Bar -> Settings -> Data Download Weather -> Uncheck download weather automatically"......
Agreed it is the weather program.
Specifically I turned off my location data collection..... Settings > Location > Improve Location Service (Slide to off). This worked! However out of interest I switched it back on and my backlight still sleeps OK, I just hope this problem doesn't keep randomly popping up.

I'm experiencing the same issue, suddenly...
But when I re-enable the Location option, it won't go into sleep...
Any ideas how to fix this?

bloddy idiots. HTC adds fancy animated auto-downloading weather at GPS location and break the ability to turn the phone on or answer calls! Quietly BRILLIANT!!!!!! idiots.

[Q] Cognition 3.04 question

The dreaded 'Sleep/Death' has returned. . . sort of!
My phone began turning itself off when the screen shut off only after long periods of time, while I'm asleep overnight.
This began after I went through Cognition 3.04 and set many things to my taste. It still took days before the problem started. I then re-set every thing back and the problem went away.
I'm now done to two possible items that could have caused the problem:
1) The 3D App Screen enabled (yes I know it says Experimental and may cause instability)
2) Sync disabled (an attempt to keep from having to delete tons of emails that have already been taken care of on my computer.)
At the moment I have the 3D App Drawer enabled and Sync ON, but, as I said, it will be a few days before the problem shows.
Any thoughts on why either of these two things would cause a phone turn off?

It seems to be the 3D App Drawer. That's the fastest it has happened about 14-15 hours. Just to make sure I now have the 3D animation and the Sync off and we'll see if it happens anymore. I'm certain I can live without it!

[Q] No Battery Backed Real Time Clock?

So I know that there's been talk about recovery not being able to get the correct date and time, but if you put your phone into airplane mode, turn off the phone and turn it back on, (and leave airplane mode on) you'll see the phone default to April 18, 1970, which indicates that the clock has reset.
At least that's what happens in CM10.0.0 and all previous CM builds I've tried. If I recall correctly this was also an issue on the Stock builds.
This is of course a huge pain in the ass, since any time the battery dies and you plug it in, the device boots up, has a date of 1970-April-19 for a good 15 seconds before picking up time from the network. Which means that alarms think they've been missed and go off, and any titanium backups that are scheduled go off as well.
(And this also happens every time you turn off your phone on a flight, for the same reasons.)
So I'm assuming that whether there is a clock or not...it just doesn't work.
Can we at least have a way to put the UTC system time at shut down into a file on /data or /sdcard that's read at startup? Such that if system time < time in file, use the time in the file.
I know this is ass backwards, but in the case there isn't actually a persistent RTC/hwclock on the device, we need some way to get an approximation of the time when the network or ntp isn't available.

Always on

I am wondering if the always-on will result in not being able to carry it on domestic flights, which require all devices to be OFF! After takeoff, airplane mode or WiFi are OK - but not on takeoff/
They could screen them out with the X-ray at the gates - large phones would gt checked and if S7 - maybe no-go.
If so - would hope custom ROMs could solve that.

Just turn the phone off then what are you talking about? Always on is just a term used for the screen displaying notifications on the black screen when the device is powered on... It can be powered on and off just like a normal phone lol

nique0201 said:
Just turn the phone off then what are you talking about? Always on is just a term used for the screen displaying notifications on the black screen when the device is powered on... It can be powered on and off just like a normal phone lol
Click to expand...
Click to collapse
CNET review said it does not turn off (" I fell in love with the S7's new always-on display, which shows you either the clock, a calendar or an image.") , and that it will display a few items like time always - or so they said. They also contracted Samsung directly on it. .

gaww said:
CNET review said it does not turn off (" I fell in love with the S7's new always-on display, which shows you either the clock, a calendar or an image.") , and that it will display a few items like time always - or so they said. They also contracted Samsung directly on it. .
Click to expand...
Click to collapse
If you are using the toggle in the drop-down, long press the "always on" icon and it will give you the options you're looking for.

bournefusion said:
If you are using the toggle in the drop-down, long press the "always on" icon and it will give you the options you're looking for.
Click to expand...
Click to collapse
Mine has not been shipped yet, so i will give that a try when it comes.
This would be odd however. I leave my S4 on for several days, and see a screen like that when it often pops up, so don't see the reason for having an "always on" since it can already be handled otherwise.

gaww said:
CNET review said it does not turn off (" I fell in love with the S7's new always-on display, which shows you either the clock, a calendar or an image.") , and that it will display a few items like time always - or so they said. They also contracted Samsung directly on it. .
Click to expand...
Click to collapse
Yes while the phone is powered on the screen doesn't turn off completely.. Unless you disable "always on display" your just understanding it wrong which is OK lol

gaww said:
I am wondering if the always-on will result in not being able to carry it on domestic flights, which require all devices to be OFF! After takeoff, airplane mode or WiFi are OK - but not on takeoff.
Click to expand...
Click to collapse
This is not a factual statement. The FAA only requires that the phone be taken out of transmit mode. Airplane mode is acceptable, even for takeoff and landing.

Look I own the phone it turns off and on like a normal phone... It's just that while it's on it has a feature called always in display where when you turn the screen off a clock and notifications will pop up because it has a amoled screen they have the ability to light pixels independently which means that you can have a clock only on part of the screen and the rest be off so then you aren't using very much energy at all. So you can glance at your phone see what time it is and other cool things. It does not mean the phone doesn't turn off. You're taking the feature completely out of Context

I believe the phone is actually always on, even when powered off. I was an airliner passenger last night, had it in Airplane Mode, and then felt it vibrate in my pocket. The phone had rebooted on its own, so I shut it off completely since I wasn't sure what was going on. Later, while it was *shut off*, I felt it get warm, pulled it out and the blue indicator light was flashing, but the phone was off and unresponsive. I held the power button down briefly to reboot it, and it rebooted in airplane mode, just as would be expected had it been shut off while in airplane mode. When it came back on, it had reset the date to February 10, the battery had decreased from 52% to 25% in the two hours since I had shut if off, and the time was displayed in negative seconds (!), something like 7 million. All the weirdness ended when I rebooted it after landing and inactivated airplane mode. I'm not sure what was going on but I am definitely sure that after I turned the phone off, the notification light continued to blink, the device became warm, and it experienced significant battery drain. I therefore believe it is actually never off.

You may have thought you turned it off but didn't. You have to hit the power button twice on screen to complete the action. The first time just highlights it. I'm willing to bet you hit it once assumed it was off and pocketed it. Trust me it turns off

Murphys law: craziness can and will happen. This thread is pointless and should be closed. All phones "turn off" completely. You don't have a 'sleeper cell' for a phone, laying dormant yet on while you believe it's off. You have to really be dense to believe otherwise.
Sent from my SM-G930T using Tapatalk

Help: Device won't finish booting?

So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?

BluSpectre said:
So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?
Click to expand...
Click to collapse
Ok, so I fixed my own problem. I tried a variety of small post-boot tricks like trying to force the device into a different boot mode (ex: Power+minus=safe boot, power+home+VolDown= Download Mode) and forcing it into Download mode worked. It overrode the issue and I was able to tell it to reboot again. This time it rebooted normally. This was really weird. I've never had this happen before on any other device I've ever owned. I hope this might help someone in the future.