Develop Bugs

No sound in calls, and it's driving me crazy.

Long story short, I started having this issue 2 days later the flashing of CyanogenMod 13 ROM, almost a month ago, maybe a little more. Searching on Google it appeared as a problem of the Cyano ROM, watching the amount of complains found on the web but, after flashing a stock-based ROM, the problem persisted. So I thought that maybe the earpiece speaker got damaged and orderer a new part on eBay. While waiting for the new part to replace, I decided to try to flash the latest stock firmware, trying to solve any kind of kernel related problems. Of course it didn't work. Finally the new part arrived and, after installing it, with a bit of disappointment on my face I realized it wasn't the earpiece speaker the problem: still no sound in calls.
Now, could the problem be the motherboard itself? The 3.5" jack, which belongs to the same module, works just fine. Any idea?

PurPLe SKy said:
Long story short, I started having this issue 2 days later the flashing of CyanogenMod 13 ROM, almost a month ago, maybe a little more. Searching on Google it appeared as a problem of the Cyano ROM, watching the amount of complains found on the web but, after flashing a stock-based ROM, the problem persisted. So I thought that maybe the earpiece speaker got damaged and orderer a new part on eBay. While waiting for the new part to replace, I decided to try to flash the latest stock firmware, trying to solve any kind of kernel related problems. Of course it didn't work. Finally the new part arrived and, after installing it, with a bit of disappointment on my face I realized it wasn't the earpiece speaker the problem: still no sound in calls.
Now, could the problem be the motherboard itself? The 3.5" jack, which belongs to the same module, works just fine. Any idea?
Click to expand...
Click to collapse
Flash the newest modem and bootloader, see if anything change

yaro666 said:
Flash the newest modem and bootloader, see if anything change
Click to expand...
Click to collapse
They have been installed on the phone automatically by flashing the latest stock rom available in my country.

Hello bro i have same problem but now no problem
Flas stock firmware n7100xxufnd3 with odin then root phone install cmw recovery 6.0.43 dont install phils or twrp ans flash rom eclips or rubaband 4.4.4 dont install any rom based cm or aosp with phils or twrp recovery .
For me when i flash phils or twrp recovery then i flash any rom i have this issue no sound in call but with cwm 6.0.43 no issue at all 3 month without any problem

zortadot said:
Hello bro i have same problem but now no problem
Flas stock firmware n7100xxufnd3 with odin then root phone install cmw recovery 6.0.43 dont install phils or twrp ans flash rom eclips or rubaband 4.4.4 dont install any rom based cm or aosp with phils or twrp recovery .
For me when i flash phils or twrp recovery then i flash any rom i have this issue no sound in call but with cwm 6.0.43 no issue at all 3 month without any problem
Click to expand...
Click to collapse
First of all thank you very much for the answer, mate, unfortunately even by following the steps you listed the problem isn't gone. Any other tip?

I'm having the same prob 2. No sound on either sides of the call. The strange part is the sound returns intermittently

vishal1286 said:
I'm having the same prob 2. No sound on either sides of the call. The strange part is the sound returns intermittently
Click to expand...
Click to collapse
What do you exactly mean? Would you verify if the problem occurs only during calls? You can test the earpiece by downloading a specific app from the Play Store (e. g. Speaker Tester).
I've been playing around with the phone flashing modems, bootloaders, stock ROMs et cetera but nothing seems to solve the issue.

PurPLe SKy said:
What do you exactly mean? Would you verify if the problem occurs only during calls? You can test the earpiece by downloading a specific app from the Play Store (e. g. Speaker Tester).
I've been playing around with the phone flashing modems, bootloaders, stock ROMs et cetera but nothing seems to solve the issue.
Click to expand...
Click to collapse
the earpiece n mic r gud n working. Tested. They work well with skype n whatsapp call. I hv been using custom ROMs n kernel in this phone since its release bt this prob started 6 mnths bk.
Sent from my GT-N7100 using Tapatalk

Virgin Mobile HTC Desire 816

I have searched all over and couldn't find any answers, so hopefully this isn't a repeat thread.
I just purchased the HTC desire 816 and upgraded to it. I activated it, and set everything up, Saturday. Sunday after trying to load xposed onto it, it froze on the boot screen.
I managed to restore it from fastboot, and got it updated to lollipop.
Now for the problem, and what I have tried:
The phone will not see bluetooth devices at all.
First I tried simply a factory reset, which allowed it to see my smart watch and start to connect to it. Part way through the setup of my watch, it lost it's connection.
Next I tried a wipe and restore to full stock, this did not allow me to see any bluetooth devices.
Then I tried rooting, cwm, and putting kitkat back on the phone. I still couldn't see bluetooth, and now I am trying to upgrade back to lollipop.
I am at a loss as to what may be the problem, but I need it to work with bluetooth.
I have tested it with both my LG G smartwatch, and a gemline bluetooth speaker.

OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.

tenchu98 said:
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
Click to expand...
Click to collapse
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811

thoctor said:
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.

tenchu98 said:
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
Click to expand...
Click to collapse
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
Click to expand...
Click to collapse
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.

thoctor said:
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
Click to expand...
Click to collapse
I did this once already, I am thinking that my next step will be to manually copy the bluetooth related files from the system image into system using root
then flash unsupersu.zip

So I hav replace every bluetooth related file I can think of, and even deleted some file suggested online, and my phone still doesn't see other devices. When I put my phone on my NFc enabled speaker it acts like it is going to pair, but then says "unable to pair gemline speaker".
I am beginning to become frustrated.

Zuk Z2 Plus Touch Freeze

Hello Guys! I recently started to notice a very odd issue on my zuk z2 plus. I currently am running AospExtended ROM V6.4 (Android 9, Pie) with magisk installed. But this problem started before magisk was installed.
What happens is when i unlock my phone, after a mere 2 seconds, the touch absolutely freezes. I mean the screen is on, hardware buttons (U touch, Power & Volume Rocker) work, and i can even receive notifications, which means the phone is working, but the screen is not? If I turn off the device (Not Power Off, Just a tap of the power button) and unlock again, the touch resumes, but only for 2 seconds. This can be done infinitely. Reboots, shutdowns, forced power off, recovery etc all seem to go in vain, though some lucky reboots can save the day. Also, if I unlock the phone and then open google in a flash and start typing anything, it sometimes works and the touch resumes. This issue also persists in Safe Mode. ​
My issue is also very similar to the one seen here :
Video (Not By Me) : https://www.youtube.com/watch?v=JdMbbML9ECg
Forum : https://forum.xda-developers.com/lenovo-zuk-z2/help/touch-issue-t3708645
Keep in mind that I faced the same issue on my previous rom, Resurrection Remix v6.0 Oreo. I can always provide additional information if anyone wants. If anyone has faced the same issue, or has the fix to this, please do tell me as it is very difficult to manage.

Did you change something in root partition. I had the same issue in msm xtended when i deleted some app from system but after dirty flash it was solved.

bisht ankur said:
Did you change something in root partition. I had the same issue in msm xtended when i deleted some app from system but after dirty flash it was solved.
Click to expand...
Click to collapse
No, I did not do anything, also, the issue persists in safe mode too, so that means no 3rd party app is causing it.

Jodh5634 said:
No, I did not do anything, also, the issue persists in safe mode too, so that means no 3rd party app is causing it.
Click to expand...
Click to collapse
It could be a rom issue, try posting it on rom thread. Sorry i may be of no help.

have you tried to QFIL to latest zui and observe if the issue persist in zui as well??

Same problem here. Never rooted my z2, don't even have twrp installed. Always have been on 2.5.104 ST rom.
Really frustrating issue caused by Lenovo. Will ever avoid any Lenovo devices in future.

****
Same problems happening with mine too
I think that my hardware problem but now i guess its every one problem slowly

As a matter of update:
I got my z2 repaired locally. Service diagnosed short-circuit failure of the sensor. Nasty /really wanted to use another word here/ production quality by lenovo. Cost me around $60.

Question Poco F3 Signal issue both MIUI and custom roms

Hello everybody.
I have an issue with the Poco F3 regarding signal and networking.
After the last update to MIUI 12.5 and later MIUI 13, my phone was having issues making and receiving calls and also using mobile data.
Before those updates, I had no issues whatsoever.
I unlocked my bootloader and decided to try a custom rom, thinking it will solve this issue but nothing has changed.
I have "no service" in areas were many other phones (xiaomi and cheap ones at that etc) have at least 4g. Other times, while I do have service, I can't make or receive calls and even if I can, it's dropping after the first minute or so. Trying to use mobile data is a mess too, working rarely and most of the times I get that exclamation mark and cannot access the internet. It's starting to cause issues at work.
Note, that I use the phone with dual sims from different carriers and the issue is the same. I tried using only a single SIM thinking it might have something to do with dual sims but nothing.
I tried everything, from factory reset, to reseting network settings, airplane mode for 30seconds, custom roms, custom apns etc etc.
The sims work as they should on a poco m3 that I also own, but on the F3 the issue remains.
Now, the issue is much work with android 12, both with MIUI and custom rom (using PixelOS at the moment).
Do you think it is a hardware issue? Should I try an android 11 custom rom and see if the issue is fixed? Is there anything else I should try?
It's driving me crazy and since it's causing work related issues I am thinking of just getting a new phone at this point.
Thanks in advance.

crashpoum99 said:
Hello everybody.
I have an issue with the Poco F3 regarding signal and networking.
After the last update to MIUI 12.5 and later MIUI 13, my phone was having issues making and receiving calls and also using mobile data.
Before those updates, I had no issues whatsoever.
I unlocked my bootloader and decided to try a custom rom, thinking it will solve this issue but nothing has changed.
I have "no service" in areas were many other phones (xiaomi and cheap ones at that etc) have at least 4g. Other times, while I do have service, I can't make or receive calls and even if I can, it's dropping after the first minute or so. Trying to use mobile data is a mess too, working rarely and most of the times I get that exclamation mark and cannot access the internet. It's starting to cause issues at work.
Note, that I use the phone with dual sims from different carriers and the issue is the same. I tried using only a single SIM thinking it might have something to do with dual sims but nothing.
I tried everything, from factory reset, to reseting network settings, airplane mode for 30seconds, custom roms, custom apns etc etc.
The sims work as they should on a poco m3 that I also own, but on the F3 the issue remains.
Now, the issue is much work with android 12, both with MIUI and custom rom (using PixelOS at the moment).
Do you think it is a hardware issue? Should I try an android 11 custom rom and see if the issue is fixed? Is there anything else I should try?
It's driving me crazy and since it's causing work related issues I am thinking of just getting a new phone at this point.
Thanks in advance.
Click to expand...
Click to collapse
Rollback miui first to any android 11 version, see if the issue remains.
Then if you want you can flash custom roms and such... Your firmware got updated to android 12 when you upgraded miui , installing custom ROM won't downgrade it that's why you want to rollback miui

Thank you for your reply.
I need some time to do this proccess since I am practically 24/7 on call, but I will surely give it a shot when I get the chance.
Just a question though. Is it something common with this phone? A quick google search shows it happens with android 12 on the oneplus phones, but I got nothing for the poco f3.
Some time ago, with a similar issue, all I had to do was flash a kernel and it got fixed. Do you think there is a chance it is kernel related?

crashpoum99 said:
Thank you for your reply.
I need some time to do this proccess since I am practically 24/7 on call, but I will surely give it a shot when I get the chance.
Just a question though. Is it something common with this phone? A quick google search shows it happens with android 12 on the oneplus phones, but I got nothing for the poco f3.
Some time ago, with a similar issue, all I had to do was flash a kernel and it got fixed. Do you think there is a chance it is kernel related?
Click to expand...
Click to collapse
No idea... I don't think kernel houses firmware components tho , they live in their own separate partition

You can use DSU Sideloader. This allows you to boot into Android 11 and check Cell-connectivity & Wi-Fi, without touching your Main OS.
Basically, you download the Android 11 GSI, extract the "system.img", set up the app (either through Root or ADB), select "system.img" and Install.
That app utilizes Android's DSU feature, but lets you install any GSI you feed it.
Android has a built-in 'DSU Loader' in Developer Options, but it only lets you install the Android 12 and Android 13 Beta GSI, not older ones like Android 11. ^^
Note: GSI's don't work on Xiaomi.eu Custom ROM. May also not work on other Custom ROMs. ^^

cyanGalaxy said:
You can use DSU Sideloader. This allows you to boot into Android 11 and check Cell-connectivity & Wi-Fi, without touching your Main OS.
Basically, you download the Android 11 GSI, extract the "system.img", set up the app (either through Root or ADB), select "system.img" and Install.
That app utilizes Android's DSU feature, but lets you install any GSI you feed it.
Android has a built-in 'DSU Loader' in Developer Options, but it only lets you install the Android 12 and Android 13 Beta GSI, not older ones like Android 11. ^^
Note: GSI's don't work on Xiaomi.eu Custom ROM. May also not work on other Custom ROMs. ^^
Click to expand...
Click to collapse
That's a cool feature and thank you so much for the reply.
However, when trying it, I get stuck on the Poco logo and then straight to recovery. So I guess it doesn't work on the rom I am using.
Rebooting back to system from TWRP works as it should, so there are no further issues.
Tried the two official images from google, and the result is exactly the same.

crashpoum99 said:
That's a cool feature and thank you so much for the reply.
However, when trying it, I get stuck on the Poco logo and then straight to recovery. So I guess it doesn't work on the rom I am using.
Rebooting back to system from TWRP works as it should, so there are no further issues.
Tried the two official images from google, and the result is exactly the same.
Click to expand...
Click to collapse
Hm, I don't know.
You just need an unlocked bootloader (in most cases apparently).
When it didn't work for me, it was solely because of the Custom ROM Xiaomi.eu. Doesn't work at all there.
You're on Stock MIUI, I think, and it should work there normally. For me it does.

cyanGalaxy said:
Hm, I don't know.
You just need an unlocked bootloader (in most cases apparently).
When it didn't work for me, it was solely because of the Custom ROM Xiaomi.eu. Doesn't work at all there.
You're on Stock MIUI, I think, and it should work there normally. For me it does.
Click to expand...
Click to collapse
That's all true I guess.
But as I stated, I am on the PixelOS custom rom at the moment.
Just to see if the issue was MIUI specific, turning out it isn't.
I will return to MIUI 12.5 when I get the chance regardless.

crashpoum99 said:
That's all true I guess.
But as I stated, I am on the PixelOS custom rom at the moment.
Just to see if the issue was MIUI specific, turning out it isn't.
I will return to MIUI 12.5 when I get the chance regardless.
Click to expand...
Click to collapse
Did you ever get the signal problem solved?

narmak said:
Did you ever get the signal problem solved?
Click to expand...
Click to collapse
No, not at all unfortunately. Tried everything, even downgrading and switching around custom roms.
I figure it's a hardware issue and have since swapped my sim to my older Mi 9 Lite and use that device only for calls and data hotspot.
If, however, you have some solution to propose I will gladly give it a shot!

Hi, I also got myself the Poco F3 in June 2022.
Some days ago (~end of September) it started having little to no signal in places that I usually had good signal coverage.
I use 2 SIMs. I tried any combination of SIM as well as single SIMs.
Signal is bad and even if the indicator shows signal with severals bars, calls are not going out nor can I receive calls.
MIUI is
I thought of resetting the phone but after reading this thread I prefer to return the phone as long as it is still stock rather than wasting my time.
There are several posts about this issue on Amazon as well.

Same thing happening to me. This is a good smartphone but sadly, it wasn't just me that is having the same issue.

Same here. Simcard works fine in my Mi 8 and iPhone 7. Went back from LineageOS to MIUI, but MIUI tells me the Simcard "can't be activated" and doesnt get signal at all. With my Mi 8 i have 4G coverage.

I do have the exact same problem.
Tried different roms A11+A12, MIUI+Custom, even opened it up to check if the antenna cable was loose.
Has anybody fixed that problem?

did you manage to fix it? I had the same problem in pixelOs and now I want to install pixel experience but it worries me

gurripato said:
did you manage to fix it? I had the same problem in pixelOs and now I want to install pixel experience but it worries me
Click to expand...
Click to collapse
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.

Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Thanks for the hint. I will try it myself and report then...

I'm on the latest xiaomi.eu weekly beta and I do sometimes have a signal, but it's really unstable.

Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Are you using 5G or LTE data plan?

Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Problem is still there...

No sound issue can u help?

Hello
Im xda forum user sience many years but on this account im new (lost my old one). I remember flashing pda's, nokias and other ancient hardware , not an expert but quite experienced user. I had some break with flashing, tempering with soft and settings because of lack in time and other hobbies(3d designing, automatics, 3d printing, milling, programming plc's, and many others) i like to do things, if i want something, i ask "can i do it myself?". this is how i made telescope tracking the moon with camera attached to it. Anyway back to the point.
I came back to xda beecause of Xiaomi Mi 10t which i bought last year. It worked fine for half a year then 1st issue occured:
- when i was browsing internet phone went black and tried to reboot but couldnt boot into android. So i said to myself "broken soft time to flash new rom" couldnt do that because motherboard was fried and phone couldn't communicate to pc. fastboot didnt work etc. It went back on varranty, they replaced motherboard with new one.
It shouldnt be bad ive got new phone xD, wrong.
At work im cnc programmer/sometimes operator so i listen a lot of audiobooks, music. After 2 months of using "new phone" i experienced some stuttering on bluetooth headset, sometimes no audio. nothing that turning on/off bluetooth cant fix. I also used wire headphones when bt out of battery. That sound problems wasnt realy an issue for me.
Some time later i run out of battery couldnt make it to charger in 30 sec xD it died. Ive put it on charge to 100% then turned on at night. I belive in that time it auto upgraded itself and rebooted - lights woke me up. There was strange thing because i couldnt hear sound at logo which was present before. i assumed it was disabled at options and went back to sleep.
When i woke up i was checking what the damn thing done i was shocked because i couldnt hear any sound.
Symptoms:
- tried to call my wife, couldnt hear her and she couldnt hear me, messanger same
- no audio at youtube, video worked
- no notification sound
- xcom2 (game) crash on startup
- camera in video mode - crash suddenly
- netflix crash
Then i tried the bt headset, same thing as above. it could pair but no audio. strange thing was that i could hear messenger call when my wife was trying to call me, so i assumed software problem not hardware. tried wire headphones same result it was recognized as headphones, icon present, bt off.
Tried different things:
- phone restart (didnt help)
- wipe cache, factory reset, (didnt help)
- tempering with sound notification settings and rebooting (didnt help)
- safe mode (sound not working)
- upgrading software (no luck)
- factory reset (no luck)
- switching sim card then restart (no luck)
Then i went to quick settings toolbar there was suspicious thing: bell was wobbling as well dnd icon but not turned on just wobble once when quick toolbar rolled out. i hid it and rolled out again icons stood still. So i restarted phone and same thing occured - first roll out gray icons wobble, second roll stood still (no blue - not turned on on both attempts). Then i started to tempering with sound and notifications options dnd and silance settings included.
- turning on/off random settings, rebooting system many times, suddenly ive heard sound at booting logo. Ok so everything was fine, had sounds working properly: notification, yt, messenger, camera in video mode eaven xcom2 was working - everything was fine. Untill i decided to restart phone to chceck if it stays that way - it didnt. After reboot again i had no sounds. tried tempering with settings again, after many attempts sound came back. Now i didnt want to restart the damn thing. i left it on for 2 weeks without restart and sound was on no issues except stuttering (i could live with it). then i had some issues when somebody or i called someone - sometimes i couldnt hear them sometimes i couldnt be heard (turning on off speaker/mic while i was on line helped, sometimes not). angry i swithed to old phone to use it as phone (which mi 10t was not at the moment not eaven a tablet).
Started to tempering with settings again sometimes i had sounds sometimes not but always temporary. after many attempts of factory reset putting the localisation and other startup settings i decided to set voice recognition from google assistant eaven i couldnt hear sound at boot logo, surprised the dots were jumping when i talked it came back alive !!! after full startup settings sound and mic was working - untill restart. tried to do few factoryresets/startup settings without voice - no sound. then i did it few times with voice recognition from google assistant - it worked every time, surprised i assumed there was something chewing in settings between miui and google assistant.
It stayed that way for a month. everytime that i had sound problem, factory reset and setting voice recognition solve it. Untill i decided to update google assistant when restarted the "voice recognition method" didnt work. only random tempering with dnd/silent sound settings and many factory restarts helped.
I found out that when u want to restart phone to get sound back, pushing vol- button hundreds times before restart eaven the volume is on bottom and silent mode/dnd is on and then just after miui starts pushing many times vol+ and disabling dnd/silent helps - but that is just workaround not solving problem.
Angry at damn mi 10t tried different things:
- unlocked bootloader
- flashed many official eu roms,
- downgrading and upgrading
sometimes i had sound but after tempering with settings never on startup. i sticked to android 11 roms in that time.
then:
- tried chinese android 11 roms (no luck)
- tried eu, chinese android 10 roms (no luck sometimes black screen - but after switching to android 11 i could use phone again)
- tried eu/chinese android 12 roms (never worked always black screen and backlight when switching to android 11 system worked - no sound)
All those roms were official and fastboot and i was always using miflash, when downgrading i simply deleted or rem two lines from "flash_all.bat":
rem fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
rem fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
- installed twrp
- wiped repaired data partition if needed
- every flash attempt was after full wipe/factory reset
- tried many different apps like toggle dnd/silance
- tried to repair system with tools like ccleaner and others
- tried wipe/clear cache on every possible app eaven those hidden 300+ apps
- found some solution with build.prop:
fix sound
build.prob remove
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=14
but couldnt find those in my file maby different phone soft
- installed magisk and tried addons
* GSI Audio Stutter Fix - Mi NOTE 10 Lite (toco)
* Audio-Modification-Library_v4_0
* Magisk-Sound+ (2.2.0)
No luck im out of options right now but will still try untill i decide it is hardware maby hotair gun at qualcom? Can u guys suggest something else or maby i missed some options done it wrong? Heard about deleting all *.nomedia file but didnt chceck it yet and dont know if i got them. Usually using MIUI 12.5.8 or different eu 12.5 because 13 never worked and most 12.0 12.1 bootloop or not working. phone M2007J3SY rom usually RJDEUXM. If u gos any solution please write.
Ty for reading this elaborate, ill make it done or burn it xD
Uzul
Ps. bt headset still pairing but usbc/jack headset not recognized - no headset icon.

Uzul Warthlokkur said:
Hello
Im xda forum user sience many years but on this account im new (lost my old one). I remember flashing pda's, nokias and other ancient hardware , not an expert but quite experienced user. I had some break with flashing, tempering with soft and settings because of lack in time and other hobbies(3d designing, automatics, 3d printing, milling, programming plc's, and many others) i like to do things, if i want something, i ask "can i do it myself?". this is how i made telescope tracking the moon with camera attached to it. Anyway back to the point.
I came back to xda beecause of Xiaomi Mi 10t which i bought last year. It worked fine for half a year then 1st issue occured:
- when i was browsing internet phone went black and tried to reboot but couldnt boot into android. So i said to myself "broken soft time to flash new rom" couldnt do that because motherboard was fried and phone couldn't communicate to pc. fastboot didnt work etc. It went back on varranty, they replaced motherboard with new one.
It shouldnt be bad ive got new phone xD, wrong.
At work im cnc programmer/sometimes operator so i listen a lot of audiobooks, music. After 2 months of using "new phone" i experienced some stuttering on bluetooth headset, sometimes no audio. nothing that turning on/off bluetooth cant fix. I also used wire headphones when bt out of battery. That sound problems wasnt realy an issue for me.
Some time later i run out of battery couldnt make it to charger in 30 sec xD it died. Ive put it on charge to 100% then turned on at night. I belive in that time it auto upgraded itself and rebooted - lights woke me up. There was strange thing because i couldnt hear sound at logo which was present before. i assumed it was disabled at options and went back to sleep.
When i woke up i was checking what the damn thing done i was shocked because i couldnt hear any sound.
Symptoms:
- tried to call my wife, couldnt hear her and she couldnt hear me, messanger same
- no audio at youtube, video worked
- no notification sound
- xcom2 (game) crash on startup
- camera in video mode - crash suddenly
- netflix crash
Then i tried the bt headset, same thing as above. it could pair but no audio. strange thing was that i could hear messenger call when my wife was trying to call me, so i assumed software problem not hardware. tried wire headphones same result it was recognized as headphones, icon present, bt off.
Tried different things:
- phone restart (didnt help)
- wipe cache, factory reset, (didnt help)
- tempering with sound notification settings and rebooting (didnt help)
- safe mode (sound not working)
- upgrading software (no luck)
- factory reset (no luck)
- switching sim card then restart (no luck)
Then i went to quick settings toolbar there was suspicious thing: bell was wobbling as well dnd icon but not turned on just wobble once when quick toolbar rolled out. i hid it and rolled out again icons stood still. So i restarted phone and same thing occured - first roll out gray icons wobble, second roll stood still (no blue - not turned on on both attempts). Then i started to tempering with sound and notifications options dnd and silance settings included.
- turning on/off random settings, rebooting system many times, suddenly ive heard sound at booting logo. Ok so everything was fine, had sounds working properly: notification, yt, messenger, camera in video mode eaven xcom2 was working - everything was fine. Untill i decided to restart phone to chceck if it stays that way - it didnt. After reboot again i had no sounds. tried tempering with settings again, after many attempts sound came back. Now i didnt want to restart the damn thing. i left it on for 2 weeks without restart and sound was on no issues except stuttering (i could live with it). then i had some issues when somebody or i called someone - sometimes i couldnt hear them sometimes i couldnt be heard (turning on off speaker/mic while i was on line helped, sometimes not). angry i swithed to old phone to use it as phone (which mi 10t was not at the moment not eaven a tablet).
Started to tempering with settings again sometimes i had sounds sometimes not but always temporary. after many attempts of factory reset putting the localisation and other startup settings i decided to set voice recognition from google assistant eaven i couldnt hear sound at boot logo, surprised the dots were jumping when i talked it came back alive !!! after full startup settings sound and mic was working - untill restart. tried to do few factoryresets/startup settings without voice - no sound. then i did it few times with voice recognition from google assistant - it worked every time, surprised i assumed there was something chewing in settings between miui and google assistant.
It stayed that way for a month. everytime that i had sound problem, factory reset and setting voice recognition solve it. Untill i decided to update google assistant when restarted the "voice recognition method" didnt work. only random tempering with dnd/silent sound settings and many factory restarts helped.
I found out that when u want to restart phone to get sound back, pushing vol- button hundreds times before restart eaven the volume is on bottom and silent mode/dnd is on and then just after miui starts pushing many times vol+ and disabling dnd/silent helps - but that is just workaround not solving problem.
Angry at damn mi 10t tried different things:
- unlocked bootloader
- flashed many official eu roms,
- downgrading and upgrading
sometimes i had sound but after tempering with settings never on startup. i sticked to android 11 roms in that time.
then:
- tried chinese android 11 roms (no luck)
- tried eu, chinese android 10 roms (no luck sometimes black screen - but after switching to android 11 i could use phone again)
- tried eu/chinese android 12 roms (never worked always black screen and backlight when switching to android 11 system worked - no sound)
All those roms were official and fastboot and i was always using miflash, when downgrading i simply deleted or rem two lines from "flash_all.bat":
rem fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
rem fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
- installed twrp
- wiped repaired data partition if needed
- every flash attempt was after full wipe/factory reset
- tried many different apps like toggle dnd/silance
- tried to repair system with tools like ccleaner and others
- tried wipe/clear cache on every possible app eaven those hidden 300+ apps
- found some solution with build.prop:
fix sound
build.prob remove
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=14
but couldnt find those in my file maby different phone soft
- installed magisk and tried addons
* GSI Audio Stutter Fix - Mi NOTE 10 Lite (toco)
* Audio-Modification-Library_v4_0
* Magisk-Sound+ (2.2.0)
No luck im out of options right now but will still try untill i decide it is hardware maby hotair gun at qualcom? Can u guys suggest something else or maby i missed some options done it wrong? Heard about deleting all *.nomedia file but didnt chceck it yet and dont know if i got them. Usually using MIUI 12.5.8 or different eu 12.5 because 13 never worked and most 12.0 12.1 bootloop or not working. phone M2007J3SY rom usually RJDEUXM. If u gos any solution please write.
Ty for reading this elaborate, ill make it done or burn it xD
Uzul
Ps. bt headset still pairing but usbc/jack headset not recognized - no headset icon.
Click to expand...
Click to collapse
If you're on miui based rom tap several times on kernel version and test the main speaker. If it doesn't work take the phone to service center.

zaqm said:
If you're on miui based rom tap several times on kernel version and test the main speaker. If it doesn't work take the phone to service center.
Click to expand...
Click to collapse
thats not true i belive it is software based issue, read what i wrote about google assistant before update. i could somehow unlock sound and mic using voice recognition setting on startup after factory reset. without it speaker mic tests failed after "voice recognition workaround" it passed flawlesly and everything worked fine. so when audio worked cit menu all test passed after reboot mic fail and speakers fail. when workaround it passed again. it could be qualcom chip fault(reballing or hotair gun on chip if somehow tin connections are not good or cold soldier, but that doesnt explain how i manage to make it work(if chip failed) by setting the voice recognition in google assistant) but it is not only this phone issue most ppl report this after miui update and reboot, same as me and on different phones mostly on miui 12.5.
Sorry for a messy response i hope it is readable, too many thoughts in my head, and my english is a bit rusty
Edit 1 Anyway ty for your response because of that ill try to downgrade google assistant to version the "workaround" worked or eaven get rid of that spying thing from cell phone. what i have seen eaven when im fasboot flashing roms the google soft stays at the same version. so it is maby on different partition not affected by flashing as well as settings for it. dunno right now didnt do that things for a long time and my knowledge is outdated in that matter 6 years a long time sience i tempered in roms and partitions. maby it is pointless because chinese roms do not use google apps but what if broken settings affect chinese roms as well - who knows.
Ps. maby my monologue help others and myself to clear my mind and get correct conclusions ill update u guys and myself
Ps. 2 service center is last resort when ill totaly give up, eaven then ill first try to get my hands on service MiFlash where there is more options, maby total wipe and setting new partitions without leftovers from prewious roms and settings.
Ps. 3 Im not the kind of person who just go to service center. i like problems and solving it by myself thats how knowledge goes from. i like to know how all is made how aluminum is extruded how electronics work, how to build this and that. knowledge is my goal and then using it to achive goals which i set myself.
Ps. 4 this is similar problem to mine but without elaborate :
Sound Issue: No internal speaker/No microphone/No sound by bluetooth
Hi guys, Im here to speak about my mi 10t who got some sound/mic issue. Everything was working good but one day, the phone muted himself on stock Rom. When i tried to use the tap recorder, the app said "verify if an app is using the microphone...
forum.xda-developers.com

Hey Man I have a really similar issue to yours
It's seems there's No proper solution for this issue
I tried contacting several devs but even they couldn't solve it
The log will say
9717 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
9717 W AudioManager: updateAudioPortCache: listAudioPorts failed
I tried all the thing that you did
This actually happened after I was updating a rom of fw 13.0.6.0 EEA to 13 13.0.8.0 EEA
At first I thought this was one of the minor problems which would get fixed by clean flashing or installing stock rom But it seems that it even messes with the xiaomi activation thingy that you won't be able to connect to the Wi-Fi in the activation process.

cyb3rvirgin said:
Hey Man I have a really similar issue to yours
It's seems there's No proper solution for this issue
I tried contacting several devs but even they couldn't solve it
The log will say
9717 E AudioSystem-JNI: AudioSystem::listAudioPorts error -19
9717 W AudioManager: updateAudioPortCache: listAudioPorts failed
I tried all the thing that you did
This actually happened after I was updating a rom of fw 13.0.6.0 EEA to 13 13.0.8.0 EEA
At first I thought this was one of the minor problems which would get fixed by clean flashing or installing stock rom But it seems that it even messes with the xiaomi activation thingy that you won't be able to connect to the Wi-Fi in the activation process.
Click to expand...
Click to collapse
mine happened after updated itself to 12.5.8. today i tried deleting *.nomedia files from root it didnt help. then i tried to boot into MIUI Rescue System (vol+, vol- and power button at the same time) tried to update device by wifi, here is what i got: "couldnt find updates MIUI-V12.5.11.0.RJDEUXM (N/A) -> ??" when system is on ive got notification that there is 13.0.8 update. tried this from android always black screen and backlight after update, sometimes bootloop. fixed bootloop with twrp but same black screen and backlight just without bootloop. will try something different. as soon as i will know more about present androids ill try to chceck system files and scripts in java json xml right now im not familiar with it that much. right now ill try to downgrade google apps (especially google assistant itself and releted apps) maby uninstall all of it if possible.

When I changed from stock rom to Lineage OS, it was a bit annoying, first I was getting an error on the sim card screen, that was just one time, but then I realized that there was no sound, I did not find any solution and trying to try other roms like Pixel Experience and Xiaomi.Eu, I accidentally found the solution, which was deleting the Dalvik Cache, I returned to Lineage OS and no longer received errors and the volume worked perfectly (to this day I only have an error related to multitasking but it's ok it's tolerable)
Greetings and sorry for my enlish

Puruixa said:
When I changed from stock rom to Lineage OS, it was a bit annoying, first I was getting an error on the sim card screen, that was just one time, but then I realized that there was no sound, I did not find any solution and trying to try other roms like Pixel Experience and Xiaomi.Eu, I accidentally found the solution, which was deleting the Dalvik Cache, I returned to Lineage OS and no longer received errors and the volume worked perfectly (to this day I only have an error related to multitasking but it's ok it's tolerable)
Greetings and sorry for my enlish
Click to expand...
Click to collapse
dalvik was deleted many times but never tried lineage os. ill try to boot to twrp from fastboot, wipe everything and then install lineage or xiaomi.eu then wipe dalvik and wipe under stock recovery which i never did like that (i mean two step wipe). maby this will help.
today i tried viper4android and it returned abnormal status of driver aswell on legacy mode.
what warries me right now is te issue with wire headphones the icon is not present anymore so i may broke some more xD. eaven with sound problems i had wire headphones recognized icon present - it is another known issue with xiaomi devices. im experiencing more and more bugs some of them fixed some not.
good for me that i like this kind of problems and solving them is like a hobby and another phone is used as phome, mi 10t is playground right now xD

Good luck with it

Anything turn out from this investigation? I am having the same issue (Chinese version of OP8P) and don't have OG firmware to go back; to the software within which the drivers are usable.

I had exactly the same problem you describe. I tried flashing both stock roms and custom roms but it didn't work. I tried everything but only today I find the solution:
after installing a new kernel https://forum.xda-developers.com/t/kernel-overclocked-no-gravity-2023-02-26-protonclang.4531497/ and cleaning the dalvik cache, the sounds are back

MicheleRoar said:
I had exactly the same problem you describe. I tried flashing both stock roms and custom roms but it didn't work. I tried everything but only today I find the solution:
after installing a new kernel https://forum.xda-developers.com/t/kernel-overclocked-no-gravity-2023-02-26-protonclang.4531497/ and cleaning the dalvik cache, the sounds are back
Click to expand...
Click to collapse
Excuse me, how did you clean the dalvik cache if twrp is not compatible with mi10T? (unable to mount storage problem) Thanks in advance

I also have the same problem. Did you find a solution?