From: "David Fernández" <davidfdzp@gmail.com>
To: 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: Tue, 4 Jun 2024 12:42:37 +0200 [thread overview]
Message-ID: <CAC=tZ0qr2ei7k+A2Jcw=ZPB7m_Dgvppb2_t=6kw4G4ourC2xiw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Both AST and Starlink are reporting speeds of around 10 Mbit/s. Those are
not like the service Globalstar is providing to Apple phones for just
emergency texts.
https://uk.pcmag.com/networking/151288/spacexs-cellular-starlink-hits-17mbps-download-speed-to-android-phone
From: David Lang <david@lang.hm>
To: Eugene Y Chang <eugene.chang@ieee.org>
Cc: 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
Message-ID: <o29q52qp-p7p8-711q-q0ns-57or8866854n@ynat.uz>
Content-Type: text/plain; charset="iso8859-7"; Format="flowed"
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.
[-- Attachment #2: Type: text/html, Size: 1872 bytes --]
next reply other threads:[~2024-06-04 10:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 10:42 David Fernández [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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='CAC=tZ0qr2ei7k+A2Jcw=ZPB7m_Dgvppb2_t=6kw4G4ourC2xiw@mail.gmail.com' \
--to=davidfdzp@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