tlaukkanen / mobile-trail-explorer

Automatically exported from code.google.com/p/mobile-trail-explorer
2 stars 0 forks source link

Never Gets GPS Fix on JSR-179 Compatible Phone #193

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I considered posting this on the Google Group, but figured there was a good 
chance it would 
eventually turn into an open issue. So here goes:

I'm attempting to get MTE working on a Motorola i425. The i425 is MIDP 2.0 and 
CLDC 1.1 along 
with JSR-179 compatible. Here's what I've done so far:

* Loaded the app into the phone.
* Launched it and enabled "Use JSR 179" under the development menu
* Chose the JSR-179 API device under the GPS menu
* Exited the menu and pressed the start/stop button. The status changes to 
recording, but the 
phone never gets a GPS fix (left it outside with a clear view of the sky for 
30+ minutes).

I checked the Log from the developer menu and found an exception from 
Controller.searchDevices regarding no Bluetooth found. The i425 does not have 
Bluetooth. Since 
I'm using the internal GPS, I'm assuming that MTE should work regardless? Is it 
possible that the 
bluetooth exception is short circuiting the app's use of the JSR-179 API?

Also, I tested Instamapper on the phone (instamapper.com) and was able to get 
it to work. Out of 
curiosity (I'm not a J2ME dev), I compared the permissions in the JAD files of 
the Instamapper 
app and MTE. I saw that MTE was not requesting permission to 
javax.microedition.io.Connector.http, javax.microedition.location.Location, or 
javax.microedition.io.Connector.socket while the Instamapper app was, so I 
modified MTE's JAD 
thus: 

MIDlet-1: 
MobileTrailExplorer,/images/explorer.png,com.substanceofcode.tracker.MobileTrail
ExplorerMidl
et
MIDlet-Description: Application for recording trails using GPS device.
MIDlet-Icon: /images/explorer.png
MIDlet-Info-URL: http://www.substanceofcode.com
MIDlet-Jar-Size: 247655
MIDlet-Jar-URL: MobileTrailExplorer.jar
MIDlet-Name: MobileTrailExplorer
MIDlet-Permissions: javax.microedition.io.Connector.file.write, 
javax.microedition.io.Connector.file.read, 
javax.microedition.io.Connector.http, 
javax.microedition.location.Location, javax.microedition.io.Connector.socket
MIDlet-Permissions-Opt: javax.microedition.io.Connector.bluetooth.client
MIDlet-Vendor: Tommi Laukkanen
MIDlet-Version: 1.14
MicroEdition-Configuration: CLDC-1.1
MicroEdition-Profile: MIDP-2.0

Then reloaded the app. Unfortunately, it's still not working.

I really appreciate any help you can lend. I'm building a cool showcase app 
with MTE at 
http://drinkcrackcoffee.com (currently stuck with Instamapper's app which only 
posts GPS 
coords every 1-3 minutes).

Original issue reported on code.google.com by jed.h...@gmail.com on 5 Aug 2009 at 11:08

GoogleCodeExporter commented 9 years ago
Oops, forgot to add that I'm using MTE 1.14, though I guess that could be 
gathered from the MIDlet.

If someone has a link to a JAD/JAR of the latest trunk, I'd love to give it a 
try. I could also build it myself, but I'm 
not a Java dev and so it would take much longer than someone throwing me a bone 
:)

Original comment by jed.h...@gmail.com on 5 Aug 2009 at 11:13

GoogleCodeExporter commented 9 years ago
You can get nightly builds from: http://law.hostsen.net/mte/nightly/

Original comment by gdjo...@gmail.com on 11 Aug 2009 at 8:08

GoogleCodeExporter commented 9 years ago
hi, the nightly builds seem to have stopped end of july...  is there another 
link from which a more recent nightly 
build can be downloaded?

thanks, d.

Original comment by danny.de...@gmail.com on 15 Nov 2009 at 10:41

GoogleCodeExporter commented 9 years ago
can confirm this, slecting the internal gps is hopeless....

it wont ever get a position!

Original comment by peter.ru...@googlemail.com on 1 Jun 2010 at 9:42

GoogleCodeExporter commented 9 years ago
I can just agree to the above. I can't get the internal GPS working, following 
the steps from the users guide. I can see that the GPS gets a fix from the 
satellite icon on the phone, but MTE does not seems to read it. 

Any clues?? Thanks!

Original comment by LindbomJ...@gmail.com on 31 Oct 2010 at 9:26