2Mark:
Ummm..... AppWidgetProvider is a subclass of BroadcastReceiver, not
Service. As such, it has no onStartCommand or onStart.
You're probably thinking of onReceive - ditto for that.
2Arnouf:
Another reason might be that something else is keeping the device awake.
Might be worthwhile to dump wakelocks in adb. Or else it might be the
setting to "keep screen on while plugged in", which is often enabled for
debugging.
-- Kostya
09.10.2010 19:00, Mark Murphy пишет:
Override onStartCommand() or onStart() in your AppWidgetProvider and
figure out what Intent is being used to update the AppWidgetProvider.
That should help you narrow down the source (your alarm or the
built-in updatePeriodMillis alarm).
On Sat, Oct 9, 2010 at 10:45 AM, arnouf<[email protected]> wrote:
Hi,
I use an AlarmManager to refresh my widget view (the view not the data
displayed which are managed by the standard updatePeriodMillis).
The AlarmManager is configured to work with RTC. The documentation
indicates :
"Set the alarm type to either ELAPSED_REALTIME or RTC, which will only
deliver the alarm when the device is awake. Then set
updatePeriodMillis to zero ("0")."
I check that but my method continue to be called even if my screen is
OFF (device awake).
What's the issue ?
--
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
--
Kostya Vasilyev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
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
