yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] realzoulou:
DAB-Z release 2.0.222 BETA

Change log:

compared to 2.0.221

* Fix: Removed Settings->Appearance "Show time" when in portrait mode because time widget is not present in portrait layout

* Fix: Re-added Settings->Appearance checkbox "Show SlideShow" (default enabled) (@SKMPLKS #200, @Kikipf #204, @IdleBadger #227)

* Fix: Manage station list: Incorrect sorting when station name starts with a "_" (@angelo1977 #222)

* Fix: Station scan did not delete old stations. Now deletes all stations except when marked as favorite.

* Fix: Rotary controller now only operates on the station list (@pin1904)

* Fix: Vertical station list not showing the favorite icon

* New: Settings->Appearance: Allow to disable notification when changing stations and app is not visible

* New: Settings->Appearance: User can choose between Toast (=default) and Notification (Android >=8 and <=12) with following limitations:

1. Android <= 7.x always uses Toast, Android >= 13 always uses Notification

2. Android 8.x to 11: Notification mimics the look of a Toast.

3. From Android 12 on, the system decides how a notification looks like

* New: Manage station list: Allow to delete stations in ALL list

* New: Settings->Station logos: Allow to define min/max logo dimensions used during RadioDNS logo download

WARNING: Non-default RadioDNS min/max logo dimension settings could negatively impact duration of logo update and app startup!

Known issues, especially with Android >= 12:

* Unable to select backgrounds

* Unable to import logos

* Unable to import station list after re-installation
[Android Head-Units] SKMPLKS:
the slideshow is hidden in DAB-Z, but it is still shown on Ubiquity Music and other android widgets. can this be resolved? :)
[Android Head-Units] pewo:
Using 2.0.221.This app is great!

Unfortunately I have the following problem:

When switching between the applications, rear view camera, main screen, navigation, the display freezes or nothing is displayed. For example, the message appears:

"Here we go" doesn't respond

x Close app

x Wait

or

"Radio" doesn't respond,

"Overview" doesn't respond....

When using 1.9.127 every thing is running well, but I like the design of version 2.0.221...

How can I solve this problem?

System: rk3566, Android 12

Thx in advance

Peter
[Android Head-Units] Kikipf:
Die Diashow ist ausgeschaltet, wird aber weiterhin angezeigt. Ein Neustart der App und des Radios hat nichts gebracht.

Mod translation: The slideshow is turned off but continues to display. Restarting the app and the radio didn't help.
[Android Head-Units] realzoulou:
What launcher app are you using?
[Android Head-Units] pewo:
The origin one from M.I.C Rafio. Don‘t no the name..
[Android Head-Units] whitebait:
I'm getting a crash on app start-up on beta 2.0.222.

Tried clearing cache and storage, uninstalling and reinstalling and removed myself from beta on play store (though realised that I was still downloading 2.0.222 after leaving the beta. Been using dab-z for literally years and not had this issue previously.

After storage clear/reinstall I get prompted to use dab usb adaptor, grant access to storage, choose layout and colour etc after which it crashes back to home screen without ever opening the app. After a couple of crashes it asks if I wish to access settings, which I do and can without a crash, but nothing obviously weird is set there and leaving setting to get to main gui causes a further crash.

HU is an android 10 px5 with 4GB Ram and 64GB storage (xtrons unit if I recall).

Let me know if a logcat would be useful or if you'd like me to try anything else. I will attempt reinstall 221 in the meantime!

Edit: rolled back to 221 and it's working fine. If you let me know if/how to capture a log at without root (and presumably outside of the app?) then I'm happy to do so.
[Android Head-Units] realzoulou:
Hi @whitebait I checked the Firebase Crashlytics statistics and I see that 2 PX5 Android 8 devices created dozends of crashes at the moment when the Change History dialog should be shown, which is a automatically shown once after updating to a new version.

My typical test device is an Android 10 PX5 device (4/64 GB), so I am quite astonished about your issue.

Are you sure that you have Android 10 and not Android 8?

Only Android 8 PX5 devices show the issue so far in the statistics.

You can double-check my theory by installing 2.0.222 again and then after the repeated crashes when the red crash dialog appears, go to Settings, then Info and press "Changes" button. If the app then again crashes, then it is clearly the same issue of what I see from the crash statistics.
[Android Head-Units] whitebait:
Hmm, pretty certain it's A10. I seem to recall it did start life as A8 and I upgraded it

I will try to reinstall and replicate the issue. I'll give the settings/info/changes thing a try. I'll keep you posted! If it's any use, I'm pretty certain that I didn't see a change log page previously after upgrading to 222 (so maybe crashing at/before that point) but could be wrong!
[Android Head-Units] whitebait:
Hey, so confirmed today that it is an android 10 unit for definite. Correction though, it's 32gb storage, not 64.

Rejoined beta and upgraded to 222, went through the screens selecting colour scheme and layout, then to dab-z splash screen and then crash. Went to settings when prompted then info, section at top is partially obscured by info banner but guessing that's the change log button near right. Tap that and it crashes again.

Hope that helps!
[Android Head-Units] wainsie:
I'm having a issue with version 222, randomly when I change station the stereo crashes with system UI has crashed, and keeps loading system and then crashing, need to quickly go into the settings and force stop dab, doesn't happen with 221, but unable to send a log at as keeps resetting the home screen and apps, have gone back to 221 for the while
[Android Head-Units] TheRiddler:
Hi ... I have been using DAB+ but thought I would try DAB Z. DAB Z works really well, but I can't get the settings icon (screen resolution is 480 x 400, using android 11 ...)? Does the menu scroll up or something? Thanks for your help!
[Android Head-Units] TheRiddler:
Sorry ... my bad, screen resolution is 800 x 480 (6.2" screen)
[Android Head-Units] TheRiddler:
Here is a picture ... initially settings icon shows, but then disappears when top strip shows?
[Android Head-Units] TheRiddler:
Sorry picture didn't seem to upload ...
[Android Head-Units] TheRiddler:
View attachment 6038876
[Android Head-Units] SkyBeam2048:
Same here. Crashes on very single startup.

When startup-crash detection kicks in going to info and pressing the 90% hidden button on top behind the top row it crashes too.
[Android Head-Units] realzoulou:
@whitebait Your device is missing "Android System WebView", which is supposed to be on every Android device. DAB-Z since 2.0.222 uses this to show the Change History dialog. Because some devices seem to exist, which miss WebView, the next version will no longer show the Change history dialog on such devices.
[Android Head-Units] whitebait:
That's weird! I definitely see it update webview quite regularly... That probably explains why waze stopped working a while back on there as well. I'll have to check version of webview installed and see if I can change a setting somewhere so apps can actually use it? Any pointers on how I can resolve it beyond the above?
[Android Head-Units] SkyBeam2048:
I can also confirm I do have Android System Webview installed. System log however stating DAB-z crashing in webview module:

12-02 18:04:16.179 868 868 F libc : Fatal signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0x7ceeed9fe4 in tid 868 (com.zoulou.dab), pid 868 (com.zoulou.dab)
12-02 18:04:16.556 2382 2382 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-02 18:04:16.557 2382 2382 F DEBUG : Build fingerprint: 'rockchip/rk3368/rk3368:10/QQ2A.200305.004.A1/eng.hct2.20210311.174752:userdebug/test-keys'
12-02 18:04:16.557 2382 2382 F DEBUG : Revision: '0'
12-02 18:04:16.557 2382 2382 F DEBUG : ABI: 'arm64'
12-02 18:04:16.559 2382 2382 F DEBUG : Timestamp: 2023-12-02 18:04:16+0100
12-02 18:04:16.559 2382 2382 F DEBUG : pid: 868, tid: 868, name: com.zoulou.dab >>> com.zoulou.dab <<<
12-02 18:04:16.559 2382 2382 F DEBUG : uid: 10159
12-02 18:04:16.559 2382 2382 F DEBUG : signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0x7ceeed9fe4
12-02 18:04:16.559 2382 2382 F DEBUG : Abort message: '[FATAL:jni_android.cc(290)] Please include Java exception stack in crash report
12-02 18:04:16.559 2382 2382 F DEBUG : '
12-02 18:04:16.559 2382 2382 F DEBUG : x0 0000000000000000 x1 0000007ced0d52c7 x2 ffffffffffffffff x3 ffffffffffffffff
12-02 18:04:16.559 2382 2382 F DEBUG : x4 8080800000000080 x5 fefeff7bedf440ff x6 fefeff7bedf440ff x7 7f7f7f7fffff7f7f
12-02 18:04:16.559 2382 2382 F DEBUG : x8 0000000000000000 x9 0000000000000000 x10 0000000000000001 x11 0000000000000000
12-02 18:04:16.559 2382 2382 F DEBUG : x12 00000002002164c0 x13 ffffffffffffffff x14 0000000000000004 x15 ffffffffffffffff
12-02 18:04:16.559 2382 2382 F DEBUG : x16 0000007cf3394aa8 x17 0000007dc47a62d8 x18 0000007dc90da000 x19 0000007ffc729640
12-02 18:04:16.559 2382 2382 F DEBUG : x20 0000007ffc729650 x21 0000007cf33bc000 x22 0000007cf343e000 x23 000000000000004f
12-02 18:04:16.559 2382 2382 F DEBUG : x24 0000007ced16b07f x25 0000007dc8208020 x26 0000007dc7f16cb0 x27 0000000000000001
12-02 18:04:16.559 2382 2382 F DEBUG : x28 0000007ffc729cb0 x29 0000007ffc7295f0
12-02 18:04:16.559 2382 2382 F DEBUG : sp 0000007ffc729180 lr 0000007ceeed9db8 pc 0000007ceeed9fe4
12-02 18:04:16.594 2382 2382 F DEBUG :
12-02 18:04:16.594 2382 2382 F DEBUG : backtrace:
12-02 18:04:16.594 2382 2382 F DEBUG : #00 pc 0000000001ffefe4 /data/app/com.google.android.webview-Wk46uwSz9lEVrI-sp8pCDQ==/base.apk!libmonochrome.so (offset 0x401000) (BuildId: 52141180e9c8e41d48dd59c573f4674c9391afb5)
[Android Head-Units] whitebait:
I uninstalled all updates from Android system webview (which was installed already - v119.0.6045.163). This left version 77.0.3865.92 installed. Dab-z 222 and waze now work fine on the ancient webview version. No idea why the new version doesn't seem to be recognised/used by stuff though?
[Android Head-Units] realzoulou:
DAB-Z release 2.0.223 BETA

Change log:

compared to 2.0.222

* New: Settings->Appearance: Day/Night mode: Added Time and Location based switch, requires Coarse Location permission to calculate sunrise/sunset time

* Fix: If Show SlideShow disabled in Settings, MediaSession Album Art was still showing the SlideShow picture (@SKMPLKS #232)

* Fix: Crash when trying to show Change history on devices without WebView. Such devices will not see Change history anymore (@whitebait #238)
[Android Head-Units] SkyBeam2048:
I installed version 2.0.223 now and it still crashed. Tried uninstalling Android System WebView updates and was able to run it just normally (displaying change notes on initial startup). After closing down change notes I was able to also upgrade WebView again. However now it immediately crashes when tapping on the "info" button in settings. Not even the info screen is shown and crashing only when trying to open the changelog. It immediately crashes when tapping the "info" button.

I personally also never understood why an app needs to show the change logs on startup. If I am interested i can open it from the info screen. Most people don't cate about it as long as the app is auto-udpated and still working the same way as before. In any case it looks like the workaround implemented to detect WebView issues are also crashing the app so the workaround is not really helpful in current implementation.

Anyway a workaround for the crashes is to uninstall all WebView updates temporary.
[Android Head-Units] Dai-San:
This version of Dab-Z slows my Xtrons head unit to a crawl and makes the entire unit unusable which is a shame as I loved the old version as it displays the station loge and track info nicely in Agama Car Launcher.
[Android Head-Units] realzoulou:
DAB-Z does not support 800x480 @240 dpi well. This is nowadays very unusual low resolution.

I propose you deinstall and reinstall DAB-Z in order to see the Intro screens again.

Then select bottom navigation bar (instead default left nav bar).

Then you should be able to get sth similiar to this:
[Android Head-Units] realzoulou:
If possible try to provide me a system-wide logcat of a startup (Settings->Info->logcat button)

This requires a rooted unit with SuperSU or similar mechanism installed so that DAB-Z can use su to create a log of ALL Android firmware and Apps.
[Android Head-Units] whitebait:
So it looks like the crash is due to the bug/issue discussed here: https://issuetracker.google.com/issues/233924343?pli=1

Silly question, but if I wanted to install v100 of android system webview (as the newest version a px5 can handle without encountering this bug) does anyone know which of the 11 available versions here I would need?

Android System WebView 100.0.4896.127 APK Download by Google LLC - APKMirror

Android System WebView 100.0.4896.127 APK Download by Google LLC - APKMirror Free and safe Android APK downloads

www.apkmirror.com
[Android Head-Units] TheRiddler:
I dont seem to be able to change options? Seems to default to nav bar left & station bar horizontal? Tried tapping on option but nothing happens. You can see a darker area around button ... so it is picking up that you are touching it but I can't get anything to change? Is there a config file or something that I could edit to have a different default configuration?
[Android Head-Units] realzoulou:
I doubt that Android WebView would ever fix https://issuetracker.google.com/issues/233924343

My own PX5 and PX6 Android 10 devices all suffered from such crashes. It was finally fixed by Hal9K ROM 5.2.0.

FYI: According to Google Firebase crash statistics this crash of DAB-Z in libmonochrome.so only happens for PX5+PX6 Android 10 devices.

The next version of DAB-Z will try to avoid the endless crash loop. It will crash once (trying to show the change history) and at next start it would not again try to show this dialog... until the next update....
[Android Head-Units] realzoulou:
Ok, I did not expect that ... I will make this area scrollable for you in next version.

Then you can scroll the area where it currently only shows "Left" or "Horizontal" and will be able to see the other options for "Bottum" and "Vertical" also.
[Android Head-Units] TheRiddler:
Thanks ... really appreciate that 🙂
[Android Head-Units] SkyBeam2048:
Many thanks. What about having a setting in options whether to show change log after update at all?

Most of us just update and use the app and people interested in change logs can still view it in about dialog or here on xda or on google play.

I am actually on HAL9k 5.0.0 and can't update as updates are not provided unless you own a license. Thinking about switching to the latest HCT4 which appeared here but the link is dead and missing key remap feature. Anyway I am fine if change logs are not displayed.
[Android Head-Units] realzoulou:
DAB-Z release 2.0.224 PUBLIC (12 Dec 2023)

Change log:

compared to 2.0.223

* Fix: Time based automatic Day/Night mode not always working as expected

* Fix: Intro Navigation bar position and Station list orientation not selectable on 800x480 resolution @TheRiddler #259

* Fix: Avoid endless crash loop for change history dialog @SkyBeam2048 #254
[Android Head-Units] TheRiddler:
As this is a BETA, how would I go about loading it? Strike that, sorted it. Seems to be working fine now 🙂 Thanks for the update!
[Android Head-Units] angelo1977:
Hi @realzoulou , have you managed to fix the import of the logos?
[Android Head-Units] SkyBeam2048:
Thank you very much.

I confirm the crash-loop detection is working and DAB-Z starting normally after first crashing. Still I am not sure why the change notes need to be displayed after update and I would like to disable this by setting (should potentially be off by default).

I also found that DAB-.Z still crashing when going to settings -> Info screen. Is the previous code trying to detect the WebView issue still in there? I am asking as it started to crash when entering the info dialog when you tried to add detection. Before the info dialog was opening properly and it only crashed when hitting the button to display the change log. So now I cannot even open the info dialog at all

Thanks again for all your effort put into the app.
[Android Head-Units] SKMPLKS:
Hello, I use the Nova Launcher in my car. Every time I start my car, the Nova Launcher comes over DAB-Z, so Nova in the foreground and DAB-Z in the background. Is there a setting somewhere that ensures that DAB-Z starts in the foreground and not the Nova Launcher?
[Android Head-Units] SirMirakuru:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

Hello everyone.

Can someone please tell me where I can get the logos? DAB Z only finds a few and I can't find any on the internet.

Please help me

*********************

Hallo zusammen.

Kann mir bitte jemand sagen, wo ich den Logos herbekomme? DAB Z findet nur ein paar und im Internet finde ich keine.

Bitte helft mir
[Android Head-Units] Oswald Boelcke:
Hello and good afternoon, @SirMirakuru Welcome to XDA! I hope you'll always get the support you require and have enjoyable times on our platform.

However, as a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your German posts.

Spoiler content hidden.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Android Head-Units] SirMirakuru:
Hallo and sorry

Hello everyone.

Can someone please tell me where I can get the logos from?

DAB Z only finds a few and I can't find any on the internet.

Please help me
[Android Head-Units] realzoulou:
On Android >= 12 devices this is still not solved
[Android Head-Units] realzoulou:
Yes, on devices where WebView crashes in libmonochrome.so (or libtrichrome.so) due to a missing ThermalService implementation in the Android system images, one will never be able to see change history because the change history is an internally created web page.
[Android Head-Units] realzoulou:
Not in DAB-Z. An app cannot enforce that it comes to foreground. You would need to direct this topic to the Nova Launcher developer.
[Android Head-Units] realzoulou:
Please look at #223
[Android Head-Units] SirMirakuru:
THX i will try it tommorow
[Android Head-Units] SkyBeam2048:
Yes but I think you missed my point here.

Before 2.0.223 I could perfectly open the info screen and see everything on it without any issues as the info screen does not use WebView to display.

DAB-Z however was crashing (expected) when hitting the button to show the change log.

Then you tried to catch the issue and implemented changes on the info screen. Now it is instantly crashing when tapping the info button. I guess there is still some debug code in there which trying to detect the issue and causing DAB-Z to crash when opening the info screen. This code should be removed again so at least DAB-Z only crashing when the change history button on info screen is tapped. But not crashing already when the info screen is tapped in settings.
[Android Head-Units] oynsy:
Hi there, I'm a noob, I hope I'm in the right place, I have an Xtrons IQP92M245P, I have always used dab-z with an external aerial and usb dongle, it was fine until I updated to version 2.0.221 and now it just shows a blue screen error message saying -

This app requires a DAB-+ USB adapter being connected

to the device.

If no supported adapter is found, the app will close

itself.

SDR adapters are NOT Supported!

I've tried a different usb port, with the same result, other dab apps seem to be working, any ideas? I appreciate any help,

Thanks
[Android Head-Units] giant53:
This screen appears on my radio after an update. Did you try the arrow to the right? (2 or 3 times) Then you can use the app.
[Android Head-Units] oynsy:
Thanks, I'll give it a go
[Android Head-Units] oynsy:
Thank very much, it was obvious when you mentioned it, really appreciate it, working again
[Android Head-Units] TheRiddler:
Hi ... have got app working & layout good. Nice to be able to use settings button! Just one issue ... car head unit & SWC not working for next/prev buttons? Using 2.0.224 BETA version... on Android 11.
[Android Head-Units] TheRiddler:
Also, I have some logos I got from RadioDNS UK website. I am going to try using them ... I have read the tutorial on page 1 but was wondering which resolution of logos I should use (there are 3 options - 32x32 pixels, 112x 32 pixels & 128x128 pixels)?
[Android Head-Units] Zizoun8792:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

Hello, I have a problem. I have no signal in the app. Does anyone know what I should do?

Thank you.

*********************

Dobrý den, mám problém. V aplikaci nemám signál. Ví někdo, co mám dělat?

Děkuji.
[Android Head-Units] Oswald Boelcke:
Hello and good afternoon, @Zizoun8792 Welcome to XDA! I hope you'll always get the support you require and have enjoyable times on our platform.

However, as a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Czech posts.

Spoiler content hidden.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Android Head-Units] Clandaries:
On the VW website you need a serialnumber of the infotainments system.

Can someone provide a downloadlink to the latest logos?
[Android Head-Units] TheRiddler:
This is the site I found ... (UK based?):

Home

Hope that helps?
[Android Head-Units] -fluffy-:
My didt the same yesterday

I just had to set it up again an all works again
[Android Head-Units] pwood999:
Have been using V1.x for quite a few years with no issues.

Tried this version for a few days in my Joying Intel Sofia Android 6.x stereo. It scanned for stations ok, but after the scan some stations failed to tune correctly. Turns out it's mainly stations with Service following that are in different multiplexes across the UK (Absolute Radio for example).

Uninstalled V2, and re-loaded last V1.9.127 from apkpure. This scans & finds all the same stations as above, but correctly selects my local copy of Absolute or other radios with multiple frequencies.

I must admit I prefer the old layout overall but that's just me !!
[Android Head-Units] realzoulou:
Post #2 has a video on how to achieve (nearly) same layout as v1
[Android Head-Units] bockywocky:
Hello, is there also a Windows version available somewhere?
[Android Head-Units] realzoulou:
No, this app only exists for Android
[Android Head-Units] olemann96:
Is it possible to receive messages from TAs through this app (norway)? And can one search in a new list that replaces existing channels?

In Norway, there are several DAB zones that correspond to the counties. I've experienced instances where the channels appear duplicated.
[Android Head-Units] Clandaries:
I think we would need two DAB receivers to get this to work.

In car entertainment system they also have doubletuners to get this to work.

One is always watching in the background and then it switches.

In Germany we have the same Station but like one for Kiel, one for Hamburg one for Schleswig-Holstein and so on.

So the tuner has to always check in the background to find the best station and then dont look at the community like Hamburg but just for the name like NDR2.

And i dont think that it will be possible with our cheap DAB adapters.
[Android Head-Units] okij:
It would be possible with two of our cheap DAB adapters, given that @realzoulou would implement support for it. :) But IIRC he dropped it from the roadmap, unfortunately.