它不是在单独模式下,U不能使用它 [英] It is not under singleton mode, U can't use it

查看:1958
本文介绍了它不是在单独模式下,U不能使用它的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的提醒应用中,如果我选择刚刚过去的时间,然后应用无法使用,则会出现以下错误:

In my Reminder app, If I select time which just passed away, then app not working, getting following error:

日志

Log

D/ANRAppManager: !!! It is not under singleton mode, U can't use it. !!!
05-13 10:55:19.934 22594-22600/com.mri I/dalvikvm: threadid=3: reacting to signal 3
05-13 10:55:20.190 22594-22600/com.mri D/dalvikvm: JIT unchain all for threadid=1
05-13 10:55:20.940 22594-22600/com.mri W/dalvikvm: threadid=3: spin on suspend #1 threadid=1 (pcf=0)
05-13 10:55:20.940 22594-22600/com.mri E/dalvikvm: Fatal spin-on-suspend, dumping threads
05-13 10:55:20.940 22594-22600/com.mri I/dalvikvm: DALVIK THREADS:
05-13 10:55:20.940 22594-22600/com.mri I/dalvikvm: (mutexes: tll=1 tsl=1 tscl=0 ghl=0)
05-13 10:55:20.940 22594-22600/com.mri I/dalvikvm: "main" prio=5 tid=1 RUNNABLE JIT
05-13 10:55:20.940 22594-22600/com.mri I/dalvikvm:   | group="main" sCount=1 dsCount=0 obj=0x4191cde0 self=0x418328b8
05-13 10:55:20.940 22594-22600/com.mri I/dalvikvm:   | sysTid=22594 nice=0 sched=0/0 cgrp=apps handle=1074880900
05-13 10:55:20.941 22594-22600/com.mri I/dalvikvm:   | state=R schedstat=( 133450832707 8412096123 56516 ) utm=13019 stm=326 core=0
05-13 10:55:20.941 22594-22600/com.mri I/dalvikvm:     at com.mri.reminders.AlarmReceiver.setRepeatAlarm(AlarmReceiver.java:~115)
05-13 10:55:20.941 22594-22600/com.mri I/dalvikvm:     at com.mri.reminders.ReminderAddActivity.saveReminder(ReminderAddActivity.java:963)
05-13 10:55:20.941 22594-22600/com.mri I/dalvikvm:     at com.mri.reminders.ReminderAddActivity.onOptionsItemSelected(ReminderAddActivity.java:1172)
05-13 10:55:20.942 22594-22600/com.mri I/dalvikvm:     at android.app.Activity.onMenuItemSelected(Activity.java:2633)
05-13 10:55:20.945 22594-22600/com.mri I/dalvikvm:     at android.support.v4.app.FragmentActivity.onMenuItemSelected(FragmentActivity.java:361)
05-13 10:55:20.945 22594-22600/com.mri I/dalvikvm:     at android.support.v7.app.AppCompatActivity.onMenuItemSelected(AppCompatActivity.java:147)
05-13 10:55:20.945 22594-22600/com.mri I/dalvikvm:     at android.support.v7.view.WindowCallbackWrapper.onMenuItemSelected(WindowCallbackWrapper.java:100)



这里是我在 AlarmReceiver.java

Here is the code which I am using in AlarmReceiver.java

public void setRepeatAlarm(Context context, Calendar calendar, int ID, long RepeatTime) {
        mAlarmManager = (AlarmManager) context.getSystemService(Context.ALARM_SERVICE);

        // Put Reminder ID in Intent Extra
        Intent intent = new Intent(context, AlarmReceiver.class);
        intent.putExtra(ReminderEditActivity.EXTRA_REMINDER_ID, Integer.toString(ID));
        mPendingIntent = PendingIntent.getBroadcast(context, ID, intent, PendingIntent.FLAG_CANCEL_CURRENT);

        // Calculate notification timein
        Calendar c = Calendar.getInstance();
        long currentTime = c.getTimeInMillis();
        long diffTime = calendar.getTimeInMillis() - currentTime;

        while(diffTime < 0) {
             diffTime += RepeatTime; // at this line getting error
        }

        // Start alarm using initial notification time and repeat interval time
        mAlarmManager.setRepeating(AlarmManager.ELAPSED_REALTIME,
                SystemClock.elapsedRealtime() + diffTime,
                RepeatTime , mPendingIntent);

        // Restart alarm if device is rebooted
        ComponentName receiver = new ComponentName(context, BootReceiver.class);
        PackageManager pm = context.getPackageManager();
        pm.setComponentEnabledSetting(receiver,
                PackageManager.COMPONENT_ENABLED_STATE_ENABLED,
                PackageManager.DONT_KILL_APP);
    }

如何解决此问题?

推荐答案

我认为对信号3作出反应是ANR的症状。应用程序在崩溃之前是否挂起?

I think that reacting to signal 3 is a symptom of an ANR. Does the application hang before crashing ? If so, it may be because the loops never ends.

您确定 RepeatTime 始终大于0特别不= 0)?

Are you sure that RepeatTime is always > 0 (and specially not = 0) ?

如下:

   while(diffTime < 0) {
         Log.d("SOME_TAG", "set diffTime to " + diffTime);
         diffTime += RepeatTime; // at this line getting error
    }

不应该显示多行。

更新:

您应确保警报在未来重复时间大于0

You should ensure that either the alarm is in the future or the repeat time is greater than 0.

    if (diffTime > 0 || RepeatTime > 0) {

        // set the alarm only if the parameters are consistents

        while(diffTime < 0) {
             diffTime += RepeatTime; // at this line getting error
        }

        // Start alarm using initial notification time and repeat interval time
        mAlarmManager.setRepeating(AlarmManager.ELAPSED_REALTIME,
                SystemClock.elapsedRealtime() + diffTime,
                RepeatTime , mPendingIntent);

        // Restart alarm if device is rebooted
        ComponentName receiver = new ComponentName(context, BootReceiver.class);
        PackageManager pm = context.getPackageManager();
        pm.setComponentEnabledSetting(receiver,
                PackageManager.COMPONENT_ENABLED_STATE_ENABLED,
                PackageManager.DONT_KILL_APP);

    }

这篇关于它不是在单独模式下,U不能使用它的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆