# Dongle Published articles for Dongle. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Do You Need a USB Wi-Fi Adapter for Raspberry Pi? DevFeed: [Do You Need a USB Wi-Fi Adapter for Raspberry Pi?]() Original publisher: [Read original article]() Author: Karen Rangi Published: 2026-09-17T02:03:01Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Raspberry Pi](), [Wi-Fi](), [USB](), [Dongle]() Tags: [beginner-s-guides](), [dongle](), [pi-4](), [raspberry-pi](), [raspberry-pi-5](), [usb](), [wi-fi]() ### AI overview This guide explains when a Raspberry Pi needs a separate USB Wi-Fi adapter. Most models have built-in wireless, while boards without Wi-Fi require a dongle; adding one may also improve wireless performance. ### Source excerpt A common question when you first get a Raspberry Pi is whether you have to purchase a separate USB adapter for Wi-Fi. If so, should you get one? I'll help you figure out whether you need one and what to look for if you do. Most Raspberry Pi models have built-in wireless and don't need... ## The 5 Best Home Office Gadgets of September 2026 DevFeed: [The 5 Best Home Office Gadgets of September 2026]() Original publisher: [Read original article]() Author: Srishti Mitra Published: 2026-09-15T11:40:11Z Content type: comparison Language: en Sources: [Yanko Design]() Topics: [Bluetooth](), [e-ink](), [USB]() Tags: [2026](), [5-best-designs](), [battery](), [best](), [deals](), [deals-gadgets-office-product-design-shop-5-best-designs-home-office-yd-design-storm-yd-selec](), [dongle](), [e-ink](), [gadgets](), [home-office](), [office](), [portable](), [product-design](), [september-2026](), [shop](), [usb](), [wireless](), [yd-design-storm](), [yd-select]() ### AI overview A comparison of five home-office gadgets selected for their practical, space-saving designs. The supplied text highlights the OrigamiSwift Mouse, a foldable Bluetooth mouse with USB-C charging and up to three months of battery life, and introduces the Inkleaf Foldable Dual-Screen E-Ink Notebook. ### Source excerpt The 5 Best Home Office Gadgets of September 2026 The home office has been redesigned more times than anyone can count. Most of those attempts involve cable management trays and monitor arms that take... ## Latent Powers DevFeed: [Latent Powers]() Original publisher: [Read original article]() Author: Armin Ronacher Published: 2026-09-05T00:00:00Z Content type: opinion Language: en Sources: [Armin Ronacher]() Topics: [Dongle](), [Hacking](), [Rust](), [Embedded Software Dev](), [Protocol (disambiguation)](), [Raspberry Pi]() Tags: [ai](), [dongle](), [firmware](), [hacking](), [protocol](), [raspberry-pi](), [rust](), [soc](), [thoughts](), [usb]() ### AI overview A developer experiments with modifying a cheap CarPlay dongle to run custom code while preserving regular CarPlay functionality. After receiving a different SoC than expected, they use LLM-assisted discussions to flash the device and compile CatPlay, a Rust reimplementation of the CarPlay protocol, for the hardware. ### Source excerpt A few weeks ago I felt like it would be fun to see if I can make one of those cheap Chinese CarPlay dongles run something other than the stock firmware. The idea was that rather than just forwarding CarPlay, why not do something more interesting with them? They all work quite similarly: they act as bridges between your car and the phone. From there they deal with video and audio streams and pass some other data through. Most of them also bring up a custom UI for pairing and have a web interface that your phone can reach for updates. Long story short: I had a conversation with Fable and Sol via Pi about what could be done with such a dongle or whether I should use a Raspberry Pi instead if I wanted to do my own thing there. I figured it might be quite fun to run my own code while still allowing regular CarPlay to pass through. Through working with the LLM I learned about CatPlay, which is a Rust reimplementation of the CarPlay protocol that can run on Carlinkit devices. In particular, it can run on the Carlinkit Mini Ultra, which I figured would be easy enough to buy. I do have a few CarPlay adapters around, but I did not have that particular model, so I bought one on Amazon. Twenty-four hours later, I had a device in my hand that was branded as a Carlinkit Mini Ultra, but instead of being the Ingenic device that the original author used, it turned out to be something else. This is normally where the story would stop. However, it's 2026. Armed with a bit of knowledge about how these systems work, I managed to have some fruitful discussions with Kimi K3 and Sol and figure out how flash the device and in turn, how to make CatPlay compile for that SoC. I guess that hacking these USB devices is not necessarily hard, but it's laborious and you can easily end up bricking your devices. It also just sucks because sometimes you need to work with someone else's code that does not itself run on your machine. In the past, I would abandon many such projects for lack of tenacity. ## Quick update: May 2026 DevFeed: [Quick update: May 2026]() Original publisher: [Read original article]() Author: LoRa Left-handed operational Radio authority; Obviously Published: 2026-05-18T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Home Assistant](), [lora](), [Matter](), [Pinephone](), [zigbee](), [Kernel](), [Pinephone-Pro](), [USB](), [Crystal](), [Dongle]() Tags: [2026](), [community](), [crystal](), [dongle](), [eol](), [home-assistant](), [kernel](), [lcd](), [pinedio](), [pinephone](), [pinephone-pro](), [pinetime](), [pinevoice](), [protocol](), [table](), [update](), [usb](), [zigbee]() ### AI overview Pine64's May 2026 update covers the PineVoice Home Assistant speaker, PineTime and PineTime Pro hardware, PineDio USB LoRa development, and recent PineTab2, PinePhone, PinePhone Pro, and PineTab-V software updates. It also reports instability in the PineDio adapter caused by an overheating crystal oscillator. ### Source excerpt Table of contents Whats been going on recently? PineVoice PineTime/PineTime Pro LoRa? (Left-handed operational Radio authority, obviously) Important recent community updates: Do you have something to share? Contact Community PineStore Whats been going on recently? Hello everyone, we wanted to do a quick update on what's been happening recently. Life has been pretty busy but there's lots of nice things happening in the background that we'd like to share. PineVoice The PineVoice Home Assistant speaker (formally PineVox) is in its final stages. Production begins. Further on this, there will be limited bundle with this device which will include a PineVoice, Zigbee dongle, power supply and two matter modules. Pair it with a SBC of choice and run your Home Assistant instance locally! PineTime/PineTime Pro The current PineTime LCD is EOL and a new one is replacing it, though it is essentially the same display. These will be shipping in the next PineTime batch. New PineTime Pro samples have been received by developers. Shiny! LoRa? (Left-handed operational Radio authority, obviously) The PineDio USB LoRa Adapter is at the focus of a new effort to begin progress on potential new LoRa devices. MeshCore is the current protocol target for the USB LoRa Adapter along with help from the pyMC_core library project. The current problem with the device is that the crystal oscillator is heating up too much and can cause clock frequency drifting instability. In a nutshell that means your messages come out garbled. This may eventually be fixed with a TXCO (Temperature-Compensated Crystal Oscillator) to maintain a stable clock frequency. Important recent community updates: DanctNIX PineTab2 updates (including factory image) Adam Piggz: PinePhone, PinePhone Pro, PineTab2 all updated to kernel 7.0, and improved USB config. Zypper ref and dup to update. machaddr@mastodon.sdf.org: with their new Gentoo PineTab-V image Do you have something to share? Do you have news to share with the communit ## Multi-function USB Dongle based on ESP32-S3 DevFeed: [Multi-function USB Dongle based on ESP32-S3]() Original publisher: [Read original article]() Author: John Lee Published: 2024-10-24T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32-S3](), [USB](), [Data Management]() Tags: [blog](), [dongle](), [esp32-s3](), [espressif](), [http-server](), [usb]() ### AI overview The article presents a multi-function USB dongle based on the Espressif ESP32-S3 module. It addresses cumbersome workflows for transferring camera photos, printing files, and sharing videos, and describes a device combining a USB MSC wireless disk with a USB wireless network card and dual-function switching. ### Source excerpt In modern digital life, we often encounter scenarios where data transfer is not flexible or efficient enough, especially when exporting camera photos, printing files, and sharing videos. In this article, we will have a closer look at the mentioned scenarios and propose a solution - Multi-function USB Dongle based on ESP32-S3. ## Fixing PiKVM and TESmart KVM video issues with an EDID emulator DevFeed: [Fixing PiKVM and TESmart KVM video issues with an EDID emulator]() Original publisher: [Read original article]() Author: Techno Tim Published: 2024-01-19T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Pikvm](), [Hardware](), [hdmi](), [Linux](), [Open Source]() Tags: [devices](), [dongle](), [emulator](), [hardware](), [hdmi](), [homelab](), [intel](), [kvm](), [linux](), [open-source](), [pc](), [pikvm](), [screen](), [server](), [testing]() ### AI overview The article explains how an EDID emulator passthrough adapter resolved video and stability problems between a PiKVM and a TESmart 8X1 HDMI KVM switch. Reported symptoms included black or green screens, failed machine switching, and CPU spikes on the PiKVM. ### Source excerpt After many hours and testing, swapping, resetting, and EDID training, all of my PiKVM and TESmart issues were solved with with a simple, cheap dongle. If you aren't aware of the struggles I faced when using the PiKVM with a TESmart switch, all of it is detailed in a previous post where I ended up settling on another switch altogether. That's all changed now with a simple EDID emulator passthro... ## Tiny Telematics: Tracking my truck's location offline with a Raspberry Pi, redis, Kafka, and Flink (Part 2) DevFeed: [Tiny Telematics: Tracking my truck's location offline with a Raspberry Pi, redis, Kafka, and Flink (Part 2)]() Original publisher: [Read original article]() Author: Christian Hollinger Published: 2022-09-08T00:00:00Z Content type: tutorial Language: en Sources: [Christian Hollinger]() Topics: [Raspberry Pi](), [Kafka](), [apache-flink](), [distributed-systems](), [Back end](), [Linux](), [USB]() Tags: [apache-flink](), [backend](), [distributed-systems](), [dongle](), [flink](), [functional-programming](), [gps](), [kafka](), [linux](), [raspberry-pi](), [redis](), [scala](), [streaming](), [telematics](), [types]() ### AI overview Part 2 of a project that tracks a truck's location offline with a Raspberry Pi and GPS dongle. It sets up backend infrastructure, builds a Kafka and Apache Flink streaming pipeline, persists location data, and tests the system on the road. ### Source excerpt Tracking vehicle location offline with a Raspberry Pi, Part 2: Apache Flink, scala, Kafka, and road-testing. ## HyperX Cloud II sound card USB connector replacement DevFeed: [HyperX Cloud II sound card USB connector replacement]() Original publisher: [Read original article]() Author: Stanko Published: 2021-09-29T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [USB](), [data](), [Windows]() Tags: [dongle](), [headphones](), [how-to](), [replacement](), [usb]() ### AI overview A repair guide for replacing the damaged USB connector on the HyperX Cloud II sound card. It explains the required soldering work and specifies the wire order: black, green, copper, and red. It also notes that reversing the middle data wires prevents Windows and Mac from recognizing the headphones. ### Source excerpt If you are only interested in the wiring diagram, jump directly to the wiring section. HyperX's Cloud II headphones come with a USB sound card, which looks like this: It is a convenient little dongle. I had it plugged in into the front USB port, and I bumped into it, bending the connector for ninety degrees. Naturally, it stopped working. Good thing about these headphones is that the sound card isn't mandatory for headphones to work, but the regular audio cable is pretty short. After searching for the replacement, I realized I can't buy it where I live, and that it costs around 35-40$ which is more than the half of the price for a whole new pair. That is why I decided to try to repair it on my own. The reason I'm writing this blog post is that I couldn't find any information on how to repair it, so hopefully it will help you fix the same problem. Wiring # The process is actually super simple. You'll need some soldering experience and a USB connector. Cut off the original connector and strip the wires. Solder wires to a connector in a following order: Black Green Copper Red Some diagrams will show you different order with middle (data) wires switched, but that won't work. I tried soldering it like that initially, but nor Windows nor Mac would recognize the headphones. The HyperX logo would light up, but Windows gave me a "Unknown USB Device (Device Descriptor Request Failed)" message. That's how I figured out that power wires are connected properly, but the data ones are not. Sorry for the blurry photo, but I didn't want to disassemble everything to get a better one. I hope this will help you fix your headphones and motivate you to try to fix more things in the future, before just ordering a replacement. ## Redsea 0.7, a lightweight RDS decoder DevFeed: [Redsea 0.7, a lightweight RDS decoder]() Original publisher: [Read original article]() Author: Oona Räisänen (noreply@blogger.com) Published: 2016-10-02T19:10:00Z Content type: article Language: en Sources: [Oona Räisänen]() Topics: [C++](), [Raspberry Pi](), [Command-line interface](), [JSON](), [Shell](), [Terminal](), [real-time]() Tags: [c-plus-plus](), [command-line](), [dongle](), [fm-radio](), [json](), [raspberry-pi](), [real-time](), [sdr](), [shell-script](), [software](), [terminal]() ### AI overview This article summarizes the current state and possible future development of redsea 0.7.6, an RDS decoder. It describes supported input streams, line-delimited JSON and hexadecimal output, and efforts to keep the C++ implementation lightweight enough for real-time use on a Raspberry Pi 1. It also notes ongoing sensitivity issues with weak signals. ### Source excerpt I've written about redsea, my RDS decoder project, many times before. It has changed a lot lately; it even has a version number, 0.7.6 as of this writing. What follows is a summary of its current state and possible future developments. Input formats Redsea can decode several types of data streams. The command-line switches to activate these can be found in the readme. Its main use, perhaps, is to demodulate an FM multiplex carrier, as received using a cheap rtl-sdr radio dongle and demodulated using rtl_fm. The multiplex is an FM demodulated signal sampled at 171 kHz, a convenient multiple of the RDS data rate (1187.5 bps) and the subcarrier frequency (57 kHz). There's a convenience shell script that starts both redsea and the rtl_fm receiver. For example, ./rtl-rx.sh -f 88.0M would start reception on 88.0 MHz. It can also decode an "ASCII binary" stream (--input-ascii): 0001100100111001000101110000101110011000010010110010011001000000100001 1010010000011010110100010000000100000001101110000100010111000010111001 1001000010110000111111011101101011001010101110100011111101000011100010 100000011010010001011100001 Or hex-encoded RDS groups one per line (--input-hex), which is the format used by RDS Spy: 6201 01D8 E704 594C 6201 01D9 2217 4520 6201 E1C1 594C 6202 6201 01DA 1139 594B 6201 21DC 2020 2020 Output formats The default output has changed drastically. There used to be no strict format to it, rather it was just a human-readable terminal display. This sort of output format will probably return at some point, as an option. But currently redsea outputs line-delimited JSON, where every group is a JSON object on a separate line. It is quite verbose but machine readable and well-suited for post-processing: {"pi":"0x6201","group":"0A","tp":false,"prog_type":"Serious classical","ta":tru e,"is_music":true,"alt_freqs":[87.9,88.5,89.2,89.5,89.8,90.9,93.2],"ps":"YLE YK SI"} {"pi":"0x6201","group":"14A","tp":false,"prog_type":"Serious classical","other_ network":{"pi":"0x6205","