Related
http://forum.xda-developers.com/viewtopic.php?t=11729&highlight=widcomm
Since I didn't see in any thread about someone updating their PDA2k to the latest widcomm drivers... Just an FYI, I copied the files from the other thread onto my PDA2k. Seems to be working. Will test further to see if I'm still getting memory issues like before.
NOTE - I used Resco to copy the files over. There were several warnings that I was updating a file in ROM.. but I went ahead and did that anyway...figured I could hard reset the device if need be.
Still testing..but handsfree is a bit sporadic in terms of connecting.. still issues with the headset profile. Doesn't always connect. Turning on and off bluetooth seems to work better.. have not seen any driver memory issues(and that is turning on and off unit along wiht turning on and off wlan/bluetooth).
Quite a few times, I had to press the button on my HB-35 to connect the voice portion after it dialed. The PDA2k reports that it is connected to the HB-35, but doesn't seem to transfer the voice call over. After pressing the button on the HB-35, the voice transferred over... Will continute to play around with it...
Any update firbird and guest? What devices are you connecting to the PDA2K?
BT Headset, Model?
GPS, Model?
Car Kit, Model?
Keyboard, Model?
Wife, Model?
I want to control everything, yes, the dog included!
To clarify, I wanted to control the dog AND the wife, I didn't mean the wife was a dog!
Sorry.. been a bit busy lately... anyway.. as for an update.. I had more problems with the headset than with the previous 1.0 driver version... as for driver memory errors.. it seemed that I got them less frequent with the 1.5 driver.. but i still got it once in a while.. There's another thread in the forums here where I mentioned that it might not be entirely the driver but the way good old MS handles its memory allocation for drivers... the PDA2k isn't the only one with these issues.. the XDA IIs, the 6300 series.. even the older ipaqs.. the driver memory thing pops up all over the place where bluetooth is involved...
I had the xda II for 9 months and never saw the driver memory error msg, in fact it was perfect.
do it runs on pda2k ?¿?¿?¿
Thanks
Hi all, for the last few months I have tried various Universal ROMs and even various WM5 phones including HTC and HP iPAQ, there are some commond issues which I haven't been able to figure out a permanent solution (work arounds are available though not ideal), these are:
- SIP (System Input Panel), if you install any additional SIP like SPB fullscreen keyboard, Monster SIP etc, every time after you soft reset the device, unless you load them up straight away, you will not be able to load them up after a few minutes (don't know exactly how long) until next reset!! This is a great pain, I have found a SIP changer program which automatically load a SIP after soft reset, but I will really love a permanent solution.
- Bluetooth problem with Tomtom 6 (TT6). With lots of AKU versions of WM5 (apart from Helmi AKU 3.3 I tried so far, haven't tried it with Helmi AKU 3.5 though so I can't be sure with that version) every time I start up TT 6 it asks me to enter the passcode to pair my BT GPS receiver again even though I have done it 100 times already!! Again I have seen this issue on other WM5 devices in addition to Universal so I am wondering if any one has a solution.
Thanks!
kevin.jiang said:
- Bluetooth problem with Tomtom 6 (TT6). With lots of AKU versions of WM5 (apart from Helmi AKU 3.3 I tried so far, haven't tried it with Helmi AKU 3.5 though so I can't be sure with that version) every time I start up TT 6 it asks me to enter the passcode to pair my BT GPS receiver again even though I have done it 100 times already!! Again I have seen this issue on other WM5 devices in addition to Universal so I am wondering if any one has a solution.
Click to expand...
Click to collapse
I've never seen this problem on either my Universal, or my friend's Wizard (which I set up for them).
I don't know if this is the "standard" way, but basically, I pair the GPS device (a BT-77 in our cases), and then setup an outgoing COM port to it, and then simply tell TomTom to attach to that COM port. In fact, I have two BT-77s, one set to COM0 in the car, and a hand-held one on COM4, and I can switch to my heart's content, and have never been asked to re-pair.
Cheers,
Steve.
kevin.jiang said:
- SIP (System Input Panel), if you install any additional SIP like SPB fullscreen keyboard, Monster SIP etc, every time after you soft reset the device, unless you load them up straight away, you will not be able to load them up after a few minutes (don't know exactly how long) until next reset!! This is a great pain, I have found a SIP changer program which automatically load a SIP after soft reset, but I will really love a permanent solution.
Click to expand...
Click to collapse
I know many SIP can not be able load out. Did you solve this? or how to load them with permanent solution?
kevin.jiang said:
I have found a SIP changer program which automatically load a SIP after soft reset, but I will really love a permanent solution.
Click to expand...
Click to collapse
i've installed a hebrew sip but i dont have a problem loading it anytime i want.
although, sometimes i have a problem composing a new text message. the device gets stuck sometimes if the keyboard it not opened when i click "new".
happends only with helmi's 3.5 and with the hebrew keyboard. doesn't happen with default SIPs.
whats te program you found to load the all the SIPs?
is it "SIPz"? (from the same maker of PQz).
I have the same problem with blue thooth and CoPilot I use. The software is iGo. I tried several roms, but after I switch off the GPS and switch it on, it always wants to pair with Uni again.
StevePritchard said:
I've never seen this problem on either my Universal, or my friend's Wizard (which I set up for them).
I don't know if this is the "standard" way, but basically, I pair the GPS device (a BT-77 in our cases), and then setup an outgoing COM port to it, and then simply tell TomTom to attach to that COM port. In fact, I have two BT-77s, one set to COM0 in the car, and a hand-held one on COM4, and I can switch to my heart's content, and have never been asked to re-pair.
Cheers,
Steve.
Click to expand...
Click to collapse
Thanks for the suggestion Steve, I have indeed paired the BT GPS receiver, created the outgoing port as COM4 (actually I also tried other available ones) and point TT6 to it. I have been using this BT GPS receiver for over 2 years with various devices including my good old HP iPAQ H4150. This problem didn't happen with my Universal's original Orange SPV M5000 ROM and it doesn't happen with Helmi's AKU 3.3/3.5 ROM either which is the main reason why I am using AKU 3.3 now.
I have this problem on JWright's i-mate AKU 3.2 ROM, my wife's HP iPAQ rw6828 (WM5 AKU 2.3), my friend's T-Mobile MDA Vario II (HTC Hermes, WM5 AKU 2.3).
vuquan said:
I know many SIP can not be able load out. Did you solve this? or how to load them with permanent solution?
Click to expand...
Click to collapse
No good solution and I am wondering if anybody else knows how to solve it. I have tried hacking the registry to make my additional SIP default and I ended up with my universal not being to boot until a hard reset. The work around is this SIPChange attached, basically you set which one you want as default, then every time you soft reset it loads that SIP automatically before it becomes impossible to load it.
kevin.jiang said:
Thanks for the suggestion Steve, I have indeed paired the BT GPS receiver, created the outgoing port as COM4 (actually I also tried other available ones) and point TT6 to it. I have been using this BT GPS receiver for over 2 years with various devices including my good old HP iPAQ H4150. This problem didn't happen with my Universal's original Orange SPV M5000 ROM and it doesn't happen with Helmi's AKU 3.3/3.5 ROM either which is the main reason why I am using AKU 3.3 now.
I have this problem on JWright's i-mate AKU 3.2 ROM, my wife's HP iPAQ rw6828 (WM5 AKU 2.3), my friend's T-Mobile MDA Vario II (HTC Hermes, WM5 AKU 2.3).
Click to expand...
Click to collapse
I've not had the problem with either of the O2 ROMs, and Ivan's AKU3.5 test ROM - I haven't tried any other ROMs. I unticked the "secure connection" - not sure if that's relevant or not.
I found that only COM0 and COM4 seemed to be available for outgoing ports.
Before you go into TT6 - is the GPS device in the device list, along with the outgoing port set up correctly? Do you switch BlueTooth on and off? I have it on all the time - I'm just trying to think of things that might be different in our configs.
Cheers,
Steve.
I have both TT6 and iGO 2006 on my XDA Exec. The TT6 (and TT5 before that) always worked well with the BT-77 by simply pairing the GPS to the XDA EXEC on a COM port and selecting that COM port in TT6.
With iGO 2006, on the same XDA EXEC, it will ask to pair the BT-77 every time I launch iGO 2006. The only solution I could find was to use Franson's GPSGate to create Virtual COM ports for the BT-77 and to select this virtual COM port in iGO 2006.
StevePritchard said:
I've not had the problem with either of the O2 ROMs, and Ivan's AKU3.5 test ROM - I haven't tried any other ROMs. I unticked the "secure connection" - not sure if that's relevant or not.
I found that only COM0 and COM4 seemed to be available for outgoing ports.
Before you go into TT6 - is the GPS device in the device list, along with the outgoing port set up correctly? Do you switch BlueTooth on and off? I have it on all the time - I'm just trying to think of things that might be different in our configs.
Steve.
Click to expand...
Click to collapse
Thanks for the advise, I have tried unticking "secure connection" as well and it didn't help.
From what I am gathering in the information supplied it looks to be caused by a combination of the BT GPS receiver, the WM5 and the Sat Nav software.
I can't remember what make and model my BT GPS receiver is because I bought it over 2 years ago and back then I didn't care what model it is. Now that I can't tell it from looking at the outside of this thing.
This is a wierd problem as with different combination of the GPS reciver, WM5 and software it may or may not happen. What I was having that problem using Tomtom 6 I tried the GPSInfo shareware and it didn't ask me to pair every time. Very strange, anyway I am alright now with Helmi's AKU 3.3 using COM5 as the port with my good old BT GPS receiver and TT6.
kevin.jiang said:
No good solution and I am wondering if anybody else knows how to solve it. I have tried hacking the registry to make my additional SIP default and I ended up with my universal not being to boot until a hard reset. The work around is this SIPChange attached, basically you set which one you want as default, then every time you soft reset it loads that SIP automatically before it becomes impossible to load it.
Click to expand...
Click to collapse
Thank you so much! it work on my device.
ok, I have an o2 orbit running WM5, and everything has been going fine..not had any problems since I installed the SD card corruoption app, and I've not even changed the apps running on it for 2 months as everything was just perfect.
but, I've been reading that WM6 would be faster (I do get the occasional hang while the machine trid to catch up with what I'm doing), so I am thinking about the upgrade.
however, a lot of the posts I've read seem to indicated that I need activesync 4.5. I've tried this at least 3 times in the past, but it refuses to work on my machine and each time I have to go back to 4.2. Bsically the application on my pc locks up, never connects to my device and I have to end the application.
so, do I really need 4.5 to upgrade to WM6...and then again..do I really need WM6...is the improvment that much better?
yes, you need it
ok thanks...I guess no upgrade to WM6 then. AS4.5 just refuses to run on my machine
You only need it to sync with your pc. I use 4.5 at home but don't have it at work so I use WM5storage to transfer files to and from my works pc
that's just it though, 4.5 wont sync with my device...it just hangs.
Ok so it seems to be a pretty universal feeling that the bt does not work well on the Hermes. I personally am having trouble with filesharing.
So i searched (forum and google) and found different threads for different bt stacks, but I want to know what is a solid, stable, well-working one I can put on my phone?
I was under the impression that the BT stacks were pretty well intertwined with the ROM making them all but impossible to mix and match. But then I haven't really tried myself, so don't let me rain on your parade.
If anyone would know the answer to this question, it would be Sleuth. He is best man for tweaking BT that I know of. BTW, I haven't had any trouble BT filesharing (assuming you mean objectpush?) with SuperD-Lite. What are you trying to share with?
larsuck said:
I was under the impression that the BT stacks were pretty well intertwined with the ROM making them all but impossible to mix and match. But then I haven't really tried myself, so don't let me rain on your parade.
If anyone would know the answer to this question, it would be Sleuth. He is best man for tweaking BT that I know of. BTW, I haven't had any trouble BT filesharing (assuming you mean objectpush?) with SuperD-Lite. What are you trying to share with?
Click to expand...
Click to collapse
Oh i see. Im not very knowledgeable about how bt is incorporated and all.
Well I've had trouble finding, linking to, and sending files to my bro's phone (it sometimes works, sometimes doesnt). First he had an LG CU500, now its a Blackberry 7130c. Same with each. I've tried the "file explorer to find file and select 'beam file'" method and Dr. Yar's bluetooth app. Working bt isnt life or death for me, but it was always handy to share a ringtone, etc.
I just tried again with the blackberry. I went in with file explorer, chose a small mp3 on my storage card to send, chose "beam file", waited till his device showed up, clicked on it, and then it said "failed". Is anyone else having similar issues?
EDIT: Ok so now i go and find my old Razr cuz i know bt works on there, and lo and behold it sent! I guess its sometin about the blackberry. Although im still interested in if htere are any ways to improve/upgrade bt.
There was development underway on the Widcomm Stack nearly a year ago... check out this from the wiki Hermes Widcomm Stack I think you will find your answer there.
...and yet I find this stack 10000% better than what was on my 6700.
Especailly with my Audi, the BT never turns off when the phone goes to sleep and all my contacts show up in the HID.
It has been perfect so far!
I had issues with Bluetooth when I was using the latest official WM5 release for my Cingular 8525. None of my Bluetooth headsets would stay connected or even paired. But since upgrading to the "official" AT&T WM6 ROM, Bluetooth works just fine!
I have had very little if any BT issues using vp3G's 3.0 ROM. Very happy but waiting for 4.0!
I'm on Schaps 3.54c and my 8525 has been perfect with my Parrot3300GPS in my car. The parrot picks up battery, signal, contacts, etc. No problems. I wish my Wizard behaved that well.
The device is Holux GPSlim 236. The phone is Hermes. The phone will pair without question on a 6.0 rom, does not matter who cooked it.
It will specifically not pair with 6.1 roms.
I can see the device when scanning for bluetooth devices, i can choose it, it asks me for passcode, but will not accept the "0000" as the passcode. (tried hardware and software keyboards). IF i type in a passcode OTHER than "0000", it appears to pair, i can see the spp slave service and select it, but once the gps software tries to talk with it, it asks to pair again.
Something is definitely different in the pairing process between 6.0 and 6.1.
Any suggestions are greatly appreciated.
Also see thread about it here from the Himelaya:
http://forum.xda-developers.com/showthread.php?t=378103
Thanks,
Rock
Did you select it as a serial port? You have to do this after you pair the device with the phone!
I am not familar with gps units, does it have a pairing mode like a headset? I know with my Plantronics headset, if I let my phone discover it without the headset being in pairing mode, the phone says it pairs with it, but it really doesn't, so I put it in pair mode then turn on bluetooth on my phone and pair up as normal(0000 passkey) and all works fine.
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Bluetooth Pairing with 6.1
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
I had issues with the same device on some roms. I eventually changed BT drivers from WM6 and all went back to normal.
On some WM6.1 roms things went OK though.
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
crusti said:
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
Click to expand...
Click to collapse
ummm no, dont move my thread thanks. you can start one over there if you would like.
crusti said:
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
Click to expand...
Click to collapse
You are not the only one
I reverted back to the 6.0 and it pairs without issue. I am thinking that alot of these cookers do not pay much attention to the development of bluetooth in some of their roms. Its not like I changed something on the GPS, so something must have happened with the software.... Still investigating. I hope it works on schaps new rom.
miffymiffy said:
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
Click to expand...
Click to collapse
this method paired my jabra automatically, it didnt even ask if i wanted to do it auto, i juck clicked "pair" and there it was.
When pairing the holux 236 on the other hand, it would ask for a passcode, then reject it if you put in the correct code of "0000". If you canceled it, it would appear in the connected devices list!!, but still ask to pair once the gps application tries to connect. VERY jacked up.
Hissing Syd said:
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
Click to expand...
Click to collapse
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
rock99rock said:
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
Click to expand...
Click to collapse
No, there was no mention of if it could be disabled.
Wam7 said:
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Click to expand...
Click to collapse
Wam, which rom are you using now that it works with? id like to download and try it. The 5 or so ive tried did not work.
I power cycle the device without any change in pairing succession.
Thanks!
BTW: Other users experiencing differences between 6.0 and 6.1
http://forum.xda-developers.com/showthread.php?t=391488
http://forum.xda-developers.com/showthread.php?p=2240665