In-call voice telephony bug on custom AOSP based roms - Xiaomi Redmi Note 4 Questions & Answers

Hello to all
First of all i would like to say sorry if my english aren't so well
but i hope you readers can still get my point.
Here we go.
Straight to the topic, does anyone having this in-call bug while using an AOSP based roms?
Here is my situations,
If i call someone, or someone call me, i can only hear them.
In the contrary, they can't hear me.
It happens for me on Xenon HD 7.1.2 last build, AOSPExtended 7.1.2 last build and Cardinal AOSP 8.0 last build too.
I once have it working while using Xenon HD by flashing some zip and change some line in build.prop from "fluence" to "none" but i get no sound in speakerphone mode.
The reason i wrote this is because i really want to use AOSP based custom roms and i also need both call mode (normal call & speakerphone mode)
I really don:t think that this was a hardware issue since i got it working right on global stable MIUI8 and MIUI9, it works too on XIAOMI.EU latest rom.
For your information, i already try all fixes regarding this sound bug (on my side) i found here in this MIDO thread.
It's too much if i ask for fixes in this stage so i just need someone who are in the same state like me to confirm that they are facing the same problem.
or is it just me?
Thank you guys

it was really only me and Mr @nasko_spasko have this bug? no other? really?

Did you check these posts already? Did you try them already?
https://forum.xda-developers.com/showpost.php?p=73914743&postcount=188
https://forum.xda-developers.com/showpost.php?p=73870036&postcount=186
The problem is known for ages now and - as you can see - there is a solution with explanation.
What are the fluence related built.prop values in your ROM?

crok.bic said:
Did you check these posts already? Did you try them already?
https://forum.xda-developers.com/showpost.php?p=73914743&postcount=188
https://forum.xda-developers.com/showpost.php?p=73870036&postcount=186
The problem is known for ages now and - as you can see - there is a solution with explanation.
What are the fluence related built.prop values in your ROM?
Click to expand...
Click to collapse
Thank you for replying @crok.bic
I got it fixed by doing 2 steps as @mirfatif explained here
Editing fluencetype in build.prop from "fluence" to "none"
manually adding this line to "audio_platform_info.xml
<device name="SND_DEVICE_OUT_VOICE_SPEAKER" acdb_id="50"/>
Click to expand...
Click to collapse
reboot and profit

Related

[DEV] - Android L AOSP 5.1 phone call speaker issue

So a few of us have now started working on AOSP 5.1 and we have noticed that when making phone calls through the standard internal speaker, you can't hear the person calling and they can't hear you.
What I have tried so far:
Radios - tried older ones and current and no difference
Kernels - Again tried a few different kernels and still did not make any difference
gruesomewolf extracted the binaries from the factory image. I have added into my rom and hasn't worked. I am trying another build now.
Here is a link to my source code, so you can see what changes I have made:
https://github.com/StephenAOSP
The only changes I have made from stock 5.1 are:
Disable encryption
Disable recovery
Add in Vendor binaries
Use ota_from_target_files from scrosler's guide
Change device name
Disable restrict vendor files
Created bootanimation folder in prep for final build
I thought this would be a good place for Dev's to work on the issue and share findings. Pinging a few dev's to make them aware of the thread:
@gruesomewolf @fhem @scrosler @zephiK @rascarlo @simms22 @jakew02
Guys
Remember this is a high level discussion forum. Please keep posts related to fixing this issue.
Click to expand...
Click to collapse
Found an interesting post here:
hondajohn88 said:
zephiK...I got the voice call working without the speaker in stock aosp 5.1. It's in the mixer_paths.xml, a couple of missing lines in the 5.1 version. I copied over the lines from 5.0.2 and that fixed the problem.
I copied over lines 466 - 496 to replace those in the 5.1 mixer_paths.
(device/moto/shamu/mixer_paths.xml)
Hope this helps
Click to expand...
Click to collapse
Pinging @hondajohn88 to make sure he is aware of this thread.
Also here is a logcat attached with making a phone call.
I can confirm the above fix works on latest radio, stock kernel and latest 5.1 vendor files.
heres a flashable zip for those those whose roms havent updated yet https://drive.google.com/file/d/0B-W-PFSvgML0Mm5NdHIyQjlPeXc/view?usp=sharing
@Stephen
Just adding lines back in to the mixer_paths probably isn't the best approach to this. The commit that broke it is here:
https://android.googlesource.com/device/moto/shamu/+/b3816857ca7463f5e776ea1e5efbf59f714a96d0%5E!/#F0
I'm willing to bet if you revert that, it will fix the issue.
I'm actually not having this issue at all myself. Have you guys merged in the 5.1 kernel and updated the vendor files to LMY47D?
jakew02 said:
@Stephen
Just adding lines back in to the mixer_paths probably isn't the best approach to this. The commit that broke it is here:
https://android.googlesource.com/device/moto/shamu/+/b3816857ca7463f5e776ea1e5efbf59f714a96d0^!/#F0
I'm willing to bet if you revert that, it will fix the issue.
I'm actually not having this issue at all myself. Have you guys merged in the 5.1 kernel and updated the vendor files to LMY47D?
Click to expand...
Click to collapse
Could that commit break VoLTE activation on aosp based Roms? Not only did I have the earpiece issue but also cannot activate VoLTE service at all. I can on stock factory. @Stephen I see you have that issue as well.
Sent from my Nexus 6 using XDA Free mobile app
Good point. I wonder if rather than just adding in those two lines into the xml file, if I replace it from the 5.0.2 rom, will it get VoLTE working?
Like I said, I'm not having this issue at all on 5.1 stock or Omni (device trees are extremely similar), on T-Mobile in an LTE-area (Philadelphia).
I know that @dhacker29 had to call a number or something to enable VoLTE for VZW.. maybe he can fill everyone in on what he did to get it activated.
Stephen said:
Good point. I wonder if rather than just adding in those two lines into the xml file, if I replace it from the 5.0.2 rom, will it get VoLTE working?
Click to expand...
Click to collapse
I was told that this guy may have fixed VoLTE. I picked the last 3 commits and although my ROM is a little larger in size I now register as no SIM found on Verizon. Anyone know what lib(s) may affect that specific portion?
https://github.com/razrqcom-dev-team/proprietary_vendor_motorola/commits/cm-12.1
Sent from my Nexus 6 using XDA Free mobile app
cjkacz said:
I was told that this guy may have fixed VoLTE. I picked the last 3 commits and although my ROM is a little larger in size I now register as no SIM found on Verizon. Anyone know what lib(s) may affect that specific portion?
https://github.com/razrqcom-dev-team/proprietary_vendor_motorola/commits/cm-12.1
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
im using same vendor, as is @zephiK in Chroma5.1 howver VoLTE seems only be working for his TMo device. Noone has seeemed to figure out the No Sim issue on first boot, the only way around this is to dirty flash over a 5.0.X rom and then your 5.1 rom will see the sim and work just. Again no VoLTE but everything else is working well on my Verizon N6.

Fix for FM Radio (For both AOSP and CM based ROMs)

Hi All, I could able to fix the FM Radio on XenonHD current version (0706 build). After the compass fix (thanks to @vasishath) I was looking for a fix for the FM radio. As I didn't get any solution, thought of giving it a try myself.
I have tested it on my Mi3, it is working fine. Need confirmation from Mi4 users whether it is working or not.
Do not forget to change the Region from FM setting for your country.
Will it work on any other ROM where FM is not working or not there at all? Check the EDIT section.
Enjoy & Thanks!
EDIT 1: The fix is working on both AOSP and CM based ROMs where FM is inbuilt, hence changing the name of the thread and also the file name.
Thanks @pkatsaras (on Mi4 Banks CM build) for the confirmation.
EDIT 2: The fix is working on ROMs where FM is not present by default. You just need to create the required directory structure first before flashing it. Here is the link which has the detailed instructions.
Thanks @heerarana (on RR 07/24 build) for the confirmation.
Thanks. It worked.
24likan said:
Thanks. It worked.
Click to expand...
Click to collapse
Thanks for the update bro. May I know which ROM you are using?
I am using Bitti's cm 12.1 rom
Worked for me too... I'm in Team eos mi3
This fix is working perfectly on my Mi4 on latest resurrection remix rom!
Huge thanks!
Working fine on AICP 10 release...
Thank you...
CM Cancro ROM / FM is inbuilt... not working.
bluviper said:
CM Cancro ROM / FM is inbuilt... not working.
Click to expand...
Click to collapse
Did you try setting the region from FM app?
I'm on Candy5 with FM inbuilt, try this fix but seem not working, keep getting FM is not on, do I have to uninstall the inbuilt FM Radio before flash this fix. I can see the file folder structure are the same as you mention at first post
rajib4 said:
Did you try setting the region from FM app?
Click to expand...
Click to collapse
tried North America, USA, Japan, HongKong, Singapore
nothing connects, it says FM Radio is turned off
wiryawang said:
I'm on Candy5 with FM inbuilt, try this fix but seem not working, keep getting FM is not on, do I have to uninstall the inbuilt FM Radio before flash this fix. I can see the file folder structure are the same as you mention at first post
Click to expand...
Click to collapse
Thanks for the feedback. No, uninstall is not needed as the fix takes care of that. I will look into it for sure but need some time.
Cheers
bluviper said:
tried North America, USA, Japan, HongKong, Singapore
nothing connects, it says FM Radio is turned off
Click to expand...
Click to collapse
Thanks for the feedback bro. Strangely the same fix used to work on CM Cancro earlier builds (some other members confirmed that). Not sure if there is any update to the device tree which might be causing this. Will look into it but it may take some time.
Cheers
thanks for looking into it... and i also wanted you to know that I followed the special steps for RR roms... and that didnt work too..
more power!
The recent change in device tree is causing the fix to fail in some ROMs. Unfortunately couldn't find till now what change has broken it. It is still working in ROMs where changes are not done device tree recently.
UPDATE: Today I flashed TipsyOS and found there is no FM in there. So used my fix to install the FM and it is working very well.
Cheers
Unfortunately the fix does not work in Omnirom.
kruga said:
Unfortunately the fix does not work in Omnirom.
Click to expand...
Click to collapse
That's right because Omni (till now) doesn't have the sources for the FM to work. Can't do anything until the support goes in on Omni for FM.
rajib4 said:
That's right because Omni (till now) doesn't have the sources for the FM to work. Can't do anything until the support goes in on Omni for FM.
Click to expand...
Click to collapse
Oh.. ok. I was hoping that it would work on it. Was using XenonHD, which I liked, but the call bug was a minus
kruga said:
Oh.. ok. I was hoping that it would work on it. Was using XenonHD, which I liked, but the call bug was a minus
Click to expand...
Click to collapse
Try AICP v10 Nightly (9th August build). Very stable and feature rich. I am on it. Very good experience. But don't update to 11/13 Aug build as it has SOD.
Cheers
rajib4 said:
Try AICP v10 Nightly (9th August build). Very stable and feature rich. I am on it. Very good experience. But don't update to 11/13 Aug build as it has SOD.
Cheers
Click to expand...
Click to collapse
I believe AICP has inbuilt and forced - i.e. without my choice - "anti-piracy support measures". I like my system to be as clean as possible (I even use the pico gapps from tk so as to not install anything I don't want) and not want any extra "features" which are detrimental.
Tomorrow, they might think that xposed or ad blockers are bad - or some of them may even do worse things like what Lenovo did (not saying that AICP is doing that) - do not want to get into that situation. I am on Android because there is freedom of choice as compared to iOS and Windows, don't want it to get curtailed.

[PATCH][FIX] CM13 based ROMs - rotation, sensors, freezing bugs fix

Hi!
I made patches which will fix some problems in CM13 based ROMs (CM13, Resurrection Remix, AICP etc)
1. ROM which you using on your phone have this bugs?
-no working auto-rotation
-sensors does not works as should
-phones just freezing, look like turned off
YOU NEED THIS:
1. Download my new, final patch LINK!
2. Install latest CM13 or another ROM based on CM, like RR, example link HERE
3. Install patch
4. Wipe caches
5. Reboot your phone
2. Phone just freezing? Auto-rotation, sensors etc works?
YOU NEED THIS:
1. Download this patch: LINK
2. Install latest CM13 or another ROM based on CM, like RR, example link https://www.cmxlog.com/13/g2m/
3. Install patch
4. Wipe caches
5. Reboot your phone
Thats all
*TESTED AND WORKS ON ALL NEWEST ROMS BASED ON CM13, FOR EXAMPLE Resurrection Remix
even if the newest CM13 will be fixed you can use my patches for older version of CM or if you use Resurrection Remix or similar ROM,
i'm sure it will be still usefull
THANKS
Hi Wypier.... Awesome job!!! A big THANKS for this patch. This will be a very good notice for all..
I just have a question... This method can working for cm14 alpha too??
Thanks thanks thanks. :good:
zampotonic said:
I Dev. Awesome job!!! A big THANKS for this patch. This will be a very good notice for all..
I just nave a question... This method can working for cm14 alpha too??
Thanks thanks thanks. :good:
Click to expand...
Click to collapse
Thanks
about cm14 - i dont think so.
WYPIERDAALAAC said:
Thanks
about cm14 - i dont think so.
Click to expand...
Click to collapse
thanks for your quick response. only to better understand ... you have already tried with 14 cm? otherwise I can try on my device. (If they do not use a different kernel! But sure it is different) Last question ... do you think it will be possible to adapt it to the CM14? because now you have found the cause of the problem. thanks again and sorry English
zampotonic said:
thanks for your quick response. only to better understand ... you have already tried with 14 cm? otherwise I can try on my device. (If they do not use a different kernel! But sure it is different) Last question ... do you think it will be possible to adapt it to the CM14? because now you have found the cause of the problem. thanks again and sorry English
Click to expand...
Click to collapse
I didnt tried. Kernel is for another fix. With new mobius kernel phone can wake after lock, on latest cm13 kernels phone just freezing after some time. The problem was good know, but i think no one tried or cant find right libs. I will trying to find one right because not all stuff of patch is needed i think but it works. If the libs from similar phone could works on g2m we can try it on cm14 for g2m.
There will be no problems with irrc patch?
Cherry M said:
There will be no problems with irrc patch?
Click to expand...
Click to collapse
Why would be?
of course no, no problems - but anyway you can reflash irrc patch.
NEW VERSION, THREAD UPDATED
-Cleaned package
-Fixed music player and file manager problems
-Root issues if exist also fixed
-Reduced weigh and generally keeps system libs updated for example camera or stagefright libs which was replaced needlessly before.
WORKS PERFECT BRO!!!! Thank you!!!
thank you works well....(Resurrection Remix)
Hey, new update.
I'm suprised no one seen that visualization of music does not work
nevermind
-cleaned again, less number of libs replacment
-new kernel included (you can install MobiusM kernel if you want but you dont have to now)
-music visualization fixed
I hope it's a final version (it looks it is) thanks for using, good words and testing.
NEW LINKS IN FIRST POST
ps remember, every new update you must install on fresh system.
You're great! All works well Thank you! Greetings from Poland! Good luck!
Where is the source code for your changes?
mttronc said:
Where is the source code for your changes?
Click to expand...
Click to collapse
its not built by source
WYPIERDAALAAC said:
its not built by source
Click to expand...
Click to collapse
So which ROM did you take the libs from?
mttronc said:
Where is the source code for your changes?
Click to expand...
Click to collapse
mttronc said:
So which ROM did you take the libs from?
Click to expand...
Click to collapse
from 20160820-SNAPSHOT, why you asked?
WYPIERDAALAAC said:
from 20160820-SNAPSHOT, why you asked?
Click to expand...
Click to collapse
Just out of curiosity. Hoped there might be a real fix for this issue.
mttronc said:
Just out of curiosity. Hoped there might be a real fix for this issue.
Click to expand...
Click to collapse
yes, you can be sure now all works good with patch. I think will be no official fix because they are focused on CM14 and this bugs are not made by CM team as I know.
The fix is just a rollback to the old sensors drivers.
mobiusm said:
The "fix" is just a rollback to the old sensors drivers.
Click to expand...
Click to collapse
Yes, but worse is nothing bro... At least he was kind enough and trouble to somehow solve this little problem that bothered more than one...
mobiusm said:
The "fix" is just a rollback to the old sensors drivers.
Click to expand...
Click to collapse
Now I feel that you're mean to me little bit, are you?
So why no one else did something after two months if it's just old libs with kernel?
tell you something, no difference between them so this is real "fix" of this bothersome bug/s.
Fix is fix.
I respect you and I want little respect for me
If I got you wrong - sorry.

Woivods RR builds

Hi all,
I'm opening this thread so we can have a place to discuss Woivods builds (given he doesn't have a profile here on xda)
https://www.androidfilehost.com/?w=files&flid=158510
12.7 Build:
Can it first boot with gapps flashed?
Does the default theme work?
Performance/battery life compared to @fedosis Los?
He has an account in xda. He is @Krik88
It's because of SOME selfish individuals that make devs afraid to publish they Developments here, asking for ETAs, going off topic, creating a mess and n00bing about :laugh:
Well in any case, ill probably test his latest build later today. So I'll post my findings
So just finished setting up woivods RR
1. Clean flashed rom and gapps, got bootloop, rebooted to twrp, changed timezone and rebooted. It booted to google wizard. Again rebooted and wiped again everything except system, booted properly
2. Default theme still broken, but if you don't change it your good
3. Kernel looks the same as fedosis so it should be good
This rom has a built-in weather provider so that's nice. Will update in a day or two about battery life
The rom is getting better with every new build. Thank you for it @Krik88
Nice build. FM working, default theme working, volte working.
Two bug:
1. Reboot to recovery not working
2. Video call bag
Solutions: flash zip of both bug. After that both working.
Overall best build of RR by wovoid. Thanks dev.
rkjha said:
Nice build. FM working, default theme working, volte working.
Two bug:
1. Reboot to recovery not working
2. Video call bag
Solutions: flash zip of both bug. After that both working.
Overall best build of RR by wovoid. Thanks dev.
Click to expand...
Click to collapse
Change the theme to the pitchblack and try to change back
rkjha said:
Nice build. FM working, default theme working, volte working.
Two bug:
1. Reboot to recovery not working
2. Video call bag
Solutions: flash zip of both bug. After that both working.
Overall best build of RR by wovoid. Thanks dev.
Click to expand...
Click to collapse
Have you tried the patches at @fedosis 's G-Drive?
If not then try the ' AppsBoot fix' and Video Call fix.
PS: Sorry I didn't notice this line "Solutions: flash zip of both bug. After that both working."
Yes you can take the both zip from @fedosis build
Does any1 know how to fix the default theme?
Are sensors working
Nectarcdeam said:
Are sensors working
Click to expand...
Click to collapse
The link in the first post is for RR M, so yea
Pre-rooted?
Hi,
Can anyone answer below queries about the ROM.
1) Is it pre-rooted?
2) Build Date of the ROM
I need this info as I cant access my corporate mails on rooted phone and/or build date before may 2017. Currently using fedosis LOS and I am happy with that as well. Just want to taste RR as well
Thanks
aks_pk said:
Hi,
Can anyone answer below queries about the ROM.
1) Is it pre-rooted?
2) Build Date of the ROM
I need this info as I cant access my corporate mails on rooted phone and/or build date before may 2017. Currently using fedosis LOS and I am happy with that as well. Just want to taste RR as well
Thanks
Click to expand...
Click to collapse
1. Yes it's prerooted, but you can disable it in the developer options, don't know if your email app is going to detect it
2. July 12
Some questions about this built...
Hi everyone, I hope you are fine, well I have some questions about this built
1. How is the stability? i'ts recommended for daily use?
2. The IR blaster works?
3. The built needs fixes? And if it needs them, where can I find them?
Sorry I'm new in XDA and I'm a little lost with this topic about fixes hahaha, Thanks for the help! :good:
*I saw something about Arkamys pathes, but I don't have any idea of what's that haha
BlondCleric said:
Hi everyone, I hope you are fine, well I have some questions about this built
1. How is the stability? i'ts recommended for daily use?
2. The IR blaster works?
3. The built needs fixes? And if it needs them, where can I find them?
Sorry I'm new in XDA and I'm a little lost with this topic about fixes hahaha, Thanks for the help! :good:
*I saw something about Arkamys pathes, but I don't have any idea of what's that haha
Click to expand...
Click to collapse
1. Yes its stable for daily use
2. Probably didn't try it
3. Regarding patches I'm not completely sure if the reboot to recovery works if it doesn't flash the emmc_TWRP patch from the following link https://drive.google.com/drive/mobi...G5yP4fi63mNE9ZM1lwYXNyRlk?sort=13&direction=a
No other patch is needed
@Krik88
So I've tried to fix the default theme by flashing 19/04 build of teamghost then dirty flashing your latest build and the default theme worked properly.!
Buut the weather plugin broke so i had to wipe everything except system and now its broken again
I am not able to get this build running. I use encrypted data partition. Just for notice.
rionline said:
I am not able to get this build running. I use encrypted data partition. Just for notice.
Click to expand...
Click to collapse
Didn't try, but fedosis los works with encryption
I know, fedosis' rom is the only functional rom... That is just my opinion. Everything works, just the camera has some issues. Haven't found any better... Till now

Caller hears echo of himself when calling me on X820 with Lineageos

Hello everybody,
i have just done a clean install on my x820 with
Lineageos 15.1 and OpenGapps_arms64_micro incl Magisk5.6.4.
The caller (mobil or via whatsapp) hears himself as an echo if the loudspeaker
is on.
Google says somthing is wrong with mixer_path_letv.xml
but i dont know which parameter i schold change there.
Taking this file from Leeco 3 pro causes that
audio is not working at all.
Same effect on Lineageos 14.1 before.
Cann anyone help me, please.
3578761 said:
Hello everybody,
i have just done a clean install on my x820 with
Lineageos 15.1 and OpenGapps_arms64_micro incl Magisk5.6.4.
The caller (mobil or via whatsapp) hears himself as an echo if the loudspeaker
is on.
Google says somthing is wrong with mixer_path_letv.xml
but i dont know which parameter i schold change there.
Taking this file from Leeco 3 pro causes that
audio is not working at all.
Same effect on Lineageos 14.1 before.
Cann anyone help me, please.
Click to expand...
Click to collapse
It kinda makes sense since the mic and the loudspeaker are close to each other but I never had such a problem. Try installing other roms like AICP or RR.
LameMonster82 said:
It kinda makes sense since the mic and the loudspeaker are close to each other but I never had such a problem. Try installing other roms like AICP or RR.
Click to expand...
Click to collapse
Hello,
before 14.1 i use cucuo92 rom.
No echo at all with this rom, only bug with delayed whatsapp notification
I found a thread for Nexus 6 here
https://www.reddit.com/r/LineageOS/comments/5z7yjb/nexus_6_speaker_echo/deye3m5/
But it seems to be solved one year ago.
Same problem on moto x style :
https://forum.xda-developers.com/moto-x-style/help/lineageos-14-1-echo-phone-call-caller-t3574517
And here is some hint that it will be fixed :
https://www.reddit.com/r/LineageOS/comments/7r1aau/weird_echo_when_calling_moto_g3_lineageos_141/
I am experiencing the same problem with clean RR 6.0 on board through loudspeaker and microphone as well.
i just try AICP
and wondering that when calling
the echo effect is gone after ten seconds of duration!
After ten seconds unstanding is possible.
Yeah
I will take at look to RR rom.
... same bad effect on latest RR rom...
I guess all 8.1 roms have this kind of problem
Heyyo, it is a known issue on Oreo ROMs for the Le Max 2. Unfortunately no fix yet...
ThE_MarD said:
Heyyo, it is a known issue on Oreo ROMs for the Le Max 2. Unfortunately no fix yet...
Click to expand...
Click to collapse
Thanks a lot !
i got the hint that it should be fix on march 2018
correct?
3578761 said:
i got the hint that it should be fix on march 2018
correct?
Click to expand...
Click to collapse
Heyyo, unfortunately no... I haven't attempted to work on that yet. I'm working on upgrading the vendor blobs for reduced battery drain, better cellular radio quality and better GPS.
Fixing audio will be an extremely painful task... It has been attempted multiple times to fix perfectly...
Any progress to fix the echo problem?
3578761 said:
Any progress to fix the echo problem?
Click to expand...
Click to collapse
Heyyo, sorry none yet... I'm on EUI ROM 20s right meow trying to extract audio logcat but so far it won't let me achieve logcat level 7 which I need... Still trying to figure out what I can do for that.
ThE_MarD said:
Heyyo, sorry none yet... I'm on EUI ROM 20s right meow trying to extract audio logcat but so far it won't let me achieve logcat level 7 which I need... Still trying to figure out what I can do for that.
Click to expand...
Click to collapse
Good luck!
Any progress ?
3578761 said:
Any progress ?
Click to expand...
Click to collapse
Heyyo! Oops sorry for not returning to this thread but yes it should be fixed. With all my audio changes I can finally for the first time outside of EUI ROM do a loudspeaker call with my wife and she doesn't hear an echo. Same goes for Bluetooth car audio mode so that's awesome too! :good:
https://github.com/LineageOS/android_device_leeco_x2/commit/f48f41ee58cacc4bc3e582cba378a6b838d20ecc
https://github.com/LineageOS/android_device_leeco_x2/commit/7ab2949ac32b934ec387b1b660c3e5845470a59b
Hello The_Mard,
that sounds good.
Your fix is for LOS 16.0?
I am a classic enduser. Where i get the related ROM for download?
On this forum?
best regards
3578761 said:
... same bad effect on latest RR rom...
I guess all 8.1 roms have this kind of problem
Click to expand...
Click to collapse
I hace the same exact problem with AOSIP 8.1. Its there a zip to fix it or something to flash?
the echo problem should be on Pie fixed!
the echo problem should be on Pie fixed!
Can someone confirm this?
I've same problem on Pixel experience 20181020 (9.0) . Is this fix id good for leeco le 2 x526?

Categories

Resources