My WiFi has issues opening new connections, like checking my email can take anything from a normal 1 second to just sit there and spin for 30 seconds.
This gets worse if I ask the email client to check all three accounts at the same time.
Opening say facebook through a bookmark on the start screen, can either load instantly, or just show a white screen until I force close Chrome and retry.
I never get an actual timeout error, but it'll keep loading some items between 10 seconds, to just never connecting.
When I do a speed check, there's no issue, I get the same 12 Mbps as the wired computer, assuming it'll actually start downloading.
On the play store there's broken downloads though, it'll download at max speed instantly, but then hang in the middle until I force stop the play store (or reboot).
If I let it sit long enough, it might resume but often with corrupt downloads as a result.
I've had this problem for a while now, and I've tried connecting to various other networks with completely different configurations and it's pretty much consistent.
Disabling WiFi and using the LTE network instead, it doesn't display this behaviour at all, so it has to be something with the WiFi.
Has anyone else had this? I can't find anything useful through the search or google, they all suggest I do this and that on my router, but the other devices work fine.
Tested with the HTC M7, an old Motorola Razr, even the now ancient Moto XT720 has no issues.
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
eyeoncomputers said:
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
Click to expand...
Click to collapse
I checked your thread, and I had a bug like that on 4.4.4 actually.
Where it would work fine, go to sleep then not wake up again.
For me, it was a game from humble bundle that triggered this, "The Deer God"
There was another game on play that did the same, but I can't remember the name of that one.
After I emailed the devs of Deer God, they oddly found the bug immediately and their new version didn't have this problem.
I didn't even send them a log file or anything.. Which was weird.
So far this never happened after upgrading to Lollipop though.
My WiFi problems disappeared at work, but remained at home.
Thinking it was the router, I borrowed a WiFi repeater but the problem still occurred.
Even when I used the repeater as a hotspot with cable.
I was about to give up, and just use my 4G all the time..
But I installed DD-WRT, and lo and behold, WiFi works flawlessly?!
It's not like I'm using a cheap rubbish router, it's the Netgear Nighthawk for crying out loud..
You'd think the software for it would be well coded considering how long they've been doing these devices...
Related
So ever since I've gotten my Nexus One I've been noticing it drops out of a WiFi way too often. It does it both at home and at work on Wireless routers using the latest firmware. I've set the sleep policy to never go to sleep but most of the times I wake my phone up, I'll find it on 3G instead of the full strength WiFi it should be on. On 2.1 when I'd go into WiFi settings it would show the connection and say something along the lines of "Connection unsuccessful, tap to try again" and on 2.2 it just says "Disabled, Secured by blah blah blah". If I retry, it ALWAYS connects and WiFi will stay active for a short period of time before falling back to 3G.
Is there some way I can tell Android to retry the WiFi connection if it fails instead of just giving up? I've been looking through the WiFi API's on the Android Developer site and I'm this close to writing an application that will attempt to mitigate this issue for me.
If I'm within range of one of my pre configured networks, I want the phone to try it's hardest to stay on WiFi. If it loses connection, retry. It it can't get it after 5 retries, wait five minutes and try it again, don't just give up and mark the connection as disabled.
I've read tons of threads about people with WiFi issues and people always say "it's the router, it's the channel, etc, etc" but my WiFi works perfectly fine as long as there is a human to reconnect it if it drops.
Anyone else in the same boat as me?
ok so apparently I'm the only one with an N1 and a WiFi issue.......
I have the same exact issues.
I have the same issue as well and if it stays on I have to turn wifi off and back on so it will connect properly
-------------------------------------
Sent via the XDA Tapatalk App
same issue here. i had been looking for an app that would force the connectivity, but the market doesn't seem to have it. just a bunch of crappy wifi on/off switcher management apps. i'm surprised that no one has hacked this function or built an app for it.
It's certainly a very annoying problem. Mine will go to known good wifi networks, at work, at home and at other locations where my other devices work flawlessly. I have a coworker with the exact same firmware (we updated using the same file) on a nexus one that has never seen this problem, which I find odd, but I'm fairly new to Android. It looks like a software or driver issue to me, but as I said, I'm new to Android.
My device shows the known networks as "Disabled", but I can connect manually.
Looks like it's worth me coding up an App to fix this then.
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
y2whisper said:
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
Click to expand...
Click to collapse
2.6.32.9-27220-g328f560
android-[email protected]#1
I've never tried a new kernel.. Is this something I should look into?
I'm running the same kernel.
BootsSiR said:
Looks like it's worth me coding up an App to fix this then.
Click to expand...
Click to collapse
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
w9ndb said:
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
Click to expand...
Click to collapse
I'd rather take the time to fix it then wait for an update that may never arrive. Always fun digging into the API anyways
That's cool. I still find it a bit troubling, though, that some devices see it and some don't, using the same firmware, on the same wireless networks.
I guess it could be a board rev. difference or an app conflict or something. ::shrugs::
I have a similar problem. I use APNdroid to keep cellular data off and use wifi, but I continually have to reconnect wifi no matter what if I am not actively using it. Defeats the purpose of push email.
I downloaded APNdroid after checking data usage and finding that with wifi on there was still significant 3G leakage. Especially confusing with wifi set to never sleep and plugged in overnight.
On the plus side, APNdroid has netted me a lot more battery life, I can almost get two days and one night. I almost never use my spare battery anymore.
Just as an additional data point, I am having the exact same issue with 2.2 FRF83 (I had been on FRF50).
It looks to me like it is simply scanning all of the time and never associating with a known network. I'm not sure why it flags them as "Disabled", however.
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
safeplayer22 said:
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
Click to expand...
Click to collapse
Yeah, it doesn't help, that was one of the first things I tried. Any time I leave and come back, the networks show as "Disabled". It's a frustrating issue in that it isn't consistant. It's 80% fail, 20% work.
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Zapo said:
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Well, I know fore a fact it's not my access point. I am a network engineer and worked on wireless systems for years and debugging these types of problems is something I'm a bit obsessive about. This stinks of a software or driver problem to me. It could potentially be a hardware revision issue since we have a N1 that works perfectly in all scanerios.
I've tested this with the following access points:
Apple Airport Extreme
Apple Airport Express
Meru
Cisco 1231
Cisco 350
Belkin pre-n
Linksys WRT54G stock
Linksys WRT54G dd-wrt (I forget the build number)
Soekris Engineering running pfSense
All exhibit the same behavior, while my control devices (Apple iPhone 3g, Apple Macbook Pro and a MyTouch 3g running Cyanogen 2.1).
I wasn't aware that this was related to rooting, I'd be more than happy to move back to a stock ROM if that solved my problem. Maybe I'll try that today if I get some time.
Could you possibly post a link to the google forum you're referencing?
I'm currently digging through the alogcat output to see if there is anything interesting in there.
This issue is worse since I upgraded to 83. I'm actually holding off to try CM6 when it comes out to see if there is any better performance there. I'm not sure if he uses updated drivers or kernel that may give better wifi performance.
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
All righty then, I guess its me
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.
UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.
Is anyone else having issues with wifi reliability? My wife and I each got a Fire a week ago, and I have done the update to 5.0.1 and the sideloading of the Google framework and Google Play to both. They both work great, except they are both very flaky on the wifi at home. The connection doesn't drop, but we'll be browsing the web or using an internet-based app, and after a while it will just sit for a long time trying to load a page or download a file. Turning airplane mode on and right back off again "revives" the connection and it works fine for a while longer, then just quits again. It's pretty frustrating and is a barrier to use. Funny thing is, we both have android phones (LG G3 for me, Moto X for her) and both of our phones are fine on the same wifi.
Is this happening to anyone else, or does anyone know what might be going on?
I've noticed the same issue, it's definitely device related. Personally it doesn't happen often to mine and hasn't become too much of a nuisance to me yet. Maybe it'll be fixed (if possible) in a future update.
i experience the same thing but with differences
1) my connection does drop out sometimes, while my
laptop has no issues
2) i don't browse the web with my Fire. But i do download
and find around 30% of files will stall for a min or so before
finishing the download
Been fine for me but when I was playing madden I kept getting disconnected I blamed it on servers as all my other games work fine I'm on 5.0.1
Sent from my HTC One_M8 using Tapatalk
TL;DR
Upgraded Android to latest on T-Mobile, only SSL connections load. Also can't send MMS messages. Factory reset after the upgrade, still having issues. No idea what causes it, but rebooting the phone sometimes makes the issues go away for a while (might as well be running Windows). The issues seem to happen at random but all happen at once and don't go away once they start.
I have an odd issue that after a little bit of Googling, I haven't been able to find anything on (outside of app developers forgetting the internet permission in their manifest file). I held off on upgrading my phone from 5.0.1 AOC9 for a long time because I had rooted it right after the release and I just never got around to it when others confirmed they could root newer versions. Everything was working until I decided to use Smart Switch to upgrade from AOC9 to the latest 5.1.1 DOJC. After the upgrade I used Odin to flash TWRP and Unikernel for root and it worked fine for a few hours until I noticed I could no longer send MMS messages (receiving them works perfectly fine). I also noticed certain apps would tell me I had no network connection and I knew this was wrong because apps like Facebook were still working perfectly fine on 4G and my WiFi. Eventually I started clicking links from Facebook and noticed some would load and others wouldn't. It took a few links to notice that anything that wasn't loading over an SSL connection would give the message "This site can't be reached. $SITE refused to connect. ERR_CONNECTION_REFUSED"
After all of those issues started happening I finally got pissed enough to factory reset, forgot about FRP and had to factory reset again using Smart Switch. I flashed TWRP/Unikernel again and I'm right back to having the issues. Has anyone ever come across anything like this before? I'm getting frustrated enough that I might just swap out the sim and use my G3 for a while until I can sort this out. If there is any kind of log I can post that will help I can post that as well. I tried using adb logcat while attempting to open a site that fails, but I didn't see anything that looked useful. Just calls to my keyboard and chrome opening.
EDIT: Completely forgot to try pinging. I am able to ping any normal HTTP site from a terminal emulator. They're all reachable from my phone. I came across a post from a Comcast customer with a similar issue, although not for Android specifically. The work around was to connect to a VPN service, so I also tried this. Still no luck.
Hey,
So I am having serious wifi issues since I installed my Google Home. I use a chromecast too, but I think it's safe to say that it's the Home device that f-ed up wifi network.
I did read all the articles back i January/February that I was not alone with the issue, and as far as I understand - Google rolled out a fix about a month ago.
However, I am still having issues. My wifi drops for no reason (on all devices at the same time, phones included) for a few seconds and then comes back up. I've tried rebooting the router, and updating firmware on the router but no help. Today I pulled the plug to the Google Home until this has been fully resolved.
I love my Home and would like to have it connected. Did the correction that Google rolled out solve it for everyone else here or does anyone still have issues - or is it just me?
How can I see what firmware/software I am running on the Home? I have obviously tried to ask it, but it responds "this is not supported yet".
Any ideas?
Vol
I had the same problem on my main router, so I tried connecting it to my secondary router, and it worked, but since that one was supposed to be for the other part of the house, I got a cheapest used router I could (doesn't even support n standard) and created a separate network with different SSID, now I use it only to connect google home devices, chromecasts and other smart home wifi devices, and it works (it still uses my main router's DHCP server, and network, it is just AP with a different SSID), oh and I use channel 6 on that router btw.
Volatyle said:
Hey,
So I am having serious wifi issues since I installed my Google Home. I use a chromecast too, but I think it's safe to say that it's the Home device that f-ed up wifi network.
I did read all the articles back i January/February that I was not alone with the issue, and as far as I understand - Google rolled out a fix about a month ago.
However, I am still having issues. My wifi drops for no reason (on all devices at the same time, phones included) for a few seconds and then comes back up. I've tried rebooting the router, and updating firmware on the router but no help. Today I pulled the plug to the Google Home until this has been fully resolved.
I love my Home and would like to have it connected. Did the correction that Google rolled out solve it for everyone else here or does anyone still have issues - or is it just me?
How can I see what firmware/software I am running on the Home? I have obviously tried to ask it, but it responds "this is not supported yet".
Any ideas?
Vol
Click to expand...
Click to collapse
Ok, i feel my networking knowledge can come handy here! Lol. Home,three chromcasts, firetv, firestick x2; Nghthawk x8000->asusrtac68u->lan2wanWNR1000(for old 2nd gen sony bluray dlna and one roomstreaming)+wirelessLinksysEA6350->asusrtac88u. Yes, intriguing network! 6bdrm 3300sqft house. Biggest ever afforded! So, needless to say i pay TWC for 100Mbps, capping at 230mbps on the rtac68u ethernet bridge to wired desktop! All running my own modified compiled tomatousb. Linksysea6350 is ddwrt, kongbuild and a PIA so thats w/e stock kong wanted. Well safe to say ive been at making all this work!! What i need from you is topology and setup, running broadcoms or others? I find broadcom way easier to mess with. Second, you running custom or boxed units? And third is the google products subnetted (more of a b***h if you ask me!) And connected 2.4 or 5? N or AC? And how are you allocating resources? IE using QOS or similar? If you can't answer those im need (if unboxed and freed) "logcats", iptables, etc.. more than safe to say, the home not the culprit in sense to it "drowning" out the wifi band, but could for drown resources, IE low grade hardware, hardware beginning stages of failure and one extra workhorse did it, RAM, eMMC, getting the gist? Im gonna say w/slight certainty you might be rebooting not wifi actually cutting out. You also could if custom firmware corrupted something that the home doesnt like. But wont know w/out the numbers to look at. All i got from you is, either a LAN2LAN or bridge as i read your main hib is the DHCP, and is the SSID you "created" a subnet? And your "30" dollar router also could not be up to task.
And sorry if the reply is anything not right, first post ever here! Years of only reading lol. And something wrong with my cheap phone cracked screen phone replacement everytime keyboard is opened! Doubt its this website. my pixel xl tried to drive on the interstate outside of my car...so sad.. just know im gonna punch this phone or throw from the anger ive gained trying to type and the sign-in to post.. thank you.
Similar solution worked for me
I use a dedicated connection for all things GH related. This stopped the wifi dropout.