Fused location API return wrong location occasionally [37058437]

Obsolete

Bug

[AOSP] duplicate

Status Update

No update yet.

Description

ca...@gmail.com

created issue #1

Aug 27, 2015 07:44AM

Library used (com.google.android.gms:play-services-location):
Version used: 7.0.0

The issue I report is similar to issue#66160, but the status of issue#66160 is set to "Obsolete".
Thus I create a new issue report.

Description:
In my app, the fused location API is used in order to display the current location info of users.
Code step -
a. Call GoogleApiClient.connect().
b. Wait unit the connection is established (GoogleApiClient.ConnectionCallbacks.onConnected(Bundle) is called).
c. Send LocationRequest with LocationRequest.setPriority(LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY);
d. Wait unit LocationListener.onLocationChanged(Location) is called, record the Lat,Lng, accuracy & time from the returned Location object.

The above logic works fine but some users complain that wrong locations (with ~20km to ~50km error) are occasionally returned.
I can occasionally reproduced this case, here is the example:

Model: LG G3 Pro (LG-D855)
Android version: 5.0
Kernel version: 3.4
Actual location: Tsui Sha Tsim, Hong kong (22.30195, 114.17417)
Actual time: 2015/08/27 11:23

API returned Latlng: Tin Shui Wai, Hong Kong (22.4545499, 114.0017855)
API returned accuracy: 20.0
API returned Time: 2015/08/27 11:21

I switched the network among 2 different WiFi & 3 different 4G provider, the API kept returning the wrong location(Tin Shui Wai).
I tried every OS location setting options (High accuracy, Battery saving & Device only), the API kept returning the wrong location(Tin Shui Wai).
I rebooted device and then launched my app, the API kept returning the wrong location(Tin Shui Wai).
The API suddenly returned the correct location (Tsui Sha Tsim) after about 30mins.

According to users' reports, this issue is found on many different device:
-Samsung GT-I9100 (Android v4.1.2)
-LG-F2405 (Android v4.4.2)
-Sony Z3 (Android v4.4.4)
-SM-G5308W (Android v4.4.4)
-Lenovo A8505 (Android v4.2.2)
-Xiaomi 2013023 (Android v4.2.2)
-Sony Z (Android v5.0.2)
-Samsung SM-N9005 (Android v5.0)
-Xiaomi HM Note 1W (Android v4.2.2)

According to users' reports, the wrong locations returned share the following characteristic:
1. They are at least 20km far from the actual location.
2. They are always match-up with the actual location. Let say the actual location is A, the API either returns the correct location(A), or the wrong location (B). Other locations are never returned.

Comments

ch...@google.com <ch...@google.com> #2Aug 27, 2015 11:38AM

I think it makes a perfect sense as a feature request and is indeed distinct from other issues you referenced. Thanks for filing!

lo...@gmail.com <lo...@gmail.com> #3Sep 25, 2015 06:57AM

I have CCed stakeholders and leaving the feature request assigned to myself for now.

lo...@gmail.com <lo...@gmail.com> #5Oct 6, 2015 06:34AM

RE:"Thanks for accepting this request": this is just being brought for consideration. Thanks again for filing the feature request.

li...@gmail.com <li...@gmail.com> #6Oct 9, 2015 11:09PM

Any progress on this?
This request is similar to

https://issuetracker.google.com/issues/72224267

Why are we so interested in this?

Our goal is to build an easy to maintain, basically 'NoETL' datawarehouse pipeline. Everywhere where we have to 'fall back' to Python programming makes the whole pipeline more complex to maintain. Having (parametrized) materialized views that could do a full or partial refresh would really be THE enabler for this.

Basically it would be something like Looker's Persistent Direived Tables, but then with the added abilities to:
-Refresh incrementally
-Fully use time partitioning and table suffixing.

li...@gmail.com <li...@gmail.com> #7Oct 10, 2015 12:39PM

What types of queries do you want to use in the MV?

Using aggregation views to optimize query performance and cost is a different use case than using MV as a workaround to ELT.

lo...@gmail.com <lo...@gmail.com> #8Oct 28, 2015 01:34PM

#7, for us the use cases would be both ETL and costs optimization queries (fyi, I am the original poster of these request)

IMO the main difference between the two patterns are:
1) ETL type MV's have more joins
2) Cost optimization MV's are simpler / aggregate style queries

In the end, what is important is that it supports the following refresh patterns:
1) easy: a full refresh (truncate / insert pattern). Oracle calls this a full refresh
2) more complex: incremental update, for this to work the insert/update/delete (or merge) has to be driven by a key. Oracle calls this the fast refresh option.

IMO this functionality could / should replace BQ scheduled queries, which I guess won't be a real focus anymore now that cloud composer is here...

lo...@gmail.com <lo...@gmail.com> #9Nov 3, 2015 09:41AM

Is there any progress with regards to this topic? Having materialised views in BigQuery would be the trigger for us to move away from our current solution, onto the BQ platform....

am...@google.com <am...@google.com> #10Nov 4, 2015 02:10AM

Assigned to am...@google.com.

Tjeerd - please sync up with your Google Cloud account team to share roadmap under an NDA.

am...@google.com <am...@google.com> #11Nov 4, 2015 01:29PM

Status: New

Is materialized view in early-access stage?
We just saw it in gcloud CLI and would like to try this feature.

am...@google.com <am...@google.com> #12Nov 5, 2015 02:01AM

Assigned to am...@google.com.

How do we get access to the experimental materialized view feature?

am...@google.com <am...@google.com> #13Nov 5, 2015 11:59AM

Status: New

please sync up with your Google Cloud account team to share roadmap under an NDA.

lo...@gmail.com <lo...@gmail.com> #14Dec 2, 2015 09:21AM

Had hoped something would be announced at Google Next '19, guess we'll have to wait :-(

ka...@gmail.com <ka...@gmail.com> #15Jan 4, 2016 12:12PM

Yep, would love this.

na...@gmail.com <na...@gmail.com> #16Jan 5, 2016 10:02AM

We are looking for this feature too, and it often comes up when we evaluate bq vs snowflake. Would be great if bq can support MVs.

ar...@gmail.com <ar...@gmail.com> #17Feb 24, 2016 09:16AM

with bq mk this is sort of possible (transfer jobs), something like:

bq mk \
--transfer_config \
--target_dataset='target_dataset' \
--display_name='schedule_name' \
--params='{"query":"SELECT xyz FROM table","destination_table_name_template":"target_table","write_disposition":"WRITE_APPEND"}' \
--data_source='scheduled_query' \
--schedule='every day 01:00'

ar...@gmail.com <ar...@gmail.com> #18Feb 24, 2016 09:20AM

nothing announced in Google Next 19 UK :(

su...@gmail.com <su...@gmail.com> #19Mar 2, 2016 12:04PM

was reading a blog about ML from google , and they dropped this info that materialized views are already in Alpha !!!!!!

ke...@brainvire.com <ke...@brainvire.com> #20Mar 31, 2016 01:01PM

Any update on this BQ team? If it is in alpha, let us know ASAP!

th...@gmail.com <th...@gmail.com> #21May 12, 2016 07:23AM

are they still working on this? the issue is created on "Jun 1, 2017 12:47PM" , But still can't see any update on Materialized view.

pa...@gmail.com <pa...@gmail.com> #22Aug 16, 2016 07:45PM

Another customer expressed interest in this capability.

[Deleted User] <[Deleted User]> #23Aug 18, 2016 06:03AM

Hi,

I have a customer that is very interested in joining early access for this functionality.
Can I help them by signing up somewhere?

Thanks,
Lorin

ji...@gmail.com <ji...@gmail.com> #24Aug 25, 2016 04:25AM

Ok, Good news, I asked the product manager of BigQuery in twitter, and he said, Google next 2020, which will be in a couple of weeks.

va...@gmail.com <va...@gmail.com> #25Oct 15, 2016 07:35PM

il...@gmail.com <il...@gmail.com> #26Oct 22, 2016 01:33PM

vi...@gmail.com <vi...@gmail.com> #27Feb 13, 2017 12:32PM

m....@gmail.com <m....@gmail.com> #28Mar 3, 2017 07:05PM

We will announce support for materialized views in BQ soon. Stay tuned!

ma...@gmail.com <ma...@gmail.com> #29Mar 5, 2017 07:40PM

Beta available:

https://cloud.google.com/bigquery/docs/materialized-views-best-practices

(emphasis on beta!)

po...@gmail.com <po...@gmail.com> #30Mar 6, 2017 03:50PM

Is there any scope to extend support to unnesting within the same table for MV's on the near horizon?

su...@gmail.com <su...@gmail.com> #31Mar 20, 2017 07:35AM

Materialized views are now GA, including support for UNNEST: https://cloud.google.com/blog/products/data-analytics/bigquery-materialized-views-now-ga

[Deleted User] <[Deleted User]> #32Apr 24, 2017 01:12PM

Thanks everyone for the suggestions. Materialized Views V2 will be coming soon.

ja...@gmail.com <ja...@gmail.com> #33May 2, 2017 01:45AM

Thank you! Do you have reference/list of features to expect on V2?

ja...@gmail.com <ja...@gmail.com> #34May 2, 2017 01:48AM

The upcoming version of materialized views will add JOIN support to allow multi-table views as well as table projections.

il...@gmail.com <il...@gmail.com> #35May 2, 2017 07:17AM

> We calculated speed and had a cap on something like 60-70 miles/hr. Though not accurate but helped in removing out spikes in certain cases

Same here. A response from Google would be nice.

bk...@gmail.com <bk...@gmail.com> #36Jun 8, 2017 05:28PM

See also issue: 37123060
New fused location provider API confused by movable WiFi sources

bk...@gmail.com <bk...@gmail.com> #37Jun 8, 2017 06:30PM

Caught in the act! The following shows some logcat output of location information. Note lines labelled (*) CORRECT
and (*) BOGUS. Somehow, right in the middle, the location changes to one the device hasn't been in for over two weeks.
The locations are over 8000 km apart! This happens repeatedly. This happens for many days after the move. It affects where Google Maps starts up. It affects what weather report is shown. The "old" information appears sporadically interspersed with good information. There is no indication that the location is bad (it claims to have good accuracy, and also has supposed current date and time).

....
06-08 14:04:05.631 11058-11058/com.example.foobar W/setupLocationCallback: Status Status{statusCode=SUCCESS, resolution=null} (SUCCESS)
06-08 14:04:05.631 11058-11058/com.example.foobar W/setupLocationCallback: Location present usable
06-08 14:04:05.631 11058-11058/com.example.foobar W/setupLocationCallback: Network present usable
06-08 14:04:05.631 11058-11058/com.example.foobar W/setupLocationCallback: BLE present usable
06-08 14:04:05.631 11058-11058/com.example.foobar W/setupLocationCallback: GPS present usable

(*) CORRECT:
06-08 14:04:05.634 11058-11058/com.example.foobar E/onNewLocationChanged: mTime 2017-06-08 14:04:05.631 gTime 2017-06-08 14:04:05.599 diff 32 (msec)
06-08 14:04:05.634 11058-11058/com.example.foobar V/onNewLocationChanged: fused 43.0871591 -71.004784 alt 125.0 acc 16.0 vel 0.0 bea 0.0
...
(*) CORRECT:
06-08 14:04:06.180 11058-11058/com.example.foobar I/onLocationChanged: EXTRA BUNDLE for network Bundle[{networkLocationType=wifi, travelState=stationary, noGPSLocation=Location[network 43.087170,-71.004788 acc=20 et=+23h58m44s439ms {Bundle[mParcelledData.dataSize=224]}], nlpVersion=2023}] size 4 keySet android.util.MapCollections$KeySet@edab8378
06-08 14:04:06.180 11058-11058/com.example.foobar I/onLocationChanged: travelState stationary (Location Listener)
06-08 14:04:06.181 11058-11058/com.example.foobar I/onLocationChanged: bWiFiFlag true bNetworkFlag false (networkLocationType wifi)
06-08 14:04:06.181 11058-11058/com.example.foobar V/onLocationChanged: Ignoring location update soon after update
...
(*) BOGUS:
06-08 14:04:11.731 11058-11058/com.example.foobar I/onLocationChanged: EXTRA BUNDLE for network Bundle[{networkLocationType=wifi, travelState=moving, noGPSLocation=Location[network 21.255215,-157.819613 acc=43 et=+23h58m49s979ms {Bundle[mParcelledData.dataSize=216]}], nlpVersion=2023}] size 4 keySet android.util.MapCollections$KeySet@edab8378
06-08 14:04:11.731 11058-11058/com.example.foobar I/onLocationChanged: travelState moving (Location Listener)
06-08 14:04:11.732 11058-11058/com.example.foobar I/onLocationChanged: bWiFiFlag true bNetworkFlag false (networkLocationType wifi)
06-08 14:04:11.732 11058-11058/com.example.foobar V/onLocationChanged: Ignoring location update soon after update
...
(*) BOGUS:
06-08 14:04:11.765 11058-11058/com.example.foobar E/onNewLocationChanged: mTime 2017-06-08 14:04:11.763 gTime 2017-06-08 14:04:11.679 diff 84 (msec)
06-08 14:04:11.766 11058-11058/com.example.foobar V/onNewLocationChanged: fused 21.2552153 -157.8196129 alt -1.0 acc 42.5 vel -1.0 bea -1.0
...
(*) CORRECT
06-08 14:04:21.896 11058-11058/com.example.foobar E/onNewLocationChanged: mTime 2017-06-08 14:04:21.890 gTime 2017-06-08 14:04:21.815 diff 75 (msec)
06-08 14:04:21.896 11058-11058/com.example.foobar V/onNewLocationChanged: fused 43.0871699 -71.004788 alt -1.0 acc 20.0 vel -1.0 bea -1.0
...
(*) CORRECT
06-08 14:04:21.910 11058-11058/com.example.foobar I/onLocationChanged: EXTRA BUNDLE for network Bundle[{networkLocationType=wifi, noGPSLocation=Location[network 43.087170,-71.004788 acc=20 et=+23h59m0s115ms alt=17.100000381469727 {Bundle[mParcelledData.dataSize=164]}], nlpVersion=2023}] size 3 keySet android.util.MapCollections$KeySet@1b4cde1
06-08 14:04:21.910 11058-11058/com.example.foobar I/onLocationChanged: bWiFiFlag true bNetworkFlag false (networkLocationType wifi)
06-08 14:04:21.910 11058-11058/com.example.foobar V/onLocationChanged: Ignoring location update soon after update

(*) CORRECT
06-08 14:04:24.110 11058-11058/com.example.foobar E/onLocationChanged: mTime 2017-06-08 14:04:24.108 gTime 2017-06-08 14:04:25.000 diff -892 (msec)
06-08 14:04:24.110 11058-11058/com.example.foobar V/onLocationChanged: gps 43.08715924 -71.00478429 alt 125.0 acc 53.0 vel 0.0 bea -1.0

fl...@polarsteps.com <fl...@polarsteps.com> #38Jun 8, 2017 06:43PM

I am attaching my problem description as well: ( we are finally getting some traction going here ). I agree... this is a major blocker!

https://stackoverflow.com/questions/43721505/fused-location-provider-non-stationary-wifi

bk...@gmail.com <bk...@gmail.com> #39Jun 8, 2017 07:33PM

May have to revert to the good old GPS (GNSS). Or rather, provide a menu option that allows
user to do that. Now if there only was a
LocationRequest.PRIORITY_SUPER_HIGH_ACCURACY
that just switched back to the old way, so we don't have to have two piles of parallel code,
one using "fused" and one using "gps" That would be convenient!

bk...@gmail.com <bk...@gmail.com> #40Jun 13, 2017 03:19PM

More examples of "ghost" geolocations reappearing when using the FusedAPI

In the following, date and time is near the beginning of the line, MCC:MNC TAC:CI next,
and geolocation obtained using the FusedAPI near the end of the line (latitude, longitude, altitude, accuracy), followed by TimingAdvance)

Note it switching back and forth between Hawaii (21.27522, -157.81961) and New Hampshire (44.08717 -71.10477) with a few values like 44.01881 -70.97358 (with large error radius 3299) thrown in for good measure (these may be associated with the U.S. Cellular CDMA base station 1317:15:25505, which Google geolocation today reports as 44.022181 -70.975294 3756.0 )

311 580 519 58950401 44.00158 -70.98502 (0x3838301) (Starks' Hill, Fryeburg, ME) basestation
9 ID (20170608_115054) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -101 lteRsrp -9 lteRsrq 0 lteRssnr 44.08716 -71.10482 130 19 phonelatlong 68 TA
33 ID (20170608_115124) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -107 lteRsrp -10 lteRsrq 0 lteRssnr 44.08716 -71.10483 128 45 phonelatlong 69 TA
174 ID (20170608_115619) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -101 lteRsrp -8 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 39 phonelatlong 68 TA
224 ID (20170608_115746) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 14 lteSS -111 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 39 phonelatlong 69 TA
276 ID (20170608_115925) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 16 lteSS -103 lteRsrp -8 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 70 TA
297 ID (20170608_120000) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -102 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 28 phonelatlong 69 TA
312 ID (20170608_120032) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -101 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 28 phonelatlong 68 TA
327 ID (20170608_120112) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -103 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 28 phonelatlong 69 TA
391 ID (20170608_120317) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -101 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 45 phonelatlong 68 TA
537 ID (20170608_120807) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
632 ID (20170608_121121) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 68 TA
650 ID (20170608_121155) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 21 lteSS -99 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
674 ID (20170608_121251) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 70 TA
703 ID (20170608_121400) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 71 TA
776 ID (20170608_121617) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -101 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 32 phonelatlong 69 TA
893 ID (20170608_122001) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -100 lteRsrp -13 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 67 TA
908 ID (20170608_122037) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -100 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 34 phonelatlong 69 TA
922 ID (20170608_122106) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 34 phonelatlong 68 TA
973 ID (20170608_122242) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 32 phonelatlong 69 TA
991 ID (20170608_122318) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 32 phonelatlong 67 TA
1009 ID (20170608_122350) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -99 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
1054 ID (20170608_122521) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 42 phonelatlong 68 TA
1072 ID (20170608_122602) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 21 lteSS -99 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
1085 ID (20170608_122633) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 68 TA
1180 ID (20170608_122952) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -101 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 39 phonelatlong 69 TA
1239 ID (20170608_123202) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 39 phonelatlong 68 TA
1289 ID (20170608_123333) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
1324 ID (20170608_123445) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -13 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 34 phonelatlong 68 TA
1353 ID (20170608_123546) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 21 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 34 phonelatlong 67 TA
1396 ID (20170608_123718) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -99 lteRsrp -8 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 32 phonelatlong 68 TA
1413 ID (20170608_123754) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 70 TA
1429 ID (20170608_123825) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -100 lteRsrp -12 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
1464 ID (20170608_123930) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -99 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 36 phonelatlong 68 TA
1518 ID (20170608_124109) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 32 phonelatlong 69 TA
1709 ID (20170608_124748) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -100 lteRsrp -12 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 71 TA
1740 ID (20170608_124848) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -101 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 26 phonelatlong 68 TA
1857 ID (20170608_125237) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 24 phonelatlong 67 TA
1874 ID (20170608_125306) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 24 phonelatlong 69 TA
1980 ID (20170608_125609) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -99 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 68 TA
2086 ID (20170608_130000) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 70 TA
2099 ID (20170608_130028) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 28 phonelatlong 68 TA
2148 ID (20170608_130212) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 24 phonelatlong 69 TA
2215 ID (20170608_130417) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 17 24 phonelatlong 67 TA
2226 ID (20170608_130451) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -101 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
2322 ID (20170608_130804) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 39 phonelatlong 68 TA
2367 ID (20170608_130934) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 20 lteSS -99 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
2450 ID (20170608_132619) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.08718 -71.10486 191 15 phonelatlong 70 TA
2467 ID (20170608_132648) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08705 -71.10477 152 15 phonelatlong 68 TA
2481 ID (20170608_132718) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -102 lteRsrp -9 lteRsrq 0 lteRssnr 44.08706 -71.10479 150 15 phonelatlong 69 TA
2494 ID (20170608_132754) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -101 lteRsrp -8 lteRsrq 0 lteRssnr 44.08707 -71.10477 145 39 phonelatlong 70 TA
2509 ID (20170608_132826) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -102 lteRsrp -11 lteRsrq 0 lteRssnr 44.08707 -71.10477 145 39 phonelatlong 69 TA
2556 ID (20170608_132958) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -101 lteRsrp -10 lteRsrq 0 lteRssnr 44.08711 -71.10477 142 13 phonelatlong 68 TA
2583 ID (20170608_133100) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08712 -71.10477 141 42 phonelatlong 69 TA
2643 ID (20170608_133310) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -102 lteRsrp -12 lteRsrq 0 lteRssnr 44.08714 -71.10478 140 12 phonelatlong 68 TA
2703 ID (20170608_133520) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 18 lteSS -102 lteRsrp -10 lteRsrq 0 lteRssnr 44.08714 -71.10478 139 29 phonelatlong 69 TA
2717 ID (20170608_133552) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -102 lteRsrp -11 lteRsrq 0 lteRssnr 44.08714 -71.10478 139 29 phonelatlong 68 TA
2836 ID (20170608_133936) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -103 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
2903 ID (20170608_134143) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08717 -71.10479 17 20 phonelatlong 68 TA
2951 ID (20170608_134319) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -103 lteRsrp -10 lteRsrq 0 lteRssnr 44.08717 -71.10479 17 20 phonelatlong 69 TA
3015 ID (20170608_134534) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -103 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 32 phonelatlong 68 TA
3081 ID (20170608_134748) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 19 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358 -1 3299 phonelatlong 69 TA
3126 ID (20170608_134925) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -104 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961 -1 34 phonelatlong 68 TA
3144 ID (20170608_135000) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 16 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.08717 -71.10479 -1 20 phonelatlong 69 TA
3154 ID (20170608_135036) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 16 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08717 -71.10479 -1 20 phonelatlong 68 TA
3251 ID (20170608_135356) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -102 lteRsrp -9 lteRsrq 0 lteRssnr 44.08717 -71.10479 17 20 phonelatlong 69 TA
3284 ID (20170608_135501) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21 PCI 17 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.08717 -71.10479 17 20 phonelatlong 70 TA

ja...@gmail.com <ja...@gmail.com> #41Jun 13, 2017 09:38PM

Status remains new which is such a disappointment. It's getting close to 2
years now and no response. Instead of improving indoor accuracy as shown in
this year's IO please fix this. I hope someone understands that without
this it's just not usable. Hopefully someone, somewhere would get this
issue prioritized.

On Jun 13, 2017 11:19 AM, <buganizer-system@google.com> wrote:

Replying to this email means your email address will be shared with the
team that works on this product.

https://issuetracker.google.com/issues/37058437

*Changed*

*bk...@gmail.com <bk...@gmail.com> added

comment #40

https://issuetracker.google.com/issues/37058437#comment40>:*
More examples of "ghost" geolocations reappearing when using the FusedAPI

In the following, date and time is near the beginning of the line, MCC:MNC
TAC:CI next,
and geolocation obtained using the FusedAPI near the end of the line
(latitude, longitude, altitude, accuracy), followed by TimingAdvance)

Note it switching back and forth between Hawaii (21.27522, -157.81961) and
New Hampshire (44.08717 -71.10477) with a few values like 44.01881
-70.97358 (with large error radius 3299) thrown in for good measure (these
may be associated with the U.S. Cellular CDMA base station 1317:15:25505,
which Google geolocation today reports as 44.022181 -70.975294 3756.0 )

311 580 519 58950401 44.00158 -70.98502 (0x3838301) (Starks' Hill,
Fryeburg, ME) basestation
9 ID (20170608_115054) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -101 lteRsrp -9 lteRsrq 0 lteRssnr 44.08716 -71.10482
130 19 phonelatlong 68 TA
33 ID (20170608_115124) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -107 lteRsrp -10 lteRsrq 0 lteRssnr 44.08716 -71.10483
128 45 phonelatlong 69 TA
174 ID (20170608_115619) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -101 lteRsrp -8 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 39 phonelatlong 68 TA
224 ID (20170608_115746) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 14 lteSS -111 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 39 phonelatlong 69 TA
276 ID (20170608_115925) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 16 lteSS -103 lteRsrp -8 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 70 TA
297 ID (20170608_120000) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -102 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 28 phonelatlong 69 TA
312 ID (20170608_120032) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -101 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 28 phonelatlong 68 TA
327 ID (20170608_120112) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -103 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 28 phonelatlong 69 TA
391 ID (20170608_120317) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -101 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 45 phonelatlong 68 TA
537 ID (20170608_120807) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
632 ID (20170608_121121) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 68 TA
650 ID (20170608_121155) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 21 lteSS -99 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
674 ID (20170608_121251) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 70 TA
703 ID (20170608_121400) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 71 TA
776 ID (20170608_121617) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -101 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 32 phonelatlong 69 TA
893 ID (20170608_122001) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -100 lteRsrp -13 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 67 TA
908 ID (20170608_122037) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -100 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 34 phonelatlong 69 TA
922 ID (20170608_122106) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 34 phonelatlong 68 TA
973 ID (20170608_122242) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 32 phonelatlong 69 TA
991 ID (20170608_122318) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 32 phonelatlong 67 TA
1009 ID (20170608_122350) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -99 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
1054 ID (20170608_122521) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 42 phonelatlong 68 TA
1072 ID (20170608_122602) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 21 lteSS -99 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
1085 ID (20170608_122633) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 68 TA
1180 ID (20170608_122952) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -101 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 39 phonelatlong 69 TA
1239 ID (20170608_123202) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 39 phonelatlong 68 TA
1289 ID (20170608_123333) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
1324 ID (20170608_123445) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -13 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 34 phonelatlong 68 TA
1353 ID (20170608_123546) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 21 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 34 phonelatlong 67 TA
1396 ID (20170608_123718) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -99 lteRsrp -8 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 32 phonelatlong 68 TA
1413 ID (20170608_123754) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 70 TA
1429 ID (20170608_123825) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -100 lteRsrp -12 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
1464 ID (20170608_123930) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -99 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 36 phonelatlong 68 TA
1518 ID (20170608_124109) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 32 phonelatlong 69 TA
1709 ID (20170608_124748) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -100 lteRsrp -12 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 71 TA
1740 ID (20170608_124848) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -101 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 26 phonelatlong 68 TA
1857 ID (20170608_125237) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 24 phonelatlong 67 TA
1874 ID (20170608_125306) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 24 phonelatlong 69 TA
1980 ID (20170608_125609) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -99 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 68 TA
2086 ID (20170608_130000) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -11 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 70 TA
2099 ID (20170608_130028) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -100 lteRsrp -9 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 28 phonelatlong 68 TA
2148 ID (20170608_130212) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 24 phonelatlong 69 TA
2215 ID (20170608_130417) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
17 24 phonelatlong 67 TA
2226 ID (20170608_130451) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -101 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
2322 ID (20170608_130804) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -100 lteRsrp -10 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 39 phonelatlong 68 TA
2367 ID (20170608_130934) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 20 lteSS -99 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
2450 ID (20170608_132619) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.08718 -71.10486
191 15 phonelatlong 70 TA
2467 ID (20170608_132648) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08705 -71.10477
152 15 phonelatlong 68 TA
2481 ID (20170608_132718) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -102 lteRsrp -9 lteRsrq 0 lteRssnr 44.08706 -71.10479
150 15 phonelatlong 69 TA
2494 ID (20170608_132754) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -101 lteRsrp -8 lteRsrq 0 lteRssnr 44.08707 -71.10477
145 39 phonelatlong 70 TA
2509 ID (20170608_132826) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -102 lteRsrp -11 lteRsrq 0 lteRssnr 44.08707 -71.10477
145 39 phonelatlong 69 TA
2556 ID (20170608_132958) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -101 lteRsrp -10 lteRsrq 0 lteRssnr 44.08711 -71.10477
142 13 phonelatlong 68 TA
2583 ID (20170608_133100) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08712 -71.10477
141 42 phonelatlong 69 TA
2643 ID (20170608_133310) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -102 lteRsrp -12 lteRsrq 0 lteRssnr 44.08714 -71.10478
140 12 phonelatlong 68 TA
2703 ID (20170608_133520) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 18 lteSS -102 lteRsrp -10 lteRsrq 0 lteRssnr 44.08714 -71.10478
139 29 phonelatlong 69 TA
2717 ID (20170608_133552) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -102 lteRsrp -11 lteRsrq 0 lteRssnr 44.08714 -71.10478
139 29 phonelatlong 68 TA
2836 ID (20170608_133936) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -103 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
2903 ID (20170608_134143) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08717 -71.10479
17 20 phonelatlong 68 TA
2951 ID (20170608_134319) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -103 lteRsrp -10 lteRsrq 0 lteRssnr 44.08717 -71.10479
17 20 phonelatlong 69 TA
3015 ID (20170608_134534) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -103 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 32 phonelatlong 68 TA
3081 ID (20170608_134748) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 19 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.01881 -70.97358
-1 3299 phonelatlong 69 TA
3126 ID (20170608_134925) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -104 lteRsrp -11 lteRsrq 0 lteRssnr 21.27522 -157.81961
-1 34 phonelatlong 68 TA
3144 ID (20170608_135000) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 16 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.08717 -71.10479
-1 20 phonelatlong 69 TA
3154 ID (20170608_135036) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 16 lteSS -103 lteRsrp -9 lteRsrq 0 lteRssnr 44.08717 -71.10479
-1 20 phonelatlong 68 TA
3251 ID (20170608_135356) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -102 lteRsrp -9 lteRsrq 0 lteRssnr 44.08717 -71.10479
17 20 phonelatlong 69 TA
3284 ID (20170608_135501) mUTC 311 MCC 580 MNC 519 TAC 58950404 CI 21
PCI 17 lteSS -104 lteRsrp -10 lteRsrq 0 lteRssnr 44.08717 -71.10479
17 20 phonelatlong 70 TA

_______________________________

*Reference Info: 37058437 Fused location API return wrong location
occasionally*
component: Android Public Tracker
status: New
reporter: ca...@gmail.com
cc: ca...@gmail.com
type: Bug P3 S3
duplicate issue: 37062988 <

https://issuetracker.google.com/issues/37062988>
hotlist: [AOSP] duplicate <

https://issuetracker.google.com/hotlists/468389>
AOSP ID: 184005
ReportedBy: Developer

Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google
IssueTracker

issue 37058437

https://issuetracker.google.com/issues/37058437> where you have the role:
starred.

fl...@polarsteps.com <fl...@polarsteps.com> #42Jul 19, 2017 05:48PM

It seems, the issue has become worse with Google Play Services 11.

What I have additionally experienced now is locations coming from the fused location provider with future timestamps (weeks ahead of the current date but with a correct time set on the device) which I need to filter out.

Past Locations (weeks ago) with a new timestamp still occur rather frequently.

Furthermore wrong locations come in very often now and those "spikes" are not easily filterable anymore, since the device seems to follow a reasonable path along the wrong locations.

Is there any update on those issues?

cr...@gmail.com <cr...@gmail.com> #43Mar 4, 2018 03:10AM

I've been tracking location reported by fused locations services and quite often it thinks I'm in a teleportation device jumping back and forth between location coordinate provided few hours ago to the current location. I cannot use any geofence due to it being triggered at a seemingly random times.

da...@wikiloc.com <da...@wikiloc.com> #44Oct 14, 2019 02:23PM

I can confirm that hundreds if not thousands of (our) users are experiencing this failures from Fused Location.

While we are working on a fix (filtering the wrong coordinates somehow), this is unacceptable, because a failure to deliver sensible data by the OS/framework is perceived as the app's fault by users, discrediting us. We are getting a big hit in reputation because of this; subscription rates are dropping, reviews are worsening...

We have very little resources and manpower to fix this intermittent, non-reproducible issues, but Google... come on, you have BILLIONS to spend getting things right for the partners that make up the Android platform.

I really hope someone gets this fixed sometime.

Regards

il...@gmail.com <il...@gmail.com> #45Oct 14, 2019 04:29PM

Gosh. I was hoping that the issue would maybe be (silently) solved in the latest Play Services version. P3 is not the right priority for this problem. I'm sure Google own services don't suffer from it, which is quite unfair.

ji...@gmail.com <ji...@gmail.com> #46Dec 12, 2019 05:22PM

This is marked as a "Hotlist: [AOSP] duplicate". Please respond with the ticket its a duplicate of.

ka...@wikiloc.com <ka...@wikiloc.com> #47May 12, 2020 05:47PM

It would be nice if, *at the very least*, Location.getProvider() could tell us the real source of the coordinate (gps, wifi, cell tower). Right now, it always returns "fused", which doesn't give any meaningful information.

sa...@google.com <sa...@google.com> #48Aug 18, 2020 03:28PM

Status: Won't Fix (Obsolete)

Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here

https://goo.gl/TbMiIO and reference this bug for context.