I tried using setCPU to enable profiles for screen off and the like. It works, but there are some issues.
When actually using the phone, I get constant notifications the setCPU has been given root privileges. Like it is constantly needing to re-ask super user for root permissions.
Anyone else seen this behavior?
Marine6680 said:
I tried using setCPU to enable profiles for screen off and the like. It works, but there are some issues.
When actually using the phone, I get constant notifications the setCPU has been given root privileges. Like it is constantly needing to re-ask super user for root permissions.
Anyone else seen this behavior?
Click to expand...
Click to collapse
Normal.
If it bothers you turn off notifications in Superuser
NilsP said:
Normal.
If it bothers you turn off notifications in Superuser
Click to expand...
Click to collapse
Normal for temp root? I have never had this issue before, I have always rooted my phones straight away. I see the notification pop up at least 2-3 times a minute.
Yes temp root. Perm root is fine because it gets it once and holds it.
I noticed a lot of awake time when I have it running, so I uninstalled until perm root.
Related
I was able to temp root my Archos 101 by using z4root ver 1.3 at several days ago and also able to set the CPU back to 1Ghz. However, my wife helped me to switch off the tablet accidentally (because she said she just helped me to save more power for the tablet and so I could only say nothing to her then. ) and the temp root has gone.
Afterwards, I tried to re-root my tablet using different methods such as clean up and uninstall z4root and superuser, turn on/off airplane mode / unknown resources / usb debugging, etc. but unfortunately no success anymore.
I can obviously notice the difference of performance between setting CPU to 800mhz and 1Ghz and I miss 1Ghz so much.
Can anyone suggest any workable methods to me? I will no doubt attempt all of them until I get back my 1Ghz...
have you tried turning debug switch off and on again?
yup, turn on/off several times but still got no success.
maybe debug off, restart, debug on, z4root?
You may have to wipe the device back to stock to get it to work again
amdchip said:
You may have to wipe the device back to stock to get it to work again
Click to expand...
Click to collapse
Keep reboot and try again few times, i also got this problem. Take about 5-10 reboot then you can root again, but it eventually went out and need to keep reboot.
This worked for me. After a reboot, I go straight to apps> development> turn OFF usb debugging. Then I run z4root (it will ask you to turn usb debugging ON). Go ahead and turn it on. Run z4root again. It should root. Now run SetCPU and you should be good. Worked for me-- maybe it's a glitch of sorts.
I knew something was doing it, but just found out one offender is the video app.
IF you set up a setcpu widget with a refresh interval of 10s or so and setcpu to 1000, run a video, check, its set at 800, the slider still shows 1000, but you have to slide it back and forth to get the max back to 1000.
Archos mentioned some apps take advantage of the processor, they must've hardcoded the cpu speed for some apps including video app.
On my 70 I kill all apps including system before attempting root.
Sent from my HTC Desire using Tapatalk
675 Trip said:
I knew something was doing it, but just found out one offender is the video app.
IF you set up a setcpu widget with a refresh interval of 10s or so and setcpu to 1000, run a video, check, its set at 800, the slider still shows 1000, but you have to slide it back and forth to get the max back to 1000.
Archos mentioned some apps take advantage of the processor, they must've hardcoded the cpu speed for some apps including video app.
Click to expand...
Click to collapse
I've also noticed this as well, but I didn't know what was causing it. I thought maybe I had to keep SetCPU in the background to keep it from doing it.
I had this same problem and the only way to get it to root again was to wipe the device and start over.
The only thing I did that might have broken it was load Titanium Backup and installed the BusyBox from that. Every since after that I wasn't able to root without wiping. I'm too afraid to try again Titanium.
Have titanium installed and root is working.
It may sound strange, but if you have moved apps to sd-card (e.g. apps2sd): move them all back to internal storage. Reboot, and rooting should work again... also be sure you enough free RAM. Worked for me. (Found at archosforums)
have you use HOT REBOOT ??
this apk stay the root !
superschotje said:
It may sound strange, but if you have moved apps to sd-card (e.g. apps2sd): move them all back to internal storage. Reboot, and rooting should work again... also be sure you enough free RAM. Worked for me. (Found at archosforums)
Click to expand...
Click to collapse
Same to me I try 3 different app2sd apk`s but everytime the app is on the archos, without switching apps to the sd-card, temp rooting won`t work.
So I deleted the app2sd from my archos reboot one time and everything is fine.
Hope we get shortly permanent Root !
THANK YOU!! This did it for me. Moved all my apps back to phone and now z4root is working perfect. Thank you again!
superschotje said:
It may sound strange, but if you have moved apps to sd-card (e.g. apps2sd): move them all back to internal storage. Reboot, and rooting should work again... also be sure you enough free RAM. Worked for me. (Found at archosforums)
Click to expand...
Click to collapse
I had to uninstall superuser and rerun z4root to successfully use su again. Annoying but it worked for me.
I'm running xtrSense4.6.5 and Cricket v10 script. My 3g stops working occasionally, a reboot usually clears this up. Last week it stopped working and wouldn't come back. I got the idea to purge my SU permissions. All my Root programs asked for permissions except Autostart, ran the script and 3g is back.
I searched and there is no answer on google. Can anyone shine a light on this?
FinalBoss said:
I'm running xtrSense4.6.5 and Cricket v10 script. My 3g stops working occasionally, a reboot usually clears this up. Last week it stopped working and wouldn't come back. I got the idea to purge my SU permissions. All my Root programs asked for permissions except Autostart, ran the script and 3g is back.
I searched and there is no answer on google. Can anyone shine a light on this?
Click to expand...
Click to collapse
Just a an educated guess based on what you already said. I know that sometimes there's permissions issues that fixing these eliminates problems that people have. FYI I don't know if it's just the paid version, but Titanium Backup has an option to fix permissions in it.
I can turn my phone off after sleeping a while, and I have full bars on wifi signal, but no internet access...have to turn wifi off, then turn it back on to be connected again
Anyone having a similar issue or find a fix?
This is really really really annoying, and it's not the router, happens any time I'm on wifi
did you happen to temp root your phone ?
i had the same problem . I had temp rooted my phone then fully rooted it and then i stated having that problem.
What i did was go into WiFi setting and forget/remove your network. Reboot pull battey just because , start it up reconnect to WiFi and it hasn't happened since.
Edit : if that happens to work let me know .
Geeble said:
did you happen to temp root your phone ?
Click to expand...
Click to collapse
I did way back when
but I've since S=OFF and did a full/proper root by flashing it through recovery
why do you ask?
Geeble said:
did you happen to temp root your phone ?
i had the same problem . I had temp rooted my phone then fully rooted it and then i stated having that problem.
What i did was go into WiFi setting and forget/remove your network. Reboot pull battey just because , start it up reconnect to WiFi and it hasn't happened since.
Edit : if that happens to work let me know .
Click to expand...
Click to collapse
didn't work
did it 3 times
that is unfortunate.
that is a very annoying problem.
only other thing i can think of is after you forget your network turn wifi off then reboot.
Those are the only thing i did and it worked for me .
have you tried going into WiFi setting then menu then advanced?
maybe change its sleep policy around.
as of now when my phone sleeps the WiFi icon will shut off . when i turn it on give a few seconds and it reconnects.
before when my phone would sleep, i turn it on WiFi would still be on but it wouldn't load any pages until i turned it off and on again.
http://forums.androidcentral.com/htc-evo-3d/103506-wifi-problems-after-30-60-min-online.html
hydrogenman said:
I can turn my phone off after sleeping a while, and I have full bars on wifi signal, but no internet access...have to turn wifi off, then turn it back on to be connected again
Anyone having a similar issue or find a fix?
This is really really really annoying, and it's not the router, happens any time I'm on wifi
Click to expand...
Click to collapse
That was a problem with the Temp. Root. If you went right from Temp. Root to full with out flashing, I recommend you flash right now, before you get too much customization done on your phone. Flash everything off of it and remove the root and turn S-ON. Then flash once more and re s-off and root. That's how I had to fix it on my sisters phone.
if all else fails and you dont want to re root you could try wifi fixer in the market
just flashed a new kernel (silverneedle)
going to see if that alleviates the issue
hydrogenman said:
just flashed a new kernel (silverneedle)
going to see if that alleviates the issue
Click to expand...
Click to collapse
Please let us know, I am having this problem and I didn't have temp root at all. It is annoying
Drachen808 said:
Please let us know, I am having this problem and I didn't have temp root at all. It is annoying
Click to expand...
Click to collapse
new kernel did not solve the problem unfortunately
Drachen808 said:
Please let us know, I am having this problem and I didn't have temp root at all. It is annoying
Click to expand...
Click to collapse
did you have the problem before you rooted at all?
I'm thinking back and am not certain I had the issue before I went S-OFF and rooted perm
StrumerJohn said:
That was a problem with the Temp. Root. If you went right from Temp. Root to full with out flashing, I recommend you flash right now, before you get too much customization done on your phone. Flash everything off of it and remove the root and turn S-ON. Then flash once more and re s-off and root. That's how I had to fix it on my sisters phone.
Click to expand...
Click to collapse
ok, I missed this somehow the first time around
guess I'll give it a try
I'm currently running a rooted Sprint stock 2.3.4 and from time to time i have notice that the screen would not timeout or go to sleep. I can push the power button and put it to sleep but it wont do it on its own. I did check and screen timeout change to "never". Has anyone else ran across this issue and/or maybe have a solution?
nunyabiziz said:
I'm currently running a rooted Sprint stock 2.3.4 and from time to time i have notice that the screen would not timeout or go to sleep. I can push the power button and put it to sleep but it wont do it on its own. I did check and screen timeout change to "never". Has anyone else ran across this issue and/or maybe have a solution?
Click to expand...
Click to collapse
um, to clarify, you have it set to never and you're asking why the screen wont timeout?
The evo changed to never on its own.
Sent from my Xoom using XDA App
nunyabiziz said:
The evo changed to never on its own.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
um, cant you just simply change it from never to like 15min or another interval?
Sorry that I was not totally cleared. My phone would randomly change from 1 minute timeout to never. So the issue is that if im not careful and check after im done using my phone, the screen would remain on and drain my battery.
nunyabiziz said:
Sorry that I was not totally cleared. My phone would randomly change from 1 minute timeout to never. So the issue is that if im not careful and check after im done using my phone, the screen would remain on and drain my battery.
Click to expand...
Click to collapse
Did you do a clean install of the ota? Because if you didn't then it could have caused that problem. I suggest you do a full wipe (after you backup) and then install the ota afterwards. See if the problem persists and if it doesnt then restore your apps.
Hope this helps
Sent from my rockin 3D
Thanks for the help. I had applied superwipe and installed rooted stock ota before posting. Of course still the same random issue. However I will use RUU and go back to stock then start all over from the beginning.
Sent from my Xoom using XDA App
So it appears to be working okay on my rooted 6p but I saw that it's turned off in accessibility. Should I turn that on? Or will it work okay with it being off?
tu3218 said:
So it appears to be working okay on my rooted 6p but I saw that it's turned off in accessibility. Should I turn that on? Or will it work okay with it being off?
Click to expand...
Click to collapse
From my understanding, that option is for users who do not have root access. It enables Greenify to work somewhat without root access.
If I am incorrect, someone please chime in.
christianpeso said:
From my understanding, that option is for users who do not have root access. It enables Greenify to work somewhat without root access.
If I am incorrect, someone please chime in.
Click to expand...
Click to collapse
Slight correction.
That option is to be enabled only if you use Greenify in non root mode. You may have root but still choose to run Greenify in non root mode in which case that option is to be enabled.
tnsmani said:
Slight correction.
That option is to be enabled only if you use Greenify in non root mode. You may have root but still choose to run Greenify in non root mode in which case that option is to be enabled.
Click to expand...
Click to collapse
Wow! You are correct. I had it enabled on my rooted devices, thinking that it needed to be enabled for automated hibernation to work. In the accessibility settings window for greenify, there is no mention of only for non root mode.
I have disabled it now.
Thanks!
tnsmani said:
Slight correction.
That option is to be enabled only if you use Greenify in non root mode. You may have root but still choose to run Greenify in non root mode in which case that option is to be enabled.
Click to expand...
Click to collapse
Thank you for clarifying.:good: