[KERNEL] [GPL] [GN] franco.Kernel r398
- Thread starter franciscofranco
- Start date
Deadline
Trying out Deadline Scheduler tweaks via script
read_expire: 351
write_expire: 3500
writes_starved: 6
front_merges: 1
fifo_batch: 1
Thanks for the suggestions. Are they purely for performance?
Trying out Deadline Scheduler tweaks via script
read_expire: 351
write_expire: 3500
writes_starved: 6
front_merges: 1
fifo_batch: 1
Thanks for the suggestions. Are they purely for performance?
Last edited:
@malaroth, I have been running your ROW tweaks for a full 24 hour now, initial impression is pretty good, there's noticeable improvement, although deadline is still a tad bit smoother, it doesn't struggle as much when writing apps to /data for example, I can still smoothly type on the keyboard (It still stutters though) while Play Store is updating a bunch of apps, as well as installing large games. Of course that's just some very basic testing without enough sample for a proper result, I'll try it for a few more days and see how it goes.
Last edited:
Re: [KERNEL][GPL][GN] franco.Kernel r365 -> 4.2.2 | r364 -> 4.2 | r300 -> 4.1
So, I added some of the deadline tweaks into my Spectrum kernel and along with some tweaks to ondemand and it seems to be noticeably smoother.
Sent from my gnex running CarbonRom and Franco kernel
So, I added some of the deadline tweaks into my Spectrum kernel and along with some tweaks to ondemand and it seems to be noticeably smoother.
Sent from my gnex running CarbonRom and Franco kernel
Re: [KERNEL][GPL][GN] franco.Kernel r365 -> 4.2.2 | r364 -> 4.2 | r300 -> 4.1
Sorry Franco cut out my tongue and chopped off my fingers so I couldn't divulg info, typing with my nose. I don't know what is being implemented in any version so *shrugs* glad they're working good for y'all. I still like deadline better
Franco r365
JBSourcery 4.5.5
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
I'm not done with row yet... just gotta figure what's needed to work out the kinks. And you cfq fans....might be awhile it's being a pain in the osm0sis
Franco r365
JBSourcery 4.5.5
Sorry Franco cut out my tongue and chopped off my fingers so I couldn't divulg info, typing with my nose. I don't know what is being implemented in any version so *shrugs* glad they're working good for y'all. I still like deadline better
Franco r365
JBSourcery 4.5.5
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
I'm not done with row yet... just gotta figure what's needed to work out the kinks. And you cfq fans....might be awhile it's being a pain in the osm0sis
Franco r365
JBSourcery 4.5.5
I have a problem with the Franco Kernel. Time ago before applying an OTA I restored the original kernel and then I applied the update. But with Android 4.2.x even if I restore the original kernel saved before installing the Franco I always get an error when I apply the OTA? Any suggestions?
Thanks!
Thanks!
I have the vbus_tuna_otg wakelock for most of my device on time, i had usb port problem, and ghost charging issue and some time later that fixed itself, but i had this problem going on.. any way to let os ignore this wakelock and let phone go to sleep
- Hardik
osm0sis
Senior Recognized Developer / Contributor
You need to read the error. Likely has nothing to do with the kernel if you properly reflashed stock.
this strange problem happened to me the same way
the issue was solved for me by putting the "sleep 35" command to the second line of the script after #!/system/bin/sh
Give it a try, your script should look like this:
I have spoken with another user and he told me about the "power.tuna.so" problem! I didn't know anything about this problem.
I think that the FK Updater should have a button to fix this!
I have spoken with another user and he told me about the "power.tuna.so" problem! I didn't know anything about this problem.
I think that the FK Updater should have a button to fix this!
This might help
miracast
Is miracast enabled in r365? I am running it and can't find an option to enable wireless displays, I was hoping to test with the new f/w on the Netgear PTV3000 box.
Is miracast enabled in r365? I am running it and can't find an option to enable wireless displays, I was hoping to test with the new f/w on the Netgear PTV3000 box.
I tried your script, but still no success. I think I'm giving up and waiting for Minco v6 with new franco kernel which should have those values as default
My first attempt was a file created on PC, then I tried writing it with OfficeSuite directly on the phone, but I had no better luck.
I tried your script, but still no success. I think I'm giving up and waiting for Minco v6 with new franco kernel which should have those values as default
My first attempt was a file created on PC, then I tried writing it with OfficeSuite directly on the phone, but I had no better luck.
You need to use a simple text editor instead of something that puts formatting in. Something like notepad++ in windows would work.
Miracast/Wireless Display is not enabled through the kernel. It's enabled through the ROM. The ROM I use that has it enabled is Shiny (only posted about it in this thread as malaroth was looking for a stock ROM).
As of now, it still hasn't worked with the GNEX. The GNEX is missing the libstagefright_hdcp.so file. Even with the file ported from the N4; using the PTV3000 won't work as PTV3000 REQUIRES HDCP. It seems to not connect right so it'll probably be best if the PTV3000 doesn't require HDCP. The N4 works with PTV300 because it has the a H264 decoder which I assume disables HDCP.
I've read that ALLSHARE works because it does NOT REQUIRE HDCP but I haven't tested it myself or known anyone personally that has tested it. I also heard CM made some changes to their build that works.
I have a buddy I work with that is currently testing all this on his GNEX/PTV3000 and provides me with updates.
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! ]
