No, there is no limitation of that kind. I’m not clear on the issue you’re having.
The initial report was that there were only null hypotheses, which turned out to be due to a dependency in your app on using the old calibration callbacks, as far as I understand it. Then we discussed where to see the other callbacks. I explained that you can’t immediately suspend after starting the engine, since it has always been bad for recognition but now it doesn’t have any point, so that is going to have a negative effect on recognition.
Is this a new issue or a different issue, or the same issue deriving from starting and immediately suspending? Can you elaborate on it for me so I can understand what we’re specifically troubleshooting?