Your setup
PS Vita model, system software or custom firmware, and the PSVITAMAN release or build version you installed. Reports should concern real PS Vita or PS TV hardware.
If you find it useful, you can support it. Support PSVITAMAN
Tell us what happened. Missing your PS Vita model, firmware version, or another technical detail? Write “I don't know” and send what you have.
Extract the ZIP and transfer the app to your console. There is no installer to run on your computer.
If your browser or antivirus shows a warning, keep protection enabled and send us the exact message or a screenshot. Console diagnostic logs are not needed for download problems.
Report a download problem (GitHub account required)
PUBLIC ALPHA DIAGNOSTICS
PSVITAMAN saves diagnostic information locally on your PS Vita storage. Nothing is uploaded automatically. Send the report anyway if you cannot find the log.
File name: PSVITAMAN-HW-DIAG.log
Where to find it: Open this location in VitaShell and copy the log to your computer:
ux0:/data/PSVITAMAN/PSVITAMAN-HW-DIAG.log
A clean START shutdown also exports a copy to ux0:/PSVITAMAN-HW-DIAG.log. After a crash, that root copy may be stale, so use the active log above.
Copy the log before opening PSVITAMAN again. The next launch starts a new log.
PS Vita model, system software or custom firmware, and the PSVITAMAN release or build version you installed. Reports should concern real PS Vita or PS TV hardware.
What you were doing, what you expected, what happened instead, and whether it repeats.
Attach PSVITAMAN-HW-DIAG.log whenever it is available. It is usually
the first evidence we check.
For song or cover problems: Include the song name, audio format, file size, sample rate, and bit depth. For cover problems, add the image type, pixel dimensions, and embedded image file size. Keep the affected file unchanged until the problem is understood.
Complete what you know and attach PSVITAMAN-HW-DIAG.log when available.
A GitHub account is required. Converting the affected file or replacing its embedded
artwork may remove useful evidence.
GitHub issues and attachments are public. Check the log before uploading it, and never attach copyrighted music. A clear description, the diagnostic log, and a photo or short video are usually enough.