Related
I've tried various different ROM images (including the excellent Dr.Gonzo), and I have this problem with all of them.
When I'm using the phone either with the keyboard in or out, the screen just switches off randomly. If I wait a few seconds (possibly the backlight timer length), then it comes back. Mostly... Othertimes I have to wait a lot longer, but it does always come back.
A reboot sometimes fixes it, but not always - does anything survive a reboot or battery removal?
Anybody else seen anything like this? I have seen a lot of threads about the screen staying on, but not off.
Of course, it could be a hardware fault, but because it's intermittent, it's hard to prove.
Mike
same problem
If you shake the phone can you re-produce this problem? I've never not heard of this being affected by software - you might also want to ensure you're not overclocking it.
Nothing is removed when you do a battery removal or reboot, ensure your connections are all tight and make sure the SIM pins are all making contact and the SIM door closes, apart from that it sounds like a possible bad LCD ribbon.
Shaking it doesn't reproduce the problem.
Once the phone has started doing this, it happens everytime you press a key.
Seems more like a memory leak to me since it always seems to happen after a while of web browsing/email use.
So actually, it looks like it might be a hardware fault.
I think it happens when the device gets warm. After a few minutes with the screen on, keyboard lit up, wifi on, the phone gets pretty warm and that's when the screen seems to go black. Leave to cool and all returns to normal.
Mike
Same issue here, but the screen does not acually go black/blank it just seems that the screen backlight does not turn back on from a standby like state, the phone itself functions but just not able to see whats going on on the screen.
(keyboard lights work fine and come on when expected)
Not sure about the heat theory as it happens (to me) most often right after a call, anything over 30-50 seconds and the backlight problem occurs, when it decides to work again is a matter of luck.
As said before because it's intermittent, it's very hard to prove.
Has anyone who has had this issue, fixed it with a hard reset ?
Very strange ... but also getting very annoying now!
i got the same thing. took it back to warranty and they said nothing's wrong with the phone but i still get this.
I experience the same problems.. it happens pretty random, but every time when you hit a key. I have set all timers to never but the problem is still there.
Running Gonzo 1.1 at the moment, upgraded from guava.. but that didn't solve the problem.
It is getting so annoying now that I am about to throw the s710 in the dustbin
I have had the same problem!
I have turn it back to my provider and no problem now.
i have the same problem with my VOX
apparently, i can still receive phone calls, and do whatever i want with the phone,
but the screen just stays black, its like if you have unplugged your monitor
since i dont have a htc center in my town or anywhere else nearby.
does anyone know a way on how to open the phone, change what need to be changed and correct the problem? im all up for testing if that would resolve this annoying problem :s
cheers everyone
there is a dismantling manual somewhere in this forum. search.
i don't think taking it apart would help you because this is not a physical fault that you can locate.
and i learned that mcel is the retail seller of vox in mozambique. they should be able to help you with service. else just send a mail to htc support and they will guide you.
yes, mcel are the retail sellers, but i tried to go there, and there are no specialists on htc's there,
the thing is, i didnt bought my htc from them, so i can't go there and change for another one
but tks anyway
no problem
but do try to contact htc support by email. they might suggest a way.
I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?
are you trying to say that by desabling the light sensor, the problem might go away?
i would also like to know if it possible to have the baklight on the lowest possible brightness forever, because it seems, on a low brightness the problem might go away
petlof32 said:
I'm having exactly the same weird problem and I think I found some pattern when it occurs. Well, the thing is that in the bright day or in a room with lots of light it works just fine. In the darker conditions… well… not so fine. It seems to me that this screen blackout happens whenever the keyboard light is on and screen changes to full brightness (in the dark, because of the light sensor). In the daylight, keyboard light doesn't turn itself on, so s710 works. I don't know much but this definitely isn't some bad contact problem. Maybe some battery problem, but I doubt it since I can receive phone call in this condition. This started to happen after I flashed this Windows Mobile 6.1 ROM from HTC (I have original S710). Flashing Dr.Gonzo's later on didn't bring any luck either. I believe that some power control SW is the main culprit. I've read that many people mention some Tornado Power Control app. Does anybody know can this application be permanently disabled or removed?
Click to expand...
Click to collapse
I also have this problem with the lightsensor turned off. And also at (as it seems) random moments.
well, even with the light sensor turned off, the problem persisted.
i got my phone to a repair shop of htc's, and they figured out the problem
my phone is now 100% thankfully, the repair man told that the problem was because of bad or malfunctioned circuits, he exchanged them with new ones, and the problem went away,
dont know wich circuits exactly, and he didnt want to tell me, but i suggest anyone having the same problem to try and do the same
probably its a hardware malfunction with these VOX,
its possible since so many times before i've heard about malfunctioned pieces coming out in large quantities for sale.
anyways, cheers everyone, and good luck Portugal in EURO!
I have the same problem. I just noticed that it usually happens when the phone is warm, so if you need to do something on my phone just... take some ice from fridge and put it on back of your mobile. I cant see any more solutions.
Please someone help us!
Update. Problem Solved
Just thought I'd update this thread I started.
I sent the phone back to my dealer (Grapevine in Poole,UK).
A week later, I got a brand new one back from the HTC repair centre.
So far, so good. Looks like the problem's solved.
Mike
Sam problem here,
i called with HTC and they sent them to there repair centre.
Hi - I just got my Sensation a few days ago and I love it. But I have now found an annoying bug (?). When I take a picture and it involves the flash going off, 8 times out of ten the phone will just go dead immediately - screen off, no response. Sometimes a battery pull required to get it to reboot. Anyone experienced this?
Seems to happen indoors when the subject is fairly close, darker conditions.
Not sure if this is a hardware or software problem - I really don't want to return it
Try turning off geotagging.
Thanks, I tried that, then turning off gps, then turning off location, same problem every time.
I find that turning off mobile data, and even leaving all of the above on, stops the problem. Or, leaving data on but turning off the flash. Data + flash = crash...!
Still not sure if this is software related? I guess so?
dazz29 said:
Thanks, I tried that, then turning off gps, then turning off location, same problem every time.
I find that turning off mobile data, and even leaving all of the above on, stops the problem. Or, leaving data on but turning off the flash. Data + flash = crash...!
Still not sure if this is software related? I guess so?
Click to expand...
Click to collapse
Hmm. Since it's correlated with the flash, and few if any others have complained about this I'd guess HW, but who knows. I'd probably do a factory reset, and if that didn't fix it get a replacement.
Has anyone found a solution to this problem? Same thing happens to my phone.
This was posted when the phone first came out. Probably in the early threads. That was one of the first things I checked when I got my Sensation. I don't know if there was a solution other than swapping - but do a search in the forum because it was covered. Hope there was a solution for you.
Same thing happens here, Revo HD.
MEETOO
At first I just waited and it would restart THEN...
Had to pull battery and it would restart THEN...
When it restarted only a speckled screen followed by home screen THEN...
Only speckled screen THEN...
Nothing but the vibration when trying to restart THEN...
A replacement is being shipped after a trip to the T-Mobile store.
Initially I called T-Mobile and they told me the UPDATE would solve my problem but as the day progressed it was all down hill.
During the course of the sales person ordering me a new phone they automatically added a protection plan without my knowledge.
YIPPEE HUH?
So, I just got my A700-32GB and it started out great but for some reason it started not responding to any touch after a few minutes. If I hit the power button to let it sleep and hit it again to power it up, it responds again for about a minute and then stops again. I did a factory reset and it works but after about 5 mins of use it does it again. Anyone else run into that prob? Well, needless to say, Acer wants me to send it in so I will be back to my A500 for a week...That sucks, but I'd rather have a working unit. I didn't have any problem with my A500, hope I didn't get a lemon.
They fixed it...So they say.
So, I sent the device back and monitored the status on the support site. Took 2 days to get there. 1 day later the status changed to resolved. I was supposed to get a follow up email with a tracking number but no dice. I looked it up and it listed resolved but no tracking number so I called. The guy was a tool from an India call center. He was hard to understand and it seemed like he didn't understand what I was asking. I got the tracking number after asking about 5 times. Then I asked if they found what was the matter with it. His response was, "It was a problem with the digitizer so they reset the software." So I asked if it a hardware problem and he said, "No" I asked to clarify if it was a problem with the digitizer hardware and or the OS and he said, "no, we reset the software." So, I hope I get back a working device that isn't going to crap out. It is scheduled to get here on Monday.
Wish me luck. I'll post my findings... Things were SOLID with the A500, I hope they didn't just screw this product up. I like my A500
cipmd said:
So, I just got my A700-32GB and it started out great but for some reason it started not responding to any touch after a few minutes. If I hit the power button to let it sleep and hit it again to power it up, it responds again for about a minute and then stops again. I did a factory reset and it works but after about 5 mins of use it does it again. Anyone else run into that prob? Well, needless to say, Acer wants me to send it in so I will be back to my A500 for a week...That sucks, but I'd rather have a working unit. I didn't have any problem with my A500, hope I didn't get a lemon.
Click to expand...
Click to collapse
Got an update for you all. So, I got the device back and the " Diagnosis/Repair" said that they reseated the digitizer cable and it fixed the problem. Well, it didn't!. It worked for about 5 mins and after that it started crapping out again. I called them and REAMED them a new one and they had to discuss it with a supervisor and they escalated me to the next level. Which means, my call got transfered from India to Texas.
After about 30 mins of walking the technician through my frustation, he sent me another Fedex Ground label (7days) and told me that he would ship it back Express (2 Days) after they repair it.
The "Diagnosis/Repair" this time says "Replaced mainboard and LCD module. All systems tested good." So, I turn it on and it is asking me if I want to updated the device. I canceled it for now to test it out and it seems to work fine.
So, does anyone think it might be the update that caused the issue? Should I try running the update? Anyone hear about the update causing a system hang?
cipmd said:
Got an update for you all. So, I got the device back and the " Diagnosis/Repair" said that they reseated the digitizer cable and it fixed the problem. Well, it didn't!. It worked for about 5 mins and after that it started crapping out again. I called them and REAMED them a new one and they had to discuss it with a supervisor and they escalated me to the next level. Which means, my call got transfered from India to Texas.
After about 30 mins of walking the technician through my frustation, he sent me another Fedex Ground label (7days) and told me that he would ship it back Express (2 Days) after they repair it.
The "Diagnosis/Repair" this time says "Replaced mainboard and LCD module. All systems tested good." So, I turn it on and it is asking me if I want to updated the device. I canceled it for now to test it out and it seems to work fine.
So, does anyone think it might be the update that caused the issue? Should I try running the update? Anyone hear about the update causing a system hang?
Click to expand...
Click to collapse
Holy cr*p, why doesn't Acer just send you a new device? It's a lot faster, easier, customer-friendly and probably much cheaper.
The update is probably JB, which changes (fixes) the touch response. But since Acer replaced the whole motherboard and LCD (why not the friggin' touchscreen itself?), it should be nothing to worry about updating. Some people (US peeps mainly) are having trouble with the update yeah, but it should go well and if it doesn't, the tablet will (or should ) revert to the state before updating.
Good luck.
cipmd said:
Got an update for you all. So, I got the device back and the " Diagnosis/Repair" said that they reseated the digitizer cable and it fixed the problem. Well, it didn't!. It worked for about 5 mins and after that it started crapping out again. I called them and REAMED them a new one and they had to discuss it with a supervisor and they escalated me to the next level. Which means, my call got transfered from India to Texas.
After about 30 mins of walking the technician through my frustation, he sent me another Fedex Ground label (7days) and told me that he would ship it back Express (2 Days) after they repair it.
The "Diagnosis/Repair" this time says "Replaced mainboard and LCD module. All systems tested good." So, I turn it on and it is asking me if I want to updated the device. I canceled it for now to test it out and it seems to work fine.
So, does anyone think it might be the update that caused the issue? Should I try running the update? Anyone hear about the update causing a system hang?
Click to expand...
Click to collapse
Well Mate, I have a 701. Long story, but it's my second 701. First was bricked due to a faulty CWM recovery.
As with all reported issues with ICS (initial build) touch screen will "lag" at certain times. Not totally unresponsive, but required 2 or 3 times selecting an icon for example. This I saw myself on occasion. So you were not seeing things
With the JB update, it seems these issues have mostly been fixed. I was prompted as soon as I started (my second tab), but waited till I filled out the Wizard. And checked to make sure things were normal. Then I did the update to JB.
Also know this, some icons in apps, require you to touch the point, in a slightly "offcenter manner". Like the refresh button on the Acer weather widget. Not sure if this is a widget/app programming error in the widget itself, or is caused by the 70x digitizer. Doesn't do it with all apps though.
Go for the update.
MD
My nexus 5 is three days old now. This morning when I was reading an article in Chrome my screen started to just freak out. It was clicking links, going back to my app drawer, opening programs, going to Google now, opening (and sending!) emails, hangouts, Google Voice SMS messages, etc.
Thinking it might just be a glitch I did the first troubleshooting step - I turned it off and then turned it back on again. After a few minutes it was glitching again.
When it stopped momentarily I went right ahead and did a hard reset - just in case there was a Virus or something insidious on my phone. Normally I'd hold off on that option, but for this time since I didn't really have anything on the device I figured it was the appropriate course of action. After doing the hard reset and starting up my phone again, within a few minutes it was freaking out again. Luckily, I had the presence of mind to grab my old Galaxy Nexus and take a video recording of what I was seeing:
www [dot] youtube [dot] com/watch?v=6J5ILs-MqjI
Here are the facts:
- The phone is three days old.
- This is the first time that I've noticed this issue, however on day 1 I left the phone on my desk when I went to get some lunch. When I left (and came back) the battery was approximately 70%. Yet, mysteriously, in that 30 minute time frame the unit had shut itself off.
- The phone has not yet been exposed to moisture, extreme heat, or extreme cold. It has not yet been dropped. There are no other indications of manufacturer's defect readily visible.
- The screen is clean
- While having the tantrum, the phone went in and out of airplane mode several times.
- The tantrum occurred both before and after the hard reset. Installed apps weren't even completely downloaded when recurrence happened.
- In another fit, it eventually restarted itself.
Is this a hardware issue? Software issue? User error? Should I initiate an RMA?
DutchessDucky said:
My nexus 5 is three days old now. This morning when I was reading an article in Chrome my screen started to just freak out. It was clicking links, going back to my app drawer, opening programs, going to Google now, opening (and sending!) emails, hangouts, Google Voice SMS messages, etc.
Thinking it might just be a glitch I did the first troubleshooting step - I turned it off and then turned it back on again. After a few minutes it was glitching again.
When it stopped momentarily I went right ahead and did a hard reset - just in case there was a Virus or something insidious on my phone. Normally I'd hold off on that option, but for this time since I didn't really have anything on the device I figured it was the appropriate course of action. After doing the hard reset and starting up my phone again, within a few minutes it was freaking out again. Luckily, I had the presence of mind to grab my old Galaxy Nexus and take a video recording of what I was seeing:
www [dot] youtube [dot] com/watch?v=6J5ILs-MqjI
Here are the facts:
- The phone is three days old.
- This is the first time that I've noticed this issue, however on day 1 I left the phone on my desk when I went to get some lunch. When I left (and came back) the battery was approximately 70%. Yet, mysteriously, in that 30 minute time frame the unit had shut itself off.
- The phone has not yet been exposed to moisture, extreme heat, or extreme cold. It has not yet been dropped. There are no other indications of manufacturer's defect readily visible.
- The screen is clean
- While having the tantrum, the phone went in and out of airplane mode several times.
- The tantrum occurred both before and after the hard reset. Installed apps weren't even completely downloaded when recurrence happened.
- In another fit, it eventually restarted itself.
Is this a hardware issue? Software issue? User error? Should I initiate an RMA?
Click to expand...
Click to collapse
It definitely doesn't look like a user error, seems to prove you're using it fine when you can. This tantrum could be both hardware and/or software. If it were me with such a new device having an issue like this, i'd get a new one. I'd initiate RMA sooner rather than later.
FourPointedFreak said:
It definitely doesn't look like a user error, seems to prove you're using it fine when you can. This tantrum could be both hardware and/or software. If it were me with such a new device having an issue like this, i'd get a new one. I'd initiate RMA sooner rather than later.
Click to expand...
Click to collapse
Thanks. I guess with no other defects I just want to make sure it isn't user error or an app I have installed or anything. Seems like a waste to wait another month to get another unit and increasing the chances of it being someone else's refurb.
DutchessDucky said:
Thanks. I guess with no other defects I just want to make sure it isn't user error or an app I have installed or anything. Seems like a waste to wait another month to get another unit and increasing the chances of it being someone else's refurb.
Click to expand...
Click to collapse
Well based on my experience with Google and Nexus devices, typically they'll try hard in your situation to get a you a new device and sooner. They'll probably resell yours as a refurb but issue you a new one.
Fingers crossed.
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
This happened to my wife's Pixel 7 the first morning she had an alarm set with it.
Did you by any chance snooze it half a dozen times? It was only after she refused to get up that it locked. I think maybe it's a feature, not a bug.
That sounds familiar as if it might've happened once on my OG Pixel years ago, but I can't say for sure.
rczrider said:
It was only after she refused to get up that it locked. I think maybe it's a feature, not a bug.
Click to expand...
Click to collapse
LOL! Good point.
No snoozing and it just locked up for the second time just now. The time is displayed but stuck at 8:16 and it currently 9:57, never had this issue on the 6. I'm wondering if I have bad RAM or something that is causing random lockups.
I do see that it vibrates when I press and hold the power button but I can't see what it's doing with the screen locked up.
Talking to support, they wanted the IMEI number and a picture of the screen? The screen looks normal but is locked up. ???
They have to put me on hold to talk to someone else for each part of the questions. I called Google support but it sounds like someone overseas.
I don't see what they can do, other than replace it. I copied everything from the old phone that was working fine.
They want me to back it up and do a factory reset. I just did that when I got the phone a few weeks ago.
Then they asked that I run the phone in safe mode for a few weeks to see if its a bad app that was installed.
I asked to speak with someone more knowledgeable and they needed to put me on hold again saying I could get an email from someone or wait to talk with someone. They then said I had to give consent for them to look at all my data. ??? After the long hold I was told that I'd be getting an email. Total waste of time.
My screen froze and became unresponsive when I swiped down for notifications while watching non-fullscreen video on Youtube TV. The audio continued to play. I recovered by holding down the power button for 60 seconds to force a reboot. I can't duplicate it though.
I have had these screen freezings too. By pressing power button for 30 sec it boots the phone back up. Then after a minute or an hour it happens again. Had to do factory reset two times already. That's the only thing that helps.
I have no idea of what is causing that.
Mine has done it three times now, had to power cycle it as mentioned above, and each time it was a different app
Here is their suggested fix:
Here are some additional steps to take to try to resolve the issue with your Pixel phone:
Troubleshoot your apps
Perform a factory reset
After each step, check to see if your issue is resolved. If not, continue to the next section.
Tanquen said:
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
Click to expand...
Click to collapse
SystemUI has crashed a few times on mine, which causes a lockup. Rebooting seems to fix it, for the most part.
Tanquen said:
Here is their suggested fix:
Here are some additional steps to take to try to resolve the issue with your Pixel phone:
Troubleshoot your apps
Perform a factory reset
After each step, check to see if your issue is resolved. If not, continue to the next section.
Click to expand...
Click to collapse
You can report back that the factory reset fixes the bug for a while. But if I have to do a factory reset every week, I'm going crazy.
miimaa said:
You can report back that the factory reset fixes the bug for a while. But if I have to do a factory reset every week, I'm going crazy.
Click to expand...
Click to collapse
Just rebooting the phone fixes it for a little while. That's the trouble with random inconsistent issues. It could take a week or two or more for it to do it again. With a number of others having similar issues I don't think a factory reset again is going to do anything. I just got the phone a month or so ago and it was at factory default. What good would it do to put it back to factory again? Sounds just as unreasonable as using my phone for several weeks in safe mode to see if it's another program causing the problem.
Woke up this morning and the phone had rebooted.
RMA your device keep trying until you get someone that understands your issue. Google support is absolute rubbish and if the rep doesn't understand that you're losing all touch input just hang up and try again. It's frustrating but it's sadly the only way you'll be able to get your phone swapped out. I had this problem on my P6P and only a RMA solved my problem.
They offered to let me send it in and let their techs look at it for 2-3 weeks or take it to a local shop. I was surprised that there was an authorized shop in my city but what are they going to do with a phone that reboots every 5 or 6 days? I've not even had it 30 days but they said it was too long just be able to return it. You have 15 days. I pushed back and they set up a replacement but not before telling me about the option to mail it in a wait a few weeks. Who can be without their phone for a few weeks. I have to buy a new one and then have 30 days to return this one.
I do wonder if it's a software issue that Google will fix at some point but don't think so. There is a thread on their support forum that has not been locked yet with a number of folks with what sounds like the same issue.
Oh wait it's 21 days to return it.
"Remember that if we don’t receive your old item 21 days after your replacement ships, you will be charged $968.67, which is the full value of your replacement item."
Tanquen said:
I've not seen this with any of my Google phones but today the alarm went off and then the phone locked up while still playing the alarm sound. The screen was stuck at like 2am but it was like 6am at the time. Power and volume up buttons did not work to get to restart. I had to Google the fix and that was to hold down the power button for 30 seconds.
Video of it stuck.
Click to expand...
Click to collapse
I would attribute it to buggy software. My 7 pro locked up about a week into ownership. The last time I had a phone lock up was my last pixel phone (the 3). Not sure what it is but it always clears up after a couple updates. Maybe the same will happen for you.
Tanquen said:
They offered to let me send it in and let their techs look at it for 2-3 weeks or take it to a local shop. I was surprised that there was an authorized shop in my city but what are they going to do with a phone that reboots every 5 or 6 days? I've not even had it 30 days but they said it was too long just be able to return it. You have 15 days. I pushed back and they set up a replacement but not before telling me about the option to mail it in a wait a few weeks. Who can be without their phone for a few weeks. I have to buy a new one and then have 30 days to return this one.
I do wonder if it's a software issue that Google will fix at some point but don't think so. There is a thread on their support forum that has not been locked yet with a number of folks with what sounds like the same issue.
Click to expand...
Click to collapse
I believe it's part of their call flow offering the repair shop or mail in option. There's always the advanced RMA option where they put a hold on a card you provide and the temp charge is removed once they receive the defective device. If you don't want the chance at getting a refurbished replacement do the advanced RMA sooner rather than later.
The phone froze on me 3 times already - 2 times using Samsung browser, 1 time on Chrome.
Android 13 QPR1 Beta 3.1 introduces a GPU fix, which will hopefully resolve this issue:
Fixed issues where a device's GPU drivers sometimes caused the system UI to freeze during normal device use.
I'm swapping it out for a new(?) one. Hopefully all goes well.