yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] DaAntipop:
MOT is short for Multimedia Object Transfer. A protocol in DAB to transfer data other than audio. There are even more services defined which are transfered with this protocol e.g. Broadcast Website (BWS), TPEG for telematic Data or Journaline, which is like Teletext for radio. The most used service is SLS, short for Slideshow Service.
[Android Head-Units] Ben.suffolk:
The new version has a huge bug, after a very short period using OMRI I get stuttering audio, then the app crashes. I have included a log file here to help track it down.

I have tried it with a few different stations, and its the same story. Its always reproducible.
[Android Head-Units] davemazo:
MOT SLS

As VBA_Dev said earlier Thanks for the excellent & comprehensive answer [MENTION=8485978]DaAntipop[/MENTION]. A perfect explanation

You too VBA_Dev, thanks for clearing it up
[Android Head-Units] f465gt:
I am deeply sorry, but how does OMRI work? I am connected to the Internet via a hotspot, but I don't seem to have better reception.
[Android Head-Units] VBA_Dev:
Don’t know why you think OMRI works online?

It’s just a replacement backend library. Dab radio works in the same way using an aerial.
[Android Head-Units] surfer63:
Are you trolling?

If you have a DAB application with a DAB module you must also have a DAB antenna.

Trusting you are sincere:

Digital does in this not mean that it is sent via Internet like you are used to for your phone/laptop/pc.

It is transmitted through the air but no longer as an analog signal, but as a digital signal. So you do need a DAB antenna with your (USB) DAB module. No internet whatsoever.
[Android Head-Units] f465gt:
I just googled OMRI and it stated that it is intended to improve DAB reception by using mobile data. Which seems to be a decent idea since DAB reception in Germany, in cars especially is ridiculous. I am already using an active antenna in combination with a high quality USB receiver. It helped but as soon as you are moving out of urban areas FM is much better.
[Android Head-Units] VBA_Dev:
That’s very long term future. The dev of dab-z has only just built it in and got it working as a replacement for the Chinese middleware that contained bugs and was never updated. Jump back 10-20 pages or so and you will see when he announced the update to use OMRI.
[Android Head-Units] DaAntipop:
Where did you find such a statement about OMRI? A link would be appreciated.

But, how would an IP connection improve aerial broadcast reception, anyhow?

OMRI is intended for hybrid radio. Meaning that you mix up different broadcast and streaming radio standards like DAB and streams via e.g. Shoutcast. One could switch to the streaming service if the aerial reception is too bad and back to the broadcast service when the reception is stable enough again. This is called servicefollowing.
[Android Head-Units] realzoulou:
Unfortunately, the log does not contain any crash. I queried the crash database and cannot find a px5 device crashing in OMRI mode yesterday 24 July.
[Android Head-Units] Ben.suffolk:
I did the log cat after I restarted the app, so I guess it looses the data from before the crash.

It's a shame because it was working fine (apart from the occasional no audio where it seemed to get the bitrate wrong) on the last release.
[Android Head-Units] realzoulou:
Is there a chance for you to capture a full system log while you use DAB-Z to repro the crash? E.g. using adb logcat from a PC via WiFi while both HU and PC are connected to the same WiFi hotspot? If not I guess there are apps that can do that, too, but require a rooted unit.
[Android Head-Units] f465gt:
https://www.radioszene.de/95926/omri-radio-smartphones-wird-besser.html

That is the link. I think I misunderstood the text. I guess the Internet access is a thing that is made possible by the design of OMRI. So it may be implemented in the future.
[Android Head-Units] hhadi:
Hi [MENTION=7838245]realzoulou[/MENTION], thanks a lot for this amazing app and taking time to answer questions. Is it known which sort of data is sent via USB from the hardware once the commands are sent to the device? Is it ETI frame or I/Q raw data or the sound itself? Would it be possible to use this output in a different way? like to dump it to a file or something? Sorry if the question is a duplicate, I could not find my answer in the thread.
[Android Head-Units] DaAntipop:
Hi, you tell the stick to which frequency it should tune. If the stick has a frequency lock and FEC (Forward Error Correction) lock you get FIC (Fast Information Channel) data from a full DAB frame (96 bytes) at a time. After you've decoded the necessary information you tell the hardware which subchannel from the DAB MSC (Main Service Channel) it should send. Then you get the raw MSC data from the wanted subchannel which you have to decode according to the information from the FIC.

So it's neither ETI nor just the audio data.
[Android Head-Units] realzoulou:
Google Play release 1.5.60

Google Play release 1.5.60 is available now

Change log:

Bugfixes

* Fixed crash at loading native libmpg123plug library (affected only some devices)
[Android Head-Units] Ben.suffolk:
It seems to be a little intermittent now, iso I wonder if it's related to the sample rate or some other variable. Its been fine during the day time, but early morning when they have a different sample rate seems to be an issue. Attached is a log that I got, and I can see a crash in it.

On a few occasions it's done the restart of the app several times, and then completely gives up, saying it can't find any hardware. Which no matter how many times I restart it it can't find until I do a power off of the ignition (so I assume the USB receiver gets a full power cycle reboot).

On one occasion the other day it also allowed me to submit a feedback report on crash, which I did, but other times the crash takes that screen away as well once its popped up. So you may have a crash report in your database now as well.

Ben
[Android Head-Units] realzoulou:
Ah, you went back to legacy libdab.so, no OMRI anymore. This is a small but important piece of info ;)

I doubt that your current problems have sth. to do with MP2 audio format, or bitrates. I noticed already in your previous logs and now in this one again, that sth is strange with your USB in general. Not necessarily the DAB stick.

In both OMRI and libdab versions of your logs I see that DAB-Z reports quite often that some other USB device was detached, sometimes also the DAB stick is reported to be removed and then DAB-Z closed itself. libdab.so reports all kind of strange problems to access the USB DAB stick and sometime crashes then. Nothing new, stability was always a major issue with libdab.so

You have a PX5 device. These devices are known to be not best-in-class with regards to the USB controller.

But maybe it is only a loose cable. My test PX5 device also suddenly showed a loose USB cable at the connector at the back of the device. Made in China!
[Android Head-Units] Ben.suffolk:
I thought I I had switched back to omri, I’ll check that in the morning. I have swapped between then a lot to try and track down the issue with it.

It would certainly explain why it seems to be working again...

I have a powered usb hub between the head unit and the dongle, it also has another device on it, maybe I will swap things around and see if that makes any difference.
[Android Head-Units] liamstears:
Been looking for a better DAB app for my system and came across this and it looks great but unfortunately isn't compatible with my DAB tuner

The supplier was suppose to send me a USB DAB tuner but instead they sent one that plugs straight into the back of the unit

Any way to get this to work?
[Android Head-Units] typos1:
Whats your MCU ?
[Android Head-Units] realzoulou:
Most likely not with DAB-Z. I suspect that only the app provided along with this box would be able to connect to it.
[Android Head-Units] Marc NL:
Dab-z/CWG

Hi there,

Is it possible to broadcast the station logo as album art? This way (I hope) it will show up in CarWebGuru and will make the combo Dab-z/CWG even better.

Thanks.
[Android Head-Units] VBA_Dev:
It already is Marc, CWG and it’s lack of updates is the problem I think. Try FCC Car Launcher instead.
[Android Head-Units] Marc NL:
Thanks for the quick reply. I'll give FCC another try then.
[Android Head-Units] liamstears:
csn2_06252019_163051
[Android Head-Units] IG_Vasilich:
or "Car Launcher Pro", if you don't have MTCC/MTCD based HU.
[Android Head-Units] typos1:
Thanks, not the one I suspected it might be, so the solution I had in mind wont work, sorry.
[Android Head-Units] cozzykim:
:good: Success !!!

V1.5.60 is now working perfectly on my Pumpkin 6.01 head unit, pulling in lots of AAC and MP2 stations.

Thanks realzoulou.

This is so much better than the terrible OEM app and definitely worth a donation, one will be on the way soon. :cool:
[Android Head-Units] japioothuis:
Hi,

I installed the latest version from Google Play Store, it's working.

Now I want to add my own stationlogos but cannot find the dir where DAB-Z is installed in the fileexplorer ?

Where can I find it ?
[Android Head-Units] davemazo:
I've found it doesn't work anyway despite following instructions to the letter. I can't get to the car at the moment but if I remember correctly they go into the DAB folder and somewhere in there is a logos folder. It tells you in the Dab-z settings where the folder is
[Android Head-Units] haynesteve:
Have to create a folder inside "logos" folder (eg "user"), and put them in there (160x120 format)
[Android Head-Units] japioothuis:
Thanx for the replies.

I still use the latest not Google Play version and I'm very happy with it, no problems at all but I thought let's give the latest Google Play version a try.

So I installed it but it does not update the old one , I have both now. But I think it uses the same DAB directory because when I synchronise the logos I have my logos in the new version also.

But I will delete the new version I think because when I use OMRI the sound is stuttering and without OMRI it's ok but it seems to be slower.

Back to the old version for now.
[Android Head-Units] Marc NL:
Is it possible for Google maps to recognize Dab-z as a media app? Right now it doesn't and therefore maps doesn't show media buttons. If it is something i can do with the settings please let me know.
[Android Head-Units] ab1702:
On the newer versions you don’t have to use omri, just untick the option in dab-z settings and reboot your device.
[Android Head-Units] VBA_Dev:
[MENTION=7838245]realzoulou[/MENTION] Just an observation on my Sofia 3GR: omri mode uses a lot more cpu ~70% compared to ~20% in original mode.
[Android Head-Units] realzoulou:
[MENTION=9709140]VBA_Dev[/MENTION] Is this with MP2 stations only, or with all stations? I don't see this high CPU load on my Intel Sofia test device.
[Android Head-Units] VBA_Dev:
Not sure, possibly MP2.. will test again over the weekend and take some video
[Android Head-Units] japioothuis:
Yes I know. But that's why I went back to the older version, it is perfect for me and the new version does not add very much for me.

I only wanted to try OMRI to see if it works.

But thanks anyway.
[Android Head-Units] realzoulou:
AFAIK, only Spotify and Google Play Music are supported as media player in Google Maps. This choice is done by Google. You cannot influence it in any settings.
[Android Head-Units] Marc NL:
Damn.

Thanks for the answer and keep up the good work.
[Android Head-Units] VBA_Dev:
[MENTION=7838245]realzoulou[/MENTION] I’ve not been able to replicate the high cpu - maybe something else was going on with the head unit, as it’s been a bit flakey since updating to a beta of fcc- launcher. I’ll keep an eye on it.
[Android Head-Units] Marc NL:
Is it possible to clear the station list completely?

When back from holiday and doing a rescan all the stations from my holiday address where still listed and obviously then don't have reception. Now my station list is filled with stations i can't listen to.

Thanks.
[Android Head-Units] Minotaur:
Do a rescan, and select "Replace entire station list"
[Android Head-Units] Marc NL:
That's what i did but that didn't help.
[Android Head-Units] realzoulou:
Ouch, you have hit a bug in the current version.

You will have to delete the app data in Android Settings - Apps - DAB-Z

Or deinstall and reinstall DAB-Z.
[Android Head-Units] Marc NL:
I'll do that.

Or i will wait for the update so i can test...
[Android Head-Units] VBA_Dev:
[MENTION=7838245]realzoulou[/MENTION] had an issue with no audio when turning on the car to an mp2 station. Logcat attached - time was 12:10 ish. Audio started after selecting an aac station.
[Android Head-Units] pwood999:
Not sure what build I was using previously, but everything working well. Waze & Google Navigation both trigger the DAB audio volume to lower correctly. Only issue has been after incoming Bluetooth phone calls, where DAB-Z remained in Paused Mode. (I don't use other audio apps, so no experience of this issue with these)

*** Updated yesterday to latest version on Play Store (1.5.60), but the pause behaviour is still like this.

Is this an issue with the Joying Bluetooth app not allowing DAB-Z to resume playing, or an issue in DAB-Z itself ?

Thanks,

Pete
[Android Head-Units] realzoulou:
What Joying do you have? Sofia, PX5 or SC9853i ?

Just tested this on my Sofia on the bench and DAB-Z resumes playing after a phone call properly.
[Android Head-Units] pwood999:
My head unit is Sofia. Last updated it Jan 2018, which as far as I know was the last Joying release for my unit.

Pete
[Android Head-Units] jottenn:
**** I have intentionally marked devices called "t3-p3" as being not compatible with DAB-Z ****

I have a t3-p3 Allwinner device and with ticking the OMRI option it works perfect. Great!
[Android Head-Units] apollo1976:
Hi Realzoulou,

congratulations again for your app, it's really the best for DAB, a true masterpiece. I wanted to ask you where I'm wrong in order to view the logos. Practically although I have inserted in the folder user an image with the same name of the radio station it tells me that the name is ambiguous. How can I do??

Thank you!!
[Android Head-Units] surfer63:
On your sdcard is a folder "DAB" and inside it a folder "user".

so copy your icon folder structure below /DAB/user/
[Android Head-Units] apollo1976:
Thanks but I have already copied the image of the radio station with the same name displayed in the app into the DAB/user folder. The problem is that the app recognizes the name as "ambiguous" and does not make the association but the name between image and radio station is identical (see image). I don't understand where the problem is
[Android Head-Units] IG_Vasilich:
"ambiguous names" comes from the way DAB-Z searches for the files: it removes all special chars from station names, then makes the same for filenames found, and then tries to find a match.

Hash sign, ampersand sign and plus sigh are handled as special chars, so after deleting those from filenames you have prepared, it cannot find "better match", as both "#Radio Fresca" and "Radio Fresca" become same after filtering special chars.

So you need EITHER have "#radio fresca" OR "radio fresca" files there. Same goes for other filenames you have put in the logos folder.
[Android Head-Units] apollo1976:
Thanks for the explanation however the association does not seem to work well. The name of the station is #RadioFreccia and in the user folder there are two images called RadioFreccia and #RadioFreccia so with the # and without and the name is identical to that of the radio station. So I don't understand why all two image files are reported as ambiguous
[Android Head-Units] Oberbergler:
How are your DAB+ sticks working? Are there differences between the manufacturers?

I have one from xtrons and it has a terrible reception. My old MTCC headunit had a Shinwa DAB box which had a about 50-60 % better reception. It worked nearly everywhere, also in some tunnels. Now my xtrons PX5 is a great unit which performs very well but the DAB-stick is total crap with the same configuration as the old one.
[Android Head-Units] syk02jcb@hotmail.com:
I have the usbdab01 labeled with xtrons. Works great with a better antenna, I use Funke Adsc710, have reseption in tunnels as well
[Android Head-Units] Oberbergler:
I have the Hama roof antenna but no chance to get a strong signal with usbdab01 from xtrons :(
[Android Head-Units] syk02jcb@hotmail.com:
I don't know the specs on the Hama antenna, but it might be related to the phantom power needed for the Hama. I measured my adapter with 4,7 volts out to antenna, often do active antennas require minimum 5 volts. The Funke wants 5-12 volt, but in my case it seems to be ok with 4,7.

Maybe a phantom adapter will help?

I have a original ford dab roof antenna, this won't give my dab good signal (worse than the one that follows usbdab01). This gave a good signal on my old Sony dab, that unit gave 12 volt out to the antenna...
[Android Head-Units] Jedimindtriks:
USBdab01 from Xtrons is a hit and miss. often times its useless.

cover it in alumium foil. it helps :)
[Android Head-Units] syk02jcb@hotmail.com:
The aluminum foil tip is a good tip, I reported early the adapter's sensitivity to other signals. I moved my wifi dongle to my trunk, it gave much distortion to the adapter mounted in the glove compartment.

But this is also generally a issue with dab, other wires and metal can disturb antennas and adapters.
[Android Head-Units] Oberbergler:
OK, thank you for the tip, I will try it tomorrow. Don`t know why, but after a longer time of use I have now the full reception where I first had no reception. Maybe my dongle works better when it is warm after some time of use. :confused:
[Android Head-Units] syk02jcb@hotmail.com:
If it's from no signal to full signal without you made any major adjustments, there might have been some work on the senders, maybe a new sender in the area. Many countries are building up the dab+ coverage now a days...
[Android Head-Units] Oberbergler:
No, my old dongle worked very well in this area and I`ve got the new unit yesterday. So it went whitout adjustment within this day from no signal to full reception :D
[Android Head-Units] chammock:
[MENTION=7838245]realzoulou[/MENTION]

First I would just like to say good work on the app so far, much improved. I have a few suggestions for some tweaks if your interested.

1. Is it possible to mute the audio when google voice command is invoked. (I am not user if this is something that had anything to do with the app code or not)

2. Would it be possible to broadcast the current station name and info so that it could be referenced by a custom widget or similar. Spotify and I am sure many other apps have a similar function which I use to display what is currently playing on the home screen of my custom launcher.

3. I notice a few discussions in this thread about station art. I don't pretend to know a lot about it but I believe here in the UK at least the DAB signal is broadcast at a much lower range which means audio quality is lower than many other EU countries. I suspect this maybe the reason why we don't waste bandwidth transmitting images. I wonder with the new settings screens you have, how difficult it would be to add an option to freehand in station names and image locations so if the station name you have selected to play matches a configured name in settings then the image associated to that name would displayed.

Thanks again for your work on this.
[Android Head-Units] boss126:
Actually the UK do broadcast the station logos as can be seen from the Witson version.

http://www.witson.com/en/displayproduct.html?proID=102676214
[Android Head-Units] dennydenny:
I've tested the new Version for a while to state that it doesn't behave as expected.

When i turn on ignition there is a message "no usb device" and the app closes instantly. With the

USB Autostart Option "on" the app starts... but it also starts when it shouldn't.

By example when the last app was the music player etc...

Grettings, Denny
[Android Head-Units] kampfschachtel:
With new version of dab+ and 25th may release if I use the dormancy mode after the wake up on my joying the DAB+ app doesn't play sounds but everything else like scan works and shows full reception. To get sound I have to close app and restart it Everytime I start the car. I have gustden no kill mod through surfers extra tool installed. Was working before with previous version seamlessly.

Didn't use dormancy till now but now I do as I could fix the other issues and the bug with FM radio playing at boot drives me insane. so I only discovered this now.
[Android Head-Units] SpeedFerret:
MFSW channel change scroll direction

Ive loaded the 07_26 version and scrolling up on the steering wheel causes the cursor to scroll down on the DAB Station screen.

I'm running a Px5from Gs.

Is this a known bug ?
[Android Head-Units] syk02jcb@hotmail.com:
This is not a reported known bug i have heard about.

Is it only in DAB this happens? Not in FM radio?

Sounds to be a canbus issue, have you set the right on in factory settings?
[Android Head-Units] SpeedFerret:
I just did the upgrade b4 coming into work. Will do Radio testing on my way home tonight. If consistent with DAB I'll then look at Factory ... not that I've been in there b4 ... and check for CAN Bus settings. Cheers.
[Android Head-Units] SpeedFerret:
So the radio moves channels in the same direction as the scroll wheel on the steering wheel. However Dab+ moves in the opposite direction so guess it may be a bug.
[Android Head-Units] realzoulou:
The logos that the Witson DAB App is able to show come from a file dab.bin (in assets resource folder in the apk with a size of 8 MB).

It seems to me that this dab.bin file contains logos from DAB stations all over the world.

But it does not contain all of them and this results in a bad user experience. Look at this picture. In my station list of ~50 stations, only 10 have a logo.

During the station scan, the app searches dab.bin with some 32 char identifier and may find a picture for the current station in it. It then extracts the picture and stores it as png with the identifier as name.

Thus, the logos that the Witson DAB app shows are *not* received via DAB broadcast, but are pre-defined in the app.
[Android Head-Units] realzoulou:
No, sorry. The DAB App does not know when the Google voice comman app is invoked.

Very interesting idea. Yes, this could be done. Question is: Do you have any details on how the Broadcast Intent has to contain?

I have a much better idea in mind that I plan to be part of the "master piece" release.
[Android Head-Units] realzoulou:
This is the workaround that I have put in place in order to avoid the endless "Connecting...." screen. I wonder why you see this message. What started the App?
[Android Head-Units] IG_Vasilich:
read my explanation again. If you won't understand it - then just remove any of above mentioned files, and the ambiguity will disappear.
[Android Head-Units] apollo1976:
Yes perfect, now I understand, the problem is that in the user folder there were two image files with two names similar to that of the radio station and the app did not know which one to associate. I left a single image with the name of the radio station and made the association.

Thank you IG_Vasilich for the great support you have given.