yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

i still use old libdab.so mode, as it is still more stable (in OMRI mode i get crashes 2-3 times a week). Another reason - i still use recording function there, which is not available (yet ? ) in OMRI mode.

The problem: all records i made play slower than broadcasts. Whether those have wrong flag or whatever else reason - it seems that these AAC files are played with sample rate 44100 Hz, though really they have 48000 Hz:

Audio
Format : AAC
Format/Info : Advanced Audio Codec
Format version : Version 4
Format profile : LC
Bit rate mode : Variable
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 kHz

I have tried several players on Android (JetAudio, AIMP, TotalCommander), different android devices (headunit and cellular), different players on WIndows (MPC-HC, VLC) - it is always slower than it should be. If you want, i can send you samples in AAC and appropriate full songs in MP3 with proper playing speed to compare.

I think that it has something to do with sample rate flags/samples (44.1k vs 48k) or some unnecessary resampling step.

Can you check the way it is recorded?

Thanks in advance.
[Android Head-Units] stesofeu:
Hi I use DAB-Z while IGO Navigation is running. If an announcement of the navigation apears, dab Sound is totally muted. I use Android 8.0.0 with Csn2 Firmware. Sound Level in DAB-Z is set to 50

%

FM Radio is fade.d down perfectly. But DAB - Z will be muted totally.

Any hints or solution?
[Android Head-Units] IG_Vasilich:
[MENTION=8828575]stesofeu[/MENTION]

Your firmware version is very specific to your headunit, so it doesn't tell much to other users.

What behavior shows your HU when using external music player and IGO?

FM radio can show different behavior as in many HUsFM radio channel is controlled directly my MCU, and Android audio channels can behave differently from FM radio.
[Android Head-Units] stesofeu:
Other players like Amazon Music Player behave exactly in the same way: no music while navigation announcements.

But I found out that if I firstly start the FM radio app and after that DAB-Z, the sound seems to be switched to the radio app, which is faded during the navigation announcement takes place and after that the music player is switched on and runs with normal volume level.

So maybe during navigation announcements it is switched to the radio app. But if this radio app is not running no music sound is played. After finishing the announcement the music player is activated and the music is played.
[Android Head-Units] realzoulou:
I did some tests on Intel Sofia and PX5 based devices and unfortunately you are right. Recording audio for 1:00 min results in a file of 1:05 min audio data in it.

Bad news: I do not see what I could do to fix it. I went through the code path of how recordings are created, but I see no reason why the recording is slower than real-time (or where the "extra" data comes from).
[Android Head-Units] sleis:
Android Auto support

Hallo.

Thanks to this App i have a working solution for dab+ in my car. My installation is a galaxy 8 as a headunit connected to my oem car monitor. The galaxy 8 connects via a usb hub to the neotone DRB-100X tuner.

I wonder if this App should work with Android Auto or not. In my scenario the app works perfectly but it is not recognized by android auto. Are there plans to make it work with android auto ?

Thanks for this app, its awesome.
[Android Head-Units] IG_Vasilich:
as i said - it can be some kind of hidden sample rate conversion. E.g. wrongly treat incoming 48k as 44k1 and convert it to 48k (adding samples).
[Android Head-Units] Alexander_Kwame:
when I update the channels or re-tuning (keeping the favorites), the stations are duplicated if there is a change into: the station name, the bitrate etc...

is it possible to overwrite the channels that have the same country, ensemble and service ID when I do it?
[Android Head-Units] f465gt:
I found another issue (unfortunately). When I set the app to be closed when another music player starts, DAB-Z does not start to play again when I open it. If I switch the stations it works. The strange thing is that it shows full reception.
[Android Head-Units] realzoulou:
If you are using OMRI mode, then this issue is known to me and will be fixed in the next release.
[Android Head-Units] Gman2oo6:
[MENTION=7838245]realzoulou[/MENTION]

Any news with this unit ? ( Ownice S7001 K3 High unit )

still stutters and stops with this one
[Android Head-Units] Alexander_Kwame:
Where is the issue fixed in OMRI?

This Post 2190 or Post 2191

Thanks
[Android Head-Units] f465gt:
It's my issue with resuming playback. It is there if I switch OMRI on and it vanishes if I don't use it.
[Android Head-Units] Alexander_Kwame:
Any news?
[Android Head-Units] f465gt:
What happens if you disable OMRI and re-run a full search?
[Android Head-Units] Alexander_Kwame:
OMRI is disabled.

if I run a full search all station are overwritten, but when I "update the channels" or "re-tuning (keeping the favorites)", the stations are duplicated if there is a change into: the station name or the bitrate etc...

[/QUOTE]
[Android Head-Units] realzoulou:
Switching to OMRI mode helped for quite a lot of devices that stuttered with the legacy libdab.so. Please try it out.
[Android Head-Units] realzoulou:
Yes, this is true. I hope this is not a problem that occurs every time when you do a scan. I assume this is a problem only once when a station changes such parameters of their broadcast. Am I right? You can delete such an "orphan" station from the list.
[Android Head-Units] Alexander_Kwame:
Yes, i true!

I can delete the orphan station... could you overwrite the station that have same ensemble and service ID during the tuning?
[Android Head-Units] realzoulou:
Google Play release 1.5.61

Google Play release 1.5.61 is available now

Change log:

New

* DLS text changed from scrolling to multi-line

* Recording a logcat via Settings/Info on rooted devices asks if a system-wide logcat may be captured

Bugfixes

* OMRI only: deleted station is shown again after restart of app

* OMRI only: scan with option "Replace entire station list" does not really clear station list

* Several stability and performance optimizations
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

thanks for new version.

Is there a plan to implement recording in OMRI in near future?
[Android Head-Units] sim1964:
I am having problems with the OMRI part of this fantastic app, I have been running the last but one version from the Play Store and using the old libdab.so version all my stations play absolutely fine here in the UK, however when I try to use OMRI, BBC radio 4 causes the app to crash within a minute every time. I have tried a couple of other stations and they have played ok without a crash. I also notice that with libdab.so the app reports BBC Radio 4 as being 80kbps while OMRI reports 128kbps.

I hope it will be possible to fix as I tend to mainly listen to the above station. I tried to make a logcat but was unable to do so.

Sim

edit to add I have tried the latest release and there is no change
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION], the last 2 days DAB-z is running in resets every now and then, without any visible reason, just when playing in the background.

OMRI as interface active.
[Android Head-Units] Ben.suffolk:
Yes I had to stop using omri for this reason. The first version with it worked fine, but then after the first upgrade, a month or so back, this started happening and it became unusable.
[Android Head-Units] f465gt:
Hi,

I just updated to the latest version and the OMRI issue I had is now different. Before it was that DAB-Z won't re-start playing when I came from PowerAmp. Now the issue is that the sound get's some strange echo. This echo stays even if I switch to another station and back. Also if I switch to another station, go to PA and back, then suddenly both stations show this echo. If I switch to a third station everything is fine, until I go back to PA. And so on...
[Android Head-Units] sinbrad:
Is it at all possible to adjust the size of the information text as it is way too small on a 7" head unit?
[Android Head-Units] sinbrad:
Were any of these implemented, especially point 2
[Android Head-Units] ozzybon:
DAB app

Yes they have all been added. If your thinking about getting a dongle that can use a DAB+ app then look no further, Real Zoulou's app is superb
[Android Head-Units] mrolek:
DAB app

Love your work [MENTION=7838245]realzoulou[/MENTION] DAB-Z works great!

Maybe im a noob :confused: or there isnt any way to tweak this by now. But can anybody help?

1. Favorite list: Is there a easy way to relocate stations?

2. Full screen: Is it possible to integrate a clock in fullscreen?
[Android Head-Units] cmderks93:
Hi,

Anyone any suggestion about the best adapter? I'm also wondering if the start post is still actual? I see some links are not working anymore. Thanks!
[Android Head-Units] ba55bar:
Re: stuttering.

I tried the suggestions I found but none worked. What eventually fixed it was turning off 'suppress audio distortions'. The stuttering was only on dab+ (AAC), never had a problem with dab (MP2).

Brilliant app, been using for over a year now
[Android Head-Units] VBA_Dev:
Yes, I’ve found issues with the supress distortions option too. Just not had time to video or report it.
[Android Head-Units] VBA_Dev:
Made a recording of a uk station with the suppress issues.

https://1drv.ms/u/s!AkqUSuFd07nW1ybzamlQzYzONDvI

Photo shows station bitrate etc
[Android Head-Units] Forester_Diesel_CVT:
Hello,

......with the latest Version (1.5.61) i have a little issue - when i change the station sometimes the volume goes down.

When i restart the app the volume ist ok again.

I installed the previous version - everything is ok.....

I have a Dasaita Max6 (px6/4GB/64GB)

....any idea?

I really love the app - thanks for your work!

Best regards
[Android Head-Units] blue_one:
Is there a widget for dab-z out there?
[Android Head-Units] stesofeu:
[MENTION=7838245]realzoulou[/MENTION] Thanks for that great app! One suggestion for one of your next updates: while sound recording is enabled the station label isn't centered anymore. It's just an optical issue but it should be easy to solve ?
[Android Head-Units] okij:
+1 :)

It would be awesome if DAB-Z had some built-in widgets which can be put on the home screen, like

display the current station name and the current track information

start a specific station

switch to the previous / the next station in list.

[MENTION=7838245]realzoulou[/MENTION]: Are there any plans for this?
[Android Head-Units] rigattoni:
If you guys want a widget which shows DAB-Z, you should have a look at FCC Car Launcher.
[Android Head-Units] japioothuis:
Or use Agama Car Launcher, it also does.

And it's a beautiful great launcher.

---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ----------
[Android Head-Units] ozzybon:
I too use Agama Car Launcher but its development seems to be none existent. I wish we could get the developers to do something like real zoulou does and talk to its users.
[Android Head-Units] igogu:
Hello,

I am using the DAB-Z on an Android 9 head unit instead of the pre-installed version, is light years ahead of the old one, brilliant reception and top graphics, but I have the following annoying situation:

- if IS set to start when USB device is recognized, after reboot, somehow 2 instances are started and I need to kill both and start a clean instance again

- if is NOT set to start automatically when USB device is recognized, after unit restart, DAB-Z is asking always for USB permission, there is a way to store / remember the USB permission for DAB-Z?

Regards,

J.G.
[Android Head-Units] realzoulou:
[MENTION=5351345]igogu[/MENTION]

"somehow 2 instances are started": This should be impossible. I tried to reproduce such situation but I never succeeded. A system-wide logcat (DAB-Z Settings->Info) could maybe help to understand what is going on on your device. Start the unit and when you notice that there are 2 instances of DAB-Z, use one of the two and create the systemwide logcat.

"NOT set to start automatically ... DAB-Z is asking for USB permission" maybe this is an effect of the "2 instances issue".
[Android Head-Units] pogit:
I have the two (or more) instances problem as well. I’ll try and get a log sent off. I does appear to be linked to the USB auto plugged in and or the delayed start. My unit does have usb/Wi-Fi/Bluetooth issues on occasion if some apps start up before the system fully up and running. Auto sleep / timed & wifi sleep settings seem to have something with that issue but I’ve not found exactly what the source issue. I believe it’s likely to be settings that don’t save properly when changing any of the above.
[Android Head-Units] rigattoni:
I was able to reproduce this issue.

At least 4 instances of DAB-Z in the last active apps (Seems that they are not closed completely).

One instance in foreground playing and second with a delay of some milliseconds too. Sounds like hall.

View attachment dab-z_2019-11-01_11-23-53.zip
[Android Head-Units] tangcla:
I too can confirm the duplicate instance issue, sounds like an echo as described above.
[Android Head-Units] VBA_Dev:
Had this myself too a few days ago.. sounded very odd..
[Android Head-Units] surfer63:
Maybe you already understand the issue ;), but I had the same too a couple of times last week. At least 2 instances running with really awkward sound. To me it looked more like it was pushed to the background and when the other app ( the builtin joying radio app with RDS traffic information) stopped, suddenly 2 DAB versions were playing.
[Android Head-Units] realzoulou:
No, the log from rigattoni did not help me to understand the problem. Please send more logs...

Gesendet von meinem SM-G970F mit Tapatalk
[Android Head-Units] igogu:
Hello gentlemen’s,

today I did more tests and I can summarize (maybe this behavior is related to the Android Pie or to my head unit (A-Sure))

1.	Independent of 1 or 2 or more instances are started, always after reboot is asking for permission if the I am not clicking “Always open DAB-Z when DAP USB Dongle is connected”:

https://imgur.com/Gv3I7mb

2.	If “Always open DAB-Z when DAP USB Dongle is connected” is enabled in this dialog window, then the setting in the app “Automatic start on USB device detection” has no effect.

The DAB-Z is started always automatically

https://imgur.com/dIzxnWP

3.	I have no problem to start 2 instances, but something like this is happening, the DAB+ radio stations signal is with not present and nothing is working till the next could boot.

https://imgur.com/0mtfFsd

4.	The DAB-Z is started even before the home app:

https://imgur.com/cBxuBMc

https://imgur.com/tONXRNh

https://imgur.com/AxDMeui

5.	I have collected more logs maybe you can figure out what is happening:

https://gofile.io/?c=SnE2xn

Best regards and thanks for your support!
[Android Head-Units] realzoulou:
Thanks [MENTION=5351345]igogu[/MENTION]. Your logs clearly show that two instances are running. You have a PX30 device (rk3326_mid). I am astonished that you are not using the OMRI mode. I thought PX30 stutters with the legacy libdab.so. I see that DAB-Z seems to crash quite often on your device in libdab.so. Could you try to switch to OMRI mode and test if this somehow "magically" resolves the duplicate DAB-Z instances?
[MENTION=2534110]rigattoni[/MENTION] however has OMRI mode already enabled, but he has a PX5 (rk3368).

You both have Android 9. This is so far the only common fact but still leaves me with no clue how I could avoid what you guys see...
[Android Head-Units] VBA_Dev:
[MENTION=7838245]realzoulou[/MENTION] I’m on android marshmallow and also using omri mode, and I had the two instances too - not had it happen again yet. Running FCC Car Launcher if that helps too.
[Android Head-Units] rigattoni:
hmmm.... I´m on FCC Launcher too.

May be this a relation?
[Android Head-Units] VBA_Dev:
Are you also running the alphas or betas?
[Android Head-Units] igogu:
Hello,
[MENTION=7838245]realzoulou[/MENTION] thank you for suggestions, maybe will sound like ignorance :), I have clicked in the past for a couple of time OMRI option but then no sound was available, is needed to install some additional libs for OMRI or just to reboot the unit? This is the reason that I have reverted the OMRI to the legacy lib.

The same behavior is with the unit native launcher or with CarLauncher which I am using right now.

Regards,

J.G.
[Android Head-Units] rigattoni:
I try the alphas from time to time, but in my car I always use the Playstore version, nothing else.

I´m just using the alpha version only on my units on the bench.
[Android Head-Units] igogu:
Hello,
[MENTION=7838245]realzoulou[/MENTION] : sorry, as I indicated, I was ignorant - my bad: After enabling OMRI (10 min ago), I did a radio re scan and now, I can hear Antenne Bayern with OMRI on :).

As a hint for next release: maybe is not a bad idea to put a remark lile "do a radio re scan after enabling OMRI" in the pop up window with advantages/disadvantages of using OMRI mode.

I will keep you posted here with the App behaviour next days in regards with the number of instances.

Best regards,

J.G.
[Android Head-Units] surfer63:
[MENTION=7838245]realzoulou[/MENTION]: Any idea when you can implement "service following" in OMRI? I must admit I switched back to libdao as "service following" is actually a necessity for the Netherlands. It is the reason why I bought a DAB+ receiver as the Joying radio (in my case) doesn't have RDS-AF at all.

And please understand that I'm immensely greatful about how you greatly improved the DAB+ app already.
[Android Head-Units] pogit:
Interesting my unit is a px3 and I was having issues using OMRI so had left it off for a while but after my post the other day I put it back on and so far touch wood no multiple instances, but I have also changed the Wi-Fi sleep mode to always on and out the auto sleep back on instead of **** down after 30 seconds. (I previously had battery’s drain issues)
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

it is just a gentle reminder to implement advertised recording for OMRi if possible. Low priority.

And thanks again for the app.
[Android Head-Units] igogu:
Hello,

I want to post some updates in regards of the issue with DAB-Z described above:

OMRI is activated, is working ok, the difference in daily utilization between legacy libs and OMRI libs seems to be the speed of changing the senders but the issue with 2 instances persist also with the OMRI mode (not always after unit reboot, but enough to be annoying):

-I believe that the issue is generated by the DAB-Z autostart function when USB DAB dongle is detected, because independent of the settings in the DAB app (“Always open DAB-Z when DAP USB Dongle is connected” ) the DAB-Z app is always started.

-also with OMRI mode and only one instance, after reboot is asking for permission if the I am not clicking “Always open DAB-Z when DAP USB Dongle is connected” as was indicated before here: https://imgur.com/Gv3I7mb

-the logs collected are here: https://gofile.io/?c=e3oqiO

Best regards and thank for support!
[Android Head-Units] Alexander_Kwame:
I tried to update the stations and now it works, but the new parameters haven't overwrited the old one so the station doesn't update.
[Android Head-Units] okij:
From the FCC thread:

Did you fix this bug in the meanwhile and would you mind releasing a new version of DAB-Z? :)

Also I'm curious if you got any insights into this yet. :fingers-crossed:
[Android Head-Units] erik010:
I have an Android head unit in my car and I have "automatic start on USB device detection" turned off in the application settings. However, everytime the head unit starts I get a popup asking "Open DAB-Z when this USB device is connected?" (see screenshot)

How can I prevent this popup from happening? I thought disabling the automatic start in settings should prevent this popup as well, no?

Besides the popup I'm very happy with it, great work
[Android Head-Units] realzoulou:
[MENTION=4916555]okij[/MENTION]: I am about to release a bugfix version of DAB-Z soon, which will fix the "echo audio" for sure. The "double instances" phenomenon maybe too, but I am still not able to reproduce myself. [MENTION=5351345]igogu[/MENTION] is giving great support with testing potential fixes for me.

Regarding FCC not able to start DAB-Z: I tested with FCC alpha 3.318 and DAB-Z 1.5.61 and DAB-Z was always started after a suspend/resume on a PX5 (Hal9k, Android 8). On device restart it was never started, but the root cause is not in DAB-Z as far as I see. Not sure if it is important: I don't have the FCC premium version.
[Android Head-Units] realzoulou:
[MENTION=10329325]erik010[/MENTION]: I think you have the "double instances" problem, too. One of the side effects of this is, that the 2nd instance attempts to get access to USB, too and this brings the popup somehow. I am working on a fix.
[Android Head-Units] realzoulou:
Google Play release 1.5.65

Google Play release 1.5.65 is available now

Change log:

Bugfixes

* OMRI only: When app is closed and then re-opened, audio output has an "echo" (two audio outputs in parallel)

Note: With the fix, also some "no audio" cases should be fixed.

* On some devices: After cold boot two DAB-Z instances are shown in Recents.

Note: It may still occur that two DAB-Z are visible in Recents, but DAB-Z can now cope with this situation. Per my analysis this is caused by the SystemUI or Launcher.

* Stability improvements

Very big THANKS to [MENTION=5351345]igogu[/MENTION] for his support in finding the root cause for the "echo audio/duplicate instances" issues.

Next release will come with a new feature: Sorting of favorite stations
[Android Head-Units] okij:
Thanks a lot for the new release! :)

Unfortunately, even after installing the update, I still experience the echo bug in OMRI mode. :( Also after a full reboot, it still occured this morning. As you know, I'm using FCC launcher, if this matters.

Only force-closing DAB-Z via Titanium Backup fixes this bug for a while. It seems to occur again after the head unit was sent to sleep and turned on again. I've configured DAB-Z to start playing when a DAB-USB-device is detected.

IMHO for fixing this bug you should add a check if an instance of DAB-Z is already running or playing, to prevent multiple instances. I hope that this is possible and that this bug can be finally fixed, because I really like the OMRI mode. :fingers-crossed:
[Android Head-Units] realzoulou:
Please create a logcat from Settings-Info and provide it to me.

If you have rooted, please choose the option to create system-wide logcat.
[Android Head-Units] okij:
OK, I'll do so when the echo occurs again. Root also is not a problem.

Yesterday evening I installed the latest version of the Malaysk Android 9 ROM which now has the ability to configure the Mode button. Before I used FCC to configure the Mode button, which is just a workaround. Maybe my new configuration could have fixed the echo bug (it didn't happen yesterday evening), I will have an eye on it.
[Android Head-Units] blinger:
Anyone else notice when in OMRI mode, when I cycle through the channel list (using up and down buttons on steering wheel) that it would play the channel that was in the middle of scrolling through the list?

Eg

Channels 1, 2, 3, 4, 5

I rapidly scroll (using up or down buttons) from channel 1 to channel 4. But the app plays channel 3.
[Android Head-Units] realzoulou:
Yes, I see this, too
[Android Head-Units] erik010:
Assuming it's part of the just released version I'll a.s.a.p. give it a try and let you know. :good:
[Android Head-Units] blinger:
Thanks for checking. Hope this can be fixed in future updates [emoji4]
[Android Head-Units] Felix de Luxe:
Great App but lost connection so many times and stutters. I have the Eonon DAB+ maybe the antenna sucks?!
[Android Head-Units] realzoulou:
Try the OMRI mode