Make sure Android Support is not running. Now use squashfs-tools again to pack the files to system.imgĬopy the new system.img to your phone.

Copy this system folder over your unpacked_image_path/system to replace the original files with the patched files. zip file which includes a /system folder. You probably only need the signature spoof patch. I chose the default settings which includes mock location patch and the signature spoof patch. So switch to Windows (unless you can find a Linux version of smalipatcher) and use the graphical UI to patch services.jar. Now you need to use SmaliPatcher to inject the signature spoof patch to the services.jar (which now includes the x file). Now you should have a file called services_x, you need to rename it to x and pack it into the services.jar file i path/to/services.vdex -ignore-crc-error Unpacked_image_path/system/framework/services.jarĭeodex the services.vdex with vde圎xtractor Unpacked_image_path/system/framework/oat/arm/services.vdex Get the following files and copy them to another folder Get the file /opt/alien/system.img from your phone and copy it to your PC (make a backup too) squashfs-tools (available for both Windows and Linux, I used the Linux Also you probably need to do this everytime there is an update for the Android Support and the system.img is changed. Many apps will crash if you install MicroG after them, but you can reinstall the apps and they should start working. Note that you should do this before installing Android apps. I just managed to get the signature spoofing and MicroG working on XA2 (3.0.1.14) with the new Android support so I thought to write a small how-to if others are interested. Modifying system.img is still required for mapsv1 API, but it's a bit simpler.Įdit: Check the answer by yeoldegrove for an automated script, thank you to yeoldegrove! Starting from 3.1.0 Seitseminen, the Signature Spoofing is built-in, there's no need for patching, only to activate it in Settings, and grant the Signature Spoofing capability in Android Settings. If some options are built as modules, add them to /etc/modules-load.Update : This is for Sailfish OS up to 3.0.3 Hossa.Ensure the kernel is build with CONFIG_VETH and CONFIG_NETFILTER_XT_TARGET_CHECKSUM.Ensure the kernel is built with puddlejumper,hwpuddlejumper and vndpuddlejumper binder nodes.Once libgbinder 1.1.20 is available in SailfishOS, the config file will no longer be required. However, different devices have different binder files, or they may be in another location such as /dev/binderfs/.įilenames are typically /dev/*puddlejumper and /dev/anbox-*binder and depending on the waydroid version, the aidl version needs to be 2 or 3.īecause of all these combinations, it is easier for a user to provide the config file for their device based on the description above, or the device parter can include the config file with their port. Which details the binder nodes and aidl version used for the waydroid release. As of Sailfish 4.4, libgbinder 1.1.18 is shipped.Ī config file is provided in packages waydroid-gbinder-config-hybris and waydroid-gbinder-config-mainline, adding a file to Note about waydroid-gbinder-config packagesĪ config file is required for libgbinder < 1.1.20. It is expected that you will be presented with an Android window. If using waydroid-runner, start it from the launcher. Click on the Waydroid icon launcher, this will start the fullscreen waydroid UI.Goto Jolla Settings > Waydroid and start the 'Session' service (you can choose to start it automatically).Reboot (container service will start next boot).See waydroid init -h for the list of available images.

As root (devel-su) run the command waydroid init which will download the required root filesystems.

Install waydroid-gbinder-config-hybris or waydroid-gbinder-config-mainline depending on the type of device you have.

Install waydroid-settings or waydroid-runner package.

The dedicatedĪpp can be installed via waydroid-runner package. In addition, as it is using nested Wayland composer, it isĮxpected to be slower than running directly on Lipstick. Slower to start than using pre-started Waydroid session via

With start of the app and closed with the app. In the case of the dedicated app, Waydroid session will be started It will not open again due to some issue in interaction between Of using UI via this approach is that if you close the UI in Lipstick, Will be opened with the launcher on applications grid. Starting the session on boot and start/stop session. When using Waydroid through systemd services, Waydroid settings areĪvailable as a module of Sailfish Settings. Recommended to run Waydroid using its full UI mode, UI is similar in Service (on boot or on request) or through dedicated app. You can run Waydroid session either by starting it as a systemd Waydroid Sailfish OS packaging User Usage

Apkinstaller for sailfish os