Nuevos links

http://www.4shared.com/file/Fm4p1TMs/Locale_v16.html
http://www.filesonic.pe/file/882085441

workaround for the update notice to make locale 1.6 work again - rooted phone only!
- close locale (kill via app settings or similar)
- go to /data/data/com.twofortyfouram.locale
- delete all files and directories EXCEPT FOR databases/locale.sqlite - DO NOT DELETE THIS, it contains the situations of locale
- forbid internet access for locale, e.g. with DroidWall or on CM7 with the app management

- forbid internet access for locale, e.g. with DroidWall or on CM7 with the app management

This works, but Locales ability to determine the actual location without GPS is quite limited/non-existent. I had to download the cell-plugin in order to do that.

Right, this is the downside. And it could be, that denying internet access is not sufficient, on one of the two phones here the update notice popped again. So I denied the right to check the license in the market, too.
Let's hope that 2.0 finds the way to mobilism quite soon...

Another idea: if we could find out in which files locale save the update info, perhaps read-only these files could do the job.
In com.twofortyfouram.locale/shared_prefs are two xml files, com.twofortyfouram.locale.xml and com.twofortyfouram.locale.licensing.xml. The first one contains the entry "LOCALE_EXPIRED". Changing this to false didn't work out, the notice popped up immediately. So somewhere must be another entry, perhaps in the licensing file.
I'll play around a bit and see if I can work something out.

any luck with this?

[javaguy216]

Locale 2.02

viewtopic.php?f=443&t=248184&hilit=locale

Reviews for 2.0.2 in the Market are not that great, seems the location detection is quite lame compared to 1.6, also there are complaints about huge battery drain.
Don't know if I give it a try or stay with 1.6 for a while.

About 1.6 and the update notice, what I've tried today:
After yesterday's try with deleting nearly all files and denying license check (as stated above), I edited com.twofortyfouram.locale.xml, set "UPDATES_ENABLED" to false. Then I allowed network access again, but kept denying the license check. Even after a locale restart with data on, until now (about 10 hours later) no update notice.

My current guess: the update check is done via the market, the info about update available or not is stored both in com.twofortyfouram.locale.xml ("LOCALE_EXPIRED") and in one of the crypted entries in com.twofortyfouram.locale.licensing.xml ("lastResponse" and/or "validityTimestamp").
Should it happen to me that the update notices pops up again, I'll try to figure this out (delete the two xml files and see what happens, when neccessary then one of the other files after another until the update notice vanishes).

Findings:
- setting "UPDATES_ENABLED" to false in com.twofortyfouram.locale.xml doesn't change anything, value is being overwritten by locale.
- deleting both xml files resets the update notice.
- denying market license check only doesn't work.

So I guess the only usable way is to use a (w)lan-sniffer to find out and block the update server adress. Since this forced update behavior affects all releases, even current and future ones like 2.0.2 (to which I have updated), this seems to be a neccessary step. Or the release groups patch out the update check