Motorola's stable Android 17 reaches four US phones, including the Razr Ultra 2026

Two Edge 60 Pro phones from the same purchase order can sit on one desk, one showing Android 17 and the other reporting no update. Both are working as intended. Motorola is distributing the update in stages, with availability varying by region, carrier and device variant, according to TechRepublic. A phone on the rollout list does not mean every owner can download Android 17 immediately, the outlet notes ^[3].

Here's what teams tell themselves: once a model appears in a rollout report, the fleet is on Android 17. Here's what users actually see: whatever build has reached their own unit, and that depends on carrier and country as much as on the model ^[3].

The reported list is short. The rollout widened in early October ^[1], and PhoneArena counts four US models getting the stable build ^[2]. Motorola's reported compatibility list runs to more than 50 phones ^[6]. That puts fewer than 8 percent of eligible models on a reported US release ^[12]. Motorola has not provided a complete rollout schedule for every eligible phone ^[4].

Features split the same way. TechRepublic, working from Motorola's changelog, says not every listed feature is necessarily available on every phone that receives the update ^[10]. PhoneArena reports image processing changes on Edge 60 models and extra cover-screen widgets on the Razr Ultra (2026), and the exact changes may differ by device ^[11].

Sort each phone on two tests. The first is whether the model has a reported stable release in the country where the phone is used: one of PhoneArena's four in the US ^[2], or the Edge 60 Fusion and Edge 60 Pro in India, where the evidence is user reports ^[5]. The second is whether the planned change needs Android 17 itself or a named feature such as Tap to Share, Quick Drop or the Razr's AI Key shortcuts ^[9][8].

Reported release, version only: schedule it, and confirm the build on each unit before closing the ticket. Reported release, feature-dependent: test the feature on that exact model and build first ^[10]. No report, version only: treat the phone as staying on its current version until it says otherwise. No report, feature-dependent: leave it off the plan.

I'd hold any Android 17-specific workflow until every unit in scope reports the new build. The tradeoff is running two sets of support instructions, one per version, for as long as the staged rollout takes.

Phones from the models Android Authority found missing from the eligibility list sit outside both tests, and some of them already have software update commitments ^[7]. For those, eligibility is a question to put to Motorola before anyone writes a help desk script.