yashsingh1/xdaforums huggingface dataset:
[Magisk] firemaker911:
Lenovo Vibe K5 Plus (A6020a46)

[MENTION=5999829]Nomelas[/MENTION] & To All Members

Hi

Im Actually Use The Latest "Vibe Os" On My Device,

Latest Magisk-Package With DOLBY Atmos Version 2.1.0

(It Works Definitely With No Erros/Bootloops Etc.),

Vegito 7.2 Kernel And The Latest TWRP-RECOVERY.

Apart The Waiting For The Final Working Release

Of The Xposed-Framework & The Xposed-Installer

I Have The Issue With The Low-Noised

Handsfree-Loudspeaker Of My Device.

No Dev Answer Me For This Problem,

To Fix etc....

My Question:

What Line In The Build.prop I

Must Change & With Wich Parameters

To Increase The Best Power

On My Handsfree-Loudspeaker?

Next Week I Go To Holidays & Want To Use

This Device As My Daily Driver.

Hope I Get A Working Solution From The XDA-Members.

Many Thanks ? ? ?
[Magisk] firemaker911:
Lenovo Vibe K5 Plus (A6020a46)

[MENTION=5999829]Nomelas[/MENTION]

BTW, I Tried Your "Android Mic Fix" On My Device.

Downloaded Latest File From Your Description-Side,

Install It VIA Magisk But Nothing Changes.

Still The Same Issue Present....
[Magisk] Nomelas:
What device?

As I've stated though, this won't work for all devices and all situations/mic issues unfortunately.
[Magisk] KokkoM:
Works fine on Oukitel U16 Max :)
[Magisk] firemaker911:
On My Message Thread: Lenovo Vibe K5 Plus (A6020a46)
[Magisk] g40q90:
Hello everybody, I'm using a LG G5 H840 with encryption and there is a issue with magisk template v4 installing modules in cache partition. Here there is the solution https://github.com/topjohnwu/magisk-module-template/issues/25

[MENTION=5999829]Nomelas[/MENTION], could you please add the commit to "android mic fix"? If necessary I could upload the error log installing v3.1.1 with magisk 13.3 on my phone. Thank you!
[Magisk] Nomelas:
I've updated to 3.2.1, it should hopefully fix your issue. unfortunately I have no way of testing.

In fact, I am no longer using this module as I've updated my phone to the OP5 so I no longer have the ability to test any future updates.
[Magisk] g40q90:
Great! It works perfectly, thank you for your work :)
[Magisk] distante:
Is there any news regarding the low volume in speaker?
[Magisk] m3n3chm0:
Hello guys,

I'll try this trick ASAP. My smartphone is a Zopo Speed 8 with MTK helio X20 MT6797 and when I make calls my mic volume is too slow.

It's running under marsapa custom rom Android 6.0 Cwm and rooted obviously.

Does anybody tried this on this MTK processor already?

I'll test it but before I need to backup all my data and try to flash as explained here.

Fingers crossed haha.

[emoji23]

Enviado desde mi m3 mediante Tapatalk
[Magisk] bgboii:
is there a fix to the low volume on the ear piece? im running abc rom on nexus 6p.
[Magisk] Nomelas:
This only fixes mic issues and not speaker issues
[Magisk] bgboii:
Well once I flashed this I had low volume in my earpiece but once I go back to stock it's loud. But of course the mic sucks.
[Magisk] Rockst4r007:
So this really works but I'm experiencing one issue, if I turn on VoLTE a weird noise will come out during the call... this doesn't happen if I disable the module. Any ideas what this could be due?

Thank you in advanced
[Magisk] 6hexanexz:
Thanks :highfive:
[Magisk] Nomelas:
here's the latest release for Magisk v14

can someone please test it out and see if it still works. It's been updated to the latest template.
[Magisk] AGoogler:
It don't work. After install it my phone stuck on boot screen.
[Magisk] DiogoSilva48:
On my Xperia z2 this improved a lot the call quality but when I have the ok Google on all screen activated with voice model, people can't ear me on calls, like the mic is muted. And sometimes mic is muted for some reason.
[Magisk] Macmoc16:
Also to me in the call people feel bad,when the register feels good. But whatsapp in audio or really bad calling, some advice?
[Magisk] james_321:
So after installing Android mic fix, ok Google will work even the screen off? I still looking a module for my s8. I tried Google assistant enabler 11.0.0 no difference. Can anybody help?
[Magisk] zkrocek:
Wow. Thank you so much. Just found out my warranty with Google expired in August and had to fix this myself. I haven't tinkered with any of this for a while and it reminds me just how much power we can have with root. You helped me fix this issue and I'm stoked!
[Magisk] kaisar11:
thanx for such a nice module

one query

if i manually edit my build.prop

n do these changes

ro.qc.sdk.audio.fluencetype=none

persist.audio.fluence.voicerec=true

persist.audio.fluence.speaker=false

use.voice.path.for.pcm.voip=true

do i still need module or module has just these changes

is these the only changes done to system or there is other things too

please confirm
[Magisk] Didgeridoohan:
That would be it. Nothing else needed...
[Magisk] Nomelas:
Correct. Though any firmware updates will reset your build.prop so it won't survive an update. Unlike this module, which will.
[Magisk] r0tati0n:
Hello [MENTION=5999829]Nomelas[/MENTION]

I found this:

https://vcillusion.wordpress.com/20...n-low-mic-during-call-problem-in-oneplus-one/

There it is suggestet to edit the line

ctl name="RX1 Digital Volume" value="93"

Could you take a look at this? For me it worked, what this site suggested.

OPO, Android 6 Sultan
[Magisk] Nomelas:
Thanks. I'll give this a test.

My girlfriend's phone died so she's using my old OPO so I'll be able to test this again, and I'll update to the latest template, when I get a chance.
[Magisk] r0tati0n:
Thank you :)

If you take a look at the comments at the bottom of this page, the writer explains something technical about these values.
[Magisk] davix3f:
But, does someone know why this happens?
[Magisk] greatcoder:
Has anyone tried it for lenovo k6 power?
[Magisk] e2vinay:
No change observed in-call

Loud speaker call volume goes insanely low :(

Loud Speaker is OK after removing the module

Redmi Note 4 | Linage OS 14.1 | Magisk 14
[Magisk] bmwfrkvt:
I just updated to 14.0 stable and installed this beta, seems to be working fine

Nexus 6p, pure nexus 6.0.1
[Magisk] Nomelas:
Sorry for the delay, I updated the master to the latest version.
[Magisk] vatstarun18:
I am Using lenovo zuk z2 plus

custom rom AEX 4.6

Whichever sim i have putted in sim1 ,receiver not able to hear me properly some echo voice i guess...sim2 quality is great

Do this work for me ?

i dont want to use magisk as i have installed Supersu so can i edit build.prop file from es file manager ?

i am on final version of custom rom so this file will never change i guess ?

please suggest me this as i really need voice clarity better
[Magisk] Didgeridoohan:
Of course you can. No guarantees that it'll work though...
[Magisk] lazye53:
Le Pro(zl1) working...

thanks :)
[Magisk] Rhaegar85:
It seems like a great work. Can somebody please confirm, will it work on MI5 running on viper 3.1? Thanks.
[Magisk] asusgarb:
I tried on Samsung Galaxy Note 3 SM-N9005 with LineageOS 14.1, and it sets the in call volume to 0. I can hear nothing. I have to activate speaker to hear the call.

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Magisk] pixiebob:
on my galaxy S7 my wife says that she heard me better so it's working :)
[Magisk] loop4444:
can this enable ok google detection when the screen is off? using rremix on 7.1.2 d855
[Magisk] deilativ:
Same question as [MENTION=1341566]loop4444[/MENTION], will this module make "OK, Google" work when screen off?
[Magisk] siealex:
No, it's a hardware feature.
[Magisk] Nomelas:
This module doesn't add any features to your phone that don't already exist. It only attempts to fix what is broken.
[Magisk] :
Does it work on oreo? I cant find mixer paths file on oreo?
[Magisk] HIRA123:
I'm not able to install it on my Lenovo p2. Tried two different versions but the installation fails.

How to solve this issue( I have attached the log below)
[Magisk] raamishmk:
Hi,

It fixes the mic to a really great extent, but breaks the loudspeaker option as the volume drops to 0 or so. The in call speaker is fine, but the loudspeaker doesn't works then.

Can there be a fix?

Thanks a lot for the module though.

Phone - Redmi Note 4 SD

Rom - Global Stable 9.2.1.0 with Magisk and Xposed

Recovery - Red Wolf Recovery
[Magisk] bmwfrkvt:
Compatibility w/ Magisk v16?

Nomelas,

Is this module still compatible with Magisk v. 16? If so, is it available in the repo?

I'm currently on v.14 and don't want to update if your module is not compatible.
[Magisk] rjwboys:
On Galaxy S5. LineageOS latest the module makes my receaver stop working
[Magisk] trohn_javolta:
I run an unofficial lineageos 15 version on oneplus x and my only issue is that in whatsapp the audio recording volume is really low. Flashing this didn't help, I'm here to ask if someone may have a fix for this.
[Magisk] Timer2006:
Hi, I try to install this module from magisk manager (v. 5.6.4) with magisk v 16.3 and the installation fails.

******************************************

Copy zip to temp directory

- Installing Android_Mic_Fix-v3.2.2.zip

- Mounting /system, /vendor, /data, /cache

*****************************************

! /data/magisk isn't setup properly!

! please install Magisk v14.0+!

*************************************

What's the problem? I use a nougat rom 7.1.2 resurrection sultanized

I try to install this module from the manager and from recovery but I have the same issue
[Magisk] Nomelas:
Sorry I haven't been around lately. I'll try and get this updated for v16
[Magisk] vaibhavpathak007:
agreed ? facing same issue
[Magisk] fmc000:
Make it three :D
[Magisk] Intelli69:
Is there anyway to make this mod a non magisk mod so I can use it on my snapdragon rooted S8? The incall volume is so low I have to wear earbuds every time I talk on the phone. It's ridiculous. Can anybody help me please?
[Magisk] Didgeridoohan:
Pretty much anything a Magisk module does can be done to your system directly. Take a look at the module to figure out what it does, and then do that manually...

If it's a module that adds something to /system or /vendor, you can do that yourself.

If it's a module like this one, that changes some prop values, you can edit build.prop (or even default.prop, but that's trickier) to match the desired values (you'll find the ones modified by this module in the OP).

Etc...
[Magisk] Nomelas:
I have in the description what props I changed. These are found in your build.prop file. You can easily google how to find it. Any time your firmware is updated though you'll need to reapply the changes (which is why I created a module instead)

On another note, I have v3.2.3 in git bumped to the latest template, I just haven't tested it yet. I have my oneplus one back from my wife so I'll check in the next few days.
[Magisk] Nomelas:
New version should be in the repo now
[Magisk] JPSU:
where is the new version? I'm using the latesr magisk v16 but all the files attached here always getting error
[Magisk] Nomelas:
3.2.4 should work from the OP. It's downloaded directly from the repo. Or just install from the repo (works on my oneplus one just fine)

What error do you get?
[Magisk] Gilfreitas:
I installed here in my j7 15 that has very low call volume and nothing has changed. Is there anything I can do? :(
[Magisk] _tz:
It fixed outgoing sound quality but reduced my loudspeaker volume to even lower than earpiece volume on my Redmi Note 4
[Magisk] Dreamer(3MF):
We Can Solve This Problem Partially By Using ViPER4Android So Kindly Try The Following

- Download ViPER4Android From This Link https://androidfilehost.com/?fid=818070582850508290 & Add The Following

-NEW

To The End Of Its Name. And Flash It Thru Magisk Manager Then Reboot

- Try To Use ViPER4Android & If It Didnot Work, Download Audio Modification Library From This Link https://xdaforums.com/att...5&d=1524785486 & Flash It Thru Magisk Manager Then Reboot

- Try To Use ViPER4Android & If It Didnot Work, Download SELinuxModeInverter4Magisk From This Thread https://xdaforums.com/apps/magisk/selinux-mode-inverter-t3775271 & Flash It Thru Magisk Manager Then Reboot

- Try To Use ViPER4Android
[Magisk] PedroCaseiro:
Doesn't work.

Zenfone 2 running latest official LOs14.1
[Magisk] darrenpauli:
Hi [MENTION=5999829]Nomelas[/MENTION]

Flashed Android Mic Fix via Magisk on my Nexus 6p running 8.1 Lineage. It dropped the in-call volume (not mic, not loudspeaker) to virtually 0. I uninstalled the module and it did not restore it. I wiped and flashed stock nexus and it did not fix the problem. Build.prop fluence values are default but the in-cakll volume remains extremely low.

My phone is virtually unusable in this state. I'll try a NANDROID backup in a few hours time.

cc [MENTION=7805402]mirfatif[/MENTION] [MENTION=4281335]jazzh[/MENTION] [MENTION=4281335]jazzh[/MENTION]
[Magisk] darrenpauli:
Full stock adb restore didn't help, nor did NANDROID. Mixer xml edits do not help. Anything you can offer in terms of remediation or what this mod may have done is very much appreciated [MENTION=5999829]Nomelas[/MENTION]. Phone is ruined unless I can fix this ?
[Magisk] lakshya dahiya:
Hello, your Module is not changing build prop value they are not sticking, plus the build prop command line u use are not same they have been updated example.

# This file will be read by resetprop

# Example: Change dpi

# ro.sf.lcd_density=320

ro.vendor.qc.sdk.audio.fluencetype=fluence

persist.vendor.audio.fluence.voicecall=false

persist.audio.fluence.audiorec=true

persist.audio.fluence.voicerec=true

Pls update module and instead of using system.prop use build.prop

[MENTION=5999829]Nomelas[/MENTION]
[Magisk] Didgeridoohan:
Are you checking the build.prop file or the actually set values? Because Magisk doesn't change the file, it reads the module system.prop file and loads those values. You can check with the getprop command.
[Magisk] lakshya dahiya:
i am opening build prop and checking , well if u can help how do i check if the value have changed in real time , also i didnt find any system propr should not the file in he module be read as build.prop not sytem.prop
[Magisk] Didgeridoohan:
No. The system.prop file is only used by Magisk to load the props and values you want to set. It doesn't directly have anything to do with the build.prop file.

If you want to check the value of a prop, use the getprop command. Here's an example:

getprop persist.audio.fluence.voicerec
[Magisk] SilverZero:
Seems to have fixed OK Google detection on my V30+ with screen off and locked, and in other apps. Neither was working before. Have not tested in-call volume but I'll update if anything negative emerges.
[Magisk] FredMontteiro:
Hi there,

I am trying change the mic sensitivity of a Usb headphone.

Which Mixer Paths line I need to change?
[Magisk] Chuky22:
Don't work in magisk manager v17.1
[Magisk] fido14dido:
Thanks. This helped fix my mic issue on my gen 1 Pixel running 8.1 RR ROM.

---------- Post added at 01:53 PM ---------- Previous post was at 01:52 PM ----------

Worked fine forms using Magisk repo
[Magisk] kholdstayr:
worked for my Moto G6

This fix worked for my Moto G6. I recently got a Moto G6 (RETUS channel, OPSS27.104-92-2, XT1925-6) and I found that I had really bad call quality after rooting it. I was told that I sounded like I was "off in the distance", or "tinny" sounding during phone calls.

I tried this fix and it worked great.

I am pretty new to rooting and this sort of thing, and I'm curious why rooting is messing up the build.prop and leading to poor call quality. Is there any good explanation for this?

Thanks!
[Magisk] UdayHawash:
I have lineage 16 on my j701f phone

will this work on my phone ???
[Magisk] Kaarb:
Anyone know if this work with Android pie? I'm using a oneplus 6
[Magisk] Nikola G.:
On bacon (OnePlus One) running a LOS 16.0 (Pie) ROM, this module does NOT seem to work.

I am experiencing very, very low in-call volume, which means that the other side can very barely hear me.

Unless someone offers a workaround/fix, this currently seems like a deal breaker for me to have Pie instead of Oreo.
[Magisk] Nomelas:
Hey guys - sorry for the lack of updates - I am no longer supporting this module and it will be removed from the repo shortly - unless someone wants to take it over.
[Magisk] maximusxxx:
After modifying build.prop this code:

ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicerec=true
persist.audio.fluence.speaker=false
use.voice.path.for.pcm.voip=true

the microphone has become much more sensitive and the interlocutors hear me much better.

But there is one unpleasant moment. now during the conversation I hear strong noises.

If i return the parameter:

ro.qc.sdk.audio.fluencetype=[B]fluence[/B]

the noise disappears, but the sensitivity of the microphone becomes weak again.

Can you advise something?
[Magisk] Nikola G.:
What I am doing currently is modifying the build.prop file manually (since it resets after each ROM flash because of updates), and it looks like the following

ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicerec=true
persist.audio.fluence.speaker=false
use.voice.path.for.pcm.voip=true

This definitely fixes the default state of the microphone, which is basically very much awful and the other side is unable to, or barely able to hear me - to be at least decent and workable.

I have not tested anything deeper than this, thus cannot provide details or metrics on the call quality itself like noise, sensitivity, volume.

Bottom line is that after applying this fix, the mic is actually usable and works much better than with its previous, default build.prop state.
[Magisk] tripLr:
Do you think the build prop can be imported to the actual ROM build codes ? [MENTION=6005084]ripee[/MENTION] to fix these mic issues ?
[Magisk] dallasnights:
Will give it try on Oneplus 7 pro thanks
[Magisk] vuoshino:
Is it working? Thanks
[Magisk] Mozie:
As vuoshino said above, does it work?

Really aweful crappy sound when recording, especially on apps like Snapchat and Instagram.
[Magisk] joranto:
I have two questions. The first is if I can edit the build.prop and add the lines listed at the beginning of this topic? And the second is if with this I improve the audio when recording the videos with the camera?
[Magisk] Redskitter:
Android 10

Is this compatible in android 10?
[Magisk] AntoRei:
Thank you, works on OnePlus 6t android 10
[Magisk] mahdira:
hello. my phone is pocophone f1 and cant find these file also the app for opening system file.

please help me to bost up my microphone
[Magisk] Omerozkn1:
Does it work with oneplus 6 oxygen os 10.3.7 android 10 please help me my phone mic doesnt work with apps like whatsapp snapchat
[Magisk] FarSight87:
Has anyone been able to try this on the Oppo Find X2 Pro? Does it work? Cheers.
[Magisk] avidichard:
This absolutely does not fix the issues with Samsung Galaxy S6 Canadian version. With an AOSP ROM, I was hoping my calling partner would not hear any noise, but it seams that AOSP is doomed to have this horrible screeching noise
[Magisk] babyboy3265:
Any idea if this could fix the top mic of an S9+?

Basically the top mic has some issue with strange cuttings. The bottom mic works fine. So during normal calls all is ok, but if I switch to the loudspeaker the phone starts using the top mic and people on the other side can barely hear me due to cutting.

Testing the sound loop with *#0283# showed exactly that, a normal sound from the bottom and very choppy sound from the top.

For a while I have been fearing that maybe the fact that I used to have Viper4android somehow damaged the mic since the same issue was present on my Note 5 as well, also at some point after installing v4a on the n5.

Any suggestion would be very welcome. Thank you.
[Magisk] Sparshit Thakur:
Hey there, it's 2021 now, and i have the issue with my Android 11 rom, and it is not a oneplus device though! Its xiaomi, should i try this ?? And i don't have a low volume issue, but i have and extra loud volume issue while calling 😂😂, tell me if i can try this, nothing has been working for this yet, i hope you'll reply soon...
[Magisk] redfield7:
Solved the problem with the poor quality of audio recording on whatsapp?
[Magisk] callmedanielpida:
hello I tried uploading every file to see if this android mic fix would work on my pixel 5a but it when I put it into magisk it says the files does not work please help
[Magisk] callmedanielpida:
this doesnt work for my pixel 5a I tried everything please help
[OnePlus 3 Questions & Answers] DeveloperOne:
Hi, I got this OnePlus 3, it had a very slight pink tint in right half and no tint on left (on white screen) so I got it replaced. Now the replacement is even worse,bottom and right side is much more pink than before, only top left side is fine, even on grey, I can see the top left portion is more bright than rest. What to do guys, I'm afraid third replacement will be even worse, I previously owned Nexus 6 and it had only pink tint in low brightness not this kind of uneven hue. Please suggest something.
[OnePlus 3 Questions & Answers] Explorer23:
Well, there's nothing you can do except replacing it ...

It can't be worse every time, you'll run out of bad luck eventually ?
[OnePlus 3 Questions & Answers] acmerw:
ask for RMA phone replacement, mine got replaced after 4 months of purchace.
[OnePlus 3 Questions & Answers] DeveloperOne:
Anyone from India? Amazon is refusing to replace it, now I don't know about service center, can anyone help me what to do, will service center replace ?
[OnePlus 3 Questions & Answers] candiesdoodle:
They may not replace the phone. But they should change the screen again.

Go to the one plus service center.. the ones they own and manage.. not the ones outsourced.

Btw, I have a similar issue.. on specific greys, the left side (about half a inch) seems brighter than the right side. Only on greys. All other Colors are just fine.

I took it to the non-company owned service center, the guy there couldn't really tell the difference as much as I noticed, but he agreed that he can try changing the screen. Though I haven't really gone that route yet since the phone is less than a month old. Will wait for some time and see. The color variation is fairly minor and not many people I have shown it to have been able to tell the difference.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] st!x:
Hey guys.

Yes, I'm new here, but not new to phones or computers by any means - trust me.

In any case, what happened was I downloaded the XDA Live version of Windows Mobile 6 for my Hermes (originally Rogers branded) and installed it.

Then, I discovered the actual forum here, and saw Schaps' version of WM6 pro and I want that badly. Regardless of which version I'm trying to upgrade to, I get the same issue.

Here it is:

When I connect the phone normally with ActiveSync and try to upgrade to Schaps' ROM (or Dutty's, or the official one, or the T-Mobile one, or the Qtek one, anything), I get a 260 error saying that my USB cable isn't properly connected. Now I've seen and tried the fixes for that error with no luck. The other error I occasionally get is one saying that my device code isn't correct or something or other. And another one is that my image file is corrupt and that I should check my update utility.

What do I do?

ANY HELP would be greatly appreciated!

Thanks in advance!

P.S. My bootloader version is 1.11 (I think) as per the following screen during bootloader:

HERM200

IPL-1.01

(The following part is in yellow below the above part)

HERM200

IPL-1.11
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pschoch:
I had the same problem.

I then upgraded the boot loader with hard-SPL:

http://xdaforums.com/showthread.php?t=296722

Now it's working fine and I can load any ROM.

Cheers

Pat
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] st!x:
I successfully upgraded to SPL-1.10, with the same result (no change).

I'm really unsure of what's going on with this...but I really need to upgrade to Schaps' TouchFLO ROM - and should be able to easily...
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pschoch:
When you upgrade the rom, chose hard-spl (safe).

Good luck

Patric