[Oppo Find 5] AngryHapposai:
I can't tell if anything in there is relevant, but since you asked for it... here you go :

...

I/ActivityManager( 955): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.af.synapse/.MainActivity bnds=[540,960][540,960]} from pid 6989

D/PhoneStatusBar( 4116): disable: < expand icons alerts ticker system_info back home recent clock* search >

I/ActivityManager( 955): Start proc com.af.synapse for activity com.af.synapse/.MainActivity: pid=4923 uid=10099 gids={50099, 1028, 1015, 1023}

W/ActivityThread( 4923): Application com.af.synapse can be debugged on port 8100...

I/Adreno200-EGL( 4923): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)

I/Adreno200-EGL( 4923): Build Date: 04/11/13 Thu

I/Adreno200-EGL( 4923): Local Branch:

I/Adreno200-EGL( 4923): Remote Branch: quic/mako_jb_mr1

I/Adreno200-EGL( 4923): Local Patches: NONE

I/Adreno200-EGL( 4923): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 + NOTHING

D/OpenGLRenderer( 4923): Enabling debug mode 0

I/ActivityManager( 955): Displayed com.af.synapse/.MainActivity: +675ms

D/AndroidRuntime( 4953):

D/AndroidRuntime( 4953): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<

D/AndroidRuntime( 4953): CheckJNI is OFF

D/dalvikvm( 4953): Trying to load lib libjavacore.so 0x0

D/dalvikvm( 4953): Added shared lib libjavacore.so 0x0

D/dalvikvm( 4953): Trying to load lib libnativehelper.so 0x0

D/dalvikvm( 4953): Added shared lib libnativehelper.so 0x0

D/dalvikvm( 4953): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init

D/dalvikvm( 4953): Note: class Landroid/app/ActivityManagerNative; has 179 unimplemented (abstract) methods

D/AndroidRuntime( 4953): Calling main entry com.android.commands.am.Am

D/AndroidRuntime( 4953): Shutting down VM

D/dalvikvm( 4953): GC_CONCURRENT freed 97K, 15% free 598K/700K, paused 0ms+1ms, total 3ms

D/dalvikvm( 6989): GC_FOR_ALLOC freed 1086K, 22% free 50087K/63804K, paused 53ms, total 53ms

D/dalvikvm( 955): GC_FOR_ALLOC freed 4070K, 15% free 44105K/51516K, paused 128ms, total 128ms

D/dalvikvm( 6989): GC_FOR_ALLOC freed 1068K, 22% free 50087K/63804K, paused 47ms, total 47ms

D/PhoneStatusBar( 4116): disable: < expand icons alerts ticker system_info back home recent CLOCK* search >

I/ActivityManager( 955): Killing 25848:com.google.android.calendar/u0a66 (adj 15): empty #17

W/InputMethodManagerService( 955): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@42d0d258 (uid=10149 pid=6989)

W/ProcessCpuTracker( 955): Skipping unknown process pid 5110

W/ProcessCpuTracker( 955): Skipping unknown process pid 5112

I/ActivityManager( 955): Killing 4923:com.af.synapse/u0a99 (adj 9): remove task

I/ActivityManager( 955): Killing 32736:com.android.browser/u0a18 (adj 13): remove task

I/ActivityManager( 955): Killing 31764:com.android.settings/1000 (adj 15): remove task

I/ActivityManager( 955): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.teslacoilsw.launcher/com.android.launcher2.Launcher} from pid 4292

D/PhoneStatusBar( 4116): disable: < expand icons alerts ticker system_info back home recent clock* search >

D/dalvikvm( 4292): GC_CONCURRENT freed 2365K, 26% free 33817K/45328K, paused 2ms+4ms, total 40ms

D/PhoneStatusBar( 4116): disable: < expand icons alerts ticker system_info back home recent CLOCK* search >

D/dalvikvm( 955): GC_FOR_ALLOC freed 6131K, 20% free 41462K/51516K, paused 130ms, total 130ms

D/dalvikvm( 6989): GC_FOR_ALLOC freed 1084K, 22% free 50089K/63804K, paused 51ms, total 51ms

...

I totally love breaking my pricey high-tech stuff, so I did exactly what you instructed. :D

After flashing the modified kernel, and a couple of hicups when first starting the app, I can confirm that Synapse now runs perfectly fine on my phone. :victory:

Ahem... I guess this is where I screwed up. I'm pretty sure I didn't do any full wipe when I switched to your kernel... :o

And I believe it is actually working just fine... Since I tried the modified script trick, I will also try flashing your untouched kernel after a full wipe and report back later. :)

Thanks to everyone for their help, dedication and hard work! :good: