yashsingh1/xdaforums huggingface dataset:
[SuperSU] mag01:
[MENTION=631273]Chainfire[/MENTION]

Is it possible to do something about the following?

I recently updated Greenify so that it would popup the SuperSU prompt on its next activity that requires root - and it happened later yesterday.

Once I let the screen go off with some apps running.

Greenify tried to hibernate some of those apps after few minutes, but that didn't succeed right away but triggered that SuperSU prompt (while the screen was still off of course).

And here comes the problem - the phone was kept awake in this state until I turned the screen on and granted the Greenify to perform its stuff as root.

But there was period of few hours during which the phone was kept awake and that drained the battery quite significantly.

When I look into the Setup / Battery I see SuperSU as the main offender with the time 2:22:23.

When I look into the BetterBatteryStats I see SUperSU (eu.chainfire.supersu) in the Process view only (e.g. not in wakelocks) with the User time 2:20:38 and System time 00:01:44.

Nexus 5, stock ROM, Linaro Kernel r50, SuperSU (Pro) 1.94, Greenify 2.3.1
[SuperSU] nick123ablxx32:
It happened when the phone just started after I installed the SuperSU 1.99 R2 and opened it when I pressed update binary via TWRP I got FCs then it rebooted to recovery....... Sorry this is all the help I can give....... Don't have access to a PC
[SuperSU] stef_ladefense:
Yes, with reboot, and no, the updading binary not work

for info, dont have custom recovery in my TabPro 10.1, and mobile odin does not work with it (have uploaded mobileodin.txt for ...) http://xdaforums.com/showpost.php?p=52728084&postcount=3992

just root by CF-AUTO-ROOT,

and have installed supersu apk from your last zip (1.99r2)

sorry for my English, my French is good :)
[SuperSU] bobbarker2:
Still bugged for me on an S4 running CM11. Tried flashing several times, still get "binary needs update" if I go into the supersu app.
[SuperSU] Blac Caesar:
Running smoothly over here.. Nexus 5, with latest Paranoid Android Beta 6 + Trinity b10

#KCCO.. PARANOID four.Four.Two Nexu5
[SuperSU] Chainfire:
Well until you do this will not be looked at. You're the only one reporting FC's so far as well.

It'd be interesting to know if you can get it to work with flashing through a custom recovery ...

Can you point me at the *exact* CM11 build you are running? I have tried several so far without issue.
[SuperSU] Elluel:
v1.99 flashed fine on latest Carbon ROM nightly for the Nexus 5, everything working.
[SuperSU] bobbarker2:
Sure it's the 5/21 nightly, you can download it here http://download.cyanogenmod.org/get/jenkins/69516/cm-11-20140521-NIGHTLY-jflte.zip

Also tried it on PA Legacy 4.3 Beta 6 found here http://goo.im/devs/aospa_legacy/jflte/pa_jflte-4.3-BETA6-20140523.zip and it's the same issue. In the app it says "su binary needs to be updated" and "Normal" method fails while "TWRP/CWM" method installs but when you boot up it still says "binary needs to be updated" I've also tried flashing the latest supersu.zip several times from download.chainfire.eu as well as installing the 1.99r2 apk.
[SuperSU] nick123ablxx32:
Reverted back to 1.94 still FCs it wasn't SuperSU..... Something else auto starting at boot.... Still can't figure it out....... Anyways binary couldn't update (1.99) I'll try a different ROM see if that works
[SuperSU] 78Staff:
No to OTA Survival, sorry. Seems some or most CM/AOSP/AOKP are working fine, while others all exhibit the same symptom of binary update failing. Wish I could say for sure whether the F2FS-enabled TWRP had any affect, but theoretically it shouldn't.

in 1.94, Enable SU during boot is set to denied, is that the default setting - I don't recall changing it so assume so. Would that make any difference in using recovery?
[SuperSU] Smoosh1:
Same problem here.

In SuperSU app I switched from Access:Grant+Time to Grant for Greenify. Did this one hour ago, and so far it seems to be a workaround solution. But I agree, it would be best if SuperSU could handle this on its own.
[SuperSU] nuck1982:
i flash with twrp 2.7.0.0 other recoverys not compatible with the new cm11 builds for my phone (Gt-I9001 Galaxy S Plus)

i try the new build maybee its fixed

thanks for reply

edit: thx with 1.99r2 it works good

Gesendet von meinem GT-I9001 mit Tapatalk
[SuperSU] rs tony:
I got ATM supersu v1,94 installed and it's system app. I got cm/aokp based rom and tried install v1,99 via twrp recorvery but it 'doesn't work.when i reboot my phone v1,94 is still there. This 1,99 update comes in google play too?
[SuperSU] Crescendo Xenomorph:
System language changed on its own since v1.99 again.. it happens on my Note8.0 running stock rooted 4.1.2....
[SuperSU] ceza1380:
1.99 works good with Carbon ROM.
[SuperSU] marbulas:
From 1.97 to 1.99r2 can't re-enable adter disable root via SuperSU on Galaxy Note 3 with Kitkat(SM-N900S) and SELinux Enforcing.

Is there an incompatibility about KNOX?
[SuperSU] bovirus:
[MENTION=631273]Chainfire[/MENTION]

I re-post the question (I didn't see the answer).

Which are the reason about version mis-aignment?

SuperSU v. 1.94 - on Goiogle Play

SuperSU v. 1.97 - XDA thread title

SuperSU v. 1.99 - SupeRSU update for recovery

Why don't align the version on Google Play/XDA thread/recovery update? It can create misunderstanding.
[SuperSU] jorceshaman:
1.94 was the last fully stable release. 1.97 came directly after that but there were issues from many users, 1.99r2 is the latest test version to try and fix the errors with 1.97.
[SuperSU] kingvortex:
Chainfire answered you already.....

http://xdaforums.com/showpost.php?p=52864003&postcount=5409
[SuperSU] bovirus:
OK. Thanks for teh info.

But this various versions can create misunderstanding.

If I vist this thread (Tile = SuperSU v. 1.97) and I checked on first post

Google Play link I downloaded APK v. 1.94

Recovery update I found version 1.99 (not R2)

The thread Title say 1.97 but version 1.97 is not availabel for downlaod.

I believe that to avoid misunderstanding should be a stable version. Ex. in first post

Title = latest (beta version available)

Link vs. Google Play that point to latest stable version (ex. 1.94) with reference that it's the latest stable version

Link or file that point to the latest beta version (APK)

Link or file that point to the latest beta version (recovery zip)

Note: beta version (APK & recovery) should be same version.

Of course all theese infos should update toghether
[SuperSU] maxsalsa:
Inviato dal mio SM-N9005 utilizzando Tapatalk
[SuperSU] Chainfire:
Seriously, stop whining. You have been answered repeatedly. We're trying to get work done here. Whether you agree with how that work is done is completely irrelevant - stop wasting everybodies time. I'll repeat it again because apparently you aren't listening: usually this all matches up. Right now because of some problems it doesn't for a few days. I know, the end of the world is nigh! I have zero patience for this type of commentary, so stop delivering it, or be removed from this thread.
[SuperSU] Frank Westlake:
Have patience -- chainfire is solving a significant future problem and also has many other programs to maintain.

Frank
[SuperSU] himanshu.khanna:
its working fine by now, thanks mate... will let you know if any issue occurs
[SuperSU] anagramgenius:
how to add supersu to custom rom? i mean what files in the UPDATE-SuperSU-v***.zip should be added to the custom rom?

just the superuser.apk in /system/app/Superuser.apk and su in /system/xbin/su?
[SuperSU] Chinaboy5216:
I just flashed it (zip file ) with TWRP on Tim's katkiss 4.4.2v24 without any problems
[SuperSU] Pons:
Nope. You need more than that. Read the update script/Binary, and do what it does.
[SuperSU] NZgeek:
What exactly is the problem here? You're set things up in such a way that you're pretty much guaranteed to have problems.

Greenify needs root in order to suspend applications. You've changed things such that you need to reconfirm root access for Greenify. This means that the next time Greenify goes to suspend an app, it's going to cause SuperSU to prompt for access. This will time out, the app won't be suspended, and Greenify will try again. And again, and again, and again.

I'm pretty sure that Chainfire has said in the past that simply displaying the access pop-up will wake up the phone. This isn't something that SuperSU does explicitly, it's something built into Android. In other words, any time the prompt is displayed the phone is going to be kept awake. This is obviously a problem when something keeps causing the prompt to show.

The only thing that I can think of that might possibly help is an option not to show the prompt if the screen is off. Instead, SuperSU would simply act like the prompt had timed out, temporarily denying access.

Of course, this might make no difference whatsoever. Depending on how aggressively Greenify wants root, it could end up chewing through battery, constantly failing to get root. But I guess at least the blame would be with the right app.
[SuperSU] egingell:
It's been my experience that once the timeout expires, you have to remove the "deny" from SuperSU before it will ask again.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] toyr99:
So what's the latest version to flash in recovery?

Inviato dal mio Nexus 4 usando XDA App
[SuperSU] wonsky21:
As far as I see it it 1.99

GT-I9505 | SlimKat 4.4.2 UNOFFICIAL build 5.x by kantjer
[SuperSU] kingvortex:
You could have just visited the download page yourself, but currently 1.99. :)

Latest SuperSU zip.
[SuperSU] cbeckstein:
1.99r2 solved all Problems for Stock XXUBMGA (Touchwiz Android 4.2.2), especially the continuous “supersu binary update available“ one
[SuperSU] brunodu91:
Why v1.99 isn't the official release in this topic?

Envoyé de mon S4, via tapatalk 4 Vip .

Slimkat 4.4.2 v5.2 stable, Kernel stock , buzz launcher , modem ET bootloader NC4.
[SuperSU] kingvortex:
If you read back some pages you will see that 1.99 is the version currently being tested.
[SuperSU] boyheadkick:
Clean flashed my Note2 LTE with Odin last night with the latest stock Sammy official 4.4.2 update and rooted it with v1.99..no problem encountered at all..i just had an issue moving files from internal to external storage but i think it's a file manager app issue..

edit: also working well with my galaxy s3 i9300 running Archidroid 1.7.15 4.3 Touchwiz based

-aL

Tapatalked from my BoefflaDroid i9300
[SuperSU] muniz_ri:
Tried the "full unroot" settings option on my GS4 I337 running stock twz NC1 using v1.99r2 and phone crashed/rebooted and unroot failed. Tried it a second time and it worked fine. Just an fyi..
[SuperSU] pastordl:
Running 1.99v2 and it purrs like a happy kitten, on my Nook Color with latest CM11 nightlies.
[SuperSU] bobbarker2:
It didn't solve all problems for the bugged "su binary update". Several people and myself were posting about 1.99r2 still being bugged a few pages back. But of course CF is very busy preparing for future code changes.
[SuperSU] UltraPower31:
I've flashed I9505XXUGNE5 and the phone randomly reboots with any root app. Is there a way to fix it? Without root it doesn't.

Gesendet von meinem GT-I9505 mit Tapatalk
[SuperSU] K-alz:
[MENTION=631273]Chainfire[/MENTION] It makes me wonder (I'm trying so hard to believe it), why you haven't rooted the AT&T and Verizon locked devices yet (especially KK). There is a very huge bounty there that you should be able to get easily.

from the tip of my fangers...!
[SuperSU] E:V:A:
Wonder no more.

CF doesn't do it for the money or he'd be working somewhere else. He's doing it for the global developer community. So what make you think he should waste his time unlocking the heavily locked-down phones by ATT and Verizon, just to have it all undone in a few weeks?

What you should wonder about, is why people ignorantly insists in buying into these companies locked-down phones, and then whine about it, when they got their few dollars in savings by doing so?

Just stop buying their products.

End of whining, end of ATT/Verizon mafia.
[SuperSU] :
Sorry for a n00b question,

Do I need BusyBox along with SuperSU for root privileges???

Or is SuperSU alone sufficient???:confused:
[SuperSU] volkmadi:
Hi,

for root SuperSu is enough.

You need to be root to install BusyBox itself.

BusyBox is just a collection of useful UNIX utils.

Dirk
[SuperSU] :
Can you please tell which apps need BusyBox besides TB???

Can you elaborate what BusyBox is???

Will I be missing any features if I don't install BusyBox???

I don't plan to install TB btw...
[SuperSU] volkmadi:
Hi,

TB does not need it (just needs root for sure), it brings all it needs with it.

BusyBox is explained here:

http://busybox.net/products.html

Due to your question I would say you will not miss anything when you do not install BusyBox. ;)

Dirk
[SuperSU] K-alz:
That's very true man. This is my very last samsung device with AT&T. I've said that a while ago when I found out they're locking down our devices, but I'm just waiting to finish paying my device then I'm leaving them.

Ps: I disagree with you on "CF doesn't do it for the money". Why would he ask for donations if he didn't do it for the money? And that's not a bad thing, I mean, he deserves it for providing root for us. I don't think he was able to find out a way to root those devices like he did before they started locking them down, otherwise he would've done it with no hesitation.

Also, I don't think my post contained any "whining". Just wondering is all :)

from the tip of my fangers...!
[SuperSU] DSA:
If he did it for money he would charge you for any product he makes. There's no obligation with a donation and is down to the discretion of the donator.

I imagine Cf is the same as the rest of us...donations are greatly appreciated for the work that's put in but isn't a prerequisite for downloading his work
[SuperSU] K-alz:
Not gonna start a debate and clutter the thread over a question, but that is true, but still wants money in return if possible. Again, not a bad thing. I was just replying to the other guy who basically implied that there is no money involved in any of CF's work. There are some paid apps in the playstore of his work (I know he also provided them for free on his thread, but putting them on the playstore for a price means.....? And that's not bad). Just please don't tell me no one likes money for their very hard work. LOL

Didn't know it's going to turn out as "trolling", just asked the guy a question. I'm pretty sure he can speak for himself and he doesn't need lawyers for this big huge crazy deal I just made. Geez!

Good days homies [emoji111]

from the tip of my fangers...!
[SuperSU] coukou:
Hi,

I downloaded and installed SuperSU on Google Play. Except the fact that is v1.94 it works just fine. So, I decide to update to UPDATE-SuperSU-v1.99.zip. I got successful TWRP update.

However, When I start SuperSU (v1.99 update), I get "The SU binary need to be updated" message. By clicking on [Continue] I get the second message "If you have a custom reovery like TWRP or CWM...blablabla" (see bellow images). When I click on [TWRP/CWM], it restart TWRP install, get the same message again and again...

The only way to get SuperSU working is to install the SU binary in [Normal] mode. But again, each time I start SuperSU, I get the above messages and I select install the SU binary in [Normal] mode.

Is any chance to get ride from these messages? Maybe a last stable version v1.97 or v1.99 through Play?

Regards
[SuperSU] stef_ladefense:
Sorry, but don't have custom recovery for T520, only Stock, and mobile odin not work for T520 :(
[SuperSU] Jayman007:
I have the same issue. I updated my 1.97 to the 1.99 that is on CF site (recovery version) and after I installed I still get the "Binary needs updating" message every time I start it. I have confirmed that I am indeed running 1.99. I don't see anywhere that mentions 1.99r2 even when I run su -v from a terminal I still see 1.99.

I should also add that even though I have the language setting in both android and SuperSU set to ENGLISH, every time my reboots it sets the language to Thai.
[SuperSU] volkmadi:
Hi,

I experienced the same. So that's a quite interessting point for me too!

I have a question, have you disabled the com.sec.knox.seandroid?!

Dirk
[SuperSU] UltraPower31:
Yes, SuperSU asked me to do so. Additionally I've frozen every Knox App with Titanium Backup.
[SuperSU] volkmadi:
I fear to follow the instructions is no longer correct for our new firmware with knox2. SuperSu is not the guilty one here on our S4 it works perfect in version 1.94 as well as with 1.99!

It is the disable of the seandroid!

I'm curious for the official solution!!

Dirk
[SuperSU] BurlaMatto:
Same here, with latest firmware (I9505XXUGNE5) i have got some random reboots after disabled knox. If i leave knox untouched everythings work fine, even rooted apps.

I think it's not a supersu issue, it's some knox apps that remain active. It would be nice if supersu disables all of them like it did with old knox :P (or just a list of app to be deleted/disabled).

Thanks!
[SuperSU] DESASTER75:
... so SuperSu 1.99 is not running well atm? I'm still on 1.94 and as I'm reading the previous posts, I'm thinking to avoid installing 1.99 or any chance to get those messages avoided but 1.99 working well?

Got the 'UPDATE-SuperSU-v1.99.zip' -> CWM-install-version! Will those messages do show, too?

Thx
[SuperSU] Sleepy!:
1.99 is working fine on my Sensation and N7 LTE.
[SuperSU] DESASTER75:
HI!

So how did you install 1.99? Through CWM? If yes, did you got the messages to update binaries, ...? If not, what have you done to avoid?
[SuperSU] Sleepy!:
TWRP 2.7 on both devices.
[SuperSU] :
This is hands down the best superuser app I have used...PERIOD!:good:

[MENTION=631273]Chainfire[/MENTION] You're the Lord of Root...PERIOD!:svetius:

Please don't interpret this as spam... Consider this as my ode to you...

---------- Post added at 03:11 PM ---------- Previous post was at 03:01 PM ----------

The only option for you guys is to flash SuperSU v1.94 through custom recovery....

And my 2 cents of advice would be to stick with SuperSU releases which are released through Play Store...;)

If you go through the changelogs v1.93 and v1.97 were built in anticipation of overcoming the root shortcomings of the next version of Android...

Hence they were not released through Play Store cause the releases before those were sufficient for us average Joes...:D
[SuperSU] volkmadi:
Hi,

I can not remember that SuperSu disabled any knox app in the past, was that really the case?!

I thought it is just the installer/updater for root app (where it has to be installed first with CF-Auto-Root;for example)?!

Answer highly welcome!!

Dirk
[SuperSU] evildog1:
Supersu update?

After i re-flash Supersu to v1.99. Supersu app ask me to update. how do i do?

my device is Galaxy S3 mini
[SuperSU] :
It is a known bug in v1.99, thats why the changelog in this thread hasn't been updated...

You better flash the SuperSU v1.97 zip file from recovery...
[SuperSU] Chainfire:
I flashed I9505XXUGNE5 (United Arab Emirates version) on my I9505 and installed the v1.99r2 zip - I cannot reproduce the language reset nor the reboots. I need more information to reproduce.

Please provide a link to the *exact* version you flashed, a list of root apps you think may be active when the reboots happen (who triggers the reboot ?)

The language reset is also very concerning, we've had this issue before (with slightly different details) but it was a real drag to find, even when I *can* reproduce it...
[SuperSU] gerardo87:
I had reboot when I was with 1.97 version. Then I flash the zip version of 1.99 and the random reboots seems to be finished. I'm not sure if this is can be helpful

Edit: I have had a random reboot just right now... When happened I was simply using Tapatalk

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] UltraPower31:
Hey, thanks for your answer.

I'm using the DBT version of I9505XXUGNE5 and the latest v1.99.

When the reboot happens I'm not using any root app but tapatalk or Gmail for example or many times the phone reboots when I just turn off the screen or when it's laying on the table.

When the phone is unrooted there are no reboots, they only appear with SuperSU or koush's Superuser. When Knox is disabled they happen more often than with an untouched Knox, so I can't recognize a trigger.

By the way the phone doesn't perform a complete reboot, only the bootanimation appears and I don't have to enter the SIM's PIN.
[SuperSU] volkmadi:
Hi,

with me it have been always soft-reboots too (no pin question).

It was too while the phone was not used at all or short after the screen was looked/turned off by it self (the screen).

I solved it with knox enable su 1.99 (but still in the revision 1;I'm not willing to flush all day a new version specially when it works for me)

and I set the knox state to "permissive" (there are apps for that in the store).

The only "bad" thing that remains is a status notification in the notification pulldown.

Since then no auto reboot at all!! ;)

Dirk
[SuperSU] Chainfire:
You guys running ART or Dalvik?

EDIT: Don't even see the option in dev settings... If you guys have the knowhow, it would be interesting to connect your computer's adb over Wi-Fi, and keep it running logcat, then when it eventually reboots, the reason will probably be in the logcat somewhere.
[SuperSU] gerardo87:
But if I want to come back to 1.94 version (to test if I have more rr) where can I found the flashable zip (through cmw) or the odin version (of that specifically version number)?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] Jayman007:
I was just wondering the exact same thing.
[SuperSU] volkmadi:
Hi,

DBT I9505XXUGNE5 so I suppose Dalvik, in Stock I never saw the ability to change to ART up to now.

I did logcat and dmesg and just have seen nothing strange some java errors from somewhere and a timing error which seem to come from a maybe not up to date sound app (equalyzer or so).

Dirk
[SuperSU] Mistertac:
If you Google SuperSu 1.94 it pops right up. One way at least
[SuperSU] Chainfire:
UPDATE-SuperSU-v1.94.zip
[SuperSU] gerardo87:
I'm on TW imperium v5.0 and I'm using dalvik.

Can I use a logcat made by kt kernel?

Can I flash that though I'm whit 1.99 version now, right? It just replace the binary

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] :
Yes, you need to flash it through recovery and it will just replace the binary...:good:
[SuperSU] gerardo87:
Thanks I've forget to delete my previous post because for extreme safety I did the complete unroot (on supersu app) and then I've flashed the 1.94 zip. For now seems all ok and the system more smooth. Finger crossed :fingers-crossed:
[SuperSU] darkrevlis:
Hello, I as well had problems with the firmware I9505XXUGNE5 but reboots solved by uninstalling knox apps from titanium backup.
[SuperSU] gerardo87:
I'm on old bootloader (MGA) and with rom knox free (imperium rom v5.0). Which specific app did you remove? Maybe remain someone

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] :
Oh, lets hope you don't face any more probs...:fingers-crossed:
[SuperSU] bobbarker2:
So the current workaround for the "binary needs to be updated" bug is to downgrade to 1.94, right?
[SuperSU] darkrevlis:
Through the app titanium backup, go to the uninstall option user applications and system.

uncheck all applications and search applications by alphabetical order starting with knox... , the ticked all and uninstall. Done
[SuperSU] gerardo87:
Wait, I didn't say that. I'm testing if this can be solution

just in that hours. I report tomorrow if it works for me [emoji6]

No one app with knox in the name is present so I think I'm ok [emoji16]

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] nuck1982:
its not a bug in v1.99. it works fine at cm11. maybee a big with your android system.

Gesendet von meinem GT-I9001 mit Tapatalk
[SuperSU] bobbarker2:
I'm running a clean flashed CM11 5/26 nightly on an S4 and I still have the bug with 1.99r2.