Mike Murphy reports via Quartz of Samsung's new top-of-the-line televisions announced at an event in New York today: Samsung's new QLED line of 4K TVs features a technology the company is calling "Ambient Mode." Before you mount the TV, you'll snap a picture of the wall it's going to hang on -- it doesn't matter if it's brick, wood, patterned wallpaper, or just a white wall -- and then after it's up, you can set that picture as the TV's background. The result is something that looks like a floating black rectangle mounted on a wall. Samsung even includes a digital version of the shadow this black rectangle would cast on the wall, as if there really wasn't a large LED panel sitting in the middle of the thin metal strips. There are five QLED models, with minor tweaks between them, ranging in size from 49 inches, up to an absolutely massive 88 inches. The televisions have a built-in timer so that the ambient setting will turn off after a while, in order to spare your electricity bill. Viewing the televisions before Samsung's event, the ambient really did appear to blend them into the walls at first blush. One, against a fake brick wall, was indistinguishable from what was behind it until you really got close up to the screen. The distinction on another, attempting to mimic a painted off-white wall, was a little more obvious. But that's not really the point -- the mode is just intended to give the illusion of invisibility between watching TV, and when you want to show off your new television to a visitor. Pricing isn't available but you can expect them to range from a few thousands dollars all the way up to $20,000 for the largest, sharpest models. Samsung also announced that it's partnering with The Weather Channel, The New York Times, and others to overlay content on the ambient TVs. They will also be able to control any smart device that can control to Samsung's SmartThings system, like Amazon Echoes, Ring doorbells, and Philips Hue Lights. Bixby is baked into the remote to help you search for content and cater to commands.

Jason Koebler shares a report from Motherboard: The right to repair battle has come to Silicon Valley's home state: Wednesday, a state assembly member announced that California would become the 18th state in the country to consider legislation that would make it easier to repair your electronics. "The Right to Repair Act will provide consumers with the freedom to have their electronic products and appliances fixed by a repair shop or service provider of their choice, a practice that was taken for granted a generation ago but is now becoming increasingly rare in a world of planned obsolescence," Susan Talamantes Engman, a Democrat from Stockton who introduced the bill, said in a statement. The announcement had been rumored for about a week but became official Wednesday. The bill would require electronics manufacturers to make repair guides and repair parts available to the public and independent repair professionals and would also would make diagnostic software and tools that are available to authorized and first-party repair technicians available to independent companies.

Polygon reports that Oculus Rift virtual reality headsets around the world are experiencing an outage. The outage appears to be a result of an expired security certificate. "That certificate has expired," said the Oculus support team on its forums, "and we're looking at a few different ways to resolve the issue. We'll update you with the latest info as available. We recommend you wait until we provide an official fix. Thanks for your patience." Polygon reports: One place where users experiencing the issue are gathering is on the Oculus forums. Last night user apexmaster booted up his computer, tried to open the Oculus app and was greeted by an error indicating that the software could not reach the "Oculus Runtime Service." That same error is cropping up on computers all around the world, including several devices here at Polygon. Once it has appeared, there's no way to restart the Oculus app, which renders the Rift headset unusable.

According to incident reports collected by the California department of motor vehicles, some Californians are purposely colliding with self-driving cars. The Guardian reports: On January 10, a pedestrian in San Francisco's Mission District ran across the street to confront a GM Cruise autonomous vehicle that was waiting for people to cross the road, according to an incident report filed by the car company. The pedestrian was "shouting," the report states, and "struck the left side of the Cruise AV's rear bumper and hatch with his entire body." No injuries occurred, but the car's left tail light was damaged. In a separate incident just a few blocks away on January 28, a taxi driver in San Francisco got out of his car, approached a GM Cruise autonomous vehicle and "slapped the front passenger window, causing a scratch." The police were not called in either case.

Google has launched the first developer preview of Android P, the company's new mobile operating system that brings new features and improvements over Android Oreo. Unfortunately, developers will only have a small set of blessed hardware to choose from with Android P: the Pixel, Pixel XL, Pixel 2, and Pixel 2 XL. Google's Nexus smartphones and Pixel C tablet will not get Android P when it's fully released. The Verge reports: Eventually, Android P will ship on new phones from other manufacturers, along with the handful of handsets that third-parties bother to update, but there are a couple Android mainstays that won't get to enjoy this marvelous future: Google's Nexus 5X and Nexus 6P phones, and the oft-forgotten Pixel C tablet. As Ars Technica confirmed with Google, those devices won't be getting Android P when it's released fully. Also, as Android Police notes, there's no Developer Preview image for the Nexus Player, which came out in 2014, so it might be done getting updates as well. It's 2018, and we're beyond the two years of major OS update support these devices were promised, so this isn't hugely surprising. All three devices will continue to get monthly security updates through at least November of this year, but they'll remain stuck on Android 8.1 for an underlying OS as far as official Google updates go.