From: Eugene Y Chang <eugene.chang@ieee.org>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Eugene Y Chang <eugene.chang@ieee.org>,
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 10:47:32 -1000 [thread overview]
Message-ID: <BA5D7792-9292-4065-9AF2-8D883B58304B@ieee.org> (raw)
In-Reply-To: <CAJUtOOhmve_-F=Lw8ijJiL1mYAJN9F_qY43aBa7uK29VqisouA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1526 bytes --]
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>
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
>
>
> 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>_______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #1.2: Type: text/html, Size: 10913 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-03 20:47 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 [this message]
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
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=BA5D7792-9292-4065-9AF2-8D883B58304B@ieee.org \
--to=eugene.chang@ieee.org \
--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