I've been having a weird issue since I bought my 5X. When I make a call via my car's audio system (VW CC), it takes a long time and says "Call failed", but then will connect shortly after sometimes. I noticed if I unlock the phone via finger print, right after initiating the call, it works fine. So it seems bluetooth is not waking the phone to make the call in a timely manner? Anyone else having a similar issue? Thanks.
Related
Hi,
I am having problems with the HTC One X and my car kit. It connects ok and allows outgoing calls no problem. However incoming calls were automatically answered (worked out it is the stock installed car mode),and a message played to the caller "the person you are calling is currently driving". After that, it is not possible to connect to the caller.
I have now disabled the car mode app and done a hard reset. The phone now still works for outgoing calls. It works for incoming calls, provided it is not plugged into the charger.
If plugged into the charger (cig lighter with non-HTC usb cable),hitting answer (whether on phone or car kit) picks up the call and then the audio goes silent after about 2 seconds. The call can then only be recovered by selecting the audio out as handset, and then re-selecting the car kit. After doing that, everything works fine (provided the caller hasn't hung up in the meantime!).
Has anyone else had similar issues? Any ideas are welcome.
I have tried installing no dock and a tonne of similar apps to no avail.
I have tried enabling the car mode app and answering calls through it (but does the same as above - 2 seconds of audio then audio goes until carkit disconnected and then reconnected during call).
I am running a stock phone, not rooted, with 1.26. I am not encrypting the storage or anything else (I notice there have been threads about enryption and bluetooth problems prior to 1.28).
Thanks
TS
You may have solved this by now but I had a similar problem with my One S. It turned out not to be the phone at fault.
In my case the phone would ring once then fall silent and the car audio would go silent while the incoming caller received the message that I was driving. I had not changed any of the settings on my car so assumed that the phone was at fault.
After trying to change phone settings I had a look at the settings for the Bluetooth on the car, where I found a setting for placing calls on hold. I found that this was set on automatic so I changed it to manual and everything worked properly.
What had been happening was that all incoming calls were being put on hold, which is why the incoming caller received the "driving" message. The caller was actually connected but on hold and if I had pressed the button to swap between callers on hold I would have been connected.
It appears that the setting had always been on automatic but my old phone didn't use the automatic call hold function, which is why I only had the issue when I changed to the One S.
Hope this helps.
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!
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
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.
I have a weird and annoying issue with my 10 (stock 7.0, 2.51.531.32):
During every phone call, after ~1 minute, my microphone seems to cut out for perhaps 10 seconds (as reported by the person at the other end). After that, it works normally again. I just installed "automatic call recorder" so I can start to pin down these numbers precisely.
The microphone(s) pass the HTC hardware tests, and when I use "Voice Recorder" in voice notes mode, it will record for many minutes without any issues. In addition, I don't think this ever happens when I use a Bluetooth headset for calls.
Any suggestions?