Screen Overlay Detected - Samsung Galaxy S7 Edge Questions and Answers

Hi guys, I have recently updated my Galaxy S7 edge to the lastest software version G935FXXU1BPG3 (August Security Patch) and have received this error.
I tried disable all of the screen overlay application and the error is gone. I suspect the app that is causing it is Velis Auto Brightness and Network Monitor Mini.
However, in the previous software version (July Security Patch), I have both of these applications enabled for screen overlay and everything is working as it is. The new update has caused me to disable these apps so that I can allow permission for app to access location, contact, etc.
Is there anyway to fix this to allow the auto brightness and network monitor mini to work correctly without the screen overlay detected error?
How I wish I can go back to the previous software version so that I do not have to disable these applications for it to work.
Thank you for your help.

If your phone is rooted you can download module called no screen overlay dictation it will fix it

I moved to a unrooted S7E with MM and I'm also getting the screen overlay questions. And I just don't get what they want me to do.
For example, from the Telegram app I want to send my location. Maps starts and I'm asked If I want to grant Telegram access to my location.
I want to press 'Allow' but then the "Screen overlay detected" dialog appears and I'm redirected to a list.
So what app do I need to allow permission to appear above other? Not telegram because that one already has it, so it must be Maps then? But Maps is greyed out?
Or is it some kind of system app (Settings? System UI?) that needs te permission to appear above Maps?
It's quite confusing :\

Related

Can't enable storage permission for gmail - "screen overlay detected" error message

Can't enable storage permission for gmail - "screen overlay detected" error message
New Nexus 6p, latest OTA upgrade.
Tried saving a file from an email attachment on Gmail app, the system asked me if I wanted to allow storage access permissions, I said yes, and another popup message said:
Screen overlay detected
To change this permission setting, you first have to turn off the screen overlay from Settings > Apps
When I go to these settings it shows the setting (YES or No) for each individual app. Gmail wasn't in the list of apps.
Any idea what to do?
I realized I should have posted to Nexus 6P Q&A, Help & Troubleshooting subforum instead. Can a moderator please move the thread and delete this message? Thanks
Just had this. Do you use lux or something like it? I unchecked lux from screen overlay, and was able to download my attachment. Now I dont know if that means that lux won't work as well, but....
EDIT: Yes, it completely stops lux. Is there a way to get lux not to interfere with other things?
EDIT 2: In Lux use alternative overlay in advanced and both work now.
Thanks, it was indeed Lux. After disabling permission for screen overlay to Lux, it stopped and wouldn't start again. I uninstalled and reinstalled it and it worked. I can't find the setting you mentioned (maybe because I have Lux lite?). Anyway, they both work now (for now!). Very strange though.

Questions regarding N preview

1. Can it be used as a daily driver ?
2. Does the N bootloader and radio work with and can boot existing marshmallow custom Roms and twrp 3
3 Will dirty flashing work ( earse data but leave data/media intact before flashing preview using fastboot)
4 What's wrong with twrp on N, I read some people saying that twrp asks a password or something. So pls tell me about it
Thanks
Here are all the known issues with Android N
Platform Issues
Performance and battery
System and app performance is known to be periodically slow / janky, and device may become occasionally unresponsive. These problems may become more acute with prolonged use.
Battery life may be regressed in this release for screen-on and screen-off use cases.
Dialer
Dialer app does not support Direct boot. This will be addressed later in N Developer Preview.
Voicemail playback does not work.
System UI
Some new or modified strings in the system UI are not translated to all languages.
Overview UI is still in development, and subject to change. For example, we intend to remove the timer that appears when the user switches between apps.
Settings controls and toggles may be slow or appear to be unresponsive.
Visual design of notifications is subject to change.
In the Gmail app, direct archiving of emails included in a notification bundle does not work properly.
Android for Work
Work Security Challenge
After migration to N, or after the user creates work profiles, work profiles can't create keys in the keystore until the user changes their pattern, PIN, or password, or sets up a Work Challenge.
In Direct boot mode, applying the passcode restrictions to the device causes the work profile to be unlocked, even though the device is locked. This makes the work profile accessible even though it should be protected by the device lock screen.
When the user enters a wrong password and pin, the system does not display any informational message; instead, it only clears the input field. This issue does not affect pattern or fingerprint input.
On a tablet, the background displayed with the work challenge is disproportionately small.
The version of Google Apps Device Policy that is bundled with N Developer Preview does not yet support the Work Profile Security Challenge feature. Developers should instead use TestDPC to test this feature.
Always On VPN
If Always On VPN mode is turned on, but VPN is not available, apps not specified as exceptions to the Always On policy connect over the ordinary network. Unless specified as exceptions to Always On VPN policy, apps should be offline if they have no VPN connection available.
When Always On mode is on, a VPN connection is not established after a device reboots into Direct boot mode, even after the user unlocks the secure lock screen.
Improved Contacts
Bluetooth PBAP/MAP devices do not display Caller ID for work contacts. The next release of Preview resolves this issue.
Work Mode
The Google Now Launcher does not display whether Work Mode is on or off. The Launcher also does not show app suspension state.
After the user turns Work Mode off and on, the system no longer shows Work profile app widgets, such as Calendar.
Suspend Packages
Device admins can suspend critical system packages, which may lead to unexpected behavior, such as placing calls despite the Telephone disabled dialog’s being displayed.
Other
The Settings app crashes on launch if DISALLOW_MOUNT_PHYSICAL_MEDIA is set to true when the user inserts physical media such as an SD card.
The DPM.setPackagesSuspended state does not persist when the user uninstalls and then reinstalls an app. Either the app should remain suspended after uninstall/reinstall, or suspended apps should not be uninstallable
The first check-in in a Work Profile takes several minutes to complete. This may cause the device to take longer than normal to be visible in the Play EMM API.
Notifications from Work Profile apps are not visible to notification listeners installed in the personal profile. As a result, the system does not display Notifications as expected.
The version of Google Apps Device Policy that is bundled with N Developer Preview does not yet support the Work Profile Security Challenge feature. Developers should instead use TestDPC to test this feature.
Keyboard
Bluetooth pairing between keyboards and Android devices may be unstable.
Video
Video playback may lag and show interruptions.
Wi-Fi
Wi-Fi has undergone some refactoring which may change API corner case behavior. Specifically, applications which attempt to connect to specific networks, or attempt to reconnect to networks should retest.
The legacy DHCP client has been removed from the platform. The only DHCP client that the platform supports is the DHCP client introduced in M.
Direct boot
NFC doesn't function until first unlock.
When a phone with Bluetooth enabled is restarted, Bluetooth does not turn on automatically. You must manually re-enable Bluetooth.
Under some circumstances, the default ringtone may not sound for phone calls and messages. This behavior is fixed in the next N Preview release, with one exception (and workaround):
On a device that is not freshly wiped--one that has been booted at least once since being set to direct boot mode--the default notification ringtone does not sound. The user can work around this issue by manually selecting a ringtone from Settings.
Direct boot is not enabled by default on devices running an N Developer Preview build. To enable direct boot for testing and development, go to Developer Options and tap Convert to File Encryption. In this dev preview, this requires a factory reset to repartition and reformat your device for File-based Encryption.
Picture-in-picture for Android TV
The PIP integration in the Recents UI is not finalized, and is subject to change.
The animation of the PIP window is not smooth. Future releases of the Preview will improve this.
Future releases of the Preview will improve upon the visual design and layout alignment of PIP.
Bug reports
Bug reports do not always complete successfully (as a workaround, sometimes they can still be accessed through the bug report document provider in internal storage).
Split-screen Multi-window
Apps may experience crashes and unexpected UI behavior when put into split-screen mode. These are app issues that must be fixed by the app developer.
When an app targets a version of the Android platform earlier than N, the App may not work with split-screen toast may appear multiple times.
Long-pressing the Overview button while using an app with a fixed orientation may produce unexpected app behavior.
Apps may flicker while resizing.
Animations are not yet final.
Input method
Google Keyboard unexpectedly falls back to the generic Google keyboard when Use system language, but Google Keyboard doesn’t support any of the languages selected in the system-language preferences. It should fall back to American English.
You can work around this problem by adding at least one language that Google Keyboard supports.
Accessibility
TalkBack exhibits issues with features including Notifications, Quick Settings Tiles and Multi-window display that may cause system crashing or lack of spoken feedback from TalkBack. Future releases of the preview will address these issues.
N has been pretty stable for me so far. Dark mode took a few taps to get it to turn on and a few slow downs in the camera app one time, but mostly pretty good. Way better than some custom ROMs (or even some stock ROMs on crappy phones) I've run back in the day.
Have a good one!

"screen overlay detected" even when all are switched off

So, I've just updated to the latest Pure Nexus - did a wipe and clean install - and I'm trying to get my apps set up again, but I can't grant permissions through system settings. If an app actually pops up and requests a permission, I can allow it; but for some apps, this doesn't happen. Home Remote Control, for example, won't request the storage permission it needs to access my ssh key. So I go into settings->apps, find the app, tap permissions, try to enable the storage permission, and..."screen overlay detected". Except there is no screen overlay active. I have disabled every app's "draw over other apps" permission. I even found the "show system" option in the list and disabled all system apps' ability to draw over other apps. At this point, SYSTEMUI can't draw over anything else! And I'm still getting "screen overlay detected" when I try to change permissions. Any advice? Is there another way to manage permissions in Marshmallow (like maybe an xposed module)?
EDIT: Thought I should also mention, the issue persists in Safe Mode.
tardis_42 said:
So, I've just updated to the latest Pure Nexus - did a wipe and clean install - and I'm trying to get my apps set up again, but I can't grant permissions through system settings. If an app actually pops up and requests a permission, I can allow it; but for some apps, this doesn't happen. Home Remote Control, for example, won't request the storage permission it needs to access my ssh key. So I go into settings->apps, find the app, tap permissions, try to enable the storage permission, and..."screen overlay detected". Except there is no screen overlay active. I have disabled every app's "draw over other apps" permission. I even found the "show system" option in the list and disabled all system apps' ability to draw over other apps. At this point, SYSTEMUI can't draw over anything else! And I'm still getting "screen overlay detected" when I try to change permissions. Any advice? Is there another way to manage permissions in Marshmallow (like maybe an xposed module)?
EDIT: Thought I should also mention, the issue persists in Safe Mode.
Click to expand...
Click to collapse
Do you have twilight or lux installed?
The reason it's warning you is BECAUSE they're disabled. Enable all the toggles and the prompts will go away. You can then choose to disable one by one until you figure which app is throwing the error.
Sent from my Nexus 6P using Tapatalk
Turned out to be because GravityBox pie controls were enabled. Doesn't show up in the "draw over" list, but trips the overlay detection regardless. Disabling pie controls in the GravityBox app let me change permissions.
Hi,
Try to flash this by Custom Recovery.
http://www.mediafire.com/?ouxua6rkkagi3g9
tardis_42 said:
Turned out to be because GravityBox pie controls were enabled. Doesn't show up in the "draw over" list, but trips the overlay detection regardless. Disabling pie controls in the GravityBox app let me change permissions.
Click to expand...
Click to collapse
Thanks man. I have been going crazy for the past few days trying to figure this out lol. Just posted asking for help as well. Such a random and rare issue, that i couldnt find anything on it.

"Screen overlay detected" when no apps have overlay enabled?

So, I just got this "error" on my J5 2016 and well, the "screen overlay detected" message shows up even if there are no apps have overlay activated (happens when giving permissions, for example), I checked in settings even the system apps and disabled them, still doesn't work. That'a basically it.
Any help would be appreciated! :fingers-crossed:
Orbity said:
So, I just got this "error" on my J5 2016 and well, the "screen overlay detected" message shows up even if there are no apps have overlay activated (happens when giving permissions, for example), I checked in settings even the system apps and disabled them, still doesn't work. That'a basically it.
Any help would be appreciated! :fingers-crossed:
Click to expand...
Click to collapse
try to set permissions from Application manager if not already.

Draw over other apps setting not sticking on LG G6

I wanted to share this with everyone in hopes that my solutions helps at least one person.
I have an LG G6 running Android 8.0. A few apps I use require Draw over other apps to be turned on. One of those apps is Keeper Security, which needs permission to Draw over other apps so that its Keeper Fill feature can read the screen and go find my username/password for that website/app I am trying to login to. Since around December 2018 it has started acting 'flaky'. Even though I had enabled Draw over other apps for the app already, it kept notifying me that I needed to turn it on. After some random setting changes of turning the draw over apps setting ON/OFF, along with the Keeper Fill setting from within the source app that needs this permission, I could eventually get it to work again, but it would always break again very soon after.
As I am getting ready to go on a trip, I installed Google's Datally app. It, too, wants me to turn on Draw over other apps, but when I tap "next" to be taken to the Android settings page to enable Draw over other apps, nothing happens (I usually expect an app detects it has been enabled and gives "success" message).
So I started disabling the 3 possible suspects listed by kapil1100 in this post. I had LG's Comfort View and some Accessibility options enabled, so I turned them off and: no change.
I disabled all other apps that have permission to Draw over other apps via: Settings > Apps & notifications > Special access > Draw over other apps, and: no change.
I use Evie launcher, so I went back to the stock one: no change.
I got thinking about what else could be modifying/accessing the screen and realized that LG has custom Home touch buttons.
I went to: Settings > Display > Home touch buttons > Hide Home touch buttons and DISABLED Show lock/hide icon and then tried enabling Draw over other apps for Datally and IT WORKED!.
I was then able to turn Show lock/hide icon back ON and everything has been working as expected. I suspect that, because I had Show lock/hide icon turned on during an upgrade, something got messed up and my turning it OFF and back ON fixed the issue.
I hope this helps someone!

Categories

Resources