Hello all, I have trigger setup to automatically turn on my lockscreen with a pin when I plug it in to charge, as sometimes people get nosey while you sleep. I was wondering if either app or perhaps some other one has a way to automatically turn off the lock screen notifications at the same time the phone locks, and then when my other trigger to disable the lock screen (when my phone connects via bluetooth to my truck) it could turn them back on?
Anyone know if this is possible?
Thanks!
Related
I know it's something to do with the dock, but I don't know what service I can freeze to stop this behavior. If I've rebooted the phone and used it for whatever length of time, it will go to sleep at the time I've set for the screen to go off. If I plug it into the dock, the clock comes on as expected. If I then remove it from the dock, it won't go to sleep. The screen will dim but only remain dimmed.
I've tried to use TiBackup to freeze whatever says dock, but it doesn't seem to work. Anyone know how to stop this?
I'm looking for a possible app that can automatically lock the phone regardless of what it is doing. I use the MHL to HDMI cable to output to my tv when I'm in bed and I like to watch shows to put me to sleep.
The thing is when the cable is plugged in, the phone's screen never turns off because it would turn off the tv display as well. The display just goes dim when it's idle. I can manually lock it and it will shut off, but I would like something that can send a lock command or a power off command after a certain amount of time, sorta like a sleep mode.
I don't like having my phone screen's stay on until morning even though it's staying fully charged. It's usually pretty warm when I wake up. Is there any way this can be done?
Maybe it could be done with tasker? https://market.android.com/details?id=net.dinglisch.android.taskerm&feature=search_result
I gave it a try and it seems like a really nice app, but I couldn't find a way to command it to lock or turn off the phone. There were 2 options I saw called "lock" and "system lock" and I tried both but nothing happened when the specified event occurred.
I'm tempted to try the HDMI on my Galaxy Tab 10.1, but I'm thinking it would remain on as well if plugged in. Thanks for the suggestion though.
Ok, I have a voice changer app that I want to use with the screen off. Ideally I'd start the app, turn on real-time processing, then turn the screen off. Currently, it only runs when the screen is on, as soon as I turn the screen off the app stops all voice processing. Screen needs to be off so the battery will last longer, and so the settings can't be changed accidentally (so touch has to be disabled as well).
I either need the app to keep running in the background, or have the screen turn off but not actually locked (I dunno the right term, but if the screen was off and didn't accept touch input, but the phone thought the screen was on...that'd be fine).
Closest I've found is to edit the AndroidManifest.xml file to set it persistent, then make it a system app. This will take me a while to figure out, and not even sure it'll work.
Is there some simple solution I'm overlooking? I've seen an app that turns off the screen with help from the proximity sensor...but I want the screen off whether it's in my pocket or lying on top of a table.
Edit: I tried some apps that use the proximity sensor to turn off the screen; as soon as the screen goes off, the voice changer app just stops. I have no idea what's triggering it (if the phone is actually entering a sleep state, or if the app is specifically watching for the screen to go off and suspends itself). Thought that might be a workaround, but nope.
UPDATE: CapnPez's suggestions seems to have worked. Screen on/off needs to be set as an event, not a state!
Thanks for the help!
My setup:
Rooted
Running SnowJB 1.1
Tasker Installed...no profiles or task setup to toggle the Bluetooth radio. Do use a Screen On/Off state profile to turn on Wifi/Data/Gps/NFC when screen is on. When screen is off, they are all off. Also have Secure Settings plugin installed to toggle NFC and GPS.
NFC Task Launcher installed...Only one tag exists for my "car mode". When I place the phone in the car dock it launches CarHome Ultra
CarHome Ultra installed....turns on BT when it launches.
So with all of this setup, let me explain the issue. When I place the phone in my car dock and turn the screen on, NFC radio should turn on, NFC task launcher should then read the tag in the car dock which launches CarHome Ultra. CarHome Ultra turns on BT when it launches.
What has been happening lately is when CHU launches, the bluetooth starts toggling on and off VERY rapidly. I can see the BT toggle icon in the notification power bar flashing or blinking. Pressing the BT icon does nothing. Closing CHU does nothing. I have to restart the phone to get out of this strange blinking loop. I have frozen/uninstalled Tasker and everything seems to behave as designed. However, I reinstall tasker, DO NOT CREATE ANY BT TOGGLE ACTIONS, and the blinking BT returns.
Has anyone experienced similar behavior?
I'm not sure if this is the problem, but my first thought is that you mentioned that you are using the screen on STATE. Perhaps you should use the screen on EVENT. What it might be doing with the state is that it checks that the screen is on and toggles your wifi/data/gps/nfc and the turned on nfc now detects the tag again and then tries to re-turn on your bluetooth. It might be doing this each time it detects that you are still in that state (as quick as the interval it takes to recheck that state). With an event, it should just trigger once.
This is my first guess, but it might be worth a shot to change it to the event. I may be mistaken with what Tasker is doing when it is in the state. Good luck and I'll keep thinking what else it might be (there are others out there who are better Tasker Gurus than I).
Thanks, I have made this change and will give this a try. It's strange that the thing most affected is the Bluetooth and I have no Tasker profiles set up to toggle the BT radio.
CapnPez said:
I'm not sure if this is the problem, but my first thought is that you mentioned that you are using the screen on STATE. Perhaps you should use the screen on EVENT. What it might be doing with the state is that it checks that the screen is on and toggles your wifi/data/gps/nfc and the turned on nfc now detects the tag again and then tries to re-turn on your bluetooth. It might be doing this each time it detects that you are still in that state (as quick as the interval it takes to recheck that state). With an event, it should just trigger once.
This is my first guess, but it might be worth a shot to change it to the event. I may be mistaken with what Tasker is doing when it is in the state. Good luck and I'll keep thinking what else it might be (there are others out there who are better Tasker Gurus than I).
Click to expand...
Click to collapse
Hi all,
So if you are on Android 4.2+, you may already know the feature called Daydream, which is essentially a screensaver that activates when the phone is docked or charging. I'm very fond of how minimalistic the screensaver clock is, and I would like to put my phone in this Daydream mode and wrap it on my wrist so that it acts as a low power "smart watch".
Question is, I can't seem to figure out how to keep Daydream awake without having to keep the phone plugged in.
1. I used various "wake lock" apps that can keep screen awake in regular cases, but they all don't work in Daydream.
2. I tried an app named Car Mode Enabler which sends a sticky "car mode" intent. The phone thinks it's docked and goes into Daydream, but it would still shut the screen after some time.
3. I tried to find an app that sends charging intents (so as to simulate a charging behavior) but to no avail.
So can anyone get me out of this? You can either tell me how to make Daydream stay on, or even better, tell me if there's an app that functions like Daydream (white clock on black background, with system font). Thanks in advance!