Very Laggy and no vibration - needs replacement - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

Hello,
I on lollipop (soak test) build on my moto maxx. It was working great until one day there was no vibration. The vibrator wasn't working at all. The phone then was super laggy. Every action took a good 2-3 seconds to execute.
2 reboots failed to fix it. A final 3rd reboot fixed the issue. I have not faced the issue since.
I don't really know what the issue was about but it was annoying.
I just want to put this out there because there was not a single post about it.
Cheers !
- Navneet

Problem persists
After the official 5.0.2 update..things were looking good for a few days.
The vibration issue is back and it takes numerous restarts to get the vibrator to start working again.
There is nothing about this anywhere else. I've tried safe mode and it doesn't seem like a software issue.
A lot of Motorola users (Droid MAXX and few others) have been complaining about vibrator motors being faulty which just shows the quality of parts being used here.
Verizon has been replacing the motors or handsets if within warranty. However Motorola doesn't seem to acknowledge the issue.
Anyway this is my last Motorola device. I've picked up an S6 Edge and extremely happy with it.

rednav said:
After the official 5.0.2 update..things were looking good for a few days.
The vibration issue is back and it takes numerous restarts to get the vibrator to start working again.
There is nothing about this anywhere else. I've tried safe mode and it doesn't seem like a software issue.
A lot of Motorola users (Droid MAXX and few others) have been complaining about vibrator motors being faulty which just shows the quality of parts being used here.
Verizon has been replacing the motors or handsets if within warranty. However Motorola doesn't seem to acknowledge the issue.
Anyway this is my last Motorola device. I've picked up an S6 Edge and extremely happy with it.
Click to expand...
Click to collapse
never heard about this issue, try installing official firmware from rsd, to play safe.

Related

[Q] That screen...

I've scoured the internet in attempt to resolve this issue, and I know it's been talked about many a time before, but this just doesn't have an answer yet afaik.
Does anybody have any experience with fixing the inaccuracy of the touch screen after prolonged use? I love the nexus one, it's by far the best phone I've owned; but this little bug makes the phone completely unrealistic in real-world use.
If this isn't a software issue, it has to be something with the digitizer being powered off and back on to remove the accuracy bug. In that case, is there any low-level way to turn the digitizer off and back on as fast as possible every X seconds? That would mean losing touch capability for a few milliseconds, but is much better than locking and unlocking the phone each time it "goes wild."
I had given up all hope that this issue could be resolved in any fashion as dodgy hardware is, well...dodgy. Nothing can be done about it right?
I haven't had a screen wonk since starting in on the CM7 nightlies many moons ago!
IN YOUR FACE WONK!
Is there an FAQ about this digitizer issue?
JoeSchmoe007 said:
Is there an FAQ about this digitizer issue?
Click to expand...
Click to collapse
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
DirkGently1 said:
No, but it's been covered so extensively that nobody really mentions it any more. Either that or others have found what i have, that somehow the CM7 ROM mitigates the problem. Seriously, i haven't had an issue with it for months!
My particular N1 was never good with stock ROMs. Hated them and gave me endless trouble with one thing or another. It's the polar opposite for me with CM ROMs. Never any issues at all. No call or screen wonk, none of the bugs that others often complain about. It's like the phone has an attitude!
After flashing something ridiculous like 40+ CM7 Nightlies and stable releases, i've not had to wipe data once
Click to expand...
Click to collapse
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Hollow.Droid said:
Basically the digitizer has a couple of quirks. One is that after prolonged use (I found it to be completely random) the accuracy goes berserk, registering touches nowhere near they actually are. Secondly there is a switching of the axis when you cross two points: video. They are hardware related so there is no fix. The wonk is a problem with CyanogenMod7 specifically, causing black screens when receiving calls.
Personally I rarely if ever come across the digitizer problem and have never came across the wonk. They aren't deal breakers but can cause a few problems if you play a lot of multi-touch games.
Click to expand...
Click to collapse
When accuracy goes berserk - does powering phone off/on help?
JoeSchmoe007 said:
Can you please describe what the digitizer issue was/is? I just ordered N1 and haven't received it yet. And what about call wonk? I haven't seen anything about this one.
Click to expand...
Click to collapse
Well, the touchscreen issue is nothing more than a bad digitizer that was released with the phone and never improved during manufacture of the device. All Nexii have the same one, although people suffered the problem in varying degrees. What would happen is every so often your touch on the screen would register in the wrong place so you may be selecting a shortcut on your homescreen to launch an app, but it might register the touch as being an inch higher/lower/somewhere random. the solution has always been to simply press the power button to turn the screen off/on again. This would fix the issue... until it occurred again.
The call wonk is really in two parts. Stock GB ROMs had a habit of introducing a slight delay in one party being able to hear the other during the start of a call. On CM7 ROMs it was a more significant issue of black screens and freezes during the start of a call. These didn't affect affect everyone though, and even Cyanogen himself didn't have it on on his own device.
EDIT: The other issue affecting the N1 was a weak, and often failing, power button. With the need to keep using it to fix the screen wonk the problem was made worse. That's why you might often see mentions of Trackball wake as it reduced the need to use the power button, therefore extending it's life. Trackball wake is only available on custom ROMs so bear that in mind too!
The phone isn't perfect but with the custom ROM devs doing there thing it's pretty decent for me
Hollow.Droid and DirkGently1 - I appreciate your responses.
Can I bring your attention to my other question to which nobody responded yet?
http://forum.xda-developers.com/showthread.php?t=1077733
JoeSchmoe007 said:
When accuracy goes berserk - does powering phone off/on help?
Click to expand...
Click to collapse
When the issue happens you just lock and unlock the screen to fix it. No need for a reboot.
This issue isn't really such a big deal. It happens once a week or so, and it takes a few seconds to black out the screen then unlock, problem gone.

[Q] New behavior/ proximity sensor

Hi all,
So a couple months or so ago, my dad got an S5 and handed down his Droid DNA to me which I promptly rooted and rom'd. Fast forward to last week (didn't take long), and I dropped the DNA and broke the screen. So while I'm waiting on a new screen to arrive for the DNA I activated my trusty Bionic. Only now, again only a short time since last use, the proximity sensor is giving me issues which it hadn't before. Now, as soon as I place a call the screen goes black and won't turn back on until the caller on the other end hangs up, as well as the sensor giving off that faint red light I've read so much about. I had slimkat installed and thought that was the issue, so wiped clean and installed PA. The problem persisted and I just tested a call on stock and now it's happening on stock too! Whereas beforehand it wasn't
I've read that an app can be causing this to happen, but between my stock rom, and PA, there are no common "running" apps so that can't possibly be the problem unless it's one app on stock and a separate app on PA which seems unlikely. I have replaced the screen before, but I used the phone for probably another 8-10 months after that before activating the DNA and putting the Bionic on the shelf, during which time I had never once had this issue.
Does anyone have any experience with this? If so what did you do to fix it? It's a super annoying problem :/
Thanks in advance, hopefully somebody's got the answer I need!
EDIT: Just tried blowing really hard through the speaker port while on stock in case something got lodged in front of the senso, and that appeared to fix it! Made a voicemail call and the screen stayed on while allowing use of the keypad. Switching boot options in safestrap to PA to try there.
...no dice in PA faint red light still, and black screen with no access to keypad. Maybe a rom issue, will investigate further I guess...

Call issue

I've got a problem with calls. On stock ROMs and Paranoid Android, with every kerenels.
Sometimes I can't hear the person with who I'm talking but only on "normal mode". When I activate loudspeaker or plug in headphones I can hear without problems but after deactivating or plugging out the problem comes back and I can't hear anything. This occurs not always but very often.
Can someone helps?
I had this issue you may want to check with other people around here who are running cyanogenmod as far as I know mine was spoiled so I had to change it no idea if it was cause by cyanogenmod highly doubt it
I have the same issue! I actually had it when I was running OEM software, before rooting I sent it in to sony with the complaint 3 times. Each time they returned it with simply a software update applied.
I find if you cover and uncover the light sensor a couple of times it tends to fix itself, but its frustrating!
Yes, very frustrating! But this must be a software defect.
Maybe someone could make a fix...
Any help?
I highly doubt that it is a software defect issue but if it is a really software defect issue causing the ear speaker to fail then sony has some explaining to do nevertheless some of them reported the same issue with cyanogenmod 11.0 so honestly I dont know what is causing this but overall it seems like quite a big issue..
http://talk.sonymobile.com/t5/Xperi...e-can-t-hear-me-with-my-xperia-zl/td-p/758763
did you amplify the speaker or did anything to it, in the past etc ? like fauxsound
if you never did did you remain on stock kernel with cm11 all the way
Yes. I used some mods like pxa, but without any mods and with the problem exists
kael2404 said:
Yes. I used some mods like pxa, but without any mods and with the problem exists
Click to expand...
Click to collapse
then your hardware is damage sent it to the service centre
But it exists only sometimes and mostly with weak range
kael2404 said:
But it exists only sometimes and mostly with weak range
Click to expand...
Click to collapse
yeah it is damaged how long did you have your xperia z cause I had mine for 1 year 3 months before it died today it works fine.
huh? so what is causing this? sound-mods or just bad luck? had my xperia z 1 year 4 months and so far its ok... (*touch wood*) will be gutted if it dies...
must be sound mod blow out the speaker o.o no idea but I got mine fully replaced.
I had the same Problem. After installing Sound About from playstore and disabled headphone detection the Problem is gone
haha it isn't the old 'dust in the headphone socket' problem is it?

[Q] Phone Questions

So I'm thinking about getting an LG G2 on Verizon, and I have a few questions about it. Is the bootloader unlockable/can custom ROMs be installed on the latest stock OS? Is battery life good? What is your average screen on time? Have you had any problems with the G2?
Thanks for your time.
redusk said:
So I'm thinking about getting an LG G2 on Verizon, and I have a few questions about it. Is the bootloader unlockable/can custom ROMs be installed on the latest stock OS? Is battery life good? What is your average screen on time? Have you had any problems with the G2?
Thanks for your time.
Click to expand...
Click to collapse
My experience: xlnt screen, long battery life, easily bootloader-unlocked by Stump v1.2, TWRP is good custom recovery,
and there are lots of good roms being cooked up. See XDABEB and other great dev's work in dev sections here.
On the two I own, both had GPS issues. I took xlnt advice from others here and opened the case, located the GPS antenna,
and put a bit of black tape underneath it to hold it up to the connection on the caseback. Second part of GPS repair is
installing Play Store app called 'GPS Status". It runs in the background and keeps your GPS honest. I had another issue
caused by flashing several roms in a row: lost double-tap-to-wake which is essential on this phone for me. The fix sounds
kinda complicated, but it's done in 20 minutes and now tap to wake is perfect. That fix is also here on xda.
It's a great phone that seems to do everything well.
Thanks!
The reason the GPS gets goofy is because the backplate clip isn't springy enough. I've owned a few Verizon models and never had an issue with GPS.
Later versions (seems fixed now) of Maps would mess up my compass heading at a stop. I never taken my phones apart.
Best phone ever. I love the stock rom. Been using G3 ports lately

Xperia X Performance (F8132) Accelerometer failure & Screen Auto-rotate irresponsive

Xperia X Performance (F8132) Accelerometer failure & Screen Auto-rotate irresponsive
Hi All,
I got an issue bothering me since I bought Xperia X Perfomance (F8132) Mid June.
The auto rotate function failed after a while but everything goes fine after reboot.
When it fails, I use "Xperia Service Menu" -> "Service Tests" -> "Accelerometer",
then all X,Y,Z are zero and the ball just sticks and freezes at mid.
I bought from Taiwan and I can find 15 more people having the same symptom with me on 2 forums
( http://mobile01.com and http://gamer.com.tw ).
Hence I don't think it's only me and it's a common issue or common yield problem for Xperia X Perfomance.
I post here because I'd like to find more people with the same issue and raise the attention of SONY in order to find the root cause (i guess it's either over-heat causes this or accelerometer yield issue) and give a patch.
Now I'm using a APP "Rotation Control" to workaround this, but all photos cannot records correct orientation data and no auto-rotate is kinda inconvenient.
For a flag-ship and high-priced cellphone for SONY this year, it is very disappointing to me. :crying:
Version: 35.0.A.1.227 and 35.0.A.1.238 both occur
huangjs said:
Hi All,
I got an issue bothering me since I bought Xperia X Perfomance (F8132) Mid June.
The auto rotate function failed after a while but everything goes fine after reboot.
When it fails, I use "Xperia Service Menu" -> "Service Tests" -> "Accelerometer",
then all X,Y,Z are zero and the ball just sticks and freezes at mid.
I bought from Taiwan and I can find 15 more people having the same symptom with me on 2 forums
( http://mobile01.com and http://gamer.com.tw ).
Hence I don't think it's only me and it's a common issue or common yield problem for Xperia X Perfomance.
I post here because I'd like to find more people with the same issue and raise the attention of SONY in order to find the root cause (i guess it's either over-heat causes this or accelerometer yield issue) and give a patch.
Now I'm using a APP "Rotation Control" to workaround this, but all photos cannot records correct orientation data and no auto-rotate is kinda inconvenient.
For a flag-ship and high-priced cellphone for SONY this year, it is very disappointing to me. :crying:
Version: 35.0.A.1.227 and 35.0.A.1.238 both occur
Click to expand...
Click to collapse
I also have that problem. No more auto-rotation after a while (1-2 days) . Only a reboot fixes that
DiLeon said:
I also have that problem. No more auto-rotation after a while (1-2 days) . Only a reboot fixes that
Click to expand...
Click to collapse
Thank you for letting us know.
It shows it's not a regional FW issue but a global HW or FW one.
I wonder if SONY knowing this. If not, we need to address this and push SONY to work it around.
And if it is not workaroundable, SONY will have a big problem.
I have the same issue on my Xperia X (F5121) bought in Sweden. Haven't checked the accelerometer but the behaviour is the same and reboot is only fix.
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Sent from my F8131 using XDA-Developers mobile app
HellRoot said:
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Click to expand...
Click to collapse
Same
HellRoot said:
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Click to expand...
Click to collapse
Can you specify "messed up"? I've had issues with the touch screen also, mostly that it registers a tap while I'm scrolling resulting in involuntary tapping on links. Also it often takes a while to start scrolling, as if the screen has a hard time recognising the swipe.
I have the same problem. The accelerometer stop working 15 minutes after reboot.
Help me verify if is caused by a third party app or not.
Use your phone in safe mode for a while.
I'm from Hong Kong, the accelerometer and its auto-rotation of my x performance has the same problem that it won't work until i reboot my phone.
I dont think that is caused by a app crashing when the problems occuring in all around the world.
The issue didnt come to me when I was not yet update to 35.0.A.1.282. Please notice this problem SONY. It seriously affected the satisfaction from user of the phone from your brand.
There is a topic on the Sony support forum - see here: http://talk.sonymobile.com/t5/Xperia-X-Performance/Accelerometer-stops-working/m-p/1158490#U1158490
At least they are aware of the problem. As soon as it happens again on my phone, I will send them my logs. I will report any development...
It seems that I uninstall the AR effects in my phone and reboot, it works again
Rotation fails
Hello guys,
I have the same problem. Yesterday it worked fine, but today, the auto rotate don't work. Very disappointing. Only a reboot can help but not every time.
Sony has to do something with it.
Gyroscope/Auto-Rotation Issue
Hey everyone,
I'm also having this same issue, but only since the most recent update from late September. When trying to make a pic display as fullscreen by rotating the phone, nothing happens, unless I reboot the phone. Then within day or two, it starts happening again. When I go to camera it loads up and STAYS in landscape mode, no matter what I do, even closing it out and clearing out the cache & force stopping it then reactivating it. It seems like a software issue that Sony needs to address PRONTO!
It appears another thread here on XDA is dealing with the same issue. I tried shenlong85's idea and it seems to have fixed the issue, but I need another day or so to make sure. If you don't hear from me by Sunday (10/23), assume it's been fixed. Hopefully the Nougat update we're all about to get any day now will permanently fix it!
The memory uninstall updates only prolong the issues. Seems like the firmware issue earlier on.
Nougat... When are u coming?
shenlong85 said:
The memory uninstall updates only prolong the issues. Seems like the firmware issue earlier on.
Nougat... When are u coming?
Click to expand...
Click to collapse
Well, we'll see. I am giving my XP 'til Sunday........if no more auto-rotate issues by then, then I will consider your idea to be gold. lol Of course, once we get Nougat, I'm hoping it will ensure that the issue never comes back period. As of this time, the issue has NOT returned.
I bought my Xperia X Performance from Kogan who sells imports in Australia from Asia and I have the exact same issues with my orientation and touchscreen. However my jumpy touchscreen only seems to occur while charging.
RockStar2005 said:
Hey everyone,
I'm also having this same issue, but only since the most recent update from late September. When trying to make a pic display as fullscreen by rotating the phone, nothing happens, unless I reboot the phone. Then within day or two, it starts happening again. When I go to camera it loads up and STAYS in landscape mode, no matter what I do, even closing it out and clearing out the cache & force stopping it then reactivating it. It seems like a software issue that Sony needs to address PRONTO!
It appears another thread here on XDA is dealing with the same issue. I tried shenlong85's idea and it seems to have fixed the issue, but I need another day or so to make sure. If you don't hear from me by Sunday (10/23), assume it's been fixed. Hopefully the Nougat update we're all about to get any day now will permanently fix it!
Click to expand...
Click to collapse
I tried shenlong85's idea, but less than 24 hours after trying it, I switched my phone from Portrait to Landscape to view a 16:9 widescreen pic I had in my Album, and it WOULD not auto-rotate the pic. So unfortunately this "trick" doesn't work either.
Just have to hope Sony includes a fix with the Nougat update we're about to get any day now from them.
I'm noticing now too that once the Auto-Rotate function stops working, so does Smart Call Handling. Have to swipe screen once again to take calls. Hurry up Nougat!! lol
I'm having the same issue and the only help I'm getting from Sony support is to factory reset my device :\ I'm hoping Nougat makes it's way to our devices soon. I really like this phone and this is a pretty big issue to have.
SpencerElliott said:
I'm having the same issue and the only help I'm getting from Sony support is to factory reset my device :\ I'm hoping Nougat makes it's way to our devices soon. I really like this phone and this is a pretty big issue to have.
Click to expand...
Click to collapse
I agree Spencer. And yes Sony Mobile told me the same thing. I'll do a repair (which yes, includes a factory reset) only IF Nougat doesn't fix it. They say we're getting it "in or close to October", so I'm guessing it's gotta be coming any day now. Hopefully they include a fix with Nougat though and I don't have to do that. Getting tired of this BS with Sony. My Z3 had an issue where if I turned on Stamina Mode, it would 1) mess with my MMS (group/pic/video) text messages.........you don't know how many times I had to ask ppl to resend those to me and how much that sucked lol 2) Cause a "random" battery drain. Only fix was a factory reset. I FINALLY got wise and realized it was SM and kept it off. Found a great app called 360 Hibernation Master that did what SM was supposed to do but better, MINUS the buggy BS. But OF COURSE it doesn't work on any X series phone (at least not my XP), so I'm stuck with SM now. At least Sony Mobile FINALLY fixed that bug with SM so that's not an issue anymore. lol
It is a big issue, and it makes me not want to keep buying their phones.

Categories

Resources