Closed Bug 769167 Opened 9 years ago Closed 8 years ago
[Tracking bug] verify B2G frame rate meets required rate
Test B2G frame rate on Panda Board: target is 60fps
Panda board is believe to be most analogous device with video out to otoro type phones. If possible we should probably disable one of the two cores on the panda board to better simulate. mwu, cjones said you would be able to help on the stand up of b2g on the panda board. Ideally we'd have this done before July 20.
I'll get it running as soon as I receive a panda board.
cjones, michael, what scenarios should we be trying to measure the framerate of? Transitions during launching of apps from the home screen?
There are three broad classes - transitions and animations. This includes the animation when opening/closing apps, transitioning between "pages" within apps, and rotating the screen. - scrolling/panning/zooming. Basically the same thing as fennec, but we want to test panning/zooming of arbitrary content in the "browser app", in addition to panning of lists within gaia apps. - raw perf: video playback and camera preview are the big ones. WebGL games/demos and 2D canvas games after that.
Bug 771653 needs to be fixed but once fixed, the pandaboard should be able to output video fine. I've landed support for building for the pandaboard. The pandaboard is a bit tricky to setup - some notes: - Rebooting from android into fastboot doesn't work. So, in order to use the flash script, you have to manually put the device into fastboot mode by holding the GPIO_113 button while plugging in power. - You have to format the sd card using the instructions in devices/ti/panda/README, which partitions the card in a way that resembles normal Android devices. - The default partition scheme uses *very* little sd card space - I think no more than 1-2GB.
Depends on: 771653
I want to be certain I understand. Once bug 771653 is fixed, we'll be able to build the pandaboard as one of the device targets when building a b2g build?
(In reply to Clint Talbert ( :ctalbert ) from comment #6) > I want to be certain I understand. Once bug 771653 is fixed, we'll be able > to build the pandaboard as one of the device targets when building a b2g > build? You can already build the pandaboard as one of the device targets in a B2G build. You'll just have to apply the patch I posted to bug 771653 to the gecko repo to make it work.
blocking-basecamp: ? → +
blocking-kilimanjaro: --- → +
Summary: Test B2G Frame rate → verify B2G frame rate meets required rate
Malini, is this a good "get Eideticker working with b2g" metabug? Are you working on this?
Assignee: nobody → mdas
While we obviously need this from a product qualification standpoint, we discussed during triage that it's not a release blocker from an engineering perspective. Therefore I'm clearing the basecamp-blocker flag but please re-nom if this is incorrect in your opinion. (How will we keep track of these sorts of issues if we don't + them?)
blocking-basecamp: + → ---
(In reply to Chris Jones [:cjones] [:warhammer] from comment #8) > Malini, is this a good "get Eideticker working with b2g" metabug? Are you > working on this? Yes, and yes she is.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #8) > Malini, is this a good "get Eideticker working with b2g" metabug? Are you > working on this? Yes, and it can replace Bug 781178 as a tracker bug if you prefer.
Doesn't matter to me! :)
(In reply to Chris Jones [:cjones] [:warhammer] from comment #12) > Doesn't matter to me! :) heh okay, I think you can keep this as a metabug, it depends on all other related bugs.
Summary: verify B2G frame rate meets required rate → [Trackingverify B2G frame rate meets required rate
Summary: [Trackingverify B2G frame rate meets required rate → [Tracking bug] verify B2G frame rate meets required rate
No longer tracking fps on pandaboards. Moved to on-device fps testing: https://datazilla.mozilla.org/b2g/ and b2g eideticker results will eventually be posted there as well: Bug 909796
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.