yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] realzoulou:
I introduced a bug into 1.0.33 that affects stations that broadcast MP2 audio (DAB standard = MP2, DAB+ standard = AAC audio encoding)

It results in both a) crashes, b) "fast forward" audio.

I found the root cause and I am preparing a fix already.
[Android Head-Units] biker_955:
Strange as I am on Dab, and I didn't notice the crash or fast audio. Maybe 'cause my HU is a 1Gb unit?
[Android Head-Units] royalhawk2002:
It is possible that the bug is affecting also other apps? At last cold reboot I was on the bluetooth streaming app and the same occurred also with it. The issue is started from this morning after I had installed the Google Play Dab app.

I don't have the fast forward audio problem

Inviato dal mio SM-N960F utilizzando Tapatalk
[Android Head-Units] realzoulou:
Only when the station was sending audio with a mono channel only instead of 2 channels (=stereo)

I strongly doubt. On Android, one app should never be able to influence another app in such a bad way as you describe.
[Android Head-Units] rknuette:
I have a diffent issue with the latest release from Google Play.

On some apps which require the audio channel, especially a TV app (DVB T2 hardware connected to clinch audio input) the audio channel is only lowered, therefore DAB Radio is always in background playing with lowered audio while TV is in foreground with normal audio (it's like lowering audio with navigation software). It does not occur with all apps (build in FM radio app acts as expected).

This haven't happened before.
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION],

Hmmm.... running into a similar issue today.

If DAB-Z is running in background and I choose the FM radio app, DAB-Z is still running in background and just lowered. But you are able to hear the DAB in background playing.

Same for any other player. Even if the new player is in foreground (but paused) DAB-Z is playing.

In the past, DAB was closed if another player required the audio channel, as rknuette wrote.
[Android Head-Units] royalhawk2002:
This morning at first boot no crash happened but I saw in the notification bar Dab Z starting for 1 second and then disappeared leaving the home page of the default launcher. Started the app manually worked fine. Following hot boots from standby were ok

Inviato dal mio SM-N960F utilizzando Tapatalk
[Android Head-Units] Ben.suffolk:
Today I updated DAB-Z and FCC Beta to the latest versions from Play Store, I'm I'm really pleased to see that now the radio information (station name and whats playing) doe snot keep going blank. Not sure if that was the update to FCC or DAB-Z that fixed it but its working now :)

For me the think that would really make my head unit as I want it, is to be able to change to a station from FCC without having to switch into DAB-Z and then back again. I think this could be done by FCC being able to send an intent to DAB-Z. It would be really great if you could change to a station like that.

Ben
[Android Head-Units] realzoulou:
I can confirm this bug and will fix that soon.
[Android Head-Units] rigattoni:
Thanks realzoulou.

Would it be possible that DAB-Z just gets muted instead of closed? That would be nice to have it running complete without waiting...
[Android Head-Units] realzoulou:
Yes, that's my plan.
[Android Head-Units] realzoulou:
I just replied to a very similiar request on Google Play. When pressing the HOME button while DAB-Z app is visible, the DAB-Z app should not stop playing. If this is the case for you then see below:
[Android Head-Units] rigattoni:
Hi [MENTION=7838245]realzoulou[/MENTION]

there seems to be an issue with updating the notification for at least the station "Absolut Relax". The Album art is not updated frequently and this leads to the problem that old pictures are shown in any widget which listens to the notification update. The notification differs to the picture shown in the app itself.

I coould not verify this behavior with other stations as "Antenne Bayern".
[Android Head-Units] johno2004:
Music skipping

Hi downloaded latest app from play store on my car android head unit and all's well detecting all the channels but as soon as I select any station it just skips every second or so like an old record making it un listenable.

Do you know why this is happening and how to fix it.

Thanks
[Android Head-Units] realzoulou:
what head unit do you have?

If your CPU is an Allwinner T3 running Android 7, then I am sorry to say that this app will not work properly.

If you have a PX5 based unit, try adding a USB hub in between HU and DAB adapter.
[Android Head-Units] johno2004:
Yes it's the allwinner T3.

Gutted app looks great.

The dab software that came with it is the same so you g to ask seller for a fix or they can have it back.

Only got it for the DAB.

Do you know of a DAB app that will work with the allwinner T3

Thanks
[Android Head-Units] realzoulou:
Other users with a Allwinner T3 on Android 7 said that this version would not stutter:

http://download.seicane.com/doc/12/DabPlayer-pad-201603310918.apk

Just in case you want to ask: Yes, it is 2,5 years old and no, I cannot make my app based on this old one.
[Android Head-Units] realzoulou:
Can you reproduce it even with ServiceFollowing=disabled?
[Android Head-Units] rigattoni:
Good question....

I will try out tomorrow morning on my commute.
[Android Head-Units] rigattoni:
It was reproducible with both settings of the ServiceFollowing.
[Android Head-Units] Willinickersen2:
Will only download "13E" channels in Norway... 9

Sent fra min SM-G965F via Tapatalk
[Android Head-Units] Wout2426:
Example:
[Android Head-Units] Flemischguy:
Normally it would, but that's for app writers like real zoulou, this radio board is open source like you can see in the link.. http://www.monkeyboard.org/products/85-developmentboard/80-dab-fm-digital-radio-development-board .

For some, the price could be to high (90 Euro) for the monkeyboard sold by a German car pc store by cartft.com.
[Android Head-Units] kampfschachtel:
in switzerland the app shows already some station logos, not all of them but some.

Favorites is a great and welcomed add on:good:

very much appreciated, looking forward to the next release.
[Android Head-Units] Tumke32:
That is the 1.0 app. i have the same logos there. In the 2.0 version you have 2 places were you can see logos. one place is the same like 1.0 but the 2.0 has also logos in the stationlist. in the stationlist i only have 1 logo.
[Android Head-Units] sausist:
I'm having a problem with this app.

When I had the malaysk rom it worked very good.

Now I have changed to dsa rom and every time the dab app loses its signal.

Sometimes after 5 seconds , sometimes 2 minutes , ...

The dab+ app stays open but signal is gone. When I close the app and reopen it works again for some time but loses signal again.

I already installed the nousdevice and the regular one.

What could this be ?
[Android Head-Units] surfer63:
I'm thinking of purchasing Joyings DAB+ adapter as well, using this improved app.

One question though: If the Joying reboots it always starts the builtin radio. Now with the DAB+ apk and hardware, does it still do that? Or does the DAB+ app and hardware prevent that?
[Android Head-Units] realzoulou:
Yes. This is because some JY system app changes to the FM Radio App before it actually performs the reboot. After the reboot the FM Radio App will come up again because it was the previous foreground app.

Installing the DAB+ app (regardless whether the original, or my modded one) will not change the Joying specific behavior.
[Android Head-Units] surfer63:
Yeah, I was already afraid so. The sofiaServer apk calls the "com.syu.carradio" (talks to the FM/AM chip) and then the "com.syu.radio" (frontend that talks to the carradio).

I only hoped the DAB+ would do "something" to prevent that by means of some hidden setting or whatever method.

I already have been thinking to mod the sofiaServer to prevent it from starting the "com.syu.radio" automatically but it's actually not worth the effort.

Or to not have it start the "com.syu.radio", but to have it start the "com.ex.dabplayer.pad". Again: not worth the effort.
[Android Head-Units] realzoulou:
I suspect that the USB connection to the DAB stick gets lost. In this case the app does not react to it, but runs into a busy loop consuming quite a lot of CPU.

If you are using the 2017-06-23 version, then you could create a folder named "dablogs". The folder must be be located in parallel to the Download folder.

Then the DAB app writes its logcat output into the dablogs folder all the time. The filenames contain the local date and time, when the file was started.

I will take a look at the logs if you want...

To deactivate this tracing feature, delete the dablogs folder again.
[Android Head-Units] sausist:
Thx , just inspected the usb dongle and its broken :( . I have bought a new one.
[Android Head-Units] kampfschachtel:
I think this worth the effort as this FM radio startup is pain in the ass, having this cripple sound while it boots, I am not using dormancy mode as I have several strange behaviuors when using it. So I am forced to listen to cripples for min. 10sek with volume I had before till I am able to change it. ****ing 6 android....:silly::eek:
[Android Head-Units] edit:
+1
[Android Head-Units] realzoulou:
Release YHX-DAB+V170519-zoulou-170726 -----> "join piece"

As announced earlier here, this is now my "join piece" in Android app modding :)

YHX-DAB+V170519-zoulou-170726

Download: REMOVED

Changes (see also the Changes.txt from the download)

Layout mods:

- Left and right area equally distributed (50/50 instead of 60/40)

- Station list additionally shows DAB channel and Ensemble label

- Added "favorite button" at right hand side of service name to switch station list between "full list" and "only favorites"

- Added large notification icon

- Added "Settings" button to notification, which starts a new Settings activity

Fixes:

- Fixed: Avoid "Connecting..." screen. You should additionally activate "Avoid running twice" in Settings.

- Fixed (2nd attempt): When using steering wheel controls, avoid issue with scrolling by 2 stations instead of only 1.

The fix is to add a debounce time of 150 ms between changing stations.

New:

- Can only be installed on Android >= 4.1.x ("Jelly Bean", API level 16)

- A long press on a row in the station list toggles the "favorite" status of a station.

A favorite station is marked with a "star".

- When DAB App is not visible and steering wheel controls were used to change station, a Toast informs about current, previous (in current list) and next (in current list) station name.

- When App is started with no DAB USB device, a Toast is shown and App exists.

- The App stores persistently, which station list was last active: full, filtered by favorites, or filtered by PTY

- The internal SQLite database format has changed in order to introduce the favorite station list feature.

Please uninstall any previous versions before installing this version. Please start a new service scan afterwards.

In order to enforce this, the DAB+ App is signed with a new key (valid until year 2042).

- Undocumented feature introduced in 20170623 release:

The DAB App produces a logfile of its own traces only, when a folder "dablogs" is created by the User.

The folder must exist in the "external storage directory". This is usually the directory which also contains "Documents", "Download", "Movies", "Notifications", etc. and is typically opened by default by your File Manager app.

- Removed assets/dab.bin (~8 MB) since it seems to be superfluous.
[Android Head-Units] OnkelDeffe:
Great work! Will try it tomorow ... can you send me (PM) your bank account info; paypal donation does not work and I would like to send you 10,- € reward for your work! Perhaps the new app will handle my steering wheel commands when not visible ;)
[Android Head-Units] Jedimindtriks:
Nvm, fixed it :)

thanks again for an awesome job Zoulou :D
[Android Head-Units] Wout2426:
Installed it, it's really nice, and works great. Thx !
[Android Head-Units] realzoulou:
Honestly, I doubt.

The App supports 3 methods of receiving events from steering wheel.

1. Via the "standard" Activity:onKeyDown() function: keyCode 87 = NEXT, 88 = PREV

(can be tested with "adb shell input keyevent 87")

2. Via broadcast intent "android.intent.action.MEDIA_BUTTON". Again keyCode 87 = NEXT, 88 = PREV.

3. Via MTC specific intent "com.microntek.irkeyDown". Here keyCode 300 = NEXT, 299 = PREV.

(can be tested with "adb shell am broadcast -a com.microntek.irkeyDown --ei keyCode 300")

My Joying Sofia uses option 2. All of the MTC(B/C/D) devices should support option 3.

Option 1 is typically not working when the DAB App is in background. There seems to be some Android system app that sends the key to the Media Player in the system. But the DAB App is not the Media Player! And so this event does not get delivered to the DAP App.

Yeah, I was already thinking of making it configurable in the Settings whether you want this additional info, or not.

I will put this into my TODO list... ;)
[Android Head-Units] realzoulou:
Btw. Thanks for pictures! For a lot of you guys the MOT picture is not well aligned. Never saw this before. Will look into this too.
[Android Head-Units] OnkelDeffe:
I used the custom key assign function in factory settings to set the steering wheel buttons for functions "Next track" and "previous track" - don't know which internal message function is used here. Should I try different function assignments? (If I remember correctly it is possible to assign 2 functions for one key or for long press function)
[Android Head-Units] halo_djk:
Good news.

Latest version, no more moving DAB Z icon on the home page. Nousb switch doing what it should.

Only tiny niggle for me is that when my unit goes deep sleep, if music player or radio are active at shut down, they come back up when you wake up, it would be sweet if we knew how they did that so DABZ could do the same. At the moment it comes back on without the app running even if you shut down with it running.

---------- Post added at 05:11 PM ---------- Previous post was at 05:11 PM ----------

Good news.

Latest version, no more moving DAB Z icon on the home page. Nousb switch doing what it should.

Only tiny niggle for me is that when my unit goes deep sleep, if music player or radio are active at shut down, they come back up when you wake up, it would be sweet if we knew how they did that so DABZ could do the same. At the moment it comes back on without the app running even if you shut down with it running.
[Android Head-Units] IG_Vasilich:
that depends on ROM of your headunit.

E.g. on FYT headunits the ROM remembers foreground app before going sleep, and restores it after wakeup. THere is a special handling for built-in radio app, bluetooth app, navi, music player. So to let ROM handle DAB-Z as your music player, you need to put the full name of DAB-Z app to a special text file with list of all apps that ROM will treat as a music player. The file is located in SofiaServer system app (assets\property\player_app.txt), but you need to unpack that SofaSetver app, change that text file, pack the app and replace it on your headunit - for that you need to have root rights. Sounds complex, but you need to do it only once.

I don't know whether it is possible on not-FYT units though.
[Android Head-Units] halo_djk:
Thanks IG. I'm not rooted and it's only a little inconvenience. Takes no effort to just tap the DAB Z icon when I start the car. =)
[Android Head-Units] IG_Vasilich:
i just wanted to mention, that (at least) in case of FYT-based HUs, not the app handles wakeup, but ROM. So zoulou cannot do anything to change behavior of DAB-Z after wakeup.
[Android Head-Units] Ben.suffolk:
FCC launcher (others may be able to do the same), can be set to auto start apps when the unit wakes up. So you could have a look at downloading something like that to help you.
[Android Head-Units] Joecool92:
Is this a Dab-Z or FCC problem? The app crashs after switching beetween quick players or sometimes after back button. also other media players start in background, only dab z opens after quick selected. i will report this to fcc too.

btw: without mail app the logcat report crashs too. i will make a log after installing an mail app.

https://youtu.be/MU8Hre_4wVA
[Android Head-Units] biker_955:
I managed to use a file manger to save the logcat to the sdcard.

The latest version fixed my logo issue thanks.
[Android Head-Units] realzoulou:
No need to send me a log. I get this reported by the built-in Crashlytics module. The crash is caused by a simple bug in DAB-Z itself.
[Android Head-Units] abbots:
I was looking to install the DAB+, noticed here it's on GPlay, many thanks, installed this morning, works well, thanks!
[Android Head-Units] bancswissunique:
Experience with Joying PX5

Just wanted to share my experience in case it helps others:

I own the following equipment:

Joying JY-VO130P4 (PX5, 4GB RAM, 32GB ROM, Android 8.0 with latest update at time of writing)

https://www.joyingauto.com/joying-eu-warehouse-android-8-0-oreo-system-8-inch-vw-skoda-seat-car-music-system-head-unit-4gb-32gb.html

Latest DAB-Z app from play store (v1.0.37)

https://play.google.com/store/apps/details?id=com.zoulou.dab

External DAB+ active antenna from Aliexpress

https://de.aliexpress.com/item/Universal-DAB-Erweiterung-Antenne-Mit-USB-Adapter-Empf-nger-F-r-Android-4-4-5-1/32853981586.html

I had no issues installing the head unit as well as the DAB antenna based on the manuals that came with them. Reception was also good (all green bars) and the station scan was successful. The only issue I initially had was with frequent stuttering (every few seconds). The way I got it "fixed" was by deactivating "suppress audio distortions" in the settings menu. This option is active by default but in my case it made the audio sound very bad (creating sound gaps as it is supposed to do). If I switch it off I can't notice any distortions which would bother me but the audio quality is very good. Interestingly even though I had "Show a short notification if audio distortions have been filtered." enabled I never saw a notification.

P.S.: I do not use any USB hub and the DAB+ adapter is connected to USB2 while USB1 is not in use atm. There is no reason I chose USB2 it was just the first thing I managed to grab when installing the adapter.
[Android Head-Units] biker_955:
With latest from play (yesterday) I am experiencing the closing issues. Was playing happily for about 5 min then closed, I restarted it and it closed after 30 sec.
[Android Head-Units] realzoulou:
[MENTION=1641760]biker_955[/MENTION]: please provide me with a logcat. The changes that I did in 1.0.37 (9 Nov 18) are solely stability related changes. I did not touch any functionality.
[Android Head-Units] biker_955:
WIll do next time it does it.
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

have tested DAB-Z after being used the version from this thread (nousb). Now i can delete stations from the list, thanks!

But it has same behavior as an old app: for interface in notification area the logos are being cut to square. It looks bad esp. for some logos that have aspect ratio far from square (e,g, Sunshine live, where only 2 letters in the middle can be seen, or SWR - only part of W is visible).

Not sure if this is the reason why the launcher i use (CarLauncher) also shows the same picture as an album art.

Another issue with this picture in notification area - it refreshes too seldom - much more seldom than the station logo/picture changes. Is it intentionally? I like it, when for some stations there are album art changing for every track...
[Android Head-Units] biker_955:
here is the logcat from after it quit the 1st time
[Android Head-Units] realzoulou:
Thanks, but your system does not buffer enough log data. The previous launch of the app, which you say ended in a sudden quit, is not in the log. So, I cannot tell for sure what happened, sorry.

I assume that the USB connection to the DAB adapter suddenly dropped. This is currently the only reason, why the app suddenly quits. I guess I should add a notification to the user when this happens.
[Android Head-Units] realzoulou:
The app cannot decide how exactly the metadata is shown. I use a "MediaStyle" notification from Android. The SystemUI of Android is responsible for displaying the content and yes, I can reproduce myself all what you noticed. But I cannot influence the SystemUI. If it wants to scale, crop, or whatever the bitmap, which the app sends into the Android system, then Android can decide to do so. I have written a test app in order to verify that the content is transferred correctly. I verified that the bitmap itself is unchanged.

FCC car launcher obviously uses a similiar way to display the bitmap as Android does and so also here it looks odd.

I also can reproduce that sometimes a new bitmap is not updated in the notification and often is takes quite some time for the update to get visible. I only can say that I send the metadata update into Android as soon as you see it in the app. At the moment I see no way to improve the current situation.
[Android Head-Units] biker_955:
Strange as it is wired direct to the front port. It also didn't happen with previous versions.
[Android Head-Units] biker_955:
It seems to happen when the signal is lost/poor in my case. As I said it is only with this latest one it has started happening.

EDIT:

Have installed the external dab/fm antenna so will see if it still quits on me now.
[Android Head-Units] IG_Vasilich:
As all music players (i have tested) had no problems with notifications (the new text and album art were instantly visible in notification area on every track change), i can just assume that Android not always (or with delay) reacts on LargeIcon changes only. Does your app sends changes in LargeIcon only, when the bitmap from DAB changes?

your app also has no problems to change the station logo in case of station switch, so i assume there should be a dependency of updating LargeIcon on other information changes...
[Android Head-Units] IG_Vasilich:
[MENTION=7838245]realzoulou[/MENTION]

I have written small app that just changes LargeIcon and pushes a notification. And it works always (i see all changes pushed) -even if push it 4 times per second!

So i assume the way i do it differs from yours.

If you interested in my way - just let me know in private (as i don't think this part is interesting enough for others in this thread).

Thanks.
[Android Head-Units] royalhawk2002:
[MENTION=7838245]realzoulou[/MENTION]

last version is working well but I noticed that at cold boot, if it was left running at switch off, it doesn't restart automatically.

All the apps restart at cold boot if they were running at switch off, the same was for your DAB+ not from Google Play.

---------- Post added at 12:45 PM ---------- Previous post was at 12:45 PM ----------

[/COLOR [MENTION=7838245]realzoulou[/MENTION]

last version is working well but I noticed that at cold boot, if it was left running at switch off, it doesn't restart automatically.

All the apps restart at cold boot if they were running at switch off, the same was for your DAB+ not from Google Play.
[Android Head-Units] Darkfleet:
Hi, I have tried installing this via the play store on my android headunit (comes with dab+ app stock), but google lists it as not compatible with my device? I am currently waiting for the usb dab module to arrive so not too much of a problem yet
[Android Head-Units] realzoulou:
If Google Play does not list it for you, then you have a Android 7 with Allwinner T3 CPU, right?

I excluded this device "t3_p3" from being compatible. Audio will stutter and I cannot fix this.

You will need to use the DAB+ app, which comes preinstalled.
[Android Head-Units] Darkfleet:
Yep spot on, damn oh well, maybe I'll re-theme it myself if I can be bothered.