yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] okij:
Since I already collected the names all UK users on this thread in post #2496, I'm tagging them here again. Hopefully one of them has a rooted unit and can help you in this matter: [MENTION=456516]typos1[/MENTION], [MENTION=8476598]ab1702[/MENTION], [MENTION=10471615]DrRobin[/MENTION], [MENTION=1046126]davemazo[/MENTION], [MENTION=10431651]DominicS65[/MENTION], [MENTION=2784358]haynesteve[/MENTION], [MENTION=9709140]VBA_Dev[/MENTION] and [MENTION=2336681]sim1964[/MENTION], please help [MENTION=7838245]realzoulou[/MENTION], it's in your own best interest. :)
[Android Head-Units] realzoulou:
haynesteve and sim1964 have no root access. They already supported as good as they can.
[Android Head-Units] DrRobin:
I would really like to help, but I don’t have the a problem with the app crashing and don’t run OMRI, just the audio going in to slow motion mode when the program changes to news on Radio 4 in a morning.

I am also not sure if I am rooted or not.

If you want me to run some tests I am more than happy to give it go and run it if you let me know? what to test?
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: Of course you are right, I was just too lazy to edit the user list after copy&paste. :)

[MENTION=10471615]DrRobin[/MENTION]: You are most likely rooted if you use a custom ROM like Hal9k or Malaysk. In this case you should fetch a log after switching to OMRI mode, which should lead to a crash on UK stations like BBC.

If you are on stock ROM, most likely you are not rooted and cannot provide the necessary logs.
[Android Head-Units] haynesteve:
I am using Hal9k rom (v4), which uses magisk as root, but don't know how, or if, I can grant Dab-z root rights, as there doesn't appear to be an option to add it.
[Android Head-Units] okij:
I'm using the same ROM and Magisk asks if it should grant root rights when an app asks for them for the first time.

In DAB-Z, you go to settings -> info -> write logcat and choose "system wide", then you will be asked for root rights which you have to confirm.
[Android Head-Units] realzoulou:
You can check for root access even with DAB-Z:

Go to Setting-> Info and press the logcat button. If you get a dialog that asks for app only or system-wide logcat, then you have root access. If you get no such dialog, your unit is not rooted.

On rooted units after system-wide logcat was selected, Magisk or SuperSu should ask you now if you want to grant DAB-Z root access. Grant it and then logcat should contain everything I need.

My ask is: All UK users with a rooted unit that are able to reproduce the "whole system lock up with BBC stations in OMRI mode". Please share a system-wide logcat with me.
[Android Head-Units] haynesteve:
Tried this morning, allowed system wide log, but then said no root. Un-installed and installed again, this time was asked to grant root rights. Will try another log later after work.
[Android Head-Units] VBA_Dev:
I’ve caught a crash on BBC radio 2 this morning and sent on to [MENTION=7838245]realzoulou[/MENTION].

The first few crashes didn’t take long to happen, then by about the 4th crash I got a warning that google had crashed and the head unit rebooted.
[Android Head-Units] DrRobin:
I haven't changed the ROM from the standard version, so most likely not rooted.
[Android Head-Units] haynesteve:
Here we are, thought it wasn't going to crash at first, but it did eventually. System wide log.
[Android Head-Units] davemazo:
I am not rooted nor do I seem to have a problem. I don't use omri mode because I don't know what it is and it doesn't seem to work in the UK anyway.
[Android Head-Units] realzoulou:
Thanks a lot [MENTION=9709140]VBA_Dev[/MENTION] and [MENTION=2784358]haynesteve[/MENTION] !! :cool: :highfive:

In a quick rush through the logs, I see a certain pattern all the time.

a) the amount of audio samples drops down (not sure why, signal quality is good)

b) Android Audio subsystem (audioflinger) detects that not enough audio samples come in from DAB-Z and closes the audio output to hardware

c) Android Garbage Collector prints that it was collecting garbage in DAB-Z for several (up to 10) seconds

d) All kind of Android system services detect that something is slowing down the system

e) other apps are getting killed by Android

So, my current working assumption is that BBC Radio 2 causes DAB-Z (OMRI) to allocate RAM memory at a dramatic rate and forces the whole system into a low memory situation.

I will need much more time to look at the details of the log...
[Android Head-Units] okij:
Thanks for your analysis, it's interesting to read although I'm not a UK user. :)

About a week ago you wrote that you found a major CPU hog in the OMRI driver. Since it might take a while to fix the UK/BBC related problems: Could you release a version with a fix for the CPU hog in the meanwhile? OMRI mode is stuttering a lot on my PX5 device, but feature-wise I prefer it over non-OMRI mode, so I would like to have it useable again.
[Android Head-Units] realzoulou:
Yes, I plan to release a new beta in the next days
[Android Head-Units] Rahle:
The app doesn’t show in Google Play on my Android device - what do I do?

Used to have it on it and worked fine, but I wanted to reinstall only to find it is not showing up in Play store anymore :(
[Android Head-Units] realzoulou:
What device? What Android Version?
[Android Head-Units] rigattoni:
by the way [MENTION=7838245]realzoulou[/MENTION]:

On CSN2 units there is a possibility to get complete dmesg.txt and logcat.txt files without root rights out of the unit:

Logcat logo file steps:

1. Insert the USB disk.

2. Enter Settings- Car settings- Factory settings- input the password 0000, the logcat OK appears at the bottom of the screen.

3. Return to the interface and click the ES file explorer, then choose the USB Disk.

4. Here are the dmesg.txt and logcat.txt files.
[Android Head-Units] realzoulou:
DAB-Z release 1.7.81

DAB-Z release 1.7.81 (beta channel)

Change log:

Changes

* OMRI: When "no audio" is detected, one retry is attempted to re-start the selected station.

Toast message changed from "No audio! Try with OMRI disabled" to "No audio! Will retry..."

* When DAB-Z is re-opened after it crashed, a dialog is shown that allows to go to Settings before OMRI or libdab are used.

The dialog closes automatically after 5 seconds and DAB-Z continues to start, but will show the dialog again a next start.

If unit is rebooted or User selects either "OK" (=open Settings), or "Cancel" to ignore, the dialog does no longer appear, until a next crash may happen.

Note: After leaving Settings, DAB-Z has to be started manually.

This is mainly for those Users that cannot go to Settings anymore because DAB-Z crashes too fast.

* The on-time dialog after installation about OMRI is removed.

* OMRI: Added Settings->General: OMRI verbose logging enable/disable (default=disabled)

* OMRI: If RadioDNS logos is disabled in Settings, no RadioDNS logo download is performed at station scan and no message about missing Internet connectivity is shown

Bugfixes

* OMRI: Stability fixes and CPU usage optimizations

- Constant load on CPU reduced from ~20% to ~5% (measured on PX5 Android 9 Hal9k 4.0.1)

- Station switch time (from UI selection to first audio audible, in average!):

same ensemble: ~ 0.6 - 0.8 sec (previously ~ 0.7 - 1 sec)

different ensembles: ~ 3-4 sec (previously ~ 4-5 sec)

(for comparison: legacy libdab: always ~3-4 sec)​

* OMRI: Importing a station list shows "import failed" or does not pick up the station list.

* OMRI: When switching between stations on same ensemble frequency, DLS text and MOT slideshow picture are not updated anymore

Known issues

* new in 1.7.81: After bringing already running DAB-Z to foreground, Settings cannot be opened for several seconds

* 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] rigattoni:
Bug report:

Environment:

Joying SC9853i

Android: 8.1

DAB-Z release 1.7.81

Unit rooted

Reproducible:

Yes

Observed behavior:

Sometimes after switching stations you need 3 tries to get into the settings menu of DAB-Z. You are sometimes thrown back to the main screen of DAB-Z instead of staying in the settings menu.

Attachments:

Video and log file are stored on Dropbox. Video and log are not from same session, but always reproducible.
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: Besides the problem that [MENTION=2534110]rigattoni[/MENTION] just reported and I also experience (on a PX5 device on Hal9k 4.0.1 ROM), DAB-Z 1.7.81 is really awesome! :cool:

OMRI mode is now running stable without stuttering and hickups even when the CPU is under load, e.g. when starting Sygic or when updating an app via Play Store, which caused problems on previous versions.

As promised, I just sent you another donation to thank you for your great work. :highfive:
[Android Head-Units] VBA_Dev:
[MENTION=7838245]realzoulou[/MENTION] thanks for the beta update, sounds like it’s getting to a more stable place now :)

Would a new log with omri verbose logging enabled help with the UK radio 2 issue?
[Android Head-Units] realzoulou:
Yes, OMRI verbose logging is meant e.g. for

* BBC Radio 2 whole system lock up and reset

* No audio ever with some stations

* Stations missing after scan in OMRI mode (AUS)

* Audio slow down at the hour bell (UK)
[Android Head-Units] NogenLunde:
I don't see this improvement (Snapdragon 625, 4 GB RAM), still 4-5 sec on station switch between different ensembles.

Can confirm that this is fixed here.

Other observations after playing with this version for 30 minutes:

No crashes.

Temporary silent station bug not encountered.

Stuttering when switching stations is better in this version, but still not perfect (as it was in the stable release).

Don't have the problem getting into the settings menu, reported by other users.
[Android Head-Units] realzoulou:
Confirmed and added to Known issues in the release post:

* new in 1.7.81: After bringing already running DAB-Z to foreground, Settings cannot be opened for several seconds​
[Android Head-Units] realzoulou:
[MENTION=9709140]VBA_Dev[/MENTION] and [MENTION=2784358]haynesteve[/MENTION] I hope I can ask you once more for a reproduction of the "BBC Radio 2 system reset".

BUT: You have to follow these instructions below. The DAB-Z built-in logcat feature cannot get any log from a previous lifecycle. Android keeps logcat only in RAM. A system restart clears RAM !

1. Install a Terminal Emulator

I propose "Android Terminal Emulator" by Jack Palevich on Play Store using this link: https://play.google.com/store/apps/details?id=jackpal.androidterm

2. Install Google Gboard and activate it as standard keyboard

Reason: The standard keyboard of your device likely will cover most of the screen and makes it impossible to see what you have to type into the terminal

3. Start DAB-Z, activate OMRI, activate OMRI verbose logging, close DAB-Z again. (Important! changes to "OMRI verbose logging" get effective only after a DAB-Z restart)

4. Open Terminal Emulator

5. Type this command

while true; do sync ; sleep 1; done [ENTER]

6. Open a new window in Terminal Emulator (press the + button)

7. Type these commands (lower/upper case is important)

cd /sdcard/DAB/logs [ENTER]
touch bbc2.txt && su -c "logcat -f bbc2.txt" [ENTER]

6 Grant Terminal Emulator access when asked by SuperSU or MagiskSU

7. Then press HOME to send Terminal Emulator to background

8. Re-start DAB-Z, select BBC Radio 2 and wait for the crash of the system. All what you do is now written to the logcat file immediately in realtime. With this procedure only the very last second before the unit reboots is lost.

9. After the reset, download the logcat file from /sdcard/DAB/logs folder and send it to me.
[Android Head-Units] Firsave40:
I would really like to test the latestest beta version. Is this possible?
[Android Head-Units] haynesteve:
Here you go, hope it does some good.
[Android Head-Units] realzoulou:
See Post 2468 for instructions on how to become beta tester
[Android Head-Units] realzoulou:
Perfect log !! Thanks a lot :highfive:
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

would it help to set logging to verbose to debug wrong bitrate on Intel SoFIA device? Or should i test all previous versions of DAB-Z until i find the version where OMRI showed proper bitrate? I remember that i have seen proper bitrates on older versions (last year november ?), so it would be possible to see with what OMRI version it was broken/started to show wrong bitrate for high values...
[Android Head-Units] realzoulou:
Yes, OMRI verbose logging on current version should help me to analyze your problem, too
[Android Head-Units] Firsave40:
Thank you
[Android Head-Units] VBA_Dev:
For some reason, I cannot get the bbc2 log via terminal to work. It creates the log but it’s always blank - tried 3 times following instructions to the letter including upper/lower case. I’m glad [MENTION=2784358]haynesteve[/MENTION] was able to capture one though :)

---------- Post added at 09:56 PM ---------- Previous post was at 09:56 PM ----------

For some reason, I cannot get the bbc2 log via terminal to work. It creates the log but it’s always blank - tried 3 times following instructions to the letter including upper/lower case. I’m glad [MENTION=2784358]haynesteve[/MENTION] was able to capture one though :)
[Android Head-Units] lonnebol:
Maybe it had already been mentioned here, but I could not find it.

I installed DAB-Z on my Android unit with Android 9. It works great, except for the fact that the app asks to start automatically when the unit starts/ask for permission. I disabled and enabled this option in the settings, but still I get the pop-up at start-up of the unit. The unit is in sleep mode when the car is off.

Is this necessary or how can I avoid this at each start-up?

Verstuurd vanaf mijn Lenovo P2a42 met Tapatalk
[Android Head-Units] realzoulou:
You need to tick the checkbox in the dialog that you show in your picture. This is unavoidable. Then this dialog should no longer come up after resume or startup.

If you don't want that DAB-Z starts automatically when DAB USB adapter is found by Android at startup/resume, then deactivate this option in DAB-Z settings
[Android Head-Units] lonnebol:
[MENTION=7838245]realzoulou[/MENTION]

So it's automatic startup of the app at the start of the unit or the pop-up each time?

Verstuurd vanaf mijn Lenovo P2a42 met Tapatalk
[Android Head-Units] realzoulou:
The pop-up should only come once after you start the app after installation. You must tick the box in the pop-up, otherwise the pop-up comes after every startup of the unit.

This however causes Android to always start the app when it detects the USB dongle. To avoid this, I have added the option in my settings.
[Android Head-Units] lonnebol:
Ahhh, ok. So start-up in background?

Verstuurd vanaf mijn Lenovo P2a42 met Tapatalk
[Android Head-Units] realzoulou:
No, Automatic start ...
[Android Head-Units] realzoulou:
DAB-Z release 1.7.82

DAB-Z release 1.7.82

Change log:

Bugfixes

* introduced in 1.7.81 (beta): After bringing already running DAB-Z to foreground, Settings cannot be opened for several seconds

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: 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] lonnebol:
Isn't it possible to not auto start the app and not have the pop-up when the usb connects? I don't want autostart, nor do I want to press anything regarding the app when the car starts. When I went to listen to DAB I will start the app manually.

At this point I am considering to delete the app for these reasons, although the interface is great and the app works like a charm.

Verstuurd vanaf mijn Lenovo P2a42 met Tapatalk
[Android Head-Units] NogenLunde:
Of course this is possible: Settings, do not auto start when DAB USB dongle is detected. And tick to not show the pop-up next time.
[Android Head-Units] lonnebol:
I believe I already tried this before, but still the pop-up comes up. But, I will try. [emoji846]

Verstuurd vanaf mijn Lenovo P2a42 met Tapatalk
[Android Head-Units] costyg79:
hi guy's

sorry if i ask a stupid question, i'm new to this topic

DAB-z application is compatible with car android head unit (i have the 8227l model running on android 9) or i have to install the old DAB+ app?

tkx
[Android Head-Units] boss126:
This works great

http://www.ebay.co.uk/itm/DAB-Digit...447562?hash=item1a2dacc70a:g:7k4AAOSwFgtZeGBS
[Android Head-Units] doraimontv:
Thank you! Do you use DAB why not like original radio?
[Android Head-Units] pwood999:
I just tried this Witson DAB app on my Joying Intel Sofia. It does work using the same eBay USB dongle and finds same number of stations as RealXoulou app, but it has issues. App is slow & sluggish. Many UK station logos are missing. Have to tune each station manually before saving as favourite. On the plus side, it has an "auto follow" feature (cant remember exact name), which I assume is similar to AF station retuning on RDS radios ?

But, now removed the Witson & re-installed RealZoulou version, because it is much better overall.

Station Logos would be really useful.

Pete
[Android Head-Units] Tumke32:
I'm using a Joying dab USB dongle in combination with a hui sold by witson. Im using the new app from witson, in my case its fast, and it find much more stations than the old dab app. In the netherlands, were i live theres only one logo avaible (classic fm)....so different machines, different experiences.
[Android Head-Units] hans.vinkers:
I tried the witson app also but went back to real zoulou. In the witson app I get station logo on the right (after a few moments, sometimes minutes). For me the station names are to hard to read while driving.

Ps. All stations have logos in the Netherlands. They are broadcasted like a beacon every couple of ? Seconds or minutes

Verstuurd vanaf mijn Z2 Pro met Tapatalk
[Android Head-Units] Tumke32:
Yes indeed all stations have a logo, but they are not shown in the stationlist beneath. The logo's are shown only if you select a station than it appears (on another location than the stationlist) after 2 of 3 minutes.

I dont understand why they didnt choose to download the stationlogo to stationlist and save the logo there.
[Android Head-Units] realzoulou:
I feel I need to explain a few things regarding "station logo".

DAB does not broadcast station logos. It broadcasts a socalled slideshow (SLS). The SLS is a set of 320x240 pictures in png format, sometimes also jpg is used.

Some stations do not send an SLS at all.

Some send the same one and only picture again and again.

Some update the picture every minute or when the song changes.

Some send pictures with categories ("catSLS"). This App here cannot deal with catSLS and I cannot add support for this, because the decoder portion is done in a native library called libdab.so, which I am unable yo modify.

How fast the picture is updated depends on the bitrate that the station uses to encode it. Every station can be totally different.

What you see as station logo in the Witson app in the station list are predefined pictures that are contained in the App itself. The file is called dab.bin, but the format is not known to me, so I cannot tell you how to add any station logo there.

I plan to have support for station logos in my masterpiece release. But I have not even started with the necessary mods, and I guess the changes will be huge... So dont ask me for a date.

Technically it will be a solution that uses Volkswagen provided station logos, which they provide on the Internet free to download for everyone.
[Android Head-Units] SpeedFerret:
So the Radio Tuner knob works in the correct direction. But when I've put an microSD card in, the scroll button works as per DAB. ie scrolling down on the MFSW, causes the previous station / track to be selected.

Happy holidays everyone !
[Android Head-Units] A_hijazi_:
Hey Guys

sorry if this is a repetitive question , but i just received my head unit, from seicane 7.1.2, does this app work with nougat? , or only lollipop?

and if anyone can help me, my dab+ doesn't get any signal, and neither any channels!

the light on it works just fine,

please help
[Android Head-Units] SpeedFerret:
Back from holidays. So the Radio Tuner knob works in the correct direction. But when I've put an microSD card in, the scroll button works as per DAB. ie scrolling down on the MFSW, causes the previous station / track to be selected.

Happy holidays everyone !
[Android Head-Units] realzoulou:
It works for sure also with Android 6.

I tested the app with a 7.1 running on the Genymotion emulator. So it should work for you, too.
[Android Head-Units] pwood999:
Just found the small "station change" notification bar when using the DAB app in the background. This pops up when changing stations using my steering wheel buttons and, either with another app foreground, or just home screen.

Is there any way to make this notification bigger? (or at least the same size as the other test on the home screen)
[Android Head-Units] ch_swat_89:
I'm not able to install the app. "App could not be installed"

What's wrong? Root needed?
[Android Head-Units] zeMadCat:
Uninstall the old DAB app before you install this
[Android Head-Units] ch_swat_89:
Thank you, now it's working like a charm.

Will there be an update to use FM when DAB is not possible? I had this on my original VW Unit.

Regards

ch_swat_89
[Android Head-Units] rknuette:
Two different apps, therefore no.
[Android Head-Units] viktste:
Hi. I just replaced the original RCD 310 in my Golf mkVI with a Joying JY-VM130N2D with the DAB+ dongle. The main reason for doing that is because a lot of the radiostation no loger transmit on the FM band anymore in Norway. First impressions of the Joying unit is faily good, but I was not very impressed by the DAB+ app. Especially the Graphics flikker with the signal strength bars annoys me. So after some time on Google I found this thread, manned up and installed the latest Zoulou's mod.

It works like a charm - thank you for making this. :)

Will be watching for the station following update

:good:
[Android Head-Units] hans.vinkers:
What antenna are you using?

Verstuurd vanaf mijn Z2 Pro met Tapatalk
[Android Head-Units] viktste:
I use the original DAB antennae that is in the back window in the Golf, as my RCD310 had DAB (but not DAB+). I just cut the plug on the DAB antennae cable and mounted one that fits the Joying USB dongle. Unfortunately reception is not all that great so I might have to look into how/where to mount the Joying antenna instead...
[Android Head-Units] besty10:
Hey team.

First of all, thanks heaps for all the work and answers that have been put up here.

I purchased a generic usb DAB dongle from ebay (i am not allowed to post the link of the item) that has the FC0013+RTL2832U chips, but when i open the app it just sits there spinning on "searching"

Is that something to do with the usb device i have bought or have i not done something correct? i have uninstalled all previous dab software, tried rebooting and multiple installs using different versions of the software you have uploaded.

Any info would be muchly appreciated.

Christ