Related
Hello,
i have 2 phones one is sony xperia m4 aqua another is blackview bv7000. On both phones from different reasons was reflashed official firmware. Before flashing firmware formating (total format including bootloader) was done on both devices. Now on both devices is exactly same problem data works but it wont connect to voice service when checked under *#*#4636#*#* > System information.
I tried all available network types (gsm cdma, wcdma, LTE, and all same with auto (PRL) option) but non seems to connect to voice service allowing to make voice calls. Only LTE seems to work but as soon as call is done it switches back to GSM and "we" are back at no service. The sms works but only sometimes.
Also tryied reflashing different versions of official firmwares . All work but with same problem.
The sim i tested it with is working on all phones but these two.
I dont think this is some kind of device problem rather this is solely software problem.
When i checked on my xperia xz premium (which is working fine) *#*#4636#*#* > System information under baseband was available all kinds of regions but on these 2 mobiles there is only america nothing more. Also didnt choose any of these regions on any of mobiles.
Any help would be very appreciated because i have 2 fine phones sitting in shelf because of this "bug".
I have tried this new feature coming with the stock Oreo ROM and received a message from my mobile carrier initially, welcoming me to WiFi calling. All network settings seemed to be working fine, I was also browsing internet with no problems, all apps were connecting and responding as expected. However the first time I tried dialing one of my contacts I've got a message "Server error. Try again later." on the dialing screen itself. It looked like the call couldn't be connected. This happened to all outgoing calls, I suppose to all incoming also although I couldn't confirm that.
I tried many things like restarting the phone, turning data on and off, going into flight mode and disabling it, in the end I reset all network settings disabling LTE advanced services before doing that and enabling them again after the reset, but I still get that error. If I disable LTE advanced, all calls get connected with no problems.
Does anyone know if this is something with a list of supported devices explicitly enabled by the mobile carrier in their network? I am considering calling my carrier for more information but the fact itself I have got a welcome message means the device has been detected as part of the advanced services network. Perhaps there are some network settings I need to enter? Anyone ever used Axon 7's WiFi calling/advanced LTE features on any network?
Does that maybe include VoLTE which the carrier may not support?
https://www.4g.co.uk/what-is-volte/
Well according to the link provided and what I know, LTE is supported by my operator, but I wonder if it needs to be specifically tailored to a phone model by them and/or the 8.0 update by itself is not providing such functionality or it is limited by default. And I think it may be the first since ZTE products are never on the list of supported phones by any operator. But I couldn't claim it for sure as otherwise ZTE would not have included it at all with the 8.0 ROM and there are so many basic or very old models like LG K8 or Microsoft Lumia 550 that are supported.
Has anyone tried using "LTE advanced" on their 8.0 yet?
Menergy said:
Well according to the link provided and what I know, LTE is supported by my operator, but I wonder if it needs to be specifically tailored to a phone model by them and/or the 8.0 update by itself is not providing such functionality or it is limited by default. And I think it may be the first since ZTE products are never on the list of supported phones by any operator. But I couldn't claim it for sure as otherwise ZTE would not have included it at all with the 8.0 ROM and there are so many basic or very old models like LG K8 or Microsoft Lumia 550 that are supported.
Has anyone tried using "LTE advanced" on their 8.0 yet?
Click to expand...
Click to collapse
LTE Advanced = Volte
If your carrier does not support Volte, keep this option off.
WiFi Calling is something separate and not related.
If your carrier does not support WiFi calling, keep this option off.
You should still get LTE service with both of these options off. I personal find WiFi calling to work poorly, so I leave it off even though my carrier supports it. (TMobile US)
Also, there is a Q and A section for these types of posts. Don't post questions in the Guides and News section please.
Thanks for the input. Both of these options are reported to be supported by my carrier on their website. Also I always had LTE before 8.0 so simply wanted to try the new "HD voice and advanced communication service" as described in the latest firmware.
About posting this thread in the news & discussion section, this only relates to Oreo which was only recently released to the public so it is a completely new feature for the Axon. Most of the other threads are too general and since there will still be many people with 6.1 and 7.0/7.1, I would have hardly got any response whatsoever in there. For now I will keep this new option off and will contact my carrier for the support of the Axon and ZTE in general.
Good day all,
I'm encountering an issue: a fairly new phone of mine (Umidigi F1) loses its ability to get data from Verizon Wireless when I install Treble Generic System Images (AOSP-based, typically derived from phhusson's et al work). For clarification, despite being from a small Chinese company, the phone normally fully supports VZW (4G LTE data, calls, and text). While on those GSIs, I get a signal and am able to call people with it, but there is no data from the connection.
The APN settings appear to match the ones that work normally (stock F1 and a Pixel 2), so despite not being able to edit or add a new one, I am led to believe this isn't the culprit. Next, I looked at build.prop; the model, device, and brand info changed from the default states and I believe that VZW may be strict enough not to allow the altered info on their network. Attempting to modify build.prop causes a boot loop, though.
Anybody have any thoughts on what I can do? One of the comments at the top of the build.prop file indicates that it is autogenerated by buildinfo.sh. Should I attempt to modify that instead? Or maybe something else?
Veiran said:
Good day all,
I'm encountering an issue: a fairly new phone of mine (Umidigi F1) loses its ability to get data from Verizon Wireless when I install Treble Generic System Images (AOSP-based, typically derived from phhusson's et al work). For clarification, despite being from a small Chinese company, the phone normally fully supports VZW (4G LTE data, calls, and text). While on those GSIs, I get a signal and am able to call people with it, but there is no data from the connection.
The APN settings appear to match the ones that work normally (stock F1 and a Pixel 2), so despite not being able to edit or add a new one, I am led to believe this isn't the culprit. Next, I looked at build.prop; the model, device, and brand info changed from the default states and I believe that VZW may be strict enough not to allow the altered info on their network. Attempting to modify build.prop causes a boot loop, though.
Anybody have any thoughts on what I can do? One of the comments at the top of the build.prop file indicates that it is autogenerated by buildinfo.sh. Should I attempt to modify that instead? Or maybe something else?
Click to expand...
Click to collapse
many MTK soc devices on pis gsi have this issue with sim based data connection. Some even have issue with sms / text.
I did at one point have data working on one of my mtk phones, only when switched connection typs to 3G. But that was not acceptable because way too slow speeds. A solution may come. but i do not know when.
umidigi-f1-tag
I just got a umidigi f1 and am trying to get it working on Verizon. I have talk ant text(sms and mms) working through sim1. However, like you I can't get data to work.
The odd thing is that I can't seem edit the apn settings. That section is missing from my mobile networks section. I am on a stock rom, not rooted.
The sim I was using is a page plus sim. It gets service though Verizon via Tracphone.
I think my issue is that my apn is not set correctly.
Success!
Go to the phone dialer and dial
*#*#4636#*#*
Go to phone information and change your preferred network type to lte only
The default is lte/umts which probably just good for GSM phones
You should see a lte connect. Hit the ping test to verify if you can ping Google.com
Edited to say, the phone is kind of flaky with regards to the APN setting so ymmv. It was working for me for a while then stopped...
Edited 2: Okay I figured it out. To reveal the Apn menu on Verizon, change the preferred network to LTE only as above, then unselect 4g in the Mobile Network section for the Verizon Sim. Restart the phone. Next time you go to the Verizon section, there should be an Apn setting item. Create the proper Apn for Verizon because the default probably does not work. For me, I needed tracfone.vzwentp.
Here's the phone info screen
Here's the mobile network section for the Verizon Sim. Nonintuituve but had to disable 4g toggle but doesn't have any effect on speed. After a reboot, Apn section shows up
Hellom did you get it to work on Verizon? If so what are the full steps?
Make sure your Verizon sim card is in slot 1. Sadly, it seems like Verizon works best in that slot so not able to use a micro SD card.
On 2 other phones running on Red Pocket Verizon, everything just worked. No need to do anything extra.
Also disable wifi calling.
On my other phone running on tracfone/page plus, I had to do the extra steps in the previous posts above.
I just got my moto G power yesterday, purchased unlocked through best buy. I can't seem to figure out how to enable HD voice. I've looked through the settings, looking for advanced calling or anything like that, but I've come up empty. Google searches haven't been helpful for me either. Is HD voice working for anyone else?
no hd voice on this device using sprint in the us, what carrier/region variant are you using?
Verizon in the US. I just assumed it was a given with any new phone, budget or high-end.
If your carrier and sim supports it: Settings> Network and Internet > Mobile Network. You'll also have WiFi calling under the advanced settings.
I tried an ATT MNVO, it didn't give me any of those options, but every one of them appeared with a Verizon MNVO.
Unfortunately I don't have those options when i go to that setting menu. Might be unavailable when bringing an unlocked phone to verizon perhaps?
I bought a g8 power yesterday. My carrier supports VOLTE. before that I had xiaomi me a3 and there it worked after entering the "code" * # * # 86583 * # * # (an option appeared in the settings). Well, I can't find this option on g8 power and I can't even enable it.
Verizon does not allow Advanced Calling features on unlocked models. I was able to flash my unlocked Z4 to enable Advanced Calling: https://forum.xda-developers.com/t/...ng-and-root-with-xt1980-3-on-verizon.3994025/
But no luck so far with the Moto G Power XT2041-4.
Follow this thread and maybe someone can help:
all about official firmware and where to find it
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms. First of all, there...
forum.xda-developers.com
Got it working...
HD and WiFi Voice and Video Calling on XT2041-4 with Verizon
Prerequisites: You must bootloader unlock your XT2041-4. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a As far as I'm aware, this only applies to XT2041-4 on Verizon Wireless. To be clear, the XT2041-4...
forum.xda-developers.com
So I got the phone and it's working really well. My biggest issue is the lack of VoWifi. I called T-Mobile and the tech felt it should have it.
When I dialed *#*#4636#*#* (I think it's that), VoWifi is greyed out. Is there any way to use ADB or anything to force-enable it? There's no way, with the LTE/5G bands it has that it cannot be enabled on T-Mobile...
Dometalican said:
So I got the phone and it's working really well. My biggest issue is the lack of VoWifi. I called T-Mobile and the tech felt it should have it.
When I dialed *#*#4636#*#* (I think it's that), VoWifi is greyed out. Is there any way to use ADB or anything to force-enable it? There's no way, with the LTE/5G bands it has that it cannot be enabled on T-Mobile...
Click to expand...
Click to collapse
It can be related to your provider or it's SIM settings. I use Dual SIM. My Vodafone (NL) in SIM bay 1 has the WiFi-calling option. My KPN (NL) in bay 2 doesn't have it.
jordidejongh said:
It can be related to your provider or it's SIM settings. I use Dual SIM. My Vodafone (NL) in SIM bay 1 has the WiFi-calling option. My KPN (NL) in bay 2 doesn't have it.
Click to expand...
Click to collapse
You will only get wifi calling on Google fi on xperia 1, xperia 1 ii and xperia 1 iii. I have used all three phones on tmobile and it doesnt get wifi calling but on Google fi they do.
leony74 said:
You will only get wifi calling on Google fi on xperia 1, xperia 1 ii and xperia 1 iii. I have used all three phones on tmobile and it doesnt get wifi calling but on Google fi they do.
Click to expand...
Click to collapse
That's because Google has its own WiFi calling implementation, not using VoWIFI. It should work on just about any device.
I am able to get VoWIFI on T-Mobile after flashing Sony's Developer Binary (for the Xperia 1 ii), but unfortunately that one comes with some other unacceptable compromises (like no task switcher). Anyway the attached screenshot shows the service screen (dial *#*#INFO#*#*) on T-Mobile with this firmware. T-Mobile WiFi calling also works with even more out-of-fashion phones like my Nokia 9 PureView, so I would say this is definitely a Sony firmware issue.
In turn, the WiFi hotspot function does not work on Google Fi on any of my Xperias (1 ii, 5 ii, 1 iii). The client (e.g. laptop) connects to the phone and gets an IP address, but can never reach any website. It works fine with other phones (Nokia, Samsung,. ... and even the same developer image), and it works fine also with the Xperia on T-Mobile and AT&T. I suspect some iptables/firewall incompatibility between Fi and Sony's stock firmware.
I returned my phone back to sony because of missing vowifi.
T-mobile expert said its fully compatible but Sony expert said All Sony Phone dont have vowifi (disabled by software)
So I bought Xperia 1 III (along with a prepaid 3HK SIM card) when I was traveling in Hong Kong.
I inserted that 3HK SIM card to Sony phone, the Wi-Fi Calling was an option in the setting menu.
But after I returned to US, I swapped an Ultra Mobile SIM card to the Xperia 1 III, the Wi-Fi calling option is gone.
Before that, the Ultra Mobile SIM card worked perfectly on a Samsung Note 9 (also Hong Kong version) with Wi-Fi calling enabled. So it looks like it's a software problem.
Tried Google Fi SIM card, I was able to activate Wi-Fi Calling in Google Fi app, but not in phone setting menu.
T-Mobile VoWiFi is incompatible with the stock Sony firmware. You can get it back by flashing one of Sony's developer binaries onto your OEM partition (for "open devices" like the Xperia 1 ii and 5 ii but not 1 iii); however this also makes the phone not really suitable for day-to-day use (for instance, no "recent apps" switcher).
FWIW, T-Mobile VoWiFi works great on my older Nokia 9 PureView, which is definitely not a "known" device as far as T-Mobile is concerned. So the issue is limited to the combination of T-Mobile USA and stock Sony firmware. (Of course, VoWiFi also does not work on AT&T, but that's expected since they only provision AT&T-branded phones).
WiFi calling works on Google Fi, because they use their own implementation (not VoWiFi). Alas, WiFi hotspot functionality is broken on Fi - there seems to be something like a firewall/iptables incompatibilty between Fi and the Sony firrmware. The client (e.g. laptop) is able to obtain an IP address and ping the phone, but is not able to then connect to the Internet. (This, too, is fixed with the developer image above).
FWIW, as a workaround, you can install the T-Mobile DIGITS application and enable this feature on your account to make calls over WiFi. The only caveat, as I learned today, is that this does not let you make international calls. :-(
Hlorri said:
T-Mobile VoWiFi is incompatible with the stock Sony firmware. You can get it back by flashing one of Sony's developer binaries onto your OEM partition (for "open devices" like the Xperia 1 ii and 5 ii but not 1 iii); however this also makes the phone not really suitable for day-to-day use (for instance, no "recent apps" switcher).
FWIW, T-Mobile VoWiFi works great on my older Nokia 9 PureView, which is definitely not a "known" device as far as T-Mobile is concerned. So the issue is limited to the combination of T-Mobile USA and stock Sony firmware. (Of course, VoWiFi also does not work on AT&T, but that's expected since they only provision AT&T-branded phones).
WiFi calling works on Google Fi, because they use their own implementation (not VoWiFi). Alas, WiFi hotspot functionality is broken on Fi - there seems to be something like a firewall/iptables incompatibilty between Fi and the Sony firrmware. The client (e.g. laptop) is able to obtain an IP address and ping the phone, but is not able to then connect to the Internet. (This, too, is fixed with the developer image above).
Click to expand...
Click to collapse
What does developer binaries do? What can you achieve with this and how do you install it
Hazzay88 said:
What does developer binaries do? What can you achieve with this and how do you install it
Click to expand...
Click to collapse
They are actually just meant to bring back some of the original Sony functionality (e.g. camera) on top of a plain-vanilla AOSP build. For instance you can build and install AOSP 12 and then flash this image to the OEM partition. Won't give you Google Play services though, so not really useful for most people.
However you can also flash it on a stock Sony firmware. (Just apply step 7 in the AOSP instructions above, without doing the rest). Fixes some issues, including VoWIFI on T-Mobile and WiFi hotspot on Google Fi, but unfortunately the recent apps switcher is then gone.
Only available for "Open Devices" like the Xperia 1 ii and 5 ii, but not 1 iii.
I know this is a roundabout solution, but it worked for me:
Port your number(s) to Google Voice. This will end your current wireless subscription.
Sign up for a new wireless plan, with new numbers. (*) If you order a new plan online, it's a good idea to do this first so that the SIMs arrive ready for activation before you start the previous step.
Set up Google Voice to forward your calls to that number. Or better yet, install the Voice app on your phone - you can redirect both inbound and outbound calls via this app/service. (I.e. you can use the native dialer to make Voice calls; however for text messages and voicemail you need to use the Voice app).
Optional: In the native phone app, block all inbound calls directly to the new number (remember, your primary one is now on Google Voice).
This also gives you the ability to send/receive calls, voicemail, text messages on a web browser. In other words, all of this is essentially a roundabout way of getting functionality similar to Google Fi; but remember, Fi's hotspot does not work on the Xperia.
(*) Apparently if your carrier is T-Mobile, cancelling 3+ lines and then signing up for 3+ new ones won't give you the same discount as the original signup. According to a local T-Mobile store rep I talked to, if you cancel and recreate service within 90 days, the system thinks you are trying to somehow cheat on discounts. Weird -- I ended up going (back) to AT&T for this reason. You may also consider T-Mobile MVNOs such as Mint Mobile. (**)
(**) Oddly enough, in addition to better overall coverage, I get much higher download speeds on AT&T LTE/LTE+ compared to T-Mobile 5G (NR/NSA) - even in a place with full bars on both carriers. I did a test today with two SIMs in the phone - on AT&T I got 100 Mbps down on first try, whereas on T-Mobile the best I ever got (20+ tries) was ~30 Mbps down; typically 15-20. Not sure if this is another artifact of the Sony firmware, YMMV.
------
Course, if you only need to make domestic calls while on WiFi, T-Mobile DIGITS is the path of least resitance.