A typical Windows OS ready x86_64 Android emulator is made of the 2 components Virtualbox - host - and Android image - client OS - so as with Bluestacks, MEmu, LDPlayer, etc.pp.
Actual x86_64 Virtualbox v6 - without extensions - occupies 228 MB, an x86_64 Android 11 GSI image occupies 1.5 GB disk space, so in total ~1.8 GB at minimum are used by an Android emulator based on Virtualbox, whereas
Microsoft's Windows Subsystem for Android ( WSA - it's Android 11 ) occupies 2.03 GB.
BTW: If you add Virtualbox Extension pack, then additional 10 MB diskspace is used.
Resume: An x86_64 Virtualbox based Android emulator suprisingly takes ~ 10% less disk space than WSA.
i prefer wsa because due its intel-arm-translator it can run apps compiled for arm, too
Related
Hi,
I'm facing imgdiff freeze when creating OTA package (vendor Lollipop SDK) on large files. Applypatch package is same as AOSP 5.1.1, OS is Debian 8.2 x64, machine is dedicated server with 8 physical cores and 72 gb ram, ccache is not used.
top command shows that imgdiff utilizes 100% of CPU while iotop shows no HDD activity (SW raid, 2x1TB mirror, not running out of space).
Any idea or help appreciated, I'm out of ideas.
Thanx
Hi,
I have a program compiled for ARM Linux. It can use /dev/fb0 rather than X. Is there an Android app, possibly more than one choice, which will provide an environment where this program can run?
The version of this program for the Intel PC runs in Android under bochs. If the ARM executable can work, I'd expect it to be faster than the Intel executable.
Thanks! ... Peter E.
Hi
I have tried usb key, hdd install using both 32 and 64 bit, however after the grub screen my display goes blank. I have waited over 30 mins but it does load and show remix screen. Here is my config. I have this running fine on my old HP pavilion and its great so would love to be able to run it on my large Acer. Any help appreciated
OS Name Microsoft Windows 7 Ultimate N
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name KITCHEN
System Manufacturer Acer
System Model Aspire Z5610
System Type x64-based PC
Processor Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz, 2327 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date Phoenix P01-B2, 19/01/2010
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
Time Zone GMT Daylight Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.87 GB
Available Physical Memory 1.63 GB
Total Virtual Memory 7.74 GB
Available Virtual Memory 5.45 GB
Page File Space 3.87 GB
Page File C:\pagefile.sys
Name NVIDIA GeForce G210M
PNP Device ID PCI\VEN_10DE&DEV_0A74&SUBSYS_069110DE&REV_A2\4&357F6195&0&0008
Adapter Type GeForce G210M, NVIDIA compatible
Adapter Description NVIDIA GeForce G210M
Adapter RAM 512.00 MB (536,870,912 bytes)
Installed Drivers nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver Version 8.17.11.9666
INF File oem5.inf (Section013 section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 1920 x 1080 x 60 hertz
Bits/Pixel 32
Memory Address 0xFC000000-0xFCFFFFFF
Memory Address 0xE0000000-0xEFFFFFFF
Memory Address 0xDE000000-0xDFFFFFFF
I/O Port 0x00002000-0x0000207F
IRQ Channel IRQ 16
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver c:\windows\system32\drivers\nvlddmkm.sys (8.17.11.9666, 13.09 MB (13,728,616 bytes), 17/02/2010 06:13)
I have installed Android Studio version 2.3.3 on Windows 7 64-bit Enterprise.
Using the AVD Manager, I created a new device.
Issue: When I start the Android Virtual Device, a screen flashes and disappears. Based on some suggestions online, I read that we need to modify the Graphics settings of the Virtual Device however I don't get the option to modify these settings.
Below are the settings of the Android Device I have created:
Nexus 5X (5.2 1080x1920 xxhdpi)
Nougat (Android 7.0 x86)
Emulated Performance (Graphics -> Automatic)
Device: Enable Device Frame (checked)
Camera: Front and Back (Emulated)
Network Speed: Full and Latency: None
RAM: 1536 MB
VM Heap: 256 MB
Internal Storage: 800 MB
Keyboard: Enable Keyboard Input.
And here is the output of the command: avdmanager.bat list avd
Available Android Virtual Devices:
Name: username
Device: Nexus 5X (Google)
Path: C:\Users\username\.android\avd\username.avd
Target: Google Play (Google Inc.)
Based on: Android 7.0 (Nougat) Tag/ABI: google_apis_playstore/x86
Skin: nexus_5x
Sdcard: C:\Users\username\.android\avd\username.avd\sdcard.img
'Ello.
I successfully installed LineageOS 14.1 to its own 32 Gb ext4 partition through manual install via cgdisk 1.0.0. After it completed instead of rebooting I ran it, updated it, even installed XCOM: Enemy Within (woot!). Once I was done configuring my android OS, I decided to test reboot. Ubuntu auto loads, and there is no way to select which OS to boot to When I boot to Ubuntu and open 'Computer' desktop icon, I see the LineageOS partition as *HDD Model*: Android-x86 and all files within a folder as follows:
cm-x86-14.1-r4
data
system
initrd.img
kernel
ramdisk.img
How do I add LineageOS 14.1 to GRUB to ensure that on boot up I can select between the two OS's?
Partitions are:
NTFS 100 Mb (Windows 10)
EFT4 8 MB GRUB
EFT4 50 Gb Ubuntu /root
LinuxSwap 8 Gb
EFT4 42 Gb /Home
EFT4 32 Gb LineageOS
Also, during the manual install I was asked whether I wanted to install GRUB boot loader, but I opted against it, knowing I had already done so for Ubuntu. For future installs, If I had opted do so, would that have amended the GRUB list for me, or just caused more boot issues?
Thank you!