If I map out a long distance, it can take 10 minutes for Primo to load. Long time to calculate, then a long time to load on restart. I assume it's because of low memory. Could it be the TTS Voices that are slowing things down?
The lack of memory could be part of the problem, but when a GPS is running as slow as you describe, I would suspect a slow cpu. In any event this tool will let you know what resources are available. It will tell you the type of cpu, and speed, but you will have to do some research to determine how that compares to the cpus being used in todays gpses. What kind of GPS are you using?
I know my specs. I am using a 528Mhz ARM processor with 64kb of RAM. I use a piece of software that keeps track of Mhz and steps it up or down depending on the load. The higher the load, the higher the Hz. I think it only ran at 128 when Primo was working so hard.
In the interest of science, I can try stepping it up to 528 manually and see if that improves things. Please stand by.
I guess we are not allowed to edit our posts here.
I tried to set up a destination about 800 miles away and turned the CPU on "high."
Put in the State okay!
Put in the City okay!
Street took about 2 minutes, then okay!
Put in the street number okay!
Displayed the location on the map, okay!
Then poked "Select" and it all ground to a halt.
It's been a few minutes and things are still unresponsive here.
I am downloading the tool as I wait, but this is a Samsung SCH-I730 phone running WM5.
The phone has GPS built-in, but the company will not allow access to it by other programs, so I am using a Bluetooth Puck. A Globalsat BT-359.