(04-21-2014, 10:35 PM)zxcvbad Wrote: [ -> ]SeannyM, I'm waiting since today, when I've seen you've made fix. Thanks 
Wow, fastmem no longer crash on v@66, just checked on my z ultra
If you want, I can upload my APK to tie you over until it is merged
Only thing is, I found out that mapping L and R to physical buttons still does not work. You can use the onscreen L and R buttons though. I will look into the physical buttons soon.
And yeah, fastmem does work, the fix was submitted a while ago
SeannyM, apk would be great, with fastmem it's overall +5 fps in my case, so it's definitely needs to be tested
There was another issue with buttons - it wasn't possible to press on-screen buttons simultaneously, one button at time. Is that fixed as well?
(04-21-2014, 11:48 PM)zxcvbad Wrote: [ -> ]SeannyM, apk would be great, with fastmem it's overall +5 fps in my case, so it's definitely needs to be tested There was another issue with buttons - it wasn't possible to press on-screen buttons simultaneously, one button at time. Is that fixed as well?
No, I've been looking at the multitouch issue but don't have anything yet. I'm not that good with java (the Android interface) which is why I solved the L and R issue because the problem wasn't in the java :p Anyways, download my APK here:
https://drive.google.com/file/d/0B6RhUm9SewQgRnRnZmpZYU9kOTg/edit?usp=sharing Make sure you uninstall your current dolphin app because mine was built with a different signature and they won't install over each other. Don't worry about losing saves when uninstalling, they stay there.
SeannyM, thanks for apk, was able to test it. Found that holding l/r doesn't seems to work, you would have to press it rapidly (in order to drive for example) also it does break hardware buttons, you can still bind it in settings but they won't work in game. Couple of times android menu buttons wasn't responding while I was able to press in-game onscreen buttons.
(04-22-2014, 12:46 AM)zxcvbad Wrote: [ -> ]SeannyM, thanks for apk, was able to test it. Found that holding l/r doesn't seems to work, you would have to press it rapidly (in order to drive for example) also it does break hardware buttons, you can still bind it in settings but they won't work in game. Couple of times android menu buttons wasn't responding while I was able to press in-game onscreen buttons.
The L/R binding to hardware never worked, so it's not a regression. You can hold the buttons down, but your finger has to be completely still and it is difficult to do. I am working on the holding and the multitouch issues right now, then I will work on trigger mapping.
SeannyM, great, keep us posted. P.S. I know hardware L/R was broken, I was talking about rest of the buttons
(04-22-2014, 01:32 AM)zxcvbad Wrote: [ -> ]SeannyM, great, keep us posted. P.S. I know hardware L/R was broken, I was talking about rest of the buttons
What do you mean? My hardware buttons still work. Anyways, I have a new build here for you to test:
https://drive.google.com/file/d/0B6RhUm9SewQgVEQ2V2lwTXBkRWc/edit?usp=sharing I fixed the button holding issue. Next up is multitouch. I'm likely going to be working with these controls for a while, there's a lot to do lol.
(04-22-2014, 02:07 AM)SeannyM Wrote: [ -> ] (04-22-2014, 01:32 AM)zxcvbad Wrote: [ -> ]SeannyM, great, keep us posted. P.S. I know hardware L/R was broken, I was talking about rest of the buttons
What do you mean? My hardware buttons still work. Anyways, I have a new build here for you to test: https://drive.google.com/file/d/0B6RhUm9SewQgVEQ2V2lwTXBkRWc/edit?usp=sharing I fixed the button holding issue. Next up is multitouch. I'm likely going to be working with these controls for a while, there's a lot to do lol.
Will check it soon. With your previous build none of the hardware buttons worked, not just L/R (like I've said it was possible to bind them all,it's just they didn't worked once in game). Builds from buildbot worked fine (except L/R) was testing latest build this morning. Perhaps it has something to do with native dualshock 3 support in Xperia stock rom. I'll let you know when I'll get my hands on your latest build
SeannyM, just tested, I believe those problems I'm experiencing are linked to fastmem + bt. Hardware keys just not responding/freeze if I'm running any game with fastmem turned on. At some point I've got "bt share process crash" system report, that could be fastmem uses RAM till all the other processes are terminated, including the one responsible for dc3 (dc3 native app), (even gamepad turns lights off), few times live wallpaper was turned off. Without fastmem all worked fine, thanks for fixing L/R :-)
(04-22-2014, 03:37 AM)zxcvbad Wrote: [ -> ]SeannyM, just tested, I believe those problems I'm experiencing are linked to fastmem + bt. Hardware keys just not responding or freeze if I'm running any game with fastmem on. At some point I've got "bt share process crash" system report, that could be fastmem uses RAM till all the other process got terminated, including Sony's dc3 native app (even gamepad turns lights off), few times live wallpaper was turned off. Without fastmem all worked fine, thanks for fixing L/R :-)
Well it does say "unsafe memory optimizations", so it makes sense. I get freezes and crashes with fastmem too, one of the places I get them consistently is loading save states, it usually locks up after loading two states in a row. With fastmem disabled Dolphin is definitely more stable.