Cooper Drinkward
- Forum posts: 1
Oct 25, 2013, 9:46:06 PM via Website
Oct 25, 2013 9:46:06 PM via Website
So,
I have a Sprint Galaxy S4 on Ting Mobile. I have had it for about 3 weeks. On Wednesday, for the first time, my phone started into a crash loop while I was crossing the SF bay (low/no reception area).
I have gone through extensive trouble shooting and here is what I know.
1) The crash occurs if my mobile data connection is weak/no service.
2) It does not occur if I am on Wifi.
3) It does not occur in Safe mode.
4) I can actively cause the crash by selecting the option to "Restrict Background Data" and then turn off my Wifi. This will cause the crash 100% of the time almost immediately after I turn off the wifi.
5) The crash still occurs after deleting all 3rd party apps.
6) The crash still occurs after doing a Hard Reset to reset the device to factory settings.
Does anyone have any thoughts? Is this a hardware issue?
The last idea I have is to reset all factory apps to their pre-updated states and repro the crash there, but I am starting to conclude that the bug may be in the hardware.
Thanks,
Coop
I have a Sprint Galaxy S4 on Ting Mobile. I have had it for about 3 weeks. On Wednesday, for the first time, my phone started into a crash loop while I was crossing the SF bay (low/no reception area).
I have gone through extensive trouble shooting and here is what I know.
1) The crash occurs if my mobile data connection is weak/no service.
2) It does not occur if I am on Wifi.
3) It does not occur in Safe mode.
4) I can actively cause the crash by selecting the option to "Restrict Background Data" and then turn off my Wifi. This will cause the crash 100% of the time almost immediately after I turn off the wifi.
5) The crash still occurs after deleting all 3rd party apps.
6) The crash still occurs after doing a Hard Reset to reset the device to factory settings.
Does anyone have any thoughts? Is this a hardware issue?
The last idea I have is to reset all factory apps to their pre-updated states and repro the crash there, but I am starting to conclude that the bug may be in the hardware.
Thanks,
Coop
Recommended editorial content
With your consent, external content is loaded here.
By clicking on the button above, you agree that external content may be displayed to you. Personal data may be transmitted to third-party providers in the process. You can find more information about this in our Privacy Policy.