ICS Updated, now Phone Screen doesn't turn back on in-call when removing from ear?

[acejavelin]

yep, tried them all.

Then a CLNR is in order...

 

[tannins]

This is not a widespread issue and is a hardware thing... not related to ICS. Have you tried the various procedures discussed in this thread such as a factory reset, screen protector issues, case issues, compressed air, etc.

It's not a hardware thing. My hardware worked fine on gb, now doesnt work properly on ics.
I stopped posting all the bugs I have now because there are too many. I factory reset 3 times. Ics us just buggy.

 

[acejavelin]

Not really sure what else to say, I have only heard of a two or three instances where the Proximity sensor failed to function properly under ICS... perhaps it is a certain hardware revision that was not widely distributed or what, I dunno. But I can tell you 99.9% of people with a Rezound and ICS do not have this issue, I have two of them personally and we have about 8 or 9 in my office, no one has ever complained about this issue and all but one (my personal one which is on the Global Mode leak) are running the stock OTA firmware.

Since you have done everything normally associated with this, all I can tell you is that if it was mine, I would reflash the full OTA RUU, at least twice, and see if the problem persisted before installing any software, if it did continue then I would try the Global Mode RUU, flash at least twice, then if the problem is still there I would call Verizon, tell them you have Factory Reset at least 4 or 5 times and request a replacement. Other than that I don't know how to help you.

 

[tannins]

Not really sure what else to say, I have only heard of a two or three instances where the Proximity sensor failed to function properly under ICS... perhaps it is a certain hardware revision that was not widely distributed or what, I dunno. But I can tell you 99.9% of people with a Rezound and ICS do not have this issue, I have two of them personally and we have about 8 or 9 in my office, no one has ever complained about this issue and all but one (my personal one which is on the Global Mode leak) are running the stock OTA firmware.

Since you have done everything normally associated with this, all I can tell you is that if it was mine, I would reflash the full OTA RUU, at least twice, and see if the problem persisted before installing any software, if it did continue then I would try the Global Mode RUU, flash at least twice, then if the problem is still there I would call Verizon, tell them you have Factory Reset at least 4 or 5 times and request a replacement. Other than that I don't know how to help you.

How do you reflash the ota ruu?
Thanks for the help.

 

[acejavelin]

[Exclusive Download] HTC Rezound Ice Cream Sandwich RUU For Final OTA (3.14.605.12)

This will wipe all data on the phone itself, but not the microSD card.

Download the file, rename it to PH98IMG.zip (best bet is to verify MD5 sum at this point with what is listed on AP's website), copy it to your microSD card, power down, pull battery, reinstall battery, power up holding VOL DOWN+POWER, the process will start automatically. It should go through and after about 15-20 minutes you will be prompted to reboot, if not, wait about 40 minuted and pull the battery and start over from the battery pull step (this is normal, it just happens sometimes). Now the phone boot up completely to the setup screen, don't do anything, wait a couple minutes, then pull the battery and flash a second time. Now finish setup like normal. Remember to delete PH98IMG.zip from the microSD card to prevent accidentally flashing and factory resetting you phone, or at least move the file to sub-directory on the card.

Good luck!!!

 

[tannins]

[Exclusive Download] HTC Rezound Ice Cream Sandwich RUU For Final OTA (3.14.605.12)

This will wipe all data on the phone itself, but not the microSD card.

Download the file, rename it to PH98IMG.zip (best bet is to verify MD5 sum at this point with what is listed on AP's website), copy it to your microSD card, power down, pull battery, reinstall battery, power up holding VOL DOWN+POWER, the process will start automatically. It should go through and after about 15-20 minutes you will be prompted to reboot, if not, wait about 40 minuted and pull the battery and start over from the battery pull step (this is normal, it just happens sometimes). Now the phone boot up completely to the setup screen, don't do anything, wait a couple minutes, then pull the battery and flash a second time. Now finish setup like normal. Remember to delete PH98IMG.zip from the microSD card to prevent accidentally flashing and factory resetting you phone, or at least move the file to sub-directory on the card.

Good luck!!!

Not sure what this means;
best bet is to verify MD5 sum at this point with what is listed on AP's website
Also, what do you mean when you say flash a second time?
Thanks a bunch.

 

[acejavelin]

Not sure what this means;
best bet is to verify MD5 sum at this point with what is listed on AP's website
Also, what do you mean when you say flash a second time?
Thanks a bunch.

On Android Police's website (and most of the download sites) there is a MD5 checksum hash for the file

Download: (598.6MB, MD5: ec526757ebe84c066e31907e5fccd987)

You should verify the file you downloaded has the same MD5 checksum, there are lots of Windows, Mac, and Android tools that can do this. I use MD5 Calculator by BullZIP in Windows, and ES File Explorer on Android to check it. Verifying that the the file you have has the exact same MD5 checksum virtually guarantees the file you have on your PC or SD Card is the same as the original, the chances that the MD5 checksum values are the same, and yet the files are different, are 50% that any two files in 18,446,744,073,709,551,616 unique instances, so if they match I would put my paycheck down that they are same. Doing this is a safeguard to make sure that some error didn't occur in downloading the file (the most common cause of file issues).

Do the flash twice, go through the complete process once, then do it a second time... It might not be necessary but people who have been flashing in RUUs for a long time always recommend this to make sure everything is clean and installs correctly.

 

[feralchick]

I had this problem on my second or third replacement Rezound. Worked fine till the ICS update then the screen would stay dark when I made a call. I could barely check my email because the screen would shut off before I could enter my password. Had a few other issues so I replaced the phone. Sorry I have no suggestions to offer.

My current Rezound has slowed down incredibly running stock ICS and I am hoping to avoid a factory reset. Phone was brand new, no apps installed and I did a factory reset after installing ICS and then loaded my apps.

Any suggestions to speed up this phone short of a reset?

 

[Coupe]

Well, while searching around to diagnose this same issue on my phone I found this thread and I can't beleive I need to get a replacement phone to fix this. I have had ICS since it was pushed to my phone with no issues and then today I started messing up calls and hanging up on clients by accident. I can't trust it anymore and I am concerned about security when I wipe my phone with a factory reset, is it secure?

 

[acejavelin]

Again people, the issue is the PROXIMITY SENSOR, not the software. Use Proximity Sensor Finder from the Play Store to verify it for yourself, it talks directly to the sensor itself, not through the normal API calls. There is no known way to calibrate it either like a ZTE phone or some other manufacturers. The Prox sensors on HTC devices seem to be kind of flaky, on of their week points... my current personal Rezound is very temperamental as well, the screen has to be absolutely clean or it keeps the screen off all the time on a call, clean it with a MF cleaning cloth and it comes to life until a little bit of normal smudges causes the issue again.

Wiping your phone via the Reset to Factory defaults in Settings or via Factory Reset in hboot is very secure, the flash RAM in the device is not like your hard drive, when it is wiped and formatted, it is gone to everyone but perhaps a forensic data recovery technician, and even then I have my doubts...

 

[Coupe]

No doubt its hardware, I should have been more clear I guess. I have had ICS for a long time with zero issues.


Thanks for the secure wipe info.

 

[acejavelin]

Well it looks like rooted users now have an option for calibrating the proximity sensor, I am sure it won't fix prox issues for everyone, but I am betting it will help alot.

Rezound Prox Sensor Calibrator

And it was developed by Chad0989... and if you know anything about the Rezound ROM development world, you know this guy is a genius with the Rezound, he is the one that cracked the RIL on the Rez, a very respected developer.

Again, must be ROOTED to use this... So the Rezound Development area for more information on rooting the Rezound.

This will not fix a bad sensor, although it may allow one that is marginal to be used again, or tweak it enough to get things working... and it is possible that some people who have had issues since ICS got the calibration of the sensor corrupted and this could help. I have not tested this yet, but plan on it when I get a chance to root again.

 

[Coupe]

Well, I feel like an idiot, I was thinking the sensor was closer to the front camera opening or a part of it, it's more like center front. Anyway it turns out that my screen protector was causing the issue. It's weird because it was at least 6 months old and it looked clear.

Anyways......nevermind.

 

[acejavelin]

My favorite phone testing app, Phone Tester, has been updated so it no longer FC's or reboots the Rezound. It was my go to testing tool for all the sensors of the phones before ICS which broke it, but it works good now. Not really a fix but I like how it looks at all the sensors of the phone and not just the Proximity Sensor, a handy tool.

 

[tannins]

Ace, how do you use the proximity sensor? Mine reads far when I open the app, and doesn't change when I cover the sensor. Thx.