yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
Well, maybe we can come up with a solution, it's certainly worth thinking about one.

I was kind-of curious how long it would take and how many would complain about this - by far the most complainers have not looked for enough to see the options to disable it under settings, which I find hilarious to no end. Right now I'm just experimenting with it, really. With StickMount I did the same thing, and it almost quadrupled sales overnight. While I certainly don't just care about the money (though I do need to eat), that's the sort of sales increase you at least look into.

SuperSU is one of my most-used apps, and I've put in a lot of effort to make sure the SuperSU free version is fully functional and contains everything you may need, while the Pro version only adds things you may want. I don't hold anything against those who do not want or simply cannot pay. It's all perfectly fine with me.

However, I do feel there's a bit of a knee-jerk reaction to the notification though. I've heard from various people that all they saw was this "go pro" notification, bla bla, complain. This while there is actually no *new* notification. The notification was always there, I just added an extra line to it. If you turn off notifications, that line too will disappear.

I'm not sure what I'm going to do with this, if I'm going to keep it in, or if I'm completely throwing it out (I might!). What I do know is that by far most users of SuperSU only accept a prompt now and then, but never actually go into SuperSU, and certainly not into the Settings section which shows you the option to go Pro. A notification change like this makes them aware they even *can* go pro.

I've honestly also have had several dozens of responses by email, PM, Twitter and G+ from people who told me they just bought Pro, that they always thought they should but never really gotten round to it, and were pushed into it by the notification. That is good for me. But I am also well aware this effect goes away rather quickly with the passage of time (!) and as such in a few weeks, it might have already outlived its purpose and its no use doing this again until a few months from now.

Suggestions are always welcome, but I'm not going to decide one way or the other today. I might disable the notification if installed as /system, or only do it once a week at most, or detect certain ROMs if an agreement is reached, or if we find some other suggestion, etc. Feel free to put forward your thoughts.

I would also like to point out that you have clearly visible donations links to yourselves in the ParanoidAndroid threads ... :)
[SuperSU] tgp1994:
I really like the fact that you actually put in an option to disable the message, I think something like that is fairly rare in free+paid apps.

Heck that forethought of yours might even be my motivation to purchase the pro version :)
[SuperSU] shaggyskunk:
Re: [30.01.2013] SuperSU v1.02

I guess that already having had the pro version, from almost the first day that I rooted, is why I never even saw the prompt ;)
[SuperSU] :
Re: [30.01.2013] SuperSU v1.02

...
[SuperSU] cbeckstein:
AW: [30.01.2013] SuperSU v1.02

Fine...

But: isn't *#1234# already a reserved dialer code (showing AP / Phone / CSC as far as I recall)?
[SuperSU] polobunny:
I personally don't think the notification is that intrusive, and I bought one software because of similar notification that would appear every 10 unlock of the phone (software is DelayedLock).

I was thinking of buying SuperSU Pro eventually, and let the setting for the nag enabled so to remind me.

From my own experience, I wouldn't disable it completely or leave it disabled by default. It's a small price to "pay" for the user to see an additional line when su gets granted or denied. Hope you work something out. =)

---------- Post added at 01:38 PM ---------- Previous post was at 01:29 PM ----------

I believe you are right, but I don't think it should get triggered since the SuperSU code is *#*#1234#*#* and not just *#1234 etc etc. The pair of *# saves it. :p Correct me if I'm wrong.
[SuperSU] Chainfire:
I'm go to leave off with responding to the notification stuff for now, more food for thought and I'm in a rush.

Actually it seems you are correct - on my S3 if I use the 1234 code it opens both SuperSU and that app you mention.

As for *# vs *#*#, all I set in my app is the numbers. Whether it is *# or *#*# depends on the device. My GalNex uses *#*# while my S3 uses *# (I figured this out just now)

I'll put some more thought into this, but probably the 1234 code is going away

EDIT: actually, it seems only the 1234 code works on my S3, the other one doesn't. Hmm....
[SuperSU] polobunny:
Didn't know that it was phone-related, I thought all 'droids would be similar. Good to know. One code should be enough I imagine.
[SuperSU] molesarecoming:
i really dont know why you feel i stepped on your foot there, whats wrong with my "attitude," there is no reason to get pissy with me, none at all. i recognize his work, all i am asking for is a reasonable solution for rom makers because this nag screen does not allow us to ship a serious product anymore. why do you have to make this humble request into a negative blame game? btw, dont even try to pull this donation bs on me, you have no idea how much i "earn," its no place for making broad assumptions.
[SuperSU] molesarecoming:
that was a long text to read. i want you to understand, i do not complain. i know how much work it is to program, its not a foreign concept to me. i myself sat half a year now day and night, i know it sucks and i know xda is not compensating the loss. but all i am asking is if you would be down to have a talk. thats really it. if you think there is a reasonable solution that would make you happy, and rom makers likewise then that would be really kind of you.
[SuperSU] molesarecoming:
to make a start,

i think the notification is certainly a new way and i have not yet seen it happen in that scene, but why not --- nothing against it. but i would not ship it like this in a rom, and i believe this is where superSU finds its most propagation. i am open to virtually ANY solution at this point because i love superSU and it would hurt to go back. whatever you have in mind, i am sure i can listen to it and make compromises where necessary. for all i care i put a huge "buy supersu" flag on the first spot of every opening page. or a banner "powered by superSU" made by our graphic artist, whatever ... im curious for your suggestions. and please, i am not criticising, we all love what you do and wish to support you.
[SuperSU] Chainfire:
I am always open to discussion about this, you're probably not the only custom ROM developer who feels this way. And I don't like to lose the ROMs that include SuperSU either. If you have any ideas about how to solve this (structurally - a per-ROM exemption or multiple different versions do not fall into this category) I'm all ears.
[SuperSU] molesarecoming:
a good way in my opinion would be to create more awareness. root is an important part of any rom and people should be made aware of it. that could happen by incorporating superSU into logos, opening pages, panels, about categories and anything that leads to donations. just like dell says "powered by intel" or whatever roms declare their alliance to superSU.

a share of donations would be posible, in exchange for a special license - but dont dont get your hopes up. you know as much as i know that developers do not "earn" on xda. i dont think thats going to cut it. you should get support from the actual users.
[SuperSU] Chainfire:
While I'd love a "powered by" thingy, I was more looking into the technical side of detecting the various way SuperSU gets installed, then auto-disabling for custom ROMs that include SuperSU pre-installed. I'm also specifically not looking for a donation share (by all means keep them)

I'd elaborate but I have to run!
[SuperSU] molesarecoming:
roms could provide a broadcast or an intent and call supersu. or supersu shoots an intent and looks for an answer from the system. or framework extensions. plattform manifests or signatures. for PA we are using an intent. i know its not secure and can be hacked (it got hacked in a week lol) but then again, who cares, its those that appreciate that are willing to help.
[SuperSU] polobunny:
No intent is safe anyway, but even if it's not secure you can already disable the nag via the settings for now. No need to hack it for "normal" users.
[SuperSU] molesarecoming:
sure, but im not acting on the behalf of a single user. i know i can switch it off, i usually buy apps i like, and bought ssu.pro. but when you ship a rom, you have to make design decisions, at least if you take your job serious. the beauty of android is that although it is modular, all the cogs are working together, in stock android there is nothing that stands out to interrupt the overall flow. i love their principles and of course i try my best to implement them myself. right now i am shipping a rom that asks for money for every little click - and no matter if you guys kick me with accusations of not being able to value a good programming job, and you're dead wrong, i have my standpoint and it seems like chainfire does understand what im trying to express.
[SuperSU] goodtimes50:
FWIW, I'm still getting some strange notification behavior. I'm on v1.02 and I just got what appeared to be looping notifications after reboot. This time there was NOT a log entry corresponding to each notification. In addition to that, notifications are disabled in settings.
[SuperSU] polobunny:
Misunderstood me. I was saying the intent would work fine if Chainfire agreed to it for "batch disabling", even if hackable by a single user, because there's already a way to disable the notifications via the GUI so another way is not exactly a problem. Anyway, I'm just stating my opinion here, I'm in now way in a position to decide, just a simple user.

On a sidenote, I think you're making quite an ordeal out of something so simple as an added line to the su granted/denied notification. But again, that's just me, not Chainfire.

Does it only happen with SetCPU?
[SuperSU] goodtimes50:
No, it's a number of apps. Off the top of my head it includes KTTweaker, SetCPU, SetCPU Profiles Service, ROM Toolbox Pro, Lightflow, and one or two others I can't think of at the moment.
[SuperSU] Chainfire:
Try going to Settings --> Application Manager --> SuperSU, then do both a Force Stop and a Clear Data. Then reboot, and see if the problem persists.
[SuperSU] My1xT:
I didnt dev anything but I think I know whatcha mean, pal...
[SuperSU] Chainfire:
How about I create an additional APK you can preload in the ROM, which should be something like 10kb, which SuperSU will detect and disable nagging if present ?
[SuperSU] My1xT:
yeah, why not...

the FAR easiest way...
[SuperSU] :
Full wipe on Revolt for i9100, updated to 1.02 and installed pro from market

converted supersu to /system, rebooted and supersu is gone LOL (no icon on app drawer)

Had to reinstall it from play google! (said it wasn't installed(WTF?))

Bug?

Edit:

The icon doesn't appear in app drawer but supersu.apk is in /system/app

Weird hum? LOL

Edit2:

If i try to uninstall SuperSu, all i can do is disable it! (WTF????)
[SuperSU] Chainfire:
I've actually seen this one before, no idea what is going on as of yet - unfortunately I cannot reliably reproduce the issue. Doesn't just happen with SuperSU converting to /system either. I've seen this with random apps when moved into /system, even if they had never been installed before - so there can't really be any leftovers.
[SuperSU] :
See my edit2 on my post! :)
[SuperSU] dpwaters72:
No more root!

I no longer have root access after updating SuperSU. All my root apps no longer work including Titanium Backup. I have tried the "Reinstall" cleanup option to reinstall the SuperSU app but I am having no luck. All worked fine until the update.

I am looking for a little direction here. I really do not want to have to do a full wipe and reinstall but I will if I have to. Just wanted to see make sure there is nothing that I am missing.

Thanks for your assistance.
[SuperSU] polobunny:
Flash zip in OP from recovery. Usually fixes all there is to fix (or nearly).
[SuperSU] dpwaters72:
Okay. I will give that a try. Thanks.
[SuperSU] pat357:
I went through all the SuperSu Pro related updates I got via the Playstore (quite a few, I must say), but today I got a request for a "dumpstate_RESET_BY_SYSTEM". At first I had no clue about the cause, but after searching and tinkering what software was recently installed, I came to SuperSu Pro.

The dumpstate was saved on "/data/log/dumpstate_RESET_BY_SYSTEM_xxxxx.txt"

Maybe this can help to find the cause ?
[SuperSU] juming:
Re: [30.01.2013] SuperSU v1.02

This happened on me yesterday, today before I do move to system, I just delete superuser.apk on my /system/app since the new one that will move to system is on /data/app and it can move flawlessly.

Anyway I cannot call super user by entering *#*#7873778#*#* but it can called by *#1234# followed by CSC after quit from supersu. I'm on I9305 4.1.2
[SuperSU] molesarecoming:
that will be perfect! i will make up for it in any way i can come up with.
[SuperSU] dpwaters72:
Re: [30.01.2013] SuperSU v1.02

Actually, unchecking "Respect CM root settings" in the SuperSU settings fixed my issue
[SuperSU] Bigdrago:
Quote:

Have you used the full uninstall in SuperSU? The one to lose root and all? That will wipe everything.

Yes I used that.
[SuperSU] progster:
Re: [30.01.2013] SuperSU v1.02

I unchecked auto approval to make it ask for permission and it worked for me.
[SuperSU] polobunny:
That didn't really fix the issue though, simply override the CM settings.

In your settings, go to developer options > root access and make sure it's not on disabled. ;)
[SuperSU] Chainfire:
Just in case anybody wonders in here with this problem tonight, we have found the problem with logs/settings freezing the app, then after 30 seconds crashing. Will be fixed next update (asap).
[SuperSU] :
Re: [30.01.2013] SuperSU v1.02

Using *#*#7873778#*#* and the 1234 works for me but the issue is that:

I have SuperSU installed in /system/app and the button that says:

Install SuperSU backup script is grey.. Isn't detecting SuperSU properly.

Can you look at it Chainfire?
[SuperSU] My1xT:
try to do the "supersu number" with only one part of *# maybe it helps
[SuperSU] juming:
Same result, only *#1234# working, but it also display CSC after exit from SuperSU, already try *#7873778#* + dial, *#*#7873778#*#* + dial, both actually call those number :p

Maybe on GT-I9305 version 4.1.2 has slightly different command ?
[SuperSU] Chainfire:
Have you tried rebooting? What does the text of the backup option say?

After some investigation, it seems the Samsung dialer just doesn't do secret codes it doesn't already know. 1234 is a code it knows, so that works. The other one only works with a proper dialer like AOSP. I think.
[SuperSU] juming:
Re: [30.01.2013] SuperSU v1.02

Thank you for information.
[SuperSU] VivaErBetis:
Re: [30.01.2013] SuperSU v1.02

Just for the records; both "secret codes" works in a Nexus4 stock ROM.
[SuperSU] Chainfire:
I need somebody who has the crash in logs/settings to try the attached version of SuperSU to see if it fixes the issue. Thanks!

Yeah, I know this one doesn't fix the problem. Testing another version...
[SuperSU] quintas84:
Problem

Hello i want report one problem that happens to me in CM10 when i use version 0.89 no problem but if i update app via market or cwm i lose my root and for example titanium backup says that superuser its not garanted

thanks in advance
[SuperSU] Ghostfreak NB:
Re: [30.01.2013] SuperSU v1.02

Check your root again!

Try UNrooting and rooting again as that problem is non -existent for me!
[SuperSU] Mailia:
Try disabling "Respect CM root settings" in the SuperSU settings.
[SuperSU] cbeckstein:
When I let supersu 1.02 install / convert itself as / to a system app from within its settings then after it has (sucessfully) done so all the su permission settings (previous grants and denials) for all the apps are gone (ako full supersu amnesia)...

this strange thing does not happen when I update supersu via the CWM zip on xda
[SuperSU] juming:
Re: [30.01.2013] SuperSU v1.02

Yes, it's happened on mine too.
[SuperSU] VivaErBetis:
Re: [30.01.2013] SuperSU v1.02

+1

Add more: it doesn't happen with previous version when I installed it from Play and convert to system app. But, when I upgraded from Play to this newest version I need to make it system app again and it forgets everything in the process.
[SuperSU] Chainfire:
That might end up being useful information, thanks :)
[SuperSU] quintas84:
Thanks its working now
[SuperSU] Pons:
Before you did this, did you try the cleaner (and preferred) method of allowing root in CM settings? Menu, settings, developer options (make sure it's on), and root access set to apps only or apps and adb (whichever you use). That way, the app and ROM work together, instead of app overriding the ROM preferences. And if that doesn't work (it does for me), then we have a bug to squash.
[SuperSU] quintas84:
yes i try it before and doesnt work but now i activate respect again in Supersu and they works toghether
[SuperSU] joemhewitt:
The latest update of SuperSU doesn't respond when I click the settings button on my Samasung Galaxy Player. :(
[SuperSU] gontera:
After SuperSU is updated to 1.03, it still crashes in logs/settings.
[SuperSU] Chainfire:
Here's another test version for the crash on logs/settings.

Please make sure you have adb working, reproduce the crash, then dump the entire logcat to a file, for example like this:

adb logcat -d > logcat.txt

And please attach (a ZIPped version ?) of this logcat.txt file !

NOTICE: This is a debug version! It is slower, has security issues, depends on Android running, may segfault in edge cases, etc. DO NOT RUN THIS UNLESS YOU ARE HELPING ME DEBUG

Also note that one person was not able to reproduce the crash with this debug version... which is weird. Let me know if this version makes the crash disappear...
[SuperSU] SlimSnoopOS:
Hey Chainfire,

I'm using a Verizon GSIII and I noticed a user created a thread about SuperSU here. It's a question I'm sure you would be best to answer since it pertains to the coding within your app. The user only has about 3 posts so they can not post their comment here. Would you care to help them out with their inquiry?

Edit: Thank you for replying in that thread Chainfire!
[SuperSU] :
Tried rebooting and the text that appears is:

Install SuperSU backup script

SuperSU must be installed in /system for this feature (see above)

And SuperSU is installed in /system

:eek:
[SuperSU] My1xT:
the option install into system you have to repeat after Playtore Updates, coz the update cannot go into /system by itself.
[SuperSU] Chainfire:
Indeed. If still trouble after that, let me know the output of:

adb shell pm path eu.chainfire.supersu
[SuperSU] :
Re: [30.01.2013] SuperSU v1.02

So that's why it wasn't working :P

Thanks guys :D

Now working properly!
[SuperSU] Chainfire:
v1.04 released !

Just uploaded v1.04. I think we've finally found and nailed the crash/freeze issue. I say issue, but I mean issues, as there were actually two issues - but both showed similar behavior in SuperSU. Both of these issue were related to PackageManager:

(1) PackageManager can sometimes segfault when called from an app, as the environment is not set up correctly on some devices. That requires a workaround for some devices. This was the first fix, and actually solved the problem for some.

(2) PackageManager will sometimes not return from calls unless USB debugging is enabled. This one was really hard to track down, because I asked people for logcats, and then they couldn't reproduce the problem :) This one also required some trickery to get past, but I believe this should now be fixed. I've tested on both Android 2.x and 4.1 devices - I hope there's no problem remaining on 3.x and 4.0 :)
[SuperSU] diavolo_78:
unroot

Hi, I made the root using CWM 6 touch and update the file supersu 1.04, I wanted to know how I can remove the root? There any file to flash in recovery ?

thank you very much

ics 4.0.3 galaxy S2
[SuperSU] THE RED BLUR:
Re: [01.02.2013] SuperSU v1.04

SIGNATURE

PHONE : SGSII

Sent via: Tapatalk 2

Main ROM: AllianceROM v6 LS8

KERNEL : Dorimanx 7.45

(DEFAULT PROFILE AND SETTINGS )

MODEM : LS8

BATTERY : Stock 1650mAh

EXTERNAL Sdcard : Samsung Class 10 32gb

LAUNCHER : Apex

THE CAVE = My Guides list to install NeatRom and other ROMS and kernels on LSJ and LS8 + tools to have a bug free rom and kernel + how to back up and RESTORE ROM OM FULLY = http://xdaforums.com/showthread.php?p=35923600

1.Current list of kernels on LSJ and pros and cons

http://xdaforums.com/showthread.php?p=36698607

2.Rom Nuke / Wipe scripts

http://xdaforums.com/showthread.php?p=36742265

3. GS2KERNELWIPE script

http://xdaforums.com/showthread.php?p=36742198

4.Fast Dormancy :

http://xdaforums.com/showthread.php?p=36396636

5. How to install full wipe with rom nuke on LSJ

http://xdaforums.com/showthread.php?p=36655790
[SuperSU] diavolo_78:
mmhhh I do not understand ....
[SuperSU] polobunny:
Full unroot option. Right there, on the screenshot...
[SuperSU] diavolo_78:
ok thanks, then uninstalls of supersu apk ?

then the root I can do when I want to ?
[SuperSU] Pkt_Lnt:
The CLEANUP section is the same as removal that you are asking to do. No need to flash another app, just use cleanup.
[SuperSU] diavolo_78:
well , thanks for the explanation.
[SuperSU] THE RED BLUR:
Re: [01.02.2013] SuperSU v1.04

Lol. I thought the screenshot would have been enough. I guessed wrong:rolleyes::D:p

SIGNATURE

PHONE : SGSII

Sent via: Tapatalk 2

Main ROM: AllianceROM v6 LS8

KERNEL : Dorimanx 7.45

(DEFAULT PROFILE AND SETTINGS )

MODEM : LS8

BATTERY : Stock 1650mAh

EXTERNAL Sdcard : Samsung Class 10 32gb

LAUNCHER : Apex

THE CAVE = My Guides list to install NeatRom and other ROMS and kernels on LSJ and LS8 + tools to have a bug free rom and kernel + how to back up and RESTORE ROM OM FULLY = http://xdaforums.com/showthread.php?p=35923600

1.Current list of kernels on LSJ and pros and cons

http://xdaforums.com/showthread.php?p=36698607

2.Rom Nuke / Wipe scripts

http://xdaforums.com/showthread.php?p=36742265

3. GS2KERNELWIPE script

http://xdaforums.com/showthread.php?p=36742198

4.Fast Dormancy :

http://xdaforums.com/showthread.php?p=36396636

5. How to install full wipe with rom nuke on LSJ

http://xdaforums.com/showthread.php?p=36655790
[SuperSU] Pkt_Lnt:
It is an issue of native language and comprehension of a different language than ones native tongue. I see it in the forums all the time, and realize that expressing the way we think can be very different.
[SuperSU] diavolo_78:
thank you very much , in fact I do not speak English well ... but I know what I do ....:eek::good:
[SuperSU] Myster:
This is a bit crazy now ... i upgraded to latest version 1.04 , moved to system directory via menu command , and now i lost USB Debugging !!

I am on Samsung Gnexus Maguro with MINCO 6 ROM which does not have a visible menu to enable USB debugging !!!

Can anyone help ?
[SuperSU] polobunny:
Go to developer settings?

Tap build number 7 times in about phone to enable developer settings. Then turn USB debugging on in it.
[SuperSU] Myster:
Thanks mate , didn't know this trick !! , problem solved now :good:
[SuperSU] My1xT:
yeah, with the hidden dev settings in 4.2 google is making a fool of us...
[SuperSU] andrei1015:
New guy here. The good fellows over at MADteam said this alternative gives the permissions faster. It is the second app that convinced me to buy it in the first 5 minutes of using it. It doesn't only manage the permissions faster it also makes my phone faster! Worth every penny! Thank you Chainfire!