From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.5 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 60719C433DB for ; Sun, 3 Jan 2021 15:50:45 +0000 (UTC) Received: from krantz.zx2c4.com (krantz.zx2c4.com [192.95.5.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 577D520795 for ; Sun, 3 Jan 2021 15:50:43 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 577D520795 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=pregonetwork.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=wireguard-bounces@lists.zx2c4.com Received: by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id a4d94a49; Sun, 3 Jan 2021 15:39:43 +0000 (UTC) Received: from jeremyp3.stolon.network (jeremyp3.stolon.network [89.234.146.135]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTPS id 017c0ce1 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Sun, 3 Jan 2021 15:39:41 +0000 (UTC) Received: from jeremyp3.stolon.network (localhost [127.0.0.1]) by jeremyp3.stolon.network (OpenSMTPD) with ESMTP id 2f3707aa; Sun, 3 Jan 2021 16:50:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pregonetwork.net; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=postfix; bh=dlsivwnQ/qOXHraQJ+wX64FgMtY=; b=bD5k0m0EaXF4cseNPFJfJAfPBTxH WKqdlm62yaCWHVtlMsIYe7RUxllVN/AXe1pTSZdeJNN6j+q3tLyQUCtbED1WleN1 1TJ4tBPJ8oHvX2wYZN4fSVMVg+menT+xLPLbxtljr7BVPO80yYygBuJf4JAlnZRl +Xwbn9yATpEqyBzqV/W/l1t3qYcYqXiRjTvLZ3Nrfkl/pIaGJNG3QnnTEnSm3wuM M+bYE4S9Le7aEn+pBR2l6O/xwyMghsTjhlPB2rVAw2gnOmTd2yv+3tldbf5Gr1S1 keREbueHQo6r5CBOZ3/cNsIbhEImeBaCb2Zz3E0PXKEIHKfSTBL+95MDKA== DomainKey-Signature: a=rsa-sha1; c=nofws; d=pregonetwork.net; h=subject :to:cc:references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=LtK ff1/Ip46P+iRGROPeddwY4kZ4rvg9c2zpybd0FYNyFxIjqqU6z1s9JdD4W4A7Rpz A+6TFjMgDESpr01pOopQ9bX/A47zhFHqsGX8Eak7bEZ0avBbRQVkcfFg+5ERaBPl BKT1niQiqnN5iyzJ38gokzgxsXwoU6SnXFn6wP1qI8geqw2XvDAJ+ut3UgNTpAwy ltNjYTUWttJIhvsZErYQdkUnH0qMV60rpinD7PhcL8BODGWmBF7K8/g5nXVlK5vR ih6+TCTnkTnq5xl29Dno0n0nlh7h1ksjN/jQT6Gm0VlFGkdgSuN5mg5HMZFr4o2h OlvRhKIUS2kY8jh8qog== Received: from [192.168.80.10] (backupmail.domain.tld [10.4.4.2]) by jeremyp3.stolon.network (OpenSMTPD) with ESMTPSA id e31f0de0 (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO); Sun, 3 Jan 2021 16:50:22 +0100 (CET) Subject: Re: Wireguard Android: the application is stopped unexpectedly To: Harsh Shandilya Cc: wireguard@lists.zx2c4.com, team@wireguard.com References: <85807215-9af1-ed2d-d96c-9c3c4a41ad2c@pregonetwork.net> <2eb5a0785205119f1ec1d82bcef84e80@msfjarvis.dev> From: =?UTF-8?B?SsOpcsOpbXkgUHJlZ28=?= Message-ID: <9a398613-e032-74e7-61cb-784ed1c2957b@pregonetwork.net> Date: Sun, 3 Jan 2021 16:50:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <2eb5a0785205119f1ec1d82bcef84e80@msfjarvis.dev> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: fr X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" hello, thanks for the reply réponse inline: Le 03/01/2021 à 14:43, Harsh Shandilya a écrit : > I'm rather confident that this is MIUI's doing, because I have a > Samsung phone that has been running the same WireGuard client for 14 > days straight without failing or being force closed. on my old p10 lite phone, wireguard worked without any issues > Is there a possibility that a new MIUI "optimisation" showed up that > you did not disable yet? i dont think i have disabled all miui optimization i found on the internet. the strangest thing is that it can work for several days and end up stopping ... suddenly I don't know how I can get more information to know if it comes from miui or from the wireguard Jerem Le 03/01/2021 à 14:43, Harsh Shandilya a écrit : > Hey Jérémy, > > On 2021-01-02 11:39, Jérémy Prego wrote: >> hello and happy new year, >> >> I have a problem with the wireguard application on my Xiaomi poco m3 >> (Android 10 / miui 12.0.5). I have set all the correct permissions so >> that the application is not killed by miui, but it always ends up >> stopping anyway. >> In the attached log, I see some errors when stopping the application, >> around 11:30 am > > The auditd lines are harmless, and the app itself seems to have no > information as to why its being killed. There are no crashes, and no > fatal errors being logged. I'm rather confident that this is MIUI's > doing, because I have a Samsung phone that has been running the same > WireGuard client for 14 days straight without failing or being force > closed. Is there a possibility that a new MIUI "optimisation" showed > up that you did not disable yet? I don't believe the reason for your > issue is a bug in the app. > >> >> I remain available if you need more information >> >> thanks, >> >> Jerem > > Cheers, > Harsh