[Galaxy S III Original Android Development] NeoBlade:
I had a brief chance to check the logs earlier today... No idea if this is relevant or not but messages like these kept cropping up once I noticed the behaviour as it tried to catch up...

09-28 21:04:49.469: I/Choreographer(5757): Skipped 160 frames! The application may be doing too much work on its main thread.
09-28 21:04:49.489: I/InputReader(2568): Touch event's action is 0x0 (deviceType=0) [pCnt=1, s=0.67 ]
09-28 21:04:49.489: I/InputDispatcher(2568): Delivering touch to current input target: action: 0x0
09-28 21:04:49.489: I/InputDispatcher(2568): Delivering touch to current input target: action: 0x0
09-28 21:04:49.489: I/InputDispatcher(2568): Delivering touch to current input target: action: 0x0
09-28 21:04:49.499: I/SurfaceFlinger(2033): id=80(1) createSurf 0x4264dd54 (1x1),1 flag=400, DonversationComposer
09-28 21:04:49.499: D/KeyguardViewMediator(2568): setHidden false
09-28 21:04:49.499: D/STATUSBAR-StatusBarManagerService(2568): setSystemUiVisibility(0x0)
09-28 21:04:49.499: D/STATUSBAR-StatusBarManagerService(2568): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
09-28 21:04:49.519: D/libEGL(5757): loaded /system/lib/egl/libEGL_mali.so
09-28 21:04:49.524: D/libEGL(5757): loaded /system/lib/egl/libGLESv1_CM_mali.so
09-28 21:04:49.529: D/libEGL(5757): loaded /system/lib/egl/libGLESv2_mali.so
09-28 21:04:49.534: D/(5757): Device driver API match
09-28 21:04:49.534: D/(5757): Device driver API version: 10
09-28 21:04:49.534: D/(5757): User space API version: 10
09-28 21:04:49.534: D/(5757): mali: REVISION=Linux-r2p4-02rel0 BUILD_DATE=Thu Aug 23 10:54:04 KST 2012
09-28 21:04:49.614: D/dalvikvm(9687): GC_CONCURRENT freed 260K, 8% free 12658K/13703K, paused 12ms+6ms, total 115ms
09-28 21:04:49.639: D/OpenGLRenderer(5757): Enabling debug mode 0
09-28 21:04:49.659: I/InputReader(2568): Touch event's action is 0x1 (deviceType=0) [pCnt=1, s=]
09-28 21:04:49.659: I/InputDispatcher(2568): Delivering touch to current input target: action: 0x1
09-28 21:04:49.659: I/InputDispatcher(2568): Delivering touch to current input target: action: 0x1
09-28 21:04:49.659: I/InputDispatcher(2568): Delivering touch to current input target: action: 0x1
09-28 21:04:49.669: W/TwSweepActionListView(5757): [handleDataChanged] IN
09-28 21:04:49.804: V/Mms/Conversation(5757): loadingThreads(),return=false
09-28 21:04:49.804: V/Mms/Contact(5757): invalidateCache(),isInvalid=false
09-28 21:04:49.879: D/dalvikvm(9687): WAIT_FOR_CONCURRENT_GC blocked 0ms
09-28 21:04:49.939: D/dalvikvm(9687): GC_EXPLICIT freed 254K, 9% free 12519K/13703K, paused 4ms+6ms, total 64ms
09-28 21:04:50.059: D/Mms/ConversationListAdapter(5757): bind() complete
09-28 21:04:50.109: D/dalvikvm(17048): GC_CONCURRENT freed 453K, 8% free 13379K/14535K, paused 14ms+2ms, total 50ms

Other stuff like this I presume is with the ROM itself...

09-28 21:04:54.334: D/STATUSBAR-NotificationService(2568): Noti Alert - mSystemReady:true, AlertEnabled:true
09-28 21:04:54.339: I/TwDVFSBroadcastReceiver(8891): CPU dvfs table is not supported in this mode.
09-28 21:04:54.359: I/TwDVFSBroadcastReceiver(8891): CPU dvfs table is not supported in this mode.
09-28 21:04:54.364: I/TwDVFSBroadcastReceiver(8891): CPU dvfs table is not supported in this mode.
09-28 21:04:54.369: I/dalvikvm(5961): Turning on JNI app bug workarounds for target SDK version 10...
09-28 21:04:54.369: I/TwDVFSBroadcastReceiver(8891): CPU dvfs table is not supported in this mode.
09-28 21:04:54.374: I/TwDVFSBroadcastReceiver(8891): CPU dvfs table is not supported in this mode.
09-28 21:04:54.404: I/TwDVFSBroadcastReceiver(8891): CPU dvfs table is not supported in this mode.
09-28 21:04:54.409: E/Trace(5961): error opening trace file: No such file or directory (2)

As I believe the "I/TwDVFSBroadcastReceiver" might be related to Apex Launcher being hardware accelerated. If I'm going along the right lines I'll carry on as I don't want to clog up the dev thread by going off on a tangent.