yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] surfer63:
The logcat didn't mention anything but I'm not rooted, so I currently can't deliver a system wide logcat.

Like mentioned: "DAB-Z always starts when coming out of deep-sleep (Joying SC9853i on Android 8.1 using Nova Launcher)".

So indeed from resume, not from reboot, and using Nova Launcher. That might be a point as some weeks ago there was an update of the CarWebGuru, which I didn't like at all and that's when I switched back to Nova Launcher. I simply can't remember if that was the time when it started. I "think" it was later, but I will temporaraily switch back to CarWebGuru.

Edit: It is something that Nova Launcher does. It doesn't happen with CarWebGuru. I now tried 3 times from deep sleep (resume) and DAB-Z didn't start.
[Android Head-Units] IG_Vasilich:
have you found an issue root in OMRI or in DAB-Zor somewhere else (decoder management, etc.) ? just for me to know :)

P.S. i can confirm that the bug with wrong bitrate displaying is fixed in .73+ . I just had to rescan channels.
[Android Head-Units] realzoulou:
One line of code was missing in OMRI
[Android Head-Units] kajboj:
Hi, not sure if the following issue can be related to the app itself (or perhaps can be fixed with the app). If not, I'll delete this post. Cheers

Setup

:

Rooftop FM/AM 31'' whip antenna (removable, passive)

FM to DAB+ splitter (active)

DAB+ USB dongle (VID:16C0 PID: 05DC)

Android 8.1 Go (MCU: 3.0 | Build: android-trunk-m0.AC8227L-V1.0)

DAB-Z app from Google Play

Observations

:

In my area, DAB+ stations are broadcasted over two ensembles, 6A and 6C

Considering the above mentioned setup, FM and DAB+ stations on 6C work flawlessly (reception is the highest) whilst no signal is received on 6A.

Now the weird thing is, if i remove the rooftop antenna, the FM stays good whilst the DAB+ 6C reception is lost but the 6A reception increases to the highest level.

Solution:

Kindly follow this post.
[Android Head-Units] realzoulou:
This sounds like an EMC issue with one of the involved hardware components. Strange is that the FM reception does not suffer from the removal of the antenna. This may be an indication, but I have no advice how to further analyze.

For sure nothing that my software can address. But no need to delete your post!
[Android Head-Units] NogenLunde:
Depending on country, your car might use the FM antenna in the rear window. My BMW has the DAB III band also located there, while the signal for the DAB L-band comes from the rooftop antenna. Might be a splitting issue going on there?
[Android Head-Units] VBA_Dev:
Does anyone know of a url that can be checked for when google push out new betas of apps?
[Android Head-Units] realzoulou:
I am not aware that this exists. Only way is to check for updates in Google Play.
[Android Head-Units] VBA_Dev:
Yeah I figured, I’m an iPhone user so no easy way for me to check other than checking in the car
[Android Head-Units] haynesteve:
The latest beta version now on Google play. Only had 5 minutes on it but radio 2 did NOT crash. ?
[Android Head-Units] surfer63:
On your pc/laptop: https://play.google.com/store/apps/details?id=com.zoulou.dab

At the bottom you see the version.
[Android Head-Units] VBA_Dev:
Thanks, but this just shows the current release version number - not the beta version number
[Android Head-Units] VBA_Dev:
Updated to the latest beta and BBC Radio 2 is fine :)

Managed to catch another instance however of a station not playing any sound after switching.

Not sure which raw recording it will be but it will probably be the latest one.
[Android Head-Units] kajboj:
Issue (presumably) SOLVED! :D

I'm in Malta and both blocks, 6A and 6C, are transmitted on Band III (source: wohnort) and coverage wasn't the problem since I'm merely 2.5km away from the transmitting antenna. Since block 6A was being received without the antenna then I though that the 6A signal was "too strong" than the 6C. I went online to search if an RF signal can be "too strong" but I didn't find a clear cut answer although there are instances where an attenuator might help. At first I though of powering off the active splitter (because I think it also acts as a booster) but then I though of shortening the antenna to a typical length of an active antenna (approx. 1 foot). I've improvised with a foot long wire and Voila! Best reception on both 6A and 6C :laugh:

So basically the solution is to use a short whip antenna (passive) with an active splitter.

[MENTION=7838245]realzoulou[/MENTION] : There is a particular station (All Rock HD, some info here: wohnort) which shutters badly (OMRI on or off). The rest of the stations are fine. I don't really follow All Rock HD so it's not really an issue for me but for the sake of the app I can send any info to troubleshoot if interested
[Android Head-Units] realzoulou:
I would be interested in a raw recording of All Rock HD. Your wohnort link shows that it uses a AAC LC codec. Never saw this codec so far being used anywhere and this might be the root cause why both legacy libdab and OMRI stutter. With OMRI I might be able to solve it, no guarantee though...
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: Yesterday and today I had two crashes of DAB-Z (latest version) after resuming from standby.

I now took a system-wide logcat which I attach to this post for you to look into this issue.
[Android Head-Units] sim1964:
Played five minutes of BBC Radio 2 without a crash
[Android Head-Units] kajboj:
How do i perform a raw recording? :confused:

I have the latest Google Play version.
[Android Head-Units] realzoulou:
Post 2605 contains how to activate developer mode and activate raw recording and where the raw recording is stored

https://xdaforums.com/showthread.php?p=82150083
[Android Head-Units] kajboj:
When i tapped on the version number a small popup came up saying Credits 7h22m... And something else which I don't remember then it vanishes after a few seconds. What I'm doing wrong? :S
[Android Head-Units] realzoulou:
Then you are on the public release channel and have still 1.7.82, which does not yet have this feature. Either join the beta channel, or we both wait until 1.7.85 is available on public channel
[Android Head-Units] kajboj:
Yep, I´m on the public channel. Can I access the beta channel through Google Play or I need to download the apk separately?

Cheers
[Android Head-Units] IG_Vasilich:
join beta for this app on Google Play.
[Android Head-Units] NogenLunde:
I've experienced this too a couple of times with the 185 version. [MENTION=7838245]realzoulou[/MENTION], do you need more raw recording files to sort this out? The other bug you fixed regarding no audio on NRK1 + etc. is OK now.
[Android Head-Units] realzoulou:
[MENTION=10451415]NogenLunde[/MENTION]: I have two raw recordings from you for "NRK FOLKEMUSIKK" and "NRK JAZZ" that still do not play with 1.7.85. This is what I called "tricky ones" before. I don't know why they don't play. So, yes: If you find more "random no audio", then please send them to me.
[MENTION=9709140]VBA_Dev[/MENTION] I have not yet looked at your files.
[MENTION=4916555]okij[/MENTION] I have not yet looked at your crashes.
[Android Head-Units] kajboj:
Installed the beta, enabled raw recording, restarted the app but didn't find the rec folder in the DAB folder :/

I forced stopped and cleared the app's cache but still no rec folder. App has storage permission too. :/
[Android Head-Units] VBA_Dev:
Try enabling recording too and test that by pressing the button near the signal bars. After that works try it again ?
[Android Head-Units] kajboj:
Yes, the rec folder came up after enabling recording but all i got was an audio aac recording of the channel. :/

Stuttering problem solved! :D

Culprit was "Suppress audio distortions". After disabling it no stuttering. I don't know the underlying issue, either the CPU doesn't have enough resources (because that particular station has the highest bitrate) or perhaps a bug. Unfortunately i wasn't able to make a raw recording otherwise i would have shared it nonetheless.

Thanks to all who tried to help :good:
[Android Head-Units] VBA_Dev:
Sorry yes, I meant to try the record option to see if it worked and then maybe woke up the raw recording option (it did for me). Try the raw recording option again and look in the Rec folder - but remember to enable, close dab-z then re-open. Same to disable.
[Android Head-Units] realzoulou:
So, two action items for me: Ensure the rec path exists when needed, and finally disable by default the audio distortion detection.

Btw. 1.7.85 is now public
[Android Head-Units] realzoulou:
Thanks [MENTION=4916555]okij[/MENTION]. I know about this crash from Firebase Crashlytics. It is not in my source code, but in Android's libstagefright. I don't know how to avoid the crash.
[Android Head-Units] okij:
Thanks for looking into this and for explanation.

Since I don't experience such crashes with other media apps, I guess that it still might be able to fix this issue in DAB-Z itself. Maybe something in the interface between DAB-Z and libstagefright could be handled differently?

Of course it's not hight priority, but if you have some time after the last OMRI issues have been ironed out, maybe you could have a 2nd look into this.

BTW, congratulations for your great success in fixing the OMRI issues. Recording and analyzing raw streams seemed a very clever way to me when you introduced this idea and I'm glad that it works out so well! :good:

I'm already looking forward to listen to BBC2 in OMRI mode on my next trip to the UK after C*r*na has been successfully fought and if B*ris J*hns*n still allows us EU mainlanders to visit his island then. :laugh:
[Android Head-Units] realzoulou:
Please note that I added a known issue "OMRI: RadioDNS logo download is broken"

However, the issue is on the server side.

Up to 1.7.85 I was using a feature of OMRI called "hybrid_scan" that seems to use a test server as backend. This server now returns an error message since a few days.

In my next release I will change the RadioDNS logo download to sth completely different.
[Android Head-Units] typos1:
Thankfully, that lying **** doesnt speak for all us, youre welcome here no matter what that stupid clown says. Have I mentioned hes a liar ? Does it come over that I hate the vile low life of a man ? :)
[Android Head-Units] okij:
Thanks for your welcoming words. From talking with other UK citizens I know that a lot of you think the same way. There are just too many liars and morons in world politics nowadays. But I'm sure that it'll get better. :)
[Android Head-Units] haynesteve:
FFS why bring bull**** politics here? This is supposed to be for app development - can we please leave it as such.
[Android Head-Units] okij:
Yes We Can
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

I drove to Kaiserslautern today and on the way tried to listen to DAB. In OMRI mode it crashed every 5-6 station switches - poor reception outside of cities here in RP. Definitely most crashes came when switched to Planet Radio.

After switching to libdab there were not a single crash.

Would it help to make a raw record and send it to you? You have already my crash logs (system wide).
[Android Head-Units] realzoulou:
Yes, I think raw recordings could be helpful. But I did not receive any logcat from you. How did you send them to me?
[Android Head-Units] IG_Vasilich:
They are there https://xdaforums.com/showpost.php?p=82040553&postcount=2583

Or should i make new ones, with newer version (1.7.85)?
[Android Head-Units] iMattmax:
I say goodby to DAB-Z, because my new HU has an other oppertunity to receive DAB+ without using an USB-adapter.

It was always a good work from realzoulou
[Android Head-Units] typos1:
Is it an Android headunit ?
[Android Head-Units] iMattmax:
Yes, it is. The unit is Dasaita 10.2 Max 6 with Hal9k Mod in Android 9.
[Android Head-Units] typos1:
Interesting, how do they do DAB on that ?
[Android Head-Units] rigattoni:
Got a new toy from Klyde today. :D

12.3" turnable screen with PX6... First thing was to install DAB-Z. ;)
[Android Head-Units] NogenLunde:
This unit seems to have FM radio, not DAB.
[Android Head-Units] iMattmax:
The do it with there own dab-adapter [IMG="Dasaita DAB-adapter DAB003"]https://ae01.alicdn.com/kf/Hc2955aff9e104474a747bf289c2dffa7j/Externe-DAB-Radio-Antenne-Nur-F-r-Hotaudio-Dasaita-Kopf-Einheit-Android-8-0-8-1.jpg_50x50.jpg[/IMG]

I know what I hear and that is DAB+ and not FM, because I have the [IMG="Dasaita DAB-adapter DAB003"]https://ae01.alicdn.com/kf/Hc2955aff9e104474a747bf289c2dffa7j/Externe-DAB-Radio-Antenne-Nur-F-r-Hotaudio-Dasaita-Kopf-Einheit-Android-8-0-8-1.jpg_50x50.jpg[/IMG]
[Android Head-Units] realzoulou:
Can you share the App that works with this adapter?
[Android Head-Units] iMattmax:
Here is a link from another forum topic with the file https://xdaforums.com/showpost.php?p=82158249&postcount=310

[MENTION=7838245]realzoulou[/MENTION] it would be nice if you can integrate that adapter to DAB-Z, because after sometime of use DAB-Z I miss all the features... the other app from Dasaita has not the features ;-(
[Android Head-Units] realzoulou:
So what is the benefit of this Dasaita box compared to the known USB adapters? Seems to be not the software that comes with it ;) Does it have better reception? Better audio?
[Android Head-Units] iMattmax:
Compared to the USB variant, I would say that I have better and more stable reception.

It was already clear to me that the software made no difference.

After I bought a Dasaita HU, I also wanted to test the other type of DAB reception. As I said, the reception has already convinced me.

The software alone is not the best, the DAB-Z was much better.

If you could integrate this adapter into the DAB-Z or provide a variant of the DAB-Z for this adapter, that would be a huge quantum leap in contrast to the Dasaita app.
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION], I found a crash while moving DAB-Z to split screen.

Preconditions:

PX6 - RK3399

12.3" unit in landscape mode

Main screen visible

Unit not rooted yet

Workflow:

Open last apps

Choose DAB-Z and move it to one side of the screen

Drop the app there

Expected behavior:

DAB-Z keeps running in split screen

App list to get shown to choose the secondary app shown on split screen

Observed behavior:

After dropping DAB-Z on the side, DAB-Z stops playing

DAB-Z crashes

Crash log attached.

Side note:

If you first choose any other app and drop it to the split screen, DAB-Z does not crash if you choose it as second visible app.
[Android Head-Units] realzoulou:
[MENTION=2534110]rigattoni[/MENTION] Tried to reproduce with a PX5 Android 9 (HAL 4.0.2) but cannot crash DAB-Z.

From your log, it looks like an issue outside of DAB-Z. Every attempt of DAB-Z to communicate to Android services ends up in an Exception.

The last message below "DeadSystemException: The system died; earlier logs will point to the root cause" is a bit freaky ... Without root and system-wide logcat it is not possible for me to see what happened outside of DAB-Z.

04-28 12:54:09.568 791 817 W Sensors : sensorservice died [0x7b90c38720]

04-28 12:54:09.714 791 791 E MediaSession: Dead object in setPlaybackState.

04-28 12:54:09.714 791 791 E MediaSession: android.os.DeadObjectException

04-28 12:54:09.714 791 791 E MediaSession:	at android.os.BinderProxy.transactNative(Native Method)

04-28 12:54:09.714 791 791 E MediaSession:	at android.os.BinderProxy.transact(Binder.java:1127)

04-28 12:54:09.714 791 791 E MediaSession:	at android.media.session.ISession$Stub$Proxy.setMetadata(ISession.java:401)

04-28 12:54:09.714 791 791 E MediaSession:	at android.media.session.MediaSession.setMetadata(MediaSession.java:439)

04-28 12:54:09.714 791 791 E MediaSession:	at android.support.v4.media.session.MediaSessionCompat$e.a(MediaSessionCompat.java:40)

04-28 12:54:09.714 791 791 E MediaSession:	at com.zoulou.dab.activity.Player.a(Player.java:226)

...

04-28 12:54:09.737 791 791 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
[Android Head-Units] realzoulou:
Sorry, I don't plan to do so.
[Android Head-Units] rigattoni:
Hi [MENTION=7838245]realzoulou[/MENTION],

thanks for having a look at it. I also stumbled over this freaky log.

I rooted the device yesterday evening and I am not able to reproduce this issue anymore.... strange...

May be related due to adding a vent to the top cover to reduce the CPU temperature... It was up to 78°C and throttled down to 55% which is now in tests only 36°C and 95% performance.

If I am able to reproduce it, I now would be able to provide a full trace.
[Android Head-Units] realzoulou:
Your crash logs I analysed in post #2602 . This was about crash of DAB-Z when coming out of suspend mode where the reason is the same reason that also okij reported recently: a crash inside Android source code, in your case libmedia_jni instead of libstagefright.

Now you say you have crashes while switching stations, especially to Planet Radio. Please record a new system-wide log when it happens next time. a raw recording only helps me if it is an "always" issue and definitely relates to the DAB information received. This seems to be not the case with your issue.
[Android Head-Units] iMattmax:
Is it difficult to do it?
[Android Head-Units] typos1:
Interesting, Klyde also used to sell a similar box to what Dasaita are now selling, it plugged in to the back of the unit like the Dasaita one and used a similar plug (although actually it was still USB - it connected to USB pins on the board just via a non USB plug on the back of the unit). I cant remember anyone saying the reception was better than the type in this thread, but it was in the early days of the very similar and related MTCB/C units and not many people used it. It might actually be the same chip, you could install the app from that one (attached) and see if its the same type, there is info (in this thread : https://xdaforums.com/android-auto/mtcb-android-head-unit-general/dab-t3254201 ) about the chip it used which may help [MENTION=7838245]realzoulou[/MENTION].

(EDIT: I see he doesnt want to, oh well)
[Android Head-Units] realzoulou:
DAB-Z release 1.8.87

DAB-Z release 1.8.87

Change log:

New

* OMRI: Settings->Station logos: new entry "Update RadioDNS logos..."

Change

* OMRI: Use pure RadioDNS logo download mechanism, not OMRI's "hybrid scan"

* Suppress audio distortion is now OFF by default

Bugfixes

* OMRI: RadioDNS logo download results in no (or not enough) logos, although country should be covered.

* OMRI: raw recording fails when DAB/rec folder does not exist

Known issues

* Crash when Settings->Station list->Logo import is touched

* OMRI: Sometimes no audio, especially with stations using old DAB standard (MPEG), but also randomly with DAB+ (AAC) stations

* OMRI: If Timeshifting is enabled in settings, DAB-Z sometimes crashes.

* OMRI: After station scan, stations may be missing, which appear properly in non-OMRI mode.

* Non-OMRI: Randomly crashes while parsing data from DAB USB adapter
[Android Head-Units] NogenLunde:
This works now. :) But all imported RadioDNS logos lacks transparency.
[Android Head-Units] realzoulou:
Yes, agree. The RadioDNS specification does not specifically allow or disallow transparent logos. But bear in mind that a logo with transparency may look ok with a black background like I have, but is not visible with a blue, green, yellow, whatever colored background. The only chance for them is to avoid transparency.
[Android Head-Units] NogenLunde:
I see. The downloaded logos, are they saved somewhere reachable where we can copy them out and change them to transparent?
[Android Head-Units] realzoulou:
The files are in /data/data/com.zoulou.dab/cache/logofiles_cache

This folder was never meant to be accessed by users, so the files in there have numbers as names! You will find it difficult to identify the files that belong to a certain station.
[Android Head-Units] VBA_Dev:
9 times out of ten at the moment, I’m seeing when I turn my car on after sitting for a few days, the station that dab-z was left on will not play until I select a different station first.
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

here are some crash logs. Most of those are happened when switching to Planet Radio station, but not all of them. I also attached 2 raw recordings for Planet Radio when DAB crashed.

Most of those crash logs contain already known exception in createByteBufferFromABuffer, but there are some other exceptions - maybe you'll get a clue where it can come from...
[Android Head-Units] kajboj:
Hi [MENTION=7838245]realzoulou[/MENTION]

Just wanted to make a suggestion. Is it possible to add a Station Preview function for the favourite list?

Basically when this function is activated, the app tunes into each station for a set amount of seconds (say 10s) until either the list is exhausted or the user touches anywhere on the app. In the latter case, the app remains tuned on the currently previewed station.

The purpose of such a function is basically to get an idea of what programs are on air at the moment and tune in the preferred one.

The order of the scan can be either as the favourites list or according to the ensemble (to reduce ensemble switching which consumes more time)

Thanks for your great work! Still need to download the latest beta and check the raw saving function.
[Android Head-Units] ranseyer:
Mute or Stop function

Hi,

i searched the "hole" internet and this thread.

Does somebody have an hint for me ?

Base:

-DAB-Z is running

-Sound from Google Maps (etc.) is needed

-No DAB Soud is wanted

Is it possible to mute only the DAB-Z Application with an (existing?) Button , or is it possoble to pause or stop the DAB playback ?
[Android Head-Units] rigattoni:
You should have a look into the settings --> Audio.
[Android Head-Units] realzoulou:
You have to configure Google Maps as the "Navigation" app in your Android settings. Then DAB-Z will duck its audio while the Navigation software gives guidance audio output.

This is typically done in an Android "Car" or "Vehicle" settings menu. Every device has its own look and feel for such settings. You will have to search your Android settings...
[Android Head-Units] realzoulou:
Honestly, I see not much value in such a "Scan" feature (as I think it was called typically with the old FM/AM Radios).

I guess most users nowadays have steering wheel buttons to quickly change between the stations.
[Android Head-Units] realzoulou:
Could you please for some hours/days disable Timeshifting and see if this makes the crashes go away (or at least drastically reduce them)?

I have identified some weaks spots in that code area.
[Android Head-Units] ranseyer:
Thanks, this is absolutly clear and works perfect.

But what if dont want to listen music (DAB-Z is running), i could mute the hole head unit...

But i want to hear the navigation anyway., and and dont want to exit DAB-Z. This is the reason if is possible to mute or pause only DAB-Z...
[Android Head-Units] realzoulou:
If you don't want DAB audio at all and hear only silence while Google Maps does not say anything, then you could lower the DAB audio level to 0 in DAB-Z settings under Audio menu.

Why not exit DAB-Z if you don't want to listen to DAB? I don't get this...
[Android Head-Units] ranseyer:
Maybe im stupid... But i think its more comfotable to have always Maps open on the left side. And DAB-Z on the right side.

If i want to listen music i can press the (not existing) Pause Button from DAB-Z again, i i have imediatly music from the last uses station.

For example while parking or so, sometime music can be very annoying.