Slashdot Mirror


CyanogenMod 9 Working On the Nexus S

MrSeb writes with an article in Extreme Tech about progress toward getting an AOSP build working on the Nexus S. From the article: "Over the past week, ROM Manager extraordinaire Koush has been frantically working on making a working build of CyanogenMod 9 (Ice Cream Sandwich) for the Samsung Nexus S. The custom ROM, which is built purely from the Android Open Source Project, has now reached 'alpha 11.' All major features are present and no significant bugs remain. It's too early to say that the build is ready for prime time or mission-critical work — the final release of CM9 is due in the new year — but it's certainly stable enough for daily use. The most significant feature, if you can call it that, is that Koush's build of ICS is really very smooth — it's as nimble as Gingerbread, if not more so. Unlike the previous, non-CM build that was released last week, this alpha build of CM9 has every feature enabled, including Google Wallet, and setting a mobile data limit. As usual, the custom ROM is pre-rooted, has ROM Manager installed, and absolutely no bloatware. "

218 comments

  1. Yay by masternerdguy · · Score: 4, Funny

    I want a real linux distro, not google's vision of how linux should be. Let me know when I can load Debian, SuSe, Fedora, etc, on my phone and then we'll talk.

    --
    To offset political mods, replace Flamebait with Insightful.
    1. Re:Yay by Anonymous Coward · · Score: 2, Funny

      Come on now, follow the rules and post that stuff in the apple section.

      Think of the children.

    2. Re:Yay by Kenja · · Score: 4, Insightful

      Done. http://www.youtube.com/watch?v=xN4c61ETCWg Totally useless of course, but knock yourself out. Just hope you dont need to make calls on your "phone".

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    3. Re:Yay by Cyberax · · Score: 1

      Easy.

      http://www.youtube.com/watch?v=cWLOqVdtbkw - Ubuntu on Galaxy S.

    4. Re:Yay by Anonymous Coward · · Score: 0

      I want a real linux distro, not google's vision of how linux should be. Let me know when I can load Debian, SuSe, Fedora, etc, on my phone and then we'll talk.

      You actually can get Linux running on an android phone. You have to side-load it and can't boot directly into it but i can and has been done. Search XDA.

    5. Re:Yay by masternerdguy · · Score: 0, Flamebait

      I don't want to sideload it, I want it running as the host OS and able to make phone calls. Is this hard to understand?

      --
      To offset political mods, replace Flamebait with Insightful.
    6. Re:Yay by Kenja · · Score: 4, Insightful

      So you want a Nokia N900. Not too many people did, which is why it was dropped.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    7. Re:Yay by PitaBred · · Score: 4, Informative

      You sure are demanding and lazy, aren't you?

    8. Re:Yay by TheReaperD · · Score: 2

      Then why don't you program it? It's not something that I want so I have no plans of doing it for you.

      --
      "Be particularly skeptical when presented with evidence confirming what you already believe." -
    9. Re:Yay by exomondo · · Score: 1

      I want a real linux distro, not google's vision of how linux should be. Let me know when I can load Debian, SuSe, Fedora, etc, on my phone and then we'll talk.

      Do any of those have phone support? If not then I can't see why you would want them since loading them on to your phone seems pretty pointless...unless of course you don't actually want to use it as a phone.

    10. Re:Yay by masternerdguy · · Score: 2

      The android manufacturers should provide an open source kit for getting any linux distro to act as a phone. It's their hardware.

      --
      To offset political mods, replace Flamebait with Insightful.
    11. Re:Yay by mjwx · · Score: 5, Insightful

      Then it hasn't met my standards, because it's no longer a phone. I want an open source program I can compile and install on my distro of choice that lets me use it as a phone.

      Well, get coding. It's open source after all

      Otherwise all this sounds like is Varuka Saltz stamping her feet and shouting "Daddy, I want it NAOOOOOOOOOOO".

      As for me, I'm grateful to Cyanogen, Koush and the rest of the rather lengthy CM team for their hard work (yes I donate too). Most of us have to work with what we've got, thanks to Google we've got a great platform to work with (anyone complaining about Android never used WinMo) and thanks to people like Cyanogen, we've got an even better phone OS that is free and open.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    12. Re:Yay by Anonymous Coward · · Score: 0

      You are free to BUILD YOUR OWN phone.

    13. Re:Yay by monkeyhybrid · · Score: 1

      To be fair to Google, I don't think Android is their vision of what Linux should be but rather it's their vision of what a consumer phone OS should be (and just happens to be based on the Linux kernel).

    14. Re:Yay by Microlith · · Score: 5, Informative

      No, it was "dropped" because Nokia's internal politics damaged the company enough that they stuck an ex-Microsoft executive in the CEO slot who promptly killed off the winner they managed to create in the N9 and forced Nokia on to WP7.

      But please, blame the core OS for political and managerial failures.

    15. Re:Yay by Anonymous Coward · · Score: 0

      You don't have very many friends, do you?

    16. Re:Yay by Microlith · · Score: 2

      Should, but they won't. Mostly because at least in the US they're subservient to the carriers who don't want you to do as you wish, but rather want you to do as they wish and use your device as little as possible, pay as much as possible, and throw it away in favor of a new device and a new contract after 2 years are up.

      Until then, pick a handset and go look at http://wiki.merproject.org/wiki/Nemo">Nemo, maybe grab an N900.

    17. Re:Yay by Anonymous Coward · · Score: 3, Funny

      I want a pink unicorn. And it has to be able to speak English. And shit rainbows. I want it now.

    18. Re:Yay by Anonymous Coward · · Score: 0

      Why?

    19. Re:Yay by Anonymous Coward · · Score: 0

      "I want an open source program I can compile and install on my distro of choice that lets me use it as a phone."

      Excellent! Let us know when you have something up and running.

      Or is it that you are just entitled and are expecting other people to do it for you?

    20. Re:Yay by AgNO3 · · Score: 1

      Then Again. Get busy and code it and stop being an open source leach.

      --
      OMG Ponies!!! with Glitter!!!! I miss Pink :-(
    21. Re:Yay by Anonymous Coward · · Score: 0

      "I don't want to sideload it, I want it running as the host OS and able to make phone calls. Is this hard to understand?"

      [waaaaaah] I want it NOOOOWWWW!!!!! [/waaaaaah]

    22. Re:Yay by exomondo · · Score: 1

      The android manufacturers should provide an open source kit for getting any linux distro to act as a phone. It's their hardware.

      You mean the handset manufacturers? Why would they do that?

    23. Re:Yay by dave420 · · Score: 2

      Because that's what he wants, and that's all that matters.

    24. Re:Yay by MobileTatsu-NJG · · Score: 5, Funny

      No, it was "dropped" because Nokia's internal politics damaged the company enough that they stuck an ex-Microsoft executive in the CEO slot who promptly killed off the winner they managed to create in the N9 and forced Nokia on to WP7.

      Uh, no. It was dropped because their marketing strategy of having three guys chime in on every Slashdot smartphone thread about how great the N900 is was insufficient to gain any traction in the US.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    25. Re:Yay by Anonymous Coward · · Score: 0

      You must have a lot of free time on your hands.

    26. Re:Yay by Anonymous Coward · · Score: 0

      I don't want to sideload it, I want it running as the host OS and able to make phone calls. Is this hard to understand?

      Quite the rabble rouser, aren't we?

    27. Re:Yay by Anonymous Coward · · Score: 0

      And its the phone providers' networks, I'm pretty sure they aren't going to sign off on something like that.

    28. Re:Yay by Anonymous Coward · · Score: 0, Informative

      Just another reason to never be involved with open source. Sure, there are tons who say they'll donate but I'm sure most never do and if you don't appease your audience with the answer to every want and need you'll get a storm of excuses like "I was going to donate until I found out that your software doesn't wipe my ass." Not unlike the "I'd buy music if it only cost 99cents a song, uh... wait, make that 49 cents... uh... hold on, I meant a nickle a song".
       
      It's a losing battle unless you're building a tool for your own use and decide to open it up to others just for the fuck of it all.

    29. Re:Yay by Anonymous Coward · · Score: 0

      mod parent troll

    30. Re:Yay by im_thatoneguy · · Score: 1

      Well, get coding. It's open source after all

      Otherwise all this sounds like is Varuka Saltz stamping her feet and shouting "Daddy, I want it NAOOOOOOOOOOO".

      Maybe he would be willing to pay for it.

      I'm exactly like Varuka stamping her feet. And after parting with my cash I have an expectation that my slice of the development costs is reflected in feature development.

    31. Re:Yay by tepples · · Score: 1

      Yeah, Nokia messed up one key thing that should be part of any mobile device's marketing plan: having it available for people to touch in stores across the expected market.

    32. Re:Yay by Belial6 · · Score: 2

      Different people have different price points. I always said that I would buy my PC games if they were priced reasonably, and didn't have DRM. In the last year I have bought 140 PC games from GoG. That is at least 10 times the number of games that I had purchased over the last 10 years.

      If I could buy PS1 games in a paper sleeve at the checkout of the drugstore for $1 a pop, I would buy just about anything I could get my hands on. I would pay 2 to 3 times that for PS2/XBox games.

      99 cents per song is a ridiculously high cost for music. The cost of producing music has dropped dramatically in the last 2 decades, and 99 cents per song is what it used to cost for a physical disk. It is actually surprising how many people have bought into having the price RAISED for the privilege of not having a physical disk.

    33. Re:Yay by cheater512 · · Score: 1

      N900 fits your bill.

      Runs Android too if you feel in the mood. :)

    34. Re:Yay by chrb · · Score: 5, Interesting

      Not done. That is Ubuntu running in a chroot environment. And it makes phone calls fine, because Android is still present. Personally, I would love to see a real Linux distribution running on an Android device. Android has so many limitations: the bionic C library, Dalvik apps only (yeah, I know about NDK, but "real Linux" has Python, Perl, C++, OpenJDK Java etc.)

      The limitations of Android stem from being targetted at 2005 phone hardware, so they created a cut-down Linux. With 2012 tablets, dual-core 1.2GHz+ CPU and 1GB+ memory, there is absolutely no reason for these artificial software limitations. I want to see Gnome on a tablet. And KDE. And other GUI environments. And I want Android to be relegated to an app-compatibility environment in the same way that Java and Mono exist today - not because that's a bad thing, but because Android is just one application environment of the many that exist on Linux. Why shouldn't tablet programmers use Python+PyQT to build their apps, deployed on Debian-style apt-get repositories? Why shouldn't we have Ubuntu for Tablets? The hardware is powerful enough now, and it is only going to get more powerful, we don't need to be hobbled by the design choices of what was (8 years ago) a small startup in California.

    35. Re:Yay by fliptout · · Score: 1

      You, sir, are a legend.

      --
      A witty saying proves you are wittier than the next guy.
    36. Re:Yay by MrEricSir · · Score: 1

      Holy shit, you're right. You know what, fuck it, I'm going to go back to using a slide rule.

      --
      There's no -1 for "I don't get it."
    37. Re:Yay by CaptainLard · · Score: 1

      I bet a tablet running Ubuntu will be released as soon as you can find 1,000,000+ people to pre-order one for $500. No personal checks please.

    38. Re:Yay by Anonymous Coward · · Score: 1


      mod parent troll

    39. Re:Yay by Microlith · · Score: 1

      Fight it all you want, but mark my words.

      Sure, but that point is not the same for everyone. Just because you or someone else has decided that they don't want to mess around with mobile technology, doesn't mean that it should be a path denied to everyone. Nor should it be actively inhibited and fought against by companies selling high dollar devices.

      An entire new space is opening up and the desire to be able to hack in it and do things that aren't totally corporate-controlled is strangely meeting resistance from some odd dimension of the Slashdot readership, declaring it to be the realm of "consumer appliances," thus rationalizing the deriding of those who show interest. It's quite sad, really.

    40. Re:Yay by nemasu · · Score: 1

      Done! I got Gentoo, emerge and everything, working fantastically. And it was super easy. http://www.hubholic.com/content/60/getting-gentoo-on-my-galaxy-s-2

      --
      I made an app! Shoutium
    41. Re:Yay by Hal_Porter · · Score: 2

      Varuka Saltz

      It's Veruca Salt. Verruca are plantar walts.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    42. Re:Yay by Hal_Porter · · Score: 1

      I think Google looked at the vast Linux ecosystem and GPL community and decided very wisely they'd keep the kernel but write their own non GPL userland.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    43. Re:Yay by Anonymous Coward · · Score: 0

      How touch friendly are Gnome and KDE--and their applications? Or were you proposing tacking a keyboard and mouse onto every one of these devices?

    44. Re:Yay by Anonymous Coward · · Score: 0

      Because 'music" and "songs" are just like toilet paper, it should be less than a cent. Anyone can make music now, you just push some buttons and crap something out, and there's music. Fuck you, Yo-yo Ma, hit the bricks. I'm not giving you a dollar for your "song". Fucking musicians. I'd pay a guy $40 to do my yard, but a dollar to hear something? I can hear stuff for free. Next thing you know, game programmers are gonna want to get paid too.

    45. Re:Yay by LurkerXXX · · Score: 1

      Two years ago he would have wanted an N900. Now he'd want a N9.

    46. Re:Yay by Anonymous Coward · · Score: 0

      I think by real Linux he meant something along the lines of MeeGo.

    47. Re:Yay by CalcProgrammer1 · · Score: 2

      It is definitely possible and work is being done. The issue is that many devices have a restrictive bootloader and pre-determined partition setup that prevents the creation of additional Linux partitions and installing extra boot options. Some devices do have "developer" boot loaders (such as Archos' SDE) or modded in custom boot loaders (such as moboot on HP Touchpad) that allow you to boot whatever you want. Beyond that, getting a proper "real Linux" environment requires Xorg drivers for the video devices and many mobile systems do not have such drivers. Even when they do, those drivers are often merely framebuffer implementations which allow GUI functionality but with zero hardware acceleration. The GPU's on mobile devices are pretty much exclusively proprietary and require binary firmware blobs that may or may not be compatible with non-Android (or other OS) environments. Finally, devices found in many mobile devices are nonstandard and are not present in the main line Linux kernel source, so a one-size-fits-all kernel package such as is typical on PC setups will not work for mobile. Instead, each device must have its own custom maintained kernel that keeps all the device-specific hardware patches up to date. Some devices (such as the Archos tablets) require you to flash the kernel and initramfs into a special boot area, meaning that typical kernel upgrades through package managers will not work. Finally, even if you do get GPU acceleration to work, mobile GPU's only support the limited OpenGL ES architecture. Almost all of the desktop window managers that support acceleration do so through traditional OpenGL interfaces, meaning that these window managers must be rewritten to support OpenGL ES instead. The same applies to video acceleration in media players, and the DSP and GPU systems are much more varied in mobile devices. These are just some of the restrictions that prevent true Linux installations on mobile devices. I actually did get Debian running decently on my Archos 43 tablet but only after finding a modified 2.6.37+ kernel that did not have all the necessary drivers installed. The core functionality worked despite having to write some boot scripts to initialize the WiFi, Bluetooth, and power management systems. Even then the Bluetooth was spotty at best, often dropping connections and refusing to pair (despite working perfectly in Android with the same devices). To all mobile hardware developers: Please, if you really want consumers to get the most out of your hardware, make sure your drivers are compatible with standard Linux system utilities in addition to those found in Android and other mobile OS'es. This will help out such porting efforts and give your device a wide variety of OS choices. Also, please consider open-sourcing more drivers, especially video drivers. If not open-sourcing them, at least make Xorg compatible drivers with OpenGL ES acceleration so we can actually use the full potential of the hardware.

    48. Re:Yay by Anonymous Coward · · Score: 0

      I want a real linux distro, not google's vision of how linux should be. Let me know when I can load Debian, SuSe, Fedora, etc, on my phone and then we'll talk.

      So do I. That's why I'm buying a Nokia N9. I own a Nokia N810 (not a phone, just a small tablet); it runs a Debian-based distro (so you can install any Debian package) and you can install vanilla Debian if you really want to. I don't know how the N9's version of the OS compares, but it should be similar.

    49. Re:Yay by Anonymous Coward · · Score: 1

      mod parent troll - no mod back.

    50. Re:Yay by bemymonkey · · Score: 1

      How the hell is that supposed to work without a "Phone distro" to start with?

      Ubuntu runs on many Android devices just fine... you just need to write the phone stack and front-end yourself - nobody's stopping you.

      In other words: You CAN put pretty much anything you want on there... there just isn't anything usable *to* put on a phone yet. How is that Android's/Google's fault?

    51. Re:Yay by bemymonkey · · Score: 1

      Get a sense of humor.

    52. Re:Yay by thsths · · Score: 1

      > How touch friendly are Gnome and KDE--and their applications?

      Not at all. I was running an Ubuntu chroot under WebOS to get at least some apps. And usability is absolutely terrible.

    53. Re:Yay by dell623 · · Score: 1

      The post is actually a great example of why we should be able to mod posts both funny and insightful.

    54. Re:Yay by rtfa-troll · · Score: 1

      Man; I have just subscribed to your newsletter. As a person who has fought to get MacOS / OS X to "just work" (don't get me wrong; the others are worse) I know your pain.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    55. Re:Yay by impaledsunset · · Score: 3, Informative

      Debian runs on the Neo Freerunner, and there's software for the phone functionality. You can make calls, receive and send SMS, connect over GPRS and read your email, browse, use the GPS. It's usable, although running desktop apps on a phone can be frustrating sometimes. And it's slow.
      There's a project to run Debian on Nokia N900, however it's incomplete and because of a few proprietary components you can't "compile and install" something to make the phone work. The community is working on replacing those.

      The original OS on the phone is Maemo, which is essentially Debian-based, X-based, and you can compile and run it except for those few components. You can also run full Debian in a chroot. You can also port the apps missing in Debian from there any time you wish. It's non-trivial perhaps.

      You can run Kubuntu on N900. The phone functionality in Debian and Kubuntu is being worked on.

    56. Re:Yay by gutnor · · Score: 2

      Mostly because at least in the US they're subservient to the carriers who don't want you to do as you wish, but rather want you to do as they wish and use your device as little as possible, pay as much as possible, and throw it away in favor of a new device and a new contract after 2 years are up.

      No they won't because they want to sell a shitload of handsets and that means that they focus their effort on the most juicy target. Advanced support for geek has an extremely limited return on investment.

    57. Re:Yay by AmiMoJo · · Score: 1

      I think you missed the point of tablets. They are not general purpose computers, they are about displaying information. You wouldn't want to do too much serious work on one because the form factor is not suited to that, e.g. the on-screen keyboard can't be typed on nearly as easily as a hardware keyboard, and touch is no where near as accurate as a mouse.

      For light gaming and web browsing they are ideal, and Android is ideally suited to that.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    58. Re:Yay by Anonymous Coward · · Score: 0

      I did want one. however, the resistive touch, smaller screen and unavailability prevented me. I found exactly one store which had one on demo, but is they broke it within 2 weeks.

      Afterall I bought an HTC desire. absolutely love it. however i miss the physical keyboard.

    59. Re:Yay by vadim_t · · Score: 1

      Bah, what a boring world view.

      I'm in the process of disassembling my espresso machine and sticking an Arduino into it. The Apple-like interface doesn't appeal to me at all. It will be done when keeps temperature properly, has a status display, and is accessible by wifi.

      I have tried some Apple stuff. Yeah, it's sorta pretty for a while, but at least for me it gets outright maddening the moment I bump into one of the annoying limitations, and there's a lot of those.

    60. Re:Yay by gl4ss · · Score: 1

      well, if you'd hack android to run in ubuntu for n900, it would fit the bill.

      but then he would say that ubuntu isn't his distro of choice.

      --
      world was created 5 seconds before this post as it is.
    61. Re:Yay by MobileTatsu-NJG · · Score: 1

      The N900 was unsuccessful before Nokia was flirting with Windows.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    62. Re:Yay by Miamicanes · · Score: 4, Informative

      Well... there's a little more to it than that. A "phone" environment is fundamentally different in the sense that an incoming phone call usually will (and should) stop whatever else you're doing dead in its tracks until the call is dealt with. A scheduling and notification strategy optimized for realtime multiplayer games is going to be completely dysfunctional when your real-world use case involves being able to freeze the action mid-shot and take an incoming phone call, then gracefully ease back into the action when it's finished. That's why Android makes such a big deal about differentiating between "service" and "activity" -- a service can keep running when another activity has the activity focus.

      If Android apps weren't forced to divide up the workflow and separate out the parts into "things that can (and should) run in the background without a user interface", and "things that only make sense when the application has focus and the user's exclusive attention", we'd have the same problems that IOS does. Where things in Android's world become confusing is the ambiguity at the "service" end, between "things that happen occasionally on a schedule" (like polling a server), "things that happen in response to something else" (incoming communication, arrival at location, change of sensor state, etc), and "things that should happen, and keep happening, until something else gives them a reason to stop" (like music playback). Complicating things more is the fact that you can sort of *get away* with doing things in background services using threads and traditional Java sleep/wait strategies, but Android will break things that insist on doing things that way in increasingly aggressive ways (particularly Gingerbread and beyond), even when they do it in ways that are considered to be perfectly legitimate and polite in mainstream Java.

      Starting with Gingerbread, Android has started becoming downright mean & aggressive towards apps that use TimerTask to schedule periodic tasks in background services instead of using alarms & intents... not quite breaking apps outright, but getting VERY aggressive about killing background services that use TimerTask with partial wakelocks in ways that even a year ago would have been considered mainstream and exceptionally well-behaved (like grabbing a partial wakelock ONLY during actual network activity, to at least ensure that the phone didn't get put to sleep halfway through a http request, even if the service itself ended up suspended until the phone was awakened by something). Now, Android will kill background services after about an hour simply because it decides they've been running for "too long", even if they've been asleep in a TimerTask for most of it. I never even noticed this until I got my Photon last month, because my previous phone (Samsung Galaxy S/Epic 4G) was stuck in Froyo-land, and my app worked flawlessly on it. I knew it didn't reliably poll when the phone was asleep, but it still managed to make it work often enough to not be a big deal. Once I got the Photon, I noticed that it was just silently dying outright after about an hour, and not coming back to life after the phone was awakened.

      I can see Google's logic, but I don't think they've done a particularly good job of reaching out to developers (many of whom are still stuck in Froyo-land, if only because American carriers suck & most users are still stuck with it, often including the developers themselves). Yes, the emulator exists for newer versions, but frankly, it's so slow, even on a fast quadcore PC, I'd rather tear off my fingernails one by one than suffer its slowness (and the fact that it seems to either die, or spontaneously lose contact with Eclipse, once or twice per hour, necessitating even more delay and interruption). After I bought my new Photon, my old Epic turned into my "permanently tethered to the computer development phone".

    63. Re:Yay by tlhIngan · · Score: 2

      I think Google looked at the vast Linux ecosystem and GPL community and decided very wisely they'd keep the kernel but write their own non GPL userland.

      Exactly. Same reason why Apple chopped down OS X to make iOS for the iPhone and iPad.

      Usability of desktop OSes on handheld and tablet devices is awful, even though compatibility is great. You can buy phones running Windows XP and Windows 7 (they're on the market), but we're talking about Windows UI on a 4" screen. And we know how Microsoft did with nearly two decades of trying to sell tablet-ized Windows (Pen Windows, XP tablet, Origami (XP), now Windows 7).

      Right-click is hard enough on a touchscreen already - I can't imagine trying to simulate a middle click And then there's the typing.

      It's why there are QT environments for pocket devices, as well as Maemo/MeeGo and other UIs around - what works on the desktop does not work on a touch-enabled tablet nor phone necessarily.

    64. Re:Yay by HiThere · · Score: 1

      Wisely from their point of view isn't necessarily wisely from mine. So far I haven't bothered to get a smart phone, and have seen no real reason to want to.

      OTOH, I've nothing really against Dalvik, but I wouldn't want to comit to it until after Google wins the suit that Oracle has pressed against it. Even then Java's really *not* my favorite language. I prefer Python or D.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    65. Re:Yay by Anonymous Coward · · Score: 0

      Android doesn't kill things just because they've been running "too long". If your app is declared as idle (no foreground Activities, no running services) it has *always* been considered acceptable to be killed whenever the RAM is needed for anything else, or just because it feels like it.

      If you run in the background and want any semblance of reliability, you *must* use a Service. Period. The documentation is quite clear on that. Likewise, if you want to actually wake up you *must* use an Alarm. Again, the documentation is quite clear on that. If it works on Froyo it means your app is getting lucky and the timer is firing when something else has the phone awake - your app is still broken, it just works because something ELSE on the phone is ALSO broken.

      TimerTask has never been "supported"

    66. Re:Yay by Miamicanes · · Score: 2

      TimerTask might never have been officially "supported", but the practice of using it was widespread to the point of making it into at least one major book on Android programming as an example.

      Yes, Android has always been entitled to kill background services when RAM is needed, and has reserved the right to do it for any reason, or no particular reason at all. The unhappy surprise was Gingerbread's aggressive enthusiasm for killing background services for reasons seemingly closer to "just because it feels like it".

      In Froyo, it was reasonable to assume that Android wouldn't kill off a background service unless there was a bona-fide need to free up resources, or the service appeared to be leaking resources or spinning its wheels doing busy-waits and keeping the phone awake for extended periods of time. As of Gingerbread, it literally DOES appear to kill off long-lived, but otherwise tame and sleepy, background processes just because it thinks they've been running for "too long".

      There's a bigger problem -- to this day, there's no easy way using the bare API to say, "at XXX, wake up the phone, attempt to connect to a network, make this complete http request, and keep the phone awake until its response has been received, digested, and handled. Then go back to sleep if you feel like it." You can't directly pass a PartialWakeLock acquired by an Alarm's BroadcastReceiver to the service, but if you merely try to start the service so it can acquire its own partial wake lock, there's no guarantee the phone will remain awake long enough for the service to finish initializing. There are various ways to kludge around it using static objects, but Android's own development team has admitted that they're ugly hacks. That's why so many people used long-lived services with TimerTasks -- they worked. Not 100%, but if you could live with the service running only while the phone was awake, and you did your part to have well-behaved and polite Threads, they worked pretty well (and definitely worked better than most guerrilla attempts to make Alarm-triggered network activity work properly).

      What Android's API *really* needs badly is something like PendingHttpRequest, where you could set up a HTTP(S) GET/POST, specify the args, define intents to fire when it succeeds or fails, and throw it into a metaphorical pile for Android to execute as a bach along with PendingHttpRequests from other apps/services within 1, 5, 10, 15, 20, 30, 60, 90, 120, 180, 240, 360, 480, 720, 1080, or 1440 minutes. THEN, let ANDROID deal with bringing up the network, firing them off, retrying if appropriate, and shutting everything down when it's through. Kind of like the general idea behind SetInexactRepeat, but incorporating wakelocks and network-connectivity management into the equation as well. The problem we have now is that everyone is forced to reinvent the wheel, and just about everyone does it badly.

      Network connectivity in a narcoleptic Android device is a really hard problem for individual developers to solve. Wakelocks are a dance through a minefield. The need to make a single successful http request at some not-particularly-critical point in the future when the phone has reliable network connectivity is a common use case, and we'd all be better off if there were a nice, clean, easy way to just throw the URL, args, and handler intent at Android and say, "here's the request. Make it properly, and let me know when it's done."

    67. Re:Yay by Anonymous Coward · · Score: 0

      It's why there are QT environments for pocket devices, as well as Maemo/MeeGo and other UIs around - what works on the desktop does not work on a touch-enabled tablet nor phone necessarily.

      Why are we constantly told that the inverse is true? That the PC is dead. That all anyone really wants is a desktop or laptop running android or iOS?

  2. Re:Lies by TheReaperD · · Score: 4, Informative

    Although Android is not a true open source project, they normally release the source code with one major exception. A lot of the argument about that was because Google refused to release the 3.x Honeycomb source code. Google themselves said that the reason they never released it was that it was a 'hack' to get Android on tablets and was not up to their quality standards and they didn't want it spread any further than necessary. They promised that they would release 4.0, dubbed Ice Cream Sandwich, which would meld the phone and tablet code and they have done so, leading to the CyanogenMod 9 release.

    --
    "Be particularly skeptical when presented with evidence confirming what you already believe." -
  3. Open source vs. community development by DragonWriter · · Score: 5, Informative

    Although Android is not a true open source project, they normally release the source code

    A project that releases source code under an open source license is an open source project.

    Android, unlike many open source projects, isn't an open community development project, but while those two things often go together, they have no necessary relationship.

    1. Re:Open source vs. community development by Kjella · · Score: 1, Informative

      A project that releases source code under an open source license is an open source project.

      And any open source project that releases major new versions without source is called a "bait and switch" project. Some of the code some of the time has never been an accepted standard, even if it's Google doing it and they allegedly had good reasons for it. The standard for an open source project is if it's good enough to ship binaries, it's good enough to ship code. If say Oracle released MySQL6 and said "Hey, we're still cleaning up the code but it'll be released for MySQL7 mmmkay?" would you call that open source? No. I don't see why Google should get a free pass at something you'd never accept from another open source project.

      --
      Live today, because you never know what tomorrow brings
    2. Re:Open source vs. community development by Namarrgon · · Score: 4, Insightful

      Here's a big difference: Android is pretty much entirely funded and developed by Google. It's not a community project.

      Their project, their copyright, their licence, their rules. Demanding that they give you the source to everything they develop is simply childish. Be grateful for the source you get, since it cost the wider community nothing, not even time.

      --
      Why would anyone engrave "Elbereth"?
    3. Re:Open source vs. community development by hairyfeet · · Score: 1, Troll

      Uhhh...you DO realize that everything you said ALSO applied to Oracle, yes? Did the community just go "Okay Larry, whatever you say!"? Nope they forked it.

      Either the rules are the same for everyone or they are aren't really rules are they? It always amazes me how those that are fanboys of one company or another can come up with logic hoops to explain away the exact same shit they had a fit about from another company. Not saying you are or aren't a fanboy, but the logic in that statement as a refute to his comment about Oracle just doesn't hold water.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    4. Re:Open source vs. community development by thsths · · Score: 1

      > And any open source project that releases major new versions without source is called a "bait and switch" project.

      Well, yes - Google is in it for the money, not for the community. Many companies operate on the same principle: you can get the source under an open source license, but you can get it sooner if you pay.

      I was a bit miffed about Gingerbread, but now that Google has released the source code for ICS in a very timely manner, all is well again for the open source community. Now if only they could keep a decent log of security issues... of course the community could step up to the plate and do it based on the source, but without the original report that can never be quite as comprehensive.

    5. Re:Open source vs. community development by dell623 · · Score: 1, Flamebait

      Are you kidding me? Open source zealots like you give open source a bad name and by your philosophy the mobile device space would be a mirror of the desktop space where only people interested in self flagellation run Linux as their sole desktop OS due to the endless limitations and issues you have to deal with gaining nothing in return.

      It is incredible that Google are willing to give away the source code for free, and it may actually kill Android in the tablet arena if Amazon's devices gain ground. The Kindle Fire is going to get a lot better and Amazon are releasing bigger Kindle tablets next year. Look at the original e-ink Kindle to see how Amazon work, it was an awful and ugly device, compare that to the Kindle Touch.

      In which dream world do you live if you think Microsoft or Apple or HP or any other major IT company in the world would give away not just their operating system, but the source code as well? And Google get criticized for that??

      Do you for one moment stop and think how wonderful it is that the most popular operating system in smartphones is open source, and you can endlessly modify it or use innumerable open source ROMs and software, while still retaining compatibility with a vast library of applications.

      Without Google the smartphone OS space would be dominated by Microsoft and Apple with some token miniscule market share to n900 like devices for people like you.

      Why are Google the only company that are always criticized from a utopian perspective?

    6. Re:Open source vs. community development by Namarrgon · · Score: 2

      Well, unlike Android, MySQL is under a GPL licence, requiring them to open the source to released binaries in a timely fashion, is it not? So Oracle couldn't legally withhold source at all, unless they changed the licence somehow.

      I was under the impression that MySQL is (or perhaps was, until a couple years ago) a much more community-driven project, with many contributors who would be livid to see their work bought & derailed, but perhaps I'm wrong there. If it really was developed solely by MySQL AB (and then Sun, then Oracle), with little to no direct community input, then yes, I would think Oracle would be well within their moral rights to turn it into a restaurant ordering system, if they felt like it. The community can go play with the MariaDB fork instead, and should be happy that they were given a free DB as good as it is.

      --
      Why would anyone engrave "Elbereth"?
    7. Re:Open source vs. community development by rtfa-troll · · Score: 2

      This is a simple matter of competence and trust. When Google says "we will release the source later" even those of us who are a bit outraged* mostly trust them. When Oracle says little and occasionally mutters "we are working on the community" we immediately see a bunch of executioners coming out and start to panic. I know that I immediately switched to Jenkins / Libre Office the minute I heard that there was a fork away from Oracle. I still haven't got it together to get Cyanogenomod even though it's probably more beneficial for me. I have stopped basing anything on MySQL that I can avoid for a while.

      This is actually correct. Oracle's behavior is generally outrageous and should not be rewarded. It's completely reasonable to take almost anything Red Hat says on trust whilst I wouldn't accept a contract from Microsoft without Billions in cash, a series of senior management hostages, ownership of 90% of the voting shares, a safe room, free use of the US army for my own defence and a personal promise from a known trustworthy dominant alien intelligence to intervene on my behalf. Let's just say I'm not expecting things to work out well for Nokia.

      * A "bit outraged" is difficult to explain. It doesn't worry me most of the time because I have come to believe that Google does what they say, but when I think about it too much I get very annoyed. I guess I don't want to trust Google, but feel forced to do so by other people who are more evil than they are.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    8. Re:Open source vs. community development by Anonymous Coward · · Score: 0

      And people could, and did, fork Android 2.3. This is not hard to grasp:
      Android is Apache licensed, they don't have to release anything.
      Android up to 2.3 was open-source, Android 3.0 was not, had that continued then Android (the project) would have become closed-source. But it didn't, Android 4.0 (and 3.0) are now available so it is open-source. no ifs-or-buts
      The source is open.

    9. Re:Open source vs. community development by petermgreen · · Score: 1

      The source is open.

      More specifically the source to most versions of the stock version of the core of andriod is open. The remaining versions is probably burried in the VCS history somewhere but afaict you are on your own as regards finding them since they aren't tagged. Apps that form a key part of the user experiance are not open and neither are any customisations made for individual phones (other than bits that the GPL forces them to release).

      It's certainly better than no source at all but I wouldn't describe it as an "open source project".

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    10. Re:Open source vs. community development by jc79 · · Score: 1

      It is incredible that Google are willing to give away the source code for free, and it may actually kill Android in the tablet arena if Amazon's devices gain ground. The Kindle Fire is going to get a lot better and Amazon are releasing bigger Kindle tablets next year.

      I agree with most of what you said, but this bit baffles me. How does Amazon releasing an Android tablet (the Kindle Fire) kill Android in the tablet arena? I expect all the forthcoming Kindle tablets will run Android as well. Seems like a good way to get Android using devices into lots of people's hands, meaning the market for Android apps that work well on tablets is bigger (even if the stock Kindle Fire is tied to Amazon's app store, nothing stopping devs releasing on there as well as Google Android Market.)

    11. Re:Open source vs. community development by impaledsunset · · Score: 1

      As long as they own the copyright, yes, they can.

    12. Re:Open source vs. community development by dell623 · · Score: 1

      Sorry, I wasn't clear, I meant it might kill Google Android on tablets. Amazon forked Android a while ago, at 2.2 or 2.3 I don't remember which. I think will only run Android 2.x apps, not Honeycomb or ICS specific apps. I don't know whether Amazon will choose it incorporate the ICS source code or continue improving their forked code. The Fire is already selling like no android tablet ever has. There are still very few tablet specific apps for Android, and future developers may have to choose whether to develop for ICS or Kindle. And Kindle owners will be more likely to pay for their apps whereas Android tablet owners will pirate them, as so many people already do for Android mobile apps.

      For people who want to do more and pay more for their tablets, the iPad is still more attractive. And Windows 8 will come with a huge advantage called Windows. People considering the tablet for doing stuff they used to do on a windows computer will automatically be drawn to it, despite the fact that ARM Windows 8 tablets won't run x86/x64 windows applications. Microsoft don't have to make the best tablet OS to be successful, just something decent. Show people a functional version of Microsoft Office, and familiar stuff like Paint and they will think it's awesome, even if there are better office and drawing apps available on Android.

    13. Re:Open source vs. community development by Anonymous Coward · · Score: 0

      You're an idiot.

      Why oh why are you still complaining about the Honeycomb source code when it's been entirely surpassed and superceded by ICS?

      Google withheld the HoneyComb (Android 3.0) source for a good reason - it was a rushed botch job. They didn't really want people developing on top of that platform for good reason and wanted everyone to wait for ICS which allowed them the opportunity to clean up the code and implement more and newer features in the ICS (Android 4.0) release. The source code for which they have made freely available, and quite quickly too.

      It's Google's code, so they're allowed to do all that. You're whining on and on as if they've completely changed their minds and decided to never release any more Android code ever.

      Quit whining like a spoilt child and be thankful for the superlative ICS release. If enough idiots like you keep bitching about good gestures from Google like this, maybe they will "take their ball and go home" in the future leaving you with nothing!

    14. Re:Open source vs. community development by hairyfeet · · Score: 1

      While this is a well thought out post, you are missing the point, although I do think its funny I got a "+1 Troll" as that is a new one for me.

      The point was the way the community acts with regards to certain companies that they have already decided are "good" or "evil". If Google was to print Android manuals with the blood of dead kittens and send the community a Goatse Xmas card they would be tripping over themselves to explain away their "quirky sense of humor" whereas if one of the "evil" companies were to bump them in the street they'd be screaming "ZOFG get the pitchforks!"

      Your UID is low enough you've had to have been here for awhile RTFA, you can't tell me you haven't noticed this. When Google said they weren't gonna release the source for 3 the apologists practically RAN to their keyboards to write these huge apology posts, whereas oracle buys a GPLed program, just like what Google did when they hired developers to turn the Linux kernel into Android, and the screams of theft rang high into the night!

      I'd say a good reason to avoid GPL and why companies treat GPL is an "infection" is because trying to predict which side of the good/evil coin is gonna land is frankly impossible. I mean who would have thought a company could cook up a slogan like "do no evil" and have the community practically singing its praises when it has about as much meaning in the actual world as "think different"?

      --
      ACs don't waste your time replying, your posts are never seen by me.
    15. Re:Open source vs. community development by Anonymous Coward · · Score: 0

      Mod parent down. I love whitey.

    16. Re:Open source vs. community development by rtfa-troll · · Score: 1

      You have a definite point here; may I recommend a book "the Corporation" by Joel Backan, which will give you lots of material to support your case. In this case I don't thing you are picking the right target in at least two senses. Firstly, this is a case where those people who wrote apologies turn out, at least in their own terms, to have been right. Google did give out the code in the end. In the case of Google, a much more productive example would be the way that the whole of Google has been designed as an end run around the GPL. The example to warn about would be their lack of clear promises to offer free licenses to FOSS projects for all their patents. If the example you had brought up had been Apple then you would find plenty of posters who were supporting them for ages (and even now) as a driver of innovation even when it was obvious that their lawyer friendly side was coming out.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  4. SGS4G support Please! by modmans2ndcoming · · Score: 1

    I have had to use ICBINB builds of Gingerbread for my Samsung Galaxy S 4G because CM7 was not available for that phone.... please please please support it for CM9!

    1. Re:SGS4G support Please! by Anonymous Coward · · Score: 0

      Hear, hear!

    2. Re:SGS4G support Please! by mjwx · · Score: 4, Informative

      I have had to use ICBINB builds of Gingerbread for my Samsung Galaxy S 4G because CM7 was not available for that phone.... please please please support it for CM9!

      If you're into hacking, the difference between the SGS 4G and the SGS is the radio (IIRC), so you'll need to replace the radio drivers with ones that work (I.E. one's you've backed up from the device). I had to do this on a Motorola Milestone (and the locked bootloader didn't help).

      This is a "Do at your own risk" thing, if someone more knowledgeable then I has better advice, by all means please post it, mine info is 2 years out of date.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    3. Re:SGS4G support Please! by modmans2ndcoming · · Score: 1

      I installed a couple different Modem ROMs.... the last one I installed gave me the best wifi signal. Never had problems with cell signal.

      I am not too comfortable installing a ROM for another phone... no matter how moderate the difference in hardware....I have Odin and the proper files to recover, but I hate it when I soft brick my phone.

  5. Re:Lies by exomondo · · Score: 2

    It's easier to just say which releases/versions of Android are open source rather than trying to say whether the entire project is or is not. Pretty much all of them are with the notable exception (up until recently) of Honeycomb.

  6. Ubuntu by MrEricSir · · Score: 1

    Not sure if it's "real" enough for you, but Ubuntu is coming to tablets.

    Whether that means you'll be able to run any Linux application you like remains to be seen, but I imagine if it's Debian-based it should be quite hackable.

    --
    There's no -1 for "I don't get it."
    1. Re:Ubuntu by arazor · · Score: 1

      Not sure if it's "real" enough for you, but Ubuntu is coming to tablets.

      Whether that means you'll be able to run any Linux application you like remains to be seen, but I imagine if it's Debian-based it should be quite hackable.

      Ubuntu is already running on the ASUS TF101 and an idiot proof install is in early stages of development.

    2. Re:Ubuntu by geminidomino · · Score: 1

      Ubuntu is already running on the ASUS TF101 and an idiot proof install is in early stages of development.

      The image file self-destructs if they try to install it?

  7. and in other news... by Anonymous Coward · · Score: 0, Troll

    Cyanogen still doesn't have a functional camera for the Captivate

    1. Re:and in other news... by Bill,+Shooter+of+Bul · · Score: 1

      works for me.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
  8. droid3 by Anonymous Coward · · Score: 1

    When's it going to work on the droid 3? :(

  9. You mean Droid 1? Re:droid3 by BillTheKatt · · Score: 2

    You mean when is it going to work on the Droid 1 right? You kids and your Droid 3's. Back in my day we had 550 mhz and 256 MB RAM and had to use it on the way to school in a blizzard, uphill both ways. Still rocking the Droid 1 with CM7, although this little puppy is getting slooooowww...

  10. Re:Lies by markkezner · · Score: 4, Informative

    That's right. Just to clarify, even Honeycomb's code has been released at this point, although it's not "tagged" so it isn't as easy to get to. Google did this on purpose to encourage developers to build using the Ice Cream Sandwich code instead, which is probably better for everyone involved.

    --
    Dangerous, sexy, turing complete: Femme Bots
  11. What happened to qwerty devices? by nightfire-unique · · Score: 4, Insightful

    I recently left the n900 world for an Android phone - my first - the Samsung Captivate Glide (SGH-I927).

    I expected to root it easily; I hadn't realized how hostile manufacturers are becoming towards their customers. Indeed, as I write this, I still haven't succeeded. It actually feels like I may be the only person in the world who bought this device, which, to me, is utterly confounding.

    What happened to qwerty phones? Why did they fall so far in popularity? I find it excruciating to surrender half my screen real estate to an on-screen keyboard.

    This Nexus S looks great, and is easy to root and flash, which is nice. But, without a keyboard? To me.. useless. Come on Google! Put some weight behind a qwerty model of this!

    And for the love of god, start playing hardball with manufacturers that lock their bootloaders and fail to provide a clean method of rooting! Simply deny them access to the Google utilities.

    --
    A government is a body of people notably ungoverned - AC
    1. Re:What happened to qwerty devices? by dell623 · · Score: 5, Interesting

      Qwerty keyboards are useless. Swype or similar input methods are faster and more intuitive than mashing tiny hard keys that add bulk and extra mechanical components that can fail. Screens are huge these days so seeing the keyboard on screen while typing is no big issue. Instead of getting a thicker bulkier keyboard equipped phone a bigger screen phone is a better compromise. Physical Keyboards are simply inefficient on mobile devices - not that great for typing, add bulk etc.
      The Galaxy Nexus kind of device with no buttons at all is the future, even the soft buttons disappear for video etc, maximizing screen real estate. Ultimately you want the smallest possible device with the biggest possible screen.

    2. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      Those little thumb keyboards are hard to type on and slow. Swype is much better and faster.

    3. Re:What happened to qwerty devices? by phoenix_rizzen · · Score: 4, Interesting

      I hear you.

      It would be so nice if the major Android phone manufacturers would stop spitting out new phones every 6 weeks, and instead focused on 2-3 phone hardware platforms per year. I say platforms in that they use the exact same innards (SoC, storage, etc) but with 1-2 screen sizes, and with/without keyboards.

      Sony Ericsson is the closest to doing this with the Xperia Mini/Mini Pro, Xperia Neo/Pro, and Xperia Arc/Play. They all basically have the same hardware, with just screen size and keyboard/gamepad variations.

      Just imagine how much simpler life would be for their Android devs, support staff, and customers if they did this.

    4. Re:What happened to qwerty devices? by Microlith · · Score: 3, Insightful

      I hadn't realized how hostile manufacturers are becoming towards their customers.

      But you aren't the customer. The customer, at least in the US, is the mobile carrier who wants to restrict you as much as possible. The fallout from this is that even in places where you can buy the device unlocked, the devices are still crippled (see Motorola.) The end result is that ~2 years on I am still using my N900.

    5. Re:What happened to qwerty devices? by phoenix_rizzen · · Score: 4, Insightful

      What's the point of having a big 4" screen if you constantly lose half of it to an on-screen keyboard? Especially in landscape when vertical pixels are at a premium? If I wanted to constantly have a 1" high screen, I'd buy an older model QWERTY phone, the landscape screen size would be the same as a 4" keyboardless phone.

      Not everyone buys a phone just to watch videos or play games. some buy it to use as a phone (giant screens aren't that great to talk on), or to type a lot (QWERTY phones have more usable screen space even if the actual screen is smaller), or have issues with on-screen keyboards.

      There's no such thing as "the one perfect phone for everyone", just as there's no "perfect keyboard" for everyone. Hardware keyboards aren't going anywhere. Here's hoping more manufacturers add them to their offerings.

    6. Re:What happened to qwerty devices? by swanzilla · · Score: 1

      My keyboard and Swype usages are pretty much one-to-one on my soon to be two y/o Droid 2...making my next choice more difficult than usual. The dealbuster that has me leaning towards a keyboard for the next device is passwords. This post being a case study, with the keyboard coming out for a pretty basic, mostly alpha string.

    7. Re:What happened to qwerty devices? by Belial6 · · Score: 1

      Heck, forget building it with a keyboard. Just keep the exterior form factor the same, and offer a Bluetooth keyboard that snaps on to the phone and can swivel out. If they would keep the outside form factor consistent, they could probably even get peripheral manufacturers to handle making the keyboards.

      (Yes, I know that the iPhone has this. Peripherals are the one thing that iOS devices crush Android in.)

    8. Re:What happened to qwerty devices? by Zorque · · Score: 1

      They still exist, but they're not very prominent. I use an HTC Evo Shift 4G, basically a smaller version of the Evo with a slide-out keyboard, and I far prefer it to any of the touchscreen-only devices I've played around with.

    9. Re:What happened to qwerty devices? by Mortirer · · Score: 1

      I went from the Motorola cliq to a Nexus S. The cliq is a POS I also was apprehensive about the lack of keyboard, but I haven't missed it now that I don't have one. The screen is big enough that there is enough room to type without my fat fingers getting in the way. Besides, the smaller form factor is great in a pocket. Also, it doesn't have as many moving parts to break. I really recommend the nexus lines of phones.

      --
      Curiosity killed the cat, but cats have 9 lives.
    10. Re:What happened to qwerty devices? by chrb · · Score: 1

      Yeah, it turned out phones with keyboards are bulkier and people don't buy them. Use a bluetooth mini keyboard instead.

    11. Re:What happened to qwerty devices? by forkazoo · · Score: 4, Insightful

      I recently left the n900 world for an Android phone - my first - the Samsung Captivate Glide (SGH-I927).

      I expected to root it easily; I hadn't realized how hostile manufacturers are becoming towards their customers. Indeed, as I write this, I still haven't succeeded. It actually feels like I may be the only person in the world who bought this device, which, to me, is utterly confounding.

      I still carry my n900, but I got an iPhone for work, and bought an Android tablet recently, and I have had the same rude awakening of just how user-friendly the n900 actually was. I have spent the last two years looking for something newer, faster, and *better* than my n900, and I just haven't found it. Given how awkwardly Maemo begat Meego which has stumbled into Tizen, I'm not even very optimistic that anything will come along in the forseeable future. I'd practically kill to have a whizzy new n900 with the latest CPU and screen, but nobody wants to sell it to me. Even the most open android thing kind of pales in comparison to the promise of a genuinely open platform.

      I love the fact that I can write PyQt scripts while I am on the subway that work perfectly on my real computers when I get to the office/home. I can forward X11 apps to/from my phone just as I do with my normal computers. (Obviously, some aren't worth forwarding to a phone, but others work just fine on a touch screen.) The X11 forwarding over SSH with implausible complicated SSH tunnels between overly complicated networks is, AFAIK, impossible on Android, despite the fact that Android has VNC and ssh terminal emulator apps. In the context of working on a real big "Enterprisey" production network, having a "normal" ssh/X11 stack makes a huge difference.

      I know the n900 never got Angry Birds, or whatever, but it has been an invaluable tool in a way that no other mobile device seems willing to be, not even the "very open, easy to do whatever you want" Android platform, which is disappointing.

    12. Re:What happened to qwerty devices? by assantisz · · Score: 4, Insightful

      Try using an ssh client like ConnectBot with a virtual keyboard. You are losing enormous amounts of screen real estate that you need to get work done. I am in nightfire's camp - a phone without slide-out keyboard is utterly useless. I do not want to schlep around another piece of equipment in form of a bluetooth keyboard or some such. There are some hardware solutions for the iPhone 4 (cases with built-in keyboards) but the accessory market in the Android world sucks donkey balls thanks to manufacturers pumping out a new phone every 7 days.

    13. Re:What happened to qwerty devices? by gl4ss · · Score: 1

      a) swype isn't faster, b) you can't see shit if your screen is used up by OSK, c) the keyboard can be a slider, to add the same usable screen area and a osk, you can't do sliding really.

      it's no fun when your control buttons disappear anyhow.

      there's one real reason why they're dropping button counts. COST. so are you just trolling for max profits.

      (things might be different if you had flexible displays and actual tactile feedback for on-screen-keys.)

      --
      world was created 5 seconds before this post as it is.
    14. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      If the N900's OS was open source, then it will have been ported to everywhere, so you can still run it on newer hardware. If it's not ported, then it very likely wasn't free. You were a hostage, in essentially the same situation as an iPhone user except with better (but still chained) software. So: which is it? Where is Maemo? Was it just another Amiga or OS/2, or is it Linux?

    15. Re:What happened to qwerty devices? by dell623 · · Score: 1

      You only lose half the screen while you are typing. As I said, if you're fine with carrying bulky keyboard phones you'll be fine with carrying a 4.65" screen phone like the Galaxy Nexus or even the 5.3" Galaxy Note.

      What do you mean giant screens aren't that great to talk on? That's a function of hardware, microphones have been at that distance from the mouth for a long time, ironically in tiny cheap Nokia phones which didn't reach from your ear to your mouth. If giant screens phones offer poor call quality, that's a failure of that particular device.

      What do you mean 'type a lot' on a phone? It is a phone, you shouldn't be typing novels on it. I type on a phone when there is nothing better around. Buy a tablet if you want to type a lot and want screen real estate while typing, which you can afford if you can afford the prices of modern smartphones. A smartphone is ultimately going to be a tiny cramped device, that is not going to change. Having the largest screen possible is the best compromise for the vast majority. And what do you mean 'issues with on screen keyboards'? It's a matter of getting used to them - the same way people had 'issues with touchpads' when laptops became popular and gave that as a reason why laptops won't replace desktops. Eventually, almost everyone got used to touchpads.

    16. Re:What happened to qwerty devices? by DMUTPeregrine · · Score: 1

      What's the point of a built-in keyboard on a phone with bluetooth anyway? More moving parts, impossible to touch type on, always bulky even when you won't be typing, etc, etc. Get a bluetooth keyboard and be done with it. If you don't care about touch-typing there are bluetooth keyboards about the same size as most phones. eg the Rii mini. If you do, a folding keyboard may be better, such as the Verbatim 97537 or any of the numerous others.

      --
      Not a sentence!
    17. Re:What happened to qwerty devices? by dell623 · · Score: 1

      Swype IS faster for english words and it painlessly adds words to the dictionary. Once you start hitting 4.5"+, swype in portrait mode is just about perfect. For anything you would reasonably do on phone having part of the screen obscured while typing isn't a huge deal.

      No one (translated as 'not enough people to be commercially viable") wants slider phones. No one bought the n900 except a few nerds who think being able to SSH from a phone is really cool even if you spend 5 times more time to do anything than you would on a laptop. When I was moving on from my Blackberry Bold I considered the n900 before getting a Galaxy S. Thank god I did.

    18. Re:What happened to qwerty devices? by dell623 · · Score: 0

      If Android manufacturers had a clue Apple wouldn't be steamrolling them. Yes I know how Android phones sell more. However, Apple's profit margins are way higher. They would still dominate the $600+ price range, and Apple doesn't give a damn about the low end of the market. You can see this in how Apple still dominated mobile browser stats despite having a much smaller share of the smartphone market. Most android buyers don't use their phones very 'smartly' whereas virtually all iPhone users seem to browse and use web apps constantly.

      And don't even get me started on Android manufacturers' feeble attempts at the tablet market. At this rate despite the two year lead for Android Windows 8 will kill them.

    19. Re:What happened to qwerty devices? by dell623 · · Score: 1

      If you are in a position to attack a bloody bluetooth keyboard to your phone you are in a position to use a tablet. So buy one.

      You think tablets are expensive? What about this: http://www.ebay.com.au/itm/300625719205?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649

      a fraction of the price of a smartphone and still a million times better than attaching a bluetooth keyboard to a pathetic 4" screen.

    20. Re:What happened to qwerty devices? by dell623 · · Score: 0

      You'll be better off with a proper linux tablet than a tiny phone for doing all that. They are coming soon. As for doing all that on a phone, you're an insanely miniscule proportion of smartphone users to want to do that from a phone. Maybe when the world of smartphones calms down a bit we will see niche products like that. I doubt it though, because with smartphones the more popular your device is the more custom software ROMs etc you will find for it, that's why even power users are better off going for the popular devices.

    21. Re:What happened to qwerty devices? by dell623 · · Score: 1

      The reason few people know about swype like input methods is the iPhone. It has so dominated the very concept of a smartphone and Apple are so much better at marketing that even their stupid ideas become entrenched. Which is why when people reviewed the Galaxy S II they used the tap keyboard instead of swype and complained how the iPhone keyboard is better. It is how iPhone's auto correct is considered an in joke rather that a design failure. It is why no one comments on how insisting on having just one button like Apple do is as stupid an idea as the one button mouse, it is a result of Steve Jobs' fundamentalist, uncompromising approach to design and choosing design over function.

    22. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      "Qwerty keyboards are useless. Swype or similar input methods are faster and more intuitive than mashing tiny hard keys that add bulk and extra mechanical components that can fail."

      Bullshit. If I can't type without looking, it isn't a decent input method... touchscreen devices cause me pain and possibly injury in the future, because I constantly need to look at the freakin screen while I'm typing. So it's either walk or type, unless I want to run into telephone poles or get run over by Granny in her motorized wheelchair...

    23. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      So how do you use that bluetooth keyboard while standing in line, or when using public transportation? The whole point of typing on a phone is that you don't need a flat surface to put down something the size of a small laptop...

      I've done the folding Bluetooth Keyboard thing, and it sucked. Sure, it worked well enough at a desk, but out and about? Pfffff... flipping open a physical phone keyboard is much easier.

      As for the little mini-keyboards the size of the phones themselves: How do you hold it and the phone at the same time while typing? You're going to need to put down the phone somewhere in order to type on that little keyboard with both hands (thumbs), and if you're at a desk or have room on your lap for that, you've got room for a laptop.

    24. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      I'll take a phone with a built in QWERTY keyboard over a tablet for use on public transport any day - ESPECIALLY for getting work done, IF that work involves typing up a lot of natural language. To type decently on the tablet, you need to put it down somewhere, and the typing really isn't that much faster than with a decent QWERTY phone keyboard (too many mistakes without tactile feedback when trying to use all 10 fingers)... and those split thumb boards for tablets are far inferior to a hardware QWERTY phone keyboard.

    25. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      Absolutely disagree. Two thumbs on a keyboard with tactile feedback are better than 10 fingers on a glass touchscreen any day... and if you're unly using two fingers to hunt and peck (or two thumbs, in the case of split keyboards), that gap gets even bigger.

      And until that tablet fits in my front pants pocket without causing me pain, it's useless for mobile computing anyway...

    26. Re:What happened to qwerty devices? by dell623 · · Score: 1

      Sounds like you have never used swype: http://www.youtube.com/watch?v=SJ-RAefCG_c

      Get a Galaxy Note and use Swype in portrait mode for getting work done in public transport if you don't want to use a tablet. Swype doesn't work by tapping, so your direct comparison with 10 fingers tactile feedback etc doesn't apply. Swype (there are other implementations called FlexT9 etc which I haven't used, they may be equally good) is an input method designed for touch screens. It is faster than physical QWERTY phone keyboards. With Swype entering long words is actually easier than entering short words because the pattern you 'draw' is less ambiguous. you can combine tapping for short words and 'drawing' for long words to optimize typing speed. The speed with which I can enter a word like 'implementation' with swype is even faster than on a full size qwerty keyboard. Even considering normal text with shorter words punctuation etc. it absolutely kills a tiny physical keyboard.

      Physical QWERTY keyboards on a phone are just an awful design compromise.

    27. Re:What happened to qwerty devices? by dell623 · · Score: 1

      Now we are into the incredible minority who want to touch type on a phone. I used a blackberry bold for over a year but couldn't touch type, I didn't specifically try to learn as I wasn't interested.

      But how many people consider it essential to touch type on a phone and are willing to practice for months to be able to do that (and if you have to change phones, the keyboard is a different size and keys may be a different shape so you have to learn all over again).

      Want to type while walking around? Use voice recognition. plain vanilla or with Siri.

      It's like the CRT vs LCD debate. For a long time some people I know made a case for how CRTs were better in a way the overwhelming majority wouldn't care about, hoarded Sony Trinitron desktop monitors. they all use LCDs now.

    28. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      I tested Swype quite thoroughly back when it was new. It's still a dictionary based input method that requires the user to enter new words manually in order to compensate for the inherent lack of accuracy...

      I don't want to enter a new word into the dictionary every time I use it - this includes acronyms.

      I don't want to switch languages on the keyboard every time I talk to a different person.

      I don't want to have to look at the screen while I'm typing.

      I don't want to lose screen real estate while typing.

      I don't want to have to position the cursor with my finger in the touchscreen.

      And yes, I'm using a touchscreen-only device right now, and yes, it's driving me bat-shit-insane.

    29. Re:What happened to qwerty devices? by dell623 · · Score: 1

      See my post above about the Galaxy Note and swype: http://hardware.slashdot.org/comments.pl?sid=2548386&cid=38199868

      tl;dr: Galaxy Note fits in non hipster pants pockets and swype isn't tap based so your criticism doesn't apply.

    30. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      Tap based or "slide-around"-based, it's still a keyboard without tactile feedback, based on a user dictionary to compensate for the inherent lack of accuracy. And still more or less impossible to use without constantly looking at the damned thing. :(

    31. Re:What happened to qwerty devices? by evilviper · · Score: 1

      Swype or similar input methods are faster and more intuitive than mashing tiny hard keys that add bulk and extra mechanical components that can fail.

      Swype fails horribly when you need to type non-dictionary words. Touchscreens also lack arrow keys, necessary for navigating text boxes and more. And in portrait mode, Swype takes up the ENTIRE screen, making it completely useless. The lack of keyboards is precisely why people believe smartphones and tablets are consumption-only devices, when, in fact, they can do a hell of a lot when proper input menthods are available.

      I also challenge you to prove that swype or any on-screen keyboard is faster, as I know I'll blow by anyone, typing with my thumbs.

      And yes, on-screen keyboards fail miserably when you try to use your phone for real work, like SSH or VNC/RDP connections.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    32. Re:What happened to qwerty devices? by dell623 · · Score: 1

      You haven't used a recent version of Swype or other similar keyboard apps, maybe you tried an early beta.

      Swype automatically adds words to the dictionary, you only have to tap non dictionary words the first time. It remembers words you enter. Including acronyms.

      Where exactly do you look while you are typing on a laptop? At the ceiling?

      How exactly do you position your cursor without using a finger? some kind of telepathic method only found in phones with physical keyboards?

      Swype has an excellent view for editing with cursor keys etc.

      Use Swype, either the latest beta or even better on a phone that comes with it preinstalled (all samsung phones for example) with an open mind if oyu actually want to make a fair comment instead of posting lies like "enter a new word into the dictionary every time I use it".

      Switching languages on the fly is also very easy on Swype: http://beta.swype.com/#implang

    33. Re:What happened to qwerty devices? by dell623 · · Score: 1

      - Swype automatically adds words to dictionary, only have to tap them in once.

      - Swype edit screen with arrow keys etc you can reach with one swipe: http://media.photobucket.com/image/swype%20edit%20screen/syntax_photos/SwypeEdit.png

      It takes less than half the screen in portrait mode in 800x480: http://cdn-static.cnet.co.uk/i/c/blg/cat/mobiles/samsunggalaxys2/swype.jpg

      Takes up even less in bigger screen/resolution phones.

      You shouldn't be using phones for real work except in an emergency. And in those situations touchscreen with Swype is fine.

    34. Re:What happened to qwerty devices? by dell623 · · Score: 1

      Why would ANYONE want to ssh from a phone unless they have no choice?

      If I had a work issue I would stop somewhere whip out a laptop and use that to ssh. You cannot do real work on any phone.

    35. Re:What happened to qwerty devices? by rtfa-troll · · Score: 1

      The (low level) OS was open. The GUI / User interface were not. Basically nobody succeeded in getting a full pure Debian install running as the main OS on the N900 but you could get a Debian chroot. That makes it "more open" since you could install the software you wanted including full Debian compatible software, but not sufficiently open.

      A good warning against people who roll their own distributions.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    36. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      "You haven't used a recent version of Swype or other similar keyboard apps, maybe you tried an early beta."

      Correct - however, the concept had big problems back then, and it still has big problems now.. However, if you have a link to a (working) APK, I'd be happy to try it again.

      "Swype automatically adds words to the dictionary, you only have to tap non dictionary words the first time. It remembers words you enter. Including acronyms."

      That's just it - a user dictionary exists, and in order to input new words, I need to switch from swyping to tapping. So every time you swype out a word that turns out to not be in the dictionary, you need to take an additional 5 seconds to tap it out manually...

      "Where exactly do you look while you are typing on a laptop? At the ceiling?"

      Most definitely not at the keyboard. And I wasn't referring to laptops - I was referring to phones with physical QWERTY keyboards, their main benefit being that you can type while walking without constantly running into things because you need to constantly stare at the screen.

      "How exactly do you position your cursor without using a finger? some kind of telepathic method only found in phones with physical keyboards?"

      Never heard of a D-Pad? Nearly all Android QWERTY phones have some kind of a D-Pad or a set of cursor keys... the touchscreen phones - not so much.

      "Swype has an excellent view for editing with cursor keys etc."

      So every time I need to go back a few letters for a correction/change/insertion, I need to switch to the "cursor view", move the cursor, switch back to the regular view an THEN type? Ball-hair removal with an electric drill sounds more pleasant...

      "Use Swype, either the latest beta or even better on a phone that comes with it preinstalled (all samsung phones for example) with an open mind if oyu actually want to make a fair comment instead of posting lies like "enter a new word into the dictionary every time I use it"."

      That sentence came out wrong - obviously I don't mean that you need to enter the word manually every time you use it... just once. What I meant is that you need to do it for every new word...

      "Switching languages on the fly is also very easy on Swype: http://beta.swype.com/#implang [swype.com]"

      So the same as, well, every other halfway modern soft keyboard, huh? Language switch button, gesture, sliding across the space bar... it's all been done, and it all still requires you to switch languages manually depending on who you're talking to. If you use a lot of IM and talk to people who each speak different languages, it'll piss you off pretty quickly...

      That said, I'd gladly try Swype again to see if it's improved enough to be useful, as I currently don't have a phone with a physical keyboard (which was, to reiterate, pretty much the biggest mistake I've ever made, tech-wise)... if only I didn't have to jump through hoops to do so.

      As for Samsung devices... I'm not really that into featherweight plastic, oversaturated colors and fuzzy text. Here's to a 720p IPS display with the smallest possible diagonal and a slide-out keyboard!

    37. Re:What happened to qwerty devices? by L4t3r4lu5 · · Score: 3, Insightful

      Jesus, buy a netbook. £200-300 (half the price of the phone in your hand) and you get a keyboard with keys you can actually press (albeit not as well as a full size keyboard) and a much better screen to work on.

      The thought of anyone trying to do actual work on a smartphone boggles my mind.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    38. Re:What happened to qwerty devices? by MrHanky · · Score: 0

      You seriously recommend a tablet for typing? Idiot.

    39. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      Repeat with me: "I am a not typical user". How many people do you think rely on ssh in a phone? Most people do not need/want/buy phones with physical keyboard.

      On the other side, I would like my phone to have one as well, but looking at the HTC lineup here in the Nederlands, only the Cha Cha have it. =P

    40. Re:What happened to qwerty devices? by dell623 · · Score: 0

      You seriously recommend a mobile phone for typing a lot, for doing actual work? Idiot.

    41. Re:What happened to qwerty devices? by dell623 · · Score: 1

      You can get 720p phones from LG and HTC and others too and those screens look incredible.

      Register on swype.com to get am email link to download the latest apk, quicker than trying to find a link to the latest version through google.

      There are some narrow scenarios where physical keyboards are better, as you said if you are switching languages every minute, it would be useful, or for touch typing.

      The number of people who care about those scenarios though is very small. And even among them most would prefer having a larger screen and slimmer phone over something bulky with a physical keyboard.

      You can edit in the normal view, but it is quicker to first type everything and then switch to the edit view to correct typos.

      D-pad like things are unrelated to physical keyboards. The HTC Desire had an optical trackpad and the Nexus One had a trackball iirc but I don't know if any current phones without physical keyboards have one, you'll have to find out.

      I don't see how it's a huge hassle to have to tap non dictionary words in once, unless you are making up words all the time?? And it doesn't take five seconds..

    42. Re:What happened to qwerty devices? by MrHanky · · Score: 1

      You wrote: "It is a phone, you shouldn't be typing novels on it Buy a tablet if you want to type a lot". Yet I said nothing about typing a lot on smartphones, no one did (except you), so your counter-argument kinda sucks. Let me reiterate: you're an idiot.

      Sure, there are worse things to write novels on than a tablet. The etch-a-sketch, for instance. Stone slates. Water. But there is such a wide choice of better, more suitable technologies for the task: pen or pencil on paper; laptop and desktop computers; typewriters. I'll concede that even a decent mobile phone is better suited for writing novels than a tablet, for simple reasons of ergonomics. Editing would be hell, though.

    43. Re:What happened to qwerty devices? by gl4ss · · Score: 1

      slider phones are viable, they sell pretty well. several phone companies would like to ship their big earner models without them though, as they want less moving parts for assembly - and because several large purchasers(operators) have designated them as "business" phones..

      also for other reasons, I got a xperia play. it has a slide out controls. they're absolutely fantastic for browsing information compared to obscuring the screen with fingers, trying to hit the tiny links or doing the pinch zoom ripaska.
      also, osk sucks for gaming on the train big time. but the phone is much more balanced in hands with the slider open, I absolutely loathe the way galaxy S feels when held due to this(it's too thin overall).

      "no-one" bought n900 because it's a fucking BRICK, wasn't marketed, was late to market and the hw isn't up to classic nokia quality(just ask anyone who's had the usb port break on it or the screen sensor gone bad - the shipped model was proto quality and that probably made it more expensive to do as well than if the design had been actually finished).

      I don't mind the osk on the play, but it does take over the screen when typing. that sucks for anything where you might get a message when typing(chat), though it "only" takes half the screen in portrait mode - I would prefer a mini-qwerty to sit between the gaming controls. or do a second slider screen(slider, NOT flip open..). that makes it non-ideal for ssh. now where would I use ssh on it? probably on some trip to relatives or on a holiday.

      and no, Swype isn't the fix. swype isn't some omg out of this world magic tech like you seem to think and promote. it has the same biggest problem as already mentioned by other people that you can't use it while walking, can't use other osk's while on the move either though- they're all worse for that than typing on a traditional 9 pad(and I did a lot of slashdot posts back in the day typing on one and probably made less typos and used more coherent language than when typing on a "real" keyboard). I hate predictive input as well, in bilingual use it's not that uncommon that you have to mix the languages to the same sentence or use product names, function names, nicknames and everything else that just won't be in the dictionary and is quite likely to be used on the phone only 1-3 times during the time you own it. too bad if you own swype stock but I really don't see it as faster for character input than two-thumb qwerty.

      of course then there's 123212 other uses that physical keys are better for, from drum machines to application and setting shortcuts.

      (and no lugging around a bt keyboard doesn't cut it, and no "omg why would you do that on a phone when you have a netbook" etc arguments are just silly. I have a laptop, not gonna carry it everywhere or use it in a cafe, the bt keyboard is a novelty thing too, might just as well use the laptop)

      --
      world was created 5 seconds before this post as it is.
    44. Re:What happened to qwerty devices? by dell623 · · Score: 0

      How clever, you removed the part that actually explains why I suggested a tablet: "AND want screen real estate while typing".

      You got modded up despite the personal insult by selectively quoting me and misrepresentation. Impressive, you should consider taking part in the republican primaries.

      It's ludicrous to complain about limited screen real estate on a 4" phone while typing, if you care that much about screen real estate WTF are you doing using a 4" screen?

      I think the Galaxy Note is the perfect compromise for typing and portability and I consider it a tablet.

    45. Re:What happened to qwerty devices? by jc79 · · Score: 1

      You seriously call somebody an idiot for expressing a view contrarian to your own, without offering any argument or evidence in support of your own position, nor making any attempt to explain why they might be wrong? Rude.

    46. Re:What happened to qwerty devices? by dell623 · · Score: 1

      A tablet with a slim sliding keyboard makes way more sense for all the things you mention - Asus have the right idea but need a better product.

      You still take way longer to type anything on any kind phone than a full keyboard. Phones are for consuming content and convenience. Typing on a phone will ALWAYS suck. I wouldn't use a phone in a cafe. If I sit down and have more than five minutes and want to do something productive I never want to use a phone because it's tiny and clumsy and inefficient.

    47. Re:What happened to qwerty devices? by dell623 · · Score: 1

      Phone companies ship non slider phones not because they want fewer moving parts but because they know what the iPhone and Android did to the Blackberry and the N900 and N97 and E71/72 etc. Right now you can get a couple of keyboard phones but they are a dying breed, and don't receive cutting edge hardware or design. They might trundle on in that form..

      I'll take a laptop on a holiday if I plan to SSH. I always take one anyway, don't see how I could survive with a phone as my sole computing device.

    48. Re:What happened to qwerty devices? by Miamicanes · · Score: 1

      > SSH from a phone? Why on earth would you do that except as a last resort?

      Because it's Saturday night, you're at a bar with your friends, and the server decided to get bitchy on you. ConnectBot means not having to trek back to your car, boot the laptop, tether, and connect up to fix something you can troubleshoot in about 30 seconds.

      And yes, ConnectBot sucks donkey balls with onscreen virtual keyboards, partly because Android doesn't allow you to have a default system-wide IME, but specify specific IMEs for specific programs (I'm a Graffiti guy, but have to switch manually to some other keyboard to use Connectbot because Graffiti doesn't have any concept of cursor-up). It's not ConnectBot's fault, but that doesn't make the situation suck any less.

    49. Re:What happened to qwerty devices? by MrHanky · · Score: 1

      Actually, there was an ellipsis in there, but Slashdot cleverly removed it. Apparently, Slashdot demands you use three full stops (...) instead of unicode U+2026. And I don't see why you complain, as your argument is still utter bullshit.

    50. Re:What happened to qwerty devices? by Miamicanes · · Score: 1

      We hoarded Trinitron monitors up to the point where a LCD capable of 2560x1920 became semi-affordable to people who could previously afford a CAD-quality 21" Trinitron. For people used to having 1920x1280, 1920x1080 was a really harsh, bitter pill to swallow, especially when you factored dead/stuck pixels into the equation. I bought my first LCD around 2007, and had a daily love-hate relationship with it up until the happy, healing day I threw it in the trash on a pretense over a dying inverter and replaced it with a 30" 2560x1920 (now flanked by a pair of 22" portrait-orientation 1080x1920 displays)

    51. Re:What happened to qwerty devices? by dell623 · · Score: 1

      You just described a last resort scenario. So out of all the system admins in the world a phone with a physical keyboard is suitable only for those who would buy a phone that is inferior to alternatives in every other way, just so they can solve a problem by SSH that is complex enough for someone to call them about but not too complex to solve over a tiny phone screen. Great target market there, I see a boom in them keyboard phones coming!

    52. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      http://www.sonyericsson.com/cws/corporate/products/phoneportfolio/specification/xperia-pro

    53. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      Incapable of writing a post without insults, and with two accounts just so you can mod up your own posts? How delightful.

      Your argument is bullshit too. Wait, you don't even have one, straw man arguments don't count.

      Have to post AC because of post limit.

    54. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      I presume you mean 1920x1200 but that makes no sense because you can still get 1920x1200 monitors.

      Sony stopped producing Trinitrons a while ago when 2560x1600 high color depth and gamut LCD screens were still insanely expensive and had slow response times and other issues.

      And the people wanting CRTs back then had better reasons than people wanting keyboard phones have given here.

      Have to post as AC because of post limit.

    55. Re:What happened to qwerty devices? by tomthegeek · · Score: 1

      I hear you, I was just thinking this the other day. My last two phones have been touchscreen only, the Nexus 1 and now a Captivate (ATT Galaxy S). I switched from sliding qwerty when I got my first Android phone and did it mostly because at the time that was really the only option. Now that there are more choices I have been looking for a sliding Android because I have never been that great with the on-screen keyboard compared to a real keyboard.

    56. Re:What happened to qwerty devices? by Microlith · · Score: 1

      The GUI / User interface were not.

      They were. There were some infrastructure things (dsme, bme, some applications) that weren't. You can actually get a Mer/MeeGo derived OS that runs the same desktop environment in Cordia HD.

      And Mer/MeeGo, incidentally, are even more open than Maemo was on the N900. The regular stumbling blocks of GPU drivers still apply.

    57. Re:What happened to qwerty devices? by bemymonkey · · Score: 1

      "There are some narrow scenarios where physical keyboards are better, as you said if you are switching languages every minute, it would be useful, or for touch typing."

      Well, I'm constantly switching languages and the only time I *don't* touch type is when it's impossible due to the keyboard... it's just faster and more efficient.

      As for D-Pads: I actually have an HTC Desire, and the optical joypad isn't a great alternative (the trackball on the N1 is nice though). Furthermore, these are two of the last phones to come with something like this. Check out all the following phones... with the exception of the Desire Z, they're pretty much all entirely missing any cursor/D-Pad function :(

    58. Re:What happened to qwerty devices? by DMUTPeregrine · · Score: 1

      Some of the mini keyboards include a "case" for the phone. They slide out of the external case. I've only seen them for iphones though.

      --
      Not a sentence!
    59. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      If you have to use SSH at a bar from a phone when you are with friends on a Saturday night, you need to get a new job. Or something is seriously wrong with you. But yes, a physical keyboard comes in handy if one sends a rather long facebook update or a text message while sitting in a bar with friends on a Saturday night. Even though I like the keyboard on my OG Droid, I might have to make do with a keyboard-less phone when my contract is up, because I think there are more root-able keyboard-less phones out there.

    60. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      http://store.ovi.com/content/23158

      But who with an N900 actually used the Ovi store, when everything useful was in the apt repositories?

    61. Re:What happened to qwerty devices? by quasipunk+guy · · Score: 1

      My iPhone has four buttons and a switch. Maybe yours is defective.

    62. Re:What happened to qwerty devices? by evilviper · · Score: 1

      Why would ANYONE want to ssh from a phone unless they have no choice?

      Because it's extremely convenient, to have a thin client in your pocket at all times. In a meeting, and it would help to know something about a server? Quick and easy. Ditto for needing to VNC/RDP to your main system to look-up some things on them... Even a minimal amount of typing is a nightmare if you've got to use an on-screen keyboard.

      With a qwerty keyboard, SSH on via a phone only minimally painful. Even when sitting at home, and needing to do some installations or configuration on my DVR or such, I just pull out the phone. Sure, I've even got a netbook, which I'll fire-up if I've got serious work to do, but a little thing that fits in one hand, and floats in the air (don't need a table, not taking up my lap, etc.) and can be dropped in a pocket at a moment's notice is extremely convenient and very useful.

      ConnectBot on SSH is pretty flexible and capable, on-par with Putty for xterm emulation. I can get >80x24 on my phone in a readable font, which is the magic number where you can do everything, rather than only a subset of programs work properly.

      You cannot do real work on any phone.

      I do. Therefore it most certainly can be done.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    63. Re:What happened to qwerty devices? by evilviper · · Score: 1

      - Swype automatically adds words to dictionary, only have to tap them in once.

      Clearly you've never tried it... It gets more and more confused the more words get added to it, and it often throws in a wrong dictionary word instead of the arbitrary commands you want to enter. And you'd be amazed how useless swype is where filesystem paths are involved.

      It takes less than half the screen in portrait mode

      SSH in portrait mode is entirely useless, end of story. 80x24 is the magic number, not 12x40.

      You shouldn't be using phones for real work except in an emergency. And in those situations touchscreen with Swype is fine.

      I'm so glad you're here to tell me what I SHOULDN'T be using my phone for. And here I was getting real work done, I had no idea I was breaking the law, or doing something immoral, or whatever. Clearly all the time I've saved myself and others with my ability to quickly login to the servers at work to fix problems and look up info has been a horrible mistake...

      I wonder, do you also know the minimum size laptop I can use to get work done? I mean, my EEE Netbook is pretty small, is that supposed to be reserved for emergencies also? Hey, if some random idiot on slashdot says so, I guess I've gotta carry a 10lbs desktop replacement with me at all times, on the off chance I'd like to quickly look-up some info, or fix a server while I'm out of the house, since it's apparently wrong to do with a phone, and, I presume, other small devices as well...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    64. Re:What happened to qwerty devices? by Anonymous Coward · · Score: 0

      You must have HUGE pockets if you can fit a netbook in one of them. It may not be optimal to work from a smartphone but if you have a decent keyboard attached to the phone if you need or want to when out and about.

    65. Re:What happened to qwerty devices? by phoenix_rizzen · · Score: 1

      You don't really need to keep the physical form factor the same in order to create a viable accessories ecosystem. You just need to keep the ports in the same location.

      The reason the Apple accessories market is so huge is that there's only 1 connector you need to worry about, it's always located in the same location, it's always the same size, etc.

      We don't need a "dock" connector on Android, as we already have mini-HDMI and micro-USB which covers everything a "dock" connector would: video, audio, data, power, etc. Shoot, you could even put the headphone jack next to them if you want to support analog audio.

      What's missing is a standardised location (put them both side-by-side) and distance between the ports. Every phone manufacturer puts them in different places, and it's different even between phone models.

      If they would standardise this (even if only within a single manufacturer, across all their phone models), accessories makers would appear overnight.

    66. Re:What happened to qwerty devices? by phoenix_rizzen · · Score: 1

      Keyboard phones are not "bulky". The Sony Ericsson Xperia Pro is the same thickness as an iPhone 4/4S. The Droid 3 is thinner. Others are the same thickness. Unless you are comparing them to uber-thin (and unwieldy) phones like the Droid Razr, keyboard phones are no less "bulky" than non-keyboard phones.

      The giant screened (4"+) non-keyboard phones are a lot more unwieldy than a smaller-screened (3.5-4.0") keyboard phone, due to the width of the screen. Thickness is actually a good thing in a phone, as you have something to grab onto and hold. A super-thin, wide phone (like the Galaxy S, Galaxy Nexus, Droid Razr, etc) are actually harder to hold *because of* their thinness.

      As for giant phones being hard to talk on, it's due to the awkwardness of holding onto a wafer-thin, extra wide case. They are not comfortable to hold, nor easy to hold.

      As for "typing a lot" on a phone, the main selling features of a smartphone are SMS, IM, E-mail ... all things you have to type. And then the apps. How do you expect to use an SSH client, an IM client, an e-mail app, when half the screen is taken up by the onscreen keyboard, a quarter of the screen taken up by the previous message, and only a quarter of the screen left for your message?

      I don't want a tablet, as they don't fit in my pocket. I want a smartphone that's easy to type on, since it's used for ... typing e-mail, SMS, IM messages.

      I don't want a bluetooth keyboard, as that's just another thing to lose and have to carry around.

      I don't want a crappy onscreen keyboard with no tactile feedback, where my fingers obscure the keys, where keypresses are picked up by the wrong keys due to the size of my fingertips, where the keyboard takes up half (or more) of the screen.

      I want a decent sized screen (3.5-4"), with a hardware keyboard. Thankfully, there are some manufacturers who understand this, and make keyboards versions available.

    67. Re:What happened to qwerty devices? by Belial6 · · Score: 1

      True enough. Google has considered peripherals. The NexusOne has three little contacts on the bottom of the phone. When these are connected, the phone goes into "Car Dock" mode. This means that the OS is notified that the phone is docked, and gives contacts for charging. When the OS gets notified that it is docked, it makes a bluetooth connection to the dock, and your set to go.

      It would be nice if Google would push this feature. If they moved the notification from physical contacts to NFC, the only connection necessary would be for power.

    68. Re:What happened to qwerty devices? by phoenix_rizzen · · Score: 1

      They aren't bulkier, unless you compare them to the uber-excessively-unwieldy-thin phones like the Droid Razr. Any phone that's under 10 mm thick is unwieldy and uncomfortable to hold unless you have childish/girlish hands. Sure, it looks pretty ... but they are a pain to use.

      An Xperia Pro is actually thinner than an iPhone 4/4S. A Droid 3 is actually thinner. The HTC sliders are the same thickness as an iPhone 4/4S.

      Rather than worrying about who has the slimmest dick...er...phone, it would be nice if phone manufacturers worried about "comfort", "fit in the hand", and "extra room for more battery".

  12. Yeah Baby by gearloos · · Score: 2

    Sweetness. Guess I haven't been over on Cyanogenmod for a little too long as I didn't realize Koush was this close. I just happen to have a Nexus S and am a Cyanogen Advocate. I've been running Cyan Roms since about ver3 on my G1 way back and have found that if bugs appear, it usually gets fixed or a workaround is posted fairly quickly. I can actually say I trust most of the Cyanogen stuff to not brick my devices but I do reserve that I have a little experience with this type of thing. Can't wait to go get me an Ice Cream Sandwich !

    --
    "Computers are a lot like Air Conditioners" "They both work great until you start opening Windows"
    1. Re:Yeah Baby by GenP · · Score: 2

      I'd like to run Cyanogenmod on my Nexus S but for the life of me I can't seem to find a procedure that will let me backup my entire phone before I root/wipe :(

    2. Re:Yeah Baby by Anonymous Coward · · Score: 1

      It is referred to as taking a nandroid backup, and requires flashing custom recovery as far as I'm aware. As for the phone's content, TitaniumBackup would be the thing to use.

    3. Re:Yeah Baby by iamhugeinjapan · · Score: 1

      Yes, it's a catch 22. You can't take a nandroid backup without booting a custom recovery image. You can't boot a custom recovery without unlocking the bootloader. You can't unlock the bootloader without wiping the phone, so you can't take a backup. ICS should be out for the Nexus S officially in the next week or two, depending on how accurate Google was by saying "a couple of weeks" after the Galaxy Nexus launches. Then you wont have to wipe anything.

    4. Re:Yeah Baby by gearloos · · Score: 1

      Umm.. no. Everything is right except the unlock the bootloader. You don't have to wipe anything. Just unlock it.

      --
      "Computers are a lot like Air Conditioners" "They both work great until you start opening Windows"
    5. Re:Yeah Baby by duranaki · · Score: 1

      That wasn't true for my Nexus One, anyway. Unlocking the boot loader wiped the user disk, period. Should have been the first thing I did. :( Nexus S could be entirely different though.

    6. Re:Yeah Baby by glitchvern · · Score: 2

      Like the other poster said it's a bit of a catch 22. You can't do a nandroid backup without a custom recovery image. Can't do a custom recovery image without unlocking the bootloader. Can't unlock the bootloader without wiping the phone.

      I had this same problem on the nexus one. The trick is to root the phone without unlocking the bootloader and then using a backup utility that requires root (Titanium Backup or whatever, I actually preferred MyBackup Root). This can be done by using a local root exploit. I think it took me two days to find one that worked on my phone at the time. I think you can even get a clockwork mod installed and install a new bootloader without wiping, backup the whole phone, and then install cyanogen mod that way. I say think because I didn't know at the time but sometimes clockwork mod just plain fails to install a new bootloader and you have to try multiple times. Having already backed everything up I just unlocked the bootloader at that point. The Titanium Backup/MyBackup Root don't create a backup image of the whole phone if I remember right, but instead backup all the data/individual applications. I think they failed to restore one or two of the things on my phone, but they were things synced with my google account anyway so it didn't matter.

      Finding a premade local root exploit is surprisingly difficult. Most rooting guides use the unlock bootloader method and many of those give you no warning it will wipe the phone. All of this information is surprisingly hard to come by and the documentation leaves much to be desired. Everyone says rooting and installing cyanogen is easy on the nexus's, but it turns out that is only true if you don't care at all about the current content of your phone something you'll only discover when you actually try to do it. For that matter you would think backing up your phones contents would be something that would be easy to do. I mean that seams like the sort of thing normal people would want to do, ya know?

      Good luck

    7. Re:Yeah Baby by Anonymous Coward · · Score: 0

      Have you ever unlocked a Nexus S?

      The bootloader warns it will wipe if you unlock it. All the guides warn it will wipe everything. Other phones may vary but the Nexus S wipes.

    8. Re:Yeah Baby by GenP · · Score: 1

      Doesn't unlocking the Nexus S bootloader wipe the phone though?

  13. Obligatory tin-foil fueled comment by Anonymous Coward · · Score: 1

    Something about seeing the phrases "pre-rooted" and "Google Wallet" in the same sentence scares me.

    1. Re:Obligatory tin-foil fueled comment by Anonymous Coward · · Score: 0

      Fear of the unknown. As in "you have no idea what you are talking about".

    2. Re:Obligatory tin-foil fueled comment by grantek · · Score: 1

      Something about seeing the phrases "pre-rooted" and "Google Wallet" in the same sentence scares me.

      You want your financial details to be secured by allegedly-trusted hardware? I'd rather a secure cryptographic protocol that requires the client only to have the correct credentials. Sure, having an unwalled garden (the 'pre-rooted' bit) will lead to data theft through malware, but it's no different to being conned out of cash from your physical wallet.

    3. Re:Obligatory tin-foil fueled comment by Alex+Zepeda · · Score: 1

      Something about seeing the phrases "pre-rooted" and "Google Wallet" in the same sentence scares me.

      Really? I'm more worried about contradictions like this: "has ROM Manager installed, and absolutely no bloatware". Also, props to the CyanogenMod guys for including closed source adware.

      --
      The revolution will be mocked
    4. Re:Obligatory tin-foil fueled comment by aztracker1 · · Score: 1

      Generally the root tool asks for permission on behalf on an app that needs root access... At least that's my experience so far.

      --
      Michael J. Ryan - tracker1.info
    5. Re:Obligatory tin-foil fueled comment by clarkn0va · · Score: 1

      The ROM Manager is a very handy tool for seeing what updates to CM or the modem firmware might be available, as well as alternative ROMs and add-ons, all complete with stats and review. It may not be to CM what apt is to Debian, but it's a bit of a stretch, I think, to call it bloatware.

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    6. Re:Obligatory tin-foil fueled comment by Alex+Zepeda · · Score: 1

      Really? My experience was that the unpaid version of ROM Manager had ads which blocked key UI bits, making it nearly impossible to download anything. ROMs were only available on certain days with the free version, oh, and it had a nasty habit of bricking phones. Sure, I'd much rather fix the code than whine... but ROM Manager is closed source.

      Did I mention ROM Manager also phones home? Dunno how frequently, but it manages to spew backtraces into the logs when it fails to phone home. You're right, perhaps it's not bloatware... maybe it's just spyware? Either way, I made sure it's not installed on my phone.

      --
      The revolution will be mocked
    7. Re:Obligatory tin-foil fueled comment by clarkn0va · · Score: 1

      Are you using the version that comes with CM, or did you install it separately? I'm using CM 7.1 on an HTC Desire and I see no ads. I can't check for ROM updates (it prompts me to install the paid version), but I can download and install the latest ROM through the app regardless, so I'm not missing much.

      I've also installed CM 7.1 on my wife's Samsung Galaxy S (i9000M) and the ROM Manager has a menu item to download radio firmwares, which is a nice touch (if a little useless on a Virgin/Bell Canada phone where most radios don't work anyway) that I wish I had on mine. I don't recall offhand if I saw ads on hers.

      As for being closed source and phoning home, yeah, that's unfortunate. Lesser of two evils in my case, but still unfortunate if true (I've never looked into it so I wouldn't know).

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    8. Re:Obligatory tin-foil fueled comment by starfire83 · · Score: 1

      Are you aware that you can, in the free version, go into the options and turn off ads? It's also up to the ROM developer to put their ROM in ROM manager, not Koush's decision what ROMs are there and which ones aren't. As for the premium ones, besides the CM nightlies, it is once again up to the ROM developer to decide if they want to offer it free or premium. The only time a phone is ever actually bricked is if the bootloader is corrupted and you can't get into a recovery mode. It will, typically, only allow you to download and install a recovery for your phone and your phone only. If you flashed a recovery for a phone that isn't your phone somehow or flashed a GSM ROM and not a CDMA ROM for your phone, then that's your fault and not ROM manager's for causing a soft brick.

      What's wrong about usage statistics and seeing what an app's install base is for an indie developer? Once again, you can disable that in the options.

      When was the last time you actually used ROM manager?

    9. Re:Obligatory tin-foil fueled comment by Alex+Zepeda · · Score: 1

      Last time I used it? Long enough ago that disabling ads wasn't an option. Also, while CMStats is definitely opt-out (and I don't opt out of it), I've not seen anything to allow someone to opt-out of the tracking in ROM Manager. Oh, and bricking phones? That wasn't a result of using the wrong ROM (AFAIK). One way to ensure you can't get into recovery mode is to use ROM Manager to flash a bum recovery image. Lots of ways for things to go wrong.

      Given the fuss over Carrier IQ, I'm not sure why a closed source app like ROM Manager should be given any leeway for tracking its users (by default).

      Whatever. I've made a point of not including it in my CM builds because it's of little to zero use.

      --
      The revolution will be mocked
    10. Re:Obligatory tin-foil fueled comment by starfire83 · · Score: 1

      Not sure what you're getting at. I've flashed many recoveries on many devices in ROM Manager with no issues at all, even without the "erase recovery" option when flashing. Koush does have a habit of making sure an image works before pushing it out to RM to prevent exactly what you're talking about. And if it's an unsupported build of CWM that you're trying to flash then that's up to the person that ported CWM to verify its integrity since CWM is open source. Eventually, after testing and fixing it can make it to officially supported status. And there's no way to manually flash an unsupported recovery in RM. You'd need to use joeykrim's Flash Image app (if your device is supported)or use fastboot to flash it.

      Why are you even talking about ROM Manager when you haven't used it in what seems like a couple years? Your experiences from then are completely baseless for it now.

  14. Re:Lies by Anonymous Coward · · Score: 0

    They did release honeycomb as part of the release of ICS. they just didn't include the version branch tags, so you can't tell exactly where 3.x.y was, but the entire source code for honeycomb is in the public repo now

  15. Motorola Droid3 by csumpi · · Score: 2

    It exists. Motorola Droid3 -> http://www.motorola.com/Consumers/US-EN/Consumer-Product-and-Services/Mobile-Phones/DROID-3-by-MOTOROLA-US-EN

    The keyboard is amazing. The phone is awesome (even the actual phone part, as in I can hear the other person and the other person can hear me). Dual core processor, very nice screen.

    One click rooted, removed motorola/verizon crap, can't be happier.

  16. Re:Lies by Alex+Zepeda · · Score: 1

    Well that's easy: no version of Android is really open source.

    Call me when the rest of the Open Handset Alliance releases source for their bits. Oh. Right. They don't. Qualcomm, Broadcom I'm looking at you and all of your infernal binary blobs. Is Android 4.0 open source? Kinda. I won't hold my breath for Google to release code for "older" ARM chips (v6 chips like the Qualcomm MSM7k series). Christ. Is Davlik still deliberately broken on OSX? Or maybe Google will ACCEPT SOME OF THE LONG STANDING FIXES for various ancient bugs in the core Android framework (which can't be fixed by developers without reimplementing the whole class... thanks for making such extensive use of private classes in your tab widget bits, Google).

    --
    The revolution will be mocked
  17. Re:Lies by gl4ss · · Score: 1

    is google wallet open source too? did they use just open source drivers?

    because call me skeptic but...

    --
    world was created 5 seconds before this post as it is.
  18. Radio drivers by thecross · · Score: 1

    Are there any LTE-enabled phones which support Cyanogenmod?

  19. Re:Lies by Rennt · · Score: 2

    If you honestly can't tell the difference between the ASOP (open source), Google Apps (closed source), and the devices based on them (spectrum runs from Free through Tainted to Overtly Hostile), then hand in your geek card.

  20. Not open enough by Richard_J_N · · Score: 4, Interesting

    I bought one: it was a wonderful device (except for the touchscreen being resistive), but what killed it for us was that it had critical parts of the GUI being non-open.
    We would have deployed 200 of them, but we needed one minor bugfix: the ability to operate the camera during a voip phone call (which meant being able to disable the shutter sound so as to allow the sound-card not to block). Sadly, the camera library was crippled: it's very, very easy to use Hildon (basically GTK) to access the image capture with gstreamer, but we only if we didn't use the proprietary feature called "auto-focus"! So we couldn't fix it ourselves, and when we reported the bug, the Nokia team confirmed it, but didn't actually get round to fixing it (at least, not within many weeks).

    It's a real shame too: I could SSH into the phone, launch X-applications (on either $DISPLAY), install applications with a real package manager, and enjoy all the other Linux goodness.

  21. Re:You mean Droid 1? Re:droid3 by bemymonkey · · Score: 1

    It's the RAM. Overclock that CPU to 800 or 1000MHz and it flies, but the 256MB of RAM is a huge bottleneck. I'm currently running a Desire which is an order of magnitude faster in daily use (used to have a Milestone) because it has 512MB of RAM, but even that's still a pretty big bottleneck. Here's to hoping that the standard 1GB on current models will be enough to keep Android running smoothly for the next two years or so...

    I wonder when the first Android devices with upgradeable RAM will start to appear ;)

  22. No, mobiles are the new PC... by Anonymous Coward · · Score: 0

    It doesn't need to appeal to middle-aged paunch. It needs to appeal to hungry, young exploration.

    People once ridiculed us for wanting a Unix-like environment on the PC, instead of using a "real" computer (either some over-priced Unix workstation or a PC with MS Windows, depending on who was doing the ridiculing). We burned the midnight oil, brought it into the workforce, and now variations of Linux-based PCs are the main form of real computer used in most datacenters and even many supercomputers. Back then, we needed affordable, personal hardware to support our studies and hacking. More recently, SOHO routers like the Linksys WRT54G seemed like an amazingly cheap platform for hacking, but they lacked the crucial human-computer interface devices to support independent learning... you still need PC equipment and skills to work with these headless devices.

    Today, netbooks, tablets, and smartphones are the most comparable platform to our old PCs, affordable and personal, with clear commodity growth trajectories and a viable human-computer interface (plus desktop-oriented options with HDMI and bluetooth). My cheap PC in college ran Linux, including X Windows, Emacs, GCC, and other development-related tools, sufficient to do programming lessons and to use as a terminal to the great information resources on the 90s Internet (USENET, gopher, email lists, and eventually NCSA Mosaic). A modern smartphone with 1+ GHz multi-core ARM CPU, 512+ MB RAM, and many GB of flash is more than adequate to support programming studies and to act as a terminal to the modern Internet's information resources. And the used device market should allow hackers to have multiple such devices without blowing their budget.

    Perhaps we owe it to the next generation to break this platform wide open and give them the tools to learn and to make something great, much as an older generation was laying the foundation for our Linux PCs when we were still too green to actually pull it all off ourselves.

  23. ROM Manager by Anonymous Coward · · Score: 0

    Come on, ROM Manager IS bloatware, advertising its paid version. Completely useless as one could point to flashable image when in recovery mode.

  24. That's the joke. by reluctantjoiner · · Score: 4, Informative

    Roald Dahl wasn't above pun-ishing his readers on occasion.

  25. Re:Lies by Anonymous Coward · · Score: 0

    The source is open you dumb fuck.

    It's not run in an open manner but that's their prerogative.

  26. Linus says Google has complied with the GPL. by Medievalist · · Score: 1

    Android is GPL. You can't change the license on the Linux kernel without permission, and it has never been released under any other license. There is lots of cruft layered on top of the OS that has other licensing, but the OS is GPLed.

    Google has released source code for every version of Android that they've shipped, to the people that they shipped to (typically vendors, not users) as required by the GPL. Google is not required to post sources on slashdot, as some people seem to think, and Google is not required to give you source code for devices somebody other than Google distributed.

    1. Re:Linus says Google has complied with the GPL. by AmbushBug · · Score: 2

      "Android is GPL" is flat out wrong. Only the linux kernel and a few bits are GPL. The bulk of the code is Apache licensed. You're being disingenuous by dismissing the most interesting parts of the Android system as "cruft layered on top".

    2. Re:Linus says Google has complied with the GPL. by Medievalist · · Score: 1

      "Android is GPL" is flat out wrong. Only the linux kernel and a few bits are GPL. The bulk of the code is Apache licensed. You're being disingenuous by dismissing the most interesting parts of the Android system as "cruft layered on top".

      Or perhaps we have different interests - I don't find anything outside android's kernel particularly interesting. Does that make me a bad person?

      Hmmm, OK, Dalvik is actually interesting, even though it involves Java (which is extremely boring). Point to you.

      Nonetheless Google hasn't violated either the GPL or the Apache license, AFAIK. They've given out source to everyone they've given executables, haven't they? Where's the beef?

  27. Re:Lies by Anonymous Coward · · Score: 0

    Yes, clearly no version, except for EVERY version is open source. The source is open and readily available under a very generous license. Unless you are an idiot, it is impossible to call Android non-open source. Yes, some specific hardware drivers are not open source but those parts are not android.

    No matter how you slice it, unless you are mentally defective, Android absolutely is open source is EVERY way in which it is commonly used and defined and likely in every lessor common use.

    Just because you stand up and say something idiotic doesn't suddenly make it true. Rather, it just means you're an idiot.

  28. Re:Lies by Anonymous Coward · · Score: 0

    And if you don't know the difference between ASOP and AOSP may be you should hand in your geek card :-)

  29. Re:Lies by exomondo · · Score: 1

    Well that's easy: no version of Android is really open source.

    Of course they are, they fit the very definition of open source.

    Call me when the rest of the Open Handset Alliance releases source for their bits. Oh. Right. They don't. Qualcomm, Broadcom I'm looking at you and all of your infernal binary blobs.

    None of those are part of Android, your statement is as moronic as saying Linux isn't open source because nVidia provide binary blobs for their graphics cards.

    Is Davlik still deliberately broken on OSX? Or maybe Google will ACCEPT SOME OF THE LONG STANDING FIXES for various ancient bugs in the core Android framework (which can't be fixed by developers without reimplementing the whole class... thanks for making such extensive use of private classes in your tab widget bits, Google).

    Again, nothing to do with Android being open source.