Can anyone help me.. Just got hold of the O2 XDAIIs and I'm having problems connecting my Motorola bluetooth headset - there has been many posts about upgrading the Bluetooth driver (or getting the patch from O2's website) but I can't register the device as it says it will only accept devices from ASIA!
Can anyone send me the drivers or point me in the right direction please.
O2 will release an update for the IIs on 1st March which includes the bluetooth updates to Build 3500. I'm just gonna live without headset working until the official update turns up I think. Dont have time to use main rom from here, extented rom from there, radio rom from somewhere else etc!!
Shame O2 are so s l o w when it comes to updates.
Nigel
Here is a very complete guide for everybody who is using blackberry but tired of the limited functionality and want to switch to pocket pc using blackberry connect. I have IMate PDA2K, also named as Blue Angel, XDA IIs, MDAIII and some other names and I am trying any possible solution to have blackberry connect work on this device
1. At the current time, blackberry connect is officially offered in the following countries: A. UK by O2, supported device is XDA II/MDA II or the same device under other names, but essentially all are the same, manufactured by HTC, but the support and connectivity from O2 is ver poor. The blackberry version on this is 1.2, designed to work with pocket pc 2002. It's english version so the cab file should install on WWE version. B. Germany by T-Mobile, supports both MDAII and III. The software is blackberry connect version 2.0, designed to work with pocket PC 2003. The software is in Germany and the ROM update will not install on WWE version devise. C. Austrlia and Netherland also by T-Mobile under the same capacity.
2. There is no U.S. carrier right now who supports blackberry connect officially right now, either on the pocket PC or Palm platform. Might be available on Sony-Ericson 910, which is Sybiam based. Even if that is the case, it's of no value to pocket pc users.
3. There are examples of the O2 version BB connect working on MDA II here through T-Mobile. Go to www.xda-developers.com and looking for articles posted by cbrow51. He has detailed guide on how to make it work(Through BWC, not BES)
4. All installable .CAB and desktop BB can be found from the xda site.
5. I installed the german version of the BB connect .CAB file on my device as well as the desktop software(that can be installed in English version). The device talkes to the desktop PC and the BES side getts the correct PIN. I put my SIM card from my AT&T blackberry handheld on my new device. It's not working yet, I think I need to change the built in APN and IP address for connection from the BB connect software(which should be connecting to German) through someway to make it work.
Anybody interested in this, Let me know
Let's make it work!
Latest update on Blackberry Connect in the U.S.
Talked to AT&T support and the BES support from my company today. This is especially relevant to SX66/MDA III/XDA III/Blue Angel/QTeq 9090/IMate PDA2K, basically all the same device manufactured by HTC for different branding, which runs Pocket PC 2003. And it is related to BES.
1. The wireless carrier should have no problem with the connection. The only thing realte to the carrier side is your SIM, which doesn't really affect the connection as long as your BES side have your correct PIN. The carrier automatically recoganize your PIN when it's registrated in your BES. And it does not use IMEI at all.
2. The BES side should not have problem either since once you have your BB Client on your device talk to your desk top, the PIN should automatically recoganized by the BES
3. The trick is that all PINs on blackberry devices are hardcoded in the device, while through BB Client, it is generated from the software. The RIM server need to recoganize your PIN. I think the BB Connect i am using, which is the the .CAB extracted from the German MDA III(T-Mobile), has some utility to register the software generated PIN with RIM if you are on the T-Mobile German GPRS network, while other carriers don't have.
I will talk to RIM on Monday to see if they can register my PIN. I will keep you guys updated.
Any one interested in this topic, please let's form a ring
Re: Let's make it work!
rwu said:
Latest update on Blackberry Connect in the U.S.
Talked to AT&T support and the BES support from my company today. This is especially relevant to SX66/MDA III/XDA III/Blue Angel/QTeq 9090/IMate PDA2K, basically all the same device manufactured by HTC for different branding, which runs Pocket PC 2003. And it is related to BES.
1. The wireless carrier should have no problem with the connection. The only thing realte to the carrier side is your SIM, which doesn't really affect the connection as long as your BES side have your correct PIN. The carrier automatically recoganize your PIN when it's registrated in your BES. And it does not use IMEI at all.
2. The BES side should not have problem either since once you have your BB Client on your device talk to your desk top, the PIN should automatically recoganized by the BES
3. The trick is that all PINs on blackberry devices are hardcoded in the device, while through BB Client, it is generated from the software. The RIM server need to recoganize your PIN. I think the BB Connect i am using, which is the the .CAB extracted from the German MDA III(T-Mobile), has some utility to register the software generated PIN with RIM if you are on the T-Mobile German GPRS network, while other carriers don't have.
I will talk to RIM on Monday to see if they can register my PIN. I will keep you guys updated.
Any one interested in this topic, please let's form a ring
Click to expand...
Click to collapse
This is great news! I'm getting my SX66 on Tuesday and I was just going to hack at it till I could get the BB Connect to work.. I've been reading several posts about converting the German to English and people who have problems generating PINs that come up with a "0". The problem is all I can do is research at the moment and just think about how it should work. Do you have any tips for a newbee who will probably blowup the unit a few times??
Any help or guidance will be appreciated.
Very interested in this! I have successfully installed the BB Connect cab on my XDA2i and now just need to know if the pin issue can be sorted.
Do you think this is possible?
I believe the PIN issue can definitely be resolved as long as RIM is willing to take the software PIN, since they are doing so in German already. I am also attaching the BB Connect .CAB file extracted from the German T-Mobile ROM for MDA III. Just copy it to your device and click install it from there shouldn't cause any problem to your SX66
Also, here is the BB Desktop softie, this does have the English installation.
Hokay,
I've installed the BB COnnect on my XDAIIi and the desktop configuration sofware on my laptop, but the BB connect software says the PIN is 0 and the config software on the PC says that the PIN is "Not Configured".
How do you get it to generate a PIN in the 1st place?
squiggs1982 said:
Hokay,
I've installed the BB COnnect on my XDAIIi and the desktop configuration sofware on my laptop, but the BB connect software says the PIN is 0 and the config software on the PC says that the PIN is "Not Configured".
How do you get it to generate a PIN in the 1st place?
Click to expand...
Click to collapse
Do you have the latest radio on your IIi? I know on the MDA III the radio has to be upraged as well for the BB Connect software to read the IMEI and generate the soft PIN #.
Again this is only from what I can gather from forums that I have been reading. I will not be able to verify anything until next week when my SX66 comes in.
Hope this helps you.
As follows:
ROM Version 1.10.00 WWE
ROM Date 24/12/04
Radio Version 1.00.00
PRotocol VErsion 1337.39
ExtROM VErsion 1.10.124 WWE
squiggs1982 said:
As follows:
ROM Version 1.10.00 WWE
ROM Date 24/12/04
Radio Version 1.00.00
PRotocol VErsion 1337.39
ExtROM VErsion 1.10.124 WWE
Click to expand...
Click to collapse
Have you run any firmware updates on your unit?
I have read on this forum that the Radio needs to be upgraded for the BB Connect to read the IMEI properly in order to generate a PIN#. Most of the reasearch I have been doing is on the Blue Angel. But I do know that there is a higher rev of the Radio than 1.00.00.
Hope this helps.
squiggs1982 said:
As follows:
ROM Version 1.10.00 WWE
ROM Date 24/12/04
Radio Version 1.00.00
PRotocol VErsion 1337.39
ExtROM VErsion 1.10.124 WWE
Click to expand...
Click to collapse
Here is a link with a doc on how to get started with the BB Connect client.
http://forum.xda-developers.com/viewtopic.php?t=12589&highlight=blackberry+pin+radio
But again, I think the Radio has to be upgraded first.
I'm not sure if you have done so or not but there is one section on Page 15 of the PDF file that talks about creating a pin.
Tap Start > Settings.
Tap the System tab.
Tap the BlackBerry icon.
On the BlackBerry Introductory screen, tap next.
Read the End User License Agreement carefully, and scroll to the very bottom.
To accept the terms of the End User License Agreement, tap Accept. Your PIN is created and the
service is started.
Good luck.
Hmm...
Looks like it might be the end of the road then. As far as I can tell, there is no newer radio version ...
So at risk of sounding silly.
Has anyone managed to succesfully configure a BlueAngel with Blackberry and if so, what levels of ROM were they using, what version of the client and what carriers as I would also like to be able to set this up.
Thanks
What is the BB Connect version u r using? I had the same problem with the 1.2 version stripped from O2's ROM. But the 2.0 version generated PIN with no problem.
Hi there,
Using version 1.2. Where would I come accross v2? I'm assuming the one you posted above is in German? Sadly, I don't speak any!
version 2 generates a pin fine - but the only one i've been able to get was using the german client and although this sounds picky, i'd quite like to use a client that I can understand the settings properly (to any german readers, please dont take any offence from what i've written, its my own fault I didnt study german more at school!!)
also, the german client uses the t-mobile access point settings. i'm on o2 uk so how do i go about changing the ap's over?
Ta
Actually, for me, the GErman client still doesn't generatethe PIN correctly? :?
Contacted RIM a couple of time and seems like the German version of BB Connect from T-Mobile is not working for AT&T, at least. The problem is that it automatically look for the german T-Mobile net work to connect to the blackberry APN and IP. It is possible to change that from the CAB file though so it looks for defferent carrier's network. Bottom line, the data transfer is through the SIM card, which is carrier dependent. That is why on your blackberry device you will see the carrier's screen when you power it on. The BB devices' PIN are pre-assigned to carriers. It won't work if you shift carrier. Now, come back to our problem, we need somebody who knows how to cook the CAB file. Who can help here?
squiggs1982 said:
Hokay,
I've installed the BB COnnect on my XDAIIi and the desktop configuration sofware on my laptop, but the BB connect software says the PIN is 0 and the config software on the PC says that the PIN is "Not Configured".
How do you get it to generate a PIN in the 1st place?
Click to expand...
Click to collapse
Answering you purely from my experience.
I got BB client installed on my XDA2 and the desktop BBconfig s/w on my PC connecting to my office network. While my XDA2 is on my cradle and pressing the BBconfig connect button, I supposed the BBConfig establishes the connection to my company BES and generated a PIN which is also registered with the BES server. If any of these steps should fail (e.g. PC not connected to BES) , I suppose the PIN will not be obtained.
In any case, I haven't gotten it to work. My company BES server refuse to recognise my PIN as a valid one.
Hmm... so we need to find out how to register the PIN that is generated with the BB service.
Action points then, guys!
1. Find out how to register the software generated PIN with BES
2. Find out how to switch APNs for different carriers
Thought BA owners considering 'upgrading' to the Kaiser (TyTN II / MDA Vario III) may appreciate my experiences:
- No unlock generally available (yet) if you buy a branded version;
- No infrared port (well the OS has an option to "receive incoming beams", but I can't find one it);
- No dedicated earphone jack;
- Impossible to use dual-sim adapter (yet?);
- Need to upgrade to ActiveSync 4.5 and Lotus EasySync Pro 4.2.4 or 4.2.5 to sync WM6 Calendar / Contacts with Lotus Notes. IBM currently charging over £50 ukp for 4.2.5 if you don't have a corporate licence;
- A pain to sync with Vista; and
- Really fiddly set of key-presses to start composing an SMS.
Maybe I should have called this post "Things I miss about my BA"?
Back to the BA.
I know man I went from the BA/SX66 to the imate KJAM, to the TMo MDA, to the Cingular 8525. Then was considering the Universal. But when I just happened to cruise these BA forums and saw that the Helmi WM6 ROM was out. Loaded it to the SX66 and I was jakked! WM6 on the Large Screen. The other Devices were no longer a quantum leap ahead. My SX66 was worn out which is what started my search for a replacement. I've found it! The O2 XDA IIs with Helmi's WM6 and Xsplodes Touch cabs. A Masterpiece!
Well i have upgraded my Dash Rom to WM6.1 and no major issues so far. One thing is bothering me though. I had BB Connect (version .67) with WM6 and it worked just fine, but its completely dead with 6.1. I have tried all possible versions of BB Connect with no success. The PIN and everything is generated, but the IP is not connected. Is there anything and/or any version of BB Connect that can be used? I need my BB connect to get my work mails. since im on the BES Server.
INFO:
Windows Mobile 6.1 Standard
Radio Version 4.1.13.51_03.07.90
CE OS 5.2.19700 (Build 19700.1.0.0)
I dont know what is needed, so i included the above.
Plz Help.
Hi Buddy
I'm really sorry to report I read that all v4 Blackberry Connect versions require WM6.0 and will not function with WM6.1. I also read that RIM has decided to cease development of BBConnect for WM.
Sorry, I have the same problem so if you ever resolve it PM me but I am now pushing at my company to see if we can get PushMail running...
Yours
Leon