Doesn't work after October 2025 security patch on Pixel devices

[BlankShade98]

The app crashes instantly when pressing the Set or Reset button. The changes are never being applied and saved.

[OsakaRider]

Same here

[akpapathanasiou]

Same here. Judging by the fact that Pixel IMS also does not work, seems Google did something on the backend which broke both app's functionality.

[FoxCage]

The same thing, I read the forums and there is no solution to this anywhere. Pixel IMS have fork, but for this no(

[akpapathanasiou]

The same thing, I read the forums and there is no solution to this anywhere. Pixel IMS have fork, but for this no(

AFAIK (I could be wrong) the current fork is only for enabling 5G/VoLTE and Pixel IMS also has a carrier name implementation.

So if it's dev manages to fix it, It will probably be fixable for Carrier Vanity too :)

But for the moment that's just speculation, we'll need to wait a few days :/

[BlankShade98]

The same thing, I read the forums and there is no solution to this anywhere. Pixel IMS have fork, but for this no(

AFAIK (I could be wrong) the current fork is only for enabling 5G/VoLTE and Pixel IMS also has a carrier name implementation.

So if it's dev manages to fix it, It will probably be fixable for Carrier Vanity too :)

But for the moment that's just speculation, we'll need to wait a few days :/

The current patch (also it's not actually a fork, more like a separate standalone workaround) enables VoLTE, VoWiFi and Vo5G and uses different methods than the ones used by the current version of PixelIMS. I doubt that these methods can be used by Carrier Vanity Name. But maybe there are other methods that can be used. I'm not an Android development expert, neither a dataminer so this is only a speculation.

[akpapathanasiou]

The same thing, I read the forums and there is no solution to this anywhere. Pixel IMS have fork, but for this no(

AFAIK (I could be wrong) the current fork is only for enabling 5G/VoLTE and Pixel IMS also has a carrier name implementation.
So if it's dev manages to fix it, It will probably be fixable for Carrier Vanity too :)
But for the moment that's just speculation, we'll need to wait a few days :/

The current patch (also it's not actually a fork, more like a separate standalone workaround) enables VoLTE, VoWiFi and Vo5G and uses different methods than the ones used by the current version of PixelIMS. I doubt that these methods can be used by Carrier Vanity Name. But maybe there are other methods that can be used. I'm not an Android development expert, neither a dataminer so this is only a speculation.

To be honest I'm nowhere near able to understand techincal stuff as you are :)

But I have good news, the updated Pixel IMS app does allow us to change carrier name, by changing a few strings in expert mode, see my example here.

I hope Carrier Vanity Name could be updated using the same workaround since Pixel IMS has loads of features many users don't need :)

[ramenGirl23]

Has anyone tried with Samsung oneUI 8 Android 16 with latest patch if it still works? Thanks. 🙂

[andranoxi]

Has anyone tried with Samsung oneUI 8 Android 16 with latest patch if it still works? Thanks. 🙂

Crashing with OneUI 8.5 :(

[fatmonk8]

Also not working for me on latest December patch.

Z Fold 7 on OneUI 8.

[rhubarbshoelaces]

Yes, it seems like Samsung caught up in December to the security patches Google implemented in October, and Galaxy phones too now block overrideConfig(), which is needed to run carrierConfigLoader.overrideConfig(). I can grab a log a that says "SecurityException: overrideConfig cannot be invoked by shell".

[moesie]

@nullbytepl just wondering... Do you think this is fixable, are you still maintaining it or is this officially dead?