Files
proxmark3/client/src
Travis Weathers cce14d43e3 fix(client): stop the Indala demod printing a debug line at INFO level
detectindala() reports the bit count it gave up on through
PrintAndLogEx(INFO, ...), so every failed Indala demodulation prints

  [=] DEBUG: detectindala | 56

in normal output. It is the failure path: found_size < 64 means the
demodulator did not find a valid Indala (64 or 224 bits) and is returning
-5. Any noisy LF read hits it, so `lf search` with no card on the antenna
shows a developer's debug line to every user.

Every sibling in the same function already uses DEBUG, including the one
nine lines above it at "DEBUG: Warning - Indala had to invert bits", so
this is an oversight rather than a deliberate level. ui.c drops DEBUG when
g_debugMode is 0, which is the default, so the line stays available under
`data setdebugmode -1` and is simply no longer in the way.

Checked the whole client for the same class: the only other "DEBUG"
strings printed above DEBUG level are cmddata.c FSKToNRZ, and both of
those are already wrapped in `if (g_debugMode > 1)`, so they are correct
and are left alone.

Before, `lf search` over a reader field with no card:

  [=] Checking for known tags...
  [=] DEBUG: detectindala | 56
  [-] No known 125/134 kHz tags found!

After:

  [=] Checking for known tags...
  [-] No known 125/134 kHz tags found!

and with `data setdebugmode -1` the detectindala lines come back, now
carrying the [#] debug prefix like the rest of them.

Passes `make style` unmodified.
2026-09-15 10:57:02 -04:00
..
2024-04-22 09:21:55 +02:00
2026-06-29 22:42:37 +02:00
2026-08-27 14:25:40 +02:00
2026-08-29 17:42:29 +02:00
2026-09-14 22:18:27 +02:00
2026-09-03 02:08:30 -04:00
2026-09-15 14:39:14 +02:00
2026-07-28 15:53:20 +02:00
2025-09-20 12:32:03 +02:00
2026-06-30 02:29:57 +02:00
2026-03-24 20:21:51 +02:00
2026-09-12 16:51:53 +02:00
2026-09-12 16:48:51 +02:00
…
2025-07-13 11:29:29 +02:00
2026-09-01 17:57:31 +02:00
2026-08-29 17:42:29 +02:00
2026-08-29 13:50:49 +02:00
2025-06-30 14:28:24 +02:00
2026-02-27 20:26:50 +02:00
2026-08-29 17:42:29 +02:00
2026-08-29 17:42:29 +02:00
2026-09-12 12:38:05 +02:00
2026-05-25 20:52:51 +08:00
2026-05-24 19:12:12 +08:00
2026-08-29 16:42:01 +02:00
2026-03-14 17:34:58 +02:00
2025-02-18 18:41:09 +01:00
2026-08-29 13:50:49 +02:00
2024-02-01 10:05:04 +01:00
2026-08-29 13:50:49 +02:00
2026-09-14 12:11:42 +02:00
2025-08-28 04:06:57 -04:00
2026-03-29 09:39:42 +07:00
2026-05-24 03:33:38 -04:00
2026-08-29 13:50:49 +02:00
2026-05-29 12:36:50 +03:00
2026-05-24 03:33:38 -04:00
2026-09-14 22:27:31 +02:00
2026-09-05 05:40:45 +08:00
2026-07-15 16:39:15 +02:00
2026-08-29 13:50:49 +02:00
2025-08-28 04:06:57 -04:00
2026-07-15 16:39:15 +02:00
2026-03-30 22:58:52 +08:00
2024-05-14 10:04:28 +02:00
…
2026-09-12 12:49:17 +02:00
2026-08-29 13:50:49 +02:00
2026-09-01 17:57:31 +02:00
2026-08-29 16:42:01 +02:00
2026-09-12 16:48:08 +02:00
2025-07-08 21:15:09 +02:00
2025-07-10 11:52:39 +02:00
2026-06-29 01:57:19 +02:00
…
…
2025-07-10 11:52:39 +02:00
2025-07-08 21:15:09 +02:00
2026-09-12 20:56:08 +02:00
2024-01-18 16:21:01 +01:00
2025-07-10 11:52:39 +02:00
…
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-07-10 11:52:39 +02:00
2025-08-20 10:55:49 +02:00
2025-07-10 11:52:39 +02:00
…
add
2026-07-30 17:06:36 +02:00
2026-07-30 16:41:07 +02:00
2025-03-20 22:55:26 +01:00
2025-07-10 11:52:39 +02:00
2026-06-29 22:42:37 +02:00
2026-09-01 19:54:05 +02:00
…
2026-04-13 09:35:02 +02:00
2026-09-05 05:40:45 +08:00
…
2025-03-25 10:17:42 +01:00
…
2026-05-22 16:38:59 -07:00
2026-05-22 16:38:59 -07:00
2026-09-14 12:24:31 +02:00
…
2024-03-19 12:37:18 +01:00
2026-07-15 16:39:15 +02:00
add
2026-07-30 17:06:36 +02:00
2026-06-29 22:42:37 +02:00
2025-01-27 20:17:44 +01:00
2025-01-27 20:17:44 +01:00
2026-08-21 20:12:26 +02:00
2026-08-21 20:12:26 +02:00
2026-06-29 23:37:37 +02:00
2024-01-15 13:08:55 +01:00
2026-06-29 23:37:37 +02:00
2026-06-29 23:51:37 +02:00
2024-09-30 10:36:29 +02:00
2026-06-29 23:51:37 +02:00
add
2026-07-30 17:06:36 +02:00
2026-09-01 19:54:05 +02:00
2026-07-30 16:40:14 +02:00
2026-07-30 16:40:14 +02:00
2026-07-15 16:39:15 +02:00
2024-11-02 15:13:40 +01:00
2026-09-12 12:42:02 +02:00
2024-10-14 21:49:40 +02:00
2023-07-24 17:42:27 +02:00
2026-08-29 17:06:24 +02:00
2025-06-22 20:34:54 +02:00
…
…
2026-09-12 18:30:45 +02:00
2026-03-31 17:03:23 +03:00