The Flame developer reference phone is a milestone in Firefox OS device releases. The Flame hardware offers a representative set of specs — including FWVGA display and dual-core processor — to help developers build great content and experiences. A single hardware platform is also good for testers, making it easier to test and address specific software issues without having to worry about device model-specific bugs, etc.
If you have your phone in hand and want to start playing with it, developing and distributing apps, or contributing to the Firefox platform, the following links will get you where you need to go:
If you’d like to find out more about updating the operating system, recovering it, pushing apps to it, or phone specs, you’ll find the information you need below.
Our device manufacturer partner has made the device available to order on everbuying.com, for US$170 including global shipping (device cost is $145, shipping is $25 and custom fees may still apply, depending on the destination country). The device is bootloader and carrier unlocked, and it utilizes a quad-band GSM+UMTS radio so that it can work with a wide variety of operators/carriers.
Note: Another option for getting hold of a Flame is to participate in our Flames for Apps scheme, aimed at experienced HTML5 app developers wishing to port their highly-rated apps onto Firefox OS.
We will have two main "channels" of Firefox OS software version releases for the Flame phone:
Note: Windows users will need to install a driver to enable USB communication with their phones. See how to do this in the Windows section below. Linux users may need to add a udev rule; see the Linux and Mac section.
While our partners are working out a final storage solution for the software builds, you can get recovery files and tools at the following Onedrive storage locations:
To install the base image on your device:
adb devices command in a terminal..zip in the case of Mac / Linux, the .exe in the case of Windows)sudo ./flash.sh (if you don't run it using sudo, the flash script may fail to see your device, and it won't work).Note: You are also welcome to build your own builds to install on the Flame: see Building and installing Firefox OS.
Note: For this current build, Nightly development builds of Firefox OS do not support A-GPS, which may lead to slow performance of GPS functionality. We plan to resolve this in an updated future Nightly channel.
b2g-XX.XX.en-US.android-arm.tar.gz and gaia.zip files../shallow_flash.sh -g /path/to/gaia.zip -G /path/to/b2g-XX.XX.en-US.android-arm.tar.gz
./shallow_flash.sh -g/path/to/gaia.zip -G/path/to/b2g-XX.XX.en-US.android-arm.tar.gz
Note: If you get a "permission denied" error when running the above command, your shell script probably doesn't have the right permissions. Running chmod +x shallow_flash.sh on it should solve this problem.
Note: A "shallow flash" only updates Gecko and Gaia, as opposed to a full flash, which updates Gecko/Gaia, but also the underlying Gonk layer and associated binaries particular to that device type. This is why it is a good idea to update to the official base image first, as suggested above, then to shallow flash over the top of that, once you've got the Gonk/binary layer right.
Shallow flash flashes more than just Gecko and Gaia so all the data on the device is lost!
Once the install procedure finishes the phone should reboot into the updated build and the first time user workflow.
After updating Gecko and Gaia to nightly with the v123 base image, there will be a mismatch between the fonts that Gecko and Gaia expects and what the base image provides. To fix this, download our font update package, extract it, navigate into the directory created by extracting, and run the supplied flash.sh script.
If flashing a new build to your phone fails to work, your phone may becomes unresponsive, and the phone may always reboot in recovery mode. The recovery mode allows you a few actions (reboot, update from adb, wipe data, wipe cache, update from sdcard). Unfortunately, selecting update from adb triggers a sideload mode and you cannot use the other adb commands, only adb sideload would work but the various flash scripts rely on other adb commands.
In this case, you can probably force fastboot mode as follows:
The phone should only display the very first static logo and stay there, without displaying the boot animation. It seems stuck but is not really: it is in fastboot mode and is waiting for something on the USB cable. At this step, a computer on the other side of the USB cable should see the phone when running fastboot devices to list the connected devices. Note that regular adb would not see the device, only fastboot sees it. In this mode, you can use the flash script to install v123 as explained above. As the script does use both adb and fastboot commands, you may see some initial error and warnings from adb, but eventually the device should be flashed properly at the end.
If flashing a new build to your phone fails to work, your phone becomes unresponsive, and the phone cannot enter fastboot mode, you can use emergency mode for recovery. A USB cable and the Emergency Download Tool are required to enter emergency download mode. Install this tool and follow the instructions.
You can enter recovery mode to clear your phone data or manually update the firmware. There are two ways to enter this mode:
adb reboot recovery on the command line.When in recovery mode, press the Volume up/down keys to move the selection highlight, and the Power key to select. Make sure you have your phone data (Contacts, SMS, etc.) backed up before clearing data, and your upgrade packages downloaded before updating.
The App Manager tool makes it easy to push apps to your phone, for testing, etc. Full instructions are available in the article Using the App Manager.
Important: Additional platform-specific instructions are available below. Follow these first before attempting to use the App Manager.
No additional steps should be required if you are using a Linux or Mac system, although depending on your Linux distro, you might need to add a udev rule for your phone, which will look something like the following:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9025", GROUP="users", MODE="0666"
Make sure to --reload-rules, then unplug and replug and your device before continuing.
To access the Flame device with the App Manager/ADB, a USB driver is required. Follow the steps outlined in the below sections to install it.
Download the Windows driver from this location. Once downloaded, extract the contents of the ZIP file to a suitable place on your hard drive.
Note: The Android Debug Bridge (ADB) must be already installed.
At this point, connect your Flame device to your computer using a USB cable.
To install the driver, open the Alcatel_USB_Driver_Q_4.0.0_2013_11_11_noinstall directory within the extracted ZIP file and double click on the DriverInstaller.exe executable. You may receive a warning at this point that the executable is from an unknown publisher. If so, select the Yes button and the executable will be launched.
Click on the Install button to install the driver.
After the driver installs, you can check that it is working by opening a command line window and typing adb devices. This should list the connected device with an output something like:
List of devices attached 3561d02a device
If your device is not showing up here, check in the Windows Device Manager. Your Flame may be showing up as "ACER ADB Interface". You can confirm this by unplugging the device and seeing if it disappears from the device manager. Uninstall the driver software by right-clicking on "ACER ADB Interface" and clicking uninstall. Be sure to check the box in the dialog to delete the driver software. Now re-run the installer above. It is advisable to set the screen timeout on your Flame to something high (Settings > Display > Screen timeout) as Windows sometimes appears to reinstall the default drivers when the screen turns off.
You can adjust the available RAM capacity to see how apps perform on Firefox OS phones with lower memory footprints.
This is accomplished by entering fastboot mode (install fastboot first, which is available on the same SDK page as ADB) and typing:
adb reboot bootloader fastboot oem mem [0|256-1024]
“0” is the memory automatically detected and “256-1024” is the number of megabytes. For example, if you want to adjust device RAM capacity to 512M, enter fastboot oem mem 512.
You'll need to then reboot your device for the settings to take effect. This can be done using:
fastboot reboot
The current memory size can be returned by entering fastboot mode and typing:
fastboot getvar mem
Network:
Hardware: You can find more of the hardware features listed on our Phone and device specs page.
Additional features include: