Custom screen switching & energy issues

[joeloc]

I want to make a very basic custom screen that serves as a replacement for a simple speedometer on a bike:

++++++++++++
+    26 km/h
+    550m      
+
+
+
+
+
+
+
++++++++++++

Since it's supposed to be always on, the main issue here is amoled energy consumption. All black with just a few white letters, no complex map updating, no track drawing, no nothing. So far so good, that should be doable with Locus style sheets.

Questions:

a) I can use the back button to return to main screen. Good. Can I somehow make my custom screen also return to main by a simple single tap just anywhere on screen?

b) I would need Locus to automatically turn the screen off if the speed is 0 km/h for a minute and turn it back on when I start moving again. That could be handled either by gps or motion sensors I guess. Any ideas on this?

c) If I do not have a map displayed on my custom screen, will Locus still do internal calculations, rotations calcs, etcpp? Or is it all intelligently suspended until the map is actually visible?

[Menion]

Hi Joe,
  to go back is usable "back" button on phone. Currently no extra functionality or scripts is allowed in these screens. About quickly switching back to custom screen, there should not be any asking. When you for the first time displayed your custom screen, then every other comeback, should show immediately without asking!

c) this is not possible in locus at all, but interesting idea.

Joe, whole system for custom screens is by my opinion something like "beta". I created this as example what can be done. It's usable but not too much powerful. Currently I have some other tasks that have priority, anyway I plan to support this feature a lot in future. So, for now, don't expect many news here anyway when you'll see that I started work on this again, please bombard me with requests