> That actually shouldn't be all that bad -- just disable the updates in > ACTION_SCREEN_OFF (and onStop()) and re-enable them in ACTION_SCREEN_ON > (and onStart()).
Yup - this is the idea - my "appwidgets" does not need updates when the device is locked or something - no need for wakeup. Like the analog clock - that one doesn't wakeup the phone every second as far as I know. I'm working on gauges which are using real data taken from sensors or other sources - update is needed only when the screen is on. Something like the analog clock but having a voltmeter for example. I know this is not for phones but our aproach is also pretty different - we are working on a platform too which ain't be a phone and it will always have power source - in that case battery is not an issue. And I know that this aproach might be a new one for Android since as far as I've seen most of the developers writing here are developing for phones - which is kinda bad for us since Andoid is pushed more and more in very specific directions but I guess that's it - we have to deal with what we have :) I will digg into homescreens and I might try the service with intent from JP's solution too - in some cases 1 second update like the clock is might be good enough - TY for the tips ... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
