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.
Related
This is an old problem, but the causes are so plenty it's a doozy. So here's yet ANOTHER cause of "can't click (Install)" button and its solution.
Any way, just updated to SlimKat. And no, I did NOT have official JB installed before, just official ICS, Safestrap, and had been running on CM10 ever since. But that's not the important issue.
Tried to reinstall some APKs, like Amazon store, some Xposed modules... Except none of them will let me click the INSTALL. And yes, 3rd party apps install is active, and I even turned off verify apps.
All of the previous advice I can find says look for screen filter or brightness apps or overlay buttons. I checked. Ain't got any that's active.
I was using PermissionDog to check anything that uses an overlay and uninstall them one by one, when something hit me (not literally). All of these are overlays of some sort. What overlay did I add recently? Then I looked at my screen, then slapped my forehead... hard.
I had enabled "battery bar" that comes with BatteryMix. This optional bar shows you a horizontal 2 px high bar on the very top that shows you your battery level. That is an overlay!
I turned that off, and voila, I can install APKs again. So let that be a lesson to you.
does anyone know how to turn off this annoying pop up whenever i double press home button to use camera?
and screen over ray disable when i install new apps.
yeah its really annoying!
No but if you do let me know.
Whats the point of quick launching the camera if you have to dismiss that before snapping a pix
I have no pop up message, when double clicking home button, goes straight to camera and it should be some setting you made, because I haven't played much with settings, so mostly factory settings and don't have it. I also haven't seen overlay disable message either and I installed plenty of programs. I got once warning, something wouldn't run (can't remember what) if I don't disable overlay, it's probably some Google protection, so I don't give unwanted permission to program hiding under screen overlay. Personally I think it's all nonsense, after a while people will click OK without even reading the message or not fully understand the message. Probably another setting in security somewhere. Sorry I can't pinpoint exact issue to fix it.
I used to get the Screen overlay warning whenever I was updating permissions AND I had a floating app like Hover Note or Hover Browser floating anywhere on the screen.
The only other time I got it if I didn't have those up was when I had Twilight installed to reduce blue light from my phone. I had to pause it in order to get that Screen relay alert to stop showing up then.
I never get that message and double press home to get the camera all the time
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.
[FOR REFERENCE ONLY]
Problem solved!
The confounding variable was NOT Xposed Framework, but conena's Gesture Control app that was set up to use Immersive Mode to hide the navigation bar. And according to this post that I landed on purely by chance, if you don't exempt the Lockscreen Settings app, it causes all these problems.
Note that this problem has nothing to do with the app, it's the Immersive Mode setting to blame, on which any setting change at all will cause these same problems (to be fair, conena's app does preemptively discourage this)
Solution
Use a Substratum overlay to hide the navbar instead; do NOT use GravityBox to do that by setting navbar height to 0, or qemu.hw.mainkeys=1 in build.prop (which doesn't work, BTW). Next, backup your gesture bar data and wipe the data of the app, then restore the bar data – just don't fiddle with that Immersive Mode setting again!
Well, some explanation is in order because it wouldn't make for a great thread title:
I am running the last stock Oreo build on this G8441, which is 47.1.A.12.20, for the primary reason of being able to use rovo89's Xposed Framework because the original XPrivacy module that's vitally important to me does not run on any of the EdXposeds or LSPoseds.
Using systemless Xposed with the latest Magisk version (and older ones too, nothing changes) I find that if I were to set a lockscreen to anything other than "None" and reboot, I will have times where I simply can't see the display when pressing the power button -- but weirdly enough the touchscreen still keeps taking touch input! The only way around is to remove the lockscreen, reboot, then set your locking method and try not to have it restart for any reason.
It's quite obvious that systemless Xposed is causing this problem (Xposed can't be installed normally on this firmware version) because this problem can be reproduced even without any modules active. But I'm at a complete loss as to what's actually causing this lockscreen interference, because I've tried taking system logs with and without Xposed and there's simply nothing at all different except it taking insanely long times for the display to activate upon unlock (but the touch input working just fine for some reason?) and there's a small, dim red LED near the proximity sensor that stays stuck as long as the display is.
Please help me, I'm absolutely out of ideas -- and no, I can't upgrade to Pie, I have to stay on Oreo for the sake of the XPrivacy module.
So it seems like 47.1.A.12.75 is the last problem-free Oreo version for normal Xposed Framework, and I wouldn't mind using that, if it weren't for the fact that there doesn't seem to be any VoLTE-activating SIN file for India for it below 47.1.A.12.270. There's a 2G phaseout in progress with the largest carrier and it's only a matter of time before there'll be no fallback network and I'll have to have VoLTE at any cost.
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.