Tue 14 Apr 2026 08:10:54 AM -04 Speedybee TX800 FPV VTX: what to do if it doesn't seem to obey power-change commands from the FC - TL;DR: the VTX is probably locked, press and hold its switch for 10 seconds and release to unlock; - In detail: - Connected mine to the F722 Mini FC on my Flywoo Explorer LR4 FPV drone; - Carefully followed the Betaflight configuration section on the VTX manual; - Testing on the bench, everything seemed to work; - Out in the field, video became unusable after a couple of hundred meters; - Upping the VTX power all the way to 800mW (using BF's Features/VTX menu) didn't help. - Changing the VTX band and channel using the same menu worked perfectly, which seemed to discard the possibility of a hardware cause (all FC to VTX commands go over the same "I" wire); - Back at the bench, noticed the current meter ("A" in the Betaflight OSD) didn't change much between 25mW and 800mW VTX power (even with the motors disarmed it naturally fluctuates which made it harder to be sure, but the range in which it fluctuated didn't seem to change); - Noticed the VTX LEDs (really hard to see when the VTX has its metallic shell on) were: Orange=off, red=blink, blue=blink; the pattern didn't change when changing the power level over the menu. - The manual (https://www.speedybee.com/tx800-download/) isn't very readable (including because it showsthe LED table shows them in a different order, and not listing any valid state with the blue LED blinking), but after some head-scratching, figured that perhaps the VTX was in a "locked" state; - Pressed the VTX switch for 10 seconds and then released it; for some reason, had to do that a couple of times until the LED pattern changed to orange=off, red=off, blue=off; - In that state, the VTX seemed start obeying the FC power-change commands: setting it to 800mW for example, made the orange LED go from off to on, and the current meter showed a definite increase in the range in which it fluctuated; - Went out in the field and voila, the range definitely went with the power; - The hold-the-switch-for-10-seconds apparently only needed to be done once, haven't had to repeat it yet despite multiple battery disconnects/reconnets. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Thu 30 Oct 22:53:43 GMT 2025 BancoEstado_app_HOWTO: How to make the infamous BancoEstado app (net.veritran.becl.prod version 7.14.0.51809) work on a LineageOS smartphone rooted with Magisk Reference: https://droidwin.com/how-to-hide-root-from-apps-via-hide-my-applist/ -> Archived at: https://archive.is/FZ1Fe and https://web.archive.org/web/20260330061943/https://droidwin.com/how-to-hide-root-from-apps-via-hide-my-applist/ -> Steps 1, 2 only; -> DON'T FORGET TO TURN ON "Enforce DenyList" -> Then DISABLE USB DEBUGGING (in Developer Options) -> REBOOT -> With this, the BancoEstado app will run. -> This is APPARENTLY (because a lot of other stuff was done while trying to fix it, per reference above), what it took on Xiaomi Redmi Note 7 aka Lavender (after reinstalling with Unofficial LineageOS 22.1) and Xiaomi Redmi Note 9S aka Curtana; but did NOT work on a Xiaomi Redmi Note 9 Pro aka Joyeuse. Tue Apr 7 09:54:10 -04 2026 CONFIRMED: MUST DISABLE USB DEBUGGING, or BancoEstado app will NOT RUN, instead will stop at start with the same message stating "jailbreak or rooted phones not supported". =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Fri Apr 5 13:50:17 -03 2019 restic resiliency in case of corruption/loss/damage in its backup repository files: -> Summary of the conversation with the main developer (fd0) on irc://irc.freenode.net/#restic: 03:04 < fd0> [...] ah, the example isn't great [referring to "look for "boom" here: https://restic.readthedocs.io/en/latest/045_working_with_repos.html?highlight=%22boom%22 03:05 < fd0> [...] the index can be recreated with 'rebuild-index' if it's corrupted 03:05 < fd0> for other things, it depends what's broken 03:05 < fd0> if the key file is lost, you're screwed 03:05 < fd0> it isn't cache on the client (on purpose) 03:06 < fd0> if some file below data/ is lost, there are two cases: 03:06 < fd0> 1) it contained data blobs (parts of files), then all files referencing these blobs cannot be restored completely 03:06 < fd0> 2) it contained tree blobs (metadata), then all dirs described by the metadata cannot be restored 03:06 < fd0> including any dirs referenced by the missing metadata 03:07 < fd0> for the rest, there's a good chance most of it can be restored 03:07 < fd0> there's even the the (relatively new) 'recover' command, which looks for trees that aren't referenced anywhere, and creates a new snapshot containing them =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Sat Sep 13 08:00:13 PDT 2014 /bin/less aborting with message "Cannot allocate memory (press RETURN)" when searching for strings in a largish (~1GB) file: -> Never saw that before; a google search also returned nothing useful; -> Happened while I was searching log files in a Linux Ubuntu 10.04 (Kernel 2.6.32) 8GB ECC RAM AMD Phenon II machine which just had a complete lockup and had to be hardware-reset. -> An strace on the /bin/less process showed calls to mmap2() returning ENOMEM (even as the machine had more than enough RAM free to load the entire file in memory, which /bin/less doesn't do). -> After a few attempts trying to debug this situation, the machine hang completely again. -> I opened the case to examine it; lo and behold, it had a seized (ie, non-turning) rear fan. Also, touching the on-board chipset heatsink was distinctly umcomfortable, the CPU heatsink even more so (I estimate it was at least at 65oC, perhaps more). -> Turning the machine off and waiting for it to cool, and at the same time replacing the broken rear fan seems to have solved the problem: after turning the machine back on, no more weird behavior from /bin/less, and it has not locked up again. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Sun Aug 24 05:47:46 PDT 2014 How to get the equivalent of Stop-A on a Oracle (ex-Sun) SPARC T4-2 server using a common PC (ie, non-Oracle) USB keyboard: -> Just press combination; the commonly reported did not work (at least on an Oracle T4-2 server). -> Perhaps related, we also uncommented the following line in /etc/default/kbd KEYBOARD_ABORT=alternate and then run "kbd -i". -> Also note that, to gain use of the graphics console, we had to use ILOM to set auto-boot to false and then reboot into OpenBoot to set these two OpenBoot variables: setenv input-device keyboard setenv output-device screen reset-all -> Before all that, we also had to install patch 142373-04 which is an update for the graphics card driver. With the above, the machine now works perfectly with a common "VGA" (ie, DB-15 connector) LCD monitor plugged to its rear video connector, and an USB keyboard connected to one of the front USB ports. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Thu Aug 22 07:46:18 PDT 2013 Java stops working on Seamonkey in Ubuntu 10.04 -> Happens because the latest (2013/07/24) update to openjdk-6-jre-headless (from version 6b27-1.12.5-0ubuntu0.10.04.1, 6b27-1.12.6-1ubuntu0.10.04.2) is FUBAR. -> Symptoms: -> pages with Java applets are broken; -> The following is displayed when seamonkey is called from a shell: java version "1.6.0_27" OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.10.04.2) OpenJDK Server VM (build 20.0-b12, mixed mode) java.lang.NullPointerException at javax.swing.SwingUtilities.appContextGet(SwingUtilities.java:1858) at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1828) at javax.swing.JWindow.(JWindow.java:185) at javax.swing.JWindow.(JWindow.java:137) at net.sourceforge.jnlp.runtime.JNLPSecurityManager.(JNLPSecurityManager.java:121) at net.sourceforge.jnlp.runtime.JNLPRuntime.initialize(JNLPRuntime.java:238) at sun.applet.PluginAppletSecurityContext.(PluginAppletSecurityContext.java:245) at sun.applet.PluginMain.main(PluginMain.java:109) Something very bad happened. I don't know what to do, so I am going to exit :( -> Solution: -> Downgrade to previous version of the above package, also of related packages to avoid problems with APT: cd /tmp wget https://launchpad.net/~ubuntu-security/+archive/ppa/+build/4519908/+files/openjdk-6-jre-headless_6b27-1.12.5-0ubuntu0.10.04.1_i386.deb \ https://launchpad.net/~ubuntu-security/+archive/ppa/+build/4519908/+files/icedtea-6-jre-cacao_6b27-1.12.5-0ubuntu0.10.04.1_i386.deb \ https://launchpad.net/~ubuntu-security/+archive/ppa/+build/4519908/+files/openjdk-6-jre_6b27-1.12.5-0ubuntu0.10.04.1_i386.deb sudo dpkg -i openjdk-6-jre-headless_6b27-1.12.5-0ubuntu0.10.04.1_i386.deb \ icedtea-6-jre-cacao_6b27-1.12.5-0ubuntu0.10.04.1_i386.deb \ openjdk-6-jre_6b27-1.12.5-0ubuntu0.10.04.1_i386.deb -> To prevent APT inadvertently upgrading the packages and undoing the above: for openjdk-6-jre icedtea-6-jre-cacao openjdk-6-jre-headless openjdk-6-jre-lib; do sudo dpkg --set-selections; done apt --get-selections| grep -- -jre gcj-4.4-jre-lib install icedtea-6-jre-cacao hold openjdk-6-jre hold openjdk-6-jre-headless hold openjdk-6-jre-lib hold sun-java6-jre install -> Avoid using seamonkey for anything non-essential, specially acessing untrusted sites as above rolled back a lot of security upgrades; -> Bug the developers so they fix it ASAP: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1215487 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tue May 6 16:32:31 EST 2008 Installing the flash player plugin in Ubuntu 8.04 (Hardy Heron) -> Won't install from the "install plugin" dialog in Firefox, complais about broken repositories; -> Managed to install it with: cd /tmp wget http://us.archive.ubuntu.com/ubuntu/pool/multiverse/f/flashplugin-nonfree/flashplugin-nonfree_9.0.124.0ubuntu2_i386.deb sudo dpkg -i flashplugin-nonfree_9.0.124.0ubuntu2_i386.deb =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tue May 6 16:22:15 EST 2008 Blue Screen Of Death on Windows XP install in machine with PCI-Express X16 video card Message: "The video driver failed to initialize" Codes: "STOP: 0x000000B4 (0x00000000,0x00000000,0x00000000,0x00050000)" Situation: Installing Windows XP SP1 from CD on a new machine (motherboard AOpen i975Xa-YDG with a PCI-Express X16 Geforce 7900GT video card); Windows XP hangs in the middle of installation, right in the beginning of the first graphical boot. Solution: Move the video card from the second X16 slot (nearer the power supply) to the first (farther from the power supply) and restart the install. After Windows XP is installed and upgraded to SP2, you can move the video card to the second slot if you want (I did as it provided for better airflow inside the computer). =Eof=