ubuntu下sdk Manager没有Options选项如果没有创建改文件

最新推荐文章于 2025-06-16 21:42:09 发布

原创最新推荐文章于 2025-06-16 21:42:09 发布 · 3.5k 阅读

0 ·

CC 4.0 BY-SA版权

android 同时被 2 个专栏收录

33 篇文章

订阅专栏

linux

10 篇文章

订阅专栏

在Ubuntu环境下，若SDK Manager未显示Options选项，可能是缺少配置文件导致。本文介绍了如何在LINUX系统中设置Android SDK Manager的代理设置，通过2种解答探讨解决方案。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Android SDK Manager Proxy Settings in LINUX

up vote 3 down vote favorite

I am trying to install the Android SDK, in Ubuntu, behind my work firewall and am getting 'failed to connect to dl-ssl.google.com' messages. This is a known problem but every solution I see involves proxy settings and selecting the 'force http' option. It appears that this is straightforward in windows, however I'd like to know how to do the same in LINUX. I can set the eclipse proxy settings but I don't think this gets used by the android sdk manager. Is there a config file somewhere?

Thanks in advance.

Marc

android ubuntu proxy android-sdk-2.3

share | improve this question

edited Jun 23 '12 at 9:33

Dirk Jäckel
1,560 12 28

asked May 17 '12 at 10:42

user1400716
216 2 20

Please accept one of the answers if it helped you, so this question does not show up as unanswered anymore.– Dirk Jäckel Jun 23 '12 at 9:34

add comment

2 Answers

active oldest votes

up vote 13 down vote accepted

The solution was to setup a local proxy to perform authentication and create the file ~/.android/androidtool.cfg to redirect android to the local proxy as follows.

### Settings for Android Tool
#Tue Jun 12 01:34:55 PDT 2012
http.proxyPort=3128
sdkman.monitor.density=108
http.proxyHost=127.0.0.1
sdkman.show.update.only=true
sdkman.ask.adb.restart=false
sdkman.force.http=true
sdkman.show.updateonly=true

This file may already exist with entries such as

http.proxyPort=
http.proxyHost=127.0.0.1\:3128

For me, this did not work until I changed it to the form shown above:

http.proxyPort=3128
http.proxyHost=127.0.0.1

share | improve this answer

edited Aug 21 '12 at 0:57

Community ♦
1

answered Jun 19 '12 at 13:54

user1400716
216 2 20

This fixed it for me - the proxy port was the issue. – Shirkrin Aug 24 '12 at 9:35

My proxy requires authentication as well, but just supplying http.proxyPort and http.proxyHost did the trick; the Android tooling asked for credentials to get through that proxy. – mthmulders Jan 24 at 8:55