Return to Answer

Apparently, this is now an Android SELinux security feature -- mounts initiated from most processes are not visible to other processes. See this answer.

A related Android kernel development thread suggests replacing an uneeded system service (e.g. /system/bin/debuggerd) with a shell script that runs the desired mount command. This you'd launch with start debuggerd.

Update: This did work for me, after a reboot.

Apparently, this is now an Android SELinux security feature -- mounts initiated from most processes are not visible to other processes. See this answer.

A related Android kernel development thread suggests replacing an uneeded system service (e.g. /system/bin/debuggerd) with a shell script that runs the desired mount command. This you'd launch with start debuggerd.

Update: This did work for me, after a reboot.

Apparently, this is now an Android SELinux security feature -- mounts initiated from most processes are not visible to other processes. See this answer.

A related Android kernel development thread suggests replacing an uneeded system service (e.g. /system/bin/debuggerd) with a shell script that runs the desired mount command. This you'd launch with start debuggerd.

This did not work for me. However, I simply added my mount command to the end of /init.rc, and the mount was visible system-wide on bootup.

If you have init.rc and want more flexibility, you might be able to launch a daemon from it to execute mount commands received via IPC. But I'm not familiar with SELinux's house rules.

Apparently, this is now an Android SELinux security feature -- mounts initiated from most processes are not visible to other processes. See this answer.

A related Android kernel development thread suggests replacing an uneeded system service (e.g. /system/bin/debuggerd) with a shell script that runs the desired mount command. This you'd launch with start debuggerd.

Update: This did work for me, after a reboot.

Apparently, it is now an Android SELinux security feature that mounts initiated from most processes are not visible to other processes, according to this answer.

A related Android kernel development thread suggests replacing an uneeded system service (e.g. /system/bin/debuggerd) with a shell script that runs the desired mount command. This you'd launch with start debuggerd.

Neither of these options worked for me. However, I simply added my mount command to the end of /init.rc, and the mount was visible system-wide on bootup.

If you have init.rc and want more flexibility, you might be able to launch a daemon from it to execute mount commands received via IPC. But I'm not familiar with SELinux's house rules.

Apparently, this is now an Android SELinux security feature -- mounts initiated from most processes are not visible to other processes. See this answer.

A related Android kernel development thread suggests replacing an uneeded system service (e.g. /system/bin/debuggerd) with a shell script that runs the desired mount command. This you'd launch with start debuggerd.

This did not work for me. However, I simply added my mount command to the end of /init.rc, and the mount was visible system-wide on bootup.

If you have init.rc and want more flexibility, you might be able to launch a daemon from it to execute mount commands received via IPC. But I'm not familiar with SELinux's house rules.