Java Location Services is not part of the basic JME package. It's a JSR extension. Not all hardware supports it, so you need to check the specs from your hardware vendor to see if JSR-179 support comes with the device you're interested in.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Oct 30, 2010
Thank you for your reply. Forgive me if my question seems stupid.. Actually I am working for the first time on Eclipse and just have the basic knowledge of JAVA.
i just wanted to ask if JSR-179 is not supported by my module, the TC-65, then what should I do??? Is there any alternative so that I can extract the location using my TC-65?
I don't think it has GPS capabilities, so location services would only be possible using the cruder method of trilaterialization, and then only if the carrier provided that service. Since the main intent of the device is to provide an Internet connection or telephone services to fixed attached systems, it wouldn't be expecting its location to change very often.
So you apparently have no software because there's no hardware support for location services on this unit. In theory you could plug in an external GPS device, but you'd have to provide your own drivers. Many GPS devices present themselves as serial ASCII communications devices, so you could use the standard file/serial I/O (java.io) classes to track position without using the javax.microedition services.
Joined: Oct 30, 2010
Sorry Tim, I am actually working on HCP65-G. Its a Quad band GSM Modem with GPS Receiver. I am attaching the whole code. If you have a look at it, maybe you can find some error.
Helpful hint: if you use the "Code" button on the message editor to wrap code samples, they'll be more readable.
Just because a Java device supports GPS doesn't mean it supports JSR-179. They may have their own proprietary API for location services. Quite a few manufacturers do. I'd check with the manufacturer and see how they recommend using their GPS from Java code.
subject: javax.microedition.location can not be resolved