Posts by escalade
-
-
That's odd, I guess one of two things is happening:
- Freezing Kodi prevents the script from running any further (shouldn't happen as emulationstation.start is spawned as a separate process by systemd)
- Freezing Kodi somehow occupies the framebuffer on the Pi preventing Emulationstation to spawn
Could you try the following command through SSH on any build:
Code# echo step 1 && kodi-send --action="RunScript(/usr/bin/audio-suspend.py)" && echo step 2 && usleep 500000 && echo step 3 && killall -SIGSTOP kodi.bin && echo step 4 && emulationstation --debug && echo step 5 && killall -SIGCONT kodi.bin && echo step 6 && kodi-send --action="RunScript(/usr/bin/audio-resume.py)"
Then paste the output here?
Also test the 20161208-2 build for the RPi which reverts to the old behaviour of fully stopping Kodi.
-
-
-
Looks like you have 3 pads detected: event7, event12 and event13. I'm guessing one of your DS3's is an asian "fake" model which for some reason identifies as two devices. You might be able to reconfigure so that the real joystick devices are on 1-2 in RetroArch and other emus, but you're on your own there
-
Did quite a bit of polishing for this last release, enjoy
20161208:
Code- The "Emulationstation" shortcut on the main menu is now renamed to "Emulators" which starts ES by default but is configurable through /storage/.config/emulator-frontend.conf - Use scrolling sound from ES theme as Kodi sounds - Removed extra ES theme for a slimmer image - Start applications maximized by default - Freeze Kodi instead of stopping it when launching applications for much faster startup times - Enabled scanlines in FS-UAE default configuration - Fixed an issue with Chrome failing to start because of missing libxkcb.so - Updated packages: emulationstation-theme-carbon, dolphin, glupen64-libretro, mupen64plus-libretro, core-info, libretro-database, retroarch-assets, retroarch, mesa, SDL2, xf86-video-intel
-
-
I think you're not likely to get a 100% answer on that one, as it depends on the skin version and it's compatibility with the Kodi version of whatever build you use. Backup, test and report back.
-
You get these cheap SNES style gamepads with a USB cable for about $5 with shipping from China, perhaps try one of those.
-
It takes no effort to add support, simply enable CONFIG_CEPH_FS in the kernel.
-
New build 20161204:
Code- Kodi 17 beta 6 - Removed Docker and Mono for a slimmer build - Switched to mame2014 for the Generic build - Version bumps for a lot of packages
I used Docker for running Chrome/Spotify previously, now that they run natively we don't need Docker any more. If you still need it then install the addon. Run this command through SSH before installing so that the addon finds your containers:
Code# mkdir -p /storage/.kodi/userdata/addon_data/service.system.docker && mv /storage/.docker /storage/.kodi/userdata/addon_data/service.system.docker/
As Mono is no longer included either you will need to install the addon manually if you use Sonarr.
-
-
In that case I'll simply use the upstream packages, so don't worry about that
-
Sure you can, but you'll need to set things up manually.
1. Extract the .tar of the build you want and place KERNEL/SYSTEM into your /boot
2. Set up a GRUB entry to use LE's KERNEL with these arguments: "boot=/dev/sdaX disk=/dev/sdaY quiet tty"sdaX = your /boot partition which should contain the SYSTEM file
sdaY = an empty partition that will be used for LE's /storage -
Download my builds here: 1YiCLhk
-
-
As mentioned, I think it would be a better idea to use an ip-up script (--up) in the per-VPN OpenVPN configuration. Then you add rules for the specific tunnel interface (passed as $dev to the --up script). Likely there are users with more than one VPN and perhaps don't want to limit inbound connections. Perhaps a good idea to create a dedicated chain for the addon which then can be flushed etc without disturbing other potential rules under INPUT.
-
Well, you can once it's configured correctly. I can see why it's confusing, but this isn't a completely integrated solution evenj if it might seem like it. There's several different programs and configurations in play here. Emulationstation is simply a front-end and has it's own controller config. Most games are run by RetroArch which has it's own controller config. Then there's Dolphin for Wii/Gamecube games, Vice for C64 and FS-UAE for Amiga. Some shortcuts are listed on the front page. FS-UAE and Dolphin comes to mind as emulators which don't have an exit key by default on my DS4 and I need a keyboard. Personally I use a wireless Rii keyboard in addition to a DS4 controller.