This post is a follow-up to an earlier article I wrote about setting up a FirefoxOS development environment. I’m going to set up a Sony Z3C as the target device for Mobile OS software development. The Sony Z3C (also known as Aries or aosp_d5803 ) is a nice device for Mobile OS hacking as it’s an AOSP device with good support for building the OS binaries. I’ve set the phone up for both FirefoxOS and Android OS development, to compare and see what’s common across both environments.

I’m often asked “what are you working on?” Here’s a snapshot of some of the things currently on my teams’ front burners: Vertical Text (CSS Writing Modes) Shumway CSS Containment Image Downscale During Decode Webkit CSS Prefix Compatibility Media Source Extensions CSS Grid Encrypted Media Extensions JS Codecs FileSystem API SVG transform-origin Fira Fonts harfbuzz text shaping Web Animations WebVR Input Method Editors Runtime Hardware Rendering Validation unicode-range HTML5 Canvas Filters Off-main-thread HTML5 Canvas Rendering HTML5 Fullscreen Rust in Gecko I’m surely forgetting a few things, but that’s a quick snapshot for now.

I’m posting the steps I took to create the FirefoxOS dev environment for the Flame device. We use the Flame as our reference device on the Platform Rendering team. I had to re-do this recently on a new computer and I figure this might help others in the same boat. These steps assume you can already build the desktop version of Firefox on your computer. Get ADB Turn on ADB debugging on your device.

I’ve spent the last 3 weeks traveling in Asia for Mozilla and W3C business. On May 20 to 24, my team was in Taiwan for a series of meetings on Platform Rendering (Layout, Graphics, and Media.) It’s always an enlightening experience for me when I spend time with such a talented group of people: I’ve pasted the calendar we followed for the week, below. The links point to raw notes from the sessions (where available.