Windows 11 has been shown running directly on the OnePlus Open, turning a foldable Android handset into an experimental Windows device. According to Windows Latest's report by Mayank Parmar, developer Kevin Shroff installed the operating system on the phone's internal storage and removed Android from his test unit. This is a native boot, not a remote desktop session or Windows running inside an Android app.
The distinction matters, but so do the limitations. Touch input works, while Wi-Fi, GPU acceleration and several essential phone functions do not. For Windows enthusiasts, this is an interesting hardware-enablement project. For anyone considering a replacement for a daily-use phone or a managed Windows PC, it is not there yet.
What the OnePlus Open demonstration establishes
The reported achievement goes beyond displaying a Windows desktop on a phone screen. Windows boots as the primary operating system and can use the device's 16GB of RAM and all eight processor cores. Shroff also implemented touch input, allowing interaction with the desktop on the foldable's larger inner display.
He configured Windows at 300% display scaling and described the experience positively. That suggests the unfolded screen can accommodate a usable desktop interface, at least for this demonstration. It does not establish that every application, dialog box or touch target behaves well on the device.
Windows Latest explicitly says it has not independently benchmarked the installation. Claims that it feels responsive should therefore be treated as the developer's impressions, not evidence of laptop-equivalent performance. Booting successfully, responding to touch and completing everyday workloads reliably are separate milestones.
Why an ARM processor is not enough
Windows already has an ARM64 version, but a compatible processor architecture does not make an Android handset a supported Windows computer. The operating system still needs a way to discover the hardware, access its resources and communicate with device components.
The report describes custom UEFI firmware, device-specific ACPI work, and integration involving interrupts, memory mapping, power and drivers. In practical terms, this is the platform work that lets Windows move from its boot process to a functioning system on hardware originally built around Android.
Some existing Windows ARM64 components could be reused, including components for the processor, storage and USB. Touch required additional engineering to communicate with the phone's touch controller and deliver input to Windows.
That combination explains both the accomplishment and its limited portability. A working result on one model is not an installer for every Snapdragon handset. Different displays, controllers, firmware arrangements and peripheral components can require different solutions, even when devices share a processor family.
What still does not work
The missing features are substantial. Based on the state described in Windows Latest's report:
- Wi-Fi is not working. Firmware loads and some initial communication occurs, but that has not produced functional wireless networking.
- GPU acceleration is absent. The installation currently relies on framebuffer rendering rather than accelerated graphics.
- Cellular connectivity, Bluetooth, audio and cameras are not working. These gaps prevent it from serving as a normal smartphone.
- Dual boot has not been demonstrated. Android was wiped from the developer's test device.
- There is no ready-to-flash installation package. The project remains in development.
These are not merely missing conveniences. Networking affects access to services, updates and remote administration. Graphics acceleration can affect interface responsiveness and application behavior. Audio and cellular support are basic requirements for a device intended to replace a phone.
Battery life, sleep reliability, thermals and long-term update behavior also need evaluation before anyone could recommend such a system for routine use. The report does not establish those capabilities, and a successful boot should not be read as proof of them.
Advice for enthusiasts: follow the project, protect your phone
The sensible response is to watch for reproducible documentation and a clear hardware-support matrix rather than erase a working handset. There is currently no consumer-ready installation path in the report, and the developer's decision to remove Android should not be treated as a recommendation for other owners.
If a public release eventually appears, evaluate its recovery instructions before evaluating its screenshots. You would want to know exactly which device variants are supported, how to restore the original software, what data is destroyed, and which functions remain unavailable. Experiments of this kind belong on spare hardware without essential accounts or irreplaceable data.
Be especially cautious about interpreting future dual-boot plans as an existing safety net. Until a recovery or dual-boot method is documented and demonstrated, assume neither is available for your particular device.
What IT teams should take away
For IT administrators, the project illustrates a hardware-integration achievement, not a new supported endpoint category. A Windows desktop on an unusual device does not by itself establish firmware trust, driver maintenance, security-feature support or compatibility with an organization's management policies.
Any serious evaluation would need to test enrollment, updates, encryption, recovery and peripheral behavior on the actual implementation. Those are evaluation requirements, not capabilities demonstrated by this report.
The broader lesson is encouraging but narrow: Windows on ARM can reach unexpected hardware when someone supplies the missing platform integration. The OnePlus Open demonstration makes that possibility tangible. It does not signal Microsoft's return to Windows phones, and it does not yet offer a practical Android replacement.