The package name, the signed certificate fingerprint and the current version number are operator-controlled and not published in this guide. The desk states the install steps, the device matrix, the failure modes and the path back to the install page. Anything else belongs on the operator's install module.
Read the failure mode before the step. If the failure mode matches what you have already seen, jump straight to the recovery line.
Tap PLAY NOW or visit /Login/playnow. The operator's site opens on the install module with the rs9 download entry. Likely failure: the link opens a non-install page or the install button is missing. Use the back button and try again from the hero, or open the contact desk for a fresh link.
On Android 8 and above, Settings blocks unknown sources by default. Open Settings, then Apps and notifications, then Special access, then Install unknown apps. Toggle the active browser (the one you used to download the APK) on. Likely failure: the toggle is greyed out. Open the browser's own Settings, find Privacy, and enable installs from this source there first, then return to Android Settings.
Open the Downloads folder or the notification shade and tap the APK. Confirm the package name matches the operator's source before tapping Install. Likely failure: "App not installed" usually means a previous rs9 build is on the device. Uninstall the previous build, not the new file, then retry the install.
The install flow asks for Storage and Notifications at first launch. Grant both; decline Camera, Microphone and Contacts unless the install page explicitly requests them. Likely failure: a later feature needs a permission the first launch skipped. Open Android Settings, find rs9, then Permissions, and grant the missing permission. The setting survives app updates.
The sign-in screen is the same on a returning install and a fresh device. Likely failure: credentials fail after a successful install. Use the live support desk rather than reinstalling; reinstalling does not reset credentials.
Older Android versions accept the install but drop features that newer Android versions support natively. The matrix below pairs the Android version with the first install decision a reader is most likely to hit.
| Android | First-install outcome | Known limit |
|---|---|---|
| 14 and above | Source toggle, package install and permission prompts work as documented | None observed for the current install flow |
| 13 | Source toggle is reachable from the install prompt itself | Notification permission is granted in two steps |
| 12 | Source toggle is reachable from the install prompt itself | Storage permission is replaced by Media access on some devices |
| 11 | Source toggle requires an extra step inside the active browser | Background restrictions apply to the deposit notification channel |
| 10 | Source toggle requires an extra step inside the active browser | Scoped storage may hide the Downloads folder in some file managers |
| 9 | Source toggle is reachable, but the prompt is a single-screen overlay | Full-screen intent prompts need an extra Settings visit |
| 8 | Source toggle is greyed out by default; toggle from the browser's own Settings first | Background activity limits apply to the live contest tab |
| 7 | Source toggle is reachable; install succeeds on the latest signed package | The deposit notification channel may be silent in Doze mode |
If the install stalls on a step above, match the symptom on the left to the recovery line on the right. If the recovery line sends you to the install page, the package on the install page has already been refreshed.
| Symptom | Recovery |
|---|---|
| "App not installed" after the source toggle is on | Uninstall the previous rs9 build, then retry the new APK install |
| Source toggle is greyed out | Open the active browser's own Settings, find Privacy, then enable installs from this source |
| "Parse error" or "There was a problem parsing the package" | The downloaded file is partial; re-download from the install page |
| "Insufficient storage" on a device that has free space | Clear the Downloads cache, then retry the install |
| "Signature mismatch" warning | Uninstall the previous rs9 build first; do not attempt to install on top of a different signature |
| Install succeeds, but the app shows a network error | Switch from mobile data to Wi-Fi; the install module opens a websocket that some carriers block |
| Sign-in fails after a successful install | Open the contact desk; do not reinstall |
After the install succeeds, the desk's other routes cover the rest of the journey. The links below match the most common questions a shortlisting reader asks after install.
The five-step journey from the first sign-in to the first deposit to the first contest decision.
Open → DecisionThe decision summary, the comparison table and the limit-of-evidence note.
Open → HelpWhat the live desk covers, what it does not, and the path to operator escalation.
Open →Every step in this guide has a paired failure mode and a recovery line. The install page at /Login/playnow is where the signed package lives.
Open the install page