Related
I searched and didn't find any previous postings regarding an issue with Parrot and Audi Hands Free (Bluetooth) car kits and the TyTn.
This issue is only with the TyTn and the Wizard devices work fine.
It seems to pair fine with the car kits but 5 minutes into usage...the TyTn turns the bluetooth off on the device.
Then about 1 min later, turns Bluetooth on again. The cycle then begins Off and then On ....
Here's a link on the Parrot forum.
http://www.parrot.biz/forums/english/viewtopic.php?id=2667
I've got the same problem with my Seat Leon (new model) bluetooth carkit !!!
I think it's the same module as in the Audi (all VAG related cars).
It's very irritating !
I hope they will fix it soon....
http://forum.xda-developers.com/viewtopic.php?t=58789&highlight=
:wink:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Pyranwolf said:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Click to expand...
Click to collapse
I'm going to try this !
I hope that it works.
Thanks anyway.
What kind of Leon do you have ?
I've got an A6 with BT kit and am having this problem. I cannot make/receive a call whilst running my BT GPS device & TomTom, although from reading this the issue may be the Audi kit anyhow.
Are there any fixes available - be it HTC or Audi? Or are there any work-arounds, such as add-on software for the TyTN??
Please help - it is driving me mad. Spoiling what is otherwise a great piece of kit.
I have been having this exact problem with my Audi A4 with Audi Bluetooth.
I did wonder if it was in some way connected with the phone going into sleepy mode as it is being powered by the phone battery.
Also, the bluetooth stops responding after 5-10 minutes, but if I am continously using the phone, it seems to be ok.
Therefore, I think I need to buy an in car charger, and see what happens...
Has anybody else tried this that can confirm it works?
Markee
Just a quick note to Paul_o
My Audi A4 / SPV M3100 / Tom Tom / Bluetooth GPS work fine together.
If I am in Tom Tom, and get an incoming call, the little call window pops up over Tom Tom, Tom Tom carries on and the phone audio is routed through the speakers - the only irritating thing is that the Tom Tom lady keeps interrupting... :wink:
Mark
Hi,
I'm using Vario 2 with Audi Bluetooth and also having the BT ON - BT OFF issues.
These are my findings.
- Without JETWARE software:
- BT goes ON and OFF in the car regardless of the VARIO 2 being on or stand-by, or the phone being battery powered or connected to the car.
- Once a conversation is started the BT connection seems to be remain ON.
- With JETWARE software
- If I leave the screen always on the BT connection stays always ON. Only backlight automatic switch-off is selected
- I have tried several screen toggle programs (which claim that they only power down the screen) but the BT goes OFF in the car after a few minutes.
I'm happy to test any other proposal.
Cheers,
C
What version of JetWare are you running, they have a beta which has settings for the Audi kit, this may help, there is also a registry setting that is meant to change the power settings when bt is connected. An extract from an email conversation with Jetware...
We have also addressed the power issue, but this fix requires a registry change. Please create a DWORD registry value in HKLM\Software\JETware\AGExt named InSessionPower with a value of 0 (valid values are 0-4, with lower values indicating greater power availability). This will tell the OS that the Bluetooth device should stay at full power while it is in a Hands-free session.
Not sure if this will help, my Hermes is ariving on Monday, I'm was hoping that all the problems i've had with my magicain and the audi kit would go away with the Hermes, but maybe not.
Give the key a go and let me know
Hi dh,
thanks for your reply.
I haven't installed the Beta version yet. However I have changed the registry setting and will test first thing tomorrow. If this doesn't fix the problem I will try the Beta version with the Audi setting.
I'll keep you posted.
Cheers,
Carles
Hi dh,
I have tested the two proposals (Change in the registry and the Beta version + Audi settings) without much luck. The BT connection with the car keeps going ON and OFF when the phone is running on battery.
Have you got your Hermes? any luck?
Thanks,
Carles
Got my Hermes (Orange M3100) a couple of days ago. I've installed the JetWare extention, and without the InSessionPower set the connection is dropped. So far with the setting applied it has stayed connected. I have had other problems like not being able to make calls etc, which is a bit of a issue. I need to do some more testing, as i've been messing with the phone a bit.
I'll update here in a couple of days
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Hi dh,
You will see from my previous postings I have had the same problems too.
It should be noted, though, that the Vario (wizard) worked flawlessly with the Audi A4 Bluetooth without Jetware software.
Has anybody been able to prove there is no problems if the phone (SPVM3100) is powered whilst in the car?
Cheers
Mark
I have a factory fitted hands free system in my Vauxhall. Every other phone you can think of works with it...EXCEPT my XDA mini. It seems to pair up, but there is no signal showing from the carkit. It might work for a minute and then it drops out. Is it the XDA or Vauxhall that's at fault? It seems that nobody knows the answer and I paid serious money for this bit of car kit. I like the phone, it really is annoying. I have tried another XDA mini as well and that doesn't work either. Does anybody else have a Vauxhall with the same built-in system and not connecting?
Markee
I've had the phone plugged in without the registry entry and it seemed to be ok. If I can get to a stage of a working solution i'll test again without the registry entry and with external power.
dh said:
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Click to expand...
Click to collapse
I'm guessing that since they went from BT1.1 to BT2.0 they had to make a new stack.
My Wizard worked PERFECTLY on my Parrot, my TyTN is almost useless on it.
you make a very good point ScottC, that'll be what it is.
Just driven home and could not make a single call with Jetware installed. Removed it and i could at least make a call, but i didn't get any status info or phone book. I didn't get a chance to leave it connected without Jetware for longer enough to see if it disconnected without external power, i imagine it will. I will test some more later/tomorrow. I'll also send an email to Jetware to see what there thoughts are regarding bt v2.0 and their product
Hello,
I have an Audi A3 with the factory fitted Phone kit but without the Audi Craddle so I'm using the Bluetooth connection.
I have tried the Vario (Wizard/QTEK 9100) and Vario 2 (Hermes/TyTN) and had similar problems with the two of them. Once the connection is stablished I can make and receive calls without problems. The issue is that the BT connection goes ON and OFF without an apparent reason.
The only thing I have seen is that when the Vario is kept on (only the backlight is off) the BT connection normally stays ON, regardless of the phone being powered or not.
I have tried Jetware, the Beta version, the registry entry, programs to switch off the screen...but haven't seen any real difference.
I have bought a bluetooth USB stick and will do some test at home to see if the problem is with the car or the phone.
I called T-mobile and they said it was a faulty phone, but I don't think so.
Keep the postings, we might end up finding a solution
Cheers
C
Try upgrade the BT software. I had the same problem after that i upgraded de Parrot software. Now i have the version 4.16
Hi All,
I have been reading a lot of messages on both 8525 and 8125 trying to isolate the issue and there doesn't seem to be a straight asnwer anywhere and hence I am trying to get the attention of the users here...
I have a pioneer navigation system with a bluetooth built-in. My previous phone (blackberry) and my wife's treo650 both stay connected with car's bluetooth when on call (never a disconnect). But my new 8525 gets disconnected mid-call (usually after 2 to 5mins, but have also seen a disconnect within 1min). That is, it does pair with the car kit and when there is no call going on, the bluetooth connection never dies. This disconnect only happens mid-call, almost all the times.
I have the latest ROM (1,34.502...., radio: 1.16), got the phone about 2 weeks ago from Amazon.com. Called cingular and they say could be faulty phone and I have searched other forums like audi message board where their car kits are also having the same disconnect problem with 8525, so I doubt this is a single phone issue.
I have taken the 'band' hack and forced the phone to be in either GSM or WCDMA mode and in either modes, the phone still exhibits the same problem (there might not be any connection between the two at all, bluetooth with GSM/WCDMA, but thought there might be some weird connection...but not the case thankfully).
I read somewhere about some bluetooth tweaks on 8125, but never found what those were. I need some help here otherwise I am going to return the 8525 and stay away from it. I need the bluetooth to work efficiently.
thanks for all your help
Phal
San Jose, CA
please help
I really need some help, clue or direction on solving or at least isolating this bluetooth issue. I love the 8525 but if I cannot fix this bluetooth mid-call disconnect issue, I will unfortunately have to return, which I don't want.
What headsets the 8525 works fine with (no drops mid-call)? May be that is a starting point.
Please also give me some links to 8125 tweaks that some talked about? pof/other moderators/anyone?
thanks a lot in advance!!
Phal
I have an Motorola H700, and every once in a while it will disconnect, looking at the phone after that, BT is turned off, turn it back on and it works again...
There are problems with the hardware and the API used to access it, good phone, but I don't think it was ready for the market yet when they released it. It is likely to be corrected in the next ROM release, last I heard from Cingular is mid 2007, but by the way things go, prolly around late 07/early 08.
I'm having similar issues with the BT headset I use, which is a Samsung WEP150. It'll drop midcall to the handset. I'll look and BT is turned off.
The only remote correllation I've found is that it seems to occur when I've received a new email or something a la ActiveStink.. And I haven't really been able to confirm that... But I have definitely noticed it happening then though.
my 8525 does this as well with my factory BT in my 05 Acura TL. Kind of frustrating, have not been able to figure it out yet.
Problems w/ Audi BT as well
Same issues with my Audi Q7 BT. I have seen posts in this and other forums blaming the MS bluetooth stack.
My 8525 worked flawlessly with my Garmin NUVI 660, never disconnected or failed to connect automatically. This is frustrating.
8525 Fix
I had the same problem with the 8525 and my Pioneer Avic-Z1 bluetooth kit.
I hacked the registry to force the bluetooth radio to stay ON, rather than going into sleep mode. This seems to have fixed the problem (although with limited testing at this point).
My calls would consistently disconnect with 2-4 minutes. After the hack, I've had 2 45-minute+ conversations with no trouble.
Here's the fix... install a registry editor (like PHMedit), and add a DWORD here:
HKLM\System\CurrentControlSet\Control\Power\State\ Suspend
Add a DWORD called btl1: (note the colon, the colon must be there), with a DWORD value of 2.
Good luck!
My Q7 as well i took the advice of wolfgram and did this to my phone i will let you know how it works it would be a shame to give up this phone but it is really useless if this feature does not work right.
Well this is what i did i did what wolfgram said and it still cut out but not as much so i took the checks off in the advance power mode and never let the phone go to sleep and it works all the time. HTC needs to upgrade thier bluetooth setting not to go to sleep. It must stay active at all times MY phone book and all other info posted into my Q7 with no issues at all and it even sees the bluetooth b4 the MMI system in the car Boots up..
Lance
Resolution I think
I turned off 'Making device discoverable to other devices' and it seems to have solved this problem, I am using the phone with a parrot kit and it kept disconnecting now it works all the time.
Treo 750 doesn't have this problem
Well, hopefully you owners of Hermes have figured out the fix. I had to return it and now got the Treo 750 and can gladly say the problem is not there. The treo 750 has the v1.2, but I guess following the replies here, that possibly Palm fixed the problem by keeping the BT radio on at all times.
In any case, here is the post I wrote in avic411.com forum - if you want to see any follow up responses by other owners..
http://avic411.com/forum/viewtopic.php?p=24170
cheers
Phal
Bluetooth cut out
I am having the problem too with the garmin Nuvi and the Tytn - which is ineresting seeing as how one poster had no problem with the Garmin device. Here is something else that is interesting - I did not have the problem when I had the HTC 1.18 Rom installed. After I flashed the HTC 1.35 Rom, the problem began. I have already tried upgrading my firmware on the Nuvi - that did not help. I also use a Nokia 800 bluetooth headset - and that never cuts out with either ROM. I will try turning off the bluetooth discovery first. If that does not work, will try editing the registry. Keep you posted.
Turning off bluetooth discovery did not work.
Turning Off Bluetooth Did Not Work For Me Either
this worked for me.....
http://forum.xda-developers.com/showthread.php?t=247520&page=10
drains the battery quicker, but no more bluetooth problems.....
Hey guys, has anybody found a solution for the auto turning off of the BT in suspend mode? its gettin really annoying
After many frustrating weeks of problems pairing my TYTN2 and Parrot3100 I have stumbled upon a fix that actually works (for me anyway).
After trying all of the usual fixes (upgrading firmware, running jetware, Bluetooth hotfix etc.)with no success at all, it seems that the way to go is to downgrade the parrot to version 4.15b of the CK3300. This is apparently quite safe as the only difference is that the 3300 has gps (however you flash at your own risk). See here, post #14 http://www.parrot.com/forums/english/viewtopic.php?id=5054.
Hope this helps, post any results to confirm that this was no fluke.
Parrot released 4.17a firmware. This finally helps my tytn working perfectly in combination with jetware. Even navigation instructions pass through my car's speakers when I press the call initiate button on my carkit.
Is the 3300's software working better?
I downgraded from the 3100 v4.17a to the 3300 v 4.15b and the only difference from my old phones is that the parrot no longer syncs the contacts. But that is no problem as I am running Voice Commander 1.6 anyway, which by the way is working perfectly now too.
I received the message below from Parrot today as I had an open ticket regarding the CK3100 and my Tilt. It will be the end of next week before I can do the update, as I will be on vacation starting tomorrow.
Hello,
Parrot has released new software for the CK3100 & the 3200LS that resolves the audio transfer issue with HTC touch screen phones. Please update your car kit to the latest version using our Parrot Software Update Tool & a Bluetooth enabled computer. Be sure to delete the car kit from your phone's Bluetooth settings after updating. You will need to re-pair your phone to the car kit. Failure to do so may result in erratic behavior.
Link for Update Tool & instructions:
http://www.parrot.com/usa/support/downloads
updated the firmware to 4.17a this afternoon. So far, so good, but my phantom dialing and random engagement of the mute switch were intermittent before. Will post again in a week or so if the problems don't materialize before then.
Hey Folks!
Great work here... Coming from WM/Symbian/Blackberry I'll try Android for daily use now.
My actual only problem is, that my Hero won't reconnect with the bluetooth System MMI of my Audi A6. Pairing is fine, manually connecting works, but I found no way to automatically reconnect the Hero with MMI when I enter the car and turn on the ignition/engine.
Every other handset does this comfortable reconnect (Nokia E71, Blackberry Curve 8900, Palm Treo 750...).
Is this a problem of my Hero or of Android itself? Is there a workaround to solve the problem to get an automatic reconnect?
Thanx!
Tom
Maybe the problem with the Hero. I cannot connect the Hero to my BMW I-Drive at all.
My G1 connected to my alpine stereo fine, when it did a small microphone appeared on the stereo along with the bluetooth icon. The hero pairs, the bluetooth appears and the phonebook is browsable, however it doesnt display the mic icon on the stereo. I think this means it's not using the stereo to pick up voice. I need to test more.
It would appear that there is something different about the bluetooth stack on the hero. Which is worrying with it being a hybrid android build
There is definitely something different. My old G1 pairs and works flawlessly with my BMW I-drive. The Hero pairs but won't connect.
Works with my Audi A4 2009. Autoconnects, I can browse my contacts etc...
Lox_Dev said:
Works with my Audi A4 2009. Autoconnects, I can browse my contacts etc...
Click to expand...
Click to collapse
That's positive. Are your contacts on your SIM or straight from a Google account? Do you have the latest MMI?
I'm about to take delivery of an A6 with HDD 3G MMI with bluetooth and wondering what to expect.
I have some issues on Skoda Octavia as well. As Skoda/Audi/VW have some things in common, I thought to mention this.
Usually my Hero works fine, but maybe 33% of the times I cannot initiate a call from car bluetooth. It starts to make a call, but fails, on Hero I get some MMI error (have to write that down the next time I get it).
When the error occurs, I can still start a call from Hero and phone audio comes nicely through car bluetooth and stereo. It requires me to turn off the engine and turn it back on to get it working again, however, sometimes it will also start working by itself. Might be that if I initiate a call from phone, it will start working from car controls as well, but I cannot confirm that.
Ik works fine on my 2006 A4 MMI, and I did test it on my new A4 2009 Model coming in december.
No issues, both show contacts and auto connect.
Did you set the MMI device as "trusted"?
Automatic connection works fine with my Audi A6 4f MMI!
After a few seconds I have access to all Contacts through MMI.
No Problems at all..
Cheers, Otze
I just have a Motorola bluetooth/FM transmitter. It's not perfect, but what I have to do is turn the Hero's bluetooth on *AFTER* the Motorola unit is initialized. So maybe enter your car with the Hero's bluetooth off, turn on the car, then once the stereo's booted up, turn on the Hero's bluetooth.
It's a bit inconvenient, but it works for me.
Also, I suspect that when we get the Eclair update, our bluetooth will work better, as Eclair is said to finally include a bluetooth API (which has been missing from previous versions, as Google said they wanted to polish it up before releasing it to developers.)
ever since my G1 updated from 1.1 to 1.5, it has not been compatible with my nissan handsfree bluetooth system. i waited until another update, and now that i have my nexus one and it still doesn't work, i'm a little disappointed.
i am able to pair my phone to the car, but when i make or receive a call the car speakers shut off (as they should) but the audio comes out of the phone. i don't even know about whether or not the other people can hear me.
is this a known android issue? it may even be a nissan issue, but i'm sure it can be fixed within android (seeing as how my g1 used to do this). i'm 99% sure there's no easy way to update the nissan bluetooth firmware to help this.
anyone experiencing the same thing and is there some fix out there or some effort?
Well, I don't have a android device or nissan hands-free, but I do use a Touch Pro 2 with my sync equipped ford. Anyway, I had a very similar issue, and I had to go into the bluetooth manager and change a setting that had it default to audio over the hands-free device, rather than some other thing... It has worked great ever since then. Oh, I also learned that I had to answer the call using only the car's answer buttons otherwise if I hit answer on the device it would again send the audio only to the phone's speakers. Of course that seems logical, but my phone prior to that would allow me to answer and speak through the hands-free with either method of answering the phone.
At least it's something to look into.
Also, the phone I had before the TP2 required that I update my sync software before it would work. However, it wouldn't even pair before the update, so I don't think that's your issue. I don't know what the procedure is for updating your nissan firmware, but sync simply involves downloading a system version checker to a usb drive, plugging it into the car, return to computer and download available updates, and then return to car to install updates. I would guess nissan would have a similar method?
I realize we're dealing with two completely different systems here, but I figured I would chime in anyway since I had a very similar situation.
My Acura handsfree works like a charm. Perhaps you have too many contacts that are syncing?
awee man... I was hoping that there were no nissan/infiniti bt issues w/ this phone
I'll find out Saturday when I finally pick it up from the fedex place
rossiscatch said:
Well, I don't have a android device or nissan hands-free, but I do use a Touch Pro 2 with my sync equipped ford. Anyway, I had a very similar issue, and I had to go into the bluetooth manager and change a setting that had it default to audio over the hands-free device, rather than some other thing... It has worked great ever since then. Oh, I also learned that I had to answer the call using only the car's answer buttons otherwise if I hit answer on the device it would again send the audio only to the phone's speakers. Of course that seems logical, but my phone prior to that would allow me to answer and speak through the hands-free with either method of answering the phone.
At least it's something to look into.
Also, the phone I had before the TP2 required that I update my sync software before it would work. However, it wouldn't even pair before the update, so I don't think that's your issue. I don't know what the procedure is for updating your nissan firmware, but sync simply involves downloading a system version checker to a usb drive, plugging it into the car, return to computer and download available updates, and then return to car to install updates. I would guess nissan would have a similar method?
I realize we're dealing with two completely different systems here, but I figured I would chime in anyway since I had a very similar situation.
Click to expand...
Click to collapse
haha yeah, i don't have a "bluetooth settings manager" on my car, and i don't think i can update the firmware...which is ridiculous.
also, to the acura guy, my contacts aren't even syncing
niiiick said:
ever since my G1 updated from 1.1 to 1.5, it has not been compatible with my nissan handsfree bluetooth system. i waited until another update, and now that i have my nexus one and it still doesn't work, i'm a little disappointed.
i am able to pair my phone to the car, but when i make or receive a call the car speakers shut off (as they should) but the audio comes out of the phone. i don't even know about whether or not the other people can hear me.
is this a known android issue? it may even be a nissan issue, but i'm sure it can be fixed within android (seeing as how my g1 used to do this). i'm 99% sure there's no easy way to update the nissan bluetooth firmware to help this.
anyone experiencing the same thing and is there some fix out there or some effort?
Click to expand...
Click to collapse
I also just got an N1 and my Nissan handsfee bluetooth lets me voice-dial but the call doesn't get routed through the handsfree system. I have to take the phone out of my pocket and activate the speakerphone. Any solution would be much appreciated.
I don't have teh same system. Like the previous poster I use the N1 with my Ford Sync. If a call is initiated from the phone it starts out in "private" mode using my phone's speakers. If initiated from the car it uses the car's sound system. There's also an option in there allowing you to choose the default sound output of calls. I have the latest firmware installed.
That actually makes sense.. my previous phone always used the speakers which was a bit of a shock sometimes when I was sat in a car park wanting to make a quick call. Clearly it still has some rough edges on some cars.