Hello,
I often have the problem when I start a run activity and pause the activity at the red traffic light, then it has often happened that the activity is automatically stopped when the display is touched by the jacket.
I don't know if that's the reason, but the touch screen reacts to random inputs during jogging from time to time and so the activity has often just stopped even though I didn't want it to.
Is it somehow possible to completely disable the touchscreen during an activity and let the Stratos 2 only be operated with keys during that time?
This problem is extremely annoying as it has completely ruined a number of long activities.
Does anyone have a solution?
Thank you very much!
Stratos is always locked after few seconds, so touchscreen is automatically disable so what do you mean ?
I don't think it's the touchscreen, unless watch's digitizer is misbehaving (defect)... This is not the normal behavior of the touchscreen. Do you have auto-pause enabled in activity settings? If yes, then disable it...
Related
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
I've had the watch for about two weeks and have a major problem - one serious enough for me to stop wearing the watch. If you slide down the screen on the watch it switches the photo to "Do not disturb" mode. I'm finding this happening just from normal wear, and missing important phone calls. On the other side, the watch touching my body when I move when sleeping has done the opposite and turned of Do not disturb mode, so I get woken up by message beeps during the night.
I've searched through the settings and can't find any way to disable this "feature" - or at least require some form of confirmation. Any ideas?
DND
jeffp25 said:
I've had the watch for about two weeks and have a major problem - one serious enough for me to stop wearing the watch. If you slide down the screen on the watch it switches the photo to "Do not disturb" mode. I'm finding this happening just from normal wear, and missing important phone calls. On the other side, the watch touching my body when I move when sleeping has done the opposite and turned of Do not disturb mode, so I get woken up by message beeps during the night.
I've searched through the settings and can't find any way to disable this "feature" - or at least require some form of confirmation. Any ideas?
Click to expand...
Click to collapse
I disabled gestures for the time being as this was happening to me. Its a poor design to be able to activate/deactivate with two wrist movements
Hi everyone, I've had my Moto Z for a couple of days now and am pretty happy with the device - even with the battery life I have one small problem, however.
Sometimes, when the screen is turned off, the Moto Display approach action won't work. In these cases, I also notice that the bottom right IR sensor isn't lit up - which it usually is when the display is turned off. The approach action only starts working again when I pick the phone up. This is very inconvenient and not how it's meant to be.
Is anyone else experiencing this bug?
At first I thought it might be an issue with Doze putting the process responsible for the Moto Actions to sleep, but after whitelisting all Moto apps the issue still sometimes occurs. I have not yet found out under which circumstances this happens.
Any help would be greatly appreciated!
EDIT: It seems this issue only occurs immediately after turning off the screen, after which there is a slight delay (a couple of seconds) before the IR sensor is activated. I will observe if this is really the case, which of course would render it a non-issue.
Hi guys,
Just received my GTR and so far happy with it.
I have one question, I am using the lift wrist to view functionality but when I use this the watch only stays on for 4 seconds.
I have changed the screen on duration on the watch settings and while this works when pressing the wake button itself it does not make a difference to the lift wrist duration.
Is this normal?
Thanks!
Same here, probably bug.
Thanks!
Thanks for confirming!
I think it is design to prevent false wrist lifting detect.
You touch the screen to wake it when it turn off after that 4 seconds.
But it seems that we only able to touch to wake in this scenario.
I noticed that this watch cannot be wake by touch.
I like Amazfit GTR but so far only 2 major complains.
1. The response is kinda slow when lift wrist to wake it. And if it wont wake, it makes me feel like an idiot looking at an empty screen. lol!
2. The transition at watchface to left or right is laggy (accessing the app menu seems alright though).
and..... Long press to change watchface is laggy too. LOL!
Hi, yep I agree sometimes I do have to try it a couple of times - I have the same feeling too!
I know what you mean about trying to minimize false raises, but I think they should make the time the screen is on, configurable, like you can when pressing the top button.
Haven't really noticed a lag problem, but I tend to load watch faces from the app.
Today I received a new update. It seems this new update fixed above problem. After wrist lift, my screen stays on for the amount of time specified in screen-on duration
@quickfoxz - great news, what version are you on now and where are you based?
I am on 1.3.4.11 and it is saying there are no new updates.
Glad to hear it is fixed though!
Cheers.
Hello,
After the last update (1.3.4.14), I confirm that the wakefulness response time of the screen after wrist lift is much better, and the waking time corresponds to the time chosen in the options.
On the other hand, the lag during the face modification is always present, but it is a detail.
Same here. The response is much better.
Overall performance just got better.
Been using my Pixel 6 for my daily driver since I received it after launch. Recently, I have had quite a bit of trouble with the phone screen waking in my pocket and calling random people or 911 (emergency services) or just filling the PIN unlock screen with random numbers. I believe the screen is interacting with the fabric of my clothing. I make sure to power off the screen before I put it in my pocket, and facing the screen outward instead of inward seems to make a bit of a difference. I have scoured the settings and can not find anything. The only other option I see is a full wallet type case that closes over the phone so there is no way anything can interact with the screen. This started happening with alarming frequency in April.
Am I missing something? Any suggestions on how to prevent this? Turning off wake from notifications?
Thanks in advance!
draexo said:
Been using my Pixel 6 for my daily driver since I received it after launch. Recently, I have had quite a bit of trouble with the phone screen waking in my pocket and calling random people or 911 (emergency services) or just filling the PIN unlock screen with random numbers. I believe the screen is interacting with the fabric of my clothing. I make sure to power off the screen before I put it in my pocket, and facing the screen outward instead of inward seems to make a bit of a difference. I have scoured the settings and can not find anything. The only other option I see is a full wallet type case that closes over the phone so there is no way anything can interact with the screen. This started happening with alarming frequency in April.
Am I missing something? Any suggestions on how to prevent this? Turning off wake from notifications?
Thanks in advance!
Click to expand...
Click to collapse
Sorry for not being able to add anything other than I too am experiencing this issue, exactly as described.
I think it could be the double tap to wake I wear jeans and don't have that problem but 8 am using a pixel 6 pro though
Same issue here.
Please use the feedback form in device settings -> about the phone to send the bug report to Google as well.
Thanks!
this never happened to me.
are you using screensaver? AOD? any kind of app which controls the screen on/off?