Hub 3 data download from ML2 sometimes takes extremely long over the stock cable — best practices?

Hi Magic Leap team,

I’m using Magic Leap Hub 3 (v3.0) to download recorded data from a Magic Leap 2 headset over USB-C (stock/original cable). The data is generated by our own application and consists of saved image files (e.g., camera frames) stored on the headset. Download sometimes proceeds normally, but occasionally becomes very slow.

  1. Magic Leap Hub: 3.0
  2. ML2 OS version: 1.12.0 (API Level 29)
  3. Computer OS: Windows 10
  4. Connection: direct USB-C port
  5. Dataset: ~300 MB, the dataset may include many small image files

Are there known issues or best practices for transferring many small files (images) from ML2 via Hub 3 over USB-C?

Is there a supported faster method for bulk transfer of app data?

Thank you!

Jenny

Hey @lzy ,

This is a common issue with the way that ADB pulls many small files from a device.
For example, transferring 1 300MB file is much faster than transferring 1 300MB folder of many files (100s or thousands). The amount of data may be the same, but the performance is much different when dealing with 1 file vs many files at once.

One suggestion would be to take the many small image files and put them inside 1 single container like a .zip, .tar, or some other format. You would then need to handle decompression/extraction, but the transfer time should be much shorter.

Let me know if you have any other issues or if you find a solution that works for you!

Best,
Corey