Hey everyone,
Tried searching around the forums, but apparently this issue must be a rare occurence. This problem occured all of the sudden. The G2's LCD backlight is severely dimmed. I had tried disabling the automatic brightness and manually adjusting the brightness but even though the scroller moves freely from side the side, the backlight will only respond to such action for the first quarter of the scroller after that the backlight remains at the same brightness. Also tried AdjBrightness and behaves the same, the backlight won't change for values exceeding 50.
I am wondering if anyone here has experienced the same problems that I have encountered? Are there any solutions other than returning the device?
Thanks for everyone's time
Basic Info:
Rom:
T-mobile USA stock rom (Rooted / S-off / Unlocked)
Baseband Version:
12.22.60.09bU_26.02.01.15_M2
Kernel Version:
2.6.32.17-g814e0a1 htc-kernel and18-2 #1
Build Number:
1.19.531.1 CL255798 release-keys
I'm having the same problem with my Desire Z. My phone has always been kept in pristine condition but all of a sudden my screen just dimmed and no matter what I do to brightness settings it stays that way. I tried pulling my battery out as well but that didn't help either . The capacitive buttons and keyboard lights are working just fine it is just the screen that has gone very dim
EDIT: Wow, the problem just kind of disappeared on its own. I pulled the battery again and removed my case and the backlight magically started working again. Weird but I'm happy it's all good
I just had this happened to me. I have taken my battery out multiple times and it still has not solved the issue. Did you ever get your screen back to working normal?
Related
yesterday i bought an a8181 an with first boot i experienced poor screen brightness.with auto setting the screen doesn't adjust as should be. installed sensor test program and i've noticed tha sensor reading are stuck to 40 either on day or night,light or dark.only when i used a flashlight directly to the sensor an i show deferent readings.
also,video is very poor,very laggy in all settings and defferent ones.
i searched everything but no conclusion at last.
ps. my desire is stock and updated to the last 2.29.405 ,no screen protector or anything else is used.
ps2.pls help...
48 views an no answer?
the capactive buttons at the bottom of my defy flickers every so often. I seemed to have noticed it for the first time after rooting from stock to finland froyo with jboogi's deblur honey. this behavior persisted even after reflashing (to same finland froyo) a handful times (I wipe/reset before flashing). I just flashed to 3.4.3-11 blur UK froyo to use with Jboogie liquid arc ROM, and it still persists!
1)any solutions?
2)or suggest a more thorough method to reset/wipe i.e. fresh new start?
Thanks guys
Although you say that everything started after rooting, I would rather suspect a hardware failure. That might have been a coincidence!
My button flickers too. I havn't notice it earlier than today so I don't know when it started.
I'm running 3.4.2_155-002-deblur with some bloat APK's removed.
I don't think its hardware failure because it never flickers when I have the phone on landscape orientation. So that makes me believe there is something wrong with software controller fr the lights.
Solved!
wasn't aware that those lights also responded to the auto light sensor that controls screen brightness. The reason why the lights always came on when I held the phone landscape was because my finger was covering the sensor. haha
Hi Everyone!
So i got the OTA 2.3.4 upgrade for my TMobile G2 a couple of weeks ago and my keyboard backlight stopped working, I have seen many threads about this all over the internet (and very few actually here) but no one knows a solution to the issue yet. I was hoping someone can guide me here how to fix this. I know ultimate way to fix is to downgrade to Froyo.
I also have all the other issues that came with this "HTC screwed with" version of Android like constantly forceclosing with the dumb Tell HTC button, navigation icon disappearing when GPS chip is off, typing E sends me to short cuts, etc. The only real problem is the keyboard backlight because it has made the phone useless to me.
Thanks!
USA TMobile G2
Never Rooted.
OTA Upgrade to Android 2.3.4 with stupid Tell HTC app the only HTC footprint in the phone which is continuously freezinfg and forceclosing my apps.
Kernel 2.6.35.10-g96de068
Build Number 2.15.531.3 CL82286
Baseband 12.52.60.25U_26.08.04.30_M3
Without knowing too much about this particular issue (haven't heard of it personally) I'd say to do a factory reset, and/or dive into your auto backlight settings. The keyboard lights are tied to ambient light sensor.
Are you opposed to rooting? Sounds like you're having a lot of problems with your stock setup...
martonikaj said:
Without knowing too much about this particular issue (haven't heard of it personally) I'd say to do a factory reset, and/or dive into your auto backlight settings. The keyboard lights are tied to ambient light sensor.
Are you opposed to rooting? Sounds like you're having a lot of problems with your stock setup...
Click to expand...
Click to collapse
Actually the light sensor doesn't work either, I put the phone to my ear and my cheek starts dialing becuz the screen doesn't turn off, aft a minute it does automatically though. Then I pull the phone away from my face to hang up or dial an extenstion and the screen is off, I have to push the power button and slide to unlock.
I had rooted my old G1 and I had so many issues and speed problems that I figured I don't do that to this phone, it worked almost perfect with Froyo with a few issues but this one without keyboard backlit is 100% useless.
There is no setting in my setup for keyboard backlight or light sensor.
Well it definitely isn't a keyboard issue then, its a light sensor issue.
I'm not aware of any way to calibrate a light sensor etc. but maybe someone can add their input on that.
I know that if you are willing and able to root, you can flash a pre-rooted stock ROM or custom ROM and you won't have this problem.
I just found out when I change the screen brightness the keyboard light turns on, after I finish typing shut the keyboard and open again it doesn't turn on anymore. I can go back to home page tap the screen brightness on the widget and turn the keyboard light back on again.
Sorry to Bump! But please help! I tried rooting my phone but its just too many steps. I installed Android SDK which is hundreds of megabytes and was stuck there. Too difficult to use (I rooted my G1 many many times and installed various ROMs including CM7 so I am very familiar with rooting). I tried rebooting and erasing the phone to factory setting and still the same issue.
Thought I'd share my experience about this. I was running Paranoid Android 0.9, no issues at all. One day I was talking on the phone and noticed the screen flickered quickly... then it just stayed on. I hung up the phone a minute later not thinking much of it.
Well today I made some phone calls and the screen never turned off.. I had to manually turn it off via power button. I installed Paranoid 1.1, no changes. I flashed Trinity kernel, no changes. Just a bit ago I fully wiped the device and flashed the latest 6/4/2012 CM9 Nightly and the issue is still present.
At this point I'm guessing there is definitely a hardware issue. I have never dropped this phone and it's in mint condition aesthetically. It's the GSM version bought via Expansys.. and I won't waste my time with warranty through them I'll just bare with using the power button to turn the screen off/on during calls.
Another note, I noticed if I tap or press firmly on the proximity sensor area during a call it will trigger the screen to momentarily turn off.
Could this possibly be a CM9 issue (Paranoid is built from CM9)? I may try flashing a rom not built from CM9. I've searched high and low on the internet and NO ONE has had this issue which is leading me to believe that there's no way this is hardware related.
All roms are based off of AOSP.
I guess I'm the only one.
There are some apps that can test your Proximity sensor, though I can't remeber the app name.
/Edit: Link to the app.
Have you tried franco kernel to check if this happens aswell? You can then pin down the possible kernel related issues.
Firmware again plays a major factor? What firmware are you on? Mines came as an OTB 4.0.2 and I too had this similar issue where I had to manually swipe my finger against it, Upgraded to 4.0.4 and the issue went away. Weird.
Misledz said:
Have you tried franco kernel to check if this happens aswell? You can then pin down the possible kernel related issues.
Firmware again plays a major factor? What firmware are you on? Mines came as an OTB 4.0.2 and I too had this similar issue where I had to manually swipe my finger against it, Upgraded to 4.0.4 and the issue went away. Weird.
Click to expand...
Click to collapse
I'm on 4.0.4. I just flashed Android Revolution (4.0.4 based rom with the stock kernel) and the problem still persists. It's very intermittent. Sometimes the proximity sensor detects an object close thus turning the screen off, but it only turns it off for 2-3 seconds or sometimes not at all. I wonder if a piece of dirt/dust is sitting right on the sensor?
I tried a couple proximity sensor testing apps out there but none of them work and say "If your reading displays nothing or the maximum value then your device does not support reading of proximity sensor values".
The apps display a max of 5cm with a resolution of 5.. and the current value is ALWAYS a 5.
I just find this hard to belive I'm THE ONLY ONE on the interwebz, out of MILLIONS sold, who has reported this problem.
Ok, I'm a complete idiot....
Turns out the Galaxy Nexus proximity sensor ONLY works when the phone is in the upright position!!! I kept testing it with it flat on the table and, by design, it's SUPPOSED to keep the screen lit.
I had been running on a late May build of Lineage OS until recently without issue (5/17 I think). This week I updated to the most recent build and have noticed that one of the apps I've used for years has started behaving strangely. I use "Screen Filter" overlay app to darken my screen and turn off the hotkey lights overnight. Since updating I have found the app is behaving strangely after my phone has been idle for a while. The notification for the app still shows up, but it is set to a different brightness level than when I originally enabled it and the hotkey lights are reactivated. Since this happens while the screen is off for extended periods but doesn't seem to be an actual crash of the application I am at a loss for how to diagnose the problem. I rolled back to the July 26th build (the oldest download I could find) and this issue is still occurring, but I am not knowledgeable enough to know what might changes occurred between 5/17 and 7/26 that might cause this behavior.
Any suggestions or ideas on what might be the culprit and if there's any solution besides sticking with May software if I want to use Screen Filter?
Thanks!
<Mod Edit>
Reposted here:
https://forum.xda-developers.com/galaxy-s5/help/s5-klte-lineage-os-screen-filter-t3682337
Thread closed.