Thread: Cyclops cameras alerts stop after nüvicam snoozes, until fully restarted

Not sure what happened but I responded to the thread and post is no-where to be found... So reposting.

Originally Posted by Butters

@krzemien
That problem of yours intrigues me a bit. I wonder if it would persist if you were using the original files, i.e. purchased for and locked to your nuvicam. You can get the genuine files free for 30 days with no obligation to pay ongoing.

Intriguing, isn't it?
I did purchase yearly subscription back in 2016 or 2017 and should have these files squirrelled somewhere on my PC. So could use them.

The problem is the information about the cameras is definitely outdated and would be of no use for me today - I'm sure about it as things have moved on.
So I might see if I could get 30-days trial subscription and give it a go.

Originally Posted by Butters

Another thought is that perhaps your nuvicam supports Garmin's Cyclops Real-Time Updates which are done via Garmin's Smartphone Link or Drive App. If you have either active on your phone try with BT disabled or the phone off to see if the safety cams remain active after the nuvicam wakes up. Your "entitlement check with Mothership" suspicion may be well-founded.

That was my thinking as well, but having checked details here:

Code:

Please Login or Register to see the links

it would appear it's not the case as my device is not listed:

Cyclops™ Safety Cameras Updates and Cyclops™ Real-Time Updates are included for: Garmin Drive 51/52, Garmin DriveSmart 51/61/55/65, Garmin DriveAssist 51, Garmin DriveLuxe 51, zūmo 396/346, dēzl 780/785, Camper 780/785, DashCam 45/46/55/56/65/66, DashCam Tandem.

I might disable BT when I get back home today and see what happens.

Originally Posted by Butters

A point about "unlocked" Cyclops files, they are really de-crypted/un-encrypted rather than (traditionally) unlocked as such. The end result of course is that removing the encryption effectively "unlocks" them for use on many devices. Some modern Garmin devices can't use unlocked Cyclops files however because they have protected firmware. Could it be that your nuvicam's fw has been patched to remove MSV and GVS protections?

My device has never been patched in any such way - that I'm sure about.
I did fiddle with locked Cyclop files for some reason long time ago in the past - but normally I download and use only unlocked version, which - once copied to my satnav - just works upfront.

In either case I will keep you posted.
For some reason your earlier post was marked for moderation. I've removed it now to save duplication.
N.B. Please code external links, I've done it for you above.

Originally Posted by krzemien

................
That was my thinking as well, but having checked details here:

Code:

Please Login or Register to see the links

it would appear it's not the case as my device is not listed:

Cyclops™ Safety Cameras Updates and Cyclops™ Real-Time Updates are included for: Garmin Drive 51/52, Garmin DriveSmart 51/61/55/65, Garmin DriveAssist 51, Garmin DriveLuxe 51, zūmo 396/346, dēzl 780/785, Camper 780/785, DashCam 45/46/55/56/65/66, DashCam Tandem.

Yes i'd seen that too but because "Garmin is Garmin" it doesn't mean that other related devices aren't compatible, perhaps not completely and they work again only after a reboot.

.........
My device has never been patched in any such way - that I'm sure about.
I did fiddle with locked Cyclop files for some reason long time ago in the past - but normally I download and use only unlocked version, which - once copied to my satnav - just works upfront.

In either case I will keep you posted.

Then perhaps the bug would go away if the fw was patched with Universal Firmware Patcher (nudge nudge wink wink, google for it .... ).