From: Mark Finzel <mfinzel@protonmail.com>
To: Kalin KOZHUHAROV <me.kalin@gmail.com>,
kolargol <kolargol@protonmail.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: iOS WG Battery Life
Date: Sat, 02 Mar 2019 00:30:20 +0000 [thread overview]
Message-ID: <ADH75VEasjjK3HQr1kLelM9oY4U-yFZLxMqlG8FaYyToO8t4xGFSExYjnpd_uK3xQHrBy526KnpNXUAzI13IHcA8TiRrvd9pB6F4KoQ8CJE=@protonmail.com> (raw)
In-Reply-To: <CAKXLc7dop2Q7cS0FJ=c0fA4os6HTZQHWuuqPxzb4bygsiRNu6Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1393 bytes --]
FWIW, I haven’t noticed a difference in battery life on iOS. I’m using an iPhone XS, iOS 12.1.4, VPN is always on. So maybe something in your setup?
Sent from ProtonMail Mobile
On Fri, Mar 1, 2019 at 3:08 AM, Kalin KOZHUHAROV <me.kalin@gmail.com> wrote:
> On Fri, Mar 1, 2019 at 11:03 AM kolargol <kolargol@protonmail.com> wrote:
>> I am testing WG on varius OSes and devices and I have noted severe battery drain on iOS (12.2, iPhone 8). Typically battery drops 40% during night-time (that is 7 hours of inactivity on the phone) when WireGuard is engaged.
>>
> Compared to how much during night without activated WireGuard?
>
>> Is this some kind of known issue? I did not had chance to test previous iOS version without SIMD ChaCha20 support so i cannot tell if it is becouse of the last update.
>>
>> Anything i can do to track issue here?
>>
> Is there anything using the interface, or just wg keep-alive?
> May be try to change the keep-alive to a longer period.
> Also (and I have 0 experience with iOS), a keep-alive packet my wake
> up the phone, and let it stay awake for some longer-than-needed
> interval (e.g. 5 minutes).
> Try to have a look at what actually eats the battery: CPU, radio, screen?
>
> Cheers,
> Kalin.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #1.2: Type: text/html, Size: 1701 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-03-08 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 12:07 kolargol
2019-03-01 10:08 ` Kalin KOZHUHAROV
2019-03-02 0:30 ` Mark Finzel [this message]
2019-03-02 7:29 ` kolargol
[not found] ` <EA2CDA40-8988-4C4F-B848-B2F7C6D8716C@lonnie.abelbeck.com>
2019-03-02 19:54 ` kolargol
2019-03-02 20:09 ` John
2019-03-02 20:50 ` Mailing Lists
2019-03-03 15:30 ` kolargol
2019-03-02 21:22 ` Lonnie Abelbeck
2019-03-06 10:32 ` kolargol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ADH75VEasjjK3HQr1kLelM9oY4U-yFZLxMqlG8FaYyToO8t4xGFSExYjnpd_uK3xQHrBy526KnpNXUAzI13IHcA8TiRrvd9pB6F4KoQ8CJE=@protonmail.com' \
--to=mfinzel@protonmail.com \
--cc=kolargol@protonmail.com \
--cc=me.kalin@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).