Database Develop

Vivid ROMs and in-call volume issues

I'm doing research for a friend's phone. He has the AT&T HTC Vivid. My old phone actually. I have yet to root it or do any of the dirty work as I am concerned with the stability and flaws in ROMs for this device. A little advice would be appreciated.
I have read about the Dirty Unicorn ROM with the Pac kernel (or since updated stock kernel). They say the volume is fixed in this ROM. Can anyone confirm?
Also would like to know of other ROMs and what is available out there through others advice. I want to find him stable as he cannot be flashing daily the way I can. I have seen lots of bluetooth issues called out. I am more concerned with stability, call volume, and definitely good data/wifi. Someone point me in the right direction perhaps?
I would love to see Sense gain more support for this device, but I'm not a dev so I'm sure it's no easy task. I have used CM alot in the past, and loved most of it, but it always had its bugs so I hesitate to flash without gathering information.
Thanks guys.

acw928 said:
I'm doing research for a friend's phone. He has the AT&T HTC Vivid. My old phone actually. I have yet to root it or do any of the dirty work as I am concerned with the stability and flaws in ROMs for this device. A little advice would be appreciated.
I have read about the Dirty Unicorn ROM with the Pac kernel (or since updated stock kernel). They say the volume is fixed in this ROM. Can anyone confirm?
Also would like to know of other ROMs and what is available out there through others advice. I want to find him stable as he cannot be flashing daily the way I can. I have seen lots of bluetooth issues called out. I am more concerned with stability, call volume, and definitely good data/wifi. Someone point me in the right direction perhaps?
I would love to see Sense gain more support for this device, but I'm not a dev so I'm sure it's no easy task. I have used CM alot in the past, and loved most of it, but it always had its bugs so I hesitate to flash without gathering information.
Thanks guys.
Click to expand...
Click to collapse
No DU just fixes The volume increase decrease while in a call
If you care about in call volume try a sense 4.1 rom or a sense 3.6 rom

Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
bilibox said:
No DU just fixes The volume increase decrease while in a call
If you care about in call volume try a sense 4.1 rom or a sense 3.6 rom
Click to expand...
Click to collapse

acw928 said:
Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
Click to expand...
Click to collapse
It's always going to be work. and for me my volume is just fine. In call works loud enough for me. But everyone has their own preferences. Other people cant use the roms due to the volume issue

To answer your question... I would put CM10.1 from albinoman... Prolly the most stable we gots
Sent from my Vivid 4G using Tapatalk 4

acw928 said:
Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
Click to expand...
Click to collapse
I have an AT&T Vivid, and have had varied results in this department. Though, I work in a server room/data center, so I have more ambient noise to contend with, but I've experienced horridly low volume on some builds all the way to just less that stock quality. The first ROM I experienced this on was a Sense 4.1 ROM, but also experienced it in different ways with aosp/aokp builds as well. I don't know if it is related, but I did notice a significant increase in the in call volume after performing the S-OFF wire trick. Though that could just be a coincidence. But one common theme I have found, is when the in call volume has been low, don't even attempt speakerphone use. As when I did, it either didn't work at all (or so low it's inaudible) and then when returning to the earpiece, 6/10 times (guesstimate) the issue of no volume followed for the duration of the call. And the odds would increase when activating speaker before the call is answered on the other end (making calls). However, I must say that I the in call volume using bilibox's unofficial rootbox, I do not experience the low in call volume, but the speakerphone is (mostly) useless. (Still an awesome ROM though, just waiting for mobile data fix )
Not sure if my ramble is helpful or not, but those are summed up experiences I've had thus far. If you really just want it to work without goofing with anything, I 'd recommend either a rooted/modified/de-bloated stock ROM.
There's my 2 cents {plunk plunk}

CyanogenMod 12 for HTC One Mini 2 (Memul)

Hi guys,
Thought I would start a thread for users of CyanogenMod 12 for HTC One Mini 2 (memul).
I have installed a nightly dated 24th February 2015. It seems to be working great, my only issues have been:
After phone restart, the first time you call someone you cant hear them. Call them again, the problem is fixed and doesnt seeem to come back for that contact. (will happen again for other contacts the first time you call them though).
Camera is very laggy and doesnt respond well at all...the viewfinder is super stuttery and laggy and when you hit the take a picture button it can take a second or two to respond. I dont use the camera much so it doesnt bother me.
Have had some problems with the music player not outputting music to the headphones after a while, but taking the headphones out, pressing play so it plays out the speaker, then putting the headphones back in fixes this. Again,
not a big issue.
Official TWRP stops working after going through setup, but factory reset from within CM12 fixes it if you do have to re-flash or something.
So I recommend CM12 latest nightly for our phone, its better than CM11 and actually had less problems than the Release channel rom for our device (CM11). Although that ROM says it has no known issues, there are known issues that have not been noted on the wiki.

Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.

ECEng said:
Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.
Click to expand...
Click to collapse
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.

snorglamp said:
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.
Click to expand...
Click to collapse
Thanks for the advice, I installed march 25th build last night.
From your first post, only problem i experienced was the camera, its still very laggy, and the picture quality dose not compare well to the original. I have tired third party camera app but no joy, similar issues. Other than that, happy to say every thing else is working fine, i will update regularly to see if camera improves.

Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.

mlhamdi said:
Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.
Click to expand...
Click to collapse
Hi there,
I have been flashing the latest nightly. I think we need to log a JIRA issue for the camera, but I havent checked if someone already did. It doesnt seem to be getting better does it?
Dont use chrome...if you dont like the cyanogen browser, try firefox XD
The best recovery is TWRP, see the other posts in our part of the forum about this. Make sure your get the U-RA version of TWRP as the official TWRP page doesnt list our device for latest versions.

Also I should note that the calendar doesnt work in this ROM in offline mode, which is true for all Cyanogen ROMs i believe. But the solution is to install from DroidForge the offline calendar account, and then you can enter items in the calendar without google calendar, or sync USB with outlook etc (latter requires purchase of sync program separately to go on your PC).

Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091

corbeau56 said:
Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091
Click to expand...
Click to collapse
That is bad news alright, Is there any way for me to get back to stock rom and wait for official lollipop release? I am quiet new to this.

Microphone stopped working on calls

Hi, I have a Redmi 4a with a custom android 11 ROM (tried a few).
Since a few days the microphone is not working on calls. If I record a video the audio recording is ok, so the mic itself does not have problems.
Hands-free calls work (loudspeaker), but still mic is muted or very low level.
Headset works correctly, with its own mic.
I think the microphone level is too low during calls, maybe some setting got messed up, but I do not know how.
I already tried doing factory reset, cache wipe, full wipe+ROM re-flashing, changing ROM (still keeping Android 11).
Only a few apps have microphone permission: Camera, FM Radio, Phone & now Phone Doctor Plus, which I installed to control the mic and the earphones plug (all working perfectly, all available microphones).
Google Assistant is disabled.
Bluetooth is off, nothing coupled at all.
Any Idea before I wipe again and try a ROM with Android 10 (or 9, or 8, ...)
Thanks, Leonardo

leodp said:
Hi, I have a Redmi 4a with a custom android 11 ROM (tried a few).
Since a few days the microphone is not working on calls. If I record a video the audio recording is ok, so the mic itself does not have problems.
Hands-free calls work (loudspeaker), but still mic is muted or very low level.
Headset works correctly, with its own mic.
I think the microphone level is too low during calls, maybe some setting got messed up, but I do not know how.
I already tried doing factory reset, cache wipe, full wipe+ROM re-flashing, changing ROM (still keeping Android 11).
Only a few apps have microphone permission: Camera, FM Radio, Phone & now Phone Doctor Plus, which I installed to control the mic and the earphones plug (all working perfectly, all available microphones).
Google Assistant is disabled.
Bluetooth is off, nothing coupled at all.
Any Idea before I wipe again and try a ROM with Android 10 (or 9, or 8, ...)
Thanks, Leonardo
Click to expand...
Click to collapse
Are you sure it is issue on your side? Did you try it out with several ppl? Might be some issue on the other side, just a guess.
First of all, I would recommend to check out telegram channels/official sites of mentioned ROMs for latest updates.
It looks to me as if you installed some outdated ROM, because i have not heard of mic issues for couple years.
Also join tg channel for our device, where you can request assistance.
Second suggestion would be check for phone caller app from other ROMs, from LineageOS for example is usual choice (you can find it on APK Mirror) or AOSP from AOSP-based ROMs.
If you have Magisk installed, check out for "NLSound for QCom Devices" module, it is a module that includes setting sensitivity of mic a lil bit higher as well as other sound enhancing options. (NLSound Tg Channel), or try to check out whatever module for that matter.

I changed a few other Android 11 ROMS, all with the same issue. Also AOSP.
Android 10 CRdroid works better, mic level is low, it's higher with free speaking.
It looks like a sensitivity issue, maybe I have to change some mixer.xml settings?
Now I'm back to Android 11, Nusantara (unified 4a & 5a), but still the problem persists.
Installed NLSound: not better.
Can I configure mic level on NLSound? Where (or with which app) should the mic level be exposed?

You cannot configure mic sensitivity with NLSound, but during installation you can choose option to increase it. Which i thought could resolve your issue.
I honestly ran out of ideas atm, maybe someone more expirienced will join the discussion.
But while we are at it, could you specify a little bit more, how your mic stopped work properly? Because it still doesnt looks like a ROM issue to me, all ROMs are generic and share same device tree, which already has optimised settings and rarely being updated.
Was it like you installed custom ROM and mic immidiately went bananas, or you installed custom ROM, mic worked for certain amount of time, and then issue appeared?
Maybe try to reflash persist.img and firmware.img from original MIUI ROM, or roll back on MIUI(but dont lock bootloader) and check if issue is still present.

2ley said:
You cannot configure mic sensitivity with NLSound, but during installation you can choose option to increase it. Which i thought could resolve your issue.
I honestly ran out of ideas atm, maybe someone more expirienced will join the discussion.
But while we are at it, could you specify a little bit more, how your mic stopped work properly? Because it still doesnt looks like a ROM issue to me, all ROMs are generic and share same device tree, which already has optimised settings and rarely being updated.
Was it like you installed custom ROM and mic immidiately went bananas, or you installed custom ROM, mic worked for certain amount of time, and then issue appeared?
Maybe try to reflash persist.img and firmware.img from original MIUI ROM, or roll back on MIUI(but dont lock bootloader) and check if issue is still present.
Click to expand...
Click to collapse
It stopped by itself, without me doing any specific install, as far as I can remember.
I reinstalled NLSound, with mic and volume optimizations. Still not ok.
One question: can I flash persist.img and firmware.img without losing the functionality of the ROM I have now, or should I then re-flash also the custom ROM afterwards?
Thanks for the hints.

leodp said:
It stopped by itself, without me doing any specific install, as far as I can remember.
I reinstalled NLSound, with mic and volume optimizations. Still not ok.
One question: can I flash persist.img and firmware.img without losing the functionality of the ROM I have now, or should I then re-flash also the custom ROM afterwards?
Thanks for the hints.
Click to expand...
Click to collapse
Yes, you can flash persist.img and firmware.img without any concerns about ROM.
It shouldnt affect ROM functionality, it is just a pre-caution step, in case any of previous ROM's you played with made some unnecessary changes.

2ley said:
Yes, you can flash persist.img and firmware.img without any concerns about ROM.
It shouldnt affect ROM functionality, it is just a pre-caution step, in case any of previous ROM's you played with made some unnecessary changes.
Click to expand...
Click to collapse
persist.img flashed, no change.
firmware.img: cannot find it in the stock MIUI I downloaded
rolling back to older MIUI: have not done it yet, as I do not know how to avoid relocking the recovery. I never did it before and I have run out of wife's patience in the meantime

leodp said:
rolling back to older MIUI: have not done it yet, as I do not know how to avoid relocking the recovery. I never did it
Click to expand...
Click to collapse
Gotta download Xiaomi official tools for this purposes. MiFlash PRO, or Mi Unlock or something like this, dont remember the name. The one you unlocked bootloader of a phone with, same tool can also flash stock MIUI back, if i remember correctly, According to MiUnlock FAQ bootloader wont lock, unless you choose special option "Clean All and lock"
I also found this instructions to deal with sound problems, check if it will fix your problems.
Spoiler: instructions
For non root users
Code:
Go to the following path
Setting > Google > search > voice > "ok google" detection and turn off both the options.
That's it.
For root users, edit audio_platform_info.xml and/or build.prop
Code:
Navigate to the root directory of the phone
Root/system/etc/
Then look for a file named "audio_platform_info.xml" with text editor of your choice .
Now go to the bottom of the file you will see </acdb_ids> , you need to add the below line before/above that </acdb_ids>
Click and add this line
<device name ="SND_DEVICE_IN_VOICE_DMIC" acdb_id = "100"/>
Now just save the file and exit the root browser
Reboot the device now. As soon as it boots up you may check thr mic quality if its better now or not
If you're still not satisfied with it then you may follow one more step. This will turn off the voice cancellation ( it could cause echo sometimes to the listener)
For this open root browser and navigate
Root > system > build.prop file
Open it with any text editor.
Look for following lines
persist.audio.fluence.voicecall= true
persist.audio.fluence.voicerec= false
As soon as you find these lines make true to false and it should look as follows
persist.audio.fluence.voicecall=false
persist.audio.fluence.voicerec=false
Save the file and exit.
Reboot the device and check if it's working or not.
As of your wife, there is only one common fix for that issue: switch from 'default charge' mode during night to 'super charge' one, and gotta charge longer in this mode, usually it helps them to switch from 'nagging mode' to 'silence mode' for a while. Apply this fix as often as she slips from 'silence mode', because there is no permanent fix for this issue.

End of the story:
I bought for a few € the miniboard with the USB connector and the microphone, replaced the old one and the phone is working again.
The not clear behavior of the microphone with the various Android installations was due to it starting to malfunction. The last days It was always completely silent.
Thanks to all for the help and the suggestions, I learned some new things.

leodp said:
End of the story:
I bought for a few € the miniboard with the USB connector and the microphone, replaced the old one and the phone is working again.
The not clear behavior of the microphone with the various Android installations was due to it starting to malfunction. The last days It was always completely silent.
Thanks to all for the help and the suggestions, I learned some new things.
Click to expand...
Click to collapse
Hi,
so does that mean, it was a hardware issue?
my dads Samsung Galaxy M21 has exact same problem

bushu16 said:
Hi,
so does that mean, it was a hardware issue?
my dads Samsung Galaxy M21 has exact same problem
Click to expand...
Click to collapse
Yes, hardware damage

Pixel 4XL Face Unlock

I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!

Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.

Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.

Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.

v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.

@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.

@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.

I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL

The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.

sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.

The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working

Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?

@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.

Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.

@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM

this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(

Question Redmi Note 10 Pro - No sound at all - Mic doesnt work. Screen Recorder doesnt work.

My RN10Pro is experiencing a rather serious issue. I was about to open a game (Fate Grand Order), it freeze then crashed. Then no sound was playing at all on any apps (youtube, music ,etc). It also cant record audio from mic. No audio from calls. Can someone help?
Other Symptoms:
- Dolby Atmos is stuck in Toggle ON. I cant turn it off. I always left it OFF before the problem. I havent turned it on before.
- Going into sound effects in settings result in crash and error.
- Poweramp music player reports "No Audio Device"
-ALL APPS dont have any audio.
- No audio comes out even if I plug in my Earphones with a mic.
- Plugging my phone to charger doesnt create the Charge sound that it usually do.
METHODS THAT I HAVE ALREADY TRIED.
- Factory Reset - I have tried 2 factory resets already. Both didnt work
- Restarted phone multiple times - Still no sound
- Tried Safe Mode - No luck
- Cleared cache from Boot Screen. No luck
Any help pls T_T

Sepepe_GCL said:
My RN10Pro is experiencing a rather serious issue. I was about to open a game (Fate Grand Order), it freeze then crashed. Then no sound was playing at all on any apps (youtube, music ,etc). It also cant record audio from mic. No audio from calls. Can someone help?
Other Symptoms:
- Dolby Atmos is stuck in Toggle ON. I cant turn it off. I always left it OFF before the problem. I havent turned it on before.
- Going into sound effects in settings result in crash and error.
- Poweramp music player reports "No Audio Device"
-ALL APPS dont have any audio.
- No audio comes out even if I plug in my Earphones with a mic.
- Plugging my phone to charger doesnt create the Charge sound that it usually do.
METHODS THAT I HAVE ALREADY TRIED.
- Factory Reset - I have tried 2 factory resets already. Both didnt work
- Restarted phone multiple times - Still no sound
- Tried Safe Mode - No luck
- Cleared cache from Boot Screen. No luck
Any help pls T_T
Click to expand...
Click to collapse
Which ROM? TWRP, rooted unrooted?

Laptapper said:
Which ROM? TWRP, rooted unrooted?
Click to expand...
Click to collapse
MIUI 13 Global 13.0.8, No TWRP, Unrooted.
Edit: Im going to bed, I will be replying tomorrow. For anyone who tries to help, thanks in advance. I hope you guys can help me with this T_T

Sepepe_GCL said:
MIUI 13 Global 13.0.8, No TWRP, Unrooted.
Edit: Im going to bed, I will be replying tomorrow. For anyone who tries to help, thanks in advance. I hope you guys can help me with this T_T
Click to expand...
Click to collapse
As long as you are on seller's OS, try also to give them a call or write to them. This way you'll get both "official" assistance there and FOSS here.
If the official does not help, you may always try to unlock the bootloader and to install the same (but debloated) Miui OS or try a free one.
Hope you manage to resolve the issue. We all know how time and mind consuming are all these troubles. Good luck!

runtime64 said:
As long as you are on seller's OS, try also to give them a call or write to them. This way you'll get both "official" assistance there and FOSS here.
If the official does not help, you may always try to unlock the bootloader and to install the same (but debloated) Miui OS or try a free one.
Hope you manage to resolve the issue. We all know how time and mind consuming are all these troubles. Good luck!
Click to expand...
Click to collapse
Generally speaking, which custom ROM is the most bug free or stable one? I have a feeling that this is a software/OS problem due to how the nature it occurred.

Sepepe_GCL said:
Generally speaking, which custom ROM is the most bug free or stable one? I have a feeling that this is a software/OS problem due to how the nature it occurred.
Click to expand...
Click to collapse
There is no one and sole answer to your question. It depends on the hardware components, on how you use your phone and even on the sequence of installations.
For example, I unlocked bootloader on my Redmi and installed CrDroid which had a very good battery run time. A couple of months later I had to reinstall the OS because after OTA update I lost root and could not regain it via usual tricks. So, clean installed the same CrDroid. And now the battery consumption is visibly higher. Why? No answer. I have to search for new tricks.
So, even if you found an OS which fits your needs, you are not guaranteed to pass next years in a small country house contemplating roses.

Hello!
Having the exact same problems. Phone became defective on its own. Never rooted or flashed. All of a sudden Adobe Audio is stuck on and no audio, no recording or playing videos and no mic function. I can only write and browse with the phone. If anyone found a solution other than a motherboard swap let me know.

Sepepe_GCL said:
My RN10Pro is experiencing a rather serious issue. I was about to open a game (Fate Grand Order), it freeze then crashed. Then no sound was playing at all on any apps (youtube, music ,etc). It also cant record audio from mic. No audio from calls. Can someone help?
Other Symptoms:
- Dolby Atmos is stuck in Toggle ON. I cant turn it off. I always left it OFF before the problem. I havent turned it on before.
- Going into sound effects in settings result in crash and error.
- Poweramp music player reports "No Audio Device"
-ALL APPS dont have any audio.
- No audio comes out even if I plug in my Earphones with a mic.
- Plugging my phone to charger doesnt create the Charge sound that it usually do.
METHODS THAT I HAVE ALREADY TRIED.
- Factory Reset - I have tried 2 factory resets already. Both didnt work
- Restarted phone multiple times - Still no sound
- Tried Safe Mode - No luck
- Cleared cache from Boot Screen. No luck
Any help pls T_T
Click to expand...
Click to collapse
Same here , every application that use sound , voice , it will freeze n not responding. Guess it cause by miui update ..ahh... Do u solve it, it been 72 hours now...this phone might fly into the wall soon

Mattfun said:
Same here , every application that use sound , voice , it will freeze n not responding. Guess it cause by miui update ..ahh... Do u solve it, it been 72 hours now...this phone might fly into the wall soon
Click to expand...
Click to collapse
Nope bro, still havent solve it. Based on some research I have done, the root cause might be a faulty mainboard. . I just reverted to using my old Samsung A50 for the meantime.

same is happening with me from yesterday

Did anyone found fix or visited service centre? Also how and when did your device having audio issues @Mattfun @Sepepe_GCL @la98kraja

Same with me...
The front cam stopped working on 1st July,
Since last 4 days (29th September), the mic and speakers are not working.
In fact, the phone doesn't even boot normally, only safe mode works.
In safe mode too, cam, mic and speakers don't work.
I took a bug report and sent to Feedback team. No response since 2 days...
How effed up am I?

Did anyone try qfil rom ?

I emailed xiaomi italy. i had bought the phone 1.5 years ago and this is obviously a factory defect. Since moving houses and everything i have lost the original box of the phone with the bill in it and i dont have proof of insurance even though xiaomi told me through emails that my imei shows that the phone is under warranty but they wont take it in without a bill from the shop i got it from. the shop now post covid has closed bcs of the general crisis Italy is in.
i believe it strongly to be a motherboard or speaker problem. a redmi note 10 pro now flies around 150-200 euros new and a motherboard costs 100 euros. i can fix it myself because i am technically able but i dont think it is worth it. i bought an iphone 11 pro max and im keeping this audioless phone that i cant do much with either until someone finds another fix for it or its battery swells and damages the frame hahahah. might work well as a tinder only phone to hide from your gfs too ahahahahha.
my phone just did the audio thing on its own. one day it was working fine then the other day:
Dolby atmos stuck on
no audio from anything
every video or app that uses audio freezes. only rear camera works but sometimes decides it doesnt want to and only for taking pictures.
reboots became instantly no joke 10 minutes long. like to the point i was worrying it was never going to boot. all this 2-3 weeks before i did my first comment on this thread.
i feel like this is a disservice. xiaomi should aknowledge this problem and maybe take back all the defective redmi note 10 pros and even if they ask me to pay extra for a redmi note 11 pro or 12 i will but take at face value what i paid for their phone already and offer me a solution. i was able to take care of it but what about people who this is their only phone and have no possibility of bying another one a snap of their fingers just because their main is broken. i always used xiaomi products. love their phones and everything and i understand this is a factory defect that might happen to 0.01% of all redmi note 10s but still own up to it as a company.

I have the same problem and when I sent it to the service they said that the motherboard needs to be changed. It's really silly. A phone should not break where it stands!

Sepepe_GCL said:
Nope bro, still havent solve it. Based on some research I have done, the root cause might be a faulty mainboard. . I just reverted to using my old Samsung A50 for the meantime.
Click to expand...
Click to collapse
Yeah ...so do i ... An update cause faulty mainboard ... And it our problem cause we updated it... Damnnn .. almost a month without sound now ... Fork

Mattfun said:
Yeah ...so do i ... An update cause faulty mainboard ... And it our problem cause we updated it... Damnnn .. almost a month without sound now ... Fork
Click to expand...
Click to collapse
Did you've tried a clean flash with fw and another ROM? For example los 19

Mattfun said:
Yeah ...so do i ... An update cause faulty mainboard ... And it our problem cause we updated it... Damnnn .. almost a month without sound now ... Fork
Click to expand...
Click to collapse
It could be the driver in update as well. Try another ROM like @Laptapper said

pavan nayak said:
Did anyone found fix or visited service centre? Also how and when did your device having audio issues @Mattfun @Sepepe_GCL @la98kraja
Click to expand...
Click to collapse
Since 26/9 , still not fixed yet.

pavan nayak said:
Did anyone found fix or visited service centre? Also how and when did your device having audio issues @Mattfun @Sepepe_GCL @la98kraja
Click to expand...
Click to collapse
They said it might be causes by motherboard and they want to change it , it cost the price of the phone tho . Ah , all this happened by an update..no more xiaomi .. thank you all