yashsingh1/xdaforums huggingface dataset:
[SuperSU] SecUpwN:
Then don't use it. Your tonality is rude, given that [MENTION=631273]Chainfire[/MENTION] develops it and offers to get rid of an error for which he asks us to help him. People like you seem to only complain, instead of helping. I demand you to show more respect to our developers!
[SuperSU] igoivo:
I am sorry for my anger, but:

1) It's not only me who complained about the empty entry error,

2) The problem is known for half a year already, but the fix is absent.

3) The SuperSU log is useless in the particular problem (since the entry is empty).

4) As a Pro user, I still hope to get the fix.
[SuperSU] kingvortex:
Then help Chainfire fix it, by providing what he asked for. Intermittent bugs are very hard to troubleshoot and fix, especially when they cannot be reliably reproduced.
[SuperSU] SecUpwN:
1) How about HELPING instead of filing ANOTHER complaint?

2) Meaning: Chainfire also has a live. get used to it.

3) How about submitting a ful Logcat then?

4) Yes, you may. But please don't demand with pressure. Thank you.
[SuperSU] jorceshaman:
Unfortunately I accidentally liked your comment but... He gave very specific instructions for you to help him get it fixed. He stated "I can't fix it until I can replicate it". How about following his instructions to get it fixed instead of just complaining?
[SuperSU] Chainfire:
Please don't fight about this. I'll fix the issue if I can replicate it - merely fixing the symptom will make finding the issue in the future even harder, that is why I refuse to do it.

There is no obligation on my end to spend ages finding the root of this issue, nor is their any obligation on his end to assist me. If we meet in the middle, then maybe we can move forward, if not, then it's certainly not worth arguing about it.
[SuperSU] Frank Westlake:
It is understandable that you do not wish to do all that time-consuming work, or perhaps you are not able to do it, but perhaps one of the other people who are having this problem can help. I am repeating ChainFire's instructions here so that it is more visible:

1. ...make a CWM/TWRP backup,

2. then clear out all personal data (accounts, app data, etc),

3. then make sure the issue keeps occurring (clear SuperSU's data first, then see if it happens again),

4. then make a second backup,

5. and send me that second clean backup

6. (after which you can restore your first backup, getting your phone fully operational again)...

It is either all of the above or someone can uninstall applications one at a time (reinstall each as the next is uninstalled) until the problem goes away, then tell ChainFire which application caused the problem to stop when it was uninstalled. This might not be as difficult. First make a list of all applications which use root. Look in the SuperSU list of root applications and see which is not there and try it first.

Frank
[SuperSU] jkeuclid:
Hi, I have SuperSU Pro installed and working just fine, but then I went in and simply changed the launcher icon to different one and now it disappeared from my screen. I still can open it from the Google Play store but I cannot find it either in my apps or anywhere on my screen.

Edit: found it
[SuperSU] shekinahsmoke:
is it natural to not have to update the binary after downloading this latest one?
[SuperSU] sirxdroid:
Not all app updates involve a su binary update.
[SuperSU] Moscha:
Hmm there seems to be a bug (or a problem only on My device?) with the latest SuperSU Version. I enabled PIN Access (used my SIM pin, so I won't forget it). I am able to give Apps root access if the SuperSU Popup shows and wants me to enter the pin to authenticate.

But if I start SuperSU gui: wrong pin entered - error is always displayed.

Has anyone an idea how to solve that?

Nexus 5, stock 4.4.2, SuperSU 1.94

Gesendet von meinem Androiden mit Tapatalk
[SuperSU] casonswag:
No prob here N4 supersu 1.94 miui
[SuperSU] defim:
I can also not open the app anymore :(
[SuperSU] Pkt_Lnt:
Some users have reported this with some Xposed modules. I see in [MENTION=4501300]defim[/MENTION] sig an Xposed link. Try disable all modules and see it it happens.
[SuperSU] Moscha:
Thanks for the Suggestion!

On my device it was the Xposed module "ActivityForceNewTask" causing the problem with the SuperSU PIN.

Disabling/Uninstalling the module and a reboot solved the problem. Now it's all working fine!

Gesendet von meinem Androiden mit Tapatalk
[SuperSU] defim:
For me too. With ActivityForceNewTask version >=1.7 a whitelist entry is needed, or downgrade to 1.6.1
[SuperSU] claytonjn:
Or you could both use ActivityForceNewTask in whitelist mode as GermainZ suggests every day.
[SuperSU] defim:
What's the difference between "whitleiste mode" and a "whitelist entry". If even possible a programm should run wihthout static lists, imho
[SuperSU] Moscha:
That's correct! I was not looking inside every Xposed Thread on xda I'm using ;)

Gesendet von meinem Androiden mit Tapatalk
[SuperSU] Chainfire:
Why are people running something like that in the first place? What specific problem does it solve?

Messing with how activities and tasks work goes against how apps are designed, and mess up expected execution paths inside the app. It's asking for trouble.
[SuperSU] Chainfire:
Thanks for the explanation.

Just to make something clear - I was mostly just curious. While it can indeed be frustrating people reporting issues with my apps caused by other hacks, in this case it was solved by you guys before I even saw the issue.

One lesson to take home, and especially when using Xposed (or Substrate) modules, is that in case of errors, first see if its Xposed and only then complain to your app author. In this case it was solved quickly, but otherwise I might have wasted a few hours on this, only to find it was user error. This already happens a lot, and while that's part of the game, if it can be prevented that's always better.

In no way am I faulting GermainZ for this. Though I admit, it seems more sensical to me to make such a module always run in whitelist mode, in no way do I expect him to make it so just because that is my opinion.

Heck, if I had to give you a dollar for everything in all of my apps out there that work a certain way but maybe would work better in a different way, I'd be pretty poor ... :)
[SuperSU] lulisat:
Please Chainfire is it possible to root Note 3 neo/lite. SM-N7505

regards
[SuperSU] claytonjn:
My concern wasn't so much the complaints on this thread, because myself, as well as other, read every post and can jump in and resolve these kind of issues without your intervention. My bigger concern is if people start contacting you through the Play Store, either as ratings or emails. Only you can handle those and your time would be better spent elsewhere. Plus, you may not care about Play Store ratings (there's not much competition after all) but other developers do. If a module like ActivityForceNewTask causes users to submit negative ratings for an app due to something out of its control that's not fair to that apps developer. This was the case with the "allow any widget on lockscreen" feature of GravityBox - it caused apps with specially designed lockscreen widgets to revert to regular homescreen widgets and caused lots of headaches for developers on the Play Store.
[SuperSU] Chainfire:
Root requests go here: http://xdaforums.com/showthread.php?t=1980683
[SuperSU] Super_Dork_42:
I'm on 4.1 and it happens to me as well. Didn't happen until the 4.1 update from 4.0.4, however.
[SuperSU] Brushstroke:
Is there any way to update the su binary without using the SuperSU app? I use your app on my Nexus 7 but on my phone I prefer to use the Superuser built into the Settings menu.
[SuperSU] Pons:
Not sure exactly what you're asking, so I'll answer a couple of what you might be asking.

Use Koush Superuser to manage SuperSU binary? No.

Update the Binary, but not have SuperSU update it in app? Flash the zip in the OP via recovery, but this will replace your current su management app with SuperSU.

Not sure which rom you're on, but I'm assuming CM with the built in Superuser in settings. Omni also has this feature with SuperSU.
[SuperSU] Frank Westlake:
- Verify that '/system/xbin/su' exists.

-- If exists, verify the permissions.

-- I not exists, verify that it is in the archive at 'system/xbin/su'.

--- If in archive, verify that the busybox links are in '/system/xbin'.

---- If links OK (su in archive but not on device), add 'system/xbin/su.txt' to the archive and install the archive again.

----- If '/system/xbin/su.txt' is there but 'su' is not, rename 'su' in the archive to 'sue' and rename 'su.txt' to 'su'. Install the archive again

and see if 'su' the text file is there. If not then the OS is deleting 'su' as it boots.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] iamsuperuser:
[MENTION=5545307]Frank Westlake[/MENTION]

Yes

How do I verify ?? The phone is not rooted so I cannot use any root explorer to verify permissions

Yes

Yes

No

The root files are flashed correctly and the OS is not deleting any files at boot.

I still get the same error message as in the attached thumbnail in the previous post.

I'm making this for my Galaxy Note 3 SM-N900 Exynos with Kitkat 4.4.2 Stock

How do I proceed now ?

Please help.
[SuperSU] Frank Westlake:
Verify the permissions. Maybe ADB will let you see that directory. If you have TWRP installed you can use its terminal.

I don't recall seeing 'chcon' in your script so maybe the security context is wrong.

Frank
[SuperSU] iamsuperuser:
You are right, there is no chcon in my updater script

What is 'chcon' ? How do I use it?

I've seen it in the update binary of supersu

I did not find any tutorial or relevant material on xda on using chcon, chown or any SELinux

Please help me out here
[SuperSU] Frank Westlake:
Find another forum for system security. Regarding 'chcon', just use the same settings you see in the update archive.

Frank
[SuperSU] tgp1994:
app_process spam

Hi everyone,

I've just down/upgraded my phone to Android 2.3.4, and after updating to supersu, my phone was becoming extremely slow while running a supersu-heavy task like restoring apps from titanium backup. After a few apps, my phone slows to a crawl. Running ps from a terminal, I see dozens of app_process processes running, all taking up memory.

I saw a post about a hundred pages ago with another user that had this same issue, but they were never responded to. Can anyone help me out with this?
[SuperSU] Frank Westlake:
> I've just down/upgraded my phone to Android 2.3.4,

I don't know what "down/up" means.

> and after updating to supersu, my phone was becoming extremely slow while running a supersu-heavy task like restoring apps from titanium backup. After a few apps, my phone slows to a crawl. Running ps from a terminal, I see dozens of app_process processes running, all taking up memory.

It seems to me that the application expects 'su' to return when the task completes, and that this is what used to happen, but now maybe 'su' is handing the task over to another background process and returning immediately, which causes the application to continue launching more pending tasks. Just a guess, I haven't used 'su_daemon' and I don't know what it does, but maybe it does that.

Frank
[SuperSU] tgp1994:
I sort of meant that I was downgrading in terms of Android version, but upgrading in terms of stability and performance. Just an aside to explain why I was on such an old version in the first place.

Right, maybe that's it. I ran Titanium Backup some more this time with adb hooked up and top running on my phone just to get an idea of what's going on. I could see the CPU usage jumping around (expected), but I didn't see tons of app_process processes launching up this time.

Thanks for your help!
[SuperSU] 78Staff:
Since the thread title and Play Store have 1.94 how, It's safe to assume 1.94 is no longer a specific fix for the N7100 NB4 4.4.2 leak?
[SuperSU] Pkt_Lnt:
You could check the changelog in post #3.
[SuperSU] 78Staff:
Oh I read it, it's just not clear (at least to me) if those are the same devices as CF previously referenced. Thanks for the help though.
[SuperSU] eurochild:
[MENTION=631273]Chainfire[/MENTION]

An important issue for me and lots of Paranoid Android rom users.

Latest rom version 4.2 beta3 switched back from superSU to superuser as a built in SU app. Installing the rom removes completely superSU, when installing superSU either from recovery or from playstore has the following results..

- superSU is accessible right after installation

After reboot..

- superSU handles just fine all su requests from root apps

- superSU isnt anywhere in the appdrawer to launch it

- playstore shows just the uninstall button

Any help ?
[SuperSU] Pons:
This definitely sounds like a bug in Paranoid Android, and in no way Chainfire's fault. I quickly glanced through the merged AOSPA/android_packages_apps_Settings. And while I do see where SuperSU was added, and then later replaced by Koush's Superuser, I don't see where they removed the elements from when they had originally added SuperSU. Again, this was a quick glance, so maybe I missed it.

Have you tried looking or asking in the XDA Paranoid Android section?
[SuperSU] eurochild:
I didnt say that its his fault, i'm just pointing the issue and asking for his help/opinion
[SuperSU] Chainfire:
Well, you could complain to PA and ask them to bring back SuperSU ?

Anyway, did SuperSU use to be accessable through Settings, just like Superuser? First, check if that is no longer the case. If that was the case (or if they've played with that before switching to Superuser), they most likely forgot to remove the "supersu_title" from some strings.xml file, which SuperSU uses to detect if it is to be launched from Settings, or keeps it's own icon around.
[SuperSU] kingvortex:
And this is how forum arguments start. :D Nobody said you were blaming Chainfire. :)

It appears (to my amateur eyes) that the commit to add Koush's superuser to settings in combination with the earlier commit that hides SuperSu from the app drawer when it's installed may have caused your problem and is therefore not something that can be fixed by Chainfire, although it's always possible that I could be very wrong. You should try asking your rom developer as well. :)

Have you tried any of the dialler codes to launch SuperSu, as a matter of interest?

Edit - The man himself is here. Disregard my amateur fumblings. :D
[SuperSU] eurochild:
till the previous version yes superSU was accessible from settings/superuser although again not showed in app drawer, now the settings shortcut opens the default superuser

Is there anyway to manually edit some system xml to reveal it ?
[SuperSU] Pons:
And that is exactly the issue.

https://github.com/AOSPA/android_packages_apps_Settings/blob/kitkat/res/values/strings.xml#L4906
[SuperSU] eurochild:
omfg *#*#1234#*#* launched the superSU app ;)
[SuperSU] visky642:
Does this mean i can remove Superuser apk from system once i install SuperSu
[SuperSU] eurochild:
i suggest you dont do that
[SuperSU] NZgeek:
Why don't you just download the zip via the first post and install it from recovery? That will replace Koush's su with SuperSU, and you should be able to get to the SuperSU settings via Settings > Superuser.
[SuperSU] jesssiii:
[MENTION=631273]Chainfire[/MENTION] or [MENTION=2910818]PonsAsinorem[/MENTION], I'm rooted without custom recovery. What are the proper adb or shell commands for installing SuperSU to system and gaining root (assuming I wasn't rooted or just wanted to move it to system)? Is there a guide you could point me to?

VZW LG G2 VS98024A
[SuperSU] visky642:
You didn't get my concern mate anyway I got my answer
[SuperSU] 777.300:
That does not work unfortunately

Sent from my Nexus 4 with Tapatalk 4
[SuperSU] Rhian:
Is there any way to get into SuperSu on a tablet (Nexus 7)? This "phone number" works fine on my Nexus 4...

Or should I wait until ParanoidAndroid is fixed?
[SuperSU] eurochild:
just wait till monday that everything will be good
[SuperSU] steviemch:
Not sure why but the latest version of SuperSU won't flash in twrp, on either my N4 or N7.

Sent by Borg neural subspace transceiver node.
[SuperSU] :
You had a bad download, I faced the same problem. Try using another browser, or downloading to your pc and transferring it to your phone.
[SuperSU] gazza1988:
I've had an issue using archidroid on galaxy s3.

In a nutshell it was running for a while at full speed (1600mhz) and battery temp was around 40 degrees centigrade.

I got support in the archidroid thread http://xdaforums.com/showthread.php?p=51634900 and it turns out it was daemonsu that was causing problems and I was told to ask here because it is supersu related.

My phone did reboot on its own in my pocket (i presume it overheated)

From the time I first noticed it was running I did take a full better battery stats log. Not sure if it's helpful. Also in better battery stats it looks to be something called AudioOut_2 that was causing trouble. I've no idea what that means

The reboot seems to have fixed it and I'm not expecting anything from posting this. Just think it could be a rare bug and the better battery stats log could provide insight.

It was like my phone had a sugar rush or something :D

---------- Post added at 11:25 PM ---------- Previous post was at 10:33 PM ----------

I've just loaded up Boeffla config app and it says I had multicore powersave enabled which can cause issues like I had. I found the option and disabled it so I will see if anything else happens.
[SuperSU] Yeti47:
Search back in this thread, looks to be caused by GMD. Last post here http://xdaforums.com/showthread.php?p=51230509
[SuperSU] gazza1988:
I don't have GMD installed.

Looking at the screenshot I took yesterday while this was going off I have a lot of usage of AudioOut_2.
[SuperSU] jazzruby:
I'm not 100% certain (I haven't looked at the code) but I believe AudioOut_2 handles "Touch sounds", "Screen lock sound", etc... And possibly some notification sounds.

Check - Settings > Sound > System

HTH

-JR-

Sent from my Nexus 7
[SuperSU] gazza1988:
Thanks.

My phone has been very loud recently. 2 toddlers screaming their heads off and I still heard it from the next room loud. Even listening to headphones, if I turn it up to the max it distorts the music. I just never turned it up fully.

Looked into possible causes because it is likely to be linked and found my Boeffla config app has "boosted" the sound to the max. Everything is up to the top so I reset them and they are lowered and sounds normal.

Hopefully that's the end of it.
[SuperSU] scar200:
Good update!

Hi, just want to report back that the latest update doesn't FC on my Huawei U9508 anymore. Thank you very much!
[SuperSU] matrixzone:
awesome app
[SuperSU] Crundy:
Is there any way to backup app preferences? In order to use Now TV I have to completely unroot and remove super su, but when I reroot all my allowed / blocked apps have vanished and need to be set up again.

Using the "Enable superuser" and / or "Survival mode" options don't work; Now TV still detected the device is rooted.

I've found I can do it manually by making backups of:

/data/data/eu.chainfire.supersu/files/supersu.cfg and

/data/data/eu.chainfire.supersu/shared_prefs/eu.chainfire.supersu_preferences.xml

And then manually copying them back after rerooting and then doing another reboot, but that's a bit of a pain to do every time I want something on Now TV. I tried using Titanium Backup to backup the app data, but it specifically excludes supersu from the app list (even with system apps enabled)

Am I missing something simple?
[SuperSU] gummie:
Confirmed:

SuperSU is now fixed on the latest ParanoidAndroid 4.2 Beta 4 release. It is now back on the App Drawer.
[SuperSU] Frank Westlake:
This will make it s little easier:

http://simonmarquis.github.io/Android-PreferencesManager/

Find the preferences file and select 'backup' from the menu. When SuperSU has been uninstalled you won't be able to find the backed up file in this program, but after reinstalling SuperSU you will and you will see the 'restore' option in the menu.

Frank
[SuperSU] jorceshaman:
How do you download that? It says to join their G+ for BETA but when I click that I get a 404 error.
[SuperSU] _jis_:
Use F-Droid repository.

Sent from SGNII using Tapatalk Pro 4.5.0
[SuperSU] jorceshaman:
Awesome! Thank you!

This app is quite interesting. Playing around with it now.
[SuperSU] :
Flashed SuperSU 1.94 in CWM, but the SuperSU app is not appearing. Tried on Nexus 4 and Nexus 7 (2013), both running stock 4.4 KOT49H.

Edit: False alarm, turned out I already had 1.94 installed from before, but not as a system app. Uninstalled the update and it appeared back in the app drawer again :)

Weird that full unroot didn't remove it automatically, though.
[SuperSU] 777.300:
Not on my N4 and N7.

How did you do that?

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] psychology:
Manage apps → downloaded → supersu → uninstall updates
[SuperSU] iwobanas:
deamon mode not working on Nexus 7 4.2.2

I'm struggling to get access to root mount namespace on JB 4.2.2 so I tried switching to daemon mode and jusing new --mount-master flag.

Unfortunately after changing

/system/xbin/daemonsu --auto-daemon &

to

/system/xbin/daemonsu --daemon &

in /etc/install-recovery.sh SuperSu stops working and su command always returns "1" error code. I can see two daemonsu processes running so the setup looks correct.

Any idea what else needs to be changed to get the daemon mode working on JB 4.2.2?
[SuperSU] 777.300:
It does not show up there.

Only SuperSU Pro shows up and no update to uninstall.

I used the SuperSU zip to install SuperSU

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] xkjtx:
You might need to uninstall and reinstall or install an earlier version of SuperSU.

I'm running 1.93 and everything still working fine..
[SuperSU] 777.300:
Can someone provide a 1.93 download link?

Re-flashed 1.94 a couple of times but no cure.

Sent from my Nexus 4 with Tapatalk 4
[SuperSU] NWKENT:
Go to my page link here for your requested download >> http://waynekent.com/page26.html

Sent from my 4.3_14.14.14

(Unlocked) XT1028 Moto G

http://waynekent.com/page6.html
[SuperSU] 777.300:
Thanks.

Flashed 1.93, no cure.

Still SuperSU not in app drawer on PA 4.2 Beta 4.

SuperSU only accessible via dailpad with code *#*#1234#*#*

Hope it will be fixed in the near future.

Sent from my Nexus 4 with Tapatalk 4
[SuperSU] PiggySmalls:
Is it not baked into the settings menu?
[SuperSU] 777.300:
Unfortunately not.

Sent from my Nexus 4 with Tapatalk 4
[SuperSU] PiggySmalls:
I'm a little late to the party, so excuse me if I ask anything you've already tried, I know you've flashed the zip, have you tried to download from the play store? Maybe even uninstall, then download from the store?
[SuperSU] DigitalUnderground:
That's so weird as 1.94 works perfect on my N5
[SuperSU] vn00914361:
For those who are using Busybox Pro, the latest binary and applets aren't clean and may cause problem with SuperSU/Hangout MMS/Fauxclock. Do not upgrade your ROM busybox binary with the one from Busybox Pro!!!
[SuperSU] 777.300:
Problem started when Paranoidandroid changed there ROM and are now using Superuser from koush instead of SuperSU.

Since than I ran into problems with TitaniumBackup and switched to SuperSU manually but SuperSU does not show up as an user app on my N4 and N7.

I can only access the SuperSU settings with code *#*#1234#*#* on the N4 and cannot access it on my N7.

It is working but not showing up.

Sent from my Nexus 4 with Tapatalk 4
[SuperSU] PiggySmalls:
So I just flashed the latest Paranoid Android on my N7 (flo), and I can verify that I also have no way to get to SuperSU. I will tinker around with it, and if I find a way to get to it, I'll let you know!
[SuperSU] 777.300:
Great

Sent from my Nexus 4 with Tapatalk 4
[SuperSU] pemell:
Wow. I've been troubleshooting for 1,5 days to find the reason behind my MMS issues. Can't send MMS from any app after updating with busybox pro. Factory reset didn't help either. The only solution was to flash ftf all over again.

I need busybox though, for Secure Settings to work. Need to find a workaround.

Sorry for being off topic.