Pixel 7, the first 64-bit-only Android phone

Posted by Serban Constantinescu, Product Manager,Pixel 7 and Pixel 7 Pro are the first Android phones to support only 64-bit apps. This configuration drops OS support for 32-bit code, reducing memory usage, improving performance, and enhancing security. Over time, we expect this device configuration to become commonplace.

Thanks to the efforts and collaboration of the entire Android community, our ecosystem is ready. Transitioning Android devices to 64-bit-only required many changes across the platform, tooling, Play, and, of course, your apps. We started by introducing 64-bit support in 2014, announcing policy changes in 2017 and requiring support for Google Play apps starting 2019.

Your device is faster, safer and uses less memory

64-bit apps run faster because they have access to extra registers and instructions that aren't available to 32-bit apps. In addition, newer CPUs deliver up to 25% better performance when running 64-bit code or even drop support for 32-bit code altogether.

64-bit can help improve security. The bigger address space makes defenses like ASLR more effective and the spare bits can be used to protect control flow integrity. These countermeasures may reduce the chance an intruder can take control of your device.

Removing support for 32-bit code saves up to 150MB of RAM, which was used by the OS even when not running 32-bit apps. These memory savings result in fewer out-of-memory conditions meaning less jank and fewer background app kills.

Developers have access to better tools

Developers targeting 64-bit have access to better tools such as HWASan for detecting memory errors and improving the quality of an app.

Faster OS updates for vendors

64-bit-only device configurations halve the CTS testing time. Combined with GKI, vendors can update devices faster and more easily.

Going forward

With 64-bit-only devices now reaching users, we encourage developers to start paying extra attention to testing their apps and updates for 64-bit-only devices. To support this, Google Play now provides pre-launch reports that are run on 64-bit-only devices to detect and report compatibility problems.

Note: While 64-bit-only devices will grow in popularity with phones joining Android Auto in this group, 32-bit-only devices will continue to be important for Android Go, Android TV, and Android Wear. Please continue supporting 32-bit ABIs; Google Play will continue serving 32-bit apps to 32-bit-only devices.

Beta Channel Update for Desktop

The Chrome team is excited to announce the promotion of Chrome 108 to the Beta channel for Windows, Mac and Linux. Chrome 108.0.5359.22 contains our usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore - please head to the Chromium blog to learn more!



A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issues, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.



Srinivas SistaGoogle Chrome

Beta Channel Update for Desktop

The Chrome team is excited to announce the promotion of Chrome 108 to the Beta channel for Windows, Mac and Linux. Chrome 108.0.5359.22 contains our usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore - please head to the Chromium blog to learn more!



A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issues, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.



Srinivas SistaGoogle Chrome

Beta Channel Update for Desktop

The Chrome team is excited to announce the promotion of Chrome 108 to the Beta channel for Windows, Mac and Linux. Chrome 108.0.5359.22 contains our usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore - please head to the Chromium blog to learn more!



A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issues, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.



Srinivas SistaGoogle Chrome

Beta Channel Update for Desktop

The Chrome team is excited to announce the promotion of Chrome 108 to the Beta channel for Windows, Mac and Linux. Chrome 108.0.5359.22 contains our usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore - please head to the Chromium blog to learn more!



A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issues, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.



Srinivas SistaGoogle Chrome

How we detect, remove and report child sexual abuse material

Since Google’s earliest days, we have worked to prevent the spread of illegal child sexual abuse material (referred to as CSAM). Child safety organizations and governments rightly expect — and in many cases require — us to take action to remove it from our systems. Which is why, when we find CSAM on our platforms, we remove it, report it and often take the step to suspend the account.

Although CSAM accounts for a very small portion of the material uploaded and shared across our platforms, we take the implications of both CSAM violations and suspending accounts seriously. Our goal is to prevent abuse on our platforms while minimizing the risk of an incorrect suspension. Today, we are sharing more information on how we detect this harmful content and the steps we are taking to be more transparent about our processes with users.

How we detect CSAM

We rely on two equally important technologies to help us proactively identify child sexual abuse material: hash matching and artificial intelligence (AI). We also have a team of highly specialized and trained content reviewers and subject matter experts who help ensure that our technology delivers accurate results.

This combination enables us to detect CSAM on our platforms at scale, while keeping our false positive rate extremely low.

How we use hash matching to identify known CSAM

CSAM that has been previously identified is automatically flagged by our systems using Hash Matching Technology. This technology assigns images and videos a unique digital signature — a “hash” — and then compares it against a database of known signatures. If the two match, the content is considered to be the same or closely similar.

We obtain hashes from a variety of highly trusted sources including Internet Watch Foundation (IWF), National Center for Missing and Exploited Children (NCMEC), and others. NCMEC specifically hosts a hash-sharing service used by the tech industry and specialist NGOs from around the world. This repository serves as one starting point – but we review every purported CSAM hash independently to confirm its accuracy. Once we confirm it as CSAM, we input it into our detection systems.

The overwhelming majority of imagery reported by Google – approximately 90% – matches previously identified CSAM, much of which is already in the NCMEC database.

How we use artificial intelligence to identify new content

While hash matching helps us find known CSAM, we use artificial intelligence to flag new content that is very similar to patterns of previously confirmed CSAM. Our systems are specifically designed to recognize benign imagery like a child playing in the bathtub or backyard, which will not be flagged. A specialist team of trained personnel also reviews each piece of new imagery flagged, to confirm it is CSAM before it is ever reported.

Quick detection of new images means that children who are being sexually abused today are much more likely to be identified and protected from further abuse. And to help promote safety across the web, we provide other companies and NGOs access to detection and processing technology through our Child Safety Toolkit. This includes our Content Safety API, which helps partners more quickly prioritize and review content that is highly likely to be abusive. In the past 30 days alone, the Content Safety API has helped partners process over four billion pieces of CSAM. Through the toolkit, partners can also license our proprietary CSAI Match Technology, to detect known video CSAM on their platforms.

Our specialized content reviewers

While technology is essential in the fight against CSAM at scale, human reviewers also play a critical role to confirm hash matches and content discovered through AI. Our team members bring deep expertise to this work with backgrounds in law, child safety and advocacy, social work, and cyber investigations, among other disciplines. They are specially trained on both our policy scope and what legally constitutes child sexual abuse material. We regularly update this training and our guidelines in consultation with legal counsel, independent experts and medical professionals.

We know this is incredibly sensitive work and have a number of measures in place to protect reviewers’ physical and mental wellness. Our teams have access to tools, workspaces, resources and professional expertise, including counseling.

Referring content to NCMEC

Following this review process, we report the imagery identified as CSAM to NCMEC as required by US law. NCMEC evaluates the report and may decide to refer the case to a relevant law enforcement agency. If the local law enforcement agency chooses to investigate the NCMEC report further, requests for additional information from Google must be made through valid legal process or in accordance with applicable laws. You can learn more here on how we handle these types of requests.

In doing this work, we also believe in the importance of transparency. Today, we updated our Transparency Report, with the latest data around our detection and reporting efforts. In the first half of this year, we've made over one million reports to NCMEC about content that met the legal definition of CSAM, and where appropriate, also suspended the Google accounts associated with that content (approximately 270,000 account suspensions).

By using existing, confirmed CSAM to identify identical or similar material uploaded or shared to our platforms, we maintain an incredibly low false positive rate. However, if someone believes their account was incorrectly disabled, including for content flagged as CSAM, they can appeal the determination. A member of our child safety team reviews the appeal, and if we find we have made a mistake, we reinstate the account as soon as possible.

Improving our processes

Avoiding CSAM on our platforms is incredibly important work and is an area we’ll continue to invest in. At the same time, we recognize that we can improve the user experience when people come to us with questions about their accounts or believe we made wrong decisions. For example, we are actively working on ways to increase transparency and provide more detailed reasons for account suspensions (while making sure we don’t compromise the safety of children or interfere with potential law enforcement investigations). And we will also update our appeals process to allow users to submit even more context about their account, including to share more information and documentation from relevant independent professionals or law enforcement agencies to aid our understanding of the content detected in the account.

We will continue to explore additional ways to balance preventing this harmful content from spreading on our platforms with creating a more streamlined support experience for all users.

3 tips to maximize budget efficiency across media

In an increasingly fragmented media landscape, making good use of your ad dollars is a tall order. Using a siloed strategy means you’re at risk of unintentionally reaching the same people more often than desired. This can lead to an ineffective use of your budget and poor user experience.

For years, we’ve seen leading brands improve the efficiency of their ad operations and media using Display & Video 360 as a way to unify their campaigns across inventory sources, devices and markets. Today, we’ll share these marketers’ three best practices with some of their latest success stories highlighting key features to unify their media. Display & Video 360 continues to future-proof these tools using a combination of advanced machine learning technology, first-party data signals and privacy-preserving APIs.

Plan and forecast reach in one place

This is where it all begins. Plans that take your entire media mix into account are inherently more accurate. And planning solutions that are tightly connected to your media buying platform can let you more accurately and quickly assess the potential reach of your plans. Display & Video 360 planning tools let you estimate the reach of your campaign across any type of environment or inventory source — including web, audio, connected TV (CTV) and even linear TV.

Reckitt is a global brand that found success optimizing its budget allocation for Airborne campaigns using Display & Video 360’s reach planning capabilities. Reckitt decided to diversify its media mix beyond traditional TV ads to boost its presence on CTV. So, it started looking for a planning tool that could account for CTV streamers. Harnessing Display & Video 360 forecasting solutions, the company estimated how much incremental reach could be gained by bringing together all its CTV deals — YouTube, Disney, The CW and Discovery — in the same campaign. The tool let them create accurate, custom media plans. By pulling insights like optimal spend and reach, Reckitt could compare the effectiveness of different campaign types. Armed with these insights, the company reached over 11 million CTV households within their core audience while keeping its spend under control. Reckitt also ensured these viewers weren’t duplicative with their traditional TV audience, generating 18% more viewers by adding CTV ads to their TV mix.

Combine various inventory sources in one place

I remember days when programmatic buying was just about serving standard display ads on the web. We’ve come a long way since then. Over the years, we’ve added access to thousands of publishers and all sorts of new inventory sources in Display & Video 360. For example, using digital out-of-home, brands can now reach people out in the real-world with the efficiency of programmatic technology. Today Display & Video 360 already partners with exchanges Hivestack, Magnite, Place Exchange, Ströer SSP, VIOOH and Vistar Media. These exchanges give access to large media owners around the world like Clear Channel Outdoor, Intersection, JCDecaux, Lamar and Ströer.

With more top media companies like Disney making their inventory available programmatically, connected TV advertising gives brands another exciting terrain to engage with their customers. Today 93% of ad-supported connected TV households in the U.S. can be reached with Display & Video 360, according to comScore.[caf5bd]We’re also continuing to unlock top CTV inventory around the world. For example, you can now reach people watching Peacock, NBCUniversal’s ad-supported streaming service in the U.S. or Channel 4's programming in the U.K. And all these top CTV placements can be purchased alongside other programmatic ads in a consolidated CTV workflow featuring parameters applicable to any source of CTV inventory — whether it’s Hulu, YouTube, Paramount or any other publisher. This TV-specific insertion order makes it easier to optimize for common goals or control ad frequency across your entire CTV media mix.

Combining all CTV apps under one insertion order gives us a better way to flex budgets and manage frequency across the two universes. Jaedyn Fuqua, Account Manager
Adswerve

Manage frequency in one place

With Display & Video 360, you can manage ad exposure across media buys while respecting user privacy, even when third-party cookies and identifiers are not present. Frequency can be managed across any type of device and transaction type including CTV and Programmatic Guaranteed deals across a variety of exchanges.

We're doubling down on programmatic reservation, particularly in the growing CTV landscape. So managing frequency for Programmatic Guaranteed deals with more exchanges is critical to help us further reduce waste associated with ad overexposure. Charles Cebuhar, Sr Director Digital Activation
OMG Center of Excellence

And you can get a tailored assessment of the impact of cross-channel frequency management solutions: Display & Video 360’s self-service data visualization shows how much reach was gained due to effective frequency management at the campaign level.

This is how Audi turbocharged its incremental reach. To launch its all-new Q4 e-tron electric model in Germany, the automaker needed a cost-efficient way of reaching as many cord-cutters as possible with a new video campaign. The brand decided to use frequency management across a mix of standard in-stream video formats and exclusive Programmatic Guaranteed deals from Sky, DAZN and other well-known publishers in Germany. Having a real-time view of reach gains gave the brand and its media agency more precision in evaluating campaign performance. During the six-week campaign, Audi assessed that managing programmatic campaigns across channels in a consolidated way allowed the brand to reach 1.2 million additional unique users — or a 13% rise in incremental reach — without bumping up budgets.

With a similar approach, L’Oréal Germany was able to increase the reach of its Garnier Greentalk campaign by 16% at no extra cost.

With Display & Video 360, we’re able to see the added reach that comes from our unified frequency management strategy. This is a big step up in how we evaluate the success of our media. Nils Lenzko, Precision Advertising Manager
L'Oréal

Looking forward, we’ll ensure these media unification capabilities remain accessible to all Display & Video 360 users while respecting people's privacy online. In fact, we’ve already started enhancing these solutions using a combination of machine learning techniques and first-party data signals so they keep working in the future. For example, Unique Reach metrics already go beyond basic cookie measurement to help you understand how many times people were shown your ad across different devices, formats and networks. And Display & Video 360 already uses modeled frequency management in situations with limited user signals.

These are just a few examples of the benefits of consolidating media. We also see advertisers who take a unified approach to media buying enjoy unified reporting, rationalized budgeting, and streamlined billing. As we move forward, we’ll keep adding more functionality to advertisers’ and media agencies’ toolbox to help them get better return from their unified media budgets.

Chrome for Android Update

Hi, everyone! We've just released Chrome 107 (107.0.5304.91) for Android: it'll become available on Google Play over the next few days.

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Android releases contain the same security fixes as their corresponding Desktop release (Windows: 107.0.5304.87/.88, Mac: 107.0.5304.87, Linux: 107.0.5304.87), unless otherwise noted.


Krishna Govind
Google Chrome

Chrome for Android Update

Hi, everyone! We've just released Chrome 107 (107.0.5304.91) for Android: it'll become available on Google Play over the next few days.

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Android releases contain the same security fixes as their corresponding Desktop release (Windows: 107.0.5304.87/.88, Mac: 107.0.5304.87, Linux: 107.0.5304.87), unless otherwise noted.


Krishna Govind
Google Chrome

Chrome for Android Update

Hi, everyone! We've just released Chrome 107 (107.0.5304.91) for Android: it'll become available on Google Play over the next few days.

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Android releases contain the same security fixes as their corresponding Desktop release (Windows: 107.0.5304.87/.88, Mac: 107.0.5304.87, Linux: 107.0.5304.87), unless otherwise noted.


Krishna Govind
Google Chrome