Related
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
Please forgive me if this was already addressed at some other point. I searched, but could not find the answers I needed. I found the BlackBerry Connect software (after a while on the forums) and installed it on my BA. The software runs, generates a PIN, etc...
Right now, I do not have BB service on my plan, and I am wondering - will this client only work on BB Exchange Connector, or will BB Web Connect work also? I want to make sure I get the service that best suits my needs...
If a PIN is generated w/o sync, do I still need to sync it w/ BB software on a Win PC? I use *nix and that would be inconvinent to say the least...
Also... How the hell do you uninstall BB software if you decide not to use it? There is no entry in the remove programs app...
Thanks!
Does anybody have any practical experience with this peice of software for other than BES connectivity?
Does anybody know if this can be used for PIN messages or other Blackberry push services?
Ok. After searching through the forums, and trying various things, I've finally given up...
The goal: To enable bluetooth DUN for WM6.
According to Microsoft, this feature was originally removed due to the thought that their 'Connection Sharing' feature was superior. Unfortunately, my TomTom 910 will ONLY connect via DUN. So, obviously I would like that 'feature' back!
Do any of the chefs out there have access to this feature, and can create a CAB to enable it on my 8525??
This would REALLY be appreciated. I'm sure I'm not the only one out here who misses this feature.
thanks.
I'm with you
Me too
I'm in the same boat. 8525 and 910. Would love a fix.
Kevin
Considering how the change was made to WM6, it is probably unlikely anyone would be able to bring back without issues. I think it is time TomTom start supporting WM6.
Not very hopeful
I asked this same question on the general forum just a couple of days ago.
http://forum.xda-developers.com/showthread.php?t=309996
Unfortunately, from Menneysys' answer it looks like Ipsi2000 is correct.
I think the options for us TomTom 910 users are:
1. Use duplicate sim and keep another phone in the car to connecto to TomTom
2. Pray and wait that one of the operators releases (or one of the chefs gets hold of) a version of WM6 for the Hermes with DUN back in there (since it will be an option at each operator's discretion)
3. Hope that TomTom upgrades the firmware to support BlueTooth PAN over ICS (That will happen just after hell freezes over. We'll probably have to buy the TomTom 920 or something...)
4. Flash our Hermes back to a pre AKU 3 WM5 ROM (Nooooooooooo!)
cuccureddu said:
I asked this same question on the general forum just a couple of days ago.
...
I think the options for us TomTom 910 users are:
...
2. Pray and wait that one of the operators releases (or one of the chefs gets hold of) a version of WM6 for the Hermes with DUN back in there (since it will be an option at each operator's discretion)
...
Click to expand...
Click to collapse
I also miss DUN thingy (I have M$ BT stack on my toshiba with completely crippled/non functional PAN and don't really feel like experimenting with Widcomm BT stack right now). So, no GPRS/EDGE internet connection for me - I kind of got used to it with my old P910...
There is an idea though - I did a little digging in the BT services branch of WM6 registry and I've got an impression that DUN functionality is still there it's just has to be enabled via registry (dunno why I got so sure though). What you can try is to ask somebody with pre-AKU 3 wm5 device to dump the registry for you and compare Bluetooth branch (the part where it lists services) with your WM6 device.
It's just a hunch - if what you are saying about operators enabling DUN BT service at their discretion is true, then this trick could actually work out.
i have a spare hermes [Tmobile VarioII variant], i can dump you a copy of the registry just after a HR is you would like?
i can dump it via registry workshop if thats best for you?
Acuum2 said:
i have a spare hermes [Tmobile VarioII variant], i can dump you a copy of the registry just after a HR is you would like?
i can dump it via registry workshop if thats best for you?
Click to expand...
Click to collapse
Yup, sounds great. If you can do just HKLM branch that should be enough. I have WM6 black - we can compare BT parts se if we can try to enable DUN back.
The worst part is that, according with MS blog, they DIDN'T remove BT DUN, they give it to the operators, and they can choose to add or not BT DUN to their ROM.
Just isn't in DEFAULT rom, is an option
So, somewere, the MS BT DUN should be available!
I love how because you use it, it automatically makes Bluetooth PAN useless.
It isn't.
It is MILES better than ****ty Bluetooth DUN. I use TomTom on an ancient Ipaq PDA, and even that supports PAN. Not only does it support it, its miles miles more stable. It doesn't require you to dial-up every time you go through a tunnel, or under a bridge, it just works.
I vote NO to bluetooth DUN (unless it can run alongside PAN)
Its TomTom you should be angry at, not MS or the operators!
I know, my car is miles away from my feet, but sometimes I need to go were only feet are allowed
The problem isn't what is better but why they removed BT DUN instead of leaving it..
I am a bad, bad, bad boy, but I believe there is some marketing strategy behind, like AS4.5 NEEDED for WM6 not working with outloook 2002, with NT...
al3xxx said:
Yup, sounds great. If you can do just HKLM branch that should be enough. I have WM6 black - we can compare BT parts se if we can try to enable DUN back.
Click to expand...
Click to collapse
al3xxx
Here you go,
sorry did the entire thing...
well i added the WM DUN reg keys to my Elf WM06 and its not enabled the DUN service... (not surprised, if it were that simple it would have been figured out weeks ago... So what's next?)
Microsoft saying they give the DUN to the operators sounds fishy. Let's face it, Microsoft would prefer everyone uses PAN (considering it provides all the features available in DUN and plus more). They basically said to the operators we will support PAN, however if you wish you can implement DUN but you will have support it yourself and any issues that may crop up due this implementation. Most operators would not want the additional support or issues that may come up due to them providing a deprecated function. PAN is the replacement for DUN and there is very little we could do about it.
Software vendors need to adopt PAN or it may not work with WM6.
clublander said:
I love how because you use it, it automatically makes Bluetooth PAN useless.
It isn't.
...
I vote NO to bluetooth DUN (unless it can run alongside PAN)
Its TomTom you should be angry at, not MS or the operators!
Click to expand...
Click to collapse
Yeah not MS, what made winxp BT stack PAN absolutely NOT working - tried bunch of BT devices with it - neither one was recognized as PAN capable... See if PAN on the phone (and PC) was working for me whan I was set in front of the fact that there is the ONLY choice MS gives me if I want to use my phone as wireless modem i wouldn't really get the DUN back...
al3xxx said:
Yeah not MS, what made winxp BT stack PAN absolutely NOT working - tried bunch of BT devices with it - neither one was recognized as PAN capable... See if PAN on the phone (and PC) was working for me whan I was set in front of the fact that there is the ONLY choice MS gives me if I want to use my phone as wireless modem i wouldn't really get the DUN back...
Click to expand...
Click to collapse
Thats funny, I use my WM6 device with XP with no troubles.
I suggest you need computer lessons.
To re-iterate, TomTom is going to have to update THEIR Bluetooth stack, unfortunately. PAN is almost identical to DUN, it just has an interface on the phone now, whereas you had to do it all from your PC before. If you don't believe me that it's virtually identical, look in your WM6 registry. The PAN service is STILL CALLED "DIAL UP NETWORKING" in the registry. Furthermore, if you recall, when you pair your phone to your pc, the phone offers DUN as a service!! Do you see PAN in that service list? No... because it's DUN!! Same thing, folks.
All MS was shooting for was the ability to make it easier to dial up to the internet through the phone, not to mention, add the functionality to become a Network node. It's the same thing as buying a new pc these days that doesn't come with a dial up modem. Why not? Because it comes with a network adapter.
TomTom is going to have to update their stack to recognize this service.. not the other way around.
Stpete111,
I emailed Tom Tom about this today, and their attitude is as follows:
I told them I have a M3100 that their attitude was - we don't no support phones with WM 5 OR 6 especially NOT this device! But get this, they DO support the O2 XDA Mini S....so I don't think they understand that they are already supporting a WM5 device....
Anyway, there was no indication that they intend to change this, and I suspect that they won't.
So I suspect you'll have four choices:
1) Live without any phone when using you're TTG - not an option if you've already subscribed to one of their services.
2) Go back to WM5 - where it will work - far from ideal.
3) Get a spare phone that will work, and a duplicate sim - not that easy...
Or finally, 4) Invest in a device that's more current that WILL support WM6 devices.
Anyway, that's my thoughts - I've yet to make up my mind. But I'm not holding out any hope of TT changing their minds!!
Matt
Here's an update:
I have spoken with TomTom regarding this issue, and this is what I have found out. It's not really good news.
TomTom is phasing out the cell phone connection to their GPS units. All future units do NOT use cell phones to access traffic and weather info. They will ONLY use FM antenna for their data.
So, TomTom probably won't be updating their Bluetooth stack for us current-generation GPS owners. Their next generation ships in July.
Ideally, (for me at least), I would like to have BOTH DUN and PAN services on WM6. That way, for "older" devices, we still have connectivity, while at the same time, future devices can use PAN.
(just my .02c)
Has anyone tried Garmin products? I have tried two Garmin units but NOT with Bluetooth, so I don't know anything about their BT functionality. I DO know however that I much prefer the Garmin devices to TomTom's. Not trying to spark a debate here over which is better... but perhaps checking out Garmin's capabilities is a 5th option?
Microsoft are going to release WM6 with the ability to enable (DUN) for legacy devices, I.e. TOMTOM GO series... are there any cooks interested in releasing a ROM with this option enabled?
this would be great. if this was done i would have nothing to complain about with wm6
Same here, it's just the final thing I need for a perfect WM6 ROM.
One vote more
Same, here. I also tried to use DUN on WM6 with TomTom Go. But apparently WM6 lacks DUN support in Bluetooth Stack.
Does anyone have a fix for this or is there any good WM6 Rom out there with Bluetooth DUN support?
Yes-Sir-Eee
I would love to see that, my 910 won't use the services without DUN...
I was browsing earlier and I think I saw a .cab file in the Wizard forums for PAN support in Windows Mobile 6, however I don't think that anyone said that it worked.
Really?
Point me in the right direction & I'll happily give it a whizz...
Cheers,
mccreath said:
Point me in the right direction & I'll happily give it a whizz...
Cheers,
Click to expand...
Click to collapse
I downloaded the CAB from here, and installed on my Wizard. It says it installed but does not work.
Here's some more info:
http://forum.xda-developers.com/showthread.php?t=307235&page=2
I can confirm this fix
Used trinity files posted by MuN on the above thread.
heres what i did
Installed cab - soft reset
pasted all files from zip in windows folder - soft reset
then unpaired tomtom 910 and reparied, hey presto it found DUN support
Perfect, have been waiting for a fix for this
I've run the .cab and copied the files into the Windows directory, however I'm having a real headache trying to configure a data connection.
Which device to choose for TomTom GO 910?
@the.drone
I followed your instructions and now my TomTom reports that my phone has DUN capability. Problem is HTC TyTN or HTC Hermes ist not listed as phone in the phone list and automatic configuration does not work.
Can you please give instructions which phone to use or how to configure the data connection manually? Because DUN support which can't be configured is as good as no DUN support.
Thanks a lot.
Marc
it just worked first time automaticaly with mine, maybe i was just a fluke but it found the data coonection first time on 3g
How can I find out my TomTom thinks my phone has DUN?
Edit: when I try to add my TomTom to my Hermes, it only brings up a handsfree tick box, when in Windows Mobile 5 I think it also brought up two additional tick boxes. Any ideas if this is following the path to success of if I've screwed up?
Double post.
DUN Doin' it
Will be giving it a go first thing in the morning.
Cheers for the update, will post results....
Bargain!
You eff-ing ROCK... DUN on WM6.
My TomTom 910 loves you!!
Hoo-haa!
How did you get it to work?
So can someone share how they did it?
I followed the instructions and it now finds my ttg 300, and says it has the services - but can't set up the actual DUN connection either manually or automatically!
Any ideas?
Matt
I really am sorry to be a pain in the butt, but I'll outline what I've done.
1). Paired my Hermes up with my TomTom 910.
2). Run the .cab.
3). Soft reset.
4). Copied the files into the Windows directory of my Hermes via the storage card.
5). Soft reset.
6). Repaired my Hermes and TomTom 910 after having deleted the previous connection. At this point it says "The following features were found: Hands-free calling, Wireless data connection, Phonebook".
At this point I try and setup a data connection that it hits the fan. It's really annoying because it feels like I'm falling at the final hurdle. I also wondered if I was struggling because of an issue with connecting to the T-Mobile network, however am I right in thinking that mccreath's using a T-Mobile GPRS contract SIM connection?
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