I'm sorry there's not much I can do. It doesn't respect the wakelocks that KinScreen needs to function.
Hey, I love this app but it seems like it must run in the background in order to work, no? If I exit it from the recent apps, it doesn't work anymore, is that on purpose? Can't there be a amgisk module to have it all the time ?
New update released to Google Play and XDA Labs!
5.2.4 (January 30, 2019)
-Fixed app detection on some Android 5.0 devices
-Updated purchase system
-Updated About dialog style (spacing, date style, website link)
-Updated in-app link to go directly to privacy policy
-Linked "Our other apps" to website
I'm sorry I haven't yet figured out what's going on with the intents for Tasker. I assume they're still problematic?
Hey, I love this app but it seems like it must run in the background in order to work, no? If I exit it from the recent apps, it doesn't work anymore, is that on purpose? Can't there be a amgisk module to have it all the time ?
Yes, same issue as before. They used to work, then stopped at some point. During this whole time, intents for other apps are working fine, so I know it's not a phone-specific or user-induced problem!
Hey, I love this app but it seems like it must run in the background in order to work, no? If I exit it from the recent apps, it doesn't work anymore, is that on purpose? Can't there be a amgisk module to have it all the time ?
am broadcast -a com.teqtic.kinscreen.INTENT_TOGGLE_SERVICE -n com.teqtic.kinscreen/.ToggleServiceReceiver
@mzguy okay, I was able to fix the intents, sorry about that. I had removed the intent filters in the manifest once only explicit intents (specifying class) became required with Oreo. Still not sure why they're needed but I added them back and now this intent works again through adb shell, so it should work through Tasker:
Code:am broadcast -a com.teqtic.kinscreen.INTENT_TOGGLE_SERVICE -n com.teqtic.kinscreen/.ToggleServiceReceiver
Fix will be out with the next update. I'm curious, what do you use the start/stop/toggle intents for?
Thanks! Are you fixing start and stop too, or just the toggle?
I use intents with Tasker to allow me to turn off my phone screen with a gesture and avoid the power button. Comes in handy. I use Nova launcher and tasker to assist with that.
@mzguy okay, I was able to fix the intents, sorry about that. I had removed the intent filters in the manifest once only explicit intents (specifying class) became required with Oreo. Still not sure why they're needed but I added them back and now this intent works again through adb shell, so it should work through Tasker:
Code:am broadcast -a com.teqtic.kinscreen.INTENT_TOGGLE_SERVICE -n com.teqtic.kinscreen/.ToggleServiceReceiver
Fix will be out with the next update. I'm curious, what do you use the start/stop/toggle intents for?
Ya all of them are fixed. But how does starting/stopping KinScreen help with that?
New update is out on Google Play and XDA Labs:
5.3.0 (February 5, 2019)
-Added widget to toggle keep screen on manually in addition to notification / QS tile
-Fixed animations
-Fixed Tasker start/stop/toggle service intents
Thanks! Works great. With a Tasker script, I turn off Kinscreen to prevent it from keeping the screen awake, reduce the time out to the shortest length, and use Nova's action to darken the screen. Then, I can move the phone around, but not touch the screen, and it will sleep within 10 seconds. I then have tasker re-enable Kinscreen so it's activated the next time I turn on my screen. All that is triggered with a home screen gesture. It's pretty slick.
Or you could just flip the phone over to cover the proximity sensor and have KS do all that automatically
Hmm fair enough. Someone emailed asking for a similar feature. I think I'll build a QS toggle and widget to time screen out ASAP. Then you don't have to mess with Tasker and all that
I've came across KinScreen few days ago and gave it a try to replace Screebl. Definitely a promising app especially when you manage better in car behavior. I'd also like for KinScreen to turn off screen when my phone is paired with my car's BT against current behavior where it keeps screen on ... And I don't want to disable KinScreen in car because it really helps me a lot to just wave and turn phone on ...
Also don't know if intents worked previously but only intent working for me is TOGGLE intent whilst START and STOP don't work. Also please add a run at startup option ... Thanks.
I've came across KinScreen few days ago and gave it a try to replace Screebl. Definitely a promising app especially when you manage better in car behavior. I'd also like for KinScreen to turn off screen when my phone is paired with my car's BT against current behavior where it keeps screen on ... And I don't want to disable KinScreen in car because it really helps me a lot to just wave and turn phone on ...
Also don't know if intents worked previously but only intent working for me is TOGGLE intent whilst START and STOP don't work. Also please add a run at startup option ... Thanks.
Yes, it needs to run in the background, that's why it runs a foreground service. Sigh... welcome to third party manufacturers and their love for turning the recent apps task switcher into an app killer. This doesn't happen on stock Android. What device?
I've came across KinScreen few days ago and gave it a try to replace Screebl. Definitely a promising app especially when you manage better in car behavior. I'd also like for KinScreen to turn off screen when my phone is paired with my car's BT against current behavior where it keeps screen on ... And I don't want to disable KinScreen in car because it really helps me a lot to just wave and turn phone on ...
Also don't know if intents worked previously but only intent working for me is TOGGLE intent whilst START and STOP don't work. Also please add a run at startup option ... Thanks.
While options are great, especially for cases where many users won't use Tasker and deal with that complexity, please do keep the Tasker integration. It's one of the things that sets this app apart, and provides flexibility to power users.
For example, one advantage of my Tasker / Nova solution is this (don't know if you can replicate):
If I just put my phone in my pocket, Kinscreen shuts it down ASAP. However, in the meantime screen touches can cause all sorts of trouble. If I use my Tasker task to have Nova black-out the screen, it ignores keypresses and they can't launch apps, etc.. They do extend the screen timeout of course, but.... I have Tasker turn Kinsreen back on after about 12 seconds, so even if my screen is being occasionally pressed in my pocket, Kinscreen is able to finish the shutdown ASAP as long as there is a 3-5 second gap between accidental screen presses.
It's really a best-case solution for shutdown in-pocket. With Kinscreen / Nova / Tasker, I feel like my phone screen does exactly what I want in all scenarios.
Nope START and STOP intents don't work for me (nothing happens when I test them) only TOGGLE does. Also KinScreen doesn't automatically start on my phone.
I have a Samsung S8+ with stock ROM 8.0.0.
My intents are set up correctly, the thing is they do work if I manually start KinScreen for the first time (upon boot) but they seem not to work if KinScreen hasn't been started previously. Hope I've managed to clear my issue a bit better this time.