From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B9C543B29D for ; Mon, 27 Jul 2020 06:25:12 -0400 (EDT) Date: Mon, 27 Jul 2020 10:25:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1595845511; bh=STSLFASL651RgqKXRz0rBgGM5z7X7JXs7Ezy1PEmI/Y=; h=Date:To:From:Reply-To:Subject:From; b=U+5a5i/vW13KGyxb8UEMWIHD+Qdxaxwgrh3f9OI2sLV/tUNxYAbojo67IpGSap0OL 6Mm47YSWDEzLUCXVd83xbUPZUMnqrpZqXhq0IdNeNox4ecFxXzcgR2/uowGmylJA0X midAv9xyFhm17LMMVuiw0DpOPKUMxhKXBjz6GDLk= To: Michael Yartys via Make-wifi-fast From: Michael Yartys Reply-To: Michael Yartys Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch Subject: [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 10:25:12 -0000 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 muc= h asked for my case to be escalated to a networking specialist straight awa= y, I'll be pretty surprised if it ever makes it to someone that understands= the issue and is interested in trying to fix it. Does anybody know if anyone in the Android world cares about bufferbloat? H= as any chipset vendor or handset manufacturer ever reached out to the buffe= rbloat team? Also, are there any other tests than fast.com that are better at measuring = bufferbloat on Android devices?