Search This thread

osm0sis

Senior Recognized Developer / Recognized Contribut
Mar 14, 2012
14,484
32,552
263
Halifax
GT-i9250
Nexus 7 (2013)
Okay, let's try this again. :p

There was a little permissions issue that crept in last-minute. Updated things on GitHub to allow devs to avoid similar situations. :good:

Since I just finished my work on AnyKernel 2.0:
https://github.com/osm0sis/AnyKernel2 :D

Here's another fun thing for everyone to test out the format... ;)

franco.Kernel-r396-AnyKernel: http://v.ht/osmod

It's a test build from Franco adding the RAM OC commit from @Grarak:
http://forum.xda-developers.com/showpost.php?p=50152148&postcount=2531

You know the drill! :p

@metalspring I think it was just the RAM OC commit. So probably not much extra voodoo required on Franco's part. ;)

i'm sorry sir, i posted my request here, because i cant sent a PM to u (i tried 3x).

Sorry, I don't respond to technical questions via PM, as it states in my signature..

oh i'm sorry for that :rolleyes:
but still may i used for myself only? :eek:

Not on xda you can't, sorry, not if you need our help to get it running. I'm not going to help someone run a GPL violating (illegal) kernel. :eek:

Anyone who's still got the Final Fixed r394 osm0d kernel? I lost my copy and I need it to test something out. Thanks in advance.

r395 IS r394-fixed plus the module support and ASRAM that were missing by mistake in r394. :good:
 
Last edited:

osm0sis

Senior Recognized Developer / Recognized Contribut
Mar 14, 2012
14,484
32,552
263
Halifax
GT-i9250
Nexus 7 (2013)
Yeah I need the one with no RAM reclaim and try something out.

Ah.. Well r394 is available on Franco's server still, and if the one in the 4.4 directory doesn't work you can just combine it with the r395 ramdisk using my Android Image Kitchen tool.

http://v.ht/AIK-

Super easy. Sounds harder than it is, I promise. :)
 
  • Like
Reactions: Ci-Fi

my573r10us

Senior Member
Jul 16, 2010
85
7
38
Sorry, I don't respond to technical questions via PM, as it states in my signature..


Not on xda you can't, sorry, not if you need our help to get it running. I'm not going to help someone run a GPL violating (illegal) kernel.

oh ya im so sorry, i didnt see the states before :eek:
oke then, thanks for your reply :)

anyway, just a question, can you or add more ram (maybe till ~770mb free)? i think i dont need a 1080p recording, i need much ram bcause when im running BBM app, it take ~140mb ram *scrollingeyes*

thanks so much :D
 

osm0sis

Senior Recognized Developer / Recognized Contribut
Mar 14, 2012
14,484
32,552
263
Halifax
GT-i9250
Nexus 7 (2013)
Haha, Francisco doesn't want to add any more than the ASRAM 50mb, but you can check out other SuperRAM kernels like DirtyV. :)

If you do some research I think you'll find free RAM technically doesn't matter in Linux/Android like it does in Windows. Free RAM is wasted RAM, and management is more important. Android manages it pretty well, and never actually reaches out-of-memory. ;)
 
Last edited:

my573r10us

Senior Member
Jul 16, 2010
85
7
38
Haha, Francisco doesn't want to add any more than the ASRAM 50mb, but you can check out other SuperRAM kernels like DirtyV. :)

Free RAM technically doesn't matter in Linux/Android like it does in Windows. Free RAM is wasted RAM, and management is more important, and Android manages it pretty well.

ohh okay.. :(
with dirtyV, my camera always stop working after some use, i dont know why, need to restart to fix it, and then happen again after some use (any version of dirtyV).

but, my other app (such as whatsapp, line, and kakao talk, bbm) closed it self (notification pending till i open the app again) bcause of the little space free ram i think :'( (it always happen when i used some kernel that has ~700mb ram), after using mpokang ~751mb, it rarely happened)

wanna upgrade to nexus 5, but.. no money haha
 
Last edited:

osm0sis

Senior Recognized Developer / Recognized Contribut
Mar 14, 2012
14,484
32,552
263
Halifax
GT-i9250
Nexus 7 (2013)
Fair enough! :)

Maybe give DirtyV-SR another try. It's in constant development, so maybe your camera issue is resolved. I've never had any trouble with my camera on it, and I use the Google Camera in PA Stock GApps. I just make sure it's not set to 1080p before flashing the kernel and it's good. :good:

The one from the 27th is also at my osmod link in the post above. ;)
 
Last edited:
  • Like
Reactions: Ci-Fi

metalspring

Senior Member
Nov 5, 2011
2,466
4,327
0
ohh okay.. :(
with dirtyV, my camera always stop working after some use, i dont know why, need to restart to fix it, and then happen again after some use (any version of dirtyV).

but, my other app (such as whatsapp, line, and kakao talk, bbm) closed it self (notification pending till i open the app again) bcause of the little space free ram i think :'( (it always happen when i used some kernel that has ~700mb ram), after using mpokang ~751mb, it rarely happened)

wanna upgrade to nexus 5, but.. no money haha

you can always compile it yourself and change the amount of reclaimed ram ;)

https://github.com/bsmitty83/DirtyV_tuna/commit/bded16c4bb2075feb0f789d14b3a7e1af9a8e1fa
 

my573r10us

Senior Member
Jul 16, 2010
85
7
38
Fair enough! :)

Maybe give DirtyV-SR another try. It's in constant development, so maybe your camera issue is resolved. I've never had any trouble with my camera on it, and I use the Google Camera in PA Stock GApps. I just make sure it's not set to 1080p before flashing the kernel and it's good. :good:

The one from the 27th is also at my osmod link in the post above. ;)

woah, okay will try.. thanks sir @osm0sis :laugh:

you can always compile it yourself and change the amount of reclaimed ram ;)

https://github.com/bsmitty83/DirtyV_tuna/commit/bded16c4bb2075feb0f789d14b3a7e1af9a8e1fa

actually i dont understand how to compile it, but will see..
thanks sir.. :good::good:
 

metalspring

Senior Member
Nov 5, 2011
2,466
4,327
0
So, back on topic.. ;)

We've got a few things to play with:

r396-test, and r395-toolchain + r395-optimized. :D

Comparisons? Benchmarks vs. r395 with the same settings?

I can compare the r396 and r395 optimized, haven't had much time to compare to regular r395 yet though.
With r395-optimized, I got about 13200 but with r396 I only got about 12000 and a few games I tried stuttered a little bit on r396, but worked fine with r395-optimized

Sent from my Galaxy Nexus using Tapatalk
 

metalspring

Senior Member
Nov 5, 2011
2,466
4,327
0
I know when dirtyv tried some ram overclock like r396 has the ram speed scores went up very slightly but ram performance scores dropped from about 900 to a little over 700 so it wasn't really worth it

Sent from my Galaxy Nexus using Tapatalk
 

Max94h

Senior Member
Sep 10, 2012
108
28
58
Trento
I'm running r395 optimised and it works perfectly, it's really fast... I haven't tried any benchmark though, I really don't like them :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
 

abalam

Senior Member
Oct 30, 2011
2,380
2,224
193
www.qrz.com

ahmadairfan

Senior Member
Aug 4, 2013
215
104
0
Bandung
So, back on topic.. ;)

We've got a few things to play with:

r396-test, and r395-toolchain + r395-optimized. :D

Comparisons? Benchmarks vs. r395 with the same settings?

Just reporting, guys.
Lower overall scores on r396 test, even the rams benchmark is still the same. Even though I tested it with exact settings I have on r395-optimized :confused:
Running r395-optimized so far I am impressed, smoothy :)
Using neph's settings for DirtyV and 1536 max.
 

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://forum.xda-developers.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! ]
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone