[Ben]

I see the same issue, also on a Samsung (OneUI 8.0). I contacted INNOV support who basically shrugged (“it’s challenging for the app to achieve perfect compatibility across all devices”).

I’m guessing INNOV’s Android developers might not be across everything they ought to be; hopefully they’ll be able to sort it out. In the meantime, a workaround is to switch the phone to portrait orientation, this at least moves things around a bit to uncover some functions.

• This reply was modified 5 months ago by  Ben.

[Ben]

tl’dr: seems the K7 has problems with at least some >128GB cards.

After switching the SD Card from a 512GB TCELL to a SanDisk Max Endurance 128GB (both rated at V30/U3), and with recording interval set to 1 minute, I’m getting mostly reliable recording now. The dashcam doesn’t crash, but does skip 5-10s about once an hour or so.

I have made a few >1 hour long trips with the 128GB card and have had zero instances of the dascham ceasing to function. There are still instances where the camera glitches and skips about 5-10s at the end of a recording, this happens to about 1 in 100 recordings (about the same rate as with the 512GB card). I don’t see any pattern to the skips, other than it’s always ~5-10s missing at the end of a one-minute file. That’s not ideal, but at least it doesn’t stop completely.

Here’s one example where a video skip occurred (notice one pair of files is shorter than the others):

https://drive.google.com/drive/folders/1SgrwdAciAwDCNdZfFSj_PR_iPi54kF_O?usp=sharing

(FYI I am planning to change the mount for the front camera as it’s far too shaky, it’s currently using the supplied L-bracket but I’ll switch to a more solid bracket; I also need to clean the lens ;-))

drive.google.com

InnovK7 - Google Drive

InnovK7 - Google Drive

[Ben]

Alas, I have also seen this issue: the K7 was recording just fine for just over one hour, then stopped recording (front and back). Started up again after being turned off and on.

This is with a 512GB TCell High Endurance card; I can’t see it would be the card specifications as a) it has recorded for an over hour no worries, so clearly the card is sufficiently fast, b) plenty of people have been having the same issue with myriad different cards.

I’ll recheck connections/etc and make sure they’re all solid.

• This reply was modified 6 months ago by  Ben.

[Ben]

Thanks for the reply Hans.

I switched the camera to EIS recording, this is a little better in terms of vibration, I’ll leave it there and see how it goes.

Re. app: the app can only download one video at a time, vs. up to 6 at a time from the web server (and the app makes you click a few times for each download vs. the web server is one-click). I certainly appreciate the web server function, for me it’s the difference between “usable” and “unusable” !

Re. “emergency” videos and g-sensor: thanks for that tip, you’re quite right that the reason for the heap of emergency videos was that I misunderstood the G sensor sensitivity as for parking mode only; I turned it down to a lower value and only have the occasional “emergency video” now (Sydney roads are not great, potholes/etc can be pretty bad).

Re. track log: I was hoping there’d be a separate GPX file, that would be a good feature.

Overall I’m happy with the K7, though I’ll certainly be keeping an eye out for any new versions/models that have appreciably better nighttime image quality and stabilisation.

• This reply was modified 6 months ago by  Ben.

[Ben]

Great find – this means you don’t really need the app to download video. Once you’re connected to the camera’s wifi SSID, the camera is at http://192.168.1.254/.

There’s a very basic web interface that will allow you to download and delete videos.

[Ben]

If it were me, I’d pull the whole unit out of the bike and power it from a reliable 12V supply (e.g. car battery or high quality benchtop power supply). If it doesn’t work there it’s clearly faulty.

FTR, I have had issues with my K7 not working but have had the fewest issues when using a 128GB Sandisk Max Endurance SDCard. I believe the NVR is still crashing on hot days (>35C), but as we head into the Australian autumn that’s becoming less of a problem.

In other words, I’d check: 1) top-shelf dashcam-rated SDCard, 2) temperature.

[Ben]

SOLVED: the “wifi active duration” is buggy

This is indeed the failure: the missing 10s is correlated with the segment where the wifi would turn off. I disabled this (“wifi active duration=on”) and lo and behold, no missing bits.

So this appears to be a design/firmware bug as opposed to a hardware fault.

I wanted to try the 3 minute period too, but unfortunately my K7 NVR is now outright failing after a period of time. That is, separate to the “missing/dropping 10s” bug, I have a faulty unit; I expect that’s the root cause of the other issues I’ve been seeing as discussed in this thread: https://forum.innovv.com/forums/discussion/k7-randomly-stopping-and-restarting-during-rides/.

• This reply was modified 4 months, 1 week ago by  Ben.

forum.innovv.com

K7 randomly stops recording and restarts recording during rides - K7 Dashcam - INNOVV Forum

K7 randomly stops recording and restarts recording during rides - K7 Dashcam - INNOVV Forum

[Ben]

Small update: I’ve confirmed this is occurring across multiple cards (128 and 256GB Sandisk U3 Max Endurance), and regardless of whether or not the card is formatted in the camera. Over the last ~6 recordings (each of 25-30 mins), it’s always been only the 6th file that’s cut short (with one-minute intervals). I’ll switch that to 3 minute intervals and see what changes.

I haven’t done any longer rides over the last few weeks, so can’t tell if it’s _only_ happening in the initial period after boot, or repeats at some interval >30 mins. I hopefully will get a longer ride this weekend, will aim to update here after that.

INNOV support are implying the unit I have is defective, seems like a very odd hardware bug! I have to wonder if it’s widespread but too minor for most people to notice?

[Ben]

I was running with 3-minute intervals and was seeing the same kind of behaviour; “only” 5-10s missing only from the end of a file. I’ll have to recheck on the elapsed time/number of files.

@Hans , do you have a K7?

[Ben]

I just checked the orientation thing, and you’re right, the INNOV app is stuck on portrait when on the main app page; it seems to only respect the phone setting when in camera preview mode.

@INNOVV , it would be great to have the app UI fit within the phone UI, and also to handle landscape mode in all parts of the app.

[Ben]

I’m still working with INNOV support; I have noticed the issue pretty reliably occurs after ~4-6 minutes into each ride (this is with 1 minute recording intervals).

I guess nobody else is seeing the same problem? I’ll try another SD Card and see how that goes.

[Ben]

The missing seconds issue occurs regardless of card free space; the videos above were with the card just over half full after a reformat via the K7 app. The file sequence number gives it away: ~760 files x 102MB ea. = 78GB, on a 128GB card. The hiccup had occurred multiple times earlier in the ride too, after only a couple of hundred files.

It is true that an SDCard;’s sustained performance can vary as the card does its own internal wear levelling/etc, however this is the nature of the beast and the sort of thing that any dashcam would need to allow for.

I’m in touch with Innov’s support on this, if anything comes to light through that I’ll endeavour to update this thread.

• This reply was modified 5 months, 2 weeks ago by  Ben.
• This reply was modified 5 months, 2 weeks ago by  Ben.

[Ben]

The K7 functioned (mostly *) well on a 3.5 hour ride today; I made three changes:

1) image format back to 2K@30FPS (was 1080 stabilised / EIS); this is a slightly greater bit rate

2) interval to 1 minute (was 3 mins)

3) swapped cards to a SanDisk Max Endurance 128GB (V30/U3; same performance specs as the 512GB TCELL card)

So one of those appears to have “fixed it”; I’m guessing the card. I’ll keep this card installed and keep an eye on it.

(* mostly = a handful of files are about 5-10s short, e.g. 51s instead of 60s; no obvious reason)

[Ben]

Hi Hans,

> Did you follow the steps I described earlier?

Yep; I’m testing a Samsung SD Card now; given others have tried a variety of cards I’m not expecting a fix, but we’ll see.

> It’s also possible there’s a technical defect in the DVR. To rule out another component of the K7 causing the crash, you can disconnect the components individually (remote control, cameras, etc.) and see if the problem persists.

Seems peculiar that a peripheral would cause a crash. I’ve already seen the issue with the remote control disconnected, I guess I could disconnect everything and try only one camera at a time. I’m not sure what that would prove though.

> A power supply issue could also cause the DVR to crash.

It’s connected directly to power, acc and ground (the Speed 400 has a convenient 10A fused supply).

> Is the DVR getting enough cooling?

It’s mounted under the seat, and gets as much ventilation as could be expected from that. I would expect the K7 to be designed and built to handle this installation location as it’s pretty much the only option on a motorbike (and as per the instructions). Also, I see others have reported what appears to be the same issue at very cold temps.

Appreciate the pointers; I’ll report back with the different card.

• This reply was modified 5 months, 4 weeks ago by  Ben.

[Ben]

Unfortunately this problem is still occurring; same as described by Andrei at the start of this discussion.

For example, from today’s ride, here are the filenames (from the front camera only for easier examination; I have both cameras connected) that were saved to the SD card, and the interval between the file timestamps:

Filename			Filename timestamp	Filename sequence no.	Time interval
20251226123403_000068_F.MP4	2025-12-26 12:34:03	68	
20251226123703_000070_F.MP4	2025-12-26 12:37:03	70	00:03:00
20251226124003_000072_F.MP4	2025-12-26 12:40:03	72	00:03:00
20251226124303_000074_F.MP4	2025-12-26 12:43:03	74	00:03:00
20251226124603_000076_F.MP4	2025-12-26 12:46:03	76	00:03:00
(camera skipped 2 recordings here, started again all by itself)
20251226125503_000082_F.MP4	2025-12-26 12:55:03	82	00:09:00
(camera totally stopped recording here for approx. 30 mins, until after I parked and had lunch)
20251226142250_000083_F.MP4	2025-12-26 14:22:50	83	01:27:47
20251226142550_000085_F.MP4	2025-12-26 14:25:50	85	00:03:00
20251226142850_000087_F.MP4	2025-12-26 14:28:50	87	00:03:00
(camera skipped 4 recordings here, started again all by itself)
20251226144350_000097_F.MP4	2025-12-26 14:43:50	97	00:15:00
20251226144650_000099_F.MP4	2025-12-26 14:46:50	99	00:03:00
20251226144950_000101_F.MP4	2025-12-26 14:49:50	101	00:03:00
20251226145250_000103_F.MP4	2025-12-26 14:52:50	103	00:03:00
(camera skipped 3 recordings here, started again all by itself)
20251226150450_000111_F.MP4	2025-12-26 15:04:50	111	00:12:00
(camera skipped 1 recording here, started again all by itself)
20251226151050_000115_F.MP4	2025-12-26 15:10:50	115	00:06:00
(camera skipped 1 recording here, started again all by itself)
20251226151650_000119_F.MP4	2025-12-26 15:16:50	119	00:06:00
(camera skipped 2 recordings here, started again all by itself)
20251226152850_000127_F.MP4	2025-12-26 15:28:50	127	00:12:00
20251226153150_000129_F.MP4	2025-12-26 15:31:50	129	00:03:00

The filename sequence number appears to increment by 1 for each file written, the list above is the front camera only so should increment by 2. As can be seen above, the camera sometimes just skips recording files but starts back up again, and other times stops recording entirely until powered off and back on.

I’ve checked the recordings immediately preceding the missing files and they are all exactly 3 minutes as expected. This suggests the failure arose in writing the subsequent file to the SD Card.

In contrast, the file preceding the complete failure (seq. no. 82 above) is NOT a full 3 minutes, suggesting the NVR hard-crashed at the time.

I’ve checked all power connections, the fact the camera restarts reliably _strongly_ indicates the wiring is fine.

I’ve just switched to a different SD Card (a SanDisk), we’ll see how that goes but given others have been using different cards, I don’t see that as the problem

• This reply was modified 5 months, 4 weeks ago by  Ben.
• This reply was modified 5 months, 4 weeks ago by  Ben. Reason: formatting