Database Develop

[GUIDE] How to read logcat messages [USER-FRIENDLY]

Hi all !
Here's my guide to read logcat. The post will be updated regularly when needed.
1.) How to logcat
Assuming you already have adb :
Code:
adb logcat
To logcat and save logcat to a file :
Code:
adb logcat>file_name.txt
2.) How to read it ?
Reading logcat is easy, easier than creating a flashable stock ROM. On logcat, you'll encounter following messages :
I/ : Information about what process is doing.
W/ : Warning, mostly displays something wrong, but not as fatal as E/ .
D/ : Debugging, same as I/ but can be crucial or fatal.
E/ : Error, crucial system error. Can be a cause of a problem.
V/ : Verbose-able / output. Mostly common message like I/ or D/ .
Example of the messages :
Code:
I/dalvikvm : Means dalvik-vm is showing an information
W/vold : Means on vold process, something is wrong.
D/dalvikvm : Means dalvik-vm is doing a debug-able actions.
E/dalvikvm : Means a fatal dalvik-vm or dalvik-vm crashed.
V/java : Java is doing something
While reading logcat, you must use your common sense. I/ sometimes can be a fatal error, so you must read it carefully.
3.) Fatal system errors
Another advantages of logcat if you're a ROM themer / porter is you can read where's system error is located.
The most common system errors are :
Code:
E/dalvikvm : The common cause of a bootloop
E/JNIHelp : Another common cause of bootloop
F/libc : Mostly SIGSEGV error, cause bootloop
Examples of errors :
Code:
E/dalvikvm( 908): ERROR: couldn't find native method : Means dalvikvm couldn't find correct method for following actions.
E/JNIHelp ( 908): RegisterNatives failed for 'android/net/wifi/WifiNative', aborting : Means JNIHelp can't register native method
F/libc ( 908): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 908 (zygote) : Caused by E/JNIHelp
Guide will be updated soon when I find something interesting.

Great thread bro,here so many peeps they need to understand it,thumps up.
GREEEETZ FROM TEAM-OPTIMA!!!

[Q] SOLVED - Phone crash on missed call (com.android.phone has stopped)

Hello guys,
I have a strange issue recently, and I'm not sure, if disabling/uninstalling some system apps caused it .
Everytime I have a missed call, the com.android.phone process FCs:
[ 02-13 08:30:46.657 23339:23339 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.phone, PID: 23339
java.lang.IllegalArgumentException: Unknown URL content://com.sonymobile.home.resourceprovider/badge
at android.content.ContentResolver.insert(ContentResolver.java:1192)
at com.android.phone.NotificationMgr.updateBadgeIcon(NotificationMgr.java:1249)
at com.android.phone.CallNotifier.onDisconnect(CallNotifier.java:1268)
at com.android.phone.CallNotifier.handleMessage(CallNotifier.java:294)
at com.android.phone.CallStateMonitor.handleMessage(CallStateMonitor.java:120)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:212)
at android.app.ActivityThread.main(ActivityThread.java:5137)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:902)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:718)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
Also, when clearing the notification, there is an similiar FC:
[ 02-13 08:30:51.137 23737:23842 E/AndroidRuntime ]
FATAL EXCEPTION: IntentService[ClearMissedCallsService]
Process: com.android.phone, PID: 23737
java.lang.IllegalArgumentException: Unknown URL content://com.sonymobile.home.resourceprovider/badge
at android.content.ContentResolver.insert(ContentResolver.java:1192)
at com.android.phone.NotificationMgr.updateBadgeIcon(NotificationMgr.java:1249)
at com.android.phone.NotificationMgr.cancelMissedCallNotification(NotificationMgr.java:759)
at com.android.phone.ClearMissedCallsService.onHandleIntent(ClearMissedCallsService.java:58)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:212)
at android.os.HandlerThread.run(HandlerThread.java:61)
[ 02-13 08:30:51.137 1303: 2800 D/ActivityManager ]
New dropbox entry: com.android.phone, system_app_crash, bc7eef37-1bf4-438d-8114-11d6d071c711
[ 02-13 08:30:51.137 1303: 2800 W/ActivityManager ]
Process com.android.phone has crashed too many times: killing!
Click to expand...
Click to collapse
I tought it was XPosed, so I completetly removed it (and modules) = issue is still there. Everything works, excpet this issue with missed calls.
Anyone has any idea?
Thanks!
Solved: Freezing XPERIA HOME caused the issue (I'm using Nova Launcher). Defrosting Xperia Home got rid of this issue.

I had the same issue with my Xperia E4g, reinstalled Xperia Home and that's it!

Security app crashes on 8.12.20 global dev rom

Opening Security app:
java.lang.ExceptionInInitializerError
at com.xiaomi.ad.mediationconfig.internal.utils.gaid.AdvertisingIdHolder.getAdvertisingId(Unknown Source:0)
at com.xiaomi.ad.mediationconfig.internal.utils.gaid.AdvertisingIdHelper.getGAId(Unknown Source:57)
at com.miui.securityscan.cards.j.run(Unknown Source:4)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.SharedPreferences android.content.Context.getSharedPreferences(java.lang.String, int)' on a null object reference
at com.xiaomi.ad.mediationconfig.internal.utils.SharedPreferencesWrapper.<init>(Unknown Source:19)
at com.xiaomi.ad.mediationconfig.internal.utils.gaid.AdvertisingIdHolder.<clinit>(Unknown Source:4)
... 6 more
I see this also here: https://xiaomi.eu/community/threads/8-12-20.48265/post-463391
Is it fixable?

Hi!
I have exact same Problem on my Xiaomi Note 5!
Have you tried to Wipe Data = Factory Reset?

It has been fixed in Global Dev 8.12.27

Play Store Crash

Hey Guys,
I'm on the EEA 10.2.28 Rom and I can't open the Play Store App. I deleted the Play Store App Cache, the Data and all updates but nothing fix the problem. I also deleted the Cache, the Data and all updates from Google play service, but still nothing happens i can't open the play store app.
I also got a crash log:
com.google.android.flib.log.WhatATerribleException: FutureCallback failed
at jkh.a(SourceFile:2)
at aiud.run(SourceFile:3)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6815)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
Caused by: android.database.sqlite.SQLiteException: not an error (code 0 SQLITE_OK): Could not open the database in read/write mode.
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:211)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:195)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:503)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:204)
at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:196)
at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:880)
at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:865)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:739)
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:729)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:355)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:298)
at nqs.a(SourceFile:3)
at nqs.iterator(Unknown Source:1)
at npj.a(SourceFile:5)
at npm.call(Unknown Source:6)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at aivb.run(Unknown Source:2)
at aive.run(SourceFile:16)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at jju.run(Unknown Source:5)
at java.lang.Thread.run(Thread.java:764)
Do you have any ideas to fix the problem [emoji24] [emoji24] [emoji24] [emoji24]
Sent from my [device_name] using XDA-Developers Legacy app

Chrome doesn't open but chrome beta does.

Hello, when I installed Havoc 3.5, I used the lucky patcher to patch the signature and install vanced youtube, I tried to unpatch this, when it seemed done I opened chrome, I could see the 'Welcome to Chrome' screen then I got the error 'Chrome keeps stopping' so I installed another ROM(pixel experience 10.0 plus) and this was repeated so I reinstalled ROM (havoc 2.9) and it is still happening. In all these roms I can open and use Chrome Beta or another browser. How can I fix it? OBS: When I installed the first ROM, Chrome wouldn't open.
Log:
HTML:
time: 1589762984467
msg: java.lang.RuntimeException: An error occurred while executing doInBackground()
stacktrace: java.lang.RuntimeException: An error occurred while executing doInBackground()
at avL.done(PG:15)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at avX.run(Unknown Source:17)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at avQ.run(Unknown Source:3)
at java.lang.Thread.run(Thread.java:919)
Caused by: java.lang.RuntimeException
at cud.d(PG:90)
at cud.a(PG:126)
at avK.call(PG:6)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 5 more