Forum: General Topics

No doubt, you'll get an answer from Stephen (the guy that wrote all this...!) soon,

But it sounds to me like the application is having trouble writing to the memory of your phone.
Have you tried turning on 'Map Caching' in the settings screen?
Also, you could try setting the permissions of the application on your phone to allow it access to the phones memory.
(on my phone (SE W610i) in the 'Applications' screen, if I select TMJ-Mobile, press the 'More' key, select 'Permissions' then I can control what access TMJ has to Internet, Messaging, and Read/Write User Data.

HTH!

Chris.

Hi Rui,

Unfortunately the security prompts are imposed by the phone manufacturer on some older handsets, they are designed to prevent unauthorised access to the phones storage, but as you have found, are quite irritating when they keep appearing. The only way to prevent them is if I were to 'digitally sign' the program, but at the moment I can't afford to buy a digital signature.

More recent Sony Ericssons have better options in the Permissions menu that can completely turn off, or at least reduce the number of prompts, for example my W910i has 'Read User Data: No, Always Ask, Ask Once, and Never Ask'. Theres a slim possibility that the Sony Ericsson Update Service might have a more recent firmware version for your W900 that may allow more permissions, though I can't guarantee it.

Otherwise, as Chris suggested and as you are already doing, the only option is to use the Map Cache I'm afraid.

Your second problem has me a bit stumped - the Waypoints *should* be stored internally between restarts. Are all the other settings remembered correctly between restarts, for example the current Track, Route and TMJ Username/Devicecode, etc? This is a bit of a shot in the dark, but do any of your waypoint names contain any 'non-ascii' characters? (Although these *should* work, it might be worth renaming them on the website before syncing to see if that helps).
Also, are there any errors listed in the Event Log (Menu/Display/View Event Log) when starting the program, after syncing, after manually adding a new waypoint, or just before exiting?

Cheers,
Stephen

Glad to hear the Waypoints problem is sorted. To be honest I'd expect it to still save them when using the phones BACK button, but I guess this isn't too big a problem (its best to use the Exit function anyway to cleanly close the web connection, if enabled).

Yes, the program does just load the 4 currently needed tiles into memory at a time. It first checks whether they are stored in the Cache (which won't display the security prompt) and will take them from there if available, otherwise it will have to load them from the main file (but will then also stick them into the cache for future use).

The cause of all the annoyance is that Java only allows data to be read from a file in one 'direction'. The file is basically a string of PNG/JPEG image files stuck together end-to-end. The security prompt only appears when the file is first opened.

So if, for example, the 5th tile is needed, then the initial security prompt will appear for opening the file. The file 'cursor' then jumps to the 5th tile and the data is read.
If then, say the 11th tile is requested, the cursor can jump straight to it (as its currently at the end of the 5th file) and grab that tile as well, without prompts.
If the 10th tile is then subsequently needed, the cursor can't move backwards, so the file has to be closed and then opened again (triggering another prompt) in order for the cursor to move to the start of the 10th tile.
And so on... Annoying, huh!

The map cache is really only designed to hold a few dozen tiles at a time. Theoretically a small map file could fit entirely into the cache, in which case you might get away with not seeing any prompts. However, the cache doesn't store the maps as efficiently at the main file, so for larger map files this isn't really feasible (I'm using a map that is 170Mb in size, though fortunately my W910 doesn't display the prompts!). There is also a slight bug with the cache that I've yet to fully fix that means that some tiles never make it into the cache, so the prompts might never disappear.

Hope this makes sense!

Cheers,
Stephen

ok Stephen that's more or less what I thought was happening...