From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id AE3C03B2A4 for ; Mon, 27 Jul 2020 09:11:26 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1595855483; bh=g2jZfVH4FmBh0ej+Si2yao3V0z+GPTrdZEl5PbLAOtA=; h=From:To:Subject:In-Reply-To:References:Date:From; b=AZ3CrtkIVLAMDUVUzJUkijfTtQO2Jtw/OJEs0TeRIBqTkjSq/4z/Wq/ZaaKOHf91g reihoRl8YKvFtZd5pzJDb8fo0fhVWOrvX5Vt22gKc8m8yJapq2H8KelF2wqskHmMe5 ACaYQJy79yRVbJg5fikaemLmud4WKpU3cCs4oWHcomsUwIJ1rHsZ9fPxPc48KVVlWL hiA1P7ZK0u1duQMtXiIfeyQp3kKnL6uv/BUwoW6hbzwNLIIDKttpf/yoKXQ65QWJJ7 QSYFeXNCqZZxqdNu/pnCKVzRmFScVYodVrlw/S0NAzg8y3XBZ/XKs+VOORzcWqUpOK EIgAJzmK+OxWA== To: Michael Yartys , Michael Yartys via Make-wifi-fast In-Reply-To: References: Date: Mon, 27 Jul 2020 15:11:22 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <877dup5chx.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] Bufferbloat on Android X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jul 2020 13:11:26 -0000 Michael Yartys via Make-wifi-fast writes: > I ran the fast.com test on my Nokia 8.1, and my latency during upload > under poor signal conditions (top speed was 12 Mbps) reached over 800 > ms, which seem to indicate a lot of buffering in the WiFi stack. I've > reached out to HMD/Nokia support to try to make them aware of the > bufferbloat issue, but I haven't heard back from them for over two > weeks now. Although I pretty much asked for my case to be escalated to > a networking specialist straight away, I'll be pretty surprised if it > ever makes it to someone that understands the issue and is interested > in trying to fix it. Yup, me too :/ > Does anybody know if anyone in the Android world cares about > bufferbloat? Has any chipset vendor or handset manufacturer ever > reached out to the bufferbloat team? > > Also, are there any other tests than fast.com that are better at > measuring bufferbloat on Android devices? Not that I'm aware of (for both questions)... :) -Toke