[KERNEL] [GPL] [GN] franco.Kernel r398
- Thread starter franciscofranco
- Start date
Where can I download the latest nightly? The download page only goes to 85...I purchased the updater app and that also lists 85 as the latest nightly...I downloaded 121 a while back but now I don't see the current version which I believe is 140.
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/
Sent from my Galaxy Nexus using xda premium
weird.. i just had 2 random reboots with r140 Lazy governor
but i wasnt able to get a log coz i did not know it rebooted.
just saying
but i wasnt able to get a log coz i did not know it rebooted.
just saying
colors
@Franco would asking for an option to disable color control in ur app be an option? I would like to use the roms color control but your kernel disables them .....
@Franco would asking for an option to disable color control in ur app be an option? I would like to use the roms color control but your kernel disables them .....
Seriously I'm really happy with this build -)
UI is smooth and quick. There are no screen lags and doesn't matter what launcher (Nova or Apex) I'm using. There is no issue with cpu temp - max temp that I had today was 48°C. I have no problem with kernel wakelocks and on my mind the battery life is in the best traditions of franco.kernel. Especially I like a minimal battery drain when screen is off as it's very important for me.
Franco, thanks again for great work!!!
The simplest way using Franco's app if you have installed it. Calibrated Voltage tab > MPU Voltage
Send an email to CyanogenMod and ask them to fix their ****. I'm not responsible for roms to use their implementation over Ezekeels.
Hmmmm, i thought was a simple question? Guess not, its not just cm9, breaks most roms . Well whoever's "code " it belongs to, sorry for asking damn . Have a great day; )
On Lazy, max frequency should be on when the screen is off to get in idle faster correct?
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Yes because most roms are using CM9 java implementation on their Color Control. I don't support CM9 mods.
Oui.
r140 lazy working rly nice. I'm surprised about my battery drain! Nice work Franco, thanks!
Tapatalk
Tapatalk
Franco, I made some changes to the Lazy governor that I believe are better for our phones. I attached my cpufreq-lazy.c to this post if you're interested. Of course, you're free to do whatever you want 
.
I changed the sampling rate to 10,000 to match that of the other governors in your kernel. I also modified how "min_timeinstate" is calculated so that it isn't coming out equal to the sampling rate anymore. If sampling rate = min_timeinstate, you're not getting the benefit of preventing frequencies from quickly bouncing back and forth. In Ezekeel's original thread on lazy he had a sampling rate at 10,000 and min_timeinstate to 40,000, 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.
.I changed the sampling rate to 10,000 to match that of the other governors in your kernel. I also modified how "min_timeinstate" is calculated so that it isn't coming out equal to the sampling rate anymore. If sampling rate = min_timeinstate, you're not getting the benefit of preventing frequencies from quickly bouncing back and forth. In Ezekeel's original thread on lazy he had a sampling rate at 10,000 and min_timeinstate to 40,000, 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.
Franco, I made some changes to the Lazy governor that I believe are better for our phones. I attached my cpufreq-lazy.c to this post if you're interested. Of course, you're free to do whatever you want
I changed the sampling rate to 10,000 to match that of the other governors in your kernel. I also modified how "min_timeinstate" is calculated so that it isn't coming out equal to the sampling rate anymore. If sampling rate = min_timeinstate, you're not getting the benefit of preventing frequencies from quickly bouncing back and forth. In Ezekeel's original thread on lazy he had a sampling rate at 10,000 and min_timeinstate to 40,000, 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.
Any chance you can post a built kernel? I don't have any way to compile.
Sent from my Galaxy Nexus using XDA
Don't know, I began to lower the values till I reached the limit, in the IVA case there were *cracks* at the loudspeakers, in the CORE case reboots and freezes.
The top CORE values are for 384mhz not 512, this last one will need for sure between 50-100mAv more..
Nightly 140 has a little bug I think, the values you set don't apply (only the CPU one's).
Francisco, a couple questions:
1. Have you been following the FIOPS scheduler development? If so, do you think you'll be looking at it's performance for inclusion in your kernel?
2. Have you explored the use of the C4 state in your governor tweaks? Ezekeel makes use of it in his Wheatley governor and I think it's an interesting concept.
1. Have you been following the FIOPS scheduler development? If so, do you think you'll be looking at it's performance for inclusion in your kernel?
2. Have you explored the use of the C4 state in your governor tweaks? Ezekeel makes use of it in his Wheatley governor and I think it's an interesting concept.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1562I 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:
167
haha. It's been a crazy two days. But it's been a blast.
Now, sleep is over, time to get back to work!
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:
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:
This is a good explanation that I wrote back on page 3038:
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.
:laugh::good:111Kernel 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.105Sure. 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.
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! ]
