Here is an application to make specific programs(like ebook reader,SatNav etc) prevent standby when they are running. It will watch them even when they are in background, so be careful, if you just forget them running in the background, your phone will not go into standby. (v1.1 change: now you can disable background watch by checking "monitor active window only")
Installation:
1- Just install the latest cab file onto Device Memory and NOT Storage Memory.
2- You need .NETCF 3.5, if you don't have it, install it.
Usage:
1- If you will use background watching, find the executable name from Task Manager/Processes, drop .exe part, type it into textbox and click add. (AdobeReaderLE.exe -> AdobeReaderLE)
1a- If you want to watch only the active window (so that your battery doesn't drain if you minimize the whitelist app) Find the window title of the application (Either task manager/applications or just look at the title if it is not hidden) and insert it as above. (Adobe Reader LE this time) you can have both versions live together. There is one limitation to active application watching though, if the application doesn't report a window title in task manager, you can only background watch it. (e.g. htcreader)
2- if you want to remove a certain app, select its name and click remove button.
3- if you want to have KeepAwake open but still not active (to force into standby) click stop.
4- this app autostarts with each boot, if you don't like it, delete the shortcut under \Windows\Startup\KeepAwake.lnk
5- this app starts minimized. if you want to configure settings, select the icon one more time or switch to it using a task manager.
6- if you click quit, obviously the software quits and no more monitoring is done, so click X after configuring if you want it to monitor your apps.
7- if you want to turn off screen and lock keys (for listening to music maybe) you can click the lock button. If your app is running, the phone will still stay awake.
Tips:
1- You can map KeepAwake to a hardware button for easy access and screen locking.
Credits:
Thanks goes to Frank T. van de Ven for ProcessCE library.
Thanks a lot to DaveShaw for letting me use xdaShutdown application.
I'm pretty excited about this... I've been looking for something exactly like this to prevent specific standby times.
I hope it works with most of the applications I have in mind.
Any bugs? Would you guys find it useful to have a lock button so that it turns off the screen and locks keys but still keeps the device awake? I have implemented this for the latest version I'm using (to have my GPS logger going but preventing accidental touch on screen and keys.) Or is it better to keep it simple?
Will this also prevent Windows MSN not to idle which will cause lost connection too?
Sorry, I'm new to the WinMo scene, just saw this on Pocketnews. Let me get this straight, will this work for apps that run in the bg that don't close out IE:
Facebook
Google Maps
Email
Albums
etc.?
because they slow down my phone, I want to close them out completely, not run them in the background so they can take up valuable resources.
espaleena said:
Will this also prevent Windows MSN not to idle which will cause lost connection too?
Click to expand...
Click to collapse
I haven't specifically tried MSN app, but I see no reason it shouldn't work.
Raadius said:
Sorry, I'm new to the WinMo scene, just saw this on Pocketnews. Let me get this straight, will this work for apps that run in the bg that don't close out IE:
Facebook
Google Maps
Email
Albums
etc.?
because they slow down my phone, I want to close them out completely, not run them in the background so they can take up valuable resources.
Click to expand...
Click to collapse
I think you need a task manager so that you can close apps. This one is for making certain apps prevent the phone go standby.
ozkaya said:
Any bugs? Would you guys find it useful to have a lock button so that it turns off the screen and locks keys but still keeps the device awake? I have implemented this for the latest version I'm using (to have my GPS logger going but preventing accidental touch on screen and keys.) Or is it better to keep it simple?
Click to expand...
Click to collapse
I haven't given this a try yet, but any more additions are welcomed! This is something I've been looking for. I think it might be nice to give a way to put settings per application for standby perhaps (like some applications don't let the device go to stand by for 3 minutes, others are like 30 miuntes, etc). I think having't the screen off is a good addition, but keeping the device working is good, so things like voice recorder can work without having the screen on.
Seems to work well for IM services.
I haven't tested it completely for Opera and internet-browsing programs.
Nevertheless, this is a great idea.
new version is up..
What about on option... KEEP IT ON ? (Like LOCK)
This option would simply keep the phone ON, if the application is running in background even if we haven't listed anything
Is it possible? Maybe it's already included?
Thank you
Great app !
It doesn't work on my HD2. Youtube is running and my device locks and stops YT...
Any ideas??
Zepiii said:
What about on option... KEEP IT ON ? (Like LOCK)
This option would simply keep the phone ON, if the application is running in background even if we haven't listed anything
Is it possible? Maybe it's already included?
Thank you
Great app !
Click to expand...
Click to collapse
I thought about that but later decided that not many people would find it useful. if enough request comes, I will add it. In the meantime, you might just add an always running app like device or cprog into list manually when you want to keep it on always. or just minimize an app in the whitelist
Quider said:
It doesn't work on my HD2. Youtube is running and my device locks and stops YT...
Any ideas??
Click to expand...
Click to collapse
that's odd. I just tried and Youtube keeps itself open while playing a video for me even without this app. (Locks on the search screen) But still, KeepAwake seems to detect it when it is running. After installing have you clicked on the icon to run KeepAwake? Then minimized it by clicking on X? Have you tried another app, like Adobe Reader for instance? Is youtube minimized or active?
Hi,
Will this application disable lock option on device while using some application - eg. iGO Navigation?
Thanks
mdzepinajr said:
Hi,
Will this application disable lock option on device while using some application - eg. iGO Navigation?
Thanks
Click to expand...
Click to collapse
as long as you don't lock it yourself, yes, it won't be locked.
Very nice app...much thanks!
The app works for eReader on my Omni II running 6.3 One word of caution I have the x= app closed option turned on so the x shuts down keepAwake. It took me some time to figure out I was closing the app not minimizing it.
How would I go about disabling the standby while in a call? What's the name of the application I need to put in there? I'd like to use it so the sleep during call doesn't stop the call recording utility from working, but I still would like the screen turning off when keeping the phone at the ear.
Doesn't work on touch pro2
The software breaks error when we try to add software to the list, only with the program in background it goes to sleep anyways. It's a good idea, but not there yet...
Hopefully someone can help me out with this...been reading forums etc. for a while and can't find an answer..
Rooted HTC One m8. Tasker pro. Secure Settings free version. Running 5.0.1
I installed the helped for tasker (or whatever it's called now) and added a new task. Went to plugins >secure settings>gps and set for 'enabled'. When I test the task, it gives me nothing. I trying setting a shortcut to see if that might work and same result as the test. When I go into tasker and click 'test action' it says 'executing action' and it works. However, as soon as I try just clicking the play button,nothing. No clue what else to try, any help would be greatly appreciated.
Same Issue with Llama Locale + Secure Settings
Kevinj17 said:
Hopefully someone can help me out with this...been reading forums etc. for a while and can't find an answer..
Rooted HTC One m8. Tasker pro. Secure Settings free version. Running 5.0.1
I installed the helped for tasker (or whatever it's called now) and added a new task. Went to plugins >secure settings>gps and set for 'enabled'. When I test the task, it gives me nothing. I trying setting a shortcut to see if that might work and same result as the test. When I go into tasker and click 'test action' it says 'executing action' and it works. However, as soon as I try just clicking the play button,nothing. No clue what else to try, any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm running Exodus 5.1.1 on my OnePlus One. In Llama with the Secure Settings plug in, when I test and activity to toggle GPS to High Accuracy Mode when Maps or Waze is launched, the test works flawlessly. When I actually launch Maps or Waze though, the action never triggers and remains on GPS Battery Savings Mode.
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.
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
m0d hipp¥ said:
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
Click to expand...
Click to collapse
After your OS finishes booting and loads the full OS stack, a system-wide message called Broadcast Intent will be sent to all apps, notifying them that your device has completed booting (this intent is called BOOT_COMPLETED). Then it's up to the individual app to use that broadcasted intent to pre-load in memory whatever they want (or simply not react at all).
The thing is you want to delay auto boot for that specific application, so there are 2 options for that:
you turn off auto boot in the App itself (if it provides such an option).
you block the app from receiving the intent broadcasted.
The second option is also achieved either by using a task killer to force kill the app (which defeats your point IMO) or it manipulate the app from receiving the intent entirely. Both of these options require root access.
If you have root I suggest The App: SD maid (pro version). Under app control you can modify which system Broadcasts that Keymapper recieves (among them could be boot_completed). See attached screenshot from my device for example.
Hope I helped somehow
Thank you for your response. That was super helpful! The device I am playing around with is a Mekotronics R58x, and it had some sort of modified root that was conflicting with Magisk. I read somewhere on these forums that someone suggested renaming the su file if it exists in /system/xbin/su; which it did. I renamed it and rebooted and after that everything worked wonderfully. Keymapper was still autobooting like previously, but this time all the services loaded right up and I didn't have to restart the app it just worked.
Basically I think the issue was this custom su file that was conflicting with Magisk and causing a headache with the keymapper. I'm glad I stumbled across the fix, but either way your post was also very helpful! Thank you!