yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] okij:
Thanks for making a beta release with the numerous new features and fixes! :good: I will register as a beta user and try it.

However, could you post the APKs also here, in the announcing posts for new versions (not only for the current beta release, but also for regular releases)? I personally prefer to put APKs on a USB stick to install them on my head unit, rather than using the (rather limited) mobile data plan for my head unit. If releases are on APKPure, usually I download them from there, but not all DAB-Z releases make it there. :)

For tackling these issues (as long as the OMRI decoder doesn't get open source), what do you think about my suggestion from two days ago:
[Android Head-Units] NogenLunde:
I managed to catch the "random no audio bug" on video (see attachment), and strangely, no codec and full signal level, but still no toast. I waited 10-15 seconds before recording. The "permanent dead station bug" doesn't show bitrate, that is the only difference I can see, and there the toast is displayed.

As you can see, audio comes back after switching to a station on a different frequency.

Edit: Removed attachment.
[Android Head-Units] realzoulou:
I have decided to release on Play store only. Due to a mistake that I made when I have put the first DAB-Z version into Play store, any APK that I would release here as a file, would not be update-able via Play store and vice versa.

If the OMRI decoder really crashes, the whole app crashes.

If OMRI decoder for some (unknown to me) reason fails to decode the audio portion of the DAB protocol, there is no way for me to make it work/restart/whatever.

No worries I have a plan in mind how to attack all the issues, but I cannot comment on it publicly.
[Android Head-Units] realzoulou:
Thanks for sharing.

When there is no toast although no audio, then this means that the OMRI middleware did not give any response at all on my app request to start playing a certain station. Internal SW things...

For now, there is nothing that you guys can do to help me analyse the issue. I will let you know once a version exists that helps me better understand the true root cause.
[Android Head-Units] okij:
OK, that's fine then. Usually APKPure has your APKs from Play Store for download, I just don't think that they will also mirror your beta release(s).

Hm, then the watchdog idea still could work if you put the OMRI decoder in a separate process or APK. But that's probably too complicated.

:cool::fingers-crossed:
[Android Head-Units] DrRobin:
I have noticed a problem when listening to BBC R4 in a morning, when the news comes on at 09:00 the speech sounds really slow, like it is played at half speed. If I change to another channel and change back it is perfect. I have noticed this at other times/stations but it does it every morning on BBC R4.

It must be something in the feed or may be the program description, is there a fix?
[Android Head-Units] VBA_Dev:
Sounds like that’s when they dynamically change the bitrate as it’s just voice, but maybe this dynamic switch is confusing OMRI

---------- Post added at 09:52 PM ---------- Previous post was at 09:52 PM ----------

A quick fix btw, would be to disable OMRI mode in settings for the time being.
[Android Head-Units] ab1702:
I don’t know about anyone else but I have to use the app with OMRI disabled. IMO OMRI was made default to soon, it’s just not ready yet(well not for us in the uk anyway).

I have stations sometimes with no audio, stations where audio stutters and the app crashes or shuts down also causing FCC to restart.

As soon as OMRI is disabled everything works perfect.
[Android Head-Units] realzoulou:
I remember that someone reported this already way back with legacy libdab at a time where OMRI was not integrated at all.

And so I doubt that disabling OMRI will fix it. Actually I was hoping that OMRI would not show the same behaviour.
[Android Head-Units] rigattoni:
...and as always:

It seems to be related to the head unit and the region, DAB is used.

I now have 4 different units in use.

PX5, Intel Airmont, CSN2 and an older PX3.

I use all of them from time to time in my car or on bench, but keep all units updated and I don´t have any issues with activated OMRI here in Bavaria. I did not have any issues driving to Cologne and Wolfsburg the last few weeks in my CSN2, which was built in there.

Just one single crash seen and reported after the update on my airmont unit last week.

Seems that someone from GB needs to invite realzoulou to spend some holiday in their region to find a solution. :D
[Android Head-Units] leenq:
[MENTION=7838245]realzoulou[/MENTION] [MENTION=472138]hal9k[/MENTION], I noticed that after updating to Hal9k mod 4.01 (OTA) on some DAB stations the audio gets quite distorted. Sounds sort of like it is a "rrrrrrrr"-sound mixed in. When I downgraded to mod 4.0 the sound is much better; some occasional glitches, underruns I guess, but no annoying "rrrrrrr" sound through the music. It seems to happen on only a few stations, most stations in my area are ok. The attached log files are taken right after update/downgrade and reboot. The station in the logfile causing the troubles is TRACE FM PARIS.

Any ideas if this is an issue in DAB-Z, or a problem specifically coming from Android 9/Hal9k mod 4.01?
[Android Head-Units] DrRobin:
I am not running OMRI. I think you might be right about the bit rate. I have two head units both with DAB-z and they both do the same.

Would it help if I install a later version? I last installed a couple of weeks ago, not sure if there is an update?

Or, would it help if I watched/recorded the info screen when it changes?

Thanks for your help.
[Android Head-Units] realzoulou:
I released the beta 1.7.77 (post #2468) to the release channel
[Android Head-Units] royalhawk2002:
I need some help. Installed Android 9 ROM 4.0 from hal9k , DAB is working but I cannot load the logos even if are in correct diretory: "flash/DAB/logos/"
[Android Head-Units] realzoulou:
Logo Files must be in a subfolder of folder logos. Subfolder name is your free choice
[Android Head-Units] realzoulou:
I compared both traces. In both the signal strength varies quite a lot from "0" (=5 bars) up to 1000 (=0 bars) within seconds only.

In the 4.0.1 trace I see that my clipping detection algorithm kicks in more often, not so often in the 4.0 trace.

When you have the "rrrrr" sound again, please deactivate the "Suppress audio distortion" in Settings->Audio. Then you hear whatever comes out of libdab.so without any filtering from DAB-Z. This must be even more horrible.

In the 4.0 trace I see that libdab.so looses the sync with the DAB stream from the USB stick more often then in 4.0.1. This also indicates poor reception, too.

Overall, I doubt that Hal9K mod version 4.01 vs 4.0 makes any difference.
[Android Head-Units] royalhawk2002:
Thanks it worked!

Inviato dal mio SM-N960F utilizzando Tapatalk
[Android Head-Units] Chrisu02:
Thanks, [MENTION=7838245]realzoulou[/MENTION], with the blue selection bar it is now very good visible, and the selection does work like charm :D

i made a video for demonstation

[YOUTUBE]https://youtu.be/Cp9f3hZnDH8?t=21[/YOUTUBE]

Sincerely Kri
[Android Head-Units] realzoulou:
Thanks for the video [emoji3]

A bit OT now:

Is the iDrive controller specifically for the unit, or would the controller work also with a non BMW unit?
[Android Head-Units] Chrisu02:
This idrive controller is the original one from my BMW car, i have a navigation system on my desk so i can run it there.

Also those Pseudo idrive controllers which are sold with some BMW Android systems use CAN messages, and they dont have the panning function (and bad quality).

Some people reverse engineered the OEM Controller and made a converter with Arduino , but there is no finished product available and no source code.

You may ask this guy if he will make a finished product some day.

i think such a product would sell very well for other Android Navigation Systems :D

sincerely Kri
[Android Head-Units] typos1:
Interesting video and comments about the idrive controller, its pretty much the best OEM controler for ICE/NAV out there.

But there is one thing I think that BMW has got wrong about it though - its location - it needs to be on the back of a steering wheel spoke, not on the centre console, this way you could use it with both hands on the wheel.

BTW, there seems to be a lot of your personal info in the video, location etc. :(
[Android Head-Units] Chrisu02:
The location is probably a personal choice, for me having vol +/- on the left of my steering wheel (LHD Car), and idrive in the Centerconsole is optimal, when driving long distances is more pleasant.

i Think a knob with this much function (rotate/pan/push) would not be easy to control at the steeringwheel because you need at least three fingers to use it.

Don`t mind the Location, i had FakeGPS active, so the location is not where i really live ;)

Kri
[Android Head-Units] typos1:
I still think it would be possible to use 3 fingers if it was on the back of the steering wheel, it maybe easier if the knob was a bit smaller, but for me having it on the wheel is a basic safety feature. I would suggest that at 200kph on the autobahn you might agree its better to have both hands on the wheel ? :)

Of course in the UK we have it for the left hand, never really thought about this actually - which hand you use depending on which side of the car the wheel is on. But now I have I would suggest that, considering that most people are right handed, in left hand drive countries it is even less safe to have the right hand off the wheel using the iDrive, because for most people this is their strongest hand.

Ah, FakeGPS ! Well done :)
[Android Head-Units] apollo1976:
Hi realzoulou, as always thank you for your great job. I was thinking that maybe the only thing missing from your app is the ability to add an image as a background. Can you add this feature ??
[Android Head-Units] IG_Vasilich:
i had an interesting effect yesterday: after switching on, the radio station hat best reception, but no audio. timeshift button was active though, and after activating it i could hear audio. Switched back to realtime - no audio. activated timeshift again - audio is there. tried all this several time, waiting 10-15 seconds between each action - same effect. That means that in that case audio samples were there, just direct routing to audio output didn't work, but from timeshift - worked.
[Android Head-Units] realzoulou:
Would be very interesting to know if this is the same for UK users of DAB stations...
[Android Head-Units] okij:
Since there has been no feedback from the UK users yet, I'm tagging [MENTION=456516]typos1[/MENTION], [MENTION=8476598]ab1702[/MENTION], [MENTION=10471615]DrRobin[/MENTION], [MENTION=1046126]davemazo[/MENTION], [MENTION=10431651]DominicS65[/MENTION], [MENTION=2784358]haynesteve[/MENTION], [MENTION=9709140]VBA_Dev[/MENTION] and [MENTION=2336681]sim1964[/MENTION] to check this and report back. :)
[Android Head-Units] typos1:
Sorry my car is off the road at the moment so I cant help here. :(
[Android Head-Units] haynesteve:
Not had this problem myself (up to now)
[Android Head-Units] davemazo:
Sorry, I don't understand what the problem is. All I know is I can't use omri mode because either it gives me a poor signal and/or anything I do receive is intermittent or jumpy so I only use normal (libdab) mode.
[Android Head-Units] ab1702:
I’ve not seen the problem but I’m not using OMRI if that makes any difference.

One thing I have noticed is that when the app restarts after sleep or boot it goes back to the full list of stations and didn’t stay on favourites so I have to press the favourites button every time I get in the car. [MENTION=7838245]realzoulou[/MENTION]
[Android Head-Units] spl_decibel:
Hi realzoulou, thanks for your work.

I just wanted to warn you that with the latest update, my android radio crashes and don't power on!

so, I had to perform a factory reset to be able to use the radio again.

I had to download a previous version from apkmirror, so everything works correctly
[Android Head-Units] haynesteve:
Umm, sorry to say but more likely to be your head unit or android firmware, as (apart from OMRI, due to being in UK), working perfectly.
[Android Head-Units] DominicS65:
I don't see the specific issue but maybe what I do experience is similar or related.

I start the car and if the station I last used was my most frequent one BBC Radio 5 Live, DAB-Z starts with BBC Radio 5 Live Sports Extra silent, I select BBC Radio 5 Live which starts, then after about 10 seconds the default Android audio player starts up which I exit from only to find that Radio 5 is now paused. It has been doing this for about a month now.

If the last station I was listening to before I stop the car is not BBC Radio 5, then it resumes on the correct station working before the audio player thing happens.

Just because it gets mentioned, I too have to disable the OMRI thing or the entire unit goes exceptionally slowly.
[Android Head-Units] NogenLunde:
What unit do you have? DAB-Z will pause when another app is playing, so this is expected. The problem you have, is that the music player somehow is configured to auto start. I would do a factory reset of the unit, taking notes of all settings first. The DAB station confusion will probably be fixed also then, but you can do a new, complete station scan first, if you hesitate to do a reset.
[Android Head-Units] DominicS65:
This Erisin unit

I removed BBC Radio 5 Live Sports Extra from my favourites and the restart station is now correct.

I presume that the audio player automatic start is due to my having MP3 files on the micro-SD card and MP4 files on a USB drive attached to the back of the unit.

It would be nice if there was a config option to prevent the default audio player starting.
[Android Head-Units] typos1:
Thats not an Erisin unit - Erisin are just a retailer, the letters of your MCU after "MTCE" will tell you who makes your unit.
[Android Head-Units] realzoulou:
DAB-Z release 1.7.78

DAB-Z release 1.7.78 (released to public on 2020-02-23)

This is mainly addressing stability issues in OMRI mode.

Change log:

Bugfixes

* OMRI: Random crashes, often after selecting a new station

* OMRI: When rapidly changing stations, sooner or later app crashes

* OMRI: May crash after performing a station scan, which found certain stations, e.g. BBC R5LiveSportX

* Sometimes at start, the circle keeps spinning but DAB-Z does not start.

Known issues

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

* OMRI: When switching between stations on same ensemble frequency, DLS text and MOT slideshow picture are not updated anymore

* OMRI: Importing a station list shows "import failed" or does not pick up the station list.

Workaround: kill + restart DAB-Z (kill it by using the Recents menu) or reboot the device.

* OMRI: Some stations stutter and show a different bitrate than in non-OMRI mode.

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

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

* Non-OMRI: Randomly crashes while parsing data from DAB USB adapter
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: Wohow, this change log sounds really great! :victory: I will install the new beta tomorrow morning and check the improved stability.

Thanks a lot for your hard work! It looks like I'll soon have to make another donation. :)

Is this the general stuttering that the OMRI mode showed when the CPU is under load (e.g. directly after the boot process) or has this already been improved? The non-OMRI mode was less sensitive in this matter.
[Android Head-Units] realzoulou:
Yes, I think I changed nothing that could fix this. So I list it as open issue.
[Android Head-Units] okij:
Could you maybe raise the priority of the task that processes the audio stream?
[Android Head-Units] Salvo-x:
Hello realzoulou ,

what happened to the project to change the layout of the application?
[Android Head-Units] gdm13:
Hi,

in OMRI mode, when I change radio station, the radio takes several seconds to start. it seems very long. is this normal?

Android 9 / China 2Din car head units / PX5
[Android Head-Units] okij:
This morning I did some tests with the new beta release.

OMRI playback is working fine now in all circumstances, i.e. I couldn't provoke it to stop or DAB-Z to crash even with rapid channel switching, which is a great improvement. :good:

However, when switching from one station to another and then back to the first, the RDS infos are not displayed anymore, including the RadioDNS pictures. This bug is reproducable, so if I have switched through all of my favourite stations and switch to any of them for the second time, none of them displays or updates those informations anymore.

I attached a full catlog in hope that it helps debugging this issue.
[Android Head-Units] okij:
[MENTION=7838245]realzoulou[/MENTION]: Yesterday I had to do a longer trip using Sygic for navigation.

Audio was stuttering a lot when using OMRI mode. From what I remember it wasn't that bad on versions before 1.7.78. On my trip yesterday I then switched to non-OMRI mode, which worked without stuttering.

In the stuttering I also noticed slight jumps in the playback, like if the reading of the audio from the USB adapter and the playback of the audio get out of sync.

So it seems to me that someting must be improved in filling and/or reading of the OMRI audio buffer (if this is the way it's implemented).

If this is not the problem, then IMHO the OMRI implementation needs some optimization to work well even when CPU-demanding apps (like navigation) are running. I'm not a developer, but isn't it possible to give the OMRI thread a higher CPU priority or even assign it to its own CPU core?

Maybe this article can give you some hints: Better performance through threading
[Android Head-Units] realzoulou:
Currently on hold. I concentrate on OMRI stability and functionality issues currently.

Agree. I had the same yesterday, but it seems to be not 100% reproducible (at least on my side). Logcat does not (yet) help here, because I would need to see logs that are not active in release builds.

FYI: I pushed 1.7.78 into release channel.
[Android Head-Units] NogenLunde:
100 % reproducible when switching stations on the same frequency. Switch to a station on a different frequency (/broadcaster), and the RDS info bug is reset.

Unfortunately, no change here.

New bug in this release: Stuttering once when changing stations, every time on all stations.

---------- Post added at 01:22 PM ---------- Previous post was at 01:15 PM ----------

Changing radio stations is instant when the stations are on the same frequency, but 3-4 second when on a different frequency (this is a bit longer than in non-OMRI mode, but in that mode switching has a delay every time).
[Android Head-Units] realzoulou:
Thanks [MENTION=10451415]NogenLunde[/MENTION]. I updated release notes to not show it as "maybe fixed", but as open.

Regarding stuttering... what RAM amount + CPU is in your unit?
[Android Head-Units] NogenLunde:
CPU Snapdragon 625, 4 GB RAM. Would a video of this be helpful?
[Android Head-Units] realzoulou:
No, thanks, is not needed. This seems to be a phone, not a Head Unit, right? Anyway, today I found a major CPU hog in OMRI ... stay tuned [emoji6]
[Android Head-Units] Flemischguy:
No, it's really a head unit with a Snapdragon 625 cpu.
[Android Head-Units] sim1964:
Only just got the radio back in my car, installed latest version from play store but am still getting crashes with OMRI mode on BBC stations so back to Libdab.so
[Android Head-Units] realzoulou:
Could you send me a logcat of such a crash?

Steps: 1) switch to OMRI 2) close DAB-Z, 3) open DAB-Z, 4) got to BBC station, 5) crash of DAB-Z, 6) Open DAB-Z and disable OMRI, 7) Settings->Info->Logcat (system-wide please if your unit is rooted)
[Android Head-Units] sim1964:
Sadly cannot do a systemwide logcat as my unit is not rooted
[Android Head-Units] realzoulou:
No problem, a crash is visible also in the app-only logcat
[Android Head-Units] stesofeu:
Unfortunately got the same issue while trying 1Live or RadioNRJ. Latest version installed today but both modes with and without using OMRI crashed. I even had no time to switch OMRI off. I need several times to switch OMRI off.

Headunit tried several times to connect USB to file manager. I thought its the dashcam but it seems to be dab-z app which causes window with choosing the USB standard opening app for USB.
[Android Head-Units] haynesteve:
Ok, I have a pumpkin unit, with Agama launcher, running Hal9k version 4, in the UK. Most stations are ok in Omri, but BBC ( especially Radio 2), doesn't just crash Dab-z, but effectively locks the whole head unit until it does finally crash.

Tried to capture a system wide log, as described in Zoulou's previous post. Hope this helps.
[Android Head-Units] realzoulou:
Thanks [MENTION=2784358]haynesteve[/MENTION]. Unfortunately, there is no logcat in it. The file in the zip starts with "dab-z-" followed by the date and time and ends with ".log"

When this file is missing then this happens typically because the SuperUser app (Malaysk oder SuperSu) does not grant DAB-Z root access. Sometimes it is needed to go into the Malaysk or SuperSu app settings and activate DAB-Z as being allowed. Sometimes DAB-Z does not even appear in the list of apps that asked for root access. I did not find a reliable and reproducable way to resolve this. Sometimes it seems to help to deinstall DAB-Z, sometimes it helps to clear the whole list of apps in Malaysk or SuperSu.

What a pity that your effort is wasted. I would really appreciate if you could try again... I am unable to reproduce this at all, while I am seeing these complaints on Google Play regarding a "total crash of the unit".
[Android Head-Units] haynesteve:
Sorry about that. Will give another try tomorrow.
[Android Head-Units] Flemischguy:
Today i drove with my car to my work and when DAB Z started there was no reception whatsoever, i tried several radio channels. I disconnected the DAB+ dongle, connected it back, but no reception. This evening when i was back home from work, i did the same thing by disconnecting and connecting back the DAB+ dongle and restarted the radio again, it was the same as before, the only thing i saw was a short message 'WTF SORRY' after that message i removed the DAB Z app from the radio and reinstalled the DAB Z from the play store, everything works again like it should be. Sorry that i din't make a log file why i have no reception and OMRI was not enabled.
[Android Head-Units] haynesteve:
Hopefully a decent log this time (app only, because, as you said, magisk won't give rooting rights)
[Android Head-Units] realzoulou:
Thanks again, but there is no crash visible in the log.
[Android Head-Units] haynesteve:
One last try today. Dab-z definitely restarted itself on this.
[Android Head-Units] sim1964:
Hi (real)zoulou,

Finally had a chance to do a test here is my app logcat
[Android Head-Units] realzoulou:
Thanks again. The log shows a gap of ~30 sec where something dramatically must have happened in the Android system followed by suddenly a new DAB-Z coming up. But because it is an "app only" log and not system-wide, I have no clue what really happened.

When you switched from libdab to OMRI mode and BBC Radio 2 is about to be started, DAB-Z crashed. I have already a fix for this, which I will release soon as a new beta. But I think this crash is not the one that causes the whole system to lock up.

After DAB-Z is automatically restarted after the crash, and after switching from BBC Radio 2 to Pirate FM and back to BBC Radio 2 again, I see the very same as in haynesteve's log:

A gap of ~10 sec and suddenly a new DAB-Z comes up. Same as with haynesteve: An "app-only" logcat does not allow me to see into the Android system.

@ All UK users with a rooted unit that are able to reproduce the "whole system lock up with BBC stations in OMRI mode". Please share a system-wide logcat with me. I doubt that I will be able to fix the root cause by chance. I need to understand what happens to Android internally.