yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] erik010:
For me, the new version fixed the popup (double instance?) issue :good:

I have one more question; is there an intent that allows changing the channel (next/previous)? If so, what would this be?

Currently the physical controls in my car don't seem to work for this app, so I'm guessing it is sending the wrong intents. Thanks again.
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: This morning the bug occured again:

DAB-Z started playing correctly after waking the HU from stand-by. About 1/2 minute later the echo (or rather flanging effect) started. I took the attached logs (both only App and system wide) soon after the bug occured.

DAB-Z 1.5.65 is in OMRI mode and configured to start when the USB adapter is recognized. I'm using the player widget of [MENTION=4292729]SpeedFire-[/MENTION]'s latest FCC Car Launcher 3.326. Both apps are in the white-list to not be closed in stand-by.
[Android Head-Units] yuukiw:
Really good app sadly the dab + coverage is still shady in my region.

Would it be possible to add a traffic info like service?

On another note would it be possible to get a more traditional layout? With faves as icons on the button while the current station is on the top of the fave bar.
[Android Head-Units] ab1702:
I too use fcc and don’t have either of dab-z or fcc in the whitelist. If dab-z is set to start on usb detection then there’s no need to whitelist it. With fcc there’s a setting to start fcc on boot, so again no need to whitelist it.

I found previously when I did whitelist them for a short while it made things worse when combined with fcc etc.
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: Then this might explain the two instances of DAB-Z: One is still running after waking up from standby because it's whitelisted, the other starts because the USB device is detected.

AFAIK DAB-Z doesn't start playing again automatically when waking up from standby, that's why I also activated the "start-on-USB-device-detected" option.

Of course I can try to switch off one or the other option and see if DAB-Z then behaves as I want it to, but anyway the still-occuring echo is a bug that needs fixing.

P.S.: Could you find something helpful in my log files?
[Android Head-Units] realzoulou:
Yes, the logs were helpful thanks.

It showed me that it is not a problem of two instances of the whole app.

Instead I see that a thread processing audio data continues to run while a new one is created. The old one should exit but is does not.

I see the problem myself in my car, too.

So, the echo audio problem is not fixed, it only changed from easily reproducible to randomly reproducible. I work on it...
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: Thanks a lot for further working on the echo issue! :)

There's one more bug that I get regularly: When I wake the device from standby and DAB-Z starts playing (triggered by the USB device detection), the FCC Player Widget displays the artist and title information in the wrong order.

It should show the name of the radio station in the first line and the info that the radio station currently airs (like "artist - name of song" or e.g. some short news) in the second line, but after starting from standby the order is swapped.

Switching forth and back to my MP3 player app (I use the GoneMAD Music Player) fixes the display order again for DAB-Z until the next standby / wakeup prodedure.

I reported this issue yesterday on the FCC thread in this and this post, but 1. obviously it doesn't occur for other FCC users, using different players than DAB-Z, and 2. I tried today if the FCC Player Widget also displays the artist and title information in the wrong order with the FM Radio app and GoneMAD Music Player after waking from standby, but with those apps it's all correct.

Therefore IMO the issue must be caused by DAB-Z itself. I don't know how the artist and title information is transferred between the apps (by some intents perhaps?), but obviously something is wrong with it.

Could you please have a look into this issue? For me its quite annoying, since in the player widget I use a smaller font for the title display, so that the information that the radio station airs (which can be quite a long text) is fully displayed. When the bug occurs, the information is shown in the artist display (which I have set to a bigger font) and thus cut off in the middle.

Please tell me if you need some further information or if a log can help you with this.
[Android Head-Units] realzoulou:
A system-wide logcat will show if it's DAB-Z or FCC. Attach one here and I'll have a look
[Android Head-Units] realzoulou:
I did a test myself using FCC alpha 3.318 and DAB-Z 1.5.65. Going to suspend and then resume.

The radio station was "ARABELLA KULT" and the DLS text "Sie hören: MICHAEL JACKSON ..."

Look at the picture. I do not see anything wrong from DAB-Z side.
[Android Head-Units] okij:
Since I didn't have to use my car today, after reading your post I tried to provoke this bug on my parking space, but without success.

Yesterday it happened almost every time I started the device from standby, so I guess that it will happen again in the next days. If it happens, I will take some pictures and a system-wide logcat for you.
[Android Head-Units] chancer63:
Is there the possibility to have a custom background picture?

Gesendet von meinem ONEPLUS A6013 mit Tapatalk
[Android Head-Units] okij:
Today this bug happened again and, as promised, I took some pictures and a system-wide logcat.

On the first picture, artist (should have been "WDR 2 Rhein-Ruhr") and title (should have been "Rehab - Amy Winehouse) are in the wrong order. On the second picture, I switched to GoneMAD Music Player, where artist and title are in the correct order. On the third picture, I switched back to DAB-Z, where artist and title are now in the correct order again.

I hope that you can find the cause for this bug. If it's not caused by DAB-Z but by FCC Car Launcher, please give the details to [MENTION=4292729]SpeedFire-[/MENTION].

Thanks in advance! :fingers-crossed:
[Android Head-Units] realzoulou:
See FCC thread post #4715
[Android Head-Units] HaTeNL:
Does anyone know if this DAB receiver will work?

https://www.aliexpress.com/item/4000013360839.html?spm=a2g0o.cart.0.0.53f73c00eCHG5p&mp=1

And another thing I just found is this: https://www.aliexpress.com/item/4000004745716.html

You can apparently use your exisiting antenna and add DAB functionality to it! Anyone has experience?

edit: I just found out by searching in this topic that it will only work if your antenna is not active/amplified. I think mine is in my Opel Vectra C

Thanks!
[Android Head-Units] typos1:
Yes it looks like that receiver will work, but cant say 100% until you get it, you can only use an antenna splitter like that if you dont have a built in booster/amplifier on your existing antenna.
[Android Head-Units] erik010:
For what it's worth I can confirm this one does work (only a couple of Euro's more expensive)

https://www.aliexpress.com/item/329...hweb0_0,searchweb201602_10,searchweb201603_53

Just note that the included antenna is terrible. With it I only received ~10-12 out of the ~40 channels I receive now after using my Cars OEM antenna. I used a splitter like this: https://www.calearo.com/en/products/antennas-adapters/passive-bypass-fm-dab-vw-skoda-7590008 to split the FM/DAB signal such that I'm not losing my original functionality. This product is for audi/vw but you should be able to find a similar product for Opel.
[Android Head-Units] tazmadman:
Hi my audio is choppy and it does not scan all the channels in my area is there a workaround for these issues

Forget it i found the answer :)
[Android Head-Units] liamstears:
Has anyone ever done extensive testing on various DAB usb's to find which offers the best signal reliability?

Although mine works quite well it's still not perfect so if I knew there was a better usb device to use I would buy it...
[Android Head-Units] erik010:
Interesting question. My initial thoughts would be that the antenna and software behind it are the critical parts, with the USB device just being the "dumb" demodulator. I'd expect the software to do the heavy lifting of music frame reconstruction, buffering and alike. Hopefully realzoulou can shed a light on the role of the DAB dongle as I'd also be up for buying a better quality USB dongle if it matters.
[Android Head-Units] liamstears:
In theory I agree with you however I'm using DAB-Z and have a Kinetic DRA-6003 aerial so believe I'm already using the best in that respect and still have some reception issues so the only weak point now would be the USB receiver itself...
[Android Head-Units] typos1:
I ve always thought that inside these DAB modules are all the same.
[Android Head-Units] rigattoni:
It´s nearly the same chip-set used.

I got a test example from Pumpkin a few weeks ago from a new manufacture and this unit has another print layout and seems to be a bit better than the previous version from Pumpkin. I have the same drop outs at the same position (complete shadow of DAB+ even with high end OEM radios), but it seems to be more stable while driving. Nothing else changed as the DAB+ box. It´s on the same place deep in the dash with the same wiring and the same antenna.

Sometimes a change in the print layout of the small board brings some difference. Can be better or not, it´s always a try and error.

But to be honest: It´s not that I would say that the reception would be quite better, it´s more a "feeling".

The reception is still not even really comparable with our high end OEM in the Audi A6.
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: After having used the DAB-Z test version you sent me via PM for the whole week, I am very happy to report that the echo bug didn't occur a single time. :victory: Therefore I think it's safe to assume that this bug is fixed for good. Everything else has been working as before, so IMO you can apply the according code changes to your release version.

Thanks a lot for your work on fixing this bug! :cool:
[Android Head-Units] Tbizzness:
The DAB receiver should work. As for the antenna splitter, don't waste your time and money. I purchased one of these and it did nothing. I ended up replacing the original car antenna which in the end was quicker and a much better option to gain a good signal. Be careful purchasing anything for dab when it comes to promises about antenna quality. Best way is always replace the roof antenna if it's not already dab capable.
[Android Head-Units] erik010:
I don't think splitters are poor per definition. I bought a splitter so I could use the Audi rear window antenna and it made a world of a difference compared to the antenna that was included with the USB device.
[Android Head-Units] typos1:
Yes this is generally the best option as most modern car antenna contain boosters that interfere with splitting the signal and DAB does not give the best signal (not as good as FM) so a roof antenna is a must if you want the best reception.
[Android Head-Units] realzoulou:
Google Play release 1.6.67

Google Play release 1.6.67 is available now

Change log:

New

* Manual sorting of favorite station list:

- Long-press on a station in favorite list and drag it to another position.

- When adding new stations as favorite, these are added to the END of the favorite list.

- The order of favorites is kept even after you have performed a station scan with option "replace" and then added the same stations to the favorite list again.​

* Favorite stations are no longer marked with a star, when favorite list is active because this was redundant information.

* OMRI is no longer considered "experimental".

Bugfixes

* OMRI only: Randomly "echo audio" is audible.

* OMRI only: When rapidly changing stations, audible station is different to what is shown on screen
[Android Head-Units] typos1:
Interesting.

Its a pity the manufacturers dont specify higher end DAB chips in Android units.
[Android Head-Units] rigattoni:
If DAB would be available in China, they would...
[Android Head-Units] okij:
I personally don't see a difference in signal strenght and reception quality, comparing the factory Toyota DAB+ head unit I used before and the Witson DAB+ USB dongle plus DAB-Z app I'm using with my PX5 head unit now.

Both were/are connected to the factory Toyota DAB+ windshield antenna. I still have full reception in our underground parking garage. When driving into a tunnel, the DAB+ signal cuts off after about the same distance as before.

Only difference is that the Android head unit doesn't switch to FM if the DAB+ signal gets to week (I will try to implement this via a tasker profile when I have some time, thanks [MENTION=7838245]realzoulou[/MENTION] for sending me the needed DAB-Z intents). Also sometimes there is some stuttering, e.g. when the Play Store is updating apps, but that is caused by Android itself and not a fault of the DAB+ USB dongle.

So IMHO the reception is on par with a factory DAB+ head unit when the same antenna is used.
[Android Head-Units] typos1:
This suggests that OEM DAB antennas are of decent quality.
[Android Head-Units] royalhawk2002:
I see something different, but on 2 different cars. I have a shark antenna in my jeep (fm, gps and dab) and I found some little areas in my city where the usb dongle signal get weak or disappear. With the OEM Dab on a Nissan juke that doesn't happen.

Indeed, please let us know when you implement the automatic switch to FM. This is very useful!

Inviato dal mio SM-N960F utilizzando Tapatalk
[Android Head-Units] IG_Vasilich:
you cannot compare 2 different installations with different antennas. You need to try to install DAB stick on nissan (at least to use same antenna).

[MENTION=7838245]realzoulou[/MENTION]

I have installed latest version yesterday, ant tried OMRI mode again. It stutters on any station with bitrate 136kbps (hr ensemble) - here in Mayence these are YouFM, HR3 etc., despite of signal level "BEST".

I have switched back to libdab - no stuttering at all.

Other stations with lower bitrate (even on same ensemble - e.g. hr1 with 88kbps) play fine.

So i am back to libdab mode (and it still has recording option, though with little slower speed...)

Do you still have a plan to implement recording for OMRI? It seems not to be a feature used often here, but for me (on libdab) it is a way to remember songs to be able to download it later - just record it, and later listen recordings, decide that this song i want to have, check filename and download it at home :)

And - thanks for the station list sorting function - i had really missed it :) :good:
[Android Head-Units] realzoulou:
Could you send me a system-wide logcat of the issue with the hr station at 136 kbps?

Yes, I am currently working on the Timeshift and Recording feature for OMRI mode.
[Android Head-Units] IG_Vasilich:
unfortunately if i select "system wide log" then there is no log at all in generated zip file. I have attached zip with only dab-z log in the hope that at least this helps to recognize the problem root cause.

Do you have any idea why it doesn't collect logs at all if i select "system wide"?

I am on Joying / Intel SoFIA with Android 6, rooted.
[Android Head-Units] japioothuis:
Goodmorning.

I have a small problem.

Till now I used version 1.4-204-DAB+180804-nousbdf

Works fine for me.

Now I tried V 1.6.67.

In DAB > logos > user I have my own set of logos.

I edited them a bit to make them smaller to display correct in Agama Launcher

Worked always fine with the old version.

Using the new version my own logos also displays ok but after a minute or so it displays the original station logo.

How can I prevent this ?

Oh, b.t.w. using OMRI sound still stutters.
[Android Head-Units] realzoulou:
Then you have not granted DAB-Z su access. Check your SuperUser apk settings for DAB-Z

EDIT: I looked at your trace and the reason for system wide logcat not possible is "/system/xbin/su: invalid option -- d"

I need to go back to my source code why the "logcat -d" ended up as an option for the su binary instead as option to logcat

EDIT2: Identified the problem on DAB-Z side. Will be fixed in next release.
[Android Head-Units] realzoulou:
Could you record a video and post here?

I suspect that the MOT slide show broadcasted by the station looks like the "original station logo".

You can deactive the MOT slide show feature in DAB-Z settings "Layout".
[Android Head-Units] realzoulou:
Typically the USB dongle does not matter much, because they are pretty much all the same inside. The antenna is the most important piece in the whole chain.

However, I have one USB dongle from an Amazon seller called "Cachor", which I tested to be worse quite significantly compared to the one in my car from Joying. Tested under equal conditions, only the DAB dongle swapped. This is why I wrote "typically" above ;)
[Android Head-Units] IG_Vasilich:
thanks. I am a registered beta tester for DAB-Z, if that matters.

Just out of interest - i have read that OMRI supports also SDR sticks (RLT3232?). Do you have plans to support such sticks? Not that i need it myself, but good to know....
[Android Head-Units] typos1:
I would think that would require a complete re-write of the app as the hardware is totally different.
[Android Head-Units] realzoulou:
Registering as beta user does not give any earlier access. I don't use beta releases.

Where did you read this? I am not aware of this.
[Android Head-Units] japioothuis:
Deactivate the MOT slide show feature does the trick !

Thanx
[Android Head-Units] mazda2004:
Station Logo

Hi

Can someone please give me instruction to install station logo to a 10.2 android car stereo

Any help appreciated

Mazda2004
[Android Head-Units] typos1:
There are clear instructions in the thread, use the search function.
[Android Head-Units] VBA_Dev:
Managed to catch an instance where an AAC station would not play from startup. Logcat attached.
[Android Head-Units] realzoulou:
Google Play release 1.6.69

Google Play release 1.6.69 is available now

Change log:

New

* On devices with Android >= 8.0 and OMRI mode enabled: audio fades out and in when changing stations

* With OMRI mode enabled and DAB+ station supporting "DL Plus": Artist is highlighted in bold, Title in bold italic

* Special for FCC: Allow to be launched in background via boolean extra 'remain_background' set to true as part of the launch intent

"DL Plus" = Dynamic Label Plus (German Wiki page: https://de.wikipedia.org/wiki/Dynamic_Label_Segment)

In short: DL Plus allows to specify the

type

of information transferred within DLS text.

This enables DAB-Z to highlight artist and title in the DLS text:

Bugfixes

* yet another "echo audio" fix

* system-wide logcat not working on some devices (e.g. Joying Sofia)

Announcements

* Support for audio recording in OMRI mode coming soon

* Future releases will require minimum Android 4.4

* OMRI mode will become default, legacy libdab.so will still be supported for a while
[Android Head-Units] surfer63:
Thanks for your ongoing development and improvements.

One question though, as I can't find it back in this thread: Does OMRI (already) support service following?

For me that is really the only reason to stay on libdab at this moment (and I hope I'm wrong)
[Android Head-Units] japioothuis:
When you switch to OMRI a popup says it's does not ( yet ) I remember.
[Android Head-Units] rigattoni:
Great support and great improvements. Thanks a lot for your engagement.

Just one question: DL-Plus ?

Don´t find anything about this feature...
[Android Head-Units] japioothuis:
Thanx again for the update .

One question.

Is it possible to backup the stationlist ?

Scanned in the Netherlands I have the stationlist but when I go abroad I will have to do a scan again in that country.

So, can I have a backup of the stationlist for the Netherlands to restore that list when I'm back again ?

---------- Post added at 12:30 PM ---------- Previous post was at 12:25 PM ----------

DL-Plus is an advanced text function that is currently being broadcast as part of the new national DAB+ service in Germany.

Dynamic Label Segment (DLS) already allows a radio station to broadcast streaming text information on the display of the digital radio receiver.

DL-Plus extends this possibility by allowing the listener to choose which text he is interested in. At the touch of a button he can access information such as the name of the artist or the song being played.
[Android Head-Units] realzoulou:
Unfortunately the echo audio still occurs sometimes.
[Android Head-Units] realzoulou:
[MENTION=2534110]rigattoni[/MENTION] I am astonished ;)

Updated the release post with some description and a picture
[Android Head-Units] realzoulou:
Nice idea. I put this into my backlog.
[Android Head-Units] okij:
Oh, that's a pity! Did it already happen again on your head unit with the latest fix? Did you take a log and have some insights what could have caused it?

I have put DAB-Z on the whitelist again, so it stays in memory in standby. If the echo bug happens again, of course I will take a log for you. This might not happen in the next 1-2 weeks though, since I have holidays and won't drive my car a lot.

Anyway, thanks for your countinuous work and the latest improvements on DAB-Z! Merry Christmas to you! :)
[Android Head-Units] realzoulou:
Yes, I captured a log myself when it happened and I found another root cause... again...
[Android Head-Units] realzoulou:
Google Play release 1.6.70

Google Play release 1.6.70 is available now

Change log:

Bugfixes

* Yet another "echo audio" fix
[Android Head-Units] andy1908:
[MENTION=7838245]realzoulou[/MENTION] your app is amazing, only thing I am missing is another Layout..

youtube /watch?v=3yKHXEcglPU

That Layout is insane. Any plans for future? I got that app but missing many options your app has.

Wich you an mery christmas
[Android Head-Units] giant53:
Well, I hope I may differ in taste. I find the DAB-Z lay-out way better than this crap type of app. I really hope that the current lay-out will stay or improved if necessary.
[Android Head-Units] VBA_Dev:
That app is what realzoulou’s version has replaced. Their app is buggy as hell.
[Android Head-Units] chancer63:
A new try.....

Gesendet von meinem ONEPLUS A6013 mit Tapatalk
[Android Head-Units] realzoulou:
No, there is no such possibility and I am not planning to add such feature
[Android Head-Units] Super_paulie:
Can anyone tell me a way to remove the station notification from showing please? I assume because my Dab reception isn't great it keeps popping up over and over again. Thanks guys.
[Android Head-Units] rigattoni:
This has nothing to do with DAB-Z...

Which launcher is used?

I assume it´s FCC, right?

Launcher settings --> Display --> Notifications --> Disable the unwanted settings.
[Android Head-Units] Super_paulie:
Cheers fella, I'll give it a go. I only get it when I use Dabz so I thought that's what was controlling it.

Edit, good shout, that's cleared it. Thanks again.