Disable voice logs

I am somewhat worried that this file may be needed so I suggest not deleting the file, at least as a first attempt to save space.

You certainly could disable the file, then see if/how it affects the use of your nuvi. To disable it, what I'd do is rename the file to:

vpm_log_all.txt.disabled or maybe instead of .disabled, use your initials as in .ABC

since it will disable the file while also reminding you that this is the file you disabled when it comes time to re-enable it or to delete it.

In the old days, a single file of 48MB was large but given the map file now of over 2GB and voice files that are quite large (and there are seven TTS English language voices available), it's really not that big a file when it comes to space saving. Besides, when your nuvi runs short of room to install a map update or additional vehicles, voices, etc., Garmin Express will alert you to the option of adding a SD card for more space. Since the nuvi 67 is only a 4GB device, ( http://www.poi-factory.com/node/34375 ), you may already be using a SD card.

Thanks for the discussion of the file. I wasn't aware that there is such a file. Can you tell if the file is updated based on your spoken instructions, selection of destinations, etc. or is it a static file? If static, I wonder if it's updated with map updates.

Interesting. I just checked my nuvi 3597 which has voice command, etc. and I see no voice logs or voice log folder in either the voice folder or the .System/log folder. I wonder which Garmin models have this log, when they started adding it and what it does.

I don't know what that file does, so I would not delete it.

If you want you experiment, make sure you back it all up !

There has to be "something" similar on every Garmin that has a previous places option, from the "Where to" command.

The DriveLuxe 50 I just bought for my son has file /Voice/Logs/vpm_log_all.log. Note that it has an extension of .log rather than .txt as stated by terrenjen110. So I don't know if it has the same kind of content as the one identified in the original post.

This file seems to make an entry each time the device boots up and loads the voice file. Here is an example of the content:

I[2018/03/01 00:14:38] {22748848} [vpm_tts_log.c:vpm_tts_log_voice:198] New voice loaded.
Voice Language: American English-Samantha (TTS)
Version Number: 2.50
Filename: 0:/Voice/English_American_Samantha.vpm
Part Number: 006-D4445-00
Type: VPM_TTS2
VPM Language ID: VPM_ENGLISH (0)

While the purpose of this file is a mystery, I suspect you can safely delete it, or at least clear out the contents of the file. One possibility I thought about is that maybe it is something you can turn on or disable in the diagnostics menu. I may experiment with this sometime when i have time to tinker with it. If I discover anything useful, I will report back in this thread.

Thanks, alandb.

OK, I played around with this a little on the DriveLuxe. Here is what I found...

An entry is made in the /Voice/Logs/vpm_log_all.log file on a full power-on boot up. It does not make an entry on a soft boot from sleep mode. The time stamp in the log is UTC, not local time.

I tried various combinations of deleting. First I deleted the contents of the file (used Notepad to delete contents, then saved empty file). I also tried deleting the file and also deleting the entire Logs folder. In all of these situations there was no problem noted with boot up or operation of the device. The /Voice/Logs/vpm_log_all.log file (and folder) was automatically recreated on boot up if it had been deleted.

I looked for a way to turn the logging off in the Diagnostics menu. There is a logging option on the Diagnostics menu under Diagnostic Menu > Configuration and Settings > ASR Log Settings, That was already disabled on my DriveLuxe, so it is not what is triggering the Voice log. I looked for a way to turn off this logging, but couldn't find anything. It may be in there somewhere, but I didn't find it.

Since only a few bytes of data are added when you do a full power-on boot up, I don't see this as a real big problem. But if over time the file gets bigger than you want it to be, it would be easy to just go in and delete it.

Can you imagine a time when your log file could reach 48MB as the OP's file is? What is the size of your log file?

Given the few bytes added with a power-on boot, it's hard to see how your file could ever reach 48MB.

Terrenjen110, how do alandb's file contents compare with your contents? If truly a 48MB file, there must be an enormous number of lines of text.

Once again, Garmin has us flummoxed with a mystery.

My file was only 15 KB when I deleted it. But then this is a new (refurb) device that has never been used and only turned on a few times. And no, I can't see it ever getting to 45 MB.

I wonder if terrenjen110 has that ASR logging turned on in the Diagnostics menu, and if that setting logs all speech recognition text. If so, I could see that file growing in size if you do a lot of speech recognition. Still, 45 MB seems like a lot. Terrenjen110 said the file is named .txt instead of .log like my file. So maybe it is recording something completely different than what I observed.

When you type in an address.. where do you suppose this info is stored so you can use it later? in a *.log file I think. The "speech" the original poster wondered about surely is not his voice.. but a translation to text... same as what would be entered by adding an address manually... AND.. it is available to use by going to "recent" and re using it.

...I think Recently Found data is stored in inaccessible storage on a Garmin device, not in any user-accessible portion of storage like the .txt or .log files in question.

It's also interesting that there are maybe one or two files (depending on whether the OP and alandb are referring to the same thing or at least a file that serves the same purpose) on the newer devices but these files don't exist in a majority of Garmin devices in use today.

To me, it's still a total mystery.

[Later] Ah, found it:

http://www.poi-factory.com/node/46750

And since Recently Found only remembers the 50 most recent locations, I still question why the OP's .txt file would be so large.

Here is the content of my log file (just part of it).

The earliest information in the file contains spoken directions from mid 2017 which is when I purchased this unit. It seems to be recording every spoken directions.

VPM Language ID: VPM_ENGLISH (0)
I[2018/03/24 13:39:36] {014020f0} [vpm_tts_log.c:vpm_tts_log_voice:198] New voice loaded.
Voice Language: American English-Samantha (TTS)
Version Number: 2.50
Filename: 0:/Voice/English_American_Samantha.vpm
Part Number: 006-D4445-00
Type: VPM_TTS2
VPM Language ID: VPM_ENGLISH (0)
D[2018/03/24 18:16:03] {014020f0} [vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: In $USR_DISTANCE, turn right $USR_ON_NEXT_ROAD. (939)D[2018/03/24 18:16:03] {014020f0} [vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: In $USR_DISTANCE, turn right $USR_ON_NEXT_ROAD. (939)

D[2018/03/24 18:16:04] {014020f0} [vpm_tts_speak.c:speak_ext:809] Speaking phrase: In one half mile, turn right on tn=address West Jackson Boulevard tn=normal.D[2018/03/24 18:16:04] {014020f0} [vpm_tts_speak.c:speak_ext:809] Speaking phrase: In one half mile, turn right on tn=address West Jackson Boulevard tn=normal.

D[2018/03/24 18:16:22] {014020f0} [vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: In $USR_DISTANCE, turn right $USR_ON_NEXT_ROAD, then take the $USR_TURN_COUNT_ORDINAL left. (970)D[2018/03/24 18:16:22] {014020f0} [vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: In $USR_DISTANCE, turn right $USR_ON_NEXT_ROAD, then take the $USR_TURN_COUNT_ORDINAL left. (970)

D[2018/03/24 18:16:23] {014020f0} [vpm_tts_speak.c:speak_ext:809] Speaking phrase: In one quarter mile, turn right on tn=address West Jackson Boulevard tn=normal, then take the first left.
D[2018/03/24 18:16:23] {014020f0} [vpm_tts_speak.c:speak_ext:809] Speaking phrase: In one quarter mile, turn right on tn=address West Jackson Boulevard tn=normal, then take the first left.
D[2018/03/24 18:18:49] {014020f0} [vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: Turn right at the traffic light, then take the $USR_TURN_COUNT_ORDINAL left. (1143)D[2018/03/24 18:18:49] {014020f0} [vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: Turn right at the traffic light, then take the $USR_TURN_COUNT_ORDINAL left. (1143)

D[2018/03/24 18:18:49] {014020f0} [vpm_tts_speak.c:speak_ext:809] Speaking phrase: Turn right at the traffic light, then take the first left.D[2018/03/24 18:18:49] {014020f0} [vpm_tts_speak.c:speak_ext:809] Speaking phrase: Turn right at the traffic light, then take the first left.

D[2018/03/24 18:20:05] {014020f0} [vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: Turn left on Addison McCarr St.$USR_ON_NEXT_ROAD. (413)
[vpm_tts_parse.c:vpm_tts_parse:3773] Navigation phrase selected: Arrive on destination to ---- S. Wen Avenue on right.
D[2018/03/24 18:20:05] {014020f0}

Yikes!

Given this, I'm sorta liking alandb's earlier wonderings: I wonder if terrenjen110 has that ASR logging turned on in the Diagnostics menu, and if that setting logs all speech recognition text. If so, I could see that file growing in size if you do a lot of speech recognition.

And given alandb's experiments, if unsolvable, I'd be open to occasionally deleting the file (with proper backup if it's ever needed to be restored) and do a full power down, reboot since I wouldn't expect data from 2017 to be restored and the new file after deletion may initially be as small as alandb's.

A better solution may be to call Garmin Cust Srv by phone with the nuvi connected to a computer and have them take a look at what you're experiencing.

As I've said before:

The price of versatility is complexity.

It looks more like standard navigation prompts to me, not converted ASR text. It is probable that the reason I am not seeing these entries on my DriveLuxe 50 is that I have never used it to navigate since purchase (it is a gift for my son's upcoming birthday). I guess I should take it out for a spin to see if those navigation prompts start showing up.

It does explain how the file could easily grow to 45 MB (or more).

I contacted Garmin's phone support today and the representative informed me that the file is used to improve tts in new Garmin products like the Drive series and future Garmin products.

The full log file will be sent to Garmin when you opt in "data collection" in Garmin Express.

The most recent speech log will be sent even if you opt out of data collection.

So the agent told me I can delete the file before connecting to Garmin Express so a blank log file is sent instead of the log containing my trip data.

There is no way to disable since my unit is "vintage" according to Garmin and will be no more software updates to disable this.

TLDR: It is safe to delete. The log is created and sent to Garmin to improve its tts functionality in newer Garmin products. Basically, I feel like Garmin is running some research project on older units.

Thanks, a great report with info and help for you and now others.

The only surprise is that the phone support didn't go with the too-common "Sorry but that's proprietary info and I can't tell you about it." Kudos to Garmin as well.

I wonder how big the file can get. Maybe after the upload to Garmin, it deletes the old and starts a new file. I also wonder if the file is only created for those who opt in. I'll guess not and assume it's created regardless of opt-status.

I wonder if alandb opted in through GE, that his log would change from his simple voice used info to the full turn-by-turn results as you've experienced.

Thanks again.

My DS65 (w/alexa) had been not holding a charge due to a failing battery. I got brave and delved into the device's internals.

Replaced the suspect battery and spent some time checking out the microphone placement.

Then realized that the mics are hooked up to the main board with a ribbon cable attached to quick connect connector.

Flipped the lever, slid out the ribbon cable, closed the lever, taped over the end of the ribbon cable, tucked it out of harms way and put the device back together.

The device works fine, and the only logs now are from what would be given as directions to your destination.

No voice logs are generated for OK Garmin or Alexa.

But, you have no "OK Garmin, or Alexa. Or any eavesdroppers.

My eventual replacement, a DS86, was just as accommodating to the same surgery.

Haven't figured out how to quote another post properly, but I'll work at it.

Cheers