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
I've implemented a dynamic app widget that receives updates every
second (at times). Looks like the app widget framework itself is not
sophisticated enough to get to the speed you want, so you might be
able to get there based on the approach I took. Which is to run a
separate service that sends
JP wrote:
Yeah, it would be desirable to also get a more sophisticated view
model. Ideally one that allows the reuse of whatever dynamic was
developed for the main app, in the spirit of polymorphism. But here we
are, and the current model won't change, I take that for certain.
If you want
I was puzzling over this one, but I agree that a new home screen is a
good idea. It will give you the flexibility you need to display custom
views, at a suitable refresh rate.
You will, however, have to deal with all the resource consumption
issues that go with it. A 5fps update on the home
Sean Hodges wrote:
You will, however, have to deal with all the resource consumption
issues that go with it. A 5fps update on the home screen is likely to
drain the battery pretty badly when the phone is idle.
That actually shouldn't be all that bad -- just disable the updates in
On Mon, Feb 15, 2010 at 7:34 PM, Mark Murphy mmur...@commonsware.com wrote:
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()).
Good point Mark. It would take a little forward thinking,
6 matches
Mail list logo
