HTC Sensation: Possible solution of "phone doesn't sleep" and "power button" problem
Hi every body,
I was getting irritated and extremely fed up of basically two problems of my htc sensation:
1- The phone didn't automatically turn the screen off. The screen would remain ON and wouldn't automatically lock itself. For example, i use the phone and then i will place it at a side expecting that first screen will be dimmed and then phone will automatically lock itself. It wasn't happening since a very long time (I don't remember the beginning of problem), even when screen timeout setting was enabled. I also observed that if at one time i set the brightness level of display to be automatic, next time i check it and brightness level was always set to be at maximum level.
2- When i pressed the power button to lock the phone, the phone often doesn't go dark. It went dark for a second and then became ON again. I had to press it a number of times until it goes dark. Similarly when i wanted to unlock the phone, i had to press the power button multiple number of times, until it gets unlocked.
Basically i was trying to solve the 1st problem. I went into settings -> applications -> manage application. I checked for each installed application whether it has following in the permissions:
System tools: prevent phone from sleeping
Following applications had above mentioned permission, so i removed them:
xda
ebay
mobile voip
daily motion
sports tracker
Calorie Counter - MyFitnessPal
imdb
Photo Editor
speedtest.net
whatsapp
yahoo messenger
Surprisingly after removing those apps, both issues 1 & 2 were totally gone. The phone was automatically locking it self (it still is). So for me problem number 1 is totally gone now.
However, regarding second problem, i tested it like 100 times locking and unlocking the screen by pressing power button. The behavior was absolutely normal. Then i checked the brightness level of phone, it was set to maximum, i set it to automatic. As soon as i set the brightness level to be automatic, the 2nd problem somehow reappeared.
Now if i set the brightness level manually, the 2nd issue doesnt reappear, but when i set the brightness level to be automatic, power button issues reappears.
Sorry for such a long post but I hope may be this post helps someone, also i would like to ask the experts the justification of such behavior of phone.
I am using stock rom and android version 2.3.4, sense version 3.0 and software number 1.50.206.1
This definitely needs a bump!
I was thinking of possible solutions as well, but this one makes sense. Maybe it is a flaw in how that permission is handled? I don't know how to program, but if any of you clever rom hackers are around, maybe you can try tweaking this? I was thinking that it was maybe something to do with the hardware button itself, sending off multiple signals to the phone telling it to lock and unlock right after due to the shoddy power button design.
My main issue with the fix in the original post is that I use a lot of apps that require this permission, and apps are kinda what define how useful your phone is (aside from making phone calls, that is). If there was a way to fix this issue by either tweaking the "prevent phone from sleeping" permission, or maybe just trying to add an input delay that doesn't register any power button presses until half a second has passed or something.
Like I said, I don't know what is possible to tweak with android since I don't know how to program so I might just be talking out of my butt, however, I do like this phone, it just has this one major power button flaw that really annoys me!
#2 doesn't occur in ICS Roms. I'm always on auto brightness.
Some ROMS added some apps may let your phone awake automatically when you close the screen,so it is the right way to move some apps. Using ARHD ICS and Insection ICS ROMS ,#1#2problems never happend.
Basically i would like to stick to original stock rom. I know i can avoid these problems if i use custom roms.
@Tekuno
Let me tell you, i didn't delete all of those apps which were using that permission "prevent system from sleeping". I only deleted those which i mentioned in my 1st post. Among those, i installed "yahoo messenger" again and 1st problem started happening again. I removed that app, problem gone. For me it's the case of hit and trial. I can't definitely point out one specific app which cause the problems.
I think there is really a flaw in the way this permission is handled by operating system of the phone.
I would also like to keep with the stock rom if possible. I figured it would only be a few apps that would be causing the lock screen issues, I am currently too lazy to go through all of the apps and figure out which ones are causing it.
I'll wait patiently for the ICS and Sense 3.6 update and see if that helps.
i have both problems too. About no 2, i always tot it happens after using the stock camera app which forces the brightness to go maximum and sometimes after exiting, there is some bug that doesnt return setting to automatic. Just a hunch but not sure :s
Do you have "Extended quick settings" installed ? and on a custom ROM, if so then i guess you need to check the "Screen On" option in the extended quick settings dropdown window.
You must have accidentally pressed it and activated it instead.
Related
When I'm on a phone call, the screen backlight goes off after 10 seconds, even though I have Settings->System->Backlight->Battery set to 4 minutes. Even if I'm using another application while on a phone call, the backlight goes out after 10 sec. If I'm not on a phone call, then the backlight seems to obey the systems setting.
FWIW, this is a Touch Cruise, with the 1.25.405.1 WWE ROM, and WM6 18129.0.4.5.
there is nothing wrong with your phone thats normal. but the fix is a registry change. I can not remember what it is but I am sure the answer was in the the big fixes thread somewhere. I keep seeing it in there but keep forgeting to change mine. If I found it i will post it here.
Thanks. I did a search before posting, but didn't find anything.
Check out tweak #38 here:
http://forum.xda-developers.com/showthread.php?t=355277
This supposedly disables the screen turning off during a call, I haven't tried it myself.
i think it's not a problem at all for me
in fact, it prevents you to ends the call or launch a program if your cheek touch the screen
Yeah doesn't bother me either, it's expected behavior. But to each his own, some people want to turn off that feature.
Fine, it's a feature. How do I turn it off? Tweak #38 extends the time to ~30 seconds, but the display still goes off. That's a real killer if trying to navigate some company's phone menu, or trying to read a reference document while talking.
Well, in S2U2 there's in an option to choose, whether the phone should
turn the screen off during call or not. This option is available seperated
for Battery or Powered device while calling. Maybe this helps. Tested it
and works. Though I hate it, when the screen stays on during call, because
most time when I hang up I recognize, that I started tons of apps with
my fat face So I turned that option back to default for my case.
You may try yourself.
Olioaglio
Thanks. Unfortunately, S2U2 has a whole bunch of other features, which means a bunch of added overhead. It also needs a user manual to explain those features and options
So don't use what you don't need (or don't understand).
IMHO, it's worth it...
\HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
change "1" to "0"
I also found out this one:
Using Pocket Toolman2 (v.2.26.36), go to ''Tools''-->''OS Tweaks''
and there is an option to unchek the box ''Allow phone to go to sleep during calls''
cybernec said:
\HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
change "1" to "0"
Click to expand...
Click to collapse
THis is the better tweak and i have used it for a long time, simple
Where is the setting that sets the lockscreen timeout to 15 seconds? I still have a huge issue with pocket dialing and would love to adjust it down to 2 seconds (improve battery life as well). I know that it's not in the apk since the default android timeout is the same with the htclockscreen deleted.
Is this a kernel issue that can't be addressed until the source is released?
Thanks for your time.
tstack77 said:
Where is the setting that sets the lockscreen timeout to 15 seconds? I still have a huge issue with pocket dialing and would love to adjust it down to 2 seconds (improve battery life as well). I know that it's not in the apk since the default android timeout is the same with the htclockscreen deleted.
Is this a kernel issue that can't be addressed until the source is released?
Thanks for your time.
Click to expand...
Click to collapse
The timeout should be in the display section of settings.
It actually most likely is part of the apk. HTC modified the settings apk to add the scenes feature in there. Most likely they either modified that part too or, even more likely, they just read the settings for the lock screen in their lock screen apk. Either way, this is what would need to be modified to allow for adjusting of the timeout. Now, that said, there may be a plethor of other places that need to be modified to allow for this change to actually work. Right now this would be a lower priority.
There is already a 15sec lockout option. Go Menu>Sound & Display>Screen Timeout (will be at the bottom of the page).
chuckhriczko said:
The timeout should be in the display section of settings.
It actually most likely is part of the apk. HTC modified the settings apk to add the scenes feature in there. Most likely they either modified that part too or, even more likely, they just read the settings for the lock screen in their lock screen apk. Either way, this is what would need to be modified to allow for adjusting of the timeout. Now, that said, there may be a plethor of other places that need to be modified to allow for this change to actually work. Right now this would be a lower priority.
Click to expand...
Click to collapse
So you're saying that on a vanilla build of android there is a setting for the lockscreen timeout, and that the default android lockscreen is part of the settings.apk?
There is already a 15sec lockout option. Go Menu>Sound & Display>Screen Timeout (will be at the bottom of the page).
Click to expand...
Click to collapse
Not the screen timeout, the lockscreen timeout. In my pocket the menu button can be pressed, then pressed again within a 15 second window to wake the device and magically start dialing. I would like to cut that 15 seconds down to a realistic 2-3 seconds.
That's a good idea and I'm interested to hear if it's possible.
tstack77 said:
Not the screen timeout, the lockscreen timeout. In my pocket the menu button can be pressed, then pressed again within a 15 second window to wake the device and magically start dialing. I would like to cut that 15 seconds down to a realistic 2-3 seconds.
Click to expand...
Click to collapse
Why not just setup a unlock pattern?
gu1dry said:
Why not just setup a unlock pattern?
Click to expand...
Click to collapse
Have you actually tried using one for even just a day...what a giant PITA
tstack77 said:
Have you actually tried using one for even just a day...what a giant PITA
Click to expand...
Click to collapse
I've used the unlock pattern since I purchased the phone, which I got my phone 9 Oct 09...
gu1dry said:
I've used the unlock pattern since I purchased the phone, which I got my phone 9 Oct 09...
Click to expand...
Click to collapse
I commend you then, I didn't last an hour inputting the damn thing every few minutes just to read a text message...but of course I don't need my phone to be that secure so the annoyance > necessity
That said, the lockscreen should be able to accommodate the both of us, and I'm just looking for a solution that works for me.
tstack77 said:
I commend you then, I didn't last an hour inputting the damn thing every few minutes just to read a text message...but of course I don't need my phone to be that secure so the annoyance > necessity
That said, the lockscreen should be able to accommodate the both of us, and I'm just looking for a solution that works for me.
Click to expand...
Click to collapse
And I was simply suggestion a possible solution. Also I have my lockscreen timeout set to 1min.
My personal recommendation: follow the directions in the thread on deleting unwanted apps to root your Hero, remount the filesystem so you can delete HtcLockScreen.apk, then buy LockbotPro & install it instead. The current version is a little buggy in the way it handles reboots (after you reboot, the Android non-HTC lockscreen becomes re-enabled and "first in line"), but it's not too hard to fix when it happens, and it works wonderfully the rest of the time.
To fix it after rebooting, you basically swat away the default Android lockscreen (menu-menu), launch Lockbot, launch its settings menu, un-check "enable lockbot", return to home, relaunch Lockbot, launch its settings menu, re-check "enable lockbot", and you're done. Looking at the changelog, it appears that the bug I just described is a fairly recent new bug, and it looks like the author is releasing updates every couple of days trying to fix it.
Note that Lockbot will "kind of" work if you don't root & delete HTC's lockscreen... but it won't work well because HTC's lockscreen is pretty aggressive about defending its turf. It's a night & day difference. (Sorry if I sound like a broken record, but as they say... there's no zealot like the reformed sinner. If I'd known how easy it would be to fix the #1 thing I hated about my Hero, I'd have done it the afternoon the first "how to root the CDMA Hero" hit the net
I can definitely say that my overall happiness & satisfaction increased dramatically after I did it. It sounds petty, but HTC's dysfunctional/useless lock screen (backed up by Android1.5's annoying & tedious default) really did annoy me to the point where I was starting to dislike my Hero. Rooting & replacing them with Lockbot really made a difference.
Thanks for the recommendation, nice to see I'm not the only one annoyed with the default lockscreen issue.
I tried out LockBot all day yesterday but it still has one major flaw, any/every button will wake the device (not just 'menu' and 'power'). Each time I pulled the phone out of my pocket the screen was on, pretty sure it's the trackball constantly getting tapped in my pocket.
Had to delete it due to battery drain. Still looking for a solution
I'm trying this program out to get my phone profiles to change automatically (silent for work and wifi/bluetooth on at other times like when plugged in etc).
I have set up details for auto switching but the behaviour now of the profiles is a bit weird at times.
When I have an automatic switchover for instance from Home to Work (silent) profiles, I'm not certain if it's actually doing it or not.
What happened this morning for instance was that I got to work at 8.40 and checked my phone and it still had the speaker icon showing normally in the taskbar as if it was still set to 100% volume, BUT, when I pressed the volume rocker to set it silent, I found the volume bar was already fully down, suggesting it had actually changed the volume setting as required and presumably switched the profile, but simply not refreshed the speaker icon on the taskbar to show that the phone was now set as silent or vibrate.
Hope that makes sense!
On top of that, whilst it seems to work well to switch both wifi and bluetooth on when required, it doesn't always seem to turn wifi off again when it should. I'm fairly sure it's not just a case of profile settings causing it just to remain on because the profile it's gone back to still uses wifi after an auto switch.
Would love to keep this program but only if I have total confidence that my phone is not going to ring when it's meant to be silent etc, and it's a little misleading at the moment with the impression it sometimes gives about whether the phone is actually silent or not.
Anyone else have these issues, and any way I can correct this?
Cheers!
if you've gone in to setting-->profiles --> and click option --> automatic switching
then you are doing it right
also realise there are option for switch on/off bluetooth/wifi/radio etc when setting up your profile
also if you can't see the PhoneAlarm taskbar on your front screen, then that would mean its not install properly and therefore not working, hope that helps
have you been to the forums @ pocketmax.net? there is tons of information there, and plenty of help for questions such as this.
I have been using phoneAlarm with no problems whatsoever for years now...
oh, and by the way, your signature does not reflect what ROM you are using -- I have noticed on the more recent Energy ROMs of mine that the taskbar is sometimes "slow" to refresh. for instance, when unplugging usb/charger the battery icon does not change from the 'lightning bolt' back to percentage until a minute or so... (this could possibly be related to volume icon as well)
Thanks for the replies
No I've not looked on their forum I must admit. Will be worth checking out though.
I'm very interested in the comments about this slow refresh with the taskbar though as I think that must be the problem.
I had noticed the same thing with the charging 'lightning'' icon but had forgotten until you mentioned it.
I've added my rom info in signature - thanks for pointing that out.
Is there any cure for this behaviour with the taskbar other than swapping Roms?
I'm quite happy really with this one, unless someone wants to recommend a rom that's radically better and doesn't have this particular issue?
Plus the fact I could potentially go through loads of other roms til this is solved, or just be trading this bug for another one.
Would love to solve it though. This app is growing on me but if I have to double check each time it swaps a profile to make sure it's done it then it defeats the purpose of having it.
I realise at least that this may not actually be the fault of the app itself though.
I am running Dman's rooted stock UCLB3 with Entropy's DD and Voodoo Lagfix. I love the setup but one this is really bothering me: I can't set the screen security time. I like the screen to go off in 15 - 30 seconds, but I want to be able to decide how long it will be until I have to use the security unlock. Now, there used to be a setting for this under Location and Security, but for some reason it is no longer there. Is it this ROM or is this missing from all 2.3.6 builds (i.e. stock)?
In case you aren't following me, I am attaching two screenshots, one from Samsung's website, the other from my phone. As you can see there is no "Timeout" menu on my phone. Was this somehow stripped from Dman's ROM (not impossible since the android.policy.jar file - the one that I believe is related to this menu - sometimes encounters issues from deodexing) or is this feature just gone from the phone? If it was stripped, how might I go about getting it back?
This is driving me mad right now, so I'd love to hear a definitive answer.
The setting that you are looking for can be found under Settings / Display. It wasn't stripped, you're just not in the correct menu.
No, that is a different setting. You'll notice that the display setting is to determine when the display will go to sleep (when it will automatically turn off), the setting I am talking about determines when the screen will lock after the screen turns off.
There are two programs with similar functions: Delayed Lock and JuiceDefender Ultimate. However, I suspect that the phone setting is still partially alive somewhere because both programs seem to wreak havoc with whatever settings are now default.
Oh, okay, now I understand. That feature isn't available in stock UCLB3, and there were no issues when deodexing.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Thanks. That's basically the answer I wanted. I've been poking through the guts of both the stock and rooted builds trying to find out what happened. It is really irritating that it's not there (well, for me it is!) because the security screen seems to have a mind of its own, particularly if you introduce alternative lockers into the mix.
For anyone who may be interested, you may be able to set the timeout by editing values in the android.policy.jar file in framework folder. Search around, you'll find instructions. I haven't tried this.
The two apps I have found that enable this functionality are Delayed Lock and Juice Defender Ultimate. However, neither app works well with 3rd party security locks such as Go Locker. The lock delay apps trigger the system security screen lock so you may have to go through as many as 3 screens before you get to your home screen.
Sorry, there is one other app: Password Delay. I did not try this because I want to use a pattern lock. PD does not work with patterns.
Yeah, join the club lol. I just learned to deal with it after a while. But I hear you. Tried looking for some alternative ideas... and I just kept unlocking everytime.
Sent from my A500 using Tapatalk 2
Hello everyone,
It has been a while since I ventured through this forum, but it seems that y'all may be my only hope.
I've been suffering through this glitch/stutter that, when scrolling, the phone registers my finger as taps everywhere my finger slides. All I simply need to do it remove my finger from the phone and I can continue scrolling like normal. It is super annoying and I cannot find out what causes it, it just seems random. It never happened on any of my Nexus phones in the past.
Now, here's a list of things I've tried in order to fix it:
- Safe mode
- Factory Reset (Restore from Google account)
- Factory Reset (New Device option)
- RMA'd through Google support and received a new pixel and the problem persists (even after going through the steps above on the new device)
Here is a short video of the glitch while it is happening.
https://goo.gl/photos/GysQXd82MexVkk836
(Hopefully that link works)
Note: the glitch will not stop until I take my finger off the phone, you can tell when it is happening when I scroll over the share button and it registers as a tap.
If you guys have any suggestions, I'm ready to try anything at this point. I don't want to go through Google support because I know they'll send me yet another Pixel (I've already talked to them again and that was their solution, I told them I'll try a few more things) and I feel like that is a waste. I'm almost 100% positive that this is a software glitch, not hardware.
Thanks!
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Jaxidian said:
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Click to expand...
Click to collapse
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Skillfulshoe said:
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Click to expand...
Click to collapse
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Jaxidian said:
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Click to expand...
Click to collapse
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
I'm not sure if this is caused by a bad touchscreen sensor because I've had the problem on two separate Pixel phones so far. Or maybe I just got super unlucky with two faulty phones.
I don't think my fingers are too dry. If all else fails, I'll try moisturizing them I guess. I've never had this problem on all my other phones though, but I guess you never know.
Thanks for the help.
Skillfulshoe said:
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
Click to expand...
Click to collapse
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Jaxidian said:
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
Click to expand...
Click to collapse
Yeah I totally understand what you're saying. I just have gotten frustrated with this. I know it isn't a big deal honestly.
gadgetgaz said:
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Click to expand...
Click to collapse
Yeah that could be what causes it. Maybe it is just the way we are scrolling and how Google has calibrated the screen touch sensors.
Possible Fix
So I went into accessibility settings and changed the duration you need to hold your finger down to do a long press to medium (from the default as short). It seems that may have fixed it. I haven't experienced the glitch since I've done that change.
Here's to hoping that did indeed fix the issue.
Thanks everyone.