Hi, I have a XDA II TSM 500 (Telefonica) in Spanish versions:
rom 1.72.03 ESN
03/*15/04
1.10.00
1337.18
ext rom 1.72.102
And I have a parrot ck3100 but it doens´t work, I cant uase the parrot I have install the bt tools but nothing, bttools v10.12 and 11.00 but nothing, and the widcomm program but nothing, can someone help me?, must I upgrade the room? what rom?. Thanks
The parrot carkit is one of the few that support the BT headset profile. This profile is the only (speech) one the standard Himalaya roms support.
So . . .It should work. Afaik, you do have to configure the parrot in order to make it support the headset (instead of handsfree) profile.
I think this should be in the manual.
As from 1.72 roms there is NO NEED to use the Pocket Bluetooth Tools for these matters. Uninstall those!
The widsomm stack wont help either, because that one supports a lot of protocols, but it does not support the headset . . .
RE
Thanks but when I syncronice my XDA with parrot in the screen of parrot appear HEAD SET!! but dont appear coberture, battery, agenda, and I cant speek throught the parrot my radio versiono is 1.00, whan I configure the XDA II bluetooth I put the com4 and com5 enable is this right?, thanks.
RE
I tested It again, it puts HEADSET in the screen of parrot, whan I call from XDA II puts bluetooth headset is on but I it dosn´t work in parrot or in XDA II listen nothing, and the sincronice fails after 30 seconds, I downloaded 2 roms from here "windowsmobile2003se.exe", "RUU172601WWE.exe" must I put one of this?, thanks.
I bought a parrot driveblue, it didn't work . I called parrots office and they said me my version Rom 1.66.00 radio 1.10.00 wasn't high enough to work with driveblue, and I see that you still have the same radio 1.10.00. Isn't it that, your problem ?
Look edsub has a OS 1.72.00 and a radio 1.17.00.
If you change with your ESN by a WWE , be carefull with the country error code !
May be I'm wrong and this have nothing to see with your problem.
hi
TOMY00
PLEASE
use himegetdeviceinfo.exe on your device
and give me the informations you found on file devicedata
on windows directory on your pda
please
my device is dead
and i need the operator code from telefonica movistar
thanks
I have one of the first Parrot CK3000 which works fine with a Sony T610 mobile. I have expended hours of effort trying to get to work with an XDAI, an XDAII and a PDA2K (borrowed).
I tried Windows Mobile 2003, 2003se and various BT tools. None worked.
I upgraded my XDAII to Magneto (WM5) and BINGO! works fine now!
Petermcc said:
I have one of the first Parrot CK3000 which works fine with a Sony T610 mobile. I have expended hours of effort trying to get to work with an XDAI, an XDAII and a PDA2K (borrowed).
I tried Windows Mobile 2003, 2003se and various BT tools. None worked.
I upgraded my XDAII to Magneto (WM5) and BINGO! works fine now!
Click to expand...
Click to collapse
ck3000 here worked almost fine with MDA1, MDA2 (original) and MDA2 with wm2005. BUT no chance to change the volume of the loudspeakers. are you able to do this?
Related
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.
This merged English version of WM2003SE is compiled for the Australian model O2 XDA II.
:!: NOTE: It is supplied as is. Use it at your own risk!!!
:idea: TIP: First backup your data and settings using either ActiveSync, SDBackup or XBackup - then download the attached ROM_Backup.zip - extract and follow the instructions in the ROM backup folder.
To install the merged WM2003SE:
1. Download the attached Setup.exe
2. Insert your O2 XDA II into it's USB cradle and confirm that a successful USB connection has been made with your PC
3. Run Setup.exe and follow the onscreen prompts.
Details:
The ROM image is based on version: 2.06.00WWE (ver 4.21.1088 build 14132)
The Radio image is version: 1.18.00
The Extended ROM image is a variance of version 2.06.100a (Sin.Merged.v1.0)
The Extended ROM contains the following:
Merge of ROM 2.02.t1WWE over ROM 2.06.00WWE, pre-configured with:
AltTab, Blackberry, Caller ID, Camera, ClearType Landscape, ClearType Tuner, ClearVue, CMD, Contacts, Explorer, ExtROM Tools, Flash, Fonts, IE Tools, IntelliDialer, Keyboard Extension, Midi Ringtone, MMS Composer, MS Reader, Notepad, O2 Customisations, Paint, Print, RegEdit, Reset, Rotate Screen, Run, Scheduled Tasks, Space Invaders, Task Manager, Tray Launch, Video MMS, WiFi & BT Headset/Handsfree Profiles.
The Autoconfig only contains support for the following Australian Carriers: - Optus, Telstra & Vodafone + "Not Listed - Set Manually"
KNOWN ISSUES:
Today Screen BT Profile Icon likes to play Hide'n'seek
BT HandsFree Mode may disable headset mic.
A choice of either HandsFree or Headset profile is now enabled, please select only one or the other.
NOTE: BT HandsFree Mode may disable headset mic
Uninstall "Version Sin.BT.Handsfree" from "Settings->Remove Programs" if necessary.
:arrow: INFO: New version is here!
Thanks very much Sin!
Been Looking forward to this SiN! Made my weekend!
Thank Sin for putting it together.
I originally Had and Orange SPV M1000, and upgraded it with the O2 1.72 version, in the hope that it would sort out the problems with Blue Tooth and Handsfree car kits, which it did not of course.
Thought I would try the rom from Mystery Man, which interestingly did not require any changes to the files to allow it to update, which also did not work the blue tooth, so I was going to try just updating the Radio to 1.18, but saw your new package pop up, so thought what the hell, give it a go, and now I am made up cos been very frustrated that it would not work in car kit.
The car kit I have is the Nokia CK-7W Blue tooth if this helps anyone else, I also assume it will work with the others, in particualr the built in ones in BMW's.
So thanks again everyone, I can sleep now.
Mark
Other known issues..
Thanks for the job SIN!
I have to point out a couple of issues I'm having since long, that seem related to the BT problem, but looks like no one else is having: "DUAL STEREO" sound in both (XDA II and Handsfree/headset) devices.
No matter BT headset is "enabled" or "disabled", the devices configured as "handsfree" are operational. Plus, my HBH 35 headset refuses to work unless configured as a handsfree device. After that, every handsfree device works in "STEREO" mode. Nice for multi part conferences, but annoying for your caller, who hears every tap on the XDA in your pocket, since the mic is operational no matter what.
I'm really the only one with this problem?
:?:
Hi Sin
Just a quick question, tried to change the splash1 & 2 images, to get away fro O2 image you put into file, but having probs with corrupted display if the image, howd you do it please, as I understand the normal method does not work with Chinese and Trial versions !
Many thanks in advance.
Mark
BTHFP
Does the headset mic work on handsfree profile Sin?
thanks Sin
I tried to modify the extended ROM to modify the provider list but couldn't found the autoconfig.txt, is it ok to create autoconfig and put it there? or did you merged the autoconfig inside Sin.Merged.v1.0.cab?
please let me know
thanks
Brumie
Re: Other known issues..
Looking Glass,
Your not the only one with this problem.
I have a bmw with bluetooth and it does the dual stero trick.
I have a Bluespoon Digital and it also does the dual stereo trick.
Has any one tried removing the head set profile and leaving just the hands free
Thanks
Jon
hai where can i download the attachment? i need to upgrade my xda2 urgently.. thanks.
Other Bluetooth Devices
Before I try out these new updates which sound fantasic, I am interetsed to know how this will effect my bluetooth GPS.
Currently I am using bluetooth tools to connect my GPS to my XDAII, does the new roms enhance bluetooth or should I still install bluetooth tools?
thanks.
Re: Other known issues..
"I have a bmw with bluetooth and it does the dual stero trick
Click to expand...
Click to collapse
I just tried the car again and it worked perfectly. So it looks like I only have the problem with the Bluespoon.
I'm pretty happy with the car working as that was what I really wanted.
Johnson..... you have to log in then you will find the attchments at the bottom of the first post in this thread.
Guest... I dont have a bluetooth GPS. Ive no idea if it works. I do know you cant get the Sandisk WiFi SD card to work which is a bummer.
Jon
ExtendedROM...
@ Sin,
This merge ROM version of yours, what is the most very important file that I need to keep on my extended_ROM? Last time I used your version without any problem But I need to remove some CAB file for my own customization. But now seems that ms_.nbf has only one file (Sin.Merged.v1.0.cab) which I think all the CAB file was in there.
Is it possible to gave us your merge CAB without the rest of installed program? Or is it okay to delete some CAB on extended_ROM after installation (cooked-own ROM style)?
Thanks!
Re: Other Bluetooth Devices
Anonymous said:
Before I try out these new updates which sound fantasic, I am interetsed to know how this will effect my bluetooth GPS.
Currently I am using bluetooth tools to connect my GPS to my XDAII, does the new roms enhance bluetooth or should I still install bluetooth tools?
thanks.
Click to expand...
Click to collapse
What ROM are you using now? I used to have 1.72 ROM and I need to used Bluetooth tools to be able to use both BT headset and BT GPS (Belkin/rebadge Fortuna Clip-on). BUT with ROM 2.06 (mysteryman), Sin.AU.v3.5(extended_ROM) and 2.02t1 Reg CABv3.cab (from henrylim). I am no longger needed bluetooth tools, it works without any issue.
file mentioned can be found here:
http://forum.xda-developers.com/viewtopic.php?t=13660&postdays=0&postorder=asc&start=50
Hope this help. I haven't tried Sin.merge.v1.0 yet but I will soon.
Re: Other known issues..
916senna said:
Looking Glass,
Your not the only one with this problem.
I have a bmw with bluetooth and it does the dual stero trick.
I have a Bluespoon Digital and it also does the dual stereo trick.
Has any one tried removing the head set profile and leaving just the hands free
Thanks
Jon
Click to expand...
Click to collapse
Nice to know, thanks for info, I was about to think no one else has the problem.
I've been experimenting during the weekend, and found that the problem remains quite the same: some headsets/handsfree only work if the HandsFree profile is selected, and then the "dual stereo" problem arises again.
By contrast, version 2.20 properly handles every "audio" device (at least my devices) but I haven't found how to made BT ActiveSync back to life. Plus the other known issues with the translation (May I help Buzz_lightyear?)
Resume: Excellent job by Sin (regards) but the whole BT thing is not yet fixed. I like his "new compact" Ext Rom, but since HandsFree profile is at this time more important to me than BT ActiveSync, I'm going back to 2.20.
Not there yet...
with WMP 10
in rom, with wmp 10 ?
Re: with WMP 10
bos_xda_II said:
in rom, with wmp 10 ?
Click to expand...
Click to collapse
Only 2.20 comes with wmp 10. Sin's rom has version 9.
Not there yet...
Re: Other Bluetooth Devices
Anonymous said:
Before I try out these new updates which sound fantasic, I am interetsed to know how this will effect my bluetooth GPS.
Currently I am using bluetooth tools to connect my GPS to my XDAII, does the new roms enhance bluetooth or should I still install bluetooth tools?
thanks.
Click to expand...
Click to collapse
I have a CoPilot Bluetooth GPS unit and it does not need Bluetooth Tools to get it to work via serial port emulation. I'm using 2.06 ROM.
With the BT GPS bonding, you get to say you want it to be a serial port but you don't get to specify what specific port number like with Bluetooth tools. This is not a problem with CoPilot software as it will FIND the serial port and baud rate in it's Bluetooth connection/configuration setup.
I also have a SanDisk SDIO WiFi card which also works fine (note the card is NOT the SDIO RAM+WiFi though!).
Re: Other known issues..
916senna said:
"I have a bmw with bluetooth and it does the dual stero trick
Click to expand...
Click to collapse
I just tried the car again and it worked perfectly. So it looks like I only have the problem with the Bluespoon.
I'm pretty happy with the car working as that was what I really wanted.
......
Jon
Click to expand...
Click to collapse
Hi again!
How exactly did you get to eliminate de "Dual stereo" effect in your carkit? I have too a HBH 35 headset and the problem remains on both of them.
This is my only complain, everything else works so well! And Sin made such a good job putting the Ext Rom together!
Thanks Sin for the easy to install ROM.. well done.
My Bluetooth GPS works fine, a bit of a change not having to select a port, but the port is displayed so that wasn't a problem.
My Logitech Headset refuses to work. It pairs with the XDAII but I am unable to iniate a call from the headset and the mic doesn't work.
The Bluetooth smybol is gone from the task bar too... probably something I did...
Is there a cab about that allows me to reinstall the bluetooth section just in case I stuffed somethign up?
Thanks.
Hi Guys,
I have encountered the following problem.
When I first add my Supertooth II (car kit) to the ATOM (normal Hands Free handshake), everything goes well and I can get and make phonecalls.
However, after stopping the bluetooth on the ATOM and restart it after a while there is no communication between the devices any more and I have to add the Supertooth again to work.
I did not have the problem with the previous cooked WM5 ROMs.
Any Ideas?
Thanks,
Yaniv
yeah I got this problem too...actually I can turn on the BT but the phone (device) will not be found if searched by other devices. Even with the ver 7a WM6...
So A2dp does not work on assembling of Wm6 for Exec Aku0.7a.0, authors so can not correct this bag already during 2-5 months, explaining that for them a garniture absents with A2DP,AVRCP, very it is sorry...
Yeah , me too . When i conect my Atom Exec ( Aku 0.7a.0) with Bluetooth Handset , i can't hear any thing ..........
hooliganboy214 said:
Yeah , me too . When i conect my Atom Exec ( Aku 0.7a.0) with Bluetooth Handset , i can't hear any thing ..........
Click to expand...
Click to collapse
since all of you have bluetooth device, can one of you test this application. this is MSI BluePlayer, try to play the music from this application and let me know the result.
i didnt have this issue. i use a a2dp head set for listening to music. .. the only issue iv had is when ur speaking to some one over bluetooth and another calls comes in . the voice goes blank till transfer the call back to phone and then again back to bluetooth . but i thought that was a ITECH bluetooth head set issue so didnt bother talking about it. had this issue even during wm5
MSI Player is unholy bull**** crap. We need native BT stereo in any player/
chartreux said:
since all of you have bluetooth device, can one of you test this application. this is MSI BluePlayer, try to play the music from this application and let me know the result.
Click to expand...
Click to collapse
Does not work!!!
Actually, i dont have any bluetooth device, would you please someone try this,.
http://forum.xda-developers.com/showthread.php?t=332692&page=14
post #670
Report the result okay,.
Garmin said:
Actually, i dont have any bluetooth device, would you please someone try this,.
http://forum.xda-developers.com/showthread.php?t=332692&page=14
post #670
Report the result okay,.
Click to expand...
Click to collapse
/HKLM/Drivers/BuiltIn/BtA2dpSnd
remove any Priority256 value
HKLM/Drivers/BuiltIn/WaveDev,
Priority256=149
/HKLM/Software/Microsoft/Bluetooth/AudioGateway
Capability=37
/HKLM/Software/Microsoft/Bluetooth/A2DP/Settings
UseJointStereo=0
BitPool=58
MaxSupportedBitPool=80
Remove all other values from this key including SampleRate
Does not work!!!
Coarls said:
yeah I got this problem too...actually I can turn on the BT but the phone (device) will not be found if searched by other devices. Even with the ver 7a WM6...
Click to expand...
Click to collapse
you did not check the option for bluetooth settings -> make this device visible to other devices.
I have been using bluetooth to activesync with pc and interchange with other pda phone, but the atom can easily be found
i didnt have this issue. i use a a2dp head set for listening to music. .. the only issue iv had is when ur speaking to some one over bluetooth and another calls comes in . the voice goes blank till transfer the call back to phone and then again back to bluetooth . but i thought that was a ITECH bluetooth head set issue so didnt bother talking about it. had this issue even during wm5
Click to expand...
Click to collapse
This is an MS Bluetooth Stack issue and cannot be rectified because Microsoft can't be bothered. It's a problem even with other phones, which is why people have tried to replace bluetooth stacks with ones from Widcomm and co (unfortunately for us, this isn't possible, and I believe that Jiggs has tried this before).
Microsoft doesn't garuntee full compatiblity with all headsets using its lame bluetooth stack. On my end, the A2DP works, the mic works, the "return to A2DP mode" works, I can resync when cut off, but I can't hear s*** when engaged in a voice call.
Jigg's ROM is still on the WM5 Bluetooth stack. The WM6 Bluetooth stack, which I've also tested, is supposedly better for voice calls but IIRC is NOT compatible with MANY headsets (A2DP won't work on most headsets that aren't marked BT2.0) - just ask the Athena users. It isn't compatible with mine - produces NO output in A2DP... I was the one who advised Jiggs to stick to the WM5 bluetooth stack. >_>
Headset: SonicGear Blue2 SR300
NEW bluetooth audio gateway
Ultimate Chicken said:
This is an MS Bluetooth Stack issue and cannot be rectified because Microsoft can't be bothered. It's a problem even with other phones, which is why people have tried to replace bluetooth stacks with ones from Widcomm and co (unfortunately for us, this isn't possible, and I believe that Jiggs has tried this before).
Microsoft doesn't garuntee full compatiblity with all headsets using its lame bluetooth stack. On my end, the A2DP works, the mic works, the "return to A2DP mode" works, I can resync when cut off, but I can't hear s*** when engaged in a voice call.
Jigg's ROM is still on the WM5 Bluetooth stack. The WM6 Bluetooth stack, which I've also tested, is supposedly better for voice calls but IIRC is NOT compatible with MANY headsets (A2DP won't work on most headsets that aren't marked BT2.0) - just ask the Athena users. It isn't compatible with mine - produces NO output in A2DP... I was the one who advised Jiggs to stick to the WM5 bluetooth stack. >_>
Headset: SonicGear Blue2 SR300
Click to expand...
Click to collapse
thanks for clearing that out Ulti. I was wondering if you could try one more time with wm6 ms bluetooth stack? In the headset profile, I have tried to integrate a new set of bluetooth audio gateway. Unfortunately, this requires flashing a new ROM as the modules need to stay modules to work.
It is open to everyone with a bluetooth headset to try... I don't have a device to test it. sorry.
http://www.mediafire.com/?0uqg0utmpkx
Jiggs,
what can be the reason for after first handshake everything is going well, but after restarting it the devices do not communicate (for inbound & outbound phone calls) ?
Moreover, if you use the same WM5 bluetooth stack, how come I did not have that problem with the WM5 ROM ?
Thanks,
Yaniv
yanivw said:
Jiggs,
what can be the reason for after first handshake everything is going well, but after restarting it the devices do not communicate (for inbound & outbound phone calls) ?
Moreover, if you use the same WM5 bluetooth stack, how come I did not have that problem with the WM5 ROM ?
Thanks,
Yaniv
Click to expand...
Click to collapse
Yaniv,
for first question- sorry, I don't know. I think second question is obvious - wm5 drivers is meant for wm5 system and not wm6.
Have you tried the the WM6 A2DP with WM6 audio gateway driver?
jiggs said:
Yaniv,
for first question- sorry, I don't know. I think second question is obvious - wm5 drivers is meant for wm5 system and not wm6.
Have you tried the the WM6 A2DP with WM6 audio gateway driver?
Click to expand...
Click to collapse
I did not.
How do I get and install it ?
Yaniv
yanivw said:
I did not.
How do I get and install it ?
Yaniv
Click to expand...
Click to collapse
Post#13 above
It is open to everyone with a bluetooth headset to try... I don't have a device to test it. sorry.
http://www.mediafire.com/?0uqg0utmpkx
Click to expand...
Click to collapse
Thanks, Jiggs, but the A2DP's still NG to my headset with this test ROM. Replacing the keyboard with the black one I liked back during O2 Mini BigStorage is a nice touch, tho.
Anyone else with a BT Stereo Headset, especially a 2.0 standard one, go ahead and help test. You may have better luck than me (the SR200 is just BT1.2 standard, and I'm now pushing SonicGear for a firmware update).
Sorry, I have Pulsar 590E and its 1.2 Bluetooth.
chartreux said:
since all of you have bluetooth device, can one of you test this application. this is MSI BluePlayer, try to play the music from this application and let me know the result.
Click to expand...
Click to collapse
Yeah , I just try it , and it works verywell . But my Bluetooth Handset isn't MSI 's device , so i only run it in 31s . Do u have other method ???????
My S200 has been repaired (new motherboard) and I re-installed Korand 3.1 rom and restored everything, but A2DP is not working any more with my Jabra 620 stereo headset. I tried other roms such as ROM Prophet My Green Edition ROM 2, but still no A2DP.
I don't understand the problem and I don't find a solution. When I try to connect using the batterystatus function, I get the message "failed to connect to device). I never had to connect it, since I normally get the sound that it is connected using A2DP and a logo is displayed in the top. I also tried with radio 2.19 instead of 2.47, same result.
Any ideas?
Problem solved
Hi the problem is solved! I installed a bt a2dp protocol that I found here [wm6.1] My Little Green
It would be nice, if you would share this protocol with us.
Can you upload it somewere cause i have bt probs too.
Thank you
skylow said:
It would be nice, if you would share this protocol with us.
Can you upload it somewere cause i have bt probs too.
Thank you
Click to expand...
Click to collapse
It has been shared with us two month ago already.....
http://forum.xda-developers.com/showthread.php?t=382263
Thanks bro
Hi to all,
First of all.... I've searched in all the HD2 forums and could'nt find my answer.
So I'm starting a new thread.
My problem is not a big issue but very annoying.
I'm having myself a HD2 since 2 weeks and I'ts not able to connect with my Parrot carkit. Also tried the parrot carkit in the car of a friend of mine and had the same problem.
My Touch HD didn't had this problem with all the rom's it has seen.
The HD2 is still running on the stock (dutch) 1.66 rom.
Anyone had the same problem?
Thanks in advance.
Grtz John
Hi,
I have a problem with HD2 and Parrot 3100 too.
Although it connects with my Parrot 3100 there are 2 annoying things:
1. My phonebook doesnot copy into Parrot
2. I have to pair devices and provide password each time i would like to connect my HD2 to Parrot.
I have no idea what is wrong.
Guys,
I've been searching and searching...... and found the solution on a Dutch forum.
Use a registry tool for example Total Commander of Phm Registry..
Go to:
HKLM\Software\WIDCOMM\Plugins\HandsFree
Take the item %u201CSupportedFeatures%u201D.
Change DWORD data from 1379 to 1085, safe and close the editor.
Soft reset your HD2.
Open your registry editor agian and take a look agian @ DWORD %u201CSupportedFeatures%u201D you've changed it to 1085 and it now shows 1081.
That's oke and should be this way.
Now go to your carkit remove all the paired devices en try to connect your HD2 with your Parrot. Now everything should work!
Grtz John