DAB+ App: (real)zoulou's DAB-Z app (official support thread)

binar1

Senior Member
May 21, 2009
63
11
0
A small thing that I've figured out on my HU (Xtrons MTCD PX5)

- After ignition start up every second time (aprox.) the DAB+ app hangs with "connecting" message. It happens, when I listen to DAB when i turn of ignition and turn it on few hours later.
I have the same connecting problem with my xtrons unit, however it does it every time the unit boots from cold.

Sent from my HTC One M9 using Tapatalk
 

mensand

Member
Jul 20, 2009
18
2
0
I've installed the app and it finds my USB DAB+ stick and i can listen to radio stations. But it only list public stations and not the commercial station wich are all free to air. in the netherlands. Could this be a software or hardware problem? It find 26 stations if i'm correct.
 

realzoulou

Senior Member
Nov 3, 2016
748
871
113
Greater Area Munich
Is there a way to buy you a beer or support you in any way?
Yes, I have a donate button in my profile :)
After ignition start up every second time (aprox.) the DAB+ app hangs with "connecting" message
I have the same connecting problem with my xtrons unit, however it does it every time the unit boots from cold.
Few questions to both of you:
a) does this happen with an "original" DAB+ App version, too?
b) have you tried the apk version in the folder "NoUsbDeviceFilter"? Same issue?
 

dennydenny

Member
Jun 24, 2017
11
0
0
Munich

binar1

Senior Member
May 21, 2009
63
11
0
The original DAB+ app didn't do this however it would drop signal every 5 to 10 minutes so gave up with dab untill I installed your modified app

Sent from my HTC One M9 using Tapatalk
 

rigattoni

Senior Member
Apr 27, 2010
1,177
320
113
Fuerth
Ok I'll give it a try.

Sent from my HTC One M9 using Tapatalk
I had the same issue with the second build and it seems that the stick is not ready in time, when the app starts.
Seems that it is just a race condition which leads to this behavior...

With the NoUsbDeviceFilter version there is no issue at all, but for me it is better to use the NoUsbDeviceFilter version. I just push the OK button with tasker when the popup comes up. I don´t need DAB+ always on startup...
 

binar1

Senior Member
May 21, 2009
63
11
0
Then also try the NoUsbDeviceFilter version of my modded version
I have installed the NoUsbDeviceFilter app. All was fine while stationary, no "connecting" issue, however once moving the signal dropped out every 2 minutes forcing me to close and reopen the app to get a signal. I also got a "Unfortunately, DAB+ has stopped" message.
I have rescanned the the channels several times, sometimes no channels or very few channels were found but eventually I had a full channel list.

On my drive home I had a full signal no drop outs everything worked fine so a little puzzled now as to what was going on. I'll give it a few days to see if all stays well.

Sent from my HTC One M9 using Tapatalk
 

dennydenny

Member
Jun 24, 2017
11
0
0
Munich
b) have you tried the apk version in the folder "NoUsbDeviceFilter"? Same issue?
Hi

I've updated the apk to "noUSBDeviceFilter"-one from the Archive (25.06.) with APK Installer...

The Problem is now a little different but result is the same:

Before: the App seems to double start and then hanging with "connecting"
Now: It doesn't double start but when the DAB-app starts and TomTom too there is also "Connecting-Loop"

Except that everything is pretty well: I've perfect reception and no drop-outs wherever I drive. Maybe a result
of my new DAB-Antenna which I've installed...

BTW: For those who have difficulties with reception... don't use glass or indoor antennas etc. for DAB... If
you really want seamless audio you'll need a good external Antenna like the one which comes with the car for
GPS, FM etc.
 
Last edited:

binar1

Senior Member
May 21, 2009
63
11
0
Hi

I've updated the apk to "noUSBDeviceFilter"

Before: the App seems to double start and then hanging with "connecting"
Do you mean multiple instances of the app? I have suspected that might have been a problem with the original dab+ apk as when i closed the app there was another instance in the background. Killing apps though task manager was needed to get a signal.

I too have a roof mounted + amplified dab+ aerial so should get as good a reception as possible.

Sent from my HTC One M9 using Tapatalk
 

dennydenny

Member
Jun 24, 2017
11
0
0
Munich
Do you mean multiple instances of the app? I have suspected that might have been a problem with the original dab+ apk as when i closed the app there was another instance in the background. Killing apps though task manager was needed to get a signal.

I too have a roof mounted + amplified dab+ aerial so should get as good a reception as possible.

Sent from my HTC One M9 using Tapatalk
It looked like the app is starting two times:

At ignite it comes up from background... black screen... then "connecting"... -> after that the same again.
 

Icefeldt

Senior Member
Oct 22, 2005
298
13
0
Hi,
in another thread you wrote:

FYI: This app will cease to start after March 2018.
For the 20170328 Version.
Is this still the case?
If yes, I wonder why?

____________________________________

Also, can you inquire about the stuttering issue?
I had a RK3188 4.4.4 device and just bought a DAB+ adapter and installed the DABPlayerpad20160601 which I found in the thread of a 5.1 device.
Worked perfectly, without stuttering.
Now I bought a PX5 unit (which is more powerful) and had stuttering while in background with the stock DAB app provided by the factory rom.
I installed Malaysk's ROM and installed "my old" DABPlayerpad20160601.apk which ran perfectly on the 4.4.4 device.
Again, same problem: stuttering.
Luckily, I now found your modded app.
But I'am still curious, why the same file ran perfectly on the quad core 4.4.4 unit and stuttered on the 6.0 Octa-Core.
Is there an explanation for "non developer" folks? :)

Thanks in advance


PS: Grüße aus Süddeutschland.
 

Jedimindtriks

Member
Feb 5, 2017
43
10
0
Is it possible to get the steering wheel control support on the DAB+ app?

on Mercedes and some volkswagen cars you cannot change stations in the dab+ app. even tho it works in normal radio/CD/AUX.

As soon as you switch to DAB+ steering wheel control stops working.
 

realzoulou

Senior Member
Nov 3, 2016
748
871
113
Greater Area Munich
in another thread you wrote:
For the 20170328 Version.
Is this still the case?
If yes, I wonder why?
Yes, this is still the case. But anyway it looks like Android does not care about the certificate end date. At least in a test with date changed to June 2018, my DAB app still installed fine.
____________________________________

Also, can you inquire about the stuttering issue?
I had a RK3188 4.4.4 device and just bought a DAB+ adapter and installed the DABPlayerpad20160601 which I found in the thread of a 5.1 device.
Worked perfectly, without stuttering.
Now I bought a PX5 unit (which is more powerful) and had stuttering while in background with the stock DAB app provided by the factory rom.
I installed Malaysk's ROM and installed "my old" DABPlayerpad20160601.apk which ran perfectly on the 4.4.4 device.
Again, same problem: stuttering.
Luckily, I now found your modded app.
But I'am still curious, why the same file ran perfectly on the quad core 4.4.4 unit and stuttered on the 6.0 Octa-Core.
Is there an explanation for "non developer" folks? :)
I made the very same experience. With a Joying Rockchip MTCD 4.4.4 device (JY-VL130) I had no problems with stuttering. Never.
Then I changed to Joying Intel Sofia 5.1 (JY-VL130N2) and suddenly the DAB audio stuttering started.
However, there are a lot of people with the audio stuttering problem that have Android 4.4.4 or earlier. So it does not look like this came in with Android 5.

I can only tell that the original DAB+ App does not follow Androids documented way on how to make sure that a service in background gets enough resources from the Android system. And this is the reason why the original App stutters in background.
 

Icefeldt

Senior Member
Oct 22, 2005
298
13
0
Yes, this is still the case. But anyway it looks like Android does not care about the certificate end date. At least in a test with date changed to June 2018, my DAB app still installed fine.
Ah, it was done by the original author of the app?
I thought you implemented that "limitation", that's why I wondered, why you did that.

I can only tell that the original DAB+ App does not follow Androids documented way on how to make sure that a service in background gets enough resources from the Android system. And this is the reason why the original App stutters in background.
Ah, thatnk you for clarifying.