suzucappo

joined 1 month ago
[–] suzucappo@lemmy.world 2 points 2 days ago (1 children)

Yeah, I did look a little bit and saw that.

If I recall correctly the TV is kind of in this in between update where I was able to get into it and lock it down the way that I want but I can't get it to give me root access. From what I remember I shouldn't have even been able to get into it at all but was still able to.

Fun stuff.

I'll look into it again though since it's been about a year. Maybe there is something new.

[–] suzucappo@lemmy.world 6 points 2 days ago (3 children)

Haha yeah, I agree.

It's a Toshiba 65C350 Fire TV.

I considered returning it but I'm used to tinkering with stuff so I just dealt with it. I won't do that again though lol. Was not one of the more fun things to mess with.

It'd be nice if I could flash it completely to remove all their junk. I mean, the device is running Android of some sort so it's possible but I'm not that invested in trying to figure that out.

[–] suzucappo@lemmy.world 7 points 2 days ago* (last edited 2 days ago) (5 children)

Some TVs do not give you that option though. Shield or not, I have one that will straight up block 90% of the screen every 10 minutes if it doesn't have a connection.

I would toss it, but it was 250$ and 65" with a decent display. So I used ssh to get into it and install a firewall to block 90% of the TV from access, including the update service. Also have filtering through my network firewall for ad servers, update servers etc.

So now the scan for a connection works, but they aren't getting much of anything in terms of metrics or telemetry or other information from the TV. I also disabled the default launcher and installed a different one on it as well as jellyfin.

I will never buy another TV like that though, it was an absolute pain to get it working. It should be illegal to hinder usage of a TV just because they are being blocked from invading your privacy.

[–] suzucappo@lemmy.world 1 points 1 month ago (1 children)

Yeah, now the only issue is that it's showing up as an xbox controller in the games and registers as a button rather than an analog movement so it's all or nothing when I hit it lmao.

[–] suzucappo@lemmy.world 3 points 1 month ago* (last edited 1 month ago) (3 children)

Sounds good.

I'll check that out and if you remember how you did it please let me know.

Thank you!

I was able to get some help in the Simracing space. I have it working now.

Going to update the post with what we did.

44
submitted 1 month ago* (last edited 1 month ago) by suzucappo@lemmy.world to c/linux@lemmy.ml
 

As the title says I am trying to get my handbrake to recognize as a joystick so I can use it.

Running Arch.

This is the device in question. https://www.amazon.com/dp/B07SPVY2WL

It shows up with lsusb as the following. Bus 001 Device 006: ID 1021:1888 ZSC ODDOR-HANDBRAKE

Device info from cat /sys/kernel/debug/usb/devices T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=04 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=1021 ProdID=1888 Rev= 1.14 S: Manufacturer=ZSC S: Product=ODDOR-HANDBRAKE C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=01 Prot=05 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=10ms E: Ad=01(O) Atr=03(Int.) MxPS= 64 Ivl=10ms

I found this bit of information but it's related to openSUSE and is quite old but I'm hoping it might help. https://www.spinics.net/lists//linux-input/msg88778.html

It doesn't show up in /dev/input/...

Any ideas on how I could get this thing recognized so I can use it?

Update 1:

I got connected with someone at the Simracing space on matrix per the advice from @lemonuri@lemmy.ml and they helped me to get it working. Here is what we did.

Create the file 99-handbrake.rules in /etc/udev/rules.d and add the two following lines to it.

SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="1021", ENV{ID_MODEL_ID}=="1888", RUN+="/bin/sh -c 'echo 1021 1888 > /sys/bus/usb/drivers/usbhid/new_id'"

SUBSYSTEM=="input", ATTRS{idVendor}=="1021", ATTRS{idProduct}=="1888", ENV{ID_INPUT_JOYSTICK}="1"

This forces the device to usbhid as a joystick whenever it is plugged in and recognized.

Run the following command to reload the device rules if you don't want to reboot. Otherwise you can omit the command and reboot.

sudo udevadm control --reload

It now shows up and is working.

So the device was registering a button at the end of the pull and showing up as an Xbox controller while not recognizing the axis being moved so it was all or nothing.

I installed protopedal and following advice created a dummy device which remapped the inputs so that it registers the analog input only which worked.

protopedal --name "handbrake" -b JOYSTICK -a THROTTLE -s 0:THROTTLE -a Y --no-auto-buttons --no-auto-axes /dev/input/by-id/usb-ZSC_ODDOR-HANDBRAKE-event-joystick

Update 2:

All credit goes to JacKeTUs for his work on helping me out. He is making/made the driver for this. It may go into AUR for Arch users, so if anyone ends up looking for support for this handbrake you can find the source at the below link.

https://github.com/JacKeTUs/hid-oddor-handbrake

This will install the driver (currently it needs to be loaded after running sudo make) and the udev rule. It eliminates the need for protopedal but does require launch options to be set.

SDL_JOYSTICK_WHEEL_DEVICES=0x1021/0x1888 %command%

Update 3:

Latest push eliminates the need for steam launch option and removes the button from the device.