The Nintendo Switch was a great place to play Persona games, and it looks like the outgoing console has passed on the torch to its successor, with last year’s Persona 3 Reload kicking things off when it comes to Switch 2 on October 23.
Reload is a full remake of 2006’s Persona 3 (later ported to the PSP as Persona 3 Portable), which Engadget’s Mat Smith called “a gorgeous version of itself” in his review. It’s both one of the most confusing and influential entries in the long-running series, and the remake’s updated visuals means it sits proudly alongside Persona 5 Royal as one of the most stylish RPGs you’ll ever play. It’s also one of the more repetitive entries, but that didn’t put off the many Persona sickos out there from experiencing the remixed game all over again.
The Switch 2 version of Persona 3 Reload means the game will be playable on practically every modern platform, but the big question will be how it performs on the more powerful hardware. The Switch port of Persona 5 Royal wasn’t quite as easy on the eyes as the PlayStation, Xbox and PC versions, but the portability made it the ideal platform for the game all the same.
Persona 3 Reload comes to Switch 2 on October 23. At the time of writing there’s no news on whether a physical version will be available at launch.
The Galaxy Z Fold 7, Flip 7, and Flip 7 FE were just announced, set for pre-order, and launched within the last month. Just a few days after the official, widespread launch, Samsung is pushing a software update to these devices, including the Z Fold 7.
The Galaxy Z Fold 7 and Flip 7 are Samsung’s best foldable, and they’ve done a lot to improve on a design that showcased what these phones are capable of, while bringing some key design changes that make themmore viable.
Just days after the release, Samsung is rolling out a couple of firmware updates for these devices. That includes both the standard Galaxy Z Fold 7 and Flip 7, as well as the Flip 7 FE. The updates fall under versions F966BXXS2AYGG, F766BXXS2AYGD, and F761BXXS2AYG5 (via SamMobile).
It appears the Z Fold 7 and Flip 7’s firmware updates are relatively small, and they offer little in the way of information or details. Most notably, improved security is mentioned. There’s little beyond that.
Advertisement – scroll for more content
These types of updates are common right after a launch. Once the device gets into the hands of thousands, Samsung can easily identify larger security threats and start producing solutions on a wider scale. The update doesn’t offer anything in the way of new features.
It was already noted that larger updates with UX and UI features would come out during Galaxy S series launches, per previous information from the company. That’s even with foldable now being the debut device for the upcoming One UI versions.
FTC: We use income earning auto affiliate links.More.
Incorrect altitude readings on the Army helicopter that collided with a passenger plane over Washington, D.C., in January contributed to the aircraft getting too close, but air traffic controllers warned about the hazards helicopter traffic presented years before the crash.
Those warnings came even before the 85 near misses near the airport in the three years before the crash. But despite the concerns that were raised about the route the Black Hawk helicopter followed that night, the Federal Aviation Administration didn’t make changes to it or warn pilots about it.
The details came out of the first day of National Transportation Safety Board hearings in Washington, where investigators highlighted several of the factors that contributed to the crash between the American Airlines plane from Wichita, Kansas, and the Black Hawk helicopter near Ronald Reagan National Airport that was the deadliest aviation disaster in America since November 2001.
“It’s so bureaucratic,” NTSB Chairwoman Jennifer Homendy said. “I mean we heard it in the testimony today: ‘Oh you could bring it up in another symposium or another group. or you could take this option or we said no.’ But then I asked did you provide an alternative? That’s why people are so critical of the federal government because you can’t ensure safety.”
Christina Stovall, whose son, Mikey Stovall, died on American Airlines flight 5342 in a collision with a U.S. military helicopter, weeps as she leaves the room during the NTSB fact-finding hearing on the DCA midair collision accident, at the National Transportation and Safety Board boardroom, Wednesday, July 30, 2025, in Washington. (AP Photo/Rod Lamkey, Jr.)AP
Representatives of the Army and Federal Aviation Administration tried to deflect responsibility throughout the hearing. The Army acknowledged that their Black Hawks altimeters might be more than 100 feet (30 meters) off, but they seemed to say that was acceptable because their pilots’ goal is to maintain altitude within 100 feet of a limit.
Army officials instead raised concerns about the lack of separation between landing aircraft and helicopters flying on approved FAA routes near the airport. But later in the day, FAA and Army officials both implied that those routes were never supposed to ensure separation. Instead they suggested that it was up to the air traffic controller to keep helicopters from flying on that route anytime planes were taking off or landing from that runway.
Aviation lawyer Bob Clifford, who is representing several of the victims’ families said there was a lot of “finger pointing” and “no acceptance of responsibility and accountability” during the hearing.
The board’s final report won’t be released until sometime next year, but it became clear Wednesday how small a margin of error there was for helicopters flying the route the Black Hawk took the night of the crash.
The January nighttime incident was the first in a string of crashes and near misses this year that have alarmed officials and the traveling public, despite statistics that still show flying remains the safest form of transportation.
Animation, altimeter discrepancy
A video animation showed where the helicopter and airliner were leading up to the collision. It showed how the helicopter flew above the 200 feet (61 meters) altitude limit on the helicopter route along the Potomac River before colliding with the plane.
Investigators said Wednesday the flight data recorder showed the helicopter was actually 80 feet to 100 feet (24 to 30 meters) higher than the barometric altimeter the pilots relied upon showed they were flying. So the NTSB conducted tests on three other helicopters from the same unit in a flight over the same area and found similar discrepancies in their altimeters.
Dan Cooper with Sikorsky helicopters said that when the older Black Hawk helicopter involved in the crash was designed in the 1970s, it used a style of altimeter that was common at the time. Newer helicopters have air data computers that help provide more accurate altitude readings.
Army Chief Warrant Officer Kylene Lewis told the board that she wouldn’t find an 80 to 100 foot discrepancy between the different altimeters on a helicopter alarming because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Below 500 feet (152 meters), Lewis said she would be checking both instruments and cross referencing them, although that’s not something every Army pilot is trained to do.
Army officials said the greater concern is that the FAA approved routes around Reagan airport that included such separation distances as small as 75 feet between helicopters and planes when planes are landing on a certain runway at Reagan.
“The fact that we have less than 500 foot separation is a concern for me,” said Scott Rosengren, chief engineer in the office that manages the Army’s utility helicopters.
But Rosengren said that “if he was king for a day” he would immediately retire all the older Black Hawk models like the one involved in this crash and replace them with newer versions of the helicopters.
Questions over the route
Army officials and the head of a local medevac helicopter company that flies around Washington told the board they believed air traffic controllers would never let them fly the helicopter route involved in the crash anytime a plane was approaching the runway.
Chief Warrant Officer David Van Vetchen said after the crash that he talked to many of his fellow pilots and everyone had the same assumption that controllers would never allow them to fly across the path of the runway the American plane was approaching before the crash. But Homendy said other pilots in the unit told investigators they were allowed to fly underneath landing planes.
Citing the numbers for runways, Van Vetchen said that “100% of the time when I was on route four and 33/15 was active” he would be instructed to hold until after the plane landed or took off from that runway.
‘Stepped on transmission’
During the two minutes before the crash, one air traffic controller was directing airport traffic and helicopters in the area, a task that involved speaking to or receiving communications from several different aircraft on two different frequencies, according to the NTSB’s History of Flight Performance Study released Wednesday.
The air traffic controller had spoken to or received communications from the Black Hawk helicopter, an airplane that was taking off, an Air Force helicopter, an airplane on the ground, a medical helicopter and an inbound flight that was not the American Airlines plane that would crash.
“All aircraft could hear the controller, but helicopters could only hear other helicopters on their frequency and airplanes only other airplanes,” the report stated. “This resulted in a number of stepped on transmissions as helicopters and airplanes were not aware when the other was communicating.”
Stepped on transmissions are those that are unheard or blocked because of other transmissions. The NTSB report provides a list of 29 separate communications between the airport tower and other aircraft during approximately the 1 minute and 57 seconds before the collision.
Previously disclosed air traffic control audio had the helicopter pilot telling the controller twice that they saw the airplane and would avoid it. Officials on Wednesday also raised the use of night vision goggles, which limit the wearer’s field of view, on the helicopter as a factor.
Investigations have already shown the FAA failed to recognize a troubling history of 85 near misses around Ronald Reagan National Airport in the years before the collision, and that the Army’s helicopters routinely flew around the nation’s capital with a key piece of locating equipment, known as ADS-B Out, turned off.
On Wednesday, it came out that even if they had been turned on, the ADS-B Out systems on most of the helicopters in the same unit as the one that crashed wouldn’t work because they had been installed incorrectly. When the NTSB uncovered that problem, the Army sent out an alert about it and worked to quickly reprogram the units so they would work.
Homendy highlighted that an FAA working group raised concerns about all the helicopter traffic around Reagan airport and the risk of a collision in 2022, but the FAA refused to add a warning to helicopter charts urging pilots to use caution when this runway was in use.
Homendy said “every sign was there that there was a safety risk and the tower was telling you that.” But after the accident the FAA transferred managers out of the tower instead of acknowledging that they had been warned.
“What you did is you transferred people out instead of taking ownership over the fact that everybody in FAA in the tower was saying there was a problem,” Homendy said. “But you guys are pointing out, ‘Welp, our bureaucratic process. Somebody should have brought it up at some other symposium.’ Are you kidding me? 67 people are dead. How do you explain that?”
Proposed changes
U.S. Sen. Ted Cruz, a Republican, introduced legislation Tuesday to require all aircraft operators to use both forms of ADS-B, or Automatic Dependent Surveillance Broadcast, the technology to broadcast aircraft location data to other planes and air traffic controllers. Most aircraft today are equipped with ADS-B Out equipment but the airlines would have to add the more comprehensive ADS-B In technology to their planes.
The legislation would revoke an exemption on ADS-B transmission requests for Department of Defense aircrafts.
Homendy said her agency has been recommending that move for decades after several other crashes.
Transportation Secretary Sean Duffy said that while he’d like to discuss “a few tweaks,” the legislation is “the right approach.” He also suggested that the previous administration “was asleep at the wheel” amid dozens of near-misses in the airspace around Washington’s airspace.
If you purchase a product or register for an account through a link on our site, we may receive compensation. By using this site, you consent to our User Agreement and agree that your clicks, interactions, and personal information may be collected, recorded, and/or stored by us and social media and other third-party partners in accordance with our Privacy Policy.
GitHub Copilot, an AI coding tool offered by Microsoft-owned GitHub, has now reached more than 20 million users, Microsoft CEO Satya Nadella said on the company’s earnings call Wednesday. A GitHub spokesperson confirmed to TechCrunch that this number represents “all-time users.”
That means five million people have tried out GitHub Copilot for the first time in the last three months; the company reported in April the tool had reached 15 million users. Microsoft and GitHub don’t report how many of these 20 million people have continued to use the AI coding tool on a monthly or daily basis — though those metrics are likely far lower.
Microsoft also reported GitHub Copilot, which is among the most popular AI coding tools offered today, is used by 90% of the Fortune 100. The product’s growth among enterprise customers has also grown about 75% compared to last quarter, according to the company.
AI coding tools are rising in popularity, and they seem to be one of the few AI products generating notable revenue. In 2024, Nadella said GitHub Copilot was a larger business than all of GitHub was when Microsoft acquired it in 2018. In the year since, it seems GitHub Copilot’s growth rate has continued in a positive direction.
The world’s most popular AI coding tools still have tiny user bases compared to AI chatbots like ChatGPT and Gemini, which attract hundreds of millions of users every month. Of course, software engineering is more niche than the general informational queries offered by AI chatbots.
That said, software engineers and their employers seem to be willing to pay a premium for AI coding tools. And with Microsoft’s long list of enterprise customers and GitHub’s ecosystem of developers, GitHub Copilot is well positioned to dominate the market for enterprise AI coding tools.
Cursor, another popular AI coding tool, wants to challenge GitHub Copilot in the enterprise, and it’s been scooping up talent from fledgling AI startups to do so. Cursor reportedly had more than a million people using its product every day in March, according to Bloomberg. At that time, the company generated about $200 million in annualized recurring revenue. Today, Cursor’s ARR is more than $500 million, suggesting there are now a lot more people using its products everyday.
Techcrunch event
San Francisco | October 27-29, 2025
While GitHub Copilot and Cursor initially sought to tackle different parts of the developer experience, they’re steadily converging into similar products.
Both companies have recently introduced AI agents to review code and catch bugs introduced by humans. Github and Cursor are also both trying to create AI agents that automate programmer workflows, allowing developers to offload tasks altogether. Nadella said during Wednesday’s earnings call that GitHub was seeing great momentum with their AI coding agents.
Beyond Cursor, GitHub has an array of well-capitalized competitors that would like to sell AI coding tools to the enterprise.
iPhone devotees, listen up: Tons of new updates are coming to Apple’s operating system this fall that you’ll be excited to try out. But instead of being named iOS 19, it’ll be called iOS 26. The biggest change? The new Liquid Glass design (think Windows Vista, but arguably more thoughtful), which looks to be Apple’s largest visual update in years. We spent two weeks test-driving it — you can check out our detailed hands-on iOS 26 preview, or you can try it out yourself by downloading and installing the public beta, available now. Before you dive in, we’ll help you answer this question: Will my iPhone be able to run iOS 26?
Last year, Apple didn’t nix any iPhones from its eligibility list, but that’s not the case for 2025 — a few models are getting cut this time. All iPhone 8 models and the iPhone X were the last to get the boot in 2023, and this year the 2018 models are getting left behind. If you have an ineligible device, you won’t be able to download iOS 26 when it becomes available this fall.
These three iPhones won’t be compatible with iOS 26
Unlike last year, several iPhone models won’t be eligible to download the newest iOS when it makes its debut this fall. This trio of models first released in 2018 won’t be coming to the iOS 26 party:
iPhone XR
iPhone XS
iPhone XS Max
iPhones compatible with iOS 26
While we don’t yet know the new iPhones Apple will be dropping this fall — though there are iPhone 17 rumors — we do know, per Apple’s site, that the phones listed below will be compatible with iOS 26. Basically, if you have an iPhone that was announced in 2019 or later, you’re in the clear:
What if I don’t want to buy a new iPhone?
If you want to continue using your older iPhone that isn’t supported by iOS 26, that’s fine. However, you’ll miss out on security updates which could potentially put your phone at risk for malware and other threats. Additionally, some apps may stop working if they require a certain version of iOS or later. And of course, you won’t be able to access the latest features iOS 26 offers.
When will iOS 26 become available?
Apple usually rolls out its latest iOS in mid-September, just a few days before the new iPhones hit store shelves. Last year, it released iOS 18 on Monday, Sept. 16. Expect a confirmation of the release date at the iPhone 17 event, expected in early September.
iOS 26 features we’re excited about
Liquid Glass design: Your home screen is getting revamped with new app icons, including dark mode and all-clear options. You’ll also notice buttons with a new floating design. Liquid Glass was designed to make all of Apple’s OSes more cohesive.
Phone app redesign: You’ll finally be able to scroll through contacts, recent calls and voicemail messages all on one screen. It also comes with a new feature called Hold Assist that’ll notify you when an agent comes to the phone so you can avoid the elevator music.
Live Translate: iOS 26 is bringing the ability to have a conversation via phone call or text message with someone who speaks another language. Live Translate will translate your conversation in real time.
Polls feature: Coming to group messages in the Messages app, chat members will be able to create polls. This can help prevent the unwanted 30+ messages when it comes to deciding which restaurant you’re meeting at this weekend.
Expanded locks experience: Manage passcodes, schedule access, and enjoy one-tap entry for your smart locks. You can also set automatic locking, use vacation mode, and get notifications on door status.
Customizable Favorites: Tailor your favorite devices, actions, and automations for each Google Home app surface, including Wear OS.
Bug Fixes
Improved setup flows: Fixed an issue where users were unexpectedly redirected during the setup process for certain devices.
Device status reliability: Fixed an issue where device status was not updating correctly, ensuring you always see the accurate status of your devices.
Reduced crashes: Implemented fixes for various crashes, including those related to audio and device linking, enhancing the overall stability and reliability of the app.
Google Home 3.35 from June 23, 2025 is a big camera update. This is the latest stable release on devices we checked today. We are not seeing the Cast controller refresh widely rolled out in preview.
Features
Camera event notification media: All camera event notifications now include a static thumbnail along with a large animated preview of the event to help you understand what the notification is about.
On iOS, press and hold the notification to see the animation.
On Android, click the expand arrow on the notification to view the animation.
Camera controller gestures: Simple swiping gesture support to allow you to effortlessly control common navigation features.
Switch between Timeline and Events List with a left or right swipe
Expand and collapse the player window with a swipe down on the middle control bar
Dismiss the camera with a swipe downwards on the camera player
Cast controller refresh (Android – Public Preview): Improves UI reliability and performance and aligns with the Google Home app’s latest design standards.
Bug Fixes
Improved app stability: Fixed a crash related to generic specialization in Swift, improving the overall stability of the app.
Device linking issue: Fixed an issue where users were unable to link devices through “Works with Google Home”, ensuring a smoother setup process.
Version 3.36 is dated July 8, 2025 with just bug fixes. We have not seen this update yet. In fact, Google is already beginning to roll out 3.37 (we received it today).
Bug Fixes
Reduced “no video available” errors: Camera users will see fewer cases where a recent video is not yet available for streaming.
Camera stream reliability: Fixed an issue where turning a camera off and on during a live stream would result in a “Camera Unavailable” error, ensuring the stream recovers properly.
Setup interruptions: Fixed an issue that caused interruptions during the setup flow for new devices after QR code scans or setup code entries.
Outdoor temperature display: Fixed an issue where outdoor temperature was incorrectly displayed on Android devices.
Reduced app crashes: Fixed a significant crash related to suspend/resume partial functions, improving the app’s overall stability and reliability.
FTC: We use income earning auto affiliate links.More.
A 16-year-old boy was seriously injured Wednesday afternoon when he was struck by a car while bicycling in Lynn, according to police.
Officers responded to the intersection of Cottage and Woodman Streets shortly after 4:25 p.m. for a report that a cyclist had been hit by a car, Lynn police said in an email. First responders found the teen boy with serious injuries and took him to a hospital for treatment.
The driver involved in the crash stayed at the scene, police said. The investigation into the crash is ongoing.
No further information has been released.
If you purchase a product or register for an account through a link on our site, we may receive compensation. By using this site, you consent to our User Agreement and agree that your clicks, interactions, and personal information may be collected, recorded, and/or stored by us and social media and other third-party partners in accordance with our Privacy Policy.
The Trump administration said on Wednesday that it secured commitments from Google, OpenAI, Amazon, Anthropic, and Apple to start building a digital health ecosystem.
The efforts will focus on two areas: creating a framework for patients and providers to easily share information, and creating more personal tools so patients can access resources needed to stay informed about their health. Such tools include apps to manage diabetes and obesity, using artificial intelligence as assistants to perform tasks like checking symptoms and scheduling appointments, and finding ways to reduce the amount of paperwork associated with medical appointments by digitizing some tasks.
Democrats and Republicans have tried before to make data sharing in the U.S. health system a more seamless experience, Bloomberg reports, though the technology was never quite up to par. Over 60 companies have said they will work on the new health effort and results are expected in early 2026.
Skechers just released a helicopter parent’s dream shoe. is a new line of children’s shoes that encourages parents to hide an under the heel. If wasn’t enough and didn’t quite cut it, now you can hide an AirTag on their person.
Remember running around the neighborhood with your friends and being told to be home for dinner? Or perhaps biking to and from school? You were figuring out how to navigate the world on your own and parents were learning how to let you do so just like they did when they were younger.
Find My Skechers shoes are offered in sizes for children as young as one and as old as ten. This begs the question: does Skechers think we are leaving our toddlers unsupervised to the degree that we need to hide trackers in their shoes? On the other end of the spectrum, do we think a 10‑year‑old won’t figure out that their parents bought them the AirTag‑tracking shoe? After all, about and might even get that an AirTag is following them. Add to this that there is suggesting that using digital technology to track your children’s whereabouts can lead to more rebellious behavior.
This feature may help locate shoes left at school, camp or a sleepover. Some online commentators were also quick to point out that this shoe could help keep track of elderly loved ones who might wander.
A for the new line of shoes describes the “clever secure hidden compartment” where parents can hide the AirTag and notes that your child won’t be able to feel it in their shoes. The shoes are machine‑washable and available for sale now. An Apple AirTag is not included.
If you buy something through a link in this article, we may earn commission.
Google will reportedly not raise the price — which was a concern amidst tariffs — of the Pixel 10, 10 Pro, 10 Pro XL, and 10 Pro Fold in the US.
According to Android Headlines today, the Pixel 10 will be priced like its predecessor and start at $799 for 128 GB. Going to 256 GB is $899, with Google once again offering six months of AI Pro and Fitbit Premium, as well as three months of YouTube Premium.
Meanwhile, the 128 GB Pixel 10 Pro starts at $999, while it’s $1,099 for 256 GB. The 512 GB model is $1,219 and 1 TB is $1,449.
The Pixel 10 Pro XL starts at 256 GB — compared to 128 GB last year at $1,099 — and is $1,199. The 512 GB Pro XL is $1,319 and 1 TB is $1,549.
Advertisement – scroll for more content
128 GB
256 GB
512 GB
1 TB
Pixel 10
$799
$899
Pixel 10 Pro
$999
$1,099
$1,219
$1,449
Pixel 10 Pro XL
$1,199
$1,319
$1,549
Pixel 10 Pro Fold
$1,799
$1,919
$2,149
Finally, the Pixel 10 Pro Fold is also unchanged at $1,799 for 256 GB, despite a previous report from the same publication in April that said this year’s foldable is “expected to drop to around $1,600.” The 512 GB model is $1,919 and a new size this year is the $2,149 1 TB.
The Pro phones also get one year of Google AI Pro, six months of Fitbit Premium, and three months of YouTube Premium.
Canada
128 GB
256 GB
512 GB
1 TB
Pixel 10
$1,099
$1,229
Pixel 10 Pro
$1,349
$1,479
$1,649
$1,949
Pixel 10 Pro XL
$1,629
$1,799
$2,099
Pixel 10 Pro Fold
$2,399
$2,569
$2,869
More on Pixel 10:
FTC: We use income earning auto affiliate links.More.
