Mini review of Qubo Pro dashcam

There are various reviews on youtube, like this one, which give more details about this dashcam. I purchased it since it was one of the lowest priced dashcams with good reviews on Amazon. 

• The "audio notification" feature quickly turns annoying on our rough roads, it keeps chiming. So I turned it off via the app. 
  
  
• I used it initially with my existing 2 GB mini-SD card, but they recommend faster newer cards - maybe with a faster card, I won't see the frame skipping as seen in the "manual mode" recording below.
  
  
• If we download a recording, it is approx 1 minute long, as the reviews suggest. Around 30 MB. So, a 64 GB card can have around 2000 minutes or 30 hours of video.
  
  
• General recordings are FIFO auto-deleted, "Emergency" recordings, based on the accelerometer jerk detection, are not auto-deleted as quickly. We can set the number of "Emergency" recordings to keep, and it will auto-delete older ones only after that limit is reached.  
  
  
• The time-lapse feature captures 640 x 480 frames - an example embedded below. The audio track for the time-lapse is also created by the app. Apparently it is something which is licensed for Youtube uploads.

• I will add a video recorded in "manual mode" on the app below. During manual mode recording, I believe nothing is saved on the mini-SD card, and the app needs to be in the foreground with the mobile switched on. If we turn off the mobile's screen during recording, the recording is lost. We need to manually press the record icon and stop recording, only then the recording is seen in the app gallery. It is saved as mp4, but with a H265 or HEVC codec or something like that. Probably the dropped frames are due to my mobile phone's internal memory or CPU not being fast enough? Samsung Galaxy M12. 

• Edit: Found that the one minute clips recorded on the miniSD card have a small overlap of a few frames - 10 frames or so - each. So no data is supposed to be lost between clips. 1800 frames recorded in each segment. So, with the overlap, slightly less than a minute of unique content each. Filenames are like  
  VIDEO_30112022085501_1669778701951.mp4
  VIDEO_30112022085600_1669778760947.mp4
  So assuming a time-stamp in milliseconds, via Epoch Converter, 
  08:55:01.951 to 08:56:00.947 - so probably one second of overlap.
  
  
• Edit: Here are a couple of videos - one from the running car, one from the timelapse generated for an entire day of driving to Bangalore and back.
  Approx. six hours of driving = 6*3600 = 21600 seconds.
  The timelapse = approx. 3 minutes at 5 fps = 900 frames. 
  So, the timelapse was shot at approx. one frame every 30 seconds? Or some other scene-based method? Will try looking at the raw files and see.
  
  Looking at the files saved on the miniSD card, there is a folder called Timelapse created, with the saved files used to make timelapse videos. There are 5 timestamp files per minute. According to the timestamp of the file, once every 12 seconds. According to the filename, which is like
  timelapse_1669964034331.jpeg
  timelapse_1669964022031.jpeg
  subtracting the unix timestamps, 12.3 seconds between the frames.
  
  

Edit: More videos of the complete drive are available at this post.