Closed GoogleCodeExporter closed 9 years ago
An update on this, the Nexus 4 specifically seems to still pick wifi access
points when set to 'device only'.
Original comment by homebran...@gmail.com
on 30 Jan 2014 at 10:28
I can confirm that my Nexus 4 is suffering from this issue too. No amount of
changing settings resolves it. I have run GPX Logger simultaneous, this tracks
perfect, while Mytracks jumps all over the place. I have attached a screen
grab of chart view to show the problem.
Original comment by jamesbla...@googlemail.com
on 30 Jan 2014 at 11:14
Attachments:
Same here. I left both My Tracks and Strava running, and My Tracks had lots of
problems with location. It's a Nexus 4 and putting it on Device only does not
fix the issue.
Original comment by tda...@gmail.com
on 1 Feb 2014 at 12:37
Same issue as defect report #1448
Original comment by rwz...@gmail.com
on 2 Feb 2014 at 9:25
For me the issue started when Google Play Services updated to 4.1.32. Setting
the Location Mode to Device Only worked for me (using a Nexus 5), My Tracks is
now recording properly again, thanks for the tip.
I have no idea if this will work, but for those that are still having the issue
even when setting the location mode to device only, you could try turning off
wifi and disabling the wifi scanning always available
(Settings>Wi-Fi>Advanced>uncheck Scanning always available).
The Secure Settings app/plugin for Tasker exposes the Location Mode (does
require root). I've been able to automate it using Tasker and the Secure
Settings plugin so when I open up My Tracks the Location Mode gets changed to
Device Only.
Original comment by scottbau...@gmail.com
on 3 Feb 2014 at 5:21
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 works fine even with both "High Accuracy"
and "Device Only" modes.
This is the issue that affects bug #1443 and bug #1444.
Original comment by tda...@gmail.com
on 4 Feb 2014 at 2:46
I have exactly the same issue on Nexus 5 but setting location mode to "device
only" does not fix the problem. Sometimes the record is fine but most of the
cases it looks like in screenshot above.
Original comment by kej...@gmail.com
on 23 Feb 2014 at 8:10
Is this bug going to be fixed in a future release? Issues #1441, #1443, #1444,
#1450, #1452, #1463, #1464, #1483 all seem to relate to the same problem …
The workaround to switch location mode to “Device Only” works fine most of
the time, but it's quite cumbersome to always change it back to “High
Accuracy” after a track has been recorded, which is necessary, if you're
using Google Now’s location based services et cetera.
Original comment by lehmann....@gmail.com
on 1 Apr 2014 at 4:04
Issue 1483 has been merged into this issue.
Original comment by jshih@google.com
on 2 Apr 2014 at 12:42
Issue 1441 has been merged into this issue.
Original comment by jshih@google.com
on 2 Apr 2014 at 12:46
Issue 1443 has been merged into this issue.
Original comment by jshih@google.com
on 2 Apr 2014 at 12:47
Issue 1444 has been merged into this issue.
Original comment by jshih@google.com
on 2 Apr 2014 at 12:52
Issue 1452 has been merged into this issue.
Original comment by jshih@google.com
on 2 Apr 2014 at 1:02
Before my run today, I switched my location settings to "device only" (as usual
for the past few months) but I got pretty awful data. Last Tuesday, I recorded
a track with "device only" and it worked perfectly, as it has been for the past
few months, since this bug first appeared.
However, today, my track stats say 1:58:28 moving time and 2:06:20 total time.
I was moving the entire time, so there are 8 minutes not accounted for. Also my
total distance was about a half mile off. This obviously affects my avg pace
and my avg moving pace.
These symptoms have usually happened with "high accuracy mode" but now they are
appearing with "device only" as well.
Original comment by 2emoo...@gmail.com
on 18 Apr 2014 at 10:45
This is fixed in the next version.
In version 2.0.7, one will be able to use My Tracks is any mode "High accuracy"
or "Device only".
Original comment by jshih@google.com
on 11 Jun 2014 at 8:30
Fixed in 2.0.7 my butt! 2.0.7 is nowhere to be found. You cannot close a bug
until software that fixes it is RELEASED!.
Original comment by rwz...@gmail.com
on 14 Jun 2014 at 7:00
I just noticed 2.0.7 is available as an update on google play store.
Original comment by patrick....@gmail.com
on 18 Jun 2014 at 10:22
Still broken for me, Android 4.4 and Tracks 2.0.7
Original comment by pd.ya...@gmail.com
on 25 Sep 2014 at 9:17
Original issue reported on code.google.com by
homebran...@gmail.com
on 29 Jan 2014 at 9:55Attachments: