Perhaps the decade of publications have never involved optical image stabilization in the loop.
What you could have, however, is a simulation of where the OIS moves the optical axis of the lens to, when given the gyroscope inputs. In control theory terms, an open loop observer. But that would need to be calibrated to each model of phone.
We needn't suddenly forget that every android phone asks you to wave it around in figure eights to calibrate the compass (and then still only seems to be accurate to within +/- 180 degrees). Making every video you take come out better on every Android device with sufficient CPU power after a few seconds of recording would be significantly preferable to "Only works on our devices, neener neener." To me, obviously, maybe not to Google.
https://www.microsoft.com/en-us/research/product/microsoftpi...
Aside from gatekeeping, what does any of this have to do with the Pixel 2? Why is the headline not "Fused video stabilization for any Android device with a camera"?
I mean, Microsoft published inertial image deblurring using entirely unintegrated devices in 2010 (https://www.microsoft.com/en-us/research/publication/image-d...), though I swear I remember seeing a poster from them earlier than that.
(Also, I can honestly say that I've never seen a video recorded on a phone that had motion blur or shutter wobble anywhere near as bad as what they show in their examples, so those examples seem contrived, but obviously it's great to have an algorithm that can handle exceptionally bad cases.)