Since we're well past v2.3 and Android is on v2.4.0.1 now, I'm going to suggest you upgrade to that version and respond in the threads specific to that version.

I've been running the new client for a few days now. It's horrible and unusable. It keeps jamming, have to force it to shut down constantly.

I have one issue (so far, just appdated Andorid to 2.3.3) with this release. Every time I reject a speedcam (that is not there offcourse) waze will crash and I have to restart it waze again.

dmcconachie wrote:Hi Efrat,

For me the widget just Force Closes all the time and leaves me with a never ending "Please wait".

Running Cyanogenmod 7.0.2 on HTC Desire

Darren

I also have this problem on my HTC Sensation.

Error79 wrote:Here a new one.
Once you muted during navigation, it is no longer possible to unmute again.
It simply stays on mute permanently

I have the same problem. Typically I let Waze navigate me most places but because I already know my way I keep the volume muted. This week there have been a few time I have gone somewhere less familiar and I wanted to hear the directions but have since not been able to restore the TTS. The option is always there to unmute and like previously posted, it behaves as if you clicked on it closing the menu but never restores the voice. All other voice prompts still operate, warnings, etc. Just no navigation. I checked my Android settings for another voice to switch to but all I have is one, Pico TTS.

LG Revolution
Android 2.2.2

dmcconachie wrote:Hi Efrat,

For me the widget just Force Closes all the time and leaves me with a never ending "Please wait".

Running Cyanogenmod 7.0.2 on HTC Desire

Darren

Same here.

I see no data until I open the Waze client, which starts crashing time after time (but only if the widget is in use). If closed, the widgets stays forever with a message, only that in the Spanish localized version only "Por favor," can be seen.

About the client itself, spontaneous crashes are gone, but these two days, the connection is lost very often, apart from taking ages until it finds the network after starting.

Going back to the client itself, has anybody else seen long time data disconnects in every route these days? I mean 5-10 minutes offline every hour, and that is happening randomly after Waze has successfully started.

Did I also mentioned that the "one item in the event list means not clickable (but yes if in the group event list)" issue still persists?

unwallflower wrote:Pings are still being sent to the wrong user sometimes. This really is a BAD bug, you guys. It's definitely the most concerning of all the Android bugs IMO.

Connectivity issues are even worst for me, not having found much use for the pings. It is impossible to be reported or to report alerts and speeds if one goes suddenly offline for several minutes, or it takes 2 mins to become online after starting Waze.

Is there any news on that, by the way?

Cova_fe wrote:Do enyone got a problem with speed cams? Each time I mark "not here" on a speed cam, waze immediately crashes. Simple, repeatable every time

SGS, 2.3.4, italy.

I clicked "not here" for a particular speedcam a couple of times and it didn't crash, but I cannot remember if it was with this beta or the previous one.

Does it happen with the same cam or with different ones? Perhaps it is location dependant.

This version contains new text to speech feature (TTS) which is available in USA & Canada only at this stage (hopefully will be available in other countries in the near future)

I'm getting a fair number of voice prompts that stop at the "at." For example, "In one tenth of a mile turn right at" with no road name spoken. This happens where the road name is more complicated than a simple two or three word street name which includes many ramp names. Does anyone know what is required to have the name of the turn spoken?