[Team Kernelizers][How To][SPR][TK MOD 1.0.4]KT747 Kernel Tweaks-Updated 5-14-13

stas333 · Jun 15, 2013

BTT8 said:
That, and the added bulk .

True, that thing is HUGE
Its not a battery, its a weapon.

TheDriller · Jun 15, 2013

stas333 said:
True, that thing is HUGE
Its not a battery, its a weapon.

A damn powerful one too

---------- Post added at 02:45 AM ---------- Previous post was at 02:44 AM ----------

prboy1969 said:
These screen shots are on RErick's latest setup. Pretty good for a first full run . Thanks RErick . Yes I know Android OS is way too high. I think I've figured out what was causing it :fingers-crossed: .

TEAM MiK
MikROMs Since 3/13/11

You're going back to butterlicious after a run like that on mine? Lol sorry iamikon I gotta promote this one lol. If you can get os and system usages under control you could see like 5 days and 16 hours or more of screen time!

ArcAngel66 · Jun 15, 2013

castle_bravo said:
Are you on tk build prop? If so restore stock build prop, issue should be resolved.

So what I did was delete all info for the KTweaker and reinstalled this and then was messing around with different tweaks and this is when the WiFi issued started. From your post, I forgot to actually flash the TK-Mod-Beta-1.0.4-Rev1.zip file and once I did this, it seems to be working like before.

I did add the tk build prop from within the tk mod (like I did before) as I have never had an issues before when using this, but I will check this out more as I have not been around WiFi much yesterday...

ryandubbz · Jun 15, 2013

I've noticed the Wi-Fi not working issue is very hit or miss. I was getting the issues then I put tkmod back to stock. I ran it again last night and haven't had any issues since. I don't think the build props or tweaks like restarts

ArcAngel66 · Jun 15, 2013

prboy1969 said:
I had really good results on the original butterlicious. May go back to it now that I've tweaked a few more things.

TEAM MiK
MikROMs Since 3/13/11

If you go back, can you post those settings?

---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------

rhodiggah said:
I went straight to butterliciousV2 without trying the first version and liking it. All I changed was the min/max (81/1.7) I believe that was your suggestion... Smoothalicious, I call it hehe.

Sent from my rooted TPR_TW Rom!

I am assuming the min/max is from within the General settings?

From my phone, my min lowest is 81, but my max is 1512, so just checking as I do not see 1.7 for max...

ryandubbz · Jun 15, 2013

ArcAngel66 said:
If you go back, can you post those settings?

---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------

I am assuming the min/max is from within the General settings?

From my phone, my min lowest is 81, but my max is 1512, so just checking as I do not see 1.7 for max...

You have to check the enable over clock box so you can see the over clocked frequencies

prboy1969 · Jun 15, 2013

RErick said:
You're going back to butterlicious after a run like that on mine? Lol sorry iamikon I gotta promote this one lol. If you can get os and system usages under control you could see like 5 days and 16 hours or more of screen time!

Yes it was an excellent run, in spite of the high AOS. Again THANK YOU for the awesome setup

. I'm going to try iamikon's butterlicious rev2 . Going to see if I can figure out exactly what the deal is with users reporting reboots. Have to do what I can to help

TEAM MiK
MikROMs Since 3/13/11

---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------

ArcAngel66 said:
If you go back, can you post those settings?

Yes I will

TEAM MiK
MikROMs Since 3/13/11

Ragnar · Jun 15, 2013

prboy1969 said:
Yes it was an excellent run, in spite of the high AOS. Again THANK YOU for the awesome setup . I'm going to try iamikon's butterlicious rev2 . Going to see if I can figure out exactly what the deal is with users reporting reboots. Have to do what I can to help
TEAM MiK
MikROMs Since 3/13/11

Funny thing I have run both setups, never had a single issue with reboots. I stick to my original statement has to be user interface issue

Sent from the future via Tapatalk 4

prboy1969 · Jun 15, 2013

LuigiBull23 said:
Nope. I'm also on stock battery and will continue to stick with those. I will never purchase an extended battery Why? simply because I personally prefer ro monitor my device's battery life in real-time.

I to would still be on the Stock Battery. But an extremly generous TK member (Uhmm RErick

) decided otherwise. Must say the battery is nothing short of awesome.

BTT8 said:
That, and the added bulk .

It's honestly not much thicker than an SGS3, with an OtterBox Case.

TEAM MiK
MikROMs Since 3/13/11

mw86 · Jun 15, 2013

ryandubbz said:
I've noticed the Wi-Fi not working issue is very hit or miss. I was getting the issues then I put tkmod back to stock. I ran it again last night and haven't had any issues since. I don't think the build props or tweaks like restarts

I agree i wish i could get it figured out as I never once in the months we been working on it had the issue ever.

hard to diagnose i wish i had experienced it to try to help remedy it.

LuigiBull23 · Jun 15, 2013

BTT8 said:
That, and the added bulk .

The bulk honestly isn't a big deal to me.. Maybe on the Note 2 but besides that It doesn't bother me. Nonetheless, they are pretty beast and are extremely useful for travelers and such.

iamikon · Jun 15, 2013

I never had WiFi issues either. I'm on a stock battery hence the underclock in every setup lol. I like my otter box too much but I might get a normal sized lemon. RErick hahaha go for it. I always self promote just for fun

the reboot issues on butterlicious are driving me nuts. So for anyone having them please change all voltages to the stock value. Let me know.

Sent from my SPH-L710 using Tapatalk 4 Beta

mw86 · Jun 15, 2013

I don't know your setup but if your looking for stability for many use no more than 50-25mv down as more than half may be weak cpu. Preferably the 25mv at most. 850mv min but better yet no lower than 875mv. Many users have had far lower stable but if you want a setup for mass amount of phones and setups don't include much of a undervolt. Even when i had a big undervolt seemingly stable no crashes etc i witnessed random radio issues which left as soon as i went closer to stock volt. The users who posted about not using much of any undervolt are right. Effects the whole phone entirely. Prboy maybe was one??!? I hope it gets resolved Iamikon.

iamikon · Jun 15, 2013

That's where I'm confused. Rev2 had a much more universal voltage table min 875 at most was -25

Sent from my SPH-L710 using Tapatalk 4 Beta

stas333 · Jun 15, 2013

iamikon said:
I never had WiFi issues either. I'm on a stock battery hence the underclock in every setup lol. I like my otter box too much but I might get a normal sized lemon. RErick hahaha go for it. I always self promote just for fun the reboot issues on butterlicious are driving me nuts. So for anyone having them please change all voltages to the stock value. Let me know.

Sent from my SPH-L710 using Tapatalk 4 Beta

iamikon said:
That's where I'm confused. Rev2 had a much more universal voltage table min 875 at most was -25

Sent from my SPH-L710 using Tapatalk 4 Beta

thats weird. when i had mine installed, the min voltage was 850

whats the min voltage on REricks universal setup? mine is 855 after the install.

LuigiBull23 · Jun 15, 2013

iamikon said:
That's where I'm confused. Rev2 had a much more universal voltage table min 875 at most was -25

Sent from my SPH-L710 using Tapatalk 4 Beta

I wonder if undervolting only specific steps maybe with different values rather than the same values across the board will provide more stability for those users? That would take a lot of experimenting to get it just right though.

Ragnar · Jun 15, 2013

stas333 said:
thats weird. when i had mine installed, the min voltage was 850

whats the min voltage on REricks universal setup? mine is 855 after the install.

That's correct REricks min is set at 855, I've had my phone as low as 825 without a single issue but saw no significant change in battery consumption or savings.

Sent from the future via Tapatalk 4

iamikon · Jun 15, 2013

The min was 875 the two at 850 are not being used 135 and 81

Sent from my SPH-L710 using Tapatalk 4 Beta

GTOJim · Jun 15, 2013

mw86 said:
I don't know your setup but if your looking for stability for many use no more than 50-25mv down as more than half may be weak cpu. Preferably the 25mv at most. 850mv min but better yet no lower than 875mv. Many users have had far lower stable but if you want a setup for mass amount of phones and setups don't include much of a undervolt. Even when i had a big undervolt seemingly stable no crashes etc i witnessed random radio issues which left as soon as i went closer to stock volt. The users who posted about not using much of any undervolt are right. Effects the whole phone entirely. Prboy maybe was one??!? I hope it gets resolved Iamikon.

I also agree with MW as I've had my phone stable at lower voltages but encountered other issues that raising voltage close to stock voltage resolved.

On my last device one kernel developer did not believe there was any battery savings by undervolting so his kernels didn't include undervolting options.

Reminder if your having problems go back to stock mhz if overclocked or if undervolted go back to using stock voltages to see if this eliminates the problem your having. Once the device is stable and you want to overclock or undervolt take your time and go in steps. Make one change and leave it that way for several days, possibly a week, to make sure things are stable before making any more changes. I suggest leaving things for a week as I have experienced first hand that it can take that long for something to show up. In this case I backed off a bit and things were rock solid which is what I think most of us wish to accomplish.

mw86 · Jun 15, 2013

GTOJim said:
I also agree with MW as I've had my phone stable at lower voltages but encountered other issues that raising voltage close to stock voltage resolved.

On my last device one kernel developer did not believe there was any battery savings by undervolting so his kernels didn't include options for undervolting.

Just to repeat what has already been stated before, if your having problems go back to stock mhz if overclocked or if undervolted go back to using stock voltages to see if this eliminates the problem your having. Once the device is stable and you want to overclock or undervolt take your time and go in steps. Make one change and leave it that way for several days, possibly a week, to make sure things are stable before making any more changes. I suggest leaving things for a week as I have experienced first hand that it can take that long for something to show up. In this case I backed off a bit and things were rock solid which is what I think most of us wish to accomplish.

Well said Jim thank you for your contribution

glad to see you continue to be one of those who participate i discussion. Im on gs4 exynos and its almost same observation. Some ways undervolt has caused me nothing but issues even if ever so hard to notice. Seems like the best idea of undervolt is just to cool down some high mhz if stock mv keeps that frequency to hot, the limit being when it starts to destabilize.

Cpus have worked same forever. I take a quote from my stweaks app with a voltage note. Personally statement holds true for all hardware.
"Decreasing voltage will lower the power consumption of the cpu. Increasing it on overclocked frequencies improves stability. Too low voltages may cause instabilities and freezes."

-When undervolting you are deviating from what has already been proven to be free of instabilities and freezes. If you push too far there is no other result than those issues. Some instabilities really effect data rates as a mobile data radio can push a cpu harder in a download in a split millisecond vs even some benches. Sometimes you'd not know and just see data signal loss or download should be working and just keeps getting 0kbs...

-When overclocking or undervolting there is usually two types of typical instabilities. One way the device freezes (screen displays last activity) (*holding power button for 4 seconds forces power off or battery removal) , screen goes black not from user inactivity, stays this way when should be on and toggling screen on fails) (*holding power button for 4 seconds forces power off or battery removal) and the luckier crash and reboot as atleast phone is returned to running state immediately.

The less typical type of instability is sometimes experienced before the point one find true stability in everything. Apps could crash to home screen or glitch in user interface functions, messages or data sent through radios may fail since cpu is sending erroneous data either read or written where accuracy is key which is in almost all cases. These cpus and hardware luckily has error correction so the occasional data that is nit accurate is fixed while calculations continue. If you push below stable thresholds this will start being used and may feel stable but in all cases when it really is happening regularly will slow down cpu far more than in some cases cutting mhz in HALF. The idea is never have need of error correction and have it to protect you not hold you from falling because you happen to be right at the cliffs edge. If you want cpu to run optimally its like a race car and straight lines. Holes in the road are errors and error correction is the work crew ahead of you fixing those things ahead of you to continue on. You must wait for them while they fix, slowing you from where you'd be without these holes in th road. So for a faster trip for the cpu keep stability the first and foremost concern even over battery life, because STABILTY effects BATTERY LIFE just as much or more than a governor being more or less efficient at controlling mhz.

Btw guys its been tested from what ive seen that on a workload matched to the capabilities of say 378mhz set to 1200mv and same one on 1512mhz set to 1200mv and the workload is on going the later takes much more power than the 378mhz at 1200mv and shockingly very close to the same power taken on 378mhz @1200mv vs 378mhz @ 900mv on the Arm chips.
*as a rule of thumb higher mhz regardless of voltage set will take more power than a lower mhz on same workload.

The only way that doesn't hold true is more related to a workload itself, being if a low mhz takes so much time to complete a big workload vs a high mhz it can eventually take more power at the lower mhz just because that mhz is just inefficient for high workloads hence why we raise and lower mhz based on percent cpu load otherwise inefficiency would be met immediately when a given mhz is overloaded. This is why a governor thats smart is key. You want to linger on low mhz if you can anytime ypu can it will always save you the most power and when things get too much you definitely want more speed to get the job done even if the mhz is going to start to take more power.

-a cpu core will always take more power when it nears 80-100% load then if it just was dealing with a 20-50% load regardless of mhz pertaining to this aspect. Again a good reason a smart governor is important to match mhz to workloads.

Inherently from the above statements you can combine the infos. A cpu at high 100% load will take more power but if that mhz is getting the job done fast enough it would save more power than raising mhz since that would always require more power, but if its too slow at such a load an increase of mhz would be warranted and best only as little increase as possible to be mindful of power. That governor holding you at low mhz under a heavier load playing music as example will save most as long as it dont stress the cores too much vs a governor playing music jumping often to peaks in high mhz. Time is also key, better jump up to target mhz get job done and return as fast as possible to the target cpu load at low mid mhz. As long as sample rate allows cpu load to see a change from the changed mhz which governor chose than as fast a sample rate as possible is welcomed. Once it starts to jump up from just small jumps in load it has already been set too low to be accurate to workloads anymore.

I jumped all around on subject and info and the following was just experience and observation with no concrete data to base it on other than the few facts such as Arm chips at varied mv on the same mhz will draw close to the same power vs same mhz voltage differed. This only holds true to a certain point as to some extent a voltage far too high will increase uneeded energy and inherently increases heat produced. Ironically increases in heat raise voltage requirements for a given mhz

as well as increases in battery temperature yield lower battery life. Those not using a throttle control setup in kernel may want to consider to start using such controls to keep temperatures down.

[Team Kernelizers][How To][SPR][TK MOD 1.0.4]KT747 Kernel Tweaks-Updated 5-14-13

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Retired Forum Moderator

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Retired Forum Moderator

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts