Background mode logical bug?
I have found what I think to be a bug but want to get some more input from all to help confirm or deny my findings. Last week I was driving through NYC. I got stuck in bumper-to-bumper traffic for about an hour. Waze was running, but in the background since I wasn't moving. After traffic cleared up I didn't re-open waze until 70 mi. later where I wanted to see what the conditions were as I approached known speed traps on the NJ TPKE. When I later checked on-line the miles I logged between where waze when to sleep and when I re-opened the app were lost. The miles prior to the traffic and after I re-opened were properly captured.
Here is some questions.
1. How long do I have to be stationary before waze goes to sleep when in background mode?
2. Do I have to be completely stopped for it to go to sleep (as in stop logging activity)?
3. Will waze wake up on its own if I start moving again after it has gone to sleep? Or do I have to wake it up manually?
FYI. I am using the latest version of the iPhone app.
Here is some questions.
1. How long do I have to be stationary before waze goes to sleep when in background mode?
2. Do I have to be completely stopped for it to go to sleep (as in stop logging activity)?
3. Will waze wake up on its own if I start moving again after it has gone to sleep? Or do I have to wake it up manually?
FYI. I am using the latest version of the iPhone app.
Re: Background mode logical bug?