Get it? The title is a Star Wars reference. As in developers are Jedi? Like in the movie? Nevermind.
I have been having a strange audio bug recently. I flashed RC Mix Runny v1.0 through to v1.4 and each subsequent ROM version did exactly what it should. No issues that weren't listed on the thread.
Then I flashed Runny v1.5, followed by (after the ROM had booted twice) a theme I made on UOT Kitchen. A few days afterwards, when making a phone call, I couldn't hear the phone ringing through the phone's speaker. Nothing. That's the bug.
This only applies to phone calls (or at least the speaker normally used for phone calls). When I select 'speaker phone' the rear speaker kicks in and I can hear the phone call just fine, though a little loud when walking around in public.
The headset also works perfectly.
I flashed RCMix3d 3.5 v1.0 today - no themes this time in case it was the cause last time. The ROM boots up just fine, everything seems perfect but when I go to make a phone call the same bug presents itself. Meaning it's most likely a bug I have caused, not a bug in a ROM.
But what did I do?! Has anyone heard of this behavior before? Could it be radio/RIL related?
If anyone can shed a little light, I would appreciate it greatly.
Max-E-Moose said:
Get it? The title is a Star Wars reference. As in developers are Jedi? Like in the movie? Nevermind.
I have been having a strange audio bug recently. I flashed RC Mix Runny v1.0 through to v1.4 and each subsequent ROM version did exactly what it should. No issues that weren't listed on the thread.
Then I flashed Runny v1.5, followed by (after the ROM had booted twice) a theme I made on UOT Kitchen. A few days afterwards, when making a phone call, I couldn't hear the phone ringing through the phone's speaker. Nothing. That's the bug.
This only applies to phone calls (or at least the speaker normally used for phone calls). When I select 'speaker phone' the rear speaker kicks in and I can hear the phone call just fine, though a little loud when walking around in public.
The headset also works perfectly.
I flashed RCMix3d 3.5 v1.0 today - no themes this time in case it was the cause last time. The ROM boots up just fine, everything seems perfect but when I go to make a phone call the same bug presents itself. Meaning it's most likely a bug I have caused, not a bug in a ROM.
But what did I do?! Has anyone heard of this behavior before? Could it be radio/RIL related?
If anyone can shed a little light, I would appreciate it greatly.
Click to expand...
Click to collapse
Please search before opening a new post as I have seen this pop up alot the past few days with that rom. I would look in the roms thread
I will search more thoroughly. Apologies for any infraction.
Cheers for pointing the way.
Max-E-Moose said:
I will search more thoroughly. Apologies for any infraction.
Cheers for pointing the way.
Click to expand...
Click to collapse
While you are searching for hours for a solution, download a different ROM (other than RCMix) and find out if it is really a bug or some hardware issue. And while you wait for the download and flash, keep searching
hohinder said:
While you are searching for hours for a solution, download a different ROM (other than RCMix) and find out if it is really a bug or some hardware issue. And while you wait for the download and flash, keep searching
Click to expand...
Click to collapse
Thanks for your advice. I heeded it!
I flashed Black Ice [AOSP] to see if it was still persisting. It is.
Seems like it's a hardware problem. I was hoping it wasn't. I didn't want to have to pay to fix it!
Ta for the help!
try changing the radio or kernel see if it helps
SOLVED
NOT SOLVED
rakinisbat said:
try changing the radio or kernel see if it helps
Click to expand...
Click to collapse
I was holding back on changing the radio because I don't like higher risk of bricking. Having done it in the past though, I said it was worth a shot before I blame the hardware entirely and hand over money to fix it.
I had been using radio 26.09.04.11 and it's matching RIL with every ROM I tried.
Once changed to radio 26.13.04.19_M and it's corresponding RIL and the problem was erased. I can hear phone calls on the phone speaker again. (Like normal folk!)
Thanks for the push rakinisbat, I needed it!
Edit: NOT SOLVED. The problem has re-surfaced. I have made absolutely no changes to the system since it started working. I am now going to pay someone to take a look and will report back with results.
Definitely not solved.
This problem with the receiver not working has not gone away.
I have tried ignoring it for the last while and just using the speakerphone on a low volume - not ideal but workable.
A few days ago I changed ROM - curious to try out ICS. I load up the new ROM and a while later, accidentally forgot to put a call I was making onto speakerphone and suddenly the receiver is working again - JOY!
Now, two days later, the receiver is not working again.
I have pry tools now and would happily change the receiver, but this recurring trend of it working for a spell after a new ROM is flashed leads me to believe this is more software related than hardware.
If anyone has ANY ideas or thinks they could help (if I provide a logcat to them or something) then please PM me or respond to this thread.
Everything works fine for me...never experienced this .....check your audio settings....and why you running such an old version??
Sent from my Desire HD using xda premium
harshrocsu;20112881why you running such an old version??[/QUOTE said:
The last time I changed to that radio, my audio bug was fixed (temporarily).
I will update to the new radio (12.65.60.29_26.14.04.28) I saw mentioned a few days ago and see if it changes anything - though I doubt it.
I have done a fair bit of research on this and it is not as uncommon as I thought it was a few months ago. It seems to have happened to the HTC Desire, Desire S and Desire HD - but not en mass. In every case, the phone was working fine, then came intermittent receiver audio, then receiver audio gone altogether.
I have not heard of one working solution, though I have had some helpful people lend an ear!
Click to expand...
Click to collapse
You say the problem is solved for a while when you flash a new ROM. Is there a possibility that a certain app that you install/restore that maybe messes with the speaker?
Just a thought..
if4ct0r said:
You say the problem is solved for a while when you flash a new ROM. Is there a possibility that a certain app that you install/restore that maybe messes with the speaker?
Just a thought..
Click to expand...
Click to collapse
An avenue I had not gone down. I have been restoring mostly the same apps for ages.
Thanks for the idea. I will do a backup and then a fresh install tomorrow (I'm at work) and check. Will report back afterwards.
Ongoing audio issue
I have fully wiped the phone and re-installed a ROM twice now (ICS both times, I know this problem acts the same with GB). I didn't install any apps for a while and had audio in the receiver for phone calls.
The first time I wiped it, I had audio back so decided to install apps from the market - one at a time and test the receiver by ringing the house number after each is installed. I got distracted (it was late) and when I next picked up the phone, audio was gone.
Second attempt, this time stay vigilant. I fully wiped the phone, installed a ROM, and got to work on installing the apps again. I installed a few apps, which I will list here, and audio disappears again.
Installed apps:-
Dictionary.com
Dropbox
Earth
Es File Explorer
Facebook
Goggles (I dunno why, the camera isn't even working - habit maybe)
Google Sky Map
Google+
Messenger
Moon+ Reader Pro
MX Video Player
Streetview For Google Maps
Sugarsync
Tumblr
Twitter
XDA
To my knowledge, apart from MX Video Player, none of the rest these apps should have any effect on the audio.
Today I am going to wipe it and not install any apps for the next 24-48 hours and see if the audio still disappears.
Tune in next time to see if the problem makes my brain crack in two.
Max-E-Moose said:
I have fully wiped the phone and re-installed a ROM twice now (ICS both times, I know this problem acts the same with GB). I didn't install any apps for a while and had audio in the receiver for phone calls.
The first time I wiped it, I had audio back so decided to install apps from the market - one at a time and test the receiver by ringing the house number after each is installed. I got distracted (it was late) and when I next picked up the phone, audio was gone.
Second attempt, this time stay vigilant. I fully wiped the phone, installed a ROM, and got to work on installing the apps again. I installed a few apps, which I will list here, and audio disappears again.
Installed apps:-
Dictionary.com
Dropbox
Earth
Es File Explorer
Facebook
Goggles (I dunno why, the camera isn't even working - habit maybe)
Google Sky Map
Google+
Messenger
Moon+ Reader Pro
MX Video Player
Streetview For Google Maps
Sugarsync
Tumblr
Twitter
XDA
To my knowledge, apart from MX Video Player, none of the rest these apps should have any effect on the audio.
Today I am going to wipe it and not install any apps for the next 24-48 hours and see if the audio still disappears.
Tune in next time to see if the problem makes my brain crack in two.
Click to expand...
Click to collapse
I had exactly the same issue. After rooting my desire HD I installed ARHD 6.3.1 and it was working very fine until I installed the ICE HD theme for ARHD 6.3.1. Sorry, no disrespect to the theme author but I was not able to hear anything through Phone speakers after installing this theme. This is what I did to solve this issue,
1- Use Superwipe to clear everything using ClockworkMod recovery.
2- Install the STOCK 1.32 PD98IMG.zip from here. Put it in your SD card, Flash is using the HTC Stock Recovery (It will detect it automatically). Remember that the Kernel and Radio are inside this ZIP file so you need not to install anything else.
That's it. you are back to old stock ROM and now you must be able to hear you phone speakers. If not, switch off your phone for few hours and then turn on. (I know switching off and on sounds silly but it worked for me). You can install any custom ROM after that rooting again.
kaydee7902 said:
I had exactly the same issue. After rooting my desire HD I installed ARHD 6.3.1 and it was working very fine until I installed the ICE HD theme for ARHD 6.3.1. Sorry, no disrespect to the theme author but I was not able to hear anything through Phone speakers after installing this theme. This is what I did to solve this issue,
1- Use Superwipe to clear everything using ClockworkMod recovery.
2- Install the STOCK 1.32 PD98IMG.zip from here. Put it in your SD card, Flash is using the HTC Stock Recovery (It will detect it automatically). Remember that the Kernel and Radio are inside this ZIP file so you need not to install anything else.
That's it. you are back to old stock ROM and now you must be able to hear you phone speakers. If not, switch off your phone for few hours and then turn on. (I know switching off and on sounds silly but it worked for me). You can install any custom ROM after that rooting again.
Click to expand...
Click to collapse
Thanks so much for getting on to me, I have been hoping that someone out there solved this issue and might read this little thread!
I will be following your advice today and will report back.
Solution seems good so far!
I'm not going to jump the gun again and say that it is definitely solved but my audio came back!
I did what you said, reverted everything back to stock. When it loaded up Froyo and for the first while, the receiver wasn't working. I set about rooting, Radio S-Off, ENG S-Off, adding CWM etc.
About three hours later (I didn't actually leave the phone off, I reset it a lot though) the audio returned to the receiver!
I'm delighted but remain skeptical as it has come back to life and then died again so many times before.
I want to believe!!!... So I remain hopeful. Time will tell.
It fixed itself...(!)
See post below
Absolutely positively finally fixed.
Thanks to everyone for their help in trying to solve this issue.
I replaced the broken receiver with a new one I got from eBay (along with prytools for under €10) and this issue is completely fixed.
What had happened, if anyone is interested, was that the inside of receiver housing and the output on the receiver itself had been clogged with dust, tiny hairs and the like. That must have shorted the tiny thing.
Lesson learned. Get stuck in.
Related
I dropped my phones while skiing and some snow must have got in because now, when making or receiving calls, I can not hear the other side and they can't hear me unless I use speakerphone.
No media sounds play any more, however the phone notifications and alarm still work. I understand that perhaps the media speaker has broken but why is the microphone still working only in speakerphone mode?
Is there an independent microphone/speaker set for speakerphone?
There is nothing else wrong with the phone.
[EDIT] Another side effect is that the Google voice search was not working.
Install this: https://market.android.com/details?id=com.seb.audiotoggle
I think it will actually solve your problem. It did for me when the exact same problems started to bother me today after skiing as well!
You need to start it at every boot as it don't stick between reboots. Consider using a startup manager.
The problem seems to be a mix of hardware and software in the headphone jack, but I have not examined it much yet.
Thanks for the reply. The app you suggest should be very useful and I will download it anyway. However, this to say that the phone had fixed itself this morning.
I put the phone on charge overnight, and this morning, it asked for my sim unlock code, which I thought was very strange! But I entered the code that I had received from my network provider and now everything is working as it should.
It was probably something do with the remaining water inside the phone or possibly the cold temperatures.
Good to know! Maybe my phone fixes itself during the night as well
Still working?
Has the issue remained fixed for you? I ask because I have the same thing - the symptoms are that I can't hear anyone and they can't hear me, all media sounds are off, and the phone can't hear me.
I ran Tasker to monitor things, and the phone keeps thinking I plugged in headphones (with a mic), so that explains all the behavior. Running the headphone toggle app works temporarily - sometimes only a few seconds.
After doing a factory reset, sound would still come and go. With my Nandroid backup back on, same thing. I want to return it, and so I put everything back to stock, and noticed that now the bootloader is locked again, the issue is gone (for now).
I just wanted to keep the discussion going because I can't even tell if it's hardware related or not, and other people probably have this problem, and it takes some snooping to realize it's the headphone connector (vs sound settings, speaker issues, etc.). It could be a short (my guess) but now that it's working today I can't return it as the tech would probably claim nothing's wrong. I also already used up the one return my stupid carrier allows, so I'd rather fix it myself if it's software-related, instead of sending it out for repair.
I still have this problem, even after cleaning the headphone plug. My guess is that this is a hardware problem affecting only a few. It makes the phone pretty much useless, as you can't hear the other part talking, so I made myself a software fix that resets the sound routing the the default speaker on every boot and incoming and outgoing call. I guess I can share the apk-file if anyone is interested.
Give it a try: ----
Can release source if you are interested, but I am currently in a car getting ready for a ski weekend
I am also having this problem with my Galaxy Nexus. I would be interested in seeing the source, if you are still up for releasing it.
VingInMedina said:
I am also having this problem with my Galaxy Nexus. I would be interested in seeing the source, if you are still up for releasing it.
Click to expand...
Click to collapse
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Thanks for posting the source. I was able to work with it fine.
I've replaced my Nexus with a new one under warranty. Hopefully this one won't have the same problem.
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
Worked for me. Still hoping that Negri will replace my phone though.
Melhouse said:
I still have this problem, even after cleaning the headphone plug. My guess is that this is a hardware problem affecting only a few. It makes the phone pretty much useless, as you can't hear the other part talking, so I made myself a software fix that resets the sound routing the the default speaker on every boot and incoming and outgoing call. I guess I can share the apk-file if anyone is interested.
Can release source if you are interested, but I am currently in a car getting ready for a ski weekend
Click to expand...
Click to collapse
Thanks for releasing this! It works great!
I was going out of my mind trying to figure out what was going on. I was unlocked, rooted in stock 4.02 when this started to happen. I thought it was bad signal quality because i only noticed it when I stopped being able to make calls and use voice dialer. I only listen to music with a headset, so never even noticed that it wasn't working with the speaker til I tried to play a youtube video.
I actually upgraded to stock 4.04 with new FA2 radios and thought I had cured it, only to have it happen again. When I read this I tried resetting all my notification sounds (Handcent, et al) hoping somewhere there was a conflict, but still couldn't find it. I'm using NOVA launcher - wonder if there's something in there?
Anyhow, I gave up since your audiojack.apk works great! Someday when I have time I'll go back to troubleshooting to see where the problem is coming from.
Thanks again!
Works temporarily
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
This worked, but the OS will eventually think the headphone is plugged in again and I have to press the "Force Speaker phone" button again. I wonder if there is an event that is fired every time the OS thinks the headphones were plugged in? If so, that event can be captured and code could look to see if the headphones are turned off by the user and ignore the event.
Wired Headphone Routing Fix
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
If you want the same routing fix as audiojack but have it done automatically in a service try this.
There is an issue with a lot of Galaxy Nexus where the OS thinks the headphone is being plugged in and unplugged on its own. Try this free application to resolve it:
Search Google Play for Wired Headphone Routing Fix
The birth of SoundAbout...............................
dmwoods said:
If you want the same routing fix as audiojack but have it done automatically in a service try this.
There is an issue with a lot of Galaxy Nexus where the OS thinks the headphone is being plugged in and unplugged on its own. Try this free application to resolve it:
Search Google Play for Wired Headphone Routing Fix
Click to expand...
Click to collapse
Nice! What events do you listen for?
I have another problem. When i'm in a call and i swich to speakers the person i speak can't here me...if i switch back he can here me again. I don't know what is the problem i don't think that are two microfhones one for speakers mode and one for normal mode...Maybe a software problem but i wipe and flash another rom and kernel i tryed 2 or 3 roms and kernel and i have the same issue. Now i'm on AOKP B32 with Franco Kernel 135. Anyone have this problem?
android.intent.action.HEADSET_PLUG
Melhouse said:
Nice! What events do you listen for?
Click to expand...
Click to collapse
android.intent.action.HEADSET_PLUG
6jaipur6 said:
I have another problem. When i'm in a call and i swich to speakers the person i speak can't here me...if i switch back he can here me again. I don't know what is the problem i don't think that are two microfhones one for speakers mode and one for normal mode...Maybe a software problem but i wipe and flash another rom and kernel i tryed 2 or 3 roms and kernel and i have the same issue. Now i'm on AOKP B32 with Franco Kernel 135. Anyone have this problem?
Click to expand...
Click to collapse
I am having the exact problem that you are. I am running a different ROM though, but the same issue.
ddub1 said:
I am having the exact problem that you are. I am running a different ROM though, but the same issue.
Click to expand...
Click to collapse
Have you solve your problem?
can't install the audiojack.apk because I'm still on Android 4.0.2 and min SKD is 15, could anybody port it to sdk 14?
Melhouse said:
See attachment for source, I also added a compiled apk file in the zip-file. You can open the project in Eclipse if you want.
Click to expand...
Click to collapse
Worked for me on Verizon GN. Verizon already has a replacement on the way... guess I should've done more extensive searching for a fix first!
Spoke too soon. Seems as though the screen doesn't shut off while I am on a call. Guess I'll give the replacement a try after all.
So i installed 7.2.0RC1 on my desire and it worked perfectly for 2 days but i've noticed this morning that when im getting calls or messages the phone isn't making a noise and notifying me of this.
I checked that I wasnt accidently on silent and I wasnt, so checked volumes, all ok, and then I decided to look at the ringtones and select a different one and where each one is supposed to give you a little preview of the tone im getting nothing.
Im really at a loss, has anyone else had this problem or knows how to solve it, its handy being made aware when someones trying to contact me
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
stankyou said:
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
Click to expand...
Click to collapse
Tried rebooting and still nothing off previews or anything, its just kinda weird for a RC for this to happen, might have to go back down to 7.1.0 until the bugs are ironed out, thank god for nandroid.
Still might have a solution pop up here before i get round to doing that
Did you modify the rom? Change or remove ringtone files you don't need?
Even I had same problem various times. Rebooting solves the issue everytime.
I didn't modify the rom at all and rebooting doesnt solve it, come to think about it, its happening since i used a pair of headphones for the first time
Do you use any Bluetooth headset? Usually when I use mine it happens what you have described and the only quick fix was to make a reboot. I didn't tested it yet on CM7.2 RC1 but the issue was present in CM7.1 Stable.
I use Rings Extended, it`s perfect
Today I tested the CM7.2 RC1 ROM with my Bluetooth headset and so far it is working with no problems (no sound issues like you mentioned). Now I just have to see if it would also stay this way in the few days.
I also found that some users had the problem described in the first post when they were using usual cord headphones but so far I hadn't experienced any problems with them although I'm suing them almost every day since the CM7.2 RC1 ROM release day.
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
kozij said:
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
Click to expand...
Click to collapse
I had this same problem for two different reasons with two different phones.
The first time, which seems unlikely for you, was a problem with DSP Manager that comes with CM9 causing my phone to crash and restart.
The second is manufacturer error. The phone has a titanium case, and due to some errors in assembly, when I would plug in headphones, the system would freeze and restart. Because I still had warranty, I had it replaced and the problem disappeared.
If you have a multimeter there are ways to check for a short, but I'm not sure if you are familiar with this.
Hope this helps!
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
blutooth
Sent from my HTC Vision using xda premium
kozij said:
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
Click to expand...
Click to collapse
If you still want to try and find a solution, get some electrical tape (or another strong insulating tape) and cut off a thin strip lengthwise (about 0.8-1cm width x 3-4 cm length) and tape it to the top of the headphone plug on your headphones so that it blocks any contact with the titanium.
demkantor said:
blutooth
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I use a pair of Bluetooth headphones and a Bluetooth-enabled car radio. But alas, if you care a lot about your sound quality, then Bluetooth certainly is *not* the way to go.
But if you care that much about audio quality, you would have a dedicated device which uses all it's processing power for playback, right?
Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
this thread can be referred for more details on this issue:
http://forum.cyanogenmod.org/topic/81373-audio-stops-working-from-time-to-time/
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
s.vivekananda007 said:
Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
Click to expand...
Click to collapse
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
BWolf56 said:
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
Click to expand...
Click to collapse
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
s.vivekananda007 said:
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
Click to expand...
Click to collapse
I don't suggest ROM to avoid flaming but you can look in my sig
BWolf56 said:
I don't suggest ROM to avoid flaming but you can look in my sig
Click to expand...
Click to collapse
Hey it got fixed in the latest nightly ( cm-11-20140721-NIGHTLY ). I had put it in cyanogenmod forum, I guess they read the issue and fixed it. Audio is perfectly fine now! Feels so great to use cyanogenmod again.
Thank you cyanogenmod!
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
gsm22 said:
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
Click to expand...
Click to collapse
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
s.vivekananda007 said:
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
Click to expand...
Click to collapse
Thanks for the suggestion, I may as well give it a try since most everything else I've tried has had the same issue.
edit:
Clean flashed latest CM nightly, sound worked for around 2 minutes, then stopped when I plugged headphones in. Rebooted, got it to work via speakers again but then DSP manager force closed and left me without sound.
Rebooted into recovery, cleared cache, still no dice.
Going to try another clean flash to see if I can get sound to last a while longer.
edit 2: It seems to be screwed completely now, no sound after install + reboot.
Same logcat lines as in http://forum.xda-developers.com/galaxy-s3-att/help/audio-wide-custom-roms-t2825135
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. ? I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
quan2032 said:
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
Click to expand...
Click to collapse
Mine is I can't hear them but they can bear me. What the hell is going on. Hahaha! If all else fails I'm going to get a new top receiver speaker put in at a shop close by. It does appear that many Xiaomi devices have had sound issues and have had speakers replaced. If you search on YouTube Xiaomi no sound on call or speaker replacement you'll see MANY videos on "how to." Quite a few videos specifically for mi mix 2. They should let us upgrade at least to the mix 2s for free.
I'll try 3.0 havoc but I've flashed around on Android 10 and 9 and problem hasn't gone away. Still zero sound on my end on calls but all speakers work doing anything else. Appreciate the recommendation. Thanks for commenting. Later today's ill flash 3.0 and see what's up. Then I may pull a few kernels from other roms and switch em out with whatever I'm on and see if I can't get something going that way.
I will also post a log of me on the phone talking and maybe someone can see something that's wrong... Hope so anyway..
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Sinchanwa said:
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Click to expand...
Click to collapse
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
flash713 said:
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hey there just want to know is your problem solved?
Sinchanwa said:
Hey there just want to know is your problem solved?
Click to expand...
Click to collapse
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
flash713 said:
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Sinchanwa said:
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Click to expand...
Click to collapse
I never thought that my sound issue was related to havoc in any way I am almost positive its a broken speaker. Looks as though that type of thing happens often on this device and other xiaomi devices. Google search receiver speaker replacement really fast and watch how many things show up about it. Its all over. I'm going to get a replacement. Using my moto g7 power rn as my main phone so I can have conversations and hear on my end. I always clean flash everything I flash. I never fail to wipe data, system, cache, delik cache on any install.
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
r_nally said:
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
Click to expand...
Click to collapse
This is just too strange. So maybe my issue does have something to do with installing Havoc 3.1. That was the first rom I flashed after I unlocked my bootloader and speaker worked fine on latest MIUI Global rom before... I wonder if it's possible to break a speaker due to a rom installation? I've never heard of that before. I thought surely it was just the rom and was a bug or a firmware problem. I flashed all kinda firmwares afterwards in latest twrp and also sideloaded a few to see if maybe something wasn't right with recovery and like you say it did not change anything at all. I still get zero sound on my receiver speaker while on a call.
I'm going to try a few more things and see if it does anything. If I find a fix or something that allows me to hear anything at all out of my end on receiver speaker I'll most definitely add it here in a post and to the op. Seems like there would be more people than us if it had something to do with Havoc... Idk. Appreciate your information. I hope we can get this fixed soon. I never even hardly used my phone when the speaker worked. ? I bought it used off swappa and about two weeks later unlocked and flashed Havoc and no sound during calls on my end.
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
r_nally said:
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
Click to expand...
Click to collapse
I used an app off Google play store to test speakers and my receiver speaker works but refuses to work during a call on my end. It did have sound come through loud and clear when I ran the tests I did when it first happened. I've flashed using magisk stable, canary, formatted data, used different firmwares, everything know to mankind and searched around and tried several things online and nothing. I've been trying to boot the Android 10 GSIs to see if that makes any difference but have had no luck using the same vendor and boot everyone used on pie GSIs so I snatched some from different roms and still no luck on GSIs that are Android 10. Lemme find link to test all i used and I'll return and post a link. Brb
Sent from my OnePlus5 using XDA Labs
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
r_nally said:
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
Click to expand...
Click to collapse
I doubt it and I did make a post there a while back about it. There are many others there ok that thread who reported sound issues and I wanted to confirm what for sure caused it before I put the blame all on a rom... The speakers on this device have had issues MANY times based on all the reports i read all over the internet. But if I can confirm exactly what it is I'll dang sure be very open about it online and let the world know in hopes that if it was something I did maybe someone else won't and I can somehow prevent it. But I did make a post there when it occurred. Search my username on the thread and you'll see it.
When you set a ringtone does sound come from your top speaker? On my device it does. Just curious. See if you can hear any sound selecting different ringtones. ?
Sent from my Mi MIX 2 using XDA Labs
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
I'm going to clean flash now after I do a backup and I'll install havoc and NanoDroid which eliminates Googles hold on all our devices. Once I get all setup I'll run some tests and see if maybe this solves it.
NanoDroid: https://forum.xda-developers.com/showthread.php?t=3584928
[MODULE/SYSTEM] NanoDroid 22.5.1.20200102 (microG, pseudo-debloat, F-Droid + apps)
No difference
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
On my other device , Moto G7 Power see the 8th post here: https://forum.xda-developers.com/g7-power/development/rom-havoc-os-3-2-t4058987
This time I haven't had it occur on G7 Power but when I saw that guys post I had a flash back. :/
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread.
[edit 17Jul20]
OK, it happened again today. No sound from top speaker when making or receiving calls. Had to switch to speaker phone. Then I cleared the 'Contact and dialer' app cache memory. (And for good measure the other caller and dailer apps also. TOP SPEAKER CAME ALIVE AGAIN!! So I am pretty sure its a bug/memory issue.
What I did: Long press the dailer icon - tap on App info - press 'Clear data' icon and select to clear chache memory.
ToBadX2 said:
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread. - Christo
Click to expand...
Click to collapse
What's crazy is this happened on my device just after I wiped data, system cache and flashed HAVOC which was the first rom that I flashed when I got this device. And I flashed my firmware and it did nothing at all. I'm getting a another speaker from eBay this week. They're only like $3 US. Gonna replace it and see what happens. ?