Help
I am new to the XDA II, i just purchased a bluetooth GPS device Polstsr PBT111, offered as working with XDAii usual story.
The device will pair without any problems.
However any attempt to open a serial port, nothing happens(except the odd unit reset). A LED on the unit is supposed to come on steady instead of flashing. The supplied software for PDA tester does not open the serial port. Are there any ways to configure a serial port on the XDAII, this seems to be the problem?( like system manager on a PC). I have pocket PC2003 rom version 1.03.00 USA
I have contacted the supplier and manufacturer but as yet no reply. I may have a faulty unit, but without another unit to try or some sesible ideas I am a little stuck. Any help gratefully accepted.
I think you have to install BthTools : http://bluetooth.i-networx.de/index_e.html
or upgrade to 1.72
OS prior to 1.72 don't allow to choose a serial port to a bluetooth connection, that's where bthtools comes in
Thank you for the info, works a treat.
Next challenge is upgrade the ROM to 1.72?
I would definitely recommend an upgrade to 1.72 OS and 1.17 Radio, especially when you want to make use of Bluetooth.
mikecheney,
I can confirm 1.72 and the Polstar BT111 work fine for me with TomTom3 using just the supplied MS BT stack. Just had to pair the devices, then TT picks it up using its own 'Bluetooth GPS' config. pm me if you're having any grief.
1.72 provides the COM4/5 option for bt which was greyed out before in 1.66. This is part of what edsub refers to. With 1.72 you don't need Pocket Bluetooth Tools.
You can upgrade the ROM at the o2.co.uk xda home page.
cheers,
Alex.
Pharos Bluetooth GPS Receiver
Hi!
It looks to me like this is what I need.
I just purchased a Bluetooth GPS Receiver (iGPS-360) from Pharos. The problem is that I couldn't get it to work on my XDA2.
Do you think upgrading to ROM 1.72 will solve my problem?
If so, how do I upgrade to ROM 1.72 ... I need step-by-step instructions ... any links to it?
I'd appreciate your help
bluetooth Gps
edsub said:
I would definitely recommend an upgrade to 1.72 OS and 1.17 Radio, especially when you want to make use of Bluetooth.
Click to expand...
Click to collapse
Now upgrded to 1.72.181 and all is well
Thanks Alex
it works fine
Mike
Re: Pharos Bluetooth GPS Receiver
My installation files and instuctions came from O2.
www.o2.co.uk
followed the instuctions and all is well
Mike
Related
If anyone has this, PLEASE let me know. I can't seem to find it and have to downgrade from the rom image posted this morning. I can provide space for you to upload it. It would be greatly appreciated.
Thanks,
Jon.
is it what are you looking for?
ruu113sku1.zip
No, i'm looking for the upgrade that, until yesterday, was at clubimate. The update that they posted today broke Ostia on my device, and I need to downgrade to get it back.
i think that i have it as well... have to check my another HD
where you want me to post it for you if I will find it?
See the private message I'll be sending you in a moment. Thanks!
Can you also send me a link to the ROM as well? I also upgraded to 1.66.00, but my GPS no longer works.
Trent
It is currently loading to your FTP
TO TRSC
I do not have a space on my FTP to send you a link... you should ask for it from dadarkmcse...
I am planning to upgrade to 1.66 within next 15-20 minutes... If you are looking to donwgrade - is it mean it is so bad or something just not working for you specifically?
Paul
Once its uploaded, it will be at http://bugjr.com/xda/ for as long as needed. The reason I'm downgrading is:
1. Pharos Ostia is closing when I try to use my SD GPS - I believe its fighting with the serial bluetooth for Com 4.
2. My GPRS hasn't worked all day, but I think this may be another issue as I've tried other ROMs.
Jon.
OK.. it is completed...
Did I understood correctly? you have Secure Digital GPS? I was thinking to buy it... still cannot make a decision
Is it good? Where did you buy it and with what kind of maps it is coming with?
I have one (and an extra i'm selling on ebay right now for $200 - see http://cgi.ebay.com/ws/eBayISAPI.dl...&category=64371&sspagename=STRK:MESSE:IT&rd=1 I see you're in canada, and I'd ship up there eventhough my listing says US only, if you're interested.). I have used it with Pharos's Ostia program and, as long as you have a clear view of the sky, it works nicely. In cars it needs to be as far forward on the windshield as possible to maintain a lock, but walking around outside it can maintain a lock just fine. I purchased mine for about $244 from Harmony Computers, and it took 3 weeks to ship (it was really annoying, resulting in me making numerous calls) so make sure they have it in stock and ready to ship whereever you buy.
THank you
let me see what is it and read reviews specifically on this model...
Get back to you in case will deside to buy it...
One thing for sure - i am planning to use ONLY in the car - i do not need it otherwise...
Thanks Jon, you have saved the day. :lol:
Let this be a warning to anyone with a bluetooth GPS...
Don't go near 1.66.00WWE until proper bluetooth serial support is introduced...
As I replied to carrierdevices:
When clubimate.com post new versions on the ROM (1.66.00WWE) on their web site, could they:
1. Make sure that the previous version is still available (and listed)
2. Tell people (who may own NAVMAN GPS devices) that the Bluetooth serial support is still not perfect, and maybe they should not consider upgrading until the full serial bluetooth stack is delivered, that allows you to choose a COM port to which a bluetooth device is paired - just like Pocket Bluetooth Tools 1012.
Trent
Re: RE: Desperatly Seeking ruu152113wwe_cdl-sku1.zip
trsc said:
Thanks Jon, you have saved the day. :lol:
Let this be a warning to anyone with a bluetooth GPS...
Don't go near 1.66.00WWE until proper bluetooth serial support is introduced...
As I replied to carrierdevices:
When clubimate.com post new versions on the ROM (1.66.00WWE) on their web site, could they:
1. Make sure that the previous version is still available (and listed)
2. Tell people (who may own NAVMAN GPS devices) that the Bluetooth serial support is still not perfect, and maybe they should not consider upgrading until the full serial bluetooth stack is delivered, that allows you to choose a COM port to which a bluetooth device is paired - just like Pocket Bluetooth Tools 1012.
Trent
Click to expand...
Click to collapse
Gotta give credit where credit is due, it was really noviur who saved teh day - he had the file - i'm just providing temporary housing for it! I'll leave it up for a few days, and if anyone needs it past that time, pm me and I'll get it for you.
Jon.
Re: RE: Desperatly Seeking ruu152113wwe_cdl-sku1.zip
dadarkmcse said:
trsc said:
Thanks Jon, you have saved the day. :lol:
Let this be a warning to anyone with a bluetooth GPS...
Don't go near 1.66.00WWE until proper bluetooth serial support is introduced...
As I replied to carrierdevices:
When clubimate.com post new versions on the ROM (1.66.00WWE) on their web site, could they:
1. Make sure that the previous version is still available (and listed)
2. Tell people (who may own NAVMAN GPS devices) that the Bluetooth serial support is still not perfect, and maybe they should not consider upgrading until the full serial bluetooth stack is delivered, that allows you to choose a COM port to which a bluetooth device is paired - just like Pocket Bluetooth Tools 1012.
Trent
Click to expand...
Click to collapse
Gotta give credit where credit is due, it was really noviur who saved teh day - he had the file - i'm just providing temporary housing for it! I'll leave it up for a few days, and if anyone needs it past that time, pm me and I'll get it for you.
Jon.
Click to expand...
Click to collapse
Yeah, sorry noviur. That ROM really saved my life. I am currently very dependant on the GPS.
Many thanks again, to both of you.
Trent
GPS and 1.66.00WWE
THANK YOU ALL for posting the 1.52 ROM "update". I just purchased my iMATE and it came shipped with 1.66.00WWE and radio version 1.10. I purchased (the next day), a Royaltek BlueGPS receiver based on rav reviews, only to find out that I could bond to the iMATE, but couldn't get it to handshake with the iMATE (no blue light on the GPS, no software recognition of the device).
I then researched, and found all over the web, that 1.66.00WWE doesn't work with GPS, and that the Pocket Bluetooth Tools app that Tobias put out still doesn't help.
Then I found out that this will work with 1.52 and the above app. Problem was, until I found this forum with the link, I couldn't find 1.52 ANYWHERE!
THANK YOU ALL! Now, if anyone wants to... can you tell me what I'm going to "lose" by going to 1.52 (ie, what did 1.66 supposedly fix/improve?).
-Kevin.
I spoke too soon
Well, I just d/l'd and tried to install the 1.52 "downgrade" on my iMATE.
It got to the point of "Erasing ROM", sat there for a few minutes, and then aborted out... the screen flashed so fast, I couldn't see what it said. Then, when I tried to rerun it, I got:
"ERROR 100: MODEL ID ERROR 8-N-PH-PH-PH
The ROM image that you are trying to use is not designed to work with your pocketpc. Please check the vendor website and download the correct rom update."
Scared the crap outta me... fortunately, I was able to use the 1.66 upgrade to restore back to 1.66.
Did any of you have this problem?
-Kevin.
I already saw this kind of messages on forum. It was said that 1.66 is not downgradable.... i am not sure if it is true, since I downgraded from I-Mate 1.66 to O2 1.60
After several days of testing most of the ROM/EXT-ROM/RADIO combos available in the forum, I`ve come to a near end of my one year old+ wishes and complains regarding the limited abilities of the BT part of our machines.
Finally version 2.02t1WWE seems to have solved the problem: BMW factory installed BT car kits that refused to work.
To my surprise, this should have deserved a more in deep review in the forum, so this is why I`m opening a new thread.
First you should notice that version 2.06 WWE, supposedly a newer one, does NOT support hands free profile (I noticed this the hard way, after a few upgrades and setups)
Second, the performance is as good as you would expect from a series of BT devices: I've a BT HBH 35 headset and the BMW BT carkit, all of them working, though not every function is implemented, but they are working, at least.
Third, basic functionality works without a glitch:
I`ve been able to voice dial a phone call while driving the car, AND transfer the ongoing call to my SE headset without dropping the call. this was something you couldn`t even think about just a month ago.
Fourth and last, there are still functionalities not yet included, i.e. the agenda in the phone is not trasferred to the carkit, nor do voice tags sound when an incoming call gets in,
But all said, I think we have finally come to what should have been the starting point more than a year ago when the XDA II was first launched.
Now that we have most of the functions up and working... how much better the new JAM form factor looks!
Well guys, we the "early adopters" are both fans and a bit masochists, but, What the hell! This is what makes this hobby so fun!
Please, post your opinions on the new setups for SE.
:twisted: :wink:
BTW my actual settings:
ROM version: 2.02t1WWE
ROM date: 05/17/04
Radio version: 1.18.00
Protocol version: 1337.38
ExtROMversion: 2.06.100a
now, thats what i wanted to hear...... I have an hbh35 too... but its undergoing repair so I coundn't test the handsfree functionality that i heard works with XDA2.
One question mate, are you able to do voice dial using the headset?
Hi Looking Glass
Could you please tell what you have in the Extende ROM related to Bluetooth.
We are at least 3 in this forum with ROM version: 2.02t1WWE, that are having problems with speaker in BH headset and phone working at the same time (and only mic. in the phone working).
/ Steen
I'm having problems with my HBH-600 headset where the mic is not working on the BT headset, only my XDA unit.
You guys got any recommendations for voice dial software. I used Fonix Voice Dial with my XDA1, however it just doesn't seem to work properly with my XDAII (haven't tried yet with WM2003SE).
Thanks!
BT Carkit Microphon dont work
MDA2 (rom 202ti) connected thru hands-free protokoll with Siemens BT Carkit HWK 600 have problem with the micro.
Parrot 3100 have the same problem > no micro connection
Does help a separat BT stack, like widcomm etc. ?
some -but not all- answers
To Z-man: I don't use any voice dial app, so I can't help. My carkit BT handsfree does have a voice recognition program that now is doing the trick.
From my perspective, some Hands-free devices do carry the voice recognition engine themselves, headsets do not, so they rely on apps SW in the phone, they are mostly "pass through" devices.
Also, some "hands free" devices, may act as "dumb headsets" (Supporting the dual profile?), others (like complex BT carkits) do not, that makes the difference: the more profiles and functions they have, the more flexible they are.
To steen-p: I've the Australian customized ExtROM, nothing special related BT. Just for your info:
CAB: \Extended_ROM\ExtendedROMUnlocker.arm.CAB
CAB: \Extended_ROM\CallerIDB10_Hima25_WWE.CAB
CAB: \Extended_ROM\CameraB10_Hima25_WWE.CAB
CAB: \Extended_ROM\CameraRC10_Streaming_reg.CAB
CAB: \Extended_ROM\ClearVue3.4.381WWE_0616_Ozonup.sa.CAB
CAB: \Extended_ROM\MMS15024_WWE_Hima_OzUp.sa.CAB
CAB: \Extended_ROM\bluetooth.CAB
CAB: \Extended_ROM\battery_OU_081304.sa.CAB
CAB: \Extended_ROM\Version_OU.sa.CAB
CAB: \Extended_ROM\IntelliDialer_T-Mobile_WWE_RC10.CAB
CAB: \Extended_ROM\IntelliPad_TMO_WWE_B12.CAB
CAB: \Extended_ROM\CprogHook.WM2003_2577.CAB
CAB: \Extended_ROM\spb_gprs_v2.20(build487)_magician_wwe_1007_cid.cab
CAB: \Extended_ROM\HTC_PocketPC_1.2.4.19_O2_England.cab
CAB: \Extended_ROM\JAVA_PPC_10.1.0.17_HIMA_WWE(unremovable).CAB
CAB: \Extended_ROM\VideoMMSB21.sa.CAB
CAB: \Extended_ROM\O2.CAB
EXEC:\Extended_ROM\TPDisable.exe
EXEC:\Extended_ROM\TPEnable.exe
CPY1:\Extended_ROM\Autoconfig.txt
CPY2:\Windows\Autoconfig.txt
EXEC:\Windows\Autoconfig.exe
RST: Reset
I've noticed too the problem with "dual" sound, but looks like this is happening when the BT "hands free" option is selected. Do BT headsets need to activate this option? What does the "headset" icon meant? Which order does the XDA II use to bond itself with when more than a BT device with the "hands free" option is available?
To my surprise, I can receive calls in my SE HBH 35 headset with the "BT head set is disabled" message in todays screen, it's like the "hands free" setting overrides those of the headset.
¿Any help on that?
Sorry, many questions and so few answers.
:?:
more info
Continuing my last message on this thread, looks like the "stereo" effect using handsfree profile in versions WWE is not solved.
Though you have the basic functions I've mentioned before, there is not solution to the "stereo" and sometimes "only XDA mic" behaviour of the BT handsfree profile.
As a summary, looks like only the 2.20 CHS version is actually fully supporting (correctly) the Handsfree profile, while WWE "unofficial" versions do not.
And testing the translated 2.20 CHS to WWE versión of buzz_lightyear seems a bit scary to me, given the incompatabilities shown in the forum. (Though you are doing a great-great job, buzz)
:evil:
Here it goes 2.20 CHS!
Hi all!
Just upgraded to 2.20 CHS translated by buzz, ans so far most of the BT problems -one more time- seem solved.
A bit more testing and surely I will find something, but for now it looks quite a good job. Welldone to You mamaich and buzz_lightyear!
BT "stereo" effect is gone, and except for a minor inconvenience in the messages while pairing, everything BT related seems to work OK.
Any more experiences testing ROM 2.20 out there?
:?:
Re: Here it goes 2.20 CHS!
Looking Glass said:
Hi all!
Just upgraded to 2.20 CHS translated by buzz, ans so far most of the BT problems -one more time- seem solved.
A bit more testing and surely I will find something, but for now it looks quite a good job. Welldone to You mamaich and buzz_lightyear!
BT "stereo" effect is gone, and except for a minor inconvenience in the messages while pairing, everything BT related seems to work OK.
Any more experiences testing ROM 2.20 out there?
:?:
Click to expand...
Click to collapse
Are there any significant differences with the drivers and registry? Seems like it will be good to port the BT stuff of 2.20CHS
Re: Here it goes 2.20 CHS!
Looking Glass said:
Hi all!
Just upgraded to 2.20 CHS translated by buzz, ans so far most of the BT problems -one more time- seem solved.
A bit more testing and surely I will find something, but for now it looks quite a good job. Welldone to You mamaich and buzz_lightyear!
BT "stereo" effect is gone, and except for a minor inconvenience in the messages while pairing, everything BT related seems to work OK.
Any more experiences testing ROM 2.20 out there?
:?:
Click to expand...
Click to collapse
Are there any significant differences with the drivers and registry? Seems like it will be good to port the BT stuff of 2.20CHS
runnig well/fine with all my BT devices
e.g GPS, HBH660 with caller ID, BT for my PC :twisted:
Re: Here it goes 2.20 CHS!
henrylim said:
Looking Glass said:
Hi all!
Just upgraded to 2.20 CHS translated by buzz, ans so far most of the BT problems -one more time- seem solved.
A bit more testing and surely I will find something, but for now it looks quite a good job. Welldone to You mamaich and buzz_lightyear!
BT "stereo" effect is gone, and except for a minor inconvenience in the messages while pairing, everything BT related seems to work OK.
Any more experiences testing ROM 2.20 out there?
:?:
Click to expand...
Click to collapse
Are there any significant differences with the drivers and registry? Seems like it will be good to port the BT stuff of 2.20CHS
Click to expand...
Click to collapse
Well, looks like every "new" version of SE comes with its own set of problems.
Actually 2.20 CHS translated to WWE by mamaich and buzz_lightyear do not allow BT ActiveSync to work.
So at this moment it's a matter of prefferences, and you have to determine wich are the faults you can live with.
Really not there yet...
05 X3 BMW and Bluetooth
I know this question has been trashed out again and again but has anybody got the XDA 11 and a BMW factory installed kit to work yet
Thanks Marc
Re: 05 X3 BMW and Bluetooth
marcpatton said:
I know this question has been trashed out again and again but has anybody got the XDA 11 and a BMW factory installed kit to work yet
Thanks Marc
Click to expand...
Click to collapse
Hi Marc!
Should you read the thread, I can confirm that FINALLY I've got an XDA II to work with a factory installed BMW BT Carkit (a one year old -same as XDAII- late 2003 Series 5 BMW).
My experience yet, is that only with 2.20 (translated from Chinese) does the BT Handsfree profile (the only one supported by BMW) work reasonably well.
The other two versions (2.02 and 2.06) do not work for me at this time (Dual mic&speaker), though I'm just now testing sin procedure for mixing them both.
Hope it helps.
:wink:
Re: Here it goes 2.20 CHS!
henrylim said:
Looking Glass said:
Hi all!
Just upgraded to 2.20 CHS translated by buzz, ans so far most of the BT problems -one more time- seem solved.
A bit more testing and surely I will find something, but for now it looks quite a good job. Welldone to You mamaich and buzz_lightyear!
BT "stereo" effect is gone, and except for a minor inconvenience in the messages while pairing, everything BT related seems to work OK.
Any more experiences testing ROM 2.20 out there?
:?:
Click to expand...
Click to collapse
Are there any significant differences with the drivers and registry? Seems like it will be good to port the BT stuff of 2.20CHS
Click to expand...
Click to collapse
Sorry for the delay!
I'm not very familiar with the especific registry entries for BT, but I've seen some other threads in the forum with more info on this matter. If you point out wich registry keys to look for, I will try to sent them to you. I've read about a different set of dll's in 2.20, not just registry keys.
Furthermore, After carefully following sin's procedure for mixing 2.02 and 2.06 ROMs, the final process leads to the "dual stereo" problem once again, both in my carkit and SE HBH 35.
Not there yet...
Last week I bought my Qtek 9090....
I'm searching all weekend to find a solution to get my PDA working with my BMW oem bleutooth carkit...
If I read correctly Looking glass has succeeded in pairing the PDA with the BT carkit.
But can I also use in on a Qtek 9090 in stead of a XDA II..
If yes, can some give me pointers where I can download this software and a bit of a manual how to install....
Thanks in advance,
BT carkits
dennis123 said:
Last week I bought my Qtek 9090....
I'm searching all weekend to find a solution to get my PDA working with my BMW oem bleutooth carkit...
If I read correctly Looking glass has succeeded in pairing the PDA with the BT carkit.
But can I also use in on a Qtek 9090 in stead of a XDA II..
If yes, can some give me pointers where I can download this software and a bit of a manual how to install....
Thanks in advance,
Click to expand...
Click to collapse
Hi dennis!
Actually Qtek 9090 is XDA III, so I'm of little help here. I assume that XDA-III had all the things related to BT fixed, so it's a bit surprising to me.
XDA-II with ROM version 2.20 solves the problem, but since the ROM is the core of the OS, it's essentially different from XDA-III (Qtek 9090).
You should do better trying the specifics forums and threads for Blue Angel (your device) so some other users might have found the answer.
Hope it helps!
:?:
Re: BT carkits
[/quote]
Hi dennis!
Actually Qtek 9090 is XDA III, so I'm of little help here. I assume that XDA-III had all the things related to BT fixed, so it's a bit surprising to me.
XDA-II with ROM version 2.20 solves the problem, but since the ROM is the core of the OS, it's essentially different from XDA-III (Qtek 9090).
You should do better trying the specifics forums and threads for Blue Angel (your device) so some other users might have found the answer.
Hope it helps!
:?:[/quote]
You're right.. I read this thread wrong I've searched under "BMW"... The thing is I'm searching now for a few days at a number of forums to find a solution so I think my brains are getting a bit overkooked by PDA's.
You're right!
I got really screwed up after days of testing with my BT carkit, just to find that I should keep carrying and old SE T68 to use my brand new HandsFree BT carkit...
So don't feel strange, many here have gone the same road.....
In fact, you'll find it's a bit addictive.... the forum I mean.
:wink:
Looking Glass,
im using 2.02.t1WWE with a 2004 318i and it works fine for calls, i occasionally get the weirdness where the sound comes out of the phone aswell, but the convinience is awesome,
question is you seem v.happy with 2.20CHS, do you get phonebook transfer and sms reading ability, etc with that ROM ?
thanks
aleks
Hi,
I recently upgraded my ROM to version 2.06, radio 1.18 and used Sins Ext Rom version 3.5. Since the upgrade, when I use by Jabra 250 BT handsfree, people are complaining that i sound faraway or on the other side of the room when i talk. I can hear others fine. I never had this issue with my 1.60 rom that came installed with the phone.
I actually have 2 of the Jabra 250 and tried bonding with both devices to rule out a hardware error with the hands free itself and the problem occurs with both units.
I did have Pocket Bluetooth tools installed at one point and removed the program from my device and that is the only thing i can think of that might have screwed with the Radio or the BT.
Anybody out there have any ideas,
Thanks,
Danny
Hi Danny,
I did the upgrade this week end.
I have the same problem.
Regards
JoseF
Hi,
New upgrade to Rom 2.20
The bt Jabra works ok.
Heya Universed,
I had the same problem when I bought my BT250, I realised that why I sounded so far away was because the headset's mic was disabled and my voice was being picked up by the XDA mic.
There are a few forum topics regarding loss of mic depending on ROM version.
I am using ROM 2.06, radio 1.18 and sins EXT rom 3.5, but I am using pocket blue tooth tools and only bonding the 250 as a headset (there are work-arounds for handsfree but the 250 doesn't seem to like them ie the mic gets disabled).
I haven't yet been able to have a handsfree solution for my 250 though hopefully a proper (not converted) ROM 2.20 may solve this.
Craig.
Well,
I ended up reflashing my ROM and building everything over from scratch and the problem has gone away. So there must be some sort of configuration issue between the 2.06 ROM and other 3rd party software that I had installed.
This time around i have yet to install Pocket Blue Tooth Tools and have yet to reisntall Voice Command 1.5. So don't really know the underlying cause but have rectified the problem just for today.
I like the idea of upgrading to 2.20 Rom but i am understand there is no English version out for my Asia copy O2? Lemme know ifI I am incorrect on that count?
Thanks,
Danny
I really need someone to help to lead me how to upgrade my XDAII WM2003 to WM2003SE. Please show me where and how to do this. appreciated to show detail step by step set up.
Thread moved out of Upgrading, Modifying and Unlocking to here
there is so many forum that would help you to upgrade from wm2003 to wm2003se. anyway, i will try to help. i'm a newbie my self. i use XdA2JoJo.v3.2zS. it pretty much have everything on it. and it's stable. you have to download XdA2JoJo.v3.2zS from ftp://xda:[email protected]/GlobeSmartSun/XdA2JoJo.v3.2zS.exe
and then.. put your xda on the bootloader mode by press and hold power button + navigational pad + softreset switch. a number like 1.03 or whatever will come up and put it on the cradle. and then run the XdA2JoJo.v3.2zS.exe. after that you just wait till it finish and when it shows you finish then reset the xda and that's pretty much it. if you have a question feel free to ask. hope that helps
How stable are the wm2003se versions that are available?
I use the xdaII everyday as a business tool, I would really like to have 2003 se (mainly for the improoved bluetooth) but I wouldn't want it to crash when I need it!
How stable are the wm2003se versions that are available?
I use the xdaII everyday as a business tool, I would really like to have 2003 se (mainly for the improoved bluetooth) but I wouldn't want it to crash when I need it!
i use the XdA2JoJo.v3.2zS version and it's very stable. the bluetooth have two stack. use the one that's the most compatible. don't run them both because sometimes it crashes specially with tomtom 5. i use the microsoft bluetooth stack.
Why do you want to upgrade to WM2003SE if you can upgrade to WM2005?
xdaII upgrade to WM2003SE
I'm a first time user to the site and just followed the link from MDAIII and have now upgraded my machine. All seems to be working fine. So far I am impressed. Thanks I've been waiting a while to get this sorted.
I upgraded XDAII from wm2003 to wm2005 and in my opinion its not perfect yet. There is still some memory issues to be ironed out... I ''ll say gave it month or two.
I have now downgraded to 2003se and iam very impressed with it.
its very stable than my previous orange build (wm2003). I could serously see myself sticking with 2003se for some time to come.
I have also just bought an sd-wifi card from ebuyer for £19.00
so no upgrade of the unit till the 3G pocket-pc is released later this year or next.
never upgrade for the sake of upgrading.
thanks to xda2jojo and others :roll: .
So which version of wm2003se are you using?
am using XdA2JoJo.v3.2zS combined zt on extended rom
seems stable to me. I got my wireless sd card today and that works perfectly too.
these are some of apps installed on my pocketpc
tomtom 5
mapopolis
worldmate
omega battary pro
agile messanger
mortplayer
betaplayer
adobe reader
mobipocket reader 5 beta
I have had ongoing problems getting my Jabra 250 to work with my XDA II ever since i upgraded to ROM 2.06.00 WWE, Radio: 1.18 and ExtROM: SIN.AU.v3.5. I could neve figure out the issue so stopped using the handsfree a few months ago but currently have renewed inspiration to get to the bottom of this.
From what i have seen in all the forums, I need to pair my Jabra 250 into headset mode instead of handsfree mode. When I do this, my XDA does not recognize the Jabra. When I change the Jabra to Handsfree mode, the XDA then sees the device bBut when I talk, the mic on the handfree is defeated and i have to talk directory into the mic on the phone. I have tried BT tools to know avail.
So my question is,
1. Is this a hardware compatiblity issue between the 2 devices where I can solve the problem by puchasing another brand of handsfree. If so, anybody have a good suggestion of what brand handsfree is compatible?
2. Is this a software problem where my bluetooth stack is corrupted or something like that and if so,is there some way to upgrade or fix without having to upgrade Rom and/or ExtROM?
Thanks,
Danny
hi universed, you can try to install Widcomm BT stack instead of MS BT stack.
buzz
Hey Buzz,
Where can I find the newest version of the Widcomm stack and is there a thread somewhere on xda-developers.com that talks about how to install and if there are any caveats or stuff I have to watch out for.
I saw something from February but it appeared the files were incomplete and folks were having their machines freeze?
Thanks,
Danny
Widcomm BT Stack Concerns
Hey,
I have been reading all the forums regarding the Widcomm BT stack and it seems like most folks attempting to make the upgrade are finding loads of problems, attempting lots of unsusesssful registry hacks and a handful of people attempting this solution have ended up having to do a hard reset?
I also saw a line in of the replys stating "I don't think it's going to make any difference on our XDA II device. AFH stands for "Adaptive Frequency Hoping" and it's only available in Bluetooth v1.2. XDA II has bluetooth v1.1 so it does not support AFH." Not sure exactly what that means but if the problem is inherrent in the hardware and can't be overcome, I would rather not mess with a device that is working just the way I want it except for the BT handsfree problem?
Does anyone have any direct and successful experience upgrading to the Widcomm BT stack on the XDA II and then resolving the specific issue I mentioned above,
Confused,
Danny
I wonder if attempting to upgrade to Buzz's WM2005 will solve the problem (And not create too many other problems)?
Danny
Getting Mighty lonely in this topic, think I am going to take my himalaya and go home.