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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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" <[email protected]> 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 [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
