Arducam B0447C stuck at 640x480, low FPS, flickering on Galaxy Tab A8 with USB-C hub

Hi everyone, hoping someone can point me in the right direction here. I recently had to replace my Arducam USB camera because the old model (B019701) was discontinued, and the suggested replacement is the B0447C. On my Samsung Galaxy Tab A8 (connected through a USB-C multiport hub) the B0447C will only run at 640x480. If I try anything higher, everything gets extremely slow or just crashes. Even set at 30fps the framerate drops below 15fps as soon as there’s any movement in the frame, and I get these horizontal stripes flickering through the image.

Thanks for the details. Could you share a bit more about your setup? Which USB-C multiport hub are you using, and can you confirm whether the previous B019701 worked fine on the same Galaxy Tab A8 with the same hub? Also, have you had a chance to try the B0447C on any other device to compare?

Sure. The old B019701 worked perfectly at 1920x1080@30fps on the same Tab A8 with the same USB-C multiport hub. The new B0447C is where all the trouble starts. For reference, the same hub + B0447C works perfectly on my Samsung Galaxy Tab A7 Lite. Here’s a screenshot of what I’m seeing on the A8:

capture

Looking at this, the camera itself appears to be fine since it runs without issues on the Galaxy Tab A7 Lite. That points toward a platform compatibility problem with the Galaxy Tab A8 rather than a hardware fault with the B0447C. Unfortunately we don’t have a Galaxy Tab A8 in-house to reproduce this, which makes it tricky to pin down. One thing that would really help narrow it down: could you test the B0447C on a regular PC? If it misbehaves there too, that tells us something very different than if it only fails on the A8.

So I tested it across a few devices. On my Galaxy Tab A7 Lite, on a new laptop, and on several older PCs, I went through all the available modes and everything worked without the slowdown or the stripe flicker. It really only misbehaves on the Galaxy Tab A8, which is odd because the A7 Lite is actually the older, less capable tablet. Does anyone know what changed between the B019701 and the B0447C that could cause this on the A8 specifically? Here’s another capture from the A8:

capture

Thanks for running all those tests. To summarize where we are: the B019701 ran 1920x1080@30fps on the Galaxy Tab A8 without issue, but the B0447C on the same A8 + hub can only manage 640x480. Anything higher gets extremely slow or crashes, the framerate at 30fps drops below 15fps when there’s movement, and horizontal stripes flicker through the image. Meanwhile, the same B0447C + hub works perfectly on the Galaxy Tab A7 Lite, a new laptop, and older PCs across all modes. So this still looks like a platform compatibility issue specific to the Galaxy Tab A8. We’re continuing to investigate, and no fix or workaround is available yet, but if we find anything we’ll update here.