• 1 Post
  • 107 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2024

help-circle

  • Look up how a CRT works. As the beam draws picture fields, it moves downwards across the screen driven by a 59.94Hz sawtooth wave. The generator of this sawtooth wave needs to be synced to the vertical blanking interval between fields. “Vertical hold” refers to how long the oscillator waits before the window in which it can accept the sync pulse. Too soon and the picture scrolls down, too late and the picture scrolls up (however, slightly too late, as long as 1/59.94 seconds is still within the window, is fine and the picture can stabilize after one slow scroll up).

    Seeing almost two copies of the picture means V-Hold is very late and the vertical oscillator is running way too slow. About 30-40 Hz, very flickery to the person taking the picture!










  • I have a 2013 phone running Android 13. Sony Xperia Z, found in e-waste in 2023 in great condition (except for dust in the camera). I used it a lot and even replaced the battery, although that didn’t make much difference, it just kept overheating and discharging like crazy on modern websites. The notification LED broke in a peculiar way (likely shorted driving transistor, burning it out within hours) and so did the vibrator. Recently, I dropped it and the back shattered but I still carry it every day, although now it’s a secondary phone (can’t get some apps running on my primary one although both are degoogled). It has a 32-bit processor, noisy camera and no fingerprint reader, but a 5" 1080p LCD, MHL (HDMI over microUSB), NFC and headphone jack. And a mediocre FM transmitter that can be enabled with custom drivers for the Qualcomm chip. It was covered in Janus Cycle’s video on monoliths.








  • Which command said that? The first one? Those are just the numbers of sound devices, don’t change those!
    As in:

    Sound device #0 (headphone jack, perhaps): uses snd_hda_intel driver
    Sound device #1 (built-in speaker, perhaps): uses snd_hda_intel driver

    The sleep timer is set by the number in /sys/module/snd_hda_intel/parameters/power_save!


  • Sound card might go to sleep after some time of inactivity.

    Check using cat /proc/asound/modules that you are using standard kernel Intel audio drivers: snd_hda_intel. In that case, try cat /sys/module/snd_hda_intel/parameters/power_save. The number printed is the number of seconds the sound card goes to sleep after the last sound played. Sleeping a sound card can cause pops or buzz and saves very little power, so it’s better to set it to 0 for no sleep.