again read the red
See "bro" | "god" | "nerd" or whatever people call you. yea, sorry my name isnt as catchy as.. "5schatten" IMHO you've no clue what you're talking about and again you don't respect the rules:
Bug reports without a suitable log will often be ignored - no debug log, no issue - or at best will take much longer to be investigated.
xobox one controllers work fine in regular linux builds from my experience. besides i could press CTRL+ALT+F(1-7) ALL DAY and it wouldnt show up in a log, plus even if im wrong my previous logs have me trying every Fkey 1-12 once it boots so check those since this isnt the first time ive said that either
But since I'm in mood to tell you how this build works... let's enlighten you.
It's totally normal to use echo 1 > /sys/module/bluetooth/parameters/disable_ertm for other Linux distros too. Gamepad - ArchWiki
correct... which is why i did that to try and use the xbox one controller. i was asking why it doesnt work, which youre about to answer:
Also the Xbox controller has a long history of problems:
didnt know this, however, im not using emulationstation, i used it to test to see if it works for more troubleshooting information.
*i wasnt filing a bug this time btw i was asking why the xbox one controller maps to mouse. literally never experienced it before*
So maybe think twice before you buy a controller.
right, ill tell my friend that next time he has an xbox one s. its not even my controller dude. i have fiends and we wanna play mariokart wirelessly WITHOUT buying new hardware. MY BAD. jesusare you drunk?
You're refering to your Xbox One controller and the fact that the left analog stick works as a mouse in Kodi.(correct) Well yeah so if in your opinion the input mapping in Kodi is wrong... (what? i never said this. i was saying i cant define the input mapping for neither kodi, es, nor ra) where should you file this bug? Probably in a Remix build that's focused on Retroarch & Emulationstation. Makes sense. Totally. ( it doesnt work at all in official nor escalade, so the fact that it moved the mouse in your remix made me think it was *supposed* to work, but wasnt, which is why i came to wher OH YEA YOUR POST FOR SAID REMIX, so yes, totally makes sens, if you could focus enough to read, friggen drunk.)
Retroarch uses udev as default to detect your controller and load a matching config file. These config files are provided by retroarch-joypad-autoconfig/udev at master · libretro/retroarch-joypad-autoconfig · GitHub and have nothing to do with Kodi. All libretro-cores use this mapping and are not affected by ES or Kodi.
i know this, in retro, the bindings to get recorded just fine, using udev driver, but it ALSO moves the mouse. same as kodi, it will map just fine, BUT ALSO moves the mouse and select goes back no matter what
Emulationstation relies on SDL2 and uses this file to detect your controller sdl_gamecontrollerdb.h and tries to find a matching mapping in es_input.cfg also this mapping is only used for ES menu navigation. All emulators based on SDL2 use the same gamecontrollerdb or gamecontrollerdb.txt to detect controllers and either automap them or allow you to map inputs. Well beside Amiberry that uses SDL2 to detect your controller and is RA mapping compatible but that's another story.
(i dont really use es, thanks for the info but all i asked was how to make the analog stick stop moving the mouse)
So we conclude one frontend mapping does not impact any other frontends and you have to set up your controller properly if you run into problems.
(sigh, god you can ramble)
About your tty problem... well it's interesting how you don't understand that escalades build is based on LE 8.2 and mine is based on LE 9.0. (i understand this completely man, idk what youre on about)And when you're talking about "official" then you're referring to what? This one libreelec-generic.x86_64-8.2.5.img.gz or this libreelec-generic.x86_64-8.90.006.img.gz ? (and when i say official i mean the one on the main download page, published stable one; libreelec-generic.x86_64-8.2.5.img.gz. i have a main hdd two 20gb hdds and when something doesnt work i boot from the other one and test it to see if its specific to a build or not, or if 9.0 fixes it )
Since tty is missing here LibreELEC.tv/mkimage at master · LibreELEC/LibreELEC.tv · GitHub and here LibreELEC.tv/installer at 3230a0838bb43648a935b8a0f14b0eebd1d8cc26 · LibreELEC/LibreELEC.tv · GitHub so there is no tty on official LE alpha builds. If you really need one follow this guide Raspberry Pi Config.txt [LibreELEC.wiki] to unlock your flash partition and add tty to the line APPEND boot=... in /flash/syslinux.cfg
ok this is where you lose me, you do realize im not trying to access a PHYSICAL serial console right? but the ones you can access on virtually any linux dstro, by holding CONTROL and ALT at the same time and then one of the "F" keys at the top of the keyboard. doing this works as i expect on both modified 8.2.5 and escalades 8.2.5, without any modification to cmdline.txt,config.txt or syslinux.cfg but on your build it switches to a black screen with a blinking cursor. this makes it almost impossible to set up on my GENERIC build without a livecd to add the workarounds to udev i need apparantly, because ssh doesnt work ootb, the console normally does on literally every other build ive used. *THAT was the bug i was reporting THIS TIME*
Enabling tty by default could be a major security risk if you use LE in a public environment so a pretty good reason to disable it.
" security risk." oh yea, dont want nobody stealling all my important documents and credit card info off this FREAKIN LIBREELEC BUILD.
you need to take some reading courses or some AA man