Does anyone know of a way within Tasker to toggle Wi-Fi Calling on/off? I'm looking to setup a profile to turn it on when I connect to my setup networks and off otherwise (it seems to drain battery if left on and not in use for me?).
I found someone else on the Note 3 T-Mobile side of things that developed the equivalent (haven't tried it yet, may have to take a backup and give it a go to see if it works) which shows as incompatible with my device unfortunately.
Not sure, but I'm also interested in this.
I joined up and asked over in the beta group, to see about any possibility of having the dev take a look at it...
Thanks for doing that, I was planning on doing the same this evening. I'll add a comment as well. Here's hoping for an easy solution
Sent from my SM-N900P using xda app-developers app
You ever find a solution?
Related
I plan on trading my tablet so I reverted back to stock last night using the info I found on these forums (Thank you). Everything is looking fine except when I try and add my zip code or city state for the weather that's on the main screen it keeps saying can't find. I even erased all the ones already on the list and even those can't be found. I can get on my wireless network no problem and I even downloaded a weather app and even that app can't seem to find where I am. Is there a setting I am missing somewhere? Everything worked fine when it was rooted and using the weather channel app but I would like it stock so the person receiving it can choose what to do with it. Anyone have a clue on what it could be?
Nothing huh. phone support sucks and I'm at loss here
Loodachris said:
I plan on trading my tablet so I reverted back to stock last night using the info I found on these forums (Thank you). Everything is looking fine except when I try and add my zip code or city state for the weather that's on the main screen it keeps saying can't find. I even erased all the ones already on the list and even those can't be found. I can get on my wireless network no problem and I even downloaded a weather app and even that app can't seem to find where I am. Is there a setting I am missing somewhere? Everything worked fine when it was rooted and using the weather channel app but I would like it stock so the person receiving it can choose what to do with it. Anyone have a clue on what it could be?
Click to expand...
Click to collapse
Do you have the locations setting checked? Since there isn't a GPS in this tablet, it has to rely on location via your wireless to determine where you may be.
Thanks for the response. I am not able to locate that option in the settings. I rooted the tablet again and everything works great but I doubt I could sell it like this.
I posted this in Tasker's Google Groups, but nobody had a solid solution for me. Since the XDA is full of intelligent people, figured I'd give this a shot.
I want to use Tasker to automatically enable my WiFi Tether app automatically under certain circumstances (namely, to sync my tablet's RSS while I get ready for work in the morning).
I followed these directions to set it up, but quickly discovered that the command was wrong. After a little searching and then taking this picture, I arrived at the command being !/data/data/com.googlecode.android.wifi.tether/bin/tether start. However, that doesn't work. When I test it, it grants superuser permissions, but never starts tethering.
It was recommended to me that I try the misc/script function, but I don't understand how that works. Alternately, they recommended I try the built-in wifi tether functionality, but as I'm on a completely stock ROM, I don't believe I can do that (unless someone figure out what to change to unlock it). I used to do that on my old EVO 4G with MikG, though, so I know that would work if I had a ROM with the feature unlocked.
So, any advice on how to resolve this problem is welcome. At current, I turn it on manually, but Tasker is great at making life easier and this would be a huge convenience if I could get it to work.
And before someone recommends a custom ROM, I'm on the fence with doing that. There are features I'd love to have, but the ROMs that have all of those features also have features I don't want (like remapping the multi-tasking button, for example). Perhaps someday I'll have the time to sit down and figure out how to build my own ROM.
No ideas? The XDA has never let me down, before...
I read a mod yesterday that enables the built-in tethering.. it was like 1 change.. it worked for me.
btw i have tasker but maybe people didn't want to buy it and therefore can't help, just a thought?
edit:
open your build.prop and add anywhere in it the following line:
code:
ro.tether.denied=false
then reboot and u should be good to tether.
Well it's not necessarily familiarity with Tasker that I figured would help (of course, with the Misc/Script explanation, it would be), but rather the program language stuff. Perhaps the command I was using was wrong, and someone with ADB experience could correct it. With that said, I have seen a lot of people on here comment about how they use Tasker, so I didn't think it was a stretch that someone familiar with it could help with the Misc/Script part.
I will give your recommendation a shot, though. Thanks!
So I added the line to the build.prop, and it worked exactly once. Second time I started it, I got a data call failure as it dropped 3G. Continued getting the failure warning until turning off tethering. Repeating process yielded same results.
Sent from my EVO LTE using Tapatalk 2
Tasker for Wifi Tether
Not sure if your even paying attention to this post anymore but I had a few tidbits of info that might help.
I have had the same problem but I am using tasker in addition to NFC task launcher. I wanted to be able to turn WiFi tether on after swiping an NFC tag.
I tried the same string that you mentioned in post 1(!/data/data......) to no avail. The way that I got it to work was I set a task in NFC task launcher to open the WiFi tether app then a task that ran the string. Although the app opened and it APPEARED that it did nothing after that but it actually was working in the back ground. I haven't tested the same scenario using just tasker but it should work. So you should just need a task to open WiFi tether and one that runs the string. The string should be controlled with the Locale plugin. At least I think that is what its called. Hope this helps.
I remember a thread awile back about nfc turning off on its own...now that I been usung it I notice it also, seems now when I least expect it ill go to scan a tag and it wont work them im like oh wtf its probably turned itself off and sure enuff it has....anyway anyone else experiencing this??
I'm also experiencing this. I'm on beans v6.
I'll be using the NFC Task Launcher app, and it will randomly say "NFC is disabled. Enable NFC to use this app."
Sent from my SCH-I605
I take it this only happens to like 3 different people wth wrong with my sheet lol it drives me nuts dont even really care for nfc and when I wanna use it I gotta do like 9 steps to get it to work grrr lol
There are all-out of people having the issue. I have no idea the cause. I can say my wife does not have this issue.
Neither of us are rooted.
She does not play with the NFC tags we received, and I do. We do not use WiFi. And we have completely different apps on the phone.
I own a Wireless Media Hub and this has gone on prior to me getting that. I do not use the Hotspot.
When sharing files via Wifi Direct, I always create the connection.
So from my personal experience, it is either a specific app triggering it. Or. It is me using the Tags and after so much non-use it disables itself on its own.
Sent from my SCH-I605 using Tapatalk 2
I am having a peculiar issue. My Wi-Fi drops out and then reconnects every 30-45 minutes or so. I have the latest version of the ROM, flashed the boot.img in the thread, but it still doesn't fix my issue. It doesn't matter how far I am away from the signal, it just drops out temporarily, and then reconnects. I can't explain it. Other than that, it seems to be working great, but before I rooted and flashed, I never had any issues of any kind with the WiFi.
Also, it may be worth noting that I don't know for sure yet, but it may also turn on the WiFi automatically even though I have it set not to. Sometimes when I am out and about, I'll get a popup saying that WiFi networks were found nearby, do you want to connect etc...
Any help will be appreciated, I love this ROM and can't see myself going back on stock but this is a pretty cumbersome issue...
Re: WiFi Issue On Venom
Have you tried it out on other routers?
And fir the asking to join networks, there is a setting in wifi>advance for that.
Sent from my HTC6435LVW using xda app-developers app
About the only thing that I haven't tried is another router, but the other devices on the network don't seem to be having any issues. Then again, it is an Airport, so...Yeah, I won't fully know until I get a chance to test it elsewhere...
But I know about the advanced setting and have it disabled. That's why I'm wondering it its something in the ROM or something that I did wrong that it keeps trying to come come back. My guess is that it's disconnecting the mobile network and resetting it, just as it is doing on the WiFi...
Update
Just in case someone else runs into this issue, the problem was with an app that I used to change my host name. It would intermittently interrupt my connection trying to do that. I uninstalled it and edited my build.prop file the old fashioned way. The issue didn't have anything to do with Venom, just the fact that I had rooted and tried new things.
Thanks for your help!
This was the app that caused the issue: https://play.google.com/store/apps/details?id=com.tiranodroid.change.hostname
AYHJA said:
Just in case someone else runs into this issue, the problem was with an app that I used to change my host name. It would intermittently interrupt my connection trying to do that. I uninstalled it and edited my build.prop file the old fashioned way. The issue didn't have anything to do with Venom, just the fact that I had rooted and tried new things.
Thanks for your help!
Click to expand...
Click to collapse
Can you please go to the advanced editing options and change the name of your thread and place "Fixed" in there so people can reference it, if need, and what app it was. Thanks.
My issue is that I am constantly stepping outside, out of reach of my modem, and I'll have to turn my Wi-Fi off or my phone will stay connected to the the incredibly weak wifi signal.
So, I tried turning the dev option for "aggressive wifi to cellular handover" on thinking this would help and allow me to just leave wifi turned on while stepping outside and have it switch over to data without my assistance. And it worked, for the most part (it still held on to wifi signals *I* would deem too slow, but not often), BUT whenever I reboot the option in dev settings un-ticks so I have to go back in and turn the setting back on.
My question is, is there a way to prevent the aggressive wifi to handover from turning off on reboots, or is there another option I could try that may even be more aggressive?
Thank you in advance!
Have you tried the setting to automatically disconnect from a poor WiFi signal? It's under WiFi>settings>advanced WiFi>avoid unstable connections
Juggernaut79 said:
Have you tried the setting to automatically disconnect from a poor WiFi signal? It's under WiFi>settings>advanced WiFi>avoid unstable connections
Click to expand...
Click to collapse
That says it'll automatically disconnect from no connection, but I still have an internet connection off the wifi, it's just like slow as all get out
6NomoN6 said:
That says it'll automatically disconnect from no connection, but I still have an internet connection off the wifi, it's just like slow as all get out
Click to expand...
Click to collapse
For me it disconnects from a weak signal.
I'll be back!
6NomoN6 said:
My question is, is there a way to prevent the aggressive wifi to handover from turning off on reboots, or is there another option I could try that may even be more aggressive?
Click to expand...
Click to collapse
I have the same problem, discovered the same solution, and have run into the same issue with no persistence after reboot! I'm googling now for a solution because going into developer options every reboot is incredibly damaging to the smoothness of the user experience I've worked so hard to customize.
Whether I find a solution or not I'll post in this thread again to let you know. If the latter is the result I will personally either write a tasker script, init.d script, or if nesseceary an Xposed module depending on factors I've yet to research. Can you Beta test for me if it comes to that? Maybe it's as simple as editing build.prop, I don't know yet, but I wanted to make this post ASAP so that you know you aren't alone on this and someone capable is working on the issue. For a developer like myself tapping menus every boot is unacceptable! Hopefully there is already a fix out there in the wild and I won't have to do any work.
P.S. Don't forget to also enable cellular radio always active for fast network switching at the price of some battery life. It's a few options below aggressive handover in Developer Options and thank jolly the setting is sticky unlike it's counterpart. Also, sorry for the poor turnout on your thread. I figured there'd be 100 posts by now, but at least you got my attention.
Edit 1: "setprop persist.{i-dont-know-yet}" in terminal emulator may do the trick. Checking for variables for the setting we want now. Hopefully they exist!
Edit 2: :laugh: I FOUND EVERYTHING I NEED FOR A FIX!!! However, an Xposed module will be required. I need some sleep but I should have something by tomorrow night. In case any other developers are reading this, here is the information required to make things work the way Iwe want them to:
http://android.stackexchange.com/qu...-cellular-handover-option-in-developer-settin
https://android.googlesource.com/pl...ndroid/settings/DevelopmentSettings.java#1061
Edit 3: Now that I know how this setting actually works together with wifi_watchdog (see source code WifiWatchdogService.java) I think I may have changed my mind regarding how to go about solving the root problem at hand (network switching) which this setting really does a "hack" job of taking care of. The developer that made it decided on a arbitrary, static number to be used for decreasing the connected WiFi AP's RSSI value (thereby making handover more "aggressive") instead of exposing any kind of grainular control to the user. So yes I could easily make the developer options setting stick but a much better approach would be to hook the method android.net.wifi.WifiManager with an Xposed module and implement additional logic to the network switching. The great thing about this method is there is the possibility for adding additional checks besides just periodically pinging the current primary dns server and monitoring the delay and timeout of the result. I also know for a fact modding the framework persists after reboot which is afterall all we originally wanted to have. The second or alternative route would be to edit the secure settings database using SQLite. The pro of this method is it is guranteed to be compatible with nearly ANY rom, won't break anything after an update, and doesn't use resources like an Xposed module. The con is that you are limited to the variables built into android, can't implement any new logic, and the worst is that I'm not even sure the modified tables would even persist after a reboot (or network state change for that matter) which if true would defeat the original purpose of this expedition. I'll make a fourth edit to this post after I've thought about and considered how to best proceede to reaching the goal of having a solution to our problem. :victory:
FoxysWorkplace said:
I have the same problem, discovered the same solution, and have run into the same issue with no persistence after reboot! (...)
Click to expand...
Click to collapse
First of all, thank you so very much for looking into this!
I'm sorry for not responding sooner, but I had honestly lost hope of finding a solution to this issue mainly because I am not a developer myself and haven't the foggiest how to get started with it on Android
But when I opened my notifications and saw a response to this post (!) I got *extremely* excited, and as I read through your post, my excitement intensified to great happiness!
I can't express my gratitude, but I would be more than happy to help with anything that I can!
Any news on this?
Has anyone found a solution?
Had anyone found a solution that doesn't require root access?
Can we expect that fourth update any time soon? Any solution without xposed?
I'm following this thread in the event that someone finds a non-rooted solution. The Galaxy S7 really cannot be rooted without a serious performance hit (and yes I've gone through the two or three best/popular lag-fix solutions) but it works best in stock :-/