Android 4.2 issues

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: krankyd, Unholy

Re: Android 4.2 issues

Postby mendesmartini » Wed Dec 05, 2012 11:53 am

mpawlicki wrote:All I get is a Waze splash screen and then it quits, no errors and it does not show running in Recent menu. I tried reinstalling, wiping cache and wiping data, also manually removing the waze folder from SD card. Same result each time.


Exactly the same issue with me.

I already tried reinstall, wipe cache, wipe data, wipe dalvik, fix permissions, and even manual removal of Waze files. Nothing helped.

I'm using Android 4.1.2, Cyagnogen(Mod) on a Galaxy Tab 10.1.
Carlos Martini
E-mail: carlos AT mendesmartini.com
Blog: http://mendesmartini.com
Image Image Image : /mendesmartini
mendesmartini
 
Posts: 2
Joined: Sun May 13, 2012 4:25 pm
Location: Florianopolis, SC, Brazil
Has thanked: 0 time
Been thanked: 0 time

Re: Android 4.2 issues

Postby mendesmartini » Thu Dec 06, 2012 9:34 am

majic12 wrote:I have no issues on android 4.2...
I did have issues though when i re-installed the app through titanium backup but i deleted waze... re installed and its been flawless


I tried this procedure:

- Wiped dalvik
- Wiped cache;
- Wiped data;
- Manually removed remaining Waze files;
- Reinstalled Waze by Play Store (I never use backup for this).

The problem continues... :cry:
Carlos Martini
E-mail: carlos AT mendesmartini.com
Blog: http://mendesmartini.com
Image Image Image : /mendesmartini
mendesmartini
 
Posts: 2
Joined: Sun May 13, 2012 4:25 pm
Location: Florianopolis, SC, Brazil
Has thanked: 0 time
Been thanked: 0 time

Android 4.2 issues

Postby mpawlicki » Mon Nov 26, 2012 12:55 am

I can't get Waze to launch in Jelly Bean 4.2. Not the current stable release nor any of the released betas. Can anyone else running 4.2 tell me if they have same issues or if it's just me? I'm on Galaxy Nexus.
Image
mpawlicki
 
Posts: 79
Joined: Thu Jul 12, 2012 3:16 pm
Location: Columbus, OH, USA
Has thanked: 2 times
Been thanked: 5 times

Re: Android 4.2 issues

Postby mpawlicki » Mon Nov 26, 2012 12:59 pm

All I get is a Waze splash screen and then it quits, no errors and it does not show running in Recent menu. I tried reinstalling, wiping cache and wiping data, also manually removing the waze folder from SD card. Same result each time.
Image
mpawlicki
 
Posts: 79
Joined: Thu Jul 12, 2012 3:16 pm
Location: Columbus, OH, USA
Has thanked: 2 times
Been thanked: 5 times

Re: Android 4.2 issues

Postby mpawlicki » Tue Nov 27, 2012 1:52 am

So, it's working for me now. I'm running a custom ROM and after released update everything works fine.
Hope your's will too soon, stjohnh.
Image
mpawlicki
 
Posts: 79
Joined: Thu Jul 12, 2012 3:16 pm
Location: Columbus, OH, USA
Has thanked: 2 times
Been thanked: 5 times

Re: Android 4.2 issues

Postby mpawlicki » Wed Dec 05, 2012 11:43 pm

I am on AOKP, seems all my issues were resolved with the ROM update itself.
Image
mpawlicki
 
Posts: 79
Joined: Thu Jul 12, 2012 3:16 pm
Location: Columbus, OH, USA
Has thanked: 2 times
Been thanked: 5 times

Re: Android 4.2 issues

Postby nswint » Mon Nov 26, 2012 3:12 am

It's worked for me on my Galaxy Nexus on upgrade from 4.1.2 and on a fresh install.

What problems are you having?
Waze 3.5.1.3 on Samsung Galaxy Nexus (Android 4.2)
nswint
 
Posts: 3
Joined: Sun May 13, 2012 9:37 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Android 4.2 issues

Postby rwyatt365 » Mon Sep 09, 2013 11:53 am

I just got a Nexus 7 (2013), and installed Waze. It will start, and present the login screen but it ALWAYS reports that I've put in the wrong password - even when I reset the password! It's a stock Nexus 7 running version 4.2.
rwyatt365
 
Posts: 1
Joined: Mon Apr 30, 2012 12:23 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Android 4.2 issues

Postby stjohnh » Mon Nov 26, 2012 7:50 pm

Main navigation screen doesn't work on my Nexus 7 tablet, worked fine w Android 4.1
stjohnh
 
Posts: 1
Joined: Sun Aug 26, 2012 5:50 am
Has thanked: 0 time
Been thanked: 0 time

Re: Android 4.2 issues

Postby Xuefer » Sat May 18, 2013 4:49 pm

1028}
I/ActivityManager( 539): START u0 {cmp=com.waze/.MainActivity} from pid 31711
D/WAZE.FBWrapper(31711): New session created. Current state: CREATED
W/WAZE DEBUG(31711): ON RESUME. Task id: 53
D/WAZE (31711): Previous active activity: null
D/WAZE (31711): Current active activity: class com.waze.MainActivity
W/WAZE (31711): MapView onResume
W/WAZE (31711): MapView Surface changed: 1024, 695.
W/WAZE (31711): OGL RENDERER SURFACE CREATED
W/WAZE (31711): OGL RENDERER SURFACE CHANGED ( 1024 , 695 )
W/WAZE (31711): MapView Surface changed completed
I/ActivityManager( 539): Displayed com.waze/.MainActivity: +633ms (total +980ms)
D/WAZE_Service(31711): Setting the service to be foreground
I/WAZE (31711): Available space at /sdcard: 6380388352
D/WAZE_PIONEER(31711): Pioneer app mode enabled - will start when Waze will be fully initialized.
W/WAZE (31711): Native thread is running
D/WAZE (31711): Before changing native thread priority, current priority is 0
I/WAZE_Service(31711): Service Created. Instance: com.waze.AppService@2bbdc970
I/WAZE_Service(31711): Start service is called com.waze.AppService@2bbdc970
D/WAZE (31711): Resources extraction unnecessary
D/dalvikvm(31711): Trying to load lib /data/app-lib/com.waze-1/libwaze.so 0x2b795d38
D/dalvikvm(31711): Added shared lib /data/app-lib/com.waze-1/libwaze.so 0x2b795d38
D/dalvikvm(31711): No JNI_OnLoad found in /data/app-lib/com.waze-1/libwaze.so 0x2b795d38, skipping init
I/WAZE (31711): Library is loaded
D/WAZE.LOCATION_LISTENER(31711): Starting location listener
E/WAZE (31711): com.waze.MainActivity@2b7d4a20
I/DEBUG ( 139): pid: 31711, tid: 31732, name: Native Thread >>> com.waze <<<
I/DEBUG ( 139): #00 pc 0010d970 /data/app-lib/com.waze-1/libwaze.so (hash_find+16)
I/DEBUG ( 139): #01 pc 0010e68c /data/app-lib/com.waze-1/libwaze.so (config_set+76)
I/DEBUG ( 139): #02 pc 000b1450 /data/app-lib/com.waze-1/libwaze.so (core_config_set_closed_properly+16)
I/DEBUG ( 139): #03 pc 00068128 /data/app-lib/com.waze-1/libwaze.so (Java_com_waze_NativeManager_ClosedProperlyNTV+40)
I/DEBUG ( 139): #00 50a06bc0 50c6e710 /data/app-lib/com.waze-1/libwaze.so
I/DEBUG ( 139): 50a06bc4 50bfb734 /data/app-lib/com.waze-1/libwaze.so
I/DEBUG ( 139): 50a06bc8 50c71260 /data/app-lib/com.waze-1/libwaze.so
I/DEBUG ( 139): 50a06bcc 50c71260 /data/app-lib/com.waze-1/libwaze.so
I/DEBUG ( 139): 50a06bd4 50b16690 /data/app-lib/com.waze-1/libwaze.so (config_set+80)
I/DEBUG ( 139): 50a06c04 50ab9454 /data/app-lib/com.waze-1/libwaze.so (core_config_set_closed_properly+20)
I/DEBUG ( 139): 50a06c0c 50a7012c /data/app-lib/com.waze-1/libwaze.so (Java_com_waze_NativeManager_ClosedProperlyNTV+44)
W/InputDispatcher( 539): channel '2bd76518 com.waze/com.waze.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
E/InputDispatcher( 539): channel '2bd76518 com.waze/com.waze.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
I/ActivityManager( 539): Process com.waze (pid 31711) has died.
W/ActivityManager( 539): Scheduling restart of crashed service com.waze/.AppService in 5000ms
W/ActivityManager( 539): Force removing ActivityRecord{2c4613f8 u0 com.waze/.MainActivity}: app died, no saved state
W/InputDispatcher( 539): Attempted to unregister already unregistered input channel '2bd76518 com.waze/com.waze.MainActivity (server)'
I/WindowState( 539): WIN DEATH: Window{2bd76518 u0 com.waze/com.waze.MainActivity}
^C
130|root@android:/ #


cm 10.1-20130408-unofficial-tenderlion (touchpad) 4.2.2 kernel 2.6.35
please fix it asap

however not reproduced with cm-10.1-20130517-unofficial-epinter-olympus (atrix4g)
Xuefer
 
Posts: 10
Joined: Sun Apr 14, 2013 6:11 am
Has thanked: 0 time
Been thanked: 1 time

Previous

Return to Waze App

Who is online

Users browsing this forum: Bing [Bot], Google Feedfetcher