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.
I have a Touch Pro2 on Verizon that has recently started to put itself in headphone mode at random. Trying to push the pins down via stylus or plugging and unplugging the headphones hasn't worked at all. I did soft resets and left the battery out for a while.
It was at this point that I realized the phone had also ceased to vibrate.
I tried putting the phone on vibrate, but it acted as though it was on silent. I then finally flashed the ROM, which confirmed both issues to be due to hardware (which was already pretty obvious ...)
It's worth noting that sometimes when I select a Manila tab, I can hear the motor TRY to vibrate, making a single slight clicking noise. Normally, I wouldn't make too big a deal out of the vibrating issue, but that coupled with only hearing half of my notifications due to the headphone problem is maddening.
I hastily opened the phone to see if it was anything I could fix (which wasn't smart, but I guess I figured the dings on the phone coupled with the fact that I was using the latest MightyROM release was enough to forget the warranty.) Obviously, I got nowhere.
I'm out of ideas at this point, and am curious to hear what everyone here has to say. I'm nowhere near upgrade time, and don't feel like paying full retail for another phone.
flash the stock SPL, flash the stock ROM, tell verizon to fix it. Or get insurance and pay for a replacement phone.
Interesting note: Quickly inserting and removing headphones runs "Windows Media", and doing so twice redials the last number. Figured this post would at least be entertaining if nothing else.
I'm still trying to figure this out (since that's the kind of guy I am) but I'll probably end up getting a new phone altogether. Probably won't get another Touch Pro2, but it'll be hard to go back to any other QWERTY keypad after this one.
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
I want to say that I noticed something similar the other day, but it was short-lived, and I'm not 100% sure. It wasn't long enough or bad enough to make me think the phone is defective, but I'm a bit used to funky capacitive button responses from my N1 days.
I can't reproduce the issue right now, though. How much usage are you talking about needing to duplicate?
Does your phone get hot, or feel hotter than normal when this happens?
I'd see if there's some particular pattern or software that seems to trigger it if you're interested in trouble-shooting.
The problem goes away when I don't touch the phone for a while (it seems that 1 hour is enough to reset the problem).
It seems "recharging".
Then with normal usage, nothing in particular, just even browsing in the settings/maps/market/browser etc., in few minutes the problem appears. The button definitely loses his "power".
It's very annoying, and my friends confirmed the same behavior.
EDIT:
Forgot to sat that the phone is not getting hotter, everything else is really normal.
Cheers
Mine definitely can be used for much more than a few minutes without the problem you're describing appearing.
I'd take it back. Factory reset the phone to protect your private data before taking it back. After the factory reset, you might want to test the behavior again, if it went away, the phone's not defective, you just had some software glitch.
Reminder, factory reset erases everything on the phone, so if you do it as troubleshooting step, be prepared to have to set the phone up from scratch again...I'm sure you knew this, but just covering my butt in case you didn't. It's a good trouble shooting step no matter what if you don't mind the hassle of re-setting things up.
I have a similar experience with the back button. Not sure what to think yet.
Sent from my Nexus S using XDA App
I had a similar problem when I had the Vibrant. Just exchanged it and luckily I got a better one without any problems. I did find out though if you are using the screen protector that came with the phone, it can cause this type of problem.
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
michele72 said:
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
Click to expand...
Click to collapse
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
distortedloop said:
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
Click to expand...
Click to collapse
Thank you, giving it a try.
Anyway, today I factory-reset my telephone and the problem of the back button is still there. I am returning the device.
Back button non responsive
Hi,
I just got my new nexus S (about an hour ago) that I was really excited about and am faced with a problem with the back button too.
Its got factory settings, so it cannot be a downloaded software issue. Also, I have not yet charged the battery at all, its still running on the same battery power that it shipped with.
The other buttons at the bottom of the phone (home, menu and search) all respond fine, its only the back button that does not seem to work. After going through this thread, I tried long-pressing the button, hard-pressing it, pressing just above it, below it, etc. It just wont respond. I had removed the screen protector it shipped with, so that cannot be the issue either.
If this is a known hardware problem (i.e. others have faced it too), irrespective of whether it is acknowledged by Samsung / Google, I'll return the handset. I do not want to spend a fortune and be landed with a handset that does not work - forget working as desired, but it does not seem to be working as designed !
Thanks & Regards,
Rohan
Yep. Definitely a problem here with the back button. There's also two other threads here about it.
I'm having similar problems. I have to touch the button just right for it to work properly
Sent from my Nexus S using XDA App
I was experiencing the same thing with my Nexus S, wasn't sure if it was the case I was using! Took of case and still had problem. I eventually returned mine cause it seemed like it was getting worse! I have a new one worth no problems, definitely a hardware problem! Return it!
Sent from my Nexus S using XDA App
michele72 said:
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
Click to expand...
Click to collapse
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
same issue was with Nexus 1. less responsive buttons. thats why there is a bigger gap between the buttons and the screen for galaxy S phones. i dont know why they did such a thing again with the nexus S. its like samsung didnt learn from anything from HTCs mistake.
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
I think this is true ...
I have an HTC Desire with AMOLED screen.
When I play a finger intensive game, like "SkyForce Reloaded", after some times, the touch is not registered.
Then I must stop for a while, or change finger
Try that, you will know what I meant.
But, I don't have issue with the back button on HTC Desire because it is a hardware button. I am just trying to explain about loosing touch registration because finger interaction on (s)amoled screen.
PS: SkyForce Reloaded is an old school shot'em up game where you control a little space ship with your finger, shooting enemies.
ll_l_x_l_ll said:
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
Click to expand...
Click to collapse
The Desire's digitizer is the same Clearpad 2000 which is used in the Nexus One (and quite a few others), the problem there is that it's pants.
Rusty! said:
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
Click to expand...
Click to collapse
lol, isnt called like that because it registers the heat from your fingers. thats why if you try to use a pen, it wont register . and thus. the screen is NOT resistive type "where it will recognize anything since its being pushed by force ? "
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Rusty! said:
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Click to expand...
Click to collapse
from your link
"A capacitive touchscreen panel is one which consists of an insulator such as glass, coated with a transparent conductor such as indium tin oxide (ITO).[7][8] As the human body is also a conductor, touching the surface of the screen results in a distortion of the screen's electrostatic field, measurable as a change in capacitance. Different technologies may be used to determine the location of the touch. The location is then sent to the controller for processing.
My Nexus 5 vibrate motor seems to randomly stop. Usually, it stops working for just a few seconds at a time, but sometimes it stops for more than just a few seconds. It started randomly one day, and I haven't been able to tie it to a specific app yet, and it didn't coincide with the installation of a kernel or ROM.
I'm running rooted stock Lollipop with elementalX kernel (2.03).
I've tried pushing on the back, since some people have issues with the vibration motor not making good contact with the rest of the phone, but it seems that doesn't really do anything for me. It seems to help occasionally, but not necessarily.
Sometimes turning the screen off and back on helps, but sometimes not either.
Unfortunately, the inconsistency is making it difficult for me to figure out what the problem is. Could it just be a dying motor?
You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.
bblzd said:
You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.
Click to expand...
Click to collapse
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket
And it happens with stock kernel as well, correct? If it has been less than 1 year you could RMA.
chronostorm said:
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket
Click to expand...
Click to collapse
I had this problem as well and still encountering it sometimes. Don't worry about a missed call though. My vibration completely stopped working and a reboot didn't help, however a call made the vibration work again lol and it has been working since. Fingers crossed same **** doesn't happen again.
I'll try to keep this short yet detailed.
So I basically flashed Custom ROM on my whyred 2-3 years back.
RR Rom and I have no Vibration since then. (I might have wiped incorrect partition Idk, some people said something about the device tree I've no idea.)
Lemme answer few questions that will pop up in your minds.
Yes I checked every setting, everything's ON.
QC Test failed for vibration.
I got my vibration motor changed as well.
I flashed fastboot ROM as well.
Flashed custom kernels as well.
Multiple ROMs - Pixel, Lineage, RR, Evolution X.
Nothing worked for me.
It's been more than couple of years now. Same happened with Kenzo it still work but without vibration.
PS - I've other devices that work fine on custom ROMs, probably because I've been more careful.
PPS- Vibration comes back sometimes but that's literally like once a year.
Sounds to me, like there is not enough power to trigger the actual motor, based on the fact you've tried so many roms and had same problem for so long.
This can be caused by custom roms, or maybe the motor is just old n cranky, (ok, you changed it) and needing a wee shove to trigger it into moving again, after being still for so long.
Think ps3 controller, if you can open your fone, and put the tiniest bit of wd40 on the motor spindle, then lightly turn it by 'finger' lol, that should do the trick if it's not software related, and it works when it CAN rather than when it wants or is told to.
Just a suggestion. If you do go to look and do the wd40, test the power on the red and black cable while instructing fone to vibrate, if all is good, it's the roms.
Edit: Oh, and it's a good idea to look into notification settings, see what permissions are granted to vibrate/sound/on off? Some apps like to change settings we make being not so obvious. Sometimes denying other apps can affect such stupid things.
Yup I got it, but I'm an electronics guy... If you can confirm if there is power TO the motor (set ringer to vibrate then call yourself, while testing power)... yup....if you cant get power to motor, backtrace the power till you find it.
Its software after that.
.
Pachacouti said:
Sounds to me, like there is not enough power to trigger the actual motor, based on the fact you've tried so many roms and had same problem for so long.
This can be caused by custom roms, or maybe the motor is just old n cranky, (ok, you changed it) and needing a wee shove to trigger it into moving again, after being still for so long.
Think ps3 controller, if you can open your fone, and put the tiniest bit of wd40 on the motor spindle, then lightly turn it by 'finger' lol, that should do the trick if it's not software related, and it works when it CAN rather than when it wants or is told to.
Just a suggestion. If you do go to look and do the wd40, test the power on the red and black cable while instructing fone to vibrate, if all is good, it's the roms.
Edit: Oh, and it's a good idea to look into notification settings, see what permissions are granted to vibrate/sound/on off? Some apps like to change settings we make being not so obvious. Sometimes denying other apps can affect such stupid things.
Yup I got it, but I'm an electronics guy... If you can confirm if there is power TO the motor (set ringer to vibrate then call yourself, while testing power)... yup....if you cant get power to motor, backtrace the power till you find it.
Its software after that.
Click to expand...
Click to collapse
Hey, thanks for the reply.
I'm also an electronics guy, and I'll definitely get the motor power checked.
Yesterday only it randomly started working but it was so weak I knew it wasn't getting enough power. But not sure how.
About the setting vibration is on everywhere and There's no app which may cause any sort of problems. I'm pretty sure it's either the kernels or something else entirely.
Thanks again.
Could be time to get a new battery, or look at one of my teenage hacks:
Redmi Note 9S weird Battery Issue
Hello, My phone problem is, whenever i charged my phone to any certain percentage like 80%, 90%, 100%, and unplugged the charger and using the phone, first 5-10 minutes its consume 5-6% battery and first 1 hour of using its consume 10-12%. This...
forum.xda-developers.com