Android平台更快的屏幕捕获方案咨询：优先捕获主布局

Hey there! I totally get the frustration of dealing with laggy screen captures—80ms or even 50ms can feel like an eternity when you need smooth performance. Let's break down some optimized approaches to get your capture times way down, whether you're targeting just your main layout or going fullscreen.

首先，优化你现有的Canvas绘制方案 #

Your current Canvas method is already better than drawing cache, but we can squeeze more speed out of it by reusing Bitmap objects instead of creating a new one every time. Creating Bitmaps is expensive because it involves memory allocation and garbage collection overhead. Here's how to adjust your code:

// 全局复用的Bitmap对象
private Bitmap reusableCaptureBitmap;

private Bitmap captureMainLayout() {
    int layoutWidth = getWidth();
    int layoutHeight = getHeight();

    // 只有当尺寸不匹配或Bitmap为空时，才重新创建
    if (reusableCaptureBitmap == null 
        || reusableCaptureBitmap.getWidth() != layoutWidth 
        || reusableCaptureBitmap.getHeight() != layoutHeight) {
        
        // 回收旧Bitmap，避免内存泄漏
        if (reusableCaptureBitmap != null) {
            reusableCaptureBitmap.recycle();
        }
        reusableCaptureBitmap = Bitmap.createBitmap(layoutWidth, layoutHeight, Bitmap.Config.ARGB_8888);
    }

    // 直接将布局绘制到复用的Bitmap上
    Canvas canvas = new Canvas(reusableCaptureBitmap);
    draw(canvas); // 这一步比手动绘制子View快，因为它走的是View的原生绘制流程

    return reusableCaptureBitmap;
}

This tweak should cut your capture time to 20ms or less in most cases, since we eliminate the repeated memory allocation step.

全屏捕获？用MediaProjection + ImageReader（最快方案） #

If fullscreen capture is acceptable, this is the gold standard for speed—system-level capture that bypasses most app-level drawing overhead, usually clocking in at under 10ms. It leverages the device's GPU and media framework directly:

private MediaProjection mMediaProjection;
private ImageReader mImageReader;
private DisplayMetrics mDisplayMetrics;

// 初始化捕获（需要先获取MediaProjection权限，这里假设你已经处理了权限请求）
private void initFullscreenCapture() {
    mDisplayMetrics = getResources().getDisplayMetrics();
    int screenWidth = mDisplayMetrics.widthPixels;
    int screenHeight = mDisplayMetrics.heightPixels;

    // 创建ImageReader，设置缓冲区数量为2避免丢帧
    mImageReader = ImageReader.newInstance(screenWidth, screenHeight, PixelFormat.RGBA_8888, 2);

    // 创建虚拟显示器，将屏幕内容投射到ImageReader的Surface
    mMediaProjection.createVirtualDisplay(
        "FastScreenCapture",
        screenWidth, screenHeight, mDisplayMetrics.densityDpi,
        DisplayManager.VIRTUAL_DISPLAY_FLAG_AUTO_MIRROR,
        mImageReader.getSurface(),
        null, // 不需要回调的话传null
        null
    );
}

// 获取最新的捕获帧
private Bitmap getLatestFullscreenBitmap() {
    Image capturedImage = mImageReader.acquireLatestImage();
    if (capturedImage == null) return null;

    Image.Plane[] planes = capturedImage.getPlanes();
    ByteBuffer pixelBuffer = planes[0].getBuffer();
    int pixelStride = planes[0].getPixelStride();
    int rowStride = planes[0].getRowStride();
    int rowPadding = rowStride - pixelStride * capturedImage.getWidth();

    // 创建Bitmap并复制像素
    Bitmap tempBitmap = Bitmap.createBitmap(
        capturedImage.getWidth() + rowPadding / pixelStride,
        capturedImage.getHeight(),
        Bitmap.Config.ARGB_8888
    );
    tempBitmap.copyPixelsFromBuffer(pixelBuffer);

    // 裁剪掉多余的行padding，得到准确的屏幕尺寸Bitmap
    Bitmap finalBitmap = Bitmap.createBitmap(tempBitmap, 0, 0, capturedImage.getWidth(), capturedImage.getHeight());
    tempBitmap.recycle();
    capturedImage.close();

    return finalBitmap;
}

Just remember to release the MediaProjection and ImageReader when you're done to avoid resource leaks!

额外小技巧：临时调整视图的绘制层 #

If you're still seeing lag with layout capture, try temporarily disabling hardware acceleration layers for your view during capture. Some layer configurations can add overhead when capturing:

// 捕获前临时关闭硬件加速层
setLayerType(View.LAYER_TYPE_NONE, null);

// 执行你的捕获操作...

// 捕获完成后恢复原来的层设置（比如默认的硬件加速）
setLayerType(View.LAYER_TYPE_HARDWARE, null);

This is a niche fix, but it can help with certain custom views that use complex layer effects.

内容的提问来源于stack exchange，提问作者Peri Hartman