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.
Related
Since the day I purchased my Fuze, the vibrate has been hit and miss. I have checked Sounds and Notifications and such, but it still almost never vibrates when it should. Sometimes it will work when I press the Volume buttons to change to vibrate, but it usually does not. Touch Response does not vibrate either, and a Hard Reset did not fix the problem.
It worked better with the stock rom then it did with either RRE or Energy. Any help?
maybe the little motor inside the phone is broken. try different roms and see what happens. could be a hardware issue though...
In my old 6700 that issue was caused by a slightly dicey connection between battery and phone. Try moving or 'jiggling" the batt - that fixed it for me every time. Also, occurred more often when using 3rd party batts as the size probably wasnt as precise as the OEM.
Thought about the motor, was hoping it wasn't that.
Battery doesn't really move much. I was going to test it with a voltmeter, but one of the points on mine is broken so I can't get it to reach the contacts for the battery.
I think I might see if I can exchange it where I bought it.
Don't ask why but try doing the following:
- Settings -> Sound -> Haptic Feedback. UNCHECK (turning it off)
- Settings -> Language and Keyboard -> Android Keyboard Settings -> Vibrate on KeyPress. UNCHECK (turning it off)
I've had good results since doing this without changing anything else, phone has been more stable and no random reboots or freezes yet. Theory is due to the custom driver/vibrator used in the LG G2X (per CM7 team) there's a memory leak or some bug that over time causes the phone to reboot/freeze.
Why I think this:
- A few times in the last few weeks it froze was when a notification came in (GMail, SMS, etc.) that would have caused the phone to vibrate but instead of doing so it just did the SOD. Know this because I have a XOOM with me (3G) and emails come to both XOOM and G2X same time
- If I leave everything on, after about 2-3 days of use the vibrations start getting wonky with some lasting longer than they should or just not doing it properly
- Had a similar issue with CM7 on my Verizon Incredible where vibration issues would eventually lead to a reboot/freeze
NO GUARANTEES THIS WORKS. But I wanted to share and get more feedback. Please make these changes and then restart so its fresh. You don't need to disable vibration alerts, just the haptic feedback and keyboard vibrate.
Please post your feedback. Thanks.
I dont have reboots and never have those on...I'm gonna turn em on and see what happens..
I just turned mine off as suggested... I am on my 2nd G2x and am experiencing reboot issues already. I will keep you posted after a couple days on the results.
Thanks for posting this potential fix.
Had these off ever since I got the phone, haptic feedback gets really annoying. Will put them on and see what I find
I have had those on and had no reboots.
Sent from my LG-P999 using XDA App
witeboy07 said:
I have had those on and had no reboots.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Might be related to hw. The vibrator in the phone is a piece of hw so maybe some versions have problems and some don't. I know while my Incredible had vibration problems on CM7 others didn't with same exact software.
I wanted to see more if people getting reboots benefitted at all from these or not. It you don't have reboots at all this post is irrelevant.
mobilehavoc said:
Might be related to hw. The vibrator in the phone is a piece of hw so maybe some versions have problems and some don't. I know while my Incredible had vibration problems on CM7 others didn't with same exact software.
I wanted to see more if people getting reboots benefitted at all from these or not. It you don't have reboots at all this post is irrelevant.
Click to expand...
Click to collapse
It might have more to do with the software. I've used the stock ROM, the leaked 2.3.3, and Cyanogenmod, and all three use different vibration models. The 2.3.3 was particularly bad, CM7 is probably the best.
Bought my G2x on the 9th( So, hello! I'm new ) and everything was great until... yesterday actually. Had a bootloop and had to factory reset, then it locked up later. Then today it locked up and I pulled the battery and just now it didn't come on when I tried to unlock it.
So... I'm trying this. Hopefully it works. D:
If not, I'm gonna have to get a replacement or something. I'll be back with a follow up, some time.
For those of you who try this, please update here after a day or two. I am likely to let T-Mobile switch my phone out to a Sensation today so I may not have a G2x to play with any more. I really like it and if there is a simple fix I'd be willing to give it another go.
Trying it now
I haven't had it reboot on me since I did a factory reset last week...
I'm going to turn off the vibrate settings as described in the first post. I'll come back in a few days to respond if I've had any reboots, freezes, etc.
EDIT: I'm also going to reboot after changing these settings just to make sure they "stick" and the phone is "fresh".
Day 1, no freezes.
I charged the phone and it didn't freeze either...
It's Day 2 now and I'll let you know how this goes down as well.
I haven't had either of these options checked since I first got the phone. I have a reboot approx every 1-2 days and a freeze every 3rd time.
Another strange thing
It's been over a day and a half after I've turned off the haptic feedback settings described by OP and no reboots or freezes yet. Even while using wifi calling and heavy camera use and very heavy picture uploading directly from phone to picasaweb.
Something else strange that happened to me before that could be related to the vibrate software/hardware is when some one called me it would vibrate and ring like normal but after sliding the green arrow over to answer it stopped ringing, answered the call just fine, but the whole time while talking the motor continued to vibrate in the two pulse way it normally does! Has anyone else had this happen!?
harleyxlc said:
I haven't had either of these options checked since I first got the phone. I have a reboot approx every 1-2 days and a freeze every 3rd time.
Click to expand...
Click to collapse
Try wiping your dalvik cache as I've posted in a separate thread.
worked for me. 2 days no problems
day/charge 2 and 3... everything is going well.
Hello all, I have a problem with vibrations on my I9105P. More specifically: my phone fell down from a table right on the floor (maybe 0.5 meter) and since then vibration doesn't work. Everything else works fine, tried reflashing the system and all - nothing works (first I thought it was kernel's fault). What can I do now? Will the warranty cover the repair?
PS. I use case for my phone - it's made of a silicone or something like this (don't know exactly).
If ur phone falls down, how u can say that is kernel problem?
rs tony said:
If ur phone falls down, how u can say that is kernel problem?
Click to expand...
Click to collapse
Well, maybe I said it wrong. I didn't notice that the vibration isn't working for about 5 hours after the fall and so when I reflashed the kernel I thought about the fall - my phone used to fall from time to time and it never broke, so now I'm quite confused. However today, when I was writing on the phone's keyboard, it vibrated once while pressing the letter. Since then - silence.
If you stay it vibrated once that means it's somehow not completely broken. I would disable every sort of vibration in the phone's settings. The vibration motor is probably stuck and it is probably getting damaged more if it keeps trying to spin like that. What did you think - if the phone survived one fall it will survive 10 more just as well? Try the warranty, there's a good chance they'll cover it. Or learn to live without vibration.
cLick1338 said:
If you stay it vibrated once that means it's somehow not completely broken. I would disable every sort of vibration in the phone's settings. The vibration motor is probably stuck and it is probably getting damaged more if it keeps trying to spin like that. What did you think - if the phone survived one fall it will survive 10 more just as well? Try the warranty, there's a good chance they'll cover it. Or learn to live without vibration.
Click to expand...
Click to collapse
I didn't think like that. I guess it's like every time it fell down I felt a relief, because nothing was broken (I wasn't throwing my phone around my house, as I said, it OCCASIONALLY fell). Anyway, thanks for help - I'll try the warranty, just wasn't sure if they will accept it at the service.
I have a Moto G and it seems like the screen response sometimes just stops working. When it is working all is well. I have tried few of the touch applications and they are all good. If i put it into sleep and press the power button, i can unlock the phone but no response at the home screen. Sometimes it works great for hours and then would stop. Don't think its a screen issue.
It's out of warranty so sending it back is out of question. I don't think it ever got wet or water damaged. Don't know much of the history on this. Would appreciate the help.
EDIT:
1) I reflashed the stock Telus Rom again last night, but issue hasn't changed much.
2) I disabled the lockscreen (set to none) and seems like it only registers one touch then stops as was the case with the lockscreen. Sometimes it just keeps working fine.
Just trying to figure out if its a software issue or a touchscreen issue. The hard buttons all work fine.
Stock? Which version?
Third party ROM or Kernel?
Does it happen randomly or only while connected to the charger or USB?
rmrbpt said:
Stock? Which version?
Third party ROM or Kernel?
Does it happen randomly or only while connected to the charger or USB?
Click to expand...
Click to collapse
Kitkat 4.4.4 Stock Telus/Kodoo Rom.
Happens Randomly.
EDIT: Added some notes above.
If it keeps doing it after a full clean flash then I would bet it's an hardware problem...
rmrbpt said:
If it keeps doing it after a full clean flash then I would bet it's an hardware problem...
Click to expand...
Click to collapse
Hardware wise is it the lcd/digitizer or motherboard ? Trying to figure that out.
Sorry, can't give any insight on that. I don't even know if there is an easy way to be able to know what of those two is faulty.
Just out of curiosity. Are you in a very moist/damp/humid (not sure what's the right word for this) area?
Do you have sweaty fingers?
I'm asking this because I also feel kind of an unresponsiveness whenever the screen has any moist on it or if my fingers are sweaty.
So, I pick up my device from the wireless charger, a minute later, it buzzes.
I put the device down on my desk, it buzzes every minute or so. Yet, there's NO notification that tells me something needs attention.
The constant buzzing is driving me nuts. If I have the sound on like I do at home, it's accompanied by the default sound every time a buzz happens.
Anyone know what's going on? And, can I stop it?
No, turning off the device and putting it on my pocket isn't an option because I need to be using the device.
It sounds like a replacement :-/
sackynuts said:
It sounds like a replacement :-/
Click to expand...
Click to collapse
I don't think there's anything wrong with the device, I think it's got an issue with something running that is making it buzz so often but for the life of me I can't figure out what it is that's running.
***FIGURED IT OUT*** It was the software update that I paused. Seems the S8+ kept buzzing to tell me that it wasn't done. It is MEANT to be annoying***
Fixed the buzzing by downloading the rest of the update and not applying it.