I've been lurking for a while and attempting to solve this problem on my own but I've run up against a brick wall and I need some help.
A bit ago, I was running an older stable CM10 build with no real issues. Then, suddenly, one day, the wi-fi stopped connecting. It sees everything broadcast and saves the network, but any time I tried to connect it would, essentially, time out. It would try for a few seconds, then go back to saying "saved". I tried a few different things to test the connection, rebooting the tablet, rebooting the router, removing all security from the router, installing a new router, and trying a public wi-fi. The results were all the same: the tablet can see all the broadcasts but not connect to any.
So, I wiped CM10 totally from the device and installed CM10.1. When I tried setting it up, the exact same thing happened. It can detect all the wi-fi broadcasts but cannot connect to any of them (and as a side note, any time it tried to connect, the wi-fi bars would drop out from full to one bar).
All in all I tried installs of CM9 (that I had used successfully before), CM10, CM10.1, CM10.2 and Evervolv 4.3.1, each from wiped touchpads. EVERY one of them had the exact same problem. The wi-fi when in WebOS works great, so I'm not thinking it's a hardware failure. There's just something odd going on with android installs and my touchpad and I need help.
If anybody has any ideas, I'm all ears. Thanks!
Related
Search function is currently unavailable, so apologies if this is a dupe...
Anyways, I'm currently running Rooted Stock 2.3.4 on my N1, and I've noticed that whenever I connect to my friend's DLink router (DIR-655, I think) the Wireless will work for some amount of time, but eventually it will stop working. And not just on my phone, either - the entire router stops working (at least for Wireless requests. Didn't have any wired devices connected to it). Thing is, last time I noticed it, it worked for quite a while - hour or two, maybe - then everything broke about 10 minutes after I received an email... At that point, the router needs to be rebooted, after which it continues working just fine.
The router is using WPA2 encryption, for what it's worth.
I've noticed this with previous versions of Android, so it's not a breaking change introduced with 2.3.4 or anything.
Unfortunately, I don't have an awful lot of Wireless routers to test with, and I haven't yet found an opportunity to test at home, so I'd be hard-pressed to say whether it's a router/D-Link problem, or if it's a device problem...
Has anyone else experienced this? Would flashing a custom ROM (e.g. CM7) fix this? Or would I need a new device? Any thoughts on what else I could do to debug this problem? As I said, this is a rooted device, with an unlocked bootloader and the latest version of Busybox installed.
I'm running 2.3.4 and haven't had this issue with this version or any previous ones.
I've had my phone disconnect from Google Services (the icons turn white instead of green), but the internet stays on and all other devices work just fine.
I have a Netgear router at home and a Linksys one at work and I'm connected to both the whole time I'm at either place.
Hmm... That's interesting.
I've never had Google Services disconnect, but I do have another issue with data randomly turning off. That's not a big deal, as I can just turn it actually off then back on again, and all is good.
Anyone else able to chime in with their experiences?
I have had this happen with cheap, crappy routers. Sometimes upgrading the router to DD-WRT helps, sometimes it doesn't. I had an ASUS this would happen to all the time, and an Airlink that this would happen to occasionally.
This doesn't ever happen to my Linksys WRT610N, and it never happened to an old ZyXEL X550.
I'm going to say, it's just a crappy router.
Thanks. Not really what I was hoping to hear, but that's life.
Did either bad router ever have this issue with other devices? One of the other folks living there has an iPad, and never has this issue, so I'm inclined to say it's at least partly my N1s fault. Also doesn't happen with any of the PCs connected to it.
Yeah, they actually did occasionally have issues with other devices. Hard to narrow it down because I have a ton of Wifi devices. The ASUS also seemed to go down based on time... after so long, it would just stop working properly. The Airlink seemed to get stuck based on demand and range. If I had my phone or laptop at the far end of the house and started using it a lot, it would get stuck. It was as if the router decided it was too much work to pump its signal that far and it would get tired.
Stock ROM on my N1 doesn't seem to allow it, but if you have a custom ROM, you might see if there is any way to set the Wifi to G-only. I had noticed on my old router that G wireless devices seemed less demanding for it.
What's up guys, first of all I've looked up for that problem on the board and none of the topics are helpful.
Well, I've got SGS with CM9 nigtly 2012-05-06 with the IcyGlitch kernel. I've checked different modems and kernels and nothing. The problem is connected with the wifi. However it is only about my router. Somehow my phone and router don't like each other. The wifi speed is really slow, to download something is a miracle, facebook sometimes even doesn't want to log in. The problem started after I installed cm9. I've tried many builds of CM9 and none of them helped. I don't wanna wipe the phone and install another rom, I just want to fix it, if everybody can work without any problems, I also can. My router is D-Link 524. I've tried other cell phones and they work fine with the wifi. Also I've tried other wifi connection like at my university and it works cool.
What can you advise me to do ?
Hello everyone, since I got my cappy I've been delighted by it, it's an awesome phone, even more so when you get to root and update it, now here's the problem: my wifi keeps acting up. First it was the autenticating loop, now my cappy connects but doesn't send or receive any data. I know it's not my router since I have other wifi enabled devices and they can connect and use the wifi properly. Been trying changing from WPA to WPA 2 and auto, no luck. Been trying setting static IP, no luck. It just... sits there connected and not sending. He worked properly in stock, hence I tried going to stock, and then reflashing, no luck.
I used cyanogen and slim bean, with custom semaphore and cyancore, and different basebands (namely ugkg3, tubjv6, bvjjw2) I hope someone can help me on this since this is the only flaw I've encountered so far with this awesome phone.
Thank everyone in advance, and have a nice day.
EDIT: Forgot to add, when I freshly flash a ROM it works perfectly... Until some time passes (around 4 hrs) or until I attempt to download something higher than 20 mb+. Then the issues start.
mastershen23 said:
Hello everyone, since I got my cappy I've been delighted by it, it's an awesome phone, even more so when you get to root and update it, now here's the problem: my wifi keeps acting up. First it was the autenticating loop, now my cappy connects but doesn't send or receive any data. I know it's not my router since I have other wifi enabled devices and they can connect and use the wifi properly. Been trying changing from WPA to WPA 2 and auto, no luck. Been trying setting static IP, no luck. It just... sits there connected and not sending. He worked properly in stock, hence I tried going to stock, and then reflashing, no luck.
I used cyanogen and slim bean, with custom semaphore and cyancore, and different basebands (namely ugkg3, tubjv6, bvjjw2) I hope someone can help me on this since this is the only flaw I've encountered so far with this awesome phone.
Thank everyone in advance, and have a nice day.
EDIT: Forgot to add, when I freshly flash a ROM it works perfectly... Until some time passes (around 4 hrs) or until I attempt to download something higher than 20 mb+. Then the issues start.
Click to expand...
Click to collapse
Wifi drivers are coming from the kernel, therefor, I'd suggest other kernels. If that doesn't work, try another ROM (like AoCP). If the problem still persists, I'd suggest flashing stock KK4 and starting over.
Hey! Thank you for your suggestions, yeah I've been seeing some improvements using unofficial semaphore so I'm sticking to it right now.
God I love this phone. Haha. Thanks again.
Hey xda users,
I have a Touchpad currently with Android 4.4.4 EOS data media build, previously on 4.2 CM9 (I think).
Now it updated fine and installed Android fine on the first install.
I believe this may be more of a hardware problem than software.
First of all, I believe this problem starting occurring after I had streamed local video on my PC with VLC to the Touchpad using the application MX Player.
Currently, my Touchpad has been having trouble getting a good wifi signal, despite being in the same room as the router.
On the same table with the router, 3 ft. away, it only gets 2-3 bars or a good signal.
10 ft. away, it drops to 1 bar or a poor signal.
On the previous version of Android (4.2 something I think, before data media builds), the wifi signal reception was fine, then I used the Touchpad to watch locally streamed video, and then wifi reception got worse.
Wifi signal reception is about the same in WebOS.
So could this most likely be a hardware problem being that the wireless chip/adapter got damaged due to streaming?
Thanks for any help.
Sometime, it could be overheat issue from overuse. If you try to shut it down for some hours, it could maybe help if this's the issue. If it still got the same problem, try to reinstall your TP with the toolbox the same roms and/or other roms and do a A6 battery reset when the battery's at 100%. If it still happen, you might have no choose to try to get the part to replace it or buy a new TP or something more modern.
Thanks for the reply.
I tried leaving it off in both Android and WebOS, and neither seems to have done anything.
I then tried doing the A6 Firmware flash, which seems to have not done anything either.
I have also tried switching broadcast channels on my router, but no increase in signal there.
Guess the wireless adapter on this thing did get overheated and damaged.
My SM-N900A has been working great for a few years now and is running Android 5.0 from an OTA update (maybe a year ago). A few weeks ago I started having trouble with the wifi. Sliding the wifi control to "on" will sometimes work, but more often it can't find any networks. Often rebooting will fix it, and the wifi will connect (showing a strong wifi signal). Sometimes I see it rescanning several times when I don't think it should be scanning. Then after a few minutes or occasionally up to an hour it will disconnect from the wifi entirely and refuse to show any networks as before. Sometimes I have thought that disconnecting the battery is a surer way to restart the wifi than just rebooting, but it is hard to be sure. This happens with my home wifi, as well as with several other wifi networks I have tried. I haven't dropped or damaged my phone, so I'm wondering if this could be a software problem. I have tried rebooting in safe mode, but the problem persists so I don't think this is caused by an errant application. I have also tried swapping in my spare battery, but that didn't change the problem (although neither battery is a genuine Samsung). If I leave wifi off and just stick to the cellular connection, the phone seems to work as it should. Would there be any logic to trying one of the alternate ROMs on this forum to see if this could fix the wifi problem? One reason I haven't tried this already is that the directions I've seen for installing these ROMs seem to be written for people who have done this dozens of times (which I have not). If this is a reasonable tack, is one of these ROMs known for its ease of installation, or perhaps for the quality and detail of its installation instructions? Are there any less drastic things I should be trying first (other than buying a new phone of course)?
Got the same issue. used odine reinstall 5.0 modem/radio and when that did work, i reinstalled 5.0 and 4.4.4 but nothing worked. i think its a hardware failure. time for a new phone.