(12-20-2019, 06:00 PM)AR105 Wrote: I will test your changes, but the bigger problem seems to me that changes in the system settings are "forgotten" during / after sleep mode.
.........
It works flawlessly on my Android 8.1 China phone - so there has to be a way that can also be done on the Joying device.
The difference between your Joying head unit and a phone (any phone), is that upon sleep mode "nothing" happens on your phone, but on the head unit almost all apps are killed, including their current "in memory" settings. If your unit does a cold boot, it looks at the Settings which are set for default boot volume and for default volumes for the several apps (actually the channels).
I also have a "No Kill" mod that prevents apps from being killed upon going to sleep. This will keep your apps in memory including your wanted settings and the like, as they were before deep sleep. Using the NoKill mod can have some other negative side effects, when using it with apps that place "wake locks". I do not know if Macrodroid does that.
Other options are to alter the fyt.prop and reflash the modified Allapp.pkg, alter com.syu.sys apk and add your specifi apps to the unkill_app.txt. All is described in several posts on XDA.
I do not know how to keep your current "in memory" settings in another way.
(12-20-2019, 06:45 PM)PCB-Tech Wrote: Interesting is, if no audio app is running, the voice is also almost not to be heard. Only if the AM/FM radio app is running in the background, the TTS voice is also audible.
Android knows different "channels" for audio. On Android, "media" apps use the media channel. The radio is not an Android app. It is a piece of hardware in combination with an analog or digital amplifier, normally unknown to phones. Joying (and all other brands) use a custom made audio switching on their head units to make the radio heard.
If you use media apps together with your navigation app, both use (in 90% of the cases), the same media audio channel. In this case the media player outputting constant (!) audio gets the focus, whereas the navigation app, sometimes outputting audio, has its volume level lowered. Actually the exact other way round as you want it.
If you use the radio, the media channel is "free" for your navigation app.
I have been using Mapfactor Navigator as well. As far as I can remember I set the output to one of the Bluetooth "phone call" options, as if it was an app on a remote BT-connected phone.
On all of these Chinese head units (on any head unit for that matter), BT "phone calls" always get preference over any other channel. Then it might work.
Note though that reall phone calls wait till the phone is picked up. Not all navigation apps are so sophisitcated that they wait 100~300 milliseconds (or so), before starting their output. Sometimes the first part of a navigation instruction might be cut off otherwise. Building up a BT phone call channel (which is 2-ways) simply takes some time.
But it remains a struggle. I only know and use navigation apps that use OSM data. It is always a trial and error in the navi app itself to check which output is best.
(a.k.a. surfer63 on XDA)