| || |
Can I use logcat to see why Android repeatedly kills a GPS app?Or can I protect it from being killed
How do I log when and why Android kills an app?
The problem I'm having is I'm trying to use my phone as a GPS tracker to log thinks like hiking, sailing and MTB rides but after a while I pull my phone out and the tracking app is no longer running! This happen when using various apps, like Sport Tracker and MyTracks. It really makes tracking long journeys impossible!
The phone I'm using is my little Sony Ericsson X10 mini pro. Rooted, running custom Gingerbread 2.3.7 ROM (miniCM220.127.116.11), 256MB RAM. Runs very well usually, with about 35MB free most of the time. I don't use no stupid task killers.
I suspect that due to the phone's limited RAM, something is periodically starting up (play services, for example) and Android is killing my GPS app to reclaim RAM because the process has been running for a long time with no user input.
My question is how can I use logcat to find out when and why my GPS app is getting killed? Or if there are any apps that startup at the same time the GPS app gets killed?
An additional question would be, can I somehow raise the priority of my GPS app or somehow protect it from being auto-killed?
I have CatLog installed,and I can see and save the logs but I don't know what I'm looking for. Searching on google only brings up **** about task killers and battery life. I think the keywords 'Android' + 'killer' attracts allthe rubbish from the RAM free task killer debate...