According to NPowerUser, Monce—known across GitHub and X as @gus33000—shared a short video on November 21, 2026, showing a Lumia 950 running Windows 11 Pro, version 23H2, with the Windows Settings app displaying a 1.82 GHz clock speed for its Qualcomm Snapdragon 808 (MSM8992) processor. For anyone who has watched the smaller Lumia 950 limp along at sub-gigahertz speeds under desktop Windows, seeing that 1.82 GHz figure on screen is a bit like watching a vintage Volkswagen Beetle suddenly hit its factory top speed on the Autobahn—without shedding its transmission on the shoulder.
Still, before enthusiasts rush to dust off their old phones and declare the Lumia 950 a pint-sized Copilot+ PC, it pays to look closely at what that 1.82 GHz readout actually proves—and what technical caveats remain under the hood.
Inside the November 2026 Lumia 950 Video
As reported by NPowerUser, the three Settings screens captured in Monce’s video identify the handset as PHONE-BFF1PHVIR running a 64-bit ARM desktop build of Windows 11. Because the original X post and video have not been independently mirrored in public driver release notes yet, these specific screen readings rest on NPowerUser’s reporting of Monce’s demonstration rather than an official WOA-Project changelog.
Here is the configuration shown in the reported screenshots, alongside the Lumia 950’s factory hardware specifications for comparison:
| Component / Metric | Reported in Windows 11 Settings | Factory Lumia 950 Hardware Spec |
|---|---|---|
| Operating System | Windows 11 Pro, Version 23H2 (Build 22631.6345) | Windows 10 Mobile (launched Nov 2015) |
| Feature Experience Pack | 1000.22700.1108.0 | N/A |
| Processor (SoC) | Qualcomm Snapdragon 808 (8992) @ 1.82 GHz (ARM64) | 2x Cortex-A57 (1.82 GHz) + 4x Cortex-A53 (1.44 GHz) |
| Memory (RAM) | 3.00 GB installed (2.86 GB usable) | 3 GB LPDDR3 |
| Internal Storage | 29 GB shown (10 GB used) | 32 GB nominal eMMC (expandable via microSD) |
| Graphics (GPU) | Listed as Qualcomm Adreno 430 (331 MB) | Qualcomm Adreno 418 |
| Touch & Input | 10-point pen and touch support | 5.2-inch WQHD AMOLED capacitive touch |
A couple of curious numbers in that table immediately jump out to any seasoned PC technician—starting with the GPU and the Windows build number.
Spotting the Hardware and OS Discrepancies
- Adreno 430 vs. Adreno 418: NPowerUser notes that the Settings overview card lists a
Qualcomm(R) Adreno(TM) 430 GPUwith 331 MB. On paper, however, the Lumia 950’s Snapdragon 808 actually houses an Adreno 418 GPU; the Adreno 430 belongs to the Snapdragon 810 inside the larger Lumia 950 XL. Since the community’sLumia-Driversrepository maintains unified packages for both MSM8992 and MSM8994 devices, it is entirely plausible that a shared driver string or Windows display-adapter label caused the card to report Adreno 430—not that someone soldered a Snapdragon 810 GPU onto a 950 board. Even so, enthusiasts should treat that "Adreno 430" readout as a reporting quirk rather than a hardware upgrade. - Why 29 GB instead of 32 GB? Showing 29 GB of total storage and 2.86 GB of usable RAM is par for the course when desktop Windows sits on a 32 GB smartphone. Binary-versus-decimal sizing, EFI/UEFI boot partitions, and hardware-reserved memory shave a few gigabytes and megabytes off the top.
- An End-of-Servicing Build of Windows 11: According to Microsoft Support records, OS Build 22631.6345 corresponds to KB5071417, a cumulative security update released on December 9, 2025. That means the test device isn't running the bleeding edge of Windows 11: Microsoft ended updates for Windows 11 23H2 Home and Pro in November 2025, and formally ended servicing for 23H2 Enterprise and Education editions on November 10, 2026. Moreover, the LumiaWOA project’s own status table only lists Windows 11 Build 22000 (21H2) as formally supported, placing 23H2 outside the project's documented support baseline.
Why 1.82 GHz Was Such a Mountain to Climb
Wait a minute—why did it take six years to hit 1.82 GHz on a chip whose stock Cortex-A57 cores were already rated for 1.82 GHz back in 2015? Isn't Windows on ARM supposed to just read the CPU clock and go?
If only embedded mobile silicon were that polite. When early tinkerers first booted desktop Windows 10 on the Lumia 950 back in 2018—and when Monce famously got Windows 11 running on the Lumia 950 XL within days of its 2021 Insider debut—the two flagship Lumias behaved very differently. The larger Lumia 950 XL (codenamed Cityman) eventually achieved full support across all eight cores of its Snapdragon 810. The smaller Lumia 950 (codenamed Talkman), meanwhile, hit a brick wall on processor power management.
According to the official LumiaWOA hardware status page, CPU management on the Lumia 950 has long been flagged as only "partially working," with only the four efficiency Cortex-A53 cores active and locked down to 763 MHz. Running a full 64-bit desktop OS with modern browser tabs and background services on four A53 cores throttled below 800 MHz is about as snappy as wading through wet concrete.
The Power Engine Plugin (PEP) Catch-22
To understand why those two big Cortex-A57 cores stayed sidelined, look at the February 2025 release notes for WOA-Project/Lumia-Drivers on GitHub. In Windows, the Power Engine Plugin (PEP) acts as the traffic cop between the OS scheduler and the Qualcomm SoC’s clock tables and power rails.
On the Snapdragon 808 (MSM8992), the community driver team documented a nasty clock-scaling bug:
- Cluster 1 (Cortex-A53) Drift: PEP managed the efficiency cluster reasonably well, though clocks still drifted slightly off target (1.53 GHz instead of 1.48 GHz).
- Cluster 2 (Cortex-A57) Overclock Crash: When PEP attempted to push the high-performance A57 cluster into higher frequency states, an error in the clock tables drove the cores to 1.96 GHz instead of 1.87 GHz, triggering a fatal platform crash during boot.
- The Stability Tradeoff: Because uncapping the A57 cores caused boot loops or random shutdowns—especially on aging batteries—users either ran locked at 763 MHz or manually crippled the CPU via
bcdedit /set numproc 4to disable the second cluster entirely.
That technical history is why Monce’s latest video matters. Getting Windows 11 Pro to boot cleanly and register 1.82 GHz suggests progress in taming those stubborn PEP clock tables, UEFI (Lumia950XLPkg), and BootShim handoffs without immediately sending the Snapdragon 808 into a boot-time tailspin.
Critical Perspective: Clock Speed Is Not a Benchmark
As veteran IT journalists, we have seen plenty of impressive screenshots that tell only half the story. Before anyone mistakes a Settings readout for a finished, consumer-ready firmware update, there are several critical boundaries to keep in mind:
- Peak Display vs. Sustained Load: A static Settings page showing
1.82 GHzconfirms that Windows recognizes the target frequency—it does not prove that all six cores (four A53 plus two A57) scale dynamically under sustained multi-threaded workloads without thermal throttling or kernel panics. - No Public Driver Release Yet: As of this writing, the public
WOA-Project/Lumia-Driversrepository does not reflect a newly published November 2026 driver pack claiming full PEP resolution for the Lumia 950. Until patches land in GitHub and pass community testing, this remains a developer demonstration. - Thermal and Battery Realities: Unlike the Lumia 950 XL—which shipped with a vapor-chamber/liquid-cooling heat pipe—the smaller Lumia 950 relies on a tighter thermal envelope. LumiaWOA documentation explicitly warns that desktop Windows runs hotter than Windows 10 Mobile and that worn-out or third-party replacement batteries frequently cause unexpected power cuts below 50% charge when all CPU cores are enabled.
What Remains Broken—and Safety Warnings for Tinkerers
Even if a 1.82 GHz PEP fix makes its way to public driver channels soon, the Lumia 950 remains a fascinating engineering playground rather than a practical daily device. LumiaWOA’s own documentation outlines several hard limitations that every prospective modder should weigh before touching their bootloader:
- Zero Camera or Windows Hello Support: Cameras do not work on any LumiaWOA device ("there's nothing we can do," per the project status page), which also permanently disables Windows Hello iris/face unlock.
- Broken or Partial Telephony: On modern Windows 10 and Windows 11 builds (above Build 18363), SMS and MMS are non-functional, VoLTE does not work, and cellular voice calls require manual workarounds.
- Emergency Services Warning: The LumiaWOA project explicitly warns users never to rely on the ported firmware as a primary phone, noting that the experimental software stack is not approved for emergency services and may disrupt access to emergency calls.
- No Hyper-V and Tight Hardware Margins: Firmware lacks Hyper-V support, and with 3 GB of LPDDR3 RAM, eMMC flash storage, and a 5.2-inch display, heavy web apps, x64 emulation, and multitasking quickly hit physical hardware ceilings.
- Strict Flashing Precautions: Anyone experimenting with
DriverUpdater.exeand LumiaWOA’s experimental channel (the Stable channel and ARM32 support were deprecated in 2025) is advised to back up all data—especially original modem partitions, without which cellular connectivity can be permanently lost—and ensure the battery is charged to 100% before flashing.
Why This Decade-Old Phone Still Matters to Windows
At first glance, coaxing a 2015 Snapdragon 808 smartphone to hit 1.82 GHz on an out-of-support build of Windows 11 23H2 might seem like pure tech nostalgia. Why spend six years debugging ACPI tables and Qualcomm Power Engine Plugins for a phone Microsoft abandoned years ago?
Because projects like LumiaWOA—alongside Monce’s later porting work on devices like the original Surface Duo and Windows 10X—were the proving grounds that kept independent Windows on ARM engineering alive long before Snapdragon X-series Copilot+ PCs arrived. Every reverse-engineered UEFI port, recreated INF file, and PEP clock-table fix deepens the community's understanding of how Windows handles heterogeneous big.LITTLE ARM silicon.
For Lumia collectors and Windows modding fans, seeing 1.82 GHz appear next to Snapdragon 808 inside Windows 11 Pro is a triumphant reminder that great hardware—and stubborn developer curiosity—rarely goes quietly into the night. Just keep your real phone charged in your other pocket.
References
- Dev Finally Unlocks 1.82 GHz on the Lumia 950 Running Windows 11 After Six Years nokiapoweruser.com · 2026-11-22T11:14:04+00:00
- Releases github.com
- microsoft.com support.microsoft.com