News
SpaceX Starship fires up Raptor Vacuum engine twice in one hour
After weeks of exceptionally cautious buildup, SpaceX’s first orbital-class Starship prototype has repeatedly broken new ground tests in the first few hours of its first static fire test window.
SpaceX first installed Starship S20 on one of two suborbital launch and test stands more than two months ago. After almost six weeks of largely invisible work, longer than any other new Starship prototype has spent inactive at Starbase launch facilities, Ship 20 came to life for the first time during a ‘pneumatic proof’ test completed on September 27th. Two days later, put the Starship through a complex cryogenic proof test, loading supercool liquid nitrogen instead of ambient-temperature gas and simulating the thrust of six Raptor engines with hydraulic rams.
According to CEO Elon Musk, Ship 20 passed its first ‘cryoproof’ without issue, opening the door for static fire testing with real methane and oxygen (LCH4/LOx) propellant and Raptor engines. However, for unknown reasons, it would ultimately take SpaceX more than three weeks of additional work to prepare Starship S20 for its first engine-involved test.
On October 19th, near the end of a seven-hour test window, Starship S20 sort of fired up for the first time, completing what is known as a preburner test. Effectively the first half of static fire test without full ignition, it was nevertheless the first time a Raptor Vacuum engine was operated on a Starship prototype. Originally, based on road closures scheduled with Cameron County, Texas, that preburner test and associated static fire testing was initially scheduled to begin as early as Friday, September 31st.
SpaceX continued to file for and cancel closures throughout the next week, culminating in a few local residents receiving a routine safety notice about a possible test on October 13th. That attempt was canceled soon after and SpaceX ultimately distributed alerts for tests on October 14th and October 18th. Ship 20’s first preburner test was completed on the 19th, followed by another soon-to-be-rescinded notice on the 20th.
Finally, after perhaps the windiest road yet for a Starship from cryoproof to static fire, Starship S20 sailed through a static fire test flow on October 21st and ultimately fired up for the first time ever at 7:16 pm CDT (00:16 UTC). In perfect opposition to weeks of unprecedentedly slow testing, Starship S20 not only completed its first true static fire early in the test window, but it completed the first on-vehicle static fire of a Raptor Vacuum engine and then, just over an hour later, performed a second static fire – this time simultaneously igniting both a Raptor Vacuum and Raptor Center (sea-level-optimized) engine. Aside from also marking the first time that two Raptor variants have been simultaneously fired on the same vehicle, Starship S20’s two-test surprise was technically the fastest back-to-back static fire SpaceX has ever completed, beating Starship SN9 by about 15 minutes.
Back in January 2021, SN9 completed an unprecedented three back-to-back-to-back Raptor static fires in less than 100 minutes as part of what Musk described as “[a day] about practicing Starship engine starts.” SN9 ultimately completed two of those tests in 75 minutes, setting a niche but still impressive turnaround record. Starship S20, however, managed two static fires in 62 minutes on October 21st.
With any luck, Ship 20’s unexpected first-test milestones will mark the start of a more energetic period for the orbital-class prototype, potentially building up to the first Starship static fire with more than three Raptors and the first test with all six engines installed. Super Heavy Booster 4 is also well overdue for its own proof and static fire test campaign, virtually all of which will be new territory for SpaceX.
News
Anti-Tesla union leader ditches X, urges use of Threads instead
Tesla Sweden and IF Metall have been engaged in a bitter dispute for over two years now.
Marie Nilsson, chair of Sweden’s IF Metall union and a prominent critic of Tesla, has left X and is urging audiences to follow the union on Meta’s Threads instead.
Tesla Sweden and IF Metall have been engaged in a bitter dispute for over two years now.
Anti-Tesla union leader exits X
In a comment to Dagens Arbete (DA), Nilsson noted that her exit from X is not formally tied to IF Metall’s long-running labor dispute with Tesla Sweden. Still, she stated that her departure is affected by changes to the platform under Elon Musk’s leadership.
“We have stayed because many journalists pick up news there. But as more and more people have left X, we have felt that the standard has now been reached on that platform,” she said.
Jesper Pettersson, press officer at IF Metall, highlighted that the union’s departure from X is only indirectly linked to Tesla Sweden and Elon Musk. “Indirectly it does, since there is a lot of evidence that his ownership has caused the change in the platform to be so significant.
“We have nevertheless assessed that the platform had value for reaching journalists, politicians and other opinion leaders. But it is a microscopic proportion of the public and our members who are there, and now that value has decreased,” Petterson added.
IF Metall sees Threads as an X alternative
After leaving X, IF Metall has begun using Threads, Meta’s alternative to the social media platform. The union described the move as experimental, noting that it is still evaluating how effective the platform will be for outreach and visibility.
Pettersson acknowledged that Meta also does not operate under Sweden’s collective bargaining model, but said the union sees little alternative if it wants to remain visible online.
“In a perfect world, all large international companies would be supporters of the Swedish model when they come here. But unfortunately, the reality is not like that. If we are to be visible at all in this social media world, we have to play by the rules of the game. The alternative would be to become completely invisible, and that would not benefit our members,” he said.
Despite many recent rumors and various reports, Elon Musk confirmed today that SpaceX is not developing a phone based on Starlink, not once, but twice.
Today’s report from Reuters cited people familiar with the matter and stated internal discussions have seen SpaceX executives mulling the idea of building a mobile device that would connect directly to the Starlink satellite constellation.
Musk did state in late January that SpaceX developing a phone was “not out of the question at some point.” However, He also said it would have to be a major difference from current phones, and would be optimized “purely for running max performance/watt neural nets.”
Not out of the question at some point. It would be a very different device than current phones. Optimized purely for running max performance/watt neural nets.
— Elon Musk (@elonmusk) January 30, 2026
While Musk said it was not out of the question “at some point,” that does not mean it is currently a project SpaceX is working on. The CEO reaffirmed this point twice on X this afternoon.
Musk said, “Reuters lies relentlessly,” in one post. In the next, he explicitly stated, “We are not developing a phone.”
Reuters lies relentlessly
— Elon Musk (@elonmusk) February 5, 2026
We are not developing a phone
— Elon Musk (@elonmusk) February 5, 2026
Musk has basically always maintained that SpaceX has too many things going on, denying that a phone would be in the realm of upcoming projects. There are too many things in the works for Musk’s space exploration company, most notably the recent merger with xAI.
SpaceX officially acquires xAI, merging rockets with AI expertise
A Starlink phone would be an excellent idea, especially considering that SpaceX operates 9,500 satellites, serving over 9 million users worldwide. 650 of those satellites are dedicated to the company’s direct-to-device initiative, which provides cellular coverage on a global scale.
Nevertheless, there is the potential that the Starlink phone eventually become a project SpaceX works on. However, it is not currently in the scope of what the company needs to develop, so things are more focused on that as of right now.
Tesla has added a notable improvement to its Dashcam feature after complaints from owners have pushed the company to make a drastic change.
Perhaps one of the biggest frustrations that Tesla owners have communicated regarding the Dashcam feature is the lack of ability to retain any more than 60 minutes of driving footage before it is overwritten.
It does not matter what size USB jump drive is plugged into the vehicle. 60 minutes is all it will hold until new footage takes over the old. This can cause some issues, especially if you were saving an impressive clip of Full Self-Driving or an incident on the road, which could be lost if new footage was recorded.
This has now been changed, as Tesla has shown in the Release Notes for an upcoming Software Update in China. It will likely expand to the U.S. market in the coming weeks, and was first noticed by NotaTeslaApp.
The release notes state:
“Dashcam Dynamic Recording Duration – The dashcam dynamically adjusts the recording duration based on the available storage capacity of the connected USB drive. For example, with a 128 GB USB drive, the maximum recording duration is approximately 3 hours; with a 1 TB or larger USB drive, it can reach up to 24 hours. This ensures that as much video as possible is retained for review before it gets overwritten.”
Tesla Adds Dynamic Recording
Instead of having a 60-minute cap, the new system will now go off the memory in the USB drive. This means with:
- 128 GB Jump Drive – Up to Three Hours of Rolling Footage
- 1TB Jump Drive – Up to 24 Hours of Rolling Footage
This is dependent on the amount of storage available on the jump drive, meaning that if there are other things saved on it, it will take away from the amount of footage that can be retained.
While the feature is just now making its way to employees in China, it will likely be at least several weeks before it makes its way to the U.S., but owners should definitely expect it in the coming months.
It will be a welcome feature, especially as there will now be more customization to the number of clips and their duration that can be stored.
Anti-Tesla union leader ditches X, urges use of Threads instead
Elon Musk confirms SpaceX is not developing a phone
