Weird message. What is it?

[touch_rules]

This solved the issue for me.
Below is a transcript from online help with Samsung:

Valerina: Let's try to troubleshoot the issue by performing Wipe cache partition. Wipe cache partition will recycle the internal circuit of your phone and it will delete unwanted files. Shall I proceed with the steps?

Visitor: no modifications, no root

Visitor: sure

Valerina: 1 Power the device off (remove and re-insert the battery).

Valerina: 2 Press and hold the Volume Up key and the Home key, then press and hold the Power key.

Valerina: 3 When the device vibrates; release only the Power key.

Valerina: 4 When the Android system recovery menu displays; release the Volume Up and the Home key.

Valerina: 5 Navigate with the Volume keys to the Wipe all cache .reset option and press the Power key to select.

Valerina: 6 press the Power key to reboot system now.

Visitor: rebooting now

Visitor: That seems to have worked normally it pops up on reboot

Edit**This also magically solved my issue with logging into netflix

Did this and then turned off wifi and turned wifi back on. I immediately got the notification again. This is bogus. Paid enough for this phone not to have silly issues like this.

Thanks anyway.

 

[rivencap]

Did this and then turned off wifi and turned wifi back on. I immediately got the notification again. This is bogus. Paid enough for this phone not to have silly issues like this.

Thanks anyway.

Ya, when I rebooted a 2nd time I got the notification again. It's so weird how this is poping up all of a sudden. What a icky bug.

Palm Treo line > Blackberry line > Samsung Galaxy S line > NOW - the Samsung Galaxy Note 3

 

[Dronak]

I tried using the App Ops menu to turn off Knox Notification Manager's "post notification" permissions, but the stupid message popped up again after I did, so it looks like that alone isn't going to solve the problem. The other two permissions it has still say they've never been used. I turned them off now, too, but doubt it will help. I can go into the application manager for it and clear cache, clear data, and/or force stop it, but whatever combinations of that I've tried so far hasn't managed to stop the notifications. Can anyone clarify what the cache-clearing process Silkwrm posted does? Am I going to lose any apps or app data if I wipe the cache using that method? I have only limited experience using things like system recovery. And if it may not work, like it didn't in touch_rules' case, I'm not sure it's worth trying if it's going to wipe out stuff I'd rather keep. Sprint and/or Samsung really needs to do something about this. BTW, there is a fairly new thread about this on Sprint's forums at https://community.sprint.com/baw/thread/138878 if anyone's interested in seeing what happens over there. Sometimes Sprint reps do respond, and while their replies are not always the most helpful, it is an official source, coming from the carrier.

 

[touch_rules]

I tried using the App Ops menu to turn off Knox Notification Manager's "post notification" permissions, but the stupid message popped up again after I did, so it looks like that alone isn't going to solve the problem. The other two permissions it has still say they've never been used. I turned them off now, too, but doubt it will help. I can go into the application manager for it and clear cache, clear data, and/or force stop it, but whatever combinations of that I've tried so far hasn't managed to stop the notifications. Can anyone clarify what the cache-clearing process Silkwrm posted does? Am I going to lose any apps or app data if I wipe the cache using that method? I have only limited experience using things like system recovery. And if it may not work, like it didn't in touch_rules' case, I'm not sure it's worth trying if it's going to wipe out stuff I'd rather keep. Sprint and/or Samsung really needs to do something about this. BTW, there is a fairly new thread about this on Sprint's forums at https://community.sprint.com/baw/thread/138878 if anyone's interested in seeing what happens over there. Sometimes Sprint reps do respond, and while their replies are not always the most helpful, it is an official source, coming from the carrier.

Thanks for the link from sprint. I'll add that to my threads to watch on this. Clearing the cache in recovery will not get rid of anything. You don't lose anything at all. In fact, with other phones I've had I've cleared the cache from time to time to clean up buggy behavior. Just be careful you don't select the factory reset option instead.

As far as getting it to stop until next boot goes, next time it appears long press the notification in the pulldown and go to app info. Clear data, then clear cache, then force stop the app. That has worked for me, until next reboot that is.

 

[Caddyman46]

Interesting this bug hasn't been stepped on yet.....like an annoying nasty roach.

For the adventurous my method tho long winded it is.....I still haven't seen the shield since I did it.

Sent from my stock/rooted MJ4 blazing fast beastly Galaxy Note 3

 

[Dronak]

For the adventurous my method tho long winded it is.....I still haven't seen the shield since I did it.

If I'm not mistaken, the method you described requires root. Not all of us have rooted our phones, so some of us are looking for a solution that will work without requiring root.

I've been chatting with @sprintcare on Twitter about this (and other things), and the latest I got from them was: "Clear new aps. Go to security in general & uncheck verify apps. Then powercycle. Then recheck verify apps." I can't remember installing any new apps in the past few days, so I skipped the app part. I did the rest, turning on verify apps as soon as I could get to the settings menu, and the message came up again. So this method appears to have done nothing useful. I replied suggesting that this problem may need more than some setting changes to fix. I really hope they're taking a serious look at this -- why it happens and how to stop it if there's no real good reason for it.

Yes, things like clear data/cache in the app make the notification go away, but it's temporary, as already noted. I'm going to try something else, but not reboot now to test (I've got to get to work soon) -- I'm going to use the Android Assistant app I downloaded from the Play store to kill Knox Notification Manager on startup. Force closing the app basically kills it, right?, so maybe if this app can successfully kill it on startup, I won't see the messages anymore. We'll see later on, I guess, the next time I need to reboot. I just thought I'd toss this out there. If others try this out before me, please report back and let us know if it appears to be successful. Thanks.

 

[rivencap]

If I'm not mistaken, the method you described requires root. Not all of us have rooted our phones, so some of us are looking for a solution that will work without requiring root.

I've been chatting with @sprintcare on Twitter about this (and other things), and the latest I got from them was: "Clear new aps. Go to security in general & uncheck verify apps. Then powercycle. Then recheck verify apps." I can't remember installing any new apps in the past few days, so I skipped the app part. I did the rest, turning on verify apps as soon as I could get to the settings menu, and the message came up again. So this method appears to have done nothing useful. I replied suggesting that this problem may need more than some setting changes to fix. I really hope they're taking a serious look at this -- why it happens and how to stop it if there's no real good reason for it.

Yes, things like clear data/cache in the app make the notification go away, but it's temporary, as already noted. I'm going to try something else, but not reboot now to test (I've got to get to work soon) -- I'm going to use the Android Assistant app I downloaded from the Play store to kill Knox Notification Manager on startup. Force closing the app basically kills it, right?, so maybe if this app can successfully kill it on startup, I won't see the messages anymore. We'll see later on, I guess, the next time I need to reboot. I just thought I'd toss this out there. If others try this out before me, please report back and let us know if it appears to be successful. Thanks.

Good luck!

Palm Treo line > Blackberry line > Samsung Galaxy S line > NOW - the Samsung Galaxy Note 3

 

[cheers4thechive]

You just have to accept the security terms and conditions in KNOX and it will stop popping up. It's part of the Jelly Bean 4.3 on Samsung devices. As well it was on older Samsung devices that had KNOX.

 

[rivencap]

How do you accept it. I swear what you are talking about, popped up and I accepted it. Hmmm...

Palm Treo line > Blackberry line > Samsung Galaxy S line > NOW - the Samsung Galaxy Note 3

 

[Dronak]

Unfortunately, it didn't work. I've read elsewhere that a security policy update may fix it -- see settings, general, security, I think the option is in there -- but I haven't been able to force one to happen yet.

Yes, please clarify these security terms. I didn't install KNOX, so I don't know what you're suggesting I accept.

 

[Dronak]

Sorry for two posts in a row, but I thought this was worth bumping the thread. Over on the Sprint forum thread about this, a Sprint Product Ambassador (whatever exactly that means, but he's got a Sprint logo by his avatar) said, "We are aware of this issue and working on a fix. The error is is erroneous and related to how KNOX perceives WiFi data streams. Turn off WiFi and it goes away." There's a reply from someone who says he/she has the problem without using WiFi, so I don't know. But I think the main info here is (1) Sprint knows about the problem, (2) Sprint knows a fix is needed, (3) Sprint is working on a fix, and (4) this is a false notification, and thus a type of bug rather than a legitimate problem all of us with this issue suddenly started experiencing. While there's not ETA on the arrival of a patch (of course), let's hope it doesn't take too long.

 

[Ntchwaidumela]

I just started getting this message today, oddly enough, after I saw this thread. I didn't actually install Knox, so I'm not sure why it's triggering messages, if that is what's happening here. And the app titled "KNOX Disabler" requires root, so that's not a solution for me. Are there other alternative fixes? If anyone finds one, please let us know. Thanks!

Knox disabler no longer requires root.

Sent from my SM-N900P using Tapatalk

 

[Dronak]

FWIW, I think I read somewhere that this problem could possibly be related to security policy updates. When I checked in my settings for that option, I saw that it was turned off so I wasn't getting them automatically. I turned it on a few days ago, I think, and just now saw a notification that I got an update. Clicking it says, "The latest security policy has been applied. - Current version: 0012". I don't really know what these updates do or how they're used, but if the KNOX prevention information message is somehow related to them, maybe this update will help solve the problem. If not, then I guess we'll have to keep waiting for Sprint/Samsung to push out the update they said they're working on.

 

[TenshiNo]

Just a quick note, this is a common problem for rooted phones, especially if you use Titanium Backup to restore an app. Basically, Knox sets special permissions on data that an app creates that further prevents apps from accessing data created by other apps (or apps trying to access "system" files). This is actually part of the SELinux framework. Not sure why this would happen with using apps normally, but this is not something that's generally part of Android itself, so some apps may be creating files the "wrong" way.

The fix, found over at XDA involves running a special command from a terminal emulator on your device to "reset" these markers. Unfortunately, this *does* require root. But, if you're rooted, running this command (after "su") should fix the problem:

restorecon -R -v /data/data

Make sure you use the capital "R".

Here's the link to the XDA page:

Fix for Titanium Backup restoring with data - xda-developers

 

[Dronak]

Just a quick note, this is a common problem for rooted phones, especially if you use Titanium Backup to restore an app.

Perhaps, but I and probably at least some others are not rooted. Sprint on their forum has said that it's an erroneous message based on how KNOX is viewing WiFi streams and are working on a fix

 

[TenshiNo]

Perhaps, but I and probably at least some others are not rooted. Sprint on their forum has said that it's an erroneous message based on how KNOX is viewing WiFi streams and are working on a fix

Yeah, I found more info on this after posting that. Not really sure what to tell you as for fixing it. Rooting of these phones is very easy and can be done without tripping the "custom rom counter", if anyone is interested:

Sprint Galaxy Note 3: root MJ4 update by using Kingo app | AndroMods

This is generally pretty safe, so long as you follow the instructions to the letter.

 

[TenshiNo]

I just found this info (supposedly from Google) about fixing the "Shield" notification:

The Google team of specialists advise the following to have you clear the cache and data of the Google Play store and Download Manager as well as uninstalling updates manually.

I've included the steps they provided on how to do so bellow:

1. Visit Menu > Settings > Applications > Manage applications
2. Tab over to "All"
3. Select the Play Store app, and then tap "Clear cache" and "Clear data"

For the Download manager:

1. Visit Menu > Settings > Applications > Manage applications
2. Tab over to "All"
3. Select "Download manager," and then tap "Clear data" and "Clear cache"

Please note that after clearing the Google Play Store app data, if you have set a PIN code and/or a content filter, you'll need to re-apply these settings.

In order to temporarily uninstall updates to the Google Play store app. To do so, please follow these steps:

1. Go to "Home" > "Menu" > "Settings" > "Applications" > "Manage applications"
2. Touch the "All" tab
3. Scroll down and select the Play Store app
4. Touch "Uninstall updates"

This will revert Google Play to the original version that came with your device. Google Play should automatically self-update to the current version within a few days - there's no way to permanently uninstall updates. However, you can perform the following steps to ensure the latest version of Google Play is updated properly:

1. Launch Google Play
2. Switch to the Home screen
3. Wait 5-10 minutes for the app to self-update
4. Re-launch the Google Play store app

To check your version of Google Play:

1. Go to Settings > Applications > Manage Applications
2. Touch the All tab
3. Scroll down and select Play Store

If you continue to experience issues after temporarily uninstalling updates and clearing the cache and data, please contact Google at (855) 492-5538 for further trouble shooting.​

Here's the link to the post on Sprint's community forums:

https://community.sprint.com/baw/thread/136227?start=29&tstart=0

Please post and let everyone know if it works after you try it. I'm not having the problem myself, so I haven't been able to test.

 

[anon(7604117)]

This worked for me -- message is now gone for several days, after having appeared at least a few times daily for about a week. Bizarre that the fix was in a program I've never used & probably never will.