I successfully paired Cingular8525 with Acura 2007 HandsFreeLink. But after it report successfull pairing, I can not use it. It saying phone not found. I use same phone before with PArot system without any problem.
If you go to Acura web site they report 8125 will not support call waiting and data link, but will support basic phone functions. But it does not work for me. Does anyone succesfully paired 8525 with Acura HandsFreeLink? Is 8525 better then 8125 in list of futures supported by acura?
Thanks
I successfully use the 8525 with my Acura TL's Bluetooth. (Previously used an 8125). It works, but occasionally it will drop the Bluetooth connection. This seems to be a known issue with Bluetooth on the 8525.
BTW To get battery level and signal strength meter on the Acura, you need to get the following program:
http://www.jetwaremobile.com
Mike
I have the same problem with my 2005 BMW 545i. Only stays connected when I leave the screen on. If I hybernate it, I lose bluetooth connection. The Jetware program did not seem to help.
sign up for the jetware beta -- might help
my TL also randomly drops the connection as well.
Question, when you answer an incoming call, does the HFL beep twice? Mine does, and the people on the other line can hear the second beep....
Oh well, just live with it I guess....
Bluetooth Acura paudible Tone problem
Yes, I also get dropped more than occasionally in the Acura bluetooth connection. Any fixes? Another Acura problem for me is that when audible tones are created to SEND tone data replies ( " hit 7 to disconnect"), the last tone in teh sudible series sticks and hangs on for 10 seconds or so. The tone message is sent and recieved, so the call actions continue in the background to the tone. Cingular says hardware and send back phone. Any alternative ideas ,or does everyone else have tone work ok?
Bluetooth Acura audible Tone problem
Yes, I also get dropped more than occasionally in the Acura bluetooth connection. Any fixes? Another Acura problem for me is that when audible tones are created to SEND tone data replies ( " hit 7 to disconnect"), the last tone in the audible series sticks and hangs on for 10 seconds or so. The tone message is sent and recieved, so the call actions continue in the background to the tone. Cingular says hardware and send back phone. Any alternative ideas ,or does everyone else have tone work ok?
this actually worked for me, however, the drain on the battery is siginificant, so if you can live with that, I have gone two weeks now without a dropped call....
http://forum.xda-developers.com/showthread.php?t=247520
Hi everybody.
Recently I've purchased a new HTC Hero. Everything is working fine and this gadget is by far the better mobile+PDA i've used.
OK, now the question.
I've paired the device with my bluetooth car handsfree (Toyota Prius) and although everything works fine (I can call and receive calls and both battery and coverage meter display OK) caller id is not working. So when I receive a call, instead of displaying call number or name in handsfree, it gives and error (something like "Unable to display").
Does anybody have the same problem?
This happens both with official 2.73 upgrade and modaco 2.2 (2.73 based).
Thanks in advance.
Hi to all,
I have a problem with my Samsung Galaxy S III, 16GB, Android 4.3, stock rom, and the integrated SIP voip system (Call Settings < Internet calls settings) with bluetooth headset: when I receive a SIP call the audio is not transferred to the bluetooth, I do not hear anything and the microphone does not transmit. Otherwise, when I make a sip call everything works perfectly. I have tried many SIP providers and many BT headset but this issue remain.
It 'possible that some of you do a test to see if the problem is only mine or if it is a S III bug?
Thank you!
Same problem here
axterx said:
Hi to all,
I have a problem with my Samsung Galaxy S III, 16GB, Android 4.3, stock rom, and the integrated SIP voip system (Call Settings < Internet calls settings) with bluetooth headset: when I receive a SIP call the audio is not transferred to the bluetooth, I do not hear anything and the microphone does not transmit. Otherwise, when I make a sip call everything works perfectly. I have tried many SIP providers and many BT headset but this issue remain.
It 'possible that some of you do a test to see if the problem is only mine or if it is a S III bug?
Thank you!
Click to expand...
Click to collapse
I tried to make a skype call through my bt headset (NEXUS10) It works just fine, but when I try to make it with my S3 I have the same issue I dont hear the voice and the microphone was not working, I tried to make modifications to the sound files (root) but I didn't find what the problem was.. I'm using slimkat7 and former user of CM10.2 (
I tried also to make a call but instead of using the BT headset I used the little waterproof speakers (built in mic) and I could make it!! So I have three conclusions (actually they are questions if someone could help me too, I'm:
-You need an a2dp earpiece in order to make VoIP calls (as my speaker that worked)
-It can be the ROM or kernel (I've heard that)
-You need to modify de sound files (root) in order to "unlock" the feauture with the Samsung Galaxy s3.
None of above are actual solutions, I think they could be solutions so if someone could help to make it happen I would be very greatful!
thanks again
I have a rooted micromax bolt A35.
I have got whatsapp calling feature but the mic is not working.. I can hear the receiver but he can't hear me.
On reqular calls mic is working so no hardware problem
Even i can record voice on whatsapp voice note .
How to resolve it.?
I'm on T-Mobile, and I have a T-Mobile supplied S21. My S21 is generally functioning very well.
One problem: If I'm on WiFi calling, and I make a call, the person on the other end can hear me perfectly, but I hear nothing. It's not a trivial issue like my volume is off or the sound is redirected to another device.
If that person calls me, even if I am on WiFi calling---no problem.
If I call out using Google Voice Dialer (WiFi calling, Google Voice number)---no problem.
I have WiFi calling (T-Mobile) enabled. VoLTE enabled.