yashsingh1/xdaforums huggingface dataset:
[Android General] Witalka 15:
dude your awesome :D

works like a charm ..

Client 0: UP - 19

Client 0: Down - 19

...

edit:

this works to ..

they show me the mac .. :D ..
[Android General] treUse:
Works flawlessly on the NS. Now if we could get the app so I could try it out for real :)
[Android General] sir_earl:
Which ROM are you running?

I'll have a go at getting the full version up onto the market this weekend, but I'm quite busy with real life stuff, so no promises.
[Android General] treUse:
I'm currently running CM7 N147. If you want I could give the full app a run to test things. Trying it out on different ROMs. Unless you already got the testing covered of course.

Anyway though, thanks for creating this and I'll be buying this without hesitation as soon as you're ready to release. Which I do hope will be soon, I'm dying to test this out :)

Oh, and screw real life, you just gave the wolves an appertiser and they're this close to taking your hand with it unless you give them something else :P
[Android General] presslab:
I tried the latest version, again on my Asus Transformer running Prime 1.6r2. It worked fine, and I was even able to delete hciconfig and it still worked.

With this new version, will it be possible to use other bluetooth devices at the same time?
[Android General] sir_earl:
Not as it stands, because the high level bluetooth system must be turned off to stop it from intercepting the connection to the controller. It may be possible to turn the high level bluetooth system back on once the device has connected. I will also add this to my 'to do' list.
[Android General] iMaxCB:
Tried it on my SGS2 running CM7, works fine, too
[Android General] presslab:
Just tested it with my Fascinate Galaxy S phone running CM7 (fascinatemtd) and it works fine.
[Android General] sir_earl:
Hi guys,

Just letting you know that both the full version and compatibility checker are now live on the Android Market! Check the first post for links.

I decided to go with slightly more than the $1 USD I originally suggested, due to an unfavourable exchange rate.

The latest version of the SixaxisPairTool can be found on the website, along with more detailed instructions and a FAQ that I will be adding to as questions begin flooding in ;)

Feel free to contact me via the website if you have any enquires or questions.

Also, if anyone has any constructive feedback about the instructions and suggestions about how to make it clearer and easier to use, I'd love to hear them.

Thanks to all those that took the time to do a little testing for me.
[Android General] treUse:
Can't get this to work together with SNesoid. I can bind the keys without problem, but they aren't doing anything while in game...

Any ideas?
[Android General] flex59:
In snesdroid go to settings other settings, use input method.

Make sure that it is selected in your input settings.
[Android General] flex59:
Got it... Had to adjust some settings, butt nothing too taxing ;-)

Works very well.

Many thanks.

p.s this it's the first app I have paid for. Well worth it
[Android General] treUse:
Ah, right. Thanks, can't believe I missed that...
[Android General] presslab:
I downloaded the app, looks pretty good so far. Is there a chance that full analog support could be added in the future? I'm not sure if this is a limitation of Android. What about the Dualshock? Does Android have an API for this or whatever?
[Android General] sir_earl:
It would be completely possible to expose the full functionality of the controllers to developers (including rumble on the dualshock), however it would still requires games to explicitly support it. Unfortunately, as long as the app requires root and is limited to certain devices, I doubt it would ever get that support.

I have also played with the idea of making a touch screen emulation type of input method, in which anyone can create and share profiles for different games. This would work by allowing areas on the screen to be mapped to different buttons, and could support the analog sticks by defining an area in which hold and slide touches occur. There are many games this would suit.
[Android General] presslab:
Touch screen emulation would be very interesting. Another option is the accelerometer emulation / redirection. It would be neat if the accelerometers inside the sixaxis could override the device's accelerometers. And/or the sticks could emulate the accelerometer function as well.
[Android General] sir_earl:
Yeah - especially cool to be able to plug the phone in to HDMI and still use the accelerometer from the couch! But I'm not sure if it's possible to simulate accelerometer events...
[Android General] marckaraujo:
Man,

Could you introduce on the input mapping key to simulate keyboard keys?
[Android General] imneveral0ne:
would be nice to try before i buy. i downloaded the testing app and it turned on my bluetooth and said it was connected. problem is my ps3 isnt even in this room nor is any part of it on.
[Android General] sir_earl:
Hardware key mappings will come soon in the next major update.

The analog buttons have a green ring that you can grab and resize once selected.
[Android General] sir_earl:
The the touch profile has actually stopped working entirely? Do any button presses show up if you run 'Touch Test' from the market?
[Android General] h_zee13:
I tried both...and nothing works

I can use it on my PS3 with the usb cable and I can use it on the phone with the usb cable, but the moment I remove the cable and try to connect it wirelessly it doesn't work on both the phone or the PS3
[Android General] sir_earl:
Can you please try connecting a controller and selecting a touch profile, then running the following commands from a terminal, waiting a couple of seconds, then pressing some buttons on the controller and reporting the output.

su

getevent
[Android General] sir_earl:
When the controller is disconnected and you press the PS button, do the lights start blinking? If not, maybe try charging the controller over night. Could be a failing battery...
[Android General] outlawstarc:
Hey I also have a xoom and have experienced my touch profile no longer registering on touch test. Just chiming in.

---------- Post added at 09:27 PM ---------- Previous post was at 09:05 PM ----------

Hey earl I gave this a try and had a lot of code scrolling up the screen, too fast for me to record any of it according to my button presses on sixaxis (not sure how to screenshoot with my xoom) But a lot of dev/input/output1 00000002ae (however this last section changed by the millisecond) with the occasional output2. Sorry if this doesnt help much, educate me a little and I'll see what I can do after "girl with the dragon tattoo"
[Android General] ranova:
heres a screenshot. as you can see its just registering at the bottom left. No matter which button I press (that is assigned in the touch emulation) its that same spot.
[Android General] Larry94:
Pictures still show up in portrait after the last update :(
[Android General] Us3rName:
You are able to crop and rotate them by selecting "Edit Background."
[Android General] Larry94:
Hahaha sorry about that. I hadn't updated yet and a buddy said it wasn't working for him.
[Android General] gabster21:
I can confirm the exact same issue for GNex, in GTA3 my guy just keeps running in circles no matter what mapped button I press. All presses are registering at the bottom left.
[Android General] WarrenOfSnares:
I'm sort of new to this so bear with me please, I'm running a rooted Samsung Galaxy Tab 8.9, when I run the program and hit start I get the following repeated message:

Attempting connection type 1...

Driver starting...

Permission denied

I apologize if this was answered before, I'm new to android in general but if someone could point me in the right direction to get the Sixaxis PS3 controller working, it would be greatly appreciated! Also, running version 0.3.5

Thanks!
[Android General] dirtyyy:
after testing my xoom on touch test. i can confirm no buttons are working on my ps3 controller. only the select button which exits/minimizes the app works.

i have tried this on my own touch profiles and with touch profiles turned off.

however the pads buttons are working, if i keep the touch profile off i can navigate the xoom etc with the pad.
[Android General] sir_earl:
I can reproduce this behaviour by placing a button in the bottom left corner of the screen, so this issue is because all button presses have been scaled to the coordinate (0, 0). Apparently other devices aren't using the same mechanism for passing the touch screen calibration settings through to Android.

I'm investigating why this is happening now!
[Android General] gabster21:
Awesome, thanks! Let me know if there are any tests I can run to help.
[Android General] sir_earl:
Can you check your phone for the existence of a file called 'pointercal'. It may be in /etc, but you should be able to do something like 'find | grep pointercal' to search for it.

It's a pain, because it doesn't look like there is a standard method that the touch screen is calibrated, so I'm thinking I might have to run an automated calibration step to do this.

For now, I'll roll the calibration changes back, as I've broken the touch profiles for quite a few devices.

Update: Ok, the calibration changes have been rolled back, so the Galaxy Nexus should work better than before - it still might not be aligned, but the button presses should show up at coordinates other than (0, 0).
[Android General] Artfuldodger89:
Sorry no go.

Still doesnt work for me.

If there is anything i can do to help let me know.

i'm desperate to get this working.
[Android General] ellokomen:
Same situation here, the update .7 did not fix the problem of the .6, I have a backup of the version .5 and I need to roll back to use the touch profiles again
[Android General] Us3rName:
Check your Superuser app to make sure that the Sixaxis Controller app is not blocked.
[Android General] usmcc2000:
The Touch Profile does not work with the Galaxy S II Epic 4g Touch. The app works great for the regular inputs, but does not register the analog sticks or regular button presses with the touch profile.

I did receive input in the terminal emulator when running the getevent command, but cannot get it to work in my games.

I'm using N64oid.
[Android General] letifercito:
the same issue happens on my toshiba thrive, i tired the touch test app with some touch profiles i've created, but no response for my ps3 controller, but if i use the "getevent" command on terminal emulator, y get response from all the buttons.

maybe some honeycomb issue?
[Android General] WarrenOfSnares:
I found out that I rooted my tab improperly, which is why the permissions were denied, which is absolutely puzzling. I followed the entire step by step instructions by putting root.zip in the /sdcard directly and running it in the alternate startup mode where you hold the power and volume button. Completed it entirely and rebooted, used Root Checker which informed me that I didn't have proper root access. Completely stumped, now haha. More than likely this will work once I get properly rooted. Oi, what a headache haha
[Android General] dirtyyy:
yeah. it seems so.
[Android General] sir_earl:
Can you perhaps send me a dump of the output from getevent, in which you first touch the screen with you fingers, then use the touch profile and the controller?
[Android General] WarrenOfSnares:
Finally got this to work. Used the 10.1 method and files to get it to work on my 8.9. D'oh! Now I'm having some difficulty properly mapping the input in Sixaxis for use with SNESoid and other emulators. Is there a tutorial somewhere that I can scope out to do this with ease? Because I'm not sure what buttons "1" "2" "3" etc. are in relation to the controller itself and simply pressing them in Sixaxis doesn't incite ant response unless I choose it manually from a list.
[Android General] letifercito:
how can i do that?
[Android General] sir_earl:
Open a terminal, then type the following:

su

getevent > /data/output.txt

Then wait a couple of seconds before touching the screen and pressing buttons on the controller (make sure the screen is on while doing this).

Next hit Ctrl-C and send me the file '/data/output.txt'.
[Android General] ezigzag:
i been trying to play onlive using Xperia Play Buttons but onlive wont register me pressing anything. anyone get six axis to work with onlive? besides dirt or lego batman?
[Android General] sir_earl:
I've put up yet another version (0.3.8) in the hopes of reverting to the 0.3.5 versions behaviour.

I'm working on the calibration problem now and might post a debug version for some testing soon.
[Android General] ranova:
Hi Earl,

0.3.7 works perfectly with the Galaxy Nexus now (havent tried .8 yet), thanks for the dev support, I left a 5 star review.

For a future request, can you add a input profile for Onlive? I dont think their official wireless controller is out yet, but people say that the PS3 controller does not fully work yet.
[Android General] gabster21:
Damn, you beat me to it! Yes 0.3.7 works great with the Galaxy Nexus. Just tried a basic mapping for GTA3 (run, jump, sprint, accelerate, brake, turn..) and so far it works perfectly. Those who want to get an idea for the mapping check out the screenshot.

Hope 0.3.8 doesn't break the touch functionality for the SGN! :D
[Android General] WarrenOfSnares:
What do each of keys in "1st controller mappings" correspond to? For example, does "8" "star" or "pound" equal the square button? I'm having some difficulty with this. I realize that these seemingly differ from emulator to emulator too, how do I know which mapping corresponds to the emulator's button?
[Android General] Us3rName:
In the sixaxis app you can assign the input mappings to whatever you want. The default assignments will work fine if you aren't planning on using the analog sticks. Then in your emulator of choice (I will use Nesoid here as an example) go to Other settings and enable "Use input method" (some emulators don't have the option and are enabled by default). Then go back to Input settings > Key mappings, touch the button you want to map and press your desired button on the controller.
[Android General] teknoplayer:
It would so amazing to have the Rumble working with DualShock 3 controllers :P.
[Android General] needtoride:
This did it. Thanks!
[Android General] NeoMagus:
Ok guys I need some help. The app works fine with my droid and bionic, however I cant get it to work with my Galaxy Nexus for anything. The program has root and I have the address to it linked with the computer so when I push the ps button it says client connected in the sixaxis app, but it doesnt work in any emulators, and I have it mapped to the same controls so dont know what im doing wrong.. tried with ime on and off nothing..if anybody could help thatd ne great cause if you guys say its working I cant figure it out.

**figured it out thanks to usernames post, it was the setting other settings use input method i didnt have checked works great now
[Android General] Elloco305:
How can I make it work for need for speed shift. Or other games that aren't ran on emulators??
[Android General] Us3rName:
For games that support hardware controls go to Sixaxis settings and enable "Bypass IME". The input mappings will need to match those used by the specific application. The key mappings for movement are typically the d-pad directions (DPAD_UP, DPAD_RIGHT, etc.) For the rest of the buttons you will either need to experiment or search for the correct mappings online. For games that utilize on-screen controls you will need to configure a touch profile in the Sixaxis app.
[Android General] Elloco305:
Wow. I've been following this thread since it had 2 pages aand I still don't understand the whole touch profile or the key mappings. >…< ill just try and experiment thanks though
[Android General] Shift Sunny:
Any time frame on the new update since 3.8 doesnt let you touch map on Galaxy S2?

Or is there a way to revert back to .7?
[Android General] Juandachu:
Touch emulation has stopped working on my stock 2.3.5 Galaxy S2 in any version after 0.3.5 so I'm just sticking to it until it works again.
[Android General] letifercito:
done!, check your gmail account :)
[Android General] bigboss59400:
Is it working with a dualshock ?
[Android General] Us3rName:
This app is compatible with the Sixaxis and DualShock 3.
[Android General] flex59:
sigh... restarts my cm7 nexus s pretty much every other time i try to run it.

GTA3=

touch is not working ... tried loading others maps... tried making my own maps... the best i can do is no touch. which gives me movement with both sticks and d-pad.

edit

tried touch test and nothing shows so guessing there is a problem with the app itself. going to re-install and try again...
[Android General] Jackzoor:
Hi there ! Im having a real hard time to get this working with my t989 !

when I run my Sixaxis Controller it says

Could not start driver. Check that your device is rooted and has given permission to run Disconnected.

Im on 2.3.5 perfect stock

i though i heard that the new app work with stock now ? can anyone help me out plz ??? Thank you !!

t-mobile sgs2 t989
[Android General] sir_earl:
The app requires the device to be rooted in order to function.
[Android General] sir_earl:
Wish I'd found this earlier - can some of you run the following command and send me the output. I'd like this for as many devices as possible, Galaxy Nexus included. I only need the first block of text that appears, so it's fine to kill the command after a couple of seconds.

su

getevent -v 36

If you could also include what device you ran the command on, that would be helpful.
[Android General] letifercito:
how can i kill the command?
[Android General] sir_earl:
Just press Ctrl-C
[Android General] flex59:
Nexus s cm7

hope that works / is of any help
[Android General] ellokomen:
#getevent -v 36 on Galaxy Tab 8.9

root@android:/ # getevent -v 36

name: "magnetometer_sensor"

events:

SYN (0000): 0000 0002

REL (0002): 0003 0004 0005

name: "light_sensor"

events:

SYN (0000): 0000 0003

ABS (0003): 0028 value 0, min 0, max 65528, fuzz 0 flat 0

name: "sec_touchscreen"

events:

SYN (0000): 0000 0001 0003

KEY (0001): 014a

ABS (0003): 0030 value 0, min 0, max 255, fuzz 0 flat 0

0032 value 0, min 0, max 255, fuzz 0 flat 0

0035 value 0, min 0, max 1279, fuzz 0 flat 0

0036 value 0, min 0, max 799, fuzz 0 flat 0

0039 value 0, min 0, max 9, fuzz 0 flat 0

name: "sec_keyboard"

events:

SYN (0000): 0000 0001 0011

KEY (0001): 0002 0003 0004 0005 0006 0007 0008 0009

000a 000b 000c 000d 000e 000f 0010 0011

0012 0013 0014 0015 0016 0017 0018 0019

001a 001b 001c 001d 001e 001f 0020 0021

0022 0023 0024 0025 0026 0027 0028 0029

002a 002b 002c 002d 002e 002f 0030 0031

0032 0033 0034 0035 0036 0039 003a 003d

0045 0047 0048 0049 004a 004b 004c 004d

004e 004f 0050 0051 0053 0060 0062 0064

0066 0067 0069 006a 006c 006f 0071 0072

0073 007a 007b 008b 0096 0098 009e 00a3

00a5 00a8 00b9 00bb 00be 00bf 00c0 00cf

00d0 00d7 00d9 00e0 00e1 0167 020b

LED (0011): 0001

name: "sec_key"

events:

SYN (0000): 0000 0001

KEY (0001): 0072 0073

name: "sec_power_key"

events:

SYN (0000): 0000 0001

KEY (0001): 0074 008f

/dev/input/event2: 0003 0039 00000000 <-- I touched the screen

/dev/input/event2: 0003 0035 00000297

/dev/input/event2: 0003 0036 000001bc

/dev/input/event2: 0003 0030 00000026

/dev/input/event2: 0003 0032 00000026

/dev/input/event2: 0000 0002 00000000

/dev/input/event2: 0000 0000 00000000

/dev/input/event2: 0003 0039 00000000

/dev/input/event2: 0003 0035 00000297

/dev/input/event2: 0003 0036 000001bc

/dev/input/event2: 0003 0030 00000000

/dev/input/event2: 0003 0032 00000000

/dev/input/event2: 0000 0002 00000000

/dev/input/event2: 0000 0000 00000000
[Android General] letifercito:
Toshiba Thrive with Honeycomb 3.2.1

export PATH=/data/local/bin:$PATH

sh-4.1$ export PATH=/data/local/bin:$PATH

sh-4.1$ su

sh-4.1# getevent -v 36

name: "prox_tegra"

events:

SYN (0000): 0000 0003

ABS (0003): 0019 value 0, min 0, max 1000, fuzz 0 flat 0

name: "light_tegra"

events:

SYN (0000): 0000 0003

ABS (0003): 0028 value 0, min 0, max 120000, fuzz 0 flat 0

name: "thom_tegra"

events:

SYN (0000): 0000 0003

ABS (0003): 0006 value 0, min 0, max 150000, fuzz 0 flat 0

name: "tegra Wired Accessory Jack"

events:

SYN (0000): 0000 0005

SW (0005): 0002 0004

name: "gpio-switches"

events:

SYN (0000): 0000 0005

SW (0005): 000c

name: "gpio-keys"

events:

SYN (0000): 0000 0001

KEY (0001): 0066 0072 0073 0074

name: "egalax_i2c"

events:

SYN (0000): 0000 0003

ABS (0003): 0035 value 0, min 0, max 32767, fuzz 0 flat 0

0036 value 0, min 0, max 32767, fuzz 0 flat 0

0039 value 0, min 0, max 4, fuzz 0 flat 0

003a value 0, min 0, max 1, fuzz 0 flat 0

Hope it helps.
[Android General] sir_earl:
Thanks guys, it's looking promising. I'd still like reports on a few more devices, especially the Galaxy Nexus.
[Android General] sir_earl:
Perfect. Looks like I will be able to get this working without the calibration step after all! Should have an update very soon!

Could you explain what you mean by 'work intermittently'?
[Android General] renaissance.man:
Thanks for the confirmation.

I had a touch profile map working really well in GTA III yesterday morning after enabling "relative touch" for the analog controller. When I tried to play the same game with the same controller and map later in the afternoon, several of the buttons did not line up and the analog controls were not working correctly.

Obviously, this was confusing since it was fine as previously configured.

I tried repairing the controller, a different OEM sixaxis controller, rebooting the phone and the controller, creating a new profile map using a background screenshot from the game that was properly sized, and reinstalling the sixaxis controller app to no avail.

It is after this frustration that I noticed that other users were having issues with the latest version and the GNex. Therefore I settled on the conclusion that it was working intermittently.

Let me know if you need any further clarification.
[Android General] letifercito:
i wish your next update will work on my tablet, thanks for all your effort btw :)
[Android General] sir_earl:
Hmmm, I'll do the update and then revisit the problem if it persists, as things may have changed by then.
[Android General] renaissance.man:
Great. Sounds like a plan. Looking forward towards testing the changes and reporting back.

Thanks for the great communication.
[Android General] Shift Sunny:
Cant wait for the update sir_earl! Thanks for working so hard at getting this right!
[Android General] sir_earl:
Ok great. I'm 90% confident that this update should work, so I'm going to be very embarrassed if it doesn't! I was actually quite close with my approach, but just a couple of details were off and I was coding blind. Thanks to the info that many of you provided, I'm hopeful that I've solved the issues, so thanks to everyone that contributed! Anyway, I've uploaded the update, so it should come through soon.
[Android General] renaissance.man:
EDIT: Was able to pull down 0.3.9 from market today.

Confirmed as working on Samsung Galaxy Nexus :)

FWIW: I do not know if anyone else has reported this, however, I am seeing some nonresponsiveness when the left analog stick is used in conjunction with another button. Neither one will send input until I release of the triggers, then reapply one trigger at a time. Also not consistent.

Not a huge problem but tricky to plays when this happens. Seems like a glitch.
[Android General] ellokomen:
wohoo everything is working now! I just updated and version 0.3.9 is back to business :-) touch profiles are working again
[Android General] dirtyyy:
can confirm working on xoom with touch profile and gta3.

movement stick can get stuck sometimes. so have to let go on stick and start again.

anyone got gta working on ps3 pad working flawlessly incl all buttons? is it/will it be possible?

nice 1 erl!
[Android General] @rbiter:
^^^. I read all that. I swear. :D
[Android General] gabster21:
lol, on a regular browser the code tag works so it doesn't take up so much space