Xperia™ PLAY touch pad tutorial now available

Hi, I have a question.
I’ve already had a Android SDK code, but I need to implement the touchpad. You says I need to use NDK to do touchpad, but I still want to keep SDK code. So what’s the better way to do this?
I’m thinking some ways:
1. Use NativeActivity, but then my own Activity won’t work and I don’t know how to call a java’s view from NDK code.
2. Keep the own SDK code and call NDK method from SDK code. But it seems the inputqueue can only get when I implement NativeActivity? (I don’t know about the JNI code…)

So can you give me some suggestion how to do this?
Thanks.

1  0

@shirley: Yes, you’re correct. You need to use a NativeActivity instead of an Activity. It’s best to use the NativeActivity with the native-app-glue helper library, as described in the tutorial. This avoids any threading issues related to using the nativeActivity class. Note that you can’t call down to the native code with JNI. You need to use the Native activity and everything else that comes with it on the native (C/C++) side.

As far as how to use the NDK code with Java, see the TouchpadNAJava code example that is packaged with the Tutorial. There are three code examples packaged with the Tutorial:

TouchpadNAGlue: Uses a NativeActivity and the native-app-glue helper library.
TouchpadNAJava: Uses a NativeActivity and a Java class.
TouchpadNA. Uses a NativeActivity (no helper library).

0  1

Hi,
thanks for your answer, but I still have trouble making it work.
When I create a view and a Thread in Java class, the program just run NDK’s thread instead of the Java’s thread I created.
So how should I make a multi-view, one to run Java’s thread and show grphics and the other to run NDK’s thread to get control pad response?
Thanks again.

0  0

@Shirley: The best advice I think I can give you is to examine the code in the TouchpadNAJava example.You can find the link to the samples download in the More Information section at the end of this article.

0  1

hello SE Developers. Why Dont you make a computer program that convert ps1 games that we have on disks & images instead of re-programing the whole ps1 game that you own in this way users can convert their own games into xperia play & they will be satisfied for a period of time, & your mobile phone will be in the market for a will before it die like other SE phones did, this would be a win-win situation for both USERS & YOU. OR at least you can release an open project for the same purpose & Third Party DEVs will do the job. Or your will phone will be hacked by hackers for the same purpose. You Know we all love the old PS1 games but the problem is no body will buy a game that he already have,why would i pay 3-6$ for game that i have & can play on my PSP/Ps3/&PC for free???!!!
So Please Please Take My advise & Make that Conversion Program its much better for all of US.

WITH THANKS: YOUR faithful USER

0  0

@Sponmagnet. We appreciate your suggestions. However, this is really a request you need to direct to Sony Computer Entertainment, which is responsible for PS1 games, not Sony Ericsson. Sony Computer Entertainment and Sony Ericsson are two different companies.

0  0

Hello, I have a question about the touchpads.

Why is it implemented in such a clunky and awkward way? You are making it extremely difficult to add to existing apps, especially for indie developers like me who cannot afford to purchase an Xperia Play just to check their NDK code works.

Here is a suggestion as to how you should have implemented it.

If you touch the pad, it generates a touch event (same as if a finger was touching the screen). The touch position would be a position on the screen, circular, as big as the screen. Eg. if you touched ’9 o’ clock’ position on the touchpad, a touch would be generated a x=0, y=240 (landscape mode) touch the centre of the touchpad and you’ll get a touch event at 480,240. Likewise touch the second pad and you get 2 touch events. The second touch pad can generate events x = -840 to -0 or something like that, to differentiate the two touch pads.

That way it would be trivial for existing apps to incorporate your touchpad without all this NDK nonsense. Apps would work in the SDK as it was intended. Basically you did this already for the buttons, so you started out like it but didn’t finish the job.

This is a massive fail for you and if you’d thought about it a bit more you could have implemented the above very easily. I was quite excited about getting my game working on one, but now it is unlikely to happen. It means I have to purchase one and with the level of sales it would take a while to recoup the cost. If you would like to ‘loan’ me an Xperia Play for this purpose that would be okay

5  0

Is it just me or is the tutorial pdf completely borked? Most of the text looks like ASCII jargon and the only legible text is bits and pieces of code.

0  0