[Arch Linux] Android SDK, NDK, Eclipse, ADB Auto-Installer

Search This thread

Tahl

Member
Aug 15, 2011
22
62
Birmingham
** I would really like to hear your results on if the script was successful or not and if you have any errors so that I can try and work out the bugs that the script may have. I am new to Arch Linux and working from a fairly barebones system. I believe I will have most of the dependencies resolved in the script, but 64-bit Linux systems *may* need to have the Multilib repository for this to function properly.


I wanted to bring my Auto-Installer over to Arch Linux while I am playing with it. It uses the Pacman manager, so as long as you are using that I believe you'll experience no problems installing this.

Some changes from this one, compared to the Mint/Ubuntu version: The script cannot be executed with SUDO. Don't edit the code and remove the fail safe for this, to try because it'll just cause the script to fail at the end. Just enter the password requests.

Download Links
Github, Download link is at the top. Use the command: tar xvfz <filename.tar.gz> to extract this one.

git clone git://gist.github.com/1254981.git gist-1254981

Dropbox Script Link

For safety reasons, I'd suggest taking one of the first two just incase dropbox corrupts the script for some reason.

Installation Instructions

This script assumes you know very basic knowledge of the terminal (or GUI equivalent). Download the file you want from above and navigate to the directory that it is and type the following commands (dropbox users substitute andadb.sh with andadbarch.sh:

Code:
$ chmod +x andadbarch.sh
$ ./andadbarch.sh

[COLOR="#FF0000"]This part takes a long time depending on your internet connection.[/COLOR]
Install the "Android SDK Platform-tools" to gain access to ADB.  
Also install any other API that you would like at this time.

You can now test your phone by typing "adb" in terminal while plugged in with USB debugging mode turned on.


What's Been Done to my System?

  • Eclipse has been installed.
  • Android SDK is installed in /usr/local/android-sdk
  • Android NDK is installed in /usr/local/android-ndk
  • Symlink created for Dalvik Debug Monitor, start it from terminal with "ddms" -- If you run two monitors or it gives you an error the first time you run it type it again and the program will start.
  • Symlink created for Android Debug Monitor. Type "adb" from terminal to see command list.
  • 99-android.rules created automatically and placed into /etc/udev/rules.d directory.


Version 1.0.4 99-android.rules:

Code:
#Acer
SUBSYSTEM==usb, SYSFS{idVendor}==0502, MODE=0666
#ASUS
SUBSYSTEM==usb, SYSFS{idVendor}==0b05, MODE=0666
#Dell
SUBSYSTEM==usb, SYSFS{idVendor}==413c, MODE=0666
#Foxconn
SUBSYSTEM==usb, SYSFS{idVendor}==0489, MODE=0666
#Garmin-Asus
SUBSYSTEM==usb, SYSFS{idVendor}==091E, MODE=0666
#Google
SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666
#HTC
SUBSYSTEM==usb, SYSFS{idVendor}==0bb4, MODE=0666
#Huawei
SUBSYSTEM==usb, SYSFS{idVendor}==12d1, MODE=0666
#K-Touch
SUBSYSTEM==usb, SYSFS{idVendor}==24e3, MODE=0666
#KT Tech
SUBSYSTEM==usb, SYSFS{idVendor}==2116, MODE=0666
#Kyocera
SUBSYSTEM==usb, SYSFS{idVendor}==0482, MODE=0666
#Lenevo
SUBSYSTEM==usb, SYSFS{idVendor}==17EF, MODE=0666
#LG
SUBSYSTEM==usb, SYSFS{idVendor}==1004, MODE=0666
#Motorola
SUBSYSTEM==usb, SYSFS{idVendor}==22b8, MODE=0666
#NEC
SUBSYSTEM==usb, SYSFS{idVendor}==0409, MODE=0666
#Nook
SUBSYSTEM==usb, SYSFS{idVendor}==2080, MODE=0666
#Nvidia
SUBSYSTEM==usb, SYSFS{idVendor}==0955, MODE=0666
#OTGV
SUBSYSTEM==usb, SYSFS{idVendor}==2257, MODE=0666
#Pantech
SUBSYSTEM==usb, SYSFS{idVendor}==10A9, MODE=0666
#Philips
SUBSYSTEM==usb, SYSFS{idVendor}==0471, MODE=0666
#PMC-Sierra
SUBSYSTEM==usb, SYSFS{idVendor}==04da, MODE=0666
#Qualcomm
SUBSYSTEM==usb, SYSFS{idVendor}==05c6, MODE=0666
#SK Telesys
SUBSYSTEM==usb, SYSFS{idVendor}==1f53, MODE=0666
#Samsung
SUBSYSTEM==usb, SYSFS{idVendor}==04e8, MODE=0666
#Sharp
SUBSYSTEM==usb, SYSFS{idVendor}==04dd, MODE=0666
#Sony Ericsson
SUBSYSTEM==usb, SYSFS{idVendor}==0fce, MODE=0666
#Toshiba
SUBSYSTEM==usb, SYSFS{idVendor}==0930, MODE=0666
#ZTE
SUBSYSTEM==usb, SYSFS{idVendor}==19D2, MODE=0666
 
Last edited:

sleepytux

Member
Jul 20, 2011
32
3
Really nice script... Work perfect!!! The more easy install as possible...
But some package more are needed so that adb can start:

Code:
pacman -Sy lib32-alsa-lib lib32-openal lib32-libstdc++5 lib32-libxv lib32-ncurses lib32-sdl lib32-zlib swt

And if your adb don't have the right to see your device. You have to kill it and restart with root:

Code:
su
cd /usr/local/android-sdk/platform-tools
./adb kill-server 
./adb start-server 
./adb devices

THX for sharing...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    ** I would really like to hear your results on if the script was successful or not and if you have any errors so that I can try and work out the bugs that the script may have. I am new to Arch Linux and working from a fairly barebones system. I believe I will have most of the dependencies resolved in the script, but 64-bit Linux systems *may* need to have the Multilib repository for this to function properly.


    I wanted to bring my Auto-Installer over to Arch Linux while I am playing with it. It uses the Pacman manager, so as long as you are using that I believe you'll experience no problems installing this.

    Some changes from this one, compared to the Mint/Ubuntu version: The script cannot be executed with SUDO. Don't edit the code and remove the fail safe for this, to try because it'll just cause the script to fail at the end. Just enter the password requests.

    Download Links
    Github, Download link is at the top. Use the command: tar xvfz <filename.tar.gz> to extract this one.

    git clone git://gist.github.com/1254981.git gist-1254981

    Dropbox Script Link

    For safety reasons, I'd suggest taking one of the first two just incase dropbox corrupts the script for some reason.

    Installation Instructions

    This script assumes you know very basic knowledge of the terminal (or GUI equivalent). Download the file you want from above and navigate to the directory that it is and type the following commands (dropbox users substitute andadb.sh with andadbarch.sh:

    Code:
    $ chmod +x andadbarch.sh
    $ ./andadbarch.sh
    
    [COLOR="#FF0000"]This part takes a long time depending on your internet connection.[/COLOR]
    Install the "Android SDK Platform-tools" to gain access to ADB.  
    Also install any other API that you would like at this time.

    You can now test your phone by typing "adb" in terminal while plugged in with USB debugging mode turned on.


    What's Been Done to my System?

    • Eclipse has been installed.
    • Android SDK is installed in /usr/local/android-sdk
    • Android NDK is installed in /usr/local/android-ndk
    • Symlink created for Dalvik Debug Monitor, start it from terminal with "ddms" -- If you run two monitors or it gives you an error the first time you run it type it again and the program will start.
    • Symlink created for Android Debug Monitor. Type "adb" from terminal to see command list.
    • 99-android.rules created automatically and placed into /etc/udev/rules.d directory.


    Version 1.0.4 99-android.rules:

    Code:
    #Acer
    SUBSYSTEM==usb, SYSFS{idVendor}==0502, MODE=0666
    #ASUS
    SUBSYSTEM==usb, SYSFS{idVendor}==0b05, MODE=0666
    #Dell
    SUBSYSTEM==usb, SYSFS{idVendor}==413c, MODE=0666
    #Foxconn
    SUBSYSTEM==usb, SYSFS{idVendor}==0489, MODE=0666
    #Garmin-Asus
    SUBSYSTEM==usb, SYSFS{idVendor}==091E, MODE=0666
    #Google
    SUBSYSTEM==usb, SYSFS{idVendor}==18d1, MODE=0666
    #HTC
    SUBSYSTEM==usb, SYSFS{idVendor}==0bb4, MODE=0666
    #Huawei
    SUBSYSTEM==usb, SYSFS{idVendor}==12d1, MODE=0666
    #K-Touch
    SUBSYSTEM==usb, SYSFS{idVendor}==24e3, MODE=0666
    #KT Tech
    SUBSYSTEM==usb, SYSFS{idVendor}==2116, MODE=0666
    #Kyocera
    SUBSYSTEM==usb, SYSFS{idVendor}==0482, MODE=0666
    #Lenevo
    SUBSYSTEM==usb, SYSFS{idVendor}==17EF, MODE=0666
    #LG
    SUBSYSTEM==usb, SYSFS{idVendor}==1004, MODE=0666
    #Motorola
    SUBSYSTEM==usb, SYSFS{idVendor}==22b8, MODE=0666
    #NEC
    SUBSYSTEM==usb, SYSFS{idVendor}==0409, MODE=0666
    #Nook
    SUBSYSTEM==usb, SYSFS{idVendor}==2080, MODE=0666
    #Nvidia
    SUBSYSTEM==usb, SYSFS{idVendor}==0955, MODE=0666
    #OTGV
    SUBSYSTEM==usb, SYSFS{idVendor}==2257, MODE=0666
    #Pantech
    SUBSYSTEM==usb, SYSFS{idVendor}==10A9, MODE=0666
    #Philips
    SUBSYSTEM==usb, SYSFS{idVendor}==0471, MODE=0666
    #PMC-Sierra
    SUBSYSTEM==usb, SYSFS{idVendor}==04da, MODE=0666
    #Qualcomm
    SUBSYSTEM==usb, SYSFS{idVendor}==05c6, MODE=0666
    #SK Telesys
    SUBSYSTEM==usb, SYSFS{idVendor}==1f53, MODE=0666
    #Samsung
    SUBSYSTEM==usb, SYSFS{idVendor}==04e8, MODE=0666
    #Sharp
    SUBSYSTEM==usb, SYSFS{idVendor}==04dd, MODE=0666
    #Sony Ericsson
    SUBSYSTEM==usb, SYSFS{idVendor}==0fce, MODE=0666
    #Toshiba
    SUBSYSTEM==usb, SYSFS{idVendor}==0930, MODE=0666
    #ZTE
    SUBSYSTEM==usb, SYSFS{idVendor}==19D2, MODE=0666
    2
    Really nice script... Work perfect!!! The more easy install as possible...
    But some package more are needed so that adb can start:

    Code:
    pacman -Sy lib32-alsa-lib lib32-openal lib32-libstdc++5 lib32-libxv lib32-ncurses lib32-sdl lib32-zlib swt

    And if your adb don't have the right to see your device. You have to kill it and restart with root:

    Code:
    su
    cd /usr/local/android-sdk/platform-tools
    ./adb kill-server 
    ./adb start-server 
    ./adb devices

    THX for sharing...