# radio Published articles for radio. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Upcoming Changes to the Nearby Connections API DevFeed: [Upcoming Changes to the Nearby Connections API]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-20T13:00:00Z Content type: release Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [API](), [Android](), [App]() Tags: [android](), [api](), [app](), [applications](), [developers](), [privacy](), [radio](), [update](), [workflows]() ### AI overview Android is changing the Nearby Connections API in late 2026 so it will no longer automatically enable Wi-Fi or Bluetooth radios for applications. Developers must manage radio state manually and notify users when radios need to be enabled. ### Source excerpt Posted by Wei Wang, Engineering Manager, Android BeTo User privacy and transparency are core to the Android experience. To better align with these principles, we are updating the default behavior of the Nearby Connections API regarding how it interacts with device radios. What is changing? Previously, the Nearby Connections API could automatically toggle Wi-Fi and Bluetooth radios ON to facilitate connections without explicit user intervention. Moving forward, the API will no longer automatically enable these radios for 1P and 3P applications. What this means for developers If your app relies on Nearby Connections, you will need to update your implementation to account for these changes: Manual Radio Management: You must ensure that the necessary radios (Wi-Fi or Bluetooth) are enabled before initiating Nearby Connections tasks. User Notification: If the required radios are disabled, your app must now inform the user and request that they enable them manually. The API will no longer programmatically turn them on for you. Timing These changes are scheduled to take effect in late 2026. We recommend reviewing your connection workflows now to ensure a seamless transition for your users. ## How Rain Affects Wireless Microwave Links: 24 GHz, 60 GHz, and 80 GHz Compared DevFeed: [How Rain Affects Wireless Microwave Links: 24 GHz, 60 GHz, and 80 GHz Compared]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-15T09:47:43Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Network](), [Network design](), [Internet](), [data centers]() Tags: [24ghz](), [60ghz](), [80ghz](), [adaptive](), [backhaul](), [capacity](), [changes](), [e-band](), [error-correction](), [fiber](), [microwave](), [network](), [network-design](), [perfomance](), [radio](), [reduction](), [rf](), [wireless](), [wireless-networking]() ### AI overview This article explains how rain fade affects wireless microwave links, with emphasis on 24 GHz, 60 GHz, and 80 GHz bands. It describes how precipitation reduces signal strength, causes adaptive modulation and throughput reductions, and can eventually cause a link to drop when fade margin is exhausted. ### Source excerpt Rain can have a major impact on wireless microwave links, especially as frequencies increase. Learn how rain fade affects 24 GHz, 60 GHz, and 80 GHz circuits, and why fade margin is critical for reliable network design. The post How Rain Affects Wireless Microwave Links: 24 GHz, 60 GHz, and 80 GHz Compared appeared first on Justin Wilson (j2sw). ## Hedy Lamarr's Frequency-Hopping Idea and Its Connection to Bluetooth DevFeed: [Hedy Lamarr's Frequency-Hopping Idea and Its Connection to Bluetooth]() Original publisher: [Read original article]() Published: 2026-06-08T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Bluetooth](), [Protocol (disambiguation)](), [data]() Tags: [bluetooth](), [devices](), [protocol](), [radio](), [receiver](), [signal](), [story](), [technology](), [workshop-learning-programming]() ### AI overview The article describes Hedy Lamarr's life as an actress and inventor, focusing on her World War II idea of rapidly changing radio frequencies to help protect torpedo guidance from jamming. It explains that the US Navy did not use the technology and later connects the frequency-hopping concept to Ericsson's work on a data-exchange protocol, while acknowledging uncertainty about whether Lamarr directly inspired it. ### Source excerpt Fascinating story of Hedy Lamarr, the Hollywood star who is considered the mother of Bluetooth. ## 130 Years of Wireless Communications DevFeed: [130 Years of Wireless Communications]() Original publisher: [Read original article]() Published: 2026-05-29T05:32:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Internet](), [ssh]() Tags: [blog](), [blog-post](), [communications](), [history](), [internet](), [radio](), [ssh](), [wireless]() ### AI overview A brief history of telecommunications compares Guglielmo Marconi's early wireless telegraph experiments and the limited speed of Morse Code transmission with the author's modern 200 Mbps low-Earth-orbit satellite Internet connection and responsive SSH access. ### Source excerpt Here's a short glimpse into the history of telecommunications: in a building at the top of this mountain (barely noticeable blip across the saddle from the radio tower; search for Capo Figari for more details), Guglielmo Marconi conducted experiments in the ~1930s (after inventing the wireless telegraph system in the late 1890s). The original radio could "transmit" at most 40-60 words per minute (the limit of a skilled Morse Code operator). 130 years later, I'm writing this blog post using a 200 Mbps Internet connection via a low-earth-orbit satellite with response times low enough that I can run an interactive SSH session with no noticeable delay. It's almost incomprehensible how far we've come in such a short time. ## Tuning in FM Radio on a 3D Printer Heatbed DevFeed: [Tuning in FM Radio on a 3D Printer Heatbed]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-05-28T14:00:00Z Content type: opinion Language: en Sources: [Jeff Geerling]() Topics: [3D](), [Nanovna]() Tags: [3d](), [3d-printer](), [3d-printing](), [fm-radio](), [geerling-engineering](), [nanovna](), [pcb](), [radio](), [rf](), [sdr](), [signal](), [video]() ### AI overview The article tests whether a 3D printer heatbed can act as an FM radio antenna. Measurements with a NanoVNA found several potentially suitable frequencies, although the heatbed traces are not optimized for radio-frequency use. Near a high-power FM tower, the heatbed received a clear stereo signal. ### Source excerpt Pooch from Repkord dropped by my studio while he was in St. Louis, and asked a simple question: Can a 3D printer's heatbed act as an antenna? A fair question, as many an antenna is embedded in a PCB these days... and the traces on a PCB heatbed like the one used in Prusa's Core One look kinda like an antenna, if you squint the right way. Really, anything (or anyone) can be an antenna, given enough power. ## 2026.5: We're on the same frequency now 📡 DevFeed: [2026.5: We're on the same frequency now 📡]() Original publisher: [Read original article]() Author: Franck Nijhof Published: 2026-05-06T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [GitHub](), [Code](), [Discord]() Tags: [2026](), [building](), [core](), [devices](), [discord](), [documentation](), [github](), [integrations](), [platform](), [radio](), [release](), [release-notes](), [rf]() ### AI overview Home Assistant 2026.5 highlights open development, including a public roadmap and broader community participation. The release also introduces native radio-frequency device support and substantially reworked templating documentation. ### Source excerpt Home Assistant 2026.5! 🎉 What a few weeks it has been! Earlier this month, we hosted State of the Open Home 2026 live in Utrecht, the Netherlands. A big chunk of that day was dedicated to something we deeply care about: building in the open, and how we're going to take that even further from here on out. 💙 Building in the open isn't just about source code on GitHub. It's about doing the planning, the decision-making, and the prioritizing out where everyone can see it, follow along, and join in. And "joining in" doesn't mean you have to write a single line of code or even consider yourself technical. Sharing how you use Home Assistant, telling us what frustrates you, what you wish existed, voting on ideas, helping a fellow user on the forums or Discord, translating, writing documentation, or simply leaving a thoughtful comment on a roadmap item: it all counts, and it all shapes where this project goes next. 🤝 A great first step in that direction also went live this month: our roadmap is now public. You can go browse it, see what we're working on, what's next, and (most importantly) comment on it, share your thoughts, and help shape it. We talked about all of this, and a lot more, on stage. So if you weren't able to join us live, please go watch the recording. It is genuinely worth your time, and it's the best invitation I can give you to come build the Open Home with us. 🗺 Now, on to this release. My personal favorite this month is maybe a bit unexpected, considering it sits all the way at the end of this post: the completely reworked templating documentation. I know, I know, "documentation" doesn't exactly scream headline feature. But hear me out: making Home Assistant more approachable is one of our biggest missions this year, and darn good documentation is a big part of that. We've expanded our documentation team and are investing heavily in this, and the new templating docs are the very first taste of what's to come. I'm really proud of where this is heading. 📚 ## Capturing PAL video with an SDR (and a few dead-ends) DevFeed: [Capturing PAL video with an SDR (and a few dead-ends)]() Original publisher: [Read original article]() Author: Oona Räisänen (noreply@blogger.com) Published: 2019-08-24T18:30:00Z Content type: tutorial Language: en Sources: [Oona Räisänen]() Topics: [Hardware](), [Software]() Tags: [camera](), [capture](), [devices](), [finland](), [github](), [hardware](), [mac](), [programming](), [radio](), [video]() ### AI overview A project diary explores ways to capture PAL video from a Nintendo NES on a MacBook. It discusses unsuccessful or limited capture-device options and records a CRT television and manually configured DSLR camera setup that produced usable video, with some low-frame-rate jerkiness. ### Source excerpt I play 1980s games, mostly Super Mario Bros., on the Nintendo NES console. It would be great to be able to capture live video from the console for recording speedrun attempts. Now, how to make the 1985 NES and the 2013 MacBook play together, preferably using hardware that I already have? This project diary documents my search for the answer. Here's a spoiler - it did work: Things that I tried first A capture device Video capture devices, or capture cards, are devices specially made for this purpose. There was only one cheap (~30EUR ) capture device for composite video available locally, and I bought it, hopingly. But it wasn't readily recognized as a video device on the Mac, and there seemed to be no Mac drivers available. Having already almost capped my budget for this project I then ordered a 5EUR EasyCap device from eBay, as there was some evidence of Mac drivers online. The EasyCap was still making its way to Finland as of this writing, so I continued to pursure other routes. PS: When the device finally arrived, it sadly seemed that the EasyCapViewer-Fushicai software only supports opening this device in NTSC mode. There's PAL support in later commits in the GitHub repo, but the project is old and can't be compiled anymore as Apple has deprecated QuickTime. Even when they do work, a downside to many cheap capture devices is that they can only capture at half the true framerate (that is, at 25 or 30 fps). CRT TV + DSLR camera The cathode-ray tube television that I use for gaming could be filmed with a digital camera. This posed interesting problems: The camera must be timed appropriately so that a full scan is captured in every frame, to prevent temporal aliasing (stripes). This is why I used a DSLR camera with a full manual mode (Canon EOS 550D in this case). For the 50 Hz PAL television screen I used a camera frame rate of 25 fps and an exposure time of 1/50 seconds (set by camera limitations). The camera will miss every other frame of the original 50 fps video, but ## Descrambling split-band voice inversion with deinvert DevFeed: [Descrambling split-band voice inversion with deinvert]() Original publisher: [Read original article]() Author: Oona Räisänen (noreply@blogger.com) Published: 2017-09-12T20:31:00Z Content type: tutorial Language: en Sources: [Oona Räisänen]() Topics: [Software](), [Algorithm](), [Tool]() Tags: [algorithm](), [communications](), [radio](), [security](), [software](), [tool](), [walkie-talkie]() ### AI overview This article explains how the deinvert software tool reverses simple voice inversion and descrambles split-band inversion. It covers the filtering and mixing stages, the role of inversion carrier and split-point frequencies, and why split-band audio requires two inversion passes. ### Source excerpt Voice inversion is a primitive method of rendering speech unintelligible to prevent eavesdropping of radio or telephone calls. I wrote about some simple ways to reverse it in a previous post. I've since written a software tool, deinvert (on Codeberg), that does all this for us. It can also descramble a slightly more advanced scrambling method called split-band inversion. Let's see how that happens behind the scenes. Simple voice inversion Voice inversion works by inverting the audio spectrum at a set maximum frequency called the inversion carrier. Frequencies near this carrier will thus become frequencies near zero Hz, and vice versa. The resulting audio is unintelligible, though familiar sentences can easily be recognized. (HTML5 audio: Inverted speech.) Deinvert comes with 8 preset carrier frequencies that can be activated with the -p option. These correspond to a list of carrier frequencies I found in an actual scrambler's manual, dubbed "the most commonly used inversion carriers". The algorithm behind deinvert can be divided into three phases: 1) pre-filtering, 2) mixing, and 3) post-filtering. Mixing means multiplying the signal by an oscillation at the selected carrier frequency. This produces two sidebands, or mirrored copies of the signal, with the lower one frequency-inverted. Pre-filtering is necessary to prevent this lower sideband from aliasing when its highest components would go below zero Hertz. Post-filtering removes the upper sideband, leaving just the inverted audio. Both filters can be realized as low-pass FIR filters. This operation is its own inverse, like ROT13; by applying the same inversion again we get intelligible speech back. Indeed, deinvert can also be used as a scrambler by just running unscrambled audio through it. The same inversion carrier should be used in both directions. Split-band inversion The split-band scrambling method adds another carrier frequency that I call the split point. It divides the spectrum into two parts that are ## CTCSS fingerprinting: a method for transmitter identification DevFeed: [CTCSS fingerprinting: a method for transmitter identification]() Original publisher: [Read original article]() Author: Oona Räisänen (noreply@blogger.com) Published: 2016-10-07T13:17:00Z Content type: article Language: en Sources: [Oona Räisänen]() Topics: [Programming](), [Streams](), [Library](), [USB]() Tags: [algorithms](), [analysis](), [audio](), [communications](), [dsp](), [library](), [quality](), [radio](), [security](), [side-channels](), [signal](), [usb](), [voice](), [walkie-talkie]() ### AI overview The article investigates whether the 88.5 Hz CTCSS tone in hand-held FM transceivers can fingerprint transmitters by revealing small differences in crystal frequencies and modulation depths. It describes analyzing walkie-talkie recordings with liquid-dsp and a phase-locked loop. ### Source excerpt Identifying unknown radio transmitters by their signals is called radio fingerprinting. It is usually based on rise-time signatures, i.e. characteristic differences in how the transmitter frequency fluctuates at carrier power-up. Here, instead, I investigate the fingerprintability of another feature in hand-held FM transceivers, known as CTCSS or Continuous Tone-Coded Squelch System. Motivation & data I came across a long, losslessly compressed recording of some walkie-talkie chatter and wanted to know more about it, things like the number of participants and who's talking with who. I started writing a transcript - a fun pastime - but some voices sounded so similar I wondered if there was a way to tell them apart automatically. The file comprises several thousand short transmissions as FM demodulated audio lowpass filtered at 4500 Hz. Signal quality is variable; most transmissions are crisp and clear but some are buried under noise. Passages with no signal are squelched to zero. I considered several potentially fingerprintable features, many of them unrealistic: Carrier power-up; but many transmissions were missing the very beginning because of squelch Voice identification; but it would probably require pretty sophisticated algorithms (too difficult!) and longer samples Mean audio power; but it's not consistent enough, as it depends on text, tone of voice, etc. Maximum audio power; but it's too sensitive to peaks in FM noise I then noticed all transmissions had a very low tone at 88.5 Hz. It turned out to be CTCSS, an inaudible signal that enables handsets to silence unwanted transmissions on the same channel. This gave me an idea inspired by mains frequency analysis: Could this tone be measured to reveal minute differences in crystal frequencies and modulation depths? Also, knowing that these were recorded using a cheap DVB-T USB stick - would it have a stable enough oscillator to produce consistent measurements? Measurements I used the liquid-dsp library for signa ## A history of HTML input elements and their inconsistent browser behavior DevFeed: [A history of HTML input elements and their inconsistent browser behavior]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2015-10-22T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [HTML](), [Web Development](), [Web platform](), [Forms](), [browsers]() Tags: [browsers](), [chrome](), [file](), [firefox](), [forms](), [html](), [html5](), [password](), [radio]() ### AI overview This opinion article reviews the history of HTML input elements, including their original types, the behavior of image and file inputs, differences between browsers, and the relationship between input and textarea. It also discusses newer HTML5 input types and their uneven implementation. ### Source excerpt Some people build furniture. Some people knit. Some people have hobbies that don't involve HTML specs from the 90s. I am not those people. So here's a story about , how it got to be the jerk that it is, and why it needs to die in a fire. The early years 1995 was a good year. Friends, ER, Xena were all on TV. TLC had dominated the charts with "Waterfalls". Browsers were ok, because HTML was pretty ok. We had Mosaic, Netscape and IE1, and the HTML2 spec was finally getting around to standardizing forms. 1995 was the year when was born, and now that it's about old enough to drink, we need to have a talk. Input initially came along with 8 types: text, password, checkbox, radio, image, hidden, submit and reset, and in a separate RFC that followed, file. Wait, did you say image? Yeah, let's talk about it. looks like an image, but it's actually an image button that also submits the (x,y) coordinates of where you clicked on the image. Unless you don't specify a src file, in which case it's an "image button" that says "Submit". Unless you're in Firefox, in which case it says "Submit Query" and looks like a label. Unless you're in IE in which case it doesn't say anything at all. Also, for your local pub trivia night, the message that the type=file input to indicate you haven't done anything is "No file chosen", "no file selected", "No file selected", and just an empty textbox on Chrome, Safari, Firefox and IE respectively. Right, ok. And now, a