Android 17 for Business: What Changes and When

For a business that owns its phones, Android 17 changes less than the headlines suggest. The update reaches each phone when its manufacturer decides, so you will run a mixed fleet for months. Your job is to control when an offered update installs, test it on one or two phones first, keep the phones that won’t get Android 17 patched, and watch patch age rather than version numbers. The consumer features matter far less than those four things.

This guide covers what changes on company phones, when each brand is shipping it, how to stage it, what to do about the older phones, and a checklist you can run in about an hour for a fleet of 20.

What changes for company phones?

Very little in how they are managed. Company-owned devices are still managed through Android Enterprise, Google’s framework for business devices, in one of two set-ups.

Fully managed devices are general work phones used by one person. The company controls the whole device: screen lock, which apps are allowed, whether the camera works, whether files can be copied off over USB.

Dedicated devices do one job: a check-in tablet, a stock-scanning phone, a screen on the wall. These usually run in kiosk mode, locked to one app or a short list. If you run dedicated devices, there is a walkthrough in how to lock an Android tablet to one app.

What does change is the reporting underneath. Alongside the release, Google announced the stable AndroidX Security State Libraries, described as a unified view of device security for developers and enterprise partners. You will not see them on the phone. They give apps and management tools a more consistent way to ask a device how protected it is, which shows up in the quality of what your console reports.

For a small business the useful question stays simple: which of my phones are behind, and what should I do about it? In NounDesk that answer lives on the dashboard. Fleet health shows as Healthy, Needs attention or Critical, with the rules behind each status in plain English, and the patch age report shows how old each device’s security patch is.

When will company phones get Android 17?

It depends on the brand, the model and sometimes the carrier. There is no single date, and no Android MDM can make a manufacturer ship an update sooner.

Samsung. The rollout has come in stages, and the reporting reflects that. On September 16 Samsung announced the start of the Android 17 rollout with One UI 9 and confirmed an initial list of Galaxy devices. The update did not show up on phones straight away, and on September 22 9to5Google reported that Samsung had delayed its Android 17 update. Two days later it began reaching the Galaxy S26 in the US, starting with T-Mobile phones before unlocked ones, as a download of roughly 4GB. The stable release then reached the Galaxy S25, Z Fold 7 and Z Flip 7 in Korea, and by September 29 updates were rolling out for the Galaxy S26, S25 and more across more regions. So Samsung’s Android 17 is rolling out now, in stages, and timing still varies by model, region and carrier.

Motorola. The rollout just got another expansion to more phones.

Honor. Honor has confirmed which devices get its Android 17 update, which arrives as MagicOS 11 with a new visual style.

Nothing. Still at the beta stage. The Phone (4a) and (3a) Pro can now join the Android 17 open beta, with a stable build expected in early November.

Pixel. Google is still shipping test builds of the next quarterly release: QPR2 Beta 5 and then QPR2 Beta 6 this month.

“Initial list” is the phrase to notice in every announcement. Picture a plumbing company with fifteen Galaxy phones bought over three years. Only the newest few may be on Samsung’s first list, and the four Motorolas in the office may be offered Android 17 weeks before the older Samsungs. Nothing is wrong with either group. They are on different calendars.

So start with your own inventory. Open the Android versions report, export it to CSV and add a column for each manufacturer’s published list.

How to set the update schedule and stage the rollout

Two parties set your timing. The manufacturer decides when a device is offered the update. You decide, through the update schedule in your device policy, when an offered update installs.

In NounDesk the update schedule lives in your Security policy, next to screen lock and Play Protect. The question it answers is: when is it safe for this phone to restart and change? For most businesses, that means outside working hours. A delivery driver’s phone restarting mid-route is a real problem. The same restart at 2 a.m. on a charger is not. If your office staff and your night-shift warehouse team work different hours, give them different policies.

One honest limit: NounDesk has no “install update now” button. The schedule shapes timing on your side. The offer still comes from Samsung, Honor or whoever built the phone.

Staging means watching a small number of devices closely before you change anything fleet-wide. For a small fleet, two stages are enough.

Stage one: one or two test phones. Pick the first eligible devices that match real work. If your technicians use a job app and a Bluetooth headset, the test phone should too, and it should belong to someone patient who reports problems clearly. Put these phones in a group named something obvious like “Android 17 test” so they stand out on the dashboard.

Stage two: everyone else. Once the test phones have run a normal working week without trouble, raise any minimum app versions, tell staff what to expect and let the rest update as they are offered it.

Trouble means a business app that crashes or won’t sign in, a printer or card reader that stops pairing, or a kiosk tablet that no longer stays locked to its app. Bluetooth deserves its own test: after Android 17 QPR1, Pixel users reported Bluetooth volume control issues. That is one bug on one brand, but if a driver takes calls through a car kit, test that exact pairing.

Keep company phones out of beta programs too. Betas are for testers, not the phone your office manager uses to take bookings.

How to manage a mixed fleet and phones that won’t get Android 17

For months, some phones will be on Android 17 and some won’t. A few older models will never get it. That is normal. A mixed fleet nobody is watching is where the trouble starts.

Sort every phone into three piles in your exported report: already on 17, waiting, or not getting it. A cleaning company with 18 phones might find seven new Samsungs already updated, six mid-range phones waiting and five older handsets with no update coming. Check Last seen before drawing conclusions. A phone that has been Offline for a week still shows the version it had when it last checked in.

Read the version label on each setting. In NounDesk every policy setting shows the Android version it needs. If a setting needs a version only half your fleet runs, you have two honest choices: accept that it covers the newer half, or wait.

Watch patch age, not just the version. A phone on an older Android with last month’s patch is often safer than a newer one unpatched since spring. If a phone’s patch age keeps climbing month after month, it has stopped receiving fixes. Being one version behind is a note. Months without a patch is a problem.

Give older phones lower-risk jobs. A restaurant can move an older tablet from the manager’s office to the pass, running the kitchen order screen in kiosk mode. Take email with customer data, payment apps and shared drives off older phones first.

Retire on a rule. For example: replace a phone when its patch age has climbed for a few months, or when an app you depend on needs a newer build than the phone can run. Anything below Android 8 can’t be enrolled in NounDesk at all, so put those at the top of the list. If you are buying replacements (this month’s deal roundups included a Galaxy Z Fold 8 offer), enroll each by QR code with a saved enrollment profile so it lands in the right group with the right policy from the first minute. If an old handset is going to another employee instead, see how to wipe a company phone before giving it to a new employee.

Android 17 admin checklist

Run these before stage two. Most of it is reading reports you already have.

1. Know which devices will get it. The Android versions report, matched against each manufacturer’s list.
2. Run business apps for a working week on the test phone. Real jobs, real invoices.
3. Set minimum app versions for the few apps you can’t run without, such as scheduling, point of sale and delivery. When a vendor ships an Android 17 fix, raise the minimum so every device gets it through Managed Google Play, then check the app compliance view for devices below it.
4. Test Bluetooth accessories: headsets, car kits, card readers, label printers.
5. Check kiosk devices stay locked. Look at per-device kiosk health, then try the tablet yourself: press Home, try to reach settings, check volume lock and brightness.
6. Check policy settings against your oldest version, using the version label on each setting.
7. Preview every policy change. The publish preview lists exactly what changes and how many devices it affects. If you expect to touch six office phones and it says 23, you just learned the drivers share that policy. Change one setting per publish, and if a change is wrong, version history restores the previous version in one click.
8. Confirm the update schedule installs outside working hours.
9. Check the phones that won’t update are still getting patches.
10. Write down who staff call if an update breaks something: one name, one number, and what to report.

Then decide. Go if the test phone ran a clean week. Prepare one group if a single check failed: warn the drivers and give them a wired headset while the office phones carry on. Escalate if a business app you can’t work without is broken: tell the vendor now, because the manufacturer, not you, decides when the rest of the phones are offered the update.

What to watch in the weeks after it lands

Check three things each morning for the first week, then weekly.

Device status. A phone that took a major update and then went to Recently offline, or Offline for more than 24 hours, may need a hand. Call the person carrying it before assuming the worst.

App compliance. Required apps should still be installed and at or above your minimum version.

Alerts. Set an alert rule for devices that drop into Needs attention or Critical and turn on the email digest, so a phone that stopped checking in on Tuesday doesn’t go unnoticed until Friday. Device Trust also flags any phone whose security update is more than 90 days old. For more on reading these numbers, see how to keep company Android phones updated.

What to do this week

1. Export the Android versions report and mark each device: on 17, waiting, or not getting it.
2. Sort the patch age report oldest first and deal with the worst two devices before worrying about Android 17 at all.
3. Review the update schedule in each Security policy so updates install when devices are idle. Split policies if teams work different hours.
4. Create an “Android 17 test” group with one or two representative phones.
5. Set minimum versions on three business-critical apps and check app compliance the next day.
6. Set one alert rule for devices in Needs attention, and post the “who to call” note where every device holder will see it.

FAQ

Will all my company phones get Android 17 at the same time?

No. Each manufacturer releases it on its own schedule, and some older models won’t get it at all. Samsung’s rollout, for example, slipped after its September 16 announcement and then started reaching Galaxy phones in stages from September 24. Expect a mixed fleet for months.

Can an MDM push or force Android 17 onto my phones?

No. The manufacturer decides when a device is offered the update, and NounDesk has no “install update now” button. What device management gives you is the update schedule, which controls when an offered update installs, and visibility into which devices have updated.

Should I let Android 17 install on every company phone right away?

Not until one phone has proved it. Use the first one or two phones offered the update as test devices for a normal working week. If apps, accessories and kiosks behave, let the rest update as they are offered it.

Do I need to change my security policy for Android 17?

Probably not much. Review the update schedule and check whether any setting you rely on needs a particular Android version. In NounDesk each setting shows the version it needs, and the publish preview shows what changes before anything goes out.

What happens to phones that can’t update to Android 17?

They keep running their current version and stay managed as long as they are on Android 8 or later. Watch their patch age. When security patches stop arriving, plan the replacement.

Should company phones join the Android 17 beta?

No. Betas are for testing and change often. Keep work phones on stable releases so a beta bug doesn’t land on the device someone uses to serve customers.

Android 17 is mostly a scheduling problem for a small business, and a manageable one once you can see the whole fleet in one place. Try NounDesk free for 14 days and see every phone’s version and patch age on one screen.