[PEQHUB]

This bundles the rootless features I've been working on into one PR. It replaces #349 (low-latency mode and Android EQ), which is included here unchanged apart from dropping its measuring tools.

Per-channel PEQ needs a small libjamesdsp change: timschneeb/JamesDSPManager#6. The submodule is pinned to that commit. GitHub serves it through the existing .gitmodules URL, so the URL is unchanged. Merge the libjamesdsp PR first.

Low-latency mode (on by default)

Rootless capture added up to ~0.5 s of delay, so video went out of sync.

• Reads in 960-frame blocks instead of the whole buffer.
• Caps the output track queue and requests the low-latency output path.
• Drops a block (with a short fade) when the output queue grows past its target, so latency can't stay high after a slow start.

Bluetooth, cold start: A/V offset about 340 ms before, about 120 ms after.

Android EQ (off by default)

Instead of capturing, the GEQ/PEQ curve runs inside each app with Android's DynamicsProcessing effect, so video stays in sync. The curve is fitted to the effect's pre-EQ, MBC and post-EQ stages (up to 380 bands) against its actual block response. Left and right curves are applied separately. Settings: latency (~10/20/40 ms) and a limiter. Other effects are off in this mode.

Measured on the speaker with a mic: 10/21/42 ms added depending on the latency setting, and a -10 dB preamp comes out at -9.4 dB.

Live EQ

A bottom sheet on the parametric EQ screen for editing bands while listening: a logarithmic frequency slider, gain and Q controls, and chips to pick the band. Changes are saved when a slider is released.

Per-channel parametric EQ

Each band applies to both channels, left only or right only. The engine sends separate left and right curves to the stereo arbitrary EQ, and the preview draws both. Equalizer APO import and export use Channel: lines, so per-channel presets round-trip.

Song tonality analyzer (off by default)

A card on the DSP page shows how the music you play compares with a reference spectrum. It measures the captured audio before JamesDSP processing, per song.

• Songs are split by media session metadata (needs notification access), by silence, or by a lasting change of the spectrum.
• Seven bands (sub to air) are each judged against a normal range. The graph shows the deviation (compensated) or the measured spectrum (raw).
• A codec's cut-off and missing deep bass are detected and left out, instead of reading as a deficit.
• References:
  • IEC 60268-1 programme simulation noise (default)
  • M-Noise
  • pink noise
  • a tilt of -3 to -6 dB/oct
  • the average spectrum of popular music, and of its least and most percussive tracks (Elowsson & Friberg, AES 142, 2017)
  • an average learned from the songs you play
  • a custom reference: the playing song, or an imported WAV. The official M-Noise file is recognized by its checksum; the file itself is never bundled.
• It has its own settings page, which also opens from the card.

Testing

• Unit tests: Android EQ fitter, APO Channel: import/export, the tonality analyzer (reference feed-back, codec cut-off, missing bass, resets, bad input), reference curves against the IEC table, the resampler and the WAV decoder.
• On a OnePlus CPH2655 (Android 16): latency over Bluetooth and the speaker (numbers above), and the tonality card with streaming music.

[1576-del]

Title: JamesDSP Full ARM64 – Play Protect warning and user experiences

Hello PEQHUB,

I'm interested in testing your JamesDSP Full ARM64 build ("JamesDSP-Full-arm64-v8a.apk") on my Samsung Galaxy S26 running Android 17.

However, Google Play Protect blocks the installation with a warning about access to sensitive data and possible identity theft or financial fraud.

Before installing it, I would appreciate some clarification:

1. Has anyone successfully installed and used this exact APK?
2. Have other users encountered the same Google Play Protect warning?
3. Have users reported any security, stability, or compatibility problems?
4. Why is this APK signed with an Android Debug certificate rather than a release certificate?
5. Is there a security review or a reproducible build available to verify the APK?

I would also appreciate feedback from anyone who has personally tested this exact build, particularly on recent Samsung devices.

Thank you for your work and for any clarification.