I tried a BT GPS and the internal GPS on my 8130 and had no problems with either.

Just downloaded and installed it (8830 verizon) pretty neat. Would be nice if it actually used the real GPS in the phone (damn verizon :( ).

Works on my 8830 with Freedom puck

And I agree - Verizon needs to reexamine its lock out policy on gps. (might as well, apply negative pressure any chance there is so maybe the "bad press" will eventually work????)

Ok...found out the issue. Apparently OS 4.5 doesn't play well with BES v4.1.3. When activated on BES 4.1.3 the permissions get all screwed up. It's said to be fixed in BES 4.1.4. I can downgrade to 4.2.2 and it'll all work fine but not with 4.5.

So, anyone having trouble with Google Maps, on OS 4.5 and on a BES 4.1.3, don't bother with Google Maps v2.0.0 or higher.

Loving 2.10 on a 8310, uses internal GPS fine and loads / refreshers faster than 2.0x

John,

We've got BES 4.1.5 and Google Maps gets the same hang up when accessing Radio Information using 4.5.0.18.

Any ideas on how to fix it?

Eh...that's disheartening. I've been prodding my BES Admin to upgrade to 4.1.5 in hope of fixing this issue. There is no fix that I'm aware of and RIM is aware of the problem. I guess we just wait.

If you have any ideas on permissions or BES policy to try and fix it, I can make some attempts.

Are you able to change the permissions to Allow for Location (GPS) in the Application Permissions?

when you say 2.10 .. do you mean 2.0.1 ???
(if so, yes, that 2007 version works the best with my 8310 as well)

No, 2.1.0. It's the latest version of GMM.

No, I only see Prompt or Deny

Wirelessly posted (BB 11020)

Yeah, the "Allow" option is lost when the 4.5 device is activated on the BES. if one uses JL_Cmder to "resettofactory" the device, which wipes the BB along with all IT policy, the option comes back. This isn't affecting everyone on all BES's, though, but its happening to me on BES 4.1.3 (Exchange.) Its not happening on Lotus or Domino BES's. I don't know if that really has to do with why it works for them and not me but its the most obvious difference. It could be the way the policy is setup, too. We only use the default policy and the DST policy that RIM put out There is no workaround that I'm aware of.

I read a few comments about the AT&T 8310 and the newest GMM 2.10 and the "My Location" feature not working with internal GPS after install (NON-BES USER).

I had the same problem when I first installed, or should I say, "updated" to the 2.10 verison. My location would not work with GPS, it would triangulate (dot with the blue shaded circle) and would say within 3000 meters, which was strange cause it normally would be a lot closer within cell range.

Anyway, all I did was go under my blackberry options>advanced options>GPS and selected to refresh GPS and viola! Problem fixed.

It was weird because I had MapQuestNavigator, and that stopped working as soon as I installed GMM 2.10, mapquestnavigator wouldn't pick up any satilites.. Resets and battery pulls did nothing. But as soon as I refresh GPS, everything started working again! Not a problem since.

everything works automatically as soon as satellites are locked in ..
(you get a couple of thousands of meters accuracy before - a couple of meters of accuracy after)

- if you want to you can go and check under application permissions and set all to allow as other posts mention - but by the default permission worked fine in my case.

Curve 8310 on T-Mobile BIS .. v.2.10 worked fine
(i did have to manually change the browser address to Blackberry model 42 as by default for some reason it kept sending me to model 40 that does not work with the 8310's internal GPS)

apart from that initial screen/downloading .. anyother changes? i did not see any ..
(glad to see that the address book add in is still there)

AP.

have just loaded the new version on my AT&T 8310 and works with no problems. But I did to realize that my location is about a 1/4 mile from where I really am located.

JC,

I run BES 4.1.5 on Domino. Still same problem.

Wow....I know another user with 4.1.5. on Domino and it works. I wonder what the deal is?

Nice update. Like the new translucent traffic indicators.