Yeah, so that basically means it will be a long while before Android is truly viable on the X86 platform. I would think most ppl who want to run Android on X86 are looking for more apps. But if most apps don't work, then it's no better off than the Windows app store. A little disappointing, but totally understandable.
By the same token, wouldn't the 500T which runs on Atom (ARM?) be more compatible theoretically? Why is it that dual booting to android is not even possible to do there?
Atom is also x86. In the case of the 500T its a clovertrail atom chip, which for some reason has had its UEFI module locked to windows 8 and as a result will only boot into windows 8, it just refuses everything else. The previous generation of atom chips and the next generation which are on the way do not have this limitation.
There is a 2nd variant of the clovertrail (and a 3rd too actually) which does the opposite. Its locked to android. But the android devices which are sold with clovertrail CPU's have a modded version of android which has an ARM emulator. ARM emulation is kinda slow but its better than the situation your in right now with not all apps working, its not 100% compatible either but still, better than not compatible at all. In the event that an app does have an x86 variant, this modded copy of android will run the x86 version for max performance as you would expect (although being atom its not on the same level as your core i5 systems). The samsung galaxy tab 3 is using one, motorola and ZTE also have clovertrail phones out.
Does mean though that if you bypassed the UEFI limitation, you could probably port a ROM from the galaxy tab 3 or something which does include the ARM emulator and run that on the 500t, there are a few other difference between the clovertrail variants than the UEFI thing but they should be more easily worked around.
I have seen discussions about bypassing the lockdown on windows clovertrail tablets, someone did make some progress towards getting it to boot linux I think but for some reason it just kernel panicked shortly after booting, there may be more to the lockdown than UEFI, or UEFI might not have been fully bypassed.
There is a bit of an increase in x86 devices sold now. So hopefully in future more developers who make use of native code will be supporting x86.
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
If you want to remove, you have to reinstall your windows from your recovery with your back up and combine your divided partition. Because android installation divides your sdd in 2seperated partition and you can not combine it without formatting which meaning removing your existing windows.
So make a full back up, create usb boot and install.
There is another way of installing android to our windows machine. It is an emulator. I did not try but they say it is perfect. Here is the link.
http://www.socketeq.com/
Wrong. You can remove the android partition and then expand an already formatted partition WITHOUT FORMATTING AGAIN to restore windows. But it is easy to go wrong.
There are actually quite a few android "emulators" out there, but emulator is not actually the correct term. They actually just port the dalvik virtual machine and standard library to run on windows instead of linux. Android in a pinch is just the dalvik virtual machine running on linux, there isn't a whole lot more to it than that, its only the NDK which gets complicated in that regard (which consequently is where alot of these android "emulators" trip up)