As it is built for KBOX4, all operations on busybox on Android 9 fail with a "bad system call" error message. There are a few other report of similar problems in other places -- KBOX4 is not the only thing that tried to use Busbox on Android -- but it isn't clear what the solution is, if there is one. This isn't a general problem with the Google Android NDK, because the Busybox unpacker -- which is built with the same NDK using the same switches as Busybox -- does run correctly (although the irritating distiction between "cleaned" and "not cleaned" versions still exists). However, the unpacker invokes a Busybox script to do the rest of the installation, and that fails.
I do not know if this is the same problem that others are reporting on Android 8.
I don't see any obvious solution here, except to debug BB laboriously, looking for the failing system call. Maybe it is something crucial that is broken, and maybe it can be worked around -- at this stage, I really don't know.
As it is built for KBOX4, all operations on busybox on Android 9 fail with a "bad system call" error message. There are a few other report of similar problems in other places -- KBOX4 is not the only thing that tried to use Busbox on Android -- but it isn't clear what the solution is, if there is one. This isn't a general problem with the Google Android NDK, because the Busybox unpacker -- which is built with the same NDK using the same switches as Busybox -- does run correctly (although the irritating distiction between "cleaned" and "not cleaned" versions still exists). However, the unpacker invokes a Busybox script to do the rest of the installation, and that fails.
I do not know if this is the same problem that others are reporting on Android 8.
I don't see any obvious solution here, except to debug BB laboriously, looking for the failing system call. Maybe it is something crucial that is broken, and maybe it can be worked around -- at this stage, I really don't know.