Closed Bug 1064483 Opened 11 years ago Closed 7 years ago

Three splash screens at boot is too much

Categories

(Firefox OS Graveyard :: Performance, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: asa, Unassigned)

References

Details

Tested: Flame phone with latest nightly JellyBean builds shallow flashed on v123 base image. When I reboot my Flame, I see the Thundersoft splash screen for about 12 seconds, then a Firefox OS splash screen with an animated fox and the Firefox logo and Firefox OS wordmark for about 14 seconds, then a black screen for approximately 1 second, and then a second Firefox OS splash screen with just the Firefox logo and Firefox OS wordmark shows for about 13 seconds, then finally I get the lockscreen. This is awful. We should immediately remove at least one of the Firefox OS splash screens, and if we can, we should drop the Thundersoft screen and just boot right into a Firefox OS look and then to the lock screen. (Also, 45 seconds from power button to lock screen is pretty awful, IMO.)
Blocks: 994998
Component: General → Performance
I'm not sure that any of the splash screens add any delay to the boot, but I could be wrong. I only see Thundersoft (for about 26 seconds), and then the "based on mozilla" splash for 14 seconds (includes the black screen time). So total 40 seconds from reboot until home screen. The Thundersoft one is displayed by the bootloader. It gets replaced when b2g actually launches. By reducing the number of splash screens, you'll just be making one of the other ones show up for a longer period of time.
I don't really care if it improves the overall load time, three different splash screens is just ugly.
Summary: Three splash screens at boot is too much and too slow → Three splash screens at boot is too much
Agree with Asa, I think the number of boot splash screens is excessive. I know the first one (thundersoft) is the OEM branding logo and is part of the bootloader, so that is tricky to change. Is there a spec for OEM branding for FFXOS? Perhaps there could be a standard FFXOS bootloader splash where the OEMs can put their brand logo on the bottom edge, in order to make the experience more consistent across various devices/OEMs? As for the other splashes, I rather like the animated fox bootanimation.zip, I hope that stays. I think I could do without the static "Firefox OS" splash and the "Made with Mozilla Technology" splash as well. Perhaps those two static splashes could be combined into one if they must stay?
UX could be improved on multiple fronts, to look more snappy * Optimize our code that our logo is painted as early as possible (and less screentime for ThunderSoft) * Use the same artwork for our current stage 2 and 3 * Maybe include some sort of spinner / progress bar
Frederik, Is it even possible to put a non-looping spinner/progress bar [that shows actual boot progress] on a bootanimation the way they're structured? I know that we can have N-Number of different "stages" of the boot animation and we can define how long a pause or how many times each stage loops, but I don't see anywhere a mention that the bootanimation can be progressed at whatever time given changes reported by the system.
Blocks: 1204371
No longer blocks: 1204371
Depends on: 1204371
[Tracking Requested - why for this release]:
OS: Mac OS X → Gonk (Firefox OS)
Priority: -- → P3
Hardware: x86 → ARM
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.