Related
You may have noticed, especially if you've got the new Free Wifi Calling feature from T-Mobile, that WiFi Calling is a BATTERY HOG. Worse, it hogs battery even when disabled. You can verify it's Hogginess even when disabled by noting it will almost always be the top APP in history using SystemPanel. It's incredibly badly coded, and if you've got a Rom with Wifi Calling on it, and you've had bad battery life, now you know WHY.
But, really, with the new Free Wifi Calling feature, we shouldn't have to kill it entirely.
You can freeze it with Titanium Backup, but that's a hassle. Likewise using Bloater to uninstall/reinstall it all the time. Wouldn't it be nice just to have a desktop widget to do it for you? Or be able to hook it into your "Home Wifi" profile, so it's always enabled at home, and then have it turned off as soon as you're no longer near your home wifi?
Thanks to user AntonX in this thread , I came across a method to simply kill the app at the system level until needed. Still not convenient. So, I whipped up some Tasker scripts which will help the situation.
This assumes you have Tasker, as well as a basic knowledge of how to use it. Here are your the TASKS to create (Don't create any profiles unless you want to)
You also need to have the Locale Execute plugin, which is free.
NOTE: For this to work correctly, leave the slider set to ENABLE in the wifi calling app, and disable the feature using the Tasker widget and not inside the app!
Create a Task "Disable Wifi Calling"
1. Variable Set %WIFIWASON to YES If %WIFI ~ on
2. Wifi Set Off
3. Wait 5 Seconds If %WIFIWASON ~ YES
4. Execute @!pm disable com.android.kineto
5. Wifi Set On If %WIFIWASON ~YES
6. Variable Clear %WIFIWASON
7. Variable Clear %WIFICALLING
Create a Task: "Enable Wifi Calling"
1. WiFi Set On
2. Plugin:Execute @!pm enable com.android.kineto
3. Wait 5 Seconds
4. Load App Wifi Calling
5. Variable Set %WIFICALLING to YES
Create a Task "Toggle Wifi Calling"
1. Perform Task Disable WIFI Calling If %WIFICALLING ~ YES
2. Perform Task Enable WIFI Calling If %WIFICALLING |~ YES
TO USE:
Add a Tasker Widget to your homescreen for the "Toggle Wifi Calling" task.
What is going on:
Disable script will check if wifi is on at the time it is executed. It has to turn Wifi OFF so we get a clean disconnect from the network and the taskbar Icon goes away before killing the Wifi Calling app. If Wifi was on beforehand, it turns it back on.
Enable script will make sure wifi is enabled, and give it time to connect, and then load the application since sometimes it won't activate on its own without loading manually.
These tasks are intended to be linked to Tasker widgets on your homescreen, but you can call them from location based profiles or whatever.
Now, when Wifi Calling is OFF, it is REALLY off, and not just sitting around, unused, sucking up your battery. With a little more work, this could probably be turned into a single "Toggle" task, but that's an exercise for someone who has slept and doesn't have work in 5 hours. Comments/Improvements welcome.
Update 1:
Added instructions for creating a Toggle widget at the same time.
Streamlined Tasks.
Planned Features:
1. Automatically disable WIFI calling app once WIFI has been disconnected to save battery. Seems to need a block to prevent the state from triggering during processing of the disable/enable tasks, as it breaks functionality. I'm sure it is trivial but I have a limited attention span.
2. Automatically enable WIFI calling app if currently connected to WIFI *and* cell has no signal for longer than a set time. (%CELLSIG)
3. [not possible?] - Audible warning that WIFI signal is getting low and you are currently on a call. Is there any way to read current WIFI signal strength with Tasker?
Very good guide and a great idea.. if only we could get a better coded wifi calling app... or one for cm7
Sent from a cell tower to the XDA server to you.
I love the idea, but I can't quite seem to get it working. When I run the "disable" task, it eventually turns WiFi back on and WiFi calling gets re-enabled.
Then, a while later I get an "app not responding" warning from the Android system for the execute locale plugin (I can select Force Close or Wait).
Also, what is the best way to grant SU permissions to the plugin in the SU application? I have never been prompted to allow it. To test it out, I just temporarily granted access to everything...
Thanks!
lotherius,
I follow on the G2X forums. And you know how the G2x & MIUI Roms can't seem to get Wifi Calling to work consistently. I noticed that if I can get the Wifi Calling app to stay turned OFF it allowed my Sim card to not get the "Invalid Sim" error and then I was able to get wifi calling to work again even after reboots. Do you think by any chance that this script could help cure our Wifi Calling issue with MIUI Roms??? And is there a way to make a flashable zip of this for us Noobs? Thanks Again.
GFam4 said:
lotherius,
I follow on the G2X forums. And you know how the G2x & MIUI Roms can't seem to get Wifi Calling to work consistently. I noticed that if I can get the Wifi Calling app to stay turned OFF it allowed my Sim card to not get the "Invalid Sim" error and then I was able to get wifi calling to work again even after reboots. Do you think by any chance that this script could help cure our Wifi Calling issue with MIUI Roms??? And is there a way to make a flashable zip of this for us Noobs? Thanks Again.
Click to expand...
Click to collapse
Nope, this script wouldn't help with that. The problem on MIUI roms on the G2X is due to the operator (T-Mobile for most) not sending the phone # directly to the SIM card when it is activated. Some SIM cards have it, typically older ones, so it works. Those without, however, find that it doesn't work.
Supposedly you can manually program the SIM by using a phone that supports doing so, but I haven't checked to see if that would fix the problem.
Also I no longer bother with this on the G2X as it appears that while wifi calling still uses *some* battery when not active, it's not the battery hog it was back on the Vibrant.
Lotherius,
I had an HD2 running MIUI with Wifi Calling working before the G2X. The is the hack/mod that this guy TyTung did to get wifi calling to work for the HD2. http://forum.xda-developers.com/showthread.php?t=1038784 You think something like this can be used for the G2X to get wifi calling working?
GFam4 said:
Lotherius,
I had an HD2 running MIUI with Wifi Calling working before the G2X. The is the hack/mod that this guy TyTung did to get wifi calling to work for the HD2. http://forum.xda-developers.com/showthread.php?t=1038784 You think something like this can be used for the G2X to get wifi calling working?
Click to expand...
Click to collapse
WiFi Calling is really picky about the network information being accurate. I'm surprised that they got it working on the HD2...
The best fix for it on MIUI on the G2X would depend on fixing MIUI itself, since the RIL is correct -- the G2X doesn't allow you to change the RIL so it isn't affected. In the case of MIUI, older SIM cards typically work better than new ones.
The issue comes down to the ability to read the network information from the SIM card. If that data has been programmed to your SIM card, then it might work. If it has not been programmed to your SIM card, then it won't work.
So basically... not saying it's impossible to get it working on G2X/MIUI, but it is more likely to require a fix to MIUI rather than to Wifi Calling.
lotherius said:
WiFi Calling is really picky about the network information being accurate. I'm surprised that they got it working on the HD2...
The best fix for it on MIUI on the G2X would depend on fixing MIUI itself, since the RIL is correct -- the G2X doesn't allow you to change the RIL so it isn't affected. In the case of MIUI, older SIM cards typically work better than new ones.
The issue comes down to the ability to read the network information from the SIM card. If that data has been programmed to your SIM card, then it might work. If it has not been programmed to your SIM card, then it won't work.
So basically... not saying it's impossible to get it working on G2X/MIUI, but it is more likely to require a fix to MIUI rather than to Wifi Calling.
Click to expand...
Click to collapse
I wish i knew what Lib's and RIL's that I can swap from a CM7 Rom (Weapon G2X, Eaglesblood, or TSUGI) and push it via Root Explorer. I did this on my Hd2 and had wifi calling working. Can't this method work to get wifi calling working on G2X. Sorry I know this is off topic. But I even had Wifi Calling on your TSUGI ROM. You wouldn't happen to know what Lib's & Ril's on your TSUGI Rom are responsible for Wifi Calling to be enabled?
Is battery life really bad with wifi calling for you guys? I use it nearly 24/7 on my phone, and get fantastic battery life. Like way better than I did without it.
Of course, I'm on the clearly superior HTC G2, but still
I've been toying with this, but anytime I force Wifi calling to disable (by killing the app or disabling kineto), restarting Wifi calling says I'm not registered with the T-Mobile network (sure) and won't connect (even after clicking Register) until I reboot the phone.
Any tips?
I want to ensure nothing on my phone as access to wifi if my vpn is not connected. Anybody know how I could achieve this?
Any ideas greatly appreciated.
You might want to give Tasker a try. Llama (it's free / haven't used it though), or another Task automation tool might work too. It depends on how the app works, but you may have to do one or two things manually. For instance
Example Pseudo-code:
Code:
IF VPN app OPENED (
TURN OFF WIFI
SET VARIABLE vpnfrontend=1)
IF VPN app LOSES FOCUS (closed) (
ASK "Is VPN Enabled?"
IF YES (
ENABLE WIFI
SET VARIABLE vpnfrontend=0 )
IF NO (
SET VARIABLE vpnfrontend=0 ) )
That's the best I can think of off the top of my head.
Hope this helps!
Thanks for the reply closeone.
I purchased Tasker a couple of days ago. Hopefully I'll be able to do this - afraid there are going to be some manual steps though. I bought WifiJumper to auto connect to hotspots (known or unknown) so my wifi phone (Samsung Galaxy Player YP-G70) would be more like a cell phone. I thought if I could get OpenVPN working on my phone it automatically tries to reconnect but it is sometimes a slow process - thereby leaving my wifi connection open for a minute or so.
The ultimate goal here is: Android is a lot like CarrierIQ in that it tracks every IP you log in from. So I want to use a vpn so the IP I login from is the same one no matter where I'm at. I'm not a hacker, pedo, or even using P2P - I just want my privacy. Kind of a principal type of thing.
Your code is similar to what I was thinking of but.... I'm thinking I won't be able to check to see if VPN is enabled and then turn on wifi because the vpn requires wifi access to connect.
I'm still new to Android but so far the only tool I see to block wifi access is Airplane Mode and I think it blocks all apps (including the vpn). Maybe pdroid or Droidwall have some options for what I want to do????
Got to thinking if Droidwall had profiles I could build a profile that had wifi blocked for everything except Vpn. Then use Tasker to check to see if vpn was up. If not then set Droidwall to that profile. Problem is I don't think there is a way to run Tasker rule constantly. So there would be data leakage.
Sent from my YP-G70 using Tapatalk
Hey guys,
I have been reading around the wlan_rx_wakelock since days now since I cannot get rid of this battery drain and just wanted to collect all the information out there and the solutions that worked for some people.
If you put your phone into airplane mode or just simply turn off WiFi you will see in better battery stats that the wlan_rx_wake wakelock will vanish and a deleted_wakelocks will turn up with a similar up time and battery drain percentage.
Some people wake up with a drained phone in the morning, some have a horrendous battery drain when in work on the work/school/university WiFi. Some people have found solutions, but for most it could be tracked back to a certain WiFi network. The wakelock doesn't appear when signed in on the home WiFi, but is present when at work. This shows it is not a problem of the phone itself, but the WIFI AP is the cause.
This is the basic information from the BBS thread here:
wlan_rx
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: wlan_rx
Rationale: Wifi chip received a packet from somewhere - On a Galaxy S II, lots of these combined with the fact that the device takes 650 msec to resume from suspend and 150 to go back to sleep means that occasional wifi packets coming in will skyrocket Android OS usage. As an extreme example, run the following from a Linux box when wifi sleep policy is "never" and watch your deep sleep percentages plummet, your battery drain, and Android OS skyrocket: ping -i 5 <wifi IP address of phone>
Know actions: Use a sniffer to determine the cause of the traffic.
Known conditions of occurence:
Related wakelocks: wlan_wake References:
Click to expand...
Click to collapse
wlan_wake
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: wlan_wake
Rationale: wifi chip woke the CPU (Usually this fires and leads to a wlan_rx wakelock).
Know actions: Use a sniffer to determine the cause of the traffic.
Known conditions of occurence:
Related wakelocks: wlan_rx References:
Click to expand...
Click to collapse
To investigate what traffic is causing the constant wifi usage you can use Shark or Network Log to get a better resolution of the actual network traffic (source):
1. Shark for Android - Capture the packets with this. Use wireshark on your PC/MAC to read the captures.
2. Network Log (also in play store) : Will help identify which applications are using your network, on a per packet basis. Note, this is a higher level capture than Shark for Android. (As in, shark will capture every packet that hits the interface. Network log will not.)
Solutions:
use a static IP instead of DHCP (you may have to set a static IP every time you sign up in that particular network)
disable IPv6 protocol on your phone (Dorimanx kernels have an option for this in ST tweaks or you can use "Android Firewall" for this
update your router firmware
buy a gaming adapter for your Wifi network that gets the DHCP IP adress, but gives your phone a static IP (source)
optimise router settings: click
Windows network is causing the problem - solution here: click
Change wireless network encryption method, change wifi channel, instead of using auto baseband use only 2.4 or 5GHz baseband (Wi - Fi - advanced - Wi - Fi frequency band)
turn off uPNP in router/AP
t urn off netbios in windows network
Thoravukk FAQ tells you: Q. My device not entering deep sleep if i use Wifi?
A: That's not a Kernel issue! It's a Router and (Windows 7) Network problem. Disable IPv6, IP Helper service, shell hardware detection service and the Windows Media Player Network Sharing Service. Source: here
try different kernels: see below
Apps that have been demonstrated to cause the wakelock:
Dropbox (October 2012)
Several people have been able to get rid of this problem by using a different kernel:
If your wlan_rx wakelock is caused by the IPv6 problem then switching to Dorimanx 7.4x kernel will get rid of this problem as this kernel disables IPv6 for you.
People with Galaxy Nexus phones got rid of the problem by using the CMplusTuna kernel, which is not available for SGS2 unfortunately.
Another user got rid of the problem using "lean kernel" available for GNex and SGSIII.
i9300 users might get rid of it by using the Perseus Kernel "It's caused by the OS enabling some unwanted network filters, I disabled this now in Perseus 26.1 and it should also remove all drain." Source: here
Following up on network filtering and multicast I found this code project which seems to be merged into CM10.1:
bcmdhd: Change packet filter settings to block multicast
A common complaint of users is that battery life on wifi
is very poor, with frequent wlan_rx_wake wakelocks.
It turns out Samsung "opened up" the packet filter
settings from Gingerbread to ICS.
This makes them match the tuna configuration, minus
the filter to allow mDNS through (which lets a bunch
of other stuff through too.)
The original patch reverted to Gingerbread settings,
but it seems like the filter definitions changed
from GB to ICS.
Click to expand...
Click to collapse
(Source: here)
Several users reported that they only have this problem in their work/school/university network. Many users mentioned a network called "eduroam" which is a worldwide network in universities besides the local network (which normally uses the same equipment). So it seems the WiFi equipment/settings cause our phones to be constantly awake. And many report they don't have good 3G reception in these kind of buildings, so they can't just go without WiFi sadly. I can confirm this as I only have the battery drain here in my university.
Also a very interesting in the common Networking forum: http://forum.xda-developers.com/showthread.php?t=1738171
Kernel's I have tried without any luck:
Siyah 5.0.1
Dorimanx:7.44
Fluxi kernel: http://fluxi.xda-hosting.de/download.php?fname=./data/ota/files/fluxi-kernel-sgs2-XX.03-beta1.zip
N.E.A.K kernel: 2.1.2x http://forum.xda-developers.com/showthread.php?t=1576355
Shun Andromeda: 2-2-7
Dream Kernel: 2.7.5
Abyss Kernel: 2.0 F4
Maybe something is hidden in those Nexus kernels that would also work for the SGSII. Unfortunately I haven't got a clue about coding, so I am hoping that if we help together we find a solution.
Thanks for any input.
damnation333
GB was wifi-awesome, ICS & JB came with that devious wlan wakelock.
Sent from the little guy
Yeah. JB seems to have it, too. Installed CM10.1 to get rid of it, but same problem unfortunately.
I have the same problem on both my tablet (TF300) and Samsung Galaxy S2.
When WiFi was enabled on my tablet and policy set to "Keep WiFi on during sleep = always) the battery went from 100% to 40 in 8 hours.
The next day I disabled WiFi completely and let the tablet be for 8 hours again, when I got home I still had 99%
Today I'm trying with WiFi enabled but WiFi-policy set to Never instead.
The reason why I've always used always as policy is that I read somewhere (could be a year maybe) that the battery would last longer with that setting. But that doesn't seem to apply to jellybean as it did with ICS.
Sorry for rambling.
I've tried disabling IPv6 and updated my router firmware as well, I'll get back with results later.
Cheers!
Yeah, it seems to respond better to static IP config than dynamic IP.
F&%@ing wifi eats my battery alive.
Sent from the little guy
So i've had the same problem where my galaxy s3's battery has just gone to 0 in ~10 hours and i finally found the fix for it, this is what's causing it for me and might be what's causing it for you to, anyhow i'm gonna go step by step with what i did to find the culprit.
I downloaded an app called Network Log and let it log some of my traffic, i quickly found that packets where beeing sent by 192.168.1.74 wich is not any android device but my main computer and there i found the source of the problem, i was then searching around and stumbled across this post, http://forum.xda-developers.com/showpost.php?p=25876666&postcount=3
I found this line in the post,
Q: Wakelocks "wlan_rx_wake" wake up my device constantly what I can do about it?
A: The problem is neither Android nor the kernel, but the router and the (Windows7) network. In the network properties, uncheck "IPv6", disable the service "IP Helper", "Shell Hardware Detection" and "Windows Media Player Network Sharing Service", which provide ongoing Traffic. Then they scored again 98% of deep sleep.
Click to expand...
Click to collapse
and i decided to look in to it, i started the "run" command in windows and wrote "services.msc" wich then boots up you services that's started by windows, after that it's pretty simple.
Find the line called Ip Helper and stop it after that right click it and chose properties and decided the start method as inactive, after that look up the "Windows Media Player Network Sharing Service" and do the exact same thing there, this actually fixed it, my computer for some reason got stuck on sending useless packets over the network and was sending it to my galaxy s3 along with my mothers galaxy note 10.1 (no other android devices where seeing this thou for some reason) and after setting those 2 to disable i now have had my phone at 99% battery for over an hour with wifi active.
I do hope this helps and i'm gonna post this in the other wifi_rx_wake posts i can find.
Zlappy said:
So i've had the same problem where my galaxy s3's battery has just gone to 0 in ~10 hours and i finally found the fix for it, this is what's causing it for me and might be what's causing it for you to, anyhow i'm gonna go step by step with what i did to find the culprit.
...
I do hope this helps and i'm gonna post this in the other wifi_rx_wake posts i can find.
Click to expand...
Click to collapse
Hey,
Thanks for your input. I had read that before, but unfortunately this problem only occurs for me (and many others) in work/university. So I wonder if there is a way just to block the requests on our phones rather than turning off these services on the computers.
Damnation333
It's an IP conflict, dynamic IP will drain your battery faster than Static.
Sent from the little guy
That's where i belive you're wrong, i have static ips on all my machines in my home so an ip conflict i highly doubt. As i said in my previous post, it shows that it's a specific ip that's sending packets to my phone constantly.
@damnation333 i can't really answer that i'm afraid, however you should be able to look up the ip and ask your ip department of the school/university if they could have a talk with the owner of the ip Network log does show what ip it is that's sending the packets .
damnation333 said:
Hey,
Thanks for your input. I had read that before, but unfortunately this problem only occurs for me (and many others) in work/university. So I wonder if there is a way just to block the requests on our phones rather than turning off these services on the computers.
Damnation333
Click to expand...
Click to collapse
Turning off the 5 GHz band on wifi fixed the problem for me.
I really hope that someone can find a more permanent solution so I can still connect to 5 GHz bands
Piegoodman said:
Turning off the 5 GHz band on wifi fixed the problem for me.
I really hope that someone can find a more permanent solution so I can still connect to 5 GHz bands
Click to expand...
Click to collapse
i have the same problem on my Note 10.1" Tablet,
{
"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 a way to deactivate 5ghz band in Tablet or do you have to deactivate it in the router?
Haldi4803 said:
i have the same problem on my Note 10.1" Tablet,
Is there a way to deactivate 5ghz band in Tablet or do you have to deactivate it in the router?
Click to expand...
Click to collapse
You will have to deactivate on the router.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
You will have to deactivate on the router.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
You can specify in the wifi settings of android that it only should use 2.4 or 5GHz networks. Have a look in your advanced wifi settings.
damnation333 said:
You can specify in the wifi settings of android that it only should use 2.4 or 5GHz networks. Have a look in your advanced wifi settings.
Click to expand...
Click to collapse
Hmm there's no such option in my JB xwlsn, could you post a picture?
Sent from my GT-P6200 using xda app-developers app
You need to download a 3rd party app because Samsung removed that menu for whatever reason.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
king_below_my_lord said:
Hmm there's no such option in my JB xwlsn, could you post a picture?
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
]
Oh sorry. I am on SlimRom. Maybe they added that back in.
Here a screenshot:
Haldi4803 said:
i have the same problem on my Note 10.1" Tablet,
Is there a way to deactivate 5ghz band in Tablet or do you have to deactivate it in the router?
Click to expand...
Click to collapse
Deactivated 5ghz band in Router, did not help!
ah well, since i still manage aroun 8-10days Standyby i don't care...
Haldi4803 said:
Deactivated 5ghz band in Router, did not help!
ah well, since i still manage aroun 8-10days Standyby i don't care...
Click to expand...
Click to collapse
Use an app called WiFi Band Switcher to disable it on your phone. Google it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Originally Posted by king_below_my_lord
Hmm there's no such option in my JB xwlsn, could you post a picture?
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
]
Oh sorry. I am on SlimRom. Maybe they added that back in.
Here a screenshot:
Click to expand...
Click to collapse
Those Slim ROM features are pretty nifty, but I guess there are app alternatives though.
Sent from my GT-I9100 using xda app-developers app
have the same issue on optimus 4x hd. had it when we had 10a and 10b (ICS) firmwares, but after lg pushed 10f firmware (one of theirs changelog beeing: "improved wifi during sleep", the problem was gone.
So, before 10f firmware, when you ping your phone, the response was imediatelly, after 10f the ping response came only after a while like it should be during sleep.
(testing on iphone is the same result, it only asnswers ping request after a while, when it its sleeping)
So, after changing from 10f (ICS) to cyanogenmod (10.1.2) , the problem came back, because CM didnt probably implement this particuly fix. so in my opinion its a rom or kernell bug (i guess kernel) and nothig regarding to network, because i didnt change anything in my network & computers, only changed the ROM.
Hey guys, have any of you been able to share internet using the s3 as wifi hotspot on LOS 14.1? I connect to the phone with other devices, but all of them are unable to surf and they say cpnnection is limited and without internet. I can't find anything on the rom thread.
Thanks!
Does your carrier allow WiFi tethering?. Some carriers charge extra.
Check the ip addresses are all in the same pool on each device ie 192.168.xxx.yyy (xxx must match, yyy must be unique to the device).
Check the WiFi tethering block list and make sure all devices are allowed.
For testing purposes make sure any power saving options are disabled for WiFi.
shivadow said:
Does your carrier allow WiFi tethering?. Some carriers charge extra.
Check the ip addresses are all in the same pool on each device ie 192.168.xxx.yyy (xxx must match, yyy must be unique to the device).
Check the WiFi tethering block list and make sure all devices are allowed.
For testing purposes make sure any power saving options are disabled for WiFi.
Click to expand...
Click to collapse
checked everything, still not working
Are you using magisk?. If so look in magisk manager for "crossbreeder lite" and kill it.
shivadow said:
Are you using magisk?. If so look in magisk manager for "crossbreeder lite" and kill it.
Click to expand...
Click to collapse
Nope, it's unrooted, just plain lineage os 14.1 with latest updates and nano or pico gapps
Sounds like a network setup issue, like no gateway or dns being found.
Hi. When someone trying to call me and i answer the call it immidietly disconnecting and it shows that i have missed call, the same happens when I'm trying to call someone. I'm almost 100% sure that this is happening because I deleted some important system app, but i have no idea which one. I tried to restore a few of them, rebooting phone in save mode, removing SIM card and insert it again. Nothing helped. I read somwhere that it could be potentially some spying app, but this is unlikely, because if that was the case then phone calls should work fine in safe mode, but they don't. I attached file with almost all the system apps i deleted.
Update: I reset network settings and figured that phone calls don't work when I have VoWi-Fi turned on, but they worked before without any problems, they work however with VoLTE turned on. I couldn't find any system app that could cause this and it's unlikely that my phone operator has changed something with this. Perhaps it is caused by some router update (Huawei AX3 Pro Quad-Core)?
I think this issue is from your phone operator's side.
Again, if this happens just try this, turn on Airplane mode for a few seconds then turn it off, hope it works.
rickysmith-tth said:
I think this issue is from your phone operator's side.
Again, if this happens just try this, turn on Airplane mode for a few seconds then turn it off, hope it works.
Click to expand...
Click to collapse
I already did that
Update: I spoke with Orange support and this is the informations i got:
,,Phones not on the list of terminals supporting VoLTE in Orange will have The VoLTE and Wi-Fi Calling services systematically disabled. Because the phones have not passed certification, Orange is not able to ensure the correct combination of calls and quality during the call. Connections from non-certified engines can have a negative impact on the service for other users on the network."
,,If the phone was purchased outside of Orange, the service is not supported by Orange"
So they created some magical certificate and only the phones bought from their shop will support this functions and the same phones from outside their shop will not. Nice job Orange! And of course they didn't share any information about this certificate even tho i asked, they just copy and paste the same massages over and over again.
Ps. This line ,,Connections from non-certified engines can have a negative impact on the service for other users on the network." is of course a total crap, because everyone in my house is using this functions and no one has ever complain about quality of phone calls and not a single phone was bought from the operator.
Certification just means the phone has been tested and proven to work. There is no actual certificate. You can use non-certified devices on a network but you run the risk of something not working correctly. Remember that this is their network and they can control who can use and what they can do on it. If they choose to block all non-certified devices then thats up to them. They can let it be a free-for-all but that just makes diagnosing issues alot more difficult for them and for you.
The bit about negative impacts you are misinterpretating. They only say that it CAN have a negative impact, not that it does. I've seen issues on networks where one misbehaving device interferes with all other devices on the network. Thats what the network operator is trying to avoid with certification.
As for the original issue, VoLTE and WiFi Calling are complex technologies. You're calling over a data connection which routes your call to the operators servers which then transfer the call to the standard telephone network. There are so many kinks in the chain here that its never a simple fix. For instance, if your Internet provider uses traffic shaping or you set QoS on your router, they can interfere with WiFi Calling.
I would suggest the biggest issue here though is that you have tinkered with your phone and broke it yourself. You cant blame anyone else but yourself for that. System apps can interlink with each other. Deleting an apparently useless app maybe provide something useful to a critical app. That will then break functionality. Your tinkering also widens all the possible issues that it could be so I dont even know where to start.
richhaynes said:
Certification just means the phone has been tested and proven to work. There is no actual certificate. You can use non-certified devices on a network but you run the risk of something not working correctly. Remember that this is their network and they can control who can use and what they can do on it. If they choose to block all non-certified devices then thats up to them. They can let it be a free-for-all but that just makes diagnosing issues alot more difficult for them and for you.
The bit about negative impacts you are misinterpretating. They only say that it CAN have a negative impact, not that it does. I've seen issues on networks where one misbehaving device interferes with all other devices on the network. Thats what the network operator is trying to avoid with certification.
As for the original issue, VoLTE and WiFi Calling are complex technologies. You're calling over a data connection which routes your call to the operators servers which then transfer the call to the standard telephone network. There are so many kinks in the chain here that its never a simple fix. For instance, if your Internet provider uses traffic shaping or you set QoS on your router, they can interfere with WiFi Calling.
I would suggest the biggest issue here though is that you have tinkered with your phone and broke it yourself. You cant blame anyone else but yourself for that. System apps can interlink with each other. Deleting an apparently useless app maybe provide something useful to a critical app. That will then break functionality. Your tinkering also widens all the possible issues that it could be so I dont even know where to start.
Click to expand...
Click to collapse
They said that they will be disabling systematically Wi-Fi Calling and VoLTE on non-certified phones (phones that were not bought directly from them), so that would mean that this is not my fault, but if it is then this is why i shared a list of system apps that i deleted so someone who knows more about them than me could tell me which one have any connection to Wi-Fi Calling. Also this phone I have is marked on their website as supported for this technlology, so tell me what is the diffrence between exactly the same phone bought directly from them and bought somewhere else (from official source of course), except additional bloatware, that would have any complication with those technologies?