Skip to content
Ziednaga edited this page Nov 3, 2026 · 18 revisions

IMS

5G not available

  1. Open Settings > System > TrebleApp > Misc features and enable Force Display 5G network.
  2. Dial *#*#4636#*#*, open Phone information and set the preferred network type to NR/LTE/WCDMA (NR is 5G).
  3. Turn mobile data off and on again.

The network settings will keep showing LTE as the preferred network type. Leave it as it is, the value set in step 2 is the one used.

No push notifications after a restore

After restoring app data or switching between Google Play services and microG, apps can keep a stale push registration and stop receiving notifications. On build 17.0.0-202611021750 or newer, open Settings > System > TrebleApp > Misc features and tap "Re-register apps for notifications". Apps are stopped, open each one once to get notifications again.

On older builds, run this in a root shell (adb root on a debug build, or su):

pm list packages -3 | cut -d: -f2 | xargs -n 1 -P$(nproc) sh -c 'rm -f /data/data/$1/shared_prefs/com.google.android.gms.appid.xml && am force-stop $1' _

MediaTek: apps have no internet access

Some MediaTek devices on kernel 4.14 / 4.19 ship a vendor kernel patch that breaks BPF map updates. Android's BPF-based networking, including the firewall and RestlessOS's per-app network permission, stops working: apps have no internet access even though they're allowed, or firewall rules don't apply.

This can't be fixed from the GSI, the bug is in the vendor kernel. Patch the kernel with mtk-bpf-patcher by R0rt1z2. There is also an APK version that patches on-device, untested by us. More details in the XDA thread and the README.

Back up your boot image before patching, see Backing up your device.

Fixing VoLTE in Exynos and MTK devices

Some Exynos or Mediatek devices can get VoLTE with "Alternative FlossIMS", an alternative build of phh FlossIMS which was forked and updated with new fixes and patches. You need build 17.0.0-202610101859 or newer.

How to enable it:

  1. Open Settings > System > TrebleApp > IMS Features
  2. Tap "Install IMS APK for phh FlossIMS"
  3. Select "Alternative FlossIMS"
  4. Done. Wait a few seconds and if it doesn't apply fully, reboot your phone.

If you don't want to use it anymore, it can be uninstalled through Settings > Apps > See all apps.

Problems with Alternative FlossIMS or wanting support for your device?

If you find bugs or calls/SMS/VoLTE aren't working, please report these issues on GitHub, with the right logs:

•https://github.com/clangsdorff/ims/issues

logcat -b all -d > /sdcard/imslog.txt
logcat -b all -d -v threadtime > /sdcard/imsverbose.txt           
logcat -b radio > /sdcard/imsradio.txt

#This command bellow requires to perform a call while its running:
logcat -b all -v threadtime > call.txt

It is possible to add support for more devices in the meantime: If VoLTE not working, for more devices just sharing logs is enough and helping the contributor with testing.

AOSP IMS stack

RestlessOS ships the AOSP IMS stack (com.android.imsstack), an alternative to FlossIMS that only needs the standard radio HALs. It's experimental and disabled by default. You need build 17.0.0-202611021750 or newer.

How to enable it:

  1. Open Settings > System > TrebleApp > IMS Features
  2. Turn on "Use the AOSP IMS stack"
  3. Reboot your phone.

If VoLTE doesn't show up after the reboot, your carrier config probably leaves it off. GSIs don't ship carrier IMS profiles, so the AOSP IMS stack doesn't register on many carriers until you force it:

  1. Open Settings > Network & internet > SIMs > (your SIM) > Carrier settings overrides
  2. Set "VoLTE / Vo4G availability" to "Forced available"
  3. For VoWiFi, also set "Wi-Fi calling availability" to "Forced available"
  4. Turn on "Enable overrides"

When enabled, it takes priority over any installed IMS APK. Turn it off and reboot to go back to FlossIMS.

If calls/SMS/VoLTE don't work with it, report on GitHub with the logs from Reporting issues and logs.

Padding

Status bar

By default RestlessOS ships a status bar and quick settings padding values to 0, if you (for example) find the status bar clock or battery icons being covered by the screen borders you can increase the start & end padding values in this way:

  1. Open Settings > System > TrebleDroid Settings > Misc Features > User Interface

  2. Set in the start or end padding related options a higher value than 0

For all of this options the values recommended are at least 30 for start padding and 2 for end padding. Each device has it's own screen diameters so the user must find the proper values for its device.

Once this changes are performed you must reboot your device in order to apply the wanted values.

User can set 0 as value if it wants to revert the previous changes.

Bluetooth

Bluetooth not working or crashing

Some devices have problems with Bluetooth: it crashes, doesn't turn on, or calls and media audio fail over Bluetooth devices. Try these options in Settings > System > TrebleApp > Misc features > Bluetooth:

  1. Try enabling Disable LE APCF Extended features. This fixes Bluetooth crashing on some devices.
  2. Enable Use System Wide BT HAL if calls or media audio don't work over Bluetooth.
  3. Open Bluetooth workarounds and select the one that matches your device's chipset or brand: Mediatek for MediaTek devices, Huawei for Huawei devices. Leave it on None otherwise.
  4. If you still have audio issues, try changing Set eSCO transport unit size. The available values are 0 (default), 8, 16, 24 and 32. There is no recommended value: the one that works depends on each device, so you have to find the proper one for yours by trying them one at a time, starting from the default.
  5. Test Bluetooth again after changing each option, and reboot your phone if the change doesn't seem to apply. Change one option at a time, so you know which one fixed it.

For Bluetooth headsets or headphones: Try also enabling this option in Settings > System > TrebleApp > Misc features > Use alternate way to detect headsets.

If none of these work, report it on GitHub with the logs from Reporting issues and logs.

Clone this wiki locally