G-Force Settings — Frame Mapping, Fixed Orientation & Overload Alerts

Use this page when the G-Force panels are moving, but you want to know whether they are interpreting the vehicle motion correctly. These settings are shared by G-Force Monitor, G-Force Bowl, G-Bands, and G-Cross.

Best for

• users who want precise control over how the G-Force frame maps to their vehicle
• users who want repeatable results from a fixed phone mount
• users who want alerts only for stronger braking, acceleration, or cornering events
• users who see left and right or braking and acceleration reversed

Frame mode

Frame mode decides what the whole G-Force system calls Forward, Braking, Left, and Right. If this mapping is wrong, every panel can look active and still describe the wrong motion.

Use Auto-learned when the phone stays in its normal holder and you want the app to work out vehicle directions from real driving motion. This is the best starting point for normal use because you do not need to tell the app how the phone is mounted.

Use Fixed orientation when you want a deterministic frame immediately. This is the right choice when the phone stays in a known screen orientation in its holder and you want to lock that orientation instead of waiting for motion learning.

When Fixed orientation is selected, the same section shows four child controls:

• Current screen orientation
• Captured orientation
• Capture current
• Declared orientation

Current screen orientation tells you what the app sees right now from the rotating screen. This is only a live readout. It does not change the stored frame by itself.

Captured orientation is the fixed orientation currently stored for the G-Force frame. This is the value the app will use while Fixed orientation is active.

Capture current copies the live Current screen orientation into Captured orientation. Use this when the phone is already sitting in its real holder position and the screen rotation is correct. In practice, this is the fastest way to lock the frame.

Declared orientation lets you choose that same fixed orientation manually. Use it when you already know the correct orientation and want to set it directly, or when you are testing without rotating the phone into the mounted position.

How to verify Frame mode:

• acceleration should register as forward load
• braking should register as braking load
• a left turn should register left, not right

If those directions are wrong, fix Frame mode before touching alerts.

How to use Fixed orientation in real life:

• mount the phone the way you actually use it
• rotate the screen until Current screen orientation matches that mounted screen position
• tap Capture current
• do one safe acceleration, one safe brake, and one corner to confirm the directions are correct

If the phone is mounted correctly but the directions are still reversed, choose the right value in Declared orientation manually instead of capturing again and guessing.

Overload alerts

Overload alerts define when stronger force events should stand out. Start with directional thresholds. Only after the display already looks correct should you tune cadence, cooldown, sound, and haptics.

Enable overload alerts is the master switch. Leave it off while you are still correcting frame direction. Turn it on only after Forward, Braking, Left, and Right already make sense.

The four thresholds are independent:

• Forward threshold
• Back threshold
• Left threshold
• Right threshold

This matters because strong braking, strong launch, and side load often need different limits. A practical setup is to use lower values for the events you care about most and higher values for the ones you only want to flag when they become clearly aggressive.

Dwell controls how long the threshold must stay crossed before the alert is allowed to trigger. Use a shorter dwell if you want fast reaction to brief events. Use a longer dwell if you want to ignore tiny spikes and only react to stronger sustained load.

Cooldown controls how soon a new alert can happen after the last one. Increase it if repeated warnings feel noisy during one rough sequence. Decrease it if you want the app to react again sooner after a distinct second event.

Alert cadence changes whether the warning happens once or keeps repeating while the load is still unsafe.

• Single warns once when the unsafe event starts
• Repeat while unsafe keeps reminding while the load stays outside the safe range

Repeat interval only matters when repeating is enabled. It controls how often those repeat warnings may happen.

Haptic alert, Sound alert, and the selected alert sound decide how the warning is delivered. Start with haptics first. Add sound only if you need clearer feedback without looking at the screen.

Reset restores the whole shared G-Force frame and overload-alert setup to defaults. Use it if the frame logic and alert tuning have both drifted and you want to start from a known baseline again.

Real-life examples

• use lower thresholds when you want to catch harsh city braking or rough passenger-comfort events
• use higher thresholds when you only want to flag stronger cornering or test-run events
• confirm the setup with one safe firm brake and one sharper corner