I'm using an iPhone 6 Plus with SWConnect. I've had essentially the same setup for about two years now.
The last two trips I've taken, there are long stretches where my location data isn't displayed. I presume this is a SWConnect problem, and not SpotWalla, but is there any settings or anything I can change to prevent this from happening?
What's weird is that as far as I know, I'm not doing anything differently when the location data disappears. There may be stretches where I don't have a cell phone signal, but SWConnect has always buffered that data and sent it when a connection was available, but recently it's not always reliable, even when cell data is available again.
Here are my trips with the long sections of missing data:
Hey, Jamie. I believe the only way SWConnect would not be able to acquire your location and buffer it until it was able to connect to SpotWalla, would be if it couldn't acquire your location using GPS. Are these possibly explainable due to no clear GPS signal? Not sure. It's a difficult thing to diagnose after the fact.
I wouldn't let the lack of updates tarnish SWConnect. It could be a sign of a stable, dependable application, right?
I'll ping Ray, the SWConnect developer, and see if he's able to provide any insight into the issue.
My phone is on the dash of my car essentially the entire trip. I used navigation software the entire time without any issues. I can confidently rule out the lack of GPS location information.
One thing I noticed several times during my trip, and I don't know if this is relevant or not, but when I'd open the app, for the first half a second or so, the location data at the bottom of the screen was written in red type. And then it would change to the standard whitish grey. The red letters seemed to be an indication that it didn't have a GPS position...
I'm not a developer, so I shouldn't judge whether or not an app is stable or not, but I do know that no software is bug-free, and any software I use is updated periodically to fix bugs or add a new feature or two. So when it came to SWConnect and I saw the most recent version was released well over a year ago, it made me wonder if the developer was still supporting the app.
Thanks for looking into this, Jason. I've used SWConnect without much trouble for a couple of years now. This issue, while not entirely new, has been much worse the last two weekend trips I've taken.
Hi, sorry for the delayed response. Haven't been to the forum in a bit, and needed to get my account setup. I am the author of SWConnect. Thank you for making one of your trips have downloadable data, as I was able to look at that, and see some of the debug info that is in the messages part of each location.
Actually, it does appear you are having issues with GPS accuracy. You even touched upon it above in that SWConnect displays GPS locations in red if they fall below the accuracy requested, which is 10 meter. Those locations are essentially ignored. Given that you've seen the red text, that matches with what I saw in your track data, i.e. data counts increasing, but not being used.
There are three things which cause the data to be ignored:
1. GPS accuracy too low 2. Time threshold has not be crossed (you had it set for 8 minutes in one trip, and 5 in the other) 3. You haven't traveled 100 meters since last location sent (so you don't get multiple hits while parked to eat, etc)
So, the big question is why is your location information coming in with poor accuracy. What maybe has changed? You've indicated you've put the phone on the dash, which should be perfect. I assume in the last couple of years that you've changed phones. Did this start happening wth a new phone? How about a new case? I've seen examples where cases limit both cellular signals, but also GPS accuracy.
If you would like to help get to the bottom, and fix, this issue I can fairly easy generate a new build with (1) a relaxed GPS accuracy, and (2) some extra debug in the message to further point to whether or not this is the issue. Let me know if you'd like to do this. I can probably spend a bit of time today getting a new build ready, but I leave on Sunday for a week vacation, so we will have to work fast, or wait a week. Actually, I could probably bring my laptop with me on vacation too.
Let me know if you'd like to do this, and pass on your email info to email@example.com and we'll get this figured out.
I have rebuilt SWconnect with a relaxed GPS location accuracy (from 10.0 to 50.0 meters), which hopefully should solve your issues in those out of way places. I've also added the returned accuracy in the debug message in the location report, so we might be able to tell if that was the problem (i.e. accuracy > 10.0).
Please contact me at firstname.lastname@example.org and I will get you setup to test this build.
OK I've been able to duplicate the issue you're reporting. It seems that the deferred updates used on newer hardware is now somehow failing to deliver updates in the background. So, basically from what I am seeing is that I am only getting updates when the app is running in the foreground.
Still looking at why this is happening and hope to have a fix soon.
OK, it seems I was likely right about my first assessment, and that SWConnect was receiving points where the accuracy was too low, and ignoring them. It seems my newer phone (6+) suffers from a similar lack of accuracy. By rebuilding I was able to see accuracy values at 30 or 50 meters, when typically once the GPS got going, I always had 10 meter accuracy, which is what the program expects.
So, that's the good news, the fix SHOULD have been easy. BUT NO. Any location services app built now with current development tools (i.e. the IOS 9 toolset) has changes that need to be made. It appears that Apple changed the deferred updates that SWConnect used to limit battery use while running in the background. With deferred updates, the GPS would buffer up a set of location reports, and hold them until a time of 5 minutes, or 5 miles had passed, and then it would send multiple updates in one time.
Well, this works differently now, and the reason that I *thought* I was seeing your issues, was that when my phone when into the background mode, updates stopped completely, which looked like I was seeing the gaps you showed in your trip reports. I've been researching the changes, but when I make the suggested changes, the location services seems to be on constantly in the background, and although this sort of fixes the issue, I'm concerned about battery life.
So, I am going to do some more research,and possibly contact Apple with a support issue about this. I've seen others report similarly, with no clear suggestions being offered.