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.
Related
Everyone is complaining that my outgoing audio is horrible. They hear me, but it is muffled, with an echo, and not very clear.
I'm not sure if it started when I installed AOKP, or whether it started after I installed the new skin.
Ideas anyone????
Can anyone specify where the two microphones are? I know that one is on the bottom. But I can't find the other one (unless it is on top under the back cover)...?
try turning down the ear piece volume the mic can pick it up
This happened to mine as well. I had to factory reset it, but that fixed the problem. Obviously some update (most likely) or program caused it. Backup everything first (apps media and data). I then reinstalled my apps from the app store then recovered my data from the backup.
Remember, the reset will erase EVERYTHING on the phone -- including "SD" memory.
IMWarthog said:
This happened to mine as well. I had to factory reset it, but that fixed the problem. Obviously some update (most likely) or program caused it. Backup everything first (apps media and data). I then reinstalled my apps from the app store then recovered my data from the backup.
Remember, the reset will erase EVERYTHING on the phone -- including "SD" memory.
Click to expand...
Click to collapse
A couple of questions:
1. which ROM are you on? Are you on stock ROM or AOKP?
2. I did a factory reset before upgrading to AOKP Build 28. A factory reset DOES NOT wipe the SD card. It only wipes app data and rom data. What reset are you talking about?
I'm wondering whether this problem is due to something simple as a modem change. Feedback anyone?
IMWarthog said:
This happened to mine as well. I had to factory reset it, but that fixed the problem. Obviously some update (most likely) or program caused it. Backup everything first (apps media and data). I then reinstalled my apps from the app store then recovered my data from the backup.
Remember, the reset will erase EVERYTHING on the phone -- including "SD" memory.
Click to expand...
Click to collapse
Well I did a factory reset and installed AOKP Build 31 and I still have the same problem.
The factory reset DID NOT format the SD drive, so I have no idea what you are talking about.
Is anyone else experiencing bad outgoing audio?
montrealguy said:
Well I did a factory reset and installed AOKP Build 31 and I still have the same problem.
The factory reset DID NOT format the SD drive, so I have no idea what you are talking about.
Is anyone else experiencing bad outgoing audio?
Click to expand...
Click to collapse
First of all, I am sorry to hear that you are having this problem. We welcome you to our lives. A lot of CDMA Gnex and a few GSM GNex users had this issue arise more than 4 months ago.
Second of all, I don't think you searched for this issue yet, or you just haven't found it, so I'll do the search for you. This issue is somewhat prevalent.
1) the post I made about this issue:
http://forum.xda-developers.com/showthread.php?t=1604730&highlight=microphone
2) the post most of us with this issue have been following here on XDA:
http://forum.xda-developers.com/showthread.php?t=1403051
3) And the location map (Although, I personally believe location doesn't even matter because even according to this post, it pretty much happens everywhere):
http://forum.xda-developers.com/showthread.php?t=1545621
4) Google Issue Report:
http://code.google.com/p/android/issues/detail?id=24019
The bottom line:
1) there's no fix as of yet, even if some users naively recommend you to get custom ROMs, Radio, Factory Reset, the chances are, none of will work.
2) due to severe variations among devices, some have whole lot worse than others (happening as soong as 5 sec into a call on every other call), some have it better than others (never had it happen for weeks, but infrequent enough for it to be any "issue" per say.)
3) I have noticed many of the members here at XDA don't even use GNex as a phone that much but rather a very nifty computer you can flash OSs on. Hence, the issue might be a little bit more prevalent than users report simply because many of us don't use this phone as a phone.
4) When you hear from problem free users "You are covering mic with your finger", "It's probabaly user issues, check out the apps that you installed."
Stay calm, just realize that some hasn't seen this issue and do not understand what we are going through.
5) In the mean time, I recommend you not using this phone for business purposes (e.g. try landline or second phone for conference calls, etc). Or even use a flip phone for business purposes. You may also try to get a replacement hoping the other one will have less issue. But it will have it most likely as well.
Let the other party know if your voice becomes robotic sounding and starts breaking up, let them know you'll call them back as soon as you call them.
6) Contact your carrier, and let them know. Many of them actually have been telling all of us the fix is on the way since January, so who knows..
Hope this post saved your time understanding this issue in depth.
Thank you for reading my 4 months of investigation regarding this issue.
Charlescom: I read through your posts and I am doubting whether I have the same problem as you.
My OP stated that people hear me, but it is muffled, with an echo, and not very clear. Your posts state that the microphone cuts out entirely or sound turns robotic. My microphone has never cut out.
Is this really the same problem?
montrealguy said:
Charlescom: I read through your posts and I am doubting whether I have the same problem as you.
My OP stated that people hear me, but it is muffled, with an echo, and not very clear. Your posts state that the microphone cuts out entirely or sound turns robotic.
Is this really the same problem?
Click to expand...
Click to collapse
In a broader scheme of things, it is a similar problem or even a same problem.
I had people tell me 1) my voice turned into a static robot that chops up 2) muffled with an echo...as well..
see post 1199 here
http://forum.xda-developers.com/showthread.php?t=1557606&page=120
but before you slam me--
i am not sure if these two audio issues are even related and if the N1 fix can be adapted to the GN--just fyi for the real techies
rugmankc said:
see post 1199 here
http://forum.xda-developers.com/showthread.php?t=1557606&page=120
but before you slam me--
i am not sure if these two audio issues are even related and if the N1 fix can be adapted to the GN--just fyi for the real techies
Click to expand...
Click to collapse
Well it seems that the fix works for some people on the Desire and on the Nexus One on a 4.04 ICS ROM!
Can one of you tech experts check it out???
It was the only fix that worked for me--my issues were no onboard working mike and overdriven audio to listener as well as echo. I am on that rom--bcmics 4.0.4
rugmankc said:
It was the only fix that worked for me--my issues were no onboard working mike and overdriven audio to listener as well as echo. I am on that rom--bcmics 4.0.4
Click to expand...
Click to collapse
Now we need to know whether it works on the Galaxy Nexus GSM and AOKP...
And can someone create the fix in the form of a CWM zip? Most of us have no idea how to use ADB.
montrealguy said:
Now we need to know whether it works on the Galaxy Nexus GSM and AOKP...
And can someone create the fix in the form of a CWM zip? Most of us have no idea how to use ADB.
Click to expand...
Click to collapse
Cwm zip is a good idea. Learn how to use adb. It's actually pretty damn easy.
Sent from my i9250 using Forum Runner
Can someone with expertise here create a CWM version of the audio fix for us? And comment on whether it actually works on the Galaxy Nexus GSM? And AOKP?
I'd love to find out whether it works!
Sent from my Galaxy Nexus using XDA
I got this issue while running AOKP.
Yup. Never changed ROMs faster.
Solution: Different ROM
Sent from my Galaxy Nexus using XDA
Smokeey said:
I got this issue while running AOKP.
Yup. Never changed ROMs faster.
Solution: Different ROM
Click to expand...
Click to collapse
Which ROM are you using now on your GNex GSM? I think that AOKP is based on CyanogenMod so I don't think CM9 would work either.
Are you having this problem with calls only or does it happen when you record audio with the mic (I.e. a video or voice recording)?
Personally, I'd stick with stock rom and kernel as the custom stuff often introduce issues here and there and troubleshooting them can be a nightmare.
montrealguy said:
Well it seems that the fix works for some people on the Desire and on the Nexus One on a 4.04 ICS ROM!
Can one of you tech experts check it out???
Click to expand...
Click to collapse
Different audio chipset.
No bueno.
EP2008 said:
Are you having this problem with calls only or does it happen when you record audio with the mic (I.e. a video or voice recording)?
Personally, I'd stick with stock rom and kernel as the custom stuff often introduce issues here and there and troubleshooting them can be a nightmare.
Click to expand...
Click to collapse
I just tried a video recording with the front camera and the audio is great. Sound recording in the same conditions with Tape-a-Talk sounds pretty bad (robotic). And calls sound pretty bad too.
Could it be that the stock camera is using/not using the second microphone for noise cancellation, and the calls feature isn't?
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?
I'm currently running Re-Calked.E4GT.0.2.1.FI25. For the most part everything is solid, and getting some of the best battery life I've ever gotten out of the phone (24 hrs with ~2hrs screen time no problem if in a good signal area).
The one little problem I'm having is any time I finish a call using my in-car bluetooth device, the screen blacks out for a while then I get a message saying Com.android.phone has stopped.
The device is still connected to bluetooth (music starts streaming again, etc...), but if I try to make another call, the dialer won't enable bluetooth (a lot of weirdness about finding a bluetooth device when you tap the bluetooth button on the dialer UI). A hot-boot puts everything back again the way it should be until my next call. This happens 100% of the time on bluetooth, never on a regular call - speaker or otherwise.
I don't think it's Re-Calked's fault, I've experienced the same problem on the stock ROM (FH25). It was fine on FH13, and I'm fairly certain FI03 was good too, but I got dismal battery performance on these kernels.
Any suggestions? This is a real downer for me ... I'd hate to have to try an older ROM since everything else is effin' fantastic! (BIG thanks tdunham!!)
UPDATE:
If anyone else runs into this problem, flash the FF18 Phone from THIS POST (thanks tdundham)
The problem appears to be related to the phone being in landscape orientation, which is only available during a call when docked in a car dock.
I'm using the Official Samsung Vehicle Mount
Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Edit: It would help if you could backup and flash back to FI03 to verify if the problem still exists on that version.
tdunham said:
Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Click to expand...
Click to collapse
Actually it's not a built-in bluetooth. It's a "Belkin Bluetooth Car Hands-Free Kit for Apple iPod, Apple iPhone, BlackBerry,and Android Smartphones, US Version" ... search for that on Amazon ... tried to post a link, but I'm too much of a noob to post links yet, apparently.
I have the phone in a Samsung windshield mount, and the Belkin device ports all audio through the aux-in jack of my car stereo. It also has a built-in microphone so that I can use it for calls.
I have experimented a bit to see if it was a conflicting app, but it still happens even if I'm using nothing else. Worked fine on the older kernels, even with multiple apps running (Car Home Ultra, Waze, and Play Music are typical) went wonky as of FI25. I even tried disconnecting it from the dock and disabling car mode. The only thing that causes it is being connected to bluetooth and ending a call, and then it happens every time. Doesn't matter if I initiate the call or receive it. (Which is useful, because I could easily test by calling 611)
I wish I had another Bluetooth device to test if it was specific to the Belkin ... but that's all I've got.
No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.
tdunham said:
No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.
Click to expand...
Click to collapse
Thanks for that ... can't wait to try. Going to flash your new Re-Calked update soon too.
On a tangent regarding Waze ... did you install the latest update? I can't stand the way they use 30% of the screen with that black bar ... even worse when you get close to your destination and that other menu bar pops in above it. 50% of the screen covered with useless info.
I rolled back to the prior version from my Titanium backup.
I only used Waze this morning once after the update but didn't really check it out.
Backup your phone.
Flash this first - FI03.flash.first.zip
Test bluetooth, if it isn't working move on...
Flash this second - FI03.stock.lib.zip
Test bluetooth. Even if it is working, flash this next. FI03.stock.lib.zip
Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app
romgnascher said:
Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yeah, don't forget to backup first.
Sent from my SPH-D710 using xda premium
So, it looks like I was wrong with my initial investigation.
I did flash the first file ... everything connected fine. Placed and disconnected a call no crash. But what I DIDN'T do was put the phone in the car dock.
So, I think the problem isn't bluetooth at all. I think it's some interaction with the car dock. If the phone is connected to the car dock when I disconnect the call ... that's when com.android.phone crashes (I can start the call connected, just need to disconnect before I end the call). I also had a suspicion that Car Home Ultra might have been a factor, but it happens even if Car Home Ultra is not running. I thought I had tested this scenario originally, but I guess I missed that one.
I'll flash back to my nandroid later and reconfirm these results. In the mean time ... any thoughts on what the car dock might be doing to trip up the phone?
UPDATE:
Now that I've narrowed it down to the dock, I found this bug report that appears to be related to my issue (yay, I'm not the only one):
http://code.google.com/p/android/issues/detail?id=34612
Down the end of that thread, it appears that the issue seems to be related to the phone being in portrait mode ... not necesserily the dock, it's just that you can only get portrait mode during a call when docked.
Just curious. Does your dialer rotate when docked so you can make a call?
Anyway, I sent you something in a PM check it out.
Edit: I'm working on one more thing to add to that. Give me a little while.
Cool, I'll look at it afterI get the kids to bed.
Yes, the dialer rotates in the dock. Also, when in a call, the contact's photo is also rotated and moved left.
Sent from my SPH-D710 using xda app-developers app
Ok we're running out of choices I guess. Try this older stock dialer and if that doesn't work, I guess that's it for now.
Thanks for your efforts whatever the outcome!
I'll flash this tomorrow and see how we go.
I just flashed the new Re-Calked update by the way. No problems, good stuff and it's been idling at around 1.6%/hr.
Changing out the phone did the trick!
OP updated with resolution.
Sent from my SPH-D710 using xda app-developers app
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
Cool, I'll look at this one too. Have an answer for you by lunch time.
tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.
romgnascher said:
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.
Click to expand...
Click to collapse
That's fine, as long as we got it working for you.
Has anyone found a fix for the sound cutting out after a few seconds of a video or game? I have tried the soubdabout app, Turing the USB option off, disable Power save.. Still happening..
Sent from my SAMSUNG-SM-G891A using Tapatalk
I have the same issue sometimes, I've read around the web and it seems to be a mix of software and hardware related, I read a guy suggest removing and putting back the case (in case you have one) and I did that and the sound came back, haven't had the issue again.
Dakotahorse said:
Has anyone found a fix for the sound cutting out after a few seconds of a video or game? I have tried the soubdabout app, Turing the USB option off, disable Power save.. Still happening..
Sent from my SAMSUNG-SM-G891A using Tapatalk
Click to expand...
Click to collapse
hudtwalcker said:
I have the same issue sometimes, I've read around the web and it seems to be a mix of software and hardware related, I read a guy suggest removing and putting back the case (in case you have one) and I did that and the sound came back, haven't had the issue again.
Click to expand...
Click to collapse
Hmm, I keep mine out of a case,.. Yeah I'm not sure what it is, it's a 50/50 between some say software and some say hardware. I would asume that software would of been fixed by now, either Samsung or 3rd party
Sent from my SAMSUNG-SM-G891A using Tapatalk
So I found a solution for the issue in my case, it does seem to be software but it's really weird cause the issue continues in any firmware, it started when I was on 6.0.1 PI2, then I flashed Nougat and had the same problem (I hated it and battery drain was killing me) I went back to 6.0 and changed to the PK2 version and the issue continued, it was really weird cause it would cut out in audio messages, games but not music, I also tried every single suggestion on every forum and post I could find EXCEPT the Soundabout app, today I gave up, installed soundabout, selected media to speakers and bam, problem solved, I still need further testing, but it seems ok for now, keep in mind that I also have "prevent USB audio routing" on and "Easy Mute" off.
Dakotahorse said:
Hmm, I keep mine out of a case,.. Yeah I'm not sure what it is, it's a 50/50 between some say software and some say hardware. I would asume that software would of been fixed by now, either Samsung or 3rd party
Sent from my SAMSUNG-SM-G891A using Tapatalk
Click to expand...
Click to collapse
Im trying the soundabout app now, I orginally had it set to automatic and was still having the issue, now I set it to speaker and so far so good.
as this worked for me but idk about others... I was told to remove all paired bluetooth devices (on/off doesnt matter) then go to settings>connections>more connection settings>nearby device scanning then turn off... worked for me... (sorry for zombifying an old post but as this is still current with mine and many devices i decided to help)
samsung galaxy s7
Hi. I drop my boyfriend phone today and the volume cut it off for a while. It's that because I drop it off? Or because of the headphones that I had it in...because after I took the headphones off its works but after starts and go again? Pleasee helppp....
Andra1997 said:
Hi. I drop my boyfriend phone today and the volume cut it off for a while. It's that because I drop it off? Or because of the headphones that I had it in...because after I took the headphones off its works but after starts and go again? Pleasee helppp....
Click to expand...
Click to collapse
Is anything still wrong? Or does the sound work both with and without headphones?
Hi. I dropped my phone and have the same problem now. Did you get any useful help?
-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. ?