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.
Related
I have a Blaze on T-mobile's value plan with 2gb data. I am currently running stock 2.3.6 gingerbread and have an icon blinking that there is an OTA update to ICS waiting for me to install. I've postponed that for the moment until I find the answer to my tethering question.
I would rarely use it, but on trips I would like to be able to use my blaze as a hotspot for a tablet/laptop. Im a noob, and afraid to go down the rooting path. With staying stock 2.3.6, would I be able to just use the built in hotspot app to give access to a tablet/laptop? If not, would foxfi or another program work?
Also, if I were to go ahead and install the ICS update would that affect things? If I can use the built in hotspot app or foxfi only in 2.3.6 and ICS update would not allow these options then I'd prefer to stay where I am on 2.3.6. If I need to stay on gingerbread, how can I get this annoying icon telling me to update to go away?
Thanks so much for your help guys
i recently went ics with the over the air update and i was able to get my wifi tethering working with the built in hotspot w/o rooting. i still rooted in the end though.
ics has the ability to disable apps, so you can disable WifiProvision.apk (i stopped getting t-mobile messages related to hotspot)
i'm not sure if it matters, but i also use the app Widgetsoid. It feels like many apps in one. I use the widget to enable my wifi (which is wifi hotspot)
chandrew said:
i recently went ics with the over the air update and i was able to get my wifi tethering working with the built in hotspot w/o rooting. i still rooted in the end though.
ics has the ability to disable apps, so you can disable WifiProvision.apk (i stopped getting t-mobile messages related to hotspot)
i'm not sure if it matters, but i also use the app Widgetsoid. It feels like many apps in one. I use the widget to enable my wifi (which is wifi hotspot)
Click to expand...
Click to collapse
I havent upgraded yet, but I have a question about disabling things. I have a galaxy tab 2 with 4.04 ics and I wanted to turn off the software update feature to remain on that version in case a JB update came out. I could not figure out how to disable the app, so I wondered about how to disable things in general. What are the steps?
To disable apps on ICS: Settings > Applications > All > [Select app / .apk]. Then you just hit disable, or uninstall to uninstall updates, then the disable button appears.
This would be howto disable OTA: http://forum.xda-developers.com/showthread.php?t=1856632
I would still recommend going to the latest update on stock. I think it's better and generally is able to support everything in the previous.
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!
Hi, friends! I use all my devices as WiFi only. (0$ a month, hangouts is a godsend.) But on MM, Doze disables WiFi after 10-15min or so, I forget the exact time. There's gotta be a way to whitelist it. Any ideas? I don't want to downgrade back to LP. I have read that Android N doesn't disable WiFi during Doze, however. So at least that's something to look forward to.
Also, I've searched up this issue for well over a month now. Many people would like a fix of sorts. You'd be helping out a lot of people if possible.
I've got a question about changing the Dun APN requirement for the native mobile Hotspot. The December update from OTA on galaxy S8+ or generally galaxies I'm not sure how many phone's it affected, but I've been working on a solution to get the native hotspot to work again. So far I've found a way to activate the native hotspot through the build prop/ or using an xposed module. Build prop is the easier choice for those without xposed. But even after activating it, the actual connection gets constant DNS errors in assuming because of the dun requirement that's the only thing i can guess would be doing it. Even so I might be wrong and need to do something else entirely. Either way I'm trying to figure out how to make the dun requirement null through ADB. I'm away how to set the dun requirement to 0 but the problem is any time I activate data or hotspot or turn data off or turn the hotspot off it immediately reactivated dun requirement.
TL;DR I'm trying to find a way to erase the dun requirement from hotspot protocols. Any help would be appreciated.
So I'm guessing this has been answered before, but I couldn't dig it out in my searches. I'm on T-mobile US and need wifi calling in my basement apartments. I know on the Pixel devices, wifi calling is supported in AOSP builds die to the type of implementation of it.
Is the same true for the OP6? It'd be cool to use some of them, although the stock room in pretty great. I'm curious about it, as I am a tinkerer and will probably want to change things up eventually. I wasn't able to find reference on any of the AOSP room threads.
I'm on HAVOC OS rom (AOSP-BASED) and there is not a VoWifi toggle by default, although, you can install VoEnabler from magisk which will make the toggle appear in mobile data settings.
Gionikva said:
I'm on HAVOC OS rom (AOSP-BASED) and there is not a VoWifi toggle by default, although, you can install VoEnabler from magisk which will make the toggle appear in mobile data settings.
Click to expand...
Click to collapse
Thanks for the response! When I get bored enough to start tinkering, I'll check it out and see if it works!