Mir

visual glitches and flashing on Nexus 4

Bug #1215979 reported by Jamie Strandboge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CyanogenMod
Fix Released
Undecided
auto-rsalveti
Mir
Fix Released
Critical
Kevin DuBois
mir (Ubuntu)
Fix Released
Critical
Kevin DuBois

Bug Description

I used phablet-flash cdimage-touch --pending -d mako on my nexus 4, then followed https://wiki.ubuntu.com/Touch/Testing/Mir#Easy_way to install Mir yesterday. After rebooting I sometimes see visual gliches: flashing, portions of previously displayed apps, etc.

Related branches

lp:~kdub/mir/fix-1215979
Alan Griffiths: Approve
PS Jenkins bot (community): Approve (continuous-integration)
Alexandros Frantzis (community): Needs Fixing
Ricardo Salveti (community): Approve (testing with the android changes)
Diff: 1279 lines (+224/-393)
21 files modified
include/shared/mir/graphics/android/syncfence.h (+2/-19)
include/test/mir_test_doubles/mock_hwc_layerlist.h (+6/-6)
src/server/graphics/android/android_hwc_factory.cpp (+1/-1)
src/server/graphics/android/hwc10_device.h (+0/-1)
src/server/graphics/android/hwc11_device.cpp (+22/-38)
src/server/graphics/android/hwc11_device.h (+3/-4)
src/server/graphics/android/hwc_layerlist.cpp (+46/-23)
src/server/graphics/android/hwc_layerlist.h (+18/-14)
src/server/graphics/android/internal_client_window.cpp (+2/-1)
src/server/graphics/android/server_render_window.cpp (+2/-1)
src/shared/graphics/android/mir_native_window.cpp (+3/-19)
src/shared/graphics/android/syncfence.cpp (+16/-6)
tests/integration-tests/graphics/android/test_display_integration.cpp (+2/-2)
tests/unit-tests/client/android/CMakeLists.txt (+0/-1)
tests/unit-tests/client/android/test_android_syncfence.cpp (+0/-91)
tests/unit-tests/graphics/android/test_hwc10_device.cpp (+0/-1)
tests/unit-tests/graphics/android/test_hwc11_device.cpp (+45/-120)
tests/unit-tests/graphics/android/test_hwc_device.cpp (+17/-17)
tests/unit-tests/graphics/android/test_hwc_layerlist.cpp (+26/-24)
tests/unit-tests/graphics/android/test_internal_client_interpreter.cpp (+12/-3)
tests/unit-tests/graphics/android/test_server_interpreter.cpp (+1/-1)
Mir development team: Pending requested
Diff: 1146 lines (+213/-371) (has conflicts)
21 files modified
include/shared/mir/graphics/android/sync_object.h (+2/-2)
include/shared/mir/graphics/android/syncfence.h (+2/-19)
include/test/mir_test_doubles/mock_hwc_organizer.h (+2/-2)
src/server/graphics/android/android_hwc_factory.cpp (+1/-1)
src/server/graphics/android/hwc11_device.cpp (+25/-35)
src/server/graphics/android/hwc11_device.h (+3/-4)
src/server/graphics/android/hwc_layerlist.cpp (+47/-23)
src/server/graphics/android/hwc_layerlist.h (+18/-14)
src/server/graphics/android/internal_client_window.cpp (+2/-1)
src/server/graphics/android/server_render_window.cpp (+2/-1)
src/shared/graphics/android/mir_native_window.cpp (+3/-19)
src/shared/graphics/android/syncfence.cpp (+16/-6)
tests/integration-tests/graphics/android/test_display_integration.cpp (+2/-2)
tests/unit-tests/client/android/CMakeLists.txt (+0/-1)
tests/unit-tests/client/android/test_android_syncfence.cpp (+0/-91)
tests/unit-tests/client/android/test_client_surface_interpreter.cpp (+1/-0)
tests/unit-tests/graphics/android/test_hwc11_device.cpp (+45/-119)
tests/unit-tests/graphics/android/test_hwc_device.cpp (+3/-3)
tests/unit-tests/graphics/android/test_hwc_layerlist.cpp (+26/-24)
tests/unit-tests/graphics/android/test_internal_client_interpreter.cpp (+12/-3)
tests/unit-tests/graphics/android/test_server_interpreter.cpp (+1/-1)
Revision history for this message
kevin gunn (kgunn72) wrote :

I belived this is already being tracked whitin this bug
https://bugs.launchpad.net/unity8/+bug/1215039
- but this is a good description of a side effect

Changed in mir:
importance: Undecided → Critical
status: New → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Jamie,

The flashing can happen if you still have surfaceflinger running while Mir is running. You should move surfaceflinger out the way first:

mount -o remount,rw /system
cd /system/bin # I think?
mv surfaceflinger surfaceflinger.hide
reboot
# Expect the Google logo to be all you see, even when boot complete

Then Mir will always have exclusive access to the display and won't fight/flash with surfaceflinger. Does it work for you?

Changed in mir:
status: Triaged → Incomplete
Revision history for this message
kevin gunn (kgunn72) wrote :

kdub using this bug association for his bug fix

Changed in mir:
status: Incomplete → In Progress
assignee: nobody → Kevin DuBois (kdub)
Revision history for this message
kevin gunn (kgunn72) wrote :

technically the bug was in CM10.1 hwcomposer + kernel FB....as well as the mir code interfacing to hwcomposer

Changed in mir (Ubuntu):
importance: Undecided → Critical
status: New → In Progress
assignee: nobody → Kevin DuBois (kdub)
Revision history for this message
Kevin DuBois (kdub) wrote :

fix coming...
https://code.launchpad.net/~kdub/mir/fix-1215979/+merge/187346

kevin gunn (kgunn72)
Changed in mir:
status: In Progress → Fix Released
Changed in mir (Ubuntu):
status: In Progress → Fix Released
Changed in cyanogenmod:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

  • auto-rsalveti Edit

Bug watches keep track of this bug in other bug trackers.