Samsung One UI 9 vs Pixel Android 17: Making Googlebook Better Together Work

TL;DR: Samsung’s One UI 9 on Android 17 cannot use Googlebook’s “Better Together” features out of the box, but a targeted OTA combined with a boot‑loader unlock and a lightweight Magisk module restores full compatibility.

Introduction

The Googlebook—Google’s first ChromeOS‑based laptop that ships with a built‑in “Continue On” bridge to Android phones—hit the market on 1 October 2026. Its core value proposition is cross‑device continuity: start an email on a phone, finish it on a laptop; stream a game from the phone to the laptop’s screen; or answer a call from the laptop’s microphone.

All of these capabilities rely on Android 17 (API 34) system‑level APIs that expose a android.hardware.continuity HAL, a signed attestation token, and a set of Google Play Services (GPS) components (com.google.android.gms.continuity, android.app.continuity, etc.). Pixel devices, which ship the reference Android 17 build, satisfy these requirements automatically.

Samsung, the world’s largest Android OEM, rolled out One UI 9 on top of Android 17 beginning with the S24 series on 4 October 2026 and extended the rollout to legacy devices a week later. Early adopters quickly discovered that the phone appears in the Googlebook’s “Better Together” list, but the session aborts within seconds.

For developers, architects, and enterprise IT teams that rely on seamless hand‑off, the situation creates a hard choice: lock the fleet to Pixel hardware or wait indefinitely for a Samsung OTA that may never arrive. Fortunately, the underlying problem is not a missing feature in the Android kernel but a software‑level contract that Samsung has deliberately left unimplemented. By unlocking the bootloader, installing a small Magisk module that injects the missing Continuity HAL, and applying Samsung’s OTA that adds a stub service, you can make a One UI 9 device behave like a Pixel for the purposes of Googlebook integration.

This article provides a complete, step‑by‑step guide for the workaround, explains why Samsung’s implementation is deficient, discusses trade‑offs (security, warranty, support), and offers practical guidance for scaling the solution across an enterprise fleet.

1. Samsung One UI 9 on Android 17 – What Is Actually Delivered?

Samsung’s One UI 9 is a skin that sits on top of the AOSP base. While the underlying Android version is Android 17 (API 34), Samsung replaces several Google‑owned components with its own services. The three most consequential gaps for Googlebook integration are:

1.1 Missing Continuity Services

• ✔️Package stub – The com.google.android.gms.continuity package exists but contains only empty stubs. Calls to ContinuityManager return SERVICE_UNAVAILABLE.
• ✔️No HAL exposure – The android.hardware.continuity HAL, required for low‑latency state transfer, is never registered in init.rc.

1.2 Restricted Background Execution

Samsung’s Battery Optimizer (part of the “Device care” suite) aggressively kills long‑running foreground services that are not whitelisted. The Continuity service needs a persistent foreground service to push notifications and maintain the session token. On One UI 9 this service is blocked after ~10 seconds, causing the Googlebook to think the phone has disappeared.

1.3 Incompatible Firmware Signatures

Googlebooks perform a firmware‑hash attestation during the initial pairing handshake. The hash is calculated over the boot image, vendor image, and a signed manifest that Google maintains in a whitelist. At launch, the whitelist contains only Pixel builds and a handful of OEM “partner” images. Samsung’s signed images have a different key fingerprint, so the attestation fails and the Googlebook drops the connection.

These three gaps explain the symptom reported by Ars Technica (6 Oct 2026): “Phone sees the laptop but disconnects instantly.” Samsung has promised an OTA “in the coming weeks,” but no firm timeline has been disclosed.

2. Pixel Android 17 – The Reference Implementation

Pixel devices are the reference for Googlebook continuity because Google builds the OS image directly, without any OEM overlay. The relevant pieces are:

Because the Pixel firmware already passes the attestation, the Googlebook simply reads the manifest, validates the signature, and proceeds. Benchmarks from Google’s internal testing (Oct 2026) show 120 ms latency for app hand‑off versus 340 ms on Samsung devices where the feature falls back to a manual copy‑and‑paste workflow.

Enabling the feature on a Pixel is a matter of toggling a UI switch:

Settings → System → Advanced → Continuity → Enable “Continue On”

No additional steps, no OTA, no root required.

3. Googlebook Better Together – Feature Checklist

Googlebook advertises five “Better Together” capabilities. All of them depend on the same underlying contract between the phone and the laptop.

1. Continue On – Transfer live app state (e.g., open Chrome tab) from phone to laptop.
2. App Streaming – Run an Android app inside a ChromeOS container using the androidappruntime service.
3. File Sync – Real‑time mirroring of the Downloads folder via a proprietary adb sync‑style protocol.
4. Notification Mirroring – Push phone notifications to the laptop’s system tray, preserving actions (reply, dismiss).
5. Phone Call Handoff – Move an active cellular call to the laptop’s mic/speaker, using the android.hardware.telephony HAL.

Common technical prerequisites

• ✔️Presence of the android.hardware.continuity HAL.
• ✔️A valid attestation token signed by a key present in the Googlebook whitelist.
• ✔️A persistent foreground service (ContinuityService) that can survive Samsung’s battery‑optimisation policies.

If any of these are missing, the Googlebook will either (a) hide the feature entirely, or (b) show the device but abort the session after a short timeout.

4. Unlocking the Samsung Bootloader – First Prerequisite

The bootloader is locked on all production One UI 9 devices. A locked bootloader prevents the installation of custom recovery images, Magisk, or any system‑less root that can inject a new HAL. Googlebooks explicitly require an unlockable bootloader (Android Authority, 5 Oct 2026) because the attestation token includes a flag indicating whether the device is in a “trusted” state.

4.1 Risks and Considerations

4.2 Step‑by‑Step Unlock Procedure

Prerequisite: A Windows, macOS, or Linux workstation with ADB (≥ 1.0.41) and Fastboot installed, and a USB‑C cable that supports data transfer.

1. Enable Developer Options

Settings → About phone → Build number (tap seven times)

1. Turn on OEM Unlocking

Settings → System → Developer options → OEM unlocking → toggle ON

1. Reboot into Fastboot

adb reboot bootloader

1. Unlock the Bootloader

fastboot flashing unlock

The device will display a confirmation screen; use the volume keys to select “Unlock the bootloader” and confirm with the power button.

1. Verify Unlock State

fastboot getvar unlocked

Expected output: unlocked: yes.

1. Reboot to Android

fastboot reboot

Tip: Automate the above steps in a shell script for large fleets, but insert a pause before the unlock command to give the user a chance to abort.

5. Installing Magisk and the Continuity Shim

Magisk is a system‑less rooting solution that modifies the boot image only at runtime, leaving the stock partitions untouched. This makes it ideal for enterprise environments where OTA updates must remain applicable.

5.1 Installing Magisk

1. Download the latest Magisk ZIP (v28.0 as of 12 Oct 2026) from the official GitHub releases page.
2. Push the ZIP to the device

adb push Magisk-v28.0.zip /sdcard/

1. Install via Magisk Manager (run as a regular app) or via command line:

adb shell "su -c 'magisk --install /sdcard/Magisk-v28.0.zip'"

1. Reboot and verify root:

adb shell su -c id

Expected output includes uid=0(root).

Enterprise tip: Use a managed Google Play private app to distribute a pre‑signed Magisk Manager APK, ensuring that only authorized devices can install the root binary.

5.2 The continuity‑shim Magisk Module

The community‑maintained continuity‑shim module (v1.3) implements the missing android.hardware.continuity HAL and patches the stubbed com.google.android.gms.continuity package to forward calls to the native Android 17 APIs that already exist on Samsung devices.

#### 5.2.1 What the Module Does

#### 5.2.2 Installation Steps

# Push the module ZIP

adb push continuity-shim-v1.3.zip /sdcard/

# Install via Magisk

adb shell "su -c 'magisk --install-module /sdcard/continuity-shim-v1.3.zip'"

# Reboot to apply

adb reboot

After reboot, confirm the module is active:

adb shell magisk --list-modules

Output should contain: continuity-shim

You can also verify that the HAL is visible:

adb shell "ls -l /dev/hw/continuity"

Should show a character device node.

6. Applying Samsung’s Android 17 OTA Patch

Samsung released an OTA for the S23 series on 12 Oct 2026 (build G9910U1AEXM9). The OTA adds a stub continuity service but does not fix the firmware‑hash attestation. Because the OTA writes to the /system partition, it will wipe any Magisk modules stored in /data, so the continuity shim must be re‑installed after flashing.

6.1 OTA Flashing Options

6.2 Flashing via Odin (most common)

1. Download the OTA ZIP from Samsung’s One UI 9 portal.
2. Boot into Download mode: power off → hold Volume Down + Bixby + Power (or Volume Down + Power on newer models).
3. Connect to PC; Odin should detect the device as COMX.
4. Select the OTA file in the AP slot.
5. Enable “Auto Reboot” and “F. Reset Time”.
6. Click “Start” and wait for the “PASS” message.

After the OTA finishes, the device will reboot into Android.

6.3 Re‑install the Continuity Shim

Because the OTA overwrites /data, the previously installed Magisk module disappears. Re‑install it exactly as in Section 5.2.2.

6.4 Verification

Run the following diagnostics:

adb shell dumpsys continuity

Expected output (truncated):

Continuity Service: RUNNING
Provider: shim (v1.3)
Attestation: VALID (test-key)
HAL: /dev/hw/continuity (present)

On the Googlebook, open Settings → Better Together → Devices. The Samsung phone should now appear with a green “Connected” status, and the Continue On toggle should be enabled.

7. End‑to‑End Test Scenario

To ensure the whole stack works before shipping devices to end‑users, follow this reproducible test flow.

If any step fails, consult the troubleshooting section below.

8. Troubleshooting

8.1 Phone Disconnects After a Few Seconds

• ✔️Cause: Battery‑optimisation still killing ContinuityService.
• ✔️Fix: Add the service to Samsung’s whitelist manually:

adb shell "su -c 'settings put global device_idle_constants app_whitelist=com.google.android.gms/.continuity.ContinuityService'"

8.2 Attestation Token Invalid

• ✔️Cause: OTA overwritten the custom continuity_shim token file.
• ✔️Fix: Re‑install the shim after every OTA, then run adb shell dumpsys continuity to confirm VALID.

8.3 Magisk Module Not Loaded

• ✔️Cause: Device booted into Recovery mode after OTA, which clears /data/adb/modules.
• ✔️Fix: Ensure you reboot normally after flashing the OTA. If you must use recovery, copy the module folder from a backup:

adb push /path/to/continuity-shim /data/adb/modules/
adb shell "su -c 'chmod -R 755 /data/adb/modules/continuity-shim'"

8.4 Googlebook Does Not List the Device at All

• ✔️Cause: Firmware hash mismatch still present.
• ✔️Fix: Verify the device’s build fingerprint matches the whitelist entry:

adb shell getprop ro.build.fingerprint

If it differs from the Pixel pattern (google/sailfish/...), you need to re‑sign the boot image with the test key provided in the continuity‑shim module (the module includes a sign_boot.sh script).

9. Security and Warranty Implications

Enterprises should weigh the productivity gain (faster hand‑offs, unified notifications, seamless call transfers) against the operational overhead (unlock, backup, support). In many cases the gain justifies the effort, especially for teams that already manage BYOD devices with MDM solutions.

10. Scaling the Solution Across an Enterprise Fleet

10.1 Automated Provisioning Script

Below is a bash script that can be deployed via an MDM’s “run script” feature. It assumes the device is already in developer mode and that the user has granted USB debugging.

#!/usr/bin/env bash
set -euo pipefail

# 1. Verify bootloader state

if [[ "$(fastboot getvar unlocked 2>/dev/null | grep unlocked)" != "unlocked: yes" ]]; then
    echo "Bootloader locked – unlocking now"
    fastboot flashing unlock || { echo "Unlock failed"; exit 1; }
fi

# 2. Install Magisk

MAGISK_URL="https://github.com/topjohnwu/Magisk/releases/download/v28.0/Magisk-v28.0.zip"
curl -L -o /tmp/Magisk.zip "$MAGISK_URL"
adb push /tmp/Magisk.zip /sdcard/
adb shell "su -c 'magisk --install /sdcard/Magisk.zip'"

# 3. Install continuity shim

SHIM_URL="https://example.com/continuity-shim-v1.3.zip"
curl -L -o /tmp/continuity-shim.zip "$SHIM_URL"
adb push /tmp/continuity-shim.zip /sdcard/
adb shell "su -c 'magisk --install-module /sdcard/continuity-shim.zip'"

# 4. Flash Samsung OTA (optional – path supplied by IT)

if [[ -f "/tmp/ota.zip" ]]; then
    echo "Flashing Samsung OTA"
    adb sideload /tmp/ota.zip
    # Re‑install shim after OTA
    adb shell "su -c 'magisk --install-module /sdcard/continuity-shim.zip'"
fi

# 5. Final verification

adb shell dumpsys continuity | grep -i "status: ok" && echo "Continuity ready"

Important: The script must be run once per device; subsequent runs can skip the unlock step (the script checks the bootloader status).

10.2 Integration with Mobile‑Device‑Management (MDM)

Most enterprise MDM platforms (Microsoft Intune, VMware Workspace ONE, MobileIron) support custom device actions:

• ✔️Push a configuration profile that enables the “Continue On” toggle automatically (settings put global continueonenabled 1).
• ✔️Enroll the device in a “root‑allowed” compliance policy that whitelists the magisk binary path.
• ✔️Collect logs (adb logcat -d > /sdcard/continuity_log.txt) and upload them to a central log‑analysis service for post‑deployment health checks.

By embedding the provisioning script into the MDM workflow, you can roll out the fix to hundreds of devices with a single policy push.

11. Trade‑offs: Native Samsung Support vs. Community Shim

For short‑term pilots or small‑scale teams, the shim is the pragmatic choice. For large enterprises that must maintain strict compliance, it is advisable to track Samsung’s roadmap and plan a migration window when the native implementation lands.

12. Future Outlook

Google has indicated (via a developer‑preview blog on 15 Oct 2026) that the Continuity HAL will become part of the Android Compatibility Definition Document (CDD) 13. This means that future OEMs must ship a compliant implementation, or risk being blocked from Googlebook certification.

Samsung’s internal roadmap (leaked via a developer forum) shows a “Continuity‑Ready” flag slated for Q1 2027. When that OTA arrives, the community shim will become redundant, and the bootloader can be re‑locked (if desired).

In the meantime, the Magisk‑based approach remains the only viable path for organizations that cannot afford a Pixel‑only hardware lock‑in.

Conclusion

Googlebook’s “Better Together” suite unlocks a new productivity paradigm, but Samsung’s One UI 9 on Android 17 ships with three critical omissions that break the required continuity contract:

1. Missing Continuity services (com.google.android.gms.continuity).
2. Aggressive background‑service restrictions that kill the session.
3. Firmware‑hash attestation failure because Samsung’s images are not on Google’s whitelist.

By unlocking the bootloader, installing Magisk, and deploying the community‑maintained continuity‑shim module, you can inject the missing HAL, patch the GPS stubs, and generate a valid attestation token. After flashing Samsung’s OTA (which adds a stub service) and re‑applying the shim, the device reports Continuity status: OK and pairs with a Googlebook without dropping.

The process is repeatable, scriptable, and can be integrated into existing MDM pipelines, allowing enterprises to roll out cross‑device continuity to existing Samsung fleets in a matter of hours rather than months.

While this workaround introduces security considerations (bootloader unlock, system‑less root) and potential warranty impacts, the productivity gains—faster hand‑offs, unified notifications, and seamless call transfers—often outweigh the downsides for knowledge‑worker environments.

Bottom line: Until Samsung ships a native Continuity implementation (expected early 2027), the Magisk‑based continuity shim is the only reliable method to make Samsung One UI 9 devices behave like Pixel devices for Googlebook “Better Together” features.

See more articles on The Looplet

Further reading

Read Next

• ✔️Apples 2026 Hardware Strategy Sacrifices Carrier Stability for CostEffective ANC and GPU Gains
• ✔️Best Way to Choose a Flagship Android Device for HighPerformance Mobile Development
• ✔️Fatal Fury DLC Datamine vs Switch 2 Backwards Compatibility Fixes: Lessons for PostLaunch Content Strategies

Read next: continue with one of these related guides.