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.
Related
So I've have been having this issue on and off with my phone I have the Rhod210 US T-mobile Touch Pro2 with the most recent Energy ROM and for a couple months now the screen will randomly change orientation and it will do it constantly even if the phone is closed and on a level area. I also have an issue where this will happen after the screen has been turned off, after a minute with the screen off the back light will come on and the orientation will keep flipping from Horizontal to Landscape over and over again.
I have an overclock set on this phone but I didn't have this issue until weeks after I had my overclock set
Anyone else having this problem? Is my phone broken?
Is there a fix for this that I don't know about?
Thanks in advance guys
Honestly, it sounds like a faulty G-Sensor. Flash a stock ROM and see if the problem persists.
I calibrate the G sensor and it still doesn't make a difference. It seems to just happen randomly and for a few minutes or sometimes a whole night.
You should flash a stock ROM to see whether this is a hardware issue or not. If it happens on a stock ROM with nothing installed, then it is hardware. If it does not happen, then you've got a problem with the software on whichever ROM you're currently using.
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 ???
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.
So.. i have had a weird problem for quite awhile now but have been putting up with it..
When on a voice call when the screen goes off it will mute the mic, leaving the other person asking if i am there.. i have to shake the phone or hit the power button a bunch. It also doesn't wake up instantly when that happens, almost like its in a deep sleep. I don't have any battery saver apps or anything installed....
I am using CM11 right now with FL24 modem, i have tried other modems.. same issue.. This issue also happened on other roms incluing vanir and others...
I did a search and found one other person with the same exact issue.. but no fix posted, was hoping someone might have an idea on how to figure this out.. thanks..
Experiencing Similar Problem
I've been experiencing a similar issue for a bit over a month, too. I'm not quite sure if it was when the screen went off, but certainly within 15 seconds of making or receiving a call my mic cuts off. It sometimes comes back after -- I don't know if that's because I shake the phone around or otherwise get the screen to come on, although the mic turning back on and the screen turning back on do not happen at the same time.
I'm also on CM11 with FL24 modem on a Samsung Epic 4G Touch, which makes me suspect it's the same problem. Do you have a link to the other forum post?
I suspect it's a relatively recent regression with CM, because I installed CM11 on the phone at the end of October and everything was fine. I first started experiencing the issue a few weeks thereafter. I can't recall if it happened after upgrading CM, or if It was after I installed Google Voice (since removed,) or if there was no particular prompt.
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...