[Q] Weird WiFi Issue (Wont Turn On) - T-Mobile Samsung Galaxy S 4

Hello all,
Its been a while since I had an issue with my phone but this one is really bothering me. Last week for no reason at all I noticed my WiFi was turned off while at work. When I tried to use the drop down widget to turn it back on it would just stay gray for like 5-10 seconds then go back to the off position. So I went into settings and tried to turn it on the long way and got the same result. This was troubling to me because I had made no changes to my phone that could have effected this. So after doing some digging around online and not finding any answers I contacted Samsung tech support who was terribly uninformed about their product and offered very little help with my problem. They suggested I go into the application manager and reset the application preferences. I was skeptical because I had spent a considerable amount of time disabling all the bloatware that was not needed in the past but I did take the advice of tech support and to my surprise it did get wifi working again.. temporarily that is.
Today I did the OTA 4.4.2 Kit Kat upgrade in hopes that it would fix my issue and to my shock and surprise it did. Wifi worked flawlessly for a few hours but then all the sudden earlier today it just shut off again without notice. Now once again, it will not turn back on no matter what I try. Im thinking this could potentially be a hardware issue. If it is then why after the upgrade to 4.4.2 did it work so well for a few hours?
Any help would be much appreciated as I have chewed through nearly all of my monthly data allocation while trying to find a working fix.
Thanks in advance!

KingKash420 said:
Hello all,
Its been a while since I had an issue with my phone but this one is really bothering me. Last week for no reason at all I noticed my WiFi was turned off while at work. When I tried to use the drop down widget to turn it back on it would just stay gray for like 5-10 seconds then go back to the off position. So I went into settings and tried to turn it on the long way and got the same result. This was troubling to me because I had made no changes to my phone that could have effected this. So after doing some digging around online and not finding any answers I contacted Samsung tech support who was terribly uninformed about their product and offered very little help with my problem. They suggested I go into the application manager and reset the application preferences. I was skeptical because I had spent a considerable amount of time disabling all the bloatware that was not needed in the past but I did take the advice of tech support and to my surprise it did get wifi working again.. temporarily that is.
Today I did the OTA 4.4.2 Kit Kat upgrade in hopes that it would fix my issue and to my shock and surprise it did. Wifi worked flawlessly for a few hours but then all the sudden earlier today it just shut off again without notice. Now once again, it will not turn back on no matter what I try. Im thinking this could potentially be a hardware issue. If it is then why after the upgrade to 4.4.2 did it work so well for a few hours?
Any help would be much appreciated as I have chewed through nearly all of my monthly data allocation while trying to find a working fix.
Thanks in advance!
Click to expand...
Click to collapse
I'm having the same problem. I upgraded to the KK 4.4.2 and now my WiFi won't turn on! I'm getting the Security notice that "Your phone's security has blocked an action that is not permitted. No further action is required." So, I went to the phone security tab to see what my settings were and it is set to Normal and the only other choice is High. So, I don't want to change that setting!

Both of you guys try flashing Ktoonz newest KK kernel for tw.. If that won't work there's also something to try to fix it in the OP, or you could also try that first
Sent from my SGH-M919 using Tapatalk

serio22 said:
Both of you guys try flashing Ktoonz newest KK kernel for tw.. If that won't work there's also something to try to fix it in the OP, or you could also try that first
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Correct me if im wrong but your suggested fix would require root right?
I am running a stock unrooted rom
please help!

KingKash420 said:
Correct me if im wrong but your suggested fix would require root right?
I am running a stock unrooted rom
please help!
Click to expand...
Click to collapse
Right.. But other than that, the only other thing I can think of is to Odin the 4.4.2 firmware and see if that would fix it, if not then its likely a hardware problem
Sent from my SGH-M919 using Tapatalk

Related

[Q] SGS3 screen flashes off and on randomly while in use

This never used to happen but in the last week has.
While using it, whether I'm in GoSMS Pro, or Chrome or even in the homescreen the screen will fade to black then back one to three times. It almost feels like proximity detection but there's absolutely no obstruction nor am I in a call.
Running 4.0.4 stock unrooted, latest update from Rogers.
Has anyone had this? Getting a bit worried!
Screen blacking out randomly
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
dropzone01 said:
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
Click to expand...
Click to collapse
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Victorminator said:
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Click to expand...
Click to collapse
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Temporary solution found
Victorminator said:
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Click to expand...
Click to collapse
I think I've solved it, but this may not be a solution for most people experiencing this (my friend also had this issue). In my case removing the game Modern War solved it.
I remember that after I installed it, the system started doing these flashes. It now has been behaving ok for 4 days since uninstalling it.
I don't think the game itself is the cause, but rather there could be some background task from it (it does occasionally push game event updates as notifications) that doesn't like the 4.0.4 update. In this case I can't quite identify what nor do I know how to diagnose it.
Just thought I'd update people in case they still have this issue. It may be one of your apps, essentially. It sucks and it shouldn't happen, but alas unless we test with a new stock OS update, we won't have much to eliminate it without removing the offending app.

Random Reboots since JVB by OTA

This has happened to me twice while in my pocket since receiving the OTA a week ago. This never happened with ZV9 since getting the phone months ago.
Has anybody else seen this? Any ideas what this might be? Any apps to help figure out what's causing this? Is this related to the location service reboots that other phones on Jelly Bean like the Nexus were having?
I am not a big fan of Android version changes via "patching" for this very reason. I suggest doing a factory reset and see if it continues to happen.
Lokifish Marz said:
I am not a big fan of Android version changes via "patching" for this very reason. I suggest doing a factory reset and see if it continues to happen.
Click to expand...
Click to collapse
Good call, thanks for the input. I was considering doing that if it keeps up.
I'll probably root and unlock soon anyway once I have some time.
spackmanbr said:
Good call, thanks for the input. I was considering doing that if it keeps up.
I'll probably root and unlock soon anyway once I have some time.
Click to expand...
Click to collapse
I had this problem and it only happened after I had updated the Android Booster FREE app. I uninstalled Android Booster FREE (as it really wasn't useful, in my opinion anyway) and the problem disappeared. If you have this app installed maybe you can uninstall it and see if that solves your problem.
Thanks for the input, but I never use any apps of that nature, and no power saver apps either.

[Q] N7 shutting itself off at night

So my first N7 had dead pixels and when I returned it I had to open 3 others in store to find one that was perfect. Or seemingly perfect. Twice now I've woken up to find my N7 off. The first time it happened I thought maybe I turned it off but last night I know I left it on. I did some searching and found that I am not the only one with this issue, but I haven't found any recent threads about it or any known fixes. Now I'm still on 4.3 and really don't want to update to 4.4 but if this bug was addressed I'll update it. Anyone here have this issue, found a fix, or updated and had the issue disappear? I really don't want to exchange it yet again but I will if it's the only way to get one that doesn't do it. Any insight would be appreciated.
Sent from my Moto X
_MetalHead_ said:
So my first N7 had dead pixels and when I returned it I had to open 3 others in store to find one that was perfect. Or seemingly perfect. Twice now I've woken up to find my N7 off. The first time it happened I thought maybe I turned it off but last night I know I left it on. I did some searching and found that I am not the only one with this issue, but I haven't found any recent threads about it or any known fixes. Now I'm still on 4.3 and really don't want to update to 4.4 but if this bug was addressed I'll update it. Anyone here have this issue, found a fix, or updated and had the issue disappear? I really don't want to exchange it yet again but I will if it's the only way to get one that doesn't do it. Any insight would be appreciated.
Sent from my Moto X
Click to expand...
Click to collapse
Why don't you want to update to 4.4.2? It might solve the problem.
Anyway, the only device I had that had random reboots was my Nokia Lumia 520 which I straight away replaced.
I would advise you to do it aswell incase 4.4.2 doesn't fixe it.
username4this said:
Why don't you want to update to 4.4.2? It might solve the problem.
Anyway, the only device I had that had random reboots was my Nokia Lumia 520 which I straight away replaced.
I would advise you to do it aswell incase 4.4.2 doesn't fixe it.
Click to expand...
Click to collapse
I don't like the way 4.4 looks. I am a big fan of the blue/holo theme of 4.3. I have 4.4 on my N5 and that's enough for me. 4.4 really doesn't bring much to the table (for me anyway) that would compel me to update.
My N7 isn't rebooting, it's turning off. Never had a device that did that before. I'll probably update just to see if it stops it, and plus I have some bad stuttering when watching embedded videos in chrome and from what I've read, 4.4 solves that too. I really don't want to have to exchange it again, and I'm sure the manager at Best Buy doesn't want me to either lol.
Sent from my Moto X
_MetalHead_ said:
I don't like the way 4.4 looks. I am a big fan of the blue/holo theme of 4.3. I have 4.4 on my N5 and that's enough for me. 4.4 really doesn't bring much to the table (for me anyway) that would compel me to update.
My N7 isn't rebooting, it's turning off. Never had a device that did that before. I'll probably update just to see if it stops it, and plus I have some bad stuttering when watching embedded videos in chrome and from what I've read, 4.4 solves that too. I really don't want to have to exchange it again, and I'm sure the manager at Best Buy doesn't want me to either lol.
Sent from my Moto X
Click to expand...
Click to collapse
Obvious question here but have you tried a factory reset?
username4this said:
Obvious question here but have you tried a factory reset?
Click to expand...
Click to collapse
I'm going to tomorrow if it does it again tonight. But the tablet is only a few days old and I already did a factory reset before I set it up initially.
Ok it just did it again right in front of my face. It didn't just go black in the middle of use, I picked it up to use it and before I could do anything it powered down, but did so as if I had deliberately done it. Meaning, the Power Off pop up was on the screen and it said "shutting off" the same way it does when you turn it off manually. That would lead me to believe it would be a software bug as opposed to a hardware one... am I correct in that assumption? Or can some hardware defect actually trigger the normal power down sequence?

Persistent Auto-Rotation Problems

Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
abubakr125 said:
Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No ideas other than to suggest that you do an RMA with ASUS. I just looked and I pre-ordered mine through Best Buy and it shipped July 26 of last year so you might still have time left on the one year warranty.
Hey, I hope this topic is still alive. Mine has exactly same issue as yours. It all started after I re- clean flashed Mahdi ROM (I messed up some stuff so I had to do it). Ive tried clean flash again, but it doesn't work. I've also tried different settings and apps but nothing helped. The only thing I found working is turning on lockscreen blur. For some reason, it makes the rotation work for a bit longer.

Tab S 10.1 Touch Screen Stops Working

Ok so I am having a strange touch screen issues with both mine and my wife's tab S 10.1. It started on mine several weeks ago. When using the device, the touch screen will all of a sudden stop responding. If I press the home button, the device goes to the home screen, it just does not respond to any touch. If I press the power button to put the device to sleep and push it again to turn it back on the screen is working again but it will freeze up again, sometimes in less than a minute. When it first happened I tried to do a factory reset to see if that would help and the problem actually occurred during the initial device setup then so I know it's not related to an App that I have installed. I have sent mine to Samsung now three times trying to get them to fix it. They have replaced the screen once and said that there is nothing wrong the second time (still waiting on the determination of the third time). I have tried to research the issue but have not seen anyone experiencing the same thing. I do not have the rebooting issues that others have mentioned and turning the screen off and then back on does make it work, at least temporarily. I only remember noticing it since upgrading to Android 5 so I am going to try getting the device downgraded to Android 4.4.4 to see if that helps. Wanted to see if anyone had any other ideas. Samsung has basically told me if their techs say there isn't a problem they won't do anything for me.
A few people have mentioned touchscreen problems after upgrading to v5.0.2 mostly 8.4" but some 10.5" have you had any horizontal/vertical lines on the screen.
John.
Tinderbox (UK) said:
A few people have mentioned touchscreen problems after upgrading to v5.0.2 mostly 8.4" but some 10.5" have you had any horizontal/vertical lines on the screen.
John.
Click to expand...
Click to collapse
I have never noticed any lines. I have noticed after the first time at the repair center that the touch screen also seemed to be acting erratically, jumping around when trying to scroll or pan instead of having smooth motion. If I am able to get the device downgraded to KitKat and that improves things, I will just stay there until they figure out what is wrong with Lollipop.
I have stayed on kitkat because of the problems with lollipop, it`s just not worth it to me, but the majority of people don't seem to have any problems with it, I cannot see how upgrading to lollipop affects some touchscreens and not them all, but some people have reported the problem after upgrading i just don't know what to say.
It is normal for the touchscreen to behave erratic if you use it while your tablets is being charged, it is mentioned in the user manual.
I would say you have a faulty touchscreen, do you use a screen protector, have you tried the setting that increases the sensitivity of the touchscreen.
John.
I did not know about the charging item so that might explain the erratic behavior. I thought it might explain the screen locking up too but I know that has happened at times when I am not charging the device. I will be interested to see what happens this time when it comes back the third time from Samsung and whether downgrading my wife's device helps the issue on hers or whether we will need to fight with Samsung about hers as well.
For a couple months, I've had exactly the same problem on my Galaxy Tab S 10.5 (SM-T807V). It comes and goes in severity; some days, I lose all touch input every 5 minutes, it seems, while other days, I can go hours without trouble. Using the device without a case seems to help, as does restarting it, at least temporarily.
I have not sent my device to Samsung, nor have I performed a factory reset. But based on your experience, I'm not sure if either option is worth it.
Hi.
I would suggest removing any screen protector and cleaning the screen looking for any damage, download a touchscreen tester app from google play and testing your screen.
After searching around i found an touchscreen recalibration app for android, but i am very wary of it being fake or causing more damage or that it is for a specific brand of phone/tablet.
EDIT: I used an hex editor, and found this text within the apk file, see photo below.
John.
Well Samsung is finally sending the device back to me. This time they said the found the problem and replaced the main board and updated the software. So we will see what happens when it gets back to me tomorrow.
For anyone who is having this problem like I did. My wife has not had problems since she stopped using the device while it was charging. I have not had problems with mine since it got back related to this but whether that was Samsung fixing the issue or the fact that I also am not using it on my charger, I do not know. So if anyone else if having the problem, try the charger thing; otherwise, you may be looking at some kind of hardware issue that Samsung will have to resolve for you.
Most devices behave erratically while being charged. My HTC does it so does my tab.
Samsung even mention it.
Hi, i am having EXACTLY the same issue. The tab toucj freezes and normalizes if i lock it and unlock it with home button. I think its a software issue.
Sent from my GT-N7000 using Tapatalk
I have two of these from Verizon (T807V) and after updating them to 5.0.2 they both have this same behavior.
Quite annoying.
Any luck finding a cure ? I have noticed that the ram usage gets crazy. Any given time 1.8 gb is utilized out of he 2.77 gb available. I have uninstalled quite a few apps and shut down background processes but still the system is eating too much ram. Can any one help me on how to monitor aap ram usage ?
Sent from my SM-T807V using Tapatalk
Hi.
I was reading the HTC forum as i have qone of their phones, and i read that some people were using an Samsung touchscreen app to boost the touchscreen as they were having problems, the app is called "SGS Touchscreen Booster" link below, The Tab S1 has it`s own touch screen booster in the settings, maybe try that first.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en_GB
http://forum.xda-developers.com/showthread.php?t=1581098
John
siddiqui.nauman said:
Any luck finding a cure ? I have noticed that the ram usage gets crazy. Any given time 1.8 gb is utilized out of he 2.77 gb available. I have uninstalled quite a few apps and shut down background processes but still the system is eating too much ram. Can any one help me on how to monitor aap ram usage ?
Sent from my SM-T807V using Tapatalk
Click to expand...
Click to collapse
That's how android works. Its pointless trying to reduce ram usage if there is still ram to spare.
Android utilises ram not wastes it.
siddiqui.nauman said:
Any luck finding a cure ? I have noticed that the ram usage gets crazy. Any given time 1.8 gb is utilized out of he 2.77 gb available. I have uninstalled quite a few apps and shut down background processes but still the system is eating too much ram. Can any one help me on how to monitor aap ram usage ?
Sent from my SM-T807V using Tapatalk
Click to expand...
Click to collapse
I had multiple problems with 5.0.2, ram hogging, touchscreen problems, my solution was to root and install a custom rom 4.4.4 the tablet is so much more responsive after reverting back to kitkat. I know it's not a solution for everyone but it fixed mine (SM-T800). Just throwing it out as an option.
Used kies today to upgrade to the latest firmware but still the problem continues. I have the Samsung sm t807v Verizon locked. Is there a way I can downgrade it to kit kat? Xda experts are saying it's bootloader is locked
Sent from my SM-T807V using Tapatalk
Steve1698 said:
I had multiple problems with 5.0.2, ram hogging, touchscreen problems, my solution was to root and install a custom rom 4.4.4 the tablet is so much more responsive after reverting back to kitkat. I know it's not a solution for everyone but it fixed mine (SM-T800). Just throwing it out as an option.
Click to expand...
Click to collapse
This is a strange one I used to have the opposite. 4.4.4 every now and then touch screen stopped responding. Pressing power resolved it.
When I upgraded to LL the problem went away.
However I mostly use custom builds. At the moment the best for me is PhoeniX ROM.
Absolutely bug free so far.
Can't say I had any issues with Ironrom either.
ashyx said:
This is a strange one I used to have the opposite. 4.4.4 every now and then touch screen stopped responding. Pressing power resolved it.
When I upgraded to LL the problem went away.
However I mostly use custom builds. At the moment the best for me is PhoeniX ROM.
Absolutely bug free so far.
Click to expand...
Click to collapse
I'm running BlissStalk (discontinued) but I haven't had any issues with it. I was running the CM11 unofficial also without issues. But the stock 5.0.2 it had on it when I purchased it (used) had issues. All my devices eventually end up with a custom rom eventually!
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
siddiqui.nauman said:
Used kies today to upgrade to the latest firmware but still the problem continues. I have the Samsung sm t807v Verizon locked. Is there a way I can downgrade it to kit kat? Xda experts are saying it's bootloader is locked
Sent from my SM-T807V using Tapatalk
Click to expand...
Click to collapse
I flashed stock kitkat firmware via Odin... But it is a different tablet than yours (SM-T800). I found the following thread when I was trying to do it. Just make sure you flash the firmware for your specific model.
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t800-best-to-downgrade-5-0-2-to-t3069929
Bootloader unlocking
So basically searching around the internet to find a kitkat firmware for this. I think it can be downgraded but I need the stock firmware for the sm-t807v.
XDA forums have support for the other variants but for the one I have which is Verizons sm-t807v there are no STOCK firmwares anywhere.
Ashyx and steve if you know any resource, please help me out. I need to get this fixed. I don't have access to any verizon stores where I could go and get this fixed or sorted. It just me and the internet.

Categories

Resources