I have a Linux ARM64 _computer_ (not phone). How can I use this to run an ARM64 Android phone image? [Android Studio does not work on ARM64 computers](https://developer.android.com/studio/install#linux) . Android Studio with emulator works on x86. I do not want to use ARM64 to emulate x86 to run the x86 Android image since it is unusably slow.

Sometimes I start Android Emulator with the GUI, and sometimes I start with the CLI. If I keep using the same method, everything is fine, but if I switch between methods, it causes problems. For example if I start the emulator with the CLI, then shut down, then start again using the GUI, I get this: ~~~ Cold boot: snapshot failed to load ~~~ If I start with the GUI, then shut down and start with the CLI, I get this: ~~~ qemu-system-i386.exe: Failed to load virtio-blk:virtio ~~~ Here is the command I use with CLI: ~~~ adb start-server emulator -writable-system -avd Pixel_2_API_24 ~~~ Am I doing something wrong?

Can I run a virtual Android machine on my Samsung Galaxy S6 Edge? Or maybe can I run a custom ROM without flashing stock?

I run Android Virtual Device manager, and use the fake location option "... more", Location, Set location. But I have to do this every time I start, so my apps get another location during bootup. How can I permanently set this?

I managed to run an Android emulator:

$ emulator Android30
INFO    | Storing crashdata in: /tmp/android-pcmagas/emu-crash-34.2.14.db, detection is enabled for process: 93905
INFO    | Android emulator version 34.2.14.0 (build_id 11834374) (CL:N/A)
ERROR   | No AVD specified. Use '@foo' or '-avd foo' to launch a virtual device named 'foo'
$ emulator -avd Android30

And I have a Realtek RTL8188EUS Wi-Fi USB dongle. How can I pass through it to the emulator so I can make the emulator manage it directly? I want to do similarly as I do with VirtualBox:

Based on my 30-60 minutes doing research on Google it seems there is no general solution for my question, but I wanted to double check on my favorite Q&A forum network, SE. So, how can I run an Android app on an iPhone?

I have tried only the android emulator in the android sdk, and waydroid until now. Apps installed into both say that they are running on a rooted device, what is right - having access to their image files I could actually do there what I want. However, I would be more happy to run seamlessly also them. Is there a solution, ideally free but also paid might be fine, where I can execute these apps and they do not know that the phone is "rooted"?

I am using Termux to run a Linux environment on an Android device. When I try to run the command adb shell getprop ro.build.fingerprint I get the error "no devices/emulators found". I have already enabled the USB Debugging in the Developer Options. I have installed the program

by executing

install android-tools

. I have also tried killing and starting the servers via adb kill-server adb start-server But I still get the same error. I would appreciate it if someone could help me fix it!

When I try to install an apk file through the monkeyrunner Python script, getting the error INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113. How can I resolve this issue? Detail of the virtual device is listed as follows: - CPU/ARM: **x86** - API Level: **24** - Target: **Android 7.0 (Google Play)**

The older version of the Outline app could be installed on BlueStacks and the MEmu emulator. However, the new version of Outline available on the Play Store is no longer compatible with the Android versions of these emulators. Is there a way to install the Outline app on these emulators?

I'm dealing with some pretty insidious hacks on both my phone and computer (Fedora 41). A lot of it has to do with Google, but more than that, I'm still a little lost. I plugged my compromised Android into my USB port and probably compromised my computer more than it already was. When setting up a simple blank activity in the emulator with Wireshark running, I'm seeing A BUNCH of RTSP packets signifying consistent streaming. I'm guessing it to be real-time sound data. The microphone icon is on on the toolbar of my desktop too. This doesn't seem correct to me, but as I don't have a known safe baseline to compare I can't determine "appropriate" behavior. Is this normal behavior?

I developed an Android application using Adobe Flash Professional and I need to try it with a virtual device. I failed to install Adobe Air under AVD and Genymotion. For Genymotion, some services are limited in the case of the free version. Can someone describe how to fix my problem?

https://developer.android.com/studio/run/managing-avds#system-image says > To ensure app security and a consistent experience with physical devices, system images with the Google Play Store included are signed with a release key, which means that you cannot get elevated privileges (root) with these images. If you require elevated privileges (root) to aid with your app troubleshooting, you can use the Android Open Source Project (AOSP) system images that do not include Google apps or services. But what if I wanted both root AND Google services? how could I do that? Thanks!

When I run adb devices, it shows an offline emulator: List of devices attached emulator-5554 device emulator-5562 offline However, when I run Device Manager in Android Studio, it's not listed. When I try to kill the emulator with adb -s emulator-5562 emu kill, I get connection refused. When I try to get info about it with adb -s emulator-5562 shell getprop, I get "device offline". My $HOME/.android/avd folder is empty. I can't find any sign of this emulator in my file system. I'm on a Mac. How do I get rid of this thing? I have a React Native project that I can't run on Android, because the expo command keeps trying to run on this mysterious offline emulator, so I'm trying to attack what I think is the root issue.

Does anyone know what the trick is to sign into Google in Android Studio Emulator? I have tried to follow every tutorial I can find. - [Could not sign in Google account on android emulator with react-native app](https://stackoverflow.com/questions/58882366/could-not-sign-in-google-account-on-android-emulator-with-react-native-app) - [Unable to Sign in into with google in Android Studio Emulator(API 30, target - Android 11.0 with Google Play, CPU- x86 )](https://discuss.appium.io/t/unable-to-sign-in-into-with-google-in-android-studio-emulator-api-30-target-android-11-0-with-google-play-cpu-x86/34596)

We have a project and development within an Esri ArcGIS enterprise platform that will utilise the FieldMaps Android (standard Play Store) application. We need to work out how to side-load data (regional map data) onto the device within an MDM-managed environment. However, we are struggling to use Android Studio to create a fully managed device within a mobile device management platform. We have tried: - At AVD Creation, we don't get an option to allow the out-of-the-box experience (i.e. initially setup) to enroll a device into fully managed. - We have attempted to factory reset the emulated device but it never actually resets - We have been able to enroll a device as a work profile, but this isn't the same as a Managed Device. For a fully managed Android device, you press the screen 8 times at the setup stage and it asks how you want to enroll, but in the emulator, it bypasses this. Any way to get it back? Or is it a specific image we need or is it not possible?

I have an Android Headunit in my car and I have started to "play" with Tasker automation as a hobby. I wanted to create some Tasker scenes on my personal computer using the Android Emulator from Android Studio since sitting in the car all day is not convenient. Unfortunately, I cannot get the hardware acceleration to work and the virtual devices are very slow. I tried to set up the **Android Emulator hypervisor driver** as described here . **Settings I made:** - *Windows Features deactivated:* VM-platform, Windows-Sandbox, Credential Guard, Hypervisor Platform - *BIOS:* Intel Virtualization Technology: On (cannot be switched off); Intel VT-d Feature: On (cannot be switched off) I've **installed the Driver** via *SDK-Tools*: Android Emulator hypervisor driver (installer): Installed (Version 2.2.0) The installer from Github **failed (silent_install.bat)** (I translated the output-message): [SC] ControlService ERROR 1062: Service not started. [SC] DeleteService SUCCESS [SC] StartService NOT SUCCESSFUL, ERROR 4294967201. Check for Hardware Acceleration in the Emulator failed: emulator -accel-check liefert folgende Antwort: INFO | Storing crashdata in: C:\Users\xxxx\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db, detection is enabled for process: 15964 Mayer\AppData\Local\Android\Sdk\emulator\emulator-check.exe: 100 Unknown argument Mayer\AppData\Local\Android\Sdk\emulator\emulator-check.exe accel: 0 Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.19045) is installed and usable. accel I ran bcdedit /set hypervisorlaunchtype off as suggested and it succeeded. But the check in **Windows command** line shows that **driver is not running:** sc query aehd SERVICE_NAME: aehd TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 31 (0x1f) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 The Check for Hardware Acceleration in the Emulator failed: emulator -accel-check INFO | Storing crashdata in: C:\Users\*****\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.20.db, detection is enabled for process: 15964 Mayer\AppData\Local\Android\Sdk\emulator\emulator-check.exe: 100 Unknown argument Mayer\AppData\Local\Android\Sdk\emulator\emulator-check.exe accel: 0 Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run bcdedit /set hypervisorlaunchtype off, reboot.WHPX (10.0.19045) is installed and usable. accel **System-Information:** Windows 10 Enterprise 10.0.19045 Build 19045 Processor: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz, 2803 MHz, 4 Kerne, 8 logische Prozessoren Physical Memory: 16.0 GB BIOS: LENOVO N34ET48W (1.48),28.01.2022 Android Studio Information: Android Studio Iguana 2023.2.1 Patch 1 Android SDK Build-Tools 35-rc3 Does anybody know what I am doing wrong?

I learned that on modern mobile phones, the Android Keystore is protected using the TEE (Trusted Execution Environment), and even if you gain root access to the device, the files in the keystore located in /data/misc/keystore are useless as they are encrypted, and even the "owner" app using the keypairs are unable to access the private key material to display/export/modify it. This all makes sense. My question is: What is happening in an emulator like the one coming with Android Studio (Virtual Device Manager)? I am running an x86 Android 8.1 Oreo (API 27) there. Who's protecting the keystore, as there is no TEE present? Are the keys located in /data/misc/keystore encrypted too, or are these the real certificates and keypairs?

I'm trying to install GApps/Magisk etc any addon through the TWRP recovery to the Android Virtual Device based on Android 5.1.1 and the Nexus 10. The first step that I have accomplished has been to boot the TWRP thanks to an hint found here : https://github.com/TeamWin/android_device_emulator_twrp/issues/2 He suggested to use an older version of SDK Tools(24.4.1). With it I have booted TWRP 2.8.0.1 in android 5.1.1 armeabi-v7a for the tablet Nexus 10 : $ /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator -verbose -avd Nexus_10_API_22 - ramdisk /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img -kernel /home/ziomario/ Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel -show-kernel -gpu off emulator:Found AVD name 'Nexus_10_API_22' emulator:Found AVD target architecture: arm emulator:Looking for emulator-arm to emulate 'arm' CPU emulator:Probing program: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm emulator:return result: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm emulator:Found target-specific emulator binary: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm emulator:GPU emulation is disabled emulator: Running :/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm emulator: qemu backend: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm" emulator: qemu backend: argv = "-verbose" emulator: qemu backend: argv = "-avd" emulator: qemu backend: argv = "Nexus_10_API_22" emulator: qemu backend: argv = "-ramdisk" emulator: qemu backend: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img" emulator: qemu backend: argv = "-kernel" emulator: qemu backend: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel" emulator: qemu backend: argv = "-show-kernel" emulator: qemu backend: argv = "-gpu" emulator: qemu backend: argv = "off" emulator: Concatenated backend parameters: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm -verbose -avd Nexus_10_API_22 -ramdisk /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img -kernel /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel -show-kernel -gpu off emulator: found ANDROID_SDK_ROOT: /home/ziomario/Android/Sdk/ emulator: Android virtual device file at: /home/ziomario/.android/avd/Nexus_10_API_22.ini emulator: virtual device content at /home/ziomario/.android/avd/Nexus_10_API_22.avd emulator: virtual device config file: /home/ziomario/.android/avd/Nexus_10_API_22.avd/config.ini emulator: using core hw config path: /home/ziomario/.android/avd/Nexus_10_API_22.avd/hardware-qemu.ini emulator: Found AVD target API level: 22 emulator: Read property file at /home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//build.prop emulator: No boot.prop property file found. emulator: found skin 'nexus_10' in directory: /home/ziomario/Android/Sdk/skins emulator: autoconfig: -skin nexus_10 emulator: autoconfig: -skindir /home/ziomario/Android/Sdk/skins emulator: keyset loaded from: /home/ziomario/.android/default.keyset emulator: trying to load skin file '/home/ziomario/Android/Sdk/skins/nexus_10/layout' emulator: Auto-detect: Kernel image requires legacy device naming scheme. emulator: Auto-detect: Kernel does not support YAFFS2 partitions. emulator: Using initial system image: /home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//system.img emulator: autoconfig: -data /home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata-qemu.img emulator: autoconfig: -initdata /home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata.img emulator: autoconfig: -cache /home/ziomario/.android/avd/Nexus_10_API_22.avd/cache.img emulator: autoconfig: -sdcard /home/ziomario/.android/avd/Nexus_10_API_22.avd/sdcard.img emulator: Physical RAM size: 1907MB emulator: GPU emulation is disabled emulator: WARNING: CPU acceleration only works with x86/x86_64 system images. Content of hardware configuration file: hw.cpu.arch = arm hw.cpu.model = cortex-a8 hw.ramSize = 1907 hw.screen = touch hw.mainKeys = no hw.trackBall = no hw.keyboard = yes hw.keyboard.lid = no hw.keyboard.charmap = qwerty2 hw.dPad = no hw.gsmModem = yes hw.gps = yes hw.battery = yes hw.accelerometer = yes hw.audioInput = yes hw.audioOutput = yes hw.sdCard = yes hw.sdCard.path = /home/ziomario/.android/avd/Nexus_10_API_22.avd/sdcard.img disk.cachePartition = yes disk.cachePartition.path = /home/ziomario/.android/avd/Nexus_10_API_22.avd/cache.img disk.cachePartition.size = 66m hw.lcd.width = 1600 hw.lcd.height = 2560 hw.lcd.depth = 16 hw.lcd.density = 320 hw.lcd.backlight = yes hw.gpu.enabled = no hw.initialOrientation = landscape hw.camera.back = none hw.camera.front = none vm.heapSize = 192 hw.sensors.proximity = no hw.sensors.magnetic_field = yes hw.sensors.orientation = yes hw.sensors.temperature = yes hw.useext4 = yes kernel.path = /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel kernel.parameters = androidboot.hardware=goldfish android.checkjni=1 kernel.newDeviceNaming = no kernel.supportsYaffs2 = no disk.ramdisk.path = /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img disk.systemPartition.initPath = /home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//system.img disk.systemPartition.size = 1500m disk.dataPartition.path = /home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata-qemu.img disk.dataPartition.size = 2g avd.name = Nexus_10_API_22 . QEMU options list: emulator: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm" emulator: argv = "-show-kernel" emulator: argv = "-android-hw" emulator: argv = "/home/ziomario/.android/avd/Nexus_10_API_22.avd/hardware-qemu.ini" Concatenated QEMU options: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm -show-kernel -android-hw /home/ziomario/.android/avd/Nexus_10_API_22.avd/hardware-qemu.ini failed to load image file '/home/ziomario/Android/Sdk/skins/nexus_10//port_back.webp' emulator: ## WARNING: can't load part '' from skin failed to load image file '/home/ziomario/Android/Sdk/skins/nexus_10//land_back.webp' emulator: ## WARNING: can't load part '' from skin emulator: ### WARNING: ignoring part location with unknown name 'portrait' emulator: ### WARNING: ignoring part location with unknown name 'landscape' emulator: Starting QEMU main loop emulator: trying to find: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/lib/ca-bundle.pem emulator: registered 'boot-properties' qemud service emulator: Using kernel serial device prefix: ttyS emulator: Ramdisk image contains fstab.goldfish file emulator: Found format of system partition: 'ext4' emulator: Found format of userdata partition: 'ext4' emulator: Found format of cache partition: 'ext4' emulator: system partition format: ext4 emulator: Mapping 'system' partition image to /tmp/android-ziomario/emulator-s31jL5 emulator: nand_add_dev: system,size=0x5dc00000,file=/tmp/android-ziomario/emulator-s31jL5,initfile=/home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//system.img,pagesize=512,extrasize=0 emulator: userdata partition format: ext4 emulator: nand_add_dev: userdata,size=0x80000000,file=/home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata-qemu.img,pagesize=512,extrasize=0 emulator: cache partition format: ext4 emulator: nand_add_dev: cache,size=0x4200000,file=/home/ziomario/.android/avd/Nexus_10_API_22.avd/cache.img,pagesize=512,extrasize=0 emulator: registered 'boot-properties' qemud service emulator: Adding boot property: 'dalvik.vm.heapsize' = '192m' emulator: Adding boot property: 'qemu.sf.lcd_density' = '320' emulator: Adding boot property: 'qemu.hw.mainkeys' = '0' emulator: Adding boot property: 'qemu.sf.fake_camera' = 'none' emulator: Kernel parameters: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=1 emulator: autoconfig: -scale 0.471507 serial0 console emulator: Forcing ro.adb.qemud to "0". emulator: control console listening on port 5554, ADB on port 5555 emulator: sent '0012host:emulator:5555' to ADB server emulator: android_hw_fingerprint_init: fingerprint qemud listen service initialized emulator: Failed to parse .AndroidStudio preferences file usage.statistics.xml emulator: Defaulting user crash-report opt-in to false emulator: Skipping metrics reporting: No user opt-in. emulator: UpdateChecker: skipped version check Uncompressing Linux... done, booting the kernel. goldfish_fb_get_pixel_format:170: display surface,pixel format: bits/pixel: 16 bytes/pixel: 2 depth: 16 red: bits=5 mask=0xf800 shift=11 max=0x1f green: bits=6 mask=0x7e0 shift=5 max=0x3f blue: bits=5 mask=0x1f shift=0 max=0x1f alpha: bits=0 mask=0x0 shift=0 max=0x0 Booting Linux on physical CPU 0 Initializing cgroup subsys cpu Linux version 3.4.67-gd3ffcc7 (dees_troy@XPS12-Ubuntu) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #2 PREEMPT Thu Aug 14 16:20:36 CDT 2014 CPU: ARMv7 Processor [410fc080] revision 0 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Goldfish Truncating RAM at 00000000-772fffff to -2f7fffff (vmalloc region overlap). Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 193040 Kernel command line: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=1 PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 760MB = 760MB total Memory: 745824k/745824k available, 32416k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) lowmem : 0xc0000000 - 0xef800000 ( 760 MB) .text : 0xc0008000 - 0xc0454578 (4402 kB) .init : 0xc0455000 - 0xc047a000 ( 148 kB) .data : 0xc047a000 - 0xc04b3808 ( 231 kB) .bss : 0xc04b382c - 0xc05fdaf0 (1321 kB) NR_IRQS:256 sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms Console: colour dummy device 80x30 Calibrating delay loop... 1047.75 BogoMIPS (lpj=5238784) pid_max: default: 32768 minimum: 301 Security Framework initialized SELinux: Initializing. Mount-cache hash table entries: 512 Initializing cgroup subsys debug Initializing cgroup subsys cpuacct Initializing cgroup subsys freezer CPU: Testing write buffer coherency: ok Setting up static identity map for 0x368698 - 0x3686f0 NET: Registered protocol family 16 bio: create slab at 0 Switching to clocksource goldfish_timer NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP: reno registered UDP hash table entries: 512 (order: 1, 8192 bytes) UDP-Lite hash table entries: 512 (order: 1, 8192 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. Trying to unpack rootfs image as initramfs... Freeing initrd memory: 2976K goldfish_new_pdev goldfish_interrupt_controller at ff000000 irq -1 goldfish_new_pdev goldfish_device_bus at ff001000 irq 1 goldfish_new_pdev goldfish_timer at ff003000 irq 3 goldfish_new_pdev goldfish_rtc at ff010000 irq 10 goldfish_new_pdev goldfish_tty at ff002000 irq 4 goldfish_new_pdev goldfish_tty at ff011000 irq 11 goldfish_new_pdev goldfish_tty at ff012000 irq 12 goldfish_new_pdev smc91x at ff013000 irq 13 goldfish_new_pdev goldfish_fb at ff014000 irq 14 goldfish_new_pdev goldfish_audio at ff004000 irq 15 goldfish_new_pdev goldfish_mmc at ff005000 irq 16 goldfish_new_pdev goldfish-battery at ff015000 irq 17 goldfish_new_pdev goldfish_events at ff016000 irq 18 goldfish_new_pdev goldfish_nand at ff017000 irq -1 goldfish_new_pdev qemu_pipe at ff018000 irq 19 goldfish_pdev_worker registered goldfish_interrupt_controller goldfish_pdev_worker registered goldfish_device_bus goldfish_pdev_worker registered goldfish_timer goldfish_pdev_worker registered goldfish_rtc goldfish_pdev_worker registered goldfish_tty goldfish_pdev_worker registered goldfish_tty goldfish_pdev_worker registered goldfish_tty goldfish_pdev_worker registered smc91x goldfish_pdev_worker registered goldfish_fb goldfish_pdev_worker registered goldfish_audio goldfish_pdev_worker registered goldfish_mmc goldfish_pdev_worker registered goldfish-battery goldfish_pdev_worker registered goldfish_events goldfish_pdev_worker registered goldfish_nand goldfish_pdev_worker registered qemu_pipe audit: initializing netlink socket (disabled) type=2000 audit(0.350:1): initialized Installing knfsd (copyright (C) 1996 okir@monad.swb.de). fuse init (API version 7.18) msgmni has been set to 1462 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) console [ttyS0] enabled brd: module loaded loop: module loaded nbd: registered device at major 43 goldfish_audio_probe goldfish nand dev0: size 5dc00000, page 512, extra 0, erase 0 goldfish nand dev1: size 80000000, page 512, extra 0, erase 0 goldfish nand dev2: size 4200000, page 512, extra 0, erase 0 tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre eth0: SMC91C11xFD (rev 1) at fe013000 IRQ 13 [nowait] eth0: Ethernet addr: 52:54:00:12:34:56 mousedev: PS/2 mouse device common for all mice *** events probe *** events_probe() addr=0xfe016000 irq=18 events_probe() keymap=qwerty2 input: qwerty2 as /devices/virtual/input/input0 goldfish_rtc goldfish_rtc: rtc core: registered goldfish_rtc as rtc0 device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com ashmem: initialized logger: created 256K log 'log_main' logger: created 256K log 'log_events' logger: created 256K log 'log_radio' logger: created 256K log 'log_system' Netfilter messages via NETLINK v0.30. nf_conntrack version 0.5.0 (11700 buckets, 46800 max) ctnetlink v0.93: registering with nfnetlink. NF_TPROXY: Transparent proxy support initialized, version 4.1.0 NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd. xt_time: kernel timezone is -0000 ip_tables: (C) 2000-2006 Netfilter Core Team arp_tables: (C) 2002 David S. Miller TCP: cubic registered NET: Registered protocol family 10 ip6_tables: (C) 2000-2006 Netfilter Core Team IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 NET: Registered protocol family 15 8021q: 802.1Q VLAN Support v1.8 VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 0 goldfish_rtc goldfish_rtc: setting system clock to 2024-08-21 19:34:03 UTC (1724268843) Freeing init memory: 148K mmc0: new SD card at address e118 mmcblk0: mmc0:e118 SU02G 512 MiB mmcblk0: type=1403 audit(1724268843.570:2): policy loaded auid=4294967295 ses=4294967295 SELinux: Loaded policy from /sepolicy type=1404 audit(1724268843.580:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 init: /dev/hw_random not found init: cannot open '/initlogo.rle' eth0: link up init: /dev/hw_random not found init: Unable to open persistent property directory /data/property errno: 2 init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead init: property 'ro.serialno' doesn't exist while expanding '$ro.serialno' init: cannot expand '$ro.serialno' while writing to '/sys/class/android_usb/android0/iSerial' EXT4-fs (mtdblock1): recovery complete EXT4-fs (mtdblock1): mounted filesystem with ordered data mode. Opts: EXT4-fs (mtdblock0): mounted filesystem with ordered data mode. Opts: Now,let's say I want to install Magisk using the TWRP to the emulator, what should I do ? I imagine that I should save the Magisk file (or any other zipped adddon) inside the sd card...or ? How can I do this ?

I want to build AOSP from source, build Linux kernel from sources and run all of this in android emulator. Later I need to make some experiments, for which I need to modify sources, so this is why i need to build all the code from sources. I am doing repo init --partial-clone -b main -u https://android.googlesource.com/platform/manifest (I have tried main branch and android 14 branch...), then repo sync, lunch some target (I have tried miscellaneous ones) then "m", then trying to run emulator. And at this moment I have a problem: the emulator cannot start. Basically, there are two reasons for that: * Kernel is unable to decompress LZ4-compressed image (I unpack the image by hands, but this not helps, see next issue); * Kernel is unable to mount file systems. This may happen because kernel doesn't have DTB (which dtb on x86_64???) Also, I found, that by default emulator uses not a kernel from "out" directory, but some other. I specify in command line (via -kernel option) the kernel found in "out" directory, but this not helps. * for -eng builds, emulator complains on absence of user-data.img file; * for userdebug builds, emulator is unable to mount root or some other partitions (linux kernel starts, but init process aborts with error message). I'm looking for instruction how can I make x86_64 build which will run in the emulator. Maybe I need some particular target or some particular branch?