yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] realzoulou:
Never even thought about this and never attempted to use Google Assistent to start an App. Will check if it's really true that the assistent tries to calculate "DAB minus Z" ;)

This odd behavior may be a result of the launcher you are using. On phones this works flawlessly. On my Joying Android 6 it also works fine with the stock launcher (launcher 2).

Are you using Xposed? What Android version are you using and what device is it?

Totally agreed. I changed to a new MediaStyle notification and this is more a step backwards than forwards. Will try to improve this.

Hmm, I have not touched this area since the old ZOU-DAB version. Logos were never picked up from /logos folder directly. The png or jpg files always needed to be in a subfolder of DAB/logos The name of the subfolder is irrelevant. Or you can simply use the predefined /DAB/logos/user folder.
[Android Head-Units] realzoulou:
Release 1.0.31 should appear soon in Google Play.

Change log:

New: Create logcat and send it as e-mail from Settings->Info

Fix: Re-occuring USB permission request in Android 7 and 8

Fix: Frequent crashes due to ANR (Application Not Responding) in Android 8

I am not 100% sure if I was able to fix the re-occuring USB permission requests in all circumstances. But I guess it ain't be worse than it already is. So, please test this out and let me know of any issues.
[Android Head-Units] surfer63:
I'm almost sure it has something to do with the name, but I'm not sure it has to do with the "DAB minus Z". It was one of the reasons I could think off.
[Android Head-Units] CelticWebSolutions:
I recently swapped from Malysk to Halsk9 rom on my PX5, factory wipe then installed all my apps again. For some reason DAB+ won't start from play store, nothing happens when you attempt to open it. However installing an old version that I used before it became available on the play store works fine. Is this a known issue by any chance?
[Android Head-Units] realzoulou:
No, this is new to me. Are you able to create a full logcat of the system with when you attempt to start DAB-Z? If yes, send that to me. I will have a look then.
[Android Head-Units] CelticWebSolutions:
https://pastebin.com/BdQsEhYw
[Android Head-Units] realzoulou:
[MENTION=4110046]CelticWebSolutions[/MENTION] Very strange. ActivityManager kills quite a lot of things all the time. And also com.zoulou.dab is in the list below. And this is why it never comes up.

10-20 15:56:13.486 484 484 I ActivityManager: Force stopping cn.manstep.phonemirrorBox appid=10104 user=0: from pid 484
10-20 15:56:13.498 484 484 I ActivityManager: Force stopping service ServiceRecord{62ac41d u0 cn.manstep.phonemirrorBox/.AutoStartService}
10-20 15:56:13.503 484 484 I ActivityManager: Force stopping com.ex.dabplayer.pad appid=10110 user=0: from pid 484
10-20 15:56:13.590 484 484 I ActivityManager: Force stopping cn.manstep.phonemirrorBox appid=10104 user=0: from pid 484
10-20 15:56:13.604 484 484 I ActivityManager: Force stopping com.ex.dabplayer.pad appid=10110 user=0: from pid 484
10-20 15:56:13.619 484 484 I ActivityManager: Force stopping cn.manstep.phonemirrorBox appid=10104 user=0: from pid 484
10-20 15:56:13.637 484 484 I ActivityManager: Force stopping com.ex.dabplayer.pad appid=10110 user=0: from pid 484
10-20 15:56:13.756 484 484 I ActivityManager: Force stopping com.zoulou.dab appid=10112 user=0: from pid 484
10-20 15:56:13.876 484 484 I ActivityManager: Force stopping cn.manstep.phonemirrorBox appid=10104 user=0: from pid 484
10-20 15:56:13.956 484 484 I ActivityManager: Force stopping cn.manstep.phonemirrorBox appid=10104 user=0: from pid 484
10-20 15:56:13.963 484 484 I ActivityManager: Force stopping com.ex.dabplayer.pad appid=10110 user=0: from pid 484

For me there seems to be some bug in this Halsk9 Android. But I can't tell what is is. For sure this guy should run a spell checker on his changes:

ActivityManager: getPackageFerformanceMode--ComponentInfo{com.zoulou.dab/com.zoulou.dab.activity.MainActivity}----com.zoulou.dab

The above line is not part of Google's version of 8.0.0
[Android Head-Units] CelticWebSolutions:
Actually, I admit to not having read that it was force quitting things. I may have an idea what that is. I’ll give it a try later and let you know. Thanks for he prompt reply :)
[Android Head-Units] haynesteve:
I actually had this problem on Hal9k Rom, and discovered i had it blocked from running at same time as a music app. After cancelling this, it runs perfectly now. Might not be same, but worth checking
[Android Head-Units] CelticWebSolutions:
That’s exactly what I was thinking when I said yesterday. Weirdly, if you select it to not run with other apps, this one will never run, even if it’s the only app running. It’s no great issue, just need to remember to turn it off or it ends up running at the same time as other audio apps.
[Android Head-Units] surfer63:
I actually consider this a bug in the Hal9K ROM. Android is designed so that only one app at the time can use the media audio channel (with some exception for phone calls) and every car unit android behaves like that as well. So why does this hal9k rom need an xposed module for that?
[Android Head-Units] CelticWebSolutions:
I actually find it useful that some poorly made apps can now have audio over other apps. For example, my Waze app and CarPlay app didn’t used to play nice, one would stop the other, now they play nicely together and I can listen to music wit CarPlay and have audio from android Waze. I know iPhone Waze works with CarPlay but android one is much better imo
[Android Head-Units] surfer63:
I understand what you mean. The Joying uses a txt file for that in the assets of the main server apk. It only contains some Asian navigation apps. I extended that with almost all Western Nav apps (incl. your mentioned Waze) and recompiled it.

I assume every ROM builder (Microntek, FYT, QD) has their own approach, but I would not wonder if your unit has such a same main server apk. With decompiling apks over the several ROMs there are so much similarities, apart from that MCU control of course.
[Android Head-Units] halo_djk:
Installed new version from play store.

With no usb turned on app starts even if unit was shut down with another music app playing. Never used to do that with last Web release.

Also on every start app icon moves by itself now to the empty spot in the bottom right corner of the screen after I always put it in the top left corner.

---------- Post added at 02:22 AM ---------- Previous post was at 02:22 AM ----------

Installed new version from play store.

With no usb turned on app starts even if unit was shut down with another music app playing. Never used to do that with last Web release.

Also on every start app icon moves by itself now to the empty spot in the bottom right corner of the screen after I always put it in the top left corner.
[Android Head-Units] biker_955:
Latest ver. still asking for usb permissions every time for me. (I have auto start off if it makes a difference)
[Android Head-Units] typos1:
I would think he was trying to prevent the scenario where you get MTC apps etc playing at the same time as other, non built in music apps,why dont you ask him ? Hes usually responsive to feedback.
[Android Head-Units] realzoulou:
On your 1st point. Are you sure that not the launcher is starting DAB-Z again at startup? You can check the reason why the app was started in Settings->Info.

On 2nd (moving app icon): Sounds like a launcher issue. DAB-Z app exchanges the launch activity at the moment when you change the setting for "Automatic start on USB device detection". It does not do anything afterwards and for sure not on every startup of the device.

Yes, it makes a huge difference. Unfortunately, Android is behaving very un-consequently and I am struggling to find a solution that fits everyone.

Let me explain:

1. There are Android devices that require a "USB device filter" to be present in the app in order to stop asking for permission at every start of the app (or after a restart of the whole device). Note that this is not about the Android version. Looks like this is an option when building an Android for a specific device, but I am not sure about this.

2. When a "USB device filter" is present, then the app is started automatically by Android after the USB device is connected. The checkbox in that dialog is obviously not functioning correctly.

Btw, the "USB device filter" is nothing else than an XML file that contains the USB VID/PID combination of the DAB USB adapter.

Understandably, no users wants to see the permission dialog more than once. I can also understand that the DAB app should not always start when the head unit is started.

But with the "USB device filter" being used for both by Android, I am unsure if I can ever solve this topic for everyone.
[Android Head-Units] halo_djk:
I'll keep an eye on it. Re start up, I intentionally left my MP3 player running at shut down, then on restart, dab came on.

The moving icon issue has happened to me both times I started the car.

On upgrading dab z after I was sure it was done about 5 seconds later I watched it move, so I figured it was part of the upgrade process and I moved it back. On starting the car the second time, about 5 seconds after start it jumped back to the wrong spot again. This has only happened after the last update.
[Android Head-Units] sieg01:
Hi,

supports the DAB-Z app the TPEG (Transport Protocol Experts Group), if yes how can I see it?

---------- Post added at 07:55 AM ---------- Previous post was at 07:55 AM ----------

Hi,

supports the DAB-Z app the TPEG (Transport Protocol Experts Group), if yes how can I see it?
[Android Head-Units] realzoulou:
No, there is no support of TPEG. There is not much use of such support anyway because Navigation apps do not have any standard interface in order to feed TPEG data into the app.
[Android Head-Units] skezza:
Does anyone know if these adapters support Link Set's?
[Android Head-Units] SkyBeam2048:
Actually I confirm that DAB-Z from play store still asks for USB permissions when started by launcher/ROM. However I have noticed that it does not ask for USB permissions if started by USB device.

I did disable the "Automatic start on USB device detection" option when upgrading to Hal9k Oreo ROM and intended to use the ROM built-in function to launch the app on resume. It kind of worked but each time DAB-Z launches I am asked for USB permissions. So I disabled auto-start on resume in the ROM and instead re-enabled "Automatic start on USB device detection" in DAB-Z app. Now the app also auto-launches on resume but does not ask for permission.

However this might not be a solution if you don't want to have DAB-Z running on every resume but just run on-demand.
[Android Head-Units] iMattmax:
I have the same problem / result...
[Android Head-Units] halo_djk:
Icon on the home screen since last update still moving around. As reported before. The first play store version didn't move.

I tried to move it to the spot where I wanted, then plugged up the hole it kept moving to with another app icon. After shut down and restart it still moved, right to the last page of apps.

Something to do with the nousb addition me thinks.
[Android Head-Units] realzoulou:
I will release soon a new version where I do not modify the launch activity anymore. So the "moving icon" should no longer happen.

I still want to avoid having to release a "nousbdf" version in Google Play.

When the option "Automatic start on USB device detection" is set to disabled, then the app will close itself as soon as possible. This should then not disturb any other music player that is already running. I think this is the main reason why a lot of users want the "nousbdf" version.

Or is there anyone that used to have the old (non-Google) "nousbdf" version for any other reason?
[Android Head-Units] royalhawk2002:
In my case the main reason is the continuous request of USB permission at every start.

(issue still confirmed with the last version from Google Play)
[Android Head-Units] Bose321:
Not sure if it has been reported, but I tried to convert to the Store version. (Btw, I like the idea, because of updates and such). Works fine mostly, but I lost the previous/next buttons on the notification? Now It's back to a huuuge and high notification with just a DAB+ logo. Is that an option? Couldn't find it. Loved that feature. So for me it's back to the 'old' version.
[Android Head-Units] biker_955:
I only want it not to autostart. It should let another media player/radio take over but can stay running just muted.

I tend to switch between dab & fm as I loose the dab signal and switch over. Sketchy coverage here and still only a crappy internal ae, until I can get the new one fitted. (not happening at the mo as it is FREEZING outside)
[Android Head-Units] realzoulou:
Hmm, this astonishes me. So I guess I have to do a nousbdf Version in Play Store. Your Xtrons PB68WRJP with Android 8 does not behave like other Android 8 devices do.

Will fix in next release.

Thanks for the feedback.
[Android Head-Units] iMattmax:
That's the same thing for me...
[Android Head-Units] realzoulou:
[MENTION=1227970]royalhawk2002[/MENTION] and [MENTION=4240402]iMattmax[/MENTION]

Could you please try the attached nousbdf Version and let me know if there is any improvement for you?

Please note that you will have to un-install this version again once I release it to Google Play because Google re-signs the apk with different signing keys.
[Android Head-Units] surfer63:
Hi realzoulou.

Can't you make a version that checks for the existence of an /sdcard/nousbdf.txt. If found act as nousbdf, if not found behave as standard.

It means that users have to create an /sdcard/nousbdf.txt file, but that is not a big deal. It could also be created/removed from the Setting screen.

Or will that not help?
[Android Head-Units] realzoulou:
This would not help. The main difference between the "normal" and "nousbdf" is in the AndroidManifest.xml.

The content of this file cannot be changed programmatically after installation of the apk. The AndroidManifest defines how Android will treat the app in various ways, including whether Android's UsbSettingsManager will save persistenly that the User granted the USB permission.

You can read about the USB device filter entry in the AndroidManifest here: https://developer.android.com/guide/topics/connectivity/usb/host#discovering-d

IMHO, the Android documentation lacks a lot of information and/or head unit vendors change Android in an incompatible way.

Example:

All Android versions that I run in Genymotion's VirtualBox based emulator and all Android devices that I own personally, need the USB device_filter.xml to be present in my app (="normal" version), otherwise the devices/emulator images do not remember that I granted USB permission already and keep asking me after reboot.

For a lot of users, it seems to be exactly the other way round.

Btw. Thanks a lot for the hint regarding "directBootAware". Since I added this into version 1.0.31, I get no questions from Android 8 users anymore regarding re-occuring USB permission requests.
[Android Head-Units] royalhawk2002:
Thank you! Installed and worked only the first time. At first reboot started without asking permissions. Successive reboot (both cold and hot) asked permissions again.
[Android Head-Units] realzoulou:
Did you have the normal version installed at the same time? This was not an update, but it installs as completely separate app. Technically you can have both versions installed at the same time.
[Android Head-Units] royalhawk2002:
I have the old DAB + not from Google Play installed .

Before to install the version you provided here I disinstallled the Google Play version of DAB Z

Inviato dal mio SM-N960F utilizzando Tapatalk
[Android Head-Units] iMattmax:
[/COLOR]

I have the apk installed on my system and I delete the googleplay store app.

The question is still there, everytime I start the app.
[Android Head-Units] realzoulou:
What head unit do you have? Is it also a Xtrons Android 8?

I thought that the permission dialog only appears once after a reboot, not EVERY time when launching the app. Am I wrong?
[Android Head-Units] binar1:
I also have an xtrons android 8.0 it asks for permission every time, and I have to check the box as well, or the dialogue box pops up again untill I do.
[Android Head-Units] typos1:
You cant identify a head unit by the seller [MENTION=7838245]realzoulou[/MENTION] - Xtrons sell at least 2 different types of Android Oreo head units, made by 2 totally different companies, some are MTCD/E RK3368/PX5 units some are a different platform, so you need to identify them using MCUs.
[Android Head-Units] iMattmax:
My HU is an Erisin and the permission dialog appears every app start
[Android Head-Units] surfer63:
There is one thing to keep in mind here. You both mention the app asks permission at every app start.

1. Do you mean after you turn on the car/head unit and then every app start

2. or you open the app and it asks for permission, you close the app and re-open it again and it asks again permission.

1. The first is quite obvious. Only very few head units go into deep sleep (2~3 seconds functioning again). Most head units simply switch off (and take 20~30 seconds till functioning again). This means that when you switch on the car/head unit, it goes through a cold boot. That is the reason why it asks on every "app start", or actually head unit start and then app start, for the permission.

2. This is indeed a real issue if it behaves like that.

Please clarify whether it is 1 or 2.
[Android Head-Units] iMattmax:
I'm speaking about point 1.
[Android Head-Units] typos1:
No it isnt, Erisin are a seller, not a manufacturer, you need to quote your MCU.
[Android Head-Units] royalhawk2002:
I'm speaking about point 1. My MCU is 2.94 (latest). With "non Google Play" version never happened.
[Android Head-Units] binar1:
Point 1. But my head unit is coming out of sleep, not cold boot. Curiously, if I disable automatic start on USB device detection Dab-Z starts no problem but, the usb dialogue appears for Neutron music player.
[Android Head-Units] ZeroZorro:
I dont know if it helps narrowing down the problem but I can also add that when unit goed to sleep and it is waken short after (several seconds) it won't ask again for permission. When waiting let's say 20 seconds before waking up it will ask again for permission every time
[Android Head-Units] biker_955:
My HU does a warm boot on switch on, up in about 20 sec. With the app setting of autostart off, I get asked for permission every time I launch it.

With autostart on, I get asked once but the app starts with the HU (which I don't want)
[Android Head-Units] iMattmax:
Can you explain me how I do it?
[Android Head-Units] typos1:
Settings/about device/MCU version
[Android Head-Units] iMattmax:
I have updated the mcu, but the app still show every time the permission
[Android Head-Units] realzoulou:
I released 1.0.33 to Google Play. It has a new way to try to mimmick the "nousbdf" Version. It is still about enable/disable the general setting "Automatic start on USB device detection". Please give it a try. I am really running out of ideas.

Some might think why it is so difficult for me to re-create the nousbdf Version on Google Play. I honestly cannot really tell you. The main difference between the Google Play versions and the old ZOU-DAB versions are:

- Fully built from Java source in Android Studio instead of patching the smali code.

- Built against API 27 (=Android 8.1). This was the main source for all the sudden incompatibilities with Android 7 and 8. From November 2018 on, Google will no longer allow to upload apps to Play store that are not targetting at least API 26. The old ZOU-DAB was using target API 16 (=Android 4.1), so I cannot go back to this API level but still provide the app in Play store.
[Android Head-Units] masterhacka:
I have tested the new version and it seems to work. I had to completely reinstall the app (clear Data & Cache) because the app icon didn‘t appear. After that I can cold boot the device and close and start the app as often as I want and it didn‘t ask for permission except from the first start after the installation. I disabled the auto start on usb detection option in settings. The only thing I recognized was that when I quit the app and open another one (e.g. FM Radio) and then do a reboot, the FM Radio app will open but you can see the media buttons from DAB-Z in the notification center even the app is fully closed. But for me this doesn‘t matter. If you close the FM Radio app and open the DAB app also no permission is needed. So great work and thank you!
[Android Head-Units] karlos103:
Hi all

Just install the new version into my Xtron 8.0 android headunit ....but lot of the channels sound like they are in fast forward .

Radio 1 and 2 are fine , but a lot are terrible .

Old version never had a problem.

I have cleared cash , unistalled etc ...rebooted headunit ...but still same.

I only upgraded as was having permission issues .... now have audio issue lol

Ow and on a few radio stations it just crashes the app.

Any help most appreciated

Karl
[Android Head-Units] dextgod:
You this be used in the USA

---------- Post added at 08:38 AM ---------- Previous post was at 08:38 AM ----------

Could this be use in the USA
[Android Head-Units] rigattoni:
DAB+ is not provided in the US.

You need to use HD Radio or SIRIUS XM radio...
[Android Head-Units] IG_Vasilich:
Does that mean that the app won't work on older Androids (e.g. on Android 6.0.1 = API 23) ?
[Android Head-Units] binar1:
Same for me after installing the new Playstore version.
[Android Head-Units] karlos103:
glad its not just me having issues
[Android Head-Units] biker_955:
Looking good!

Had some issues when I updated it, my only option was UNINSTALL rather than OPEN. No DAB+ in the app list either

So I removed it and re-installed it. Re-set my favorites again. App permission poped up, clicked use by default. App started fine, unselected the autostart. Powered off a couple of times and it didn't autostart GREAT! and no pop-up

Will check again tonight when I go out and see if it returns.
[Android Head-Units] surfer63:
No, you specify a target-sdk and a min-sdk. min-sdk determines at what version it still runs.

In the old version min-sdk and target-sdk were both set to 16.

In the playstore version min-sdk =16 (4.0.1) and target sdk is set to 27 (7.0)
[Android Head-Units] realzoulou:
No, it will work from Android 4.1 on.

I am using it myself on Android 6.0.1
[Android Head-Units] biker_955:
The usb issue is fixed on mine at least. Many thanks for that.

Just got the no logo issue remaining.
[Android Head-Units] realzoulou:
Great!

Your no logo issue should have been fixed, too. At least I found a possible root cause and fixed that. Could you send me a logcat of such an occurance using the built-in functionality in Settings-Info tab?
[Android Head-Units] biker_955:
will do tommorow
[Android Head-Units] iMattmax:
The new version looks good. Till now I have no more permission questions. So, it works allright, thank you for your work
[Android Head-Units] OHP:
I've installed this on my extrons head unit (px5) and it seems to play the day stations in double speed any idea why it's doing this ?
[Android Head-Units] royalhawk2002:
The new version from Play Store looks working on my Xtrons PX5. Till now I have no more permission questions. I have only to check it in a cold boot. Thank you for your work

Inviato dal mio SM-N960F utilizzando Tapatalk
[Android Head-Units] biker_955:
OK logcat as requested

Was on for over 5 min with no logo showing. Shown in the list just not on the main window when playing.
[Android Head-Units] royalhawk2002:
At first cold boot I had an error message saying that the app was crashed. I restarted the app and it is working. I need to check again at next cold boot

Inviato dal mio SM-N960F utilizzando Tapatalk
[Android Head-Units] realzoulou:
What a strange log. Unfortunately, there is not the type of information in it that I wanted to see because your device seems to buffer logs from apps only for a quite short time.

I will see if I can find the root cause by code review.