Swapchain errors and device lost when submitting secondary command buffer to render pass

When testing my applications on Android 15 with a Mali-G710 MP7 (Pixel 7), I noticed that any time I submit a secondary command buffer to a render pass I get the following validation error when presenting the swap chain:

VUID-VkPresentInfoKHR-pImageIndices-01430: Validation Error: [ VUID-VkPresentInfoKHR-pImageIndices-01430 ] Object 0: handle = 0xb400007be5014a90, type = VK_OBJECT_TYPE_QUEUE; | MessageID = 0x48ad24c6 | vkQueuePresentKHR(): pPresentInfo->pSwapchains[0] images passed to present must be in layout VK_IMAGE_LAYOUT_PRESENT_SRC_KHR or VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR but is in VK_IMAGE_LAYOUT_UNDEFINED.
The Vulkan spec states: Each element of pImageIndices must be the index of a presentable image acquired from the swapchain specified by the corresponding element of the pSwapchains array, and the presented image subresource must be in the VK_IMAGE_LAYOUT_PRESENT_SRC_KHR or VK_IMAGE_LAYOUT_SHARED_PRESENT_KHR layout at the time the operation is executed on a VkDevice (docs.vulkan.org/.../wsi.html

After a few frames, the device is lost. I haven't encountered either issue on any other platform when running the same tester going through the same Vulkan code paths.

Here is a screenshot from RenderDoc when running the same tester on Linux with the same configuration to draw with a secondary command buffer:

I have highlighted the barriers that perform the layout transitions. Here are the contents of the barriers themselves:

Some other things to note:

• When I start the subpass, I do provide VK_SUBPASS_CONTENTS_SECONDARY_COMMAND_BUFFERS.
• The secondary command buffer has both ONE_TIME_SUBMIT and RENDER_PASS_CONTINUE bits set.
• The inheritance info is set with the render pass, subpass index, and framebuffer.
• The render pass is a single subpass. I have tried with and without multisample resolve with no difference between the two.
• The swap buffers is waiting on the semaphore for the submit.
• I wait on fences before re-using any resources from a few frames ago. For command buffers, I reset the command buffer pool once it is no longer in use.

When debugging, I even tried waiting for the GPU to be idle before processing the submit, and I still had the same behavior. The following can avoid both the validation and device lost issues:

• Put drawing commands directly to the main command buffer rather than using a secondary command buffer.
• Omitting the submission of the secondary command buffer to the primary command buffer.
• Removing all draw calls from the secondary command buffer.

So far I haven't been able to find the source of the error for the image transitions, command buffer setup, or queue submission and swapchain presentation. I see that Mali-G710 was advertised as the first Mali GPU with native secondary command buffer support. Are there extra steps that I'm missing when the hardware support is used for Mali, such as extra barriers? Could this be a driver issue, perhaps android-specific with the swapchains?

The project is open source, I can share it and instructions to reproduce if need be.