Search This thread

myrdog

Senior Member
Dec 8, 2010
56
9
London
If sampling rate = min_timeinstate, you're not getting the benefit of preventing frequencies from quickly bouncing back and forth. [...] so I changed it so that after the calculations it comes out similar to that with a sampling rate of 10,000 with a min_timeinstate of 30,000. At least with my phone, this seems to have helped reduce the "bounce" effect.

This makes sense. If the sampling is the same as the mintime, you might as well not set a minimum time in the state. It's changing as soon as it samples no matter how long its been in the state.
 

Antob125

Senior Member
May 23, 2011
386
52
Franco I know Milestone are usually stock GPU but is there any way when milestone comes out you can make a 512 version. Loving the speed.

Sent from my Galaxy Nexus
 

bigeyes0x0

Senior Member
Jun 20, 2011
1,342
1,640
Saigon
So where're your other 231648 versions?

Jokes aside trying the latest hoping to see my Bluetooth bug fixed. Otherwise I hope it's fixed after M3 with kernel 3.0.28 included. I'm pretty sure that it's a bug in kernel now, as I do not have it in stock, ogdobber and faux's kernels.
 

drawde40599

Senior Member
Aug 11, 2010
5,322
1,967
charging

Can some1 please see if there phone still charges after install of 512build 141?? I was just charging phone on build 140 now not working 141? May have nothing to do with the kernel but if someone could check please
 

6jaipur6

Senior Member
Feb 1, 2010
805
238
Targu Jiu
After a day with r140 I can say that my artifacts problem is solved. No lags no high temperatures no other problems. Mentioned that hotplugins is of, lazy gov and the rest is default. Thanks Francisco for your great work. With no exaggeration you are brilliant.

Sent from my Galaxy Nexus using xda premium
 

StyxJ

Member
Aug 3, 2011
34
3
Connecticut
  • Like
Reactions: drawde40599

Metallice

Senior Member
Jun 24, 2010
3,275
5,173
Franco 141 with tweaks to Lazy.

Sampling Rate lowered to 10,000 (same as previously posted tweak). Min Time In State now calculates to 40,000 (Previous tweaked lazy i posted had it at 30,000). Lazy 10,000/40,000 source attached as well.

[Also includes lowered VAUX3/VUSIM voltages, Vibrator Control, and FSync Control, but that's only because this is also my personal build. Lowered voltages may cause graphical glitches.]

DO NOT DOWNLOAD THIS AND EXPECT ANY SUPPORT FROM ANYONE ANYWHERE EVER. This is only to test out the changes to lazy governor, and if people like it MAYBE Franco will decide to include them sometime in the future if he feels like it. Maybe he won't. Who knows? The man has the right to do whatever the f*** he wants with his kernel.

Now to go get drunk. College beckons.
 

Attachments

  • franco.Kernel-r141MOD_5.zip
    3.1 MB · Views: 37
  • cpufreq_lazy.c
    23.4 KB · Views: 6
Last edited:

dwang

Senior Member
Nov 23, 2008
2,453
318
Smoothest version yet. I can definitely feel the difference w the latest interactive governor patch in 141.

r141
* Disable Sync framework for now - it seems too experimental and it was slowing the kernel down. I also think it was causing few random reboots to some users which makes sense since in the patch description it says it can give a few kernel deadlocks. Everything should be ok now
* Merged another Interactive patch
* Merged a patch from TI that adds 3 local caches for DSSCOMP that improves reliability, autonomy and efficiency of the module
 

ragnarokx

Senior Member
Sep 1, 2010
2,335
512
Southwest
Does r141 include the patches for he lazy governor to manage the "bouncyness"? It seems to work very well

Sent from my Galaxy Nexus using XDA

Is fixing the "bouncyness" supposed to increase battery life? Because I've had outstanding battery life on franco's included Lazy governor, and it is so smooth I'd be afraid that changing any parameters to try for more battery life would increase UI stuttering.
 

nklenchik

Senior Member
Oct 24, 2010
923
236
33
Binghamton, NY
Franco 141 with tweaks to Lazy.

Sampling Rate lowered to 10,000 (same as previously posted tweak). Min Time In State now calculates to 40,000 (Previous tweaked lazy i posted had it at 30,000). Lazy 10,000/40,000 source attached as well.

[Also includes lowered VAUX3/VUSIM voltages, Vibrator Control, and FSync Control, but that's only because this is also my personal build. Lowered voltages may cause graphical glitches.]

DO NOT DOWNLOAD THIS AND EXPECT ANY SUPPORT FROM ANYONE ANYWHERE EVER. This is only to test out the changes to lazy governor, and if people like it MAYBE Franco will decide to include them sometime in the future if he feels like it. Maybe he won't. Who knows? The man has the right to do whatever the f*** he wants with his kernel.

Now to go get drunk. College beckons.

I'll try it out my dude
 

ssglackey

Senior Member
Feb 6, 2012
124
10
^^^ What he said. How the hell did you get 5 days out of this!? Do you touch your phone ever?

sure I did. Every time I needed the phone. But I didn't browse too much, at work I have a PC and at home ipad. I used it lightly, sms, whatsapp, 1 gmail sync. some photos made, also updated many apps on HSPA.
Most of energy was saved by 2G with data sync only once per hour, 3G olny when needed for browsing & app installing.

I have black themed AOKP b31 used no UV, interactive 384-1.3G, generic hotplug and tweaked auto brightness levels.
Not used wifi, it is disconnecting during sleep. And of course airplane mode during night.

Sent from my Galaxy Nexus using XDA
 

Attachments

  • uploadfromtaptalk1334987307210.jpg
    uploadfromtaptalk1334987307210.jpg
    46.1 KB · Views: 480
  • uploadfromtaptalk1334987335580.jpg
    uploadfromtaptalk1334987335580.jpg
    77.5 KB · Views: 482
  • Like
Reactions: motoman234

drewlim

Senior Member
Feb 26, 2012
127
21
Nice finally 512 running w/o any problems on r141. Was having problems with 512 versions ever since r121+. Thanks franco!

Sent from my Galaxy Nexus using Tapatalk 2
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1562
    I hate big OPs.

    Works on all roms. r390 and newer versions are ONLY for 4.3 or newer.

    F.A.Q:
    1. My device rebooted or crashed, how can I help?
    A: Get me /proc/last_kmsg on pastie.org.
    2. Battery sucks, my device is not entering deep sleep. FIX PLOX!
    A: Fix it yourself, it's an app waking your device up not the kernel's problem
    3. Signal is dropping since I flashed the kernel, amg u sucks!
    A: The kernel has nothing to do with gsm/cmda signal. Make sure you have the latest radios
    4. Do I need to wipe anything when flashing this kernel?
    A: No.
    5. Does this kernel has X or Y mod?
    A: Learn to read, everything you need to know is in the features list, changelog or public repo.

    Downloads:
    4.3: http://192.241.177.15/GalaxyNexus/4.3/
    4.4: http://192.241.177.15/GalaxyNexus/4.4/

    Kernel changelog:
    http://192.241.177.15/GalaxyNexus/4.3/appfiles/changelog.xml

    Source:
    https://github.com/franciscofranco/Tuna_JB_pre1/tree/nightlies-4.3

    franco.Kernel updater Free apk: http://xdaforums.com/showthread.php?t=1867127

    203
    [KERNEL][GPL][5 JUN - #Milestone 4][r200-ICS r210-JB] franco.Kernel | 4.0.3/4 |

    Terminal commands for all the options in this kernel:

    Color Multipliers:

    echo r g b > /sys/class/misc/colorcontrol/multiplier

    Replace r g and b for 2000000000 for stock color. If you want to change the colors just replace the first 3 numbers of each r/g/b with 0-400 of your choice.

    Gamma Control:

    echo r g b > /sys/class/misc/colorcontrol/v1_offset

    Replace r/g/b by -255/200 of your choice.

    Fsync:

    echo 1 > /sys/module/sync/parameters/fsync_enabled - to enable

    echo 0 > /sys/module/sync/parameters/fsync_enabled - to disable

    Sound Control:

    echo i > /sys/devices/virtual/misc/soundcontrol/volume_boost

    Replace i with 0-3 of your choice.

    Sound High Performance:

    echo 1 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to enable

    echo 0 > /sys/devices/virtual/misc/soundcontrol/highperf_enabled - to disable

    USB Fast Charge:

    echo 1 > /sys/kernel/fast_charge/force_fast_charge - to enable

    echo 0 > /sys/kernel/fast_charge/force_fast_charge - to disable

    wifi_pm:

    echo 1 > /sys/module/bcmdhd/parameters/wifi_pm - to enable

    echo 0 > /sys/module/bcmdhd/parameters/wifi_pm - to disable

    Trinity's Contrast:

    echo i > /sys/module/panel_s6e8aa0/parameters/contrast

    Replace i with -25/16 of your choice.

    BLX:

    echo i > /sys/class/misc/batterylifeextender/charging_limit

    Replace i with 0-100 of your choice.

    OMAP Gamma interface:

    echo i > /sys/devices/platform/omapdss/manager0/gamma

    Replace i with 5-10 of your choice.

    Thermal Throttle:

    echo 1 > /sys/module/omap_temp_sensor/parameters/throttle_enabled - to enable

    echo 0 > /sys/module/omap_temp_sensor/parameters/throttle_enabled - to disable

    TCP Congestion Algorithm interface

    To check all the available options:

    sysctl net.ipv4.tcp_available_congestion_control

    To change to other option:

    sysctl -w net.ipv4.tcp_congestion_control=NAME_OF_THE_ALGORITHM

    Detailed test of all the algorithms:
    Latency - Download - Upload

    cubic:
    1st run: 15ms - 10,75Mbps - 7,82Mbps
    2nd run: 14ms - 10,84Mbps - 8,06Mbps

    reno:
    1st run: 13ms - 15,51Mbps - 6,73Mbps
    2nd run: 13ms - 14,73Mbps - 8,51Mbps

    bic:
    1st run: 12ms - 10,38Mbps - 8,61Mbps
    2nd run: 13ms - 10,78Mbps - 8,62Mbps

    westwood:
    1st run: 11ms - 17,65Mbps - 8,30Mbps
    2nd run: 13ms - 13,28Mbps - 8,29Mbps

    highspeed:
    1st run: 13ms - 10,76Mbps - 7,94Mbps
    2nd run: 16ms - 14,42Mbps - 8,52Mbps

    hybla:
    1st run: 14ms - 11,19Mbps - 7,44Mbps
    2nd run: 14ms - 13,47Mbps - 7,56Mbps

    htcp:
    1st run: 14ms - 13,24Mbps - 7,03Mbps
    2nd run: 15ms - 10,85Mbps - 8,00Mbps

    vegas:
    1st run: 14ms - 8,49Mbps - 6,62Mbps
    2nd run: 14ms - 12,00Mbps - 7,07Mbps

    veno:
    1st run: 13ms - 9,58Mbps - 8,13Mbps
    2nd run: 13ms - 8,50Mbps - 7,64Mbps

    scalable:
    1st run: 18ms - 12,01Mbps - 8,73Mbps
    2nd run: 14ms - 13,96Mbps - 8,23Mbps

    lp:
    1st run: 14ms - 14,90Mbps - 8,68Mbps
    2nd run: 14ms - 13,44Mbps - 8,72Mbps

    yeah:
    1st run: 14ms - 13,37Mbps - 8,28Mbps
    2nd run: 17ms - 13,89Mbps - 8,14Mbps

    illinois:
    1st run: 13ms - 12,93Mbps - 8,24Mbps
    2nd run: 16ms - 13,97Mbps - 6,46Mbps
    167
    Just woken up and feel like my head is going to explode already this last 5 pages is crazy

    haha. It's been a crazy two days. :) But it's been a blast.

    Now, sleep is over, time to get back to work!

    I got these from that thread:

    so it makes much sense, to make the min_sample_time as low as possible (?), but how low? what's the most appropriate sample time for battery and performance?

    for the timer_rate, franco suggested 30k to consider the CPUs latency. What has it to do with the cpu's latency?

    he also said min_sample_time doesn't have to be in multiple of timer_rate.
    in my case, all my timers are in 20k, which works fine as of now. But i must be missing some things, because I just saw somebody post these values, and no detailed explanation for having them.

    Yes and no. Here's what we're thinkin' so far.

    THIS POST WILL BE A RECAP OF THE LAST FEW PAGES OF RESEARCH! :)

    This was my original settings that I've been using for weeks:
    above_hispeed_delay: 20000
    go_hispeed_load: 50
    min_sample_time: 40000
    timer_rate: 20000
    So to make the short hand easier, we kept it in that order and just said: 20000/50/40000/20000 became 20k/50/40k/20k became 2/5/4/2. Make sense?

    Here is a breakdown of what they each mean:
    -above_hispeed_delay: Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load.
    -go_hispeed_load: The CPU load at which to ramp to the intermediate "hi speed".
    -min_sample_time: The minimum amount of time to spend at a frequency before we can ramp down.
    -timer_rate: Sample rate for reevaluating cpu load when the system is not idle.

    This is a good explanation that I wrote back on page 3038:
    -above_hispeed_delay: higher = better battery, lower = better performance. (100k is default)
    -go_hispeed_load:.......higher = better battery, lower = better performance. (50 is default)
    -min_sample_time:......lower = better battery, higher = better performance. (60k is default)
    -timer_rate:.................higher = better battery, lower = better performance. (20k is default)
    So Google's default is 10/5/6/2. Lower numbers are all better for performance except min_sample_time (there higher is faster). So our goal is to find a sweet spot.

    The default 10 is for "Once speed is set to hispeed_freq, wait for this long before bumping speed higher in response to continued high load." So we think 10 is too high, but if you go too low, then you'll be using the higher freqs a lot more than you need and it will hurt the battery. So we are leaning towards 6 (60000) for above_hispeed_delay.

    The default 5 is for "when the CPU hits X% amount of load, then jump to the hispeed_freq." Again if this one is too low then it will cause the higher freqs to be used more often then they need, so we actually turn go_hispeed_load up a little bit to 7 (70).

    The default 6 is for "how long do I wait before lowering the clock speed from what it's currently at." So the lower we put this, the better battery will be. We're still trying to decide between 3 (30000) and 5 (50000). Osm0sis is getting more lag at lower levels, and finds the best performance mark at 5. So we turn min_sample_time down a little from stock to help with the battery.

    The default 2 is for "wait this long before changing the clockspeeds from what it's at now." While technically 2 sounds better because it's changing more often, Franco believes that by setting the timer_rate to be the same thing as the CPU sample_rate (which is preset at 30000), then that will make the CPU more efficient at switching. So we increased it from 2 (20000) to 3 (30000).

    So TO RECAP: Using the stuff from above, Google's defaults for these settings are 10/5/6/2 and we are changing them to 6/7/3/3 or 6/7/5/3 (again, still testing that third number for the min_sample_time).

    Does that make sense for everyone interested in following along? Any questions? Feel free to try out these settings yourself (the easiest way is with Franco's app or something like Trickster). We want as much feedback as possible on this.
    The next kernel release will have the totally tweaked settings for everyone to test without having to change their own stuff.

    :):D:laugh::good:
    111
    Kernel Emergency Settings Reset Zip

    Alright so here's something that's been requested for awhile.

    I wrote it up recently with Franco's stamp of approval, so I'm posting it here now. Please direct people back to this post from other threads.

    This can/should be everyone's go-to when experiencing problems after updating to a new kernel build, you get stuck in a bootloop, or you think there's a conflict between ROM and kernel (or kernel tweaking app) you can't track down, since likely some leftover settings (voltages, etc.) are at fault. It's also useful if you just want to make sure you're running clean defaults. This should work on any device franco.Kernel and f.Ku support, as well as a variety of other devices, kernels and control apps: eXperience (Free/Pro), GLaDOS Control, TricksterMod, Trinity Kernel Toolbox, ROM Toolbox (Lite/Pro), SetCPU, Faux123 Kernel Enhancement Project, Performance Control and Synapse.

    Flashing this via custom recovery of your choice will delete the kernel app settings file(s), disable init.d and userinit.d scripts by moving them to a subfolder (/system/etc/init.d/off/ and /data/local/userinit.d/off/ respectively) and wipe cache and dalvik-cache for good measure.

    Hopefully it helps!


    Note: If your ROM has a Performance/Tweaking App built-in you should also manually disable any Set On Boot options it has. For example, I couldn't include clearing CM's Advanced Settings since they're built into the main com.android.settings/Settings.apk along with a lot of other Android OS settings (APNs, Developer Options, etc.), so to run clean and without conflicts on CM you need to unset them yourself.

    You should also avoid having more than one control app installed at a time. Conflicts have been reported even with everything "unset" in two apps.

    I also chose not to disable anything your ROM may have in /data/cron or /system/addon.d since some rely on it heavily, so you can choose to review those directories' contents and whether you want to leave them enabled on your own. I also left out disabling sysctl.conf since that's done by f.K and the Franco's Dev Team scripts, and also seemed a bit heavy-handed for this zip script.



    Download counts for the previous versions: 790; 2678.
    105
    Sure. Happy to post my franco.Kernel settings here for anyone who wants to try them. I'll keep these up-to-date if I change them. :)

    These are my f.K settings, my DirtyV settings can be found here.
    Device: Galaxy Nexus
    Max Frequency: 1305 MHz
    Min Frequency: 384 MHz
    Governor: interactive
    Governor Tunables: a_h_d 15000 / g_h_l 95 / h_f 729600 Hz / m_s_t 45000 / t_r 15000 / i_b_f 1036800 Hz / t_l 85 / t_s 80000 / b_d 1000000
    IO Scheduler: row
    IO Scheduler Tunables: h_r_q 100 / r_r_q 75 / h_s_q 5 / r_s_q 4 / r_w_q 4 / l_r_q 3 / l_s_q 2 / r_i 15 / r_i_f 25
    Read Ahead Buffer: 512; NR Requests: 512
    TCP Congestion Avoidance Algorithm: westwood
    Screen Off Max Frequency: 537 MHz

    Color Multipliers: 230 235 340
    RGB Gamma: -4 0 5
    Trinity Contrast: -22; OMAP4 Gamma: 4; CAB: Disabled

    Sent from franco.Kernel updater app:
    https://play.google.com/store/apps/details?id=com.franco.kernel

    The following voltages are just as a reference. DO NOT enter them; your device may not be able to handle them this low, causing freezes and reboots. They are here so that people can compare their stable voltages after following the UV guides linked below, to see how our devices compare. Every device is different, so again, DO NOT enter them.
    mpu_voltages:
    1804mhz: 1425 mV
    1728mhz: 1375 mV
    1612mhz: 1325 mV
    1536mhz: 1275 mV
    1420mhz: 1225 mV
    1305mhz: 1175 mV
    1228mhz: 1125 mV
    1036mhz: 1075 mV
    729mhz: 925 mV
    537mhz: 825 mV
    384mhz: 775 mV
    192mhz: 725 mV

    iva_voltages:
    430mhz: 1125 mV
    332mhz: 1025 mV
    266mhz: 925 mV
    133mhz: 825 mV

    core_voltages:
    512mhz: 1050 mV
    384mhz: 975 mV
    153mhz: 800 mV
    There are some battery savings from UVing but they aren't extreme. If you do not know how UVing works and/or you can't/won't read to properly build your own voltage profile, then just stick with the defaults Franco has already UVed. If you do still want to learn to UV then, once again, everyone should build their own voltage profile for their own device. Read this, this, this, and this for starters on UV methods. You don't know how your device will do until you learn and try.

    As a sidenote, if anyone else wants to share their voltages for comparison the easiest way is to copy the contents of the 3 voltage files (mpu/iva/core) in /sys/class/misc/customvoltage/ - they look (almost) exactly as the sections above.
    Fsync on just in case anything ever happens I want my data protected. That said I do disable it temporarily if I ever want a bit more performance in an app or game. SR is hardcoded disabled in the latest builds.

    The other thing worth noting is I set my color settings on boot with an init.d script. Doing it that way you can end up with a completely different result from the same values. The contrast, blacks and colors are much more natural. Also it's seamless which is nice; they take effect during the Google logo. Attached is my init.d script for that. Alter it to your own color settings, remove the .txt extension, push to /system/etc/init.d/ and set the correct perms; rwxr-xr-x (chmod -R 755 /system/etc/init.d in Terminal Emulator).

    900colorsettings can be found with my other init.d scripts (from Franco Dev Team), here: https://s.basketbuild.com/filedl/devs?dev=osm0sis&dl=osm0sis/scripts/900colorsettings

    Note: On my new replacement screen, setting the color multiplier too early in the boot (any time before the boot animation) made everything look dark, oversaturated, uncontrasted and dusky; basically the opposite of the way it used to work on my old panel. Adding sleep 2; before that line in the init.d script fixed this, so experiment if your panel is more like my new one, and the init.d as-is after you put in your settings makes it look worse.

    [ New init.d script with my new colors. I need the sleep 4 because of my problem in my "Note" above, so comment it out if you don't need it, it will make it look worse. Previous download counts were 1880, 646, and 307. Thanks everyone! ]