Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] SpaceX/Starlink says it's ready for a fall satellite-to-cell service with T-Mobile
Date: Wed, 5 Jun 2024 13:30:00 +0200	[thread overview]
Message-ID: <d519393f-b54b-4df8-872b-ba37fbbaa087@gmail.com> (raw)
In-Reply-To: <9687.1717527495@obiwan.sandelman.ca>


Le 04/06/2024 à 20:58, Michael Richardson via Starlink a écrit :
> Eugene Y Chang via Starlink <starlink@lists.bufferbloat.net> wrote:
>      > I observe a difference in my phone’s batter life between urban and
>      > rural usage. I expect the battery life to be significantly reduced with
>      > Starlink.  And yes… if the phone isn’t communicating then the battery
>
> Sure, but if my phone is plugged into my car, and it's sitting on the
> dashboard, that still seems like a win to me.
> (Except for people who were hoping to unplug their kids by going camping)
>
> The service across northern ontario, along the Trans-Canada is still very
> poor (okay, I was last there in 2018).

A phone plugged on the power of the car, but not on its roof antenna, 
and with windows closed - one should worry about strong EM waves and 
health in a first place.

Besides, such an in-car phone might have little chance to talk up to 
satcom 5G direct-to-cell (direct-to-smartphone, -to-device, 'D2D' but 
not 'device-to-device'; care about these terms, they are wrongly used 
and abundantly these days, probably because it's at the beginning).

Similarly, in-_plane_ smartphones might have similar problems to talk 
up(?) to satcom 5G.

It might work, maybe very badly, maybe with very low bandwidth and high 
latencies, if at all.

The frequency range around 800MHz (and not 1GHz-3.5GHz) has been 
mentioned for direct-to-cell.   This frequency set was often touted 
advantageously for car 4G communications but it has not really been 
used.  Maybe it'll be re-proposed for satcom 5G NTN, because it is 
little occupied but present in many smartphones.

Alex

>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

  parent reply	other threads:[~2024-06-05 11:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 18:08 Frantisek Borsik
2024-06-03 18:17 ` the keyboard of geoff goodfellow
2024-06-04 12:32   ` Alexandre Petrescu
2024-06-03 20:47 ` Eugene Y Chang
2024-06-03 21:16   ` David Lang
2024-06-03 21:57     ` Eugene Y Chang
2024-06-03 21:59       ` Frantisek Borsik
2024-06-03 22:41       ` David Lang
2024-06-04  0:13         ` Eugene Y Chang
2024-06-04  0:54           ` David Lang
2024-06-04 11:20             ` Frantisek Borsik
2024-06-04 11:43               ` Alexandre Petrescu
2024-06-04 11:54                 ` Frantisek Borsik
2024-06-04 13:11                   ` Ulrich Speidel
2024-06-04 18:10                     ` David Lang
2024-06-04 18:51                       ` Eugene Y Chang
2024-06-04 18:58       ` Michael Richardson
2024-06-04 23:01         ` Mike Puchol
2024-06-05  3:17           ` David Lang
2024-06-05  4:16             ` Mike Puchol
2024-06-05  4:26               ` David Lang
2024-06-05  4:47               ` Sebastian Moeller
2024-06-05  6:12                 ` Mike Puchol
2024-06-05  7:03                 ` David Lang
2024-06-05 11:30         ` Alexandre Petrescu [this message]
2024-06-04 10:42 David Fernández

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

  List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d519393f-b54b-4df8-872b-ba37fbbaa087@gmail.com \
    --to=alexandre.petrescu@gmail.com \
    --cc=starlink@lists.bufferbloat.net \
    /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