The code implementation has serious performance issues

[proxiti]

Every rememberXXXSensorState has performance issue, here is demo:

@Composable
fun Demo() {
  val state = rememberGameRotationVectorSensorState()

  SideEffect {
    Log.e(TAG, "recompose") // infinite recomposition
  }
}

Any state will trigger infinite recomposition, which is not correct. I found the issue comes frome here:

val gameRotationVectorSensorState = remember {
        mutableStateOf(
            GameRotationVectorSensorState(...)
        )
    }

LaunchedEffect(key1 = sensorState, block = {
        gameRotationVectorSensorState.value = GameRotationVectorSensorState(...)
    }
})

return gameRotationVectorSensorState.value

It's incorrect to reassign the state value before return statement, every reassignment will trigger a recomposition even no component reference this state value.

[proxiti]

Especially for high-frequency collected data, I cannot skip recomposition to optimize performance, such as using lambda expressions to pass data, which causes the phone to overheat severely.

[proxiti]

A good way is to put the logic (before the return statement) in the state holder, and also put the sensor data in the state holder. Then exposed rememberXXX like this:

fun rememberGameRotationVectorSensorState(...) = remember {
  GameRotationVectorSensorState(...)
}