AbracaDABra - multiplatform DAB SDR for RTL-SDR USB sticks and other devices

[KejPi]

AbracaDABra 3.99.0 (4.0.0 beta 1) has been released

After almost half year of development I am proud to announce a first public release of the application with brand new UI and Android support.
There are almost no new features, but everything in UI has been redesigned from the scratch so problems and bugs to be expected. Be nice!
It is highly recommended to backup current settings and service list before experimenting with this version. Feel free to report any problem you will find.

Changes:

• fresh and modern UI based on QML
• single window design but most of the views can be detached to separate window (use Cmd+Click/Ctrl+Click on left navigation bar or button in the view to detach the window)
• all files are stored in subfolder to the location that you can select in Settings -> Others
• minimum Qt version is 6.7
• Android build available (Android 11 or newer, arm64-v8a required) - this is more like alpha version, be careful

Note: AppImage for Linux AARCH64 is compatible with 64bit RaspberryPi running Debian 12.

You can download binaries here: https://github.com/KejPi/AbracaDABra/re ... ag/v3.99.0
Arch Linux users can install AbracaDABra from AUR
If you have any problem please report here or enter new issue on GitHub

[andimik]

The Android version does not seem to load the rtl-sdr driver from Martin Marinov. But I can see the stick in the list.

Code: Alles auswählen

23:22:19.018 [I] Application: Version: v3.99.0
23:22:19.022 [I] qt.multimedia.ffmpeg: Using Qt multimedia with FFmpeg version 7.1 LGPL version 2.1 or later
23:22:19.026 [I] Application: Audio output: Qt
23:22:19.032 [I] RtlSdrInput: "Realtek | RTL2838UHIDIR | SN: unknown"  |  "Realtek:RTL2838UHIDIR:0bda:2838:unknown"
23:22:19.032 [I] Application: Proxy config: No proxy
23:22:20.122 [I] Application: Application state changed: Qt::ApplicationActive
23:22:20.122 [I] Application: Application active - audio continues playing
23:22:21.207 [C] RtlSdrInput: Failed to get USB file descriptor from Android
23:22:21.209 [I] RtlSdrInput: "Realtek | RTL2838UHIDIR | SN: unknown"  |  "Realtek:RTL2838UHIDIR:0bda:2838:unknown"
23:22:32.441 [I] TII: TX database items loaded: 5396
23:22:32.958 [W] default: QGeoTileProviderOsm: Tileserver disabled at  QUrl("http://maps-redirect.qt.io/osm/5.8/satellite")
23:22:32.958 [W] default: QGeoTileFetcherOsm: all providers resolved
23:22:49.297 [I] TII: TX database items loaded: 5396
23:22:49.299 [I] TII: LocationPermission Granted
23:22:49.307 [I] TII: Location source system
23:22:49.585 [W] default: QGeoTileProviderOsm: Tileserver disabled at  QUrl("http://maps-redirect.qt.io/osm/5.8/satellite")
23:22:49.586 [W] default: QGeoTileFetcherOsm: all providers resolved
23:22:49.586 [W] default: QGeoTileProviderOsm: Tileserver disabled at  QUrl("http://maps-redirect.qt.io/osm/5.8/satellite")
23:22:49.586 [W] default: QGeoTileFetcherOsm: all providers resolved

Maybe this helps: https://github.com/signalwareltd/rtl_tcp_andro-

I also tried a (no more published) beta from welle.io, this is working.

But good news: raw files can be loaded into AbracaDABra, TII and SPI (incl. logos) do work as well.

[KejPi]

Android version does not use that driver, it has its own driverfor both RTL-SDR and Airspy. Make sure that the driver is not running.

[andimik]

Ah, interesting. Ok, I will try in the evening again.

[andimik]

It only works with a very old stick with E4000 tuner, so I have poor reception.

The very common nooelec sticks cannot be connected. Seems your driver doesn't support them yet.

[KejPi]

It supports all sticks I have at home, that includes Nooelec with E4k tuner, RTL-SDR V3 and V4 and Airspy mini. Application on Android uses more or less the same driver as desktop application.

It is interesting that there is unknown SN, I have never seen that with any RTL-SDR device I have ever use on desktop.

EDIT: Adding few screenshots

[cazian]

Thanks for uploading an alpha version for use on Android, I was excited to try this out, as it would be great to not have to lug around a laptop if using the software whilst out mobile.

First impressions are that it's working very smoothly on my phone, being fed with an RTL-SDR v3. The phone is a Motorola Moto G55 with 8GB of RAM sporting Android 15.

Just a couple of issues so far:

(1) I can't work out how to save my co-ordinates manually under the TII tab in the settings. I enter my co-ordinates, in exactly the same format as in the PC version and hit the return key on the Android keyboard. I can't see any save button. But, if I come out of the settings and into one of the other screens and then return to the TII tab under Settings, the co-ordinate values have reverted to 0, 0. Maybe I'm doing something wrong, rather than this being a bug.

(2) A couple of times, when I reopened the app, the display was corrupted. Force closing the app and clearing the cache fixes the display issue. I think this may have happened when the RTL-SDR disconnected, as the connection was a bit dodgy, but I'm not certain, but I can't replicate it on retrying.

[cazian]

Replying to myself, I've realised I can get the "auto" setting for location working, but I had to set the location permission in Android manually. The location permission was set to "not allowed" by default.

[KejPi]

Replying to myself, I've realised I can get the "auto" setting for location working, but I had to set the location permission in Android manually. The location permission was set to "not allowed" by default.

I have borrowed very old Pixel 3a and I purchased Samsung Galaxy Tab A11 for development and in both cases the system asked me to approve permissions when I entered map page (TII or scanner) when location was set to System. Entering the coordinates is probably a bug, I have not tested that on Android, I am even not sure this option makes sense.
And regarding the visual corruption, I am afraid there is not much I can do, perhaps only upgrading to Qt 6.10 to see if it helps, currently application on Android is built with Qt 6.8 LTS

EDIT: TII coordinates bug will be fixed in next build

[cazian]

Replying to myself, I've realised I can get the "auto" setting for location working, but I had to set the location permission in Android manually. The location permission was set to "not allowed" by default.

I have borrowed very old Pixel 3a and I purchased Samsung Galaxy Tab A11 for development and in both cases the system asked me to approve permissions when I entered map page (TII or scanner) when location was set to System. Entering the coordinates is probably a bug, I have not tested that on Android, I am even not sure this option makes sense.
And regarding the visual corruption, I am afraid there is not much I can do, perhaps only upgrading to Qt 6.10 to see if it helps, currently application on Android is built with Qt 6.8 LTS

Strange that I didn't get a prompt, asking to grant the location permission. I only tried the manual co-ordiantes option, as system didn't seem to work initially, but that was before I realised that the location permission was set to not allowed. Auto makes more sense, as it should always be correct if you're using it mobile and your GPS is working on your phone. I haven't seen the display corruption again, by the way.

[andimik]

Well, all my sticks work with AbracaDABra under Windows and Linux. So I don't think the driver for Android is the same, but you should know better...

I'll try to set a s/n with

Code: Alles auswählen

rtl_eeprom -s 00000001

[pomnitz26]

The Android version works for me on everything I could find, including my tablet. I'm not entirely sure about the Windows PC version, as the old one also works very well. Depending on the screen resolution, the new version doesn't adjust properly in some windows, and some windows are too large; they can't be made smaller. On my phones and tablets, I plug in the RTL SDR V4, and it automatically asks whether I want to open AbracaDABra or the SDR driver for Welle i.o. What's missing on Android and Windows is that the TII locations remain grayed out when the signal is lost. AbracaDABra runs on Android with just as good a signal as on Windows. With Welle i.o., it was unusable. On my Redmi Pad, I can easily operate the window on the right with the ensembles (DR Germany, Antenne DE, etc.) manually, but with the Bluetooth pen, the windows are very difficult to open and close; they keep jumping around.

Are there any plans for a TII distance display in the future, where you can see if a location is offset by 30 km? Otherwise, it's really well done; battery consumption is acceptable, neither the tablet nor the phone gets hot, and nothing crashes. Mobile use in the car with the magnetic antenna is still pending.

[andimik]

The command

Code: Alles auswählen

rtl_eeprom -s 00000002
Found 1 device(s):
  0:  Generic RTL2832U OEM

Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner

Current configuration:
__________________________________________
Vendor ID:		0x0bda
Product ID:		0x2838
Manufacturer:		Realtek
Product:		RTL2838UHIDIR
Serial number:		00000001
Serial number enabled:	yes
IR endpoint enabled:	yes
Remote wakeup enabled:	no
__________________________________________

New configuration:
__________________________________________
Vendor ID:		0x0bda
Product ID:		0x2838
Manufacturer:		Realtek
Product:		RTL2838UHIDIR
Serial number:		00000002
Serial number enabled:	yes
IR endpoint enabled:	yes
Remote wakeup enabled:	no
__________________________________________
Write new configuration to device [y/n]? y

Configuration successfully written.
Please replug the device for changes to take effect.
Reattached kernel driver

has solved my issue, now the nooelec will also work.

The S/N 00000001 will NOT be accepted by the Android version of AbracaDABra (but it works under Linux and Windows).

[KejPi]

The command

Code: Alles auswählen

rtl_eeprom -s 00000002
Found 1 device(s):
  0:  Generic RTL2832U OEM

Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner

Current configuration:
__________________________________________
Vendor ID:		0x0bda
Product ID:		0x2838
Manufacturer:		Realtek
Product:		RTL2838UHIDIR
Serial number:		00000001
Serial number enabled:	yes
IR endpoint enabled:	yes
Remote wakeup enabled:	no
__________________________________________

New configuration:
__________________________________________
Vendor ID:		0x0bda
Product ID:		0x2838
Manufacturer:		Realtek
Product:		RTL2838UHIDIR
Serial number:		00000002
Serial number enabled:	yes
IR endpoint enabled:	yes
Remote wakeup enabled:	no
__________________________________________
Write new configuration to device [y/n]? y

Configuration successfully written.
Please replug the device for changes to take effect.
Reattached kernel driver

has solved my issue, now the nooelec will also work.

The S/N 00000001 will NOT be accepted by the Android version of AbracaDABra (but it works under Linux and Windows).

As you can see in my screenshots above, S/N: 00000001 is accepted on Android. I do not know what was wrong with your device, but I am pretty sure, the problem is not SN 00000001 because almost all of my RTL-SDR have this serial number as it is default SN unless you change it manually like you did.

[KejPi]

Depending on the screen resolution, the new version doesn't adjust properly in some windows, and some windows are too large; they can't be made smaller.

What windows? Be specific, some of them can be made smaller whne they are detached. My intention was to keep the same minimum size as before. And what is your screen resolution?

What's missing on Android and Windows is that the TII locations remain grayed out when the signal is lost.

This bug has been addressed already and will be fixed in next beta build.

On my Redmi Pad, I can easily operate the window on the right with the ensembles (DR Germany, Antenne DE, etc.) manually, but with the Bluetooth pen, the windows are very difficult to open and close; they keep jumping around.

Sorry, I do not undrestand this comment.

Are there any plans for a TII distance display in the future, where you can see if a location is offset by 30 km?

What do you mean? What kind of offset?

Please feel free to enter issue on GitHub where we can have more focused discussion about the problems you are facing, you can also record your idea for the new feature there.