[Boot splash screen] Inconsistent spinning-logo screens for startup and system image update

[Matthew Paul Thomas]

Ubuntu 14.10 r183

1. Wait for an Ubuntu update to become available.
2. Install the update, confirming the prompt to restart the phone.

What happens:
* The screen goes mostly black with a tiny, flat, dark orange, quickly spinning Ubuntu logo.
* The phone restarts.
* The screen goes black with a second, large, flat, pale orange, quickly spinning Ubuntu logo.
* The phone restarts.
* The screen goes black with a third, small, glowing, dark orange, slowly spinning Ubuntu logo.

What should happen:
* The Ubuntu logos should have exactly the same size, position, lighting, color, and speed on all screens where they appear.

<https://wiki.ubuntu.com/SoftwareUpdates#installing-mobile-system>: "If you choose 'Restart & Install', a variation of the shutdown screen should appear..."

<ogra_> mpt, to fix that properly you would have to run Mir in recovery :)
<larsu> ogra_: or change the graphics to be similar enough?
<ogra_> larsu, tricky .... one is a true color hi-res image, the other is more like a 64 color animated gif ...
<ogra_> even getting the colors to roughly match will be hard
<ogra_> it would be good to make them the same size per device and get rid of the awful progress bar in recovery at least ... but having them look the same will be a hard task

It may save time to fix bug 1335789 at the same time as this bug.

[Jani Monoses (jani)]

Should the unity logo be larger or the recovery logo be smaller?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

I was thinking the same thing :)

[Daniel van Vugt (vanvugt)]

Come to think of it, it is informative for the recovery and boot screens to look different. So the user knows what's happening. Although the addition of a line of text or progress indicator would suffice and you could indeed use more similar logos on both.

I'm not entirely sure if it's technically possible to make the recovery spinner as smooth as the boot spinner though. The latter is a Mir client using OpenGL, while I suspect the former doesn't have such luxuries as OpenGL in recovery mode(?).

[Matthew Paul Thomas (mpt)]

It would be fine for them to look as if they were intentionally different. As you suggest, a line of text and/or a progress bar would achieve that. The problem is that at the moment they look as if they're accidentally different.

[Jane Silber (silbs)]

This may be a different problem altogether, but the inconsistency of "I'm busy doing something" indicators extends to apps. The in-progress indicator as an app starts is 3 dots that seem to bounce off of each other. The in progress indicator in apps use when they are doing anything other than starting seems to be 3 dots that chase each other around in a circle. I understand that we may want the app in-progress indicator to be different than the system startup in progress indicator, but is it intentional to have 2 different app in-progress indicators?

[Daniel van Vugt (vanvugt)]

Jane: I suggest logging that bug in Unity8:
   https://bugs.launchpad.net/ubuntu/+source/unity8/+filebug

[Matthew Paul Thomas (mpt)]

Jane, I reported the inconsistency of the app-launch spinner as bug 1374449.

[Barry Warsaw (barry)]

Not a bug in the system-image client.

[Matthew Paul Thomas (mpt)]

There is yet a *fourth* Ubuntu spinner when you flash a phone with a new image. This one is an orange symbol on a white disc, while the other three are at least the usual white symbol on an orange disc.

Again, it's okay for the images to be different as long as they look deliberately different. Currently they look as if they've been done by four different designers.

[Jouni Helminen (jounihelminen)]

The design for the boot animation (which should also be used with a solid colour background when flashing) is here - it has been sent over to Mirco for development a while ago but not sure when it is going to be implemented

https://www.dropbox.com/sh/ulthdi43a7t2os9/AABd_E913XKUlaFhHenYLtzsa?dl=0

[Matthew Paul Thomas (mpt)]

The bug that Jouni was referring to seems to be bug 1367696.