yashsingh1/xdaforums huggingface dataset:
[SuperSU] audinswfc:
I'm on OmniRom 4.4.4. SuperSU is integrated in to the seeing menu like your ROM, no icon in the app drawer. Guess that's why then. Thanks ☺
[SuperSU] slavislavi:
After update to 2.35 ... my GPS is often looking for location. Can anybody confirm?

Location history is off in my settings, and also nothing else was changed - only supersu was updated.
[SuperSU] djbosanac:
Hello,

I have a ZTE nubia device CUCOU or something uses the SuperSU app, now since a few weeks

Google says i need to update the SuperSU app , and SuperSU Binary and the app it self must be updated to? Can i just update this?

Because its getting anoying to get everytime a message to update it.
[SuperSU] xda___:
lost...

- root with the newest update from the play store (the one with the new logo)...

what should i do?

download and install w/out playstore?
[SuperSU] sancho_panzer:
Maybe a coincidence, I can't see how these could be related. Everything running smooth here.

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M12 (KK 4.4.4)

Kernel:

Default CM11/M12 3.4.104

Recovery:

TWRP 2.7.1.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9 (KK 4.4.4)

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[SuperSU] wiljums:
Random reboots GS4 stock rom

Hi, after updating to 2.35 my phone is rebooting at random. It is a rooted galaxy S4 with stock rom and Google Now Launcher, xposed GEL and adblock. Before the update I didn't have any problems. Any advice how to solve this problem?
[SuperSU] quincho54:
No, gps running normal. I'm on a s4 19500 and uncharchted rom v9 lite.
[SuperSU] schaggo:
Xperia Z1 Compact, same issues. Since the 2.35 update system partition cannot be mounted r/w and write operations to /system fail.

I completely unrooted the device by wiping and reflashing the system partition. Obtained root by using towelroot, manually moved SuperSU apk to system partition. Yet after installation and updating the su binary to 2.35 respectively 2.36 r/w access to system partition is lost. Other root functionality is working just fine.

[MENTION=631273]Chainfire[/MENTION] which logs do you need and how may I obtain them?
[SuperSU] creesch:
In this thread you'll find the details which is where I eventually ended up posting them. Glad to know I am not the only one with this issue, let's hope it is a relatively easy fix :)
[SuperSU] Takamoto:
[quote name="Takamoto" post=57058060]what a pity, I was hoping for help..[/QUOTE]<br /><br /><br />

<br /><br /><br />

In your first Greenify screenshot, there is a reference to 'keyguard is unlocked' (keyguard = lockscreen, I think that part of greenify was badly translated in your language) ... probably it is inherent to the Pin protection offered as pro feature in SuperSU but I'm not entirely sure.<br /><br /><br />

<br /><br /><br />

Now I think we should ask to @<a href="http://xdaforums.com/member.php?u=631273" target="_blank">Chainfire</a> if this lockscreen permission may be stopped in free version without issues. :)<br/><br /><br />

<br /><br />

Can I solve the problem with the last supersu update? now i'm on supersu v 2.16<br/><br />

<br />

I've update the last version supersu..same situation.. :(<br/>

no one have a solution?
[SuperSU] Chainfire:
How exactly are you remount /system r/w, and how are you testing it
[SuperSU] EliXer9:
Thanks-a-lot [MENTION=631273]Chainfire[/MENTION] ! Can't imagine a day without SuperSU :)
[SuperSU] shinra00:
I had this issue but after a day with 5 or 6 reboots it got stable
[SuperSU] Steven Seagal:
I'm having problems with the new update free google SuperSU play. Do not updated binaries, the update and I returned to skip the message to update after restarting ...

What I have to delete file here? :confused:

/system/bin

or

/system/bin/.ext

or

/system/xbin

Please , help me ....
[SuperSU] Atmazzz:
Same on my Lollipop Nexus 10 with SU 2.35 and now 2.36. Still rooted and everything seems to work, just update binary failure. I get an occasional reboot I wasn't getting before. Stock recovery rooted with CFAR.
[SuperSU] Seriously Ponies?:
Tried installing the 2.35 version on my Moto G 2014 (XT1063) running Lollipop, and it bootloops as well.

Used the TWRP 2.8.0.1.Titan-v2 recovery to install.
[SuperSU] bluefan:
The smartphone Xperia Z1 is a problem. Does not update binary.

In Recovery, as well.

ps. I write with a translator ;)

Xperia Z1 ,KitKat 4.4.4, C6903_14.4.A.0.157

Root
[SuperSU] theprodigy85:
Is there supposed to be a binary update with every update of SuperSU?

I ask because I updated from 2.35 to 2.36 from the playstore and never got the prompt to do so.
[SuperSU] claytonjn:
Not necessarily.
[SuperSU] albert_htc:
Flashed boot and system. Then 2.36 via twrp.

All seems well.

One thing I did notice was I had to reflash twrp.

Seems OK now.
[SuperSU] hwlester:
In the same boat and was wondering this myself. :) I still seem to have root, so not too concerned. :)
[SuperSU] Smerks:
First, Thanks to Chainfire for some amazing work on all his stuff, it allows a dummy like me to play with his phone easily.

I am using this on a Nexus 5 with only whatever changes CF Autoroot make to my phone, I wanted as close to stock as possible and that gave me my desire perfectly.

Since the Lollipop update I was unable to use root with the previous CF auto root but now have since been able to with the newest update.

Now anything that has asked for root it will not allow me to grant access. When I say will not allow I mean I touch the screen and it just does nothing but count down and try again and again in some cases (Better Battery Stats) or just fail root check and load app (Titanium Backup Pro). At first I was unable to even go in and manually give permission once it showed as denied.

Then I did a cleanup for re-install from Play store and re-installed SuperSU and still cannot grant permission from within apps but can now manually grant permission for apps to have root once they attempt and it fails since I cannot touch "GRANT" to grant permission in the window but can within the supersu app.

I hope I am clear on this as it seems to be a minor bug but Im not sure and if any more info is needed I will gladly provide it. For me its minor inconvenience so far but I dont know if it is affecting others or maybe just something of mine screwed up (dont think so).
[SuperSU] zombieryder:
Flashed 2.36 successfully , wipe then reboot still the same "no root"
[SuperSU] DingoDingo:
Are you using Lux or similar app for dimming and controlling brightness?

If yes, try without.
[SuperSU] 3DSammy:
Is there a chance that you have "Lux" installed? I'm asking that question as there is a bug related to Lux where if its enabled when the SuperSu pop-up to grant root permissions for an app is displayed, clicking on "grant" does nothing. To work around this issue all you need to do is disable "Lux", click "grant" which will work then enable "Lux" again. Once you do this the Lux bug is not an issue. I've experienced this problem on both my Nexus 5 and 10 but I was lucky and stumbled accross mention of the issue and the easy solution before upgrading to lollipop.
[SuperSU] pkelly517:
Or..

Disable Tapjacking in SuperSU.

Or..

Add SuperSU to the sleep list in Lux
[SuperSU] tntnt:
Is it safe to update SuperSU in a LG G Pad, 4.4.2 Stock, only root by Towelroot?
[SuperSU] claytonjn:
This is NOT a bug, it is a feature. An app that overlays the screen in the way Lux or similar apps do could simulate pressing the grant option on the SuperSU dialog box and therefore grant su privileges to any app without the users consent or even knowledge. Since Chainfire doesn't have the capability to investigate every such app, nor should he be responsible for deciding which apps are "okay", SuperSU simply will not allow button presses on the dialog if any overlay is active.

As mentioned, one can disable tapjacking protection in SuperSU settings, however that removes that layer of security and IMO people really shouldn't be suggesting that as a fix without explaining that the system security will be loosened by doing so.

When Chainfire added the tapjacking protection he also added an intent that fires when the SuperSU dialog opens. This means that any overlay app, such as Lux, can listen for this intent and disable it's overlay when it is fired, which would allow the buttons to be pressed while keeping tapjacking protection enabled. This is obviously the most secure option but it requires for the app generating the overlay, such as Lux, to be updated. I believe it was reported that this is already in the works for Lux.

Also, a third solution is for apps to have a whitelist themselves that can be used to disable them in certain situations, which is already the case with Lux. It has been reported that whitelisting SuperSU in Lux will disable the overlay when the SuperSU dialog is opened and therefore allow the buttons to be pressed.
[SuperSU] schaggo:
I did not try it via shell/command line. I first noticed it with AdAway failing to write the hosts file to /system, I then subsequently tried two file managers (FX, SolidExplorer) to move content to /system or create new files. Both refused to do so. I then had a look at SuperSU logs and found, for all 3 apps, that attempts to write to /system failed and/or that remounting /system r/w failed.

I am back on SuperSU 2.06 (the one which comes with the one-click-root solution of Androxyds FlashTool for Sony devices) and this works. While I was on 2.35/2.36 I pulled the logs as instructed in the [SUPPORT] thread, I will quote my fellow Sony owner which seems to have the same problems I do and post the respective log files. I will edit this post and link there once done.
[SuperSU] Smerks:
I tried putting supersu in the sleep list of lux and it didnt help so I uninstalled it and it works fine now. Thanks to all for the help.
[SuperSU] liqice:
Supersu pro no OTA survival option?

Nexus 6, LRX21O stock - Supersu 2.36 -I bought Supersu pro through the Amazon App Store but I don't have the option for OTA survival. Is this normal? I thought by purchasing the app I would get the OTA option but I didn't.
[SuperSU] SamuriHL:
Read the release notes. It was removed for 5.0 builds. It may or may not return in the future.
[SuperSU] JBWKZ2099:
What about swap memories?

Well, I updated superSU and I lost the swap, I fixed it... Now, I've downloaded the update zip (2.36) and I don't know if I can lose the swap again if I flash the update zip by CWM...
[SuperSU] IronTechmonkey:
I'm also curious about what this means (not just whether or not it is checked by default). Kind of assuming that a warning in Titanium that SuperSu's "mount namespace separation" setting might not work properly on some platforms is part of the preparation for Lollipop but would like some clarification about what this setting actually does in SuperSU. Thanks,

CM11, 11/25 nightly (KK 4.4.4), SuperSU 2.36, TBU 6.2.01
[SuperSU] EatBeans:
Nice

thank you for your work
[SuperSU] hwlester:
Oddly enough, after the update, StickMount is complaining that I should be using SuperSU v1.93 or above. LOL StickMount is still working, but I'm not sure why it's complaining.
[SuperSU] Farmer General:
Gravity Box Screen Brightness Module

I would like to let everyone know that the Gravity Box Module that controls screen brightness has also caused lock-ups, and reboots. On average I had about 4 seconds after tablet boot to do anything before it either locked up or rebooted.

I came here and saw the issue regarding "Lux" and another user saying that "Any" application that controlled screen brightness would cause this. After reading this I used my 4 seconds judiciously and turned off the brightness module in gravity box and everything is back to normal.

While the problem was happening after the update, I noticed that Super Su Listed no apps as having been granted Su status. You folks probably already know that, but I figured I'd report my experience.

I hope some sort of fix is figured out. The module on brightness greatly helped my battery stay alive longer before recharges.
[SuperSU] Strephon Alkhalikoi:
The "fix" is to have the Gravitybox author update the module so it doesn't interfere with SuperSU's dialog boxes when they appear. See post #7621 for more details.
[SuperSU] hwlester:
I think this might have been a fluke. I tried running Root Checker yesterday after updating it and it said the system was running slow, and I never got a SuperSU prompt. I launched SuperSU and it prompted me for root, but wouldn't let me press the grant button. I finally force closed SuperSU after the OS said it wasn't responding. Everything seemed to be fine after that. StickMount is no longer complaining and Root Checker gave me the all green. :)
[SuperSU] Farmer General:
Thanks for the reply, I will head over to the Gravity Box Application forum and see what's going on.
[SuperSU] claytonjn:
It's not necessarily the case that "Any" application that controls screen brightness will cause issues, only those which create an overlay on the screen to dim it will cause issues. I could be mistaken, but I'm pretty sure that chainfire's CF.lumen app uses a different method and therefore would not have the same issue. Also, it should be noted that the only issue is the inability to interact with the SuperSU popup dialog when there is an overlay active, an app like Lux should not be causing reboots, etc. and if it is then that's an entirely different issue.

By the way, su privileges aren't needed for Xposed modules. Typically if an Xposed module requests su it's so that it can kill and restart system apps so that a reboot isn't needed for changes to be seen. As a general rule of thumb, however, there's very little chance that an Xposed module issue would be related to SuperSU.
[SuperSU] Farmer General:
The problem in my instance was that none of the apps which required SU and which were previously granted that status were being allowed SU status. The overlay came up first which denied SU access to everything including Xposed framework. When Xposed could not get permission with all my other modules and apps which changed system behavior and UI behavior it caused lock-ups and reboots. So in a roundabout way SuperSU+Gravity Box Screen Brightness Module=non-responsive System UI and Reboots. The Brightness module in Gravity Box caused a denial of all SU permissioned apps by using an overlay.

Thanks for the help my friend! I gave you a Thanks.
[SuperSU] zelendel:
Ok guys take it elswhere. The dev already has stated he will not support xposed and to be honest I would get used to not having it.
[SuperSU] Farmer General:
Sorry my friend, I was not even aware of this fact. Thank-you for informing me and I will remember this.
[SuperSU] annoyingduck:
Just gonna bump this question....I don't quite understand it. Should this feature be enabled or disabled for using Titanium correctly? Plus the original question....
[SuperSU] kInOzAwA:
The feature needs to be disabled if you have the problem stated in the new TB. Some users reported that it causing error with not enough storage issues. From what I've been reading somewhere else, that feature added mount-master instead of just normal su for added security. - -mount-master is an argument to the SuperSu version of su, which, forces the child app to use the root mount namespace.

Whoever having issue when using lux brightness (or any app that using overlay) need to disable tapjacking protection. It works for me.
[SuperSU] quincho54:
Using latest version of super su and lux on 19500 and uncharted rom v9 lite, never had a problem with tapjacking.
[SuperSU] IronTechmonkey:
Thanks for the clarification. As that sounds like an error message delivered by Titanium about free space and I've not experienced it I wont disable the SuperSU namespace setting. Still curious about the circumstances in which this is necessary - in order to avoid those circumstances or at least see them coming.
[SuperSU] Chainfire:
mount namespace separation separates the mount namespaces :)

Mounting, remounting, unmounting, these are things often done by root apps. This option makes sure they don't accidentally interfere with eachother. For the rare case where an app needs to manipulate the global mount namespace - for example mounting network or USB-connected storages so that other apps can use them - there is the --mount-master option.

This usually works. However, some OEMs have gone back to the Android 2.x world and are using non-standard /data vs 'internal storage' configurations. SuperSU only handles the standard AOSP-supported mount configuration. In some cases this may lead to - for example - /sdcard not being visible from root apps.

I suspect that's the case TiBu has run into, though without a comment from them, I'm just guessing. This option is generally not something you need to touch, unless you're running into rather obvious issues.
[SuperSU] IronTechmonkey:
Thanks! For what it's worth I've backed up and restored plenty with the namespace setting enabled in SuperSU enabled and had no problems in TBU. CM11 MSM8960 jbbl recently nighlty, ART, AHD.
[SuperSU] ironia.:
PIN protection is for grant supersu permission or for open the supersu app??

tnx
[SuperSU] egingell:
Yes.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Seriously Ponies?:
Update:

Tried 2.36 and formatted cache. This time it rooted!
[SuperSU] Elluel:
This is not a bug, and its been mentioned on literally every single page.

Tapjacking Protection. Either disable it or disable whatever overlay you're using.
[SuperSU] Seriously Ponies?:
thanks -- saw that, edited post.
[SuperSU] gumbyx84:
Read through the recent pages in this threads and keep seeing conflicting reports. Has the boot loop issue been resolved and the most recent release is now stable?
[SuperSU] fer456:
Thanks for updating the app, Chainfire. I have ready the log of the supersu, but I discover the new update on Play Store (before publish my first reply here, about the problem of had, I updated 2 or 3 times, I don't remember now). But for the last update (released today) I can update perfectly my binaries.

Thanks and keep good work!

One question: Why I haven't material design on my phone? [MENTION=631273]Chainfire[/MENTION]
[SuperSU] gyongyosimate1:
SU Binary update

Hi!

I can't update the SU binary on my Alcatel OneTouch Idol 2S phone (also aka: TCL 6050Y).

What can I do?
[SuperSU] greyhd:
[MENTION=631273]Chainfire[/MENTION], After the last update Secure Settings is unable to get access even after I grant access. The message "Unable to Grant Access" comes up. Thank you for the continued updates. If you need logs, please let me know.
[SuperSU] IronTechmonkey:
For what it is worth: Secure settings 1.3.5 (updated 11/27/14) behaving nicely with SuperSU 2.3.7 (updated today 12/1/14) here in a fresh install of CM11 MSM8960 jbbl nightly/PA gapps nano on a Moto AHD/MB886. Secure Settings permissions correct in SuperSU and various homemade widgets/shorcuts depending on Secure Settings w/SU permissions working fine. ROM/gaps flash, app installation and configuration done yesterday. Update to SuperSU today via Play Store.
[SuperSU] JulianJenner:
Thank you [MENTION=631273]Chainfire[/MENTION]?! 2.37 works correctly with my LGE-P760, Android 5.0 (by Artas182x)

Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
[SuperSU] Srandista:
Do you have a Lollipop on your phone?
[SuperSU] fer456:
No, I don't have it. But it will be good if you can select that theme in the settings. I think it would be great. Why to restrict to the older Android version user's to have a good theme? [MENTION=631273]Chainfire[/MENTION]
[SuperSU] egingell:
Material Design is introduced in Lollipop.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] fer456:
Yes, i know. But a lot of google apps has this new design and them are beautiful and really stable. Why not to do the same with SuperSu?
[SuperSU] greyhd:
I have all the latest updates and even did a fresh install of secure settings, but still getting the "Unable to grant access". I will try another time and see what happens.
[SuperSU] egingell:
I think you're misunderstanding. The API for Material Design is only available in Lollipop. All it is is a method for building a UI. The actual appearance of said API is immaterial.

https://developer.android.com/training/material/index.html

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] fer456:
A lot of other Apps has MaterialDesign in oler versions and don't depend on the Lollipop API. GAPPS is the most famous example. There need to be a method to port that API (if it is really needed) to older versions. A lot of apps have jelly bean (Holo) design in Gingerbread. And also, if there is some apps with "themes" like CleanMaster (I don't see any Holo on that app, and the same design is used on all versions of Android), it is possible to make a port of that theme and make it like a custom theme. Or just would be easy for [MENTION=631273]Chainfire[/MENTION] to see how works apps with MaterialDesign on older versions.
[SuperSU] egingell:
Whether it's possible it not, this app is more about functionality than appearance. I wouldn't be surprised if he's only using it in anticipation of when/if Holo gets deprecated.

Of course I can only speak for myself. Switching UI design models is a pain in the ass which requires rewriting most of the UI elements and there's only one reason I would do it - deprication.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Pkt_Lnt:
Or

We could let him solve the real issues of installation, upgrading, and binary updates that are causing so many issues with the changes in Lollipop.
[SuperSU] fer456:
Yes, but I'm talking when that of all will be finished. I also suggest that because sometimes the app take a lot of time to receive a update and include some little details like that would be great and can make that app different from other superusers apps.
[SuperSU] Chainfire:
This has been explained at length in the last batch of release notes.
[SuperSU] Wakamatsu:
Holo is a theme. Material Design touches on app performance and user interaction as well as theming.
[SuperSU] zelendel:
Let's drop this. It has nothing to do with the functionality of the app. The material idea will be changed in 6.0 again.
[SuperSU] Takamoto:
[quote name="Takamoto" post=57058060]what a pity, I was hoping for help..[/QUOTE]<br /><br /><br /><br />

<br /><br /><br /><br />

In your first Greenify screenshot, there is a reference to 'keyguard is unlocked' (keyguard = lockscreen, I think that part of greenify was badly translated in your language) ... probably it is inherent to the Pin protection offered as pro feature in SuperSU but I'm not entirely sure.<br /><br /><br /><br />

<br /><br /><br /><br />

Now I think we should ask to @<a href="http://xdaforums.com/member.php?u=631273" target="_blank">Chainfire</a> if this lockscreen permission may be stopped in free version without issues. :)<br/><br /><br /><br />

<br /><br /><br />

Can I solve the problem with the last supersu update? now i'm on supersu v 2.16<br/><br /><br />

<br /><br />

I've update the last version supersu..same situation.. :(<br/><br />

<br />

no one have a solution?<br/>

It was enough to simply convert supersu as system app.

Thanks all.
[SuperSU] esgie:
I'd like to report a tiny little bug which does not really affect the superuser experience but leaves a (little) mess on some configs (below description is for KitKat rom).

The cwm installer script in order to be sure that /system has enough free space needed to update SuperSU, temporarily moves /system/apps/GMS_Maps.apk (apk of Google Maps) to some temp location, then performs SuperSU install, then recovers the apk file of Google Maps to its original location mentioned below. The problem appears when the Google Maps apk file is named differently, ie. /system/apps/Maps.apk (like on my device) - if so, after every SuperSU installation through cwm, file /system/apps/GMS_Maps.apk is being created with 0 bytes in size. It does not really affect Android performance in any way (it still uses untouched Maps.apk as the apk file for Google Maps and "ignores" the empty apk), but guess you may want to fix it somehow, as it leaves unneeded file in /system/app.

Best regards.