853698 - [System] Device does not enter cpu idle state (AP's core 0 voltage)

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::System, defect, P1)

Description

[Leo]

1. Title : Device does not enter cpu idle state (AP's core 0 voltage)
2. Precondition : Turn on deivce
3. Tester's Action : Check device state after turn on.
4. Detailed Symptom :  When device is turned on, the AP's core voltage never goes down.
5. Expected : Device should enter cpu idle state (AP's core 0 voltage), when there is no input for certain period of time.
6. Reproducibility: Y
1) Frequency Rate : 100%
7. Gaia revision : 

FYI.
It was observed that during booting procedure (with firefox logo and rectangle logo) the AP's core can go down to 0 when there is no user input. However, once the system app is loaded, it never goes down.

Comment 1

[Leo]

Attachment: Pull Request URL 8757

After system is loaded, wrapper.css apply progress.gif to background-image of #wrapper-activity-indicator. In this situation, even if user does not input any action, device does not enter cpu idle state because system app always use cpu for representing progress.gif (Though this image is not shown to user).

Comment 2

[Leo]

When applying Bug 874010 patch, cannot enter CPU Idle state too. (If we role back this patch, device can enter CPU Idle state)

Can you check this?

Comment 3

[Leo]

Sorry. Bug 874010 -> Bug 838486

Comment 4

[Leo]

Dear Julien Wajsberg, 
When Bugzilla 838486 patch is applied, the phone can't go to cpu idle state. 
Plz check the issues.

Comment 5

[Julien Wajsberg [:julienw]]

This patch never landed.

master: 8d877e1d7341f294934f104b30683bf753d00604

Comment 6

[Julien Wajsberg [:julienw]]

Leo, regarding the other problem, I suspect something deeper (ie: we should probably stop the animations from running when the screen is off). Could you please file a new bug ?

Comment 7

[Gareth Aye [:gaye] (back from PTO)]

I was not able to uplift this bug to v1-train.  If this bug has dependencies which are not marked in this bug, please comment on this bug.  If this bug depends on patches that aren't approved for v1-train, we need to re-evaluate the approval.  Otherwise, if this is just a merge conflict, you might be able to resolve it with:

  git checkout v1-train
  git cherry-pick -x -m1 8d877e1d7341f294934f104b30683bf753d00604
  <RESOLVE MERGE CONFLICTS>
  git commit

Comment 8

[Julien Wajsberg [:julienw]]

I'll see what I can do.

Comment 9

[Julien Wajsberg [:julienw]]

v1-train: a6d5dc7e091409f442ca54e147c2b912dd688ef7

Comment 10

[Leo]

This issue seems like it exists. As discussed in San Diego marking this for work week.

Comment 11

[Julien Wajsberg [:julienw]]

Leo, I filed Bug 877215 to track this specific issue.