(12-27-2014, 03:01 AM)[Unknown] Wrote: Just to clarify, you mean that v0.9.9.1-896-g4ed97f9 does not work, and v0.9.9.1-892-ge43c7af does, right? There are multiple v0.9.9.1-896. The "896" number isn't what tells me what version it is, it's the part after the g. This is because git isn't exactly "linear" - multiple developers work on the project at the same time.
Assuming that range is correct, I would've expected v0.9.9.1-1280-g326c298 to fix it. v0.9.9.1-1292-g2db9275 should've had that fix (again, I'm assuming that's the one you mean probably.)
Can you double check with the latest git build? If it still happens, can you confirm which git builds you were testing (are my assumptions correct)?
-[Unknown]
yes. as you stated above, v0.9.9.1-896-g4ed97f9 does not work, and v0.9.9.1-892-ge43c7af does.
here my finding
not having force closed issue after dueling
v0.9.9.1-892-ge43c7af
having issue (tested)
v0.9.9.1-896-g4ed97f9
v0.9.9.1-1280-g326c298 (yes. this build i means on previous post. not fix the problem as you expected)
0.9.9.1-1292-g2db9275 (not fix the problem as you expected)
v0.9.9.1-1310-g1a0f537 (latest build in http://buildbot.orphis.net/ppsspp/index.php?m=fulllist )
still having auto/force closed issue after dueling in latest build.

