I've heard about a bunch of new roms (the BLACK and LVSW) that have somehow cleared up that nasty A2DP bug in the Microsoft BT stack that caused certain headsets to buzz and hiss with certain frequencies.
I'm wondering if anyone here knows how that works, what has changed in these new Roms? Are they updated bluetooth drivers from MS?
I'm wondering if we can't put together a new a2dp patch for other devices so that additional phones can benefit as well, without getting a whole new rom (similar to the way the initial Tornado A2DP patch was circulated around).
Anyone have any info?
Can anyone even verify that this is true? (I don't have a hermes, but I do have an i.tech R35 headset with horrible distortion from any windows Mobile device playing music... I'm just assuming what I've heard is true about new roms fixing it...)
The only change is to some registry entries, the HTCustom tool should work on most any phone. Black's config tool should work but sometimes crashes on other roms when you try to save.
I have got the same problem with my iTech. I think it is something related to the design of the bluetooth headset. Is anyone experiencing the same problem with a solution?
nope maybe your release is a bad bath?
My Hermes with the Black ROM works fine with my Jabra BT620s. Hands-free mode works flawlessly too.
porkchop83 said:
nope maybe your release is a bad bath?
Click to expand...
Click to collapse
No no no, this is KNOWN issue with the MS stack and certain Bluetooth headsets, including the R35.
Its not the headset.
Proof is that when paired with another device, IE a nokia, or PC running bluesoleil, it works just fine- no hissing, very good audio quality.
Also, tested on a Wizard using the Widcomm stack instead of the MS stack, and sure enough it works GREAT!
So, its clearly a problem with the MS Windows Mobile stack, and in fact it has been discussed in various forums here.
Shadowmite, are you sure its just registry changes?
Is there any way to find out what they are?
Dishe said:
No no no, this is KNOWN issue with the MS stack and certain Bluetooth headsets, including the R35.
Its not the headset.
Click to expand...
Click to collapse
Correct. I had that problem with my Vodafone V1640 (HTC Universal). Kind of solved that problem using the Widcomm stack patch uploaded by someone here. Go search for it.
richardlai said:
Correct. I had that problem with my Vodafone V1640 (HTC Universal). Kind of solved that problem using the Widcomm stack patch uploaded by someone here. Go search for it.
Click to expand...
Click to collapse
Yes, I mentioned that I had it working with the Widcomm stack on a Wizard, but I'd rather have a working MS stack for various reasons including the Widcomm stack's instability on certain devices, and more importantly, its not available on the Tornado and Vox (or any smartphone), which is my device of choice at the moment!
So, once again, does anyone know what these new roms do to "fix" the problem?
Its gotta be something I can re-create...
Dishe said:
Yes, I mentioned that I had it working with the Widcomm stack on a Wizard
Click to expand...
Click to collapse
Sorry, I missed that part.
I didn't notice that Bluetooth performs differently in custom ROMs on the same hardware. If it is true, the ROM creators would know what they have done. Try contacting them directly if no one else here knows.
Related
It is from an HP 6315 from 3/31/05
http://h18007.www1.hp.com/support/files/HandheldiPAQ/us/download/22539.html
I would love to see if we could get this stack and the settings on our XDAII and other HTC devices,,, THAT would be cool.
Bluetooth build 1.0.0.3701:
Corrects inaccurate display of headset icon when a call is in progress.
Adds a check to determine if Bluetooth stack is initialized before accepting messages from phone.
Adds a user interface (UI) change to enable a connected headset to automatically disconnect before attempting to connect to a different headset when the user chooses to connect to a second headset.
Corrects check for invalid device name.
Corrects issue where handheld could not reconnect to remote device after a page timeout.
Corrects Object push profile update so it sends all files.
Updates FTP connection wizard to correct service discovery issue.
Corrects issue with call waiting for incoming call handling while dialing out.
Corrects issue with headset connection icon so it is correctly displayed after power cycling.
Corrects audio to make it compatible with an in-car solution.
Corrects audio issue where the right channel for a headset was unavailable for playing audio and during calls.
Corrects issue where the LED and network status were not properly synchronized.
Corrects issue where the user could not send multimedia messaging (MMS) message.
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
2. This is not a HTC device, so I doubt the tools developed here will work on it.
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Well, even though I don't want to stop progress because I would like to have the ROM taken apart for my own personal reasons, the 6315 was actually made by Compal. Bad move on the part of HP in my opinion. However, the bluetooth stack that was taken from an iMate JAM worked on the 6315 and that is how most survived until the update was released. So it very well could work on the HTC's. On a side note, if someone could point me in the right direction, I will take the ROM apart, just don't know where to start.
mamaich said:
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Click to expand...
Click to collapse
Oops....my bad....excuses!
no htc dont make ALL hp's pda's the H5400's was oem'd from LG
and even if the ipaq in question is made by HTC then that dont garentee that the xda tools work as they are not made by HTC
I can tell you now that the XDA tools do not work on that ROM as it stands. However, looking through the HEX, it is laid out a little differently than the XDA ROM's but have some of the same portions, just in different locations. Now if I knew more about what I was looking at, I could take it apart for you. The 6315 uses Widcomm BT and like I stated before the BT drivers ripped from a JAM worked great on the 6315 so I have a feeling the 6315 drivers will work on the XDA's.
I can also tell anyone looking at it that in the first header of the ROM the letters are shifted 13 characters. So when you see RAT it equals ENG and so on. It looks like they don't do that for very long though.
BT
HappyGoat said:
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
Click to expand...
Click to collapse
BT 3900 and 3500 do not support Hands Free Profile or even Headset Profile on my XDAII.. This is important so people can use Caller ID on a BT device and OR a Car Kit with the Hands Free Profile....
Switching stacks is a pain in the but...
Even so, the only OS that even slightly works with Hands Free on the Himalaya, is 2.20 translated but even that has bugs that makes it very frustrating. The 2005 did have a fully functional BT, even having separate serial ports for each BT device, (like GPS), but the other bugs and the limited memory left over from the useless and unerasable Extended ROM from the other OS made it no good..
With this new ROM, I may be tempted to buy the HP again.. When I first bought one, it was DAM slow and the BT SUCKED!!!
Maybe now it is usable.
I love my Himalaya and it's 128 of built in..
http://www.expansys.com/product.asp?code=PDA2&asource=IMATE
http://www.expansys-usa.com/product.asp?code=PDA2&asource=IMATE
I will just have to keep waiting for one of the above unless someone finds a fix for the BT Hands Free.
I have read every post about MS bluetooth stack vs widcomm etc....
I know someone can build a cab file that will uninstall the MS one and replace with the newest widcomm stack.
I LOVE my universal but I carry TWO phones with me because the universal's connection via bluetooth is not PERFECT for phone calls like the blackberry (oh i fking hate the blackberry for everything else).
I REALLY REALLY REALLY want to use only my Universal but the static on bluetooth KILLS me because I am on the phone 10 hours a day.
PLEASE please help me. Fish
This file fix Blue Tooth
Bluetooth stack
I would second Fish's comments about the Univerasl and the Bluetooth stack. I have bluetooth in my car and it is great WHEN it works. When it doesn't work it takes a lot of tinkering to get the car to recognize the phone again. I'm of course not sure if the issue is on the Universal side, but Bluetooth turns it self off, so there is some kind of problem. I have tried different radios, currently 1.13 (tried 1.14 as well, but went back). I'm very interested in finding a solution (not using two phones), can you please provide some detail on what the CAB file does to Bluetooth?
Thanks,
Sven
Logout. said:
This file fix Blue Tooth
Click to expand...
Click to collapse
What exactly does this file fix/change ?
I've just installed the WM6 crossbow helmi_c version
do I still need this file ?
This is a Stack changer to change from MS BT stack to Cambridge Silicon Radio BT stack. Originally developed for Dell AXIM (about what I've found). Seems to work fine there, but need to uninstall/reinstall after every soft-reset because of a volume lock bug.
http://www.pocketpcmag.com/blogs/index.php?blog=3&p=392&more=1
http://www.aximsite.com/boards/showthread.php?t=108767&page=1
UPDATE
Do not install this patch yet. It is over a year old.
Follow the development/information on Widcomm BT Stack instead. Following links
http://forum.xda-developers.com/showthread.php?t=279236
http://forum.xda-developers.com/showthread.php?t=285419
http://forum.xda-developers.com/showthread.php?t=285696
http://forum.xda-developers.com/showthread.php?p=1073003
SO this is a different BT stack then the original MS and the widecomm ?
Daelyn said:
UPDATE
Do not install this patch yet. It is over a year old.
Follow the development/information on Widcomm BT Stack instead. Following links
http://forum.xda-developers.com/showthread.php?t=279236
http://forum.xda-developers.com/showthread.php?t=285419
http://forum.xda-developers.com/showthread.php?t=285696
http://forum.xda-developers.com/showthread.php?p=1073003
Click to expand...
Click to collapse
True
reading the posts in the forum he linked:
12-12-05, 09:57 PM
I'd rather go with the widecomm BT
I installed the Hermes Widcomm BT stack on my Universal. Sound is great, but the rest is troublesome. We need a developer to fix the code for us so it works on the UNiversal .
Check my thread in UNiversal/accessories. Or move that thread over here please!
Daelyn said:
http://forum.xda-developers.com/showthread.php?t=285419&page=20
Tried out BT Stack change for Hermes patch/program.
TEST RESULTS ON UNIVERSAL WITH WM6 (Midget aka Helmi unreleased)
Sound IS great. But other than that, this program does not work very well on my device. Of course this is designed for Hermes but I gave it a shot.
Issues:
1:
Screen flickers (only when this BT is turned on).
Flickers really bad and unable to use device.
Fix: set the device to standby (power button) and wake it up again. Flickering gone
2:
Once BT is deactivated for a few minutes I can't start it again.
Fix: No fix found yet. Only a Soft-reset and directly activate BT works.
3:
I can't use my GSM/UMTS connection anymore. Trying endlessly. Even after soft-reset's I can't connect. WiFi works fine though.
Fix: No fix found yet.
4:
Unable to uninstall this program. Tried several times. I get to the "Soft Reset Device Yes/Cancel". I soft reset, program still there and working.
5:
Hard-Reset, complete setup with WAP, MMS, MAIL etc.
Installed Widcomm BT Stack again.
Soft-reset:
Screen flickering (fix)
No 3G/UMTS connection avalible anymore. Even when BT stack is completly shut down.
We need a specific one for our Universal. Who's up to fixing this for us?
KEEPING this post updated.
EDIT 06: 18:40 @ 21/01/07
Click to expand...
Click to collapse
Quoted from my A2DP/AVRCP thread in accessories.
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
try this link
it may help
http://www.pocketpctweaks.com/pocketpc_tweaks/increase_bluetooth_volume
frz
Thanks for the info
I changed the channel in the registry of the device to channel 5 as suggested on that webpage. It was the same quality. I then tried a few other channels and the same results - connection quality still staticy.
Thank you very much for trying to help me though. Fish
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
I'm also worried with the same issue, because I've exactly the same problem. But I don't think only altering of BT stack should fix the problem. My understanding is, something is also to be done in radio (rom) side itself. Because I was using a different radio rom last year at about May or June and my BT headset worked perfect. But I can't remember now about what build that was, because later on I've updated my radio to few other releases.
Radio rom has NOTHING to do with the Bluetooth or Wifi - It's ONLY the firmware for the GSM chip.
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
We know the MS BT stack is crappy. I found out today that Helmi_c is developing one. But, still, this thread should be more about how to resolve the BT stack change (or just shut it until our friend Helmi_c finishes his school stuff and gets back to being the ROM-N3rd in need of more RAM that we all love so much) than bringing up more issues about the MS BT stack.
Thanks.
guys,tried almost all roms on my universal,some of them works a few days,after 3 months i flashed with the good old official rom,better and stable than all
anyway,the only reason for this waste of time was this a2dp issue,being not able to listen music to my motorokr(tested with 2 laptops and 2 htc,working great)
so i think is just some kind of incompatibility motorokr-universal(yes,i try all the a2dp hacks/registry editing found here
I have a Qtek 8310, and recently I bought myself a Nokia BH-501 bluetooth A2DP headset. It works great for phonecalls, but I just can't make it work for mp3-playback with Windows Media Player. My phone runs WM5 version 5.1.195 with radio version 413.1.04_02.09.00. Have anyone else had similar problems? Aren't these devices compatible?
http://forum.xda-developers.com/showthread.php?t=263735
New ROM?
I think I have the latest ROM, version 2.0.9.0. Operator version 2.5.311.2
Bluetooth software
I installed 'BlueMusic' for Smartphone, and suddenly it worked, but with terrible sound quality. Is it really necessary to have this certain kind of software to make it work? I thought it all was a part of the A2DP standard...
if the quality is poor it's prob not using A2DP
not all phones with bluetooth support A2DP
if yours does and how to make it work if it does
i sugst the link i posted before
personaly i know nothing about your device but i'm sure there are plenty who does in the forum for the device
http://forum.xda-developers.com/forumdisplay.php?f=285
I'm helping myself
http://supware.net/?bluetunes
I want to be able to tether my Axim x51v up to my cell phone using bluetooth so I can access the internet occasionally. I tried to install the WIDCOMM bluetooth stack and then the x51v was no longer visible by Vista's Windows Mobile Device Center. I ended up doing a hard reset and am back to the Microsoft bluetooth stack which is so limited in comparison. Anyone have any suggestions?
I am using WIDCOMM bluetooth stack install work with Dell Axim x51v WM6 (Football), I can connect to my cell phone using bluetooth and access the internet...
rolwu: can you go into settings --> connections --> usb to pc and try to uncheck 'enable advanced network functionality' and tell me what happens please? also, do you still have a 'bluetooth explorer' icon in programs? what happens if you click on that icon? just a couple of the problems that i had right off the bat with the widcomm bluetooth stack and want to see if you have them as well. it is very possible that i installed it wrong or just did something incorrectly. thanks!
Broadcomm stack works on my ROM and works fine
Football said:
Broadcomm stack works on my ROM and works fine
Click to expand...
Click to collapse
Yes it works!!!!
Hi Football, are you planning to remove the old Microsoft Stack ? It would be nice to release also a Widcomm enabled ROM...
Cheers!
Football: first of all, thank you for the work you did to create the great WM6 image for the Axim x51v. You have breathed new life into my old device.
If you would not mind Football, would you please give me a link to the Broadcomm stack that you installed and instructions, or a link to a thread that provides instructions, on how to install it? For some reason the one that I installed, Widcomm (which I assume is the same as Broadcomm), did not work properly.
Oh, and do you have a paypal account Football? I would not mind sending you a small gift as a token of my appreciation for your efforts.
I went ahead and tried to install the BroadcomBluetoothStackX51V05 from aximsite (which I assume is the correct one to use) and performed a soft reset as instructed. I then made the change to the registry to set the flow control value to '0' (not sure if that is still required). However, I have a few problems using this bluetooth stack:
(a) The Axim will no longer synchronize with Windows Mobile Device Center (using Vista Ultimate). If someone can please explain how to get this working I would appreciate it.
(b) If I go into Settings --> Connections --> USB to PC, I can not uncheck the 'Enable advanced network functionality' or I get this error - "Failed to disable RNDIS to use Serial." It was suggested to uncheck this in other posts related to troubleshooting failed connections with WMDC.
(c) Programs --> Bluetooth Explorer, when launched tells me that "Bluetooth radio is turned off. Do you want to turn it on?" Bluetooth is already on but I select 'Yes' and eventually it tells me "Failed to turn on Bluetooth radio."
These are the problems I have noticed so far. Do others who are using this Bluetooth stack have the same problems with the WM6 A03 ROM? Can you synchronize with Windows Mobile Device Center?
I appreciate you help and feedback.
Hi djlenoir...
I installed the Widcomm stack from Aximsite and I also experienced same problems as you...
The '0' in the registry is not required for normal operation I think. The Hardware Flow Control must be disabled only if you connect an A2DP device to improve performance and stabilty. I'm having issue about point (c) as you and I think the BT explorer only works with MS Stack... When I tried It, also created a useless bluetooth device folder(same as CF or SD) in the file explorer wich I had to remove deleting a startup menu shortcut created by the system. Another issue is the BT Obex file transfer speed wich cannot be sustained at so high default speed (I'm having chopping between 2 and 60 KB/s. Reverting to slow speed using BTSpeedSwitcher seems to solve the problem but speed si only 28-30 KB/s. Tryed with MANY BT dongles and different PC stack (Widcomm, M$, Bluesoleil).
Cheers
Football Add The BroadCom Bluetooth Stack To Your New WM6 A05 ROM
Yes, the broadcom bluetooth stack works perfect with the X51v running Football's wm6 RTM A03 ROM. Now Football all you need to do now is add the broadcom bluetooth stack to your new wm6 A05 ROM! It's got the perfect setup for SKYPE!
Technology said:
Yes, the broadcom bluetooth stack works perfect with the X51v running Football's wm6 RTM A03 ROM. Now Football all you need to do now is add the broadcom bluetooth stack to your new wm6 A05 ROM! It's got the perfect setup for SKYPE!
Click to expand...
Click to collapse
I feel the opposite and prefer to leave MS BT stack since we can always install the Broadcom stack whenever we like. In fact, I found the A2DP sound quality a lot better from the original stack
BroadCom Bluetooth Stereo Sound Quality, The Better Of The Two!
jackleung said:
I feel the opposite and prefer to leave MS BT stack since we can always install the Broadcom stack whenever we like. In fact, I found the A2DP sound quality a lot better from the original stack
Click to expand...
Click to collapse
With out a doubt, the broadcom bluetooth stack has better stereo sound quality, than the Microsoft bluetooth stack, that's plain to see and hear. Plus I use the broadcom bluetooth stack to make VOIP (SKYPE) phone calls but I cannot do that with the Microsoft bluetooth stack.
Bluetooth {DUN"} Via Smartphone And The x51v Running The BroadCom Bluetooth Stack!
rolwu said:
I am using WIDCOMM bluetooth stack install work with Dell Axim x51v WM6 (Football), I can connect to my cell phone using bluetooth and access the internet...
Click to expand...
Click to collapse
Read my thread in the Excalibur forum on how I installed the bluetooth Dun.cab file on my T-Mobile Dash, now I can pair both devices (my X51v and my T-Mobile Dash) via bluetooth Dun, go to http://forum.xda-developers.com/showthread.php?t=340762 and get the bluetooth Dun.cab file download and complete details, works like a charm...............!
Technology said:
With out a doubt, the broadcom bluetooth stack has better stereo sound quality, than the Microsoft bluetooth stack, that's plain to see and hear. Plus I use the broadcom bluetooth stack to make VOIP (SKYPE) phone calls but I cannot do that with the Microsoft bluetooth stack.
Click to expand...
Click to collapse
It's only without "your" doubt. Not to mention a serious bug in broadcom A2DP (across all PDA I tested) which system volume adjustment is not working. I found my SE HBH-DS220 a lot worse than the original MS stack on x51v. (But the same handset works very good w/ my Asus P525 which also has use broadcom stack. Maybe some tweak is need...)
Since different people got different need, it's better to leave it and have the user to install broadcom stack as needed
Menneisyys And Mike Spikle Were The First To Come With The Broadcom BT Stack!
jackleung said:
It's only without "your" doubt. Not to mention a serious bug in broadcom A2DP (across all PDA I tested) which system volume adjustment is not working. I found my SE HBH-DS220 a lot worse than the original MS stack on x51v. (But the same handset works very good w/ my Asus P525 which also has use broadcom stack. Maybe some tweak is need...)
Since different people got different need, it's better to leave it and have the user to install broadcom stack as needed
Click to expand...
Click to collapse
I have been using the Broadcom bluetooth stack way back before Dell ever thought of a x51v! We only had the X50v back then in those days! (Old School) Menneisyys and his friend Mike Spikle were the first ones to introduce the Broadcomm bluetooth stack and I still have the same download of their first original fix with the bluetoothspeedswitcher.zip and the flowcontrolhack.reg on both of my x51v's. I have never had a skipping problem, the stereo sound is perfect. Menneeisyys uses the Plantronics 590A bluetooth headset and I also use the same headset for that perfect stereo sound quality. Maybe, you are using a different broadcom bluetooth stack, than what we are using, because I have no problem using the volume control (high or low) again it works like a charm and always has.................!
What sort of bluetooth does the orbit have, is it MS/widcomm/broadcomm?
Basically i want to use a particular software, and the requirements say this
'MS Bluetooth Stack (WIDCOMM / Broadcom is NOT supported)'
I tried the software on my XDA iis with no luck, but i believe that it has broadcomm.
Thanks in advance.
A software package I run on my Artemis (Labview PDA vs8) requires MS BT only, and it works fine for me, what is it you are trying to run? - Mike
davidwharton said:
[...]requirements say this
'MS Bluetooth Stack (WIDCOMM / Broadcom is NOT supported)'
I tried the software on my XDA iis with no luck, but i believe that it has broadcomm.
Thanks in advance.
Click to expand...
Click to collapse
Well if you believe it is a Broadcomm, then the software acts like it should, by not supporting the BT Stack, doesn't it?
well yes, but i want to know wether the software will work on the artemis. the software is btcrawler, you may have trouble finding it, as it is discontinued, but thanks for your replies.
If it need the MS stack then it will work on the Artemis, put it on and try it - Mike
By default has Orbit/Artemis m$hit bt stack. I tried 2 make widcom/broadcom from HTC Universal's (helmi_c) but i never made HFree profile 100% working(not even on Uni) - no chance to answer call with pressing button on BT Headset
alright, now i got it Sorry...
You're right, i did not find the Tool, but i had not very much time searching for it, but i think it will work with the Artemis BT Stack.
okay, thanks a lot for everyones replies.