[Galaxy Tab 7.7 Android Development] daniel_hk:
If you have clear data of settings, it would behave like booting the first time. Hit the build number 7 times in About would show the Developer Options. You may clear again if you are not sure or some settings are not working.

What did you mean by "dead"? There is the user button in top of Quick Settings but only for owner.

In case you don't know, clear data of Settings

Settings > Apps > Settings(or any app) > Storage > CLEAR DATA.

Seetings would quit immediately.

Thanks for you report and nice words.

Frankly, I rather have some detail that me or others can repeat what you said.

Don't misinterpret what I'm going to say. it is in general, not any particular person. I really appreciate your report.

I have read all your posts for sometime, correct me if I'm wrong, I haven't find any detail yet.

I have said many times. A log, a screenshot or just a picture on the screen would definitely help..

Occasionally, the outcome you described might give us something to start but it would be rarely the case.

1. I don't have a tab plus so I can't help much. That's the port I thought it would work. If it doesn't, just disable it. However, if you tap the screen a lot of times at suspend. It would generate multiple interrupts. I use interrupt to issue the "wake up" action. It might take a while if the cpu is idle. When (I think, can't remember) 8 or 16 interrupts are reached, you might hang the touch screen driver not the system. Power button would still wake your screen. I can't tell which case since there is no further info.

2. For things like random reboots, freezes etc., I never do or fix anything on that. I don't think anyone could with just term "random xxx". What really "fix" these might be a just combination of other things.

The log always give us a better idea. Whether its an app doesn't support the new system and have system err, a missing library or resource, the incompatible old data, etc. These kind of intel. might answer you right away.

Again, this is for the general not anyone particular. ;)

Most of the people don't care about the detail but result. I'm not. I always try clearing things up. At least I do my part for those who want to learn or really help (or show off to your friends). :D

If you want to hang or freeze a device, especially the oldies like ours, it won't be difficult.

There are a few bottlenecks.

1. The eMMC we have is the early generation. The throughput is low. Multiple access would definitely make you feel freezes. In those days when apks are just a few M, we might not experience it. Now we have apks upto a few hunderd M. eg. when you install a large apk and want to do anything else, you would experience delays for sure.

2. The new ART stack (introduced in KK and default since LP) use the AOT (ahead of time) compiler which would compile the part of source you are going to execute. Like the JIT (just in time) comiler, there are many advantages especially for those latest devices with multiple cores, faster eMMC and RAM. For old devices like us, it is a gift and a curse. If you know the situation, you might get a better experience, just be patient and avoiding too many processes at a time.

There is a time out for the AOT and a watchdog in the system. If AOT doesn't finish the compiling in 10mins., it would return fail. An apk might have many processes, 10mins. is usually "more" than enough. But, when we start or switch to another apk/process, some of the background process might swap out without notice (when the limit is reached). It would be so easy for a background process to reach that if a few big apks (Google Play service is definitely one of those) are running at the same time. After 10 mins. of burning resources, it would most likely crash (or hang) the system. That's why Facebook reported fail in many old devices since LP. I have increase the time out to 30mins. which allow most of the large apk (eg. Facebook) to run but this is not a fix.

3. The amount of ram might be an issue but not that serious as most of the people think. The Linux kernel (which we are using) is known to have a good memory management. Pre-emptive multitasking is a good thing but also spoil us for impatience. We just can wait for a process to finish and start another. No matter how much RAM we have, background processes would swap to the "slow" eMMC eventually.

As anyone can see, I would spend half an hour to explain. Clearly I don't want to ignore anyone. Am I wasting my time? You tell me. Naturally I would be frustrated when people just don't want to read but ask. Especially for the tab plus which I don't have. Frankly, I'm not your relative and not even an acquaintance. I also have my own life to live.

Again, If anyone don't want to read first. Just don't post here. Start your own thread and say whatever you want. ;)