Closed GoogleCodeExporter closed 9 years ago
Before the problem occured, I was tracking a route.
While tracking, my mobile-phone (desire 2.2) ran out of power.
After I recharged it, I started my tracks again and got the message, that the
app doesn't respond.
Original comment by meik.spe...@gmail.com
on 8 Feb 2011 at 11:10
This is a known issue for large tracks. The current implementation of
TrackRecordingService.restoreStats attempts to load last 20000 points, thus
exceeds internal cursor limit of 1MB.
cursor = providerUtils.getLocationsCursor(
recordingTrackId, -1, MyTracksConstants.MAX_LOADED_TRACK_POINTS, true);
I have a fix in my new iterator and will try to submit it ASAP.
Original comment by ba...@google.com
on 8 Feb 2011 at 11:23
Original comment by ba...@google.com
on 8 Feb 2011 at 11:24
I gave the submitter a custom apk -- one with MAX_LOADED_TRACK_POINTS set to
2000 instead of 20000. He confirmed that this solved his problem. As such,
I'm going to dup this against bart's issue 265 -- the refactoring of the
iterator.
Original comment by simmonmt@google.com
on 9 Feb 2011 at 6:32
Original comment by simmonmt@google.com
on 11 Feb 2011 at 12:24
Attachments:
Original issue reported on code.google.com by
simmonmt@google.com
on 5 Feb 2011 at 3:18Attachments: