Please create an account to participate in the Slashdot moderation system


Forgot your password?
Android Cellphones Handhelds Open Source Programming Software Linux

Google Releases Android 4.1 SDK 58

hypnosec writes "Google has released the full SDK for its latest edition of Android, Jelly Bean, which was unveiled during Google I/O. Google has already released the source code of Jelly Bean earlier. Google announced through a blog post that developers can develop application against the API level 16 using the new Jelly Bean APIs. Developers would be able to develop apps that will run on Nexus 7 tablets. Jelly Bean is touted as one of the best from Google and it promises a smoother and more responsive UI across the system."
This discussion has been archived. No new comments can be posted.

Google Releases Android 4.1 SDK

Comments Filter:
  • Wouldn't it have been traditional for them to make the SDK available before the OS dropped, to make sure there was a base of current apps in place when devices started shipping?

    I can only imagine the SDK was available to certain select developers for months, while the Nexus 7 was in testing and such-like.

    • I think that would have been best, but Google probably wanted to get it to retail well before the new Kindle Fire.

      Also, consider that this device has access to entire Android market ( the Fire is severely limited in comparison) - Google probably felt the existing Market is good enough until devs get things rolling.
      • While the Jelly Bean supposed to be for gadgets that have yet to reach market, hundreds of millions of older Android Devices are already at the hands of the consumers

        My question is - is it hard for average geek to install Jelly Bean on older crop of Android Devices ?

        • I had and old HTC desire which I "upgraded". It ran hotter than ever after and eventually died. I have the Galaxy Nexus which I can use as a hand warmer in the winter after a bit of use. These bits of kit seem to be made for the version they are released with, little more.
        • Well, yes and no. You can't just take the code they've released and put it on your phone, since that lacks a lot of the hardware drivers and such that are needed to make it compatible with each phone. It's possible for developers to get it to work on most phones, but it takes some time. At the moment, pretty much the only phones which you can put a fully functioning Jelly Bean ROM are the Nexus phones. A lot other recent phones have already got people working on JB ROMs, and many of them have beta versions

    • Re: (Score:2, Informative)

      by Anonymous Coward

      This is confusing. The Jelly Bean SDK has been out for a while now (since around Google IO). The "blog" link is wrong (correct url: My dev tools already had API 16 installed and the Google APIs are the only thing that saw any updates (rev 2).

    • The release order changed when Google's need to give certain manufacturers exclusive early access outweighed the community's need to have the SDK prior to the OS release. This isn't that much of an impairment for most developers, and it's a cheap incentive to win over some hardware manufacturers.

      However it is funny how the two closed source mobile operating systems give their developer base early access to their upcoming SDKs.

      • Perhaps they needed to run it past their lawyers to check that Apple hadn't patent if or case statements.

        • If the Oracle case is any indication, the existence of the patent wouldn't stop Google, and the invalidity of the patent wouldn't stop Apple (like it didn't stop Oracle).

          There isn't stopping patent litigation any more than there's stopping street mugging. If you look like something the thug wants, and the thug thinks he can take you, there's gonna be trouble. And in the tech IP world, there are no "safe neighborhoods" except maybe the EU.

    • Wouldn't it have been traditional for them to make the SDK available before the OS dropped, to make sure there was a base of current apps in place when devices started shipping?

      I can only imagine the SDK was available to certain select developers for months, while the Nexus 7 was in testing and such-like.

      One would presume so but my, admittedly non-Android, developer impression is that this was a thoroughly 'Black Project', so the only devs with a 'Need-To-Know' would have been at ASUS. Of interest to me is how much tablet manufacturer and developer uptake occurs now that it is out, not that this is a major issue. I would buy it right now, warts and all, without either occurring, which marks a first in the tablet market to date.

    • Paying horse before the cart before the free people chained up at the back

      The latest version of Android is closed for 6 months unless you pay out the ass, launch a Nexus branded device, or agree to lock people in to Google's services.
      By the time the SDK comes out and the latest version is opened up, the next significant release is already in alpha.

    • by Qwavel ( 733416 )

      Actually, there was a beta of the SDK that was released during the IO conference - so prior to the Nexus 7 becoming available.

      But I do have concern about the general beta quality of all of their stuff (actually I think that Android 4.0.0 was more like alpha).

      I'm pleased that, so far, my Nexus 7 seems to be very solid. Hopefully this means they are starting to focus more on quality.

      • Yeah, this is just rev. 2 of the 4.1 SDK. The title and summary are highly misleading.

      • by ZosX ( 517789 )

        i have a transformer tablet running ics 4.04. It seems solid enough. It is easily as reliable as cyanogen 7 on my phone. the only issue I have had is with apex launcher, which the latest update seems to want to crash and force me to wade through to the applications from the settings menu and close it. Oh well. Really, I've had no complaints. I just wish everything worked. Lots of games for 2.x phones don't want to work. (Gameloft...looking at YOU) Tegra 3 should play everything on the market flawlessly, but

    • by Reapman ( 740286 )

      I've had the SDK installed since Google I/O - this is just a "final" revision to it. Really, not that big of a news item. I've gotten tons of updates on my phone that appear to be JB related - which is probably just the dev's targeting this release and testing it still works (And fixing what's required, which was probably pretty minimal)

    • Wouldn't it have been traditional for them to make the SDK available before the OS dropped, to make sure there was a base of current apps in place when devices started shipping?

      The base of current apps was already there.

      A 4.1 Android phone can run any app 1.5 and onward.

  • Interesting. The first link is blocked by my work filter as a "malicious site". Normally I can click thru the blocked stuff but this one won't let me. I think it thinks that site is hosting malware.

    • by na1led ( 1030470 )
      Worked fine on ForeFront TMG Proxy filter.
    • Probably has to do with this crap on Parity News:

      Your experience on this site, will be improved by allowing cookies - see details

      Social media Facebook, Twitter and other social websites need to know who you are to work properly.

      Analytics We anonymously measure your use of this website to improve your experience.

      Allow for all sites

      Allow cookies

      It's pretty vanilla social media crap.

  • by Anonymous Coward

    What kind of article is this? The SDK was ALREADY RELEASED at I/O.

  • by devleopard ( 317515 ) on Thursday July 19, 2012 @07:36PM (#40705785) Homepage

    That thing is horribly slow.

    • Launch speed is still slow, but there is now Intel support for the emulator so it runs faster. Also released today is rev. 2 of the "Intel Hardware Accelerated Execution Manager" which may include some performance enhancements. []

      • by 7o9 ( 608315 )
        I do not think there is a Jelly Bean version of the Intel_x86 system image yet. The newest seems to be an Android 4.0.4 version. Hopefully there will be a JB 4.1.1 system image soon as working with the Intel_x86 emulator is very fast.
    • by ZosX ( 517789 )

      There's not much they can do, short of writing a better ARM VM. You want it to emulate ARM so you can test native code.

    • by ZosX ( 517789 )

      I meant to add that you could just get a device and use that to test your code. That would be how most devs do it. I think google might still sell a dev phone to you if you ask nicely.

    • That's been way faster for a while. Try the Intel x86 ones (which are very fast), or the GPU acceleration option for the ARM ones.


    My droid hasn't even self-upgraded to Cherry Pop Tart With Icing, yet. >:-(

  • That the 4.1 release is out is all good and well, but I'm still waiting for the Swedish wordlist for my 4.0 Galaxy Nexus. Much can be said about Apple, but at least the think about the customers in a way Google apparently never will.

Karl's version of Parkinson's Law: Work expands to exceed the time alloted it.