[Q] Nexus 5 stopped being able to vibrate - Nexus 5 Q&A, Help & Troubleshooting

So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.

thexlizardxking said:
So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.
Click to expand...
Click to collapse
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.

bblzd said:
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.
Click to expand...
Click to collapse
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?

thexlizardxking said:
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?
Click to expand...
Click to collapse
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.

bblzd said:
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.
Click to expand...
Click to collapse
That's good. I hit it a couple more times, and it's working right now. I'll see how it progresses.
Thanks

Related

Screen won't stay off from proximity sensor or using the power button

I have searched and all that came up are a bunch of issues with the screen not coming back on. This is not my issue, I wish mine would stay off. I have tried every method I know and my cheek keeps switching calls, hanging up, and dialing other numbers while I am trying to make a call. I've tried the power button method of hitting the power button and continuing the call, but even that hasn't fixed the issue. For the life of me, does anyone know of a "fix" for this? I'm about ready to break this thing in half. Thanks for any and all help.
One more thing, does anyone here use the google VVM? I had it working at one point on my D2, but ever since I switched to the TB I have had trouble getting it to work. I have tried the *71 or whatever method, but I still can't get it to forward. I can log in and see my old messages fine, but for some reason I can't get this one to forward the calls to GV for a message.
Ok, are you rooted, and of so, what ROM are you using.
I've seen some posts where people have problems with their proximity sensor, and they said blowing compressed air in the speaker (back of phone under kickstand) has helped.
Has far as Google voice goes, I've never had a problem setting it up. Again, what Rom are you running (though I don't think I've tried a Rom that didn't like Google voice.)
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
Bamf 1.8.6 remix. I'll try that. I just don't understand why it still comes back on after hitting the power button while on a call. I had it set up on my phone before changing roms, and I had it working on the D2. And I'm kinda being misleading by saying that it's not "working". I can connect to GV via the app, but I can't get the settings in the VM menu to "stick" as the GV. It keeps giving me the prompt that it is not supported by the "carrier". So I tried the long method of forwarding my missed calls to GV via *71 and two other * numbers seceded by my GV number. But for some reason the calls still won't forward if sent to VM. The only reason I have it is so that I can delete my messages without having to ever actually listen to them, I hate VM altogether, but verizon keeps giving me those popups when I have a message and they won't go away till they are either listened to, or deleted. And I'm not paying 3 or whatever dollars a month just so I can use something that is free though other methods. Thanks for your help.
My proximity sensor has never been the slightest bit reliable on any rom including stock
The proximity sensor on the Thunderbolt is located on the top front face of the device, inside the "V" of the Verizon logo. It can seen under bright light. It seems to be quite sensitive to dust, which causes the screen to turn on/off unexpectedly.
Carefully blow a bit of compressed air into the earpiece grill, and into the small gap between the glass and plastic housing shown in the circle, and it should clear it up.
I've had problems with my proximity lately as well.. Been hanging up on people (it's very embarassing) during important calls. It's making me almost switch phones. This happens on ANY rom these days so it tells me it's a hardware problem at this point. Also, usually after I get a phone call and hang up afterwards, the entire phone is unresponsive until I hit the power button on top and hit it again to wake up, then everything is functional again. So annoying.
Diversion said:
I've had problems with my proximity lately as well.. Been hanging up on people (it's very embarassing) during important calls. It's making me almost switch phones. This happens on ANY rom these days so it tells me it's a hardware problem at this point. Also, usually after I get a phone call and hang up afterwards, the entire phone is unresponsive until I hit the power button on top and hit it again to wake up, then everything is functional again. So annoying.
Click to expand...
Click to collapse
I've always felt like it was a hardware problem.

No Sound / Freezing Issues

This morning my alarm did not sound. Checked all settings everything was set to on.
Tried to call the phone no sound. Re-booted and everything is now working as it should.
Also 3 times in the last two days the screen has frozen and I have had to reboot the power using the power button.
Has anyone else had these issues?
I am using this as stock with the latest OTA update.
Same issue here.
Everything is working fine, but ~1-2 Times a day the Screen stays black and won't turn on again until a reboot via the power button. But the touch is working, because after the reboot some of the apps on my homescreen are moved (because I moved them while whiping on the black screen). Everything else is fine, CM11S Stock latest, *33R.
Just changed the Gov from "Interactive" to "On Demand", no other Modifications.
Greets, Alex
I'm having problems in this area as well, my notification will not work. I do not get any notification sounds at all even though everything is on. My call ringtone work fine, nut no notifications, not from email, or my third part oultook email app, and neither from my SMS's. It was all finw in the beginning but now it just stopped working. I got the phone with 33r and stock, have not done anything to the phone yet, and don't want to, but i cant figure this issue out.......any help would be greatly appreciated......
Same problem here.
kevace1 said:
I'm having problems in this area as well, my notification will not work. I do not get any notification sounds at all even though everything is on. My call ringtone work fine, nut no notifications, not from email, or my third part oultook email app, and neither from my SMS's. It was all finw in the beginning but now it just stopped working. I got the phone with 33r and stock, have not done anything to the phone yet, and don't want to, but i cant figure this issue out.......any help would be greatly appreciated......
Click to expand...
Click to collapse
I have also same problem... Do you get any solution for this ?
Just realize with your post that I have not posted an update......I like a certified dildo, had my phone in 'night' mode from the advanced power menu.... Put back to normal.....issue resolved......I would prefer more notification choices out the box, but that's easily fixed.....
Sent from my A0001 using XDA Free mobile app
Perhaps related to Quiet Hours getting stuck?
kevace1 said:
Just realize with your post that I have not posted an update......I like a certified dildo, had my phone in 'night' mode from the advanced power menu.... Put back to normal.....issue resolved......I would prefer more notification choices out the box, but that's easily fixed.....
Click to expand...
Click to collapse
Interesting. I've been having the same problem, and this prompted me to take a look at my Quiet Hours setting. On the Quick Settings panel I noticed that the Quiet Hours icon was lit. That was odd, because I was well outside of the quiet hours I had set. When I tapped the icon, it would not change. I had to long press, toggle a setting, and exit back out before the icon started working normally again. Now everything seems to be fine. Hope this helps someone; the problem was driving me nuts!
I too have had this issue! No lights, sound and action
But I solved my problem :=) on my own because I'm Mister Wonderful :>
I reinstalled the quiet hours tile.
Then I went into quiet hours setting and changed hours from 00:00 & 00:00 to 01:00 & 07:00. The latter being outside the current time of day I was working in.
Then I went back to the quiet hours tile and turned it off. Holy Smokes this time it actually worked.
Because the power charger was connected the notification lamp began to burn green again. SMS notification sounds were heard. Even "You got mail" wasn't afairid to stand up to be heard.
Another wonderul day in paradise!

[Q] Phone only rings for about one second and then stops.

After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.

Phone freezes up

Has anyone experienced your U11+ freezing up.
It has happened to me about 3 times.
It generally happens over night while it's charging. I get up one of those mornings and the green light is on, remove the charging cable and I can't wake up the phone. I can't even turn off the phone by pressing and holding the power button to kill the device. The only way is to put it into download mode by simultaneously holding down the vol down key and power key, and then when the menu comes up to select the reboot option to get the phone back to normal.
Has anyone else experienced this or know what could be causing this to happen?
The problem is that I use my phone as my alarm clock, and when it freezes up, my alarm doesn't work.
Any suggestions anyone?
No problem like that until now.
However, noticed sometimes that the my alarm, which is setup for vibration only, only vibrates once and then continues silently alarming until I turn it off.
Happens randomly but still strange. I've to try with another clock app.
That's really odd.
I'm going to turn off the always - on feature and see if I get anymore freezes. I had another one this afternoon.
I'll report back after some time and let you know if there has been no more freezes.
I'm just updating to the latest update 1.23.709.3 and see also how it performs.
I'm a bit concerned about this random freezing that I have experienced since I got this device.
If it persists I may ask for a new one.
globalgpj said:
I'm just updating to the latest update 1.23.709.3 and see also how it performs.
I'm a bit concerned about this random freezing that I have experienced since I got this device.
If it persists I may ask for a new one.
Click to expand...
Click to collapse
I'm still on the October security patch so I'm expecting one for the December period soon I hope.
In regards to your freezes I've not encountered anything like that so far been working flawlessly so far if there is anything I can test let me know
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
globalgpj said:
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
Click to expand...
Click to collapse
I have been using the AOD since I got the phone yesterday. Not a single freeze
Galactus said:
I have been using the AOD since I got the phone yesterday. Not a single freeze
Click to expand...
Click to collapse
Thanks for letting me know.
I guess I can rule that feature out as a probable cause.
It must be some other app that's causing this issue. But it's a pain to go through the process of finding out which one.
globalgpj said:
Thanks for letting me know.
I guess I can rule that feature out as a probable cause.
It must be some other app that's causing this issue. But it's a pain to go through the process of finding out which one.
Click to expand...
Click to collapse
Yeah trial and error isn't fun. I'd probably factory reset though and see if it happens with barely any third party apps installed.
globalgpj said:
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
Click to expand...
Click to collapse
I have the HK model I think and I had the AOD when I first got it, set to motion and nothing has happened to my phone in regards to freezing fingers crossed. I have disabled it for the moment as I noticed a greater battery usage overall, I believe between 9-10% overnight and only 2% when I had it disabled.
Hopefully you find the problem otherwise see if you can get it replaced...
Since not using the always-on feature, I don't have any more freezes. Must be some conflict with the alarms and always-on. Can't see what else could be causing those freeze ups.
My phone surprisingly just froze up yesterday. But at least it's been a long while since not having the always-on feature enabled. With always-on enabled, it seems to have happened every day.
The issue I have most about this, is missing that important call when I haven't realised that the phone is frozen, because sometimes I don't pick up the phone for hours.
I had to do a complete fresh install from scratch and I have no more issues. I believe all my issues came from using HTC's transfer tool when going from u11 to u11+. Importing all the settings features using the Transfer Tool has caused issues. I'll never use this tool again.
All good now.

Laggy Pixel - almost impossible to make/receive phone calls

Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
Ive updated to latest ota on pixel 1 and had no problems so far. You could check the dialer app is set as default dialer and all permissions are granted and maybe clear the apps storage/cache, force stop it and re open it and see if that solves anything? Could also check background apps and running services in developing options to see if an app is banging out the memory causing it to lag?
Sent from my Pixel using XDA Labs
pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
if you already did factory reset then it must be a sign of motherboard is dying soon or bad nand chip. motherboard failing on pixel is very common but it happens to less than 1% of people. there are plent of threads on reddit/xda on this.
What's the status of your Pixel? Is the bootloader unlocked? Rooted? Did you have any such problems on the December udpate?
As mentioned - I did factory reset as I thought it may help cure the problems, but it didn't.
I have never unlocked bootloder and phone is not rooted. All standard here.
I have the latest update installed and same problems persist ;/
I'll try another factory reset today.

Categories

Resources