Nexus7(2013) flo framerate maxes out at 30fps
Bug #1274189 reported by
Kevin DuBois
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Kevin DuBois | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
two ways to see this one:
run unity8 on flo, and you'll see the frame times are ~33ms.
alternatively, you could run
mir_demo_
Related branches
lp://qastaging/~kdub/mir/fix-1274189
- Ricardo Salveti (community): Approve
- Gerry Boland (community): Approve (functional)
- Daniel van Vugt: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 261 lines (+46/-20)6 files modifiedinclude/test/mir_test_doubles/mock_hwc_composer_device_1.h (+9/-1)
src/platform/graphics/android/hwc_device.cpp (+4/-7)
src/platform/graphics/android/hwc_device.h (+2/-3)
src/platform/graphics/android/resource_factory.cpp (+3/-1)
tests/unit-tests/graphics/android/test_hwc_common_device.cpp (+3/-1)
tests/unit-tests/graphics/android/test_hwc_device.cpp (+25/-7)
Changed in mir: | |
status: | Confirmed → In Progress |
tags: | added: performance |
Changed in mir: | |
milestone: | none → 0.1.5 |
summary: |
- flo framerate maxes out at 30fps + Nexus7(2013) flo framerate maxes out at 30fps |
Changed in mir (Ubuntu): | |
status: | New → Triaged |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The problem was that we were waiting on a fence in the 4.4 images that was not set in the 4.2 images. The 'related branch' does not wait and fixes this problem.