yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
Indeed, I'm talking about that same recovery script. I'm not even completely sure how it messes up, but it borks some permissions somewhere that breaks SuperSU.

And indeed, everybody tells everyone for mostly mythological reasons to run this magical script, while in all my ROM flashing days, I have never needed it. The only reason you would theoretically need it is if you flashed a ROM with serious issues ... And even then, messing with permissions is not something you should ever do unless you know full well you know what you're doing.

If you're familiar with it, it's like the "repartition" flag in Samsung's ODIN tool. Everybody and their grandma tells everyone you need to use it, but it's actually a brick risk, and across dozens of Samsung devices with a combined total of several thousand flashes, I've actually had to use it exactly twice.
[SuperSU] bsoplinger:
Ok, so given that fix permissions does irreparable harm, what is the fix? Will uninstalling SuperSU then flashing the zip from the OP fix it?

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] polobunny:
Wipe.
[SuperSU] My1xT:
can you maybe make a "fix sSU Permissions" script which does them right???
[SuperSU] Magissia:
Hello, with the latest version i still have trouble to give temp su permissio to an app on my TF101 running CyanogenMod

i checked the box, picked 30 mins, clicked the confirm button, wrote the password, clicked okay.

Instaed, i get this screen again at next app's root action, asking for permission, again.

Cyanogen is set to give root to both apps and adb, SuperSU is set to don't care about Cyanogen's setting about this.

Regards
[SuperSU] YMatrix:
Hey ChainFire!

1) I am using the free version.

2) yes, it happens to every new app that requests root access.

3) No, I have never asked a app to re-ask again. If I grant root access, its permanent tool l till I change my mind :P

Attached to this message, is a zip file with the 2 files you requested.
[SuperSU] simono_pl:
Can anyone help me to run application that check if device is rooted (this application don't need root access https://play.google.com/store/apps/details?id=pl.pkobp.iko&feature=search_result#?t=W251bGwsMSwxLDEsInBsLnBrb2JwLmlrbyJd)? I try to "Temporary unroot" option but without success. I use SuperSU Pro version.
[SuperSU] My1xT:
if it asks deny and let sSU remember that choice, maybe it helps.
[SuperSU] yasars:
hi how can i remove supersu completly from my htc one m7??

i have only a cwm backup and in this is supersu app ..

need help
[SuperSU] simono_pl:
This application only check if root exist, don't ask for it.

Wysłane z mojego GT-I9300
[SuperSU] My1xT:
ok some apps ask and if granted, stop working...
[SuperSU] ddloco:
By way of vote how many of you like me are using floating notifications I have successfully found out that after enabling accessibility in floating notification instantly breaks the supersu 15 min check box chime in whoever has this install we may be on to something

PS I didn't just wake up this morning and assume its that program I actually been trouble shooting this for two days and I'm convinced its that app that does it thanks

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[SuperSU] My1xT:
does this also apply to other accessibility apps like LightFlow and such?
[SuperSU] bsoplinger:
I complained about the checkmark issue and I also have a few other accessibility apps. I seem to remember seeing an issue with Google Now breaking when any additional accessibility apps were enabled although there was a workaround fix. Perhaps there's a general issue with the Android accessibility setup and SuperSU gets caught up in it regardless of which app it is?

Edit: To clarify, I do not have Floating Notifications installed, just other apps that use accessibility and I have the check box problem. They are full!screen+ and AddonsDetector.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] ddloco:
Have not investigated others will nandroid and them report back my finding

Edit light flow brings back issue when I turned it on in accesabilty

Okay disableing accessibility fixes it so my conclusion is accessibility is causing issues

PS I didn't have to restore android just UN enable any access ability apps and then check mark is gone

Can a few other folks try some of these things we are onto the problem thanks

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[SuperSU] Chainfire:
Great find! Installed and enabled Floating Notifications and indeed the checkbox is checked ... will see what this is about.

EDIT: My my what a terrible framework bug :X
[SuperSU] sirxdroid:
Ah, this may explain why I'm having the same problem with the checkbox. I use Dashclock with the Google Voice extension which requires accessibility enabled.
[SuperSU] polobunny:
There's numerous bugs related to accessibility services, even more so on Samsung devices with stock roms. Guess SuperSU isn't in a better position. :p
[SuperSU] My1xT:
best Accessibility bug on Samsung is AutoTalkback...

but a different launcher and you have peace again.
[SuperSU] polobunny:
Surprises everyone when their phone starts talking to them lol!
[SuperSU] My1xT:
oh yeah, I also was surprides. also on The Note Series (and probably S4 too) AirView woll be disabled, but luckily you can turn it back on...
[SuperSU] Chainfire:
Please test if the attached version fixes the problem with accessibility services enabled ... it does for me :)

This is a freaky bug in the Spinner's though ... can't say I'm surprised, the Spinner's have a couple of other strange issues ...

EDIT: Download removed, see first post for the right link, or wait for Play to update :)
[SuperSU] bsoplinger:
Did a quick test. Just installed on top of the existing version, didn't reboot, had SuperSU forget 2 apps then launched each. Both dialogs did not have the checkmark enabled. So at least it looks like its all good now.

Out of curiosity, what exactly is messed up with the Android accessibility setup? No details needed but something more than just "its broken."

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] ddloco:
Yeah chain fire the 1.33 fixes issues

PS can a brother get some love on the research I did you know it kinda feels good to know that my troubleshooting at least got us a hint in the right direction lol

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[SuperSU] Chainfire:
I'll post the details on my blog later ... including the fixed code. It is beyond hideous, though.

Seems this has also solved some weird reports of the "select a time" popup when opening app details on an app that has Grant+Time set.
[SuperSU] bsoplinger:
Wonder if it'll fix the popup issue also. I've reported that although I have the popup/notification disabled it will show for any app that I granted su permissions since I last rebooted. That is apps with "old" versions which have already been granted permissions run quietly but ones with new versions which required me to approve permissions again (with the blasted check mark on that I had to turn off) show them until I reboot and they become "old" versions that don't require approval.

Regardless thanks for following up on the accessibility issue and kudos for coming up with and releasing a fix so quickly.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] Chainfire:
I doubt those things are related. That is a really strange issue, no idea what might be causing it - again, unless I can reproduce this, there is really not much I can do about it.

Which exact device, firmware, kernels, etc are you using though ?
[SuperSU] bsoplinger:
I get the exact same behavior across my 3 "standard use" Android devices, HTC Evo V 4G (Virgin Mobile branded HTC Evo View 3D), Nexus 7 and Asus Transformer TF101. All have at least one accessibility service app installed and suffer from the checkmark issue which is why I think the odd notification issue is related to accessibility also. After all that's 2 manufacturers, 3 versions of Android and 3 sets of manufacturers "improvements" (although you can say that the Nexus device is without but that's still different from the others) and all do the same weird thing.

I understand about not being able to fix it if you can't reproduce it. And its more of an annoyance really. Its just so weird its bugs me at an intellectual level.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] Chainfire:
Well, you're the only one who can confirm or not whether the update fixes this problem or not at the moment, so please test and let me know :)
[SuperSU] Chainfire:
Sorry if you just updated folks, left some debugging code enabled in v1.33, v1.34 now attached to first post.
[SuperSU] Chainfire:
If anyone is interested in the cause of the accessibility bug or the fix, you can find the details (and code) here: https://plus.google.com/113517319477420052449/posts/fYzS1rVtf9G
[SuperSU] Narenji89:
[MENTION=631273]Chainfire[/MENTION]

I protect supersu via pincode in order to prevent bad written apps and junkwares abusing root rights, so I trust my granted root apps, Hence I've disabled logging. But after that logs tab still exists in supersu and yes it's empty! Which isn't pleasant. So I'd like to suggest you enhancing UI in this term in future updates:)
[SuperSU] :
What's the problem? There is no log just don't click the logs tab... Why is it such a problem
[SuperSU] bedtime_with_the_bear:
Exactly. Disabling logging is one thing. Removing the ability to display logs is something else entirely. The two are not the same and one does not imply or require the other.
[SuperSU] My1xT:
what is so bad about a log tab when log is disabled, why even care?

But in one point he is right. especially on Tablets in horizontal mode it is easier to go to settings when swiping rather then clickting that tab on top...

and that you must scroll through an empty log, which CAN be annoying...
[SuperSU] poyensa:
Please back on-topic. Chill out and please remember XDA forum rules:
[SuperSU] truden:
I got this with today's update, but... I think it's caused by a streaming app which I installed in the same time with the update.

The app is BGCN TV

I froze the app and the requests for a root access stopped.
[SuperSU] Little Bigboy:
anyone know if this app hides root from some apps ? like time warner cable wont let you use its app if it detects your phone is rooted, so annoying
[SuperSU] blaz1nr:
This came when JB update came out mate. Its not anything malicious. It's I.p. tunnel calling root if I remember right. Just turn of it's note.
[SuperSU] bsoplinger:
You can temporary unroot by simply unchecking the "Enable SuperUser" check box. I had to ask too as it wasn't intuitive that doing so would do the job.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] truden:
Thanks [MENTION=4632471]blaz1nr[/MENTION].

I didn't think that its malicious root request.

I just thought that it would be helpful to share my experience and thoughts about it.

However, I don't think that it came with the JB update.

Few days ago I flashed XXUBMF3 and it didn't bothered me, until I installed that TV streaming app.

Any way, I've uninstalled it and now everything is OK.
[SuperSU] lazer9:
I made a prior version 1.32 a system app in attempt to replace "superuser" on current ROM. Now when I try to proceed with updating to 1.34, it says "App cannot be updated". :silly:
[SuperSU] 78Staff:
If you flash the zip file in the OP it will install as system app. I flash it every time I update rom since it too uses Open Source SuperUser.
[SuperSU] huskysdg:
Hi Chainfire.

I've troubles (that I never had) updating SuperSU binaries in Xoom MZ601 with AOSP rom TeamEOS (I'm in 168 and i'm using since 20) for everest device. The device is not updating binaries nor in normal mode or cwm mode options (even autorebooting).

May I update binaries from my CWM recovery directly? Where can I find the file (binaries only)?

Thanks.

Edit: I've tried to update from cwm and it's failing. I've installed new 170 rom with su 1.34 implemented and now for a while i won't have updating troubles...
[SuperSU] Magissia:
Hello, i reported some posts ago a problem concerning temp autorization not working, while allowing for 15 mins doesn't work (it will only allow next action it seems)

Denying do work and the app get root refused for 15 mins

Regards
[SuperSU] luubutmucxanh:
SOS.

Hello, SuperSU stopped working. can someone help? even with the SupSU 1.34, now I believed I must pay for the Pro version for it to work. Can I remove TWRP to use Clockwork instead?
[SuperSU] Pons:
Pro is not necessary for the app to work. It does give you added benefits and is a worthy investment in my opinion, but not mandatory.

What exactly is not working? Have you checked the logs to see if it's being granted access or not? Also check the app section to see if your apps are listed there.

And yes you can use CWM instead of TWRP. See your device's forum for that.
[SuperSU] :
Biggest added benefit of the pro version is supporting [MENTION=631273]Chainfire[/MENTION] ! That's why I bought it. Haven't used any of the added features ever.
[SuperSU] Braxos:
What about the white preview when you have set the dark wallpaper? Was there a fix I didn't read?
[SuperSU] Magissia:
I don't think it is fixable

Regards
[SuperSU] Braxos:
The only think that isn't fixable is history.
[SuperSU] Pons:
Or not:
[SuperSU] nigeta_gr:
Update issue

I updated to SuperSU v. 1.34 via Google Play but after first reboot it turns back to v.1.25.

How can I solve this issue?
[SuperSU] acestars:
I have 2 problems with SuperSU 1.34

1. I already disable notification but still show notification.

2. sometime when application need superuser access SuperSU dialog is not show when i using logcat this occuring a lot

Calling main entry com.android.commands.am.Am

and when i run ps command, i found a lot of app_process and su and make my device hang.
[SuperSU] rollidark:
SuperSu have build.prop lines?

exemple for force a theme?

ro.supersu.theme=2? thanks
[SuperSU] universocrema:
Thank you!

☜ Sent from my Xperia Pro MK16a BL ☞
[SuperSU] billa:
Suggestion for improving Full Content logging

Hi Chainfire, here are some suggestion to improve Full Content logging.

Upon playing around with various apps with Full Content logging enabled Per App it seems that SuperSU is not returning # in interactive logging mode which throws off a lot of apps continuing with the rest of their commands. Basically if an app initially checks for superuser privileges by looking for a # response and it doesn't receive one back then it just gives up or hangs.

Couple of suggestions to get around this issue:

1. With Full Content logging enabled Per App have SuperSU only do an Access Only logging on all first request per app but Full Content logging on subsequent requests in order to send the essential # so the app can continue.

2. Better yet send a real or fake # in Full Content logging mode too. ;)

Let me know what you think.

BillA

p.s. tested on latest v1.34 and should have mentioned that by apps I mean PC apps interacting with the device through ADB.
[SuperSU] bsoplinger:
The latest update of virus definitions for Avast anti-virus flags SuperSU as a virus. After sending a false positive report in I had to uninstall Avast to allow SuperSU to run. Just a warning for other users.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] calisro:
This isn't windows. You don't need anti-virus. js.
[SuperSU] doppelhelix:
Well, if you sprinkle snake-oil on your device, no wonder it starts hissing and rattling.
[SuperSU] shaggyskunk:
Try going to the market, select it & try to uninstall from there.

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] mdfaisal:
thanks man... really great job... :cool:
[SuperSU] Kurupt1:
bought pro version without ANY hesitation, I own pretty much all of your apps and love them. Thank you for your work.
[SuperSU] shaggyskunk:
Has anyone experienced a very brief freeze when scrolling through the market?

I'm not sure if it's related to chainfire SUPERSU, since I don't recall it happening before?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] ivan.volosyuk:
I'm the author of DiskUsage. I've got an alert of the diskusage referenced here. ;)

DiskUsage just runs "su", types 'scan' (included scanner binary), closes input stream and reads output from the binary, skipping first characters until '\0' byte, which indicates the end of potential garbage before 'scan' output.

http://code.google.com/p/diskusage/...ogle/android/diskusage/NativeScanner.java#149

If the output doesn't match the expected format, the error can be seen. I'm a bit suspicious about logging you mentioned. If it goes in the same stream, it can be a problem.
[SuperSU] vibranturk:
Hi...

Firstly thanks for great app...

Im thinking it using my rom also... But when Root Explorer + Supersu data folder shows emty:( With Root Explorer+ superuser( chainsdd) ı can see data folder...

Maybe this is related to root explorer app and it needs update for supersu? Other then this issue excellent work;)
[SuperSU] Chainfire:
Ah, didn't know this was open source. Well build it myself and check it out.

I've still not been able to actually replicate the problem with Root Explorer. It works 100% fine for me. Others have been able to solve their problems with Root Explorer and SuperSU (see a page or two back). It's still unclear what the cause of the problem is (and I can't figure out if I can't get the problem to show up).
[SuperSU] ChitownWingMan:
Should I uninstall/uncook SuperUser from my ROM

I have the normal Super User App cooked into my rom. Should I replace it with this one?

Thanks for the great work.
[SuperSU] signumized:
Unfortunately, after intensively testing different apps with root permissions, at some point, there were 3 (!) su processes occupying whole CPU.

Hope it can be fixed in the future, because I can possibly relate to some apps' preferences in SuperSU which are still not remembered (please see a previous attachment:

http://xdaforums.com/attachment.php?attachmentid=946519&d=1331719645 )

Thanks.
[SuperSU] shaggyskunk:
There's an app called system app remover, on Play Store... It looks like it might do what you're so kindly asking for.

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] sparksco:
WOW. Ok first off if you loose root and you can't download superuser from rom manager because rom manager requires root :rolleyes: Just download it from the website and flash in recovery. If you lost root and you can't flash it in recovery then your phone has a issue.
[SuperSU] bombadier:
This worked for me when I lost SU
[SuperSU] Chainfire:
Ok I had to clean a number of posts up, it was getting unfriendly.
[SuperSU] Chainfire:
If you want, yes :)

If you can make this happen again, please post the output of:

adb shell toolbox ps

Thanks. Obviously next update brings more fixes, but again, I can only fix problems I can make happen.
[SuperSU] signumized:
Ok, I was messing around with SD Speed Increase app ( which increases buffered read cache - wanted to test the SD card, to check if there are issues with it with your latest LPQ kernel , offtopic, is maybe the SD with WIFI restart problem solved with ICS / LPQ / your kernel fixes ? ).

I discovered that from the moment I start the app, su binary goes nuts.

Please see the screenshot and the ps output.

In this case, the SuperSU had Full Logging configured for all apps.

In case that I disable full logging and leave it to no logging, it seems that all goes well (hopefully).

Thank you.
[SuperSU] plasticarmyman:
i apologize....but i keep getting people telling me to do stuff i have already tried (and i already stated that i had already tried it), and acting like they are smarter because of such advice...it get's pretty annoying when people don't read simple questions.

i'm over it now...it was just really GD annoying and i had not had my coffee or cig's yet this morning
[SuperSU] sparksco:
So your all good now? Loosing SuperUser to have SuperSU in it's place is not a bad thing LOL.
[SuperSU] grontoft:
Dude, does this app remove root access (temporarily)?

My friend has got an app that accesses secure mailserver, and it will not work on rooted phones. Do you think SuperSU would work?

The app is this:

https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImRrLmV4Y2l0b3IuZG1lbWFpbCJd
[SuperSU] DaNiElCoRe:
amazing ¡¡¡¡

i use now and works like a charm
[SuperSU] Flappyraccoon:
It works great for me too, thank you very much Chainfire! I haven't been this excited since 4EXT Recovery Touch and V6 SuperCharger :).
[SuperSU] ticktock666:
I can confirm the false positive by avast, and while I like their product, I like my superSU more

I'll head over to their forums to start a thread there, if one isn't open already

edit: here's the thread on avast forums http://forum.avast.com/index.php?topic=128589.0
[SuperSU] billa:
Just put the file or folder as an exception in your A/V. Problem solved.
[SuperSU] reflexr:
Hm I don't find this option. Maybe it's not possible in avast mobile Security?

Gesendet von meinem GT-I9505 mit Tapatalk 4 Beta
[SuperSU] bsoplinger:
Avast mobile used to offer an ignore choice for problem apps it found but they removed that choice at some point in the past. Currently the only option is to uninstall and wait on a virus definitions or app update. Or live without SuperSU (which isn't an option in my book)

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] Brds7t7:
I've been using Avast and latest SuperSU without any issues at all. It hasn't flagged anything up on mine.

And to all those saying don't use an Anti Virus on your Android device, I'd disagree. Friend of mine got hit by some sort of malicious app few months ago that ran up a massive bill by sending out premium text messages. True most of us won't need it. I'm no security expert but malware DOES exist on Android. And if google policed the play store better then these apps like Avast wouldn't be needed. Avast is free and a pretty decent app from what I've seen, so why shouldn't people use it? If it gives the average user an extra piece of mind and catches one of the rare malicious apps out there then it's all good.

Anyway excuse the going off topic.

I take it you only got SuperSU off the play store or xda? Not from another source?

Sent from My Calculator!
[SuperSU] Chainfire:
Avast has a history of false positives with SuperSU and some other of my apps as well.

- There are quite a few known Android exploits

- There are quite a few packages that use these exploits maliciously (malware)

- There are also quite a few packages that use these exploits at the device owner's behest to root and automatically install SuperSU or Superuser

- As such, files like SuperSU's (or Superuser's) are "associated" with files used in malware (though actual malware would be unlikely to contain it)

- As a result, any app that contains those same files may be flagged as malware by association. This includes SuperSU, Mobile ODIN, etc.

This is how I believe SuperSU gets marked as malicious. Avast, Trend Micro, and several other scanners are guilty of such drivel.

As Avast even uses root (anti-theft), there really isn't any excuse for this behavior. Maybe next SuperSU update will contain a warning for anyone who has Avast installed that it's malware giving you a false sense of security that's best removed (here's a newsflash: it can't actually properly scan like a real virus scanner would without root), see how they like that.
[SuperSU] calisro:
android 4.2 protects against premium messaging malware. but yes that one is an issue in 4.1 or less. But if your going to side load an app, look at its permissions. it can't bypass permissioning in any ver of android.
[SuperSU] bsoplinger:
That's what burnt my toast about this issue, that they use root to do their anti-theft bit. How could they flag any superuser app in error amazes me.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2