SSRM Warning Fails to Parse Policy XML [Samsung Fix]

SSRM Warning Fails to Parse Policy XML Samsung

SSRM Warning Fails to Parse Policy XML Samsung

In this guide, we will make you aware of the reason and more importantly, list the steps to fix the “SSRM Warning: Fails to Parse Policy XML. Please confirm that XML is well formed” error on your Samsung device. Issues and errors in the Android ecosystem are nothing new and their frequency increases even more if you leave the stock ecosystem and move over to a custom one.

Talking about custom ROMs, it is quite a common practice with Samsung devices to port firmware from another device and flash it onto another. For instance, you may flash the Galaxy S24 One UI 6 firmware based on Android 14 onto the S20 FE device which is still on the Android 13 One UI 6 firmware. While this results in an updated firmware with a few additional goodies, however, it comes at a cost.

SSRM Warning Fails to Parse Policy XML Samsung

Since these ROMs are ported over to your device rather than being specifically made for it, you will come across a few performance issues, bugs, and errors. If we take about the latter one, then many users are being greeted with the aforementioned error message every time they reboot their device. So why is this happening and more importantly how could it be rectified? Let’s find out.

What’s the Reason for SSRM Warning: Fails to Parse Policy XML

The culprit behind this issue is the SamsungDeviceHealthManagerService.apk app being corrupted. While deleting this app [ on an R/W system] will stop these prompts from appearing, however, this app is responsible for keeping track of battery usage for all your apps, so deleting it might not prove to be the most sensible approach. So keeping it aside, this guide will make you aware of a couple of additional methods to rectify this issue. Follow along.

How to Fix SSRM Warning: Fails to Parse Policy XML

There exists two different methods to fix this issue the automatic and the manual approach. In the former one, you just need to install an APK whereas, in the case of latter, you’ll have complete granular control over the process as you’ll be decompiling the APK, removing that error prompt, and then recompiling it. We have listed both these methods below, you may try out the one which is in sync with your requirements.

FIX 1: Automatic Method

  1. Download the SamsungDeviceHealthManagerService.apk corresponding to your Android device
    Android 12 | Android 13 [Credits: S20 FE Modding Telegram Group]
  2. Replace it with the APK present in the /system/priv-app/SamsungDeviceHealthManagerService/
  3. Now restart your device and you will no longer get the SSRM Warning: Fails to Parse Policy XML.

FIX 2: Manual Method

  1. Decompile SamsungDeviceHealthManagerService.apk present in /system/priv-app/
  2. Then search for the warning message using an advanced text editor like Notepad++.
  3. For example, the warning might be located in smali/G1/J.smali and the method is:
    .method public static u(Landroid/content/Context;Ljava/lang/String;)V
    .locals 1
    if-eqz p0, :cond_0
    new-instance v0, Landroid/app/AlertDialog$Builder;
    invoke-direct {v0, p0}, Landroid/app/AlertDialog$Builder;-><init>(Landroid/content/Context;)V
    const/4 p0, 0x0
    invoke-virtual {v0, p0}, Landroid/app/AlertDialog$Builder;->setCancelable(Z)Landroid/app/AlertDialog$Builder;
    const-string p0, "SSRM Warning"
    ...etc...etc...etc...
  4. Now just replace the entire method as follows:
    .method public static u(Landroid/content/Context;Ljava/lang/String;)V
    .locals 1
    const/4 v0, 0x0
    return-void
    .end method
  5. Finally, recompile the APK and push it back to the /system/priv-app/ directory.

That’s it. These were the two different methods that should help you fix the “SSRM Warning: Fails to Parse Policy XML. Please confirm that XML is well formed” error on your Samsung device. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution at the earliest.


Leave a Reply

Your email address will not be published. Required fields are marked *