I've got a strange problem with my 7t.
When it's connected with my 2019 Volvo xc60 and I want to make a call after press call.... nothing happens until I touch the screen auf my phone.
It happens not every call so this make it very odd.
Carkit is stored under smartlock!
Have anybody the same issue?
Related
Hello. My first posting. I have looked to see if this has already been asked.... After using mute or vibrate function on my XDA 2s unit, and then switching to making a call or trying to receive a call I can't hear the dial tone, or the other person on the other end of the call. I can only make and receive calls once I soft reset the unit. This is becoming a regular occurence. Any ideas would be much apprecaited.
Craig.
same problem
I also have same problem. my XDA IIs often have a problem with the incoming/outgoing calls which is I can't hear the tone nor the person's on the other end of the call (but the person on the other end of the call could hear my voice). It often (not always) happens without the device had a recent setting change or running program so on one occassion it just handles the calls perfectly and suddenly the problem happens and I also have to soft-reset it to make it back to normal, and it is becoming regular.
This is unfortunately a well known bug that none radio upgrade could solve so far...
Look at : http://forum.xda-developers.com/viewtopic.php?t=40417
The problem seems to occur only when Bluetooth is off... So the solution is to turn Bt On (and then off if you wish so) and it's ok without soft reset...
The best way to avoid it is to let Bt ON but to uncheck "Allow other devices to detect me" (forgive me if the english translation is not accurate but my PocketPC is in French) in the Bt parameters to avoid power consumption.
It worked for me so have a try
For some reason, whenever I get a call from an "Unknown" number the phone does not ring, it only vibrates. Consequently, if the phone is sitting on the table I rarely hear these calls come in. Most often, it is my brother calling from work where they have a VoIP system that does not transmit caller ID. What is causing this and what can I do to fix it? Anyone else have this issue?
Nobody else has this problem with their incoming calls?
Ive had that issue before and the only way I know to fix it is a hard reset
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.
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.
Having a strange problem on my S20U Exynos. I'm connected to my Sony Bluetooth head unit in my car and anytime I answer a call it's just silence. I can't hear anything. But if I make a call then everything works perfectly. Any thoughts on how to fix the incoming call issue? It's getting annoying having to turn off Bluetooth when I answer the phone.
Have this problem with my 2013 Infiniti but both making and answering calls. Suspect its a bluetooth codec issue and maybe changing that in developer settings helps, but haven't had time to play around.