Hi,

I used SD over the weekend quite extensively and encountered, that it activated my iPad's screensaver/lock after a while of inactivity.
This never happened before the iOS update. I cannot exactly say how long it took to darken my screen - but it definitely is problem, as I need to swipe to unlock, enter my PIN, ... just to have a look at the map again.

If there is a setting I screwed up or I just need to change, let me know - but I fear, it is another iOS 8(.0.2)-induced problem. 

Cheers,
Markus

I tested again on the ground (not flying) with simulation mode/and "go flying" with GPS position data and did not encounter the screen lock again... strange. Anybody else had that happening?! Any other reason that could cause the screen to blacken?

It could be the magnetic sensor picking up a 'cover closure' on a smart cover.

Now that's interesting. I had a similar issue flying to Cromer on Sunday. On the way out, the iPad kept going to sleep, even though SkyDemon was running in flying mode (obviously). On the return flight, no such problems. I don't have a Smart Cover, so what could make the iPad think that there was one & that it was being closed? There are ferrite chokes on all my accessory power & signal leads (required to elimate interference), so could one of those, if badly placed, have caused the issue?

If you don't have a smart cover, go into the iOS settings menu and disable it. 

If you've never had a smart cover, the option won't even be there. So if the option is there, it does mean it has been triggered at some point.

In my case, there was no smart Cover involved. Since I never had one, the setting to disable it doesn't appear either.
But there is a setting controlling the screen lock after inactivity, it was set to two minutes in my device. I can switch it off entirely. But I thought SD would do so during flight mode... In general I'd like to leave the automatical screen lock turned on and have only special apps keep everything up.

I have never had my device sleep in flight - SD definitely keeps it awake regardless of the timeout settings.

All I can think is that either...

1) SD crashed - was it still running when you went back to it?
2) Someone accidentally bumped the home or power button