yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] DanDanskin:
Yep, you're both right, my xtrons has memory/CPU issues I believe.

I turned off a few of the settings that CPU load was reduced and it seems to be stable for me.

And I really can say

OH MY WHAT AN IMPROVEMENT OVER THE STOCK PLAYER.

I was so exited to see favourites I nearly wet myself :)

I'm now looking to get AGAMA so I can see the player on the home screen.

Then I'll clean my seats :)

Thank you zoulou I'll drop you a bit of cash as soon as I send this.
[Android Head-Units] typos1:
It would be a hell of a lot of work writing an app from scratch that acts as an interface for both radio sources though.

Android stereos are identified by their MCUs, not the seller - Xtrons sell unit from several manufacturers, so it cant be established by saying "my Xtrons unit" as it could be from any number of manufacturers.

If you have an MTCB/C or MTCD/E unit with an RK3188/PX3 1Gb RAM processor, memory problems (lack of RAM) can be aleviated somewhat by installing [MENTION=5228031]Johny DJ[/MENTION]'s ROMs with microG.
[Android Head-Units] Flemischguy:
I finally installed my PX5 with 4 gb mem and 32 storage and android Oreo and the latest DAB Z app from the Google play store. Everything works fine except with the DAB+ receiver. I have a shark fin antenna with build in GPS/DAB+ and FM receivers. (the FM Receiver is not in use). Before i installed this new radio, the reception with my DAB+ monkey board in my old radio was exelent. With the new radio the reception disapointing. I cant receive any public radio station if i stand stil, and if i ride , it stutters. The other commercial radio stations i can receive, althoug it sometimes stutters while the signal quality indicator say's it has a good reception. Could it be a faulty DAB+ receiver? I changed usb cables, changed connections, DAB+ connector on the gps and the gps on the DAB+ receiver, put my old radio back in the car with the monkey board in, and this works flawless. Before i installed the radio in to the dashboard, i tested everything. About the signal quality indicator, is less better or higher better i'am a bit confused about that, if i have no reception bars the signal quality shows 8000. Did someone's encounter such problem, if so what was the solution??

I post a video so you can see what i mean. https://youtu.be/BawbKXQTyog
[Android Head-Units] SkyBeam2048:
I am not entriely surprised. On my KLD MTCE unit with Joying USB DAB+ receiver I get occasional crashes too. Yesterday I have installed the Google Play version of DAB-Z. Then launched it, immediately went to settings to do the configuration first. I have enlarged station and song text, disabled audio filtering and imported the logos (seems to use the ones from the same location as the non-Google-Play version).

After this I went out from the settings and clicked the scan button. It seemed to have found all the stations (around 160 available here) and right when the scanning finished the app crashed.

Even worse it immediately crashed again on each re-launch. So it was absolutely impossible to open the application again.

To fix this I went into Android settings and cleared the data of DAB-Z app. This time I have opened it and immediately scanned for stations. This worked fine. Even after performing the same configuration settings afterwards (including logo import).

Also sometimes I cannot tune-in some stations. I have not found a clear pattern yet but I suspect it has something to do with the frequency. So the effect is that some stations work perfectly while on others you simply don't get any signal. Rebooting the entire unit helps but also sometimes the DAB+ app crashes and after crash I can re-launch it and it works just fine again. I think it's perhaps some issue with libdab you can't resolve.

Sorry, it's all a bit fuzzy as I don't want to complain about this. The GUI of this app is as great as it's functionality and as good as it gets given the fact the underlying DAB library is not available in sources. The issues described above are not even bothering me hard enough to investigate. I just re-run the app. Just the repeated crash on initial DAB-Z configuration might be reproducible and perhaps can be solved.
[Android Head-Units] DanDanskin:
Sounds the same as my issues, but it gets more stable after a few drives?

I think it's just first run issues when it uses lots of CPU downloading images etc on a head unit that dies not like high load!
[Android Head-Units] halo_djk:
Never had a crash with the downloaded version. But now with the play store versions I had four crashes last night. It went something like this...

Installed three days ago after uninstall of previous version.

Runs fine for a few drives, and waiting for image to show full screen logo to save on the stations list.

Change channel and immediately saw a full screen logo for the station so quickly pressed and hold the logo. CRASH!

Music kept going and I get a box saying report or restart. Music stops when I click either option.

I restart app. On another station, seems OK, but if I go back to offending station, every time that same logo comes up (as one image was now playing and another with the weather then one blue image with just the station logo) the app crashes (music continues as above)

Not happening on other stations, but did on one station different from above station.

Tried restarting

Rescanning

Force stop and clear storage.

Head unit is Chinese oreo. 4gb ram 32gb storage.

Also have problem relating to sleep mode, DAB Z always comes on when starting car even though I was listening to mp3s or fm radio when it went to sleep. (annoying).

I did use the report button once from memory, so hope some data came through.
[Android Head-Units] realzoulou:
I think that I got the crash logs from your unit. Looks like this image from that "offending" station is too large to be processed by Android as part of an Intent.

Could you please disable the option Settings->General "Broadcast information as Android Intent to other apps" and then repeat the same procedure?

My assumption is that it then would not crash. If this turns out to be the case then I need to somehow limit the size of such images from DAB stations.
[Android Head-Units] realzoulou:
[MENTION=6246726]Flemischguy[/MENTION] I watched your video and did some research on Belgium's DAB stations.

on https://www.worlddab.org/country-information/belgium/multiplexes I can see that station "MNM" on channel 12A from the VRT ensemble seems to use DAB standard. So it should use MP2 audio codec, but I see in the video that the app seems to use AAC audio codec for decoding, which is only used by the DAB+ standard.

Hmm, this could get difficult to resolve, because there is no way for me to test such a scenario in Germany.

Btw. regarding signal quality: lower numbers are better: 0 = super perfect. 8000 = no signal.
[Android Head-Units] realzoulou:
Generally agreed, but this could be nearly infinite amount of work. Do you know a generic FM Radio app that works on all these Chinese head units ? Only if this exists, then it would be even worth thinking about starting a combined FM/DAB app.
[Android Head-Units] realzoulou:
For me it's funny to see how different the requirements are. Some want full screen station logo, you want full screen station list :)

I will consider this when I start working on a new layout.
[Android Head-Units] rigattoni:
[MENTION=7838245]realzoulou[/MENTION]:

Found an app crash while toggling between FM and DAB+ today.

Used system:

MTCE_KLD
Coretex-A53
PX5
Android 8.0
Hal9k Mod 3.0
FCC car launcher

Observed behavior:

Start DAB+ and listen to it

Press toggle button to switch to FM radio

Listen to FM radio

Press toggle button to switch back to DAB+

DAB+ is starting and playing

After some seconds a crash notification pops up, while DAB+ is still playing

Addes a log file as 7z file and a short video as zip file.
[Android Head-Units] realzoulou:
I released DAB-Z 1.0.30 to Google Play.

This adds the previous "nousbdf" feature into the app. There are no 2 versions needed, all is in one app.

In Settings->General you can enable/disable "Automatic start on USB device detection". Previously this was some workaround, but now it really works.

But because I use some trick here to avoid having to maintain 2 app versions, it behaves a bit odd:

When you change the setting, then the app closes itself after ~5-10 seconds.

You may also notice that the launcher icon disappears (if it was a shortcut only).

I cannot avoid this. It is Android killing the app because I exchange the main activity inside the app.
[Android Head-Units] realzoulou:
Thanks a lot, rigattoni. This ANR seems to happen only on Oreo devices. Its not fixed in 1.0.30, but I know the root cause at least now. Google changed sth. in Android 8, which I will have to adopt to.
[Android Head-Units] deswr1:
Skipping audio

I'm using a dab+ dongle on my joying Android px5 unit it works fine with the Dabplayer pad H2.12 APK, but with the Dab Z APK I'm getting audio skipping or stuttering haven't tried the newest update yet. I've put a link to the dongle I've got

https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.co.uk/ulk/itm/263202455829
[Android Head-Units] Flemischguy:
Thank you for the reply.

I living near the Dutch border (aprox. 10 km) and did this weekend some test driving and came to the conclusion that when i drive more inland towards Antwerp the DAB+ signal drastically improved. Some other things that i noticed is that my monkeyboard picked up al the Dutch radio stations on my drive way if i scan for radio stations, that's what this DAB+ receiver does not do. I exclude the antenna as the problem, so i think it had to do with the hardware that can't handel weaker DAB+ signals very well, something the monkeyboard can cope. Your doing a lot of work for all of us on the software and that's why that i donated you. Thank you.
[Android Head-Units] halo_djk:
Another crash, but this one happen within a second of the app opening. I sent through the report marked Kym S crash as I was driving..
[Android Head-Units] typos1:
Sadly an AM/FM app that works on all Android head units is an impossibility due to the different radio tuners and MCUs used, so any combined AM/FM/DAB app would have to be custom made for each Android stereo platform. Its a shame Android stereo manufacturers dont go the same way as OEMs and use a combined AM/FM/DAB tuner, but they wont do that as that would mean the same unit couldnt be shipped all over the world.
[Android Head-Units] rigattoni:
This is correct.

This is not correct. ;)

OEM have different FM and DAB tuner. Some of them are working with dual FM tuner, but they are working under a single UI.

The only difference is, that for some markets different additional tuner (SDARS for USA/Canada, DAB for ROW)) are added.

All other settings as frequency range, availability and functionality are set by configuration for the specific market.

Which means, that it would be possible to use any European FM tuner in each other market by configuration.... Just SDARS needs the specific satellite receiver.
[Android Head-Units] dj.shauny.g:
Having difficulty with the logos showing up with car AGAMA launcher.

The logo is actually showing up but i can't get rid of the original background picture.

See link https://imgur.com/a/W2cDKqn

Any help would be appreciated.

Thanks.
[Android Head-Units] royalhawk2002:
Updated to last version from Google Play but I have the same issue of before. Each time the radio start it ask to grant the USB permissions. I try to enable/disable the "Auto start on USB device detection", without success. I don't have this issue with the old apk (not the Google Play version). At the moment I am with the Xtrons Oreo 8.0 stock ROM. I don't know if the issue is related to the fact that I didn't remove the old version of the apk.
[Android Head-Units] giant53:
Same here. It is because the logo has a transparant part. So the default Agama image is showing through. Where I live most logo's have a solid background, so the default image is not visible. It is not a dabplayer fault. A solution could be provided by the Agama developer.
[Android Head-Units] typos1:
Some OEMs use one combined AM/FM/DAB chip.

I know FM settings can be configured for different markets, you misunderstood my post - Android stereo manufacturers do not want to ship Android stereos with AM/FM/DAB tuners worldwide when the DAB side cannot be used worldwide, which is why they ship with AM/FM tuners and DAB is added as a module.
[Android Head-Units] halo_djk:
I'm using the nousb option, but every time I start up the usb permissions box appears. I've tried ticking the don't ask again box, not ticking it and not using the nousb version but I can't get a start up without the box?
[Android Head-Units] royalhawk2002:
Same issue for me. I reported to the Developer here but, until now, no answer
[Android Head-Units] surfer63:
[MENTION=7838245]realzoulou[/MENTION]: There is a bug (or change) in Android 7 and above. See here.

Maybe the "android:directBootAware="true"" should be added to your "com.zoulou.dab.service.DabService" activity.

Like:

<service android:name="com.zoulou.dab.service.DabService">
<intent-filter>
<action android:name="android.intent.action.MEDIA_BUTTON"/>
<action android:name="android.media.browse.MediaBrowserService"/>
<action android:directBootAware="true"/>
</intent-filter>
</service>

Or maybe you should create such a dummy activity.

(And maybe I'm completely wrong)
[Android Head-Units] royalhawk2002:
Thank you. This is means that you will provide an update soon ?

Please note that the nonusb version not from the Google Play is not affected by this issue
[Android Head-Units] surfer63:
No, I'm not the developer. If you would have read my answer better, you would have seen that I give a suggestion to the developer.

(And I do not know whether my suggestion is correct.)
[Android Head-Units] halo_djk:
I should confirm my system "warm boots" every time. Not sure if this affects things?

When turned off it just sleeps but I'm sure it does cut power to the usb ports. It instantly boots to home screen.
[Android Head-Units] realzoulou:
Thanks for the feedback about the reoccurring USB permission request. I'll try to find a solution. Until then I propose you use the "old" 180804 version. See post #1 for the link to find the download.

[MENTION=2550900]surfer63[/MENTION] Your hint is indeed very helpful. I have only emulated Android 7 and 8 devices, but no real hardware. In my tests with the emulator versions, this issue did not show up. My head unit in the car is Android 6.

The information in the link you provided does not fully apply, but I will try the "android:directBootAware" option. I do not need a dummy activity, because the USB permission is always requested from the MainActivity, not from the DabService.

Please be patient. I have a 9-7 day currently at work and cannot spend time on the app. It could take another 1-2 weeks until I can release a potential fix.
[Android Head-Units] halo_djk:
I can be patient... I'll think of you everytime I tap "ok". =)
[Android Head-Units] surfer63:
Please take your time. Being a "free time" programmer next to your normal work and hobbies, does indeed take almost all your "free time". I'm well aware of that.

I did have a look at the trafficguard apk which is used for Joyings USB dash-cam (and quite some other units dash cams). It also needs access to a usb device, even though it is a camera and not a DAB device.

In the two relevant activities really related to the usb camera (the usb device), it uses:

<activity android:launchMode="singleTask" android:name="com.synmoon.usbcamera.BroadcastActivity" android:screenOrientation="landscape" android:theme="@android:style/Theme.Translucent">
<intent-filter>
<action android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
</intent-filter>
<meta-data android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" android:resource="@xml/device_filter"/>
<intent-filter>
<action android:name="android.hardware.usb.action.USB_DEVICE_DETACHED"/>
</intent-filter>
<meta-data android:name="android.hardware.usb.action.USB_DEVICE_DETACHED" android:resource="@xml/device_filter"/>
</activity>

Could that be helpful as well? It is not in your AndroidManifest.xml.
[Android Head-Units] royalhawk2002:
Thank you for reply. In any case I am using the non Google Play version in the mean time. I noticed that if I start DAB-Z, some time it try to access USB without success... it remain with the msg "Accessing USB". I hit the "back" button and then I start the DAB+ app (not Google Play). It start immediately but in the HU notification bar I see "DAB-Z" instead of "DAB+". Could be the issue related to the fact that I have both versions installed ?
[Android Head-Units] dj.shauny.g:
Cant get google assistant to open the app. Has to be done manually
[Android Head-Units] biker_955:
The latest version has a bug for me. It will not launch from my launcher after setting don't auto start on dongle.

To fix I removed the shortcut and recreated it after changing it to something else first (just reselecting it didn't work)
[Android Head-Units] kampfschachtel:
I have the same USB permission request bug BUT I run GTX Rom on lastest joying 6 release provided by gustden (think december 2018 one).

Just done a clean install means wiped everything, installed the december release (update from stock unrooted 25 may 2017 release), rooted it with superuser/adb from surfer's extra app and then GTX Rom and downloaded the DAB-Z from playstore. So it seems not only Android 7/8 related issue/bug.
[Android Head-Units] surfer63:
And what did you tell the Google Assistant to do?

(And I don't mean you told the Assistant to f*** up afterwards)
[Android Head-Units] dj.shauny.g:
Haha i just said "o.k google, open DAB Z"

Then i tried "o.k google, open Radio", "open DAB Radio"

None of them worked.

It was saying it can use other music sources to open (youtube music, spotify ect.)

It can't open this app whatever you say to it.

I posted this because i can open all other apps with assistant, but this one will not open.
[Android Head-Units] surfer63:
An app "listens" to its app name, which is the label in the AndroidManifest.xml, which mostly refers to the value of app_name in res/values/strings.xml.

In this case that is DAB-Z.

I'm afraid the GoogleAssistant is having trouble with that. Is it some algebraic sum, like DAB minus Z? and how should that be pronounced?

I tried a few options as well, but I can't start it either.
[Android Head-Units] dj.shauny.g:
I wonder if the older version worked?

As the app name was DAB +

Seems alot easier to pull than DAB-Z
[Android Head-Units] rigattoni:
No the old one is not recognized too.
[Android Head-Units] kampfschachtel:
If I want the stations from several countries, eg. Austria, Germany, Switzerland, France, Italy, Monaco what do I need to do after I downloaded all the countries seperatly from VW site and unzip them:

1) Copy the png files from each country into one big folder eg. named Europe

and then copy Europe Folder to the folder DAB/logos/ on the joying

2) or do I keep each country seperatly

and then copy each country Folder to the folder DAB/logos/ on the joying

and then sync
[Android Head-Units] dj.shauny.g:
I wonder if this could be fixed.
[Android Head-Units] surfer63:
2. The channels are organized per country. There is no Europe
[Android Head-Units] kampfschachtel:
solved it. It's kinda solution 2...

Just download and unzip each country, put each unziped country folder on the USB stick.

Then copy all country folders you want to have to the internal memory under DAB/logos/

so that you have the following structure on the internal memory: DAB/Logos/country folders

then synchrozise them. Close the app and start it new. Job done

by the way:

wasn't working with the DAB-Z from playstore. deinstalled it and installed manually the 18042018 DAB+ version and that worked.
[Android Head-Units] halloj:
From where did you download the logos? Link please. Thanks
[Android Head-Units] ozzybon:
UI

Hi zoulou, I'm hoping you don't change the UI as I really like it, I look forward to each new release for additional features you add. The only issue I'm currently struggling with is getting the launcher I'm using to display the radio station data, I'm using Car launcher AG which was doing it at one point but has stopped now and I don't understand why.

Thanks for all your hard work on the app it's much appreciated.
[Android Head-Units] dj.shauny.g:
Crashes on first startup everytime i select your app. Have to go back then restart app to get it 2 work. Also the set app permission to use dab stick everytime keeps popping up at the start even though i have allowed it permission.

I would welcome a new UI, this one seems boring and dated now other oem units look alot better and easier to use.

---------- Post added at 04:19 PM ---------- Previous post was at 04:18 PM ----------

Crashes on first startup everytime i select your app. Have to go back then restart app to get it 2 work. Also the set app permission to use dab stick everytime keeps popping up at the start even though i have allowed it permission.

I would welcome a new UI, this one seems boring and dated now other oem units look alot better and easier to use.
[Android Head-Units] rigattoni:
Use the one from first page. Both issues are known and zoulou is aware of them. He needs some time to fix due to high workload in his regular job. You need to give him his time...

If you have some ideas for a new UI, Zoulou would be appreciated if you would show your ideas.
[Android Head-Units] gozilla79:
Stop button

Thank you for this good working DAB + player.

However, there is a lack in this app and that is that there is no stop button function available.

As a result, the app goes into the background and stops the operation.

This is the case with all music-playing apps such as FM radio, CD player and MP3 player on an android HU.
[Android Head-Units] ab1702:
So what is it that you actually want it to do?

If you want it to go in the background and carry on functioning then all you need to do is press the home button. That works for most apps and not just dab.

If this isn’t the case then I don’t understand what you want it to do as you can’t just pause the radio station and then carry on when you want to.
[Android Head-Units] wizzsb:
Im not sure If im only one, but It seems like theres small bug with sending station logos into notification bar (or media widgets)

The size of logo is too big in notification bar and in the media widgets (from FCC launcher) you

can see only zoomed middle part of the station logo (30% of middle part)

I didnt download any logo mannually (dab-z probably did it by itself on first start)

i can add screenshots later

im on MTCE PX5 HA, Hal9k rom, FCC launcher.

About GUI recomendation, thats what i like:
[Android Head-Units] surfer63:
logos in the notification bar? I don't get these at all. Does you Hal9K custom ROM do that?

(Joying PX5 FYT Android 8.0 stock rom, rooted + Xposed.)
[Android Head-Units] wizzsb:
It works also on stock rom. But you need to enable "data broadcasting" or something like that in DAB Z.

But right now the size of logos is the issue (if I owerwrite logos with f. ex. 130x130 pixels, than is OK, but is not a correct way to resize all channel logos, as with batch resizing I'm losing png files transparency)
[Android Head-Units] surfer63:
I have data broadcasting enabled to get the info in my launcher (CarWebGuru).

But I mixed up the status bar with the notification bar. In the status bar I do have the DAB-z logo. The notification bar has indeed a hugely oversized logo.
[Android Head-Units] Brendo:
True, it's massive on mine (takes 2 swipes/scrolls to get to next notification) - pretty sure it was much smaller and beside the text in the older versions. Also has a large settings button below it

When switching to the dab-z version, I needed to put my icons in /logos/user as /logos did not work as it did in the older versions

dab-z