MoHadiShibli 745c16decf Diagnostic build: a package that shows why Control4Free does not start ...

For consoles it fails on, so a user can send screenshots instead of digging
out log files. `make C4F_DIAG=1` and `make -C launcher C4F_DIAG=1` (or
tools/build-launcher.ps1 -Diag) build Control4Free-<version>-diag.pkg, listed
as "Control4Free (diagnostic)".

Its app shows plain pages in place of the normal screen: a summary with a
verdict (firmware, GoldHEN, sandbox, auto-start files, the service and the
last start), the service log and the previous one, and the kernel log,
filtered and in full. The kernel log is read only in short windows, at
start-up, around a start and on Options, since Control4Free needs it to sign
controllers in. The pages are also saved to
/data/control4free/diag-report.txt, and to a USB stick when one is plugged in.

The payload says on screen that it started, and logs the kernel addresses
the SDK found and the process PayLoader runs it in.

2026-10-06 02:06:53 +03:00

..

build-launcher.ps1

Diagnostic build: a package that shows why Control4Free does not start

2026-10-06 02:06:53 +03:00

embed_client.py

Payload: system-wide virtual controllers through Sony's VDA API

2026-10-04 19:53:43 +03:00

embed_file.py

Launcher app: home-screen PKG to start, check and stop Control4Free

2026-10-04 19:53:45 +03:00

launcher_art.c

Logo: a DualShock 4 mark, and an icon with three lit controllers

2026-10-04 21:42:23 +03:00

make_icons.py

Keep the page on a home screen, say the address out loud, and say what went wrong

2026-10-05 02:31:50 +03:00

package_launcher.py

Diagnostic build: a package that shows why Control4Free does not start

2026-10-06 02:06:53 +03:00