Last year, Google announced Android Open Source Project (AOSP) support for Rust, and today the company provided an update, while highlighting the decline in memory safety vulnerabilities. 9to5Google reports: Google says the "number of memory safety vulnerabilities have dropped considerably over the past few years/releases."; Specifically, the number of annual memory safety vulnerabilities fell from 223 to 85 between 2019 and 2022. They are now 35% of Android's total vulnerabilities versus 76% four years ago. In fact, "2022 is the first year where memory safety vulnerabilities do not represent a majority of Android's vulnerabilities." That count is for "vulnerabilities reported in the Android security bulletin, which includes critical/high severity vulnerabilities reported through our vulnerability rewards program (VRP) and vulnerabilities reported internally." During that period, the amount of new memory-unsafe code entering Android has decreased: "Android 13 is the first Android release where a majority of new code added to the release is in a memory safe language. " Rust makes up 21% of all new native code in Android 13, including the Ultra-wideband (UWB) stack, DNS-over-HTTP3, Keystore2, Android's Virtualization framework (AVF), and "various other components and their open source dependencies." Google considers it significant that there have been "zero memory safety vulnerabilities discovered in Android's Rust code" so far across Android 12 and 13. Google's blog post today also talks about non-memory-safety vulnerabilities, and its future plans: "... We're implementing userspace HALs in Rust. We're adding support for Rust in Trusted Applications. We've migrated VM firmware in the Android Virtualization Framework to Rust. With support for Rust landing in Linux 6.1 we're excited to bring memory-safety to the kernel, starting with kernel drivers.

Read more of this story at Slashdot.

Android OEMs still don't provide the six years of updates you get with Apple phones, but some manufacturers are trying to close that gap. From a report: OnePlus is adding an extra year to its smartphone update promise and is now offering four years of major OS updates and five years of security updates. Timeline-wise, this plan matches Samsung's, though Samsung offers monthly security updates and OnePlus doesn't. The company is still only promising security updates every other month, so it can't do too much bragging. Android-maker Google -- who you'd think would have the best update plan -- is in a distant third, with only three years of OS updates and five years of security updates.

Read more of this story at Slashdot.

An anonymous reader quotes a report from Ars Technica: Google announced that Android's space-saving app file format, Android App Bundles (AABs), will finally be the standard on Android TV. By May 2023 -- that's in six months -- Google will require all Android TV apps to switch to the new file format, which can cut down on app storage requirements by 20 percent. Android App Bundles were announced with Android 9 in 2018 as a way to save device storage by breaking an app up into modules, rather than one big monolithic APK (the old Android app format) with every possible piece of data. Android apps support a ton of different languages, display resolutions, and CPU architectures, but each individual device only needs to cherry-pick a few of those options to work. Android App Bundles integrate with the Play Store to create a dynamic delivery system for each module. Your phone communicates which modules it needs to the Play Store, and Google's servers bundled up an appropriate package and sent it to your device. It's even possible for developers to move some lesser-used app functionality into a bundle that can be downloaded on the fly if a user needs it. [...] Google says Android App Bundles average around a 20 percent space savings compared to a monolithic APK, which will be a huge help for these storage-starved devices. Since 2021, they have been the required standard for phones and tablets, and in six months, TV apps will be required to use them, too. Developers who don't switch in time will have their TV apps hidden from search, so they'd better get to work! Google estimates that "in most cases it will take one engineer about three days to migrate."

Read more of this story at Slashdot.

An anonymous reader quotes a report from Ars Technica: Privacy-focused search site DuckDuckGo has added yet another way to prevent more of your data from going to advertisers, opening its App Tracking Protection for Android to beta testers. DuckDuckGo is positioning App Tracking Protection as something like Apple's App Tracking Transparency for iOS devices, but "even more powerful." Enabling the service in the DuckDuckGo app for Android (under the "More from DuckDuckGo" section) installs a local VPN service on your phone, which can then start automatically blocking trackers on DDG's public blocklist. DuckDuckGo says this happens "without sending app data to DuckDuckGo or other remote servers." Google recently gave Android users some native tools to prevent wanton tracking, including app-by-app location-tracking approval and a limited native ad-tracking opt-out. Apple's App Tracking Transparency asks if users want to block apps from accessing the Identifier for Advertisers (IDFA), but apps can still use the largest tracking networks across many apps to better profile app users. Allison Goodman, senior communications manager for DuckDuckGo, told Ars Technica that App Tracking Protection needs Android's VPN permission so it can monitor network traffic. When it recognizes a tracker from its blocklist, it "looks at the destination domain for any outbound request and blocks them if they are in our blocklist and the requesting app is not owned by the same company that owns the domain." Goodman added that "much of the data collected by trackers is not controlled by [Android] permissions," making App Tracking Protection a complementary offering.

Read more of this story at Slashdot.

Google today announced it's expanding its user choice billing pilot, which allows Android app developers to use other payment systems besides Google's own. The program will now become available to new markets, including the U.S., Brazil and South Africa, and Bumble will now join Spotify as one of the pilot testers. From a report: Google additionally announced Spotify will now begin rolling out its implementation of the program starting this week. The company had first announced its intention to launch a third-party billing option back in March of this year, with Spotify as the initial tester. Since then, the program has steadily expanded. Last month, for example, Google invited other non-game developers to apply for the user choice billing program in select markets, including India, Australia, Indonesia, Japan and the European Economic Area (EEA). The company also introduced a similar policy for developers in the EEA region in July, but the new guidelines raised the commission discount from 3% to 4% for developers who opted in. With today's expansion, user choice billing will be made available to 35 countries worldwide. Google says it's been working with Spotify to help develop the experience and now the streaming music service will begin to put the new features into action in supported markets. The experience could still change over time, Google warned, as this is still the early days of the pilot test.

Read more of this story at Slashdot.

Linux magazine explores how to breath fresh life into old Android devices: Every mobile device needs its own Android build because of numerous drivers that are not available in the source code. The need to maintain every version of Android for every mobile device means that many manufacturers eventually stop supporting updates. Often, smartphones or tablets that still work perfectly can no longer be used without worry because the manufacturer has simply ceased to offer bug fixes and security updates.... The LineageOS project, the successor to the CyanogenMod project, which was discontinued in 2016, proves that it is not impossible to keep these devices up-to-date. Unpaid volunteers at LineageOS do the work that many manufacturers do not want to do: They combine current Android releases with the required device-specific drivers. The LineageOS project (Figure 1) provides Android systems with a fresh patch status every month for around 300 devices. The builds are released weekly, unless there is a problem during the build. The Devices page on the LineageOS Wiki provides the details of whether a LineageOS build is available for your smartphone or tablet.... I recommend the LineageOS project as the first port of call for anyone who wants to protect an older smartphone or tablet that is no longer maintained and doesn't receive Google security patches. The LineageOS derivatives LineageOS for MicroG and /e/OS make it even easier to enjoy a Google-free smartphone without too many restrictions. The article also describes how to use TWRP to flash a manufacturer-independent recovery system (while also creating a restoreable backup of the existing system) as an alternative to LineageOS's own recovery tools. And it even explains how to unlock the bootloader — although there may be other locks set up separately by the manufacturer. "Some manufacturers require you to register the device to unlock it, and then — after telling you that the warranty is now void — they hand over a code. Others refuse to unlock the device altogether." Thanks to Slashdot reader DevNull127 for submitting the article.

Read more of this story at Slashdot.

According to a new report, almost half of Android-based mobile phones used by U.S. state and local government employees are running outdated versions of the operating system, exposing them to hundreds of vulnerabilities that can be leveraged for attacks. From a report: These statistics come from a report by cybersecurity firm Lookout, based on an analysis of 200 million devices and 175 million applications from 2021 to H2 2022. The report additionally warns of a rise in all threat metrics, including attempted phishing attacks against government employees, reliance on unmanaged mobile devices, and liability points in mission-critical networks. Outdated versions of mobile operating systems allow attackers to exploit vulnerabilities that can be used to breach targets, run code on the device, plant spyware, steal credentials, and more. For example, last week, Apple released iOS 16.1, fixing an actively exploited zero-day memory corruption flaw used by hackers against iPhone users to achieve arbitrary code execution with kernel privileges. Lookout reports that ten months after iOS 15 had been made available to users, 5% of federal government employees and 30% of state and local government devices were running older versions of the operating system. The situation is much worse for Android, as ten months after the release of version 12, approximately 30% of federal devices and almost 50% of state and local government devices still needed to upgrade to the latest versions, thus remaining vulnerable to bugs that can be exploited in attacks. It should be noted that Android 13 is the latest version of the operating system, but it was released after the first half of 2022, from which this data was collected.

Read more of this story at Slashdot.

According to Protocol, Amazon and Google have struck a deal in recent months that allows Fire TV models to be produced by Android TV partners. From the report: As a result of that deal, Amazon has been able to work with a number of consumer electronics companies -- including not only TCL, but also Xiaomi and Hisense -- to vastly expand the number of available smart TVs running Fire TV OS. All of these companies were previously barred from doing so under licensing terms imposed by Google. The agreement may also alleviate some of the pressure Google has been feeling as regulators around the world have investigated its Android platform. However, some experts are skeptical a singular deal will address the overarching concerns with Google's operation and licensing of Android to third parties. The deal between Amazon and Google resolves a yearslong dispute over licensing restrictions Google imposes on hardware manufacturers that make Android-based phones, TVs, and other devices. In order to gain access to Google's officially sanctioned version of Android as well as the company's popular apps like Google Maps and YouTube, manufacturers have to sign a confidential document known as the Android Compatibility Commitment. The ACC prevents manufacturers from also making devices based on forked versions of Android not compatible with Google's guidelines. The ACC, which was previously known as the Anti-Fragmentation Agreement, had long been an open secret in industry circles. Its full impact on the smart TV space became public when Protocol reported terms of the agreement in March of 2020 and outlined how the policy effectively barred companies like TCL from making smart TVs running any forked version of Android, including Amazon's Fire TV OS. Google has been justifying these policies by pointing to the harmful consequences of Android fragmentation, positing that the rules assured developers and consumers that apps would run across all Android-based devices. However, the crux of Google's requirements is that they apply across device categories. By making a Fire TV-based smart TV, TCL would have effectively risked losing access to Google's Android for its smartphone business -- a risk the company, and many of its competitors that develop both smartphones and TVs, weren't willing to take. At the time, both Google and Amazon declined to comment on the dispute. However, Amazon was a lot more forthcoming when it talked to Indian regulators for a wide-ranging probe into Google's Android policies. "Given the breadth of the anti-fragmentation obligations, Amazon has also experienced significant difficulties in finding [original equipment manufacturer] partners to manufacture smart TVs running its Fire OS," the company's Indian subsidiary told regulators in a submission that was included in last week's report. Amazon told regulators that "at least seven" manufacturers had told the company they weren't able to make Fire TV-based smart TVs because of Google's restrictions. "In several cases, the OEM has indicated that it cannot work with Amazon despite a professed desire to do so in connection with smart TVs," Amazon said in its submission. "In others, the OEM has tried and failed to obtain 'permission' from Google."

Read more of this story at Slashdot.

While many people in California felt a moderate earthquake Tuesday, some smartphone users actually got a heads-up before it happened thanks to technology developed at the University of California, Berkeley. Axios reports: Researchers at Berkeley released an app called MyShake that can offer a brief earthquake warning by detecting the signals of an earthquake just before they are felt. Think of it like how you can see lightning before you hear thunder. The app works on both iPhone and Android, but Google announced in 2020 it would implement Berkeley's technology directly into Android, allowing far more people to benefit. As often happens after an earthquake, people turned to Twitter after the Magnitude 5.1 quake. But some reported getting the alert first. "Got the earthquake alert on my Android phone a few seconds before I felt it," Google's Dieter Bohn said in a tweet. Google CEO Sundar Pichai also tweeted about getting the alert.

Read more of this story at Slashdot.

An anonymous reader quotes a report from XDA Developers: As it turns out, the Google Pixel 7 series appears to be the first set of Android smartphones that only support 64-bit applications. [Android expert Mishaal Rahman first reported the news.] Rahman later corrected himself to say that it's a 64-bit Zygote but a 32-bit and 64-bit userspace, not a 64-bit only build of Android 13 as initially reported. This certainly lends credence to the claim that the Google Pixel tablet may come with a 64-bit only build of Android 13, though. What this means is that for any apps that don't have 64-bit libraries, you won't be able to install them. This includes older versions of apps such as Jetpack Joyride and even older, completely defunct apps like Flappy Bird. It's not as if Tensor G2 doesn't support it either -- its three different cores all support AArch32 execution. Google could have enabled 32-bit support as they have done in its previous smartphones. Listing the Android Binary Interfaces (ABI) returns that there is nothing present for "armeabi-v7a" or "armeabi". "arm64-v8a" support is listed, but as per the Android documentation, it only supports the AArch64 instruction set. What does this mean, and does it have any benefits? Most benefits won't really be visible to consumers, as these improvements are primarily found in heightened security, better performance, and reduced processing cost thanks to the lack of additional ABIs. All apps on the Google Play Store have had to have 64-bit support since August 2019, and the company stopped serving 32-bit apps that don't have any 64-bit support last year.

Read more of this story at Slashdot.

Google has approved Donald Trump's Truth Social app for release in its Play Store, opening up a key distribution channel for the social network ahead of US midterm elections. Bloomberg reports: Google had previously declined to distribute the app, saying it needed to address the fact that it hosted violent threats and other content that goes against Google's standards. Google, which is owned by Alphabet Inc., confirmed on Wednesday that Truth Social was now available. Truth Social has agreed to take down content that violates Google's policies, Google said. Devin Nunes, chief executive officer of Trump Media & Technology Group, said in a statement that the development represented "a significant milestone in our mission to restore free speech online." "It's been a pleasure to work with Google, and we're glad they helped us to finally bring Truth Social to all Americans, regardless of what device they use," Nunes said.

Read more of this story at Slashdot.

Android 13 has recently hit the streets, and with it, Google is raising the minimum requirements for Android phones. From a report: Google's latest blog post announced that the minimum amount of RAM for Android Go, the low-end version of Android, is now 2GB for Android 13, whereas previously, it was 1GB. Esper's Mishaal Rahman and Google Product Expert Jason Bayton also claim the minimum storage requirements have been bumped up to 16GB, though Google doesn't seem to have publicly documented this anywhere. The increase in system requirements means any phone that doesn't meet the minimum specs won't be able to update to Android 13. New phones launching with Android 13 will need to meet the minimum requirements to be eligible for Play Store licensing, though launching with an older version of Android (with lower requirements) will still be an option for a while. Technically, anyone can grab the Android source code and build anything with it, but if you want to license the Google apps and have access to the Google-trademarked brand "Android," you'll need to comply with Google's rules.

Read more of this story at Slashdot.

Google has started sending out invites for its fall hardware event, which is set to take place on Thursday, October 6th, at 10AM ET. The Verge reports: The event will launch the upcoming Pixel 7 phones, as well as the Pixel Watch -- the company showed off both devices at its I/O event earlier this year, announcing they're coming in the fall. Since Google's last event, purported leaks have revealed even more about the devices, with both the Watch and phones seemingly making their way into people's hands. The Pixel 7 seems like it'll be a pretty straightforward continuation of the previous generation of phones, but there's a bit of pressure with the Watch as the "first smartwatch built by Google, inside and out," as its product page on Google's online store says. Google's competitors (namely Samsung and Apple) have been making wearables for years, so the company's entry has to be competent and at least somewhat competitive right out of the gate. So far, details about it are scant -- we don't even know what chip it'll use -- but we should get a clearer picture come October 6th.

Read more of this story at Slashdot.

An anonymous reader quotes a report from Ars Technica: Google is slowly opening up the Play Store's billing policies. The "user choice billing" pilot program that was announced in March is now accepting sign-ups. Google describes the program in a support article, saying, "This pilot is designed to test offering an alternative billing option next to Google Play's billing system and to help us explore offering this choice to users. We are looking to gain feedback in different countries and ensure we can maintain a positive user experience." Developers interested in billing through an alternative provider can fill out Google's sign-up form, and it sounds like Google will manually review each application. Google won't let developers use the pilot program for games -- the biggest money makers -- but only for apps. Barring a few promotional tiers, Google and Apple both take around 30 percent not just for purchases of newly downloaded apps but also for digital purchases inside already downloaded apps. Many developers view these fees as excessive, and the push inside both ecosystems to allow third-party billing was originally pitched as a solution to high app store fees. Various regulatory bodies have forced the Google/Apple app store duopoly to open up payments, but Google and Apple have each done so without fixing the core problem of high app store fees. Apple takes a 27 percent cut of purchases processed outside the app store -- basically the original 30 percent fee minus the typical 3 percent processing fee charged by credit card companies. Google is doing something similar with this new program and will only reduce its fees by 4 percent. You'll still need to pay some kind of fee to your third-party payment processor, so with only a 4 percent reduction from Google, developers won't really save money.

Read more of this story at Slashdot.

An anonymous reader quotes a report from The Register: Google in November will prohibit Android VPN apps in its Play store from interfering with or blocking advertising, a change that may pose problems for some privacy applications. The updated Google Play policy, announced last month, will take effect on November 1. It states that only apps using the Android VPNService base class, and that function primarily as VPNs, can open a secure device-level tunnel to a remote service. Such VPNs, however, cannot "manipulate ads that can impact apps monetization." The rules appear to be intended to deter data-grabbing VPN services, such as Facebook's discontinued Onavo, and to prevent ad fraud. The T&Cs spell out that developers must declare the use of VPNservice in their apps' Google Play listing, must encrypt data from the device to the VPN endpoint, and must comply with Developer Program Policies, particularly those related to ad fraud, permissions, and malware. Blokada, a Sweden-based maker of an ad-blocking VPN app, worries this rule will hinder at least the previous iteration of its software, v5, and other privacy-oriented software. "Google claims to be cracking down on apps that are using the VPN service to track user data or rerouting user traffic to earn money through ads," Reda Labdaoui, marketing and sales manager at Blokada, wrote last week in a a forum post. "However, these policy changes also apply to apps that use the service to filter traffic locally on the device." Labdaoui suggests Blokada v6, which launched in June, should not be affected because it does filtering in the cloud without violating Google's device policies. But other apps may not be so fortunate.

Read more of this story at Slashdot.

Google hasn't yet approved Truth Social's Android app for distribution via its Play Store because of insufficient content moderation, a Google spokesperson tells Axios. From the report: Truth Social CEO Devin Nunes last week claimed the decision about when the app would be available on Android "is up to Google," but Google insists that the ball is in Truth Social's court. What Nunes is saying: "I don't know what's taking them so long." What Google is saying: âoeOn Aug. 19, we notified Truth Social of several violations of standard policies in their current app submission and reiterated that having effective systems for moderating user-generated content is a condition of our terms of service for any app to go live on Google Play." "Last week Truth Social wrote back acknowledging our feedback and saying that they are working on addressing these issues." A source says that Google's concerns relate to content such as physical threats and incitements to violence.

Read more of this story at Slashdot.

Google is trying "to make it easier for developers to create Android apps that connect in some way across a range of devices," reports the Verge. Documentation for the software development kit says it will simplify development for "multi-device experiences." "The Cross device SDK is open-source and will be available for different Android surfaces and non-Android ecosystem devices (Chrome OS, Windows, iOS)," explains the documentation, though the current developer preview only works with Android phones and tablets, according to the Verge. But they report that Google's new SDK "contains the tools developers need to make their apps play nice across Android devices, and, eventually non-Android phones, tablets, TVs, cars, and more." The SDK is supposed to let developers do three key things with their apps: discover nearby devices, establish secure connections between devices, and host an app's experience across multiple devices. According to Google, its cross-device SDK uses Wi-Fi, Bluetooth, and ultra-wideband to deliver multi-device connectivity.... [I]t could let multiple users on separate devices choose items from a menu when creating a group food order, saving you from passing your phone around the room. It could also let you pick up where you left off in an article when swapping from your phone to a tablet, or even allow the passengers in a car to share a specific map location with the vehicle's navigation system. It almost sounds like an expansion of Nearby Share, which enables users on Android to transfer files to devices that use Chrome OS and other Androids. In April, Esper's Mishaal Rahman spotted an upcoming Nearby Share update that could let you quickly share files across the devices that you're signed into Google with. Google also said during a CES 2022 keynote that it will bring Nearby Share to Windows devices later this year. "This SDK abstracts away the intricacies involved with working with device discovery, authentication, and connection protocols," argues Google's blog post, "allowing you to focus on what matters most — building delightful user experiences and connecting these experiences across a variety of form factors and platforms."

Read more of this story at Slashdot.

An anonymous reader quotes a report from Wired: As marketers, data brokers, and tech giants endlessly expand their access to individuals' data and movements across the web, tools like VPNs or cookie blockers can feel increasingly feeble and futile. Short of going totally off the grid forever, there are few options for the average person to meaningfully resist tracking online. Even after coming up with a technical solution last year for how phone carriers could stop automatically collecting users' locations, researchers Barath Raghavan and Paul Schmitt knew it would be challenging to convince telecoms to implement the change. So they decided to be the carrier they wanted to see in the world. The result is a new company, dubbed Invisv, that offers mobile data designed to separate users from specific identifiers so the company can't access or track customers' metadata, location information, or mobile browsing. Launching in beta today for Android, the company's Pretty Good Phone Privacy or PGPP service will replace the mechanism carriers normally use to turn cell phone tower connection data into a trove of information about users' movements. And it will also offer a Relay service that disassociates a user's IP address from their web browsing. PGPP's ability to mask your phone's identity from cell towers comes from a revelation about why cell towers collect the unique identifiers known as IMSI numbers, which can be tracked by both telecoms and other entities that deploy devices known as IMSI catchers, often called stringrays, which mimic a cell tower for surveillance purposes. Raghavan and Schmitt realized that at its core, the only reason carriers need to track IMSI numbers before allowing devices to connect to cell towers for service is so they can run billing checks and confirm that a given SIM card and device are paid up with their carrier. By acting as a carrier themselves, Invisv can implement their PGPP technology that simply generates a "yes" or "no" about whether a device should get service. On the PGPP "Mobile Pro" plan, which costs $90 per month, users get unlimited mobile data in the US and, at launch, unlimited international data in most European Union countries. Users also get 30 random IMSI number changes per month, and the changes can happen automatically (essentially one per day) or on demand whenever the customer wants them. The system is designed to be blinded so neither INVISV nor the cell towers you connect to know which IMSI is yours at any given time. There's also a "Mobile Core" plan for $40 per month that offers eight IMSI number changes per month and 9 GB of high-speed data per month. Both of these plans also include PGPP's Relay service. Similar to Apple's iCloud Private Relay, PGPP's Relay is a method for blocking everyone, from your internet provider or carrier to the websites you visit, from knowing both who you are and what you're looking at online at the same time. Such relays send your browsing data through two way stations that allow you to browse the web like normal while shielding your information from the world. When you navigate to a website, your IP address is visible to the first relay -- in this case, Invisv -- but the information about the page you're trying to load is encrypted. Then the second relay generates and connects an alternate IP address to your request, at which point it is able to decrypt and view the website you're trying to load. The content delivery network Fastly is working with Invisv to provide this second relay. Fastly is also one of the third-party providers for iCloud Private Relay. In this way, each relay knows some of the information about your browsing; the first simply knows that you are using the web, and the second sees the sites you connect to, but not who specifically is browsing there. In addition to being included in the two PGPP data plans, customers can also purchase the Relay service on its own for $5 per month and turn it on while connected to mobile data or Wi-Fi. The carrier is still working to bring its services to Apple's iOS. It's also worth noting that Invisv only offers mobile data; there are no voice calling services.

Read more of this story at Slashdot.

This week Samsung said customers can finally start buying replacement screens, rear glass and charging ports for home repairs from repair resource site iFixit, as well as from Samsung's Experience stores across the country, according to the Washington Post. But their article warns that for now the program is limited to just "a handful of higher-end models" like the Galaxy S20 and S21 series smartphones. ("We plan to expand to more models as the program matures," said a Samsung spokesperson.) You can't, for example, buy just a screen to replace a broken one in your Galaxy phone. Instead, Samsung says you must purchase an entire screen "assembly," which includes the display itself, the metal frame that surrounds it and another battery. Essentially, that means replacing the entire front of the phone and then some. That also means that, for the time being, Samsung doesn't have a way for you to purchase a genuine battery on its own to replace the one that isn't holding a long-charge or bloating — a common issue in devices that are used and charged regularly. The Samsung spokesperson told The Washington Post that "additional parts will be added as the program ramps up," though co-founder and CEO Kyle Wiens says iFixit will continue to sell third-party replacement batteries.... And we're not kidding about how fiddly these guides can be: according to iFixit, the process of replacing a Galaxy S20's screen assembly requires 41 steps, and that doesn't include putting the phone back together.

Read more of this story at Slashdot.

In response to user criticism, Google Play is bringing back the list of app permissions, but another curious Store change sees version numbers removed from the App info section. 9to5Google reports: Historically, you've been able to find the version number by opening a listings's "About this app" section and scrolling down to "App info" where it was the first line item. As of today, "Version" no longer appears there (or in the phone section of "Compatibility for your active devices") and "Updated on" is at the top. This information is only gone for the phone version of applications. It curiously remains for Wear OS and Android/Google TV apps. Meanwhile, version numbers still appear on the Google Play website. This issue does not appear related to (or just impact) apps that only note "Varies with device."

Read more of this story at Slashdot.