How to view errors in Android: from logs to hidden menus

The smartphone on Android started to glitch: applications crash, the system slows down, and the battery runs out in an hour? The first thing to do is find the source of the problem. But how can you see errors in Android if the system does not show them directly to the user? Unlike Windows, where errors pop up in the form of blue screens or notifications, Android hides most failures deep in the system logs.

In this article you will learn how read error logs without root access, what tools for this are in the smartphone itself, and how to use ADB for advanced diagnostics. We will analyze both standard methods (through Settings and Developer mode), as well as hidden functions that are not written about in official instructions. And also, we will learn to decipher error codes in order to understand whether the hardware, firmware or a specific application is to blame.

1. Built-in Android tools: where to look for errors without additional apps

Let's start with what you can do without installing third-party utilities. Modern versions of Android (since Android 10) have built-in tools for system monitoring, but they are hidden from the average user. Here's where you should look first:

The easiest way is to check Error log in the settings. The path may differ depending on the manufacturer, but usually this is:

• 📱 Samsung: Settings → Device maintenance → Diagnostics → Error log
• 🤖 Stock Android (Pixel, Motorola): Settings → System → Advanced → Error log
• 📱 Xiaomi/Redmi: Settings → About phone → Error report (requires enabling Developer mode)
• 📱 Huawei/Honor: Settings → System and updates → Logs (not available on all models)

If your smartphone does not have such a section, do not be upset - many manufacturers remove it from the public interface. In this case, it will help hidden diagnostic menu, which is called through the codes:

• 🔢 For Samsung: dial in the phone application *#9900# → select Delete dumpstate/logcat (clearing logs) or Copy to SD card (saving logs to a memory card).
• 🔢 For Xiaomi: ##4636## → tab Usage statistics (usage statistics) and Battery history (battery history).
• 🔢 Universal code: ##2846579## (Project Menu) → Background settings → Log settings.

⚠️ Attention: Diagnostic codes may differ depending on the model and region of the firmware. Some of them (for example, ##7780## for resetting) are dangerous - use only those. specified in the official instructions of your manufacturer.

Another useful tool is "Error report" (Bug Report). It creates an archive with system logs, which you can send to developers or analyze yourself. To generate it:

1. Hold the power button until the shutdown menu appears.
2. Tap and hold Turn off power (or Reboot on some devices).
3. In the window that appears, select Error report.
4. Wait 2-5 minutes - the report will be saved in the folder /sdcard/bugreports.

2. Developer mode: how to enable and what settings to use for diagnostics

Developer mode is a hidden menu in Android that gives access to advanced settings, including bug tracking tools. It's easy to enable:

1. Go to Settings → About phone.
2. Find item Build number (or MIUI version on Xiaomi).
3. Click on it 7 times in a row - a notification will appear "You have become a developer!".
4. Return to the main menu Settings —a new section will appear there For developers.

Now let's look at what options here are useful for finding errors:

The option Error logis especially useful. After turning it on, all application crashes (ANR - Application Not Responding) and system failures will be recorded in a file /data/anr/traces.txt. To read it:

1. Connect your smartphone to the PC and use ADB (instructions in section 4).
2. Or install a file manager with root access (for example, FX File Explorer).
3. Copy the file to a memory card and open it with any text editor.

In the log you will see lines like:

----- pid 1234 at 2026-05-20 14:30:45 -----
Cmd line: com.android.chrome
ABI: arm64
Build type: release
Zygote loaded classes=4567 post zygote classes=123

Here pid 1234 is the process identifier, com.android.chrome is the application package (Google Chrome), and the time indicates when the failure occurred.

Enable USB debugging

Activate error log (ANR)

Enable location simulation (for GPS testing)

Disable window animation (speeds up the system)

-->

3. How to read Android logs through applications (without a PC)

If you do not want to connect your smartphone to a computer, you can view the logs directly on the device using specialized applications. We have selected 3 proven toolsthat do not require root access (or. work with limited access):

1. Logcat Extreme (by PlusCubed)

• 📌 Pros: filtering logs by keywords, color marking errors, exporting to a file.
• 📌 Cons: without root does not show all system logs.
• 📌 How to use: open the application, select filter Error and look for lines with E/ (for example, E/AndroidRuntime).

2. aLogcat (Open Source)

• 📌 Pros: open source, dark theme support, saving logs to .txt.
• 📌 Cons: the interface is outdated, there is no automatic decoding of error codes.
• 📌 Tip: use word search Exception or Crash.

3. MatLog (for advanced users)

• 📌 Pros: support ADB via Wi-Fi, advanced filters, ability to save logs to the cloud.
• 📌 Cons: difficult for beginners, requires configuration.
• 📌 Example: to filter out errors Google Play Servicesenter in search com.google.android.gms.

It is important to understand that without root access applications will show not all logs - some system processes are hidden. However, even this information is often enough to identify:

• 🔴 Application crashes: look for lines with java.lang.RuntimeException.
• 🔴 Battery problems: filter by BatteryStats or PowerManager.
• 🔴 Network failures: keywords - ConnectivityService, WifiStateMachine.

⚠️ Attention: Some logging applications (for example CatLogmay contain advertising or collect data Before installing, check your permissions in Google Play and read the reviews.

If you find a line with an error in the logs, but do not understand what it means, use decryption services:

• 🌐 Stack Overflow - enter the error code in the search (for example, E/WindowManager: addView, bad token).
• 🌐 Android Developers - official documentation on error codes (developer.android.com).

4. Advanced diagnostics via ADB: commands for reading logs

For full access to logs you will need a computer and a tool Android Debug Bridge (ADB)This is the official one. a utility from Google that allows you to manage an Android device via the command line. Here's how to use it:

Step 1. Installing ADB

1. Download Platform Tools from the site developer.android.com (section SDK Platform Tools).
2. Extract the archive into a folder (for example, C:\adb).
3. Enable on your smartphone USB debugging (in Settings developer).
4. Connect the phone to the PC via a USB cable (select mode File transfer).

Step 2. Basic commands for diagnostics

adb logcat

adb logcat -d

adb logcat | grep "E/"

adb bugreport

adb shell dumpsys battery

To save logs to a file, use redirection:

adb logcat -d > C:\logs\android_errors.txt

Step 3. Analysis of logs

In output logcat pay attention to:

• 🔍 Level marks:
  • E/ — errors (Error),
  • W/ — warnings (Warning),
  • I/ — information messages.
• 🔍 Process names: com.android.phone (telephony), android.process.media (media storage).
• 🔍 Key words: Crash, Exception, ANR (Application Not Responding).

Example of string decoding:

E/ActivityManager( 1234): ANR in com.whatsapp (com.whatsapp/.HomeActivity)
Reason: Input dispatching timed out (Waiting to send non-key event)

Here:

• ANR - the application WhatsApp stopped responding.
• Input dispatching timed out - problem with touch processing (possibly due to CPU overload).

⚠️ Attention: Commands ADB can vary depending on the version of Android. For example, in Android 12+ access to some logs requires explicit user permission through a dialog on the smartphone screen.

5. Decoding Android error codes: what ANR, FC and others mean

In Android logs there are often abbreviations and codes that mean little to the average user. Let's look at the most common types of errors and their possible causes:

The critical error "system_server crashed" usually indicates damage to system files and often requires a complete reset or flashing. If you see it in the logs, first try clearing the cache via Recovery, and if that doesn’t help, get ready to reinstall the software.

Some errors may occur manufacturer-specific. For example:

• 📱 Samsung: RILJ: Unsolicited response - problems with the modem (restart the phone or reset the network settings).
• 📱 Xiaomi: MiuiCamera: bindPreview failed - camera failure (try rolling back the application update Camera).
• 📱 Google Pixel: SensorService: halSensorBatch - problems with sensors (often solved by calibration).

6. distinguish software failure from hardware problems

Not all errors in Android are related to software. Sometimes symptoms. glitches (reboots, shutdowns, artifacts on the screen) indicate hardware faultsHere's how to identify them:

Signs of problems with hardware:

• 🔋 Battery:
  • The phone turns off at 20-30% charge (battery wear).
  • Errors are repeated in the logs BatteryService or healthd.
• 📶 Modem/antenna:
  • No network in places with good coverage.
  • Errors RIL (Radio Interface Layer) in the logs.
• 🖥️ Screen/touchscreen:
  • "Ghost" touches or non-working areas.
  • Artifacts (strips, flickering) at high brightness.
• 🔥 Overheating:
  • The phone heats up without load (even in standby mode).
  • Error logs thermal-engine or cpufreq.

How to check the hardware status:

1. Battery test:
   • Install AccuBattery —the application will show the actual battery capacity.
   • In ADB run the command:

     adb shell dumpsys battery

     Look for parameters health (should be 2 —"good") and temperature (normal: 25–40°C).

2. Diagnostics of the communication module:
   • Dial ##4636## → Phone information.
   • Check the network status: if Service State shows Out of Service, the problem is in the antenna or SIM card.
3. Checking the screen and sensor:
   • Use test modes:
     • 📱 Samsung: #0# (display and touch test).
     • 📱 Xiaomi: ##6484## (touchscreen test).

If you suspect problems with the motherboard (for example, after a fall or moisture), pay attention to:

• 🔌 Power: the phone does not charge from the original cable, but is charged from another.
• 🔊 Speakers/microphone: distorted sound or its absence.
• 📡 Wi-Fi/Bluetooth: modules do not turn on or work unstable.

⚠️ Attention: If errors like kernel panic or hardware faultappear in the logs, this almost always indicates a hardware failure. In this case, self-repair may aggravate the problem - it is better to contact a service center.

For comprehensive hardware testing, you can use the following applications:

• 🛠️ Phone Doctor Plus —checks the screen, camera, speakers, sensors.
• 🛠️ CPU Throttling Test —detects throttling (performance limitation) due to overheating.
• 🛠️ Dead Pixels Test —looks for dead pixels on the screen.