[Q] Changing Microphone input on Android 7.1 - ONE Q&A, Help & Troubleshooting

Currently I have Lineage OS 14.1 flashed, which uses Android 7.1 as its basis.
In the past I've manually changed the microphone input on CM 12.1, by editing the "mixer_paths" file to use one of the other microphones, as my main one is broken.
Right now I can no longer use my main mic to make calls, and always have to call on loudspeaker, which is really annoying for me and everyone around me.
That's why I'm making a thread about this, as I really need to fix this as fast as possible.
So what I'm asking here is, if anyone has any idea which files I have to edit and which values I have to change in order my main mic isn't used in the call, but the other one.
Cheers

Elder Lyons said:
Currently I have Lineage OS 14.1 flashed, which uses Android 7.1 as its basis.
In the past I've manually changed the microphone input on CM 12.1, by editing the "mixer_paths" file to use one of the other microphones, as my main one is broken.
Right now I can no longer use my main mic to make calls, and always have to call on loudspeaker, which is really annoying for me and everyone around me.
That's why I'm making a thread about this, as I really need to fix this as fast as possible.
So what I'm asking here is, if anyone has any idea which files I have to edit and which values I have to change in order my main mic isn't used in the call, but the other one.
Cheers
Click to expand...
Click to collapse
You can no longer use that "mixer_paths" trick?

I'm really having trouble. I have already edited build.prop, mixer_paths, and nothing worked. I used Magisk with an OPO-specific module and it did not work either.
Enviado de meu ONEPLUS A3000 usando Tapatalk

Elder Lyons said:
Currently I have Lineage OS 14.1 flashed, which uses Android 7.1 as its basis.
In the past I've manually changed the microphone input on CM 12.1, by editing the "mixer_paths" file to use one of the other microphones, as my main one is broken.
Right now I can no longer use my main mic to make calls, and always have to call on loudspeaker, which is really annoying for me and everyone around me.
That's why I'm making a thread about this, as I really need to fix this as fast as possible.
So what I'm asking here is, if anyone has any idea which files I have to edit and which values I have to change in order my main mic isn't used in the call, but the other one.
Cheers
Click to expand...
Click to collapse
Try this
Regards

Elder Lyons said:
Currently I have Lineage OS 14.1 flashed, which uses Android 7.1 as its basis.
In the past I've manually changed the microphone input on CM 12.1, by editing the "mixer_paths" file to use one of the other microphones, as my main one is broken.
Right now I can no longer use my main mic to make calls, and always have to call on loudspeaker, which is really annoying for me and everyone around me.
That's why I'm making a thread about this, as I really need to fix this as fast as possible.
So what I'm asking here is, if anyone has any idea which files I have to edit and which values I have to change in order my main mic isn't used in the call, but the other one.
Cheers
Click to expand...
Click to collapse
hi
i have some problems with my front mic
what line should i change in mixers_path to get the back mic to be the main mic?
thanks

Related

CM-11 testing for sm-t325 (mondrianlte), no radio support

I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !
Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?
crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.

[Q] Speakerphone - Echo sound for others while talking

Just tested with the new 4.4 image and the problem remains from when i was on 4.2 image. Anytime I place a caller on speakerphone, they report they have a bad echo in their handset while they are talking. Tested with multiple people. Any help would be greatly appreciated. Thank you!
Can microphones be disabled one by one in mixer-paths.xml?
A lot of echoing still going on when placing people on speakerphone. Everyting stock, newest OTA.
I read somewhere that disabling bottom mic helps because it's nearest to the loudspeaker. Can any mic be disabled separately on mixer_paths.xml?
Would like to also keep my phone not rooted since at the moment I don't have time fiddle with my phone a lot. Would it be possible to probably create an app where you could determine that for example when Skype is on speakerphone it only uses top mic? Or when using sound recorder it uses all the microphones?
Any progress on this? Got the phone not too long ago, but every time I put someone on speaker they report hearing their own echo. This happens on stock 38r, as well as other kernels and roms.
i read somewhere that its because the mic is near the speaker so the sound comes out the loud speaker and goes into the mic hence why the person can hear them selves. my thought it is there any way of adding an option to have the other persons voice come out the ear piece speaker instead of the speaker at the bottom? could this solve the problem?
Guys, copy the following mixer_paths.xml file to replace with the one you have in /etc (requires root)
I uploaded it here:
http://www.filedropper.com/mixerpaths
I'm not exactly sure which part of its content solved the problem, I just took it from a custom ROM that did not have this issue (SlimKat) and put it in the rom I use (that DID have the echo issue).
Solved the problem for me, hopefully it will solve it for you too.
purpleman2k said:
Guys, copy the following mixer_paths.xml file to replace with the one you have in /etc (requires root)
I uploaded it here:
I'm not exactly sure which part of its content solved the problem, I just took it from a custom ROM that did not have this issue (SlimKat) and put it in the rom I use (that DID have the echo issue).
Solved the problem for me, hopefully it will solve it for you too.
Click to expand...
Click to collapse
Sorry, but the file doesn't exist. Can you upload one more time?
Anyone who can re-upload the file?
Verstuurd vanaf mijn A0001 met Tapatalk

Mic Not working!

I have a xt1033 conveted to gpe edition! On installing custom roms, my mic is not working in viber and hangouts( Calling featue) too! I can only hear the other persons voice! While the mic is working in normal calls! Where as in stock( gpe edition ) everything is working fine! Please people give me a suggestion- What should I do?
I have this issue as well, regular moto g (3g no micro sd). Running the latest CyanogenMod niggles. Hangouts does the same thing to me. Haven't tried viber yet, skype seems to work fine.
Having this same issue as well, it's so odd. Literally EVERY rom other than stock has this issue. A couple avenues I've explored:
Another thread suggested replacing the audio_policy.conf in /system/etc with an alternate one but this did not help. As a second test I have replaced the stock audio_policy.conf with the one from SlimKat on the stock rom and it didn't make it stop working, so I guess I have exhausted this potential solution.
Another theory I have read is that Hangouts may be attempting to use the noise-cancelling microphone instead of the correct one, which is resulting in the null outgoing audio during calls. I am not sure how to adjust this.
I'm going to have a look at comparing config files from the stock rom and a custom one but I don't have much hope and I'm sure there will be a ton of differences to sort through. I really hope this gets figured out because stock roms make me feel icky.
All the best, friends.
Well, after much tiresome digging, I've finally found the solution. I was searching for "hangouts" but the solution post was obscured by Hangouts not being mentioned and also appearing to only apply to Lollipop, but it works on every KK rom I've tried:
http://forum.xda-developers.com/moto-g/general/how-to-fix-voip-calls-android-5-0-t2983391
Enjoy.

Mi4, CM13 echo in calls

Hello,
I have a Mi4 with TWRP and CM13, latest nightly from today, but the problem also occured on the nightlies before.
During calls the other party complains about hearing himself. On the internet I found ideas like:
- disabling the "OK Google"-recognition on every screen (although this held true for Skype-video-calls)
- lowering in-call volume
I did not find any other ideas. Do you have an idea?
EDIT: I also tried two things:
1. entering the following things -> no changes
su
setprop persist.audio.fluence.mode false
setprop persist.audio.handset.mic analog
reboot
2. disabling the mic while calling -> success, the other party has no echo anymore
This of course is no useful solution, as normally a mic is needed for calling.
I'm facing the same problem. Did you find a solution?
nope
Same here.
Posted this in another forum. After trying a few things it appears that microphone is relaying sound from the speaker back to the caller. It's like the microphone is too sensitive so it picks up the callers voice from the speaker.
yes, it is definitely a problem with the mic. as soon as you deactivate it, the other party has no echo anymore.
EDIT: I wonder if this is the case, because in the native MIUI there was a noise-suppression and dual-mic option which may be good for avoiding this problem. I highly doubt CM will implement this specifically for this phone. Right now I am always calling with a headset which works fine.
EDIT: Headset isn't working anymore too. Callers say I am way too silent. Soundrecorder App confirms that mic sensitivity is too low.
I think the solution might be here, thought I am not able to understand completley what they are doing there: https://jira.cyanogenmod.org/browse/NIGHTLIES-2619
It should be solved after installing the next nightly:
https://www.cmxlog.com/13/cancro/
http://review.cyanogenmod.org/#/c/139932/
Could someone pls give a feedback after installing it? I switched from nightly to snapshot-channel and therefore am not able to check.
hsquare said:
It should be solved after installing the next nightly:
https://www.cmxlog.com/13/cancro/
http://review.cyanogenmod.org/#/c/139932/
Could someone pls give a feedback after installing it? I switched from nightly to snapshot-channel and therefore am not able to check.
Click to expand...
Click to collapse
Is the problem still existing with the new snapshot release?
I'd like to know that too! I switched to nightlies now and some people I talked with say it's still there, some don't.
hsquare said:
I'd like to know that too! I switched to nightlies now and some people I talked with say it's still there, some don't.
Click to expand...
Click to collapse
I heard from some guys using latest Snapshot that the echo is gone but when they make a hands free call, the speaker and mic is very quiet/ low. So probably the problem is not totally fixed right now.
I'm on Nightly 13/04 right now, no echo at all but the phone is turning of during call (after I tried to turn on the display). Is there another behaviour on the Nightly you are using?

[FIXED] OnePlus 7 Pro Microphone issue with speaker

Most of oneplus users are having this issue, once you open the speaker in calls or games or any other apps the mic would be sick and not working good, and it also have an echo for call records, i searched alot and finally find a solution works for me
First you have to be rooted
Download Build.prop editor
Open the app and search for
HTML:
persist.audio.fluence.speaker
Make it false and save.
Reboot your device and it will be fixed. :fingers-crossed:
I hope it works, please share it with others.
_______________________
This seems to help solving that long-bugging problem for me. Thank you. :good:
Thank you
"the mic will be sick"
What does that mean?
I want to do this, but I'm fairly sure that the I don't have issues with speaker phone on calls.
Sent from my OnePlus7Pro using XDA Labs
nabril15 said:
"the mic will be sick"
What does that mean?
I want to do this, but I'm fairly sure that the I don't have issues with speaker phone on calls.
Sent from my OnePlus7Pro using XDA Labs
Click to expand...
Click to collapse
I mean it's not stable and sometimes the voice cancellation ignores my voice as the people can't hear me.
Gonna give this a try because it's super annoying.
Yo,
I tried everything you said but nothing was working, so I rooted my phone, and installed lineage OS 18.1 following this instruction. The microphone issue that I had for so long was gone (low mic input on whatsapp, snapchat, even Loudspeaker calls), unfortunatly the GPS wasn't working for me on this ROM, so I installed this rom and now it's fine.
I am having issues sometimes with the popup camera not going in sometimes but having a mic that work is so good that I close my eyes on that !
I have been searching for a fix for a very long time, so I hope it will help you.
Cheers,
Alexandre
MrBlead said:
Yo,
I tried everything you said but nothing was working, so I rooted my phone, and installed lineage OS 18.1 following this instruction. The microphone issue that I had for so long was gone (low mic input on whatsapp, snapchat, even Loudspeaker calls), unfortunatly the GPS wasn't working for me on this ROM, so I installed this rom and now it's fine.
I am having issues sometimes with the popup camera not going in sometimes but having a mic that work is so good that I close my eyes on that !
I have been searching for a fix for a very long time, so I hope it will help you.
Cheers,
Alexandre
Click to expand...
Click to collapse
Have you installed gapps with the lineageOS and GPS didn't work ?
Kirolod said:
Have you installed gapps with the lineageOS and GPS didn't work ?
Click to expand...
Click to collapse
I installed Nikgapps wich was very recommended in the comments since Gapps only supports Android 10 for the moment.
I tried differents things to get gps working but nothing changed ..
is there a way to solve this problem without root?
tayler232 said:
is there a way to solve this problem without root?
Click to expand...
Click to collapse
Some say it's been fixed in Android 11, But i don't think so.
Kirolod said:
Some say it's been fixed in Android 11, But i don't think so.
Click to expand...
Click to collapse
same issue on android 11
OnePlus7 Pro latest build of Android 11 - same issue.

Categories

Resources