Hi

This sounds like the device you are using does not have enough memory to run both Torque *and* Google Navigation, so android is closing Torque down so it can start Google Nav. Unfortunately there is little I can do about this as google nav is quite a heavyweight application. What phone are you using?

There is an option to go straight to the 'Realtime Display' in the settings when the app is started. You probably want to enable this option in the settings.

Trip counters aren't reset if the app isn't forced to quit (due to your handset running out of memory, *OR* 'Spare Tools' on the handset has been configured to immediately quit apps when applications are switched (eg setting "Aggressive process management" will cause apps to be forced-quit by android)

Quote from admin on October 13, 2011
Hi

This sounds like the device you are using does not have enough memory to run both Torque *and* Google Navigation, so android is closing Torque down so it can start Google Nav. Unfortunately there is little I can do about this as google nav is quite a heavyweight application. What phone are you using?

It's a Nexus One. Back then it was cutting edge 🙂 I never ran in to memory problem before, but I will try to check memory usage next time this happens.

There is an option to go straight to the 'Realtime Display' in the settings when the app is started. You probably want to enable this option in the settings.

This option _is_ enabled, as I mentioned before.

Trip counters aren't reset if the app isn't forced to quit (due to your handset running out of memory, *OR* 'Spare Tools' on the handset has been configured to immediately quit apps when applications are switched (eg setting "Aggressive process management" will cause apps to be forced-quit by android)
There is no way to keep track of data even at force close? Maybe periodically writing to a database? I seem to have this reset problem on average once per 4 time switching apps, and my phone is not on the low end of the specs even though it's no longer the best, so I imagine this is not an uncommon problem.

It shouldn't happen on an N1 (most of the app was developed on it when I was lucky enough to get one from google).

The app shouldn't quit, as you are then 'missing' data for a segment of your trip. I'd much rather stop it from being killed off by android. It does at the moment sound as if the process management is set to aggressive on the device (even a lowly xperia x10 mini pro is able to keep torque running when switching to google nav, so the N1 should definately not be closing it). The app is also marked as persistent. Are you sure you don't have a task manager going around killing things off or the aggressive process managment option enabled?

I'll see if I can improve on this a little, however if you have a task manager going around killing apps then the app won't get a chance to save any data as the task manager will just kill the process (Task managers are generally bad news as they can easily cause more problems than they 'appear' to solve - ie: killing an app halfway through it writing a config file is a good way to cause lots of odd force-close behaviour (as that config file would then be corrupted))

Nope, neither a task killer is turned on nor the aggressive management is turned on. In fact, I don't have a task killer installed and my spared parts app doesn't have the aggresive management option. Torque is the only the app I have that seem to have resume problems...

Also, last time I was driving, Torque also stopped (lost all recorded numbers) at an incoming call. After the incoming call screen goes away (didn't pick up the call since I was driving on the highway!) Torque resumed, but all numbers started all over.

I understand that losing data in the middle of recording isn't ideal, but I much, much rather lose a few seconds of data than losing all numbers for the trip!

Hi

Not using a task killer is good. And thanks for checking spare parts. It sounds like android has a lot running and it is killing the app service when switching tasks.

Android will only do this if it's low on free RAM to use and needs to shut something down so another process can start (ie: your phone call). Normal usage on android won't shut tasks down when switching (unless you are running a custom ROM which has this enabled).

Android can quite happily shut activities down, though should start them up again afterwards.

I'll have a play here in the next version. There is a foreground service that will prevent apps from being shutdown by android (though I have been trying to avoid using it as I didn't want Torque to be that invasive). I may add a setting for permanent running

I have the same problem.
Android 2.3.3 on HTC Desire HD.
A lot of RAM but still the same problem.
Torque still appears in the notification bar as running but when coming back to it from a nav app, it's loading it as if it was previously closed. And it resets all the trip data.
Would be useful if you could force Android not to close this app... Or reduce the memory usage when in the background (perhaps lower the polling rate or something)...

The pro app is already marked as persistent so android should not be closing it. Are you running a custom ROM, firmware, or with special settings (such as aggressive process management which will shutdown lots of applications)

The pro app is already highly optimised for running in the background and consumes little resources (practically no CPU if inactive, and very little if in the background and connected to the adapter) (quite a few people use it in 'permanent' mode)

Not running any custom ROM, just the one I got with the device. Not rooted, not nothing... And the trip still resets whenever I switch to a different app.

Hi

What network is your phone on? eg: 3,UK (etc) and what version of the app are you using lite/pro, latest market version?

Thanks

Ian

Latest pro version. Network doesn't seem to be relevant (just came back from the US and were using various different carriers).

Hi, I need to know the carrier as people like '3' make the OS aggressive at closing apps if your phone is from them. - if you have it on the 3 network, this may well be the issue.

Same issue to me. If you minimize the app all the values are getting to zero and you start over. After getting back to Torque you need to reselect the realtime information.

The only way to keep the data alive is

1. Dont switch it off
2. Only power off the screen and power back on.

If you make a call (values reset)
If you manually minimize (home button) values reset
etc
etc

Hi

I'm trying to track this down - it appears to be an OS configuration issue (the rom your provider puts on the phone, but am trying to get more information on it)

Can you post the following:

*The mobile network your device was purchased on (Sprint, Vodafone, 3, att, (etc)

* The mobile device hardware you have (HTC Evo, HTC Magic, Samsung galaxy (etc))

* The kernel version you are using (Settings menu->About->Kernel version)

* And the android version (2.3.3, 2.1, (etc))

* If you have 'Spare Parts', some memory managment or 'task killer' app installed

That'll help me pin down what this is (it's driving me a bit nuts as I can't reproduce the issue here).

HTC Desire (unbranded, free of providers)
Android Version 2.3.7,
kernel version 2.6.37.6-cyanogenmod-g8913be8
Build number MIUI-1.11.4

The issue is like pressing the back button when you are in realtime information. It gets to the main torque menu. So by getting inside realtime information again, all the values are starting from zero again. (I assume that logging still logs but I have to confirm it after data projection)

Edit: Yes logging still goes on.

I can't explain it but it started working properly now. I played around with the logging options in the settings and now everything works (almost) fine.
I'm using HTC Desire HD (Unbranded), Android 2.3.3, no task killers.

So for me the problem seems to be solved, though I can't explain what caused it or what made it go away.

A problem that I still have though, that may be related:
Load torque - it starts in the real-time information panel (like I defined in the settings, that's fine). Click home. Torque's icon appears in the app drawer. Click on that icon and torque loads the main screen (the one with the scrolling wheel) and not the panel I was looking at a minute ago (data doesn't get zeroed any more, like I mentioned earlier).

If however, I load torque, then I load a different app from the drawer, then I close that app -- then torque is back full screen in the panel was looking at.

This feels like a bug that's not really device dependent, more like a buggy onload funtion...

I have the same issue, and have had it since I downloaded torque (6+ month ago). If I leave Torque for a phone call, text message, navigation, etc, when I come back the trip data is reset. It doesn't always happen the second I leave Torque. If I go from Torque to Navigation and back within 20-30 seconds, Torque will be fine. However, if I leave for long enough (4,5,10 min?) the trip data is reset and sometimes it has to reconnect to the ECU (even though the taskbar image is green).

T-mobile
HTC G2 (Desire Z)
2.6.35.10-g96de068
htc-kernal@and18-2#1
2.3.4
No task manager software installed

Hi

This will be android shutting down the application when it thinks you no longer need it - It may be mitigated if you use the TorqueWidget application (which keeps a service alive).

I've just pushed out 1.5.66, so will have some proper time to look at this in 1.5.68 (it shouldn't be an issue on devices which use googles recommended settings for android (in terms of how aggressive to kill processes), but some phone providers roms may have these adjusted)

Purchasing the Torque widget seemed to work! Left Torque in the background for 20 minutes at a time while using navigation and it never reset.

That's good - it means that it is very likely what I suspect (android removing currently ''unused'' apps).

I've had to send out 1.5.68 to address a bug, so will likely fix this in 1.5.70/1.5.72