Skip to content

Version 2408.1 - Chucky
Compare
Choose a tag to compare
@gus33000 gus33000 released this 04 Aug 18:58
2408.1
c9757e5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Surface Duo BSP - Version 2408.1 (Chucky)

Note

Higher thermals in Windows is currently expected and is not dangerous

General information

**Released:** 08/04/2024 11:00 PM UTC+2

Quality: Preview

You can view compatibility for this release, along with important information and what works, and what doesn't at this link: https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/Status.md

Important information

- ⚠️ For users who are updating from an earlier release than version 2301.93, please reinstall.

FFU images will be made available later this week

▶️ Install Surface Duo (1st Gen) UEFI and Drivers for Windows from scratch (Clean Installation)

▶️ Install Surface Duo 2 UEFI and Drivers for Windows from scratch (Clean Installation)

▶️ Update from an older version of Surface Duo UEFI and Drivers (both got updated with v2408.1)

Clean Installation & Update Files

These files are to be used when clean installing Windows on your Surface Duo or updating an existing installation

Drivers File UEFI File Target Device OS Version Notes

SurfaceDuo-Drivers-v2408.1-Desktop-Epsilon.7z

 Surface Duo (1st Gen) Windows 10 Version 2004 and higher

N/A

SurfaceDuo-Drivers-v2408.1-Desktop-Zeta.7z

 Surface Duo 2 Windows 11 Version 24H2 and higher

N/A

SurfaceDuo-Drivers-v2408.1-Desktop-Epsilon.7z

 Surface Duo (1st Gen) Windows 10 Version 1803 to Windows 10 Version 1909

N/A

If you are clean installing:

  • Download the Driver File onto your Computer
  • Extract it
  • Connect your Surface Duo to your computer in Mass Storage mode
  • Double Tap on the OfflineUpdater.cmd file
  • Enter the Drive Letter for the Surface Duo Windows Partition (See This PC for knowing this)
  • Wait til the processes finishes
  • Reboot your device
  • Boot the device using the new UEFI version linked alongside the Driver File above

If you are updating an existing installation:

  • Download the Driver File onto your Surface Duo
  • Extract it
  • Double Tap on the OnlineUpdater.cmd file
  • Wait til the processes finishes
  • Reboot your device
  • Boot the device using the new UEFI version linked alongside the Driver File above

In case you're having issues/troubles updating within the OS on the device, you can always put your phone into mass storage, and use OfflineUpdater.cmd to update the drivers this way, and then use the new UEFI version linked alongside the Driver File above.

Full Flash Update Files

We're now providing FFU files directly from the release page outside of Telegram. The FFU files are also still uploaded on Telegram FFU channel, and they match this very specific release.

Learn more about FFU files: FFU Flashing Guide

Unfortunately, FFU files for this very version are not yet available. Download the FFU Files from the previous release alongside the previous release UEFI or come back later to this page for when the files will be uploaded.

Release notes

Note

This release includes both UEFI packages and Driver packages

Common:

  • Adds support for more pens (e.g., v3, v4).

  • Removes defaultinstall (primitive INF packages) as they are being phased out.

  • Default Surface wallpaper now matches the OS version.

  • Touch-related hacks are no longer necessary.

Surface Duo (1st Gen):

  • Resolves long-standing issues across various Windows versions.

  • Adds support for Redstone 4/5 based operating systems. You need to use a secure boot disabled variant of the UEFI in order to boot these.

  • Addresses boot issues on the latest Windows 10 version (VB).

  • Fixes recent Bluetooth issues.

  • Addresses charging-related problems.

  • Improves SAR sensor stability.

  • Resolves black screen issue on first run.

  • Fixes broken Vulkan support in GPU driver.

  • Enables flash light current protection in the PMIC.

  • Enhances brightness control curve for displays.

  • Allows control of surface data telemetry collection (previously always on for Surface app and service; now user-configurable).

  • Fixes Bluetooth advertising issue related to device type.

  • GPU driver now supports HEVC encoding.

  • Surface Dial no longer crashes the OS shell on Windows 11.

  • Headphone jack now functional with the official dongle (the dongle is not just acting as a USB audio card in regards to ADSP)

  • Please download SurfaceDuo-Drivers-v2408.1-Desktop-Epsilon.7z if you want drivers for Surface Duo 1

  • Please download SurfaceDuo-Drivers-v2408.1-Desktop-Zeta.7z if you want drivers for Surface Duo 2

  • We are aware auto pairing of the pen will not work anymore on Windows 10, a fix is due in the next update.
Known issues

- Installing Gallium Semester Insider builds may lead to a black screen on second boot of the OS, simply press the power button to continue.

  • Booting Windows 10 18362/18363 will lead to "static screen" effects on the right display, much like driver releases from last year did on any version of Windows. A fix is being worked on for the next release.

  • The TPM driver is not working for Windows 10 18362/18363. A fix is being worked on for the next release.

  • The Posture driver is not working for Windows 10 18362/18363. A fix is being worked on for the next release.

  • Enhanced auto rotation is not working for Windows 10 18362/18363. A fix is being worked on for the next release.

  • Brightness control is glitchy on both displays.

  • On device speakers are not functional.

  • Dongles are not detected correctly when plugged into the USB Type-C port.

  • Updating drivers may lead to weird configurations if done on old driver releases.

  • MAC addresses do not reflect the real addresses asigned to the device.

  • BitLocker drive encryption is not available.

  • USB dongles that are not externally powered may not currently work.

  • USB-C Billboard devices will not currently work.

  • External Display Stream support will not currently work.

  • Additional information provided by the posture sensor is currently not available for public consumption. This includes peek events.

  • Digitizers will not react to the device being folded over.

  • Displays will not react to the device being folded over most of the time.

  • Physical device data is incorrect.

  • Digitizers aren't calibrated correctly.

  • Flipping the device is not smooth.

  • Users upgrading from releases older than the January ones may want to clean install again.

  • Booting Windows 10 18362/18363 with Secure Boot enabled is not currently supported and will result in a broken installation.

  • In some cases, booting the UEFI image may lead to "static screen" effects on the left display. Please do not force reboot the device as it may interrupt the installation process, if ongoing, and instead please wait a few minutes.

  • Windows Recovery environment lacks drivers unless Windows has performed a Feature Update at least once.

  • sRGB is not available currently, and displays will not react to ICC profiles being applied.

Accessing Foldable Sensors from your applications

In order to currently access the sensor data given by the foldable sensors, you need to use the following apis:

  • Windows.Devices.Sensors.HingeAngleSensor*
  • Windows.Internal.Devices.Sensors.FlipSensor* (2)
  • Windows.Internal.System.TwoPanelHingePostureDevice* (2)

(2): These apis require the use of an externally sourced winmd available from https://github.com/ADeltaX/InternalWinMD/blob/master/%23winmd/Windows.Internal.Devices.Sensors.winmd

In the future, further apis will be functional (specifically under the Windows.System.Preview namespace). Consider this an early "thing".

The following API may be used to determine if your app is used on a dual screen device: https://docs.microsoft.com/en-us/uwp/api/windows.ui.windowmanagement.windowingenvironment.getdisplayregions?view=winrt-22621

The following API may be used to determine on which display region your app is currently being shown: https://docs.microsoft.com/en-us/uwp/api/windows.ui.windowmanagement.appwindow.getdisplayregions?view=winrt-22621

The following API may be used to move your application to the other display: https://docs.microsoft.com/en-us/uwp/api/windows.ui.windowmanagement.appwindow.requestmoverelativetodisplayregion?view=winrt-22621

THe following API may be used to move your application to a specific display: https://docs.microsoft.com/en-us/uwp/api/windows.ui.windowmanagement.appwindow.requestmovetodisplayregion?view=winrt-22621

The following API may be used for spanning purposes: https://docs.microsoft.com/en-us/uwp/api/windows.ui.windowmanagement.appwindow.requestsize?view=winrt-22621

The Windowing Environment for Windows Desktop editions (outside of tablet mode) is Overlapped. Tiled is used for Tablet Mode and Windows Core OS's ModernPC.

Code Samples

#include <iostream>
#include <windows.h>
#include <winrt/Windows.Foundation.h>
#include <winrt/Windows.Internal.Devices.Sensors.h>
#include <winrt/Windows.Internal.System.h>
#include <winrt/Windows.System.Preview.h>
#include <winrt/Windows.UI.WindowManagement.h>
#include <winrt/Windows.Foundation.Collections.h>

using namespace std;
using namespace winrt;
using namespace Windows::Foundation;
using namespace Windows::Internal::Devices::Sensors;
using namespace Windows::Internal::System;
using namespace Windows::System::Preview;
using namespace Windows::UI::WindowManagement;
using namespace Windows::Foundation::Collections;

VOID OnFoldSensorReadingChanged(FoldSensor const&, FoldSensorReadingChangedEventArgs const& args)
{
	try {
		printf("Fold sensor state changed.\n");
		switch (args.Reading().GestureState())
		{
		case GestureState::Started:
			std::cout << "Fold started\n" << std::endl;
			break;
		case GestureState::Completed:
			std::cout << "Fold stopped\n" << std::endl;
			break;
		case GestureState::Cancelled:
			std::cout << "Fold cancelled\n" << std::endl;
			break;
		case GestureState::Unknown:
			std::cout << "Fold unknown\n" << std::endl;
			break;
		}

		for (auto panel : args.Reading().ContributingPanel())
		{
			printf("Panel: %s\n", to_string(panel).c_str());
		}
		
		std::cout << "Initial angle " << args.Reading().InitialAngle() << std::endl;
		std::cout << "Final angle " << args.Reading().FinalAngle() << std::endl;
		
		switch (args.Reading().FoldType())
		{
		case FoldType::Closing:
			std::cout << "Fold Closing\n" << std::endl;
			break;
		case FoldType::Opening:
			std::cout << "Fold Opening\n" << std::endl;
			break;
		case FoldType::NotDetected:
			std::cout << "Fold NotDetected\n" << std::endl;
			break;
		}
	}
	catch (...) {}
}

VOID PrintDetails(TwoPanelHingedDevicePostureReading const& args)
{
	try {
		std::cout << "Panel1 " << args.Panel1Id().c_str() << "\n" << std::endl;
		std::cout << "Panel2 " << args.Panel2Id().c_str() << "\n" << std::endl;

		std::cout << "Panel1 Orientation " << (int)args.Panel1Orientation() << "\n" << std::endl;
		std::cout << "Panel2 Orientation " << (int)args.Panel2Orientation() << "\n" << std::endl;

		switch (args.HingeState())
		{
		case Windows::Internal::System::HingeState::Unknown:
			std::cout << "Hinge1State Unknown\n" << std::endl;
			break;
		case Windows::Internal::System::HingeState::Closed:
			std::cout << "Hinge1State Closed\n" << std::endl;
			break;
		case Windows::Internal::System::HingeState::Concave:
			std::cout << "Hinge1State Concave\n" << std::endl;
			break;
		case Windows::Internal::System::HingeState::Flat:
			std::cout << "Hinge1State Flat\n" << std::endl;
			break;
		case Windows::Internal::System::HingeState::Convex:
			std::cout << "Hinge1State Convex\n" << std::endl;
			break;
		case Windows::Internal::System::HingeState::Full:
			std::cout << "Hinge1State Full\n" << std::endl;
			break;
		}
	}
	catch (...) {}
}

VOID OnPostureChanged(TwoPanelHingedDevicePosture const&, TwoPanelHingedDevicePostureReadingChangedEventArgs const& args)
{
	try {
		printf("Posture sensor state changed.\n");
		PrintDetails(args.Reading());
	}
	catch (...) {}
}

VOID OnSensorReadingChanged(FlipSensor const&, FlipSensorReadingChangedEventArgs const& args)
{
	try {
		printf("Flip sensor state changed.\n");
		switch (args.Reading().GestureState())
		{
		case GestureState::Started:
			std::cout << "Flip started\n" << std::endl;
			break;
		case GestureState::Completed:
			std::cout << "Flip stopped\n" << std::endl;
			break;
		case GestureState::Cancelled:
			std::cout << "Flip cancelled\n" << std::endl;
			break;
		case GestureState::Unknown:
			std::cout << "Flip unknown\n" << std::endl;
			break;
		}
	}
	catch (...) {}
}

int main()
{
    init_apartment();
	printf("Trying to get flip sensor.\n");
	try {
		FlipSensor flip = FlipSensor::GetDefaultAsync().get();
		if (flip == nullptr)
		{
			printf("Flip sensor not found.\n");
		}
		else
		{
			printf("Starting listening session for flip sensor.\n");
			flip.ReadingChanged(OnSensorReadingChanged);
		}
		printf("Press any key to stop\n");
		std::cin.get();
	}
	catch (...) {}

	printf("Trying to get posture sensor.\n");
	try {
		TwoPanelHingedDevicePosture Posture = TwoPanelHingedDevicePosture::GetDefaultAsync().get();
		if (Posture == nullptr)
		{
			printf("Posture sensor not found.\n");
		}
		else
		{
			auto curpst = Posture.GetCurrentPostureAsync().get();
			if (curpst != nullptr)
			{
				PrintDetails(curpst);
			}
			printf("Starting listening session for Posture sensor.\n");
			Posture.PostureChanged(OnPostureChanged);
		}
		printf("Press any key to stop\n");
		std::cin.get();
	}
	catch (...) {}

	printf("Trying to get fold sensor.\n");
	try {
		FoldSensor fold = FoldSensor::GetDefaultAsync().get();
		if (fold == nullptr)
		{
			printf("Fold sensor not found.\n");
		}
		else
		{
			printf("Starting listening session for fold sensor.\n");
			fold.ReadingChanged(OnFoldSensorReadingChanged);
		}
		printf("Press any key to stop\n");
		std::cin.get();
	}
	catch (...) {}
}

Dual Boot Information

Important!: The Dual Boot images currently target the following Android OTA update versions from Microsoft. These images can only be used on a phone that had as latest the following OTA versions from microsoft even if you are currently running a custom android system image. Using these images will work with a custom Android System Image but the device bootloader and firmware must be from the same Microsoft OTA version as shipped from the stock Microsoft Android Updates!

Device Name Device Variant Dual Boot Compatible with the following firmware/bootloader version only
Surface Duo United States of America (GEN) 2022.902.48 (Latest OTA for Surface Duo (1st Gen) devices)
Surface Duo United States of America (AT&T) 2022.902.48 (Latest OTA for Surface Duo (1st Gen) devices)
Surface Duo Europe (EEA) 2022.902.48 (Latest OTA for Surface Duo (1st Gen) devices)
Surface Duo 2 United States of America (mmWave) 2023.501.202 (Latest OTA for Surface Duo 2 devices)
Surface Duo 2 Europe (5G NR) 2023.501.202 (Latest OTA for Surface Duo 2 devices)

Flashing these images on any other version may brick your phone or render touch unusable! Make backups of your original boot partitions and ALWAYS test before flashing permanently using "fastboot boot image.img"!.

If you do not currently run above firmware versions, please also follow https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/InstallWindows/DualBoot.md.

For more information on dual boot, manual steps on how to craft such image file, and how to flash it, and use it, please visit https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/InstallWindows/DualBoot.md.

We do not recommend inexperienced users without advanced knowledge of IT/Command prompts to do this ever. You may find it very hard and mess up your device easily if you do it wrong. Also important to note Android OTAs will not work anymore with a custom boot.img flashed onto the device and you will need to reflash your original backup for them to work or else, you'll be forced to recover with an OTA zip package from https://aka.ms/sri if one is even available for your current version or higher.

Some examples about what above warning means for you when running custom operating systems on your surface duo and if you are willing to run dual boot images

To clarify above bullet point

If for example you flashed the Pixel Experience Android 13 Android System Image on your Surface Duo, and previously you were running Microsoft Stock Android OTA version 2022.123.45, your device firmware and bootloader are still version 2022.123.45 and will not be compatible with these images targeting 2022.902.48

In another example, you flashed the Pixel Experience Android 13 Android System Image on your Surface Duo, and previously you were running Microsoft Stock Android OTA version 2022.902.48, your device firmware and bootloader are still version 2022.902.48 and you are compatible with these images.

You are currently running stock microsoft android version 2022.902.48; you are compatible

You are currently not running stock microsoft android version 2022.902.48; you are not compatible

Hey wow, that's a lot of UEFI images right here! Which one do I even download?

  • FastBoot -> Image intended to be used with fastboot boot uefi.img to directly boot into the UEFI this way via your computer, use this one if you're following the installation guides right now
  • Dual Boot -> Image intended to be flashed onto boot after checking compatibility with above table to make sure you meet the usability criteria and your device will work fine
  • FD -> File needed to make your own custom dual boot images in case you do not meet the compatibility table, using the guide to do so (https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/InstallWindows/DualBoot.md)

Use the files without SecureBoot Disabled in their filenames if and only if:

  • I am booting a version of Windows higher than build 18363 (the latest Windows 10 feature update, Windows 11, Windows 11 Version 22H2 etc..)

Only use the files with SecureBoot Disabled in their filenames if and only if:

  • I am booting Windows 10 build 18363 or lower on my device (Please also turn on testsigning in BCD in order to boot)
  • I am booting Windows 10X on my device
  • I am booting a linux distribution
How to offline update an existing Windows Desktop installation

Please follow the steps detailed at https://github.com/WOA-Project/SurfaceDuo-Guides/blob/main/Update/UpdateDriversAndUEFI.md

How to install Windows Desktop on internal Storage

Please follow the steps detailed at https://github.com/WOA-Project/SurfaceDuo-Guides

Bug reporting

This release is a Preview release. Bug exists and may happen. If you notice a bug not present in the following bug list, please report them on our Telegram Group.

Seems Faster(TM)

-- The DuoWoA authors

Assets 17
Loading