[android-developers] Re: Updates to the Android SDK
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 Force https://... sources to be fetched using http:// This seemed to work fine but as I am behing a (corporate)proxyI also filled theproxyserver and port settings, however thisproxyrequires a user/password and I can't find a way to give Android Updater aproxy authentication as no authentication box pops up when I try downloading updates and I have a response code: 407 for URL:http://dl-ssl.google.com/android/repository/repository.xml; when refreshing sources. If someone can help... Teryz. On 4 déc, 23:27, David Müller dmuvis...@googlemail.com wrote: I succeeded the update (even withsdkr3) without having to resort to snicklefritz ;-) - Quit eclipse - Killed adb.exe in Task Manager - Started SDKPath\SDKSetup.exe - Ran the update (some eclipse freezes omitted for cleanliness...) - restarted eclipse - everything runs fine! Cheers, David -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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, however this proxy requires a user/password and I can't find a way to give Android Updater a proxy authentication as no authentication box pops up when I try downloading updates and I have a response code: 407 for URL: http://dl-ssl.google.com/android/repository/repository.xml; when refreshing sources. If someone can help... Teryz. On 4 déc, 23:27, David Müller dmuvis...@googlemail.com wrote: 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, David -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 rebuilt on development environment) and tools section of android platforms are dependent on platforms. thanks red On Dec 4, 4:38 am, Jason Chen jasonc...@google.com wrote: Hey, folks. Earlier today, we released updates to several different components in the Android SDK. Xav announced these updates via the Android Developers blog:http://android-developers.blogspot.com/2009/12/android-sdk-updates.html. If you want to follow the blog via Twitter, you can now do so viahttp://twitter.com/androiddev. In addition to the new tools and platforms, there's one other important change that I wanted to point out. We've added additional clarification to the docs about android:maxSdkVersion and what effects it might have on your app if you use it. You can see these details here:http://developer.android.com/guide/topics/manifest/uses-sdk-element.h... Best, -Jason -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 the installed dir android-sdk-windows? 2 Doe the new SDK version has Google Maps API built in that? Thanks, Arun On Dec 6, 11:55 am, Adrian Romanelli adrian.o.romane...@gmail.com wrote: 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 platfo rm. C:\Users\Public\android-sdk-windows\toolsdir ..\swt.jar /s Volume in drive C has no label. Volume Serial Number is F484-7812 Directory of C:\Users\Public\android-sdk-windows\tools\lib\x86 12/04/2009 03:26 PM 1,584,454 swt.jar 1 File(s) 1,584,454 bytes Directory of C:\Users\Public\android-sdk-windows\tools\lib\x86_64 12/04/2009 03:26 PM 1,658,174 swt.jar 1 File(s) 1,658,174 bytes Total Files Listed: 2 File(s) 3,242,628 bytes 0 Dir(s) 238,457,712,640 bytes free C:\Users\Public\android-sdk-windows\toolsset ANDROID_SWT=C:\Users \Public\android-sdk-windows\tools\lib\x86_64 C:\Users\Public\android-sdk-windows\toolsandroid Starting Android SDK and AVD Manager No command line parameters provided, launching UI. See 'android --help' for operations from the command line. On Dec 4, 3:10 pm, Raphael r...@android.com wrote: For all of those who have the issue of 1.6_r2 not installing under Windows: that's because Eclipse is locking the folder. The solution is to close Eclipse and run the $SDK\tools\android.bat script directly. Then 1.6_r2 will install correctly. HTH R/ -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 i.e. android-sdk-windows? 2 Does the new SDK version has Google Maps API in-built in it? Thanks, Arun On Dec 7, 11:41 am, Sekhar sek...@allurefx.com wrote: 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 right now then. But I hope Google fixes this so regular update works and we don't need to resort to hacks. On Dec 7, 11:27 am, Xavier Ducrohet x...@android.com wrote: 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: 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 seeingwithso...@gmail.com wrote: 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 fact that another update check did not list 1.6, so I think my workaround for the file lock works just fine, and I used it on both Windows 7 64-bit and Windows XP without further issues. On Dec 4, 6:01 pm, Sekhar sek...@allurefx.com wrote: 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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? On Dec 3, 11:11 pm, Mark Murphy mmur...@commonsware.com wrote: 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 adb daemon process in memory that is tying up adb.exe. -- Mark Murphy (a Commons Guy)http://commonsware.com Android App Developer Books:http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs cr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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: 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 seeingwithso...@gmail.com wrote: 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 fact that another update check did not list 1.6, so I think my workaround for the file lock works just fine, and I used it on both Windows 7 64-bit and Windows XP without further issues. On Dec 4, 6:01 pm, Sekhar sek...@allurefx.com wrote: 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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? On Dec 3, 11:11 pm, Mark Murphy mmur...@commonsware.com wrote: 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 adb daemon process in memory that is tying up adb.exe. -- Mark Murphy (a Commons Guy)http://commonsware.com Android App Developer Books:http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 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 application in the Eclipse IDE it shows an error of ERROR: Application requires API version 6. Device API version is 5 (Android 2.0) Also in the Android Device Chooser dialog there is a red X in the Target column. Is this something to do with the USB drivers? If so, I've already tried pointing the Device Manager applet to pickup any new drivers from C:\android-sdk-windows\usb_driver on my system, where they reside. Further ideas are welcomed and would be most appreciated. I'm a new developer and am really looking forward to the possibilities with the Android platform. -- 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, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 right now then. But I hope Google fixes this so regular update works and we don't need to resort to hacks. On Dec 7, 11:27 am, Xavier Ducrohet x...@android.com wrote: 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: 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 seeingwithso...@gmail.com wrote: 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 fact that another update check did not list 1.6, so I think my workaround for the file lock works just fine, and I used it on both Windows 7 64-bit and Windows XP without further issues. On Dec 4, 6:01 pm, Sekhar sek...@allurefx.com wrote: 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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? On Dec 3, 11:11 pm, Mark Murphy mmur...@commonsware.com wrote: 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 adb daemon process in memory that is tying up adb.exe. -- Mark Murphy (a Commons Guy)http://commonsware.com Android App Developer Books:http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs cr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 much but having a detailed response like this makes a lot more sense than just a single sentence in the new features list. It helps to know how you guys are thinking about things. Anyway, from my extensive testing to get to where I am, I did uncover many bugs, some I knew, some are new (to me), so now I agree with your stance to take the plunge and fix it once :) Otherwise I can see how the problem would of just got worse and worse. At least the behaviour will be consistent now :) Thanks Dianne. On Dec 6, 4:37 am, Dianne Hackborn hack...@android.com wrote: 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 most recent sdk version and perhaps older versions (in terms of the resource system), then the documentation itself could probably have been made more clear. All the wording and the examples suggest the implication that a device has one and only one SDK version it identifies with, e.g. 1.5 identifies only with v3, if not present it uses default (given no other qualifiers), otherwise it would of read The SDK versions..., the 's' has quite some significance. Obviously the new or higher clause can not follow this single SDK definition, it is a behavioural change, not merely a fix of the documented functionality. I can certainly make the documentation more clear, but the 2.0.1 behavior is entirely the intended behavior, and is consistent with other uses of the API version such as in minSdkVersion and targetSdkVersion. Also the previous behavior is simply -not- useful. For example, the typical reason one to use this is to select different resources to match changes in newer versions of the platform. The two main examples to date: - As of v4, there are new configurations for screens. If you use these, you want to also use -v4 to ensure that older versions of the platform (which don't know about this differentiation) don't accidentally pick up your resources, for example, for small screens. - As of v5, there is a change in the standard look of some things. You can use a -v5 (actually -v6 because of another bug in 2.0) variation to switch to different variations of your graphics or colors to match the new UI. In both cases, with the old pre-2.0.1 behavior, each time there is a new platform update it breaks your use of this. So when 2.0 appeared, you needed to add duplicate -v6 resources for the first cases, or else the platform wouldn't see your resources that are using -v4 to prevent older platforms from seeing them. And that would happen again for each following platform update. The new behavior in 2.0.1 is completely how we want this to work, it caused a ton of problems for developers that it didn't work as intended previously, and now it is fixed. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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, David -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 update had failed both with the $ android method and when launching Android SDK and AVD Manager from Eclipse | Windows.) I've solved the same thing in the same way. The message about disabling your anti-virus software is somewhat misleading. In desperation I moved the 1.6 r1 folder to another location on my disk - and not in the same sub directory tree either. The install of 1.r r2 then succeeded. Now I have a 1.6 emulated device and this shows up in the SDK / AVD manager. Once I'd done the platform move, there was a big red X against the 1.6 device. My guess is that it is the SDK/AVD manager that has a lock on the 1.6 folder David Blythman -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 application in the Eclipse IDE it shows an error of ERROR: Application requires API version 6. Device API version is 5 (Android 2.0) Also in the Android Device Chooser dialog there is a red X in the Target column. Is this something to do with the USB drivers? If so, I've already tried pointing the Device Manager applet to pickup any new drivers from C:\android-sdk-windows\usb_driver on my system, where they reside. Further ideas are welcomed and would be most appreciated. I'm a new developer and am really looking forward to the possibilities with the Android platform. -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 platfo rm. C:\Users\Public\android-sdk-windows\toolsdir ..\swt.jar /s Volume in drive C has no label. Volume Serial Number is F484-7812 Directory of C:\Users\Public\android-sdk-windows\tools\lib\x86 12/04/2009 03:26 PM 1,584,454 swt.jar 1 File(s) 1,584,454 bytes Directory of C:\Users\Public\android-sdk-windows\tools\lib\x86_64 12/04/2009 03:26 PM 1,658,174 swt.jar 1 File(s) 1,658,174 bytes Total Files Listed: 2 File(s) 3,242,628 bytes 0 Dir(s) 238,457,712,640 bytes free C:\Users\Public\android-sdk-windows\toolsset ANDROID_SWT=C:\Users \Public\android-sdk-windows\tools\lib\x86_64 C:\Users\Public\android-sdk-windows\toolsandroid Starting Android SDK and AVD Manager No command line parameters provided, launching UI. See 'android --help' for operations from the command line. On Dec 4, 3:10 pm, Raphael r...@android.com wrote: For all of those who have the issue of 1.6_r2 not installing under Windows: that's because Eclipse is locking the folder. The solution is to close Eclipse and run the $SDK\tools\android.bat script directly. Then 1.6_r2 will install correctly. HTH R/ -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 seeingwithso...@gmail.com wrote: 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 fact that another update check did not list 1.6, so I think my workaround for the file lock works just fine, and I used it on both Windows 7 64-bit and Windows XP without further issues. On Dec 4, 6:01 pm, Sekhar sek...@allurefx.com wrote: 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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? On Dec 3, 11:11 pm, Mark Murphy mmur...@commonsware.com wrote: 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 adb daemon process in memory that is tying up adb.exe. -- Mark Murphy (a Commons Guy)http://commonsware.com Android App Developer Books:http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 handle. Frustrating :-( I ran into that in the previous update round. I wound up copying $SDK\tools to another peer directory (e.g., $SDK\snicklefritz), pointing all my env vars to the new directory, and launching AVD Manager from there. AVD Manager was locking the tools dir, so by running a separate copy, tools was able to then be updated. I then repointed my PATH and stuff back to the regular tools\ dir and nuked my spare copy. -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 fact that another update check did not list 1.6, so I think my workaround for the file lock works just fine, and I used it on both Windows 7 64-bit and Windows XP without further issues. On Dec 4, 6:01 pm, Sekhar sek...@allurefx.com wrote: 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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? On Dec 3, 11:11 pm, Mark Murphy mmur...@commonsware.com wrote: 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 adb daemon process in memory that is tying up adb.exe. -- Mark Murphy (a Commons Guy)http://commonsware.com Android App Developer Books:http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 most recent sdk version and perhaps older versions (in terms of the resource system), then the documentation itself could probably have been made more clear. All the wording and the examples suggest the implication that a device has one and only one SDK version it identifies with, e.g. 1.5 identifies only with v3, if not present it uses default (given no other qualifiers), otherwise it would of read The SDK versions..., the 's' has quite some significance. Obviously the new or higher clause can not follow this single SDK definition, it is a behavioural change, not merely a fix of the documented functionality. I can certainly make the documentation more clear, but the 2.0.1 behavior is entirely the intended behavior, and is consistent with other uses of the API version such as in minSdkVersion and targetSdkVersion. Also the previous behavior is simply -not- useful. For example, the typical reason one to use this is to select different resources to match changes in newer versions of the platform. The two main examples to date: - As of v4, there are new configurations for screens. If you use these, you want to also use -v4 to ensure that older versions of the platform (which don't know about this differentiation) don't accidentally pick up your resources, for example, for small screens. - As of v5, there is a change in the standard look of some things. You can use a -v5 (actually -v6 because of another bug in 2.0) variation to switch to different variations of your graphics or colors to match the new UI. In both cases, with the old pre-2.0.1 behavior, each time there is a new platform update it breaks your use of this. So when 2.0 appeared, you needed to add duplicate -v6 resources for the first cases, or else the platform wouldn't see your resources that are using -v4 to prevent older platforms from seeing them. And that would happen again for each following platform update. The new behavior in 2.0.1 is completely how we want this to work, it caused a ton of problems for developers that it didn't work as intended previously, and now it is fixed. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 quite right with the update package. On Dec 4, 8:40 am, blindfold seeingwithso...@gmail.com wrote: 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 update had failed both with the $ android method and when launching Android SDK and AVD Manager from Eclipse | Windows.) On Dec 4, 8:05 am, Sekhar sek...@allurefx.com wrote: 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? -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 version matching did not work properly and has been fixed. Did anyone realise this breaks all backwards compatibility on this qualifier? It's the inverse of how it currently works and makes it a terrible pain to now support 1.5 to 2.0.1 No it doesn't. For someone to selectively target a single sdk that is not the most current but support the sdks on other side of it, they now always have to create layout/, layout-vX/, layout-vX+1/, with vX+1/ being nothing but a duplication of resources in layout/, that are in both layout/ and vX/ No, it fixes this bug that was in 2.0. While the old method, layout/ is simply your default catch all and you single out specific sdks for specific resources with a simple layout- vX. I think you are misunderstanding the change. The change is to make it work how it was actually documented, and not the horribly broken way it was before. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? On Dec 3, 11:11 pm, Mark Murphy mmur...@commonsware.com wrote: 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 adb daemon process in memory that is tying up adb.exe. -- Mark Murphy (a Commons Guy)http://commonsware.com Android App Developer Books:http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? Here's a procedure I used for grabbing the previous ADT update on Vista 32-bit, where $SDK is the directory you installed the SDK into: 1. Copied $SDK\tools to $SDK\snicklefritz 2. Changed the relevant environment variables (e.g., PATH) to point to $SDK\snicklefritz instead of $SDK\tools 3. Started up the SDK/AVD Manager from the $SDK\snicklefritz copy 4. Ran the update 5. Changed the environment variables back to point to $SDK\tools 6. After confirming the new $SDK\tools seemed happy, deleted $SDK\snicklefritz That was for a slightly different problem than the one you're reporting, so I'm not sure if this will actually help you, but I just like writing snicklefritz. ;-) -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 and needs to be fixed by Google. Or I'm missing something here (really hope that's the case). On Dec 4, 9:06 am, Mark Murphy mmur...@commonsware.com wrote: 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 the platforms\android-1.6 is really not a solution because you're just avoiding dealing with the 1.6 update. Bottom line, I don't believe there's still a solution to updating from 1.6 r1 to 1.6 r2. This is on Vista 64 bit. Anyone? Here's a procedure I used for grabbing the previous ADT update on Vista 32-bit, where $SDK is the directory you installed the SDK into: 1. Copied $SDK\tools to $SDK\snicklefritz 2. Changed the relevant environment variables (e.g., PATH) to point to $SDK\snicklefritz instead of $SDK\tools 3. Started up the SDK/AVD Manager from the $SDK\snicklefritz copy 4. Ran the update 5. Changed the environment variables back to point to $SDK\tools 6. After confirming the new $SDK\tools seemed happy, deleted $SDK\snicklefritz That was for a slightly different problem than the one you're reporting, so I'm not sure if this will actually help you, but I just like writing snicklefritz. ;-) -- Mark Murphy (a Commons Guy)http://commonsware.com Android App Developer Books:http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 it will prevent installation by locking folder that needs to be removed. Xav On Thu, Dec 3, 2009 at 11:05 PM, Sekhar sek...@allurefx.com wrote: 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. Earlier today, we released updates to several different components in the Android SDK. Xav announced these updates via the Android Developers blog: http://android-developers.blogspot.com/2009/12/android-sdk-updates.html. If you want to follow the blog via Twitter, you can now do so viahttp:// twitter.com/androiddev. In addition to the new tools and platforms, there's one other important change that I wanted to point out. We've added additional clarification to the docs about android:maxSdkVersion and what effects it might have on your app if you use it. You can see these details here: http://developer.android.com/guide/topics/manifest/uses-sdk-element.h... Best, -Jason -- 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, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 the tools at r4 already and I did disable antivirus (AVG). But I'm just not able to get past the error. :( On Dec 4, 1:50 pm, Xavier Ducrohet x...@android.com wrote: 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 it will prevent installation by locking folder that needs to be removed. Xav On Thu, Dec 3, 2009 at 11:05 PM, Sekhar sek...@allurefx.com wrote: 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. Earlier today, we released updates to several different components in the Android SDK. Xav announced these updates via the Android Developers blog: http://android-developers.blogspot.com/2009/12/android-sdk-updates.html. If you want to follow the blog via Twitter, you can now do so viahttp:// twitter.com/androiddev. In addition to the new tools and platforms, there's one other important change that I wanted to point out. We've added additional clarification to the docs about android:maxSdkVersion and what effects it might have on your app if you use it. You can see these details here: http://developer.android.com/guide/topics/manifest/uses-sdk-element.h... Best, -Jason -- 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, send email to android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs cr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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. On Dec 4, 3:10 pm, Raphael r...@android.com wrote: For all of those who have the issue of 1.6_r2 not installing under Windows: that's because Eclipse is locking the folder. The solution is to close Eclipse and run the $SDK\tools\android.bat script directly. Then 1.6_r2 will install correctly. HTH R/ -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 recent sdk version and perhaps older versions (in terms of the resource system), then the documentation itself could probably have been made more clear. All the wording and the examples suggest the implication that a device has one and only one SDK version it identifies with, e.g. 1.5 identifies only with v3, if not present it uses default (given no other qualifiers), otherwise it would of read The SDK versions..., the 's' has quite some significance. Obviously the new or higher clause can not follow this single SDK definition, it is a behavioural change, not merely a fix of the documented functionality. -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 (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. -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 handle. Frustrating :-( -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 breaks all backwards compatibility on this qualifier? It's the inverse of how it currently works and makes it a terrible pain to now support 1.5 to 2.0.1 For someone to selectively target a single sdk that is not the most current but support the sdks on other side of it, they now always have to create layout/, layout-vX/, layout-vX+1/, with vX+1/ being nothing but a duplication of resources in layout/, that are in both layout/ and vX/ If they wanted to selectively target two sdks, they have to create layout/, layout-vX/, layout-vY/ AND layout-vY+1 again duplicating resources now against layout/, vX and vY/ etc While the old method, layout/ is simply your default catch all and you single out specific sdks for specific resources with a simple layout- vX. I don't understand why this was ever classified as a bug, can someone please explain the opposing logic to this. I would assume the purpose of a API Level qualifier would be to selectively access specific sdks, yet this change is the direct opposite of this usefulness, would it not have been far more appropriate to keep the previous method in tact but simply expand the functionality of the API Level qualifier to accept ranges? On Dec 4, 10:38 am, Jason Chen jasonc...@google.com wrote: Hey, folks. Earlier today, we released updates to several different components in the Android SDK. Xav announced these updates via the Android Developers blog:http://android-developers.blogspot.com/2009/12/android-sdk-updates.html. If you want to follow the blog via Twitter, you can now do so viahttp://twitter.com/androiddev. In addition to the new tools and platforms, there's one other important change that I wanted to point out. We've added additional clarification to the docs about android:maxSdkVersion and what effects it might have on your app if you use it. You can see these details here:http://developer.android.com/guide/topics/manifest/uses-sdk-element.h... Best, -Jason -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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. Earlier today, we released updates to several different components in the Android SDK. Xav announced these updates via the Android Developers blog:http://android-developers.blogspot.com/2009/12/android-sdk-updates.html. If you want to follow the blog via Twitter, you can now do so viahttp://twitter.com/androiddev. In addition to the new tools and platforms, there's one other important change that I wanted to point out. We've added additional clarification to the docs about android:maxSdkVersion and what effects it might have on your app if you use it. You can see these details here:http://developer.android.com/guide/topics/manifest/uses-sdk-element.h... Best, -Jason -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Updates to the Android SDK
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 adb daemon process in memory that is tying up adb.exe. -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Updates to the Android SDK
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 update had failed both with the $ android method and when launching Android SDK and AVD Manager from Eclipse | Windows.) On Dec 4, 8:05 am, Sekhar sek...@allurefx.com wrote: 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? -- 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, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
