Hi,
I created a very similar post to yours -> Android Custom ROM (AOSP 5.1.1) Reboots on Samsung Galaxy Tab 2
URL:
http://forums.androidcentral.com/sa...osp-5-1-1-reboots-samsung-galaxy-tab-2-a.html
Briefly what I did was connect the Tablet to Eclipse using LogCat through USB Debugging.
Note: The internal LogCat was completely useless. The screen turned off prior to the reboot process.
With that I only decided to filter out the error messages.
What I found is the following process with error.
10-13 15:41:45.481: A/libc(5773): Fatal signal 6 (SIGABRT), code -6 in tid 5773 (gpsd)
Seems this message means its freezing. (I would need confirmation from some Android professionals) But thats it. It just started.
What I think is causing the issue is the touchscreen receiver freezed up. (The tablet kept working as the characters in the game were still moving normally)
The other issue would by some type of synchronization going on.
Through some other forums I read people mentioned it would be either Google Play Services which is causing issues or the internal Battery failing (ie, disconnecting). On the last issue I had replacced the battery and it didn't work.
The Wipe of Cache is the most used solution everybody says. Its a pointless solution. My focus would be either finding a good rom that works and or detecting what physical component is failing.
(Being RAM, Overheating CPU, Memory Card - be it internal or external)... but again, I can't find out what it is. On my end.. It's driving me nuts, as I started out with the stock firmware and moved on to customized firmwares (such as Cyanogenmod and AOSP ... different Android versions)