Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - svartbjorn

I have used online Google Maps many times before, but when I now select Online Maps= Google Classic (or Satellite, or Hybride, or Terrain), I get the error message "Unknown problem". Anybody knows what has happened and what to do to get it back?
Other features / Re: Offline POI database
July 23, 2013, 12:18:41
Very interesting! I am going to Austria next week and will download the database for that country.

I live in Norway, so would be great if you could create the database for Norway too.

Thank you very much.
Other features / Re: GUI of Locus
February 06, 2012, 09:22:57
I really like the current GUI (what you call the *old style* above). One particular detail that is extremely useful, is that current setting of an entry is shown in yellow, so you do not need to tap into that entry to see what is selected. This is particularly useful in an app like Locus with so many settings (which all are great!). Also the way the menus are organized on the map and all the user settings there are really good.
In version 1.14.2 everything works great! The two new  Parking commands - Guide On, Navigate - are perfect!
Thank you very much!
I downloaded the latest version 1.14.1. I was curious about all the improvements in the Parking function. But every time I tap Parking, Locus crashes (GPS on or off).
Thank you very much, Menion, for a quick fix - as usual!
If I select "Color style of recorded track" = "According to speed" or = "According to altitude", the color changes. But how are the limits determining the color changes calculated?
I have enabled "Top panel hiding". The Top panel does hide after the timeout - but NOT if the Record menu line (which pops up above the bottom command line) is shown. The Top panel never hides in this case. As soon as I cross out the Record menu line, the Top panel hides again as expected after the timeout. I guess this is not the intention.
I use the Parking feature a lot. It is a really great feature.
However, there are two issues with the Parking function:

1) Parking data is lost if phone reboots
When I activate the Parking function, it is seems to be stored in the RAM, because all Parking data are lost if the phone reboots. That is critical if you trust the Parking function to find your way back to the car. So I am asking if the Parking data could rather be stored either in the internal flash memory or on the SD card. If tracking is on, the track is still there after reboot, so I guess the same could be done with the Parking data?

2) Guiding to Parking
If I activate the Parking function, the top status bar of Android shows that Parking is active. If I pull down the status window and tap the Parking (or tap Menu > Functions > Parking), I get a menu with 4 entries: Map, Compass, Edit and Cancel. But no Guiding! That is highly wanted! As it is now, I must either tap Compass and then Home, or tap Map to center the Parking and then tap the Parking POI. Would be great if the 4-entry menu mentioned above could include a 5th command: Guiding.
Other features / Re: Voice NAVIGATION
October 17, 2011, 12:25:54
I was last week on a business trip in USA and tried out Locus navigation on the freeways. In the US there are a *lot* of "No left turn"s. The MapQuest doesn't seem to supply any such information. That makes Locus navigation kind of useless. Here is a summary of this week's experience (with latest version):

- "No left turn" ignored by MapQuest. I didn't have the chance to check if "One way street" is ignored.
- exit from freeway is missing exit number
- top status line selected to show name of street turning into very often displays "Unknown". That is bad when exiting or entering freeways, since it is important to verify the street I am exiting to or freeway direction when entering. E.g. when I am entering freeway I95, the signs always display e.g. I95N and I95S. Then it is important that Locus displays that on the top status line. It doesn't do that.
- if I create a route in steps with via points in order to force a certain route, the voice says "You have reached your destination" for every via point. Since the route is shown continuing after the via point, Locus obviously knows it is not the final destination. Is it a way to rather say "You have reached your via point" ? Locus also always says "You have reached your destination" when I start the navigation by enabling guiding from the first point on the route. I assume this is the same issue.
- The 2nd status line with the two fields still displays "Unknown" if the field is selected to show "Time of arrival" or "Time to target".
Other features / Re: CloudMade "navigation"
October 05, 2011, 08:32:05
Refer my post above regarding the navigation status line. One more thing I discovered today: If I select "Time to next cross", the field shows correct value as long as I am moving. When I stop, the field displays a huge number (seems to be max number possible to store. Obviously what you get when calculated from speed =0. However, it looks too bad. It should rather display the latest calculated value that makes sense. So e.g if you have 2min left to next cross and have to stop, it should keep showing 2min. This is how car navigators work. Alternatively it could display "----".
Other features / Re: CloudMade "navigation"
October 04, 2011, 09:49:00
Discovered an error in the new navigation status line with the two user selectable fields:
- If I select "Time of arrival", it displays "Unknown" until I reach the destination whereupon it displays a time that makes no sense to me.
- If I select "Time to target", it displays "Unknown" until I reach the destination whereupon it displays a huge integer number with more than 8 digits.

I am assuming these fields are supposed to display the estimated time of arrival, not the actual time spent calculated after arrival.

What is the estimated arrival time based upon - speed limit on the streets chosen in the calculated route or an actual average speed the last minutes? The first one is what is used in other navigation apps. In that way you get a time even before you have started moving.
Exactly. The first one is correct. The second one is how I get it. I'll be busy until late tonight, so you know in case you want me to test something.
Sorry, but same problem. The location shown on Google Maps is far from my sent position. GMaps shows the closest location is can find with a street address.

You can easily recreate the issue by moving map center to a point out in the wilderness with no streets around. Send it to yourself and display it in GMaps.
Zooming does work correctly. I was just confused first time when I moved zoomed out as far as possible for the selected map, and still I saw a lot of map area outside that. But now I understand that this is the auto-loaded adjacent map. I notice that the max zoom out is defined by the selected map. So even though there are auto-loaded maps covering a larger area, I can't zoom out to get the complete map area within the screen area. Which makes sense, since the selected map wouldn't have been displayed in that case.

However, allowing to zoom further out than defined by the selected map, would been useful in the case you have for example a city map with detailed street zoom level, and another map covering a larger area around the city (including the city). In those cases it could have been useful to zoom even further out than what the city map defines. This could be expanded to an even larger map covering the whole country.  So that would allow you to zoom out to see the whole country, then zooming into a city to see the detailed streets. I have maps like that, but have to manually select the country map to be able to zoom out to see the whole country. Then I need to manually switch to the city map if I want to zoom into the detailed city streets. Which is ok. I can see it would be challenging to swicth maps like that automatically when maps are overlapping and how to decide the priority of maps.

So everything is fine, Menion.