Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 5 of 5
  1. #1
    ☼ADMIN☼ SQLite db files explained
    catymag's Avatar
    Join Date
    Nov 2007
    light side
    Rep Power

    Default SQLite db files explained

    SQLite db files explained

    quoted from bacevedo from
    Please Login or Register to see the links
    I hope Brian doesnt mind, copied here coz it's interesting

    Spoiler: CLICK

    I have been playing with the SQLite db files on my 3750 and wanted to share some of the info with you all. I have seen on other forums where people are wondering where the nuTrends and myTrends data is stored - I think I have found their location.

    You have to go into the .System\SQLite folder. In this folder are 6 files with .db file extension. The files on my 3750 are listed below. Note: I copied the files over to my computer and used those copies to connect to.

    * D232800.db
    This appears to be the trafficTrends North America data, according to the garmin_metadata table in the db. It might also be just metadata that the system uses to find the actual data somewhere else on the nuvi. There is a table called SpeedProfile that has the columns SSID, TimeID and SpeedSamples. I don't know what the data means, but there is a lot of if there.

    * local_poi.db
    I think this one is storing the information when you rate a poi and possibly mark it as not valid, etc.

    * mlg_history.db
    This appears to store the ecoRoute data for your driving habits. The history table has columns like acceleration score, speed score, deceleration score, etc.

    * pre.db
    This appears to store the myTrends data and "pre" stands for prediction. There is a table in this db called prediction that contains the stats for its "predicted" routes.

    * system.db
    This db is used by the system to find the other tables. It has only one table called system, that has two rows. One points to D232800.db and has the description of trafficTrends™ North America. The other one just points to the mlg_history.db file with no description.

    * user_strings.db
    This is where the predictive text is stored when you enter in addresses or search fields. The table user_string contains the string_data column (i.e. Best Buy, San Diego) and the context column contains a numeric value that matches to whatever screen you were in when you entered the value. There is also a usage_count and time_stamp column, probably so it can remove old and unused values when some pre-determined amount of values are stored.

    To view these databases, I downloaded a free SQLite client from [Only registered and activated users can see links. ] (I downloaded the non-commercial Lite version for Windows, which is free.) In Navicat, you create a new "connection" for SQLite, give the connection a name (I used the name of the db file) and then enter the path of the db file (press the ... button to bring up a file dialog box). Don't change any other settings in any other tab and just press OK. Double click the newly created connection and your database will open, allowing you to see all of the tables and data inside.

    I am not sure if these are copies of databases that reside in memory or if these are the actual databases. I haven't tried changing data in them to see if the nuvi detects the changes.

    Have fun!

    You have to navigate to get to the good.

    Galaxy S5 Kitkat 4.4.2 / Nuvi1200->1250 / Nuvi3790T->34xx / Nuvi 2200 / Nuvi 66 / Oregon 600

  2.    Advertissements

  3. #2
    Junior Member
    Join Date
    Sep 2010
    Rep Power


    Much appreciated. I'll have a look at my 3760 db files as well...

  4. #3
    Join Date
    Nov 2012
    Rep Power


    the number of file in this directory is higher than the one presented in the initial message. I have these:

    03/12/2012 00:00 4,096 system.db
    03/12/2012 00:25 399,360 pre.db
    03/12/2012 00:06 398,336 pre.bckup
    27/11/2012 08:52 1,731,584 mlg_history.db
    29/11/2012 15:59 26,624 local_poi.db
    02/12/2012 13:51 22,528 user_strings.db
    02/12/2012 19:39 <DIR> temp
    02/12/2012 21:42 3,072 RecentStops.db
    01/12/2012 16:00 8,192 quick_search_list.db
    12/05/2012 15:55 1,062 3805304218.lpt
    27/11/2012 08:52 3,072 custom_where_to.db
    12/05/2012 15:32 2,200,576 006D213000.db
    12/05/2012 22:45 162,174,976 D317400.DB
    03/12/2012 00:31 6,144 sms_info_list.db
    27/11/2012 08:54 10,240 dashboards.db
    30/11/2012 01:03 183,296 vsc.db
    20/11/2012 09:00 3,072 mycamera.db
    29/11/2012 14:59 2,048 recent_searches.db
    30/11/2012 23:36 5,120 db_tracker.db
    25/10/2012 00:38 34,897,920 D3413060A.db
    19 File(s) 202,081,318 bytes
    someone of them has a clear name and meaning, some other not.

    do you think that in someone of them it is configured the speed per street, used when calculating the fastest track or the estimated arrival time? and if it is also possible to change them (i.e. I ususally go fastest than 90 km/h in principal streets)

  5. #4
    Important User SQLite db files explained
    Join Date
    Dec 2010
    Somewhere over the Rainbow
    Rep Power


    If you delete files D317400.DB and D3413060A.db you'll lose some features. If you delete other files they will be recreated on Nuvi start because these files are created by firmware.

  6. #5
    GPSPower Helper SQLite db files explained
    SQLite db files explained
    dasilvarsa's Avatar
    Join Date
    Feb 2011
    Rep Power


    You can backup some of these .db files like custom_where_to and speedcorrections on 3490 and put them back after hard reset.
    The customization is retained.
    I've used both of these without problem.
    We could also backup the whole folder and restore after Hard-Reset.(Have not tried yet but will do soon.)
    The difference between stupidity and genius is that genius has its limits.
    Albert Einstein.




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.