Vibration motor dead? - Nexus 6 Q&A, Help & Troubleshooting

Hello all, here again with another issue that I haven't seen mentioned anywhere.
My sound and slow performance problem was recently resolved on its own after a complete revert to stock and back to running a custom ROM, but now I have another question. How do you know if the vibration motor is dead?
I took my phone apart recently to see what could be wrong, what could be loose, and what might be dirty, but everything looks really good, the speakers work, wireless charging works, everything seems fine. The only problem is that no matter what I do, vibrate will not work for anything.
Then I noticed what seemed to be the vibration motor, which is a little piece of metal with a rod going through, with metal rings that seem to just spin freely. It's still firmly attached to the motherboard, yet I get no vibration for anything. Even enabling it for my keyboard actually causes the keyboard to lag and skip letters, yet when disabled, its smooth as butter.
I also don't have any settings for vibration strength anymore in Kernel Adiutor, even after testing multiple kernels to see if maybe it wasn't supported.
Has anyone here had any of this happen before? I've already ordered a new motherboard to swap out with this one, but I just wanted to see if there was anything I could do to fix this, or hear what you all have to say. I don't mind spending the little bit of money to fix it myself, but if I could avoid shelling out about 60 for another motherboard, I would prefer to do that.

Related

[Q] Bad Digitizer?

I've noticed the last few days that my nc has a hard time unlocking. I start to swipe my finger across the unlock and it moves about 1/10 of the screen then shoots back. If I do it a few times, I might get lucky and unlock it.
Does this sound like the digitizer is going out? It's one of the first production models (wife bought it for me for christmas right after they came into the store). So I don't know if there was an issue with them at all or not.
Everywhere else on the screen seems to be fine, but it doesn't do me much good if I can't open the thing to read the books inside.
*edit
Just did a test on the bottom row of books, and they seem to be working fine in that general area. Is anyone else seeing this only when trying to unlock the nc from sleep/off?
Do you have it plugged in?
Yeah it seems to happen on my girlfriends NC, at least when it was running 1.1 Stock, not sure I've noticed it since 1.2. It's not a bad digitizer assuming you have the same issue which was right after resuming from sleep it will SOMETIMES be a little pokey for the first 20 seconds or so but after that it slides smooth as butter. It never really bothered me since I just assumed it was reloading some software into memory. The only other common issues I know of are issues when plugged in as mentioned above and the seemingly obvious but often overlooked dirty screen.
I do notice in general that both NC's I use are a little less than perfect when touching the far corners (I often need to jab while making grunting sounds) but I figure it's an e-reader so they probably didn't spend a fortune on the capacitive part of the screen. If you are so inclined, loading up CM7 disables the lock screen by default and there might be a way to do it in stock as well although I suspect you will still occasionally need to give it it's 20 seconds to get things running again.

[Q] Haptic Feedback messed up?

So I have this phone a week or more now and I have been having no issues whatsoever except for the battery timing being very low which I have came learn how to use more efficiently reading guides however I've come across a new problem..a problem that seriously driving me crazy
First of my phone hasn't been accidentally dropped or suffered any shock
So I've been texting and typing a lot with the phone and I loved the feeling of its haptic feedback which was very strong I think the intensity was maxed out but since last night I've been feeling it weird to type messages on it and I realized the phone hasn't been vibration back strong enough on its feedback and now vibrations is so weak It is really killing the joy, at first I felt that may be I'm being paranoid and nothing is wrong with it but after a good night sleep I am still feeling its Not intense enough for me,
I tried the screen test and the phone vibrates like a beast! but when ever it comes to using the keyboard the vibration is so low, on the intensity options the phone vibrates strongly but on keyboard its very low! I can't figure out what the problem is the vibrating is fine with other things but not with haptic feed back.. anybody know what I should do? is it a software or hardware problem? Its my first smart phone and touch screen experience and its really got ruined...
-edit-
Okay just found out something new when I used the Swype keyboard the haptic feedback got stronger so that means this isn't a hardware problem? but if its a software problem I have no Idea whats wrong with it cause I haven't done any updates on it, have reset the phone plenty of times but no avail..
Sorry Wrong forum please close.

Touch Screen Issues

I've started to have touch screen issues the past few days.
Any idea what may cause it?
Sometimes, when I touch the screen, say in settings, I touch one item, but a different item is selected somewhere randomly on the screen.
Happens in TWRP as well. If I select options to wipe, it will select others, and then it doesn't swipe over to execute the action.
No ideas? What would make touches appear where I don't touch, even on TWRP?
I tried the keyboard calibration on HTC's keyboard.
Any ideas? Screen protector?
It comes and goes.
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
mcwups1 said:
I can't believe no one else is having this issue now.
I don't do stupid things with my phone, like drop it, put it in my pocket and sit on it, and wash it with soap and water.
Since I've started running Lollipop, it appears that my case is causing this issue. I've never had this problem before.
However, I updated my wife's phone to Lollipop Sense and now she is having the same issues with a different case.
Take the cases off, and they work more responsively.
I can only chalk this up to being a Lollipop issue, and hope it will be fixed soon.
Click to expand...
Click to collapse
I opened another thread about a similar issue I'm having after Lollipop. My gesture launch randomly stops working and I have to reboot. No other issues for me though. I have an anti-glare screen protector on mine, but had no issues before the update. I've thought about a factory reset to see if that would cure what ails.
I'm on tmo but have the same exact issues. This is what i've found so far...
I turned on the developer options and turned on show pointer. This will show you where the touches are landing.
If you scroll down slowly, you can see most of the touches are in line (up and down) and not random on the screen.
I've removed all programs that have screen overlays (screen filter, twilight etc)
I've removed the cases thinking they might be causing the issue, but removing them only slightly improved the issue I thought...
Sometimes its hard to reproduce the effect, its not consistent. So this leads me to believe that it could be a process that's running in the background that calls attention at the moment you're touching the screen, and then refocuses the screen to your point of contact. And in between it thinks you're moving your finger when you really aren't.
In any event, I can't find the exact cause of this. But, it definitely started after the update to lollipop. I had none of these issues before. I even got the phone exchanged because I believed the digitizer went bad or something. But this issue exists on my original phone, its replacement, and now on my wife's current phone and that phones replacement (across 4 phones).
I'm currently working on my wife's replacement (4 or 5 non-oem programs installed) and continue to have the problem. But it is not consistent as I can't readily reproduce it.
What i've done to try and learn more is when I see the screen pointer light up in random places, I keep pressure on the screen so I can observe where the screen is registering contact. It almost looks as if it's trying to pull down the shade. Whether it be because of the dual points of contact and it thinks we're swiping down, or because of another program that is stealing focus for whatever reason.
If anyone else has insights into this, please let us know as this is more than frustrating! I keep calling people in hanouts with a lot of people and they aren't happy about it lol.
Also for reference, we're using ADW ex launcher instead of Stock HTC Sense. But even when I remove ADW (uninstall) and run sense, it continues to happen. So it's not that.

Touch Sensitivity is Wonky at Times

So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Just to weigh in I also have this issue not very often but enough to notice it. Especially since the last update also when I zoom with the stock camera it just freezes.
I'm having similar issues, camera fixes if i reboot but thats annoying if your trying to get a moving shot, also noticed it sometimes freezes switching to portrait mode.
For the screen freeze I have found if i use my finger print to unlock when the screen isnt responding its starts to work. but i didnt have the problem until i put on a crappy glass screen protector.
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
godsfilth said:
I just got the phone and im using arters r2 kernel with f2fs on data, as well as magisk and xposed so i wasn't sure if it was something i did but since others are seeing it ill assume its something with the phone and see if theres any fixes or decide if i should return it.
Click to expand...
Click to collapse
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
jonchance_84 said:
Mine does that too, but I'm not on the new kernel. Maybe it has something to do with the ambient display being turned on.
Click to expand...
Click to collapse
hmm maybe, i only had show new notifications turned on but ill try turning it off and see how it goes over the next couple days
Ok so since turning off my ambient display, no issues so far.
karlkarloff said:
So, I've noticed a weird problem my RP2 has. I carry it in my hip pocket, and at times (happens frequently enough to be annoying) when I pull it out to use it, the screen doesn't respond to a normal touch. I have to really push down hard on the screen to get it to register. If I let it sit for a few seconds/minutes the touch responsiveness fixes itself and it can be used normally. Not sure if it could be a physical problem with the digitizer/connection or if something is going on when it is "asleep" in my pocket. Just weird that it fixes itself. Anybody else see anything like this or have a suggestion as to what it could be? The phone is totally usable, and even when it messes up it still works I just have to push super hard to get it to do anything. Sometimes i'm afraid I'm going to snap the glass, although I don't really think that is likely to happen. Thanks for any ideas.
Click to expand...
Click to collapse
I use Ambient Display and sometimes the screen behaves as you've described where it won't reach to touch, but I've always just given it time/pressed the power button repeatedly until the screen came on (or continued to tap the screen lightly)... never tried pressing down very hard.
Not to Necro a thread but I've experienced this aswell, infact it's happening right now as I type this.

Vibration Intensity

Is there any way to increase the vibration intensity? I've used this phone for a few months and always keep it on vibrate (like all my other phones). I have literally missed 100% of incoming phone calls and messages because I could not feel or hear the vibration.
Same feeling...
I'm unfortunately think that there's no way to... Without root and proper dev (kernel and associated sys app).
And like huawei seems to 'never' revert their move...
But if someone may lead to something that could improve...
Thanks in advance
Tapa'DoC'eD
Well, I think there is a way. But it's for sure one nobody likes to go: Opening the phone, taking out the vibrator, open the vibrator, add/glue an additional vibration plate to the existing one, put back in the vibrator without ist housing again, close the phone again. It's the way I will go as soon as I'll insert also a headphone jack into my lovely P30 pro. Will show it on Youtube in some months - if I'll be successfull with it.
I just bought the p30 pro and I too regret this lack of functionality !
I was just about to ask if someone had a solution, an apk, to remedy the problem, and I see that apparently not.

Categories

Resources