Attn Widcomm & A2DP-users:a new, GREAT hack for all A2DP (Hi-Fi stereo headset) users
Many Dell Axim x50(v) (those that upgraded to WM5) and x51(v) users have noticed the device’s using the Microsoft Bluetooth stack, with all its problems and shortcomings. The situation wasn’t changed much by the AKU2.3-based ROM upgrades, which were only released for the x51(v) series – it only added non-full (for example, it just refuses to work with the Plantronics Pulsar 590A – this has also been reported by Solsie) A2DP support.
The lack of proper, compatible-with-all-headphones A2DP support in the new ROM versions made a lot of Dell Axim users stick with the well-known Widcomm hack to use their stereo BT headphones with their PDA's.
In June, mikelspikel and beemer, the main leaders of the Widcomm project, have released BTSpeedSwitcher, which fixed the problem of the stalling sound transfer between the PDA and the headphones. (For geeks / hackers, here are the Registry values this utility modifies.)
Up to now, it was the only solution for the problem plaguing almost all WM2003(SE) devices (and the WM5 Dells with the Widcomm hack): the sound would just stop after some dozen minutes, which can only be fixed by reconnecting the headset from Bluetooth Manager, after restarting the Bluetooth unit.
Now, mikelspikel has just come up with a much easier and, what is more important, generic hack that seems to be compatible with more models than the speed switcher hack (more on this later):
All you need to do is setting the DWORD Registry value HKEY_LOCAL_MACHINE\ SOFTWARE\Widcomm \BtConfig\ SerialTransport\ FlowControl to 0 (from the default 1). (You can, alternatively, import this registry file if you prefer importing pre-made registry files instead of manually editing the Registry.)
This hack, so far, has proved to be, generally, considerably better on two of my test devices (my old iPAQ h2210 with the HP 1.6 upgrade and the Fujitsu-Siemens Pocket Loox 720 with the PDA2k BT upgrade – please see this article for more info on these upgrades) than the BT speed hack (which doesn’t do anything on these two models, it seems).
Also, I’ve thoroughly tested the new hack with my Dell Axim x51v and found it to be perfect.
Make sure you give it a try! Also, if you have a different model, let the others know how it works.
Note that the hack (as with BTSpeedSwitcher) only works with Widcomm BT stacks. There is no point in trying to apply it on MS BT-stack based devices (to, for example, fix the Pulsar 590 problem).
A chart showing all the results of my tests can be found here
Note that, with the iPAQ h2210, you'll still need to reconnect in about every half an hour (after that time, it just starts to awfully skip). Still, it's much better than the default, hack-less, completely useless case.
Also note that I’ve also elaborated on the HP iPAQ hx4700 + Motorola HT820 combo in the chart as well (which don’t seem to like each other) in the last row.
Menneisyys, do u know if i can try the widcomm hack in my hp 6828?
Is it a Widcomm-based device? If it is, then, yes.
Menneisyys, thanks for your reply. I do not know if it's widcomm based device (or how do i check it?). hp 6828 is manufactured by Quanta similar to Atom and uses MS BT stack.
kjskho1 said:
Menneisyys, thanks for your reply. I do not know if it's widcomm based device (or how do i check it?). hp 6828 is manufactured by Quanta similar to Atom and uses MS BT stack.
Click to expand...
Click to collapse
Then, the hack won't work.
However, I've just published a new article on my latest hacks (including MS-related ones) - don't forget to check out http://forum.xda-developers.com/showthread.php?t=280454
ok, thanks! checking ur link... sad to say if i need to stick with MS BT stack, it sucks...
Related
I can't see it mentioned on any of the reviews for this device, which bluetooth stack is supplied with this device (broadcomm/microsoft)?
Thanks
No one got one of these devices and can take a look?
The Tornado has the Microsoft Bluetooth Stack.
Great! Thanks for the info.
As far as I know, all WM5 devices have the MS stack. If Broadcomm has revised their stack for WM5, no OEM I know of has decided to use it.
hey guys (and girls where aplicable),
i got a question (a sorta dumb one). If a smartphone lik the iPAQ 514 Voice Messenger or the HTC Vox have windows mobile 6 standard does that mean they run regular windows mobile programs or smartphone versions? See the Cheeta/treo 750 has windows mobile standard ed. and is called a smartphone but it uses regular PPC programs, the other two mentioned before have the same wm6 but no touch screen. so i was wondering if that made a diference in the phones capabilities to use PPC Progs? I appreciate any answers as i am greatly puzzled and intregued buy this.
With WM6 they dispensed with the term "smartphone" in favour of WM 6 Standard. Too many non Windows Mobile phones were being called "smart phones" as well as PPC phones.
WM Standard has no support for touch screens and many PPC apps will not run on it.
WM Pro has touchscreens.
understanding versions...
so lemmie go over this... a ppc with a touch screen is said to run WM6 pro, a ppc without a touch screen is said to run wm6 standard the "smartphone" version. so what of the vox? it has all the capabilities of a full sized PPC without the touch screen so where would it and the ipaq 514 fit in? Because correct me if i'm wrong but dont they offer features like MS Office editing and production verus the others whose ability is limited to viewing or is it the WM6 platform that actually enables this?
You're right, its just a functionality of WM6. Any smartphone (i.e. non-Touch screen device) running WM6 has those same office capabilities and will be running WM6 Standard, not Professional.
As far as I know the two WM6 are one same core of the same OS but..
In the PPC version there is more advanced setup in the menus wich setup is locked in the Srtandard by default.
For example in the Standard there is no way to change the IP of the wi-fi manually.
And in the pocket pc there is some dll's, responsible for touchscreen operation .
yes but....
i do believe you might be correct on everything but the I.P setup for standard. i have an sda running wm6 and i can manually setup my wifi and change certain settings in the network config. Also the HP ipaq 514 that i've been researching also has the same features. see my big thing is i love he compact size of the smart phone but need the capabilities of the PPC. It wold be great if i could get the best of both. i know the O2 XDA stealth has that exact combo but they are hard to find and kinda pricey for thier age.
There are separate SDKs for Standard and Pro, so I think the differences run a little deeper.
well what to do?
well i guess my final questions then wuld be what kind of phone are:-
1/ O2's xda stealth
2/ HP's Ipaq 514
Upon my fellow blogger Tim Hillebrand’s report and because I’ll need to quickly enter a lot of info at MWC (and I don’t want to lug around my desktop replacement and, therefore, pretty heavy IBM Thinkpad a31p just for inputting text), I’ve installed the latest StowAway / iGo Bluetooth drivers on all my mobile devices (even non-Windows Mobile ones) to find out whether the drivers available HERE are (still) compatible with the latest operating system / firmware versions. I’ve found out the following:
Windows Mobile
Pocket PC’s (a.k.a. WM6 Classic / Professional):
HP iPAQ hx4700 (WM5 AKU 3.5.2; selecting & using the Widcomm driver, NOT the MS one); HTC Universal (WM6), Dell Axim x51v (WM5 official A12 (AKU 2.3) ROM with the MS BT stack), HTC Wizard (mfrazzz’ XDA Mobile 6 Release 5 FINAL) and the WM2003 HP iPAQ 2210: all work OK with the factory, default driver.
(Note that, as far as mfrazzz’ XDA Mobile 6 releases are concerned, version 3 was a no-go at all: it didn’t even try to connect. Pressing the Disable built-in HID support doesn’t help at all – unlike with all my other test devices or the same Wizard running Release 5.)
Smartphones (a.k.a. WM6 Standard)
HTC Vox / s710 (factory WM6 Smartphone ROM); no native driver; therefore, I tested it with the s620 / Excalibur / MteoR driver (they’re the same – actually, it seems ALL HTC Smartphones have the same drivers, unlike with WM5 and pre-WM5 Pocket PC’s): OK
HTC Oxygen / s310 with the above MS SP drivers (no native driver): the config app doesn’t even load (“Keyboard driver not functioning!”); then, after closing it, I started to get system errors about the keyboard driver DLL not responding.
Blackberry:
BB 8800 (4.2.1.101 / 2.3.0.80, T-Mobile): Works OK; program invocation hotkeys also work as expected.
Palm OS:
Palm T3: Works OK, albeit some of the program invocation shortcuts (apart from the most basic calendar/ contacts / inbox) take you to some other program, not the default one (unlike with the WM or the BB version). Otherwise, it’s OK.
Symbian:
Nokia N95 (firmware version v20): No native N95 (or any new – the latest ones are dated from 03/2007; the Palm / WinMo / BB drivers have been released a bit later; for example, the BB one in 07/2007) drivers from ThinkOutside; however, the N92 driver works just great on the N95. All the shortcuts work (as opposed to the built-in drivers). Note that the green Fn + Backspace terminates the connection (unlike on WinMo), which, then, must be re-enabled by just re-invoking the wireless keyboard applet. Also note that, unlike with Windows Mobile, Alt+keys directly enters accented characters, which are a bit more cumbersome to bring up under WinMo.
Note that the built-in Tools / Connectivity / Wlss Keyboard works without the need to install any third-party driver – apart from the complete lack of program / task switcher shortcuts and the lack of the English Pound, Japanese Yen and Euro entry.
Conclusion
All in all, the drivers are fully compatible with even the latest devices / firmware versions on all mobile platforms. On Windows Mobile, all the tested WM6 devices, Smartphones and Pocket PC’s alike, worked just great.
That is, you don’t need to be afraid of purchasing the keyboard – it WILL (almost surely) work. The only device not compatible was the HTC Oxygen / s310 low-end MS Smartphone. This doesn’t mean there aren’t other WinMo devices incompatible with the existing drivers, though - it's just that I haven't found one.
Hi guys, I have been trying to get my XDAII to go online THROUGH my desktop computer via bluetooth. PAN.
Sadly, I am having ZERO luck!
On the desktop side, I was using the Toshibia bluetooth stack, I have also tested using the default Microsoft bluetooth stack, And also the bluesoleil stack.
On the XDA side, I tried and failed using WM 6.1 and the default stack, I then upgraded to 6.5 (Which is pretty sweet) and could not get the default stack to work via PAN either. I also installed Widcomm Bluetooth stack which provides much more output than the MS one.
After using the Widcomm drivers, I am getting the impression that my desktop is not offering the PAN service, but I am a little bit confused as to why.
If someone, could provide me with some current and up to date pointers (Please do not link me to random wiki pages made in 2005 - Its all changed!) I would be thankful!
I posted http://forum.xda-developers.com/showthread.php?t=520739 to begin with but i gather that is not the best place do it do
Hello,
did anyone successfully install a different bluetooth stack on a cotulla rom ?
i tried bluesoleil (but i only have a pretty old version). i also tried the toshiba stack (also pretty old version, build for 2003).
both work fine on 2003SE - but none of them work on cotulla rom.
anyone successfully did this ? or what about widcomm/broadcom ? what's so special about the magician bluetooth - i've never seen a widcomm version for magician - but for almost every other HTC device.
(i need a better stack than MS - since MS does not support BT LAN access, neither PAN (client))
In reality it's not easy to change BT Stack on Windows Mobile device...
Now my roms are using MS BT Stack...
I have some research and maybe some future versions will have BroadComm stack...but not sure...
Hello Cotulla,
nice to see you're answering about the bluetooth issue ;-)
broadcomm/widcomm stack would be great off course!
... in the meanwhile: as far i know, no broadcomm exists for magician - not even for the old ROMs - i never understood why (different BT hardware i guess ?).
but
- toshiba and
- bluesoleil exists for the old ROMs
they work - if you disable the microsoft drivers (cause it's not possible that both drivers use the same hardware - i guess).
bluesoleil: comes with a tool to disable the MS stack.
toshiba: you have to do it manually by taking off bticon.dll from HKLM/services.
so i have a question:
"taking off bticon.dll" from HKLM/services" is for 2003SE -> what is to do in WM6 to disable the MS-stack ?
maybe the toshiba/bluesoleil would even work ? did anybody tried before ?
or is this bull**** ? i heard of different "driver-models" between CE 3/4 and CE 5 - so is it even possible to use drivers from CE 3/4 on CE 5 ? i don't know! but i'm sure, you know ! ;-)
thank you cotulla for your great work! i'm wondering how you managed to get that much knowledge about this device! great!