Hey everyone has anyone had this problem yesterday i got like 100 shell granted root permissions in a type and it showed my phone down to a crawl so i took off the battery and it was fine for a while then it started again and the only thing i gave permission for root was super user... Later i put everything to deny access
Sent from my SPH-D710 using xda premium
steviee7 said:
Hey everyone has anyone had this problem yesterday i got like 100 shell granted root permissions in a type and it showed my phone down to a crawl so i took off the battery and it was fine for a while then it started again and the only thing i gave permission for root was super user... Later i put everything to deny access
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
On mijjz goodness rom? I was getting that too. I just reboot or it keeps happening.
Sent from my SPH-D710 using xda premium
That was happening on my ROM and it turned out to be the beta su binaries I had put in it. Replaced them with the standard SU and Busybox binaries and it stopped.
Need Help? Find us on our IRC
irc.flux.cd
#TeamRejectz
Mines on stock rooted ff18 one click Odin
Sent from my SPH-D710 using xda premium
Do you have SU notifications turned on? If so, try turning it off.
I did turn them off i also put if anything asks for permission to deny it... And it hasn't popped up yet
Sent from my SPH-D710 using xda premium
Ive been having that for a few days now. I thought i haf some wierd virus. Ive neen going into Super User app and checking "temp unroot" then unchecking it afyer a few seconds.
Id try scarmon's idea with the su binaries. I remember that i used superuser to update the binaries and that might have been when it started.
Sent from my SPH-D710 using xda app-developers app
How would i flash the binaries if i don't have a custom recovery
Sent from my SPH-D710 using xda premium
Related
I just wanted to check if anyone else is having issues with the newest SetCPU update? I'm getting superuser permission notifications like every 5 seconds and they've just been filling up the su log.
I've never had this problem before, no other app is doing it, and I've tried wiping the data for superuser and SetCPU. I looked at previous threads about this issue, but everyone suggests turning off superuser notifications. That's not the answer, as that's just ignoring the underlying problem. Any thoughts?
Sent from my SPH-D710 using xda premium
Looks like others on the market are having the same issue. I'll just sit tight.
Sent from my SPH-D710 using xda premium
I'm having the same issue. Not sure what the problem is.
I had the same issue after the update, I disabled my profiles I set and it went away. I guess that's causing the superuser issue.
Sent from my SPH-D710 using xda premium
I have the same problem. Ended up turning off notifications in su. Have to wait for fix for now
Sent from my SPH-D710 using XDA
Are you all having problems with the release that was pushed tonight?
Sent from my Samsung Epic 4G Touch using Tapatalk
What build are you on? I'm on fc06 and haven't had it happen.
Sent from my SPH-D710 using XDA
Update just went through. No issues here
I had the same issue. I was on FC05 when I initially updated to the newest. Had to uninstall.
Setcpu got updated on market and new update fixes the su problem...
Sent From My SAMSUNG GALAXY S II
I updated soon as the update came up and was getting annoyed by the permission pop ups. I just contacted the developer and told em. He told me to turn off notifications till he comes up with a fix. Which he did pretty quickly! Anyways what I'm trying to say is b4 coming to xda about it why not contact the developer directly to notify them
Sent from my SPH-D710 using XDA
So I have been trying without a single success on multiple different root methods on this forum to root my little brother's mt3gs. I have never had this much trouble rooting before and I can't get anything to work at all. Is there any method at all? I'm about to give up.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Have you tried this way? http://forum.xda-developers.com/showthread.php?t=1189485
yeah i have tried that one. everytime the phone reboots to bootloader then it gives me the "140 fail error"
Never mind, for some reason after installing HTC sync it worked lol
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Why do most roms OP state to "fix permissions" directly after flashing the rom, when that does nothing... it fixes them in .3 seconds? lol.... pretty sure it's best to do it after setting the phone up the way you want. Where it takes a couple minutes and actually gives you a log of what is fixed. Just curious if I'm wrong in thinking all this jazz.
Sent from my SGH-T999 using xda premium
I had no idea either. But this cleared it up for me.
http://wiki.cyanogenmod.org/wiki/Fix_permissions
Sent from my Galaxy Nexus using xda premium
Probably just because it can't hurt to do one, that and if an issue arises they can be certain that it was done.
Sent from my SGH-T999 using xda premium
Ive wondered it myself. Never do it though. To me its there for when you run into problems with FCs and such. I assume its the devs trying to be proactive for those who dirty flash.
Ive seen it screw things up to btw.
Sent from my SGH-T999 using xda app-developers app
I know what Fixing Permissions does, just why they tell their users to fix them before anything can be broken, is where my curiosity begins, if I remember right even after a dirty flash they don't wont be fixed til after a reboot...
my way of doing things
wipe data/system/cache
flash rom
boot up>let sit for 5 minutes>install through TB or recover data
boot into recovery and fix permissions, which takes a couple minutes, if I have errors.
Congratulations, no one cares.
psykhotic said:
Congratulations, no one cares.
Click to expand...
Click to collapse
True story, I'm a terrible person.
Sent from my SGH-T999 using xda premium
only fix permissions if you have issues of force closes or log cats are showing files as unreadable... basically if you are having issues of some sort.
also, good idea to fix permissions from terminal while booted into android if you are using a recovery that has not been updated in a long time
cobraboy85 said:
only fix permissions if you have issues of force closes or log cats are showing files as unreadable... basically if you are having issues of some sort.
also, good idea to fix permissions from terminal while booted into android if you are using a recovery that has not been updated in a long time
Click to expand...
Click to collapse
Oh, I know how to run and use fix permissions. I'm just curious as to why some rom cooks give instructions that are useless.
Sent from my SGH-T999 using xda premium
That's a valid question.
I think it's an instruction for crack flashers.
It levels everything out.
Especially, if you are trying to keep your data
Sent from my SGH-T999 using xda premium
********UPDATE*********
Thanks to hardcore,I found a fix in another thread
forum.xda-developers.com/showthread.php?t=1843837&page=4
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Ever since Jellybean instead of apps force closing as they normally would my phone becomes unresponsive and reboots after 2-3 minutes.It gets quite annoying and I wanted to know has anyone else has been getting this issue. I have wiped dalvic/cache also factory data reset,I am unable to do anything in anycut,the phone automatically goes through freeze process,any ideas on how to fix issue?
got the issue too. Only on tw based roms tho. why i only **** wit cm10/aokp. And anycut doesnt work completely with jb yet. You have to use the anycut widget instead
Thanks for the response I guess the only way to stop the problem is not to have a tw Rom,I guess I might just have to bit the bullet on that one,im not really into flashing roms I'm only rooted for hotspot and system settings to change certain things
Sent from my SPH-L710 using xda premium
Could always setup the dualboot to have stock and an aosp rom
Okay I might have to look into that, thanks for the quick responses I thought I was the only one, my friends have s3 to add well and was not experiencing issue,I can see now that's for top them not having stock Rom
Sent from my SPH-L710 using xda premium
You could also find out what process is causing the bad behavior, what's not playing nice, and remove or freeze that app. You could also try to do a fresh install of your rom.
I was getting the same issues, but I found out that Maps social pin-point (Latitude) was causing my issues and unchecked all of the options related to check-ins and location sharing. No problems since.
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Sent from my SPH-L710 using xda premium
brianhot1 said:
When you say fresh install do you mean hard reset?if that's what you are referring to I have done that and wipes in recovery. And how exactly did you find it was that specific app doing That to your phone?
Click to expand...
Click to collapse
For that specific problem, it was trial and error, but a logcat would help. At the time, I couldn't figure it out. I believe there's an app to help read logcats.
Okay thanks
Sent from my SPH-L710 using xda premium
I found one app that was freezing for me I cleared data and uninstall updates for play store, the issue still happens sometimes though
Sent from my SPH-L710 using xda premium
Download Fast Force Close it really helped with the extremely frustrating freezes.
https://play.google.com/store/apps/details?id=com.issess.fastforceclose
Sent from my SGS3!
Cool so how exactly would the app help me if you don't mind me asking I see that it produces the fc would that help in fixing the freezing issue? And if so then how
Sent from my SPH-L710 using xda premium
Any update? It still happens?
Sent from my SPH-L710 using xda premium
Did you use the app? It seems that the app triggers a force clse popup if (im guessing here) a certain amount of time has gone by (like the OS itself does, but maybe shorter) or whenever an app goes unresponsive (it comes up instantly)
So either way, its supposed to fix the force close dialog not showing up for you.
I have our installed but I guess im still working on how to use it, I'm going to try to run it in the background
Sent from my SPH-L710 using xda premium
Update!!!!! Thanks to http://forum.xda-developers.com/member.php?u=336619
Thanks for the tips guys. This was also irritating me to no end on several Samsung roms. I think it happens on the Note and S3 too. Maybe even the S2.
My solution was:
Using a terminal emulator or adb shell,
su
cd /data/log
chmod 444 dumpstate_*
This sets those files to read-only permissions and that seems to fix it.
Sent from my SPH-L710 using xda premium
Great tip. Had never heard of this before.
Sent from my SPH-L710 using xda app-developers app
K. I rooted last night using Bin4ry method. Immediately had problems with any app requesting permission. Repeatedly was asked by super user to allow. If I switched to auto allow it would decline instead. So I tried unroot. Reboot. Same issue persists. Any ideas how to fix this?
Sent from my C6506 using xda app-developers app
imprezif said:
K. I rooted last night using Bin4ry method. Immediately had problems with any app requesting permission. Repeatedly was asked by super user to allow. If I switched to auto allow it would decline instead. So I tried unroot. Reboot. Same issue persists. Any ideas how to fix this?
Sent from my C6506 using xda app-developers app
Click to expand...
Click to collapse
I had an issue where it wouldn't remember my permissions, kept asking every time.
Reinstalled Superuser and it was fixed.
Way to easy a fix. I tried everything but uninstalling and reinstall through Google market. That and a reboot. Seems to have done the trick.
Sent from my C6506 using xda app-developers app