Skip to content

android: [render-validation] support multiple backends#9820

Open
poweifeng wants to merge 1 commit intomainfrom
pf/android-render-val-backends
Open

android: [render-validation] support multiple backends#9820
poweifeng wants to merge 1 commit intomainfrom
pf/android-render-val-backends

Conversation

@poweifeng
Copy link
Contributor

This commit introduces several features:

  • Backend Testing: Support testing across both OpenGL and Vulkan. Test configurations expand per backend, and the Filament Engine alongside ModelViewer is recreated dynamically when the backend switches to isolate resources.
  • UI Controls: Added a backend filter toggle and a test progress bar to the main activity, themed appropriately using Material design.
  • Memory Optimizations: Drastically reduced memory usage by displaying scaled-down thumbnails (128x128) in the main list. Full-resolution images are lazy-loaded from disk on demand when clicking a thumbnail to view, and large bitmaps are aggressively recycled.
  • Device Info Collection: ValidationResultManager now collects and reports detailed GPU driver info for each instantiated backend in the output results.json.
  • Engine Teardown: Introduced an explicit destroy() method in ModelViewer to ensure full resource cleanup during engine recreation.

This commit introduces several features:

- Backend Testing: Support testing across both OpenGL and Vulkan. Test
  configurations expand per backend, and the Filament Engine alongside
  ModelViewer is recreated dynamically when the backend switches to isolate
  resources.
- UI Controls: Added a backend filter toggle and a test progress bar to the
  main activity, themed appropriately using Material design.
- Memory Optimizations: Drastically reduced memory usage by displaying
  scaled-down thumbnails (128x128) in the main list. Full-resolution images
  are lazy-loaded from disk on demand when clicking a thumbnail to view, and
  large bitmaps are aggressively recycled.
- Device Info Collection: ValidationResultManager now collects and reports
  detailed GPU driver info for each instantiated backend in the output
  results.json.
- Engine Teardown: Introduced an explicit destroy() method in ModelViewer to
  ensure full resource cleanup during engine recreation.
@poweifeng poweifeng added the internal Issue/PR does not affect clients label Mar 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Issue/PR does not affect clients

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant