[CMatthews]

Originally Posted by PDADoc

Wirelessly posted

Okay, I have to ask: what's the big deal about Visual Voicemail anyway?

I keep seeing posts about it like it's the greatest thing to come along. Yes, I know what it is, I have an iPhone 3G sitting in my desk drawer somewhere, I just don't see the big deal.

Someone care to clue me in?

Greatest advantage I see is that you can actually pick which voicemail you want to listen to without having to skip they others.

[MidnightDraven]

Originally Posted by wibbly

.216 is now official from T-Mobile UK

http://updateservice.t-mobile.net/

awesome! thanks for that. i'd have never known otherwise.

good to see t-mobile are a bit better with their OS updates for BB than for Nokia N95

[hboogz]

Has anyone tried this update on an ATT BOLD in the Northeast, specifcally NY ?

I just got my hands on the BOLD and, although haven't had any real issues with the phone as of yet, i keep hearing negative things about .167 and i'd rather not wait for them to surface.

Anyone apply this update successfully on a ATT Bold ? If so, any abnormal side affects ?

[Crupp]

I am in Atl and have no bad side effects. Actually before the update my Bold would go between EDGE and 3g almost constantly and now not so much. Can't speak to the battery since while at my desk it is plugged in. Device does seem a bit snappier too.

[Crupp]

Originally Posted by jimfraser

By the way, I did need to have a new password generated for enterprise activation when going to .216. As noted in a previous post by another contributor, others on BES were automatically reactivated on the server when going to .216. As noted in my earlier post, I did not need reactivation on three previous OS updates. I do not know why some OS updates required reactivation for me and others did not.
My caution remains, if on BES you cannot predict if an OS upgrade will require reactivation, so only do it if you know your IT people are available to reactivate/generate a new password, if required.

If you are connected to your network you can activate the BES functionality through the email settings in DM. I never knew this until the guy at RIM told me

[PDADoc]

Originally Posted by hboogz

Has anyone tried this update on an ATT BOLD in the Northeast, specifcally NY ?

I just got my hands on the BOLD and, although haven't had any real issues with the phone as of yet, i keep hearing negative things about .167 and i'd rather not wait for them to surface.

Anyone apply this update successfully on a ATT Bold ? If so, any abnormal side affects ?

My device is an AT&T Bold, and as you can see from my profile, I'm in Manhattan. I've not experienced any severe abnormalities associated with the updating process, per se. Each OS update has its own peculiar set of positives and negatives. I was on .216 but didn't like a few things about it (see earlier in this thread for my remarks) but I'm now using .185 and while there is slightly less file free memory, it's working just fine, I'm satisfied.

I should point out, however, that there was nothing wrong with my device when I had .167.

[mjbanks]

I'm skipping this OS. Haven't heard too much good about it and .190 has been working great for me. I'll wait for one that's a bit more stable.

[hboogz]

Thanks for the replys, everyone.

I'm in Manhattan as well, well most of my time at least.

Since it's brand new and i'm not that invested in the customization part of it yet, I'll be the guinea pig and give this AVEA version a shot.

I'll report back with my results..

[hboogz]

Originally Posted by Crupp

If you are connected to your network you can activate the BES functionality through the email settings in DM. I never knew this until the guy at RIM told me

How exactly can you do that using DM ?

[Crupp]

Originally Posted by hboogz

How exactly can you do that using DM ?

Connect your Blackberry open DM, go email settings, make sure "forward incomming messages to my device" is checked, (under general), under advanced - your email address should be populated and greyed out, click apply. You should then see the EA icon on your Bold and information being sent via the USb cable.

I was previously connected to the BES before I upgraded to .216. This worked for me (via the RIM guy telling me about it) going from .167 to .216

[jimfraser]

Originally Posted by Crupp

Connect your Blackberry open DM, go email settings, make sure "forward incomming messages to my device" is checked, (under general), under advanced - your email address should be populated and greyed out, click apply. You should then see the EA icon on your Bold and information being sent via the USb cable.

I was previously connected to the BES before I upgraded to .216. This worked for me (via the RIM guy telling me about it) going from .167 to .216

Thanks for the tip.
My IT guy gets somewhat anoyed. No one else in the firm upgrades the OS on their Blackberrys (we use a variety of Blackberrys).
I needed reinitialization with a new password for .167 and .216, but not for three previous upgrades (the first one was from original Rogers to .162, and recommended by Rogers so I got in the habbit of upgrading to the latest OS), which reinitialized automatically over the air.

[hboogz]

Originally Posted by Crupp

Connect your Blackberry open DM, go email settings, make sure "forward incomming messages to my device" is checked, (under general), under advanced - your email address should be populated and greyed out, click apply. You should then see the EA icon on your Bold and information being sent via the USb cable.

I was previously connected to the BES before I upgraded to .216. This worked for me (via the RIM guy telling me about it) going from .167 to .216

Strange little trick, but that seemed to have worked.

I'm currently on an ATT BOLD IN NYC running .216 and everything seems to going well so far.

I've downloaded poynt and just recently noticed retrieving a GPS signal, but could be related to my location within the office.

All is good so far.

[IS300_TRD]

Weird.

I just updated my OS to .216 a couple of hours ago. All of a sudden it just reset itself.

[kenv]

I am using 210, which works pretty well overall. But my Bluetooth Motorola H15 headset frequently doesn't work during a call, even though it is shown to be connected. This often happens after making one call, hanging up, then making another call, and the BT doesn't work during the second call. I have to close then open the BT, and then it works again. I have actually replaced the H15 device this week for other reasons, but the new one is doing the same thing.

Does anyone know if this is an OS related issue, and if so, will 216 fix it?

Thanks.

[GolfnCPA]

Originally Posted by kenv

I am using 210, which works pretty well overall. But my Bluetooth Motorola H15 headset frequently doesn't work during a call, even though it is shown to be connected. This often happens after making one call, hanging up, then making another call, and the BT doesn't work during the second call. I have to close then open the BT, and then it works again. I have actually replaced the H15 device this week for other reasons, but the new one is doing the same thing.

Does anyone know if this is an OS related issue, and if so, will 216 fix it?

Thanks.

H15 with .185 is working very well. On occasion, it takes a couple of passes to link up, but I have never had any trouble with it during a call.

[kenv]

Originally Posted by GolfnCPA

H15 with .185 is working very well. On occasion, it takes a couple of passes to link up, but I have never had any trouble with it during a call.

Thanks. Just to clarify, there is no problem with the H15 /during/ a call. What usually happens is that the device seems to be working well during a call, the call is ended, and when I attempt to make another call, with the H15 still showing as connected on the Bold, the call can be heard only on the Bold speaker, not on the H15. I then have to shut the H15 down and restart it, and then it works again when I make a call. It's as if the BT device "forgets" that it is connected after a call is completed.

[GolfnCPA]

Originally Posted by kenv

Thanks. Just to clarify, there is no problem with the H15 /during/ a call. What usually happens is that the device seems to be working well during a call, the call is ended, and when I attempt to make another call, with the H15 still showing as connected on the Bold, the call can be heard only on the Bold speaker, not on the H15. I then have to shut the H15 down and restart it, and then it works again when I make a call. It's as if the BT device "forgets" that it is connected after a call is completed.

What are your settings for Bluetooth?

Manage Connections > Bluetooth Options > Menu > Options

[kenv]

Originally Posted by GolfnCPA

What are your settings for Bluetooth?

Manage Connections > Bluetooth Options > Menu > Options

The settings are as follows:

Discoverable--Yes
Allow outgoing calls--always
Contacts --All Entries
LED connection indicator--On
Security Level--High
Connect on Power Up--Yes

And all the "services" have a check in the box

[GolfnCPA]

Originally Posted by kenv

The settings are as follows:

Discoverable--Yes
Allow outgoing calls--always
Contacts --All Entries
LED connection indicator--On
Security Level--High
Connect on Power Up--Yes

And all the "services" have a check in the box

Change a couple of options.

Discoverable--No
Contacts--Disabled
Connect on Power Up--No.

Reboot, and see if it works. Just telling you what mine looks like, and as stated, no problems.

[kenv]

Originally Posted by GolfnCPA

Change a couple of options.

Discoverable--No
Contacts--Disabled
Connect on Power Up--No.

Reboot, and see if it works. Just telling you what mine looks like, and as stated, no problems.

OK, will do--thanks very much. I'll post again if there are any further disconnects.