yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] IG_Vasilich:
@royalhawk2002

as always - supply realzoulou with stream record for that case.

Have you seen this issue on one specific station? Are you aware, that SLS pictures aren't transmitted constantly, but in some intervals? Maybe that you have seen is just an incindent (broadcaster has transmitted the picture at the time you have switched)? How long have you waited for picture to appear?
[Android Head-Units] realzoulou:
Just tested again on public 1.8.96. I am not seeing any issues. Station name coloring, text size increase/decrease, signal bar color: All working as expected
[Android Head-Units] royalhawk2002:
This is something that is happening since the last update. Before I write it here, I made several tests. Sometime the image appears immediately, some time not and the only way is to change station and then back. It happen on the same station every time.
[Android Head-Units] realzoulou:
This feature of DAB/DAB+ is called MOT SlideShow ( Multimedia Object Transfer). How quick one image is broadcasted, is up to the broadcaster to decide. Also how often a new image comes in. And of course the content of the image. I deeply analyzed OMRI source code and found no weakness here. What you see is what is technically possible.
[Android Head-Units] ibaxx:
Hi, i have installed the app today. Searching stuck on 0%... Any ideas?
[Android Head-Units] Max-Rockatansky:
Hi, I'm new here, just registered to give feedback / get help with DAB-Z.

I've just installed an xtrons PB80UNV head unit into a 2007 vw golf.

I'm having some issues with DAB-Z as follows... It starts up and works absolutely fine, but after you've changed the station, maybe a couple of times, the audio disappears. It finds the channels fine, signal strength is reported as being good, there's just no sound.

If you close it down and start again it's OK - until you start switching channels.

The supplied dab app from xtrons seems to be ok.

Any ideas?

Thanks for producing / developing the app and for being so accessible for feedback.
[Android Head-Units] typos1:
Yeah, check your antenna.
[Android Head-Units] NogenLunde:
What version of DAB-Z? Try the newest, download link on the first page.
[Android Head-Units] realzoulou:
You are from UK, aren't you? I am already digging into this issue since a week. Some other user sent me logs and raw recordings for analysis. Yes, it's an issue in DAB-Z.
[Android Head-Units] IG_Vasilich:
@royalhawk2002

if you are sure that this started to happen only with latest version - you can use APKPure to get previous version (link in 1st post of this thread) and check whether it behaved different earlier.
[Android Head-Units] Max-Rockatansky:
Thanks for taking the time to reply. Yes, I'm on the newest version, the problem was there on the previous version too.

Yes, I should have said I'm in the UK. Thanks for your reply and for looking into the issue.

For future reference, how do I send logs in the event of an issue?

Thanks again for the support 👍
[Android Head-Units] royalhawk2002:
I will try as soon as my car will be back from the shop.
[Android Head-Units] RvSNL:
hmm, strange, ok thanks for checking. Maybe a complete reinstall of the app wil solve it !? Wil have a try.
[Android Head-Units] Chrisu02:
Hello @realzoulou

sorry to disturb you again.

I am working on background images at the moment and noticed that the station-list bar that show active and selected stations do have a black frame.

would it be possible to remove them ?

Also a cool feature would be if it would be possible to have an option to change the color of the selection for the user :)

May be there a possibility to add an option to also disable the parting line between the station list and buttons ?

When doing a GUI its easier to do a parting line at the background image, with this its easier to "skin" dab-Z better :)

Next question, the images (on the right) are already scaleable which is great :)

But they are always pretty far below at headunits with a wider formfactor :/

sincerely Kri
[Android Head-Units] ab1702:
As a temporary measure go into the dab-z settings and disable OMRI if it is enabled. This should sort your problem until a fix is found.
[Android Head-Units] realzoulou:
I found the root cause and another bunch of "no audio" issues (with OMRI) will be soon gone...
[Android Head-Units] realzoulou:
Hmm, yes should be doable.

To change the color of the selection might be difficult because it is a bitmap currently, and I'm not sure how well tinting would work out.

The logo image looks to be below the center only because of your background image with the horizontal line.

But I am really impressed by your background image (y)
[Android Head-Units] Chrisu02:
I hope that "impressed" was sarcastic, because its really bad quality :LOL:

I only streched the original background image that i have from at the moment at my Android Headunit to have the line lower to fit the DAB-Z design better, my actual GUI is looking like this.

That was also the question for asking for an intent, because for now dab-z has no feature for pause or stop music manually, at least i haven`t found one :unsure:

Kri
[Android Head-Units] okij:
Please see:

Maybe @IG_Vasilich can post some further details about this.
[Android Head-Units] Chrisu02:
Yes i saw that, unfortunately that launcher does not support media intent, it is configured via app intents.

Kri
[Android Head-Units] RvSNL:
Just did a fresh reinstall....problem solved.(y)
[Android Head-Units] IG_Vasilich:
Those are not intents (= events), but app activities (= UI forms).

And that is not in Android design to start or stop players via activities- there are intents for it.

DAB-Z stops playing when you press back button (standard android button), - the app actually exits :) .

@realzoulou maybe it makes sense to show pause button at least when timeshifting is active?
[Android Head-Units] wainsie:
Have a issue with stations stuttering, especially the BBC networks, if I switch Ormi off and back on it goes until next start of the app, been like this for a while now, would I be able to get a raw dump of this with switching modes
[Android Head-Units] realzoulou:
Hi @wainsie , please record a raw recording of this situation. Please switch on OMRI and raw recording mode, then close the app, reopen it and reproduce the issue. Then send me all raw recordings being captured to my known email address.
[Android Head-Units] wainsie:
Hi @realzou have sent you a email, I believe I have done the recording correctly
[Android Head-Units] realzoulou:
@wainsie I see quite a lot of crap data in the raw recordings. These blocks cause the stuttering because they cannot be decoded usefully. I have seen this behavior with several people now already, even saw this with my equipment on the bench, too. Not sure what is the true root cause though...
[Android Head-Units] wainsie:
It's strange, it's only until you disable omri then reenable it then it stops stuttering, like a optimization issue
[Android Head-Units] marchnz:
I found if you pressed back button then opened again, it would go back then open again.
[Android Head-Units] surfer63:
Hi,

I've mentioned this earlier when using Nova Launcher.

DAB-Z always starts after resume. Of course I disabled the automatic start on detection of a usb device.

When I switched back from Nova to CarWebGuru, dab- no longer automatically started.

Now I flashed a a rooted, slightly customized rom of the T'eyes CC2 onto my Joying sc9853i. Everything functions great, but .... the DAB-Z again always starts on resume. Now with the default T'eyes launcher3.

Thinking back about carwebguru I think it is because carwebguru contains its own media player and when you use that one it immediately launches the service. Maybe that overrules dab-z.

Please find attached two logcats (system logcats with root) from the resume of the unit. I can't find any trace of com.zoulou.dab in it.
[Android Head-Units] realzoulou:
Hi @surfer63 I looked at both logs and cannot find any useful info in them at all. Your logs are totally overloaded by a constantly crashing app package com.txznet.txz installed in /oem/app/TXZSmartWakeUp
[Android Head-Units] surfer63:
OK clear, I will make new logs. That app is the T'eyes voice app but it only works after registration and then you get a new library. I already removed parts of it and reactivated the Google Assistant hich now also works when rooted.

I did not realize that the crashes of that app could remove possible com.coulou.dab log entries. I simply thought there were no entries (sames as months ago with Nova Launcher).

I will do a clean flash tomorrow with my further modifications and then create logs again.
[Android Head-Units] realzoulou:
You can lookup in DAB-Z Settings->Info what was the reason for DAB-Z being started. It can have 3 values: USB ATTACHED, LAUNCHER or UNKNOWN. If it shows LAUNCHER in your case after resume, then some software has started DAB-Z using the usual launch intent.
[Android Head-Units] surfer63:
the value mentions LAUNCHER.

When I check the AndroidManifest of DAB-Z I see ".activity.MainActivity" as main launch intent. But that should be complemented with "com.zoulou.dab".

I started with the launchers, but by now I have unpacked (apktool d) all(!) apps of the firmware. There is no reference whatsoever of com.zoulou.dab or "com.zoulou.dab.activity.MainActivity".

I have no idea which app starts this.
[Android Head-Units] realzoulou:
Of course you will not find my package name in the OEM apps, DAB-Z is not that popular yet 🤣

In previous Android 6 FYT ROMs there was a functionality that it kept track of the last MediaSession. When it was not a known (hardcoded list) package name, then the package name was stored as "third_player" in a FYT properties file and launched when the user pressed the Media hard button on the device. This "feature" irritated a lot, when I had my Intel Sofia unit, because the Media hard button changed it's behaviour all the time when using several media players.
[Android Head-Units] surfer63:
Well, I was also really surprised when you mentioned

That is when I started searching for the launch intent in the apps.

And I don't have a Media hard button. I have a unit without buttons (apart from Home, Vol+ and Vol-)

Can you remember the name of that Fyt properties file? Was it the standard one containing many settings, or was it one of the number of files inside /sys/fyt. I also wrote a post about that one and what the values were, but it's so long ago I can't remember :), but I can find it back if that's the one.

If it is another one, please let me know.
[Android Head-Units] realzoulou:
I found it in a decoded app of my Flyaudio SC9853i based unit. The app was 190000000_com.syu.ms.apk.

It uses a property "persist.sys.syu.thirdplayer" to store a package name. If I am not mistaken, then this app uses the Android System Properties environment to store such kind of settings. A "getprop" command should also show the setting.
[Android Head-Units] surfer63:
The "persist.sys.syu.thirdplayer" is indeed in the main server apk (together with "third_dvd" ? an external usb-connected CD/DVD?), and the property is indeed set to "com.zoulou.dab"

In a rooted terminal I can do a

rm /data/property/persist.sys.syu.thirdplayer

or simply

setprop persist.sys.syu.thirdplayer ""

, but then it still doesn't work although the value is nicely cleared. After resume it is back on com.zoulou.dab.

It works the same for other media players where the same property is set when used as last media player. It simply sets the last used media player, which as such is a very nice feature, but mediaplayers start in "pause" mode and do not play immediately (unless they have a setting for that).

Only DAB-Z immediately starts playing, which as such is the completely normal and logical option for a radio app, I assume.

So I further analyzed what happens during resume. For this I also needed to disconnect the DAB dongle in the several tests and disable DAB-Z (settings->apps):

The last used media player is set in the persist.sys.syu.thirdplayer (and maybe MTC units have something likewise)

Without DAB-Z (disabled and dongle disconnected):

The last media player is re-activated and starts in paused mode (unless it contains a setting "resume playing on startup")

With DAB-Z

With DAB-Z, it reacts on USB_ACCESSORY_ATTACHED and/or ACTION_USB_DEVICE_ATTACHED

DAB-Z starts and checks the setting to start on usb-connect. I disabled that setting inside DAB-Z, so DAB-Z closes again (I assume).

In the mean time however, the persist.sys.syu.thirdplayer is already and again set to com.zoulou.dab

And thus: the main server starts DAB-Z.

So....: Can I start DAB-Z in "paused" mode? I could not find it. And if not possible: Could you please add that as a Setting for all those (picky annoying :)) users on FYT compatibles?

I prefer not to disable the method in the main server as it is nice if it starts my music player after resume (in paused mode). Paused mode in DAB-Z works when another media player gets focus.
[Android Head-Units] realzoulou:
Yes I will do so. The next release is already uploaded to Google for approval. I'll add this to the next one.
[Android Head-Units] realzoulou:
DAB-Z release 1.8.97 (beta)

Change log:

Bugfixes

* Random No audio fixes (again...)

* Sometimes App does not work after reconnect of the USB DAB adapter

* Removed black border around selected/focussed station in station list (@Chrisu02)

* Some RadioDNS logos not downloaded

New

* Faster start of the App

* Faster station change between stations on different frequencies, improved by ~0.5 sec

* Display of HW/SW version of the USB DAB adapter in Settings->Info

Current plan (w/o any dates) of next major releases for DAB-Z:

v1.9.x: Service Following

=> Start of deprecation phase for legacy libdab

=> User will be notified that libdab will be removed soon and that he/she should switch to OMRI mode

v2.0.x: additional UI theme

=> libdab removed

v2.1.x: DAB Announcements

v2.2.x: DAB EPG
[Android Head-Units] Chrisu02:
Thank you , thats looking way better now :)

Sincerely Kri
[Android Head-Units] surfer63:
And I'm back on standard Joying firmware with the CarWebGuru launcher. The T'eyes firmware is tuned to their own software, which blocks "non-T'eyes" functionality I need (GoogleAssistant).

And CarWebGuru again blocks DAB-Z from autostarting.
[Android Head-Units] realzoulou:
Ok. I implemented your request already and hence I will leave it in.

Will anyway have to release another update soon, because I accidentally broke the big "Play" button in 1.8.97, which comes when DAB-Z was paused by another Media App.
[Android Head-Units] VBA_Dev:
Noticed this bug today 😀
[Android Head-Units] realzoulou:
@ users with a CSN2 MCU, preferable PX5 based units with Android 10: Are there any known issues with DAB-Z not starting automatically when the unit boots up?
[Android Head-Units] realzoulou:
DAB-Z release 1.8.98 (beta)

Change log:

compared to 1.8.97, which will not be released to public channel

Bugfixes

* Introduced in 1.8.97: Play button does not result in audio being un-paused

New

* Option for starting App always with paused audio in Settings->General
[Android Head-Units] realzoulou:
tagging @rigattoni
[Android Head-Units] rigattoni:
Thanks for tagging...

No dependent to your settings in DAB-Z starts the app automatically or not.

...and happy new year folks..
[Android Head-Units] tonimontoia:
with today's latest update we have made everything worse, as you update the station logos everything closes
[Android Head-Units] EOS78:
Hi,

I´m using Version 1.8.96 with my new Joying Headunit (EU-JY-VQ130N4G), Android 10 and the new UIS7862. i´ve got two DAB-Sticks tested, Erisin ES364 and an Eighwood DAB-Stick, which looks very similar to the original Joying DAB-Stick.

If OMRI-Mode is active, the channel search stuck at 0%, an nothing more happens.

If OMRI is not active, the channel search and the app works as usual.

With my other Headunit, an Erisin with PX5(Android 9), I had no Problems with the OMRI-Mode. Tested with both DAB-Sticks.

Do I have any disadvantages without using OMRI?

Is this a known Problem with the new Joying Device or Android 10?
[Android Head-Units] IG_Vasilich:
Hello @realzoulou

after update to 1.8.97 i lost all channels from "hr radio" (hr1, hr2, hr3, hr4, hr aktuell) - it shows full signal strength and after 5 seconds popup "no audio. will retry" appears. Works as expected in LibDab mode though. Need raw rec?
[Android Head-Units] realzoulou:
Can you please be more precise? With "everything closes" do you mean that DAB-Z crashes? Is it reproducible? Could you send me a logcat (Settings->Info) after DAB-Z crashed ?
[Android Head-Units] realzoulou:
I am aware of this behavior because 2 users contacted me via email a week ago.

It seems to be specific to some devices, but always with Android 10.

So far I know about these devices being affected:

* Isudar V72 (Mediatek based): https://www.aliexpress.com/i/33015635876.html

* Erisin 5991DG (PX30 based):https://www.erisin.com/products/eri...-golf-5assat-tiguanolo-eos-skoda-dab-navi-ops

* Joying VQ130N4GN (UIS7862 based): https://www.joyingauto.eu/8-inch-4g-vw-car-radio-upgrade-android-8-1-gps-navigation.html

I am working hard to find the root cause. Seems to be at the very lowest USB level communication
[Android Head-Units] realzoulou:
That's strange because I did not touch anything between 1.8.96 and .97, that could explain what you see.

Nevertheless, yes please send me raw recordings. You know my email address already ;)
[Android Head-Units] Mulano:
A chance u can make a skin like that? :
[Android Head-Units] realzoulou:
@ibaxx Which head unit model do you have? I guess it is a quite new Android 10 based unit, right?
[Android Head-Units] ibaxx:
Right!
[Android Head-Units] okij:
Oh, your head unit model is "Right!". That's interesting, I didn't know this make or model yet. 🙃

Jokes aside: Could you please not only anwer @realzoulou's second question but also his first one? This would be more helpful for the dev...
[Android Head-Units] realzoulou:
@okij I am in contact with ibaxx directly. Seems that his unit is also UIS7862 based.
[Android Head-Units] realzoulou:
Thanks @IG_Vasilich for pointing out and sending the raw recs (y)

It was quite a huge regression that I introduced into 1.8.97. Strange that I did not catch this with my own tests. I'll add one of your raw recs to my automated regression tests.
[Android Head-Units] realzoulou:
Root cause is identified and a fix was successfully tested by the two (Isudar and Erisin) users.

Will soon release another beta version.
[Android Head-Units] IG_Vasilich:
just out of interest - what is that different on "hr Radio" ensemble, that only it is/was affected?
[Android Head-Units] realzoulou:
Basically it is the high bitrate of 136 and 144 kbps that made my code stumble upon. Such high quality audio is very seldom.
[Android Head-Units] okij:
Thanks for explanation.

So probably the "hr" in "hr Radio" stands for "high res". ;)
[Android Head-Units] darkchild971:
In the last update a cannot download the logo. the download bar automatically close. Fresh install
[Android Head-Units] realzoulou:
Please send me a logcat (DAB-Z Settings -> Info -> logcat button) after the error occurs
[Android Head-Units] realzoulou:
DAB-Z release 1.8.99 (beta)

Change log:

compared to 1.8.98, which will not be released to public channel

Bugfixes

* Introduced in 1.8.97: no audio with ensembles containing a service with audio bitrate >= 136 kbps

* Introduced in 1.8.97: sometimes slideshow images are not shown

* Some Android 10 devices: Station scan stuck at 0%

* No audio with some stations using old DAB standard, like in UK
[Android Head-Units] Andy200877:
I've installed this Radio EZoneTronics Android 10.1 Car Radio Stereo 9 Inch for Mazda 6 Atenza 2002-2008 today with DAB-Stick.

I've installed the DAB-Z App from Google Play Store.

Realy great App !! It works fantastic. But when i change the channel by the buttons on steering wheel, dab-z always goes 2 channels up or down. In the FM-Radio App there is no Problem.

Is it a bug in DAB-Z ? Or what can i do to solve the problem ?
[Android Head-Units] EuSoLusitano:
Hi together,

I have the problem, that all of the DAB+ app, doesn’t work.

I have an Seicane H505K (Android 9.1) with an Seicane DAB+ Module SC19-1.

The app’s which I have tried, are the DAB+ from the Seicane side and the DAB-Z from the side apkpure.com v.1.8.96

But the app’s crashed every time I will start the app. The DAB-Z app, which has the better look and find much more channels, also crashed.

Do you have an idea for an solution?

Thx and best regards
[Android Head-Units] realzoulou:
Please send me a logcat (DAB-Z -> Settings -> Info -> logcat button)
[Android Head-Units] realzoulou:
I think I found your crashes of DAB-Z in the crash statistics, which I capture using Google Firebase Crashlytics.

The crash comes from Android itself:

Fatal Exception: java.lang.SecurityException

Permission Denial: broadcast from android asks to run as user 0 but is calling from user 10; this requires android.permission.INTERACT_ACROSS_USERS_FULL or android.permission.INTERACT_ACROSS_USERS

Your unit is rooted. So either you messed it up yourself, or whatever ROM you are using is already messed up.

I cannot help here.
[Android Head-Units] royalhawk2002:
Slideshow fixed! Thank you!
[Android Head-Units] sim1964:
Hi ,

Just downloaded the latest beta here in the UK but am having issues with stuttering on more than one mux all was good with the previous version have attached debug log and two raw recordings.

Sim
[Android Head-Units] royalhawk2002:
It seems that some residual issues on slideshow are still present. Testing deeper the app this morning, I see that to make the slideshow work in OMRI mode, I need to set the app in legacy mode every time the app is started, wait the image display and then go back to OMRI. In this way also in OMRI mode the images are updated.
[Android Head-Units] IG_Vasilich:
@realzoulou

in .99 i hear audio from all hr stations, but it stutters. It was not the case in .96 and earlier. All other stations (from other ensembles) have no stuttering. Need log?
[Android Head-Units] realzoulou:
@sim1964 , @royalhawk2002, @IG_Vasilich I'll need raw recordings of all the 3 issues.

Sim, what you attached above are not raw recordings, but only audio recordings in aac format.

raw recordings are done using this procedure:

1. Enable Developer Menu: tap 7x on Settings->Info->Version , then go back, a new menu item appeared "Developer options" at the very bottom

2. Enable OMRI raw recording (you don't need to activate verbose logging)

2. Enable OMRI Mode

3. Close DAB-Z (raw recording enable/disable requires a restart of DAB-Z)

4. Reopen DAB-Z

... reproduce the issue ...

6. Go to DAB-Z Settings and disable OMRI raw recording. Restart DAB-Z again.

Afterwards, files with ending .raw exist in /DAB/rec/ folder

Download them all from the head unit, zip them and send to me.
[Android Head-Units] realzoulou:
<double post deleted>
[Android Head-Units] IG_Vasilich:
@realzoulou

add these instructions to 1st post, please :)
[Android Head-Units] realzoulou:
Yes, I considered already to do so.

Btw. I can reproduce the stuttering with BR-KLASSIK (144 kbps). I don't need a raw recoding from you anymore
[Android Head-Units] royalhawk2002:
Thanks. I will provide to you raw recording this evening
[Android Head-Units] sim1964:
Appologies for that, could you take a look at this one.

Sim
[Android Head-Units] realzoulou:
Thanks @sim1964 : Question: With version 1.8.96 (current public version), was the behavior any better?

My test using your recording of BBC Radio 4 results in: No, it was stuttering in 1.8.96 also. True?
[Android Head-Units] sim1964:
I can't say for certain but I think it was 1.8.97

I can't say for certain but I think it was 1.8.97 that was stutter free, I think 1 may have skipped past 1.8.96.
[Android Head-Units] royalhawk2002:
Just to have confirmation that you reached the recording on https://drive.google.com/drive/folders/15Vq25c95anskEqfzSgZq0A1h8ThfQVdv

Thanks
[Android Head-Units] wainsie:
Hi in 1.8.99 the stuttering is really bad used to be able to disable omri then re enable it to cure the stuttering on 1.8.92 but no difference on latest version