My parrot kit ck 3100 wont automatically reconect. I have to go into setting to reconnect it works flawlessly once connected but wont reconnect after ignition cycle
gazeddy said:
My parrot kit ck 3100 wont automatically reconect. I have to go into setting to reconnect it works flawlessly once connected but wont reconnect after ignition cycle
Click to expand...
Click to collapse
Works here without an issue same parrot kit did you allow it to connect automatically? There is a question if you allow permanent connection
Sent from my GT-I9300 using XDA
yep tyurns out my kit needed updating to v 5
pairing without updating
Glad the updating worked for you, but following the procedure described here(http://forum.xda-developers.com/showthread.php?t=1700966&highlight=parrot) I was able to get it to pair successfully using 5.09 Parrot firmware.
Related
I had a N1 previously and it used to pair with my Uconnect in my SRT without any problems. Now this Tbolt pairs and then promptly disconnects and will not re-establish the connection ever again.
Is this a different Bluetooth version then the N1? Anyone else having issues with the TBolt connecting AND maintaining a connection with any of their B.T. equipment?
Any suggestions on what I should try differently?
Have you installed any battery control apps that might be shutting off your bt?
Sent from my ADR6400L using Tapatalk
I noticed mine won't auto connect to my kenwood unit in my car. BT-200 module. I can force it manually, but it should auto connect...my X used to w/o a problem.
The T-Bolt connects to my Jabra headset fine. I haven't installed any power mgmt apps that would be shutting off the BT.
It connects to my UConnect System in my Mopar and stays connected for 10 seconds and the disconnects itself. I can shut off the car , reboot the phone and turn on the car, turn on the phone and it will re-connect again for another 10 seconds and disconnect itself.
I have Uconnect also but no issues. Did you clear your old N1 from Uconnect? Not that that should matter but don't know what else to offer...
Sent from my ADR6400L using XDA App
I have a Lubix NC1. Pairs with TBolt and works fine, but when the display shuts off, so does the Bluetooth. Phone connection stays and I can manually restart the Bluetooth, then same thing happens. Any ideas? Thanks.
Yea, I deleted the N1 from there. Might be something going on with the ROM, as that is the only option I have left that I can guess at?
azturbomini said:
I have Uconnect also but no issues. Did you clear your old N1 from Uconnect? Not that that should matter but don't know what else to offer...
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Having some trouble with the bluetooth on my car kit with the Evo 3D. I have no idea if anyone here can help, but I'll see if you guys have any suggestions. I play podcasts through my car kit to my car stereo. I have been able to successfully pair the phone to the car kit, both for handsfree and a2dp. The problem is that after I turn the car off, the bluetooth fails to reconnect when I turn the car back on. I had an iPod also paired to it and that always reconnected without issue.
If I go into the bluetooth control panel and try to manually connect it, it fails as well. The only way to make it work is to unpair the phone from the car kit, and re-pair it again. After that it works until either the car kit or phone is disconnected again. I'm not sure why it works once, and then not again. Is some app on the phone possibly messing with it?
Any ideas?
Well, it works fine with my iPod, and my Palm Pre, so I tried my wife's LG Optimus. There must be an issue with this car kit and Android phones because it worked about the same with her phone as it does my Evo 3D. I did actually get it to reconnect automatically with her phone once, but could never get it to work again after that. So, off to Amazon I go to look for a new car kit...
I just got my new car yesterday, a 2012 Hyundai Veloster, and my phone refuses to connect to the already paired system unless I actually choose to connect to it.
In my Toyota Matrix in which I installed a Clarion CZ500, I had no problems auto connecting.
Can anyone think of why this might be happening or know of a workaround? Unfortunately, Tasker doesn't have a feature to connect to a Bluetooth device.
Check out the pairing section.
http://www.hyundaiusa.com/bluetooth/bluefaq.aspx
I'm going to try to set it up through the voice interface, but it shouldn't make a difference.
It started working properly all of a sudden.
Sent from my GT-I9100 using xda premium
rickytenzer said:
I just got my new car yesterday, a 2012 Hyundai Veloster, and my phone refuses to connect to the already paired system unless I actually choose to connect to it.
In my Toyota Matrix in which I installed a Clarion CZ500, I had no problems auto connecting.
Can anyone think of why this might be happening or know of a workaround? Unfortunately, Tasker doesn't have a feature to connect to a Bluetooth device.
Click to expand...
Click to collapse
Having the same problem with my Atrix 4G running GB 2.3.4 and my car stereo (Pioneer MVH-8200BT).
Manual connection works fine. This used to work too, I just can't figure out what broke it (2.3 upgrade maybe). I've deleted the BT profiles from both the car stereo and the phone, didn't change anything. (and yes, the car stereo is set to Auto-Connect).
I find this extremely annoying :-/
Is BT on before the car starts? I found that that's the problem.
Sent from my GT-I9100 using xda premium
rickytenzer said:
Is BT on before the car starts? I found that that's the problem.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I'll try to reverse the order and turn the BT on after the radio is fully powered up
At the risk of highjacking an old thread:
How secure is bluetooth.
I'm looking at a bluetooth ignition system.
Function:
When a pairing is made, a relay is turned on.
When the pairing is lost, the relay is turned off.
The device gives no indication, physical or via bluetooth about the relay status.
The device is set to non-discoverable by hardware.
The password is a 20 character alpha-numeric code.
The device performs no function and stores no data, it simply operates from the pairing.
How secure would this be? or more accurately, how much time would likely be required to crack this device assuming no physical access?
Also looked into RFID, but that looks to be easy to crack unless I spend silly money on an active encryption system.
I am having issues with my device not connecting to bluetooth. I am using hYFR on my Galaxy Note... Any suggestions
has the device been paired before to whatever your trying to connect it to? maybe try to delete the pairing configurations from both the phone and device reboot and try to re-pair them?
cjsspape said:
has the device been paired before to whatever your trying to connect it to? maybe try to delete the pairing configurations from both the phone and device reboot and try to re-pair them?
Click to expand...
Click to collapse
+1.
I'm running the same ROM and everything works. A2DP also works flawlessly. Connects to my car instantly.
Hello,
I have upgraded to Android 4.1.2 and my Kernel is JZ054K.I9100XWLSD. Since the upgrade I face problems with bluetooth. Everytime I conncect via bluetooth to our car telephone system (Audi), I get connected. After 30s I get reconnected than connected again. I had version 4.0.4 before and did not have any problems with bluettooth connections to my car. Does anyone have an idea? Does the 4.1.2 in general has this problem? How to fix it?
Thank you very much for any suggestion ort support!
That's strange. How did you update? Does is connect as rSAP or only with Handsfree profile? Did you already try to remove the pairing from the car and to do a new pairing?
I updated three days ago using KIES from 4.0.4 to 4.1.2 and I do not have any problems with connection to my VW FSE Premium. Everything is working like before I didn't even need to do a re-pairing, the old configuration was still working.
AndDiSa said:
That's strange. How did you update? Does is connect as rSAP or only with Handsfree profile? Did you already try to remove the pairing from the car and to do a new pairing?
I updated three days ago using KIES from 4.0.4 to 4.1.2 and I do not have any problems with connection to my VW FSE Premium. Everything is working like before I didn't even need to do a re-pairing, the old configuration was still working.
Click to expand...
Click to collapse
I updated via WiFi. Re-paring was not necessary. I switched not to visibility from 2 Minutes to always. Need to see, if this helps.
I do not need to set/change the visibility on my phone. I switch on bluetooth and when I enter my car, the car "takes" the sim card. When I switch off bluetooth or leave my car, the phone is getting access back to the sim card.
SGS 2 Jelly Bean 4.1.2 - Bluetooth connection problems to car telephone system
AndDiSa said:
I do not need to set/change the visibility on my phone. I switch on bluetooth and when I enter my car, the car "takes" the sim card. When I switch off bluetooth or leave my car, the phone is getting access back to the sim card.
Click to expand...
Click to collapse
I've had similar issues with my SGS2 on ICS and now with 4.1.2 (XXLSJ). I'm convinced the problem is a combination of the phone's current processes and how often the car kit retries to connect. I have a Parrot based bluetooth kit factory fitted in my 2006 Mitsubishi. It usually connects within about 20 seconds of starting the car. It often won't connect for about a minute and sometimes doesn't connect at all (maybe 1 in 20 times). When it doesn't connect, I turn off bluetooth in the SGS2 wait about 15 seconds and turn it back on. It usually connects again without touching the car kit.
I've noticed that if I unpair the car kit at the SGS2, the car kit will try to reconnect about once a minute and the phone makes a noise to tell me that something is trying to connect.
Recently I took a vacation and rented a 2012 Toyota Camry and paired my SGS2 to its bluetooth. The phone connected faultlessly very time, there were no issues.
My theory is that if the phone is busy with some process or another when the bluetooth kit tries to connect, it misses the connection. If the kit retries several times (I'm guessing the Toyota kit did this), then there seem to be no issues.
I can only guess that if the SGS2 bluetooth stack is given a higher priority it would be less likely to miss the connection. Clearly that's impractical because bluetooth only needs to connect (maybe) 3-5 times a day and may exclude a more frequently used process.
Just my 2 cents worth - I hope that helps
DaGroover said:
I've had similar issues with my SGS2 on ICS and now with 4.1.2 (XXLSJ). I'm convinced the problem is a combination of the phone's current processes and how often the car kit retries to connect. I have a Parrot based bluetooth kit factory fitted in my 2006 Mitsubishi. It usually connects within about 20 seconds of starting the car. It often won't connect for about a minute and sometimes doesn't connect at all (maybe 1 in 20 times). When it doesn't connect, I turn off bluetooth in the SGS2 wait about 15 seconds and turn it back on. It usually connects again without touching the car kit.
I've noticed that if I unpair the car kit at the SGS2, the car kit will try to reconnect about once a minute and the phone makes a noise to tell me that something is trying to connect.
Recently I took a vacation and rented a 2012 Toyota Camry and paired my SGS2 to its bluetooth. The phone connected faultlessly very time, there were no issues.
My theory is that if the phone is busy with some process or another when the bluetooth kit tries to connect, it misses the connection. If the kit retries several times (I'm guessing the Toyota kit did this), then there seem to be no issues.
I can only guess that if the SGS2 bluetooth stack is given a higher priority it would be less likely to miss the connection. Clearly that's impractical because bluetooth only needs to connect (maybe) 3-5 times a day and may exclude a more frequently used process.
Just my 2 cents worth - I hope that helps
Click to expand...
Click to collapse
Actually, we own two SGS2 phones: Both pair with our Audi telephone kit. The first reconnects after 30 sec./ 1 minute and then reconnects. The later stays connected. However, if I try to use the phone to dial a number via the Audi telephone unit.....the Audi telephone unit starts to dial and then stucks. The first phone is able to dial.....as I have seen in the web others seem to have the same problem with SGS 2 4.1.2. I even bought BLUETOOTH KEEPALIVE...no succces. With version 4.0.4 neither of the phones had a problem with paring with the Audi device. Any other ideas?
Same for me
Im also having the same issue, I have a SEAT Altea and after upgrading to JB on my S2 i have exatly the same issue.
Connecting to the Blue Tooth now takes a lot longer than previously and i get a rapid reconnection about every 30 seconds or so (could be slightly longer i havent measured it). There is no disconnect sound from the hands free though only a conneciton sound.
Please post if you find a resolution to the issue.
Regards.
Jason...
Problems with Bluetooth
Hi All,
I have the same problem. I upgraded to 4.1.2 recently and immediately after all was OK. However now it has developed a new problem.
It will connect to the Car Bluetooth and will play music however the minute I start a call it will only use the small speaker designed for when you hold it to your ear. I will not allow me to press the headset button and will not automatically switch to headset/Bluetooth. This is seriously irritating and I have tried all the usual options of rebooting and unpairing etc. but to no avail...
Your pearls of wisdom would be gratefully received
Using a Samsung Galaxy S2 with Android 4.1.2 Build JZ054K:I9100XWLSW
Regards
Fiachna
I report the same issue between my SGS2 and my '04 BMW 3-series.
With the 4.0.3 ICS no problems: the phonebook is shared correctly and visibile with the car, without loosing the connection.
Starting from 4.1.2 JB I'm not able to keep up the connection for more than 30 seconds, and I cannot read also the phonebook: in this way the phone cannot be used in the car.
The only way to have JB and the bluetooth working togheter is to install a custom ROM (4.2.2 SuperNexus or RootBox 4.2).
Try it!:good:
Install File Manager which can access system files
go to System/etc/bluetooth
in file called main.conf add
IdleTimeout=0
save file - it worked for me