yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] realzoulou:
I did not spend much time on OMRI the last few weeks, but will pick up again on it the next weeks. I hope to be able to introduce it soon as an experimental feature.
[Android Head-Units] VBA_Dev:
Cool ?

By the way, is there any chance of an immersive mode setting in the future?
[Android Head-Units] Brendo:
Is there a trick to get DAB+ to appear as a music playback control app in Google Maps or does it need to be built into the app?
[Android Head-Units] Bandor:
I have just a Problem with the modified app ZOU-DAB+180804; downloaded from #1265.

I have the radio XOMAX XM-DA708 with Android 7.1.1 in my car an the DAB+ USB Stick which looks like the Joying Digital Auto Radio Receiver DAB+ from the first page.

The first Problem was, that i can´t install the ZOU-DAB+, because the original app an the radio have the same name. The error message was, that the package name is the same like the original app. I can´t deinstall the original app, just deaktivate.

So i used the app "Appcloner" and make a clone of the ZOU-DAB+ akp (change the name and the icon-picture).

Than it was possible to install the ZOU-DAB+. Now i can start the app and search for the transmitter.

The Problem is now, that i have audio shutter though there is no app in the background.

What is the problem? That i installed an clone?

What can i do otherwise?

Or the DAB+ USB Stick?

Which hardware definitely is working (with my xomax radio)?

Allready the Pumpkin Y0251 from the first page?

I hope someone can help me.

Thank you very much.

Greetings

Bandor
[Android Head-Units] realzoulou:
Your XOMAX is an Allwinner T3 unit, where none of my app versions work.

Sorry, but you are stuck with the original DAB+ app.
[Android Head-Units] Bandor:
Thank you for your answer. That´s too bad.

And there is no way to modify this?
[Android Head-Units] realzoulou:
If I knew how, I would have done so already.

Btw. I get more and more reports about Rockchip PX30 based units that also stutter, even with the original Chinese DAB+ app.
[Android Head-Units] Bandor:
Somethimes i have shutter with the original dab+ app too.
[Android Head-Units] stuartj9:
I wonder if you can help. I had an Erisin unit PX5 working with this app. All of a sudden, I got the message attempting to connect to usb. 1, 2, 3, 4, 5 - app closes. I went back to the supplier of the dab unit as I assumed it was faulty. They sent a new one with a display (I can see it powers on). I plugged this on and the same again. I tried re-installing the app and making sure it had the permission set but still the same problem. I replaced the dab antenna and tried different USB ports and USB leads. Everything is plugged in correct and as I mentioned, it originally worked (and really well at that). On the rare occasion, the unit will recognise the dab receiver but no signal and can't load any stations. I'm using a new head unit, again by Erisin (4GB ram) and still same problems. So, 2 dab receivers and 2 different units. Could it be the version of Android I'm running - 8.1?
[Android Head-Units] realzoulou:
Android 8.1 should not be the root cause. From the currently ~14K installations of DAB-Z, ~2K are running on Android 8.1 (based on data from Google Play Console)

I suspect there is a piece of hardware, which is still common between your old and new setup. This must be defective.
[Android Head-Units] typos1:
14,000 ? Wow ! :)
[Android Head-Units] mrbigboy:
hi I bought myself recently a seicane DAB+ usb receiver which is compatible with my unit, to my surprise the original DAB+ app is not present i just wondered if anyone new how to download the original l app thanks.
[Android Head-Units] typos1:
The Seicane looks like one of the satadard adapters that works with this app.

BTW when googling "Seicane DAB" to find out what it looks like I came across a thread in their forum telling you where to download the app. I wouldnt bother as this app is way better.
[Android Head-Units] stuartj9:
I've solved the problem! It seems as though you have to use an Erisin DAB usb unit on an Erisin headunit. They must've forced the units to ignore non Erisin DAB devices!
[Android Head-Units] typos1:
Theres no such thing as an "Erisin" device, they are just a seller, they sell devices from several different manufacturers, so they must check the MCU or something, but I think thats unlikely.
[Android Head-Units] stuartj9:
Yeah, sorry, that's what I meant. Companies just brand them but they're pretty much the same.

Anyway, it is defintely the device. I bought one off Amazon that said it will work with Erisin. THe new DAB box is using the same wires and aerial as my 2 other ones.
[Android Head-Units] Gman2oo6:
Uhhh they send me this link with this apk in it YHX_DAB+20170328

looks like its yours and indeed it stutters i have the Ownice S7001 K3 High unit from them ( android 9.0 DAB+ and much more )

It also just finds around 40 stations and that's not very much if i see what my kenwood could find ( 200 + )
[Android Head-Units] tillnorden:
Logos not syncing ...

UPDATE:

Problem solved: One need to copy the files into the sub-folder called "User"

(storage/emulated/0/DAB/logos/

User

)

After syncing and new start everything was availabe :)

BTW: Great app, thumbs up!

Hello,

I copied the missing logos (downloaded from VW as png's) in the specified folder on my android head unit XTRONS TE103AP (storage/emulated/0/DAB/logos) and did a sync within the app.

Unfortuneatly no new logos showed up in the channel list. Also not after new start or channel search.

What did I do wrong?

Thanks for your help!
[Android Head-Units] realzoulou:
the logo jpg/png files must be in a subfolder of storage/emulated/0/DAB/logos

Example: storage/emulated/0/DAB/logos/VW

The name of the subfolder is irrelevant, but it must be a subfolder of DAB/logos
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

is there any progress with new middleware?
[Android Head-Units] realzoulou:
I plan to release it in a few days
[Android Head-Units] Ben.suffolk:
Amazing, I look forward to trying it out
[Android Head-Units] realzoulou:
Google Play release 1.5.54

Google Play release 1.5.54 is available soon

Change log:

New:

* Only on ARM devices: Optional OMRI middleware can be activated in Settings/General

* Removed possibility to filter stations for PTY/genre

* Added option to enable fullscreen mode (immersive mode) in Settings/Layout

* Added option to disable sending broadcast intents, which typically causes Google Play Music to crash. See Settings/General.

* A few minor UI changes

Further notes on OMRI:

1) OMRI is still in an experimental state !!

On Intel Sofia CPUs it is stuttering continuously. On Intel Airmont it immediately crashes.

Therefore I decided to disable OMRI on Intel CPUs. You will see the option, but it is greyed out.

Following are known issues/differences:

a) quite frequent crashes

b) audio recording is not supported yet

c) ServiceFollowing is not supported

d) DAB signal level is only available in 5 levels, not as detailled as with libdab.so

e) PTY/genre text in station details is only available in English

2) Features of OMRI:

a) better slideshow support.

Stations that broadcast categorized slideshows should now display them.

b) better support for audio format changes.

I expect that the "BBC hourly beep" is now properly handled.

c) faster station change when the new station is from the same ensemble (=frequency)

3) I had no chance to test with DAB-only stations (e.g. in UK). Hope it works at all :)
[Android Head-Units] rigattoni:
Great work so far! :good:

Hopefully you get it working on Intel Airmont devices. That would be fantastic!
[Android Head-Units] laserman123:
Tried new update but no sound output when OMRI selected.

When not selected sound is normal

Using: Erisin Allwinner T8 Android 8.1
[Android Head-Units] DaAntipop:
Do you have DAB (MPEG 1 Layer 2) or DAB+ (AAC) radio services?
[Android Head-Units] rigattoni:
Checked the latest update on my PX5 and it works better than the old implementation. I just have one position where I always get signal loss for ~200m. With the new implementation, same hardware and same antenna the black out is only less than 50m.

No chrashes, no freezes yet.
[Android Head-Units] haynesteve:
☹ sadly I live in the UK, so doesn't work for me. Hopefully one day we'll catch up
[Android Head-Units] Salvo-x:
great version,

- improved reception

- improved speed

- in my opinion, better audio quality

this new version with OMRI is a great choice
[Android Head-Units] Tiemen_Hendriks:
Same here for me, all around improved reception. Thank you very much Zoulou

Verstuurd vanaf mijn ONEPLUS A6013 met Tapatalk
[Android Head-Units] Ben.suffolk:
Sadly it seems that it does not work in the UK. I changed and did a new search (as all stations were, as you would expect, lost). I could see all the stations, but when you select one there is no audio.

Looking on the details of the station, the Audio Codec and Sample rate are blank., but I could see bitrate as 80 kbit/s and Signal Quality was BEST. So I guess its just that you currently don't have support for the codec needed.

This is the main reason I hope we can get it working in the UK :) so let's hope the current no audio above isn't a deal breaker.
[Android Head-Units] DaAntipop:
It also works in the UK with DAB MPEG1-Layer2 services. You just need to install a audiodecoder plugin apk. It uses MPEG123 as decoder.

This is needed because Android mostly provides only MPEG1-Layer3 decoders. Only some manufacturers have a Layer2 codec onboard (e.g. Samsung).

I will post download links for the apk tomorrow.
[Android Head-Units] realzoulou:
Thanks a lot! Even I did not know this. How did you find out?
[Android Head-Units] DaAntipop:
I know OMRI like the back of my hand ?.
[Android Head-Units] DaAntipop:
Hi,

as promised yesterday here is the MPEG-1 Audio Layer-2 plugin app to decode DAB (without the plus) services.

The source: https://github.com/hradio/omri-dabdecoder-plugin

Compiled APKs (debug and release version) under releases: https://github.com/hradio/omri-dabdecoder-plugin/releases

HowTo:

Just download the apk https://github.com/hradio/omri-dabd...nload/1.0.0/dabmpg123plugin-1.0.0-release.apk and install it.

Restart DAB-Z and the UK people should also have audio.

Have fun!
[Android Head-Units] Ben.suffolk:
Great,

I'll give that a go on on the way home

Ben
[Android Head-Units] pky:
This work perfectly after hard restarting the headunit.

Thank you.
[Android Head-Units] DaAntipop:
Great :laugh:

Could you please also check if the problem with the "BBC hourly beep" is handled correctly?
[Android Head-Units] pky:
Here comes one of those annoying posts...

I don't have a clue what that problem is?

I did a quick search of the thread but I haven't been following it closely.

Edit: ok caught up with Ben.Suffolk post regarding it.

I was listening to BBC Radio 4 at the beeps for the PM program at 5 and no slow down on the audio. At times before randomly I have experienced this but didn't make any connection to which stations it happened on. You live and learn.
[Android Head-Units] Ben.suffolk:
That does not always happen ever hour, not sure exactly when they decide to change it, but I’ll keep an eye out for it. Might be more a case of not seeing it for a week or two to be sure it’s fixed.
[Android Head-Units] Ben.suffolk:
Ok, so very odd behaviour this morning, no audio from Radio 4 (OMRI). It was working fine yesterday on the way home after I installed the plugin.

I tried other stations (Radio 2 and Radio 4 Extra) on the same Ensemble (BBC National DAB CE15). And they all worked out fine, showing the codec as MP2 and a sample rate of 48 kHz. They all swap smoothly and quickly, but nothing on radio 4.

I had hoped that at 9am it would start working (one of the times that it sometimes does the change in sample rate), but also no. So maybe today was not one of those days.

I just had an idea that I should switch back to the old method and check what details it was giving for the codec and sample rate, but when I nipped out to the car just now 09:12 it was working, so there must have been a change sometime after the news when that program started which I missed.

I'll try again, in the mean time here is a logcat I captured, which from looking in it I see nothing of interest to help.
[Android Head-Units] pky:
I had no audio last night on BBC 5 live and a local station as well. Will capture the logcat when it happens again.
[Android Head-Units] ZeroZorro:
Hi, slightly off-topic, but would anyone care to share the VW Radio Logo 7z NLD file?

For some reason all files are there to download from VW website except the file for The Netherlands and I (also for some reason) didn't care to backup the file after importing and switching to OMRI deleted those files (and scanned channels) without warning... ;)

Thanks in advance
[Android Head-Units] Chrisu02:
Hello, a great app, thanks for programming it further :)

i have a very noob question, would it be possible / difficult to add support for a second DAB(+) Tuner to have it as Twintuner ?

i`m driving alot through germany, and radiostations do often change frequency at analog, also at DAB+ the esemble frequencies and available stations do change.

BMW`s do have built in Twin tuner, so the second tuner can always scan for new frequency / esmbles that may be available at a better signal quality in the background.

At FM with a single tuner radio it`s normally that you can find a new frequency very fast or do a manual scan to the next frequency.

but with DAB/+ you have to do an entire scan every time you get out of an esemble range and have to search all stations again, which does take a long time.

it would be cool to have such a feature again to do not have the need to sit into the silent car without any music while scanning for new esembles.

a second feature maybe when switching the radio to a different essemble that maybe a other one already is ready for tuning into another one so the change time will be even shorter.

But the main benefit would be to not need to scan manually every time, when a second tuner can scan automatically from time to time in the background (every couple minutes one time).

sincerely chri
[Android Head-Units] realzoulou:
Yes, with OMRI this should be possible and I also consider to add this to my app.
[Android Head-Units] EwaldB:
Great question and a much better reply from developer! :) Thank you realzoulou!
[Android Head-Units] ZeroZorro:
For me in The Netherlands all stations are giving sound except for all 'NPO stations...

Working just fine before switching to OMRI
[Android Head-Units] Flemischguy:
I bought a new DAB+ receiver, a NEOTONE DRB-100X DAB+ on Amazon Germany. I strongly believe that the DAB+ receiver, that i now have, is junk because it stutters so bad, even in regions where the signal is good. I also sent an email to Denison DAB with the question if theire DAB+ receiver would work on our Android headunits. One down side, they are expensive, +170 Euro, but if it works better than the chinese receivers,i would buy one, also because their receivers have their own power input instead the 5 volts through the usb.
[Android Head-Units] Chrisu02:
Have you tried using an USB HUB in between ?

I have the same type, mine is working with a USB 2.0 HUB from HAMA, "HAMA 00012131", its a square typ USB hub like the DAB+ module.

Here at germany you even get it at the local "Bauhaus" center.

The trick does not work with every USB hub, so if you find another one that will work, please tell us ;)

sincerely Chri
[Android Head-Units] DaAntipop:
That's strange as the NPO stations are all DAB+ services. So this has nothing to do with the MPEG decoder plugin.

Could you please try again after a fresh service scan?
[Android Head-Units] realzoulou:
I see reports on the China-RNS forum from users with Pumpkin PX30 units about clear audio when using OMRI.

So, those with stuttering audio on PX30 based units, try the latest release and enable OMRI in Settings/General.

Feedback is very welcome!
[Android Head-Units] ZeroZorro:
Did a fresh scan and also did a 'hctreboot' and again a fresh scan (delete all channels).

Sometimes NPO channels are working, sometimes not and sometimes only after a very long wait. Strange thing is all not-NPO channels are just working.

If I toggle back to non-OMRI it works just fine, toggling again to OMRI it happens again.

To be clear I did not install the MPEG decoder plugin from I few posts back cause I thought it is not necessary for my situation?
[Android Head-Units] DaAntipop:
As far as I can see the Netherlands have no legacy DAB station. Only DAB+ services. Therefore, no plugin needed.

The NPO services are all in the Ensemble called 'NPO' with EnsembleId 0x8001, DAB block 12C, right?

And thanks for your feedback. Much appreciated!
[Android Head-Units] surfer63:
That's correct. All NPO services are indeed in DAB block 12C as AAC+. See here: https://www.radio-tv-nederland.nl/dab/dab-overzicht-12c.html

However, I can/have to confirm zerozorro's "bug" report. All available stations do play, except the NPO ones. Reboots, rescans: nothing seems to help.

Being Dutch I tried to find Dutch info on this topic (omri and NPO), but I can't find anything at all.
[Android Head-Units] DaAntipop:
Alright, thank you.

I will try to find what's going wrong with this services.
[Android Head-Units] surfer63:
I tested this morning again. "Suddenly" NPO 3FM did work. The other NPO stations still did not work. I'm almost 100% sure that 3FM did not work last night.

DAB-z is supposed to write logs to /DAB/Logs, so I created these folders both on internal and external memory, but nothing got written in my case. Not on internal and neither on external memory.

Please find attached a logcat. You can simply search for "DAB", "NPO 3FM", "NPO 3FM Alterna", "NPO 3FM KX Radio"

or "NPO FM" for "wide spectrum" search :)

This morning as of "06-30 07:42:11.548"

(Sorry I did not already provide the logcat last night :rolleyes:)
[Android Head-Units] realzoulou:
Thanks [MENTION=2550900]surfer63[/MENTION] for the log. For me it looks like the AAC decoding does not start for some reason. I will need [MENTION=8485978]DaAntipop[/MENTION] 's help to look into this.

Please note that the functionality that you expected (create /mnt/sdcard/DAB/logs folder to trigger the app to write its internal traces to a file in this folder) does not exist anymore.

I replaced it with the button "logcat and email..." in Settings/Info quite some time ago. For the regular user the previous process was to cumbersome.
[Android Head-Units] surfer63:
:o Sorry. I promise to read better next time .
[Android Head-Units] realzoulou:
[MENTION=1369996]ZeroZorro[/MENTION] Switching from legacy to OMRI (and vice versa) does not touch the logos folder. I just tested it myself and the logo that I added while in legacy mode was still there and visible in OMRI mode.

Actually the logos folder is never deleted, even when you deinstall the app completely. Only the logos/tmp folder is cleared when exiting the app.

Btw.. Not only Netherlands is currently not available from VW's download page... also Germany is offline.
[Android Head-Units] surfer63:
[MENTION=1369996]ZeroZorro[/MENTION]: I'll PM you. VAG does not allow to share these logos.
[Android Head-Units] Tonny-dk:
I just tried to enable "OMRI". There is a visuel bug in the channel names. If they contains special characters, then it shows a "?" instead of eg. "ø","æ" and so on (Danish letters)
[Android Head-Units] realzoulou:
Thanks for reporting this. This problem is ever reoccurring. DAB uses its own encoding called EBU instead of any standard encoding like UTF-8.

May I ask a few questions:

1. Are all texts coming from DAB affected?

These texts are: station name, ensemble name, DLS (the scrolling text below the station name)

2. Are there any special characters just fine, or is no Danish special character correctly shown?
[Android Head-Units] mollernorge:
Help with new headunit

Hi

I had a android 6 head unit for a couple of years before the screen died, i had a usb dab+ dongle on it and it run perfect with the app on the unit. I have now bougth a new head unit with android 8.1 go and install dab z and the usb dongle. My problem is that is stutters alot even on full bars reseption. The player is from Wanqi 2G RAM 32G ROM 9inch Android 8.1 8cores . i can put in more details. Can anyone help me figur this out?

Best regards

Møller

[IMG="Details"]https://ibb.co/sWsCdy2[/IMG]
[Android Head-Units] android9191:
Hello,

this is the best DAB-App I ever seen it, I'm loving it so much! I'm using this in my car on my smartphone, which is connected to my car stereo. I have detect some small Problems with the App. One of these Problems is, that the Station Name and -Text will only be displayed on my car stereo, if I mute the Audio and the player be paused. If I start to play, no Station Name and -Text will transfer to my Car Stereo. I'm using this in my VW Golf 7 with Discover Media.

A wish ahead, can you add a manual tuning mode to the app? This could help me soo much!

Kind Regards
[Android Head-Units] Tonny-dk:
I Took a photo where you can See it.
[Android Head-Units] realzoulou:
See post #1, FAQ item 4
[Android Head-Units] realzoulou:
On first item: I am astonished that this is even possible, but I have no clue what could go wrong here.

On second item: DAB/DAB+ is a digital service, not an analog. IMHO, manual tuning makes no sense for digital services.
[Android Head-Units] realzoulou:
Planned to be fixed in next release of DAB-Z
[Android Head-Units] android9191:
[IMG="DAB Station Infos on Radio Screen"]https://abload.de/img/20190702_20523268j94.jpg[/IMG]

Hi,

thank you for your fast answering!

to get the station name, ensemble and text on the Radio Screen, the Bluetooth Media Player from Discover Media just need a counting time (I think). If I open the Samsung Music Player, play a song (Song Title, Artist, Album will be screen on) and then switch back to the DAB-Z App, the Station Informations will always show.

For the Manual Tuning, I mean it's sometime easier, if I just need to add one Ensemble to the stations, like 11A SWR RP, without to start a complete Autosearch 5A - 13F.

(Edit 04.07.2019) Here I take a Video how I connect it:

youtube.com/watch?v=nsO5TRgGhQw

Kind Regards
[Android Head-Units] realzoulou:
The Bluetooth AVRCP 1.4 specification states that the "Playing time in millisecond" (= the duration of the song) is "optional" and not "mandatory". Looks like some VW engineer has overlooked that ;)

After watching your video I agree with your assumption. It seems that the Bluetooth Audio application on the VW head unit wants to see a duration time at least once.

Of course DAB sends no duration, it is an infinite transmission. I'll contact you via PM.
[Android Head-Units] realzoulou:
Google Play release 1.5.55

Google Play release 1.5.55 is available soon

Change log:

New

* OMRI can now be enabled on all devices. Intel CPUs are now fully supported

* OMRI only: For DAB-only services (MPEG audio format), a dialog pops up in order to install a MPEG plugin from Google Play, if not already installed.

Note: If you installed the MPEG plugin from github (version 1.0), please deinstall and install the v1.1 from Google Play. v1.1 contains a stability fix.

Users with only DAB+ services (AAC audio format) will never see the popup.

Bugfixes

* OMRI only: Special characters are now properly displayed

* DAB-Z MediaSession metadata information:

- Always sends "title". "Title" usually contains the DLS from DAB(+), "Artist" contains the station name. If no DLS is available (yet), then "Title" is filled with station name, too.

- Song duration of 1 sec is reported (fix for [MENTION=10013447]android9191[/MENTION])
[Android Head-Units] VBA_Dev:
Thanks realzoulou

Unfortunately the dabmpg123decoderplugin crashes on my Sofia 3GR in omri mode. Tried several reboots and it’s the same.