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.
Related
I'm sorry if this has been asked in the past, but I was wondering what happens to your navigation screen when a phone call comes in or when you need to place a call? Now it would be nice not to be doing several things at one time, but if a call comes in while you are trying to navigate, doesn't the call menu come on screen? How do you suppress that? Just wondering as I am looking to get a TP2 via AT&T. Thanks.
Dunno about other kit, but my copy of TomTom6 produces a popup on my iPAQ hw6915, and all I hace to do is answer the call (I use a BT headset with it when driving to stay roadsade as much as possible). The voice directions from TomTom remain muted while the call is in progress, by the way.
hi
While using GPS (GARMIN XT), the phone screen appears in case of incoming call.
I always use my bluetooth earphones while using GPS.
GPS voice will be thru the speaker and call on bluetooth.
After the call, the screen turns back the the GPS view automatically.
I have a Samung BT earpiece HM 1500. When I receive a call, the voice of the caller comes out of the earpiece & the phone simultaneously, & ofcourse it'd be so low on both. I then disable BT on the dialer & re-enable it, then the voice comes out of the earpiece only & in great quality. The same thing happens when I connect the phone to my car BT set aswell, so the issue is related to the phone & not the BT sets.
Any solution to this ?
Ok....so it is video caller id that was doing the mess....removed it.....everything back to normal
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'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
Hey everyone,
I have been having issues lately with the handsfree in my car, but this has only happened with the Moto. My previous phone, a Blackberry Priv, worked flawlessly.
Basically, when I make or receive a phone call in the car, the ringer will work, but as soon as I am in the call I cannot hear the other person. They apparently can't hear me either.
Strangely, if I make the call, it sends the instruction to my phone to make the call, then the radio goes silent for the duration of the call, but I have to pick up my phone and use it normally, defeating the purpose of 'hands free'
I have no idea what's going on, or how to get this working again. Any ideas?