Screen will not turn back on once phone is put to sleep or if the proximity sensor turns it off during a call. Very annoying, have to soft reset constantly. I currently use Android on my phone cause at least the screen will turn back on when using that.
Right now i have a stock 6.5 t-mobile rom and have tried several other roms as well.
Any suggestions?
Yep, easy fix, I posted this several weeks ago:
With the tilt 2, if the screen does not wakeup, but you can answer the phone, hear music, etc..., it is a malfunctioning light sensor, maybe hardware, or software related (drivers), but it is fixable. Just eliminate all calls for use of the light sensor.
I had this problem and took quite a while to figure it out, as there are several apps that poll the light sensor that cause problems.
First, go to start/settings/system/power/backlight and uncheck the auto adjust backlight option
Second, go to start/settings/personal/buttons/backlight and uncheck the enable keyboard auto backlight sensor.
Last, open advanced config (need to download and install from touchxperience.com, if you do not have it), tab to light sensor and set light sensor polling to disabled.
Now, my phone works normal and will wake up properly from standby like it should. this all seems hardware dependant, as I have in my family 3 of these things and I dropped and broke mine, so bought a new one (4th in the series) and it had the SOD issues, but could restart with softrest. Took me the better part of the day to find a reliable fix, but now all is well again.
Hope this helps other Tilt 2 and similar issues.
There's a lot of reasons for the SOD. The methods above probably worked for some people but never did for me. If they don't work, i'd suggest taking your your micro sd card, running scandisk on it and seeing if there are any errors. I had to switch cards because my card had errors on it. Haven't gotten a SOD since.
Yes, that was the first thing I tried on mine, because I changed the SD card with the new phone, but no errors found, so I kept digging. Stopping the all calls to the light sensor was all that worked for me. There are typically 3 culprits, bad light sensor, bad or overwritten drivers for the light sensor and sd card or ROM errors. All hard to fix and just have to keep trying, or go back for warranty replacement and hope the next one works. For me, only 1 out of 4 in our household has this problem and they essentially all have the same software, ROM and micro SD cards in them. Go figure.
hi, i have the same problem with the sod. i installed the rom from comec. then i deactivated htc sense on my phone an installed spb mobile shell 3.5 and i have no sod
Related
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 ???
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.
Hello! Firstly I'd like to say thanks to any regular posters, this site helped me root my phone in the first place! I am trying to sort out what might be the cause of this problem and remove it, hopefully without starting over, as it was a pain in the butt to get the phone set up how I wanted and I do not have a full night to commit to it at the moment.
I have a Samsung S2 (the t-mobile branded one, sgh-t989), android 4.1.2 (kernel 3.0.31-1003885). This problem is recent and came on suddenly without changing any settings or installing any new software. The phone behaved normally for the first few months I owned it, it is a used phone, however, and I have no idea how the original owner treated it.
The problem is that brightness becomes tied to one or more of the sensors, and it takes several restarts, or sometimes days of waiting for the problem to go away. The brightness most often becomes tied to the accelerometer, where having the phone pointed at 45 degrees (or 01:30 o'clock), results in near 0% brightness, while returning to full brightness at 90-0 (or 3 through 12 o'clock). Occasionally it ties to another sensor (proximity?) or changes seemingly randomly, and once or twice has tied to the compass, with North being the brightness sink (with a similar 'darkness range' to orientation). The problem starts without a discernable cause.
Whatever the problem is, it also appears to disable, or for the most part inhibit multitouch. Around the time the problem started, tasker disabled and refuses to re-enable, if it is relevant. Shortly after the problem started, any push notification began turning on the screen (with a normal timeout, however). The problem persists through changing of any of the settings, toggling any modules, and through multiple resets, and never resolves itself without a cycle of multiple pulling-outs of the battery. After it is resolved, it usually remains fixed for a day or so before re-appearing.
If anyone has any suggestions for chasing down the problem, or has heard of anything similar, I'm all ears. I would like to avoid doing a factory reset, especially since I have no assurance it will resolve the problem. I'm happy to provide any additional information. Thanks for your help!
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...
Hi everyone.
I have a note 10 + 256 go exynos from france.
SInce about last update one ui2.5, I have seen 3 issues which I think are related.
- AOD tap to show not working
- Double tap to wake not working
- When I remove the phone from the ear during a call the screen does not light up anymore whereas before yes.
I almost returned the phone in warranty a short time ago because my screen only registered two fingers,a few days later I received an update that fixed this problem.
For these 3 problems I tried 3 things :
- Update touch screen firmware via *#2663#
- Factory reset
- Reflash the stock firmware with odin and frija
I also have another problem a few times a day the screen freezes, I have to lock unlock the screen and it works again..
Do you think it's a software problem or a hardware problem (damaged screen, damaged sensor or other)?
Please help me thanks.
Lol, firmware and/or software; maybe a settings or permissions issue as there are many. Hardware rarely fails unless it receives severe abuse. You can perform some of the builtin hardware tests just to be sure.
Try using the factory load if the apk in question has been updated or wait for an update that fixes it. Be sure to check the Gallaxy Store for updates.
I'm still running on Pie because it's fast, stable and functional. No scope storage that I don't want or need.
Once you get an OS optimized and running well there's little advantage to upgrading many times unless the new OS is really worth it.
Many times it's not... I'm still running W7 too.
You invariably end up with new issues, hunting down all new glitches and worse, since it's new there not many online solutions.
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Those are all system apks that run in the background.
Is Android System configured correctly?
Try clearing it's data and of course the system cache.
A hard reboot as well.
It's interesting you lost the proximity sensor.
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
cyroko said:
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Click to expand...
Click to collapse
cyroko said:
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
Click to expand...
Click to collapse
If it happened after the firmware update... it's in the firmware or software.
Bad firmware can sometimes blowout a cpu but doubt it damaged the hardware controlling just that one feature of the touchscreen.
If that was the case the touchscreen wouldn't work at all.
Maybe the firmware is ok but got corrupted during the download or flash.
A defective memory module could corrupt the load but again that rarely happens.
So back to the firmware/software/settings...
Maybe someone here has seen this before or has a better idea to sort it out.
Honestly I'm not sure it's exactly after an update.
It's just that it's not functions that I use very often. I don't call a lot of people and most of the time I use very little Aod and double tap2wake.
Usually when I grab my phone to use it I unlock it directly with the fingerprint.
when i mentioned the problem where my screen only recognized two fingers at this time , aod and dt2w were already weird as it only worked on the top half of the screen not on the bottom half ..the update solved the problem for the 2 fingers but not for the fact that aod and dt2w only works on the upper half.
Now for some time aod and dt2w no longer work at all no matter where I touch the screen.
I want to clarify that I use a screen protector with loca glue but that it is from the beginning and that it has never been a problem before.
I know this is a weird problem thanks for your patience
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
2x post
when i did the factory reset it was the first thing i tried before even resetting a password but it didn't work anyway.
For the screen protector I use the same brand from the beginning and it has never caused me a problem of this kind, but maybe this one is defective ..
I would have to remove it to try but I have lazy to change it again because I had to change it twice in a little while.
Hoping that by dint of applying the loca glue I haven't damaged anything.
Thanks
Nah the glue didn't hurt anything; it's well sealed.
The tap on AOD I never use but I double tap to turn the screen on/off. If I lost that I be witch hunting.
Try increasing the touch sensitivity if you haven't already... and make sure no other apps have accessibility permissions that could conflict. Same for device administrator permissions.
Try it in safe mode as well.