|*KERNEL*| *hells-Core* L/KK<test b80>18thJuly<b73 stable>21stApr[Q&A][DISCUSSION]

What is your opinion about the touch control feature

  • Total voters
    951
Search This thread
By:
Advanced…
C

chinadyj

Member
Mar 18, 2015
44
13
Canton
mcguolo said:
So, seems two nights is the limit; during the latest (and third, after deleting play services data) night in safe mode I had again a SOD; next step, I'll flash ROM kernel and see if SOD will happen again. It's a f***ing long work though! :crying:
Click to expand...
Click to collapse

IMO, sod may be related to the cpu voltage. Because different cpus have different PVSs that may make an impact on the lowest voltages of different cpus. I find that the default voltage of 384Mhz is 900mV even though there are four levels of pvs (I am using Quanta v16). But different pvs values should have different voltages? you can see: http://forum.xda-developers.com/showthread.php?t=2215710
So I am trying to increase the glabal voltage (+25mV), I dont know if it could help but by far all works fine for two day. I will keep on testing.
sorry for my bad eng:(
 
mcguolo

mcguolo

Senior Member
Jun 12, 2012
125
23
chinadyj said:
IMO, sod may be related to the cpu voltage. Because different cpus have different PVSs that may make an impact on the lowest voltages of different cpus. I find that the default voltage of 384Mhz is 900mV even though there are four levels of pvs (I am using Quanta v16). But different pvs values should have different voltages? you can see: http://forum.xda-developers.com/showthread.php?t=2215710
So I am trying to increase the glabal voltage (+25mV), I dont know if it could help but by far all works fine for two day. I will keep on testing.
sorry for my bad eng:(
Click to expand...
Click to collapse

You are speaking of cpu binning, and yes, it is true that different cpus (of the same type) can reach different frequencies and voltages; normally my cpu voltage @384Mhz is 850mV... and could be possible that this value it's a little too low for Marshmallow (with KitKat and Lollipop I could easily undervolt by 50mV).
I think this SODs are mainly a software issue, but I'm going to raise lower frequencies voltage too, let's see what happen.
In the meanwhile I just replaced my two-and-a-half years old battery with a new one, and had a SOD last night, so it's not a battery thing.
 
dragos281993

dragos281993

Recognized Contributor
Mar 29, 2014
2,941
4,076
Iasi
mcguolo said:
You are speaking of cpu binning, and yes, it is true that different cpus (of the same type) can reach different frequencies and voltages; normally my cpu voltage @384Mhz is 850mV... and could be possible that this value it's a little too low for Marshmallow (with KitKat and Lollipop I could easily undervolt by 50mV).
I think this SODs are mainly a software issue, but I'm going to raise lower frequencies voltage too, let's see what happen.
In the meanwhile I just replaced my two-and-a-half years old battery with a new one, and had a SOD last night, so it's not a battery thing.
Click to expand...
Click to collapse
Do you use Xposed ?

Sent from my Nexus 4 using Tapatalk
 
mcguolo

mcguolo

Senior Member
Jun 12, 2012
125
23
No, I had the wifi-drain bug so I restored my phone formatting /data and /system at the beginning of March and configuring it as a new device; wifi drain disappeared, and since then I use a minimal installation: Pure Nexus + HC 88, no uv (only max freq @ 1242Mhz, hotplug cpu off @ 1024, dt2w), Whatsapp, Telegram, Signal and a few other apps; as I wrote in Quanta's thread, I used Quanta v13 happily for a month, then SODs began to happen; switch to HC, had 2 nights with no SOD, then again. Cleared play services data and again had only 2 nights with no SOD.
During the night I use flight mode on, and do not disturb mode. I really do not know what else to check.
 
dragos281993

dragos281993

Recognized Contributor
Mar 29, 2014
2,941
4,076
Iasi
mcguolo said:
No, I had the wifi-drain bug so I restored my phone formatting /data and /system at the beginning of March and configuring it as a new device; wifi drain disappeared, and since then I use a minimal installation: Pure Nexus + HC 88, no uv (only max freq @ 1242Mhz, hotplug cpu off @ 1024, dt2w), Whatsapp, Telegram, Signal and a few other apps; as I wrote in Quanta's thread, I used Quanta v13 happily for a month, then SODs began to happen; switch to HC, had 2 nights with no SOD, then again. Cleared play services data and again had only 2 nights with no SOD.
During the night I use flight mode on, and do not disturb mode. I really do not know what else to check.
Click to expand...
Click to collapse

May I ask what what the process of transitioning from Quanta to HC ?
Don't spare the details. Type in all the steps that you followed.

Sent from my Nexus 4 using Tapatalk
 
  • Like
Reactions: mcguolo
mcguolo

mcguolo

Senior Member
Jun 12, 2012
125
23
First of all, thank you.
I simply flashed boot.img from the ROM, rebooted system, and then flashed HC. But first I did try Quanta V10 (always flashed boot.img first). I forgot to mention that last week I flashed latest PureNexus, and again formatted /data and /system, and configured the phone as new device to try to solve SODs problem.
 
dragos281993

dragos281993

Recognized Contributor
Mar 29, 2014
2,941
4,076
Iasi
mcguolo said:
First of all, thank you.
I simply flashed boot.img from the ROM, rebooted system, and then flashed HC. But first I did try Quanta V10 (always flashed boot.img first). I forgot to mention that last week I flashed latest PureNexus, and again formatted /data and /system, and configured the phone as new device to try to solve SODs problem.
Click to expand...
Click to collapse

I suggest you switch from HC to Hellspawn r12. It's based on HC but it's constantly being updated and in case of "emergency" you'll have the full support of everyone including the kernel's developer. Hellspawn is a beefed up and improved HC, to put it this way.
Now, let's get to your issue.
Download "Hellspawn r12 tc 5.3 AOSP".
First of all, uninstall the kernel manager that you're using, or all of them if you have more than one installed. Then reboot into recovery. Do a cache + dalvik cache wipe. Dirty flash the ROM, not just the "boot.img" file, then flash the new kernel. Do a cache + dalvik cache wipe again and then reboot to system.
After the phone boots up, install kernel manager, but only one and make sure it's not restored or something cause sometimes people forget about deleting the kernel manager's data before moving to a different kernel, and when the phone boots up, the manager will attempt to apply the settings previously used and some of those settings are different or non existent with a different kernel, and that means problems.
Keep me posted.

Sent from my Nexus 4 using Tapatalk
 
  • Like
Reactions: mcguolo
mcguolo

mcguolo

Senior Member
Jun 12, 2012
125
23
Great, thank you! I didn't know of Hellspawn! I'm gonna do as you suggest and experiment with this configuration for a few days.
 
mcguolo

mcguolo

Senior Member
Jun 12, 2012
125
23
dragos281993 said:
I suggest you switch from HC to Hellspawn r12. It's based on HC but it's constantly being updated and in case of "emergency" you'll have the full support of everyone including the kernel's developer. Hellspawn is a beefed up and improved HC, to put it this way.
Now, let's get to your issue.
Download "Hellspawn r12 tc 5.3 AOSP".
First of all, uninstall the kernel manager that you're using, or all of them if you have more than one installed. Then reboot into recovery. Do a cache + dalvik cache wipe. Dirty flash the ROM, not just the "boot.img" file, then flash the new kernel. Do a cache + dalvik cache wipe again and then reboot to system.
After the phone boots up, install kernel manager, but only one and make sure it's not restored or something cause sometimes people forget about deleting the kernel manager's data before moving to a different kernel, and when the phone boots up, the manager will attempt to apply the settings previously used and some of those settings are different or non existent with a different kernel, and that means problems.
Keep me posted.

Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
After a week with no SODs I can finally (I hope) be happy again with my nexus 4. I've done as you suggested, and all is ok now, thank you!
 
dragos281993

dragos281993

Recognized Contributor
Mar 29, 2014
2,941
4,076
Iasi
mcguolo said:
After a week with no SODs I can finally (I hope) be happy again with my nexus 4. I've done as you suggested, and all is ok now, thank you!
Click to expand...
Click to collapse
I'm glad to hear that.
Even the smallest detail matters when it comes to flashing, tweaking, etc. But if you do it carefully and the right way, nothing can go wrong.

Sent from my Nexus 4 using Tapatalk
 
N

noobmazta

Member
Nov 20, 2016
8
0
hi, i read the 1st page but i still didnt get it, i actually a noob XD i never installed any custom kernel before, then now i will try to install it, but 1st i want to make sure what kernel that i sud to install.
i am using nexus 4 with pure nexus project 6.0.1 rom, and i heard that hells core kernel is good for this rom, thing that i want to ask is, where should i download the kernel, and what type of kernel that suitable for my rom? i really not understand Xd.. i hope some1 will answer my Q..
 
N

nARMstrong20

Senior Member
Dec 11, 2014
195
54
Moto G Power
noobmazta said:
hi, i read the 1st page but i still didnt get it, i actually a noob XD i never installed any custom kernel before, then now i will try to install it, but 1st i want to make sure what kernel that i sud to install.
i am using nexus 4 with pure nexus project 6.0.1 rom, and i heard that hells core kernel is good for this rom, thing that i want to ask is, where should i download the kernel, and what type of kernel that suitable for my rom? i really not understand Xd.. i hope some1 will answer my Q..
Click to expand...
Click to collapse
I think you're thinking about hellSPAWN, there is a thread and download link on this forum. Hell score support ended with early Marshmallow I think.
 
You must log in or register to reply here.

Similar threads

efrant
[REF] [RADIO] Mako modem collection
Replies
3K
Views
1M
bombadier
bombadier
75markus
★ [ROM][4.4] CyanogenMod 11 ★ DISCUSSION,TALK, Q&A Thread
Replies
7K
Views
1M
S
Suwonuser
stuffynet
Android 5.X Lollipop Discussions.....
Replies
7K
Views
1M
bluebirch
bluebirch
morrislee
[REF] Mako hybrid modem collection [UPDATED: 6/5/2014]
Replies
2K
Views
514K
gorilla p
gorilla p
KidCarter93
»All LTE Discussion«
Replies
3K
Views
576K
acejavelin
acejavelin

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 262
    xanthrax
    xanthrax
    |*KERNEL*| *hells-Core* L/KK<test b80>18thJuly<b73 stable>21stApr[Q&A][DISCUSSION]

    [SIZE=+2]This thread has been created
    for
    Questions & Answers/Troubleshooting    [/SIZE]​
    [SIZE=+2]Specific to[/SIZE]

    233680d1377019913-kernel-jb-jss15j-jwr66v-cm-hells-core-b40-21-10-2013-hells_core_banner__02_white_by_r4yntv-d6iyvf9-klein.jpg


    Hello fellas ! This is a thread for discussions, questions and answers


    DOWNLOADS    ​

    mirror BOX

    Kernel sources

    CM 12.1: https://github.com/hellsgod/hells-Core-N4/commits/cm-12.1

    Lollipop 5.1: https://github.com/hellsgod/hells-Core-N4/commits/l-mr1

    AOSP: https://github.com/hellsgod/kernel_msm/commits/mr2-rebase

    CM: https://github.com/hellsgod/kernel_msm/commits/cm-11-rebase

    L: https://github.com/hellsgod/kernel_msm/commits/l-release


    please check the 2nd , 3rd and the 4th post for some more info
    thumb_light_bulb-13775B15D.gif


    Starting with version b40 ( JSS, JWR and CM) the multiboot patch by Tasssadar has been applied so it can be successfully used for.

    Change logs b65 onwards


    (b81)
    -temp threshold set to 70°C
    -few commits from M
    -updated toolchain

    (b80)
    -updated BFQ-reverted gpu patches to fix chrome issues-some little fs fixes-hellsCode from @Maxr1998

    (b79)
    -added back Franco`s input listener-added back Franco`s conservative
    -added input boost logic to hellsactive

    (b78)
    -Reverted back to GCC 4.9.3 and reverted conservative changes, switched back to hellsactive.
    -should be back to the state of b73 now, except updated faux sound, 5.1.1 commits from google and bfq I/O sched.

    (b75)
    -faux sound updated-hopefully screen freeze issue fixed

    (b74) http://forum.xda-developers.com/showpost.php?p=60370527&postcount=10313(b73)-Merged a patch from stratosk to temporarly disable dt2w with the power key.
    -Enable it with "echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_pwr_disable"
    - If you use your power key to turn off the screen, dt2w will be disabled, until you turn it on with the power button again.

    (b70)-compiled with UBERTC-build flags from shamu/hammerhead(b69)-some fixes from linux upstream (3.4.y)
    -new build flag (floop-nest-optimize)
    -rtmutex fixes-sched/nohz/irq/genirq improvements from linux mainline

    (b66)
    -Upstream changes from Linux upstream (refer to git)
    -Some fixes for hellsactive/interactive-Removed boost framework from msm_mpdecision
    -Added cpu-boost for input boost and thread migrations-Improved cpu-boost-Make scheduler aware of frequency state-writeback fixes-some other little things

    (b68)
    -misc kgsl updates from caf-disabled some debugging and tracing
    -optimizazions for interactive and hellsactive-misc other little fixes for rq_stats and sched

    (b65-L)
    -Merged latest "L" commits-Merged some upstream stuff from my hh branch


    Change logs - old kernels

    as from b47 to b64 the kernel it is compatible ONLY with android 4.4.3/4/L

    from b65 onwards the kernel works for L only
    (b64)-Several ARM patches for suspend/cacheflush/MPU (little longer wakeup time from time to time - but a little less drain during sleep)-New build flags-kgsl: Wakeup only for touch events (to make sure the input event handler is called only for touch inputs)(b63)-kgsl upstream for using with the new drivers-UIO fixes(b60)reverted slimbus changescompiled with new boostedtcmisc fixes(b58)-smp fixes from upstream-mm, vmscan fixes from upstream-random fixes from upstream-smartmax is back!-memcpy optimizations for cortex A15 (i know we don't have a "real" A15, but lets test it)-lib: Use neon-vfpv(b57)-kthread fixes-sched/nohz fixes-tick fixes-cgroup fixes-slimbus controller from hammerhead-some improvement for the slimbus-msm_mpdecision: a tad more conservative, check-enabled sched_mc and cpupower-set fiops as default scheduler-set sched_mc = 2(b56)-merged some upstream fixes-reverted two cpuidle patches(b55)(b54)-New governor: hellsactive*-speedup late resume (faster wakeup)-ext4 patches-pm/bus patches to prevent reported crashes (feedback needed!)-some other little fixes here and there-compiled with boostedtc 4.9.2 by @aznrice2k4*hellsactive:-Based upon intelliactive-removed input boost (we have an input boost in the hotplug driver)-removed sync feature-removed sampling down factorFollowing was added:-Align timer windows for all CPUs*It's more advantageous to evaluate all CPUs at same time so that interactive governor gets a complete picture of the load on each CPU at a specific time. It could also reduce number of speed changes made if there are many CPUs controlled by same policy. In addition, waking up all CPUs at same time would allow the cluster to go into a deeper sleep state when it's idle.-Reset last evaluated jiffy in idle callback*When CPU has been busy for a long time, last evaluated jiffy will be quite behind because the timer would have been canceled. We don't want to schedule a timer to fire in the past as load will always be 100%. Reset last evaluated jiffy so that timer will be scheduled for thenext window.-Round up timer_rate to match jiffy*Timers are scheduled in unit of jiffies. Round up timer_rate so that it matches the actual sampling period.-Use del_timer/add_timer_on to rearm timers*Replace mod_timer_pinned() with del_timer(), add_timer_on(). mod_timer_pinned() always adds timer onto current CPU. Interactive governor expects each CPU's timers to be running on the same CPU. If cpufreq_interactive_timer_resched() is called from another CPU, the timer will be armed on the wrong CPU.Replacing mod_timer_pinned() with del_timer() and add_timer_on() guarantees timers are still run on the right CPU even if another CPU reschedules the timer. This would provide more flexibility for future changes.-Support variable frequency calculations**Use a threshold value up to which we are evaluating the current speed weighted by current load against each new choice of speed. Above switch to the original frequency calculation proportional to load relative to the max possible frequency which allows for more dynamic and fair changes.Default threshold is policy->min which guarantees minimal freqs and energy usage during (offloaded) media playback.Also, choose the highest frequency below or at target, which generally saves us one freq level.-Don't scale beyond min if the load is low***-Thread migration commit***http://forum.xda-developers.com/showpost.php?p=55298804&postcount=7952I've just made some little changes on commits to suit my needs.credits:*CAF**myfluxi***franciscofranco(b53)-fixed cores getting stuck at input_boost if you've min 2 cores online: commit-updated msm_mpdecision with latest nexus 5 commits(b52)Compiled with Linaro 4.9.2-2014.08 by Christopher83New build flags from my hammerhead branch and @baromeCode is identical with b51. Just a newer toolchain and new build optimizations. Let's see if there are new stability issues. I think we've gained some little performance boost(b51)-Added some commits for the camera. We had some reports about reboots while using flash. Maybe there'll be less of them. I don't think I can fix them completely...-Removed some debugging-Some love for conservative governor (thx stratosk)-Added KERNEL_MODE_NEON-Changed some little things in the flags-Some little things here and there. Refer to git if you'd like to know it exactly (b50-test)-No problems occured, just merged some cool stuff :)-Merged backlight dimmer from stratosk-Added a ton of kgsl/adreno patches (L sources) and Franco`s interactive GPU governor-Added UIO Sharedmem (L sources)(b49-test)NO UNDERVLOTING ANYMORE , stock voltages by default Compiled with Linaro GCC-4.9.1 from Christopher83msm_mpdecision from showpintelliactive governor (default)ZEN scheduler (default)FIOPS schedulerMany many things under the hood (check git)Touch Wake (stratosk)DT2W (stratosk)and so on... ... ...http://forum.xda-developers.com/showpost.php?p=55061297&postcount=7579(b47-pre-release) STABLEMerged 4.4.3Update to Linux 3.4.93Linaro 4.9.1 from Christopher83IMPORTANT NOTE!!!!!IF YOU COME FROM HELLSDOCTOR, PLEASE REFLASH YOUR ROM OR CLEAR YOUR INIT.D FOLDER!!! OTHERWAYS YOU'LL HAVE FC's LIKE HELL!(b46 test 4)-OOM Upstream to 3.14 from faux-S2W Fixes from AK-Linux 3.4.86(b44-45)-Upstream auf 3.4.84-Linaro 4.8.3 03.2014-Cpuidle Commit-futex Upstream updated-jbd2 commits optimized-LoUIS Cache-81mhz(b44 test t3)Lowest frequency 81 MHz Updated to linux 3.4.79Merged CM optimizations(b43)-Rebase auf 4.4.1 Sourcen-Linux 3.4.76-S2W/dt2w Port vom N5-faux sound 3.2-suspend_freq auf max angehoben-Kleine Fixes usw. siehe Git(b40)-Upstream from 3.4.65 auf 3.4.66-ca. 100+ SLAB/SLUB/SL[AU]B/mm... Commits-Module Support (for TouchControl)-Conservative GPU: Thresholds set slightly differently ( probably a little smoother when scrolling)-S2W Fix from fluxi-kexec Support (MultiROM)-3 epoll Commits from Upstream (b39)-Rebase auf CM/JSS/JWR Sources-Compiled with Linaro 4.8.2.09 Toolchain-Upstream from 3.4.65-O3 Support with Custom Build Flags-Conservative GPU Governor-msm_hotplug Hotplug Control (Tanks geht an fluxi)-dynamic fsync off


    -=-=-

    Thank you @hellsgod !
    do you want to show gratitude ? donate to hellsgod HERE
    all credits to him , i`m just a twitter :)
    -=-=-
    Thank you also to these awesome guys @aznrice2k4for his great toolchain
    @faux123
    @franciscofranco
    @myfluxi
    @stratosk
    @ak
    @flar2
    @neobuddy89
    @Christopher83
    @show-p1984
    @mrg666
    hells-Core on G+
    hells-Core kernel bloghells-Core kernel blog
    banners
    233112d1376855492t-kernel-jb-jss15j-jwr66v-cm-hells-core-b40-21-10-2013-hells_banner_klein.png
    233680d1377019932t-kernel-jb-jss15j-jwr66v-cm-hells-core-b40-21-10-2013-hells_core_banner__02_white_by_r4yntv-d6iyvf9-klein.jpg
    View
    74
    hellsgod
    hellsgod
    Q&A Game

    Q: My kernel app tells me my min_freq is 918mhz. Why is that?
    A: Its because of input boost. Your frequency will be boosted to 918mhz as soon as you touch your screen. It will be boosted for 1 second after touch. So you have smooth animations and no scrolling stutters.

    Q: My device rebooted / didn woke up from deep sleep. What can I do to help you to find the cause?
    A: Install "Syslog" from the Play Store and get me the "Last Kernel Log" or do it via terminal. You'll find the command one post under this.

    Q: Will you add S2W/S2S again?
    A: No. We're using dt2w from starosk now. If you want to use S2W with my kernel, clone my sources and add it by yourself.

    Q: Why the cpu jumps to 1134mhz so ofter during idle?
    A: Thats because we're using an interactive based governor. Interactive based governors jumps to hispeed_freq (1134mhz) if the load reaches 99%. Don't forget, even if you're doing nothing, you always have some background load. The lower you set your min_frequency, the faster it reaches 99% load and will jump to hispeed_freq more often.

    Battery Profile:

    I've made a battery profile for hot plug settings. Following is changed:

    echo "20" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_0 = Threshold for cpu1 to kick in
    echo "85" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_2 = Threshold for cpu2 to kick in
    echo "10" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_3 = Threshold for cpu1 to kick out
    echo "99" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_4 = Threshold for cpu3 to kick in
    echo "45" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_5 = Threshold for cpu2 to kick out
    echo "60" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_7 = Threshold for cpu3 to kick out

    Most of the time you'll be running on dualcore mode (cpu0 and cpu1). If the load reaches a high level with both cores maxed out, the other cores kicks in and will go off again really quickly. The profile will be active after 90 seconds (counted from bootanimation) so your device boots up with full power first. It'll be stupid to limit it on bootup.

    Balanced Profile:

    echo "15" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_0
    echo "35" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_2
    echo "8" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_3
    echo "55" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_4
    echo "20" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_5
    echo "40" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_7

    Its a little less conservative than the battery profile and a little less aggressive than the default values. I've tried to make something in between. Try it and left a comment :)​
    View
    74
    hellsgod
    hellsgod
    Finally after some days with my N5 kernel I've found time to compile a new kernel for our beloved N4 :) I've called it b44, because it should be the final b44. It was long enough in a test stadium... One thing I still have to do, is hardcode 192mhz as min freq, because some device won't boot, even if 192mhz is defined as min freq in the script. But the script will be executed some seconds later, so the device will spend very short time on 81mhz.

    The kernel isn't public yet on dev-host. I've just added some things, compiled and it booted fine. Flash only if you know what you're doing!

    AOSP

    CM

    Changelog:

    -Linaro 02.2014
    -Linux 3.4.82
    -Kernel Mode NEON
    -futex Changes from upstream (faux123)
    -Some other things (=

    I,ve played around with the N4 in the last few days and I don't see the need to add new governors atm (like intelliactive). intellidemand does exactly what I want it to do. I don't want to add a new governor, only because its around there.

    Feedback is welcome, as always :) If I've forgot something to add I said I'll add in this one, please let me know :)

    Aaaand good night (it's 05:46 AM here...)

    hells
    View
    64
    xanthrax
    xanthrax
    I will post here the most common issues , if any and a collection of tricks and tips based on all users experience , then will be easier for everyone to track them ;)
    i will keep an eye on every post :cowboy:
    -=-=-
    Please have a look first at this thread
    [Repository] [MakoStuff] [Nexus4 Tools] by @gorilla p

    then >>> Troubleshooting Synapse

    also >>> Installing Synapse and importing profiles

    -=-=-
    as from version b49 the kernel has been completely rebased therefore I will add below some new tips and tricks

    - first check the change log from b49 onwards and also the discussion starts with that post

    - the kernel isn`t undervolted anymore by default so , heating occurs due to stock voltages , I`m sure you know what to do then

    - new dt2w by stratosk dropping the s2w/s2s feature

    - some inputs here http://forum.xda-developers.com/showpost.php?p=55232079&postcount=7836
    terminal command for dt2w
    echo 1 > /sys/devices/virtual/input/lge_touch/dt_wake_enabled
    Click to expand...
    Click to collapse
    thanks @steviemch for heads up

    - try this http://forum.xda-developers.com/showpost.php?p=55214263&postcount=7820 if you`re facing in call delay , thanks @eurochild
    - fsync status
    -=-=-
    For those who wants to use the latest hellscore based on KK 4.4.2 on a ROM based on 4.4.3/4/L , here is a fix for loosing WIFI

    http://forum.xda-developers.com/showpost.php?p=53132436&postcount=6487

    new2.gif

    -=-=-=-
    and thanks to @themike10452 we have ...
    Hellscore Kernel Manager
    original thread here >>> http://forum.xda-developers.com/nexus-4/themes-apps/app-hellscore-kernel-tweaker-t2669442
    playstore
    Hellscore Kernel Manager
    -=-=-=-

    SCRIPT CREATOR
    thanks @Maxr1998

    hells-Core Init.d creator

    -=-=-=-
    Hells-Core kernel with OTG support for Nexus 4 KK
    thanks @justvarshney

    -=-=-=-
    as some other kernels comes with their own ramdisk which will remain over after flashing hellsCore and an unpredictable negative impact on your phone stability may occur , i would recommend you to flash a STOCK KERNEL from below prior flashing

    Nexus 4 Stock 4.4.3 KTU84L >>> http://d-h.st/qxB

    Nexus 4 Stock 4.4.2 KOT49H >>> http://d-h.st/W8P

    Nexus 4 Stock 4.4 KRT16S >>> http://d-h.st/HwN

    Nexus 4 Stock 4.4 >>> http://d-h.st/apv

    Nexus 4 Stock 4.3 >>> http://d-h.st/TRC

    Nexus 4 AOSP 4.3 >>> http://d-h.st/NuC
    -=-=-=-
    the recommended applications to control/modify the kernel are
    Trickster MOD Kernel Settings
    Faux123 Kernel Enhancement

    -=-=-=-
    to be used only for 4.3/1 kernels
    doesn`t affect kk kernels , in case of a broken wifi , just re-dirty-flash your rom and then the kk kernel
    dePRIMAtor

    -=-=-=-
    please provide logs in case of troubles
    use the command below in terminal emulator to extract the last_kmsg in case of a sudden reboot

    su
    cat /proc/last_kmsg > /sdcard/last_kmsg.txt

    -=-=-=-
    A nice collection of terminal commands to manually modify the kernel settings as per your desire made by @shengovind
    thanks pal ! ... i must write a song for him now ... oh well
    To Set CPU Governor:

    Su
    echo "NAME" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    echo "NAME" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
    echo "NAME" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
    echo "NAME" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

    NAME can be replaced by intellidemand, interactive, conservative, wheatley, ondemand, performance
    Default is intellidemand. Changing NAME to conservative changes CPU governor to conservative



    FOR SETTING GOVERNOR PARAMETERS:

    First set governor then you will be able to edit these..
    I do not know what each and every parameter does so these won’t help normal users’ and those who know what these mean will probably know how to edit these. But I’ve included them just because i had to …

    INTELLIDEMAND :

    echo "FREQUENCY" > /sys/devices/system/cpu/cpufreq/intellidemand/boostfreq

    Change FREQUENCY to required value of frequency. This is the frequency cpu is boosted to when screen is touched.

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/boostpulse

    not sure what this does and what the set of values are

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/boosttime

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/down_differential

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/ignore_nice_load

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/io_is_busy

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_active_load

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_active_max_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_browser

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_inactive_load

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_inactive_max_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/optimal_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/powersave_bias

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_down_factor

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate_min

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/sync_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/two_phase_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold_any_cpu_load

    echo "??" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold_multi_core



    INTERACTIVE

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/above_high_speed_delay

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/boost

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration

    AFAIK this is the time for which cpu is boosted

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/io_is_busy

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/target_loads

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

    echo "??" > /sys/devices/system/cpu/cpufreq/interactive/timer_slack

    CONSERVATIVE

    echo "FREQ" > /sys/devices/system/cpu/cpufreq/conservative/boostfreq
    As told above

    echo "??" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold

    echo "??" > /sys/devices/system/cpu/cpufreq/conservative/freq_step

    echo "??" > /sys/devices/system/cpu/cpufreq/conservative/ignore_nice_load

    echo "??" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor

    echo "??" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate

    echo "??" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold

    WHEATLEY

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/allowed_misses

    echo "FREQ" > /sys/devices/system/cpu/cpufreq/wheatley/boostfreq

    told above

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/ignore_nice_load

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/io_is_busy

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/powersave_bias

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/sampling_down_factor

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/sampling_factor

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/sampling_rate

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/target_residency

    echo "??" > /sys/devices/system/cpu/cpufreq/wheatley/up_threshold

    ONDEMAND:

    echo "FREQ" > /sys/devices/system/cpu/cpufreq/ondemand/boostfreq

    told above

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/down_differential

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/sync_freq

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load

    echo "??" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core

    GO HERE IF YOU WANT TO TRY AND MAKE SENSE OUT OF ALL THIS: http://forum.xda-developers.com/showthread.php?t=1369817




    CHANGING GPU GOVERNOR

    echo “GOVERNOR” > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/pwrscale/policy

    Change GOVERNOR to conservative, performance, simple, or ondemand.
    echo "1" > /sys/module/sync/parameters/fsync_enabled

    TO ACTIVATE DOUBLE TAP TO WAKE

    echo 1 > /sys/android_touch/doubletap2wake

    TO DEACTIVATE DOUBLE TAP TO WAKE

    echo 0 > /sys/android_touch/doubletap2wake

    TO ACTIVATE S2W

    echo "1" > /sys/android_touch/sweep2wake

    TO DEACTIVATE S2W

    echo "0" > /sys/android_touch/sweep2wake

    BOOST ON TOUCH

    echo "X" > /sys/module/msm_hotplug/cpus_boosted

    X can be replaced by 1,2,3 or 4 . This sets number of cores to be boosted on touch,
    Default is 2. Changing X to 4 boosts 4 cores on touch.

    MINIMUM NUMBER OF CPUS ONLINE

    echo "X" > /sys/module/msm_hotplug/min_cpus_online

    X can be replaced by 1,2,3 or 4 . This sets number of cores to be online at all time,
    Default is 1. Changing X to 2 makes sure 2 cores are online all the time.

    MAXIMUM NUMBER OF CORES ONLINE

    echo "X" > /sys/module/msm_hotplug/max_cpus_online

    X can be replaced by 1,2,3 or 4 . This sets maximum number of cores that can go online,
    Default is 4. Changing X to 2 makes sure your phone dual core.

    MAXIMUM FREQUENCY WHEN SCREEN IS OFF

    echo "X" > /sys/module/msm_hotplug/suspend_freq

    X can take values 192000, 384000, 540000, 702000, 1026000, 1242000, 1350000, 1512000
    Default is 702000. Changing X to 1026000 makes maximum frequency when screen is off to 1ghz



    Someone tell how to set gamma manually... Thank you.
    There might be a lot of mistakes, so try and correct them..

    -=-=-
    Color profiles scripts

    by @mohitgalaxy3
    0
    View
    61
    xanthrax
    xanthrax
    Dear fellas, I would like to introduce you to... Well, I can't say more uploadfromtaptalk1410293417512.jpg
    I just couldn't resist

    Sent from my Darkside of LG G2
    View

New posts