Knowing which processor you have is very important to make sure you are downloading the right files. One app, nowadays, has multiple versions for multiple processors so that it runs smoothly on each and every phone available. If you only install apps from the Google Play Store, then knowing which CPU architecture your phone has is not necessary, but if you sideload apps, then this information is required as CPU architecture is becoming a factor in more and more scenarios these days, including certain sideloaded app updates and, of course, custom ROMs and Gapps. As of now, there are three main CPU architectures used in Android smartphones * ARM: ARMv7 or armeabi * ARM64: AArch64 or arm64 * x86: x86 or x86abi There are a couple of 3rd-party apps to find CPU architecture found from this article : * Inware * Droid Hardware Info * My Device – Device info My question is, can we find the CPU architecture of the Android phone without installing any apps? Just in case it's relevant, the device I'm using is a Poco X2 with Android 9+.

While downloading Android apps, sometimes I have seen apps for armeabi-v7a and x86 architecture. I read some references for armeabi-v7a and x86 architecture. However, at the end, I couldn't finalize which mobile processors and architectures belong to armeabi-v7a and which belong to x86. As per my knowledge, mobile processors commonly used in Android devices are Snapdragon (by Qualcomm), MediaTek, Exynos (by Samsung) and Kirin (by Huawei). Almost all brands explain specifications of a smartphone and almost all specifications say mobile processor is 64-bit or not. Should I conclude that 64-bit of mobile processors (Snapdragon, MediaTek, Exynos or Kirin) belong to ARM architecture? **EDIT:** To understand which SoC supports armeabi-v7a Android apk and which SoC supports x86 Android apk, I have gone through the specifications of MediaTek Helio X30 and Snapdragon 855. The specification of Helio X30 says, it supports dual-core ARM Cortex-A73 and quad-core ARM Cortex-A53 but ARM is not mentioned anywhere in the specification of Snapdragon 855. So should I conclude that Helio X30 will support armeabi-v7a Android apps and Snapdragon 855 will not support armeabi-v7a apps? Please clarify my confusions.

I happened to be working on an Android application written around *2010* or so and the target OS is Android Cupcake. The application was written for very old hardware and still runs fine on those (it is still currently in use). I am hired to write a new feature for this application and from the description of this feature, it should run flawlessly. But I can’t seem to find the right tools that will make my job easy. I badly want to use Android Studio because I am used to it. But Android Studio doesn’t have Android Cupcake system image for x86 processor (in those days, Android was written for ARM processor only). I have an x86 Android Cupcake system image that works (please don’t ask how I got it because it is a very long story). I want to setup an AVD and use this image as the underlying system image but I’m lost. Has anyone done this before?

I previously used vga=ask and vga= in Android-x86 6.0 to set the display resolution in VMWare and now in QEMU/KVM. Now I downloaded and installed Android-x86_64 (CyanogenMod 13), in QEMU, in UEFI mode, to a GPT partition, and the option doesn't seem to work anymore. Instead it outputs: > error: invalid file name 'vga=ask' There doesn't appear to be much information about this elsewhere. But I could find: - What happened to vga=ask in newer kernels? (Unix.SE) - Grub: Legacy 'ask' parameter no longer supported (Superuser) - android-x86_64-5.1-rc1.img --- change resolution (Android-x86 at Google Groups) I tried wm size 1280x720 (in terminal emulator as root) and it *kind of* works. the resolution appears to change, but the display area doesn't and it becomes a pain to read anything. So I had it reverted with wm size reset. I also tried UVESA_MODE=1280x720 and it also reports "invalid filename 'UVESA_MODE'". There's a proposed solution at the 3rd url (debug.drm.mode.force 1280x720) but it also didn't work. So, how to change the screen resolution properly? **[Update]** I tested with a new, non-UEFI installation and the vga kernel option works there.

This question might be redundant or a possible duplicate, but I use an NDK library that runs only on ARM devices. Is there a way I could know what percentage of Android devices my app can support based on CPU architecture just like these statistics on Android Platform Versions ? My goal is to ascertain the number of devices my app won't support.

Background: Device is Toshiba WT8-A Partition is FAT32 EFI grub and Android x86, all Windows partitions have been deleted. I have tried various installs from Marshmallow, Bliss and Nougat. All with varying successes. I can link to the files that I installed if requested. Marshmallow had many failures (ie GPS, WiFi, rotation etc) but would boot. Bliss had the same failures but would boot. Nougat Android x86 had none of those failures but would not boot. I can consider going back to Lollipop if need be. But firstly let me explain what is happening: I can install fully, including the grub and I can load Nougat and everything runs smoothly. If I then reboot, an endless loop occurs and Android does not load. I have looked at the command line and there is nothing to change. I tried a different EFI from a previous install and changed the targets, but I guess there is far more to change than just that, it did not work. I reinstalled fully Nougat and instead of starting Android x86 I rebooted (as one of the options) and Android rebooted. I updated the apps Google wanted to update, rebooted and then the endless loop occurred again. I can get to the point where it has detected Android and is trying to boot, but instead of booting, the tablet appears to switch off and start again. Does anyone have any solutions? Troubleshooting guide or help? TIA

If there's a link to a fix in another thread please tell me, but for now here's my problem I want to use Instagram on an android emulator to upload reels since my phone is dead and I'm under lockdown, Neither any of the Advertised emulators work, I tried Nox,Memu,Bluestacks and LDPlayer and all of them when I install instagram the app stop working. So back to the point; I installed VMWare and download an android X86 VMDK and iso image, both doesn't boot, The iso one restarts on detecting android x86 and vmdk one gets stuck on detecting android x86, I tried Virtual box, same result. How do I fix it? Specs: Amd Athlon II x45,4GB Ram,Nvidia GT 220

I have recently started running Android-x86 version 6.0-RC1 on my iMac, and I am considering making it on of my several daily drivers. There is one major issue however that is casting some doubt: I cannot seem to find a way to install flashable zip files. I have looked into a custom recovery, however apparently the directory structure of Android-x86 is too different from that of its mobile-device counterpart to run or even install one directly. I have attempted to use Chainfire's FlashFire, however it unsurprisingly does not work for similar reasons to the last method. I've read on a very short conversation in the XDA-Developers forum discussing this topic that a recovery would be relatively unnecessary because "you could simply use a lightweight Linux distro as a recovery". I am assuming from the wording that you would do this by booting a small Linux distro on the same machine, mounting the main image for Android-x86, extracting the flashable zip and running the install script contained within, however I am entirely unsure as to whether or not this method would work in practice, as I cannot find any more info on it. I need the ability to flash a flashable zip file as it is the only way as of current aside from using a custom recovery to install the Xposed framework on android, upon which I rely heavily for everything from personal conveniences to more manually configurable security functions to ease of development. Given Android-x86's inherent compatibility with virtually anything compiled to run on an Intel Atom or Celeron based android device the lack of Xposed is the one factor stopping me from being able to attempt custom ROM development, as well as starting to port several already under development projects that have been until now exclusive to BSD/Debian distros over to rooted Intel based android devices.
UPDATE: I've managed to mount the Android-x86 fs from a live GParted CD, and chroot to it, but when running flash-script.sh it starts the installer, and output the following error log: ****************************** Xposed framework installer zip ****************************** -Mounting /system and /vendor read-write /tmp/META-INF/com/google/android/flash-script.sh: can't create /dev/null: No such file or directory /tmp/META-INF/com/google/android/flash-script.sh: can't create /dev/null: No such file or directory /tmp/META-INF/com/google/android/flash-script.sh: mount: not found /tmp/META-INF/com/google/android/flash-script.sh: can't create /dev/null: No such file or directory -Checking Environment /tmp/META-INF/com/google/android/flash-script.sh: head: not found /tmp/META-INF/com/google/android/flash-script.sh: sed: not found /tmp/META-INF/com/google/android/flash-script.sh: cut: not found *Continues till line 121* Xposed version: ! Wrong platform: arm ! This file is for: ! Please download the correct package ! for your platform/ROM Now I'm assuming the reason this happened is that the Linux version I'm using is too lightweight and doesn't include the required programmes, however that does not explain the fact that the error log reports the system as ARM and claims the x86 version is incorrect for my platform given that I'm running a copy of Android-x86, so if anyone has insight, please supply!

I'm trying to use [Mobro](http://mobdro.com) on the Android SDK emulator. It only seems to install on ARM images. Is this a Mobdro limitation?

I have an x86 Android tablet, i had no issue with it until i did a factory reset. After the reset, i noticed Chrome didn't want to launch at all (it crashed on startup). I ran logcat and concluded the crash was related to libhoudini.so, which is the ARM support library for x86 devices. I extracted the APK from the device and realized it only had ARM native libraries in it. I did the same with other apps installed from the Play Store that i knew had native libraries and the result was the same, only ARM versions of the apps were getting installed. Again, this didn't happen before the factory reset. I manually downloaded and installed an x86 version of Chrome and it ran just fine, but does anybody know why is Google Play only downloading ARM versions of the apps? and is there a way to fix it? Google Chrome wasn't the only app that gave me issues, other apps with ARM libraries usually crash as well (not at startup, but they do occasionally crash without reason)

From the [official dashboard](https://developer.android.com//about//dashboards) or other resources, I cannot derive how many (if any) real commercially available devices with Intel CPU have Nougat or higher installed (or preinstalled). As Android developer, I want to know how many regular users may suffer if I choose not to support these devices (*due to [ffmpeg text relocations in assembly](https://github.com/WritingMinds/ffmpeg-android-java/issues/195) , if you want to know why*). I don't care about the emulators, or [android-x86](http://www.android-x86.org/) deeply respected community. These people have much better alternatives for video recoding.

Since Android is a forked Linux kernel plus software stack I am wondering whether there are any projects or ideas regarding creating a version of Android that can be added to a Linux system to allow a Linux system to run Android applications (compiled for, say, x86). Does anything like that exist or would it be possible? (I don't mean the emulator that comes with the SDK.)

I've read this question , and of course, there, the answer was "you can't, because the architecture is different." But that's not necessarily the case anymore. Many Android devices, like mine , now have x86 processors and also the specs to run Windows. Thanks to Remix OS and Android x86 , many x86 desktop computers (and tablets, etc.) now run Android. So, is there any way to virtualize Windows on Android if you have an x86 device?

Is there a way to download APKs with x86 native binaries (from google play)? With [raccoon](http://raccoon.onyxbits.de/) , I can download APKs directly, but it only add an Note 5 as a device. That causes, that the APKs I download only contains ARM binaries. I need the APK to run Apps in the AVD (which is much much faster if I use a x86 android)

I have read this and this question and I want to ask for some elaboration. I'm considering buying an x86 phone . I have some questions regarding compatibility issues. 1. I know that the majority of normal (non-root) apps will work without issue on x86, but I understand that there are exceptions. Apparently some apps use native ARM functions. How common is this? What are some examples of popular apps that won't run on x86? Can I get an idea of how widespread this problem will be? 2. Is it true that root apps are less likely to run than normal ones? How widespread is incompatibility with x86 in root apps? 3. I know that Xposed Framework can work on x86, but what about the modules? Are many of them incompatible with x86? If yes, how common is it?

On my old phone (Samsung I9305), I was able to enable the dropdown notification bar while the phone was locked by using this Xposed module. However, it doesn't work on my Zenfone 2. (Running 5.0, rooted with Xposed Framework.) Yes, I have activated the module, rebooted, activated the setting and then rebooted again. Several other Xposed modules do work. Maybe it's because of incompatibility with 5.0 or x86? In any case, is there any way to enable it on the lock screen? *By the way, the bounty notice says "credible sources." Obviously, that's **not** required. It just needs to work. Should probably have used to "draw attention" tag.*