Closed GoogleCodeExporter closed 9 years ago
I've also noticed this issue. It seems to have only started after the most
recent update to Google Play Services (4.1.32), although I have no evidence.
For my tracks, my chart and map look exactly like yours, with several minutes
missing from the moving time, and therefore a severely increased average moving
pace.
I've noticed that, when replaying the track in Google earth, the result is not
a smoothly moving track. Instead, the marker jumps to a position, stays still
for a few seconds, then jumps to the next position which can be hundreds of
feet away. Before this error started happening, the tracks would always move
smoothly.
I definitely have an accurate GPS signal. GPS status usually shows an accuracy
of 16/32 ft. However, it is almost as if My Tracks is only using Wi-Fi and not
GPS for location.
Original comment by 2emoo...@gmail.com
on 29 Jan 2014 at 4:29
I'm also getting this exact same problem on my Nexus 4, even with Device Mode
instead of High Accuracy. Recording a track with Strava and My Tracks running
at the same time works fine for Strava, but My Tracks still jumps around,
missing segments and thus getting a wrong moving time and average speed. This
has been happening for a few weeks already - can't exactly remember when this
started.
Original comment by tda...@gmail.com
on 1 Feb 2014 at 12:45
My tracks: 2.0.6
Play Services: 4.1.32 (978161-36)
Android: 4.4.2
Original comment by tda...@gmail.com
on 1 Feb 2014 at 12:53
same issue logged as #1444 - speed reports as '0' with the occasional jump???
how soon to a fix?
Original comment by doile...@gmail.com
on 2 Feb 2014 at 7:08
Attachments:
my log is filled with errors like this. not sure if they're coming from
MyTracks or from google play services, but it's definitely location related...
02-03 21:10:27.134 926-1355/? E/LocSvc_ApiV02﹕ W/virtual
loc_api_adapter_err LocApiV02::injectPosition(double, double, float):496]:
error! status = eLOC_CLIENT_FAILURE_INVALID_PARAMETER, inject_pos_ind.status =
eQMI_LOC_ENGINE_BUSY_V02
02-03 21:11:15.291 926-1965/? E/locSvc_IzatAdapterBase﹕ W/virtual bool
izat_core::IzatAdapterBase::requestWps(WifiRequestType): default implementation
invoked
02-03 21:11:15.291 926-1965/? E/locSvc_IzatAdapterBase﹕ W/virtual bool
izat_core::IzatAdapterBase::requestWps(WifiRequestType): default implementation
invoked
02-03 21:11:15.900 926-1965/? E/locSvc_IzatAdapterBase﹕ W/virtual bool
izat_core::IzatAdapterBase::requestWps(WifiRequestType): default implementation
invoked
02-03 21:11:15.900 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportPosition(UlpLocation&, GpsLocationExtended&,
void*, loc_sess_status, LocPosTechMask): default implementation invoked
02-03 21:11:15.900 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportPosition(UlpLocation&, GpsLocationExtended&,
void*, loc_sess_status, LocPosTechMask): default implementation invoked
02-03 21:11:16.270 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.270 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.270 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.270 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.329 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.329 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.329 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.329 926-1965/? E/LocSvc_LocAdapterBase﹕ W/virtual void
loc_core::LocAdapterBase::reportStatus(GpsStatusValue): default implementation
invoked
02-03 21:11:16.419 926-1355/? E/LocSvc_ApiV02﹕ W/virtual
loc_api_adapter_err LocApiV02::injectPosition(double, double, float):496]:
error! status = eLOC_CLIENT_FAILURE_INVALID_PARAMETER, inject_pos_ind.status =
eQMI_LOC_ENGINE_BUSY_V02
Original comment by 2emoo...@gmail.com
on 4 Feb 2014 at 2:19
Ok, I can confirm that setting location mode to "Device Only" fixed it for me
on my Nexus 4.
Not sure why I have 1 track with bad data when Device Only was supposed to be
enabled... anyway, I have recorded 3 tracks already and all are fine - I'm
comparing them to Strava data, which by the way works fine with both "High
Accuracy" and "Device Only" modes.
This same issue affects bug #1444, bug #1446, and bug #1448.
Original comment by tda...@gmail.com
on 4 Feb 2014 at 2:48
setting location mode to "Device Only" works for me as well.
Original comment by 2emoo...@gmail.com
on 4 Feb 2014 at 8:08
Setting location mode to "Device Only" fixed it for me on my Nexus 4 too. =)
Not sure if is the perfect solution, although.
Original comment by dvale...@gmail.com
on 25 Feb 2014 at 2:16
Same issue on Nexus 4 KitKat 4.4.2 and latest version of MyTracks and Play
Services. Device only mode is no option for me as my everyday activities
require lots of moving in no-GPS areas (indoors, building and surroundings
interference). I think devs should take this bug more seriously. I wonder if we
need to link this thread in the Play Services issue tracker as well...?
Original comment by kgiz...@gmail.com
on 27 Feb 2014 at 8:46
Original comment by jshih@google.com
on 2 Apr 2014 at 12:47
Original issue reported on code.google.com by
dvale...@gmail.com
on 25 Jan 2014 at 7:44Attachments: