Related
Hi Guys: I have got the Widcomm Phone edition stack working on my unit.
It seems to be fine but I have not fully tested all aspects of the software - so if any little bits don't work, let me know...
You need to install the official widcomm 1-4-1-59 version
Then you can upgrade it using the cab file I have made.
The 1.4.1.59 version file I got from the following topic
http://forum.xda-developers.com/viewtopic.php?p=57550#57550
thanks go to mamaich for the file.
the upgrade file consistes of the PE edition files and the required registry entries.
Let me know how you all go on with it - but I am not really a hacker so any serious probs I will not be able to fix...
if anyone else can improve on the installation be my guest
any news about which profiles it support that ms or the old one dont support ?
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
I can't garauntee it works perfectly, so I suggest everyone make a backup of their system before use.
has anyone tested any BT headset with this new stack?
I've got it installed and it all seems to work well exept for the handsfree/headset profile, I have set up my headset ok it is discovered and bonds fine but when I try to connect from the xda2 the connection fails after "waiting for device" for some time. tried with a motorola hs 810 and a neovoice usb, same with both. Anyone got any ideas?
BT headset
I have a 6315 and an XDA 2, I haven't tried the BT Stack on the XDA 2 yet but I found when I bondeded my HBH-30 to my 6315 once it made the connection my BT Headset shut off for some reson. This caused the bonding to fail, but as soon as I turned my headset back on (while it was trying to discover services) it completed the process and worked on my 6315. I'm not sure if this will be the same, but it's worth a shot.
Brandon
Test results
Hi fellows
Here is little bit of my testing of this new BT Stack, which we all awaiting for..
Proc…
1. Installed as per instructions 1.59 without any problem. During installation was prom to override .dll files – agreed to do that. For good or for bad – will see later.
2. Installed .cab file provided by icarusbop (big thanks to him for doing this) without any problem. Screen shots will be attached below.
3. Reset it as requested upon installation and got Widcomm BT working instead of MS BT..
4. Paired it with my BlueTrek G2 within 3 seconds (which took usually 10 sec with MS BT)
5. BT recognized G2 as device with Headset/Hands-Free profiles and asked to use as default… I said yes…
Here comes Cons part ;(
1. Unfortunately even after paring – my I-Mate can not get connected with G2 (see screen shot)
2. As you can see in another screen shot – there is Hands Free menu – it can not be accessed, or can be accessed ONLY while connection is established.
3. AND the last L … So, this new BT is not working now… I decided to go back to MS BT… SURPISE!!! I am getting message that BT HARDWARE IS NOT INSTALL ON THIS UNIT…. L Assumption - .dll files were overwritten (see Proc 1)
Here is my 2 cents in this jorney… I am hoping that described problems can be fixed and we can make it working (without doing hard reset on my device )
Paul
thanks guys! for testing hands-free/headset profile. by now everything seems to work fine with this new stack except for hands-free/headset profile.
New comments to my testing
1. I tried what NeoCole recommended - didn't work for me
2. As soon as new BT is OFF - MS BT is working fine .....uf
LETS FIX THE HEADSET PART PLEASE
I posted this is another thread - but in case someone does not read that thread . . . it is relevant here as well.
If the intent of this is to get voice dialing without touching the device, that is by only pressing a button on the headset to initiate a voice-dial program to make the call, there is no evidence this works with this BT stack either.
I have been reading other forums with people who have the H6315 already (mine is in the mail to me now) and none of them have been able to make this work. Nor is there any mention of this capability in any of the literature and/or documentation for this device. It seems that if this was a feature of this phone, it would be prominently displayed!
Voice Command
Okay.. on my 6315 I press the headset button, it beeps, sound and voice is now transfered to the headset. I do this before I initate voice command. Now all I do is press a button that activates Voice Command on the PPC and walla, I'm speaking and listening through my BT Headset. This is a huge step forward from using the MS Stack, and I feel that since the Phone Edition of the Widcomm is 1.0.0 I'm sure that they'll associate a hardware button with the headset button in future releases. Anyhow.. I think that the functionality of the Widcomm BT Stack is well worth the work. The XDA 2 would be a lot better device if the BT Stack worked 100% of the time and was fully compatibile.
I also have not got it working.
the Hp 6315 is well know to still require a hardware button press (not on the headset) to activate voice command. They can still not do with any nokia or SE phone can do easily.
Surur
VoiceCommand
That would be correct... One press of the HW Button does it all on a Regular phone.
The 6315 has brought it closer to allow you to interact with programs using your BT Headset, but yes you must still activate the programs on your handset before you can use them with your headset.
So.. to sum it up...
1. You can't interact with Voice Command using MS BT Stack on an XDA 2
2. You can interact with Voice Command using Widcomm Stack on 6315, but you have to activate the headset first, then start VoiceCommand on the PPC by using the HW Button.
Hopefully through this thread we'll be able to give the XDA 2 the same functionality as the 6315.
And maybe if Widcomm provides an update to allow the headset to activate a HW button, we'll be to the one step solution.
I do not want my comments to be read as stating that this is not a worthwile endeavor. I simply meant to make sure that someone does not go to the trouble of installing this new stack (particularly those who might be considered novices) with the mistaken impression that by doing so they will have that "one step" voice dialing solution.
This is by all means a worthwile endeavor, but it is merely a step down the road . . . not the final destination.
Y'all are doing good work - keep on blazing that trail!
hm.. I would think that it is more of MS Voice Dial functionality than BT - to recognize signal sent from headset as request for voice dialing.
When MS released first version of Voice Dialing they did not expect new functionality to have BT headset with hands-free profile connected to the device.
paired with my Jabra 250 = ok
connected to my Jabra 250 = failed
No luck with Moto headset
Eveything else seem to be working. No problems with detecting and working with BT access point
rehman said:
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
Click to expand...
Click to collapse
Hi Rehman,
i tried to install and uninstall, for the very first time i didn't have to get a Hard-Reset done. the volume didn't disappear. so i believe trying it wont be a harm, but yet i would recommend to get a full Backup first.
Trying to figure this out
Okay, I looked through the whole registry. I can't find anything out of the ordinary. Only thing I can think of is the sound driver. Does anyone know what DLL that is? I bet it's a different version.
If someone that knows more about which DLL does what. Let's get all the DLL's that could pertain to Sound and Phone and compair the 6315 DLL's with the ones on the XDA2.
I have upgraded to the new O2 Rom 169 and all seemed ok, until I started to install my bluetooth head set.
Since I upgraded my radio ROM to 1.03 I have lost the connections to my headset.
Prior to the upgrade it worked perfectly, now the recieve functions just will not work.
I have down graded to the radio 1.00 ROM but the same thing is happening. So the upgrade seems to have corrupted something more important.
Can anyone help here?
Downgrade to previous ROM
I have now downgraded to the previous ROM 1.11.162WWE, and that seems to have solved the problem.
I have installed the Radio ROM update and that seems to work OK now, so I will stick to this for the moment, unless someone has any better ideas!
Hello,
I had the same problem. It seems, the old bluetooth software won't work with the new radio rom. I tried my bluetooth connection before restoring my old stuff from backup, and it's ok. I didn't have any serious things in my backup, so I reinstalled my software from install cd's - sorry, I had no time to figure out, wich software causes this issue, but hope this information will help you.
Z.
i also having problem with my bluetooth but I cant say the problem is from new radio ROM or others because i dont know the real cause. A message display and wrote
"Sorry! Bluetooth can no longer be used because the licence is expired"
"BDA ff:ff:ff:ff:ff:ff: Key:E3E534E19B3E8214C543A73C0A8B9A9074DD3B1753515CD8"
after that, bluetooth will off automatically.
I have found since the upgrade to the new radio, thanks PUG.
That my Handsfree and Headset Bluetooth issues have lessened.
A few little glitches but will be on the outlook for another patch or upgrade in the future :roll:
Hmm,
I have radio 1.00.00 version with t he original Asia ROM and something funny has happened:
Since the beginning, I successfully connected to Logitech and Hello II BlueT headsets + a generic car BT handsfree.
I had to perform a hard reset after one of my progs messed the registry and reinstall everything (less the troublesome prog <g>).
Since then, the BlueT handsfree does not work properly: I hear the ring but there is no volume control from the headset and I hear nothing + mike does not work. The rest of the BT conections work flawlessly, except for some rare disconnects from my BlueT RBT-2001 GPS.
The story in this thread is not encouraging but one thing is clear - the BT problems that I have are with the original radio and EROM and not after an upgrade. I have no clue what all this means except for the fact that tere is something quite problematic w/ the Xda IIi BT connectivity that I didn't have w/ any of my previous PDAs.
I thought to u/g the radio version only but decided to go for a full u/g (less the O2 stuff), hoping that my BT problems will go away.
Please correct me if I'm wrong - should I go ahead with the PUG O2-less upgrade or should I keep the old (but clearly buggy) versions?
Maybe all the problems that we have are connected to specific manufacturing HTC batches? Has anyone researched this? Is there any info correlating between problems and Xda IIi serial numbers?
Best regrads,
Al
Hi,
I have radio 1.00.00 version with t he original Asia ROM and something funny has happened:
Since the beginning, I successfully connected to Logitech and Hello II BlueT headsets + a generic car BT handsfree.
I had to perform a hard reset after one of my progs messed the registry and reinstall everything - NOT from a backup but from scratch (less the troublesome prog <g>).
Since then, the BlueT handsfree does not work properly: I hear the ring but there is no volume control from the headset and I hear nothing + mike does not work. The rest of the BT conections work flawlessly, except for some rare disconnects from my BlueT RBT-2001 GPS.
The story in this thread is not encouraging but one thing is clear - the BT problems that I have are with the original radio and EROM and not after an upgrade. I have no clue what all this means except for the fact that tere is something quite problematic w/ the XDA IIi BT connectivity that I didn't have w/ any of my previous PDAs.
I thought to u/g the radio version only but decided to go for a full u/g (less the O2 stuff), hoping that my BT problems will go away.
Please correct me if I'm wrong - should I go ahead with the PUG O2-less upgrade or should I keep the old (but clearly buggy) versions?
Maybe all the problems that we have are connected to specific manufacturing HTC batches? Has anyone researched this? Is there any info correlating between problems and XDA IIi serial numbers?
Best regrads,
Al
Is anyone else finding that their bluetooth is really slow at sending and receiving items. Also that there is no way to send items direct to a contact that is in your partnership list, you have to search for them every time you want to send something. If someone has found ways around these problems, please let me know.
an adaption of the Blue angel's bluetooth interface would be lovely. It had loads of options, and let you explore remote devices. This is just like the XDA2.
Would it be possible to port the BA software onto the wizard? I think it uses a different BT stack.
they were able to port the wizards rom to run on a blue angel. I guess they should be able to use the blue angels bluetooth on a wizard.
Please help - is so annoying
Ok, after a little research i found this thread http://forum.xda-developers.com/viewtopic.php?t=33532 .It has an app which i installed and has helped a little. I can now send images direct to people i have paired with without having to search local bluetooth first. The thing is it only sends images to paired people. I want it to also send sound and video files. When in file explorer, holding down on an image brings up the extra option of "Send image via bluetooth" which then allows to send by the already paired devices. When doing the same on videos and sound, it doesnt give this option. Maybe this can be done in the registry, but i dont know alot about that so maybe someone could help?
i tried this on my kjam and i had a problem with it, so i uninstalled it.
the problem i had is that the bt keep switching off by itself with no reason, even if i was already syncing over bt, the connection is lost suddenly and i found out that the bt is off (even though the bt icon on the system tray shows its still on).
i don't know about you guys, but i had this prob twice, i reinstalled it again and gave me the same prob.
i can live without it.
Ok, maybe that stack is not all that great. After soft reset lost all sound, and BT does not work properly. Uninstalled and back to normal. So again is there any way to send to people in your paired list without having to search for them every time. Is becoming a pain coz some new phones turn off discoverable after 60 seconds. So they have to keep turning theirs back on. Its a simple option, dont know why they didnt put this in. Any help?
I haven't seen more than 50-60KBps. Has anyone else seen higher transfer rates?
Wizard's BT is useless. Buggy, slow and poor.
And it is not v2.0, it is v1.2
It does not have EDR.
It doesn't even have PAN ffs... :x
tsiros said:
I haven't seen more than 50-60KBps. Has anyone else seen higher transfer rates?
Wizard's BT is useless. Buggy, slow and poor.
And it is not v2.0, it is v1.2
It does not have EDR.
It doesn't even have PAN ffs... :x
Click to expand...
Click to collapse
Info about BT in wizard. Directly from BT CIG's site. The problem is not with the Wizard, it is in usin MS BT stack.
thanks for that emmeborn, if the problem is the stack, do you know of a stack upgrade which works good? I tried the stack form the blue angel, but stuffed up my phone, so uninstalled it.
actually, i just looked at those pdf files, and at the bottom where it has the revisions, seems they have launched a version around 1 month ago. Would this be a software or hardware update. If its software then i reckon this could solve alot of problems im having.
Enervate said:
actually, i just looked at those pdf files, and at the bottom where it has the revisions, seems they have launched a version around 1 month ago. Would this be a software or hardware update. If its software then i reckon this could solve alot of problems im having.
Click to expand...
Click to collapse
It is the long awaited rom update. A test version of that rom has already leaked. You can find more info in the Wizard upgrade forum topic about that version.
I am awaiting the localized swedish version of that rom and the latest about that version is that it should be released mid March.
Hi!
In the last some days i read a lot and found the following :
1. download the widcomm stack from axim site : LINK
2. install it + do a soft reset
3. get a registry edittor (Resco, CECMD etc.)
4. change these values :
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BtConfig\SerialTransport]
BaudRate=115200 (Won't start at higher rate.)
Device=COM
FlowControl=0
Parity=0
Port=1 (This is the most important thing!)
-soft reset
-at the today screen you will find a BT icon, click on it and have fun
TESTED FEATURES
-BT FTP, tested with : SE K750i, hx4700.
-ActiveSync : NOT WORKING
KNOWN ISSUES
-unable to control from comm manager
-blue led not flashing, easy to forget
-a2dp not tested
-tested on aku3.2 and aku2.3 roms, others maybe ok.
-other devices can't download bt services list, but the services works well.
-maybe unable to remove, not tested yet
-turns off, when you trun off your device, that maybe a problem with BT headset.
DO IT ON YOUR OWN RISK
Great news! Posted an announcement to the SP & Pocket PC Mag Expert Blog too!
Problems!!!
I've just installed the bluetoth stack in my phone. I've not yet tested it but i've found two showstop problems:
- activesync doesn't work anymore
- i cannot start the comm manager anymore (when i press the comm manager button in the upper left corner i can see only a small dialog with wifi and bluetooth power levels)
This is what i've done (maybe i did something wrong):
- copied the cab to storage and ran it (installed in device)
- soft-reset (required by the installer)
- edited the registry according to the first post
- soft-reset
I'm using an aku3.2 rom
-----EDIT--------------
Comm manager is working again. I had to reassociate it in Start-Settings-Buttons
Still no activesync (over USB at least)
bye
bye
Has anyone else tried this then? Has anyone tried the hermes cab install found in here...
http://forum.xda-developers.com/showthread.php?p=1072292#post1072292
There has been reports that it works on the trinity as well, so it may work on the Wizard.
Edit: No it doesn't. I have just ried it and it gives the memory error.
took the plunge and tried it
Bluetooth works and I can connect my itech S35 to it. The A2DP profile is detected and can connect... problem is, the signal is too weak to maintain a connection, in other words, I just heard 2 seconds of music and that's it... Another problem is my speakers now don't work... must do more reading...
It's hopeful though...
I am using a Dopdo838...
new2city said:
Bluetooth works and I can connect my itech S35 to it. The A2DP profile is detected and can connect... problem is, the signal is too weak to maintain a connection, in other words, I just heard 2 seconds of music and that's it... Another problem is my speakers now don't work... must do more reading...
It's hopeful though...
I am using a Dopdo838...
Click to expand...
Click to collapse
Did you try tweaking the BT params (for example, lowering the bit speed) to see whether it would work at lower bit speeds? See my related articles.
got look out for the links to your tips and tricks again
Hi Menneisyys,
Surrendered on Widcomm stack almost 2 months ago, now have to look again for the links for your tips and tricks for the Widcomm stack again...
Any idea on how to restore audio to my speakers... still dead at the moment... sigh... don't want to restore my back up yet...
i found that you don't really need to remove the shift* keys. if you already removed it, download the BTSpeedSwitcher from the download link, and set the speed to 921600bps. that may help.
Got it working fine
Thanks, but now I am a bit unclear, but will clear things up later. I used the speedswitcher as you suggested and but I had to disable audiogateway before it could work... now I am stuck as I put my wizard into standby and now it won't come back.... on... doh!
Well, one thing I can confirm, you can put it into standby and the bluetooth is still on.......
will feed back more when I get a clearer picture of what happened.... The sound quality is great..... just skipped for a second but is not back to normal again...
My wizard has now a nice quality A2DP sound without the high pitch noise...
went to http://forum.xda-developers.com/showthread.php?p=1073003&posted=1#post1073003
and used the files from Superdave... all is well now... look at my reply at the hermes thread.. Now I will just back up this "working configuration" and retry these settings on the cab from Aximsite... All the same, thanks to the legendary Mikelspikel
Just wanted A2DP to work so bad.... and it does now. nicely..
new2city said:
Got it working
Click to expand...
Click to collapse
Okay, when you get time can you stick up how you got it all working? Many Thanks!
Ive installed the Superdave BBS_HERMES_03.CAB file and then modified the registry to use the above settings but every time i do the soft reset, the registry settings go back to the original values. Im stuck here.
Oh and i am using the last T-Mobile UK rom. (2.0 i think)
Edit 2: Now got it working. I had to kill voicecmd and cprog for it to load without giving the memory issue!
new2city said:
you can put it into standby and the bluetooth is still on.......
Click to expand...
Click to collapse
as it should - BT is on on PPC PE devices in standby mode, unlike on plain PPC's.
peetking said:
-unable to control from comm manager
Click to expand...
Click to collapse
It looks like comm manager is just an HTML document in the /windows directory. (Should be simple to redirect the button)
Leaskovski
sorry for the late reply but had a few setbacks during the night(I am in Malaysia)..
Got A2DP running all night and by mid morning... suddenly all went to hell..
1) No skipping with your suggestion of using MikelSpikel's speed switcher.
2) While trying to put it to standby to test if BT still works and it hung at first attempt. Something must have happened here as I recovered using the reset button and then suddenly I could get it to revert back to built in speakers and headset without issue. I thought, cool, it is like complete solution...
And then, I decided to backup this "complete solution" with SPB backup.. and after the softreset, I lost the ability to switch between headset and speakers. Then during the night while I sleep and use the headset, at around 3 am... the skipping came back...
and then... I restored the backup and now... got to tackle the skipping again.. never mind the muted speakers..
What linespeed(I use 320 dec), Blocks(16) and subband(8) do you use? I followed MikelSpikel's settings which work ok... last night...
back to the drawing board..
Right, i installed the superdave 03 version and then opened up the registry to make sure the settings matched the ones above. I had to kill cprog and voicecmd to start it without the memory error.
I have tested it now and although it is loading up ok, my headset connection is just not working properly. Its paired ok but nothing is getting routed through. However, my gps bluetooth device paired okay and is working fine with iGO 2006 after doing a detection. Damn shame about this headset! I am using a parrott ck3000.
redo..
Re-installed everything again and now I got a working version, some things to note though on my wizard..
1) I must overclock to 260mhz(battery status method) before I get skip free music.
2) Leaskovski, I had the same problem too in the beginning, where there is no audio getting through. Did you go to Bluetooth Manager and check the status of your headset? i went to mine(ItechS35) and I can see that the Wizard is sending data through successfully but there is no sound coming out of the headset. I solved this(that time, I don't know why it worked but it did) by going to Bluetooth services and removing the Check box for audio gateway enabled, and then music started coming through. I know, does not sound logical but it worked... that time..
Now hoping to find a way to redirect audio back to speakers when bluetooth is not used..
not tonight though.. its 10.46 pm now where I am...
This doesn't look promising for how i though the BT audio might work with this stack. I was hoping for something like the following...
"A good example of this is MS Voise command running on the MS BT stack. The two devices are paired and connected, however there is currently no streaming. You then receive the text message and MS Voice command reads the message back to you. Just before the message is read, the connection between the devices is made live, and thus the message gets read over the BT headset."
I was hoping that this was going to work for all applications like media player and iGO. I can reproduce what it is doing at the moment using the BTAudio programme that is available on these boards. I just wanted to get around this 'constant' streaming of silent noise.
Damn shame.
Okay for anyone wanting to play with this, here is how i installed and got it running...
1) Download from this thread post http://forum.xda-developers.com/showpost.php?p=1072773&postcount=72 the file BBS_HERMES_03.zip.
2) Install onto your wizard and soft reset when asked. Upon the reset, the device will moan at you about not having enought memory to load the drivers. Click ok to close this.
3) Load up your registry editor (i use FDCSoft Task Manager) and make the following mods as stated in the first post...
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BtConfig\SerialTransport]
BaudRate=115200 (Won't start at higher rate.)
Port=1 (This is the most important thing!)
If you only want audio routed to headset when there is audio to route then make this reg edit...
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\Plugins\handsfree]
Audiohandling=21
4) Do not do a soft reset yet.
5) Now fire up your Task Manager (i use FDCSoft Task Manager) and kill any memory hungry tasks. The ones i kill which then allow me to start the stack is voicecmd.exe and cprog.exe.
6) Now click on the BT icon in the system tray and turn BT on.
Obviously there must be some memory leaks some where in the wizard because a couple of people have said that later in the day, if you try to turn BT on again it wont start due to memory requirements. Anyway, the best thing i can think of is to leave BT on after you have turned it on.
Currently, the blue led will not flash when BT is one. Try not to use the Normal Comms Manager to turn BT one as well as i think this trys to turn the MS stack on which won't work (probably due to memory requirements! )
new2city said:
I solved this(that time, I don't know why it worked but it did) by going to Bluetooth services and removing the Check box for audio gateway enabled, and then music started coming through. I know, does not sound logical but it worked... that time..
Click to expand...
Click to collapse
I didnt get this to work in the end by the way.
I tried your idea to leave BT all the while but some problems pop up..
1) If turn off the headset without disconnecting it(BT still left on and the phone goes on standby, sometimes it won't come back.. a poke at the reset button is the only way..
2) I left BT on and disconnected the headset properly. Great BT is still on... BUT after a few hours, I can still connect the headset, but audio is not going there anymore... ??? but goes into internal speakers?
new2city said:
I tried your idea to leave BT all the while but some problems pop up..
1) If turn off the headset without disconnecting it(BT still left on and the phone goes on standby, sometimes it won't come back.. a poke at the reset button is the only way..
2) I left BT on and disconnected the headset properly. Great BT is still on... BUT after a few hours, I can still connect the headset, but audio is not going there anymore... ??? but goes into internal speakers?
Click to expand...
Click to collapse
Hmm, i dont have those issues. I am using it with my carkit, so when i turn the engine off and remove the keys, the kit turns off. I haven't had to reset the device apart from when i have turned BT off and then tried to turn it back on again at a later stage (then giving me the memory issue).