[hal1]

Summary for me: Standard Maps work, Google maps not so much - just the cell tower thing.

Maybe I am making progress, when I press the blue dot to center to my location, Google maps says "your location within 1700, meters, GPS temporarily unavailable". Maybe there is hope.

Oh well.

[xxraffyxx]

I posted this on another thread:

I installed nav4all (nav4all.com) and the GPS works! and tracks my movement perfectly. Voice turn by turn directions! for free.

BUT!!! the app is not made for the storm. very hard to navigate thru the storm.

but with that said... google just needs to update(fix) their app and they will have access to GPS!

according to nav4all:
GPS is unlocked
AGPS is locked

[eth555]

I posted this on another thread:

I installed nav4all (nav4all.com) and the GPS works! and tracks my movement perfectly. Voice turn by turn directions! for free.

BUT!!! the app is not made for the storm. very hard to navigate thru the storm.

but with that said... google just needs to update(fix) their app and they will have access to GPS!

according to nav4all:
GPS is unlocked
AGPS is locked

There is hope then!!! I really want Google maps to work!

[scougarb]

Has anyone made any progress with Google Maps? I tried uninstalling it and then pushing it out from our BES to see if that made any difference, but it didn't. One thing I did notice though when I was creating the software configuration in BES was that one of the files in the zip file that I downloaded from google was specifically for 4.7 so we at least know that google is aware of the storm and the existence of it didn't catch them by surprise.

[imann101]

we should all just e-mail them to fix it. I made a thread the other dayw ith the link to send them an e-mail

[mtbighorn]

My $.02 ...

You asked for a developers opinion so here goes nothing ...

Let me preface this with I intend to dig into the SDK from RIM this afternoon and that may shed some more light.

Here I have the two logs trimmed to show only calls made to the location api.

Google Maps

i Location API - Stop GPS -  process removed and all GPS session terminated for mode:1 - 11/23 00:57:34
i Location API - Stop GPS - application:287 with mode:1 - 11/23 00:57:34
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:33
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:32
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:31
i Location API - GPSListener - GPS Unavailable Notification - error:1 - 11/23 00:57:31
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:30
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:30
i Location API - Start GPS - single fix with no existing GPS session:287 - 11/23 00:57:30
i Location API - Authenticating application:287 - 11/23 00:57:30
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:30
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:30
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:29
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:1 - 11/23 00:57:28
i Location API - Stop GPS - application:287 with mode:1 - 11/23 00:57:28
i Location API - Last GPS error - value for:287 is:1 - 11/23 00:57:28
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:28
i Location API - Restart GPS - value for mode:1 - 11/23 00:57:28
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:28
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:28
i Location API - Start GPS - single fix with no existing GPS session:287 - 11/23 00:57:28
i Location API - Authenticating application:287 - 11/23 00:57:28
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:28
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:28
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:27
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:1 - 11/23 00:57:26
i Location API - Stop GPS - application:287 with mode:1 - 11/23 00:57:26
i Location API - Last GPS error - value for:287 is:1 - 11/23 00:57:26
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:26
i Location API - Restart GPS - value for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:26
i Location API - Start GPS - single fix with no existing GPS session:287 - 11/23 00:57:26
i Location API - Authenticating application:287 - 11/23 00:57:26
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:26
i Location API - Restart GPS - value for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:26
i Location API - Start GPS - Multiple fix for application:287 with mode:1 - 11/23 00:57:26
a Location API - Application must set valid PDE IP and Port to get Location - 11/23 00:57:26
i Location API - Authenticating application:287 - 11/23 00:57:26
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:26

BB Maps

i Location API - Stop GPS - process not registered and all GPS session terminated for mode:2 - 11/23 01:04:34
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:04:34
i Location API - Stop GPS - process not registered and all GPS session terminated for mode:2 - 11/23 01:04:34
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:04:34
a LBS - removing listener: net.rim.device.apps.internal.lbs.MapScreen@2c44895d - 11/23 01:04:28
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:2 - 11/23 01:04:28
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:04:28
i Location API - Start GPS - Multiple fix for application:291 with mode:2 - 11/23 01:03:48
i Location API - Starting location update for:291 and mode:2 - 11/23 01:03:48
i Location API - Stop GPS - process not registered and all GPS session terminated for mode:2 - 11/23 01:03:48
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:03:48
a LBS - LProvider Type: 2 - 11/23 01:03:48
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:2 - 11/23 01:03:47
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:03:47
a LBS - using LAPI - 11/23 01:03:47
i Location API - Start GPS - Multiple fix for application:291 with mode:2 - 11/23 01:03:43
i Location API - Starting location update for:291 and mode:2 - 11/23 01:03:43
a LBS - LProvider Type: 2 - 11/23 01:03:43
a LBS - adding listener: net.rim.device.apps.internal.lbs.MapScreen@2c44895d - 11/23 01:03:43
a LBS - using LAPI - 11/23 01:03:43
a LBS - using LAPI - 11/23 01:03:41

What I think is important here is that the device is requesting some kind of authentication from the software before it grants access to gps. In the log from google maps the invalid credentials exception is thrown several times, and in the BB Maps log we dont see that exception (we also dont see that the software succeeded in authenticating itself which I will research later).

The first exception we see occurs when google maps (and this is only a guess) tries to create an event listener that will notify google maps when data from the internal gps changes (this could be anything from position to device status) I have a hunch that prior to creating a listener like this (or as part of the actual creation process) that the device requires some kind of credentials that can likely be obtained from the device itself. If that really is the case then it will fall in googles court.

If anyone has any need for a more technical description of what I find in the RIM sdk then reply or pm me.

[alan8385]

When I turn on google maps it says "waiting for gps" then after a couple seconds it gives me my location. it's off by .5-1 mile... am i to believe that mine is not functioning correctly?

[mtbighorn]

You are experiencing the same as the rest of us. Your location is being calculated using triangulation from the towers and not the satellites.

[alan8385]

The satellite should be pretty exact right?

[mtbighorn]

GPS is accurate to ~ 3 meters

[albertdc]

Even if google maps is locating via cell tower triangulation at this point, I would still like to get it to work well/easily because it displays traffic info which BB maps does not. I could see myself using BBmaps for true navigation but checking google maps for traffic.
That being said - what is the best way to get google maps on the storm? I am a blackberry noob, so maybe I'm missing something. I tried going to maps.google.com in the browse, but the view is not pretty nor is that fast. I downloaded google maps yesterday from m.google.com for backberries, but it is not verry usable in that I can't manipulate the menus like you guys are doing. What have I missed. Instruction on the best way of getting google maps would be greatly appreciated.

As an aside, I can confirm that GPS can run independantly with a 3rd party app - it worked beautifully for me yesterday for GolfTraxx. It gives very accurate distance to the front, middle, and back of the greens (checked against markers on the course and my brothers SkyCaddie). I had already deleted VZNav, so I am sure that was not running in the background...

[alan8385]

Even if google maps is locating via cell tower triangulation at this point, I would still like to get it to work well/easily because it displays traffic info which BB maps does not. I could see myself using BBmaps for true navigation but checking google maps for traffic.
That being said - what is the best way to get google maps on the storm? I am a blackberry noob, so maybe I'm missing something. I tried going to maps.google.com in the browse, but the view is not pretty nor is that fast. I downloaded google maps yesterday from m.google.com for backberries, but it is not verry usable in that I can't manipulate the menus like you guys are doing. What have I missed. Instruction on the best way of getting google maps would be greatly appreciated.

As an aside, I can confirm that GPS can run independantly with a 3rd party app - it worked beautifully for me yesterday for GolfTraxx. It gives very accurate distance to the front, middle, and back of the greens (checked against markers on the course and my brothers SkyCaddie). I had already deleted VZNav, so I am sure that was not running in the background...

go to google.com/gmm on your phone to download the app. it should not be very slow and the menu is self explanatory after hitting the menu key

[mythicninja]

google maps is using cell tower triangulation... Not very acurate says to 2800 meters or something like it... Hopefully when it is officially released for the storm that it can change... BBmaps works great though.

[slimjimp]

OK I have a question that no one seemed to have answered...when I dl google maps it only comes up half screen and the other half is the keyboard....is anyone able to get a full screen without the keyboard? I have there is no option to hide the keyboard and I cant swipe down to hide the keyboard either...

[scougarb]

OK I have a question that no one seemed to have answered...when I dl google maps it only comes up half screen and the other half is the keyboard....is anyone able to get a full screen without the keyboard? I have there is no option to hide the keyboard and I cant swipe down to hide the keyboard either...

Sounds like you Compatibility Mode enabled on Google Maps
Options > Advanced Options > Applications > highlight Google Maps > press the menu button > choose 'Disable Compatibility Mode'

[slimjimp]

Sounds like you Compatibility Mode enabled on Google Maps
Options > Advanced Options > Applications > highlight Google Maps > press the menu button > choose 'Disable Compatibility Mode'

THANK YOU!!!!! Been trying to figure out for some time now...

[timberdc]

Has anyone tried MS Live search, by any chance?

[albertdc]

go to google.com/gmm on your phone to download the app. it should not be very slow and the menu is self explanatory after hitting the menu key

thanks - that's basically what I did the first time, but this time it definitely downloaded a different version which works great - the triangulation is not great, but now I can look at the traffic patterns. I used BBmaps on Saturday and searched for stores in my area and was impressed with the ease of use. I also love that you can search for an address in your contacts.

[banggooooo]

I downloaded google maps when I got my storm but deleted it because i head there was a newer version out. But when i went back to the m.google.com/gmm site, I can't seem to download the application again. Instead of the link to "install now" (which I can see if I go to the link on my laptop) it just gives me a link for "visit now".

I even tried downloading the .jad file onto my laptop and sending it as an attachement to my storm. I was able to open the file but upon installation it failed.

Anyone have this problem?

[D_Dog]

I would be very surprised if someone from Google isn't a regular member in these forums. NDA'a aside, why won't someone from Google give us an answer on this? It would be so simple for them to just say: "Yes, Google mobile maps GPS functionality will work on the Storm, we are working hard to get an update out soon." or "No, Google mobile maps GPS functionality will not work on the Storm, it is not in our control to change this."
This would end the rumors once and for all. So what is it Google?

[PC101]

I would be very surprised if someone from Google isn't a regular member in these forums. NDA'a aside, why won't someone from Google give us an answer on this? It would be so simple for them to just say: "Yes, Google mobile maps GPS functionality will work on the Storm, we are working hard to get an update out soon." or "No, Google mobile maps GPS functionality will not work on the Storm, it is not in our control to change this."
This would end the rumors once and for all. So what is it Google?

We are working on it. Should be out in January.

[dms936]

I would be very surprised if someone from Google isn't a regular member in these forums. NDA'a aside, why won't someone from Google give us an answer on this? It would be so simple for them to just say: "Yes, Google mobile maps GPS functionality will work on the Storm, we are working hard to get an update out soon." or "No, Google mobile maps GPS functionality will not work on the Storm, it is not in our control to change this."
This would end the rumors once and for all. So what is it Google?

If you follow the links to the Google Maps Help pages, Google has already confirmed that they are working on a solution for the Storm..

Judging from their response they might have some slick Storm-specific features up their sleeve for us.

[jh0]

Here's the answer in google groups from a google employee

===========http://preview.tinyurl.com/5ootl8============

[DAS112463]

i live in germany and goggle maps work to within 10 meters of my location. we could use this info for a smart bomb.

[nick125]

My $.02 ...

You asked for a developers opinion so here goes nothing ...

Let me preface this with I intend to dig into the SDK from RIM this afternoon and that may shed some more light.

Here I have the two logs trimmed to show only calls made to the location api.

Google Maps

i Location API - Stop GPS -  process removed and all GPS session terminated for mode:1 - 11/23 00:57:34
i Location API - Stop GPS - application:287 with mode:1 - 11/23 00:57:34
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:33
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:32
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:31
i Location API - GPSListener - GPS Unavailable Notification - error:1 - 11/23 00:57:31
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:30
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:30
i Location API - Start GPS - single fix with no existing GPS session:287 - 11/23 00:57:30
i Location API - Authenticating application:287 - 11/23 00:57:30
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:30
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:30
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:29
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:1 - 11/23 00:57:28
i Location API - Stop GPS - application:287 with mode:1 - 11/23 00:57:28
i Location API - Last GPS error - value for:287 is:1 - 11/23 00:57:28
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:28
i Location API - Restart GPS - value for mode:1 - 11/23 00:57:28
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:28
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:28
i Location API - Start GPS - single fix with no existing GPS session:287 - 11/23 00:57:28
i Location API - Authenticating application:287 - 11/23 00:57:28
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:28
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:28
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:27
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:1 - 11/23 00:57:26
i Location API - Stop GPS - application:287 with mode:1 - 11/23 00:57:26
i Location API - Last GPS error - value for:287 is:1 - 11/23 00:57:26
i Location API - getLocation:Invalid credential for application:287 - 11/23 00:57:26
i Location API - Restart GPS - value for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:26
i Location API - Start GPS - single fix with no existing GPS session:287 - 11/23 00:57:26
i Location API - Authenticating application:287 - 11/23 00:57:26
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:26
i Location API - Restart GPS - value for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS retrieval Error:-1 for mode:1 - 11/23 00:57:26
i Location API - GPSListener - GPS Error:1 for mode:1 - 11/23 00:57:26
i Location API - Start GPS - Multiple fix for application:287 with mode:1 - 11/23 00:57:26
a Location API - Application must set valid PDE IP and Port to get Location - 11/23 00:57:26
i Location API - Authenticating application:287 - 11/23 00:57:26
i Location API - Starting location update for:287 and mode:1 - 11/23 00:57:26

BB Maps

i Location API - Stop GPS - process not registered and all GPS session terminated for mode:2 - 11/23 01:04:34
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:04:34
i Location API - Stop GPS - process not registered and all GPS session terminated for mode:2 - 11/23 01:04:34
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:04:34
a LBS - removing listener: net.rim.device.apps.internal.lbs.MapScreen@2c44895d - 11/23 01:04:28
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:2 - 11/23 01:04:28
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:04:28
i Location API - Start GPS - Multiple fix for application:291 with mode:2 - 11/23 01:03:48
i Location API - Starting location update for:291 and mode:2 - 11/23 01:03:48
i Location API - Stop GPS - process not registered and all GPS session terminated for mode:2 - 11/23 01:03:48
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:03:48
a LBS - LProvider Type: 2 - 11/23 01:03:48
i Location API - Stop GPS -  process removed and all GPS session terminated for mode:2 - 11/23 01:03:47
i Location API - Stop GPS - application:291 with mode:2 - 11/23 01:03:47
a LBS - using LAPI - 11/23 01:03:47
i Location API - Start GPS - Multiple fix for application:291 with mode:2 - 11/23 01:03:43
i Location API - Starting location update for:291 and mode:2 - 11/23 01:03:43
a LBS - LProvider Type: 2 - 11/23 01:03:43
a LBS - adding listener: net.rim.device.apps.internal.lbs.MapScreen@2c44895d - 11/23 01:03:43
a LBS - using LAPI - 11/23 01:03:43
a LBS - using LAPI - 11/23 01:03:41

What I think is important here is that the device is requesting some kind of authentication from the software before it grants access to gps. In the log from google maps the invalid credentials exception is thrown several times, and in the BB Maps log we dont see that exception (we also dont see that the software succeeded in authenticating itself which I will research later).

The first exception we see occurs when google maps (and this is only a guess) tries to create an event listener that will notify google maps when data from the internal gps changes (this could be anything from position to device status) I have a hunch that prior to creating a listener like this (or as part of the actual creation process) that the device requires some kind of credentials that can likely be obtained from the device itself. If that really is the case then it will fall in googles court.

If anyone has any need for a more technical description of what I find in the RIM sdk then reply or pm me.

What I've heard is that Google Maps will try to get aGPS, and if that fails, it will fallback to tower triangulation rather than trying standalone GPS. As far as I know, Verizon still locks down the aGPS by using an authentication key that is provided to a GPSSettings call. Here's a link to a RIM KB article describing Verizon's method of authenticating aGPS applications at the bottom: Livelink - Redirection