Slashdot Mirror


Qualcomm Demos Eee PC Running Android OS

angry tapir writes "Qualcomm has showed off a version of Asustek Computer's Eee PC based on its Snapdragon processor at the Computex exhibition, including one running Google's Android operating system. The new laptop — which Qualcomm calls a smartbook — is thinner and lighter than current members of Asustek's Eee PC netbook lineup because the 1GHz Snapdragon processor that it uses does not require a heat sink or a cooling fan."

37 of 125 comments (clear)

  1. Because Snapdragon Is an ARM Processor! by eldavojohn · · Score: 5, Insightful

    The new laptop -- which Qualcomm calls a smartbook -- is thinner and lighter than current members of Asustek's Eee PC netbook lineup because the 1GHz Snapdragon processor that it uses does not require a heat sink or a cooling fan.

    Yes, of course, because of an important point in the article:

    Qualcomm's Snapdragon includes a 1GHz Arm processor core, a 600MHz digital-signal processor and hardware video codecs. Currently, Asustek's Eee PC line of netbooks relies on Intel processors, in particular the low-cost, low-power Atom chip, which has an x86 processor core.

    Which makes complete sense, because of its low power consumption you're going to see less heat and longer battery life (why do you think OLPC moved to it). And for those of you skeptical of the speed:

    When the first Snapdragon-based devices hit the market later this year, they will have a 1GHz Arm processor core but that will increase to 1.3GHz next year, with the release of Qualcomm's Snapdragon 8650A, Pineda said.

    Every single eee PC available (with Atom processors) on the market is x86, to my knowledge.

    This headline really got my hopes up as I just bout an eee PC 1000HE last weekend and have it dual booting to Windows XP & Easy Peasy Ubuntu. I love it. It's totally replaced my 5 year old laptop. I was hoping this meant I could partition out some space for Android but it looks like I'm left to emulating it (pretty much not an option considering the overhead). Maybe Google just doesn't see a point of porting Android to x86 since it's probably pretty dependent on the power efficiency of ARM?

    Pare away the heat sink and all that junk, add super small RAM and flash storage and ... hand held computers (like the article notes from Toshiba). Microsoft better not be resting on its laurels and should either be beefing up Windows Mobile or porting Windows 7 to ARM ... or they're going to miss out big time again.

    Has anyone found anything on how Android applications dependent on cell phone-ish hardware (like GPS location and the like) will be handled inside a device like the eee PC?

    --
    My work here is dung.
    1. Re:Because Snapdragon Is an ARM Processor! by notarockstar1979 · · Score: 2, Insightful

      You're missing the point. This isn't so that you can run Android apps, it's showing off a piece of hardware. The OS is beside the point (although I think Android is a good choice to show off the processor but that's more of a personal preference).

    2. Re:Because Snapdragon Is an ARM Processor! by sznupi · · Score: 2, Informative

      That's still order of magnitude more than ARM.

      --
      One that hath name thou can not otter
    3. Re:Because Snapdragon Is an ARM Processor! by Vu1turEMaN · · Score: 2, Insightful

      Its easier for Microsoft to just buy a company that has an ARM-compatible OS then to actually develop one. Just throw an XP theme on it and everyone will start using it like MS was saving this for the right moment.

      "Skinning is easier than Winning" - someone on the winamp forums complaining about no new features being added in a while

    4. Re:Because Snapdragon Is an ARM Processor! by Anonymous Coward · · Score: 3, Interesting

      No, that's not the important point at all...at least not the most important point.

      1. Android is "free" (unlike XP or Vista or Windows 7 or even Ubuntu on ARM)
      2. ARM is considerably cheaper than Intel processors
      3. Longer battery life from power consumption benefits (obviously a nice bonus but the big guns are going for a cheaper way to make netbooks)

      I work for one of the companies that is making software for these new devices and Asus is going to bring out netbook based devices as well. Oh there is Android for x86 as well (again cost cutting measures) but whether that comes out for the public remains to be seen. I've installed and used Android on several netbooks and this is old news.

    5. Re:Because Snapdragon Is an ARM Processor! by Hal_Porter · · Score: 5, Informative

      Pare away the heat sink and all that junk, add super small RAM and flash storage and ... hand held computers (like the article notes from Toshiba). Microsoft better not be resting on its laurels and should either be beefing up Windows Mobile or porting Windows 7 to ARM ... or they're going to miss out big time again.

      People keep saying this sort of thing, but I really don't see it being viable. A Snapdragon is probably going to end up being at best the same speed as an Atom for native code. Windows 7 is probably quite portable and from the tests I've done on the Beta on Atoms might run quite okish on an 1Ghz Snapdragon if it were ported. Even there we're talking about a 1Ghz in order core with a memory controller designed for cellphone SDRAM. High performance desktop memory is really different to the stuff used in cellphones - the buses are narrower and slower. Here's are the details for an Atom

      http://processorfinder.intel.com/details.aspx?sSpec=SLB73

      Note the bus speed, 533Mhz and the cache size, 512KB. By desktop standards the Atom is slow. Most Arm systems run memory much slower than this and have less cache. Look at the Snapdragon based Toshiba L01

      http://pdadb.net/index.php?m=specs&id=1855&view=1&c=toshiba_l01

      It uses "mobile DDR SDRAM". I don't know the clock speed, but look at this

      http://www.eetasia.com/ART_8800457078_499486_NP_197bb814.HTM
      Hynix claims 'fastest' 512Mbit mobile DDR SDRAM with a 185Mhz clock speed.

      See the thing is that the sort of memory you get in a cellphone is a lot slower than the stuff you get in a desktop because the power budget is so much less. If you want to run desktop applications or emulate an x86 that will really bite you.

      Once you get past the OS it gets worse. Office is probably less portable than Windows and Office 200x runs terribly on an Atom and would be worse on Snapdragon given the lower performance memory. Most Windows applications will not be ported and will run even worse in emulation - a Snapdragon emulating x86 will be unusably slow.

      Of course maybe ARM will do a Jazelle style extension where common x86 instructions are turned into ARM ones via an extra pipeline stage. I think that would mean a Snapdragon chip would run x86 code say 90% as fast as an Atom at the same clockspeed. Still a 1Ghz Atom is not a quick chip.

      --
      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;
    6. Re:Because Snapdragon Is an ARM Processor! by pseudonomous · · Score: 3, Interesting

      Microsoft already has Operating Systems that will run on the Arm architecture, Windows Mobile / WinCE, but I don't see what benefit you would get from using them, both taking your suggestion or using Windows Mobile would still leave an operating system that might look vaguely familiar, but still doesn't act quite like users would expect, that doesn't run much in the terms of familiar applications. I would think that, like with the Linux-based acer and msi netbooks, you would get a very high return rate on something like this.

    7. Re:Because Snapdragon Is an ARM Processor! by Tenebrousedge · · Score: 2, Interesting

      Every single eee PC available (with Atom processors) on the market is x86, to my knowledge.

      That is correct, but I can't imagine why it's relevant. Did you mean to distinguish them from x86-64 or IA64? Or are you saying that all Atom-powered Eee's are not powered by ARM processors? That seems to be a vacuous truth.

      And for those of you skeptical of the speed:

      When the first Snapdragon-based devices hit the market later this year, they will have a 1GHz Arm processor core but that will increase to 1.3GHz next year, with the release of Qualcomm's Snapdragon 8650A, Pineda said.

      If the Netburst architecture taught us anything, it was that clock speed isn't everything.

      Has anyone found anything on how Android applications dependent on cell phone-ish hardware (like GPS location and the like) will be handled inside a device like the eee PC?

      Why would this would be any different than how it's handled in any other linux-based OS?

      You seem excited by the thought of a handheld computer. I have to ask, why do you want one? I don't think there's any market for them. We've had PDAs and many other more specialized handheld devices before, and there is certainly a niche for the 'smartphone' class of devices, but what would be the point of a general-purpose computer smaller than an Eee? Touchscreen or no, anything with a keyboard smaller than about seven inches is useful for SMS-length messages only. So unless you're going to invent a radically new method of user input, the market is already segmented based on that design decision. We either already have what you're talking about as far as a 'handheld computer', or it's not likely to happen.

      --
      Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
    8. Re:Because Snapdragon Is an ARM Processor! by Taxman415a · · Score: 4, Insightful

      See the thing is that the sort of memory you get in a cellphone is a lot slower than the stuff you get in a desktop because the power budget is so much less. If you want to run desktop applications or emulate an x86 that will really bite you.

      All interesting information you added, but for a netbook platform where the battery is an order of magnitude larger than a cellphone, what makes you think they can't put in a different memory controller with a wider bus to run regular sodimms? You'd still get all the power savings from the lower power chip and no active cooling, but without the performance hit you refer to.

    9. Re:Because Snapdragon Is an ARM Processor! by Bert64 · · Score: 3, Interesting

      The problem with windows ce/mobile is that it's advertised as being windows when it really isn't.. This creates the expectation of compatibility with desktop windows. The mobile versions of windows however are not compatible at all, either at the binary or source level (and most apps don't even come with source), such that there are very few available apps...
      An arm version of linux on the other hand really is linux, and has 99% of the same applications available for it, since in most cases it's just a case of a recompile.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    10. Re:Because Snapdragon Is an ARM Processor! by Locutus · · Score: 3, Interesting

      you do not know Microsoft. They live and breath by Windows and the Windows APIs and that product is why they still exist. It would be a very small fraction of todays company that would promote the use of another OS instead of Windows. The Windows OS brings in most of their profits and the extents they go to protect that marketshare should be an indicator of how tied to it they are.
       

      You'll see them making offers companies can't refuse and dumping billions into stopping the move to Linux before you'll see an MS Linux. They'll push Windows Mobile onto this platform or even port XP to ARM before there's an MS Linux or any MS nonWindows OS. IMO.
       

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    11. Re:Because Snapdragon Is an ARM Processor! by Bert64 · · Score: 2, Interesting

      This is why Linux really stands to benefit...
      Even if windows were ported to arm, all of the applications would still need to be ported by their respective vendors, many of which wouldn't bother, or would release a castrated "mobile" version instead..

      Most commercial vendors won't port to a platform unless there is a sufficient market for it, and most customers won't buy a product unless there is already sufficient software availability.. A catch 22 that's already killed Itanium.

      Linux on the other hand, is already ported to arm, and most of the applications you would use on a typical linux desktop are also already ported... And any new open source applications being written would be trivially portable between various different processors too.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    12. Re:Because Snapdragon Is an ARM Processor! by horza · · Score: 4, Informative

      ARM + chipset runs at 0.5 watts, according to this CNET article from last June.

      Phillip.

    13. Re:Because Snapdragon Is an ARM Processor! by horza · · Score: 2, Insightful

      Why would you want to hobble an ARM processor by trying to run x86 cruft on it? A 1GHz ARM processor will blow away an equivalent x86 when running apps natively. If I was running desktop apps on a netbook I wouldn't even want something as heavy as OpenOffice, let alone a monolith like MS Office, I would want something like Abiword but with the OO import/export filters. As bert64 says, there is a wealth of Linux apps, and with Ubuntu netbook-friendly version coming you can bet their repository will fill quickly with ARM versions of all the apps.

      Phillip.

    14. Re:Because Snapdragon Is an ARM Processor! by Thumper_SVX · · Score: 2, Interesting

      I can tell you that my BeagleBoard setup runs phenomenally fast on a 500/600Mhz ARM chip and 256MB of RAM. It's more than acceptable for 99.9% of all the apps I've thrown at it... be it basic web browsing, or even more complex stuff like GPS. It's silent, it's slick... and in fact the only weak point in my opinion is its reliance on SD cards for storage since they're SLOW. However, given its interfaces there's no reason you couldn't build something to interface to SATA or at least mini IDE interfaces... and the USB bus is at least 2.0.

      Still, I can definitely see this going places. I bought the BeagleBoard to play with and it ended up becoming an actual usable system on my network. I am thinking of buying another one and building a car PC out of it :)

    15. Re:Because Snapdragon Is an ARM Processor! by sznupi · · Score: 2, Informative

      One would think you would at least check wattage drain of ARM SoCs before comparing them to some x86...

      And those Snapdragons are actually relatively power-hungry...for an ARM! (comparable to Geode LX in performance would be 0.1 W probably, perhaps 0.2)

      --
      One that hath name thou can not otter
    16. Re:Because Snapdragon Is an ARM Processor! by Hal_Porter · · Score: 2, Interesting

      As far as I can tell they didn't do that with Snapdragon. It's a fast chip by Arm standards, but the memory subsystem is very similar to their previous chips. Then again that's probably because they're interested in selling chips for cellphones rather than notebooks.

      Now Snapdragon is great for the cellphones but and I don't see why they should start to build chips for the netbook market where Arm is competing at a massive disadvantage.

      The problem is a 2+Ghz, possibly out of order, Arm chip with fast busses, big caches (which means no space for onboard peripherals) and so on would not be very good for the cellphone market. Also chip development costs a fortune - Qualcomm spent tens of millions on a custom Arm implementation

      http://www.insidedsp.com/Articles/tabid/64/articleType/ArticleView/articleId/238/Qualcomm-Reveals-Details-on-Scorpion-Core.aspx

      Overall, Qualcomm has made a huge investment in creating a custom implementation of the ARMv7 architecture. By way of comparison, Texas Instruments customized just the layout for the Cortex-A8 for its OMAP3 chips, and it has been reported that the process took 45 engineers working for a period of years. If so, Scorpion's development probably represents an investment on the order of tens of millions of dollars. And what's the payoff?

      At first glance, it doesn't look like much-as noted earlier, Scorpion is expected to run at 1 GHz in a 65 nm process, which is slightly lower than the 1.1 GHz top speed that ARM currently quotes for the Cortex-A8 in 65 nm. Scorpion is quoted as providing 2100 DMIPS at 1 GHz; Cortex-A8 is quoted at 2000 DMIPS at the same speed. However, a notable difference is that the Cortex-A8 top speed is for a TSMC GP (general-purpose) process, while the Scorpion speed is for the LP (low-power) process. ARM quotes the speed of Cortex-A8 in an LP process as roughly 650 MHz, and although TI does not publicize the exact speed of the hand-crafted, low-power Cortex-A8 core used in its OMAP3 chips, BDTI has estimated that it runs at roughly 450 MHz. (BDTI's benchmark results for the Cortex-A8 are available at BDTIâ(TM)s website, www.BDTI.com.) Thus, Qualcomm expects Scorpion to run significantly faster than Cortex-A8 when both are implemented in the low-power processes commonly used for mobile applications.

      Building an Arm that could compete with x86 would cost even more, they're up against Intel, AMD and Via all of whom already have faster chips and such a chip would not be very popular in the cellphone market. Actually the cellphone market is probably bigger than the desktop x86 market and Snapdragon is the top performer or close to it.

      In some ways it reminds me of PowerPC. Apple ditched the architecture because the main PPC vendors wanted to concentrate on designing for the embedded world where they were selling in huge volumes to the detriment of the desktop world where Apple wanted to operate but where the volumes were tiny,

      --
      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;
    17. Re:Because Snapdragon Is an ARM Processor! by Daengbo · · Score: 2, Interesting

      "Frankly speaking, the first question, I would like to apologize that, if you look at Asus booth we've decided not to display this product," he said. "I think you may have seen the devices on Qualcomm's booth but actually, I think this is a company decision so far we would not like to show this device. That's what I can tell you so far. I would like to apologize for that." -- http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9133813

      Asus didn't actually want to show off the hardware, though, which I think is a strange thing indeed since the tech industry seems quite excited about the product and it looked ready to ship.

      When asked about rumors that Asustek faced pressure from Microsoft and Intel over the use of Android and Snapdragon in the Eee PC, Tsang said "no, pressure, none."

      Intel spokesman Nick Jacobs said, "our customers are always free to make the choices they want," and declined further comment on "rumors and speculation."

      Unless, of course, you are a netbook manufacturer which wants to put a dual-core Atom in your product. Intel has promised to "penalize" manufacturers that do that.

      Obviously, I don't believe a thing coming out of their mouths.

  2. That's great, but... by DomNF15 · · Score: 2, Insightful

    I am less concerned with the OS than with the increased battery life/less weight in a device like this. As long as the OS supports mobile broadband cards from the major wireless carriers and some basic apps like web browsing and an office suite, I'd be happy.

    1. Re:That's great, but... by Locutus · · Score: 4, Interesting

      there should be no need for supporting "mobile broadband cards" with the universal 3G radio built into the Smartbooks. Unless they are misusing the term universal. The only difference between a netbook and a Smartbook is that the Smartbooks have the 3G radio builtin and the software to use it.

      I think Qualcomm has a hit here.

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
    2. Re:That's great, but... by Thumper_SVX · · Score: 3, Informative

      But Qualcomm's Gobi chipset purportedly supports EV-DO and HSPA in a single chipset, thus it's at least technically possible that they have done exactly as they say. It even includes GPS... so long as you have room for all the antennae (dead space behind the screen for example) then it should be a non-issue to make it into a truly "multi-radio" machine.

      Hmm... wonder if Apple's been talking to Qualcomm for the next gen iPhone... ;)

  3. Overhead by eldavojohn · · Score: 2, Interesting

    Why port Android to x86 when you can just run Android apps in Ubuntu?

    Like I said in my post:

    but it looks like I'm left to emulating it (pretty much not an option considering the overhead).

    I tried doing this on a P4 with 2 gigs of DDR RAM a while ago in Ubuntu 8.04 if I recall correctly. It was slow as hell.

    I don't know if the SDK has since matured since then but I was trying to do their tutorial examples and I would experience really bad startup times ... like waiting minutes for everything to initialize. Sometimes it would bomb out before making it to the applications screen in the emulator. Maybe it was memory pagination? Anyway, I also assume the emulation stops you from efficiently using the hardware like the camera? Does the emulator have access to those? I could be wrong and I'll certainly give it a shot if I find reports of people online having no problem firing up Ubuntu on their eee PC and emulating Android and running an application on it no problem. As it stands, I'd probably just look for an alternative in Ubuntu to that application!

    Who knows? Maybe I'll sell this one and trade up when the new Snapdragons come out and I'll wean myself from the Microsoft teat entirely with only ARM Linux and applications? :-) I must guiltily admit that I kind of enjoy the dual boot though and am really just curious what Android would have to offer on a netbook.

    --
    My work here is dung.
    1. Re:Overhead by Sinning · · Score: 3, Interesting

      Sorry for the confusion, I was referring more to this.

      Rather than running the Android SDK emulator.

      It looks to be a much more promising alternative to emulating the entire android OS.

  4. Re:I still don't like netbooks by hattig · · Score: 2, Interesting

    Actually Qualcomm wants them to be called "smartbooks".

    http://www.nordichardware.com/news,9392.html

  5. Wait for Pandora by tepples · · Score: 4, Informative

    I ask for ARM UMPCs and get ARM netbooks.

    Is an "ARM UMPC" essentially a PDA with a keyboard? If so, then wait for Pandora to enter mass production.

    1. Re:Wait for Pandora by tchuladdiass · · Score: 2, Informative

      Or the Nokia n810, which you can get for $200 now. Or wait for the next gen tablet. Actually, the next Maemo device coming from Nokia is actually going to be a phone, not a tablet, but rummer has it that they are still planning more tablet models.

  6. Re:Keep an eye on google... by doti · · Score: 4, Funny

    Cm'on, their motto is "do no evil".
    What can go wrong?

    --
    factor 966971: 966971
  7. Yes, but obvious question... by dvh.tosomja · · Score: 3, Funny

    Does it run windows?

  8. Re:Like iPhone OS on iPod Touch, perhaps by PhilHibbs · · Score: 2, Interesting

    Navigation apps aren't directly dependent on the GPS hardware, they are dependent on the Location API which will still return a position based on cell tower triangulation. I can't comment on "and the like" as that's a bit of a broad question, but in general they will all be calling API functions that I guess will return a default or error value if the hardware doesn't support it.

  9. 'Asustek puts Android netbook on ice' by snydeq · · Score: 5, Informative

    Asustek appears to have already scuttled this project, calling the technology 'not mature' and disavowing any pressure from Microsoft and Intel over the use of Android and Snapdragon in the Eee PC.

    Of course, the Android-based Eee was demonstrated by Qualcomm, not Asustek. Yet, Asustek's distancing itself from the machine while competitors like Acer are announcing Android plans is a little bit intriguing.

    1. Re:'Asustek puts Android netbook on ice' by Locutus · · Score: 3, Interesting

      probably under contract with Microsoft. You know, the fine print that keeps showing up after 20 years of company lawyers being surprised by Microsoft's tactics. The funny thing about lawyers, each one thinks _they_ are smarter than the other lawyers and keep signing deals with Microsoft thinking they're getting away with something.
       

      It was obvious to me that they signed a deal with the devil when the next gen eEEPC's shipped. They used the 50/50 rule to say they ship 50% Linux systems and 50% Windows systems and that's why there were no Linux netbooks on store shelves. They boosted the hardware so Windows would run but then boosted the hardware more for the Linux versions and charged more for Linux. These are all signs of a "special" deal with Microsoft and they seem to be locked into this deal at the expense of the ARM systems. After all, if they can't ship Linux, how can they ship a viable ARM based system? So, ASUS can't play in this ARM netbook or Smartbook game and all they can do is try to put it down in an attempt to limit it's value and growth with marketing speak.
       

        So ASUS is out of the netbook/Smartbook game until their contract with Microsoft ends as far as I'm concerned. Windows is just not efficient enough to make a compelling small device OS.
       

      LoB

      --
      "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  10. How will current apps cope? by riflemann · · Score: 3, Insightful

    There are ~3500 android apps out there now, virtually every one of them written assuming HTC Dream hardware.

    It will be very interesting to see how they all cope when run on emerging hardware with vastly different characteristics and screens to the opening device.

    My own Android game is not exempt and will need better adaptability (yeah, hypocrite).

  11. Interesting, I suppose by bsDaemon · · Score: 2, Interesting

    I just bought an EeePC last Thursday because I wanted to see what all the fuss was about and because I determined that there was a niche to fill between my Toshiba (which is always hooked up to an external monitor, speakers, mouse, graphics tablet and all sorts of other things), and my BlackBerry Storm.I got it at best buy, and so of course all I really had for an option was Windows XP, and I'm not sure how it'd really do with Linux (I suppose if they've been selling Linux versions the hardware should all be compatible, but I spend enough time fussing with Linux on the servers at work to really want to do Linux of FreeBSD for a hobby anymore). I'm actually typing this on it now.

    I have yet to really play with Android, even though one of my coworkers has a G1, I just haven't really felt the urge to take it for a spin. The idea of having a "phone" OS on a "computer" seems a tad bit odd to me, but I suppose its just the opposite of the deal with the stripped-down OSX on the iPhone, which I have messed with a bit (I just don't feel like switching to AT&T or I'd probably pick one up... the only thing my Storm really has going for it is the tactile feedback to the depressible touch screen).

    Is there anything particularly special about Android over any other Linux distribution, other than the Google name, that makes it well suited for this type of application? From what I've read, it seems to be just a Linux kernel combined with Java phone crap and not really anything particularly special, though as I must admit, I've not really been following it too closely.

  12. I've only got one more point on my list unsolved by Qbertino · · Score: 3, Interesting

    As far as modern day handheld computers go, I have to say that the Asus EEE induced second coming of the Netbook and its liklings has had extremley positive side effects on the market in the last two years.

    Portability? Check.
    Openess and flexibility of plattform? Check.
    Price? Check.
    Versatility? Check.

    However, there is just one more thing I want before I can say they are on par with the mid-nineties PC handhelds that where available back then and could easyly keep up with their big desktop brothers in terms of getting the job done: Battery Uptime and/or easy replacement of battery.

    Let me explain: The HP 200LX, Sharp PC 3000, 3100 and its non-name rebrands ran on AA cells. And while the off-grid uptime was a meager 3,5 hours at max, you could easyly replace them with rechargeables or - in an emergency - with fresh AA cells from the next gas station or convenience store.
    I want that kind of battery time or convenience from todays handhelds aswell. If convenience is not an option, I want the same uptime I could get from my old Palm m105 with folding keyboard attached or from the original Psion Netbook: 40 hours. ... On the Palm that uptime came from 3 or 4 AAA cells btw - but that's another story.

    Substancially increased battery uptime without outlandish pricing - then handhelds are back in the game for me. It would be about time.

    My 2 cents.

    --
    We suffer more in our imagination than in reality. - Seneca
  13. Re:I want one! by Anonymous Coward · · Score: 2, Funny

    I don't think the phrase "boy-toy" means what you think it means.

  14. So let me get this straight... by ChaoticCoyote · · Score: 4, Insightful

    Android uses Linux, but isn't Linux (no standard libraries, for example).

    Android uses Java, but it isn't standard Java nor is it compatible with most Java apps.

    Android is open source, except for certain fiddly-bits they keep private.

    This is not the competition for Windows we've been looking for.

  15. I want it NOW! by Anonymous Coward · · Score: 2, Interesting

    So when can I get my snapdragon powered mini-itx motherboard? It would make an ideal media centre.