Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You are completely right, the minimum time 45 seconds is harcoded in Android.</p> <p>This seems to be a NetworkLocationProvider class source code, when it was still in Android core:</p> <p><a href="http://www.netmite.com/android/mydroid/frameworks/base/location/java/com/android/internal/location/NetworkLocationProvider.java">http://www.netmite.com/android/mydroid/frameworks/base/location/java/com/android/internal/location/NetworkLocationProvider.java</a></p> <p>Look at the variable:</p> <pre><code>private static final long MIN_TIME_BETWEEN_WIFI_REPORTS = 45 * 1000; // 45 seconds </code></pre> <p>And the method:</p> <pre><code>@Override public void setMinTime(long minTime) { if (minTime &lt; MIN_TIME_BETWEEN_WIFI_REPORTS) { mWifiScanFrequency = MIN_TIME_BETWEEN_WIFI_REPORTS; } else { mWifiScanFrequency = minTime; } super.setMinTime(minTime); } </code></pre> <p>Now NetworkLocationProvider is out of the Android core, you can find it in NetworkLocation.apk in /system/app</p> <p>You can find an explanation of why is out of the core here:</p> <p><a href="https://groups.google.com/forum/?fromgroups=#!topic/android-platform/10Yr0r2myGA">https://groups.google.com/forum/?fromgroups=#!topic/android-platform/10Yr0r2myGA</a></p> <p>But 45 seconds min time seems to still be there. Look at this NetworkProvider decompilation:</p> <p><a href="http://android.fjfalcon.com/xt720/miui-trans/apk-decompiled/NetworkLocation/smali/com/google/android/location/NetworkLocationProvider.smali">http://android.fjfalcon.com/xt720/miui-trans/apk-decompiled/NetworkLocation/smali/com/google/android/location/NetworkLocationProvider.smali</a></p> <pre><code>.line 149 const-wide/32 v4, 0xafc8 iput-wide v4, p0, Lcom/google/android/location/NetworkLocationProvider;-&gt;mWifiScanFrequency:J </code></pre> <p>As you might guess if you convert 0xafc8 to decimal you get 45000 milliseconds</p> <p>I haven't found an explanation of why 45 seconds. I suppose there will be reasons like avoiding service overloading or other uses they don't want.</p> <p>In fact, there is a 100 request courtesy limit to Geolocation API:</p> <p><a href="https://developers.google.com/maps/documentation/business/geolocation/#usage_limits">https://developers.google.com/maps/documentation/business/geolocation/#usage_limits</a></p> <p>But they don't seem to respect this rule in Google Maps app. If you open it and you only active network location you can notice that yout location is updated much more frequently than 45 seconds.</p> <p>I noticed this line suspiciously frequent (33 times a second) in logcat when Google Maps is open:</p> <p>02-20 17:12:08.204: V/LocationManagerService(1733): getAllProviders</p> <p>I guess Google Maps is also calling removeUpdates() and requestLocationUpdates() again to obtain a new position.</p> <p>So I think there is no fix and this is the best you can do if you want to get network locations over one in 45 seconds.</p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid: requestLocationUpdates updates location at most every 45 seconds
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdjpeinado
    1. USdjpeinado
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for this very thorough answer. It seems plausible enough that Google don't "respect" their own rule for non-API users, since it is their API. However, I am not using the Geolocation API, so what I'm seeing can't be an effect of that. I found out that it is somewhat possible to control (and bring down) the intervals between updates by calling `removeUpdates(..)` and then `requestLocationUpdates(..)`.
      singulars
      1. PO
      1. USstemadsen
    2. COYou are not using Google Geolocation API directly, but I suppose it is a front end to a core part shared with android network location. So if Geolocation API is limited to 100 request/day free, it seems that there is a reason and somehow they try to limit android network location too. Keep in mind that if you could "hack" the system to dynamically set cell towers and wifi access points info you could use the phone as a Geolocation API server... That is the reason what I mentioned Google Geolocation API.
      singulars
      1. PO
      1. USdjpeinado
    3. COI have experienced a couple of times that a new location was delayed due to this, so I guess I will just have to warn my users about this issue. Thanks.
      singulars
      1. PO
      1. USstemadsen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload