I'm posting this here because the other sections rarely get answers. I tried installing Angry Birds via the download link. It installs but force closes immediately when trying to open. I've tried running it from the phone memory as well with no luck. Here is the logcat from when I try to open the game. Is the problem with hw3dc? I don't have anything relating to hw3dc in /dev. I'm on a mt3g running CM6 stable.
D/dalvikvm( 7438): Trying to load lib /data/data/com.rovio.angrybirds_lite/lib/l
ibangrybirds.so 0x43cc5608
I/ActivityManager( 231): Process com.speedsoftware.rootexplorer (pid 6976) has
died.
D/dalvikvm( 7438): Added shared lib /data/data/com.rovio.angrybirds_lite/lib/lib
angrybirds.so 0x43cc5608
D/dalvikvm( 7438): No JNI_OnLoad found in /data/data/com.rovio.angrybirds_lite/l
ib/libangrybirds.so 0x43cc5608, skipping init
I/KA3D ( 7438): Creating MultiTouchInputDelegator
I/App ( 7438): onResume
I/ActivityManager( 231): Displayed activity com.rovio.angrybirds_lite/com.rovio
.ka3d.App: 919 ms (total 919 ms)
W/IInputConnectionWrapper( 5311): showStatusIcon on inactive InputConnection
D/libEGL ( 7438): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 7438): loaded /system/lib/egl/libGLES_qcom.so
E/EGL.oem ( 7438): could not open hw3dc (Permission denied)
E/libEGL ( 7438): No EGLDisplay for hardware EGL!
W/dalvikvm( 7438): threadid=8: thread exiting with uncaught exception (group=0x4
00207e8)
E/AndroidRuntime( 7438): FATAL EXCEPTION: GLThread 9
E/AndroidRuntime( 7438): java.lang.IllegalArgumentException
E/AndroidRuntime( 7438): at com.google.android.gles_jni.EGLImpl.eglGetCon
figAttrib(Native Method)
E/AndroidRuntime( 7438): at com.rovio.ka3d.MySurfaceView$ConfigChooser.fi
ndConfigAttrib(App.java:236)
E/AndroidRuntime( 7438): at com.rovio.ka3d.MySurfaceView$ConfigChooser.ch
ooseConfig(App.java:209)
E/AndroidRuntime( 7438): at com.rovio.ka3d.MySurfaceView$ConfigChooser.ch
ooseConfig(App.java:202)
E/AndroidRuntime( 7438): at android.opengl.GLSurfaceView$EglHelper.start(
GLSurfaceView.java:916)
E/AndroidRuntime( 7438): at android.opengl.GLSurfaceView$GLThread.guarded
Run(GLSurfaceView.java:1246)
E/AndroidRuntime( 7438): at android.opengl.GLSurfaceView$GLThread.run(GLS
urfaceView.java:1116)
W/ActivityManager( 231): Force finishing activity com.rovio.angrybirds_lite/c
om.rovio.ka3d.App
Try in a terminal:
Code:
su
chmod 666 /dev/hw3dc
This should solve the problem.
If the problem is there again after a reboot
add this line:
Code:
chmod 666 /dev/hw3dc
to your userinit.sh or put a script
with this line in in /system/etc/init.d/
farmatito said:
Try in a terminal:
Code:
su
chmod 666 /dev/hw3dc
This should solve the problem.
If the problem is there again after a reboot
add this line:
Code:
chmod 666 /dev/hw3dc
to your userinit.sh or put a script
with this line in in /system/etc/init.d/
Click to expand...
Click to collapse
Thanks but I don't have /dev/hw3dc. There is no hw3dc anywhere in /dev. In fact, I have /dev but when I go in there with root explorer it says that /dev uses 0k of space. Weird.
To be exact, the correct device name is:
Code:
# ls /dev/msm_hw3d*
/dev/msm_hw3dc /dev/msm_hw3dm
and command to run in terminal:
Code:
chmod 777 /dev/msm_hw3d*
The 777 permission maybe somewhat to lax from a security point of view
so try first if 660 or 666 fix the error.
Thanks, I follow the setting, and it works.
farmatito said:
To be exact, the correct device name is:
Code:
# ls /dev/msm_hw3d*
/dev/msm_hw3dc /dev/msm_hw3dm
and command to run in terminal:
Code:
chmod 777 /dev/msm_hw3d*
The 777 permission maybe somewhat to lax from a security point of view
so try first if 660 or 666 fix the error.
Click to expand...
Click to collapse
Thread moved to Q&A.
At the start I want to mention I need to have access to some of 4.1 API features, so that I cannot use MiniCM9 or older.
The problem is that when I try to deploy any Eclipse project, or try to install it via
Code:
adb install
IDE throws:
Code:
[2013-02-18 20:41:21 - BasicGLSurfaceView] Installation failed due to invalid APK file!
[2013-02-18 20:41:21 - BasicGLSurfaceView] Please check logcat output for more details.
[2013-02-18 20:41:21 - BasicGLSurfaceView] Launch canceled!
And here is logcat snippet from my phone:
Code:
D/AndroidRuntime( 9226): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 9226): CheckJNI is OFF
D/dalvikvm( 9226): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 9226): Added shared lib libjavacore.so 0x0
D/dalvikvm( 1722): GC_EXPLICIT freed 87K, 34% free 6828K/10247K, paused 4ms+21ms, total 118ms
D/dalvikvm( 9226): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 9226): Added shared lib libnativehelper.so 0x0
I/ActivityManager( 1653): Process com.android.defcontainer (pid 9093) has died.
D/AndroidRuntime( 9226): Calling main entry com.android.commands.pm.Pm
I/ActivityManager( 1653): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=9236 uid=10027 gids={1015, 2001, 1028}
I/ActivityManager( 1653): Process com.google.android.gsf.login (pid 9156) has died.
E/Trace ( 9236): error opening trace file: No such file or directory (2)
W/zipro ( 9236): Unable to open zip '/data/local/tmp/BasicGLSurfaceView.apk': Permission denied
D/asset ( 9236): failed to open Zip archive '/data/local/tmp/BasicGLSurfaceView.apk'
W/PackageParser( 9236): Unable to read AndroidManifest.xml of /data/local/tmp/BasicGLSurfaceView.apk
W/PackageParser( 9236): java.io.FileNotFoundException: AndroidManifest.xml
W/PackageParser( 9236): at android.content.res.AssetManager.openXmlAssetNative(Native Method)
W/PackageParser( 9236): at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
W/PackageParser( 9236): at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
W/PackageParser( 9236): at android.content.pm.PackageParser.parsePackageLite(PackageParser.java:749)
W/PackageParser( 9236): at com.android.defcontainer.DefaultContainerService$1.getMinimalPackageInfo(DefaultContainerService.java:169)
W/PackageParser( 9236): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:110)
W/PackageParser( 9236): at android.os.Binder.execTransact(Binder.java:367)
W/PackageParser( 9236): at dalvik.system.NativeStart.run(Native Method)
W/DefContainer( 9236): Failed to parse package
W/ActivityManager( 1653): No content provider found for permission revoke: file:///data/local/tmp/BasicGLSurfaceView.apk
D/dalvikvm( 1653): GC_EXPLICIT freed 149K, 36% free 18567K/28807K, paused 6ms+12ms, total 141ms
D/AndroidRuntime( 9226): Shutting down VM
D/dalvikvm( 9226): GC_CONCURRENT freed 125K, 77% free 478K/2048K, paused 1ms+1ms, total 8ms
D/dalvikvm( 9226): Debugger has detached; object registry had 1 entries
Changing permissions and owners didn't give or changed anything, it further says that there is no permissions to access APK file.
I think it is releated to kernel or ROM, so I want to ask if someone knows a solution or something to change in kernel/ROM sources to fix it up.
I use: MiniCM10-4.0.2-20130210-NIGHTLY-shakira ( on stable MiniCM10, problem also occur ) with kernel 2.6.32.60-nAa-jb-03.
Yes, it is kind a solution, but when I want to test my app many times, it won't be comfortable solution, and I'm searching permament fix for this issue
Go to Settings > Development > Enable Root for Apps and ADB.
And you should be using the latest nightly only. It has fixes for the .32 kernel.
CtrlAltDelIrl said:
Go to Settings > Development > Enable Root for Apps and ADB.
Click to expand...
Click to collapse
It changes nothing at all
There is an on/off switch at the top of the dev settings page. Make sure it's on.
Use latest nightly only with .32
I'm using latest nightly with .32 kernel, I have Root access enabled for Apps and ADB, and I'm sure switch is on, It could be kernel or ROM problem, but I haven't had any knowledge about how to try fix it.
Oh could be SuperSu instead of default Superuser a problem? Because I always changing it when I reinstall ROM.
But I have root access when using adb shell, only adb install fails
Try this..
Code:
adb pm install
Before install use
Adb remount
Sent from my U20i using xda premium
CtrlAltDelIrl said:
Try this..
Code:
adb pm install
Click to expand...
Click to collapse
When I transfer apk manually and try using command you've posted from
Code:
adb shell
it gives me
Code:
pkg: Application.apk
Failure [INSTALL_FAILED_INVALID_APK]
and ADB logs:
Code:
W/zipro ( 7157): Unable to open zip '/data/local/tmp/Application.apk': Permission denied
D/asset ( 7157): failed to open Zip archive '/data/local/tmp/Application.apk'
but,
when I transfer the file to sdcard, and then execute
Code:
pm install
then it result with success and everything is ok
Rempty said:
Before install use
Adb remount
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Doesn't work
mmmm
let's wait patiently for an update I'd say..
Good luck!
DUE TO REAL LIFE TIME CONSTRAINTS I AM UNABLE TO CONTINUE READING AND DIAGNOSING LOGS FOR MEMBERS. PLEASE USE THIS THREAD AS INTENDED, AS A STARTING POINT IN LEARNING TO READ THESE LOGS AND DIAGNOSE PROBLEMS YOURSELF. THANK YOU!
The Basics
I'm starting this thread in hopes of sharing some very useful information to all our new members and hopefully either teaching something new or being a good refresher for our experienced members. I've been asked before how to tell what errors are present in logcats, how I can understand all that mess, etc...
Well, I'm going to try my best to explain all of it. In this way, you can get your own logs and try to fix the problems, or know exactly what is causing your problems to help out the developers so they aren't looking through thousands of lines of code for each persons issue.
Help us help you!
ATTENTION:
Due to the recent feature in the portal, my thread has become increasingly popular, and as such I am getting a lot of requests for help. You may post your logs here, but please do so in either pastebin format, or use hide tags. Please DO NOT request help via pm. This is for a couple of reasons:
I can't keep up with all the requests.
Your logs may be solved by another member, I have requested that any willing RC's, RD's, Moderators, or members willing to help, to do so.
If you post your logs here, any member may look at it and help you solve them.
Thank you.
To begin with, we'll need to have some understanding of adb. Check out this thread by @bigtoysrock and be sure to thank him!
Logcats
First, we'll need to know how to get a logcat. With the plethora of new users this has been the subject of many, many discussions. When asked to get a logcat, they don't know how.
Tools and Requirements
First of all, you'll absolutely NEED to have usb debugging enabled. To do this go to SETTINGS, navigate down to DEVELOPER OPTIONS and select it, if they are not on use the toggle in the top right corner and select USB DEBUGGING ( See attached screen shots )
Secondly, you'll absolutely NEED to have the ANDROID SDK grab it here
Install the SDK on the root of your computer. DO NOT change the SDK name to include any spaces as it will fail!
Also be sure to grab your device specific drivers, if they aren't already installed. Some devices will install them automatically, while others require a simple google search.
Now that you've got everything you need, lets grab a logcat!
Update: 15 Second ADB installer for windows is an excellent alternative for the above instructions, and while you're there be sure to thank @Snoop05
How to get a Logcat
WindowsNavigate to where you've installed the sdk. Once you've gotten into the sdk, you're going to look for "PLATFORM TOOLS" folder, inside hold shift + right click on any empty space, select "OPEN COMMAND WINDOW HERE"
Connect your phone to your PC via usb cable, in the command window type "adb devices" without the quotes. If you've set everything up properly it should return an alpha-numeric value, this is your device ID. If not, you've missed a step or installed sdk in the wrong manner. Go back and double check your steps.
Now that we know you're connected there are a few options, you can run the logcat in command window, or you can export it to a .txt file.
To see the log in command window just type "adb logcat" (again no quotes) and the log will scroll through your screen. To stop scrolling so you can investigate hit ctrl + c
To export to a .txt file (I personally prefer this method) type "adb logcat > logcat.txt". You can name the logcat anything you want, for example "adb logcat > MyError.txt" just be sure not to include spaces or special characters in the name of the file.
MAC/Linux
"Instructions:
Install your device driver for using adb. Everything you need will you find here
Download adb executable for your OS (Download: Windows | Linux | Mac). Paste it somewhere.
Connect your android device.
Verify if "Settings > Developer options > USB debugging" is checked, if not, simply check it.
Open a command promt (windows) or terminal (linux / mac). How to do it: On Windows: windows + r > enter "cmd" (without quotes) > click enter | On Linux: You don't know how to open a terminal? LOL | On Mac: Type Terminal into Spotlight and open it
CD to the directory where the adb executable is located. On Windows: Go to the directory where you downloaded the adb executable, Shift+Right Click and select "Open Console" (or similar) | On Linux / Mac: Rightclick in the directory and select "Open Terminal here" (or simply CD into the directory)
Type in your cmd/terminal: adb devices to verify your device is properly connected.
If your device is properly selected, type in adb logcat to show the mighty and magic logcat aka stacktrace.
Reproduce your error (or whatever) on your device.
Right after, paste the whole cmd / terminal window into a paste-service like http://pastebin.com/ and send it to us." - Quoted from Leandros here
Reading and understanding logcat output
Reading a Logcat
Ok, so now we have our log but what do we do with it?
There are a few things that you need to know before you'll understand what is what.
Preceding every line in a logcat is a class, you can learn about them here.
These will look like this and I have placed the meaning next to each:
Code:
E/ Error - I would hope this is self explanatory
F/ Fatal Error - Again pretty self explanatory
I/ Information - This is pretty tricky, the information class shows what the system is doing, but it can also show you errors so read it carefully!
D/ Dalvikvm - This class will show what the dalvik processes are doing, but can also show you where mistakes are
W/ Warning - Warnings are basically errors, but less severe. Usually it will show you missing resources, conflicting or missing paths, etc...
V/ Verbose - Basically everything the phone is doing
S/ Silent - You will not see silent
Ok so lets see some examples. Some of these will be more in-depth than others simply because there is more to it.
Code:
[COLOR="Red"]D/dalvikvm( 1853): DexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---[/COLOR]
Here we see that the dalvik process has begun to optimize our system files.
[COLOR="red"]D/dalvikvm( 2162): DexOpt: 'Lcom/sec/android/seccamera/SecCamera$OnMultiFrameShotEventListener;' has an earlier definition; blocking out[/COLOR]
Here you can see that the Dalvik process has already defined the called method, and is skipping the optimization
[COLOR="red"]I/PackageManager( 2130): /system/app/sCloudSyncBrowser.apk changed; collecting certs[/COLOR]
The information class is showing that there has been a change made to this apk, and is verifying the signature.
[COLOR="red"]W/ResourceType( 2130): Failure getting entry for 0x7f050020 (t=4 e=32) in package 0 (error -75)
D/PhoneStatusBar( 2792): Added status bar view
D/PhoneStatusBar( 2792): disable: < expand icons alerts ticker system_info back home recent clock >
W/PackageManager( 2130): Failure retrieving xml 0x7f050020 in package com.maxmpz.audioplayer
W/PackageManager( 2130): android.content.res.Resources$NotFoundException: Resource ID #0x7f050020
W/PackageManager( 2130): at android.content.res.Resources.getValue(Resources.java:1339)
W/PackageManager( 2130): at android.content.res.Resources.loadXmlResourceParser(Resources.java:2445)
W/PackageManager( 2130): at android.content.res.Resources.getXml(Resources.java:1227)
W/PackageManager( 2130): at android.app.ApplicationPackageManager.getXml(ApplicationPackageManager.java:1080)
W/PackageManager( 2130): at android.content.pm.PackageItemInfo.loadXmlMetaData(PackageItemInfo.java:227)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.parseProviderInfoXml(AppWidgetServiceImpl.java:1264)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.addProviderLocked(AppWidgetServiceImpl.java:1162)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.loadAppWidgetList(AppWidgetServiceImpl.java:1148)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.ensureStateLoadedLocked(AppWidgetServiceImpl.java:391)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.systemReady(AppWidgetServiceImpl.java:211)
W/PackageManager( 2130): at com.android.server.AppWidgetService.systemReady(AppWidgetService.java:156)
W/PackageManager( 2130): at com.android.server.ServerThread$1.run(SystemServer.java:1882)
W/PackageManager( 2130): at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:8250)
W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$9$1.run(ActivityManagerService.java:8152)
W/PackageManager( 2130): at android.os.Handler.handleCallback(Handler.java:615)
W/PackageManager( 2130): at android.os.Handler.dispatchMessage(Handler.java:92)
W/PackageManager( 2130): at android.os.Looper.loop(Looper.java:137)
W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1563)
W/ResourceType( 2130): Failure getting entry for 0x7f050021 (t=4 e=33) in package 0 (error -75)
W/PackageManager( 2130): Failure retrieving xml 0x7f050021 in package com.maxmpz.audioplayer
W/PackageManager( 2130): android.content.res.Resources$NotFoundException: Resource ID #0x7f050021
W/PackageManager( 2130): at android.content.res.Resources.getValue(Resources.java:1339)
W/PackageManager( 2130): at android.content.res.Resources.loadXmlResourceParser(Resources.java:2445)
W/PackageManager( 2130): at android.content.res.Resources.getXml(Resources.java:1227)
W/PackageManager( 2130): at android.app.ApplicationPackageManager.getXml(ApplicationPackageManager.java:1080)
W/PackageManager( 2130): at android.content.pm.PackageItemInfo.loadXmlMetaData(PackageItemInfo.java:227)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.parseProviderInfoXml(AppWidgetServiceImpl.java:1264)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.addProviderLocked(AppWidgetServiceImpl.java:1162)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.loadAppWidgetList(AppWidgetServiceImpl.java:1148)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.ensureStateLoadedLocked(AppWidgetServiceImpl.java:391)
W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.systemReady(AppWidgetServiceImpl.java:211)
W/PackageManager( 2130): at com.android.server.AppWidgetService.systemReady(AppWidgetService.java:156)
W/PackageManager( 2130): at com.android.server.ServerThread$1.run(SystemServer.java:1882)
W/PackageManager( 2130): at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:8250)
W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$9$1.run(ActivityManagerService.java:8152)
W/PackageManager( 2130): at android.os.Handler.handleCallback(Handler.java:615)
W/PackageManager( 2130): at android.os.Handler.dispatchMessage(Handler.java:92)
W/PackageManager( 2130): at android.os.Looper.loop(Looper.java:137)
W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1563)[/COLOR]
Here is a great example of the warning class showing missing resources.
[COLOR="red"]I/dalvikvm( 1853): Could not find method android.app.IActivityManager.resizeArrangedWindow, referenced from method android.app.ActivityManager.resizeArrangedWindow
W/dalvikvm( 1853): VFY: unable to resolve interface method 3769: Landroid/app/IActivityManager;.resizeArrangedWindow (IILandroid/graphics/Rect;)Landroid/graphics/Rect;
D/dalvikvm( 1853): VFY: replacing opcode 0x72 at 0x0004[/COLOR]
A prime example of Information class showing an "error", these will usually be listed in information class if they don't have a great impact of the functionality of the device.
[COLOR="red"]F/PackageManager( 2014): Unable to backup package manager settings, current changes will be lost at reboot
E/DropBoxManagerService(2014): Can't write: system_server_wtf
E/DropBoxManagerService(2014): java.io.FileNotFoundException: /data/system/dropbox/drop21.tmp: open failed: EROFS (Read-only file system)
E/DropBoxManagerService(2014): at libcore.io.IoBridge.open(IoBridge.java:416)
E/DropBoxManagerService(2014): at java.io.FileOutputStream.(FileOutputStream.java:88)
E/DropBoxManagerService(2014): at java.io.FileOutputStream.(FileOutputStream.java:73)
E/DropBoxManagerService(2014): at com.android.server.DropBoxManagerService.add(DropBoxManagerService.java:208)
E/DropBoxManagerService(2014): at android.os.DropBoxManager.addText(DropBoxManager.java:272)
E/DropBoxManagerService(2014): at com.android.server.am.ActivityManagerService$13.run(ActivityManagerService.java:8281)
E/DropBoxManagerService(2014): at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:8288)
E/DropBoxManagerService(2014): at com.android.server.am.ActivityManagerService.handleApplicationWtf(ActivityManagerService.java:8099)
E/DropBoxManagerService(2014): at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:329)
E/DropBoxManagerService(2014): at android.util.Log$1.onTerribleFailure(Log.java:103)
E/DropBoxManagerService(2014): at android.util.Log.wtf(Log.java:278)
E/DropBoxManagerService(2014): at android.util.Log.wtf(Log.java:255)
E/DropBoxManagerService(2014): at com.android.server.pm.Settings.writeLPr(Settings.java:1115)
E/DropBoxManagerService(2014): at com.android.server.pm.PackageManagerService.unloadMediaPackages(PackageManagerService.java:9314)
E/DropBoxManagerService(2014): at com.android.server.pm.PackageManagerService.updateExternalMediaStatusInner(PackageManagerService.java:9128)
E/DropBoxManagerService(2014): at com.android.server.pm.PackageManagerService.access$3800(PackageManagerService.java:165)
E/DropBoxManagerService(2014): at com.android.server.pm.PackageManagerService$10.run(PackageManagerService.java:9017)
E/DropBoxManagerService(2014): at android.os.Handler.handleCallback(Handler.java:615)
E/DropBoxManagerService(2014): at android.os.Handler.dispatchMessage(Handler.java:92)
E/DropBoxManagerService(2014): at android.os.Looper.loop(Looper.java:137)
E/DropBoxManagerService(2014): at android.os.HandlerThread.run(HandlerThread.java:60)
E/DropBoxManagerService(2014): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
E/DropBoxManagerService(2014): at libcore.io.Posix.open(Native Method)
E/DropBoxManagerService(2014): at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
E/DropBoxManagerService(2014): at libcore.io.IoBridge.open(IoBridge.java:400)
E/DropBoxManagerService(2014): ... 20 more[/COLOR]
Here we have the Fatal and Error classes.
Ok, so now we have seen some examples, lets learn to decipher them:highfive:
The beautiful thing about these logs is that they tell you exactly what and where everything is, as long as you know what you're looking at.
I'm only going to use the one line to show you how to read a log, as the format is exactly the same for any class.
Code:
E/DropBoxManagerService(2014): at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:8288)
So here we have the printed error from logcat, the format used is as follows
Class/Process/Location
[b]Important! The log WILL NOT tell you what apk or jar the error occurs in, this is the hardest part of debugging![/b]
In the above error we see
Class = E/
Process = DropBoxManagerService
Location = com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:8288) (Folder directory.File Name. Method)
I know from all my digging that the specified path is in services.jar so once I have services.jar decompiled I'll follow the path laid out. (Decompile "apkname".odex for odexed roms and classes.dex for deodexed roms)
These paths will always be located in the smali folder! For example I open my classes.dex folder after decompiling and see a smali folder, I'll open that and then I have options. The . after every word is a folder directory ( same as / in your computer directory )
The specified path says com. so I'll open the com folder, next I'm directed to android, then server, then am folder.
Now I should see a bunch of files and possibly some folders, [b]if there is no folder name that matches the next directory it is a file![/b]
ActivityManagerService is a filename, so I'll open that file using NotePad++ and search for the specified method which is addErrorToDropBox.
From here I can use another file to compare the lines to find my error, or I can know exactly where the error occured and report my problem to a helpful dev or member.
I hope that this has been a good learning experience and will help you to understand any issues you are facing.
:victory:
Bootloops and Filtering your logs
Getting a Logcat during the dreaded Bootloop
The only difference between grabbing a logcat while running and grabbing one during a bootloop is the program you're going to use. Instead of the standard adb bridge, we'll be using the adb monitor tool. You can find this tool under the "TOOLS" folder. Open the "Tools" folder, right click on any empty space and select "Open Command Window Here"
Once the window is open, type "monitor" (without the quotes) and press enter. A whole new program will open listing the device ID and subfolders (your devices partitions)
IMPORTANT! The device ID may not show up right away, THIS IS OK! I found that it took about three bootloop cycles to actually connect.
Once you see the device ID, within a few seconds you should see the "system" partition listed underneath. Select it.
Down in the bottom left corner select the "Logcat" tab. From here, you can grab the logcat in a txt format or just watch it scroll.
I have taken screenshots of the process, and are available here
There's a great guide here that goes a little more in depth and has updated information about the requirements for a log during bootloops.
How to Filter your Logcat
Lets say you want to find only the logs for a specific app or process, searching through thousands of lines can be a pain. Luckily, adb allows you to filter your logs based on application tags!
Here's how:
Code:
adb logcat ActivityManager:I MyApp:D *:S
This filter basically says "Show me only logs for ActivityManager at an Information or above level, and all logs for 'MyApp' with a priority level of Debug and higher" The *:S is important here, this makes all other tags Silent so that it ensures only the filtered tags are shown in your log.How's that for handy?
Demesg (kernel) Logs
For a demesg log you'll want to follow the same instructions as above to get into adb terminal.
Once there, type adb devices to verify you're connected. Now you can pull a log by simply typing "adb shell dmesg > dmesg.txt" (without the quotatons" This will place the logs in the same folder that you launched terminal from (platform-tools)
Also, for more detailed information and a few other useful commands check out this site
Apps and Reference
Apps for grabbing Logcats
Mobile Apps
alogcat
This app is great for seeing your logs, especially on older Android versions. The biggest issue I have with this app is that the share function doesn't work properly on jellybean. Yet...
You can grab it here
CatLog
I personally have no experience with this app, but it's highly rated in Play Store and has an easy to use User Interface.
Grab it here
getlogs
This is my favorite of these apps, I can use it to grab almost any log I want. Highly recommended for any developer, themer, or enthusiast!
Simple, clean, effective. The way getting your logs should be
Grab it here
Logcat Reader
Grab it here
Logcat Extreme
This one looks pretty cool, it has a "floating logcat" feature. Grab it here
PC Applications
A pretty neat logcat tool is AIOlog found here, contains versions for Windows, Linux and MacOS's by 32 and 64 bit systems.
Here's a neat tool for you windows users, an AIO Logcat manager. Grab it, and view the orignal thread here
Another for you windows users, Easy Logcat Maker is an executable GUI that looks pretty neat.
Another cool logging tool is here created by the genius behind VTS!
A new Windows tool by @FuzzyMeep Two, the aptly named Logcat Tool will parse your logcat to show you how many of each entry your logs contain, and then it organizes your logs into separate files based on the type of entry (Warning, Error, Verbose, etc...), and more! This could easily become my favorite desktop method of grabbing logs.
Misc. Apps and Tools
For those of you using linux there is a neat tool that color codes your logcat output to make it easier to read. You can find it here
Not a logcat app, per se, but a pretty entertaining and live logcat boot animation courtesy of @Chainfire can be found here. Download it and see your device boot in real time!
There are a lot more apps available than what I've covered here. These are simply the most widely known (possibly with the exception of getlogs) and widely used/recommended. If you find or make any more of these apps, please feel free to post the link here and share with the community!
PLEASE NOTE THAT IT IS AGAINST XDA RULES TO LINK TO PAID APPS, SO DO NOT LINK TO PAID SERVICES OR THE POST WILL BE REPORTED AND LIKELY REMOVED
Reference Links:
Googles Logcat Help Pages
How to get useful logs by tonyp
Guide to logcats provided by Deadly
Color Coding Your Logcat World
Please be sure to thank the developers of these fantastic tools for their time and efforts!
I almost did a no-no, I almost quoted the OP
Nice Job....adding it in my OP....Thanks
Shadow_God said:
I almost did a no-no, I almost quoted the OP
Nice Job....adding it in my OP....Thanks
Click to expand...
Click to collapse
LOL, Thanks bro
Oh man, I just noticed tapatalk doesn't hide the content:screwy:
I sincerely apologize to anyone on the app
Slithering from the nether regions of a twisted mind and tarnished soul
For some reason every time I try to run a logcat I get this
Sent from my SPH-L710 using xda premium
brikzpapi said:
For some reason every time I try to run a logcat I get this
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Huh. And I thought that was just me
Great info. Well done, and thank you very much for sharing :thumbup:
@ stryke_the_orc. Great job.. will add this to useful thread links in my guide..
Btw.. you have code tags inside hide.. so it doesn't appear hidden in app.. try putting code outside of hide or something.. usually indent or code tags inside hide makes hide not to work on app..
______________________________________
Anyone who doesn't think there are two sides to an argument is probably in one.
Deadly said:
@ stryke_the_orc. Great job.. will add this to useful thread links in my guide..
Btw.. you have code tags inside hide.. so it doesn't appear hidden in app.. try putting code outside of hide or something.. usually indent or code tags inside hide makes hide not to work on app..
______________________________________
Anyone who doesn't think there are two sides to an argument is probably in one.
Click to expand...
Click to collapse
Thanks, I couldn't figure out why the tags didn't work on app
Slithering from the nether regions of a twisted mind and tarnished soul
CNexus said:
Huh. And I thought that was just me
Click to expand...
Click to collapse
What are you doing in here? Lol. What's up?
I guess you'll have to add that they must install their device specific drivers(it needs to be done with my device) else adb doesn't detects the device
Sent from my LG-P990 using xda premium
Anurag pandey said:
I guess you'll have to add that they must install their device specific drivers(it needs to be done with my device) else adb doesn't detects the device
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Op updated, thank you:thumbup:
Slithering from the nether regions of a twisted mind and tarnished soul
Anurag pandey said:
I guess you'll have to add that they must install their device specific drivers(it needs to be done with my device) else adb doesn't detects the device
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
True, my brother's computer wouldn't even pick up my sd without them
Updated OP to include how to get logcat in bootloop.:good:
Edit - Also included a link to another great guide on logcats, please be sure to thank Deadly:thumbup::beer:
Very nice write up! :beer:
Should I ask about getting this stickied? What do you guys think?
Slithering from the nether regions of a twisted mind and tarnished soul
Stryke_the_Orc said:
Should I ask about getting this stickied? What do you guys think?
Slithering from the nether regions of a twisted mind and tarnished soul
Click to expand...
Click to collapse
+1
Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
I have a FRP client program. Please make it self startup. The file name is FRP_ 0.42.0_ linux_ arm64. tar. GZ, which can be run directly on the system of my Android phone "oppo" 7.1.1. In "init. RC", I added the following contents:
------------------------------------------------------------
on property:sys. boot_ completed=1
start frpc
service frpc data/frpc/frpc -c data/frpc/frpc. ini
seclabel u:r:init:s0
user root
------------------------------------------------------------
However, due to the problem of SELinux, the service cannot run after startup. After checking the data, it is found that magickpolicy can modify the context, but I won't. please ask the great God for advice on how to use this magickpolicy command? Thank you very much. Kneel down and beg the great God~
replace "seclabel u:r:init:s0" to "seclabel u:r:magisk:s0",Still not effective!
The log is as follows:
(1)[1:init]init: Starting service 'frpc'...
[ 9336.386960] (1)[13308:init]init: cannot execve('data/frpc/frpc'): Permission denied
[ 9336.387756] (0)[543:logd.auditd]type=1400 audit(1652166228.749:3720): avc: denied { execute } for pid=13308 comm="init" name="frpc" dev="mmcblk0p69" ino=2760707 scontext=u:r:init:s0 tcontext=ubject_r:system_data_file:s0 tclass=file permissive=0
[ 9336.388130] (1)[1:init]init: Service 'frpc' (pid 13308) exited with status 127
[ 9336.388167] (1)[1:init]init: Service 'frpc' (pid 13308) killing any children in process group
I modify "init.rc" this file first, and then repack boot.img, brush in with twrp, and then reinstall "magisk-v20.4.zip".
So after installation, "init.rc" The internal is as follows:
on property:sys.boot_completed=1
start frpc
service frpc data/frpc/frpc -c data/frpc/frpc. ini
seclabel u:r:init:s0
user root
on post-fs-data
start logd
rm /dev/.magisk_unblock
start qdDvrJHt
wait /dev/.magisk_unblock 10
rm /dev/.magisk_unblock
service qdDvrJHt /sbin/magisk --post-fs-data
user root
seclabel u:r:magisk:s0
oneshot
service I3RbS38QhhR4tVa /sbin/magisk --service
class late_start
user root
seclabel u:r:magisk:s0
oneshot
on property:sys.boot_completed=1
start dLqzC3oLcVMIg6u
service dLqzC3oLcVMIg6u /sbin/magisk --boot-complete
user root
seclabel u:r:magisk:s0
oneshot