iPhone 3.5.2 official feedback thread

[robin1979]

BUG: Gas station search on the Main Menu shows a $ symbol, which is improper for all non-$$ countries in the world, which is most of them. Please use the same icon that is used in the Report menu. (Previously reported in beta testing.)

Well, besides the sign for the dollar, the symbol is used worldwide for a symbol of capitalism, money, greed, Americanisation etc... I don't think it's out of place at all.

[robin1979]

When Waze has been closed using the "Switch Off" function, it consumes about 4% battery per hour. I tested this by double-clicking the home button and killing every other app.

After shutting down Waze using the double-click, battery consumption was less than 1% per hour.

There is no difference in 'Switch off' or killing it from the task bar. Both functions issue use the same system API to shut down the Waze process. The difference in battery use comes from something else, definitely not from Waze, because with both methods there are no longer any Waze processes running.

[fabryx73]

On my afternoon commute, despite having lots of Reports in the menu, and having the radius set to my usual 5 miles, I received no popups when stopped. Ever.

There is a new option (or at list I never noticed it before) to see only reports on your route, maybe the traffic was on other roads ?

As I wrote, I was not using the On Route event radius. I have tried it on 5 and 25 miles, and with that option, I should get dozens to hundreds of reports popping up when stopped.

The same behaviour happens also to me: from 3.5.2 update, no reports are shown on the display when I'm stopped during a trip. Before the update, popup was shown correctly coherently with the event distance setup.
It seem the same also increasing the radius of event notifications.
Any help / hint?
Bye

[fabryx73]

From 3.5 update, the localization seem to be less precise: when I stop my car near a crossing, the speed keep more time to fall to "0" and the time spent to do this, take my car position too ahead than the correct position. When The speed become "0" on the display, the GPS become aware of the positioning error, but istead of correcting the position on the map, it assume that the car is doing an "u" turn and place my car on the opposite lane of the street in the opposite direction .
Of course, as soon as I start moving again, the correct position and direction is resumed
I never notice this kind of error with previous versions and other nav applications performs well.
I have an iPhone 4s 6.0.1

THX
Bye

[Trakr]

Having the Gas Icon is nice on the front page but, the distance it shows stations is worthless. The distance is only about 2.5 miles. I can take 2 different routes going to a destination with the gas prices varying by as much as 10 cents/gallon between the routes. Now I can't even see those stations as they are 5 miles or more away and the destination being about 25 miles away. I would like to know which route to take to get the cheapest gas but can't without loading a route and then selecting that route, looking at the prices, then selecting all routes and selecting the other route and then looking at the prices.

It is nice that it does show stations for a complete route of at least 100 miles (tested) so why can't it show stations around my current location with a larger radius??

Thanks

[jasonh300]

When Waze has been closed using the "Switch Off" function, it consumes about 4% battery per hour. I tested this by double-clicking the home button and killing every other app.

After shutting down Waze using the double-click, battery consumption was less than 1% per hour.

There is no difference in 'Switch off' or killing it from the task bar. Both functions issue use the same system API to shut down the Waze process. The difference in battery use comes from something else, definitely not from Waze, because with both methods there are no longer any Waze processes running.

Well, today, when I arrived at work at 9:00, before unplugging the phone from the charger, I shut down Waze and manually killed every process in the taskbar...battery at 100%. At 1:00 pm, I checked and the battery was at 98%. At this point, I opened Waze and then closed it using the Switch Off function. At 5:00 pm, I checked and battery was at 80%.

All day long, I didn't use the phone, run any apps, receive or send any calls or texts or take the phone out of the sleep mode other than what I described here.

The logical conclusion is that Waze is draining the battery.

[davipt]

When Waze has been closed using the "Switch Off" function, it consumes about 4% battery per hour. I tested this by double-clicking the home button and killing every other app.

After shutting down Waze using the double-click, battery consumption was less than 1% per hour.

There is no difference in 'Switch off' or killing it from the task bar. Both functions issue use the same system API to shut down the Waze process. The difference in battery use comes from something else, definitely not from Waze, because with both methods there are no longer any Waze processes running.

Well, today, when I arrived at work at 9:00, before unplugging the phone from the charger, I shut down Waze and manually killed every process in the taskbar...battery at 100%. At 1:00 pm, I checked and the battery was at 98%. At this point, I opened Waze and then closed it using the Switch Off function. At 5:00 pm, I checked and battery was at 80%.

All day long, I didn't use the phone, run any apps, receive or send any calls or texts or take the phone out of the sleep mode other than what I described here.

The logical conclusion is that Waze is draining the battery.

As an iPhone developer, I got curious about this and had a look at my device and on one hand I can assure you that the Waze process is really gone in both cases, but on the other hand unfortunately on my device it wasn't 100% clear if the iOS' location daemon consumes the same after closing waze each way as I have too many applications consuming from the location services.
So there could be a bug somewhere on Waze or iOS that would keeps the location service consuming more when killing waze via menu, but I quite doubt it. I'm not 100% sure because I haven't checked the latest location API's and obviously I don't know exactly what Waze is doing with them, but only know what my own app does and what happens with it.

Besides you need to test it with the same environment conditions. Charge it to 100%. kill all apps and wait some hours. check the battery. then charge it again and open/close waze, wait the same hours and compare the battery.
Draining first 2% then 20% is kind of expected. It's like the gas tanks on the cars, they have 110 to 120% to give you the impression that when the tank is full it takes ages before it the pointer starts dropping to 99%, but then it goes down to 50% and 25% way too fast for my €€€

[jasonh300]

Besides you need to test it with the same environment conditions. Charge it to 100%. kill all apps and wait some hours. check the battery. then charge it again and open/close waze, wait the same hours and compare the battery.
Draining first 2% then 20% is kind of expected. It's like the gas tanks on the cars, they have 110 to 120% to give you the impression that when the tank is full it takes ages before it the pointer starts dropping to 99%, but then it goes down to 50% and 25% way too fast for my €€€

That's pretty much what I did. Yesterday, I found a huge drain after several hours. Killed Waze in the taskbar and there was no more drain (see my post from yesterday).

Tomorrow morning, I"ll repeat exactly what I did today...start from 100% at 9:00 am and see where the battery is at noon -- without killing Waze completely.

I did use a process monitor app just now to verify that when you "Switch Off" Waze, that process does stop.

[perlin]

Functionality issue: The PM notification popup contains too little space to read, so one must use the Inbox to read the whole message. However, once you read the entire message, there's no way to reply. The PM functionality in Waze is severely lacking. I do not think it should have been released (months ago) until the functionality was actually there. As it is, it is only marginally useful.

We agree with you and now days working on improving the PM/Inbox functionality.

[perlin]

BUG: 500ft turn notification happens at 1000ft (reported multiple times in beta testing)

Please send me (debug) logs that contains an example.