You are hereForums / Android Software / Android Development / Tracking feature locks up my HTC Legend
Tracking feature locks up my HTC Legend
Recently tried out BCN with my new phone and attempted to use the tracking feature this weekend while exploring unmarked forestry roads near Golden, BC. I really like the tracking feature but as soon as I hit the red circle to start it, the screen freezes. If I hit the blue square right away, it usually comes back after a few seconds further pause. If I wait and come back to it later down the trail, I find that it has only tracked me for part of the time before locking up. Android then does a Forced Close for BCN and sometimes I have to reboot the phone before it will come back up.
I suspect that my processor is underpowered for the tracking, but the HTC Legend isn't the slowest thing around so I don't know... Would it be possible to have a selectable frequency for the tracking? Every X seconds, or X meters? Something to reduce the processing power so I can have it track me and use it to navigate at the same time...
I look forward to purchasing the application as soon as this as the locking up is fixed! It will be great for snowmobiling and recording highmarks!
Thanks,
-Owen
Share This Page
I'm still catching up after my trek.
Sounds like something is wrong for sure. There is some processing with tracking, but I don't think that is the bottleneck. Writing to disk could be.
Just to confirm, is this while driving? Our default settings for distance, speed, and time interval may not be the best for driving.
In any case, to see if there are some actual crashes happening, coudl you install the app called Log Collector and try to email a log to support at this website right after the problem occurs? I may be able to glean something based on this.
Nathan
I've done some testing with track marking while driving and found the performance unacceptable.
I'll be finding out if this can best be fixed by adjusting the intervals, or if it requires more drastic action.
Hi Nathan,
I've found that it works fine while hiking but locks up after a while when quadding and almost immediately in some cases while driving on a highway. It's definitely speed related. The "force close" doesn't always engage either and I often just have a black screen on my phone and have to pop out the battery... pretty significant bug.
An option for the breadcrumb frequency would be best I think... takes a waypoint every 5/10/20/30/60 seconds or something... probably easier to program in than an distance based one which would have to calculate distance travelled constantly.
I'll try to check the forum more regularly... kinda forgot posting on it.
Cheers,
-Owen
Friday's release limits trackign updates to about seven seconds. This does not freeze for me any more.
It may be configurable in future, but until I've done some more profiling, I don't think it is safe to allow intervals smaller than seven seconds just yet.