iPhone Beta 3.1.99.28 Feedback thread

[AlanOfTheBerg]

Has anybody else been experiencing issues with uploading debug logs?

I did have a problem in a low data coverage area and it had 36 to upload. It didn't retry later. The next time I tried to upload, it did the same thing, but now had 41 files to upload. Finally, I tried it on wifi and they all went.

Today, I tried again with my issue above and happened to be, again, in a low coverage area and actually had no data signal for about 3 minutes. I retried while still on the road and it worked fine.

So, I'm unsure if it's something with the app, or just bad luck/timing, or a combination of the two.

[Dave2084]

Has anybody else been experiencing issues with uploading debug logs?

I've seen this too, though it might be attributed to the log upload starting in low/no coverage area, however, typically you're never gonna get past log 1 without forcing a manual log upload as well.

I've been meaning to post this for a while but somehow kept forgetting!

[Dave2084]

Had a crash this evening while navigating.

The purple routing line had disappeared from the roads even though I had a good 3G signal and I don't think I'd lost signal prior to the event. I was just considering taking a screenshot when it crashed. Logs uploaded at approx 8.30pm UK local time. (and they uploaded fine over 3G)

This got me thinking. For the beta builds only, can the devs add a extra button to the main screen to take a screenshot as it's not always easy/safe/continent to take one on iPhone while driving as you need 2 hands, and screenshots are so helpful when giving you feedback on these betas.

Other observations:
1. Connecting to Foursquare to check in seems to result in loss of map tracking if you hit "close" before or after checking in ("back" is OK) and you have to push the target button to get it back.
2. when adding comments to a UR in landscape mode you cannot see what you're typing as the keyboard covers it up.


Thumbs ups:
1. Nice to see when you go over a roundabout the UK TTS says "Straight on" as opposed to the previous "Straight".
2. The event radius seems to be working now (Though can we have a 10 mile setting?)

[AlanOfTheBerg]

BUG: When autozoom is off or set by distance, in navigation mode, bring up alt routes while in motion, then hit Back without making a selection.

EXPECTED RESULT: Return to map with previous zoom level.

ACTUAL RESULT: Return to map with zoom level set to maximum.


--
If it looks strange, or I used bad grammar or misspelled anything, it's my phone's fault.

[gettingthere]

BUG. Reproducible. Hopefully I list all of the steps this time

* Set a route
* On the route preview screen click on Alternative Routes
* Do not choose an alternative route
* Click the back button on the Alternative Routes screen
* The route that you originally set will continue, but without any ETA information. The black ETA box is missing.

[gonzabur]

Hi, all.

I am a spanish beta-user. Iphone 3GS, IOS 5.0.1 Jailbroken device.

In the european version (spanish langauge), it only works, the TTS, and the stop-point option. It does not work, at least for me, ASR and the gas station (I know it is only implemented in the USA servers - world )

At the begining of using this version I suffered of the same problems with the TTS as in the previous version (copyright mark issue at streets without no name; some problems with the reading of stressed letters, and the delay of the speech of the exit number at roundabouts). But, from today, something has changed and TTS works almost perfect in the spanish language, refering to the previous problems. there is still a delay in the roundabouts. Good job.

I have discovered today a bug, well I do not know if it is, but is a problem with re-routing. I will try to explain:
* I was driving to a stop-point in my route today.
* I took a different way to that stop-point than that proposed by waze.
* Waze did not re-calculate the route to the stop-point. (I was near to the stop-point, less than a kilometer in straight line). And also, the first route to the stop-point was still drawn in the map.
* In the next screen-shots, I try to show the problem for a better understarding.


I will try to reproduce again this error in my routes, in order to know if is a general issue or just only a particular one.

Another bug is when starting the app, and selecting a destination, and if you don't have data network it appear in the ETA and in the distance the following:

This has happened to me at last twice.

I hope this will help for the next.

[gettingthere]

No ETA when routing off network is by design. Waze can't accurately estimate the ETA since Waze can't communicate with the routing server(s). I appreciate that Waze is no longer providing inaccurate ETA when off network and is making it very clear that the routing may not be correct.

[gettingthere]

I suspect Waze is planning to release Waze 3.2 next week. I saw some Internet news article today where a VP at Waze was quoted that an announcement was pending next week reading new functionality.

[bgodette]

I suspect Waze is planning to release Waze 3.2 next week. I saw some Internet news article today where a VP at Waze was quoted that an announcement was pending next week reading new functionality.

What's odd is the only feature disparity between iPhone and Android is "stop on route" (waypoint) is missing from Android for some reason.

It's all my phone's fault for using Tapatalk.

[gerhardstru]

On the event radius setting can you add a option to only show events on route