Google Removes RISC-V Support From Android Common Kernel, Denies Abandoning Its Efforts

Mishaal Rahman reports via Android Authority: Earlier today, a Senior Staff Software Engineer at Google who, according to their LinkedIn, leads the Android Systems Team and works on Android’s Linux kernel fork, submitted a series of patches to AOSP that “remove ACK’s support for riscv64.” The description of these patches states that “support for risc64 GKI kernels is discontinued.”

ACK stands for Android Common Kernel and refers to the downstream branches of the official kernel.org Linux kernels that Google maintains. The ACK is basically Linux plus some “patches of interest to the Android community that haven’t been merged into mainline or Long Term Supported (LTS) kernels.” There are multiple ACK branches, including android-mainline, which is the primary development branch that is forked into “GKI” kernel branches that correspond to a particular combination of supported Linux kernel and Android OS version. GKI stands for Generic Kernel Image and refers to a kernel that’s built from one of these branches. Every certified Android device ships with a kernel based on one of these GKI branches, as Google currently does not certify Android devices that ship with a mainline Linux kernel build.

Since these patches remove RISC-V kernel support, RISC-V kernel build support, and RISC-V emulator support, any companies looking to compile a RISC-V build of Android right now would need to create and maintain their own fork of Linux with the requisite ACK and RISC-V patches. Given that Google currently only certifies Android builds that ship with a GKI kernel built from an ACK branch, that means we likely won’t see certified builds of Android on RISC-V hardware anytime soon. Our initial interpretation of these patches was that Google was preparing to kill off RISC-V support in Android since that was the most obvious conclusion. However, a spokesperson for Google told us this: “Android will continue to support RISC-V. Due to the rapid rate of iteration, we are not ready to provide a single supported image for all vendors. This particular series of patches removes RISC-V support from the Android Generic Kernel Image (GKI).” Based on Google’s statement, Rahman suggests that “there’s still a ton of work that needs to be done before Android is ready for RISC-V.”

“Even once it’s ready, Google will need to redo the work to add RISC-V support in the kernel anyway. At the very least, Google’s decision likely means that we might need to wait even longer than expected to see commercial Android devices running on a RISC-V chip.”

Read more of this story at Slashdot.

13.4 Million Kaiser Insurance Members Affected by Data Leak to Online Advertisers

Kaiser Permanente is the latest healthcare giant to report a data breach. Kaiser said 13.4 million current and former insurance members had their patient data shared with third-party advertisers, thanks to an improperly implemented tracking code the company used to see how its members navigated through its websites. Dark Reading reports: The shared data included names, IP addresses, what pages people visited, whether they were actively signed in, and even the search terms they used when visiting the company’s online health encyclopedia. Kaiser has reportedly removed the tracking code from its sites, and while the incident wasn’t a hacking event, the breach is still concerning from a security perspective, according to Narayana Pappu, CEO at Zendata.

“The presence of third-party trackers belonging to advertisers, and the oversharing of customer information with these trackers, is a pervasive problem in both health tech and government space,” he explains. “Once shared, advertisers have used this information to target ads at users for complementary products (based on health data); this has happened multiple times in the past few years, including at Goodrx. Although this does not fit the traditional definition of a data breach, it essentially results in the same outcome — an entity and the use case the data was not intended for has access to it. There is usually no monitoring/auditing process to identify and prevent the issue.”

Read more of this story at Slashdot.

A Coal Billionaire is Building the World’s Biggest Clean Energy Plant – Five Times the Size of Paris

An anonymous reader shared this report from CNN:

Five times the size of Paris. Visible from space. The world’s biggest energy plant. Enough electricity to power Switzerland. The scale of the project transforming swathes of barren salt desert on the edge of western India into one of the most important sources of clean energy anywhere on the planet is so overwhelming that the man in charge can’t keep up. “I don’t even do the math any more,” Sagar Adani told CNN in an interview last week.

Adani is executive director of Adani Green Energy Limited (AGEL). He’s also the nephew of Gautam Adani, Asia’s second richest man, whose $100 billion fortune stems from the Adani Group, India’s biggest coal importer and a leading miner of the dirty fuel. Founded in 1988, the conglomerate has businesses in fields ranging from ports and thermal power plants to media and cements. Its clean energy unit AGEL is building the sprawling solar and wind power plant in the western Indian state of Gujarat at a cost of about $20 billion.

It will be the world’s biggest renewable park when it is finished in about five years, and should generate enough clean electricity to power 16 million Indian homes… [T]he park will cover more than 200 square miles and be the planet’s largest power plant regardless of the energy source, AGEL said.

CNN adds that the company “plans to invest $100 billion into energy transition over the next decade, with 70% of the investments ear-marked for clean energy.”

Read more of this story at Slashdot.

Bezos, Other Amazon Execs Used Signal – a Problem for FTC Investigators

Pursuing an unfair business practices case against Amazon, America’s Federal Trade Commission has now “accused” Amazon of using Signal, reports the Seattle Times:

The newspaper notes that the app “can be set to automatically delete messages, to hide information related to the FTC’s ongoing antitrust investigation into the company.”

In a court filing this week, the FTC moved to “compel” Amazon to share more information about its policies and instructions related to using the Signal app… The FTC accused Amazon executives of manually turning on the feature to delete messages in Signal even after the company learned that the FTC was investigating and had told Amazon to keep documents, emails and other messages.

Many of Amazon’s senior leaders used Signal, according to the FTC, including former CEO and current chair Jeff Bezos, CEO Andy Jassy, and general counsel David Zapolsky, as well as Jeff Wilke, former head of Amazon’s worldwide consumer business, and Dave Clark, former worldwide operations chief. “Amazon is a company that tightly controls what its employees put into writing,” FTC attorneys said in a court filing Thursday. “But Amazon’s senior leadership also used another channel for internal communications and avoided the need to talk carefully by destroying the records of their messages….”

In the court filing Thursday, the FTC asked Amazon to provide two troves of documents related to its use of Signal: Amazon’s document preservation notices and its instructions about the use of “ephemeral messaging applications, including Signal.” The FTC said Amazon waited for more than a year after it learned of the investigation to instruct its employees to preserve Signal messages. “It is highly likely that relevant information has been destroyed as a result of Amazon’s actions and inactions,” the FTC wrote in court records.

Read more of this story at Slashdot.