[ICS-JB] Compatibilità Touchpad-Giochi

[gigilattina]

Compatibilit dei giochi con touchpad con ICS e JB

Lista Compatibilità Giochi con touchpad Per JellyBean E IceScreamSandwich



Games where the touchpad is working (maybe some game was already working, I can't tell :P):

9mm (ICS) Works but very laggy
Amazing spiderman (ICS)
Asphalt 7 (ICS)
Asphalt 6 (ICS) (JB) LAGS WHEN USING TOUCHPAD ON JB
Backstab (ICS) (JB)
brothers in arms 2 free+ (ICS) Works with some bugs when you use two fingers on the touchpad NEED POINTER ID STARTING FROM 1
Call of Duty - Zombies (ICS)
Cyberlords - Arcology (ICS)
Dead on arrival (ICS)
Dead Space (ICS) (JB) Touchpad works on version 1.1.33. Actually the game works perfectly with this version on ICS. But the current version on the play store is 1.1.39, and we have reports that in this version the touchpad is not recognized.
Dead Trigger (ICS) (JB)
Desert winds (ICS)
Dungeon Defenders (ICS) NEED POINTER ID STARTING FROM 1
Eternity warriors (ICS)
Fifa 10 (ICS) (JB) LAGS WHEN USING TOUCHPAD ON JB. On ICS, I didn't feel any lag but the sound is cutting while we touch the left touchpad
Fifa 12 (ICS) (JB)
Fight heroes (ICS)
FPse (ICS) (already was working). You need to let the touchpad activation for the app
GraviTire 3D (ICS)
GTA III (JB) Touch is used for changing the radio. LAGS WHEN USING TOUCHPAD ON JB
GTA Vice city (JB) This game doesn't use the touchpads. LAGS WHEN TOUCH THE TOUCHPADS ON JB
Guerilla bob (JB)
Gun bros (ICS) Sometimes (when a message appear, I think) You need to release the touchpad and press again... but I think it's a game implementation problem
Lara croft and the guardian of light (ICS) (JB) LAGS WHEN USING TOUCHPAD ON JB
Max payne (ICS) (JB) Need the touchpad always activated (you can switch it with V0.6+)
Minecraft Pocket edition (ICS) (JB) FREE OF JB LAG (already was working)
Modern combat 3 (ICS) (JB) LAGS WHEN USING TOUCHPAD ON JB
Modern combat 4 (ICS)
Mupen64plus (ICS) (JB) (already was working)
Need For Speed Most Wanted (JB) This game don't user triggers or touchpads. Actually, Touchpad is used for scroll the map, but probably because some misimplementation
Nova 3 (ICS) (JB) You need V 1.0.2 to get this working with the XPlay because Gameloft took off the support to our device
Rises of Glory (ICS) (JB)
Samurai vegeance II (ICS)
Shadow gun (ICS) (JB)
Six Guns (ICS)
Sonic 4 Ep.2 (ICS) This game does not use touchpads, but the gamepad is recognized with the fix (probably with the STEP 1)
Start Batallion (ICS) Works with some bugs when you use two fingers on the touchpad NEED POINTER ID STARTING FROM 1
The Bard's Tale (ICS) (JB) FREE OF JB LAG Apparently this game have native implementation of the touchpad, what means that it don't need the fix to work
The Dark Knight Rises (ICS)
USB/BT Joystick Center 6 (ICS) With this app you can map touchscreen areas to the gamepad and touchpad, making a non optmized game can be played with the xperia play buttons. You can see how to config it here. The result is good in some games and bad in another.
Wild Blood (ICS)

Games where the touchpad is not working

Galaxy on Fire II (ICS) (jb) FREE OF JB LAGTouchpad works and the screen button is gone, but the gamepad don't work. You need to push the area of the screen where the buttons mus be in if you want to play
Nova 2 (JB) touchpad non working + graphical bug at the menu ( not in the game) NEED A NEW TEST FOR V 0.3
OnLive (ICS) Last report: touchpad working gamepad don't. I'm waiting for more details (more details about how to get more details here)
Pewpew (ICS) -The touchpad of this game doesn't work well in the ICS, even without the fix, the touchpad is detected but it's messed up. You can use the cross to move and the buttons to shot. Each button shot in one direction, so, it's like a second cross in the gamepad.
THE KING OF FIGHTERS Android (ICS) This game doesn't use the touchpad, just the gamepad, but the gamepads isn't treated well on ICS... WORKD WELL ON MIUI AUSTRALIA. INVESTIGATING WHY

Provare ad aumentare il parco giochi compatibili in JB

1)http://www.mediafire.com/?3kmlnzdnaw6ynqs Touch pad activator




Installare questo APK e abilitarne la funzione da programma






2)Aggiungere questa riga di codice alla file del file BUILD.PROP siutato in \system

mod.touchpad.startfrom1=1

riporto ciò che è detto nel treath



FOR JB USERS For now, you need to edit the ROM flashable zip. Extract the framework.jar from the JB fix and replace directly on the system/framework folder of the ROM zip. Then, extract the build.prop from the ROM zip, do the described changes, and put it back. After that, flashthe edited ROM zip and install the touchpad activator. The flashable zip is not working, idk why yet. For now, this is the only supported way until I can solve this.

The 'ALWAYS ACTIVATED' behavior that we can choose in the TouchpadActivator app can drain the battery life?
No. The battery life is not influenced by the chosen behavior. The term "ALWAYS ACTIVATED" just means that the touchpad events is always forwarded to the onTouchEvent, but the device is always listen to the touchpad doesn't matter what behavior you choose! (even without this fix)

What ROMs supports this fix?
It can works on CM9/CM10 based ROMs, you need to try to be sure. I tested it on CM10 FXP137 and CM9 FXP138, and maybe the creator of some custom ROM did changes on the framework for himself, and then this fix can be incompatible with his ROM, and it's very likely.
ROMs based on CM7 will not work with this fix because I'm using a new feature of the ICS.

Which games is fixed with this fix?
See post #3

This fix solve once for all the touchpad issues of CM9?
I can't say that. Maybe there's other way to get the touchpad return that is not compatible with CM9 already. Maybe Sony will do a update and change this rules. Only time will telll

My phone brick! What can I do now?
Restore your nandroid backup or rename back the old framework.jar. Just to be clear: I'm not responsible for any bricks or problems of your phone.

After apply the fix, some apps gives FC. Why?
Some games and apps gives FC if their data is downloaded before the fix. It's normal. Try the app a second time, it works on almost every time. If it's keeping FC, then clear the app data and try again. Remember that some games download the data in two steps (first part download, then the app is closed and you need to open it again to proceed). If even with this the app keeping FC, post a logcat on this thread, the ROM you're using, what app is giving those troubles and any other info that you think it's useful.


The touchpad is not recognizing at all. Why?
As I need to make many tests and reboot the phone... It's very likely that I let the gamepad slided down. But, after some pain I realize that when I didn't slide down the gamepad after the reboot, the touchpad doesn't work (That is, the gamepad was already slided down, so, I didn't do it after the reboot). So, if anyone experiencing this problem, just slide up and down the gamepad and test again. This is the only situation that something like that happened to me.

What is PointerID?
pointerID is just an identification for your finger when it is touching the touchpad. It's a way to the phone know what is each finger. On GB, this ID start at 1 (finger 1, finger 2, etc...). On ICS, it start at 0 (finger 0, finger 1...). Some games do some shameful validation based that the first id will always be 1 and then get problems on GB. This is why this option is included. As it is a new resource and I'm considering it experimental, when you reboot the phone the pointerID will allways be setted to start at 0.

The pointerid starting at 1 is working better than starting at 0. Can this be the default behavior?
Yes, you can set the pointerid starting at 1 as the default behavior. Just put on the build.prop this: mod.touchpad.startfrom1 = 1. You can do this by yourself if you feel that this new behavior is better than the default one. The idea is remove this switcher and let the pointerID permanently starting at 1 (as it is on GB), but I need to do some tests to make sure that all will work okay.

There's a GB version planned for the future?
No. I'll not make a GB version for this fix, for two reasons:
1 - It's a completely different fix. The concept of this fix is based on the onGenericMotionEvent, that exists since ICS. To make a GB version we need to analyse the stock GB support for touchpad entirely, not just the framework java code, and probably will be only possible to implement directly in the sources.

2 - I don't have interest. I think we have to look forward, and we have GB ROMs good enough for gaming. Also soon, with the V 3.0 of the turbo kernel, we can make a dual boot with GB and desired ROM and then use GB just for games.

Do I need to install the touchpad activator?
No. You don't need. Editing the build.prop and flashing the zip/replacing the framework probable will be enough to get good results. BUT some games need to be tricked to get the touchpad working. For example: Max Payne checks the SDK version to activate or not the touchpad. You can't change the SDK Version in the build.prop, otherwise you'll get big problems (like the data partition wiped) when you reboot the ROM. So, to avoid this problem, you need to set the touchpad behavior, in the touchpad activator, to ALWAYS ACTIVATED. The option to set the pointer ID s becoming obsolete, because every game should work with pointerID starting at 1. The next version of the activator will not have this property anymore and this option will be setted directly in the build.prop







Tread Orinale Touchpad: http://forum.xda-developers.com/show....php?t=2135043





Se vi sono stato di aiuto premete il tasto Thanks!!!



per ogni problema potete chiedere !!! io sono qua !!!