yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] mzguy:
I've been using KinScreen for a while, and thought of a useful behavior tweak. I like to turn my phone off by putting in my pocket, so I selected "turn off by covering proximity sensor". However, I also have checked "except in Landscape mode", so I can prevent turn off while holding the phone that way (watching a video, for example). This is natural, since covering the proximity sensor accidentally is easy in landscape mode, but awkward in portrait mode.

This works fine when I am in my home screen (which only accepts portrait mode), and I put my phone in my pocket to turn it off. However, when I'm in Gmail or a similar app that functions in landscape, the phone pops into landscape mode when I turn it upside down to put it in my pocket, preventing turn off! This defeats the intent of the settings.

I suppose I could get used to putting my phone in my pocket without turning it upside down first. However, that's feels less efficient for typical handling and use. I think KinScreen can easily address this by preventing the "except in Landscape mode" from activating if the phone is only in landscape mode for less than a couple seconds before the proximity sensor is covered. Or as an alternative, ignore landscape mode if the phone is turned upside down within a couple seconds of entering landscape mode.

Does this sound like a good idea?
[Android Apps and Games] Flyview:
That's a pretty good idea but then there would be some scenarios where it will seem like "except if in landscape" isn't working. For example, you go landscape to read an article and simultaneously cover the proximity sensor. Then the screen would time out quickly. I might add this in.
[Android Apps and Games] mzguy:
How about my second suggestion then: ignore an instance of landscape mode if the phone goes upside down within 2 seconds, and the sensor gets covered at the same time? I figure then the only complaints will be from those who accidentally over-rotate their phone upside-down and then cover their sensor immediately afterwards, just to read an article. I figure that isn't common. Also, "in landscape" shouldn't be confused for "upside-down", so I don't think anyone would have a right to complain!

There will always be cases where this sort of automated behavior catches someone off guard. In this case, I think the number of erroneous screen-off occurrences under the above approach would be small, whereas many people put their phone upside-down in their pockets and are surprised KinScreen hasn't turned the screen off.
[Android Apps and Games] Flyview:
I think the first suggestion is still better where "except if in landscape" is ignored if proximity is covered within 2s of having gone landscape. It's not always easy to gauge what "upside down" is. What if you're sitting? What if your pockets are horizontal (sweater)?
[Android Apps and Games] mzguy:
That makes sense. I hadn't thought about the position of other people's pockets; only mine!
[Android Apps and Games] note2junky:
Hey just a quick question here maybe its already been asked in this section but is there anyway for you to add a sound profile to this app or a vibrate so that we know for sure that the phone is truely locked ...I'm a s7 edge user with a flip case I do have my main lock sound on but this app over rides it I'm assuming because I hear nothing once my flip cover is closed I just wait a few minutes and check and its locked so I know app works great and I love what kinscreen does for me but would be even better to have a sound or vibrate telling us all that its locked ...I've bought app and everything and would still pay more for the extra in the app if it could be done

Thanks hope to hear back
[Android Apps and Games] mrgigabyte2002:
I too would like to hear the lock sound
[Android Apps and Games] Flyview:
KS doesn't override any stock locking behavior, so your usual lock should still make a sound. What's probably happening is that your screen isn't set to lock immediately with screen-off. You can usually find this somewhere in the display or security settings in Android. For example you can have it lock immediately, 5s or 2min after screen-off. There's also a setting if turning off by power button (as opposed to timing-out) should lock immediately. Having said that, I did just add a vibrate option.

4.0.0 - Beta 1 is out on Google Play Beta and XDA Labs!

-Fixed turn-off by proximity sometimes not working

-Added option to temporarily extend screen on time with each wave

-Added option to turn-on-by-proximity "except if screen for less than x seconds“

-Added option to vibrate when screen on/off

-Fixed turn-on by proximity not working after manual turn-off and app restart

-Reset “except if screen manually turned off” with unlock instead of screen-on

-Ignore “except if in landscape” if became landscape within last 2s

-Added privacy policy link due to phone state permission

-Fixed Bosnian/Croatian/Serbian translation
[Android Apps and Games] aquatix:
I sent you the Dutch translations this weekend, but mail doesn't seem to be delivered. Do you have issues with your mail? I can try sending from another address, might be my own server ;)
[Android Apps and Games] Flyview:
Ahh damn, yea just noticed email isn't working properly. I was wondering why no one was responding!

4.0.0 is up! Everything you guys asked for is there!

4.0.0 (February 6, 2017)

-Fixed turn-off by proximity sometimes not working

-Added option to temporarily extend screen on time with each wave

-Added option to turn-on-by-proximity "except if screen off for less than x seconds“

-Added option to vibrate when screen on/off

-Added keep-screen-on toggle to QuickSettings pulldown

-Fixed turn-on by proximity not working after manual turn-off and app restart

-Reset “except if screen manually turned off” with unlock instead of screen-on

-Ignore “except if in landscape” if became landscape within last 2s

-Added privacy policy link due to phone state permission

-Changed default notification priority to low

-Fixed Bosnian/Croatian/Serbian translation
[Android Apps and Games] Flyview:
New update is out on XDA Labs and Google Play!

4.0.1 (February 9, 2017)

-Reverted default notification priority to minimum

-Fixed SEC showing for vibrate instead of MS on free version

-Updated manually-kept-on status string to “manual toggle” instead of “notification”

-Fixed Quick Settings tile being clickable when service disabled

-Added Traditional Chinese translations (Thanks Raymond!)

-Updated translations
[Android Apps and Games] mzguy:
Love your responsiveness and updates! Thanks!
[Android Apps and Games] Flyview:
I just published an update to the beta channel on Google Play and XDA Labs! Let me know if you guys see any issues, especially if you're using the "Turn off xx min after continuously kept on". One change you might notice is that when using the max-on limit, touches do not reset it, only screen-off or turn-off events do (proximity).

4.0.2 - Beta 1

-Don’t allow motion to keep screen on past max-on time limit if being kept on by charging without keep bright selected.

-Fixed incorrect dim-time when using max-on time limit and kept on by charging without “keep bright”.

-Protected against late screen-off event for “turn-on-by-proximity except if screen off less than” option.

-Small layout tweak.

-Updated translations.
[Android Apps and Games] mzguy:
Why? Doesn't this negate the basic purpose of KinScreen? I often read my phone while it's plugged in. I encountered this just now. My phone turned off while I was reading it, apparently because I didn't touch the screen during the 15s timer. What's the intention with this change?
[Android Apps and Games] Flyview:
No no, this is only if you're using the "Turn screen off after xx min of continuously kept on". You probably covered the proximity sensor.
[Android Apps and Games] mzguy:
I do have that on, set to 10 minutes. I was reading for over 10 minutes while plugged in. I don't think I covered the sensor. I suspect that after 10 minutes, motion didn't wake the phone anymore. Is that intended?

Perhaps I should turn that feature of now, with the behavior change?
[Android Apps and Games] Flyview:
In that case yes, you reached the max limit. I didn't like how motion was the only thing not abiding by that limit. For example, if you were keeping the phone on by angle, the limit would work. Now it works with motion as well (even when not charging in the upcoming update). That max limit is mostly there if say you forget your phone in an environment where KS would otherwise keep it on indefinitely and you don't want it to stay on forever. For example, a moving car and not flat, angled up, charging, etc. I set mine to 60min. What were you using it for?
[Android Apps and Games] mzguy:
Thanks for the explanation. I was using the limit without giving it much thought, mostly as a backup to turn the screen off as you described.

Please let me know if I have this correct....

Assume I set mine to 60 minutes. If I have the phone in my hands (motion, angled, whatever), charging or not (in next update), it will turn off after 60 minutes. I can't prevent that in any way, short of touching my screen before the "After last kept on" timer (15s default). The only way to reset the KinScreen functions is to turn the screen off and then back on?
[Android Apps and Games] Flyview:
Yes, it will turn off after 60 minutes. Touching the screen will only extend it the "after last kept on" amount (20s default). It will reset the max keep on limit when the screen goes off, OR when you cover the proximity sensor (if you have turn-off by proximity set). If I could detect touches I would reset it then too but unfortunately that's impossible AFAIK.

New beta is up on Play and XDA Labs, and will likely directly become the production version:

4.0.2 - Beta 2 (March 9, 2017)

-“Turn screen off xx min after being continuously kept on” now works when kept on by motion.

-Max keep-on limit reset when screen goes off, or proximity sensor covered.

-Fixed incorrect dim-time when using max-on time limit and kept on by charging without “keep bright”.

-Protected against late screen-off event for “turn-on-by-proximity except if screen off less than” option.

-Small layout tweak.

-Updated translations.
[Android Apps and Games] mzguy:
Small clarification...

I have turn off by proximity set. I also have it set to keep on and extend timeout by 15 seconds with waving over proximity sensor. Will waving reset the max limit for another 60 minutes, or only if I get the screen to turn off by covering the sensor?
[Android Apps and Games] Flyview:
As soon as you uncover the sensor (even as part of a wave) it will reset. I just changed it so that whether you cover or uncover the sensor it will reset.

Final update will probably come tomorrow in case I find any other issues!
[Android Apps and Games] mzguy:
Great, thanks. I like that.
[Android Apps and Games] Flyview:
I'm going to try and make it so that if the screen gets a chance to dim, then motion will also reset it in that case... In that sense "continuously kept on" would mean kept on bright without indications of about to shut off.
[Android Apps and Games] mzguy:
Now wouldn't that defeat the purpose? Say, in your car example? Presumably max-on despite motion, shouldn't ignore motion in the final seconds before turning off. Just playing devil's advocate by using your own argument! :)
[Android Apps and Games] Flyview:
Well the idea would be that if it's about to turn off hopefully you caused the extra motion, and if you didn't chances are it'll get to that point again and no motion will be felt and it will turn off.
[Android Apps and Games] Flyview:
I just published another beta on XDA Labs and Google Play:

4.0.2 - Beta 3

-“Turn screen off xx min after being continuously kept on” now works when kept on by motion or proximity.

-Fixed incorrect keep-on time by motion while charging without keep bright.

-Max keep-on limit resets with screen off, or during final dim by waving over proximity or with motion.

-Protected against late screen-off event for “turn-on-by-proximity except if screen off less than” option.

-Small layout tweak.

-Updated translations.
[Android Apps and Games] Flyview:
I just can't stop adding features. I just published another beta to Play and XDA Labs, it should be available soon:

4.1.0 - Beta 4

-Added double wave-over proximity to turn on option.

-“Turn screen off xx min after being continuously kept on” now works when kept on by motion or proximity.

-Fixed incorrect keep-on time by motion while charging without keep bright.

-Max keep-on limit resets with screen off, or during final dim by waving over proximity or with motion.

-Protected against late screen-off event for “turn-on-by-proximity except if screen off less than” option.

-Updated translations.
[Android Apps and Games] Flyview:
I just published the final 4.1.0 version on XDA Labs and on Google Play!

4.1.0 (March 15, 2017)

-Added option to turn screen on by double-waving-over proximity sensor.

-“Turn screen off xx min after being continuously kept on” now works when kept on by motion or proximity.

-Fixed incorrect keep-on time by motion while charging without keep bright.

-Max keep-on limit resets with screen off, or during final dim by waving over proximity or with motion.

-Protected against late screen-off event for “turn-on-by-proximity except if screen off less than” option.

-Fixed rare crash after dismissing dialog.

-Updated translations.
[Android Apps and Games] JohnDo88:
I give your app 5 stars on Google Play! Is a must have app for Android!
[Android Apps and Games] Flyview:
I just published an update that fixes a bug to XDA Labs and Google Play.

4.1.1 (March 18, 2017)

-Fixed screen turning off when keep-on by waving over proximity is unchecked.
[Android Apps and Games] avd:
It's not taking. The screen doesn't stay on.
[Android Apps and Games] Flyview:
Please post your settings.
[Android Apps and Games] avd:
Version 4.1.0 beta4
[Android Apps and Games] avd:
Missed one screen
[Android Apps and Games] avd:
4.1.1 seems to have fixed the issue for me
[Android Apps and Games] Flyview:
Yup, there was a bug in 4.1.0 if you weren't using keep on by proximity.. There's still a bug in 4.1.1 but less severe and I'll have an update out soon.
[Android Apps and Games] Flyview:
New update is out to Google Play and XDA Labs, changelog below!

4.1.2 (March 23, 2017)

-Fixed screen turning off too quickly when kept on by motion.

-Fixed squished wave-times button text.

-Added Romanian and Hungarian translations (Thanks Andras!)

-Changed wording for “active on lockscreen” option.

-Updated translations.
[Android Apps and Games] Flyview:
New update is out on Google Play and XDA Labs:

4.1.3 (March 30, 2017)

-Fixed “turn-on by proximity except if screen off more than” if also using “turn-on by proximity except if screen off less than.”

-Do not temporarily extend timeout by waving over proximity if device already kept on by any other rule.

-Decreased double-wave time interval from 2s to 1s.

-Fixed squished spinner text.

-Changed wording for lockscreen option.

-Right to left layouts supported.

-Added Hebrew translation (Thanks Liran!)
[Android Apps and Games] Flyview:
Another update! Get it on Google Play or right here through the XDA Labs app! It's been almost 3 years since KinScreen came out. This was actually my first app and is now my most downloaded, it's come a long way! Please continue to spread the word.

P.S. Has anyone noticed that the QuickSettings tile is no longer being tinted properly when toggle is being used? This was working fine on Android 7.1.1 but stopped with 7.1.2. I was hoping this would be fixed with the final 7.1.2 but I just updated and it's the same!

4.1.4 (April 3, 2017)

-Reset max-keep-on limit with touches for long standing bright wakelocks (ex. tilt angle/charging)

-Reset max-keep-on limit if there’s new motion while dimmed (as opposed to only during “final” dim time).

-Reset max-keep-on limit by waving over proximity.

-Updated to support libraries 25.3.1.

-Fixed Hebrew translation.
[Android Apps and Games] ~El Julio~:
I have, yes. This is the case with many other apps QS tiles too.

Happened already (not always) on 7.1.1 (with other apps too), seems worse on 7.1.2. (Pixel C)
[Android Apps and Games] mzguy:
I love how the features of KinScreen have evolved. Thanks for the great app. I think you're getting to the point where not much can be improved in terms of functionality, at least for how I use KinScreen. However, I think I thought of one.

I use a short (1 sec) screen off when covering the proximity sensor. This lets me put my phone in my pocket and it will turn off. Also, if it accidentally turns on in my pocket, it will turn itself back on.

I also like to extend my screen timeout by using the feature where I can do so by waving over the proximity sensor. That's a great way to read something with the phone flat on a table, while mostly keeping my hands free to do something else.

I think you can see the problem. With a short screen off by proximity sensor setting, I sometimes accidentally turn my screen off when all I want to do is extend the screen-on time. Your detection of a wave requires that I do a bit more than wave. It seems like I need to cover the proximity sensor for something like 500ms or so.

I think a potential solution would be to add some sort of confirmation that the screen extension feature has triggered - perhaps a customizable length vibration or some brief visual indication. It would be good to have a confirmation of the app taking action in any case, but the lack of indication is the primary reason that my screen turns off when I'm trying to wave over the sensor. After all, I have to keep the sensor covered long enough to extend the screen timeout, but not so long that it turns off. The lack of a confirmation makes me try several attempts to get between 500ms and 1s, without knowing which if any have worked. That results in too much trial and error.

Do you agree that a vibration or some other confirmation be a good idea?
[Android Apps and Games] Flyview:
It's doable but it's such a specific scenario. The "wave" basically needs to cycle the proximity sensor from uncovered-covered-uncovered. Based on how sensitive the sensor is on the particular device you may need to wave over slower/closer as you've noticed. Why not just set the turn-off-by-proximity to 2s? It won't make a big difference and you'll turn off the screen accidentally a lot less, in other scenarios as well since you'll probably be able to see the screen dim first.
[Android Apps and Games] mzguy:
I'll try it. Thanks.
[Android Apps and Games] Ilmadic:
Hi,

first of all thanks for the app! Very nice.

Can someone exlain how to use the intents in tasker. I tried strat stop an toggle but nothing is working.

Can someone help me.

Thanks!
[Android Apps and Games] Flyview:
Thanks! What are you trying to achieve with the intents?
[Android Apps and Games] Ilmadic:
Hi,

sometimes the app is not working (the degree stays at a specific value). Then I have to open the app and turn it off and on again. Then it is working normally. So I want to turn KinScreen off and on again everytime I unlock my phone. I want to do this with an intent in tasker. (Energy optimization is turned off for KinScreen.)
[Android Apps and Games] Flyview:
Yes this does unfortunately happen on a few devices. Until I get my hands on one that can reproduce the problem, I'm afraid I've tried everything I can think of so that the sensor readings do not get stuck.
[Android Apps and Games] jaydee 77:
I recently moved to nougat and discovered the Kinscreen quicksetting tile. I would ask if you can expand its functionality to something like the caffeine tile from CM/LOS. It has a multi tap function leaving screen on for 5min, 10min, 30min and forever on 1st, 2nd 3rd and 4th tap.
[Android Apps and Games] Flyview:
Thanks for the suggestion! I'll think about doing this, I'm just a bit worried it could be somewhat confusing for your average user.
[Android Apps and Games] Flyview:
I just uploaded a beta release to Google Play and XDA Labs. Here's the changelog:

4.1.5 - beta 1

-Proximity now has to be covered for minimum of 2s before uncovering turns screen on (so waving won’t turn it on)

-Fixed screen not turning on when proximity events are batched

-Fixed motion not resetting max-keep-on-limit during final dim period

-Fixed user activity not resetting max-keep-on-limit

-Fixed double wave detected too early

-Built for Android O

-New notification management for Android O

-Minimum Android version supported up to 14 from 11

-Updated Polish translations
[Android Apps and Games] Nitz327:
Hey, I have an odd question. I've bought this app on an older device (Moto E) and I used an apk extractor to install on my current device (Redmi 3s). The app is not supported on my device because MIUI is really weird about wakelocks and it won't work properly. I'm not using MIUI anymore (Really hates it), I'm using lineage 13 and it runs great, Kinscreen runs great on it as well. I'd love to get the new version but I don't have that Motorola anymore :S. I don't want to pirate either because the app is great and so is the dev. I'll happily buy it again if it'll help. Lol sorry, that's very long winded and I hope not too confusing.

Oh I should have mentioned in there that the app won't even show up on the play store for me, because it's by device I guess and it assumes I'm on MIUI. Any help would be great!

EDIT: Oh it let me update thru the XDA app!! Sorry I guess that big wall of text was a waste of time.
[Android Apps and Games] Flyview:
Yup, there's no restrictions through XDA Labs! I wonder if there's a way to block MIUI instead of XIAOMI devices on Google Play.

P.s. there's no need to pay again, your purchase will be recognized again as long as you use the same Google account in Google Play.
[Android Apps and Games] Nitz327:
Oh that's awesome I didn't know it would remember my purchase, thanks for getting back to me so fast! Yea MIUI is crazy when it comes to anything requesting a wakelock, it even has a whitelist but it doesn't seem to work. I'm still using my Redmi 3s but with an unofficial version of lineage, seems to run Kinscreen great I've been using it for a month or so. Lol unofficial Lineage seems less buggy than the "stable" MIUI as well.
[Android Apps and Games] Flyview:
I just published another beta to XDA Labs and Google Play beta channels:

4.2.0 - beta 3

-Added option to calibrate tilt angle

-Fixed motion not being ignored when flat and accelerometer used for tilt

-Fixed tilt angle not working when not using “keep-on by motion” if accelerometer used for tilt

-Proximity has to be covered for 2s before uncovering turns screen on

-Fixed screen sometimes not turning on

-Fixed motion not resetting max-keep-on-limit during final dim period

-Fixed user activity not resetting max-keep-on-limit

-New notification management for Android O
[Android Apps and Games] Nitz327:
The new beta is not showing up for me for some reason, shows today's date but no download option :crying:

Edit: Oh I figured it out, I didn't know about the two channels in the description, on beta channel now, sorry to bother you again!
[Android Apps and Games] avd:
Thanks working great on my SGS3 running octo 4.1.2
[Android Apps and Games] chuckiev79:
Is there any way to prevent this app from going to sleep or getting hibernated? Aka work all the time, everytime.
[Android Apps and Games] tjsuominen:
Perhaps problem with Android "Doze" mode?
[Android Apps and Games] Nitz327:
From what I understand, it should be doing that on it's own. Unless something is hibernating it like greenify. What version of Android are you on?
[Android Apps and Games] chuckiev79:
Yah I'm on marshmallow using greenify with aggressive doze. I use this because I move around all day. With this setup I would need to disable greenify or keep the cpu awake for the kin screen app to work all of the time correct? Not exactly sure what the best approach is. I'm open to any suggestions.