Well I updated my Moto X XT1092 to 5.1 yesterday. Since then, the ear speaker has stopped working during both incoming calls and outgoing calls. I can hear everything clearly while on loud speaker, however i can't hear a thing while enabling the ear speaker. The person I am talking to can hear everything though. After the update, i cleaned the device using clean master. I haven't done a factory reset yet and haven't done anything in the recovery either, hoping there is an easier fix to it. Can anybody help me fix it?
I am having the exact same issue. But in my case the earpiece worked initially and suddenly stopped working from yesterday. I tried rebooting the phone as well as rebooting in safe mode. Both didnt help. I also tried to clear the cache and data for the phone and dialer app, which didnt help either? I am planning to do a factory reset. Will that have any impact? I was on 5.0 pure edition when i sideloaded the 5.1 soak LPE23.32-14.
I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.
rectifyy said:
I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.
Click to expand...
Click to collapse
The factory reset didnt help too. Still having the same issue after factory reset
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.
rectifyy said:
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.
Click to expand...
Click to collapse
This didnt help either, Still the issue persists even after following every steps on that tutorial. Let me know if you have any luck with that
UPDATE:Finally got it working after updating to the latest build 23.16.3 posted in the general section
Nothing has worked for me so far. Is your phone xt1905? Well mine is xt1902 and I had updated it through ota before the entire issue started, and the build is 23.16.1. So I guess I'm already on the latest build. Do you have any suggestion regarding what i should do?
Hi,
I am also facing the same problem. I just updated my phone to 5.1 and now my ear speaker is not working one thing i noticed is if i connect a headphone, i am able to hear the sound, but the internal ear speaker of the phone is not working
Have anyone found any solution for it ?
Ear Speaker stop working after 5.1 update
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks
Ravneet Lohchab said:
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks
Click to expand...
Click to collapse
Someone over in the Motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.
Resolution for earpiece not working after 5.1 upgrade on moto x 2nd gen
walrusmonarch said:
someone over in the motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.
Click to expand...
Click to collapse
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset
I haven't updated to 5.1 and hearing aid isn't enabled.. Only thing I can think of is the dictionary update wifi required notification being the last thing that was done before losing sound in the ear piece. To remove dictionary updates is there a specific app I can clear data from?
owaismomin said:
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset
Click to expand...
Click to collapse
You legend, this worked! I've been trying everything. How the hell did they get enabled during the 5.1 update?
I found it a bit weird that it was working after factory reset and then suddenly stopped.
found this thread because my earpiece stopped working today. stock android 5.1 att moto x 2014. tried a bunch of stuff (hearing aid, wipe cache, reboot,..) didnt work. What did work for me was as simple as it gets. in my settings i turned everything off except cell signal (wifi, blutooth, location, screen rotate...) tried a call it worked. Dont know why or how but it did. havent tried turning everything back on yet. a bit scared to. Hope this helps someone.
!!UPDATE!! I do not think that helped . went out again and turning everything off didnt work.... So i back tracked to what I did before turning everything off. that step got my speaker back again for now at least. What that step was is i called my voicemail and inserted headphones in and out a couple times. I am thinking that the dialer thinks there are headphones plugged in so no speaker. I also believe it has to do with the dialer software since all other sounds and apps come out loudspeaker. using internal speaker test app internal speaker does not work when it is out. If it goes out again i will try headphones in that app to see if that resets it.
on I side note i just realized all my homescreen apps and widgets are gone. they are still installed just not on homescreen
So did anyone reach an effective solution regarding this issue or determined the root cause? It just happened to me today and i have been trying everything i have read online but nothing worked. Any help would be greatly appreciated.
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Tried doing that as well, didn't work.
Did anyone else find any solution?
I have wiped cache, cleaned the headphone jack, did the hearing aid thing.
Nothing has worked.
affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Found the solution, it was water damage actually.
My mom forgot to tell me that water went in through the headphone jack.
And as water conducts electricity the phone thought headphones were plugged in. Cleaning it with a cloth and a toothpick and then shaking the phone a few times fixed it.
I think that's why cleaning your headphone jack fixed it as well affiatic, water went in probably.
My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Click to expand...
Click to collapse
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3
Moriarty82 said:
My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3
Click to expand...
Click to collapse
Have you ever tried to make or receive a call on your Moto X and you hear nothing on the other side, almost as if there isn’t even a connection made? Then when you try to call again, for some reason it works?
If you have experienced this, you also understand how frustrating it can be when you have to hang up and dial again, just to make a simple call. This problem plagued me for months of owning my 2014 Moto X, searching everywhere for a resolution to this hugely annoying problem. It wasn’t only me who was experiencing this issue either. A friend with the same phone was having the exact same problem as I, however it was impacting them even more, since it was used for their business. At this point, I figured that it wasn’t only the both of us experiencing the issue, but potentially many others owners as well. After much more searching, I came across a similar issue on a different phone, which listed some ideas to fix the issue. To my surprise, when I completed the process, the problem was fixed and has yet to return. Here is what I did…
Fix Inability to Hear Calls on Moto X
I had tried many different things to fix this issue, such as switching from Dalvik to Art, then back to Dalvik again. Rebooting the phone also didn’t seem to help much at all. Now for what fixed the error (scroll below for the steps).
First, I wanted to clear all cache, as that can sometimes fix simple issues. After I had entered the Recovery menu and cleared the cache, I noticed the problem had stayed away for a bit longer than a reboot, but eventually it came back again. Next, I put the phone into Safe Mode. Once the phone rebooted into Safe Mode, I shut down the device and plugged it in to my wall charger for two hours. To my surprise, after two hours when I turned my phone back on and tried making a call, I could hear the other side. The problem was gone and has yet to return, months later.
Anybody that has experienced this same issue, should try the steps below. It may just make your phone much less frustrating to operate.
Putting the Moto X into Recovery Mode to Delete Cache:
1. Power off your phone, by pressing down the power button until the power menu pops up and selecting*Power Off.
[http://salloiacono]
2. Wait a few seconds, then proceed to next step.
3. Hold down the*Volume Down*for a second, the while still holding down the*Volume Downbutton, also hold down the*Power Button*for about 3 seconds, then let go of*Power Button. If you did this correctly, you will see the*Boot Menu.
[http://salloiacono]4. Press the*Volume Down*button, until you have*Recovery*highlighted. Then pressVolume Up*to select*Recovery.
5. Your phone will appear to reboot and you should see this little guy.
[http://salloiacono]
Don’t worry, you didn’t break anything.
6. Now you must enter the*Recovery Menu.
– For Android 4.4.4: Hold down the*Volume Up*button for about 10-15 seconds and while holding that down, press the*Power Button.You should see a new menu pop up.
– For Android 5.0: Hold down the*Power Button*for a few seconds and while holding that down, press the*Volume Up*key. You should see a new menu pop up.
[http://salloiacono]
7. Press*Volume Down*until you have*Wipe Cache Partition*highlighted, then press thePower Button.*Your phone will now reboot. It is time for the next step.
Putting your Moto X into Safe Mode
1. Once your phone has fully rebooted, you are now ready to put your phone into*Safe Mode. Hold down the*Power Button*until thePower Menu*pops up. Now press and hold thePower Off*button.
[http://salloiacono]
2. After a few seconds, you should see a new window pop up warning about*Safe Mode. Press*OK. Your phone will now reboot intoSafe Mode.
[http://salloiacono]
3. Once your phone reboots into*Safe Mode,Power Off*your phone.
4. With your phone powered off, plug it into your wall charger for 2 hours.
5. After 2 hours, you may unplug your phone and turn it back on. Now you should be able to make and receive calls without the issues you were experiencing before!
Hope this works as well for you as it did for me!
Verstuurd vanaf mijn XT1092 met Tapatalk
Related
after i upgrade my pda2k to 1.22, sometimes i cant hear voice when i make a phone call, i have to reset it and it will be normal, anyone have same problems?
Me too
I came across the problem today too, I had to reset to be able to hear a voice on calls. Not sure what causes it. Might have to go back to my old ROM :roll:
i ran into this, but not just on speaker-phone mode. i was unable to hear anything when i canned 3 or so phone numbers. after a hard reset it worked great again. this has happend a few times since the rom upgrade.
outz said:
i ran into this, but not just on speaker-phone mode. i was unable to hear anything when i canned 3 or so phone numbers. after a hard reset it worked great again. this has happend a few times since the rom upgrade.
Click to expand...
Click to collapse
i think you need do the hard reset, just soft reset will be ok.
I am using xda IIs, with the same problem.. soft reset did the job, but happens once in 3 days...
I had something similar to this which was solved in an earlier thread. Not sure if it may be related.
For myself and some other users this happened after using the headset, it turns out that this is a known problem whereas the phone still thinks the headset is plugged in even after removing. Stuck the headset jack back in and moved it around a bit. Never had the problem again. Just a thought.
I have no speakerphone sound on my captivate. No 3g noise on boot, no speakerphone, no pandora, youtube, or ringtones... The phone will vibrate, and play music out of the headphone jack, or while in a call, but not in speakerphone.
This started while i was running Cog v5.5, but I did have sound initially in 5.5.
I am now running 8.1 and the same thing is happening.
I posted in that thread and 10+ pages later, didn't get a response.
I'm wondering if there is just a setting I missed, or if i need to do more of a factory reset when i install beta 9 tonight. by more of a factory reset, when i upgraded roms, my internal memory card still had all of its data on it from the previous installation.
Please help
Don't know if you saw my respose in the other thread.
I had this same issue recently. The fix for me was to take the back cover off and gently press the speaker back into the phone. Apparently it was just the slightest bit loose. Hopefully that is all that is wrong for you as well. I too did a system wipe an re-install for this issue, but the speaker being loose was the problem.
tried that, and same thing. If i cant figure it out soon, I may just restore it to stock, and trade it in with att
kwhee07 said:
tried that, and same thing. If i cant figure it out soon, I may just restore it to stock, and trade it in with att
Click to expand...
Click to collapse
My first one did this after about 2 weeks. I took it to AT&T and they swapped it out for a brand new one.
I hope thats not the case, but if I have to, it should be pretty easy to get back to stock config
speaker broken
my speaker is also not working properly. Works intermittently, requires lots of real hard pressing down on speaker face to get it to go, etc. it is not loose, so i think this could be something in the software of the phone....I am stock all the way, 2.1 and not updated. I am also beyond 90 days on my phone.....any ideas?
W
Wow, I had the exact same issue come up, and pressing on the speaker actually fixed it. Three cheers for percussive maintenance.
everything was working great until this morning. no sound from top speaker at all, cant hear when making or receiving a call, no music, zip, nada.
only thing i have done is unlock bootloader and root and that was done when i got the phone last friday. just weird how the sound just stopped over night.
i have powered off and on, wiped cache and dalvik cache.
has anyone seen this?
ryanwv24 said:
everything was working great until this morning. no sound from top speaker at all, cant hear when making or receiving a call, no music, zip, nada.
only thing i have done is unlock bootloader and root and that was done when i got the phone last friday. just weird how the sound just stopped over night.
i have powered off and on, wiped cache and dalvik cache.
has anyone seen this?
Click to expand...
Click to collapse
I haven't seen anyone mention this myself.. I'd say that since you just got the phone and haven't really done much to it you should have it replaced since that seems like a hardware issue.
Has the phone been dropped or anything?
Mistertac said:
I haven't seen anyone mention this myself.. I'd say that since you just got the phone and haven't really done much to it you should have it replaced since that seems like a hardware issue.
Has the phone been dropped or anything?
Click to expand...
Click to collapse
Phone is mint, not dropped at all. I baby the phone lol. On phone with AT&T now.
ryanwv24 said:
everything was working great until this morning. no sound from top speaker at all, cant hear when making or receiving a call, no music, zip, nada.
only thing i have done is unlock bootloader and root and that was done when i got the phone last friday. just weird how the sound just stopped over night.
i have powered off and on, wiped cache and dalvik cache.
has anyone seen this?
Click to expand...
Click to collapse
Yea just happened to me on my Att Nexus 6. No sound during calls at all. I took of the case and rebooted the phone and then called voicemail, now the phone is making sound so I think a reset fixed my problem.
Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
shashankkp12 said:
Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
Click to expand...
Click to collapse
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
TeddyBeers said:
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
Click to expand...
Click to collapse
Thanks for the suggestion, But by full factory reset do you mean the hard reset from the recovery menu or just the factory reset from settings menu -> factory reset..?
facing same issue please help
i am facign the same issue please help me out
Still no solution for the problem...I have made an habit to turn speaker phone on and off immediately after calling .
Try Macrodroid app to set an automatic task, to turn speaker off 1 or to seconds after receiving call.
I am also facing Same issue, can any one give suggestions
Somehow that happened to me when I just got the phone a few months ago. I think that was still on 8.0.
But tapping the speaker phone button 2 times everytime I have a call became nature for me and eventually after a few days, I no longer have that issue.
Are you still having that speaker phone issue now?
Yes...but while it was consistent on 8.0 it has become a random occurrence after 8.1 update
same issue
factory reset solution is not acceptable.
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.