[KERNEL] [GPL] [GN] franco.Kernel r398
- Thread starter franciscofranco
- Start date
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1
About hot reboots: having them every now and then, every two days or something. Totally irrelevant when it happens: while listening music, or just when the phone is laying on the table with the screen on. Hopefully Google fixes this, not Franco related.
Sent from my Nexus 7 using Tapatalk HD
About hot reboots: having them every now and then, every two days or something. Totally irrelevant when it happens: while listening music, or just when the phone is laying on the table with the screen on. Hopefully Google fixes this, not Franco related.
Sent from my Nexus 7 using Tapatalk HD
I have never had a reboot or sod using Franco especially the latest one. Never while running Xylon ROM and now over a month on Baked BB7.
What about the max CPU freq for screen off?
Also just for completeness, what's the recommend TCP congestion avoidance algo? Is it westwood?
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1
It isn't a hard reboot though, when you check your uptime the phone doesn't see the reboot. Just the glowing X bootscreen.
SOD doesn't happen on Franco, luckily because my phone is sensitive for it
Sent from my Galaxy Nexus using Tapatalk 2
It isn't a hard reboot though, when you check your uptime the phone doesn't see the reboot. Just the glowing X bootscreen.
SOD doesn't happen on Franco, luckily because my phone is sensitive for it
Sent from my Galaxy Nexus using Tapatalk 2
AW: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1
The final winner tunables are running perfectly stable here on the GNex of my wife and on my own GNex.
No problems with 192/1228 :good:
I used a lot of gaming, listening to music, web browsing with Chrome, Tapatalk and Repligo Reader (PDFs). Performance and battery life are just amazing, no stability issues at all.
The final winner tunables are running perfectly stable here on the GNex of my wife and on my own GNex.
No problems with 192/1228 :good:
I used a lot of gaming, listening to music, web browsing with Chrome, Tapatalk and Repligo Reader (PDFs). Performance and battery life are just amazing, no stability issues at all.
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1
They are prefect except that I need to set read ahead buffer to 128 for listening to FLACs.:thumbup:
Sent from my Galaxy Nexus using xda app-developers app
The final winner tunables are running perfectly stable here on the GNex of my wife and on my own GNex.
No problems with 192/1228 :good:
I used a lot of gaming, listening to music, web browsing with Chrome, Tapatalk and Repligo Reader (PDFs). Performance and battery life are just amazing, no stability issues at all.
They are prefect except that I need to set read ahead buffer to 128 for listening to FLACs.:thumbup:
Sent from my Galaxy Nexus using xda app-developers app
Yes, 1024 is the safe used by most users (and kernel devs), 2048 if I recall, as you say is "the point".
Benchmarks are one thing, real usage is another one.
With 2048 i feel my phone being sluggish in transitions. The best way to test that is scrolling the widget section very fast. Its simple a no go for me.
After that i tested some other values, and for now i found that 256 gives me the best transition in the Widget Section.
With 2048 i feel my phone being sluggish in transitions. The best way to test that is scrolling the widget section very fast. Its simple a no go for me.
After that i tested some other values, and for now i found that 256 gives me the best transition in the Widget Section.
I didn't know exactly which comment to quote since there have been dozens on comments with different tunables but why the just from 30 to 15? I haven't seen anything in between like 20 and 25. We might as well get it perfect instead of just dividing the numbers in half each time for a test, I've seen every other number be tested in increments of "5" except this one.
AW: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1
That's true, it depends from personal usage. Until Read Ahead becomes configurable via f.KU I use an init.d script to set it to my taste
That's true, it depends from personal usage. Until Read Ahead becomes configurable via f.KU I use an init.d script to set it to my taste
I'm so glad I saw your post. I have been annoyed by the lag when scrolling vertically through the widgets on nova launcher for quite some time. 256 buffer cleared things right up! With no noticeable draw backs so far. Can someone who knows more than me explain the benefits of higher buffer sizes?
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -> 4.2 | r300 -> 4.1
Although 512 is a little smoother to me when opening Google now for example. Using that value now.
Sent from my Galaxy Nexus using Tapatalk 2
That's true, it depends from personal usage. Until Read Ahead becomes configurable via f.KU I use an init.d script to set it to my taste
Although 512 is a little smoother to me when opening Google now for example. Using that value now.
Sent from my Galaxy Nexus using Tapatalk 2
From yellowdie's post
So that's why we've set that value to 30 or multiple of that e.g 30/2 = 15; 30*(3/2) = 45 and so on
From yellowdie's post
So that's why we've set that value to 30 or multiple of that e.g 30/2 = 15; 30*(3/2) = 45 and so on
Got cha, thanks! So these tunables have been implemented in the latest fku, correct?
Has anyone played with the new IO scheduler options?
Those are governor tunables and always have been available to tune on fku under frequencies/voltages > Governor control
On the newest version released today franco included I/O scheduler tuning which is a completely different thing and those options are available under custom kernel settings > io scheduler tuning
And no, i haven't played with that yet. I'm at work atm and sh*ty mondays are sh*ty so not so much spare time to play around
I meant have the tunable values you guys been playing with for about a week been updated in the app? Are they the new default now?
To make them the default values they should be updated on the kernel img not in the app. You can always mod them to your personal preferences though
Just to double check, would this be the correct init.d script to set read_ahead to 512 on boot?
Code:
#!/system/bin/sh
echo 512 > /sys/block/mmcblk0/queue/read_ahead_kbAlso, I'm not quite sure I completely understand the naming schemes of init.d scripts. Is a name of "10sdboost" ok?
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! ]
New posts
-
-
Implementing landscape lock screen in LineageOS 20?
- Latest: punamkumarixharma
