Still encountering bug upon APP initialization w/latest rel

[AlanOfTheBerg]

Exit Waze using home button.

Like gerben said, use the actual correct way to Exit Waze which is the Switch Off button in the main menu. Otherwise, Waze just runs in the background and then you force-kill it. Not the right way to do it at all.

[sivigamer]

Exit Waze using home button.

Like gerben said, use the actual correct way to Exit Waze which is the Switch Off button in the main menu. Otherwise, Waze just runs in the background and then you force-kill it. Not the right way to do it at all.

Using an in app menu is not the normal way to exit an iOS app or any mobile app for that matter. It shouldn't give errors for quitting.

[AlanOfTheBerg]

Exit Waze using home button.

Like gerben said, use the actual correct way to Exit Waze which is the Switch Off button in the main menu. Otherwise, Waze just runs in the background and then you force-kill it. Not the right way to do it at all.

Using an in app menu is not the normal way to exit an iOS app or any mobile app for that matter. It shouldn't give errors for quitting.

Waze is not a "normal" iOS app and therefore requires something different for proper exit. Apple Maps doesn't quit when I background it either if it's navigation mode. Are you calling that not "normal" as well? There are certain apps which have flags to work in the background, such as VoIP and navigation apps. Many of them do not exit when hitting the home button. That is just the way these kinds of apps are designed to work. Users need to know this to understand how to properly use the apps.

[HarveyMRichards]

Like gerben said, use the actual correct way to Exit Waze which is the Switch Off button in the main menu. Otherwise, Waze just runs in the background and then you force-kill it. Not the right way to do it at all.

Using an in app menu is not the normal way to exit an iOS app or any mobile app for that matter. It shouldn't give errors for quitting.

Waze is not a "normal" iOS app and therefore requires something different for proper exit. Apple Maps doesn't quit when I background it either if it's navigation mode. Are you calling that not "normal" as well? There are certain apps which have flags to work in the background, such as VoIP and navigation apps. Many of them do not exit when hitting the home button. That is just the way these kinds of apps are designed to work. Users need to know this to understand how to properly use the apps.

I think sivigamer is saying that the normal iOS way to fully exit an app is to double click the home button, which brings up the recent apps, hold down an app and when the app jiggles, click on the upper left (-) button.

So, when I use the switch off button within the Waze menu, does Waze cease to operate even though it's still active in the recent apps list?

[AlanOfTheBerg]

I think sivigamer is saying that the normal iOS way to fully exit an app is to double click the home button, which brings up the recent apps, hold down an app and when the app jiggles, click on the upper left (-) button.

So, when I use the switch off button within the Waze menu, does Waze cease to operate even though it's still active in the recent apps list?

Apps in the multi-task list are not necessarily running. All apps recently used, running or not, are listed there. Waze happens to keep running when the home button is tapped. Most applications are not written this way and cease operation and receive no CPU time nor memory allocation once they exit. The applications in the multitask list are, by and large, not using CPU or memory.

When you exit Waze using the "Switch off" button in the main menu or use one of the various voice commands to accomplish the same, it properly exits and is allowed to finish upload of any pending drive data before terminating.

Search the 'net and you'll find many articles about people's misunderstanding of this list.

[HarveyMRichards]

Apps in the multi-task list are not necessarily running. All apps recently used, running or not, are listed there. Waze happens to keep running when the home button is tapped. Most applications are not written this way and cease operation and receive no CPU time nor memory allocation once they exit. The applications in the multitask list are, by and large, not using CPU or memory.

When you exit Waze using the "Switch off" button in the main menu or use one of the various voice commands to accomplish the same, it properly exits and is allowed to finish upload of any pending drive data before terminating.

Search the 'net and you'll find many articles about people's misunderstanding of this list.

I have found that my GPS apps, Navigon, Motion X, and Trail Maps to name a few, will continue to run while still in the mutli-task list. In fact they will run my battery down very quickly. Therefore, I try to make sure I remove them from the multi-task list.

[AlanOfTheBerg]

I have found that my GPS apps, Navigon, Motion X, and Trail Maps to name a few, will continue to run while still in the mutli-task list. In fact they will run my battery down very quickly. Therefore, I try to make sure I remove them from the multi-task list.

I am curious how one proves they are running, exactly? I would love to be able to find that out. Anecdotal info is one thing, but something which could show CPU time would be excellent. I have had no issues with Waze when shut down the correct way, FYI. The GPS icon stays on for 10-15 seconds, but I think that's an iOS lag.

[HarveyMRichards]

I am curious how one proves they are running, exactly? I would love to be able to find that out. Anecdotal info is one thing, but something which could show CPU time would be excellent. I have had no issues with Waze when shut down the correct way, FYI. The GPS icon stays on for 10-15 seconds, but I think that's an iOS lag.

I have an app, System Max, https://itunes.apple.com/us/app/system-monitor-battery-max/id386118145?mt=8 that is supposed to show running processes. I'm not sure what processes would be associated with Waze.

Will Waze run in the background?

[AlanOfTheBerg]

Will Waze run in the background?

Oh, yes, definitely. It is designed to run in the background at all times, navigation mode or not. Lots of drivers run Waze in non-navigation mode. The only way to properly quit the app is to use the function within the app.

[rcenteno_davis]

I'd like to chime in that Waze is the only app I've seen that has an in-app menu item for "shutting" down. I usually remove apps from the running list by making the icon dance and X-ing it our from the taskbar.

Now I haven't written any iOS app before (and this is directed at the app developers) but is there a way to detect the difference between a true app crash vs. the removal-by-icon-dance?