README: screenshots of the controller connecting and disconnecting

.github/ISSUE_TEMPLATE/controller-report.md

@@ -0,0 +1,22 @@
+---
+name: Controller report
+about: Tried pad2c with a controller (working or not), or want support for a new one
+labels: controller
+---
+
+**Controller** (brand, model, connection: dongle / USB cable):
+
+**Console** (model, e.g. CFI-2114; firmware; payload loader):
+
+**What happened** (works / partly / not detected):
+
+**pad2c log** (`/data/pad2c/pad2c.log`, the lines from the last start):
+
+```
+```
+
+**For a controller that is not supported yet:** send `pad2c-probe.elf` with the controller plugged in, press every
+button one at a time while it runs, and paste `/data/pad2c/probe.log` here.
+
+```
+```

README.md

@@ -1,11 +1,60 @@
 # pad2c
 
-**Use an 8BitDo Ultimate 2C (2.4G dongle) as a second controller on a jailbroken PS5, next to your DualSense.**
+**Use an [8BitDo Ultimate 2C Wireless Controller](https://www.8bitdo.com/ultimate-2c-wireless-controller/) on a
+jailbroken PS5, as a second controller next to your DualSense.**
 
 pad2c is a payload for a jailbroken PS5. It reads the 8BitDo 2.4G dongle plugged into the console's USB port and
 shows it to the system and to games as a **virtual DualSense**. No Bluetooth is involved, so it never touches your
 DualSense's pairing.
 
+## Screenshots
+
+Switching the 8BitDo on and off, with pad2c running on the console:
+
+<p align="center">
+  <img src="docs/images/connected.jpg" width="45%" alt="The PS5 shows 'pad2c: 8BitDo connected' and asks who is using the controller">
+  &nbsp;
+  <img src="docs/images/disconnected.jpg" width="45%" alt="The PS5 shows 'pad2c: 8BitDo disconnected'">
+</p>
+<p align="center"><em>Left: switched on; the console asks who is using the controller. Right: switched off.</em></p>
+
+## Which controller
+
+| Controller | Supported |
+|---|---|
+| [8BitDo Ultimate 2C **Wireless** Controller](https://www.8bitdo.com/ultimate-2c-wireless-controller/) (the one sold for PC / Android, with a 2.4G USB dongle), through its dongle | ✅ |
+| 8BitDo Ultimate 2C **Bluetooth** Controller (the Switch edition, no dongle) | ❌ different product |
+| The Ultimate 2C Wireless over Bluetooth, without the dongle | ❌ not yet |
+| Other 8BitDo 2.4G dongles | untested: run `pad2c-probe.elf` and open an issue with its output |
+
+## Why this controller, and why the dongle
+
+**The controller** is simply the one I own: pad2c was made to play with it on my PS5, next to the DualSense. It is
+also a cheap way to get a second controller: a DualSense costs at least twice as much as the Ultimate 2C Wireless,
+which still has Hall effect sticks and triggers.
+
+**The dongle instead of Bluetooth**, on purpose:
+
+- **No conflicts.** The PS5 has one Bluetooth chip, and the system uses it for the DualSense. Sharing it from a
+  payload risks taking over or unpairing the DualSense, and the chip is laid out differently from one console model
+  to another. The dongle is a plain USB device: pad2c never touches the console's Bluetooth.
+- **Simpler.** No pairing, no Bluetooth stack to keep alive, no reconnection logic: the dongle and the controller
+  already talk to each other, and pad2c only reads what the dongle sends.
+- **Practical.** Plug the dongle into a USB port and switch the controller on. That is all.
+
+## FAQ
+
+**Can I use an 8BitDo controller on a PS5?** Not on a stock PS5: it only accepts its own and a few licensed
+controllers. On a jailbroken PS5, pad2c makes the 8BitDo Ultimate 2C appear as a DualSense.
+
+**Does it work in games, or only in the menus?** In games too. Give the controller its own console user (the console
+asks when you press Home) and it is player 2, like a second DualSense.
+
+**Do I lose my DualSense?** No. Both work at the same time. pad2c does not use Bluetooth at all.
+
+**Which firmware?** Tested on 13.60 (PS5 Slim). It needs a console that already runs a payload loader such as elfldr
+or Payload Manager; it does not jailbreak anything itself.
+
 ## Status
 
 | | |