Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Android Google Open Source

Google Releases Android 4.1 Source Code 211

Unlike previous releases, where months passed between Google announcing a new version and the code being released, Google has made good on their promise to release the source code to Jelly Bean in record time. Unfortunately, the gitweb instance on kernel.org is still down so you'll have to download the entire thing to take a peek. Hopefully the Cyanogenmod team will find time to start on a community enhanced version soon.

This discussion has been archived. No new comments can be posted.

Google Releases Android 4.1 Source Code

Comments Filter:
  • No kidding (Score:5, Interesting)

    by Jethro ( 14165 ) on Monday July 09, 2012 @11:00PM (#40598915) Homepage

    CM9 just took sooo long. In fact the final release isn't out yet.

    I just couldn't resist and put Jellybean on my Galaxy Nexus. But CyanogenMod still has a few features that are not incorporated into plain Android, nor are there apps for them. Not that I could find anyway. For example I want the battery in the status bar to show a percent number (there are apps that add that, but IN ADDITION to the regular battery), and I /love/ the Volume-Button-Long-Press-Skips-Tracks. Very very very useful while jogging. Oh and the power widgets in the pull-down, way better than the Power Control Widget.

    CM9 took so long because they had to start from scratch. They are saying that CM10 should not be NEARLY as big a deal, so here's hoping!

  • by geminidomino ( 614729 ) on Monday July 09, 2012 @11:21PM (#40599033) Journal

    It's not just companies. Even FOSS projects are doing it.
    I ran GIMP 2.8 for a whole 20 minutes before I uninstalled and put 2.6 back.

    It's like there's some sort of computer programmer virus that makes you make idiotic un-usability decisions going around (pretty sure Ubuntu was patient zero)

  • by Auroch ( 1403671 ) on Monday July 09, 2012 @11:22PM (#40599039)

    Thanks! That's good to know. I haven't actually experimented much with Cyanogen yet because i've never felt to need to install it on my Nexus One. (I'm trying to hold out until the rumored five new Nexus phones this fall.) But i'm definitely going to be looking into it once i get my Nexus 7.

    You're missing out. Using vanilla android is THAT much better than most skinned versions, and using Cyanogen is THAT much better than vanilla. It's essentially ALL the options and customization you didn't realize you needed, but once you've got it, you'll never go back to vanilla.

  • Re:Yet (Score:5, Interesting)

    by DeathFromSomewhere ( 940915 ) on Tuesday July 10, 2012 @12:03AM (#40599213)
    Tell that to the Nexus S owners who had to wait over 6 months for 4.0 to land on their phones. Owning a Nexus phone is not a guarantee of timely updates.
  • by Anonymous Coward on Tuesday July 10, 2012 @12:51AM (#40599421)

    Your points are valid from your perspective...

    My perspective, on the other hand:

    The multitasking button has become probably my most used, and I'm happy they made a dedicated button for it. Next most used is Home, and that's increased with Jelly Bean making long-press home bring up Google Now with a swipe up (which actually makes more sense to me than that being multitasking). Back is used enough as well, of course. I almost never use the menu button on the bottom any more, though. The only apps that I find any use for that is... well... Facebook, but I've given up on even dealing with the Facebook app... and... honestly, I'm perfectly happy without the menu or the search buttons dedicated on the bottom. It took a little getting used to, but I don't miss those buttons at all any more...

    Essentially, the new button configuration works better for me than the old button configurations ever did. I can understand it being more of a hassle for some people. That's essentially Google's thing though: the phone manufacturers can put whatever buttons they want on there and leave whatever buttons they don't off (hence CM9 allows you to fill the damn thing up with all 5 if you really want). The manufacturers are probably going to go to the ones that seem the most logical based on potential sales to put on there. Samsung thought it made sense to keep the menu button that people like yourself are so used to, so they did. And there you have it, you proved them right and bought the S3 for that reason. Maybe they'll do that with the S4 and beyond, and you can still keep your menu button and "logical button scheme". I'll stick to the new scheme that makes more sense to me. We'll both be happy (and I understand that's a big "if they go that way...").

  • Re:Yet (Score:4, Interesting)

    by oakgrove ( 845019 ) on Tuesday July 10, 2012 @01:28AM (#40599565)
    Wasn't that the CDMA Nexus S though? For anybody that doesn't know, not only do you need to have a Nexus device to be assured of updates, that Nexus device needs to not be CDMA. Even the Galaxy Nexus from Verizon is unsupported by AOSP.
  • by phantomfive ( 622387 ) on Tuesday July 10, 2012 @01:33AM (#40599589) Journal

    It is fairly clear that one of the greatest problems with Android is with version fragmentation

    Is it really? As a mobile developer, I find that it's a simple problem to deal with by just coding to an older API. I haven't found any problem with it not being backwards compatible, and the older APIs are good enough for most things.

    A much bigger problem I've had is with different hardware platforms being different, with sometimes bizarre issues like the Kyocera Milano having a clock that goes backwards from time to time. This is a problem on iPhone too, but since there are fewer iphone platforms, it's easier...

  • by Hast ( 24833 ) on Tuesday July 10, 2012 @04:47AM (#40600229)

    It's also worth mentioning that Google has done some work to help developers with compatability. There was a talk about it on IO this year as well: Google I/O 2012 - Multi-Versioning Android User Interfaces (http://www.youtube.com/watch?v=amZM8oZBgfk).

This file will self-destruct in five minutes.

Working...