• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Netarchy Smartass Kernal with Setcpu?

M

mijjah1974

Newbie
I'm using Netarchy's 4.2.1-bfs-bfq-havs-less-smartass w/MikFroYo v4.3. Seems to work really well. Battery life is great when screen is off drains somewhat fast at times when screen is on. Would setcpu help with this. I've read other posts that says not to use profiles with smartass, but haven't read anything stating not to use setcpu at all. Just wondering what I could do to increase battery life with screen on. Tried many kernels and this one seem quick and stable compared to most. Any advice would be greatly appreciated.
 
mijjah1974 said:
I'm using Netarchy's 4.2.1-bfs-bfq-havs-less-smartass w/MikFroYo v4.3. Seems to work really well. Battery life is great when screen is off drains somewhat fast at times when screen is on. Would setcpu help with this. I've read other posts that says not to use profiles with smartass, but haven't read anything stating not to use setcpu at all. Just wondering what I could do to increase battery life with screen on. Tried many kernels and this one seem quick and stable compared to most. Any advice would be greatly appreciated.
Click to expand...

Try Netarchy's 4.2.2 kernel. It set the "Conservative" governor as its' default instead of "Smartass".

People have been getting great battery life while idling BUT so/so when phone is in use. Having the governor set at "Conservative" is suppose to help combat this problem but doesn't idle as well. Setting a screen-off profile is supposed to help tremendously. Try this setup out and see how it works for you.
 
Welcome to the forums :). There are a couple things you can try. Have you tried the CFS version of that particular kernel? In my case, BFS drains the battery faster than CFS regardless of kernel choice. Beyond that, if you haven't changed the governor, it should be set to smartass, as that's the default for that kernel. You can install setcpu and have it detect the defaults. There is nothing wrong with using setcpu with the smartass governor, just don't use profiles.

The smartass governor is known to have good battery life while sleeping, but drain the battery a little faster with the screen on. You can try switching to the conservative governor, and set up a screen-off profile set to 245/245. That should get better battery life. Try it out, and see.

EDIT: French beat me to it :).
 
frenchy714 said:
Try Netarchy's 4.2.2 kernel. It set the "Conservative" governor as its' default instead of "Smartass".

People have been getting great battery life while idling BUT so/so when phone is in use. Having the governor set at "Conservative" is suppose to help combat this problem but doesn't idle as well. Setting a screen-off profile is supposed to help tremendously. Try this setup out and see how it works for you.
Click to expand...
I'll give these a try and see. I've tried a few other netarchy kernels and had some stability problems, but it might have been my setcpu setup. Thanks for the help.
 
akazabam said:
Welcome to the forums :). There are a couple things you can try. Have you tried the CFS version of that particular kernel? In my case, BFS drains the battery faster than CFS regardless of kernel choice. Beyond that, if you haven't changed the governor, it should be set to smartass, as that's the default for that kernel. You can install setcpu and have it detect the defaults. There is nothing wrong with using setcpu with the smartass governor, just don't use profiles.

The smartass governor is known to have good battery life while sleeping, but drain the battery a little faster with the screen on. You can try switching to the conservative governor, and set up a screen-off profile set to 245/245. That should get better battery life. Try it out, and see.

EDIT: French beat me to it :).
Click to expand...
Thanks for the warm welcome, I'll try first your setcpu advice before changing the kernel. If no luck I'll give the cfs a try, if still no luck I'll try 4.2.2 with Frenchy's advice. I appreciate the quick response fellas, you are quick. Hope to chat more with ya throughout the forum, kind of becoming and addict. Thanks.
 
mijjah1974 said:
Thanks for the warm welcome, I'll try first your setcpu advice before changing the kernel. If no luck I'll give the cfs a try, if still no luck I'll try 4.2.2 with Frenchy's advice. I appreciate the quick response fellas, you are quick. Hope to chat more with ya throughout the forum, kind of becoming and addict. Thanks.
Click to expand...
akazabam, I should of asked this in previous response. Being new to a lot of this, when you mentioned change the governer, did you mean thru setcpu? I assumed so, as I don't know of any other way to modify it. Thanks.
 
Yes, that's fine. There are other apps that can do it, but if you change it in one, it takes affect globally. For example, change the governor in setcpu, then install OS monitor. if you go to the misc tab in OS monitor, you will see that the selected governor reflects the changes made in setcpu.
 
OK, so I switched over to the cfs version of this same kernel. Setcpu is set to conservative, with a screenoff profile set as you mentioned, but I'm getting screen tears at the moment. Battery is remaining fairly stable with screen on. Should I have the set on boot flagged, also, should the default max and min be adjusted. Currently at 998 and 245. Whats the recommendation. Thanks again.
 
Which kernel did you switch to, specifically? If you're getting screen tearing, try netarchy 4.3.1. That should resolve most screen tearing and instability issues. If you flashed a more aggressive HAVS version, you can also try the less aggressive HAVS version like what you have before with BFS.

As for setcpu, go ahead and check "set on boot" so that your governor doesn't change (assuming you are still using 4.2.1). If you flashed 4.2.2 or up, conservative is the default, and you didn't change the max/min, so "set on boot" won't make a difference. You may as well check it, though. If you decide to overclock, you obviously need to check that option, BUT don't check it until you know your phone is stable. If you try to overclock with it checked, and your phone locks up, you could end up in a bootloop that isn't easy to get out of without a nandroid backup.
 
Trying the netarchy 4.3.2 now. I've tried a lot of netarchy and found each one to effect the phone differently. I'll leave setcpu as is, conservative, 998 and 245. not overclocking at the moment, really looking more to conserve battery with some speed and stability. I've found MikFroyo to be most stable and extremely quick, just need to find the perfect kernel.
 
akazabam said:
Which kernel did you switch to, specifically? If you're getting screen tearing, try netarchy 4.3.1. That should resolve most screen tearing and instability issues. If you flashed a more aggressive HAVS version, you can also try the less aggressive HAVS version like what you have before with BFS.

As for setcpu, go ahead and check "set on boot" so that your governor doesn't change (assuming you are still using 4.2.1). If you flashed 4.2.2 or up, conservative is the default, and you didn't change the max/min, so "set on boot" won't make a difference. You may as well check it, though. If you decide to overclock, you obviously need to check that option, BUT don't check it until you know your phone is stable. If you try to overclock with it checked, and your phone locks up, you could end up in a bootloop that isn't easy to get out of without a nandroid backup.
Click to expand...
So far 4.3.1 has rid me of the screen tears, doesn't seem quite as responsive. Does a slight overclock to increase speed generally affect the battery life pretty drastically or does it just very?
 
Is all else the same? By that, I mean governor choice, screen-off profile, CFS, etc. If so, you might benefit from overclocking a little. I do, and the battery doesn't take too much of a hit. You can try it and see. It's not hard to change back. Like I said before, though, uncheck set at boot, first. You don't want to get stuck in a boot loop. Generally, 1152 MHz is stable for almost everyone. Some can go higher (it depends on the ROM, kernel, and the phone itself).
 
Pretty much the same, running 4.3.1-cfs-havs-nosbc. Setcpu is set to conservative. Set profile of screen off 245/245. Going to overclock 1152 to see how it handles. Thanks again.
 
Kind of got away from the thread topic. So on that note, would you recommend updating my ROM to Mik's 4.4, currently 4.3 is working so well, kind of hate to make any changes. Just curious. What ROM do you currently run or do you mix it up? Gonna get some zzz here shortly, really appreciate your help and advice. I've been following threads and experimenting a lot with ROMS (only sense), Kernels and MODS, just to see how things work.
 
I'm running Mikfroyo 4.3, as well. I haven't gotten around to flashing 4.4, yet. I haven't had an hour or two to sit down and do it properly. It's really not a huge update, but you should probably do it. If nothing else, make a nandroid backup, and if something goes wrong, just restore the nandroid.
 
akazabam said:
Welcome to the forums :). There are a couple things you can try. Have you tried the CFS version of that particular kernel? In my case, BFS drains the battery faster than CFS regardless of kernel choice. Beyond that, if you haven't changed the governor, it should be set to smartass, as that's the default for that kernel. You can install setcpu and have it detect the defaults. There is nothing wrong with using setcpu with the smartass governor, just don't use profiles.

The smartass governor is known to have good battery life while sleeping, but drain the battery a little faster with the screen on. You can try switching to the conservative governor, and set up a screen-off profile set to 245/245. That should get better battery life. Try it out, and see.

EDIT: French beat me to it :).
Click to expand...

:D
 
I see you're running MikFroYo 4.4. Is it much different than 4.3?? I'm running Netarchy 4.3, seems to work well with Mik 4.3. Just curious, don't know if an update to 4.4 will benefit me.
 
mijjah1974 said:
I see you're running MikFroYo 4.4. Is it much different than 4.3?? I'm running Netarchy 4.3, seems to work well with Mik 4.3. Just curious, don't know if an update to 4.4 will benefit me.
Click to expand...

I haven't read of any significant changes from 4.3-4.4, I flashed from 4.2. Check out the change log and see if it's worth flashing. I'm a firm believer of, "if it ain't broke, don't fix it". :D
 
Has anyone used this kernel to overclock? I am trying to make it overclock when I'm charging and battery is between 100-50%, whenever I set it to 1190MHz my EVO restarts. I'm using Myn's 2.2.
 
Droiddinho said:
Has anyone used this kernel to overclock? I am trying to make it overclock when I'm charging and battery is between 100-50%, whenever I set it to 1190MHz my EVO restarts. I'm using Myn's 2.2.
Click to expand...

You can definitely overclock with this kernel. The question is, what can your phone handle. Some phones can handle that high of an overclock, some can't. Try 1152; that's generally considered stable for most people.
 
Thanks! I managed to overclock at 1152, runs pretty good but now I'm getting alot of force closes and it wiped out all my text messages.
 
What else have you done to your phone? Just flashing a kernel/overclocking wouldn't cause you to lose your text messages. Also, force closes can be due to a lot of things. Did it not start until you overclocked? What are your hboot/radio/software versions? What kernel are you using, specifically (version, CFS/BFS, HAVS/noHAVS, SBC/noSBC)?
 
I've used it quite a bit, overlocked generally at 1152. The only problem I seemed to have was battery drain with the screen on. Great battery life with screen off. Stability was good, speed was good. Since I've switched to 4.3.1-cfs-havs-nosbc, with setcpu set conservative and screen off at 245/245, getting pretty good battery life. Only complaint is it seems sluggish at times. Smartass always seemed quick, the one thing I did like about it.
 
You must log in or register to reply here.
Back
Top Bottom