I'm currently using an LG G3 Vs985 on Sky Dragon 5.0
I'm also using T-mobile on the LG G3
I use my phone for work a lot and the most annoying thing is happening. While I am using my bluetooth headset and talking on a call, if somebody tries to call me and my screen is telling to either accept or deny the incoming call, my bluetooth speaker drops to handset volume. I have to deny the incoming call, then quickly tap to turn off bluetooth and bluetooth again to get the call back to my bluetooth.
While already on a a call if somebody is talking to me while an incoming call comes in, I miss an entire sentance or two before i can do all of the above to get the audio back to bluetooth.
Is this a wrong setting I have on the phone or simply a bug with either Lollipop or Skydraggon?
"Edit" I got so annoyed I went to my wired headphones and I noticed the issue is not happening on my headphones. I didn't expect to happen but i wanted to note that the audio does not drop to handset speaker while using wired headset.
I appreciate the help.
I wanted to update the post that either it was a phone reboot or possibly of me flashing the Skydragon 4.2 kernal to the phone that fixed the issue. So far as of right now the audio is not dropping when talking or listening on an active call with another incoming call requesting to be accepted or denied.
Edit: The issue has returned. This is goofy !! lol
Related
Wanted to ask if anybody else is having dropped calls?
Using the headset included in the box and another one that I have that I know works the call kept cutting out after 5 minutes or so and then the call hanging if I did not wake up the screen.
I thought it was a phone issue obviously, but if I leave the screen on and play around with it, then the phone call does not hang.....
Also if the sound cut out and before the call was dropped, if I wokeup the screen then we could hear each other again.
Has anyone else got this issue? I am on the original Three firmware v1.26.xxx, handset was sim locked but now sim unlocked.....
And since then I have tried calling with just the speakerphone and the call did not drop, not used the phone for long or with the speaker near my ear as I usually use a headset.
Thanks.
Bump, someone must have used the headset and made a long 10 minute+ call?
Using without a headset and the speakerphone the call has not dropped.
I only use a bluetooth headset but i don't seem to have problems with it (and i realy talk alot at the phone).
Just FYI this does not happen anymore for me after installing the 1.28 update from Three..... Still waiting on the other updates for other fixes!
Hi guys, hope you can help with an odd problem...
Very, very occasionally (maybe 1 in 50 calls) I get an issue where I can't hear the other party, as if the earpiece was dead. If I drop the call and re-dial, 99% of the time everything is fine. (I think I had one time in 6 months where the 2nd call did the same.)
Now, I can't decide if this is a network issue (Vodafone) or a phone issue. I mostly use a Bluetooth headset due to the size of the Note but I doubt it's headset related as I have tried two different high end brands and it happens with either.
Things I have noticed:
Problem applies to incoming AND outgoing calls
I have checked I haven't accidently muted the call
My Bluetooth headsets all chime at the start of a call but there is no call audio
The other party can hear me but I can't hear them
System sounds are all fine, only call audio is affected
Switching between headset, phone and speaker phone make no difference
Applies to all incoming call audio, including ringing tones and busy tones
I reboot my phone sometimes but as the issue is rare I couldn't say if it makes a difference. Also this is a standard Note II (not a branded Vodafone one) with all the latest patches downloaded. Looking through my app downloads I can't see any obvious ones that might affect the phone. Apart from the stock Samsung apps I most connect to CCTV systems. I have CSipSimple but I haven't used it in ages.
Any suggestions on how to investigate this further?
Regards,
Andy
Seriously... no ideas?
So, no one's ever had this problem and no one has any ideas?!
:crying:
I recently bought a BT car speakerphone and tried to place a call using my Xperia ZL (on 4.2.2). The call goes thru but I cannot hear anything from the speaker. I can hear sound if I play music but nothing if I make a phone call. I checked with my wife’s ZL (on 4.3) and the BT speaker works fine.
I tried my phone with another BT speaker and still no go for voice calls. Music is fine though. I believe there is an issue with the phone calls over the BT connection.
Anybody else experienced this issue? Any possible fix? I hate to send it back to Sony. Thanks
Hello people,
I have the LG Optimus G Pro from at&t, but I am using it with PureTalk GSM. It was working great for about a month; I was able to call, SMS, and use wifi, but I didn't have mobile data, because I didn't need it. For some unknown reason, all of the sudden I am not able to hear anyone who calls me, and they can't hear me either. Everything else still works, so I'm still using it for texting, but no matter who I try to call, there is no sound whatsoever. Not even static. But I know the call connected because the phone I call will ring, and when they answer it, my phone vibrates once to let me know when the call connects, but while their phone is ringing, I don't hear a ringing noise in my phone. Also, I've tried using speakerphone, and that doesn't work, but it will for any other audio. I can hear the dialing noises through the earpiece if I use the keypad during a call, so the earpiece works. I've also tried connecting to Bluetooth and it pairs and connects successfully, but still no call audio other than dialpad. And I've also tried connecting headphones, but still nothing. I called my service provider from another phone and they reset my account, but that didn't help, so I restored my phone to factory settings and that still didn't help. Does anyone have any idea why this would happen?
Thanks in advance!!
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.