yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] Nitz327:
Aggressive doze in Greenify could be doing it, I found Naptime worked better than Greenify's aggressive doze, and I'm finding now that ForceDoze seems to work better than Naptime haha. I can't remember if Greenify had a whitelist for apps or not? I know Naptime had a whitelist for ONE app just for sensors. Try disabling Greenify's aggressive doze and try ForceDoze and see if it's any better, it's a free app with a donate option if wanted.

I use Kinscreen allllll the time but I don't always use the wave or unstow to wake feature cause my device stays awake. I'm 99% sure that this is a problem with my rom tho and not Kinscreen, haha my device won't sleep at all without something like ForceDoze or Naptime.

Edit: Fudge I think you need to be rooted for ForceDoze, I forgot to mention that
[Android Apps and Games] chuckiev79:
Thanks for your expedient response. I know now that the problem is on my end and not with app. Greenify does have a whitelist for apps and I have included kinscreen but I guess it doesn't truly whitelist it. My device that I am using is a BlackBerry priv, so no root. I guess I'll just keep the cpu awake via tasker or other app when I need super responsiveness.
[Android Apps and Games] Nitz327:
What I do is leave the auto screen off function on and the keep on with motion options on so I can just drop my phone in my pocket and forget about it, and I have it so manually turning the screen off keeps it off, it's not as annoying in a car that way haha, otherwise just driving is enough to keep the screen on. Ambient display will then light my screen up when I grab my phone from my pocket (slowly tho, ambient display was always slow in my experience anyways). I've never had a blackberry with Android on it before so I don't know aaaanything about what quirks they've built into it haha. They might have a task killer that's running? I'm coming from MIUI to a stockish Android, MIUI has built in "features" that kill apps to free memory. It also had a whitelist but it never worked :/ sorry I hope I was some help at least haha.
[Android Apps and Games] kloontz:
Hello,

Same thing happening here. OnePlus 3T, OxygenOS 4.1.6 with root. No Greenify or similar.

I have added KS to auto launch list so it works ok after reboots but stops working during the day.

Any suggestion to debug?

Thanks
[Android Apps and Games] Flyview:
It already runs all the time as a foreground service. If it's being killed it's by your Android system or a task killer type app. The way it's SUPPOSED to work is even if it does get killed in memory-intensive situations, the system schedules it to restart in a few seconds to a minute. Unfortunately all these custom Android implementations (like MIUI for example) start killing off processes and don't restart them. Having said that, which feature are you finding stops working? Is it just the turn-on feature or do keep-on features also stop working while the screen is on?

The CPU doesn't need to stay awake for the turn-on features to work. That would be a huge battery drain. Somehow the proximity sensor wakes the CPU up. It's possible that on some phones this does not happen, and this could be the problem as well. If you guys want to help delve into this further, shoot me an email so I can send you a debugging version. I really need to build a debug and save option right into the app...
[Android Apps and Games] Flyview:
New version up on Google Play and XDA Labs!

4.2.0 (August 12, 2017)

-Added option to calibrate tilt angle

-Fixed motion not being ignored when flat if 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

-Fixed double wave detected too early, when inProximity

-Built for Android O.

-Minimum Android version supported up to 14 from 11

-Made notification priority spinner use ChoiceDialog instead

-Made email be clickable to start an email in About dialog
[Android Apps and Games] Flyview:
Someone reported that the keep-on functions aren't working on the lockscreen on their Galaxy S6 running Android 7.0 . Could anyone with the same phone (or similar) test this? You'll have to enable the option for "keep-on rules apply on lockscreen" first. Thanks!
[Android Apps and Games] Flyview:
Just put out a little bug-fix update on Play and XDA Labs!

4.2.1 (October 11, 2017)

-Fixed upgrade dialog being shown on first open

-Fixed warning dialog for modify system settings from showing in a loop

-Fixed notification behavior on older Android versions

-Set proper timeout after motion calibration

-Updated translations
[Android Apps and Games] Flyview:
So I had someone write to me saying that except if landscape isn't working. They ran into my 2s delay since they were covering the sensor as the phone rotated, or shortly after. Both problems are significant:

1) Old implementation - Phone goes to landscape without the user noticing as he slips it in their pocket and the screen doesn't turn off

2) Current implementation - User intentionally turns the phone to landscape while covering the proximity sensor and the screen turns off (even though they expect it not to in landscape)

I've changed the delay to 1 second, but that still doesn't solve the current issue. Any ideas?
[Android Apps and Games] mzguy:
Well, my issue is more important. :D

In all seriousness though, without a delay we can give up on putting phones in pockets upside down, since spinning it around each time requires two handed careful handling. It's an awkard risk of dropping the phone. Since you introduced the delay, functionality is perfect for me. In fact, it's all so flawless I donated a couple weeks ago, since I'm quite happy with it!

How about you start the original 2-second delay to ignore when the phone first moves to landscape, but if the phone sensor is uncovered after another 2 seconds, then you assume it is intentionally in landscape position but was accidentally covered and leave the screen on? To some extent, someone who is always covering the sensor would need to be somewhat careful and not leave it covered full time. After all, what is to prevent them from covering the sensor before the phone moves to landscape, and defeating the turn-off with sensor function entirely for all use cases. I do think there is a relatively easy burden here to be a bit careful and not just start covering the sensor full time. I figure this user also wants to be able to benefit from this function, and would run into the same kinds of issues I did, if the app's landscape policy is too strict.

Another option: since I figure most people don't pocket their phone while sitting down (hard to do as pockets are bent, and risky for the phone slipping out), the phone should be in landscape only temporarily before moving upside-down. Why not ignore the landscape orientation for 2 seconds only if the phone does not go upside-down within the 2 seconds following (as happens when going into a pocket)? After all, the only use case for the landscape exception is if one keeps it in landscape - so just test for that. My concern here is my impression that many phone models report right-side-up and upside-down interchangeably. I think the Tasker documentation taught me this.

I prefer the first option, since I believe it is more resilient under more scenarios, such as when someone puts a phone on the table, bag, etc.

I see no other reasonable way out, since if someone is constantly covering the sensor, you can't tell if it's a pocket, a hand, or a bag! I think it would be reasonable to implement one of the workarounds above.
[Android Apps and Games] Flyview:
On my N5x, the phone either never goes to landscape if I rotate it to be upside down quickly enough, or if it does go into landscape during the rotation, it stays in landscape even while upside down. If it did go back to portrait mode none of this would be a problem anyway since then the proximity exception would be gone anyway. I'll leave it at a 1s exception from the beginning of becoming landscape for now. It's actually longer than you think, 2s was too long. This still requires someone who means to go landscape to not cover the proximity sensor during rotation and for the first second of being in landscape, or to uncover the proximity before re-covering it for the exception to come into effect.
[Android Apps and Games] Flyview:
New update is out to the beta channel for now (Play and Labs). Let me know if you guys see any issues with it and if not I'll promote it to production in the next few days. I'm seeing a few ANRs reported in the console from people with Pixel 2 (incl. XL). Anyone out there with one?

4.2.2 - beta 1

-More reliable turn-on-by-proximity

-Ignore “except if landscape” for 1s instead of 2s while/after rotation to landscape

-New launcher icon (Thanks Marc!)

-Changed default tilt threshold to 45deg

-Hide notification priority choice on Android 4.0 and 4.0.3

-Updated support libraries to 27.0.1

-Got rid of legacy start receiver
[Android Apps and Games] mzguy:
I think this will work well for me. Thanks.
[Android Apps and Games] xdaca:
Any way to get premium without play store?
[Android Apps and Games] dvlad666:
Dear developer, thanks for your effort!

Unfortunately for me app is not worth money (yes i paid even to test it) and is simply useless.

I only need one crucial function from the app - reduce lockscreen timout. And it doesn't work. Yes it does set timeout for the first lockscreen activation (i.e. after i press power button on the unlocked phone), but after i let it switch off, then activate lockscreen again (i..e just to see the time for example) with either power or home button, it again stays on for long time like the main time.

We already have notification to keep APP running, why can't we have a setting to enforce any timeout? Or explicitly poll screen status and turn it off in lockscreen every XX sec.

Second, there are some good other functions that involve proximity and position sensors, but hell, why so many requests per sec? Do we really need 15 FPS on them? Do all people need that? My governors jump from 200mHz to 600mHz at no load when i enable any sensor-related stuff in the app. I'm just reading the news and wasting battery.

An FPS setting could be great as well (for both screen on and off/locaked) or some battery optimization tricks with hysteresis +-20° to angle to trigger 10 more measurements to stabilize value then make decision.

Galaxy S2 4.1.2 stock-based, pattern lockscreen. Hope this helps.

I'm more tan open to debugging and further testing, let me know what i can do.
[Android Apps and Games] avd:
I supported the developer because I liked the concept of the app, the app actually worked ( unlike other offerings ) and the developer is very responsive to the community.

I value these the things in the Las of xda development. I only wish that I had more resources than I do to pride more support to additional developer.

You're entitled to your opinion.

Thanks.
[Android Apps and Games] Flyview:
Unfortunately, no there isn't, as the purchase check is done through Google Play services.

Hey there, sorry I saw this a little bit late. What are you setting the lock screen timeout to in KS? That's pretty strange that it only works the first time. If it doesn't work, I would expect it to not work at all. The issue being that the system itself may hold its own wake lock to keep the screen on a minimum amount of time.

KS doesn't actually ever actively turn the screen off, it simply changes the timeout. To actively turn the screen off, you need to use the Device Admin API. There's a few reasons I don't wanna do this. 1) It would always lock the screen (as opposed to just turning it off). 2) Users seem to be very confused by the fact that you have to first disable device admin for any app before you can uninstall it. 3) Google really doesn't like apps using this API and will even give out warnings.

The "requests per second" are just the default sensor polling of the phone. It's needed to accurately detect small motion, for example. Are you positive that the bump in CPU frequency is caused by KS? You could check the CPU load and CPU freq in real time with my other app, SystemGlow if you're so inclined. :p Does KS show up in the battery usage screen? At the end of the day, you're using a pretty old device!

Thanks for your support!!!
[Android Apps and Games] Flyview:
New update is up on Google Play and XDA Labs!

4.3.0 (December 18, 2017)

-Non-active timeout now free

-More reliable turn-on-by-proximity

-Quicker start after boot

-Ignore “except if landscape” for 1s instead of 2s after rotation to landscape

-Reduced minimum time covered from 2s to 1s for turn-on-by uncovering proximity

-New launcher icon (Thanks Marc!)

-Changed default tilt threshold to 45deg

-Limit max dim time to 8s like stock Android

-Added Vietnamese translation (Thanks Trung!)

-Temporarily turn on sensors for calibrations if not on

-Disable tilt angle calibration if service isn’t started

-Don’t hold any wakelocks if only using turn-on options

-Don’t show toast after motion calibration

-Reset proximity extension if toggling keep-on-by-proximity or to extend

-Hide notification priority choice on Android 4.0 and 4.0.3

-Got rid of legacy start receiver

-Updated support libraries to 27.0.2
[Android Apps and Games] thewaywardgeek013:
Somehow latest version isn't working as it is supposed to. Always times out even if I use the Manual Toggle.

Using LG G2 D802 Stock Rom under Android 4.4.2 Kitkat

UPDATE:

"Turn Screen off…" setting doesn't respect Manual Toggle IF you do not enable/check "SEC after covering proximity sensor" OR "MIN after continously kept on"

Not sure if this is a bug or it's just a feature, either way just reporting it.
[Android Apps and Games] Flyview:
Hey, I'm not sure what you mean by "turn screen off..." setting doesn't respect manual toggle. Can you write out the steps of how you're testing and what you expect to happen and what actually happens?
[Android Apps and Games] thewaywardgeek013:
Here is a screenshot!

What I meant was you should turn on one of the features below "Turn screen off…"(the encircled settings in the screenshot) options/settings for Manual Toggle to work properly.
[Android Apps and Games] Flyview:
New update up on Google Play and XDA Labs:

4.3.1 (December 28, 2017)

-Fixed manual toggle not working if not using any keep-on or turn-off options

-Fixed notification not hiding on lockscreen

-Changed back to SENSORY_DELAY_NORMAL for proximity sensor

-Only show one green status indicator (other than motion + non-bright charging)

-UI tweak
[Android Apps and Games] Nitz327:
Hey sorry if this has been discussed already, but is there any way to reduce the time it takes for the screen to go off after the proximity sensor is covered? The setting is there but it seems like the system just has a minimum time, like 5 seconds or so. Maybe 6 haha.
[Android Apps and Games] Flyview:
The system minimum is usually 10s from the last touch event. So if you last touched the screen 12s ago and have KS Set to 1s, it'll turn off in one second. The only other way would be if I implement the Device Admin API. I don't want to do that for 2 major reasons. 1) it confuses users that you have to disable device admin privileges before you can uninstall the app, even with prominent messaging. 2) it necessarily locks the screen when turning it off.

On another note, how'd you get KS working on a MIUI system? Most can't hold the background wakelocks. I.e. KS only works with the settings screen in the foreground.
[Android Apps and Games] Nitz327:
Oh I see I see. Thanks for clearing it up :)
[Android Apps and Games] gutzzz:
Hello, thank you for the great app!

Can you help me to find a correct activity to toggle kinscreen on/off? I want to add the toggle to quick settings using Tiles app but there are too many activities to choose.

It would be great for android 7.x users though if you can add this natively on your app.
[Android Apps and Games] Flyview:
There's already a Quick Settings tile to keep the screen on indefinitely or not. Why would you want to start and stop KinScreen? :P

If you insist, you can use these intents:

public final static String INTENT_TOGGLE_SERVICE = "com.teqtic.kinscreen.INTENT_TOGGLE_SERVICE";

public final static String INTENT_START_SERVICE = "com.teqtic.kinscreen.INTENT_START_SERVICE";

public final static String INTENT_STOP_SERVICE = "com.teqtic.kinscreen.INTENT_STOP_SERVICE";
[Android Apps and Games] gutzzz:
Well that's not what I need. For example I'd like to turn off your app when I use a waterproof pouch since the pouch sometimes interfere with the proximity sensor. I'd like to avoid waking up the screen accidentally.
[Android Apps and Games] Flyview:
You can use those intents to turn the service on and off with something like Tasker. There's no activities to do this.
[Android Apps and Games] Nosferatu.:
Stumbled across this app very clever especially with the implementation!
[Android Apps and Games] TNSMANI:
[MENTION=2584205]Flyview[/MENTION]

Happy New Year!

I am on ver 4.3.1 and my setup is in the sig.

On this version, I find that when I enable "keep screen on until turned off" from the notification, the notification as well as the statusbar icon vanish till I lock the screen. They are available from the time of next screen on.

This is not an issue, just wanted to check whether it is the intended behaviour. That said, I was using the notification earlier to cancel the 'keep screen on' setting which is no longer possible. So I have to get used to the current implementation :(
[Android Apps and Games] Flyview:
Thanks :)

That's weird, I can't reproduce it. What Android version? If you're on Android 8+, check the notification settings and make sure you didn't turn off the notifications for the screen-kept-on channel.

Just published an update on Play and XDA Labs:

4.3.2 (January 2, 2018)

-Fixed screen possibly staying on if service restarted while screen on

-Hold turn-screen-on wake lock for 3s instead of until screen-on broadcast

-Check if screen is actually on for screen-on and screen-unlock broadcasts
[Android Apps and Games] TNSMANI:
Thank you.

Yes, you are right, somehow the notification setting was off, though I don't remember to have switched it off.

Anyway, after enabling it, everything back to normal.
[Android Apps and Games] Nitz327:
I'm having a weird problem but I'm not sure it's the app. And it's unpredictable so I'm not sure if a log would help. The easiest way to describe it is that Kinscreen loses its connection with the motion sensor? The word motion In the app stays white and after toggling the app off then back on resolves the issue. But it happens again and again seemingly for no reason. Any ideas?
[Android Apps and Games] Nitz327:
I took 2 screenshots, one where it's normal (green) and one where it's broken (white).
[Android Apps and Games] TNSMANI:
This happened to me earlier while on Nougat, where 'motion' will freeze. I asked here but the cause could not be identified. After sometime, the issue went away automatically.

EDIT: Sorry, the issue was with 'angle', not 'motion' in my case. When 'angle' did not work, I enabled 'motion' as a workaround. Now I don't have any issues.
[Android Apps and Games] Flyview:
It's most likely an issue with the device unfortunately. The device stops updating the app with sensor data, even though I re-register the sensors with every screen off. It used to happen very very infrequently on my Nexus 5. It hasn't happened at all on my Nexus 5X or Pixel 2. How often is it happening for you?
[Android Apps and Games] Nitz327:
It's possible its the device yea, it's odd that it started out of nowhere. It happens probably once every 2 or 3 days approximately. I've disabled the keep awake based on motion and just use the setting based on tilt angle, seems good that way. Thanks for getting back to me! Appreciate the help :)
[Android Apps and Games] Flyview:
No problem. Are you running the stock MIUI system? It doesn't work at all on most MIUI ROMs, so I've excluded Xiaomi phones on the Play store.
[Android Apps and Games] Nitz327:
Oh no no, nope. Not a big fan of MIUI really. I did run it for awhile and yea you're right, wouldn't work unless I kept the device awake 100% of the time. Not just your app tho, anything that needed to run in the background or hold a wakelock for any reason. I am on a Xiaomi phone but I'm running an unofficial build of Resurrection Remix right now. All has been great for months until the weird sensor refresh thing. But I don't care honestly, I noticed the keep screen on over a certain angle and that does the same thing really. Appreciate the help, love your app! It's the 1st thing I install on a new phone haha. :good::good::good:
[Android Apps and Games] mazenimad:
This is the best app ever, thanks to the dev. I'm having problems though with the app force closing and losing the kinscreen service, I have the notification on, tried reinstalling the app too. Rooted one plus 3t Nougat 7.1.1, xposed, greenify (doesn't include kinscreen, Amplify (have some wakelocks and services disabled but not with kinscreen in them, maybe someone can enlighten me).

Is anyone having this issue.
[Android Apps and Games] Flyview:
Hi, it's either being killed by the system or another app, or it's crashing. Please email contact@teqtic.com so we can get a logcat.
[Android Apps and Games] Flyview:
Would you guys be interested in me building and optimizing KinScreen to run on Android Wear devices?

Anyone have an old Wear device lying around I could borrow so I can do this?
[Android Apps and Games] Flyview:
Extensive new update is up on Google Play and XDA Labs beta channels:

5.0.0 - beta 1

-Added keep-on-by-angle max angle

-Added keep-on while app in foreground

-Added "except if in silent mode" for vibrate options

-Negative tilt angle when device is portrait and top down [only if using rotation sensor]

-Added more auto-filled details to support emails

-Fixed turn-off-by-proximity exception for manual toggle if something already in proximity

-Show launcher icon correctly on Android 8

-Fixed free tilt angle set to 50deg instead of 45deg

-Don't show notification badges/dots

What do you guys think of the more prominently colored buttons?
[Android Apps and Games] TNSMANI:
They are prominent :p but nice. This colour jumps out. Thank you!
[Android Apps and Games] Nitz327:
I didn't notice the button color to be honest :silly:

But I looooove the new "while apps in foreground" setting. :good:
[Android Apps and Games] Flyview:
I can't decide between the attached. I really like the clean look without the buttons at all but I'm afraid it's no longer obvious what you can click and what you can't.
[Android Apps and Games] Nitz327:
Oh I see what you mean now. Yea it's not as obvious without the buttons. I'm so used to how it looks with them that I'd choose them if I had the option. You could always make it an option? Not sure how much work is involved to do that haha.
[Android Apps and Games] DMagister:
On the oneplus 3, oos 5.0.1 the KinScreen lost movie detection. After to switch on/off it's working again but in sometime no movies detection is working.

5.0.0 beta 2.

P.s. it's look like the power saving mode. I set to exclude the KinScreen from power saving and now it working... The last 1-2 hours at least.
[Android Apps and Games] Flyview:
If it was happening often then yea that's probably the case.
[Android Apps and Games] DMagister:
Several times a day. Without power saving too :(
[Android Apps and Games] Flyview:
Damn. My best guess is the phone just doesn't allow a service that much time registered to a sensor, although I do unregister with every screen off. I haven't personally seen this issue since my Nexus 5, and even then it would happen at most every few weeks! Can you use the other keep-on options?