Completely turning off the backlight - Touch Pro, Fuze General

I noticed on my old Dell Axim x5 that I have the option to completely shut off the backlight, but still be able to view the screen in a lighted environment. I also noticed this on the outer screen of my Razr, which also turns off the backlight, but maintains the display. The problem with this option is that I cannot see the screen in complete darkness, but it saves battery power. However, this option is not available on my Fuze, even with the latest version of Lumos, I cannot completely turn off the backlight manually, or adjust the settings to turn the backlight off when it idles. Is this a hardware limitation with this type of LCD? It has the same TFT resistive touchscreen as the axim. Or can/has this been programmed around before? Any thought-out answer will be greatly appreciated.

Related

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.

Standard Locking Screen wm6.1 reacts to touch

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.

[INFO] Capacitive Buttons

The bottom row of 4 Capacitive buttons do not light up as bright as The other galaxy S phones. This is Normal, not sure why (maybe battery life). I went to the AT&T Store today thinking that my LEDs for these buttons were doa, however every model phone they had are the same.
Just letting everyone know.
Maybe there is just a Root Setting to Change the brightness of them, but we will have to see as Development Continues.
I'm fine with the brightness, i'd rather have the timeout fixed. Everyone is having this issue. I also would like to have the option to change lock timeout screen.

[Q] Disable diplay locking: suggestion

Hi. so, i hate the display locking. this causes to me pressing anytime a button to unlock. so i thought: why not using a screensaver that disable display locking? and why not a black screensaver to preserve battery life? so, starfield screensaver is the solution! but it has animation. so i think someone could makes somthing like that, but with black screen. what do you think?
The thing that consumes power on an LCD is the backlight, not the pixels (technically the pixels take a little, but it's minimal, and it's the black ones not the white ones). On an AMOLED screen, the power consumption is all in the pixels, and only non-black pixels draw power.
You'd either need to find a way to turn the screen "off" (the way the OS does when locking) or you'd only ever be able to stop screen power usage on AMOLED screens.
i have an AMOLED display super amoled exactly
is there a way to get a free compiler or source code from starfield's app?? only source code could be good, so i could change it and someone could compile that, and all amoled owners could be very happy

Always On Display ignores proximity sensor

Hi all,
I just got a 2018 Galaxy A7 this week.
I can't get the Always On Screen to function correctly.
When the proximity sensor at the top of the screen is covered, the screen will fade all the way down, but not shut off completely.
If I leave the phone face down on a table, I can see the screen dimly reflected off the surface if I turn the lights off.
From the manual: "If the sensor at the top of the device is covered for a certain period, the Always On Display will turn off". So it should turn off if face down, in a pocket, etc?
I tried setting "Block Accidental Touches" but this makes no difference. Same for a factory reset in case something I installed was holding the screen on.
Am I missing a required setting?
With thanks
Also: I checked with the built-in tests (dial *#0*#). The proximity and light sensors seem to work ok, so this appears to be a software or setting issue? Or a mistake in the manual?
I confirm that the aod will automatically turn off if I put my phone into my pocket. But I afraid of the burn out of my display. The aod seem to stay the same position in a very long period and there is no option to set up the period for the movement of the aod. Maybe I will turn this funtion off.
Thanks for checking. I'll contact Samsung about this.
I don't know if you need to worry about burn in, the clock and other information seems to move around often enough. Even the home button moves slightly to avoid issues. They've used these screens with these anti-burn in measures for a while and there hasn't been a large number of complaints.
Yeah, A7 has this function and I worry about the burn in of its screen but it do not have LED notification and because of that I must use aod. But the A6, my wife's phone, do not have aod and LED notification. Why Samsung did not support LED indicator for A series? It so annoying.

Categories

Resources