Related
I have some problem with bad sound/mic gain on my android(Not the robovoice error). I know several others also have that problem. It was a fix for this in this thread:
http://forum.xda-developers.com/showthread.php?t=805002
But now when I rename the file; default.acdb, my phone really goes bad with errors and so on. (tried og 2 different build and kernels)
I also have tried many different Radios, WM rom, kernels and builds but nothing helps. I also know my brother in law has the same problem.
Actually i think this is a problem with many here but we have choosen "to live with it".
Anyone have any ide what can fix this or any other useful information?
oyvpet said:
I have some problem with bad sound/mic gain on my android(Not the robovoice error). I know several others also have that problem. It was a fix for this in this thread:
http://forum.xda-developers.com/showthread.php?t=805002
But now when I rename the file; default.acdb, my phone really goes bad with errors and so on. (tried og 2 different build and kernels)
I also have tried many different Radios, WM rom, kernels and builds but nothing helps. I also know my brother in law has the same problem.
Actually i think this is a problem with many here but we have choosen "to live with it".
Anyone have any ide what can fix this or any other useful information?
Click to expand...
Click to collapse
Anyone? Maybe someone has an default.acdb that works?
I found this editing the build.prop, what happens if I put true where I have marked?
Have you done that? If not, can you please backup your build.prop and see if there are some results? If it works, I'll definately root my phone and enable it =D
Tried it, in fact I still have it enabled. But nothing changed, maybe the hardware doesn't support that..
Need HELP @ Note 3 ( SM-N9002 / SM-N9009 ) SIM2 Call Audio/Mic Routing & MagMa-NX ROM
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
I think I figured something. Everytime I attempt to make a phone call on this, I get to choose from which sim card should I dial, #1 or #2 , but what I have noticed now is that I am being asked "SIM1" or "Slot2" ... SLOT 2 I thought? That may be the reason that audio routing doesnt work well for this... tried searching build.prop but this string is not there and I just dont know where to search for this string to get this fixed, anybody can chime in?
Thanks
Did you figure it out ? As i have the same problem with the same rom in addition that when i call anyone and he is on a call i don't get notified with " call waiting
Mr.Ultimate said:
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
Click to expand...
Click to collapse
Which CSC did you choose?
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Mr.Ultimate said:
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Click to expand...
Click to collapse
Well, i know that mixer paths are different on single sim and dual sim phones.
Can you extract from stock rom the file "/system/etc/mixer_paths.xml" and overwrite the one in custom rom ?
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Mr.Ultimate said:
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Click to expand...
Click to collapse
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
zlazaar said:
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
Click to expand...
Click to collapse
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Mr.Ultimate said:
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Click to expand...
Click to collapse
Path : /system/csc
Indeed, conflits may happen. But just dump it and let we examine it.
Ok here is what I managed to try, I backed up stock rom android 5.0 all working state mixer files from etc dir, then flashed magma rom again, backed up those same files for restoration to working state, replaced files with ones extracted while on 5.0 stock android, reboot device, no sound whatsoever, phone wont even buzz keypad dialtones or connect dial phonecalls just hangs. So I went and restored back original magmanx rom mixer files, reboot, but still no success... so now I have just finished restoring 5.0 again, will dump csc folder and share with you. will also need to charge my battery a bit because @ 30% cant expect much to happen when flashing magma nx...
Thanks for the help amigo!!!
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Mr.Ultimate said:
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Click to expand...
Click to collapse
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
zlazaar said:
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
Click to expand...
Click to collapse
amazing, will try in few mins
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Mr.Ultimate said:
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Click to expand...
Click to collapse
Did you checked correct permissions before reboot ?
I'm afraid the problem is deeper than mixer paths.
I'll try to digg more.
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Mr.Ultimate said:
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Click to expand...
Click to collapse
The file "mixer_paths.xml" must have permission set to 0644 (like other files in /system/etc directory).
And try darklord Kernel.
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Mr.Ultimate said:
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Click to expand...
Click to collapse
Sorry i just noticed you already have darklord kernel.
And set permission like other files in this directory (if not already done by your file manager).
So for a while I've been trying to port Dolby Atmos 2.5 but to no avail. I tried using the Dolby Atmos Axon 7 magisk module as a reference to which libs and other files it may depend on, but it seems that there are different files, removed, possibly changed and added.
I've listed below the lib/dependency files and folders in the magisk module and the known Dolby atmos files from the system.raw image of the leaked build
These are the ones in the magisk module zip
/system/etc/media_codecs_dolby.xml
/system/etc/dolby/dax-default.xml
/system/lib/soundfx/libhwdax.so
/system/lib/soundfx/libswdax.so
/system/lib/libdlbdapstorage.so
/system/lib/libdlbmemoryservice.so
/system/lib/libhwdaphal.so
/system/lib/libstagefright_soft_ddpdec.so
/system/lib64/libhwdaphal.so
And now these are the ones that I have found in the system.raw image of the leaked Oreo ROM. I assumed the ones named "libdlb*" are ones used by Dolby so I included those, along with lib files that are similar to the old ones just incase.
/system/etc/dolby/dax-default.xml
/system/lib/soundfx/libswdap.so
/system/lib/soundfx/libswvlldp.so
/system/lib/libdlbdapstorage.so
/system/lib/libdlbdsservice.so
/system/lib/libdlbmemoryservice.so
/system/lib/libdlbnativeservice.so
The ones in red are the new libs that could be related to dolby that I've found. And as you can see, some of them are gone or changed such as /system/etc/media_codecs_dolby.xml and the lib files in /system/lib/soundfx/
Upon flashing these new files, the dolby app crashes. Logcat says this: https://i.imgur.com/ClcqbVr.png
I'm not developer guys but I am good at piecing things together. If there was a simpler way this could be done we could figure it out easily. Maybe some libs were added, removed, or modified for the Magisk Module to be compatible with ahrion's AML. I have uploaded a flashable zip that I created using Nikhil's Android Flashable Zip Creator which you can download right here. Make a backup, of course,
before flashing this. This is all being tested on the Project New World Oreo ROM by OrdenKrieger
I'm running the latest 8.1.0 Project World ROM and I'm reporting back with some force closing if the Dolby Atmos application. I can't seem to launch the app at all due to this. Thanks for trying to make this work, I appreciate it. ?
troy5890 said:
I'm running the latest 8.1.0 Project World ROM and I'm reporting back with some force closing if the Dolby Atmos application. I can't seem to launch the app at all due to this. Thanks for trying to make this work, I appreciate it.
Click to expand...
Click to collapse
Well if you noticed, the app does hang a little bit before crashing as it tries to load everything. But it seems when it can't load the audio effects it crashes. I don't know if it's related to audio_effects.conf or something
Teet1 said:
Well if you noticed, the app does hang a little bit before crashing as it tries to load everything. But it seems when it can't load the audio effects it crashes. I don't know if it's related to audio_effects.conf or something
Click to expand...
Click to collapse
I've noticed it do that when I try to launch it. My guess is that it has something to do with the audio_effects.conf
I uploaded the /system/ folder of the leaked ROM as a zip if anyone feels bold enough to try. Download here
Teet1 said:
I uploaded the /system/ folder of the leaked ROM as a zip if anyone feels bold enough to try. Download here
Click to expand...
Click to collapse
Why don't we ask the magisk module guys.
@ahrion and @Zackptg5 Is there a port of the Oreo Atmos version under way? Teet1 couldn't make it work by just taking the libs it seems
Choose an username... said:
Why don't we ask the magisk module guys.
@ahrion and @Zackptg5 Is there a port of the Oreo Atmos version under way? Teet1 couldn't make it work by just taking the libs it seems
Click to expand...
Click to collapse
I hope they are working on it....but I am certain the magisk module version was modified to work with their audio modification library. Perhaps I can try messing with that, but I probably can't share it if its their code
EDIT: so...after looking through the system image, I have found most of those missing files inside the /system/vendor/ folder...and just occured to me that a lot of the magisk patching occurs in the /system/vendor/ folder. Looking into it....
edit again: oh yes, I think I hav efigured out the problem. Now to test... https://i.imgur.com/ZfcGGka.png
Okay, so I'm making some progress. After copying from libs and other files from /system/vender/ it seems that the dolby service starts to work but still stops working. Ultimately, in the logs it ends in "dolby service not found". Also noticed a new error, the app crashes with an error saying "AudioEffect: set/get parameter error"
The app opens briefly, and hangs and then crashes. Attempting to play music pauses it for a while, then starts. Opening the dolby app while music plays pauses the music and then continues again. I copied a lot of audio files and "mixer pathes" files. If you take a look at my logcat, it seems as if I made the speakers work as they should as if it was in the stock rom! Maybe...they don't distort at high levels anymore and it's much clearer and louder. I can't get proper logs right now as I'm about to go to sleep and on my phone so i'll upload quick screenshots
I may still be missing some files, but who knows.
I am getting close. I've uploaded a link to the new zip here
Be warned, make a backup before flashing this. It's to test only, it doesn't work.
Here are some quick screenshots:
https://imgur.com/a/YQyKM
Have you had any progress?
chrisrodsa210 said:
Have you had any progress?
Click to expand...
Click to collapse
Nope, stumped now. I moved a lib/lib64 file called libaudioeffect_jni.so and that caused the app to instantly crash with a new error, which unfortunately I can't remember. The behavior was the same where the music took a couple seconds to start playing and then starts playing and opening the dolby app causes the music to pause for a bit. I took a look at that lib file and saw there were other audio libs it asks for so I moved those, which lead the phone into a bootloop. I assume that the service wants to work but can't call the audio effects for some reason. I'm not a developer, so I don't know what else I can do
Hello,
Here is a OnePlus 5 port of our Oreo Dolby. Maybe you can find the necessary files there. The current version of that thread works with OP5 but sadly didn't work with the first Project New World build, maybe the newest build works with this? Looking forward to this
https://forum.xda-developers.com/oneplus-5/themes/app-dolby-atmos-axon-7-oreo-port-t3734040
mariusfl0rian said:
Hello,
Here is a OnePlus 5 port of our Oreo Dolby. Maybe you can find the necessary files there. The current version of that thread works with OP5 but sadly didn't work with the first Project New World build, maybe the newest build works with this? Looking forward to this
https://forum.xda-developers.com/oneplus-5/themes/app-dolby-atmos-axon-7-oreo-port-t3734040
Click to expand...
Click to collapse
I'll definitely test this with the latest Project World and report back
---------- Post added at 09:07 PM ---------- Previous post was at 08:44 PM ----------
troy5890 said:
I'll definitely test this with the latest Project World and report back
Click to expand...
Click to collapse
EDIT: Tested the zip out and it didn't install on twrp. It just kept going and didn't install. Had to do a Hard Reboot.
getting the same issue where it doesn't install. I could try to use the files it moves, but theres a lot of scripts of setting permissions, writing things, etc and i feel like thats so much more complicated than just moving files it needs. I'm more hopeful of that zip than with mine.
Hello!
My problem is my device doesnt have audio. i tried calling using my device and mute is disabled. I cant also voice record. No audio from playing videos (youtube, netflix, spotify, chrome, etc). I cant record videos too.
What is wrong with my device? Do we have audio patch for this? I have also custom rom my phone with DotOS v.5.0.1 thru TWRP.. tell me if im missing a system app..
dyoliya said:
Hello!
i’m very new with having custom ROM. And I flashed my device with DotOS v5.0.1 thru TWRP. (Also tried diffrent custom rom)
My problem is my device doesnt have audio. i tried calling using my device and mute is disabled. I cant also voice record. No audio from playing videos. I cant record videos too.
did i miss something? Im sorry im really new with this. I dont know if there is a patch that i should use...
Click to expand...
Click to collapse
Not familiar with your custom ROM but many people don't properly install custom ROMs
Did you FORMAT (not Wipe - it's completely different thing) Data partition (!) when you switched the ROM? If you didn't, you must do it
Assuming you had audio with the official MIUI (otherwise, you may have hardware issue)
zgfg said:
Not familiar with your custom ROM but many people don't properly install custom ROMs
Did you FORMAT (not Wipe - it's completely different thing) Data partition (!) when you switched the ROM? If you didn't, you must do it
Assuming you had audio with the official MIUI (otherwise, you may have hardware issue)
Click to expand...
Click to collapse
ive done that. after flashing a ROM, I format data..
My audio was working before I custom ROM too. idk if i should just go back to stock rom
UPDATE:
I've tried several custom ROMs now, also stock ROM. But no luck. How am I supposed to know if this is a hardware issue??
WHAT'S NOT WORKING:
- Built-in speakers
- Video recording
- Screen recording
- Voice recording
- Headphones/Earphones
- Bluetooth earphones/speakers
- No audio calls, no ringtones
- Unable to disable/enable mute button during call
- During call, speakers are enabled but cant be disabled (still no sound)
WHAT'S WORKING:
- Adjusting volume sliders
I'm not sure if this has something to do with hardware since I dont recall it falling, etc.. It suddenly stopped working at all.
There are codes that you dial and you can test all your hardware separately. It depends on rom, so you have to try
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
yaro666 said:
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
Click to expand...
Click to collapse
I’ve tried going back to android 10 but the Original problem of my phone goes back again. It lags big time!! So i dont have a choice but to switch to a custom ROM.
i havent tried editing propsconfig yet. How do you do that?
swaggyp01 said:
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Click to expand...
Click to collapse
I have same problem but no one is trying to replace Audio ichha
Jeetp126 said:
I have same problem but no one is trying t
Click to expand...
Click to collapse
yaro666 said:
Try to wipe all, including recovery. Don't install newest rom, try older like android 10 and then if it doesn't work, you can try editing propsconfig
Click to expand...
Click to collapse
how can i edit the props config? hoping for help . big thanks. i want to try it so bad. but i dont know how to do that.
swaggyp01 said:
how can i edit the props config? hoping for help . big thanks. i want to try it so bad. but i dont know how to do that.
Click to expand...
Click to collapse
If you have Magisk, use Magisk Hide Props Config module to add/edit/remove any prop
Otherwise, from TWRP, Advanced, File Manager (for e.g. build.prop file) go to /system and copy the file build.prop to /sdcard.
Reboot to Android, edit your copy of build.prop saved to Internal memory.
Reboot again to TWRP, mount System as writable, copy build.prop to e.g. build.bak and copy your edited build.prop from /sdcard to /system
If anyting goes wrong, reboot to TWRP, remove your build prop and rename your build.bak back to build.prop
You can also copy build prop from TWRP to PC, edit it there and copy back
Google for details if you are unfamiliar with, this is just general idea
If using TWRP, make sure you make a backup file (like build.bak) to be able to resolve possible brick or something
If using Magisk and that MHCP module, changes will be systemless (google if not familiar with the term) and you can simply disable the module (and automatically all your changes on props) if anything goes wrong
Generally, it's not for beginners to play with props
zgfg said:
If you have Magisk, use Magisk Hide Props Config module to add/edit/remove any prop
Otherwise, from TWRP, Advanced, File Manager (for e.g. build.prop file) go to /system and copy the file build.prop to /sdcard.
Reboot to Android, edit your copy of build.prop saved to Internal memory.
Reboot again to TWRP, mount System as writable, copy build.prop to e.g. build.bak and copy your edited build.prop from /sdcard to /system
If anyting goes wrong, reboot to TWRP, remove your build prop and rename your build.bak back to build.prop
You can also copy build prop from TWRP to PC, edit it there and copy back
Google for details if you are unfamiliar with, this is just general idea
If using TWRP, make sure you make a backup file (like build.bak) to be able to resolve possible brick or something
If using Magisk and that MHCP module, changes will be systemless (google if not familiar with the term) and you can simply disable the module (and automatically all your changes on props) if anything goes wrong
Generally, it's not for beginners to play with props
Click to expand...
Click to collapse
Thanks for explaining everything brother. Now I will do a research about editing audio or sound on build prop. Hopefully this is not a hardware issues.
Same issue encountered with me also. I am in a great distress right now. Tried more than 30+ roms (including recover, fastboot, custom, and stock), but nothing helps.
IF you find anything please update here.. THat'll be a great help indeed!!
dyoliya said:
UPDATE:
I've tried several custom ROMs now, also stock ROM. But no luck. How am I supposed to know if this is a hardware issue??
WHAT'S NOT WORKING:
- Built-in speakers
- Video recording
- Screen recording
- Voice recording
- Headphones/Earphones
- Bluetooth earphones/speakers
- No audio calls, no ringtones
- Unable to disable/enable mute button during call
- During call, speakers are enabled but cant be disabled (still no sound)
WHAT'S WORKING:
- Adjusting volume sliders
I'm not sure if this has something to do with hardware since I dont recall it falling, etc.. It suddenly stopped working at all.
Click to expand...
Click to collapse
Exactly same thing happened with me, at that time I was on Miui global stable 12.0.9.0.. It happened all on a sudden. Now I am phoneless
swaggyp01 said:
man we have the same issues. my device has no audio source since i switched on custom rom. i tried to back again on stock rom but it doesent work again. the technician recommend to replace the audio ic which is hardware issues. anyone can help us on this problem? my device is mi 9t
Click to expand...
Click to collapse
Same exactly
If you r getting error while playing ringtone through settings then its your ui problem. You have to shift custom ui i recommend pixel UI or Oxygen os
Jeetp126 said:
If you r getting error while playing ringtone through settings then its your ui problem. You have to shift custom ui i recommend pixel UI or Oxygen os
Click to expand...
Click to collapse
Yes You are right
IMPORTANT UPDATE:
Hello everyone! it's a request to everyone who has/is facing this problem PLEASE GIVE A FEEDBACK via FEEDBACK APP.
I talked to one of the official MIUI representative & he further talked to the MOD & they said they haven't got any such feedback so please spam this problem!
here is the proof: AGB the official representative of MIUI
View attachment 5525269 View attachment 5525271View attachment 5525273View attachment 5525275
IMPORTANT UPDATE:
Hello everyone! it's a request to everyone who has/is facing this problem PLEASE GIVE A FEEDBACK via FEEDBACK APP.
I talked to one of the official MIUI representative & he further talked to the MOD & they said they haven't got any such feedback so please spam this problem!
here is the proof: AGB the official representative of MIUI
View attachment 5525269 View attachment 5525271View attachment 5525273View attachment 5525275