Userland: Bug report - Nothing works on MiBox Android 8.0

[RonCan]

Describe the bug

Simply trying to add any distro or application fails. The downloads completes but then I get the error tar: can't change directory to '/': Function not implemented after verifying assets

Steps to reproduce the behavior:

Fresh install of UserLand. Nothing special just try to add any distro or application

Device Information

Device: [Xiaomi MiBox].
Android Version: [Oreo, 8.0].
UserLAnd Version [2.3.8].
Not Rooted
Stock

Additional context

N/A

[corbinlc]

"Function not implemented" is almost certainly a PRoot error. We should be able to fix this. Can you go to settings within the app and enable PRoot debugging and set the PRoot debug verbosity to 9? Then can you try to add a distro and see the same error? After that there should be a PRoot_Debug_Log file on your device. Often it is /sdcard/PRoot_Debug_Log. If you can find that and send it to us, we should be able to help.

[RonCan]

@corbinlc thanks for a great tool. Please find the debug log here.

[EnderNightLord-ChromeBook]

found another Function Error:

tar: can't change directory to '/': Function not implemented (line 179... It's the only one.)

[RonCan]

@EnderNightLord-ChromeBook is there something I can do about this? Or is it something that needs to be fixed in the framework?

[MatthewTighe]

This is likely related to issues we've had with downloads and extraction. We're currently working on updating the process to follow a new flow that we hope will fix issues like this. Expect it to be released within a week or so.

[corbinlc]

Sorry, the new reference to this issue got me to look at this again. From the PRoot log, it looks like you device does not allow the chdir system call. We have not had to work around that one before in PRoot. That is a very basic system call. I suppose we would to replace chdir with open plus fchdir. Chaining system calls (turning one call into two or more) is ugly, but can be done.

[corbinlc]

@RonCan this took a long time for me to get to, understand and fix. My apologies. Recently a bunch of Samsung devices got upgraded to versions of Android that show this issue and so became of interest to fix it more urgently. See #1014 . I just fixed that issue in v2.6.3 (it may take a few hours until you see an option to update to that version). Please give it a whirl. Again, sorry I didn't dedicate the energy needed to solve this months ago.