Report a problem
Check Troubleshooting first. If your problem is not there, report it on GitHub.
Open GitHub issues
To report a UMS9117 phone that has no target yet, follow Bring up a new phone and use the New phone report form instead.
What to include
Section titled “What to include”-
What you ran and what happened. The exact command and its complete output, including any error. Say what you expected instead.
-
The phone and build. The target, and the
--profileand--build-typeoptions if you used them. For a phone problem, say whether the phone had a battery and whether a microSD card was inserted. -
The FPLinux version. In a source checkout, the commit and whether you changed any files:
PC git rev-parse --short HEADgit status --shortFor a standalone archive, give the archive’s file name. For a launcher failure, include the relevant error from the exact log path printed by the launcher. Each launch creates a new log in its selected working data directory.
-
The failed stage of a build, check or test. If one of these commands failed, add the output of:
PC ./fplinux logs show latest --command build --failedReplace
buildwithcheckortestfor that command’s latest run. This also shows interrupted stages. -
Your PC. The operating system and its version: the Linux distribution or Windows version, and which archive host you selected.
For a problem on a running phone, also add the output of ./fplinux verify for the same target and options. It compares the selected runtime identity with the running phone; it does not test the phone’s hardware features.
Never attach
Section titled “Never attach”- The NAND backup
nand.binor any other copy of the phone’s internal storage. - Backups, prepared device-data groups or extracted firmware from your personal phone data store.
- Images or archives built with device data.
These contain your phone’s own data and its firmware. If a problem only occurs with device data, say which group you prepared: Bluetooth, external radio firmware and calibration, FM radio or audio profile.
For a new-phone report, the NAND geometry receipt and the generated board report requested by the form can be shared. They are reports, not copies of the NAND backup or prepared firmware; follow Bring up a new phone.
Review command output before posting it, and remove anything you do not want to publish, such as user names in paths.