Slashdot Mirror


Android 1.5 SDK Is Released

RadiusK writes "Starting today, developers can get an early look at the SDK for the next version of the Android platform. Version 1.5 introduces APIs for features such as soft keyboards, home screen widgets, live folders, and speech recognition. At the developer site, you can download the early-look Android 1.5 SDK, read important information about upgrading your Eclipse plugin and existing projects, and learn about what's new and improved in Android 1.5."

31 of 135 comments (clear)

  1. a2dp !!!! Yay!!! Video Recording!!! by 8282now · · Score: 4, Informative

    # Camera & Gallery

            * Video recording
            * Video playback (MPEG-4 & 3GP formats)

    # Bluetooth

            * Stereo Bluetooth support (A2DP and AVCRP profiles)
            * Auto-pairing
            * Improved handsfree experience

  2. I'm curious by SlashDotDotDot · · Score: 2

    Anyone here written code for Android? How do you like it?

    --
    /...
    1. Re:I'm curious by john_anderson_ii · · Score: 2, Informative

      I've done some doodling, nothing serious. The Eclipse plugin with emulator integration is very nice to work with.

      --
      Be Safe! Sleep with a Marine. Semper Fi!
    2. Re:I'm curious by kTag · · Score: 4, Informative

      I did a project for the Android Challenge.
      I'm working with a Mac and Eclipse is not the most user friendly IDE on this platform.
      The process is smooth enough, forget about Linux, it's all Java based. I do Java stuff 10h a day so I felt right at home. It takes a couple of days to feel right about the suggested class design. Appart from that, I felt it was all very standard stuff, nothing really amazing, persistence is nice enough with sqlite but that's about it. You won't find any major revolution in there, it's very close to a simple standard Java application. So I didn't do more code since (it was based on SDK 1.1 if I remember correctly) and since I didn't even win the right to carry on with the Challenge, I left everything as it was (I got good technical marks, but the profitability of the idea wasn't there...). You see, if you didn't win somehow you didn't have access to the new SDK, unlike all the other lucky bastards. So why bother...
      Now I've got to get back to the Web SDK of the iPhone and the CSS transformations, these are rocking my days (actually more my nights).

    3. Re:I'm curious by IamTheRealMike · · Score: 4, Interesting

      I wrote an app which is now on the market. The good:

      • Java. OK, actually I hate Java. But I'd hate Objective-C a lot more. Implementing a simple crash reporter around my core logic was about 10 lines of Java code, and it works every time. Implementing the same thing in C++ or Objective-C would be .... non-trivial. No bother with heap corruptions, etc.

      • The whole design of activities and intents is quite well thought out. It seemed overly complicated at first but now I appreciate it a lot more. It's also very flexible, you aren't forced to use the infrastructure if you don't want to.

      • Really rich APIs. Background services, maps, multimedia, power management, package management, notifications .... even a face recognizer!

      • The market. I see a lot of people rag on the market and the comments system. Maybe I'm biased because my app has almost universally good reviews, but it's really nice to get that instant feedback about how you're doing. It's my experience that G1 owners (and there are apparently quite a lot) are ridiculously lenient. My app is extremely simple and could use a lot of extra features, yet I consistently get really flattering comments about it. It's actually been a long time since I wrote and launched an app directly to Normal People, and it's been a refreshing experience. Publishing my app to the market was a breeze - it's instant gratification. No approval process.

      ... and the bad ...

      • Java.
      • Documentation is rather rough in places. Precious few example apps. Non-existent HIG.
      • The SDK GUI editor is very basic (I believe it's much improved in 1.5, need to check it out).

      ... and the ugly ...

      • Bugs. The 1.1 release improved things a lot, but as a user I still the contact list system in particular to be distressingly buggy. It's by no means unusably buggy, but I expect a much more robust experience from my phone than I would a desktop OS.
      • HTTP APIs. There's two, the standard Java API and then apache httpclient. Unfortunately httpclient is version 4.x, not the more mature and well known 3.x. HttpClient 4.x has almost no useful documentation and doesn't support some features that 3.x did. PAIN.

      All that said, I like writing apps for Android. Eclipse is decent. Java is decent. The distribution process is decent. And it's apparently improving pretty fast.

    4. Re:I'm curious by caluml · · Score: 3, Interesting

      Java. OK, actually I hate Java.

      So you hate Java despite it allowing you to do precisely, easily, and compactly what you wanted to do? *

      People are weird.

      * I'm guessing you had a traumatic experience with an applet in 1998 that took 20 seconds to start up, and hung your browser. Get over it.

    5. Re:I'm curious by goose-incarnated · · Score: 2, Funny

      Java. OK, actually I hate Java.

      So you hate Java despite it allowing you to do precisely, easily, and compactly what you wanted to do? * People are weird. * I'm guessing you had a traumatic experience with an applet in 1998 that took 20 seconds to start up, and hung your browser. Get over it.

      Hey I agree with you - just because it will do exactly what I want it to do if I twist my head like *this* and dislocate my shoulder like *that* and leap through flaming hoops, isn't a reason to hate it. FWIW, I expect x86 assembly to do exactly what I want it to as well ;-)

      --
      I'm a minority race. Save your vitriol for white people.
  3. but where's my motivation? by sverdrup · · Score: 3, Interesting

    I'm hoping the API will eventually include some kind of anti-piracy options. I wish this version took some steps in that direction, but doesn't look it's going to happen anytime soon. I think the Android market is going to be huge, but until there's some kind of download protection for Android apps, I've got to stick to developing for the iPhone.

    1. Re:but where's my motivation? by h4rr4r · · Score: 4, Insightful

      Then I am sure the people who own Android phones thank you. DRM is not something they want, you can keep that stuff for the mac fans.

    2. Re:but where's my motivation? by sverdrup · · Score: 2, Insightful

      That might be the case for now, with bleeding-edge early adopters making up a big portion of Android's userbase. But the huge selection of apps for the iPhone came when developers realized it was the next gold rush. I think what you'll see on Android is a ton of apps with the DRM built into them, free apps that you have to pay to unlock.

    3. Re:but where's my motivation? by sverdrup · · Score: 2, Insightful

      I suppose that's the tradeoff. Android's openness lets you program cooler stuff, but shifts the burden of protecting your work to the developer.

    4. Re:but where's my motivation? by AuMatar · · Score: 2, Interesting

      And then you'll see the open sourcers step in and clone each and every one of those apps. People don't want DRM, and the idea will ultimately fail on any open phone.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    5. Re:but where's my motivation? by mjwx · · Score: 2, Interesting

      What a load of bullshit. The userbase of both phones are a majority non technical, with a small minority of technical users.

      Android will end up like this. But for the moment the GP is correct.

      iPhone users are non-technical users, Android users are technical users.

      Google is deliberately targeting technical users first so that they can learn the about the OS and find bugs without the customer becoming frustrated with the bugs thus causing negative press, this is their MO which google use will most stuff they develop in house. They also have a somewhat ulterior motive for targeting tech and phone enthusiasts first, these are the people that average people will ask for advice and help. By having a large supply of ready trained techs who can help the mundanes out with their android phone google is positioning Android so that it can have relatively few problems whist providing a lagre feature set.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
  4. Absolutely Love It by MediaStreams · · Score: 5, Informative

    Picking up Android development was as easy as it could be.

    Just downloaded Eclipse and installed the Android plugin. Everything is just standard Java that everyone already is familiar with. Standard OpenGL for the graphics stuff.

    Tons of well documented example code and documentation.

    The best part has been the people from Google so far. They are the most helpful and bright employees I've ever encountered or dealt with doing development support.

    The only thing that has been an occasional pain has been there were some major changes from the pre-1.0 Android SDK that lost of old code was written for. Sometimes when looking for an example of a certain API feature you will get tripped up looking at old code. This is getting less and less of a problem as time moves forward, but there are still Android dev books that come from ancient versions of the Android APIs.

     

    1. Re:Absolutely Love It by GNUbuntu · · Score: 2, Informative

      All the APIs are based off of a stripped down version of Java so if you use their APIs you are constricted to that. With root access you can write programs in a language like C/C++, or any language you can compile to native code, and compile for ARM and run it, but that's not supported obviously.

  5. Re:Anyone seen any android phones ? by KBlommel · · Score: 2, Interesting

    Currently in the US there's only the G1 from T-Mobile. I'm currently on Sprint and I got very excited when Sprint said they were going to be coming out with an Android based phone this year, only later to read that they feel the Android platform isn't ready yet.

    Sprint will be the first provider with the Palm Pre though, which I think looks amazing. I'm hoping it gets a strong developer base for applications, because that's what is going to decide whether the phone is great or a flop.

  6. Re:The big question is: by iserlohn · · Score: 4, Informative

    In a word, yes.

    I have a G1. It works well considering it is 1st generation hardware/software. No A2DP, but same situation as iPhone (3.0/Cupcake). Other than that, software-wise the widgets are smooth, and you can actually run services in the background. Some of the applications need improving, like the mail client needs IMAP IDLE support, etc.. but it's getting there. You can get a custom cupcake build for the G1 now which fixes a lot of those problems.

    Hardware-wise, the G1 is not as pretty, but the upcoming devices should give the iPhone a run for its money. The really good thing about it though is that it's got the right number of real buttons, which make navigation a lot more manageable.

    Talking about the N800, OS2008 is great. Nokia has been doing a lot for mobile Linux and I plan on upgrading my trusty ole 770 running OS2008 to whatever device they have for Maemo 5.

  7. That's nice... by pdragon04 · · Score: 5, Insightful

    ...now how about getting some more phones that can actually use it?

  8. Re:C API yet? by gbjbaanb · · Score: 2, Insightful

    I keep hearing a lot of people ask this, especially from Symbian devs who can't see how their image processing code would even work on java.

    Seeing as the underlying OS is all C/C++ it really beats me why they don't expose the 'environment' to C coders too. Then we'd see some fancy fast applications on Android that might make other phone manufacturers look on with envy.

    There again, if they released a C API, you'd be able to run ruby/python and perl code on it too!

  9. Re:The big question is: by Hurricane78 · · Score: 4, Interesting

    No PIM suite on the Nokia one? All Nokia phones here an germany have PIM, SyncML, and tons of features that no iPhone ever had. The series 60 and series 80 phones from Nokia are pretty much a real OS. With everything that you would expect from a computer with such a limited physical interface.

    I guess I will never get, why people like a phone that is already technologically outdated and still overpriced, and adds even more annoyances to the package (like not being able to even input some important characters, being locked-down, and having the display turn into a smudgy piece of shit after 5 seconds of usage)...
    Are looks and the name Apple really that important to you? Or is it, that the other phones that they offer in the USA are even worse?

    I mean, I'd love to make a business out of importing European and Japanese phones into the US market. There's no reason you should be that limited, that you think, the iPhone is great...

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
  10. Asking for a title on a comment is idiotic /. by greentshirt · · Score: 3, Insightful

    Seems someone at Google didn't fully realize that their low fanfare and subtle product roll out system wouldn't translate well to consumer electronics. I was very excited to hear about Android in a Wired article last year and I was pleased to see it's just around the corner. But in my opinion the launch was terrible. There was little coverage in mainstream media, I didn't see any commercials or marketing of any kind. They should have waited till they had more carriers on board, more cell phone / electronics manufacturers on board and launched with a huge marketing campaign. I would argue that Google has a more marketable IP than Apple does (almost everyone uses something Google related and most people have a generally positive view on Google), and if Android was launched properly it would have easily gone head to head with the iPhone (particularily if it wasn't rushed out and maintained all initially stated functionality).

    1. Re:Asking for a title on a comment is idiotic /. by Cyberax · · Score: 2, Interesting

      Arguably, Android G1 was not really ready for widespread use. It has a lot of rough edges and device itself (I own it) is not very well polished.

    2. Re:Asking for a title on a comment is idiotic /. by pimpimpim · · Score: 2, Interesting

      Also many of the applications are still close but no cigar. I don't care too much, though, this thing has way more potential than any of the other platforms, and there is still a lot of room for sales next to the iphone.

      --
      molmod.com - computing tips from a molecular modeling
  11. Basic functionality by blincoln · · Score: 2, Interesting

    Hey Google - have you fixed the mail reader so I can view messages composed by someone using Pine (or one of its derivatives) instead of just seeing "null" where the body should be?

    All of the flash is nice, but getting the basics working would be better. This issue is supposedly fixed in the codebase, but I don't see anything in the 1.5 release notes indicating that it's included.

    --
    "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    1. Re:Basic functionality by greentshirt · · Score: 5, Funny

      I still think it's incredible that there is no Google toolbar for Chrome.

  12. Android 1.5 Highlights by Anonymous Coward · · Score: 4, Informative

    Android 1.5 Highlights

    April 2009

    The Android 1.5 platform introduces many new features for users and developers. The list below provides an overview of the changes.
    User interface refinements

    * System-wide:
    o Refinement of all core UI elements
    o Animated window transitions (off by default)
    o Accelerometer-based application rotations
    * UI polish for:
    o In-call experience
    o Contacts, Call log, and Favorites
    o SMS & MMS
    o Browser
    o Gmail
    o Calendar
    o Email
    o Camera & Gallery
    o Application management

    Performance improvements

    * Faster Camera start-up and image capture
    * Much faster acquisition of GPS location (powered by SUPL AGPS)
    * Smoother page scrolling in Browser
    * Speedier GMail conversation list scrolling

    New features

    * On-screen soft keyboard
    o Works in both portrait and landscape orientation
    o Support for user installation of 3rd party keyboards
    o User dictionary for custom words
    * Home screen
    o Widgets
    + Bundled home screen widgets include: analog clock, calendar, music player, picture frame, and search
    o Live folders
    * Camera & Gallery
    o Video recording
    o Video playback (MPEG-4 & 3GP formats)
    * Bluetooth
    o Stereo Bluetooth support (A2DP and AVCRP profiles)
    o Auto-pairing
    o Improved handsfree experience
    * Browser
    o Updated with latest Webkit browser & Squirrelfish Javascript engines
    o Copy 'n paste in browser
    o Search within a page
    o User-selectable text-encoding
    o UI changes include:
    + Unified Go and Search box

  13. Re:C API yet? by josath · · Score: 4, Insightful

    The problem is that mobile phone apps pretty much have to be sandboxed, and that's a lot harder to do with C/C++ than it is with something like Java. The tools available on modern PC's for sandboxing applications don't even work all that well most of the time (see Vista). Now imagine that instead of a full-powered PC with all sorts of extensions and opcodes and so on, you're running on a much more limited platform. (sidenote: technically Android isn't pure Java, they've created their own bytecode, so they aren't beholden to Sun's iron grasp)

    --
    sig? uhh, umm, ok
  14. Pretentious Assertion by SuperKendall · · Score: 2, Informative

    People with Android phones, shockingly, buy them because they work well and get on with their lives.

    That's why I bought my iPhone. That's why everyone I know bought an iPhone. Because we wanted something that Just Works and so many phones before, had Just Not Worked Worth a Damn.

    They aren't lifestyle choices. They aren't something that fills a hole in their sad and empty lives.

    Well I don't know how empty your life is, but it's certainly sad that instead of enjoying your phone you see fit to bring down other phones you fear people perceive as "better". I myself like the Android platform a lot, I just see it's not as mature yet.

    Carried in the most visible way everywhere in public places hoping everyone will notice just how 'special' they are for what phone they own

    Honestly, who does that? I have never seen a person just carrying one around to display. They are usually tucked away in purses or pockets - just like other phone.

    Used in the most annoyingly over manner in public places with a desperate and sad hope that people will ask them about their phone

    So because iPhone owners actually USE the phones they carry they are arrogant? Seems like you are the one proclaiming how much better a person you are because of the brand of phone you own. I personally don't care what phone other people have, or if they know what I have.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  15. Bluetooth API's by Qwavel · · Score: 3, Interesting

    From the changelog it would appear that there are still no bluetooth API's. This makes it pretty much the only phone available that doesn't have this. Too bad.

  16. Re:C API yet? by gbjbaanb · · Score: 2, Informative

    cool. But Android doesn't use JVM bytecode, they developed their own, called Dalvik, to get round Sun's licencing.

  17. Re:The big question is: by Zero__Kelvin · · Score: 2, Insightful

    "Feature and usability-wise is it getting close to the iPhone?"

    If by "getting close to" you mean "better than", then yes ;-)

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun