[compot-dev]

Docs only, follow-up to #256 after a device test on an Android 15 phone (TECNO, HiOS).

• docs/usage.md, Start on boot: when the app opens depends on when Android announces that it has started. On the TV boxes that is ~1 min after power-on; on the phone BOOT_COMPLETED reached the app 11 min 30 s and 11 min 51 s after two boots (the firmware's broadcast queue waits on a system receiver), and the app then opened by itself (the 1×1 overlay of Start on boot: an opt-in setting for boxes without a firmware autorun (#255) #256 let the start through). Allowing autostart in Phone Master did not shorten the wait.
• The lock screen and Don't keep activities: an app opened behind the lock screen is closed at once with that developer option on, so the home screen shows after unlocking.

No code change, no version bump.

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can keep summaries lean with Findings visible per group, which tucks the rest behind a View link

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document device-dependent start-on-boot delays on phones

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Explain that Android startup work can delay automatic opening for about 12 minutes on some phones.
• Clarify that autostart permission may be necessary but does not shorten the delay.
• Describe why a locked phone may show the home screen after unlocking when Don't keep activities is
 enabled.

Diagram

graph TD
  A["Device starts"] --> B["Startup queue"] --> C["Boot broadcast"] --> D["App opens"] --> E{"Locked and option on?"} -->|Yes| F["App closes"]
  E -->|No| G["App stays open"]

Loading

High-Level Assessment

Adding these observations to the existing Start on boot section is appropriate: the delay and lock-screen outcome are device-dependent behaviors, not app changes requiring a different implementation.

Files changed (1) +2 / -0

Documentation (1) +2 / -0

usage.mdClarify phone start-on-boot timing and lock-screen behavior +2/-0

Clarify phone start-on-boot timing and lock-screen behavior

• Documents that device startup work can delay the boot notification—and thus app opening—by about 12 minutes on some phones. Notes that phone autostart permission may still be needed, and that Don't keep activities can close the app behind the lock screen.

docs/usage.md