Develop Bugs

Rooting triggered proximity sensor issue?

Hi all,
I recently received a replacement Desire for my 'faulty' one. I tested all basic functions before walking away and everything checked out.
After I rooted it and installed Modaco r17 ROM, My proximity sensor sensitivity dropped dramatically. When I make or receive a call, the screen blanks as it should, but when I move the phone away from my face, it stays blank. I can't end the call or use speakerphone or keypad. The only way to bring the screen back is to hold it under a very bright indoor light, or direct sunlight...or pull the battery, of course.
I loaded a sensor test tool (SensorList) and it confirms that the sensor is reacting only to very bright light. I've checked that my cover doesn't obscure the sensor and tested that the behavior is the same with or without the screen protector.
I tried a couple of other ROMs, Modaco r19 and Shadowfrost v13. I un-rooted my phone and dropped a stock HTC ROM back onto it...and the problem is still there!
I'm waiting on a reply from HTC service about it...but in the meantime...any advice? I've seen a few posts around the web with this problem, but no definitive solutions or answers.
Question Added to Developers
I've noticed a smattering of people in various forums, with various of the newer android phones having proximity sensor problems. Perhaps these are not quite as finely calibrated as the other sensors, or not as reliable. Have any of you developers seen a way calibrating or adjusting the sensitivity? Perhaps a value in a system file we can change?
Thanks in advance.

Added question and bumped
Apols if this is pushy. I added a question to you developers, so giving this a bump.

phantomfisho said:
Apols if this is pushy. I added a question to you developers, so giving this a bump.
Click to expand...
Click to collapse
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.

Daelyn said:
FYI:
Proximity and Light sensor does not work with Sensor List in a Froyo ROM. Tested it myself just now.
Click to expand...
Click to collapse
Images:
1. Holding hand over phone screen
2. Clear view of the screen in dimly lit room (it's quite cloudy )
3. While running FroYo
This does seem like Sensor List correctly detects and measures the proximity/light sensors in FroYo on an HTC Desire, or am I mistaken?

Ditto Issue
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.

nayajoeun said:
I have the exact same issue as yourself and believe that the problem itself started after I rooted my device.
I am yet to take it back to a Telstra store however as there is no un-rooting method I can think of. (The Telstra ROM will not install on my rooted handset due to incompatabilities that arose from rooting the device.)
Your best bet is to get it replaced again because I've flashed every WWE and custom ROM known to man in order to fix this issue and have had no luck.
Some of the responses you'll receive here are just ridiculous (no offense, as that comment was not directed at any of the above parties).
Hope it all works out for you mate,
Cheers.
John.
Click to expand...
Click to collapse
Thanks John. I tried the same thing with the same result.
I ended up taking it in to HTC. Luckily I came across a good service rep. He said they'd seen some quality problems with the first batches of Desires and mine was not the first faulty proximity sensor they'd seen. My guess is the timing with the rooting was coincidental.
They would have replaced it, but they didn't have any replacement stock at the time...more evidence of early quality issues. They gave me priority and repaired it in 24 hours. It's been running fine under a number of ROMs since.
BTW I had problems de-rooting and reloading the stock ROM. Then I realised I just had to have the original goldcard in the phone and presto! One day I'll learn to RTFM properly.
Cheers mate and good luck with yours.

I have also this problem. When I make a phone call screen goes black immediately and there's nothing you can do. After the call is over I can wake up screen by pressing power button. I'm not sure when it started because there's been so many variables. I even destroyed my invisibleshield thinking it caused the problem.
Sensor list and sensor dump says that max value for proximity sensor is 1. Screenshots above there was at least 9. Also light sensor doesn't work at all.
I tried to unroot and go back stock but the problem still exist.
Have anybody found a way to control these sensors or do I have to send my phone to HTC to get it repaired?
Thanks in advance!

Hi, I have the same problem here with my proximity sensor since I have used a custom ROM (I don't remember wich one because I have tried so many Froyo ROM before the OTA).
I can't send my desire to HTC because my phone is out of waranty since I have installed all these ROMs.
Does anybody's got an idea, some help from devs ?

OK,
Maybe I'have found a solution to the proximity sensor's problem... At least my proximity sensor is working normaly now.
What I have done (you can found all in the xda posts) :
1. Going back to Hboot 0.80 => forum.xda-developers.com/showthread.php?t=741672
2. Rooting the desire and install the new recovery using unrevoked
3. Installing the OTA 2.2 without the Radio 5.09 (not a leedroid or djdroid or any other ROM, just a 2.2 rooted)
4. Configuring my phone
5. Installing the 5.09 Radio
I don't think that I have doing anything else, but now I can call someone even in the dark and my screen doesn't stay blank anymore !
Hope this could help someone.

Touch Screen Unresponsive Gap ( a few seconds )

I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?

That doesn't sound like a common issue, and it's possible you might have a hardware defect with your phone.
I'd flash it back to stock, or as close as you can find, and take it back to wherever it was purchased for a replacement or repair.

raulttro said:
I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?
Click to expand...
Click to collapse
mine does the same with stock, but its not that common it happens like once a week for like 2-3 secs, and you dont need to have apps running, i just took it as it is

I m having no such issues in my DHD and i have used ARHD since very early versions.
Are you using any programs like setcpu or cpuspeed? Which kernel are you using?
If you have your htcsense account on, it would be a better idea to turn it off as well. And finally you can recalibrate your G-sensor (settings ---display)

I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.

Ah! ok...it is really a strange problem though, i would say. I never had this issue being touch unresponsive.
Yes of all the ARHD builds 2.0.15 is the best one, IMO. Well, the GB build is still in beta and it lags. The battery life is claimed to be slightly better though. But i could not live without search function (which FC all the time), the tweaks we have for Froyo builds and the overall user experience with froyo is just awesome...and Mike has done great job. At the moment the version i m using is priceless...

Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew

MattOsprey said:
Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew
Click to expand...
Click to collapse
You have a similar problem as mine, but not so often.
What do you mean by a serious problem? It depends if it is disturbing you or if you can live with it. It won't get worse as I've seen it is not a hardware problem.
You can do the test by installing CM7 ROM and check if it does again. For me that solved the problem, but as I like to use HTC Sense, it is not an option to stay on the CM7 ROM.

raulttro said:
I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.
Click to expand...
Click to collapse
Just a really wild guess, which launcher are you using? As I'm using launcher pro plus and it has a tendency to freeze after restart and the screen has no response for a while, usually it force closes automatically and restarts instantly after and works perfect. I'm on CM7 latest nightly and haven't tried other roms for a while so it might not be comparable. So if you are using launcher pro then try to manually restart it if it doesn't force close itself and start again. And if you're not, well just ignore this

Phone switching off problem in call.

Hi, I'm having a problem with my Desire, whenever I am phoning someone or recieving a call the phone screen stops working and shuts off, plus none of the buttons work. I have to remove the battery or get the other person to end the call in order to get it working again. The speaker still works though. Any things I should do before I restore. Oh and I am rooted running the latest Acesmod Rom.
Sent from my HTC Desire using XDA App

So you cannot turn on screen by just pressing power button? Turns the screen immediately off when you receive / make call or only when you hold near it your ear?

All the buttons are unresponsive. And no I'm not holding it up against my ear. Thanks for trying to help though.
Sent from my HTC Desire using XDA App

Nevermind I've fixed it. I found a post that said to try blowing between the screen and ear piece. And to my suprise it started working again.
Sent from my HTC Desire using XDA App

Sorry to bring this old thread up again, but I believe I have a similar problem and don't find a solution: sometimes my desire freezes or crashes, I'm not sure, but I can't wake it up from standby and there's no reaction to the buttons either.
I know from my girlfriend that she tried to call me in that state and to her it seems that I'm not picking up, which is why I think that only the screen freezes.
Also when it is not in standby and I get a call, the screen sometimes freezes and I can't get any reaction of it.
In both cases, only removing the battery helps.
I've encountered this problems in 2 custom roms, at first Reflex S 2.1.7 and now Redux2. Here are some specs:
Rom: Redux2-31.08-TEST
Android: 2.3.5 rooted
Recovery: Amon Ra, have to look up the version...
Radio: 32.56.00.32H_5.17.05.23
Kernel: 2.6.35.13-stable [email protected] #1
Screen should be SLCD, but how can I check to be sure?
Stock partition layout, S-On, PVT4, I did not change the h-boot...
sd card: 16gb sandisk: 1 gb ext3 for app2sd+ and dalvik cache, rest fat
To flash redux i wiped data, cache and dalvik cache
Does someone know how I can fix this? Or how I can find out if an app is causing the problem? Or if blowing between screen and earpiece really should solve the problem, why this occurs?
I really love my Desire now that I have som much more space than on stock Froyo, but if it's so unreliable for calling I will have to revert back...

Cpu setting...??
Sent from my MT15i using Tapatalk

taaviu said:
Cpu setting...??
Click to expand...
Click to collapse
For Redux:
ondemand, 245-998, did not change that since flashing. Freezes happened with both lower cpu when screen off (screenstate scaling) turned on and off.
Don't know for Reflex, if it was even possible to change anything I never did, so it was the standard...

lunovis said:
Or if blowing between screen and earpiece really should solve the problem, why this occurs?
Click to expand...
Click to collapse
Maybe a chunk of dirt/filth gets stuck in the groove there and tricks the proximity sensor into thinking the phone is always close to something so it turns off the screen as it's meant to.
As for the issues you're having, I have a PVT-4 Desire as well and I've often found that I get odd little issues with otherwise solid ROMs that most folks dont seem to suffer from. I usually wind up doing a complete wipe/format and reinstall the ROM to ensure nothing has been left over from an older or other ROM that's causing issues and that normally fixes most my problems.

azraelb said:
Maybe a chunk of dirt/filth gets stuck in the groove there and tricks the proximity sensor into thinking the phone is always close to something so it turns off the screen as it's meant to.
As for the issues you're having, I have a PVT-4 Desire as well and I've often found that I get odd little issues with otherwise solid ROMs that most folks dont seem to suffer from. I usually wind up doing a complete wipe/format and reinstall the ROM to ensure nothing has been left over from an older or other ROM that's causing issues and that normally fixes most my problems.
Click to expand...
Click to collapse
Well, I don't think the problem is related to that, because a friend of mine has the same problems, and has no PVT4 Desire...
could a slow SD Card or an app cause the problem?

[Q] Weird keyboard behavior in 2.3.x (official and Cyanogenmod 7.2)

Hi. I have been having this problem for some time now. When I install any firmware based on gingerbread, my keypad behaves strange: the space bar doesn't always work, works only about 50% of the time. It does this only if the phone is rotated to the left. when I hold the phone straight up, the keyboard works just fine, and it even works fine when I rotate it to the right. When I install any official firmware based on froyo, the issue is gone. Even when I use the unofficial Cyanogenmod 7.2 the keyboard annoys the hell out of me. I have tried some official firmwares based on gingerbread and all of them had this issue. It is like if the few millimeters on the left side of my phone were not touch sensitive... I did many formats etc. and nothing helped (only installing 2.2.1 fixed it). Anyone had the same issue? Or knows of any solution?
Thanks.

Maybe calibrating sensors ??
Sent from my GT-S5660 using xda premium

I think I have the same issue with CM 7.2 (dunno about 2.3.x, I was on 2.2.1 before going to CM7.2). For now I just use SwiftKeys and type in portrait mode.

Can I calibrate the touch sensor somehow?

i had the same problem + the " . " key didn't work
the solution for me, as strange it may sound, was to (re)install gapps. the only version that worked was this one
if you run out of options, feel free to try it.
ps: must flash it in cwm recovery mode

I tried the google apps but still nothing. Any other advice? I downgraded the FW - I'm currently using the official S5660XXKC5 (2.2.1 Froyo) and the keypad works flawlessly. That's really weird. Why is it broken only in gingerbread? Well I don't know why I should use gingerbread anyway, because my experience is that it eats more RAM, ROM and battery, but you know, I would like to find out what's causing this idiotic keypad behavior...

[Q] Screen Won't Come Back On After Call

I have the Chinese version of the Find 7 currently running MoKee 44.4 because I thought this issue was caused by AOSPA, which I flashed for the first time yesterday. Anyway when I make a call the screen turns off as it should and will not come back on no matter what I do. I have to reboot the phone every time. I looked through similar threads but they all seem to be unrelated to having a custom rom; this problem only started occurring after I flashed one & everything worked fine when I was running Color OS 2.0. I tried installing a new dialer but the same problem happened.
Does anyone know of a way not to have the screen turn off when making a call or better yet how to fix the issue?
Thanks very much!

I'm having a very similar situation with Paranoid Android 4.6 (both beta4 and latest beta6).
If I long-press home button, I'm sent back to the lock screen, but only after the call is finished.
Maybe there's a problem with AOSPA's proximity sensor during calls?
Sometimes, the screen will not turn off, but the screen will not react to any touch input during the call.
Power button will turn screen off but not back on again.

This is a problem coming from ColorOS 2.0.x.
I will try to flash back to and older version of ColorOS. After that try an AOSP rom.
Sent from my X9006 using Tapatalk

same problem
Whit all rom use CM11 based or similar, I have black screen when I call, and no input possible!
the only ROM stable is the Kakulay, bet it have several problem whit the contacts management! it confuse the name and numbers in the memory and SIM card!