What is Reddit's opinion of
Android-x86?
From 3.5 billion Reddit comments
81 reviews of this app found across Reddit:
I actually didn't use an emulator, I used https://www.android-x86.org/
It's pretty easy, very easy to try it out, you just install it on a usb and then you can either try it without installing by running it off the usb or install it onto the SSD probably an sd card too I suppose.
I opted to shrink my windows installation on the SSD and install it alongside windows 10, so now whenever it boots I just decide if I'm booting into android or windows.
If you've ever booted a live cd of ubuntu or another linux distro it's basically that hard.
Incorrect. Unix is not used that much in servers anymore and majority of them use Linux. 96.3% of top 1 million servers use Linux. Linux is not based on Unix, it was developed independently but was inspired by Unix.
MacOS is kind of based on Unix but it's a long lineage. It has elements of BSD which is a variant of Unix. You can read the whole lineage here.
As for Android, it uses Linux kernel like you said and that is true for any Linux distribution. Software on top of that is what differentiates distributions. There is even a project to port Android to x86 systems (regular PCs).
While Android-x86's usefulness might be questionable, I'm not sure where you're getting that, "they strongly suggest only using it in VMs, not on hardware." There's a list of tested platforms on their website, and while they do have a page for VirtualBox installation, their installation page claims, "a text-based easy installer".
Hello, it is not a dumb question. Here is my stupid answer: yes.
Android is an end-to-end operating system, integrated tightly to the underlying hardware. It is not made to float in a VM, or to be installed on off-the-shelf hardware.
Alas, it is possible to use it in a virtualized system, thanks to the Android x86 project, but it is not streamlined. You may to have a look at Waydroid, which follows another, and perhaps more promising approach.
Ideally, Android, or more precisely, its parent project the Android Open Source Project (AOSP), would be built against the Q35 machine model that is uses by KVM/QEMU. But it is a lot of work as Android, by default, targets the ARM architecture.
If you're somewhat tech savy unlock the bios via mrchromebox firmware, remove Chrome OS directly and put Fyde OS(Chromium OS based, supports Android Container) or Android x86(AOSP based, real Android) in it.
Otherwise you'll not get it
Do... Do you know what the cloud is? That is not really what we're talking about here.
https://www.android-x86.org/download Android is free.
And sure, Oracle might change the licencing. Then someone will fork it and it will continue to be free.
I'll grant that there's not really any other free type-2, windows-compatible, FOSS hypervisors around. But that's because there's four qualifiers on that sentence. Between vbox, hyper-v, vmware workstation/player, and the wide swathe of type 1s, there just isn't really a need for one. I guess add containerisation into that conversation too.
Wenn Android-Smartphones einen Mainline-Kernel verwenden würden und vernünftige Software zum Updaten des Kernels hätten (bzw. ungelockten Bootloader), könnte die Community Updates bereitstellen. Alles eine Frage des Willens.
Wenn ein alter Prozessor nicht mehr mit einem neuen OS kompatibel ist (obwohl die Architektur (ARM) die selbe ist), dann ist das kein Software-Problem, sondern gewollt. Man kann Android auch auf PCs mit normalen Laptop/Desktop-Prozessoren installieren (https://www.android-x86.org/), obwohl diese CPUs nie dafür gemacht wurden, dieses Betriebssystem zu unterstützen.
You could try installing a port of android x86 (available here) and see if touchscreen works. I have tried installing the port myself and everything works fine (even Arcaea without weird lag issues as android emulators) but I can't confirm if the touchscreen will work since I never owned a touchscreen x86 device.
> on PC
https://www.android-x86.org/ assuming you're talking about an x86 CPU.
Honestly better off just using your Note 20 Ultra, frankly. Grab a Jumpgate and you're good to go.
So is there any way to like... emulate the amazon cloud drive android app on the synology?
It's not elegant, but I'm thinking, install something like this:
On a VM on the NAS, and then using Amazon's official clouddrive app
I'll put my money on Intel sp7/7+ given how many Android emulators are running fine today on Intel platforms.
https://alternativeto.net/software/bluestacks/
And
Hilarious actually how slow Microsoft is to add what the community has had for years and years. But lest one forgets, X out in 2019 and STILL HAS NO official x64-bit app support...
I am not talking about emulator. I am talking about android x86
The thing is I tried it before 2018. Back then it said under device name that it is pixel.
So there may be a hope.
Will try this weekend and share the result.
Years ago I used to run Android on a lot of PC's using
https://www.android-x86.org/installhowto.html
I'm sure there's a lot of other projects out there now like the one you found. My only concern would be the possibility of less security since it's not on the actual hardware the systems made for. Congratulations have fun and good luck ;)
It is only available on Android, unfortunately. If you really wanted to, you could run it by creating an Android x86 virtual machine using software such as VMware Player
A PC running Android-x86 or a Raspberry Pi running some version of Android could probably accomplish the "on tv" part. Wireless mouse (and keyboard if you want to chat), et voila.
A controller would be pretty hard to use unless it's something like the Steam Controller with touch input, and still it may be difficult/impossible to get it to work with the game without issue.
Want me to elaborate? Some people made a version of Android that you can run on your PC. But not many people would want that now, would they? So you can run it in a container, known as Virtual machine, and boot it inside that. It's just like a emulator in which you can run any operating system in a contained environment.
If you only need a device, but not all that fancy stuff the emulator can do, fire up a new VM using an Android X86 iso, then connect adb by network to it (adb connect 192.168.x.x).
Just follow the virtualbox guide and adapt to proxmox where needed https://www.android-x86.org/documentation/virtualbox.html
https://www.android-x86.org/installhowto.html
Follow this guide STEP BY STEP! and once done installing, run Android x86. After it starts up, setup as you would like a new phone and then go straight to settings, click on "Android x86 options" and hit "enable native bridge". Then you're good to go!
Install xcloud, sign in and play 😁!
There's the android x86_64 project which certainly could run on the surface. Would you want to run android on it? No, since android uses the linux kernel I know for a fact that the camera wouldn't work (it uses proprietary drivers that are only for windows) and the battery life would probably suck too.
If the OP reads this, don't buy it for the intend of running android on it.
A long time ago I stumbled on this website. They do the actual porting to make it work on x86/x64 cpus like Intel and amd.
It seems like the last Android they ported was 9, but they're working on porting over Android 10.
Site might look shady, but I actually tried it once... and was pleasantly surprised.
You can flash Bliss OS to a flash drive and boot your computer from there. You can also use Android x86 Project's original ISOs itself for that purpose, but Bliss OS is more designed for PC use.
Depending on your purpose, you can also use ARChon, a Chrome extension that lets you create an Android simulator on Chrome.
Check your .xsession-errors file and sudo dmesg for relevant error messages. Also Anbox is quite old and abandoned at this point. Check Redroid for proper Android in a Container setup, or directly run Android x86 or Bliss OS through virt-manager.
Redroid:
https://github.com/remote-android/redroid-doc
Android x86:
Bliss OS:
Yes, there actually is. I was kind of surprised to learn this.
Of course, you can also use an emulator, but this will run better, and if it's for your little brother Android-86x is probably simpler for him. Only upside I can see is easier installation.
> I wanted to try out Bedrock to see if it runs better on 1.18, but even using the new launcher, it costs 27 dollars to buy and run separately.
If it's worth spending $7.50 on the Android version, I play that on my laptop using Android x86. It can be installed on a bootable USB 3.0 flash drive, which is how I do it. It's not emulated, so it actually runs Android for Intel on your hardware. It's free, so make sure you try it out first to make sure it supports things like your network card.
I originally set it up that way as a novelty, but it's now how I actually play.
I'm not really experienced with this but Android x86 seems like what you want. Alternatively there is Android Studio which includes AVD Manager for running an Android emulator.
>would BlueStacks work via proton?
I don't think BlueStacks works via proton, but I didn't check. Feel free to try if you want.
>is there another software to use?
Like people said, anbox/waydroid might work (I'm not sure because last I cheked, they didn't translate arm apks. Though if you only want to use x86 apks, you're good to go for sure)
If you want an emulator, I'd suggest VirtualBox + Android-x86 https://www.android-x86.org/documentation/virtualbox.html
It also works on Windows.
People talk about anbox and waydroid, they only work for x86 android games. A lot of android games only have arm versions, so they don't work with anbox/waydroid. I don't know if it's the case for the games you want to play.
If you have games that don't have an x86 version, you can use a VM, just like NOX on Windows. I would recommend VirtualBox with the android-x86 iso. Here's a guide: https://www.android-x86.org/documentation/virtualbox.html
(btw I heard waydroid are planning to implement a way to run arm packages on x86 hardware, but I don't know how long it will take)
Android has alo x86 an x64 versions https://www.android-x86.org/ And as far as the samsung config you can use a whitelist and tell wich apps will be allowed in the background also . Not in to cout that in order to have real multitasking you need at leat 8GB ram on android 11 arm 64
Virtualbox with android-x86 is the closest you can get. Both things are open-source, with no ads, but you'll be missing a lot of features offered in bluestacks/memu, especially keymapping for games. There is also no hardware acceleration for graphics, and android versions above 8 have compatibility issues with virtualbox.
I'd suggest you explore this with folks who develop x86 Android (https://www.android-x86.org/documentation/virtualbox.html). Your setup is not supported officially by Virtual Box. Specifically, your Host OS, MacOS Big Sur, is not validated to run Virtual Box (last supported MacOS Host is Catalina). Similarly Android x86 releases have not been validated to run as Guest OS by Oracle.
you could use Windows 11's built-in emulator when it comes out, or Anbox on Linux, or you could install an emulator, like Android-x86 in Virtualbox/VMWare
>This was using VBoxSVGA.
Well, this would run contrary to the advice of the x86 Android devs, who state -
Mandatory: Unless guest additions are installed[1], change the default VMSVGA to VBoxVGA.
https://www.android-x86.org/documentation/virtualbox.html
>I was able to get it running flawlessly on windows 10 where I had access to the bios.
Well, I can't comment on how "flawlessly" you other VM setup was, but I'd note it was manifestly different from what you are doing now in that -
- You were using a different Host OS. - I'd note Virtual Box 6.0 predates the release of the latest Builds of Window 10 (21H1, etc.) , and may not have been never validated for operation in this manner either.
- You were using a different Guest OS. - There are significant differences in Virtual Box configuration from 32 and 64 bit OSs. 64 bit OS, generally speaking require I/O APIC to be enabled in Virtual Box while 32 bit OSs do not.
- You were running with VT-x / AMD-v / SVM enabled. - Without this, you are forcing Virtual Box to run in "compiler" mode, a mode which was dropped in later Virtual Box builds (i.e. 6.1.x).
Given these differences, I don't think you really come to any conclusions as to why your setup on Windows Server 2016 Host is not working as opposed to your Windows 10 Host. There are just two many variables that are different between the two setups for you to draw be able to draw any hard conclusions.
That being said, as you are running a Windows Host, if I had to speculate, your issue maybe that AMD-V / VT-x / SVM is enabled on your Windows Server 2016 system, along with Hyper-v. This can cause all kinds of random issues with Virtual Box. You can determine this for sure by checking the VM's vboc.log as previously stated.
Not really dead, Android-x86 is just very very niche so not many people. The last stable release was less than a month ago.
Auto installing is exactly what you don't want to do. You just said you want to dual boot but this is not for dual booting.
>If you want to use Android-x86 as the only OS in your device, you may choose "Auto Installation" under the "Advanced options".
>
>https://www.android-x86.org/installhowto.html
To dual boot you will want to select the "Install Android-x86 to harddisk" option then in the "Create/modify partitions", partition your main Windows partition and then format the new empty partition to ext4 and install onto that, and select yes when it asks you install the GRUB which will let you select the partition to boot into when you turn on the computer.
If you want to try your luck you can go the Android x86 route and just install android straight into the surface pro if you think it'd be worth it instead of using Dex. [ https://www.android-x86.org ] basically turn it into a better chromebook.
Giusto per completezza, ci sono una varietà di soluzioni per usare Android su CPU x86 (per un periodo ASUS faceva persino degli smartphone e dei tablet x86 con CPU Intel!)
Suppongo però tu stia parlando della distribuzione https://www.android-x86.org
Direi che sì, è sicura e tutto... Anche se non so in che condizioni sia, l'ho provata solo molti anni fa e farla andare era un po' un terno al lotto.
That's what I am trying to test. If you look at the release note , there's an option to enable support for arm (from the release note): "Support arm arch apps via the native bridge mechanism. (Settings -> Android-x86 options, 64-bit only)".
I haven't got time to test properly yet. Whenever I turn that option on , it turns off automatically, I think that's some of glitch right there, have to wait for the next update I guess.
Got a spare PC or laptop laying about with at least a dual core CPU, 2GB RAM and 8GB HDD?
You could install Android x86 and use Tasker on a larger display with keyboard and mouse abilities. It is also possible to run these in a Virtualbox or the like, depending on how powerful a PC you have.
If you do do this, be sure to enable App Compatibility (libhoudini) before installing Tasker.
I don’t know off hand, I did have to google through some boot/startup issues once I had the ISO started in VMware.
I am using Android X86 https://www.android-x86.org/releases/releasenote-9-0-r2.html
Running in free VMware... https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html
I actually haven’t been using Tinycam much lately. I had it on an old phone, then COVID...
It may be worth it to look into Android-x86 if it's an older or weaker PC
> Android-x86 is an unofficial initiative to port Google's Android mobile operating system to run on devices powered by Intel and AMD x86 processors, rather than RISC-based ARM chips. The project began as a series of patches to the Android source code to enable Android to run on various netbooks and ultra-mobile PCs, particularly the ASUS Eee PC.
The above is a description from DistroWatch
Here are some other links. Even if you don't decide to go that route it's still pretty neat.
https://www.howtogeek.com/howto/22665/run-android-on-your-netbook-or-desktop/
The one I downloaded is a LineageOS ISO but has the play store and other google apps which means it has Gapps and other google stuff included.
​
https://www.android-x86.org/releases/releasenote-cm-x86-14-1-r3.html
Even though it is not supported, it still works when you make it Linux/Other.
Make sure to select an x86 version of android, like this one: https://www.android-x86.org/
Range harga segitu kayaknya mending AMD sih. Kalo insist intel, Celeron juga udah cukup banget kalo ngeboot Android atau Linux. Harga laptop dan part computing sini melambung jauh sejak WFH.
Not sure about that but you can take a backup for your bluestacks and try, However i will suggest to install in virtual box and download an android version from Android-86.org.
lolthere are no moderators here, moderators are dead since 2 years they havent come. you could have given gift card in secret after someone solved your problem instead of trying to get attention, even if you gave a gift card or not people help you
contact android x86 developers
From what I recall the original Google team released their progress on x86 platforms under the open source licences, and these open source devs have picked it up and ran with it.
I've used it on a couple of old laptops and it works pretty well.
Yes I did download the ISO from https://www.android-x86.org/ and unfortunately it contains Google's services again.
Genymotion on the other hand looks very interesting. I have heard of it in the past but to this day every mention of it ever only told me that it is a cloud based Android virtualization solution. Which is a thing but to my surprise they provide local images as well and completely free for personal use. From the pictures it also looks like an older Android which suits my use case better. I am curious if it's compatible with VMware? They provide VirtualBox image and this shouldn't be all that much different and you should be able to run it on VMware but you know sometimes you are surprised to see how someone can fuck up compatibility like totally.
If this works as I think it does it's a dream!
Your best bet is Android x86, but if you need a driver for a camera or something, chances are it just doesn't exist. Make sure you can restore Windows from a USB or something before trying it.
Sure Its free https://www.android-x86.org/ When I used it (years ago) UX was bad.
alternatives comparison looks better, but ads no sideloading apps w/o paying etc. The video is gonna tell everything.
Make sure you are using a 64-bit ISO, and verify it by comparing it's sha1sum value - an easy way to do this in Windows is go to the folder where your ISO is stored, hold CTRL+Shift and right click, and select Open Powershell here. Type the following command:
CertUtil -hashfile "android-x86_64-9.0-r2.iso" sha1
Replacing the file name with the filename of your ISO if it is different. It will then spit out a long piece of text, compare that to the piece of text under "sha1sum" on the download page. Both of those need to match exactly. If they do not you need to redownload your ISO.
You can also try going into your UEFI settings (probably F2) and see about disabling "Secure boot" (under the "Boot" tab) and "Load legacy option rom" also under the boot tab. You may or may not need to disable secure boot.
If that doesn't work make sure your UEFI firmware is up to date, if you got the machine brand new there may be an update that will make booting from USB work more reliably.
No, that's not true.
From here
98% of Debian is currently built: over 12200 source (arch-specific) packages. for Arm64 architecture and Unstable Flavour.
And Raspian is a distro based on Debian targeted towards arm64 architecture for Raspberrypi.
And no you can't run Android Apps on Linux OS as such. You have Android-x86 or Anboc or some other emulator as options.
For a bit more of an exotic OS, try Android-x86. It runs amazingly well on my surface pro 3 and everything works fine out of the box and it can even see the pen pressure (the only app I've found that for sure supports it is the handwriting mode in GBoard).
Not sure what happened to you there for a loop to happen but I think its best to try the other option "Upgrade" or re-install fresh to be on the safe side at this point.
Stick to instructions here: https://www.android-x86.org/installhowto.html
Hope all goes well for you bro!
- Remove any screen lock or passwords from you Android x86 system for good measure.
- Download the latest Android x86 ISO
- Format a jump drive to fat32
- Extract ISO contents to Jump drive
- Boot to Jump drive
- GRUB Menu will come up and give you a bunch of options (same GRUB menu that came up when you were installing Android x86)
- You will see an option called "Auto_Update - Auto Update Android x86"
- It will find you partition and automatically update the Android System where you installed it on your hard-drive.
- Wait till its done and either boot to the updated Android or for good measure Reboot the device (but remove the Jump Drive) and Boot into your updated system. Rebooting first is the best way to know that things worked as it should and there are no issues when booting into it normally.
----------------------------------------------------------------------------------------------------------------
Update: I just remembered there is a guide by the Android x86 Team here:
https://www.android-x86.org/installhowto.html
Scroll down until you see a section called "Auto-Update" OR the "UPGRADE" section.
I think the "UPGRADE" section is what you're looking for and the "AUTO-Update" might be more for Updating from eg. Android 9.0r1 to Android 9.0r2 (Then again I think both work to do the same thing ...whether it be to jump from release 1 to 2 or from android 8 to 9.)
Good luck bro !
https://www.android-x86.org/download.html
Download .ISO, open it and copy/extract the files to a formatted (fat32) usb (no need for Rufus), have laptop boot from usb and run the install to HDD. I used this same method with my dual boot setup for windows 10 + Android x86 on my Surface Pro 3. Thank me later
Hm, would be difficult. Do you have a spare phone lying around? Then I'd recommend flashing lineageos or any other rom without gapps.
Alternatively, there's the Android x86 project: https://www.android-x86.org/ Note however that only the 14.1 version is supported as far as I'm concerned. I also don't know if these images actually work in a VM setup.
Never used virtual box ....but Bliss OS has issues with XCloud...however Android x86 works for me. I think the dev of bliss OS once told me the native bridge on Android x86 is different from that of Bliss OS and that maybe the issue.
Android x86 (https://www.android-x86.org/releases.html)
Does it need to be separate from your phone? I know there's a couple of programs to control your phone from your pc. (emulate the phone)
As u/AayushBhatia06 suggested, you could use a VM.
Just download the Android ISO and put it into Virtual Box or Hyper-V (not sure if Hyper-V is supported on win 7 but I know virtual box is)
Seems you can download the ISO from here
https://www.android-x86.org/download
​
It's really quick and easy to set up.
Not sure how you're gonna "emulate" the gsm card / sim card / gps or stuff like that if you need it (on the vm).
Try to go the VirtualBox route, then. Install Oracle VM VirtualBox, and attempt this: https://www.android-x86.org/documentation/virtualbox.html
Use the 32-bit version of Android-x86.
Various parts of the Android system are hardcoded to expect SSE instructions to improve performance.The Android x86 project put in some work to be able to run Android without these (see https://sourceforge.net/p/android-x86/misc/3/ for example) but nobody investigated yet what it would take and if it makes sense to bring these changes to Anbox without decreasing performance for those systems with newer processors that do support modern versions of SSE.
Iirc ALL Android-x86 images are GApps compatible.
I've seen many posts of people posting their desktops and writing about Ubuntu/Windows dual boot, so I thought I'd do something new:
Ubuntu/Android dual boot!
I recently got rid of Windows and switched over to Ubuntu completely after I managed to get most of my steam games running on Ubuntu. While searching for an android emulator I stumbled upon Android x86 and tried to install it on my device. Works like a charm and after editing the Ubuntu GRUB I can now switch between both OS.
> Can I download Android x86 source code manually. 1. My internet is very slow
What do you mean by "manually"? On paper? If not, if the download is being interrupted, use 'wget -c (url)', this form will restart a failed download.
Also the Android x86 source is a huge download, by anyone's standards. Android-x86 : "Note: The Android-x86 repository is very big (more than 20GB for oreo-x86)"
20 gigabytes. That's enormous.
> But now it doesn't support ARM architectured applications.
Most everyday Android applications are written in Java, which doesn't care what the host processor is. But if you need to run ARM binaries meant for Android, on an x86 platform this approach won't work no matter what Android emulator you choose -- Android-x86 can't do this either.
Why not check out the Android x86, I use it for development sometimes as it is the fast version that runs on the x86 platform. They are only up to Android 9.x right now
Just run it in Vmware/Virtual Box. No lag,
Your safest option to run Android apps on PC is not through emulation, but installing Android directly onto your drive. Android-x86 will outperform any emulators since it's not emulation. It's not very desktop-friendly, which is why Bliss OS exists.
There are special Android packages like Android-x86 that are specially compiled to run on desktop processors (normal Android distributions require an ARM processor).
So you can install Android-x86 on a VM and run most kinds of Android apps (except those that use native ARM binary code).
These are the instructions I used:
https://www.android-x86.org/source.html
I built on Ubuntu 16.04 previously, and the instructions are even clearer this time, for using Ubuntu 18.04.
That should get you started. Just remember, when building using Android x86/LineageOS/AOSP it is building just the base, so there are no GApps in it but they can be added later if you really want. Others might like to install F-Droid but it's entirely up to you :)
That will get you to an ISO which you can either burn directly or extract to USB (I extract to USB).
https://www.android-x86.org/releases/releasenote-9-0-r2.html
Did you download the RPM, convert it to *.deb using the instructions, and install that way? It's supposed to automatically add itself to your currently existing GRUB menu.
If you used the ISO, then it won't do that.
>There are no 100% safe emulators
There is. Androdi x86 +your favorite virtual machine. Performance isn't great and it may require some tinkering to make things work but it is open source so you know what actually goes under the hood.
There are x86 sources & binaries out there. In fact the first stable build of Android_9 for x86 was just released Thursday https://www.android-x86.org/releases/releasenote-9-0-r1.html. Their build process allows for kernel customization.
If you really want to build an image from scratch using the AOSP then this is a good place to start http://www.staroceans.org/kernel-and-driver/%5BEmbedded.Android(2013.3)%5D.Karim.Yaghmour.pdf
I see you having two options:
A cloud emulator - https://cloud.geny.io/
Or doing dual boot into Android when you want to run your code (not recommended) https://www.android-x86.org/
Or buying a raspberry pi and running Android on that. (although I would just run it on the phone directly)
I have a pretty fast computer and I prefer to run dev on my Android handset. Debugging works a treat, and it's much smoother.
The one I used is https://www.android-x86.org/
I agree with you. Even a year ago, your options sucked. Things have changed drastically recently it seems. Honestly I expected this thing not to work. I wouldn't have been surprised if it didnt boot. When it did, expected wifi to not work and mouse pad to not work. But nope. Everything works perfectly. The only thing is when I launched Echoes, it kept crashing instantly. I went to permisssions and allowed storage, mic, etc and now it works without an issue. I'm getting pretty much the same performance as my iPad air. With bluestacks running on windows 10, I was getting like 10 fps.
I know I'm late but you can use Virtual Box + Android x86. It is worse than Nox, Bluestacks, Memu and basically any other stand alone emulator, but at least it is as safe as you can get. The downside is that installation itself is quite a process and requires several google searches to do it properly.
잘 안됩니다. 전 Venue 8 Pro 5855 였는데요.
설치해본 건 피닉스 OS, The Android-x86 9.0-rc1 released 및 ubuntu 기반 linux
전부다 사운드가 안나옵니다. 그리고 무슨이유인지 OS가 최고속도로 계속 작동이되서 베터리가 녹더군요.
Here , run it in a virtual machine or boot from a pen drive, or put the iso on your phone and use DriveDroid to boot from the iso (better if you're trying multiple isos)
I installed this KitKat many years ago:
They are still on Oreo, likely not current on monthly patches, but should run some apps. There was some collaboration with Lineage in the past.
Otherwise, I remember PhoenixOS as an option, but I wouldn't use it for anything sensitive.
Please instead of using these terrible malware-ridden 'android emulators' - just grab a copy of VirtualBox and Android-x86.
Although there are few and little optimized emulators, we have a port of Android for x86 and some arm forks, both stripped with any Google code, although they're working in replacing google's proprietary libraries for free ones.
You could execute them in a real computer and would get all the 3D acceleration of Linux Mesa drivers.
(Can the app in App Store work in x86? They're java and java-like programs, they should work in any architecture... shouldn't they?)
Well if you're set on Windows, here's a video about running it off an SD card.
https://www.youtube.com/watch?v=BrcBKpE9aQg
Though I would still recommend finding an x86 build of Android. It'll almost definitely be faster.
One thing you could try is get the Windows solution working first, and then try out Android. That way, even if Android fails, you'll still have that Windows bootable SD to fall back on.
you tried this? https://www.android-x86.org/ supposedly a linux distro based on android so should be dual bootable with windows
or you could try running it in a VM, guide here https://linuxhint.com/install_android_virtualbox/
Gw ga tau memu (ini qemu versi windows?) apaan, tapi kalo mau pake android gw boot up android-x86 sih.
Lebih ringan, berhubung itu tok Android doang, ga menuh2in sistem buat jalanin Windows + virtualisasi lagi. Kalo pake laptop, jauh lebih hemat batre juga. Gw ga tau sih kualitas ARM bridge-nya kayak gimana sekarang, meski dulu ade gw pake buat gaming game ecek2 macem Mobile Legends sih jalan2 aja. Gw selama ini cuma pake buat aplikasi yang gw ga mau taro ke hp karena suka ngetrack2.
That's not entirely true. Android is not bloated or heavy. Gapps on the other hand are. More to the point, take a look at any desktop environment and you can't possibly get away with using less than 400MB of RAM while Android will happily run on that. If you want to see just how much faster the Android is than regular Linux application I suggest grabbing Android x86 image and running it from USB. You'll surprised.
I have no idea what makes you think that first mobile release of desktop applications, services and environment would be better at running on mobile phone than operating system specially designed for mobile devices and optimized over the course of almost a decade. If nothing else Android will silently close applications while saving their state in order to free up memory for others while there's no such functionality on native Linux applications.
Early Androids, sure. Versions after 5 I don't agree as much. Android is very flexible and well optimized operating system. It doesn't feel like it but the moment you run it on x86 CPU you realize just how fast and well optimized it is. Also, when people say Android, they usually think of Android + Gapps. Pure Android is far less bloated.
I suggest grabbing Android x86 ISO image, making a bootable USB and trying it. It's one hell of a usable desktop OS and blistering fast.