Android 3.5.1.4 official feedback thread

[Kuhlkatz]

This relates to TTS, but here's the full story.

3.5 version was updated through Play store, no problems. Navigated to work fine this morning.
I saw the Waze Google+ posting on "Robin" and decided to install it to play around later. Selected Waze integration while briefly looking at it at work, and shut it down.

Later when starting Waze to verify a menu option for someone. Waze just would not start, as it could not connect. I was connected on Wi-Fi at the time, so thought it was a network issue. Switched Wi-Fi off & tried 3G. Still the same - Waze could not connect to the network. A colleague verified that he connected fine, so I cleared Wazes data from Apps settings.
Voila, that worked ! Looks like Robin broke my Waze, but I'll figure that out later..

When I drove back home, I obviously had to set ASR back on as all my setting was toast. Restarted and set course home, and then Serena said in her finest English voice "Lets get streeteted".
I thought I heard wrong, but looked at the TTS files when I got back. The TTS in both files that says 'started' are pronounced as 'streeteted'.

It looks like 'St' is now overcompensated for after being pronounced as Saint all over. It's probably a good thing that Serena did not tel me to get "Saint-eted". That would have ended my editing career.

Here's the links to both files on my dropbox public folder as I cannot upload .tts to the forum :
Let's get streeteted.
Let's get streeteted. Drive Safely.

We should really get TTS sorted if there is no form of whitespace between word abbreviations. 'N1' is not 'North One'. Fine if it was 'N 1' is, but parsing text can seriously be improved.
Better get streeteted on fixing this asap.

[Kuhlkatz]

I could be smoking my socks, but when a better route is found popup appears, it might be interfering with TTS.
I had 3 notices in succession this morning, and when manually closing the final notification I got an exit left TTS which was less than 100 meters before the exit.
With 4 lanes to cross in peak flow, this cannot be done without being an idiot, so had no option but wait out the delay about 1km beyond this point of no return.
Even if the suggested route is a valid alternative, and one that I would normally take in an extreme situation, Waze itself has never routed me around this way before. I also never checked if this was the initial route, as I left Waze to automatically start navigation when I left home.

I cannot safely say if it was actually just a last-minute change or if the previous pop-ups blanketed the 1km exit left notice, but I'll keep an eye open for this.

Did anyone else have something similar?

[Kuhlkatz]

That pinkish route reminds me of a not so major problem.
When navigating and you go to the stop option in the menu, even when you do not select a stop, the route is highlighted as the pinkish one from there, not the original purple marker.

[luisvale]

Hi

I'm trying to use Waze 3.5.1.4 on a Samsung Galaxy s3 4g (LTE) model GT-i9305 running Android 4.1.1 but Waze keeps crashing whatever I try to do. I've been submiting the crash reports but do we have a reasonable expectation to have Waze working on this phone ?

best regards

luis

[luisvale]

To the last two posters: please try removing all application settings and cache and temp files from the applications menu, then removing Waze app, then remove the entire Waze folder on sd and after that a clean reinstall from play store.

Hi

thanks although I had done it 2 or 3 times. Also the phone is brand new so the install was fresh. Previously I had Waze running on iPhone 3gs and for a few days on a Android 4.04 from ZTE (ZTE Skate Acqua) without issues. Also it still is able to run on my old Nokia e71


this issue with this phone is a PIA....

brgds

luis

[luisvale]

Also tried various network settings but always crashed. I can replicate the crashes easily. Just open waze and go to settings. Crashes immediately everytime.

Luis

edit:

After cleaning up Waze, I installed beta 3.5.1.905 and the problems continue. Waze starts ok, but after going to settings it crashes.

Phone: Samsung Galaxy S3 4G - GT-i9305

Android version 4.1.1

[Majumdar]

My first key impression:

Waze is FINALLY stable when running in the background .... every version prior to the 3.4.x beta / 3.5.x releases would crash if I would switch to another mobile app for more than 15-20 seconds.

Now it stays running for essentially the entire drive - which is on average between 30-60 minutes for me.

Good job for that improved stability!

[Manevitch]

I updated Waze to the latest version at about the same time I updated my Galaxy S III to Android 4.1.1, so I'm not quite sure where the problem lies. I drive with a bluetooth headset and it used to be that Waze would automatically mute turn-by-turn directions when I was on a phone call. Now I get the phone call AND the navigation in my ear, so I have to swipe around on my phone to stop navigation when I'm on a call. This, obviously, is a bad thing when I'm relying on Waze to provide driving directions.

Any thoughts?

[MartVR6]

Downloaded this morning the newest Waze 3.5.1.4 from Google Play and it gives me No Network connection and gets Waze closed.
So reinstalled it after removal and still No Network connection.
Cant use Waze anymore now, please help
Sony Ericsson Xperia X10i on Android 2.3.3

After battery remove and restart i got back a working Waze app

[maryjayjay]

Subject says it all. At this point I'd be happy just getting some acknowledgement that anyone has noted the issue. I keep going back to my old posts, but nothing.

To summarize: When listening to audio in a different app while in Waze the ffw and rew keys work on my BT stereo head unit, but not the pause key. Switching to a different app or pulling down the notification tray allows me to use the pause button, but I don't want to take my hands off the wheel to do this.