yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] surfer63:
No. You really have a genuine Android 12 on SDK level 31.

Is it a 7870 FYT based?
[Android Head-Units] TorstenH:
DABdream version 1.2.14​

is available as open test on Google Play.

Please join the beta program on Google Play to install this beta.

What's new:

1. More station logos via button logo download

Please note: Only tested for German stations. Let me know if it also works for your country. There is still no 100% coverage of station logos.

2. Updated stuttering prevention

Testing at home can't replace the real-world experience and so the setting is still marked as experimental. I'm looking forward to read your feedback.

The setting is a slider but finally there are only two statuses:

- most left ➡️off

- >=1 ➡️ on

I kept this as slider for now because I still don't know if it makes sense to make the sensitivity adjustable. Otherwise the setting will become a simple switch.
[Android Head-Units] FiveInline:
Im using both DAB-Z and DABdream in my car, with an Android 13 head unit.

It seems to me that i have much more stable and stronger signal with DAB-Z, is it any settings i can try on DABdream?

On DAB-Z there is also an small Service Following icon (SF) on the channels that support it.
[Android Head-Units] TorstenH:
You can click on the signal bars to execute SF manually.

Here you can see how to check if a station supports SF:

https://xdaforums.com/t/dabdream-dab-player-for-usb-adapters.4638309/post-89384305
[Android Head-Units] Abgl1619:
What is 7870 FYT and where to find if it is that?
[Android Head-Units] TorstenH:
After tons of discussions regarding station logos, I expected massive feedback... 🤣
[Android Head-Units] richmask:
I have only just updated to new version, scanned for logos but didnt bring up anymore station logos than previous. Located in UK
[Android Head-Units] TorstenH:
Thank you for your feedback. Could you provide me the details of two or three stations you're not getting a logo for? This would help me to check if it should work.
[Android Head-Units] sukimdennis:
I have resetted the app, gave the permissions again...

Started channel scan. 107 channels.

DNS download.

Found 60 of 107 Logos in the first run, 73 of 107 in the secound run and 44 of in the third run.

Gave the app a fourth run and get 79 of 107 Logos.

What?!?

Ok some Logos are still missing.

Reboot app, fifth run 78 of 107 Logos.🤣

But some of the logos dont look good.

I think the new function is not fully developed yet, well it is a beta.

I have resetted again, channel scan again, used my list at first and after that the DNS download, 3 times, some Logos are still missing.

And the download is sometimes very slow and sometimes very fast.
[Android Head-Units] TorstenH:
There is a reason why it's a beta version. 😉

Seems to be a timeout and/or cache issue.

Are you talking about the width/height ratio and transparent background? Or what do you mean with "don't look good"?

True true

We will not have a 100% coverage because some stations don't provide their logo via RadioDNS/Radioplayer.
[Android Head-Units] TorstenH:
If you are not interested in a solution:

1. leave the developer out in the rain and keep the error message to yourself.

2. tell him your free interpretation of the error message - never the exact error message.

3. always give a bad rating before you talk to the developer. This shows appreciation, especially if we're talking about a free app.

4. if it works again, do not change the rating. This avoids the developer having to deal with too many users.
[Android Head-Units] sukimdennis:
These new provided Logos from the stations or from service providers don't look good. Width/height ratio is fine. Transparent background, havent seen one. In the end, more Logos are better than no Logos. 👍🏻👍🏻👍🏻

Ignor, my failure😅, I took the wrong logo.zip file.

I added them manually before, but I thought they were downloaded. So that's the only reason they were missing. My mistake.
[Android Head-Units] TorstenH:
The logos are not hand-picked by me, but are provided by the stations or their service providers via RadioDNS. Unfortunately, I have no influence on this. You may want to write to the stations. I have already done this successfully with one station that did not send a nice logo via slideshow.

I was confused by the screenshots you shared.

No problem. Thank you for your feedback.
[Android Head-Units] TorstenH:
DABdream version 1.2.16​

is available as open test on Google Play.

Please join the beta program on Google Play to install this beta.

What's new:

1. Station logo download considers all ensemble IDs to find more matches.

2. Stuttering prevention is a switch, now. Must be enabled even if it was activated before update.
[Android Head-Units] sukimdennis:
I can confirm that.

If logos are provided by the broadcasters or service providers, they will be found.

If no logos are provided, you can add them separately.

If you add your own logo packs, these logos will be prioritized and overwrite the logos found, and that's a good thing.

Example:

I don't like the blue BOB logo that was provided, see above, and it was overwritten with my black BOB logo below from my logo pack.

In addition, the last missing logos that were not provided are also filled with the logo pack.

Keep going!!!
[Android Head-Units] TorstenH:
The priority is (1 = highest prio):

4. DABdream logo

3. Downloaded logo

2. Logo set by logo pack or single image

1. Logo set via slideshow image
[Android Head-Units] TorstenH:
DABdream version 1.2.16​

is available as public release on Google Play...

What's new:

1. More station logos via RadioDNS logo download

2. Updated stuttering prevention

Must be enabled after update even if you used it before.
[Android Head-Units] TorstenH:
DABdream version 1.3​

will come with better TTP.

After I've already done a lot to improve TTP (time to play) in earlier versions, it's time for the next step:

DABdream 1.3.x will include optimized decoding of MSC audio data in native C/C++.

This improves TTP and also allows to continue playback after signal loss with minimal delay. This could also lead to the user impression of better receiption quality.

I give a first preview with the video below.

The stations SWR3 and DASDING are on the same frequency so there is no need to switch frequency. This also influences TTP:

Stay tuned...
[Android Head-Units] MasterOfLight:
I found a minor glitch. When the App switches from day mode to dark mode, the visible station buttons change the background. however the invisible ones not. they are all in the bright color still. just a small visual glitch
[Android Head-Units] TorstenH:
Which setting are you using? "Auto (follow system)" or "Auto (GPS)"?

Or does this also happen when you switch the theme manually from Day to Night?
[Android Head-Units] MasterOfLight:
I'm using Auto (GPS).

Manual switching works, I tested it right now and all is fine
[Android Head-Units] TorstenH:
Okay. I will try to do some tests and let you know if I hopefully can reproduce the issue.
[Android Head-Units] TorstenH:
I was able to reproduce the issue and beta version 1.3 will include the fix.

I simulated a switch to Sunset and the result looks good, now.

Thank you for reporting the issue and your help to make this app better. ♥️
[Android Head-Units] MasterOfLight:
that was really fast, thank you (y)
[Android Head-Units] TorstenH:
DABdream version 1.3.3​

is available as open test on Google Play.

Please join the beta program on Google Play to install this app version.

What's new:

1. Improved reception performance

This includes faster TTP / time to switch stations

2. Show hint to scan if station list is empty

Users already complained about empty station list before they started a scan. To improve app experience and avoid bad ratings, the app forces to start a station scan via a dialog.

🐛 Additionally this version fixes these bugs:

- switch to dark / night theme caused by "Auto (GPS)" only partially changes UI elements.

Since there are a lot of coding changes behind the scenes this is "only" a beta. Looking forward to read your feedback...

Fixes (only relevant for beta dev)

- fix mp2 playback (untested)

- fix station only playing after selected 2nd time
[Android Head-Units] richmask:
Just tried the newest version 1.3, my favourite stations do not play at all, reception is full bar but no sound. I have unistalled and reinstalled from playstore, the app scans stations 80 in total but it sometimes shuts down after scan is finished. Please help
[Android Head-Units] TorstenH:
That's really surprising me.

Do you have the possibility to capture the Android log? Especially after the app shuts down?

Could you please take a photo of the station details of one of your favorite stations? Is none of the stations playing or only your favorite stations not?
[Android Head-Units] Burkenhoerster:
Hi Torsten,

first of all, big thanks.

I really like the app.

However, it is still causing some difficulties on my Sinosmart TS10S.

When I connect to Android Auto via Z-Link, the radio continues to play in the background and does not stop.

For example, Spotify and DABdream run at the same time.

In addition, the app doesn't start properly from time to time when I restart the radio. It then runs, but is not visible.
[Android Head-Units] richmask:
I have reverted back to version 1.2.16 by downloading from apkpure. The stations work fine, when i get home later i will try download to 1.3 think i missed an update and skipped a version. Could be nothing but worth a try first before sending a log
[Android Head-Units] TorstenH:
Thank you very much. I'm very happy to read that.

Could you check if other 3rd party apps stop playback? E.g. by installing a mp3 player app.

This would help to identify if it's a problem only DABdream has.

Sounds for me like another app starts after DABdream and so it gets pushed to background. You could investigate the Android log to see what's happening after the DABdream start. Alternatively you could export the log with an app like Logcat Reader directly after reboot.
[Android Head-Units] TorstenH:
Would be great if you could test with 1.3 because it contains many changes and maybe one or more of the issues is already fixed.

Just a guess: I've read that some stations in UK are using the mp2 audio format (old DAB instead of new DAB+). That might be related to the issue.
[Android Head-Units] kugyman:
Hi,

I have also experienced some stations not playing sound although have full signal bar. I believe this happens only after a new scan(keep favorites). Not completely sure, because driving at the time of scan and not paying attention to radio more than the road. I think I have then closed the app and started again and it worked. Will try again later, and try to observe more closely.

But I must say, It seems that the reception is better. Plays music also at locations, where would previously stop. I am using it with disabled stutter prevention.
[Android Head-Units] TorstenH:
I think that's currently just a timing issue and switching temporarily to another station on another frequency seems to be a workaround.

I must do some dev tests before I publish the fix asap.

I'm happy to read that because that's the reason for the latest change and so it's worth the effort.
[Android Head-Units] Burkenhoerster:
Yesterday i deinstalled DABdream and installed DAB-Z and everything was ok. Also AA workes correct and DAB-Z stops playing.
[Android Head-Units] richmask:
I have tried the update 1.3 again, app not shutting down as before but it still not playing most stations even with full bar signal. My favourite station kisstory is on channel 11D
[Android Head-Units] TorstenH:
Thank you for the feedback. According to this side

11D content of DAB UK London

Bitrate measurements of TV channels and Radio DAB+ DTT FIBER Satellite Cable OTT.

www.digitalbitrate.com

we're really talking with Kisstory about a station using MP2 codec.

I will provide an update tomorrow which should fix the issue.
[Android Head-Units] TorstenH:
New DABdream version 1.3.1 will be available as beta within the next hours.

After I left mp2 (DAB) playback behind acc (DAB+) playback I pushed it to the same level. E.g. features like stuttering prevention are working also for DAB stations, now.

Please note:

- I can only do dry tests for mp2 stations as all German stations are using DAB+ standard.

- Please perform a station scan, first. I've seen that Kisstory station details doesn't show the audio codec so I made it to a mandatory info to collect during station scan.

Let me know if the new version is an improvement🤞
[Android Head-Units] TorstenH:
New DABdream version 1.3.1 will be available as beta within the next hours.

Playback start should be reliable for all stations, now. There is no need to select a station for a 2nd time to get audio output. I tested this with my whole station list several times.

Let me know if you can also observe an improvement.
[Android Head-Units] TorstenH:
Unfortunately I can't reproduce this behavior. DABdream stops as soon as I start audio playback via Zlink.

Please provide the Android log in a private message so I can continue to investigate the root cause. Thank you.

@ all: can you confirm this issue on your head unit?
[Android Head-Units] MasterOfLight:
it works fine for me as well. As soon as ZLink starts an audio playback DABdream stops
[Android Head-Units] TorstenH:
New DABdream version 1.3.2 is available as beta on Google Play.

I restored two functionalities of the productive release:

- suppress invalid slideshow images / images with artifacts

- show only complete dls text (after switching to another station)
[Android Head-Units] FiveInline:
I have compared DAB-Z and DABdream in my car a couple of days now.

DABdream v1.3.1 and v1.3.2 have been used.

There is no doubt that DAB-Z has a much more stable and better signal reception. Driving towards the city near my town, DABdream looses signal completely every single time, while DAB-Z manage to keep a strong signal. On a standstill in town (parked), DABdream had 1 bar signal strength, while DAB-Z had 3-4 bars.

DABdream seem to fluctuate in signal strength alot, going from 4-5 bars and down to 1 bar or to loose signal completely. This behavior seems to happen frequently.

I have tried:

Service Following ON/OFF

Prevent Stuttering ON/OFF.
[Android Head-Units] TorstenH:
Please understand that I will not reply to public comparisons of DAB-Z and DABdream. That's not a style I like because both apps are for free and the developers invest thousands of hours in this apps so I want to avoid blaming - even if it would be only indirect.

Just note that the signal bar indicators of the apps are not compareable.
[Android Head-Units] FiveInline:
I have sent you a reply on PM.
[Android Head-Units] richmask:
Torsten, ive tried this version its not playing Kisstory UK, we have spoke before and you were going to add mp2 old dab playback. Ive had to revert back to 1.2.16 to get stations to play. When on 1.3.2 any station i select plays for 1 sec then stops, full bar on signal. Its such a great dab player im hoping a fix can be solved to make it one of the best apps for head units
[Android Head-Units] TorstenH:
I've send you a private message.
[Android Head-Units] kugyman:
Hi, I can say, that since updated to 1.3.1, I no longer have issues with playback not starting. Everything works as it should. Music plays stable, no interruptions, signal reception is better. Will try 1.3.2. to see further improvements.
[Android Head-Units] TorstenH:
Thank you for the confirmation which absolutely fits to my observation.

I will provide v 1.3.3 today which fixes minor bugs and contains cleaned code so it might make sense to wait until it's available.

Before I will release 1.3.x as public version I want to fix the mp2 bug together with @richmask
[Android Head-Units] TorstenH:
Fixed a bug 🐛 in latest beta: App freezes after exit.

New beta version 1.3.4 will be available within next hours.

I drove a bit and changed the stations via SWC. Here is the corresponding recording:

Might be a bit boring due to no dropping signal bar or other issues 🤣
[Android Head-Units] TorstenH:
DABdream version 1.3.5​

is available as open test on Google Play...

Please join the beta program on Google Play to install this app version.

What's new:

1. Restored DAB (mp2) playback capabilities

Since all German radio stations are using new DAB+ (acc) standard this was only possible with the awesome help from @richmask

Additionally the audio codec gets shown correctly on station info view, now.

This version is the candidate for the next public version.
[Android Head-Units] TorstenH:
DABdream version 1.3.6​

is publicly available on Google Play. 🎉

What's new:

1. Massively improved playback performance 🚀

2. Improved TTP (time to play) 🥇

3. No initial cawing 🦅

4. Several bug 🐛 fixes and improvements

My big thank goes to the XDA community and their amazing test support!

Thank you for your engagement. 🥋
[Android Head-Units] richmask:
Do i need to upgrade my version of the test one?
[Android Head-Units] TorstenH:
I suggest to do so but compared to your test version we're only talking about code cosmetic 💄. There is no need to clear app data or cache and you can simply run the update via Google Play Store.
[Android Head-Units] Lacki12:
Dabdream with latest version does not store the 12 A frequency.

With other dab apps no problem. Only to me?
[Android Head-Units] TorstenH:
Unfortunately I don't live in a region where stations on 223,936 MHz (12A) can be received.

Let's see if anyone reports the same problem.
[Android Head-Units] G.Scholtens:
Ik heb je even een pb gestuurd
[Android Head-Units] Lacki12:
with dab z , the frequency 12A is stored.
[Android Head-Units] TorstenH:
In case of you can send me the Android log directly after station scan. Write me a private message if you need further instruction.

Update: I've sent you a private message because this might be just a confusion.
[Android Head-Units] Lacki12:
I discovered that dabdream tunes all the frequencies available in my area, only that it only stores 64 radios out of 103.

for example, the 12A stores only 1 BBC WorldService radio
[Android Head-Units] TorstenH:
Unfortunately you've not answered my question I've sent you via private message.

Nevertheless, consider the description "Synthetic Service Following", please.

https://xdaforums.com/t/dabdream-dab-dab-player-for-usb-adapters.4638309/post-89126460

It makes absolutely no sense to compare the number of found stations with other DAB apps because DABdream lists each station only once (based on the Service ID).

Here you can see a station which is available on four different channels / frequencies:

Sources for the alternative channels are:

1. A station gets found a second time during scan

2. DAB submits alternative frequencies from time to time. Dabdream collects this information in background while you're using the app.
[Android Head-Units] Lacki12:
Dab z, no problem.
[Android Head-Units] TorstenH:
DABdream also no problem as already described here:

https://xdaforums.com/t/dabdream-dab-dab-player-for-usb-adapters.4638309/post-89505615
[Android Head-Units] Lacki12:
I deleted dabdream version 1.3.6 and reinstalled dabdream version 1.1.8, as you can see there is a difference,this version stores ok
[Android Head-Units] TorstenH:
Please uninstall 1.1.8, install the latest DABdream version and execute a full station scan. Then share the details of station RTL 102.5, please.

Please note: The station details are scrollable so there are additional fields below Service-ID.
[Android Head-Units] Lacki12:
I've already done this, reinstalling 1.3.6, it doesn't store RTL and many others
[Android Head-Units] TorstenH:
Please execute a station scan and send me a private message with the Android log.

Also send me a private message if you need further assistance to export the log. Thanks.
[Android Head-Units] dfahren:
Hi there,

@TorstenH : Can you tell us whether or not your app is capable of receiving and displaying TPEG traffic messages? Maybe it's a feature you plan to implement in the future?

Best wishes,

Deetsh
[Android Head-Units] TorstenH:
Currently there are no plans to implement this feature. Even more interesting than traffic messages (because most users use a navigation app which provides traffic information) are audio alarm announcements.

I never used a radio EPG. Is this really a relevant feature in an automotive scenario?

All mentioned features would be hard to implement and would require massive testing support. Finally it depends if enough people are interested in the mentioned features and are ready to invest time to support me.
[Android Head-Units] TorstenH:
DABdream version 1.3.7​

is available as open test on Google Play.

Please join the beta program on Google Play to install this app version.

What's new:

1. Possibility to set accent color

2. General improvements and bug 🐛 fixes
[Android Head-Units] dfahren:
Oh, that's a real pity that you don't have any capacities to implement this nice feature.

Well, TPEG ist not some sort of an Electronic Program Guide (EPG). It is this:

TPEG - der Digitale Verkehrsservice der ARD

Sie haben ein Navigationsgerät? Das Navi zeigt Ihnen Staus an? Dann gehören Sie wahrscheinlich zu den Autofahrern, die Verkehrsinformationen von der ARD erhalten.

www1.wdr.de

But I think you already know this, don't you?! It is the successor of the rather slow and inaccurate TMC used in conventional FM-RDS receivers in cars.

In fact many drivers use their head unit or mobile phone to get the latest traffic jam infos in order to have Google Maps or some other program do the best routing, but in my case I don't want to use a phone or an online map if there is nearly as accurate and timely information broadcasted by big broadcasting stations.

If I had time, I would like to implement it myself, but unfortunately with kids and a demanding job, time is a very scarce resource.

Thanks for your input and all the best!

- Deetsh
[Android Head-Units] TorstenH:
I wasn't sure if you really talk about TPEG traffic because it makes only sense to use this data for a navigation software and not for a radio application like DABdream. An offline navigation could use this data to suggest alternative routes and show the traffic situation on its map.

Additionally DAB+ provides a programme guide:

Same situation here 😉

You're very welcome.
[Android Head-Units] sukimdennis:
I think some people need a little help with creating log files.

It didn't work for me straight away and took a few attempts, and I sometimes spent minutes searching for the saved data.

But now I think it's working quite well.

So I decided to make a short video tutorial and hope I can help a little.

The steps:

You need a log file reader.

In this example I'm using this one:

Logcat Reader | F-Droid - Free and Open Source Android App Repository

Eine einfache App, um Systemprotokolle einzusehen

f-droid.org

More information here:

Releases · darshanparajuli/LogcatReader

A simple app for viewing logs on an android device. - darshanparajuli/LogcatReader

github.com

Start the Logcat reader, start recording, a message appears below, recording starts, and just let it run.

Then start Dabdream and reproduce possible errors.

Then switch back to the Logcat Reader and stop recording, a save message appears at the bottom.

You can display saved logs at the top right.

With a long press on a file, you can save or export it directly. Bluetooth, G Drive etc. ...

Then you just have to send this file to the developer.

Generally, the transferred Bluetooth data can be found in a separate Bluetooth folder or, as in my case, in the download folder.

This file can be incredibly helpful to the developer in locating possible sources of error and then fixing them.
[Android Head-Units] TorstenH:
Thank you for sharing your knowledge. Awesome!

Please note that LogCatReader needs READ_LOGS permission. Many head units grant this permission automatically but in some cases this permission must be granted manually. Unfortunately that's not possible using the Android UI and so ADB must be used:

adb shell "pm grant com.dp.logcatapp android.permission.READ_LOGS && am force-stop com.dp.logcatapp"