cat devices I: Bus=0005 Vendor=2820 Product=0009 Version=0100 N: Name="Bluetooth Wireless Controller   " P: Phys=00:15:83:49:94:89 S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/bluetooth/hci0/hci0:43/0005:2820:0009.0001/input/input0 U: Uniq=9a:fc:dd:48:fb:f8 H: Handlers=sysrq kbd mouse0 js0 event0 B: PROP=0 B: EV=12001f B: KEY=4 0 ffff0000 1f0000 10000 2000007 ff9f307a c14057ff febeffdf ffefffff ffffffff fffffffe B: REL=103 B: ABS=30627 B: MSC=10 B: LED=1f   I: Bus=0005 Vendor=1949 Product=0404 Version=011b N: Name="Broadcom Bluetooth Wireless  Remote Control                  " P: Phys=00:15:83:49:94:89 S: Sysfs=/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/bluetooth/hci0/hci0:44/0005:1949:0404.0003/input/input2 U: Uniq=74:c2:46:7d:62:f6 H: Handlers=kbd event1 B: PROP=0 B: EV=10001b B: KEY=10000 1110 40000800 1681 0 0 0 B: ABS=100 0 B: MSC=10

hey there! i've been using a fire tv remote on rpi2 with openelec and osmc. osmc did work out of the box openelec with the help of the following thread http://openelec.tv/forum/104-bluetooth-remotes/75420-fire-tv-stick-remote-with-raspberry-pi it connects on recalbox, but it doesn't respond neither in kodi nor in emulationstation --------------- # hcitool dev Devices: hci0    00:15:83:49:94:89 # hcitool con Connections: < ACL 74:C2:46:7D:62:F6 handle 44 state 1 lm MASTER AUTH ENCRYPT < ACL 9A:FC:DD:48:FB:F8 handle 43 state 1 lm MASTER AUTH ENCRYPT # hcitool info 9A:FC:DD:48:FB:F8 Requesting information ... BD Address:  9A:FC:DD:48:FB:F8 Device Name: 8Bitdo NES30 GamePad Joystick LMP Version: 3.0 (0x5) LMP Subversion: 0xc Manufacturer: RDA Microelectronics (97) Features page 0: 0xff 0xff 0x8d 0xf8 0x98 0x1f 0x79 0x83 <3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <hold mode> <sniff mode> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <power control> <transparent SCO> <broadcast encrypt> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <extended SCO> <AFH cap. slave> <AFH class. slave> <3-slot EDR ACL> <5-slot EDR ACL> <sniff subrating> <pause encryption> <AFH cap. master> <AFH class. master> <extended inquiry> <simple pairing> <encapsulated PDU> <err. data report> <non-flush flag> <LSTO> <inquiry TX power> <extended features> Features page 1: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Features page 2: 0xff 0xa7 0xff 0xff 0x00 0x65 0x07 0x01 # hcitool info 74:C2:46:7D:62:F6 Requesting information ... BD Address:  74:C2:46:7D:62:F6 Device Name: Amazon Fire TV Remote LMP Version: 3.0 (0x5) LMP Subversion: 0xa05 Manufacturer: Broadcom Corporation (15) Features page 0: 0xbf 0x06 0x86 0x78 0x18 0x1e 0x59 0x87 <3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <sniff mode> <RSSI> <channel quality> <paging scheme> <power control> <broadcast encrypt> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <AFH cap. slave> <AFH class. slave> <sniff subrating> <pause encryption> <AFH cap. master> <AFH class. master> <extended inquiry> <simple pairing> <encapsulated PDU> <non-flush flag> <LSTO> <inquiry TX power> <EPC> <extended features> Features page 1: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 ----------------------- any ideas anyone? thanks Stefan

@hstampfl what? are these shaders going to be activated in 3.3.0? they look nice! can't wait for 3.3.0

no but i hope someday you can

hey there! am i seeing double or are there 2 kodi locations? so there are 2 userdata-folders... the first in /usr/share/kodi/ the second in /root/.kodi/ and it seems like xml-files have to be put in just one of them... the right one for each file. so advancedsettings to /usr/share/kodi/userdata but not to /root/.kodi/userdata sources.xml has to be put in /root/.kodi/userdata but won't work in the other. or do they belong to /usr/share/kodi/userdata and then automatically moved to the /root/.kodi?? i am confused...

oh okay, that's why... thanks. but honestly i wouldn't care for a longer boottime - its a raspberry pi, so most people can and will run it 24/7 anyway because thats one of the main benefits of the low power consumption (especially because recalbox is a mediacenter as well and might be used everyday)

even when using a network cable there seems to be a problem with the network to be initialised too late. mounting a cifs share only works when adding "mount -a" to /etc/init.d/S99myscript (for example). but then it's too late -> emulationstation won't start and an error message (no roms found). is it possible to make the network working even before /etc/fstab is "started"? so there'd be no need for an additional script. that's my order now and it seems to be working (i changed S13, S15 and S19) S01logging S02hotplug S02serial S03cleanrun S10udev S11removeeth1 S13network S15networkrestart S19myscript (just "mount -a") S20urandom S29recalboxsystem S30dbus S31emulationstation S31sixad S49ntp S50dropbear S50kodi S60nfs S91smb rcK rcS

i think it's only there on rpi1. BUT my rpi2 is on 900mhz instead of 1100mhz (the front page on recalbox.com is saying 1100mhz) i guess 1100mhz is too much though

it's working now with 3.2.8 after rebooting emulationstation even shows a changelog where it says "cifs support" thanks edit: i mean, YEEEEEAAASSSS!!! edit 2: mounting with fstab didn't work at first. i'm using a cable for network and no wlan but i tried adding a startup script (just "mount -a") and.. it worked! just strange, that it didn't work with /etc/fstab alone... https://github.com/digitalLumberjack/recalbox-os/wiki/Add-your-own-startup-script-(EN)

so should "cifs" be there only in 3.2.8 or also in 3.2.7?

well you learn that (backup) after using raspberry pis for some time pulling the plug should be avoided on RPI at all costs when the system is running - even when it looks like it's frozen... it's always a good idea to try SSHing into the RPI and reboot it there by entering "reboot" instead of pulling the plug. at least if it's not frozen completely... https://github.com/digitalLumberjack/recalbox-os/wiki/Root-access-on-terminal-(EN)

that's why i always talking about backups and smb-shares for easy backup did you do anything? did you change anything in config.txt? overclocked a bit too much or anything? maybe you can set up linux (live cd?) on your desktop computer, but in the sd card, mount the volumes and copy over the needed files?

scraping boxarts and stuff can be a very long process. it's very frustrating, when those files get lost (SD card breaks,...) i can't find a way to backup this stuff... any ideas how to do that? maybe another share of /root/.emulationstation/gamelists and /root/.emulationstation/downloaded_images ?

hey! will n64 savestates from /root/.local/share/mupen64plus/save one day be available in the network share "sauvegardes" when n64 support is out of beta?

cat /proc/filesystems | awk '{print $NF}' | sed '/^$/d' sysfs rootfs ramfs bdev proc cgroup tmpfs devtmpfs debugfs sockfs pipefs rpc_pipefs configfs devpts ext3 ext2 ext4 vfat msdos nfs nfs4 ntfs autofs fuseblk fuse fusectl mqueue # cat /proc/filesystems | awk '{print $NF}' | sed '/^$/d' | grep cifs

well, thank you for the how-to, but sadly that's still not working for me... MANUALLY # mount -t cifs //192.168.1.240/Daten /mnt/test -o user=rpi@home.int,password=,domain=home.int,uid=0,gid=0,rw mount: mounting //192.168.1.240/Daten on /mnt/test failed: No such device ON BOOT //192.168.1.240/Daten /storage/srv01/daten cifs user=rpi@home.int,password=,domain=home.int,uid=0,gid=0,rw 0 0 # mount -a mount: mounting //192.168.1.240/Daten on /storage/srv01/daten failed: No such device

yatse: youhave to activate the webinterface in kodi settings (what you already did) and enter the ip adress manually in yatse or xbmc remote. it wont find it automatically, because zeroconf isnt active (i think)

i have a set of these www.amazon.de/CSL-Gamepad-Vibration-Controller-schwarz/dp/B007AAYFW2 seems like the analog-switch-button is broken on one of them oops so this explains this thing... seems like, when in digital mode the sticks do the same as the d-pad (digital and 8-directions) and the right stick does the same as the buttons A B X Y. when in analog mode they suddenly become additional analog axes. i hope that clears things up. a new problem is, that the screen now turns black after mapping the buttons when both of them are connected - ssh connection is still possible... can i get a logfile out of the system that might be helpful, if you think that might be caused by the new script you posted.

yes. it's working now. i cant turn on analog now... don't know why. the sticks still work but behave like 8-direction digital d-pads. but that only might be important when playing some n64/psx games. thanks!

Try this: On the frontend screen, press F4 to quit, then ALT+F2 to get a terminal and use the same credentials as above. (User: root / Password: recalboxroot) Source: https://github.com/digitalLumberjack/recalbox-os/wiki/Mini-How-To-(EN)