add another android note

Handbook/src/misc/android-standalone-deployment/README.md

@@ -15,3 +15,18 @@ Here are a few important notes to consider:
 <div style="margin: 0 auto; width: 560px;">
 <iframe width="560" height="315" src="https://www.youtube.com/embed/zU8Nf4ssOO0" frameborder="0" allowfullscreen></iframe>
 </div>
+
+> [!CAUTION]
+> As noted in the
+> [v2.1.0 release changelog](../../appendix/changelog.html), since this release
+> enabling the Meta XR plugin, —and potentially the VIVE OpenXR plugin—
+> alongside the SenseGlove Unreal Engine Plugin in the same project will disrupt
+> the OpenXR functionality provided by the SenseGlove Unreal Engine Plugin,
+> rendering it unusable.
+>
+> `Although the SenseGlove OpenXR implementation is fully compatible with the IOpenXRHMD interface and the FOpenXRHMD XRTrackingSystem, it is not compatible with the FOculusXRHMD backend provided by the Meta XR plugin. The same issue likely applies to the VIVE OpenXR plugin. So, if these plugins are enabled in your project, the SenseGlove OpenXR will not function as intended, effectively breaking the plugin's functionality. It seems these plugins are necessary in order to make the fallback to the hand-tracking feature work on Android. While we may add support and compatibility with Meta XR and VIVE OpenXR plugins in the future, for the time being, if your project requires these plugins, we advise continuing with the v2.0.x release of the SenseGlove Unreal Engine plugin until this issue is addressed.`
+>
+> This also means that although the SenseGlove Unreal Engine Plugin is able to
+> produce FXRMotionControllerData for SenseGlove devices just fine, the
+> hand-tracking on Android won't work. So, the fall-back to hand-tracking
+> mechanism on Android is broken at the moment.