Hey guys,
Is there a way to manually add a core if you are not rooted? I got the latest nightly , which fixes problems with the xbox controller, but rearmed will just crash when launching a game I am on the shield TV
I think you can change the cores path in the directory settings.
@talos91 I have tried setting the path of the cores, but when I tried to load a core it doesn’t do anything (still says no core). Maybe it’s been changed recently
@sergio-br2 For me it’s not related to restarting t he core. I can’t start any games at all with rearmed. On the shield portable I had the same issue and I could fix it buy manually adding an older version of the core (I am rooted on the portable). On the shield TV I am not rooted, so at the moment I can’t do anything I suppose.
Would be cool to have an option to load cores from a local directory, or even be able to download older cores directly from retroarch. At least people would have the option this way, just like we have the option to install a previous version of RA by sideloading an apk. I like the idea of modularity by having cores separated from the main program, just a shame that on android you can’t fully benefit from that unless you are rooted.
sounds like this issue? https://github.com/libretro/pcsx_rearmed/issues/43 - need a log added to this issue to work out what’s happening
How do I generate a log on the android version?
I’m confused now.
[QUOTE=Scardi;39793] Would be cool to have an option to load cores from a local directory[/QUOTE]
RetroArch has this options for ages. Take a look at Directory options.
@dankcushions Yes that’s exactly the problem I am having. Hopefully it’s easy enough to generate a log on android? Never done that before, I’d love to be able to help
I was able to change the core directory to somewhere else on internal memory. It loads, but I can’t save the directory to the default profile. Cores won’t load from external sd.
@Brianvgplayer Strange I am pretty sure I tried doing that, and loading from internal memory, but it would not load the cores at all. I am using a very recent nightly.
Regardless, I hope someone can fix the rearmed core soon.
But it would definitely be handy to be able to easily import cores that you manually downloaded. Kind of like the core updater, but with an option to import a core from local storage rather than the internet.
[QUOTE=Scardi;39809]@dankcushions Yes that’s exactly the problem I am having. Hopefully it’s easy enough to generate a log on android? Never done that before, I’d love to be able to help[/QUOTE] i’m afraid i don’t know how and do not have an android device, although i was involved with the last few commits, so if someone does know how to get a log/backtrace, i might be able to help from there.
You can use a logcat program to see them directly in Android but I’ve had better luck debugging from a PC using adb logcat.
I guess that would mean get the source code, compile, and run on an android device?
If that’s the case it’s well outside of my realm of capabilities - I was hoping more for a text file generated on the device 
Hopefully a programmer with an android device will be able to provide that
You don’t need to compile anything for it. You just need the adb utility and maybe some USB drivers for your phone on your PC.
As is often the case with this sort of thing, it’s much easier in Linux, but this tutorial should cover doing it in Windows:
Cool, I’ll give that a go on my shield portable and see what happens as soon as I get a chance
Ok, I have a debug log, and its a LOT of text (I only turned on logging just before loading the rearmed core, until I got the crash).
Sorry for the dumb question, but is there a way to attach a file to the post? What’s the best way to pass it on?
[QUOTE=Scardi;39864]Ok, I have a debug log, and its a LOT of text (I only turned on logging just before loading the rearmed core, until I got the crash).
Sorry for the dumb question, but is there a way to attach a file to the post? What’s the best way to pass it on?[/QUOTE]
Go to go advanced and there should be an attachment button on the top right.
throw it on pastebin et al. and then past the link here. All of the lines that we care about start with [RetroArch], so you can trim off the beginning until you start seeing that.
Ok, here we go, let me know if it’s ok, first time I am doing this
http://pastebin.com/download/UJtGrwjG
good work! you should add that log to the github issue linked on the previous page. i’m not sure, but it seems like it crashed during dfinput_activate ? this area was changed by the multitap commits, so maybe they are the problem.
maybe the android build shouldn’t bother with these commits for now? a lot of android devices wouldn’t be able to support 3+ controllers anyway, right?