Month: October 2023
Tesla’s Autopilot was not to blame for fatal 2019 Model 3 crash, jury finds
A California jury has found that Tesla was not at fault for a fatal 2019 crash that allegedly involved its Autopilot system, in the first US trial yet for a case claiming its software directly caused a death. The lawsuit alleged Tesla knowingly shipped out cars with a defective Autopilot system, leading to a crash that killed a Model 3 owner and severely injured two passengers, Reuters reports.
Per the lawsuit, 37-year-old Micah Lee was driving his Tesla Model 3 on a highway outside of Los Angeles at 65 miles per hour when it turned sharply off the road and slammed into a palm tree before catching fire. Lee died in the crash. The company was sued for $400 million plus punitive damages by Lee’s estate and the two surviving victims, including a boy who was 8 years old at the time and was disemboweled in the accident, according to an earlier report from Reuters.
Lawyers for the plaintiffs argued that Tesla sold Lee defective, “experimental” software when he bought a Model 3 in 2019 that was billed to have full self-driving capability. The FSD system was and still is in beta. In his opening statement, their attorney Jonathan Michaels also said that the “excessive steering command is a known issue at Tesla.”
Tesla’s defense argued that there was no such defect, and that an analysis cited by the plaintiffs’ lawyers identifying a steering issue was actually looking for problems that were theoretically possible. A fix to prevent it from ever happening was engineered as a result of that analysis, according to the company. Tesla blamed human error for the crash, pointing to tests that showed Lee had consumed alcohol before getting in the car, and argued that there’s no certainty Autopilot was in use at the time.
The jury ultimately found there was no defect, and Tesla was cleared on Tuesday. Tesla has faced lawsuits over its Autopilot system in the past, but this is the first involving a fatality. It’s scheduled to go on trial for several others in the coming months, and today’s ruling is likely to set the tone for those ahead.This article originally appeared on Engadget at https://www.engadget.com/teslas-autopilot-was-not-to-blame-for-fatal-2019-model-3-crash-jury-finds-210643301.html?src=rss
A California jury has found that Tesla was not at fault for a fatal 2019 crash that allegedly involved its Autopilot system, in the first US trial yet for a case claiming its software directly caused a death. The lawsuit alleged Tesla knowingly shipped out cars with a defective Autopilot system, leading to a crash that killed a Model 3 owner and severely injured two passengers, Reuters reports.
Per the lawsuit, 37-year-old Micah Lee was driving his Tesla Model 3 on a highway outside of Los Angeles at 65 miles per hour when it turned sharply off the road and slammed into a palm tree before catching fire. Lee died in the crash. The company was sued for $400 million plus punitive damages by Lee’s estate and the two surviving victims, including a boy who was 8 years old at the time and was disemboweled in the accident, according to an earlier report from Reuters.
Lawyers for the plaintiffs argued that Tesla sold Lee defective, “experimental” software when he bought a Model 3 in 2019 that was billed to have full self-driving capability. The FSD system was and still is in beta. In his opening statement, their attorney Jonathan Michaels also said that the “excessive steering command is a known issue at Tesla.”
Tesla’s defense argued that there was no such defect, and that an analysis cited by the plaintiffs’ lawyers identifying a steering issue was actually looking for problems that were theoretically possible. A fix to prevent it from ever happening was engineered as a result of that analysis, according to the company. Tesla blamed human error for the crash, pointing to tests that showed Lee had consumed alcohol before getting in the car, and argued that there’s no certainty Autopilot was in use at the time.
The jury ultimately found there was no defect, and Tesla was cleared on Tuesday. Tesla has faced lawsuits over its Autopilot system in the past, but this is the first involving a fatality. It’s scheduled to go on trial for several others in the coming months, and today’s ruling is likely to set the tone for those ahead.
This article originally appeared on Engadget at https://www.engadget.com/teslas-autopilot-was-not-to-blame-for-fatal-2019-model-3-crash-jury-finds-210643301.html?src=rss
Two artists suing AI image makers never registered works with Copyright Office
Artist suing Stability AI pushed to explain how Stable Diffusion actually works.
Artists suing Stability AI, Deviant Art, and Midjourney hit a roadblock this week in their quest to prove allegations that AI image generators illegally use copyrighted works to mimic unique artistic styles without compensation or consent.
On Monday, US district judge William H. Orrick dismissed many of the artists’ claims after finding that the proposed class-action complaint “is defective in numerous respects.” Perhaps most notably, two of the three named plaintiffs—independent artist Kelly McKernan and concept artist/professional illustrator Karla Ortiz—had apparently never registered any of their disputed works with the Copyright Office. Orrick dismissed their claims with prejudice, dropping them from the suit.
But while McKernan and Ortiz can no longer advance their claims, the lawsuit is far from over. Lead plaintiff, cartoonist, and illustrator Sarah Andersen will have the next 30 days to amend her complaint and keep the copyright dispute alive.
Porsche integrates google services into its cars
Porsche announced on Oct. 30 that it will integrate Google services into future vehicle models, representing a major step towards
The post Porsche integrates google services into its cars appeared first on ReadWrite.
Porsche announced on Oct. 30 that it will integrate Google services into future vehicle models, representing a major step towards a more connected driving experience.
Beginning in the middle of this decade, Porsche vehicles will offer Google Maps for navigation, Google Assistant for voice control features, and access to a wide variety of apps through the Google Play Store. While incorporating Google’s technology, Porsche says its signature user interface and Porsche Communication Management (PCM) system will remain intact.
PCM will serve as the gateway to Google services and continue receiving regular over-the-air updates, keeping the system current. According to Porsche Chairman Oliver Blume, “Our customers fulfill a dream with our vehicles. In addition to timeless design and exceptional performance, they also want a seamless digital experience.” He added that “this blended ecosystem results from integrating platforms and apps that customers know from their end devices.”
Blume said Porsche welcomes an open approach to develop innovations with partners like Google. The collaboration will allow Porsche to integrate relevant digital ecosystems directly into vehicles using standardized interfaces and platforms.
Porsche described the partnership with Google as a long-term commitment. For its part, Google is eager to bring its technology into Porsche vehicles. “We’re excited to partner with Porsche on their goal to bring innovative and helpful in-vehicle experiences to their customers,” said Hiroshi Lockheimer, Senior vice president of platforms and ecosystems at Google.
The integration with Google services represents the latest push by Porsche to enhance connected features and in-vehicle digital experiences. With smartphone-like capabilities built into the dashboard, Porsche aims to blend exceptional driving performance with industry-standard convenience and enjoyment.
Featured Image Credit: From the official finder.Porsche site; Thank you!
The post Porsche integrates google services into its cars appeared first on ReadWrite.
Best AT&T Deals Available: Save Up to $1,000 Right Now – CNET
Don’t overpay for your phone or your monthly service plan. Save some cash with these AT&T deals.
Don’t overpay for your phone or your monthly service plan. Save some cash with these AT&T deals.
Marcus by Goldman Sachs Savings Rates for October 2023 – CNET
Competitive rates and 24/7 customer service support make this savings account stand out from the competition.
Competitive rates and 24/7 customer service support make this savings account stand out from the competition.
Google Plans RISC-V Android Tools In 2024, Wants Developers To ‘Be Ready’
An anonymous reader quotes a report from Ars Technica: Android is slowly entering the RISC-V era. So far we’ve seen Google say it wants to give the up-and-coming CPU architecture “tier-1” support in Android, putting RISC-V on equal footing with Arm. Qualcomm has announced the first mass-market RISC-V Android chip, a still-untitled Snapdragon Wear chip for smartwatches. Now Google has announced a timeline for developer tools via the Google Open Source Blog. The last post is titled “Android and RISC-V: What you need to know to be ready.”
Getting the Android OS and app ecosystem to support a new architecture is going to take an incredible amount of work from Google and developers, and these tools are laying the foundation for that work. First up, Google already has the “Cuttlefish” virtual device emulator running, including a gif of it booting up. This isn’t the official “Android Emulator” — which is targeted at app developers doing app development — Cuttlefish is a hardware emulator for Android OS development. It’s the same idea as the Android Emulator but for the bottom half of the tech stack — the kernel, framework, and hardware bits. Cuttlefish lets Google and other Android OS contributors work on a RISC-V Android build without messing with an individual RISC-V device. Google says it’s working well enough now that you can download and emulate a RISC-V device today, though the company warns that nothing is optimized yet.
The next step is getting the Android Emulator (for app developers) up and running, and Google says: “By 2024, the plan is to have emulators available publicly, with a full feature set to test applications for various device form factors!” The nice thing about Android is that most app code is written with no architecture in mind — it’s all just Java/Kotlin. So once the Android RunTime starts spitting out RISC-V code, a lot of app code should Just Work. That means most of the porting work will need to go into things written in the NDK, the native developer kit, like libraries and games. The emulator will still be great for testing, though.
Read more of this story at Slashdot.
An anonymous reader quotes a report from Ars Technica: Android is slowly entering the RISC-V era. So far we’ve seen Google say it wants to give the up-and-coming CPU architecture “tier-1” support in Android, putting RISC-V on equal footing with Arm. Qualcomm has announced the first mass-market RISC-V Android chip, a still-untitled Snapdragon Wear chip for smartwatches. Now Google has announced a timeline for developer tools via the Google Open Source Blog. The last post is titled “Android and RISC-V: What you need to know to be ready.”
Getting the Android OS and app ecosystem to support a new architecture is going to take an incredible amount of work from Google and developers, and these tools are laying the foundation for that work. First up, Google already has the “Cuttlefish” virtual device emulator running, including a gif of it booting up. This isn’t the official “Android Emulator” — which is targeted at app developers doing app development — Cuttlefish is a hardware emulator for Android OS development. It’s the same idea as the Android Emulator but for the bottom half of the tech stack — the kernel, framework, and hardware bits. Cuttlefish lets Google and other Android OS contributors work on a RISC-V Android build without messing with an individual RISC-V device. Google says it’s working well enough now that you can download and emulate a RISC-V device today, though the company warns that nothing is optimized yet.
The next step is getting the Android Emulator (for app developers) up and running, and Google says: “By 2024, the plan is to have emulators available publicly, with a full feature set to test applications for various device form factors!” The nice thing about Android is that most app code is written with no architecture in mind — it’s all just Java/Kotlin. So once the Android RunTime starts spitting out RISC-V code, a lot of app code should Just Work. That means most of the porting work will need to go into things written in the NDK, the native developer kit, like libraries and games. The emulator will still be great for testing, though.
Read more of this story at Slashdot.
2nd person in history to receive pig heart transplant dies, hospital says
submitted by /u/Top-Organization-124 [link] [comments]
submitted by /u/Top-Organization-124
[link] [comments]