Mir

Mir's grey background looks ugly on phone

Bug #1215322 reported by Gerry Boland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Undecided
Daniel van Vugt
mir (Ubuntu)
Fix Released
Undecided
Unassigned
unity8 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Before the grey background, when phone booted, it went directly from the Google splash, which is white text on black background, to the shell screen.

Now after Google splash, you see this ugly grey fill the screen, until shell screen appears.

Can we make the grey a debugging option or something?

Related branches

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, grey shows you that the shell has failed to paint pixels where it should have, when it should have.

But to make it seamless we need more compositing hooks so the shell can override Mir's default clear function. It's bad for the shell to assume Mir will clear the screen to black all the time.

Changed in mir:
status: New → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually, the seamless transition work does require Mir changes. But I would like to leave the default grey so we can see where the transition is not yet seamless.

Changed in mir:
status: Invalid → Confirmed
assignee: nobody → Daniel van Vugt (vanvugt)
summary: - Mir's grey background looks ugly on phone
+ Shell startup transition is not yet seamless - grey background is
+ visible.
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I give in. We don't have an immediate timeline for when compositing control will be available to shells. So the workaround is to go back to the old black.

Changed in mir:
status: Confirmed → In Progress
Changed in unity8:
status: New → Invalid
summary: - Shell startup transition is not yet seamless - grey background is
- visible.
+ Mir's grey background looks ugly on phone
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.0.10

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
milestone: none → 0.0.10
Changed in mir:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mir - 0.0.10+13.10.20130827.1-0ubuntu1

---------------
mir (0.0.10+13.10.20130827.1-0ubuntu1) saucy; urgency=low

  [ Alan Griffiths ]
  * ipc: add a protocol version to the wire protocol so that we can bump
    it in future.
  * graphics::nested: Handling of output configuration changes.
  * graphics.nested: Hookup NestedDisplay to display change
    notifications.

  [ Daniel van Vugt ]
  * Introducing mir_demo_client_progressbar. It's pretty boring;
    designed to simulate key repeat scrolling in a terminal, as an aid
    for tracking down bug 1216472. . (LP: #1216472)

  [ Eleni Maria Stea ]
  * changed the GBMBufferAllocator constructor and class to use the
    gbm_device instead of the GBMPlatform to remove the dependency from
    the mg::Platform interface - this way we can use the
    GBMBufferAllocator with the NativeGBMPlatform (nested mir).

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 1025
 -- Ubuntu daily release <email address hidden> Tue, 27 Aug 2013 18:04:47 +0000

Changed in mir (Ubuntu):
status: New → Fix Released
Michał Sawicz (saviq)
affects: unity8 → unity8 (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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