Android v3.7.3 Official Feedback Thread

These forums are specific to the Waze mobile app. Post here if you experienced a problem while using the app, have a question about the app functionality or a feature such as navigation or search.

Moderators: Unholy, bextein

Re: Android v3.7.3 Official Feedback Thread

Postby Superfraggle » Fri Oct 18, 2013 11:19 pm

elohssasihtmaps wrote:I may have found a bug or something similar.

The waze app used to be able to direct me to my office without any problem. For roughly the past two weeks it is completely screwed up when it tries to navigate me the last 1/4 mile or so. If you see the picture I have included a link for below, you'll see my destination marked, but the route given ends in the middle of an interstate highway. No matter which direction I come from waze has no idea how to get me to the proper location. See my second linked picture to see how waze won't even direct me to the correct location from the same street! I have repeatedly checked the surrounding roads to make sure an allowed turn hasn't been marked as not allowed and things like that, but it seems to check out fine.

http://i.imgur.com/XmI4oK3.jpg

http://i.imgur.com/05iItzR.jpg


Nothing to do with the client version.

Suggest you post in the navigation and routing forum, or the local US forum, as there are several issues with some edits that may not be helping your issue.
ImageImage
Superfraggle
Area Manager
Area Manager
 
Posts: 1015
Joined: Tue Jul 17, 2012 8:21 pm
Has thanked: 47 times
Been thanked: 115 times

Re: Android v3.7.3 Official Feedback Thread

Postby Murphys78 » Sat Oct 19, 2013 5:17 am

Murphys78 wrote:Hi,
I (and somes friends too) can't find the waze group : "GS_Fr" when using the android version. :shock:
I know this group exist because I created it months ago ;)
Please, let me know how my friends can join this group, if they can't find it through the Waze App ?

Thanks for your answer
Bests regards
O.

:oops: Up :oops:
Murphys78
 
Posts: 8
Joined: Sat Dec 03, 2011 7:44 am
Has thanked: 0 time
Been thanked: 0 time

Re: Android v3.7.3 Official Feedback Thread

Postby Mike-1323 » Sun Oct 20, 2013 1:48 pm

elohssasihtmaps wrote:I may have found a bug or something similar.

The waze app used to be able to direct me to my office without any problem. For roughly the past two weeks it is completely screwed up when it tries to navigate me the last 1/4 mile or so. If you see the picture I have included a link for below, you'll see my destination marked, but the route given ends in the middle of an interstate highway. No matter which direction I come from waze has no idea how to get me to the proper location. See my second linked picture to see how waze won't even direct me to the correct location from the same street! I have repeatedly checked the surrounding roads to make sure an allowed turn hasn't been marked as not allowed and things like that, but it seems to check out fine.

http://i.imgur.com/XmI4oK3.jpg

http://i.imgur.com/05iItzR.jpg
One problem is that the parking lot road that has your destination pin is looping back and attempting to close upon itself (WME won't allow this). This seems to be causing a problem in the routing server because if the destination pin is moved to the portion of the parking lot road that isn't in that loop then routing appears to work. The fix is to correct the parking lot segment as covered in the Wiki.
Mike-1323
Area Manager
Area Manager
 
Posts: 1026
Joined: Fri Jul 15, 2011 11:06 pm
Location: Lorton, Va
Has thanked: 3 times
Been thanked: 186 times

Re: Android v3.7.3 Official Feedback Thread

Postby r-gabor » Sun Oct 20, 2013 4:29 pm

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
r-gabor
 
Posts: 5
Joined: Mon Dec 27, 2010 6:13 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Android v3.7.3 Official Feedback Thread

Postby eljerrys » Mon Oct 21, 2013 2:17 am

Ok, try this... use the voice command dictate what ever, affer that the movil key board has been working, no more crashes
eljerrys
 
Posts: 1
Joined: Mon Oct 21, 2013 2:15 am
Has thanked: 0 time
Been thanked: 0 time

Re: Android v3.7.3 Official Feedback Thread

Postby thecondor44 » Mon Oct 21, 2013 1:45 pm

I am incredibly frustrated with the latest update. The voice announcements are intermittent at best. I have re installed the app and it works for a few trips/days but then stops.

I can use this as a navigation tool if you cant keep it talking to me. Very frustrating.

Scott
thecondor44
 
Posts: 2
Joined: Wed Sep 11, 2013 1:43 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Android v3.7.3 Official Feedback Thread

Postby Guill007 » Mon Oct 21, 2013 5:15 pm

Version 3.7.3.1 is not behaving: it reports lost network way too often while in the mean time I'm still receiving emails...
Are Waze servers all saturated ? Or is it a bug ?

I lose my connexion in areas that are quite well covered by my provider, at times when the network is not overloaded.
Please fix this since without network, Waze looses quite a bit of its interest.
Guill007
 
Posts: 6
Joined: Sat Jun 15, 2013 8:33 am
Has thanked: 5 times
Been thanked: 1 time

Re: Android v3.7.3 Official Feedback Thread

Postby sidfiz » Tue Oct 22, 2013 8:34 am

Guill007 wrote:Version 3.7.3.1 is not behaving: it reports lost network way too often while in the mean time I'm still receiving emails...
Are Waze servers all saturated ? Or is it a bug ?


Same here.
Sunday evening, had to use another navigation app (that was working just fine) while Waze was unable to get any data... Particularly frustrating as traffic was heavy...
sidfiz
 
Posts: 3
Joined: Fri Oct 04, 2013 2:01 pm
Has thanked: 0 time
Been thanked: 1 time

Re: Android v3.7.3 Official Feedback Thread

Postby ArtVictorP » Tue Oct 22, 2013 2:33 pm

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


Those crashes occur wile you're on mobile data, not wifi right? I haven't figured out a solution besides using the 3.6 version.

Sent from my GT-I9505 using Tapatalk
ArtVictorP
Waze Global Champs
Waze Global Champs
 
Posts: 583
Joined: Wed Jun 16, 2010 4:36 pm
Location: Guayaquil, Ecuador
Has thanked: 597 times
Been thanked: 231 times

Re: Android v3.7.3 Official Feedback Thread

Postby paulkok_my » Tue Oct 22, 2013 2:49 pm

What about trying Version 3.7.2?

Sent from my GT-I9300 using Tapatalk
ImageImageImage
Area Manager: Shah Alam / Klang, Southern Region, Malaysia
Send me a Telegram!
Join our FB group: Peninsular Malaysia, Sabah/Sarawak
or Google+ group: Waze in Malaysia on Google+
paulkok_my
Waze Global Champs
Waze Global Champs
 
Posts: 977
Joined: Thu Jul 19, 2012 4:34 am
Location: Selangor, Malaysia
Has thanked: 194 times
Been thanked: 189 times

PreviousNext

Return to Waze App

Who is online

Users browsing this forum: Google [Bot]