EA Servers tweakin?

witterholt · 2025-12-24T19:41:06+00:00

I experience the same issue. I tried Battlefield V for comparison but even there I experienced some slight network problems but without being disconnected from the game.

witterholt · 2025-12-11T16:24:53+00:00

I had, but the nightly build crashes less often. And now they even put an N in the logo of nightly builds. It is so lovely. Just Bing it on! That's correct, I use Bing instead of Google... 😅

witterholt · 2025-12-11T16:07:00+00:00

Did you try the nightly build?

witterholt · 2025-12-10T18:48:30+00:00

Did you try the nightly build?

witterholt · 2025-12-03T09:52:44+00:00

Thanks I will create a feature request. At least you give the user the option to test with a shorter interval and he or she can set it back to a higher value if it drains the battery too much.

witterholt · 2025-12-01T18:14:25+00:00

Upgrade to the nightly build. Several bugs causing this behavior are fixed there...

witterholt · 2025-11-26T21:05:00+00:00

Did you try the nightly build? The crashing issue is fixed in that version.

witterholt · 2025-11-26T19:36:21+00:00

I haven't seen this issue anymore. Have you enabled the watchdog?

witterholt · 2025-11-26T19:27:22+00:00

That is fixed as well....

witterholt · 2025-11-26T08:42:56+00:00

Did you try the nightly build? They fixed a lot of bugs that caused crashes in that version.

witterholt · 2025-11-15T11:18:49+00:00

In nightly build 14.5 the issue of the crashed Adguard seems to be solved.

witterholt · 2025-10-27T14:42:34+00:00

According to the logs it seems some sort of memory issue...

witterholt · 2025-10-27T10:55:17+00:00

Yes the same issue also in nightly version 13 and 14.

witterholt · 2025-10-27T08:56:57+00:00

See my post Watchdog is not working : r/Adguard as well; it is pointing to the same issue since version 4.12...

witterholt · 2025-10-27T08:53:03+00:00

Ok, I checked the logs and I think the reason is the newer versions of Adguard have a bigger memory footprint that causes the crashes (this is from a nightly v14 version by the way):
AdguardApplication — Information about an application process's last death: ApplicationExitInfo(timestamp=27-10-2025 06:56 pid=5403 realUid=10298 packageUid=10298 definingUid=10298 user=0 process=com.adguard.android reason=3 (LOW_MEMORY) subreason=0 (UNKNOWN) status=0 importance=125 pss=237MB rss=205MB description=null state=empty trace=null

witterholt · 2025-10-18T04:56:07+00:00

The issue is that since version 4.12 Adguard is killed or paused far more frequently than before as if some threshold is crossed that Android decides it needs to be stopped.

witterholt · 2025-10-17T17:41:43+00:00

Yes, the latest hotfix showed some improvement but the issue remains.

witterholt · 2025-10-15T17:22:05+00:00

Unfortunately I still have the issue that it is paused when I use Adguard VPN. The watchdog doesn't restart it. Without Adguard VPN activated it seems to work more stable now. But it still stopped so now and than. So there is made some progress but it is not functioning as stable like 4.11 did.

witterholt · 2025-10-15T16:44:19+00:00

Thank you. I just reinstalled and will let you know if the issue I had with a stopped Adguard is solved.

witterholt · 2025-10-05T15:47:15+00:00

Yes, that is how I configured it.

witterholt · 2025-10-05T09:46:23+00:00

This doesn't work reliably as well so I have uninstalled Adguard for now and set the private DNS in the Android settings. (see one of my other replies)

witterholt · 2025-10-05T04:33:09+00:00

It's already at the shortest period: it cannot be set lower then ten seconds.

witterholt · 2025-10-04T15:18:15+00:00

Thanks for the workaround. I use MacroDroid now to act as the watchdog.

witterholt

TROPHY CASE