diff options
Diffstat (limited to 'files/pl/archive/b2g_os')
13 files changed, 0 insertions, 1871 deletions
diff --git a/files/pl/archive/b2g_os/add-ons/index.html b/files/pl/archive/b2g_os/add-ons/index.html deleted file mode 100644 index 7fe91371cd..0000000000 --- a/files/pl/archive/b2g_os/add-ons/index.html +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Firefox OS add-ons -slug: Archive/B2G_OS/Add-ons -translation_of: Archive/B2G_OS/Add-ons ---- -<p class="summary">Firefox OS 2.5 introduces support for add-ons, a feature that desktop users have known and loved since the beginning of Firefox. Add-ons on Firefox OS are even more powerful and can customize not only the browser, but the whole phone experience, including tweaks to the homescreen and system apps like E-Mail and Messages. This page tells you everything you need to know to get started with creating Firefox OS add-ons and get involved with the add-ons community.</p> - -<div class="note"> -<p dir="ltr"><strong>Note</strong>: Firefox OS add-ons are based on the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions">WebExtensions API</a>, which is also supported in Firefox desktop starting with version 42 and is based on the extension APIs used in Chrome and Opera.</p> -</div> - -<h2 id="Prerequisites">Prerequisites</h2> - -<p>You should follow the below steps to get set up to start developing extensions.</p> - -<h3 dir="ltr" id="1._Flash_your_phone_to_Firefox_OS_2.5">1. Flash your phone to Firefox OS 2.5</h3> - -<p dir="ltr">Firefox OS add-ons are only supported on Firefox OS 2.5 and later. Here’s a list of supported devices and how to update them (this list is incomplete, and will be added to as time goes on.)</p> - -<ul> - <li dir="ltr">Flame (recommended): See <a href="/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame#Quick_guide_to_updating_your_device">Quick guide to updating your Flame</a>.</li> -</ul> - -<h3 id="2._Enable_USB_Debugging">2. Enable USB Debugging</h3> - -<p>In the <em>Settings</em> app on the device, select <em>Developer > Debugging via USB > ADB and Devtools</em>. You should now be able to debug installed apps using WebIDE, either via a USB cable, <a href="/en-US/docs/Tools/Remote_Debugging/Debugging_Firefox_OS_over_Wifi">and over Wifi</a> (no USB cable required.)</p> - -<h3 id="3._Set_up_WebIDE">3. Set up WebIDE</h3> - -<p>The <a href="/en-US/docs/Tools/WebIDE">WebIDE</a> tool is part of Firefox and can be used to install add-ons on your phone during development — see <a href="/en-US/docs/Mozilla/Firefox_OS/Add-ons/Developing_Firefox_OS_add-ons#Testing_your_add-on_using_WebIDE">Testing your add-on using WebIDE</a> for more information.</p> - -<h2 id="See_also">See also</h2> - -<h3 id="Developing">Developing</h3> - -<ul> - <li dir="ltr"><strong>Tutorial</strong>: <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Add-ons/Developing_Firefox_OS_add-ons">https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Add-ons/Developing_Firefox_OS_add-ons</a></li> - <li dir="ltr"><strong>In-depth example</strong>: <a href="https://hacks.mozilla.org/2015/11/building-an-ios-style-unread-notifications-add-on-for-firefox-os/">https://hacks.mozilla.org/2015/11/building-an-ios-style-unread-notifications-add-on-for-firefox-os/</a></li> - <li dir="ltr"><strong>API reference</strong>: <a href="https://developer.mozilla.org/en-US/Add-ons/WebExtensions">https://developer.mozilla.org/en-US/Add-ons/WebExtensions</a></li> -</ul> - -<h3 dir="ltr" id="Distributing">Distributing</h3> - -<ul> - <li dir="ltr"><strong>Submitting to Marketplace</strong>: <a href="/en-US/docs/Mozilla/Marketplace/Add-on_submission">Add-on submission</a></li> - <li dir="ltr"><strong>Review criteria</strong> (working draft): <a href="/en-US/docs/Mozilla/Marketplace/Add-on_submission/Review_criteria">Add-on review criteria</a></li> -</ul> - -<h3 dir="ltr" id="Get_involved">Get involved</h3> - -<ul> - <li dir="ltr"><strong>Mailing list</strong>: <a href="https://mail.mozilla.org/listinfo/dev-addons">https://mail.mozilla.org/listinfo/dev-fxos</a></li> - <li dir="ltr"><strong>Discourse forum</strong>: <a href="https://discourse.mozilla-community.org/c/add-ons/development">https://discourse.mozilla-community.org/c/add-ons/development</a></li> - <li dir="ltr"><strong>IRC</strong>: irc.mozilla.org, #webextensions and #fxos</li> - <li dir="ltr"><strong>Join the unofficial Telegram group</strong>: <a href="https://telegram.me/joinchat/BTLPMAC90O9n8cpgsZ03_A">https://telegram.me/joinchat/BTLPMAC90O9n8cpgsZ03_A</a></li> - <li dir="ltr"><strong>Let us know what new APIs we should prioritize</strong>: <a href="https://webextensions.uservoice.com/forums/315663-webextension-api-ideas">https://webextensions.uservoice.com/forums/315663-webextension-api-ideas</a></li> - <li dir="ltr"><strong>Follow us on Twitter</strong>: <a href="https://twitter.com/MozWebExt">@MozWebExt</a></li> -</ul> diff --git a/files/pl/archive/b2g_os/firefox_os_wstępne_budowanie/index.html b/files/pl/archive/b2g_os/firefox_os_wstępne_budowanie/index.html deleted file mode 100644 index f9e294568c..0000000000 --- a/files/pl/archive/b2g_os/firefox_os_wstępne_budowanie/index.html +++ /dev/null @@ -1,381 +0,0 @@ ---- -title: Firefox OS wstępne budowanie -slug: Archive/B2G_OS/Firefox_OS_wstępne_budowanie -translation_of: Archive/B2G_OS/B2G_OS_build_prerequisites ---- -<div class="summary"> - <p><span class="seoSummary">Before obtaining the code to build Firefox OS, you need a properly configured <a href="https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions" title="https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions">build system</a> — this page shows you how. You can currently build on 64-bit Linux distributions and OS X.</span></p> -</div> -<div class="note"> - <p><strong>Note</strong>: To build Firefox OS onto a phone, begin with your phone NOT connected to your computer. We'll tell you when to plug it in.</p> -</div> -<h2 id="Posiadaj_kompatybilne_urządzenieemulator">Posiadaj kompatybilne urządzenie/emulator</h2> -<p>You need to have a compatible device to build onto, or to use an emulator. Though we support several phones, some have multiple variations. We currently support specific variations and some devices have better support than others.</p> -<div class="note"> - <p><strong>Note</strong>: Mozilla's <a href="https://github.com/mozilla-b2g/B2G">B2G source code</a> effectively is the reference implementation of B2G, but phone vendors are free to add patches or make changes. When you buy an Alcatel One Touch for example, it contains the vendor's version. This doesn't make a difference for the installed apps, but it can at the platform level. The Nexus 4 port is maintained directly by Mozilla; so it's a lot more likely to work with our version of Gecko out of the box than other tier 3 devices.</p> -</div> -<h3 id="Krok_1">Krok 1</h3> -<p>Tier 1 devices represent a primary target for development and will typically be the first to receive bug fixes and feature updates.</p> -<dl> - <dt> - Keon</dt> - <dd> - Keon is the <a href="http://www.geeksphone.com/" title="http://www.geeksphone.com/">Geeksphone</a> Keon device, which was one of the initial developer phones. Note that builds for this device are provided by Geeksphone.</dd> - <dt> - Inari</dt> - <dd> - Inari is another testing device. Use this configuration to build for the ZTE Open device. <strong>Warning:</strong> newer builds of Firefox OS may have trouble booting on the ZTE Open's default boot partition.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators" title="en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators">Emulator (ARM and x86)</a></dt> - <dd> - There are two emulators available: one emulates ARM code and the other runs everything in x86 code. <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators" title="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators">Learn more about installing and using the emulators</a>.</dd> - <dd> - <strong>Note that you shouldn't use the x86 emulator — it is hard to install and not well supported.</strong></dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client" title="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client">Desktop</a></dt> - <dd> - You can also build a desktop version of Firefox OS; this runs <a href="/en-US/docs/Mozilla/Gecko" title="/en-US/docs/Mozilla/Gecko">Gecko</a> in a <a href="/en-US/docs/XULRunner" title="/en-US/docs/XULRunner">XULRunner</a> application, and you then use the <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Introduction_to_Gaia" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Introduction_to_Gaia">Gaia</a> user experience inside it.</dd> -</dl> -<p>You can, of course, build the <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client" title="en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client">desktop client</a> or one of the <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators" title="en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators">emulators</a> without a phone.</p> -<h3 id="Krok_2">Krok 2</h3> -<p><span id="answer_long1" style="display: block;">Tier 2 devices are generally functional and many developers (especially app developers) are using them, so they tend to pick up changes secondarily.</span></p> -<dl> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Samsung_Nexus_S" title="/en-US/docs/Mozilla/Firefox_OS/Samsung_Nexus_S"><span class="link-https">Samsung Nexus S</span></a></dt> - <dd> - The known working model numbers of Nexus S devices are GT-I9020A and GT-I9023. Others may work.</dd> - <dt> - Samsung Nexus S 4G</dt> - <dd> - The SPH-D720 is supported as a tier 2 device.</dd> -</dl> -<h3 id="Krok_3">Krok 3</h3> -<p><span id="answer_long1" style="display: block;">Firefox OS can be built for these devices, but they are not being actively worked on a regular basis by core developers. Their reliability and feature set may lag noticeably behind tier 1 and even tier 2 devices.</span></p> -<dl> - <dt> - Samsung Galaxy S2</dt> - <dd> - The only model that works is the i9100; no other variants are officially compatible. (i9100P might work, since the only change is a NFC chip added)</dd> - <dt> - Samsung Galaxy Nexus</dt> - <dd> - We are not currently aware of any variations that are not compatible.</dd> - <dt> - Nexus 4</dt> - <dd> - Some users on IRC have tested this successfully. May or may not require reflashing to Android 4.3 first if was running 4.4 (Android <a href="https://developers.google.com/android/nexus/images#occamjwr66y">images available from Google</a>)</dd> - <dt> - Nexus 5</dt> - <dd> - Some users on IRC have tested this successfully.</dd> - <dt> - Tara</dt> - <dd> - Tara is another testing device. Manifest of Tara is in master branch only. The script of getting Tara code is "BRANCH=master ./config.sh tara".</dd> - <dt> - Unagi</dt> - <dd> - Unagi is a phone being used as a test and development platform as a low-to-midrange smartphone. Many core Firefox OS developers are working on Unagi.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Pandaboard" title="/en-US/docs/Mozilla/Firefox_OS/Pandaboard">Pandaboard</a></dt> - <dd> - The Pandaboard is a development board based on the OMAP 4 architecture, used to do development work on mobile platforms.</dd> -</dl> -<div class="warning"> - <strong>Important</strong>: Only devices running at least <strong>Android 4</strong> (aka <strong>Ice Cream Sandwich</strong>) are supported. If your device is listed above but running an older version of Android, please update it before doing anything.</div> -<div class="note"> - <p><strong>Note</strong>: Tier 2 and Tier 3 devices have a software home button instead of a hardware home button</p> - <p>All Tier 1 devices have a hardware Home button which returns the user to the home screen. Most current ICS based Android devices use onscreen touch buttons for navigation. We have a virtual home button for the devices without hardware home button now. If it's not automatically enabled, <span style="line-height: 1.5em; font-size: 14px;">open the Settings app, go to the <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a>, and then toggle on the <a href="/en-US/Firefox_OS/Debugging/Developer_settings#Enable_software_home_button">Enable software home button</a> preference.</span></p> - <p><span style="line-height: 1.5em; font-size: 14px;">In 1.4 there is also a developer option for "Home gesture enabled"; enabling that will remove the on-screen home button in favor of swiping up from the bottom of the screen.</span></p> -</div> -<h2 id="Wymagania_dla_systemu_GNULinux">Wymagania dla systemu GNU/Linux</h2> -<p>To build on Linux, you'll need:</p> -<ul> - <li>A <strong>64 bit GNU/Linux</strong> distribution (Ubuntu 12.04 recommended).</li> - <li>At least <strong>4 GB</strong> of RAM.</li> - <li>At least <strong>30 GB</strong> of available hard disk space.</li> -</ul> -<p>This is more than the bare minimum, but sometimes building fails just because it's missing resources. A typical error in this case is "<span style="line-height: 1.5;"><strong>arm-linux-androideabi-g++: Internal error: Killed (program cc1plus)</strong>".</span></p> -<p>You will also need the following tools installed:</p> -<ul> - <li><strong>autoconf 2.13</strong></li> - <li><strong>bison</strong></li> - <li><strong>bzip2</strong></li> - <li><strong>ccache</strong></li> - <li><strong>curl</strong></li> - <li><strong>flex</strong></li> - <li><strong>gawk</strong></li> - <li><strong>git</strong></li> - <li><strong>gcc / g++ / g++-multilib</strong></li> - <li><strong>make</strong></li> - <li><strong>OpenGL shared libraries</strong></li> - <li><strong>patch</strong></li> - <li><strong>X11 headers</strong></li> - <li><strong>32-bit ncurses</strong></li> - <li><strong>32-bit zlib</strong></li> -</ul> -<h3 id="Emulator_build_issues"><strong>Emulator build issues</strong></h3> -<p>If you are making an <strong>emulator</strong> build, you need to pay attention to these issues:</p> -<div class="note"> - <p><strong>First, note that you shouldn't use the x86 emulator — it is hard to install and not well supported.</strong></p> -</div> -<p>Next, the build-system for the emulator builds both 32bit and 64bit versions of the emulator. As the emulator depends on OpenGL, this means that you need to have both 32bit and 64bit versions of OpenGL libraries installed on your system. See the discussion in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=897727" title="https://bugzilla.mozilla.org/show_bug.cgi?id=897727">bug 897727</a>.</p> -<p>There are two ways that you can solve this problem:</p> -<h4 id="Solution_1_have_both_32bit_and_64bit_OpenGL_libs_installed_with_the_right_symlinks">Solution #1: have both 32bit and 64bit OpenGL libs installed, with the right symlinks</h4> -<p>If your linux distro has multilib packages for OpenGL libraries, you can attempt installing them. You might then have to manually create some symlinks.</p> -<p>For example, here is the situation on Ubuntu 12.04 LTS x86-64. On this distribution, the <code>libgl1-mesa-dev</code> package cannot be installed simultaneously in x86-64 and i386 versions, but you can have the following combination of packages simultaneously installed:</p> -<pre class="bz_comment_text" id="comment_text_12">sudo apt-get install libgl1-mesa-dev libglapi-mesa:i386 libgl1-mesa-glx:i386</pre> -<p>After having run this command, you will still have to manually create some symlinks for the emulator build to succeed:</p> -<pre class="note">sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so -sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so</pre> -<h4 id="Solution_2_just_patch_the_emulator_so_it_only_builds_64bit">Solution #2: just patch the emulator so it only builds 64bit</h4> -<p>Just apply <a href="https://bug897727.bugzilla.mozilla.org/attachment.cgi?id=786280" title="https://bug897727.bugzilla.mozilla.org/attachment.cgi?id=786280">this patch</a> to the sdk/ git repository under the B2G repo. This will cause the B2G emulator to only attempt to build the 64bit emulator if you're on a 64bit system, thus avoiding any multilib issues. The 32bit emulator is unused anyway on a 64bit system. This is the simplest solution, until this patch eventually bit-rots.</p> -<h3 id="64_bit_requirement_installation">64 bit requirement installation</h3> -<p>This section lists the commands you need to run in different Linux distributions to install all the requirements for building Firefox OS.</p> -<h4 id="Ubuntu_12.04_Linux_Mint_13_Debian_6">Ubuntu 12.04 / Linux Mint 13 / Debian 6</h4> -<p>Run the following command in Terminal:</p> -<pre>sudo apt-get update -sudo apt-get install autoconf2.13 bison bzip2 ccache curl flex gawk gcc g++ g++-multilib git ia32-libs lib32ncurses5-dev lib32z1-dev libgl1-mesa-dev libx11-dev make zip</pre> -<p>If you'll build for the <a href="https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame">"Flame"</a> reference device or Nexus 5, run the following command in Terminal:</p> -<pre>sudo apt-get install libxml2-utils </pre> -<p>And see the above comments about emulator build issues!</p> -<h4 id="Ubuntu_12.10">Ubuntu 12.10</h4> -<p>Run the following command in Terminal:</p> -<pre>sudo apt-get install autoconf2.13 bison bzip2 ccache curl flex gawk gcc g++ g++-multilib gcc-4.6 g++-4.6 g++-4.6-multilib git ia32-libs lib32ncurses5-dev lib32z1-dev libgl1-mesa-dev libx11-dev make zip</pre> -<p>In addition to the emulator build issues discussed above, the compiler will default to <code>gcc-4.7</code>, which will fail to build with an error along the following lines:</p> -<p>"<code>KeyedVector.h:193:31: error: indexOfKey was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation"</code></p> -<p>To fix this, you will need to specify GCC 4.6 as the default host compiler after having retrieved the B2G sources: Read <a href="/en-US/docs/Mozilla/Firefox_OS/Customization_with_the_.userconfig_file#Changing_the_default_host_compiler">Changing the default host compiler</a> to find out how to do it.</p> -<p class="note">In a fresh Ubuntu 12.10 install, you'll get an error about unmet dependencies for ia32-libs. The following commands fix it:</p> -<pre>sudo dpkg --add-architecture i386 -sudo apt-get update -sudo apt-get install ia32-libs</pre> -<h4 id="Ubuntu_13.04">Ubuntu 13.04</h4> -<p>Run the following command in Terminal:</p> -<pre>sudo apt-get install --no-install-recommends autoconf2.13 bison bzip2 ccache curl flex gawk gcc g++ g++-multilib gcc-4.6 g++-4.6 g++-4.6-multilib git ia32-libs lib32ncurses5-dev lib32z1-dev zlib1g:amd64 zlib1g-dev:amd64 zlib1g:i386 zlib1g-dev:i386 libgl1-mesa-dev libx11-dev make zip</pre> -<p>In addition to the emulator build issues discussed above, the compiler will default to <code>gcc-4.7</code>, which will fail to build with an error along the following lines:</p> -<p>"<code>KeyedVector.h:193:31: error: indexOfKey was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation"</code></p> -<p>To fix this, you will need to specify GCC 4.6 as the default host compiler after having retrieved the B2G sources: Read <a href="/en-US/docs/Mozilla/Firefox_OS/Customization_with_the_.userconfig_file#Changing_the_default_host_compiler">Changing the default host compiler</a> to find out how to do it.</p> -<h4 id="Ubuntu_13.10">Ubuntu 13.10</h4> -<p>With Ubuntu 13.10, multi-arch packages are now the main way to support multiple architectures (e.g. 32-bit on a 64-bit install). You must tell your Ubuntu system that you want to support 32-bit packages as well:<br> - </p> -<pre>sudo dpkg --add-architecture i386 -sudo apt-get update</pre> -<p>Once you've completed that, then you can install the necessary packages:</p> -<pre style="font-family: 'Open Sans', sans-serif; line-height: 21px;">sudo apt-get install --no-install-recommends autoconf2.13 bison bzip2 ccache curl flex gawk gcc g++ g++-multilib gcc-4.6 g++-4.6 g++-4.6-multilib git lib32ncurses5-dev lib32z1-dev zlib1g:amd64 zlib1g-dev:amd64 zlib1g:i386 zlib1g-dev:i386 libgl1-mesa-dev libx11-dev make zip libxml2-utils - -sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.6 1 - -sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 2 - -sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.6 1 - -sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.8 2 - -sudo update-alternatives --set gcc "/usr/bin/gcc-4.6" - -sudo update-alternatives --set g++ "/usr/bin/g++-4.6" </pre> -<h4 id="Fedora_17181920"><br> - Fedora 17/18/19/20</h4> -<p>Run the following command in Terminal:</p> -<pre class="note">sudo yum install autoconf213 bison bzip2 ccache curl flex gawk gcc-c++ git glibc-devel glibc-static libstdc++-static libX11-devel make mesa-libGL-devel ncurses-devel patch zlib-devel ncurses-devel.i686 readline-devel.i686 zlib-devel.i686 libX11-devel.i686 mesa-libGL-devel.i686 glibc-devel.i686 libstdc++.i686 libXrandr.i686 zip perl-Digest-SHA wget</pre> -<p>In addition to the above you will need GCC 4.6.x in order to compile the project:</p> -<ul> - <li><a href="http://people.mozilla.org/~gsvelto/gcc-4.6.4-fc18.tar.xz">Pre-compiled GCC 4.6.x for Fedora 17/18</a></li> - <li><a href="http://people.mozilla.org/~gsvelto/gcc-4.6.4-fc19.tar.xz">Pre-compiled GCC 4.6.x for Fedora 19/20</a></li> -</ul> -<p>Download the right version for your Fedora installation, then install it to <code>/opt,</code> with the following command on Fedora 17/18:</p> -<pre class="note">curl -O http://people.mozilla.org/~gsvelto/gcc-4.6.4-fc18.tar.xz -sudo tar -x -a -C /opt -f gcc-4.6.4-fc18.tar.xz -</pre> -<p>And with the following command for Fedora 19/20:</p> -<pre class="note">curl -O http://people.mozilla.org/~gsvelto/gcc-4.6.4-fc19.tar.xz -sudo tar -x -a -C /opt -f gcc-4.6.4-fc19.tar.xz -</pre> -<p>You will need to specify GCC 4.6.x as the default host compiler after having retrieved the B2G sources: Read <a href="/en-US/docs/Mozilla/Firefox_OS/Customization_with_the_.userconfig_file#Changing_the_default_host_compiler">Changing the default host compiler</a> to find out how to do it.</p> -<p>If build fails with the compiler complaining about not finding libmpc.so.2, install the package compat-libmpc</p> -<h4 id="Arch_Linux"><strong>Arch Linux</strong></h4> -<p>Run the following command in Terminal:</p> -<pre class="note">sudo <span style=""><span style="">pacman -S --needed </span></span><span style=""><span style="">alsa-lib </span></span><span style=""><span style="">autoconf2.13</span></span><span style=""><span style=""> bison</span></span><span style=""><span style=""> ccache</span></span><span style=""><span style=""> </span></span><span style=""><span style="">curl firefox </span></span><span style=""><span style="">flex </span></span><span style=""><span style="">gcc-multilib </span></span><span style=""><span style="">git </span></span><span style=""><span style="">gperf </span></span><span style=""><span style="">libnotify </span></span><span style=""><span style="">libxt </span></span><span style=""><span style="">libx11 mesa multilib-devel </span></span><span style=""><span style="">wget wireless_tools </span></span><span style=""><span style="">yasm</span></span><span style=""><span style=""> zip </span></span><span style=""><span style="">lib32-mesa </span></span>lib32-mesa-libgl <span style=""><span style="">lib32-ncurses lib32-readline</span></span><span style=""><span style=""> </span></span><span style=""><span style="">lib32-zlib</span></span></pre> -<p>To install the lib32-* packages you need to have the multilib repository enabled.</p> -<p>B2G <a href="https://developer.mozilla.org/en-US/Firefox_OS/Building#KeyedVector.h.3A193.3A31.3A_error.3A_indexOfKey_was_not_declared_in_this_scope">can only be compiled with gcc4.6.4</a>, and because Arch Linux always has bleeding edge software you will need to install <a href="https://aur.archlinux.org/packages/gcc46-multilib">gcc46-multilib from AUR</a>. Note that you will have to edit the PKGBUILD and add <code>staticlibs</code> to the <code>options</code> array, or gcc will be unable to compile B2G and give you a <code>cannot find -lgcc</code> error when compiling. You will also need to add the following to your <code>.userconfig</code> file:</p> -<pre class="language-html">export CC=gcc-4.6.4 -export CXX=g++-4.6.4</pre> -<p>By default, Arch Linux uses Python3. You'll have to force it to use the old python2. You can do that by linking the python2 executable to python but this is discouraged and considered error-prone. This will also break python 3 if it is installed on your system. A better way is to use <code>virtualenv</code>/<code>virtualenvwrapper</code>:</p> -<pre><span style=""><span style="">sudo pacman -S python-virtualenvwrapper -</span></span>source /usr/bin/virtualenvwrapper.sh -mkvirtualenv -p `which python2` firefoxos -workon firefoxos -</pre> -<p>Android will complain that you need make 3.81 or make 3.82 instead of 4.0. You can download <a href="https://aur.archlinux.org/packages/make-3.81/">make 3.81 from AUR</a>. This will install the make-3.81 binary on your path, you need to create a symlink named make to a location earlier in the PATH variable for the build to use the correct version.</p> -<pre>mkdir -p ~/bin -ln -s `which make-3.81` ~/bin/make -export PATH=~/bin:$PATH -</pre> -<p>Android also needs the Java6 SDK and Arch only has Java7. Unfortunately the aur build is broken, but you can still download the <a href="http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html#jdk-6u45-oth-JPR">Java 6 SDK</a> and install it manually. You will then need to put it in your path.</p> -<pre>cp ~/Downloads/jdk-6u45-linux-x64.bin /opt -su -cd /opt -chmod +x jdk-6u45-linux-x64.bin -./jdk-6u45-linux-x64.bin -exit -ln -s /opt/jdk1.6.0_45/bin/java ~/bin/java - -</pre> -<h4 id="Gentoo_Linux"><strong>Gentoo Linux</strong></h4> -<h5 id="Installing_ccache">Installing ccache</h5> -<p>You will need to install <strong><a href="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=3#doc_chap3">ccache</a></strong>, a tool for caching partial builds.</p> -<pre><span style=""><span style=""># emerge -av ccache</span></span> -</pre> -<p>Because ccache is known to frequently cause support issues, Gentoo encourages you to use it <em>explicitly</em> and <em>sparingly</em>.</p> -<p>To enable the required use of ccache, on <em>the subsequent step</em> of this guide where the <code>./build.sh</code> script is called, Gentoo users should instead run the command with an explicitly extended path, ie.</p> -<pre><span style=""><span style=""><strong>PATH=/usr/lib64/ccache/bin:$PATH</strong> ./build.sh</span></span> -</pre> -<h5 id="Generating_Partition_Images">Generating Partition Images</h5> -<p>If you are building B2G for actual physical hardware, then you may at some point also wish to generate some partition images for upload to your device. (For example, to restore backed up files to the device via the <strong><em>fastboot</em></strong> utility)</p> -<p>The filesystem image format used in this case is YAFFS2 (Yet Another Filesystem 2). Gentoo has support for the very latest (ie. git HEAD) <code>yaffs2-utils</code> userland package in portage. (Note: You will also need kernel patches if you want to mount YAFFS2 images, but this is not really required since you can deconstruct and rebuild them instead.)</p> -<pre># emerge --autounmask-write yaffs2-utils; etc-update; emerge -av yaffs2-utils</pre> -<p>In order to generate such an image, simply change to the parent directory of the partition filesystem tree you wish to package, and issue a command like this:</p> -<pre>mkyaffs2image system/ system.img</pre> -<h2 id="Wymagania_dla_systemu_Mac_OS_X">Wymagania dla systemu Mac OS X</h2> -<p>To build Firefox OS on Mac OS X, there are a number of prequisite steps you need to follow, which are detailed below. We also discuss common errors you might come across in particular situations, and solutions to those.</p> -<div class="note"> - <p><strong>Note: Configuring and Building B2G for Keon WON'T WORK on a Mac</strong>. You'll need to use Linux to build B2G for this device.</p> -</div> -<h3 id="Install_XCode_Command_Line_Utilities"><strong>Install XCode Command Line Utilities</strong></h3> -<p>You need to install Xcode's Command Line Utilities. You can download <em>just</em> the Command Line Utilities from <a href="https://developer.apple.com/downloads/" title="https://developer.apple.com/downloads/">Apple's developer downloads page</a> for your particular version of OS X, however if you would like the entire Xcode suite of applications, you can <a class="external" href="http://itunes.apple.com/us/app/xcode/id497799835?mt=12" style="line-height: 1.572;" title="http://itunes.apple.com/us/app/xcode/id497799835?mt=12">install Xcode</a><span style="line-height: 1.572;"> through the Mac App Store. </span></p> -<p>Xcode 4.3.1 (OS X 10.7 "Lion") and other newer versions such as 4.4.1+ (that is, Mac OS X 10.8 "Mountain Lion"), won't necessarily include the required Command Line Utilities. When you install Xcode, make sure to go into Preferences, then the Downloads panel, and install the Command Line Utilities. In addition, make sure you have at least 20 GB of free disk space.</p> -<p><img alt="Screenshot of Xcode Downloads Command Line Tools" src="/files/4557/xcode_downloads_command_line_tools.png" style="width: 750px; height: 528px;"></p> -<div class="note"> - <strong>Note:</strong> The Firefox OS emulator requires a Core 2 Duo processor or later; that is, a system that is compatible with Mac OS X 10.7 "Lion". You do not actually have to be running Lion, you just have to be compatible with it. You can, however, build any Firefox OS build on many older Macs.</div> -<h3 id="Run_Firefox_OS_Mac_Bootstrap">Run Firefox OS Mac Bootstrap</h3> -<p>Next, open a terminal and run the following command:</p> -<pre class="brush: bash">curl -fsSL https://raw.github.com/mozilla-b2g/B2G/master/scripts/bootstrap-mac.sh | bash</pre> -<p>This will pull and run a bootstrap script that makes sure you have all the prerequisites met to build the emulator. It will also prompt you for permission to install anything you're missing, and provide warnings and suggested fixes to problems. The script will check for and install the following items:</p> -<ul> - <li><code>git</code></li> - <li><code>gpg</code></li> - <li><code>ccache</code></li> - <li><code>yasm</code></li> - <li><code>autoconf-213</code></li> - <li><code>gcc-4.6</code></li> - <li><code>homebrew</code></li> -</ul> -<h4 id="Xcode_wrangling">Xcode wrangling</h4> -<p>If you have already upgraded to Xcode 4.4+ and get the message that Xcode is outdated, check the Xcode path with:</p> -<pre>xcode-select -print-path</pre> -<p>If it still points to <code>/Developer</code> you can update the path with:</p> -<pre>sudo xcode-select -switch /Applications/Xcode.app</pre> -<h4 id="Making_the_Mac_OS_X_10.6_SDK_available">Making the Mac OS X 10.6 SDK available</h4> -<p>You also need to have the Mac OS X 10.6 SDK available. The SDK needs to be available at</p> -<pre>/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/</pre> -<p>If it cannot be found there you will need to extract and copy it from Xcode 4.3. To do this:</p> -<ol> - <li>Download the XCode 4.3 .dmg file from the <a class="external" href="https://developer.apple.com/downloads/index.action">Apple Developer</a> portal (you'll need an <a href="https://developer.apple.com/register/index.action" title="https://developer.apple.com/register/index.action">Apple Developer account</a>).</li> - <li>Download the utility <a href="http://www.charlessoft.com/" title="http://www.charlessoft.com/">Pacifist</a> and use it to extract the 10.6 SDK from the XCode 4.3 .dmg file. Click on the "Extract Package" button, find the SDK by searching for 10.6 in the search box, then <em>Ctrl + click</em> on the MacOSX10.6.sdk directory and Extract it to a suitable location.</li> - <li>Add a symlink from the 10.6 SDK location to the <code>/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/</code> directory. For example, if you put the 10.6 SDK on your desktop, the comment would be</li> -</ol> -<pre>ln -s /Users/<em><yourusername></em>/Desktop/MacOSX10.6.sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/</pre> -<h3 id="Be_aware_of_Mac_file_system_case_sensitivity">Be aware of Mac file system case sensitivity</h3> -<p>By default, Mac OS X ships with a case-insensitive file system. This is problematic because the Linux kernel has a number of files with the same name, but different case. For example, see the header files <code>xt_CONNMARK.h</code> and <code>xt_connmark.h</code>. This results in a number of files appearing to be modified in <code>/kernel</code> after a fresh <code>./config.sh</code>.</p> -<p>In many cases you can run the build just fine; for some platforms, however, you may encounter the following error:</p> -<pre><span class="quote">ERROR: You have uncommited changes in kernel -You may force overwriting these changes -with |source build/envsetup.sh force| - -ERROR: Patching of kernel/ failed.</span></pre> -<p><span class="quote">Please see <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=867259" title="https://bugzilla.mozilla.org/show_bug.cgi?id=867259">bug 867259</a></span> for more discussion and possible fixes for this problem.</p> -<p>Alternatively, it will always be safest to build on a case sensitive file system. The easiest way to do this is to create a separate, mountable disk image with case-sensitivity enabled. You can do this using Apple's Disk Utility application or from the command line:</p> -<pre>hdiutil create -volname 'firefoxos' -type SPARSE -fs 'Case-sensitive Journaled HFS+' -size 40g ~/firefoxos.sparseimage</pre> -<p>Mount the drive with:</p> -<pre>open ~/firefoxos.sparseimage</pre> -<p>Change into the mounted drive with:</p> -<pre>cd /Volumes/firefoxos/</pre> -<p>You can then check out the code and compile from this location without worrying about case-sensitivity problems.</p> -<h3 id="Mountain_Lion_homebrew_gotcha">Mountain Lion homebrew gotcha</h3> -<div> - <div> - If you are on Mountain Lion and you receive an error during the installation of the dependencies via homebrew, such as:</div> -</div> -<div> - <pre>clang: error: unable to execute command: Segmentation fault: 11</pre> - ... try reinstalling the dependency manually adding the <code>--use-gcc</code> flag, for example: - <pre>brew install mpfr --use-gcc</pre> -</div> -<h3 id="Follow_Samsung_Galaxy_S2_extra_steps">Follow Samsung Galaxy S2 extra steps</h3> -<p>If you plan to build for the Samsung Galaxy S2, you will also need to install heimdall. See {{ anch("Installing heimdall") }} for details. This is <strong>not</strong> done for you by the bootstrap script!</p> -<div class="note"> - <strong>Note:</strong> If you have installed the <a class="external" href="http://www.samsung.com/us/kies/" title="http://www.samsung.com/us/kies/">Samsung Kies</a> tool, which is used to manage the contents of many Samsung phones, you will have to remove it before you can flash Firefox OS onto your device. You can use the standard application removal process on Windows; on Mac, the Kies install disk image has a utility to fully remove Kies from your system. Flashing <strong>will not work</strong> if you have Kies installed. If you forget to remove Kies, the build system will detect it and remind you to uninstall it. Note also that the uninstall tool does not correctly remove the folder <code>~/Library/Application Support/.FUS</code>, and leaves a reference to a utility there in your user startup items list. You will want to remove these manually.</div> -<h3 class="note" id="Fix_libmpc_dependency_if_broken">Fix libmpc dependency if broken</h3> -<p><code>gcc 4.6</code> was built with <code>libmpc 0.9</code>; if you then use homebrew to update packages, libmpc gets updated to version 1.0, but homebrew doesn't rebuild <code>gcc 4.6</code> after the library version changes. So you need to create a symlink to make things work again, like this:</p> -<pre>cd /usr/local/lib/ -ln -s libmpc.3.dylib libmpc.2.dylib</pre> -<h3 id="Optional_Install_HAX">Optional: Install HAX</h3> -<p>Intel provides a special driver that lets the B2G emulator run its code natively on your Mac instead of being emulated, when you're using the x86 emulator. If you wish to use this, you can <a class="external" href="http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager/" title="http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager/">download and install</a> it. It's not required, but it can improve emulation performance and stability. </p> -<p>Before you install HAX you will need to install the <a href="http://developer.android.com/sdk/index.html" title="http://developer.android.com/sdk/index.html">Android SDK</a>.</p> -<h2 class="note" id="Instalacja_adb">Instalacja adb</h2> -<p>The build process needs to pull binary blobs from the Android installation on the phone before building B2G (unless you're building the emulator, of course). For this, you will need <code>adb</code>, the Android Debug Bridge. Our <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">Installing ADB</a> article explains how to get <code>adb</code> installed.</p> -<div class="warning"> - <p>Note for future when you start to use adb: adb needs the phone's lock screen to be unlocked in order to see your phone (at least in later versions of Firefox OS). You'll probably want to disable the lock screen (we'll get to how later in the build instructions).</p> -</div> -<h2 class="note" id="Instalacja_heimdall">Instalacja heimdall</h2> -<p>Heimdall is a utility for flashing the Samsung Galaxy S2. It's used by the Boot to Gecko flash utility to replace the contents of the phone with Firefox OS, as well as to flash updated versions of B2G and Gaia onto the device. You'll need it if you want to install Firefox OS on a Galaxy S2; it is <strong>not</strong> needed for any other device. For other devices, we build and use the fastboot utility instead.</p> -<div class="note"> - <strong>Note:</strong> Again, it's important to note that this is <strong>only required for installing Firefox OS on the Samsung Galaxy S2</strong>.</div> -<p>There are two ways to install heimdall:</p> -<ul> - <li>You can <a class="link-https" href="https://github.com/Benjamin-Dobell/Heimdall" title="https://github.com/Benjamin-Dobell/Heimdall">download the code</a> GitHub and build it yourself.</li> - <li>Use a package manager to install it. - <ul> - <li>On Linux: <code>sudo apt-get install libusb-1.0-0 libusb-1.0-0-dev</code></li> - <li>On Mac, you can <a class="link-https" href="https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.2-mac.dmg" title="https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.2-mac.dmg">download an installer package</a> and use that.</li> - </ul> - </li> -</ul> -<h2 id="Konfiguracja_ccache">Konfiguracja ccache</h2> -<p>The B2G build process uses ccache. The default cache size for ccache is 1GB, but the B2G build easily saturates this; around 3GB is recommended. You can configure your cache by running the following command inside terminal:</p> -<pre><code>$ ccache --max-size 3GB</code></pre> -<h2 id="Dla_systemu_Linux_konfigurowanie_reguł_udev_dla_telefonu">Dla systemu Linux: konfigurowanie reguł udev dla telefonu</h2> -<div class="note"> - <p><strong>Note</strong>: This section is specific to Linux; Mac OS X has the necessary device permissions set up already.</p> -</div> -<p>Next, you need to confingure the udev rule for your phone,</p> -<p>You can get the <a href="https://developer.android.com/tools/device.html#VendorIds">USB vendor ID</a> by running <code>lsusb</code> with your phone plugged in, but typically it's Google <code>18d1,</code> Samsung <code>04e8</code>, ZTE <code>19d2</code>, Geeksphone/Qualcomm <code>05c6</code>. Add this line in your <code>/etc/udev/rules.d/android.rules</code> file (replacing <code>XXXX</code> with the ID for your device):</p> -<pre>SUBSYSTEM=="usb", ATTR{idVendor}=="XXXX", MODE="0666", GROUP="plugdev"</pre> -<p>Take ZTE for example, the content in android.rules will be</p> -<pre style="font-size: 14px;">SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev"</pre> -<div class="note"> - <p><span style="line-height: 1.572;">If the file doesn't exist, create it. The <code>rules.d</code> directory is usually read only by default, so you may have to use <code>chmod</code> to make the directory writeable, or the file, or both.</span></p> -</div> -<p><span style="line-height: 1.572;">Once you've saved the file, and closed it, make the file readable:</span></p> -<pre>sudo chmod a+r /etc/udev/rules.d/android.rules -</pre> -<p>Now that the udev rules have been updated, restart the udev daemon. For ubuntu:</p> -<pre>sudo service udev restart</pre> -<p>Finally, unplug and the USB cable but don't replug it in because we need to enable remote debugging on the phone first.</p> -<h2 id="Enable_remote_debugging">Enable remote debugging</h2> -<p>Before you plug your phone back into your USB port, put it USB developer mode. This allows you to debug and flash the phone. To enable developer mode, on your phone enable <a href="/en-US/Firefox_OS/Debugging/Developer_settings#Remote_debugging">Remote Debugging</a> in <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a> (this was called Developer mode on older versions.) Once the option is checked, remote debugging is enabled, and you are ready to go.</p> -<p>At this point, connect your phone to your computer via a USB cable (if you created the udev rule before, this will trigger udev to detect the phone and create the device node with the right permissions). Now you can check if you can list your device via the <code>adb devices</code> command (remember that adb can only see your phone when the lock screen is unlocked). If everything has worked ok, you should see an output similar to this (the following is for a Geeksphone Keon):</p> -<pre style="font-size: 14px;">$ adb devices -List of devices attached -full_keon device</pre> -<p>If the device did not list as expect, check the file name and the script are all correct (see previous section), then restart the computer and retype the command again. Note also that if your device uses fastboot, the bootloader may identify itself with a different vendor ID than the one you see when the device boots normally.</p> -<h2 id="Backup_the_phone_system_partition">Backup the phone system partition</h2> -<div class="note"> - <p><strong>Note</strong>: You have to do this before you build your device if you do not have an existing system backup, because some libraries will be referenced in build time. These library might be proprietary so we can't provide in our code base.</p> -</div> -<p>It is recommended that you back up the entire Android system partition on your phone.</p> -<p>You can use this copy of the binary blobs for Android in case you later delete your B2G tree. To do this, run:</p> -<pre>adb pull /system <backup target dir>/system -</pre> -<p> Depending on the phone, you may also need to pull the <code>/data</code> and/or <code>/vendor</code> directories:</p> -<pre>adb pull /data <backup target dir>/data -adb pull /vendor <backup target dir>/vendor -</pre> -<p>If the pull commands fail with an "insufficient permission" message, try the following:</p> -<ul> - <li>stop and restart the adb server, or if that fails,</li> - <li>double-check that you have granted root permissions to the <code>adb</code> tool within your custom ROM (e.g. under CyanogenMod, change <em>Settings > System > Developer Options > Root Access</em> to <em>Apps and ADB</em> or <em>ADB only</em>).</li> - <li>Verify that you have set up the udev rule correctly (see {{ anch("For Linux: configure the udev rule for your phone") }}.</li> -</ul> -<h2 id="On_to_the_next_step">On to the next step</h2> -<p>At this point, you should be ready to <a href="/en-US/docs/Mozilla/Firefox_OS/Preparing_for_your_first_B2G_build" title="en-US/docs/Mozilla/Firefox_OS/Preparing_for_your_first_B2G_build">fetch the Firefox OS code</a>!</p> diff --git a/files/pl/archive/b2g_os/index.html b/files/pl/archive/b2g_os/index.html deleted file mode 100644 index 7ed185db02..0000000000 --- a/files/pl/archive/b2g_os/index.html +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: B2G OS -slug: Archive/B2G_OS -tags: - - B2G - - Firefox OS - - Gaia - - Początek FirefoxOS - - Początkujący - - Przegląd - - Łatwe -translation_of: Archive/B2G_OS ---- -<p>Firefox OS jest obecnie w trakcie intensywnego rozwoju; Stale pracujemy nad ułatwieniami w używaniu i bezpieczeństwie Gaia, i tworzeniu aplikacji. Jakkolwiek, potrzebujesz wiedzy o systemach na jakich jest zbudowany stos Firefox OS lub telefon z Firefox OS. Linki poniżej są przeznaczone dla programistów sieciowych zainteresowanych uruchamianiem i tworzeniem zmian do Gaia lub tworzeniem i rozwijaniem aplikacji na urządzenia z systemem Firefox OS.</p> - -<table class="topicpage-table"> - <tbody> - <tr> - <td> - <h2 class="Documentation" id="Documentation" name="Documentation">Dokumentacja Firefox OS</h2> - - <dl> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Introduction" title="en-US/docs/Mozilla/Boot_to_Gecko/Introduction">Wprowadzenie do Firefox OS</a></dt> - <dd>Informacje wprowadzające czym jest Firefox OS i jak on działa.</dd> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Writing_apps_for_Boot_to_Gecko" title="en-US/docs/Mozilla/Boot_to_Gecko/Writing apps for Boot to Gecko">Pisanie aplikacji dla Firefox OS</a></dt> - <dd>Tutorial opisujący jak tworzyć aplikacje działające na urządzeniach z Firefox OS.</dd> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Building_and_installing_Boot_to_Gecko" title="en-US/docs/Mozilla/Boot_to_Gecko/Building and installing Boot to Gecko">Kompilacja i instalacja Firefox OS</a></dt> - <dd>Przewodnik jak skompilować Firefox OS i zainstalować go na swoim urządzeniu. Ten przewodnik obejmuje również kompilację emulatora Firefox OS dla uruchamiania Firefox OS na komputerze.</dd> - <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Gaia" title="/en-US/docs/Mozilla/Gaia">Gaia</a></dt> - <dd>Dokumentacja Gaia, aplikacji interfejsu użytkownika dla urządzeń z Firefox OS. Jest to internetowa aplikacja uruchamiana na szczycie stosu oprogramowania Firefox OS.</dd> - <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Gonk" title="/en-US/docs/Mozilla/Firefox_OS/Gonk">Gonk</a></dt> - <dd>Dokumentacja Gonk, warstwy systemu operacyjnego poniżej Gaia. Składa się on z jądra Linuxa i warstwy abstakcyjnej sprzętu, z którym łączy się Gecko.</dd> - <dt><a href="/en-US/docs/Gecko" title="/en-US/docs/Gecko">Gecko</a></dt> - <dd>Gecko jest warstwą Firefox OS która zapewnia taką samą implementację otwartych standardów internetowych, jakiej używają Firefox i Thunderbird, a także wiele innych aplikacji.</dd> - <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Security" title="/en-US/docs/Mozilla/Firefox_OS/Security">Bezpieczeństwo</a></dt> - <dd>Dokumentacja zabezpieczeń w Firefox OS. Ten zawierający tematy o bezpieczeństwie urządzeń z każdej perspektywy: dla programistów aplikacji, integratorów urządzeń, itd. </dd> - <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Performance" title="/en-US/docs/Mozilla/Firefox_OS/Performance">Wydajność</a></dt> - <dd>Artykuły o optymalizacji aplikacji dla Firefox OS.</dd> - <dt><a href="/en-US/docs/Mozilla/Firefox_OS/Architecture" title="/en-US/docs/Mozilla/Firefox_OS/Architecture">Przegląd architektury Firefox OS</a></dt> - <dd>Przegląd jak zbudowany jest Firefox OS.</dd> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Troubleshooting" title="/en-US/docs/Mozilla/Boot_to_Gecko/Troubleshooting">Rozwiązywanie problemów</a></dt> - <dd>Przewodnik wspólnego rozwiązywania problemów z Firefox OS.</dd> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Testing_Boot_to_Gecko" title="en-US/docs/Mozilla/Boot_to_Gecko/Testing Boot to Gecko">Testowanie Firefox OS</a></dt> - <dd>Przewodnik testowania Firefox OS, zawierający informacje o tworzeniu testów automatycznych.</dd> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Debugging_on_Boot_to_Gecko" title="en-US/docs/Mozilla/Boot_to_Gecko/Debugging on Boot to Gecko">Debugowanie w Firefox OS</a></dt> - <dd>Przewodnik debugowania twoich aplikacji mobilnych i samego Firefox OS.</dd> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Boot_to_Gecko_developer_phone_guide" title="/en-US/docs/Mozilla/Boot_to_Gecko/Boot to Gecko developer phone guide">Przewodnik telefonu dla programisty </a><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Boot_to_Gecko_developer_phone_guide" title="/en-US/docs/Mozilla/Boot_to_Gecko/Boot to Gecko developer phone guide">Firefox OS</a></dt> - <dd>Przewodnik po telefonie programisty Firefox OS, który Mozilla zapewnia niektórym programistom. Ten przewodnikma zastosowanie również wtedy, gdy ktoś zainstalował Firefox OS na twoim telefonie za ciebie.</dd> - <dt><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Porting" title="/en-US/docs/Mozilla/Boot_to_Gecko/Porting">Przenoszenie Firefox OS</a></dt> - <dd>Informacja o tym jak przenieść Firefox OS na nowe urządzenie.</dd> - </dl> - - <p><span class="alllinks"><a href="/en-US/docs/tag/B2G" title="/en-US/docs/tag/B2G">Zobacz wszystko...</a></span></p> - </td> - <td> - <h2 class="Community" id="Community" name="Community">Jak dostać pomoc od społeczności</h2> - - <p>Jeśli pracujesz z Firefox OS lub tworzysz aplikacje, które chcesz uruchomić na urządzeniach z Firefox OS, tutaj są wspólne zasoby, aby ci pomóc!</p> - - <ul> - <li>Zadawaj swoje pytania na kanale IRC Mozilli do spraw Gecko: <a class="link-irc" href="irc://irc.mozilla.org/b2g" title="irc://irc.mozilla.org/b2g">#b2g</a></li> - </ul> - - <p><span class="alllinks"><a class="external" href="http://www.catb.org/~esr/faqs/smart-questions.html" title="http://www.catb.org/~esr/faqs/smart-questions.html">Nie zapominaj o netykiecie...</a></span></p> - - - <h2 class="Related_Topics" id="Related_Topics" name="Related_Topics">Powiązane tematy</h2> - - <ul> - <li><a href="/en-US/docs/Mobile" title="en-US/docs/Mobile">Mobilność</a></li> - <li><a href="/en-US/docs/HTML" title="en-US/docs/HTML">HTML</a></li> - <li><a href="/en-US/docs/CSS" title="en-US/docs/CSS">CSS</a></li> - <li><a href="/en-US/docs/JavaScript" title="en-US/docs/JavaScript">JavaScript</a></li> - </ul> - - <h2 class="Tools" id="Zasoby">Zasoby</h2> - - <ul> - <li><a class="link-https" href="https://wiki.mozilla.org/B2G/FAQ" title="B2G/FAQ">Mozilla wiki FAQ</a></li> - <li><a class="link-https" href="https://wiki.mozilla.org/B2G/Schedule_Roadmap" title="https://wiki.mozilla.org/B2G/Schedule_Roadmap">Mapa drogowa</a></li> - <li><a href="/en-US/docs/Mozilla/Boot_to_Gecko/Feature_support_chart" title="/en-US/docs/Mozilla/Boot_to_Gecko/Feature_support_chart">Tabela opcji pomocy</a></li> - </ul> - </td> - </tr> - </tbody> -</table> diff --git a/files/pl/archive/b2g_os/instalacja_firefox_os/index.html b/files/pl/archive/b2g_os/instalacja_firefox_os/index.html deleted file mode 100644 index 792927987e..0000000000 --- a/files/pl/archive/b2g_os/instalacja_firefox_os/index.html +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Instalacja Firefox OS -slug: Archive/B2G_OS/Instalacja_Firefox_OS -tags: - - Android - - Firefox - - Firefox OS - - FirefoxOS - - Gaia - - OS - - dual boot - - instalacja - - konfiguracja - - sgs2 - - system -translation_of: Archive/B2G_OS/Building_and_installing_B2G_OS ---- -<p>Ponieważ Firefox OS jest aktualnie w fazie ciągłego rozwoju (przedpremierowa wersja) najlepszą drogą do upewnienia się, że posiadamy jego aktualną wersję jest instalcja ręczna. Poniższe artykuły pomogą Ci przejść przez proces przygotowania i instalacji Firefox OS na emulatorze, kompatybilnym urządzeniu lub w interfejsie użytkownika <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Introduction_to_Gaia" title="en-US/docs/Mozilla/Boot_to_Gecko/Introduction_to_Gaia">Gaia</a> przeglądarki Firefox.</p> -<table class="topicpage-table"> - <tbody> - <tr> - <td> - <h2 class="Documentation" id="Pobieranie_i_konfiguracja_Firefox_OS">Pobieranie i konfiguracja Firefox OS</h2> - <dl> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/B2G_build_prerequisites" title="en-US/docs/Mozilla/Boot_to_Gecko/B2G build prerequisites">Wymagania Firefox OS</a></dt> - <dd> - Co potrzebujesz(oraz co musisz zrobić) zanim skonfigurujesz Firefox OS po raz pierwszy.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Preparing_for_your_first_B2G_build" title="/en-US/docs/Mozilla/Boot_to_Gecko/Preparing for your first B2G build">Przygotowanie do konfiguracji Firefox OS</a></dt> - <dd> - <span id="result_box" lang="pl"><span class="hps">Zanim będzie można</span> konfigurować <span class="hps">Firefox</span> <span class="hps">OS</span><span>, trzeba</span> <span class="hps">sklonować repozytorium</span><span class="hps">.</span> <span class="hps">W tym artykule opisano</span><span>, jak to zrobić</span><span>.</span></span></dd> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Building_Boot_to_Gecko" title="en-US/docs/Mozilla/Boot_to_Gecko/Building Boot to Gecko">Konfiguracja Firefox OS</a></dt> - <dd> - Jak skonfigurować Firefox OS.</dd> - </dl> - <p><span class="alllinks"><a href="/en-US/docs/tag/B2G" title="/en-US/docs/tag/B2G">Więcej...</a></span></p> - </td> - <td> - <h2 class="Community" id="Instalacja_Firefox_OS_ilub_Gaia">Instalacja Firefox OS i/lub Gaia</h2> - <dl> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Choosing_how_to_run_Gaia_or_B2G" title="en-US/docs/Mozilla/Boot_to_Gecko/Choosing how to run Gaia or B2G">Sposób uruchamiania interfejsu Gaia lub Firefox OS</a></dt> - <dd> - Możesz używać interfejsu Gaia w Firefoxie lub uruchamiać Firefox OS na urządzeniu mobilnym lub w symulatorze okienkowym na komputerze. Ten przewodnik pomoże wybrać odpowiednie rozwiązanie dla Ciebie.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Using_Gaia_in_Firefox" title="en-US/docs/Mozilla/Boot_to_Gecko/Using Gaia in Firefox">Używanie intefejsu Gaia w Firefoxie</a></dt> - <dd> - Jak używać interfejsu Gaia w przeglądarce Firefox na komputerze.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Using_the_B2G_desktop_client" title="en-US/docs/Mozilla/Boot_to_Gecko/Using_the_B2G_desktop_client">Używanie klienta okienkowego Firefox OS</a></dt> - <dd> - Artykuł poświęcony używaniu klienta okienkowego Firefox Os; Symuluje interfejs Gaia w oknie aplikacji. Jest to lepsze rozwiązanie od pracy w oknie przeglądarki, ale gorsze od używania emulatorów.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Using_the_B2G_emulators" title="en-US/docs/Mozilla/Boot_to_Gecko/Using the B2G emulators">Używanie emulatorów Firefox OS</a></dt> - <dd> - Artykuł dotyczący wyboru wersji emulatora Firefox Os, jego konfiguracji i instalacji.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Installing_Boot_to_Gecko_on_a_mobile_device" title="en-US/docs/Mozilla/Boot_to_Gecko/Installing Boot to Gecko on a mobile device">Instalacja Firefox OS na urządzeniu mobilnym</a></dt> - <dd> - Jak zainstalować system Firefox OS na urządzeniu mobilnym.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Boot_to_Gecko/Dual_boot_of_B2G_and_Android_on_SGS2" title="/en-US/docs/Mozilla/Boot_to_Gecko/Dual boot of B2G and Android on SGS2">Dual boot Firefox OS oraz Androida na SGS2</a></dt> - <dd> - Jak przygotować Firefox OS/ Androida do dual boot'a na Samsungu Galaxy S2</dd> - </dl> - </td> - </tr> - </tbody> -</table> -<p> </p> diff --git a/files/pl/archive/b2g_os/instalacja_firefox_os/streszczenie_procesu_budowania_firefox_os/index.html b/files/pl/archive/b2g_os/instalacja_firefox_os/streszczenie_procesu_budowania_firefox_os/index.html deleted file mode 100644 index 3666a7ded4..0000000000 --- a/files/pl/archive/b2g_os/instalacja_firefox_os/streszczenie_procesu_budowania_firefox_os/index.html +++ /dev/null @@ -1,149 +0,0 @@ ---- -title: Streszczenie procesu kompilowania Firefox OS -slug: Archive/B2G_OS/Instalacja_Firefox_OS/Streszczenie_procesu_budowania_Firefox_OS -tags: - - Firefox OS - - Kompilowanie - - instalacja - - install -translation_of: Archive/B2G_OS/Building_and_installing_B2G_OS/B2G_OS_build_process_summary ---- -<div class="summary"> -<p>Kompilowanie i instalowanie systemu Firefox OS wymaga dużo wolnego czasu, szybkiego łącza internetowego i wysokiej mocy obliczeniowej komputera. Niestety podczas tak długiego procesu coś może pójść nie tak. Na tej stronie znajdują się informacje, które pomogą przebyć tę długą drogę.</p> -</div> - -<div class="note"> -<p><strong style="font-weight: bold;">Notatka:</strong> Podczas czytania artykułów dotyczących kompilowania Firefox OS natkniesz się na określenia "B2G", lub "Boot2Gecko". "Boot2Gecko" jest oficjalną nazwą kodową systemu Firefox OS.</p> -</div> - -<h2 id="Główny_cel_uzyskanie_czterech_plików_.img">Główny cel: uzyskanie czterech plików .img</h2> - -<p> </p> - -<table style="margin: 4px auto; vertical-align: top; width: 90%;"> - <tbody> - <tr> - <td><strong>boot.img</strong></td> - <td>Zawiera rdzeń Linuxa, system plików i podstawowe narzędzia Unixowe.</td> - </tr> - <tr> - <td><strong>system.img</strong></td> - <td>Znajduje się tam główny rdzeń systemu Firefox OS, czyli Gonk, Gecko i plik wykonywalny b2g.</td> - </tr> - <tr> - <td><strong>userdata.img</strong></td> - <td>Tutaj zawarty jest profil Gecko i aplikacje Gaia.</td> - </tr> - <tr> - <td><strong>recovery.img</strong></td> - <td>Tak samo jak boot.img, zawiera rdzeń Linuxa i system plików, ale odpowiada za udostępnienie użytkownikowi narzędzi do naprawy uszkodzonego urządzenia.</td> - </tr> - </tbody> -</table> - -<p>Kiedy te cztery obrazy zostaną stworzone, mogą zostać przesłane do urządzenia.</p> - -<p>Firefox OS jest tworzony na podstawie Android Open Source Project (AOSP). Narzędzia AOSP takie jak<code> adb</code> lub <code>fastboot </code>pozwalają na zaawansowane zarządzanie urządzeniem. Przykładem może być komenda <code>adb reboot-bootloader</code>, która sprawia, że urządzenie zrestartuje się i zatrzyma rozruch systemu na wczesnym etapie, co umożliwi przesłanie obrazu systemu poprzez wpisanie komendy <code>fastboot flash $partition $image</code>.</p> - -<h3 id="Pierwszy_obraz_boot.img">Pierwszy obraz: boot.img</h3> - -<p>Zawiera rdzeń Linuxa, odpowiadający za uruchamianie podstawowych programów i wykonywanie skryptów. Zostanie przesłany na partycję "boot" i dostęp do niego będzie możliwy poprzez użycie komendy <code>adb shell</code>. Ponieważ jest najważniejszą częścią systemu, aby go modyfikować, potrzeba uprawnień <strong>root</strong>.</p> - -<p>Możliwe jest również modyfikowanie istniejącego już obrazu boot.img, poprzez przeglądanie, kopiowanie, ponowne kompilowanie jego elementów. Takie operacje zostały opisane na tej stronie: <a href="http://k.japko.eu/alcatel-otf-hackers-guide-1.html">Alcatel One Touch Fire Hacking (Mini) Guide</a>.</p> - -<p>Obrazy <code>boot.img</code> mogą zostać przetestowane przed przesłaniem ich. Gdy urządzenie będzie w trybie bootloadera, wystarczy użyć narzędzia <code>fastboot</code> do uruchomienia obrazu boot.img. Nie trzeba wtedy instalować obrazu na urządzeniu, tak, jak miałoby to miejsce w przypadku komendy <code>fastboot boot /ścieżka/do/boot.img</code>.</p> - -<h3 id="Drugi_obraz_system.img">Drugi obraz: system.img</h3> - -<p>Obraz systemu (<code>system.img</code>) zawiera główne elementy systemu Firefox OS:</p> - -<ul> - <li><strong>Gonk</strong>: nisko-poziomowy dostęp systemu do komponentów urządzenia.</li> - <li><strong>Gecko</strong>: silnik przeglądarki Firefox, przystosowany do obsługi urządzeń mobilnych.</li> - <li><strong>B2G</strong>: główny proces systemowy.</li> -</ul> - -<div class="note"> -<p>Więcej informacji o budowie systemu znajdziesz na stronie <a href="https://developer.mozilla.org/en-US/Firefox_OS/Platform">Firefox OS platform</a>.</p> -</div> - -<p>Obraz systemu zostanie przesłany na główną partycję urządzenia (utworzoną przez obraz <code>boot.img</code>), a wszystkie pliki systemowe będą znajdowały się w folderze <code>/system/</code>.</p> - -<div class="note"> -<p><strong>Notatka</strong>: Obraz systemu zawiera również plamy binarne (binary blobs), które mogą zostać wykorzystane przez urządzenie do kontrolowania radia komórkowego.</p> -</div> - -<h3 id="Trzeci_obraz_userdata.img">Trzeci obraz: userdata.img</h3> - -<p>Obraz z danymi użytkownika zawiera aplikacje Gaia, które są wykorzystywane podczas pracy systemu.</p> - -<p>Obraz <code>userdata.img</code> zostanie umieszczony na partycji <code>userdata</code>, a jego zawartość będzie widoczna w folderze <code>/data/</code> wtedy, gdy system plików urządzenia będzie z niego korzystał. Trzeba również wspomnieć, że folder <code>/data/b2g/</code> zawiera profil platformy Gecko, a zawartością folderu <code>/data/local/webapps/</code> są wszystkie aplikacje, które znajdują się w pamięci urządzenia.</p> - -<h3 id="Czwarty_obraz_recovery.img">Czwarty obraz: recovery.img</h3> - -<p>Obraz przywracania systemu zawiera taki sam rdzeń, jaki ma obraz <code>boot.img</code>. Różnicą jest sposób wykonywania skryptu, co pozwala użytkownikowi na aktywowanie skryptu przywracającego system poprzez użycie fizycznych przycisków na urządzeniu.</p> - -<p>Obraz <code>recovery.img</code> zostanie umieszczony na partycji <code>recovery </code>i nie może on zostać zmodyfikowany podczas działania systemu.</p> - -<h2 id="Proces_kompilacji">Proces kompilacji</h2> - -<p>Cały proces kompilacji systemu Firefox OS składa się z następujących etapów:</p> - -<table style="margin: 4px auto; vertical-align: top; width: 90%;"> - <tbody> - <tr> - <td><strong>Przygotowania</strong></td> - <td>Uzyskanie wszystkich programów potrzebnych do przeprowadzenia procesu kompilacji. Do tych programów zaliczają się kompilatory, biblioteki itp.</td> - </tr> - <tr> - <td><strong>Konfiguracji</strong></td> - <td>Pobranie kodu źródłowego i utworzenie pliku <code>.configure</code>, w którym zawarte będą zmiennie, ścieżki i inne wartości, które zostaną wykorzystane w procesie kompilacji.</td> - </tr> - <tr> - <td><strong>Tworzenia</strong></td> - <td>Tworzenie profili platformy Gecko i aplikacji Gaia dla urządzenia.</td> - </tr> - <tr> - <td><strong>Instalowania</strong></td> - <td>Zainstalowanie na urządzeniu wcześniej przygotowanych plików.</td> - </tr> - </tbody> -</table> - -<p> </p> - -<h3 id="Przygotowanie">Przygotowanie</h3> - -<p>Należy przeprowadzić konfigurację wstępną, aby upewnić się, że komputer ma wszystkie narzędzia, potrzebne do skompilowania systemu. Do takich narzędzi zalicza się m.in. kompilator.</p> - -<p>Ten krok można wykonać przy użyciu skryptu. Szczegóły zostały omówione na <a href="https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites" title="Firefox OS build prerequisites">tej stronie</a>.</p> - -<div class="note"> -<p><strong>Notatka</strong>: Na Unixowych systemach można sprawdzić obecność wymaganego oprogramowania, poprzez komendę <code>which</code>. Parametrem komendy <code>which</code> jest sprawdzany program.</p> -</div> - -<h3 id="Konfiguracja">Konfiguracja</h3> - -<p>Aktualny krok zaczyna się wraz z uzyskaniem plików systemu Firefox OS. W uzyskaniu tych plików może pomóc narzędzie <code>git</code>. Konfiguracja obejmie cały kod źródłowy i utworzy plik<code> .config</code>, w którym znajdą się zmienne dla kompilowanego systemu.</p> - -<p>Konfiguracja rozpocznie się po uruchomieniu skryptu <code>config.sh</code>. Szczegóły zostały omówione na stronie <a href="/en-US/Firefox_OS/Preparing_for_your_first_B2G_build" title="Preparing for your first B2G build">Preparing for your first B2G build</a>.</p> - -<p>Skrypt konfiguracyjny potrzebuje parametrów urządzenia, na którym ma zostać zainstalowany system Firefox OS. Nazwa tworzonego systemu jest nazwą kodową powiązaną z architekturą CPU, a nie z konkretnym urządzeniem. Lista nazw kodowych znajduje się <a href="/en-US/Firefox_OS/Phones">tutaj</a>.</p> - -<p>Podczas konfiguracji używane jest również narzędzie Android Open Source Project <code>repo</code>. Pozwala ono na pobranie lub zaktualizowanie kodu używanego podczas procesu kompilacji.</p> - -<h3 id="Kompilacja">Kompilacja</h3> - -<p>W tym kroku zaczyna się kompilacja kodu źródłowego i uzyskanie czterech obrazów.</p> - -<p>Kompilacja uruchomi się po aktywowaniu skryptu <code>build.sh</code>. Szczegóły zostały omówione na stronie <a href="/en-US/Firefox_OS/Building" title="Building">Building Firefox OS</a>.</p> - -<p>Możliwe jest skompilowanie tylko części systemu Firefox OS. Można to zrobić poprzez dodanie do skryptu kompilującego jednego parametru. Na przykład, jeżeli chcemy uzyskać tylko element gaia, to dodajemy parametr <code>gaia</code>.</p> - -<p>Możliwe jest również skompilowanie obrazów omówionych na początku tej strony. Jeżeli chcemy skompilować obraz <code>system.img</code>, możemy to zrobić komendą <code>./build.sh out/platform/$target/system.img </code>(parametr <code>$target</code> jest taki sam, jak w procesie konfiguracji).</p> - -<h3 id="Instalacja">Instalacja</h3> - -<p>Należy uruchomić skrypt <code>flash.sh</code>, aby nowo skompilowany kod trafił do pamięci urządzenia.</p> - -<p>Możliwe jest zainstalowanie tylko poszczególnych części systemu. Żeby to zrobić, trzeba dodać parametr do skryptu <code>flash.sh</code>. Na przykład, żeby zainstalować tylko aplikacje Gaia, wystarczy wpisać <code>./flash.sh gaia</code>.</p> diff --git a/files/pl/archive/b2g_os/phone_guide/index.html b/files/pl/archive/b2g_os/phone_guide/index.html deleted file mode 100644 index d90e90d259..0000000000 --- a/files/pl/archive/b2g_os/phone_guide/index.html +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Firefox OS developer phone guide -slug: Archive/B2G_OS/Phone_guide -tags: - - B2G - - Firefox OS - - Landing - - NeedsTranslation - - Phones - - TopicStub -translation_of: Archive/B2G_OS/Phone_guide ---- -<div class="summary"> - <p>This section contains developer information relevant to specific phones that run Firefox OS. We have general information available on <a href="/en-US/docs/Mozilla/Firefox_OS/Building_and_installing_Firefox_OS" title="Building and installing Firefox OS">Building and installing Firefox OS</a> and <a href="/en-US/docs/Mozilla/Firefox_OS/Hacking_Firefox_OS" title="/en-US/docs/Mozilla/Firefox_OS/Hacking_Firefox_OS">Hacking Firefox OS</a>, so please go there for information about building and installing the platform from scratch. Developers with specific phones in their possession may however find the following articles useful.</p> -</div> -<h2 id="Specific_device_information">Specific device information</h2> -<dl> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Phones">Firefox OS phone data</a></dt> - <dd> - In this article we list the various available Firefox OS phones along with information such as their code names, availability, and specific hardware features.</dd> - <dt> - <a href="/en-US/Firefox_OS/Developer_phone_guide/Flame">Flame</a></dt> - <dd> - Information on Mozilla's high-end Firefox OS reference phone, codenamed the Flame, and produced in partnership with T<sup>2</sup>Mobile.</dd> - <dt> - <a href="/en-US/Firefox_OS/Developer_phone_guide/Geeksphone">Geeksphone</a></dt> - <dd> - In this article we cover some basic tips on how to keep your Geeksphone up-to-date and how to tweak the system Gaia applications.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN">ZTE OPEN</a></dt> - <dd> - This article contains information on the ZTE OPEN Firefox OS device.</dd> - <dt> - <a href="/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C">ZTE OPEN C</a></dt> - <dd> - The ZTE Open C is an updated ZTE-produced Firefox OS device, with higher end hardware and newer software.</dd> -</dl> -<h2 id="General_Firefox_OS_information">General Firefox OS information</h2> -<dl> - <dt> - <a href="/en-US/Firefox_OS/Developer_phone_guide/Firefox_OS_device_features">General device features</a></dt> - <dd> - This page lists typical Firefox OS hardware features and minimum hardware requirements.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Troubleshooting">Troubleshooting</a></dt> - <dd> - This article provides tips for resolving common problems you may have while using Firefox OS.</dd> - <dt> - <a href="/en-US/Firefox_OS/Developer_phone_guide/Best_practices_open_reference_devices">Best practices for open reference devices</a></dt> - <dd> - A set of best practices that we believe should come highly recommended for any widely available open reference devices. All of the recent Firefox OS reference devices have followed these practices.</dd> -</dl> diff --git a/files/pl/archive/b2g_os/phone_guide/płomień/index.html b/files/pl/archive/b2g_os/phone_guide/płomień/index.html deleted file mode 100644 index ab4c222e60..0000000000 --- a/files/pl/archive/b2g_os/phone_guide/płomień/index.html +++ /dev/null @@ -1,384 +0,0 @@ ---- -title: płomień -slug: Archive/B2G_OS/Phone_guide/płomień -translation_of: Archive/B2G_OS/Phone_guide/Flame ---- -<div class="geckoVersionNote"> -<p><strong>Updates on your Flame</strong>: We encourage you to join the following mailing list to receive periodic updates on software builds and other news affecting your Flame device: <a href="https://mail.mozilla.org/listinfo/flamenews">https://mail.mozilla.org/listinfo/flamenews</a></p> -</div> - -<p><img alt="A picture of the Flame device, showing the Firefox OS homescreen containing several app icons." src="https://mdn.mozillademos.org/files/8373/flame-dev-hud.png" style="float: left; margin-bottom: 20px; margin-right: 50px; width: 25%;"></p> - -<h2 id="Available_to_order" style="text-indent: 100%; white-space: nowrap; overflow: hidden; margin: 0; height: 0;">Available to order</h2> - -<p><span class="seoSummary">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.</span></p> - -<p>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:</p> - -<ul> - <li><a href="/en-US/Firefox_OS">Firefox OS zone</a>: For creating your own Firefox OS builds and contributing to the B2G and Gaia projects.</li> - <li><a href="/en-US/Apps">App Center zone</a>: For building open web apps compatible with Firefox OS.</li> - <li><a href="/en-US/Marketplace">Marketplace zone</a>: For information on publishing and distributing apps.</li> - <li><a href="https://marketplace.firefox.com/">Firefox Marketplace</a>: The best place to find and publish new Firefox OS apps.</li> -</ul> - -<p>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.</p> - -<h2 id="Purchasing_a_device">Purchasing a device</h2> - -<p>Our device manufacturer partner has made the device <a href="http://www.everbuying.com/product549652.html">available to order</a> 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.</p> - -<h2 id="Important_steps_to_follow_first">Important steps to follow first</h2> - -<p>There are a couple of steps you should make sure you follow for your particular operating system, before you start trying to update your device, for example by updating your Flame's version of Firefox OS, or pushing apps to your phone (both are covered below.)</p> - -<h3 id="All_operating_systems">All operating systems</h3> - -<p>You need to install ADB and Fastboot on your computer — these are applications that allow you to interact with your phone from your computer when the two are connected via the phone's USB charger cable. They are needed for Flashing your phone to a new version of Firefox OS, recovering from an unresponsive state, pushing apps to your phone, etc.</p> - -<div class="note"> -<p><strong>Note</strong>: If you are on Ubuntu you can install ADB and Fastboot simply by using <code>sudo apt-get install android-tools-adb android-tools-fastboot</code> on the command line.</p> -</div> - -<p>ADB and Fastboot are available in the <a class="external external-icon" href="http://developer.android.com/sdk/index.html" title="Android Developer Tookit">Android Developer Toolkit</a>:</p> - -<ol> - <li>Go to the above link.</li> - <li>Press the <em>Download Eclipse ADT</em> button.</li> - <li>Agree to the license conditions.</li> - <li>Choose between the 32-bit and 64-bit version (32-bit will do if you are not sure).</li> - <li>Click the final <em>Download Eclipse ADT with the Android SDK...</em> button.</li> - <li>Once the download is complete, unzip the zip file's contents onto your computer's desktop.</li> - <li>The folder name is a bit complicated; rename it to just <em>adt.</em></li> -</ol> - -<p>ADB is a tool that you run from the command line. If you open your terminal/command prompt, go to adt/sdk/platform-tools and run the <code>adb</code> command, you should see a load of information thrown back at you about what you can do with ADB. Running <code>adb devices</code> should return the line <code>List of devices attached</code>, and nothing else, because you haven't got any devices attached yet.</p> - -<p>But at this point, you need to set the PATH variable to point to the ADB tool, so you can run it from anywhere, not just when you are in the exact directory that ADB is in.</p> - -<p>To do this on Windows 8 (Windows 7 will be very similar, but with slightly different menu options):</p> - -<ul> - <li>Right click on the Windows button in the bottom left and select <em>Control Panel</em> > <em>System and Security</em> > <em>System</em> > <em>Advanced System settings</em> > <em>Environment Variables</em>.</li> - <li>In the <em>System variables</em> list, find the one called <em>Path</em>, select it, then click <em>Edit...</em></li> - <li>In the <em>Variable value</em> text field of the resulting dialog box, make sure you are at the end of the big string of characters in the box, then type a semi colon (;), followed by the location of the adb tool on your system, which should be <em>C:\Users\[YOUR USER NAME]\Desktop\adt\sdk\platform-tools</em>.<br> - <br> - So if your user name is jamessmith, you would enter ;<em>C:\Users\jamessmith\Desktop\adt\sdk\platform-tools</em>.</li> - <li>Press <em>OK</em> on all the dialog boxes you opened up in this section.</li> - <li>Close your command prompt, open a new one, and test it by typing <code>adb devices</code>. If it comes up with <code>List of devices attached</code>, you are successful!</li> -</ul> - -<p>On Mac/Linux:</p> - -<ul> - <li>In the Finder app, go to your home folder (the one with the house icon.)</li> - <li>If you can't already see hidden files (for example, system files with dots (.) at the beginning), go to Terminal and enter the command <code>defaults write com.apple.finder AppleShowAllFiles YES</code>, then restart Finder.</li> - <li>Open your <code>.bash_profile</code> or <code>.bashrc</code> file in a plain text editor like Text Wrangler or Sublime Text (it needs to be a plain text editor.)</li> - <li>Inside the file, add a new line <code>PATH=/Users/<em>[YOUR USER NAME]</em>/Desktop/adt/sdk/platform-tools:$PATH</code></li> - <li>Save and close the file.</li> - <li>Restart your terminal, and test it by typing <code>adb devices</code>. If it comes up with <code>List of devices attached</code>, you are successful!</li> -</ul> - -<h3 id="Extra_steps_for_Linux_and_Mac">Extra steps for Linux and Mac</h3> - -<p>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 <a href="https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites#For_Linux.3A_configure_the_udev_rule_for_your_phone">add a udev rule</a> for your phone.</p> - -<p>The udev rule for the Flame should look something like the following:</p> - -<pre>SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9025", GROUP="users", MODE="0666"</pre> - -<p>Make sure to <code>--reload-rules</code>, then unplug and replug and your device before continuing.</p> - -<h3 id="Extra_steps_for_Windows">Extra steps for Windows</h3> - -<p>To access the Flame device with the <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a> and Mozilla dev tools like <a href="/en-US/Firefox_OS/Using_the_App_Manager">App Manager</a>/<a href="/en-US/docs/Tools/WebIDE">WebIDE</a>, a USB driver is required. Follow the steps outlined in the below sections to install it.</p> - -<h4 id="Downloading_the_driver">Downloading the driver</h4> - -<p><a href="http://cds.w5v8t3u9.hwcdn.net/Alcatel_USB_Driver_Q_4.0.0_2013_11_11_noinstall.zip">Download the Windows driver from this location</a>. Once downloaded, extract the contents of the ZIP file to a suitable place on your hard drive.</p> - -<div class="note"> -<p><strong>Note</strong>: The Android Debug Bridge (<a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a>) must be installed first: see instructions above if you've not already done this.</p> -</div> - -<h4 id="Installing_the_USB_Driver">Installing the USB Driver</h4> - -<p>At this point, connect your Flame device to your computer using a USB cable.</p> - -<p>To install the driver, open the <code>Alcatel_USB_Driver_Q_4.0.0_2013_11_11_noinstall</code> directory within the extracted ZIP file and double click on the <code>DriverInstaller.exe</code> executable. You may receive a warning at this point that the executable is from an unknown publisher. If so, select the <em>Yes</em> button and the executable will be launched.</p> - -<p><img alt="Simple dialog box showing a picture of a phone along with install and uninstall buttons." src="https://mdn.mozillademos.org/files/8079/driver-install.png" style="display: block; height: 523px; margin: 0px auto; width: 358px;"></p> - -<p>Click on the <em>Install</em> button to install the driver.</p> - -<p>After the driver installs, you can check that it is working by opening a command line window and typing <code>adb devices</code>. This should list the connected device with an output something like:</p> - -<pre>List of devices attached -3561d02a device</pre> - -<p>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 (<em>Settings</em> > <em>Display</em> > <em>Screen timeout</em>) as Windows sometimes appears to reinstall the default drivers when the screen turns off.</p> - -<h2 id="Updating_your_Flame's_software">Updating your Flame's software</h2> - -<p>We will have two main "channels" of Firefox OS software version releases for the Flame phone:</p> - -<ul> - <li>The first channel is our release channel. Flames ship with this channel and will receive over-the-air updates for future major versions, that is, Flames will update from 1.3 to 2.0 to 2.1, etc.</li> - <li>The second channel is our nightly channel. Flames can be flashed to this channel, and after the initial flashing will get over the air updates on a daily or nearly daily basis.</li> -</ul> - -<p>You can get recovery files and tools at the following storage location:</p> - -<ul> - <li><a href="http://cds.w5v8t3u9.hwcdn.net/Flame_2.0_v180_1.zip">Base image v180.zip</a>: An archive containing the Flame's base image of Firefox OS 2.0.</li> -</ul> - -<div class="note"> -<p><strong>Note</strong>: Firefox OS images v180 and above are based on Android KK (Kitkat, 4.4); JB (Jellybean, 4.1–4.3) builds have now been discontinued and are no longer supported, so don't use anything older than v180.</p> -</div> - -<div class="warning"> -<p><strong>Important</strong>: When running a shallow or full flash, your phone data will be overwritten: you should therefore back up your data before updating! See the {{anch("Backing up and restoring your Flame data")}} section for more details.</p> -</div> - -<p>To install the base image on your device:</p> - -<ol> - <li>Make sure remote debugging is enabled on your Flame, using the <em>Remote debugging/Debugging via USB</em> option in the device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a> (the option is different, depending on whether you have Firefox 1.3 and under, or Firefox 1.4+ installed).</li> - <li>Connect your Flame to your computer via a USB cable if it isn't already. Verify that the computer is connected to the device by running the <code>adb devices</code> command in a terminal.</li> - <li>Download the <code>.zip</code> file referenced above. Unzip it onto your Desktop.</li> - <li>Go into the directory you extracted the software into and run it: - <ul> - <li>On Windows, enter the directory in your command prompt, then run the <code>flash.bat</code> script using <code>flash.bat</code> (or double click the file in explorer.)<br> - <strong>Note</strong>: If <code>flash.bat </code>is missing, simply rename the <code>flash.sh</code> file to <code>flash.bat</code>, then run that. Make sure you have <code>adb</code> and <code>fastboot</code> installed and available on <code>PATH</code>.</li> - <li>On Linux / OSX, enter the directory in your terminal, then run the <code>flash.sh</code> script using <code>sudo ./flash.sh</code> (if you don't run it using <code>sudo</code>, the flash script may fail to see your device, and it won't work).</li> - </ul> - </li> -</ol> - -<div class="note"> -<p><strong>Note</strong>: You are also welcome to build your own builds to install on the Flame: see <a href="/en-US/Firefox_OS/Building_and_installing_Firefox_OS">Building and installing Firefox OS</a>.</p> -</div> - -<h3 id="Updating_your_Flame_to_a_nightly_build">Updating your Flame to a nightly build</h3> - -<div class="note"> -<p><strong>Note</strong>: 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.</p> -</div> - -<div class="warning"> -<p><strong>Important</strong>: When running a shallow or full flash, your phone data will be overwritten: you should therefore back up your data before updating! See the {{anch("Backing up and restoring your Flame data")}} section for more details.</p> -</div> - -<ol> - <li>Before updating your phone to a Nightly build you should flash the latest base image to make sure the underlying systems are up to date. Download a base image and use it to update your device's software, as explained above.</li> - <li>Because the above step installs a fresh operating system on your device, you'll need to enable remote debugging on your Flame again, using the <em>Remote debugging </em>option in the device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a>.</li> - <li>Next, choose a build to install (found on <a href="http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/">http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/</a>.) You'll want one of the following: - <ul style="margin-left: 40px;"> - <li>Production builds (including locales) - <ul> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame-kk/">Latest master builds</a> (currently 2.2)</li> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-aurora-flame-kk/">Latest aurora builds</a> (currently 2.1)</li> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g32_v2_0-flame-kk/">Latest release builds</a> (currently 2.0)</li> - </ul> - </li> - <li>Engineering builds (with test apps and only pseudo-locales) - <ul> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame-kk-eng/">Latest master builds</a> (currently 2.2)</li> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-aurora-flame-kk-eng/">Latest aurora builds</a> (currently 2.1)</li> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g32_v2_0-flame-kk-eng/">Latest release builds</a> (currently 2.0)</li> - </ul> - </li> - </ul> - </li> - <li>Pick a version and download both the <code>b2g-XX.XX.en-US.android-arm.tar.gz</code> and <code>gaia.zip</code> files. Save them inside a directory on your Desktop called something like <code>fxos</code>.</li> - <li>Download the <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/shallow_flash.sh">shallow flash script</a> and save it in the same directory as the above two files: follow the link, press the <em>Raw</em> button, then use your browser's save functionality to save the page directly as <code>shallow_flash.sh</code>.</li> - <li><strong>For Windows users:</strong> Also download the <a href="https://raw.githubusercontent.com/Mozilla-TWQA/B2G-flash-tool/master/shallow_flash.bat">shallow_flash.bat windows script</a> and install <a href="https://cygwin.com">Cygwin</a>, which provides a Linux-like environment on Windows. You will need to install the default Cygwin <em>base</em> category plus the <em>unzip</em> package (on the installer, type <em>unzip</em> in the search box and click <em>skip</em>).</li> - <li> - <p>In your Terminal, <code>cd</code> into the directory you saved the files in and Flash the builds to your phone using the following:</p> - - <p><strong>Linux</strong>:</p> - - <pre class="brush: bash">./shallow_flash.sh -ggaia.zip -Gb2g-XX.XX.en-US.android-arm.tar.gz -</pre> - - <p><strong>Mac</strong>:</p> - - <pre class="brush: bash">./shallow_flash.sh -g gaia.zip -G b2g-XX.XX.en-US.android-arm.tar.gz</pre> - - <p><strong>Windows</strong>:</p> - - <p>Double click <code>shallow_flash.bat</code> (with cogs icon) or run it from a command shell. It will flash <code>gaia.zip</code> and a single <code>b2g-XX.XX.en-US.android-arm.tar.gz</code> file.</p> - </li> -</ol> - -<div class="note"> -<p><strong>Note</strong>: If you get a "permission denied" error when running the above commands, your shell script probably doesn't have the right permissions. Running <code>chmod +x shallow_flash.sh</code> on it should solve this problem.</p> -</div> - -<div class="note"> -<p><strong>Note</strong>: A "shallow flash" updates <a href="/en-US/docs/Mozilla/Gecko">Gecko</a> and <a href="/en-US/Firefox_OS/Platform/Gaia">Gaia</a> plus data directories, as opposed to a full flash, which updates Gecko/Gaia, but also the underlying <a href="/en-US/Firefox_OS/Platform/Gonk">Gonk</a> 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 shallow flash over the top of that, once you've got the Gonk/binary layer right.</p> -</div> - -<p>Once the install procedure finishes the phone should reboot into the updated build and display the first time user workflow.</p> - -<h4 id="Font_fix">Font fix</h4> - -<p>After updating Gecko and Gaia to nightly with the v180 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 <a href="https://people.mozilla.org/~mwu/fira-font-update.zip">font update package</a>, extract it, navigate into the directory created by extracting, and run the supplied <code>flash.sh</code> script.</p> - -<div class="note"> -<p><strong>Note</strong>: Another option is to use the <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/update_system_fonts.sh"><code>update_system_fonts.sh</code></a> script, which will download and flash the system fonts automatically.</p> -</div> - -<h4 id="Switch_to_nightly_update_channel">Switch to nightly update channel</h4> - -<ol> - <li>Make sure remote debugging is enabled on your Flame, using the <em>Remote debugging/Debugging via USB</em> option in the device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a></li> - <li>Download the <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/change_channel.sh">change channel</a> script: follow the link, press the <em>Raw</em> button, then use your browser's save functionality to save the page directly as <code>change_channel.sh</code>.</li> - <li>In your Terminal, <code>cd</code> into the directory you saved the script in and change the update channel on your phone using the following command:<br> - - <pre class="brush: bash">./change_channel.sh -v nightly</pre> - </li> - <li>Once the phone reboots, check for updates by going into <em>Settings > Device information > Check now</em></li> -</ol> - -<p>You should now get nightly OTA updates to your phone.</p> - -<div class="note"> -<p><strong>Note:</strong> You can choose between several different update channels. Run "./change_channel.sh -h" to see the other channel options.</p> -</div> - -<h3 id="Fastboot_mode">Fastboot mode</h3> - -<p>If flashing a new build to your phone fails to work, your phone may become unresponsive, leading to the phone rebooting in recovery mode. The recovery mode provides few options (<em>Reboot</em>, <em>Update from adb</em>, <em>Wipe data</em>, <em>Wipe cache</em>, and <em>Update from sdcard</em>). Unfortunately, selecting <em>Update from adb</em> triggers a sideload mode in which you cannot use the other adb commands. The <code>adb sideload</code> command would work but the various flash scripts rely on other adb commands.</p> - -<p>You can force fastboot mode as follows:</p> - -<ol> - <li>Power off the phone (which may involve removing the battery in extreme cases...)</li> - <li>Plug in the USB cable.</li> - <li>Power the phone up again by pressing the Volume Down and Power buttons together.</li> -</ol> - -<p>The phone should now display the text "FASTBOOT": it is in fastboot mode and is waiting for a USB connection. At this point, a USB-connected, computer with adb installed should see the phone listed when the <code>fastboot devices</code> command is run. Note that regular adb would not see the device — only fastboot sees it. In this mode, you can use the flash script to install v180 as explained above. As the script does use both adb and fastboot commands, you may see some initial error and warnings from adb, but the device should be flashed properly at the end of the procedure.</p> - -<h3 id="Emergency_download_mode">Emergency download mode</h3> - -<p>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 <a href="http://cds.w5v8t3u9.hwcdn.net/Flame%20Rescue%20Tool.zip">Emergency Download Tool</a> are required to enter emergency download mode. Install this tool and follow the instructions.</p> - -<h3 id="Recovery_mode">Recovery mode</h3> - -<p>You can enter recovery mode to clear your phone data or manually update the firmware. There are two ways to enter this mode:</p> - -<ul> - <li>If <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a> tools are available, make sure Remote debugging is turned on in the phone's <a href="/en-US/Firefox_OS/Debugging/Developer_settings#Remote_debugging">Developer settings</a>, connect your phone to your computer via USB and enter <code>adb reboot recovery</code> on the command line.</li> - <li>If your phone is powered off, press the Volume Up + Power buttons together.</li> -</ul> - -<p>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.</p> - -<h2 id="Backing_up_and_restoring_your_Flame_data">Backing up and restoring your Flame data</h2> - -<p>When using a Flame, you won't want to lose your phone's contacts and other data while upgrading to a new build (as explained earlier in this article). To backup and restore data you can use our <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/backup_restore_profile.sh">Backup and restore profile</a> tool.</p> - -<ol> - <li>To use this, first download it from Github at the above link. The easiest way to save it is to press the <em>Raw</em> button, then save the raw code as a <code>.sh</code> file using your browser's <em>Save As...</em> option.</li> - <li>Next, make sure you'll have the necessary permissions to execute this file: <code>cd</code> into the directory where you saved the file, and run the following command: - <pre class="brush: bash">chmod +x backup_restore_profile.sh</pre> - </li> -</ol> - -<div class="note"> -<p><strong>Note</strong>: When using this tool, you'll also need to make sure that your phone is connected via USB to your computer, and that ADB (see {{anch("Important steps to follow first")}} above) and Debugging via USB (in your device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a>) are enabled.</p> -</div> - -<div class="note"> -<p><strong>Note</strong>: These instructions should work on Mac and Linux out of the box. To use the backup and restore feature on Windows you'll have to install <a href="https://www.cygwin.com/">Cygwin</a> and run it from inside that.</p> -</div> - -<h3 id="Backing_up_data_from_your_phone">Backing up data from your phone</h3> - -<p>In the directory where you saved the <code>backup_restore_profile.sh</code> file, run the following:</p> - -<pre class="brush: bash">./backup_restore_profile.sh -b</pre> - -<p>This should save your device profile to a directory called <code>mozilla-profile</code>, in the same directory as the script is located.</p> - -<h3 id="Restoring_data_to_your_phone">Restoring data to your phone</h3> - -<p>In the directory where your <code>mozilla-profile</code> directory is located (see above section), run the following:</p> - -<pre class="brush: bash">./backup_restore_profile.sh -r</pre> - -<h3 id="Other_options">Other options</h3> - -<p>The full list of options available for the <code>backup_restore_profile.sh</code> script is as follows:</p> - -<ul> - <li><code>-b</code> or <code>--backup</code> — Backup user profile.</li> - <li><code>-r</code> or <code>--restore</code> — Restore user profile.</li> - <li><code>--sdcard</code> — Also backup/restore the SD card.</li> - <li><code>--no-reboot</code> — Do not reboot B2G after backup/restore.</li> - <li><code>-p</code> or <code>--profile-dir</code> — Specify the profile folder. The default is <code>./mozilla-profile</code>.</li> - <li><code>-h</code> or <code>--help</code> — Display help.</li> -</ul> - -<h2 id="Pushing_apps_to_your_Flame">Pushing apps to your Flame</h2> - -<p>The <a href="/en-US/Firefox_OS/Using_the_App_Manager">App Manager</a> and <a href="/en-US/docs/Tools/WebIDE">WebIDE</a> tools make it easy to push apps to your phone, for testing, etc.</p> - -<h2 id="RAM_adjustment">RAM adjustment</h2> - -<p>You can adjust the available RAM capacity to see how apps perform on Firefox OS phones with lower memory footprints.</p> - -<p>This is accomplished by entering fastboot mode (install fastboot first, which is available on the same SDK page as <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a>) and typing:</p> - -<pre class="brush: bash">adb reboot bootloader -fastboot oem mem [0|256-1024]</pre> - -<p>“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 <code>fastboot oem mem 512</code>.</p> - -<p>You'll need to then reboot your device for the settings to take effect. This can be done using:</p> - -<pre class="brush: bash">fastboot reboot</pre> - -<p>The current memory size can be returned by entering fastboot mode and typing:</p> - -<pre class="brush: bash">fastboot getvar mem -</pre> - -<h2 id="Network_and_Device_specs">Network and Device specs</h2> - -<p><strong>Network</strong>:</p> - -<ul> - <li>802.11b/g/n wireless internet</li> - <li>GSM 850/900/1800/1900MHz</li> - <li>UMTS 850/900/1900/2100MHz</li> -</ul> - -<p><strong>Hardware</strong>: You can find more of the hardware features listed on our <a href="/en-US/Firefox_OS/Developer_phone_guide/Phone_specs">Phone and device specs page</a>.</p> - -<p>Additional features include:</p> - -<ul> - <li>NFC</li> - <li>Bluetooth 3.0</li> - <li>Accelerometer</li> - <li>FM radio</li> - <li>Proximity Sensor</li> - <li>GPS W / A-GPS support</li> - <li>Ambient Light Sensor</li> -</ul> - -<h2 id="See_also">See also</h2> - -<ul> - <li> - <div class="warning"> - <div class="syntaxbox"><a href="https://hacks.mozilla.org/2014/08/videos-getting-started-with-your-flame-device/">Getting started with your Flame</a>: How-to videos by Chris Heilmann</div> - </div> - </li> -</ul> - -<p> </p> diff --git a/files/pl/archive/b2g_os/phone_guide/zte_open_c/index.html b/files/pl/archive/b2g_os/phone_guide/zte_open_c/index.html deleted file mode 100644 index 8e4616e631..0000000000 --- a/files/pl/archive/b2g_os/phone_guide/zte_open_c/index.html +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: ZTE OPEN C -slug: Archive/B2G_OS/Phone_guide/ZTE_OPEN_C -translation_of: Archive/B2G_OS/Phone_guide/ZTE_OPEN_C ---- -<div class="summary"> - <p><span class="seoSummary">ZTE Open C jest następnym telefonem od ZTE z Firefox OS. </span>Posiada między innymi 3-megapikselowy aparat i 4-calowy ekran WVGA. Wyposażony jest w Firefox OS 1.3. Ten artykuł przedstawia informację o tym telefonie oraz szczegóły o aktualizacji i naprawianiu problemów.</p> -</div> -<div class="note"> - <p><strong>Uwaga</strong>: Ten artkuł nie dotyczy ZTE Open. Jeśli posiadasz ten model, powinieneś udać się na stronę <a href="/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN">ZTE Open</a>.</p> -</div> -<div class="note"> - <p><strong>Uwaga</strong>: Narzędzie aktualizacji, które jest potrzebne, aby odblokować telefon jest narazię dostępne tylko do systemu Windows. Nie kupuj tego telefonu jeśli nie masz systemu Windows i chcesz ręcznie instalować własne budowy Firefox OS.</p> -</div> -<p>ZTE Open C jest pierwszym telefonem z <a href="http://blog.mozilla.org/futurereleases/2014/05/08/firefox-os-update-adds-new-features-including-dual-sim-support-and-enhancements-for-music-lovers-and-gamers">ostatnią aktualizacją Firefox OS</a>, oferującą dużo nowości, w tym dostęp do odtwarzacza muzyki z zablokowanego ekranu oraz pasek powiadomień i zaawansowane udostępnianie bluetooth, pozwalające na przenoszenie wielu plików jednoczesnie. Urzytkownicy mogą teraz poruszać się po telefonie szybciej, dzięki inteligentnym folderom, które grupują aplikacje i wyszukiwanie aplikacji w kategorie. Dodatkowo zostały przyśpieszone czasy uruchamiania i przewijania systemowych aplikacji, np. kalendarza, kontaktów, aparatu.</p> -<h2 id="Kupno_urządzenia">Kupno urządzenia</h2> -<p>Telefon kosztuje US$99.99, i jest dostępny w sklepie eBay:</p> -<ul> - <li><a href="http://item.ebay.com/291125433026">ZTE eBay US store</a></li> - <li><a href="http://item.ebay.co.uk/171301269724">ZTE eBay UK store</a> (Klienci z Francji i innych pobliskich europejskich krajów)</li> - <li><a href="http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=131151681046&ssPageName=STRK:MESE:IT">ZTE eBay DE store</a></li> - <li><a href="http://www.ebay.com/itm/111326263156">ZTE eBay RU and EU stores</a></li> -</ul> -<div class="note"> - <p><strong>Uwaga</strong>: Telefon nie posiada domyślnie zainstalowanych aplikacji i usług dla konkretnych sieci. Jest odblokowany dla wszystkich operatorów.</p> -</div> -<h2 id="Parametry_telefonu">Parametry telefonu</h2> -<p>Zobacz <a href="/en-US/Firefox_OS/Developer_phone_guide/Phone_specs">Telefony i informacje</a>.</p> -<h2 id="Aktualizowanie_Firefox_OS">Aktualizowanie Firefox OS</h2> -<p>Najłatwiej zaktualizować urzywając aktualizacji ze <a href="http://www.ztedevices.com/support/selectproduct.html?type=software">Strony pomocy ZTE</a>, wybierz swój kraj w lewej kolumnie, "<em>Smart Phones"</em> w środkowej, i w prawej "Open C(European Standard)" jeśli mieszkasz w europie lub "Open C(American Standard)" jeśli w USA. Potem kliknij przycisk "Selected" aby przejść do strony pobierania.</p> -<p>Gdy pobierzesz aktualizację, w pobranym pliku ZIP poszukaj pliku PDF, pokazującego jak zaktualizować telefon.</p> -<h2 id="Ręczne_aktualizacje">Ręczne aktualizacje</h2> -<p>Jesli chcesz zaktualizować Geco lub Gaia samemu, proces jest trochę trudniejszy. Telefon jest domyślnie zablokowany(bez uprawnień root'a). Aby odblokować telefon użyj <a href="http://en.comebuy.com/developer-firefox-os-open-c.html">Open_C_upgrade_Tool na stronie comebuy.com</a>. Te narzędzie aktualizuje firmware dając prawa root'a i włączając fastboot. Pozwala to także na wgranie nowego oprogramowania na telefon.</p> -<div class="note"> - <p><strong>Uwaga</strong>: To narzędzie jest narazię dostępne tylko dla systemu Windows.</p> -</div> -<h3 id="Aktualizowanie_Geco_i_Gaia">Aktualizowanie Geco i Gaia</h3> -<p>Kiedy posiadasz włączony fastboot, możesz <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Building_and_installing_Firefox_OS">zbudować i zainstalować nowe elementy Firefox OS/B2G</a> Gecko i Gaia na nim.</p> -<ol> - <li>Zacznij od instrukcji <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites">wstępnej budowy</a> i traktuj Open C jak telefon Flame na potrzeby konfiguracji. Ponieważ obydwa (Flame i Open C) bazują na systemie Android Jellybean.</li> - <li>W dalszych krokach trzeba odwołać się do niestandardowego pliku manifest. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1016867">Pobież załącznik tego bug'u</a> i zapisz jako openc.xml.</li> - <li>Wyczyść katalog B2G, usuwając niepotrzebne katalogi:<br> - <pre class="brush: bash" id="comment_text_2">rm -rf objdir-gecko/ out/ backup-flame/</pre> - </li> - <li>Teraz skonfiguruj Firefox OS następującą komendą: - <pre class="brush: bash language-html">./config.sh flame /ŚCIEŻKA/DO/openc.xml</pre> - </li> - <li>Teraz możesz zbudować i wgrać komponenty Gecko wpisując: - <pre class="brush: bash language-html">./build.sh gecko -./flash.sh gecko</pre> - </li> - <li>Teraz powinieneś zaktualizować Gaia, aby nowa wersja Gecko działała z odpowiedną wersją Gaia: - <pre class="brush: bash language-html">cd gaia -make reset-gaia</pre> - </li> -</ol> -<div class="warning"> - <p><strong>Uwaga</strong>: Próba wgrania całego obrazu Flame może uszkodzić telefon, dlatego jest to niezalecane.</p> -</div> -<h3 id="Aktualizowanie_Gaia">Aktualizowanie Gaia</h3> -<p>Aby zaktualizować tylko Gaia(bez Gecko), musisz zrobić fork'a i zklonować repozytorium Gaia na Github, zanim wgrasz go na telefon.</p> -<ol dir="ltr"> - <li>Upewnij się że masz <a href="https://developer.mozilla.org/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a> zainstalowane.</li> - <li>Wejdź na <a href="https://github.com/mozilla-b2g/gaia">https://github.com/mozilla-b2g/gaia</a> i kliknij "fork" w prawym górnym rogu aby zrobić fork'a do własnego repozytorium.</li> - <li>Skopiuj kod z własnego repozytorium na komputer, następującą komendą: - <pre class="brush: bash language-html">git clone https://github.com/twoj-nick-na-github/gaia.git</pre> - </li> - <li><code>cd</code> do pobranego katalogu .</li> - <li>Na telefonie, <a href="https://developer.mozilla.org/en-US/Firefox_OS/Debugging/Developer_settings#Debugging_via_USB">włącz zdalne debugowanie</a> (wybierz opcję "ADB and Devtools").</li> - <li>Teraz podłącz telefon do komputera przez USB. Sprawdź czy ADB dziala komendą <code>adb devices</code>.</li> - <li>Wpisz poniższą komenda, aby zresetować i zaktualizować twój telefon z nową wersją Gaia: - <pre class="brush: bash language-html">make reset-gaia</pre> - </li> -</ol> -<h2 id="Zepsułem_telefon">Zepsułem telefon</h2> -<p>Jeśli twój telefon przestanie odpowiadać, powinieneś naprawić go urzywając oficjalnych wersji Firefox OS i instrukcji do wgrania ich przez karty SD, na stronie ZTE:</p> -<ul> - <li><a href="http://www.ztedevices.com/support/smart_phone/65229ec9-3165-424e-a7dd-3759356325fd.html?type=software">ZTE Open C (Ebay) - Spain</a></li> - <li><a href="http://www.ztedevices.com/support/smart_phone/92f36c98-9cc0-42d6-8f23-8834b4a6849c.html?type=software">ZTE Open C (Ebay) - UK American Standard</a></li> - <li><a href="http://www.ztedevices.com/support/smart_phone/46d40c52-bed4-4cdc-9df9-01719cdf0a70.html?type=software">ZTE Open C (Ebay) - UK European Standard</a></li> -</ul> -<p>Możesz też odwołać się do tego <a href="https://support.mozilla.org/en-US/questions/1003136">wpisu pomocy technicznej</a> po więcej informacji.</p> diff --git a/files/pl/archive/b2g_os/platform/gaia/index.html b/files/pl/archive/b2g_os/platform/gaia/index.html deleted file mode 100644 index 2e30a4b098..0000000000 --- a/files/pl/archive/b2g_os/platform/gaia/index.html +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Gaia -slug: Archive/B2G_OS/Platform/Gaia -translation_of: Archive/B2G_OS/Platform/Gaia ---- -<p>Gaia jest warstwą interfejsu <a href="/en-US/docs/Mozilla/Firefox_OS" title="Mozilla/Firefox_OS">Firefox OS</a>. Wszystko co pojawia się na ekranie po uruchomieniu Firefox OS jest rysowane przez Gaia, włączając w to ekran logowania, ekran główny, aplikację telefonu i inne. Gaia jest całkowicie napisana w <a href="/en-US/docs/en-US/HTML" title="HTML">HTML</a>, <a href="/en-US/docs/CSS" title="CSS">CSS</a> oraz <a href="/en-US/docs/JavaScript" title="JavaScript">JavaScript</a>. Jedynym interfejsem komunikacji z systemem operacyjnym i sprzętem jest standardowe Web API implementowane przez <a href="/en-US/docs/Gecko" title="Gecko">Gecko</a>.</p> -<p>Ze względu na sposób w jaki została zaprojektowana, Gaia może być uruchamiana nie tylko na urządzeniach działających pod kontrolą systemu Firefox OS, lecz także na innych systemach operacyjnych i w innych przeglądarkach internetowych (aczkolwiek, w przypadku tych potencjalnie wycofanych, funkcjonalność zależeć będzie od możliwości przeglądarki).</p> -<p>Aplikacje od zewnętrznych dostawców instalowane poza Gaia mogą być uruchomione za jej pośrednictwem.</p> -<table class="topicpage-table"> - <tbody> - <tr> - <td> - <h2 class="Documentation" id="Documentation" name="Documentation">Dokumentacja na temat Gaia</h2> - <dl> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Introduction_to_Gaia" title="Mozilla/Boot_to_Gecko/Introduction to Gaia">Wstęp do Gaia</a></dt> - <dd> - Gaia jest aplikacją stanowiącą interfejs użytkownika dla urządzeń z systemem Firefox OS; to po prostu aplikacja webowa uruchomiona na wierzchu stosu aplikacyjnego systemu Firefox OS. Ten przewodnik wprowadza do Gaia.</dd> - <dt> - <a href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Gaia_apps">Aplikacje Gaia</a></dt> - <dd> - Informacje o każdej z domyślnych aplikacji dostępnych w rodzinie Gaia wraz ze wskazówkami dotyczących ich użytkowania i modyfikacji.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Hacking" title="Mozilla/Boot_to_Gecko/Gaia hacking guide">Przewodnik hackowania Gaia</a></dt> - <dd> - Przewodnik hackowania i modyfikowania interfejsu Gaia.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Build_System_Primer" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Build_System_Primer">Elementarz Systemu Budującego Gaia</a></dt> - <dd> - Więszość znaczących prac na etapach kompilacji Gaia jest realizowana przez skrypty znajdujące się wewnątrz podkatalogów katalogu build.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Hacking_Tips_And_FAQ" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia/Hacking_Tips_And_FAQ">FAQ i wskazówki hackowania Gaia</a></dt> - <dd> - Lista przydatnych wskazówek i często zadawanych pytań dotyczących hackowania Gaia.</dd> - </dl> - <p><span class="alllinks"><a href="/en-US/docs/tag/Gaia" title="tag/B2G">Zobacz wszystko...</a></span></p> - </td> - <td> - <h2 class="Community" id="Community" name="Community">Uzyskanie pomocy od społeczności</h2> - <p>Jeśli pracujesz z Gaia lub tworzysz aplikacje dla Gaia jest mnóstwo zasobów przygotowanych przez społeczność, które mogą Ci pomóc!</p> - <ul> - <li>Zasięgnij porad na forum projektu Boot to Gecko: {{ DiscussionList("dev-gaia", "mozilla.dev.gaia") }}</li> - </ul> - <ul> - <li>Zadaj pytanie na kanale IRC projektu Gaia od Mozilli: <a href="irc://irc.mozilla.org/gaia" title="irc://irc.mozilla.org/gaia">#gaia</a></li> - </ul> - <p><span class="alllinks"><a class="external" href="http://www.catb.org/~esr/faqs/smart-questions.html" title="http://www.catb.org/~esr/faqs/smart-questions.html">Nie zapominaj o <em>netykiecie</em>...</a></span></p> - <br> - <h2 class="Related_Topics" id="Related_Topics" name="Related_Topics">Powiązane tematy</h2> - <ul> - <li><a href="/en-US/docs/Mobile" title="Mobile">Mobile</a></li> - <li><a href="/en-US/docs/Web" title="/en-US/docs/Web">Technologie dla webdevelopera </a> - <ul> - <li><a href="/en-US/docs/HTML" title="HTML">HTML</a></li> - <li><a href="/en-US/docs/CSS" title="CSS">CSS</a></li> - <li><a href="/en-US/docs/JavaScript" title="JavaScript">JavaScript</a></li> - </ul> - </li> - <li><a href="/en-US/docs/WebAPI" title="/en-US/docs/WebAPI">WebAPI</a></li> - </ul> - <h2 class="Tools" id="Resources" name="Resources">Zasoby</h2> - <ul> - <li><a href="/en-US/docs/Mozilla/Firefox_OS/Architecture" title="Mozilla/Firefox_OS/Architecture">Przegląd architektury Firefox OS</a></li> - </ul> - </td> - </tr> - </tbody> -</table> -<p> </p> diff --git a/files/pl/archive/b2g_os/platform/index.html b/files/pl/archive/b2g_os/platform/index.html deleted file mode 100644 index ff2142919b..0000000000 --- a/files/pl/archive/b2g_os/platform/index.html +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: The Firefox OS platform -slug: Archive/B2G_OS/Platform -tags: - - B2G - - Firefox OS - - Landing - - TopicStub -translation_of: Archive/B2G_OS/Platform ---- -<p>The Firefox OS platform consists of many components. While you don't need to understand its architecture in order to build applications that run on Firefox OS, if you're working on developing or porting the platform—or are simply curious—the following documentation may be of interest to you.</p> -<table class="topicpage-table"> - <tbody> - <tr> - <td> - <h2 class="Documentation" id="Documentation" name="Documentation">Documentation about the Firefox OS platform</h2> - <dl> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Gaia">Gaia</a></dt> - <dd> - Documentation about Gaia, the user interface application for Firefox OS devices; this is a Web application running atop the Firefox OS software stack.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Gonk" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Gonk">Gonk</a></dt> - <dd> - Documentation about Gonk, the operating system layer underneath Gaia. This consists of a Linux kernel and a hardware abstraction layer to which Gecko communicates.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Gecko" title="/en-US/docs/Mozilla/Gecko">Gecko</a></dt> - <dd> - Gecko is the layer of Firefox OS that provides the same open web standards implementation used by Firefox and Thunderbird, as well as many other applications.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Security" title="/en-US/docs/Mozilla/Firefox_OS/Security"> Security</a></dt> - <dd> - Documentation about security in Firefox OS; this includes topics about security devices from every perspective: for app developers, device integrators, and so forth.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Feature_support_chart" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Feature_support_chart">Feature support chart</a></dt> - <dd> - A chart of which features are available in which types of Firefox OS builds.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Architecture" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Architecture">Firefox OS architecture overview</a></dt> - <dd> - An overview of how Firefox OS is structured internally; this is primarily of interest to platform developers and people doing porting work.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Apps_architecture" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Apps_architecture">Firefox OS apps architecture</a></dt> - <dd> - An overview of the application model on Firefox OS.</dd> - <dt> - <a href="/en-US/docs/Mozilla/Firefox_OS/Platform/Settings_list" title="/en-US/docs/Mozilla/Firefox_OS/Platform/Settings_list">Firefox OS settings list</a></dt> - <dd> - A list of common setting names that can be used with the <a href="/en-US/docs/WebAPI/Settings" title="/en-US/docs/WebAPI/Settings">Settings</a> API.</dd> - </dl> - <p><span class="alllinks"><a href="/en-US/docs/tag/B2G" title="/en-US/docs/tag/B2G">View All...</a></span></p> - </td> - <td> - <h2 class="Community" id="Community" name="Community">Getting help from the community</h2> - <p>If you're working with Firefox OS, or developing applications you'd like to run on Firefox OS devices, there are community resources to help you!</p> - <ul> - <li>Consult the Boot to Gecko project forum: {{ DiscussionList("dev-b2g", "mozilla.dev.b2g") }}</li> - </ul> - <ul> - <li>Ask your question on Mozilla's Boot to Gecko IRC channel: <a class="link-irc" href="irc://irc.mozilla.org/b2g" title="irc://irc.mozilla.org/b2g">#b2g</a></li> - </ul> - <p><span class="alllinks"><a class="external" href="http://www.catb.org/~esr/faqs/smart-questions.html" title="http://www.catb.org/~esr/faqs/smart-questions.html">Don't forget about the <em>netiquette</em>...</a></span></p> - <br> - <h2 class="Related_Topics" id="Related_Topics" name="Related_Topics">Related topics</h2> - <ul> - <li><a href="/en-US/docs/Mobile" title="en-US/docs/Mobile">Mobile</a></li> - <li><a href="/en-US/docs/HTML" title="en-US/docs/HTML">HTML</a></li> - <li><a href="/en-US/docs/CSS" title="en-US/docs/CSS">CSS</a></li> - <li><a href="/en-US/docs/JavaScript" title="en-US/docs/JavaScript">JavaScript</a></li> - </ul> - <h2 class="Tools" id="Resources">Resources</h2> - <ul> - <li><a class="link-https" href="https://wiki.mozilla.org/B2G/FAQ" title="B2G/FAQ">Mozilla wiki FAQ</a></li> - <li><a class="link-https" href="https://wiki.mozilla.org/B2G/Schedule_Roadmap" title="https://wiki.mozilla.org/B2G/Schedule_Roadmap">Roadmap</a></li> - <li><a href="/en-US/docs/Mozilla/Firefox_OS/Feature_support_chart" title="/en-US/docs/Mozilla/Firefox_OS/Feature_support_chart">Feature support chart</a></li> - </ul> - </td> - </tr> - </tbody> -</table> -<p> </p> diff --git a/files/pl/archive/b2g_os/preparing_for_your_first_b2g_build/index.html b/files/pl/archive/b2g_os/preparing_for_your_first_b2g_build/index.html deleted file mode 100644 index 5ac3b5ee4c..0000000000 --- a/files/pl/archive/b2g_os/preparing_for_your_first_b2g_build/index.html +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Preparing for your first B2G build -slug: Archive/B2G_OS/Preparing_for_your_first_B2G_build -translation_of: Archive/B2G_OS/Preparing_for_your_first_B2G_build ---- -<div class="summary"> - <p>Before you can build B2G, you need to clone the repository and configure your build tree. This article explains how to do that. </p> -</div> -<p>Depending on your internet connection, the configuration step takes a number of hours to download the files necessary to build FirefoxOS (with a mediocre 150 kBps connection, downloading gigabytes of Android repositories can take tens of hours). Waiting is not as fun as doing, so after you have read through this page and have kicked off the configure script, consider using the time to set up and try out the <a class="vt-p" href="/en-US/docs/Mozilla/Firefox_OS/Using_Firefox_OS_Simulator" title="/en-US/docs/Mozilla/Firefox_OS/Using_Firefox_OS_Simulator">Firefox OS simulator</a>, begin familiarizing yourself with <a class="vt-p" href="/en-US/docs/Apps" title="/en-US/docs/Apps">Documentation for app developers</a> including Designing and Building an App, or familiarize yourself with the information on upcoming steps.</p> -<div class="note"> - <p>You might want to have a side task prepared, or a friend available to go for a coffee with, while you are running the B2G config and build steps. They can take a bit of time.</p> -</div> -<h2 id="Clone_B2G_repository">Clone B2G repository</h2> -<p>The first step, before you can start your first build, is to clone the B2G repository. This will not fetch everything! Instead, it will fetch the B2G build system and setup utilities. Most of the actual B2G code is in the main Mozilla <a class="vt-p" href="/en-US/docs/Mercurial" title="Mercurial">Mercurial</a> repository.</p> -<p>To clone the repository, use git:</p> -<pre>git clone git://github.com/mozilla-b2g/B2G.git</pre> -<p>After cloning (which should only take a minute with a fast connection), <code>cd</code> into the B2G directory:</p> -<pre>cd B2G -</pre> -<h2 id="Configuring_B2G_for_your_device">Configuring B2G for your device</h2> -<div class="warning"> - <strong>Important</strong>: Remember that only devices running <strong>Android 4.0.4</strong> (<strong>Ice Cream Sandwich</strong>)<strong>, 4.3 (Jelly Bean) and 4.4 (KitKat)</strong> and platforms based around it are supported (current Firefox OS devices are). Please check that your phone is actually running one of those supported versions, otherwise this step will most likely fail since some drivers are pulled from non-Nexus devices. Also, if you have to flash your device with the matching stock release. Keep in mind that some USB hubs don't work well with flashing tools, so you may have to connect your device to a built-in USB port.</div> -<div class="warning"> - <strong>Important</strong>: if you are doing the build on Ubuntu 12.10+ or Fedora, you will need to specify GCC 4.6 as the default host compiler after having retrieved the B2G sources, for the process to work (these distros use GCC 4.7 by default). Read <a class="vt-p" href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Customization_with_the_.userconfig_file#Changing_the_default_host_compiler">Changing the default host compiler</a> to find out how to do it.</div> -<div class="note"> - <strong>Note:</strong> <strong>please read all the instructions below</strong> before running any of the build process commands, to make sure you are doing the right thing for you!</div> -<p>Once you've retrieved the core B2G build system, you need to configure it for the device on which you plan to install it. To get a list of supported devices, you can use the <code>config.sh</code> utility — run the following command from within the B2G directory:</p> -<pre>./config.sh -</pre> -<p>This will display a list of the supported devices, like so:</p> -<pre>Usage: ./config.sh [-cdflnq] (device name) -Flags are passed through to |./repo sync|. - -Valid devices to configure are: -- galaxy-s2 -- galaxy-nexus -- nexus-4 -- nexus-s -- nexus-s-4g -- flo "(Nexus 7 2013)" -- nexus-5 -- flame -- otoro -- unagi -- inari -- keon -- peak -- leo -- hamachi -- helix -- wasabi -- fugu -- tara -- pandaboard -- emulator -- emulator-jb -- emulator-kk -- emulator-x86 -- emulator-x86-jb -- emulator-x86-kk -</pre> -<p>If your device isn't listed, you should stop right now and either help port B2G to your device or wait until someone else does it. We'd prefer it if you help out!</p> -<div class="note"> - <strong>Note:</strong> You can find the device name of your phone on the <a href="/en-US/Firefox_OS/Phones">Firefox OS Phones</a> page.</div> -<div class="note"> - <strong>Note: Configuring and building B2G for Keon on a Mac DOESN'T WORK</strong>. You'll need to use Linux when building for this device.</div> -<div class="note"> - <strong>Note</strong>: If for any reason you want to build against a specific version of Gecko, see <a href="#Building_against_a_custom_Gecko">Building against a custom Gecko</a> before you proceed. If you want to build a branch other than the the default for your device (for example, to build a specific version of B2G), see <a href="#Building_a_branch">Building a branch</a>. Note: the default branch varies by device and is <strong>not necessarily trunk</strong>.</div> -<p>This would be a good time for a coffee break, since at this point, you'll be doing your first pull of all the code needed to build Boot to Gecko. Running the device config step as indicated below can take a long time; you may stop it with Ctrl-C and restart it at a later time. If you think some part of the process may have been terminated without completing, run './repo sync' to repair any possible problems.</p> -<h3 id="Configuring_the_B2G_build_for_a_mobile_device">Configuring the B2G build for a mobile device</h3> -<p>At this point, connect your device if it is not already connected; the configure process will need to access it.</p> -<p>If your device was listed in the results shown above, you can start the configure process by running <code>config.sh</code> again, this time specifying your device's name. For example, to build for the Samsung Google Nexus S, you would type:</p> -<pre>./config.sh nexus-s -</pre> -<div class="note"> - <strong>Note:</strong> If you get an error message like <code>fatal: manifest 'nexus-s.xml' not available</code>, chances are that you simply have to specify the branch you want to use. See <a href="#Building_a_branch">Building a branch</a> for details.</div> -<div class="note"> - <strong>Note</strong>: If the config step fails with an error message like <code>error: manifest required for this command -- please run init</code>, then changes are that the manifest file for the repo (located at <code>B2G/.repo/manifest.xml</code>) wasn't created successfully. You should try running <code>config.sh</code> again. If you are doing this for a new device you could add it to <code>config.sh</code> and then hand it your local manifest file like so:<br> - <code>./config.sh <device> -m path/to/manifest.</code></div> -<p>Near the start of the configuration you might need to set the option for color usage, then after this the process continues. You can just select 'y' here, as you probably want a color build.</p> -<h3 id="Configuring_a_build_using_a_system_backup">Configuring a build using a system backup</h3> -<p>If your phone no longer has Android on it, and your B2G tree doesn't have the binary blobs in it, but you wisely <a class="vt-p" href="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites#Backup_the_phone_system_partition" title="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites#Backup_the_phone_system_partition">made a backup of the <code>/system</code> partition</a>, you can perform the build on the system backup like this:</p> -<pre>ANDROIDFS_DIR=<absolute path to parent dir of system dir> ./config.sh <target> -</pre> -<p>The build system will default to looking in someplace like <code>backup-inari/system</code> (depending on the device configuration); if you place the files in the expected place you won't need to specify the directory.</p> -<p>Note that if your phone always had Firefox OS on it to begin with and never ran Android, it's still fine to pull the <code>/system</code> partition per the above directions — this will give you the right files.</p> -<h3 id="Configuring_the_B2G_build_for_an_emulator">Configuring the B2G build for an emulator</h3> -<p>If you want to build an emulator rather than on a real phone, you can specify <code>emulator</code>* to get an ARM device emulator, or <code>emulator-x86*</code> to build an x86 emulator. The latter is faster but not as accurate a representation of an actual mobile device and not as well supported; using it is not advised.</p> -<p>So, to build the ARM Jellybean emulator, for example, you would use the following command:</p> -<pre>./config.sh emulator-jb -</pre> -<p>Near the start of the configuration you might need to set the option for color usage, then after this the process continues. You can just select 'y' here, as you probabaly want a color build.</p> -<p>By this point you should be ready to <a class="vt-p" href="/en-US/docs/Mozilla/Firefox_OS/Building" title="Mozilla/Firefox_OS/Building">start the build</a>, unless you need any of the more advanced information detailed below.</p> -<p>Beware that building for the emulator may fail on 64-bit Linux.</p> -<div class="note"> - <strong>Note:</strong> Developers on Mac OS X 10.9 or above have to switch to emulator-jb or emulator-kk instead, because AOSP ICS based emulator can't be built on Mac OS X 10.9. See <a class="vt-p" href="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites#Requirements_for_Mac_OS_X" title="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites#Requirements_for_Mac_OS_X">Requirements for Mac OS X</a> for further information.</div> -<h2 id="Building_against_a_custom_Gecko">Building against a custom Gecko</h2> -<p>There may be times that you want or need to build Boot to Gecko based on a different version of Gecko than the one that's used by default (as specified in the manifest). You can do so by editing the file <code>.userconfig</code>. For example, if you want to build against mozilla-central:</p> -<pre>export GECKO_PATH=/path/to/mozilla-central -export GECKO_OBJDIR=/path/to/mozilla-central/objdir-gonk -</pre> -<div class="note"> - <p><strong>Note</strong>: if building against a custom Gecko in Mac OS X, the mozilla-central directory must be in a case sensitive file system.<br> - </p> -</div> -<p id="Building_a_branch">Note that you can do this either before you pull the repository (i.e. before the <code>config.sh</code> step above) or at any later point. You can also keep multiple builds (with debugging on or not, etc) by having multiple userconfig files (with different settings--each needs a different OBJDIR, of course) and making .userconfig a symlink that points to whichever config you want to build at the moment.</p> -<p>For more information, read <a class="vt-p" href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Customization_with_the_.userconfig_file#Changing_the_Gecko_source_tree" title="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Customization_with_the_.userconfig_file#Changing_the_Gecko_source_tree">Changing the Gecko source tree</a>.</p> -<h2 id="Building_a_branch_2">Building a branch</h2> -<p>If you want to build for a branch other than the default branch (<strong>note: the default branch may not be "master"!</strong>), you will need to prefix your call to config.sh with a branch name, like this:</p> -<pre>BRANCH=branch-name ./config.sh <device></pre> -<p>The branch names are pretty logical, and largely follow the names of the products/versions, so <code>v1-train</code>, <code>v1.0.0</code>, <code>v1.0.1</code>, <code>v1.1</code>, <code>v1.1.0hd</code>, <code>v1.2, v1.3, v1.4, v2.0</code> and so on into the future. As an example, to build B2G Firefox 1.2, for the Arm emulator, you'd enter</p> -<pre>BRANCH=v1.2 ./config.sh emulator</pre> -<p>If you have run config.sh already, you can see the names of the branches, by going to <code>B2G/.repo/manifests</code> and doing "<code>git branch -a</code>" (this isn't populated unti then.) <strong>The branch name is given as the final token on the line, e.g. "<code>v1-train</code>" or "<code>master</code>"</strong>:</p> -<pre> remotes/origin/master - remotes/origin/v1-train - remotes/origin/v1.0.0 - remotes/origin/v1.0.1</pre> -<p>See <a class="vt-p" href="/en-US/docs/Mozilla/Firefox_OS/Customization_with_the_.userconfig_file" title="Mozilla/Firefox_OS/Customization_with_the_.userconfig_file">Customization with the .userconfig file</a> for additional customizations you can do.</p> -<h2 id="Copying_your_B2G_tree_to_a_new_machine">Copying your B2G tree to a new machine</h2> -<p>If you've previously set up the B2G tree and then gotten a new computer (lucky you!), you'll find your life will be much easier if you simply migrate your entire B2G tree from your old computer to your new one, rather than setting the whole thing up again. To do that, mount your old computer's drive onto your new computer, then do this:</p> -<pre>rsync -a <em>source</em>/ <em>dest</em>/ -</pre> -<p>Where <code>source</code> is the full path (including the trailing slash) of the source tree, and <code>dest</code> is where you want to put it (the trailing slash is also important!).</p> -<div class="note"> - <strong>Note:</strong> If you copy the files from a computer with another platform ensure to run '<em>./build.sh clean'</em> before you start the build process. If you don't do this you might encounter compilation issues.</div> -<p>If you do this, you can skip all of the rest of this article and move right on to <a class="vt-p" href="/en-US/docs/Mozilla/Firefox_OS/Building" title="Mozilla/Firefox_OS/Building">building</a>.</p> -<h2 id="Updating_your_B2G_tree">Updating your B2G tree</h2> -<p>When the repository is updated to a newer version of B2G, you'll want to update your B2G tree. To do this, you can run the following commands:</p> -<pre>git fetch origin -git checkout origin/master</pre> -<p>You can check that these worked correctly by running:</p> -<pre>git show HEAD</pre> -<p>and checking that the commit shown matches the latest commit shown at: <a class="vt-p" href="https://github.com/mozilla-b2g/B2G/commits/master" title="https://github.com/mozilla-b2g/B2G/commits/master">https://github.com/mozilla-b2g/B2G/commits/master</a></p> -<h2 id="On_to_the_next_step">On to the next step</h2> -<p>At this point, you should be ready for <a href="/en-US/Firefox_OS/Building">Building Firefox OS [en-US]</a>.</p> diff --git a/files/pl/archive/b2g_os/simulator/index.html b/files/pl/archive/b2g_os/simulator/index.html deleted file mode 100644 index f9ac33f6e9..0000000000 --- a/files/pl/archive/b2g_os/simulator/index.html +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Symulator Firefox OS -slug: Archive/B2G_OS/Simulator -translation_of: Archive/B2G_OS/Simulator ---- -<div class="note"> - <p>Dodatek Symulator Firefox OS składa się z dwóch części:</p> - <p> </p> - <ul> - <li><strong>Symulator</strong>: zawiera <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client" title="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client">desktopową wersję klienta Firefox OS</a>, który jest wyższą warstwą <a href="/en-US/docs/Mozilla/Firefox_OS" title="/en-US/docs/Mozilla/Firefox_OS">Firefox OS</a> działającym na twoim pulpicie. Symulator zawiera dodatkowo kilka <a href="#Simulator-toolbar" title="#Simulator-toolbar">dodatkowych funkcji</a> które nie są w standardzie desktopowych wydań Firefox OS</li> - <li><strong>Dashboard</strong>: narzędzie przeglądarki Firefox umożliwiające uruchomienie i zatrzymanie symulatora oraz instalację, deinstalację i debugowanie aplikacji działających symulatora. Dashboard ponadto umożliwi Ci instalację aplikacji na prawdziwym urządzeniu i sprawdzenie manifestów w poszukiwaniu problemów.</li> - </ul> - <p>Teraz te dwie części zostały połączone: funkcje Dashboard są zaimplementowane przez <a href="/en-US/Firefox_OS/Using_the_App_Manager">Menedżer Aplikacji (App Manager)</a> Firefox OS, wbudowanego w Firefoxie. The Simulator add-on now only includes the Simulator part.</p> -</div> -<p>Dodatek Symulator Firefox OS umożliwia Ci testowanie i debugowanie <a href="/en-US/docs/Apps" title="/en-US/docs/Apps">aplikacji Firefox OS</a> na komputerze. Cykl kodowanie-testowanie-debugowanie jest znaczenie szybsze na symulatorze w porównaniu z rzeczywistym urządzeniem, oczywiście nie potrzemujesz urządzenia aby go używać. Symulator jest <a href="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client" title="/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_desktop_client">desktopową wersją klienta Firefox OS</a>, który jest wyższą warstwą <a href="/en-US/docs/Mozilla/Firefox_OS" title="/en-US/docs/Mozilla/Firefox_OS">Firefox OS</a> działającym na twoim pulpicie.</p> -<p>Włączasz i wyłączasz symulator i dołączasz narzędzia deweloperskie używając <a href="/en-US/Firefox_OS/Using_the_App_Manager">Menedżera Aplikacji (App Manager)</a>, wbudowanego w Firefox.</p> -<h2 id="Limity_symulatora">Limity symulatora</h2> -<p>Pamiętaj, że symulacja Firefox OS nie jest idealna.</p> -<h3 id="Limity_sprzętowe">Limity sprzętowe</h3> -<p>Symulator nie symuluje limitów sprzętowych takich jak dostępna pamięć RAM lub prędkość procesora.</p> -<h3 id="Kodeki_audiowideo">Kodeki audio/wideo</h3> -<p>Poniższe kodeki wymagają sprzętowego dekodowania i nie są wspierane:</p> -<ul> - <li>MP3</li> - <li>AAC</li> - <li>H.264 (MP4)</li> - <li>WebM</li> -</ul> -<p>To znaczy, że symulator nie potrafi przetestować odtwarzania dźwięku i wideo między innymi na witrynach internetowych.</p> -<h3 id="Niewspierane_API"><a name="Unsupported-APIs">Niewspierane API</a></h3> -<p>Pewne API które normalnie działają na urządzeniu nie zadziałają w symulatorze ze względu na wspierany sprzęt niedostępny na komputerze. Zaimplementowaliśmy symulacje dla kilku API takie jak geolokacja (oczekujemy, że dodamy więcej w przyszłych wydaniach symulatora).</p> -<p>W obecnym momencie poniższe API nie są wspierane. Używanie ich może spowodować otrzymanie błędów lub niewłaściwych wyników:</p> -<ul> - <li><a href="/en-US/WebAPI/WebTelephony" title="/en-US/WebAPI/WebTelephony">Telephony</a></li> - <li><a href="/en-US/docs/WebAPI/WebSMS" title="/en-US/docs/WebAPI/WebSMS">WebSMS</a></li> - <li><a href="/en-US/docs/WebAPI/WebBluetooth" title="/en-US/docs/WebAPI/WebBluetooth">WebBluetooth</a></li> - <li><a href="/en-US/docs/WebAPI/Using_Light_Events" title="/en-US/docs/WebAPI/Using_Light_Events">Ambient Light</a></li> - <li><a href="/en-US/docs/WebAPI/Proximity" title="/en-US/docs/WebAPI/Proximity">Proximity</a></li> - <li><a href="/en-US/docs/WebAPI/Network_Information" title="/en-US/docs/WebAPI/Network_Information">Network Information</a></li> - <li><a href="/en-US/docs/Online_and_offline_events" title="/en-US/docs/Online_and_offline_events">navigator.onLine and offline events</a></li> - <li><a href="/en-US/docs/WebAPI/Vibration" title="/en-US/docs/WebAPI/Vibration">Vibration</a></li> -</ul> -<h2 id="Getting_help"><a name="Simulator-help"></a>Getting help</h2> -<p>The Firefox OS Simulator is still at an early stage of development, and isn't yet as reliable and complete as we'd like it to be.</p> -<p>If you find any bugs, please <a href="https://github.com/mozilla/r2d2b2g/issues?state=open">file them on GitHub</a>. If you have a question, try asking us on the <a href="https://lists.mozilla.org/listinfo/dev-developer-tools">dev-developer-tools mailing list</a> or on <a href="irc://irc.mozilla.org/#devtools">#devtools on irc.mozilla.org</a>.</p> -<h3 id="How_to_enable_verbose_logging"><a name="Simulator-verbose-logging"></a>How to enable verbose logging</h3> -<p>Use about:config to create the preference <a href="mailto:extensions.r2d2b2g@mozilla.org.sdk.console.logLevel">extensions.r2d2b2g@mozilla.org.sdk.console.logLevel</a>, set it to the integer value 0, and disable/reenable the addon. Additional messages about the Simulator's operation will appear in the Error Console (or Browser Console in newer versions of Firefox).</p> diff --git a/files/pl/archive/b2g_os/using_the_app_manager/index.html b/files/pl/archive/b2g_os/using_the_app_manager/index.html deleted file mode 100644 index 2480e1f3ac..0000000000 --- a/files/pl/archive/b2g_os/using_the_app_manager/index.html +++ /dev/null @@ -1,274 +0,0 @@ ---- -title: Using the App Manager -slug: Archive/B2G_OS/Using_the_App_Manager -translation_of: Archive/B2G_OS/Using_the_App_Manager ---- -<div class="summary"> -<p>The App Manager is a tool for Firefox Desktop which provides a number of useful tools to help developers test, deploy and debug HTML5 web apps on Firefox OS phones & Simulator, directly from Firefox browser.</p> - -<p>App Manager is available for Firefox OS 1.2 or later, lower versions are supported in <a href="/en-US/docs/Tools/Firefox_OS_1.1_Simulator">Firefox OS 1.1 Simulator</a>. The App Manager is being replaced by the <a href="/en-US/docs/Tools/WebIDE">WebIDE</a>, starting from Firefox 33. The WebIDE provides all the features of the App Manager also features an editing environment to create and develop Firefox OS apps.</p> -</div> - -<p>{{EmbedYouTube("z1Bxg1UJVf0")}}</p> - -<p>The App Manager is composed of:</p> - -<ul> - <li>An <a href="#Apps_panel"><em>Apps panel</em></a>, which manages local apps (app source code located on your computer) and apps hosted externally, allowing you to package and install them on your device or simulator, and debug them using Toolboxes</li> - <li>A <a href="#Device_panel"><em>Device panel</em></a>, which displays information about the connected device including Firefox OS version installed, permissions required for using device APIs on the device, and apps installed</li> - <li><a href="/en-US/docs/Tools_Toolbox"><em>Toolboxes</em></a>, which are are sets of developer tools (web console, inspector, debugger, etc.) that can be connected to a running app via the Apps panel to perform debugging operations</li> -</ul> - -<h2 id="Quick_setup"><a name="Configuring_device">Quick setup</a></h2> - -<p>This section is designed to get you up and running as soon as possible; if you need some more detail please skip forward to the {{ anch("Device and system configuration") }} section and start reading from there. Also see the {{ anch("Troubleshooting") }} section for help if you are having trouble.</p> - -<ol> - <li>Make sure you have Firefox Desktop 26+ installed</li> - <li>Open the App Manager (in the URL bar, type <code>about:app-manager</code>)</li> - <li>If you don't have a real device: - <ol> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/">Install the Firefox OS Simulator</a></li> - <li>In App Manager's bottom toolbar, click on <em>Start Simulator</em>, then click on the name of the installed simulator, which should appear there.</li> - </ol> - </li> - <li>If you have a real device: - <ol> - <li>Make sure your device is running Firefox OS 1.2+</li> - <li>On Windows, make sure to install the drivers provided by your phone manufacturer</li> - <li>In the Settings of your device, disable Screen Lock (<code>Settings > Phone lock > <code>Lock Screen</code></code>) and enable Remote Debugging (<code>Settings > Device information > More information > Developer</code>)</li> - <li><a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/">Install the ADB Helper</a> add-on in Firefox Desktop</li> - <li>Connect your device to your machine via a USB cable</li> - <li>You should see the name of your device in the App Manager's bottom bar. Click on it.</li> - </ol> - </li> - <li>The bottom bar should show "Connected to: xxx"</li> - <li>Click on the <em>Apps</em> panel and add an app (packaged or hosted)</li> - <li>The <em>Refresh</em> button validates your app and installs it on the Simulator/Device</li> - <li>The <em>Debug</em> button connects the developer tools to the running app</li> - <li><strong>See the {{ anch("Troubleshooting") }} section for help if you are having trouble</strong></li> -</ol> - -<h2 id="Device_and_system_configuration">Device and system configuration</h2> - -<p>The first thing you'll need to do when using the App Manager is make sure your system and phone are set up correctly. This section will run through all the steps required.</p> - -<h3 id="Firefox_OS_1.2_required">Firefox OS 1.2+ required</h3> - -<p>Make sure your device is running Firefox OS 1.2/Boot2Gecko 1.2 or higher. To check which version of Firefox OS the device is runing, go to <code>Settings > Device Information > Software</code>.</p> - -<p>If you don't have a high enough version installed, depending on what phone you have you will need to either install an available nightly build of Firefox 1.2+, or configure and build it yourself from source.</p> - -<p>Builds available:</p> - -<ul> - <li><a href="http://downloads.geeksphone.com/">Geeksphone Keon/Peak builds</a> (to find out more about using these, read <a href="/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/Updating_and_Tweaking_Geeksphone">Updating and Tweaking your Firefox OS Developer Preview phone/Geeksphone</a>)</li> - <li>More to follow</li> -</ul> - -<div class="note"> -<p><strong>Note</strong>: To build your own Firefox OS 1.2+ distribution, follow the instructions located at <a href="/en-US/docs/Mozilla/Firefox_OS/Building_and_installing_Firefox_OS">Building and installing Firefox OS</a>, starting with <a href="/en-US/docs/Mozilla/Firefox_OS/Firefox_OS_build_prerequisites">Firefox OS build prerequisites</a>.</p> -</div> - -<h3 id="Remote_debugging">Remote debugging</h3> - -<p>Next, you need to enable remote debugging in Firefox OS. To do so, go to <code>Settings > Device information > More information > Developer</code> and check the Remote Debugging checkbox.</p> - -<h3 id="Adb_Helper_Add-on" name="Adb_Helper_Add-on">ADB or ADB helper</h3> - -<p>The process uses the Android Debug Bridge (ADB) to handle the device-computer connection and communication. There are two options for running ADB:</p> - -<ul> - <li> - <p>Let Firefox handle ADB (recommended). <a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/">Install the ADB Helper add-on</a>, which makes the process easier. With this installed, there's no need to install the ADB, and no need to type the <code>adb forward</code> command: everything is handled by the add-on.</p> - <a href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/" style="margin-bottom: 20px; padding: 10px; text-align: center; border-radius: 4px; display: inline-block; background-color: #81BC2E; white-space: nowrap; color: white; text-shadow: 0px 1px 0px rgba(0, 0, 0, 0.25); box-shadow: 0px 1px 0px 0px rgba(0, 0, 0, 0.2), 0px -1px 0px 0px rgba(0, 0, 0, 0.3) inset;" title="https://addons.mozilla.org">Download ADB Helper Add-on</a></li> - <li>Use ADB manually. You need to have it installed on your computer: download and install <code>adb</code> as explained in <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">Installing ADB</a>. You'll need to enable port forwarding by entering the following command into your terminal: - <pre>adb forward tcp:6000 localfilesystem:/data/local/debugger-socket</pre> - Note that you'll need to do this every time the phone is restarted or unplugged then re-plugged.</li> -</ul> - -<div class="note"> -<p><strong>Note</strong>: There's no need to run this command if you installed the ADB Helper Add-on.</p> -</div> - -<h2 id="Connecting_your_device_to_the_App_Manager">Connecting your device to the App Manager</h2> - -<p>With all your configuration done, it's now time to plug your device into your computer and start the App Manager:</p> - -<ol> - <li>Plug the device into your computer via USB.</li> - <li>Disable Screen lock on your device by going to <code>Settings > Screen Lock</code> and unchecking the <code>Lock Screen</code> checkbox. This is a good idea because when the screen gets locked, the phone connection gets lost, meaning it is no longer available for debugging.</li> - <li>Start the App Manager — In Firefox Desktop select the <code>Tools > Web Developer > App Manager</code> menu option, or type <code>about:app-manager</code> in the URL bar.</li> - <li>At the bottom of the App Manager tab, you will see a connection status bar (see screenshot below). You should be able to connect your device by clicking the "Connect to localhost:6000" button.</li> - <li>If this works successfully, a prompt should appear on your device: "An incoming request to permit remote debugging connection was detected. Allow connection?". Tap the OK button (You may also have to press the power button on the phone so you can see the prompt.) The connection status bar should update to say "Connected to B2G", with a Disconnect button available to press if you want to cancel the connection.</li> -</ol> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6263/connection-status.png" style="display: block; height: 30px; margin: 0px auto; width: 600px;"></p> - -<div class="note"> -<p><strong>Note</strong>: The other controls in the connection status bar allow you to connect a simulator to the App Manager, which we cover in the next section, below, and change the port that the connection happens on. If you change the port, you'll also need to enable port forwarding for this port as well, as instructed in the {{anch("Enable port forwarding")}} section, above.</p> -</div> - -<h2 id="Using_a_Firefox_OS_Simulator_Add-on"><a name="Simulator">Using a Firefox OS Simulator Add-on</a></h2> - -<p>If you haven't got a real device available to use with App Manager, you can still try it out using a <a href="/en-US/docs/Tools/Firefox_OS_Simulator">Firefox OS Simulator</a> Add-on. To start off, install the simulator with the following button (multiple versions are available; you are advised to install them all, for maximum flexibility):</p> -<p><a class="download-button external ignore-external" href="https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/" rel="noopener">Install Simulator</a></p> - - -<p>Once you've installed the simulator(s), you need to go to about:app-manager to see the connection status bar at the bottom of the App Manager tab, and click the "Start simulator" button. At least three buttons will appear:</p> - -<ul> - <li>"Firefox OS 1.3", "Firefox OS 1.2" ... etc. (or something similar): the left-most buttons contain the names of the simulator versions you have installed. Click one to start a connection to a simulator.</li> - <li>"Add": the middle button navigates to the simulator install links in this article, so you can add more Simulators (Firefox OS 1.3, Firefox OS 1.4, etc.)</li> - <li>"Cancel": the right hand button cancels the connection.</li> -</ul> - -<div class="note"> -<p><strong>Note</strong>: The Firefox OS 1.5 Simulator has been removed, as 1.5 was changed to 2.0. If you have the Firefox OS 1.5 Simulator installed, it won't automatically update to 2.0, so you should uninstall 1.5 and install 2.0 instead. The Firefox OS 2.0 simulator will then automatically update.</p> -</div> - -<div class="note"> -<p><strong>Note</strong>: The Firefox OS 1.2 Simulator has been removed, as no phones are likely to be released with version 1.2 installed — this version is therefore of limited value, and it makes more sense to spend your time debugging on other versions.</p> -</div> - -<h2 id="Running_custom_builds_in_the_App_Manager">Running custom builds in the App Manager</h2> - -<p>Note that you can run custom B2G Desktop and Gaia/Gecko builds in the App Manager via the simulator. Read <a href="/en-US/Firefox_OS/Running_custom_builds_in_the_App_Manager">Running custom Firefox OS/Gaia builds in the App Manager</a> for instructions on how to do this.</p> - -<h2 id="Apps_panel_2"><a name="Apps_panel">Apps panel</a></h2> - -<p>Now that everything is working, let's review the functionality available inside the App Manager, starting with the Apps panel. From here, you can import an existing app to push onto your device and debug:</p> - -<ul> - <li>To install a local app, click on the plus next to the "Add Packaged App" label and use the resulting file chooser dialog to select the directory your app is contained inside.</li> - <li>To install an externally hosted app, enter the absolute URL of the app's manifest file into the text field inside the "Add Hosted App" box, then press the plus button.</li> -</ul> - -<p>Information about your app should appear on the right hand side of the window, as seen below:</p> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6261/apps-panel.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p> - -<h3 id="Manifest_editor">Manifest editor</h3> - -<p>From Firefox 28 onwards, the Apps Panel includes an editor for the app manifest:</p> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6613/apps-panel-fx-28.png" style="display: block; margin: 0px auto; width: 600px;"></p> - -<h3 id="Debugging">Debugging</h3> - -<p>Clicking on <em>"Update"</em> will update (install) the app on the device. Clicking on <em>"debug"</em> will connect a toolbox to the app, allowing you to debug its code directly:</p> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6265/debug.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p> - -<div class="note"> -<p>You'll enjoy playing around with the toolbox — try altering the DOM, CSS etc. and you'll see the updates reflected on the device in realtime. Such updates will be saved on the installed app code; you'll see them next time you open the app on the device.</p> -</div> - -<p>Before Firefox 28, the tools are launched in a separate window. From Firefox 28 onwards, the tools are launched in a separate tab in the App Manager itself, alongside the Apps and Device tabs. The tab is given your app's icon so it's easy to find:</p> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6615/toolbox-fx-28.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p> - -<h3 id="Errors">Errors</h3> - -<p>If an app was not added successfully — for example if the URL was incorrect, or you selected a packaged app folder — an entry will be added to the page for this app, but this will include error information.</p> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6259/apps-error.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p> - -<p>You can also delete an app from this view, by hovering over the App name/description on the left of the window, and pressing the "X" button that appears in each case. This however doesn't remove the app from the device. To do that you need to manually remove the app using the device itself.</p> - -<h2 id="Device_panel_2"><a name="Device_panel">Device panel</a></h2> - -<p>The <em>Device</em> tab displays information about the connected device. From the <em>"</em>Installed Apps<em>"</em> window, apps on the device can be started and debugged.</p> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6267/device-tab.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p> - -<div class="note"> -<p>Note: Certified Apps are not listed by default. <a href="#Debugging_Certified_Apps">See how to debug certified apps</a>.</p> -</div> - -<p><a name="permissions"></a>The "Permissions" window shows the required priviledges for different <a href="/en-US/docs/WebAPI">Web APIs</a> on the current device:</p> - -<p><img alt="" src="https://mdn.mozillademos.org/files/6269/permissions.png" style="display: block; height: 375px; margin: 0px auto; width: 600px;"></p> - -<p>Finally, you can take a screenshot of the current device display by clicking the "Screenshot" button. The screenshot appears in a new tab on Firefox, and from there you can save or discard it as you wish.</p> - -<h2 id="Debugging_Certified_Apps_2"><a name="Debugging_Certified_Apps">Debugging Certified Apps</a></h2> - -<p>Currently only devices running a development build of Firefox OS 1.2+ are capable of debugging certified apps. If you have a development build, you can enable certified app debugging by changing the pref <code>devtools.debugger.forbid-certified-apps</code> to <code>false</code> in your profile. To do this, follow the steps below:</p> - -<ol> - <li> - <p>On your computer, enter the following command in Terminal/console to enter your device's filesystem via the shell:</p> - - <pre class="brush: bash">adb shell</pre> - - <p>Your prompt should change to <code>root@android</code>.</p> - </li> - <li> - <p>Next, stop B2G running using the following command:</p> - - <pre class="brush: bash">stop b2g</pre> - </li> - <li> - <p>Navigate to the following directory:</p> - - <pre>cd /data/b2g/mozilla/*.default/</pre> - </li> - <li> - <p>Here, update the prefs.js file with the following line:</p> - - <pre class="brush: js">echo 'user_pref("devtools.debugger.forbid-certified-apps", false);' >> prefs.js</pre> - </li> - <li> - <p>After you've finished editing and saving the file, start B2G again using the following command:</p> - - <pre class="brush: bash">start b2g</pre> - </li> - <li> - <p>Exit the android filesystem using the <code>exit</code> command; this will return you to your normal terminal prompt.</p> - </li> - <li> - <p>Next, reconnect to the App Manager and you should see certified apps appear for debugging.</p> - </li> -</ol> - -<div class="note"> -<p>Note: If you want to add this preference to your Gaia build you can run <code>make DEVICE_DEBUG=1 reset-gaia</code>.</p> -</div> - -<h2 id="Troubleshooting_2"><a name="Troubleshooting">Troubleshooting</a></h2> - -<p id="My_device_is_not_recognized">If the device is not recognized:</p> - -<ul> - <li>If clicking the button corresponding to your Firefox OS phone doesn't do anything, make sure you haven't connected an Android phone at the same time as the Firefox OS phone to your computer.</li> - <li>Read the <a href="#Configuring_device">Device and system configuration</a> section thoroughly, and make sure all the steps are followed:</li> - <li>Is your device running at least Firefox OS 1.2?</li> - <li>Don't see all the apps? Do you need to enable <a href="#Debugging_Certified_Apps">Certified Apps debugging</a>?</li> - <li>Did you enable "Remote Debugging" in the settings of your phone?</li> - <li>If you are not using the <a href="#Adb_Helper_Add-on">ADB Helper add-on</a>: - <ul> - <li>Did you successfully run the <code>adb forward</code> command?</li> - </ul> - </li> - <li>If you are using the <a href="#Adb_Helper_Add-on">ADB Helper add-on</a> and your device is not listed in the bottom toolbar: - <ul> - <li>If you use Linux, <a href="http://developer.android.com/tools/device.html#setting-up">make sure to setup udev correctly</a></li> - <li>If you use Windows, <a href="http://developer.android.com/tools/device.html#setting-up">make sure to install the appropriate drivers</a></li> - <li>You can also enable verbose logging to gather diagnostics: - <ul> - <li>Use about:config to set the pref "<span class="message"><span class="content"><span class="email">extensions.adbhelper@mozilla.org.sdk</span>.console.logLevel"</span></span> to the string value "all"</li> - <li>Disable and re-enable the ADB Helper add-on from the add-ons manager, or restart Firefox</li> - <li>Open the App Manager again</li> - <li>In the <a href="/docs/Tools/Browser_Console">Browser Console</a>, you should now see additional output lines that mention "adbhelper"</li> - <li>If you see them but aren't sure what they mean, stop by the <a href="https://wiki.mozilla.org/DevTools/GetInvolved#Communication">#devtools room on IRC</a> or <a href="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_ignored=0&bug_severity=normal&bug_status=NEW&cf_blocking_b2g=---&cf_crash_signature=&cf_status_b2g18=---&cf_status_b2g_1_1_hd=---&cf_status_b2g_1_2=---&cf_status_firefox24=---&cf_status_firefox25=---&cf_status_firefox26=---&cf_status_firefox27=---&cf_status_firefox_esr17=---&cf_status_firefox_esr24=---&cf_tracking_b2g18=---&cf_tracking_firefox24=---&cf_tracking_firefox25=---&cf_tracking_firefox26=---&cf_tracking_firefox27=---&cf_tracking_firefox_esr17=---&cf_tracking_firefox_esr24=---&cf_tracking_firefox_relnote=---&cf_tracking_relnote_b2g=---&comment=&component=Developer%20Tools%3A%20App%20Manager&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-203=X&flag_type-37=X&flag_type-41=X&flag_type-5=X&flag_type-607=X&flag_type-720=X&flag_type-721=X&flag_type-737=X&flag_type-748=X&flag_type-781=X&flag_type-787=X&flag_type-791=X&flag_type-799=X&flag_type-800=X&flag_type-802=X&flag_type-803=X&flag_type-809=X&flag_type-825=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Firefox&qa_contact=developer.tools%40firefox.bugs&rep_platform=x86&requestee_type-203=&requestee_type-41=&requestee_type-5=&requestee_type-607=&requestee_type-748=&requestee_type-781=&requestee_type-787=&requestee_type-791=&requestee_type-800=&short_desc=&status_whiteboard=&target_milestone=---&version=Trunk">file a bug</a> with the log output</li> - </ul> - </li> - </ul> - </li> - <li>See <strong>"???????"</strong> instead of the device name on Linux? You have permissions issues. <a href="http://developer.android.com/tools/device.html#setting-up">Make sure to setup udev correctly</a>.</li> - <li>Is your phone screen unlocked?</li> - <li>If the command "adb devices" shows no entries even though the phone is connected and unlocked, you may have to <a href="http://blog.fh-kaernten.at/wehr/?p=1182">edit adb_usb.ini</a>.</li> -</ul> - -<p>Can't connect your device to the App Manager or start the simulator? <a href="https://wiki.mozilla.org/DevTools/GetInvolved#Communication">Let us know</a> or <a href="https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_ignored=0&bug_severity=normal&bug_status=NEW&cf_blocking_b2g=---&cf_crash_signature=&cf_status_b2g18=---&cf_status_b2g_1_1_hd=---&cf_status_b2g_1_2=---&cf_status_firefox24=---&cf_status_firefox25=---&cf_status_firefox26=---&cf_status_firefox27=---&cf_status_firefox_esr17=---&cf_status_firefox_esr24=---&cf_tracking_b2g18=---&cf_tracking_firefox24=---&cf_tracking_firefox25=---&cf_tracking_firefox26=---&cf_tracking_firefox27=---&cf_tracking_firefox_esr17=---&cf_tracking_firefox_esr24=---&cf_tracking_firefox_relnote=---&cf_tracking_relnote_b2g=---&comment=&component=Developer%20Tools%3A%20App%20Manager&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-203=X&flag_type-37=X&flag_type-41=X&flag_type-5=X&flag_type-607=X&flag_type-720=X&flag_type-721=X&flag_type-737=X&flag_type-748=X&flag_type-781=X&flag_type-787=X&flag_type-791=X&flag_type-799=X&flag_type-800=X&flag_type-802=X&flag_type-803=X&flag_type-809=X&flag_type-825=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Firefox&qa_contact=developer.tools%40firefox.bugs&rep_platform=x86&requestee_type-203=&requestee_type-41=&requestee_type-5=&requestee_type-607=&requestee_type-748=&requestee_type-781=&requestee_type-787=&requestee_type-791=&requestee_type-800=&short_desc=&status_whiteboard=&target_milestone=---&version=Trunk">file a bug</a>.</p> |