Bug 5414 - In Airplane more LocationManager doesn't fire any event
Summary: In Airplane more LocationManager doesn't fire any event
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-30 12:43 UTC by Ian
Modified: 2013-05-23 14:00 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Ian 2012-05-30 12:43:23 UTC
On an Android 2.2 device enable Airplane mode.

Use this code to start the location Manager. None of the ILocationListener events ever fire. Turn off Airplane mode and it works perfectly.

				var cr = new Criteria ();
				cr.Accuracy = Accuracy.Coarse;
				cr.PowerRequirement = Power.Low;
				cr.AltitudeRequired = false;
				cr.BearingRequired = false;
				cr.SpeedRequired = false;
				cr.CostAllowed = true;
				string serviceString = Context.LocationService;
				locationManager = (LocationManager)GetSystemService (serviceString);
				var bestProvider = locationManager.GetBestProvider (cr, false);
				locationManager.RequestLocationUpdates (bestProvider, 5000, 500f, this);

		public void OnLocationChanged (Location location)
			Log.Debug ("DEBUG", "OnLocationChanged");
			myLocation = location;
			locationManager.RemoveUpdates (this);

		public void OnProviderDisabled (string provider)
			GoeLocationReceived ();
			Log.Debug ("DEBUG", "OnProviderDisabled");

		public void OnProviderEnabled (string provider)
			Log.Debug ("DEBUG", "OnProviderEnabled");

		public void OnStatusChanged (string provider, Availability status, Bundle extras)
			Log.Debug ("DEBUG", "OnStatusChanged"); 
Comment 1 Jonathan Pryor 2013-05-23 14:00:49 UTC
This appears to be device-specific behavior: