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."
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.
... 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.
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
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.
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.
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.
... 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!
:-) 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.
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
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?
My work here is dung.
Actually Qualcomm wants them to be called "smartbooks".
http://www.nordichardware.com/news,9392.html
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.
Cm'on, their motto is "do no evil".
What can go wrong?
factor 966971: 966971
Does it run windows?
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.
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.
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).
Sparks:Gadget:Beer Maker
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.
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. ... On the Palm that uptime came from 3 or 4 AAA cells btw - but that's another story.
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.
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
I don't think the phrase "boy-toy" means what you think it means.
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.
All about me
So when can I get my snapdragon powered mini-itx motherboard? It would make an ideal media centre.