This bug is to measure the power consumption after we migrate to MediaCodec on Flame.

I play the attached video clip from video app. Here is my testing environment. * gecko version: 54f71a0db6059318089e9d30fc429091c3b461dd * gaia version: 7b965db30278e46aaaa2a78555c187a041ab7864 * FW-Release: 4.4.2 * Bootloader: L1TC000118D0 * unit: mA I capture the power consumption in the 3 stages. 1. restart the device in homescreen 2. play the video clip 3. pause the video omx-codec media-codec homescreen 303.0329 295.4528 playing 356.07 459.45 pausing 292.89 431.18 It looks like when media-codec in pausing mode, it still uses much power. In pausing mode, I check the CPU usage from top. The CPU usage is low(top one is about 1~3%). So that I think it's not the problem from CPU. Hi m1 and Wesly, Can you get someone to help this issue? Thanks.

caf's b2g OMXCodec::pause() is modified from aosp OMXCodec::pause(). It set OMX IL component state to OMX_StatePause. https://www.codeaurora.org/cgit/quic/la/platform/frameworks/av/tree/media/libstagefright/OMXCodec.cpp?h=b2g_kk_3.5#n4891 Semantics of OMXCodec::pause() is different between caf's b2g and aosp. aosp one is just to stop reading data source. caf's b2g is set omx il component state to OMX_StatePause.

OMXCodec and MediaCodec(ACodec) use same OMX IL component. The difference exists only to "how to use the OMX IL component".

We'll look at this once bug 1129264, and likely the fixes referenced by bug 1129264 comment 4 are uplifted to v2.2

aaaand by bug 1129264 I of course mean bug 1033935, and bug 1033935 comment 4 :)

> Hi m1 and Wesly, > Can you get someone to help this issue? Thanks. Sorry for late, Steven! As discussed offline, so far we don't have further contract with T2M for 2.2 work on Flame (existing contract covers 1.3 & 2.0, while new contract on-going is for only L-BSP porting). Thus we need to find other way forward to handle this issue (for example other device with 2.2). Thank you.

Mass closing do to inactivity. Feel free to re-open if still needed.