Related
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
I have you seen s you. Have you found a solution yet? When I use a bluetooth headset it works Fine
You need to update your radio
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I was having this issue as well, and that worked perfectly! Thanks man!
*system error* said:
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I tried that and that app and messed with different settings and it didn't work. I'm gonna try updating the radio and see what that does.
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
That worked actually. Thanks!
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
Huge thanks for this one. I had been searching google for a solution to this one for a week or so now. I will have to say, the most annoying thing I've had to deal with in quite some time. I should have just come to XDA first like an adult.
T-mobile s4
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Try the T-Mobile S4 Forum
ptsite said:
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Click to expand...
Click to collapse
Sorry, but I don't know if this applies to the Samsung S4. I would try posting over in the T-Mobile Galaxy S4 forum.
This is very frustrating.
I use my phone for calls between 3-5 hours a day. I've been having this issue where I'll be on a call and after some time (ranges between 2-10 minutes) I can continue to hear people but they can't hear me. I use the Samsung headphones with a built in mic to talk. I'll notice that they can't hear me, I'll unplug the headphones and they still can't hear me. I hit speaker phone and still can't be heard. I end up hanging up and calling back. This happens about 30% of the calls I'm on. I also bought other Samsung headphones and the problem persists. It's also not always with my headset. I've had this muting issue happen while talking directly on the phone.
Here is the kicker. I'm on my 3rd s6 edge+ and I've had the problem with all 3!! My first phone the microphone by the speaker stopped working. My second one started having the same issue with the mic. But all three had the same exacting muting issue.
Anyone else in the same boat? Any suggestions on fixing this?
Thanks
mikeysweet said:
This is very frustrating.
I use my phone for calls between 3-5 hours a day. I've been having this issue where I'll be on a call and after some time (ranges between 2-10 minutes) I can continue to hear people but they can't hear me. I use the Samsung headphones with a built in mic to talk. I'll notice that they can't hear me, I'll unplug the headphones and they still can't hear me. I hit speaker phone and still can't be heard. I end up hanging up and calling back. This happens about 30% of the calls I'm on. I also bought other Samsung headphones and the problem persists. It's also not always with my headset. I've had this muting issue happen while talking directly on the phone.
Here is the kicker. I'm on my 3rd s6 edge+ and I've had the problem with all 3!! My first phone the microphone by the speaker stopped working. My second one started having the same issue with the mic. But all three had the same exacting muting issue.
Anyone else in the same boat? Any suggestions on fixing this?
Thanks
Click to expand...
Click to collapse
Doh. I dont know which firmware/rom/kernel you're running but maybe you should wipe cache/dalvik or clean re-flash.. If already rooted, give a try a custom kernel. Hope you solve it. Thanks.
I have the exact same issue, except my call quality is poor and calls drop a lot as well. Im on my 3rd phone as well. All the issues have followed me on the phone. T mobile told me that I would have to wait for the marshmallow update since its a known issue with the phone and it should correct it. I told them it wasnt a good answer so they are sending me a new sim card to try out and see if that helps. Personally I hope it doesnt so I can get a new device
Konsstantine34 said:
Doh. I dont know which firmware/rom/kernel you're running but maybe you should wipe cache/dalvik or clean re-flash.. If already rooted, give a try a custom kernel. Hope you solve it. Thanks.
Click to expand...
Click to collapse
Oops!
I'm running completely stock, no root/rom/kernel changes at all:
Build# LMY47X.G928AUCU2AOJ1
Android: 5.1.1
Kernel Version: 3.10.61-5921265
bb4ninja said:
I have the exact same issue, except my call quality is poor and calls drop a lot as well. Im on my 3rd phone as well. All the issues have followed me on the phone. T mobile told me that I would have to wait for the marshmallow update since its a known issue with the phone and it should correct it. I told them it wasnt a good answer so they are sending me a new sim card to try out and see if that helps. Personally I hope it doesnt so I can get a new device
Click to expand...
Click to collapse
Ugh. It's going to take forever for Marshmallow to come out. First Samsung needs to rip it apart, then AT&T before it gets to me.
Let me know how the SIM change works for you. That's one thing I've yet to try.
mikeysweet said:
Oops!
I'm running completely stock, no root/rom/kernel changes at all:
Build# LMY47X.G928AUCU2AOJ1
Android: 5.1.1
Kernel Version: 3.10.61-5921265
Click to expand...
Click to collapse
Umm. I see thats AT&T, isnt it? If so, you have got locked bootloader etc, I dont have proper info about it sorry. I prefer you to try something like wipe cache/dalvik etc but it may bricks your phone. So you better ask that in AT&T Forum Good luck.
Edit: I saw your post after posted mine lol. I've simfree g928C btw.
I recently updated my xt575 with the September security patch. Since then my microphone doesn't work only when making a phone call on speakerphone. Normal phone calls, audio and video recording, and voice commands all work just fine. I have tried booting into safe mode with no success, and then did a full factory reset and held off on downloading anything before trying again, still with no success. Is anyone else having this issue? Does anyone know of a fix or workaround for this before I try contacting Motorola? Thanks.
P.s. I am on stock ROM on Att network. I use Android pay a lot so would like to avoid rooting.
SirMiks said:
I recently updated my xt575 with the September security patch. Since then my microphone doesn't work only when making a phone call on speakerphone. Normal phone calls, audio and video recording, and voice commands all work just fine. I have tried booting into safe mode with no success, and then did a full factory reset and held off on downloading anything before trying again, still with no success. Is anyone else having this issue? Does anyone know of a fix or workaround for this before I try contacting Motorola? Thanks.
P.s. I am on stock ROM on Att network. I use Android pay a lot so would like to avoid rooting.
Click to expand...
Click to collapse
Same man. It's weird too. It will fix itself after a couple days - or at least mine did
Sent from my iPhone using Tapatalk Pro
Odd... I am on AT&T, for the moment at least, and use my speakerphone all the time, never had an issue before or after the update.
Try clearing your cache partition maybe?
Same problem
Hello. I'm trying to solve my Moto's mic for over a week now.
I was trying many ROMs, but ended up using TruePureXMM ROM along with franken kernel.
It was all working fine, except some overall phone lag and constantly trying out other kernel auditor settings...
...untill about 2 weeks ago. Phone's microUSB port got damaged, and I had to return my phone to repair service.
After I received it back, I wanted to try out some Nougat ROMs, and tried couple of them, but found out that the mic isn't working properly there.
Decided to return back to stock, using this forums tutorials, done it without any single errors or problems in the process, I did many devices roms changes before.
It didn't help at all. The receiver don't hear me at all, the only sound they can hear is when I blow into the mic's direction.
*Note that when I change to speaker mode, the receiver hear me with some breaks in between, but it's the only way to call from now on...
I'm confused now, completely no idea if it is really the OS problem, or if it's just something with the microphone itself.
Looking forward for any tips, thanks for help.
SR3TLAW said:
Same man. It's weird too. It will fix itself after a couple days - or at least mine did
Click to expand...
Click to collapse
I hope so. It's been a few weeks already... If it doesn't fix itself then hopefully the nougat update will help.
Sent from my Moto X Pure using XDA Labs
acejavelin said:
Odd... I am on AT&T, for the moment at least, and use my speakerphone all the time, never had an issue before or after the update.
Try clearing your cache partition maybe?
Click to expand...
Click to collapse
I have tried that too. Nothing send to help and I've been searching online for a while for a solution with no results. I don't think being Att has any relevance but figured I'd share that anyways just in case.
Sent from my Moto X Pure using XDA Labs
Also on att with September security update and speaker phone works fine.
After updating to Build NMK24B I've noticed I cant hear people during calls via the earpiece headphones, Bluetooth or speaker phone and everyone I call says I sound like static. I also get an issue where my screen gets a ghost touch in a area on my phone where j would be on a keyboard that taps crazy amount of times until i shut off the screen then it goes away for a few hours. Anyone else having these issues? also wondering if this would be something covered by warranty cause I sadly didn't pay for sprints insurance plan.
glasscitysd said:
After updating to Build NMK24B I've noticed I cant hear people during calls via the earpiece headphones, Bluetooth or speaker phone and everyone I call says I sound like static. I also get an issue where my screen gets a ghost touch in a area on my phone where j would be on a keyboard that taps crazy amount of times until i shut off the screen then it goes away for a few hours. Anyone else having these issues? also wondering if this would be something covered by warranty cause I sadly didn't pay for sprints insurance plan.
Click to expand...
Click to collapse
Build issue.
Go back to the previous build or go to 8.0 Beta 3.
This is a known issue. I lost both hearing and speaking on calls in that build.
tech_head said:
Build issue.
Go back to the previous build or go to 8.0 Beta 3.
This is a known issue. I lost both hearing and speaking on calls in that build.
Click to expand...
Click to collapse
thanks ill go back to oreo
glasscitysd said:
thanks ill go back to oreo
Click to expand...
Click to collapse
What do you mean back to Oreo?
geoff5093 said:
What do you mean back to Oreo?
Click to expand...
Click to collapse
back to the oreo beta I went back to official just to see if it was running any better and didn't have the ghost touch issue
just updated back to oreo and got the beta for 8.1 nice
March security update is out which also includes "digital wellbeing support"
Downloading now, 93Mb.
Update went fine.
New wellness feature looks good, could be useful for some, though it does list all apps even ones you are not "really" using like Nova launcher .... but this will probably reduce in stats prominence as I use phone properly during day.
More importantly. Does it fix the Bluetooth issues that exists in the Jan and Feb updates
mobileman88 said:
More importantly. Does it fix the Bluetooth issues that exists in the Jan and Feb updates
Click to expand...
Click to collapse
I presume it doesn't.
Titokhan said:
I presume it doesn't.
Click to expand...
Click to collapse
Though I wonder if our bug is related to the Pixel "Bluetooth reliability" update (I don't have this issue so not checked)
Listed in update bulletin
https://source.android.com/security/bulletin/pixel/2019-03-01
And here is the security update bulletin, if anyone is interested
https://source.android.com/security/bulletin/2019-03-01.html
Titokhan said:
I presume it doesn't.
Click to expand...
Click to collapse
Not much point in this update then. I had to roll back to December for my Bluetooth even be remotely usable for my car and speakers
The thing that's strange is all these Bluetooth issues ...I don't have any of em. My PH1 works normally with my car, portable Bluetooth speaker and 2 different sets of Bluetooth headphones. Many of the issues others complain of I can't replicate or simply don't have.
autosurgeon said:
The thing that's strange is all these Bluetooth issues ...I don't have any of em. My PH1 works normally with my car, portable Bluetooth speaker and 2 different sets of Bluetooth headphones. Many of the issues others complain of I can't replicate or simply don't have.
Click to expand...
Click to collapse
I think most of the people who are having issues have a wearable device, like a smart watch, that is giving the most issues.
OTA and Fastboot zip images from Essential
goofball2k said:
OTA and Fastboot zip images from Essential
Click to expand...
Click to collapse
How about LED notification light? look like still not working or not fixed yet
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
Works for me. Do you have it enabled?
autosurgeon said:
The thing that's strange is all these Bluetooth issues ...I don't have any of em.
Click to expand...
Click to collapse
Same here. Stock, rooted with Magisk, no TWRP. The phone was on Jan update when I bought it, went through both Feb and March updates, no issues. As pointed out, the problem might be more related to wearables, and I don't use them (just a headset and a car speakerphone)...
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
This one seems to be hit and miss for me... For example, it works for SMS, but not for missed calls.
Does this update have any sim relocking tricks? Thanks.
kt-Froggy said:
Same here. Stock, rooted with Magisk, no TWRP. The phone was on Jan update when I bought it, went through both Feb and March updates, no issues. As pointed out, the problem might be more related to wearables, and I don't use them (just a headset and a car speakerphone)...
This one seems to be hit and miss for me... For example, it works for SMS, but not for missed calls.
Click to expand...
Click to collapse
I'm also in Stock w Magisk 18.1 anderen w/o twrp since february. How exactly did you update? AS described here?
https://topjohnwu.github.io/Magisk/tutorials.html
no SIM relocking issue for me. mine stills says Sprint on bootscreen but i'm able to get T-Mobile signal
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
Mine has worked fine all along. In fact I don't have and never had either the Bluetooth issues or the wifi issues. So either the hardware is that different from device to device or something else is going on.
autosurgeon said:
Mine has worked fine all along. In fact I don't have and never had either the Bluetooth issues or the wifi issues. So either the hardware is that different from device to device or something else is going on.
Click to expand...
Click to collapse
Just to double check, you're on Pie, not Oreo right?
If so, that's weird, 'cause on mine, it's ok on Oreo but latest Pie
tqwzUX6fn39GZMEzSnDF said:
I'm also in Stock w Magisk 18.1 anderen w/o twrp since february. How exactly did you update? AS described here?
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
No, my update process is based on the steps from this thread: https://forum.xda-developers.com/es...de-step-step-instructions-to-install-t3877259
In short: adb sideload OTA zip, extract new boot.img from the update, patch with Magisk, fastboot flash patched boot. I haven't tried the method you linked. Maybe another time...
chanh2018 said:
Just to double check, you're on Pie, not Oreo right?
If so, that's weird, 'cause on mine, it's ok on Oreo but latest Pie
Click to expand...
Click to collapse
I have been on 9.0 since the first Beta. I am currently on the latest March security update of 9.0.0
autosurgeon said:
I have been on 9.0 since the first Beta. I am currently on the latest March security update of 9.0.0
Click to expand...
Click to collapse
Hummm.....that's really bug me. I just re-flashed the stock ROM and still no LED notification. Have no clue how to fix it.
but thanks for the response.