I have had my imate JASJAR since Tuesday and as of this morning, I have given up trying to setup Goodlink over gprs. It just doesn't work.
Up until the universal, there has not been a factory gprs WM5 device. In fact, Good is saying that they really have only tested WM5 on a Dell Axim X50 with WiFi. So guess what will only work right now on a WM5 device? You guessed it, WiFi only.
I tried no less than 5 different ways on provisioning the device, and numerous calls to Good. It may work on gprs the first time, but after that, it will not do any send/receive on gprs. As soon as you turn on WiFi, it works like a charm.
Looks like I'm on Exchange Active Sync over gprs until they fix it, or until Exchange 2003 Server SP2 comes out. I have turned the corner on my PDA2K and I'm not looking back. The JASJAR is probably the best handheld I have ever owned. I am thinking of getting rid of my laptop in favor of using this...maybe.
Oh and by the way....Good has also not tested their apps with a VGA device (because they only tested the QVGA X50), so everything looks a little fuzzy and the cursor on the screen is one space to the right of where it should be on the screen. So it looks like you have a space after the last letter typed, but you don't.
I have no doubts that Good will have a new release soon, since the devices have now hit the market. They make a great product and I have had a good experience using it. I guess I'm just a little ahead of the curve.
Which of the server product you were trying (Good Server, Good Server Workgroup)? Also, which version of the client you were using on your device, was it 4.5.0.65?
Good Server and the most current version of the client 4.5.0.65.
You should ask them about the workgroup product. It is however currently in beta.
Why? does it have a different client? What makes it different then the server product?
I believe the client is the same, however the server is a little different. I am using it and I don't be I have the issues you have. Nonetheless, I will have to wait a little while to see how well things are going.
I always thought the pocket pc client was a little flaky especially when also sync it with the pc. However there are some days when it works well without issues.
Goodlink on WM2005
I am having similar issues on the Wizard. Good told me there will be a formal WM2005 client release in Q4 2005 and a beta/trial version of the client in the next few weeks. It seems that Sprint AV6700 users are having the same issues... I added my name to those who would like to try out the beta client. Perhaps you guys might try that also... I'll let you know if/when I get a WM2005 beta.
Regards
Chris
Related
Hi all. Heard there's a newer version of ActiveSync on another thread. namely Activesync 4.1. Can anyone give any feedback confirming this (although I think it's still in Beta stage). If so, isn't it worth a try given the problems encountered on the Universal using just Activesync 4.0.
Someone must know!
Here's the link: http://forum.xda-developers.com/viewtopic.php?t=28535
Well I have it installed and I don't see anything different. Probably bug fixes. Won't harm to upgrade.
i have 4.1 running, dont know if its connected to the activesync on universal always restarting but i can only sync with pc if i have the universal powered off, then when plugging it in i see the orange power led kick in, 10secs ish later active sync will start,
if i plug in when switched on i get a error bubble on pc saying i have a malfunctioning device, power off and plug back in, wait a bit, i have a working syncing device. wierd!!!!
i only got usb1 on this lappy and my other has 2.0 had same problem, so i dont think its a usb problem
no bugs on my side
i installed 4.1, and it works like a charm on both pda2k and universal
mikeycollins13 said:
It took a while to work out, but here it is: Skype works fine as long Activesync is not on. In the old machines, AS would kick in and appear in the memory only after you sync'd. Here it comes up automatically, whether you sync or not. In fact, you should see Active sync running in the background virtually always.
Clicking on the memory you'll see its always on, you press stop, and Skype works for 5-10 minutes, until AS turns tiself back on.
Any fixes for this in the registry?
Click to expand...
Click to collapse
Great stuff Nabil! Now, can someone please check if there are still issues with ActiveSync causing problems with Skype? I would do it, but I don't have my Universal yet! Waiting on the MDA Pro or Exec.
I'm not entirely happy that Activesync is workig the way it was intended & as I was unable to get this confirmed from several forum members, I ventured out of Xda developers.com to seek confirmation of my doubts.
I ended up reading a review of the new Dell Axim X51v Pocket PC, which as you may or may not know, uses WM 5.0 (but less the phone side of things). Not exactly to my surprise, i found that even in non-phone PPC devices, Active sync is a bit of a cause for concern!
Read here: Review of Dell Axim x51v PPC (WM 5.0)
Windows Mobile 5: Not All is Golden
I won't delve too much into Windows Mobile 5 in this review, since I'm focusing on the X51v itself, but I found Windows Mobile 5 very painful in two ways when I was setting up and using the X51v. First, after a hard reset I connected the X51v to my PC and set up a new partnership. ActiveSync 4.0 has a different partnership wizard if you have a Windows Mobile 5 device, and it's quite intuitive. I entered my hosted Exchange account information, then watched as basically nothing happened. The X51v synchronized with my desktop PC, but coughed up an 0x85020006 error when the device tried to sync with the Exchange server. ActiveSync 4.0 removes the option for Internet passthrough - I assumed that meant it was automatic, but after fighting with Connection Manager on the X51v for 15 minutes I gave up and disconnected. I turned on WiFi, and the X51v saw my access point - I entered my WEP key, started ActiveSync, and clicked sync. It worked! Within a few minutes I had all my data on the X51v - but why wouldn't the synchronization work in the cradle? I have no idea, but it's a serious problem.
Later, I wanted to see if a particular ActiveSync bug had been fixed: I've always had the problem where, after a backup and restore, the Pocket PC has been unable to synchronize against the Exchange server again. Only a hard reset would allow the Pocket PC to sync again. On the X51v, I did a backup using the included application, then hard reset and a restore. I restore the device, then after a soft reset I noticed the date was wrong. No matter, I fixed it and started a sync session. Much to my delight, the sync actually started, which is sometime that wouldn't have happened under Windows Mobile 2003SE.
My delight turned to disbelief, then anger as I saw what ActiveSync was doing: it duplicated 900 contacts, 50 emails, and 6 months worth of appointments! No warning, no "Replace, Remove, or Combine" dialogue box, simply a duplication. It will take me hours to fix this manually, unless I can find a tool to remove duplicates. I have memories of such a tool, but at this point I haven't had time to track one down. Any suggestions for one that will work with Outlook 2003 and an Exchange server? I'm unsure as to whether this is a problem with Dell's backup application, or with ActiveSync. The bottom line is that in this instance Exchange ActiveSync remains broken after a restore - and I'd rather have it break completely then duplicate all my data, so from my point of view it's actually gotten worse. I didn't think that was even possible!
Suffice it to say that while Windows Mobile 5 brings with it several key advantages - persistent storage is amazingly helpful - my experience with it so far has been mixed (WMP 10 Mobile retains its horrible library functions), and I have no shortage of feedback for Microsoft at the MVP Summit coming up in a few weeks. Windows Mobile 5 feels like one step forward and two sideways.
End of this part of the review. Full Review here: http://www.pocketpcthoughts.com/articles.php?action=expand,43092&start=2
What do you guys think? I think quite a few problems Universal owners are experiencing will dissapear once MS fix their ActivShite application!
I spent some time yesterday trying to find an answer to my continuous problems connecting with Blackberry Connect. This included different ROMS and different versions of Blackberry and Desktop Connect software.
My problem (like many others) is that the initial set-up of Blackberry connect seems to work but as soon as I restart the device or service, it is disconnected and sometimes the service completely shuts with the blackberry icon dissappearing from the tray.
The best success I had (and is still working after 24hrs) is to install Blackberry service without wireless calandar support. Somehow for all versions of ROMS and connect software, enabling wireless calander is causing the disconnects. I can't remember what the service name for this is but for those with similar problems this might help.
On a similar note, does anyone know why wireless calander could be bringing down the blackberry service?
Sean.
seanrkelly said:
I spent some time yesterday trying to find an answer to my continuous problems connecting with Blackberry Connect. This included different ROMS and different versions of Blackberry and Desktop Connect software.
My problem (like many others) is that the initial set-up of Blackberry connect seems to work but as soon as I restart the device or service, it is disconnected and sometimes the service completely shuts with the blackberry icon dissappearing from the tray.
The best success I had (and is still working after 24hrs) is to install Blackberry service without wireless calandar support. Somehow for all versions of ROMS and connect software, enabling wireless calander is causing the disconnects. I can't remember what the service name for this is but for those with similar problems this might help.
On a similar note, does anyone know why wireless calander could be bringing down the blackberry service?
Sean.
Click to expand...
Click to collapse
I had a similar problem with the BB connect (2.1.2.16) client on my Wizard. BB connect works fine without calendar sync. I had similar stability issues when I used the old BB connect client (1.x) when my mailbox got too large, and I have a HUGE amount of calendar information thus I am guessing it is size that is causing the issue. It does not help that the BB connect calendar sync doesn't specify a cutoff date to reduce the number of old entries.
I am running BB Connect 2.1.2.16 on my 1605 and have constant issues with the BB client.
I get the odd VCAL error occuring but these are rare compared to the BB Client just switching itself off on a regular basis. Restarting the client does not fix the issue and I have to softreset the device. The device is generally slow and unstable after a long period of running the BB Connect client constantly.
I send and receive about 200 mails a day and keep a weeks worth of mail in my Blackberry mailbox so yes perhaps this is size related.
However I have a collegue in Austria who is using the T-Mobile version of the Hermes, and a slightly earlier version of BB Connect (2.1.2.15 I think) and it seems to be a lot more stable.
Any clues ??
Halfpenny said:
I am running BB Connect 2.1.2.16 on my 1605 and have constant issues with the BB client.
I get the odd VCAL error occuring but these are rare compared to the BB Client just switching itself off on a regular basis. Restarting the client does not fix the issue and I have to softreset the device. The device is generally slow and unstable after a long period of running the BB Connect client constantly.
I send and receive about 200 mails a day and keep a weeks worth of mail in my Blackberry mailbox so yes perhaps this is size related.
However I have a collegue in Austria who is using the T-Mobile version of the Hermes, and a slightly earlier version of BB Connect (2.1.2.15 I think) and it seems to be a lot more stable.
Any clues ??
Click to expand...
Click to collapse
I run 2.1.2.16 on a Wizard and without PIM, it works reasonably well. The most I've kept in the BB inbox is around 400 mail as that was around when the BB 1.x client used to play up an I got used to deleting the mail from BB (I do not sync deletes with my Inbox for this reason). If you are keeping 1000 mail I would say try and delete the mail daily (including deleting from the "Deleted" folder) and see if it improves. I know that with the BB 1.x client, if I got too many mail the BB client would start chewing up CPU and the device would act strange, and sometimes I needed to soft reset, disable BB, delete the mail, reset again and things would be good again.
What baffles me is why people keep so many emails on their BB's I read a message, if it requires an immediate response I send a note from the BB and then maybe follow up later on the PC, I then delete the message, if its not relevant I read and delete it, if it can be dealt with later, I read it, then mark it as unread and then delete it from the BB, I do not sync my mailbox with the BB thus all mail is still in my Outlook inbox...
tonyb15re said:
What baffles me is why people keep so many emails on their BB's I read a message, if it requires an immediate response I send a note from the BB and then maybe follow up later on the PC, I then delete the message, if its not relevant I read and delete it, if it can be dealt with later, I read it, then mark it as unread and then delete it from the BB, I do not sync my mailbox with the BB thus all mail is still in my Outlook inbox...
Click to expand...
Click to collapse
I think it just depends on how people work. I tend to read on the run (between meetings) and I delete when I remember sometime at home or on the train on the way to work or something like that.
Anyone got it working or tried Blackberry Connect client 4.0 on the Athena?
Mine (4.0.0.67) seems to try to create the blackberry network connection but won't connect. I can run it fine on the TyTn, but not on my X7500.
any ideas? I tried creating manually a netowrk connection for the APN, named it BlackBerry etc, to no avail. You see the device type is recognized as HTC-Athena. When I check the status, it stays at not connected. When I suspend, then resume, it briefly shows, Network available, then flashes Data Tunnel available, and quickly switches back to not connected. As if it looses connectivity. And yes, I'm all provisitioned fine, the same darn SIM in the TyTn with the same BBC client executable on it works. Go figure.
lbarouf said:
Anyone got it working or tried Blackberry Connect client 4.0 on the Athena?
Mine (4.0.0.67) seems to try to create the blackberry network connection but won't connect. I can run it fine on the TyTn, but not on my X7500.
any ideas? I tried creating manually a netowrk connection for the APN, named it BlackBerry etc, to no avail. You see the device type is recognized as HTC-Athena. When I check the status, it stays at not connected. When I suspend, then resume, it briefly shows, Network available, then flashes Data Tunnel available, and quickly switches back to not connected. As if it looses connectivity. And yes, I'm all provisitioned fine, the same darn SIM in the TyTn with the same BBC client executable on it works. Go figure.
Click to expand...
Click to collapse
I had running perfectly BBC 2.1.2.54, I never hear a version 4, where is it?
lbarouf said:
Anyone got it working or tried Blackberry Connect client 4.0 ...
Click to expand...
Click to collapse
I tried, but unfortunately it's the same problem like with other devices. If you don't have a matching OS-Version number you will not be able to get it up running. As far as I can see there is currently no way to change the os version number in the athenas rom. I found the right values but the .nbh file is signed, thus it will not flash.
I think we will have to wait for another BBC version or another ROM version (or someone finds a way to flash any rom).
lbarouf said:
Anyone got it working or tried Blackberry Connect client 4.0 on the Athena?
Mine (4.0.0.67) seems to try to create the blackberry network connection but won't connect. I can run it fine on the TyTn, but not on my X7500.
any ideas? I tried creating manually a netowrk connection for the APN, named it BlackBerry etc, to no avail. You see the device type is recognized as HTC-Athena. When I check the status, it stays at not connected. When I suspend, then resume, it briefly shows, Network available, then flashes Data Tunnel available, and quickly switches back to not connected. As if it looses connectivity. And yes, I'm all provisitioned fine, the same darn SIM in the TyTn with the same BBC client executable on it works. Go figure.
Click to expand...
Click to collapse
I should be getting my hands on BBC 5.0, will try it. It's build for the HTC Excalibur and Hermes, but I suspect it will run also on the Athena. They are renaming the BBC to something else ?!? Anyway, the BBC 4.0 client was working fine on WM5 OEM on Hermes and on the WM6 rom for asia, can't recall which provider. Won't on the Black 3.01. Sounds right about the version number though... anyway. BBC 2.1 will do fine for now I guess.
Anyone tried BBC and Live on the same device (BBC on a BES, with calendar sync) ?
lbarouf said:
I should be getting my hands on BBC 5.0, will try it. It's build for the HTC Excalibur and Hermes, but I suspect it will run also on the Athena. They are renaming the BBC to something else ?!? Anyway, the BBC 4.0 client was working fine on WM5 OEM on Hermes and on the WM6 rom for asia, can't recall which provider. Won't on the Black 3.01. Sounds right about the version number though... anyway. BBC 2.1 will do fine for now I guess.
Anyone tried BBC and Live on the same device (BBC on a BES, with calendar sync) ?
Click to expand...
Click to collapse
BBC 5.0? Is this the 'virtual bb' offering that bb announced not long ago?
obviously my athena fails with bb 4.x.
The only coment is that when I install, the today pluggins disappear, maybe provide some light to hackers...
titus666 said:
BBC 5.0? Is this the 'virtual bb' offering that bb announced not long ago?
Click to expand...
Click to collapse
So I heard... BBC is renamed to Virtual Blackberry. Anyhow. Better version of BBC 4.0 (supposedly).
lbarouf said:
So I heard... BBC is renamed to Virtual Blackberry. Anyhow. Better version of BBC 4.0 (supposedly).
Click to expand...
Click to collapse
Virtual bb works differently than BBC. Its basically a virtual machine, and thus apps within it is not integrated with WM.
My experience with BB 2 in Athena (WM5) is great. Works perfect... or at least as expected. You got the problems related to versión 2 that don't allow you to view jpg files and so on, but you receive and send messages without any problem.
My configuration is BB 2 against a BES server in release 4 (I think) and my account is on Lotus Notes R6.
Well I tested the BB 4. Madness. The program was working properly on my Athena (WM5) but the installation makes a real mess with the Today screen. Everything in today screen stop working and left the Today program unable to use or configure. That happens to more users than me. So is not a problem with my Athena (WM5). Looks like BB 4 has real troubles with Today of WM5. The guess is BB 4 is designed to be used with WM6... I'm not sure.
The BB 4 seems to work faster, supports more attachments and allows you to navigate Internet thru the BB connection which is useful for those users that are not allow to access Internet directly from the Athena.
But from my point of view BB 4 did a real mess with my WM5 so I finally made a hardreset and rollback to BB 2. I will back with BB 4 as soon as I upgrade to WM6 my Athena.
Best Regards,
mahjong
mahjong said:
My experience with BB 2 in Athena (WM5) is great. Works perfect... or at least as expected. You got the problems related to versión 2 that don't allow you to view jpg files and so on, but you receive and send messages without any problem.
My configuration is BB 2 against a BES server in release 4 (I think) and my account is on Lotus Notes R6.
Well I tested the BB 4. Madness. The program was working properly on my Athena (WM5) but the installation makes a real mess with the Today screen. Everything in today screen stop working and left the Today program unable to use or configure. That happens to more users than me. So is not a problem with my Athena (WM5). Looks like BB 4 has real troubles with Today of WM5. The guess is BB 4 is designed to be used with WM6... I'm not sure.
The BB 4 seems to work faster, supports more attachments and allows you to navigate Internet thru the BB connection which is useful for those users that are not allow to access Internet directly from the Athena.
But from my point of view BB 4 did a real mess with my WM5 so I finally made a hardreset and rollback to BB 2. I will back with BB 4 as soon as I upgrade to WM6 my Athena.
Best Regards,
mahjong
Click to expand...
Click to collapse
Hi, I answered in the main BB Hacking thread.
I have version 4 installed on my Athena with WM5 without any problems. It didn't make any mess to my today screen. Also I haven't noticed any other negative side effects (except that I cannot disable the automatic device lock after max. 1 hour, but I assume thats a company policy setting, have to talk to our BES guys).
Cheers
I have it running on my AMeo, no tweaks whatsover just installed it, soft reset and voila... The only thing I have done is disablethe today item as they appear to havea few conflicts.
Its much more stable than BBC 2xx.
Bring on Virtual Blackberry im hoping that it will enable me to RDP to my work machine through the BB connection negating the need for VPN
Good morning,
I have just switched from a Nokia N95 to an Asus P635 running WM6 professional.
One thing that is confusing me is how to select a specific connection to the internet.
What I mean by this is that I use ActiveSync to sync email with a server. When I am at home, I want to use WiFi to perform this, when out of the house I want to use GPRS. On the Nokia, I simply selected the access point to use when I came in or out of the house. How do I do this in WM6 so I can ensure I use my home WiFi when available but GPRS when not available?
Many thanks,
Mike
same prob here...
for "usable" phones/pdas stick with the nokias or sonys etc
for "playing around" wm phones are more fun - almost everything we take for granted on "usable" phones needs a 3rd party util or something made by the wonderful people here to do the same. hence a great way to have some fun and pass the time..
Hi
Has Anyone Got the BlackBerry Connect Software Working on this model?
Thanks
Leon
i'd be curious as well. there are a few threads on this, and it seemed like nobody got it to work on the touch cruise (though people have gotten it to work on their touch).
out of curiosity, why are people choosing to use blackberry connect rather than direct push through exchange? i find that my push is not 100% reliable and considered using blackberry connect to fix this. does anybody else have that dilemma?
Sadly, blackberry is the 'corporate standard', so I am stuck with it.
I have managed to get the Blackberry Connect client 4.0.0.97 to work 100% reliably on HTC touch p3450 with an HTC release ROM. As soon as you load a tweaked or cooked ROM the Blackberry Connect stops working.
Sadly the XDA Orbit 2 comes with an o2 cooked rom so it wont work with that, I have a call in to o2 support but I wont hold my breath
Yours
Leon
Seams to work
Hi,
I still new to Blackberry installation. (It´s my first go today)
From what I have read here a lot of people have problems.
I´ve successfully installed 4.0.0.97 of the Polaris with Bepes 0.58 Full German, eventhough the first installation required a compleate reset:
The HTC also connects to the server, but I get an error as my current user has been rejected. I do believe that our IT Admin needs to allow me to use the Blackberry function..... or am I still doing something wrong?
Unforunately I´ve noticed that the PDA has slowed down somewhat after installing the Blackberry connect
Look forward following this post.
Cheers
Rar9
Rar9 said:
Hi,
I still new to Blackberry installation. (It´s my first go today)
From what I have read here a lot of people have problems.
I´ve successfully installed 4.0.0.97 of the Polaris with Bepes 0.58 Full German, eventhough the first installation required a compleate reset:
The HTC also connects to the server, but I get an error as my current user has been rejected. I do believe that our IT Admin needs to allow me to use the Blackberry function..... or am I still doing something wrong?
Unforunately I´ve noticed that the PDA has slowed down somewhat after installing the Blackberry connect
Look forward following this post.
Cheers
Rar9
Click to expand...
Click to collapse
To get connected, you can talk to your IT amdin, but you don't need to if you also install the Blackberry Connect for Windows Mobile DESKTOP software. What that lets you do is obtain and assign a PIN to your Polaris/BBC setup. Its a security measure to tie your phone with your email account. Install BBC for WM desktop on a PC that has access to your email account (i.e. Outlook connecting to your Exchange server), then run the program. It generates a PIN, assigns it to your phone within BBC on the phone, then you should be good to go. Of course, you can talk to your IT guy otherwise.
And the slowdown is what I mentioned in the other forum. BBC uses LOTS of CPU, memory, and thus, battery.
Hi Rar9
If it connects then disconnects that is because you're using a non-release ROM (cooked).
On a succesful install of 4.0.0.97 you will see after reset a connection even if you havent configured desktop, it is required for the desktop proggie to do its work.
HTH
Leon
leondaphillips said:
Hi Rar9
If it connects then disconnects that is because you're using a non-release ROM (cooked).
On a succesful install of 4.0.0.97 you will see after reset a connection even if you havent configured desktop, it is required for the desktop proggie to do its work.
HTH
Leon
Click to expand...
Click to collapse
are u saying the ver 4.0.0.97 will work n you have it on your cruise?
I have not been able to get it to work and I have the stock HTC ROM. I'm not aware of anyone who's been able to get Blackberry Connect to work on this device. Check out this thread for others in the same boat:
http://www.sems.org/entry.asp?ENTRY_ID=276
Seven
leondaphillips said:
Hi Rar9
If it connects then disconnects that is because you're using a non-release ROM (cooked).
Leon
Click to expand...
Click to collapse
Leon,
I don´t think it would be related to the cooked Rom. I believe that it tries to get allowance from the server and then is rejected since I never had a blackberry so far with this company. Unforunately I still can´t confirm 100% since the our IT has not responded to my query.
In the meantime I have removed the BBconnect and use an Outlook Webmail connection via Seven (thanks for jomo25) which is very FAST and is not so hard on the CPU like BBConnect. I also believe its a lot easier to install.
(http://community.seven.com/forum/index.php?forum=true)
I´ll give it another try once I get more feedback from our IT and will post my results.
Cheers
Rar9
Yeah I don't think it has anything to do with the ROM. There seems to be an issue with the TC connecting to the Blackberry server and I have no idea why. That thread I sent earlier contains some theories on the topic. The BC software is a resource hog for sure.
Assuming you're using BC to connect to Coporate Mail (Enterprise) you can always try Microsoft Direct Push instead of Blackberry Connect to get to the Exchange server. A less optimal path would be to use IMAP to connect to the Exchange server. Then you would lose Push mail functionality
Well, we have 2 threads on the same topic. Some diff players in each, so I'll cross-post this one last time...Here's the other thread: http://forum.xda-developers.com/showthread.php?t=376917
Here's what I posted last: Seven is a "competing product" to BB's suite. If you are trying to connect to a BB server, then yes, you'd need BBC. But if you are just trying to get your email delivered, whether it be personal, POP3, IMAP, or you corporate email (Exchange) and you are behind a firewall, then Seven has a solution for you. Some more elegant than others. But it works. For me, it's the only option since we do use Exchange, behind a firewall, with no OWA externally accessible and BBC's software is very juice hungry.
As for getting BBC to work. Without knowing your exact setup, its hard to know what the issue is. First, make sure you are on the right data plan. I.e. for AT&T you MUST be on one of their BB data plans. Otherwise, you won't be able to get to the blackberry.net APN needed. Then, make sure you have the BBC for WM software installed on your phone and PC. (There are 2 programs, one for each) Then, connect your phone to the PC as in ActiveSync. Run the PC's program. You should notice that ActiveSync connection is severed, and the BB program should find the phone. Then go to assign a PIN and it should. Then it shoudl start to pull email to your phone.
The second software you need to run on the PC is here:
http://www.sems.org/entry.asp?ENTRY_ID=225
Click on the link for: ActiveSync_BBConnect_Desktop_Setup_4.0.0.17.zip
Because BBC uses a different APN than all other network access on your phone, and your phone can only connect to one APN at a time, you will not be able to do other things like surf via IE on your phone while you are connected to BBC (another reason it sucks).
----------
@ Rar9, I'm glad Seven is working for you. To be honest, if you can use the Seven software, you might just wanna stick with it. Seriously, BBC is a resource hog and a half as you seem to have experienced. You'll find it tough to go thru a day without battery dying, if your expereicne with BBC was similar to mine. I even have to run Seven's Workgroup Connector (which sends my work mail through my work PC) and I STILL prefer Seven over BBC for that reason. PLUS, you don't have to worry about switching APNs between your carrier's normal Internet gateway and the blackberry.net gateway. And of course th efinal bonus: the BB data packages tend to be MUCH more expensive than the normal data ones (up to 50% price diff with AT&T).
But try it again if you would like. Hope my instructions and links above for BBC help with that.
Ok so let me clarify. I am trying to connect to get my Exchange email through a Blackberry server. Microsoft Direct Push is not an option since IT doesn't enable it on the server. I do have the Blackberry Enterprise (not personal) plan from ATT. I do have the BC software. I do have an activation code from IT. The problem is the phone does not connect to the Blackberry server. Like I mentioned in my previous post if you check out that thread on SEMS others seem to have this issue. I am getting the same behavior this user in the UK is having:
"After installation and Blackberry Setup I get:
PIN pending
IMEI it's ok
IP address No connection
Status/Service Not Connected
By pressing the "register now" button I get Blackberry Edge connection, Status/Service shows Network Available then Data Tunnel Available and finally "Not Connected". During the process I can see an IP address in the Identity screen."
Appreciate your instructions but I just don't think it works. I've tried several different versions of the BC software, no cigar.
So, just to make sure, you have the desktop PC software also? If so, what happens when you connect the PC to the phone via USB? Doesn't it ask you to move the mouse around to generate a random and unique PIN? Oh, and did you force your phone to only use Edge? I beleive AT&T's connection to the BB APN is still only available via their 2G network, not 3G (not 100% on that last thing, but I do remember it was the case before).
You know, it's been awhile since I tried this, but honestly I remember trying like every permutation. I installed and uninstalled almost every version of BC. I tried it with Edge and/or 3G. I tried using the desktop software to generate the PIN and other times I didn't. I guess I can always try again. Have you gotten it to work on your device?
Not on my Polaris. I haven't tried. I did on my Kaiser and on my Hermes. I had the same issues you describe, til I used the desktop software to gen the Pin. I'd try on my Polaris now, except that I don't have the BB data plan and don't want to go thru the hassle with the AT&T guys again to get it added (esp since I won't keep the BBC software on my phone anyways for the aforementioned issues).
So, it may be that it doesn't work with the Polaris. the new versions of BBC should work, but they may not. If you feel you've tried it and did everything right, then it just may not work as you say.
I definitely don't want to steer you down a dead end. I was just checking to see if you did everything I thought needed to be done. Sounds like you had those bases covered.
Sorry!
hambola said:
Yeah I don't think it has anything to do with the ROM. There seems to be an issue with the TC connecting to the Blackberry server and I have no idea why. That thread I sent earlier contains some theories on the topic. The BC software is a resource hog for sure.
Assuming you're using BC to connect to Coporate Mail (Enterprise) you can always try Microsoft Direct Push instead of Blackberry Connect to get to the Exchange server. A less optimal path would be to use IMAP to connect to the Exchange server. Then you would lose Push mail functionality
Click to expand...
Click to collapse
Hi hambola
I read that the RIM Blackberry Connect was designed to work on Release / RTM versions of Windows mobile and has been coded to prevent it logging on via the global BES if the ROM is unsigned or if the device name is not in the list of allowed devices.
I can prove this using my trusty P3450. When loaded with a vanilla WWE RTM ROM Blackberry Connect 4.0.0.97 works fine. Load a cooked ROM and it connects then disconnects. This is the behviour I get on my polaris with its customised o2 ROM.
So it could be a clean ROM problem or it could be that Blackberry just havent allowed the Polaris to connect just yet.
Yours
Leon
xphobic said:
are u saying the ver 4.0.0.97 will work n you have it on your cruise?
Click to expand...
Click to collapse
No
4.0.0.97 doesnt work on Cruise but works fine on a vanilla ROM on P3450
Yours
Leon
jomo25 said:
Not on my Polaris. I haven't tried. I did on my Kaiser and on my Hermes. I had the same issues you describe, til I used the desktop software to gen the Pin. I'd try on my Polaris now, except that I don't have the BB data plan and don't want to go thru the hassle with the AT&T guys again to get it added (esp since I won't keep the BBC software on my phone anyways for the aforementioned issues).
So, it may be that it doesn't work with the Polaris. the new versions of BBC should work, but they may not. If you feel you've tried it and did everything right, then it just may not work as you say.
I definitely don't want to steer you down a dead end. I was just checking to see if you did everything I thought needed to be done. Sounds like you had those bases covered.
Sorry!
Click to expand...
Click to collapse
Hi Jomo25
no offence taken, thanks for your ideas - a second pair of eyes is always welcome!
Yours
Leon
hambola said:
Ok so let me clarify. I am trying to connect to get my Exchange email through a Blackberry server. Microsoft Direct Push is not an option since IT doesn't enable it on the server. I do have the Blackberry Enterprise (not personal) plan from ATT. I do have the BC software. I do have an activation code from IT. The problem is the phone does not connect to the Blackberry server. Like I mentioned in my previous post if you check out that thread on SEMS others seem to have this issue. I am getting the same behavior this user in the UK is having:
"After installation and Blackberry Setup I get:
PIN pending
IMEI it's ok
IP address No connection
Status/Service Not Connected
By pressing the "register now" button I get Blackberry Edge connection, Status/Service shows Network Available then Data Tunnel Available and finally "Not Connected". During the process I can see an IP address in the Identity screen."
Appreciate your instructions but I just don't think it works. I've tried several different versions of the BC software, no cigar.
Click to expand...
Click to collapse
Same behaviour on a cooked ROM on P3450 - exactly the same.
German O2 Orbit 2 will support BBC in May. This is what someone from O2 told me. BBC software sends the PDA ID (Pola200) the OS version and the carrier to RIM. If your PDA is not supported by RIM you'll get " pin pending".
So we have to wait.