Database Info

[Q] Wifi Calling CM-10?

Hello all,
Apologies if this is the wrong place for this question, but is there any Wifi calling .apk for the Stable version of CM-10? I flashed it the other day and so far it's been super smooth and the battery's running better than ever. I'm on Android 4.1.2, using the CM kernel and radio. I'd love to get back to using Wifi calling again as I did on the stock ROM.
Any ideas?
Thanks!

Vinotas said:
Hello all,
Apologies if this is the wrong place for this question, but is there any Wifi calling .apk for the Stable version of CM-10? I flashed it the other day and so far it's been super smooth and the battery's running better than ever. I'm on Android 4.1.2, using the CM kernel and radio. I'd love to get back to using Wifi calling again as I did on the stock ROM.
Any ideas?
Thanks!
Click to expand...
Click to collapse
I believe this is a topic that will just never die. Every n00b (no offense intended) to our little party always asks about it it's a shame nobody's replied before now. But I guess no replies is better than troll replies Perhaps we should sticky a notification at the top of the forum alerting everybody about WiFi calling?
Here's the deal with WiFi calling. In the olden days, when 2.3.6 was prevalent on most devices (including the high end devices), T-Mo's wifi calling was using an actual app (with an apk extension) using a running service. This was glorious. This was rip-able and implantable into CM ROMs.
Now, however, T-Mo's WiFi Calling feature is implemented using an IMS stack. Essentially, what IMS does is it takes a VoIP connection and authenticates using unknown parameters (though it's speculated to be your cellular number, IMEI, SIM serial, or some other device/account specific number it can pull programatically) to T-Mo's IMS servers and uses that tunnel to establish a connection with T-Mo's call routing servers through the internet rather than cellular connection.
I know what you're thinking... "That's great! But that still doesn't answer why I dont have it in CM10.x/11"
Because the IMS stack and all related services and dependencies are built and compiled into the TouchWiz framework (for Samsung, idk if WiFi calling is available on other manufacturers phones), which is closed source and proprietary. Nobody knows what's needed. And trust me, I've researched the crap out of it, discussed the crap out of it, and nobody's getting anywhere.
Ohgami_Ichiro said:
jparnell8839 said:
essentially, here's what IMS is (I've researched the #$%^ out of it, but just dont have the dev skills to impletement)
IMS sits on Touchwiz's framework as a service waiting for a wifi connection
Upon connecting to wifi, it authenticates to T-Mobile's IMS servers using public and private keys (theres a lot of speculation as to what is used to authenticate, but seeing as how you dont have to be stock, you can use any touchwiz based rom, i would say its something hardware specific, such as SIM serial, IMEI, phone number, etc)
Once authentication is complete, it creates a voip tunnel.
The biggest problem (from what I can tell reading other people's research) is figuring out what files are necessary from Touchwiz to emulate in AOSP ROMs. IMS itself is open source, but Tmo has hacked it all up
Click to expand...
Click to collapse
Bingo! That's exactly it. To Cross post a tad, 1. I haven't given up on Development, I have had some Life issues reciently (nothing bad just time consuming) so I have had to put things on hold for about 3-4 weeks while I get some time to myself to work on this uninterupted. 2. I have combed through the SGS4 Files and T-Mo looks to be moving more Files in to the WiFi Calling App itself. This is sort of signalling them making this more Standalone. But They have a Very long way to go though.
Click to expand...
Click to collapse
Because it's so ingrained into TW's framework, we have no chance of it ever getting into an AOSP-based ROM short of sideloading the entire TW framework on top of it (which defeats the purpose of AOSP). There are various bounties, but I think everybody has pretty much given up hope on ever achieving this. It would probably be easier to figure out what exactly is being sent to T-Mo's IMS server as authentication and try to build a standalone IMS client from scratch to authenticate and open the VoIP, which T-Mo is likely to have thought to prevent.

Wow thanks for the explanation, I had no idea it was so ingrained into the actual framework of the system. I had an old Vibrant that I rooted and swapped ROMs but managed to add a Wifi calling .apk so was hoping there was one for the Blaze. Bummer.
In any case, thanks and Happy Thanksgiving!

Auto 2g toggle

Are there any apps that will auto toggle to 2g on Wi-Fi on stock based ROMs that DO NOT require Xposed? Tasker and Secure settings are out of the question as the options are blacked out and not able to be turned on. The main 2 apps I've seen required Xposed.

Stock-based ROMs are almost nonexistent since you would have to decompile, modify smali and recompile, not build from source.
AOSP and CAF ROMs are built from source.

Thanks for clarifying.
Any ideas on apps that do what I'm looking to do?

Data is off when WiFi is on. ?

For sure.
However what I'm seeking to do has nothing to do with data. It's about having the strongest cell signal possible. When LTE is set to recommended my cell signal almost never shows green. It is constantly in yellow, red, or no signal and my phone shows crazy times being awake to find a stronger signal. When I set the phone to 2G recommended my phone almost ALWAYS is in the green. In the exact same locations(sofa at home/desk at work). Idle drain is much much lower with the stronger cell signal.
The attached screenshot is of a typical work day with 2G set to recommended.

@AndrasLOHF I have a tasker profile I could send to you. Why do you say tasker is out of the question? What option is blacked out?

Sandman-007 said:
@AndrasLOHF I have a tasker profile I could send to you. Why do you say tasker is out of the question? What option is blacked out?
Click to expand...
Click to collapse
Which ROM are you running? If i remember correctly i had a working profile on SlimKat. On stock, PA, and the latest dev preview the 2g/3g option was always grayed out.

AndrasLOHF said:
Which ROM are you running? If i remember correctly i had a working profile on SlimKat. On stock, PA, and the latest dev preview the 2g/3g option was always grayed out.
Click to expand...
Click to collapse
You can use the state 'connected WiFi' and the task Network > Mobile data > Mode set to 2G only.

Get rhe option not available on that one too.

wifi calling without upgrading to MM?

Is there any way to get wifi calling on our AT&T G4's without upgrading to MM? I'd prefer to stay on LP so I can root and also so I can use my bluetooth heart rate monitor and other sensors. 6.0 has bugs that make bluetooth Low energy sensors not work correctly. There is a fix in 6.0.1 but my understanding is the G4 is still on 6.0. Wifi calling would be great because I encounter poor signal at work.
It seems to be part of the firmware, but I didn't know if there was a setting somewhere like the build prop file to change or something I could sideload to enable wifi calling.

Hopefully this can be done, I also am still rooted on LP mainly for tether. I would like the wifi calling feature, but don't want to give up another one.

It look like the update makes the wifi calling toggle appear up in the notification panel. I don't know if it adds any code. I wonder if it's buried somewhere in the firmware already? I thought maybe I could find/toggle it by creating a shortcut in Nova Launcher like I did with the permission manager for Access Lock. I couldn't find one although I don't know what I'm exactly looking for. there are settings buried in there with vzw in there so maybe it is buried in there.

[Magisk] Module to enable visible AOSP/OOS

jeffsga88 (https://forum.xda-developers.com/member.php?u=7188028) deserves credit for this, He made did all the real work here, I just packaged it into a magisk module container (cant remember which one I used for this so apologies if you're not credited for this)
This should work for both stock oos and aosp (android q only). I am currently using it on Omni with working mms. In theory this should work on the 6t for visible as well.
To use;
1. Install module in magisk and reboot.
2. Open settings and navigate to network & internet
3. Open "Mobile Network"
4. Make sure VoLTE is toggled on
5. Set preferred network type to "LTE"
6. Select "Access Point Names"
7. Click the 3 dot menu button on the top right of the screen
8. Tap "Reset to default"
9. Now click the hollow circle next to Visible Internet
That's it, You should now have Visible service running on your custom rom.
Please share your experience so others will know what roms do and do not work. I'm especially curious about the 6t.

lfaber06 said:
jeffsga88 (https://forum.xda-developers.com/member.php?u=7188028) deserves credit for this, He made did all the real work here, I just packaged it into a magisk module container (cant remember which one I used for this so apologies if you're not credited for this)
This should work for both stock oos and aosp (android q only). I am currently using it on Omni with working mms. In theory this should work on the 6t for visible as well.
To use;
1. Install module in magisk and reboot.
2. Open settings and navigate to network & internet
3. Open "Mobile Network"
4. Make sure VoLTE is toggled on
5. Set preferred network type to "LTE"
6. Select "Access Point Names"
7. Click the 3 dot menu button on the top right of the screen
8. Tap "Reset to default"
9. Now click the hollow circle next to Visible Internet
That's it, You should now have Visible service running on your custom rom.
Please share your experience so others will know what roms do and do not work. I'm especially curious about the 6t.
Click to expand...
Click to collapse
I used to use visible with a pixel 3A and service was awesome. Can anyone confirm this works on an oxygen os oneplus 7 pro? Thanks!

I have a pixel 3a xl right now and I am curious if this will work with it?

Thanks for all your work on this! I installed on Havoc ROM and rebooted. I only have Trackphone (trakphone?), Verizon, and Xfinity options. None seem to work... even after "reset to default" in APN settings.
Am I missing a step? Thanks!

Is this only for Visible or will it work for Verizon as well? MMS doesn't work on Verizon on some AOSP ROMs for the OP7 Pro

Did not work for me. I can get visible to work on roms with adding the apns...... except for MMS. Only one that worked on was Havoc.

Question Mobile Data not turning on after leaving WiFi Redmi Note 11 Pro 5G (veux)

Hi,
I'm running MIUI 13.0.6 stable (EU rom) with Magisk 24.3 (zygisk + universal safetynet fix 2.2.1).
When ever I leave a WiFi (WiFi still on or off doesn't matter) mobile data won't turn back on.
I have to reboot the phone to get it working again. Airplane mode or turning mobile data off and on again doesn't do the trick.
Am I missing something?
Help is appreciated.
Thanks in advance
IG
Edit:
It seems to be connected with a firewall setting. Does anyone know what service is used for switching to mobile data in MIUI?

Got it sorted out, had to allow kernel (Afwall UID -11) to access WAN, mobile data, roaming and VPN.
Thanks to @berbant from github

IronGibbet said:
Got it sorted out, had to allow kernel (Afwall UID -11) to access WAN, mobile data, roaming and VPN.
Thanks to @berbant from github
Click to expand...
Click to collapse
Can you provide resources to figure out how to do that?

awaj2006 said:
Can you provide resources to figure out how to do that?
Click to expand...
Click to collapse
I'm not sure what resources you are referring to.
If you want to know how I came ti the conclusion for kernel, I went to the afwall github page and found a similar issue.
If you want to know how to allow kernel, you need to configure the UI to show System apps and show App-IDs, then you can enable what you need. Depending on your UI configuration you might only see WiFi, Mobile Data and Roaming. You can adjust that to be more "specific".
If you use a custom iptable config script you'll need to edit that.

IronGibbet said:
I'm not sure what resources you are referring to.
If you want to know how I came ti the conclusion for kernel, I went to the afwall github page and found a similar issue.
If you want to know how to allow kernel, you need to configure the UI to show System apps and show App-IDs, then you can enable what you need. Depending on your UI configuration you might only see WiFi, Mobile Data and Roaming. You can adjust that to be more "specific".
If you use a custom iptable config script you'll need to edit that.
Click to expand...
Click to collapse
It's a shame there's no out-of-the-box solution for this. I wonder if there's a chance someone found a non-root solution to this problem.