Hello everyone,
I have recently been experiencing a weird issue with making or receiving calls. About 20% of the time, I am able to successfully make and receive calls, and majority of the time I just see the dailer timer progressing but no audio output from the earpiece speaker. When I insert headphones or try speakerphone I am still unable to hear any audio from calls. However, music plays just fine from headphones. I can also send texts and MMS with no issues. Sometimes when power cycle the phone it will work for a couple calls only.
I have literally tried everything. Flashed different modems, went back to stock touchwiz, numerous factory resets, removed SIM/SD card, etc. with no luck. I am currently on the latest GPE build since my GS4 has the MDK bootloader. I have determined that it is not an issue with this ROM itself since no one else is experiencing this issue and I have seen it on the other ROMs I have recently tried.
If anyone has suggestions I'd really appreciate it. I have searched for days online and have not been able to find a solution that has worked, and I am beginning to think it is a hardware issue although my call audio works some of the time. Any input would be greatly appreciated.
OK Google Voice Search
I had a similar issue. I was able to resolve it by disabling the setting where you can say OK Google from anywhere on your phone and that fixed it. Unlike you, I am on the latest update, rooted. Maybe try messing with OK Google Detection settings, disable all of them and see if it starts working, then re-enable 1 at a time until you find the issue.
Related
I just bought a new car recently and when I try to pair my Fascinate with the car bluetooth, my phone slows down considerably, won't successfully complete calls, and eventually locks up, forcing me to do a hard reset. My car's bluetooth program locks up as well. One time I got an error message on my phone saying services.exe had to force close. At first I thought the problem was with the car, but my dad's Droid Incredible works beautifully on it.
My phone is rooted w/o lagfix, and has launcher pro. It's also been de-binged and has other basic bloatware removed. I don't use taskillers either. Any help or advice would be greatly appreciated, thanks!
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Bluetooth Crash After 1st Call is Ended
DeezNotes said:
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Click to expand...
Click to collapse
I'm also having this same problem with my Bluetooth crashing after my first call ends when using following:
ROM ComRom 1.3
Kernel TW with Voodoo Sound+BLN+UV+Misc tweaks 4/15 by jt1134
Radio ED04
2011 VW Jetta SEL (just purchased a few weeks ago)
I'm thinking to go back to stock as well but would prefer some kind of fix or even a workaround over doing that.
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
(No Longer Resolved) The ROM was the Problem with Bluetooth
DeezNotes said:
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
Click to expand...
Click to collapse
Excellent!!! Thank you for this! I already had the ED04 modem so that wasn't the problem. Last night I updated my kernel and this morning I tried again with no success so the kernel wasn't the problem. Later this morning, I loaded up the MIUIwiz 1.1 ROM and on the way home from work, I tested 4 calls and viola SUCCESS!!! ComRom 1.3 was the culprit and even though MIUIwiz is based on ComRom, somewhere along the line Bluetooth in the ROM was fixed.
Thanks again DeezNotes!
Edit: My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
On the same setup, the problem is back. Its actually a lot worse than before. I actually noticed crashes from Pandora when hanging up a call and Pandora wasn't even running (for days). Even after uninstalling Pandora, still get plenty of consistent crashes after hanging up a call. Interestingly enough, this is with an Audi, so hearing the issue is with a VW isn't far off from what I'm seeing since those cars are typically very identical.
I'm trying out a different phone on a different carrier [again] later this week. If all goes well, I'm going to chalk it up to Samsung and their lack of QC. I would say it's an Audi/VW issue, but I've successfully used the same features with a Blackberry and an LG G2x. Later this week I'll try the HTC Sensation and see how things go. Based on my experiences so far, this might be the last Samsung smart phone I'll ever get.
Bluetooth drivers issue - causing crashes.
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
piemmmm said:
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
that sounds really really technical. any ideas on what we can do to fix it?
Handsfree Bluetooth Problem is Back
My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
I have the same issue with ED05 de-bloated, stock kernel.
Has anybody found a solution?
I bought my S4 with VRUAMDK firmware used hence no warranty
when I got it it tested fine I made calls
after rooting it just stopped making any sounds or phone calls, (I'm pretty certain I followed the rooting instructions correctly)
tried unrooting, going back to stock and rerooting and trying several ROMS I still have no sound whatsoever no headphones nothing, it does eventually detect the headphone if plugged in, even in the diagnostic menu sound doesnt work
I can browse using mobile data I can attempt a call and the other phone rings but the dialer doesnt work after placing the call the phone hangs or restarts sometimes.
everything else works I can send and receive text messages, emails, cameras work. etc
if this is a hardware issue what needs to be replaced? any idea whats the best way to get this fixed? and probable cost?
I read other threads that were similar which suggested unrooting and resetting and tried that
Dear community,
I'd like to adress an issue which occured on my i9300 after the udate to jelly bean over a year ago. It was the last official firmware update for the device and I was using the stock rom then. Soon, I noticed a huge distortion of my dialogue partner's voice and even the dial tone during hands-free in my car. Talking hands free is not possible because of that if the issue occurs. Random switching on and off the mobile seems to fix it sometimes, but not reproducibly. Meanwhile I am using kit kat via SlimRom (Slim-i9300 4.4.4. build. 9.0-OFFICIAL-8312) with Boeffla kernel (boeffla-kernel-2.8-Omnirom-i9300.recovery), and the problem still persists. Switching from bluetooth to phonespearks and back during a call sometimes fixes the issue, but sometimes it even worses it. Basically, sometimes distortion is there, sometimes not. On the web I found a few reports of the problem without solutions. Recently, I tried several modems / radios for my device because I had heared that might fix the problem, but to no avail. I further tried to alter the audio seetings in engineerig / service mode like suggested in this thread, but encountered a "locked" Audio-submenu - I simply cannot open it, while all the other options worked. This seems to happen and people say to change your modem, like in this S2-Thread. However, all the modems which I tested neither enabled me to enter the audio-menu, nor fixed the main issue - the distortion. Lastly, I dug up this thread mentioning to unblock the keystring-file in order to access the audio menu, but I have no idea what exactly I should do. Apart from this, I have no clue whether fiddling around in the service/audio-menu can fix the distortion-issue anyway. I should add that the device's speakers work flawlessly during non-hands-free calls. Furthermore, transmitting music via bluetooth to my car never causes distortion. Also, other devices, among which a S4 with lollipop, do not cause distortion.
So, long-story short: Can anyone help with the distorted audio-issue during hands-free? I now rely on hands free communication and will have to switch to a reliable device if I can't get it to work on my i9300. Thank you very much. Obviously, downgrading to a pre-jelly bean-Android might also fix the issue, but to be honest I don't want to give up all the benefits of kit kat in terms of usability.
Best regards!
My Verizon S8's microphone has recently developed heavy static and noise whenever making phone calls and voice recording. My voice is barely audible. This seems to have happened after upgrading to Pie. It was working perfectly fine before, and I didn't install any new apps. The only changes I made was upgrade to Pie and switch out my Google Fi sim card for the Verizon one. I tried rebooting in safe mode, wiping cache, restoring network settings and nothing has helped. Does anyone know a solution to this or know what could've caused this? Thanks in advance.
Hi, I'm having a issue with my redmi note 9 pro. Whenever i try to make a call, it always goes to speakerphone. I cannot get it to go to the earpiece. WHen i try turning off speakerphone, the audio is still routed through the bottom speaker, and the person on the end of the call notices i sound broken up. WHen i swotch on the speakerphone the sound is clear, and then the person can hear me just fine. I've tried with whatsapp, google voice, and the regular phone app, and all have the same issue. I'm running Evolution X currently as my rom, but i've tried lineage os, and it has the same bug. On stock MIUI I don't remember having this issue, so maybe it's something weird with the custom roms. I'm also rooted with magisk. Anyone got any ideas, or has anyone ever experienced this issue when running custom roms on this phone? Any ideas, or suggestions are welcome. Thanks
Hi, I have this problem too. Of course inside the pubg mobile game. To temporarily solve this problem, first turn off the phone and connect the headphones when the operating system logo is displayed. A hissing sound is heard when plugging in the headphones.
Of course, to avoid this problem, you should use Bluetooth headphones.
Hi, I just tried your suggestion. it doesn't appear to work. My issue is with the earpiece, not headphones. Headphones for me have always worked flawlessly when running custom roms or stock. My issue is when making calls using the earpiece. Making calls using headphones seems to work fine. However when trying to use the earpiece, i cannot get it to work. What i mean by earpiece, is the top speaker of the phone, the one you have to hold close to your ear when making a call. FOr whatever reason calls always remain on the bottom speaker, and never seem to go to the top speaker aka earpiece. This happens in all calls, and in apps like whatsapp. Has anyone else ever experienced this issue? Again, headphones seem to work fine, and yes I'm rooted, and running a custom rom. When i was running stock, I don't ever remember this happening, but now that i'm running a custom rom, i can't get the earpiece to work. I really don't want to go back to the stock miui rom, but idk maybe i will if a solution can't be found
pielordbrian said:
Hi, I'm having a issue with my redmi note 9 pro. Whenever i try to make a call, it always goes to speakerphone. I cannot get it to go to the earpiece. WHen i try turning off speakerphone, the audio is still routed through the bottom speaker, and the person on the end of the call notices i sound broken up. WHen i swotch on the speakerphone the sound is clear, and then the person can hear me just fine. I've tried with whatsapp, google voice, and the regular phone app, and all have the same issue. I'm running Evolution X currently as my rom, but i've tried lineage os, and it has the same bug. On stock MIUI I don't remember having this issue, so maybe it's something weird with the custom roms. I'm also rooted with magisk. Anyone got any ideas, or has anyone ever experienced this issue when running custom roms on this phone? Any ideas, or suggestions are welcome. Thanks
Click to expand...
Click to collapse
I am having the same issue! any solution please let me know!
I am having the same problem - BUT on stock MIUI 12.5 - it started happening after I upgraded. If I could go back I would, but am happy to flasha new ROM if that will fix it.
I was thinking of flashing Lineage 18.1 but if that is having the save issue I ont bother. It must be a note 9 pro issue seeing as I only have the stock version..
I wonder if anyone at all has fixed this issue. I even contact xiaomi technical support but they were useless!
Anybody found its solution please update?
I'm having the exact same issue. When I initiate call it's on loudspeaker even though I didn't select that option. The other side can't hear me well. When I select "speaker" then it's still on loudspeaker, as it should be, and the other person can hear me fine.
I had the problem on crDroid (Android 12) and am currently experiencing the same problem on Pixel Experience (Android 12).
Please help someone us
I found the solution when I changed sim 1 to sim 2 the problem was solved.
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Not quite sure I follow. Are you saying to remove sim 1? Or are you saying to change the default calling sim to sim 2 or something? I should note that I'm using both sims and a SD card. Are you saying I should just use sim slot 2?
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Short version:
OK, so I just tried your advice, and it WORKED.
Long Version:
Ok, so I first removed both sims with the phone off. Then i put one of my 2 sims ONLY in slot 2 like you said. I inserted it into the phone, booted it up, and made a test call. To my surprise, the phone wasn't on speaker. I couldn't beileve it. I tried again, and it worked. I switched to speaker, now it's on speaker. I turned off the speaker and it was back to the earpeice! I tried whatsapp, and same result, the earpiece was working. I then decided to shut the phone down, and put the both sim 1 and 2 back in the phone. Guess what? after booting the phone up again, and making a test call, it still works! I don't understand the rhyme or reason behind it, but I'm not complaining. I'm so happy it FINALLY works.
to recap, Basically here are the steps:
1. Turn Off phone
2. Remove both sim cards.
3. Put a sim only in slot 2
4. Turn on phone and make a test call, it should no longer be on speaker!
5. go ahead and shut down the phone, and put a sim in both slots, if you are using 2 sims.
6. Turn the phone back on, and make a test call. It should still be working on the earpiece!
yes - this worked for me also - I have been looking for so long. A simple and un-remarkab le solution to a serious problem. Xiaomi should have been able to solve this.
All the same - thank you!
Great phone that was hindered for quite a few months by this serious problem
Again - thank you !
mamamoiryani said:
I found the solution when I changed sim 1 to sim 2 the problem was solved.
Click to expand...
Click to collapse
Thank you so much. I have been waiting for it for more than a year.