Other than being annoying, is it affecting the hyperlapse itself in any way? If not, just get used to it. It will eventually get fixed, but minor annoyances like this that don't affect the recordings, assuming it doesn't, are a low priority among the allocation of DJI's resources.
Your point is well made. It was happening on my hyperlapses as well, and while I agree that the recording is what counts, I am hyperaware when I see behavior that is undesirable, and/or not working as designed. I generally don't waste DJI resources on a minor issue if functionality isn't affected (output video) or there is a workaround, like when the patient tells his doctor "it hurts when I do THIS." and the good doc replies, well, don't do THIS. I would also be hypervigilent that the behavior doesn't worsen, which could indicate a hardware root cause, at which point, it wouldn't be wasting DJI resources as much as utilizing them.
