yep ADM is a playstore app, i dont believe we are at the point of accessing usb sticks from the dock via android, I could be mistaken though, SXOS allows mass storage via the dock but this android stuff is basically a different OS, just take out the SD card and copy across for now
- Joined
- Jan 25, 2013
- Messages
- 467
- Trophies
- 1
- Age
- 40
- Location
- Birmingham, United Kingdom
- Website
- www.youtube.com
- XP
- 1,206
- Country
You can access usb drives and hard drives while docked in android. I personally did this to transfer gamecube games over.
search for the website "apkmirror". There you can download the newest version of nvidia games. copy over to sd card, boot up, open up a file explorer and install it (allow unknown sources)
- Joined
- Jan 25, 2013
- Messages
- 467
- Trophies
- 1
- Age
- 40
- Location
- Birmingham, United Kingdom
- Website
- www.youtube.com
- XP
- 1,206
- Country
Has anyone found a way to get wired controllers working? I have my ps4 controller working via bluetooth but i would like to use my wired xbox one controller through usb.
Suggest finding out how to get the Button Mapping Feature that is present in the GPD XD / XD+ or the NVIDIA Shield Portable and get it integrated into this Android Build, mapped to the Screen Capture Button. That way, Users can Map the Buttons for Games that rely on just Screen Controls.
I had the Shield Portable before, and the button mapper was excellent! It would be very fitting to have that work on the Switch, so it could be part of the Shield family.
I only hope one day that Switch could have an Nvidia Shield TV style interface when docked.
Sent from my SM-G955U using Tapatalk
For those using RetroArch, a User in the Libretro Forums just Posted the following for using the JoyCons....
Posted by bettik
For anyone else stumbling upon this: I’ve got my JoyCons working with RetroArch in Android (LineageOS) on the Switch. (I haven’t tested this with JoyCons connected to Android on any other device.)
You’ll need to install the joycon fix via the built-in TWRP if you haven’t already (just like you would have done if you installed GApps or shieldifier). This was all in the official XDA thread for installing LineageOS on your Switch. You’ll also need to install Magisk the same way (or get yourself root access some other way).
Then you need to replace the existing autoconfig file for the JoyCon with a file that contains the following:
The file, by default, is found somewhere like /data/data/com.retroarch/autoconfigs/android. That’s why you need root access.
You’ll be able to use the analog sticks in the GUI, but they won’t work in games because despite the system seeing them as analog sticks, they are only sending digital data (8-point D-Pad) so RetroArch isn’t getting the actual data it needs from them to use them as analog sticks. It’s going to take someone making a new driver for Android for them to work as analog sticks, so keep checking in on the development over at XDA.
Posted by bettik
For anyone else stumbling upon this: I’ve got my JoyCons working with RetroArch in Android (LineageOS) on the Switch. (I haven’t tested this with JoyCons connected to Android on any other device.)
You’ll need to install the joycon fix via the built-in TWRP if you haven’t already (just like you would have done if you installed GApps or shieldifier). This was all in the official XDA thread for installing LineageOS on your Switch. You’ll also need to install Magisk the same way (or get yourself root access some other way).
Then you need to replace the existing autoconfig file for the JoyCon with a file that contains the following:
input_driver = "android"
input_device = "Nintendo JoyCons"
input_device_display_name = "Nintendo JoyCons"
input_vendor_id = "1406"
input_product_id = "8198"
input_b_btn = "97"
input_y_btn = "99"
input_select_btn = "109"
input_start_btn = "108"
input_up_btn = "h0up"
input_down_btn = "h0down"
input_left_btn = "h0left"
input_right_btn = "h0right"
input_a_btn = "96"
input_x_btn = "100"
input_l_btn = "102"
input_r_btn = "103"
input_l2_btn = "104"
input_r2_btn = "105"
input_l3_btn = "106"
input_r3_btn = "107"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_b_btn_label = "B"
input_y_btn_label = "Y"
input_select_btn_label = "Minus"
input_start_btn_label = "Plus"
input_up_btn_label = "D-Pad Up"
input_down_btn_label = "D-Pad Down"
input_left_btn_label = "D-Pad Left"
input_right_btn_label = "D-Pad Right"
input_a_btn_label = "A"
input_x_btn_label = "X"
input_l_btn_label = "Left Bumper"
input_r_btn_label = "Right Bumper"
input_l2_axis_label = "Left Trigger"
input_r2_axis_label = "Right Trigger"
input_l3_btn_label = "Left Thumb"
input_r3_btn_label = "Right Thumb"
input_l_x_plus_axis_label = "Left Analog X+"
input_l_x_minus_axis_label = "Left Analog X-"
input_l_y_plus_axis_label = "Left Analog Y+"
input_l_y_minus_axis_label = "Left Analog Y-"
input_r_x_plus_axis_label = "Right Analog X+"
input_r_x_minus_axis_label = "Right Analog X-"
input_r_y_plus_axis_label = "Right Analog Y+"
input_r_y_minus_axis_label = "Right Analog Y-"
input_device = "Nintendo JoyCons"
input_device_display_name = "Nintendo JoyCons"
input_vendor_id = "1406"
input_product_id = "8198"
input_b_btn = "97"
input_y_btn = "99"
input_select_btn = "109"
input_start_btn = "108"
input_up_btn = "h0up"
input_down_btn = "h0down"
input_left_btn = "h0left"
input_right_btn = "h0right"
input_a_btn = "96"
input_x_btn = "100"
input_l_btn = "102"
input_r_btn = "103"
input_l2_btn = "104"
input_r2_btn = "105"
input_l3_btn = "106"
input_r3_btn = "107"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_b_btn_label = "B"
input_y_btn_label = "Y"
input_select_btn_label = "Minus"
input_start_btn_label = "Plus"
input_up_btn_label = "D-Pad Up"
input_down_btn_label = "D-Pad Down"
input_left_btn_label = "D-Pad Left"
input_right_btn_label = "D-Pad Right"
input_a_btn_label = "A"
input_x_btn_label = "X"
input_l_btn_label = "Left Bumper"
input_r_btn_label = "Right Bumper"
input_l2_axis_label = "Left Trigger"
input_r2_axis_label = "Right Trigger"
input_l3_btn_label = "Left Thumb"
input_r3_btn_label = "Right Thumb"
input_l_x_plus_axis_label = "Left Analog X+"
input_l_x_minus_axis_label = "Left Analog X-"
input_l_y_plus_axis_label = "Left Analog Y+"
input_l_y_minus_axis_label = "Left Analog Y-"
input_r_x_plus_axis_label = "Right Analog X+"
input_r_x_minus_axis_label = "Right Analog X-"
input_r_y_plus_axis_label = "Right Analog Y+"
input_r_y_minus_axis_label = "Right Analog Y-"
The file, by default, is found somewhere like /data/data/com.retroarch/autoconfigs/android. That’s why you need root access.
You’ll be able to use the analog sticks in the GUI, but they won’t work in games because despite the system seeing them as analog sticks, they are only sending digital data (8-point D-Pad) so RetroArch isn’t getting the actual data it needs from them to use them as analog sticks. It’s going to take someone making a new driver for Android for them to work as analog sticks, so keep checking in on the development over at XDA.
this is very slooooow for me, the SD is 64G U1 class (UNS-1), so not too bad
first try it could no finish the setup, it looped through the google login process
after that it booted into android but it's way too slow, I have 5-6 years old tablets (acer iconia A500 and some NEXUS from the same generation ) and are much faster that this
does other have the same speed issue, I was planing to use it for comics reading with comicrack, but this is unusable
first try it could no finish the setup, it looped through the google login process
after that it booted into android but it's way too slow, I have 5-6 years old tablets (acer iconia A500 and some NEXUS from the same generation ) and are much faster that this
does other have the same speed issue, I was planing to use it for comics reading with comicrack, but this is unusable
i am really confused on how dongles actually work
like how come with terga rcm on PC and an android phone you need a payload bin that goes on the phone or on the PC
does it not work like that with the SX OS pro dongle?
you just said you can use SX OS pro dongle but how can the SX OS pro dongle inject a hekate payload?
is it just like already built in tot he dongle so the dongle and it knows which one to launch automatically somehow?
or do you need to connect a micro USB cable to the SX OS pro dongles female micro USB port and plug it into your PC and upload the hekate bin payload file onto the dongle itself?
how can the SX OS pro dongle just work to launch hekate when the tegra RCM app and a PC need a payload file on the injector end? or doe sit not work?/
do you need to actually upload any different payload files intot he dongle itself or not, can this even be done?
You can boot the Hekate payload by chainloading it from the SX boot menu; that way you only need the SX files and the Hekate payload on your SD card, you don't need a PC. Here is a guide by PRAGMA I found, you may want to check this out.
You can also make the SX pro dongle to inject the Hekate payload, but I am not sure how to do that
Similar threads
