yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] mawi29:
Just tested it in a parking garage. I drive in, the signal is gone, I press mute on my steering wheel, the display shows mute. After a few seconds driving in the parking garage the music starts playing again as soon as a bit of signal is detected, I keep trying to mute it, but it doesn't work because the signal keeps dropping and coming back, so as soon as I press mute, a split second later signal is detected and the music plays again. Very annoying.
[Android Head-Units] realzoulou:
Tested in my garage with a weak station. Simulated signal loss/regain by removing the antenna rod. Nothing happened, as expected.

@mawi29 I assume you have a launcher or some other app, which may react on DAB-Z's media metadata, which it broadcasts into the Android system all times when running. This app is then unmuting the system apparently.

Btw. Does Youtube or some other media player app show the same unwanted behavior?
[Android Head-Units] BruggC:
I do use the 1.9.117 awhile now and I'm satisfied with this apk. I did dive into the settings and came across a minor bug. Within the apk it should be possible to change the color of the radiostation. I changed the color pressed OK but nothing happend. Perhaps this can be changed in a new version
[Android Head-Units] IG_Vasilich:
@mawi29

i use this app several years and use underground parking garage, where the DAB signal drops on several places. Never seen this behaviour you have described.

I have old Joying HU, where mute/volume is controlled by MCU, so there is no way for any app to mute/unmute the sound. But on your place i would first install any intent monitor to check whether any app (or ROM itself) issues the unmute and play intents.
[Android Head-Units] escitalofreniko:
hello friends .. what article DAB, DAB + would be the convenient one to buy and work with the DAB Z software?
[Android Head-Units] rknuette:
Did you read the very first post in this tread before posting?
[Android Head-Units] escitalofreniko:
Yes, I have translated it. Thank you very much for passing me a link and / or helping me a little more by specifically recommending where, prices, etc., you are very kind!😒
[Android Head-Units] IG_Vasilich:
@escitalofreniko

use google and local online shops for it.
[Android Head-Units] escitalofreniko:
Thank you mate!!
[Android Head-Units] realzoulou:
@escitalofreniko Following 2 links point to Amazon Germany. You should be able to find such devices by searching for "DAB USB Android" in any marketplace, like eBay, Amazon, AliExpress, etc.

I usually do not give hints to such devices, because they are basically all the same, and the links to these items outdate within a month typically.

Car Kit Digital Audio Broadcast DAB DAB+ Box Empfängeradapter mit Antenne für Autoradio Android 5.1 und höher, Digitaler Radio Antennentuner UKW-Übertragung USB: Amazon.de: Elektronik & Foto

Car Kit Digital Audio Broadcast DAB DAB+ Box Empfängeradapter mit Antenne für Autoradio Android 5.1 und höher, Digitaler Radio Antennentuner UKW-Übertragung USB: Amazon.de: Elektronik & Foto

www.amazon.de

USB 2.0 Stick Empfänger, Digitalradioempfänger, Mitgelieferte Antenne, für Android, Unterstützung Automatische Lokale Suche RDS-Funktion DLS: Amazon.de: Computer & Zubehör

USB 2.0 Stick Empfänger, Digitalradioempfänger, Mitgelieferte Antenne, für Android, Unterstützung Automatische Lokale Suche RDS-Funktion DLS (Dynamic Label Service) - Kostenloser Versand ab 29€. Jetzt bei Amazon.de bestellen!

www.amazon.de
[Android Head-Units] realzoulou:
Thanks for noticing this problem. Indeed, I must have broken this some time back. I will this is a next release (no date planned yet)
[Android Head-Units] go-ran:
Is it possible to integrate clock somewhere in the app?

I am asking because when I use full screen I lose clock on upper right corner, and since it is only clock in car I am missing that information.

Thanks :)
[Android Head-Units] realzoulou:
Now it is getting weird... I can only reproduce this with my PX5 and PX6 devices, not on any other Android version and not on Android 10 Emulators. Don't know currently how to workaround this...
[Android Head-Units] it00x32:
First of all: Thanks a lot for your work!

i have a problem on my PX5 / Android 10 / V 1.9.117

After external apps reducing the volume (eg notification of my radar app blitzer.de or my app for my carplay connection - navigation informations) the volume stays reduced - i have to restart the app to have the normal volume output again (the 2nd volume slider isnt changing anything)
[Android Head-Units] realzoulou:
I use Blitzer.de (Pro version) myself and never faced this issue that DAB-Z ducks but does not un-duck after the audio of the other app finished. Note: This is steered by Android itself when to un-duck.

If the DAB-Z Audio setting "Sound volume in background" does not change anything, then you have most likely set an App as the "Navigation application" in Android settings -> CAR settings -> Navigation. If there is an App defined, then some MTC system app takes over Audio Session handling and DAB-Z not even gets notified about any other app becoming the foreground audio app. Thus, the volume level in DAB-Z settings is not getting effective.

Try with no app set in Android settings -> CAR settings -> Navigation. Does this change anything?
[Android Head-Units] realzoulou:
Since this is asked quite often in direct emails, too, I will include this in a next release.
[Android Head-Units] it00x32:
Thanks for your fast reply! I ve set the Navigation App and will try again without one
[Android Head-Units] it00x32:
still the same - can I debug anything?
[Android Head-Units] IG_Vasilich:
@realzoulou

if we are talking about ducking ... :)

I have following behaviour: DAB is set to reduce volume for ducking. But it unpauses itself after it was set to pause (manually) and navigation app said something.

Can someone confirm/contradict this? Is it intended behaviour?
[Android Head-Units] realzoulou:
Android's audio focus management is a "collaborative" one. This means it expects that Apps behave "nice" to Android (and therefore other Apps) and follow the Android documentation for "Manage audio focus": https://developer.android.com/guide/topics/media-apps/audio-focus

Expected behavior Ducking:

DAB-Z playing audio, other app starts a short-lasting audio output, DAB-Z ducks to the level configured in settings (default 50%), then other app stops audio, DAB-Z unducks.

Precondition: Some device specific system apps from MTC, FYT, etc. allow this behavior. Means: above applies only to a "near standard" Android device.

If DAB-Z previously got the pause command, it remains in paused.

Expected behavior Play/Pause:

DAB-Z playing audio, User pauses DAB-Z via a media control widget, launcher, from DAB-Z notification, etc. , then DAB-Z stops audio, other audio app can now output audio as long as it wants (ex. Youtube, Spotify, etc.). When User(!) brings DAB-Z to front and presses the big Play symbol shown "above" the logo, or is using media control widgets, launcher, etc. to command DAB-Z to play, then DAB-Z will continue to output the live DAB audio (no timeshift recording in the meantime). Other media player is expected to stop its audio output and decide by itself what to do now.

If during DAB-Z paused, another app does a short-lasting audio output (ex. Navi guidance), DAB-Z remains in pause (@IG_Vasilich : sic!).

If the above is not working as expected, it is likely an MTC, FYT, ... system app interfering with this standard Android behavior.

Expected behavior Mute:

DAB-Z playing, system wide Mute is triggered ex. via SWC, or volume control from status bar, etc., no audio output from any(!) app. Since Android 10, Android in parallel sends a pause command to the currently active audio source. Then User unmutes, (Android 10 sends play command) and DAB-Z is audible again.

If during Mute state, the User switches the audio source to any other app, then DAB-Z is not coming back of course when User unmutes.
[Android Head-Units] IG_Vasilich:
That means that if i am on Android 10+ and have DAB paused, then after unmuting DAB will start to play? and you cannot change this behaviour because you (DAB-Z) will get proper intents to play and cannot recognize whether those come from my widget/launcher or were generated by android?

Anyway, pls set this information you posted above on first post of this topic, so the people can easily find it. It is kinda technical documentation, and in some cases is very valuable.
[Android Head-Units] realzoulou:
No, if DAB-Z was paused, it must not un-pause. Irrespective of what happens.

In other words: your behavior on Intel Sofia Android 6 is wrong and not expected
[Android Head-Units] naira1:
Some new stations don't have logos and when i tried to search for logo using the suggested "VW station logo download", am not getting anything usable off Google. Can some one please point me in the right direction? Am looking for logos from Germany Preferably the NRW region.
[Android Head-Units] IG_Vasilich:
@naira1

there are many logos built in DAB-Z. If there are some logos missing - have you tried to activate RadioDNS logos?

If there are still some logos missing after it - make a list of it (exact names) and post here (or export station list and post the generated ZIP file here).
[Android Head-Units] naira1:
Thanks! These are the ones with no logos.

Antenne NRW

Energy NRW

Kiss FM NRW

NDR 1 OS

NDR 2

NDR blue

NDR Info NDS

NDR Schlager

Radio Holiday

Radio teddy NRW
[Android Head-Units] IG_Vasilich:
@naira1

here they are
[Android Head-Units] naira1:
Awesome. Worked like a charm. Thanks mate.
[Android Head-Units] neo61uk:
Hi all

Just installed latest version of 1.9.117 on my headunit. My old one was 4-5 months old so not sure what version exactly. But it used to start on every usb detection upon boot.

But now it won’t do that.

I have to manually start it every time.

Any idea why it won’t start even when selected in settings?

Thanks for help
[Android Head-Units] BruggC:
Thx!
[Android Head-Units] realzoulou:
@BruggC I hope you had also seen this post. Means: I will not be able to fix it.
[Android Head-Units] realzoulou:
Done.
[Android Head-Units] bigburd05:
Hi,

Having trouble with my USB DAB+ on XTRONS PX5 unit (model PB78HGT)running Android 8. It's been working for 3 years but now failing every time I start up the DAB Z app with "No dab usb hardware". I've checked the USB cable, and it is ok with a memory stick (can browse files with ES file Explorer app). I swapped the USB cable with a new XTRONS USB cable, same result. I also swapped the DAB dongle (USBDAB01) with a new dongle with its own antenna (USBDAB03) and it failed the same way. I updated DAB Z app to the latest version too, same result, although it's a little more verbose about the 5 attempts it makes to connect.

I was going to follow the instructions on the original post on this thread to set up logging on the DAB Z app, but I can't get to the settings of the app, because it exits as soon as it displays the "no DAB USB" error.

Can someone advise on next steps for me, please?

Is there another way to set up DAB Z to log details or not to exit on that error, or some other way to understand the reason for the error?

Does the Android USB mode need to be set to some specific mode to work for DAB?

Is it likely I have a hardware issue with the USB socket on the head unit?

Cheers

Iain
[Android Head-Units] realzoulou:
@bigburd05 : If a USB memory stick is working fine, then it means that:

1. USB mode is already setup correctly: Head Unit is the host, USB DAB adapter is the device.

2. "In principle" all involved HW is doing ok: USB host controller within the HU, USB cable/plug from HU to DAB device.

Android logs of DAB-Z will not help. Save your time for sth else.

Questions:

a) On SW:

- Have you installed any app at the time when DAB-Z started failing to find the DAB adapter? If yes, which ones.

- Do you use any "Projection" App (like ZLink, Apple CarPlay, Android Auto), which allow you to bring the phone's screen onto the HU display?

b) On HW:

Have you tried using a USB hub in between HU and USB DAB adapter?
[Android Head-Units] IG_Vasilich:
c) have you tried to connect (temporarily) DAB hardware to your smartphone or tablet? Will DAB-Z on phone recognize that stick?
[Android Head-Units] bigburd05:
Thanks for the replies and suggestions guys. I've tried as best i can to follow up...

* I don't recall any app installs at the time it started failing - the only install I've done is after it started to fail I updated DAB Z to latest (1.9.117)

* I don't use any projection or mirroring apps. I have started using the A2DP app to stream music from my phone to the head unit while I cannot use DAB Z.

* I use CarWebGuru as my launcher for the head unit.

* I have used ES File Explorer a few times - I wonder it is plays with the USB settings at all that might upset things for DAB?

Yes, had a hub in between originally. Removed it (still worked). Have tried both with and without since it started failing, without success.

I tried, but my Samsung s10 is awkward to get to USB settings. I had to enable developer mode and it still wouldn't offer me options very easily.

I now have two DAB adapters. The original USBDAB01 (UAB A connector) is still fitted to the car and HU and a new USBDAB03 (USB C) connector which is not connected and which I tried when the original setup started failing (thinking the adapter was the fault). The USBDAB03 has a red light on the adapter (whereas USBDAB01 has no indicator of any kind), which lights up when I connect it from my phone (nice positive sign that "something" is working, maybe!), but when I start the DAB Z app with my phone , it fails with "No DAB USB Device" the same as for the HU setup etc. I tried fiddling with the USB settings on the phone, for example,

1. set to USB mode = MIDI. Made no difference - still just seems to be in charge mode. Also tried setting to File Transfer etc, but no difference.

2. setting the phone to be the controller (default seems to be the device as controller), but it always fails to change to make the controller the phone (the phone gives me an error changing and reverts to the device as controller).

I also tried using a hub between phone and DAB adapter but this failed the same way (red light on, but DAB Z fails to connect on startup).

I tried the USBDAB01 in the car connected to my phone (with, and without a hub in between) and DAB Z fails to connect on startup as per usual

I tried connecting the USBDAB03 to the head unit (with, and without a hub in between) , and I don't see the red light on the adapter (and DAB Z fails to connect on startup).

I kinda think the way the samsung s10 setup hides the USB functionality is a bit of a barrier to using it to test the dongle (unless you guys know how to set the phone up reliably).

My unit is installed with the following (might be a bit old - have not changed this in a while)

Model is: PB78HGT Android 8.0.0

ROM: 4.4.93+ rocky@hctr930 #319 Sat Jun 9 2018

build Number px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180703.094228 test--ke....

MCU: MTCE_GS_V2.90c_4 Aug 13 2018 17:42:12

Any more ideas?

Cheers

Iain
[Android Head-Units] smilie1964:
Try with an active hub. Maybe the USB Power is to less.
[Android Head-Units] Th0m4s88:
I found a small problem with a relatively new android 10 px5 head unit.

MCU: SF0-px5_C55_whd01a-aAaAaA_C8_20201202-10:45

When the head unit shuts down and wakes up again DAB-Z seems to have problems receiving signals from the DAB stick. There's no error message but the app shows no signal from all the radio stations. As soon as I restart DAB-Z everything is back to normal and all the radio stations have good signal strength again.
[Android Head-Units] bigburd05:
OK, folks, I had to get some cables and adapters to try the next steps but it's still failing. I have tried:

(new )USBDAB03 adapter attached through powered USB hub and hooked up to my existing roof antenna (needed an MCX to SMB adapter for that) and the red light comes on on the USBDAB03 dongle (power indicator, I guess?), but when I start up DAB Z it goes through its 5 attempts to connect, but fails in the usual way ("No DAB USB device").

Having tried hooking up the dongle to my Samsung S10 phone, I'm a bit reluctant to continue with that option, as the phone USB settings seem so difficult to manage.

I'm a bit stuck again. Is it time to consider a factory reset on the HU, or an update to MCU or system? Any other ideas before I start down that route? Reluctant to do that as it takes a while and drains the car battery while it's in progress.

Cheers

Iain
[Android Head-Units] realzoulou:
This is reliably showing the issue! Your head unit does not power the DAB USB adapter. That's strange because you wrote previously, that a USB memory stick is working fine. Did you for sure use the same USB port?
[Android Head-Units] bigburd05:
HI, Thanks again. Yes, I only have one USB socket wired in to my XTRONS currently, and it successfully allowed the USB memory stick to work but did not power the USBDAB03 dongle when wired directly. If I am using a powered hub, as suggested by another forum article, I see the power light on USBDAB03 dongle working ok, but still, there is no connection when starting DAB Z. Should the connection work if the power light it on, or is the hub a potential barrier to the DAB functionality/connection?

If DAB reception is poor at the time, would that show this behaviour, or is connection independent of reception?

Cheers

Iain
[Android Head-Units] realzoulou:
Hi Iain, a powered hub provides 5V to all attached devices from its own power supply. Such USB hubs are also called "active". Without a powered hub, the 5V are supplied by the host (=HU). 5V alone does not do much, it only allows the device to be charged (of course DAB adapters cannot be charged). When 5V are present, then the host polls all the devices periodically using the data lines (D+ and D- when USB 2.0).

The DAB signal strength ("DAB reception") does not have any influence at all on the USB connection.

So... you wrote previously that a previous version of DAB-Z has worked well. Just after the update to 1.9.117, the issue started, right? Try older versions from apkpure going backwards.

I suggest trying in this order: 1.9.110, 1.8.105, 1.8.96
[Android Head-Units] NogenLunde:
Make sure USB Host is selected in the settings of your HU.
[Android Head-Units] denization:
i know i cannot provide a lot of information, but im curious about the overall picture. maybe someone has a clue. is a non-functioning SWC related to DAB-Z or my OS? the SWC used to work with DAB-Z until some point last year and then stopped working. dont know if its due to an OS update or app update. for other 3rd party music players the SWC still works. regards
[Android Head-Units] bigburd05:
Hi, thanks, that sounds worth a check. How to I find the settings for "USB Host" in the HU? I checked the developer settings for USB Mode but that offers me Media Transfer Protocol (selected), Picture Transfer Protocol, RNDIS (USB Ethernet), Audio Source, MIDI and Charging. Does one of those imply USB Host, or is the setting exposed somewhere else? My HU is running Android 8
[Android Head-Units] NogenLunde:
Depends on your unit, of course, on my Android 9/10 KSW SnapDragon unit (not in the Android specific settings): Factory Settings, Function, USB-Host.
[Android Head-Units] Max-Rockatansky:
I'm following this with interest...

I have an xtrons PB80UNV running the standard firmware that it came with, and fairly regularly when starting dab-z it fails to find the USB device - it tries 5 times (I think) and then says 'no dab usb device' and closes.

Sometimes it works, sometimes it doesn't, there doesn't seem to be any pattern. If I hard reset the unit it all works fine. Until next time....
[Android Head-Units] bigburd05:
Thanks. There's nothing in my factory settings for USB host. When I type in my pass code at factory settings, there's a ton of settings arranged in tabs but no USB Host settings as far as I can see. Think this is the XTRONS skin on top of Android 8. I'd read that there's an XML file I can look for in protected folders to indicate USB host being set but think it's protected and only accessible while USB debugging, which seems tricky. Any other ideas? Getting close to doing a factory reset but not keen to have to the install all the other apps all over again.
[Android Head-Units] Zabzd:
Good day.

I sending some information to "Service Following"

1. After SF, information about the original channel 12C will remain on the information screen, see figure. I'm in an area where there is no "12C" signal and auto-tuning to "12D" has taken place.

2. In the event of a signal failure, "SF" often does not turn on automatically to retune the station to another frequency. I have to go to DAB-Z and run "SF" manually. in Settings I have "sensitivity - 9"

3. See point 2. I would like to ask you if the information on "automatic scanning" could be reported in the field "Text Dinamic Label Segment DLS", I would also have the information in "Car Launcher"
[Android Head-Units] bigburd05:
Folks,

Just for closure, and to offer many thanks for all the suggestions and help given in this thread, my DAB is now working again!

Turns out the original problem was a broken USB connector in the original XTRONS USBDAB01 dongle.

The secondary problem was that the new USBDAB03 dongle from XTRONS has too high a power requirement to allow it to be powered from the XTRONS head unit's USB socket (and I could find a suitable/convenient powered hub set up to mitigate / test that).

Managed to get XTRONS customer service to suggest strongly enough that the USBDAB03 power requirement might be too much for the socket and send that to the retailer who agreed to provide an older model USBDAB01 dongle, which works perfectly!

Many thanks for all the help; if nothing else I've learned more about USB configuration and have now updated my DAB Z app version which is an improvement over the version I had been running. All good!

Cheers loads!

Iain
[Android Head-Units] BruggC:
Ok, it would be nice, but it's just a minor issue.
[Android Head-Units] HMT06:
hello, the following service does not work. I just downloaded the latest version 1.9.117 on an android 11 unit, Snapdragon 662, the app works fine but when I click on the SF symbol next to the station list, a window pops up and says: Service following currently not possible! I previously used a Pure Highway 400 usb adapter which worked perfectly in following service. Do you have an idea ? Excuse me for my English.. Hervé
[Android Head-Units] NogenLunde:
What is your current adapter? Not all DAB adapters support service following.
[Android Head-Units] HMT06:
Hello, the receiver is the Neotone DRB-100X GEN3, the latest generation. I was in Switzerland yesterday and the SF function was working! I specify that I usually live in France. All the French transmitters would be in question? Technically, how do the usb dab adapters that I used previously work? (Pure highway 400). Do they have a "service following" function or do they proceed differently? Finally, I use a company car equipped with a dab plus receiver which works perfectly in frequency following when I travel. (Renault Zoé). Are there any other technical solutions for memorizing the list of alternative transmitters of the same multiplex?What is the use of the dablib.so function, I have not found any clear explanations! Thank you for your insightful responses. Herve