Oh you got me wrong: Yes, I added this limitation because I had to re-sign the App with my own RSA key.
DAB+ App: (real)zoulou's DAB-Z app (official support thread)
- Thread starter realzoulou
- Start date
Hi. tested in a w211 Mercedes. the speedometer says "AUDIO OFF" as usual. but the steering wheel still doesnt work.
the stereo beeps when you press the buttons, but nothing happens. No idea if its related to the car, or the android system or DAB+
it works fine in FM/AUX/CD
Hi,
good news I could reproduce the "connecting-issue". It's just happening when the DAB+-App starts and immediately moved to background
(like at ignition on when e.g. TomTom starts too, even reverse camera seems to affect that).
If the DAB+-App is the only App that's starting and not moved to background at "connecting-state" everything is fine.
greetings, Denny
good news I could reproduce the "connecting-issue". It's just happening when the DAB+-App starts and immediately moved to background
(like at ignition on when e.g. TomTom starts too, even reverse camera seems to affect that).
If the DAB+-App is the only App that's starting and not moved to background at "connecting-state" everything is fine.
greetings, Denny
On my device Joying VL130N2 this scenario works fine. It never gets stuck in Connecting.
I suspect that this problem only appears on some devices.
Which device are you using?
I suspect that this problem only appears on some devices.
Which device are you using?
Even not when reverse camera is enabled when "connecting".??
I have the xtrons octa as well, running malaysk v2, the problem with stuck on "connecting" only happens when the reverse is in before dab has connected. But I'm reversing out of my garage every day, so it's pretty often...
I can confirm that too, same behaviour.
New (replaced) Joying DE-JY-UMS02N2 straight out of the box, total clean, latest 25th may 6.01 release and no mods beside DAB+ app from you. Only your modded DAB+ App (and Spotify + Carly VAG from play store) installed and steering wheel button mapped in settings, other then that nothing else done or setting changed on the joying.
Still a perfect job, again thank you so much as this is the 2nd most used app on the joying so appreciate your work every day. All I wanted to change was changed and DAB+ is finally useable.
Last edited:
Can someone create a logcat of such a startup, which ends in the Connecting screen. I cannot reproduce it myself.
I will try to send logcat when I'm back from my holiday.
App Stops
Hi,
Firstly THANKs for this - MUCH better than the stock app.
However on my Android 6 unit, the app stops after a period when running the background - any ideas?
Ta.
M.
Hi,
Firstly THANKs for this - MUCH better than the stock app.
However on my Android 6 unit, the app stops after a period when running the background - any ideas?
Ta.
M.
Many thanks for this great app - seems to work perfectly on my "px5 modded" XTrons TD101AS - only one minor problem: volume seems to be on a lower level than before - playing music from usb stick or navigation messages are much louder. Is there any way to increase the DAB+ volume? (perhaps in MCU factory settins?)
Greetings
Detlev
Greetings
Detlev
'Backgrounded' DAB app closes
May I add my voice to chorus of thanks. to realzoulou and offer recognition for the obvious time effort realzoulou has invested so far.
Here are my experience notes, in the hope that they may prove useful:
My unit is Pumpkin CN10-01201B Android v6.0 with an external usb connected DAB+ module, model number: 13-Y0251-UK
Stock DAB apk, as for everyone here, is naff.
Annoying checkbox every start, full signal bars cause the display to shift and critically for me, with the App in the background (Waze in the foreground) the music stops after a few minutes and the app has been closed.
Found this thread and it looked like it might be better than what I have, so I removed the stock app, download this APK and via USB installed it on my head unit.
Install completes normally, app can be opened and channels scanned, but no sound. Try volume controls - nothing - fixed at zero. Other audio apps like radio and media player refuse to even start.
In the system settings, the audio level is at zero and cannot be changed. I have obviously lost a component in the audio drivers/sub-system, thinking it may have been part of the original DAB app, I uninstalled this one and searched for the original DAB .apk - found it installed it... still no audio control.
Restarted unit several times - nothing.
Then I performed a system reset using the tiny button 'hidden' in a small hole on the front panel, system starts up with all the installed apps and settings and also with audio and volume control - phew...
Now install this app again but this time there is no problem - app installs, audio control is still present, search stations... all there, and I am delighted to find that this app looks and feels MUCH better than the stock .apk
Now for the acid test. Start the DAB, select my favourite station and then launch Waze from the 'Nav' button which 'foregrounds' Waze and 'backgrounds' DAB.
DAB continues playing normally (I never did get the 'choppy' sound breaking up) for a few minutes and then suddenly silence - the icon in the message bar has gone and the app has closed.
I have picked over the 'apps' section of system settings, but I cannot find any setting for any of the installed apps that might suggest to the OS to allow (prioritise) 'this' app to run in the background without being a candidate for culling.
I have read that the cause of this may be Android 6 and its more aggressive inactive app memory 'harvesting' and reduced options to control that.
I also thought I read that this app is changed to run like a 'foreground service' and should therefore not be subject to this type of culling
Any words of wisdom are welcome.
May I add my voice to chorus of thanks. to realzoulou and offer recognition for the obvious time effort realzoulou has invested so far.
Here are my experience notes, in the hope that they may prove useful:
My unit is Pumpkin CN10-01201B Android v6.0 with an external usb connected DAB+ module, model number: 13-Y0251-UK
Stock DAB apk, as for everyone here, is naff.
Annoying checkbox every start, full signal bars cause the display to shift and critically for me, with the App in the background (Waze in the foreground) the music stops after a few minutes and the app has been closed.
Found this thread and it looked like it might be better than what I have, so I removed the stock app, download this APK and via USB installed it on my head unit.
Install completes normally, app can be opened and channels scanned, but no sound. Try volume controls - nothing - fixed at zero. Other audio apps like radio and media player refuse to even start.
In the system settings, the audio level is at zero and cannot be changed. I have obviously lost a component in the audio drivers/sub-system, thinking it may have been part of the original DAB app, I uninstalled this one and searched for the original DAB .apk - found it installed it... still no audio control.
Restarted unit several times - nothing.
Then I performed a system reset using the tiny button 'hidden' in a small hole on the front panel, system starts up with all the installed apps and settings and also with audio and volume control - phew...
Now install this app again but this time there is no problem - app installs, audio control is still present, search stations... all there, and I am delighted to find that this app looks and feels MUCH better than the stock .apk
Now for the acid test. Start the DAB, select my favourite station and then launch Waze from the 'Nav' button which 'foregrounds' Waze and 'backgrounds' DAB.
DAB continues playing normally (I never did get the 'choppy' sound breaking up) for a few minutes and then suddenly silence - the icon in the message bar has gone and the app has closed.
I have picked over the 'apps' section of system settings, but I cannot find any setting for any of the installed apps that might suggest to the OS to allow (prioritise) 'this' app to run in the background without being a candidate for culling.
I have read that the cause of this may be Android 6 and its more aggressive inactive app memory 'harvesting' and reduced options to control that.
I also thought I read that this app is changed to run like a 'foreground service' and should therefore not be subject to this type of culling
Any words of wisdom are welcome.
I wished I would be able to explain why, but sorry I can't.
There are still a couple of users that see some strange behaviour in conjunction with my modded App and I cannot reproduce them at all on my Joying VL130N2, nor in the Android Emulator by Genymotion.
It seems that nearly every Android model behaves slightly different. This may be because all of them are full with vendor specific system apps, or maybe specific adaptions to the Linux kernel.
I will continue to read carefully any comments in this thread and try to find solutions for common problems if possible for me.
There are still a couple of users that see some strange behaviour in conjunction with my modded App and I cannot reproduce them at all on my Joying VL130N2, nor in the Android Emulator by Genymotion.
It seems that nearly every Android model behaves slightly different. This may be because all of them are full with vendor specific system apps, or maybe specific adaptions to the Linux kernel.
I will continue to read carefully any comments in this thread and try to find solutions for common problems if possible for me.
@realzoulou
As the original app is full of messy code, it would be a wonder if it would work without issues.
The app would not pass the Google shop criterias because the developers don´t even think about google design guidelines.
The credits belonging to you that the app is working quite stable right now.
As the original app is full of messy code, it would be a wonder if it would work without issues.
The app would not pass the Google shop criterias because the developers don´t even think about google design guidelines.
The credits belonging to you that the app is working quite stable right now.
Sorry i see your response this late.
I use this
https://nl.aliexpress.com/item/Andr...32799756951.html?spm=2114.13010608.0.0.RRthFP
But i would like to use the in car antenna. I've a Ford focus. I'm in the netherlands to.
You need a roof antenna. The window type don't work. Only npo, no qmusic or 538 when I drive through my city. (Tiel) reception is just not strong enough.
I ordered this one, not installed yet.
Superbat Universele Dak Mount Digitale DAB Antenne met Versterker voor DAB DAB AM/FM Autoradio Antenne Antenne SMA
http://s.aliexpress.com/ZbE7R3IN
(from AliExpress Android)
If i may do a recommendation, buy a Calearo antenna.
They have a Dutch dealer.
I mounted a DAB+/FM/GPS shark antenna on my bmw E46 coupe and the Digital radio reception is great, i live some few km from the Dutch border (Putte-Kapellen) and can receive al the Dutch radio stations on my driveway, if the car don't move, i know that sounds stupid, bud the Dutch DAB+ broadcast signal is very weak, even 3 km in the Netherlands)
It ain't cheap but Calearo build quality antennas in Italy with 2 years warranty. I don't trust those Chinese electronics if you have to drill a hole in the roof.
For cars from the VW group they have FM/DAB+ amplifiers that you can switch with the original FM amplifier.
https://www.calearo.com/en/
Last edited:
I installed the latest version V170519 on my xtrons td101as with px5 board installed. It works fine but I can only switch between radio stations with steering wheel buttons when DAB+ app is in front. When starting MapFactor too or any other app and DAB+ is in background the steering wheel buttons doesn't work. Thats a bit annoying because during driving with navigation app in front it often can be that the selected radio station becomes weak and I want to change to next station in list. Maybe there's something special with my xtrons because it doesn't have any hardware keys - but in every other program I tested (music player, fm radio, dvd) in background the track up/down buttons are working.
The old (originally) DAB+ app on the px3 board (which I missed to save) did recognize the steering wheel buttons?! Any idea?
Thx
Detlev
The old (originally) DAB+ app on the px3 board (which I missed to save) did recognize the steering wheel buttons?! Any idea?
Thx
Detlev
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone