I doubt that there's much involved in running android on an A1 considering that there is already an x86 VM of Android... http://code.google.com/p/live-android/ ** this should run OK on any existing x86 netbook such as the current A1's.
It seems likely to me that this move is simply to replace Acer's version of linux "linpus" with something bigger. Linpus sucks anyways, its a severely crippled version of Fedora (which actually is top notch when not crippled). On Jul 9, 3:46 pm, DM <[email protected]> wrote: > I wonder how this affects the announced upcoming Acer Aspire One > Android-based netbook that we're all waiting to see in Q3 of this > year. (http://www.reuters.com/article/marketsNews/idUSTP18980620090602 > ). Will it become vaporware? Will Google lobby them to strongly > consider Chrome OS? I can imagine the Android model is already in the > works, so we'll likely see just that one. But this news does affect > the future of such endeavors. Why shoehorn a mobile OS into a netbook > when there's already a "better" free Google OS designed specifically > for the platform? > > As a new Android programmer, I was hoping for some fun on netbooks > too. Bummer. > > -- > Dennis > > On Jul 9, 11:50 am, Eric F <[email protected]> wrote: > > > Has anybody seen an "Android netbook" before.. Really. Like beyond a > > launcher screen with some shortcuts that are incredibly spaced apart > > from each other (which shows that they didn't even modify the source > > code to support the higher resolution at all). I think a few people > > with netbooks with ARM processors booted up Android on them, because > > it was easy, just to get a little extra press because there are > > basically zero Android devices out there so anything shown running it > > immediately gets some buzz. > > > I, personally, was never excited about the prospect about Android on a > > netbook. I don't think mobile phones and netbooks are in the same > > class at all. On a mobile phone, you want to conserve battery life, > > and make your application work on limited screen real estate. Those > > are the big challenges. Then the big functional advantage is the > > always with the person aspect, notify someone that they got an email, > > even though the screen is off and they aren't looking at the device. > > These are the defining characteristics and they aren't shared at all > > with netbooks. > > > Now, I don't know what ChromeOS will bring to the table (sounds more > > like a new Linux distro with all the features that are not a web > > browser removed at this point). But while it could amaze me when we > > actually see it, somehow I doubt it. However I think the big news here > > is that it runs on ARM. And it has Chrome. Which, to me, if Google is > > smart, means that Android will be getting some pieces of Chrome > > (mostly V8) soon. Given that web performance tests have not stacked up > > well against competitors like the Pre, and the iPhone, I think this is > > a good thing. Of course if Google were smart they wouldn't have > > launched on a flagship phone that had only 70MB of user space on the > > internal flash memory, no multi-touch on a capacitive display on the > > smallest telecom carrier in the US (you know, the one that didn't even > > have a pre-existing 3G network). So maybe we won't see any > > improvements trickle down to the Android browser, but I think we > > should cross our fingers. Unlike installing apps on SD card, allowing > > users to browse the web DOES seem to be on Google's agenda. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
