12-05-2012 6:31 PM
If you goto Edit Pages from Menu Button and click Edit Page.. Then if you try to remove a page from the group of screens (pages).. it says TouchWiz Error and also no updates for Camera found in this release and also other issues associated with the relese.. I am not sure maybe ATT released the Jelly Bean out of the blue.. I call this a Toilet paper Release...
02-13-2013 7:37 PM
After having tried everything under the sun, I was finally resigned to the idea that I might have to replace the hardware and turn it in for a refurb. The local store rep suggested that I work with the AT&T Device Support folks, who would be able to reflash the phone. i.e. Emergency Recovery (which I tried a couple times) is not the same in that it leaves remnants of old apps around. After the reflash, all was rock solid for a few days. I began trickling in my apps, one by one.
Life was good until I started running the last app that I installed. I loaded Pocketcast and downloaded a couple of podcasts. All was quiet until I got in my car, paired with my Satechi Soundfly and started listening to a podcast. 10 minutes into my ride and the phone reboots. Got to work and the phone rebooted a couple more times. I uninstalled Pocketcast and "unpaired" the Soundfly with no success....the phone rebooted 5 more times in the next couple hours. Brought it back to the Device Support folks who reflashed it again.
All is quiet. I'll run it without Pocketcast for another week and then pair it with the Soundfly...maybe listen to some music. If all stays quiet, I'll know it's the app; if not, I'll know it's the Soundfly. If not for the fact that it was stable when it was ICS, I'd start suspecting the onboard bluetooth.
In any case, I'll post my findings over the next week or so.
02-26-2013 7:25 PM
...am back with an update.
Reflashing worked temporarily...but status returned to random reboots. I have since replaced the phone twice with no success. But I now think that I'm closing in on the problem components. I don't believe there's a silver bullet. Rather, there are multiple targets. I turned off wifi and bluetooth. I then enabled bluetooth and paired only to my headset for phone calls (no media streaming). It's been over 10 hours with no reboots or freezing (where reboots every 2-3 hours was typical).
So...In summary....When ICS, all was stable. When updated to JB, random reboots and freezing. Reboots occurred on several wireless routers. After reflashing and unit replacement, only the last actions have stabilized the phone...turn off wifi and no bluetooth media streaming on Satechi Soundfly (although my Nexus 7 works fine with it). I believe the issue to be a firmware problem and only an update will resolve assuming that Google and/or Samsung acknowledges it. I'm especially concerned that this be resolved soon since turning off wifi as a workaround can put a strain on my data plan.
03-03-2013 11:04 AM
To recap with similar problems as Rickalodeon, my device was stable with ICS. Following the upgrade to JB I also had the reboots and freezing. Mine was definitely tied with wireless, as I could simply turn wireless off and have the freeze. Moving out of an area with wireless could also cause a freeze/reboot.
I got to the point of running without wireless at all, and then my device was stable -- no freezes or reboots, but I expect to use wireless for at least some of my data. I would think that ATT would rather that I use wireless to have less bandwidth used on their network as well (minus their incentive to have me pay for more data).
I have elected to run through the reset scenario one more time to see if I can isolate the problem with a particular app or change. Before doing a reset, I uninstalled applications that had been installed to see if removal of any application fixed the problem... but that did not work. I also tried several wireless fix-it programs, and none worked.
My device went through a reset at the end of last week. For the moment I am trying to minimize changes and tracking everything I do, testing wireless at most steps along the way to see if the symptoms change. I have done a group of changes every day to spread the changes, and rebooted once each day to get a clean start after a bunch of changes. So far so good...
It has only been a few days, but things are stable.
Unfortunately, it feels like the slightest change (not necessarily installing/updating a package) could trigger the freezes again. I am going to hold off on installing most of the other apps for a while to see if things remain stable.
Although this is Android, if it was a wider spread problem I would think we would be seeing broader reports on the scenario that ATT/S3. It is disappointing that either ATT or Samsung would allow their wireless implementation to be impacted somewhere along the line if this is tied to applications doing something at some point. I am no longer using the device to its full potential for concerns that the freeze/reboots will come back. This is definitely something that ATT or Samsung need to address.
I will post an update once I have more observations....
03-05-2013 1:05 PM
marker_this.....We are now connected in this universe in that I have experienced and gone down the very same road as you. I have also come to the conclusion that wifi is the culprit. I did the slow trickle of apps into a new phone, but reached the spontaneous reboot problem within a couple days of receiving a new phone. Here are some of my observations:
My last test was with Wifi alway on. i.e. "Never" sleeps. i.e. If it never goes to sleep or has to reconnect, the rebooting stops. However, if I wander out of range, it will freeze. If I resist the temptation to force reboot, it will reboot on its own.
At this point, I feel like my options are:
03-11-2013 8:17 AM
Update: Just when I think I've tried everything, I find yet another component to consider...my SIM card. I found a buried post on the web that spoke to this possibility. As I look back on this thread, I see some reference to SIM card errors. I may be grasping at straws, but here's my latest test...
Hypothesis: Wifi stability varies from router to router (work, home, in-laws). If the wifi loses connection for a moment, the phone attempts to go back to 4G, the phone freezes and reboots. The phone comes back, connects back to wifi and keeps going until the next momentary connection incident.
Any thoughts? Does this sound far fetched? With nothing to lose, I'm going to see if AT&T will replace my SIM card.
03-12-2013 10:54 AM
Update: Replaced SIM card. No success. (Was able to recreate the problem right in front of the AT&T rep, who couldn't understand it either).
I've even gone into Service Mode and restricted cell data to 2G and 3G...still no success.
Called Samsung....after over an hour of hold time between two calls, I got in touch with Level 2 who will be sending me instructions for me to send them one of my S3's for evaluation and repair.
I can't wait to see what they find....or if they do find something, if they'll tell me what it was (I'm assuming they won't be able to explain how 3 phones that I've had in my possession could have the same problem).
03-14-2013 5:13 PM
Final Update: SUCCESS!!!
I decided that I would send Samsung the refurb S3 that exhibited the same problem as my new one. Before I would do so, I thought I would fire it up with the new SIM (that I just received) to recreate the problem - so that I could claim that it froze/rebooted just before I sent it. To my surprise, it didn't. In fact, it was stable for the next two days....no reboots at all. There were two variables that made it different from when it was rebooting: 1) a new SIM card, 2) I did a Factory Data Reset just before I put it away (when I went to the new phone).
So...I decided that I would do a Factory Data Reset of the new phone and reinsert the new SIM. It's been stable all day. By now, it would have rebooted every time the status of the wifi connection changed.
The solution for my several month journey: remove SIM, Factory Data Reset the phone, reinsert a new SIM card.
Unsolved mystery: Why the problem started after the ICS to JB update; and how would a bad SIM card corrupt something in the system.
I hope this helps. When all is said and done, the S3 is an outstanding smartphone.
03-22-2013 2:36 PM
It appears that I had a different problem than Rickalodeon.
The offender has been identified. Surprise, it is an AT&T app: AT&T Voicemail Viewer.
After going through a factory reset and tracking everything I do (not just app installs but when enabling any feature in an app...) it appears that the problem child was "AT&T Voicemail Viewer" which was an app that I enjoyed. Silly me, when I had the problem and went through uninstalling apps before the factory reset, I had not done the ATT apps since I figured those were solid. Doh!
Here are comments from the Google Play store -- other user comments on the ATT Voicemail Viewer app:
... there are more reports, but hopefully you get the idea of the problems -- reboots after changes to the network state.
The reports of the reboots tied with network state change go back to January. It is disappointing that AT&T has not addressed the problem with their application.
The network changes match my scenario of triggering the freezes and reboots.. I miss using the application (Ireally liked reading texts of msgs left on voicemail), but I do not miss the reboots.