yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] zyxraid55:
Hi People have installed the newest Version from play-store. The app work´s but after a warm-start-up there is no sound I start the app after manually and it work´s for a few minutes

Then the app crash and i must start the app new. I Have installed Malaysk Full 1.1.7 I hope anyone can help Is this a bug ?

The Version with 04 at the End works better without crash where i can download the older version please ?

Many thank´s People greets from Austria (sorry for my bad Englisch speak) ;-)
[Android Head-Units] NogenLunde:
@zyxraid55 Older versions of DAB-Z here:

https://apkpure.com/dab-z-player-for-dab-usb-adapters/com.zoulou.dab/versions
[Android Head-Units] okij:
I can't go to settings because there's no UI. DAB-Z doesn't fully crash, so I don't get into settings this way either. Also I rather don't want to start from scratch by wiping app data. Let's see what @realzoulou says. :)
[Android Head-Units] zyxraid55:
Many Thank´s for the Information :)
[Android Head-Units] okij:
@realzoulou: I now tried @NogenLunde advice and turned off "Swap logo and station list" (which was quite easy because I could revert to an older version via TitaniumBackup, then turned off that option before installing latest beta again).

It helps as a workaround (thanks @NogenLunde for the tip), but when turning on "Swap logo and station list" again, the no UI bug is back too. :(

I prefer the station list to be on the left side, because it's closer to the driver and safer this way. So I hope that you can soon find the cause of this bug and fix it. 🤞
[Android Head-Units] realzoulou:
Sorry, that I didn't find this bug with Swap logo and station list in my own testing. I will provide a fix as soon as possible.

EDIT: Release was uploaded to Google at 21:38 UTC+2
[Android Head-Units] okij:
@realzoulou Thanks a lot, that was really quick! :cool:(y)
[Android Head-Units] royalhawk2002:
Not appeared in the store yet... but I found another small bug... the station name color, if changed, is not saved.
[Android Head-Units] royalhawk2002:
Anyone already found this update in the store ? I am looking every day but it is not there.
[Android Head-Units] realzoulou:
DAB-Z release 1.9.109 BETA

Change log:

compared to 1.9.108

* Fixed black screen with activated "Logo and Station list swap" (introduced in 1.9.108)
[Android Head-Units] realzoulou:
Since the first Corona Lockdown in March 2020, Google Play Console shows to me:

Spoiler content hidden.

Before Corona it took ~2-5 hours for Google to complete their review of a newly uploaded apk.

Now it is nearly unpredictable for me. I experienced 6 hours, but also 5 days already. 1.9.109 took from May 3 21:38 to May 5 12:02 UTC+2. I cannot influence this delay.
[Android Head-Units] realzoulou:
The raw recording of HR1 (after HU comes up) contains audio and it plays fine in my test setup for raw recordings.

@#marcg# Do you also do some "special setting" as indicated by
[Android Head-Units] TorstenH:
Seems there is an additional init required in some special circumstances.
[Android Head-Units] royalhawk2002:
Thanks... this evening finally appeared... issue on station list swap solved Thanks!
[Android Head-Units] #marcg#:
No, i dont have set any special settings. IMHO Malaysk has some special settings, i will look at it. But im using the default settings... There must be a different between your versions... .96 works properly .105 not. (IMHO all after .96, i have tested some versions)

Im using my Headunit always in Standby-Mode. Reboot only once a month, Malaysk runs very stable on it. The current DAB-Z Version works always after reboot, but not after a standby.

I will look for special settings in malaysk....

Greets & thanks for your work

mgreen

[Edit]

hmm... im using this modded MCU Firmware too for the real EQ, should this be the problem ?

https://xdaforums.com/t/mod-mcu-bd375xx-sound-processor.3834657/

[/Edit]
[Android Head-Units] Zabzd:
Storage location of the DAB folder for recordings, logs and user imported logos changed

Previous location <internal memory>/DAB/...

From now on: <internal memory>/Android/data/com.zoulou.dab/files/DAB/...

Good day.

Moving the directory, see point 4, deletes everything after uninstallation DAB-Z, so there is no backup left.
[Android Head-Units] IG_Vasilich:
I expect it to do so. If the apps i have uninstalled would leave its data on my phone, then the phone memory would be full long time ago.

Moreover, there is google requirement to delete all data on uninstall.

So if you want to install it later and get all settings as before, then you should backup data you need.
[Android Head-Units] NogenLunde:
Well, I can't imagine anyone expecting all .docx files to be deleted when MS Word is uninstalled. Recordings and backup data are likewise user files. This is a serious bug reported by @Zabzd which I'm sure will be fixed before release.
[Android Head-Units] IG_Vasilich:
agree for recs, user logos and station list backups = user data.
[Android Head-Units] IG_Vasilich:
@realzoulou

checked SF function - seems to work (no real testing while driving yet - just manually triggered SF) (y) , but transmission of this information (coming from broadcaster) id sometimes weird. E.g. "Antenne Bayern" from Oberfranken has SF links to same station in "Antenne DE" ensemble, but not vise versa! Does the broadcaster expect that Antenne DE is available in any place of Germany (as "zweites Bundesmux") and therefore shouldn't be linked to anywhere else? Anyway - not the fault of DAB-Z.

Back to DAB-Z: Timeshift play point stays on live point when pausing station, playing live point: after resuming it ("play" intent from external app/hw button) it continues from live point. But if the station was playing timeshift NOT from live point (e.g. 10 seconds back), then it continues exactly from the same point, where it was paused (as expected) - you can see "time diff to live" indication increasing during pause in that case. Have you changed this behaviour in last versions? Tested with v1.9.109.
[Android Head-Units] realzoulou:
No, I have not changed anything here. I had tested what you said before would not work on 1.8.104 or .105, but found it working there also.
[Android Head-Units] IG_Vasilich:
So only i experience an issue with pause not moving timeshift from live point?

And you cannot reproduce it?
[Android Head-Units] realzoulou:
This is how it is expected from my side. I think your expectation is different.

Normal/Live:

Pause: Live audio is muted, nothing is recorded

Play: Live audio is un-muted

Timeshift was started with UI button:

Pause: Timeshifted audio playback stops, recording continues in background

Play: Timeshifted audio resumes where it stopped before
[Android Head-Units] IG_Vasilich:
OK, then it works as you expect it to. Fully agree with second part, but to start timeshift i have to go to UI and press "shift back" button.

Would you consider to make a possibility to set the timeshift point to the time when pause was pressed (even if timeshift points to live point)? Maybe optionally, as i have different expectation of how timeshift+pause should work in that case?
[Android Head-Units] Chrisu02:
Hello @realzoulou

I wanna report two small things i noticed :)

1st one is, that i noticed that with service-following then resuming a station when DAB-Z is paused is not possible anymore, as the when pressing the button the focus is going to the "SF" logo then, before it was possible to go to the "PLAY" logo and resume DAB-Z from there.

I made a little video to show this behaviour:

The second issue is already known to me since longer but still does appear, its just a small optical thing at the Thumbnail Icon when switching radiostations at background.

I also made a video to show that:

Note, the station list does end with:

HR-INFO

hr3

sunshine live

YOU FM

at the top then, the station list does start with BIG-FM, DLF, ect.

Now when changing Stations at the background, when switching down stations, at about second 7, it does show:

hr3

Sunshine live

BigFM

so it does not show the last station "YOU FM", but then switching down again, then "YOU FM" does appear will be selected.

Software Version at the moment is 109, also did a factory reset of the headunit recently and did a new manual station scan, so not imported old files.

This is already since longer , but i never felt to do a post only because that :D

sincerely Kri
[Android Head-Units] Pataan_CH:
Hi

I am using a Joying HU on Android 8. I have installed DAB+ app from Google Store, latest version available there.

As an antenna I have a default one clued at front window.

I am struggling with the reception, where cars with DAB+ installed from factory have constant reception, I do not get constant one. As it would be that not all frequencies are supported.

- Service following is on

- Signal coverage per se here in greater area Zurich / Switzerland is given

Many thanks for input

Pat
[Android Head-Units] IG_Vasilich:
Read last 2-3 pages of this thread - it was discussed several times already.

In short: forget about windscreen antenna, and install rod antenna with amplifier. One of possible types was described here.
[Android Head-Units] Pataan_CH:
Thanks for the quick reply

I've read it and saw the links to Amazon. But this would mean I have to make a hole in my car! *not amused* and I have a cabrio, means roof is not working...

Any re-use of my audi FM Antenna sytem possible? Audi has antenna somehow integrated in windows and carrosserie...

Cheers Pat
[Android Head-Units] IG_Vasilich:
if antenna in your car has no amplifier (i.e. it is passive antenna), then you can try to use antenna amplifier like this one https://www.amazon.de/Eightwood-Antenne-Amplifier-Blaupunkt-MVH-X580-SMBJ-DINP/dp/B0722JGGSZ/

But bear in mind, that if your car has built-in FM amplifier in the antenna feed, then additional amplifier won't work. In that case you can try to fetch your built-in rod aerial output and connect it directly to combined amplifier (thus override built-in FM amplifier).

And the last thing: all this has nothing to do with this great DAB-Z app! So if you want to discuss about antennas - pls open new thread.
[Android Head-Units] SkyBeam2048:
Usually not as many FM antenna systems apply a frequency filter and therefore attenuate the frequencies used by DAB. If your car is using an active (amplified) antenna it will very very likely not amplify the DAB+ frequencies if your OEM system is optimized for FM.

The good news is: You don't need to drill any holes if your car already has an external FM antenna. Just replace your antenna with an active combined FM/DAB/GPS antenna. You might have to run additional cables from the antenna to the head unit though as well as you might need additional power lines. An option to simplify things might be to take 12V from the wiper motor if the antenna is close by.

If you don't want to do it yourself, go to a car dealer or specialized car hifi dealer to mount it.

I personally have mounted an ABB 3785.01 combined roof mount antenna.

And yes, if you properly mount the antenna it will be a difference like night and day. I was barely able to receive any DAB station with the window antenna in my area and as soon as driving into a village I lost reception completely. Now I can even receive Radio BOB from germany in my area (btw. I am from Lucerne Area in Switzerland).
[Android Head-Units] Pataan_CH:
Thanks a lot both of you

I hope you didn't get it personal that I suspected the app to hide frequencies for me :-) sorry . The app is great and that's why I want to use it fully functional

Audi doesn't have external antenna. that means I have to investigate on Vasilich's input. I started this once, but gave up since results were not satisfying. Will re-start that project...

Once I am writing here: what is this OMRI stuff about, is there any explanation somewhere whether to use it or not?

Thanks, Pat
[Android Head-Units] SkyBeam2048:
No worries. Antenna issues are quite common. There is just nothing the Software can do to improve reception if the signal from the antenna is weak.

Somewhere the antenna is located. Some models do have an integrated antenna into the back or side window. Those antennas are different to the sticker antennas you typically put on the inside. But also most of them are optimized for a narrow frequency band.

So putting a real antenna somewhere on the outside might be the only valid option at the end. Even if you run a cable to an external antenna holding on to the car magnetically.

Unless your Audi is already all-plastic 🤣

For this to answer you need to know the history of DAB-Z. Initially it was "just" a GUI mod for the OEM DAB app delivered with those Chinese head units. The author did of course not have the source code but replaced GUI classes to change the look and feel. The USB communication to DAB sticks was handled by a proprietary binary (libdab). Of course this does not allow to work around any issues within this library as well as it does not allow to add new functionality which is simply not existing in this library.

So @realzoulou was looking for an alternative solution and he found OMRI. The source code of OMRI is available and it can be extended with new functionality. So he is able to fix issues and add new features.

Recently it was also announced that libdab is going to be removed in the near future as OMRI meanwhile is stable and seems to be working fine in most/all environments where libdab can be used.

So there is a clear recommendation: Use OMRI mode only!
[Android Head-Units] bluemask69:
Is your app compatible with Unisoc 7862 unit (Navifly CC3 or Teyes CC3) ?
[Android Head-Units] NogenLunde:
Both units are Android based, so DAB-Z should work. You need an USB dongle for DAB reception, search "usb dab" on aliexpress.
[Android Head-Units] Flosch_93:
I have exactly the same problems. For me, version 1.8.96 is the last version where harmony.fm and planet radio works.

Is there a solution to this problem in the meantime?
[Android Head-Units] pr3mi3r3:
Same problem for me, please fix it. Thanks.
[Android Head-Units] TorstenH:
Great to have this background information. Thank you!
[Android Head-Units] IG_Vasilich:
@realzoulou

just FYI: in my Intel SoFIA/Android 6 the above stations (harmony.fm and planet radio) have worked with every version of DAB-Z, and also work with newest .109.
[Android Head-Units] Flosch_93:
I tried it last night with my Samsung Galaxy S10 (OneUI Android 11). Unfortunately with the same problem. Maybe the higher Android versions cause this problem. Unfortunately I don't have a device with older Android to test it out.

Edit:

I just noticed that the harmony.fm and planet radio work again when I deactivate the OMRI mode.
[Android Head-Units] bluemask69:
the app don't work with the dongle DAB+ (I used before in MTCE unit) in the new unit 7862.
[Android Head-Units] TorstenH:
DAB-Z doesn't closes by itself /pauses playback if I switch to Headunit Reloaded and starting audio playback there.

If I start another audio app on the head unit (e.g. Black Player) DAB-Z stops how expected.

To stop DAB-Z playing in first case I have to use the app switcher to kill it. Not really funny while on the road.

Any ideas? Is there another way to silence DAB-Z?
[Android Head-Units] IG_Vasilich:
@TorstenH

1. broadcast Pause intent

2. In DAB-Z app screen press "back" button

3. (most preferred as it would work automatically :) ) Tell "Headunit reloaded" (no idea what it is) to use standard android functions for playing music - in that case DAB-Z detects, that other media application plays music, and therefore stops (as it do with any other music players e.g. Black Player).
[Android Head-Units] TorstenH:
I thought using DAB-Z and Headunit Reloaded is something like a standard.

[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi

This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis. App links: https://www.b3itlabs.com/prod.php?id=1 PlayStore...

xdaforums.com
[Android Head-Units] royalhawk2002:
@realzoulou :

I found a small issue with Service Following. When the signal disappears for few seconds (i.e. in the city tunnels), correctly the Service Following starts to search alternative frequencies. After that, since the alternate frequency is not found, the app return to the previous one that in the meantime is back. But, at this point, the signal strength is zero and audio is lost. Changing the station and coming back to the previous one it starts to play again. Is this behaviour correct ?
[Android Head-Units] realzoulou:
After a failed attempt to search for alternatives, it goes back to the station where it was before SF was attempted. This is expected behaviour.

The failure you saw (no signal bar, no audio) is likely due to a random failure, which I basically know about, but don't understand why it happens. It's in the lowest level part of OMRI, which talks to USB.
[Android Head-Units] TorstenH:
In meantime HUR was identified as the bad boy.
[Android Head-Units] hias9:
Since a few months a have the following problem.

After turning on the car and the unit, DAB-Z app starts automatically, the interface is working and the signal reception is shown correctly with the red/yellow/green bars. But there is no audio output to the speakers. I always have to close and restart the DAB-Z app, after that it is working.

Unit is a PX6 and I am using Android 9 with hal9k mod (latest version).
[Android Head-Units] pr3mi3r3:
It works again when you turn off OMRI.

Their is an issue with the new DAB-Z Version.
[Android Head-Units] IG_Vasilich:
@realzoulou

i made a trip to Austria last week, and heard mostly DAB+ radio on my way. Have some thoughts/suggestions/reports:

1. While service following works good when signal disappeared completely (thumbs up!), in several areas i had issues with reception. After scanning of new stations i have seen, that this station exists with same name on other ensembles, and can be triggered manually to search other station via SF. Could be that done also automatically in some cases (e.g. when reception has no audio in 4 seconds from last 10 seconds of reception)? the problem is that in such border areas you can still get signal from far transmitter, but audio will be interrupted quite often - let's say 1 second of audio following with 2 seconds of silence because of weak signak from that transmitter.

2. some stations show its name without the last char. I tried to clear station list and rescan - same problem. This bug appeared since ~2 months (?). I assume that it has smth to do with string encoding, because the names with missed last char have umlauts in names ("RadioRüsselsheim", "MDR Thür Mitte-W"), but not always names with umlauts are getting cut (e.g "MDR Thür West" is shown completely). I have looked into the logcat after station scanning, but haven't seen there anything that points to misbehaviour. I still can send you log if you interested. I have also checked those names on my kitchen DAB radio - it shows full names, doesn't cut last char.

3, 2 times i had a bug when after station scanning the progress window stayed in front of app forever - "cancel" button hadn't helped, a station started playing in background, but it was not possible to switch to other station. So the only way to get it working again was to close app from recent app list and restart DAB-Z.

I am using latest beta version in OMRI mode on Intel SoFIA (x86) + Android 6.0.1.

Thanks.
[Android Head-Units] NogenLunde:
I've experienced this once, too. Android 9.
[Android Head-Units] Mops10542:
Hello, i installed a new HU in my Honda.

Dab-Z worked fine… but i had 1 problem.

Dab-Z doesnt start on Warm Boot/Cold Boot automatically. I had to start the app manually

It starts Only automatic when i connect the usb Stick.

Any Help?
[Android Head-Units] NogenLunde:
That's how it's supposed to work. Why don't you have the USB dongle permanently connected? DAB-Z should then start automatically on boot of the Android device, provided you have selected that option.
[Android Head-Units] Mops10542:
It doenst Start automatically when the stick is connectet :(
[Android Head-Units] NogenLunde:
I see. What version of DAB-Z? Version Android?
[Android Head-Units] surfer63:
Which launcher are you using? Some launchers have a builtin media player which check USB before other apps get a chance, as the launcher is started first.
[Android Head-Units] Mops10542:
DAB-Z: 1.8.105

PX-6, Android 10

Standart Launcher, didnt work with agama/Car launcher pro
[Android Head-Units] trap63:
@realzoulou I bought a new HU (UIS7862 Navifly 6+128GB like Teyes CC3) and installed with same hardware of previous PX6 RK3399, same DAB hardware (usb stick and antenna) but it seems that on UIS7862 signal is often go and down, with no way to listen enough well. Sometimes you need to reinstall apk (both 1.8.105 and 1.9 Beta), and station list is empty twice. After some enter and exit, station list (90 in my area - NW Italy) will appear after scan. I think that there is incompatibility (or not?) with UIS7862, isn't it? If you wish I can help you to perform onthis platform, tell me what you need.
[Android Head-Units] r33a:
Same here, station search does not find any station on channel 6A in OMRI mode
[Android Head-Units] realzoulou:
@trap63 could you enable "OMRI verbose logging", restart DAB-Z and capture a logcat for me? See post #1 for instructions
[Android Head-Units] trap63:
tha

that's ok, I will test with upcoming new stick and I will send you log as detailed.
[Android Head-Units] denization:
hello everyone

i was wondering if i am missing something, but i dont get service following to work. i read that realzoulou wrote somewhere here that the 'trigger' for SF is only sent every now and then by the radio stations, but even if i listen to the same station for like half an hour or longer it never gets SF. is it supposed to work in the DACH countries? i didnt try a vast lot of station, but i assumed "major"/governmental stations like bayern3 or the SRF stations would support SF.

i use a rockchip PX5 or 6 (dont remember) / MCU S32F0 radio with the malaysk rom and agama launcher and the latest version of dab-z. any ideas how i could get SF to work?

regards
[Android Head-Units] IG_Vasilich:
it worked for me in Austria (for global mux and in Vienna), and works for both so called "Bundesmux" - "DR Deutschland" and "Antenne DE". There are some stations, that send SF information on some ensembles, but not on all of those. No idea about Switzerland though.
[Android Head-Units] trap63:
Well, @realzoulou I confirm you that on UIS7862 Platform, manufacturer 116 NaviFly your apk really works very fine. I found the big issue: car antenna. I removed windshield dab antenna and I installed a factory car antenna of Renault genuine (Renault Samsung), the new shark antenna for CLIO IV MEGANE IV 8201684054.

Now I receive inside my private park.. more than 119 stations!

All the chinese windshield dab antennas are very poor, try all with genuine roof antenna, the Renault one is full passive, no need of signal amplifier

Antenna ORIGINALE RENAULT CLIO IV MEGANE IV 8201684054 | eBay

Le migliori offerte per Antenna ORIGINALE RENAULT CLIO IV MEGANE IV 8201684054 sono su eBay ✓ Confronta prezzi e caratteristiche di prodotti nuovi e usati ✓ Molti articoli con consegna gratis!

www.ebay.it
[Android Head-Units] Flemischguy:
I have a Teyes CC3, also on the UIS7862 Platform, the app works really great. It is so important to place the DAB+ receiver or antenna away from the headunit screen and power wirers/fuse boxes in gloveboxes. Since i placed the DAB+ receiver in the trunk (connected to a powered tripp lite usb hub) in combination with a shark antenna on my roof, i have barely have drop outs of DAB+ signals and receiving even Dutch channels 15 km away from the border.