[Q] Kineto/WiFi calling issue on CM7 - Defy Q&A, Help & Troubleshooting

First I would like to thank Maniac for all his hard work getting the kineto wifi calling working with CM7 on the Defy.
It seems to be working fine except for one issue. The caller on the other end is getting a nasty echo of their own voice. I restored my phone back to the Moto Froyo 2.2 rom and it does not seem to have this problem. If anyone has any ideas how to fix this I am certainly willing to give it a try.
Thanks again.

This might be related to the second (noice cancellation) microphone. Does that also happen if you're using a headset (wired/BT)? In any case, about the only idea I have at the moment would be replacing the audio libraries to the ones in the stock t-mobile ROM. I've attached them; please copy libaudiopolicy.so to /system/lib, reboot and retry; if the problem is still there, please do the same with libaudio.so. Then give feedback about the outcome

Thanks for replying.
I copied the libaudiopolicy.so to /system/lib using es file explorer, but upon rebooting the phone it hangs at the moto logo screen.
Is there anything else I need to do?

Oh, that's bad. You normally don't need to do anything additionally. As I don't have time to investigate this at the moment, I suggest to reinstall the nightly you're using in order to get your phone into a working state again for now.
EDIT: But do you get the same kind of echo when calling with headset or speakerphone?
Sent from my Defy

Yes, the echo is still there with a wired or bluetooth headset or speakerphone mode. But oddly enough if I enable mute the echo goes away.
I was able to get my phone working again by restoring a backup.

Hi i can confirm that this is indeed a problem that happens consistently (tho the kineto app works perfectly with Voice and text messages).
When you copy the two proposed files to the file system using Root explorer, it causes the phone to hang upon reboot.
Anything i can do to aid in the fixing of this issue? i would love to have this very annoying echo gone.
Thanks in advance.

Did you set the permissions the same as the previous?

Hi, the permissions appeared to be the same according to root explorer.

Can anyone confirm that swapping in these libs has fixed the echo problem? I tried replacing libaudiopolicy.so first and got stuck at the Google/Moto bootup screen just as Mr. Cool did, and had to do a restore on my phone. I guess it would make sense to copy both files, but I'd at least like to hear that it worked for someone else first.

I also had trouble with callers complaining of a bad echo. I tried replacing both libaudio.so and libaudiopolicy.so, but replacing those files resulted in the phone getting stuck at the boot screen.

wifi calling echo
just installed the latest "CyanogenMod-7-20120628-unofficial-jordan." confirmed when talking to my wife that there is a huge echo on her end and not on my end.

capntang said:
I also had trouble with callers complaining of a bad echo. I tried replacing both libaudio.so and libaudiopolicy.so, but replacing those files resulted in the phone getting stuck at the boot screen.
Click to expand...
Click to collapse
I did this to clear up my stock ROM wifi-calling quality but others have mentioned also doing this to clear up quality issues on alternative ROMs with wifi-calling: go into your router setup and if default is "mixed mode" change to either straight G or N. May help.

scrannel said:
I did this to clear up my stock ROM wifi-calling quality but others have mentioned also doing this to clear up quality issues on alternative ROMs with wifi-calling: go into your router setup and if default is "mixed mode" change to either straight G or N. May help.
Click to expand...
Click to collapse
Thanks for the idea. I changed my router from "mixed mode" to G only, but the echo persists.

Related

Poor in-call audio quality

Info in my sig. I was on a previous version of CM (4.2.12.2, iirc) and had no problems. It did run sluggish, but was guessing it was due to my class 2 sd card and using swap/ext/fat32 on it.
I repartitioned my card to all fat32 and loaded 4.2.13 yesterday. It runs much faster, much more responsive than before.
Now, when on a call, it sounds like it's breaking up, like I have bad signal every once in a while. When it would do it, I checked and had 3G and 3-4 bars. I was at my house, where I've never had problems before. This happened both with just the my3g and on a BT headset. Initially I thought it was where I was in the house, but it happened no matter where I went.
I searched and found a thread titled "Background noise" talking about improved call quality. I can't post a link because I'm a no0b, but here's the info, with attached filename Audio-mic-gain-fix.zip:
scheng said:
Is there any way to reduce the background noise of the Magic on the voice call? Will it be improved by updating the latest radio?
Click to expand...
Click to collapse
sombionix said:
You can try this. It has improved my call quality a lot. Follow these instructions using terminal app.
*unzip the files using astro or file manager of your choice*
Open terminal emulator
Type - su (enter)
Type - mount -o remount,rw /dev/block/mtdblock0 /system
Type - mkdir /sdcard/mic
Type - cp /system/etc/* /sdcard/mic
Type - cp /sdcard/download/*.csv /system/etc/ (or whatever directory you unzipped to)
Type - reboot
Click to expand...
Click to collapse
sombionix said:
Are you rooted with a modified ROM? If so, many people have complained about poor call quality, distortion, etc. This file has fixed this problem in many cases. The *'s stand for 'files'. If you call out an * in a command it pulls all files in that directory. However, another example would be *.csv, which would only pull .csv files, or whatever file extension you put after the *. Sorry, hopefully that makes sense.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Since the file is named audio mic gain fix, it seems this is more for the mic gain, not the ear speaker.
Am I having the problem this is intended to fix?
Thx!
If you're having a problem with your ear piece (speaker), I don't think the mic-gain file will help with your situation. The mic-gain file was intended to improve call quality via the microphone. Some users were claiming that the people they were calling said they could hardly hear them or that there was distortion and background noise.
I don't believe there have been any reported issues with the ear piece using any Cyanogen ROMS, but I could be wrong. Sounds more like a hardware issue. One way to test is to downgrade to a previous ROM and see if you still have the issue. If so, more than likely, its a hardware problem.
Good luck!
That's kinda what I figured. I'll continue using it to see if I still have probs. If so, I'll try a different ROM.
thx for the infoz.
This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.
Weirdkid said:
This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.
Click to expand...
Click to collapse
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.
fwiw, I did a wipe, reformated the sdcard, and a fresh install of CM 4.2.13.
I have a feeling it was just poor reception at the time. I don't talk on the phone that often, but used it today for about 5 mins and it seemed fine. I was riding in a car and background noise was loud (my buddies arguing over steroids & McGwire, lol), but the guy on the other end had no probs hearing me.
Glad to hear you got it fixed.
Sorry, I guess that was out of context. That was @Weirdkid, stating that I didn't do an upgrade like he did. I haven't touched it since yesterday, I wanted to let roll to see how it plays out.
sombionix said:
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.
Click to expand...
Click to collapse
Not quite, I was already getting static every now and then even before root(I thought I could live with it). It was just a little glitch I guess and that pushed me to get an exchange. After the unroot and back to Donut, the glitch with all calls getting low quality was gone but still getting minor static noise every now and then(just like before). Sorry for the confusion.
Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.
cougar694u said:
Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.
Click to expand...
Click to collapse
Yeah, I stopped using Cyan's ROM when the 4.2.10 release came out. Great ROM, just seemed to have increasing issues after 4.2.9. You should try the Super D rom. Fastest and most stable ROM I've run, hands down.
http://forum.xda-developers.com/showthread.php?t=613809
Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?
cougar694u said:
Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?
Click to expand...
Click to collapse
Not a problem. Also, if you have a mt3g, you don't need to upgrade your SPL to run the Super D rom. Aside from that, just make sure you have the correct radio, then do a full wipe and flash the ROM.
In regards to the 10mb ram hack, it definitely increases system speed and performance. So that would be your 'pro'. However, the ram hack is created by pulling 10mb of ram that would normally be used for graphical processes, and instead applies it to your operating system. The con would be a decrease in 3d game performance. So, if you play a lot of 3d games, then I wouldn't recommend the 10mb ram hack. If you don't, then use it. Currently, the only Super D rom you can download that doesn't have the ram hack is the 1.6.6 beta, which as of right now is fairly stable. However, If you are considering switching to this rom, just wait a couple days, the developer has announced that he is releasing the 1.7 stable version this week. I'm assuming he will have two separate downloads. One with the ram hack, and one without.
Btw, I didn't see your phone setup before my last post. You DO have the correct radio to run the Super D rom. So, all you have to do is a full wipe and flash the rom.
Nice! I forgot I was reading the page in the Dream/G1 section...I got this one how I like it, so I'll roll with it a few days and keep an eye out for Super D 1.7.

Bell Atrix , lost wifi, bluetooth and rebooting lots

Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
A friend of mine has the same problem, Im pretty sure thats a hardware issue already. !
running gb 2.3.6 #4 - still no wifi/bluetooth
Having the same issues. Does anyone know if wifi and BT share an antennae?
try flashing a differnt radio? for your phone specs
look in ihop thread or fruit cake thread for your radios
r0nz3y said:
Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
Click to expand...
Click to collapse
schufly73 said:
Having the same issues. Does anyone know if wifi and BT share an antennae?
Click to expand...
Click to collapse
I'm pretty sure this is a hardware issue... I have been having this problem myself, and have tried flashing many of ROM and Radio's since it has reared it's ugly head - all to no avail. The WiFi an Bluetooth do share the same Broadcom chip... maybe there's enough of us experiencing the problem that we can collaboratively order a dozen of these things (they only seem to sell in bulk).
Had the same issue, ATT had to replace the phone.
Any more news on this issue?
Same thing happened to my Atrix last week (Bell, 2.3.6, locked bootloader, unrooted).
Same here
Same problem on my original Atrix, which was replaced under warranty by AT&T six months ago. Recently my replacement Atrix has been having the same problem. Wifi won't enable and frequent reboots.
Although the phone should still be under the 1-year warranty, AT&T refuses to honor it because the screen is cracked (so much for Gorilla glass).
After getting two phones with the same problem, and hearing about countless others having the same problem, and getting screwed out of the warranty, this is definitely my last Motorola phone.
EDIT:
The "fix" that was originally posted here doesn't actually work. I'm almost certain that this is a hardware problem. As of now there is no software fix, if one even exists.
Check this thread for more info:
https://forums.motorola.com/posts/0c2f1387d6
I recommend that you post to acknowledge you have the same problem.
i tried the script and it tells me "oops... did NOT find wpa_supplicant.conf! any help?
cafe. said:
I found a permanent solution to the problem. It was probably more obvious than I originally thought it would be. This is probably what will fix it if you recently ran some sort of 3G tweak as it probably damaged/corrupted /data/misc/wifi/wpa_supplicant.conf. Before I get started with what what problems my phone was having:
-'Wifi Error' message when enabled
-Random reboots when trying to enable wifi
-Bluetooth worked fine (and if you are having issues with bluetooth it may be due to a similar bluetooth related file having problems)
-Impossible to fix by flashing new roms, wiping/factory reset, and virtually every other possible thing I tried
So, just before giving up, I found something called 3Gturbocharger--which can be downloaded from here: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 REMEMBER: IT'S 3GTURBOCHARGER, NOT ANY OF THE OTHER SIMILARLY NAMED FILES.
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
I'm assuming that in your case the bluetooth equivalent of "wpa_supplicant.conf" was corrupted. Possibly /data/misc/bluetooth/dynamic_auto_pairing.conf or /data/misc/bluetooth/incoming_connection.conf. Worth a shot trying the method I described on those files as well. Try it out, you've got nothing to lose.
Click to expand...
Click to collapse
im getting that to
My Atrix wifi stopped working in the past, but started working again. It currently stopped working once more, giving me an Error if I turn it on. The Bluetooth has never had issues and still works, I am a month past warranty but with unlocked BL it doesn't matter anyway. This seems to be a slight issue with these phones unfortunately.
I could live with the phone without wifi, but the constant reboots are unavoidable. I notice that when I originally boot the phone, if I use it and keep the screen on it works, but as soon as I turn the screen off, it reboots. Odd to me.
Ya I have the Bell Atrix myself and I'm still on Froyo because of complaints of GB. (especially battery life) Maybe I'll do ICS, but I'll wait for some reviews since its not that easy to go backwards as say my OG SGS...
Sent from my MB860 using xda premium
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
Click to expand...
Click to collapse
Anyone try doing this manually? I can't locate the file.
wpa_supplicant file
hi, the file is in etc/wifi and the bluetooth file is in etc/bluetooth/ i renamed the .conf files but this don't solved the problem.

Background noise through handset earpiece

I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Sent from my XT1575 using Tapatalk
Same issue here ! immediately after MM OTA update on my XT1575 (stock vanilla) people start complaining they cannot hear me well !
After sorting most of MM issues this is a major pain in the a**
Let Moto know about this as it makes the phone crippled.
How come there aren't any more complaints about this serious issue !
This is 100% MM related - People complain they can barely hear me on the other end of the line - I sound muffled, stuttered and basically bad to the point they cannot continue the conversation and demand I call them from a land line !
Forget all MM bugs, problems, etc (need I mention the Equalizer went AWOL) now this Smartphone which I highly praised and loved became a ...smart something - with no phone feature.
Help me let Moto support be aware of this issue.
Thanks
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
alon3232 said:
Got the following advise from Motorola support on chat - it seems to help - please tell me if it work for you:
please go to settings > apps > all > Audio Effects app - Tap Force Stop - Clear Cache and Clear Data.
Also under settings > apps > all > go to Phone app - Tap Force Stop - Clear Cache and Clear Data.
Now please turn off the phone and when you turn it back on try making a call.
Click to expand...
Click to collapse
Did all that on a call to Motorola after the first replacement phone failed to address my issue. No surprise, it made no difference.
That was followed by a factory reset and a test prior to connecting to my Google account and downloading any apps. Also, made no difference.
Now I'm waiting for my second replacement.
Sent from my XT1575 using Tapatalk
I have a thread on the Motorola forums for this issue.
My second replacement arrived yesterday. It solved the background noise issue! Unfortunately it came with loose buttons which actually rattled when shook or when the phone vibrated. Back to Amazon it goes.
Unfortunately, now Amazon wants to pull the plug on the purchase and take it all back. I'm not ready to give up though. Besides really liking the phone, I've also invested in a screen protector and car mount. I'll have to talk to Amazon today and see what we can do.
Sent from my XT1575 using Tapatalk
It's all boxed up and ready for UPS. I'm really unhappy that I could not get a good MXPE. As I consider other options, it's tough, especially at the $350 price point.
I'm actually giving the ZTE Axon Pro some thought, but undecided so far. And if the was a sale on the Nexus 6P that brought it down $100, it would be a contender. I'll pay a few more bucks for a Nexus. Given the right price, I may even give the MXPE anther shot, after they work through this stock of bad phones.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Don't get the axon. If you can't get the. 6p I'd go with Nexus 6 some places U can get it under 3 I think
Sent from my XT1575 using Tapatalk
Solved
Hi guys ive got the solution to this problem, my mic used to not work at all on handset calls and wud work on speakerphone. After diagnosing for 24 hrs I was able to understand the problem, all you need to do is replace top mics with bottom mics in music_path.html file If someone is not able to do it lemme know on twitter ill email u my edited file, just replace yours with mine. N nw the mic works like a charm. I am not a regular xda user, so won't be able to check back frequently, my twitter id is @smartphoniac
Have seen ppl replacing motherboards and phones in service center, also some use it on Bluetooth or handsfree, trust me its nt needed just do what i wrote above and issue is solved, if u r a noobie tweet me ill email u my file so that u will have to do jst the copy pasting and this painful issue will be gone forever.
Edit: This will also solve the problem if caller gets his own voice as echo. After this editing even that issue will be solved
Hi guys,
I've just bought a Moto X Style and I'm having the same problem as the original poster - constant background noise (kinda buzzing/hissing) during phone calls, coming through the upper speaker:
jswclw said:
I am hearing a low level constant static noise with all audio through the handset earpiece. This happens on all calls, and only on the handset. Switching the call audio to a wired headset, Bluetooth headset, or the speaker phone makes the noise go away.
I have experienced this on my first MXPE, and now on its replacement. One the second go around, I did learn something more.
On the second phone I tried a call before I setup anything and it was close to fine. I say close because it was not without background noise, it was just very slight. Acceptable.
Then I finished the setup. I tried another call, and still OK. Then came the upgrade to Marshmallow. Now under Marshmallow, the noise is right back to where it was with the original phone, also on Marshmallow.
Bottom line, it is a software problem, not a hardware problem. And the software problem is only present in Marshmallow.
Click to expand...
Click to collapse
So far I've tried booting into safe mode, wipe data/factory reset, different carrier/SIM card - no difference.
I'm running Android 6.0.1 and I upgraded right after I bought the phone, so cannot tell if the problem existed on Android 5.
However - and this is my question - since you claim that it's a software thing and Marshmallow-related, is there anyone who tried flashing a Nougat ROM and has it helped? I don't know if I should try and get a replacement phone (especially that some people had the same issue on 2-3 consecutive phones) or just wait for the Nougat update, assuming that it helps.
Thanks for advice!
Hi, it's me again - just wanted to tell you that I've flashed the 7.1.1. AICP ROM and the background noise is still there while calling Is it really a software issue? So many people say it appeared after MM upgrade and there were no problems on Lollipop, but maybe my speaker/mic is simply broken? Is there any ROM you can flash to get rid of this issue? All help is really appreciated! :good:

Microphone Problem after installing cm-13 unofficial.

Hi, i'm encountering a problem with the microphone of my one plus 2 that occured right after installing this custom ROM :
http://forum.xda-developers.com/oneplus-2/development/6-0-x-cyanogenmod-13-oneplus-2-t3292436
What happens is that the mic doesn't work when making a normal call, but works just fine with audio notes/skype/whatsapp etc.
I'm thinking about 3g/4g problems since the mic works with wi-fi services as i see. Does anyone have the same problem? It's preatty annoying...
FUN FACT: my girlfriend called me 4 times today and couldn't answer because of this... needless to say she got angry at me :crying: sooo it's urgent :silly:
On OxygenOS I had Cortana and when I was using Google now microphone and others apps which requires microphone I didn't work but for calls it worked for me and I don't know if there is Cortana is CyanogenMod 13 but if you disable/uninstall it I think i'll work (for me it worked)
scratur said:
Hi, i'm encountering a problem with the microphone of my one plus 2 that occured right after installing this custom ROM :
http://forum.xda-developers.com/oneplus-2/development/6-0-x-cyanogenmod-13-oneplus-2-t3292436
What happens is that the mic doesn't work when making a normal call, but works just fine with audio notes/skype/whatsapp etc.
I'm thinking about 3g/4g problems since the mic works with wi-fi services as i see. Does anyone have the same problem? It's preatty annoying...
FUN FACT: my girlfriend called me 4 times today and couldn't answer because of this... needless to say she got angry at me :crying: sooo it's urgent :silly:
Click to expand...
Click to collapse
Enable root, go to File Manager, /system/build.prop
change true to false in "persist.audio.fluence.voicecall"
credits to the person who shared,.
If it doesn't work, revert to Oxygen, clean flash again. Take backup though!
krishna442 said:
Enable root, go to File Manager, /system/build.prop
change true to false in "persist.audio.fluence.voicecall"
credits to the person who shared,.
If it doesn't work, revert to Oxygen, clean flash again. Take backup though!
Click to expand...
Click to collapse
i'm having same problem. So i edited TO ro.qc.sdk.audio.fluencetype=none, FROM ro.qc.sdk.audio.fluencetype=fluence
Now i'm having very low voice of opposite party during the call.
Any fix to this?
Thanks

microphone acting up

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.

Categories

Resources