yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] voxmagna:
UPDATE: I eventually managed to root the beast so I could copy all the logo files into the system area folder and they are now found and listed by the app. It would be nice if logo files insider a folder could be found on a external USB or the internal mnt/sdcard without moving them into a system folder?

The crashes when dab-z is run from Sleep are still there. For now the head unit option is set for normal slow reset boot, but it's not how a car radio should normally start up.
[Android Head-Units] realzoulou:
I looked at 'crash-2022-10-01-11-44-20-com_android_launcher17.txt'. From the name of the file I suspect that the log is from your launcher app, not from DAB-Z.

The content of the file does not contain much. But I can say that it is for sure not coming from DAB-Z.
[Android Head-Units] realzoulou:
The folder where the logo png/jpeg files need to be present is

not

a system area, but the "usual" user's area:

<internal memory>/Documents/DAB/logos/

This "internal memory" has no standard name in Android and so all file manager apps call it differently, "Local", "Internal", "Flash", ...

The actual path name inside your Android device is printed on the Logo Import screen.
[Android Head-Units] voxmagna:
Thanks. Yes I wondered about the Launcher? It's the one thing in these head units that is very customised. Although you can get into developer mode, unlike Android phones and tablets, the launcher restricts what you can do. I couldn't even get in with adb. Now I have Root and the original firmware to restore to I can play some more. There's no restore partion I can find in the usual place and TWRP would have to be a customised version. For now I've managed to get the Boot.img file modified for Magisk.

I'll have another look at where the logo pngs are. What does the logo 'sync' command in DAB-Z do? My next challenge is to remove a lot of the bloat, most of which requires a mobile neteork data connection. I just want a reliable car radio with resident satnav and Bluetooth phone connections, not a complex Google Android platform with GAPPS I don't need. As shipped, my App storage is running at 16Gb from available memory of 32Gb which I hope to reduce since my satnav map data is only 1.5Gb.
[Android Head-Units] realzoulou:
It traverses the <internal memory>/Documents/DAB/logos/ folder (incl. sub-folders) and builds/refreshes a SQLite database, where it stores the relation from DAB station to logo file. Only the logo file name is used to guess from file name to which DAB station this may belong.

Because I did not want to scan this folder at every app launch (to see what the user may have changed there), I left it up to the user to press the "Sync" button.
[Android Head-Units] TJF2:
I sometimes(!) have a problem starting the car when DAB-Z was active before. It is a current 64 bit top model from XTRONS with Android 11. The radio is basically in standby mode and is shut down after removing the car key.

After starting the car, the attached error message ("Fehler_1.jpg") is displayed ("Storage Location-> Please select 'Documents/DAB' in the next dialog..."). If you click on "OK", the next window appears ("Fehler_2.jpg": This folder cannot be used. Select another folder to protect your data) ...

If I switch the radio off and on at this point, everything works normally...
[Android Head-Units] realzoulou:
In "Fehler_2.jpg" you should select the folder "Documents" -> "DAB" and then press ok. Did you try that?

If you did that but the error comes again and again, try to change the status of DAB-Z Settings -> General -> "Re-enable startup dialog when storage access is needed". If it is checked, then un-check (or vice versa) then restart DAB-Z.
[Android Head-Units] TJF2:
No. I have not done that yet. I will do it as soon as this occurs again. I will report... Thanks!
[Android Head-Units] okij:
@realzoulou Today I checked the memory usage of the internal storage and saw that DAB-Z is collecting enormous amounts of cache files over time.

If you look at the attached screenshots, you can see that betweet 3rd May 2021 and today it has generated 1472 file directories named "ts_*", each containing "dabtmp_*.dab" files and "textuals" and "visuals" subdirectories.

According to my apps listing in Play Store, DAB-Z is occupying a whopping 23 GB by now, whereas according to the DAB-Z app page in system settings its "just" 12 GB of cache. I don't know if 23 GB or 12 GB is correct, but it's far too much of cache files anyway.

What is the reason for DAB-Z saving all these cache files and - more importantly - not deleting them again? Is it a bug?

I haven't found a setting in DAB-Z to influence this behaviour, but for sure it should be user controllable. If those cache files are needed, they at least should be purged every day / week / month.

Thanks in advance for some feedback on this. :)
[Android Head-Units] surfer63:
You make a big mistake here in confusing the necessity for root and the ability to write to "external memory" for which you need the DocumentsUI which is by default not in the FYT firmwares.

And even with root you can't copy/write inside the system area. It is read-only on your uis7862 or any Android 10. Root can't change that and has absolutely nothing to do with it..

Please read through the proper documentation about the documentsui and about dynamic partitions. You do things without knowing what you do and without understanding your system.
[Android Head-Units] rigattoni:
Hi @okij ,

I just checked that on my setup... That look quite different in my PX6.
[Android Head-Units] okij:
That looks fine on your device.

I'm using a PX6 too, it's an MTCE device running on Hal9k v4.2.1.

@realzoulou So is this a bug of DAB-Z on my device or is there some (hidden) setting that controls the purging of DAB-Z's cache? Can I help you with some logs for debugging this issue?
[Android Head-Units] surfer63:
Are you using the "timeshift" function? That writes ~32MB per hour constantly, when using DAB-Z, to your memory/cache.

Maybe it should be removed on a restart of DAB-Z. Or is DAB-Z already doing that?
[Android Head-Units] okij:
@surfer63 Thanks for the hint. :)

I had the timeshift function enabled and indeed it is writing the cache files. After disabling it, no cache files were written.

The best thing is that after re-enabling the timeshift function, DAB-Z now only keeps the latest cache files, i.e. when closing and opening DAB-Z, the old "ts_*" directory is deleted and a new "ts_*" directory is created, which should be the way it's supposed to work.

Since still about 12 GB of older files were in DAB-Zs cache directory, I purged its cache via the system settings. This took about ten minutes to complete because of the vast number of files.

So now everything's fine again on my setup. (y)

@realzoulou: Maybe you should still have a look into this issue, because for some reason DAB-Z didn't clear the timeshift cache until I toggled the timeshift function off and on again. There might be other users who fill their internal storage without noticing it. ;)
[Android Head-Units] realzoulou:
@okij Yes, one portion of dir/files is from the Timeshift functionality. By design the App should delete all timeshift folders it created at runtime when the App is closed. Seems it does not always do so properly.

The other portion is from RadioDNS logos. I noticed this myself also.

I will fix both in 2.0.x, not in 1.9.x anymore.

Btw. Cleaning the cache of any app can be done in the Android settings of the app. I see no benefit to add an option in DAB.Z itself.
[Android Head-Units] okij:
Thanks, that's great! :)

Yes, of course. I only had to do it once because DAB-Z didn't delete the cached files by itself, which - as you wrote - will be fixed.
[Android Head-Units] realzoulou:
DAB-Z release 1.9.127

Change log:

compared to 1.9.126

* Fix: Station scan stuck with Italian ensembles
[Android Head-Units] moiloon:
hi wonder if anyone can tell me if this item would be adequate for dab-z

https://www.aliexpress.com/item/1005003294256877.html?spm=a2g0o.cart.0.0.50f638daQD3uVW&mp=1
[Android Head-Units] realzoulou:
Yes it will work
[Android Head-Units] moiloon:
awesome, thankyou
[Android Head-Units] IG_Vasilich:
@moiloon

just be aware that this window-sticked antenna has very poor reception capabilities, so if you live far from transmitter then you will get poor reception.It is better than nothing, but much better way is to use roof antenna with amplifier (so called "active antenna") e.g. like this https://www.amazon.de/gp/product/B073R8KW7F .
[Android Head-Units] moiloon:
thanks for the reply, and i know these window antennas are pretty poor, but, im going to be doing this on my audi tt, and following this thread ,post 5, and using the antenna to attacth to the window as per the info described

https://www.ttforum.co.uk/threads/how-to-installing-rear-screen-dab-aerial-amp-module.1004361/
[Android Head-Units] TJF2:
It was checked and immediately I unchecked it. Since then, the problem no longer occurs! Thanks again!
[Android Head-Units] okij:
@realzoulou I now checked this again and unfortunately this bug is back, i.e. the cache files are not being deleted again, please see attached screenshots.

It's no problem for me ATM, since I now disabled the timeshift function. I just wanted to let you know that this indeed needs to be fixed in v2.0. :)
[Android Head-Units] voxmagna:
Dab-Z sound mute: I don't know if I'm missing something but I have DAB-Z runing fine in a car head unit. As most of us know, car head unit apps sometimes need features not needed in phone Apps. My problem is DAB-Z boots to my Android Home screen link where I run it, but I can't mute its sound and keep satnav audio running?

DAB-Z and SATNAV apps sound are both locked together on the same volume settings. The head unit launcher allows me to set the sound ratio level difference, but what I want is to be able to mute DAB-Z audio from its screen if I'm concentrating on NAVI, or if my passenger finds my choice of music whilst navigating annoying. I don't know how to do that? If I could kill DAB-Z whilst it was running that's less desireable, but could work. I don't know how to do it once it's running?

Any ideas please?
[Android Head-Units] voxmagna:
I'm a retired rf engineer and for what its worth, I've just finished the 'As perfect as I could make it' car antenna system. But it would be too complicated to fully explain. Traps are in cheap Chinese antennae and their pre-amplifiers. I had to test several of them to get components with truthful specs. Pre-amps are useless without a decent whip and then it should be mounted over a metal area (Ground Plane). Avoid the dual band FM/DAB+ whip antennae with integral pre-amps. Better to just use a dual band whip and attach the pre-amp(s) externally. I used a BMW 'Mini' dual band antenna - it's the longest you can get and when tested I confirmed it was tuned to FM and DAB+ bands. That way you can set lower gain for FM. I designed an active diplexer to separate strong AM/FM signals from DAB+. I had a special reason for mounting the antenna on my trunk lid.

There is so much Chinese junk car antennae parts and amplifiers out there it's likely giving DAB a bad name in UK. My car antenna system drives a Chinese USB DAB+ dongle with the head unit running DAB-Z. The dongle came with an active screen antenna which was useless. To run a whip antenna and remote amplifiers you have to think about d.c blocking the dongle antenna input and re-inserting d.c at the correct voltage for amplifiers which will be 12V NOT 5V. But as I hinted, a good car r.f antenna system isn't going to be easy plug and play with parts from Ebay.

If you want to prove your car DAB system, search the internet for some local DAB stations, get their coverage map, tune your station then drive to the edge of the published service area. If you get sounds and more than 2 green strength bars you are good, if you get pops crackles and DAB mutes, your mobile antenna isn't good enough.
[Android Head-Units] Flemischguy:
I agree with you, thats why i installed the cheap chinese DAB receiver in the trunk away from the radio, and an Italian Calearo shark fin antenna on the roof of my 325i coupe, and it works like a charm.
[Android Head-Units] voxmagna:
I left myself the option of trying a shark fin antenna over the same cable entry hole which would look neater if I painted it to match my trunk lid, but performance wise, a long straight dual band whip is going to be better than a short stub antenna and pre-amp. Unlike you, I have a cabriolet with a folding roof and glass fiber trunk lid. Therefore my r.f design included creating a ground plane on the trunk lid which involved more work.

Most DIY car antenna systems will work to some extent near DAB transmitters, but it's only out on the road as you move from one local DAB station coverage to another or get into areas screened by tall buildings that you can really tell their effectiveness. I think that's how Ebay sellers get away with selling most of the Chinese DIY junk which may seem to 'just work'. IMHO the antenna systems designed by OE manufacturers for new cars are going to be more credible.

The DAB-Z signal strength bars are quite useful to watch as you drive around. But I still haven't found out how to mute the radio or kill the app and still leave the Navi or an MP3 tune playing? Germany has a lot of DAB stations and German car makers should know best what they are doing if you look at newish DAB car models post 2018.

Putting the dongle in the trunk or even inside the head lining close to the antenna makes sense to reduces cable losses, but after a preamp either integral or mounted close to the antenna cable, losses don't matter so much because the biggest effect on noise figure will be losses at the first pre-amplifier input. Post antenna pre-amp and my active diplexer splitting stronger FM/AM from weaker DAB signals, I ran 2 lengths of RG174 - one to the head unit for F.M and the other to the glove box where my USB DAB+ dongle is plugged in. I removed every FAKRA connector and used plated SMA throughout.

Most Chinese head units have a selectable software option to produce 12v pre-amp power when turned on. From measurements, I found their d.c output was poorly regulated for loads above 50mA and was probably a simple source resistor to protect against shorts. My pre-amp and active diplexer draws about 100mA so I took an 'Always on' fused voltage source and switched it from the radio antenna d.c with a mini 12V relay.

All is not as simple as it seems.
[Android Head-Units] realzoulou:
When you switch to any other audio or video app, DAB-Z should stop its audio output immediately. See #3,515

This will cause DAB-Z to enter a sort of paused state.

When you want to close DAB-Z you simple press the BACK button when DAB-Z is on screen. This will stop DAB-Z. It is not like killing the app, because the Linux process will still remain in RAM and when tapping on the DAB-Z icon in Launcher, it will "warm start".
[Android Head-Units] TJF2:
I have made a firmware update ( Android 11 ) in my car radio. Now (! ) I can no longer install DAB-Z. I do not use Google software ( Playstore ). I downloaded and installed the apk file from apkpure.com as before.

It starts and seems to install. Then the message appears "DAB-Z wasn't installed". What can I do?
[Android Head-Units] TJF2:
Problem solved: Since the latest DAB-Z version, you have to select the right variant for the matching hardware on apkpure.com. To do this, you have to scroll down and click your way to the right section among all releases.
[Android Head-Units] TJF2:
Android 11, Car: When the audio player Neutron Pro (setting "bitperfect") plays and DAB-Z is opened, Neutron is neither closed nor muted. Both apps are playing. And vice versa. In DAB-Z I have set the quitting under "Audio".

Is there any way to set it to only play the app in the foreground besides manually quitting?
[Android Head-Units] IG_Vasilich:
@realzoulou

tested with .126 and 127, but not sure when it started to happen again:

Problem with missing last station name char, when name contains non-ASCII chars, is back.

"RadioRüsselsheim" is scanned as "RadioRüsselshei". Checked with my kitchen radio with DAB+ - it still has full name after rescan.

Do you need log, or this is already known problem (you have already fixed it once) and you already know where to look at?
[Android Head-Units] IG_Vasilich:
@TJF2

have you checked ducking settings in DAB+ app and in Neutron app?

I have no problems with DAB+ - it mutes when navi app is talking, and switch to pause when any other music player (checked with Stellio and AIMP) is starting to play - everything works acc. to DAB-Z settings.
[Android Head-Units] TJF2:
What means "ducking settings" :)
[Android Head-Units] IG_Vasilich:
Manage audio focus | Android Developers

developer.android.com

And screenshot from AIMP:

Spoiler content hidden.
[Android Head-Units] realzoulou:
Bug confirmed. Originally fixed with 1.9.114 Fix: Some station names miss the last character (e.g. Rüsselsheim) and likely broken with 1.9.121 (undocumented change)

@IG_Vasilich I still have the raw recording from back in Oct 2021 from you. No new logs needed.
[Android Head-Units] danilaur:
for Isudar v72

ISUDAR USB Mini DAB+ digitial audio broadcasting for Android Series

Isudar USB Mini GPS Receiver Antenna For Europe + Android Car DVD DAB For Isudar A30 /H53 car stereo.

www.isudar.com
[Android Head-Units] AntonyTime:
Hi, i have a problem, the USB DAB+ Is connected, the antenna too, but the app does not find the stations when I do the search, someone help me?
[Android Head-Units] IG_Vasilich:
@AntonyTime

where are you located? Are you sure that there is some DAB+ broadcasting in your area? check here pls https://www.worlddab.org/countries/italy#coverage

Moreover, your DAB antenna has been installed wrongly (as I see from your picture) - the last part (farmost from antenna housing) should be connected to unpainted metal part of your car - read/watch installation manuals for that type of antenna.
[Android Head-Units] davidwatson007DAB:
Hi, I have an issue with fairly frequent 'ducking' when playing a station which I listen to most frequently, LBC here in London, UK. I have an AVIN 4 running the latest firmware - reinstalled yesterday from scratch, with the only 3rd party app being DAB-Z v1.9.127. The signal strengh seems very strong always 5 green bars so I'm really not sure what else to do as I love DAB-Z. I have swapped out the USB dongle twice and that hasnt made any difference to the issue. I am happy to pay for support if that helps at all. Many thanks, David
[Android Head-Units] realzoulou:
@davidwatson007DAB

Hi @davidwatson007DAB . When DAB-Z "ducks" then because some other app on the device outputs audio intermittently. See post #3,515

In case you are using CarPlay or AndroidAuto, then it could even be an app on the phone, which "disturbs" listening to DAB-Z.

If your device is rooted, then you could create a system-wide logcat from DAB-Z Settings->Info *after* such unwanted ducking occurred. Send it to my email address and I can have a look whether I find the "offending" other app. My GMail email address is visible in the Info screen as well.
[Android Head-Units] davidwatson007DAB:
Hi, thanks so much for your reply. I'm just wondering what else could cause the ducking issue. I had contacted Avin and they sent me the latest fw Android o/s so I completely reset the Avin 4 head unit with no Satnav installed although it's possible my phone might have been Blutooth connected. But DAB-Z still ducked quite frequently. What I will also do is test on stations other than LBC London and just check if the behaviour is the same on any other station.
[Android Head-Units] rigattoni:
Have a look if there are some notifications from upcoming Mails, Whatsapp or anything like that, even from your phone. Disconnect your BT connection and test again if the ducking is still present.
[Android Head-Units] davidwatson007DAB:
I will take a look thanks. Actually I have two phones. One is a Blackberry Key which is acting as a WiFi hotspot to my Avin 4 head unit and the other is a cheap Nokia C2-01 which is connected via Blutooth. I'll disconnect both and see if that makes a difference - Many thanks
[Android Head-Units] davidwatson007DAB:
Hi, I've just tested my Avin 4 BMW system again this morning. Neither of my 2 phones were connected to the system. WiFi is turned off on the head unit too. But I still get the annoying ducking on LBC London.... I dont think it's the station as we have DAB in the house and the signal and audio are perfect. The Avin 4 has been factory reset also and that has made no difference. I am now wondering if it's the latest DAB-Z causing this issue as I dont recall earlier versions of DAB-Z having this problem. Do you think that's possible at all? Many thanks, David
[Android Head-Units] rigattoni:
If you think a former version did not show this issue, you can try to sideload an older version. Just have a look at https://apkfab.com/de/dab-z-player-for-dab-dab-usb-adapters/com.zoulou.dab, there you can find older versions for testing.

As already been mentioned by realzoulou: If your unit is rooted, please provide a logcat DAB-z --> Settings -->Info
[Android Head-Units] IG_Vasilich:
You shouldn't compare reception quality between stationary radio in the house and DAB receiver in the car with many other interference sources.

Try to listen to other stations (if possible - from another DAB ensemble) to be sure that it is not the station who makes problems...
[Android Head-Units] davidwatson007DAB:
Hi, that's perfectly true! I wont compare home DAB to DAB running on my Avin 4 setup on my BMW 7 Series. I think that's a good idea to try other stations. I think what is throwing me a bit is although I prefer to listen to LBC in London I do note the signal quality even during the ducking remains at full strength. One other thing I should add is that this occurs even when the car is just sitting in my driveway going nowehere!
[Android Head-Units] rigattoni:
Well... did you already follow my instruction? https://xdaforums.com/t/dab-app-real-zoulous-dab-z-app-official-support-thread.3609608/post-87828455
[Android Head-Units] davidwatson007DAB:
Hi, a minor update after just having got my beloved BMW E38 back from a service.

Listening to other perhaps higher quality BBC Radio 2 broadcasts here in London, there is no ducking issue at all. So curiously and annoyingly it does just seem to be present on LBC. So even when my car is just sitting in the driveway the issue can still be heard. Not sure where to go with this now other than to try an older DAB-Z version where I just don't seem to recall the issue being present. I'll try to download the logs you've requested too. Many thanks once again, David
[Android Head-Units] gozilla79:
I have an Alps FF5000 head unit with fake android 10 on board.

A standard DAB app is installed on this head unit. This standard DAB player has no delay in starting the player, unlike the DAB + app from real zoulou that waits for minutes before the player finally starts.

I like the real zoulou DAB+ player better, but now prefer to use the standard DAB player because it started playing almost immediately.

Is there a solution for this player startup delay?
[Android Head-Units] NogenLunde:
What is the name of this app?
[Android Head-Units] realzoulou:
Send me a logcat and I will have a look. See post#1 on "how to"
[Android Head-Units] gozilla79:
The standard DAB+ player has file name DAB+ version 1.4 at my Head Unit.

A screenshot looks like this.
[Android Head-Units] TorstenH:
Maybe related to the issue that DAB-Z sometimes stuck on splash screen whereby I never waited several minutes. It works if I switch to home screen and then back to DAB-Z.
[Android Head-Units] TorstenH:
I don't know if this is the right thread for such a discussion. At least I would hate you if you propagate other apps in a thread related to my app. 😅