Android SDK

Google has released the full Honeycomb 3.0 SDK updates, meaning developers can download and begin work with the finalized APIs for Honeycomb.  This comes in preparation for the launch of the Motorola Xoom on Feb. 24 and will let developers check what they've built using the 3.0 SDK preview against the final version before the Honeycomb tablets start to roll out.  If you're an app developer, or just like to keep your SDK current, you can update things through the SDK manager.

It's worth noting that the AOSP source (as well as Motorola's open-source portions) should be released before the Xoom is launched, so be on the lookout for that come Thursday morning if you're a DIY kind of person.  [Android Developers blog]

 

Reader comments

Android Honeycomb 3.0 SDK add-on finalized and available

19 Comments

i dont think you will see cm8 for phones because its a tablet os but now we will see CMN1 (cyanogenmod: nook 1)

I still don't see why you wouldn't be able to put Honeycomb on phones if Android is open source and you can do a little bit of tweaking and stuff.

You could put honeycomb on a phone but I wouldn't recommend it. I have had it on my nook for a while and works great on a tablet but I couldn't see myself using daily on my droid2 since its all touchscreen controls. Plus the controls would either be too small on the screen or if they made them bigger to fit a phone screen would look horrible.

I can see CM8 on a phone in 1 of two ways

First, unmodified. At 800x480, Honeycomb looks nothing like tablet honeycomb, in fact it looks very similar to other stock phone roms.

Second, modified. Can't hit the home button on the touchscreen? Hit your phone home button. Just remap the screen buttons to your phone. Can't be hard.

You might need to launch the SDK manager as Administrator by right clicking on it and click Run as Administrator. Worked for me by doing that. Otherwise, I got your error.

Wasn't it said that the preview 3.0 sdk had phone capabilities and even a "phone friendly" launcher and lockscreen?