The Random Reboot

R

RandomBob

New Member
Joined
Jan 29, 2012
Messages
1
Reaction score
0
Hello,
I recently figured out what was causing some random restarts and boot loops for my RAZR and thought I would share what I found here. Perhaps if someone else has the same issue, they will find this usefill.
Basically my RAZR would randomly restart. Once it did it would go into boot loop until I did a hard reset( vol down and power). Then it would run fine for a while until it did that again. After trying to install and uninstall damn near each app with no change, I finally got an app to record the logcat when it was happening. The following is the log just before a crash:

Code: 
01-25 21:09:38.907 D/IMSCLIENT(14353): TransactionObject.c:5244:          0x1 TRANSACTION : INFO  - TransactionChangeState - Transaction 0x0x249310: state changed to Client General Request Sent
01-25 21:09:38.907 D/IMSCLIENT(14353): RvSipRegClient.c:478:      0x1 REG_CLIENT  : INFO  - RvSipRegClientRegister - Register client 0x0x24e558: REGISTER request was successfully sent
01-25 21:09:38.907 W/IMSCLIENT(14353): IMS_OSservice.cpp:369: Critical Region ID (0) has not created.
01-25 21:09:38.907 W/IMSCLIENT(14353): IMS_OSservice.cpp:414: Critical Region ID (0) has not created.
01-25 21:09:38.907 V/IMSCLIENT(14353): IMS_ENG_registration.cpp:567: IMS_ENG_registration::ClientStateChanged new state 2 reason 0
01-25 21:09:38.938 D/dalvikvm(14790): GC_FOR_MALLOC freed 456K, 63% free 1785K/4803K, external 2500K/2964K, paused 15ms
01-25 21:09:38.938 I/dalvikvm-heap(14790): Grow heap (frag case) to 5.000MB for 74770-byte allocation
01-25 21:09:38.954 I/BlurServiceMother(14293): onCreate() called
01-25 21:09:38.954 D/dalvikvm(14293): GC_CONCURRENT freed 195K, 61% free 582K/1475K, external 1945K/2087K, paused 1ms+0ms
01-25 21:09:38.961 I/ServiceManager(  365): service 'SurfaceFlinger' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'sensorservice' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'usagestats' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'cpuinfo' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'entropy' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'power' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'DeviceManager3LM' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'batteryinfo' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'telephony.registry' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'meminfo' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'activity' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'permission' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'alarm' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'package' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'account' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'backup' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'content' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'deepsleep' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'battery' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'vibrator' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'hardware' died
01-25 21:09:38.961 I/ServiceManager(  365): service 'window' died
01-25 21:09:38.961 I/ActivityThread(14655): Removing dead content provider: settings
01-25 21:09:38.969 I/ServiceManager(  365): service 'wifi' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'bluetooth' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'bluetooth_a2dp' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'bluetooth_hid' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'bluetooth_pan' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'mot_device_policy' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'bluetooth_dun' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'bluetooth_gatt' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'device_policy' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'mot_encryption_service' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'statusbar' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'clipboard' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'input_method' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'netstat' died
01-25 21:09:38.969 I/ServiceManager(  365): service 'network_management' died
01-25 21:09:38.969 E/util.Log(14293): failed to find or bind checkin service
01-25 21:09:38.969 E/util.Log(14293): android.os.DeadObjectException
01-25 21:09:38.969 E/util.Log(14293):    at android.os.BinderProxy.transact(Native Method)
01-25 21:09:38.969 E/util.Log(14293):    at android.os.ICheckinService$Stub$Proxy.canLog(ICheckinService.java:158)
01-25 21:09:38.969 E/util.Log(14293):    at android.util.Log.<init>(Log.java:170)
01-25 21:09:38.969 E/util.Log(14293):    at android.util.Log.registerTag(Log.java:245)
01-25 21:09:38.969 E/util.Log(14293):    at com.motorola.blur.service.blur.BlurServiceMother.onCreate(BlurServiceMother.java:389)
01-25 21:09:38.969 E/util.Log(14293):    at android.app.ActivityThread.handleCreateService(ActivityThread.java:2032)
01-25 21:09:38.969 E/util.Log(14293):    at android.app.ActivityThread.access$2500(ActivityThread.java:124)
01-25 21:09:38.969 E/util.Log(14293):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1028)
01-25 21:09:38.969 E/util.Log(14293):    at android.os.Handler.dispatchMessage(Handler.java:99)
01-25 21:09:38.969 E/util.Log(14293):    at android.os.Looper.loop(Looper.java:130)
01-25 21:09:38.969 E/util.Log(14293):    at android.app.ActivityThread.main(ActivityThread.java:3859)
01-25 21:09:38.969 E/util.Log(14293):    at java.lang.reflect.Method.invokeNative(Native Method)
01-25 21:09:38.969 E/util.Log(14293):    at java.lang.reflect.Method.invoke(Method.java:507)
01-25 21:09:38.969 E/util.Log(14293):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:840)
01-25 21:09:38.969 E/util.Log(14293):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:598)
01-25 21:09:38.969 E/util.Log(14293):    at dalvik.system.NativeStart.main(Native Method)
01-25 21:09:38.969 I/ActivityThread(14430): Removing dead content provider: settings
01-25 21:09:38.969 I/ActivityThread(14285): Removing dead content provider: settings
01-25 21:09:38.969 I/ActivityThread(15000): Removing dead content provider: settings
01-25 21:09:38.969 I/ActivityThread(14253): Removing dead content provider: settings
01-25 21:09:38.969 I/ActivityThread(14253): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14577): Removing dead content provider: settings
01-25 21:09:38.969 I/ActivityThread(14454): Removing dead content provider: settings
01-25 21:09:38.969 I/ActivityThread(14655): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14454): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14291): Removing dead content provider: settings
01-25 21:09:38.969 I/ActivityThread(14298): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14291): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14334): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14297): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14577): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14285): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.969 I/ActivityThread(14649): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.977 I/IMSCNative(14353): onRegistrationCallback: IMS-Registration callback event:
01-25 21:09:38.977 I/IMSCNative(14353): mRegId: 1
01-25 21:09:38.977 I/IMSCNative(14353): mEventType: 0 -- Registering
01-25 21:09:38.977 I/IMSCNative(14353): mEventData:
01-25 21:09:38.977 I/IMSCNative(14353): _s _i _p 3A _v _z _i _m _s 2E _c _o _m 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNative(14353): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01-25 21:09:38.977 I/IMSCNetwork(14353): onRegistrationCallback, regId:1
01-25 21:09:38.977 I/IMSCNetwork(14353): onRegistrationCallback, evType:0
01-25 21:09:38.977 I/IMSCNative(14353): onMgrWakeupAlarmCallback: 0, timer:3000
01-25 21:09:38.977 I/IMSCNetwork(14353): onStartAlarmTimer, timeOut: 3000
01-25 21:09:38.985 E/SCGAndroidPlatformInitializer(15000): Error initializing platform: com.tcs.la.platform.a.a: Requires READ_PHONE_STATE: Neither user 10003 nor current process has android.permission.READ_PHONE_STATE.
01-25 21:09:38.985 E/Verizon Location Agent(15000): Error setting up platform
01-25 21:09:38.985 I/Verizon Location Agent(15000): Setup SCG service
01-25 21:09:38.985 I/ServiceManager(  365): service 'ethernet' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'connectivity' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'vzwconnectivity' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'throttle' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'accessibility' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'mount' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'diskstats' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'notification' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'devicestoragemonitor' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'location' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'appwidget' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'sensorhub' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'search' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'dropbox' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'checkin_mot' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'wallpaper' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'usb' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'uimode' died
01-25 21:09:38.985 I/ServiceManager(  365): service 'audio' died
01-25 21:09:38.985 I/ActivityThread(14297): Removing dead content provider: settings
01-25 21:09:38.985 I/ActivityThread(14520): Removing dead content provider: settings
01-25 21:09:38.993 D/dalvikvm(14790): GC_FOR_MALLOC freed 81K, 63% free 1857K/4931K, external 2500K/2964K, paused 37ms
01-25 21:09:38.993 I/ActivityThread(14669): Removing dead content provider: settings
01-25 21:09:38.993 I/ActivityThread(14669): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.993 I/ActivityThread(14790): Removing dead content provider: com.motorola.android.providers.settings
01-25 21:09:38.993 I/ActivityThread(14918): Removing dead content provider: settings
01-25 21:09:38.993 I/ActivityThread(14832): Removing dead content provider: settings
01-25 21:09:38.993 I/ActivityThread(14814): Removing dead content provider: settings
01-25 21:09:39.001 I/AutoKiller(14962): Setting done.
01-25 21:09:39.001 I/ActivityThread(14790): Removing dead content provider: settings
01-25 21:09:39.016 I/AutoKiller(14962): startTryTimer started
01-25 21:09:39.024 I/BlurServiceMother(14293): blur version: Blur_Version.6.11.748.XT912.Verizon.en.US
01-25 21:09:39.024 E/SCGAndroidPlatformInitializer(15000): starting initLogging.....  
01-25 21:09:39.024 E/SCGAndroidPlatformInitializer(15000): initLogging Debug is off
01-25 21:09:39.024 E/SCGAndroidPlatformInitializer(15000): Production is on
01-25 21:09:39.040 D/PollingManager(14293): PollingManagerService()
01-25 21:09:39.040 D/PollingManager(14293): init()
01-25 21:09:39.047 D/AndroidRuntime(14293): Shutting down VM
01-25 21:09:39.047 W/dalvikvm(14293): threadid=1: thread exiting with uncaught exception (group=0x4001e560)
01-25 21:09:39.047 E/AndroidRuntime(14293): FATAL EXCEPTION: main
01-25 21:09:39.047 E/AndroidRuntime(14293): java.lang.RuntimeException: Unable to create service com.motorola.blur.service.blur.BlurServiceMother: java.lang.IllegalArgumentException: ConnectivityManager() cannot be constructed with null service
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.app.ActivityThread.handleCreateService(ActivityThread.java:2042)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.app.ActivityThread.access$2500(ActivityThread.java:124)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1028)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.os.Handler.dispatchMessage(Handler.java:99)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.os.Looper.loop(Looper.java:130)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.app.ActivityThread.main(ActivityThread.java:3859)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at java.lang.reflect.Method.invokeNative(Native Method)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at java.lang.reflect.Method.invoke(Method.java:507)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:840)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:598)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at dalvik.system.NativeStart.main(Native Method)
01-25 21:09:39.047 E/AndroidRuntime(14293): Caused by: java.lang.IllegalArgumentException: ConnectivityManager() cannot be constructed with null service
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.net.ConnectivityManager.<init>(ConnectivityManager.java:534)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.app.ContextImpl.getConnectivityManager(ContextImpl.java:1225)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.app.ContextImpl.getSystemService(ContextImpl.java:1057)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.content.ContextWrapper.getSystemService(ContextWrapper.java:384)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at com.motorola.blur.service.blur.pollingmanager.PollingManagerService.init(PollingManagerService.java:118)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at com.motorola.blur.service.blur.BlurServiceMother.onCreate(BlurServiceMother.java:396)
01-25 21:09:39.047 E/AndroidRuntime(14293):      at android.app.ActivityThread.handleCreateService(ActivityThread.java:2032)
01-25 21:09:39.047 E/AndroidRuntime(14293):      ... 10 more
01-25 21:09:39.055 I/Process (14293): Sending signal. PID: 14293 SIG: 9
01-25 21:09:39.055 I/AutoKiller(14962): ======= 1. run ========
01-25 21:09:39.055 I/AutoKiller(14962): setMinfreeValue started
01-25 21:09:39.055 I/AutoKiller(14962): Setting values: 3072,4608,7168,11776,17408,20992
01-25 21:09:39.055 E/AndroidRuntime(14293): Error reporting crash
01-25 21:09:39.055 E/AndroidRuntime(14293): android.os.DeadObjectException
01-25 21:09:39.055 E/AndroidRuntime(14293):      at android.os.BinderProxy.transact(Native Method)
01-25 21:09:39.055 E/AndroidRuntime(14293):      at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:2547)
01-25 21:09:39.055 E/AndroidRuntime(14293):      at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
01-25 21:09:39.055 E/AndroidRuntime(14293):      at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:854)
01-25 21:09:39.055 E/AndroidRuntime(14293):      at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:851)
01-25 21:09:39.055 E/AndroidRuntime(14293):      at dalvik.system.NativeStart.main(Native Method)
01-25 21:09:39.079 E/su   (15052): sudb - Opening database
01-25 21:09:39.086 E/su   (15052): sudb - Database opened
01-25 21:09:39.086 D/dalvikvm(15000): GC_CONCURRENT freed 1013K, 41% free 2425K/4099K, external 1945K/2087K, paused 1ms+1ms
01-25 21:09:39.102 E/su   (15052): sudb - Database closed
01-25 21:09:39.110 I/DEBUG   (15054): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-25 21:09:39.110 I/DEBUG   (15054): Build fingerprint: 'verizon/spyder_vzw/cdma_spyder:2.3.5/6.5.1-73_DHD-11_M1-2/111130:user/release-keys'
01-25 21:09:39.110 I/DEBUG   (15054): pid: 15052, tid: 15052  >>> su <<<
01-25 21:09:39.110 I/DEBUG   (15054): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
01-25 21:09:39.110 I/DEBUG   (15054): tls: afd4e4fc
01-25 21:09:39.110 I/DEBUG   (15054):
01-25 21:09:39.110 I/DEBUG   (15054):  r0 00000000  r1 00000284  r2 00000000  r3 00000280
01-25 21:09:39.110 I/DEBUG   (15054):  r4 bece5948  r5 bece5914  r6 bece58e4  r7 00000001
01-25 21:09:39.110 I/DEBUG   (15054):  r8 00000000  r9 00000000  10 00000000  fp 00000000
01-25 21:09:39.110 I/DEBUG   (15054):  ip 0000b14c  sp bece58c8  lr a821ad93  pc 000096c6  cpsr 60000030

As you can see it mentions AutoKiller just before the crash. Taking this advice, I reset my phone to factory, reflashed my rom, and reinstalled all my apps except AutoKiller Pro, using Titanium Backup, and there was no random reboots. After a couple days without problem, I reinstalled AutoKiller Pro to verify it was the problem. Sure enough the reboots into boot loop started all over. So needless to say, I reset, re-flashed, and restored all apps but AutoKiller Pro and the device once again works properly. I hope someone else finds this helpful.
 
B

brim13stone

New Member
Joined
Apr 6, 2012
Messages
2
Reaction score
0
same thing happening to me

This has recently started on my girlfriends razr maxx within the past cpl of days. it will reboot randomly several times and then finally get stuck in a loop. What app did you use to get the logcat that you posted? Any other advice for fixing the problem?
 
jsh1120

jsh1120

Silver Member
Joined
Dec 9, 2009
Messages
2,401
Reaction score
1
Location
Seattle, Washington
Task killers, especially "automatic" task killers are notorious for creating problems. Unless you have reason to believe that an app is smarter than the OS at managing multiple applications, it's usually a good idea to avoid them.
 
B

brim13stone

New Member
Joined
Apr 6, 2012
Messages
2
Reaction score
0
no task killers on the phone, when she first got it she had one on the phone but it was not an "automatic" task killer. I had her delete it soon after she had downloaded it, but the phone never gave any problems when the killer was installed.
 
M

mjedwards13

New Member
Joined
Apr 15, 2012
Messages
3
Reaction score
0
Thanks for the info...I've been having the same problem. Will get rid on my task killer. Thanks!!!
 
SCREWd2V

SCREWd2V

Member
Joined
Mar 30, 2012
Messages
67
Reaction score
0
Man this thread is a gold nugget! Thank you, uninstalling task killer now. I will follow up with results.

Sent from my Fist, using your Face
 
SCREWd2V

SCREWd2V

Member
Joined
Mar 30, 2012
Messages
67
Reaction score
0
SCREWd2V said:
Man this thread is a gold nugget! Thank you, uninstalling task killer now. I will follow up with results.

Sent from my Fist, using your Face
Click to expand...

this totally solved most of my problems, especially with lag when pressing the homescreen button while in a application. haven't had any auto reboots until today when streaming pandora at the gym while messaging someone. going to clear my data for pandora, hopefully it will solve that issue.

but hands down, DO NOT INSTALL AN APP KILLER for a razr, or Razr MAXX. it WILL cause problems.
 
C

CoolBlu55

New Member
Joined
Jul 14, 2012
Messages
1
Reaction score
0
Not sure if this thread is still active but before the OS update task killers would inhibit my phone from charging past 30% and would cause overheating. But now thanks to the update the OEM task killef app was replaced by a new format and i was wondering if anyone has tested the new platform with a killer yet. My razr maxx is now runnin 6.16.211.XT912.verizon.en.us if that matters.
I will be trying an app tonight and will post the program and initial response to the programming; thanks for any input.
 
pbickel

pbickel

Member
Joined
Jan 27, 2012
Messages
162
Reaction score
3
Location
Colorado
CoolBlu55 said:
Not sure if this thread is still active but before the OS update task killers would inhibit my phone from charging past 30% and would cause overheating. But now thanks to the update the OEM task killef app was replaced by a new format and i was wondering if anyone has tested the new platform with a killer yet. My razr maxx is now runnin 6.16.211.XT912.verizon.en.us if that matters.
I will be trying an app tonight and will post the program and initial response to the programming; thanks for any input.
Click to expand...

On ICS you don't need an app killer. Just hold down the home button to get to recent apps. When they appear swiping them away (side to side like you would a notification) kills the app as a task killer would
 
MattyP

MattyP

Rescue Squad
Rescue Squad
Joined
Sep 26, 2010
Messages
2,291
Reaction score
208
Location
In a race car...
pbickel said:
On ICS you don't need an app killer. Just hold down the home button to get to recent apps. When they appear swiping them away (side to side like you would a notification) kills the app as a task killer would
Click to expand...

I MAY be wrong, I am not 100% sure, but I THINK I read somewhere that swiping the apps doesn't actually kill them, it just removes them from the "Recent Apps" list. Again, I may be wrong, but I'm pretty sure I read that here somewhere. :)
 
94lt1

94lt1

Super Moderator
Staff member
Premium Member
Joined
Jan 16, 2012
Messages
17,041
Reaction score
3,997
Location
SE TX
Current Phone Model
Droid Turbo 2
Hmm, it kills em on my devices.. I checked in running apps.. perhaps it doesn't kill em all though?? Idk. :)

DROID RAZR MAXXIMIZED!!!! PREPARE TO BE VANQUISHED!!!
 
MattyP

MattyP

Rescue Squad
Rescue Squad
Joined
Sep 26, 2010
Messages
2,291
Reaction score
208
Location
In a race car...
94lt1 said:
Hmm, it kills em on my devices.. I checked in running apps.. perhaps it doesn't kill em all though?? Idk. :)

DROID RAZR MAXXIMIZED!!!! PREPARE TO BE VANQUISHED!!!
Click to expand...

I'm not sure ... I just remember it being discussed somewhere on here. Someone said it doesn't actually kill them. But I'm not sure. :)
 
TisMyDroid

TisMyDroid

Super Moderator
Staff member
Joined
Feb 16, 2011
Messages
7,442
Reaction score
3,194
Location
Central New York
Current Phone Model
Samsung Note 3
I'm not 100% sure either. I know that you can kill an app and it will still appear in the recent apps list (ral) and if you press on it, it will open the app from scratch. It seems that it will close out of some by swiping and others are more persistent... but that could be that those are the ones that would be no matter what.
 
Natey2

Natey2

Senior Member
Joined
Oct 23, 2010
Messages
1,308
Reaction score
5
Android reboots are a common phenomenon. Check your device uptime (Settings / About / Status / Uptime) and verify that your device rebooted earlier than you last recall restarting it :)

Sent from my unrooted DroidX using Tapatalk
 
You must log in or register to reply here.

Most reactions - Past 7 days

Similar threads

T
Albums Fail to Create
Replies
1
Views
3K
JohnnyS101
JohnnyS101
S
help, my droid is damn near unusable now
Replies
0
Views
2K
sprime01
S
A
Need some help evaluating my new Incredible's battery
Replies
0
Views
2K
AceCalhoon
A
M
Pulled a stupid
Replies
4
Views
2K
spaz33g
spaz33g
A
I have a weird question, please help! Any input in greatly appreciated.
Replies
0
Views
3K
alex89
A
Top