| page.title=Known Issues |
| @jd:body |
| |
| <!-- |
| Copyright 2013 The Android Open Source Project |
| |
| Licensed under the Apache License, Version 2.0 (the "License"); |
| you may not use this file except in compliance with the License. |
| You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| <div id="qv-wrapper"> |
| <div id="qv"> |
| <h2>In this document</h2> |
| <ol id="auto-toc"> |
| </ol> |
| </div> |
| </div> |
| |
| <p>Even with our best care, small problems sometimes slip in. This page keeps |
| track of the known issues around using the Android source code.</p> |
| |
| <h2 id="build-issues">Build issues</h2> |
| |
| <h3 id="missing-cellbroadcastreceiver">Missing CellBroadcastReceiver in toro builds</h3> |
| <p><strong>Symptom</strong></p>On AOSP builds for toro (up to Jelly Bean 4.2.1), |
| CellBroadcastReceiver doesn't get included in the system.</p> |
| |
| <p><strong>Cause:</strong></p> There's a typo in <code>vendor/samsung/toro/device-partial.mk</code>, |
| where <code>PRODUCT_PACKAGES</code> has the K replaced by an H. |
| <p><strong>Fix</strong>: Use the latest packages for 4.2.2, or manually fix the typo.</p> |
| |
| <h3 id="missing-cts-native-xml-generator">Missing CTS Native XML Generator</h3> |
| <p><strong>Symptom</strong>: On some builds of IceCreamSandwich and later, the following |
| warning is printed early during the build: |
| <code>/bin/bash: line 0: cd: cts/tools/cts-native-xml-generator/src/res: No |
| such file or directory</code></p> |
| <p><strong>Cause</strong>: Some makefile references that path, which doesn't exist.</p> |
| <p><strong>Fix</strong>: None. This is a harmless warning.</p> |
| <h3 id="black-gingerbread-emulator">Black Gingerbread Emulator</h3> |
| <p><strong>Symptom</strong>: The emulator built directly from the gingerbread branch |
| doesn't start and stays stuck on a black screen.</p> |
| <p><strong>Cause</strong>: The gingerbread branch uses version R7 of the emulator, |
| which doesn't have all the features necessary to run recent versions |
| of gingerbread.</p> |
| <p><strong>Fix</strong>: Use version R12 of the emulator, and a newer kernel that matches |
| those tools. No need to do a clean build.</p> |
| <pre><code>$ repo forall platform/external/qemu -c git checkout aosp/tools_r12 |
| $ make |
| $ emulator -kernel prebuilt/android-arm/kernel/kernel-qemu-armv7 |
| </code></pre> |
| <h3 id="emulator-built-on-macos-107-lion-doesnt-work">Emulator built on MacOS 10.7 Lion doesn't work.</h3> |
| <p><strong>Symptom</strong>: The emulator (any version) built on MacOS 10.7 Lion |
| and/or on XCode 4.x doesn't start.</p> |
| <p><strong>Cause</strong>: Some change in the development environment causes |
| the emulator to be compiled in a way that prevents it from working.</p> |
| <p><strong>Fix</strong>: Use an emulator binary from the SDK, which is built on |
| MacOS 10.6 with XCode 3 and works on MacOS 10.7.</p> |
| |
| <h3 id="partial-and-emulator-builds"><code>WITH_DEXPREOPT=true</code> and emulator builds.</h3> |
| <p><strong>Symptom</strong>: When conducting partial builds or syncs (make system no dependencies) |
| on emulator builds, the resulting build doesn't work.</p> |
| <p><strong>Cause</strong>: All emulator builds now run Dex optimization at build |
| time by default, which requires to follow all dependencies to |
| re-optimize the applications each time the framework changes.</p> |
| <p><strong>Fix</strong>: Locally disable Dex optimizations with |
| <code>export WITH_DEXPREOPT=false</code>, delete the existing optimized |
| versions with <code>make installclean</code> and run a full build to |
| re-generate non-optimized versions. After that, partial builds |
| will work.</p> |
| <h3 id="permission-denied-during-builds">"Permission Denied" during builds.</h3> |
| <p><strong>Symptom</strong>: All builds fail with "Permission Denied", possibly |
| along with anti-virus warnings.</p> |
| <p><strong>Cause</strong>: Some anti-virus programs mistakenly recognize some |
| source files in the Android source tree as if they contained |
| viruses.</p> |
| <p><strong>Fix</strong>: After verifying that there are no actual viruses |
| involved, disable anti-virus on the Android tree. This has |
| the added benefit of reducing build times.</p> |
| <h3 id="build-errors-related-to-using-the-wrong-compiler">Build errors related to using the wrong compiler.</h3> |
| <p><strong>Symptom</strong>: The build fails with various symptoms. One |
| such symptom is <code>cc1: error: unrecognized command line option "-m32"</code></p> |
| <p><strong>Cause</strong>: The Android build system uses the default compiler |
| in the PATH, assuming it's a suitable compiler to generate |
| binaries that run on the host. Other situations (e.g. using |
| the Android NDK or building the kernel) cause the default |
| compiler to not be a host compiler.</p> |
| <p><strong>Fix</strong>: Use a "clean" shell, in which no previous |
| actions could have swapped the default compiler.</p> |
| <h3 id="build-errors-caused-by-non-default-tool-settings">Build errors caused by non-default tool settings.</h3> |
| <p><strong>Symptom</strong>: The build fails with various symptoms, possibly |
| complinaing about missing files or files that have the |
| wrong format. One such symptom is <code>member [...] in archive is not an object</code>.</p> |
| <p><strong>Cause</strong>: The Android build system tends to use many host tools |
| and to rely on their default behaviors. Some settings change |
| those tools' behaviors and make them behave in ways that |
| confuse the build system. Variables known to cause such |
| issues are <code>CDPATH</code> and <code>GREP_OPTIONS</code>.</p> |
| <p><strong>Fix</strong>: Build Android in an environment that has as few |
| customizations as possible.</p> |
| <h3 id="build-error-with-40x-and-earlier-on-macos-107">Build error with 4.0.x and earlier on MacOS 10.7.</h3> |
| <p><strong>Symptom</strong>: Building IceCreamSandwich 4.0.x (and older |
| versions) fails on MacOS 10.7 with errors similar to this: |
| <code>Undefined symbols for architecture i386: "_SDL_Init"</code></p> |
| <p><strong>Cause</strong>: 4.0.x is not compatible with MacOS 10.7.</p> |
| <p><strong>Fix</strong>: Either downgrade to MacOS 10.6, or use the master |
| branch, which can be built on MacOS 10.7.</p> |
| <pre><code>$ repo init -b master |
| $ repo sync |
| </code></pre> |
| <h3 id="build-error-on-macos-with-xcode-43">Build error on MacOS with XCode 4.3.</h3> |
| <p><strong>Symptom</strong>: All builds fail when using XCode 4.3.</p> |
| <p><strong>Cause</strong>: XCode 4.3 switched the default compiler from |
| gcc to llvm, and llvm rejects code that used to be |
| accepted by gcc.</p> |
| <p><strong>Fix</strong>: Use XCode 4.2.</p> |
| <h3 id="build-error-with-40x-and-earlier-on-ubuntu-1110">Build error with 4.0.x and earlier on Ubuntu 11.10.</h3> |
| <p><strong>Symptom</strong>: Building IceCreamSandwich 4.0.x (and older |
| versions) on Ubuntu 11.10 and newer fails with errors similar to this: |
| <code><command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default]</code></p> |
| <p><strong>Cause</strong>: Ubuntu 11.10 uses a version of gcc where that symbol |
| is defined by default, and Android also defines that symbol, |
| which causes a conflict.</p> |
| <p><strong>Fix</strong>: Either downgrade to Ubuntu 10.04, or use the master |
| branch, which can be compiled on Ubuntu 11.10 and newer.</p> |
| <pre><code>$ repo init -b master |
| $ repo sync |
| </code></pre> |
| |
| <h2 id="source-sync">Source sync issues<h2> |
| |
| <h3 id="difficulties-syncing-the-source-code-proxy-issues">Difficulties syncing the source code (proxy issues).</h3> |
| <p><strong>Symptom</strong>: <code>repo init</code> or <code>repo sync</code> fail with http errors, |
| typically 403 or 500.</p> |
| <p><strong>Cause</strong>: There are quite a few possible causes, most often |
| related to http proxies, which have difficulties handling the |
| large amounts of data getting transfered.</p> |
| <p><strong>Fix</strong>: While there's no general solution, using python 2.7 |
| and explicitly using <code>repo sync -j1</code> have been reported to |
| improve the situation for some users.</p> |
| <h3 id="difficulties-syncing-the-source-tree-virtualbox-ethernet-issues">Difficulties syncing the source tree (VirtualBox Ethernet issues).</h3> |
| <p><strong>Symptom</strong>: When running <code>repo sync</code> in some VirtualBox installations, |
| the process hangs or fails with a variety of possible symptoms. |
| One such symptom is |
| <code>DownloadError: HTTP 500 (Internal Server Error: Server got itself in trouble)</code>.</p> |
| <p><strong>Cause</strong>: The default network behavior of VirtualBox is to use |
| NAT (Network Addrss Translation) to connect the guest system to |
| the network. The heavy network activity of repo sync triggers some |
| corner cases in the NAT code.</p> |
| <p><strong>Fix</strong>: Configure VirtualBox to use bridged network instead of NAT.</p> |
| <h3 id="difficulties-syncing-the-source-tree-dns-issues">Difficulties syncing the source tree (DNS issues).</h3> |
| <p><strong>Symptom</strong>: When running <code>repo sync</code>, the process fails with |
| various errors related to not recognizing the hostname. One such |
| error is <code><urlopen error [Errno -2] Name or service not known></code>.</p> |
| <p><strong>Cause</strong>: Some DNS systems have a hard time coping with the |
| high number of queries involved in syncing the source tree |
| (there can be several hundred requests in a worst-case scenario).</p> |
| <p><strong>Fix</strong>: Manually resolve the relevant hostnames, and hard-code |
| those results locally.</p> |
| <p>You can resolve them with the <code>nslookup</code> command, which will give |
| you one numerical IP address for each of those (typically in the |
| "Address" part of the output).</p> |
| <pre><code>$ nslookup googlesource.com |
| $ nslookup android.googlesource.com |
| </code></pre> |
| <p>You can then hard-code them locally by editing <code>/etc/hosts</code>, and |
| adding two lines in that file, of the form:</p> |
| <pre><code>aaa.bbb.ccc.ddd googlesource.com |
| eee.fff.ggg.hhh android.googlesource.com |
| </code></pre> |
| <p>Note that this will only work as long as the servers' addresses |
| don't change, and if they do and you can't connect you'll have |
| to resolve those hostnames again and edit <code>etc/hosts</code> accordingly.</p> |
| <h3 id="difficulties-syncing-the-source-tree-tcp-issues">Difficulties syncing the source tree (TCP issues).</h3> |
| <p><strong>Symptom</strong>: <code>repo sync</code> hangs while syncing, often when it's |
| completed 99% of the sync.</p> |
| <p><strong>Cause</strong>: Some settings in the TCP/IP stack cause difficulties |
| in some network environments, such that <code>repo sync</code> neither completes |
| nor fails.</p> |
| <p><strong>Fix</strong>: On linux, <code>sysctl -w net.ipv4.tcp_window_scaling=0</code>. On |
| MacOS, disable the rfc1323 extension in the network settings.</p> |
| |
| |
| <h2 id="runtime-issues">Runtime issues</h2> |
| <h3 id="camera-and-gps-dont-work-on-galaxy-nexus">Camera and GPS don't work on Galaxy Nexus.</h3> |
| <p><strong>Symptom</strong>: Camera and GPS don't work on Galaxy Nexus. |
| As an example, the Camera application crashes as soon as it's |
| launched.</p> |
| <p><strong>Cause</strong>: Those hardware peripherals require proprietary |
| libraries that aren't available in the Android Open Source |
| Project.</p> |
| <p><strong>Fix</strong>: None.</p> |
