I was pleased to find that upon updating to the Android 14 preview, VK_EXT_dynamic_state + VK 1.3 were both supported. However when updating my application to take advantage of the new vertex binding call - 'bindVertexBuffers2EXT' - making use of both the dynamic stride and limit capabilities, I found that causes severe graphical corruption. Almost as if the GPU just skips some draws entirely and lets others through just fine. I can send an RDC capture or a demo app if necessary.
Pixel 6 Pro
Sounds good :) There were various issues with other dynamic state as well but I believe we caught them in time. That said there's always a small non-zero chance not all patches made it to all partners before ship -- so it might be a good idea to be on the lookout for issues and test without dynamic state if you see any weird behaviours. As far as I know only vkCmdBindVertexBuffers2EXT is the only one that is definitely problematic.