Hi there! I have an MDA II and a Parrot CK-3000 (with sw ver. 3.13) carkit. I read about the outcoming of this sw and I decided to install it on my MDAII. But, after a correct installing procedure, it simply doesn't work: my carkit remains mute like a fish!!! :shock: I'm asking you, guys already use successfully this sw, a hand of help to solve my trouble (if possible). Note that I downloaded it from this
http://bluetooth.i-networx.de/index_e.html
and I tried to follow all the instructions placed in there...
Thank you all!
pap
paperuccio said:
Hi there! I have an MDA II and a Parrot CK-3000 (with sw ver. 3.13) carkit. I read about the outcoming of this sw and I decided to install it on my MDAII. But, after a correct installing procedure, it simply doesn't work: my carkit remains mute like a fish!!! :shock: I'm asking you, guys already use successfully this sw, a hand of help to solve my trouble (if possible). Note that I downloaded it from this
http://bluetooth.i-networx.de/index_e.html
and I tried to follow all the instructions placed in there...
Thank you all!
pap
Click to expand...
Click to collapse
Why not email the author, he is most helpful.
Had the same issue with the Parrot. My Plantronics headset works a treat, but not the Parrot.
I mailed the author who confirmed there are some problems and a new release will be needed.
As the author is doing this work unpaid and the functionality is so good, I can wait.
@ mrg2003
I send an e-mail some days ago but still had no response.
Anyway, I agree with IanF and I'll wait for the new release.
I wish I read this bulletin board more often.
Yes, I have exactly the same problem with the CK3000 (v3.13) and PBT. HBH-35 works a treat but CK3000 does not bond (XDA thinks it does but there is no handshaking and CK3000 repeats request to bond).
Back to basics again ...
Incidentally, does anyone know if Tobias plans to engineer a way to trigger Voice Command and take input from the car microphone for voice recognition? Would be the dogs and well worth a major donation ....
Cheers
I've had some problems with pocket bluetooth. I have emailed tobias as follows and am awaiting a reply. Was wondering if anyone has faced similar problems:
Tobias,
Thanks for all the hard work in getting these tools working. I have just bought an XDAII with the latest 1.60.00 ROM using the 1.10.00 radio version.
At the same time, I have a WIDCOMM bluetooth dongle on my PC which supports numerous profiles including the headset profile, which allows me to use the PC's speakers and mic as a 'headset' with the XDAII.
I set up the XDAII with the PC, using the built-in bluetooth bonding and pairing application and managed to get it all working fine with the PC using the speakers and the mic as the headset, with the phone automatically transferring the call to the PC when the 'Bluetooth Headset mode is enabled' shows on the today screen. Furthermore, activesync also seems to work fine too.
After installing Pocket Bluetooth Tools, the headset stops working. Before installing it, I unpaired the device by deleting it from the list of paired devices. After installation and going through the process of pairing the device again, it correctly gives me the option to choose the Serial Port, ActiveSync, Modem, and Headset profile. I select all of these and click on OK. Once this happens, my PC gives me a message saying that the XDAII has connected with the headset. However, this doesn’t happen once but goes into a continuous loop giving me notifications every 2-3 seconds that this is the case. Furthermore, when making a call to see if the voice has been transferred to the PC< this stops working and the XDAII's speaker and mic continue to be used. The only way to stop the constant loop of connections is to switch off the bluetooth radio on the XDAII. Furthermore, when deleting the pairing from the XDAII this constant loop continues.
Have you faced this issue previously, as I think it may be a bug. The only reason I installed pocket Bluetooth is that my current b.tooth headset is a Nokia HDW-30 that supports the handsfree profile and your documentation states that Pocket Bluetooth tools supports this profile.
Let me know if there is a fix for this.
pap[/quote]
Why not email the author, he is most helpful.[/quote]
maybe just because he doesn't answer
i wrote a very long report some days after the long awaited new version came out in april, but haven't got any reply. (maybe my email got lost - who knows ...)
i have exactly the same problems. i also have a parrot ck3000 (tried with firmware 3.11 and 3.13) and an mda2 with rom 1.6.00GER and extROM 1.60.07. the two devices pair, and sometime i can even select the "headphone profile" afterwards. i even managed to make it work ONCE, after several hours, of installing, reinstalling, pairing, reparing, ect, ect ...
what did work once was making calls. but after the first call came in, i could answer it, the caller could hear me, but i couldn't hear anything. this happened twice and then i just turned off bt and used the mobile as always.
as i'm using my mda in my car for work and not for fun this is no solution for me . i went back to the original bt stack that works quite well. i can make and take calls w/o any problems.
one thing i'd like to see changed (as soon as parrot and mda work together) is, that ALL calls are made via the handsfree, as, as long i'm in the car it HAVE TO use the handsfree by law (and it's much more comfortable anyway). it's not practicle to dial with the mobile, and then by pressing the green button on the parrot to move the call to the handsfree. but that's the only way you can do it when using speeddial.
another thing i desperately miss is a way to change the volume of the handsfree. i could do this using the volume slider of my nokia 6310, but volume stays all the same when using the mda. and it's just too low when doing higher speeds on the autobahn
of course voice dialing would be a great feature to have ... but it's not that necessary.
please don't get me wrong .. i'm don't want to be ungrateful as i'm not paying for this software - i just want to help ppl by saying that they are not alone with their problem and they should give up wasting their time and better wait for a new release....
and of course i'm very willing to PAY for that software as well as soon as it is any improvement over the original bt stack (for me of course. for most of you it already is)
maybe TOWA could say some words here. that would be really appreciated.
thanks anyway a lot to all ppl that spend their free time developing software and providing it to the comunity!!! thumbs up !
regards ize|man
Bluetooth tools and ROM 1.72
Does ROM version 1.72 require TOWA's bluetooth tools? In this ROM, there are options for COM port selection etc under Bluetooth settings and the clubimate site mentions bluetooth improvements. Anyone with this info?
other com settings then
Inbound COM port com4
outbound COM port com5
??
if so what are they?
Rudegar
You are right. Inbound 4, outbound 5. Likely required for GPS devices, if i am not mistaken
faisal said:
Rudegar
You are right. Inbound 4, outbound 5. Likely required for GPS devices, if i am not mistaken
Click to expand...
Click to collapse
These are the ports for BT beaming, as I understand! (not for BT GPS).
For BT GPS you do not specifically need BTHTools anymore (since 1.66) because WM can install a BT GPS com at first bonding.
Something is different however (vs BTHTools) since with 1 application (Alturion) I can not get the BT GPS working anymore, which can also not be solved by still installing BTHTools!! (while I have no problems with my other application TT. Figure that out?!)
Ronald
I now have the same problem, the parrot ck3000 was working until I insatlle dthe bluetooth tools, and now it doesn't.
Its a shame I did not see this thread before
Will the 1.72 rom work with both parrot and my emtac bluetooth gps?
Cheers
Justinp
justinp
have you tried uninstalling Bluetoothtools?
no not yet, I might give that a go, but then my gps wont work :?
justinp said:
no not yet, I might give that a go, but then my gps wont work :?
Click to expand...
Click to collapse
I think it will still work!
With my working application (TT3) I see the GPS on COM5 (installed by WM) + on COM7 (installed by BTHTools) + on the BT/SIRF interface!
If I uninstall BTHTools I only loose the selection for COM7. The other two selections still work!
Of course you must have acknowledged the WM com installation with first bonding (in any case for the serial operation)! My BT/SIRF connection always works in TT3 regardless of WM/BTHTools installation of serial ports.
Ronald
I'm also having that strange problem with the parrot CK3000. I did install the previous version of BT but I don't see any difference with or without BT. But when I de-install and want to go back to the original state, the same problem persist. Is there any way to download anyware the original Bluetooth stack without re-install everything (and loosing all my settings and software)?
Thanks for helping out.
Frank.
hey guys,
i´m writing to see if anyone has got similar problems.
i cant connect my mozart with my car audio Pioneer DEH 6100BT. my last device (t-Mobile MDA compact IV) did it very well. but the mozart cant connect.
it searches for devices but nothing happens. same problem while searching with the car audio for new device. seems like they cant "see" each other.
can anybody help?
Problem solved!
After trying different things, i just had to activate BT on my device and start then the car audio. seems that you have to keep the right order!
please close
I have had some difficulty too. Initially the Mozart connected to my car's bluetooth and worked for a few days. Then it failed to connect even after resetting the device. I also tried deleting the partnership from either or both ends and trying to make a new connection, but it refused to connect - error message simply said connection failed. I thought I would have to hard reset the Mozart and start again.
However, a few days later I connected by bluetooth to my laptop which went smoothly. After that I was able to make a new connection to the car which has since worked fine.
Hi Forum
I have have updated to o2 2.2 Froyo & still im unable to get my bluetooth headphones to pair to my Dell Streak .
i have tried headphones on other phones and they pair straight away
is there anything i can check or install so i can get it to work as Dell just say send it back .
I have the phone rooted as if i don't like the Dell official update will go to Steves
I'm hating the Stage ui don't know whos idea that was,need to look into changing it but bluetooth issue is just a real pain
Thanks
Only thing i can suggest is a Factory reset if still no good then reinstall the ROM
Sorry, can't help you, but got a little longer. I haven't succeeded yet in making a bluetooth phone audio connection with my Streak Android 2.2. Paired but not connected is the message. It connects with the headset for media audio but not for phone audio. Tried with different headsets. Mostly if I try to connect to the phone audio in "options" the app crashes with the message "The application closed unexpectedly....." "system exception....". I just won't work. I know I'm not the only one with the problem. Has someone an answer?
Bluetooth connection solution
Well, then I finally had to do a factory reset. The connection problem is solved and maybe can solve others. Because I downloaded a reboot-app and used it, the Streak didn't want to start any longer. I had to do the factory reinstall (press both the volume down and upp buttons and at the same time also the power button, keep holding until you see text, choose factory install). After that the bluetooth connects fine. It's a lot of reinstallation, but it worked. With the help of Dell Backup most of the configuration/apps can be restored.
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
Hi
I am on BOGE firmware fresh install no root yet. Having issues with bluetooth connectivity. When I connect a device (Beats Studio Wireless 2.0) I can listen to an app until I start switching apps or stop and resume the playing. Occasionally the connection breaks and I need to switch on and off the headphones. Switching bluetooth on/off on the device does not help. Had no problems using these headphones on S5. Tried to clear bluetooth cache/data and format cache partition, unpair/pair the device with no result.
Any help would be much appreciated.
Thank you
Having the same issues with the newest update BOGF.
The connection drops constantly when connected to my cars BT.
Used to work fine until last update.