A black screen before the menu, after switching apps and during an active run needs different checks. Return the game/host tab to the foreground first; solo mobile play may have auto-paused and co-op intentionally waits for an inactive host. If the original also remains black, check save mode before reloading and record when the screen failed.

Choose the matching black-screen branch

Scroll sideways to read every column.

What you seeWhat to doSuccess / next step
Before login/menuOpen the original in another tab and follow the loading checks. Click once if the game asks to start; a silent audio track alone is not a failed render.A visible login/menu separates loading from account problems.
After app/tab switch or phone rotationReturn to the game and landscape. Resume a solo pause if shown; in co-op ask the host to return and finish any item/Bond choice.Scene and shared movement resume. If still black, test the original separately and record the trigger.
Freeze/black screen during an active runAllow the game to end/save the failed run if it presents a summary; verify the save indicator before closing. A forced iframe reload closes that document and cannot preserve guest memory.Saved summary/record can be checked; if absent, retain the exact time, device, browser and error for a report.

The old hour-long failures and the current endgame

October 11 reported an image-memory black-screen fix after an hour; October 12 fixed black screens, freezing and infinite leveling after 84 minutes and added crash-result saving. Those are dated fixes, not evidence that your current device has the same cause. October 13 removed minute-60 overtime and added Arceus at 30:00, so a current long-run guide should prepare for Judgment instead of diagnosing every failure as the old minute-84 bug.

Open the next useful page

Related pages