Search results

Hey, awesome! gonna try this later today :) How did you end up fixing that Unity crash? is it related to EGL_BAD_DISPLAY? (I'm looking at the repos under https://github.com/CM12-1-Douglas/ and I can't find any related commits...). Thanks!

Hi! This crash was captured after I flashed your low_memory_killer_kernel.zip ... although I didn't reflash the entire new build (just the kernel, with the previous build I belive). Sure! Willing to try anything you throw at me :) These are awesome gaming/kids tablets and I really wish I could...

Getting a similar crash in libunity.so in Monument Valley 2. Build fingerprint: 'Amazon/douglas/douglas:5.1.1/LVY48F/50.6.3.6_user_636558520:user/release-keys' Revision: '50' ABI: 'arm' pid: 3497, tid: 3516, name: UnityMain >>> com.ustwo.monumentvalley2 <<< signal 11 (SIGSEGV), code 1...

I found the fix for this error. It's caused by a mismatch between the /system/build.prop and /vendor/build.prop (search for "There is an internal problem with your device, and it might be unstable until you factory data reset." on android.stackexchange ... I can't post links on xda yet)...

was going to post the exact same thing :) Just popped the heatsink and I too have a sandisk, and also DAT0 and CLK are under the quarter round "notch" ... the only point I could potentially reach with a hairpin (clipped to ground) would be CMD, if it's the same as in OP's picture (ie. right...