Performance plummets after screen is dimmed, then awoken

Solar2D Android
#1

This happens when screen is dimmed, then touched to keep the phone from hibernating the app. All the stuff goes to 3fps, including overlays and pickerViews. I can’t fault my app. Using Storyboard, graphics v2, 30 fps on 2014.2511.

What I have on screen is a few images, rects, and newTexts on a scrollview, nothing moving around. The only background code running is a locationHandler. But when this happens, even transition.to on one image’s alpha goes choppy.

I could shut down the app if I could detect the screen dim, which is not the best option, but might prevent some bad ratings at least. What scene events are called on screen dim and restore?

Is this a known problem? Couldn’t find it via search.

Edit: I also have an AdMob banner ad. 

#2

You can try adding the following line, near the top of your main.lua.

system.setIdleTimer( false )

This should prevent the screen from dimming, but you might just be masking over some other problem. I’ve never seen the problem you’re describing and I don’t usually add this line to my apps.

#3

The problem was the changed(?) behavior of the locationHandler. It or the phone created a barrage of rapid fire events at roughly 10 second intervals that were not filtered. Since the position update called a screen update function using transitions, this created several transitions on the same object, which created an imbalance in the correct onComplete handling and in general a rift in The Force. I have felt it.

#4

You can try adding the following line, near the top of your main.lua.

system.setIdleTimer( false )

This should prevent the screen from dimming, but you might just be masking over some other problem. I’ve never seen the problem you’re describing and I don’t usually add this line to my apps.

#5

The problem was the changed(?) behavior of the locationHandler. It or the phone created a barrage of rapid fire events at roughly 10 second intervals that were not filtered. Since the position update called a screen update function using transitions, this created several transitions on the same object, which created an imbalance in the correct onComplete handling and in general a rift in The Force. I have felt it.