Closed Bug 878656 Opened 12 years ago Closed 10 years ago

[OPEN_]Sometimes, after finish some operation, current is too large.

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: Firefox_Mozilla, Unassigned)

Details

Attachments

(1 file)

Sometimes, after we finish some operation, current is too large. For example: browser a page and then in standby, current is too large. In the Mozilla log file,it only has the register codec log, not has release log 01-06 00:02:18.914 604 636 E OMXCodec: Attempting to allocate OMX node 'OMX.qcom.audio.decoder.mp3' 01-06 00:02:18.934 604 636 E QC_MP3DEC: component_init[0x442e5000]component init: role = OMX.qcom.audio.decoder.mp3 01-06 00:02:18.934 604 636 E OMXCodec: Successfully allocated OMX node 'OMX.qcom.audio.decoder.mp3' In Andriod ,it has the release log: 02-16 10:14:04.309: ERROR/QC_MP3DEC(113): Killing timer thread... 02-16 10:14:04.309: ERROR/QC_MP3DEC(113): Timer thread exited 02-16 10:14:04.309: ERROR/QC_MP3DEC(113): Component-deinit m_drv_fd = -1 02-16 10:14:04.309: ERROR/QC_MP3DEC(113): COMPONENT DEINIT... 02-16 10:14:04.309: ERROR/QC_MP3DEC(113): OMX MP3 component destroyed
Which version of Firefox OS? If it is v1.1, this problem should be fixed by Bug 860760.
V1.0(In reply to Sotaro Ikeda [:sotaro] from comment #1) > Which version of Firefox OS? If it is v1.1, this problem should be fixed by > Bug 860760. V1.0. Is there some patch fit for V1.0?
blocking-b2g: --- → tef?
(In reply to khu from comment #2) > V1.0(In reply to Sotaro Ikeda [:sotaro] from comment #1) > > Which version of Firefox OS? If it is v1.1, this problem should be fixed by > > Bug 860760. > > V1.0. Is there some patch fit for V1.0? ni?(Sotaro)
Flags: needinfo?(sotaro.ikeda.g)
(In reply to Andrew Overholt [:overholt] from comment #3) > > V1.0. Is there some patch fit for V1.0? > > ni?(Sotaro) There is no patch for v1.0.1. A patch of Bug 860760 has a bug and need to fix it. I create a patch for v1.0.1.
Flags: needinfo?(sotaro.ikeda.g)
I created the patch, but I do not know qcom support this capability. OMXCodec is modified from android default by qualcomm. The support of OMXCodec and hw is an area of qcom's support.
Are we actually considering this as a possible 1.0.1 blocker? What's the exact user impact here - x% more power consumption when doing y?
blocking-b2g: tef? → -
this will not be fixed it is a driver issue
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: