I am in the process of configuring Tasker for use in my vehicle to replace my aging CarPC with Nexus 7 2013(MMB29O/rooted). I am currently using Dashdroid as the front end. However, it seems tasker cannot completely kill the Dashdroid app. It still shows as open(when you click the square on the tablet) and not completely killed.
Tasker is set up as such:
Profile > Not Power Any > Tasks > Power Off > Kill App > Car Dashdroid (Use Root On)
Is there a better way to go about this? A way to shut down all apps and go to sleep, etc? Thanks!
Related
I wasnt sure where to post this as i am not sure whether the problem is with AOKP M5, Tasker, or Secure Settings.
I have a Tasker profile set to pop up a menu when i plug my phone in, and it has 4 different charging options. The task i have when i unplug the phone includes the following...
1. Secure Settings > GPS Disabled
2. Secure Settings > Location Services Disabled
3. Bluetooth > Off
4. Display Brightness > 75
5. Perform Task > Pandora Off
(Just in case)
the Pandora Off task includes...
1. Media Control > Pause
2. Go Home
3. Kill App > Pandora
4. Media Volume > 0
Now i have used all the same profiles and tasks on all the AOKP builds before this, and the problem started when i went to M5.
Here is where it gets weird...
When i unplug the phone, doesnt matter when, com.android.phone crashes. ALSO, when i open the actual Secure Settings app, it crashes there too.
Any tasker task that needs secure settings really will crash it.
I have updated Tasker, and i have updated Secure Settings and Helper. Unknown sources are checked, and Tasker and SS are set as admins in the security menu.
Edit: also want to mention the crash i get when opening the secure settings app happens whether the phone is plugged in or not.
Not sure what else to check. Thanks for any help.
now that i think about it it may be the theme. I am using natemz red theme. Didn't think to mention it because i thought themes were just graphical enhancements.
I found a couple other threads where themes caused similar issues.
Sent from my Galaxy Nexus using Tapatalk 2
FYI: The following requires root access but should work on all roms and kernels.
For anyone who uses Tasker, I've created a profile so that when you connect your headphones, it will run the music player and also set CPU Idle mode to Idle only. Then when you disconnect your headphones it will set idle mode back to idle + LPA.
Idle only mode fixes the crackling noise caused while the screen is off, however, it might result in higher battery drain (albeit negligible) when the phone is sleeping. To avoid this, the Tasker profile will switch idle mode back to Idle + LPA (which is default in the stock rom) when you don't need it anymore.
See the xml files in the zip file if you want to import them. Link to the zip file here: https://www.dropbox.com/s/vqt2fruwhcomdec/Tasker Headphones CPU Idle Mode.zip
The xml called "Tasker headphones profile" should be imported to the profiles tab. Everything else is a task.
If you don't want to import the xml files you can create the tasks and profile yourself by doing the following:
Create a Task called "Music + CPU Idle". Add the following actions to it:
App -> Load App -> Select the music player
Misc -> Run Shell -> In the command field put:
Code:
echo "0" > /sys/module/cpuidle_exynos4/parameters/enable_mask
Then ensure "use root" is checked.
Create another task called "CPU Idle LPA". Add the following action to it:
Misc -> Run Shell -> In the command field put:
Code:
echo "2" > /sys/module/cpuidle_exynos4/parameters/enable_mask
Then ensure "use root" is checked.
Finally, create a profile to combine these tasks:
Click + profile -> Optional Name -> State -> Hardware -> Headset Plugged -> Select the "Music + CPU Idle" task you just created.
Then long press the task next to the new profile and select "Add Exit Task" -> Select the "CPU Idle LPA" task you created.
You can test if this has worked by connecting and disconnecting your headphones and viewing the contents of /sys/module/cpuidle_exynos4/parameters/enable_mask with es file explorer or similar. You can also test it obviously by listening to music with the screen off and listening for crackling.
Sent from my Samsung Galaxy SIII via Tapatalk
Has anyone seen a wireless charging adaptor that comes with a connect that makes Android think it's on a dock. The situation I'm in is I use a wireless charging dock at work. I would love to set it so that when the adaptor is connected it will start the screensaver.
You can also start the screen saver automatically when the pixel is charged. Not only when it is in a dock.
Settings > Display > Screensaver > three dot menu > when to start screensaver
Sent from my Pixel XL using XDA-Developers Legacy app
Atomregen said:
You can also start the screen saver automatically when the pixel is charged. Not only when it is in a dock.
Settings > Display > Screensaver > three dot menu > when to start screensaver
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I thought of that. The only issue is my phone lays on my bed while I sleep. I would like a solution that doesn't require me to turn it off and on everyday.
I've never seen one. Logically I'm not sure how this would even be possible?
Maybe you could use something like Tasker to disable screensaver based on time of day or location.
Sent from my Pixel XL using XDA-Developers Legacy app
mims1979 said:
Maybe you could use something like Tasker to disable screensaver based on time of day or location.
Click to expand...
Click to collapse
Turning the function on or off depending on something like the home wifi network may be another way.
It looks like the following shell commands can turn the screensaver on or off:
settings put secure screensaver_enabled 1
settings put secure screensaver_enabled 0
To run a shell command with Tasker it's necessary to use root. Another way to do it without root is to grant permission to an app, such as AutoTools Secure Settings.
https://joaoapps.com/AutoApps/Help/...utotools.activity.ActivityConfigsettings.html
Is there anyway to get the theatre mode double press shortcut back? Having to pulldown and tap a small menu button is really bothering me.
Also tripple press for brightnes boost not working.
A must have on a sunny day.
Skickat från min SM-G950F via Tapatalk
I really miss the single tap waking the screen and putting it back into ambient mode. It allowed for turning my screen on and off without causing finger prints or possibility of undetected touch due to dry fingers. Palming the screen to turn off/enable ambient mode, used to intermittently result in onscreen actions being pressed like starting my stopwatch, or even worse stopping my stopwatch after I had just started it. I must have used single press of the button 100x per day. Now I have to actually wait for my screen to turn itself off. This alone has to half the battery life on the watch.
Double tap button for cinema mode was also a nice feature but I only do it once per day at night to save power so enabling through the swipe down menu isn't a big deal for me.
Worse is the three tap to turn on max brightness temporary. Today outdoor i Couldn't see my watch screen. Not seeing it also makes it impossible to enter brightness menu to increase brightness. I start to get more and more annoyed by 2.0 ?
Skickat från min SM-G950F via Tapatalk
I haven't tried it yet, but I saw this app, Wear Button Remapper, recommended on Reddit.
It says it can remap your button long press to any app, or to theater mode if your watch is rooted.
There are a ton of things that are frustrating, but I have figured out a way to cope with most of it.
For Do Not Disturb Sync, there is an app that restores this functionality.
https://play.google.com/store/apps/details?id=rkr.weardndsync
For theater mode, I setup a tasker task using autowear to run an app that allows toggling theater mode.
https://www.reddit.com/r/AndroidWear/comments/64qitr/toggle_theater_mode_on_wear_20/
I'm guessing that wear button remapper would allow us to enable theater mode without root using this app.
It's great that devs have developed apps to remap long press. Hopefully it won't be long before they can map double and triple tap to let us use the 1.5 theater and max brightness modes again.
irule311 said:
There are a ton of things that are frustrating, but I have figured out a way to cope with most of it.
For Do Not Disturb Sync, there is an app that restores this functionality.
https://play.google.com/store/apps/details?id=rkr.weardndsync
For theater mode, I setup a tasker task using autowear to run an app that allows toggling theater mode.
https://www.reddit.com/r/AndroidWear/comments/64qitr/toggle_theater_mode_on_wear_20/
I'm guessing that wear button remapper would allow us to enable theater mode without root using this app.
Click to expand...
Click to collapse
Whoa!! You DO Rule!
This is soooo frickin' awesome, I am just thrilled. I finally got one of the automatons I missed on AW 1.5 with Wear Shell. It took me a couple tries to get the task set. I use Sleep as Android and it supports Tasker but it would not trigger this app adding it to my existing profile, but just setting Toggle Theater Mode to run when Sleep runs did the trick!
Pkt_Lnt said:
Whoa!! You DO Rule!
This is soooo frickin' awesome, I am just thrilled. I finally got one of the automatons I missed on AW 1.5 with Wear Shell. It took me a couple tries to get the task set. I use Sleep as Android and it supports Tasker but it would not trigger this app adding it to my existing profile, but just setting Toggle Theater Mode to run when Sleep runs did the trick!
Click to expand...
Click to collapse
Yeah, there does seem to be some sort of glitch with the tasker autowear integration. I'm not sure what it is, but it seems to run the same autowear task even if you reconfigure it in tasker. The fix seems to delete the task and create a new one with a different name.
I use minimal and elegant as my watch face and was able to use the interactive functions to run the tasker task. I now have a button on the watch face that allows quick access to sleep tracking that enables do not disturb and theater mode.
You have to use SleepWear for the app name instead of start sleep tracking which makes it a little more difficult. Any ideas on how to find the app package name on wear?
irule311 said:
Yeah, there does seem to be some sort of glitch with the tasker autowear integration. I'm not sure what it is, but it seems to run the same autowear task even if you reconfigure it in tasker. The fix seems to delete the task and create a new one with a different name.
I use minimal and elegant as my watch face and was able to use the interactive functions to run the tasker task. I now have a button on the watch face that allows quick access to sleep tracking that enables do not disturb and theater mode.
You have to use SleepWear for the app name instead of start sleep tracking which makes it a little more difficult. Any ideas on how to find the app package name on wear?
Click to expand...
Click to collapse
I just made a second task that triggers on the Sleep app starting, so I have two tasks - one runs on the Sleep Start intent and the other to trigger your app via Auto Wear. It works great. If I do open the Sleep app during the day then I do get theater mode, but I'm fine with that to get the night time auto start. :good:
In an adb shell:
Code:
pm list packages -f
I can even pipe it through grep or more on my linux box which is good.
edit -
Code:
[email protected]:~$ adb shell
sturgeon:/ $ pm list packages -f | grep urbandroid
package:/data/app/com.urbandroid.sleep-2/base.apk=com.urbandroid.sleep
I have my new S9 on T-Mobile, and really like it. However, I keep getting notifications that the "app power monitor" has terminated sleeping processes. This sounds like something that Samsung is doing to "enhance" my Android experience *smile*. I'd really rather just use the native Android OS, rather than some Samsung monitoring facility that's most likely using more battery than it's saving. Is there a way to turn off the "app power monitor"? I looked for an app with that name and didn't find it, so they've probably got an app with a different name doing this.
I've already turned off the annoying notifications using the "Device Maintenance" settings tab -> Battery -> Advanced settings -> Notifications, but I assume that doesn't turn off the functionality. Nice not to have the notifications, but I'd really like to kill the whole thing *smile*.
Does anyone out there know how to turn off the "app power monitor" app/functionality?
Thanks!
Update: I believe that I've answered my own question. Now that I've turned off the notifications from the app power monitor, I believe that has also turned off the app power monitor itself. When I go into "Device Maintenance" -> "Battery", I now see the "App Power Monitor" section has been collapsed to a single setting to "Turn on" the app power monitor. So, oddly enough, turning off the notification for the app power monitor also turns off the functionality. These are usually orthogonal, notification settings and functionality, but in this case not so much.
Next time you get the notification, swipe right on it, tap the gear icon, scroll down and turn off "Apps consuming battery"