Related
Out of the blue yesterday, my AT&T Moto X stopped vibrating. I noticed it first with the soft keys (home, back etc) but it affects everything from vibrating on ringing, to enabling silent mode, to unlocking with active display, to games.
I've tried rebooting and toggling vibration in settings. I've downloaded vibration tester apps from the Play Store. I only have the same ~70 or so apps that most of us use (dropbox, weather channel etc) and I don't run any obscure apps (less than 1000's of downloads), and I hadn't downloaded anything new for hours before the problem started.
I feel I've tried all the basic stuff, except factory reset, I don't think there's anything too obvious I'm overlooking.
So that leaves me facing either a hardware or software problem. I doubt its a problem with the physical vibration motor. Factory defects are so ridiculously rare that it should never be your first course of action. However, if it's a problem with the hardware I could try my local ATT Service Center. If it's a software problem, which seems much more likely, I could try a factory reset on the device. However it seemed a wise idea to post this question to the pros before I go down that road.
Appreciate any help you guys can offer.
AT&T Moto X
4.4
Not rooted
I would try a factory reset if you done everything else. My wife's Galaxy S3 did the same thing after the update to 4.3. A factory reset fixed it.
my gf's at&t motox running 4.2 lost vibration too. after many many reboots it would randomly work, or work very weakly (so it wasn't a problem with the physical motor, maybe it was an electrical connection to the motor?).
it was covered under warranty. they gave her a code, she re-did motomaker, and returned her original broken phone in the box the new one came in.
I hate the vibration in this thing. I would love mine to stop lol
Sent from my XT1058 using Tapatalk
I just performed a standard factory reset on the device and the problem persists... No vibrations, anywhere.
Is there anything else I can try? or am i headed to a service center?
Deenybird said:
I just performed a standard factory reset on the device and the problem persists... No vibrations, anywhere.
Is there anything else I can try? or am i headed to a service center?
Click to expand...
Click to collapse
You can sbf back to 4.2.2. I had a connectivity problem and a factory reset didn't fix it. But going back to 4.2.2 and taking the OTA did.
All the files are in the Dev section. If the links are broken I have copies of everything I can share. Except the 4.2.2 file for att I have Verizon.
Sent from my XT1060 using Tapatalk
If that doesn't work then your only other option is a warranty claim. Or live with it I guess.
The final verdict:
With nothing else working (factory reset, safe mode etc) I took the device to the ATT service center. They replaced the device, attributing the problem to defective hardware. Still find it hard to believe it was actually the hardware, but I don't see any other conclusions to draw.
Thanks for everyone's help.
Deenybird said:
The final verdict:
With nothing else working (factory reset, safe mode etc) I took the device to the ATT service center. They replaced the device, attributing the problem to defective hardware. Still find it hard to believe it was actually the hardware, but I don't see any other conclusions to draw.
Thanks for everyone's help.
Click to expand...
Click to collapse
At least it worked out and you have a working phone again.
I am with this problem right now and i can´t fix it.
After i flashed CM13 without Gapps my Moto X 2nd (xt1097 brazil) all vibration stopped working.
I tried going back to stock rom 5.1, 6.0 and even NX 10.1 but with NX i can hear something vibrating the phone, so i eliminated the possibilite of a hardware malfunction.
I don´t know what to do...
please help
Hello guys, I've acquired my New Moto X last monday and I've been using since then. It a fantastic phone and everything else but I have a problem with the moto voice. I use it like, 5 times a day, works perfect, but after a time, and I have a theory that it's conflicting with other apps installed in the phone, it became too slow. Like, i say my activation phrase, it beeps but nothing shows up, only 10 seconds later a very slow and laggy version of the interface. It also happens when I open it directly from the Moto app. After this, I've done a factory reset on the phone, and the Moto Voice came back to life... BUT, after 3 days it started again... Then I done it again... And guess what in 24 hours the same error. The worst part is that I dont' know if they are going to solve this error, I have already reported it but I don't know... And if I send it back to the store to get a new one I'll probably saty almost a month without a phone... Anyone else have this problem? Any solutions
Did you try clearing cache?
Also, are you on the latest version 6.1.10.1?
Yes to both!
I found the OK google feature responds faster and better. Just as long as you don't want to command other apps.
I'm having the exact same issue. It's very slow. Same issues after factory reset. Also - when it does work, works with Google Now, but none of the MOTOX apps like 'find my phone' etc.
any resolution?
Same thing here
I have had the same issue. I tried uninstalling and reinstalling several times with no luck. The few times I've managed to get through the entire voice set up it ends up un-checking my launch phrase with in a few uses and moto voice stops working. I keep providing feedback when the voice app fails and hopefully they will figureboit why this is happening. Happy to hear its most likely not my device and an issue with the app.
I have the same problem and i may have located the problem. Try turning off bluetooth completely and see if the problem still exists?
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.
Hello guys
Ran into a snafu yesterday, clicked home a N6 demo-ex from one of the internetstores here, it was cheap and I've always wanted one. Of course it came with a pre-unlocked bootloader and everything else you'd expect from a used Nexus, but I wasn't too bothered about that, I would have unlocked it myself anyways. Flashed MM on it as soon as the images were available. I played around with it for a few more hours, then late last night I decided I should move my simcard to the N6 and try Speedtest and a few other goodies. Speedtest went just fine, got the usual 64 Mbit over LTE, then .. I'll call my automated bank just to check the earpiece and speakers. "Dial .... call ended". Try again. "Dial... call ended". Put the simcard back into my Nexus 5, dialed the same number, worked perfectly. Back into the N6, same number, it dials, then just as it's supposed to start ringing, "call ended". Has anyone got any ideas as to what could be wrong here?
Done so far to find the error:
*Reboot *duh*
*Reflash MM
*Flashed 5.1.1, thinking it was a new modem and my simcard didnt like it. Sim is about 2 weeks old by the way.
*A couple of factory resets, just to be sure
This is the very last Nexus 6 these guys had on the shelves so I would really, really rather not have to return it but of course a phone that you can't use for phonecalls .. I already own a Nexus 7, don't need a miniversion of it. Bright ideas or even far fetched guesses appreciated!
Hey bud, I had a similar issue with my phone as well and the way to fix it is by rebooting exactly 6 times in a row....literally. Power on, power off power on power off etc........ Ive encountered that issue several times, it usually happens when i left my phone die and then reboot after full charge. I could only use data, no voice/text and sometimes it would be backwards, no data, voice text only
I posted this in an older thread but figured I would just go ahead and make a separate post about it.
Ever since I updated the phone to 5.1 it has crashed repeatedly, super laggy, battery life is significantly worse than kitkat, Turbo charge seems to take longer than on kitkat, my texts and calls won't go through, and on a rare occasion my phone will reboot by itself. I've cleared the cache regularly and have factory reset a couple of times and the problems will go away for about a week, but only to return again. I'm going to Verizon tomorrow to see if they can do anything.
Anybody else have these issues with their Turbo?
Sent from my XT1254 using XDA Forums
I'm not experiencing any of this. Have you troubleshot apps that you have downloaded as possible culprits? Also, did you upgrade via OTA or did you manually flash the 5.1 update via rootjunky? I've heard multiple people having issues with the flashed one.
Maybe it's one of the apps you have installed. Try a FDR and install your apps a few at a times. Try to pinpoint which app is constantly taxing your phone. If all else fails make verizon give you another 4.4.4 Turbo
So I went to Verizon yesterday and they couldn't do anything for me. I just took the OTA that came out yesterday and I am hoping it fixes more than the stage fright exploit. If not I guess I will be migrating back down to my old Galaxy S4.
Murd0c said:
So I went to Verizon yesterday and they couldn't do anything for me. I just took the OTA that came out yesterday and I am hoping it fixes more than the stage fright exploit. If not I guess I will be migrating back down to my old Galaxy S4.
Click to expand...
Click to collapse
If you haven't already, try using the Verizon Upgrade Assistant (that annoying thing that pops up every time you plug your phone into a computer) and select repair. This will do the cleanest wipe possible, reflash everything and bring you up the the latest firmware version. If you still have problems after that, chances are you're using an app that lollipop doesn't like, or you have a physically defective unit.
I ended up with what I think was a physically defective unit, and I got a warranty replacement straight from Motorola. The process was painless, and as long as the phone doesn't have any physical damage and was never exposed to water (in most modern phones, there's a water-sensitive sticker on the inside that changes color when exposed to water, so they can tell if you're lying), you basically just have to ask for it.
In fact, forget what I said in my first paragraph. Just get the Motorola replacement.
https://motorola-global-portal.cust...sion/L3RpbWUvMTQ0NDMzNDc3Mi9zaWQvWDgyS2RzeW0=
OK guys quick update I sucked it up and got the Motorola replacement and it works perfectly now, turns out I had a factory fault or something
My phone isn't laggy, but my Turbo charging is definitely slower, my WiFi is hit or miss at times, and the battery does seem to drain a bit faster but isn't too awful.
Sent from my Droid Turbo using XDA