has anyone found a way to keep Tasker alive on resume.. when restating it starts ok, but when it resumes tasker is not resumed automatically..
Nomader0 said:
has anyone found a way to keep Tasker alive on resume.. when restating it starts ok, but when it resumes tasker is not resumed automatically..
Click to expand...
Click to collapse
What kind of hu?
Thanks an MTCD of course
I managed to whitelist it along other apps using MTC Manager xposed module on Malayks ROM. It is kept alive and kicking on sleep..
Nomader0 said:
Thanks an MTCD of course
I managed to whitelist it along other apps using MTC Manager xposed module on Malayks ROM. It is kept alive and kicking on sleep..
Click to expand...
Click to collapse
Hi.
Same problem here - could you write down the steps you made so i can give it a try?
Thanks
there is a whitelist.ini file (that is of you coppied the MTC Manager files like Malaysk says to do) inside you can just write down the tasker process (net.dinglisch.android.taskerm). it will be kept alive during sleep
while you are there also add poweramp process (com.maxmpz.audioplayer) (that is if you are using poweramp)
that will make poweramp resume playing automatically when resuming from sleep.
anyone know how to do this without xposed? PX5 units doesn't have xposed support yet.
I haven't found a way. I've been through every APK in /system looking for the task killer, no luck at all
Sent from my 2PS64
Hi,
I don't have a fix, but a short-cut. I've set a homescreen widget to launch a Tasker Task (which can just be a pop-up saying "Tasker is now running"), that way when I start up the unit it's one tap on the homescreen, Tasker loads, runs the task, and then remains in the background. This does save you opening the Tasker app and then backing out again.
This initial task can also be used to load up other items you'd rather have running all the time (I'm using Twilight and GMD Immersive) - if you do this it's worth putting in a slight delay between each (I've gone for 500 MS) and then launching the Home app as the last item to put you back where you were.
Ideally I'd want Tasker resuming after sleep, but until that's an option "one tap and it's there" will have to do.
Hi there,
maybe someone read it in the PX5/Malaysk Thread about my question regarding Tasker recognizing the shutdown/"sleep" command, but maybe I've a little more luck in this forum
So...
Is there a intent signal, which I can use in Tasker for recognizing the switched ignition signal (which ends in shutdown/sleep of the head unit)?
I think there has to be a signal/command, as android itself gets it for going to shutdown.
Background for my question:
I want to use PowerAmp, but it doesn't save the track position after switch off.
Actual solution:
I connected an active usb-switch, which has only the data signals from USB to the head unit. The switch is powered by the ignition signal, so at least I can trigger a disconnected usb-device and pause PowerAmp.
But this needs little hardware modification and I hope, that I can use it with a software solution.
Thanks for your help
Shadow128 said:
Hi there,
maybe someone read it in the PX5/Malaysk Thread about my question regarding Tasker recognizing the shutdown/"sleep" command, but maybe I've a little more luck in this forum
So...
Is there a intent signal, which I can use in Tasker for recognizing the switched ignition signal (which ends in shutdown/sleep of the head unit)?
I think there has to be a signal/command, as android itself gets it for going to shutdown.
Background for my question:
I want to use PowerAmp, but it doesn't save the track position after switch off.
Actual solution:
I connected an active usb-switch, which has only the data signals from USB to the head unit. The switch is powered by the ignition signal, so at least I can trigger a disconnected usb-device and pause PowerAmp.
But this needs little hardware modification and I hope, that I can use it with a software solution.
Thanks for your help
Click to expand...
Click to collapse
I have no first hand knowledge of the MTCD units. I have been no stop researching them for the past week, as I would like to upgrade but need to keep the functions I had with MTCB.
Can you please try these intents and see if they work?
com.cayboy.action.ACC_ON
com.cayboy.action.ACC_OFF
Based on other information, I believe there could be a spelling error. Please try this variation too.
com.carboy.action.ACC_ON
com.carboy.action.ACC_OFF
Thanks,
Thanks for your first help, but it doesn't seem to work.
I created a task which is triggered by incoming Intent, and I tried every four combinations.
But never triggered.
But maybe I also need some parameters in it?
Or maybe there is a possibilty to log all these events?
Shadow128 said:
Thanks for your first help, but it doesn't seem to work.
I created a task which is triggered by incoming Intent, and I tried every four combinations.
But never triggered.
But maybe I also need some parameters in it?
Or maybe there is a possibilty to log all these events?
Click to expand...
Click to collapse
Do these even work? I hope we can find a working solution for this
android.intent.action.SCREEN_ON
android.intent.action.SCREEN_OFF
Just to confirm. Tasker is on whitelist to not sleep? Using Graser's dasaita tool or some other method.
carter.w.jason said:
Do these even work? I hope we can find a working solution for this
android.intent.action.SCREEN_ON
android.intent.action.SCREEN_OFF
Just to confirm. Tasker is on whitelist to not sleep? Using Graser's dasaita tool or some other method.
Click to expand...
Click to collapse
I hope also, that there's a solution. Can't believe, that only the internal MP3 Player is working without any problems
Tasker is not going to sleep as I put it into settings.ini.
I think that should be enough
I tested the intent for Screen_Off, but also not working :/
I tried also the internal Screen detection of Tasker, and also no success.
As I understand correctly from a logcat log, the systems first shows the shutdown window, that it unmounts the sdcard and then it switches off the screen.
So for correct working the pause signal for PowerAmp should be received during shutdown windows and unmounting the sdcard.
But is there a possibility to check a pop-up window
But question before.
Do I need any extra options for the intents inside of Tasker?
One more thing, what is curious.
It seems, that the most important function of the internal MP3 is the prevention of unmounting the sd-card while playing and switch ignition
Do I need any extra options for the intents inside of Tasker?
Click to expand...
Click to collapse
No other options needed for this.
I tested the intent for Screen_Off, but also not working :/
Click to expand...
Click to collapse
I'm puzzled on that. I wonder whats going on?
I've just ordered a PX5 unit, so I'll be able to experiment soon.
Yeah, thats cool. Maybe you've more luck on it
For me it's horrible at the moment. One problems come to another.
Yesterday I'd a working solution with hardware modification, and then I tried the CD Player of the radio.
That was not working, as I'd to freeze the internal MP3 Player of the system
I also tried to put android storage manager on whitelist, without succes.
Poweramp starts by xposed MTCDManager and wants to play right after startup, but the usb-stick isn't ready at this time and I get message that the track wasn't found. A few seconds later I can start by push play, but trackposition is gone.
Has someone maybe any idea?
springstil said:
I also tried to put android storage manager on whitelist, without succes.
Poweramp starts by xposed MTCDManager and wants to play right after startup, but the usb-stick isn't ready at this time and I get message that the track wasn't found. A few seconds later I can start by push play, but trackposition is gone.
Has someone maybe any idea?
Click to expand...
Click to collapse
At the moment I've got my MP3s on internal storage, and then PowerAmp can play the tracks with kept trackposition.
But.... everytime after switch on the sound is scrambled, so I've stop stop and restart playing
Not a good solution
Okay. I will test it with music on sd-card instead of the usb-stick. If that doesn't help I will have to live with that push on play I think
I have no more idea and googled for a week now, without success.
springstil said:
Okay. I will test it with music on sd-card instead of the usb-stick. If that doesn't help I will have to live with that push on play I think
I have no more idea and googled for a week now, without success.
Click to expand...
Click to collapse
I have a Eonon GA2170 running Malaysk 8.0 version 1.1. Since I want to be able to easily add new music and I don't want to completely fill my head units internal storage, I have my music on a 32gb sd card. I too struggled with getting PowerAmp to play nicely with sleep mode on the Android head unit. But after much trial and error I was finally able to get it to a point to where it is about 90% working to my satisfaction. I've been tied up the last 2 months, so I haven't been able to address last issue.
Instead of trying to remember everything off the top of my head, I'll try to let you know how I have everything setup when I get home tonight.
With my current setup:
If PowerAmp was playing when ignition turned off, song will continue at correct spot when ignition turned on.
If radio was playing when ignition turned off, radio will start when ignition turned on.
The issue I need to resolve is:
If you play music via PowerAmp, then switch to the radio before turning off the ignition. The radio will start when ignition turned on, as it should, but about 15 seconds later PowerAmp will start and you have to manually switch back to the radio.
albtross said:
I have a Eonon GA2170 running Malaysk 8.0 version 1.1. Since I want to be able to easily add new music and I don't want to completely fill my head units internal storage, I have my music on a 32gb sd card. I too struggled with getting PowerAmp to play nicely with sleep mode on the Android head unit. But after much trial and error I was finally able to get it to a point to where it is about 90% working to my satisfaction. I've been tied up the last 2 months, so I haven't been able to address last issue.
Instead of trying to remember everything off the top of my head, I'll try to let you know how I have everything setup when I get home tonight.
With my current setup:
If PowerAmp was playing when ignition turned off, song will continue at correct spot when ignition turned on.
If radio was playing when ignition turned off, radio will start when ignition turned on.
The issue I need to resolve is:
If you play music via PowerAmp, then switch to the radio before turning off the ignition. The radio will start when ignition turned on, as it should, but about 15 seconds later PowerAmp will start and you have to manually switch back to the radio.
Click to expand...
Click to collapse
I´m looking forward hearing from you.
That would be really great if it would work with Poweramp. The issue you have with radio, I could live with that. I rarely hear radio, most of the time my music from usb is playing. But I have a lot of mixes with over 1 hour playtime, driving to work for 30 minutes and every time hearing the first 30 minutes of the track is really annoying.
I have a Dasaita HA2317-V840 running Malaysk 8.0 v1.1, too.
albtross said:
With my current setup:
If PowerAmp was playing when ignition turned off, song will continue at correct spot when ignition turned on.
If radio was playing when ignition turned off, radio will start when ignition turned on.
Click to expand...
Click to collapse
Now the question is, do you've something special configured to use it like this (especially only Poweramp)?
And does it work with using from SDCard?
It's been a while since I looked at this so I had to refresh my memory. The good news I that I now think I know why I'm seeing the issue I mentioned above. Hopefully I'll get a chance to look into it this weekend.
MTCManager un-mounts external storage devices when the head unit goes to sleep. If PowerAmp has been white listed, then it will try to resume playing before the external storage device can be re-mounted. Which, as you have found, causes 2 issues. The 1st being that the music will not auto start when the ignition is turned on and the 2nd being that PowerAmp forgets the current track position.
Step 1:
To prevent PowerAmp from try to play a song on an un-mounted device, remove PowerAmp from the whitelist and allow MTCManager to kill PowerAmp when the head unit goes to sleep. MTCManager will automatically restart the app that was in the foreground when the head unit was put to sleep. Turns out that on my head unit, the storage is mounted by the time PowerAmp comes up. This slightly delays the playing of music for 2-3 seconds when you turn the ignition on, but it is hardly noticeable.
Doing this exposed another issue. If PowerAmp is force killed, it does not get a chance to save it's current track position, so it restarts at the beginning of the track.
Step 2:
Have Tasker pause PowerAmp as soon it detects that the head unit is going to sleep. This allows PowerAmp to save its current track position before being killed.
Event:
Intent Received (Action: com.microntek.bootcheck)
Task:
If %class ~ poweroff
Send Intent (Action: com.maxmpz.audioplayer.API_COMMAND, Extra: cmd:2)
End If
Note that works for PowerAmp 2. PowerAmp 3 will require a different intent.
This is probably all you need, if you are not concerned about restarting PowerAmp if it was in the background when the head unit goes to sleep. It appears that MTCManager restarts the foreground task up on waking up, but none of the non-MTC background task are restarted. So if you were playing music via PowerAmp and then switched to Google Maps before turning the ignition off, Google Maps would automatically restart when the ignition was turned on, but PowerAmp would not.
Step 3:
I wanted to handle restarting PowerAmp with Tasker so that I would have full control, but haven't had time. Since MTCManager takes care of restarting the MTC Music player when the head unit wakes up, I decided to let it restart PowerAmp instead. I ended up doing a search and replace of the mtcmanager smali files. I replaced com.microntek.music.MainActivity with com.maxmpz.audioplayer.PlayerUIActivity and com.microntek.music with com.maxmpz.audioplayer.
This has the added benefit of including PowerAmp in the applications that get cycled through when pressing the Mode button on your steering wheel remote.
I hope this helps.
Sounds very good!!!
I'll try it the next days
But one question:
This works only on Android 6.0 as you're using MTCManager?
albtross said:
It's been a while since I looked at this so I had to refresh my memory. The good news I that I now think I know why I'm seeing the issue I mentioned above. Hopefully I'll get a chance to look into it this weekend.
MTCManager un-mounts external storage devices when the head unit goes to sleep. If PowerAmp has been white listed, then it will try to resume playing before the external storage device can be re-mounted. Which, as you have found, causes 2 issues. The 1st being that the music will not auto start when the ignition is turned on and the 2nd being that PowerAmp forgets the current track position.
...
Click to expand...
Click to collapse
Hi albtross,
today I tried to test your configuration, but had no success
My steps:
1. Removed "com.maxmpz.audioplayer" from settings.ini (/sdcard/mtce-utils)
2. Created tasker profile for PowerAmp (attaced as screenshots)
3. Extracted MTCManager.apk and replaced "com.microntek.music.MainActivity" with "com.maxmpz.audioplayer.PlayerUIActivity" and "com.microntek.music" with "com.maxmpz.audioplayer" in every .smali file (at least 4 files)
4. Re-compile with APKTools and put modified MTCManager.apk back to Head Unit
Test:
During playing a MP3 from a SDCard I switched off and it goes to standby. After switching on PowerAmp starts directly, but I got the message "Folder is missing or unreadable" from Poweramp.
I tried also to configure Tasker to the Whitelist, but same behavior.
Maybe you've an idea what is wrong?
Or maybe you can upload your tasker profile?
Thank you so much
Shadow128 said:
Hi albtross,
today I tried to test your configuration, but had no success
My steps:
1. Removed "com.maxmpz.audioplayer" from settings.ini (/sdcard/mtce-utils)
2. Created tasker profile for PowerAmp (attaced as screenshots)
3. Extracted MTCManager.apk and replaced "com.microntek.music.MainActivity" with "com.maxmpz.audioplayer.PlayerUIActivity" and "com.microntek.music" with "com.maxmpz.audioplayer" in every .smali file (at least 4 files)
4. Re-compile with APKTools and put modified MTCManager.apk back to Head Unit
Test:
During playing a MP3 from a SDCard I switched off and it goes to standby. After switching on PowerAmp starts directly, but I got the message "Folder is missing or unreadable" from Poweramp.
I tried also to configure Tasker to the Whitelist, but same behavior.
Maybe you've an idea what is wrong?
Or maybe you can upload your tasker profile?
Thank you so much
Click to expand...
Click to collapse
The settings.ini file whitelist does not currently work on Malaysk. The only way to prevent apps from being killed is by editing the mtcmanager apk. See https://forum.xda-developers.com/an...to-whitelist-packages-mtcd-head-unit-t3765437. PowerAmp is hard coded in mtcmanager.apk, so it must be removed from the c.smali file. I just changed "com.maxmpz.audioplayer" to "com.was.audioplayer".
Try renaming your /system/priv-app/MTCManager/MTCManager.apk to MTCManager.apk.orig and placing the attached file into the same directory.
albtross said:
The settings.ini file whitelist does not currently work on Malaysk
Click to expand...
Click to collapse
OK, that explains it.
Your HowTo is for Android 8.0 and not 6.0?
But no problem, I'll test it on Android 8.0 with your modded apk
Shadow128 said:
OK, that explains it.
Your HowTo is for Android 8.0 and not 6.0?
But no problem, I'll test it on Android 8.0 with your modded apk
Click to expand...
Click to collapse
I've never had 6.0, so it was written for Android 8.0.
As in the title. Is this possible to do on Android head unit.
As we know we have various different physical button options and ways to link steering buttons to different apps. But as far as I know there isnt a way to shuffle running apps to bring them to the front or in focus with just 1 simple button (steering).
As we know using our phones we can press the left list button on our phones and scroll through recent apps and select the one we want to use to bring it back into focus. Well I generally have less than half a dozen main apps I might use any one time in the car and its a bit of a faff doing this with the screen. Id rather do it with just any easy dedicated button. And possibly assign the apps I want to switch between such as navi, radio, music, phone etc.
So can this be done ?
Its already done. I got a pumpkin px5 that has a mod button where in hal9k rom i set any numbers of apps i want and i scroll with that perfectly. Also i had assign for it a steering wheel button that works also fine.
I highly recommend the Hal9k rom as well. It does exactly what you want.
If you don't want to flash a new rom though I did this originally by using an app called MTCD Tools. I don't have a link but it's mentioned a lot in here.
I ended up using a combination of that and Tasker to get apps like Spotify or Pocketcasts to start playback automatically at different volume levels when cycled to.
But again, much less effort with Hal9k
Thanks guys, i thought perhaps mtcdtools might do it. But it is a bit scary as i dont understand most of it.
Good to no its possible tho. The more I think about it the more I like the idea.
Ive only just installed malaysk's rom which is very good + all my other apps so dont really want to wipe n flash again just yet. Did you also use Malaysk rom or go straight to Hal9k. I thought they were much the same.
I did install at 1st malaysk but it was too altered for my taste because i like just root and some extra options and hal9k rom fit the bill perfectly.
You sure malaysk doesn't have this option? Better ask in malaysk thread if you don't find it.
Yes I could do. Where did you find it in Hal9ks rom. Is it under settings?
Yes
Settings -> mod settings-> apps that cycle throw mode button.
If i remember right the last setting
Three questions in this one.
1. In my config.txt there is an entry:
ro.fyt.splitscreen=0
Can anyone confirm what it does? I have attempted value of 1 and 2 (assumed it may not have been binary) but there is no result. I was hoping that it would force a split screen to stay a split screen when awakening. I have looked in the skipkillapp.prop but didn't see anything particularly relevant.
2. Continuing on from question 1, I have attempted to use Macrodroid to create a split screen which worked under Macrodroid test conditions but I cannot find a trigger that will run the macro in real life scenarios. I have attempted triggers of power on, screen on, wake from sleep, charging on and a few others. I have my Headunit set to sleep in factory settings. I could probably get the trigger to piggyback off my bluetooth connection to my phone but I would like something more instant. Does anyone have success in getting Marcodroid to trigger from a head unit screen on / wake up when the car powers up?
3. In the config.ini there are mic vol and mic level. What is their role in that file? They don't seem to overwrite the config.txt values for mic as changes in config.txt for mic change mic response. There is also reference to GOC-Android in Config.ini... Any ideas?
ludditefornow said:
Three questions in this one.
1. In my config.txt there is an entry:
ro.fyt.splitscreen=0
Can anyone confirm what it does? I have attempted value of 1 and 2 (assumed it may not have been binary) but there is no result. I was hoping that it would force a split screen to stay a split screen when awakening. I have looked in the skipkillapp.prop but didn't see anything particularly relevant.
2. Continuing on from question 1, I have attempted to use Macrodroid to create a split screen which worked under Macrodroid test conditions but I cannot find a trigger that will run the macro in real life scenarios. I have attempted triggers of power on, screen on, wake from sleep, charging on and a few others. I have my Headunit set to sleep in factory settings. I could probably get the trigger to piggyback off my bluetooth connection to my phone but I would like something more instant. Does anyone have success in getting Marcodroid to trigger from a head unit screen on / wake up when the car powers up?
3. In the config.ini there are mic vol and mic level. What is their role in that file? They don't seem to overwrite the config.txt values for mic as changes in config.txt for mic change mic response. There is also reference to GOC-Android in Config.ini... Any ideas?
Click to expand...
Click to collapse
For 1): Sorry to give a non-helping answer here, but I don't know either. I wondered about that one myself and also searched 4pda extensively, but can't find anything.
2) This will not work. As of Android 10 apps are not allowed to do a split-screen, only the user him/herself. It is a new security feature. (And then adding to 1): Maybe the ro.fyt.splitscreen still worked on the sc9853i Android 8.1 versions. I will get my device back on power on the bench.)
3) config.ini? Which config.ini? I searched the latest Joying and Mekede firmware and can't find a config.ini.
surfer63 said:
For 1): Sorry to give a non-helping answer here, but I don't know either. I wondered about that one myself and also searched 4pda extensively, but can't find anything.
2) This will not work. As of Android 10 apps are not allowed to do a split-screen, only the user him/herself. It is a new security feature. (And then adding to 1): Maybe the ro.fyt.splitscreen still worked on the sc9853i Android 8.1 versions. I will get my device back on power on the bench.)
3) config.ini? Which config.ini? I searched the latest Joying and Mekede firmware and can't find a config.ini.
Click to expand...
Click to collapse
1. You were helpful. You confirmed to me that the info is not easily obtainable. I've several hours that I have spent today looking for this and learning other things andf made a list of items where I need to learn and research more. This item will now go further down the list. So thank you.
2. It does work already when I trigger from within Macrodroid. The issue is that I can't find an auto trigger in macrodroid what works when I turn on a screen. For a moment forget that I want split screen. I just want Macrodroid to dop *something* when the screen comes on when I start the car.
I can't find what turning on the head unit triggers in macrodroid. Something must happen in the head unit OS that macrodroid can see, I would have thought.
3. I think I have answered this one already. Theshortcut was found in oem/apps. The config seems to be denoting what server or service it should look for for certain info. I have translated the chinese text and it makes sense now.
Attached is the config.ini with chinese characters and then below the end is the translated to english.
I'll put this here more for a reference for me.
thanks for replying.
ludditefornow said:
3. I think I have answered this one already. Theshortcut was found in oem/apps. The config seems to be denoting what server or service it should look for for certain info. I have translated the chinese text and it makes sense now.
Attached is the config.ini with chinese characters and then below the end is the translated to english.
I'll put this here more for a reference for me.
thanks for replying.
Click to expand...
Click to collapse
Thanks.
It must be created or copied somehow at the moment of flashing, or first boot or maybe on every boot. I can't find it in any of the partitions in the firmware.
When I look in the firmware system.img (system.new.dat.br) it is a symlink to "config.ini -> /oem/config.ini", but the oem is freshly created on flashing and than "filled" with the AllAppUpdate.bin apps.