WiFi Keeps Shutting Off

[donelam304]

I'm currently running 4.4.2 and biggins ROM. been running flawlessly since I put it on it when it came out. Now, for about the last month or 2 my WiFi Keeps Shutting off on its own, forgets WiFi passwords, won't connect hardly when it does come in. It's also been randomly rebooting on its own, sometimes 3 or 4 times in a row. Anyone have any suggestions on how to fix it. I've had the phone since the note 3 came out.

Sent from my SM-N900V using Tapatalk

 

[bftb0]

Frankly that sounds more like hardware troubles than software.

(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:

(A) Throw the phone away and get a new one.

(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)

 

[donelam304]

Frankly that sounds more like hardware troubles than software.

(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:

(A) Throw the phone away and get a new one.

(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)

I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.

Sent from my SM-N900V using Tapatalk

 

[bftb0]

I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.

Sent from my SM-N900V using Tapatalk

Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.

So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?

If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.

Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.

But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.

If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.

Are you on NC4?

Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)

 

[donelam304]

Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.

So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?

If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.

Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.

But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.

If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.

Are you on NC4?

Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)

Here is my current build. I am on NC4.



Sent from my SM-N900V using Tapatalk

 

[bftb0]

Well,

What do you plan on doing? It's not like there's a toggle button in Settings labeled "Act strange and reboot randomly mode" that we can just go in and turn off.

Do you have any Safestrap backups?

How about the NC4 factory Odin firmware file, do you have that? A copy of Odin somewhere & a PC it will run on?

That's how these things go - you need to create a fault hypothesis, and then try something that will hopefully do something to remedy that type of fault... which might or might not work.

The "bit rot" hypothesis assumes that flashing the same software you already have on the phone will correct eMMC memory pages that have gone bad, both by refreshing the data and also through page replacements by the Flash memory controller doing wear leveling. But that's only one hypothesis out of many that are possible. There's no guarantees that this will fix the problems you are having if the origin of the problem has nothing to do with this mechanism.

If it were me I'd probably make TiBu backups of my most frequently used apps, back up the internal SDcard, and start from scratch by Odin flashing NC4 stock*. Its more effort, but pretty much everything gets re-written that way, and if you continue to have issues then you know it is time to move on to a new phone, rather than continuing to diddle with it.

good luck

* I believe that the TowelRoot app works on NC4, does it not?

 

[donelam304]

Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.

Sent from my SM-N900V using Tapatalk

 

[bftb0]

Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.

Sent from my SM-N900V using Tapatalk

If you do a "tar tvf filename" on those .win00x files the dates of the files listed will give you a better idea. (I suppose that some widows archive programs also understand .tar file formats, but I can't give you a reccomendation)

Also I sort of recall that the Safestrap version of (twrp) recovery adds the name of the slot from which the backup was made.

You actually have lots of choices. You could unlock the bootloader, install a custom recovery, and try a different ROM. Or when faced with Odin flashing, bite the bullet and upgrade to OF1. (As near as I can tell, using towelroot on NC4 is far less of a hassle then that Yemen tool appears to be with OB6/OF1 ... that sort of argues for flashing NC4 instead of more recent firmware.)


Well anyway. If it's failing hardware none of this will make a whit of difference and your phone will still lockup/reboot/drop WiFi.

good luck