Inhibit power manegement while exporting

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a long track (I had something around 18,000 points)
2. Stop and save, then export to GPX
3. Don't touch the phone, watch it go to sleep
4. Switch it on again and check status

What is the expected output? What do you see instead?
Expected: prompt and smooth export of all points.
What I see instead: Screen turns off after selected interval, (apparently) 
interrupting export. When I turn the screen back on manually, export is still 
where it was when the screen turned off and will freeze for a while before it 
resumes.

What version of the product are you using (See "About" screen)?
0.5.1 (IIRC this also happened on 0.5.2, which I used on my other phone)

Make/model of your device, and Android version?
Neo Freerunner, Android 1.5 (Cupcake) 0.2.0 RC2 (see "Android on Freerunner" on 
Google Code) - my main device used for tracking
Other phone (not thoroughly tested on this one): GeeksPhone One, Android 2.3 
(Gingerbread, RCMod 4.0.0)

Please provide any additional information below.
The issue is particularly pronounced on the Freerunner because it uses an ARMv4 
processor and is thus generally slower than "approved" Android devices (which 
have ARMv5 or later processors).

In any case, I'd suggest keeping the device powered up while exporting, as 
sleep mode will apparently interrupt the export process (and it will take a 
while to resume again), and I guess it's safe to assume users want the export 
to be as fast as possible; saving battery while exporting is less of an issue...

Original issue reported on code.google.com by mich...@vonglasow.com on 7 Mar 2011 at 6:09

[GoogleCodeExporter]

Hi, 
thanks for the feedback. Sorry for the delay in commenting. I submitted a patch 
to speed up GPX export (issue #97). This has not yet been included in the 
released OSMTracker. This is due to isue #98 where, we hope to overhaul the 
export functionality to make a more comprehensive, this patch has not been 
added yet

I don't know if you have the tools, or the time, to try building the latest 
code with that patch applied. If you can, I'd suggest trying that and it may 
mean that more of your tracks are fully exported before the phone goes into 
standby.

- Paul

Original comment by oshea.p...@gmail.com on 23 Apr 2011 at 4:23

[GoogleCodeExporter]

If you can't, or it doesn't help with the issue, let me know and I'll see what 
I can do.

- Paul.

Original comment by oshea.p...@gmail.com on 23 Apr 2011 at 5:26

[GoogleCodeExporter]

I have since switched to a Google Nexus S with CyanogenMod 4.0.0. The code 
speedup and faster processor help a lot, making it an issue only with really 
long tracks (several hour of logging). 

However, I still don't think it is a good idea to do that kind of bulk 
processing in an Activity (see also issue #98) - this should really go into a 
service that would get started with "startForeground()". With a foreground 
service, sleep also shouldn't be an issue (the export would get slowed down or 
interrupted, but resume when the device wakes up again).

Original comment by mich...@vonglasow.com on 23 Jan 2013 at 10:41