You need to view system log files on an android device. how can this be accomplished?

Solutions

Please note that the device's log buffer is cleared after 15 minutes so it is important that the log file is captured within this period of time.

  1. In the Phone Application, enter *#9900#
  2. Set the Debug Level to Mid.
  3. Wait for the device to restart.
  4. Open the app you want to debug and reproduce your issue.
  5. After reproducing your issue, enter *#9900# again in the Phone Application
  6. Select Run dumpstate/logcat
  7. Select Copy to sdcard Navigate to the log directory that was created on the device using the My Files app or a Windows PC with a USB cable connection .
  8. Ask the user to send you the dumpState in a Zip file.
  9. After you have finished, you can follow steps 1-3 again and delete dumpstate/logcat and return the Debug Level to low.

You need to view system log files on an android device. how can this be accomplished?

Environment

Samsung mobile devices

Overview

You might need to help troubleshoot a mobile device issue by getting a log of the device's activities. This knowledge base article guides you through the steps on how to collect these logs.

How do I collect dumpstate logs on a mobile device?

The easiest way to get these logs from a Samsung mobile device is to use the SysDump tool:

  1. Reproduce the issue that you would like to troubleshoot. Note that logs must be collected within 10 minutes of reproducing the issue.
  2. Launch the Phone app.
    If your device does not have a Phone (for example, device is Wi-Fi only like the Galaxy Note 10.1 2014 edition), use the Calculator app and enter (+30012012732+ in the keypad. This switches the Calculator to Factory Mode.
  3. Enter *#9900# to launch the SysDump tool.
  4. Tap Run dumpstate/logcat
  5. Tap Copy to sdcard. This copies a timestamped .log file to the folder /log, which you can access through My Files in your personal space.
  6. Navigate to the log directory that was created on the device using the My Files app or a Windows PC with USB cable connection.
  7. You can send the file to Knox Support using one of these methods:
  • From My Files, share the .log file via email.
  • Connect a USB cable to a computer, then copy the file to your computer, and email the file from your computer.

NOTE—Some carriers, like Verizon, have disabled the SysDump tool on their devices. For these devices, use the Android Debug Bridge instead.

NOTE—If requested by Knox Support, you may need to change the debug level to MID. To change the debug level, perform Steps 2 and 3 above, then tap Debug Level > MID. After the device restarts, follow Steps 1-7 above to collect the logs.

Additional information

For steps on how to collect logs on Samsung wearable devices, see How to collect dumpstate logs on Samsung wearable devices.

There are a few ways to view the System-Log - but finding the location of the log files is considerabaly harder. I will list 3 options that will allow you to view the logs (either on a device or computer), but I do not know where they are kept. I may be wrong, but from what I have gather, the Android System does not keep a "Log File". Rather, there is a buffer that contains the "Log" (again I may be wrong on this)!

You first option is to install an app from the play-store called aLogCat. This app is very useful for both viewing and sending logs from your device. It can be setup to Email you the "Log Files" from your device. This method works best with root.

The second method works by using the Android SDK. Connect your device (with USB-Debugging enabled) and, at a Terminal enter the following:

    $ adb logcat -d > logcat.txt

The -d option tells adb to copy the entire File Log from the Android System. Because you seem to know how UNIX Systems work, I won't explain the rest of the command.

A third option (if you are rooted, that is) is to install a Terminal Emulator on your Android device. Open the Terminal Emulator and enter the command:

    $ logcat -d > /sdcard/my-log-file.txt

This will do the same as above (except you don't need a computer, and the file saves on your device/SDcard. Feel free to change the "/sdcard/my-log-file.txt" part to anything you like, but I strongly recommend you save it to either your external or internal storage - so in short: Save it to a location you can accsess without # (superuser) permission!

Audit and investigation page: Review activities on your organization’s devices

Supported editions for this feature: Business Plus; Enterprise; Education Standard and Education Plus; G Suite Business; Cloud Identity Premium.  Compare your edition

You can use the audit and investigation page to run searches related to Device log events. There you can view a record of actions on computers, mobile devices, and smart home devices that are used to access your organization's data. For example, you can see when a user added their account to a device or if a device’s password doesn’t follow your password policy. You can also set an alert to be notified when an activity occurs.

For a full list of services and activities that you can investigate, such as Google Drive or user activity, read through the data sources for the audit and investigation page.

Open the audit and investigation page

Before you begin

  • To see all audit events for mobile devices, the devices need to be managed using advanced device management. 
  • To see changes to applications on Android devices, you must turn on application auditing.
  • You can’t see activities for devices that sync corporate data using Google Sync.
  • If you downgrade to an edition that doesn't support the audit log, the audit log stops collecting data for new events. However, old data is still available to admins.

Access Device log event data

  1. On the left, click ReportingAudit and investigationDevice log events.

Filter the data

  1. Open the log events as described above in Access Device log event data.
  2. Click Add a filter, and then select an attribute.
  3. In the pop-up window, select an operatorselect a valueclick Apply.
  4. (Optional) To create multiple filters for your search:

    1. Click Add a filter and repeat step 3.
    2. (Optional) To add a search operator, above Add a filter, select AND or OR.

  5. Click Search.

Note: Using the Filter tab, you can include simple parameter and value pairs to filter the search results. You can also use the Condition builder tab, where the filters are represented as conditions with AND/OR operators.

Attribute descriptions

For this data source, you can use the following attributes when searching log event data:

AttributeDescription
Account state Whether the account is registered or unregistered
Actor group name Group name of the actor
Actor organizational unit Organizational unit of the actor
Application ID Identifier for the application
Application SHA-256 hash For app-related events, the SHA-256 hash of the application package (Android only)
Application state Whether the application is installed, uninstalled, or updated
Date Date and time of the event (displayed in your browser's default time zone)
Device compliance state

Whether the device complies with your organization’s policies.

A device is marked not compliant if it:

  • Violates an applied password setting or encryption policy.
  • Doesn’t have the latest Device Policy app installed.
  • Doesn't comply with security settings.
  • Doesn’t have a work profile when a work profile is expected.
  • Isn’t in device owner mode when device owner mode is expected.
  • Is blocked by an administrator.
  • Is no longer syncing because an administrator disabled synchronization.

Example: User's Nexus 6P is not compliant with set policies because device is not adhering to password policy.

Device compromised state

Whether the device is compromised. Devices can become compromised if they’re rooted or jailbroken—processes that remove restrictions on a device. Compromised devices can be a potential security threat.

The system records an entry each time a user’s device is compromised or no longer compromised. 

Example: User's Nexus 5 is compromised.

Device ID Identifier for the device that the event happened on
Device model The model of the device
Device owner The owner of the device
Device ownership

Whether the ownership of the device changed. 

For example, a personal device was changed to company-owned after its details were imported into the Admin console. 

This audit occurs immediately after a company-owned device is added to the Admin console. If a company-owned device is deleted from the Admin console, the audit occurs at the next sync (after it’s re-enrolled for management).

Example: Ownership of user’s Nexus 5 has changed to company owned, with new device id abcd1234.

Device property Information about the device, such as Device model, Serial number,or WiFi MAC address.
Device setting

The device user changed the developer options, unknown sources, USB debugging, or verify apps setting on their device.  

This event is recorded the next time the device syncs. 

Example: Verify Apps changed from off to on by user on Nexus 6P.

Device type Type of device that the event happened on. For example, Android or Apple iOS.
Domain The domain where the action occurred
Event The logged event action, such as Device OS update or Device sync event
Failed password attempts

The number of failed attempts by a user to unlock a device. 

An event is generated only if there are more than 5 failed attempts to unlock a user's device. 

Example: 5 failed attempts to unlock user's Nexus 7.

iOS vendor ID Identifier for the iOS vendor
New device ID Identifier for the new device
OS property Information about the OS, such as Build number, OS version,or Security patch
Register privilege The role of the user for a device, such as Device owner or Device administrator
Resource ID Unique identifier for the device
Serial number The serial number of the device
User email Email address of the device user

Manage log event data

Manage search results column data

You can control which data columns appear in your search results. 

  1. At the top-right of the search results table, click Manage columns.
  2. (Optional) To remove current columns, click Remove.
  3. (Optional) To add columns, next to Add new column, click the Down arrowand select the data column.
    Repeat as needed.
  4. (Optional) To change the order of the columns, drag the data column names.
  5. Click Save.

Export search result data

  1. At the top of the search results table, click Export all.
  2. Enter a nameclick Export.
    The export displays below the search results table under Export action results.
  3. To view the data, click the name of your export.
    The export opens in Google Sheets.

Create reporting rules

Go to Create and manage reporting rules.

When and how long is data available?

Go to Data retention and lag times.

  • Data sources for the audit and investigation page

Was this helpful?

How can we improve it?

Which of the following power issues can lead to a brownout quizlet?

What can cause a brownout? Overloading electrical circuits can cause a brownout.

What are the two principal security challenges when it comes to mobile device security choose two?

Mobile device security has two principal challenges: portability and capacity.

Which Windows utility command can be used to create a custom management console?

To create a custom MMC, you'll use the runas command. A snap-in is a tool that is hosted in MMC.

Which one of the following data destruction methods involves electromagnetic disruption?

Degaussing Degaussing destroys computer data using a high-powered magnet which disrupts the magnetic field of an electronic medium. The disruption of the magnetic field destroys the data. Degaussing can effectively and quickly destroy the data in a device storing a large amount of information or sensitive data.