yashsingh1/xdaforums huggingface dataset:
[Xperia Play Android Development] ThePlasticBling:
OK thanks. Do I need to manually adjust settings or will it do things automatically?
[Xperia Play Android Development] farenheith:
Manually. The games we know that need some change in the activator, you can see in the post #3
[Xperia Play Android Development] farenheith:
Last recommendations!

Guys!

The next version of the touchpad activator will not have the pointer ID option anymore.

If your current ROM doesn't have the following line in the build.prop already, please, include it:

mod.touchpad.startfrom1=1

This line will set the pointerID behavior to always start at 1

REASON

This is the Stock gingerbread behavior. We tested a lot of game and this option is not affecting any of them and improve compability with anothers (until now, we found Star battalion and Modern combat 2 recognizing the touchpad with this option).

That's why the toggle will be removed of the touchpad activator!!! The best is the pointerId always start from 1
[Xperia Play Android Development] f3w1n:
Nice to see improvemets! :)

How is the touchpad-lag-fix going? If you and dan solve that there will be no reasong to stay on gb!
[Xperia Play Android Development] farenheith:
No solutions for the touchpad lag on JB, as far as I know :(. But Dan found some good reasons for the touchpad lag, but is really hard to solve.

This is really a pain in the ass...

I'll release a new version of the touchpad activator when I implement an option to automatic switch the touchpad behavior for the listed games (for example, you choose Gallery and Max Payne to use the always activator behavior and, when the apps is in the foreground, the activator switch the behavior automatically) sometime ago I already discussed this possibility with CosmicDan, now ThePlasticBling questioned about that and the touchpad fix is a good time without updates, so, I think this is the moment.

but I'm really a beginner in android programming and I'll take a good while to get this
[Xperia Play Android Development] clivejefferies:
For the touchpad activator, it sounds like you want a background service running that changes the value when you start the game. I am not sure if you can listen for other apps starting. It would be easier just to have a drop down box to choose a game which updates the value.
[Xperia Play Android Development] farenheith:
Actually yes, there's a way. I'll give you an example: The profile options of setCPU.

We can make a condition to switch the CPU settings when an app is in the foreground, and it works pretty good. i use this with Mupen64, to switch the CPU to the most aggressive settings when this app is running in foreground.
[Xperia Play Android Development] clivejefferies:
It seems like a lot of work for something simple.
[Xperia Play Android Development] farenheith:
Maybe, but we already have something simple. The effort to change the behavior with the current solution is almost the same of have a dropbox and the number of games we need to do that is very low so far.

Also, a appstate listener or even a generic state listener is a useful class to have. Imagine the possibilities! We can use this to set cpufreqs like setCPU does, we can change the touchpad behavior, what else we can do?

I think a lot of things, we just need to have an idea of something useful to trigger when a particular app is running
[Xperia Play Android Development] Dany XP:
I know it's a noob question, so i apologize.

Do i need to erase completly what it's inside my build.prop and just copy&paste this: http://xdaforums.com/showpost.php?p=31822603&postcount=81

Or do i have to correct line by line the ones are incorrect?
[Xperia Play Android Development] farenheith:
Just locate and change the lines in red
[Xperia Play Android Development] Dany XP:
The lines in red ok. What about the others?

And these:

ro.semc.version.cust=1253-3429

ro.semc.version.fs_revision=4.1.B.0.431

ro.semc.product.model=R800i

ro.semc.ms_type_id=AAD-3880119-BV

ro.semc.version.cust_revision=R1I

ro.semc.content.number=PA5

ro.semc.product.name=Xperia Play

ro.semc.product.device=R800

ro.semc.batt.test.min_level=70

ro.semc.version.fs=WORLD-i

ro.semc.rem-roam-icon=1

ro.semc.xloud.supported=true

ro.semc.batt.test.z_threshold=50

ro.semc.batt.capacity=1500

ro.semc.sols.company-code=5

ro.semc.sols.product-code=87

ro.semc.timescape_keys=Sony_Ericsson_Xperia_PLAY

ro.semc.dashboard.xperiaplay=true

ro.semc.wifi.hostapd=1

ro.semc.dashboard.searchuri=http://pss.dl.playstation.net/pss/content/list.html

Those are just not in the build.prop. Do i have to add them? and if i have, where?
[Xperia Play Android Development] farenheith:
Dude,

Really, just locate and change the lines in red.

All these lines is from stock GB, is there if someone want to do experimentation, but if you want to experimenter you must do it for your own. For the mod, just change the lines in red.

As I didn't get thIs questions before, maybe I didn't let it clear in the post, so, I'll put it in red and bold there
[Xperia Play Android Development] Dany XP:
Ok i got it, thanks
[Xperia Play Android Development] Dany XP:
Thank u farenheith, everything work allright! CM9.1.

You can add The Dark Knight Rises to list, works just fine.
[Xperia Play Android Development] Hardtron:
Hi everyone!

I used this fix in CM9.1 and was so good that I could stick with it permanently.

I've been testing some roms JB (CM10 and KXPmilestone1-r1) and am really liking what I see. Are very fluid and particularly not found any bug than those already known.

They have everything to be a daily rom, especially now with the camera functioning. But we own XPlay, and things are slightly more complicated.

I wonder if the friend farenheith still working on this great project.

Here are the framework.jar of CM10FXP149 and KXPmilestone1-r1 respectively.

I'd be honored to be able to test them!

Edit: Excuse me. By mistake I have attached the wrong files.
[Xperia Play Android Development] farenheith:
I thought only KXP was not working with the fix. Are you sure FXP149 is not working either?

I'll patch the files in a while, but have you tried to replace the framework.jar directly in the ROM flashable zip and then flash it?

There's reports about errors while trying to use the touchpad fix flashable zip in JB, maybe because I did something wrong, idk :P or maybe for not space enough in the system partition
[Xperia Play Android Development] Hardtron:
I tested the two roms.

First follow the steps for you: Replace build.prop and framework.jar with the fixes in the ZIP. After flash and rebooted.

In both roms I got stuck in the boot animation.

Then I tried to just replace the framework.jar to later edit buid.prop. Still got the boot animation.

I do not know if it is correct, but also tried to install the original rom normally. Then I tried to replace the framework.jar corrected, but I get a warning that the copies can not be made for insufficient space in the partition. In both roms.

I used root explorer and WINRAR for this
[Xperia Play Android Development] farenheith:
Dude,

You sent the framework.jar from the fixes, unfortunatelly. You need to send me the original framework.jar from the last releases of the ROMs. I saw that those framework.jar you sent me is already modded. The kxp one is modded with the version 1.0, so, those files is the one from the fixes

Edit: I just downloaded the FXP149 a few minutes before post this, so, you don't need to bother with this one, but send me the one from kxp, because I'm getting some troubles with the Internet and I'll take some hours to get this
[Xperia Play Android Development] Hardtron:
Sorry! I was thinking away and confuse me with the files.:silly:

Now I have attached the correct ones.
[Xperia Play Android Development] CosmicDan:
Yeah, I'm trying to add the fix to Project Jellyzeus faren. I went by the manual smali patching in post #2 because that is newest, but it broke my touchscreen input. Then I tried to compare CM10 framework with mine, and it's a much older version of it. So I'm stuck and I'm waiting on testing the ICS InputTransport forward-port until JB instructions/mod is updated :(

EDIT: Even though my touchpads don't work, I was successful in porting the ICS InputTransport to Jellyzeus. However in GTA3, pressiing a touchpad while moving still causes the FPS drop :(

It took me a week to get that far, now I have no idea. We need to find a way to get more information on the system processes, to find out where the code is that's causing this "flood".
[Xperia Play Android Development] MonY960:
hey farenheith can you add CM7 fix ?
[Xperia Play Android Development] chery2k:
Farenheith says he won't make a CM7 fix.
[Xperia Play Android Development] MonY960:
:( why ?
[Xperia Play Android Development] rashid.fairus:
read the OP
[Xperia Play Android Development] farenheith:
Sorry, I was off solving some business, but I'll patch the files right now!

The problem with the touchscreen input broking is the MotionEvent patch. You can just grab the MotionEvent class from the PACman sources. This class is never changed in any ROM, and if you patch it right will just be exactly the PACman version. I'll take a look if the instructions for this class is updated.

About the touchpad lag, I'll tried your new version, and I can test it with FPSe, try to grab some new information... I don't know if you released something yet, I was out some time solving personal and professional stuff :/... busy week

If you didn't release this version with the ported input yet, maybe you can pass me the kernel so I can test it too
[Xperia Play Android Development] farenheith:
Okay.... files patched

here is the CM10 fxp149 one

here is the aokp jb one

Those files is not flashable zips! You need to replace it in a copy of the ROM flashable zip and then flash the ROM again.

@Hardtron, when you test it, give me a feedback so I can put the links in the OP

thanks!
[Xperia Play Android Development] Hardtron:
Ok, I'll start testing now.

Preparing the ZIP package of CM10.
[Xperia Play Android Development] farenheith:
Dude, is not that simple to make a fix for CM7. There's no genericmotionevent in GB, and this is the base of our fix here.

To make it work in CM7 like it's working in Sony ROM, we need a lot of efforts to implement all the way through, and unfortunately it's beyond my knowledge.

Also, I prefer to focus in the new android versions, so we can make our device be alive for more time. The Stock GB is good enough in what is proposed and also we have a lot of good ROMs stock based, so, you have good choices for GB.
[Xperia Play Android Development] CosmicDan:
Yeah, that's the bit I had trouble with. OK I'll figure it out, I was kinda rushing but I realized I can test Touchpad lag even without your fix finished yet.

The ported Input was in the ROM, kernel is unchanged. I reverted it to stock JB style in Jellyzeus r2 release in case it causes issues, it had no effect. However in androidfw InputTransport I've tried turning on verbose logging just now, and I see a *lot* of errors related to input queue even on touchscreen events. I need to investigate this, maybe it is infact the touchscreen driver that is "interfering" with the touchpad event queue which causes the lag.
[Xperia Play Android Development] Hardtron:
I managed to get a boot full now. But changed the sequence of change the ZIP package.

In the first attempt made ​​to replace the framework.jar and build.prop in the package. I did a clean install of the rom changed without the google apps. With this process does not boot past the logo of the kernel.

After redid the ZIP package of rom just changing the framework.jar and keeping buid.prop legitimate. The boot went well, only then did the changes in build.prop and rebooted.

I installed gapps and now I have the complete system.

I'll start testing the games now.
[Xperia Play Android Development] farenheith:
If you edited the build.prop with a root explorer you have a chance that it wans't keep the changes. Take a look after reboot if the changes you made is still there.

If the build.prop is untouched, then you need to try again replace it in the ROM zip. Finally, if you get bootloops, you'll need to grab a logcat of the boot. To do this, you need adb and a USB cable. Plug it in the device, and, when it's starting, you'll need to try this command (in cmd with administrator option):

adb shell logcat > logcat.txt

Try it until the windows look "freezed". If you get some return like "device offline" keep trying. Finally, let the logcat processing for a while and finish it with ctrl+C. The file must be writed in the current folder. Send it to me.
[Xperia Play Android Development] Hardtron:
I have the build.prop with the changes even after rebooting. Just took care to delete the file .BAK before restarting.

But thanks for the advice logcat. Can I still need this.
[Xperia Play Android Development] farenheith:
mmmm.... Maybe the problem then is something with line-terminator, the editor you used in the PC maybe did the difference.

If you want, you can save the build.prop edited in the phone in your PC for further tests
[Xperia Play Android Development] Hardtron:
Okay! We have touchpads working fine in NOVA 3!:D:D

Tomorrow I will test more games.

I am attaching here the build.prop corrected.
[Xperia Play Android Development] farenheith:
Thanks for the report!

Got any lag?
[Xperia Play Android Development] Hardtron:
It really can be that.

I am using notepad to do this. Can you indicate a more suitable?
[Xperia Play Android Development] farenheith:
I use textpad
[Xperia Play Android Development] Hardtron:
I played only 4 minutes, but the impression I got is that it runs very well, worked as in GB. Maybe installing the new drivers Adreno V3 improve further.

Unfortunately I have to leave it at the moment, but I will continue with the tests here a few hours.
[Xperia Play Android Development] CosmicDan:
You can not use them on any of our JB ROM's.
[Xperia Play Android Development] Slothboy:
If you're using Jellybean then don't flash the Adreno drivers, reports of loss in performance
[Xperia Play Android Development] CosmicDan:
Well, touchpad lag will be fixed in next Jellyzeus release :) Will report my findings to all the other JB ROM builders.

It was *very* easy, I can't believe I wasted a week on forward-porting ICS transport LOL.

// Socket buffer size. The default is typically about 128KB, which is much larger than
// we really need. So we make it smaller. It just needs to be big enough to hold
// a few dozen large multi-finger motion events in the case where an application gets
// behind processing touches.
//static const size_t SOCKET_BUFFER_SIZE = 32 * 1024;
static const size_t SOCKET_BUFFER_SIZE = 512 * 1024;
[Xperia Play Android Development] farenheith:
Are you serious this worked out?!?!?!

Amazing!!!

How did you figure out?
[Xperia Play Android Development] CosmicDan:
Well after verbose logging I found that the frametime was -1, which means that it is supposed to be handled by the driver/hardware and not the InputTransport. Eventually the bufferqueue would report a bunch of errorcode 11 which is related to deblocking the transport, so I tried a few experimentation and thought "hang on, maybe we just need a bigger buffer...." turns out that's all it was :)
[Xperia Play Android Development] farenheith:
I think this can help with the touchscreen Input either, making it still more smoother!

Good one!

Can't wait to try it!
[Xperia Play Android Development] CosmicDan:
Yeah maybe. But now system server will use about 480KB more RAM than before :P oh well!
[Xperia Play Android Development] farenheith:
480KB is almost nothing!

Also, maybe you can do the trick with half the value increasing it just in 240KB, that is, nothing / 2 ;P
[Xperia Play Android Development] CosmicDan:
Default was 32. I tried 128 first, lag dropped a tiny bit. Then 256, lag was about halved, tried 400, lag was still I tiny bit there - so I think 512KB buffer is best.
[Xperia Play Android Development] farenheith:
I see...

Well, better 480kb used than wasted lol
[Xperia Play Android Development] CosmicDan:
Lol. I don't think it matters that much, JB is much more memory efficient than ICS anyway. Finally, JB is at a state for our device that puts ICS to shame in every way :)

I only tested gamepad with GTA3, the game was not running very well. But i was on SLot 2 and not overclocking at all, so maybe (when Jellyzeus r3 is out, should only be 24 hours max) some people should test on Internal with slight overclock on gaming. Might be better than GB.
[Xperia Play Android Development] Hardtron:
Hello everyone!

I just tested two more games (Batman TDKR and MC3).

Really delay problem of touchpads there.

I'm doing the tests without overclock.

I would like to get the path to edit the bufer as cosmicdan said. This is amazing!

I looked at the changelog of FXP. Looks like FXP will fix the proximity sensor.
[Xperia Play Android Development] CosmicDan:
Yes, proxy sensor already fixed in Jellyzeus r2. And r3 with have no more touchpad lag.

Sent from Xperia Play (R800a) with Tapatalk
[Xperia Play Android Development] Hardtron:
Looking forward to it man!

Then the buffer can only be edited before compilation. Or you can launch a generic fix for roms JB in the future?
[Xperia Play Android Development] farenheith:
I'm afraid a generic fix is not possible
[Xperia Play Android Development] CosmicDan:
Eventually PAC and SlimBean will. Maybe CM10 but I need to make it device dependant before it can be submitted, probably with ro.input.legacytouch=true.

Sent from Xperia Play (R800a) with Tapatalk
[Xperia Play Android Development] Hardtron:
Feedback.

I tested the settings for KXP milestone1-R1 successfully. Full recognition of touchpads in games, NOVA3, MC3, Batman TDKR. But with a little lag in touchpads. It seemed that the game flowed better in CM10 FXP149.

The games were tested without overclocking and without treatment of memory RAM.
[Xperia Play Android Development] wedhusman:
I tried to find missing files from neo l ics rom, compared to play ics beta and lucky, I got a working touchpad. Excluding the app, font, framework and media folders. :)
[Xperia Play Android Development] CosmicDan:
This fix is not for stock ROM's.
[Xperia Play Android Development] olokos:
Need For Speed Most Wanted 1.0.28

Jellybean wedgess pac rom + CosmicDan's kernel r5/6

Dpad + buttons are working great. Touchpads + triggers are not doing anything as the game don't need them.

I've played well for 15minutes now. :)
[Xperia Play Android Development] olokos:
Gta vice city, same config.

Working overall but after 15 minutes I've got FC (has to be game issue) but everything except ANY control was working. Before FC - touchpads are not used (i think same as in most wanted) but Dpad and every other Xperia Play button was working. Had to lower the game graphics but performance is Allright.
[Xperia Play Android Development] farenheith:
How do you get GTA Vice city? I can't find this app in the market
[Xperia Play Android Development] olokos:
Magic :) use Google, warez isn't allowed although it's the only way to play it on our play. It's using the X play buttons so lol, no idea why it's not in the market for us... Oh, triggers are used to look left and right.
[Xperia Play Android Development] farenheith:
lol I'm not talking about warez. I thought it's in some other market, like the guys of EA or Gameloft does
[Xperia Play Android Development] farenheith:
Also... the GTA 3 use the touchpads to change radio. Maybe this one do the same
[Xperia Play Android Development] olokos:
Never used one of them, I've only used Google play. I've reed that we can't get it 'legal way' which is disappointing.

---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------

Nope, it's lagging and radio isn't changed when I try to change it this way. We have to swype radio name left and right on the touchscreen to change it.

---------- Post added at 08:06 PM ---------- Previous post was at 07:39 PM ----------

And again got FC, happens every 15-30 minutes.
[Xperia Play Android Development] farenheith:
Thanks for the reports, dude, but I think I can't list this title in the post 3 as we can't get it in a legal way.
[Xperia Play Android Development] yekasangredevago:
Here you can find it.

https://play.google.com/store/apps/details?id=com.rockstargames.gtavc

Nose region but that you, as it depends on the region if it is available or not, I'm from Argentina, and here is now available to download for 3 days
[Xperia Play Android Development] farenheith:
I see.

I didn't found it before but looks like I can now! Thanks
[Xperia Play Android Development] olokos:
Little update for most wanted. Touchpads ARE used, lol it's actually hard to say that they are used as all what they are doing is scrolling through the in game map... They are some kind of 2 small duplicates of touch screen and they actually act the same way...

And please add the GTA VC to the list :)
[Xperia Play Android Development] farenheith:
Anyone can test "THE KING OF FIGHTERS Android" in another ROM other than MIUI Australia and give me some report (JB or ICS)? I compared the keymap of MIUi Australia with the CM9 and I saw no difference...
[Xperia Play Android Development] cj360:
Not sure if it's listed or not but asphalt 6 from the play store works with your fix. I accidentally bought it at first but I kept it cause the free on from verizon's rom is only for gingerbread.
[Xperia Play Android Development] farenheith:
Are you using Slimbean?
[Xperia Play Android Development] cj360:
Yeah sorry, forgot to mention that. Anyone one slimbean will still have to make the build.prop changes or just flash the fix you made.
[Xperia Play Android Development] farenheith:
Nice, thanks. In the list was only reports from ICS! Any lags with the touchpads?
[Xperia Play Android Development] cj360:
A little, it doesn't ruin the game or anything but it's pretty noticeable.
[Xperia Play Android Development] gopin:
I'm currently running cm10, fxp151 and I noticed that FIFA 12 is not listed as working on jb, we'll it works. Playing the game on a clean install is flawless, after restoring all my junk it lags a little bit, but nothing serious.

Batman tdkr works, it lags , but I can't tell if its due to the touchpad (I think not) after a couple of min playing I got a reboot though.
[Xperia Play Android Development] farenheith:
Thanks!

You know now we have the ff3 remake for android. The game is not optimized for xperia play but maybe accepts d-pad, cross and circle inputs. I'll buy it and see soon :3
[Xperia Play Android Development] :
In my case I'm in wedgess PACman rom (which is awesome) and FIFA 12 worked for me, but it didn't recognized the gamepads and touchpads, so I had to play touching the screen :(

And of course I would like to say thank you to you farenheith, because of your hard work, and your desire to keep alive our Xperia Plays :good:
[Xperia Play Android Development] Dany XP:
NOVA 3 problems

Ok, first of all i have to say that in ics sony based roms i don't think this problem is not present, at least as i recall.

Everytime i try to install (not download, wich is fine) NOVA 3 the play reboot itself. After that, i reopen NOVA 3 and i can see the app is installed.

So the game begins, but instead of "Press x for shoot" or "press O to reload" in the firsr tutorial (or in menus), the game just say "touch this to shot" , "touch that", etc etc...like it doesn't recosgnize my phone as a Xperia Play, and in fact the touchscreen controls works, but not d-pad, and buttons. Ironically, touchpads are the only thing working (left for move , right for look around).

Did i something wrong?

I just edit build.prop and flash the zip. I DID NOT installed the touchpad activator. Should i?
[Xperia Play Android Development] olokos:
Gta VC is not using touchpads at all. It's using triggers to look left right when in vehicle, but to change radio u have to swype left or right on the radio station name using touchscreen (not touchpads!) in order to choose another radio station.