From ArchWiki
Revision as of 04:04, 12 July 2013 by Granted (talk | contribs)
Jump to: navigation, search

I'll leave this here until I get enough time to put the changes in the wiki page: GermainZ (talk) 18:45, 4 May 2013 (UTC)

Let root run the Android SDK Manager?

If the SDK is installed via pacman, it is a system wide installation, so the configuration of it should also be done by root, shouldn't it (sudo android etc.)? This way, no dirty chmod -R stuff in system installations must be done. If one wants user configurability of the Android SDK, she should just install it locally in their home dir, imho. --Epinephrine (talk) 14:25, 13 June 2013 (UTC)


I found installing the Android SDK within Eclipse is much more pleasant, especially when your developing alone. No need for AUR and chmod orgies.

Open up Eclipse, go to Help - Install new Software - Add...


and choose "Developer Tools"

In my case everything was installed to

~/Development/android-sdks (of course the installer lets you choose any directory that suits you best)

After that, close eclipse,

cd ~/Development/android-sdks/tools and fire up the Android SDK Manager ./android sdk

to get additional libs and the latest updates (don't miss this step)

You can now create a new Android project in Eclipse and everything works fine!

Goodboy (talk) 14:46, 6 July 2013 (UTC)

Set up android as root and no chmod needed

I have tried both approaches mentioned above. I find the AUR version more convenient.

To run android as root you may have to edit your sudoers file.

sudo visudo

and add DISPLAY to your environment. Something like this:

Defaults env_keep += "DISPLAY HOME"

Now you should be able to run android and set it up as you wish. From here on any account can run the eclipse environment and use the android SDK you have set up as root.

Granted (talk) 01:45, 12 July 2013 (UTC)