Originally Posted by AxelE
Returning to the installation of GpsTrack ...
Tried to install the jar file OTA. It seems to be installed, but once I start I receive:
"Error starting GpsTrack: Module 'GpsTrack' attempts to access a secure API"
Getting this GPSTrack to work on my Pearl seems to be my mission
lately but I can't seem to get past the Secure API error that was
posted by others. I have tried installing the software every which
way but Sunday...then I even tried Sunday and that didn't work. I
even, thanks to the help of other forum members, obtained a copy of
the GpsTrack.cod file that a person that had it working downloaded
with javaloader to see if maybe it was a version issue. I have lots
of data that maybe someone smarter then me (not hard to find) can
help get me to the next level with as I am at a roadblock.
First, my specs:
T-Mobile BB8100 Software version TMO 4.2.064 on BES with unrestricted
policy that I control so if you think it is something with the BES
policy let me know as I control the policy for my BES and can change
it to test ideas and theories but I have tried everything I can find
to fix this problem.
Now for some interesting notes/findings in all my research. I will
start with the theory it could be policy related.
Policy Related Theory:
In Application Permissions I have the default permissions set to
Allow everything listed including Bluetooth, GPS, etc. and the same
settings as default for the modules by using the handheld Application
Permissions option under Security Options. I then view the
properties of the Application and see basic info about the app.
However, when look at the properties of the GpsTrack module I see a
laundry list of Policy Restrictions including the following:
Event Injector API
Bluetooth Serial Profile
Handheld Key store
Key Store Medium Security
Oh yeah and it is not a signed app as you can probably guess. Now
that all being said I have other unsigned apps that have not Policy
Restrictions, in fact no other module on my BB signed/unsigned has
any restrictions listed at all. If anyone has any ideas of why this
one app has all of these restrictions I am open to trying some
different approaches as I have tried 507ing my BB to make sure it
wasn't an app causing the problems.
My second theory is that it has something to do with my version of
the Handheld software and the application. Below is my application
not coded for my version of software based on my latest discovery
with another app.
HandHeld Software version and GpsTrack coding not compatible:
Here is what I learned, I recently tried to install the J2ME Map
software from the wap.landspurg.net page and accidentally installed
the CLDC 1.1 instead of the CLDC 1.1 minimum version. Interesting
enough I got the same error ("Secure API attempt") and when looking
at the Modules it had the same policy restrictions. Very interesting
because when I reloaded the CLDC 1.1 minimum version I got no errors
and in the Module properties there are no Policy Restrictions listed
but the J2ME Maps application has a problem with being able to select
the Use Bluetooth option in Param to make it useful, they say it is a
Pearl (trackball) issue but that is for a seperate topic.Now I am not
a programmer by any means but with this information I am hoping again
that maybe someone knows the difference between the CLDC1.1 and CLDC
1.1 minimum and can help. The source code for GpsTrack is available
on the developers website so if anyone is gracious enough to look at
the code, make some updates I am more than willing to help test any
mods if a .jar is posted for OTA or the .cod is provided for
Application Loader installation.
Thanks to anyone out there that thinks they can help!!!