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 :-/
Related
I recently flashed on cm7 on my aria. it is great but my data usage began shooting up. i realized it was due to the fact that everytime i lock my phone, it disables my wifi (i saw this because everytime i unlock im on 3g for a 1-2 seconds then i get on wifi so that means that the whole time my phone is locked it uses 3g data ) is there anyway i can prevent this from occurring??
Thanks,
Okachowwa
Menu -> settings -> wireless & networks -> wi-fi settings -> menu -> advanced -> wi-fi sleep policy -> never
I think that's it.
Sent from my Aria - CM7 Build 24
okachowwa said:
I recently flashed on cm7 on my aria. it is great but my data usage began shooting up. i realized it was due to the fact that everytime i lock my phone, it disables my wifi (i saw this because everytime i unlock im on 3g for a 1-2 seconds then i get on wifi so that means that the whole time my phone is locked it uses 3g data ) is there anyway i can prevent this from occurring??
Thanks,
Okachowwa
Click to expand...
Click to collapse
Have you checked the Wifi Settings to see which sleep option is selected? There is an 'Never' option which tells wifi to stay on even when the phone sleeps.
One thing I noticed its that if I leave my house I have to turn off wifi and turn it back on to find my router.
Sent from my Liberty using XDA App
klbmth said:
One thing I noticed its that if I leave my house I have to turn off wifi and turn it back on to find my router.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
yup...that's why you just turn your wifi off with the notification widget (very simple and painless might I add) if you know you're leaving the house...what's the point of having wifi enabled if you're not in range of your network? all it's going to do is drain your battery. i left my wifi enabled one day when i sent to work and within half the day i had ~12% battery life...definitely not good practice to leave it enabled that's my 2 cents, do as you wish though. to each his own.
klbmth said:
One thing I noticed its that if I leave my house I have to turn off wifi and turn it back on to find my router.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Yup, I have the same issue with CM7 nightlies. This worked flawlessly in CM6 and stock2.1. So far there isn't a viable solution.
from the CM6.1.1 thread...
Q. How do I keep my wifi from going to sleep every time the screen shuts off?
A. There is a hidden feature that disables wifi sleep.
menu > Settings > Wireless & networks > wifi settings > menu (again) > advanced > Wi-Fi Sleep policy > Never > menu > Save
However: although you can keep the wifi service from sleeping, the wifi driver will still sleep on it's own after detecting no bus activity for a period of time.
Click to expand...
Click to collapse
mattbollenbach said:
from the CM6.1.1 thread...
Click to expand...
Click to collapse
I've made sure to set Wifi Sleep Policy to "Never" but that did not fix my wifi problems. What I see when I open Wifi Settings is a cycle of:
Code:
Scanning --> Connecting --> Disconnected... Scanning, etc
When I look in logcat it shows it attemping (in vain) to authenticate against the last wifi network I was using -- even though it is no longer in range (and clear across town). In a nutshell it is refusing to recognize the actual nearby network UNTIL I toggle wifi settings.
I've had the same behavior on FR008 and the stock ATT 2.1 load as well. When Wifi is in that on but not really connected state some apps can wake it up...the default browser usually will, but Listen would not. I just gave up and only turn on wifi when I need it.
kinggrowler said:
I've made sure to set Wifi Sleep Policy to "Never" but that did not fix my wifi problems. What I see when I open Wifi Settings is a cycle of:
Code:
Scanning --> Connecting --> Disconnected... Scanning, etc
When I look in logcat it shows it attemping (in vain) to authenticate against the last wifi network I was using -- even though it is no longer in range (and clear across town). In a nutshell it is refusing to recognize the actual nearby network UNTIL I toggle wifi settings.
Click to expand...
Click to collapse
What is the point of having wifi set to ON when you are not in range of a network? Hence why, if you are using CM7 or CM6, you should utilize the notification widget and turn wifi off if you know you're leaving the area of your network. It's simple. Things aren't ALWAYS going to work how YOU want them to work. Thing will not always be automatic. I think I quote attn1 when I say this, just because it doesn't work how you want it to work, does not mean it is broken.
zervic said:
What is the point of having wifi set to ON when you are not in range of a network? Hence why, if you are using CM7 or CM6, you should utilize the notification widget and turn wifi off if you know you're leaving the area of your network. It's simple. Things aren't ALWAYS going to work how YOU want them to work. Thing will not always be automatic. I think I quote attn1 when I say this, just because it doesn't work how you want it to work, does not mean it is broken.
Click to expand...
Click to collapse
Well, just because people don't work exactly like you work, does not mean they are doing it wrong. If something is broken I'm going to call it out. I might be incorrect, but let's be clear: you aren't questioning that wifi in CM7 isn't working the way it did in CM6, you are questioning my behavior -- which is a weak argument.
I guess you don't understand the issue, so I'll spell it out:
Wifi worked flawlessly and automatically for me in stock 2.1 AND CM6. This automatic behavior does not work in CM7. Manually toggling something that simply "just worked" before is a regression, not a feature. Hence the reason I point it out -- the devs can't fix something unless they know it's broken, and I seriously doubt the devs are able to test all/every permutation. I have nothing but respect for the work they do, thus my very respectful tones in my earlier posts. I've had no indication that the devs are unwilling to get feedback about their work.
You asked a question though, and here is the answer:
I leave Wifi on all the time because I'm a consultant -- I work in many different locations throughout the week, travelling the country. I have dozens of wifi networks saved on my phone, and it is useful for me to have my phone automatically jump on the correct, nearest network. I'd rather use free wifi instead of paying AT&T for data charges. It is not always possible for me to remember I'm in a location with a known wifi network, or to remember to manually toggle wifi settings: it is useful for me to have this happen in the background. Sometimes I'm on a call, sometimes I'm heading into a meeting and I'd rather not mess with my phone. I want wifi to be on all time, scanning for the correct network, and jumping on it when it's in range.
Outrageous, right?! Not actually -- this is the existing behavior in CM6 and stock 2.1. From my standpoint, wifi just worked -- I didn't have to think about it, didn't have to manually toggle something to prevent AT&T data charges.
This is desired behavior for me, and I'm happy with rolling back to CM6 to get it. I understand that _you_ don't need this behavior, but that doesn't mean it's wrong. It just means the world is bigger than you realized.
And yes: wifi in CM7 (beta) is currently broken. Read the threads. Many people are having problems with it.
zervic said:
yup...that's why you just turn your wifi off with the notification widget (very simple and painless might I add) if you know you're leaving the house...what's the point of having wifi enabled if you're not in range of your network? all it's going to do is drain your battery. i left my wifi enabled one day when i sent to work and within half the day i had ~12% battery life...definitely not good practice to leave it enabled that's my 2 cents, do as you wish though. to each his own.
Click to expand...
Click to collapse
That's a good tip, I feel kind of dumb for not thinking about it lol and I also agree that it is good practice to do so. I just wanted to point it out in case a dev was going through this thread which is relevant to the topic.
Sent from my Liberty using XDA App
kinggrowler said:
Well, just because people don't work exactly like you work, does not mean they are doing it wrong. If something is broken I'm going to call it out. I might be incorrect, but let's be clear: you aren't questioning that wifi in CM7 isn't working the way it did in CM6, you are questioning my behavior -- which is a weak argument.
I guess you don't understand the issue, so I'll spell it out:
Wifi worked flawlessly and automatically for me in stock 2.1 AND CM6. This automatic behavior does not work in CM7. Manually toggling something that simply "just worked" before is a regression, not a feature. Hence the reason I point it out -- the devs can't fix something unless they know it's broken, and I seriously doubt the devs are able to test all/every permutation. I have nothing but respect for the work they do, thus my very respectful tones in my earlier posts. I've had no indication that the devs are unwilling to get feedback about their work.
You asked a question though, and here is the answer:
I leave Wifi on all the time because I'm a consultant -- I work in many different locations throughout the week, travelling the country. I have dozens of wifi networks saved on my phone, and it is useful for me to have my phone automatically jump on the correct, nearest network. I'd rather use free wifi instead of paying AT&T for data charges. It is not always possible for me to remember I'm in a location with a known wifi network, or to remember to manually toggle wifi settings: it is useful for me to have this happen in the background. Sometimes I'm on a call, sometimes I'm heading into a meeting and I'd rather not mess with my phone. I want wifi to be on all time, scanning for the correct network, and jumping on it when it's in range.
Outrageous, right?! Not actually -- this is the existing behavior in CM6 and stock 2.1. From my standpoint, wifi just worked -- I didn't have to think about it, didn't have to manually toggle something to prevent AT&T data charges.
This is desired behavior for me, and I'm happy with rolling back to CM6 to get it. I understand that _you_ don't need this behavior, but that doesn't mean it's wrong. It just means the world is bigger than you realized.
And yes: wifi in CM7 (beta) is currently broken. Read the threads. Many people are having problems with it.
Click to expand...
Click to collapse
fyi CM6 & 2.1 != CM7. Your argument is null & void.
Also, being a "consultant" and the very important man you are, flashing a rom that's not even in beta stages yet probably isn't the best idea you've ever had.
zervic said:
Also, being a "consultant" and the very important man you are, flashing a rom that's not even in beta stages yet probably isn't the best idea you've ever had.
Click to expand...
Click to collapse
Why do you remind us that the rom is in a beta stage? "Beta" implies it is not fully functional, but your argument all along has been that it works perfectly....
Look, it's clear you haven't actually understood any of my posts. I'm highlighting error messages or erratic behavior I see in logcat running CM7. I've posted what I've seen so the devs can take action, or not, as they choose. Since you aren't in that audience I don't understand what your beef is.
Oh wait! Straw man arguments; personal attacks; logical fallacies: I've been dealing with either a highschool student or a troll - not sure which.
zervic said:
fyi CM6 & 2.1 != CM7. Your argument is null & void.
Click to expand...
Click to collapse
...although I have a strong suspicion.
kinggrowler said:
Why do you remind us that the rom is in a beta stage? "Beta" implies it is not fully functional, but your argument all along has been that it works perfectly....
Look, it's clear you haven't actually understood any of my posts. I'm highlighting error messages or erratic behavior I see in logcat running CM7. I've posted what I've seen so the devs can take action, or not, as they choose. Since you aren't in that audience I don't understand what your beef is.
Oh wait! Straw man arguments; personal attacks; logical fallacies: I've been dealing with either a highschool student or a troll - not sure which.
...although I have a strong suspicion.
Click to expand...
Click to collapse
First of all:
attn1 said:
Just because something does not work they way you'd like it to doesn't mean you've discovered a bug.
Click to expand...
Click to collapse
That being said. Beta does NOT necessarily imply that thing are not fully functioning, it simply implies that it hasn't been put into RC or stable. You can have a fully functioning beta program. HOWEVER, it may not be working properly. But creating a thread about an issue that's been brought up 20+ times now is pointless. I'm PRETTY sure the devs know about the issue, should it actually be an issue. Now that I just wasted another 15 seconds of my life, i'm going to casually /part from this thread and I'll end my post with this quote again, in case you didn't catch it the first time.
attn1 said:
Just because something does not work they way you'd like it to doesn't mean you've discovered a bug.
Click to expand...
Click to collapse
This is for OP and very important man of the day, kinggrowler:
http://forum.xda-developers.com/showpost.php?p=11171075&postcount=1054
and i'll even quote it directly for you:
attn1 said:
There are no broad wifi issues to resolve, and I do not plan to change the wifi driver one iota. I am using the one that works right for most people, and flawlessly for me.
If you are not having such luck, then you need to look at your access point if you have already wiped data.
Really, the constant carping about wifi is absolutely pointless.
Click to expand...
Click to collapse
I believe the proper thing for me to say right now would be:
game. set. match.
Me too. I can't roam between networks, either. I have to disable and re-enable the wifi each time.
zervic said:
...what's the point of having wifi enabled if you're not in range of your network?
Click to expand...
Click to collapse
1) Because Google Maps uses known wifi hotspots to help establish your location.
2) So that you don't have to keep toggling wifi on and off when moving between hotspots (or home and work, for example).
3) To use the network notification feature (aka "notify me when an open network is available").
HTH
Edit: seems to be fixed in RC3!
zervic said:
What is the point of having wifi set to ON when you are not in range of a network? Hence why, if you are using CM7 or CM6, you should utilize the notification widget and turn wifi off if you know you're leaving the area of your network. It's simple. Things aren't ALWAYS going to work how YOU want them to work. Thing will not always be automatic. I think I quote attn1 when I say this, just because it doesn't work how you want it to work, does not mean it is broken.
Click to expand...
Click to collapse
i have try everything and still same issues with wifi. and i change the radio ( baseband ). still i am thinking of uninstalling it bc i dont have wifi
Sorry to tell you but that was with the old wifi stuff (every nightly up to build 25), which I had no problem with. The RC/nightlies have new wifi data made by jznomoney, which I have on and off problems with. Its working for most people but there are a handful who are having problems. I flashed ladios' kernel and my wifi is doing a lot better with the new RC/nightlies.
Signatures are fancy.
kinggrowler said:
I've made sure to set Wifi Sleep Policy to "Never" but that did not fix my wifi problems. What I see when I open Wifi Settings is a cycle of:
Code:
Scanning --> Connecting --> Disconnected... Scanning, etc
When I look in logcat it shows it attemping (in vain) to authenticate against the last wifi network I was using -- even though it is no longer in range (and clear across town). In a nutshell it is refusing to recognize the actual nearby network UNTIL I toggle wifi settings.
Click to expand...
Click to collapse
I've noticed something similar with CM7 on my Aria. When I leave the house and come back it doesn't always connect automatically and it will enter into this cycle of scanning, connecting, disconnected.
I had to reboot the phone to get it to stop the cycle and stay connected. I don't use a lot of data anyway but I still prefer to use wifi when available. Interestingly just now it wouldn't even see any of my neighbor's wifi networks at all which is odd.
EDIT: This issue appears to have been solved. the newest ril2 and a recent radio for your CDMA handset should do the trick. Thanks muzling, arrrggh and hyc.
The bug seems to vary for people. My signal pretends to be lost after each call, and sometimes after texts. It will still receive calls, but I have to toggle airplane mode if I want to call out or text out.
I don't make many calls so the bug hasn't bothered me much, but I had to make a bunch of calls today while on the road, so toggling airplane mode after each one actually got on my nerves a little. I was going to ask if there were any tasker users here to try out some things, but apparently tasker offers a 7 day trial straight from their site, so I decided to try it out. It crashed on its first run, but seems to be running fine now on FRX07.
It took a few tries, but it seems to be working with this combo.
Profile 1: context -> application -> phone; task-> variable-> Set Variable -> %CALL to 1
Profile 2: context -> application -> phone (NOT); task-> variable -> Set Variable -> %CALL to 0
Profile 3: context -> state -> variable -> %CELLSRV matches "noservice"; task -> Phone -> Radio -> Toggle (if %CALL matches 0); task 2 -> Phone -> Radio -> Toggle (if %CALL matches 0)
My first try had the phone hanging up on me during a call. I figured maybe the phone was reporting no signal before the hangup, so I added profiles 1 and 2 and the user var %CALL to limit the radio toggle to when the phone app wasn't in the forefront. For now at least, it seems to reconnect within a couple of seconds of hanging up. Color me happy.
Links of interest:
Quick tour of avail contexts and actions || User Guide
My next task is figuring out a way to toggle the speaker when I first dial out. It always spits some fuzz when I begin outgoing calls unless I toggle the speakerphone on and off. I haven't found an appropriate context yet (application -> phone would toggle unnecessarily for incoming calls as well, not sure if %SPHONE would detect the speakerphone as being on during the bug), but hope springs eternal.
Interesting solution...
I would much rather figure out the root cause (with a fix in theory to follow), but in the meantime anything to help with sanity is always welcome. Kudos.
Thanks. Root causes are definitely the way to go, I'm just not smart enough to aid and assist on that level. Noticed enough complaints about signal loss, I thought some others might benefit from the profiles.
Tasker is no mortscript, but it seems the closest android analog. I used to kind of enjoy scripting away at winmo's faults, and hope I might be able to smooth some rough edges in my android experience too.
Thanks... I just installed Tasker and added the profiles as you said and will report back if it helps me with the signal loss.
Would you mind telling me why you put the same task twice in the last profile? Thanks
Daved+ said:
Thanks... I just installed Tasker and added the profiles as you said and will report back if it helps me with the signal loss.
Would you mind telling me why you put the same task twice in the last profile? Thanks
Click to expand...
Click to collapse
The first toggle turns off the cell radio, the second turns it back on.
After several days of trials, I ran into an instance (when my phone was a little laggy anyway) where it was endlessly turning on and off, apparently because it was detecting noservice multiple times before the toggle was complete. I haven't done this yet, but adding a several second delay into the mix should prevent loops.
Hope it helps!
signal loss?
signal icon show no signal or signal strength zero level?
Which radio version you use?
I dunno, no signal or no service (incoming stuff still works though), I think it's a little x where the signal bars would be. It's a common enough issue, see the FRX07 thread. I'm using whatever radio is bundled with FRX07.
fortunz said:
I dunno, no signal or no service (incoming stuff still works though), I think it's a little x where the signal bars would be. It's a common enough issue, see the FRX07 thread. I'm using whatever radio is bundled with FRX07.
Click to expand...
Click to collapse
I think he means radio firmware - it's flashed in bootloader mode, and usually comes with stock ROM's... Basically it's completely independent of our Android port.
I'm curious, did you try hyc's updated RIL? There was a slight bug that seems to be helping all sorts of issues, it was related to incoming calls...
arrrghhh said:
I think he means radio firmware - it's flashed in bootloader mode, and usually comes with stock ROM's... Basically it's completely independent of our Android port.
Click to expand...
Click to collapse
Oh, thanks. I don't believe I've made any changes to that. Whatever came with the phone from the factory.
I'm curious, did you try hyc's updated RIL? There was a slight bug that seems to be helping all sorts of issues, it was related to incoming calls...
Click to expand...
Click to collapse
Downloaded it, haven't put it in place yet. Last post I saw had someone recanting on it fixing an issue like this one, but it's worth a try.
hyc's updated RIL not support all radio firmware version,
I encouted the same problem with you when use an special radio, try to use newest radio ( http://forum.ppcgeeks.com/cdma-tp2-...10-rhodium_w-radio-roms-mirrors-included.html )
You can upload your ril's logs,use command "adb logcat -b radio",when signal icon show x, there must be an error like "system need return success, but ril return fail"
It's late, goodnight.
Thanks guys, newest vzw radio and newest ril fixed it.
Can more people contact Viber team and push them to fix this "bug"?
When you set Wi-fi sleep policy to "When screen turns off"
Viber actually prevents this setting and keeps Wi-fi on all the time.
I don't like having an app that overrides my system settings and Viber should disable this "feature"
When I uninstall Viber then my Wi-fi sleep policy works the way I set it up.
I have contacted Viber team for some weeks ago but it seems that they don´t care about one single user.
We need to push them, if I want my phone to use 3G/GSM when screen is off it´s my choice, not vibers.
Please support!
Edit: Viber team has responded and is finally fixing this bug!
There probably doing you a favour i get much better battery leaving wifi on and not 3g.
mynamesteve said:
There probably doing you a favour i get much better battery leaving wifi on and not 3g.
Click to expand...
Click to collapse
But not all people, SGS2 gets some drain with some routers and my battery last longer on 3G, but i prefer the speeds on my wifi and want to use it when my screen is on.
I have great 3G reception in my area so 3G is best for my battery when idle.
So I don´t need a bloody favor from viber, I want to set up my phone the way I want.
rodak said:
I want to set up my phone the way I want.
Click to expand...
Click to collapse
right, in the spirit of android.
HearthC0re said:
right, in the spirit of android.
Click to expand...
Click to collapse
Viber is written in the spirit of iOS
Hi,
This is a member of the Viber Development Team.
This is something that has been brought to our attention by many users such as yourself, and it is definitely a priority for future development.
@rodak - Thank you for pushing us a little harder, just don't push us over the edge
Please feel free to let us know your thoughts, questions and comments.
Thanks,
Viber Team
Viber Team said:
Hi,
This is a member of the Viber Development Team.
This is something that has been brought to our attention by many users such as yourself, and it is definitely a priority for future development.
@rodak - Thank you for pushing us a little harder, just don't push us over the edge
Please feel free to let us know your thoughts, questions and comments.
Thanks,
Viber Team
Click to expand...
Click to collapse
Thank you for your response.
I really like your app and use it all the time, but this "feature" is really bugging me since it impacts on my battery life.
Hope you fix it soon, and no, I wont push you over the edge
Like everything else about the app and don´t care about emotions and other stuff that I saw other people are requesting.
As long as I can call my friends and still have control over my settings i´m fine.
Thanks for an almost great app
very good ,thanks
+1
Can somebody let us know here when its fixed
So I can reinstall it
Viber keeps WiFi alive because it naturally thinks you intended to keep it available.
Might be a dumb question, but why aren't you simply disabling WiFi when you go to skeep at night? According to what you're saying, you want your WiFi to shut down the second your screen is turned off. After that, it will be deactivated for hours and hours until you wake up anyway.
See my point?
Viber Team said:
Viber keeps WiFi alive because it naturally thinks you intended to keep it available.
Might be a dumb question, but why aren't you simply disabling WiFi when you go to skeep at night? According to what you're saying, you want your WiFi to shut down the second your screen is turned off. After that, it will be deactivated for hours and hours until you wake up anyway.
See my point?
Click to expand...
Click to collapse
You have misunderstood the whole thing.
We want wifi to sleep when phone sleeps, not when we are going to bed.
Some routers drains battery more than 3G if you have good 3G signal.
So I only want to use wifi when my screen is on. Just because greater speed. But when I turn off my screen I want wifi to sleep and 3G to take over. Just to save battery.
No other apps I have keeps wifi alive and I have 70+ apps installed.
Android users want to control the settings the way they want.
We don't need an app that "assumes" that we want wifi to be kept alive.
See my point?
Sorry to say but the only thing that keeps me away from viber is this stupid wifi keep alive "bug".
Sent from my GT-I9100 using Tapatalk
Go to wifi settings, advanced. There you see wifi sleep policy. Under this you see 3 options you can make.
They are there for a reason. Some users want wifi to sleep when phone sleeps. Some want it to be on the whole time, and some only when the phone is plugged to charger.
If it was supposed to have wifi on all the time this options would not be there.
I want to control my own settings, don't need Viber team to control this for me.
Should be illegal!
Sent from my GT-I9100 using Tapatalk
@rodak -
We fully understand your criticism and respect your will to control your own Android.
However, please note that the number of users that want their 3G to be kept on instead of their WiFi does not make up the majority, and in fact makes up an extremely small percentage of users. At the Beta stages we tried implementing this feature for some of our testers, and this resulted in receiving multiple complaints from users that their Viber was not working properly. When we dug deeper we realized that this was the issue. Apparently, there are quite a few users that somehow accidentally turned this feature on, but did not realize that they did.
As such, we do not believe adding an extra "turn off WiFi" option is needed. It would merely serve to unnecessarily complicate the application. We are sorry if this is not the answer that you were looking for, but we need to make sure that adding features that would make some happy would not hurt other users.
Viber Team said:
@rodak -
We fully understand your criticism and respect your will to control your own Android.
However, please note that the number of users that want their 3G to be kept on instead of their WiFi does not make up the majority, and in fact makes up an extremely small number of users. At the Beta stages we tried implementing this feature for some of our testers, and this resulted in receiving multiple complaints from users that their Viber was not working properly. When we dug deeper realized that this was the issue. Apparently, there are quite a few users that somehow have this on, but do not know about it.
As such, we do not believe adding an extra "turn off WiFi" option is needed. It would merely serve to unnecessarily complicate the application. We are sorry if this is not the answer that you were looking for, but we need to make sure that adding features that would make some happy would not hurt other users.
Click to expand...
Click to collapse
Total fail viber.
As mentioned over 70 apps installed and only viber gets in the way of my settings.
Why not simple add this word in vibers description:
If you want viber to run at wifi all the time, simple change your wifi sleep policy to never under wifi settings.
Or just a simple "wifi always on" on/off switch in the app.
But you go iOS style, control stupid users that should have a dumbphone and can't change their own settings. So lets put them in "jail" and control their life.
Sent from my GT-I9100 using Tapatalk
rodak said:
Total fail viber.
As mentioned over 70 apps installed and only viber gets in the way of my settings.
Why not simple add this word in vibers description:
If you want viber to run at wifi all the time, simple change your wifi sleep policy to never under wifi settings.
Or just a simple "wifi always on" on/off switch in the app.
But you go iOS style, control stupid users that should have a dumbphone and can't change their own settings. So lets put them in "jail" and control their life.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Rodak,
Again, we understand your point completely. We don't regard our users as stupid, and never have we done so. Among the Android community we get many, *many* requests and suggestions like the one you are making. We welcome the criticism and requirements - that's why we have representation in forums!
However, please bear in mind that we are not able to comply with everyone's demands all the time. By itself, adding the option of "non-sleep wifi" button on/off isn't technologically complex of course, but doing so will again raise the previous problem. Users who accidentally use this feature will have their WiFi go to sleep. They will receive Viber calls (who will now use their 3G connection) and the sound quality will be disrupted, thus creating even more negative comments and complaints, etc etc.
When your product serves tens of millions of users it is hard to find the balance between all the requests. In this specific story, we are compelled to go with the preference of the large majority. We understand the inconvenience caused to others (like yourself) and we apologize for it, but by no means do we keep "insisting for no reason" because we believe our users are dumb. Trust us, all we do all day is listen to our users. I think XDA is the best example
This was the reason i left viber, and you dont need an extra button, you should not override the system settings, without telling your users. That's just bad policy.
If you don't want to use common sence and make your app listen to your users device settings, the least you should do is to tell them about it.
Your answer is also just a sign of lack of respect, you can talk about the community all you want, and how complex your problem is, but fact remains. You dont give a **** about our settings, and therefore you can write a whole seminar for all i care, it's just wrong to do this.
I dont want an extra option viber team, i already have this option to set my wifi sleep policy, why would you deny me the right to change this without telling me?
verrox said:
This was the reason i left viber, and you dont need an extra button, you should not override the system settings, without telling your users. That's just bad policy.
If you don't want to use common sence and make your app listen to your users device settings, the least you should do is to tell them about it.
Your answer is also just a sign of lack of respect, you can talk about the community all you want, and how complex your problem is, but fact remains. You dont give a **** about our settings, and therefore you can write a whole seminar for all i care, it's just wrong to do this.
I dont want an extra option viber team, i already have this option to set my wifi sleep policy, why would you deny me the right to change this without telling me?
Click to expand...
Click to collapse
Totally agree verrox. To bad that we don't get more users with us.
But OK, I'll make an app that turns your brightness to Max, turns off autorotate and turns on data roaming. Just to guarantee my users that they see the screen even in daylight, and that they don't get confused if the screen autorotates and last I'll enable the data roaming so they don't wonder why my app doesn't works when they go to another country.
All this is user settings FAILBER TEAM!!!
It's just wrong to manipulate this.
And for your information, wifi kicks back in when screen is turned on, so just keep wifi on during call will be enough. Don't override our settings in the OS. Fail fail fail.
Sent from my GT-I9100 using Tapatalk
rodak said:
Totally agree verrox. To bad that we don't get more users with us.
Click to expand...
Click to collapse
That's exactly the point - if there was a larger number of users requesting it, we would make the change in a heartbeat.
I apologize that you and @verrox feel like we're neglecting your requests, but as explained above - that is not true. Just FYI - I have raised your request all the way up to our CEO, but again - we wish we could help *ALL* users in the world who all had just one very important request. But unfortunately our resources are limited
rodak said:
And for your information, wifi kicks back in when screen is turned on, so just keep wifi on during call will be enough.
Click to expand...
Click to collapse
This unfortunately won't be possible, because there are serious problems of Android itself - it can't handle a clean switch between 3G and WiFi (this has been tested numerous times). We can't trigger the call on 3G, wait for Android to successfully (if at all) switch to WiFi, and only then start the call. The delay cuts the call.
Viber Team said:
That's exactly the point - if there was a larger number of users requesting it, we would make the change in a heartbeat.
I apologize that you and @verrox feel like we're neglecting your requests. Just FYI - I have raised your request all the way up to our CEO, but again - we wish we could help *ALL* users in the world who all had just one very important request. But unfortunately our resources are limited
This unfortunately won't be possible, because there are serious problems of Android itself - it can't handle a clean switch between 3G and WiFi (this has been tested numerous times). We can't trigger the call on 3G, wait for Android to successfully (if at all) switch to WiFi, and only then start the call. The delay cuts the call.
Click to expand...
Click to collapse
Then thank you and goodbye.
As stated before, viber is the only app that overrides my settings and I simply won't accept that.
There is a few more users at Swedish community's that is bothered about you way of interacting with our settings.
There are people that even have wiped their phones just because they thought there was some bug in the software.
Can you imagine how many hours people lay down to just find out that it's viber that keeps the wifi on?
You must type in description: BE WARNED, VIBER WILL KEEP YOUR WIFI ON ALL THE TIME AND IGNORE WIFI SLEEP POLICY. SO NO NEED TO FACTORY RESET YOUR PHONE. IT JUST OUR FAULT!!
I will investigate this and see if there is any legal action that I can take against this.
As I see this, this bull**** that you are doing is illegal.
This is my settings and you are not allowed to override this.
Sent from my GT-I9100 using Tapatalk
Please relax, and let's keep this discussion civilized.
Your idea of adding a message (in Market, for example) that states that Viber needs to keep your WiFi enabled is a good idea. I will certainly pass it on to our management. Thank you!
By the way, it is important to clarify something - Viber keep WiFi on *only* instead of WiFi-sleep policy. By no means does it try to "fight" the manual disabling of WiFi on your Android.
Anyway, I will certainly keep you posted if I have any news. Thank you again for your concern and comments
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.
Hi,
I have rooted android 4.2 tablet.
I would like to destroy my wifi.
If I will remove MAC adress (if it possible??) will it make the job? I thought that would be possible through software code. or remove some systems folder.
also, if there is an option to remove the wifi icon from status bar and also from setting menu that would be great. I will turn it off then remove those symbols.
I need help with those things. if you have other better ideas I'll be happy to hear.
Thank you.
oriels said:
Hi,
I have rooted android 4.2 tablet.
I would like to destroy my wifi.
If I will remove MAC adress (if it possible??) will it make the job? I thought that would be possible through software code. or remove some systems folder.
also, if there is an option to remove the wifi icon from status bar and also from setting menu that would be great. I will turn it off then remove those symbols.
I need help with those things. if you have other better ideas I'll be happy to hear.
Thank you.
Click to expand...
Click to collapse
This by far is the strangest post I have ever encountered in all my time on xda, anyway, I don't think it's possible, atleast with simple ways, for removal of options from quick tiles and settings you will need to mod the settings and systemui which will make it impossible to access wifi on/off option which in turn will remove wifi in a sense. But doing it takes some advanced knowledge on the workings and manipulation of Android system files.
Mufrad said:
This by far is the strangest post I have ever encountered in all my time on xda, anyway, I don't think it's possible, atleast with simple ways, for removal of options from quick tiles and settings you will need to mod the settings and systemui which will make it impossible to access wifi on/off option which in turn will remove wifi in a sense. But doing it takes some advanced knowledge on the workings and manipulation of Android system files.
Click to expand...
Click to collapse
:laugh: I need it to block the internet for some reasons.
Does it possible with any firewall or specific app to block the internet?
oriels said:
:laugh: I need it to block the internet for some reasons.
Does it possible with any firewall or specific app to block the internet?
Click to expand...
Click to collapse
I don't think any app will help you turn wifi off if someone intentionally wants to use wifi on the device, a firewall can only stop apps from accessing the internet. But maybe you can try a method that I am not 100% sure about but it worked for some people, go to build.prop the find the lines;
wifi.interface=
wifi.supplicant_scan_interval=
And delete them, or if those lines aren't present then go to system>etc>wifi, find the files which are named "bcmdhd_" and delete them and reboot, but I definitely recommend taking a backup with a custom recovery before doing either of the two because these edits might cause adverse side effects or might bootloop your device, so use caution. Hope it helps.
Mufrad said:
I don't think any app will help you turn wifi off if someone intentionally wants to use wifi on the device, a firewall can only stop apps from accessing the internet. But maybe you can try a method that I am not 100% sure about but it worked for some people, go to build.prop the find the lines;
wifi.interface=
wifi.supplicant_scan_interval=
And delete them, or if those lines aren't present then go to system>etc>wifi, find the files which are named "bcmdhd_" and delete them and reboot, but I definitely recommend taking a backup with a custom recovery before doing either of the two because these edits might cause adverse side effects or might bootloop your device, so use caution. Hope it helps.
Click to expand...
Click to collapse
Thank you.!!
I found that line: "wifi.interface=wlan0" but didn't found "wifi.supplicant_scan_interval=".
Anyway I deleted that line. At first WI-FI woreked well but after reboot it stoped.
Now it show "WIFI" symbol and I can enter to wifi interface but he can't find any of the lans available. and the lans I used to connect it say "out of range" even I near the router. That enough for me and that is what I wanted.!!
Thank you!
oriels said:
Thank you.!!
I found that line: "wifi.interface=wlan0" but didn't found "wifi.supplicant_scan_interval=".
Anyway I deleted that line. At first WI-FI woreked well but after reboot it stoped.
Now it show "WIFI" symbol and I can enter to wifi interface but he can't find any of the lans available. and the lans I used to connect it say "out of range" even I near the router. That enough for me and that is what I wanted.!!
Thank you!
Click to expand...
Click to collapse
No problem, glad I could help you out. Still the strangest request ever. Lol. Take care buddy.