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 wrote:
> My development system: Windows 7 64-bit, 4GB RAM, 2.1 Dual Core
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 wrote:
> Right, but my point is: if you delete the 1
On Fri, Dec 4, 2009 at 5:17 PM, adamphillips12 wrote:
> "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 versi
> 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
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
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 wrote:
> Not working for me. The standalone manager won't connect to the SSL
> url (https://dl-ssl.google.com/android/repository/repository.
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 s
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
> 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:
On Thu, Dec 3, 2009 at 10:35 PM, adamphillips12 wrote:
> "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
> 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
11 matches
Mail list logo
