I've had a problem that has been bugging me with my phone for a few months. I have no programming abilities, but was hoping someone here might be able to whip something up.
Whenever network interfaces go down it kills data access for 30-45 seconds. Not usually a huge problem, but I work in a hospital where there is a new router over the same network every 50 yards which knocks out the signal.
I also notice the interfaces switching when I put pandora on in the car. In my driveway I am still pulling from the home router. I lose audio when I the phone switches to 3G then lose it again when it routes to 4G.
My solution: Have a dummy interface that all data is tunneled through. Some service in the background pings all available gateways every X number of packets to monitor which are active. It can then swap between known working interfaces so there is no drop in service.
Problems I'm considering:
1. Power - How much would keeping alive all interfaces and each modem drain the battery?
2. New source IP -- Each time you switch the interface you are connect to a website from a new IP address. Would pandora allow this, it sees it streaming to your account on a.a.a.a and all the sudden you are telling it to stream to b.b.b.b. Same goes if you were logged into your bank account, your logged in and all the sudden their servers see someone choosing links with a different ip address.
I know there are many people on the board much smarter than myself. Could this be done?
Related
Just like the title says, I use xiia player. Im forced to stream off EVDO to avoid the buffering issue but it tends to use more battery than wifi, plus i have dead zones in certain areas of the house. Any thoughts on what it could be?
Also is their a similar app that uses a pre-buffer to avoid or lessen skipping?
Phone setup: 0003
Calkulin 1.7.6 with the included kernel
Netgear dual band N router (WNDR3400) onewave cable internet 10/mbs
I can stream on my loptop, run Netflix on two devices all at the same time with no issues, there's no reason my phone should be buffering every 2 mins even if my phone is the only thing connected at the time.
Could be QoS or WISH on the router or ISP level. Try the following:
1) See if you can listen to the same stream on another device (laptop, etc.)
2) Listen to the stream through another player.
3) Check and see if you're getting this problem with multiple streams from different sites/servers, or just one server.
I remember reading a post (on here?) about similar issues. Something having to do with wifi power settings on the router?
I stream on my loptop and it works fine also the router power is at %100. Im convinced its something goibg on with the phone.
It had something to do with a low power mode setting on the router. Look at your wifi settings for power too... Something in the router had to match this.
I didn't run into the issue myself so didn't pay much attention, but it stuck in my mind.
Thank to a post by duffman in another forum:
Apparently the update changed the settings below to something that disrupts streaming. Whether it is because Sprint wants to redirect this traffic to a proxy server or someone just goofed on the settings, who knows.
Here's the fix:
1) Dial ##3282#
2) Choose Edit Mode
3) Enter MSL
4) Choose Advanced
5) Change HTTP PD Proxy Port to: 0
6) Change HTTP PD Proxy Address to: 0.0.0.0
These are the settings for other Android devices so I do not know why Sprint changed them. But this will get your streaming services working again.
phatmanxxl said:
These are the settings for other Android devices so I do not know why Sprint changed them. But this will get your streaming services working again.
Click to expand...
Click to collapse
Conserve bandwidth, faster response since it doesn't need to go offnetwork...
Proxy's are a double edged sword, good for static content that doesn't change too often.
At my workplace (400+ employees, probably 75 use devices that connect to WiFi, less than 10 on now), IT staff uses MAC filtering on a DHCP server (freeware called PF Sense, if anyone is knowledgeable with that software) that broadcasts IP addresses from the range of 10.10.1.50 to 10.10.1.200 - everything below the last .50 goes to a bunch of access points. This hasn't changed in at least five years, same setup.
IT uses a combination of Linksys and D-Link routers WITH THE DHCP TURNED OFF. This is verified, this is not at issue at all. And WiFi sniffers on two different phones and a MacBook turned up nothing but the EXTERNAL WiFi network (though, obviously, sometimes as many as 3 access points to connect to at one time).
At my work, we've got probably 2-3 city blocks of space here, with the building and myself no closer than 500 feet from the nearest road, let alone other businesses or residences.
Again, no other WiFi networks appear at all.
To be perfectly clear here: I have used this exact setup with no issues going back 2.5 years on both my current Samsung Galaxy S (Sprint Epic 4G) and my former Palm Pre (Sprint).
So here's what's going wrong:
I turn on WiFi, my Android phone running CM9 claims it's connected to "EXTERNAL" (the name of the WiFi network), the WiFi indicator in Android status bar goes blue (meaning has Net access), then it immediately goes gray (connected, no Internet available).
Instead of getting a 10.10.1.1xx IP, Android tells me I've got a 192.168.1.68 (or .21 or .8 or whatever).
Connected to a Cisco/Linksys device (always), and it tells me the following:
Gateway, DNS1 and DHCP server are all: 192.168.1.1.
Subnet mask: 255.255.255.0
IT has nothing that broadcasts this. My phone does not appear in the DHCP lease logs. It doesn't appear to connect on PF Sense's end at all, despite the MAC addresses matching in that system and on my phone. We killed mine out and reentered it. No change.
Of course, my WiFi at home works like a champ (and delivers IPs only above 192.168.1.100). Open WiFi at a McDonald's works. Pass pro WiFi at a local bar works as advertised.
WHAT DA FAAAAAAAAK??
I've reflashed my CM9 rom. I've wiped dalvik and regular caches. I've forgotten ALL WiFi networks and started from scratch.
What am I missing? What could be causing this? IT is stumped, I'm stumped - and I'm on Sprint so getting a data connection here is about as trustworthy as a methhead in a plumbing store.
Have you tried forcing the static ip and manually entering the settings?
Sent from my SPH-L710 using xda premium
I haven't, no. But of course after dealing with this since last Thursday, all of a sudden I'm working fine. :-/
8-D
XD
??????
IT is heading out for hte day, but they're going to check every access point in the building tomorrow.
So, so weird.
It actually sounds like one of the linksys access points may be going rogue on you. The default address for a linksys router is 192.168.1.1. It the linksys dhcp server responds before the main dhcp server, your phone can't get out of the neighborhood.
Sent from my SPH-D700 using xda app-developers app
Almost certainly a rogue access point. All too common for employees to sneak them in or for consumer grade units to behave curiously.
Enterprise wireless systems will automatically detect that sort of thing and contain the unit. It's rather stunning how well that works.
The hospital I used to work for was plagued daily until we properly engaged that security.
Sent from my SPH-D700 using xda developers app
I've been trying to narrow down the battery leech on my Nexus 7. Something is keeping it from going into deep sleep; it will spend more than 80% of its time in wlan_rx_awake and 20% in deep sleep and a few others (with screen off and otherwise idle). For example I just rebooted about 2 hours ago and while PowerManagerService is currently the #1 offender since I've actually been using the tablet, for just wlan_rx_wake I've got 32 minutes and a count of 2204. Last night I saw the count at over 8000 and the majority of the time.
I've blown away the obvious suspects - apps that might be waking my device up like facebook or garbage like that. I've done a lot of googling and UTFSE, and have been monitoring BetterBatterySaver, Network Log, and CPU SPY. There are no single processes or appps that seems responsible on the N7 - I'm thinking it's some sort of wireless broadcasts from my d-link 655. Network log shows a lot of UDP packets from 192.168.0.184 to 255.255.255.255, with source ports either 32805 or 32806 and dest port 1234 or 53274. Some research shows 1234 is VLC USP stream and 53274 TCP is "Xsan. Xsan Filesystem Access" from Apple - but I don't find anything about UDP 52374 192.168.0.184 is my Seagate Goflex Home, my network attached storage device - which is also a media server. I don't use the media server component but it apparently can't be disabled (though I've thought of logging into the goflex via the secret ssh interface and killing the minidlna server for troubleshooting purposes[it's running an embedded linux].) I've already disabled UPnP on it and that didn't change anything. I've also gone to the 2 Windows 7 machines that share the wifi and disabled the IP Helper service; something I read somewhere suggesteted that. It also suggested disabling Shell Hardware Detection, but disabling that service disable Windows Image Acquisition, rendering my wifi-attached HP 3050 scanner inoperable. So I had to leave those running. I'm not seeing a lot of packets from that printer so I don't think that's it - I really am suspecting the Goflex Home.
I wish I could output from Network Log. The Goflex home traffic is broadcast in bursts of about ten packets with anywhere from 1 minute to 45 minutes between. That's why this is my suspect but it could be a red herring. Can anyone offer me suggestions on how to proceed? Is there perhaps a sysctl command I can use to tell the device to go into deep sleep quicker? I suppose I could just have wifi turn off when the screen does but I'd rather not, I like the benefit of having everything sync'd and up to date. For now I've installed DS Battery Saver which just intermittently turns on Wifi. Hasn't been long enough to know if that helps.
Thanks for any help!
tl;dr wlan_rx_wake is keeping my device from deep sleep, leeching battery, and I suspect it's my Goflex Home's network broadcasts but I'm not sure.
Edit: Attached BetterBatteryStats output log
Did you try shutting the NAS down for some time, to really see if that's the culprit ?
Also one idea I've seen is disabling IPv6 on Windows clients in Adapter settings, which connect to the network, but this probably isn't the main case here.
Regarding output from Network log, you can enable monitoring in the app, so the log gets recorded to the storage. You can even filter the output before recording, so it's not crowded.
madd0g said:
Did you try shutting the NAS down for some time, to really see if that's the culprit ?
Also one idea I've seen is disabling IPv6 on Windows clients in Adapter settings, which connect to the network, but this probably isn't the main case here.
Regarding output from Network log, you can enable monitoring in the app, so the log gets recorded to the storage. You can even filter the output before recording, so it's not crowded.
Click to expand...
Click to collapse
I've got it logging, and filtered right now for just the Goflex IP.
I have rebooted the goflex, but not shut down for a period of time. Since it's only a weekly backup server that's not a bad idea.
I have made some progress. I got root on it and killed the minidnla service as well as the mt-daapd service (the latter provided Itunes [and possibly Bonjour] service I learned). Even with those killed I'm getting the same spurious UDP broadcasts with the same UDP ports. Using netstat on the goflex I found that a service called "locator-server" was opening connections to one of the aforementioned remote ports (didn't note which). I can find very little info on this service in google though. The goflex's core is an Axentra so I'd think more info would be available but not that I could find. Here's what's in the startup script for that service:
# locator: UDP broadcast of HipServ's presence
# description: broadcasts UDP messages to announce presence
I *think* that locator broadcast is just for this garbage Seagate dashboard program which is not necessary for the function of the NAS and is not installed. But I'm not sure. I suppose I need to shut it down and see if I lose functionality.
I guess I before I spend more hours on this I need to answer a basic question: does a series of wireless UDP packets to 255.255.255.255 even keep the N7 in wlan_rx_wake state?
Whatever's doing it is hitting it hard, of 2 hours uptime BetterBattery shows 45 minutes wlan_rx_awake right now with 2nd place going to just 2 minutes of PowerManagerService.
Edit: well I killed locator and not 2 minutes later got another burst of traffic from it, to UDP ports 1234, 53274, from 32775 and 32776. I even did "netstat -cap|grep -e 1234 -e 32775 -e 32776" but got no output. Time to shut it off.
Edit: No longer getting the spurious broadcast packets, but the wlan_rx_awake number continues to grow. All apps look normal - google play, mail, currents.
Hm, maybe try shutting down all devices in your network except the phone and router. That's the easiest route to troubleshooting with so many parameters - exclusion.
If this doesn't help, then you might want to borrow another router and after that it must be the phone configuration. But you'll know where to focus on.
A quick google for udp broadcasting to 255.255.255.255 says it might be the Apples Bonjour service. I presume you have some Apple software on the clients, so you might want to check that out. Try my suggestion above to see if it clears up when only the phone is present on the network and you'll know it's the other clients for sure.
Well I did a sort of test like that today - I took it to work. No issues at all with it going into deep sleep or wlan_rx_wake increasing dramatically. My battery lasted all day even with quite a bit of use.
Using Network Log I can easily see which systems are sending out the 255.255.255.255 packets, next step is to narrow it down as to what IP corresponds to what device. I can't shut all devices down, I have roommates.
With the Goflex NAS shutdown, my network broadcasts have dropped dramatically. At work I can use it off and on all day and still have 80% battery with 5 hours deep sleep. I get home and the battery starts to drop faster, and the wlan_rx_wake counter starts rapidly going up. But Network Log shows only normal things like checking email, no suspicious packets. I don't get it - why is it that at home the wlan_rx_wake counter just goes nuts and my battery shoots downwards -- it's now at 64%, down from 80% when I got home four hours ago, and I haven't even touched it.
Then it's the clients or router, if thats also whats left in the network ;] As i said try to troubleshoot those, talk to roomates to shut them down for couple hours or something.. Maybe its just one particular client, with some kind of broadcasting **** which is waking your device.
Sent from my Galaxy Nexus using Tapatalk 2
Do you happen to know does any packet sent to the broadcast address wake an N7 up from deep sleep?
Also shouldn't they be showing in Network Log? It's like wireshark so it should be showing any packets I receive.
You can also go through some tips in here : http://forum.xda-developers.com/showthread.php?t=2133176
The NetBios part was happening in my home network and I saw those in Network Log app.
Thanks, those are good tips I hadn't stumbled across that thread. I don't think I can disable netbios (I'd have to google how to do that anyway); I do my backups and file storage to a Goflex NAS via Windows networking and my wife I and I share some files between our Windows 7 machines. I also can't turn off Shell Hardware Helper service, as it seems to be needed for my network scanner. I did turn off the other services already "IP Helper" and "Windows Media Sharing Service" with no change. I've already got all systems that I have control over getting a static IP from the DHCP server, though I realize that's not the same as setting a static IP. But if I set a static IP I'll have to disable it when I get to work and re-enable when I get home. If I just spent my time on one network that'd work. Actually though for testing I could do a static I suppose. It's not possible in 4.2.2 to set a static IP on one SSID and DHCP on another is it?
Network Log is really not showing much NetBIOS activity anyway - seems like dhcp requests are the most common broadcasts I'm seeing.
Biggest revelation from that thread was that Network Log doesn't capture all packets! - I'd need to put Shark for Android on my N7 then transfer the file to my desktop and use Wireshark to look through it. Ugh, time consuming but I may have to do. Another thing I can try is disable IPv6 on my N7 but it looks like I need to install Android Firewall to get to that setting, it's not accessible otherwise.
Edit: Changed my DHCP leases from 24 hours to 7 days. I found these interesting checkboxes in my router config page though (Belkin d-655):
Enable DHCP Server: X
DHCP IP Address Range: 192.etc to 192.etc
DHCP Lease Time: 25200 (minutes)
Always broadcast: X (compatibility for some DHCP Clients)
NetBIOS announcement: X
Learn NetBIOS from WAN:
NetBIOS Scope: (optional)
NetBIOS node type :
Broadcast only (use when no WINS servers configured) X
Point-to-Point (no broadcast)
Mixed-mode (Broadcast then Point-to-Point)
Hybrid (Point-to-Point then Broadcast)
Primary WINS IP Address: 0.0.0.0
Secondary WINS IP Address: 0.0.0.0
I wonder what would happen if I turned off those two broadcast options....
I tried changing to hybrid mode, then making 192.168.0.1 (my router) as the first address. All sorts of things went awry then. I could get to the internet despite the Network and Sharing Center showing an X. Also when I tried to browse my network, it said File and Printer Sharing service is turned off, do you want to turn on? I'd hit yes and a second later would do again. I went into the Windows 7 settings and everything regarding sharing had been changed to no. So I turned them back on (I also share a printer from this computers) And I reverted back to broadcast only on the router and now I can browse my local network, but the goflex didn't show up under Network until I went there by hand (\\goflex_home\) in an explorer window. Very odd. Maybe I'll just stop wasting time with this before I break something, and just use DS battery saver at home.
Well, I've not made a little progress, my tablet battery can last overnight now. It still spends many hours in wlan_rx_wake (6 hours) though deep sleep is finally beating it (17 hours). The only significant changes I can think of were disabling "IP Helper" and "Windows Media Sharing" services, and disabling DLNA and mt-daapd on my goflex_home. To do that I had to ssh in, and chkconfig'ing them off didn't work - I had to rename their startup scripts /etc/init.d. I think it was the latter that helped the most as Network Log showed most broadcasts coming from it. I'm still curious if any broadcast traffic on the wlan is enough to trigger the N7 to wake up from deep sleep. CPU Spy shows most cpu time in Deep Sleep now, with the next highest being 340mhz.
Hope this info helps someone else.
I am finding many instances where I am getting the cloud icon when I am at home. My watch has both of my access points set up. Sometimes I will get the cloud and I will be 10 feet away from an access point and within line of site while my phone is sitting even less than that from another access point and also in line of sight, and when I check the phone it is connected to wifi.
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
I have also noticed that the watch does not seem to automatically connect to wifi when it loses the BT connection even though I have it set to automatic in the settings.
I am not going to carry my phone all over the house like a goofball so that the watch works. Wifi capability was one of the things I was waiting for for this very reason. It makes the watch WAY more useful...but it actually has to work properly.
brizey said:
I am finding many instances where I am getting the cloud icon when I am at home. My watch has both of my access points set up. Sometimes I will get the cloud and I will be 10 feet away from an access point and within line of site while my phone is sitting even less than that from another access point and also in line of sight, and when I check the phone it is connected to wifi.
Click to expand...
Click to collapse
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
Have experienced the same. However, it may not be the watch problem and may be the Google cloud ☁ service.
vvveith said:
I thought being on the same LAN was supposed to be functionally equivalent to having a Bluetooth connection.
Have experienced the same. However, it may not be the watch problem and may be the Google cloud service.
Click to expand...
Click to collapse
Experiencing the same thing more and more often.
My phone (N6) is connected to either wifi or 4G; my watch connects to wif's as well. Nonetheless when disconnected from bluetooth it disconects completely (The Cloud thingy).
Why? I must be doing something wrong, Android Wear is new to me.
This has been plaguing me for a while and it's making me hate this phone. I've also seen this issue pop around the internet so it's not just me.
What happens is the wifi stays connected to the router but has no connectivity (i've tried pinging the gateway when it happens, the connection is dead although it is listed in the router as connected). And it happens totally random, sometimes it works entire day, sometimes it happens every hour or worse. This seems to have gotten worse with MM. I used to be able to fix it with turning wifi off/on but now even reboot wont help (it connects to the router but immediately says no internet on wifi), i have to reset wifi on the router for it to start working. I have 2 other androids (kitkat, lolipop), an iphone 5, tablet with a hybrid OS, 2 laptops and a desktop on the wifi working without issues so that kinda rules out the router as the sole culprit (it's a Technicolor crap from my ISP that i can't change, i can only buy an additional AP but i have no idea it will help). Ofc, when the connectivity is lost, the phone is still connected to the wifi, hence doesn't switch to network and i stop receiving notifications, which is driving me insane (also a work phone).
I recently installed an app ("wifi connection manager", the app itself is fairly useless, half the stuff doesn't really work that well, and all the options are really things you can do manually) that has a background service that i thought would keep the connection alive. It worked for about a week and then all of a sudden it stopped. I've tries everything else, short of reflashing the phone.
So after ****ing around for the 1000th time, trying to figure it out i realized that turning the WMM off (router QoS) stops the connectivity issues. Problem with this solution is that my download rate over the wifi drops by half immediately (from 50mbit to 25) and after a while all the wifi connections start to deteriorate to the point where it becomes painfully slow. What's more puzzling however is that when i do turn it off, the G4 connects via 802.11g (and for some reason this makes the connection not lose connectivity). Other devices connect via 802.11n whether WMM is off or on (except the desktop, which has an old wifi card, also on 11g).
Sorry for the wall of text. This and the anticipation of a bootloop is making me seriously regret my purchase.
So my two questions are:
1. Is there a way for me to force the G4 to connect via 802.11g even when WMM is On ? It obviously chooses how to connect on it's own.
2. Given the history of events, is there a network guy somewhere here that could identify wth is going on ?
Thanks a lot for those that made it this far