The Dev channel is being updated to OS version 16328.18.0 (Browser version 139.0.7258.33) for most ChromeOS devices.
If you find new issues, please let us know one of the following ways
Visit our ChromeOS communities
General: Chromebook Help Community
Beta Specific: ChromeOS Beta Help Community
Interested in switching channels? Find out how.
Andy Wu,The Dev channel is being updated to OS version 16328.18.0 (Browser version 139.0.7258.33) for most ChromeOS devices.
If you find new issues, please let us know one of the following ways
Visit our ChromeOS communities
General: Chromebook Help Community
Beta Specific: ChromeOS Beta Help Community
Interested in switching channels? Find out how.
Andy Wu,Traditionally, Android has operated with the 4 KB memory page size. However many ARM CPUs (the most common processors for Android phones) support the larger 16 KB page size, offering improved performance gains. With Android 15, the Android operating system is page-size-agnostic, allowing devices to run efficiently with either 4 KB or 16 KB page size.
Starting November 1st, 2025, all new apps and app updates that use native C/C++ code targeting Android 15+ devices submitted to Google Play must support 16 KB page sizes. This is a crucial step towards ensuring your app delivers the best possible performance on the latest Android hardware. Apps without native C/C++ code or dependencies, that just use the Kotlin and Java programming languages, are already compatible, but if you're using native code, now is the time to act.
This transition to larger 16 KB page sizes translates directly into a better user experience. Devices configured with 16 KB page size can see an overall performance boost of 5-10%. This means faster app launch times (up to 30% for some apps, 3.16% on average), improved battery usage (4.56% reduction in power draw), quicker camera starts (4.48-6.60% faster), and even speedier system boot-ups (around 0.8 seconds faster). While there is a marginal increase in memory use, a faster reclaim path is worth it.
If your app uses native C/C++ code from the Android NDK or relies on SDKs that do, you'll need to recompile and potentially adjust your code for 16 KB compatibility. The good news? Once your application is updated for the 16 KB page size, the same application binary can run seamlessly on both 4 KB and 16 KB devices.
This table describes who needs to transition and recompile their apps
We’ve created several Android Studio tools and guides that can help you prepare for migrating to using 16 KB page size.
APK Analyzer: Easily identify if your app contains native libraries by checking for .so files in the lib folder. The APK Analyzer can also visually indicate your app's 16 KB compatibility. You can then determine and update libraries as needed for 16 KB compliance.
Alignment Checks: Android Studio also provides warnings if your prebuilt libraries or APKs are not 16 KB compliant. You should then use the APK Analyzer tool to review which libraries need to be updated or if any code changes are required. If you want to detect the 16 KB page size compatibility checks in your CI (continuous integration) pipeline, you can leverage scripts and command line tools.
Lint in Android Studio now also highlights the native libraries which are not 16 KB aligned.
Tools Updates: Rebuild your native code with 16 KB alignment. Android Gradle Plugin (AGP) version 8.5.1 or higher automatically enables 16 KB alignment by default (during packaging) for uncompressed shared libraries. Similarly, Android NDK r28 and higher compile 16 KB-aligned by default. If you depend on other native SDK’s, they also need to be 16 KB aligned. You might need to reach out to the SDK developer to request a 16 KB compliant SDK.
Eliminate Hardcoded Assumptions: Identify and remove any hardcoded dependencies on PAGE_SIZE or assumptions that the page size is 4 KB (e.g., 4096). Instead, use getpagesize() or sysconf(_SC_PAGESIZE) to query the actual page size at runtime.
Android Emulator Support: Android Studio offers a 16 KB emulator target (for both arm64 and x86_64) directly in the Android Studio SDK Manager, allowing you to test your applications before uploading to Google Play.
On-Device Testing: For compatible devices like Pixel 8 and 8 Pro onwards (starting with Android 15 QPR1), a new developer option allows you to switch between 4 KB and 16 KB page sizes for real-device testing. You can verify the page size using adb shell getconf PAGE_SIZE.
Leverage Android Studio’s powerful tools to detect issues, build compatible binaries, fix your code, and thoroughly test your app for the new 16 KB memory page sizes. By doing so, you'll ensure an improved end user experience and contribute to a more performant Android ecosystem.
As always, your feedback is important to us – check known issues, report bugs, suggest improvements, and be part of our vibrant community on LinkedIn, Medium, YouTube, or X.
To better support you and provide earlier, more consistent access to in-development features, we are announcing a significant evolution in our pre-release program. Moving forward, the Android platform will have a Canary release channel, which will replace the previous developer preview program. This Canary release channel will function alongside the existing beta program.
This change is designed to provide a more streamlined and continuous opportunity for you to try out new platform capabilities and provide feedback throughout the entire year, not just in the early months of a new release cycle.
The Developer Preview program has been a critical part of our release cycle, but its structure had inherent limitations:
The new Android platform Canary channel addresses these challenges directly. By flashing your supported Pixel device to the Canary release channel, you can now receive a continuous, rolling stream of the latest platform builds via over-the-air (OTA) updates.
The Canary channel is intended for developers that want to explore and test with the earliest pre-release Android APIs and potential behavior changes. Builds from the Canary channel will have passed our automated tests as well as experienced a short test cycle with internal users. You should expect bugs and breaking changes. These bleeding-edge builds will not be the best choice for someone to use as their primary or only device.
The existing beta channel will remain the primary way for you to make sure that your apps are both compatible with and take advantage of upcoming platform features.
You can use the Android Flash Tool to get the most recent Canary build onto your supported Pixel device. Once flashed, you should expect OTA updates for the latest Canary builds as they become available. To exit the channel, flash a Beta or Public build to your device. This will require a data partition wipe.
Canary releases will be available on the Android Emulator through the Device Manager in Android Studio (currently, just in the Android Studio Canary channel), and Canary SDKs will be available for you to develop against through the SDK Manager.
Since most behavior changes require targeting a release, you can target Canary releases the way you can target any other platform SDK version, or use the Compatibility Framework with supported features to enable behavior changes in your apps.
Feedback is a critical component of this new program, so please file feature feedback and bug reports on your Canary experience through the Google Issue Tracker.
By transitioning to a true Canary channel, we aim to create a more transparent, collaborative, and efficient development process, giving you the seamless access you need to prepare for the future of Android.
The next generation of foldable and wearable devices from Samsung has arrived. Yesterday at Galaxy Unpacked, Samsung introduced the new Galaxy Z Fold7, Galaxy Z Flip7, and Galaxy Watch8 series. For Android developers, these devices represent an exciting new opportunity to create engaging and adaptive experiences that reach even more users on their favorite screens.
With new advancements in adaptive development and the launch of Wear OS 6, it has never been a better time to build for the expanding Android device ecosystem. Learn more about what these new devices mean for you and how you can get started.
The launch of the Galaxy Z Fold7 and Z Flip7 on Android 16 means users are about to experience your app in more dynamic and versatile ways than before. This creates an opportunity to captivate them with experiences that adaptively respond to every fold and flip. And preparing your app for these features is easier than you think. Building adaptive apps isn’t just about rewriting your code, but about making strategic enhancements that ensure a seamless experience across screens.
Google and Samsung have collaborated to bring a more seamless and powerful desktop windowing experience to large screen devices and phones with connected displays in Android 16 across the Android ecosystem. These advancements will enhance Samsung DeX, starting with the new Galaxy Z Fold7 and Z Flip7, and also extend to the wider Android ecosystem.
To help you meet this moment, we’ve built a foundation of development tools to simplify creating compelling adaptive experiences. Create adaptive layouts that reflow automatically with the Compose Adaptive Layouts library and guide users seamlessly across panes with Jetpack Navigation 3. Make smarter top-level layout decisions using the newly expanded Window Size Classes. Then, iterate and validate your design in Android Studio, from visualizing your UI with Compose Previews to generating robust tests with natural language using Journeys with Gemini.
The next chapter for wearables begins with the new Samsung Galaxy Watch8 series becoming the first device to feature Wear OS 6, the most power-efficient version of our wearable platform yet. This update is focused on giving you the tools to create more personal experiences without compromising on battery life. With version 4 of the Watch Face Format, you can unlock new creative possibilities like letting users customize their watch faces by selecting their own photos or adding fluid transitions to the display. And, to give you more flexibility in distribution, the Watch Face Push API allows you to create and manage your own watch face marketplace.
Beyond the watch face, you can provide a streamlined experience to users by embracing an improved always-on display and adding passkey support to your app with the Credential Manager API, which is now available on Wear OS.
Check out the latest changes to get started and test your app for compatibility using the Wear OS 6 emulator.
With these new devices from Samsung, there are more reasons than ever to build experiences that excite users on their favorite Android screens. From building fully adaptive apps for foldables to creating more personal experiences on Wear OS, the tools are in your hands to create for the future of Android.
Explore all the resources you’ll need to build adaptive experiences at developer.android.com/adaptive-apps. And, start building for Wear OS today by checking out developer.android.com/wear and visiting the Wear OS gallery for inspiration.
Google Ads API v18 will sunset on August 20, 2025. Starting on this date, all v18 API requests will begin to fail. Migrate to a newer version prior to August 20, 2025 to ensure your API access is unaffected.
Here are some resources to help you with the migration:
You can view a list of methods and services your project has recently called using the Google Cloud Console:
Posted by Mayank Jain – Product Manager and Jomo Fisher – Software Engineer
Posted by Dan Galpin – Android Developer Relations
Posted by J. Eason – Director, Product Management
google.ads.googleads.v18.services.GoogleAdsService.Mutate.
If you have questions while you’re upgrading, reach out to us on the forum or at [email protected].
Benji Rothman, Google Ads API Team
Tens of millions of videos have been generated in Flow, our AI tool for filmmakers since launching in May.To help get the most out of Flow, starting this week, you can a…
You can now use Veo 3 to create video clips from photos you upload in the Gemini app.
 |
| Searching for Lucid documents in Chat spaces |