GAN iCarry browser setup
The iCarry family spans more than one GAN protocol generation, but the practical setup is consistent: remove competing clients, wake the cube and grant SupaKewber browser access.
Direct answer
Close CubeStation, use current Chrome or Edge, enable Bluetooth, turn the iCarry several times and press Connect Cube in SupaKewber. Choose the GAN device in the browser chooser, wait for live moves and return the physical and virtual cubes to solved before the first scramble.
Step by step
Quit the official app completely and close any smart-cube website that was connected earlier.
Use SupaKewber over HTTPS in Chrome or Edge on a supported computer, or Chrome on Android.
Make several turns immediately before pressing Connect Cube. Replace or charge the battery first if the cube wakes unreliably.
Approve the browser chooser entry whose name begins with GAN, then keep the cube close during service discovery.
Confirm multiple face turns on screen, solve both states and only then follow the generated scramble.
Complete guide
Identify whether you have an original iCarry, iCarry S or iCarry 2 when possible. SupaKewber’s Gen2 driver covers the original and S family, while iCarry 2 uses a Gen3 move-history protocol with different packets.
Battery condition is especially important for a cube that seems to wake and disappear repeatedly. Weak power can look like a browser problem because the device advertises briefly and then drops during the encrypted handshake.
SupaKewber requests GAN service identifiers and manufacturer data from the browser chooser, then derives the encryption information needed to read the move stream. That work happens in the site rather than CubeStation.
The iCarry 2 protocol can request recent move history when packets arrive out of sequence. This helps recover short gaps, but a badly interrupted connection should still be reset before recording serious training data.
Turn R, U and F one at a time and compare each physical move with the 3D cube. A single matching move is encouraging; several consecutive moves confirm that notifications and ordering are stable.
If the states do not match, do not start a timed solve. Solve the physical cube, reconnect if necessary and re-check from a known solved position.
When the browser chooser cannot see the cube, wake it again, close other clients and place it within arm’s reach. When the chooser works but moves do not arrive, refresh, restart Bluetooth and reconnect.
For repeated disconnects during a session, inspect battery, sleep behavior, distance and radio interference. The dedicated disconnecting guide orders these checks from most common to least disruptive.
Quick answers
Yes. SupaKewber implements compatible GAN Bluetooth protocols directly in the browser.
It uses GAN’s Gen3 packet and move-history format rather than the earlier Gen2 format.
Not for pairing, but synchronizing both physical and virtual cubes to solved is recommended before scrambling.
Standard iPhone browsers do not expose the Web Bluetooth API required for this connection.
Practice with feedback
SupaKewber connects timing, smart-cube telemetry, training and online competition in one browser workflow.
Pair an iCarry