[Feature Request]: Select type of android sensor

[Koboo]

Feature Summary

Support selection of specific android sensor type

Detailed Description

Hey, first of all I want to thank you for creating this library! :)

My feature request is pretty straight forward: I read about androids sensor types and found out that there's a SENSOR_TYPE_GAME_ROTATION_VECTOR which acts pretty much the same as the SENSOR_TYPE_ROTATION_VECTOR but with the difference that it doesn't use the magnetometer to reduce wrong values caused by electromagnetic issues.

Potential Benefits

Less value issues caused by electromagnetic fields, because it doesn't use the magnetometer.

Possible Solutions

As far as I resarched: It should respond with the same values as the current SensorEvent. So you should only have to create an enum and make it selectable.

Docs: https://source.android.com/docs/core/interaction/sensors/sensor-types#game_rotation_vector

Alternatives Considered

No response

Additional Context

I can try to create a PR for that, but I'm not very familiar with flutter plugin development, so I would highly apprecicate this feature!

Preliminary Checks

• I've checked if this feature request does not already exist.
• I've considered and outlined any potential impact on existing functionality.

[tlserver]

Thank you for your feature request regarding support for the GAME_ROTATION_VECTOR sensor.

Unfortunately, this sensor type is specific to Android and does not exist on iOS. Since the plugin aims to support both platforms, and this feature cannot be implemented on iOS due to platform limitations, we won’t be adding support for GAME_ROTATION_VECTOR at this time.

If you need this sensor on Android, you might consider forking the plugin and adding Android-only support, but official support in this plugin will remain focused on sensors available on both platforms.

Thanks for your understanding!

[tlserver]

Hi everyone,
I’ve reopened this issue because I found a good iOS equivalent.
After some research, I discovered that Apple’s CMAttitudeReferenceFrame.xArbitraryZVertical can provide behavior very similar to Android’s GAME_ROTATION_VECTOR sensor.
I’ll look into adding support for selecting different reference frames / sensor types (with proper cross-platform handling) in the near future.
Thanks for the original request!