Microsoft's Surface Duo 2 has become the subject of an unusual operating-system experiment: iOS 26 running across its two screens. In an October 27 report, Windows Latest describes developer SmuOS, also known as None24, booting Apple's software on the discontinued Android handset and getting both displays and touch input working.
For Surface enthusiasts, this is an interesting community-development story. For anyone hoping to turn an old Duo into a dependable iPhone, the practical conclusion is more cautious. A successful boot is not a support lifecycle. The reported build remains an experiment, with substantial questions around hardware compatibility, everyday usability, and security.
What the developer reportedly demonstrated
Windows Latest's Abhijith M B reports that the test device displays iOS 26.5.2 and identifies itself in Settings as an iPhone 17 Pro Max. The publication describes photos supplied by the developer showing Settings and the Phone app spread across the Duo 2's displays.
That identification should not be confused with certification or official Apple support. It is information presented by the experimental software, not evidence that Microsoft's hardware has acquired the capabilities of the Apple device it names.
The report also describes rapid progress: an initial boot with one working display, followed by both displays and touch support. The developer claims display performance improved to 37 frames per second. That figure is a reported development milestone, not an independently measured benchmark or a guarantee of smooth performance in applications.
QloudBlog has not independently tested the port. The technical implementation and progress described here are attributed to the Windows Latest report and its developer interview.
Why this is more complicated than installing another OS
According to the report, the project combines Apple's open-source XNU kernel, a custom UEFI loader, and work associated with UniXNU, a project intended to bring Apple's operating systems to non-Apple ARM64 hardware.
Sharing an ARM architecture does not make two devices interchangeable. The operating system still needs appropriate drivers, a compatible graphics path, and support for the particular hardware surrounding the processor. Booting a kernel is only one part of that job.
Graphics are a major obstacle in this account. The Duo 2 uses Qualcomm hardware with an Adreno GPU, whereas iOS software expects Apple's graphics environment. Windows Latest describes a Metal-to-Vulkan translation approach using the open-source Turnip driver. The developer identifies the graphics stack, rather than simply starting the kernel, as a particularly difficult part of the work.
The article also describes changes to accommodate Apple's arm64e software assumptions. These are deep compatibility modifications, not routine settings adjustments. Their existence is another reason not to assume that the experimental system preserves the behavior or security properties of a supported iPhone.
Two working screens do not guarantee usable applications
The most revealing limitation is the hinge. In the reported Phone app demonstration, the interface treats the displays as one continuous area. Parts of the keypad and call button consequently land in the gap between them.
That is a useful distinction for anyone evaluating dual-screen software: rendering across both panels is different from understanding that the panels are physically separated. A usable implementation needs to position important controls where people can actually see and touch them.
Windows Latest also describes graphics artifacts, a black wallpaper, and unavailable Wi-Fi and Bluetooth identifiers in Settings. Those observations do not provide a complete compatibility matrix, but they clearly argue against treating the screenshots as proof of a finished phone.
Likewise, opening the Phone app does not demonstrate working cellular calls. The report does not establish dependable telephony, battery life, camera support, account services, or compatibility with the applications an owner might need every day.
Practical advice for Surface Duo owners
For now, follow this as a research project rather than an upgrade recommendation. The source says Apple's firmware files are not redistributed with the project, so this is not presented as a simple downloadable image that ordinary owners can flash and forget.
If you are experienced with experimental firmware and decide to investigate, use a spare device with no important data. Before changing anything, establish whether a documented recovery process exists for your exact model and whether you have the required files and tools. Do not assume a guide for the original Surface Duo applies to the Duo 2.
Keep primary accounts, payment applications, and work credentials off an unvalidated build. Also distinguish the availability of source code for individual components from permission to redistribute an entire operating system; Apple's firmware is not made open source merely because XNU is available.
For IT administrators, this does not create a new supported endpoint option. A demonstration cannot substitute for verified patch delivery, device-management compatibility, encryption behavior, and a recoverable deployment process. No fleet decision should depend on the device name displayed in Settings.
What would make the project more useful?
The next meaningful evidence would be reproducible build instructions, a detailed hardware-support matrix, independent testing, and clear recovery documentation. Hinge-aware layouts and reliable connectivity would matter more to most owners than another impressive screenshot.
Windows Latest reports that the developer wants to explore Surface Pen compatibility and a newer iOS build. Those are development intentions, not delivered features. The project is worth watching for its technical ambition, but owners should keep the distinction between experimental achievement and dependable device reuse firmly in view.