Yea the 7a is a great phone, I sort of regret buying a 7 Pro given what a good phone for the price the a is.

Shaddow798: I think this seems like a repeat of what happened with volte, where spark got it first in one update and then it was another 3 months for the next quarterly patch for the people on Vodafone or 2degress to get it.

Anyway on my Pixel 6a on Kogan I don't have Vowifi in settings however it did work fine when I used the pixel ims patch

But when I was on skinny it would enable and I could make and receive calls however the line was completely dead If I was the caller and it the other end couldn't hear me when I could hear them. (This was on ims patch not native android 14) so I hope that's fixed now.

I still do hope we get retail devices in NZ at the start of the year or something.

no issues with vowifi calling (android 14) on Skinny on pixel 6a

Seen on the Pixel 8 forum

https://www.geekzone.co.nz/forums.asp?forumid=97&topicid=307101&page_no=12#3148048

Let's hope this extends to the P8 and P8 Pro

lchiu7:

Seen on the Pixel 8 forum

 

https://www.geekzone.co.nz/forums.asp?forumid=97&topicid=307101&page_no=12#3148048

 

Let's hope this extends to the P8 and P8 Pro

Update for other people in case it helps them:

Original testing:

Pixel 4a (5G)
Android 13 - 5 July 2023 Security Update
2Degrees
VoLTE - Not provisioned

VoWifi - Not provisioned

Attempted fixes:

Change to e-sim - Did not help.
Upgrade to Android 14 - Did not help.

Now running two sims in Australia on my phone:
SIM 1 - Local Australia SIM. VoWifi:YES; VoLTE YES
SIM 2 - 2Degrees e-sim roaming on the SAME NETWORK as my local Australia SIM: VoWifi: NO; VoLTE: NO

So definitely an incompatibility between the phone and 2degrees. From my reading, Google needs to fix it (which I doubt the will given the age of the phone).

Got Pixel 8 from MightyApe on last Thursday.

with Spark NZ prepay account. 

confirmed = WiFi Calling, VoLTE 

still no 5G even have 5G option in the network preference.

Any ideas? 

Thanks :) 

zjs787:

 

Got Pixel 8 from MightyApe on last Thursday.

 

with Spark NZ prepay account. 

 

 

 

confirmed = WiFi Calling, VoLTE 

 

still no 5G even have 5G option in the network preference.

 

Any ideas? 

 

 

 

 

 

 

Thanks :) 

 

contact Spark and ask them to provision 5G for your phone

zjs787: Thanks, just talked to one of the customer advisor, been told Pixel 8 is not on the provision list for 5G, maybe in the future. Wondering how other user get their provision done through Spark... 🫠

DM me your number.

Theclaytons: Following as have Pixel 8 on route ex Amazon. $1060 delivered.

My partner and I both bought Pixel 8 Pros from becextech recently. Both of ours ended up being the mmWave variant although mine seems to be a US model and hers a Japan model. We are both on spark and I was happy to see that 5G, VoLTE and WiFi calling was working just like my old Pixel 6, but on hers, while VoLTE and WiFi calling was working she was not able to get a 5G signal despite mine working right next to it. I remember when I bought my Pixel 6 I had asked spark to provision 5G. They said they did it, but it never worked until around the middle of this year. We contacted spark about 5G on my partners phone and they said it was already provisioned.

After owning it for 3 days now it seems to suddenly have 5G.

I've got 2degrees WiFi calling working on my Pixel 8 Pro. At this stage you need the Pixel IMS patcher and the ability to add a custom DNS entry on the WiFi network(s) you intend to use. This should be applicable to any Tensor-based (6 or later) Pixel.

Make epdg.epc.mnc024.mcc530.pub.3gppnetwork.org resolve to 118.149.14.20 (the 2degrees ePDG / VoWiFi IPSec gateway) on your network. Then use the IMS patcher to enable WiFi calling.

Based on code merges for the IMS patcher, the next release (1.2.7) should allow setting the following (for use on any WiFi network) instead of custom DNS:
iwlan.epdg_static_address_string = 118.149.14.20
iwlan.epdg_static_address_roaming_string = 118.149.14.20

I found the root problem while looking at the output from the radio log buffer with adb logcat:

12-17 17:12:15.467  3326  3326 D DNC-0   : Start handover [DataNetwork: DN-378-C, ims, state=ConnectedState] to WLAN
12-17 17:12:16.731  3326  3326 D DNC-0   : Handover failed. [DataNetwork: DN-378-C, ims, state=ConnectedState], cause=IWLAN_DNS_RESOLUTION_NAME_FAILURE(0x4004), retryDelayMillis=2000ms, handoverFailureMode=retry handover

IWLAN_DNS_RESOLUTION_NAME_FAILURE = "Unable to resolve FQDN for the ePDG to an IP address", and sure enough, I found this in the logs for my router:

dnsmasq reply epdg.epc.mnc024.mcc530.pub.3gppnetwork.org is NXDOMAIN

A bit of googling then led me to the Android documentation for CarrierConfigManager.Iwlan and a reference to "3GPP TS 23.003". Vodafone and Spark both have DNS set up per section 19.4.2.9.2, but 2degrees does not. @SaltyNZ is this intentional? 

nslookup:

> epdg.epc.mnc001.mcc530.pub.3gppnetwork.org
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    epdg.epc.mnc001.mcc530.pub.3gppnetwork.org
Addresses:  203.96.213.192
          203.96.213.193

> epdg.epc.mnc005.mcc530.pub.3gppnetwork.org
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    epdg.epc.mnc005.mcc530.pub.3gppnetwork.org
Addresses:  122.63.255.115
          122.63.255.112
          122.63.255.109

> epdg.epc.mnc024.mcc530.pub.3gppnetwork.org
Server:  one.one.one.one
Address:  1.1.1.1

*** one.one.one.one can't find epdg.epc.mnc024.mcc530.pub.3gppnetwork.org: Non-existent domain