Hitting the "off" button sometimes just results in a Waze restart. This is on an iPhone 5 with iOS 6.

I've set the app to use kilometers, but there are still several places where the app shows "miles", for instance in the scoreboard.

There could be lots of places that isn't adjusted between km/miles. Do you need me to list all the places in the app, or is the above enough?

fvwazing wrote:a 3GS with iOS6

Impressive! Sorry for offtopicness, but:
I didn't upgrade my 3G beyond iOS 3.1.3 because I felt the performance on 4.x was too poor. I know that the 3GS is significantly faster, but still - is it acceptable? Or is it a retired device you only use in the car?

Places where "miles" are shown even when the app is set to use "kilometers":

- settings > scoreboard > "drive 55 miles to next level"
- settings > scoreboard > my points > "drive 100 miles"
- settings > scoreboard > my rank > "your first 10 miles"
- settings > scoreboard > my rank > "drive 500 miles within a week"

That's what I found for now, but I might append some to the above list if/when I find more.

argus-cronos wrote:Support???

Sorry for being dense but is this directed at me? I expected this to be parameterized and not translation-related, but if I can help with translation then I just need to know how/where to do that. I had not looked into translations yet, especially not for German.

gerben wrote:These are hard strings without parameters. If the value is in miles while your country uses metric, the translation should be adjusted.

I'd like to refute that. I've driven a little more and my app's scoreboard now says "Drive 43 miles to next level".
I don't think there's a complete string for every increment of distance.
I do think it's something like "Drive " %%distance_remaining%% " miles to next level".
That would indicate that two changes are needed:
1) a translation string ("miles","kilometers",...) based on app settings, (app change + translation)
2) calculate the value of %%distance_remaining%% based on app settings. (app change)

The need to enter a decimal (or comma) was removed to make things easier. You should just have to keep typing. If you want to enter 1.234, just type 1234. At least that is how it SHOULD work.

dsdaraujo wrote:

WeeeZer14 wrote:The need to enter a decimal (or comma) was removed to make things easier. You should just have to keep typing. If you want to enter 1.234, just type 1234. At least that is how it SHOULD work.

But it's not working. I tried to keep typing, but Waze just ignore aditional digits, and just put the first typed number.

Maybe related to the fact that Brazil should be using a comma and not a decimal? The client is putting in the decimal automatically but then the client is choking because it wants a comma?

Dave2084 wrote:New bug, never seen this before so probably not that important but as I was able get a screenshot I thought I'd post it:

http://img.tapatalk.com/d/12/09/05/4usutadu.jpg

Have you been playing about with your preferences file? This happened to me when I altered the scale factor of the wazers.

We have troubles in Italy to insert the prices (gas station) with iOs iPhone and iPad.
It doesn't see the numbers after the point (.)

If you type 1.879, it takes 1.000