我的AppWidget
没有更新时间。我无法弄清楚原因。
这是我的app_widget_info.xml
文件。 updatePeriodMillis
设置为零,因为我使用AlarmManager
手动更新小部件:
<?xml version="1.0" encoding="utf-8"?>
<appwidget-provider xmlns:android="http://schemas.android.com/apk/res/android"
android:minWidth="250dp" android:minHeight="110dp" android:updatePeriodMillis="0"
android:initialLayout="@layout/app_widget"
android:widgetCategory="home_screen|keyguard"
android:initialKeyguardLayout="@layout/app_widget"
android:previewImage="@drawable/preview_image" />
以下是我AppWidgetProvider
课程的相关部分:
public class MyAppWidget extends AppWidgetProvider {
private static PendingIntent service1 = null, service2 = null, update_service = null;
public static void nullifyService( String service_name ) {
if ( service_name.equals( "service1" ) ) {
service1 = null;
} else {
service2 = null;
}
}
public static void updateMyWidget(final Context context, AppWidgetManager appWidgetManager, int appWidgetId) {
/* ... code to update my widget ... */
/* ... this code is tested and I know it works ... */
// Instruct the widget manager to update the widget
appWidgetManager.updateAppWidget(appWidgetId, views);
}
@Override
public void onUpdate(Context context, AppWidgetManager appWidgetManager, int[] appWidgetIds) {
// set alarms if necessary for the beginning and end of the next void
if ( null == update_service || ( null == service1 && null == service2 ) ) {
final AlarmManager m = (AlarmManager)context.getSystemService(Context.ALARM_SERVICE);
// set alarms for the beginning and end of the upcoming/current event window
if ( null == service1 && null == service1 ) {
final Calendar s1_c = Calendar.getInstance(), // service1 alarm time
s2_c = Calendar.getInstance(); // service2 alarm time
final Intent s1_i = new Intent(context,MyService.class).putExtra( "serviceName", "service1" ),
s2_i = new Intent(context,MyService.class).putExtra( "serviceName", "service2" );
final long s1_millis, s2_millis;
// get the current VOC info
if ( db == null ) db = new MyDataBase(context);
alarm_info = db.getCurrentAlarms();
// alarm times for service1 and service2 are UNIX timestamps
// pulled from a sqlite database (tested and working fine)
s1_c.setTime(new Date(alarm_info.getLong(4) * 1000 ));
s2_c.setTime(new Date(alarm_info.getLong(1) * 1000 ));
// if it is still before the next service1 alarm time
// set an alarm for the exact time
if ( s1_c.getTimeInMillis() > Calendar.getInstance().getTimeInMillis() ) {
s1_c.set(Calendar.MILLISECOND, 0);
s1_c.set(Calendar.SECOND, 0);
service1 = PendingIntent.getService(context, 0, s1_i, PendingIntent.FLAG_ONE_SHOT );
s1_millis = SystemClock.elapsedRealtime() + s1_c.getTime().getTime() - System.currentTimeMillis();
m.setExact(AlarmManager.ELAPSED_REALTIME, s1_millis, service1);
}
// set the alarm for the service2 alarm time
s2_c.set(Calendar.MILLISECOND, 0);
s2_c.set(Calendar.SECOND, 0);
service2 = PendingIntent.getService(context, 1, s2_i, PendingIntent.FLAG_ONE_SHOT );
s2_millis = SystemClock.elapsedRealtime() + s2_c.getTime().getTime() - System.currentTimeMillis();
m.setExact(AlarmManager.ELAPSED_REALTIME, s2_millis, service2);
}
// set the widget to update every 15 minutes regardless
if ( null == update_service ) {
final Intent up_i = new Intent(context,MyService.class).putExtra( "serviceName", "update" );
update_service = PendingIntent.getService(context, 2, up_i, PendingIntent.FLAG_CANCEL_CURRENT);
m.setRepeating(AlarmManager.ELAPSED_REALTIME, SystemClock.elapsedRealtime(), 15 * 60 * 1000, update_service);
}
}
// There may be multiple widgets active, so update all of them
for( int appWidgetId : appWidgetIds) {
updateMyWidget(context, appWidgetManager, appWidgetId);
}
}
@Override
public void onDisabled(Context context) {
// Enter relevant functionality for when the last widget is disabled
final AlarmManager m = (AlarmManager)context.getSystemService(Context.ALARM_SERVICE);
m.cancel(service1);
m.cancel(service2);
m.cancel(update_service);
}
}
以下是我Service
课程的相关部分:
public class MyService extends Service {
@Override
public int onStartCommand(Intent intent, int flags, int startId){
// update all of the widgets
ComponentName cn = new ComponentName(this, MyAppWidget.class);
AppWidgetManager m = AppWidgetManager.getInstance(this);
for ( int awid : m.getAppWidgetIds(cn) ) {
MyAppWidget.updateMyWidget(this,m,awid);
}
String service_name = intent.getStringExtra( "serviceName" );
if ( "service1" == service_name || "service2" == service_name ) {
MyAppWidget.nullifyService(service_name);
}
return START_NOT_STICKY;
}
}
update_service
工作正常,每15分钟可靠地更新小部件service1
和service2
的警报。 以下是运行adb shell dumpsys alarm
的代码段,其中显示了一个重复警报(每15分钟触发一次,或900000毫秒):
ELAPSED #0: Alarm{41a9e1b8 type 3 com.mycompany.myappwidget}
type=3 whenElapsed=231265839 when=+11m52s295ms window=-1 repeatInterval=900000 count=0
operation=PendingIntent{41dbf158: PendingIntentRecord{41cf7920 com.mycompany.myappwidget startService}}
这是另一个显示在确切时间触发的警报之一:
ELAPSED #4: Alarm{433d1560 type 3 com.mycompany.myappwidget}
type=3 whenElapsed=90066209 when=+4h34m36s121ms window=0 repeatInterval=0 count=0
operation=PendingIntent{41f0ec28: PendingIntentRecord{41f1e690 com.mycompany.myappwidget startService}}
以下是d
和c
引用已启动服务的警报的统计信息:
com.mycompany.myappwidget +1s857ms running, 0 wakeups:
+1s817ms 0 wakes 83 alarms: cmp={com.mycompany.myappwidget/com.mycompany.myappwidget.d}
+40ms 0 wakes 1 alarms: cmp={com.mycompany.myappwidget/com.mycompany.myappwidget.c}
如您所见,警报 被触发,但界面未更新。
Service
类,以避免警报相互取消suggested by this post Log
语句确认在触发每个警报时实际调用updateMyWidget()
函数。似乎调用了该函数,但并不总是更新小部件。requestCode
设置不同的唯一PendingIntent
,以便在设置新警报时,它不会无意中取消其他警报设置的PendingIntent
我这样做错了吗?平均而言,更新似乎只需要大约200毫秒,因此我应该使用PendingIntent.getBroadcast()
并调用android.appwidget.action.APPWIDGET_UPDATE
而不是创建Service
来处理更新。这让我疯了,所以任何可能指向正确方向的提示或线索都会非常感激。
@ Karakuri的回答告诉我如何区分PendingIntent
对象,以便在设置警报时不让它们互相覆盖。以下是我修复此代码的方法:
putExtra()
调用更改为setAction()
并将操作设置为预定义常量之一,例如Intent.ACTION_MAIN
,似乎在语义上类似于服务正在做什么onUpdate()
onUpdate()
android:updatePeriodMillis
中的app_widget_info.xml
更改为1800000
(30分钟)并摆脱重复的警报我会设置为setRepeating()
非常感谢!!!
答案 0 :(得分:2)
以下是我的建议,希望这里的某些内容可以解决您的问题。
请勿使用==
来比较服务中的字符串(或任何位置)。将.equals()
与命名常量一起使用。
您的PendingIntent
仅因附加内容而异。当您将Intent
提供给PendingIntent
时,它只保留其中一个Intent
。为了比较PendingIntent
s,附加内容不被视为(请参阅Intent
的文档)。我会给每个intent.getAction()
一个不同的操作,而不是使用附加内容,并在您的服务中使用SharedPreferences
。
不要依赖静态变量来保持状态。您的流程可以随时关闭,您将丢失该数据。您的AppWidget在不同的进程中运行,因此除非您有其他运行,否则Android可能会决定清除您的进程。我会使用某种持久性存储,如果只是少数几个键,可能会{{1}}。