Database Info

SetCPU for Android

I'm sure almost all (if not all) of you that have obtained root on your Incredible (which this app requires) know what this app is and possibly have even used it in the past. There doesn't appear to be any Incredible specific modifications made to the app yet, but I just wanted to throw this out there. As always, be VERY careful with overclocking, esp. with this CPU (I personally wouldn't try anything over 1.2ghz). If you feel your phone getting hot, don't keep running it! Also neither the author, XDA or I take any responsibility in the case that you toast your Incredible.
http://www.pokedev.com/setcpu/

I thought we'd need a modded kernel to run it over 1.2 Ghz? How can we do that with just rooting the phone and installing setcpu?
Or I'm way off and I have no idea what I'm thinking lol..

andrew53517 said:
I thought we'd need a modded kernel to run it over 1.2 Ghz? How can we do that with just rooting the phone and installing setcpu?
Or I'm way off and I have no idea what I'm thinking lol..
Click to expand...
Click to collapse
no, you are correct. i have built the kernel (HTC release) w/ the required changes. but have not been able to flash

Wow I wasn't aware of the kernel limits, or maybe I subconsciously read it somewhere since I threw 1.2ghz out there (over the last couple weeks I've been dealing with a cold I can't seem to shake so I blame a combination of insomnia+Nyquil... mmm Nyquil).

Id say its worth some green to get that kernel. I have been looking high and low to find one. seems that the demand is there but not the development. Let me know if you get it up and running and I'll donate to the cause.
Just wish I could develop it at this point, but getting the phone rooted was a task for me. Even with video instructions....

Getting setCPU to stick after reboot

Hello,
I am running stock ROM with S-oFF and rooted. Ive got setCPU running via the methods used for temp root. (Basically pulled the code from the BAT files everyone used to overclock and temp root). It works alright, but after a reboot, I have to redo it.
I see people are running ROMs that include setCPU. How does a custom ROM manage to keep setCPU "set" after a reboot? Can the methods be used for the stock ROMers?
Also, I see that setCPU requests SU hundreds of times a day when I look at the SuperUser logs. Why is this? Is it bad?
Thanks,
Matt

They are using custom kernels and oc daemon.

Behold_this said:
They are using custom kernels and oc daemon.
Click to expand...
Click to collapse
thank you for the reply! Is this something that a stock rom could implement in its own? Or, should I consider flashing a custom rom?
Thanks,
Matt

Its a little hit and miss right now unfortunately. The kernels can still be buggy on some devices, though they, in theory, should work on a stock device. If you have issues you can always just flash the stock kernel back. Some love it and have no issues, others not so much. In fact some devs have stopped bundling their kernels with their roms and leave them as optional add ons because of issues.

Is cm7 expected do implement overclocking? If so, I may just wait for them to finish.
Matt

Not sure...they are playing cm7 for the sensation very close to the chest, lol, but I don't think so. Just a guess though.

Behold_this said:
Not sure...they are playing cm7 for the sensation very close to the chest, lol, but I don't think so. Just a guess though.
Click to expand...
Click to collapse
Ahh...I guess that only time will tell what sort of advancements come in the way of overclocking (reliably and efficiently).
My theory is that setCPU is the cause for my headaches and may be the cause of most others using it as well. (Crappy battery despite conservative governors as well as phone freezes and data connectivity issues). Seeing setCPU request SU a few thousand times a day seems suspicious. I have it frozen for now, well see how things go.
Matt

I don't know for sure either, but I suspect you might be right, at least to an extent.

Xoom Overclock Question.......

Just a curious question..cause im thinking about getting one of these soon. I like em.
But..these ship with Android 3.0 or 3.2 already on them. NOW...example..the G Tablet...people ROOT those because of the bad stock ROM it came with. And the Non Android market that it shipped with. Then lead to many other things to be added to the GTab like the SetCPU for overclocking.
My question would be....since the Xoom already has Android 3.2 and all...no need to really ROOT it for me. BUT..is there a way to overclock it with any app...WITHOUT having to ROOT the Xoom??? Most of those overclock apps you need to be ROOTED. Just wondering if there is a such app to overclock the Xoom without ROOT.
Thanks for any reply.

DJR0D said:
Just a curious question..cause im thinking about getting one of these soon. I like em.
But..these ship with Android 3.0 or 3.2 already on them. NOW...example..the G Tablet...people ROOT those because of the bad stock ROM it came with. And the Non Android market that it shipped with. Then lead to many other things to be added to the GTab like the SetCPU for overclocking.
My question would be....since the Xoom already has Android 3.2 and all...no need to really ROOT it for me. BUT..is there a way to overclock it with any app...WITHOUT having to ROOT the Xoom??? Most of those overclock apps you need to be ROOTED. Just wondering if there is a such app to overclock the Xoom without ROOT.
Thanks for any reply.
Click to expand...
Click to collapse
No, you need to root and install a kernel or rom that supports overclocking. But the Xoom, while perfectly fine on stock, absolutely shines when rooted and running custom rom/kernel.

okantomi said:
No, you need to root and install a kernel or rom that supports overclocking. But the Xoom, while perfectly fine on stock, absolutely shines when rooted and running custom rom/kernel.
Click to expand...
Click to collapse
I knew that was coming. So Xoom you would say is still VERY good straight out the box??? Speed wise. loading...startup and stuff like that.
What could be added with the ROOT that it doesnt already have??? Besides a overclocking app like SetCPU. How else could it benefit from a ROOT that it cant now?

DJR0D said:
I knew that was coming. So Xoom you would say is still VERY good straight out the box??? Speed wise. loading...startup and stuff like that.
What could be added with the ROOT that it doesnt already have??? Besides a overclocking app like SetCPU. How else could it benefit from a ROOT that it cant now?
Click to expand...
Click to collapse
Ok, for me, I hate not have root control over the device, and when unrooted/unmodded, it feels less snappy. Plus rooting adds functionality (sdcard r/w and usb host mode in addition to overclocked cpu/gpu) so I can't see leaving it stock/inrooted.

okantomi said:
Ok, for me, I hate not have root control over the device, and when unrooted/unmodded, it feels less snappy. Plus rooting adds functionality (sdcard r/w and usb host mode in addition to overclocked cpu/gpu) so I can't see leaving it stock/inrooted.
Click to expand...
Click to collapse
THAT i understand. Like example..the G tablet. That HAD to be ROOTED. It was a very powerful Tablet. Tegra 2 Dual Core..it had the power. But the software on it sucked. No Official Android market or Google stuff on it. So to me...that HAD to be ROOTED to bring it up with all the other big Tablets.
But the Xoom...it had the Official Market...it has Tegra 2 Dual Core also. The things that the GTab didnt have...Xoom has out the box. Thats why i wanted to know besides overclocking...what else would it need. The things they ROOTED the GTab for....the Xoom has already. Cept the overclock. So for me...as long as its not too slow (Which it cant be that slow)....i should be good with it. Just want it overclocked maybe a lil if i felt it was needed. Know what i mean?

DJR0D said:
THAT i understand. Like example..the G tablet. That HAD to be ROOTED. It was a very powerful Tablet. Tegra 2 Dual Core..it had the power. But the software on it sucked. No Official Android market or Google stuff on it. So to me...that HAD to be ROOTED to bring it up with all the other big Tablets.
But the Xoom...it had the Official Market...it has Tegra 2 Dual Core also. The things that the GTab didnt have...Xoom has out the box. Thats why i wanted to know besides overclocking...what else would it need. The things they ROOTED the GTab for....the Xoom has already. Cept the overclock. So for me...as long as its not too slow (Which it cant be that slow)....i should be good with it. Just want it overclocked maybe a lil if i felt it was needed. Know what i mean?
Click to expand...
Click to collapse
I used to think the same thing until I installed morray 2.2.2 all this time on a stock rom and I was just getting used to how much it sucked. I would suggest giving morray a try and I can say you won't be disappointed.
Sent from my Xoom using Tapatalk

the app "root booster" - is it an over clocking app?

I downloaded the app a few days ago after watching a "best apps" video on YouTube... But I've been nervous to really try it as I've heard over clocking can fry your phone... So I'm just wondering if anyone knows how it works exactly? Do i need to be nervous to use it?

Yes it modifies your processor speed, but you need not be nervous.
Its pretty stable.

I ended up deleting it actually. tried it but didnt notce much difference, in speed or battery, with it changed. so i just switched it back to stock then deleted it.
Only bummer was that rebooting from that app, the phone shuts off SO MUCH FASTER.... i wish i had an app to do that part alone lol

Pawprints1986 said:
I downloaded the app a few days ago after watching a "best apps" video on YouTube... But I've been nervous to really try it as I've heard over clocking can fry your phone... So I'm just wondering if anyone knows how it works exactly? Do i need to be nervous to use it?
Click to expand...
Click to collapse
it does not overclock it ...only you can do that form kerenl auditor or something like that app...adn you need a kernel that support an overclocking ...but i had that app and it really helped

Overclocking requires a custom kernel that allows it. Usually, overclocking is pointless anyway.
As for quick reboots, you can find stand-alone apps/widgets that give you reboot options.

Dirty Cow Exploit - Root

If you haven't heard of Dirty Cow you should look it up.
There thread is dedicated to rooting the GS7 / GS7E with Dirty Cow
Additional Goals:
Root without Tripp Knox
Working Verizon Hotpsot App
Unlock Bootloader
Receive future Android Updates
Fix all Bug fixes

Anyone can confirm???? New s7 edge and ready to blaze gigs!!!!

Don't listen to this fool. Look at his name.

I don't trust this guy either but this is an actual thing with code written for Android devices already. Any developer who complies it into an apk will have the next kingroot on their hands. Except for truly all Android devices

This will not work for our devices. Even if you do manage to gain root, you won't be able to do much. Any changes to the /system partition will be overwritten on reboot. Dm-verity won't allow those changes.
The current root method is going to be the only option until we are able to unlock the bootloader. That may never happen.
TLDR; Use the current engineering kernel.
Sent from my SM-G935U using Tapatalk

Dameon87 said:
This will not work for our devices. Even if you do manage to gain root, you won't be able to do much. Any changes to the /system partition will be overwritten on reboot. Dm-verity won't allow those changes.
The current root method is going to be the only option until we are able to unlock the bootloader. That may never happen.
TLDR; Use the current engineering kernel.
Click to expand...
Click to collapse
Honestly, I feel like a tethered root would be better than what we have currently. The engineering kernel is pretty terrible after about a week of use. It lags terribly even when maxed out and set to performance in the kernel settings. Maybe someone will at least look into an alternative root.

jal3223 said:
Honestly, I feel like a tethered root would be better than what we have currently. The engineering kernel is pretty terrible after about a week of use. It lags terribly even when maxed out and set to performance in the kernel settings. Maybe someone will at least look into an alternative root.
Click to expand...
Click to collapse
I'm not really sure you understand the implications in such a method. We have dm-verity checks that check the checksum of data on the /system partition. If even one bit is changed, the hash becomes invalid and various things can happen. The Note4 had such a method before, and while it was something... It had tons of issues with reboots, and losing root at random. It became so frustrating that it was honestly not worth the time invested. These problems with exacerbated by changes to the /system partition. So things like xposed and the like were highly hit or miss.
With the amount of issues likely to be caused, the engineering kernel is the best bet until a bootloader unlock is achieved. (if it ever is.) Truthfully a 'tethered' half functional root would be a waste of time. We have the engineering kernel, and while it is far from perfect... It works. And with the right tweaks and time, it can be stable as a daily driver.

Dameon87 said:
With the amount of issues likely to be caused, the engineering kernel is the best bet until a bootloader unlock is achieved. (if it ever is.) Truthfully a 'tethered' half functional root would be a waste of time. We have the engineering kernel, and while it is far from perfect... It works. And with the right tweaks and time, it can be stable as a daily driver.
Click to expand...
Click to collapse
You argue how the engineering kernel is better, and that a tethered root would be a waste of time. But the same could be argued both ways. A tethered boot has the aforementioned problems, and the engineering kernel have the obvious problems of horrible battery life, stability, etc.
So at the end of the day, they're both shotty, half baked, and far less than ideal ways to get root. But who's to say one crappy method is crappier than another crappy method. I'll take what I can get, and due to the fact my S7 Edge hasn't been rooted for months due to how sh*t the engineering kernel is, I wouldn't mind a another root method, reguardless.

FoxyDrew said:
You argue how the engineering kernel is better, and that a tethered root would be a waste of time. But the same could be argued both ways. A tethered boot has the aforementioned problems, and the engineering kernel have the obvious problems of horrible battery life, stability, etc.
So at the end of the day, they're both shotty, half baked, and far less than ideal ways to get root. But who's to say one crappy method is crappier than another crappy method. I'll take what I can get, and due to the fact my S7 Edge hasn't been rooted for months due to how sh*t the engineering kernel is, I wouldn't mind a another root method, reguardless.
Click to expand...
Click to collapse
So you logic is to trade a stable-enough solution for a lesser one that has more implications, will noticeably impact performance. (Because of various methods that have to be used to keep root active.) I'm not sure I follow that at all. And anyone who has actually dealt with a Samsung 'tethered root' will tell you the same thing. The dm-verity check makes things hell. That check is -not- enabled with the Engineering kernel. There were issues with root being lost if you even remove a file from the /system partition (Which by the way, respawns on reboot, so no changes will ever stick. Every change you make... Installing xposed, etc etc.... is wiped -every- time you reboot. There is no saving states.)
In any regard, I've done my homework.. I've messed with the solutions before, and I have developer insight into the former. It's not a feasible solution when we have an engineering kernel. It may not be optimal, but with time and effort it works just fine. And battery life, as well as other things can nearly be mimicked to a T with that kernel over stock.

Dameon87 said:
So you logic is to trade a stable-enough solution for a lesser one that has more implications, will noticeably impact performance. (Because of various methods that have to be used to keep root active.) I'm not sure I follow that at all. And anyone who has actually dealt with a Samsung 'tethered root' will tell you the same thing. The dm-verity check makes things hell. That check is -not- enabled with the Engineering kernel. There were issues with root being lost if you even remove a file from the /system partition (Which by the way, respawns on reboot, so no changes will ever stick. Every change you make... Installing xposed, etc etc.... is wiped -every- time you reboot. There is no saving states.)
In any regard, I've done my homework.. I've messed with the solutions before, and I have developer insight into the former. It's not a feasible solution when we have an engineering kernel. It may not be optimal, but with time and effort it works just fine. And battery life, as well as other things can nearly be mimicked to a T with that kernel over stock.
Click to expand...
Click to collapse
Do you have any advice on making the engineering kernel more optimized?

The v15 fixes here, greenify, amplify, l speed, and gov tuner help a lot! Personally, not the same as stock life, but close... that's the trade off
Sent from my SM-G930U using XDA-Developers mobile app

The first week of rooted u firmware is rough after that with only kernel adiutor my battery life if that of stock unrooted u firmware with only 15 fixes. Only rom I've used that I would say is capable of this is the playstore pi3.

Cant we use dirty cow and change the /system of a combination firmware as dm-verity check is disabled by default, then some how engineer a way to flash the bootloader that would accept a modded twrp recovery or similar..?