IssueTracker

I'm afraid you are going to need to reproduce this on an aosp build such as the emulator to rule out any issues from Samsung.

This apparently is a bug which could be reproduced on different devices, not only Samsung but also HTC, even a Google Nexus (see SO links down this posting).

After some time (hours to days), Android (starting 4.1? 4.2?) just does not call the listener anymore.
Most apps I have running using the NETWORK provider don't get updates after that.
Reboot fixes the issue and all apps seem to find the proper location again.

Checking the providers' getLastKnownLocation().getTime() shows it's very old data.
What's really interesting, that Google Maps actually seems to work. Some would assume that it would not, too; and some would assume the getTime() for the providers lastknown location would get updated, but they still show with old locations and old timestamp.


http://stackoverflow.com/questions/12630413/has-network-provider-behavior-changed-in-android-4-1-1?lq=1
http://stackoverflow.com/questions/13594932/network-provider-not-providing-updated-locations
http://stackoverflow.com/questions/15747543/locationlistener-of-network-provider-is-enabled-but-onlocationchanged-is-never?lq=1

I actually do experience this problem, too, and it's not a real solution to tell my customers "you have to reboot your device".

Regards,
Oliver

We have seen very similar problem in our application. Our problem has happened in
- HTC Desire S (Android 4.0.4)
- two different Samsung Galaxy S3 phones (Android 4.1.2)
- Samsung Galaxy Tab 2 10.1 (Android 4.0.4)

So this is not only Samsung related problem.

In our case the problem has started to occur after 2-10 days after rebooting phone.

For example today I was 50 kilometers from home but it said my location was at home. Then I shut down WLAN and GPS and started Google maps and it showed correct location. After that I checked the location from our app and it said again that my location was at home.

Same problem has happened in:

- Galaxy S2
- Galaxy S2 plus
- Galaxy S3
- Galaxy S4

Regarding the Google Maps; I guess it is using the Google Play Location API. I did some small test app to compare results; the Google Play API does even deliver more accurate results and usually has a slightly different location than using the native Android Location API. The location provider returned by Google Play is named "fused", so it's some internal plugin.
That's most probably the reason Google Maps is still reporting accurate results and does not update the "network" location provider as it simply not uses it.
As soon as my "network" provider does not return anything anymore, I am going to doublecheck if the Google Play API still returns valid results.

Drawback with Google Play API: Only available on >=2.2, only available when latest Google Play installed. For me, can't use...

This is unacceptable.
I have an app on version 2.2 that works great, and on 4.2 i experience this issue.
If there is no fix for this, then they should deprecate the requestLocationUpdates method.
Can someone from google please respond with root cause and fix for this.

In response to #1, this cannot be reproduced on the emulator as the emulator does not support the network location provider.

Side note: Issue 36949180 (http://code.google.com/p/android/issues/detail?id=55896) seems to be very closely connected to this one, but got closed (wrong forum).

I set up a very basic apk which tries to get location using native network provider and Play API; timeouts after 10 seconds: http://www.jav.net/lt/LocationTester.apk
Pressing "Start" button starts to get the location.

After a couple of days without device reboot, "network" provider times out; can see that location age gets really old and not refreshed. Play API still responding with accurate up-to-date locations.

At that time, basically all weather widgets, location-based apps cease to work or report false locations.

I checking status on a number of devices now, including Nexus 7 (Wifi only, at home), Galaxy S3. As I don't own a ASOP Nexus 4 and could use real-world scenario, I'm thinking to put some ASOP build onto my old Galaxy S2 and test it there, too.

It's hard to provide much more information to that topic. Would it help if this apk regulary (each minute?) tries to get position and, if detected timeout/no call to onLocationChanged(), tries to capture the device system log?

Regards,
Oliver

As reported by other users I've tested my application with Sony & HTC devices with Android 4.0.4/4.0.3 as well, The issue replicates and location updates to my registered listeners stop after 3-4 days itself.
After the issue starts coming, re-installation or any setting change doesn't help at all, until we re-boot the device. After device reboots it starts to call the listener with location updates till next 3-4 days.

Finding out no other solution through Android Location APIs, I tried Google Play Service locations and this issue is not faced by the api. And the app runs fine for days without interruption. Though it seemingly has other issue where old version PlayService was working in Android 2.3.7 Sony device but the latest version has broken something and hence the updates fail to reach (It gives some DB Schema error).

Regards
Rishabh

I have the same issue as well. I have an app that notifies the user when they arrive or depart a targeted location. Using NETWORK_PROVIDER in a Service, I connect to my server, and get a list of nearby locations. If there are locations nearby, I remove the listener and switch to the GPS_PROVIDER to double check their location and notify them if they are truly going to that location. We have hundreds of thousands of users who are experiencing this issue in the 4.1.x and 4.2.x software range. In 2.3.x it works great. I see reports all over stack overflow and other sites. I'm hoping that we can come up with a way to fix this issue, even if it is a hack. Right now we are relying only on GPS_PROVIDER and obviously, this sucks down the battery way too fast.

We have used the fused location provider , and it does not retrieve location updates on mobile network.  
We have also tested the sample app (LocationUpdates) shared on developer site and it also has a similat behaviour.
It woks fine only when on wifi or gps.

Tested on following devices
Samsung S3 , S4 and HTC One

Please fix this as the apps rely heavily on location updates.

We are preparing an application (Family Watch), which is heavily dependent on the continuous collection of location data. We really appreciated the possibility offered to us by the newly introduced fused location provider, but as other guys here, we have problem. As soon as the mobile phone is out of GPS and WiFi signal range (e.g. building in country or train). The provider stops give requested updates and until it gets GPS or WiFi it is not invoked (it does ignore the requested polling interval). It is really a shame because the promising tool is simply not possible to use. And frankly this behavior is in contradiction to the promised feature.

We tested also following devices: Samsung Galaxy S (2.3.6), ZTE Skate pro (4.0.4) and SONY Xperia J (4.1.2), Huawei Ascend Y300 with the same results regardless of setting of the priority (PRIORITY_HIGH_ACCURACY or PRIORITY_BALANCED_POWER_ACCURACY). All devices had access to all sources of localization data (GPS AND GOOGLE) in settings.
Google Play services version code 3225100 (Google play version 4.3.11).

I have done some tests with my S3 running 4.1.2

1. Network provider currently does not show updated position.
2. I uninstalled latest Google Play Services app and rebooted - made no difference. The network provider got one lock, but then does not get subsequent locations.
3. I disabled the Google Play Services and rebooted.
4. The network provider now updates locations whenever I move around.
5. Re-enable Google Play Services and update to latest version (because phone wont stop whining about it until I do) - Network provider stops working.


Google Maps works fine because they are using LocationClient in Play Services.  Seems to be an introduced bug in LocationManager caused by something in latest Play Services.

This is a big issue for us, because we need to know employee location and we cannot rely just on GPS locks.

I'm experiencing the exact same problem on many 4.x devices, like HTC sensation (4.0.3) and Nexus 10 (4.2.1)

After about a week, calling LocationManager.requestLocationUpdates with NETWORK_PROVIDER doesn't provide locations anymore and the only way to have it work again is a device reboot. In the meantime, GPS_PROVIDER and and Google Maps (without GPS) still work.

An interesting sidenode: Nexus 4 running 4.3 seems immune to this as I have never witnessed the problem with uptimes > 2 weeks, but it may just be a coincidence.

I am experiencing this issue as well.  I never noticed it until I turned satellites off today. Rebooting the device resolved the issue.

Samsung S3, S4, Note 2 .  All running JellyBean from different carriers.

[Comment deleted]

Me too experiencing this issue as well. Rebooting the device resolved the issue. Samsung Note running JellyBean 4.1.2

We are also experiencing the same issue on Android 4.X, with FUSED location provider.

Fused location provider is part of Google Play Services and not part of AOSP Android - you need to report bugs with that elsewhere. Unfortunately there doesn't seem to be an appropriate place to report bugs with Play Services. Sorry.

fyi - I opened an Android StackExchange question asking where Google Play Services issues should be reported, since all known existing support forms seem to be inappropriate:
http://android.stackexchange.com/questions/53354/where-should-issues-with-google-play-services-e-g-fused-location-provider-be

No responses yet.  You might consider upvoting it if you have the same question.

Is everyone seeing the following backtrace concerning this issue?  I want to gain some confidence that what we're seeing is the same concerning fused location provider.

E/AndroidRuntime( 2316):        at com.android.server.LocationManagerService.requestLocationUpdates(LocationManagerService.java:1316)
E/AndroidRuntime( 2316):        at android.location.LocationManager.requestLocationUpdates(LocationManager.java:836)
E/AndroidRuntime( 2316):        at android.location.LocationManager.requestLocationUpdates(LocationManager.java:461)
E/AndroidRuntime( 2316):        at com.android.location.fused.FusionEngine.enableProvider(FusionEngine.java:138)
E/AndroidRuntime( 2316):        at com.android.location.fused.FusionEngine.updateRequirements(FusionEngine.java:191)
E/AndroidRuntime( 2316):        at com.android.location.fused.FusionEngine.setRequest(FusionEngine.java:114)
E/AndroidRuntime( 2316):        at com.android.location.fused.FusedLocationProvider$2.handleMessage(FusedLocationProvider.java:98)
E/AndroidRuntime( 2316):        at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2316):        at android.os.Looper.loop(Looper.java:137)

F*** you google. Last android I ever bought| Getting same behaviour on Huawei y300, What a shame!

We are also experiencing the same issue on JellyBean devices, I hope Google will fix this issue soon, it is very annoying..

We require to locate the user location either by GPS or by network provider.
Please fix this bug ASAP as this is very annoying and frustrating...

I also got the same problem. Any update for this issue? Thanks.

Happened to us as well.  Samsung Galaxy S4.

I had to use Maps API in last week and was a pain to get it working, just because now we MUST to use this messed Google Play Services API/Google Maps API v2, even if Maps V1 was working fine until some time ago.

Today, I have to make use of user location, but this is not working, even if I copy entire code available here:
http://developer.android.com/training/location/retrieve-current.html

I never get any onLocationChanged() event on my Nexus 4 with KitKat.

What is up with you, Google guys?

Why instead to make easier to us to develop for Android, you rather prefer to make our life harder?

Don't you think that the platform fragmentation is enough to we deal with?

Hi,

this problem also happens while using Google Nexus with 4.1.1. Although, in samsung galaxy mini with 2.3.6 this doesn't happen i think.

Hope for a fix soon.

Hi, I am running the same code with GPS_PROVIDER and NETWORK_PROVIDER. GPS_PROVIDER runs perfectly but I am not getting location updates with NETWORK_PROVIDER. The mine is a Sony E. Xperia Neo V with Android 4.0

This is terrible look for more than two weeks the solution. And the problem is android. It is true that if you get google map the exact location and not as you would with listeners but GPS does not work.

Inconvenience to fix this or have uan solution by code to avoid these problems.

Customers are desperate. Since we all now have android 4.0.0 or higher

[Comment deleted]

I got this log from one of my app users:


12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734): Exception
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734): java.lang.SecurityException: need INSTALL_LOCATION_PROVIDER permission, or UID of a currently bound location provider
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at android.os.Parcel.readException(Parcel.java:1461)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at android.os.Parcel.readException(Parcel.java:1415)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at android.location.ILocationManager$Stub$Proxy.reportLocation(ILocationManager.java:1122)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at com.android.location.provider.LocationProviderBase.reportLocation(LocationProviderBase.java:137)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at com.google.android.location.network.NetworkLocationService.onHandleIntent(SourceFile:80)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at android.os.Handler.dispatchMessage(Handler.java:102)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at android.os.Looper.loop(Looper.java:137)
12-05 05:46:26.755 E/GmsNetworkLocationProvi(2734):     at android.os.HandlerThread.run(HandlerThread.java:61)
12-05 05:46:26.765 E/FusedLocationProvider(2734): Exception
12-05 05:46:26.765 E/FusedLocationProvider(2734): java.lang.SecurityException: need INSTALL_LOCATION_PROVIDER permission, or UID of a currently bound location provider
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at android.os.Parcel.readException(Parcel.java:1461)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at android.os.Parcel.readException(Parcel.java:1415)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at android.location.ILocationManager$Stub$Proxy.reportLocation(ILocationManager.java:1122)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at com.android.location.provider.LocationProviderBase.reportLocation(LocationProviderBase.java:137)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at ezg.a(SourceFile:147)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at ezx.a(SourceFile:303)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at ezx.a(SourceFile:287)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at ezo.a(SourceFile:931)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at fak.handleMessage(SourceFile:68)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at android.os.Handler.dispatchMessage(Handler.java:102)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at android.os.Looper.loop(Looper.java:137)
12-05 05:46:26.765 E/FusedLocationProvider(2734):       at android.os.HandlerThread.run(HandlerThread.java:61)

my app already has these permissions:

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

I to experienced this problem with my galaxy s3 and Nexus S phone. While debugging the Xamarin.Android C# code, I noticed, The GPSProvider is showing up as disenabled in the code IDE. The code was work great prior to Android 4.1 and 4.2 OS.

I am experiencing same issues.After spending lots of hours, came to know that this is bug in Android.Since our app is location sensitive, please Google take this issue at Highest Priority & fix it ASAP.I noticed that issue happens in 4.1 & 4.2.Also it is not vendor specific issue, happens in Micromax Canvas HD Device.

I am having the same problem with my new Samsung Galaxy S4 mini. Google maps can locate me correctly but none of the apps can do (all location services are on) ! (current version: 4.4.21) THIS IS ANNOYING!!

I have updated my location code to play services due to this problem.but i am experiencing the same problem.It really hurts the application which works based on network location.
I really don't understand what information google is needed more than this..they simply updated the status as "NeedsInfo" and let it go.I really feel bad as an android developer...

It appears to me that google are a bunch of lazy guys that let bugged fill
S.O. come into the wild and then tell the costumers to take in th a@@.
Em 12/12/2013 13:52, <android@googlecode.com> escreveu:

Samsung Ace 2, happens a lot!!!

Same issue with my Samsung Galaxy S4

I'm a user and I'm experiencing the same issue on my JellyBean device since Jan 11.

I have the same problem in several devices, I changed to the new google play LocationClient and network updates work fine for a while(usually until I disable it and enable again) but then they stop until I reboot the phone.

I tested on several devices:

Nexus 4(4.4.2)
Galaxy S3, S4 and S4 mini(4.1~4.2).

All the same issue.

But it seems to work fine on galaxy ace(2.3.6) and a galaxy tablet with 3.2

Did you try loading google maps to check if that kick starts the location ? My tests showed that if I loaded google maps it magically knew the location. And my app worked really well.

The reason the Google Play Services Location API doesn't use network positioning should be that it's built upon the vanilla Android APIs, and is affected by this issue as well.

Not as visible though because most often you have either Wifi or GPS available, so the Google Play Services Location API kind of hides this issue.

I can see that a lot of people are complaining about this issue and the google guys are giving a great shit about this!
Should I tell the users to reboot their phones??????????????
When I use fused location provider to get network updates it works fine, but when I switch to the non-fused and use the classic approach it won't update the location over network!!!!!!! It happens on HTC and Huawei! Google maps works fine (of course)

Happened on a Nexus7 (2013) for me. This is really a killer of the network locations, if you cannot rely at all on an update.

I would also like to add the following observation: In order to check whether a location provider is enabled, while my app is working, I go to my Nexus 7 (2013) Settings and disable all location services. My app identifies that no location is currently enabled, hence prompts the user to do it. When the location services are re-enabled, the app identifies that at least one location provider is enabled, however the onLocationChanged is never fired again... On top of that, the official Google Maps app also stops working, and the only solution is to restart the device.. :(

On other words..  Google devs suck...
Em 28/01/2014 16:25, <android@googlecode.com> escreveu:

Good news,

The GPS on third-party software started to work again (after a year or more) on my Nexus one a few days ago. I have not check to see if the Android OS has been update. But what else could it be?

King

I'm experiencing this issue, too. The only workaround I found is to restart the device.

I recall this same issue (or some duplicate) to have an 'open' status... I'm sure because I used the link to explain my customer why the restart was needed.

So this is a known issue, not sure why it's status is 'NeedsInfo'.
For that matter, I filtered this log from my S2:


02-03 12:26:22.464   2131-25598/? I/LocationManagerService﹕
request network (pid 8407) 0 0

02-03 12:26:54.524    2131-2142/? I/LocationManagerService:
remove network (pid 8407), next minTime = 86400000

02-03 12:26:54.579    8407-8407/org.myapp W/ResourceType﹕ Failure getting entry for 0x010802c0 (t=7 e=704) in package 0 (error -75)

I'm also facing the same issue. Isn't there no alternative to it??

It also occurs with google play services. Why there is no solution to such a big  problem.

I'm afraid Google will do nothing about it.

Exactly as my Nexus 4 with unstable Wi-Fi connection since Android 4.2. I had to bought a new router to fix this problem, because Google never did anything about this bug that affects many Nexus 4 and Nexus 7 users.

Nobody can explain why many Nexus devices does not work properly with some routers, but Google simple does not care about this.

Also, Google does not seem to worry about problems with onLocationChanged().

i have 2 words, shame on google :D

// Current Location
                locationManager = (LocationManager) getSystemService(Context.LOCATION_SERVICE);
A year back I found a way to kick start the locationManager to get the LAST KNOWN LOCATION. And today, this fails. Instead of just calling getLastKnownLocation, I used the requestLocationUpdates to kick the cache to update its location. It worked. Today it is not working.

GOOGLE WAKE THE F' UP. FIX THIS, we have better work to do than to report that your "get me current location" api's DON'T work.

Tested in Micromax Jellybean (I DONT NEED TO TEST ANY MORE, its clear from above posts that people are seeing this on other devices too.

                locationManager.requestLocationUpdates(
                                LocationManager.NETWORK_PROVIDER, 0, 0, new LocationListener() {
                                        @Override
                                        public void onStatusChanged(String provider, int status,
                                                        Bundle extras) {
                                        }

                                        @Override
                                        public void onProviderEnabled(String provider) {
                                        }

                                        @Override
                                        public void onProviderDisabled(String provider) {
                                        }

                                        @Override
                                        public void onLocationChanged(final Location location) {
                                        }
                                });
                Location hereNow = locationManager
                                .getLastKnownLocation(LocationManager.NETWORK_PROVIDER);
                locationManager.removeUpdates(this);

[Comment deleted]

This seems to be the same bug: https://code.google.com/p/android/issues/detail?id=62323

And I also experience the same bug.

I'm also seeing the same problem both through Play Services (4.2.42) and the LocationManager on a HTC One X with 4.2.2. I don't see the problems on a Samsung Galaxy Ace 2 (GT-I8160) with 4.1.2.

What I have noticed is that turning off both "Sleep mode" (Automatically turn off data connection during long periods of inactivity) and the "Power Saver" Data connection "Put to sleep when screen is off" then re-booting will increase the time before the problem occurs. This leads me to believe that the problem is being caused by a lock not being released when the network is not available.

Also turning Airplane mode on then off seems to restart location updates.

If anyone from Google is reading this I'm happy to provide you with any info. that you need - just let me know what you want.

Same issue here...no love from the Googles.

Same issue here

Anyone found a workaround ? (code... not restart)

I think uninstalling the google play services & restart might work.

Thats not a workaround a code can/should invoke.

there is nothing wrong with the code since the same code is working on gingerbread, the real problem is google play services on higher version so either an update to it or removing it should fix the issue just try it and give feedback.

[Comment deleted]

Hi i am facing the same problem i am using the new location api of google to get currentlocation  its working fine on the note 2 but when i tried it on nexus 5 the onlocationchanged is not called.

when i reboot the device and start my app its getting the location and working fine.
but once i disable the location service and enable it again onlocationchanged is not called. its called only when i reboot the device.

 sushilku... i am also having problems after the upgrade to kitcat. If i disable location service and enable again, onlocationchange is never called. Actually you dont need to reboot the phone, if you restart play services it will work. So clearly google has broken something AGAIN!
Google, FIX this thing !

restart or rebooot is temporary solution, uninstall update to google play services would fix it.

On my LG G2 I got the 4.4.2 update yesterday.

Since than my location reporting history is useless, either the intervall is to low.
Or this defect is a new issue.

This thread looks simial to Issue 36920981

I have the same problem. the problem is happen on android 4.1 or 4.2.
I guess the problem is happen after a long standby time(sleep mode?), so I changed my program. try to solve the problem.
use PowerManager to check the screen is ON or OFF, when the screen is off, I unregister the LocationManager's listener. when the screen ON (again), I register the listener (again)
I testing the problem for two day, unitl now it is ok for me...

I have the same problem in nexus 4. I use google play services and OnLocationGhanged is never called.
But if wifi or 3G is on than it works if i press a button to get the location.

Jesus... how much more info does it need... :(

wonder why it works when i restart my nexus 4? If it has to do with the GPS reset, i wonder if i can do it programmatically, clear the gps data or something like that (i mean, do the same as a restart does)?

The status of this ticket is still "NeedsInfo". Does anyone know what info is still required by Google for this crystal clear bug to be accepted?

I've seen several times how onLocationChanged() no longer receives events from NETWORK_PROVIDER although Google Maps still knows the current location without GPS. Rebooting helps. Using Samsung Galaxy S2 and Android 4.1.2

My old applications to be migrated to new cell phones do not work, it seems that the locator API no longer works. The only solution so far is to migrate GooglePlay Services new code... this is terrible, and it will be an expensive job. Well done Google, by forcing us all to reprogram our APP just because they want to save battery with the new API! : (

I have the same experience, it doesn't call it at all even after device restart. It's seems like Google is not going to do anything about this.

A few days ago i started to receive complaints from a few customers that my app started to report wrong location, not i am receiving lots of complaints. One of the clients noticed that when my app is reporting 'old locations' with 'current gps_timestamp' Google Maps is also reporting the current position as the old one. Everything works fine after disable/enable the location. Has google changed anything in PlayServices lately ? Come on google ! i switched from LocationManager to LocationAPI and now you break the LocationAPI too ?!

I'm developing an ap that uses Location Listener and when I'm developing everything is ok, but when I created the release apk, It doesn't work. What is happening ?

I think the issue is that if in the settings - Location Services 'Access to My Location' and atleast 'WiFi & Mobile Network' option is not enabled the service wont trigger. So please check it

That's not what this issue is about.

When "access to my location" is disabled (either gps or network provider), LocationListener.onProviderDisabled() is called immediately after the location updates are requested.

This issue is about a crash of LocationManagerService, only recoverable thru an OS restart.

I called the locationupdates from the main bundle of the main activity. Not from the onlocationchanged bit. Created a location listener and put the code to be executed inside the onLocationchanged bit of the location listener. Not in the onlocationchanged bit of the main bundle. The main bundle extends the mapfragment activity and implements the location listener. It works perfectly for me and updates the location, plus sets the camera every minute marking the current location.

I have the same problem. In my case I use AlarmManger to call periodically a Service which invokes requestLocationUpdates function in onStartCommand, when a location change is triggered the service kills itself (and invokes removeUpdates to unregister the listener).

At the beginning it worked for me but after trying it several times it stopped working.

What is the status of this bug?
Does anyone know how to solve this (using an alternative solution)?

I think this is a serious bug and it should be fixed.

My team is trying to build an application that would acquire data for risk assessment. And we have the same problem. onLocationChanged works fine after reboot. If I am in the middle of nowhere trying to document potential hazard with low battery I can't reboot my device!
We are working on a project vital for our community. We can't let suspicious data in our database (and Google knows it's true).

How many examples and comments do you Google people need?
It looks like you made this OS to be good only for fun&games (and marketing) not for responsible tasks.

Same problem here guys!!

I have a LG 4x HD P880 (4.1.2)..

The problem is on the device? My partner has a Samsung Note 3 and it doesn't happens with him..

Hi,

any news about this BIG problem ?

[Comment deleted]

LocationManger not working on new devices(Android 4.1 HTC), LocationClient not working on old devicess(Android 2.3 Samsung). Tnx Google we solute you.

I have the similar problem. Have a class that implements LocationClient and works fine on 4.4.2 Moto G, but not work on 2.3.5 XT860 and 2.3.6 GT-P1000L. It's work fine before the ADT update, now from the logs I got it's show that onLocationChanged never been called.

Thanks for the help from now.

So, is this improving or not? The onLocationChanged is also not called in my Atrix with 2.3 anymore...

I too have this problem sometimes, without wifi on, the locationclient didn't work. But after i turned on wifi, tried the app once again, it got back to normal. Tried to turn off the wifi after that wanna check if the app went back to normal. and it did! Strange behavior! Oh i forgot to mention, this situation occurs many times, when my battery is low. FYI, I use galaxy s4.

As a small update to my case where I use an Atrix with 2.3.4: If I have both locationManager and locationClient in my activity enabled, and register a locationListener to the locationManager, then both locationManager and locationClient are fired and show the updated location. It might be a workaround for devices that the locationClient is not fired.

This is the first time I have seen this pages, it was hidden from me and their are more apps and pages hidden from me.

La mia posizione predefinita ( casa ) l'indirizzo è Borgoricco via vento,29 Padova 35010

I meet the bug that the network locaiton can not be used by third on Android4.4, but the gmap can use its own network location.
The log is:
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986): Exception
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986): java.lang.SecurityException: need INSTALL_LOCATION_PROVIDER permission, or UID of a currently bound location provider
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at android.os.Parcel.readException(Parcel.java:1476)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at android.os.Parcel.readException(Parcel.java:1430)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at android.location.ILocationManager$Stub$Proxy.reportLocation(ILocationManager.java:1123)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at com.android.location.provider.LocationProviderBase.reportLocation(LocationProviderBase.java:137)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at com.google.android.location.network.NetworkLocationService.onHandleIntent(SourceFile:88)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at android.os.Handler.dispatchMessage(Handler.java:102)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at android.os.Looper.loop(Looper.java:136)
08-08 06:09:14.591 E/GmsNetworkLocationProvi( 1986):    at android.os.HandlerThread.run(HandlerThread.java:61)


Can someone help me?
Thanks!

I have same issue in many devices... samsung, karbon... etc... please resolve these as soon as possible...

Has anyone checked if using only requestSingleUpdate can help avoid this situation ?

It's the same with me.

onProviderDisabled is called instead of onLocationChanged directly. This happens only with NETWORK_PROVIDER.

Device restart never fixed the issue.
This is weird.

Android 4.4 Vanilla Build
Samsung Galaxy S3

Same problem.
device Huawei Ascend P6 (kitkat).

Best.

Same here in a Galaxy S2 Android 4.1.2
Restarting device turns network provider listener on again. But after some hours or a day its stops again.

In response to #98:

requestSingleUpdate exhibits the same behavior, unfortunately.

Rebooting fixed the issue (for now), but that's an unacceptable workaround.

Asus Transformer Pad tf700t
Android 4.2.1 (with all of Asus' modifications)

In response to #102:

I know it exhibits the same behavior I just want to make sure you understood my question.. If I use only single locations to begin with every X minutes in the background (just an example) will I encounter the same issue ?

(I know that after the issues occurs only a restart helps)

tenho um  lg l5  tenho o aplicativo gratuito os primeiros dias funcionou perfeito mas agora a localizaçao fica somente em 1 local e nao rastreia meus trajetos aguardo resposta e espero uma soluçao por parte do dono do aplicativo que e muito bom

could be flagged as priority=high and not medium...

This is just infuriating. Experiencing the same issue on Samsung Galaxy Nexus.

Reboot is the only option and we can count on this issue never being fixed just like numerous other issues of the entire Android ecosystem.

This comment may be unhelpful but not as much as Google not giving a damn about developers.

I also face the same problem in my Nubai Z7 max, i have to reboot the phone to lock the network positioning and also it work for sometime then later on not lock to the Wifi and data position until i reboot the phone...

[Comment deleted]

Almost Dec over a year and still needsInfo??? I'm still getting the same issue. The reboot fixes it but that is not a solution. This on a Samsung SGH-T959V with 4.2.2, rooted

Obsolete ?! The problem is still occurring with no code based workaround..

What is happening here? Why is this issue made obsolete? Please provide more information.

yes this issue is not resolved.

Just because an API has revved doesn't mean we should obsolete the issue on all previous platforms.
Applications that have valid bugs on precious APIs shouldn't be thrown under the bus just because you want to consolidate all your special sauce in Google play Apis and close up shop.

Maybe not evil but certainly shameless

Still getting this issue on android version 4.1.2, Samsung Core many times. Not resolved in latest Play service library also.

Still getting this issue on Android version 4.1.2.
Samsung Core model number GT-I8260L.

[Comment deleted]

With Fused location provider I got the same issue after 2 or 3 days of app is running.
Why this issue have status obsolete?

I can confirm that this issue is NOT obsolete in Play Services 6.7.76 using the fused location provider. I see many devices which are not receiving location updates until they are restarted when using the PRIORITY_BALANCED_POWER_ACCURACY.

I am working on location sensitive app .I too faced same issue,while using fused location provider.Seems it stops receiving location updates in between thereby pointing the user in old location.

This issue also happens to me on Galaxy S3 with Android 4.1.2, very annoying issue.

[Comment deleted]

I have the same issue and my app depends on this working correctly.

Please increase issue priority to 'High'.

In the meantime, please provide a realistic workaround that can be implemented in code.

The issue occurs on a ZTE N9520 Android version 4.4.3.

its still happen on 5.0.1  Nexus4 :/ really google, REALLY??? after 2 Years? and you still try to push the new api... again REALLY?  maybe its time to switch to M$ or the bitten fruit...  ... REALLLY???? no that one of google's dev will read it... but REALLY?

OMG i'm really disapointed :(((, i didn't understand what is the problem until i find it here, i'm using google api to get the distance duration and direction between 2 places. the current location sometime work and sometime not.

I do not understand. Why google map get current user location, but other apps are not? Finally, google maps (or fused location from google services) use build-in Android capabilities for retrieving location. Why we can't use it too? Google, open your secret, how you workaround this issue?

My solution is "when the screen is off, unregister your location service, otherwise your location wiil be lost. and you must restart your device to fix it"
you can try this way, I think this is why Google Map can work.

Google: The frustration you are seeing from this from stems from the fact if any of us in here marked an open issue as obsolete, without telling anyone what the solution was or offering an explanation, then walked away from the issue after people continued to report it, our bosses would, at the very least, call us out on the carpet.

Granted we are not paying you but we do have an implied contract that we can enforce by simply moving our apps to another platform.

In my case, when I stay at the same place, network provider get location, but when I'm walking it doesn't work.
I only use data package from the phone provider.

locationManager.requestLocationUpdates(LocationManager.NETWORK_PROVIDER, THREE_MIN, 0, listener)

We have been facing this issue GPS_PROVIDER works fine on Moto-e with lollipop and sometimes works in a Azus zenphone running kitkat. The behaviour is very confusing we cannot find out when it'll work work and when not the same issue happens with samsung Galaxy s running Kitkat

Did anyone come up with a better work around than telling users to restart their phone?  I'm okay with that for testing but beyond that it's a bit much to ask.  Only thing I could think of was to use the network provider as a fall back, but that is a huge draw back for me personally as accuracy is key.

It is just unacceptable that the LocationManager cannot do its work properly. Whenever I use GPS as the provider, the onLocationUpdate is never called. I have to switch to Network_provider for it to work.

Google earns enough money so this issue doesnt need to be taken care of it seems to me!

still i too facing this problem!!! :(

still facing this problem too

So, do we need to just use the play service API for the workaround?

No that doesn’t solve it either, tried!

I still have this issue and i'm using a  note 5
does anyone know when this issue will be resolved

i have this problem too on LG-D605 Android 4.4.2

While Google Maps App gets the location without problem

They ever gonna fix this or comment?

I have a HTC OneM8, location doesn't update after 2 days, it's pathetic to ask people to reboot their devices at regular intervals.
Is this problem going to be resolved ?

[Comment deleted]

This issue is reported by user yesterday. I was not having problem earlier ,when we published app in store in march 16. I don't know how it started without code change.

This is also an issue for us!

Experiencing the same issu

We have also experienced the similar issue in Samsung , Moto G2 device
in Moto G2(Android 5+) device if we switch off GPS and On Again it starts working sometimes
Samsung /Sony(Android 4+) devices problem comes once in a while after few days  

My map appication (to show nearby places like Hospitals, Restaurants, etc) works in ICS, Lollipop & Marshmallow. In Jellybean and KitKat, a blank map appears. It is showing the world map with just the current location. On debugging, the latitude & longiude values are (0,0). Its working perfectly in devices other than KitKat & Jellybean.
Does anyone has any idea about the possible issue & solution for the same?

This happened to one of my app's users last Friday. There was no error, the listener stopped working and he had to reboot the device. If it helps, that was a Moto G as well.
PS: if a lot of people is having this issue, in my opinion it should not be obsolete.

Ridiculous how there's no official response yet.

same problem here... still no solution?

Issue still occurring on Android 6 devices (Alcatel Pixi 4034N).  Clearly not obsolete, as it is still occurring on new devices with the latest available version of the OS, when used using the sample code provided in current documentation on the developer.android.com describing how to access location data (at https://developer.android.com/guide/topics/location/strategies.html).

Any update about this issue guys.... i am also facing same problem

Same here, I'm trying to get an approximate location, and I want to get it as fast as possible, even if it's off by 50km, it's still good enough for me:

        Criteria criteria = new Criteria();
        criteria.setAccuracy(Criteria.ACCURACY_COARSE);
        criteria.setBearingRequired(false);
        criteria.setAltitudeRequired(false);

        List<String> providers = locationManager.getProviders(criteria, true);
        if (providers != null) {
            Location newestLocation = null;
            for (String provider : providers) {
                Location location = locationManager.getLastKnownLocation(provider);
                if (location != null) {
                    if (newestLocation == null) {
                        newestLocation = location;
                    } else {
                        if (location.getTime() > newestLocation.getTime()) {
                            newestLocation = location;
                        }
                    }
                    locationManager.requestSingleUpdate(provider, this, null);
                }
            }
        }

Even though location is turned on on high accuracy, and requestSingleUpdate gets called twice with gps and network providers... .onLocationChanged does not get called most of the times.

Sometimes gets called right away... sometimes it takes minutes... sometimes it never gets called. Also the documentation on this is rather confusing...
Using the google play services gcm didn't help either. I've been able to reproduce this in multiple devices.

This issue is been open since 2013 and it is not yet fixed.. at least come up with a work around or list of devices or Versions or Specs which are not going to support.

i also have a "sometimes issue" with no onLocationChanged called
so my app is on waiting condition... and it makes anoying.

locationManager.requestLocationUpdates(LocationManager.NETWORK_PROVIDER, 0, 0, this);

Unfortunatly, N OS still have a same issue.

Dear Google's Guru, please help this.

This issue is still a problem for me. Affected devices: HTC 10, Samsung S8

This issue is still a problem for me. But also with GPS provider. Affected devices: Samsung S7

GOOGLE WAKE THE HELL UP. This issue is open since 2013 and haven't been resolved yet? If you can't resolve the issue at least mark it as deprecated or simply give us some workaround. This is so NOT very responsible of you to not pay any attention to the issue that is brought to you. SOLVE THIS.

Please, did someone find a solution or workaround for that? Thanks.

2020 already and nothing yet?

And the year 2021 has come, Google still can't fix it. Oh great Google! Do something finally!!!

it's 2024 and we still have same issue