Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AdGuard Nightly causing my Phone to heat up #5524

Open
5 of 6 tasks
Batman2814 opened this issue Nov 29, 2024 · 27 comments
Open
5 of 6 tasks

AdGuard Nightly causing my Phone to heat up #5524

Batman2814 opened this issue Nov 29, 2024 · 27 comments
Assignees

Comments

@Batman2814
Copy link

Please answer the following questions for yourself before submitting an issue

  • Filters were updated before reproducing an issue
  • I checked the knowledge base and found no answer
  • I checked to make sure that this issue has not already been filed

AdGuard version

Version 4.7 Nightly 60

Environment

  • OS version: Android 14 One UI 6.1
  • Device: Samsung Galaxy S24 Ultra

HTTPS filtering

  • yes, I do

Root access

  • yes, I have it

Integration with AdGuard VPN

  • yes, I do

Routing mode

Local VPN

Ad Blocking

AdGuard Base filter, AdGuard Mobile Ads filter

Privacy

AdGuard Tracking Protection filter, AdGuard URL Tracking filter, EasyPrivacy

Social

AdGuard Social Media filter, Fanboy's Social Blocking List

Annoyances

AdGuard Cookie Notices filter, AdGuard Popups filter, AdGuard Mobile App Banners filter, AdGuard Other Annoyances filter, Adblock Warning Removal List

Security

Online Malicious URL Blocklist

Language-specific

AdGuard Chinese filter, AdGuard German filter, AdGuard Japanese filter, AdGuard Russian filter, AdGuard Ukrainian filter

Other

No response

Which DNS server do you use?

Custom DNS

DNS protocol

DNS-over-QUIC

Custom DNS

No response

What Stealth Mode options do you have enabled?

Block trackers, Remove tracking parameters from URLs, Hide your search queries, Ask websits not to track you, Self-destruction of third-party cookies, Block ETag and If-None-Match headers, Disable WebRTC, Block Push API, Block Location API, Hide your Referrer from third-parties, Hide your IP address, Remove X-client-Data header from HTTP request, Protect against DPI

Issue Details

Steps to reproduce:
1.
2.
3.

Expected Behavior

Should not cause my phone to heat up.

Actual Behavior

When AdGuard Adblocker is enabled my phone heats up when causes my phone to show a message saying "your phone is to hot wait until it cools down".

Screenshots

Screenshot 1

Additional Information

I disabled adguard to see if it is the problem and it was the problem because when disabling adguard my phone doesn't heat up.

@AlgorithmOfGithub
Copy link

Same
Samsung S24+
v4.7 N60

@0xrxL
Copy link

0xrxL commented Nov 29, 2024

@Batman2814

1). Set AdGuard Registration Log on Debug.
2). Export the log after 30 minutes of device use.
3). Send the log to the email address that you'll found here: #5505

@Batman2814
Copy link
Author

The logs have been sent.

@Batman2814
Copy link
Author

If AdGuard is not the culprit, I think it might be the Samsung Health app. If anyone else can confirm this after doing some tests of their own, it would be much appreciated.

@ameshkov
Copy link
Member

ameshkov commented Dec 2, 2024

@Batman2814 please check battery stats in AdGuard, what CPU time value do you see there?

Also, check battery stats in Android itself, what app is in the top there?

@Batman2814
Copy link
Author

Screenshot_20241202_073118_Device care.jpg

Screenshot_20241202_073134_Device care.jpg

@Batman2814
Copy link
Author

Screenshot_20241202_073413_AdGuard.jpg

@Batman2814
Copy link
Author

Screenshot_20241202_075731_Device care.jpg

Screenshot_20241202_075741_Device care.jpg

@Versty
Copy link
Contributor

Versty commented Dec 2, 2024

@Batman2814 We have examined the logs from your device, and have spotted one potentially problematic event.
Unfortunately, the default logging level was active at this moment.

Could you please enable Debug logging level, relaunch AdGuard and enable protection, use your device as usual for a 3-4 hours, then export logs and send it qa@adguard.com with [android] keyword and 5524 number in the subject?

@Batman2814
Copy link
Author

Okay, I'll send it your way once the four hours are up.

@Batman2814
Copy link
Author

Logs have been sent

@Versty
Copy link
Contributor

Versty commented Dec 5, 2024

@Batman2814 Our developers added additional logging to the latest nightly version. We believe that this logging will help find the root cause. Therefore, would you please upgrade to version 4.8 nightly 3, then collect and submit the logs once again, following the same instructions?

@Batman2814
Copy link
Author

The logs have been sent.

@Versty
Copy link
Contributor

Versty commented Dec 9, 2024

@Batman2814 Collecting this file is a bit complicated, but important in order to find the exact cause of the issue.
Therefore, we kindly ask you to follow the instruction below.

What you need to know

  • Collecting the necessary information will take 15-20 minutes.
  • You need to know how to use command line to do that.
  • You should use v4.8 nighly 3

Please follow the steps that I describe below to collect all the necessary information.

Install adb

The necessary step is to install adb ("android debug bridge"), here's the instruction on how to do that.
This is probably the most complicated step of the whole instruction.

Please make sure that adb is properly installed and your device is connected by running adb devices after everything has been set up.

Enable debug-level logging in AdGuard

In addition to the information collected via adb we'll need the debug-level log so that we could

  1. Settings -> General -> Advanced -> Logging level.
  2. Set the logging level to debug.

We'll need this log later alongside everything else.

Find AdGuard's process ID

Now that you have adb installed we can start using it. However, every command that we need requires AdGuard's process ID.

To find run this command adb shell "ps | grep com.adguard.android", the number in the second column is the process ID.

Here's how it will look like

image

Threads statistics

Now we need to find which thread consumes CPU and for that please use the following command:

adb shell "top -H -p PROCESS_ID > /storage/emulated/0/Download/stats.txt"

Replace PROCESS_ID with the process ID from the previous step.

This command will run until you press Control + C (or Cmd + C on macOS) and it will be recording the threads CPU usage information to the file stats.txt.

Let it run for 15 minutes and do something with your device that usually triggers higher CPU usage, try to emulate how you normally use your device.

Once you finished, press Control + C (or Cmd + C on macOS).

Now you can run adb pull /storage/emulated/0/Download/stats.txt to download the file from your device to the computer.

Here's how it will look like

image

Export logs

Finally, export AdGuard logs: Settings -> General -> Advanced -> Export logs

Send the info

Send the data to qa@adguard.com, here's what we'll need:

  1. Logs archive
  2. stats.txt

Please mention the [android] keyword and the #5524 number in the email subject line.

@Batman2814
Copy link
Author

How do I do this on an Android Galaxy device? This says it's for Windows, Linux, and iOS, but not Android.

@Versty
Copy link
Contributor

Versty commented Dec 11, 2024

@Batman2814 To perform these steps, you will need both your Android Galaxy device and a PC.

@Batman2814
Copy link
Author

I sent the logs. Let me know if I did it correctly. Can I update AdGuard Nightly to nightly 4, or should I stay on nightly 3 until I know the logs are correct, just in case I have to do that again?

@Versty
Copy link
Contributor

Versty commented Dec 17, 2024

@Batman2814 You can upgrade to the latest nightly version, if you wish.
The logs are collected in the correct way.

@sk1llsh0t
Copy link

I had sent in logs and thread cpu stats. Looking for an update on this.

I don't even have to be browsing. Immediately after initial startup of the app, the cpu goes to 100+% immediately.

@Versty
Copy link
Contributor

Versty commented Dec 20, 2024

@sk1llsh0t Hi!
On app launch, a lot of application modules start at the same time, which can cause CPU spike for a few seconds. After the application has started, the CPU usage should return to its normal level.

Unfortunately, I do not see any emails with 5524 number in the subject from you.
Have you sent it to qa@adguard.com?

@sk1llsh0t
Copy link

sk1llsh0t commented Dec 20, 2024 via email

@Versty
Copy link
Contributor

Versty commented Dec 20, 2024

@sk1llsh0t

Can you please provide the ticket number?

@sk1llsh0t
Copy link

sk1llsh0t commented Dec 20, 2024 via email

@Versty
Copy link
Contributor

Versty commented Dec 28, 2024

@sk1llsh0t @Batman2814 We have found the root cause of this issue and are currently working on the fix.
The fix will be included in one of the next nightly versions.

As temporary solution, please clear the AdGuard app data in the system settings.

@Batman2814
Copy link
Author

Ok thanks

@Batman2814
Copy link
Author

After I cleared the app data for AdGuard in the system settings I Imported back my settings on how it was set before then when I went into the AdGuard Diagnostics web page ' tracking protection" wasn't showing a checkmark.

Screenshot_20241228_171832_Samsung Internet.jpg

@Batman2814
Copy link
Author

AdGuard Diagnostics is saying tracking protection is enabled now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants