After unlocking my phone with ChevronWP7 and now my screen goes black during a call and is unusable. The connection is fine, but its like my proximity sensor is doing its job even when the phone is away from my face. I checked and there is nothing physically blocking my sensor. I have to wait for the other person to hang up, then my phone shows the lock screen. I did a reboot but this didn't fix the problem. I don't know if this is device specific but I'm running an HTC HD7 without the software update. Here's everything I did after the unlock:
Prevent my phone from relocking:
http://forum.xda-developers.com/showthread.php?t=913748
Change my theme color:
http://forum.xda-developers.com/showthread.php?t=929017
And lastly installed a couple custom ringtones.
Unfortunately, I can't say after what step this started happening as I didn't get a call until I was all done.
Anyways, If anyone as had this same issue or a possible way to fix it without a hard reset, I'd sure appreciate some help.
Thanks,
JT
the problem is in your sensor.....it's hardware related problem and have nothing to do with software, use your warranty to fix it
Related
Hi to all!
I have a strange problem with my HTC s710.
I bought it a month ago and it worked fine for a while, then it started to shutdown the display. Then it appears again, and the it turns off... it continues to work, but you can see nothing because the display turns off.
It's impossibile to use it. The HTC customer care sended back my phone after having upgraded the software but the problem is still here.
They wrote: "upgraded software and no problems found" but it's not really true.
I can't use the phone because the display turns off while i'm using it...
i tried to hard reset it several time without results.
Please, help me...
I would take it apart, clean the contacts and make sure it is seated properly. Does it happen when you're not using the device? Say if it's sitting on the table will the display flicker?
Unfortunately this is a very common problem with the S710... Since so many people are experiencing this issue with their phones even after hard resetting & changing roms I strongly believe it's a hardware issue.
It's not s710 only, even the microsoft emulator also have the problem
Look in the registry HKEY_CURRENT_USER\ControlPanel\Power The Dword-key "Display". It sets the seconds for display timout. It overrides every other setting!
It happens while i'm using the phone...
for example, if i'm writing an sms, it suddenly turns off the display... then i have to wait for a while and the it appears again... and this go on for all the time...
same problem to me.... dunno what the source of the problem is
guess gonna have to take it back and ask for refund
i've already send it back to the HTC customer care and they said there is nothing to do because it works fine... (oh my god!)
I think it's an hardware problem...
Display blackout
I got the same problem too, did rom upgrades but no success, it s**ks
Its an intermittent fault.
Should someone identify the problem pls let me know !!
This is almost sure a connection problem of the Flex-cable between upper and lower part of the device. Search related threads here or on MoDaCo.
s710 display issues
Hi Guys,
This is not a LCD or flex issue, neither is it a connection issue.
The actual fault is the display driver on the main board, it seems to be an intermittant fault.
please post your findings on this topic....
bro am also havin the same problem but they say it seems to replace the board which costs 9k... hw can i fix this problem pls help me i bought this stuff for 17 k...
tjsa said:
Hi Guys,
This is not a LCD or flex issue, neither is it a connection issue.
The actual fault is the display driver on the main board, it seems to be an intermittent fault.
please post your findings on this topic....
Click to expand...
Click to collapse
What makes you so sure it is not HW related? The only thing that really changes over time is the HW (as you slide in/out the keyboard, move the device etc.pp) - SW stays as it is and if even ROM reload does not fix it, well I feel rather sure it is HW.
Anyway, hunting intermittent faults is hard to do and you may construct a causality from just coincident events - no fun nailing this down.
any solution for my problem..?
I have had so many power related issues so far. Sometimes it is the battery, sometimes it is the charging connector, sometimes LCD and sometimes even the whole circuit board.
When i had the same problem relating to intermittent off displays, I got it repaired in the warranty and they had to change the main board. I dont think there is any other solution to your problem!
Display failure
The failure of the screen is not the problem on my Vox. My screen always jumps back to the Home screen. Even while writing an SMS or scrolling in the application menu. Is there a possibility that there ever comes a Dutch version for my Vox?
It happens to me also. I tried to open the device, take everything apart then mount everything back. The problem stays. I tried hard rest, ROM flashing, soft reset, changing settings etc etc etc... The problem is still here.
Then, I left the mobile without using it for 6 month or so. I am using it again and the problem doesn't happen so often but still happens. Any news on this matter?
I solved this problem because my device was still under warranty: I had to get back it to HTC four times before to fix it.
They changed me three motherboard and finally it seems to work fine...
hi,behind the sim reader there is a small switch,either open it or close it,remove the sim reader to and push it back to open the switch or open the housing and do it manuelly.
cheyn said:
hi,behind the sim reader there is a small switch,either open it or close it,remove the sim reader to and push it back to open the switch or open the housing and do it manuelly.
Click to expand...
Click to collapse
And what is supposed to happen after that? Also, I guess we have to open again the phone to find this switch because I can't see any switch otherwise. Can you please post a picture of it?
hi,
I'm not sure when exactly this issue started on my phone, but I updated my touch pro with the chevron updater and have quite a lot of apps installed.
after several seconds workling with the phone, the touch screen stops working while the phone acts perfectly normal. I can use the keyboard and tilt the phone but I cannot use the touch screen anymore.
By turning the phone off and on it works again.
has anyone experienced a behavior like this?
I noticed my touchscreen becoming unresponsive when loading particular websites. Even had it freeze once (only time it ever froze on me)
What were you doing when it does this? Do you have the multitasking reg edit on?
exilkubaner said:
hi,
I'm not sure when exactly this issue started on my phone, but I updated my touch pro with the chevron updater and have quite a lot of apps installed.
after several seconds workling with the phone, the touch screen stops working while the phone acts perfectly normal. I can use the keyboard and tilt the phone but I cannot use the touch screen anymore.
By turning the phone off and on it works again.
has anyone experienced a behavior like this?
Click to expand...
Click to collapse
I know this is an old thread but this is the only reference to the exact same problem that I'm having. I'm having difficulty putting this down to hardware as the screen becomes responsive again when locking and unlocking which might point to software.
It could be a hardware issue that is resolved by locking then unlocking the phone but I don't know enough about the construction of it to have an opinion.
The advice I've had from htc is to wipe the 'phone and start again but I don't expect that to solve it (especially as their call handling system refers to Window Mobile 7 - the second large commercial organisation I've seen that on in recent weeks without looking too hard!).
Has anyone else seen this since the original post or @exilkubaner was a solution found to your problem?
Hi,
I have exactly the same problem. I hard reset my HTC 7 Pro, but no success, my screen doesn't respond until i lock/unlock the device.
So, any one have resolved this issue since the first post ?
Regards
Had the same issue, but I didn't have any roms installed.
Brought it in to Sprint and they found that I had a fried ribbon connecting the screen to the phone. Replaced under warranty.
It happened again, I determined that it was caused by my click in belt clip/holster. When I pull the phone out, it pulls the screen away from the keyboard a bit.
^Wow. Nice find. I'll have to be careful with mine now as I could easily run in to the same problem pulling it out like that.
Hi guys, I've a problem with my HTC HD2.
When I make or receive a call the screen turn off and I can't do anything, I can't use the speakerphone or keypad, nothing at all.
If I want to close the call I must unlock the phone and hang up by navbar.
I've searched on web and I found many thread in relation to my problem; I've tried many solutions to resolve it but failed.
I've also disabled the light and proximity sensor but it didn't work. The problem still remain.
I've forgot to say that I changed the main flex and the display of my HD2 because the originals was damaged. Until now I never had any problem, it all started with the new pieces.
I tought that if the sensors were damaged the screen shouldn't become black when I answer or when I start a call, am I wrong?
Another thing, I've just inserted headphones in the phone and made the call from another device: the screen remains on and I can use all the commands without any problems. What could be the problem?
I hope someone can help me to find and resolve it.
Ps: I apologize if there are mistakes in my english but it isn't my mother tongue.
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.
Hello everyone,my fingerprint was working fine till afternoon,then suddenly I tried unlocking my device and I couldn't with fingerprint. I went to settings and it told me fingerprint error,please restart your device bla bla. When I dial *#0*# under fingerprint test it shows the version butility when I click normal test it says fingerprint initializing fail.Could anyone help?
I get basically the same error!
In my case it stops working even for a couple of days and then it suddenly comes back for no reason (for few days as well). No clue why this all occurs. I assume it's some kind of a hardware issue since, as you mentioned above, the phone somehow stops recognizing the sensor and you end up getting this annoying notification on the lockscreen. I have to mention that my GS6 has never fallen down or been left in the hot (I put a case on it and take . What makes the whole thing even more weird is that sometimes a simple reboot helps - it happens quite rarely though.
Tbh, I thought of two things which would possibly solve the issue since I'm quite sure it's NOT software related (tested different ROMs, kernels, etc) - 1) open the GS6 and check whether the home button is connected properly 2) buy a new home button and replace it. I need some free time to do it though so I guess it won't happen too soon
The biggest problem is that i can't really find any logical dependences, it happens too randomly :|
I have done many reboots,only one time it worked for a while and then stopped working again.
makisss said:
I have done many reboots,only one time it worked for a while and then stopped working again.
Click to expand...
Click to collapse
Exactly. Unfortunately my warranty is voided so I can't even send it to Samsung.