yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Gregor.poetzsch@gmail.com:
Hello folks,

Thx for all the details,

I think current handling of service following is based on some misunderstanding of DAB Spec an interpretation of the rules of implementation. Basically there are implicit and explicit linking.

Explicit linking is signalized by FIG0/6 service link. As dab to dab or dab to FM hard and soft links. Both exist in national an international version and can be activated or deactivated by link actuator. But there is also implicit linking which compares ECC of ensemble or service, Sid and acid and or scids and uses following Rules to find same Service relationship.

1. ECC , EID, SID AND SCID is the same but transmitted on different frequency.

2. ECC SID AND SCID are same only Eid is different.

Important to know ECC can be transmitted on ensemble level and also on optionally on service level with cross country distribution like radio Maria or Bayern 3 in south Tyrol .

I hope this helps why pure dab highway is able to support service following if not fig 0/6 is transmitted.
[Android Head-Units] pin1904:
Hi, thanks for your response, but unfortunately simple gallery, at least that one I've tried (Simple Gallery), doesn't work either. I've talked to Zoulou and he mentioned that the problem might be that I'm using an Android 11 device which came without any "factory" image picker and the Simple Gallery isn't optimized for A11.

Does anybody know an image picker app for A11?
[Android Head-Units] okij:
Total Commander
[Android Head-Units] blackmike:
Jello , is there a way to run sab-z on a klyde headunit with internal dab tuner? Or a versionof dab-z?

I find the dab-z app better than the original.
[Android Head-Units] realzoulou:
Only USB connected DAB adapters are supported as described in post#1
[Android Head-Units] rigattoni:
Ignore the installed DAB receiver and just buy an USB one. That enables you to run DAB-Z.
[Android Head-Units] blackmike:
Ok. Thats not that what i want to hear....the internal tuner is not bad.. can you tell me which one is a good dab tuner ? The internal dab must be disabled? If yes , how to do?
[Android Head-Units] rigattoni:
Just have a look aat the first posting in this thread.

There are a lot of different and nearly the same in different covers.

You don´t need to deactivate anything, cause the related SW is not present. Just attach the new receiver to the USB and install DAB-Z. That´s it.
[Android Head-Units] blackmike:
Ok. Thank you very much
[Android Head-Units] Anton TNT:
Hi realzoulou .

Just one small problem to address to for all users here including you.

This DAB-Z app is having a problem on my HU. It works fine as app but...

I have noticed that this DAB-Z app cause a interference with radio app specifically with 8227L motherboards.

I have ALPS F5000 device with Android 10 (fake Chinese 8) - build: CHS.8227_8_UI4_Android 10.

Namely, when you install new firmware on the 8227L platform, everything works ok (meaning for ALPS, JUNSUN, XTRONS, MEKEDE, A1 etc.), but when you log in to the GOOGLE PLAY STORE and download the DAB-Z app and install it, it's there application interference occurs. I don’t know why but it just freezes my radio app after the engine shuts down and is idle. After restarting the engine the radio app simply freezes and will not return or work again until I reinstall the firmware from scratch. How does this affect the operation of radio tuners and what is the problem? What it needs to be done here to resolve this ?

P.S: Also noticed that problem maybe lies in app settings "on top of other app".
[Android Head-Units] pin1904:
Unfortunately TC doesn‘t work either.. I think I have to wait for another solution, hopefully Zoulou finds a way to fix. Until then i‘ll stay with my workaround to use an older Release, customize the look, Update, and then never touch this menu again 😅 but thanks anyway ✌🏼
[Android Head-Units] sat_rik:
Hey everyone,

how is the current state of the "app asks for usb permissions dialog popping up on every start"?

I found some posts here, but they are more than 1 year old and on my HU I get this dialog on every start.
[Android Head-Units] realzoulou:
@sat_rik Status since years is that DAB-Z has all support for USB permission dialog implemented. A one time USB permission popup dialog is normal. When you set the checkbox in the dialog, then your device should never ask again.

If you device nevertheless asks again and again, contact your seller. It is an issue in your device, not in DAB-Z.
[Android Head-Units] sat_rik:
@realzoulou trank you for the explanation :)
[Android Head-Units] realzoulou:
DAB-Z release 1.9.121 BETA

Change log:

compared to 1.9.119

* New: Settings Button on Splash screen

* Fix: Android 11 background image not selectable

* Fix: Android 11 storage permission dialog skipped automatically

* Removed legacy libdab.so

* Removed pre-Android-6 deprecation dialog

As announced with 1.9.119, this is the last (planned) release for the 1.9.x line.

libdab.so is gone. No option to choose anymore.

Non-OMRI users will find their station list empty after the update.

Farewell to Android 4.4 and 5.1 users

This is the last version of DAB-Z, which your device will be able to update to.
[Android Head-Units] gibbylinks:
Hi, installed my new Android 10 head unit at weekend. Tried DAB+ which came with it, then installed your DAB-Z, Thank you for your work, it's a much nicer interface and feels more polished.
[Android Head-Units] shzlmnzl:
cheers.

stupid question: where i can find older versions?

.117 oder .118

because i have some issues at the moment.

I use FCC Launcher and on the start screen some widgets from FCC to show the radio sation picture and track/perfomer names...

unfortunately at the moment it will not updated both if i change the radio station.

only if i reboot the whole radio unit, then it will work as long as i shut off the radio with ignition (deepsleep)...

then it will no more update the radio station picture and don´t show the track name... until i reboot the radio unit.

and so on...

i tried several older FCC versions with same issue.

DAB-Z is at the moment the .119 version so i will try an older version because it worked in the past :)

(i haven't tried yet the verion .121)
[Android Head-Units] ndev2k:
I've recently installed a new head unit into my car. PX5 based.

I use Agama Car Launcher and DAB-Z. Latest stable version.

For me the audio ducking does not work. Whilst using DAB-Z and my Speed Play (Apple Carplay) app the audio does not duck during navigation, reading messages or using Siri.

I have tried changing the audio channel that DAB-Z used from media to navigation, unknown etc but it is still the same.

Can anyone help with what I need to do?

I can provide any further information that may help if you let me know what is required.
[Android Head-Units] kc1:
Hi - I have this DAB receiver https://www.amazon.co.uk/dp/B09VBS6TNW (branded "Hikity")., which works only in the head unit's 6-pin USB socket. (which unfortunately I need my phone to work with Android Auto). Do all USB DAB receivers need a 6 pin socket (actually I think only 5 are used), with the extra OTG wire? If so there any HUB that will let me use the DAB and phone at the same time?
[Android Head-Units] IG_Vasilich:
can you make a picture of your 6-pin USB socket?? standard for USB2 (all DAB adapters use this version) has only 4 contacts - +5V, GND, Data+, Data-. There is neither 5th nor 6th contact in USB2 specification.
[Android Head-Units] IG_Vasilich:
Does ducking work for any other app on your HU (any music player, that wasn't preinstalled on HU)?

I can imagine that your HU manages sounds from SpeedPlay in a nonstandard way, so apps do not get information that the audio channel is busy...
[Android Head-Units] NogenLunde:
There is a link to previous versions on the first page. :)
[Android Head-Units] kc1:
It's like the one on the right in the picture in this page https://android-headunits.com/usb-lead-has-a-6-pin-plug/
[Android Head-Units] IG_Vasilich:
well, these differences are merely to split host and device modes.

Then use your USB socket coming from 6pin connector, and use USB hub in between (maybe better powered hub, as phones normally pull much current from USB)
[Android Head-Units] kc1:
Well I tried 2 hubs, one powered, one not, with only the DAB unit connected, but it wasn't recognized/ found by DAB-Z with either hub. I don't understand why not, and why it doesn't work in the 4 wire socket
[Android Head-Units] IG_Vasilich:
Apparently your 4wire socket supports only device mode, and DAB receiver is like a flash drive - it should be connected to host (thus the DAB receiver acts like Device itself).

read https://en.wikipedia.org/wiki/USB_On-The-Go for details about your 6-pin connector with USB socket - it seems that this port is working in Host mode.
[Android Head-Units] kc1:
I'm confused. I thought 4 wire was the USB standard. If like you said most DAB players work with 4 wire standard, what's different about my head units 4 wire port/socket? A dashcam works in that port/socket, by the way. Is that device mode?
[Android Head-Units] ndev2k:
The only other thing I have set up for audio ducking is the reversing camera. When I put the car into reverse the camera comes on and the volume of the dab-z app drops to 50% as expected
[Android Head-Units] realzoulou:
See post #1
[Android Head-Units] DominicS65:
Sorry for not seeing this earlier but I replied on here about this. I feel the age of my reply is not relevant to whether I am correct.

Post in thread 'DAB+ App: (real)zoulou's DAB-Z app (official support thread)' https://xdaforums.com/t/dab-app-real-zoulous-dab-z-app-official-support-thread.3609608/post-84491753
[Android Head-Units] realzoulou:
@ndev2k Lots of devices don't allow for 3rd party apps to take part in the Android defined "audio focus" management. Reason: They implement their own audio focus management in a proprietary system app.

Typically I hear that DAB-Z does not duck when Navigation gives route guidance. This can be fixed by *not* setting any Navigation app in the Android Settings -> Car -> Navigation -> Navigation application (your Car settings may differ).

But even if all is good, the Speed Play app, which gives you Apple CarPlay, may not report any audio states to the Android system and thus DAB-Z does not know that it should duck/unduck.

Note: The driving backwards use case you mentioned, might be another exceptional case handled by a proprietary system app, which forcefully lowers any audio output of any app (Speed Play, or DAB-Z, or ...)
[Android Head-Units] kc1:
So I had a better look - the 6 pin is actually just a plug for 6 pins, with only the standard 4 wires running to it. In the picture below its the one with the grey tape round the wires next to the plug. It is wired in the same configuration as the the 4-pin plug next to it (plugged in in the picture)

For some reason, phones and DAB player only work when plugged into those 4 pins marked with the arrow, irrespective of whether its the with 4 pin plug or the cable with the 6 pin plug. Other devices, like a dash cam or USB stick work fine when they're connected to the 4 pin plug socket. Nothing works connected to either set of pins through either a powered or a non-powered USB hub. (The head unit is a Chinese EKIY T5 https://www.aliexpress.com/item/1005003767850705.html?spm=a2g0o.order_list.0.0.21ef18024hxSHs)
[Android Head-Units] IG_Vasilich:
description says that this unit supports USB Hub. What kinds of hubs have you already tried?

And what kind of DAB dongle do you have? normally phones acting as hosts, and all other devices (cams, flash drives, mices, keyboards) - as devices. So DAB Dongle should work on those USB sockets, where USB flash drives are working. I have USB hub, where DAB stick, USB dash cam and OBD2 adapter are working simultaneously without problems.
[Android Head-Units] kc1:
I tried this one:

Portable 4 Port USB HUB 2.0 High Speed USB Laptop PC Slim Smallest HUB Mini USB Splitter Adapter For Phone Laptop PC Black: Amazon.co.uk: Computers & Accessories

Free delivery and returns on eligible orders. Buy Portable 4 Port USB HUB 2.0 High Speed USB Laptop PC Slim Smallest HUB Mini USB Splitter Adapter For Phone Laptop PC Black at Amazon UK.

www.amazon.co.uk

And this one (powered):https://www.amazon.co.uk/gp/aw/d/B07TXFT75P

I have this one:

Hikity Car DAB/DAB+ Radio Receiver, DAB Digital Audio Transmission with Antenna, DAB Car Radio Adapter USB Dongle for Most Android Car Stereo: Amazon.co.uk: Electronics & Photo

Shop Hikity Car DAB/DAB+ Radio Receiver, DAB Digital Audio Transmission with Antenna, DAB Car Radio Adapter USB Dongle for Most Android Car Stereo. Free delivery and returns on eligible orders.

www.amazon.co.uk

And tried this one: https://www.amazon.co.uk/gp/aw/d/B07BBGHL6Q

This one:. https://www.amazon.co.uk/gp/product/B083Q7YG4F

And this one: https://www.amazon.co.uk/gp/aw/d/B09ST7FPNX
[Android Head-Units] realzoulou:
Maybe they want you to buy their (specific?) Ekiy USB hub https://www.aliexpress.com/item/1005002883744622.html as indicated on the Aliexpress link above...
[Android Head-Units] kc1:
I'm not sure how they'd be able to enable just for theirs and block all others, with just a 4 pin wiring
[Android Head-Units] okij:
That would be possible without problems on software side and has nothing to do with the wiring.

USB devices identify themselves to the system with what type they are (like storage device, hub, input device and so on) and a device- and vendor-specific ID. So they could be blocked (i.e. not recognized) if the manufacturer decided to do so.
[Android Head-Units] realzoulou:
DAB-Z release 1.9.123 BETA

Change log:

compared to 1.9.121 BETA

* Fix: Favorite station list includes all stations

* Fix: Splash screen Settings button not reacting

(both introduced in 1.9.121 BETA)
[Android Head-Units] Chrisu02:
@realzoulou

I reinstalled my machine due to an update and installed now the latest version of DAB-Z

Unfortunately with the idrive controller i can only scroll/select within the Stationlist anymore.

I can not move sideways and more to select the "Play" button when paused, or to select the lower menu buttons :(

I guess that the FIX "6. Fix: Too many UI controls are focus-able with rotary controller ("iDrive")" is the reason for this ?

Any chance this may be at least selectable between the old/new behavior ?

Sincerely Chri
[Android Head-Units] NogenLunde:
You're right about that. I suggested to implement iDrive right/left click to tab in and out of the menu row. We have touch screens, so no big deal? But people without touch screen are in trouble ...
[Android Head-Units] Chrisu02:
For BMW one and 3 E Series the display is very far away of the driver, thats why the idrive controller is much better for using it.

I nearly have everything on the HU modded to be selectable via Tasker/touchtask Scripts to simulate touch controls, which also does give the whole system a much more OEM feeling and also does not distract as much anymore :)

Before the update DAB-Z was controllable by 98% via the idrive, now it feels like its only 10% anymore.

doing the left/right to only switch to menu / Image (Play Button) Tile, sounds like a good idea :)

sincerely Chri
[Android Head-Units] realzoulou:
@Chrisu02 , @NogenLunde I will bring the old behavior back and update the current Beta version
[Android Head-Units] Chrisu02:
Thank you very much :)

Sincerely Chri
[Android Head-Units] nihonjin:
I like the interface of this app and for the most part it works really well. However, reception on the road to work does have many drop outs. Yet another app that is nowhere near as polished as this one seems to have far less drop outs. Same route, car and dab hardware just different apps. Is there any setting or way to make this app less sensitive to low reception areas or why else does the other app more consistently keep signal and not drop out?

This is the other app just so you know which one I am talking about. I much prefer to be able to use DAB-Z.

DAB+ Radio USB - Apps on Google Play

Radio app for USB DAB+ receivers (not SDR), optimized for car headunits

play.google.com

Thanks.
[Android Head-Units] realzoulou:
@nihonjin Sorry, to read that you face issues with DAB-Z. No, there is no setting to avoid signal drop outs. Usually only the antenna and coverage at the location decides how well DAB is received. In super rare cases, it is also a combination of a) head unit, b) Android version, c) DAB USB adapter. Which one it is actually, is virtually impossible to find out, except when you would be able to exchange one after the other.

Btw. the other app has it's own thread in XDA: https://xdaforums.com/t/app-dab-radio-for-usb-modules.4280741/ but seems to be out of regular maintenance already.

It is up to you to decide, which app to use.
[Android Head-Units] thommy4:
Is it possible to sort the channels into multiplex folders? The channel list can become very confusing with over 100 channels.
[Android Head-Units] realzoulou:
Some hints on the UI...

What you are looking for is to mark certain stations as favorite and then only use the favorite list from that point on. Note: Only favorite list can be "sorted". Switch between full / favorite list with the button between "<<" and ">>"
[Android Head-Units] pwood999:
After using this for several years in my car, I just installed DAB-Z in my wife's Freelander on new Joying android 10 head unit. All works well, especially now I installed a decent amplified antenna to replace the FL antenna.

Found 123 channels (in UK), but having a strange issue with Favourites (Favorites). some channels like BBC Radio 1 & 2 will not save. Did the usual Long Press & select the Star, but BBC channels don't save. All other channels I tried seem to work ?

[EDIT] Just tried deleting all channels & re-scanning. Now I can add any station to Fav list, but when displaying all channel list, some don't have a star even though they are in the Fav list ?? (but wife happy because her favourites work)

Pete
[Android Head-Units] realzoulou:
I suspect that you have several "BBC Radio 1" entries in the main list, right?

Note that DAB-Z does not combine services that are transmitted in different ensembles or frequencies to one, but keeps them separate. So, you might expect that selecting one specific BBC Radio 1 in the main list makes all BBC Radio 1 appear in the fav list. If I got you wrong, let me know.
[Android Head-Units] buffke:
Hello,

I'm looking for settings to enable a buffer.

With my android car radio and external DAB+ module, there are often short interruptions of 1-5 seconds, if I drive through the city.

I would like to bridge this with a small adjustable buffer (10s).

Is such an option available in the app?
[Android Head-Units] realzoulou:
@buffke This is technically not feasible. DAB is a real-time broadcast of audio and additional metadata. There is nothing you could buffer in advance in order to bridge a gap.

It is the very same with FM/AM radio and live TV. You cannot buffer sth. that does not exist yet. What you hear/see is Live (!).

And I assume you would not want to wait for 10sec after you changed to a station until you hear/see something. This would be the consequence of adding a 10sec buffer: You need to wait until the buffer is full, so that there is sth available for bridging a gap. But if the gaps sum up to more than 10sec, the "problem" is anyway back again.
[Android Head-Units] DominicS65:
I used to get this stuttering on one channel I only use on the odd occasion they have the rights to broadcast test match cricket commentary. The problem was a setting I had enabled that did something like mute when the signal is poor.
[Android Head-Units] IG_Vasilich:
you can enable timeshift and go 10 seconds back on this channel, to get the idea whether the buffer helps or not in your case.
[Android Head-Units] rigattoni:
Hi @realzoulou,

I´m wondering why DAB-z shows up a couple of times in "last apps" as seen in my screenshot:

DAB-Z is just started after a clean boot once.

Any Idea about that?
[Android Head-Units] realzoulou:
DAB-Z release 1.9.125

Change log:

compared to 1.9.123 BETA

* Fix: UI controls for rotary controller ("iDrive")

* Removed: PayPal and Google Play links
[Android Head-Units] realzoulou:
@rigattoni I don't see this with my devices. This screen comes from the SystemUI. Can you send me a system-wide logcat of such a cold boot ending in so many DAB-Z "recent tasks" ?

Btw. I just did a cold boot and it showed a recent task WiFi settings, which I did not open in this cold boot cycle, but had it open in one of the previous boot ups. Looks like Android / SystemUI remembers previous things. However, it should not show the same thing so often...
[Android Head-Units] rigattoni:
I took a log file from cold boot.

Don´t be surprised: There are tons of null pointer in there and visible issues.

Not really surprising as this is a really new unit from Klyde: PX6 on Android 10 in the moment, with CSM4 MCU, rotatable screen 12.2".

I´m in contact with the developer on Klyde side and provided already a list of issues in the firmware.

Nevertheless... see attached log. May be you find something related to DAB-Z.
[Android Head-Units] realzoulou:
@rigattoni From DAB-Z perspective all fine. DAB-Z was always only running once (process 759).

It started due to USB_ATTACHED, but remained in background (your setting in DAB-Z).

Then FCC launched DAB-Z again with "remain in background" flag. DAB-Z noticed that it is already running and did nothing.

And later on again FCC launched DAB-Z, likely because you touched on DAB-Z icon on FCC. This brought DAB-Z to foreground.

Thus, I see no reason why DAB-Z would appear more than once in Recents.

Btw. What you see in Recents is the socalled "Player" activity of DAB-Z, which was instantiated exactly once in the log.
[Android Head-Units] rigattoni:
Thanks a lot for your quick analysis, appreciate your fantastic support. (y)

As I said... I am still in discussion with Klyde about some things. You may have seen the NullPointer and the Java issues in there.

Just one thing I need to report then to them.
[Android Head-Units] VBA_Dev:
Hi @realzoulou, a bug from a few years ago seems to have started happening again over the last month or so with UK stations.

Sometimes all stations within a certain mux will just refuse to play. Full signal is always shown, but the bit rate is always blank as it’s not playing.

The trick to get the playing again is to switch to a station on a different mux, allowing it to play and then switch back again. I’m guessing because it’s loading the mux/station from scratch.

Is there anyway we could have a button or action to force a “mux reload” or something to that effect?
[Android Head-Units] realzoulou:
@VBA_Dev I will need raw recordings from that scenario. Please follow these steps closely:

1. Prepare:

1a) Enable OMRI raw recording in Developer Menu

1b) Select the station, which "refuses to play"

1c) Close DAB-Z

2. Create recordings

2a) Start DAB-Z, wait for ~30sec, expected behavior: No audio, bitrate is blank. Note down the exact time (minutes especially)

2b) Select a different station from a different mux, wait for ~30sec, expected behavior: Audio is audible. Note down exact time.

2c) select the previous no audio station, wait for ~30sec, expected behavior: Audio is audible. Note down exact time.

2d) Close DAB-Z

3. Pull the .raw files from the device, zip them and send to my email address with the times noted above.

4. Open DAB-Z and disable raw recording option again. Close and restart DAB-Z to apply the change.
[Android Head-Units] VBA_Dev:
I’ll see what I can do. The other issue is that it’s a intermittent bug.
[Android Head-Units] thommy4:
Thanks for the tip. I have already saved my favorites. However, I live near the border and receive channels from Germany, Austria and the Czech Republic. In addition, I often go to new broadcast areas, where I have to make a station search again. For this reason, I would still find it great if the stations are grouped. So, for example, 11D-Bayern is a folder and then below that is Bayern 1, Bayern 3, etc. So it makes e.g. also VW in their radios:
[Android Head-Units] TorstenH:
Why not combining them and create an artificial Service Following (SF)?