No longer finds GPS signal

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Every morning I step outside and press record.
2. After as long as 40 minutes, still no signal.
3. Worked perfectly until Wed. prior to Thanksgiving.

I have not made any known changes on my Nexus phone.

What is the expected output? What do you see instead?

Typically it takes 16 - 30 seconds to locate and begin tracking.

What version of MyTracks are you using? On what version of Android? On what
phone?

My Track version v2.0.8
Android version 5.0
  Kernel version: 3.4.0-perf-g60eefcd
  android-build@vpbs1.mtv.corp.google.com #1
  Fri Oct 10 18:28:38 UTC 2014
Device: Nexus 4

If possible please provide a log by uploading here.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by glbe...@gmail.com on 2 Dec 2014 at 2:53

[GoogleCodeExporter]

I'm having the same problem with My Tracks 2.0.10 running on Android 5.01/ LG 
G3. My Tracks seems to be recording but at the end of a multi mile walk "Stats" 
will show a distance of 27 ft. I'll try the workaround tomorrow.

Original comment by phillo12...@gmail.com on 9 Aug 2015 at 7:46

[GoogleCodeExporter]

I'm having the same problem with My Tracks 2.0.10 running on Android 5.1.1 on a 
Note 4.  It is nearly always "Waiting for GPS Signal" and has no accuracy.

Original comment by rmapear...@gmail.com on 11 Aug 2015 at 12:40

[GoogleCodeExporter]

I had to install "GPS Status Test & Fix - No Ads" and since that time
'MyTracks' has worked.  I start GPS Status and allow it to register a
signal then start MyTracks and so far, so good.

Original comment by glbe...@gmail.com on 11 Aug 2015 at 12:55

[GoogleCodeExporter]

This issue severely hurts the value of MyTracks.  I would guess this should be 
higher than MEDIUM.  See snapshot attached.

In mid-July 2015, tracks were gathered accurately (no gaps) on my daily walks.  
Since early August 2015 (through at least today 8/19/15), most if not all 
tracks show large gaps.  For example, on one six mile walk, around San Jose 
Airport area, the distance was recorded as 4.5 miles, but actual distance was 
more like 5.5-6.0 miles.  I NEVER receive a "Waiting for GPS Signal" message, 
different from many of the recent commenters, suggesting possibly two issues 
here.

Attached screenshot of map showing gaps in the track.  My longest stops were 4 
minutes (to buy a sandwich, paused, tracked fine) and 2 minutes doing 
stretches.  I was running Google Play Music listening to audio most of the way. 
 Interestingly Google Play Music cut out on me a 4-5 times, but the locations 
don't correlate with map cut outs.  I seldom run Google Play Music on my walks, 
so Google Play Music is not a contributor to the problem (to my knowledge).

Samsung S5, Verizon
Android 5.0 (See below)
Google Play services 7.8.99 (2134222-438)
My Tracks 2.0.10

System Updates shows:
    Problems during and before the most recent update.
Last system update:  to G900VVRU2B0G5, Applied on Aug  14, 2015
    Problems during some part of this time period, yes.
    Yet, definitely no prolems the week after July 10.
Previous update:     to G900VVRU2B0E1, Applied on July 10, 2015
  No problems before July 10, that I know of.  Used it less before this time.

Thanks.

Original comment by alan.d.c...@gmail.com on 20 Aug 2015 at 12:47

Attachments:

• MapSJCAirportLoopGaps08122015.png

[GoogleCodeExporter]

I used to use MyTracks often for kayaking, hiking, biking, for trips to obscure 
stores, and even long drives across multiple states. It was the best route 
recorder out there. It worked flawlessly on my Samsung Galaxy S2 and S3. Since 
I got my Galaxy Note 3 it's been non-functional; all I ever see is "Waiting for 
GPS signal". I can use GPS for other apps, but not this one. I've tried every 
work-around and fix I could find on this and other sites, but nothing has 
worked. 

Samsung, Galaxy Note 3, US Cellular
Android 4.4.2 
Google Play services 7.8.99 (2134222-038)
MyTracks 2.0.10

I agree, this should be much higher priority than Medium. It's useless to too 
many of us as is.

Original comment by skf...@gmail.com on 20 Aug 2015 at 6:38

[GoogleCodeExporter]

Ditto for all of the above for my LG.  It was working great than all of a 
sudden "waiting . . ." and big gaps in the map and recordings of a few feet.  
Besides complex work arounds, how can this be simply fixed?  Is anyone reading 
this?  I really like My Tracks, but this is ridiculous.

Original comment by dnvr...@gmail.com on 20 Aug 2015 at 10:05

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Listen to the people please!

Original comment by jiveho...@gmail.com on 23 Aug 2015 at 4:11

[GoogleCodeExporter]

I also echo the above problem described in #54. Although the app starts 
normally and visibly tracks my progress when I have the screen on and the app 
enabled, it seems to track very intermittently or not at all when the device is 
locked and the screen is off. I can confirm I recorded a track normally on 
7/25. It did not work 8/1 and still did not work on 8/22. The phone was 
rebooted multiple times in between these dates.

The app tracked just 1.75 miles of a 12 mile trip on 8/22 and 6.6 miles of a 
~14 mile trip on 8/1. Both trips were in areas I've successfully used My Tracks 
in the past, so I don't believe GPS reception is the problem.

For what it's worth, I turned the screen off (via the power button) and after a 
few seconds of movement it still gave be a voice prompt indicating it had 
tracked movement. This was before the password-based lock had happened (set for 
a 30 second delay). 

Whenever I stopped and unlocked my phone to view progress, I could see the GPS 
icon. The app appeared to be functioning normally and I didn't see a "Waiting 
for GPS message". However generally the app had not been tracking my progress 
prior to unlocking, and tracking start up again in several seconds each time 
and worked as long as the screen was on and phone was unlocked.

Google Nexus 4, T-Mobile
Android 5.1.1
My Tracks 2.0.10

Original comment by benjamin...@gmail.com on 23 Aug 2015 at 4:32

[GoogleCodeExporter]

I'm having the same problem as described in post 54 and post 59. Tracking cuts 
in and out intermittently. This has been an ongoing problem for a few months.
Galaxy S6
Android 5.1.1
Verizon

Original comment by 22fasted...@gmail.com on 24 Aug 2015 at 6:58

[GoogleCodeExporter]

OK, having come out of the software industry, I know that if an issue occurs 
when a client is using your software it is your issue - regardless of the cause 
- but I cannot help but wonder if these issues are in some way related to 
hardware or modifications to code by specific vendors?  When I initially posted 
- Dec. 2, 2014 - I was having issues with a "Google Nexus" phone manufactured 
by LG.  Now I am on a Nexus 6 and I have had exactly zero issues with "My 
Tracks"  I use it frequently and it has been pretty darn solid.  But it is on a 
phone optimized for use with Google Android.  Any thoughts?

Original comment by glbe...@gmail.com on 24 Aug 2015 at 8:11

[GoogleCodeExporter]

I am using a Google Phone (Motorola Droid Maxx XT-1080) and it happens to me. 
This  __IS__  a Google device and therefore should not be happening at all, at 
a minimum, right?   :)

I could see if I was the only one on this thread who was just chugging along 
without a problem, and every other vendor had problems, but I am on a Google 
phone (effectively, Motorola is Google) ... so, strikes are MAJOR against the 
My Tracks folks because I should be just moving along without issue ...

:)

Original comment by SGlai...@gmail.com on 24 Aug 2015 at 8:30