Dzzydvl wrote:

ArtVictorP wrote: This bug was reported on version 3.7.2 and was supposed to be fixed on this one. Sadly it wasn't.

What I figured out was that the app crashed when the following conditions occurred:

1. Android 4.2.1. or less
2. App Version 3.7.2 (and now 3.7.3)
3. Not using Wi-Fi, only Data Connection
4. Some people reported that the app crashed when the language voice was being downloaded or that the map crashed first and the only thing you could see was a blue square on the map with "BIG" written over it.

As I said before, most of the people could use the app only with a Wi-Fi connection.
Can you guys confirm this issue? Does the conditions have changed in anyway? I haven't confirmed if the bug appears on a specific brand or model.

Sent from my GT-I9505 using Tapatalk 2

I'm using Nexus 4 with Android 4.3.

I also get that "BIG" word but usually the map loads after that and sometimes would even work for a minute before crashing.

jdeyoung wrote:Sigh.
I give up.
Thought that FINALLY getting a new version would fix the crashes when stopping.
But no
Really depressing that they can't seem to fix this.
And I got the crash when trying to access the "about" box to verify that I was actually running the newest version.
Will this EVER get fix on Razr Maxx HD?
Please don't tell me I have to get an android update for my phone from Motorola. That seems like an even more elusive "fix" than the one to waze crashing...

jaimitop wrote:Hi,
is the crash issue ever going to be fixed? Or just waiting Google to kill this app in favour of Maps?
It's only me who think that Waze become unstable just after Google bought it?
BTW, i have a Galaxy S2 (I9100), tested with both stock 4.1.2 and custom 4.2.2 (CM). And Waze 3.7.3.

BigVDawgy wrote:

m-t-brandao wrote:Just happened again.
Sometimes I only notice when get to the destiny and grab the phone to turn off waze. It was already off.

Been happening to me every time now since the update. I turn Waze on, put the phone down, arrive at my destination and Waze is already off. The app is pretty much useless at this point.

Nexus 4 running 4.3 Build JWR66Y

Anyone know how to get back to the 3.7.2 build?

rigferna wrote:Have a galaxy note 2, with 4,1,2 installed. Have been having issues after this update were waze will turn off by itself after start. Some occasions will work for a couple of minutes others it will turn off almost inmediatly with no error screen. Have tried following
1, uninstall and re install - same problem
2, uninstalled, cleared cache on boot screen, wiped data, reinstalled - same problem
3. Uninstalled, wiped data, rooted, kept stock ROM, installed - same problem
4, wiped dalvik cache - same problem
5. Tried various settings, changed zoom settings, language strings, notifications, just about all but problem continues.
Point to note, on WiFi the program is more stable while on mobile data it is constant.
Same issue with 2g, H+ data speeds. Operator movistat Ecuador.
At this point the program is basically useless.

rongabor wrote:Waze 3.7.3.1 is still crashing a lot (just like previous versions).
It sometimes works for days, and sometimes crashes (over and over again on each restart). When it crashes it usually crashes while navigating for a few seconds to a few minutes.

Waze 3.7.3.1
Android 4.1.2
Samsung Galaxy S3 (GT-I9300)

I have uploaded debug logs (after using 2##2) today at around 18:50 (user: rongabor).
The debug logs contain multiple crashes, for example at: 17:45, 17:46, 18:10.

Browsing archive_waze.log I see the following before each error: "[##### Error] read_size <= 0: -1 [http_async.c:223 (_has_data_cb)]":
...
[17:45:15.634 Debug] Callback 0x5d8ec5e0 execution has been finished with state: 7. Connection id: 8. Pending [net.c:1602 (_run_callback)]
[17:45:15.635 Debug] Handled io callback message. Connection id: 8. [net.c:258 (net_msg_handler)]
[17:45:15.655 Debug] Callback 0x5d8ec5e0. IO Action: 1. Connection id: 8. [net.c:1597 (_run_callback)]
[17:45:15.655 Error] read_size <= 0: -1 [http_async.c:223 (_has_data_cb)]
[17:45:15.656 Debug] Receiving packet of size -1. Connection id: 8. State: 7 [net.c:533 (net_receive)]
[17:45:15.656 Debug] no ssl net recv: 1448. connection id: 8 [net.c:570 (net_receive)]


Is there a way around these crashes?

Please note that I have been submitting logs in multiple versions and reporting it in the official feedback threads. If this is not the preferred way, please let me know. I'd appreciate some feedback from Waze support (needless to say - I am willing to submit more logs if you wish for more debug info, or for me to test some beta version that works around the crashes).

Any feedback from Waze support would be appreciated.

Ron

paulkok_my wrote:What about trying Version 3.7.2?

Sent from my GT-I9300 using Tapatalk