BTStackGPS freezes after about 50 minutes on my iPod Touch

[GoogleCodeExporter]

I'm using RunKeeper with BTStackGPS to capture my GPS track logs while jogging. 
 In general I've gotten everything working nicely, except that my tracks are 
getting truncated at about 45-50 minutes. The clock keeps running but no more 
GPS data is collected. I thought maybe it's running out of cache for the data, 
since I cannot upload data until I return home to wifi.   I've been blaming 
RunKeeper for this, since one test with SportyPal captured my entire run, no 
truncation.  (SportyPal collects and uploads less data points)

But yesterday when RK again quit tracking after about 45 min, I looked at 
BTStackGPS and noticed that although data was displayed, it was static and not 
updating.  Can't pin that on RunKeeper.

Details:  I'm running BTStack on my iPod Touch 3rd gen, iOS 5.0.1, jailbroken 
with the latest RedSn0w.  It works fine with my external bluetooth GPS puck.  
When I run, I start music playing and then leave RunKeeper on the screen with 
the system's auto-lock off.  To save battery I use a little free app called 
ScreenDim.  It blacks out the screen with just a swipe, without locking it.  A 
one-hour workout drains less than 25% of the battery.

Original issue reported on code.google.com by whenders...@gmail.com on 5 Feb 2012 at 6:42

[GoogleCodeExporter]

I should add that the bluetooth connection is maintained until I disconnect it. 
 The loss of GPS track logging does NOT coincide with losing a connection to 
the GPS puck, which would do an auto-power-down after a few minutes if it lost 
the BT connection.  This does NOT happen - it's on throughout.

Original comment by whenders...@gmail.com on 5 Feb 2012 at 6:48

[GoogleCodeExporter]

Update:  Although I occasionally get lucky and record a track over an hour, 
most of the time BTstack freezes before that.  It happens with both RunKeeper 
and SportyPal, probably the two leading apps for this.  As I noted before, the 
bluetooth connection is maintained and the running app continues running, but 
the GPS data flow is frozen.  The BTstackGPS panel shows no clock advance and 
is completely static.

I have to conclude this is a problem with BTStack and I'm going to go try 
RoqyBT4.  If that works, I'll regret having wasted my money and time trying to 
go cheap with BTstack.  If RoqtBT doesn't work, I'll really be mad!!

Original comment by whenders...@gmail.com on 4 Mar 2012 at 7:08

[GoogleCodeExporter]

First track with RoqyBT4 was 54 minutes, which is longer than I could expect 
from BTstack.  If this holds up, I'll switch and not look back.

Original comment by whenders...@gmail.com on 5 Mar 2012 at 2:14

[GoogleCodeExporter]

OK, just completed a run over 75 minutes and RoqyBT4 performed flawlessly.  I 
NEVER got a track that long with BTstack, rarely even close.  So RoqyBT at 5 
euros ($6.83 I think) is a bargain compared to BTstack $5.

Original comment by whenders...@gmail.com on 6 Mar 2012 at 2:14

[GoogleCodeExporter]

Hi. Please try the BTstack GPS 1.7 update and let me know if that fixes your 
problem. 1.7. has a new and much better RFCOMM implementation.

Original comment by matthias.ringwald@gmail.com on 10 Dec 2012 at 10:47

• Changed state: Done

[GoogleCodeExporter]

Sorry for the delay.  Last night I finally got around to trying the latest 
version.  I recorded a 48 minute track in Runkeeper without issues.  This would 
have been unlikely before.  I can't really say the problem is solved until I 
get a few successful tracks over 50 minutes, but so far so good!  Thanks.

Original comment by whenders...@gmail.com on 13 Apr 2013 at 2:42