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?
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.
Since moving to Jellybean (when it first got released) and attempting to use Google Now, I noticed that the it wasn't doing or understanding what I was saying. It appeared that there was a lot of static noise before it would recognise what I was trying to say.
I loaded some recording software to make sure it wasn't just Google Now, but it turns out that it just hisses for that first 5 seconds before it comes good. It does not happen in phone calls, just when recording/talking to Google Now. Changing ROMs, kernels and radios has not changed the problem. Even moving up to the new 4.1.1 hasn't rectified the problem.
Has anyone else had this problem? Has it ever been fixed?
Any help would be fantastic!
Bumping.
Still can't seem to find an answer anywhere for this.
This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?
galapogos01 said:
This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?
Click to expand...
Click to collapse
I've tried different basebands, ROMs etc. Still suffers from the 2 seconds of hissing/not working microphone before it comes good and is usable.
Interesting. I too am on Telstra, tried few 4.1 and 4.1.1, CM10 and the same issue. Not to mention, even after the hiss is over, the volume is very low and rubbish in general.
Interesting that it affects a lot of Telstra phone owners.
Anyone reverted to the stock Telstra rom/baseband to test? Does it affect voice search in 4.0.x as well?
Same problem!
I have this exact problem!! I've had difficulty finding any others with this problem until I found this thread.
Grr, mine shows static for about 4 seconds and it struggles to understand anything at all! After those 4 seconds, it dies down, then I can speak and it is better but far from perfect with recognising my speech!
FYI mine is a yakjudv Telstra phone from Australia which I flashed to yakju 4.0.4 and then did a JB update OTA......
It was on the stock DVKK6 but am now on the XXLF1 radio that came with JB....
Argh, whats going on, i was so pumped for google now voice actions!!! Now its basically useless!!
Mines almost spot on 4 seconds every single time.....
Any solution to this would be greatly appreciated!
+1 again on my gnex
factory installed yakjudv i think, from vodafone.
I have had it since ICS, tried to record lectures in class, and the first few seconds is always static.
Now that you mention it, when I activate voice search in google now, i see the grey circle voice indicator spazzes out for a few seconds before it goes back to normal. Maybe that's why I have to speak loud for it to recognise my voice to make it distinct from the initial static, so it usually doesn't work that well.
Kinda weird that it appears to be Telstra gnex's. Still no luck in finding fixes yet.
Sent from my Galaxy Nexus
Any workaround or fix for this?
It seems like Santaria has already tried a variety of different radios with no luck.
Is this a case of sit and hope that Google fixes this?
So what exactly is the problem? There's 2 mics in the phone, but its picking up the wrong one?
Since when were there 2 mics? one for phone call and one for speakerphone? I didn't even know this. How could this happen and why is it only on Aussie phones? The hardware should be the same across the board?
I'm so confused
One is for noise reduction.
Cheers,
Jason
I wonder if there's a way to enable/disable the noise reduction mic?
Sent from my Galaxy Nexus
galapogos01 said:
One is for noise reduction.
Cheers,
Jason
Click to expand...
Click to collapse
One is for calls the other one is for recording videos and video calls...The Galaxy Nexus do not have a noise reduction software on board neither the required hardware so no noise canceling feature!
Sent from my Nexus 7
Err...
http://www.slashgear.com/galaxy-nexus-review-21196912/
http://en.wikipedia.org/wiki/Galaxy_Nexus
There seems to be some debate about its effectiveness - probably related to the above bug disabling it in some cases.
For the record, same problem on my telstra Gnex, google now only works if I hold the mic right to my mouth.
I'm having the exact same issue. I just bought a new gn that was locked to Vodafone Australia. I unlocked it and went to yakju then got the OTA and then started having the exact same problem that everyone else has described. I get massive static and so far nothing I've said has been recognised. It just times out with the message "recognising...".
I've recorded my voice using an app but everything sounded fine and I didn't get any static. I have the same problem if I use a hands free kit too.
Seems this happened with ICS also
http://forum.xda-developers.com/showthread.php?t=1602840
Star this issue
Hey guys, a few of us seem to be having this problem, please star this issue so that Google will be aware of it.
http://code.google.com/p/android/issues/detail?id=29092
SIMPLY CLICK HERE AND STAR THE ISSUE.
Starred
Starred a long time ago...
No luck, even with 4.2.2
I take it they're never going to fix this problem
For the longest time I was on stock rooted EK02. I recently took the plunge and wiped all and installed CM10, which I love. The only problem I've had is that *all* sound suddenly decides to just go away whenever it wants to (ring/notif tones, touch clicks, app sounds, everything except in-call audio). It might last 5 minutes, or it might last an hour, but it always comes back on its own, and a reboot does not fix it. I can't seem to trigger the problem with a certain app or a certain action, but for example, I will be sitting here playing Angry Birds Star Wars, and the sound will just drop out completely. A few levels later, it comes back on its own. I put the phone down, go do something else, and the entire phone has muted itself again. Frustrating...
I'm on CM10 beta2 nightly 20121108
Kernel version says 3.0.15-CM-g8e7ed92, which seems appropriate since it references CM and this is the first CM I've ever had on the phone. Should I try other kernels though? AFAIK, no one else has mentioned this particular audio problem in the CM10 discussion thread. At least I don't think this is related to the "low volume in some apps" issue.
HOWEVER, something interesting, the baseband/radio version says EK02. I guess I should update that to get better comm, but it couldn't be causing an intermittent muting issue, right? I guess I assumed incorrectly that a ROM installed after a wipe would have to include its own modem. Argh.
This is frustrating, as I said. Thanks for any help.
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
I am not exceedingly familiar with cm10 but I would bet it is not the modem causing that issue. I would be inclined to think you have intentionally and / or accidentally changed the "quiet hours" or setup some form of silent profile. Otherwise it was perhaps a bad flash, you did not wipe CLEANLY (IE. calkulins format all or odin a full wipe/restore rim first) or maybe not install with what many revs believe to be a CWM safe kernel???
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
also do you have anything (pc or stereo) connected to Bluetooth with the phone nearby?
trmitche2 said:
Wow. 5 days and no replies. Can't someone at least tell me what you think? I've never understood why I can ask a legitimate, polite, and descriptive question after searching the forums as much as possible, and it gets ignored, while someone else can post something completely redundant that barely forms a coherent sentence, yet it sparks a 10 page discussion... frustrating.
Click to expand...
Click to collapse
Nobody knows the answer to your questions. This is not a common problem and as mentioned above the modem has nothing to do with it. My only suggestion would be to flash a stock release one click, not a leak, and go from there.
Agree with above and mainly because I borked my build... it was perfect and then I tried a gps fix flash. Can confirm now that wipe in CWM and calks format all does not do crap for aosp, jb, or the like. So long story short, yeah you gotta one click or my guess is best served to clean slate with a stock ROM and in consequently factory wipe and just stay there.....
Wow thanks for the replies guys! I was really getting discouraged there for a bit.
I don't think it's a quiet hours setting, because all sound is cutting in and out *every 5-10 minutes*,
I will use Calk's wipe and start from scratch as suggested.
Although unrelated, surely EK02 is not a recommended modem for CM10, right? I guess I made a naive assumption that a full wipe followed by CM10 install would replace my old modem. I'm just curious what kind of problems might be caused by using such an old modem, even though I know sound is not one of them.
Can anyone recommend a modem for this ROM from personal experience? I understand from the main beta2 thread that the FK modems break 3G...
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
someguyatx said:
Just flash a one click, it will wipe everything and install a new modem. I'm using fi27 modem with codename rom, works fine. My current install method is run one click update prl and profile and get gps lock then do the install process of the rom.
Click to expand...
Click to collapse
Yes. Do this. Then. Format all is still a good idea if you choose to revert to a GB ROM like el29 and progress.
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
trmitche2 said:
UPDATE: I fixed this.... accidentally. What fixed it is hard for me to believe or accept, but Iv'e confirmed it by being able to reproduce it. The problem was being caused by the FRIKKIN' FACEBOOK APP. :/ I uninstalled the FB app for a totally unrelated reason: battery drain pointed out in another post. I realized the next day that the sound had not cut out once since then, I re-installed FB, and the problem returned quite predictably: all sounds started cutting in and out every few minutes. Uninstalled FB again, and sound has been fine ever since. My best guess is that the sound was cutting out/in each time a background sync of FB occurred. So now my sound is perfect and my battery life is much better to boot. I never used that damn app anyway.
Unrelated, but for what it's worth, I never installed a new modem as discussed above. Still running EK02 with CM10 nightly from 11/28. Have no problems to speak of. I didn't leave it on purpose, (noob mistake, thought CM10 installation would replace it), but I don't see any reason to change it as long as everything seems perfect, unless anyone can tell me what types of problems it could cause. Any further thoughts welcomed, but thanks again to you guys who already gave me advice.
Click to expand...
Click to collapse
None, modems are interchangeable between builds with the exception of the fk-- and newer modems, they only work with Touchwiz based JB roms. If your modem is performing well speed and call quality wise then there's no need to change. However you could always test other modems to see if you get any improvement in your location. If you choose to change modems you should be on a touchwiz rom so you can update prl and profile after the modem flash. Modems are a YMMV item each one interacts with different devices and locations differently so to find the best modem for you you just need to flash and test them out if you so choose
Sent from my hand to your eyes!
Samsung: Intercept, Galaxy S2, Galaxy S3, Galaxy Note 2, Nexus10
HTC: EVO4g, EVO 3d
LG: Optimus G, Nexus 4
Asus: Nexus7
Motorola: Photon
Amazon: Kindle Fire, Kindle Fire HD
We are legion, for we are many!
Thanks KoN! Extremely helpful post, as always. All other replies in this thread have been thanked as well. I learned a lot.
Still wish I knew how FB could make my sound cut in and out every few minutes, but if no one else has seen that issue, it must've been a quirk, so I imagine I'll never know. Moving on....
Hello and thank you in advance to all. I have a t989,
I run AOKP Galaxysbean V_12
KKO Kernel Governor is Smartass V2 and I/O is deadline
UVLI4 Radio
Problem: I know for a fact this is not a hardware problem, because I have went through 3 phone replacements because of stupidity and learning how to root phone, flash roms, yada, yada, etc. And with each of these phones this persistent problem occurs where all of the sudden at any given time, I will go to make a call and nothing. I can't hear the ring of another person's number, my voicemail, etc. The person does get the call, and when they answer, I still cannot hear them, and they cannot hear me.
Resolution: Ways I have fixed this before are with the first and second phone I flashed over a new radio, (previously UVLE1, UVLH1, 4G Blaze) and it fixed the calling upon reboot. Also I had flashed custom roms, or restored previous Nandroid backups and it worked again. (Little annoying doing this every 3 or 4 days. Though today, this happened with my newest phone, and flashing a radio did not work nor did restoring a Nandroid. This time I had to flash a new custom rom, then it worked. Then I flashed back over the Nandroid and it still works as of now.
Question: Could this be because of the kernel? Or the rom?
deleted
same here
Me and my wife have the same issues. We both have GS2s but hers is stock unrooted and mine is running CM10.1. Been dealing with Tmobile for months without success, swapping out cut down on how often its happening but did not fix it. Tmobile is stumped, very annoyed by this issue.
Not sure what's causing the problem but it seems jellybean 4.2 has fixed this issue. Try flashing AOKP 4.2 and make sure noise suppression is enabled and call this number 9143388802. The third option is an echo test and fourth option let's you record a playback to listen to how you sound. If you sound normal and people are still complaining then its their phone.
Sent from my SGH-T989 using xda app-developers app
I've come to the conclusion that its a rom problem because for me it happens with only certain roms. Ive tried all the rom kernel combinations and different radios but the only fix I've found is to retire that particular rom, no matter how good it is. Smoothness aint gonna get the cops or the fireman to your house. The only roms that have worked for me as far as call quality are, for some reason all of TheLastSidekick's Kangs, Darkside evolution 3, Sky Jellybean, Rushing's Bulletproof,and both of the 10.1 variants we have. The strange thing is I can't recall any call quality issue's when flashing roms from the Skyrocket thread. For instance I get the worst call quality ever using Jedi Jelly, but I'm crystal clear using Embryo from the Skyrockets thread, so much so I wont even try our version of the same rom.
I blame T-Mobile network. This would happen to me all the way back to my old flip phones. Every other call or so would do this. I've always put up with it cuz I like T-Mobile customer service.
Sent from my SGH-T989 using xda app-developers app
bonetweeter122 said:
I blame T-Mobile network. This would happen to me all the way back to my old flip phones. Every other call or so would do this. I've always put up with it cuz I like T-Mobile customer service.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I wouldn't go that far because I never had a problem on the Sensation no matter what rom I was using. I blame sammy
You know.. Now that I think about it.. My old flip phones were Samsung! Lil..
Sent from my SGH-T989 using xda app-developers app
I actually just realized this problem persisted when I would turn on the phone and try to make a phone call to quickly. After becoming aware of this. I turned the phone off and allowed it to fully boot back up, and it worked again.
deleted
WatchGintama said:
I can confirm that this is the problem. I rebooted my phone, called someone right away, and couldn't hear anything. Next I let it load for 40 seconds after boot, and I can hear fine.
Now we have to tell t-mobile this.
Click to expand...
Click to collapse
This is not the issue, it also happens to phones that have been on for minutes/hours/days.
Is there any updates on this issue? My wife is having this problem on her phone, and it seem like it's been getting worse...
gwuhua1984 said:
Is there any updates on this issue? My wife is having this problem on her phone, and it seem like it's been getting worse...
Click to expand...
Click to collapse
I found out with my problem. It was when I tried to make a call to soon. It would do this. As long as I have let the phone load for a minute or two after boot, I haven't had any more problems. My problem may be different from yours tho. Hope this helps.
I'm having this issue, and its not from calling too quick after a boot.
It came on out of the blue the evening of March 6 ...
I have the Tmob phone but it's unlocked and I'm using a Straight Talk AT&T SIM, connected to the AT&T network in Sierra Vista, AZ.
Ok... I need help. I am such a novice at this stuff but I find myself so very interested in the world of root, and the freedom that it brings. Basically my entire knowledge of computers..... Is Android, and worse than that, I'm self taught... Please don't run!! I'm a super quick study. Ok now to my problem, I started off rooting my T 989 surprisingly enough with absolutely no issues at all, or at least that I could tell. Ran beautiful and super smooth, then I went app hoarding and installed A fonts package installer, opened it, it installed about 85 prcnt. done and crashed. Never made it back. The novice, and the dumbass in me, FREAKED! and did an uneducated, no experience attempt to make recovery....... 4 times needless to say that I COMPLETELY wiped the entire phone. I had a friend bless me and show me a thing or two and I successfully managed to flash one of your Roms to it and I must tell you that I supremely thankful to all who n these projects.... MAD RESPECT to all of you. So the one issue I am clearly having is everyone I speak to says I sound like I'm on speaker or just can't generally hear me. Been through the settings a couple of times and I am pretty sure that I have them correct, and I have not touched anything that I wasn't sure about, and I definitely have completely refrained from pimpin my kernel. I really just need someone who can spend a little time setting me straight on some unfamiliars. Also just have a few stupid questions that won't be the least bit stupid after I get them answered. Any time any one can lend would be greatly appreciated and someone's good deed for the day. Thanks for allowing me to vent guy's
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 05:03 AM ---------- Previous post was at 04:54 AM ----------
And no, issue definitely is not exclusive to happening on reboot, mine has been that way ever since flashing, and on every call. But I can hear the other end perfectly......
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
neilc300 said:
Ok... I need help. I am such a novice at this stuff but I find myself so very interested in the world of root, and the freedom that it brings. Basically my entire knowledge of computers..... Is Android, and worse than that, I'm self taught... Please don't run!! I'm a super quick study. Ok now to my problem, I started off rooting my T 989 surprisingly enough with absolutely no issues at all, or at least that I could tell. Ran beautiful and super smooth, then I went app hoarding and installed A fonts package installer, opened it, it installed about 85 prcnt. done and crashed. Never made it back. The novice, and the dumbass in me, FREAKED! and did an uneducated, no experience attempt to make recovery....... 4 times needless to say that I COMPLETELY wiped the entire phone. I had a friend bless me and show me a thing or two and I successfully managed to flash one of your Roms to it and I must tell you that I supremely thankful to all who n these projects.... MAD RESPECT to all of you. So the one issue I am clearly having is everyone I speak to says I sound like I'm on speaker or just can't generally hear me. Been through the settings a couple of times and I am pretty sure that I have them correct, and I have not touched anything that I wasn't sure about, and I definitely have completely refrained from pimpin my kernel. I really just need someone who can spend a little time setting me straight on some unfamiliars. Also just have a few stupid questions that won't be the least bit stupid after I get them answered. Any time any one can lend would be greatly appreciated and someone's good deed for the day. Thanks for allowing me to vent guy's
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 05:03 AM ---------- Previous post was at 04:54 AM ----------
And no, issue definitely is not exclusive to happening on reboot, mine has been that way ever since flashing, and on every call. But I can hear the other end perfectly......
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Just leave me some thanks. Under your phone settings, there should be a noise surrpression box. Make sure it is check marked. Every time I do that people have said I sound better. What do you want to do? Change it back to custom rom? P.S. ALWAYS MAKE A NANDROID BEFORE YOU DO ANYTHING.. ALWAYS ALWAYS ALWAYS!.. Google will solve many questions too. If nothing helps or you need to be walked through some processes, message me.
Enable noise suppression in phone settings. Fixed my problem.
[ NEXUS⁴ / VANILLA ROOTBOX / APEX PRO / TAPATALK ]
dEris said:
Enable noise suppression in phone settings. Fixed my problem.
[ NEXUS⁴ / VANILLA ROOTBOX / APEX PRO / TAPATALK ]
Click to expand...
Click to collapse
I'm running cm10.1 nightlys as and I cannot find that setting.
Trbobuick said:
I'm running cm10.1 nightlys as and I cannot find that setting.
Click to expand...
Click to collapse
Open phone dialer, menu settings, and it's in there.
-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. ?