SarTool uses public Windows API's to control SAR state in WLAN (Wi-Fi) and LTE subsystems.
- install WDK version 1809 or later
-OR- - use an EWDK to LaunchBuildEnv.bat and SetupVSEnv
- open Visual Studio from that cmd.exe
NOTE: If building in Visual Studio does not work (it's not yet fully supported from EWDK), use a command line like the following: msbuild /t:rebuild SarTool.sln /p:configuration=debug /p:platform=arm64 /property:WindowsTargetPlatformVersion=%Version_Number%
sartool getsar wifi
sartool setsar wifi off
sartool setsar WiFi on 0x3 0xff 2
| File | Contents |
|---|---|
| Dmf_Wlan_Public.h | contains struct and value definitions shared between SurfaceSarManager.dll and an IHV’s WLAN driver |
| Wlan_Ihv_Config.h | contains struct and value definitions provisioned by the OEM but otherwise only read by the IHV’s WLAN driver |
| GUID | struct | UEFI variable name |
| WDI_SAR_UEFI_COMMON_PARAMS (see Wlan_Ihv_Config.h) | ||
| SAR_CONFIG_HEADER | WifiSARHeader.bin | |
| SAR_CONFIG_VALUES | WifiSARConfig.bin | |
| WDI_SAR_UEFI_IHV_PARAMS (see Wlan_Ihv_Config.h) | ||
| REGION_CONFIG_VALUES | WifiRegionConfig.bin | |
| SAR_POWER_TABLE | WifiSARTable.bin | |
The document that describes the format of SarTool.exe payloads is WLAN_SAR_IHV_DOC.
Inside the document a Revision History table indicates the version (e.g. 1.3).
The version numbers in Wlan_Ihv_Config.h and Dmf_Wlan_Public.h will kept in sync with the document’s version (revisions of a given version should not alter struct formats or contain other “material” changes.)
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.