I just upgraded my Galaxy S3 from 4.3.x to 4.4.2. Waze was previously installed and worked fine. Now, it cannot connect to the network. Continuously says it's searching for the network. I've tried both the cellular network and wifi with the same problem. All other apps are having no problems.
There's a bug regarding how this app is using the GPS, at least on my Nexus 5. I'm a new user and have no idea if this is something new or and old bug but nevertheless it's an annoying bug.
Whenever this app is running, it's preventing other apps from using the GPS. I love to be helping out by adding roads and tracks when I'm out geocaching, but this app is not allowing it to work smoothly enough.
Just to show the difference, install the 2 free apps OSM-tracker for Android and c:geo. You will be able to run both of them at the same time recording all the tracks to upload it to the openstreetmap network when done and still use cgeo for geocaching. With waze running in the background no other apps will be allowed to use the gps in cgeo at all.
Whenever this app is running, it's preventing other apps from using the GPS. I love to be helping out by adding roads and tracks when I'm out geocaching, but this app is not allowing it to work smoothly enough.
Just to show the difference, install the 2 free apps OSM-tracker for Android and c:geo. You will be able to run both of them at the same time recording all the tracks to upload it to the openstreetmap network when done and still use cgeo for geocaching. With waze running in the background no other apps will be allowed to use the gps in cgeo at all.
https://wiki.waze.com/wiki/images/c/c1/ ... Tester.png
Nexus 5X - Android 8.1.0
Nexus 5X - Android 8.1.0
Same phone (xt890), same problem
Code: Select all
C_CODE|943365720|italiano|normal|4.1.2-SDK16|motorola|XT890|smi|Received signal SIGSEGV 11. Fault address: 59f0e007. Error: 0. Code: 2. Thread: 0x5305bb30. PC: 0x3a43ef04Registers:
R0 59f09060 R1 59f0e000 R2 59f09130 R3 6094d0d1 R4 0719da4b R5 c7429b80 R6 e773bd1d
R7 eb1ab14c R8 59079dc8 R9 6600828e R10 e173a6e6
fp e099c8d2 ip 0040a2c2 sp 100ffb58 lr 3a43ec30 pc 3a43ef04 [0003ef04 /system/lib/arm/libcrypto.so] cpsr 10000000 fault 00000000
Stack data: Flags: 100ff998, Size: 0, SP: 3a515d94
100ffb58 : 00000000
100ffb5c : 00000000
100ffb60 : e6a59e9e
100ffb64 : 1048f3d2
100ffb68 : 6748c2ef
100ffb6c : e173a6e6
100ffb70 : 7cbf4b23
100ffb74 : e099c8d2
100ffb78 : 474370b8
100ffb7c : c82b88f9
100ffb80 : 2278906c
100ffb84 : 8452cae2
100ffb88 : 6234dd8d
100ffb8c : 6ffefe79
100ffb90 : b6f7e8cd
100ffb94 : 23479d1f
100ffb98 : 80a74fd5
100ffb9c : f3db1748
100ffba0 : 07000000
100ffba4 : 07000000
100ffba8 : 07000000
100ffbac : 07000000
100ffbb0 : 07000000
100ffbb4 : 00000000
100ffbb8 : 00000000
100ffbbc : 00000000
100ffbc0 : 01000000
100ffbc4 : d0ff4959
100ffbc8 : 00d00200
100ffbcc : 0010ee59
100ffbd0 : 0dd563c6
100ffbd4 : e391e204
100ffbd8 : 31a9664a
100ffbdc : c3dc109e
100ffbe0 : bdc3b2b4
100ffbe4 : 8f8c8cbb
100ffbe8 : 23a1b5d9
100ffbec : 531f2e0d
100ffbf0 : 59f09060
100ffbf4 : 00000005
100ffbf8 : 5b40f054
100ffbfc : 59f090b0
100ffc00 : 00000040
100ffc04 : 00000000
100ffc08 : 59f08e70
100ffc0c : 00000000
100ffc10 : 3a522c48
100ffc14 : 3a4cf298 [000cf298 /system/lib/arm/libcrypto.so]
100ffc18 : 3a4a4460 [000a4460 /system/lib/arm/libcrypto.so]
100ffc1c : 5b27eed0
100ffc20 : 3936e374
100ffc24 : 5b40f05d
100ffc28 : 3a51f07c
100ffc2c : 00000100
100ffc30 : 5b40f014
100ffc34 : 3a49eb70 [0009eb70 /system/lib/arm/libcrypto.so]
100ffc38 : 59f09060
100ffc3c : 3a21d4c8 [0001d4c8 /system/lib/arm/libssl.so]
100ffc40 : 5b1f94f0
100ffc44 : 100ffc6c
100ffc48 : 00000005
100ffc4c : 100ffcf0
100ffc50 : 5b40f05d
100ffc54 : 00000045
100ffc58 : 59c88a20
100ffc5c : 00000005
100ffc60 : 59f089c0
100ffc64 : 5b1f94f0
100ffc68 : 00000100
100ffc6c : 00000001
100ffc70 : 3a51f07c
100ffc74 : 00000000
100ffc78 : 00000000
100ffc7c : 59f09060
100ffc80 : 00000000
100ffc84 : 3a4a4460 [000a4460 /system/lib/arm/libcrypto.so]
100ffc88 : 5b4198b0
100ffc8c : 3a4d1150 [000d1150 /system/lib/arm/libcrypto.so]
100ffc90 : 00000001
100ffc94 : 3a441f70 [00041f70 /system/lib/arm/libcrypto.so]
100ffc98 : 3a51611c
100ffc9c : 3a4567b8 [000567b8 /system/lib/arm/libcrypto.so]
100ffca0 : 5b4198f0
100ffca4 : 3a528614
100ffca8 : 00000001
100ffcac : 5b449020
100ffcb0 : 00000003
100ffcb4 : 5b449020
100ffcb8 : 00000c55
100ffcbc : 00000c55
100ffcc0 : 00000000
100ffcc4 : 3a441ce4 [00041ce4 /system/lib/arm/libcrypto.so]
100ffcc8 : 0001352c
100ffccc : 3a4d1194 [000d1194 /system/lib/arm/libcrypto.so]
100ffcd0 : 5b4198f0
100ffcd4 : 3a4d1150 [000d1150 /system/lib/arm/libcrypto.so]
100ffcd8 : 100ffcf0
100ffcdc : 3a4da924 [000da924 /system/lib/arm/libcrypto.so]
100ffce0 : 5b27eed0
100ffce4 : 3a22d21c [0002d21c /system/lib/arm/libssl.so]
100ffce8 : 00000000
100ffcec : 00000000
100ffcf0 : 59ec05d0
100ffcf4 : 00000000
100ffcf8 : 5b1f2fc0
100ffcfc : 5b449020
100ffd00 : 00000000
100ffd04 : 00000000
100ffd08 : 00000000
100ffd0c : 3a4d943c [000d943c /system/lib/arm/libcrypto.so]
100ffd10 : 3a4d81fc [000d81fc /system/lib/arm/libcrypto.so]
100ffd14 : 3a4d658c [000d658c /system/lib/arm/libcrypto.so]
100ffd18 : 3a4d8398 [000d8398 /system/lib/arm/libcrypto.so]
100ffd1c : 3a4d9158 [000d9158 /system/lib/arm/libcrypto.so]
100ffd20 : 00000000
100ffd24 : 3a4da9dc [000da9dc /system/lib/arm/libcrypto.so]
100ffd28 : 3a4d8524 [000d8524 /system/lib/arm/libcrypto.so]
100ffd2c : 3a4d83f0 [000d83f0 /system/lib/arm/libcrypto.so]
100ffd30 : 3a4d5f0c [000d5f0c /system/lib/arm/libcrypto.so]
100ffd34 : 3a4d60d8 [000d60d8 /system/lib/arm/libcrypto.so]
100ffd38 : 59f08e78
100ffd3c : 3a4f3aa0 [000f3aa0 /system/lib/arm/libcrypto.so]
100ffd40 : 59f08e78
100ffd44 : 3a502158 [00102158 /system/lib/arm/libcrypto.so]
100ffd48 : 0000000a
100ffd4c : 00000001
100ffd50 : 00000189
100ffd54 : 3a43f8c0 [0003f8c0 /system/lib/arm/libcrypto.so]
100ffd58 : 5b27eed0
100ffd5c : 00000001
100ffd60 : 0000000
Thank you for the update, i've just reinstalled 3.7.0.0 from a backup and still no errors
After a couple of restart I have the same problem even with 3.7.0.0 only if the data connection is activated
Inviato dal mio XT890 utilizzando Tapatalk
Inviato dal mio XT890 utilizzando Tapatalk
Last edited by blknit on Thu Mar 13, 2014 3:57 pm, edited 1 time in total.
- Device Info -
Phone model: Xperia U [ST25i]
ROM version: Z2 Sirius Xperience V1 (url: http://forum.xda-developers.com/xperia- ... e-t2725846) based on XU AOSX V1 (url: http://forum.xda-developers.com/xperia- ... m-t2716190)
Kernel version: 3.0.101_by_Munjeni_and_AOSX-g8cf2b99 (24/04/14)
- Problem -
The App crash at start for error with the OpenGLRenderer
Catlog: https://drive.google.com/file/d/0ByVAIG ... sp=sharing
Phone model: Xperia U [ST25i]
ROM version: Z2 Sirius Xperience V1 (url: http://forum.xda-developers.com/xperia- ... e-t2725846) based on XU AOSX V1 (url: http://forum.xda-developers.com/xperia- ... m-t2716190)
Kernel version: 3.0.101_by_Munjeni_and_AOSX-g8cf2b99 (24/04/14)
- Problem -
The App crash at start for error with the OpenGLRenderer
Catlog: https://drive.google.com/file/d/0ByVAIG ... sp=sharing
[img]https:///yg4dV[/img]
Phone Razr M
Carrier Verizon
App force closes when stopped, maybe when trying to load an ad?
Anyone else with this issue?
Carrier Verizon
App force closes when stopped, maybe when trying to load an ad?
Anyone else with this issue?
Hi,
I'm Running Android 4.4.2 on a Motorola Droid RAZR M, running Waze 3.7.8.0.
I've got 2 issues:
1. Major - No voice direction prompts. When I first joined Waze ~2 months ago (before Android Update) all good. Then update, then loss of some direction prompts and now no verbal directions at all. I searched the Wiki and tried the uninstall/re-install fix - no improvement. The only time it has worked correctly since Android update is during a speaker phone call...I had Waze and the call both using the speaker simultaneously.
2. less annoying - when sharing a drive the email option works fine but the txt option does not. Waze creates a text message, but does not populate the message with the link to the drive.
My wife's RAZR M has similar issues...the difference? Her voice prompts for accidents and obstacles still work but no directions.
Thanks for any feedback.
I'm Running Android 4.4.2 on a Motorola Droid RAZR M, running Waze 3.7.8.0.
I've got 2 issues:
1. Major - No voice direction prompts. When I first joined Waze ~2 months ago (before Android Update) all good. Then update, then loss of some direction prompts and now no verbal directions at all. I searched the Wiki and tried the uninstall/re-install fix - no improvement. The only time it has worked correctly since Android update is during a speaker phone call...I had Waze and the call both using the speaker simultaneously.
2. less annoying - when sharing a drive the email option works fine but the txt option does not. Waze creates a text message, but does not populate the message with the link to the drive.
My wife's RAZR M has similar issues...the difference? Her voice prompts for accidents and obstacles still work but no directions.
Thanks for any feedback.
Brian
Update: I found this thread with 2 suggested solutions to the "No Verbal Directions" issues reported here and on other threads:
viewtopic.php?f=3&t=93070#p782015
1st solution restored the "OK, Let's get started" but no other verbal directions...I'll be trying the second later today.
viewtopic.php?f=3&t=93070#p782015
1st solution restored the "OK, Let's get started" but no other verbal directions...I'll be trying the second later today.
Brian
Further update...tried the delete files and reload fix from the above thread - no resolution.Brian-D-N wrote:Update: I found this thread with 2 suggested solutions to the "No Verbal Directions" issues reported here and on other threads:
viewtopic.php?f=3&t=93070#p782015
1st solution restored the "OK, Let's get started" but no other verbal directions...I'll be trying the second later today.
Also tried the uncheck the use speaker box - no resolution
Also tried to reboot phone - no resolution.
That's 4 different fix attempts on the "no audio directions" bug on a Motorola RAZR M running Kitkat 4.4 & Waze 3.7.8.0 with no resolution. Have I missed any? I would love for this app to be fully functional again. I miss the traffic rerouting
EDIT - Powering down the phone, turning it on and then unchecking the send to speaker box worked...on one phone. But no "let's get started" when you launch navigating a route...
Last edited by Brian-D-N on Tue Jun 03, 2014 2:03 pm, edited 1 time in total.
Brian
Re: Android v3.7.8.0 Official Feedback Thread