Cyclops cameras alerts stop after nï¿½vicam snoozes, until fully restarted

**krzemien** · 17th October 2023,Â 07:29 AM

Hello

I posted the below in the sticky Cyclops thread only to be corrected by Mods - so apologies!

Quick two questions:

1. My satnav (nï¿½vicam) consistently stops alerting me about Cyclop cameras up until I restart it (rather than put to sleep, as you do). No big deal but rather annoying as I started using my car a bit more often recently.

Is it related to the Cyclop files perhaps (I only ever used unlocked versions as they just worked for me and are seen by the satnav upfront, although know how and can unlock them as/if needs be) - or rather (and as usual) it's buggy Garmin software that's at fault here?

2. Where do I find which satnav units might require unlocked versions?

Ta!

PS Just realised something... Would operation of my satnav (with these files on-board) be somewhat hindered by me having it connected to my phone by BT / to Internet at all times? Entitlement check with Mothership of some sort perhaps?
Or I am overcomplicating things?
EDITED TO ADD: I doubt the above matters as I turned the satnav off and on again yesterday prior to my trip back home, and all camera warnings worked as expected.
Also, satnav definitely does see these files at all times (as evidenced in About... menu) - the ones I am currently using are from sometime in August.

**Garman_Nuvi** · 17th October 2023,Â 10:19 PM

If your device is in [Only registered and activated users can see links. ] you will not get any warnings.
If your device is plug in to the correct Garmin vehicle power cable why put it in sleep mode it is to conserve battery power when your device is not in use

**krzemien** · 18th October 2023,Â 07:41 AM

Thanks for responding.

Firstly, what I meant by device sleep mode is: Having completed my trip, and with vehicle engine off (and power to the satnav cut off either), satnav counts-down 15 seconds or so before it turns off - but it does not actually shut down entirely, but 'goes to sleep' up until I start the engine again (and supply power to satnav), at which point it's ready to use almost instantly, as opposed to full lengthy start-up procedure that normally takes place (with Garmin logos etc.).
The above link describes the same thing.

And this seems to be the problem: once 'restarted' that way, Cyclops warnings do not happen subsequently en route at all, and the only way to restore their presence is to fully power-cycle the device (via power button, 5 sec etc.).

I do use device as intended, with power cable / cradle etc. When not in use, satnav is removed and kept in the stowage or at home. And normally I didn't bother with full shut down.

**asprin624** · 18th October 2023,Â 04:02 PM

I shut all my Garmins completely off every time.
Even after I completed my trip and it shuts down I still turn it back on and hold the off button till the turn off shows on the screen.
That way I know it is completely off.
It only takes a short time to come back on and find the satellites and I put in my trip and off I go.
Never had any problems with it not doing things correctly.
Most if not all Garmin GPS car units only last 1 hour with out external power.
Why even put it in sleep mode when not in use??

Seeing the way you use it does cause problems.......

**krzemien** · 19th October 2023,Â 08:56 AM

Thanks very much for your response.
The sleep mode kick in automatically and is no-brainer really if/when you regularly commute to and from work (as I started recently), and when device remains in the cradle throughout the day.
I take your point regarding the full shutdown but find it really unnecessary in the view of the above. Otherwise what's the point of this mode then?
When one takes infrequent strolls every now and then, or drives longer distances during holidays (as I did in the past) then that's another story, obviously, especially as I usually connect my satnav to my PC every now and then and get all trip's data downloaded to BaseCamp for posterity... Which actually fully shuts it down afterwards, hence me not experiencing this problem before.
Admittedly, sleep mode consumes battery a bit, and it wears with time, but then again: it's 7-year old device already, and I did replace its battery quite recently either.
So I take it it's the usual buggy firmware from Garmin that's the root cause then. I might give these guys a shout perhaps, when I have some time...

**Butters** · 19th October 2023,Â 09:41 AM

@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.

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.

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?

**krzemien** · 19th October 2023,Â 10:34 AM

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.

**Butters** · 19th October 2023,Â 11:07 AM

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 ....

).

**krzemien** · 19th October 2023,Â 06:57 PM

Many thanks again.

So I can confirm that satnav upon resuming back from sleep and with BT turned off in my phone beforehand misbehaved again, i.e. there were no camera warnings present on my trip back home.

Which doesn't surprise me really as this idea of checking the entitlements remotely by the device was a long shot really, and I doubt it's taking place.

I can also confirm that device still did see the relevant PoI files - as evidenced via 'About...' menu section - I specifically re-checked it.

I will look Universal Firmware Patcher up at convenient time - one is never too old to learn something new! - but at this stage will concentrate on investigating other PoI files I might have owned and used in the past (including the ones I used to have from Garmin).

Nonetheless my thesis still is that it's the fluffy Garmin's firmware (device software) that is the root cause here. I used to own 3590 before nï¿½vicam, and some of the errors I witnessed there are present in this device as well.

**Garman_Nuvi** · 20th October 2023,Â 08:45 AM

The easiest way to prove if your issue is "Firmware" related is to download a Free trial using Garmin Express ,you can only do this once per device and you will have to register your device with Garmin if you haven't already.

Spoiler: Cyclops trial