Slashdot Mirror


Android Ice Cream Sandwich SDK Released

Hitting the front page for the first time, ttong writes "The highly anticipated Android 4.0 (codenamed Ice Cream Sandwich) has been released and finally brings the features of 3.x Honeycomb to smaller devices. Some of the highlights include: a revamped UI, a much faster browser, face unlock, a vastly improved camera app, improved task switching, streaming voice recognition, Wi-Fi Direct, and Bluetooth Health Device Profile. ... The API level is 14, download the new SDK here." calc noted that the source code has yet to be released (Google account required) except to legally required GPL components. Supposedly progress is being made toward getting AOSP back online: "We're working on it and we're making good progress, but we're not ready to announce any additional details yet." How many of the new features will remain proprietary and tied to Google services remains to be seen.

309 comments

  1. Ice Cream Sandwich? Really? by snowgirl · · Score: 1, Interesting

    I heard my bother talking on the phone about this awhile ago... It seems like one of the most weird and random names to call something. I get it, code names are cool, and people readily recognize them. But you sound absolutely silly for doing so. Who wants to go to a meeting and tell their bosses that they're thinking of: "Replacing Honeycomb with Ice Cream Sandwich on all our android devices"?

    Use the damn version numbers, PLEASE.

    --
    WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    1. Re:Ice Cream Sandwich? Really? by Tukz · · Score: 1

      Google have used types of desserts as naming scheme for Android since 1.5 (April 2009), and I can't see a problem with it.

      No one is forcing you to use the names, however.
      If you need to have a meeting with your bosses, feel free to use the actual version number, which is 4.0 for Ice cream Sandwich.

      A lot of software use naming schemes, it's very common in OSS community.

      --
      - Don't do what I do, it's probably not healthy nor safe. -
    2. Re:Ice Cream Sandwich? Really? by TimeOut42 · · Score: 4, Informative

      They do use version numbers; Gingerbread = Android 2.x, Honeycomb = Android 3.x and Ice Cream Sandwich = 4.x This way satisfy the enthusiasts craving for a sweet desert and the professional's need to not sound like an enthusiast.

    3. Re:Ice Cream Sandwich? Really? by i_ate_god · · Score: 2

      wow you're boring.

      I just finished the cassowary version and now I'm working on the dingo version. Yes we use those terms in meetings, with bosses, and it gets a good chuckle. It's far more entertaining than version numbers.

      --
      I'm god, but it's a bit of a drag really...
    4. Re:Ice Cream Sandwich? Really? by TarMil · · Score: 5, Informative

      Gingerbread = 2.3 more precisely. 2.1 is Eclair and 2.2 is Froyo.

    5. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      Yes. They should use serious code names like Gutsy Gibbon, Intrepid Ibex, etc.

    6. Re:Ice Cream Sandwich? Really? by grommit · · Score: 0

      Who wants to go to a meeting and tell their bosses that they're thinking of: "Replacing Honeycomb with Ice Cream Sandwich on all our android devices"?

      Just about anybody that isn't a complete and total prude.

    7. Re:Ice Cream Sandwich? Really? by darjen · · Score: 1

      I told my wife that Google names all their operating systems after desserts in order of the alphabet. She seriously thought I was kidding and was trying to make her sound gullible. For the record she does use a Droid Eris. She just doesn't really care what operating system is on it.

    8. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      At least naming them after deserts is better than the vulgar and juvenile sexual terms many FOSS projects use (gimp, kuntlik, fetchmail, jizm, I'm looking at you!)

    9. Re:Ice Cream Sandwich? Really? by RyuuzakiTetsuya · · Score: 3, Interesting

      I worked on a project with another Doctor Who fan and we were perfectly fine with upgrading Jon Pertwee to Tom Baker.

      I'm glad I got laid off before I had to go from Sylvester McCoy to Paul McGann. Although if we made it to version 10, we had the idea of naming 10.5 "Handy."

      --
      Non impediti ratione cogitationus.
    10. Re:Ice Cream Sandwich? Really? by mwvdlee · · Score: 1

      Because it's easier to refer to a name than a version number.
      Primarily these code names are used only internally but as companies have become more public about internal ongoings, so have the code names.
      To the public it's still 4.0. I've never seen any non-developer-targetted ad mention anything besides "Android X.Y" for the Android OS.
      Not to mention having an excuse for themed release parties.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    11. Re:Ice Cream Sandwich? Really? by arkhan_jg · · Score: 1

      You can say 'upgrading from version 2.3 to 4.0' in that meeting with your boss if you prefer. People often prefer the code-names as they're easier to remember the distinguishing features; gingerbread and froyo mean more to me than 2.3.4 and 2.2.1, but whatever works for you.

      Personally, I was really looking forward to the nexus prime as the 'flagship' for ice cream sandwich (or 4.0!) - but the hardware looks pretty unimpressive compared to the galaxy S II, the new Razr or even something older like the optimus 3D.

      Hopefully it goes AOSP soon so it can get back-ported by cyanogenmod to existing phones in something like a reasonable time frame - if we wait for the OEMs and then the carriers, it'll be many months if it happens at all.

      Though I'm keeping my eye on the LG LU6400 - could be a good phone, and may launch with ice cream sandwich.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    12. Re:Ice Cream Sandwich? Really? by arkhan_jg · · Score: 1

      Oops, that should be the LG LU6200.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    13. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      What's wrong with fetchmail?

    14. Re:Ice Cream Sandwich? Really? by L4t3r4lu5 · · Score: 1

      Read her sig, and wonder how you fell for the troll.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    15. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0, Funny

      he confused it with feltchmale. Common problem amongst those who are obsessed with sucking cum out of a man's ass.

    16. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      And they're working through the alphabet, which is another way to tell versions without numbers.

      Cupcake
      Donut
      Eclair
      Froyo
      Gingerbread
      Honeycomb
      Ice Cream Sandwich

      I wonder what dessert starts with J?

      I'm more of an iOS fan myself, but it's a fun and cute naming convention. Pity most Android devices can't be easily upgraded. :-)

    17. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      As usual, I blame Microsoft.

      Chicago, Memphis, Whistler, Longhorn...

    18. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      They're just using a letter sequence, the same as Ubuntu does.

      Eclair
      Froyo
      Gingerbread
      Honeycomb
      Ice cream sandwich

      I agree that "Ice cream sandwich" is a bit of a silly name, but it is part of a logical sequence.

      And kinda like Ubuntu, everyone will now start second-guessing what the next code name will be.

    19. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 1

      Jello of course !

    20. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 1
    21. Re:Ice Cream Sandwich? Really? by RyuuzakiTetsuya · · Score: 1

      Using an ice cream sandwich as a phone is still less ridiculous than side talking on an NGage.

      --
      Non impediti ratione cogitationus.
    22. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 1

      Jellybean actually. Jello is trademarked, obviously.

    23. Re:Ice Cream Sandwich? Really? by Canazza · · Score: 1

      Jam RollyPolly

      --
      It pays to be obvious, especially if you have a reputation for being subtle.
    24. Re:Ice Cream Sandwich? Really? by snowgirl · · Score: 1

      Because it's easier to refer to a name than a version number.
      Primarily these code names are used only internally but as companies have become more public about internal ongoings, so have the code names.
      To the public it's still 4.0. I've never seen any non-developer-targetted ad mention anything besides "Android X.Y" for the Android OS.
      Not to mention having an excuse for themed release parties.

      Ah, this makes a lot of sense. I'll have to defer to non-developer targetted ads, since I haven't really looked at Android except through enthusiast who use the code names.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    25. Re:Ice Cream Sandwich? Really? by snowgirl · · Score: 1

      gingerbread and froyo mean more to me than 2.3.4 and 2.2.1

      Except as a non-enthusiast, I don't know which comes first. "The first initial of the code name tells you which order they came in, A-Z." Huh, I hadn't noticed that at all, and no one else is likely to notice without being told, excepting of course for the random insights that people make from time to time.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    26. Re:Ice Cream Sandwich? Really? by voss · · Score: 3, Informative

      Actually its not random. The Android releases are being done in alphabetical order.

      2.2 Froyo
      2.3 Gingerbread
      3.0 Honeycomb
      4.0 Ice cream sandwich

      get it?

    27. Re:Ice Cream Sandwich? Really? by snowgirl · · Score: 1

      They're just using a letter sequence, the same as Ubuntu does.

      Eclair
      Froyo
      Gingerbread
      Honeycomb
      Ice cream sandwich

      I agree that "Ice cream sandwich" is a bit of a silly name, but it is part of a logical sequence.

      And kinda like Ubuntu, everyone will now start second-guessing what the next code name will be.

      I noticed this once I was clued in above. I don't really think Ubuntu code names are any better (or worse), honestly...

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    28. Re:Ice Cream Sandwich? Really? by NatasRevol · · Score: 1

      But not matching sequential versions. i.e. F=2, G=3, H=4

      --
      There are two types of people in the world: Those who crave closure
    29. Re:Ice Cream Sandwich? Really? by snowgirl · · Score: 1

      he confused it with feltchmale. Common problem amongst those who are obsessed with sucking cum out of a man's ass.

      Ahem, the proper term is "santorum"...

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    30. Re:Ice Cream Sandwich? Really? by poofmeisterp · · Score: 1

      he confused it with feltchmale. Common problem amongst those who are obsessed with sucking cum out of a man's ass.

      Ahem, the proper term is "santorum"...

      Only in a "sanitorium" is it so.

      *choke*

    31. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      Every software company uses names like this - internal names for Windows follow (or used to anyway) city names, Apple uses cats as the naming convention for releases of OSX and Ubuntu uses a two name convention of Adjective-Animal for their releases. Personally I find it more fun...

    32. Re:Ice Cream Sandwich? Really? by ttong · · Score: 1

      You mean Jell-O. Jello is a german band with hits such as The race and Oh Yeah.

    33. Re:Ice Cream Sandwich? Really? by dswskinner · · Score: 1

      Not sure if i am expecting a whoosh or not, but the group is called Yello.

    34. Re:Ice Cream Sandwich? Really? by Bill,+Shooter+of+Bul · · Score: 1

      There was an awesome speed metal band that went by the name of Green Jello, but they were forced to change it to Green Jelly after Kraft foods the maker of Jell-O complained.

      http://en.wikipedia.org/wiki/Green_Jell%C3%BF

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    35. Re:Ice Cream Sandwich? Really? by oakgrove · · Score: 1

      That article is a hit piece. The video is of a site loaded down with flash. Flash is enabled on the Nexus S and not on the iPhone. The site could be buggy in other ways too. This anecdote means nothing as the Nexus S outperforms the iPhone 4 on many other sites.

      --
      The soylentnews experiment has been a dismal failure.
    36. Re:Ice Cream Sandwich? Really? by RussellSHarris · · Score: 1

      For "J" they'll buck the trend of desserts and name it "John Jacob Jingleheimer Schmidt".

    37. Re:Ice Cream Sandwich? Really? by quenda · · Score: 1

      At least naming them after deserts is better than the vulgar and juvenile sexual terms many FOSS projects use (gimp, kuntlik, fetchmail, jizm, I'm looking at you!)

      Onanistic Ocelot?

    38. Re:Ice Cream Sandwich? Really? by AvitarX · · Score: 1

      Jelly

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    39. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      They were not speed metal, and it was more like a comedy metal band. Did you even read the link you supplied?

    40. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      I wonder what they come up with for 4.x or 5.0, I hope its better than Jelly Bean.

    41. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 1

      Who wants to go to a meeting and tell their bosses that they're thinking of: "Replacing Honeycomb with Ice Cream Sandwich on all our android devices"?

      Just about anybody that isn't a complete and total prude.

      ppl with good jobs.

    42. Re:Ice Cream Sandwich? Really? by phoenix_rizzen · · Score: 1

      No, it's easier to refer to a number than a name, especially when comparing two versions.

      Without knowing about the alphabet trick, how does one know that "honeycomb" is better than "eclair"? Or that "froyo" came before "gingerbread"? Or that "some-other-weird-name" is worse than "ice cream sandwich"?

      At least with version numbers, you know which came first, which came later, and which (in theory) should be better. 1.5 1.6 2.0 2.1 2.2 2.3 3.0 4.0

      Names may be easier to remember for some. But relationships between items is *much* simpler for everyone using numbers.

    43. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      Which one?

      The thisismynext.com review & video?
      The flyosity.com agreeing with it?
      The youtube videos showing it?
      The androidforums.com sections giving information on how to reduce the lagginess?

      Yeah, they're all hit pieces - trying to show the truth.

    44. Re:Ice Cream Sandwich? Really? by johnthorensen · · Score: 1

      On a serious note, I'm betting on "Jujube" or "Jelly Roll", or even "Jelly Donut".

    45. Re:Ice Cream Sandwich? Really? by oakgrove · · Score: 1

      Which one?

      The thisismynext.com review & video? The flyosity.com agreeing with it?

      Yes.

      The youtube videos showing it?

      The androidforums.com sections giving information on how to reduce the lagginess?

      For every youtube video you can show me of a Nexus S lagging behind an iPhone, I can show you 10 of the Nexus being faster than the iPhone.

      You fanboys are pitiful.

      --
      The soylentnews experiment has been a dismal failure.
    46. Re:Ice Cream Sandwich? Really? by Cute+Fuzzy+Bunny · · Score: 0

      Without knowing that number trick, how would one know that "2" comes after "1" or that "3" is better than "2"?

    47. Re:Ice Cream Sandwich? Really? by PwnzerDragoon · · Score: 2

      Because most people learn that in kindergarten, whereas aside from Android code names are typically more or less random?

    48. Re:Ice Cream Sandwich? Really? by PCM2 · · Score: 1

      Without knowing about the alphabet trick, how does one know that "honeycomb" is better than "eclair"? Or that "froyo" came before "gingerbread"?

      Or that "aardvark" comes before "cat" in the dictionary? That's why kids should watch Sesame Street -- so they can be computing geniuses.

      --
      Breakfast served all day!
    49. Re:Ice Cream Sandwich? Really? by Bucky24 · · Score: 0

      Don't most people learn the alphabet in kindergarten as well?

      --
      All the world's a CPU, and all the men and women merely AI agents
    50. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      1.5 Cupcake
      1.6 Donut
      2.0 Eclair
      2.2 Froyo
      2.3 Gingerbread
      3.0 Honeycomb
      4.0 Ice Cream Sandwich
      ?.? Jellybean

    51. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      You fanboys are pitiful.

      Never go full retard.

      Ha!

    52. Re:Ice Cream Sandwich? Really? by amRadioHed · · Score: 1

      Why would they do that? They are used for every release, not just the ones with major version number changes.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    53. Re:Ice Cream Sandwich? Really? by crazycheetah · · Score: 1

      Actually. The first two versions of Android weren't named, so A and B were never done. The third version was Cupcake. Then Donut for the fourth and Eclair for the fifth. So Froyo = 6, Gingerbread = 7, Honeycomb = 8, and Ice cream sandwhich = 9.

      You can see this reflected in CyanogenMod's version numbers, where Gingerbread = CM7 (the current) and Ice Cream Sandwhich = CM9 (there has been no CM8 at this point, because CyanogenMod was never made for Honeycomb due to lack of source).

      Android's version numbers of 2.2, 2.3, 3.0, and 4.0 are on a different version scheme, where 2.0 was a major step up from those of the 1.x ilk (through Donut, as 2.0-2.1 was Eclair). Honeycomb, 3.0 was then a major step up from the 2.x ilk (through Gingerbread), and 4.0 is a major step up from Honeycomb (and Gingerbread as is the case for phones only). Donut was then just a minor step up from Cupcake and Gingerbread was just a minor step up from Froyo, which was a minor step up from Eclair.

      Make sense?

    54. Re:Ice Cream Sandwich? Really? by niktemadur · · Score: 2

      Working up the ladder, non-copyrighted names: K - Key Lime Pie, L - Lollipop, M - Meringue, N - Napoleon, O - Orange Sherbet, P - Profiterole, Q - Quince or Quiche, R - Rice Pudding, S - Shortcake, T- Tiramisu, can't think of satisfactory "U" terms, "Upside Down Pineapple Cake" is too much of a... err... mouthful.

      --
      Lil' Thindime, lilting a lacrimose lament, krashes the kwaint konfines of Kokonino Kounty
    55. Re:Ice Cream Sandwich? Really? by mjwx · · Score: 1

      wow you're boring.

      I just finished the cassowary version and now I'm working on the dingo version. Yes we use those terms in meetings, with bosses, and it gets a good chuckle. It's far more entertaining than version numbers.

      +1

      Code names provide more human friendly reference to a project or product with different versions or iterations.

      Version numbers computationally convenient, but a bugger for humans to associate with other things. So in general conversation about Android I tend to use its code name (Froyo, Cupcake, Ice Cream Sandwich) because its easier for humans to associate the code name to it's feature set or current installed version then it is to associate "2.2".

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    56. Re:Ice Cream Sandwich? Really? by Anonymous Coward · · Score: 0

      Pull the stick from your ass.

    57. Re:Ice Cream Sandwich? Really? by PwnzerDragoon · · Score: 1

      Yes. What does that have to do with pattern recognition in software code names?

      If you're not aware that Google is naming them alphabetically, it looks like they're just picking random dessert names.

    58. Re:Ice Cream Sandwich? Really? by Meski · · Score: 1

      She uses a phone named after the Greek god of strife and discord, and thought you were kidding about desserts? Perhaps they'll make a mistake, and name one after a desert. Nullabor, anyone?

    59. Re:Ice Cream Sandwich? Really? by mwvdlee · · Score: 1

      For people who need to refer to different versions of the code numerous times each day (i.e. the developers), a code name isn't random at all; it's just much more eaily pronounced name without any risk of confusion.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    60. Re:Ice Cream Sandwich? Really? by BrokenHalo · · Score: 1

      Hmmm. I would suggest that the Nullarbor isn't really a desert. It is a plain, but of course that's not really the same thing. As it happens, I drove across it last summer, and the vegetation was quite lush, especially by comparison with the "real" Australian deserts such as the Simpson or Gibson. Oh, and while I'm being a pedantic prick, Eris was a goddess.

    61. Re:Ice Cream Sandwich? Really? by PwnzerDragoon · · Score: 1

      True enough. I wasn't knocking code names; I was just pointing out that unless you're familiar with Android, it may not be obvious its code names follow a pattern.

  2. That's cool, but my one grip still by skeletor935 · · Score: 0

    is the miserable battery life. My droid Incredible goes barely a day and a half with little to no good smartphone usage. If I use the internet or video at all the battery is gone in less than a day. I even have all the default auto-running programs deleted. I will probably go back to iphone after this just because of its incredible battery life. I had the 3g and it was amazing.

    1. Re:That's cool, but my one grip still by daid303 · · Score: 1

      Might be related to your droid, my HTC Legend gets about a week of "idle" time. A bit less with CyanogenMod instead of the stock firmware (not sure why...)

    2. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0

      sure, mr.fanboy. because iphone does more than one day of heavy usage now. probably in your magic iphony land.

    3. Re:That's cool, but my one grip still by ArcherB · · Score: 4, Interesting

      is the miserable battery life. My droid Incredible goes barely a day and a half with little to no good smartphone usage. If I use the internet or video at all the battery is gone in less than a day. I even have all the default auto-running programs deleted. I will probably go back to iphone after this just because of its incredible battery life. I had the 3g and it was amazing.

      I hear that complaint a lot, and even made it myself when I had an Evo4G. However, I found that if you disable all the features that are not present in the iPhone, like 4G, live wallpaper, widgets, flash, live weather, etc, I think you'll find the battery life to be comparable to what you had on your iPhone. My Evo3D is as good or better than my buddy's iPhone4 by simply turning off live wallpaper and 4G.

      --
      There is no "I disagree" mod for a reason. Flamebait, Troll, and Overrated are not substitutes.
    4. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0

      What apps you have installed, running, and their configuration as well as things like WiFi & 4G settings all affect battery life when idle. Something as simple as checking for new email less frequently can have a big impact on battery life.

      And don't forget to turn of GPS & Bluetooth when you don't need them!

    5. Re:That's cool, but my one grip still by lunatic1969 · · Score: 2

      That's been a huge issue for me too. I went and got the extended battery for the Evo 4G which worked wonderfully, although it made the phone heavy as a brick. I've found a surprising solution though. Recently upgraded to the Galaxy S2 (Or whatever the hell you call the thing) and there wasn't an extended battery available yet that I could find. So, against my better judgement I tried JuiceDefender. It works. It works *well*. Basically it shuts down the sensors when they aren't in use, and turns them on when you unlock your phone to use it. Worried about email? No problem, it turns on the data every so often to allow apps to synch that need to synch. I'm actually not sure why a similar strategy isn't just a default part of the operating system.

    6. Re:That's cool, but my one grip still by lunatic1969 · · Score: 1

      My reasoning has always been, if you have to turn off all the features to make the phone usable, why have the features at all? And turning them on only when I want to use them is too much hassle if I have to do it manually. I'm an American, I want it now and I want someone else to do it for me, damnit. Fortunately I found a workable solution (battery saving application).

    7. Re:That's cool, but my one grip still by Gaygirlie · · Score: 1

      ICS should improve battery-life quite a bit. As it says in the TFA they're now requiring all devices with ICS to do hardware-accelerated graphics, and as you likely know a GPU is a lot better at handling such tasks and at shifting around large amounts of data in memory than a regular CPU is, so the more you actually use the device the larger the difference in battery-life should be. Obviously it won't affect idle standby-life, but from your comment I understood that that wasn't the problem anyways.

    8. Re:That's cool, but my one grip still by Lifyre · · Score: 1

      So you would rather not have them at all?

      --
      I'll meet you at the intersection of "Should be" and "Reality"
    9. Re:That's cool, but my one grip still by lunatic1969 · · Score: 1

      So you would rather not have them at all?

      The device has to be usable. If the battery consumption is such that I have to be within reach of a power supply every few hours, then no - I don't want the features. I'd rather have the battery life.

    10. Re:That's cool, but my one grip still by danabnormal · · Score: 1

      Do you really need Bluetooth on all the time? How about a data connection? I tend not to look at the web in my sleep or if I'm gonna be in a long meeting, so I turn that radio off. Its a swipe and a press to turn them back on, it really isn't a hassle at all and the difference it makes isn't small.

    11. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0
    12. Re:That's cool, but my one grip still by lunatic1969 · · Score: 1

      I don't need it on all the time. I also know that realistically there's no way I'm going to remember to turn things on and off on my phone when I need them. My brain doesn't work that way at this stage of the game. That's why I'm glad there's an app for that.

    13. Re:That's cool, but my one grip still by Gaygirlie · · Score: 1

      ICS still doesn't improve lagginess.

      http://flyosity.com/iphone/androids-touch-responsiveness-is-terrible.php

      That may be, but after having owned a 10-inch Honeycomb tablet for several months I just personally don't share his opinion on it. I don't find it "totally unacceptable" or anything like that and can perfectly fine live with it, I care a lot more about all the new features and improvements ICS brings to the table.

    14. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 1

      So you don't deny his facts. There is a lag.
      It's just your opinion that lag features.

      I get that, I just think the lag would drive me nuts after a while. Especially after having used an iPad for a bit.

    15. Re:That's cool, but my one grip still by Gaygirlie · · Score: 1

      So you don't deny his facts. There is a lag.

      No, I don't deny that. I just see very little lag, so little that it doesn't bother me in the least, whereas the guy makes it sound like you see one frame every 5 seconds and that it takes 10 seconds for anything you type to appear. And that obviously ain't true.

      I get that, I just think the lag would drive me nuts after a while. Especially after having used an iPad for a bit.

      Indeed. That's called "differing tastes"; I have used an iPad and I just didn't find it any better than my tablet, a little smoother animations but lacking features.

    16. Re:That's cool, but my one grip still by jeffmeden · · Score: 1

      My reasoning has always been, if you have to turn off all the features to make the phone usable, why have the features at all? And turning them on only when I want to use them is too much hassle if I have to do it manually. I'm an American, I want it now and I want someone else to do it for me, damnit. Fortunately I found a workable solution (battery saving application).

      My reasoning has always been: "reading, it's fundamental!"'

      However, I found that if you disable all the features that are not present in the iPhone

      In other words, if you make it feature-comparable with an iPhone it will also be battery life comparable with an iPhone. This has been my experience with battery life as well. If you turn off the cool but unnecessary features (Google Latitude is one example) and still retain its smartphone-ness (email, web, social media, etc) you will get plenty of life out of your Android phone.

    17. Re:That's cool, but my one grip still by Miamicanes · · Score: 1

      Truth be told, I think 98% of Android's "lagginess" problem is due to CPU scaling and power management. A few weeks ago, I was using my old Hero (overclocked to 711MHz, CPU scaling & power management disabled, CM7 installed, running balls-to-the-wall full speed), and it was actually smoother than my dualcore Motorola Photon. Graffiti input was absolutely flawless (on the Photon, it's mostly accurate, but has its moments when I'm left wondering WTF the phone's power management is trying to do because it starts making weird recognition errors). On my Xoom, Graffiti is fucking unusable. It lags worse than my Hero did at 508MHz with stock HTC kernel and 1.5. I suspect Motorola did the same thing HTC originally did -- said, "Hey, we're displaying a soft input area, which is just sitting there idle with a bitmap waiting for a blunt keypress, so let's drop the speed down to something absurd like 200MHz" -- totally ignoring the fact that somebody might be using an input method that depends upon frequent sampling at close intervals.

      It's sad when a tablet with 1GHz dualcore CPU can't accurately do something a 16MHz glorified 680x0 could almost do in its sleep with 99.999% lag-free accuracy.

      We don't need more aggressive power management, we need 4800mAH batteries so we can enjoy our phones and have them last all day. The problem is that manufacturers like HTC, Samsung, and Motorola are all afraid to release a phone that's thicker than last year's iPhone, so they all ship with anemic & undersized batteries. Take a phone with a 4.25+ inch display, make it a millimeter thicker, and redistribute the innards to make full use of every cubic millimeter of interior space for either electronics or battery (the Evo 4G, for instance, wasted nearly 25% of its internal volume on an empty orange plastic frame, and most new phones are no different). Maybe ship the phones with TWO batteries -- a custom, non-(easily)-replaceable battery that takes those space-filling frames and fills them with 1800-2400mAH worth of Lithium gel, and a second ~1700mAH battery that's replaceable and gets used first and recharged last. If you add the volume of the space-wasting frame with another ~3.5" x 5.5" x 1mm of lithium gel spread out across the entire area of the phone, it would be no big deal to make phones with 4,000+ mAH batteries.

    18. Re:That's cool, but my one grip still by lunatic1969 · · Score: 1

      You're looking for a fight where there isn't any and I have no idea why. My recommendation is decaff. While you're looking for the coffeepot, you might re-read my message and try to figure out where I had misunderstood anything I read.

    19. Re:That's cool, but my one grip still by Dishevel · · Score: 0

      So in effect you are stating that your brain does not work well so for you an iPhone is better?

      I had to!

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    20. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0

      There doesn't appear to be much stuttering on the prototypes they had for demo. Interesting that there seems to be an option to force gpu rendering, see here at 4:24: http://www.youtube.com/watch?annotation_id=annotation_718183&v=sLlhhgTEXBA&feature=iv&src_vid=b1D7zZuIM3Y

    21. Re:That's cool, but my one grip still by lunatic1969 · · Score: 1

      So in effect you are stating that your brain does not work well so for you an iPhone is better?

      I had to!

      Not at all. I'm saying my brain doesn't work so well, so I need the phone to manage its resources for me. I have an android phone and the solution for me was an application to help do that. I'm not trying to argue iPhone vs Android, to me it's all the same. I'm just sayin'. I have an android, and this is what worked well for me.

    22. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0

      Point taken. But since your average user cares more about ease of use than features, lagginess is going to make a bigger impact than some secondary bulletpoint on a list of what's available.

      Which probably explains why Android tablets haven't taken off. Well, that and a lack of carrier subsidies & sales outlets.

    23. Re:That's cool, but my one grip still by jeffmeden · · Score: 1

      You're looking for a fight where there isn't any and I have no idea why. My recommendation is decaff. While you're looking for the coffeepot, you might re-read my message and try to figure out where I had misunderstood anything I read.

      Epic, you insult me then insist I simultaneously look for a coffeepot and re-read your post. The statement "if you have to turn off all the features to make the phone usable" is very clear and to the point, but is completely misplaced since no one ever suggested doing that. Thanks for trolling then complaining when someone called you out on it. You are really making the internet a better place!

    24. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0

      The thing is, Android introduced multitasking on the mobile platform. It doesn't sound like your phone is actually "idle." It sounds like you have applications which constantly wake and run in the background. This is common for applications which fetch the latest weather, social network sites, mail, synchronization, so on and so on. Just because you're not actively using your device doesn't mean its idle. Not to mention bluetooth is also a drain. And if you leave WIFI on, even when you're not using it, the periodic scans it does, plus reconnection during wakes (even with screen off), can significantly affect battery life. Some tests I did indicate that WIFI, even on an "idle" device can cost you upwards of 20% of your battery. If you try, you will be amazed how much power you save just by being observant of the applications you install on your phone and which devices you have powered on.

      Also, contrary to dad303's comment, most people report a sharp increase in battery life when running CyanogenMod. Those that report less battery life are frequently running overclocked with more aggressive scheduling, so on and so on. In an apples to apples comparison, most people report roughly 20% - %50 better battery life (not to mention smoother, faster performance) when upgrading from stock to CyanogenMod. By far, the best way to increase battery life is to be mindful of the types of applications you install on your phone. And last, don't forget, you need not ever actually start an application by its icon for it to negatively effect battery life. If an application starts at boot, it never needs to interact with you to use battery juice.

    25. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0

      Yeah, bigger batteries will get rid of the lagginess. You assume that the code would change to use more power instead of just giving more talk time.

    26. Re:That's cool, but my one grip still by lunatic1969 · · Score: 1

      You're clearly having a bad day. I'm not arguing the iPhone. It's a perfectly good phone. I don't have one. I'm not against having one, but I have an android and my comment was regarding the android, battery consumption, and the act of turning on/off sensors. Contrary to your analysis, my reading comprehension is perfectly sound. I stand by my suggestion on the decaff, by the way.

    27. Re:That's cool, but my one grip still by Beowulf_Boy · · Score: 1

      You can blame HTC and Verizon for that and not Android.

      My wife has the same phone. MISERABLE battery life.

      Last weekend I rooted it and tossed Cyanogenmod7 on it, which is about as vanilla a rom as you can get.
      Her battery life has improved drastically. From dying around noon every day, to having 70% battery life left at dinner time.

      Its because Verizon just loves to load your phone up with useless crap. Same reason Windows used to come preinstalled with MSN, AOL, etc.

    28. Re:That's cool, but my one grip still by Anonymous Coward · · Score: 0

      Go back to your hole, you little disgusting troll. I've never experience that level of shit on my Android devices.

    29. Re:That's cool, but my one grip still by lunatic1969 · · Score: 1

      Just as an aside, I recently did the same to my Evo 4G. I really was surprised, Cyanogenmod is some good stuff. The installation process is also easy enough that even someone who hasn't done such things before should be able to handle it without issues.

    30. Re:That's cool, but my one grip still by scot4875 · · Score: 2

      That's pretty much a gross exaggeration of battery consumption. Not only that, but you seem to keep comparing battery life for Android phones under heavy load to the expected battery life of an iPhone under ideal conditions with no use. Apple doesn't own some magic technology that lets its phones do lots of work with no negative impact on battery life; they drain just as fast under heavy load.

      I have my Evo 4G with me all the time with bluetooth enabled and I easily get 2 days out of the battery unless I'm doing a lot of web surfing or playing a lot of games.

      --Jeremy

      --
      Jesus was a liberal
    31. Re:That's cool, but my one grip still by scot4875 · · Score: 1

      Actually, there are plenty of Android apps that will automatically start/stop applications/services based on your location/time of day/whatever, so your brain doesn't need to remember to do all that manually if you don't want to.

      --Jeremy

      --
      Jesus was a liberal
    32. Re:That's cool, but my one grip still by johnthorensen · · Score: 1

      I have had an extended battery for my Droid Incredible since not long after I got it, and was never disappointed with battery life. Then one day, I went back to a (new) standard-sized battery. I haven't gone back. I'm the kind of user that plugs in my phone on the nightstand to charge while I sleep, and even if I forget a night I can generally make it through the next day as well. My usage profile does include quite a bit of widgets, web browsing, et cetera (though no games), and I'm quite satisfied.

      I think for a lot of users it's the games or Netflix that does it. Or, living in an area with poor signal quality where the radio power (and power consumption) is automatically increased to compensate. With those situations, I could definitely see someone being disappointed in the battery life - but that's on just about any smartphone platform.

    33. Re:That's cool, but my one grip still by Atzanteol · · Score: 1

      Coming from the Apple world this concept may be new to you but these things are called "options." You can "choose" to turn them on or off. So if you want to remove them for better battery life you can do so. You don't even need to root your phone to do so. And if you want those features back you can do that too. Apple won't even sue you for doing so!

      --
      "Ignorance more frequently begets confidence than does knowledge"

      - Charles Darwin
    34. Re:That's cool, but my one grip still by NatasRevol · · Score: 1
      --
      There are two types of people in the world: Those who crave closure
    35. Re:That's cool, but my one grip still by shadowfaxcrx · · Score: 1

      I use my Bionic pretty heavily. It's either got streaming radio or streaming scanner traffic (which is really the same thing) going at least 6 hours a day. I also surf, read news sites, play games, etc. It lasts from 8am when I unplug it until I plug it back in, usually at around 30% battery, sometime between 11pm and midnight. The stock battery would require a boost (I usually plugged it into my mouse's USB recharger while at my desk), but the extended battery (all of 25 bucks) pretty much means I'm good to go all day, and about 90% of that is on 4G.

      I don't understand people bitching about having to plug the phone in at night. Really? This is a hardship? We have a device that fits in our hand that's more advanced than the portable computers depicted on Star Trek, and we're whining about batteries that only last 15 hours?

      --
      "I disagree with you" does not equal "flamebait."
    36. Re:That's cool, but my one grip still by Gaygirlie · · Score: 1

      To be honest, just being able to link to stuff doesn't prove your point either. Lag is a very subjective thing and many people interpret almost anything whatsoever as "lag", and never stop to think what could be causing it. For example, googling "iphone lag" produces plenty of stuff:

      https://discussions.apple.com/thread/1608445?start=0&tstart=0
      http://www.youtube.com/watch?v=Ui9bPJfeRoM
      http://www.iphonedevsdk.com/forum/iphone-sdk-development/59048-how-reduce-lag.html
      http://techgeeks-online.com/2010/eliminating-lag-on-iphone-ipod-touch/
      http://techgeeks-online.com/2010/eliminating-lag-on-iphone-ipod-touch/
      http://www.wowza.com/forums/showthread.php?7745-How-to-reduce-Iphone-live-Latency
      http://www.ifans.com/forums/showthread.php?t=37347

      Does that mean that there's some inherent lag to it, or could it just be that... well, people are whining over misconceptions and issues they caused themselves?

    37. Re:That's cool, but my one grip still by Joe+Tie. · · Score: 1

      Upgrade the battery. I have an incredible as well, and can't believe they actually thought the battery life was acceptable. I bought a huge battery for it that came with a new back cover to handle the increased size. It gets three times the life of the default battery, which finally got it to the point of me not having to really think about charging it.

      --
      Everything will be taken away from you.
    38. Re:That's cool, but my one grip still by shutdown+-p+now · · Score: 1

      iPhone may not do heavy workload any better, but it definitely is better at not using battery significantly when idling. You can leave iPhone on (and idling) for two days easily, while all Android phones I've had would die by the end of the second day.

      Ditto for iOS vs Android tablets, by the way. iPad, with a daily use of 1-2 hours, will easily last through half a week. Android tablet, not so much.

      Given that I much prefer Android otherwise, I wish Google would pay more attention to this deficiency.

    39. Re:That's cool, but my one grip still by tehcyder · · Score: 1

      I don't understand people bitching about having to plug the phone in at night. Really? This is a hardship?

      The point is that you don't know it will last til you get home at night, as for most people if you use the actual smartphone features the battery can drain at an alarming rate. I don't know what magic special battery you're using, but even so that's not an option for iPhone users.

      We have a device that fits in our hand that's more advanced than the portable computers depicted on Star Trek, and we're whining about batteries that only last 15 hours?

      No, we're moaning about batteries that only last 6 or 7 hours if you use it as an actual smartphone continuously accessing information.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    40. Re:That's cool, but my one grip still by BrokenHalo · · Score: 1

      That's pretty much a gross exaggeration of battery consumption.

      Not by very much. I have a Sony/Ericsson Xperia X10 Mini Pro which struggles to maintain useful charge for much more than a day with a new battery.

    41. Re:That's cool, but my one grip still by shadowfaxcrx · · Score: 1

      The point is that you don't know it will last til you get home at night, as for most people if you use the actual smartphone features the battery can drain at an alarming rate.

      I'd say streaming 6 hours worth of data, in addition to web browsing, etc, is fairly heavy use.

      I don't know what magic special battery you're using

      I told you. The extended battery made for the Bionic. It's $25 including the new back cover.

      but even so that's not an option for iPhone users

      I know someone will mod me troll for this, but the solution to that seems obvious. ;)

      --
      "I disagree with you" does not equal "flamebait."
  3. Ice Cream Sandwich by rossdee · · Score: 1

    Do you get wafers with it?
    What flavours are available?

  4. Continuous Voice Input by Gaygirlie · · Score: 1, Insightful

    It says there on the website that "The new voice input engine lets users dictate the text they want, for as long as they want, using the language they want.", but... well, is it really true? Can I just start blabbing out in Finnish, or does that actually mean "using the language they want as long as it's one of the few select languages"? If it's the latter then it's obviously not all that useful or wonderful as they make it out to be.

    1. Re:Continuous Voice Input by mwvdlee · · Score: 2

      If Google had invented the universal translator, they might have made a slightly bigger deal out of it.
      So my guess is that it's limited to the languages you specify, just like the keyboard.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    2. Re:Continuous Voice Input by Gaygirlie · · Score: 1

      You kinds of missed my point. My point was that they're just outright lying if they claim you can use whatever language you wish if that ain't true, and that it's simply nothing new then; everyone does that nowadays.

    3. Re:Continuous Voice Input by ceoyoyo · · Score: 2

      A marketing company lying? Say it isn't so!

    4. Re:Continuous Voice Input by Anonymous Coward · · Score: 0

      Google is a marketing company?

    5. Re:Continuous Voice Input by gsslay · · Score: 1

      Allowing input in multiple languages is not the same as translating multiple languages. Google could be allowing input through every and any language on the planet, and it still wouldn't be translating anything.

      But seriously, the current Google voice input can't even handle accents, never mind handle any language. It's laughably useless in at least 50% of its attempts, which makes it totally useless. If they're being honest with their description here it will be a massive step forward.

      And can I switch language mid stream?

    6. Re:Continuous Voice Input by johnthorensen · · Score: 1

      Er, they do derive the majority of their revenue from advertising. So it's probably fair to at *least* call them an advertising company (which isn't exactly the same as marketing - but it's close!) :)

    7. Re:Continuous Voice Input by The+Dawn+Of+Time · · Score: 1

      They're only "outright lying" if you take an overly strict interpretation based on assumption, as you did.

      Feel free to believe whatever you want, of course. I'm not here to tell you that you aren't allowed to be dead wrong about stuff. This is Slashdot, where there are no bounds on the stupidity you can bring to the table in the name of being smarter than everyone else.

    8. Re:Continuous Voice Input by Xest · · Score: 1

      To be fair, last time I used Google translate on my phone (about a year ago) I was suprised at how effective it was at supporting the most random of languages in terms of both input and output as both text and speech. I dare say they've made more progress in the last year, I wouldn't be suprised if they actually do support a hell of a lot of languages so whilst it's still down to supported languages, last time I checked that list was a pretty decent size spanning languages spoken by the vast majority of the world's population at least.

    9. Re:Continuous Voice Input by jeffrey.endres · · Score: 1

      It is called http://en.wikipedia.org/wiki/Puffery>puffery.

    10. Re:Continuous Voice Input by Anonymous Coward · · Score: 0

      They're only "outright lying" if you take an overly strict interpretation based on assumption, as you did.

      Feel free to believe whatever you want, of course. I'm not here to tell you that you aren't allowed to be dead wrong about stuff. This is Slashdot, where there are no bounds on the stupidity you can bring to the table in the name of being smarter than everyone else.

      Thats not all. This is some sort of software product. Where's my ice cream sandwich? That is false advertising!!!!

  5. So because of that asshole... by dev897 · · Score: 0

    The asshole that hacked kernel.org?
    Because of him we don't yet see source of 4.0?
    Or its just Google trying to feed us bullshit again?

    1. Re:So because of that asshole... by Anonymous Coward · · Score: 0

      Shut up, stupid.

    2. Re:So because of that asshole... by squiggleslash · · Score: 1

      I'm pretty sure we'll see the source of 4.0. Generally Google doesn't release the source immediately, it makes a source code drop a little after the OS is announced and released.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:So because of that asshole... by Anonymous Coward · · Score: 1

      Yeah, 2 years after we see Honeycomb.
      Coming real soon now.

    4. Re:So because of that asshole... by Anonymous Coward · · Score: 0

      Nobody here actually cares about seeing the Android source. The main point to make is that Google could release the source if they wanted to, whereas Apple/Microsoft never will.

      It may seem like a petty point, but with a $100 bounty for +5 ranked pro-Android or anti-iPhone posts on slashdot, it sure helps pay the bills.

    5. Re:So because of that asshole... by squiggleslash · · Score: 2

      Google made it clear from the beginning that Honeycomb wasn't going to be opened. There's been no problem getting the source for Honeycomb's mobile peer, Gingerbread - I'm running it right now courtesy of Cyanogen.

      I don't like the fact that Google didn't open Honeycomb, but they had their reasons, and I respect them. Unlike ICS, Honeycomb was always a rushed "production" beta, and Google didn't want developers working from it. ICS, on the other hand, is the future direction of Android. There's no reason to suppose that Google isn't going to release the source for it, as failing to do so would pretty much kill the platform.

      --
      You are not alone. This is not normal. None of this is normal.
    6. Re:So because of that asshole... by oakgrove · · Score: 1

      The implications of your post sadden me.

      --
      The soylentnews experiment has been a dismal failure.
    7. Re:So because of that asshole... by Dishevel · · Score: 0

      They pretty much told you that Honeycomb was a dead end in the beginning and that they would not release the source code of that.
      Oh wait, Posting AC, iMicrosoft shill just trying to spread FUD.

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    8. Re:So because of that asshole... by Miamicanes · · Score: 1

      They also did it to stop the flood of cheap, borderline-useless 480x800 $100-200 tablets from China that were destroying the Android tablet market by setting consumer price expectations to unrealistically low prices & making it almost impossible to sell Android tablets with more appropriate hardware (1-GHz dualcore, 1280x800 display). Google basically told manufacturers, "you can have Honeycomb if you want it, but you're only allowed to use it on appropriately high-end hardware". The alternative would have been an endless flood of cheap tablets that totally sucked and made Android forever look bad compared to the iPad. Google HAD to do something, and do it fast, to forcibly raise Android tablet specs to realistic levels, and restricting access to Honeycomb was the only real sledgehammer they had available.

      Obviously, ICS is going to quickly end up on those same cheap under-powered tablets anyway. The difference is, at least now the market has had about a year to mature, so faster tablets at least EXIST now so consumers can directly compare them side by side and see firsthand why a faster tablet with higher-res screen is worth the extra cost.

      I do think Google went a little overboard by mandating a minimum screen size, as opposed to sticking with a minimum RESOLUTION. Given a choice, I would have rather bought a tablet with the same 1280x800 resolution, but a *slightly* smaller screen (say, around 8 or 9 inches).

    9. Re:So because of that asshole... by iapetus · · Score: 2

      Loads of people here care about the Android sources being available. Personally I work with the Android source, and need it available to me where possible. But for people who don't, many of them still want to be able to use Cyanogenmod or other ROMs developed from the source. Even if they don't see it personally, they can get benefit from it.

      --
      ++ Say to Elrond "Hello.".
      Elrond says "No.". Elrond gives you some lunch.
    10. Re:So because of that asshole... by Cute+Fuzzy+Bunny · · Score: 1

      Hmm, I have one of those cheap borderline useless chinese tablets. I use it all the time to check my email, facebook, play tons of games, as a big screen gps, watch netflix and hbo-go, etc, etc, etc. What sorts of things can I not do with it that would magically come about if I used a more expensive android tablet with 'appropriate hardware'. Whats weird is that my cheap noname tablet has virtually the same hardware as the original ipad, except some people say the screen isnt as good. Which I dont seem to give a @#%$$ about.

      Amazon also appears to have solved the problem with the Fire, since they realized that almost nobody gives a #$%$@ about what the hardware is, only that its inexpensive, does 98% of the stuff that 98% of users want, and has a full market of products behind it. Thus the consumer gets cheap access to content, amazon makes their profits on that, and everyone lives happily ever after.

      Except for Apple, who will need to learn to either give away ipads and iphones, or lower their content prices to remain competitive. And Google, which will have to take on turning out cheap tablets/phones through their new motorola subsidiary and back it up with cheap market content. Everyone else might as well just get out of the business entirely, since nobody is going to buy $400-500+ tablets anymore, and anyone without a fully fleshed out market wont make any profit on the sale of the devices.

  6. Seriously? by vlm · · Score: 2, Insightful

    face unlock

    Does that mean if someone steals my phone and my wallet, all they have to do is hold the drivers license up to the cam to unlock? Sounds like a very bad idea.

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    1. Re:Seriously? by Anonymous Coward · · Score: 2

      And do you really think that you won't have the option to turn this off?

    2. Re:Seriously? by Slyfox696 · · Score: 1, Insightful

      face unlock

      Does that mean if someone steals my phone and my wallet, all they have to do is hold the drivers license up to the cam to unlock? Sounds like a very bad idea.

      Then, perhaps, you might not want to use the facial recognition feature, and instead go with one of the other lockscreens. It's not a bad idea, just one you won't use.

    3. Re:Seriously? by grommit · · Score: 1

      Quick, you need to tell Google because there is no doubt that they didn't think about this workaround already!

      Of course, that'll be one of the first things that I test out when I get ICS. :)

    4. Re:Seriously? by ttong · · Score: 1

      You can still set a password, pin code or pattern to lock the screen. 3rd Party apps also allow for other unlocking methods such as a gesture.

    5. Re:Seriously? by camperdave · · Score: 1

      face unlock

      Does that mean if someone steals my phone and my wallet, all they have to do is hold the drivers license up to the cam to unlock? Sounds like a very bad idea.

      When I first read the term "face unlock", I thought it was that system where they put up a grid of random faces and you pick the one that you recognize. I'd much rather see that in effect than this facial recognition system.

      Mind you, if it could recognize my ear instead of my face...

      --
      When our name is on the back of your car, we're behind you all the way!
    6. Re:Seriously? by mwvdlee · · Score: 1

      Recognizing a face is probably a lot harder than distinguishing whether whatever is on the camera is dead or alive, so my guess is that it won't work.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    7. Re:Seriously? by Asic+Eng · · Score: 1

      Well it's more secure then just "slide to unlock" and it's not as inconvenient as a more secure screen lock.

      Secure screen locks are a bit of a problem with smart phones, since (in order to save battery) the lock engages so often. It would be nice if there was an option to have different locks - just a slide if you haven't used the phone for a minute, and e.g. a PIN if you haven't used it in 15 mins or so.

    8. Re:Seriously? by jrumney · · Score: 1

      It might still be an improvement over "run your finger along the visible smearmarks on the screen" method of unlocking.

    9. Re:Seriously? by f0rk · · Score: 1

      Dont take my word for it, but i think this is already the case. It might be a feature of CyanogenMod and not AOSP.

    10. Re:Seriously? by blizz017 · · Score: 1

      which really only works if the only thing the person did was unlock the phone.. if the phone was actually used, you'd have indistinguishable smear marks all over the screen.

    11. Re:Seriously? by ceoyoyo · · Score: 1

      From the video face unlock is enough of a pain that most people will probably turn it off after showing it to all their friends anyway.

    12. Re:Seriously? by jeffmeden · · Score: 1

      A little digging into focus distance data will give the phone more than enough info it needs to tell the difference between an actual life-size face and a tiny little image of a face on a card... Also, most (all?) photo IDs have security features including watermarks, overlays, and holograms that could be detected and used to negate the scan. Or, as many have pointed out, just don't tell it what your face looks like and stick with putting in a pin or using a silly little puzzle to unlock it. Whatever lets you sleep at night.

    13. Re:Seriously? by Miamicanes · · Score: 3, Insightful

      Ahhh, yes.... biometrics: the weak, insecure password you can't change.

    14. Re:Seriously? by Miamicanes · · Score: 1

      ^^^ what he said. Maybe take advantage of the Hall Effect sensor to be aware of when the phone ceases to be in close proximity to some large, blunt fleshy object (hand, thigh/butt adjacent to phone in pocket, etc) and progressively escalate the security as the phone's body-presence is interrupted or as time passes with inactivity. Perhaps monitor the accelerometer for motions that could indicate grabbing/dropping, setting down on a table, orientation (face up/face down), etc. Put the phone on a table face up, and strong authentication doesn't kick in for a couple of minutes. Put the phone on the table face down, and it kicks in within 5 seconds. Maybe keep track of the current authentication level, so a corporate app that demands neurotic authentication levels could hide its content until the user authenticates without torturing the user and making him jump through the same hoops to answer an incoming phone call. This is an area with PROFOUND opportunities for improvement.

    15. Re:Seriously? by jeffmeden · · Score: 1

      Well it's more secure then just "slide to unlock" and it's not as inconvenient as a more secure screen lock.

      Secure screen locks are a bit of a problem with smart phones, since (in order to save battery) the lock engages so often. It would be nice if there was an option to have different locks - just a slide if you haven't used the phone for a minute, and e.g. a PIN if you haven't used it in 15 mins or so.

      Yeah, it's a wonder they haven't thought of that... Er wait no they did that exactly. You can set the PIN to engage only after a set interval that can be longer than the screen timeout. Slightly less secure but a lot less annoying if you are prone to using your phone for short, frequent bursts during the day.

    16. Re:Seriously? by Anonymous Coward · · Score: 0

      I wonder if it's tuned to facial features, or if it would work with other parts of your body.

    17. Re:Seriously? by Asic+Eng · · Score: 1

      Don't have it on my stock SGS2. I'm not sure if that's the fault of Google or of Samsung.

    18. Re:Seriously? by Funnnny · · Score: 1

      It'll not that easy. They said it can detect real person or a image. I think they can do so by just change the front camera focus.

    19. Re:Seriously? by OverZealous.com · · Score: 1

      It's simple: tattoo a unique face (that isn't yours) to the pad of your thumb. Then just hold your thumb up to the camera!

      It's two! two! two biometrics in one!

    20. Re:Seriously? by Anonymous Coward · · Score: 0

      No, you have to think deeper. Sure you can leave it on or off, but why not have a different picture of you to unlock it than your normal picture?

      Red foam clown noses are easy to keep in your pocket... Though people might give you funny looks when you put one on to use your phone.

    21. Re:Seriously? by AvitarX · · Score: 1

      My understanding is a lot of these systems look at depth of focus and use a video stream to establish some level of dementionality.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    22. Re:Seriously? by Knuckles · · Score: 1

      Worked like that on Blackberry. After switching to Android I thought I just can't find the setting. Thanks for clearing that up.

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    23. Re:Seriously? by erikboi · · Score: 1

      The pattern unlock only uses each dot the first time you touch it so there is nothing stopping you from adding an extra swipe or two to the pattern without affecting the input. With at little bit of thought put into the path it pretty much makes this issue go away.

    24. Re:Seriously? by Anonymous Coward · · Score: 0

      iOS has this option, has for a while

    25. Re:Seriously? by Anonymous Coward · · Score: 0

      Or alternatively, you know, take more care with personal possessions that are clearly very valuable to you.

    26. Re:Seriously? by DaVince21 · · Score: 1

      And who says they'd be able to steal both? Or perhaps the picture on the license isn't high quality enough to be usable (my ID contains a 1-color pointy grid of my actual photo, more or less)?

      They're adding a bit of security that wasn't there before, and may or may not work depending on the person and their ID. It doesn't sound like a "very bad idea" to me.

      --
      I am not devoid of humor.
  7. Re:first by camperdave · · Score: 1, Offtopic

    my first post!

    Oh come on Anonymous Coward. You've been posting for as long as I've been on Slashdot. Nobody believes this is your first post.

    --
    When our name is on the back of your car, we're behind you all the way!
  8. Andriod app development by LizardKing · · Score: 0, Troll

    Have they fixed the appalling development platform for programming Android apps? I've some experience of programming for the iPhone, and as I can already program in Java I thought I'd give Android programming a try late last year. The API is horrible - standard Java classes replaced by poorly designed alternatives for no apparent reason, those horrible XML files as the preferred way of designing a UI, and unavoidable casts all over the place. When I got to the bit in the tutorials about apps being forcibly restarted when the orientation changes I cried with laughter. It feels a proof of concept rather than a polished development platform, as though Google bought a work in progress and couldn't be arsed to finish it because they needed to get it out quick in order to compete with iOS. Compared to the best practices with regular Java programming, it's as though the Android SDK ignores all the lessons of the last twenty or more years of object oriented programming ...

    1. Re:Andriod app development by oakgrove · · Score: 5, Insightful

      The API is horrible - standard Java classes replaced by poorly designed alternatives for no apparent reason

      So your rationale is that the API is horrible because they added in some bespoke classes? In the platform developer's opinion, those classes are better suited to mobile devices. But, guess what, you don't even have to use them. What Java classes did they "replace" that aren't still there? I haven't found anything in particular that has been replaced, they just gave you the option of using the newer stuff. The analagous Java class is still there. And how are the new classes poorly designed?

      those horrible XML files as the preferred way of designing a UI

      Er, if you don't want to use XML files to do your UI, you don't have to. You can use pure Java all day long. Besides, the XML files are exploded into Java on the device anyway. You use the XML to quickly design the static elements of your UI and use Java code to do the interactive stuff. What is there to bitch about?

      When I got to the bit in the tutorials about apps being forcibly restarted when the orientation changes I cried with laughter.

      This is not even true. The activity does not "restart", the ui reinitializes to use the layout prescribed for that particular orientation. You don't want a long list of single column buttons in landscape, you want them more logically laid out so the UI for the activity restarts. It is trivially easy to keep all of the ui data like form contents, etc. and reinsert it into the layout when the screen rotates and it happens instantly so the user isn't even remotely aware. Poor app developers that don't take the very small amount of time to make this happen is what gives it a bad rep.

      It feels a proof of concept rather than a polished development platform

      Nothing you've said supports this conclusion. The points you make are what I would expect from someone that is looking for a reason to hate before he's even given the platform a chance.

      --
      The soylentnews experiment has been a dismal failure.
    2. Re:Andriod app development by LateArthurDent · · Score: 2

      those horrible XML files as the preferred way of designing a UI

      Hmm...separating the UI description out in xml files is a good thing. In fact, it's a standard thing across all platforms. Android has those xml files, Windows has xaml, and iOS has .xib files.

      Sure, interface builder abstracts you from the .xib files, and you never have to look inside it, but you can do xaml and android xml via their respective design interfaces too. The fact that you can also edit the xml manually is a feature, not a bug.

    3. Re:Andriod app development by LizardKing · · Score: 0, Flamebait

      So your rationale is that the API is horrible because they added in some bespoke classes?

      I looked at the implementations of the alternative to many of the Collections classes in particular, and they had nothing in them that suggested they were "better suited to mobile devices". And I'm not going to dig through the API docs, but they were certainly no improvement on the equivalent Java classes, and I recall them often being less intuitive.

      Er, if you don't want to use XML files to do your UI, you don't have to.

      I know you can construct your UI directly in code, but virtually all the documentation I have seen assumes you'd never want to do that and omits coverage of it. Hence why I said the XML format was presented as "the preferred way".

      This is not even true. The activity does not "restart"

      The process is exactly the same as when the app is explicitly shutdown by the user or the app developers code, so it is true. That's why you have to store the current state of the application, as you allude to in your comment.

      Nothing you've said supports this conclusion [that the development platform feels like a proof of concept]

      Well, if you feel it's more than just adequate then I dread to think what your own code looks like. While I dislike the walled garden approach of Apple, from a purely technical point of view I love the iOS as a platform to develop for. I had high hopes that the Android SDK would be as pleasant to develop for, since it is a much more open platform, but I'm left hoping instead that someone comes up with an alternative.

    4. Re:Andriod app development by Gaygirlie · · Score: 2

      When I got to the bit in the tutorials about apps being forcibly restarted when the orientation changes I cried with laughter

      Err.....lolwut? Was it perhaps a how-to-spread-FUD - tutorial?

    5. Re:Andriod app development by Anonymous Coward · · Score: 1

      I am an android developer fulltime. The UI builder in Eclipse (which is the one that comes with the SDK) is crap. Just plain crap.
      So what you end up having to do, is, to edit the XML manually, which is cumbersome and unintuitive.

      No, I have never laid eyes on the development platform for Apple devices, but I do know that the one for Android does feel entirely immature. It's everything I have come to expect from open source projects.

      But to be fair, Google also have another problem that Apple just doesn't have and which has always been Apple's strength: A small set of known hardware to support. I mean, the rate at which they cancel support for old devices should prove that this is part of their success. The main gripe with Windows has always been "this doesn't work. that old graphics card crashes" aso. Everything that crashes on a platform reflects on that platform. So a stable known environment is a huge advantage.

    6. Re:Andriod app development by squiggleslash · · Score: 1

      I think some specifics might make this a more useful post. I've not come across the issues you describe.

      As far as the "XML files (being) the preferred way of designing a UI", that's kinda dubious at best. Generally most of the specifics are coded in Java, with only basic metadata about the app being specified in XML. True, there's more metadata than there is in a desktop Java application, but it's not a lot.

      I should state here I hate XML with a passion, so if I thought Android development burdened people with large amounts of entirely unnecessary and pointless XML coding, I'd be the first to be screaming from the hilltops. I just don't see that as being the case, however.

      --
      You are not alone. This is not normal. None of this is normal.
    7. Re:Andriod app development by oakgrove · · Score: 3, Insightful

      I looked at the implementations of the alternative to many of the Collections classes in particular, and they had nothing in them that suggested they were "better suited to mobile devices". And I'm not going to dig through the API docs, but they were certainly no improvement on the equivalent Java classes, and I recall them often being less intuitive.

      The use the Java classes. Why complain about choice?

      I know you can construct your UI directly in code, but virtually all the documentation I have seen assumes you'd never want to do that and omits coverage of it. Hence why I said the XML format was presented as "the preferred way".

      Yes, because the XML way is going to be easier and more intuitive for many people. For the hardcore olde thymers such as yourself, you can use Java. Again, the choice is yours.

      The process is exactly the same as when the app is explicitly shutdown by the user or the app developers code, so it is true. That's why you have to store the current state of the application, as you allude to in your comment.

      No, it most assuredly is not. Android apps are not like desktop apps. The lifecycle is totally different and more suited to an "on-the-go"/everything runs fullscreen device. onCreate initializes the logic of your activity and it is called once when that activity is first run. When you shut down an app explicitely, it calls onCreate when you go back to it. When you rotate the screen, it calls onPause and onResume so that your portrait layout (for example) isn't just jumbled together and resized for landscape. You can have a completely different layout for the two modes. Or you can just use onPause and onResume to fill form data back in and to hell with having multiple layouts. When the screen is rotated, everything done in onCreate is maintained that includes all variables, etc. You save form data with onPause and refill it with onResume. It's trivially easy and in the context of the system makes sense. I'm not a teacher, I'm a programmer so my explanation likely sucks. My suggestion is you read this.

      Well, if you feel it's more than just adequate then I dread to think what your own code looks like.

      Because I disagree with you and think Android is an elegant system to develop for, that means my code sucks? I'm sorry, who are you and what are your credentials again that I should just slavishly follow what you say? When you can give me compelling reasons for why Android supposedly sucks (and you haven't), I'll believe it. So far, you've just given biased opinions based on your impressions of a platform that you don't code for and obviously don't have any real intentions of even giving a fair chance. With that attitude of inflexibility, I'd really hate to see your code.

      --
      The soylentnews experiment has been a dismal failure.
    8. Re:Andriod app development by Anonymous Coward · · Score: 0

      I have no idea who keeps modding you up as you haven't the slightest fucking clue what you are talking about. This is why I spend more and more time on Hacker News.

    9. Re:Andriod app development by LateArthurDent · · Score: 1

      I am an android developer fulltime. The UI builder in Eclipse (which is the one that comes with the SDK) is crap. Just plain crap.
      So what you end up having to do, is, to edit the XML manually, which is cumbersome and unintuitive.

      Developers have different preferences. I readily admit that I've only played with iPhone and Android development, but I am a full-time windows developer, and I deal with .net and xaml all day long. I end up editing the xaml manually, but I don't find it cumbersome and unintuitive. Frankly, I find Interface Builder cumbersome.

      After I've placed a combo box on a screen, I want to bind the selected item to a property. The editing xaml manually method is to click on the combo box to take you to its ComboBox definition tag in the xaml, and add the attribute:

      SelectedItem="{Binding TheSelectedItem}"

      Where "TheSelectedItem" is the property name in the object set as the data context. The Apple method is more like, "ok, I need to find the menu item that does binding, click on that, then click on the combo box, and drag the arrow to the objective c file that contains the class description, then select the attribute I wish to bind and the variable name I want to bind to."

      Again, I'm not going to say that one method is better than the other, because I know people have different preferences, and I bet you can be pretty proficient if you know your way around interface builder better than I do. That said, I can tell you that my personal preference is for editing the xml manually.

    10. Re:Andriod app development by Miamicanes · · Score: 4, Insightful

      Not quite. Orientation changes do, in fact, terminate and restart activities. It works fine if you do literally all network activity with background services and strictly observe canonical model-view-controller design, but kills newbie Android developers left, right, and diagonally, and is the single biggest reason why so many non-MVC Android apps forcibly lock views to a single orientation (the only way to prevent it from happening).

      You can tell the scheme was originally concocted based on the G1's hardware -- flip out the keyboard, the screen rotates. A specific, unambiguously deliberate act. The problem is, they extended rotation to the accelerometers, and all hell broke loose because you started to get spurious, accidental rotations caused by users holding the phone in their hand and changing its orientation when something else captured their attention for a moment (like the cashier at a store or fast food restaurant, or putting the phone down while driving because the light turned green). The teardown behavior is sensible in a pure MVC design, and is tolerable when orientation changes are deliberate and rare, but breaks down and becomes totally dysfunctional when you add the current accelerometer-driven orientation dynamics.

      Don't get me wrong -- I think accelerometers are a great way to determine orientation. I just wish there were a big, easy to deliberately press (and hard to accidentally press) hardkey that meant, "take an accelerometer reading now, and adjust the orientation if appropriate. Then stay that way until I press the button again". Right now, with tablets like the Xoom, you're forced to either lock the orientation (and go through 20 seconds of annoyance to switch between portrait and landscape), or deal with endless spurious orientation changes that seem to be far easier to trigger than to undo (ie, a slight tilt in the wrong direction changes the screen, but when you try to get it to go BACK, the new orientation is "sticky" for a few seconds. Pure frustration.) In the Xoom's case, I'd overload the power button so that a rapid double-press (that would normally turn off the screen, then turn it back on with the screen lock annoyingly activated even though the screen was only off for ~300 milliseconds) would trigger an accelerometer reading and orientation change.

      The other hugely stupid thing Android did that causes endless misery, and will probably cause misery forever, was to implement a SUBSET of BouncyCastle without changing the namespace, which totally fucks up any program that needs to use a part of BouncyCastle that's not part of the core API. You can't just drop the BouncyCastle jarfile into your project, because then you get namespace collisions and Bad Things Happen(tm). So, you have to basically take BouncyCastle, then rebuild it with a different package name, then change every reference to use your new namespace instead of the original.

    11. Re:Andriod app development by mswhippingboy · · Score: 1

      ...I cried with laughter.

      Same reaction I had when I read

      When I got to the bit in the tutorials...

      in your post.

      I'll take your criticisms with the same level of credibility as the depth of your analysis.

      --
      Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
    12. Re:Andriod app development by Anonymous Coward · · Score: 0

      The proof is in the pudding. Android itself and Android apps cosistently don't hold a candle to iOS apps in their functionality, usability and general quality.
      The obvious culprit is the underlying over engineered misarchitecture and the resulting horrific APIs.
      Case in point. For the very obvious and what should be mundane and simple task of communicating between activities you get this, http://developer.android.com/resources/faq/framework.html#3, various different ways of saying "use globals". An API that requires using globals to be able to use it reasonably is broken. Very broken.

    13. Re:Andriod app development by Anonymous Coward · · Score: 0

      Have they fixed the appalling development platform for programming Android apps? I've some experience of programming for the iPhone, and as I can already program in Java I thought I'd give Android programming a try late last year. The API is horrible - standard Java classes replaced by poorly designed alternatives for no apparent reason, those horrible XML files as the preferred way of designing a UI, and unavoidable casts all over the place. When I got to the bit in the tutorials about apps being forcibly restarted when the orientation changes I cried with laughter. It feels a proof of concept rather than a polished development platform, as though Google bought a work in progress and couldn't be arsed to finish it because they needed to get it out quick in order to compete with iOS. Compared to the best practices with regular Java programming, it's as though the Android SDK ignores all the lessons of the last twenty or more years of object oriented programming ...

      I think the real revelation here is that you were never a programmer in the first place. Sorry to break it to you. Have you considered data entry?

    14. Re:Andriod app development by PoopCat · · Score: 1

      This is the first time I've seen XML presented as easy or intuitive.

    15. Re:Andriod app development by PoopCat · · Score: 1

      As far as the "XML files (being) the preferred way of designing a UI", that's kinda dubious at best. Generally most of the specifics are coded in Java, with only basic metadata about the app being specified in XML.

      You're lying, or just very inexperienced with Android development. The typical, standard, preferred way of describing an Android app's UI is via XML; this allows you to very simply leverage the platform features that display the correct UI based on device capabilities such as screen size, resolution etc. Not to mention there are some things you simply cannot do in java, such as easily applying a style to a UI element (via something like textView.setStyle(R.style.text_view)) .

      Professional android developer (over 40 released apps) here with a deep, ingrained distaste for XML.

    16. Re:Andriod app development by oakgrove · · Score: 1

      The proof is in the pudding. Android itself and Android apps cosistently don't hold a candle to iOS apps in their functionality, usability and general quality. The obvious culprit is the underlying over engineered misarchitecture and the resulting horrific APIs.

      Silly me. Here I was thinking it had to do with the fact that there is much more money to be made developing for iOS so developers are going to target it first and hardest.

      Case in point. For the very obvious and what should be mundane and simple task of communicating between activities you get this, http://developer.android.com/resources/faq/framework.html#3, various different ways of saying "use globals".

      Assuming you understand how intents work, how is

      Intent.putExtras()

      a global in any conceivable way?

      --
      The soylentnews experiment has been a dismal failure.
    17. Re:Andriod app development by oakgrove · · Score: 1

      Maybe actually try developing an Android app or two. Throw in a full dose of intellectual honesty and then you can come back and tell us all if creating an XML based layout is intuitive or not. I'll be waiting.

      --
      The soylentnews experiment has been a dismal failure.
    18. Re:Andriod app development by Anonymous Coward · · Score: 0

      I retract this. You are entitled to your opinion. Mine differs.

    19. Re:Andriod app development by squiggleslash · · Score: 1

      You're lying, or just very inexperienced with Android development

      Or I don't code the way you've chosen to.

      I appreciate the quantity of Android apps you've written, but if a particular feature of development is bugging you so much, I have to wonder why you've not even tried to avoid it?

      --
      You are not alone. This is not normal. None of this is normal.
    20. Re:Andriod app development by Anonymous Coward · · Score: 0

      the activity restart on portrait change is a simple config change to get rid of, you add that to where the activity is declared and bam, it doesn't create it again so you don't have to save your data into a bundle or whatever(there's a zillion ways to retain the data, the process is the same too so statics stay what they are too). however, it's not mentioned too widely that you can do this. you'll find it with google easily enough though. you'll get a configure change event though about the orientation change and can switch layouts if you wish - though I suspect quite a lot of app developers just keep static references to their data and state so they can come back to whatever state they were in even if the activity gets created again(if the process gets killed you're fucked anyways if you didn't dump stuff to disc so...).

      there's a LOT of similar small things in android. and a lot of bullshit in the tutorials and docs, like this orientation change thing. the code styling recommended to put things into bundles and do expensive service style moving of data around when you're in the same fucking java process are another thing, it's like the style(recommended way of doing things, as in tutorials, official examples etc) was written for something that android didn't end up being.

    21. Re:Andriod app development by Anonymous Coward · · Score: 0

      You can make it not restart activities by adding this to your manifest and the corresponding activity:

      android:configChanges="keyboardHidden|orientation"

      If you then dont override onConfigurationChanged, it doesnt restart the activity.

      It should be the default, but you're wrong in saying its not possible.

    22. Re:Andriod app development by Anonymous Coward · · Score: 0

      that's all fine until you realize that you're better off building 20 xml's for one screen and stitching them together with code - and then if you want to change it, you actually have to change things in 3 files and the total line numbers you have to mess with are much larger than if you had just stuck with creating the ui in code(or even invented your own markup).

      the fact that the wysiwyg editor sucks means you'll be writing the xml's by hand anyways. I mean it's really horrible if you compare to qt creator. really, really horrible.

      it works though, I'm not saying that it doesn't work. I'm just saying that it's nowhere 4.0...

    23. Re:Andriod app development by PoopCat · · Score: 1

      Yeah, I should give that a try huh.. oh wait, I already did! I stand by my comments. Creating a layout in XML is intuitive? Nope, not. What else you got?

    24. Re:Andriod app development by PoopCat · · Score: 1

      Maybe, but your statement was effectively "claiming XML is preferred is dubious.. the general way is to use java". Which, IME, is certainly *not* the case. But since "preferred" and "general" are both anecdotal at best, I don't think either of us is in danger of changing the other's mind about which approach best fits those terms.

    25. Re:Andriod app development by oakgrove · · Score: 1

      Read my reply to myself.

      --
      The soylentnews experiment has been a dismal failure.
    26. Re:Andriod app development by Miamicanes · · Score: 1

      Cool, I didn't know that. Thanks! :-)

    27. Re:Andriod app development by Coward+Anonymous · · Score: 0

      You are not silly. You are just in denial. Google can't produce the same high quality apps on Android like it does on iOS. You also fail to appreciate the massive vendor interest and effort in creating Android apps.

      Read the FAQ question and answer. Intents are not for "complex objects". The official answer is stick your non-trivial object in a global hash map and pass the key in the intent. Epic fail. Truly epic when you keep in mind that the app could get blown away in the interim and the intent used to restart the activity with a key that is no longer meaningful.
      No, the one true way according to Google is to write hundreds of lines of code to marshal and unmarshal data between intents, SQLite and content providers. Amazingly, nobody does that. Nobody does it because it is an unmaintainable mess.

      Activities and intents are an over engineered mistake. They sacrifice everything (developer ease of use, functionality, performance, flexibility, maintainability, etc.) for the vague notion of being "restartable" and invocable across apps which in the end contribute nothing to your app.

    28. Re:Andriod app development by PoopCat · · Score: 1

      Fair enough - that reply was anonymous, so I did not automatically associate it with your good self.

    29. Re:Andriod app development by Anonymous Coward · · Score: 1

      Orientation change doesn't have to terminate and restart activities it's just the default and recommended way it done. You can configure it via the manifest to not restart your activity on orientation changes. Then it becomes completely your responsibility to manage the layout. Android does a lot of stuff in the background like loading layout dependent resources etc. and if you let it restart your activity then you don't it have to manually think about all these stuff. Also the activity is meant to be a lightweight UI. any background processing is meant to go into services and like.

      Once you understand the actual application stucture of an android app with activities, providers, services, etc. it actually makes sense. But like you said one needs to read the (not so good docs) and understand the concepts behind it. But for those who have come from the background of having all work being done on the UI window control this is a major hassel.

      I completely agree with the accelerometer comment. I simply disabled the automatice orientation change on my phone and found it to much more simpler to use.

      As a reply to grand parents comments. Best practices meant to a enterprise app doesnt always work with a memory constrained real time device like a mobile phone. Like Raymond Chen says best practices are best under certain ciruimstances not everywhere.

      Android has it's weakneses but it's nowhere near as what grandparent says. My peeve has to do with all the undocumented stuff.

    30. Re:Andriod app development by johnthorensen · · Score: 2

      In addition to what the other responder said about android:configChanges="keyboardHidden|orientation", it's possible with most mobile platforms for the application developer to include a soft-button in their interface that does what you describe.

      Personally, I do actually like the feature on the Xoom, included with Honeycomb 3.0, that allows one to globally lock screen orientation. Short of the 'orientation-flip' button you describe I find it a fairly reasonable alternative.

    31. Re:Andriod app development by Coward+Anonymous · · Score: 1

      Er, if you don't want to use XML files to do your UI, you don't have to. You can use pure Java all day long.

      Umm. No you can't. There are many widget aspects that are only configurable through XML. There is no Java API for them.

      Besides, the XML files are exploded into Java on the device anyway.

      Nope the XML files get bundled in your apk as is. Android might interpret them later in java but so what? It's gotta do it somehow.

      You use the XML to quickly design the static elements of your UI and use Java code to do the interactive stuff. What is there to bitch about?

      Oh, I don't know. That your UI code is now spread across some a few unverifiable XML files and Java instead of being in one place where it would be easy to maintain.

    32. Re:Andriod app development by scot4875 · · Score: 1

      When I got to the bit in the tutorials about apps being forcibly restarted when the orientation changes I cried with laughter.

      Kind of tough to take the rest of your subjective criticisms seriously when you get this objective one completely wrong. The activity is restarted, not the app. If you don't know how to engineer an app to make it so that activity != the whole app, it doesn't speak very highly of your software engineering ability. I'm not even a Java dev and I had that 'problem' solved within hours.

      --Jeremy

      --
      Jesus was a liberal
    33. Re:Andriod app development by Miamicanes · · Score: 2

      I'm not arguing that the 'orientation lock' feature shouldn't exist, just arguing that it would be nicer to use if a power button double-click were interpreted as "reorient the screen based on the accelerometer now, then lock it until the next time I double-click the button". A separate button would be even nicer, but making do with the hardware buttons the Xoom already has, a powerbutton doubleclick is just about the best unambiguous-yet-easy gesture I can think of.

      I personally despise gestures that require menu navigation. I'm impatient. I like things like "press and hold button one with the left index finger, press and release the right button with the right index finger three times, press it a fourth time and hold it, then press and release the left button two more times and release the right button" (just to give an example of some hypothetical multi-shifted multi-click gesture you could do with two hard buttons), because they're self-clocking and you can execute them as quickly as your muscle memory can actuate the buttons. I hate having to stop, look at the screen, touch something, wait, touch again, wait, wait, wait, and complete a gesture. I grew up triggering Mortal Kombat fatalities that involved 17 discrete key gestures within 800 milliseconds, and miss the old fashioned immediacy of hardkeys and muscle-memory instantaneous gestures.

    34. Re:Andriod app development by oakgrove · · Score: 1

      Umm. No you can't. There are many widget aspects that are only configurable through XML. There is no Java API for them.

      First of all, who cares? Second of all, by definition, this can't be true as the xml files are translated into java by the device.

      Nope the XML files get bundled in your apk as is.

      No shit, Shirlock. Android running on the phone translates them into the relevant Java code.

      Oh, I don't know. That your UI code is now spread across some a few unverifiable XML files and Java instead of being in one place where it would be easy to maintain.

      Welcome to modern software design. Here, I'll provide a linky.

      --
      The soylentnews experiment has been a dismal failure.
    35. Re:Andriod app development by Anonymous Coward · · Score: 0

      Google can't produce the same high quality apps on Android like it does on iOS.

      I own an iPad and multiple Android tablets and cellphones. The staple Google apps on Android are better than their counterparts on iOS. Maps in particular thoroughly trounces what is on my iPad. Gmail on Android is great and is even better with ICS. What exactly are you talking about here if I may ask.

      Read the FAQ question and answer. Intents are not for "complex objects". The official answer is stick your non-trivial object in a global hash map and pass the key in the intent. Epic fail. Truly epic when you keep in mind that the app could get blown away in the interim and the intent used to restart the activity with a key that is no longer meaningful.
      No, the one true way according to Google is to write hundreds of lines of code to marshal and unmarshal data between intents, SQLite and content providers. Amazingly, nobody does that. Nobody does it because it is an unmaintainable mess.

      Just did an informal poll in the office here. The consensus is that you have no idea what you are talking about. Sorry.

      Activities and intents are an over engineered mistake.

      If that's true then object oriented programming is an overengineered mistake since the concept of activities and intents is very similar. You fail.

    36. Re:Andriod app development by Coward+Anonymous · · Score: 1

      There is a glimmer of hope for you yet. You have not been completely brain damaged by Android development.

      First of all, who cares?

      You said it was possible. I pointed out you were wrong.

      Second of all, by definition, this can't be true as the xml files are translated into java by the device.

      No. Use your terminology correctly. It interprets the XML. It does not translate anything. Its not generating new Java and it is not generating bytecodes. Huge difference.

      And here is our glimmer of hope for you. You would expect that proper design would create a situation where "by definition" anything expressed in XML would be an expression of an underlying Java interface.
      But it is not designed correctly. The XML interpreter does not use the public APIs available to the developer. It does its own thing and so you end up with two code paths for the same thing- bad design.

      Don't believe me? Go look at the code.

      No shit, Shirlock. Android running on the phone translates them into the relevant Java code.

      Nope it doesn't. For someone who doesn't understand the basic difference between an interpreter and a code generator calling me clueless is a bit rich.

    37. Re:Andriod app development by oakgrove · · Score: 1

      I'll take a long hard look at what you've said. If you're right, thanks. If you're wrong, you suck.

      --
      The soylentnews experiment has been a dismal failure.
    38. Re:Andriod app development by Coward+Anonymous · · Score: 1

      If the quality of your reply is an indication of the general quality of the developers in your office I'm not surprised they don't understand how Android is meant to be developed in. It's too complex for your average drone to figure out.

    39. Re:Andriod app development by chrb · · Score: 1

      The correct question is: intuitive for whom? Tens of thousands of web developers around the world seem to manage okay developing layouts in HTML/XHTML (you might argue that HTML isn't XML, but I would argue it's close enough that you won't find one intuitive and the other not). Is it intuitive for them? For many it is. Would it be intuitive for my grandmother? Certainly not. Remember that creating a layout in XML doesn't actually require writing XML - the Android plugin for Eclipse enables XML layouts to be created by drag-and-drop of GUI widgets, no XML editing necessary.

      Gnome and other GUI frameworks have allowed layouts to be specified in XML for a long time, and there are other frameworks like QML that allow declarative descriptions of layouts in non-XML based languages. Is it the declarative nature of the task that makes it non-intuitive for you? Or is it the use of XML, rather than another declarative language like QML? There are many programmers who find declarative GUI layouts to be preferable to programatic ones, and there are many who are familiar with XML and prefer to use it rather than learn another custom layout language.

    40. Re:Andriod app development by PoopCat · · Score: 1

      I would argue that "familiarity with" != "intuitive". Since we're talking about Android here, can you really tell me that you are able to intuit that "fill_parent" *actually* means "match_parent" (which is why the former was replaced with the latter some time around SDK 8)? Or that an EditText needs a special declaration to make it multi-line? Remember, intuitive is by definition NOT something you already know.

      That said, since the argument was about creating layouts in XML, I'm ruling out the use of drag-n-drop, since you're not actually creating the layout in XML at that point. Something is, but it isn't the developer.

      And finally... yes, my biggest beef with XML is.. XML itself. It is a HORRIBLE language for humans to read or write, which explains in large part the enormous number of HTML/ XML/ SGML GUI editors.

      None of your arguments have convinced me that anyone would consider XML *intuitive* - even to someone skilled in other languages (except perhaps HTML, but as you said, the two are so closely linked as to make no odds). You seem to be confusing intuitiveness with facility, and frankly I'm not convinced XML exhibits either property.

    41. Re:Andriod app development by shutdown+-p+now · · Score: 1

      Google can't produce the same high quality apps on Android like it does on iOS.

      Simply comparing Google Maps app side by side on iOS and Android (2.3) device is enough to disprove this statement.

    42. Re:Andriod app development by shutdown+-p+now · · Score: 1

      Compared to creating a visual tree of widgets and wiring up event handlers for them in code? Yeah, it's pretty damn easy and intuitive.

      There's a reason why all modern UI frameworks move on to some dedicated markup language rather than code for UI, and quite often it's XML. On Windows, WPF, Silverlight and Win8 Metro are all XAML-based. On OS X, most Cocoa developers use Interface Builder, which outputs XML files (though those are generally not meant to be hand-authored - but it's easy enough to do so in practice). Gtk has Glade. Qt has QML, which, while not XML-based, is still a tree markup language.

    43. Re:Andriod app development by PoopCat · · Score: 1

      Intuitive? Ok, we'll find our mythical average man in the street, and ask them to code up an android app's UI in XML...Ok... Go!

      Hmm.. less than satisfactory results.. Ok, I'll try one of the python guys here, after all perhaps the man in the street just had no frame of reference to even begin.

      Nope, still not getting anything done. Ok, I'll make it easier. Find someone with no android-coding experience. You really think they'll be able to code up a UI in XML with NO reference to the docs?

      Perhaps "intuitive" belongs in the same category as "inconceivable" ? And perhaps your "creating a visual tree of widgets" might need some expansion, since you could be using shutdown -p now's Useless Tool For UI Creation and we have no idea how effective that actually is at its purported task.

      To put it bluntly, you have shown that *for you* creating a UI in ANY language is a breeze, because you've done it before. Once again, that does NOT make it intuitive!

    44. Re:Andriod app development by shutdown+-p+now · · Score: 1

      If you want to nitpick on wording, fine. No-one said that it's "intuitive". GGGP (who is not me, by the way) said that it's "easier and more intuitive" - which it is. It's much easier to describe a tree structure (which is what the widget tree is) is in a markup language that is specifically geared towards describing tree structures, than it is to do so in an imperative language which has no syntactic sugar whatsoever for this.

    45. Re:Andriod app development by Miamicanes · · Score: 1

      > The official answer is stick your non-trivial object in a global hash map and pass the key in the intent.

      Or subclass Application, instantiate it in the manifest, implement the code to serialize your values that need to persist IF it gets closed, and use it as a data repository for both the Activity subclasses and your background Service. From my experience, your application's (naturally) Singleton subclass of "Application" is pretty durable and long-lived if you declare & instantiate it in the manifest itself, unless the user is running some psychotic hyper-aggressive task killer (the kind that occasionally crops up at XDA, gets raved about for a few days, then gets abandoned almost as quickly by disillusioned users tired of having everything crash nonstop).

      If you don't embrace canonical Model-View-Controller architecture, Android is pretty dysfunctional. If you DO embrace it, it works fine, and works more or less exactly the way canonical MVC architecture is expected to work. As others have pointed out, the biggest single problem with the Android API is its documentation and examples, many of which were written for the G1 era, and describe scenarios that have only a loose connection to modern Android reality.

      As I've told others, if you're writing a networked client-server app, just forget that AsyncTask exists (it'll let you down, and cause you more long-term grief than it's worth) and just move the network communication directly into a multithreaded background service (with Application subclass as your transient backing store). Store returnvalues in the Application object, and fire off an Intent to let the Activity know something interesting happened and that it should update itself based on the new data in the Application object. It's a lot of work to get to "HelloWorld", but once you've gotten there, it makes everything several orders of magnitude easier to deal with. Kind of like Struts and Spring. In fact, if you've mastered J2EE web apps with Struts or Spring, Android's architecture actually makes a lot of sense. If you're coming from a PHP or C background, it'll seem more like the seventh level of Hell.

      It's not a coincidence that people's opinions of Android tend to fall into two extremes, with very little middle ground. I can't speak for game development, but when it comes to networked client-server apps, Android pretty much forces you to go 100% MVC whether you like it or not. If you like MVC, it rocks. If you hate MVC, it sucks. And if you don't really understand MVC, you're going to find yourself thrown naked into the frigid North Atlantic to sink or swim. IMHO, the best background you can possibly have going into Android development is a few solid years of J2EE development based on Struts or Spring, with at least one Sun certification under your belt (just to make sure you really, REALLY have a solid grasp of object scope, multithreading, and object-oriented programming in general. Android really doesn't cut newbies much slack, and the entire Android API pretty much takes for granted that you've completely mastered the finer points of advanced Java. Android *really* isn't the place to learn Java as your first real programming language. You can learn enough Java to scrape by and write Android apps that kind of work, but they'll never be *good* -- let alone *great* -- until you move up to the next level of expertise.

    46. Re:Andriod app development by Anonymous Coward · · Score: 0

      You are entitled to your opinion. Mine differs.

      You are entitled to my opinion. Yours differs.
      Sorry, I couldn't resist the wordplay, it was there for the taking.

    47. Re:Andriod app development by Coward+Anonymous · · Score: 1

      So you've described another form of "stick it in a global" which you admit is still susceptible to the app kill\restart problem. In practice, this is not really a problem because your app can just unwind itself and start afresh and the user will be fine with that.

      For reliable persistence you need to continually serialize your data which based on your detailed description you don't do either. I'll wager you don't do it because it is a cumbersome mess and are willing to pay the price of the app ocassionally not coming back in exactly the same state.

      Given that you don't do it and apparently most other devs don't do it there is something wrong with the design.

      Ironically, android activities were designed to allow this perfect restartability (by forcing the dev. to work like every activity is in a different memory space) and as a result are so ridiculously cumbersome to use. So cumbersome that everyone hacks around them and discards their design goals.

      There is nothing wrong with MVC.

      There is a huge problem with Android's architecture.

    48. Re:Andriod app development by PoopCat · · Score: 1
      If you're going to reply, at least reply to the word under discussion:

      said that it's "easier and more intuitive" - which it is. It's much easier

      .

  9. Updates to phones by dogmatixpsych · · Score: 4, Insightful

    I just hope that my phone gets updated to this. I'm still stuck with Froyo and my phone just came out in July. That's one of the most frustrating aspects of Android phones - the manufacturers do not upgrade the phones. With the quick turnover in phone OSes, it's inexcusable for manufacturers to stick with old OSes. I can understand if the phone hardware cannot handle the upgrade but I know that many phone manufacturers simply do not want to support their devices. Instead, to get updates we have to turn to CyanogenMod. This is one reason iPhones are so popular (yes, I know Android is overtaking iOS but the iPhone is the most popular smartphone model), at least Apple does a good job of updating iOS and getting it to as many iPhones as possible.

    All this being said, Android 4.0 looks great.

    1. Re:Updates to phones by mwvdlee · · Score: 1

      Assuming the driver model is compatible, upgrading Android really shouldn't be as troublesome as it is.
      It's a good point where iOS wins (though still by far not enough for me to even consider an iPhone).

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    2. Re:Updates to phones by spacepimp · · Score: 1

      I think the biggest issue here is that the manufacturers and wireless carriers are responsible for the updates to the OS. Leaving this to them means that they incur development costs, strain their networks with downloadable updates, and then support costs for failed upgrades or confused consumers. Then they consider that if they do nothing they save those headaches and people will upgrade their phones/tablets sooner. Then they choose the latter. This is an awful precedent to set for the post PC PC's. We have lost control and the legal right to upgrade our OS on the smartphone and tablet hardware we purchased, at least in the Android ecosystem. Apple doesn't have this issue as they forced the carriers hand to prevent this and it results in an improved customer experience. This is something that I sincerely hope Google/Android resolves in the near future. It is hard to defend Google/Android when forced obsolescence is part of your purchase agreement. There are time when there are security updates that take months to reach these devices. Is the manufacturer or carrier legally liable for failing to address these vulnerabilities in a timely manner? Perhaps when lawsuits start landing on their doorstep they will streamline or get out of the way of updates altogether.

    3. Re:Updates to phones by Anonymous Coward · · Score: 0

      I'm still stuck with Froyo and my phone just came out in July.

      I'm assuming your phone met your needs when you bought it because if it didn't, you should have got something else. I'm also assuming your phone still does everything it did when it came out in July. That's correct, right? If that is true, why mess with it? It's a smartphone, not a computer. I didn't get this nerd obsession with constantly changing a phone's interface every couple of months. If it meets your needs, you'd be a fool to fuck with the underlying system. My girlfriend has an Epic 4G from Sprint with Froyo. I mentioned to her a while back that Gingerbread should be coming out for it and the look of horror was priceless. She finally got a great phone and she's starting to feel sure of herself and "cool" that she's learned how to work it and you want the rug pulled out from beneath her one morning when she wakes up to realize that the damn thing has up and changed? Icons look different, settings are moved around... Yeah, right. A phone is an appliance. When's the last time you changed the OS on your microwave?

    4. Re:Updates to phones by Anonymous Coward · · Score: 0

      That's on the manufactures who layer on MotoBlur and other such garbage.

      Stock Android is a much easier upgrade as Google demonstrates with their Nexus phones.

      I would imagine as Android fills out and the costs associated with maintaining things like Blur are clear most will revert to stock android.

      People buy phones for the design, not the little tweaks you made to the stock OS.

    5. Re:Updates to phones by Anonymous Coward · · Score: 0

      Not going to happen. They want to to replace your device. That's how the market works. Cyano now works for Samsung, coinciding with their more rooting friendly attitude. Stick to Apple, but don't forget how new iOS updates kill old iphone performance and you cannot roll back.

    6. Re:Updates to phones by ironjaw33 · · Score: 1

      I think the biggest issue here is that the manufacturers and wireless carriers are responsible for the updates to the OS.

      Wireless carriers _want_ to be responsible so they can force their custom OS and bloatware on customers. Indeed, there are costs to do this, but ultimately, it's about control. It really ought to be like a PC where the Android phone calls home to Google and asks for daily updates and bug fixes.

      This fragmentation everyone talks about isn't a problem of hardware diversity, it is really a consequence of allowing wireless carriers to control Android updates.

    7. Re:Updates to phones by gclef · · Score: 1

      When's the last time you changed the OS on your microwave?

      When my microwave reads email, IMs, and browses the web, I'll update it's OS pretty damn regularly.

      (Honey, the popcorn's been hacked again!)

    8. Re:Updates to phones by oakgrove · · Score: 1

      There are millions of phones that do those things and never get upgraded.

      --
      The soylentnews experiment has been a dismal failure.
    9. Re:Updates to phones by Kev+Vance · · Score: 1

      Manufacturers and carriers that hold back Android updates are like IT departments that keep everyone on IE6. Developers have to decide whether or not to support new features given so many people running old versions. And if they do use the new features, do they lock out the old versions, or spend extra time writing workarounds and testing on those old versions?

      --
      F0 07 C7 C8
    10. Re:Updates to phones by Anonymous Coward · · Score: 0

      There's a key difference: Apple knows it's going to sell shit-tons of iPhones whatever they do, so pushing iOS upgrades until the phone slows to a crawl is a good strategy. Some Android OEMs withhold updates because they hope you'll buy a new phone for it, because there's tons of Android models and they feel they need to differentiate that way.

    11. Re:Updates to phones by Anonymous Coward · · Score: 0

      I just hope that my phone gets updated to this. I'm still stuck with Froyo and my phone just came out in July. That's one of the most frustrating aspects of Android phones - the manufacturers do not upgrade the phones. With the quick turnover in phone OSes, it's inexcusable for manufacturers to stick with old OSes. I can understand if the phone hardware cannot handle the upgrade but I know that many phone manufacturers simply do not want to support their devices. Instead, to get updates we have to turn to CyanogenMod. This is one reason iPhones are so popular (yes, I know Android is overtaking iOS but the iPhone is the most popular smartphone model), at least Apple does a good job of updating iOS and getting it to as many iPhones as possible.

      All this being said, Android 4.0 looks great.

      The creation of 4.0 is for the purpose of unifying devices, bringing the tablets and the phones together, though older phones will be left behind, just as the oldest iPhones can't really support the new versions of IOS. And by the way, Android has already overtaken IOS.

    12. Re:Updates to phones by Miamicanes · · Score: 1

      > I'm assuming your phone met your needs when you bought it because if it didn't, you should have got something else.

      You're assuming he's not American, more or less married to a specific carrier, and basically stuck with the half-dozen or so Android phones they have available at any moment in time. Want a slide-out keyboard? You've just eliminated 80-90% of them. Specifically want a 4.3+ screen that's LCD or a specific flavor of pentile (or non-pentile)? Your phone choice has basically been made for you, and you're stuck with that one specific model, regardless of what version of Android it ships with.

      > It's a smartphone, not a computer.

      Maybe it is to you. To most of us here on Slashdot, it's a pocket laptop with universal wireless connectivity, and is expected to behave like one.

    13. Re:Updates to phones by Miamicanes · · Score: 1

      They don't really care whether you replace your device, they just don't want to have to support it after you've taken it out of the box and activated it.

      Cyanogen is actually a wet dream come true for Samsung, because it effectively means they can outsource the ongoing support and development of their phones' OS to an army of highly-skilled, unpaid volunteers whose work is loosely coordinated by a single employee (who, as an employee, can be given access to proprietary stuff that they aren't allowed to release to the general public, like driver source from Qualcomm, and build custom CM-optimized kernels for those developers to work with). In business terms, Samsung hit the jackpot when they hired him. They get lots of goodwill from the people who'd complain the loudest, and clueless consumers will replace their phones on schedule anyway. They know they aren't losing sales, because people who aggressively run the latest and greatest Cyanogen tend to be the same people who chuck their phones and upgrade the moment their anniversary date arrives.

    14. Re:Updates to phones by Cajun+Hell · · Score: 5, Insightful

      That's one of the most frustrating aspects of Android phones - the manufacturers do not upgrade the phones.

      It's starting to look like one of Android's greatest weaknesses is that people flame manufacturers, but don't mention their name yet do mention Android's name in spite of the fact that Android had nothing to do with the problem they had.

      Dude: name names. Someone sold you an un-upgradable phone and you won't say who? Thanks, now they will be free to pull the same bullshit on me.

      If we were talking about desktop computers instead of phones, you wouldn't be talking shit about the OS not being upgradable; you'd be warning the world against the desktop computer manufacturer and their user-hostile BIOS.

      --
      "Believe me!" -- Donald Trump
    15. Re:Updates to phones by tlhIngan · · Score: 1

      I just hope that my phone gets updated to this. I'm still stuck with Froyo and my phone just came out in July. That's one of the most frustrating aspects of Android phones - the manufacturers do not upgrade the phones. With the quick turnover in phone OSes, it's inexcusable for manufacturers to stick with old OSes. I can understand if the phone hardware cannot handle the upgrade but I know that many phone manufacturers simply do not want to support their devices. Instead, to get updates we have to turn to CyanogenMod. This is one reason iPhones are so popular (yes, I know Android is overtaking iOS but the iPhone is the most popular smartphone model), at least Apple does a good job of updating iOS and getting it to as many iPhones as possible.
       

      You didn't buy an Android phone. You bought an Android *COMPATIBLE* phone.

      There are now TWO Android phones out there on the market - Nexus S and Nexus Prime or whatever it's called. These obey the same reasons why we hate iOS - and these phones give complete freedom very easily. The compatible phones, they have to be "rooted" and "unlocked" to get to that point. Sure it's trivially easy on a lot of phones, but it's just like jailbreaking on iOS - why do you have to do it? Rooting/unlocking is trivial on a real Android phone (instructions are out before you can get your hands on it - Google publishes it!).

      And you can always get the latest updates immediately - just update your tree and build it.

      Android is just a phone OS that OEMs and carriers pervert to their will. The best bet is to with as pure Android as possible, which means going with the Google phones.

      Apple can do it because they've told carriers to bend over and take it. Google's pretty much done the same. HTC, Samsung, LG, ... nope, they'll bend to carrier's wishes.

      And nevermind about the AOSP based phones.

    16. Re:Updates to phones by Sez+Zero · · Score: 1

      So can you jailbreak an Android phone and update the OS to the latest yourself? Is there a blog or tracker anywhere with a phone-OS-company matrix that shows who lets you use what on what?

      Hard to believe that I don't have a smart phone, but I now find myself needing to replace my burner pay-as-you-go with something real. I have an iPod Touch and have obviously looked at the iPhone, but the Android (especially the ICS phones) are intriguing. The only problem is it is hard to tell what's what. I don't want to go out and buy a new phone to find out that I can't get the latest OS on it. I know that it will have a limited lifespan, but I definitely don't want to get stuck with Eclair or Froyo.

    17. Re:Updates to phones by Sloppy · · Score: 1

      It's a smartphone, not a computer. .. A phone is an appliance.

      Smartphones are PCs. Indeed, being thought of and used as a "computer," and being extensible to handle new applications that the manufacturer never thought of, is practically what distinguishes a smartphone from a dumbphone. Being totally-unlike-an-appliance was the essense of the iPhone1'z buzz.

      When is the last time you installed a new application on your microwave? When's the last time your microwave interacted with an upgrading world over a network, perhaps through a web browser? If you did those things with your microwave, you would expect it to be upgradable.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    18. Re:Updates to phones by gauauu · · Score: 2

      So can you jailbreak an Android phone and update the OS to the latest yourself? Is there a blog or tracker anywhere with a phone-OS-company matrix that shows who lets you use what on what?

      Yes or no, depending. (And thus the problem).

      Some phones have the bootloader locked so you can't do that. (Although often there's a hack to unlock it).

      Then the problem is drivers -- you can't install stock Android updates on your device and expect all the components to work correctly, as they all have slightly different hardware.

      There are many 3rd party ROMs that package up Android releases for various phones (cyanogenmod is one of the most popular). If there's a cyanogenmod build for your specific phone, then yes, you can flash that on your phone to upgrade (it will replace everything that was there before).

      If there's not any 3rd party roms (I have the wifi-only 7" galaxy tab, and nobody has released ANYTHING for it), then you are our of luck, unless you are proficient enough to build your own rom (which chances are, you aren't).

    19. Re:Updates to phones by johnthorensen · · Score: 1

      Another reason I'm a fan of Android though (see my other post to this thread), is that every update has actually made my Droid Incredible *faster*, or at least not any slower.

      The phone is just as capable as the day I got it, and even though I consider myself an advanced user I have yet to see any reason to upgrade. The only real features that have been added to smartphones since its release are front-mounted cameras and faster/dual-core CPUs. I could care less about the front-mounted camera; while the upgraded CPUs are nice on Javascript-heavy websites and such, it's not enough of a difference for me yet to upgrade.

      I say this as a user or former-user of just about every smartphone platform under the sun (extending all the way back to Palm's first phones, but admittedly with the exception of Blackberry), and I don't think I've ever kept a single phone for so long. This includes a couple of iPhones - where I certainly *did* complain about the slowdown that seemed to come with every new iOS release.

    20. Re:Updates to phones by loconet · · Score: 1

      "the manufacturers do not upgrade the phones"

      Stop buying non "Google experience" phones. I've stuck with the Nexus series ever since the HTC fiasco in Canada with the OS upgrades. Couldn't be happier.

      --
      [alk]
    21. Re:Updates to phones by Anonymous Coward · · Score: 1

      Motorolla Atrix. Marvelous phone, but they have made it their mission thar the user cannot update a thing.
       
        Actually, make that all of Motorolla. They have taken the walled garden approach. They sell their hardware, and tailor the software to it so no user can complain about their phone suddenly not working if the user broke it. I presume they are trying to be the apple of Android phones. Which is great, so long as you don't buy their hardware with the assumption of easy hacking.

    22. Re:Updates to phones by dogmatixpsych · · Score: 1

      Ok, the manufacturer is Motorola (actually Huawei made the phone for Motorola but it is Motorola branded and they claim it for support).

    23. Re:Updates to phones by dogmatixpsych · · Score: 1

      "You didn't buy an Android phone. You bought an Android *COMPATIBLE* phone."

      True. But Google's problem was that they initially allowed any manufacturer and/or carrier to modify Android as needed. In theory this is a great idea but what's happened is manufacturers will often release a phone and then stop caring about it (anecdotally, this is the norm across all carriers in the U.S. and most phone brands based on my talking with people I know with Android "compatible" phones). That attitude works just fine with traditional cell phones but is poor customer service with smart phones.

    24. Re:Updates to phones by dogmatixpsych · · Score: 1

      I would but there are no "Google" phones on my carrier and the cost of switching carriers would be prohibitively expensive for me (on the order of >$700 a year). I'm not complaining; I like my phone and my carrier is just fine but having to rely on "the community" for OS updates is telling of a manufacturer's attitude towards its customers.

    25. Re:Updates to phones by scot4875 · · Score: 1

      So can you jailbreak an Android phone and update the OS to the latest yourself? Is there a blog or tracker anywhere with a phone-OS-company matrix that shows who lets you use what on what?

      Find for a phone you like, use Google to find out if you can install an alternate ROM on it. It's not that tough. Of course, you might not be able to buy the latest and greatest on day one, because nobody knows whether or not it'll be hacker friendly, but that's just how it works if this is an important feature for you.

      --Jeremy

      --
      Jesus was a liberal
    26. Re:Updates to phones by Anonymous Coward · · Score: 0

      I bought an Android phone, and they've kept me updated for the past two years AND they've come out with the updates within a month or two of general availability.

      Take a guess which device! :D

    27. Re:Updates to phones by Bill_the_Engineer · · Score: 2

      It's starting to look like one of Android's greatest weaknesses is that people flame manufacturers, but don't mention their name yet do mention Android's name in spite of the fact that Android had nothing to do with the problem they had.

      That's because pretty much ALL of the Android phones have this problem. The only phones I know that *may* not have a problem are the ones commissioned by Google.

      Dude: name names. Someone sold you an un-upgradable phone and you won't say who? Thanks, now they will be free to pull the same bullshit on me.

      Okay: HTC, Motorola, and Samsung. Pretty much any Android phone sold through a phone carrier.

      If we were talking about desktop computers instead of phones, you wouldn't be talking shit about the OS not being upgradable; you'd be warning the world against the desktop computer manufacturer and their user-hostile BIOS.

      Two totally different things. Nice try deflecting blame but we all knew this was going to happen when manufacturers were allowed to make changes to the OS in an attempt to differentiate themselves from the other Android phones.

      This is just the nature of the beast. You can't have a pseudo-open phone OS and not expect fragmentation caused by the hardware makers. If you use your desktop computer comparison, you could think of these modifications as one step above the crapware pre-installed on your PC computer.

      Also why would a manufacturer spend money updating your phone when they rather you buy a new one? The only way this can be solved is by Google owning up to the task of building the OS and pushing it out to the manufacturer to install on their phone (like OEM MS Windows). I don't see this happening in the near future, so the best advice I can give you is to accept the limitations of the Android universe and don't take it personally when people point it out.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    28. Re:Updates to phones by gclef · · Score: 1

      ...and they're vulnerable to being hacked (and don't think for a minute that cell phone malware doesn't exist). That's my point.

    29. Re:Updates to phones by farnsworth · · Score: 2

      Also why would a manufacturer spend money updating your phone when they rather you buy a new one?

      I'm sure Apple would also rather everyone buy a new iPhone every year, and yet they bend over backwards to get the latest OS working on every conceivable model they have sold. Same with the Google phones, from what I understand.

      The manufacturers who ship Android phones and then never publish updates obviously don't care one bit about their customers experience. It's as if they don't even perceive the people they sell to as "customers", but rather as "transaction generators". This approach might work fine for these businesses, but it's bad for the people who end up buying from them.

      --

      There aint no pancake so thin it doesn't have two sides.

    30. Re:Updates to phones by CWCheese · · Score: 1

      So can you jailbreak an Android phone and update the OS to the latest yourself? Is there a blog or tracker anywhere with a phone-OS-company matrix that shows who lets you use what on what?

      There is the group at www.xda-developers.com where you can get all the tools needed to jailbreak/root your Android phone. Also, www.androidcentral.com, www.androidforums.com, etc. which have very well organized forums for each Android device - whether phone or tablet.

      --
      Have a Day!
    31. Re:Updates to phones by Anonymous Coward · · Score: 0

      I think that is the kind of thing Apple was talking about when they said Android led to a fragmented experience.

    32. Re:Updates to phones by Anonymous Coward · · Score: 0

      Dude: He did name names. "The manufacturers" refers to the manufacturers. All of the ones offering Android phones.

    33. Re:Updates to phones by Anonymous Coward · · Score: 0

      Worst parts of Android: the manufacturers and the carriers.

    34. Re:Updates to phones by Keen+Anthony · · Score: 1

      Really? I still update my Droid too, and it's gotten slower and slower. It's now at the point that the UI lag is so noticeable that it's no longer worth it to me to use the Droid. I just upgraded to iOS 5 on my iPhone 4 and it's no slower. I'm still holding out for a new Droid, but I'm waiting to see if Windows Phone offers me anything. Like you, I've had just about everything, but I did have Blackberry and didn't have a Palm based mobile.

    35. Re:Updates to phones by Anonymous Coward · · Score: 0

      That's because pretty much ALL of the Android phones have this problem. The only phones I know that *may* not have a problem are the ones commissioned by Google.
      Okay: HTC, Motorola, and Samsung. Pretty much any Android phone sold through a phone carrier.

      Samsung and Motorola have both updated their phones to Gingerbread. I don't know about HTC, but you're clearly not very well informed.

    36. Re:Updates to phones by AmiMoJo · · Score: 1

      That's because pretty much ALL of the Android phones have this problem. The only phones I know that *may* not have a problem are the ones commissioned by Google.

      Some manufacturers are getting better, such as Samsung and HTC. My Samsung Galaxy S is updated regularly now after a bit of a slow start when it first came out. They have realised there is demand in the market for updates.

      Ice Cream Sandwich should improve things further. One of the design goals was to allow easier updates, and to allow more of the built-in apps to update independently.

      Also why would a manufacturer spend money updating your phone when they rather you buy a new one?

      Ask Apple? Actually there is no need, the reason is obvious. Most people get their phones on contract, meaning they are stuck with them for 18 or 24 months. If a manufacturer doesn't support them they are not going to get another phone from them when their contract is up.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    37. Re:Updates to phones by Bill_the_Engineer · · Score: 1

      I was expressing the attitude of HTC and Motorola. Apple doesn't have this attitude.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    38. Re:Updates to phones by DaVince21 · · Score: 1

      With the iPhone, the responsibility lies solely at Apple. With Android phones, the responsibility lies at many different companies for their own phones... That's where the problem lies, mainly. Better get a phone from a manufacturer that's known for getting updates for your phone.

      --
      I am not devoid of humor.
    39. Re:Updates to phones by Bill_the_Engineer · · Score: 1

      Yay! Samsung and Motorola finally and recently upgraded to Android 2.3. Yet here we are talking about Android 4.0.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
  10. Compatibility by theswimmingbird · · Score: 1

    I've really been thinking about purchasing the Samsung Galaxy Player 5. I don't have a need for a smartphone as I find wifi + Google Voice to be more than adequate to meet my needs since I shut down my Verizon account and kept my Droid. It's like having a portable landline; I can go to the park without being tied into an endless stream of information.

    Are these PMP devices rootable? And will custom ICS ROMs support them?

  11. But it's so much fun by RussellSHarris · · Score: 1

    What would you do for an Android SDK?

  12. (Google account required) by Anonymous Coward · · Score: 0

    The link to that thread seems to work fine for me without a Google account. Is there more that I'm missing?

  13. Ultimate Yawnsauce. by L4t3r4lu5 · · Score: 1

    Where's the full disk encryption? I shouldn't have to rely on a 3rd party app like that Whisper Systems product to provide some fundamental data security for the device.

    Considering what these devices are connected to (social networking, email, contacts, pictures etc) you'd think that this was a higher priority than a new font for the clock.

    --
    Finally had enough. Come see us over at https://soylentnews.org/
    1. Re:Ultimate Yawnsauce. by Gaygirlie · · Score: 2

      Honeycomb does provide that, so I would also imagine ICS providing that. Perhaps someone just forgot to mention it?

    2. Re:Ultimate Yawnsauce. by L4t3r4lu5 · · Score: 2

      Pretty big thing to fail to mention! It's fundamental to Android being a contender to Blackberry in the corporate world.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    3. Re:Ultimate Yawnsauce. by chowdahhead · · Score: 1
    4. Re:Ultimate Yawnsauce. by Hatta · · Score: 1

      If Google provided full disk encryption, would you trust it?

      --
      Give me Classic Slashdot or give me death!
    5. Re:Ultimate Yawnsauce. by Gaygirlie · · Score: 1

      Well, it seems I was indeed correct, the other poster did provide with a link that confirmed that there is indeed full device-wide encryption on ICS, too. And yes, I agree that it is an important thing to mention and the fail is pretty hefty.

    6. Re:Ultimate Yawnsauce. by Gaygirlie · · Score: 1

      If Google provided full disk encryption, would you trust it?

      Why not? They already have access to your data, the encryption is to keep outsiders from accessing it.

    7. Re:Ultimate Yawnsauce. by Hatta · · Score: 1

      Really? I haven't used android, so this may be a stupid question. Is everything stored in the cloud? Are android tablets just completely unusable without a network connection?

      --
      Give me Classic Slashdot or give me death!
    8. Re:Ultimate Yawnsauce. by PoopCat · · Score: 1

      Yes, no, and no. In that order.

    9. Re:Ultimate Yawnsauce. by Hatta · · Score: 1

      Ok, so why did the GP assert that google already has access to your data. If it's locally stored, how does google have access to it?

      --
      Give me Classic Slashdot or give me death!
    10. Re:Ultimate Yawnsauce. by johnthorensen · · Score: 1

      You do have the option to use your Google account to backup certain things. I also know that when you log into a new device with the same Google account you used on another one, you have access to re-download (not re-BUY - good for them) any apps which you have purchased to the new device.

    11. Re:Ultimate Yawnsauce. by Anonymous Coward · · Score: 0

      By writing the software which runs on the device.

    12. Re:Ultimate Yawnsauce. by Hatta · · Score: 1

      OK, but if I write a text file, and save it on my tablet, there's no way Google can read that text file, right? If that's the case, gaygirlie's assertion that google has all my data is false. I think we're only having this discussion because gaygirlie said something stupid.

      --
      Give me Classic Slashdot or give me death!
    13. Re:Ultimate Yawnsauce. by scot4875 · · Score: 1

      No, and no.

      --Jeremy

      --
      Jesus was a liberal
    14. Re:Ultimate Yawnsauce. by Gaygirlie · · Score: 1

      OK, but if I write a text file, and save it on my tablet, there's no way Google can read that text file, right? If that's the case, gaygirlie's assertion that google has all my data is false. I think we're only having this discussion because gaygirlie said something stupid.

      It was a sarcastic remark, I didn't think anyone would actually take it for real :S

    15. Re:Ultimate Yawnsauce. by Hatta · · Score: 1

      Ah, it's been a while since I misinterpeted sarcasm on the internet. Guess it'll always happen once in a while. Apologies if I offended.

      --
      Give me Classic Slashdot or give me death!
    16. Re:Ultimate Yawnsauce. by Bucky24 · · Score: 1

      Theoretically they could access it via the OS itself (by backends built into the operating system) over the cell network. I rather doubt this actually exists, but it is possible, and a lot of anti-Google or just tin foil hats around here seem to think that every phone has a backdoor built into it.

      --
      All the world's a CPU, and all the men and women merely AI agents
    17. Re:Ultimate Yawnsauce. by Anonymous Coward · · Score: 0

      I missed it the first time I read it too, but the first link in the summary has a sidebar entitled "Key Android 3.x developer features, now for phones too", stating "Full device encryption".

    18. Re:Ultimate Yawnsauce. by Sark666 · · Score: 2

      Why isn't multi-user support not more important? Maybe not so much in phones, but definitely tablets. If I am at my bro's and my nephew wants to play angry birds on my tablet, I should be able to hand it to him with confidence that he can't see my emails etc. And maybe a limited user (guest) account that can't install/uninstall stuff etc. Why does it have to be like win98 again?!

    19. Re:Ultimate Yawnsauce. by Anonymous Coward · · Score: 0

      They did mention it. They said: "All the features of Honeycomb AND [x features]"

      You were supposed to already know that honeycomb had this shit.

  14. Simpler answer by V.+P.+Winterbuttocks · · Score: 3, Funny

    Use a body part that isn't visible in your ID photo.

    --
    I'm the real Vorokrytin P. Winterbuttocks.
    1. Re:Simpler answer by fran6gagne · · Score: 1

      But be careful on which part you use, because you will have to expose it each time you want to unlock your phone.

    2. Re:Simpler answer by jeffmeden · · Score: 1

      Facial recognition is not just a "how much does this pic look like that pic" type of operation. The algorithm (or a useful algorithm anyway) looks at the key metrics of your face, such as pupil separation vs distance from eyes to mouth (to judge distance and aspect ratio) and then looks at nose size, jaw width, ear width, and a number of other features to determine if the two faces are identical. Otherwise, you would lock yourself out of your phone (in this case) by simply growing a beard or adding/removing glasses from your face (something a true recog algo has no problem overcoming).

    3. Re:Simpler answer by V.+P.+Winterbuttocks · · Score: 1

      You make it sound almost like that's a bad thing.

      --
      I'm the real Vorokrytin P. Winterbuttocks.
    4. Re:Simpler answer by Anonymous Coward · · Score: 0

      Good or bad, I don't know. But I know that there are countries where it is illegal to show specifics body parts in public.

    5. Re:Simpler answer by Anonymous Coward · · Score: 0

      Not in the toilets.

  15. ICS... by Anonymous Coward · · Score: 0

    It looks and feels like Honeycomb, which I have used on a tablet. For mobile phones, this is a substantial boost,
    but not that much for tablets. I actually expected more tweaks to it, and that they solve all those effects.

    IMHO, it's not up to the hype that was following it. It's all polish and refinement, no stunning new features that'd prompt Jobs to pick up chalk and go back to the drawing board. Oh, and I hope Google patented, for defensive use, every bit of that face recognition gimmick.

    Also, Apple makes much of a show when new phone is released. Here, they didn't even show tablet capabilities of 4.0., only the SG Nexus.

    1. Re:ICS... by Gaygirlie · · Score: 1

      no stunning new features that'd prompt Jobs to pick up chalk and go back to the drawing board

      If Google actually managed to get Jobs to pick up chalk and start innovating again that would SURELY generate some ginormous press.

  16. It's not always whether the phone can support it by Quila · · Score: 1

    Mine technically supports 2.3 if I wanted to root and load my own OS, but the manufacturer/carrier only went to 2.1. It's the manufacturers and carriers: They sold you the phone, they don't give a damn about you anymore. Wait until the next upgrade cycle so they can sell you a new phone. At least Apple supports phones with the latest version for at least two years after release.

    And by the way, Android has already overtaken IOS.

    And the only relevance that has is for developer support, which is irrelevant since both platforms have easily surpassed critical mass. Also, your statement isn't just restricted to phones. You have to include all iOS devices: phones, tablets and the iPod Touch (and possibly Apple TV, although you don't get the App Store for that). This pushes iOS much higher than Android.

    If you want to talk only smartphones, then Apple is outselling them all.

  17. Finally by ncohafmuta · · Score: 1
    From the platform highlights..

    VPN client API
    Developers can now build or extend their own VPN solutions on the platform using a new VPN API and underlying secure credential storage. With user permission, applications can configure addresses and routing rules, process outgoing and incoming packets, and establish secure tunnels to a remote server. Enterprises can also take advantage of a standard VPN client built into the platform that provides access to L2TP and IPSec protocols.

    this, to me, is the most signifigant part of the release. End-users and IT people have been asking for this forever.

  18. Samsung Nexus official specs by Flu · · Score: 1
    Samsung Sweden today issued a pressrelease with the Samsung Nexus and Android 4.0 specifications:

    4,65" hd super-amoled display, 1280x720 pixels
    1,2 gigahertz dual-core
    HSPA+ 21Mbps DL; HSUPA 5.76Mbps UL
    Size: 135,5 x 67,94 x 8,94 millimeter, 135 gram
    16GB internal memory
    Front cam 1,3 mipxel for videoconf
    Back cam 5 mpixel
    NFC, Bluethooth 3.0, wifi 802.11 a/b/g/n, usb 2.0

    More information at http://www.samsung.com/se/news/newsRead.do?news_group=productnews&news_ctgry=&news_seq=29470

    1. Re:Samsung Nexus official specs by Anonymous Coward · · Score: 0

      Oh boy! Spec list! You just made a million filthy geeks climax!

      And, yeesh, you people with your decimal commas.

    2. Re:Samsung Nexus official specs by doti · · Score: 1

      It's good to see they didn't increase the megapixel of the camera.
      Without a bigger/better sensor, it does not give a better picture quality, just a bigger file to waste space and processing time.

      But 1080p movie recording would be nice.

      --
      factor 966971: 966971
  19. Obligatory XKCD by johnthorensen · · Score: 1

    Well, at least now they can just hold the phone up to your face while you're tied up instead of beating you senseless with a $5 wrench...

    http://xkcd.com/538/

  20. Droid Incredible has received *every* OS update! by johnthorensen · · Score: 1

    I've actually been very pleased with the update support from Verizon/HTC for my aging Droid Incredible (original, not version 2). This phone started out with 2.1 (Eclair), and shortly received an update to 2.2 (Froyo). The phone was actually 'end-of-life'd this past March but that didn't stop them from providing an update to 2.3 (Gingerbread - the latest version available for phones prior to 4.0's imminent release) just this past September. These are all vendor-sponsored updates mind you, no CyanogenMod required.

    So essentially, I've been provided with an update to the latest Android every time a new version has come out since the release of the phone. Can't ask for much more than that.

    That's not to say that I'm necessarily expecting an update to 4.0 (Ice Cream Sandwich), but with today's uber-short product lifecycles I'm pretty happy with the support for this 1.5-year-old phone. And if they *do* update the Droid Incredible to 4.0, that's going to significantly enhance my loyalty to Verizon/HTC to the point where I'll probably insist on the same carrier/vendor when I upgrade.

  21. Embrace, extend, extinguish? by wick3t · · Score: 1

    So Google suck in various OEMs and open source enthusiasts, release two major upgrades and still not release the source code? I'll stick with MeeGo/Mer/Tizen, etc. thank you very much.

    1. Re:Embrace, extend, extinguish? by Anonymous Coward · · Score: 0

      They're planning on doing it once they recover from their hosting service being compromised. It's in the summary, you didn't even have to read the article to know that.

  22. Yes, this feature exists. by jvonk · · Score: 1

    Google/Samsung/et al. don't have a separate timeout for slide lock & security lock feature. This was originally an HTC Sense feature but now is also available in CyanogenMod.

    Why CyanogenMod? Well, that's because after I wrote the code to replicate & improve upon the Sense feature, I only submitted a patch to CyanogenMod. (Hey, it's what I use...)

    The feature is in CyanogenMod 7.1 or later, and any other ROMs that pull from CM 7.1 as an upstream. As stated before, a similar feature is also found in HTC Sense-derived ROMs. However, HTC's implementation isn't as versatile as mine, so I suggest you disregard that and just use CM instead (haha).

    Pull the source if you want; port it anywhere you like:
    Framework code
    UI code

    1. Re:Yes, this feature exists. by Asic+Eng · · Score: 1

      Cool, yeah I think I'll switch to CyanogenMod eventually.

  23. I took a look at ICS last night by Dennis+Sheil · · Score: 3, Interesting

    I do Android development, and I had a look at the SDK and emulator when it was released last night. I created an emulator and was testing my applications out on it.

    The first thing I noticed is that there are more help screens. I believe they disappear after first use, but they tell users how to navigate around the phone. Or tablet as it may be - that's probably the biggest thing about ICS, it integrates Gingerbread (smartphones) and Honeycomb (tablets) into one OS. I've been getting the hang of Android layout, and it is not so hard once you get used to it, you just stick with the things they recommend - density-independent pixels, scale-independent pixels, objects sized by width and/or height by fill-parent (fill layout container object is in) or wrap-object (make object only as large as it need be), objects or layout containers being assigned by weight. One trick I learned - I start design with the smallest device - WVGA - a small device with a low number of dots per inch. I do a portrait (device held with more height than width), and if I have time a landscape (device held with more width than height) view. Sometimes that is enough, and those two layouts work from the smallest to largest devices. Usually it requires a little tweaking, especially Activity classes that make use of buttons. You take the layouts you made and increase text size, increase the distance between objects and other objects, or objects and the edge of the screen. Some people rethink the design, they use Fragments so that where something that would be done on a small screen with ten screen changes with ten different Activity views, is now done with five screen changes with the same ten different Activity views - you just use Fragments to put two or so Activity views per screen. The ICS smartphone/tablet integration will help in that department, although you can do it to some extent already. In fact Fragments were introduced in Honeycomb (the old tablet Android version, before this ICS tablet/smartphone integration), so some of this is just bringing Honeycomb advances back to the smartphone. Another example of this is the Actionbar - over time the Android designers realized it would help UI consistency, ease of programming etc. if they put a bar on top that let people do things (open an email, go to the next page, whatever). So Actionbar was in Honeycomb, now it is in ICS as well. I should mention there is a compatibility package which allows apps to use many (but not all) of these new features on older phones like Gingerbread, Froyo, Eclair etc.

    The next thing I noticed when looking at my apps in the ICS emulator is the new Roboto font. It is said to be able to be a good font for everything from a small, low density to a large screen with a high density. Some of my apps use the Android non-default fonts, and the ones I looked at looked most the same, although there may have been small tweaks I did not notice. And Android lets you use your own fonts.

    One of my applications runs in the background, doing a database search while updating a progress bar - and while all of this is happening, an ad is often being loaded as well via the web. It seems to be stalling on something in the ICS emulator, I will do some debugging later to see where it is getting stuck. It may be one of those cases where I was doing something wrong but Android allowed it, and they increased the strictness of things. With ICS's use of Fragments, I can probably just load one ad Fragment when my app starts and put that on every screen anyhow.

    Regarding source code, I'm sure it will be released. It will be a month or so before you can buy a Samsung Galaxy Nexus anyhow. The sooner the release the better for me, but Android's open nature beats Windows 8 Mango and iOS any day. I can sit at my Linux box, use open source tools to develop everything, and then just push it out to Android Market (or some other market - Android does not lock phones to their store like Apple does). It is beyond me why Apple punishes developers with an app sto

    1. Re:I took a look at ICS last night by Sark666 · · Score: 1

      It doesn't sound like your apps need it but there's not much mention of hardware acceleration, which I'm probably more excited about that than other new features. It's not about eye candy, but touch displays typically have menus and icons moving around so responsiveness matters.

      I'm hoping it will be relatively easy for developers to take advantage of this for current apps.

  24. Re:It's not always whether the phone can support i by Anonymous Coward · · Score: 0

    If you want to talk only smartphones, then Apple is outselling them all.

    If you want to talk only smartphones, then Android is outselling iOS. There's no reason why the manufacturer should magically become more relevant than the OS just because you're talking about a specific type of device.

  25. Full disk encryption is present by manekineko2 · · Score: 2

    This is from one of the Android devs:
    https://plus.google.com/112413860260589530492/posts/DDTKFhiDS9U

    "Support for Encryption for Phones
    Honeycomb added full-device encryption, but ICS brings it to phones."

    Guess they figured it too boring for the launch demo.

  26. GPL by Raenex · · Score: 2

    Like we did for all Honeycomb release, this is NOT the full source tree for IceCreamSandwich, these are only the GPL parts that are in the SDK (along with a few associated files), and they're not enough to build the whole IceCreamSandwich for a device.

    One of the fundamental principles behind the GPL is that if you used GPL parts to make a whole work, then the whole work must also be GPL:

    "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. "

    "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. "

    It's quite obvious that "IceCreamSandwich" is a whole work, and that it contains GPL parts.

    1. Re:GPL by Anonymous Coward · · Score: 1

      It's not obvious at all, particularly since it isn't the case. "It's obvious" is a way to avoid stating your position and having everyone just agree, because only a fool would not see the obvious.

    2. Re:GPL by Raenex · · Score: 1

      Can you explain how it isn't a "whole"? Can you explain why the developer I quoted used the words parts and whole himself? It seems obvious to me, and you haven't prevented any evidence to the contrary.

    3. Re:GPL by shutdown+-p+now · · Score: 1

      It's not a "whole work", just like pretty much any Linux distro out there is not "whole" - it's a mere aggregation of many different programs and libraries, each of which may have its own license.

    4. Re:GPL by Raenex · · Score: 1

      "mere aggregation" is bullshit. Ice Cream Sandwich is a name to describe the whole: a functioning operating system for smart phones and tablet computers. The parts operate together to provide the function of the whole. If it was just "mere aggregation" there wouldn't be any relation among the parts.

    5. Re:GPL by shutdown+-p+now · · Score: 1

      Like I said, by your logic, any Linux distro would also be a single "functional operating system", and as such would have to be licensed entirely under GPL as a single work - and any non-GPL-compatible components would have to be purged. This is demonstrably not the case in practice, and that's because the meaning of "work" is pretty narrow in practice. FSF itself has long acknowledged that different program binaries (but not shared libraries) constitute different "works" for the purposes of GPL, so even if they are designed to work together (via pipes or sockets or whatever), one being GPL'd does not place any requirements on the other. And FSF has one of the more far-reaching interpretations of GPL - quite a few disagree with their claim regarding shared libraries, for example.

    6. Re:GPL by Raenex · · Score: 1

      Like I said, by your logic, any Linux distro would also be a single "functional operating system", and as such would have to be licensed entirely under GPL as a single work

      Just because people ignore the GPL doesn't mean it isn't being violated.

      FSF itself has long acknowledged that different program binaries (but not shared libraries) constitute different "works" for the purposes of GPL, so even if they are designed to work together (via pipes or sockets or whatever), one being GPL'd does not place any requirements on the other.

      The FSF has some stances that are not explicitly stated in the GPL and that I don't agree with. What really matters is what the license says and what happens when you take it to court to enforce it. It's rather silly to presume that wrapping a library in sockets instead of linking to it all of a sudden makes something no longer a derivative work.

      It's one thing to code to an interface and letting the user download non-GPL components (as Nvidia does with their Linux drivers), but it's quite another to ship all the components that implement the interface as a functional whole while claiming "mere aggregation".

    7. Re:GPL by shutdown+-p+now · · Score: 2

      See, that's why I don't like GPL - everyone has their own favorite interpretation of it, and they are often wildly different. According to yours, it would seem that even using a GPL'd web service in a program would make that program a "derived work" of the service. I'm glad to say that it's not a particularly popular one, but you are of course entitled to it - we'll never find out who's right until a court rules on this, and even then I expect it might arrive at different answers in different jurisdictions.

      Just to address one point:

      It's rather silly to presume that wrapping a library in sockets instead of linking to it all of a sudden makes something no longer a derivative work.

      It's rather silly indeed, which is why many people believe that FSF's interpretation of dynamic linking as a single "derived work" is flawed - precisely because it's not really any different from IPC. In both cases, you have a well-established protocol by which two clearly disjoint parts communicate. Either part could be swapped out and replaced by a different one that conforms to the same protocol. It needn't even do the same thing, functionality-wise, just provide the minimum that's required by the other side - e.g. libreadline replacement could ditch all history, completion etc and just wrap fgets. Clearly, once you have two implementations of one of the parts, only one of which is GPL'd, and both of which are drop-in replacements for one another, the second part is in no meaningful way a derived work.

      Heck, even Stallman himself had to admit that the logic is sound - his final argument in a dispute over whether GPL applies to CLisp because the latter links dynamically to libreadline was, basically, a panicky "I'm afraid that this workaround might work for you and set a precedent, and it's going to be real bad for us - can you please not do that?"

      Static linking is clearly covered, because there's a single artifact produced as an output, which contains machine code produced from both GPL'd and non-GPL'd source code intermixed together - it's hard to argue that it is a single, atomic work, and that said work is "derived" from the GPL'd code.

    8. Re:GPL by Anonymous Coward · · Score: 0

      I think you are confused. The Linux kernel is an independent piece of code. I can show that it's independent in that GNU will run with a Linux kernel just as well as Android. It is specifically stated in many places that the Linux kernel is intended to be used this way and that anything you run on top of the kernel can be licensed any way you want.

      The GPL "parts" of Android are the Linux kernel (I'm not sure if there is anything else -- I can't remember if they eventually started distributing the C library for instance, but it has similar disclaimers). I would be very happy if the whole of Android was GPLed, but it isn't and doesn't have to be. The only people who have any standing in the matter are the copyright holders of the GPLed code and they are quite happy with the situation.

    9. Re:GPL by Raenex · · Score: 1

      According to yours, it would seem that even using a GPL'd web service in a program would make that program a "derived work" of the service. I'm glad to say that it's not a particularly popular one, but you are of course entitled to it

      No, I never said that. That's your strawman. What counts is what you distribute, which I directly quoted from the license: "But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License"

      Android is distributed as a whole on the devices they ship on.

      It's rather silly indeed, which is why many people believe that FSF's interpretation of dynamic linking as a single "derived work" is flawed - precisely because it's not really any different from IPC.

      As I already stated, I don't agree with the FSF's interpretation. I read the license and look at the law. What counts is distribution. It's well established, in US courts at least, that writing to an interface is allowed and does not break copyright. What does break copyright is when you distribute code you don't have rights to.

      Heck, even Stallman himself had to admit that the logic is sound - his final argument in a dispute over whether GPL applies to CLisp because the latter links dynamically to libreadline was, basically, a panicky "I'm afraid that this workaround might work for you and set a precedent, and it's going to be real bad for us - can you please not do that?"

      I read your link, and you are either lying, willfully ignorant, or did not read the whole thread. I don't even agree with his position, and yes, he did appeal to what was good for GPL, but in the end this is what he said:

      "The FSF position would be that this is still one program, which has only been disguised as two. The reason it is still one program is that the one part clearly shows the intention for incorporation of the other part.

      I say this based on discussions I had with our lawyer long ago. The issue first arose when NeXT proposed to distribute a modified GCC in two parts and let the user link them. Jobs asked me whether this was lawful. It seemed to me at the time that it was, following reasoning like what you are using; but since the result was very undesirable for free software, I said I would have to ask the lawyer.

      What the lawyer said surprised me; he said that judges would consider such schemes to be "subterfuges" and would be very harsh toward them. He said a judge would ask whether it is "really" one program, rather than how it is labeled."

      Static linking is clearly covered, because there's a single artifact produced as an output, which contains machine code produced from both GPL'd and non-GPL'd source code intermixed together - it's hard to argue that it is a single, atomic work, and that said work is "derived" from the GPL'd code.

      Now apply that same logic to Ice Cream Sandwich. They distribute a complete operate system. If they removed the GPL parts it wouldn't function the same. Now why does it matter that it's statically linked or not? The GPL doesn't limit itself to static linking.

    10. Re:GPL by Raenex · · Score: 1

      The Linux kernel is an independent piece of code. I can show that it's independent in that GNU will run with a Linux kernel just as well as Android. It is specifically stated in many places that the Linux kernel is intended to be used this way and that anything you run on top of the kernel can be licensed any way you want.

      The Linux kernel is released under the GPL and has many authors. No single author can dictate an alternative license.

      The only people who have any standing in the matter are the copyright holders of the GPLed code

      Legally, that's true. That doesn't mean I can't call them out for violating the GPL.

  27. Apple can play that game, too by emblemparade · · Score: 1

    I'll just note two points:

    1) Older Apple devices do get abandoned by Apple. My early iPod touch is locked at iOS 3.3 and Apple has made it clear that it will not receive updates.
    2) The exciting "Siri" feature available on the iPhone 4S does not work on earlier phones, even though they do get an iOS 5 update. The official reasoning is that earlier phones are not powerful enough, but this seems to be dubious (even David Pogue, the super Apple fanboy seems to doubt this).

    Bottom line: Apple plays the "obsolete" game pretty well, too.

    On the other side, while Android has had painful fragmentation in the past, Google is claiming, at least, that Android from version 4.0 onwards will be able to run on older devices, though obviously not all features will be supported there. And Google is trying to muscle vendors into a consortium which *requires* them to provide updates for older phones. We'll see how well this happens! And this is all for future phones and Android versions, of course: current "early adopters" of Android will be stuck with the existing mess.

  28. The "lock" is not for security in the first place by Anonymous Coward · · Score: 0

    Really the only "secure lock" part in your mobile phone is the SIM PIN query. The rest is more or less for show.

    The primary function of the lock screen is to prevent accidental keypresses.

    Therefore unlocking it with your face or your coffee mug works just as well, it won't get unlocked by mistake in your pocket or your bag.

    Honestly, does someone think a screen wipe pattern is somehow secure? You can check the greasy fingerprints what the pattern is. Same applies to PIN codes so remember to wipe your phone screen after unlocking the PIN.

  29. Hello? Proof reading? by Anonymous Coward · · Score: 0

    Well they obviously didn't use the new Android 4.0 Spell Checker on their release notes... how many times can you accidentally type continously instead of continuously?

    1. Re:Hello? Proof reading? by Anonymous Coward · · Score: 0

      I make that mistake continously. Erm, continously. I mean, cont... the hell with it. I mean constantly.

  30. Re:It's not always whether the phone can support i by Quila · · Score: 1

    There's no reason a type of device should magically become more relevant than the OS.

  31. Hi, Archos by neminem · · Score: 1

    Are you listening? My Archos 5 is still stuck permanently at 1.6. And now they're working on 4? It's getting a bit depressing.