Hello,
I installed Endomondo on my Gear fit, but it drains my battery. Is there any possibility how to turn display off after some time and turn it on only when I do a wrist movement? Or something like that? Because endomondo is having display still on and even when i turn it off by button, it turn it back on when the circuit notification shows (which is every kilometr = 2 minutes on bike).
Thanks for respond.
Neonik!
I found out, that when endomondo is "not running" - paused or stopped, display it turned off after time, that is set in fit gear settings. Is there any way how to apply this settings to my fit gear also when I'm running workout?
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.
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!
ok so i have just noticed this… first off.
Gear fit manager latest version 1.88.xx
Device : samsung note 2 LTE 4.3
-
ok so i have noticed recently if my phone is in deep sleep. not being charged but just in deep sleep and i get a notification on my phone. the notification doesn't forward to my gear fit until i push the home button on my phone. i have only seen this happen when my phone was in deep sleep. if i am charging my phone and the phone is in deep sleep the notification will push to the gear fit right away. if i had just used my phone then the notification will push to the gear fit right away. so the problem i am seeing is not being able to receive notification when the phone is deep sleep( not charging) . like if i haven't touched my phone in 1hr and i get a notification. its not pushing it to my gear fit.
I don't have this issue. Are you using a battery saver or any kind of sleep modd progrzm that may interfere?
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