01Why time from the cube instead of the keyboard?
A keyboard or touchscreen adds a human stop action after the cube is already solved. A Bluetooth cube reports the move that reaches the solved state, so timing and cube state share the same event.
That does not make every Bluetooth solve an official result, but it creates consistent browser practice and unlocks data that a conventional stopwatch cannot see.
02Direct connection without a companion app
Wake the cube, press Connect Cube and approve the browser device chooser. SupaKewber requests the GAN Bluetooth services needed for the selected model and retries common GATT handshake failures.
CubeStation and other smart-cube tabs should be closed first. Bluetooth Low Energy cubes commonly accept one active client, so a background app can prevent the browser from discovering services or receiving moves.
03What the move stream enables
The on-screen cube follows the physical cube, the scramble can be checked against the tracked state and the solve begins on the first post-scramble move. Cross, F2L and OLL completion are detected before the final solved state.
The result becomes a small telemetry record: total time, stage splits, move count where available, scramble, penalties and session position.
04Browser compatibility is part of the setup
Current Chrome or Edge on a supported desktop system and Chrome on Android are the safest choices. Safari and a standard Firefox installation do not expose the Web Bluetooth API required for direct pairing.
If Web Bluetooth is unavailable, SupaKewber keeps Manual mode available. The smart-cube browser compatibility guide explains platform-specific limitations before you troubleshoot the cube itself.