|*KERNEL*| *hells-Core* L/KK<test b80>18thJuly<b73 stable>21stApr[Q&A][DISCUSSION]
- Thread starter xanthrax
- Start date
-
- Tags
- hellscore kernel mako
Ohh... Unfortunately I can't find that b47, apparently the clouds we stored these kernels are empty or containing fee versions, I will try to resurrect my dead Nexus 4 to see what I can find inside of his belly, damn I miss that phoneSorry to be a pain @xanthrax any luck with b47?
No worries just wanted a KK kernel & IMO that particular version was the best, hey-ho thanks anyhow.Ohh... Unfortunately I can't find that b47, apparently the clouds we stored these kernels are empty or containing fee versions, I will try to resurrect my dead Nexus 4 to see what I can find inside of his belly, damn I miss that phone
Last edited:
I have added some more as well, maybe already uploaded
https://app.box.com/s/gmvg9kwoj3gvfxlf5e9f7s7223omqxh6
@hellsgod I've got an issue with this kernel using chroma and magisk. with b88
Apparently this kernel sets the /sbin/.core/img folders to read only and nothing can change this to RW for magisk to work properly. I've asked this in the magisk thread and it's been decided that this kernel is causing this issue. by setting some things to read only. as when i use chroma's default kernel, no issue like this is present.
https://forum.xda-developers.com/showpost.php?p=77068536&postcount=25871
https://forum.xda-developers.com/showpost.php?p=77075605&postcount=25894
https://forum.xda-developers.com/showpost.php?p=77084333&postcount=25913
This is what should be happening, but it's not.
https://github.com/topjohnwu/Magisk...74a2940ed52/native/jni/core/bootstages.c#L405
I dont know if you can offer some advice as this kernel is fantastic for my nexus, Super low core speed, everything.
Apparently this kernel sets the /sbin/.core/img folders to read only and nothing can change this to RW for magisk to work properly. I've asked this in the magisk thread and it's been decided that this kernel is causing this issue. by setting some things to read only. as when i use chroma's default kernel, no issue like this is present.
https://forum.xda-developers.com/showpost.php?p=77068536&postcount=25871
https://forum.xda-developers.com/showpost.php?p=77075605&postcount=25894
https://forum.xda-developers.com/showpost.php?p=77084333&postcount=25913
This is what should be happening, but it's not.
https://github.com/topjohnwu/Magisk...74a2940ed52/native/jni/core/bootstages.c#L405
I dont know if you can offer some advice as this kernel is fantastic for my nexus, Super low core speed, everything.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
262|*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]
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
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
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
-=-=-
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
74Q&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 comment74Finally 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...)
hells64I 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
-=-=-
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
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
-=-=-=-
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
-=-=-
Color profiles scripts
by @mohitgalaxy3
0
