Hello all, first post here. I have attempted to research all avenues to figure this out. I have come across a few threads but either no one replies or they dont apply to this specific problem. I have just purchased the Red Samurai v2 from gamestop and can only get one game to work. Is there no way to map the controller?, to get games with native support to see the controller?, I am at a loss here. My Asus Transformer TF300, tablet is not rooted and would prefer to keep it that way. I do understand that you can use the PS3 controller and Xbox controller with a rooted device, just really trying to keep the native system on here.
Love reading the posts on here and would really appreciated some/any help on this. Thank you.
Also I hoped that I posted this in the proper place.
ukantcme87 said:
Hello all, first post here. I have attempted to research all avenues to figure this out. I have come across a few threads but either no one replies or they dont apply to this specific problem. I have just purchased the Red Samurai v2 from gamestop and can only get one game to work. Is there no way to map the controller?, to get games with native support to see the controller?, I am at a loss here. My Asus Transformer TF300, tablet is not rooted and would prefer to keep it that way. I do understand that you can use the PS3 controller and Xbox controller with a rooted device, just really trying to keep the native system on here.
Love reading the posts on here and would really appreciated some/any help on this. Thank you.
Also I hoped that I posted this in the proper place.
Click to expand...
Click to collapse
You can try this to remap them.
BluezIME!
https://code.google.com/p/android-bluez-ime/
If any of the built in drivers (mappings) don't work for you, fully activate Bluez IME (select GS Gamepad in select device, then activate and select the Bluez IME input method) and set it to Data Dump Reader then turn on debug mode and bring up adb shell from a connected computers cmd prompt.
Enter the following:
Code:
logcat DataDumpReader:V *:S -v long > /sdcard/bluetoothdatadump.txt
Press every button on the Red Samurai and roll the analogs then hit control-C. Grab the text file from your sdcard and create an issue on the bluez IME with the dump and which keys are which (if you want) and support will probably be added the next dev build.
https://code.google.com/p/android-bluez-ime/issues/list
This way, everybody who uses BluezIME will have support with this controller within a matter of time. I already did a dump for this controller on an SGS2, but it looks like I got a bad controller.
Edit: GameKeyboard apparently works with the Red Samurai v2, but it isn't ideal... allows you to map buttons to screen press/touches. I haven't personally tried it as it costs money.
https://market.android.com/details?id=com.locnet.gamekeyboard
Related
Mupen64plus-AE
Hi I just wanted to give some attention to the new open source
n64 emulator for android Mupen64plus-AE which was developed by Paul Lamb.
Its currently in its beta testing phase and it would be awesome if other developers wanted to join in and contribute to the project.
Android market link:
https://market.android.com/developer?pub=Paul+Lamb
Heres a link to the latest build + source code:
http://www.paulscode.com/forum/index.php?board=11.0
[This is currently the only emulator for android with xperia touch pad support]
Here is an overview of the emulator:
Here is a comparison video of banjo-tooie running on n64oid and mupen64plus-ae:
Here is an extra video I made of the xperia play touch pads working with the emulator:
Common questions
The GUI is now finished so most of this information is now irrelevant​
How do I map the gamepad buttons?
First, install and run the "SDL Scancode Finder" linked below. Press the keys you want to map, and write down the Scancodes that are displayed. Then after running Mupen64Plus AE at least once, close the app and edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. For the analog stick, use the scancodes for the left and right buttons for "X Axis", and the scancodes for the up and down buttons for "Y Axis". Finally, save the file and restart the emulator.
SDL Scancode Finder:http://www.paulscode.com/source/AndroidSDLScancodeFinder/ScancodeFinder-debug.apk
Alternatively you use my control config and just paste is over the file. Just replace [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini with the custom version of the InputAutoCfg.ini
Heres my config: http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini (right click and save as)
How do I change games?
Delete or rename the file [sdcard]/app-data/paulscode.android.mupen64plus/roms/mario.n64. Place the ROM you wish to play into that directory, and call it "mario.n64" (it doesn't matter what format the ROM is in, just call it "mario.n64", and the emulator will load it instead of Mario64).
How do I remove the touch control overlay?
Go to [sdcard]/app-data/paulscode.android.mupen64plus/skins and delete everything in there except the folder called touchpads, the touch pads folder it what lets you use the xperia play touch pads.
Click to expand...
Click to collapse
*I take no credit in the creation of this emulator all credit goes to Paul and the people behind the original Mupen64plus source code. Im just a tester nothing more haha*
that'd be cool, but even cooler if N64oid got it
Nhialor said:
that'd be cool, but even cooler if N64oid got it
Click to expand...
Click to collapse
N64oid probably never will though. Adding touch pad support cuts of every android device
that has a firmware lower than 2.3 and thats alot of devices.
With Mupen64plus-ae multiple builds can be made so it doesn't effect other devices.
Thats why I feel so strongly that developers should help support this project,
it means that developers can add whatever they want and can create device specific features.
I would love to see this with touchpad support. Waht do you guess how long will it take?
IE-coRe said:
I would love to see this with touchpad support. Waht do you guess how long will it take?
Click to expand...
Click to collapse
Touch pad support is nearly done, my best guess it will either be finished by tomorrow or in a few days. Also just to clarify I am not the one making this emulator.
This the latest build for non qualcomm devices: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug.apk
This is the latest build for qualcomm devices (like the xperia play: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug-sortProblem.apk
The xperia play version has very bad graphics at the moment but paul is working on fixing that atm.
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Logseman said:
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Click to expand...
Click to collapse
No the full name of the Paul who is making the emulator is Paul Lamb
Rockin'
Sent from my R800x using xda premium
P.s. I can't wait for this to come to fruition. Finally! A viable way to play Duke Nukem
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Nhialor said:
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Click to expand...
Click to collapse
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
bubblegumballon said:
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
Click to expand...
Click to collapse
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Nhialor said:
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Click to expand...
Click to collapse
No problem and Im sure ive seen Shtruck say something along those lines on the fpsece forums
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
hairdewx said:
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
Click to expand...
Click to collapse
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
bubblegumballon said:
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
Click to expand...
Click to collapse
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
hairdewx said:
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
Click to expand...
Click to collapse
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
bubblegumballon said:
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
Click to expand...
Click to collapse
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
hairdewx said:
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
Click to expand...
Click to collapse
The project is open source so anybody (with the right knowledge) could just go and add touch pad support if they wanted.
Also I would like to point out touch screen controls have now been added but they are still not finished, there are still a few more things to be added like a moving analog stick and lots of optimisations so dont expect it to be perfect just yet.
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
bubblegumballon said:
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
Click to expand...
Click to collapse
did you use the first apk or the "qualcomm" apk?
because Im trying the second apk and its not letting me download the data from paulscode.com...
any help would be appreciated
Alright this is going to be a doozy of a post for my first one on XDA. While playing this game today called Exitium, I got a crazy idea in my head. "What if there was a way to take games with virtual controllers (D-Pad and buttons) and map them to physical keys?" Either on a built-in keyboard like the Droid 4, or the Xperia Play's keys, or even mapping them to a third party device such as a bluetooth keyboard or Wiimote/PS3 controller.
Obviously the easiest solution here is to contact the developer and request hardware button support within the game you are wanting to play. But...
I have looked everywhere and have not found an outside application that attempts to do this. So after a long talk with a friend of mine, we came up with some rough draft ideas of how this could be done. Unfortunately neither of us have a lick of sense when it comes to actual programming and the idea of creating this from the ground up seems impossible at our level.
So what I was wondering, is if there already is an app out there that can take a point on the touchscreen, and assign it to a keypress on a physical device? And if not, are there any developers out there willing to give this a stab (and I'd obviously give as much input as I possibly could), or someone willing to help me try to understand where I'd even begin to make something like this?
I know this probably sounds like a mess but I promise I tried to make it as simple and coherent as I possibly could. Thanks for taking the time to read this.
Hoping!! BEGGING!!!!
I would love to see this - like a more universal version of sixaxis mapper. it could work with keyboards or any game controller or mouse. even really useful for phones that have physical keyboards attached! Hope one of these pops up. I couldn't find any so far ...
I often use keyboard with my N7 and i have thought about this many times, it would be very useful for playing games... I'm sure that many ppl had the same idea.
I don't know about any apps that can do this, but it already exists as a built in feature in a kind of a console tablet hybrid called "archos gamepad", so hopefully some apps like this could soon come to google play...
To all developers: please make it, i would have no problem paying $5 for such an app.
Sent from my Nexus 7 using xda app-developers app
Hello
My archos g9 fall down with result a broken unuasble screen. But that doesnt mean it is useless!
The hdmi output works just fine, so i will use it like a media center with my tv.
I want to update to 4.0.25 so i can use it from my phone with archos remote, but it currently run with blue rom and cant update by it self. Also the hdmi is not working in recovery and i cant see.
Is there any alternative way to update? (adb or something )
thanks in advance
buluba89 said:
Hello
My archos g9 fall down with result a broken unuasble screen. But that doesnt mean it is useless!
The hdmi output works just fine, so i will use it like a media center with my tv.
I want to update to 4.0.25 so i can use it from my phone with archos remote, but it currently run with blue rom and cant update by it self. Also the hdmi is not working in recovery and i cant see.
Is there any alternative way to update? (adb or something )
thanks in advance
Click to expand...
Click to collapse
Hi There,
Grab the surdu rooted update from here
You can flash the sde zImage and initramfs.cpio. using an archos tool called kd_flasher, just push the zImage and initramfs.cpio.lzo to the device, doesn't really matter where, /data/local/ is as good as any, Then push archos.ext4.update from (Stock_Root_4.0.25) on to your device, then reboot into sde , something like this should sort you out
Code:
adb push zImage /data/local/zImage
adb push initramfs.cpio.lzo /data/local/initramfs.cpio.lzo
adb push archos.ext4.update mnt/storage/
adb shell kd_flasher -i/data/local/initramfs.cpio.lzo -k/data/local/zImage
adb shell reboot_into sde
Hope that help you out
buluba89 said:
I want to update to 4.0.25 so i can use it from my phone with archos remote
Click to expand...
Click to collapse
Man, I've can't believe I didn't clock this app sooner, I only just look at what it does, my touch screen has been fooked for months as well, It's one of the few thing about Archos that has made happy. I was looking in play around with USB/IP adb virtual mouse drivers, Sill will. It's nice to see they finally Got Something right!
Thanks a lot for the help, i ll try this and post how it went in the next days.
Yes after 4.0.24 update it says that you can use your phone as a touchpad that sounds very interesting. Also i saw lots of updates at the video app of archos that is the only one that plays fine through hdmi.
Sent from my Optimus 2X using xda app-developers app
buluba89 said:
Thanks a lot for the help, i ll try this and post how it went in the next days.
Yes after 4.0.24 update it says that you can use your phone as a touchpad that sounds very interesting. Also i saw lots of updates at the video app of archos that is the only one that plays fine through hdmi.
Sent from my Optimus 2X using xda app-developers app
Click to expand...
Click to collapse
Yes, I'm in a quandry now with it, I'm porting CWM and stuff and probably going with a 4.2 from the Omapzoom sources, Archos G9's are based heavily on the Blaze Development Platform.
It's not overly difficult to write my own app to do that although I suck and hate doing UI work and the archos did feel alright to use on the HTC Sensation. I already tore apart the Client APK from my HTC, It's pretty heafty but that isn't what I need anyway. It's just a case of Implementing the protocol on the custom roms. Considering I control both ends of the conversation you just gotta tell.
Piece of Cake Really..... I'll add it to the list
You're rooted currently right? Have you tried changing your system properties the pretend to be a 4.0.24 rom....It probably won't work because I think Archos will is reliant on the input classes of the android framework. which is wrapped in the a script in /system/bin/input. On ICS the commands available are as follows
usage:
input text <string> : this will "type" a string to the focused android ui window
input keyevent <event_code> : an number between 0-255 which represent either keyboard keys, both soft and hard buttons as well as custom assigned things
I currently make heavy use this of it with my custom adb. Which is how I mae inly work with it . Although I given them some nice wrappers because I'm a lazy bastard. Anyways input in jellybean add a couple of extra
usage:
input text <string>
input keyevent <key code number or name>
input tap <x> <y>
input swipe <x1> <y1> <x2> <y2>
I played with tap and swipe earlier, on a Galaxy Tab I put 4.1.2 on. they work pretty nicely. Quick Left and Right Swipe can be done with just add a sign to the number, The only thing missing then is an easy way to do long presses. It possible the send them using /dev/input codes, I've not got round to playing with that, I've not had an overwhelm need to do it as I always have a otg cable with a mouse to hand.
Ah F**k it, I'll get wireshark on it later and backport whatever the after.
Apologises for the technical mind dump, I just got myself started. at least you know there more than what archos provide re remote controlling.
I didn't quite understand that big post of yours but your solution worked perfectly and now my g9 is update to 4.0.25
Archos remote touchpad is a little bit difficult to use but it's functional. Now i move on to solve the next 2 problems ,network speed for streaming movies from my data server and force screen to be off because the screen is white all the time and it is a little bit irritating
But these are not device specific so i believe mr Google will help me
Thank you very much again!!!
buluba89 said:
I didn't quite understand that big post of yours but your solution worked perfectly and now my g9 is update to 4.0.25
Archos remote touchpad is a little bit difficult to use but it's functional. Now i move on to solve the next 2 problems ,network speed for streaming movies from my data server and force screen to be off because the screen is white all the time and it is a little bit irritating
But these are not device specific so i believe mr Google will help me
Thank you very much again!!!
Click to expand...
Click to collapse
Haha, Welcome to the inside of my mind....I've been affectted by these robots.
To turn off the display on the device do some more command line trickery
echo 0 > /sys/devices/platform/omapdss/display0/enabled
or
echo 0 > /sys/class/leds/lcd-backlight/brightness
Both achieve the same result, It's been a while since I worried about network speeds but generally I try an be wired in the route either directly or through home plugs, I know some of the usb etherports are cheap and work with out much hassle of the G9 On wireless I try to be on fairly channel away from other people ( not always possible ) and Networking said to try to use even channels, Some to do with Electrical and thing I don't fully care to understand yet
Ok, I purchased the Nyko Playpad assuming because of the packaging that it would simply sync and then i would key map and i would be playing Castlevania:COTM right now after years of not owning an actual GameBoy. I tried the suggested/"included free software" available from the play store, I got the controller synced in APP mode, which only works for initial boot and in the app its self. It does not work as a mouse or HID input. One of my emulators has iCade support; so I set the controller to iCade, synced and then went to key map. Failure. I've gotten as far as getting the controller to recognize 2-4 commands from the controller at a time; however, they inputs were, I: straight into the google seach app thinger II: the back key III: 5/* IV: 8. so no really anything useful for playing any sort of game or even browsing in mouse mode.
I began re-reading all of the instructions, reviews and watching Nyko's how-to stuff on YouTube. Over the course of 5 hard hours of me being neck deep in failure and coding I don't fuly understand, I found my problem. Sense lacks proper l2cap support, apparently...
I tried Bluez IME, and its respective hid enabling apk. That did not work for me either.
So, right now, I'm looking at unlocking and possibly rooting.. I guess, I'm not ready to admit defeat and return the controller right yet. Will Cyanogen/any other stable homebrew unlock this for me without msoftware, I goe losing camera, BT, etc... functions? Will a simple unlock and a flash of the BT fix the issue or is it too closely tied to the sense input system? I'm not too familiar with all the coding, but I have been an Ubuntu user for about a decade, I know it's like the baby step, but it's quick and has me at least a little familiar with the Android's linux based system.
Stats-
model number: HTC6435LVW
hardware version: 003
Android version: 4.1.1 w/ Sense 4+
software number: 2.06.605.1 710RD
Any other stats needed can be gladly provided.
Help, guidance and ibuprofen are all greatly appreciated.
Unfortunately, unless someone has tried that specific controller with the software that you want to run, you'll just never know for sure.
Thanks to your post though, I just tried a Zagg Flexx keyboard which has never worked with Sense (4.1, I haven't tried newer Senses) and didn't work with CM 10.1. It is working just fine for me on CM 10.2.
Well snap, you think if i set up CM 10.2 it would be kosher and i could reinstall my emulators and game roms, proceed to link via BT and actually be able to use the thing as an input device?
I was going to just jump the gun and do it, but I'm having issues even compiling adb and the like... I'm on Ubuntu 12.10, afaik. The htc guide offers windows instructions, but only files for linux/mac use. I got stuck on a ".bin" step... the first one actually..
Could I get a step-by-step and a complete list of what I actually need? I've been all over and through 80+ page threads and watched an hours worth of youtube guides, many of which are thanks to this forum, and thank you, but I'm lost...
Guru guidance is much appreciated.
As I said, no way to know for sure unless someone has actually tried it. Every device potentially acts differently.
It should be easy to install (not compile) adb for linux. You need to install the Android SDK from Google and make sure you select the right component to get adb. Searching for
install adb linux
should give you easy instructions.
I just bought the X96H PRO TV Box a all winner H603 chipset 32gb rom 4gb ram quad core, running android pie 9.0. It's native root without read/write access I never knew that root could exist no read/write access in the first place? Any way, I need to find out how to get read and write tried the permission changes in folders and files namely the Genric.kl file and subsequent folders.The issue is I cannot press enter on a keyboard not the built in virtual keyboard or a USB keyboard wired or wireless in both chrome and or Google play store apps nor brave browser either. Hence this is one big paragraph lol as can't hit enter key and go to a new paragraph how ridiculously idiotic a flaw to add to a firmware surely the decade and then some years should have given the dev an idea to include enter as key option 28 in Genric.kl but no he put D_PAD ENTER instead so I am stuck now no full root to modify it, I have no experience modding stuff I struggle to learn. However can reflash devices extremely well and hard mod but this has got me stumped now, I don't want to void the warranty it's not a day old I don't want to return it either, I tried USB keyboard helper tried remapping it to 28 enter and fails well works in apps bar play store and chrome/brave browsers. Can someone maybe help me out please get the system read and write everything, there is another interesting option to input hdmi on this device again it comes with a flaw it's controlled via the remote only and designated as a source button with no visible os around it sort of dictating it could be simply for passing hdmi sources through it and not to record with which sort of seems gimmicky and a clever sort of you buy it on the assumption it records you bought it for good thing I think it is, if anyone could also shed light how I might records this please let me know.