Strange Location API behaviour on a C3-00 without SIM (WeatherApp)

[openskymap]

Hello,
Using weatherapp on a C3-00 without a SIM card, the location API handling has a strange behaviour : the app starts and pops a view outside the app about bluetooth device search (as if it was looking for a GPS connected by BT ?), with Back you come back to the app and it pops cannot find Location (ok this is expected if he can't solve location).

In LocationFinder.java, the handling is ;
no CellIdLocationFinderImpl (because no SIM) -> go to GpsLocationFinderImpl ?
otherwise i should see ViewMaster.VIEW_LOCATIONS if no provider.

[bandarap]

Hello openskymap,

Couldn’t get exactly what you see strange in Location API behavior with WeatherApp.

C3-00 is Series 40 6th Edition (initial release) and don’t have built-in GPS. So, the only ways to get location in C3-00 is with Cell Towers (using SIM) or External GPS connected through your device Bluetooth.

[openskymap]

Hello,

the expected behaviour for me should be : no CellIdLocationFinderImpl (because no SIM) , no GpsLocationFinderImpl (because no internal GPS) -> return null.
The user sees an interface that is not clearly related to the fact that the device is looking for an external BT GPS device ... this should be managed by the developper : ok no internal device, ask if user want to try to connect to external GPS, if yes launch the BT seek.

Thanks

[skalogir]

the expected behaviour for me should be : no CellIdLocationFinderImpl (because no SIM) , no GpsLocationFinderImpl (because no internal GPS) -> return null.

The application's behavior is very similar to what you describe: first it attempts a Cell-Id retrieval, then a GPS retrieval (if the Location API is supported by the device) and finally, if the location API is not supported, the MIDlet is launched in network mode only. C3-00 is 6th Edition as mentioned here, and the device supports the Location API but it doesn't come with a built-in GPS. The second you retrieve the LocationProvider, the series 40 software (and not the API) launches the Bluetooth search. Unfortunately there is no way to know at runtime, if a device that supports the Location API, has a built-in GPS or not, in order to skip the call to the LocationProvider. If you cancel the Bluetooth search or it let it time out, then you get a null value for you LocationProvider instance, and then you can hide all GPS related actions.