Firmware Version: v01.03.07.10
I had a glitch after recent firmware update. I stated recording with quickrecord, it recorded for a few seconds and then without any action from me it stopped, the screen went black but was still powered on, and after a few seconds the screen again displayed the scenery and OA4 was again ready for use. Looks like a restart took place. It happened only one time in 3 days of usage after update.

Also, until last update, the first switch on time and record operation of the day was slow and ercord icon not really in sync but I got use to it. Now I had a few instances where it happens for the first 2 consecutive quickrecords of the day. Just mentioning it in case. To avoid the inconvenience, on a new day or after long time no use, I just switch on the OA4 and

wait a short while before using the cam and it is allright.

PS: Happy Chirstmas season.

Hi there. Thank you for reaching out and we do apologize for the trouble. Please provide us with the operation video showing the issue so we can check it further. Keep us posted. We appreciate your cooperation.

DJI Paladin Posted at 12-25 00:20
Hi there. Thank you for reaching out and we do apologize for the trouble. Please provide us with the operation video showing the issue so we can check it further. Keep us posted. We appreciate your cooperation.

Hi Paladin,
A similar glitch occurred again today. I start a recording with quick recording, it looks like it started recording but very soon after the screen froze (the scene was displayed but was not updating anymore), after a sec or 2 the screen went black (not sure if the power went off or not). After 1 s or 2 the screen switched on again and I could use the cam normally. I noticed that this time no video was recorded but instead there is a file named ".DJI_20231226133425_0122_D.LRF.trinf" in the folder. No other files corresponding to 0122.
Again, it happened only one time today, like the other day.

sounds like a downgrade is needed to see if its actually bad firmware djji made or hte camera f ailed.

Fishycomics Posted at 12-26 04:03
sounds like a downgrade is needed to see if its actually bad firmware djji made or hte camera f ailed.

Hi Fish.
It happened 2 times in more than 400 clips (I usually take ~4 s to 15 s clips). So that is a rate of ~ 0.5%... No way I could make a video showing the problem.
It can be a problem if I start a long recording and do not check if the cam works, like when on neck mount...
There is that file I mentioned in previous post (.DJI_20231226133425_0122_D.LRF.trinf) but DJI does not seem interested in asking me to provide it to them so far... Could contain some hints...

Yaman-Python Posted at 12-26 19:06
Hi Fish.
It happened 2 times in more than 400 clips (I usually take ~4 s to 15 s clips). So that is a rate of ~ 0.5%... No way I could make a video showing the problem.
It can be a problem if I start a long recording and do not check if the cam works, like when on neck mount...

Yeah DJI will ask for it now that you mentioned.   its sales first, support last

Yaman-Python Posted at 12-26 01:33
Hi Paladin,
A similar glitch occurred again today. I start a recording with quick recording, it looks like it started recording but very soon after the screen froze (the scene was displayed but was not updating anymore), after a sec or 2 the screen went black (not sure if the power went off or not). After 1 s or 2 the screen switched on again and I could use the cam normally. I noticed that this time no video was recorded but instead there is a file named ".DJI_20231226133425_0122_D.LRF.trinf" in the folder. No other files corresponding to 0122.
Again, it happened only one time today, like the other day.

Thank you for your response. The Trinf file is used for fixing a video when the video stops recording abnormally. Please try to insert and remove the microSD card when the unit is powered on or restart the unit to fix the video. After fixing, the trinf file will be deleted automatically. If the original video file still cannot be opened after the above operation is complete, please provide us the camera log with the exact date and time and the original file via Google Drive so we can check it further. Please keep us posted. Thank you.

DJI Paladin Posted at 12-28 05:00
Thank you for your response. The Trinf file is used for fixing a video when the video stops recording abnormally. Please try to insert and remove the microSD card when the unit is powered on or restart the unit to fix the video. After fixing, the trinf file will be deleted automatically. If the original video file still cannot be opened after the above operation is complete, please provide us the camera log with the exact date and time and the original file via Google Drive so we can check it further. Please keep us posted. Thank you.

Thanks for looking into this. I do not need the video from the trinf file. In fact it was probably interrupted so quickly after start that it was probably 1 s or less.
Please find documents in the shared folder below. Hopefully, you could look into what created the problems and fix it.
https://drive.google.com/drive/f ... JsSl8IK?usp=sharing

there is:
1- a log folder, created a short while ago
2- the trinf file mentioned above for the 2nd occurrence (26 Dec 13:34). No video for this.
3- a video recorded during the 1st occurrence (Dec 17 ~12:00). It was interrupted as described in the first post.

Yaman-Python Posted at 2023-12-28 17:09
Thanks for looking into this. I do not need the video from the trinf file. In fact it was probably interrupted so quickly after start that it was probably 1 s or less.
Please find documents in the shared folder below. Hopefully, you could look into what created the problems and fix it.
https://drive.google.com/drive/f ... JsSl8IK?usp=sharing

Thank you for the information provided. We will now coordinate this with our relevant team for further investigation. We will keep you posted once we receive an update. Thank you for your understanding.

Yaman-Python Posted at 2023-12-28 17:09
Thanks for looking into this. I do not need the video from the trinf file. In fact it was probably interrupted so quickly after start that it was probably 1 s or less.
Please find documents in the shared folder below. Hopefully, you could look into what created the problems and fix it.
https://drive.google.com/drive/f ... JsSl8IK?usp=sharing

Hello there, Yaman-Python. Kindly please provide us a picture showing your SD card (the side of the model and speed) so we can proceed with the investigation. Please keep us posted. Thank you for your cooperation.

DJI Paladin Posted at 1-3 19:10
Hello there, Yaman-Python. Kindly please provide us a picture showing your SD card (the side of the model and speed) so we can proceed with the investigation. Please keep us posted. Thank you for your cooperation.

Hi. Here it is:

Yaman-Python Posted at 1-3 23:12
Hi. Here it is:
[view_image]

Thank you for keeping us posted. We will keep you posted once we receive an update. We appreciate your patience.

Hello there. We appreciate your patience. Can you please provide us with a third-party view showing the abnormal interruption process so we can proceed with the investigation? We understand that the issue only happens occasionally but we need to have the video to proceed with the analysis. Lastly, if you have other SD cards, please try to test them to see if the issue occurs. We appreciate your understanding and support.

Keeping you posted!
It happened again, around 2 times since my last post here, which is a very low % of times given the 100s of clips taken, but 2 times in the last weekend. Maybe low temperature is a factor. I also had a couple of times this weekend where the cam, after stopping a quick recording, would take a few seconds before turning black and showing the countdown (longer than usual).