Whats the default directory for your configs? I cant seem to find it anywahere in the root directory.
Sorry bout the trouble mate. Cant seem to find the cause of the problem too. I tried another controller but that didnt fixed the problem. Someone with another phone might be able to confirm if iam isolated case or not.
It's in /data/data/MarcusD.IRDa/files/
Also, can you please record me on a video slowly how you're setting up your axes? I'll try to do what you're doing and check with my setup to see what could've gone wrong.
Also, in a few days I'll make a debug Activity where you'll be able to test the axes, and I'll ask you to test it.
Well... you can hook up an USB or Bluetooth controller to your phone and use that to play with your 3DS.
Obviously the limitations of InputRedirection also apply here, and you need to make sure the 3DS passes the conntest so it can connect to the same network as the phone is on.
But other than that yes.
Right here my mate.
I also included the file itself in the attachments compressed in archive.
About the remapping, yes i could provide you a video later tonight. But im quite sure i did the right thing because i made the circlePad analogs work properly.
.------------------------
You could connect a Controller to your 3ds.
But 3ds doesnt have bluetooth functionality or capabilities/drivers to read a controller hooked up so they made inputRedirection.
You connect your controller to your PC, the PC interprets the "inputs" and "redirects" it to the 3ds.
Instead of a PC, OP created an android app so we could use our phones instead.
Last edited by chirogan,
im quite sure i did the right thing because i made the circlePad analogs work properly.
Yup, you did. I checked the axis cal, and it's a perfect mirror and all axes are matching logically. Good to hear you magically got it working
Things can magically just start working (again), even if it defies all laws of physics and existance.Oh no mate.. i meant the right analog sticks are working correct. But i still got the c-stick problems.. xDYup, you did. I checked the axis cal, and it's a perfect mirror and all axes are matching logically. Good to hear you magically got it working
I think the c stick issues are caused by an overflow or something, as I can't get issues with partial presses.
First i tried and d'nt worked, but them i remember turn on the controler than it worked, thx!! a question, you plan add more stuff to this app? cuz it would be awesome , a Android 3DS helper Central...
This is quite bothering. I tried to debug the app this morning but i get app crashes before it even starts loading. Ill try another way.
Edit: ill try to debug the app via android studio when i get home. I'll let you know the results later.
Last edited by chirogan,
I don't plan on adding new features, since this is an InputRedirection client, not a 3DS multitool. The code is already impossible to manage, so I'd rather start a new application if the demand is high enough.
I don't know why it'd crash right at the start :c
setContentView is supposed to inflate the view at the moment you call it, not after onCreate, so it makes no sense why it'd crash right at the start...
Hey buddy, how are you? Had some trouble over our internet connection this past week(yeah. Our isp sucks). I totally forgot this.
I tried debugging but no luck. I cant make the debugger to work. Either i cant find a way to debug this or i suck at this. Do you emulate the app or you tried directly on a compatible phone? Im just curious coz you fixed the app in your phone but the problem is persistent with the package..
I tried debugging but no luck. I cant make the debugger to work. Either i cant find a way to debug this or i suck at this. Do you emulate the app or you tried directly on a compatible phone? Im just curious coz you fixed the app in your phone but the problem is persistent with the package..
I have 4 Android devices (only two of which recognize the controller), and those two both work the same way, and work perfectly fine.
Sadly I only have one compatible controller, so can't test others
Also, I can't dev for a while due to my left hand, so the most thing I can do is rebuild the apk where it's set to be debuggable.
I have 4 Android devices (only two of which recognize the controller), and those two both work the same way, and work perfectly fine.
Sadly I only have one compatible controller, so can't test others
Also, I can't dev for a while due to my left hand, so the most thing I can do is rebuild the apk where it's set to be debuggable.
Its not some serious injury or something isnt it? Goodluck on your recovery.
Im just too outdated to explore new stuff and doing so requires a lot of work for me. Now with my current work, it makes it even impossible.
Anyway, the app is functional. The games on the 3ds rarely use the c stick but it just boggles my mind thinking i can't use it to the fullest potential. Also, the games i want to use these on requires c stick and platformer games. Monster hunter series, xenoblade, SMASH bros. Id be glad to attach a 20bucks controller, game as hard as possible and throw the controller if it starts malfunctioning. (Nah, i care for my 3ds, i just want it when my brother and friends borrow and smash the 3ds instead of the game)
Anyway, is it possible to get the apk file from your phone directly? Like send the app through shareit to get the apk to another phone, or if you have root access, find the root apk. Etc. I want to try getting something you have recently tried on the actual phone rather than a freshly built one. If it makes more sense? And of course of you can manage to do it for me..
The apk you're using is the exact same which gets installed via `adb install` by the debugger, so that's not the problem here. I just can't understsnd how and why--
[at this moment I realized that I made changes to the program, I fixed the same issue with the CPad, but I left the CStick code as-is, and since I'm using my 2DS to test (there's no old3DS irrst support yet) I can't detect CStick code mistakes]
It'll take me a while to fix the CStick bug with one hand, but I'll try and post a (hopefully) fixed build here.
