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.
Related
My buddy's HTC Eris cannot connect to our work WIFI.
His Phone: Gingerbread 1.6RC1
Our network: Hidden SSID WPA2+TKIP+AES
Before you ask, yes, I've entered in the SSID and Password manually.
I've tried Hidden SSID enabler, I've tried setting the IP to static... no dice. No one seems to have a solution or a reason why this happens. The best advice they give is to unhide the SSID. While I agree, I can't, because this is a work WiFi network. Not my router, not my policy.
Does anyone know if there's a radio update for the WiFi or a way to get it working? I thought the custom rom would fix it, but it doesn't. The LG Swift and Moto Droid both connect, no problems.
I've helped others with issues like this for the Eris and usually turning off TKIP solves the problem. For some reason, TKIP causes issues, and though you'd think that having AES as well would fix that, it may be that the Eris tries to use the "easy" method of TKIP and then fails.
That said, TKIP and WPA2 means that it is not exactly following the standard - I think that WPA2 is supposed to use CCMP/AES only. (It's actually a sort-of misnomer to say TKIP vs. AES - TKIP is to CCMP as RC4 is to AES. Or, in other words, TKIP uses RC4 as a cypher, while CCMP use AES.)
Anyway, the other possible issue is that the Eris is b/g only - if that router is a or n only, the Eris will not work.
It seems rather silly these days to be using SSIP hiding with WPA2 - anybody who wants to break in will get around SSID hiding easily, but will only get around WPA2 through brute-force cracking, and WPA2 will keep casual drive-by people out anyway - but, as you say, it's not your router. I'm not sure if you'll have any luck getting the folks who run it to change it to CCMP/AES only if you can't get them to unhide the SSID.
What doogald told you is spot on.
The only thing that I can add to what he said is that - unfortunately - it is quite typical with WiFi to run into interop problems when mixing gear from different vendors. That's not supposed to happen - but it in fact it happens all the time.
I ran into a case where Eris successfully negotiated an association with a older WiFi router (with AES+TKIP+WPA2), got an IP via DHCP from the AP.... and then was completely unable to communicate via IP - not even a ping. This particular problem was solved by updating the router firmware to a newer version.
I have beacons supressed on my WiFi router (although I completely agree with doogald that it provides NO extra security, despite popular misconceptions to the contrary), and sometimes my WiFi connection does not come up straight away - sometimes using the WiFi Scanner app (by farproc) seems to do something to kickstart the association/authentication. (The other thing you might give a try is this - if the PSK is a series of hex characters, check to see that it is not a simple matter of the case of the a-f characters being wrong. iirc, WPA2 uses string values rather than hex, so case sensitivity can pop up from time to time if network admins had a past history of using hex strings for WEP)
Usually, fixing a problem like this is a matter of trial and error; you try and eliminate or change one behavior at a time until something changes. (e.g. the B/G/N multi-mode behaviors, or turning beacons back on.) Generally, because there are more knobs to turn on the WiFi router, that's the place to start.
If you are in a position where the WiFi router can not be touched - well, you might be SOL, as there's precious little you can easily tweak on the Eris**
bftb0
**PS I suppose that it is possible that if we are talking about a rooted phone, you could dig in to configuration options for the "wpa_supplicant" process on the Eris - "wpa_supplicant" is based off of open source code, so perhaps a configuration file could - if nothing else - encourage it to be a little more verbose so you can detect what the error is.
bftb0 said:
I have beacons supressed on my WiFi router (although I completely agree with doogald that it provides NO extra security, despite popular misconceptions to the contrary), and sometimes my WiFi connection does not come up straight away - sometimes using the WiFi Scanner app (by farproc) seems to do something to kickstart the association/authentication.
Click to expand...
Click to collapse
I hate to go a little off-topic, but this happens to me with Froyo and GB ROMs (not with the Eclair ROMs), and I am not hiding the SSID. I actually think it has more to do with the kernel (Conap's CFS or BFS vs. Zanfur) than it does the Android version, though I could be wrong about that.
Anyway, here is what I noticed: in 2.2 or 2.3, if I turn on the WiFi radio using a widget, or just a setting toggle in an app like Quick Settings, it takes about 5-10 minutes before it finally connects to the access point. However, if I follow the settings->wireless & networks and then check WiFi to enable it, it will make the connection in a matter of seconds - every time; it's 100% repeatable. With a 2.1 ROM running Zanfur, no matter how I turn on WiFi, it reconnects every time within seconds.
I've tried looking at logs but I haven't seen anything obvious to suggest that there is some issue.
This is just a question for you two or anyone else who knows. Has there ever been a reported problem with anyone's Eris WIFI when using JIT? I'm just grasping at straws here.
Also, thanks doogald for the information regarding TKIP and AES. I don't recall if I ever researched this stuff before, but if I had, evidently it hadn't sunk in. I'm sure I could've found the information if it was actually important enough for me to, but I have often wondered about some of the "options" available in setting up wireless networks.
doogald said:
I hate to go a little off-topic, but this happens to me with Froyo and GB ROMs (not with the Eclair ROMs), and I am not hiding the SSID. I actually think it has more to do with the kernel (Conap's CFS or BFS vs. Zanfur) than it does the Android version, though I could be wrong about that.
Anyway, here is what I noticed: in 2.2 or 2.3, if I turn on the WiFi radio using a widget, or just a setting toggle in an app like Quick Settings, it takes about 5-10 minutes before it finally connects to the access point. However, if I follow the settings->wireless & networks and then check WiFi to enable it, it will make the connection in a matter of seconds - every time; it's 100% repeatable. With a 2.1 ROM running Zanfur, no matter how I turn on WiFi, it reconnects every time within seconds.
I've tried looking at logs but I haven't seen anything obvious to suggest that there is some issue.
Click to expand...
Click to collapse
In case you don't already know this, a long time ago I learned that differen't widgets ways of toggling things like 3G and WIFI may differ slightly, and some widgets methods may cause problems or delays where other widgets with different methods may work without any trouble. I use the EasySwitch app myself, I actually paid for it. I would suggest at least trying the trial version and see if that helps any.
roirraW "edor" ehT said:
Also, thanks doogald for the information regarding TKIP and AES. I don't recall if I ever researched this stuff before, but if I had, evidently it hadn't sunk in. I'm sure I could've found the information if it was actually important enough for me to, but I have often wondered about some of the "options" available in setting up wireless networks.
Click to expand...
Click to collapse
You're very welcome.
roirraW "edor" ehT said:
In case you don't already know this, a long time ago I learned that differen't widgets ways of toggling things like 3G and WIFI may differ slightly, and some widgets methods may cause problems or delays where other widgets with different methods may work without any trouble. I use the EasySwitch app myself, I actually paid for it. I would suggest at least trying the trial version and see if that helps any.
Click to expand...
Click to collapse
Thanks for the suggestion, and I will try it just to see. I do know that the Cyanogen notification bar widget, plus the Android standard Power Control Widget, has this issue with all of the Froyo and GB ROMs that I have tried, and I think I even had this issue when I installed Conap's BFS or CFS on xtrROM as well. Again, it doesn't happen with the Zanfur kernel in a standard 2.1 Eris ROM that you'll find here.
What I like about Quick Settings (https://market.android.com/details?id=com.bwx.bequick&feature=search_result) allows you to tap the WiFi wording (not where it has an on/off toggle button, but anywhere else on that line) it will bring you to settings->Wireless & Networks directly. Nice little app.
roirraW "edor" ehT said:
This is just a question for you two or anyone else who knows. Has there ever been a reported problem with anyone's Eris WIFI when using JIT? I'm just grasping at straws here.
Click to expand...
Click to collapse
Sorry, I forgot about this with my last post.
I tend to doubt that JIT would have anything to do with WiFi issue. If I am not mistaken, the JIT that we are talking about is just in time compiling for the Dalvik virtual machine, and I am fairly certain that WiFi operations are handled by Linux on the phone, not by Dalvik. Perhaps I am wrong about that, though.
That said, I ran GSB for a day or so before I realized that JIT was turned off by default, and it had that same issue with delayed connection. It's actually one of the first things I test with a new ROM...
And I am also pretty sure that I have seen issues with people whose router was set to TKIP (it's usually WPA rather than WPA2, where TKIP is more likely than WPA2) with stock Eris (and the Hero, I might add), which, of course, is not JIT.
roirraW "edor" ehT said:
I use the EasySwitch app myself, I actually paid for it. I would suggest at least trying the trial version and see if that helps any.
Click to expand...
Click to collapse
doogald said:
Thanks for the suggestion, and I will try it just to see.
Click to expand...
Click to collapse
As it turns out, EasySwitch Trial is set to run up to 2.2 only. It doesn't show up in the market on 2.3, and it wasn't until I went to market.android.com that I learned that it's not compatible with my GB device.
I will try it the next time I go back to Froyo, though.
doogald said:
You're very welcome.
Thanks for the suggestion, and I will try it just to see. I do know that the Cyanogen notification bar widget, plus the Android standard Power Control Widget, has this issue with all of the Froyo and GB ROMs that I have tried, and I think I even had this issue when I installed Conap's BFS or CFS on xtrROM as well. Again, it doesn't happen with the Zanfur kernel in a standard 2.1 Eris ROM that you'll find here.
What I like about Quick Settings (https://market.android.com/details?id=com.bwx.bequick&feature=search_result) allows you to tap the WiFi wording (not where it has an on/off toggle button, but anywhere else on that line) it will bring you to settings->Wireless & Networks directly. Nice little app.
Click to expand...
Click to collapse
Oh yeah, I remember Quick Settings. I used to use that a lot for the first few months I had my Eris (I had rooted immediately), before I went to EasySwitch.
doogald said:
Sorry, I forgot about this with my last post.
I tend to doubt that JIT would have anything to do with WiFi issue. If I am not mistaken, the JIT that we are talking about is just in time compiling for the Dalvik virtual machine, and I am fairly certain that WiFi operations are handled by Linux on the phone, not by Dalvik. Perhaps I am wrong about that, though.
That said, I ran GSB for a day or so before I realized that JIT was turned off by default, and it had that same issue with delayed connection. It's actually one of the first things I test with a new ROM...
And I am also pretty sure that I have seen issues with people whose router was set to TKIP (it's usually WPA rather than WPA2, where TKIP is more likely than WPA2) with stock Eris (and the Hero, I might add), which, of course, is not JIT.
Click to expand...
Click to collapse
I see. Thanks for your informed opinion!
doogald said:
As it turns out, EasySwitch Trial is set to run up to 2.2 only. It doesn't show up in the market on 2.3, and it wasn't until I went to market.android.com that I learned that it's not compatible with my GB device.
I will try it the next time I go back to Froyo, though.
Click to expand...
Click to collapse
Ah! Well, that is a bummer. Although, actually, I wasn't using EasySwitch under CM6 since it had the notification bar widgets. Does CM7 have those yet? That would probably be a deal breaker for me until I could at least use one of those under GB, which I haven't tried yet.
roirraW "edor" ehT said:
Ah! Well, that is a bummer. Although, actually, I wasn't using EasySwitch under CM6 since it had the notification bar widgets. Does CM7 have those yet? That would probably be a deal breaker for me until I could at least use one of those under GB, which I haven't tried yet.
Click to expand...
Click to collapse
Yep, CM7 sure does have those.
doogald said:
Yep, CM7 sure does have those.
Click to expand...
Click to collapse
Oh, good. I'm not positive if I'll try a CM7 build until a final release or not, anyway. Thanks for the info.
Hey guys
I just installed the leaked AT&T ICS (the CWM version that's been posted), and so far everything's generally great.
However, ever since I upgraded to ICS, my phone has been downloading data like crazy over WiFi. Oddly enough, this has happened on my phone before as well when I was using GB, and I believe it also occurred then right after a reinstall.
It's incredibly annoying because whatever the phone's downloading, it seems like it's using a lot of bandwidth because any other internet-related activities I try and do take *forever*. I've rebooted the phone several times, tried stopping every service that I can, and turned off all auto account sync stuff. It's been several hours since I installed ICS, and it's still going.
I'm going to let it sit overnight and see what it's doing in the morning, but even if this is only a temporary problem it's REALLY annoying. Especially since if it's not done doing whatever it's doing by morning, I won't be able to use cellular data on it because I only have the 200 MB plan and don't feel like losing my entire volume for the month because I can't stop my phone from downloading.
Any ideas as to what's causing this? Like I said I'm pretty sure this isn't an ICS-specific problem because it happened under 2.3.4 also, I just want to be able to shut down whatever's doing this excessive downloading. And I'd love to know *what* exactly is being downloaded that's it's taking so long and using so much bandwidth.
Thanks for any help you guys can lend
If you do switch to data to let it pull it down, you can use the data usage in the settings to see what app is doing it. My Data Manager (free in the Play Store) can also monitor data, on cell data and wifi. That would also tell you what app is doing it.
I would guess you either have a ton of data in your Google account, such as contacts, calendar, Gmail, or you have an app that is trying to sync data down. I'm guessing you are restoring apps, then notice the data draw. Think about any apps you have that may sync data back and forth. If you sign into your Google account at initial set up, it should (depending on settings) automatically download and install your apps. But, that should be apparent, you should see the downloads as it does them app by app.
All that is based on guesses of what I would consider "normal" behavior after installing a new ROM.
Good luck tracking it down. :thumbup:
Sent from my Galaxy S II (i777)
Settings > Data Usage
Check what is using it, and listing what APKs you added might help.
quarlow said:
If you do switch to data to let it pull it down, you can use the data usage in the settings to see what app is doing it. My Data Manager (free in the Play Store) can also monitor data, on cell data and wifi. That would also tell you what app is doing it.
Click to expand...
Click to collapse
Or avoid all that and use the native ICS data monitor.
The weird thing is that I hadn't really done anything to the phone when it started using all the data. My Google account doesn't really have much in it (don't have a ton of contacts, don't use it to back up apps/etc.), and I think the only things I'd done app-wise were updating a couple preinstalled apps (Facebook and Maps, I think), but I hadn't installed anything new yet.
I installed My Data Manager, but it looks like it's already done whatever it was doing. Though, even now the download arrow is constantly lit up on WiFi, but I think whatever it's doing now has something to do with the network I'm on (dorm room) as I've noticed almost constant non-zero download bandwidth being used on my desktop as well when it's on the network. If I turn WiFi off now it isn't constantly using cellular data any more, so thankfully it looks like it's finished with whatever it was doing and the constant WiFi downloading is a network, not phone, issue.
On an unrelated note, I was going to reinstall a tethering app, but figured I'd give a try to the built-in tethering first (don't have a plan). On GB it wouldn't even let me start up the tethering without a plan IIRC, but under ICS the tethering not only starts up, I can even connect my laptop to it. Unfortunately I couldn't get internet access on my laptop though, so I'm guessing there's still a restriction on it. Just found it interesting that you can actually enable the tethering without a plan now.
But there's a more serious problem, however. Is ATT clamping down on third-party tethering? I used to use Barnacle WiFi Tether, so I went to install that from the market. Well, Play tells me the app isn't able to be installed on my device because of carrier restrictions (lame). No problem, I figure, I go to their website and download the apk from there and manually install.
Well, when I try and start tethering using Barnacle, it says "WiFi: Could not set ad-hoc mode of wlan0: Operation not supported on transport endpoint"
Does this mean I'm screwed? Will any third-party tethering apps work? To be honest I'm not really into trying out 5 million different ROMs on my phone and don't really mind TW at all, so I'd prefer to keep it stock. But I use my phone overseas and need to be able to use tethering, and if ATT is really clamping down on third-party apps then I'll be installing a completely stock kernel once one's easily available.
Thoughts? Anyone else experimented with tethering on UCLC2 yet?
Well, never mind regarding the tethering stuff - I'd still be interested anyway to know if ATT is trying to actively prevent you from using it in ICS, but I just flashed the SHOstock2 ROM and I gotta say I'm blown away. Even after using it for a half hour I'm pretty sure I'll never go back to stock again (I'm sure most of you would say DUH to that), has everything I'd want in a ROM and nothing I don't. Default tethering works right out of the box too, so I don't even have to worry about installing another app.
Only kinda weird thing is the data indicator keeps switching between H+ and 3G (I'd post on the actual ROM thread but I don't have 10 posts yet...). I'm only on the 200 MB data plan so I switched it to the wap.cingular APN, but even after doing that it still switches. Data seems fast - and I'm not one to be super-concerned with data speeds since I'm mostly just checking e-mail - so it's not a huge deal, but figured I'd mention it anyway.
hbar said:
Well, never mind regarding the tethering stuff - I'd still be interested anyway to know if ATT is trying to actively prevent you from using it in ICS, but I just flashed the SHOstock2 ROM and I gotta say I'm blown away. Even after using it for a half hour I'm pretty sure I'll never go back to stock again (I'm sure most of you would say DUH to that), has everything I'd want in a ROM and nothing I don't. Default tethering works right out of the box too, so I don't even have to worry about installing another app.
Only kinda weird thing is the data indicator keeps switching between H+ and 3G (I'd post on the actual ROM thread but I don't have 10 posts yet...). I'm only on the 200 MB data plan so I switched it to the wap.cingular APN, but even after doing that it still switches. Data seems fast - and I'm not one to be super-concerned with data speeds since I'm mostly just checking e-mail - so it's not a huge deal, but figured I'd mention it anyway.
Click to expand...
Click to collapse
The data switching is normal. The device idles on 3g to save battery and kicks up to 4g when it needs the speed. Stock roms hide this behavior by showing the 4g icon even on 3g
Sent from my SGH-I777 using Tapatalk 2 Beta-4
LiLChris06 said:
Settings > Data Usage
Or avoid all that and use the native ICS data monitor.
Click to expand...
Click to collapse
I never thought to press the menu key in there, there is no indication there are more options. By default it doesn't show wifi data, but on my TouchPad running CM9, that's all it shows. Guess I shouldn't have assumed the ICS wouldn't be without menu use fragmentation like every other android version.
Yeah, the data switching on a custom ROM is normal. Just showing you what the phone actually does. It can save power by reverting back to the 3G vs H when you are idle. The first thing most custom ROMs add is tethering on the built in method. If the leak let you start it up, I'm guessing its incomplete. I would bet att does the same in ICS as GB and has an app to check your account before letting you turn on tethering. Att can detect tethering on the back end too, so if you are caught they warn you first, but you can end up being put on the tethering plan if you keep tethering.
Sent from my Galaxy S II (i777)
Ahh, thanks for the info on the data switching, never knew about that!
I don't use tethering in the US, but I do overseas, which is why I was concerned about ATT blocking tethering apps. However, I realized it's probably not an issue anyway because I'm guessing that tethering wouldn't be blocked with a non-ATT SIM card. Anyway, SHOstock rocks, so it's all good
Also good to know that ICS can monitor WiFi traffic by default - didn't think to hit the settings button on that screen. I gotta admit, that's one huge interface design flaw of Android. There should be some kind of indicator on the screen when there's a menu available, really poor interface design choice to have to hit the menu button randomly to see if any menus are there.
hbar said:
Also good to know that ICS can monitor WiFi traffic by default - didn't think to hit the settings button on that screen. I gotta admit, that's one huge interface design flaw of Android. There should be some kind of indicator on the screen when there's a menu available, really poor interface design choice to have to hit the menu button randomly to see if any menus are there.
Click to expand...
Click to collapse
With new ICS developed devices, most don't include touch buttons... The Nexus for example (using on screen buttons) only shows a menu button when a menu is available...
Cheers.
ALSO- I also noticed what appears to be constant "spurts" of Wifi data usage as well (at least according to my Wifi status bar indicator)... It doesn't seem to affect my Mobile Data, and every data monitoring App (including stock ICS data monitoring) doesn't show the culprit, which leads me to believe that we may be dealing with a system app that is accessing data in the background almost constantly... But only on Wifi. Maybe a location service, or something to do with Syncing? I say system because not even stock Data Monitoring is recognizing an app using data...
Another reason I say this is because I pointlessly wiped my device and started over due to this... "bug"... Only to find that running stock CM9 (with no installed apps) my Wifi indicator still led me to believe my device as downloading spurts of data constantly.
I haven't been able to narrow it down, and am hoping that the issue is fixed in a future software update. - But it is more than likely not an app, just an ICS/CM9 bug.
UPDATE- Just checked a Samsung Epic 4G running CM9 and the bug isn't there... So, it's something specifically within our device and ICS... Again, maybe a System app or Kernel bug...
After a few searches, I still can't find any posts about the exact issue I'm having with my WiFi.
Often my WiFi won't connect to my routers I have saved when I turn it on or leave one location and enter another. It will just sit at scanning until the moment I open the WiFi settings menu, then it suddenly finds routers. I can let it sit for a long time and it still won't find anything until I click the settings, then they pop up and connect automatically like they should.
Is this a common issue, or is i just my X2?
What ROM/android version number are you running? Need more data to tell you what is going on.
It's been no matter what ROM. CM9, Eclipse, stock, it's always done it. Not every time, but randomly hit and miss.
There is a known issue with CM7 not staying connected to wifi, but that was fixed with CM9.
That issue shouldn't happen on stock though. It almost sounds like a hardware issue in your case.
That's what I was wondering. It's been the same since I've had it, and has never gotten worse, so I've just lived with it.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Stuckinabox said:
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Click to expand...
Click to collapse
I have the same symptoms. Even with stock ROM 2.3.5.
Stuckinabox said:
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Click to expand...
Click to collapse
Exactly. I don't ever get disconnects on any ROM. Though while settings can't find any networks is pretty uncommon, it happens.
Stuckinabox said:
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Click to expand...
Click to collapse
Exactly. I don't ever get disconnects on any ROM.
DigitalMD said:
I have the same symptoms. Even with stock ROM 2.3.5.
Click to expand...
Click to collapse
Yup, even with stock. And every ROM I've ever tried.
It's kinda good to know it isn't just me.
I upgraded my phone to KK back in late december and have been on it ever since but one problem has plagued me since then and I'm hoping to get some insight here. heres the problem...
When im connected to wifi (and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.Often i turn my screen on and get a barrage of notifications that i should have gotten hours ago. Ive tried all the sleep modes and Ive tried turning off wifi optimization.Nothing works and I know for fact it did not do this on JB.
I DO get text messages and phone calls instantly though but nothing else will wake my phone up. While i do enjoy the deep sleep, i would like to get my notifications in a reasonable amount of time without having to turn the phone on to check them.
Has anyone else had this "problem"?
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
SteveMurphy said:
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
Click to expand...
Click to collapse
Yeah i know and I've googled it to death for a few months now. I'll check g settings but idk why that would stop gmail. It's like when I'm on Wi-Fi w/ the screen off its just a plain old dumb phone. I turn the screen on and the notifications just flood in.
Edit: nothing in g settings is muted. The only thing i can think of is i don't have app data synced in accounts.
I think i figured it out. I had "sync app data" unchecked in accounts. So far I've been getting notifications screen on and off. Now if someone will just play back to me on wwf...
EDIT: i may have spoke too soon. It still doesnt wake up without turning on my screen
hey @SteveMurphy do you by chance use the active display?
razen_kain said:
hey @SteveMurphy do you by chance use the active display?
Click to expand...
Click to collapse
I did when I was using Omni and it worked great. I haven't used it since running RR, however.
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
razen_kain said:
[...](and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.[...]
Click to expand...
Click to collapse
cyril279 said:
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
Click to expand...
Click to collapse
No i never turn mobile data off. I just meant that notifications come as expected when I'm on mobile data but on Wi-Fi, once the phone hits deep sleep (<a minute) i won't get notifications unless i turn the screen on.
I ask about active display because i remember when on resurrection ROM i was using it and getting notifications then and kind of forgot about it but I'm on PAC 4.4 now and it's doing it again. However i was using the init.d scripts they have baked in but have them all turned back off now to see if that fixes it.
It's the strangest thing I've seen. It's like when I'm on Wi-Fi and turn the screen off it just disconnects from all data even though i can plainly see that it is not. Angela has the same phone with the same settings as mine but on RR 5.0.5 and she gets notifications fine.
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
razen_kain said:
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
Click to expand...
Click to collapse
cyril279 said:
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
Click to expand...
Click to collapse
Well all my testing so far has lead me no where with the exception of using that app. So far, I've not been able to reproduce the problem while using it. The question is,"what is it doing" to make it work....
EDIT: The app does not fix it....
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
razen_kain said:
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
Click to expand...
Click to collapse
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
Click to expand...
Click to collapse
Its 4.4 and I have faced this issue on every rom Ive tried since switching to KK. Im starting to wonder if it's not an issue with my wifi. Im wondering if maybe my wifi is suspending my connection when my phone goes quiet.
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms...
Click to expand...
Click to collapse
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
SteveMurphy said:
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
Click to expand...
Click to collapse
It's always good to have you around buddy.
[SOLVED] Not Receiving Notifications on WiFi
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Great news, glad it was an easy fix!
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
Great news! Now you just need to install DD-wrt on your router and turn it from a $40 router to a $400. I know you like to tinker but check it out. ITs free and its just firmware for certain routers. It turned my old wrt54g into a baus
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
I'm having the same issue with KitKat CM11 ROM on my HP Touchpad (which is WiFi only), and will have to try this. Notifications come in instantly on my iPhone/iPads, but my Touchpad gets some serious delays...sometimes right away, and sometimes delayed.
By the way, did "Sync App Data" setting for an account have anything to do with push notifications, or is that more for backup purposes?
---------- Post added at 02:32 PM ---------- Previous post was at 02:04 PM ----------
Oh darn, mine is still delayed even with the push notification fixer installed and WiFi heartbeat at 5min. Even after I've just rebooted my Touchpad, actively using it, and not even 5 minutes has passed. Delay was 8 minutes and then the notifications came streaming in.
With Android/KitKat, do you have to have the app open in the background for push notifications to go thru? Or run the app at least once after a reboot?
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 :-/