[Galaxy S II Android Development] thunder45:
I believe SI_KERNEL is a memory address violation. Note the fault addr is NULL.

I noticed that any aplication that requests LOCATION causes Play Service to FC. Instagram is one of those. I was taking a deeper look at the FC.

Instagram Starts and service com.google.android.gms/com.google.android.location.network.NetworkLocationService: pid=5320 is invoked

06-13 22:42:46.408 I/ActivityManager(2231): Start proc com.google.android.gms.persistent for service com.google.android.gms/com.google.android.location.network.NetworkLocationService: pid=5320 uid=10015 gids={50015, 3003, 1007, 1028, 1023, 1015, 3002, 3001, 3007, 2001, 3006}

Does the line below mean pid=5320 (location.network.NetworkLocationService) died?? Or was it a clean exit

06-13 22:42:46.678 I/ActivityManager(2231): Exiting empty application process com.google.android.gms.persistent (null)

Almost immediately, com.google.android.gms/.fitness.service.FitnessInitReceiver: pid=5337 is started

06-13 22:42:46.708 I/ActivityManager(2231): Start proc com.google.android.gms.persistent for broadcast com.google.android.gms/.fitness.service.FitnessInitReceiver: pid=5337 uid=10015 gids={50015, 3003, 1007, 1028, 1023, 1015, 3002, 3001, 3007, 2001, 3006}

Here are some warnings from pid=5320 (location.network.NetworkLocationService). I don`t know what those mean.

06-13 22:42:47.923 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:47.928 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:47.928 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8

Then we have a couple of logs which apparently have nothing to do with the problem

--------- beginning of /dev/log/main
06-13 22:42:48.183 E/AuthorizationBluetoothService(2666): Proximity feature is not enabled.
06-13 22:42:48.183 D/GCM (2666): GcmService start Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.gcm.GcmService } com.google.android.gms.INITIALIZE
06-13 22:42:48.188 D/exynos_camera(1858): Found 8 preview buffers available!
06-13 22:42:48.188 V/GmsCoreStatsServiceLauncher(20395): Received broadcast intent Intent { act=com.google.android.gms.INITIALIZE flg=0x10 pkg=com.google.android.gms cmp=com.google.android.gms/.common.stats.GmsCoreStatsServiceLauncher }

And so we have some logs from pid=5320 itself. Not sure if here is where the problem starts:

06-13 22:42:48.203 I/dalvikvm(5320): Could not find method android.content.pm.PackageManager.getPackageInstaller, referenced from method com.google.android.gms.common.ij.a
06-13 22:42:48.203 W/dalvikvm(5320): VFY: unable to resolve virtual method 449: Landroid/content/pm/PackageManager;.getPackageInstaller ()Landroid/content/pm/PackageInstaller;
06-13 22:42:48.203 D/dalvikvm(5320): VFY: replacing opcode 0x6e at 0x000d
06-13 22:42:48.218 I/dalvikvm(5320): Could not find method android.app.Notification$Builder.setLocalOnly, referenced from method com.google.android.gms.common.ij.b
06-13 22:42:48.218 W/dalvikvm(5320): VFY: unable to resolve virtual method 154: Landroid/app/Notification$Builder;.setLocalOnly (Z)Landroid/app/Notification$Builder;
06-13 22:42:48.218 D/dalvikvm(5320): VFY: replacing opcode 0x6e at 0x0201

Here we have two logs from pid=5337 (fitness.service.FitnessInitReceiver), and another log in the middle of them which is probably related to 5320

06-13 22:42:48.228 E/MDM (5337): [1067] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}
06-13 22:42:48.248 D/LocationInitializer(20395): Restart initialization of location
06-13 22:42:48.253 E/MDM (5337): [1070] b.run: Couldn't connect to Google API client: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null}

Again some warnings from pid=5320 (location.network.NetworkLocationService). I don`t know what those mean.

06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.368 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.373 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8
06-13 22:42:48.373 W/ActivityManager(2231): Can't find mystery application for StrictMode from pid=5320 uid=10015: android.os.BinderProxy@428ccae8

Then, a couple more logs from pid=5320 (location.network.NetworkLocationService). Is that the root cause of the problem?

06-13 22:42:48.418 I/dalvikvm(5320): Could not find method android.os.UserHandle.isOwner, referenced from method com.google.android.location.internal.server.n.e
06-13 22:42:48.418 W/dalvikvm(5320): VFY: unable to resolve virtual method 1619: Landroid/os/UserHandle;.isOwner ()Z
06-13 22:42:48.418 D/dalvikvm(5320): VFY: replacing opcode 0x6e at 0x00a7
06-13 22:42:48.468 V/GmsNetworkLocationProvi(5320): ENABLE
06-13 22:42:48.473 V/GmsNetworkLocationProvi(5320): SET-REQUEST
06-13 22:42:48.473 V/GmsNetworkLocationProvi(5320): in Handler: ProviderRequestUnbundled, reportLocation is true and interval is 20000

The following also doesn`t seem to relate to the problem.

06-13 22:42:48.628 E/exynos_camera(1858): exynos_camera_preview_thread: Starting thread
06-13 22:42:48.668 I/GCoreUlr(7011): Received powerMode change from NLP: com.google.android.location.activity.DEEP_STILL_MODE_DISABLED
06-13 22:42:48.668 I/GCoreUlr(7011): Triggering possible samping update for: PowerModeReceiver
06-13 22:42:48.668 I/GCoreUlr(7011): Starting service, intent=Intent { act=com.google.android.location.reporting.ACTION_UPDATE_ACTIVE_STATE cmp=com.google.android.gms/com.google.android.location.reporting.service.DispatchingService (has extras) }, extras=Bundle[{source=PowerModeReceiver}]
06-13 22:42:48.873 I/GCoreUlr(7011): DispatchingService.updateActiveState+PowerModeReceiver: Ensuring that reporting is active for [account#5#]

And here we get more details of the crash. Again the very same fault addr 0000000:

06-13 22:42:48.723 W/Settings(5320): Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
06-13 22:42:48.798 W/dalvikvm(5320): VFY: unable to find class referenced in signature (Landroid/location/GpsMeasurementsEvent;)
06-13 22:42:48.798 W/dalvikvm(5320): VFY: unable to find class referenced in signature (Landroid/location/GpsNavigationMessageEvent;)
06-13 22:42:48.953 F/libc (5320): Fatal signal 7 (SIGBUS) at 0x00000000 (code=128), thread 5382 (nlp-async-worke)
06-13 22:42:49.058 I/DEBUG (8973): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-13 22:42:49.058 I/DEBUG (8973): Build fingerprint: 'samsung/GT-I9100/GT-I9100:4.1.2/JZO54K:user/release-keys'
06-13 22:42:49.058 I/DEBUG (8973): Revision: '14'
06-13 22:42:49.058 I/DEBUG (8973): pid: 5320, tid: 5382, name: nlp-async-worke >>> com.google.android.gms.persistent <<<
06-13 22:42:49.058 I/DEBUG (8973): signal 7 (SIGBUS), code 128 (SI_KERNEL), fault addr 00000000
06-13 22:42:49.478 I/DEBUG (8973): r0 421377e0 r1 421365ce r2 00000010 r3 00000087
06-13 22:42:49.478 I/DEBUG (8973): r4 421377d8 r5 421365c6 r6 00000001 r7 00000080
06-13 22:42:49.478 I/DEBUG (8973): r8 00000000 r9 1f800005 sl 00000001 fp 00000000
06-13 22:42:49.478 I/DEBUG (8973): ip 417e0d30 sp 581caa84 lr 4f0df053 pc 4f0dee46 cpsr 000d0030
06-13 22:42:49.478 I/DEBUG (8973): d0 0000000000000000 d1 0000000000000000
06-13 22:42:49.478 I/DEBUG (8973): d2 0000000000000000 d3 0000000000000000
06-13 22:42:49.478 I/DEBUG (8973): d4 0a0a030b0e0b0b09 d5 094005fa52090a01
06-13 22:42:49.478 I/DEBUG (8973): d6 120a0b110909090a d7 230b11090a090909
06-13 22:42:49.478 I/DEBUG (8973): d8 0000000000000000 d9 0000000000000000
06-13 22:42:49.478 I/DEBUG (8973): d10 0000000000000000 d11 0000000000000000
06-13 22:42:49.478 I/DEBUG (8973): d12 0000000000000000 d13 0000000000000000
06-13 22:42:49.478 I/DEBUG (8973): d14 0000000000000000 d15 0000000000000000
06-13 22:42:49.478 I/DEBUG (8973): d16 0000000000000000 d17 cb65b84b2f8fba13
06-13 22:42:49.478 I/DEBUG (8973): d18 0000000040b64ccc d19 5291fb5800000000
06-13 22:42:49.478 I/DEBUG (8973): d20 414e848000000000 d21 0000000000000010
06-13 22:42:49.478 I/DEBUG (8973): d22 4156e36000000000 d23 4008000000000000
06-13 22:42:49.478 I/DEBUG (8973): d24 0000000000004000 d25 fffffffffffffffe
06-13 22:42:49.478 I/DEBUG (8973): d26 991f1f1f991f1f1f d27 991f1f1f991f1f1f
06-13 22:42:49.478 I/DEBUG (8973): d28 0707070703030303 d29 4114585555555555
06-13 22:42:49.478 I/DEBUG (8973): d30 3ff0000000000000 d31 3ff0000000000000
06-13 22:42:49.478 I/DEBUG (8973): scr 80000010
06-13 22:42:49.483 I/DEBUG (8973):
06-13 22:42:49.483 I/DEBUG (8973): backtrace:
06-13 22:42:49.483 I/DEBUG (8973): #00 pc 0001de46 /system/lib/libjavacore.so
06-13 22:42:49.483 I/DEBUG (8973): #01 pc 0001e04f /system/lib/libjavacore.so
06-13 22:42:49.483 I/DEBUG (8973): #02 pc 0001e880 /system/lib/libdvm.so (dvmPlatformInvoke+116)
06-13 22:42:49.483 I/DEBUG (8973): #03 pc 000597f7 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+170)
06-13 22:42:49.483 I/DEBUG (8973): #04 pc 00027ca0 /system/lib/libdvm.so
06-13 22:42:49.483 I/DEBUG (8973): #05 pc 0002ea80 /system/lib/libdvm.so (dvmMterpStd(Thread*)+68)
06-13 22:42:49.483 I/DEBUG (8973): #06 pc 0002c328 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+180)
06-13 22:42:49.483 I/DEBUG (8973): #07 pc 0007115d /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+284)
06-13 22:42:49.483 I/DEBUG (8973): #08 pc 000711e9 /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
06-13 22:42:49.483 I/DEBUG (8973): #09 pc 000627eb /system/lib/libdvm.so
06-13 22:42:49.483 I/DEBUG (8973): #10 pc 0000d490 /system/lib/libc.so (__thread_entry+72)
06-13 22:42:49.483 I/DEBUG (8973): #11 pc 0000d62c /system/lib/libc.so (pthread_create+244)
06-13 22:42:49.483 I/DEBUG (8973):
06-13 22:42:49.483 I/DEBUG (8973): stack:
06-13 22:42:49.483 I/DEBUG (8973): 581caa44 00000010
06-13 22:42:49.483 I/DEBUG (8973): 581caa48 4cc456d0 /dev/ashmem/dalvik-LinearAlloc (deleted)
06-13 22:42:49.488 I/DEBUG (8973): 581caa4c 581caa60
06-13 22:42:49.488 I/DEBUG (8973): 581caa50 417e555c /system/lib/libdvm.so
06-13 22:42:49.488 I/DEBUG (8973): 581caa54 417e555c /system/lib/libdvm.so
06-13 22:42:49.488 I/DEBUG (8973): 581caa58 421377c8 /dev/ashmem/dalvik-heap (deleted)
06-13 22:42:49.488 I/DEBUG (8973): 581caa5c 417e51f8 /system/lib/libdvm.so
06-13 22:42:49.488 I/DEBUG (8973): 581caa60 00000008
06-13 22:42:49.488 I/DEBUG (8973): 581caa64 417685bb /system/lib/libdvm.so
06-13 22:42:49.488 I/DEBUG (8973): 581caa68 00000000
06-13 22:42:49.488 I/DEBUG (8973): 581caa6c 00000000
06-13 22:42:49.488 I/DEBUG (8973): 581caa70 1f800005
06-13 22:42:49.488 I/DEBUG (8973): 581caa74 529154b0
06-13 22:42:49.488 I/DEBUG (8973): 581caa78 00000000
06-13 22:42:49.488 I/DEBUG (8973): 581caa7c 421377c8 /dev/ashmem/dalvik-heap (deleted)
06-13 22:42:49.488 I/DEBUG (8973): 581caa80 529154b0
06-13 22:42:49.488 I/DEBUG (8973): #00 581caa84 5291d7d8
06-13 22:42:49.488 I/DEBUG (8973): 581caa88 1eb00009
06-13 22:42:49.488 I/DEBUG (8973): 581caa8c 421364e0 /dev/ashmem/dalvik-heap (deleted)
06-13 22:42:49.488 I/DEBUG (8973): 581caa90 00000008
06-13 22:42:49.488 I/DEBUG (8973): 581caa94 421377d8 /dev/ashmem/dalvik-heap (deleted)
06-13 22:42:49.488 I/DEBUG (8973): 581caa98 1f800005
06-13 22:42:49.488 I/DEBUG (8973): 581caa9c 00000001
06-13 22:42:49.488 I/DEBUG (8973): #01 581caaa0 00000001
06-13 22:42:49.488 I/DEBUG (8973): 581caaa4 42137b48 /dev/ashmem/dalvik-heap (deleted)
06-13 22:42:49.488 I/DEBUG (8973): 581caaa8 00000080
06-13 22:42:49.488 I/DEBUG (8973): 581caaac 000000e6
06-13 22:42:49.488 I/DEBUG (8973): 581caab0 00000000
06-13 22:42:49.488 I/DEBUG (8973): 581caab4 529154c0
06-13 22:42:49.488 I/DEBUG (8973): 581caab8 4c89be00 /dev/ashmem/dalvik-LinearAlloc (deleted)
06-13 22:42:49.488 I/DEBUG (8973): 581caabc 00000000
06-13 22:42:49.488 I/DEBUG (8973): 581caac0 52937dbc
06-13 22:42:49.488 I/DEBUG (8973): 581caac4 581caaec
06-13 22:42:49.488 I/DEBUG (8973): 581caac8 52937da0
06-13 22:42:49.488 I/DEBUG (8973): 581caacc 0000000c
06-13 22:42:49.488 I/DEBUG (8973): 581caad0 581cab04
06-13 22:42:49.488 I/DEBUG (8973): 581caad4 41736884 /system/lib/libdvm.so (dvmPlatformInvoke+120)
06-13 22:42:49.488 I/DEBUG (8973): #02 581caad8 00000080
06-13 22:42:49.488 I/DEBUG (8973): 581caadc 1eb00009
06-13 22:42:49.488 I/DEBUG (8973): 581caae0 000000e6
06-13 22:42:49.488 I/DEBUG (8973): 581caae4 00000008
06-13 22:42:49.488 I/DEBUG (8973): 581caae8 00000001
06-13 22:42:49.488 I/DEBUG (8973): 581caaec 417e0c80 /system/lib/libdvm.so
06-13 22:42:49.488 I/DEBUG (8973): 581caaf0 4f0deffd /system/lib/libjavacore.so
06-13 22:42:49.488 I/DEBUG (8973): 581caaf4 529154b0
06-13 22:42:49.488 I/DEBUG (8973): 581caaf8 00000001
06-13 22:42:49.488 I/DEBUG (8973): 581caafc 52937da0
06-13 22:42:49.488 I/DEBUG (8973): 581cab00 20200001
06-13 22:42:49.488 I/DEBUG (8973): 581cab04 417717fb /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+174)
06-13 22:42:49.493 I/DEBUG (8973):

blahblahblah

06-13 22:42:49.818 D/Zygote (1856): Process 5320 terminated by signal (7)

And here, GPS is scheduled to restart, note the location services

06-13 22:42:49.898 I/ActivityManager(2231): Process com.google.android.gms.persistent (pid 5320) has died.
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/com.google.android.location.network.NetworkLocationService in 16000ms
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/com.google.android.location.fused.FusedLocationService in 176000ms
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/com.google.android.location.geocode.GeocodeService in 336000ms
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/com.google.android.location.fused.service.FusedProviderService in 496000ms
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/com.google.android.location.geofencer.service.GeofenceProviderService in 656000ms
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/.deviceconnection.service.DeviceConnectionServiceBroker in 816000ms
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService in 976000ms
06-13 22:42:49.898 W/ActivityManager(2231): Scheduling restart of crashed service com.google.android.gms/.common.stats.GmsCoreStatsService in 1136000ms
06-13 22:42:49.933 W/LocationProviderProxy(2231): android.os.DeadObjectException
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at android.os.BinderProxy.transact(Native Method)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at com.android.internal.location.ILocationProvider$Stub$Proxy.setRequest(ILocationProvider.java:215)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at com.android.server.location.LocationProviderProxy.setRequest(LocationProviderProxy.java:209)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at com.android.server.LocationManagerService.applyRequirementsLocked(LocationManagerService.java:1268)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at com.android.server.LocationManagerService.removeUpdatesLocked(LocationManagerService.java:1560)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at com.android.server.LocationManagerService.removeUpdates(LocationManagerService.java:1522)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at android.location.ILocationManager$Stub.onTransact(ILocationManager.java:89)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at android.os.Binder.execTransact(Binder.java:404)
06-13 22:42:49.933 W/LocationProviderProxy(2231):	at dalvik.system.NativeStart.run(Native Method)

This NULL address could be due to optmization, but I don`t really think that is the case here. More likely, GPS is expecting some object or service that this build cannot provide.

The following two lines are calling my attention:

06-13 22:42:48.798 W/dalvikvm(5320): VFY: unable to find class referenced in signature (Landroid/location/GpsMeasurementsEvent;)

06-13 22:42:48.798 W/dalvikvm(5320): VFY: unable to find class referenced in signature (Landroid/location/GpsNavigationMessageEvent;)

But I really don`t know what to do with that. Are those new services? Or services that have been changed recently?

Regards