使用getApplicationState().isInForeground()怎么样?

现在回答可能已经太迟了，但如果有人来访，我建议有一个解决方案， 一个应用程序想要知道它的状态是在后台还是在前台的原因可以有很多，有几个是， 1. 当用户在BG时显示祝酒和通知。 2.第一次从BG来的用户执行一些任务，如投票，重画等。

Idolon和其他人的解决方案解决了第一部分，但没有解决第二部分。如果你的应用程序中有多个活动，并且用户在它们之间切换，那么当你处于第二个活动时，可见标志将为假。所以它不能被确定地使用。

我做了一些CommonsWare建议的事情，“如果服务确定没有可见的活动，并且在一段时间内保持这种状态，那么在下一个逻辑停止点停止数据传输。”

粗体部分很重要，可以用来完成第二项。所以我所做的是一旦我得到onActivityPaused()，不改变可见直接为假，而是有一个3秒的定时器(这是下一个活动应该启动的最大值)，如果没有onactivityresume()调用在接下来的3秒，改变可见为假。 类似地，在onactivityresume()如果有一个定时器，然后我取消它。 总之，可见变成了isAppInBackground。

对不起，不能复制粘贴代码…

检测应用程序是否在后台运行的方法很少，但只有一种是完全可靠的:

The right solution (credits go to Dan, CommonsWare and NeTeInStEiN) Track visibility of your application by yourself using Activity.onPause, Activity.onResume methods. Store "visibility" status in some other class. Good choices are your own implementation of the Application or a Service (there are also a few variations of this solution if you'd like to check activity visibility from the service).   Example Implement custom Application class (note the isActivityVisible() static method): public class MyApplication extends Application { public static boolean isActivityVisible() { return activityVisible; } public static void activityResumed() { activityVisible = true; } public static void activityPaused() { activityVisible = false; } private static boolean activityVisible; } Register your application class in AndroidManifest.xml: <application android:name="your.app.package.MyApplication" android:icon="@drawable/icon" android:label="@string/app_name" > Add onPause and onResume to every Activity in the project (you may create a common ancestor for your Activities if you'd like to, but if your activity is already extended from MapActivity/ListActivity etc. you still need to write the following by hand): @Override protected void onResume() { super.onResume(); MyApplication.activityResumed(); } @Override protected void onPause() { super.onPause(); MyApplication.activityPaused(); }   Update ActivityLifecycleCallbacks were added in API level 14 (Android 4.0). You can use them to track whether an activity of your application is currently visible to the user. Check Cornstalks' answer below for the details. The wrong one I used to suggest the following solution: You can detect currently foreground/background application with ActivityManager.getRunningAppProcesses() which returns a list of RunningAppProcessInfo records. To determine if your application is on the foreground check RunningAppProcessInfo.importance field for equality to RunningAppProcessInfo.IMPORTANCE_FOREGROUND while RunningAppProcessInfo.processName is equal to your application package name. Also if you call ActivityManager.getRunningAppProcesses() from your application UI thread it will return importance IMPORTANCE_FOREGROUND for your task no matter whether it is actually in the foreground or not. Call it in the background thread (for example via AsyncTask) and it will return correct results. While this solution may work (and it indeed works most of the time) I strongly recommend to refrain from using it. And here's why. As Dianne Hackborn wrote: These APIs are not there for applications to base their UI flow on, but to do things like show the user the running apps, or a task manager, or such. Yes there is a list kept in memory for these things. However, it is off in another process, managed by threads running separately from yours, and not something you can count on (a) seeing in time to make the correct decision or (b) have a consistent picture by the time you return. Plus the decision about what the "next" activity to go to is always done at the point where the switch is to happen, and it is not until that exact point (where the activity state is briefly locked down to do the switch) that we actually know for sure what the next thing will be. And the implementation and global behavior here is not guaranteed to remain the same in the future. I wish I had read this before I posted an answer on the SO, but hopefully it's not too late to admit my error. Another wrong solution Droid-Fu library mentioned in one of the answers uses ActivityManager.getRunningTasks for its isApplicationBroughtToBackground method. See Dianne's comment above and don't use that method either.

我想出的最好的解决办法是使用计时器。

你已经在onPause()中启动了一个定时器，并在onResume()中取消了相同的定时器，有一个定时器的实例(通常在应用程序类中定义)。计时器本身被设置为在2秒后(或您认为合适的任何时间间隔)运行Runnable，当计时器触发时，您设置一个标志，将应用程序标记为在后台。

在取消定时器之前的onResume()方法中，您可以查询后台标志来执行任何启动操作(例如开始下载或启用位置服务)。

这个解决方案允许您在back堆栈上有几个活动，并且不需要任何权限来实现。

如果你也使用事件总线，这个解决方案也很有效，因为你的计时器可以简单地触发一个事件，应用程序的各个部分可以相应地做出响应。

如果你想知道一个特定的活动是否在前台，如果你是一个没有直接访问应用程序的SDK，那么没有一个答案非常适合特定的情况。对我来说，我在后台线程刚刚收到一个新的聊天消息的推送通知，只想在聊天屏幕不在前台时显示系统通知。

使用ActivityLifecycleCallbacks，正如在其他答案中推荐的那样，我已经创建了一个小的util类，它包含MyActivity是否在前台的逻辑。

class MyActivityMonitor(context: Context) : Application.ActivityLifecycleCallbacks {

private var isMyActivityInForeground = false

init {
    (context.applicationContext as Application).registerActivityLifecycleCallbacks(this)
}

fun isMyActivityForeground() = isMyActivityInForeground

override fun onActivityPaused(activity: Activity?) {
    if (activity is MyActivity) {
        isMyActivityInForeground = false
    }
}

override fun onActivityResumed(activity: Activity?) {
    if (activity is MyActivity) {
        isMyActivityInForeground = true
    }
}

}

当一个对话框出现在活动上方时，活动将被暂停，因此所有推荐的解决方案都是半解决方案。您还需要为对话框创建钩子。