Unexpected output of 'dumpsys SurfaceFlinger' command: no GL extensions found.

[gmck]

Android framework version

net10.0-android, net11.0-android (Preview)

Affected platform version

VS2026 Insiders and Community 18.10.2 and 12217.175 - Net10 and Net11 RC1

Description

Unexpected output of 'dumpsys SurfaceFlinger' command: no GL extensions found. This occurs for both VS’s at the end of the output for a release deploy. The deploy succeeds in both cases and the apps run normally.
About three years ago I remember getting something similar and it was suggested that it was an incorrect version of the BundleTool #8368

Output from Community

C:\Program Files\Android\openjdk\jdk-21.0.8\bin\java.exe -Xmx1G -jar "C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\36.1.69\tools\bundletool.jar" install-apks --apks obj\Release\net10.0-android36.1\android\bin\com.glmsoftware.obdnowpros.apks --adb "C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe" --device-id 49280DLAQ005DD --allow-downgrade --modules ALL
Unexpected output of 'dumpsys SurfaceFlinger' command: no GL extensions found.
The APKs have been extracted in the directory: C:\Users\gmcke\AppData\Local\Temp\12300568263795936877
Skipping target "_Upload" because all output files are up-to-date with respect to the input files.
1>Deployment was successful to Google Pixel 9.
Done building project "OBDNowPros.csproj".
Build succeeded.
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Build completed at 9:10 AM and took 11.330 seconds ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
========== Deploy completed at 9:10 AM and took 11.330 seconds ==========

Output from Insiders

C:\Program Files\Java\jdk-21.0.1\bin\java.exe -Xmx1G -jar "C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\37.0.0-rc.1.2257\tools\bundletool.jar" build-apks --connected-device --mode default --adb "C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe" --device-id 49280DLAQ005DD --bundle obj\Release\net11.0-android37.0\android\bin\com.glmsoftware.obdnowpros.aab --output obj\Release\net11.0-android37.0\android\bin\com.glmsoftware.obdnowpros.apks --aapt2 "C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\37.0.0-rc.1.2257\tools\aapt2.exe" --ks C:\glmkeystore\upload_key.keystore --ks-key-alias upload_key --key-pass file:c:\glmkeystore\KeyPassword.txt --ks-pass file:c:\glmkeystore\KeyStorePassword.txt
Unexpected output of 'dumpsys SurfaceFlinger' command: no GL extensions found.
Touching "obj\Release\net11.0-android37.0\android\bin\com.glmsoftware.obdnowpros.apks".
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s 49280DLAQ005DD uninstall -k com.glmsoftware.obdnowpros
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s 49280DLAQ005DD shell cmd package uninstall com.glmsoftware.obdnowpros
C:\Program Files\Java\jdk-21.0.1\bin\java.exe -Xmx1G -jar "C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\37.0.0-rc.1.2257\tools\bundletool.jar" install-apks --apks obj\Release\net11.0-android37.0\android\bin\com.glmsoftware.obdnowpros.apks --adb "C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe" --device-id 49280DLAQ005DD --allow-downgrade --modules ALL
Unexpected output of 'dumpsys SurfaceFlinger' command: no GL extensions found.
The APKs have been extracted in the directory: C:\Users\gmcke\AppData\Local\Temp\10647139466876826923
Using cached value from RegisterTaskObject
Found device: 49280DLAQ005DD
Creating "obj\Release\net11.0-android37.0\upload.flag" because "AlwaysCreate" was specified.
Touching "obj\Release\net11.0-android37.0\upload.flag".
Done building project "OBDNowPros.csproj".
Build succeeded.

Steps to Reproduce

N/A

Did you find any workaround?

Tried Repairing both VS's. Same result each time.

Relevant log output

[jonathanpeppers]

🤖 This message comes from Google's bundletool while it detects the connected device's capabilities, not from the app or Visual Studio. Bundletool runs adb shell dumpsys SurfaceFlinger and looks for a SurfaceFlinger global state: header, a GLES: line, and a following GL-extensions line. If it cannot find that sequence, it prints this warning and proceeds with an empty GL-extension list. Your logs show that the APK build and deployment still succeed; unlike the older failure in #8368, this is non-fatal.

Could you share the Pixel 9's Android version and the relevant lines from adb -s 49280DLAQ005DD shell dumpsys SurfaceFlinger (around SurfaceFlinger global state:, GLES:, and the following line, if present)? That will show whether the device omits that information or reports it in a format bundletool does not recognize. Bundletool parser

[dotnet-policy-service]

Hi @gmck. We have added the "need-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[jonathanpeppers]

I think the AI is on the right track, but Google does have bundletool on GitHub so you could report it there.

[gmck]

@jonathanpeppers

I’m a bit out of my depth on SurfaceFlinger, so this is a GitHub Copilot summary after looking at the raw output.
I think I misunderstood the earlier request. I had provided the bundletool / deployment log showing:
· build-apks --connected-device
· install-apks
· Unexpected output of 'dumpsys SurfaceFlinger' command: no GL extensions found.
But it now seems you may have been asking for the raw output from:
adb shell dumpsys SurfaceFlinger
I captured that from the affected Pixel 9 and reviewed it. The main thing Copilot noticed is that the dump does not appear to contain the older-style GL/EGL lines that bundletool seems to be looking for, such as:
· GL_EXTENSIONS
· EGL_EXTENSIONS
· GL_VENDOR
· GL_RENDERER
· GL_VERSION
Instead, the output looks more Vulkan-oriented. For example, it includes entries like:
· SurfaceFlinger global state:
· RE Vulkan (Graphite)
· Vulkan device initialized: 1
· Name: Mali-G715
· Supported API version: 1.4.343
· Enabled instance extensions: []
· Enabled device extensions: [ VK_* ... ]
It also contains:
· Sync configuration: [using: EGL_ANDROID_native_fence_sync EGL_KHR_wait_sync]
So Copilot’s guess is that bundletool may still be expecting GL extension output in an older format, while this device/OS is returning Vulkan-oriented renderer information instead. That seems consistent with the warning:
Unexpected output of 'dumpsys SurfaceFlinger' command: no GL extensions found.
For context, deployment still succeeds and the app runs normally. I also see the same behavior with both:
· net10.0-android36.1
· net11.0-android37.0
and in both VS Community and VS Insiders.

I've attached the full raw adb shell dumpsys SurfaceFlinger.

I've now noticed that it doesn't produce the warning every time that I build and deploy, but I can't establish a pattern for that behaviour.

SurfaceFlinger.txt

.