maemo.org - Talk - How tracker works

maemo.org - Talk (https://talk.maemo.org/index.php)

- Multimedia (https://talk.maemo.org/forumdisplay.php?f=32)

- - How tracker works (https://talk.maemo.org/showthread.php?t=61960)

Re: How tracker works

All media meta data like artist, album, ... in the mediaplayer is based on
tracker information.

nicolai

Re: How tracker works

Certainly in Meego it actually stores info by itself (from the meego-dev) mailing list :

Quote:

From patrick.ohly at intel.com Wed Sep 8 04:32:25 2010
From: patrick.ohly at intel.com (Patrick Ohly)
Date: Wed, 08 Sep 2010 13:32:25 +0200
Subject: [MeeGo-dev] data storage and indexing in MeeGo - a survey
Message-ID: <1283945545.7176.302.camel@pohly-mobl1.ikn.intel.com>

Hello!

As those who I have been pestering with questions in the past already
know, I'm trying to get an overview of which data we store in MeeGo core
and how it can be accessed and/or searched. This email is an attempt to
close some gaps and extend the list that I'll present below. I also have
some general questions around Tracker.

Typically the answer consists of a domain specific storage and API
(mkcal + sqlite) plus Tracker for indexing the data. In some cases,
Tracker is also the main storage of the data (QtContacts +
qtcontacts-tracker). Sometimes there are additional portability layers
on top of the MeeGo platform component (QtMobility Messaging on top of
the Qt Messaging Framework (QMF)).

The next question then becomes how data items are referenced at the
various levels, and how the data content is mapped. For example, can I
take the Tracker search results and open the corresponding item using
domain specific tools and APIs?

This mapping is mostly only defined in the source code which implements
the Tracker indexing. I'll provide pointers below.

Finally, how can a permanently running app be notified of data changes?

Here's what I gathered so far - please extend and/or correct.
...

Very interesting and hardcore article on data and searching it. Most of it Meego oriented but interesting in the wider tracker context
http://lists.meego.com/pipermail/mee...er/005546.html

Re: How tracker works

from what I understand..how about we juss write few scripts.. mk a desktop shortcut or qbw.. and turn on /off indexing/watchdog with the scripts..
if we cant merge those scripts with the apps like camera an all.. atleast we wil hv option to turn off indexin/watchdogs before using the camera... :D
another idea... will write a script fr qbw i guess

Re: How tracker works

One issue I have with the tracker.cfg is that there seems to be misunderstanding about the two Battery flags in it:

The config file itself and the help in the "Tracker Cfg" state that:

Code:

# Set to true to disable indexing when running on battery

BatteryIndex=false

# Set to true to disable initial indexing when running on battery

BatteryIndexInitial=false

However, the tracker.cfg man states that:

Code:

BatteryIndex=BOOLEAN

    Enable or disable indexing when on battery power. 

BatteryIndexInitial=BOOLEAN

    Enable or disable initial index sweep (i.e. the very first indexing) when on battery power.

These two statements seem to be 180° contradictory.

For me, I now have set these flags to FALSE and expect that this DISABLES indexing while ON BATTERY.

Re: How tracker works

Quote:

Originally Posted by twaelti (Post 812571)

One issue I have with the tracker.cfg is that there seems to be misunderstanding about the two Battery flags in it:

The config file itself and the help in the "Tracker Cfg" state that:

Code:

# Set to true to disable indexing when running on battery

BatteryIndex=false

# Set to true to disable initial indexing when running on battery

BatteryIndexInitial=false

However, the tracker.cfg man states that:

Code:

BatteryIndex=BOOLEAN

    Enable or disable indexing when on battery power. 

BatteryIndexInitial=BOOLEAN

    Enable or disable initial index sweep (i.e. the very first indexing) when on battery power.

These two statements seem to be 180° contradictory.

For me, I now have set these flags to FALSE and expect that this DISABLES indexing while ON BATTERY.

They're not really contradictory - the manual page doesn't say which value enables and which disables. I'd be surprised if the details in the config file are correct though. Setting BatteryIndex to false to enable indexing while on battery is just so wrong - anyone who implements that deserves to be staked out on an anthill and smeared with honey.

Re: How tracker works

To follow up, i finally removed all but the two camera (DCIM) folders from my watch folders list to solve the problem of tracker indexing folders i don't want it to. It seems that either having the root of a child folder in the watch folders root list overrides the do not watch list, or the do not watch list is not recursive.

I added the music folders to the crawl list, because i only need those indexed when i (infrequently) change the music and can trigger a rebuild myself when i do that.

I tried increasing the delay time to 120 s. That seems to be a good way to work around tracker jumping in during the middle of a short filming or series of photos. However, it seems i'm not notified now of the reindexing countdown.

It may be something else that broke that, though.

Re: How tracker works

LowMemoryMode=true seems to cause the reindexing ETA not to display.

Can anyone confirm this?

Re: How tracker works

Can someone please tell me how to check the current version of tracker in our devices. I am running PR1.3+CSSU-Updates (latest is 13).

There is a current (hot) discussion going on at meego-dev miling list about the future of tracker. The point that came out (w.r.t tracker in maemo) is to which version we are running. Looks like we are running the 0.6.95.x version of Tracker. But their latest version is 0.10.1 and they claim that the latest version is way better than the one that maemo uses.

So, can someone please tell me how to check which version of Tracker are we running. 0.10.1 or older?

http://lists.meego.com/pipermail/mee...ch/482001.html
http://lists.meego.com/pipermail/mee...ch/481890.html (Thread start)

Thanks in advance,

Re: How tracker works

Quote:

Originally Posted by vkv.raju (Post 964580)

This should be the PR1.3 version - http://maemo.org/packages/package_in...-35maemo1+0m5/

Re: How tracker works

Quote:

Originally Posted by dsawhney (Post 964589)

This should be the PR1.3 version - http://maemo.org/packages/package_in...-35maemo1+0m5/

So, from the link it looks like 0.6.95-35maemo1+0m5 is the version for tracker. But how to find out if CSSU has already updated it to the latest? If not, may be we can request the CSSU team to include the latest version of tracker in the CSSU?