u/lukmly013 💾 (lemmy.sdf.org)

I like computers, trains, space, radio-related everything and a bunch of other tech related stuff. User of GNU+Linux.
I am also dumb and worthless.
My laptop is HP 255 G7 running Manjaro and Linux Mint.
I own RTL-SDRv3 and RSP1 clone.

SDF Unix shell username: user224

  • 5 Posts
  • 247 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle








  • A bit unrelated, but if you have DD-WRT on WiFi router with USB, you can install Entware. There’s also a few games.

    I used to play Tetris (vitetris) on my old WiFi router. I also tried to compile doom_ascii for MIPS, but I wasn’t successful and gave up. That was 5 months ago, so I basically forgot everything I tried already.
    I have also tried to compile it directly on the WiFi router, but it kept crashing even when I killed all running services (including SSH and Telnet so I had to use console, at least it’s 115,200 baud) that weren’t necessary. I think 32MB of RAM was my problem.
    Anyway, I doubt it would run on it anyway, but at least I tried.

    List of games available (at least for MIPS): angband, cavezofphear, crawl, gnuchess, minesweep-rs, nethack, rcon, sudoku-tui, superstartrek, tty-solitaire, vitetris, zork.

    Edit: Hmm, it seems at least very few Netgear switches may be supported by OpenWRT (e.g.: https://openwrt.org/toh/netgear/gs308t_1). Maybe there is potential to actually play games on that switch!


  • Manufacturers are allowed to add supplementary charging standards on top of USB-C PD

    Controversial opinion: I wish this wasn’t the case. So many different proprietary protocols, most of the time you’ll still need a specific adapter, and in some cases even a proprietary cable to utilize the full speed, and nowadays most devices come without the adapter.
    And there’s even PPS in the PD spec allowing to request for a specific voltage rather than something in an existing list.

    But I do also have some personal grievances here:

    1. Mi TurboCharge - This may be something based on PD, but still being something separate. I don’t know, but I do know it requires more pins than USB-A has. 5 pins. Somewhere I read this is connected to a CC pin in the USB-C connector. But no, they did not use USB-C, they used USB-A, with an extra pin. Only shortly before the phone died I finally figured out why it wasn’t charging as fast as expected - I wasn’t using their proprietary cable.

    2. My current phone’s interference (?) with Qualcomm QC 2.0 - Somehow when using a cable with non-perfect connection on QC-compatible adapters, when I move the USB-A connector, it starts triggering 12V mode until it finally shows overvoltage error and slows down to 7W. QC 2.0 is how my USB tester identifies it. This is a MediaTek-based device, so I don’t think it would support QC. The original adapter uses PD and some 11V 6A thing with unknown protocol. Perhaps that is where the problem originates, I don’t know what data it sends down. But testing with OTG adapter on the original brick it seems the protocol needs the extra pins of USB-C to work properly.

    I’ve had 3 phones that supported some fast charging, so far 2 of them made it into a confusing mess. Had they all used just PD it would have been a better experience.






  • If I remember correctly, GSM900. The shutdown of 2G in my country is set at around 2028 - 2030, so I’d be good for a bit.

    In other words, just like with my current phone that doesn’t work with VoLTE on my carrier because VoLTE is a total mess. This once again leaves me with 2G for phone calls. (Although I use LTE-only to prioritize data meaning nobody can call me ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯)
    Hell, my carrier hasn’t even yet implemented USSD over IMS which means no call barring settings, no call forwarding settings, no caller ID settings, no USSD codes and just everything else that uses MMI codes. All depends on GSM.

    I don’t know why it is accepted that there’s no single mandatory standard for VoLTE that would work everywhere, but I guess people’s ability to put up with BS is just going up over time.
    And yes, this impacts emergency services too, with US visitors, for example, even if the devices support VoLTE at home.


  • I hope for something like the Motorola D lineup. You could take out the original battery and replace it for 4xAA batteries. That’s pretty cool.

    A few months ago I was quite happy to finally win one functional handset, Motorola D170, in auction for just around €7 incl. shipping. Unfortunately, I always bring bad luck. The seller unexpectedly ended up in hospital and I got a refund.

    The D170 even has a flip-out keypad cover which makes it even cooler. And all of these have extendable antennas.
    A picture of D170 for illustration (not the same unit):

    Otherwise the most available seems to be D520, but almost all of them are corroded and non-functional because people left batteries in them.





  • Just in case: If your storage is completely full all of a sudden, check /var/log/nginx if you haven’t pointed the logs elsewhere.

    I know I was pretty confused to find my storage absolutely full, then I found the multi-GB error.log file. When a network interface it was listening on disappeared it filled with errors as such:

    2024/12/10 07:57:06 [alert] 20420#20420: accept4() failed (22: Invalid argument)
    2024/12/10 07:57:06 [alert] 20420#20420: accept4() failed (22: Invalid argument)
    2024/12/10 07:57:06 [alert] 20420#20420: accept4() failed (22: Invalid argument)
    2024/12/10 07:57:06 [alert] 20420#20420: accept4() failed (22: Invalid argument)
    2024/12/10 07:57:06 [alert] 20420#20420: accept4() failed (22: Invalid argument)
    2024/12/10 07:57:06 [alert] 20420#20420: accept4() failed (22: Invalid argument)
    

    (I just reproduced that now on-demand, thus the date.)

    There’s a tool called logrotate to take care of logs, but I just did the stupid and lazy thing…

    error_log /dev/null;
    

    Well, in case you get the idea to run NGINX in Termux, and then later you find your phone hot, stuck in a bootloop, it’s possible the error.log filled the storage causing Android to crash because it now can’t even write system files.
    Not that I would have done such thing…