Hey all, I'm wondering if anyone else has had issues with calls after upgrading to Android 13.
I am having 2 problems with calls
1) When I pick up calls on Bluetooth or loudspeaker, often people can't hear me until I switch to holding the phone to my ear, I can then switch back to Bluetooth or loudspeaker, and it works.
2) when I put a call on mute it automatically unmutes after about 20 seconds even though it still shows the mute button as turned on.
These issues happen on multiple different diallers, so they are clearly a phone problem and not to do with a specific dialler app.
Same here. Let's wait for an update. Temporaly I using a wired headset.
Related
I use an, admitedly ancient, Icon BT Headset for calls while driving, and all works well with one annoying problem.
With all other phones that I have used this with, the Headset synchronises completely with the phone. By this I mean that once connected, the phone's speaker is disabled and all keypad sounds, tones and other noises come through the Headset. To answer a call I could press "answer" on the phone OR press the button on the Headset, and the same to hang-up. Lovely Jubbly.
However, with the Blackstone, I have to Slide to Answer the Phone and then press the button on the Headset to activate that. Pressing the Button on the Headset alone does not answer the phone but instead tries to activate the Voice Dialling function, whether or not there is an incoming call.
The only noises that come through the headset, except while "in a call" are the ring tones.
Now, I ask, is this a problem with the Headset or, is that just the way things are with the Blackstone and BT Headsets?
If it's just that mine is old and knackered then I will get a new one, but i do not want to shell out for something that is not going to fix the problem.
OK. How about I rephrase the question.
Most of you out there use BT Headsets of some description. Which ones work like a common or garden phone?
Any? None?
Just want some advice before shelling out on trying to fix a problem that may or not be fixable.
Before you go spending money, try this software. It is fully featured and free for 15 days. It is an alternate bluetooth stack for Windows Mobile. See if it fixes your situation.
thanks for the advice.
been away, so only just got the message.
have installed. will report back with how it goes.
I searched the forums and google for this issue with no avail. I am pretty sure this is a issue of Cyanogenmod (I think I read that somewhere) but I still would like to know if there is a fix I can apply.
I am on Inferior Human Organs Purity X (On Optimus V). When I am on an internet call (only internet calls; regular calls work but I don't use those) and press the speakerphone button, it turns on for a split second on the speaker then re-routes through the ear piece. The icon stays on the notification bar but the call does not stay in speaker mode for more than a split second. Is there any remedy for this issue?
Hi all,
Can't find any info on this topic, so therefore this post.
Phone is a galaxy S2 9100.
Headset tried Plantronics Voyager Pro and Discovery 975.
Outgoing calls work fine, exept when screen turns black, then after about 10-15 sec, sound in bluetooth dies. Can be reactivated when pressing home button, which brings the screen back.
Incoming calls (around 50% times), I can hear beeping in the headset, I can pick up the call (using headset or soft key), and can hear the caller speak. But the caller can't hear me. If I switch to speaker, still the same. But found out that if I press home button, which exits to home screen, then return back to phone app, the sound in bluetooth headset appears.
Another annoying thing is that when I'm at home, wifi is on and connected, sound is fine with no distortions or bluetooth fallouts. As soon as I leave home = no home wifi connection, every maybe 30 sec, I hear choppy sound in my bluetooth headset (the caller hears me just fine). I can make it go away by disabling wifi while in-call.
Have of course tried several different mods in service menu, although it helped a bit on the sound volume and echo, the bluetooth problems are the same.
Details:
Tried different phone.apk mods all the same
Tried different roms, all seem to behave the same
android: 2.3.6
Baseband: I9100XXKF2
Kernel: [email protected] #66
Build number: CheckROM RevoHD V4
macfreak said:
Hi all,
Can't find any info on this topic, so therefore this post.
Phone is a galaxy S2 9100.
Headset tried Plantronics Voyager Pro and Discovery 975.
Outgoing calls work fine, exept when screen turns black, then after about 10-15 sec, sound in bluetooth dies. Can be reactivated when pressing home button, which brings the screen back.
Incoming calls (around 50% times), I can hear beeping in the headset, I can pick up the call (using headset or soft key), and can hear the caller speak. But the caller can't hear me. If I switch to speaker, still the same. But found out that if I press home button, which exits to home screen, then return back to phone app, the sound in bluetooth headset appears.
Another annoying thing is that when I'm at home, wifi is on and connected, sound is fine with no distortions or bluetooth fallouts. As soon as I leave home = no home wifi connection, every maybe 30 sec, I hear choppy sound in my bluetooth headset (the caller hears me just fine). I can make it go away by disabling wifi while in-call.
Have of course tried several different mods in service menu, although it helped a bit on the sound volume and echo, the bluetooth problems are the same.
Details:
Tried different phone.apk mods all the same
Tried different roms, all seem to behave the same
android: 2.3.6
Baseband: I9100XXKF2
Kernel: [email protected] #66
Build number: CheckROM RevoHD V4
Click to expand...
Click to collapse
Tried different roms, phone.apk's, resetting dalvik cache, system cache and still no luck.
Today I did a "full wipe", installed CheckROM RevoHD v6 and the problem seems to have disappeared. Made 5 incoming calls and bluetooth seems to be working as it should. Maybe it was just a question of wiping the /data partition...
Hello,
I'm new to this site so apologies if I'm in the wrong place or this has been raised before but I've googled with no joy..
I have a Samsung Galaxy S3 i9300 uk unlocked.
For the last month or so m having problems with Bluetooth devices and loudspeaker (seems to be connected)
I can connect to bluetooth devices fine, beats wireless and vw car bluetooth.
It connects automatically and I can talk and hear fine, after a while the sounds drops and it goes echo like, I can't hear the other person at all but on the phone the green button Nader headset is still lit up and the connection is still made. I have to press the headset button to in light it/disconnect it and then re press to connect / light the button back up. I then can hear the person again but it does this continuously throughout the call. Listening to music via Bluetooth is fine and this problem doesnt arise.
When using loudspeaker it's the same, will go to phone (button lit) and I have to press it again twice to disconnect and reconnect.
Can't find out why this happens. I've done a factory reset and it allowed me a few days of it working fine but then goes back to normal.
Anyone else having this problem? I've read a lot about it disconnecting and having to repair but mine seems to stay connected but just drop the sound?
Cheers
Syak2008
same issues
I am having the same issues... did you find the solution?
Same issues too.. i thought it was my ford bluetooth (POS!)
From time to time it just happens. I hear nothing from the other side while they hear me ok and turning the speaker mode on also doesn't help. Only restart could fix it. It's not something new that happened during the latest update - it was like that for a long time. Is this some known bug and is there a fix?
Thanks
got the same problem now. did you find any fix?
Hi, I'm having the same issues as well.
When i make or receive calls, i can't hear anything from the receiver, unless i plug in my earpiece.
Also, my screen goes completely black and does not respond even when i press the power button, nor when i connect it to the charger. Any workarounds for this?
//running Nougat 7.1 on my 2-year old Sony z5c//