Is your Pokémon clock correct on Miyoo Mini Plus?

Three documented time paths

The Onion Clock page describes these differences. This guide does not identify the motherboard revision in your unit, and you do not need to open the device to begin an observational check.

Set a baseline you can actually compare

Open Apps → Package Manager if the Clock app is not available, then use Clock to inspect and manually set the device date. Onion documents using the D-pad in that app. On Mini Plus, WiFi time is configured through Tweaks. Choose which time path you intend to rely on before the test, and record that choice.

Check the date as well as the hour. “The clock is roughly right” is not enough when the event you are investigating depends on a particular day. Write the complete visible date and time, then compare it with a separate clock.

A useful baseline contains four entries: displayed time before shutdown, actual elapsed time, displayed time after boot, and WiFi availability. Repeat under the conditions you normally use. If you mainly play away from home, a connected boot alone does not answer the offline question.

Check the device before the game

1. Back up progress and record Onion version, game build and selected core.
2. Read the date and time in the Clock app. Record whether WiFi time is enabled and whether you have a working connection.
3. Close normally, note the real elapsed time, then boot and inspect the clock again.
4. If relevant to how you use the device, repeat once with WiFi unavailable. Change only that condition.

Write down what happened instead of inferring the hardware from a single boot. An incorrect time suggests you should resolve the device-time setup before treating a Pokémon event as broken.

Worked example: an overnight offline boot

Neither result identifies the board revision by itself. What it does provide is an actionable observation: whether the device time matches the time you expected before opening Pokémon. Repeat the comparison while recording the same settings rather than changing the game and clock together.

Then inspect the exact game's event

Choose one event documented by that project's creator, with its location and conditions recorded. Verify the game build and whether you loaded Continue or resumed a state. Observe it under the current clock settings before changing dates or emulator cores.

Unbound's profile links to creator information about its daily-event adventure. A timed feature in one hack does not establish the schedule or reset rules of another. Check that project's documentation rather than applying a generic berry or day/night fix.

Do not repeatedly jump the clock while experimenting on your only save. If a creator provides an RTC recovery procedure, follow it for the exact release and preserve the original files.

Write an event check that somebody else can repeat

Use a single documented event rather than collecting several unrelated symptoms. Record its name, location, expected condition and the creator's instructions for your release. Include the trainer, relevant story milestone and any stated restriction. If the documentation does not state a reset time, leave that detail not documented.

Then describe the actual result in ordinary terms: the character was present or absent, an interaction was available or unavailable, or the game displayed a particular message. “RTC broken” is an interpretation; those observations are the evidence needed to assess it.

If you resume an old session, label that explicitly. If you instead reach the title screen and choose Continue, record that too. Do not compare two different launch paths and two different game versions while attributing every difference to the clock.

If time looks right but the event does not

Record the event's prerequisites, game version, emulator core and loaded progress. Compare the device clock with the hack's event prerequisites.

Check the save guide if a resumed state displays different progress from Continue. Use the GBC setup guide for Crystal-based projects; the game's title or region does not determine its platform.

What remains untested

No particular Mini Plus revision, offline accuracy measurement or Pokémon event was tested by Pocket Deal Radar. This checklist helps separate device time, loaded progress and game rules so you can report a reproducible result.

Separate the displayed clock from the event result

Record the handheld system time, the day or time shown inside the game, and the event you expected. Include the game build and whether you resumed a state or loaded an ordinary save. If you have not checked an event prerequisite, leave it as an open question. A displayed clock and an available event answer different parts of the problem.

For example: the game shows the expected day, but a timed encounter does not appear. That observation sends you back to the game’s event rules and progression requirements; it does not by itself show a clock failure. If the displayed time is wrong, record the discrepancy before changing anything. Repeating the same check with one change gives you a clearer comparison than repeatedly advancing the clock.

Use the local GBC session notebook to download a plain-text record of your attempt. Blank fields stay unrecorded; the notebook does not diagnose your setup.

Continue with your setup

Miyoo Mini Plus with Onion: full overview · All Pokémon handheld paths