So I wanted to see if someone can read log files and tell me if my device seems hacked,cloned or remote accessed or rooted I know nothing about this stuff but it seems like my log files don't look right

I would like to know whether on an Android device it is possible to: 1. Log the date and time of every time a password is entered on my Android phone (this security measure would mean that if someone in my home sees me enter a password without me noticing it, and then uses it to log into my phone, I would then be able to see whether this happened or not to take care of my suspicion). 2. As an extra step, I would like to log all activity once the login screen is bypassed as well (for instance the date an time and application name for each time an application is opened. This is because, while my phone is password protected, once I make the screen go blank by pressing the hardware button on the right, some time goes by until a password is required: I have things set up this way so that I don't have to enter the password just so often). So, is there a way to log all user activity when the lock screen has been bypassed as well? The device I have is a Samsung Galaxy SIII Neo running Android KitKat 4.4.2. The device has been rooted. Thanks!!!

Is it possible to use USB debugging on an app that is not yours, and was downloaded from the Google Play Store? I don't really need any in-depth information, I just want to be able to see general errors that may be occurring. I'm basically trying to debug a scrolling issue in my US Bank app on my own because their response is terrible, slow, and I've done redundant "troubleshooting" steps. The phone I have is a Google Nexus 5 running Android 6.0.1, which is not rooted.

I'm trying to make an automatic night mode for my phone using "Automate", but I can't find certain app activities. How do I get to know what activities are executed in the foreground at the moment, so I can start it?

There is a lot of interesting stuff in the Android system log, that is helpful in many ways - find root causes of problems - identify misbehaving apps **How can I view and examine the Android log?**

Would like to know how can I get the adb logcat of ONLY certain app, and all its errors and messages associated. I've tried before with adb logcat -c; adb logcat | grep com.fitbit.FitbitMobile, but the thing is, it forces a grep on EVERY line, and sometimes there's a crash that involves multiline where needed information gets omitted. I've tried the command on page Displaying and filtering with Logcat , however doesn't work. It just gets everything: adb logcat -c && adb logcat com.fitbit.FitbitMobile:V I've tried also the filtering option on Android Developers Documentation , but just mutes everything: adb logcat com.fitbit.FitbitMobile:D *:S Others commands that get the pid are not useful if the app is not running when I run logcat, and crashes immediately and is relaunched with a different pid. Any ideas about the proper format?

How do I know which process or app currently accessing camera? Android 5.1, Nexus 5, shell access (no root)

My com.android.nfc service keeps crashing, how can I pinpoint why/how it is crashing? Below is the adb logcat logs I have gathered, but nothing points me to what is causing the service to crash. This is repeated constantly and happens every 5 seconds.

3369  5620 D ActivityTaskManagerServiceExtImpl: preBindApplication record is null
15753 15753 E OplusCustomizePackageManager: mIOplusCustomizePackageManagerService is null
15753 15753 E OplusCustomizePackageManager: mIOplusCustomizePackageManagerService is null
15753 15753 E OplusCustomizePackageManager: isOplusCertificatePackage Errorjava.lang.NullPointerException: Attempt to invoke interface method 'boolean android.os.customize.IOplusCustomizePackageManagerService.isOplusCertificatePackage(java.lang.St ing)' on a null object reference
15753 15753 D ResourcesManagerExtImpl: applyConfigurationToAppResourcesLocked app.getDisplayId() return callback.displayId:-1
15753 15753 W ActivityThread: ClassLoader.loadClass: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());
 3369  4367 I ActivityManager: Death received, pid = 15753, processName = com.android.nfc for thread android.os.BinderProxy@a60a167
 3369  4811 I ActivityManager: Process com.android.nfc (pid 15753) has died: pers PER
 3369  4811 W ActivityManager: Re-adding persistent process ProcessRecord{c8f2673 15753:com.android.nfc/1027}
 3369  3697 I ActivityManager: Start proc 15773:com.android.nfc/1027 for restart com.android.nfc

03-21 20:57:23.604  6499  6499 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.oplus.wirelesssettings/com.android.settings.SettingsActivity}: java.lang.NullPointerException: Attempt to invoke interface method 'int android.nfc.INfcAdapter.getState()' on a null object reference
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4372)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4569)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:126)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeNonLifecycleItem(TransactionExecutor.java:179)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:114)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:86)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2902)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:107)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:282)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:387)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:9494)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:600)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1005)
03-21 20:57:23.604  6499  6499 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'int android.nfc.INfcAdapter.getState()' on a null object reference
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.nfc.NfcAdapter.getAdapterState(NfcAdapter.java:1112)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.nfc.NfcManager.getDefaultAdapter(NfcManager.java:121)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.nfc.NfcAdapter.getDefaultAdapter(NfcAdapter.java:889)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.NfcPreferenceController.(Unknown Source:12)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.c.buildPreferenceControllers(Unknown Source:7)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.c.createPreferenceControllers(Unknown Source:14)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.settings.dashboard.DashboardFragment.onAttach(Unknown Source:29)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.nfc.c.onAttach(Unknown Source:5)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.Fragment.performAttach(Unknown Source:49)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.s.c(Unknown Source:199)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.s.m(Unknown Source:124)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.d0(Unknown Source:277)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.i1(Unknown Source:84)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.a0(Unknown Source:21)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at androidx.fragment.app.m.e0(Unknown Source:1)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.a.switchToFragmentExt(Unknown Source:55)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.oplus.wirelesssettings.a.onCreate(Unknown Source:88)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at com.android.settings.SettingsActivity.onCreate(Unknown Source:0)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:9192)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:9164)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1544)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4346)
03-21 20:57:23.604  6499  6499 E AndroidRuntime:        ... 13 more
03-21 20:57:23.934 21462 21484 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 21484 (android.hardwar), pid 21462 (android.hardwar)
03-21 20:57:23.961 21571 21571 F DEBUG   : Process name is /odm/bin/hw/android.hardware.nfc-service.nxp, uid is 1027, not key_process
03-21 20:57:23.961 21571 21571 F DEBUG   : keyProcess: 0
03-21 20:57:23.961 21571 21571 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-21 20:57:23.961 21571 21571 F DEBUG   : Build fingerprint: 'OnePlus/CPH2655/OP5D55L1:15/AP3A.240617.008/V.R4T3.1c79fbd_1e174_440e:user/release-keys'
03-21 20:57:23.961 21571 21571 F DEBUG   : Revision: '0'
03-21 20:57:23.961 21571 21571 F DEBUG   : ABI: 'arm64'
03-21 20:57:23.961 21571 21571 F DEBUG   : Timestamp: 2025-03-21 20:57:23.948224098-0700
03-21 20:57:23.961 21571 21571 F DEBUG   : Process uptime: 3s
03-21 20:57:23.961 21571 21571 F DEBUG   : Cmdline: /odm/bin/hw/android.hardware.nfc-service.nxp
03-21 20:57:23.961 21571 21571 F DEBUG   : pid: 21462, tid: 21484, name: android.hardwar  >>> /odm/bin/hw/android.hardware.nfc-service.nxp >> /odm/bin/hw/android.hardware.nfc-service.nxp >> /odm/bin/hw/android.hardware.nfc-service.nxp <<<
03-21 20:57:33.977 23360 23360 F DEBUG   : uid: 1027
03-21 20:57:33.977 23360 23360 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
03-21 20:57:33.977 23360 23360 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
03-21 20:57:33.977 23360 23360 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
03-21 20:57:33.977 23360 23360 F DEBUG   :     x0  0000000000000000  x1  0000000000005b1b  x2  0000000000000006  x3  00000076449e8990
03-21 20:57:33.977 23360 23360 F DEBUG   :     x4  2f3d485441500000  x5  2f3d485441500000  x6  2f3d485441500000  x7  0080d0c1d4c8bdaf
03-21 20:57:33.977 23360 23360 F DEBUG   :     x8  00000000000000f0  x9  00000076c9c8b378  x10 ffffff80ffffffdf  x11 fffffffffffffffd
03-21 20:57:33.977 23360 23360 F DEBUG   :     x12 00000076449e8480  x13 0000000000000008  x14 00000076449e85e8  x15 000000004a40580d
03-21 20:57:33.977 23360 23360 F DEBUG   :     x16 00000076c9d74e60  x17 00000076c9d5fac0  x18 0000007642fa8000  x19 0000000000005afc
03-21 20:57:33.977 23360 23360 F DEBUG   :     x20 0000000000005b1b  x21 00000000ffffffff  x22 0000000000000001  x23 00000076449e8f80
03-21 20:57:33.977 23360 23360 F DEBUG   :     x24 00000076cdaa28f8  x25 00000076cdaa1268  x26 00000076449e8a60  x27 00000076cda9d1b0
03-21 20:57:33.977 23360 23360 F DEBUG   :     x28 00000076cdaa2238  x29 00000076449e8a10
03-21 20:57:33.977 23360 23360 F DEBUG   :     lr  00000076c9cfaa68  sp  00000076449e8970  pc  00000076c9cfaa98  pst 0000000000001000
03-21 20:57:33.977 23360 23360 F DEBUG   : 7 total frames
03-21 20:57:33.977 23360 23360 F DEBUG   : backtrace:
03-21 20:57:33.977 23360 23360 F DEBUG   :       #00 pc 0000000000095a98  /apex/com.android.runtime/lib64/bionic/libc.so (abort+172) (BuildId: f4501bd873d8a85bd2dd833a169dec5f)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #01 pc 0000000000044e34  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_emergency_recovery(unsigned char) (.cfi)+252) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #02 pc 0000000000038238  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_process_ext_rsp(unsigned char*, unsigned short*) (.cfi)+4876) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #03 pc 000000000002cc98  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_read_complete(void*, phTmlNfc_TransactInfo*) (.cfi)+304) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #04 pc 000000000002bccc  /odm/lib64/nfc_nci.nqx.default.hw.so (phNxpNciHal_client_thread(void*) (.cfi)+560) (BuildId: e5c5a0ba31b03a6aff69fb79f0e48440)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #05 pc 00000000000a7488  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+196) (BuildId: f4501bd873d8a85bd2dd833a169dec5f)
03-21 20:57:33.977 23360 23360 F DEBUG   :       #06 pc 0000000000099584  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: f4501bd873d8a85bd2dd833a169dec5f)
03-21 20:58:28.891 24176 24207 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 24207 (android.hardwar), pid 24176 (android.hardwar)
03-21 20:58:28.924 25096 25096 F DEBUG   : Process name is /odm/bin/hw/android.hardware.nfc-service.nxp, uid is 1027, not key_process
03-21 20:58:28.924 25096 25096 F DEBUG   : keyProcess: 0
03-21 20:58:28.924 25096 25096 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-21 20:58:28.924 25096 25096 F DEBUG   : Build fingerprint: 'OnePlus/CPH2655/OP5D55L1:15/AP3A.240617.008/V.R4T3.1c79fbd_1e174_440e:user/release-keys'
03-21 20:58:28.924 25096 25096 F DEBUG   : Revision: '0'
03-21 20:58:28.924 25096 25096 F DEBUG   : ABI: 'arm64'
03-21 20:58:28.924 25096 25096 F DEBUG   : Timestamp: 2025-03-21 20:58:28.912536513-0700
03-21 20:58:28.924 25096 25096 F DEBUG   : Process uptime: 53s

I'm trying to sideload a Magisk patched rom. It's failing. I would like to extract that log. Where is it stored?

Applications on Android use class android.util.Log for producing logging output with log level, tag etc. We can view the logs using tool logcat. Writing to standard error output also writes to the same log, but with tag System.err. I am wondering how this works internally. Does each application have open some file descriptor to a pipe or socket, which has the “log processing stuff” attached on the other end? When looking to the source code of the android.util.Log class, I see that the messages end up in some native function: /** * Low-level logging call. * @param bufID The buffer ID to receive the message. * @param priority The priority of the message. * @param tag Used to identify the source of a log message. It usually identifies * the class or activity where the log call occurs. * @param msg The message you would like logged. * @return A positive value if the message was loggable (see {@link #isLoggable}). * @hide */ @UnsupportedAppUsage public static native int println_native(int bufID, int priority, String tag, String msg); I also noticed that some of the log can become lost (not flushed) when the process of the app exits directly, using java.lang.System.exit, but the stderr output is not lost. What does this function do? I ask only for educational purposes and I know that the portable way of logging is to use proper Android SDK/NDK functions.

I can't find a good reason that this application must always be running on my phone. However, it starts at boot and I'm constantly getting error traces in Logcat about the Ebay application. Why does this application start at boot?

Sometimes I get asked for a LogCat. **What is this?**
**What is it supposed to do?**
**How can I get it?**

I want to monitor network traffic on my rooted Android device. I found an app called "Network Log" (repo ), but it's outdated, designed for old Android versions, and has some bugs (but not critical). The app captures every packet using iptables, so it requires root. Can the approach be replicated without an app? Otherwise, are there other apps?

Every time I interact with logcat, I am spammed with a lot of uninteresting debug messages from all over the system. How do Android developers narrow down its output, so that they can focus on that single application they're currently debugging?

I am trying to obtain some info about the forwarding call facility in Android using the ADB tool from my computer (device attached to USB port and USB debugging enabled). I'm looking for evidence of changes in settings about enabling and disabling call forwarding and the phone numbers used for that. I've tried some commands like - adb shell content query --uri content://call_log/calls and - adb shell settings get global last_call_forward_action. But the information that I need is not present. The logcat shows something from the past, but its time range is limited to a few days and I want to know what happened several weeks ago. Is that possible? Should I use another different tool?

**Problem** I have Samsung Note 20 and a Samsung Watch. The watch wakes me up every morning between 4:42 and 4:43 am. This is independent of the time zone. It happens in NZ and Malaysia. It happens even though I have "Do Not Disturb" on a time schedule. I notice that the phone even disconnects from the car, while I am still sitting in the car (with it on). It also disconnects from the car and watch when the phone is showing on an advert on an app. This happens often, maybe it's related to the ad that's being played. **Information** The notification is Phone disconnected. I have this notification on, to remind me if I forget my phone. **Assumption** I assume that bluetooth has been turned off or disabled. **Question** Where can I find the logs on bluetooth enable and disable, so that I can discover what process is responsible?

I know of the method of using adb logcat to receive logs from an Android device. However, the logs I receive are, at best, only 1 hour old. I need the logs for the whole day, however. Is there a way for getting the logs of the whole day, or am I restricted to this?

I'm seeing a small number of logcat entries from my apps and the system, since Android 13, and now Android 14, on both my Pixel 6 Pro and Pixel 8 Pro. I can only see entries from about 5 - 10 minutes into the past before plugging the phone in to check the logcat. If I leave it plugged in, then it doesn't clear and I can see as far back as I could when I first plugged it in. However, a lot of the time I need to check something a couple of hours after it happens while the phone was unplugged. I have increased the log buffer size in Developer Options to 4M and then 8M and it's still the same. I should be able to see logcat entries from the previous day with such big log buffers! It's also the same whether checking the logcat from Android Studio or from the phone itself with a logcat reader app, unless I leave it open to record. Has anyone else run into this? Anything I can do to bring this back to how it was on Android 12 and below?

How can I see all records of every time my mic and camera have been accessed and which app accessed them? Not quite sure I'm fairly new to this stuff.

My Sony Xperia 1 V is using an unofficial build of LineageOS (rooted with Magisk) and after a few weeks of working fine, became stuck in a bootloop. I can access Fastboot and Recovery fine, and I still have the PIN and all my fingers (enrolled for fingerprints). LineageOS's Recovery also allows me to start a root shell via ADB from a PC connected with a USB cable, as well as modify the system partition (either directly when mounted read-write, or via ADB sideload). **How can I read the logs from the regular boot?** I cannot access my data partition (yet ). When I'm on an ADB shell in Recovery, there is no /proc/last_kmsg and my /sys/fs/pstore is mounted but empty. Can I somehow force the system to log to some specific location while booting (or maybe it *does* log somewhere but I don't know where to look)? Or maybe instead I could get rid of the splash boot animation to see the logs instead of it? I believe I can add some kernel arguments by carefully writing them in the header block of vendor_boot_a and vendor_boot_b partitions.