Huge battery drain

[bam80]

Possibly related with #516, needs testing by more people.

So the first day of test with the proxy showed inadequately huge battery consumption, and I'm afraid this is not a coincidence:

Unfortunately, I can't test without proxy,
but it looks we definitely need to check it out.

I'm afraid this level of the consumption is unacceptable.

Originally posted by @bam80 in #516

[dolonet]

Triage / state-of-play for the next person:

• The technical question is still "does the outbound keep-alive cadence (30s idle / 10s probe / 3 retries, applied to mtg→DC dials) measurably contribute to phone battery drain vs. running Telegram without the proxy". The observation in #516 (comment) is one data point on one phone with no baseline.
• The cheap experiment that answers it is the A/B sketched in #516 (comment): same phone, two mtg instances with DefaultKeepAliveIdle patched to 30s vs 600s, same Telegram session, overnight idle-drain comparison. If patched ≈ stock, keep-alive isn't the culprit and a client-facing knob wouldn't help; if patched < stock by a meaningful margin, the knob has a reason to exist.
• Until that measurement exists, this stays in "needs data", not "ready to design a config option".

Labelling as question + help wanted — anyone with mobile-measurement capability welcome to pick it up.

[bam80]

Possible reason:
Android client can't connect, sni-router log is flooded with:

...
[haproxy] | 192.168.1.228:57360 [20/May/2026:18:27:51.711] tls web/web 4/1/66 0 -- 19/19/0/0/0 0/0
[web]     | {"level":"debug","ts":1779301671.7884865,"logger":"http.stdlib","msg":"http: TLS handshake error from 192.168.1.228:57364: tls: first record does not look like a TLS handshake"}
[haproxy] | 192.168.1.228:57364 [20/May/2026:18:27:51.785] tls web/web 3/0/73 0 -- 19/19/0/0/0 0/0
[web]     | {"level":"debug","ts":1779301671.8709724,"logger":"http.stdlib","msg":"http: TLS handshake error from 192.168.1.228:57376: tls: first record does not look like a TLS handshake"}
...

Here I connect locally, the same happens if connect outside.

Tried with official TG app, too.
It doesn't happen with TG Desktop, with exact same proxy, secret, etc.

Effectively I can't connect at all, so the problem even worse than I thought in the beginning.
It seems it can connect sometimes, but most of the time, after phone is idle for some time, I see this picture and can't recover whatever I try.

Please help, I'm out of ideas.

PS:
If I try with browser, the TLS cert is valid.