Closed
Bug 979419
Opened 11 years ago
Closed 11 years ago
Lazy load the world in oncall.html
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(blocking-b2g:1.3T+)
RESOLVED
WONTFIX
blocking-b2g | 1.3T+ |
People
(Reporter: etienne, Assigned: etienne)
References
Details
We did a *lot* of work to have a lean critical path when launching the dialer.
But we did nothing for the call screen... :/
We can probably make some significant progress optimizing the a "critical path" where the "critical path" is -> ringing/vibrating to alert of a new incoming call.
Assignee | ||
Comment 1•11 years ago
|
||
Assigning myself because I have a WIP.
Assignee: nobody → etienne
Blocks: 973596
Updated•11 years ago
|
blocking-b2g: --- → 1.3+
Updated•11 years ago
|
blocking-b2g: 1.3+ → 1.3T+
Assignee | ||
Comment 2•11 years ago
|
||
Bad news.
My patch is shaping up nicely [1], *but*, although we do start vibrating about 300ms earlier on a keon, we ring at best at the same time.
I'll profile this better tomorrow but getting the ringtone out of the mozSettings database is killing us.
Tried waiting for the ringtone to be loaded before continuing lazy loading stuff, but no luck, same ~1550ms between the moment we get the system message and the moment we call .play() on the ringtone player.
[1] https://github.com/etiennesegonzac/gaia/compare/bug-979419-lazy-load-oncall-html
Assignee | ||
Comment 3•11 years ago
|
||
Going with bug 980984 instead.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•