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
Related
This might prove trivial, but I have not had success yet.
When I go to navigation mode, my display will dim after ~15 seconds (not turn off). Periodically, it will go back to the set brightness after ~30 seconds. This is while a charger is connected.
What setting do I change to cancel this behavior? I find it a feature when not connected to a charger or when not in certain applications.
....One thing to note and will likely work for me...
Testing in "Car Home" appears to resolve the problem.
Hey guys,
I have a fairly brand new (within the month) rooted GN II. The backlight fails to turn off after sometime for some odd reason. I have the backlight set to 15 seconds and Smart Stay off (aka all software options set to off). If I restart the phone, it seems to temporarily fix the problem until it happens later on somehow. Anybody know what could be causing this? Application?
PS- I havent soft/hard reset it yet.
Thanks
Some applications will keep the backlight on. Are you leaving a specific app when it happens?
imnuts said:
Some applications will keep the backlight on. Are you leaving a specific app when it happens?
Click to expand...
Click to collapse
Thanks for the reply! Not that I can think of. But wouldnt the phones hardware/software settings override any app? I think the only app I use on it is Skype?
Apps can request the android permission that allows the backlight to stay on constantly, think Navigation, the screen stays on the entire time you're navigating. Watching a movie or video does the same thing. It sounds like an app that has this permission not working properly and keeping the backlight on, but it's hard to tell. This would be why a reboot fixes it, because it would close the app.
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!
Hi
Tasker begginer here.
I'm having some minor issues with Tasker that I was hoping you could help me sort out:
I use Greenify and I was having a little problem with autohibernation feature in my unrooted Nexus 5: The screen has to turn on in order to automatically greenify something. This is a problem when the phone is in my pocket or facing down on the table because it conflicts with Gravity Screen (this app turns the screen off -and keeps it off- when the proximity sensor is active and the device is in a particular orientation), so when the phone is in my pocket or laying face down on a surface, Greenify can't finish its job because Gravity Screen will quickly turn the screen off.
In light of this, I disabled the autohibernation feature in Greenify and made a rather simple group of profiles to control it from Tasker. The main profile, the one that calls the "Hibernate now" shortcut from Greenify, is triggered when the screen turns off and has and If condition. This is the logic of that if:
- If
Proximity sensor: Not active
AND
Screen off
- Then
Run task
I do this to make sure that the hibernate action is not triggered while the screen is on or while the proximity sensor is active. Since Tasker doesn't have a variable for monitoring the proximity sensor, I made a profile that sets a variable (%PROX) to 1 when it's covered and 0 when its uncovered. So the if conditional uses the value of %PROX.
The problem is that if I turn the screen on WHILE the proximity sensor is active, Tasker skips the if statement (as it should), but if I turn the screen off with the proximity sensor uncovered and then cover it, it'll run the task. It's as if the profile that sets the variable %PROX to 1 does not work while the screen is off. Is this normal behaviour? How can I make this work better?
I managed to sort this out by deactivating Gravity Screen at the beggining of the task and reactivating it at the end (with a little waiting to give Greeenify time to finish), but I still want to keep my screen off while the phone is in my pocket.
My other doubt is regarding a group of profiles (that I got from here) that turn Wi-Fi on whenever I'm near two locations using the cell tower and Wifi near state in Tasker. I made some minor adjustments to these profiles, but they're still basically the same. The problem I'm having is that, most of the times, these profiles won't do anything if the screen is off. For example, I have it set to recognize cell towers near my house (and of course my Wifi connects automatically). Let's say I get home and I haven't used my phone in a while (screen off), I'd expect to see my Wi-Fi on and connected some time after I arrived, but this is not the case. It is not until I turn the screen on AND unlock the phone that I see the profiles doing their thing. I see wifi connecting, flash alerts and so on. This probably have something to do with the fact that, for some reason, my phone will not connect to a network while the screen is off. Same example, I get home with wifi on and the screen off, and I'll only see the wifi connecting after I turn the screen on (this happens with or without Tasker and with any wifi) regardless of how long I've been home.
Could it be that the near wifi profile cannot toggle wifi or can't recognize any network while the screen is off due to this bug I have with Wifi connections in my phone (Which I haven't been able to sort out)?
Thanks in advance and sorry for the long post!
Help with wifi profile
Hi, i saw your post in here and i think i can help, do you still have that problem or you managed to fix it? I think I might be able to help you
My Tab 4 turns itself on every night at specific time. I cannot figure out why, or what setting may be the culprit.
Every evening, I tap the power button to "sleep" my tablet before I put it in its cradle to charge. However, every evening at a specific time the tablet display lights up showing the lock screen, which wakes me up. This is making me nuts! I can't find any setting that would affect this behaviour, and there are no alarms set to "wake" the tablet at some specific time.
Any ideas where I should check?