我也有同样的问题。Android模拟器在Android < 6.0上运行良好。当我使用模拟器Nexus 5 (Android 6.0)时，应用程序在I/Choreographer:在日志中跳过帧时运行非常慢。

所以，我解决了这个问题，在Manifest文件hardwareAccelerated选项更改为true，像这样:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.myapplication">

    <application android:hardwareAccelerated="true">
        ...
    </application>
</manifest>

2022年1月更新。根据@M的评论。Ed:如果您的目标api为>= 14，则默认启用硬件加速。

Android UI:修复跳过的帧

任何开始开发android应用程序的人都会看到这条消息 “编舞(abc):跳过xx帧!申请可以是 在主线上做了太多工作。”那么它实际上是什么 意思是，你为什么要担心以及如何解决它。

这意味着您的代码需要很长时间来处理和帧 都因为它而被跳过，这可能是因为一些沉重的 您在应用程序或数据库的核心所做的处理 访问或任何其他事情，导致线程停止一段时间。

Here is a more detailed explanation: Choreographer lets apps to connect themselves to the vsync, and properly time things to improve performance. Android view animations internally uses Choreographer for the same purpose: to properly time the animations and possibly improve performance. Since Choreographer is told about every vsync events, I can tell if one of the Runnables passed along by the Choreographer.post* apis doesnt finish in one frame’s time, causing frames to be skipped. In my understanding Choreographer can only detect the frame skipping. It has no way of telling why this happens. The message “The application may be doing too much work on its main thread.” could be misleading. source : Meaning of Choreographer messages in Logcat Why you should be concerned When this message pops up on android emulator and the number of frames skipped are fairly small (<100) then you can take a safe bet of the emulator being slow – which happens almost all the times. But if the number of frames skipped and large and in the order of 300+ then there can be some serious trouble with your code. Android devices come in a vast array of hardware unlike ios and windows devices. The RAM and CPU varies and if you want a reasonable performance and user experience on all the devices then you need to fix this thing. When frames are skipped the UI is slow and laggy, which is not a desirable user experience. How to fix it Fixing this requires identifying nodes where there is or possibly can happen long duration of processing. The best way is to do all the processing no matter how small or big in a thread separate from main UI thread. So be it accessing data form SQLite Database or doing some hardcore maths or simply sorting an array – Do it in a different thread Now there is a catch here, You will create a new Thread for doing these operations and when you run your application, it will crash saying “Only the original thread that created a view hierarchy can touch its views“. You need to know this fact that UI in android can be changed by the main thread or the UI thread only. Any other thread which attempts to do so, fails and crashes with this error. What you need to do is create a new Runnable inside runOnUiThread and inside this runnable you should do all the operations involving the UI. Find an example here. So we have Thread and Runnable for processing data out of main Thread, what else? There is AsyncTask in android which enables doing long time processes on the UI thread. This is the most useful when you applications are data driven or web api driven or use complex UI’s like those build using Canvas. The power of AsyncTask is that is allows doing things in background and once you are done doing the processing, you can simply do the required actions on UI without causing any lagging effect. This is possible because the AsyncTask derives itself from Activity’s UI thread – all the operations you do on UI via AsyncTask are done is a different thread from the main UI thread, No hindrance to user interaction. So this is what you need to know for making smooth android applications and as far I know every beginner gets this message on his console.

我也有同样的问题。当我在另一台计算机上运行这段代码时，它工作得很好。然而，在我的系统上，它显示“应用程序可能在主线程上做了太多的工作”。

我通过重新启动Android工作室解决了我的问题[文件->无效缓存/重新启动->单击“无效并重新启动”]。

我也有同样的问题。Android模拟器在Android < 6.0上运行良好。当我使用模拟器Nexus 5 (Android 6.0)时，应用程序在I/Choreographer:在日志中跳过帧时运行非常慢。

所以，我解决了这个问题，在Manifest文件hardwareAccelerated选项更改为true，像这样:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.myapplication">

    <application android:hardwareAccelerated="true">
        ...
    </application>
</manifest>

2022年1月更新。根据@M的评论。Ed:如果您的目标api为>= 14，则默认启用硬件加速。

我也有同样的问题。 我的是一个案例，我使用的背景图像是在绘图。这个特殊的图像大约有130kB，在我的android应用程序的启动画面和主页上使用。

解决方案-我只是把特定的图像从drawables转移到drawables-xxx文件夹，并且能够释放大量的内存占用在背景和跳绳帧不再跳绳。

更新使用“nodp”可绘制资源文件夹来存储背景可绘制图 文件。 密度限定的可绘制文件夹还是drawable-nodpi优先?

如果在应用程序中使用async/await功能，这是正常的。