[Q] [SOLVED] S Note crashes on "Transform into" - Galaxy Note 4 Q&A, Help & Troubleshooting

Hi all,
My S Note on my Note 4 (stock 4.4.4 rom, S Note updated to the latest from the Samsung app store) seems to always crash when I use the "Transform into" option after selecting a piece of text. From logcat I can see a stack trace as below. Does anyone know what could be the cause?
Thanks!
E/SNoteApp(26967): FATAL EXCEPTION: main
E/SNoteApp(26967): App version info: 4.0.1501.4/150126001
E/SNoteApp(26967): Process: com.samsung.android.snote, PID: 26967
W/System.err(26967): java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
W/System.err(26967): at com.samsung.android.snote.control.core.recognition.a.h.e(SourceFile:223)
W/System.err(26967): at com.samsung.android.snote.control.core.recognition.a.h.a(SourceFile:47)
W/System.err(26967): at com.samsung.android.snote.control.ui.object.c.au.i(SourceFile:705)
W/System.err(26967): at com.samsung.android.snote.control.ui.object.c.au.a(SourceFile:296)
W/System.err(26967): at com.samsung.android.snote.control.core.e.b.au.d(SourceFile:64)
W/System.err(26967): at com.samsung.android.snote.control.core.e.b.bf.a(SourceFile:778)
W/System.err(26967): at com.samsung.android.snote.control.core.e.b.a.c.onMenuSelected(SourceFile:59)
W/System.err(26967): at com.samsung.android.sdk.pen.engine.SpenControlBase$1.onSelected(SourceFile:717)
W/System.err(26967): at com.samsung.android.sdk.pen.engine.SpenContextMenu$HAdapter$1.onClick(SourceFile:1021)
W/System.err(26967): at android.view.View.performClick(View.java:4754)
W/System.err(26967): at android.view.View$PerformClick.run(View.java:19605)
W/System.err(26967): at android.os.Handler.handleCallback(Handler.java:733)
W/System.err(26967): at android.os.Handler.dispatchMessage(Handler.java:95)
W/System.err(26967): at android.os.Looper.loop(Looper.java:146)
W/System.err(26967): at android.app.ActivityThread.main(ActivityThread.java:5748)
W/System.err(26967): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err(26967): at java.lang.reflect.Method.invoke(Method.java:515)
W/System.err(26967): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1291)
W/System.err(26967): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1107)
W/System.err(26967): at dalvik.system.NativeStart.main(Native Method)
I/Process (26967): Sending signal. PID: 26967 SIG: 9
I/WindowState( 986): WIN DEATH: Window{43965a20 u0 com.samsung.android.snote/com.samsung.android.snote.control.ui.note.NoteActivity}
W/WindowManager( 986): Force-removing child win Window{43aecc10 u0 PopupWindow:46441c50} from container Window{43965a20 u0 com.samsung.android.snote/com.samsung.android.snote.control.ui.note.NoteActivity}
I/ActivityManager( 986): Process com.samsung.android.snote (pid 26967) (adj 0) has died.(205,409)

After a lot of trial and errors and a bit of googling, I finally solved this.
My phone somehow has no handwriting language installed or selected. If I goto Settings -> Language and input, it's empty under "Handwriting Recognition". What I did then was going into the settings for the "Samsung keyword", and then "+ Select input languages", then update/check/install some languages (in my case English AU). Now going back to the "Handwriting Recognition" I can select whichever one I want.
The crash in S Note is then fixed. That also fixes the crash I get when I try to use the "Easy Chart" in S Note too.

Related

freeze on unlock??

hey guys it's been like 2 days no when i try to unlock my phone the screen freezes..
sometimes i get this?
java.lang.SecurityException: Permission Denial: opening provider com.google.android.gm.provider.MailProvider from ProcessRecord{407c6ed8 1761:com.sec.android.app.twlauncher/10032} (pid=1761, uid=10032) requires com.google.android.gm.permission.READ_GMAIL or com.google.android.gm.permission.WRITE_GMAIL
at android.os.Parcel.readException(Parcel.java:1322)
at android.os.Parcel.readException(Parcel.java:1276)
at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:1882)
at android.app.ActivityThread.getProvider(ActivityThread.java:3351)
at android.app.ActivityThread.acquireProvider(ActivityThread.java:3376)
at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java:1826)
at android.content.ContentResolver.acquireProvider(ContentResolver.java:748)
at android.content.ContentResolver.query(ContentResolver.java:256)
at com.sec.android.app.twlauncher.Launcher.onGmailChanged(Launcher.java:30)
at com.sec.android.app.twlauncher.GmailObserver.onChange(GmailObserver.java:23)
at android.database.ContentObserver$NotificationRunnable.run(ContentObserver.java:43)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3687)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
at dalvik.system.NativeStart.main(Native Method)

[Solved]Stuck at Boot Logo with Bootloop, Need help reading Logcat

I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
japzone said:
I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
Click to expand...
Click to collapse
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Thanks for the reply. Nice crash course on log reading I have gone ahead and flashed a fresh install of PA ROM.
I really just wonder how the error might of happened. It occured at a bad time for me where my External Harddrive died on me taking my backups with it, and leaving me with nowhere to put new ones. My new Laptop with a 1TB drive is coming in August so I was planning on backing up and Flashing a Custom ROM then. But this error took out my device before I could make a backup. Oh well, I managed to scavenge most of my apps and hopefully will be able to restore them. Sadly I lost a day off to resuscitating my Nexus
Red Devil said:
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Click to expand...
Click to collapse

Verification failed on class ART / Dalvik

I'm getting a weird error using the Aviary SDK for some users who are using ART. I'm confused on why this happening (only on 4.4.x obviously) as the app works perfectly when calling this SDK on Dalvik. Any one have any have any ideas to solve this? Aviary claims it's PhoneGap/Cordova issue (our base), but I don't think that's the issue here as it only fires when the activity is launched.
HTML:
06-06 09:45:36.037: D/Aviary(27701): Pictures folder: /storage/emulated/0/Pictures
06-06 09:45:36.037: D/Aviary(27701): show
06-06 09:45:36.037: D/Aviary(27701): VERSION => 3.0.4
06-06 09:45:36.037: D/Aviary(27701): VERSION => 157
06-06 09:45:36.041: I/ActivityManager(741): START u0 {dat=file:///storage/emulated/0/DCIM/Camera/1402062335694.jpg cmp=com.XXXX.app/com.aviary.android.feather.FeatherActivity (has extras)} from pid 27701
06-06 09:45:36.054: W/CursorWrapperInner(27701): Cursor finalized without prior close()
06-06 09:45:36.058: I/CordovaLog(27701): Changing log level to ERROR(6)
06-06 09:45:36.087: I/ActivityManager(741): Start proc com.XXXX.app:standalone for activity com.XXXX.app/com.aviary.android.feather.FeatherActivity: pid=28285 uid=10060 gids={50060, 3003, 1028, 1015}
06-06 16:20:12.473 W/art (188): Could not get current activity
......
06-06 09:45:36.320: E/art(28285): Verification failed on class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler in /data/app/com.XXXXXXX.apk because: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider)
06-06 09:45:36.320: E/AndroidRuntime(28285): FATAL EXCEPTION: SessionHandler
06-06 09:45:36.320: E/AndroidRuntime(28285): Process: com.XXXXX.app:standalone, PID: 28285
06-06 09:45:36.320: E/AndroidRuntime(28285): java.lang.VerifyError: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider) (declaration of 'com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler' appears in /data/app/com.XXXXXXX.apk)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.init(LocalyticsSession.java:1427)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.handleMessage(LocalyticsSession.java:1124)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Handler.dispatchMessage(Handler.java:102)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Looper.loop(Looper.java:136)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.HandlerThread.run(HandlerThread.java:61)
06-06 09:45:36.320: W/ActivityManager(741): Force finishing activity com.XXXXXX.app/com.aviary.android.feather.FeatherActivity

LG QuickMemo for CM11

I'm trying to make QuickMemo work on CM... So far it's not going anywhere as I'm kinda noob with Android... And I'm hoping someone with more knowledge can help me!
I copied LGQMemo.apk to /system/priv-app and was able to run it through Secure settings Launch activity and here is what I got in return:
06-11 11:54:48.412 I/ActivityManager( 826): START u0 {flg=0x10000000 cmp=com.lge.QuickClip/.QuickClipActivity} from pid 8370
06-11 11:54:48.422 I/SecureSettings.ActionService( 8370): onHandleIntent::Action Success
06-11 11:54:48.422 V/Zygote ( 8527): Switching descriptor 42 to /dev/null
06-11 11:54:48.422 V/Zygote ( 8527): Switching descriptor 9 to /dev/null
06-11 11:54:48.422 I/ActivityManager( 826): Start proc com.lge.QuickClip for activity com.lge.QuickClip/.QuickClipActivity: pid=8527 uid=10149 gids={50149, 1028, 1015}
06-11 11:54:48.462 I/dalvikvm( 8527): DexOpt: mismatch dep name: '/data/dalvik-cache/[email protected]@[email protected]' vs. '/system/framework/core.odex'
06-11 11:54:48.462 E/dalvikvm( 8527): /system/priv-app/LGQMemo.apk odex has stale dependencies
06-11 11:54:48.462 D/ActivityThread( 8527): handleBindApplication:com.lge.QuickClip
06-11 11:54:48.462 D/ActivityThread( 8527): setTargetHeapUtilization:0.75
06-11 11:54:48.462 D/ActivityThread( 8527): setTargetHeapMinFree:2097152
06-11 11:54:48.462 W/dalvikvm( 8527): Unable to resolve superclass of Lcom/lge/QuickClip/QuickClipActivity; (270)
06-11 11:54:48.462 W/dalvikvm( 8527): Link of class 'Lcom/lge/QuickClip/QuickClipActivity;' failed
06-11 11:54:48.462 D/AndroidRuntime( 8527): Shutting down VM
06-11 11:54:48.462 W/dalvikvm( 8527): threadid=1: thread exiting with uncaught exception (group=0x419b2ce0)
06-11 11:54:48.472 E/AndroidRuntime( 8527): FATAL EXCEPTION: main
06-11 11:54:48.472 E/AndroidRuntime( 8527): Process: com.lge.QuickClip, PID: 8527
06-11 11:54:48.472 E/AndroidRuntime( 8527): java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.lge.QuickClip/com.lge.QuickClip.QuickClipActivity}: java.lang.ClassNotFoundException: Didn't find class "com.lge.QuickClip.QuickClipActivity" on path: DexPathList[[zip file "/system/priv-app/LGQMemo.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2120)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2253)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.app.ActivityThread.access$800(ActivityThread.java:145)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1206)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.os.Handler.dispatchMessage(Handler.java:102)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.os.Looper.loop(Looper.java:136)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.app.ActivityThread.main(ActivityThread.java:5128)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at java.lang.reflect.Method.invokeNative(Native Method)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at java.lang.reflect.Method.invoke(Method.java:515)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at dalvik.system.NativeStart.main(Native Method)
06-11 11:54:48.472 E/AndroidRuntime( 8527): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.lge.QuickClip.QuickClipActivity" on path: DexPathList[[zip file "/system/priv-app/LGQMemo.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
06-11 11:54:48.472 E/AndroidRuntime( 8527): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.app.Instrumentation.newActivity(Instrumentation.java:1061)
06-11 11:54:48.472 E/AndroidRuntime( 8527): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2111)
06-11 11:54:48.472 E/AndroidRuntime( 8527): ... 12 more
06-11 11:54:48.472 W/ActivityManager( 826): Force finishing activity com.lge.QuickClip/.QuickClipActivity
06-11 11:54:48.472 W/InputMethodManagerService( 826): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
06-11 11:54:48.972 W/ActivityManager( 826): Activity pause timeout for ActivityRecord{424ae208 u0 com.lge.QuickClip/.QuickClipActivity t15 f}
06-11 11:54:49.022 I/Timeline( 1458): Timeline: Activity_idle id: [email protected] time:413509
06-11 11:54:49.482 D/qcom_sensors_hal( 826): hal_sensor1_data_cb: msg_type 2
06-11 11:54:49.922 I/Process ( 8527): Sending signal. PID: 8527 SIG: 9
06-11 11:54:49.932 D/PhoneStatusBar( 1239): disable: < expand icons alerts ticker system_info back home recent CLOCK* search >
06-11 11:54:49.932 W/InputMethodManagerService( 826): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$S[email protected] attribute=null, token = [email protected]
06-11 11:54:49.932 I/ActivityManager( 826): Process com.lge.QuickClip (pid 8527) has died.
Click to expand...
Click to collapse
Since I cannot install it directly, I was wondering why can the Secure Settings find the application and it's main activity but in the logcat it says it cannot be found?
Thanks in advance! (QMemo and QMemo.odex taken from latest CloudyFlex 2.4)
You may want to look for his people got the remote working. Pretty sure it looks for the eula being agreed to before it works
Sent from my LG-VS980 using Tapatalk
Hummm... But wouldn't it need to be shown on the EULA when you first start the system? As I recall, only the remote and VuTalk where shown...
I tried copying some files the the system/framework folder and got a reboot AND system format for free! Had to reinstall CM! Damn! (as I said I'm not a android/linux expert hehehe)

Phone app continuously crashing

First, some information about the device:
1. Samsung Galaxy S5 from TMobile
2. Has Lollipop installed (from OTA update)
3. Factory ROM, not rooted, bootloader still locked, no modifications whatsoever.
For some reason I am getting the "Unfortunately, Phone has stopped" popup continuously. This occurs from the moment I boot up (at lockscreen) and as soon as I press "OK", it comes up about 0.2 seconds later. Makes it very difficult to navigate the device menus.
I have looked at logcats and this exception is what occurs:
Code:
I/Telecom (10435): Call: CallerInfo received for ****: [email protected] { name null, phoneNumber non-null }
I/Telecom (10435): MissedCallNotifier: showMissedCallNotification
D/ScoverManager(10435): serviceVersion : 16908288
D/EcidContact(10435): ECID AOSP VERSION: 2.3.6
D/AndroidRuntime(10435): Shutting down VM
E/AndroidRuntime(10435): FATAL EXCEPTION: main
E/AndroidRuntime(10435): Process: com.android.server.telecom, PID: 10435
E/AndroidRuntime(10435): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime(10435): at com.android.server.telecom.secutils.TelecomUtils.getPresentationString(TelecomUtils.java:2917)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier.showMissedCallNotification(MissedCallNotifier.java:191)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier$3$1.onCallerInfoChanged(MissedCallNotifier.java:617)
E/AndroidRuntime(10435): at com.android.server.telecom.Call.access$000(Call.java:74)
E/AndroidRuntime(10435): at com.android.server.telecom.Call$1.onQueryComplete(Call.java:165)
E/AndroidRuntime(10435): at com.android.internal.telephony.CallerInfoAsyncQuery$CallerInfoAsyncQueryHandler.onQueryComplete(CallerInfoAsyncQuery.java:343)
E/AndroidRuntime(10435): at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
E/AndroidRuntime(10435): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(10435): at android.os.Looper.loop(Looper.java:145)
E/AndroidRuntime(10435): at android.app.ActivityThread.main(ActivityThread.java:5837)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1388)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1183)
V/ApplicationPolicy( 783): isApplicationStateBlocked userId 0 pkgname com.android.server.telecom
W/ActivityManager( 783): Process com.android.server.telecom has crashed too many times: killing!
I/dumpstate(10454): begin
D/StatusBarManagerService( 783): manageDisableList userId=0 what=0x0 pkg=WindowManager.LayoutParams
D/CrashAnrDetector( 783): processName: com.android.server.telecom
D/CrashAnrDetector( 783): broadcastEvent : com.android.server.telecom system_app_crash
W/ContextImpl( 783): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1701 com.android.server.analytics.data.collection.application.CrashAnrDetector.broadcastEvent:296 com.android.server.analytics.data.collection.application.CrashAnrDetector.processDropBoxEntry:254 com.android.server.analytics.data.collection.application.CrashAnrDetector.access$100:60 com.android.server.analytics.data.collection.application.CrashAnrDetector$1.onReceive:102
I/SurfaceFlinger( 245): id=21 createSurf (49x49),1 flag=4, Application Error: com.android.server.telecom
I/OpenGLRenderer( 783): Initialized EGL, version 1.4
I/OpenGLRenderer( 783): HWUI protection enabled for context , &this =0x9de366f0 ,&mEglDisplay = 1 , &mEglConfig = 8
E/android.os.Debug( 783): [email protected] > sdumpstate -k -t -z -d -o /data/log/dumpstate_app_error
I/ServiceManager( 345): Waiting for service AtCmdFwd...
D/PowerManagerService( 783): [input device light] handleInputDeviceLightOff
It seems to have something to do with telecom. I have removed the SIM card, SD card, etc. No difference. I have tried clearing app data for contacts, contacts storage, phone app, even "com.android.server.telecom" from ADB SHELL PM CLEAR command, but no change.
Does anyone know what the issue could be? What can I try to do (besides factory reset of course) to fix the issue? Thanks in advance. I can post more logcats if needed.
There are numerous bugs with system apps crashing with lolipop on the S5. My contacts app is constantly crashing, vzw, OTA.
Ended up doing a factory reset, which fixed the issue
I really didn't want to factory reset ?
You need to factory reset after upgrading from KK to LP
That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.
Android.Addiction said:
Ended up doing a factory reset, which fixed the issue
Click to expand...
Click to collapse
Android.Addiction said:
That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.
Click to expand...
Click to collapse
___________________

Categories

Resources