Media/WebRTC/Peak: Difference between revisions

From MozillaWiki
< Media‎ | WebRTC
Jump to navigation Jump to search
Line 19: Line 19:


* There is a bad interaction with the high resolution peak screen that makes links not work properly. Install all the patches from here: https://bugzilla.mozilla.org/show_bug.cgi?id=883646. Note that the first 7 of these have already landed on m-i, so you may only need the 8th depending on when you update and which tree you are on.
* There is a bad interaction with the high resolution peak screen that makes links not work properly. Install all the patches from here: https://bugzilla.mozilla.org/show_bug.cgi?id=883646. Note that the first 7 of these have already landed on m-i, so you may only need the 8th depending on when you update and which tree you are on.
* The patchsets at: https://github.com/YiyiLee/webrtc-perf-patches should get WebRTC working. However, because the Peak has more CPU, you do not need as aggressive tuning. A new patchset is coming shortly.

Revision as of 14:31, 21 June 2013

Notes on getting WebRTC Working on a Peak

Here are some ad hoc notes on how to get WebRTC working on a peak as of June 21, 2013. This assumes you already know how to compile and install B2G, and just covers stuff that's special to the peak.

Hopefully this will be unnecessary soon.

  • Turn on developer mode on the peak so that adb can copy stuff. I believe: (Device Information >More Information > Developer > Console Enabled)
  • You will need a backup directory of the Peak's system directory.
   mkdir ${B2G}/backup-peak
   adb pull /system ${B2G}/backup-peak/system
   export ANDROIDFS_DIR=${B2G}/backup-peak
  BRANCH=master ./config.sh peak
  • There is a bad interaction with the high resolution peak screen that makes links not work properly. Install all the patches from here: https://bugzilla.mozilla.org/show_bug.cgi?id=883646. Note that the first 7 of these have already landed on m-i, so you may only need the 8th depending on when you update and which tree you are on.