Related
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
I'm having the same issue...
+1
Follow up
kenrothman said:
I'm having the same issue...
+1
Click to expand...
Click to collapse
So today I tried newest builds of Parandoid Android, and Liquid Smooth with the same result. Pretty much all the popular ROM's in the "AT&T Galaxy S III Original Android Development" contain this bug, I'm assuming because they share alot of code. Seems like they base alot of work off of Cyanogen Mod so perhaps that's where it lies, I don't know.
What I do know is I installed DrewGaren's Jellybean 747 Milestone 7 ROM which is Touchwiz based and the speakerphone echo went away. So my stock ICS ROM and this one do not contain the issue but every other JB based ROM I have tried does. I don't have the knowledge to troubleshoot this issue I just wanted to share what I've found and hopefully someone with the knowledge can help track it down.
I do prefer the CM 10 style ROM's over the stock experience but I can't live without speakerphone so hopefully this issue gets resolved, thanks for listening!
I have the problem too. I bought my S3 3 weeks ago and within a few days rooted it and installed the latest CM10 nightly. The first time I used the speakerphone I became aware of the echo problem with the it. So I switched back to the stock rom and the problem was gone, so I knew it wasn't a hardware problem with my phone. I've tried every nightly CM10 rom including the recently released stable build. I also tried the latest official AOKP as well as Task and Koonsez's latest build and they all produce the echo.
My buddy suggested I try the black jelly rom, and that's the only one I've been able to use that doesn't have any echo, but it's a touchwiz/Samsung based build. It's not bad, but it doesn't support wifi tethering and it's not as smooth as CM or AOKP. I really want to run CM but can't live without speakerphone.
On a side note, I rooted and rom'd my wife's and friends S3 the exact same way as mine and neither of theirs have the speakerphone echo problem. I suspect there are some hardware differences with Samsung phones. Maybe different parts suppliers that aren't playing properly with the drivers in the CM10 build.
From my tests this bug sounds like the mic is turned up max when speakerphone is on so it's super sensitive. Also, the volume level doesn't have any effect on the speakerphone volume whether you raise or lower it.
Really hope the dev's can fix this so I can run CM or AOKP once and for all.
On a final note, my phone is blue, while both my wife's and my buddy's are white. I don't want to conclude that the white phones don't have the speakerphone echo problem with CM roms. Hope it's just a coincidence.
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Randomacts said:
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
gots54 said:
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
Click to expand...
Click to collapse
Hi, just wondering if anyone has found a fix for this or any other AOSP JB Roms that has the speakerphone echo fixed?
ladd76 said:
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
+1
speakerphone echo
I also have this problem. using baked 8. with kt747 and its awesome!! They seem to be aware and working on it. tried a different kernel but no dice. Ive been in every setting cant seem to get rid of it. my phone is white so its not that. hope someone can figure this out soon. tw roms dont have this problem and I like the aosp feel.It would be nice to know if anyone even an idea of the cause, maybe the users could check files and find something.
I confirm that I LOVE these ROMs, but absolutely need a working speakerphone too.
Some other thread said something about changing the radio to ULVA3 or something like that... not sure if anyone had any luck with that.
Anyways, thought I'd break my lurked tendencies and post for my 1st time here.
Love my GS3!
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
speakerphone echo bug in CM10.1 RC2 for quincyatt
gots54 said:
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
Click to expand...
Click to collapse
I have the speakerphone echo bug on my Samsung Galaxy Note with CM10.1 RC2. This has happening on earlier versions as well, but I thought a reset/wipe fresh install would fix it. Would like to stay on CM10.1 but I really depend on my speakerphone.
Good Afternoon,
I have noticed a problem with my Zuk Z2 and I want to ask if anyone else is facing it.
Every now and then, especially when typing with keyboards, the vibration completely disappear from the phone (vibrate on touch, vibration when unlocking, ecc. ecc.) and then after some times, after locking and unlocking the screen few times, the vibration returns to work properly.
This is not due to any rom because I experienced this problem with almost all the custom roms posted on XDA, also on ZUI official builds this problem is present.
Is anybody else facing this problem?
VMat21 said:
Good Afternoon,
I have noticed a problem with my Zuk Z2 and I want to ask if anyone else is facing it.
Every now and then, especially when typing with keyboards, the vibration completely disappear from the phone (vibrate on touch, vibration when unlocking, ecc. ecc.) and then after some times, after locking and unlocking the screen few times, the vibration returns to work properly.
This is not due to any rom because I experienced this problem with almost all the custom roms posted on XDA, also on ZUI official builds this problem is present.
Is anybody else facing this problem?
Click to expand...
Click to collapse
As far as I know there is an apparent problem with gboard on all z2 plus devices. Maybe that's what is causing this problem [emoji848]
Sent from my Moto G Play using Tapatalk
C4ptain ph4ntom said:
As far as I know there is an apparent problem with gboard on all z2 plus devices. Maybe that's what is causing this problem [emoji848]
Sent from my Moto G Play using Tapatalk
Click to expand...
Click to collapse
Thank you for this tip!
Do you have this problem? Which keyboard are you using?
I have tried a different keyboard but unfortunately the problem still persists
TBH I really don't have the phone. I just read it somewhere on the zukfans forum. So I suggest that you post there or wait for someone else !
Sent from my Moto G Play using Tapatalk
I have tried to gather information about this error but apparently nobody knows anything.
I have tried multiple keyboards without success, I have tried to install the keyboards as system apps but also in this case the problem persists.
I have even tried to reinstall old and new ZUI chinese builds (1.9.063, 3.1.117 up to the latest 3.5.261) via QFIL, hoping that a deep factory reset would have solve it but every attempt was unsuccessful.
Probably this is an hardware problem and I don't know if can be fixed.
If anybody has any idea, feel free to suggest.
I have this problem too
All I can confirm that this isn't due to the rom or kernel (RR 5.8.4 + Darkmoon 4.001)
because the exact same combo never had this bug before. After a clean wipe, and subsequent restoration from TWRP backup & installation of updated GApps, this bug has infected my phone. Also, what I've noticed is that this bug only happens when we're typing, not at random (for example, when it is locked or viewing media or playing music or scrolling feed)
Also, apparently from the same time, the phone tends to heat up lot and drain it's battery much more quickly.
That's all I observed, let me know if that helped anyone
It might be a problem with any of the system level google processes on the phone as far as I can guess.
I am using the Moto G 2015 (Osprey) build of LineageOS with MicroG bundle and whenever I use the keyboard there seems to be a slight vibrate on tap permanently on. I have tried toggling the actual 'Vibrate on tap' setting under 'Sound/Other sounds' but is the same whether on or off. This wasn't happening under the original stock Android the phone came with so I can only think it is a bug in LineageOS. Has anyone else experienced this or know of a solution?
I am using the 10/03/2018 build and was previously using the 10/02/2018 one, same issue in both.
AndraMan said:
I am using the Moto G 2015 (Osprey) build of LineageOS with MicroG bundle and whenever I use the keyboard there seems to be a slight vibrate on tap permanently on. I have tried toggling the actual 'Vibrate on tap' setting under 'Sound/Other sounds' but is the same whether on or off. This wasn't happening under the original stock Android the phone came with so I can only think it is a bug in LineageOS. Has anyone else experienced this or know of a solution? I am using the 10/03/2018 build and was previously using the 10/02/2018 one, same issue in both.
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3466246
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Today I updated from lineage os 14.1 as per instructions. Phone was running smooth until but after some timemy phone stopped working suddenly after taking a call, for no apparent reason. I Restarted the phone and at lock screen, screen is totally unresponsive ( cant type my pin) and goes dark and phone reboots again!!! I don't know what causes this, as it never happened before.
Is this more likely to be a software or hardware problem? I am new to this, Please help -.-
sillo007 said:
Today I updated from lineage os 14.1 as per instructions. Phone was running smooth until but after some timemy phone stopped working suddenly after taking a call, for no apparent reason. I Restarted the phone and at lock screen, screen is totally unresponsive ( cant type my pin) and goes dark and phone reboots again!!! I don't know what causes this, as it never happened before.
Is this more likely to be a software or hardware problem? I am new to this, Please help -.-
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3739169
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
-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. ?