[Android Head-Units] realzoulou:
Last updated: 2023-10-28

DAB-Z v2.x thread is here

This thread is discussing the (now old) DAB-Z v1.x versions...

Release notes of last v1.x release 1.9.127

If you want to become beta user, subscribe in Google Play or open this link from the device : https://play.google.com/apps/testing/com.zoulou.dab

The app is available in Google Play named DAB-Z with package name "com.zoulou.dab".

It can be installed in parallel to any original preinstalled DAB+ Player.

Get DAB-Z on Google Play

Get previous versions on Apkpure

Compatible devices:​

all DAB USB dongles with VID/PID = 16C0/05DC (decimal 5824/1500) ("VOTI", "Van Ooijen Technische Informatica", "shared ID for use with libusb", "wshtyr@126.com")

Examples

(for sure not complete!)

XTRONS USBDAB01

Joying DAB+

Pumpkin Y0251

Hotaudio Dasaita DAB+

(and dozends or hundreds more, they are all quite the same, if not equal.)

Use this link to find out more

NOT SUPPORTED:​

* Any SDR ("Software Defined Radio") devices (e.g. based on Realtek RTL2832U R820T)

* Fulljoin adapter

* Dension DAB+U

* Dasaita DAB box

Frequently asked questions FAQ:​

DAB-Z's expected behavior regarding Play/Pause, Mute/Unmute, Navi App announcements

Q: Does DAB-Z support fallback to FM Radio?

A: No and it is not planned due to technical reasons.

Q: Why do some stations appear several times in the list but have all the same content?

A: This is an annoying behavior of the broadcasting stations. DAB-Z does not lump them together to give the user the choice to pick one into the favorites list that has the best signal strength.

Q: Is it possible to add a sort of buffer to bridge short reception outages and therefore interruptions of audio, e.g. while driving through a tunnel?

A: No. DAB is a real-time, live (but digital) broadcast (same as old-style TV and FM radio), in contrast to streaming. The broadcasted data that is lost due to missing reception cannot be recovered or re-requested later. Also, DAB cannot be read-ahead in contrast to streaming. An app therefore cannot create a buffer of "future" data in order to have data locally, which can then be used to bridge the loss of reception.

For testers ...​

... that want to

actively

support me and help everyone to have a better DAB-Z app:

If you encounter an issue with DAB-Z, I will maybe ask you to provide a) logcat logs or b) raw recordings.

a) logcat logs are created by pressing the logcat button in DAB-Z Settings -> Info (at the very bottom)

A zip file is created and you will be able to choose what to do (send via Email, add to Google Drive, etc...). Get this zip file to me somehow.

If I additionally ask you to enable "OMRI verbose logging", then follow these steps before creating the logcat as above:

1. Enable Developer Menu: tap 7x on DAB-Z Settings->Info->Version , then go back, a new menu item appeared "Developer options" at the very bottom

2. Enable OMRI verbose logging

3. Close DAB-Z

4. Reopen DAB-Z

... reproduce the issue ...

5. Create the logcat DAB-Z Settings -> Info (at the very bottom)

b) raw recording are created by this procedure:

raw recordings are done using this procedure:

1. Enable Developer Menu: tap 7x on Settings->Info->Version , then go back, a new menu item appeared "Developer options" at the very bottom

2. Enable OMRI raw recording (you don't need to activate verbose logging)

3. Close DAB-Z (raw recording enable/disable requires a restart of DAB-Z)

4. Reopen DAB-Z

... reproduce the issue ...

6. Go to DAB-Z Settings and disable OMRI raw recording. Restart DAB-Z again.

Afterwards, files with ending .raw exist in:

<internal memory>/Documents/DAB/rec/

Download them all from the head unit, zip them and send to me.