I ended up with what I thought was a broken earpiece speaker: During calls, I could not hear anything through my earpiece, but putting the call to speakerphone worked.
Also, all media palyback was mute (youtube, VLC, audiobook player ...). Headphones continued to work. I played around with all the audio settings, nothing.
So I assumed a broken earpiece and ordered a new one. I took my MI5 apart and replaced the earpiece, but nothing changed: Earpiece stayed silent, headphones and speaker worked.
By that, I already factory reseted and flashed new LOS builds and firmwares back and forth. No change.
Yesterday I came up with the idea to write an app that routes all audio to my surround speaker ... I researched the Playstore to check if anything like that already existed, and I came up with an app called SoundAbout which I used to route all audio to the speaker instead of the earpiece.
So far so good.
But even better: I configured it to route all media sounds from "let app decide" to "earpiece", and to my surprise it worked!
Setting it back to "let app decide", I dont hear anything: The setting "earpiece" makes it working again.
My question is: The issue is clearly software related, somehow I managed to break my audio routing, which survives flashing new builds and even factory resets as far as I can tell.
I am on official LOS 20170425, 7.4.14 firmware, official su addon. No custom kernel, no magisk or any battery saving trickery ...
Does anyone have an idea what I can check to fix my audio routing again? Anyone experienced something similar? I will buy that SoundAbout app because it just saved me from buying a new MI5/MI5s/MI6, but I would still like to understand how I managed to break my audio routing like this. The fact that it survivd factory resets makes me think it might be firmware related (I am using the ones from here: https://forum.xda-developers.com/mi-5/development/tool-flashable-firmware-twrp-easy-t3474898) ...
Ok, after several months, I finally figured it out.
It was not a firmware issue after all, but hardware: My 3.5mm audio headphone jack was blocked, meaning the trigger for detecting a headphone was jammed.
The phone constantly thought a headphone was inserted, and so switched to headphone mode, trying to play all sounds and media to the headphone audio port where nothing was present.
Thats the reason why e.g. SoundAbout was a working workaround: It simply ignores the headphone-inserted-trigger and forces all audio to speaker or earpiece.
I found out about the b,ocked trigger with another tool that simply shows if a headphone was inserted or not, and that tool constantly showed that something was inserted.
Unfortunately you cannot get a replacement headphone-jack for the MI5 (redmi and mi4s are available, but no mi5 for some reason), only the whole mainboard for 140$. But I took my MI5 apart anywayto see if I can get that trigger unstuck (tried a small needle and qtip before, but didnt work). I could not get it unstuck, and instead removed the whole headphone jack from my MI5 mainboard, meaning I actually broke a small piece of my mainboard out ... but it worked nontheless: Now that the audio port is gone, my phone no longer thinks a headphone is present, and all audio issues are gone.
Now that I removed the audio port I obvously can no longer use my headphones, so I ordered an usb-type-c-to-audio-adapter for 5$ (after checking that xiaomi usb-type-c headphones cost 50$, which I consider waaaayy too expensive).
So, if anyone has a similar problem where it looks like your phone doesnt play any audio, check out "headset toggle" from the play store to see if the headphone-trigger is broken.
Related
Hello, I am a new user here.
I have a strange problem with my Bolt where at times the rear speaker plays all streams (alarm, notification, ringtone, media, etc.) so quietly that I have to put my ear directly next to the speaker to hear anything. At random times the speaker decides to play at normal volume again. I do not really hear a crackling sound so it seems the speaker is not blown.
The issue occurred when I was using SynergyROM for Thunderbolt r264, but the issue still occurs when I do a nandroid restore to a ROM I flashed previously when the problem did not occur. I am now using CyanogenMod 7.1.1 for Thunderbolt and yes, I am rooted.
The headphone jack works fine, so I'm guessing it has nothing to do with the system volume control. However, the problem sometimes occurs as soon as I plug in my headphones and then unplug them.
Does anyone know what I can do besides taking my phone to Verizon (my carrier) or a phone repair shop to fix this?
I have this same problem. I would also like to know what the cause is. It is very annoying because most of the time, I cannot hear my phone ring.
I think this may have something to do with the system thinking that headphones are still plugged in. I am running a Theoryrom based off of CM7 and if I go into the CyanogenMod settings in the sound menu and check the boxes for notifications, ring tones, and alarms to always play on speaker, all of a sudden the speaker volume seems to have improved. Something you may try. If it happens again on mine (which it will) I will see if I can figure out what the problem is.
Nevermind, it went back to being quiet, and that doesn't seem to fix it. Must have been a fluke.
It seems like there is no indication of when it will happen. Is it a hardware issue or an issue with the Android system and plugging in a headset?
My initial guess would be that it is a hardware issue. I have tried flashing new and different ROMs ranging from Sense base DasBAMF roms to AOSP based liquid roms and the problem persists even after a flash, which to me would indicate that it is not an issue with the Android system.
The last time it came and went for me had nothing to do with plugging or unplgging a headset. I have no idea what is going on.
Ok, so my speaker came back this morning, and I did notice one potentially related thing when it happened. Just before it came back, the DSPManager application force closed. I wonder if something is wonky with that program. If you are still having issues, could you try to force close, uninstall, or freeze (using Titanium) the DSPManager application to see if your speaker volume comes back?
Update: Nope, not it. Must be hardware.
The strange part about this problem is that nothing wrong seems to be happening with the software when the sound comes back on. Also, I have to play music constantly in order for the sound to come back on. It doesn't seem like the speaker is blown out... there is no crackling sound. The sound is just really really quiet.
Alright, I finally decided to replace the speaker unit inside my phone because it would no longer go back to the original volume. It seems my hunch was right. The new speaker is working perfectly now.
Hi guys,
I just got an VS985 and I'm already fighting with him.
I got the following issue: Everytime I try to make a call, the "headphone" icon will appear in the notification area and the call will work, but witout any sound. If I put speaker, I'll be able to listen without any problem, but disabling will have the previous result.
After the call ends, the icon will remain in the notification area.
If I try to call with headset, 0 problem, everything ok. The issue appears to be that the phone doesn't detect when a headphone is actually connected or the headphone jack is faulty, but I'm unsure.
I've heard that the G3 has general issues with the headphone jack, but mainly on the Pause button working by its own, not the same as this.
I tried updating to 5.1 (35B stock) and the result is the same. Whatsapp calls show the same behavior. There's any known fix for this? (the headphone hole is clean) If I replace the headphone jack might solve the issue? (I have no problem replacing it, I repair cellphones).
Thanks for your time!
BB
Well, I ended up opening and apparently it was refurbished and the contacts of the headphone jack werernt that great, also there was some double sided tape on them.
Clean it, forced the contacts a little bit more open and voila everything works.
btw, strange system for the jack contacts.
Greetings. Phone appears to be stuck on headset mode, even when headset is not connected. As a result, the device's main speaker does not produce any sound while the front speaker does not function during a call. As a workaround I am using the SoundAbout app to redirect audio to its respective speakers, however I would love a have a more permanent fix. I've tried 2 different roms and the problem persists on both. (Umang96's Unofficial rom with Radon kernel and, what I'm running now, the latest official nightly for my device with stock kernel). If a headset is conencted it works flawlessly, so I'm not sure if it's a hardware problem. I tried cleaning the audio jack using a cotton bud, but it didn't help. Can someone point me to a solution for this ? Thanks for your time in advance.
ps: My device is the Kenzo variant.
That's funny, I had the same problem this morning. Over here I poked inside the audio jack with a tooth pick and blowed compressed air it. It seemed tout have fixed it, for now anyway. (It just suck I wiped my whole phone before trying this)
Hey guys,
yesterday I installed the 14.1-20180719-NIGHTLY-h850 version of LineAgeOS on my phone.
Everything worked fine, but then I found a bug.
WhatsApp voice mails and any other voice record doesn't have any sound except an cracky sound at the beginning, after that, theres no sound.
The strange thing is, when I record a video with any camera App, theres normal mic sound, maybe a little bit crackling.
Do you know how to fix this?
PS: If I connect a headset, I get very strange Sound in WhatsApp voice mails/records etc and no Sound in Discord.
Also WhatsApp and Snapchat (no more tested) don't record the sound with Headset mic rather the normal phone-mic.
Ok guys, after flashing it new... a few times... I got normal mic performance when no Headphones or Headsets are connected.
If so, the mic level is very, very, low.
Any ideas?
My mic doesnt work regardless if I was on stock, downgraded version, custom ROM, etc. I dont know what to do. I do have the same symptom as yours tho where when I record, there is a few pops at the beginning then just silence
I got the replacement module for the g5 and not even that fixed it. I am stumped of how to fix this issue.
EDIT: I just now found out that after taking out the motherboard, there was a red sticker covering some golden connectors, after taking that off fixed it. No idea why there was a red sticker there but please check and if it is there then take it off. itll be on the other side of the motherboard..
Hello! I've searched everywhere for answers and fixes about my problem, but unfortunetly I didn't find anything.
Problem 1: Since I installed the latest update to Oreo [RNE-L21I 8.0.0.332 (C432)] I have problem with the stock EQ, and others from the Play Store - when bass boost is turned on, the sound from headphones is awful. When bass boost is turned off this issue disappears, but is annoying since I really enjoyed the sound before installing this update. I tried different pairs of headphones, different EQ apps, restarting, Hard resseting, etc. no fix unless I turn off bass boost.
Problem 2: When I connect my phone via AUX cable to my car, home subwoofer or anything like that music play normally for 2-3 mins then somehow volume is turned down (and when I check is turned to the max, so it's not that the volume is turned down to protect the hearing) and the only fix is to get out the cable and insert it again. This is also really annoying, because I can't listen to one song normally. Yes, I tried different cable (like I already said it happens to different devices), hard resseting and etc. And yes, the problem is still on when I use the stock music app, YouTube and other apps, so it's not an issue with the app. I also found out that my dad has the same issue with his Huawei Y5 II.
I really look forward to any fix since I really enjoy this phone, it's been only a month since I bought it and yes, it is in warranty but I want to try anything that I can do to fix this before I send it.