yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] burny02:
t3-p3

Hi; I think I have an allwinner T3 (It's hard to find out - Will do more research) and am getting audio stuttering.

As you said in FAQ #1, installing from APKPure etc I still get stuttering. Does this mean it's not fixable? (I will send back - Having only just installed)

item I bought:

https://www.ebay.co.uk/itm/7-Android-7-1-Car-DVD-Radio-Sat-Nav-GPS-Player-Audio-HD-Ford-Focus-Mondeo-S-Max/322626985478?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649
[Android Head-Units] realzoulou:
Can you capture a system-wide logcat? A DAB-Z-only logcat will maybe not help to find the root cause.

EDIT: I was able to reproduce the crash on my Sofia unit. No need for logcat anymore.
[Android Head-Units] realzoulou:
The ebay link you provided above states it is a (Rockchip) RK3188 CPU, not an Allwinner T3.

The Apkpure and Google Play versions of my app don't differ. Apkpure is only an alternative source and it keeps also previous versions, while Google Play only provides you with the latest.

RK3188 based devices are not known to stutter with my app. Have you tried all options from FAQ#4 ? (i.e. USB hub, OMRI)
[Android Head-Units] rigattoni:
The unit is a Cortex PX3, not a Allwinner unit.
[Android Head-Units] burny02:
Thanks for the help guys, Google had it down as a allwinner but apparently like you said it is not. The support for these things is a joke

On a side note, I was able to get the latest version 1.5.55 with a Firefox plugin from the play store, and can confirm with OMRI it works perfectly.

Still not available on apkpure etc, and can't get directly from play store (not compatible)
[Android Head-Units] rigattoni:
Sorry to say: You got what you paid for... Sorry, but in your case this get´s true again.

But good to hear that it´s working now.
[Android Head-Units] burny02:
Yeah that's true, but it still should work as claimed. And if not, it's going back.
[Android Head-Units] typos1:
Its a Rockchip RK3188/PX3, Cortex is the ARM architecture type.

We cant judge his unit unless we know what type it is.

"You get what you pay for" is nonsense - there are plenty of expensive devices that are crap and plenty of cheap devices that are good, as well as cheap devices that are crap and expensive devices that are good.

When it comes to full Android head units, theyre pretty much all cheap anyway.

There are plenty of apps in the Playstore that will show the specs of the device they are installed on.

The ad claimed DAB works with OMRI ?
[Android Head-Units] burny02:
No the AD just says it works with DAB, which is not true if it stutters. Had to find a dab app myself (all of them stuttered apart from this OMRI version. 1.5.54 OMRI mode was just silent)

Plenty of pissing around getting everything to work as it should
[Android Head-Units] kare_meesner:
after the latest Update I've testet OMRI on my MTCE MX2 PX5 unit (Witson) with HAL9K ROM:

everything's working fine, thanks.

one small thing I noticed: on the screensaver I see the number of the station now "station 69 of 120", before it showed only with the number of the favourite list "station 5 of 6" , but no problem as long I can switch with on the steering-wheel inside the favourite-list
[Android Head-Units] realzoulou:
A new version 1.2 of dabmpg123decoderplugin is rolled out via Google Play soon.

This fixes the crash on Sofia units. Thanks [MENTION=9709140]VBA_Dev[/MENTION] for your support!
[Android Head-Units] Ben.suffolk:
Installed the update this morning, and removed the git hub version of the plugin. However it did not prompt me to install one from the play store.

How does it determine if it should show the dialogue prompt for the install? Do I need to do a new scan under OMRI for that to happen?

Regards

Ben
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION] I could catch a crash today. Happened yesterday too, but the log was empty. Just now i was able to catch it.

Environment:

Joying Android 8.1

Intel Airmont eight-core 1.8GHz

SC9853i

DAB+ USB box

SD-Card in slot

USB dashcam in record mode.

Precondition:

FCC Car launcher active in foreground

DAB broadcasts visible in widgets (Logo, artist and title in different widgets)

DAB-z running in background

ReadItToMe running in background

Skype running in background

TomTom running in background

Observed behavior:

Skype message arrived

ReadItToMe tried to get audio focus to read the message by TTS engine

In this moment DAB-z crashed

Expected behavoir:

No reset.

Attachments:

Logcat from crash
[Android Head-Units] realzoulou:
If you first installed the Play version and then removed the original one, DAB-Z will find the one from Play Store, of course.

The dialog would appear when you select a station that sends MP2 audio and no plugin is installed.

EDIT: Sorry, I misunderstood. So, you updated DAB-Z to the latest (1.5.55 currently) and removed the git hub plugin. Yes, then you should see the dialog when you first select a DAB (MPEG) station. Maybe it needs a reboot to occur, because Android does not kill the app when you close it, but keeps it in RAM if possible.
[Android Head-Units] realzoulou:
Google has rejected my version 1.2 of the MPEG plugin. It will take some time to provide you with a solution. Sorry for that.
[Android Head-Units] realzoulou:
My repect! You know how to write bug reports :)

This type of crash is known already and reported to the OMRI developer. But it seems to happen randomly only.

Was the crash yesterday (with empty log) in the very same situation, i.e. when ReadItToMe started to output audio?

07-08 20:15:51.661 17913 28664 E AndroidRuntime: FATAL EXCEPTION: Thread-947853
07-08 20:15:51.661 17913 28664 E AndroidRuntime: Process: com.zoulou.dab, PID: 17913
07-08 20:15:51.661 17913 28664 E AndroidRuntime: java.lang.IllegalStateException
07-08 20:15:51.661 17913 28664 E AndroidRuntime:	at android.media.MediaCodec.native_dequeueOutputBuffer(Native Method)
07-08 20:15:51.661 17913 28664 E AndroidRuntime:	at android.media.MediaCodec.dequeueOutputBuffer(MediaCodec.java:2632)
07-08 20:15:51.661 17913 28664 E AndroidRuntime:	at org.omri.radio.impl.DabAudioDecoder.decode(DabAudioDecoder.java:8)
07-08 20:15:51.661 17913 28664 E AndroidRuntime:	at org.omri.radio.impl.DabAudioDecoder.access$700(DabAudioDecoder.java:1)
07-08 20:15:51.661 17913 28664 E AndroidRuntime:	at org.omri.radio.impl.DabAudioDecoder$4.run(DabAudioDecoder.java:2)
07-08 20:15:51.661 17913 28664 E AndroidRuntime:	at java.lang.Thread.run(Thread.java:764)

As a side note: via Google Play Console and Fabrics Crashlytics crashes are reported automatically to me, if the unit has Internet access.
[Android Head-Units] rigattoni:
It´s just a minimalistic bug report, not as I would expect it from our customer, devs and tester, but that would be oversized I think ;)

Yes it happened in the same situation. It´s not really reproducible for now, otherwise I would have mentioned it.

As additional information about the version of ReadItToMe:

Because the latest update from playstore of this app does not work anymore, I use the version 2.2.5, just to use the same version if a retest would be neccessary on dev side.

Regarding your side note: In this case the automatic report should have been sent to you too.
[Android Head-Units] Ben.suffolk:
I did try a full reboot of the head unit, but I’ll check again tomorrow to make sure the update I did took me to 1.5.55
[Android Head-Units] IG_Vasilich:
My 2 cents for testing OMRI on Intel SoFIA (FYT 6021) with 2 GB RAM + Android 6:

it crashes quite frequently - mostly either when trying to set favorite flag for station, or when tuning to other station. Logs attached.

When switching to other station works - it is really fast when the previous station was on same frequency. Though i have feeling that tuning to other freq takes a bit longer than with libdab.so.

Another issue - i haven't managed to save SLS picture (from HR Ost/West) as a logo - nothing happens when i keep holding my finger touched to logo station. It worked once for other station this morning, so it can have smth to do with station name?

About recording with OMRI: is it impossible, or just not implemented yet?

Thanks in advance
[Android Head-Units] skiib:
Crashing dab

Hi after updating to new version on play i have got a problem.

with zoudab playing and gps on my screen everything is ok. But when i go to homescreen and tapping on zoudab to get back to dab screen it stops playing and crashing/freezes. I have tryed and old version nousbuf it dosent crash, but when starting this version i have to grant acces everytime.Anyone have a fix for this.

My unit is a china unit T8 running oreo 8.1 with screen 1024x600
[Android Head-Units] Ben.suffolk:
When I started it yesterday it did indeed offer to install the plugin, so not sure why it didn't do it from as reboot. But all good now. Interestingly once installed I could not get any audio until I did another reboot.

Ben
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION], I need to withdraw my statement that the crash is not reproducible.

At each startup with the first notification read out, DAB-z crash happens.

I had a look into the traces, it is always the same issue.
[Android Head-Units] realzoulou:
Yes, it has sth to do with the station name: The slash "/" in "hr4 Nord/Ost" causes a problem. I will need to filter out such characters internally.

java.io.FileNotFoundException: /storage/emulated/0/DAB/logos/user/hr4 Nord/Ost.png: open failed: ENOENT (No such file or directory)

OMRI does allow to record audio, it is just not implemented yet.

Maybe I can come up with sth. much cooler that the libdab.so based "simply" recording.
[Android Head-Units] lexdh:
I have the same problem with the NPO channels with OMRI. No sound. Sometimes i have sound, but mostly no sound. Did you already looked into this?
[Android Head-Units] Tumke32:
[MENTION=7838245]realzoulou[/MENTION] you fixed this problem a few releases ago, but since i gues 2 or 3 release ago there is a new problem. When i use the next button on my steeringwheel the app is paused. The back button Works fine. Can you please fix it like before? Thanks!
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION],

would it be possible to freeze (or a setting to decide if it would be needed) the notification updates when the app is on pause?

I´m running into the issue that if I switch in FCC widget to Poweramp V2 pro, that after some seconds artist, station and logo are shown in FCC widget.

Healing is to switch off DAB-z on audio focus switch... but that is not really comfortable, because fast switching between the sources is in this case not really possible.

I think/hope, that pausing notification too would heal this issue.
[Android Head-Units] IG_Vasilich:
I agree with [MENTION=2534110]rigattoni[/MENTION]: i also continuing to get notifications about playing song change (those are from launcher CarLauncher), when FM radio is active.

"what to do when another music player starts to play" setting in DAB-Z is set to "pause playing".
[Android Head-Units] Ben.suffolk:
I had an issue yesterday morning with no audio from omri, I tried with libdab and audio was fine. What do you need me to try and capture when it does this to help identify the issue?

Omri was showing a bitrate of 80kbs but no codec, libdab was showing a bitrate of 128kbs and mp2 codec at a sample rate of 48khz.

So it looks like the bit rate was not being recognised correctly. I suspect this would be one of those times when on the hour it dropped back down to 80 an libdab would screw up audio.
[Android Head-Units] skiib:
Dab Icon

Hi does anyone know how to get another icon for this app. Need a brigther icon for my head unit
[Android Head-Units] cozzykim:
I just installed DAB-Z on my older Pumpkin Single DIN dual core head unit running Android 6.01, with a DAB adapter that I only bought this week.

It's much nicer to use than the original clunky app of course. :good:

I found that I find more stations with OMRI but there's no sound from any of them, it works fine with the OMRI option deselected.

Can I help to resolve this by providing any more info?
[Android Head-Units] Ben.suffolk:
It should have asked you to install a plugin for the audio to work. If not have a look back a few pages and it will tell you what you need to install from the play store.
[Android Head-Units] davemazo:
Same here on my Joying airmont unit. I don't know what omri is but I enabled it, installed the addon but I too get no sound. I do understand though that at the moment there are some issues so I unticked the omri box and this excellent app is back to normal
[Android Head-Units] cozzykim:
Sorry, I should have said:

It did ask me to install the plugin which I did, V1.1

I also rebooted several times after reading the thread comments.

I've uninstalled and reinstalled everything and it's still the same.

Is there some way to tell whether the plugin service has been called, or even started?

There's no sound from any stations at all by the way.
[Android Head-Units] realzoulou:
It helps if you could give the name of the station that was not working and if it was consistently not working. A logcat via the DAB-Z built-in button press as quickly as possible (ie. not waiting minutes or hours) after the issue appeared also helps. Some systems only capture a few seconds, some capture half an hour, but I cannot influence this.
[Android Head-Units] realzoulou:
Some areas in UK have DAB+ stations meanwhile, i.e. audio in AAC format. With such stations I'd expect no audio issues anymore (crashes: yes).

You can swipe on the image/logo then the station details are shown. When the audio format is empty, then there is also no audio. Root cause is still not really understood.

When it shows "MP2" then it is a DAB station, when "AAC" is shown it is a DAB+ station.

Question: Do you have AAC stations that have no audio?
[Android Head-Units] realzoulou:
Are you sure that not maybe something on your head unit changed? I did not touch this code area at all in the past releases. And it is quite strange that "next" and "previous" have different behavior. A system-wide logcat would help to see what is going wrong. If you are not able to create such, a DAB-Z logcat via the Settings/Info could maybe be enough, too.
[Android Head-Units] realzoulou:
Will make this configurable in a next version.
[Android Head-Units] cozzykim:
Thanks for the hints, I'll check for MP2/AAC and report back. :good:
[Android Head-Units] Ben.suffolk:
Its BBC Radio 4 (As always that I have problems with). Here is a logcat. I swapped between turning OMRI on and off (you can see the app restart in the logs when this happens). Whilst the bit rate was wrong (showing 80 when it was really 128) it would always not play audio via OMRI.

For some reason it also seems to pick a different station from my favourites list when the app starts. You can see in the logcat it picking BBC Radio 2 and BB Radio 4 Xtra (Pretty much I only have BBC Radio 4 selected). I can't be exactly sure about when it does that but I think it's either when there is no audio, or possibly its just picking the last used favourites number which happens to be slightly different list between OMRI and LIBDAB. I shall look to see if thats whats happening when the audio is working correctly under OMRI.
[Android Head-Units] cozzykim:
Okay, I checked and you're correct. I live in a poor reception area so there aren't too many stations to check, but I found that as you say the DAB+ AAC stations like Virgin Chilled work fine with OMRI enabled, and it's the DAB MP2 stations that don't have any audio. The sample rate is always empty even if I leave the station selected for several minutes.

I also looked at the staus of the MP2 decoder plugin, does this help? The unit is a Single DIN QuadCore-R16 by the way.

Thanks for your help and the great app.
[Android Head-Units] Alexander_Kwame:
Please let me know if I have to install the plugin?

Thanks
[Android Head-Units] realzoulou:
DAB-Z would tell you automatically if you would need it. Since Italy is only using DAB+, there is no need for a MPEG decoder plugin for you.
[Android Head-Units] realzoulou:
The favorite station lists are kept separate when switching between libdab and OMRI.

When you select a station as favorite while using libdab.so, it is NOT automatically a favorite when using OMRI (and vice versa).
[Android Head-Units] Ben.suffolk:
Yes I think I worded it badly for you to understand what I was saying. I can see the lists are different, but what I meant was if I have BBR4 in both lists (but a different position due to the missing some stations lower in the list) when I switch between OMRI and libdab on restart it loads a different station to what I was listening to last time. I suspect because its remembering the last station was number x in the favourites list, then because the list changes it loads station from position x which happens to be a different one.

Not an issue at all, it was simply confusing me as I initially though it was giving a different station due to no audio on the OMRI with Radio 4, but then I figured it was more likely to be the above scenario. I have not tested that to be sure but I will.
[Android Head-Units] realzoulou:
Yes, this is a bug. The software keeps a number that is used for both variants. But because the favorite lists are different, the number points to a different station.

I will not fix this bug, because my mid-term plan is to remove libdab anyway and it happens only when switching middlewares.
[Android Head-Units] cozzykim:
Update:

I plugged my DAB004 adapter into my Pixel 3 via OTG, installed DAB-Z and the OMRI option works fine on all stations that I tested both MP2 and AAC.

Does this mean that the difference is something to do with my head unit's older Android 6.01 version perhaps?

On my Pixel 3, the decoder plugin service is running in the background even when the DAB adapter isn't present and DAB-Z isn't running - On the head unit the MP2 decoder doesn't seem to get started, and isn't running as the 'FORCE STOP' option isn't present.

Does this suggest that the service isn't being started under 6.01 perhaps?
[Android Head-Units] Tumke32:
Yep, you were wright. I checked my steeringwheelcontrol app and i noticed something was changed. After resetting the controls and mapping it to the buttons it works again. Sorry for the inconvenience.
[Android Head-Units] realzoulou:
Nice approach of testing thanks for that! Which is just another indication how different Android devices are, and our Chinese Android head units have likely never passed the tests defined by Google's Android Compatibility Program and so there is virtually no guarantee that an app works on such a device.

Anyway... a new version of DAB-Z is in the queue already with a significant amount of changes under the hood...
[Android Head-Units] realzoulou:
Google Play release 1.5.59

Google Play release 1.5.59 is available now

IMPORTANT NEWS:

1)

When using OMRI mode, you will need to start a new scan for stations. After the update the station list is empty.

This is due to a change in how stations are stored by the OMRI middleware, which is meant to improve startup performance.

2)

The extra DabMpg123DecoderPlugin app is no longer needed and I will very soon take the Google Play version 1.1 of it offline.

The github version 1.0 is outdated. Please deinstall them after you update to this release manually. DAB-Z will remind you at every start to deinstall it!

Because the DabMpg123DecoderPlugin is not shown in the launcher app list, you need to deinstall it using the Android Settings app.

Open the Settings menu on your device. After that, open Apps or Application manager (depending on your device), find the DabMpg123DecoderPlugin app, select it, and then just tap on the Uninstall button.

Change log:

New

* OMRI: An external DabMpg123DecoderPlugin app is not needed anymore, because it is now built into DAB-Z.

You can deinstall the DabMpg123DecoderPlugin app (both github and Google Play versions) from your system manually.

After you deinstalled DabMpg123DecoderPlugin, please reboot the system.

* OMRI: During scan, the progress dialog shows the number of stations found so far.

Bugfixes

* OMRI version is updated to 1.0.12 with numerous bugfixes (e.g. NL NPO stations now working, greatly improved stability)

* OMRI mode only: After performing a station scan, displayed station name is not matching actually played station

* OMRI mode only: Scanning with "keep favorites" option did not start

* Logo storage via long-press on image not working for stations containing a slash "/" in the name (e.g. "Radio East/West")

* When PAUSED, DAB-Z sends out no metadata information to other apps/launchers (I decided to make it not configurable)
[Android Head-Units] rigattoni:
:highfive: :good:

Sent some bucks for a beer or 2...
[Android Head-Units] VBA_Dev:
Does anyone know if UK stations support the MOT slide show? I cannot find any info anywhere so I presume not.
[Android Head-Units] cozzykim:
The new version is crashing on my head unit.

It also finds far fewer stations than the older version with OMRI/DABMPg, only the ten BBC stations in fact.

There is also no sound in the few seconds that it's working. :crying:
[Android Head-Units] ZeroZorro:
1.5.59 first test results:

Much better using OMRI mode!!

Dutch (NPO) channels working just fine now and I am not experiencing crashes.

Sometimes changing channels is instantly, sometimes it takes 3-5 seconds.

Thought that it was only when first using a channel but seems randomly.

Only bug so far: when pushing back (while playing) untill exiting the app and then restarting it will not autoplay (or at least no sound) untill changing channel.

The same when usb got disconnected/connected again. (This happens quite a lot with my device, did not find a solution yet to prevent this from happening).

Great progress!!!
[Android Head-Units] DaAntipop:
Some stations are broadcasting MOT SLS. I know that 'Capital London' and 'Heart London' have an SLS service. The problem why it's not displayed in DAB-Z is that the MOT Slideshow is transmitted in a different Subchannel and (currently) the implementation of the USB-adapter driver delivers only one Subchannel at a time. Therefore it chooses to decode the audio Subchannel rather than the Slideshow ;) .

Most other DAB services which support Slideshow transmit the MOT as PAD (Programme Associated Data). Also Dynamic Label is transmitted as PAD. This PAD is a portion of data at the end of the main ServiceComponent Subchannel. So only one Subchannel is needed to have audio and MOT applications.

---------- Post added at 07:47 AM ---------- Previous post was at 07:40 AM ----------

Thanks for reporting back that the NPO services are playing fine now :D

The time needed for a service change depends on which Ensemble the curent and the newly chosen service is running. If the service is on the same Ensemble, and therefore on the same radio frequency and same Ensemble parameters, the new service will play almost immediately. If the service is located on another Ensemble, the tuner has to tune to the new frequency, collect Ensemble and Service parameters, and play the new Service. This takes some time.

I had the same problem with disconnecting/connecting USB stick. For me it helped to use a passive USB 2.0 hub. Since I use the hub no more disconnects happen.
[Android Head-Units] ZeroZorro:
Can you share which hub you use, cause I have a cheap Chinese hub that I use for powering my Dashcam and Huawei MiFi but they are another USB port.

To rule out I prefer to buy one that has proven to work ;)
[Android Head-Units] VBA_Dev:
Thanks for the excellent & comprehensive answer [MENTION=8485978]DaAntipop[/MENTION] ?
[Android Head-Units] davemazo:
Excuse my ignorance but what is MOT SLS?
[Android Head-Units] VBA_Dev:
A slide show that is transmitted alongside the audio. So for example an image of the current artist or news/weather. Or adverts!