Viewing Logs¶

By default, FIRERPA does not write any logs. If you need to view runtime logs, you can configure the service to write logs to a file in two ways. In most cases, you might have installed it via a Magisk module or an auto-start app. In these scenarios, you cannot set the log file by directly adding command-line arguments; you need to configure logging through properties.local. You can manually edit the properties.local configuration file or use the following command to write the log configuration.

echo logfile=/data/local/tmp/server.log >>~/properties.local

For users who start the service manually, since you run launch.sh directly (either manually or through other methods), you can also achieve this by adding the --logfile=/data/local/tmp/server.log argument to the command. This has the same effect as the method described above.

sh /path/to/server/bin/launch.sh --logfile=/data/local/tmp/server.log

Generally, we do not recommend enabling logging. This is because service logs are written in append mode, which, in extreme cases, might fill up your device's storage. Therefore, you may need to write additional script logic to automatically clean up logs to prevent such issues.