yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] realzoulou:
Yes, DAB-Z can work on all Android phones, tablets, TVs from Android 4.4 onwards. Our beloved Chinese head units are actually tablets typically, trimmed for being used in vehicles. Of course the DAB USB hardware requirements must be met. See post#1
[Android Head-Units] HaTeNL:
I have reception issues when using the DAB receiver on the (Joying) car radio, but not when using it on my mobile phone. This looks to me like some interference on the power?

Does anyone know how I can solve this? I have already tried adding a 1uF capacitor between the 0 and +5V, directly behind the USB connector inside the housing of the receiver, without success.
[Android Head-Units] IG_Vasilich:
pls read last 2-3 pages here, there were discussions about it.

[MENTION=7838245]realzoulou[/MENTION]

here (dab-z_2020-03-17_08-35-52.zip) are my verbose logs after scanning - i see many times frequencies 144 and 136, but it still shows me 32kbps for all stations of hr ensemble (hr1, hr2, hr3, hr4*,, you fm).

And some logs directly after chashes

P.S. all logs were taken in OMRI mode.

And -yes, the switching time is back to normal (up to 2 seconds in one ensemble, 3-5 s - between different ensembles). And i have a feeling that hr ensemble (with high bitrate) plays much smoother now :good: :victory:
[Android Head-Units] HaTeNL:
Cool! A few questions.

You added an earth to the DAB dongle. Where did you connect the earth? From the copper tape to the vehicle chassis?

Can you explain 4 a little bit more? What did you connect?

Thanks!
[Android Head-Units] DrRobin:
Hi,

I wrapped the DAB dongle in copper tape and soldered a thick piece of wire on to the tape, which then went to an earth point in the boot (picture attached).

I wrapped copper tape round the metal case of the head unit at the front, just back from the front bezel, taking tape over the case towards the back of the unit. I also taped round the antenna connectors at the back. Then I soldered a thick wire on to the tape and fixed it in to an earth point (picture attached). The HU cradle is badly earthed in my car, but there was a steel re-inforcement bar behind the radio, so I took two pieces of copper tape from the back of the radio and over the metal bar, leaving enough slack to get the HU in and out (pictures attached).
[Android Head-Units] iMattmax:
Why did you do that?
[Android Head-Units] surfer63:
Don't you read? And don't you read back?

He starts his post (3 posts up) with: "I have finally fixed the DAB noise problem on my Xtrons TA709IPL, here is what I did:"
[Android Head-Units] iMattmax:
No, I can't read [emoji6]

He wrote his post in the 3. Februar 2020 (#2465), the post above is only a quote from his post!
[Android Head-Units] surfer63:
Ok, but nevertheless: it mentions it quite clearly. (Click the orange arrow in the quote and you will jump immediately to that post, in case you did not know that)
[Android Head-Units] Dannydownload:
realzoulou, found AndroidAutoShop-DAB+ 1.0 on my android headunit (hotaudio px5) and searching for an update.

found this thread and installed DAB-z from the play store.

Will see if dab will will work in the north of the Netherlands

Thank you for your work
[Android Head-Units] surfer63:
It absolutely does.

See here.

Note: look at "fase 3" as that is active since 2016 and since it has expanded even further.
[Android Head-Units] EwOkie:
Installed latest release but upon startup

I get need to remove older plugin all the time?

How do I find this?

On non root car head unit
[Android Head-Units] realzoulou:
You find it in Android Settings -> Apps

It is an app that you need to uninstall.
[Android Head-Units] realzoulou:
Here the quote from release 1.5.59 regarding the mpeg decoder plugin
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

have you had a chance to check my logs i posted earlier? the crash happens always after 1st station change after awaking HU from sleep.

And i confirm, that the situation with hr ensemble is almost good now (with latest version), except the fact that the app still shows 32kbps on it (that can be ignored :) ).
[Android Head-Units] realzoulou:
Sorry, but not yet... I was busy working on the ultimate tracing, which should allow me in the future to reproduce myself what you experience in the car.

It will only require that the issue is reproducible, so that you can create a recording of the issue. I plan to release a beta this weekend and the release notes will come with all the details... It is not logcat based and it will be quite user friendly.
[Android Head-Units] VBA_Dev:
Excellent ?

I’ve found another bug too that I’ve been meaning to catch a logcat from, although it’s not an omri fault.

I have one station that no longer plays in libdab.so mode, but plays fine in omri. Would your new tracing logic pick that up, or is it targeted just at omri mode?
[Android Head-Units] realzoulou:
It will only work for OMRI.

I can't fix libdab.so anyway so I don't bother about it anymore. As said earlier already, I plan to remove libdab.so when OMRI has reached full stability and is feature wise equal to it. Service Following is still missing. When I reached this, I will remove libdab.so
[Android Head-Units] VBA_Dev:
Cool, no problem
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

just out of interest:

do you have access to OMRI code, or can you influence it? Are there any plans to make OMRI open source?
[Android Head-Units] realzoulou:
Yes, it was uploaded to GitHub in January: https://github.com/hradio/omri-usb

DAB-Z version 1.7.78 was the first version with OMRI built from source.
[Android Head-Units] realzoulou:
Now I did:

1. On the wrong bitrate of 32kbps: This is a fault in DAB-Z, not in OMRI. It doesn't affect any functionality, only the displayed value is wrong. Easy to fix and will be in the release after the currently planned one (so: not this weekend)

2. On the crash after 1st station change after resume: I saw this type of crash already quite often on FirebaseCrashlytics but there it did not show up with a backtrace. Now I have them, thanks ! However, it comes out of Android itself, so I am not sure yet how to fix this...

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14
backtrace:
#00 pc 00027097 /system/lib/libmedia_jni.so (_ZNK7android11JMediaCodec27createByteBufferFromABufferEP7_JNIEnvbbRKNS_2spINS_7ABufferEEEPP8_jobject+55)
#01 pc 000274fb /system/lib/libmedia_jni.so (_ZNK7android11JMediaCodec9getBufferEP7_JNIEnvbjPP8_jobject+171)
#02 pc 0002757e /system/lib/libmedia_jni.so
#03 pc 02340d31 /system/framework/x86/boot.oat (offset 0x1f79000)
[Android Head-Units] IG_Vasilich:
So would it help to insert more tracing in these parts of code that are involved in retuning and recreating audio stream?

I am ready to install any debug version if you want me to...
[Android Head-Units] NogenLunde:
[MENTION=7838245]realzoulou[/MENTION]

I made a few pictures to show how we're experiencing the BMW iDrive on DAB-Z: Scrolling clockwise right after launch never reaches the station list. Scrolling counter clockwise activates the station list, and we can then scroll up and down.

To remedy this: Is it possible to synchronize the blue selector with the active station on launch?
[Android Head-Units] realzoulou:
DAB-Z release 1.7.83

DAB-Z release 1.7.83 (beta channel)

(be patient... Google states in the Play console: "Due to adjusted work schedules at this time, we are currently experiencing longer than usual review times.")

Change log:

New

* Version number is shown at startup of app in "DAB-Z starting..." popup

* Developer Menu (hidden by default)

Tap 7 times on Version number in Settings->Info until you see "You are developer!". Then close and reopen Settings and an additional menu "Developer Menu" appears.

- OMRI raw data recording: When activated and app is restarted: DAB-Z records the raw DAB data from the current station into a file (~32 MB per hour).

example filename: /DAB/rec/dab_2020-03-27_23-45-43_labelunknown_1162_dc1a.raw

- OMRI demo mode: Keep your fingers off, this is only for me for now. It will destroy your station list. In this mode a raw data recording can be re-played.

- Force test crash (self-explaining)

Screenshot of the Developer Menu

Changes

* OMRI verbose logging option moved into Developer menu

Bugfixes

* Several minor stability fixes in OMRI and DAB-Z

Known issues

* Regression in 1.7.83: No audio at all for some users

* OMRI: System crash when selecting BBC Radio 2 in UK

* OMRI: Sometimes no audio, especially with stations using old DAB standard (MPEG), but also randomly with DAB+ (AAC) stations

* OMRI: Some stations stutter and show a different bitrate than in non-OMRI mode.

* OMRI: After station scan, stations may be missing, which appear properly in non-OMRI mode.

* OMRI: RadioDNS logo download results in no (or not enough) logos, although country should be covered.

* Non-OMRI: Randomly crashes while parsing data from DAB USB adapter
[Android Head-Units] realzoulou:
[MENTION=2784358]haynesteve[/MENTION], [MENTION=9709140]VBA_Dev[/MENTION]

May I again ask for a repro of the "BBC Radio 2 -> system reset" issue?

This time it should be much simpler for you and the result should allow me to reproduce the issue on my own bench.

1. Enable Developer Menu: tap 7x on Settings->Info->Version: -> 1.7.83, then close Settings, re-open settings

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

2. Enable OMRI Mode

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

4. Reopen DAB-Z

5. Select BBC Radio 2

.... Wait for the crash of the system

6. After reboot go to DAB-Z Settings and disable OMRI raw recording and disable OMRI. Restart DAB-Z again.

Result of this procedure is hopefully in /DAB/rec/ folder. It should contain at least one file "dab_<date-and-time>_unknownlabel_ce15_c222.raw file(s).

Please send me the file(s) if they are not 0 bytes ;)
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

should i do smth special? does the new version have kinda other logging? or was it targeted mainly on people with system reset issue?
[Android Head-Units] NogenLunde:
I get no sound at all in OMRI mode, on any station, DAB-Z release 1.7.83.
[Android Head-Units] realzoulou:
Yes, mainly on the system reset topic.
[Android Head-Units] realzoulou:
I should not have changed anything, which breaks audio completely... If the issue persists, could you provide me with raw recording files as described above. 10 seconds of recording a station should be enough
[Android Head-Units] haynesteve:
Updated this morning, but it won't play anything from any station in OMRI. Tried a fresh station search, but wouldn't even try.

Did a system log any way, if it helps.
[Android Head-Units] realzoulou:
Thanks haynesteve. Somehow the log makes no sense. When you switched from libdab.so to OMRI mode, libdab.so crashed as usual. But then DAB-Z somehow was not started properly by Android... Just as if only half of it was running... as I said... makes no sense...

NogenLunde and you said that there is no audio at all with OMRI, but at the same time I get positive feedback via the beta channel and all my 4 test devices work properly.

So for now, I assume it is not a generic problem of 1.7.83

[MENTION=9709140]VBA_Dev[/MENTION] did you give it a try already?
[MENTION=9350973]All[/MENTION] I would appreciate OMRI raw recordings from anyone that has "no audio" or "system reset" issues with OMRI.
[Android Head-Units] VBA_Dev:
Only just saw that you have released the beta, but same as haynesteve, I’ve had no reason to go in the car over the last week or two due to the U.K. lockdown.

I’ll give it a test tomorrow hopefully and report back.
[Android Head-Units] NogenLunde:
Makes sense from what I see here: In OMRI mode, when closing DAB-Z it will disappear as normal, but it is not really completely closed, so when I start it again, there is no reception, not even when switching stations. This is maybe what you see in the log (from the other user) as "not started properly by Android". Either I have to wait until Android removes it, or I can use task manager to kill it. Then when I start it now, I will actually get sound from one broadcaster, but only if a station from this broadcaster was the one last used (no sound if a different broadcaster was the last one used). I can also now switch between stations from this broadcaster and get sound as normal. Selecting a station from other broadcasters and DAB-Z stops working again; no sound from any station, not when switching back to the previous working broadcaster either.

I didn't follow all your steps when creating these raw log files, because I had to kill DAB-Z to get sound, but hope they are useful anyway. Let me know if you need more.
[Android Head-Units] haynesteve:
Did a complete re-install of the app. First try it crashed doing a station search in OMRI. Restarted, turned off OMRI, and tried station search again, crashed the entire HU forcing me to use reset button. Another re-install, turned off OMRI, and this time worked, playing stations. Changed to OMRI and did station search, after getting to 78%, stuck and eventually restarted.

2 logs, first after using reset button, and second after OMRI crash. Hope they have some info for you.
[Android Head-Units] haynesteve:
Just an update. Tried using so again this afternoon, played ok in normal, so tried OMRI again. Did a search which once again stuck on 78%, tried to cancel, but it wouldn't clear screen, so pressed home button and the launcher (Agama) rebooted. Opened up app again and got just a large play button displayed and a rotating circle, but no stations. Did another log for you.
[Android Head-Units] VBA_Dev:
Installed today, but I can’t enable the dev menu. No matter how many times I tap the version number in the info tab, nothing happens.
[Android Head-Units] NogenLunde:
I had this problem, too, but I continued to tap and suddenly "4 more to go" appeared, taped and taped, and finally developer mode was enabled. What screen do you have? Mine is 10.25", Android 9, Snapdragon 625.
[Android Head-Units] VBA_Dev:
Mines an intel Sofia, android 6
[Android Head-Units] IG_Vasilich:
so as mine, but i had no problem to get devMode enabled - just tapped as fast as i can about 20 times...
[Android Head-Units] surfer63:
You all didn't know yet, but [MENTION=7838245]realzoulou[/MENTION] actually built a tapping speed checker, and he logs the tap repetition speed. The winner gets an update of the apk ;)
[Android Head-Units] VBA_Dev:
Haha ?
[Android Head-Units] realzoulou:
[MENTION=10451415]NogenLunde[/MENTION]: Perfect !! All my expectations for the raw recording files became true :) This is the Bazooka-like weapon for terminating the remaining major issues of OMRI with stations in UK and NO.

The raw recordings helped me to find the root cause for the no audio regression that I caused myself in the 1.7.83 beta. I can reproduce with the 4 files all what you stated above, also the weird behavior that it makes a difference, which was the last station used.
[Android Head-Units] VBA_Dev:
Excellent news!
[Android Head-Units] VBA_Dev:
Had another go at enabling dev mode, and managed it after about 300 quick presses! Lol I think there is an issue with the detection

But if you need any more U.K. logs, I can now get them.
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION],

I just played a bit with DAB-z.

OMRI mode seems to be completely unstable now.

If I open DAB-z after boot, DAB-z works as expected. If I close the app (Back button) and reopen it, I just get the turning circle instead of stations.

Healing by rebooting the device.
[Android Head-Units] realzoulou:
I will replace 1.7.83 with 1.7.84 as soon as Google permits...
[Android Head-Units] rigattoni:
On my side it´s quite perfect. I first touched the String "Version"... but this is wrong. ;)

You don´t need to touch it fast, just some clicks on the right place are necessary:
[Android Head-Units] VBA_Dev:
Yes that’s what I thought, but the text string is small, so the hit area is also small on my screen. I got there eventually.
[Android Head-Units] rigattoni:
May be it´s easier on my 10.2" screen...
[Android Head-Units] netwave:
Is there any version of DAB-Z that support's my Parrot Asteroid Classic?
[Android Head-Units] realzoulou:
What I have seen on the Internet about the Parrot Asteriod I doubt that DAB-Z would be usable. But nothing prevents you from trying it out. Minimum Android version is 4.4 and the Android device must support USB host mode. No idea if this is the case for the Parrot. Note that the layout of DAB-Z is optimized for 6-10 inch devices with a screen resolution of more than 800x480.
[Android Head-Units] realzoulou:
DAB-Z release 1.7.84

DAB-Z release 1.7.84 (beta channel)

Change log:

Bugfixes

* Regression in 1.7.83 beta: No audio at all for some users

* OMRI: Some stations show a different bitrate than in non-OMRI mode.

Known issues

* OMRI: System crash when selecting BBC Radio 2 in UK

* OMRI: Sometimes no audio, especially with stations using old DAB standard (MPEG), but also randomly with DAB+ (AAC) stations

* OMRI: After station scan, stations may be missing, which appear properly in non-OMRI mode.

* OMRI: RadioDNS logo download results in no (or not enough) logos, although country should be covered.

* Non-OMRI: Randomly crashes while parsing data from DAB USB adapter
[Android Head-Units] realzoulou:
Please provide me with raw recordings of MP2 stations, especially from those with reproducibly no audio and most desperately I'm waiting for a BBC Radio 2 raw recording leading to a system crash.
[Android Head-Units] NogenLunde:
[MENTION=7838245]realzoulou[/MENTION]

I haven't got the .84 version yet, but here is raw recording capturing the "permanent no audio" affecting four stations in OMRI mode in my country (NO). First a working station is selected, then a non working, recorded until toast message and a few seconds more.
[Android Head-Units] realzoulou:
[MENTION=10451415]NogenLunde[/MENTION] Found the root cause why NRK P1+ was not playing at all. Thanks to your raw recording I was able fix the issue in OMRI.
[Android Head-Units] BJ Hunnicutt:
Station Logos

Hello,

I use 2 Isudar PX5 Android Radios. For a few months now, the button for synchronizing the station logos has disappeared. Even a new installation has brought no change. The logos are not recognized
[Android Head-Units] realzoulou:
It did not disappear, I changed the structure of Settings some months ago, because I needed space on the main screen for "Time Shifting" and did not want to overload the main screen.

Settings->Station logos:

When "Logo import" is clicked, you find the screen that you seem to be looking for.

I am not sure what you mean with "station list is gone" in your Google Play review. In case you mean the loupe button for scanning, this moved into Settings->Station list
[Android Head-Units] VBA_Dev:
Hey [MENTION=7838245]realzoulou[/MENTION] hopefully these recordings help you
[Android Head-Units] BJ Hunnicutt:
Thanks for the answer. I know how to import the station logos. But there is no Sync Button in the Logo Import menu. This button has been gone for a few months. And the .png files are where they belong.
[Android Head-Units] realzoulou:
What do you mean with no Sync Button? Does your screen not look like https://xdaforums.com/attachment.php?attachmentid=4991651

Please send me a picture of your screen to my email address zoulourns@gmail.com. We can continue then by mail (and in German ;) )
[Android Head-Units] realzoulou:
Thanks a lot [MENTION=9709140]VBA_Dev[/MENTION]. As nearly expected already... something causes DAB-Z to consume a hell lot of RAM memory.

The chart below from Android Studio Profiler shows how playing BBC Radio 2 looks like from a memory consumption perspective. It goes up until nearly 2 GB !! (Tested on a PX5 with 4 GB RAM). This explains why users with head units with only 1 or 2 GB of RAM see DAB-Z always crashing. Strange that Android allows that DAB-Z even causes a system-level crash. I expected it to be robust against that scenario.

View attachment 4991835
[Android Head-Units] NogenLunde:
[MENTION=7838245]realzoulou[/MENTION]

The 1.7.84 update is finally available on google play. :) Can confirm that OMRI mode is working again with audio. :)

Still stuttering sometimes when changing stations, in both modes (since version 1.7.78). Do you need recording of this? Unit has 4 GB RAM and snapdragon 625 CPU.

I managed to capture the "random no audio bug", somewhere in the raw recording files attached. First I select a few stations from broadcaster/ensemble NRK ..., no audio. Then I select one or two stations from a different ensemble, audio working. Then back to NRK ..., getting audio now.
[Android Head-Units] realzoulou:
Puh, this was a difficult one... but I now have the root cause and the fix for it available locally.

Root cause: BBC still uses an older DAB standard for encoding "Frequency Information" (ETSI TS 300 401 chap. 8.1.8).

OMRI implementation is based on the recent DAB standard V2.1.1 (2017-01), but BBC uses the older V1.4.1 (2006-06), which contained information on AM frequencies, which was removed in V.2.1.1. This caused OMRI to fall into into a 100% CPU and continuous RAM allocation "trap".

Will release this as soon as possible...
[Android Head-Units] typos1:
Interesting, glad you finally got to the bottom of it, whats the fix gonna be ?
[Android Head-Units] realzoulou:
Previously the code got stuck in a loop and created useless data in RAM. For those even more insterested, see my commit on my github fork of OMRI:

https://github.com/realzoulou/omri-usb/commit/321fdcde82722e1cd82321016eabcac3043e1983
[Android Head-Units] VBA_Dev:
Good job ?
[Android Head-Units] rhydsnewi:
Thanks for finding the issue. I'm guessing the BBC have stuck with the older version as Radio 4 and Radio 5 Live (and I think Asian Network) are simulcast on DAB as well as AM frequencies
[Android Head-Units] realzoulou:
Thanks for the files. I am analysing them right now... seems to be another tricky one...
[Android Head-Units] realzoulou:
DAB-Z release 1.7.85

DAB-Z release 1.7.85

Change log:

Change

* Station Logo Import: Now also files from DAB/logos/ are imported, previously only subfolders of logos/ were scanned

Bugfixes

* OMRI: System crash when selecting BBC Radio 2 in UK

* Screen for Station Logo Import from DAB/logos/ is not scrollable and thus Sync button is not visible at 800x480

Known issues

* OMRI: RadioDNS logo download is broken

* OMRI: Sometimes no audio, especially with stations using old DAB standard (MPEG), but also randomly with DAB+ (AAC) stations

* OMRI: After station scan, stations may be missing, which appear properly in non-OMRI mode.

* OMRI: RadioDNS logo download results in no (or not enough) logos, although country should be covered.

* Non-OMRI: Randomly crashes while parsing data from DAB USB adapter
[Android Head-Units] ale_prince:
I also wanted to disable the pop up,I have version 1.7.82 but after disabling the autostart when usb dongle is detected I can't find the setting you say
[Android Head-Units] surfer63:
I have the same issue in the last 3 versions. I set the switch to NOT autostart, but DAB-Z always starts when coming out of deep-sleep (Joying SC9853i on Android 8.1 using Nova Launcher). I already tried to enable the setting, then disable it again, rebooted: nothing. I uninstalled DAB-Z and then reinstalled (scanned again and added logos again), disabled the autostart feature, but DAB-Z always autostarts.

It gets pretty annoying. Logs don't say anything. I will try with the "raw recording" to see if that gives some info, but I hardly use the car lately.
[Android Head-Units] realzoulou:
Raw recordings don't help here. Send me a logcat and describe what exactly you did. Cold start or resume? What launcher? System-wide logcat helps me the most.
[Android Head-Units] ale_prince:
i have Android 9 on head unit rockchip px5 with FCC car launcher but i don't have this problem(autostart)