automatically update translations

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md

@@ -9,33 +9,19 @@ This article covers AdGuard for Android, a multifunctional ad blocker that prote
 
 :::
 
-Sometimes you may notice that, according to Android built-in statistics, AdGuard consumes a lot of traffic and/or battery resource.
+On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated.
 
-Both these problems are two sides of the same coin. Since in the process of filtering all the mobile traffic goes through AdGuard, Android decides that it is AdGuard that consumes it all. In reality, of course, it is not true.
+With OS 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data.
 
-Battery and traffic consumption shown in devices statistics **do not represent the facts**. The thing is, Android attributes all of the WiFi and Mobile traffic to AdGuard, which was in fact consumed by other apps. Due to this, AdGuards real share of total consumed traffic and battery resource increases, and the share of other apps, on the contrary, decreases.
+Nevertheless, AdGuard users can always get a true picture of the situation on the *Battery usage* screen.
 
 ### Own battery usage stats screen
 
-To mitigate this misconception, we added a new screen called 'Battery usage'. You can access it by tapping on the battery icon in the top right corner of the main screen.
+You can access it by navigating to *Statistics* → *Battery usage*.
 
-![Battery stats *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/battery/batterystats.png)
+![Battery stats *mobile_border](https://cdn.adtidy.org/content/articles/battery/1.png)
 
-Inside you will find a chart that shows the AdGuard battery resource consumption within the last 24 hours, with an option to get more detailed hour-to-hour data by tapping on the dots on the chart. Besides that, there’s also a numeric breakdown of the relevant data and a short technical explanation.
-
-### Real example
-
-On the screenshots below you can see the battery resource consumption statistics for a night and subsequent morning:
-
-![Battery 1 *mobile](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/battery_1.png) ![Battery 2 *mobile](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/battery_2.png) ![Battery 3 *mobile](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/battery_3.png)
-
-From these screenshots you can see that:
-
-1. AdGuard, as expected, is at the top of the chart. This is generally typical for smartphones (and not at all for tablets without 4G, since WiFi is much less 'costly' in terms of battery consumption).
-
-2. Pay attention to the number of sent Mobile and WiFi packages, which were attributed to AdGuard (Mobile packets sent и Wi-Fi packets sent) on the second screenshot.
-
-3. On the third screenshot are stats for one of the real traffic consumers, Yandex.Browser. It was not attributed almost any traffic at all, while in reality 70% of the total traffic was consumed by it.
+Inside you will find a chart that shows the AdGuard battery resource consumption within the last 24 hours, with an option to get more detailed hour-to-hour data by tapping on the chart. Besides that, there’s also a numeric breakdown of the relevant data and a short technical explanation.
 
 ### How much battery resource does AdGuard really consume?
 

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md

@@ -1,6 +1,6 @@
 ---
 title: Known compatibility issues with Android apps
-sidebar_position: 15
+sidebar_position: 16
 ---
 
 :::info
@@ -14,49 +14,52 @@ This article covers AdGuard for Android, a multifunctional ad blocker that prote
 Other VPN apps are incompatible with AdGuard running in the Local VPN filtering mode since you cannot have two active VPNs at the same time. To solve this problem we suggest you:
 
 * use [AdGuard VPN](https://adguard-vpn.com/welcome.html) — it has Integrated mode that allows two apps to operate seamlessly
-* use AdGuard in Local HTTP Proxy mode. *Please note that 'manual' HTTP Proxy mode is not supported on devices since Android 10*
-* if you use a third-party VPN app, figure out whether it supports SOCKS4/SOCKS5 mode. If it does, you can configure your VPN app to work as outbound proxy and set up local outbound proxy with params from the third-party app. For instance, AdGuard can be automatically configured with 'Orbot: Proxy with Tor'
+* use AdGuard in Local HTTP Proxy mode
+
+:::caution
+
+Please note that on Android 10 and later devices, the 'manual' HTTP proxy mode is no longer supported.
+
+:::
+
+* configure your VPN app to to act as an outbound proxy and set up a local outbound proxy using the parameters from the third-party app. To do this, a third-party VPN app must support SOCKS4/SOCKS5 mode. For example, AdGuard can be automatically configured with 'Orbot: Proxy with Tor'.
 
 ## Private DNS
 
 The Private DNS feature was introduced in Android Pie. Before version Q, Private DNS didn't break AdGuard DNS filtering logic and the DNS forwarding through AdGuard worked normally. But starting from version Q, the presence of Private DNS forces apps to redirect traffic through the system resolver instead of AdGuard. See Android [devs blog](https://android-developers.googleblog.com/2018/04/dns-over-tls-support-in-android-p.html) for more details.
 
-:::tip
+* To solve the problem with Private DNS, use the `$network` rule
 
 Some device manufacturers keep Private DNS settings hidden and set 'Automatic' mode as a default one. Thus, disabling Private DNS is impossible but we can make the system think that the upstream is not valid by blocking it with a `$network` rule. For instance, if the system uses Google DNS by default, we can add rules `|8.8.4.4^$network` and `|8.8.8.8^$network` to block Google DNS.
 
-:::
-
 ## Unsupported browsers
 
 ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD
 
 To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there.
 
-**Solution**
+* To solve this problem, move the certificate to the system certificate store
 
-*Requires root access*. To solve this problem, move the certificate to the system certificate store.
+:::caution
 
-### Opera mini: Opera mini, Opera mini with Yandex
+Requires root access.
 
-Opera mini drives traffic through a compression proxy by default and AdGuard is not able to decompress and filter it at the same time.
-
-**Solution**
-
-There is no solution at this moment.
+:::
 
 ### Dolphin Browser: Dolphin Browser, Dolphin Browser Express
 
 AdGuard cannot filter its traffic when operating in **Manual proxy mode** because this browser ignores system proxy settings.
 
-**Solution**
+* Use the **Local VPN** filtering mode to solve this problem
+
+### Opera mini: Opera mini, Opera mini with Yandex
+
+Opera mini drives traffic through a compression proxy by default and AdGuard is not able to decompress and filter it at the same time.
 
-Use *Local VPN* filtering mode.
+* There is no solution at this moment
 
 ### Puffin Browser: Puffin Browser, Puffin Browser Pro
 
 Puffin Browser drives traffic through a compression proxy by default and AdGuard is not able to decompress and filter it at the same time.
 
-**Solution**
-
-There is no solution at this moment.
+* There is no solution at this moment

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md

@@ -14,13 +14,13 @@ The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a
 
 ## How to get HAR files
 Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps:
-1. Open AdGuard and go to "Settings".
-2. Choose "Advanced" in the menu.
-3. Choose "Low Level Settings".
-4. Activate "pref.har.capture" (you will have to restart the protection).
-5. Now reproduce the problem - open the app, perform the necessary actions to make the ad appear.
-6. Now turn "pref.har.capture" off again.
-7. Go back and tap "Export logs and system info" → Save.
+1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner).
+2. Tap **General** →**Advanced** → **Low-level settings**.
+3. Scroll down and activate **Capture HAR** in the Filtering section.
+4. Open the app and perform the necessary actions to reproduce the problem.
+5. Turn **Capture HAR** off.
+6. Go back to **Advanced**.
+7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**.
 
 **Please send the file with logs (that you've got as a result) to the AdGuard support service.**
 

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md

@@ -1,6 +1,6 @@
 ---
 title: Moving CA certificate to System store on rooted devices
-sidebar_position: 13
+sidebar_position: 14
 ---
 
 :::info
@@ -15,11 +15,15 @@ On non-rooted devices CA certificates can be installed to the **User store**. On
 
 However, on rooted devices, you can install the certificate to the **System store** and allow HTTPS filtering of other apps' traffic too.
 
+
 Here's how to do that.
 
 ## How to install AdGuard's Certificate to System store (on a rooted device)
 
 1. Enable HTTPS filtering in AdGuard for Android and save AdGuard's certificate to the User store (use [this instruction](../../overview#https-filtering) if needed)
+
+> From AdGuard for Android v4.1 and after users can install two certificates to the User store, which will help to filter websites in Chrome browser.
+
 2. Go to **AdGuard app** → **Menu** (≡) → **Settings** → **Network** → **HTTPS filtering** → **Security certificate** → tap “**Copy to the system store**”
 
 That is enough for older versions of Magisk.
@@ -52,7 +56,7 @@ In that case, proceed to steps below:
 
 7. Reboot
 
-![Reboot the device](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-7.png)
+![Reboot the device *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-7.png)
 
 If a new version of "AdGuard certificate" module comes out, repeat steps 3-7 to update the module.
 

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md

@@ -1,5 +1,5 @@
 ---
-title: How to collect a full log
+title: How to collect debug logs
 sidebar_position: 2
 ---
 
@@ -9,40 +9,20 @@ This article covers AdGuard for Android, a multifunctional ad blocker that prote
 
 :::
 
-Sometimes in order to understand a problem and fix it we need to collect **log files**, or **logs**. Basically, these files contain information about the program and it's work.
+In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team askes you to provide debug logs, simply follow these instructions.
 
 ### Collecting debug log
 
 To collect **debug** log and send it to us you need to perform following steps:
 
-1. Open AdGuard and go to "Settings".
+1. Go to *Settings* → *General* → *Advanced*.
+2. Tap *Logging level* and set it to *Debug*.
+3. Reproduce the problem and try to remember the exact time it occurred.
+4. Wait a while, then return to *Settings* and choose the *Support* tab. Tap *Report a bug* and complete the required fields. Don't forget to check the *Send app logs and system info* checkbox. Finally tap *Send*.
 
-2. Choose "Advanced".
+If you're interested in following the resolution of your issue and engaging in a dialogue with the developers, we recommend that you take the following steps after completing the first three:
 
-3. Set "Logging level" to "Record everything". It's desirable to close all background apps that don't concern the problem beforehand.
+4. Wait a while, then return to the *Advanced* screen and export logs via *Export logs and system info*. Then report a bug on GitHub by following these [instructions](/guides/report-bugs.md).
+5. After creating an issue on GitHub, send the log file to devteam@adguard.com. Include the time of the bug and attach a link to your issue or its number (it appears as #number next to the title). Alternatively, you can upload the log file to Google Drive and send it to devteam@adguard.com. Add the file link to your GitHub issue
 
-4. Reproduce the problem and set the logging level back to "Default". Notice the exact time when it happened.
 
-5. Send us a message from program by choosing "Support" → "Send Feedback" in the menu. Don't forget to check the "Send detailed system info" checkbox under the text field and to include the timestamp from the step 4 into the message.
-
-As an alternative, you can export the logs (along with the *state.txt* file that contains system information and information about AdGuard settings) directly into a local file. It can be convenient, for example, if you are having a conversation with a developer on [GitHub](https://github.com/AdguardTeam/AdguardForAndroid/issues), [forum](https://forum.adguard.com/) or on another platform.
-
-To export logs and system information into a file, go to "Settings" — "Advanced" and tap "Export logs and system info". Select the destination folder and tap "Save".
-
-### Collecting web requests log
-
-To collect **web requests** log and send it to us you need to perform following steps:
-
-1. Open AdGuard and go to "Settings".
-
-2. Choose "Advanced".
-
-3. Set "Logging level" to "Record web requests". It's desirable to close all background apps that don't concern the problem beforehand.
-
-4. Reproduce the problem and set the logging level back to "Default". Notice the exact time when it happened.
-
-5. Send us a message from program by choosing "Support" → "Send Feedback" in the menu. Don't forget to check the "Send detailed system info" checkbox under the text field and to include the timestamp from the step 4 into the message.
-
-As an alternative, you can export the logs (along with the *state.txt* file that contains system information and information about AdGuard settings) directly into a local file. It can be convenient, for example, if you are having a conversation with a developer on [GitHub](https://github.com/AdguardTeam/AdguardForAndroid/issues), [forum](https://forum.adguard.com/) or on another platform.
-
-To export logs and system information into a file, go to "Settings" — "Advanced" and tap "Export logs and system info". Select the destination folder and tap "Save".

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md

@@ -1,28 +1,33 @@
 ---
-title: How to get Logcat log
+title: How to get system logs
 sidebar_position: 4
 ---
 
 :::info
 
-This article covers AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://adguard.com/download.html?auto=true)
+This article covers AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, firsthand [download the AdGuard app](https://adguard.com/download.html?auto=true)
 
 :::
 
-## General Instruction
-
-For troubleshooting problems with crashes a regular log is almost always not enough. In such cases to identify the origin of the problem we need the system log. Below is the instruction how to collect and get it.
+Sometimes a regular log may not be sufficient to identify the origin of the problem. In such cases a system log is needed. Below are instructions on how to collect and get it: via Developer options and Logcat.
 
 ## Capture a bug report from a device
+
 To get a bug report directly from your device, do the following:
 
-1. Be sure you have [Developer Options](https://developer.android.com/studio/run/device.html#developer-device-options) enabled.
+1. Be sure you have [Developer options](https://developer.android.com/studio/run/device.html#developer-device-options) enabled.
 
 2. In **Developer options**, tap **Take bug report**.
 
 ![Bug report *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreporten.png)
 
-3. Select the type of bug report you want and tap **Report**. >After a moment you get a notification that the bug report is ready (see figure 2).
+3. Select the type of the bug report you want and tap **Report**.
+
+::: note
+
+After a moment, you will see a notification that the bug report is ready (see Figure 2).
+
+:::
 
 ![Bug report *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreporteen.png)
 
@@ -32,15 +37,17 @@ To get a bug report directly from your device, do the following:
 
 5. Send this log to our support team.
 
-:::note
+::: note
 
 Our support team will process your ticket much faster if you specify the HelpDesk ticket number or the GitHub issue number in your message to support.
 
 :::
 
-## Additional Instruction (for old Android versions)
+## Capture a bug report via Logcat
+
+On devices with Android 7 and below, it is not possible to send a bug report automatically. Then you can capture it manually via Logcat — a standard Android command-line tool that dumps a log of system messages.
 
-On old Android devices there is no such option to take a bug report automatically. It has to be done manually by following this instruction:
+Follow this instruction:
 
 **Part #1: prepare the device**
 
@@ -52,30 +59,37 @@ On old Android devices there is no such option to take a bug report automaticall
 
 4. Increase **Logger buffer** sizes to 4MB per log buffer.
 
-4MB should be enough for storing the logs we need until you're able to do the second part (getting log from the device);
+4 MB should be enough for storing the logs we need until you're able to do the second part (getting the log from the device);
+
+**Part #2: reproduce the problem**
+
+It is important to reproduce the problem after you're done with the first part.
+
+1. Reproduce the problem.
 
-**Important:** you need to reproduce the problem after you've done with the first part!
+2. Remember/write down the date and time of reproduction and include it in the email to our support later.
 
+**Part #3: get the log**
 
-**Part #2: get the log**
+1. Connect your device to a PC with a USB cable.
 
-1. Connect your device to PC with USB cable.
+2. Download [Android SDK Platform Tools](https://developer.android.com/studio/releases/platform-tools#downloads). Choose the appropriate download link for your OS from the Downloads section. Once you tap the link, a ZIP file will be downloaded. You can extract the ADB (Android Debug Bridge) files from the ZIP file and store them wherever you want.
 
-2. Download and install Minimal ADB:
+3. Test whether ADB is working properly: connect your Android device to your computer using a USB cable, open the Command Prompt, PowerShell or Terminal and run the following command:
 
-<http://forum.xda-developers.com/showthread.php?t=2317790>
+`adb devices`
 
-Direct download link:
+An example of a successful result:
 
-<https://www.androidfilehost.com/?fid=24052804347803384>
+![Step 3](https://cdn.adtidy.org/content/kb/ad_blocker/android/logcat/logcat_step-3.png)
 
-3. Run this command in the console (it will be opened after install):
+4. Then run the following command (insert the relevant path):
 
-adb logcat -v threadtime -d > C:\logcat.txt
+`adb logcat -v threadtime -d > C:\Program Files\platform-tools\logs.txt`
 
-Send this log to us by contacting support or by any other way.
+Email the created `txt` file as well as the time the problem was reproduced (from part #2) to our support team at support@adguard.com.
 
-**Alternative way for ROOT users:**
+### Alternative way for ROOT users:
 
 1. Download and run [Logcat](https://play.google.com/store/apps/details?id=com.pluscubed.matlog).
 
@@ -87,7 +101,7 @@ Send this log to us by contacting support or by any other way.
 
 5. Send this log to our support team.
 
-:::note
+::: note
 
 Our support team will process your ticket much faster if you specify the HelpDesk ticket number or the GitHub issue number in your message to support.