Check this out !!
http://www.windowsfordevices.com/news/NS3839185925.html
I've just had it with MS BT stack not being able to retrieve remote device names from incomming connections. Hopefully this new version should solve our problem. But now the question is ....... How the hell are we gonna get our hands on this new version of Broadcom's BT stack ??? :?
And what's so new about this?
The press release is from june 1, 2005 :?
Sascha
Well ...
It's true that the stack was announced long time back, but if you read carefully, it seems they already have released it to some mobile manufacturers and will be releasing it to the public very soon. Which means new hope for our BT enabled pdas instead of that old crappy MS BT stack we have been suffering with.
ummhhhh. that's good. and when will we get this?
Maybe I just missed it, but the article doesn't seem to specifically mention WM5 support.
Where can i download the stack? haven´t found anything in the forum.
There's no such stack. It's discussed over the the so-called xda wiki here...
Related
Hello there!
I was seriously thinking about buying myself one of those Bluetooth stereo headsets. Unfortunately they need the A2DP Profile which isn't included in our present MS BT stack.
I have read a lot in this forum about transferring the Broadcomm/Widcomm stack - a guy even offered 200$ on success. Yet so far no success.
Now I was wondering if it would not be easier to add that profile to the existing stack somehow? By "somehow" I mean that I am not a programmer and havbe no clue how to do so on my own.
Any suggestions or help?
Cheers, <))><
Hey Guys!
At least a simple "No" or some reply would be nice. I can't imagine that I am the only one who looks for something like that
Well I just tried to find a thread for you over at Howard Forums but was not successful. Go over there there is a poster named "whtrbt7" he seems to know a bit on this subject.
Basically I believe the short answer is no.
I think we are a year or so away from getting true full stereo audio via A2DP Profile.
I'm no expert on this subject, but I believe there needs to be more consistance and control within the BT industry as a whole.
i just posted this link in another thread but maybe its useful to you:
http://www.send2press.com/newswire/2005-03-0311-002.shtml
iWALTZ enables multimedia mobile phones using MS Smartphone(R) and MS Pocket-PC Phone(R)-Edition to stream music over Bluetooth, seamlessly switch between music and voice calls, and display rich media related information on wireless accessories.
"Mobile phones are transforming to be the next generation multimedia devices," said K.Srikrishna, CEO of Impulsesoft. "iWALTZ enables this transformation by delivering an integrated Bluetooth audio experience and significantly reducing time to market for mobile phone OEMs. Impulsesoft is working with multiple mobile phone OEMs to deploy iWALTZ in their products that are launching in the first half of 2005."
Click to expand...
Click to collapse
Maybe soon we we are able to get a2dp working on the magicians
Cheers,
Rainer
Cheers for the answer! I hope so too. Just installed the newest Widcomm Soft on my PC in order to give it "More Power" (Tim Allen from Home Improvement). Now I can't wait to make A2DP work somehow on our Magicians. It would be like Star Trek :wink:
anyone been able to successfully, and possibly flawlessly change the bt stack on there magician? i just spent around 6 hours trying to change mine over, first to widcomm 1.4 and then 1.6 as well as the broadcom stack, nothing.. kept giving me the memory error and asking to restart.
better Bluetooth stack
hi, if you want to replace Bluetooth stack try this one:
http://forum.xda-developers.com/viewtopic.php?t=18537
there is an easy guide how to do it, and where to get it.
thanks, checking it out now.
tried with my O2 Xda II mini
but still failed to listen to MP3 using bluetooth :-(
Hi All,
Unlike the T-Mobile MDA Compact, does the Vodafone VPA Compact a Widcomm BT stack? Anybody tried?
[url]http://www.plawa.com/support/...800bt_kompatibilitaet_treiberzuordnung_de.pdf
[/url]
---
Hersteller Status Betriebssystem/Bluetooth
T-Mobile
MDA Compact
Windows Mobile 2003™ 4.21.1088 (Build 14235.2.0.0),
Microsoft Bluetooth stack
Vodafone
VPA compact
Windows Mobile 2003™ SE 4.21.1088 (Build 14132)
Widcomm BT-PPC/PE Version 1.0.0 Build 1900
Greetings Ben...
So if this information is correct we need a VPA Compact rom. Anyone?
Ok, well if that .pdf file is correct, harrah! However, Expansys have listed the VPA Compact as a discontinued item. I can't find a single store that sells it, so maybe it's over before it began!!
After a quick search there is no ROM is availabe over the internet. The hope is the dumping. But my knowledge is this phone is sold only in Germany. Not sure!!!!
hbahaie said:
After a quick search there is no ROM is availabe over the internet. The hope is the dumping. But my knowledge is this phone is sold only in Germany. Not sure!!!!
Click to expand...
Click to collapse
Thanx to Google:
http://download.vodafone.de/spopup16.html
It is a German ROM 1.12, coming from Vodadafone.
Greetings Ben...
OK, well does anyone have the ability to extract the stack and find out whether it's widcomm or MS? I certainly don't!
I've done a google translate of this page and it doesn't mention anywhere about which phone it's for. I'm guessing you selected this on the previous page?
And what's with the constant reference to blackberry? Has vodafone acquired blackberry software now?
Makes me want to just install the rom and find out, but I can't read much german!
jimmy-bish said:
OK, well does anyone have the ability to extract the stack and find out whether it's widcomm or MS? I certainly don't!
I've done a google translate of this page and it doesn't mention anywhere about which phone it's for. I'm guessing you selected this on the previous page?
And what's with the constant reference to blackberry? Has vodafone acquired blackberry software now?
Makes me want to just install the rom and find out, but I can't read much german!
Click to expand...
Click to collapse
http://download.vodafone.de/
Upgrades for handheld
The link to Blackberry is that exchange between VDA Compact & Blackbeery needs the VDA Compact rom 1.12 upgrade.
http://download.vodafone.de/index_l3_2d.html
http://download.vodafone.de/index_l3_2d.html#vpacompact
Then you see the license agreement page.
Greetings Ben...
Hey i upgraded stack to bluesoile, how do i downgrade back to original stack? i backuped deleted registry keys?
Dakky said:
Hey i upgraded stack to bluesoile, how do i downgrade back to original stack? i backuped deleted registry keys?
Click to expand...
Click to collapse
You're better off posting that one in the bluesoile thread, dude. You'll get more help there.
Berkens.. Ok cool, so it is the rom.. (just worked out you need to click on the link that says "heir" to see the ROM), but how do we find out which bits we need? Can Buzz or anyone with ROM experience tell me whether there's any substance to this?
Hi,
I updated my T-Mobile MDAc with this and it's similar to the T-Mobile update, no new BT-Stack, just Vodafone branding
Bugger! Oh well, got our hopes up for a bit!
sack said:
Hi,
I updated my T-Mobile MDAc with this and it's similar to the T-Mobile update, no new BT-Stack, just Vodafone branding
Click to expand...
Click to collapse
How would one be able to tell if it is the MS stack or Widcomm one?
I've not seen the Widcomm stack running on a PPC yet- so wouldn't know.
I'm sure like most here, the interest is whether you can get the A2DP profile setup on the MDAc.
I'm sure this is 'easily' possible- just need some with the know how i guess...
EDIT: Just noticed the BT Stack for the VPAc is exactly the same as for MDAIII- so is this a mistake regarding the VPAc stack running Widcomm. Or is the difficulty in uninstalling the MS BT?
Me and a group of talented developers here in Dubai are proud to announce the semi-completed BT Stack replacement for wm2003,wm2003se, and wm2005.
What we have learned so far is that the listening component of the MS BT Stack sucks big time. Our first aim with the new addon/replacement is to make windows mobile retrieve remote device name on incomming connection. And guess what...... It Worked !!!!!
Our first Beta version that will be released shortly, includes a BT listenener that replaces Microsoft's BT Stack Listener and will accept all incomming connections with added bonus of showing the Sender Device's BT name without having to first pair with the remote device. It also includes a File Save Dialogue Box that appears whenever incomming files have arrived and will allow you to save all these files to your own selected destination.
We hope that this BT Replacement Project will succesfully replace some major parts of the MS BT Stack and add some more important functionalities to our pda's.
Date of release: Very Soon ...
Device Compatibility: All HTC PDA phones that use the MS BT Stack.
OS Compatibility: wm2003, wm2003se, wm2005 (All Versions so far)
Price: Absolutely FREE !!!
Wish us luck .... TAN Software 2005
cool.. maybe it the answer in the BT WM5 Problem...
okay.. its a Blue Angel problem.. but i wait ^^ :lol:
eviltrooper said:
cool.. maybe it the answer in the BT WM5 Problem...
okay.. its a Blue Angel problem.. but i wait ^^ :lol:
Click to expand...
Click to collapse
So, where is it??? :lol:
Re: Great News... 70% Done... New BT Stack Replacement 4 wm2
Hey if u need my help, lemme knw. I live in dubai.
Do you intend that your replacment stack will support A2DP?
I'd shoot me in the head if I'd get WM5 on my Magician and then it would even be able to act as A2DP-SRC... :lol:
Support for A2DP profile on my Magican is what I'm waiting for... which I definitely would pay for!
I've even got the compatible bluetooth headset...
@sh500: How do you use it at the moment? I plan for gift and I dunno which way to go. It should be A2DP headset as well as call headset used on a Magician. And Voice Command should be activated over the headset. Too much to ask?
wonderful!!!!!!!!!!!
Thanks For you effort,
but hope that it is a developement of widcomm stack cause ms stack is poor in its functions (there is no network support or other widcomm services),so hope that the new stack will be full of inovations.......
Thank you a lot
Sounds great! Can't wait to test it!
very good
i am so happy to hear such a news
This is an example of the type of device the new stack will hopefully be compatible with
http://www.tekkeon.com/site/products-ez3000.php
Good luck!!
I sure do hope that it is the b/t solution with WM5 on the BA........I had to switch back to 2003SE and it is not near as nice as WM5, as well as the fact that I now have to soft reset once a day again with 2003se.
Later.......... 8)
eviltrooper said:
cool.. maybe it the answer in the BT WM5 Problem...
okay.. its a Blue Angel problem.. but i wait ^^ :lol:
Click to expand...
Click to collapse
Good Luck
i wish you all the best in this project, also i hope it will work with WM05
Date of release: Very Soon ... Very<----- how soooon?
could be compatible with axims x50v using wm5 upgrade ... Ms stack sucks!
Widcomm 1.50 working on WM5.0
Maybe in the meantime those using WM5.0 could take a look at that...
http://buzzdev.net/index.php?option...c=view&id=6671&catid=26&limit=15&limitstart=0
Dunno if it's specifically for Himalaya running WM5.0, but...
Haven't installed it myself so I can report success or failure.
Read carefully the thread for instructions.
Cheers,
Hal
this is most needed for the wizard basically theres no bluetooth for it.
Dont forget with the Widcomm stack bluetooth voice dialling doesnt work.
I dunno why everyone complains about MS Stack... it just lacks a lot of profiles. But when they are added the stack is more or less ok, isnt it?
You may have heard (particularly if you’ve been following my past articles) about the differences between the Microsoft Bluetooth stack coming with HTC Phone Edition devices and know its major shortcomings when compared to the major alternative, the Widcomm / Broadcom BT stack:
It lacks BT PAN (albeit the latest AKU3 has some basic support for BT PAN server functionality) support, which would be of high importance in, say, chatting / talking apps (for example, 4Talk or Microsoft Portrait or multiplayer games)
It, as far as versions prior to AKU3 are concerned, lacks support for BT FTP (see THIS ARTICLE for more info)
It has wildly inferior A2DP (stereo Bluetooth headphones) sound quality
No wonder a lot of people have been actively trying to “hack” the Widcomm BT stack on Pocket PC models initially coming with the Microsoft BT stack. Of them, the WM5-upgraded Dell Axim x50(v) and the x51(v) may already be known to you (I’ve also posted a lot on the project; see for example THIS).
Some weeks ago, well-known XDA-Developers hackers started to work on the port to HTC Phone Edition phones; for the most part, with success.
For the most part, you may ask? Yes, unfortunately, there still are problems; they are as follows:
Currently, it’s not possible to use traditional Bluetooth headsets for calling. Upon trying to connect to the headset, the PDA will just display an error message as can be seen in HERE. In the Hermes Widcomm developer thread, people are working on fixing this issue; so far, with little success. This will be a showstopper for many.
You won’t be able to use the PDA as a modem via Bluetooth (see my tutorial here) using either pre-AKU3 DUN or AKU3 Internet Sharing BT PAN. Also see this thread for my posts on this problem.
That is, if the lacking functionality is a showstopper for you, do NOT consider switching BT stacks as yet.
Model-specific tutorials / threads
Check them out for a discussion and / or a tutorial for installing the BT stack on your particular phone model:
HTC Wizard
HTC TyTN (Hermes) (my earlier report)
HTC Trinity: it seems it still doesn’t work at all (I’ve tried hacking very hard).
HTC Universal; well-known Pocket PC hacker and coder Helmi has just announced he’ll really soon release a working version even with headset support. I'll keep you posted.
it may sound silly, but does this stack appear in the uninstall list? so, am i able to remove it?
i'm asking because last time i changed my bt stack i ended up with my wizard being mute all the time. luckily i was able to restore my old bt version by uninstalling new one. so how is it with this one?
BTW, here's the Headset-enabled (!!!!) Universal BT stack hack: http://forum.xda-developers.com/showthread.php?p=1115973
banannq said:
it may sound silly, but does this stack appear in the uninstall list? so, am i able to remove it?
i'm asking because last time i changed my bt stack i ended up with my wizard being mute all the time. luckily i was able to restore my old bt version by uninstalling new one. so how is it with this one?
Click to expand...
Click to collapse
Yes, it can be uninstalled - I haven't had any problems doing so on my Wizard and on the Trinity. Note that the Universal uninstallation is a bit more tricky.
banannq said:
it may sound silly, but does this stack appear in the uninstall list? so, am i able to remove it?
i'm asking because last time i changed my bt stack i ended up with my wizard being mute all the time. luckily i was able to restore my old bt version by uninstalling new one. so how is it with this one?
Click to expand...
Click to collapse
Yes, it can be uninstalled - I haven't had any problems doing so on my Wizard and on the Trinity. Note that the Universal uninstallation is a bit more tricky.
Has anyone come up with a solution to route **INCOMING** VoIP audio to the internal speaker on the S710/VOX?
The vanilla S710/Vox VoIP install (at below link) works great out of the box, except I can find no way to redirect incoming audio to the earpiece. The conversation always plays through the speakerphone.
http://forum.xda-developers.com/showthread.php?t=311087&highlight=voip
There’s lots of talk about this problem on the Development and Hacking board—but I cant find a published solution—For **ANY** wifi enabled handset—even with cooked ROMs.
Any suggestions-- ??
THANKS.
Same Problem
Please, Help !!!
This problem is only with this phone, urgent VoIP Services please...
TAL
OK-
Ive found two solutions-- unfortunately, both for **PPC**.
Glofiish X500—WM5 non cooked:
http://eten-users.eu/index.php?showtopic=9556&hl=
SPV M3100—WM6 cooked:
http://forum.xda-developers.com/showpost.php?p=1400247&postcount=783
Several posts on different boards indicate this is an **OS** problem. Seems to me if this is true we are out of luck until an official ROM update (because there are no S710/Vox SP ROM Hacks out there).
On the otherhand—
The implementation may lie in the VoIP .dll’s which may be worth looking at since there are some floating around for SP's and PPC's.
Can anyone **CONCEPTUALLY** confirm the above?
Of course—
There may be an temporary workaround like the Glofiish solution.
Thanks.
From a posting on Modaco: would the headset solve the noise/privacy issue? I have not yet tested (I use Skype) but it seems like a reasonable workaround.
This issue is NOT SPECIFICALLY related to the S710/VOX!
THIS IS A CROSS POST-- TO CLOSE THE ISSUE IN THIS THREAD--
I EXPECT A NEW ISSUE-RELATED THREAD IN THE "DEVELOPMENT AND HACKING BOARD" SOMETIME SOON. THOSE GUYS KNOW WHAT THEY ARE DOING-- SO I THINK THATS WHERE THE ISSUE BELONGS.
And I Quote from Windows CE Networking Team WebLog:
http://blogs.msdn.com/cenet/archive/...ws-mobile.aspx
“… On some Windows Mobile 6 SKUs, VOIP (Voice over IP) is supported. This functionality is based on RTC. So, RTCDll.dll (RTC binary) will be available on some of the WM 6 SKUs. However, on these SKUs, RTC is not released as an SDK, but solely to provide the VOIP functionality. So if an application wishes to use RTC on these SKUs, it is free to do so, but that scenario won’t be supported by Microsoft. …” (May 23, 2007)
My reading of this is simply:
In order to “correct” the speakerphone problem, you gotta “correct” the rtcdll.dll.
And since all we have is a Microsoft binary release of the .dll (there’s no source out there, correct?) the only solution would be to write a new handset-aware (hardware-integrated, lets say, native) sip-client. And that’s not trivial without rtcdll.dll source.
That’s basically why the ROM-chefs havent come up with a solution… yet.
Or:
Is it as simple as getting the correct registry-settings?
I think not. I can think of several reasons why there’s likely no easy/simple registry fix.