03-25-2016 04:48 AM
I sent the phone back already, so I can't absolutely confirm, but I believe it is in settings. There were instructions when I went through the trouble shooting guide on the Motorola website. Make sure to back up any data before doing the reset. Also they say you should not let the phone automatically reload your previous settings and apps when it starts back up. There are good instructions on the website.
03-25-2016 04:52 AM
Here's the link from which you can start the trouble shooting : https://motorola-global-portal.custhelp.com/app/mcp/landing_troubleshooter/g_id/5059
I selected the call icon and went from there.
03-31-2016 08:39 AM
PHONE AUDIO: I had same exact problem with phone audio. It worked perfectly until I upgraded to Marshmallow. 90% of the time you cannot hear the other person, they cannot hear you, you cannot hear it dial, but you can see it was answered, then once in a while it will work. You think you've resolved it, but it quickly stops working again. Saw another post about speakers being inverted by the Marshmallow upgrade, so I plugged in ear buds and voila, sound works. Cannot exactly spend my life with earbuds, so would appreciate Android/Motorola fixing this bug. Have not found any other Marsmallow issues, yet.
04-06-2016 02:37 PM
Got my phone back after about 2 weeks. It seems to be working OK now. From their e-mail to me: We had to make extensive changes, but it's now in good working condition. I'll check back in if things go downhill quickly......
04-12-2016 07:10 PM
So, got the phone back last Wednesday after "extensive" fixes. Same issues when I tried to answer a phone call this PM. No sound without headset. Worked again after a reset. Any bets on how long before it stops working? 10 days before warranty ends. Planned obsolescence?
05-16-2016 11:06 AM
I've also been having the same sorts of problems that started after the "upgrade" to Marshmallow/6.0. I'd estimate the phone works about 25% of the time on Bluetooth.
05-16-2016 11:53 AM
I should mention a few things:
05-16-2016 02:12 PM
I had this problem, and Motorola's only suggestion was a factory reset. This does appear to work for a while until the problem re-occurs. I found a workaround on another forum. The phone application has a setting to control Hearing Aid accessibility. Something appears to inadvertently turn this setting on after the Marshmallow upgrade, and when it does, the phone stops working, and the symptoms described occur - cannot hear a connection you make or receive. Turn this setting off and the phone starts working again.
Not sure where the actual bug resides, but this workaround will at least temporarily fix the problem. I'm expecting it re-occur again, but changing a setting is a lot easier than a factory reset and reload.