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.
Related
Has anyone else noticed their Dash's keyboard backlight not turning off? Very frequently (but not always), the keyboard backlight stays on (and doesn't turn off) after I initiate keylock. The lcd dims and goes off, but the keyboard stays on and won't go off on its own - so far, I've timed it staying on for a whole hour after initiating the keylock. I have to undo keylock, redo it, and sometimes do it a couple times to end up with the Dash locked and the keyboard backlight out. As you can imagine, it's a real drain on the battery, not to mention a real pain.
Has anyone else noticed this, or know what might be causing it (maybe a bug or something I've done)?
I was just going to write about this, but you beat me to it. Happens to me as well, randomly. I don't know if it is a program that is running on the background when the LCD shuts off, but it is very frustrating. Any ideas?
I've noticed it, usually after the device reboots -- stays on until I hit a key, then it'll time out normally. Probably one of those quirks that'll wind up fixed in a future ROM update.
chaznet said:
I've noticed it, usually after the device reboots -- stays on until I hit a key, then it'll time out normally. Probably one of those quirks that'll wind up fixed in a future ROM update.
Click to expand...
Click to collapse
I was wondering whether a background app was causing it too. I'm new to Win Mobile smartphones, so I'm curious what the likelihood is that T-Mobile will actually release an update for the Dash (at least to those that have already have the Dash), and if they did, how they might go about deploying it (user install made available by T-Mobile, T-Mobile install, or user having to install leaked/hacked ROM's made available on sites like this)? I've been a T-Mobile customer for many years, and at least with my previous phones (non-smartphone), T-Mobile hasn't had the best track record with firmware/software updates. New firmware updates would be released by the manufacturer, but T-Mobile would always claim they didn't have any updates available.
chaznet said:
I've noticed it, usually after the device reboots -- stays on until I hit a key, then it'll time out normally. Probably one of those quirks that'll wind up fixed in a future ROM update.
Click to expand...
Click to collapse
That's strange - hitting a key on my Dash doesn't get it to timeout! In fact, it seems that the keyboard backlight goes out, and then about 10 seconds later, relights (and won't go off). Very strange!
I've noticed a lot of bugs that T-Mobile needs to fix with the Dash: The XT9 bug, keyboard backlight, the call status screen showing gibberish (when using MS Voice Command to initiate a call), WiFi having problems connecting. Here's hoping to a quick update from T-Mobile!
Hello,
I got a problem with my flashlight.
It turn's randomly on and off but it's only for about a second.
It doesn't matter if the device's screen is off or on or if the device is connected with the pc or not.
Also the flashlight turrns on for about a second if I restart my device. The flashlight turns on and off and then the screen lights up.
Is there a known bug with an app or radio? I tried already two different roms and two differentt radios.
If there is no way to solve the problem, is there a way to deactivate the flashlight so no app can use it?
greetz Nightskill
Hello all,
I found out, that the Flashlight turns on if I touch the Desire at the top left of the phone. Exactly at the intensity and proximity sensor.
Is there a known Problem with the Desire?
Never heard of it before, but damn that must be annoying
Are you using original rom?
Yes, It's very annoying...
Yes I'm using a pre rooted original Rom. But I tested already other roms.. same problem...
Sent from my HTC Desire using XDA App
Sounds weird, but if you did not do a full wipe when switching ROMs then that may be a cause I'd imagine.
how about removing the Flashlight.apk and install it again
have you tried other application for use the LED as flashlight, like teslaLED etc?
Having the some problem here, and my charge led light has also stoped working but the battery is charging, what can I do do fix this beceause its not showing indications
Very same problem with my Desire. Did not install any custom roms, only the updates that came automatically from HTC.
Yesterday did a 'hard reset', (reboot with volumn down button, and choose 'clear storage', but this did not help. I only needed to install every program i again
On the other hand, maybe this was not a real 'hard reset', because the HTC is still on the 'updated version', not on the android version as it was when I did purchase the phone.
Version now is: 2.29.405.5.
It looks like a bug in the system, not a hardware problem, because the flashlight does work sometimes (as described in the first post).
Searching the internet did not work, there are more people with the same problem, but not any solutions (yet).
Any new Informations?
I'm now using CyanogenMod 7 (7.0.3) but the issue is still the same. The radio is upgraded to the newest version. (32.54.00.32U_5.14.05.17)
Is it possible to swap the LED (and Camara) Modul (or board) without replacing the whole mainboard?
Me too
I got the same problem.
bad luck~~!!
I tried many ROM or RADIO or RECOVERY,but can not slove this problem.
The Problem still exists, but I got interessting news.
The problem is caused by the Proximity Sensor.
You can test this very simple:
Download an app which shows the value of your Proximity sensor.
Hint: My Desire only shows 0cm or 9cm value. This is normal, because our sensor is not capable of reporting all intermediate values. Then just hold something in front of the Proximity Sensor (left top of the Phone) and remove it. The value will change and after you removed the thing, the flashlight will switch on for some miliseconds.
Unfortunaly I don't know how I can solve this problem. I also don't know wheather it is a software or hardware problem.
I hope somebody can give some hints or something else.
I am on CM 7.0.3 and I should admit that I use the flashlight quite often. On the high brightness option.
Everything was ok for months but now I get a blueish tint when the flashlight is on. For example, if the normal colour is white (around 6000k), now I get 8000k. Moreover, the led is not as bright as it used to be.
I have never used the torch app, for more than 4-5 minutes constantly on.
Is the led dying?
Got this problem two times already, not even flashing with RUU helped.
Returned my HTC for warranty, when it arrived flashlight worked fine (as per return slip, some module was replaced) but the light sensor was screwed. During phone calls LCD stayed off all the time, it worked only under direct strong light. went back for repairs this time got mainboard replaced.
After a while flash stopped working again and soon after, or maybe at the same time, LCD stopped turning off during phone calls and touchscreen stayed active.
Went for another repair. not sure if i want the same thing to happen again, if it does, i should get a new phone, but i know that it will be a lot of hassle.
Same problem here. This morning the flashlight was working without problems, now it's dead. So this could get the 3'rd mobile replacement within 2 weeks, the 4'th at all. I've already tried CM7.1RC, InsertCoin1.1.0 and the original RUU - no effect...
Now I'm thinking about returning the mobile (possible after 3'rd replacement/repair when You can present the failure in the shop) and ordering a HTC Sensation instead... Maybe this will be better ???
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
I've been using this phone for over a year w/o any problem but lately, since I last update some apps (and only apps, no android vers upgrade) my speaker phone seems to be glitchy. During calls, the speaker phone always turn on all by itself as if it was set on by default.
Is there anyway I can make the speaker phone to be the way it used to be? As in only turn on only when I tap the icon? Because I can't find any setting at all that deals with this.
A further info, there seems to be a glitch that the car panel apps also turn on by itself twice even without ever using any dock at all. Might it be if in car panel mode, the speaker phone was defaulted to on? FYI, I've never even used the car panel apps before, therfore it's strange that it does turn on out of a sleep/lock screen. I've turn off the auto launch so it never turn on again, but the speaker phone prob still persist.
Android ver 2.3.3 Sense 2.1 no rooting.
If the only solution is to hardreset, anyone know how I can save all my apps state so I can restore later? Installing the apps all over again seems to be a major headache.
Had that issue on my inspire, when ever i answer a call it would automaticaly go to speaker but i was rooted and on a custom rom. I unchecked quite ring on pickup , pocket mode, flip for speaker, and havent had the issue ever since
I've just try that, but sadly no, it's still doesn't fix it.
The only time it didn't turn on speaker phone was if I use ear phone.
I'll try to get 2.3.5 update and see if it help for now. But currently, the update still have't available yet.
I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?
I experience the same thing sometimes with stock rom
keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...