To take a screenshot on this phone, I must tap the square button on the bottom right. This gives me 2 options: Screenshot and Select. They are both always greyed out, and so clicking on either one does nothing. I don't even get an error message.
Interestingly, I have found a crappy work around. If I reboot the phone, the options are not greyed out, and they actually work, BUT for only like 5 to 10 minutes, then at some point, they are once again always greyed out. It doesn't matter what app or what I have on the screen, even just trying to take a screenshot of my Settings menu, for example, the two options are greyed out.
Any suggestions where to start to narrow this issue down? Obviously, something during startup is disabling it since it works for a few minutes.
Phone Details:
Android 11
Magisk 25.2 (25200) (33)
Zygisk - LSPosed v1.8.5 (6649)
Universal SafetyNet Fix v2.3.1 by kdrag0n
Systemless Hosts v1.0 by Magisk
Sounds like global power management may be causing it. Not sure what Pixel call it. A settings issue if so. You'll need to either disable it or set the app that's getting shutdown as an exclusion to this service.
Developer options> standby apps; if all bucket states are showing as active, power management isn't enabled. If you have apps showing various bucket states, it's running.
Perhaps a 3rd party app; try in safe mode to rule that out. Regardless track down the root cause otherwise even with a factory reset it's likely to reoccur.
Related
Under Settings; Apps there is no option for toggling 'Installing from Unknown Sources". This toggle is usually found on Android systems but the Nook color has it disabled.
Does anyone know how to turn option on, so it appears in the Apps section?
just open NookColor Tools it should be the first option.
In my case, the box was checked, but I still could only install from the market. After unchecking and rechecking the box, I was able to install other APKs.
NCTools
I tried the suggestion above to uncheck - check the box but that didn't work. When I uncheck the box, close NCTools abd reopen NCTools the box is still checked. Anyone with another suggestion?
I didn't close NCTools after unchecking, I just unchecked and rechecked in the same instance, then installed the APK. Sometimes it helps to power-cycle the device too. Hold down the power button until the device turns off (don't let go of the button to press the "Power Off" option on the screen). Then hold it down for a couple of seconds to power it back on again.
Samsung Galaxy S6: Wanted to update from Marshmellow (rooted with SU) to Nougat.
Unrooted, updated to Nougat and rooted with SU 2.78 and used Titanium Backup to re-install some stuff and mainly data back into Nougat.
Everything worked good but while reading a bit more i found that there was a newer version of SU then the one i had used (2.82 instead of 2.78).
So i uninstalled SU 2.78 and installed 2.82 instead.
Then i noticed that some stuff didn't work anymore, one thing was toggling NFC on or off through Tasker, it always came with an error that there was no root for System+ in Secure Settings.
But whatever i tried, i could not get System+ detecting root in Secure Settings, also not when trying a few fixes i found on the internet (ex: https://dammit.nl/20160406-how-to-f...oid-devices-with-supersu-systemless-root.html).
Went back to SU 2.78 but that didn't work our anymore either.
While gathering information (i don't follow the progress on rooting etc... because lack of time) i stumbled on Magisk for doing the root.
Unrooted SU and re-rooted with Magisk 14.2
Then System+ in Secure Setting could be enabled again and i could toggle NFC through Tasker again without issues.
But, tapping on the Power Toggles NFC symbol still brings me to the Nougat settings page to set NFC from there (and then the Power Toggle NFC status isn't updated) instead of toggling NFC direct like it used to do before with SU 2.78 (on Marshmellow and the first install of Nougat with SU 2.78).
Looking for a solution for this i found this on the Power Toggles website (http://powertoggles.com/help/?e=17).
It says that you always are directed to the phone's settings to set either GPS or NFC and only works directly if you have root.
Well, it works fine for GPS but for NFC. Power Toggles see's root for the GPS function but not for the NFC one... weird.
Removing Magisk and re-installing it doesn't help, nor does going back to whatever version of SuperUser so i'm still looking for a solution to toggle NFC directly from Power Toggles.
My Tasker Root Support module have been reported to make Secure Settings recognise root. You could give that a try...
Thx, i'll give it try but this then means i have to go back to SuperUser for root instead of Magisk?
The actual problem is that Secure Setting does detect root now when rooted with Magisk but that Power Toggles only partly thinks is not (works fine GPS toggle, not for NFC).
I guess the problem lies more on the Power Toggles part (but then that's a wild guess) which only seems to see half of a root so to say... LOL.
Toggling NFC with Power Toggles works fine for me. With Magisk.
And no... You'll have to stay on MagiskSU to use Magisk modules. SuperSU isn't compatible with Magisk.
Installed the module in Magisk (double checked if it's activated), unfortunaly no joy...
Confession: Far far away in my brain there is a small spark that says that's is't some sort of setting somewhere and that i had the same problem once in the past (long ago) but since my brain is getting rather old and that spark would refuce to become firework...yet.
I did make a small Tasker task to update the Power Toggles bar on changing NFC status. So i can already check on the PT bar in what status NFC is in even if i changed it through regular settings.
Found also this:
Note: starting with android 4.2, system access is no longer required for any functionality. Root should be enough.
If your device is rooted you could install the Power Toggles app as a system app. You can use apps like Titanium backup or /sys/app mover or any similar app for this purpose.
Installing the app as system app, enables protected functionalities like one-click GPS/NFC toggle or Airplane mode toggle.
Wondering if it could help i tried to installing Power Toggles as system app. However, this didn't work. First i used /sys/app mover but this came also up with error: could no remount/system.
Then i tried Titanium Backup but this kept on going in a loop. After stopping TB after +/- half an hour and a reboot the Power Toggles shortcut was gone but that was it. Retried a second a time and this time TB worked itself through the process quickly but Power Toggles wasn't moved and was not a system app. To be continued...
Noticed a second little glitch with Nougat for the Power Toggles, just a NFC now opens de setting instead of toggling, the same happens with the brightness slider toggle (didn't tried that before).
On Marshmellow this opened only the brightness slider, on Nougat is does the same as with the NFC, it opens the settings and goes to the brightness slider there.
After fiddling around with a bit i thought of reversing the firmware back to Marshmellow to try but this came with an error and de Galaxy S6 locked up. Tried a second time, same issue although the firmware should be valid and the checksum is OK (got it from SamMobile).
Re-installed Nougat (a 1st update now), but the Power Toggles still open settings for NFC and Brightness Slider.
Workaround for the Brightness Slider is using a widget to open a 3th party brightness slider. This works noce but the Power Toggles bar is not as nice (even icons) as before.
Are you sure that Power Toggles have been granted root access? Check the superuser section of the Manager...
Yes it has, just double checked on the SU settings in Magisk.
If it doesn't, tapping the GPS/Location or Mobile Data symbol on the Power Toggles bar also opens up the settings pages like with NFC and the brigthness slider.
And whan it has been granted root access, it doens't do that for GPS/Location or the Mobile Data toggle but still for the NFC and brightness slider. That's the big issue. Whay does it work only partially? It would be easier to solve it was the same for every toggle for which it needs root access.
Like I said previously, there are no such issues on my side with Power Toggles...
Toggling NFC and bringing up the brightness slider works without a hitch.
There must be something about your setup.
Didgeridoohan said:
There must be something about your setup.
Click to expand...
Click to collapse
That's what i'm still thinking too but can't pinpoint it (for now).
I'll keep on diggin'...
Managed to make the Power Toggles app a system (with Titanium Backup) but... no joy.
Unrooting makes every toggle that has no direct action go through the settings page as it is intended to do, rooting again still leaves the NFC and brightness slider in an unrooted action state.
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
*gentle push*, because the problem still remains
katerlouis said:
*gentle push*, because the problem still remains
Click to expand...
Click to collapse
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
fehrcomp said:
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
Click to expand...
Click to collapse
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
katerlouis said:
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
Click to expand...
Click to collapse
Yes! On my device Mate 1o Pro, it was Talkback as well that ¨obscured a permission request¨.
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
help please
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
YEESSSS!!! Thank you for mentioning this, I never would've make that connection and that's exactly what it was for me! I guess those pics weren't all that smart after all ?
Panshu Mehra said:
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
Click to expand...
Click to collapse
I have an Honor 8 pro and I'm facing the same issue. I've disabled all apps which draw on the screen and restarted my phone too.
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Wow, good call. I was having this same issue. Thanks!
Fix #2 - if it works
i was messing with my Samsung Galaxy J7 Core J701F/DS and I was trying to figure out your problem also because i got the same problem as yours so the thing that worked for me is going to Settings (Nougat 7.0/1)> Apps> 3-dot menu/optionsl settings/other settings> Special Access> Apps that can be on top> Disable all apps like literally disable them all and try to debug your phone again...if it works, enable apps in that setting one by one and repeat debugging process. If it doesnt work, disable the last app you enabled, and if it works again...that is the app that is doing the dirty work...mine was not in the system apps it was one of my apps which is AZ Screen Recorder lol....(why the app that is being used everyday need to be disabled....)
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Omg thank you so much for this. It was driving me bat**** crazy. I tried everything didnt even think this would cause it.
katerlouis said:
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
Click to expand...
Click to collapse
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
kapil1100 said:
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
Click to expand...
Click to collapse
This put me on the right track.
I have an LG G6 running Android 8.0. My Keeper Security app needs permission to Draw over other apps and since around December 2018 it has started acting 'flaky'. The app would warn me that I need to turn on this permission, but when I clicked "OK" in the Keeper app to take me to the Android setting for the app, it was always turned on. I could turn it ON/OFF, along with the setting that needed this permission in the Keeper app (called Keeper Fill) and 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. 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!
I don't really wan't a custom rom, but do have Magisk and TWRP. It's the last thing I don't like about this phone (just came from the Pixel 2 XL).
Try this:
In Developer Options, search for Absolute Volume, then turn it off.
I found "Disable Absolute Volume" and tried it. Still when the phone turns back on the pop up is there the moment I turn up the volume.
Yeah It seems that is not a permanent solution... You could try to automate it with tasker and autoinput, but i dont think is worth the effort...
Yeah I agree, Thanks for the info.
samfix from xda labs used to cope with it but no update since pie..
Yeah, I tried it and no go on pie. Its a really small thing, just the last thing that bugs me.
i would add the mess with dolby atmos. I think it turns off randomly.
TakamineSubasa said:
Yeah It seems that is not a permanent solution... You could try to automate it with tasker and autoinput, but i dont think is worth the effort...
Click to expand...
Click to collapse
Well, if money is not the problem, you can do it with Tasker and AutoTools and it works just fine. I don't have root. Set it up once and forget it:
Just google "disable-safe-volume-warning-no-root-required" (geez, you can't even share a link to tutorial)
I haven't found easier solution for non-root. Sorry if OP looks for something root-only...
It is available in Stock ROM, no root required.
Settings > Sounds and vibration > Volume
Tap the three vertical dots in the top right,
Select "Media Volume Limiter" (It's the only option on my phone')
(Now here comes the counter-intuitive part)
Turn it on.
Set the "Custom Volume Limit" all the way to the right.
pTeronaut said:
It is available in Stock ROM, no root required.
Settings > Sounds and vibration > Volume
Tap the three vertical dots in the top right,
Select "Media Volume Limiter" (It's the only option on my phone')
(Now here comes the counter-intuitive part)
Turn it on.
Set the "Custom Volume Limit" all the way to the right.
Click to expand...
Click to collapse
is it possible that after a reboot the setting resets?
if so, there are modules like gravity box for edxposed that can change it for good. maybe others too.
bober10113 said:
is it possible that after a reboot the setting resets?
if so, there are modules like gravity box for edxposed that can change it for good. maybe others too.
Click to expand...
Click to collapse
Wherever limit you set (in the case, full volume) persists.
I have just rebooted my phone and the limiter is still on, and set to full.
pTeronaut said:
Wherever limit you set (in the case, full volume) persists.
I have just rebooted my phone and the limiter is still on, and set to full.
Click to expand...
Click to collapse
ok then they must have changed it in pie since i remember users complaining of it being reset after each reboot( probably an oreo issue)
pTeronaut said:
It is available in Stock ROM, no root required.
Settings > Sounds and vibration > Volume
Tap the three vertical dots in the top right,
Select "Media Volume Limiter" (It's the only option on my phone')
(Now here comes the counter-intuitive part)
Turn it on.
Set the "Custom Volume Limit" all the way to the right.
Click to expand...
Click to collapse
That STILL gives you the warning once after every reboot.
BUT! If you use systemui tuner you can actually, permanently, disable it. Seems to be the only way without root.
@Delano.888 Yeah, just had that experience at the very moment that you posted that.
Thanks for the pointer to SystemUI Tuner.
i knew i wasn't crazy....
Does anyone know how to get rid of this with Tasker? The old method no longer works, and I am afraid I am going to wreck my car trying to click the ok on the screen when I need the volume up. Please help! I've literally tried everything from granting securetask device ownership rights etc... I can even watch the setting change on my Note 9 without affecting the warning whatsoever. Any ideas??? Also, what exactly does deprecated mean?
Yes there is. I have done it multiple times. You will need a PC and Magisk Manager though. Tried it worked on Android 10 too.
The solution is with Smali Patcher. It makes Magisk module for individual phones via PC when being connected to the phone in ADB mode.
Google it. You will find the xda link.
Delano.888 said:
That STILL gives you the warning once after every reboot.
...
Click to expand...
Click to collapse
That issue has been fixed in subsequent FW updates.
Is this a package that can be disable from adb?
Everytime that I take a screenshot through the power menu or holding power + volume down, I get this weird toast that says "screenshot saved". This started recently and I'm not sure what caused it. Note that I am on Magisk stable with Xposed however I've tried disabling Xposed and running Core-only to no success.
Weird thing is it only applies to system UI screenshots, not assistant ones. This was confirmed when I download a toast origin app which showed the toast originating from System UI. Of course running in safe mode did nothing.
The only way I've found to temporarily stop the toast every time i screenshot is to reflash the patched boot image. However it comes back fairly quick and I've tried to find in the magisk logs if anything's changed.
here's a demo of it:
photos.app.goo.gl/R9VECpHgzpRyecag7
I know this seems really insignificant but if something isn't supposed to happen (which accd to the pixel group it isn't), then something's gotta be wrong.