Since v9.0, the Homey Android app only ships ARM native libraries (armeabi-v7a / arm64-v8a). This means it can no longer be installed on x86/x86_64 Android devices or emulators.
This is a regression from v8.x, which was pure Java/Kotlin and ran on any architecture without issues.
Why this matters:
Many users want to run Homey Dashboards on large screens (wall-mounted monitors, TVs, repurposed PCs) using the Android Emulator or Android-x86. The Homey web interface and homey.tv currently lack the Dashboard feature, so the mobile app is the only way to access it. The Android Emulator with Google Play system images uses x86_64, and without x86 native libraries, the app cannot be installed — Play Store shows “No compatible device” and sideloading fails with INSTALL_FAILED_NO_MATCHING_ABIS.
The fix is straightforward: include x86 and x86_64 ABIs in the app’s build configuration (e.g., adding ‘x86’ and ‘x86_64’ to ndk.abiFilters in build.gradle). This increases APK/Bundle size slightly but restores compatibility that existed in v8.x.
Steps to reproduce:
Create an Android Virtual Device (AVD) with a google_apis_playstore x86_64 system image (API 35)
Search for “Homey” in Play Store → “No compatible device”
Download Homey v9+ XAPK and attempt adb install → INSTALL_FAILED_NO_MATCHING_ABIS
For comparison: Homey v8.2.2 APK installs and runs perfectly on the same AVD
Environment:
Android Emulator 37.1.11, AVD with Android 15 (API 35), x86_64
Homey v9.9.0 XAPK — only contains armeabi-v7a split
Homey v8.2.2 APK — works fine (no native libraries)
This would enable a great use case: running Homey Dashboards on dedicated screens without buying additional hardware, using any PC with the Android Emulator.
I believe our support team has already contacted you, but I just saw your post and wanted to provide some additional technical context.
Homey v9.9.0 and newer include native libraries for armeabi-v7a, arm64-v8a, and x86_64. Only legacy 32-bit x86 is unsupported.
The XAPK used in your reproduction is likely the source of the installation error. XAPKs obtained from third-party sources often contain device-specific split APKs, and yours appears to include only the armeabi-v7a split. Installing this ARM-specific package on an x86_64 emulator will result in INSTALL_FAILED_NO_MATCHING_ABIS. This does not mean that x86_64 support is missing from Homey’s official Google Play App Bundle.
We do not currently provide App Bundles or universal APKs outside the Play Store. Homey relies on Google Play Services, and we do not officially support sideloading on other devices because we cannot guarantee that everything will work correctly. If you manage to get it working, that is of course great.
Installing Homey through the Play Store on an x86_64 device should work. If the Play Store itself reports that the device is incompatible, please contact our support team again with the exact AVD configuration and a screenshot so we can investigate that separately.
Thank you for the detailed response! I really appreciate you looking into this.
I followed your suggestion: uninstalled the old v8.2.2, cleared Play Store and Play Services data, and tried again. Unfortunately, the Play Store still shows the device as incompatible:
“Ez az elem nem kompatibilis az eszközöddel” (This item is not compatible with your device)
The device appears as “Google Sdk_gphone64_x86_64” in the device picker, greyed out.
Here is my AVD configuration:
Android Emulator: 37.1.11
System Image: Android 15 (API 35), google_apis_playstore, x86_64
Device model: sdk_gphone64_x86_64
Build ID: AE3A.240806.036
Resolution: 2560x1600, density 320
RAM: 4096 MB
GPU: auto (hardware accelerated, NVIDIA RTX 3060)
WHPX enabled
Bluetooth features present: android.hardware.bluetooth, android.hardware.bluetooth_le
The old Homey v8.2.2 (pure Java/Kotlin, primaryCpuAbi=x86_64) installs and runs perfectly on this same AVD.
I have attached:
Screenshot of the Play Store showing the incompatibility message
Full device properties (getprop output)
Full feature list (pm list features output)
I would be happy to provide any additional information or test a direct APK if you can share one with x86_64 support.
Thank you for the detailed response! I really appreciate you looking into this.
I followed your suggestion: uninstalled the old v8.2.2, cleared Play Store and Play Services data, and tried again. Unfortunately, the Play Store still shows the device as incompatible:
“Ez az elem nem kompatibilis az eszközöddel” (This item is not compatible with your device)
The device appears as “Google Sdk_gphone64_x86_64” in the device picker, greyed out.
Here is my AVD configuration:
Android Emulator: 37.1.11
System Image: Android 15 (API 35), google_apis_playstore, x86_64
Device model: sdk_gphone64_x86_64
Build ID: AE3A.240806.036
Resolution: 2560x1600, density 320
RAM: 4096 MB
GPU: auto (hardware accelerated, NVIDIA RTX 3060)
WHPX enabled
Bluetooth features present: android.hardware.bluetooth, android.hardware.bluetooth_le
The old Homey v8.2.2 (pure Java/Kotlin, primaryCpuAbi=x86_64) installs and runs perfectly on this same AVD.
I have attached:
Screenshot of the Play Store showing the incompatibility message
Full device properties (getprop output)
Full feature list (pm list features output)
I would be happy to provide any additional information or test a direct APK if you can share one with x86_64 support.
I verified that Google Play lists Google emu64xa as supported in Play Console. The issue is therefore not caused by a missing ABI.
Could you confirm whether Homey is also incompatible inside the AVD’s Play Store app, and whether Play Store → Settings → About → Play Protect certification reports the emulator as certified?
This should help determine whether the remaining issue is related to the specific emulator instance’s certification or integrity status.
Play Store incompatibility inside AVD: Yes, confirmed. The Play Store app on the AVD shows Homey as “Ez az elem nem kompatibilis az eszközöddel” (This item is not compatible with your device). The device appears as “Google Sdk_gphone64_x86_64” in the device picker, greyed out.
Play Protect certification: The emulator is not certified. Play Store → Settings → About shows:
“Az eszköz nem rendelkezik tanúsítvánnyal” (Device is not certified)
Additional details:
ro.boot.verifiedbootstate: empty (no value returned)
ro.product.model: sdk_gphone64_x86_64
Play Store version: 52.6.26-34 [0] [PR] 959312099
System image: google_apis_playstore, Android 15 (API 35), x86_64
So it appears the incompatibility is caused by the emulator’s uncertified status rather than a missing ABI. Is there anything that can be done on Homey’s side to allow installation on uncertified but otherwise compatible devices?
As a workaround, I was able to install Homey v10.1.0 successfully via Aurora Store (anonymous login, no device spoofing). The app runs fine on the x86_64 emulator with full Dashboard functionality, confirming that the x86_64 build works correctly.
As a workaround, I was able to install Homey v10.1.0 successfully via Aurora Store (anonymous login, no device spoofing). The app runs fine on the x86_64 emulator with full Dashboard functionality, confirming that the x86_64 build works correctly.
I’m glad to hear you got it working and that the Dashboard runs correctly! At this time, however, we are not planning to change our Google Play integrity or distribution policy to support uncertified devices or alternative installation methods.
