Hao Lin

Hao Lin

A PhD student at Tsinghua University, who is interested in mobile operating systems and virtualization systems.

Include Intel Houdini in Android-x86

1 minute read

Published:

In this post I’ll document the necessary steps for incorporating Intel Houdini in Android-x86 9. Note that this does not work on Android 10+.

Prior methods of enable_nativebridge no longer works on Android 8+ of Android-x86 due to missing libraries for downloads. Fortunately, BlissOS has provided an alternative solution by extracting the Houdini libraries from ChromeOS. Here’s how it’s done.

1) Create a vendor/google folder at the root directory if necessary, and run git clone https://github.com/BlissRoms-x86/android_vendor_google_chromeos-x86 vendor/google/chromeos-x86

2) Add the following to device/generic/common/BoardConfig.mk.

  BOARD_SEPOLICY_DIRS += vendor/google/chromeos-x86/sepolicy
  -include vendor/google/chromeos-x86/board/native_bridge_arm_on_x86.mk

3) Remove the hal_drm_widevine.te file at device/generic/common/sepolicy/nonplat.

4) Add the following to device/generic/common/device.mk.

  $(call inherit-product-if-exists, vendor/google/chromeos-x86/target/houdini.mk)
  $(call inherit-product-if-exists, vendor/google/chromeos-x86/target/native_bridge_arm_on_x86.mk)
  $(call inherit-product-if-exists, vendor/google/chromeos-x86/target/widevine.mk)

5) Modify device/generic/common/nativebridge/nativebridge.mk to the following.

  #
  # Copyright (C) 2015 The Android-x86 Open Source Project
  #
  # Licensed under the GNU General Public License Version 2 or later.
  # You may not use this file except in compliance with the License.
  # You may obtain a copy of the License at
  #
  #      http://www.gnu.org/licenses/gpl.html
  #
  
  # Enable native bridge
  WITH_NATIVE_BRIDGE := true
  
  # Native Bridge ABI List
  NATIVE_BRIDGE_ABI_LIST_32_BIT := armeabi-v7a armeabi
  NATIVE_BRIDGE_ABI_LIST_64_BIT := arm64-v8a
  NATIVE_BRIDGE_ABI_LIST := x86_64 x86 arm64-v8a
  
  LOCAL_SRC_FILES := bin/enable_nativebridge
  
  PRODUCT_COPY_FILES := $(foreach f,$(LOCAL_SRC_FILES),$(LOCAL_PATH)/$(f):system/$(f)) \
      $(LOCAL_PATH)/OEMBlackList:$(TARGET_COPY_OUT_VENDOR)/etc/misc/.OEMBlackList \
      $(LOCAL_PATH)/OEMWhiteList:$(TARGET_COPY_OUT_VENDOR)/etc/misc/.OEMWhiteList \
      $(LOCAL_PATH)/ThirdPartySO:$(TARGET_COPY_OUT_VENDOR)/etc/misc/.ThirdPartySO \
  
  PRODUCT_PROPERTY_OVERRIDES := \
      ro.dalvik.vm.isa.arm=x86 \
      ro.enable.native.bridge.exec=1 \
  
  # ifeq ($(TARGET_SUPPORTS_64_BIT_APPS),true)
  PRODUCT_PROPERTY_OVERRIDES += \
      ro.dalvik.vm.isa.arm64=x86_64 \
      ro.enable.native.bridge.exec64=1
  # endif
  
  PRODUCT_PROPERTY_OVERRIDES := ro.dalvik.vm.native.bridge=libhoudini.so
  
  # ifneq ($(HOUDINI_PREINSTALL),intel)
  # PRODUCT_DEFAULT_PROPERTY_OVERRIDES := ro.dalvik.vm.native.bridge=libnb.so
  
  # PRODUCT_PACKAGES := libnb
  # endif
  
  $(call inherit-product-if-exists,vendor/intel/houdini/houdini.mk)

You May Also Enjoy

Step Debugging Android Native Framework in VS Code

4 minute read

Published:

Tracing the execution flow of Android Framework and debugging your own system components are significantly more convenient with the step debugging capability. It saves the trouble of frequently instrumenting the Android sources. This post will show how to enable this capability using LLDB and VS Code.

Building A Sideload Shell Program in Android

4 minute read

Published:

A normal Android app almost always comes with graphics interfaces (except for services) and limited privileges. In this post I’ll show how to write a program (in Java or C/C++) that runs in headless mode and possesses system-level privileges, which can be used to perform various tasks in practice such as system service monitoring, debugging and performance profiling.

Enable VoLTE/ViLTE on Pixel in Unlisted Regions

5 minute read

Published:

In this post I’ll document the steps to enable VoLTE/ViLTE (or their counterparts in 5G such as VoNR) on Google Pixel devices in unlisted regions, e.g., China. For Chinese operators (e.g., China Unicom), Pixel devices are already shipped with the corresponding Qualcomm modem mbn files, which are placed under /system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/China/. However, such files are not enabled by default, which renders VoLTE/ViLTE unusable in China.

Modify Board and CPU Info in Android-x86

less than 1 minute read

Published:

In this post I’ll introduce how to make your Android-x86 more like a real device by changing its board and CPU configurations. I’ll use the configurations of Samsung Galaxy S20 Ultra as example.