Database Info

Ulefone Power 3S in Canada - Where is VoLTE option ?

So I was seduced by this phone, I was hesitating between this one and the Xiaomi Redmi plus. The Redmi was a bit too big to fit well in my belt holster. The thing is, I didn't know that much about network requirements. I thought that if I have LTE, I'm all good, but I need 2G or 3G for calls !!!
I'm in Canada. Zero support for 3G, I then tested a few carriers and Rogers/Fido support the same 2G as my phone, so now I can make calls but I don't have LTE tower from Rogers here that is compatible with my phone (Band 7 only), so I'm stuck in 2G for data. I have full LTE speed with Bell, but no phone calls. I'd rather stay with Bell, but I need to activate VoLTE, the option is not there. I'd like to confirm that I can flash my phone with the patch (ref here https://forum.xda-developers.com/nexus-5x/themes-apps/enable-volte-flashable-nougat-phone-t3693152). Or should I wait for Oreo which should get to the phone in May ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SM-986U, flashed to U1, CSC won't change with sim.

Purchased a Note 20 Ultra SM-986U. It was unlocked by T-Mobile.
I use Cricket, which is an ATT MVNO. It generally will be "AIO" in Samsung CSC list.
I flashed the Note 20 to U1, and no matter what SIM I put in, it stays at TMB/TMB/TMB.
I have tried what I believed was the specific ATT firmware as well, but still, TMB/TMB/TMB, no matter what I do.
I saw someone post about this on reddit in the T-Mobile subreddit, but no answer yet.
Anyone have any ideas on how to get it to change?
Without that, I'm stuck with no 5g, volte, or wifi calling. I'm basically stuck with a Tmobile device...

Hello, you could try *#272* your IMEI #... you can select your CSC.. Be warned .. It could wipe your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good luck

pseudo-VoWiFi on any phone

Hi All.
Let's assume I have two SIMs on phone.
SIM1 corresponds to roaming, the carrier supports VoLTE and VoWiFi so I can easily enjoy home pricing for calls and messages as soon as I have WiFi.
SIM2 corresponds to local provider and allows to have access to 4G internet for quite cheap price.
The task is to make SIM1 working using SIM2 internet in the places where WiFi is not available.
This approach sometimes is called as "pseudo-VoWiFi" and works on iPhones and latest Samsung phones with One UI 4.
My question: is it possible to realize such pseudo-VoWiFi on any Android phone? For instance, now I have two network interfaces:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any way to forcely push routes to IMS service to use rmnet0 rather than swlan0 to make VoWiFi working with mobile internet?
Any suggestions/ideas on this?

Question Incoming Call Glitch

I am using the Pixel 6a with a Verizon eSim and a physical AT&T sim card - both with WiFi calling turned on.
If I'm on a call using the Verizon network and an AT&T call comes in while on WiFi, I can neither answer the call or decline the call. Very strange behavior. The caller id displays a box with an X in it.
Anyone else seen this behavior? This bug has been present since using the Pixel 6a regardless of the updates I've applied.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have created a screen recording of the behavior as well.

having same problem, or simulare. Using eSIM and physical one. Very often when i reciving call to physical sim caller id displays a box with an X in it, cant do anything and call just drop. it happening from day one.

Voice Service says Emergency calls only. Data works but Calls and mms does not.

Hi.
I have a Galaxy J7 2016 from South Korea. The issue that I am facing right now is that I get LTE data fine on my device but I cannot make or receive calls and messages. I am currently using Verizon. When I entered *#*#4636#*#* I was able to see that I was getting a Voice Network connection but the Voice Service I got was only Emergency only. I tried changing the radio band to the us which it said it failed. I tried changing the preferred network type which also didn't help. I think it might have to do with the fact that these phones are from Korea since my LG Q7 also had the exact same problem. What makes it weird is that it works fine an a more modern phone like my Galaxy Z flip which is also from Korea.
I currently have LineageOs 17.1. However, I also had the same problem on a stock samsung rom.
Thanks. Here is a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}