pixel-volte-patch
pixel-volte-patch copied to clipboard
kyujin-cho
App crashes on A16 QPR2 Beta 3
Unable to enable VoLTE in the just released A16 QPR2 Beta 3.
App crashes when enabling VoLTE or any toggle within the Pixel IMS app. It was working perfectly on beta 2
- Device: Google Pixel 9 Pro XL
- OS: A16 QPR2 Beta 3
google has fixed the bug used by this app, that means this app will no longer be useful for qrp2 beta3
It seems latest pixel ims 1.3.0 version, it doesn't work although I toggle the button
I have the same problem on my Pixel 7 and I already tried with the latest version of Pixel IMS
@kyujin-cho Hello there, I just updated my Pixel 9 Pro XL to Android 16 QPR2 Beta 3 to see if the problem exists since nobody is providing the log here, and unfortunately the app crashes on any tap on any toggle.
Crash log here:
--------- beginning of crash
10-16 10:53:45.061 4227 4227 E AndroidRuntime: FATAL EXCEPTION: main
10-16 10:53:45.061 4227 4227 E AndroidRuntime: Process: com.android.phone, PID: 4227
10-16 10:53:45.061 4227 4227 E AndroidRuntime: java.lang.SecurityException: overrideConfig with persistent=true only can be invoked by system app
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at com.android.phone.CarrierConfigLoader.lambda$overrideConfig$1(CarrierConfigLoader.java:1489)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at com.android.phone.CarrierConfigLoader.$r8$lambda$awyWVEFGyL7wJU6ZQxWH-k78PJs(CarrierConfigLoader.java:0)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at com.android.phone.CarrierConfigLoader$$ExternalSyntheticLambda0.run(R8$$SyntheticClass:0)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:1070)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:125)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at android.os.Looper.dispatchMessage(Looper.java:333)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:263)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at android.os.Looper.loop(Looper.java:367)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:9282)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:566)
10-16 10:53:45.061 4227 4227 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: FATAL EXCEPTION: main
10-16 10:53:46.168 13158 13158 E AndroidRuntime: Process: dev.bluehouse.enablevolte, PID: 13158
10-16 10:53:46.168 13158 13158 E AndroidRuntime: java.lang.NullPointerException: getSubscriptionCarrierName(...) must not be null
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at dev.bluehouse.enablevolte.SubscriptionModer.getCarrierName(Moder.kt:414)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at dev.bluehouse.enablevolte.pages.ConfigKt.Config(Config.kt:53)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at dev.bluehouse.enablevolte.pages.ConfigKt.Config$lambda$77(Unknown Source:6)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at dev.bluehouse.enablevolte.pages.ConfigKt.$r8$lambda$RNU9ZpVD5qFxcMIlimRgHQuyGGA(Unknown Source:0)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at dev.bluehouse.enablevolte.pages.ConfigKt$$ExternalSyntheticLambda43.invoke(D8$$SyntheticClass:0)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.RecomposeScopeImpl.compose(RecomposeScopeImpl.kt:196)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.ComposerImpl.recomposeToGroupEnd(Composer.kt:2895)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.ComposerImpl.skipCurrentGroup(Composer.kt:3231)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.ComposerImpl.doCompose-aFTiNEg(Composer.kt:3855)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.ComposerImpl.recompose-aFTiNEg$runtime(Composer.kt:3779)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.CompositionImpl.recompose(Composition.kt:1075)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.Recomposer.performRecompose(Recomposer.kt:1373)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.Recomposer.access$performRecompose(Recomposer.kt:156)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.Recomposer$runRecomposeAndApplyChanges$2.invokeSuspend$lambda$22(Recomposer.kt:627)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.Recomposer$runRecomposeAndApplyChanges$2.$r8$lambda$OqADLCDYmRw1RgNUvn1CR0kX32M(Unknown Source:0)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.runtime.Recomposer$runRecomposeAndApplyChanges$2$$ExternalSyntheticLambda0.invoke(D8$$SyntheticClass:0)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.ui.platform.AndroidUiFrameClock$withFrameNanos$2$callback$1.doFrame(AndroidUiFrameClock.android.kt:39)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.ui.platform.AndroidUiDispatcher.performFrameDispatch(AndroidUiDispatcher.android.kt:108)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.ui.platform.AndroidUiDispatcher.access$performFrameDispatch(AndroidUiDispatcher.android.kt:41)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.doFrame(AndroidUiDispatcher.android.kt:69)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1628)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1639)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.view.Choreographer.doCallbacks(Choreographer.java:1235)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.view.Choreographer.doFrame(Choreographer.java:1160)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1613)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:1070)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:125)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.os.Looper.dispatchMessage(Looper.java:333)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:263)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.os.Looper.loop(Looper.java:367)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:9282)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:566)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
10-16 10:53:46.168 13158 13158 E AndroidRuntime: Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [androidx.compose.runtime.PausableMonotonicFrameClock@f1d2133, androidx.compose.ui.platform.MotionDurationScaleImpl@ff6dcf0, StandaloneCoroutine{Cancelling}@50d6269, AndroidUiDispatcher@e514ee]
QPR2 Beta 3 introduced a new limit making non-system apps unable to call overrideConfig with persistent=true. The method still works by setting persistent to false but configurations will be reset on every reboot. Previously, with persistent=true they are only reset after a system update.
Can you tell me how to set “persistent” to false？> QPR2 Beta 3 introduced a new limit making non-system apps unable to call overrideConfig with persistent=true. The method still works by setting persistent to false but configurations will be reset on every reboot. Previously, with persistent=true they are only reset after a system update.
Can you tell me how to set “persistent” to false？> QPR2 Beta 3 introduced a new limit making non-system apps unable to call
overrideConfigwithpersistent=true. The method still works by settingpersistentto false but configurations will be reset on every reboot. Previously, withpersistent=truethey are only reset after a system update.
https://github.com/vvb2060/Ims
Try this instead, but do note that without persistent=true the carrier configuration will be reset to default.
That means you cannot reboot your phone at any time you want (for example, after rebooting you will not be able to get VoLTE, VoNR etc., if you are not connected to WLAN, this is common when you are outdoors).
Great！thanks.> > Can you tell me how to set “persistent” to false？> QPR2 Beta 3 introduced a new limit making non-system apps unable to call overrideConfig with persistent=true. The method still works by setting persistent to false but configurations will be reset on every reboot. Previously, with persistent=true they are only reset after a system update.
https://github.com/vvb2060/Ims
Try this instead, but do note that without
persistent=truethe carrier configuration will be reset to default.That means you cannot reboot your phone at any time you want (for example, after rebooting you will not be able to get VoLTE, VoNR etc., if you are not connected to WLAN, this is common when you are outdoors).
Idea: set persistent false, but introduce a boot service to reapply on boot the changed values.
Hi, could you tell me how to use this apk?> > Can you tell me how to set “persistent” to false？> QPR2 Beta 3 introduced a new limit making non-system apps unable to call overrideConfig with persistent=true. The method still works by setting persistent to false but configurations will be reset on every reboot. Previously, with persistent=true they are only reset after a system update.
https://github.com/vvb2060/Ims
Try this instead, but do note that without
persistent=truethe carrier configuration will be reset to default.That means you cannot reboot your phone at any time you want (for example, after rebooting you will not be able to get VoLTE, VoNR etc., if you are not connected to WLAN, this is common when you are outdoors).
Hi, could you tell me how to use this apk?> > Can you tell me how to set “persistent” to false？> QPR2 Beta 3 introduced a new limit making non-system apps unable to call
overrideConfigwithpersistent=true. The method still works by settingpersistentto false but configurations will be reset on every reboot. Previously, withpersistent=truethey are only reset after a system update.https://github.com/vvb2060/Ims Try this instead, but do note that without
persistent=truethe carrier configuration will be reset to default. That means you cannot reboot your phone at any time you want (for example, after rebooting you will not be able to get VoLTE, VoNR etc., if you are not connected to WLAN, this is common when you are outdoors).
This app does not have GUI.
Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
This app does not have GUI.
Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
Heads up, that app completely broke service on Verizon (it kept trying to force network mode to WCDMA only which no longer works anyway). Had to completely reset mobile network settings to get service again
This app does not have GUI. Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
Heads up, that app completely broke service on Verizon (it kept trying to force network mode to WCDMA only which no longer works anyway). Had to completely reset mobile network settings to get service again
Does Verizon need these hacking to get VoLTE and VoNR? It is a North America carrier and should have native support.🤔
This app does not have GUI. Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
Heads up, that app completely broke service on Verizon (it kept trying to force network mode to WCDMA only which no longer works anyway). Had to completely reset mobile network settings to get service again
Does Verizon need these hacking to get VoLTE and VoNR? It is a North America carrier and should have native support.🤔
Tried more out of curiosity than anything because some Verizon mvnos still don't enable VoNR
This app does not have GUI. Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
Heads up, that app completely broke service on Verizon (it kept trying to force network mode to WCDMA only which no longer works anyway). Had to completely reset mobile network settings to get service again
Does Verizon need these hacking to get VoLTE and VoNR? It is a North America carrier and should have native support.🤔
Tried more out of curiosity than anything because some Verizon mvnos still don't enable VoNR
Looks more like a carrier problem than a phone vendor one to me, these hacking might not work as expected.
Almost 80% of global carriers don't get VoLTE on Pixel phones, and Google tends to ignore our feedback. That's why we (people using Pixels in "unsupported regions") have to use these workarounds (other than rooting) so Pixels aren't just bricks.
This app does not have GUI. Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
Heads up, that app completely broke service on Verizon (it kept trying to force network mode to WCDMA only which no longer works anyway). Had to completely reset mobile network settings to get service again
Does Verizon need these hacking to get VoLTE and VoNR? It is a North America carrier and should have native support.🤔
Tried more out of curiosity than anything because some Verizon mvnos still don't enable VoNR
Looks more like a carrier problem than a phone vendor one to me, these hacking might not work as expected.
Almost 80% of global carriers don't get VoLTE on Pixel phones, and Google tends to ignore our feedback. That's why we (people using Pixels in "unsupported regions") have to use these workarounds (other than rooting) so Pixels aren't just bricks.
Don't get mistaken, sometimes Pixels don't get VoLTE even in supported markets if you don't use one of the main, expensive carriers. In the meantime, anyone with an iPhone 7 (!) or newer has no issues whatsoever.
This app does not have GUI. Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
Heads up, that app completely broke service on Verizon (it kept trying to force network mode to WCDMA only which no longer works anyway). Had to completely reset mobile network settings to get service again
Does Verizon need these hacking to get VoLTE and VoNR? It is a North America carrier and should have native support.🤔
Tried more out of curiosity than anything because some Verizon mvnos still don't enable VoNR
Looks more like a carrier problem than a phone vendor one to me, these hacking might not work as expected. Almost 80% of global carriers don't get VoLTE on Pixel phones, and Google tends to ignore our feedback. That's why we (people using Pixels in "unsupported regions") have to use these workarounds (other than rooting) so Pixels aren't just bricks.
Don't get mistaken, sometimes Pixels don't get VoLTE even in supported markets if you don't use one of the main, expensive carriers. In the meantime, anyone with an iPhone 7 (!) or newer has no issues whatsoever.
Wow, that's interesting... It seems that Google doesn't care about its hardware business (that takes up less than 5% of its total annual revenue, while money generated from advertising is about a whopping 75%) at all.
Pixel phones are just bricks when it comes to connectivity and global telephony availability.😐
App is working but there seems to be an issue setting network modes. Network modes seem to be disabled somehow. If I go to Phone Info and force LTE Only it still falls back to 3G sometimes. Very strange.
Hi, could you tell me how to use this apk?> > Can you tell me how to set “persistent” to false？> QPR2 Beta 3 introduced a new limit making non-system apps unable to call
overrideConfigwithpersistent=true. The method still works by settingpersistentto false but configurations will be reset on every reboot. Previously, withpersistent=truethey are only reset after a system update.https://github.com/vvb2060/Ims Try this instead, but do note that without
persistent=truethe carrier configuration will be reset to default. That means you cannot reboot your phone at any time you want (for example, after rebooting you will not be able to get VoLTE, VoNR etc., if you are not connected to WLAN, this is common when you are outdoors).This app does not have GUI.
Simply install the app and authorise it in Shizuku, then terminate Shizuku and start again, and you will see all the toggles are in your SIM settings.
Thank you, I was able to enable VoLTE on Red Altan in Mexico
Hola, ¿podrías decirme cómo usar este apk?> > ¿Puedes decirme cómo configurar “persistente” en false？> QPR2 Beta 3 introdujo un nuevo límite que hace que las aplicaciones que no son del sistema no puedan llamar
overrideConfigconpersistent=true. El método todavía funciona configurandopersistenta falso pero las configuraciones se restablecerán en cada reinicio. Anteriormente, conpersistent=trueSólo se restablecen después de una actualización del sistema.https://github.com/vvb2060/Ims Pruebe esto en su lugar, pero tenga en cuenta que sin él
persistent=trueLa configuración del operador se restablecerá a los valores predeterminados. Esto significa que no puedes reiniciar tu teléfono en cualquier momento que quieras (por ejemplo, después de reiniciar no podrás obtener VoLTE, VoNR, etc., si no estás conectado a WLAN, esto es común cuando estás al aire libre).Esta aplicación no tiene GUI.
Simplemente instale la aplicación y autorícela en Shizuku, luego finalice Shizuku y comience de nuevo, y verá que todos los interruptores están en la configuración de su SIM.
I managed to get the toggles enabled, but when making a call it doesn't connect. Did you manage to get it working?
After installing IMS, I just had to terminate the Shizuku service and restart it. Afterwards, Pixel IMS already had all the SIM options turned on, and the operator service works correctly.
Try this — it’s an app I just built and tested on the Pixel 8, fully compatible with Android 16 QPR2 Beta 3. https://github.com/Turbo1123/TurboIMS
Try this — it’s an app I just built and tested on the Pixel 8, fully compatible with Android 16 QPR2 Beta 3. https://github.com/Turbo1123/TurboIMS
it worked. thank you! (Pixel 9 Pro XL)
