[Q] All vibration stopped working and I can't fix it - Moto X Q&A

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

Related

[Q] Soft Keys Not Working

This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...

[Q] Screen not waking up while on phone call

Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
hmmm
carlosmeldano said:
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
Click to expand...
Click to collapse
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
really?
madhukarmohan said:
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
Click to expand...
Click to collapse
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
yes
carlosmeldano said:
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
Click to expand...
Click to collapse
Yeah, few r experiencing that. i hv seen complaints in sony blog and here too. I asked this question few days back. but, I didnt get reply.
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
thx
UltraWelfare said:
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
Click to expand...
Click to collapse
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
carlosmeldano said:
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
Click to expand...
Click to collapse
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
UltraWelfare said:
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
Click to expand...
Click to collapse
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
carlosmeldano said:
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
Click to expand...
Click to collapse
I hope everything goes fine
no success
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
carlosmeldano said:
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
Click to expand...
Click to collapse
Bring it to a sony service(or how's it called to your country)
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
carlosmeldano said:
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services are just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
Click to expand...
Click to collapse
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
UltraWelfare said:
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
Click to expand...
Click to collapse
yes, that's another option. the other option is to cry off from purchase (I can do it within a week), they return the money, and I buy another one. I'll see as this is not that disturbing problem and I have no other problems with the phone like wifi bug or anything else.
someone said it's a bug so I hope 4.3 next month will solve it.

[Q] Moto X (NOT ROOTED) - Wifi and Bluetooth problems

Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
rafaelrossignoli said:
Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
Click to expand...
Click to collapse
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
aviwdoowks said:
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
Click to expand...
Click to collapse
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
rafaelrossignoli said:
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
Click to expand...
Click to collapse
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
aviwdoowks said:
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
Click to expand...
Click to collapse
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
rafaelrossignoli said:
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
Click to expand...
Click to collapse
Correct.
I've sent my phone warranty. I'm a previous contact they told me it's probably a hardware issue. The battery comsumption has increased a lot and the explanation is that phone is constantly searching for wifi/bluetooth. Is it possible even with hardware failure?
When I get my phone back tell you what was it's problem and the possible solution.
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
rafaelrossignoli said:
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
Click to expand...
Click to collapse
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
samwathegreat said:
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
Click to expand...
Click to collapse
Well, wifi and bluetooth aren't working anymore since my last post. There's a big battery drain - something like 60% of battery life in 3 hours with phone - supposedly - in sleep mode, even when it is in airplane mode. It seems the system tries to find wifi and bluetooth. When I see my battery status, Android OS and Android System processes are draining more battery life than screen itself. Could it be a hardware failure even if wifi and bluetooth get back working sometimes?
I think I'll buy a lower cost android phone if I decide sending my Moto X warranty. It's complicated staying without a smartphone during 20~30 days.
I appreciate you all for the help and considerations.
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
crappy wifi
rafaelrossignoli said:
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
Click to expand...
Click to collapse
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
mutukrp said:
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
Click to expand...
Click to collapse
For first, thank you for reminding me about this thread. I bring bad news for you, unfortunately. It's 99% a hardware failure. In my case, it really was one. After 25 days, my phone was back from warranty with a new wifi/bluetooth hardware.
My phone was behaving the same way as yours. Sometimes the wifi was back working for a while, then my phone restarted and wifi was unavailable again. So, i recommend you send your phone warranty as soon as possible. Good luck!
rafaelrossignoli said:
So, i recommend you send your phone warranty as soon as possible. Good luck!
Click to expand...
Click to collapse
Well, I don't think I really have a choice here. I would be able to give my device for service only in about another 2 weeks so I have to live with 4G! I'll let you know how it goes. And thanks for the update...
wifi and bluetooth not turning On FIX
Hello everybody.i use a moto x (xt1052) 4.4.4 kitkat not rooted.
A week ago started having problems with wifi communication not turning on and a couple of days later bluetooth couldnt locate any connections
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
I am also wondering if anyone has any random reboots or its just my pocket..
Hope it helps for you too.
Cheers,Stelios
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
are.petrakis said:
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
Click to expand...
Click to collapse
Nope, that didn't help me at all. I think at least my issue is hardware related. Giving the phone for warranty repair on Thursday, let's see what happens.
Update
Been to the service center a week ago. Apparently the moment I explained my issue, they said it is an hardware issue and so the board needs a replacement. Got my phone back and it has been a week with no issues. Fingers crossed...

vibration mode

I have the T-Mobile LG G6 (h872) running stock oreo ROM. Last night the vibration mode stopped working suddenly. I was on the phone with T-Mobile support and only option is factory reset. Is there any way to test or activate vibration mode?
I was also told the lg g6 is no longer available for replacemrnt. Any help or suggestions would be appreciated
flyers00 said:
I have the T-Mobile LG G6 (h872) running stock oreo ROM. Last night the vibration mode stopped working suddenly. I was on the phone with T-Mobile support and only option is factory reset. Is there any way to test or activate vibration mode?
I was also told the lg g6 is no longer available for replacemrnt. Any help or suggestions would be appreciated
Click to expand...
Click to collapse
Mine did the same. A factory reset DOES NOT fix the issue. It's a physical hardware issue. It's been inactive for months, and, to my surprise, randomly turns back on from time to time without warning. Maybe once every two months for about a week vibration will work. It's a known issue with the phone. If it's a huge problem (as in, a smart watch or always-on screen won't fix it as an easy workaround) I recommend getting a G7. Supposedly the faulty part didn't carry over to the next version of the phone.
NeroTheTyrade said:
Mine did the same. A factory reset DOES NOT fix the issue. It's a physical hardware issue. It's been inactive for months, and, to my surprise, randomly turns back on from time to time without warning. Maybe once every two months for about a week vibration will work. It's a known issue with the phone. If it's a huge problem (as in, a smart watch or always-on screen won't fix it as an easy workaround) I recommend getting a G7. Supposedly the faulty part didn't carry over to the next version of the phone.
Click to expand...
Click to collapse
Thanks for confirming what I suspected. Tech support only wanted to do a factory reset and I refused. I will look into the G7.

New here and with a weird problem...

Hi all !
I'm a retired recording engineer from eastern Québec, Canada, enjoying retirement and keeping busy buildingand fixing audio equipment and restoring vintage British motorcycles.
I'm having a very strange problem with my Moto G5 (not Plus) that started out of the bue earlier this week. When the phone is locked, be it after locking it manually or after exceeding the preset time, and I receive a call, I do not get the phone logo on the screen anymore. If I want to take the call, the screen remains dark and I can't simply swipe it. I need to press the "start-stop" button, then a white box appears telling me who is calling and the padlock appears at the bottom of the screen. Then I have to trace the security pattern and the phone app appears, but on the in-out call screen instead of showing the button that would allow me to take the call. Instead I have to swipe down in order to get the box that allows me to take the call or reject it. I did countless Google searches and went through all the settings but I couldn't find any mention of that problem. The weird thing is that the phone was working perfectly one night, and then the following morning I had that problem. Can anyone help ?
Welcome to XDA
Was the phone updated overnight?
Clear the system cache if possible on this model.
Try in safe mode to help rule out 3rd party app interference.
It could possibly be a virus, rootkit or the hidden users settings have been corrupted.
The rom itself may have been corrupted, not necessarily anything nefarious... maybe just a high energy particle that flipped a flash memory cell read state. Atomic particles playing god, I hate that
Worse case solutions, factory reset, if that doesn't work reflash last known good firmware.
If all that fails it's likely a hardware failure but this is probably the least likely cause.
Hi !
Thanks for your reply. As far as I can tell there is no recent update. I tried everything you suggested except the factory reset because I dread reinstalling all the apps, but I guess I'll have to bite the bullet. Hoping it's not one of those pretentious atomic particles... ;-)
lanhet said:
Hi !
Thanks for your reply. As far as I can tell there is no recent update. I tried everything you suggested except the factory reset because I dread reinstalling all the apps, but I guess I'll have to bite the bullet. Hoping it's not one of those pretentious atomic particles... ;-)
Click to expand...
Click to collapse
Try disabling the lock screen etc. Go back to where it needed no password to use.
That's the first thing I tried, no luck... :-(
lanhet said:
That's the first thing I tried, no luck... :-(
Click to expand...
Click to collapse
I'm not familiar with that phone.
In general, try clearing the system cache.
I don't like messing with the phone app data but... first backup your contacts then start clearing data in the associated phone apps.
If a hidden user setting has been toggled it may be very hard to find/correct unless you know how. A factory reset would do so.
If that fails the firmware has become corrupted and needs to be reflashed.
If all that fails it's likely a hardware failure, either the mobo or possibly the C port PCB.
A C port pcb failure can do strange things on a Samsung like loss of internet/phone connection. I bring up the C port pcb because they get a lot of wear and tear... and they're a lot cheaper than a mobo.

Categories

Resources