AVR-Remote

de.pskiwi.avrremote
by Zapstore _@zapstore.dev

Republished from GitHub / F-Droid by the Zapstore main account.

Turn your phone into a full remote control for your Denon or Marantz AV receiver. The app talks to the receiver directly over your own Wi-Fi - no account, no registration, no cloud service and no ads. WHAT YOU CAN CONTROL • Power, volume and mute - for the main zone and for every additional zone your receiver has, up to four • Inputs and surround modes, selected by name instead of by button code • Quick Select and Smart Select presets • Channel levels - front, centre, subwoofer and surround, individually or linked • Audio options: Dynamic EQ, Dynamic Volume, Night Mode, Cinema EQ, tone control, Source Direct, Audio Restorer, Dynamic Bass Boost, sleep timer • Video options: video select, HDMI monitor, output resolution and HDMI audio routing • Tuner: frequency, presets, and DAB on the models that support it ON-SCREEN DISPLAY Browse what the receiver is playing from the phone instead of the TV: network audio, internet radio, USB and iPod, plus FM/DAB, XM and Sirius where the model offers them - including text search and jump-to-letter, which is far quicker than a cursor on the TV screen. MADE FOR DAILY USE • Macros: record a sequence of commands and replay it with a single tap • Rename inputs and zones so the app shows your names, not "CD" and "DVD" • Up to three receivers, switched from inside the app • An optional notification puts volume control in the status bar without opening the app • Your own background image, text colour and theme HOW IT CONNECTS Phone and receiver have to be on the same router. The app finds the receiver by scanning your network, or you enter its IP address yourself. The receiver's network function must be enabled - on many models "network standby" also has to be on, otherwise the receiver cannot be reached while it is switched off. Receivers without a network interface cannot be controlled at all. Nothing leaves your network. There is no backend and no account. SUPPORTED MODELS Denon: AVC-A1HDA, AVP-A1HDCI, AVR-100, AVR-990, AVR-991, AVR-1613, AVR-1713, AVR-1912, AVR-1913, AVR-2112, AVR-2113, AVR-2312, AVR-2313, AVR-3310, AVR-3311, AVR-3312, AVR-3313, AVR-3805, AVR-3806, AVR-3808, AVR-4306, AVR-4308, AVR-4310, AVR-4311, AVR-4520, AVR-4806, AVR-4810, AVR-5308, AVR-5805, AVR-E300, AVR-E400, AVR-X1000, AVR-X2000, AVR-X3000, AVR-X4000, DN-500AV, DNP-720AE Marantz: AV-7005, AV-7701, AV-8801, NR-1504, NR-1602, NR-1603, NR-1604, SR-5006, SR-5007, SR-5008, SR-6005, SR-6006, SR-6007, SR-6008, SR-7005, SR-7007, SR-7008 Experimental: Denon ASD-51 and RCD-N7, Marantz M-CR603, M-ER803 and NA-7004 Model not in the list? AVR-Generic speaks the common part of the protocol and usually covers power, volume, mute and input selection. OPEN SOURCE AVR-Remote is free software under the GPL v3. Source code, issue tracker and older releases: https://github.com/pskiwi/avr-remote This is experimental software - use it at your own risk. This application is not affiliated with Denon or Marantz. Denon and Marantz are trademarks of their respective owners.

First release: Aug 8, 2026, 2 total releases.

Most recent release: Sep 27, 2026.

Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Sep 27, 2026 1.7.0
    - **Updated for Android 17.** The app now asks for access to devices on your local network. Without it neither the receiver search nor the connection works (pskiwi) - If that access was denied, the hint about it and the new menu entry *Android app settings* lead straight to the page where it can be granted again (pskiwi) - **Mobile network:** without Wi-Fi the app no longer tries to reach a receiver outside your local network. If you control your receiver from elsewhere, over a VPN or a forwarded port, switch on Settings > Network Settings > Use mobile network (pskiwi) - Connections to the receiver go through the Wi-Fi even when mobile data is on (pskiwi) - The receiver search is much faster, works in networks larger than 255 addresses and no longer skips every 16th address (pskiwi) - When the receiver answers but its control connection is taken by another app or device, the app now says so instead of blaming the receiver (pskiwi) - A connection that silently dies is now noticed and re-established (pskiwi) - Fixed: after the app had been in the background for a while, the "Trying to connect" message could stay on screen for good and hide the hint about what is wrong (pskiwi) - Fixed a crash when the configured address belonged to another device instead of the receiver (pskiwi) - The receiver website opens the start page when the configured page does not exist on your model (pskiwi)
    More…
    - The network detection was rewritten. If the app no longer finds or reaches your receiver, please send feedback from the menu (pskiwi) - Feedback mails now include the most recent log lines, without switching on file logging first. They can contain what your receiver displays, such as track titles and searches - untick *Include recent log lines* to leave them out. You see the mail before it is sent (pskiwi)
  • Aug 8, 2026 1.6.1
    A bug-fix release. No new features and no new receiver models — three connection bugs and their fallout. Requirements are unchanged from 1.6.0: **Android 7.0 (API 24) or newer**. > The crash below takes the whole app down and is present in 1.6.0 **and** 1.5.1 identically, > so updating is worth it even if the rest does not apply to you. If something behaves oddly right after updating, pull the plug of the receiver for about a minute before reporting it — the receivers keep a stale control session otherwise. ### Fixed
    More…
    - **The app could crash when Wi-Fi was switched on or off.** `getNetworkInfo(TYPE_WIFI)` may return `null`, and that is exactly what the broadcast the app listens for reports — so it crashed on the event it exists to handle. Because it happened in a broadcast receiver, the whole process went, not just the screen. (@pskiwi) - **After a long standby the app came back disconnected** and stayed that way until it was closed and started again. Android delivers the queued screen-off broadcast to the frozen process on resume, which tore down the connection that resuming had just rebuilt. (@pskiwi) - **Returning to the app could freeze it for about a second**, because it waited for the reconnect thread on the UI thread. (@pskiwi) - **On four-zone receivers the zone 4 controls stayed active** after the connection was lost. Affects the AVR-5308, AVR-4308, AVR-4810 and AVR-5805. (@pskiwi) - **Reading the input names from a 2008-series receiver** could fail if the receiver answered with an unexpected page. (@pskiwi) ### Changed - **The on-screen display follows the device orientation again** instead of being locked to portrait. (@pskiwi) - **Logs sent by mail are considerably more useful.** They now carry the exception details, the thread that wrote each line, and a sequence number to sort by — line order is not event order. *If you have reported a problem before and it could not be reproduced, a fresh log is worth sending.* (@pskiwi) ### For developers The connection code now has a written reference in [CONNECTION.md](https://github.com/pskiwi/avr-remote/blob/master/CONNECTION.md) — the two transports, the reconnect loop, what Doze does to it, and how to read a log a user sent in. Test classes went from four to six, covering the reconnect thread's teardown and the status flags.