Sailfish OS for Fairphones devices

Hello !
I have the same behaviour as yours on my FP4, waydroid doesn’t start at all.
[17:53:29] Failed to get service waydroidplatform, trying again...

I asked IA for some help (let’s use the technology :wink: ) and after making me do some tests like those:

ls -l /dev/binderfs/
crw-rw-rw-    1 root     root      502,   1 Jun  4 15:30 binder
crw-------    1 root     root      502,   0 Jun  4 15:30 binder-control
drwxr-xr-x    3 root     root             0 Jun  4 15:30 binder_logs
crw-rw-rw-    1 root     root      502,   3 Jun  4 15:30 hwbinder
crw-------    1 root     root      502,   6 Jun  4 15:30 hwpuddlejumper
crw-------    1 root     root      502,   4 Jun  4 15:30 puddlejumper
crw-rw-rw-    1 root     root      502,   2 Jun  4 15:30 vndbinder
crw-------    1 root     root      502,   5 Jun  4 15:30 vndpuddlejumper
for mod in veth xt_CHECKSUM nf_conntrack_bridge br_netfilter; do
    devel-su modinfo $mod 2>/dev/null && echo "✅ $mod" || echo "❌ $mod";
done

name:           veth
filename:       (builtin)
✅ veth
name:           xt_CHECKSUM
filename:       (builtin)
✅ xt_CHECKSUM
❌ nf_conntrack_bridge
❌ br_netfilter
devel-su grep -q "binder_ioctl" /proc/kallsyms && echo "✅ Binder IPC present" || echo "❌ No Binder IPC"
✅ Binder IPC present

devel-su grep -q binderfs /proc/filesystems && echo "✅ BinderFS supported" || echo "❌ No BinderFS"
❌ No BinderFS

IA concluded that there is something wrong with the FP4 kernel:

1. Binder System Status

Feature Status Verdict
Binder IPC (binder_ioctl) :white_check_mark: Present Fully functional
Binder device nodes :white_check_mark: Present (binder, vndbinder, etc.) Correctly configured
BinderFS :x: Missing Requires workaround

2. Network Stack Status

Feature Config Status Verdict
CONFIG_VETH :white_check_mark: =y Virtual Ethernet supported
CONFIG_NETFILTER_XT_TARGET_CHECKSUM :white_check_mark: =y Checksum offloading enabled
CONFIG_BRIDGE_NETFILTER :x: not set Critical missing feature
CONFIG_NF_CONNTRACK_BRIDGE :x: Not found Breaks container networking

3. Key Findings from Config

CONFIG_ANDROID_BINDER_IPC=y # Core binder present
CONFIG_ANDROID_BINDERFS=y # Config says yes but not in /proc/filesystems?!
CONFIG_ANDROID_BINDER_DEVICES="binder,vndbinder,hwbinder,puddlejumper..." # Custom nodes


The Paradox Explained

Your kernel is compiled with BinderFS support (CONFIG_ANDROID_BINDERFS=y), but:

  1. Not showing in /proc/filesystems → Possibly disabled at runtime
  2. puddlejumper nodes exist → Hybris-style binder implementation
3 Likes