Android beta 3.1.99.111 feedback thread

[Spil]

Settings->General->Keep backlight on doesn't work...

Screen is always on, also if settings checbox is in disable state

Was your phone plugged in and charging at the time? Depending on your phone's master settings, this could cause the screen to remain on, regardless of what you change in Waze's settings.

[Autourdupc]

My device is in French.

With settings set to "Full guidance". When setting "General/Navigation", I have only the choice Male 1 or Male 2 (This should be translated Homme 1 or Homme 2) --> No female !

In both cases, voice navigation is bad quality and not the same as for alerts witch is clear and perfect.

Also, instructions are mixed with other language than French. I have to return back to setting set to Minimal vocal guidance to get a clear and good quality male voice.

Ima.jpg (22.78 KiB) Viewed 616 times

[Autourdupc]

For popup reports, should be added to the settings the radius of 2 and 3 kilometers... In big city, this is enought ! Otherwise, we get so many reports from area too far to be usefull !

[Sanicko]

Was your phone plugged in and charging at the time? Depending on your phone's master settings, this could cause the screen to remain on, regardless of what you change in Waze's settings.

No, phone was not plugged, no charging. System settings: backlight off after 30 seconds. Before Waze start and after Waze close backlight realy off after 30 seconds...

Just I performed another test, results are:
- After Waze start, I leave phone on the desk and... after 30 seconds backlight off
- I selected route and... backlight still on
- After stop navigation... backlight still on


-= Odoslané z Xperia Neo V =-

[alenansk]

hi all

i would like to make a little suggestion

yestersday while navigating, i received a call (i have bluetooch headset)
so after call accepted, on display i see only data of calling person, no waze/maps and navigation instructions as well as the person to talk i hear in my headset.
Then, after x seconds, screen with call data become black (classic stand-by of phone settings). After conversation finished, a screen riappear and waze turned back to the screen.

i would prefer if the waze continue working on background, and the call data appears something about 1/4 or 1/3 of screen in some angle (attach an example), so while talking i can continue to see the street to drive... and no black screen

thank you

[FreeMan12]

<snip>

i would prefer if the waze continue working on background, and the call data appears something about 1/4 or 1/3 of screen in some angle (attach an example), so while talking i can continue to see the street to drive... and no black screen

<snip>

I agree. What I usually do, is after the call has been connected (either incoming or outgoing), I hit the notification drop down and return to waze, letting the call run in the background. Mostly, because I've never had waze return after the call is over - I always get the screen timing out & when the call disconnects, I'm at the phone's lock screen.

[FreeMan12]

I've been getting odd cities showing up in the client. This has been going on for quite some time, so it's nothing new in this particular version of the client, but I finally remembered to get a picture of it and post about it.

Here's the client screen:

where you can see the town of "Belmont" off in the distance.

Here's Belmont (A) in relation to where I actually was (B):


Here is where I was when the screen image was taken. I was heading east from a bit west of where State Rd 213 turns back north. As you can see, the only town listed east of my location is "rankton" (who's initial "F" is missing). I've just confirmed that there are no road segments between my location and Frankton with a city name of "Belmont".

Sometimes, I see the town of Washington listed to the east (where Belmont is currently shown), but the real location of Washington is even farther south and west of Belmont.

FreeMan

EDIT: Just for fun, I found an older image that shows "Belmont" to the east, and "Carmel" to the north, with Atlanta in the right location. Carmel is actually located about 20 miles south of where this was captured.

[crazycomputingdotnet]

I have noticed an odd issue. When I am in navigation mode and I deviate from the route and not on network, Waze will try to connect to the routing server for a while, then end the routine (can't connect to the routing server) and then if I am still off network in ~1-5 minutes Waze will hard crash. This happened to me again today. Logs were sent around 1430 CDT.

[yoho]

I'm using an HTC Wildfire. This version is much more responsive and usable than any other Waze v3.X so congrats, I can finally use waze 3 instead of waze 2 !
Problems encountered :

• Crash everytime I want to report something (as soon as I click the report button or if I drag it to the left or even if I answer yes to the "stuck in traffic ?" prompt)
• Alternate routes are not displayed properly : the first route (#1) is a straight line from the start till the end. When I want to display only 1 route by clicking on its button, no route is displayed at all.
• While driving, additional lines are displayed in purple (in addition to your route) : it looks like they are joining nearby junctions with a straight line.
• GPS is rather stable but like for previous versions of waze, you need to shut down waze and start it up again to get the GPS back.
• A few crashes when turning my phone (from portrait to landscape or vice-versa) but hard to tell exactly when : it only happened twice in a full week of test (and I use waze at least twice a day).
• I'm in belgium and there are several official languages spoken here : french, dutch and german. The TTS only proposes dutch male & female. By the way, why don't you use the native TTS feature of android ? I have bought the SVOX TTS engine (for other apps) but it's not in use by Waze.
• I went past 2 accidents and each time I wanted to say thanks to the reporter but the accident icon wasn't there anymore : is it because I didn't confirm it in time and waze removed the accidents ?

[bgodette]

Not likely a problem with the client; but since sometime on 5/29 searching for an address or catagory fails with "cannot connect to server" or "no results found" from the Denver, CO metro area. Previous .105 beta and market versions both work fine. Navigating to favorites works as well, presumably because position is stored, map pins also work.

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