S31-Syntax

I'm embarrassed that I even have to ask for help considering the lead-up to it.

I attempted a basic battery swap for my Go, but it flat out won't boot now with either battery.

It charges, orange light stays on for what feels like a full cycle and turns off, but the power switch causes the power light to blink briefly but then stay off.

I tried reading the Indonesian blog linked here but that hasn't helped me very much. It says the first fuse next to the battery connector should read 4.2v with a battery plugged in... but I get at best 3.8. Last I knew, a blown fuse would be an open

Heyo

I acquired this card https://www.ebay.com/itm/154725248752 in order to utilize the touch function of my m14t on my desktop. The monitor works fully using my laptops TB ports, but touch functionality (or usb at all) seems to not work through that card.

I'm using an asrock x570 board with a TB header, the TB header is connected, I can see the card and all its ports using hwinfo64, TB is enabled via bios, and I can get video from the card... but I can't seem to get anything else to function.

Am I just using the wrong kind of card? am I misunderstanding what "thunderbolt ready" means? I'd gladly use the asrock or gigabyte AICs instead but those

Remote access is fine, outside clients can still connect and stream things.

Local access is a totally different story. The TV in the living room can access it, but phones, the tv upstairs, web browsers, etc cannot unless they nav directly to the actual local IP. Plex.tv access flat out doesn't work if I'm on the local network. The app on android times out unless I disconnect from Wifi.

I am going nuts lol, everything is functioning as far as I can see. I did a controlled reboot of everything in the network, and it made no difference. There's nothing in the logs for Plex or its container to suggest a malfunction, which suggests a network bug, but I can't figure out what is causing the i

So I've recently acquired an MZ-R500 and noticed on the wiki pages how easy it was to change EEPROM values to "unlock" features due to the similarities under the hood between it and its siblings. That inspired me to look at the remarkably detailed service manuals to see what the chances are that the pins for the remote are present but just not exposed.

Well, according to the circuit diagram and block diagrams, the MZ-R500 has ALL the necessary bits and bobs under the hood to run a remote, its just not physically broken out to the jack!

Page 37 of the service manual shows the 4 remote pins labeled AP302-AP305, the R700 has those same pins broken out and exposed on TP311-TP314, visible on

I recently purchased a DS720+ as an upgrade to my home media server with the intent to run Plex off of this device. I upgraded from a Dell Micro 7040 primarily because the Celeron j4125 was far newer with a more modern iGPU that claimed to be able to transcode everything I do.

What I've noticed very quickly is that while it can transcode 4k HDR content quite happily, something the i3-6100t in the Micro couldn't do, it cannot transcode subtitles realtime into anything at all, no matter the bitrate... Something the i3-6100t could do flawlessly.

I've applied every fix I can find, fixed every permissions issue I can see, there are zero errors in any of my logs... It just looks like the j4125

So, swarm and sacrifice, railgunner. I realized at wave 52 that I hadn't pulled the trigger more than twice in 5 minutes.

I fired for the last time on wave 55.

Wave 56 I realized you could ride the void crab.

I no longer fear death.

Wave 60 I started on crab back, I did not move not even shoot. Bungus triggered skulls which sparked bands which did obscene damage because of ignition tanks, followed by missiles, then daggers and wil-o-whisps, and the cycle continues until everyone is gone. Enemies die before their spawn animations even finish.

Wave 64 I heard an enemy fire, actually got startled. It's been so long since I felt fear.

Wave 65 was punctuated by a drop to 3

I've been playing with this phone for a couple of weeks now and while I love it, i'm having an issue where no matter what android 7.1 based ROM I flash is unusably unstable.

Wipe everything
Flash LOS14.1 final official nightly-2019213: MTP Host repeatedly crashes, settings crashes, cannot install any apps or view files

Official nightly-2019113: same deal
LOS14.1 unofficial from 2020: same deal
Unofficial from 2021: same deal
/e/-.9: same deal

If I dare install Gapps, everything crashes. Phone, keyboard, MTP, settings, browsers, all of it.

Android 6 roms didn't have this issue
SailfishOS3 started fine but wouldn't update repos and wouldn't install anything, quickly becam

Hey,

I am fully aware that Pico-8 does not have an android release It does however have compiled linux binaries for x86_64 (amd64) and arm64 (aarch64)

Knowing I can't actually execute these binaries in "native" android, I started experimenting with proot-distros I've had success running linux binaries in proot before, namely with titles like Dwarf Fortress using this person's research here: https://www.reddit.com/r/dwarffortress/comments/r80m7y/dwarf_fortress_mobile_running_dwarf_fortress_on/ TL:DR proot debian, fill in required libraries, disable video/sound, force text rendering, launch linux binaries via box64

Obviously I can't force text rendering for pico-8 (although that would be ba

Kinda stuck in place here, i've never had home end up as read-only before. Everything else went off without a hitch

Hey, so after a lot of head-banging over why I couldn't get my pi3 to do HID over Bluetooth despite following the documentation to the letter... I had to go learn how bluez does its doing. Originally I thought that the FLIRC case I had my pi3 in was inhibiting bluetooth function by virtue of it being an aluminum case, but I found that this wasn't the... sigh the case...

Turns out, for whatever reason, the PiKVM HID bluetooth device was never actually turned on by Bluez and never actually told to be discoverable.

It may be worth it to add to the Bluetooth HID documentation found at
[https://docs.pikvm.org/bluetooth_hid/#configuring-the-os](https://docs.pikvm.org/bluetooth_hid/#conf