[REQUEST] /e/OS Pie for LeRee R116 / Le 3

/e/OS Devices Request a Device
1

[REQUEST] /e/OS Pie for LeRee R116 / Le 3

Hello everyone,

I am looking for a developer ( @ronnz98 ?? ) interested in building /e/OS for the LeRee R116 / Le 3.

I’d prefer Android 9 / Pie based on LineageOS 16, as this seems to be the most mature source base available for this device family.

Device

  • LeRee R116 / Le 3

  • Qualcomm MSM8976 / Snapdragon 652

  • 3 GB RAM

  • 1920×1080

  • Target: /e/OS Pie / Android 9

Existing sources

Device tree:
Ampir — android_device_cool_msm8976-lineage-16.0

Kernel:
Ampir — android_kernel_leeco_msm8976-9.x

Vendor:
Ampir — vendor_cool

Additional reference:

itsMustafa — C106 device tree

itsMustafa — MSM8976 kernel

R116-specific information

The R116 is closely related to the Cool1 C103/C106, but there are known differences.

Most importantly, the LeRee audio configuration is different. Existing Android 9 development includes a separate LeRee mixer configuration and a microphone/audio fix using:

persist.vendor.audio.fluence.speaker=false
persist.vendor.audio.fluence.voicecall=false
persist.vendor.audio.fluence.voicerec=false
ro.vendor.audio.sdk.fluencetype=fluence
vendor.voice.voip.conc.disabled=false

The existing Ampir tree already contains the relevant Android 9 audio configuration:

Ampir audio sources

There is also historical evidence of the LOS 16 C106 build being tested on an R116.

/e/OS

The historical /e/OS Pie build infrastructure is available here:

/e/OS LineageOS 16 build integration

What I’m looking for

A developer who could assess the existing sources and build a proper /e/OS Pie ROM specifically for the R116, including the R116-specific hardware configuration.

Thanks!

1 Like
2

With some tweaking I could build:

e-0.23-p-20260816-UNOFFICIAL-c106.zip

However, I don’t think the chances are high that its actually working

1 Like
3

IMG_20260817_174255_322
IMG_20260817_174255_3221920×2560 1.07 MB
Hm not sure what went wrong here. Used the same recovery as my successful flash of crdroid based on Pie.

4

Please try this:

  1. Open the ROM file

    • Do not extract the .zip file.

    • Right-click the ROM .zip file.

    • Select Open with and choose 7-Zip or WinRAR.

  2. Find the installation script
    • Go to this folder path inside the zip:
      META-INF ➔ com ➔ google ➔ android
  3. Edit the updater-script file

    • Find the file named updater-script (it has no extension).

    • Drag and drop this file onto your desktop.

    • Open it with Notepad++ or your standard text editor.

  4. Delete the device check (assert)

    • Look at the very first lines of code.

    • Look for lines starting with assert or containing getprop("ro.product.device").

    • Delete that entire section from assert( until the first semicolon ); ends.

    • The file should now start with commands like ui_print or mount.

  5. Save and update the ZIP file

    • Save the changes to your text file.

    • Drag and drop the edited updater-script back into the open 7-Zip/WinRAR window.

    • Confirm that you want to replace the old file.

    • Close the zip program.

1 Like
5

This helped, it flashed fine now and booted up.

Couple of issues though: Wifi not working also Bliss Launcher crashes constantly, so that it’s impossible to do anything.

1 Like
6

you can try to install a different launcher via adb:

7

Yes, would need to sideload the apk in recovery, since WiFi is not working and can’t be enabled in initial setup.

8

I used now this sources: itsMustafa

e-0.23-p-20260817-UNOFFICIAL-c106.zip

9

@ronnz98

I managed to fix both issues locally:

  • Wi-Fi: The ROM includes wpa_supplicant.conf, but installs it to the wrong location: /system/etc/etc/wifi/. The Wi-Fi stack expects the file at /system/vendor/etc/wifi/wpa_supplicant.conf, where it is missing. Copying the existing configuration file to that expected path fixed Wi-Fi immediately.

  • BlissLauncher: the included foundation.e.blisslauncher 1.3.2 crashes on Pie because it tries to load android.graphics.BlendMode, which is unavailable on API 28. Replacing it with the F-Droid BlissLauncher 1.3.1 APK and clearing its app storage fixed the launcher crash.

3 Likes
10

This one won’t boot unfortunately.

11

Can you please provide instructions so other can follow it

12

Sure thing.

/e/OS Android 9: Wi-Fi fix + Bliss Launcher fix

:warning: Make a full recovery backup first. Boot into custom recovery, connect the phone via USB, and run all commands from a computer terminal (Windows/macOS/Linux) using ADB.

1. Fix Wi-Fi

The config file was already in the ROM, just in the wrong path.

adb shell mount -o rw,remount /system
adb shell mkdir -p /system/etc/wifi
adb shell mv /system/etc/etc/wifi/wpa_supplicant.conf /system/etc/wifi/wpa_supplicant.conf
adb shell chown root:root /system/etc/wifi/wpa_supplicant.conf
adb shell chmod 0644 /system/etc/wifi/wpa_supplicant.conf

Wipe Dalvik / ART Cache and reboot.

2. Replace crashing Bliss Launcher

Download Bliss Launcher 1.3.1:

https://f-droid.org/repo/foundation.e.blisslauncher_13100.apk

Save the APK file into the same folder where your adb/fastboot tool is located, then run:

adb shell mount -o rw,remount /system
adb shell mkdir -p /system/app/BlissLauncher
adb push foundation.e.blisslauncher_13100.apk /system/app/BlissLauncher/BlissLauncher.apk

adb shell chown root:root /system/app/BlissLauncher
adb shell chmod 0755 /system/app/BlissLauncher
adb shell chown root:root /system/app/BlissLauncher/BlissLauncher.apk
adb shell chmod 0644 /system/app/BlissLauncher/BlissLauncher.apk
adb shell restorecon -RF /system/app/BlissLauncher

Clear old launcher data (recovery can’t use “pm clear”)

adb shell rm -rf /data/data/foundation.e.blisslauncher
adb shell rm -rf /data/user_de/0/foundation.e.blisslauncher

Wipe Dalvik / ART Cache and reboot.

Both fixes survive a factory reset (stored in /system), but are lost if /system is wiped or reflashed. Clearing launcher data is only needed once, right after replacing the APK.

1 Like