T2 Ultra cuts active recordings after 9–11 seconds

Ask aosu
1

My T2 Ultra is set to:

  • Intelligent Detection
  • Person Detection ON
  • Track Motion ON
  • Intelligent Detection REC Mode
  • Maximum event recording: 60 seconds
  • Battery: 100%

Despite this, recordings repeatedly stop after 9–11 seconds while the detected person is still visible and moving.

aosu has stated on this forum:

“If activity continues, the camera will keep recording in segments.”

That is not what my T2 Ultra is doing.

The problem is not the 60-second maximum. The problem is that the camera terminates an active event after ~10 seconds with no user control over minimum recording duration, post-motion recording, or event continuation.

My battery remains at 100%, so I also have no reason to accept aggressive battery-saving behavior at the expense of missing security footage.

Please answer directly:

  1. Is this behavior by design or a firmware defect?
  2. If it is by design, how is it consistent with AOSU’s statement that recording continues while activity continues?
  3. If it is a defect, when will it be fixed? Please provide an expected firmware/app update timeframe.
  4. Is there any current workaround that forces recording to continue while the detected person remains active?
  5. Will aosu add manual minimum/fixed recording duration or a Maximum Recording / No Battery Saving mode?

Until this is corrected, the camera can stop recording before a security event has ended and therefore cannot reliably perform its stated purpose of recording detected security events.

Please provide a specific technical response and, if this is a known defect, an expected date or timeframe for the fix.

2

Good day, Sharaz here. I’m not a part of AOSU, so I’m unable to answer some of your questions officially, but I may be able to answer a few and give you some insight as I also have the same device.

Firstly, your settings look perfectly reasonable. However, I actually think the Intelligent Detection setting may be related to what you are experiencing.

AOSU certainly has room to improve some aspects of their products, and this is something that could potentially be addressed through a future firmware update.

From my own experience, what may be happening is that the camera initially identifies the movement as a person and begins recording, but during the event the AI may stop classifying the subject as a person. When that happens, the camera may consider the event finished and terminate the recording even though, from a human perspective, the person is clearly still there and moving.

I have experienced something similar, although in my case it was almost the opposite situation. One of my cameras is located in a hilly agricultural area, where trees moving in the wind, birds flying past, and animals occasionally walking through the area can trigger the camera. I had it specifically configured for person detection, but the intelligent detection system would sometimes initially classify the movement as human activity and then later determine that it wasn’t a person. The result was that the recordings could be unexpectedly short.

Because of that, I would recommend trying Record Everything temporarily as a test. If the camera records the entire activity normally under that setting, it would be a good indication that the issue is related to the intelligent/person-detection logic rather than the camera’s ability to record.

The downside, of course, is that if the camera is in a high-traffic area, or there are animals, trees, vehicles, etc., you may receive considerably more recordings and notifications.

I would also recommend testing whether Track Motion remains active after the recording stops. If the camera continues physically tracking the person after the 9–11 second recording ends, that would be particularly useful information because it would suggest that the camera still considers the subject present but has ended the recording for another reason.

You could also try temporarily disabling Person Detection while keeping motion tracking enabled, just as another test. If the recording duration changes significantly, that would provide further evidence that the intelligent detection system is involved.

I obviously can’t confirm whether this is a firmware defect or intentional behavior, nor can I provide a firmware release date, since I’m not an AOSU representative. But given that you are seeing the recording stop while the person is still visibly present, I would definitely test the above before concluding that the 60-second recording limit itself is the problem.

If Record Everything records continuously without cutting off at 9–11 seconds, I think that would be a very useful finding to report back to AOSU, as it would give their technical team something much more specific to investigate.

3

Thanks, Sharaz. Your explanation makes sense, and the tests you suggested should help isolate whether the problem is specifically related to Intelligent Detection/person classification.

I’ll test Record Everything, check whether the camera physically continues tracking me after the recording has already stopped, and also try disabling Person Detection while keeping tracking enabled. I should be able to do that within the next few days and I’ll post the results here.

That said, even if your hypothesis is correct, I think it highlights a more fundamental design problem.

AOSU already provides recording-duration options of 20 or 60 seconds, but these are apparently treated only as maximum limits. Selecting 60 seconds does not mean the camera will actually record for 60 seconds. The camera can still terminate the event after 9–11 seconds based on its own detection logic.

What is missing is a fixed recording duration option.

For example:

Fixed Event Recording: 20 / 30 / 60 seconds

Once an event is triggered, the camera should record for the selected duration regardless of whether the AI later changes its classification, temporarily loses the person, or decides that the event has ended.

That would solve this entire class of premature-termination problems. The AI would still decide when to trigger the recording, but it would no longer be allowed to prematurely terminate an already-triggered security recording.

The camera is already capable of recording for up to 60 seconds, so I don’t see an obvious reason why users cannot be given this choice.

If battery life is the concern, AOSU could simply keep the current automatic behavior as the default and provide Fixed Recording as an optional mode with a warning that it may increase battery consumption.

In my case the battery remains at 100%, so I would absolutely choose reliable, complete recordings over unnecessary battery conservation.

So I’ll definitely run the tests you suggested and report back. But regardless of what those tests reveal, I think a true fixed-duration recording mode that cannot be shortened by AI/detection logic would be the simplest and most universal solution.

4

This early termination of recording is unnecessary I should be able to select the length of an event or at least override aht AI thinks is termination… How many more users need to complain about this trivial issue…

/ˌənˈnesəˌserē/