TL;DR
- Google Play Services is building an “eSIM cloud transfer” flow that can prompt you straight from the lock screen — naming your carrier and your destination phone — to approve moving a SIM between devices.
- The wording makes the operation explicit: it’s a move, not a copy — once the transfer completes, the SIM stops working on the original phone.
- We found the strings in Google Play Services v26.23.34, pulled from a Pixel running the Android 17 QPR1 beta and diffed against the previous v26.22.33 build. It isn’t live yet, and like any work-in-progress code it could change or never ship.
Moving an eSIM from one phone to another is still one of the more awkward parts of switching Android devices — usually a trip through Settings, and in the worst case a phone call to your carrier. A teardown of the latest beta — Google Play Services v26.23.34, which we pulled straight off a Pixel and diffed against the previous v26.22.33 build — suggests Google is working to make that far simpler, with an approval prompt that can appear right on your lock screen.
Approve the transfer from your lock screen
The clearest piece of evidence is a lock-screen string, esim_cloud_transfer_lock_screen_description_with_carrier, which reads: “Unlock to transfer your [carrier] SIM to your other device. Once you transfer the SIM, it will no longer work on this device.” A second variant, ..._with_carrier_and_device, names the destination phone directly: “Unlock to transfer your [carrier] SIM to [device]…”
The placeholders for the carrier name and the destination device mean the interface is built to fill in your actual carrier and the specific phone you’re transferring to, dynamically — not a generic prompt. A companion “half sheet” string (esim_cloud_transfer_half_sheet_subtitle) — “After you transfer your SIM, it will no longer work on this device.” — points to a bottom-sheet confirmation step alongside the lock-screen prompt.
The phrasing repeated across all of these strings makes the direction of the operation explicit: this is a move, not a copy. Once the transfer completes, the SIM stops working on the original phone — which is exactly the behavior you’d want when retiring an old device.
The evidence
The new strings in Google Play Services v26.23.34:
esim_cloud_transfer_lock_screen_description_with_carrier =
"Unlock to transfer your %1$s SIM to your other device. Once you
transfer the SIM, it will no longer work on this device."
esim_cloud_transfer_lock_screen_description_with_carrier_and_device =
"Unlock to transfer your %1$s SIM to %2$s. Once you transfer the
SIM, it will no longer work on this device."
esim_cloud_transfer_half_sheet_subtitle =
"After you transfer your SIM, it will no longer work on this device."Why ‘cloud transfer’ matters
Google Play Services already underpins the existing “Transfer SIM from another device” option in Android’s setup flow, and earlier teardowns surfaced groundwork for backing up SIMs to the cloud. These new strings appear to extend that work toward a transfer that’s brokered through the cloud and approved with on-device authentication — bringing Android closer to the friction-free eSIM handoff that has been available between iPhones for some time.
Google hasn’t announced this flow, and the strings aren’t active in the shipping app yet. But a lock-screen, cloud-brokered eSIM transfer would smooth over one of the last rough edges in moving to a new Android phone. We’ll keep an eye on future betas and update if and when it surfaces.
