yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Terje_N:
What do you mean?
[Android Head-Units] typos1:
You didnt keep a copy of the apk ?
[Android Head-Units] ynorynor:
Zoulou's modded app is based on a different version (probably newer) of the app that does not stutter (V1.1, the old one from Joying). The difference between the base for the modded app and the old V1.1 are at least different .lib files. The base for the modded app does not play well with Allwinner units, but the old V1.1 does work kind of without stuttering except when running in background with heavy load from other apps. Hence, since the base for the modded app stutters with Allwinner units, the modded app also stutters.

If it is possible to do simular mods with the old app as base, problems could be reduced. I have replaced the hideous background of the old V1.1 app though, but would like to have many of the functions that the modded app have. However, I don't have the knowledge to do the other mods.
[Android Head-Units] Terje_N:
Which of them?

I do not have a copy of the one on the unit from the factory, and the update I received for it, but I've saved all the versions I've got now afterwards.

The problem is that those versions that do not have choppy sound, they do not support the buttons on the steering wheel, and it is not possible to create a favorite list in them..
[Android Head-Units] ynorynor:
Try the one from Seicane. This is the oldest version I have found (V1.0), but it does not stutter. Do not know if steering wheel buttons works. Here is the link:

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

Let me know how it works for your player.
[Android Head-Units] typos1:
My thinking was that the one with the favourites along the bottom would be useful as [MENTION=7838245]realzoulou[/MENTION] could use the nicer interface on his app.
[Android Head-Units] Terje_N:
I bought my unit in november 2017.

It is built to be integrated in my dash, not as a regular 2din player.

It was only avilable with Android 5 and 6 that time.

I asked the dealer if the Octa/7.1 comes soon for my car, but he didnt give any ansvere.

It was made for Toyota Avensis with octa/7.1 that time but not yet for my Toyota Verso.

The sales add on Aliexpress say it work well with DAB+, so I trusted it and bought....

The octa/7,1 came out for my car now in january... Uggghhhhh....

Is it possible to change the CPU without to mush problem, or can I just forget it?

---------- Post added at 09:35 PM ---------- Previous post was at 09:27 PM ----------

Ahaaa...

That face I got by the update from the dealer.

I didnt download the update file.

I just went to the file server site I got link to,from the dealer, by the headunit itselfe....by WiFi...

And installed directly to the unit.

If I had known then... what I know today, I should saved it.

I have asked the dealer ones again to give me the update, but he is a crock and dosent do anything to help me out.

I started to argue with him about this problem already in november december last year, and january 18 he stop responding.
[Android Head-Units] typos1:
Ok, shame, although theres nothing stopping me from using apkeditor to mod the xml files myself . . .
[Android Head-Units] Terje_N:
That is the same version I already have, and it dosent stutter, but dont support steering wheel.

I hope the crock gives me the "facelift update" ones again so I can see if it works with this non stuttering version.
[Android Head-Units] ynorynor:
You can find the facelift updated version in the comments in this Youtube video:

https://www.youtube.com/watch?v=3yK...1sacebdtr3kmst0phg1pw03c010c.1509762382165152
[Android Head-Units] binar1:
Isn't this version the witson dab+ app it has been discussed before. If I remember rightly somebody tested and found it calls home to some chinese server. Anyway the latest version is

CZY-DAB+H2.05-20171213.apk

Available here.

https://m.sendspace.com/file/q8oaca
[Android Head-Units] Terje_N:
Now I tryed the "facelift" togheter with the non stuttering version, but it falure....

Then I tryed it together with the newer stuttering version, and that works...

I get the facelift, but stuttering.

Fu........

---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------

Downoaded it now.

Must test it out...
[Android Head-Units] SkyBeam2048:
I have also upgraded to the very latest version of this app by [MENTION=2583521]realzo[/MENTION]ulu. It just works perfectly on my MTCE PX5 init whereas the original app used to stutter in backgrount. I also really love the interface changes. It really improved usability a lot and minimizes distraction while driving.

To me it looks like mainly Allwinner based units still suffer from stuttering. Not sure if there is much which canbe done about it. It might require updated audio codecs optimized for Allwinner CPUs.

I also noticed that the latest realzulu app by default enables the audio distortion filter which increases CPU loaf by analyzing the audionstream and applying filters to it. Perhaps Allwinner owners might try disabling this feature.

[MENTION=2103535]realz[/MENTION]ulu: I am not fully sure if the option in setting to disable audio distortion really works. I disabled it and still never had such sqeaking noises on signal dropout. But this is still to be confirmed as I didnt use the app very often since. However I think the option could potentially be removed if the implementation is improved. It might be possible to just enable the audio filtering when signal levels drop below certain tresholds or even better if audio buffers run empty. This would allow to filter only when the audio buffer runs out and the audio stream is defective/interruped which is the cause of these squeaking noises I believe. So filtering would only be applied when there is a risk of a broken stream.

On units which cannot handle the adfitional load this might lead to stutter (but no squeaking noises) but stuttering might occur also due to signal dropout.
[Android Head-Units] Terje_N:
Done some testing of several versions today...

https://www.youtube.com/watch?v=MbO-p34s6RA&t
[Android Head-Units] realzoulou:
Can you please share a download link to this version DabPlayer-pad-1.4-20171018.apk ?
[Android Head-Units] realzoulou:
IMHO, audio dropouts have nothing to do with the audio distortion filtering.

Why are there audio dropouts?

a) The Android system does not give enough CPU resources to the app. I was hoping to have fixed this, but seems on some (Allwinner?) CPUs this is still not working fully.

b) The USB hardware/software cannot process the data from the USB DAB adapter quickly enough up to the DAB App. This might be due to a stupid hardware implementation with too many internal hubs within the hardware, a messed up Linux kernel USB subsystem, or whatever.

c) the USB DAB adapter is not the root cause (typically)

Why is there high pitch audio noise?

From my experience this is caused by the DAB adapter or by the decoding library within the DAB App (which I cannot debug), typically when the signal quality becomes very low.

The decoded PCM audio samples (DAB encodes them either in AAC or MP2) are already damaged when they appear in the Java source code of the DAB App. The audio distortion filter that I implemented, identifies decoded PCM audio samples that are "clipped" (or nearly clipped) (see Wikipedia for explanation of audio clipping ). If the algorithm finds clipped samples, it replaces those samples with "silence", i.e. value=0. The algorithm is multi-threaded and introduces a CPU load increase of ~5%. This should typically be no problem for any of the head units that are in use these days, so I decided to activate this algorithm by default, but with the option to disable it in Settings. Believe me, disabling this feature really works as expected. I spent weeks on that topic.

On my Joying Intel Sofia head unit with a Joying DAB adapter I virtually never have such high pitch audio noise. But I live in the greater area around Munich, Germany, where DAB coverage is really good.
[Android Head-Units] ynorynor:
Could you please share some info on how to address CPU resources to the app, and how to implement the clipped samples filter? I would like to try these mods on one of the earliest versions of the app that works with my Allwinner unit.
[Android Head-Units] realzoulou:
The trick is to run the DabService in foreground according to this documentation from Android: https://developer.android.com/guide/components/services.html#Foreground

If you expected a one line source code example, then you may be disappointed now. Sorry for that, but it is not as simple as you might expect.
[Android Head-Units] Oberbergler:
My new UI mod based on realzoulou`s February app is online: https://mega.nz/#F!r1AzWZyJ!qMshHpnPCIXCVhGXFIeZ-Q Positive and negative feedback is welcome :)
[Android Head-Units] Ibanez99:
I have tried every file you have made, but all of them stutter on my Bosion unit.. :(

The one who is stable on my unit is the original YHX-DAB+20170328.apk, but i have to keep on accepting usb every time i start the app..
[Android Head-Units] Terje_N:
Here is all of the versions I have got...

https://www.dropbox.com/s/gmuioyncb1mx5wn/Dab-Player-pad-201603310918.apk?dl=0

https://www.dropbox.com/s/r42ue15lp56ixdb/DAB+1V1-20160801Sofia.apk?dl=0

https://www.dropbox.com/s/iddz34am26l8nit/DabPlayer-pad-1.4-20170518.apk?dl=0

This is the one you ask for...

https://www.dropbox.com/s/ad8jat9zr1auvgg/DabPlayer-pad-1.4-20171018.apk?dl=0

https://www.dropbox.com/s/gmuioyncb1mx5wn/Dab-Player-pad-201603310918.apk?dl=0

https://www.dropbox.com/s/3bml5p9bnh1pnln/DabPlayer-pad-201606010919.apk?dl=0

https://www.dropbox.com/s/54lhfnjsw6kxapl/YHX-DAB+H2.03.apk?dl=0

This two last one is RealZoulou's versions....

https://www.dropbox.com/s/hmkqmak2ysdrs0w/Dab+_by_Oberbergler_nousb.apk?dl=0

https://www.dropbox.com/s/bzerva5lb4bnbw9/ZOU-DAB+180210.apk?dl=0
[Android Head-Units] Danno1975:
Hello trying to get a decent dab reception

Was thinking this This for tv and dab?, https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.co.uk/ulk/itm/152895987779

or as just use as a cheap external aerial to google with this https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.co.uk/ulk/itm/273047725477 (discarding the windscreen element)

If this might work could I theoretically get away with mounting it inside in the dash where my GPs aerial works well? It’s under the dash cubby in my Vito.

Or this better aerial https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.co.uk/ulk/itm/400872415168

with just the module on the previous notes glass mount?.

Currently I have a windshield stick on and the reception is horrific and unreliable. But sadly it’s all in one so I can’t simple unscrew the aerial and up grade.

I guess I could simply cut and Connect the external aerial? Or is there some tech in the black box on the screen mount I need?. Thx
[Android Head-Units] Terje_N:
Tested them now...

Bouth is stuttering on my Allwinner...

Sad...

By the way...

What is the diferences from yours to realzoulou`s versions?

Since they are stuttering, I havent used any time to go in depth of them...

Should it be possible to make your versions based on the old app that dosent stutter on my Allwinner?

It should been interesting to see...

I have several versions of those with the old face.

The oldest ones dosent support my steering wheel buttons, and those also dont stutter on my Allwinner...

Those newer versions wish support my steering wheel buttons does stutter on my Allwinner...
[Android Head-Units] Oberbergler:
There is no difference beside the design.
[Android Head-Units] SkyBeam2048:
I agree, but reading your response I believe you misunderstood my comment or I have not been clear enough.

So applying audio distortion filter on those devices might cause even more dropouts since the distortion filter takes even more CPU resources. So on allwinner devices the audio distorition filter might cause more dropouts.

And THIS is exactly the use case I was referring to.

Those high-pitch noises are caused by defective data packets entering the decoding chain. It only happens if the signal is low or too noisy so the data packets received are damaged.

This is why I believe coupling the filter with the signal level would be ideal. So when the signal level is high there is almost no risk of receiving defective data packets in the decoding chain. Therefore the filter is not needed. Only when the signal level drops below certain threshold there is a risk of receiving broken audio stream frames which might decode to high-pitch sound. So when the signal level drops below this threshold the filter might be applied in order to assure the high-pitch sounds resulting from broken packets are replaced by silence causing a clean silencing-out rather than annoying high-volume squeaking noise.

The signal level indicator is available to the app I believe (else no signal strength bars or levels in detailed information might be possible to show).

Automatically enabling/disabling the filter would allow to run the device without additional CPU load in most conditions and just apply the filter when needed. Lowering the overall CPU load.

And yes, when signal becomes low and the filter is enabled some weak devices might respond with stuttering due to CPU load, but this might be acceptable given the fact that the filtering and stuttering would only be increased if the signal level is low anyway and the audio stream might stutter anyway due to low signal.

I personally disabled the filter due to the fact my device actually never creates these high-pitch noises as the reception is usually good and I don't want to waste CPU cycles "just in case" as there is no need to continuously filter the audio on perfect reception. Also some PX5 devices seem to be affected by heat problems and more CPU load means more heat. But generally it's more my personal development attitude not to waste any resources and for me applying a filter in conditions where the filter is not needed is a waste of resources.

Moreover I usually try to hide unnecessary options from the user and the distortion filter switch could be removed if he filter is normally not applied and only enabled in cases where audio dropout/defective packets are expected.

Granted I didn't have a look at the code and it might be impossible to dynamically enable the filter based on signal level - or enabling/disabling on the fly might also cause some interruption.
[Android Head-Units] Terje_N:
Are you able/interested to make your version based on one of the oldest non stuttering app versions to see if it sty without stuttering?
[Android Head-Units] Oberbergler:
There is no other app that is working for me without stuttering except realzoulou`s DAB+ app. For me it does not make sense to do it since I am no programmer and no designer and I need very long to understand how I can mod some design related codes. I am modifying realzoulou`s app for personal use to adapt it more to my head units UI and I am sharing the result with people here on xda. If you want to mod another DAB+ app I can help you with the needed programs on your computer, the rest you have to do by your own. Maybe an older version of realzoulou`s apps is working on your unit. These are my mods on the last 3 releases: https://mega.nz/#F!ChgRnJYS!wv1hkUy6G04iCvETx3cLXA
[Android Head-Units] Terje_N:
What is the diferences between standard and nousb...?

I'm a newbee...

Non of the newer versions works without stuttering on my Allwinner...

I have to go all the way back to early 2016 versions.

Wonder what is diferences on the newer ones that make them stuttering.

I bought my head unit in november 2017, and now I have desided to sell that car, so I'm in a little hurry to find out if I just have to stay with the basic old version, or if there is some posibilitys to get it some upgraded so it get the favorite list option.
[Android Head-Units] Oberbergler:
"No USB" is an error after rebooting. Since there are many different Android head units there are two versions because some units need the "No USB" version to start the app correctly after rebooting the HU. Did you already try the Witson version? https://www.sendspace.com/file/q8oaca
[Android Head-Units] Terje_N:
Yes...

Have tested it.

Stuttering as well...
[Android Head-Units] mcwieger:
Don't know if this issue is specific to this app, but I'm receiving 12c channels only (Netherlands). I have full signal strength, using a Chinese USB dongle + Joying radio. Any tips or settings how to receive the other stations?
[Android Head-Units] hans.vinkers:
It's not the app but your antenna. Lately they have improved the power of the radio stations but still not optimal on a window antenna
[Android Head-Units] japioothuis:
Hi,

Strange. I recieve all 12, 11, 8 channels, public and commercial, here in Noord Holland, full 5 signal bars, christal clear sound without stuttering.

I noticed that after a channel search it also finds channels like Omroep Gelderland but they don't play ( no signal bars ) . I think that's normal ?

I suppose when I drive to Gelderland it will play these stations.

No idea why it finds these stations during a search.

Do you use a Joying DAB+ USB unit ? Or another brand ?

Window antenna or a roof antenna ?

---------- Post added at 04:47 PM ---------- Previous post was at 04:44 PM ----------

[/COLOR]

Thrue Hans, but he would not have full 5 bars signal strenghts I suppose ?
[Android Head-Units] mcwieger:
Since these Chinese dongles are supposedly "all the same", I bought a cheap one (not the Joying). (not allowed to post links yet...). With a window antenna.

What do the bars mean: reception of a particular station or a signal in general (if that even exists, I'm new to the topic). If it's the first, it would probably mean that not all channels are broadcasted equally strong (assumption).

On a side note: since I installed the dongle, all of a sudden my FM radio receives many more channels than before, just when I was about to phase out that app because it was useless without any reception :D
[Android Head-Units] hans.vinkers:
With the window antenna you get what they call 'flutter' that means the signal strength is ok but falls out very short amount of time (milliseconds) . That is just enough to have poor reception or even no reception at all. Where are you from in the Netherlands ? There are websites to find out where the support signals come from. That way you can find out when the reception should be good. And I have read somewhere that led lights distort dab signal.

There can be so many reasons why the reception is not good.

Ps.i live in Twente and see channels on 11c 12c 6b and 6c (I could check it to be sure, the 11 12 and 6 band are used surely). When I get closer to Germany I see 5 band as well
[Android Head-Units] japioothuis:
Well, I posted this before but cannot find it anymore.

I have a Joying DAB+ adapter ( is yours a really DAB+ ? ) and the antenna that came with it is useless.

So I bought a cheap FM / Dab+ antenna splitter but that also did not work with my Fiat roof antenna, I think because it's a combi tel, gps radio antenna.

I found a very cheap one at the Action ( Dunlop, Euro 1. 29 , comes with M6 & M5 ), unscrewed the Fiat antenna and replaced it with that one, guess what ?

Perfect now.

I have no idea if there is a difference between the Joying adapter and other brands. Don't think so if the hardware inside is the same.

About the FM radio ??? That's strange, but no problem I suppose ?
[Android Head-Units] realzoulou:
FYI ... file DabPlayer-pad-1.4-20171018.apk is

binary identica

l to YHX-DAB+V170519.apk (which is the basis of my mod)

So, despite the new date in the filename it is still an old version.
[Android Head-Units] mcwieger:
Middle of the country, so signal should be good.

Description says so...

Do you have a link?

No problem, let's call it a feature...

Would a self-built antenna using a coax cable fix this (as linked to somewhere else on this forum)?
[Android Head-Units] hans.vinkers:
You can pick up my coax antenna for testing... Didn't help me

I want to buy the superbat RF antenna but I can't find one with fakra and smb yet

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

Should be sma connector
[Android Head-Units] japioothuis:
Problem is where to place that self made antenna. I tried, looked good but during a drive signal is lost every time.

Have no link, no idea Action still sell it.

[IMG="antenna"]http://www.webresources.nl/joying/Dunlop.jpg[/IMG]
[Android Head-Units] mcwieger:
Thanks for the offer and your fast replies trying to help solving the issue.

I did a full scan on a different location and now many other stations showed up (11C). As I mainly listen to two stations that have proper reception and my I think I spent enough time making the Joying work, I'll leave it with this...
[Android Head-Units] japioothuis:
Yes, that's right. It still depends where the car is located. Sometimes a few 100 meters can make a big difference.

There are still black spots here in The Netherlands.
[Android Head-Units] typos1:
Would you be interested in changing using the UI with the favourites at the bottom if we can get hold of the app ?
[Android Head-Units] realzoulou:
Was this a question to me? If yes, then I do not understand your question.

I would only consider to move to a new "baseline" apk, if this new apk has any significant improvement compared to the current "baseline" apk, which is YHX-DAB+V170519
[Android Head-Units] mrnorx:
[MENTION=7838245]realzoulou[/MENTION] I have created buttons on my launcher to start the various music apps using tasker, do you know how I can start the DAB player in the background so it doesn't launch the UI. I assume this is possible as it happens when I switch the radio on in the morning.. if i use the main activity it launches the UI.

Many thanks
[Android Head-Units] realzoulou:
[MENTION=637803]mrnorx[/MENTION] In Settings->General there is an option to put the App immediately into background, if it was started by a USB device detection event. But there is no option to start the App in background when it was started from the Launcher, because then you would *never* see the app.
[Android Head-Units] mrnorx:
Ok thanks, I have a button to launch the app when I need to but I have another button to toggle between Spotify playing and dab playing without leaving my home screen but that's what I can't get to work.
[Android Head-Units] Zeze21:
I have tried several versions found here - original apks and modded ones.

To my findings there are basically 3 types of apks:

1. runs smoothly in the foreground but stutters horribly when running in the background.

2. stutters in the foreground and stutters in the background (but stutters over all less in the background than the 1. app)

3. apks which do not run/immediately close/do not get any signal/do not connect to the usb etc.

Shame though that I have not found a single apk which runs smoothly in both fore and background. :(
[Android Head-Units] pwood999:
I'm running this version with no stuttering either in foreground or background:

"2018-02-10:ZOU-DAB+180210 "Master Piece Maintenance Release 1" Link: Post#753"

The only time I get any DAB audio issues are when the signal drops due to antenna related problems. I used DIY Coax antenna in rear window, but really need to install an external antenna. I do suspect there are occasional RF Multi-path issues in the UK, but we have to live with this because it's a fact of life for RF systems !! At least DAB is better than FM for this.

My head unit is single din with 7" screen. I have installed extra heatsinks & fan, plus re-located the head unit under the passenger seat using a Joying 1 metre screen cable. The cooling definitely helps.

Fan install is here: https://xdaforums.com/showpost.php?p=75274018&postcount=154

Remember DAB Mpeg audio needs to be decoded in the main CPU, therefore any other running apps could impact audio.