I'm having the same issue. I'm behind an authenticated proxy so I
can't install the SDK. I've tried everything.
On Dec 31 2009, 9:13 am, teryz teryzpl...@gmail.com wrote:
I have a problem using AndroidSDKUpdater (revision 4). For the
record I'm under win xp 32-bits, jdk 1.6.
I set up the
I have a problem using Android SDK Updater (revision 4). For the
record I'm under win xp 32-bits, jdk 1.6.
I set up the Force https://... sources to be fetched using http://
This seemed to work fine but as I am behing a (corporate) proxy I also
filled the proxy server and port settings,
Hi,
With this new modular approach of SDK, i would like to move between
development platforms like between linux and windows.
Is it possible to reduce the download size of the android platforms
i.e. 1.6/2.0/2.0.1 etc...
I am sure it is quite possible as mostly only the prebuilt (may be
Android has been active in Korea, I wish it soon!
However, Korea has not said that ...
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group,
Hi,
I have Android 1.5 Platform on my machine.
I just installed the latest version i.e. 2.0.1 using the android-
sdk_r04-windows.zip available online. I am using Eclipse Galileo IDE.
I have few questions on this,
1 Can i switch to the new version by just changing the preference in
the IDE to
Hi,
I had Android 1.5 installed on windows XP with Eclipse Galileo as IDE.
I downloaded the latest Android SDK 2.0.1 from
http://developer.android.com/sdk/index.html
and unzipped to
My question is,
1 Can I switch to the new SDK by pointing in Eclipse IDE in the
preference to the installed dir
actually it's the same.
installing 1.6_r2 wipes the 1.6_r1 folder (which is why you get a lock error
if it fails to do so.
It is completely safe to manually delete the 1.6_r1 folder and then get r2.
Xav
On Sun, Dec 6, 2009 at 10:47 PM, Sekhar sek...@allurefx.com wrote:
Right, but my point is:
This is because your manifest says minSdkVersion=6 but your droid is still
running 2.0 with api 5.
Until all droids have received 2.0.1 you should keep minSdkVersion to 5.
Xav
On Sat, Dec 5, 2009 at 9:17 AM, George Scott bud...@gmail.com wrote:
My development system: Windows 7 64-bit, 4GB
Actually, the original error said that r1 was being moved to a temp
directory (not removed); but I see now it was probably just to handle
errors during r2 install so it can roll back to r1 if necessary. So,
all good - I guess deleting the platforms directory is the best way to
handle this issue
Thanks for this response, I didn't mean to come off as rude but I was
more frustrated than anything, I did some long thinking and approached
my drawables differently, There are redundancies yes but I suppose no
system is going to be perfect stretching over 4 SDKs.
I know it might not seem like
I succeeded the update (even with sdk r3) without having to resort to
snicklefritz ;-)
- Quit eclipse
- Killed adb.exe in Task Manager
- Started SDK Path\SDK Setup.exe
- Ran the update
(some eclipse freezes omitted for cleanliness...)
- restarted eclipse
- everything runs fine!
Cheers,
Yes, I had exactly the same problem last night, with no apparent other
running program blocking the folder renaming. In the end I just quit
Eclipse and deleted the particular 1.6 r1 folder manually in Explorer
(Windows 7 64-bit), after which the update ran without problems.
(Before that,
My development system: Windows 7 64-bit, 4GB RAM, 2.1 Dual Core
notebook
Eclipse development issue:
I've updated the needed bits for Android development with Eclipse for
Java. However, I do not choose to use the emulator, I prefer testing
on my Droid mobile phone.
When I try to Run my
This is what I did, when I came upon the same problem, and it worked
for me (Windows 7 x64).
C:\Users\Public\android-sdk-windows\toolsandroid
Starting Android SDK and AVD Manager
SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for
your
Right, but my point is: if you delete the 1.6 platforms folder, you're
going to lose the r1 - you only get 1.6 r2. I.e., you're basically
wiping out 1.6 and just picking up the latest. May be OK if you don't
need 1.6 r1, but it's not the same as a regular update.
On Dec 5, 1:18 am, blindfold
Grrr I have yet another issue of the block on my home XP machine.
Using the standalone sdk manager, it keeps telling something is
locking the tools dir so it can't install tools r4. But I killed adb,
closed Eclipse, all Explorers... still won't work. Process Explorer
can't find anything
Quitting Eclipse, manually deleting platforms\android-1.6, and
restarting Eclipse to run Android SDK and AVD Manager from its Windows
menu brought back platforms\android-1.6 with what I presume is a full
replacement of the 1.6 folder with the now updated 1.6 content. This
is further proven by the
On Fri, Dec 4, 2009 at 5:17 PM, adamphillips12 adamphillip...@gmail.comwrote:
It was documented like so The SDK version supported by the device,
for example v3. The Android 1.0 SDK is v1, the 1.1 SDK is v2, and the
1.5 SDK is v3., if that was supposed to imply that a device supported
its
Just had this renaming block again on another system, here running
Windows XP SP3. Quitting Eclipse, manually deleting the platforms
\android-1.6 folder, and relaunching Eclipse to run Android SDK and
AVD Manager from its Windows menu again fixed the problem. Looks like
there is something not
On Thu, Dec 3, 2009 at 10:35 PM, adamphillips12 adamphillip...@gmail.comwrote:
The framework now correctly selects application resources in project
folders that use the API Level qualifier. For example, drawable-v4/ is
a folder of drawable resources for API Level 4 (or higher) devices.
This
Yeah, that was the first thing I tried (kill-server), but adb will get
started again automatically, so that doesn't help. I'd also tried
deleting adb.exe from tools\ in the hope it would'nt get started, but
then I can't even bring up the SDK/AVD manager to do the update. Also,
blindfold: deleting
Yeah, that was the first thing I tried (kill-server), but adb will get
started again automatically, so that doesn't help. I'd also tried
deleting adb.exe from tools\ in the hope it would'nt get started, but
then I can't even bring up the SDK/AVD manager to do the update. Also,
blindfold:
Unfortunately, that won't work since the SDK/AVD manager will refer to
the its own stuff (platforms, etc.) regardless of how you start it.
I.e., you can't run the manager from one directory and have it refer
to the platforms in another directory. Looks like the install process
is basically broken
adb isn't run from the 1.6 folder so that should have no impact.
If you're having problem, I would suggest updating to the tools r4 first (or
ADT 0.9.5) and then try 1.6_R2. The new SDK Manager is a better at dealing
with this.
Also, if you have an anti-virus you should temporarily disable it as
Well, if I check the file location for the adb.exe program in Task
Manager, it's showing as from the 1.6 r1 tools/ directory (I have the
SDK set as 1.6 r1 in Eclipse, that's it's launching that - if I change
to 1.5, it loads the adb.exe from 1.5 tools/, but that doesn't help).
And yes, I do have
Not working for me. The standalone manager won't connect to the SSL
url (https://dl-ssl.google.com/android/repository/repository.xml); and
if I make it http, it won't find compatible updates. This is really
frustrating, can't believe such a basic install issue managed to slip
through the cracks.
Sorry Dianne, my reply was intended for public, hit Reply to author by
accident:
It was documented like so The SDK version supported by the device,
for example v3. The Android 1.0 SDK is v1, the 1.1 SDK is v2, and the
1.5 SDK is v3., if that was supposed to imply that a device supported
its most
Sorry for the frustration.
You should get the exact same updates whether you are using the https
or the http link.
R/
On Fri, Dec 4, 2009 at 4:17 PM, Sekhar sek...@allurefx.com wrote:
Not working for me. The standalone manager won't connect to the SSL
url
Grrr I have yet another issue of the block on my home XP machine.
Using the standalone sdk manager, it keeps telling something is
locking the tools dir so it can't install tools r4. But I killed adb,
closed Eclipse, all Explorers... still won't work. Process Explorer
can't find anything using that
The framework now correctly selects application resources in project
folders that use the API Level qualifier. For example, drawable-v4/ is
a folder of drawable resources for API Level 4 (or higher) devices.
This version matching did not work properly and has been fixed.
Did anyone realise this
I'm not able to update 1.6 r1 to 1.6 r2 in Eclipse on Windows, it's
throwing an error A folder failed to be renamed or moved. Looks like
adb.exe that's running is preventing a move to temp. Anyone else
having this problem?
On Dec 3, 3:38 pm, Jason Chen jasonc...@google.com wrote:
Hey, folks.
I'm not able to update 1.6 r1 to 1.6 r2 in Eclipse on Windows, it's
throwing an error A folder failed to be renamed or moved. Looks like
adb.exe that's running is preventing a move to temp. Anyone else
having this problem?
Run adb kill-server, or reboot, and try again. You probably have an
Yes, I had exactly the same problem last night, with no apparent other
running program blocking the folder renaming. In the end I just quit
Eclipse and deleted the particular 1.6 r1 folder manually in Explorer
(Windows 7 64-bit), after which the update ran without problems.
(Before that, the
33 matches
Mail list logo
