yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] NogenLunde:
By channels I mean radio stations, and in the latest release I experience instant switch (audio fade in (nice), otherwise instant) between stations nearby in the station list, when in OMRI mode. I thought that was a new cache feature? Edit: I realize know that this feature works only between station from the same broadcaster or channel.

Two of these are from my country (NRK ...), both from the biggest broadcaster, and the one with most reports (NRK1) is a nation wide station. However, reports on this is only from one city. I guess an Internet connection is required for reports to be sent, I'm usually not connected while driving, but could connect on my next long trip if that might help.

How can we know if using DAB+ or only DAB?

Edit:

Found how to reproduce the no-sound-at-all-bug:

1. Go to Car info (OEM screen).

2. Go back to Android and launch DAB-Z. There is no sound at all, in no stations.

3. Go to main menu and launch the built-in music app. DAB-Z starts playing sound.

This is probably an Android specific bug, maybe even to this model of the unit. The other "no sound" issue, where DAB-Z loses sound in just some stations, is not related to this, I think. I also encountered this other bug today when playing around: I moved up and down the station list, choosing one after another from the same broadcaster (same channel?), got no sound from any of them. Got sound when a station from a different broadcaster was selected. After that the other stations worked also.
[Android Head-Units] Flemischguy:
I know it's a bit off topic, but have a strange thing going on with my DAB+ reception. I have a 9 inch PX5, 4gb mem and 32 gb storage, radio with android 8.0. If i switch on or off my headlights. If i turn on the headlights, the screen reduces the brightness and i getting a better reception, if i turn of the lights, the screen increases the brightness and the DAB+ signal drops significant. I made a short video of this strange behavior, am i the only one or does others has this issue as well, and if so, what can be done to keep a steady reception with headlights on or off. https://video-bru2-1.xx.fbcdn.net/v...=4616b71f9594cb12f5e7ac32ce7839e5&oe=5E1FC72F
[Android Head-Units] NogenLunde:
LED bulbs are known to be a cause for interference with certain networks. Do you perhaps use LED lights as Daytime Running Lights (DRL)? Just google "led dab reception".
[Android Head-Units] Flemischguy:
I have a BMW 2004 E46 coupe facelift model, and that model has LED tail lights, that's all, my DAB+ antenna is located on the roof (shark fin), to reduce interfering, i put Braided sleeving EMC shielding over the coax cable of the DAB+ and GPS antenna, because it passes my fuse box underneath the dashboard. Could it be the screen it self that interfear with the DAB+ signal?
[Android Head-Units] realzoulou:
I also have now [MENTION=3076686]gustden[/MENTION] 's no-kill mod on my JY-VL130N2 and I can reproduce the issue. Root cause is that the DAB app looses connection to the USB device, but does not react on it.

I have a potential fix for this and I am testing it now for a while. This may even help [MENTION=8363773]dennydenny[/MENTION], but I am not 100% sure.
[Android Head-Units] realzoulou:
I double check my changes regarding Steering Wheel support again and found no unintentional changes.

I suspect that also the original version YHX-DAB+V170519.apk does wrong on your unit. Could you maybe confirm this?

There are users with PX5 devices (don't know the exact model, though) where I know for sure that steering wheel controls are working fine for them with my current 170726 release.

So it is for sure not a bug, but maybe an "incompatibility". Yes, I know this does not help you much...
[Android Head-Units] dennydenny:
it is started by MCU or something OEM specific...

the HU always starts the last two opened apps autonomous.
[Android Head-Units] desko:
I have got message from bitspice.net

"The app must support Android's standard media controls to be supported by AutoMate. If it doesn't work within AutoMate, there's a good chance the app is using a non-standard media playback method. "
[Android Head-Units] rigattoni:
That´s what I wrote mate... ;)

Seems that we need the help from realzoulou to get it working... if the app is able to be redesigned to regular Google standards. But if it´s not possible, I think we can live with it... more or less ;)
[Android Head-Units] Tumke32:
can we add logos ourselfs and link them to a stationname?
[Android Head-Units] realzoulou:
I tried to find out the format of the dab.bin file, but failed. It does not simply contain the png file next to the identifier.

Also I have no clue how the identifier (example 1D7E337E60C094EB9044235D83472A79) is built by the Witson app.

So, answer to your question: I guess: No.
[Android Head-Units] SpeedFerret:
Thanks realzoulou. Its going to be around 10 days until I can confirm as we are away on our Summer Holiday from tomorrow am early (Yeah !!).

My HU is an Xtrons PB76AA3AP.

I'll be in contact within the fortnight. Really appreciate your work. You have made DAB+ really useable and I rarely use the analogue service. :good: :good: :good:
[Android Head-Units] syk02jcb@hotmail.com:
Is it only with the swc it happens? Or if you turn the right knob on the HU as well (the "tun" / "ent")?
[Android Head-Units] chammock:
Thanks for your reply. Regarding point 2 my launcher basically uses the script on this page http://www.lightninglauncher.com/wiki/doku.php?id=script_music_metadata. But I think the apps like spotify send data to the BroadcastReceiver and the script simply identifies the update and simply reads the content into different variables. I am sure I could modify the script of the radio app would send the data. This maybe a very specific feature not to waste the time but it seems to me to be a very consistent way of reading data from apps without the need for specific integration for each app.

Can't wait for your "Master Piece" release.
[Android Head-Units] realzoulou:
[MENTION=7771599]chammock[/MENTION]

ok, got you.

You would like that the DAB app sends out an Intent with action "com.android.music.metachanged" and putExtra following info:

"id" - Integer: the database row ID => could be mapped to the DAB station no.

"artist" - String: the name of the artist => no idea what to map to ?!?

"album" - String: the name of the album => no idea what to map to ?!?

"track" - String: the name of the track => DAB station name

Ok with this approach ?
[Android Head-Units] nyogtha:
Sounds to me like this would also make it easier to create a widget for controlling the app! :)
[Android Head-Units] Spawn32:
Station Following

Hi realzoulou,

Is there any possibility that you can implement Station Following ?

Or is that buried deep in the app so you would need the source code ?

/Spawn
[Android Head-Units] chammock:
[MENTION=7838245]realzoulou[/MENTION]

That sounds about correct. I am not sure what the station ID is, and the station name would be a must, I have noticed some stations also broadcast additional information which in the app displays under the station name that is playing. Maybe this could be mapped to either one of the spare variables like artist? It is of no use to me as I cant see station logos but I believe the example I sent has an image variable usually used for album art, maybe this could be used for station logos, or maybe that's a Phase 2 request.

Let me know if I can assist in anyway.
[Android Head-Units] Jedimindtriks:
this is coming soon.
[Android Head-Units] doraimontv:
Congratulations on the application!

I have a question:

Is it valid for the JY-VM131N2 radio?

Thank you!
[Android Head-Units] realzoulou:
Sure. The only requirements are:

* Android at least 4.1.x (JellyBean)

* a compatible USB DAB Stick
[Android Head-Units] doraimontv:
USB?
[Android Head-Units] realzoulou:
Yes, a USB connection would be required in order to plug the USB DAB stick to the unit.

USB 2.0, which should be anyway the standard nowadays.
[Android Head-Units] doraimontv:
Perfect.

What are the compatible stick?

Thank you!
[Android Head-Units] NogenLunde:
Could you take these LED bulbs out and try again, just to eliminate them as cause for interference.
[Android Head-Units] typos1:
You could try shielding the rear lights with some metal mesh wrapped in carpet ?
[Android Head-Units] AnthonyUK:
The most recent update crashes my launcher (AGAMA) approx. every minute.

Any easy fix?
[Android Head-Units] AnthonyUK:
I found a solution online which is to disable OMRI mode.
[Android Head-Units] matteo2:
Does it work on eonon ga5153? Which receiver do you advise me?

Inviato dal mio SM-G950F utilizzando Tapatalk

View attachment 4929043
[Android Head-Units] typos1:
"ga5153" is a made up number by Eonon who are not a manufacturer and re-badge other company's products, please quote your MCU and processor type in order to identify what unit you have.
[Android Head-Units] matteo2:
I attached a photo. However my eonon have MTCB-KLD-V2.55 and Android 5.0.2_OT49H en.

Some DAB receiver ask for Android 5.1+

Inviato dal mio SM-G950F utilizzando Tapatalk
[Android Head-Units] realzoulou:
DAB-Z works from Android 4.4 on
[Android Head-Units] realzoulou:
They are all pretty much the same, if not equal. See Post #1 for a small list of known working adapters.
[Android Head-Units] realzoulou:
DAB-Z release 1.7.75

Google Play release 1.7.75 is available

Change log:

New

* Settings->Layout: Choose RadioDNS logo size in station list: default=128x128; or 32x32, 112x32

* Settings->Layout: Choose RadioDNS logo size when used as slide show picture: default=320x240; or 600x600

* Settings->Station logos: Choose Search order for logos: default = "imported => RadioDNS => built-in"; or "RadioDNS => imported => built-in"

* Timeshift: Long press on -10 or +10 button repeats the seek command with a 2 sec delay so that audio is briefly audible in between

* Settings->Station logos->Logo import: Added a 5th hint to the text, which explains how filenames should look like

* When OMRI enabled: If no audio comes after 5 seconds, a Toast is shown "No audio! Try with OMRI disabled"

This is also the moment where the NoAudio event is sent to Firebase Analytics via Internet

Bugfixes

* Favorite station list sorting and deletion of stations shows wrong behavior

* With "Hide station list automatically" enabled, station list fades out although user is still using the station list

* Settings->Audio->Sound volume is ignored

* When opening Settings->Layout->Image brightness, the initial brightness of the picture is always 100% although the slider shows e.g. 50%

* When using a BMW iDrive (or keyboard) to control station list, the focused item is not visible. Now it is blue (not configurable!), see picture below

* During a station scan in OMRI mode, the loupe icon is not shown

Known issues

* OMRI: Random crashes, often after selecting a new station

* OMRI: Sometimes no audio, especially with stations using old DAB standard (MPEG), but also randomly with DAB+ (AAC) stations

* OMRI: May crash after performing a station scan, which found certain stations, e.g. BBC R5LiveSportX

FYI: This happens during the RadioDNS logo download running in the background if connected to Internet

* OMRI: Some stations stutter and show a different bitrate than in non-OMRI mode. Seems that mainly Intel Sofia devices are impacted.

* OMRI: After station scan, stations may be missing, which appear properly in non-OMRI mode.

* OMRI: RadioDNS logo download no (or not enough) logos, although country should be covered.

* Non-OMRI: Randomly crashes while parsing data from DAB USB adapter

* All modes: After having moved favorite stations, at next start the wrong station is played.

Reported by users:

* Settings>Station logos>RadioDNS: Screen is locked while logos are counted in background
[Android Head-Units] VBA_Dev:
Many thanks [MENTION=7838245]realzoulou[/MENTION]

If it helps, when I have the no audio bug on AAC, most of the time flicking to an MPEG station and letting it play for a second and then flicking back allows the station to start playing. Maybe just coincidence, but I think it maybe because it’s unloading the aac player and starting an MPEG one. Then selecting the aac station is loading the aac player again from scratch. Maybe the aac player crashes when left overnight or doesn’t unload properly.. just guesses
[Android Head-Units] XDAGnom:
Good morning, I'm not really a technology freak. Maybe you can help me?! Would like to get a DAB + stick for my Samsung Galaxy Note 10 Plus. Unfortunately I don't find a suitable one. Greetings and thanks
[Android Head-Units] realzoulou:
See my post #1 at the end.
[Android Head-Units] NogenLunde:
Is this also a timeout? Because in this version I have four ACC stations which consistently fail with "No audio! ..." message, two of them in your list for Norway. They work in non-OMRI mode. I think they fail due to too short timeout. Increase to 6-7 seconds for testing?

This looks very, very nice, near pefect! Ideally I would have the option to change color (to blend better with our units), but this is no big deal if much work.

Have you considered letting only the station list be selectable? Now also elements like buttons and the big station picture are selectable (even the placeholder or frame for the station list), so if you scroll too far, you end up there. Some may like to have some of these other elements selectable by tabbing navigation, but if the choice is between only station list or all like now, I think most will prefer only the station list.

Settings says 0 RadioDNS logos downloaded, and I don't have any manually imported either. But still most of the stations have logos in the station list. Have I misunderstood? I thought these small logos are RadioDNS logos. They seem to have been transmitted over DAB, not Internet.
[Android Head-Units] XDAGnom:
Unfortunately I couldn't do anything with that. Do you / you have a few links of suitable sticks ?!
[Android Head-Units] NogenLunde:
I'm using this, works perfect: https://www.aliexpress.com/item/4000028228001.html
[Android Head-Units] Duvel999:
@ realzoulou

I bought you a beer:highfive:
[Android Head-Units] realzoulou:
No, this is not a timeout in the sense that DAB-Z gave up providing audio. You did not say if you had audio on the AAC (sic!) station and so the Toast was a false positive, or if the Toast was correctly informing the user. Can you please comment?

Yes, I did changes there because I found out during testing with a USB keyboard that there the order of focussable items was totally confusing. So I corrected it to my best. But you seem to see more with the iDrive than I see with the keyboard. If sth. is screwed up then let me know. But I would need a video then.

There are about 400 logos built-in in my app. This explains why you see logos. And this is why the app is so huge (~12 MB). The logos consume ~5 MB.

Thanks [MENTION=3126160]Duvel999[/MENTION]. I received it, but it is too early to have a bear (Sunday 2pm) :highfive: so I had a coffee ... haha
[Android Head-Units] okij:
Thanks a lot for considering and implementing my feature suggestion! :highfive:

I tried it today and IMHO it should be improved in one aspect: While it's OK that the first delay before the seeking begins is at 2 seconds, the succeding seek commands should follow much quicker, e.g. after 0.2 or 0.5 seconds. The best would be if this value was configurable.
[Android Head-Units] NogenLunde:
There is no sound (ever) when in OMRI mode on these stations, so no false positives, user is correctly informed. They work in non-OMRI mode only, I never get sound from them in OMRI mode.

However, this may be a different bug than the sporadic "no sound" issue. I encountered this again today (AAC stations), and there was no message from your Toast, I waited 10-15 seconds. Sound comes back when moving to a different broadcaster and back (all stations from the same channel are silent), it doesn't matter if this other station is AAC or MP2.
[Android Head-Units] IG_Vasilich:
I managed TV/Radio channel logo repository for MediaPortal several years, recreated many logos by myself (in vector format(SVG)), did many tests with PNG optimization, etc.

So in case you are interested, we can try to optimize the logos, that are built in, to save some space ?
[Android Head-Units] Duvel999:
Does this app support RDS support?
[Android Head-Units] DrRobin:
I have an Xtrons Android 8 and USB DAB (02) dongle, this works great with DAB-Z.

So I bought a Xtrons Android 9 and USB DAB (02) dongle, but this doesn't work as well. I have tried several different antennas on the Android 9, but in the signal drops low all of the time. I would say that the received signal is about 3 bars weaker on the Android 9 than the 8. If I swap the DAB modules over there isn't much difference.

Is there a driver issue on Android 9 and DAB-Z?

I have been asking Xtrons support, but they don't seem to be able to help.
[Android Head-Units] VBA_Dev:
[MENTION=7838245]realzoulou[/MENTION] - possible glitch on setting screen. Radio DNS logos are showing as >700 for me, but I think this count is causing lag on the other settings screens - possibly recounting on every setting page change/load?
[Android Head-Units] DrRobin:
Can anyone recommend a really good USB DAB dongle to work with DAB-Z and Android 9?
[Android Head-Units] NogenLunde:
You can see link to my USB dongle on the previous page, I'm using it with DAB-Z on Android 9 SnapDragon 625, no issues, full signal most of the time, but I have the original BMW antenna.
[Android Head-Units] Duvel999:
It look similar to the Xtrons:cyclops: but it's better?
[Android Head-Units] typos1:
Theyre pretty much all the same inside.
[Android Head-Units] Duvel999:
My reception is worse.

Any tips / instructions for installing it in the car?

- best place for reception

- how to place

- how to adjust

- other tips

- other Dab+ antenna's

Is Dab+ in every Country good supported?

Let's make a grafic sheet or something for best results in several Countries.

Dab+ looks for me like a extra selling point, but I hear many complaints.

Simply it doesn't veork or no reception.

From New Cars with Dab+ build in also, So not only aftermarket....

This App is the best there is.
[Android Head-Units] leenq:
- This website has a full database of all radio transmitters, you filter by DAB and by location: https://fmscan.org/index.php?la=en

It can also show the reception area of each ensemble on a map.

- Coverage really depends on the country. In France for example there are still only a handful of DAB transmitters. In Belgium and Netherlands where I often drive the whole countries are well covered with many DAB transmitters all over.

- I found that the location of the DAB USB receiver box (not the antenna itself) can make a big difference. First I had it right behind the headunit and it would drop signal all the time, to the point of being useless. I started investigating and experimenting to find a solution.

When I placed it further away from the HU, basically I dropped it in the open space in the dash on the passenger side, things got quite a bit better, but still drop outs in some areas. I guess there can be interference from the cables/BT/Wifi, as inside the Chinese USB DAB receivers there is no RF shielding at all.

- Then I finally installed a Calearo shark fin antenna replacing the original FM antenna and I did away with the windshield DAB antenna, and since then I get full strength signal on all ensembles in my area even when driving between buildings. I am 25-50km straight line away from the various DAB transmitters in Paris. It was a €120 investment, but in addition to the DAB it also improved FM and GPS reception greatly.

I hope this helps some.

---------- Post added at 08:48 PM ---------- Previous post was at 08:23 PM ----------

I doubt the difference is between Android 8 and 9. At least on my Xtrons TE-706PL there was no difference in DAB reception when I upgrade from Android 8 mod 3 to Android 9 mod 4.

See my other post above about the placement of the DAB-USB receiver, it seems sensitive to interference (I suspect RF blocking due to other signals).
[Android Head-Units] realzoulou:
I have 2 devices on my desk for testing: Joying Sofia and a PX5. Under the exact same conditions, the Joying device provides always a much better signal strength and receives more channels than the PX5 device. I have no theory why this is the case, but it is a fact that apparently also the head unit itself makes a difference.

The term RDS is not correct for DAB. Anyway... there is no support for traffic information data services in my app and there never will be. Only audio services.

Wow, >700 logos !!! :cool: Yes, logos are counted each time when you enter the station logos settings screen. But this is done in a background thread and should not impact the usability of the UI. I would be interested in seeing a video...
[Android Head-Units] okij:
Thanks for your post, it was interesting to read. :)

About the missing RF shielding: Maybe It would be an idea to wrap some aluminum foil around the USB DAB receiver. Has anybody with bad DAB reception tried this?
[Android Head-Units] realzoulou:
Several tried this and - if I remember right - no one reported that is was of any use
[Android Head-Units] okij:
Gladly my USB adapter works well, so I don't have to try shielding. :)

But maybe shielding could work if it gets connected to electrical ground, e.g. to the outer ring of the antenna coax connector!? Hm, I guess that this has already been tried too...
[Android Head-Units] DrRobin:
I did wonder if it was noise. The screening can is missing round the circuit and if I hold the dongle in my hand then the signal strength does increase.

Perhaps if the dongle was moved further away from the head unit (long usb cable) and screened and earthed it might help?

I have an SDR which covers the frequency,perhaps I will check noise? It might be usb noise either at 225MHz or whatever I/F frequency the dongle uses. That might be harder to fix.

---------- Post added at 02:36 AM ---------- Previous post was at 01:41 AM ----------

Just googled dab and usb noise, seems a lot of people have had problems with dab after fitting a dash cam. It appears to be the 12v to usb PSU which is the problem.

Both of mine have the same dash cam so will try unplugging it on the Android 9 just in case.

If a dash cam can cause problems then perhaps so can a noisy head unit. I will run a spectrum scan tomorrow, gonna for noise at 225MHz.
[Android Head-Units] NogenLunde:
Remember that the window antenna *must* be grounded for good reception.
[Android Head-Units] DrRobin:
Okay, this morning I disconnected my dash cam, no difference, I also un-plugged the OBD adapter (it's Bluetooth), no difference. Even with the engine off the poor performance is still there.

Outside work the DAB signal went almost completely, I pushed the antenna coax close to the metal (of the head unit and dash board) and clasped my hand tightly round the dongle, making sure to touch the USB outer and the antenna, my signalwent up to 3 bars and just once 4 bars. My Android 8 gets 5 bars at work, may be 4 on a bad day.

Since everything was switched off apart from the head unit, it looks like the noise is coming out of the head unit, possibly along the USB.

Clearly it is some kind of noise or ground loop, possibly common mode noise in the outer of the coax. My hand and body will increase the capacitance and might give a bit of shielding. I will put the spectrum analyser on later, but suspect good shielding and common mode chokes might sort it out.