[KERNEL] [GPL] [GN] franco.Kernel r398
- Thread starter franciscofranco
- Start date
I love it too!)
r141 (512) + AOKP b33
autobrightness
1344
729
no UV
Lazy governor
Generic Hotplug off
SR on
hi
what about deep sleep does r141 works well, i just got 4% drop with r135 in 24hrs
No. I can say by 95% of certain that r142 is Milestone 3. Just a few more days to let it flow and see what happens.
It's 384.
Hey man, what are you personally using lately? I've tried lazy in the past few builds but my idle times aren't that great.
In any case, thanks for your work with Liquid
Dunno really, I vary between interactive and lazy.
i keep going back to 135 because it gives me the lowest cpu temps, and my instinct is that this is good for longevity and performance.
the calibrated gpu voltage behavior is interesting thought. on all of the kernels r130 and newer, when i first flash them, the gpu voltage is over 1000, but then after about a day drops to 800's. that's fine and all, i don't mind waiting for a kernel to settle, but the problem is that as soon as I reboot the phone, it's back to 1000, and stays there for a day again before dropping. i reboot quite a bit, and would like to understand why this is happening, and why it can't just use lower voltage from the get go.
the calibrated gpu voltage behavior is interesting thought. on all of the kernels r130 and newer, when i first flash them, the gpu voltage is over 1000, but then after about a day drops to 800's. that's fine and all, i don't mind waiting for a kernel to settle, but the problem is that as soon as I reboot the phone, it's back to 1000, and stays there for a day again before dropping. i reboot quite a bit, and would like to understand why this is happening, and why it can't just use lower voltage from the get go.
+1.. Maybe my phone's problem but i really keep getting high temp reading on latest
nightly 141 as well... On idle, i check my temp shoot to 57 degree.. After on call for 1 min, my temp shoot to 60 degree... How accurate is this temp reading actually? Is there any apps in the store to monitor processor temp as well?
So can the.gpu voltage effect the cpu temp? Im on the 512 version but never see artifacts or anything. and yeah meant my max freq is 1ghz
Sent from my Galaxy Nexus using Tapatalk 2
Yeah that happens to me too. The 24 hours after a reboot even without flashing a new kernel my corr voltages are ~1000 and after a day they drop to ~860. I wonder whether its running at a higher speed initially or if something weird is going on with smart reflex.
Sent from my Galaxy Nexus using xda premium
Just letting you know, USB host seems to not be working. I am able to use a USB stick with stickmount no problems, but using a usb mouse or ps3 controller won't work. Just flashed AOKP b33, and tried it out with faux kernel before re-flashing yours, and it was working. Just wondering if you can look into seeing why it's disabled in your kernel.
Unable to download any zip files from the op. But able to download files from other threads. Am I missing something other than brains?
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
Hey man, what are you personally using lately? I've tried lazy in the past few builds but my idle times aren't that great.
In any case, thanks for your work with Liquid
Well, yeah, if you're referring to time spent in deep sleep, of course an interactive based governor will give you better results. Since an interactive governor will scale to the highest frequency quickly, the system will be able to reach deep idle a lot quicker.
So it really depends on your usage patterns. Are you the kind of user who will turn the screen on, check the time, and turn it off? Are you pulling it out of your pocket, reading a text or email, firing off a response, and then back in the pocket it goes? Well than interactive will give you the best battery life. However, if your the kind of person who will take their phone out, play a game, read the news, browse the web, check out reddit, and then turn it off, Lazy will do best for you.
Basically when you do go on your phone, how long do you spend on it? Minutes at a time? - Lazy. A minute, maybe two? - Interactive.
Franco I finally figured out what has been giving me so much lag lately, it's smart reflex. The second i turn it off my phone turns to butter, what's up with that? If it's unfixable, any chance of having smart reflex off, on screen on, ever implemented?
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2
I finally got to playing with r141 today and I have to say, this is by far the best overall kernel for the Galaxy Nexus hands down...no lag, great battery life AND benchmarks...wow. The updater app is awesome too...I'm currently using this with Bugless Pete...awesome combination!
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Had to go into xda site through browser to download. Unable to download through tapatalk. Whierd
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
Maybe his fingers is capable of moving and using the phone in matters of nanoseconds
Screen on time 2 minutes?
Haha you guys are funny!
Okay because I was out camping for 3 days 2 nights and I forgotten to turn off my phone before that. So when I got back to camp, I realised my phone was dead. =D So just saying, it could last 2 days without usage. Haha =DHaha you guys are funny!
Actually, your phone should be able to last much longer if you ain't using it. You must have plenty of background apps running.
Sent from Galaxy Nexus using Tapatalk 2
Just flashed latest liquid rom to try r142.I love the lazy governor.
For the battery drain r141 is good for me.20hrs with 3hrs screen on time,30％ left.
If r142 is the milestone,I will say OH YES！LOL.
Sent from my Galaxy Nexus using Tapatalk 2
For the battery drain r141 is good for me.20hrs with 3hrs screen on time,30％ left.
If r142 is the milestone,I will say OH YES！LOL.
Sent from my Galaxy Nexus using Tapatalk 2
The only reason I cannot drop SetCPU app are this two options.
Is there any possibility to include that in your app? My music is skipping sometimes with hotplug option enabled. With this governor options I am getting much better battery life. I am charging my phone every second day with moderate usage.
Also can you please include check box option to apply CPU, IVA and CORE undervolt voltages on boot? Finally I found out the lowest voltages I can use but I need to apply them every time after reboot.
BTW r141 is just amazing. Very fast and no more crashing. Excelent work Franco
Is there any possibility to include that in your app? My music is skipping sometimes with hotplug option enabled. With this governor options I am getting much better battery life. I am charging my phone every second day with moderate usage.
Also can you please include check box option to apply CPU, IVA and CORE undervolt voltages on boot? Finally I found out the lowest voltages I can use but I need to apply them every time after reboot.
BTW r141 is just amazing. Very fast and no more crashing. Excelent work Franco
142
OK I can finally say goodbye to 121, 142 is ridiculous!! battery 4.6 hours I've never hit that with stock battery before, AND!! its faster then hell!! Interactive gov, rest settings stock . I wanna see u top this build ; ). THANKS FRANCO!!!!
OK I can finally say goodbye to 121, 142 is ridiculous!! battery 4.6 hours I've never hit that with stock battery before, AND!! its faster then hell!! Interactive gov, rest settings stock . I wanna see u top this build ; ). THANKS FRANCO!!!!
The only reason I cannot drop SetCPU app are this two options.
Is there any possibility to include that in your app? My music is skipping sometimes with hotplug option enabled. With this governor options I am getting much better battery life. I am charging my phone every second day with moderate usage.
Also can you please include check box option to apply CPU, IVA and CORE undervolt voltages on boot? Finally I found out the lowest voltages I can use but I need to apply them every time after reboot.
BTW r141 is just amazing. Very fast and no more crashing. Excelent work Franco
I hope those aren't your real frequencies. You may as well give it a wheel chair and a hearing aid
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! ]
