31–40 of 47 posts
"ASUS Eee PCs/Laptops"
This reminded me that I have a 5 year old Eee laptop that I haven't used in years and throwing Android on there could be a fun weekend-afternoon project.
If this is what you want - Android on your PC, you might as well use Genymotion ( https://www.genymotion.com/ ) - essentially a well packaged version that uses VirtualBox. Free for non-commercial use, $100/year for commercial use. Have new OS versions fast and easy to install Google apps/services on.
Genymotion's free edition has too many limitations. It's not just free for non-commercial usage. Some examples are: multi-touch and accelerometer, which are not supported in the free edition. Comparison can be found here: https://www.genymotion.com/#!/store
Doesn't Android itself support x86? There are phones [1] and tablets [2] base on Intel chips, after all, and they run Android. [1] http://www.intel.com/content/www/us/en/smartphones/smartphon... [2] http://www.intel.com/content/www/us/en/tablets/shop-tablets....
Perhaps Android in a VM will replace wine for running unported stuff on a Linux desktop.
If only Google considered Android for its desktop OS. It could be something like this (or better, if they are actually serious about it): http://www.jide.com/en/remixos But as long as Google and now Sundar Pichai consider ChromeOS to be the one and only Google desktop OS ever, unfortunately that won't happen. Of course such a desktop OS would also have to be more like Android Wear than "AOSP" - as in only Google woul…
I suspect Google actually wants Android to be more like Chrome OS. But they know Android's too important and popular to risk by outright replacing it with Chrome OS. That's why they are slowing mixing them together.
Chrome on Android is now integrated in the taskbar while they are pushing things like Web Manifests, Web Workers and Web Push Notifications. On the other hand it is now possible to run Android apps on Chrome OS via App Runtime for Chrome (ARC).
Doesn't Android itself support x86? There are phones [1] and tablets [2] base on Intel chips, after all, and they run Android. [1] http://www.intel.com/content/www/us/en/smartphones/smartphon... [2] http://www.intel.com/content/www/us/en/tablets/shop-tablets....
They used to have an FAQ which acknowledged the unofficial Android-x86 project: https://web.archive.org/web/20140331192152/https://01.org/an...
If you are one of those die-hard Linux fans who, like me, have been eagerly expecting each new Linux video driver release from AMD and/or nVidia, to be able to finally show our employer and everyone else that we can use Linux as our main machine, then these times are like living in a dream. (I don't really care that this Linux is labelled "Android" and has a Java "GUI", and I like many of the design decisions, e.g. f…
So they are still working on 4.4.3. I assume this is a daunting task, but are they always playing catch up? I do not say that dismissively. It is mind-blowing to me that they can port this to x86 (whether or not the toolchain supports it at this stage) and iron everything out with every major and minor release. I see no mention of Lollipop or Marshmallow, but I am really curious.
http://www.android-x86.org/releases/releasenote-4-4-r3
> The 4.4-r3 release is based on the Android 4.4.4_r2.0.1 (KTU84Q) release.
Their "What is new?" section on the front page says development on the Lollipop branch had started by 2014-11-06 (just two days after Google released the source) and that lollipop-x86 was updated to 5.1 on 2015-03-18.
I'm guessing part of the reason there isn't a stable Lollipop build yet is the switch from Dalvik to ART.
If you are one of those die-hard Linux fans who, like me, have been eagerly expecting each new Linux video driver release from AMD and/or nVidia, to be able to finally show our employer and everyone else that we can use Linux as our main machine, then these times are like living in a dream. (I don't really care that this Linux is labelled "Android" and has a Java "GUI", and I like many of the design decisions, e.g. f…
Personally, I've been scratching my head for a while at why Google is so dead-set on their "Chromebook" idea when they would have a great chance at killing off Microsoft for good if they put in some effort to create a great desktop version of Android.
As a Linux fan I prefer they stick to ChromeOS. It's just a custom Gentoo. Many of their devices support Coreboot, which makes them excellent machines to run my favorite Linux distro.
Doesn't Android itself support x86? There are phones [1] and tablets [2] base on Intel chips, after all, and they run Android. [1] http://www.intel.com/content/www/us/en/smartphones/smartphon... [2] http://www.intel.com/content/www/us/en/tablets/shop-tablets....