Closed Bug 820282 Opened 12 years ago Closed 7 years ago

Enabling the FM radio HW when we know it can't play is probably bad for battery life

Categories

(Core :: DOM: Device Interfaces, defect)

19 Branch
ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED INVALID
blocking-basecamp -

People

(Reporter: cjones, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [blocker-call-awaiting-821063][tech-p1])

See bug 815452 comment 38.

If the hardware is smart and turns itself off when muted we should be OK, but the odds of that are ... not high ;).
Do we know how much current an enabled-but-not-playing FM radio chip draws?  Will leaving it running prevent us from suspending?
Flags: needinfo?
Flags: needinfo? → needinfo?(overholt)
Flags: needinfo?(overholt)
Michael, can you help with some info here?
Flags: needinfo?(mvines)
Flags: needinfo?(mvines)
Whiteboard: [blocker-call-awaiting-821063]
Putting this in NEEDINFO so it doesn't come up in our daily triage sessions until we have the information.
Flags: needinfo?(rsomani)
We will have update on this tomorrow. Getting power impact of keeping fm on mute but not turned off.
Flags: needinfo?(rsomani)
If we don't have a good answer by Friday, we will probably minus this - it could be renomm'ed later if more data becomes available.
Keeping it muted vs off has noticable impact. Power numbers went up for incall use case when fm was muted.
This would be nice to fix but we discussed it during triage and don't think we can block on it.  Obviously if anyone disagrees they should feel free to re-nom.
blocking-basecamp: ? → -
Needed for competitive parity in power usage.
Whiteboard: [blocker-call-awaiting-821063] → [blocker-call-awaiting-821063][tech-p1]
Keywords: perf
This is no longer a thing we care about.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.