From ccb2b4439a430d4a736bcb294ba8f00be79fc66c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rulong=20Chen=EF=BC=88=E9=99=88=E6=B1=9D=E9=BE=99=EF=BC=89?=
 <26625149+0xZOne@users.noreply.github.com>
Date: Tue, 30 Jan 2024 14:59:24 +0800
Subject: [PATCH] Using `initExpensiveAndroidView` for Android Hybrid
 Composition Mode (#142399)

After https://github.com/flutter/flutter/pull/100990, we should use `initExpensiveAndroidView` for Android Hybrid Composition mode instead of `initSurfaceAndroidView`.

`initSurfaceAndroidView` attempts to use `TLHC` when possible. In cases where that is not supported, it falls back to using Hybrid Composition.

https://github.com/flutter/engine/pull/49414
---
 .../lib/android_platform_view.dart                              | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev/benchmarks/platform_views_layout_hybrid_composition/lib/android_platform_view.dart b/dev/benchmarks/platform_views_layout_hybrid_composition/lib/android_platform_view.dart
index 1153fdf8952..def05d9a399 100644
--- a/dev/benchmarks/platform_views_layout_hybrid_composition/lib/android_platform_view.dart
+++ b/dev/benchmarks/platform_views_layout_hybrid_composition/lib/android_platform_view.dart
@@ -34,7 +34,7 @@ class AndroidPlatformView extends StatelessWidget {
         );
       },
       onCreatePlatformView: (PlatformViewCreationParams params) {
-        return PlatformViewsService.initSurfaceAndroidView(
+        return PlatformViewsService.initExpensiveAndroidView(
           id: params.id,
           viewType: viewType,
           layoutDirection: TextDirection.ltr,