Android“错过”了使用 ScheduledExecutorService 定期执行线程

发布于 2024-09-16 13:14:10 字数 1014 浏览 4 评论 0原文

我有一个Android应用程序，它反复从周围的wifi网络收集指纹（出于科学原因，不侵犯任何人的隐私）。

不管怎样，假设我有一个函数可以完成这项工作，它的名字是 scanWifi()。我最初想这样开始它：

ExecutorService mExecutor = Executors.newSingleThreadScheduledExecutor();

mExecutor.scheduleAtFixedRate(new Runnable() {
    @Override
    public void run() {
        scanWifi();
    }
}, 0, interval, TimeUnit.MILLISECONDS);

遗憾的是，这只有在手机插入时才能可靠地工作。如果它拔出并放置一段时间，它不会每分钟运行我的 scanWifi() 函数。有时，对 scanWifi() 的单次调用之间会有几分钟的间隔。

我还尝试使用 Timer/TimerTask 做同样的事情，但结果也很差。

到目前为止，唯一看起来或多或少可靠的方法是将其发布到处理程序并重复调用它，如下所示：

Handler h = new Handler();
Runnable r = new Runnable() {
    @Override
    public void run() {
        if (!mIsStopped) {
            scanWifi();
            h.postDelayed(this, mInterval);
        }
    }
};
h.post(r);

为什么会这样？ CPU 是否处于睡眠状态，从而错过了预定的执行？我在我的应用程序中持有部分唤醒锁。

原文

I have an android app that repeatedly collects fingerprints from the wifi-networks that are around (for scientific reasons, not to invade anybodies privacy).

Anyways, imagine I have a function that does this work and it's called scanWifi(). I initally wanted to start it like this:

ExecutorService mExecutor = Executors.newSingleThreadScheduledExecutor();

mExecutor.scheduleAtFixedRate(new Runnable() {
    @Override
    public void run() {
        scanWifi();
    }
}, 0, interval, TimeUnit.MILLISECONDS);

Sadly, this only works reliably when the phone is plugged in. If it's plugged out and lays there for a while, it doesn't run my scanWifi() function every minute. Sometimes there are gaps of several minutes between single calls to scanWifi().

I also tried doing the same thing using a Timer/TimerTask with similarly poor results.

The only thing that seems to work more or less reliable until now is to post it to a handler and call it repeatedly, like this:

Handler h = new Handler();
Runnable r = new Runnable() {
    @Override
    public void run() {
        if (!mIsStopped) {
            scanWifi();
            h.postDelayed(this, mInterval);
        }
    }
};
h.post(r);

Why is that the case? Is the CPU sleeping and thus misses the scheduled execution? I hold a partial wakelock in my app.

分享到QQ

分享到微博