Surf Donkey, you're 100% correct. I can re-create the problem now. It is the locknow thing.
Major bummer.
Major bummer.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Galaxy S7
- Thread starter nviz22
- Start date
- Sort by reaction score
While this might not be exactly what you want, you can go into the accessibility settings and under hearing there is an option that says it'll light up the camera flash when you get a notification, but it also lights up the screen. So if you don't mind your camera flash lighting up as well, you could try that.
Couldn't the developer make it so that the screen just times out normally? If the app itself doesn't shut off the screen, then it wouldn't trigger the locknow thing, right...?
While this might not be exactly what you want, you can go into the accessibility settings and under hearing there is an option that says it'll light up the camera flash when you get a notification, but it also lights up the screen. So if you don't mind your camera flash lighting up as well, you could try that.
Thanks for this. The camera flashing is a deal breaker. So close.
BTW, speaking generally now... this makes "Always On Display" seem even more half baked than ever before. Samsung really ought to open this feature up to third party and make the notifications action-able.
Especially now that apps like Screen On Notification can't work without causing an incredible inconvenience with the lock screen.
[doublepost=1457986639][/doublepost]
I've emailed the developer. Let's see how he/she figures it out.
Really quite bummed about this. I liked having my phone standing on my wireless charger or even flat on my desk, and having the screen light up whenever a notification comes in. Again, ala the iPhone.
To lose this because of Marshmallow.... ugh.
I have to confess, there have been some serious hiccups to this whole S7 Edge experience, ranging from the preorder mishap to now realizing I have to sacrifice one of my most favorite features.
Not a very happy camper right now with Google or Samsung.
Hmmm. Have you tried changing the lock automatically settings? Maybe if you give it more time it will work without requiring the pass code?
Hmmm. Have you tried changing the lock automatically settings? Maybe if you give it more time it will work without requiring the pass code?
Thanks for the suggestion. Doesn't make a difference sadly.
It's clearly 'waking' the device fully and hence triggering the need for security authentication.
Sadly doesn't help you though
Totally confused here. When I get a notification my S7 Edge turns the screen on for about 5 seconds, shows me what the notification is and then goes back to "Always on" screen. I have no special apps installed. So I'm confused with your description of your issue?
The worse part is that this is built into MM. That means none of these apps that turn on the screen for notifications will work anymore without the inconvenience. Not unless they can figure it out.
This is a big lose for my Android experience.
[doublepost=1457988140][/doublepost]
Really? Mine definitely does not do that.
Is it because of Always On? Let me try it. EDIT: Nope. Makes no difference.
How is your device turning on for notifications? The whole screen lights up? And you see your normal Android lockscreen?
Does everyone else's S7/Edge do that, too?
This is a big lose for my Android experience.
[doublepost=1457988140][/doublepost]
Really? Mine definitely does not do that.
Is it because of Always On? Let me try it. EDIT: Nope. Makes no difference.
How is your device turning on for notifications? The whole screen lights up? And you see your normal Android lockscreen?
Does everyone else's S7/Edge do that, too?
I promise I'm not trying to be a wise-ass...but the Galaxy S7 does have a notification LED, doesn't? Can't it still be configured for different colors to associated with each type of notification?
It does, but that's not enough to see information as it comes in. I guess I'm greedy because I want it all and had it all with my S6.
I want to be able to see and act on notifications when they come. That means when something comes in, the screen turns on, I see the good ol' Android lock screen with the notification card, I can read a bit of it, and if I want more, I can pull down to expand, or double tap and unlock my device via fingerprint to go into it for a full response. If I don't want more, I let the screen time out. No fuss.
And if I'm not around to actually see it, and the screen times out, then I do have the LED light to alert me I have something waiting for me when I do get back to my desk or back near my phone.
Both is still achievable with the S7, but at the cost of inconvenience. Because now, if I should let that screen time out, it'll require additional security to unlock.
Very unfortunate. And if this is baked into MM, then those days are over. Unless the developers of those Screen On type apps figure it out.
Not very happy.
I was surprised that whatapp notification seem to sit in front of security and is on the front screen to read and reply without security, I had to turn it off.
I also got a new curved glass screen protector today from amazon http://www.amazon.co.uk/gp/product/B01CCY1F14?ref_=pe_385721_37038051_TE_3p_dp_1 I would say although a perfect fit its no good especially with a case as the top and bottom lift slightly reducing the sensitivity and clicks/sticks when pressed, also there is a cutout for the Sammy logo and generally the sensitivity is reduced on the edge. I doubt it will settle down in the next day or two.
I also downloaded the extra edge apps for call logs, messages and files, the call logs and sms often have to refresh and take good 5 secs to reappear not good IMO, the files also locked up a few times, I would wait for next revision.
I also got a new curved glass screen protector today from amazon http://www.amazon.co.uk/gp/product/B01CCY1F14?ref_=pe_385721_37038051_TE_3p_dp_1 I would say although a perfect fit its no good especially with a case as the top and bottom lift slightly reducing the sensitivity and clicks/sticks when pressed, also there is a cutout for the Sammy logo and generally the sensitivity is reduced on the edge. I doubt it will settle down in the next day or two.
I also downloaded the extra edge apps for call logs, messages and files, the call logs and sms often have to refresh and take good 5 secs to reappear not good IMO, the files also locked up a few times, I would wait for next revision.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Honestly, I'm surprised some form of screen on for notifications wasn't developed sooner from Samsung to be part of TouchWiz. It's always been on the iPhone.
Have you figured out why and how your screen turns on for notifications without a third party app?
Whatsapp notifications light up the screen no problems then goes back to the always on display after a few seconds. Perhaps the developer could apply a similar method to the app you are having issues with.
Yeah, I emailed him a few times with all the info I've gathered here. Hopefully he can update it and find a work around.
I'm not happy with the screen not able to light up when I get a notification.
But I'm also not happy that in order to allow that to happen, I have to deal with entering my pattern when it should just be asking for my fingerprint.
This is not a happy day for me and Android. I'm quite soured by this.
Yeah, its not MM though. This has been around for a while. Old bug that needs to be fixed. Here is a complaint with it related to Smart Lock
https://code.google.com/p/android/issues/detail?id=79735
The question is why this is being called in your App. I would be curious why they are doing this specifically, as it is the cause.
if (dpm.isAdminActive(deviceAdmin) && isDeviceLocked()) {
mLogger.debug("Device is an active admin and device is still on lock screen, locking");
dpm.lockNow();
}
https://github.com/lkorth/screen-no...ennotifications/helpers/ScreenController.java
Why are they forcefully shutting off the screen here?
What's strange is that the same app, Screen On Notifications, works perfectly on my Galaxy S6, which is on Lollipop. I've always recommended it to people who were looking for a similar feature. Never had to input my secondary unlock method after a screen on notification.
OK, something permission-wise changed with MM then. Well, you could always fork the app developers code on github, comment out that line, and build a new APK and see what happens.
Boom. Found an alt app that does the same thing without the lock screen issue: https://play.google.com/store/apps/details?id=de.nullgrad.glimpse
Tested it a bunch of times.
Screen On Notification has to update their app.
EDIT: Serious though, thanks for all the help earlier from everyone that chimed in.
[doublepost=1457993096][/doublepost]
I don't know why or how Glimpse app works. But it does. I get notification, the screen turns on to show me, if I let it sit and the screen goes off, I can still turn it on and unlock with my fingerprint. No more inconsistent additional security messiness.
Thank goodness.
https://play.google.com/store/apps/details?id=de.nullgrad.glimpse
Tested it a bunch of times.
Screen On Notification has to update their app.
EDIT: Serious though, thanks for all the help earlier from everyone that chimed in.
[doublepost=1457993096][/doublepost]
OK, something permission-wise changed with MM then. Well, you could always fork the app developers code on github, comment out that line, and build a new APK and see what happens.
I don't know why or how Glimpse app works. But it does. I get notification, the screen turns on to show me, if I let it sit and the screen goes off, I can still turn it on and unlock with my fingerprint. No more inconsistent additional security messiness.
Thank goodness.
https://play.google.com/store/apps/details?id=de.nullgrad.glimpse