Hello Alexander, thank for the fast response. Sorry but I don't think that my issue has something to do with right permissions. However, I have already tried several udev rules and also as root/su without success. Following guide was taken as a reference - - Please noticed – in bootloader mode my device, a Asus MeMo Pad FHD 10, has the same product ID as yours! Which device did you use? Can I do something else to solve my issue or enclose the failure root cause?

Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices. Or, get it from the Android SDK Manager as follows: In Android Studio, click Tools >Android >SDK Manager. May 13, 2010. If you are like me and like developing in Linux, then you will find this guide useful. When I was setting up everything for my Android development, I ran into the problem that Linux was not recognizing my Android phone, and took me some time figuring out how to make Linux recognize my phone.

Dell Optiplex Gx240 Vista Drivers here. By the way, my Android SDK environment (adb and fastboot) works with an other Android device without any problem – no Intel device, Sony Xperia P. Thank in advance!

Best regards Tom.

Contents • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Exploring Android device When you connect a modern Android device via USB to a computer you can use to transfer files and to debug it. Files can generally be transferred with various protocols (,,, HTTP). You just need to setup a client and a server (via apps Android can act as either one). For flashing and restoring Android firmware see. See for software available for Arch Linux that can be used to connect to Android. Android development There are 3 steps that need to be performed before you can develop Android applications on your Arch Linux box: • Install the Android SDK core component, • Install one or several Android SDK Platform packages, • Install one of the IDEs compatible with the Android SDK.

Android SDK core components. Note: • If you are running a 64-bit system, make sure the repository is enabled to avoid error: target not found: lib32-* error messages.

• If you plan to install and want the IDE to manage your SDK installation, you do not need to install these packages Before developing Android applications, you need to install the Android SDK, which is made of 4 distinct packages, all installable from: • AUR • AUR • AUR • AUR If supporting older devices, or working with older code, AUR and AUR might be required. Android-sdk will be installed on /opt/android-sdk/.

This folder has root permissions, so keep in mind to run sdk manager as root, otherwise you will not be able to modify anything in this directory. If you intend to use it as a regular user, create the Android sdk users group: # groupadd sdkusers Add your user into this group: # gpasswd -a sdkusers Change folder's group. # chown -R:sdkusers /opt/android-sdk/ Change permissions of the folder so the user that was just added to the group will be able to write in it: # chmod -R g+w /opt/android-sdk/ Re-login or as log your terminal in to the newly created group: $ newgrp sdkusers. Note: If you plan to install and want the IDE to handle your SDK, you don't need to install these packages Install the desired Android SDK Platform package from the: • AUR (latest) • AUR • AUR • AUR • AUR • AUR • AUR • AUR • AUR • AUR • AUR • AUR • AUR • AUR Android System Images Install the desired package from the. This step may not be necessary if installing Android Studio. The Images are needed for emulating a specific android device. They are not needed if you want to develop with an android phone.

Development environment Android Studio is the official Android development environment based on IntelliJ IDEA. Alternatively, you can use with the NBAndroid plugin. All are described below. Android Studio is the official Android development environment based on. It provides integrated Android developer tools for development and debugging. You can it with the AUR package. If you get an error about a missing SDK, refer to above.

Note: • If you are using a tiling window manager other than i3wm, you may need to apply one of the fixes mentioned in issue page. • Make sure you properly otherwise android-studio will not start.

Normally, apps are built through the Android Studio GUI. To build apps from the commandline (using e.g../gradlew assembleDebug), add the following to your ~/.bashrc: export ANDROID_HOME=/opt/android-sdk Netbeans If you prefer using as your IDE and want to develop Android applications, download the by going to Tools >Plugins >Settings. Add the following URL: Then go to Available Plugins and install the Android and JUnit plugins. Once you have installed go to Tools >Options >Miscellaneous >Android. And select the path where the SDK is installed (/opt/android-sdk by default). That is it, now you can create a new Android project and start developing using Netbeans.

Note: • if you get a message about unresolvable dependencies, install manually and try again. • as an alternative, you can install the ADT via eclipse's built in 'add new software' command (see instructions on ADT site).

• if you are in real trouble, it is also possible to download Android SDK and use the bundled Eclipse. This usually works without problems. • if you need to install extra SDK plugins not found in the AUR, you must change the file ownership of /opt/android-sdk first. You can do this with # chgrp -R users /opt/android-sdk; chmod -R 0775 /opt/android-sdk (see for more details).

Enter the path to the Android SDK Location in Windows >Preferences >Android. Note: Installing both and to build LineageOS may result in a build speed improvement as the build process will prefer the system's Java Development Kit The depends on the Android version you're building: • For Android 7 and 8 (Nougat and Oreo), OpenJDK 8 is required, which is available with the package. • For Android 5 and 6 (Lollipop and Marshmallow), OpenJDK 7 is required, which is available with the package. Older versions require a working Oracle JDK installed on your build system. It will not work with OpenJDK.

• For Gingerbread through KitKat (2.3 - 4.4), Java 6 is required, which is available as AUR from the AUR. • For Cupcake through Froyo (1. Jennifer Lopez Get Right Mp3 Indir Boxca. 5 - 2.2), Java 5 is required, which is available as AUR from the AUR. Note: Android expect java in /usr/lib/jvm/java-x-openjdk-amd64, where x is the java version.

Set JAVA_HOME to avoid this requirement and match archlinux installation path. Example: $ export JAVA_HOME=/usr/lib/jvm/java-x-openjdk This change will be valid only for the current terminal session.

Setting up the build environment the package. Create a directory to build. $ mkdir ~/android $ cd ~/android The Android build process expects python to be python2.

Create a python2 virtual environment and activate it: $ virtualenv2 venv $ source venv/bin/activate. Note: • This activation is only active for the current terminal session. The virtual env will be kept in the venv folder. • During build you may receive error pertaining to missing python modules.

A quick and dirty fix is to symlink /usr/lib/python2.7/* to ~/android/venv/lib/python2.7/ (Change ~/android to reflect your build directory if different than above). Example: $ ln -s /usr/lib/python2.7/* ~/android/venv/lib/python2.7/ or (assuming build directory Data/Android_Build): $ ln -s /usr/lib/python2.7/* /Data/Android_Build/venv/lib/python2.7/ Downloading the source code This will clone the repositories. You only need to do this the first time you build Android, or if you want to switch branches. • The repo has a -j switch that operates similarly to the one used with make. Since it controls the number of simultaneous downloads, you should adjust the value depending on downstream network bandwidth. • You will need to specify a branch (release of Android) to check out with the -b switch. If you leave the switch out, you will get the so-called master branch.

$ repo init -u -b master $ repo sync -j4. Note: To further decrease sync times, you can utilize the -c switch with the repo command as such: $ repo sync -j8 -c The -c switch will only sync the branch which is specified in the manifest, which in turn is determined by the branch specified with the -b switch, or the default branch set by the repository maintainer. Wait a long time. Just the uncompiled source code, along with the.repo and.git directories that are used to keep track of it, are well over 10 GB.

As of Android 6.0.1, the entire codebase totals 40 GB. Note: • Make sure you have enough RAM. Android will use the /tmp directory heavily. By default the size of the partition the /tmp folder is mounted on is half the size of your RAM. If it fills up, the build will fail. 4GB of RAM or more is recommended.

Alternatively, you can get rid of the tmpfs from all together. • From the: 'GNU make can handle parallel tasks with a -jN argument, and it's common to use a number of tasks N that's between 1 and 2 times the number of hardware threads on the computer being used for the build. On a dual-E5520 machine (2 CPUs, 4 cores per CPU, 2 threads per core), the fastest builds are made with commands between make -j16 and make -j32.' Testing the build When finished, run/test the final image(s). $ emulator Creating a Flashable Image To create an image that can be flashed it is necessary to: make -j8 updatepackage This will create a zip image under out/target/product/hammerhead (hammerhead being the device name) that can be flashed. Restoring Android.

Note: Restoring firmwares using fastboot can be quite tricky, but you might want to browse for a stock firmware, which is mostly a *.zip file, but inside of it, comes with the firmware files and flash-all.sh script. For example, firmwares include flash-all.sh script or another example could be for OnePlus One -, where you can find firmwares with included flash-all.sh script. Samsung devices Samsung devices can't be flashed using Fastboot tool. Alternatives are only Heimdall and Odin (by using Windows and VirtualBox). Heimdall is a cross-platform open-source tool suite used to flash firmware (also known as ROMs) onto Samsung mobile devices and is also known as an alternative to. It can be installed as or AUR. The flashing instructions can be found on Heimdall's or on.

Odin (Virtualbox).