Open GoogleCodeExporter opened 9 years ago
I really do need more info than this to investigate it, sorry! You will need to
give debug output, device names, versions, location state, library version -
basically what you'd expect an end user to provide when you need to investigate
something. Cheers!
Original comment by ken...@kentonprice.com
on 9 May 2014 at 10:01
Device is samsung TAB 3
os- Jealybean
version 4.1.2
problem
Always take latitude and longitude as -2134.37878,-2345.989898 like that
where my current location should be 20.0000,73.7800.
location : nashik,Maharashtra, India
Original comment by vijayweb...@gmail.com
on 9 May 2014 at 11:30
Same issue here with a galaxy s4 4.1.2.
Same code works on Nexus4, nexus5, LG....... using jar version v15.
The broadcast receiver doesn't get any intent.
IntentFilter intentFilter = new IntentFilter();
intentFilter.addAction(LocationLibraryConstants.getLocationChangedPeriodicBroadcastAction());
CustomLocationManager.startAlarmAndListener(sBaseContext.getApplicationContext());
sBaseContext.getApplicationContext().registerReceiver(mLocationBroadcastReceiver, intentFilter);
Having this BradcastReceiver:
private static class LocationBroadcastReceiver extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent) {
if (intent.getAction().equals(LocationLibraryConstants.getLocationChangedPeriodicBroadcastAction())) {
broadcastedLocationInfo = (LocationInfo) intent.getSerializableExtra(LocationLibraryConstants.LOCATION_BROADCAST_EXTRA_LOCATIONINFO);
}
}
}
Original comment by marcos.h...@gmail.com
on 14 May 2014 at 3:28
Thanks for the info. Will get back to you.
Original comment by ken...@kentonprice.com
on 14 May 2014 at 3:39
Same here. I tried in a emulator and a real device (s4 4.2.2) and got the same
-2134.37878,-2345.989898
However, on the real device this value changed when i went to google maps and
requested a location update using the google maps button (on the screen). The
value is updated only when I go to google maps and hit the button. So I guess
either this is a bug or I missed something to force location update :S
Original comment by oba...@gmail.com
on 25 May 2014 at 2:42
Original issue reported on code.google.com by
vijayweb...@gmail.com
on 9 May 2014 at 9:43