feat(eos): investigate a bug

- **Update /e/OS** – use the Updater in Settings to download the latest release, install it, and reboot. [Step-by-step →](how-to-update/)

- **Factory reset without a screen** – wipe data and storage via ADB commands even if the display is unusable. [Reset guide →](factory-reset/)

- **Build /e/OS** – pull the Docker image, extract blobs, and configure the environment variables before running the build command. [Build guide →](build/)

- **Investigate a bug** – capture logs, fix adb authorizations, and troubleshoot your mobile connection before requesting help. [Investigate the issue →](investigate-bug/)

## Learn

# Investigate a bug

This workflow helps you gather diagnostics, fix USB debugging issues, and diagnose mobile connectivity problems before reporting to support.

## Capture logs

1. Enable Developer options (`Settings > About phone > tap Build number seven times`) and turn on **Android debugging**.

2. Install [`adb`](https://www.xda-developers.com/install-adb-windows-macos-linux/) on your computer, connect the phone, and run `adb devices`. Accept the prompt and tick **Always allow**.

3. Reproduce the issue and run `adb logcat -d > logcat.txt`; review for personal data and share the file with support. If requested, capture the radio buffer via `adb logcat -db radio > radio.txt`.

4. Alternatively, generate a bug report directly from Developer options → **Bug report** (choose Interactive or Full), wait for the notification, then share it via email after confirming the warning.

## Fix unauthorized adb devices

If `adb devices` shows your handset as `unauthorized`:

1. Disconnect USB, run `adb kill-server`, and revoke USB debugging authorizations on the phone.

2. Delete the `adbkey` file in your `.android` directory.

3. Reconnect, approve the prompt, and rerun `adb devices` until it lists your device as authorized.

## Troubleshoot mobile connectivity

1. Verify APN settings (Settings → Network & internet → Mobile network → Advanced → Access Point Names). Edit or add the values provided by your carrier.

2. Cycle through Preferred network type (4G/3G/2G) and ensure the right SIM card owns mobile data when using dual SIMs.

3. Reset network settings (`Settings → System → Advanced → Reset options → Reset Wi‑Fi, mobile & Bluetooth`) for each SIM.

4. Try other SIM cards to isolate SIM/account issues, and manually select your network operator if automatic selection fails.

5. For AT&T/Straight Talk 4G, add an APN named `ims` with type `ims` and protocols `IPv4/IPv6`, then reboot.

6. Capture screenshots of APN settings and the `*#*#4636#*#*` Phone information screen, and share them along with your country, operator, and signal strength when contacting support (paid customers via murena.com/contact-us, community via forum).

## Why do you need a log?

Whenever you run into an issue and try to report it you must have seen the request from the support or development teams to provide a log or a logcat.

A log helps the development team debug the issue and find out the resolution.  

To generate a logcat you would need to enable `adb` on your phone as well as your PC.

## What is `adb`?

`adb` stands for Android Debug Bridge. `adb` is a versatile command-line tool that lets you communicate with a device. The `adb` command facilitates a variety of device actions, such as installing and debugging of apps.

## To enable adb

1. On your phone

   - Enable `Developer options` in `Settings` (`Settings` > `About phone` > Tap `Build number` 7 times).

   - Enable Android debug (`Settings` > `System` > `Developer options` > `Android debugging`).

1. On your computer,

   - Install `adb` on your PC.

   - There could be issues here with the device driver or the OS type. You can find details on how to install `adb` [here](https://www.xda-developers.com/install-adb-windows-macos-linux/).

   - Connect your device to your computer.

   - Detect your device by typing the below command at the command prompt:

     `$ adb devices`

   -  You would have to accept an authorization on your phone. A pop up like this will appear.

<div class="text-center">

  <img src="/images/Allow_USB_Debugging.png" alt="">

</div>

   - Check the option `Always allow from this computer` and click `Ok`.

   - Check that your device is being detected by `adb`.

   - Once you accept the authorization shown above you will see the display on you screen like this.

<div class="text-center">

  <img src="/images/adb_Device_Detected.png" alt="">

</div>

   - If you do not accept the message will say that the device is unauthorized.

## Generate a bug report using adb

   - Try to reproduce the error. For e.g if Music app is crashing then run it again. The app you are   

      facing an issue with will crash.

   - Now Run this command at the command prompt / console:

     `$ adb logcat -d > logcat.txt`

   - This will create a file called logcat.txt in the current folder.

   - Check the file for any personal data. You can either scroll the log file or do a search. Remember the file can be quite large.

   - Once you have the logcat file please share it with the development team as an attachment to the Gitlab error .

   Additionally, the radio buffer can be viewed or stored with logcat. If needed or requested, type the below command:

    `adb logcat -db radio > radio.txt`

  Next save it as `radio.txt` and share with the development team or on Gitlab.

## Capture a bug report from a device

- Pre requisites for sending this report from the device:

   - To be able to attach the bug report once it is created, there should be an email account configured on the phone.

   - Enable `Developer options` on the device. If `Developer options` has not been enabled on your device check [this guide](/pages/enable-usb-debugging). 

  -  In `Developer options`, tap `Bug report`.

<div class="text-center">

  <img src="/images/support-topics/generatelog/generatelog_developeroptions_01.png" alt="">

</div>

  -  Select the type of bug report you want and tap `Report`. Two options will be displayed - `Interactive` and `Full Report`. Check with the developers what type of report they require.

<div class="text-center">

  <img src="/images/support-topics/generatelog/generatelog_logtypes_02.png" alt="">

</div>

 -  After a moment you get a notification that the bug report is ready.

  -  Swipe down on the notifications to share the bug report you just created.

<div class="text-center">

  <img src="/images/support-topics/generatelog/generatelog_notification_03.png" alt="">

</div>

 - You would see a warning regarding the information in your log. Check the logs for any personal information before sharing.

<div class="text-center">

  <img src="/images/support-topics/generatelog/generatelog_notificationwarning_04.png" alt="">

</div>

- Once you have accepted the above warning you will be shown the option to share the information. Here we are assuming you will go ahead with the email option.

<div class="text-center">

  <img src="/images/support-topics/generatelog/generatelog_sharescreen_05.png" alt="">

</div>

- The below screenshot is how the email will show up. Add the email ID of the person or Murena team you want to send the log to.

<div class="text-center">

  <img src="/images/support-topics/generatelog/generatelog_mail_06.png" alt="">

</div>

When running `adb devices` in bash a device is shown as `unauthorized`

1. Disconnect USB between PC and device.

1. Stop adb server by entering `adb kill-server`  in command window.

1. On device use **Revoke USB debugging authorizations**  in **Developer Options**

1. On PC delete `adbkey`  file in user directory, eg. `.android`

1. Reconnect the device to the PC.

1. Check the box on the popup on the device.

1. Open a bash and enter `adb devices`

Device should be shown as shown in this screenshot

![](/images/adb_Device_Detected.png)

    - Update /e/OS: eos/how-to-update.md

    - Factory reset: eos/factory-reset.md

    - Build /e/OS: eos/build.md

    - Investigate a bug: eos/investigate-bug.md

  - Learn:

    - Transparency: eos/transparency.md

    - Spot Search: eos/search.md