Develop Bugs

Loss of Service:Fix(kinda) test

Hey as everyone knows there are some people having LOS and it will remain that way until after a reboot. First I'm rooted but not with a custom kernel. I'm on the stock kernel(just flashed CWM and then root.zip) So I have had LOS a few times since I got my phone. Just a few minutes ago I got LOS after a phone call and it remained that way. AbsolutZeroGI on IRC wanted me to try something whlile I had LOS before I rebooted. I went into the task manager, selected the ram tab and then pressed the clear button. That didnt bring service back but after I did that I did get the roaming notification(but still had LOS) so I plugged my phone into my PC(not to try to fix it but to boot into recovery) and then I noticed my signal came back without a reboot as soon as I plugged in the cable. Now I'm not really sure if/why plugging in the USB would correct this or if it was just a coincidence or if it fixed it. Although I know the other times I had LOS it didnt come back until a reboot no matter how long I waited.. So I would like to run a test..
The next time you get LOS go into the taskmanager, select the ram tab and then click clear, then plug your phone into your PC (Edit: While your screen is off). Did your signal come back or do you still have LOS?
EDIT:
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.

Thank you in advance for everyone who tests this out for us. If we can find a real method that works every time we can start working on a temporary fix until Sammy gives us a firmware update so LOS won't be so bothersome.

i have not experienced the los, but have experienced very poor signal when trying to connect to the net. but when i rebooted the signal did get better

Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.

plmiller0905 said:
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
Click to expand...
Click to collapse
Hmm maybe I'll install the stock kernel and see of that fixes it. I only had my phone since yesterday and it was rooted after an hour or so of having it and since I've had at least 5 Los. :-( but I have read the same that people claim its happening to them as well without ever rooting
Sent from my SPH-D710 using XDA App

I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium

I've had my phone since launch day. I didn't root until the 20th. I had no LOS in that time I was completely stock. Right after I installed bubby's CWM and root the problems started. I mean the same night. It had happened several times until I went back to the stock kernel. I have since had the LOS for literally 5 seconds while it switched from Sprint to roaming and service was right back. Not a problem since. I'm not saying these other kernels are the complete problem and that the phone is not without bugs. I just think that maybe the other kernels make the problem (if any) worse.
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
jirafabo said:
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The other night I had 5 times in two hours. Literally!!

I'm completely stock and picked up my phone on Launch day. I had several LOS during the first few days. I updated my PRL, Profile, Firmware etc. and it hasn't been an issue since.
I do have an issue roaming, as in my phone wont.

Ok guys, I'm going to update the OP but here is a new development.
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.

graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
I saw that theory from someone else around here as well. Definitely seems like something is going to sleep and not coming back on and the modified kernels seem to exacerbate the issue for some reason. (Maybe the source Samsung released is older than what the phone shipped with and the issue was improved between the two versions?)

Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!

graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
That wouldn't work, because in reality, the phone checks cell towers for new calls something like every 5-10 seconds. No sleep for the wicked radio.
No. It is definitely something that disables the radio entirely.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
plmiller0905 said:
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
Click to expand...
Click to collapse
There's no reason not to root the phone now AT ALL.
The current root method of:
1) Install custom recovery+kernel,
2) Flash su binary,
3) Flash stock recovery+kernel
---
The current root method does nothing but add files to /system partition -
you change nothing else in the operation of the phone but add root privileges.
Flashing roms while they are in beta though, that's just asking for trouble, unless you are testing for the rom builder.

I have the LOS icon at this very moment, yet I just received a call? Also, I plugged it into my computer, but nothing changed.

Hi all. I just had LOS and tried to use my car charger instead of my computer. It didn't fix the issue but I did notice that the charging led wouldn't illuminate. after reboot the phone gets signal and the led is working fine. I don't know if that is significant but wanted to mention it.
Sent from my SPH-D710 using XDA App

Interesting thread. Ive had mine for 3 days now and havent experienced this at all.
Sent from my SPH-D710 using Tapatalk

about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?

I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium

leond said:
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
Click to expand...
Click to collapse
No, but that is major suckage, happens to me once a day. Makes me want to punch babies.
los, which I get too, is when you get the no smoking signal instead of a cdma signal.

I went to root+stock kernel and the problem is gone and LOS is gone to

txmikester said:
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There was no update when these phones were released. If she was activating the phone then she was 9/10 referring to a profile update and prl update which each phone does when being activated.
Sent from my SPH-D710 using xda premium

WIFI Problem

I've had my Xperia Play for a little while now and this is my first problem I've had with it. I held down the power button to turn it off and waited for a while. I then took out the battery and looked at the IMEI code and the Serial Number and then placed back in the battery back in the phone. It then rebooted and said I was connected to my WIFI connection but the time and date were wrong. It also came up showing 2 missed calls from earlier in the day.
I went into the settings and turnt on and off WIFI but still no luck. I've also tried rebooting my phone multiple times and have had the same outcome. I can use the browser on my phone but can't connect to things such as the android market or youtube. So the phone comes up with a WIFI symbol at the top of the screen but I can't go on anything apart from youtube and the market. Any suggestions?
Please Help me as this is really annoying.

Exactly the same problem I had before, I can't remember what I did to fix it, if you come up with a solution post it please, weird thing is this issue started as I was going to read this thread.

I wasn't paying much attention when I fixed this but I think I might have fixed it by turning off the option in time and date settings that uses internet values. Then the time swt itself and then I just turnt it back on. Its working fine now. Very strange.
Sent from my R800i using XDA Premium App

[Q] Bluetooth Won't Turn On

When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?

TomSilverSpring said:
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
Click to expand...
Click to collapse
Are you using an experimental ROM or stock rooted?

Jedi Mind Trick XI (although the problem has been growing worse and has happened across the last several JMT versions). I will give a stock rooted ICS a try.

I just tried a stock rom and the problem persisted.

I have the same problem
I have scoured the net looking for an answer, any answer, to this problem. It seems that a few people are having the same issue. But before it is ever answered, some dip$#!t always jumps in and says "I have the same problem, my phone won't connect to my car." Then the conversation goes off into other people that can't connect their bluetooth to their car or their headset- or their cat... That is not the same problem!!!
I cannot turn my bluetooth on unless I soft reset the phone. Even after I've gotten the bluetooth working, if I restart my phone the bluetooth turns off and when you try to turn it on, it says "Turning on Bluetooth..." It cycles for about a minute and a half and then goes back to "To see devices, turn on Bluetooth."
I bought this phone on Amazon for what appeared (at the time) to be a reasonable price. Since then, I believe that I have read at least one of the seller's post about bluetooth not coming on (no proof, just an educated guess). The seller probably got rid of the phone because noone could or would give an answer to this problem. Heck, it's possible that every post that I've read so far is by someone who owned this phone at one point or another. :silly:
I am sending this post to XDA because even the adminstrators on android forums say that you guys are the smartest and most responsive forum available. (Okay, they didn't say smartest- it was implied). Please help me resolve this issue.
I rooted this phone the moment that I pulled it out of the box. In other words, I don't know if the bluetooth issue is caused by the root, or if the previous owner didn't root the phone and also couldn't get the bluetooth to work. I believe that, because the phone is rooted, I should be able to remove and reinstall the app that bluetooth is based upon.
I am not a techie, the only reason I know anything about root is because I was complaining to someone about my old phone and how all of the bloatware that seems to constantly run eventually kills my battery. He told me about rooting, and it was easy enough - the rest is history. In other words, if you ask me for more information- I promise that I can give it to you. Yet, have patience with me if I ask you a question that you believe that any person that has rooted their phone should know.
I really hope that you guys can help me without bricking my phone. I truly appreciate any suggestions or thoughts on this matter.

jzxpw6;34880517I cannot turn my bluetooth on unless I soft reset the phone. [/QUOTE said:
I may have figured out what is going on, although I can't understand why it is (maybe someone more versed with processes can help me figure this out).
Using Titanium Backup, I first froze the two bluetooth items (Bluetooth Share and Bluetooth Test). Of course, that didn't remove anything, but I wanted to make sure that I could. Then I wanted to see how Bluetooth Share would react without Bluetooth Test. I unfroze Bluetooth Share.
I was then able to turn on and off Bluetooth fine. I restarted the phone and Bluetooth came in just like it did on my old phone. I guess I want to know:
1) Is the Bluetooth Test the cause of my problem?
2) Why is it there?
3) If I uninstalled it, would I experience a major hiccup?
There is still the possibility that this was simply a fluke, and very soon I will go back to the old bluetooth soft reset problem.
There is, however, one distinct difference between this phone and the last and may be the "drop out" that everyone else seems to be having. I have a Chevy Malibu with bluetooth in the stereo. On my old phone, when I started the car and got going, the word "Bluetooth" would appear on the digital display for about 10 seconds, which means that the vehicle detected and connected the bluetooth pairing. Yesterday, as I was driving in the car, every 5 minutes or so, "Bluetooth" would appear on the digital display.
This leads me to the conclusion that Bluetooth is dropping out and being picked up continuously by my vehicle. Does anyone have any thoughts on this? I'm okay with that as long as when I am talking to someone for more than 5 minutes I don't have to keep calling them back. I simply want to know what you guys think about this issue.
Click to expand...
Click to collapse

I am beginning to think that the problems I have had are related to the condition of the battery contacts.I have several third party batteries with contacts that are somewhat damaged from the pins on an external charger that came with them. I seem to experience a variety of problems when I try to use them.my original factory battery seems to work most of the time. I have several new Samsung batteries on order and will post again if they seem to solve the problem.
Sent from my SGH-T989 using Tapatalk 2

i had the same problem and it started with JMT so I switched roms countless times and the problem kept coming back. It would work for a little bit but when i turned it off it would not turn back on. I decided to go back to stock to see if the problem was still there and it was gone. Since then I have rerooted and once again flashing diff. rom every other day and bluetooth works just fine.

Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.

enveous said:
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
Click to expand...
Click to collapse
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.

aaronchili said:
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
Click to expand...
Click to collapse
Hey thanks! I switched to JMT JB4 and it's not happening (much) now, I'll try to flash it and see if it fixes something :good:

[Q] Does not auto reconnect anymore

So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.

Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk

droidkevlar said:
So over the past few days, have noticed that if I walk away from my phone (LG G3 Verizon rooted) my watch does not auto reconnect. Any ideas? It does reconnect after 2-3 mins, or if I disconnect/reconnect from Wear app. Never did this before. Always reconnected almost instantly when I got back within range of the phone.
Click to expand...
Click to collapse
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.

I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?

kpjimmy said:
Have you unpaired the watch and phone. Reboot and pair up? If you have what about unpaired then uninstall android wear, then reboot and start again?
Last resort would be a reset of the watch.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
JayRyu said:
Try restarting the watch and turning off and on the bluetooth your phone. I noticed that it takes about a min to reconnect sometimes and restarting the watch and turning off/on the bluetooth on the phone helps.
Click to expand...
Click to collapse
I have tried all of this, minus doing a reset on the watch. If I cant figure out, this is what Ill be trying next.
euroclie said:
I noticed the same thing, and it's indeed not very convenient...
I wonder if this may have something to do with the latest update that achieve a better battery management.
Maybe they increased the time between bluetooth connection attempts in case of connection loss, to avoid wasting precious battery life?
Click to expand...
Click to collapse
Thought this too, but it just happened out of the blue. It wasnt right after the update.
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.

So just tested and it still takes a long time to reconnect. Next step will be wiping watch completely and seeing if it resolves the issue. Will try this over the next few days when I get some free time to really mess with it.

My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.

fwayfarer said:
My device also does not seem to auto reconnect. A manual cycle of the connection status from the android wear app on the phone immediately reconnects it for me. I don't have the patience to wait and see if it has a timeout on reconnect but I can test if need be.
Click to expand...
Click to collapse
Good to hear I am not the only one. Which phone do you have? Mine does reconnect, but takes 1-3mins. Im not using a stop watch, just looking at clock and watching the time before it reconnects.

Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.

fwayfarer said:
Nexus 5 32gb. Ill do an intentional test and see if it reconnects eventually with a time out. I imagine as others have said it was set to a timeout to save battery.
Click to expand...
Click to collapse
OK, Im on LG G3 Verizon rooted. Its just weird that either I didnt notice it after the update, or it happened shortly after the update. Either way, batt life has been a lot better, I just wanted to make sure something I did didnt screw it up.
And let us know about your test for the disconnect.

droidkevlar said:
I just rem'd last night that there was an update to an xposed module I use, called Unbounce, Im wondering if this is the culprit. You wouldnt happen to have it installed too, would you? I am going to test disabling it and see if it resolves my issues. Will report back.
Click to expand...
Click to collapse
FWIW I don't have Xposed installed (but a custom ROM on a i9502 Dual-SIM Samsung Galaxy S4, which might contain some Xposed stuff even though it's unlikeley).
I didn't notice the same reconnect delay today, so maybe this isn't a permanent phenomenon...

I have same issue with reconnecting after walking away. I have a Galaxy S5.

Walked upstairs and watch disconnected, got alert. Came back down and put phone in my pocket. Took three minutes to reconnect.

Bluetooth reconnect takes ages
Same issue with my 360. I have a xperia z2 and its taking a good 2-3 mins to recconect. Such a pain as this is really important to me and work.
Any ideas on if its a downloaded app or not?

Everyone's timeout is looking about equal. It was probably put in for battery savings.

Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed

fwayfarer said:
Everyone's timeout is looking about equal. It was probably put in for battery savings.
Click to expand...
Click to collapse
robber said:
Isn't this what we want? An immediate reconnect (admittedly what my gear live and neo do) would mean constant ping attempts while disconnected. This means battery. My 360 re-connects within 2-3 minutes which is fine by me.
LG g3, sprint, rooted, xposed
Click to expand...
Click to collapse
Yep. Just wanted to make sure as it seemed to happen not right after the update. Thanks everyone.

Wifi slowdown

Last couple weeks I've had an issue will my Internet connection gets painfully slow over wifi. Today it would give me decent results on a speed test, but would take forever to start running test. Chrome, Facebook, etc, would be really slow to load anything. Similar thing happened last week, except that time speed test came back really slow.
Both times a restart fixed the problem.
Any idea what could be causing this? Before these two times, I never had any issues and never rebooted the phone except if the battery died. I was up to 15 days without any issues and no restarts. Now I've restarted twice in the last 8 days to fix a problem.

I'm following the post closely.
I have similar issues and at first I thought it could be my wifi modem. Restarted that and it seemed to work for a couple days then the same issue. Major slow down. I tested other devices that I have connected to my wifi, none of which have duplicated the major slow down of the wifi. I have done the update and I'll post in a week or so if this has fixed the issue.

I know it wasnt a router issue because my friend has a note 4 and didn't have any issues while I did.
I did a factory reset this morning, will see if it happens again.

I'm also curious about this. Is your wifi AC enabled?

Same here, slow slow slow. My nexus 7 works fine so it isn't wifi.
---------- Post added at 05:40 AM ---------- Previous post was at 05:40 AM ----------
I know it wasnt a router issue because my friend has a note 4 and didn't have any issues while I did.
I did a factory reset this morning, will see if it happens again.
Did that help?

I'm going to take mine to the At&t store this morning. Facebook just sits there and does nothing, Instagram is the same can't receive email either and that's after doing a factory reset.

I took it in and they are now sending me to the device support center. The rep couldn't get it to hook up with there wifi.

Thanks for the update. Mine isn't quite that bad. It'll just slow down to about 5mb/s while the other devices on the network are fine

harlenm said:
Last couple weeks I've had an issue will my Internet connection gets painfully slow over wifi. Today it would give me decent results on a speed test, but would take forever to start running test. Chrome, Facebook, etc, would be really slow to load anything. Similar thing happened last week, except that time speed test came back really slow.
Both times a restart fixed the problem.
Any idea what could be causing this? Before these two times, I never had any issues and never rebooted the phone except if the battery died. I was up to 15 days without any issues and no restarts. Now I've restarted twice in the last 8 days to fix a problem.
Click to expand...
Click to collapse
Have you tried to turn off WiFi power savings off. You do that from the dialer, *#0011#, go to wifi settings and turn it off. It's known to samsung phones to cause issues with power savings on.

jerrychasta said:
Have you tried to turn off WiFi power savings off. You do that from the dialer, *#0011#, go to wifi settings and turn it off. It's known to samsung phones to cause issues with power savings on.
Click to expand...
Click to collapse
Turned it off. Will see if that does anything.
Hasn't happened in the last week.

harlenm said:
Turned it off. Will see if that does anything.
Hasn't happened in the last week.
Click to expand...
Click to collapse
Do a speed test it'll surprise you.

jerrychasta said:
Do a speed test it'll surprise you.
Click to expand...
Click to collapse
Not seeing much of a difference in a speed test. I'm at the outer edge of my wife network, and I'm seeing 10 down /5 up. If I go right underneath my access point, I'll get 50/20.

I take it back, I got 10/5 under the router, while a wired connection got 40/10.
Gonna restart the access point and see what I get.

An iPhone 6 just did 15/1.5
Another test for me and I got 8/6

Restarted the phone and got 20/4.
What is causing this?

Same issue for me as well. It's only the wifi on my phone and it just started last week. I even did a hard reset to fix it and no luck. It's laggy as hell now and I just leave it on LTE so I don't have to wait so long. Any updates?

My issue is worse than it ever was. Instead of happening every 6-7 days without a restart, it happens after 1 day now. It's not so much that WiFi is slow, it's that it takes forever to start downloading and for Web pages to load up. 30-40 seconds before a page will begin to load.
I have a replacement phone coming from att today.