Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Eugene Y Chang <eugene.chang@ieee.org>
To: David Lang <david@lang.hm>
Cc: Eugene Y Chang <eugene.chang@ieee.org>,
	Frantisek Borsik <frantisek.borsik@gmail.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] SpaceX/Starlink says it's ready for a fall satellite-to-cell service with T-Mobile
Date: Mon, 3 Jun 2024 11:57:16 -1000	[thread overview]
Message-ID: <32AD770E-336E-4CF4-8B1B-8AE7353981CC@ieee.org> (raw)
In-Reply-To: <o29q52qp-p7p8-711q-q0ns-57or8866854n@ynat.uz>


[-- Attachment #1.1: Type: text/plain, Size: 4502 bytes --]

I expect low data rate because the distance will fall back to a lower coding rate.

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 life isn’t drawn down much…
But users with high screen times will have to change their habits.
— avoid receiving text messages (not under the user’s control)
— don’t receive email pushes
— stop all the social media updates, messages, and likes.
— turn off the apps
— only use the phone for emergencies.

Who are the intended users?

Gene
----------------------------------------------
Eugene Chang
IEEE Life Senior Member
IEEE Communications Society, Computer Society, & Signal Processing Society,
    Hawaii Chapter Chair
IEEE Life Member Affinity Group Hawaii Chair
IEEE Entrepreneurship, Mentor
eugene.chang@ieee.org
m 781-799-0233 (in Honolulu)



> On Jun 3, 2024, at 11:16 AM, David Lang <david@lang.hm> wrote:
> 
> This is a fallback that will only be if there is no other coverage, and will be a poor data rate.
> 
> I would expect that the impact to the phone battery would be less than the phone continually searching for a tower
> 
> Also, SpaceX has pushed back, according to them this isn't observed interference with their signals, instead they reconfigured a satellite to the direct-to-phone frequencies and were able to detect them
> 
> we'll see what the real story is.
> 
> On Mon, 3 Jun 2024, Eugene Y Chang via Starlink wrote:
> 
>> Date: Mon, 3 Jun 2024 10:47:32 -1000
>> From: Eugene Y Chang via Starlink <starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net>>
>> Reply-To: Eugene Y Chang <eugene.chang@ieee.org <mailto:eugene.chang@ieee.org>>
>> To: Frantisek Borsik <frantisek.borsik@gmail.com <mailto:frantisek.borsik@gmail.com>>
>> Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net>>
>> Subject: Re: [Starlink] SpaceX/Starlink says it's ready for a fall
>>    satellite-to-cell service with T-Mobile
>> I found this line in the article very interesting: The larger 2nd generation SpaceX satellites can connect to the majority of T-Mobile’s 4G and 5G phones over its 1900 MHz spectrum.
>> 
>> It is exciting a subscriber does not need to buy a new phone.
>> What is the expected impact to the phone’s battery life?
>> Any speculations?
>> 
>> Gene
>> ----------------------------------------------
>> Eugene Chang
>> eugene.chang@ieee.org
>> o 781-799-0233
>> 
>> 
>> 
>> 
>>> On Jun 3, 2024, at 8:08 AM, Frantisek Borsik via Starlink <starlink@lists.bufferbloat.net> wrote:
>>> 
>>> SpaceX & T-Mobile intend to launch direct-to-device (D2D) satellite servicethis fall
>>> An analyst told us that will give them an 18- to 24-month lead over some rivals
>>> AT&T & Verizon are still backing AST SpaceMobile as an alternative
>>> 
>>> https://www.fierce-network.com/wireless/space-x-says-its-ready-fall-direct-satellite-cell-service-t-mobile <https://www.fierce-network.com/wireless/space-x-says-its-ready-fall-direct-satellite-cell-service-t-mobile><https://www.fierce-network.com/wireless/space-x-says-its-ready-fall-direct-satellite-cell-service-t-mobile <https://www.fierce-network.com/wireless/space-x-says-its-ready-fall-direct-satellite-cell-service-t-mobile>>
>>> 
>>> All the best,
>>> 
>>> Frank
>>> 
>>> Frantisek (Frank) Borsik
>>> 
>>> 
>>> 
>>> https://www.linkedin.com/in/frantisekborsik <https://www.linkedin.com/in/frantisekborsik> <https://www.linkedin.com/in/frantisekborsik <https://www.linkedin.com/in/frantisekborsik>>
>>> Signal, Telegram, WhatsApp: +421919416714
>>> 
>>> iMessage, mobile: +420775230885
>>> 
>>> Skype: casioa5302ca
>>> 
>>> frantisek.borsik@gmail.com <mailto:frantisek.borsik@gmail.com> <mailto:frantisek.borsik@gmail.com <mailto:frantisek.borsik@gmail.com>>_______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
>> 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>

[-- Attachment #1.2: Type: text/html, Size: 17588 bytes --]

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-06-03 21:57 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 [this message]
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
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=32AD770E-336E-4CF4-8B1B-8AE7353981CC@ieee.org \
    --to=eugene.chang@ieee.org \
    --cc=david@lang.hm \
    --cc=frantisek.borsik@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