安卓定时器在手机屏幕锁定后延迟

9
我有一个服务,其中的 TimerTask 在一个方法中运行,必须每秒计数并在一定时间后执行某些操作。我的服务正常工作,当我在服务中启动该方法时,计时器开始每秒滴答一次(1000毫秒)。问题是,当设备的屏幕关闭时,我的计时器有时会停止,并且无法正确计数。我可以在日志文件中看到计时器停止了15秒,然后运行了5秒,然后再次停止...当设备连接到电脑时,计时器总是正常工作,但是当我断开设备与电脑的连接时,就会出现这个问题。
以下是我的服务代码:
public class MyService extends Service {
    private String TAG = getClass().getName();

    public void count() {

        Log.i(TAG, "Service Count Method Start");

        int counter;
        Timer mTimer = new Timer();

        mTimer.schedule(new TimerTask() {

            @Override
            public void run() {


                Log.i(TAG, "Timer count value : " + counter);

                if (!someCondition) {
                    counter++;
                    if (DefaultApplication.notOnDisplayTime >= 180) {
                        Log.d(TAG, "APPLICATION REACHED TIME LIMIT!");
                        someCondition = true;

                    } else
                                someCondition = false;
                } else {
                    counter = 0;
                }
            }
        }, 0, 1000);

    }

    @Override
    public IBinder onBind(Intent intent) {
        // TODO Auto-generated method stub
        return mBinder;
    }

    public class MyServiceBinder extends Binder {
        public MyService getService() {
            return MyService.this;
        }
    }

    private final IBinder mBinder = new MyServiceBinder();
    @Override
    public boolean onUnbind(Intent intent) {
        // TODO Auto-generated method stub
        Log.i(TAG, "MyService Unbound");
        return super.onUnbind(intent);
    }
}

以下是logcat输出:

    04-25 14:35:22.951 I/com.mypackagename.MyService( 6745): Timer count value : 73
    04-25 14:35:23.949 I/com.mypackagename.MyService( 6745): Timer count value : 74
    04-25 14:35:24.019 D/dalvikvm( 6832): GC_FOR_MALLOC freed 6656 objects / 495856 bytes in 61ms
    04-25 14:35:24.951 I/com.mypackagename.MyService( 6745): Timer count value : 75
    04-25 14:35:25.951 I/com.mypackagename.MyService( 6745): Timer count value : 76

#### 在这里屏幕正在被锁定 ####

    04-25 14:35:26.929 I/power ( 96): *** set_screen_state 0]
    04-25 14:35:26.959 V/KeyguardViewMediator( 96): password timeout now
    04-25 14:35:26.959 D/KeyguardViewManager( 96): show()
    04-25 14:35:26.999 D/Sensors ( 96): close_akm, fd=138
    04-25 14:35:26.999 I/com.mypackagename.MyService( 6745): Timer count value : 77
    04-25 14:35:27.039 D/HtcLockScreen( 96): onScreenRestart
    04-25 14:35:27.039 I/HtcLockScreen( 96): updateStatusViewByPriority, mIsSimCheckView = false, mIsBatteryInfo = false, mIsMusicPlaying = false, mIsAirPlaneMode = false
    04-25 14:35:27.049 I/HtcLockScreen( 96): HtcLockScreen:onResume 
    04-25 14:35:27.069 D/SurfaceFlinger( 96): Layer::setBuffers(this=0x785580), pid=96, w=480, h=762
    04-25 14:35:27.079 D/SurfaceFlinger( 96): Layer::setBuffers(this=0x785580), pid=96, w=480, h=762
    04-25 14:35:27.109 D/SurfaceFlinger( 96): Layer::requestBuffer(this=0x785580), index=0, pid=96, w=480, h=762 success
    04-25 14:35:27.339 D/alogcat ( 6832): stopping ...
    04-25 14:35:27.339 D/alogcat ( 6832): paused
    04-25 14:35:27.609 D/SurfaceFlinger( 96): About to give-up screen, flinger = 0xb4e28
    04-25 14:35:27.669 D/AK8973 ( 72): Compass CLOSE

#### Screen Locked ####

    04-25 14:35:27.949 I/com.mypackagename.MyService( 6745): Timer count value : 78
    04-25 14:35:28.949 I/com.mypackagename.MyService( 6745): Timer count value : 79
    04-25 14:35:44.602 I/com.mypackagename.MyService( 6745): Timer count value : 80
    04-25 14:35:45.603 I/com.mypackagename.MyService( 6745): Timer count value : 81
    04-25 14:35:45.784 I/wpa_supplicant( 256): CTRL-EVENT-SCAN-RESULTS Ready
    04-25 14:35:45.799 D/LocationMasfClient( 96): getNetworkLocation(): Returning cache location with accuracy 75.0
    04-25 14:35:46.603 I/com.mypackagename.MyService( 6745): Timer count value : 82
    04-25 14:35:47.603 I/com.mypackagename.MyService( 6745): Timer count value : 83
    04-25 14:35:48.604 I/com.mypackagename.MyService( 6745): Timer count value : 84
    04-25 14:35:49.604 I/com.mypackagename.MyService( 6745): Timer count value : 85
    04-25 14:36:10.558 D/SurfaceFlinger( 96): Layer::requestBuffer(this=0x785580), index=1, pid=96, w=480, h=762 success
    04-25 14:36:11.033 I/com.mypackagename.MyService( 6745): Timer count value : 86
    04-25 14:36:13.269 I/com.mypackagename.MyService( 6745): Timer count value : 87
    04-25 14:36:13.289 D/com.mypackagename.utils.XUtil( 6745): return 0 char $
    04-25 14:36:14.039 D/com.mypackagename.utils.XUtil( 6745): return 0 char $
    04-25 14:36:14.269 I/com.mypackagename.MyService( 6745): Timer count value : 88
    04-25 14:36:17.009 I/com.mypackagename.MyService( 6745): Timer count value : 89
    04-25 14:36:29.512 I/com.mypackagename.MyService( 6745): Timer count value : 90

您可以看到,当屏幕被锁定后,计时器似乎不会每秒滴答作响。它会停止15-20秒,然后正常工作5秒...

对于如何防止设备锁定屏幕时计时器停止,您有什么意见吗?

1个回答

5
听起来你需要一个部分唤醒锁定。这将防止CPU在屏幕关闭时进入睡眠状态。但请注意,滥用可能会导致电池问题,并且您需要获得使用唤醒锁的权限。

我遇到了完全相同的问题,我已经按照您建议的使用了Partial Wake Lock,但问题仍然存在。我正在使用以下代码进行Partial Wake Lock:PowerManager pm = (PowerManager) context.getSystemService(Context.POWER_SERVICE); PowerManager.WakeLock mWakeLock = pm.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK, "Timer::lock"); mWakeLock.acquire(5000); - Rahul Patidar
过去十年中发生了许多与电源管理相关的变化。多亏了Doze,唤醒锁常常被忽略。 - Mike dg

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接