Closed Fbx2000 closed 1 month ago
I've got this same issue too with the latest android security update on my Pixel 7.
Pixel IMS has previously worked very well for me - I've had to reapply the patch every update and always worked without a problem.
After updating to the latest security patch the changes do not seem to apply. I do have the WiFi calling toggle in my android settings after enabling in Pixel IMS but enabling it makes no difference. VoLTE also doesn't work.
Any thoughts? I have tried resetting network settings as per another thread.
Edit: I am in the UK on Lebara network.
I've tried resetting network settings, removing and reinstalling IMS (endless amount of restarts in between every action and still no joy. As mentioned the settings appear in the network provider setting to enable WiFi calling since installing but doesn't seem to work. IMS app status is unregistered. I believe google has done something major in regards to network settings and updates that seems to break IMS registration. Also, just after the march update restart, my Mobile Provider sent me the network settings (perhaps because I went back to a blank setting at first) keep me posted if any solutions come up please.
//Update Pixel IMS somewhat works for VoLTE and registers fine (calls occur over 4G successfully) but seems unstable and after a while goes back to unregistered. However as soon as VoWifi is enabled it goes to unregistered and calls fall back to 2g in my tests. Thanks
On 5 March 2024 20:54:13 ParanoiaP @.***> wrote:
I've got this same issue too with the latest android security update on my Pixel 7.
Pixel IMS has previously worked very well for me - I've had to reapply the patch every update and always worked without a problem.
After updating to the latest security patch the changes do not seem to apply. I do have the WiFi calling toggle in my android settings after enabling in Pixel IMS but enabling it makes no difference. VoLTE also doesn't work.
Any thoughts? I have tried resetting network settings as per another thread.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.
--18e107e05d7794e280dfde5408 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.= w3.org/TR/html4/loose.dtd">
= head>On 5 March 2024 20:54:13 ParanoiaP ***@***.***>= ; wrote:
I've got this same issue too with the latest android securi= ty update on my Pixel 7.
Pixel IMS has previously worked very well for me - I've had= to reapply the patch every update and always worked without a problem.
After updating to the latest security patch the changes do = not seem to apply. I do have the WiFi calling toggle in my android settings= after enabling in Pixel IMS but enabling it makes no difference. VoLTE als= o doesn't work.
Any thoughts? I have tried resetting network settings as pe= r another thread.
=E2= =80=94
Reply to this email directly, view it on GitH= ub, or unsubscribe.
You are receiving this be= cause you authored the thread.Message ID: <kyujin-c= ho/pixel-volte-patch/issues/277/1979618811@github= .com>
App crashed on P8 after the march update.
I have P6P and have the same problem with new google update.VOLTE does not work.
I had the app crash on me when I tried the older version of Pixel IMS in one of my experiments to make it work. Latest version doesn't crash for me on P7P ( only the odd time here and there after moving to another app I got the "app has crashed popup") Sorry Ur also facing an issue but glad that it's definitely a Google thing across several devices and hat broke Pixel IMS. I do wonder if then Delay in March update for the USA is related due to Verizon or Others not approving the new radio related update yet.
On 6 March 2024 09:58:09 ziofat @.***> wrote:
App crashed on P8 after the march update. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
--18e136b7e8d26e1280de3881d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.= w3.org/TR/html4/loose.dtd">
= head>On 6 March 2024 09:58:09 ziofat ***@***.***> w= rote:
App crashed on P8 after the march update.
=E2= =80=94
Reply to this email directly, view it on GitH= ub, or unsubscribe.
You are receiving this be= cause you authored the thread.Message ID: <kyujin-c= ho/pixel-volte-patch/issues/277/1980493582@github= .com>
I have the same problem on Pixel 6. I was using an old version of the application, after updating it did not start, I updated the application and now IMS does not register VoLTE.
Hi everyone, just clarifying that Pixel IMS is completely broken after the March update?
Yes as reported no longer seems to work. VoLTE seems to work for me but I don't know if that used to work before trying Pixel IMS. VoWiFi is completely not working. Function to enable APN editing is also not working. Thanks On 6 Mar 2024 17:01, Joy @.***> wrote: Hi everyone, just clarifying that Pixel IMS is completely broken after the March update?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Alright, I'll have to check out the source code and see what went wrong then. I somehow didn't get the march update yet (yay?)
For me it works again after updating pixel ims to 1.2.8 (from GitHub). On french carrier NRJ mobile Build AP1A.240305.019.A1
Is the pixel ims v1.2.8 in Google play and github not the same? Are there any difference?
Just to confirm, I have VoLTE working too - though I'm not sure how and I'm not sure if this is due to PixelIMS or despite it and I'm not messing with anything now in case it breaks!
The other behaviour I have noticed is that when running PixelIMS first, then Shizuku, when returning to PixelIMS the IMS Registered status at first reports as registered - but then changes to unregistered (without changing any settings).
I am also experiencing PixelIMS crashing, but I cannot isolate exactly the circumstances that cause this - it is not all the time - perhaps when refreshing the status page.
For context, Pixel 7, Android 14 March Update AP1A.240305.019.A1, PixelIMS v1.2.8 (from playstore)
Today I received 14 (AP21.240216.010) update and Pixel ims is also not working either. Tried the 1.2.8 version also.
Everyone, can I get the phone models of everyone, your android version and if updating to 1.2.8 worked at all? Also consider uninstalling Pixel IMS and reinstalling it
v1.2.8 (downloaded from GitHub releases) works well on Pixel 8, Android 14 with March update, China Unicom.
V 1.2.8 Both GitHub and Play versions not working, Device Google Pixel 7 March beta update Android 14 version 14 (AP21.240216.010).
v1.2.8 ( GitHub ), Pixel 7 Pro, Android 14 with March update, AP1A.240305.019.A1 , UK , SIM free, . lebara
V1.2.8 google play store, Pixel 6 Pro, android 14 with march update, Iran,with uninstalling and installing PIXELIMS was not solved.
Same here. Not working on Pixel 7 Pro since QPR3 Beta 2 March update.
Same issue as everyone else - enabled but makes no difference. Latest versions of everything. On Lebara (UK) and have a Pixel 8.
Phone: Pixel 6 Android version: 14 Build number: AP1A.240305.019.A1 SIM card type: eSIM PixelIMS: 1.2.8 (tested both GitHub and Google Play) Does VoLTE setting appear?: Yes Does VoLTE work?: No Did VoLTE work before?: Yes
Same problem with VoLTE and Video Calling on Pixel 6 build AP1A.240305.019.A1 with Iran MCI operator. Worked before with v1.2.6 and an older build but no luck on the new one. Things I've already tried: -Resetting network settings, reinstalling app and activating VoLTE -Adding IMS apn (With all combinations of caps and no caps) -Disabling/Enabling VoLTE from carrier side
I would gladly share more info/dumps if requested.
Today I received the February Google Play Update and Pixel ims now working
Pixel ims version 1.2.8 (GitHub) Device Google Pixel 7. Security Patch March. Android version 14 (AP21.240216.010). Play security update February
Hey everyone, if you are still experiencing calling issues you can try this Settings > System > Reset options > Reset Network Settings See if that can get IMS services working again
Hey everyone, if you are still experiencing calling issues you can try this Settings > System > Reset options > Reset Network Settings See if that can get IMS services working again
I've already tried this (and resetting wireless and Bluetooth also) unfortunately to no avail.
Do you have the latest google play update?
Do you have the latest google play update?
Also yes.
Ya tried that a few whilst figuring out why ims wasn't working before logging the issue. Also did endless restarts between steps to be have and no Joy. Quoting the original issue log "I've tried resetting network settings, removing and reinstalling IMS (endless amount of restarts in between every action and still no joy. As mentioned the settings appear in the network provider setting to enable WiFi calling since installing but doesn't seem to work. IMS app status is unregistered. I believe good has done something major in regards to network settings and updates that seems to break IMS registration. Also, just after the march update restart, my Mobile Provider sent me the network settings (perhaps because I went back to a blank setting at first) keep me posted if any solutions come up please."Thanks On 13 Mar 2024 22:12, Joy @.***> wrote: Hey everyone, if you are still experiencing calling issues you can try this Settings > System > Reset options > Reset Network Settings See if that can get IMS services working again
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Hey everyone, if you are still experiencing calling issues you can try this Settings > System > Reset options > Reset Network Settings
I also did this but unfortunately no results. Android security update: March 5, 2024 Google Play system update: February 1, 2024
I suppose Google has broke the IMS Services for everyone it seems. Wait until April, or if your phone straight up cannot call/text as a result of this, follow the guide below
Go to this link and find your device model listed under there. Look for Feb 2024 build and click on Flash, not Link. Your computer will guide you through a process to connect the phone to the computer, and follow all the instructions there.
It seems it's the February Google play system update which broke ims. Because ims works on my pixel 7 pro, with march update.
WiFi calling stopped working as soon as I update to march update (but my phone could have possible updated both at the same time) .Anyone tried or knows how to roll back to Jan Google play ?
On 16 March 2024 10:57:05 Frank KUBLER @.***> wrote:
It seems it's the February Google play system update which broke ils. Because ims works on my pixel 7 pro, with march update. Screenshot_20240316-115212.png (view on web) Screenshot_20240316-115341.png (view on web) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
--18e474f57e3e27280d2e2c306 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.= w3.org/TR/html4/loose.dtd">
= head>On 16 March 2024 10:57:05 Frank KUBLER ***@***.***= m> wrote:
It seems it's the February Google play system update which= broke ils. Because ims works on my pixel 7 pro, with march update.
Screenshot_20240316-115212.png (view = on web)
Screenshot_20240316-115341.png (view = on web)=E2= =80=94
Reply to this email directly, view it on GitH= ub, or unsubscribe.
You are receiving this be= cause you authored the thread.Message ID: <kyujin-c= ho/pixel-volte-patch/issues/277/2001948436@github= .com>
I suppose Google has broke the IMS Services for everyone it seems. Wait until April, or if your phone straight up cannot call/text as a result of this, follow the guide below
Rolling back to February Image (For Pixels only)
⚠️ WARNING: THIS WILL ERASE ALL FACTORY DATA. BACKUP YOUR DEVICE DATA. YOU HAVE BEEN WARNED
Go to this link and find your device model listed under there. Look for Feb 2024 build and click on Flash, not Link. Your computer will guide you through a process to connect the phone to the computer, and follow all the instructions there.
In,china,the operator CMCC works perfectly fine . However, sometimes the CUCC needs to reset the network and then open Pixel IMS and register IMS.
Pixel 7, Android 14 March Update AP1A.240305.019.A1, PixelIMS v1.2.8
Sorry, took a while to notice the thing being screwed up... I was on the preview track of Android 15 DP. Currently in the verge of downgrading the software.
Update: Bullshit, just got my P7P bricked during the downgrade.
Oh damn. For real?
Sadly - yes, not a drill. What's more worse is there is no official support for Pixel on my region...
Holy crap 😐 I wonder what went wrong... Not going to ask you if you did this or that, I guess you know what you're doing...
Okay I give up - threw everything but still my phone is not working. All I've done is flashing "official" Android 14 QPR3 (or whatever) downloaded directly from google. What a joke! Until I manage to unbrick the phone by myself or buy a new Pixel - but you guys will know that the latter will happen in a very unlikely manner after all of these crappy situations -, there will be no patches published from my side. PRs are still welcome, so if any other of you guys manage to solve this error please feel free to mention me.
PS: anybody with an idea to unbrick Tensor Pixel please reply here or email me. All I see is an unresponsive screen and USB device named "Pixel ROM Recovery" when plugging into the computer.
Did you by any chance fall victim to the last OTA beta bug that bricked phones with locked bootloaders?
Okay I give up - threw everything but still my phone is not working. All I've done is flashing "official" Android 14 QPR3 (or whatever) downloaded directly from google. What a joke! Until I manage to unbrick the phone by myself or buy a new Pixel - but you guys will know that the latter will happen in a very unlikely manner after all of these crappy situations -, there will be no patches published from my side. PRs are still welcome, so if any other of you guys manage to solve this error please feel free to mention me.
PS: anybody with an idea to unbrick Tensor Pixel please reply here or email me. All I see is an unresponsive screen and USB device named "Pixel ROM Recovery" when plugging into the computer.
Shit, check XDA
Edit: You likely are facing the black screen of death
I will say, I did update to March build and on version 1.2.8 from github and am experiencing zero issues
Seems to work for me? Tried on two SIMs in the space of two weeks. I wonder if it's because I'm opted into the beta or something but it still says March
Pixel 7 (No new updates at the time of posting) PIMS v1.2.8 Shizuku v13.5,adb (Wireless Debug Method)
Seems to work for me? Tried on two SIMs in the space of two weeks. I wonder if it's because I'm opted into the beta or something but it still says March
Pixel 7 (No new updates at the time of posting) PIMS v1.2.8 Shizuku v13.5,adb (Wireless Debug Method)
Same here
Hi guys mine all works well, I'm also using Pixel IMS from play store and now my back up calling also works fine. My pixel is from Japan, My main Sim is from Malaysia (U Mobile) and my secondary sim is from Brazil (TIM) since I'm travelling. VoLTE, VoWiFi works well when I'm connected to only wifi and surprisingly my back up call is also working well. Below are the picture
Hi guys mine all works well, I'm also using Pixel IMS from play store and now my back up calling also works fine. My pixel is from Japan, My main Sim is from Malaysia (U Mobile) and my secondary sim is from Brazil (TIM) since I'm travelling. VoLTE, VoWiFi works well when I'm connected to only wifi and surprisingly my back up call is also working well. Below are the picture
Same here, but we need to see why it's not working for people in the March update
I mean mine work better after the march update, before March update back up calling was not working and now it works well
Just updated from the Feb to March Play update and still no joy. Activating VoWifi from pixel IMS shows the option in the phone settings and doesn't cause the device to unregister however, as soon as the VoWifi is activated from the phone settings IMS status is unregistered. I have tried the calling Preferences in settings to "Call over mobile network if mobile network is unavailable, use Wi-Fi" and it remains registered however, as soon as signal drops it's unavailable to connect using VoWifi
UQ1A.240205.002 IMS 1.2.8 VoLTE seems works, but if i turn on VoWiFi, VoLTE stop works (unregistered) and VoWiFi anyway not working (no icons when calling, no icon in top bar. In ##4636## VoWiFi have status - no access If i turn off WiFi card, VoLTE is registered
Just updated from the Feb to March Play update and still no joy. Activating VoWifi from pixel IMS shows the option in the phone settings and doesn't cause the device to unregister however, as soon as the VoWifi is activated from the phone settings IMS status is unregistered. I have tried the calling Preferences in settings to "Call over mobile network if mobile network is unavailable, use Wi-Fi" and it remains registered however, as soon as signal drops it's unavailable to connect using VoWifi
That is super weird. I know this might sound stupid, but AFAIK samsung galaxy devices are generally optimised to work well by carriers globally. Do you have a galaxy device and can you test if IMS is working inside a galaxy device? We could try and get a useragent out if everything works on the galaxy device.
Not working since March Update on P7P. Whilst it was working for the last few months, After the update March 5th update the IMS status was unregistered. I updated to the latest version and tried again to register again but no Joy