Related
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
So I used the ACS/Shabbypenguin root method (do a Google search, I can't post links...) and followed the directions exactly. Well almost exactly, I knew of some issues so this is what I did...
First I downloaded Superuser & Superuser Elite (I previously paid for it on a different phone).
Then I downloaded the drivers and Odin and both kernals.
I installed the drivers and put my phone into development mode.
Next, I turned off my phone then turned it back on in download mode and flashed the pre-rooted kernal as per the instructions there.
Finally, I went through the process again to flash in the stock kernal.
Now the other users had issues with USB connection and the phone not being recognised, the answer to that was on page 11 of the above linked thread (editing the vold.fstab file). I did this (using ES Root Explorer) as per the instructions and restarted.
Things seemed fine for half a day. Now my phone randomly restarts, but not always randomly. I can perform specific actions to cause it to freeze and reboot (example, simply opening the vold.fstab file does this EVERY TIME, but I was able to copy/paste it to the SD card and then open and edit it and even copy/paste it back, all using ES root explorer, and no crash/reboot unless I open it specifically and yes, that's with having the system mounted as R/W).
Another thing I noticed since rooting, and it still has maintained the rooted status, is that any time my phone restarts or I restart it, I open the system tray and this stupid "tip" toast message comes up that, prior to rooting, only came up once. Now, it comes up only once after a restart but resets every time.
I tried to sign up for the ACS forums but for some reason, I've not gotten a single registration e-mail from them and messaged half their admin with no response (the fact that the site has no cancel account and no re-send activation option troubles me enough as it is and in my opinion, should be internationally illegal).
Anyway, that's the issue, I need to resolve these random restarts, which may or may not be caused by this vold.fstab file.
Also, I connect now (before when I did the fix, it worked), the computer doesn't recognise the phone so I can't even re-flash using Odin, but the phone works (until randomly restarting which is a pain...), so I am at a loss as to what the actual cause was and since nothing I change sticks when it restarts, I have no idea what the deal is.
Some more information...
Nothing I change sticks. I have programs that I uninstalled, but they still show up in the system tray after a reboot (if I click it, it says that the program is not installed, but it still shows up).
I tried swapping back the original build.prop - didn't stick.
I tried factory data reset - didn't do anything.
I tried a restore in BusyboxPro (stericon or something is the dev) - restored but there were some "errors".
Tried temporarily unrooting (Superuser Elite) - nothing.
I read about a power button issue - my power button is fine.
There is something wrong specifically with the OS in some way that certain actions cause it to freeze and restart. I have a game, "Deathworm" that I can play with no issues or freezes. I can do a few things but:
if I get on the mobile browser, sometimes it will freeze and reboot.
if I run AppManagerPro III, sometimes it crashes when calculating the cache size (always when it gets to 70/125 or whatever the total is, but always at 70 if it DOES crash).
Now I went into task manager and went through and cleared all the app data individually app per app. Before when I tried to do this (before restoring in Busybox, before restoring the original build.prop, etc), it would crash when I went into the downloaded tab of the thing to clear the cache. This time it didn't crash on me.
Other root stuff I have installed which was working before the random rebooting issue:
Script manager (free) and V6 supercharger (also unsupercharging wouldn't stick, which I tried before restoring the build.prop manually)
SuperUserElite
App Manager Pro III
SD Maid Pro
ES File Explorer (free version I think)
BusyBox Pro
SU Update Fixer
Screenshot It
After everything I just did, it seems to (for the moment) be working again, I am just waiting to see if it crashes again. So far I have opened and closed App Manager Pro III a few times and it calculated cache sizes with no crash. Right now, SD Maid Pro hasn't crashed yet open, hide certain tabs (clearing the data so I had to reset those options), close, reopen, scanned with system clean and app clean and actually did the app clean, so far no crashes (my phone would normally have crashed by now), cleared databases and no crash.
Also while I was in there, two programs I uninstalled via the system tray (menu button, edit, uninstall) that kept coming back were a buld.prop editor and some wonkey game (Fall down) or something, anyway those were in the downloaded section of task manager and I uninstalled them through there. Maybe that did it?
And no... still freeze, reboot and not saving any changes.
So far I've also tried uninstalling practically everything I installed and those changes aren't persisting (the uninstalled apps remain uninstalled, but reappear in the system tray or on the home screen if I had an icon there for it).
No changes I make to anything persist except things I save or copy to the SD card.
Tried factory reset again, still didn't stick.
So apparently SOME others have this issue without rooting, I can't tell, there's not a ton of reviews that I can find beyond "F*** STRAIGHT TALK CUSTOMER SERVICE THIS PHONE IS CRAP".
I hate to keep bumping this, but every time I have an issue, I am highly detailed in things and I NEVER EVER have EVER gotten a response EVER on this site, EVERRRRRRRRRRRRRR.
I really really really don't want to waste another ~$200 for nothing.
I would appreciate even a response of "yeah I have this problem too".
I don't want this to die like all the other threads I started...
Does anyone even have a clue as to where I can begin attempting to troubleshoot this on my own then?
What tools should I look into or what logs in what folders?
I know this post is very outdated but there may still be someone tinkering with these older phones still as I am.
Over the past few days I have been trying to get this Straight Talk Samsung Galaxy Proclaim rooted and working just for something to do.
I'm not one to ask for help to often so I end up doing a lot of reading and a lot of trial / error.
In my reading I have seen quite a few posts / comments around the net stating not to use the Shabbypenguin root method
as it is very buggy and unstable.... I can not tell you from experience so please do not quote me. I ended up using the TeamProlusion
root method and all has went very well other than a few minor problems I need to work out.
In all honesty I'm not real sure what I may post or may not.... ( Yes I need to REread the rules for sure ) but I
will leave this link for anyone that may be in need... Mods / Admins please feel free to edit this post if this is not permitted and
please accept my apologies.
Please google androidarea51
It not happens always, but when it happens, it's always when the system is starting, when the apps are starting and being granted root permissions, etc. If I don't do anything, is fine, but If I unlock my screen while the apps are loading on startup and start to open some apps, it reboots(not always). I don't know If it overloads or something, but aLogcat doesn't record anything after the system reboots. I've already used Boot Manager to disable some apps from starting, but the problem persists. It's a Moto X 4.4.4 Stock and I never had this problem before. I belive t's a Xposed Module, but I want to know which one is. I've already did a factory reset, then rooted again, but the problem persists.(before I rooted I wasn't having this problem, this is why I believe it has to do with some Xposed Module or something related to root.)
PS: I will pay you 5 dollars(via Paypal) If you help me and find the problem (what's causing it) via these 2 logs. I know it isn't much, but I want to show some appreciation for helping me.
Here's the kernel message:
https://www.dropbox.com/s/5v9bcbsbqk3z3sq/kernel.pdf
Here's another one that I got right after the reboot happened.(I've waited for the device to start, connected my device to USB, then went to adb and wrote # adb shell dmesg.
https://www.dropbox.com/s/l2ghokfk2w97yv4/Kerneldef.pdf
Thanks.
Xposed Module
I belive t's a Xposed Module, but I want to know which one is.
Click to expand...
Click to collapse
Try to uninstall the modules one by one and see which one is causing the problem. What are the modules that you installed as of this moment?
PS: If you're rooted try wiping cache + delvik cache in case you didn't do that.
I've already tried cleaning the cache. Xposed modules: ActivityForceNewTask, Complete Action Plus, GravityBox, Smooth System Progress Bar, Statusbar Scroll to Top, Statusbar Volume, TintedStatusBar, XBlast Tools.
Just happened again. Uploaded another kernel log .
alex91s said:
I've already tried cleaning the cache. Xposed modules: ActivityForceNewTask, Complete Action Plus, GravityBox, Smooth System Progress Bar, Statusbar Scroll to Top, Statusbar Volume, TintedStatusBar, XBlast Tools.
Click to expand...
Click to collapse
Try uninstalling them all first and see what happens. Then install them one by one and check which one coincides with the others in order to see which one causes the problem.
Hello, I have a Redmi Note 3 Pro running sMiUI (based on the Xiaomi.eu ROM) but this seems to be irrelevant.
while this strange behaviour doesn't seem to be limited to this device, being noted here and here, it does seem that the symptoms are the same.
In the SuperSU logs i found that firstly Whatsapp tried to gain root and was denied, followed by zygote requesting 3 times over the following few hours. The log for each is blank.
I have just rebooted my device and after unlocking whatsapp immediately requested root. Yet to see zygote request root again but I'll update you should it appear.
UPDATE: Whatsapp has again requested root.
UPDATE2: WhatsApp continues to request, however zygote has not. It appears to be happening every half-hour (ish)
U3: uninstalled WhatsApp, will see what happens at the half-hour mark.
Anyone know what's going on?
Also some probably irrelevant weirdness but I'll write it anyway given this only started appearing after this happened:
My phone did something weird earlier, I restarted, and normally on my ROM it just has a spinning little loading thingy in the middle of an otherwise blank screen, then goes off and reboots, showing the Mi logo, this time however it randomly showed a kinda-pulsating android logo shortly after the usually " spinning loading icon" and then continued to the usual Mi logo. Given I'm running sMiUI I've never seen it display a large android logo before like this. I just rebooted again and this behaviour was not repeated.
Try xiaomi.eu rom, or stock rom. Or might be you're just installed modified WhatsApp and zygote apk from untrusted source. I don't use sMIUI
immns said:
Try xiaomi.eu rom, or stock rom. Or might be you're just installed modified WhatsApp and zygote apk from untrusted source. I don't use sMIUI
Click to expand...
Click to collapse
The struggle I went through to get off of the vendor ROM, I'm not going back to stock. sMiUI was based on the Xiaomi.eu ROM, so the zygote is probably straight out of that.
I have installed WhatsApp from Google Play so I assume it doesn't get more secure than that. I've made no attempt to replace zygote, I don't really know what it does, something about starting apps.
The ROM I'm using doesn't seem to be remotely relevant to this, given it's happened on 3 different devices from different brands as I can see from the links I provided.
It doesn't make any sense. WhatsApp is used to not request any root permission unless it's infected by mallware. You can try to use xiaomi.eu rom alongside with 3rd party mods instead of use pre-moded rom from sMIUI.
immns said:
It doesn't make any sense. WhatsApp is used to not request any root permission unless it's infected by mallware. You can try to use xiaomi.eu rom alongside with 3rd party mods instead of use pre-moded rom from sMIUI.
Click to expand...
Click to collapse
Indeed, last WhatsApp update was 13th December, so I would have seen this happening before today if it was in normal WhatsApp. This is nothing to do with sMiUI, I've had this ROM installed for many months now with no issues.
And as previously stated it is based on Xiaomi.eu ROM.
But yes my suspicion is malware, however it's not specific to MIUI or any varients as this was also occurring on a Galaxy S5 and another device.
Everyone: Please read the entire thread before replying so I don't have to keep restating facts
Hey, i have same problem too, im using redmi note 2, today i get notif, whatsapp need access root, after several minute, zygote need access root too, now i deny that access at super su
first time root/customrom/kernel etc.
Ive had the same thing happen..First time I thought it was strange though and denied permision was with the zygote thing asking permission...ive granted whatsapp and whatsapp extensions permisson for example cause i thought that was just the way it worked. ive granted LMT permission and a couple more apps
thought it was more of a windows type "" do you trust this program to do things" type thing.
things is my, installation is pretty fresh. and I dont get where I should've gotten malware from
htcm8/Viperrom/elementalx kernel
bunch of file explorers (sdmaid /totalcommander) and terminals all from the playstore. Xposed installer and a couple modules that all seemed reputable with ongoing xda threads and downloaded from the original source. amplify/bootmanager(something with that maybe?)/chromepie/secure settings for a tasker profile/minminguard.
you see something we have in common on the phone?
phone is running fine..nothing strange. The zygote i got for the first time today and I denied and hopped on google...whatsapp is in my rootlog constantly. i see the greybox popping up every once in a while that root was granted. never thought anything of it.
today I installed termux ternimal from the playstore...maybe thats where the zygote su request comes from?
---------- Post added at 10:05 PM ---------- Previous post was at 09:39 PM ----------
from what I see elsewhere the whatsapp extension module in xposed, which is a root app might have something to do with the whatsapp requests. I dont exactly know how these things work but the altering might explain app doing thing they normally dont do.
dont know about zygote...got it one time and it has not been back
Same here.
I'm on a fresh install and this zygote su request wasn't appearing until I reinstalled all my apps.
Another forum states that zygote is run at such a raw level that it simply would never request root.
I am for now denying su requests with little to no adverse effects.
Can anyone confirm for certain that zygote should never need to request root? Is there anyway to dig out the rogue source/apk when av apps are showing nill?
As I have nothing Whatsapp on my phone, thinking it may be an xposed mod. Might be a good idea for us to list are xposed mods so we can cross reference. Not sure?
samsung i9505 | resurrection remix | android 6
Hello, I have a Samsung Galaxy A5 2017 running AOSP Extended 4.6 rom. I'm using TWRP recovery and have it rooted with SuperSU. I'm having a problem where my wifi won't turn on. The button is grey, and when I try to switch it on it says "turning on wifi" but the button never switches to blue, and it never finds any wifi. It's totally broken.
It's an old phone, so I thought it might be a hardware issue, so I did a backup then a clean wipe, and whattaya know, the wifi worked fine. So it's something gone wrong particularly in the "data" segment of the backup, since restoring the backup without the data block selected acts just like a clean wipe. When I do a full backup with all apps and settings, that's when the problem happens.
I tried to just start from scratch, but for some reason titanium backup is hanging on restoring all my apps and settings and won't do it, so it's a major pain in the ass, and I'd rather just figure out what the problem is on the full backup and fix it so I can keep my phone nice and familiar.
Okay, so I ruled out any user apps as being the problem, as I completely uninstalled every user app, without any change. I can't uninstall most system apps without breaking the OS, so I hope the problem is in some internet configuration setting or something that I can easily change.
Does anybodoy know how I can fix my wifi?
Thanks!
0
Hello, thanks for the response! I haven't had an opportunity to try this but I will when I get a chance and I'll post the log. And yeah I've been trying to swap to magisk, but it doesn't like the modded boot.img of my custom rom, it won't do it. I'm trying to figure it out. >.<
Seppppx said:
You can run logcat in adb
See : https://developer.android.com/studio/command-line/logcat
Also you can install a logcat app like MatLog to get logs without a computer (requires root).
That might give you a hint to why the wifi doesn't work. If the logcat doesn't show anything that would indicate the problem in detail try obtaining the kernel logs with dmesg or kmsg
See : https://forum.xda-developers.com/showthread.php?t=2185929
I also recommend using Magisk insteaf of SuperSu as chainfire sold it to a random sketchy Chinese comapany.
Click to expand...
Click to collapse