Checked 14 September 2026
Updated September 2026 · first publication, carrying the 2011 and 2012 Sony, Samsung and Three stories that send readers here
Two things decide when a new Android version reaches your phone: whether the maker still promises one for that model, and whether anything sits between the maker and your handset. In the United Kingdom that second thing is the network, and a news post of 13 March 2012 complained that Orange, O2 and others could hold an update up for six months. This page covers where the window is published, how to read what your own phone runs, what the network step is in 2026, and why a leaked build is the one route that cannot be undone. The blunt part: nothing here makes an update arrive sooner.
Sent here by a 2012 post about the Xperia arc S and Jelly Bean? The Sony decision. By the 2011 Galaxy Ace on Three, or the March 2012 Galaxy S II date? Unlocked against network. By the January 2012 leaked Ice Cream Sandwich build? Leaks and the official beta. Our answer and the table ↓
Waiting is our answer inside a published window, because Google’s Pixel update page, read 14 September 2026, gives Pixel 8 and later seven years and Pixel 6 and 7 five years, and says that covers operating system and security updates. Samsung’s figure is a different claim: its security site, read the same day, extends security update support to up to seven years for Galaxy models added since January 2024 and publishes no Android version window.
Reading your own build is our answer when a phone looks skipped, because Samsung’s United Kingdom support page, read 14 September 2026, says Software updates are released at different stages, depending on your location and mobile carrier
.
Leaving it alone is our answer to a leaked build on a Samsung, because Samsung’s Knox documentation, read 14 September 2026, says There is no way to revert the Warranty Bit and Knox won’t work on this device
.
Data checked: 14 September 2026.
The version window comes from Google’s Pixel update page and the security update window from Samsung’s mobile security site, which are not the same claim; menu paths from Google’s and Samsung’s United Kingdom support pages; the Knox consequences from Samsung Knox documentation; the history from archived copies of the original posts. Nothing rests on our own use of a beta, a leak or a custom build.
Start with the published window
A major version is a promise made when the phone was sold, and the two large sellers here publish very different things. Google’s page says Pixel 8 and later phones will get updates for 7 years starting from when the device first became available on the Google Store in the US
and that this includes 7 years of OS and security updates
, puts Pixel 6, 6a, 6 Pro, 7, 7a, 7 Pro and Pixel Fold at five years, and lists Pixel 5a and older as no longer receiving Android version or security updates (Google’s Pixel update page, read 14 September 2026). Samsung’s security site says that as of January 2024 it is extending security update support for Galaxy devices by up to seven years, and sorts current models into monthly, quarterly and biannual lists; that is a patch window and not a version window, and the page’s only word on versions is footnote 1, Availability and timing of Android OS upgrades and security updates may vary by market, network provider and/or model
(Samsung Mobile Security, read 14 September 2026). So one of the two publishes a version promise and the other does not.
For any other make there is a rule rather than a habit: government guidance says the consumer connectable product security regime came into effect on 29 April 2024 and requires manufacturers to publish information on minimum security update periods (the guidance itself, read 14 September 2026), so look for that period before you look at a forum. Our United Kingdom buying guide goes further. Google’s developer site listed Android 17 at the head of its released versions (the release list, read 14 September 2026), so a phone on Android 15 is two behind, not one. The blunt part: a published window binds the maker, not the network that sold you the handset.
The decision that ends a model
If you arrived from a July 2012 post headed No Jelly Bean for the Arc S or other 2011 Xperia phones
, this is that story. A United Kingdom news post of late July 2012 reported Sony Mobile saying in a Facebook question and answer session that the Xperia arc S would not be updated to Android 4.1 Jelly Bean, and that because the arc S was the highest specified 2011 Xperia, the Ray, the mini, the mini pro and the Neo V would not get it either.
The same blog followed up on 31 July 2012 under the heading 2011 Xperia handsets to get Jelly Bean after all?
, reporting that Sony had said on its developer blog that the earlier information was given out in error and that it was looking into Android 4.1 for some phones, without saying which (archived copy, read 14 September 2026). That lasted until 19 October 2012, when the blog reported Sony confirming the refusal for the 2011 handsets while naming the Xperia acro S, ion, P, go, J and T for Jelly Bean in the first quarter of 2013 (archived copy, read 14 September 2026).
So the arc S ended on Ice Cream Sandwich. Wikipedia’s entry for the phone says it was updated to Android 4.0.3 Ice Cream Sandwich in January 2012 and updated to Android 4.0.4 in May 2012
, while its specification box gives it as officially upgradeable up to Android 4.0.3 (the Wikipedia entry, read 14 September 2026). The reasoning belonged to 2012: the October 2012 post itself argued that with the arc S being the highest specified of the 2011 Xperia phones, if it was not seeing Jelly Bean the others would follow suit. This page found no current maker statement that ties the models of a range together in that way. What to do with a phone in that position is in what to do when the updates stop.
Unlocked against network
Two more posts send readers here. One of 28 July 2011 reported that Three had begun pushing Android 2.3 Gingerbread to Samsung Galaxy Ace handsets bought through Three, announced in a tweet; the report that linked it the same day said Three have just pushed out Android 2.3 for Samsung Galaxy Ace users
(Coolsmartphone, read 14 September 2026). Bought through Three meant a build the network handled and released to its own customers, which is why the announcement came from the network rather than from Samsung. One of 13 March 2012, by Chris Spackman, relayed a Samsung United Kingdom statement that Android 4.0 Ice Cream Sandwich would reach the Galaxy S II from the week beginning 19 March 2012, with availability in the United Kingdom dependent upon each network’s own software approvals process
, said unlocked phones would be first while Three was already testing, and complained that Orange, O2 and others could hold it up for six months (archived copy, read 14 September 2026). A phone bought from a United Kingdom network still meets that division of labour in 2026: the maker builds it, the network’s stage decides when it lands, and the carrier code on the handset tells you which queue you are in.
Two of those four names have gone. Orange’s own site states that in 2015 Orange and Deutsche Telekom sold their participations in EE to BT and that all Orange United Kingdom customers became EE customers (orange.co.uk, read 14 September 2026). Vodafone and Three are one company: the merger of Vodafone UK and Three UK successfully completed on 31 May 2025
, says Vodafone’s release, which names the combined business VodafoneThree (Vodafone’s own release, read 14 September 2026); both consumer sites still answered separately when requested on 14 September 2026.
The staging itself has not gone. Samsung’s United Kingdom support page says Software updates are released at different stages, depending on your location and mobile carrier
(Samsung UK support, read 14 September 2026). The blunt part: this page looked for a first-party figure for how far a network build now trails a SIM-free one and found none, so it gives no number, and anything that puts a week on it is observation rather than a commitment. What the network apps can settle is in our guide to the United Kingdom network apps.
Read your own build first
Before deciding you have been skipped, read what the phone runs. Google gives Settings, then About phone, then Android version, and says Update schedules vary by device, manufacturer, and mobile carrier
(Google’s own page, read 14 September 2026). Samsung’s United Kingdom page gives Settings, then About phone or About device, then Software information for the version, and Settings, then Software update, then Download and install for the check, with Download updates manually on Android 7 and 8. The line headed Service provider software version carries the region and carrier code, the CSC. An explainer published 8 March 2026 and updated 20 April 2026 calls a CSC a Country Specific Code, which identifies the region or carrier associated with a Samsung device
and says updates go out gradually by CSC (SammyGuru, read 14 September 2026); that is an explainer, not a Samsung statement.
If the phone offers nothing, a computer is the second route. Samsung’s United Kingdom Smart Switch page says the desktop version can Prompt you to update your device’s software and display options for updates
(Samsung UK Smart Switch, read 14 September 2026). Smart Switch is the tool Samsung names in 2026; Kies belongs to the era of the posts above.
That prompt is a function of the desktop version. The phone app of the same name is a separate listing: Samsung Smart Switch Mobile · Rating 3.8 from 531,091 reviews on the United Kingdom Google Play storefront, read 14 September 2026 · Installs 1,000,000,000+ · Free to install · No in-app purchases listed · Developer Samsung Electronics Co., Ltd. · Listing updated 3 September 2026 · Contains ads: No
Google Play listing · 3.8 (531,091) on the United Kingdom storefront · read 14 September 2026
The walkthrough for installing what you are offered, and the difference between the Android version, the security patch and the Google Play system update, lives in how to update your Android version.
The route that cannot be undone
Read the warning before the history. On a modern Samsung, loading unofficial firmware trips a hardware flag: Samsung’s Knox documentation says the warranty bit detects if a non-Knox kernel has been loaded on the device
, that There is no way to revert the Warranty Bit and Knox won’t work on this device
, and that Samsung Pay, Secure Folder and Samsung E-FOTA stop working once it is tripped (Samsung Knox documentation, read 14 September 2026). Back the phone up before going near any of this; our guide to backing up an Android phone covers what to include.
The three routes are not interchangeable. A leak is official firmware that escaped early: Samsung code with no support and no clean way back. A custom build is somebody else’s, and generally needs an unlocked bootloader, the same trip wire; the tooling is in our round-up of root apps. The official beta is neither: Samsung calls the One UI Beta owned, managed, and operated solely by Samsung
, lists the United Kingdom among the countries where it is open, has you register in the Samsung Members app, and says Before installing beta software, it is highly recommended to back up your data to your computer with Smart Switch
(Samsung’s One UI Beta page, read 14 September 2026). It is the only one of the three Samsung will take back.
The history that sends readers here shows the cost. A post of 2 January 2012, headed Ice Cream Sandwich ROM leaked for the Galaxy S II
(the blog’s archived tag page, read 14 September 2026), covered an unofficial Android 4.0.3 build that appeared ahead of Samsung’s own update. Its body was not recovered, but in the forum thread that linked it, posting between 2 and 4 January 2012, users reported the SD card refusing to mount, ClockworkMod recovery not working, apps closing on their own and Kies no longer offering updates; that thread was read 13 September 2026 and answered HTTP 403 on 14 September 2026, so its reading stays at the earlier date. The blunt part: those symptoms were recoverable in 2012 and the modern equivalent is not, because the Knox flag is a fuse rather than a setting.
Going back to stock
Going back to stock means writing the official firmware for your exact model number and your own region code over whatever is there, from a computer, which erases the phone. Take the backup first and read the model number from the Software information screen, because firmware built for another region is the usual cause of a handset that flashes cleanly and then loses its network features. A normal result is that Settings, then Software update offers the official build again once the phone is back on its own region firmware.
Samsung’s United Kingdom Smart Switch page, read 14 September 2026, documents backing up, restoring and prompting for updates, and documents nothing about recovering a phone that will not start. What reflashing does not undo is the warranty bit: the Knox documentation quoted above says The only way to get the device back to its original settings is to replace the PBA (Printed Board Assembly) on the device; hardware replacement will be required
, so Secure Folder and Samsung Pay stay gone on that handset however clean the firmware is afterwards. That is the argument for waiting out a staged rollout instead of jumping it.
Look for the window the maker published, and check what kind of window it is. Google’s Pixel update page, read 14 September 2026, gives Pixel 8 and later seven years and Pixel 6 and Pixel 7 five years, and says that covers operating system and security updates. Samsung’s security site, read the same day, extends security update support to up to seven years for Galaxy models added since January 2024, but publishes no Android version window at all.
Because the rollout is staged. Samsung’s United Kingdom support page, read 14 September 2026, says software updates are released at different stages, depending on your location and mobile carrier. It puts no length on that, and neither does this page. Check by hand in Settings, then Software update, then Download and install.
Open Settings, tap About phone or About device, then tap Software information. The line headed Service provider software version carries the region and carrier code. The same screen shows the One UI version and the security patch date, which tells you whether the phone is behind on versions, on patches, or on both. Checked 14 September 2026.
No. A United Kingdom news post of late July 2012 reported Sony saying the arc S would not get Android 4.1, a follow-up of 31 July 2012 reported Sony calling that an error and looking at it again, and a post of 19 October 2012 reported Sony confirming the refusal for every 2011 Xperia. The arc S ended on Ice Cream Sandwich.
Treat it as one way. On a Samsung it trips the Knox warranty bit, and Samsung's own Knox documentation, read 14 September 2026, says there is no way to revert that bit and that Samsung Pay and Secure Folder stop working. Reflashing official firmware afterwards does not reset it, so the loss is permanent for that handset.
A leak is unreleased official firmware that escaped, carries no support and has no clean way back. The One UI Beta is run by Samsung, is open in the United Kingdom, is joined through the Samsung Members app, and can be reversed with the desktop version of Smart Switch. Samsung's beta page, read 14 September 2026, tells you to back up first.
Checked 14 September 2026: first publication. Every source behind a figure, a policy claim or a store listing was re-opened on 14 September 2026: the Pixel version window from Google’s Pixel update page; the security update window from Samsung’s mobile security site, which publishes no version window and is labelled here as a patch window only; menu paths from Google’s and Samsung’s United Kingdom support pages; the Knox consequences from Samsung Knox documentation; the beta terms from Samsung’s developer site; the Orange and VodafoneThree positions from orange.co.uk and Vodafone’s own release; the 2011 and 2012 history from archived copies of the original posts and from the Coolsmartphone report of 28 July 2011; and the Smart Switch Mobile listing from the United Kingdom Google Play storefront, where the review count read 531,091 against 530,935 in the 13 September draft. One source did not answer: the forum thread behind the January 2012 leak symptoms returned HTTP 403, so that reading is left dated 13 September 2026. Not carried, because no first-party source could be read: any figure for how far a United Kingdom network build trails a SIM-free one, and any claim that current Samsung firmware carries the network region codes in a single build.