12-16-2008 10:04 PM
12-16-2008 10:37 PM
You might have just put your finger on something - the GPS app I'm working on *does* require RRT, probably due to some other secure API's.
Take a look at KB article DB00591 and see what you think about it.
12-17-2008 03:17 PM
Could you try including some code for a library that requires RRT and see if that fixes the problem? I don't have signing keys yet, but if that is the trick, then I will get some.
12-17-2008 05:34 PM
12-18-2008 01:48 AM
OK! We're getting somewhere. I'm still not getting getting a GPS fix, but I'm no longer getting "GPS not allowed"! So here's where I'm at. I have a BlackBerry Storm with GPS. The Criteria I'm using are:
Criteria criteria = new Criteria();
The location provider is initialized like:
I am on the Verizon network.
What am I doing wrong? I suspect I'm mis-assigning my criteria, or my timeouts are wrong for my location provider.
12-18-2008 02:58 AM
12-18-2008 03:04 AM
12-18-2008 09:10 AM
12-18-2008 07:53 PM - edited 12-18-2008 07:53 PM
Your accuracy requirements look too strict. I would set horizontal accuracy to 100m and vertical accuracy to 300m. In fact, I would leave out the accuracy stuff entirely. The defaults should be reasonable.
So, is setting setCostAllowed to false and signing with an RRT key not enough to get a GPS fix on BB Storm? Did anyone get it to work?
Keep in mind that with autonomous GPS getting a fix will take at least 40 seconds and you have to be outside and have a good view of the sky.