Standard Locking Screen wm6.1 reacts to touch - General Questions and Answers

On the standard WM6.1 lockscreen the screen still reacts to touch. You can't actually do anything but when it's dimmed it goes back to full brightness when you touch the screen. This prevents the screen from turning off causing battery drain. Is there a way to change this behavior without using an external program? Or at least a way to make sure the screen turns off after say one minute.
I have tried about every locking program I could find but they all seem to cause some battery drain on my phone configuration.

Related

Keyboard and screen locking issues...

I have problem with my keylocking.
I put keylock after 30sec of inactivity.
Phone does lock it but when i put phone in my pocket and after puting in out there are number of programs called and
sometimes even accidently sends sms to some number.
i cant figure out if these buttons do that or side buttons or i just somehow press the touchscreen...
I know this will sound odd, but change your brightness to something a little higher, I have noticed that if my Treo is set to a lower brightness that it will either wakeup on it's own, or not shut off correctly.
This is a know bug indeed. You have to turn brightness to at least 40% to prevent the device from turning on on it's own.

AT&T Fuze screen issue - bottom menu-area of screen is flickering almost constantly

AT&T Fuze screen issue - bottom menu-area of screen is flickering almost constantly
(Forgive me for the length of this post. I am just trying to provide as much information as possible! If anyone has encountered this same or similar issue, your help is greatly appreciated).
I need help! (professional and otherwise) ...with my AT&T Fuze (rebranded Touch Pro).
I am developing a game for Windows Mobile called Scrobble (http://forum.xda-developers.com/showthread.php?p=3206316&posted=1), and I left it running overnight.
My screen is set to turn off after 1 minute, and my device set to sleep after 5 minutes when plugged in to external power.
I had the Fuze plugged into wall outlet power to recharge. I left it lying, like I always do, face down on a black soft-leather CD case (so the glowing charging light doesn't bother me).
I left it alone for the 7.5 or so hours I was asleep. When I woke up in the morning and picked it up, the screen was on. It usually is not on, and I don't think I pressed the button to activate the screen.
When I looked at the screen, the Scrobble program was still running, and the bottom menu portion of the screen was flickering. Scrobble has two menu buttons at the bottom -- "Turn" and "Game" -- with a SIP keyboard icon in between them (same as nearly all WM apps).
In any other program, or the Today screen, the menu portion of the screen flickers (the brightness constantly and rapidly fluctuates consistently... like a fluorescent light that is on its last leg).
I did a full power off and power on, and during the "world phone" screen and the the AT&T 3G "power up" animation, the flicker was -not- there. But as soon the Windows Mobile loading/splash screen appeared, the flicker returned, in the exact same spot.
And I can see the ghost "Turn -- [SIP] -- Game" menu in the flicker. But I don't think it's burnt into the display, because it's not there during the first two loading/splash screens.
Currently I have the battery completely removed from the device and will leave it out for a while. If that doesn't work I will do a hard reset.
Any help would be greatly appreciated!! (This device is about 2 months old -- does HTC provide any support for it directly?).
Fixed
Phew! My screen flicker issue is no more.
I'm not sure if it's because I took the battery out and let it sit and think about what it had done for ~22 hours, or if it's because it just went away after a while (with the battery out for 22hrs). But either way, my Fuze is back to normal!
So if anyone leaves theirs on overnight and wakes up in the morning to a flickering ghost of a menu at the bottom, my suggestion is to fully reboot it, then take the battery out and leave it out overnight!
(It's kind of nice going a full day without any phone calls!!).
good for you.. you dont need a new phone giving you damage issues already... glad to hear that its gone
Thanks you for this post. I am going through the same thing with my ATT Fuze. This time it is Tomtom that I left running overnight with the screen turning on and off. I can add that the flicker and ghost is there the second the phone powers on. I have already hard reset and took the battery out for a few mins, but the flickering still there. Now I will take the battery out for several hours and hopefully it will be normal again.
I had a similar issue this week. I was using the phone all day, getting emails and phone calls, no problems. I get home and go to charge my phone and it doesn't appear to be charging. I flip on the screen and the whole screen is flickering on and off like it's not getting enough power. I charged the device over night, hard reset, pulled battery for 24 hours and still it won't go away. I just got the device thru amazon so I already reordered a replacement.
I've never left my screen on for hours at a time and I sometimes run into that same issue. The bottom of the screen flickers, and I can see a ghost image of my left and right soft keys when doing things that pull up a dark grey or black screen, like adjusting the volume. I usually try a few soft resets, and if that doesn't work I turn it off and take the battery out for a while. From what I am reading it seems to be correlated with extended periods of screen usage, but my screen has rarely been kept on for more than 30 minutes at a time.
Not to beat a dead horse or anything, but I was just having the same problem with my Fuze: the bottom quarter of the screen was flickering, but without the ghosting you spoke of. Out of curiosity, I went into my "Power Settings" menu, and for some reason the "auto adjust backlight" was unchecked, and the brightness settings were maxed out. I checked "auto adjust backlight" and the flickering stopped. Not sure why, but thought I'd add it to the thread.
kart_racer3 said:
Not to beat a dead horse or anything, but I was just having the same problem with my Fuze: the bottom quarter of the screen was flickering, but without the ghosting you spoke of. Out of curiosity, I went into my "Power Settings" menu, and for some reason the "auto adjust backlight" was unchecked, and the brightness settings were maxed out. I checked "auto adjust backlight" and the flickering stopped. Not sure why, but thought I'd add it to the thread.
Click to expand...
Click to collapse
Yeah I did notice that it's only really noticeable when the screen is set to max brightness. Setting it on auto adjust cleared it up for me also.
proj3ktpat said:
Yeah I did notice that it's only really noticeable when the screen is set to max brightness. Setting it on auto adjust cleared it up for me also.
Click to expand...
Click to collapse
thx guys...helped me out too...
Just sent my unit in for repair (under warrenty) due to the screen flicker issue, lets see what happens when it comes back.
I just started to experience the flicker today. Has be somewhat concerned. The device is only two weeks old.
However, it seems to have stopped by itself while I was searching the forums for an answer. If it returns, I'll try the 'remove battery' method and see if that helps.
Also, I love Scrobble! Shame it doesn't work on QVGA displays. Or, at least, didn't on my Wizard...
Related thread
Hey guys there's a thread with the same exact issue and a screenshot on the first post.
http://forum.xda-developers.com/showthread.php?t=535099
Seems to be something related to the Hardware 3D Acceleration driver for Windows Mobile, I get this problem only once 3d has been activated.
If Sense/TF3D is turned off, I never see this problem. It only comes up once a game or Sense has been launched.
I can also boot into Android without 3D activated and not have this problem, but if I run Sense then go into Android I get the flicker from a Windows Mobile screen while in Android.
protwitness: That doesn't seem to be the case (for me, at least.) I don't run TF3D and it still happens. I can't really discern what the trigger is, but I have a feeling it has something to do with the screen brightness auto adjustment. (Sometimes, I'll turn my phone on when it's dark and it jumps to full day-light brightness for some reason.)
I've adjusted to it and it doesn't really bother me any more.

HTC Diamond - backlight not off after inactivity - just fading out a little

Ok so I have a little problem with my HTC Diamond. In options I set to turn-off the backlight after 10s of inactivity which is standard. The problem is that after those 10s I can see that the screen backlight is fading out but it doesn't fade out completly - if you look from an angle it might appear that it's off but if you look at the front of the phone or simply in the dark you can see that the backlight is still on only set to something near 10 or 5%. As you know the battery just sucks in this device and I don't want the backlight to drain it so any ideas or tips on this matter? Of course I can put the phone to sleep mode but I'd just prefer to make the backlight turning off so I can take a look at the screen to for example check the time without having to press any buttons...
Same problem here
After those 10s the screen is not turning off completly, just fading to 5, 10 %. The screen with all the info, the home page let us say, is still visible and drains the battery. I also could just press the power button to turn is completly off, but I would also prefer it to do this manually after ten second.
Did you find a solution to this problem yet?
Help Battery Drain
Same thing here, and my Backlight is stuck to 100% i think,
anyone found a solution to this? any hints?
Guys, i assume youve set the "turn off device if not used for xxx mins" correctly whilst in battery and external power correctly?
If you have, what roms are you using as you give us no information to help any further
Hello,
I had the same problem with ROM 2.03.421.2, date 12/24/08.Back then I had SPB mobile shell installed and a very few applications and I couldn't find the problem. I made a hard reset so now, with nothing installed, the device also enters standby. You should take care because it is possible that the device is not entering standby either and it is making calls. When I had this problem my friends were complaining that I kept calling them and not talking. It is strange as I'm sure I put the device to sleep with the power button. But still, somehow, it was making calls...

Screen Timeout issue

I use an older Samsung Note 4 with the latest stock OS allowed for it. I have had an issue since day one that I can't seem to find a solution.
I want to be able to disable the screen from turning on, unless I hit one of the physical buttons (typically Home or Right side button). The reason is that notifications and other background processes keep lighting up the screen. Sometimes, the screen will just stay on and not timeout. Also, if the phone is in my pocket, it senses my body and starts interacting as though its my fingers. I am only aware of this once the phone heats up and then all my icons are messed up. The biggest problem is the battery drain from all this. Setting the timeout short does not really help and is kinda annoying itself.
I have not been able to find a setting or app than can suppress this. All of my searches just turn up the opposite solution to keep the screen active constantly.
Is it possible to disable the screen until an actual physical button is pressed? If so, what is the solution? New OS, new phone, app?
Thanks.

Question Screen brightness and power off issue

I don't know if this is a general issue or if it just affects my phone, but from time to time, the screen gets stuck on full brightness at some random point during the day (especially whenever I use Ambient Display and/or Lift-to-wake), and then it will refuse to turn off, no matter what I do (the screen shows pure black, but the backlight remains on). Understandably, the phone gets dangerously hot when this is happening.
The only way to "solve" the issue when it arises is a full shutdown or removing the battery, a simple system reboot won't cut it.
Is there anyone else suffering from this? Does it have any permanent solution?

Categories

Resources