Related
Code:
[CENTER]*** Disclamer ***
I am not responsible for any that you do to your device. Please be ready to provide as much information as possible. This includes logcats and providing necessary information like ROM, build date of my kernel and the ROM you are using.[/CENTER]
Introduction
This kernel is based of @raymanFX's AOSP kernel for the p600. The kernel name comes from the ROM it was built for BrokenOS. The BrokenNote kernel will work on any of the AOSP or CM based ROMs.
Click to expand...
Click to collapse
Installation instructions
* Flash using TWRP or Flashify
Click to expand...
Click to collapse
Download
BrokenNote Download
Click to expand...
Click to collapse
Kernel Source
BrokenNote Source Core
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: 06-25-15
[INDENT]
---Initial Release---
project kernel/samsung/lt03wifi/
92df186 cpufreq: Add back all Governors
6282159 Lazy: Fixups
7864f3e cpufreq: Remove unnecessary initialization of a local variable
35c7c5d cpufreq: Fix sparse warning by making local function static
2f8a379 cpufreq: return early from __cpufreq_driver_getavg()
c1990c4 cpufreq / core: Fix typo in comment describing show_bios_limit()
2850b3e cpufreq: Optimize cpufreq_frequency_table_verify()
e5dadb9 cpufreq: Introduce intellimm
1b20e4e un****ify interactive. again
1a1181c enable all the govs
5bbcc24 broken note kernel
8d89db1 this wont work yet
196a7fa dont need these either
[/INDENT]
Older changelogs:
Code:
Changelog: xx-xx-xx
Click to expand...
Click to collapse
Bugs
You tell me
Click to expand...
Click to collapse
Thanks To/Credits
* @raymanFX for bring the Exnyos 5420 to AOSP
* Ethan Johnson
Click to expand...
Click to collapse
XDA:DevDB Information
BrokenNote, Kernel for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
Orion116, raymanFX, Ethan Johnson
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 1.0
Created 2015-06-26
Last Updated 2015-06-26
Reserved
Reserved
I flashed to Temasek's rom and it bootloop. Flashed back the original Temasek kernel and it's working again.
buhohitr said:
I flashed to Temasek's rom and it bootloop. Flashed back the original Temasek kernel and it's working again.
Click to expand...
Click to collapse
Nope sure why it would bootloop since it is pretty much stock kernel with a few things add like more governors and some performance tweaks. Get a adb logcat for me.
Sent from my SM-P600 using Tapatalk
buhohitr said:
I flashed to Temasek's rom and it bootloop. Flashed back the original Temasek kernel and it's working again.
Click to expand...
Click to collapse
+1
hello install your latest kernel on 06/25/2015 Rom Temasek's bootloop:silly:
jeanmarce said:
+1
hello install your latest kernel on 06/25/2015 Rom Temasek's bootloop:silly:
Click to expand...
Click to collapse
Logcats or it didn't happen?. Also how are you flashing it. I need as much info as possible.
I will flash temasek later I guess.
Sent from my SM-P600 using Tapatalk
jeanmarce said:
+1
hello install your latest kernel on 06/25/2015 Rom Temasek's bootloop:silly:
Click to expand...
Click to collapse
buhohitr said:
I flashed to Temasek's rom and it bootloop. Flashed back the original Temasek kernel and it's working again.
Click to expand...
Click to collapse
I need a log otherwise I can't fix it.
Sent from my SCH-R530U using Tapatalk
I can confirm bootloops on Pacman and Temasek. How do I provide you with a logcat? The bootloop typically happens after it goes through the "Android is upgrading" bit.
Koserman said:
I can confirm bootloops on Pacman and Temasek. How do I provide you with a logcat? The bootloop typically happens after it goes through the "Android is upgrading" bit.
Click to expand...
Click to collapse
What TWRP version? What steps did you take to flash the kernel? I didn't get a android is updating boot up on BrokenOS. You need ADB installed. XDA has several tutorials on setting adb up. After adb is set up use the first and third adb commands at boot to get the logs. http://forum.xda-developers.com/showthread.php?t=1520508
Sent from my SM-P600 using Tapatalk
TWRP 2633
1st flash: On established Temasek - Wipe Caches, then flash.
2nd: PAC - Fresh ROM install, reboot into recovery, flash (no wiping).
3rd: PAC - Flashed again, Fix Permissions.
4th: Complete wipe, install Temasek, install GAPPs, install kernel. With this method, I got to a lock screen but rebooted shortly after.
I just broke my computer tonight (PSU or GPU...I overclocked the heck out of the poor thing...it was only a matter of time before it died) literally MINUTES after finishing the main quest line of Skyrim after hundreds of hours of goofing around ;-p
If I get my computer running, I'll try to get those for ya! Thanks again!
Koserman said:
TWRP 2633
1st flash: On established Temasek - Wipe Caches, then flash.
2nd: PAC - Fresh ROM install, reboot into recovery, flash (no wiping).
3rd: PAC - Flashed again, Fix Permissions.
4th: Complete wipe, install Temasek, install GAPPs, install kernel. With this method, I got to a lock screen but rebooted shortly after.
I just broke my computer tonight (PSU or GPU...I overclocked the heck out of the poor thing...it was only a matter of time before it died) literally MINUTES after finishing the main quest line of Skyrim after hundreds of hours of goofing around ;-p
If I get my computer running, I'll try to get those for ya! Thanks again!
Click to expand...
Click to collapse
Try this on either temasek or PAC. Clean flash, wipe everything but internal and external storage, the ROM and gapps, don't fix permission, get the ROM set to your liking then use flashify to flash the zip don't wipe anything just flash the zip.
Sent from my SM-P600 using Tapatalk
So, I wiped Cache + Dalvik, System, Data. Installed PAC + GAPPs, I rebooted, installed Flashify and flashed the kernel without wiping anything.
Once the tablet rebooted, it did the normal "Android is starting... Optimizing apps 1-80 something" at which point it reboots once it completes optimizing everything. It'll continue in this loop indefinitely.
Just for kicks, after 6 reboots, I then tried fixing permissions and wiping caches but to no avail. Hopefully someone with a working computer can help with the logcats!
Koserman said:
So, I wiped Cache + Dalvik, System, Data. Installed PAC + GAPPs, I rebooted, installed Flashify and flashed the kernel without wiping anything.
Once the tablet rebooted, it did the normal "Android is starting... Optimizing apps 1-80 something" at which point it reboots once it completes optimizing everything. It'll continue in this loop indefinitely.
Just for kicks, after 6 reboots, I then tried fixing permissions and wiping caches but to no avail. Hopefully someone with a working computer can help with the logcats!
Click to expand...
Click to collapse
Hmm. I will be interest in the logs for sure. Is PAC AOSP based or cm based? It shouldn't matter but it is good to know.
Sent from my SCH-R530U using Tapatalk
Just to let you know, I've been running BrokenOS and it's amazing! It think I'd gonna be my daily driver for quite a while. I've got the kernel tweaked and now it's absolutely flying and still getting great battery. My only requests would be Westwood TCP, Fiops scheduler, and undervolt control and I would be ecstatic! Great ROM and kernel my good man!
Koserman said:
Just to let you know, I've been running BrokenOS and it's amazing! It think I'd gonna be my daily driver for quite a while. I've got the kernel tweaked and now it's absolutely flying and still getting great battery. My only requests would be Westwood TCP, Fiops scheduler, and undervolt control and I would be ecstatic! Great ROM and kernel my good man!
Click to expand...
Click to collapse
Could you please provide the link for brokenOS ?
i am trying to use that kernel with temasek rom but bootloop
thanks
If you click on the kernel link, go up one directory and then you're there! It's under "lt03wifi."
Had nothing better to do this afternoon so figured I'd flash temasek and this kernel to get a log of the bootloop people are having. See attached
7786 said:
Had nothing better to do this afternoon so figured I'd flash temasek and this kernel to get a log of the bootloop people are having. See attached
Click to expand...
Click to collapse
Very cool man. Thanks. This will help with compatibility issues.
Can you also get a last_kmesg for me.
Sent from my SM-P600 using Tapatalk
I confirm brokenOS with the kernel is the best ????
Compatibility:
LineageOS 14.1 based roms; reported working with most 7.1.2 ROMs.
Download:
See attachments.
How to install:
Flash the zip.
If you come from another kernel, dirty flash your rom or LineageOS's boot.img before flashing this one (that also includes ROMs that come with a different kernel built-in).
Features:
Flash and forget
All cores are unlocked and unshackled
No hotplug (see: https://forum.xda-developers.com/showpost.php?p=72198795&postcount=140)
Spectrum support (Info: https://forum.xda-developers.com/showpost.php?p=72804608&postcount=192)
Reduced idle power consumption (don't complain about 3rd party wakelocks)
some wakelocks are blocked by default (thanks to @franciscofranco)
Credits:
@franciscofranco's zips.
Powered by: AnyKernel2 - @osm0sis
Extra thanks:
@karthick and @chaubeyprateek - Hyper Kernel
Interactive how-to: [GUIDE] [AKT] Advanced Kernel Tweaks by @Asiier, @patalao, @Mostafa Wael and @Senthil360
I am trying this out.Will you add d2w?
Working here on a6020a40 sd415 indian varient.
bodafranus said:
Compatibility:
Android Nougat 7.1.1 Lineage OS 14.1 based roms.
A6020 (tested only on l36 variant)
Download:
http://www106.zippyshare.com/v/IcjLb4RP/file.html
(will move to AFH shortly)
How to install:
Flash the zip.
Features:
Flash and forget
All cores are unlocked and unshackled
Reduced idle power consumption (don't complain about 3rd party wakelocks)
Wakelocks blocked by default (thanks to @franciscofranco)
Changelog:
https://gist.github.com/LegendMaster/767d12c93c5fc53dc5f214b4e10fce29
Source:
https://github.com/LegendMaster/android_kernel_lenovo_msm8916/tree/experimental
Known bugs:
Minimum frequencies on big cluster reverting to 960MHz. CPU Freq driver doesn't seem to remember policy->user_policy.min when waking up from suspended state.
You tell me. :good:
Credits:
init.rc all from @franciscofranco zips.
Powered by: AnyKernel2 - @osm0sis
HMP Scheduler and insights: [GUIDE] [AKT] Advanced Kernel Tweaks
Extra thanks:
@Dreamstar - Vegito Kernel
@chaubeyprateek - Hyper Kernel
Click to expand...
Click to collapse
Finally someone developing a different kernel! Very much appreciated!
Take a look at ExtremeKernel, it adds some bits missing from stock Kernel that would be nice to see here (Extreme seems to be discontinued).
Gonna follow this thread and try it!
@bodafranus thanks for a great kernel! Working here o a40 sd 415 indian variant. Here one bug though.. touch response is not working on ambient display.. it has been fixed in latest commits by Karthik. Kindly include these fixes in next version. Thanks!
Waiting for Alpha1 to try it! When will it be available?
Changelog seems to be promising!!
New version:
alpha1
1. changed governor and HMP scheduler values.
2. added bw_hwmon shenanigans to ramdisk (responsible for controlling some bus frequencies)
3. updated some drivers
4. merge 'caf/LA.BR.1.2.9_rb1.12' (kang from: karthick111)
If you experience any problems, send logs. (some can be found at: /sys/fs/pstore)
tanx said:
I am trying this out.Will you add d2w?
Click to expand...
Click to collapse
Not my priority, still have tons of patches to apply.
You can use Gravity Screen with everything but "Turn Screen ON by Proximity" disabled.
dr.bathman said:
Working here on a6020a40 sd415 indian varient.
Click to expand...
Click to collapse
Thanks.
IagoJevaux said:
Finally someone developing a different kernel! Very much appreciated!
Take a look at ExtremeKernel, it adds some bits missing from stock Kernel that would be nice to see here (Extreme seems to be discontinued).
Gonna follow this thread and try it!
Click to expand...
Click to collapse
You're welcome.
dr.bathman said:
@bodafranus thanks for a great kernel! Working here o a40 sd 415 indian variant. Here one bug though.. touch response is not working on ambient display.. it has been fixed in latest commits by Karthik. Kindly include these fixes in next version. Thanks!
Click to expand...
Click to collapse
I haven't seen anything in his commits related to this. Could you be more specific?
IagoJevaux said:
Waiting for Alpha1 to try it! When will it be available?
Changelog seems to be promising!!
Click to expand...
Click to collapse
Available now.
Is it working on a46?
Sent from my Lenovo Vibe K5 Plus using XDA Labs
AmithNRG said:
Is it working on a46?
Sent from my Lenovo Vibe K5 Plus using XDA Labs
Click to expand...
Click to collapse
You'll have to test it yourself or wait for somebody else's feedback.
The OP only has the l36 variant.
It's working on a46. I have it and working. Thanks for the work.
It seems kernel is not fully compatible with vibe k5 a6020a40 sd 415 Indian varient. Phone gets booted only if flashed over hyper kernel of prateekchaubey. But if lm kernel is flashed over stock lineage kernel, phone gets stuck at bootlogo. I checked both alpha0 & alpha1 versions after I got this. Logs from sys/fs/pstore has been attached which are after flashing alpha1 over hyper kernel.
And touch on ambient display is still not working with alpha1 version.
dr.bathman said:
It seems kernel is not fully compatible with vibe k5 a6020a40 sd 415 Indian varient. Phone gets booted only if flashed over hyper kernel of prateekchaubey. But if lm kernel is flashed over stock lineage kernel, phone gets stuck at bootlogo. I checked both alpha0 & alpha1 versions after I got this. Logs from sys/fs/pstore has been attached which are after flashing alpha1 over hyper kernel.
And touch on ambient display is still not working with alpha1 version.
Click to expand...
Click to collapse
@bodafranus
List of bugs:
timer_rate fixed on Little cluster, unable to change it.
minimum frequency on big cluster reverting to default after CPU wakes from suspended state.
AmithNRG said:
Is it working on a46?
Click to expand...
Click to collapse
Should work.
tanx said:
It's working on a46. I have it and working. Thanks for the work.
Click to expand...
Click to collapse
Thanks for letting me know
dr.bathman said:
It seems kernel is not fully compatible with vibe k5 a6020a40 sd 415 Indian varient. Phone gets booted only if flashed over hyper kernel of prateekchaubey. But if lm kernel is flashed over stock lineage kernel, phone gets stuck at bootlogo. I checked both alpha0 & alpha1 versions after I got this. Logs from sys/fs/pstore has been attached which are after flashing alpha1 over hyper kernel.
And touch on ambient display is still not working with alpha1 version.
Click to expand...
Click to collapse
That's strange, can you try flashing over latest official Lineage, after a Factory Reset wipe?
Try to grab a logcat while in bootloop, if it persists (see: https://forum.xda-developers.com/showthread.php?t=2274119)
I will check Ambient Display after I fix some issues.
bodafranus said:
List of bugs:
timer_rate fixed at 60000 on Little cluster, unable to change it.
minimum frequency on big cluster reverting to default after CPU wakes from suspended state.
Should work.
Thanks for letting me know
That's strange, can you try flashing over latest official Lineage, after a Factory Reset wipe?
Try to grab a logcat while in bootloop, if it persists (see: https://forum.xda-developers.com/showthread.php?t=2274119)
I will check Ambient Display after I fix some issues.
Click to expand...
Click to collapse
Ok.. I tried it on official lineage 10/4 build with fresh flash and the lm kernel alpha 1 is working without any problem like bootloop/stuck to bootlogo.
i am not using this kernel even not other, but having big trouble with lineage OS, basically cpu core bug i can say and i asked on its respective thread, page 72 and 73, dev and other users helped me but partially solved you can refer if you want to, but i will explain anyway here shortly,
i am using 20170410 built, and kernel adiutor, selinux permissive, i tried switching all possible options like core control, clock speed, governor, other thing, the only thing bug me is governor, like interactive and ondemand, max 1497mhz and min 200mhz i set, but it always on 1497mhz when even idle little process and core directly goes offline when no use, and never downclock, i also found too much over heating when any games or heavy task.
(**this is not bug of this kernel,
and this exactly same paragraph i'll be posting on lineage os thread, so if you like to suggest me about this bug you can in that thread )
so back to main track, will this kernel solve this problem?
also i see alpha 2 change log but no built.
dr.bathman said:
Ok.. I tried it on official lineage 10/4 build with fresh flash and the lm kernel alpha 1 is working without any problem like bootloop/stuck to bootlogo.
Click to expand...
Click to collapse
Great.
bik95122 said:
i am not using this kernel even not other, but having big trouble with lineage OS, basically cpu core bug i can say and i asked on its respective thread, page 72 and 73, dev and other users helped me but partially solved you can refer if you want to, but i will explain anyway here shortly,
i am using 20170410 built, and kernel adiutor, selinux permissive, i tried switching all possible options like core control, clock speed, governor, other thing, the only thing bug me is governor, like interactive and ondemand, max 1497mhz and min 200mhz i set, but it always on 1497mhz when even idle little process and core directly goes offline when no use, and never downclock, i also found too much over heating when any games or heavy task.
(**this is not bug of this kernel,
and this exactly same paragraph i'll be posting on lineage os thread, so if you like to suggest me about this bug you can in that thread )
Click to expand...
Click to collapse
Wrong thread. If you demand CPU power obviously it'll deliver, so expect it with heavy tasks. Overheat is a problem inherently of our device and its chassis, after all metals are good heat conductors...
Check your target_loads and background processes if you encounter this problem while idle.
bik95122 said:
so back to main track, will this kernel solve this problem?
Click to expand...
Click to collapse
It may, because tunables are already set up properly by default.
bik95122 said:
also i see alpha 2 change log but no built.
Click to expand...
Click to collapse
Yeah, no point in releasing a build with minimal changes. Next one will come up shortly with some bug fixes.
bodafranus said:
Wrong thread. If you demand CPU power obviously it'll deliver, so expect it with heavy tasks. Overheat is a problem inherently of our device and its chassis, after all metals are good heat conductors...
Check your target_loads and background processes if you encounter this problem while idle.
It may, because tunables are already set up properly by default.
Yeah, no point in releasing a build with minimal changes. Next one will come up shortly with some bug fixes.
Click to expand...
Click to collapse
really appreciate , i am gonna try this right now and sure will giving you some feedback, thanks.
quick feed, changes i see. A46 device
- little cores working very good as expected now, clock speed interactive as on demanded, which i prefer.
-but big core just stay at 1497 mhz constant (which i know its not problem on this kernel, it from lineageos rom that why i tried using this kernel to see fix) but i know someday may be solved by this kernel,
-one more thing i notice on small core, as its clock speed is as on demanded, but all 4 core speed same, instead of individual.
-now no core get automatically shutdown, even if no demand of an individual core. which is good as well as bad (i am kind of confused for this)
that all, this changes i looked as after flash just now.
bik95122 said:
-but big core just stay at 1497 mhz constant (which i know its not problem on this kernel, it from lineageos rom that why i tried using this kernel to see fix) but i know someday may be solved by this kernel,
Click to expand...
Click to collapse
this problem solved, this above mentioned problem is related to problem below quoted one
bik95122 said:
-one more thing i notice on small core, as its clock speed is as on demanded, but all 4 core speed same, instead of individual..
Click to expand...
Click to collapse
actually, its kernel adiutor doing, when i used cpuz, it showed all cpu at 200mhz which i set, and kernel adiutor need 2 full speed core to work smoothly, so kernel throttles to max clock speed of all 4 big core, instead of 2,
so far i am happy, thnks :good:
bik95122 said:
this problem solved, this above mentioned problem is related to problem below quoted one
actually, its kernel adiutor doing, when i used cpuz, it showed all cpu at 200mhz which i set, and kernel adiutor need 2 full speed core to work smoothly, so kernel throttles to max clock speed of all 4 big core, instead of 2,
so far i am happy, thnks :good:
Click to expand...
Click to collapse
How is the battery usage in this kernel
Custom version of Blackscreen Kernel by mosimchah
Check out this thread for info:
https://forum.xda-developers.com/le-pro3/development/kernel-blackscreen-pro3-aka-zl1-x727-t3594976
Read the second and third posts on original thread for more info on the kernel settings, and features, and how to get better performance and battery life and stuff like that
Install instructions:
1. Download : Blackscreen 3 OR: Blackscreen 3.5.i (14/08/2017) OR: 3.5.i with OC (not oc'd by default)
2. Flash in twrp.
3. Reflash Root
4. Use Kernel Adiutor from playstore to change kernel settings or anything else that tickles your fancy.
AICP ROM with black screen built in:
Build 17/11/2017
https://drive.google.com/open?id=1BSB1V6f23I6xabAXXtRXqrz3ISX9pS6H
Build : 27/09/2017
https://drive.google.com/open?id=0B4k5OpXTXcS9MG5pTXlESmp4MU0
Build : 15/09/2017
https://drive.google.com/open?id=0B4k5OpXTXcS9NmZsdzE4bnI4Njg
Older:
https://drive.google.com/open?id=0B4k5OpXTXcS9aGZvLWFTQ1FKZDQ
One more kernel , onemore choose
i flashed it and camera isnt working anymore,pls fix this flashed with rr build
Can you port kernel from mi5 SlimDragons rom ?) they made good kernel )
Thanks, will try it later is it possible to port EAS?
This is the andr68rus link to various extras, included is the link to the flashable remote files
https://drive.google.com/open?id=0B-2l1xmYBAzsa0pReTA0RWZhN1E
binkaa2 said:
i flashed it and camera isnt working anymore,pls fix this flashed with rr build
Click to expand...
Click to collapse
Weird camera works fine for me but I use cm14.
Can you get a logcat?
What camera app and what happens? Just a blank screen?
infrag said:
Weird camera works fine for me but I use cm14.
Can you get a logcat?
What camera app and what happens? Just a blank screen?
Click to expand...
Click to collapse
same here , camera is not working:crying:
sky104hk said:
same here , camera is not working:crying:
Click to expand...
Click to collapse
Ok the problem occurs because both andr68rus and I have named our camera shims differently.
Also lineage has their own name for it.
In this kernel I used the Lineageos naming as I thought that was the standard. (at least I'm 90% sure I did )
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Once he has updates RR I'll upload the updated kernel and all should be good. Of course since I've wiped my phone to try this out I'll test it first with RR this time just to make sure.
infrag said:
Ok the problem occurs because both andr68rus and I have named our camera shims differently.
Also lineage has their own name for it.
In this kernel I used the Lineageos naming as I thought that was the standard. (at least I'm 90% sure I did )
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Once he has updates RR I'll upload the updated kernel and all should be good. Of course since I've wiped my phone to try this out I'll test it first with RR this time just to make sure.
Click to expand...
Click to collapse
So, will this change make stock camera fully working?
Also, regarding signal reception
at my desk the signal is weak
any idea if we could make signal reception better,
as per my experience LOS based roms or Mokee feel like does not have stock like signal reception feature,
feels bit unstable(always trying disconnecting/connecting)...
which causes the main battery drainage(dual sim, both weak signals)
infrag said:
Ok the problem occurs because both andr68rus and I have named our camera shims differently.
Also lineage has their own name for it.
In this kernel I used the Lineageos naming as I thought that was the standard. (at least I'm 90% sure I did )
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Once he has updates RR I'll upload the updated kernel and all should be good. Of course since I've wiped my phone to try this out I'll test it first with RR this time just to make sure.
Click to expand...
Click to collapse
Tks for ur hardwork, hope u can fix this on the next update bro! I really want to use the kernel, or is there any way to fix the camera problem? Also the flashlight cannot turn on, currently im usingI andr68us's DU build
Hi:
Where is the kernel?
Where can I download the kernel?
Thanks for your job
infrag said:
Thanks to @mosimchah for his hard work on Blackscreen kernel. I've just ported it to X2.
BlackScreen is meant to give you great battery life and performance (depending on how you tune it , more on that later in the second post).
Please read original thread for details.
https://forum.xda-developers.com/le-pro3/development/kernel-blackscreen-pro3-aka-zl1-x727-t3594976
Whats working:
this space intentionally left blank
Fixed Ambient Display
Added in stock LeEco charger settings to fix OTG & USB headphones.
Whats not working:
Dodgy camera as every other X2 kernel/rom atm.
I doubt IR works. Someone want to supply me a .zip with it so I can test? (I cant be bothered extracting)
Install instructions:
Download .zip
link removed while i check camera...
Flash in twrp.
Reflash Root?
Use Kernel Adiutor from playstore to change kernel settings or anything else that tickles your fancy.
Here are some of the features
f2fs not working yet as I dont care and havent turned it on.
(check out the third post on original thread for more info)
CPU:
ability to disable all input boosters
darkness governor- credit to @villarleg for porting it to our device
Lionfish governor-credit to @villarleg for porting it to our device
blue_active governor (not for the eas build)
nebula governor
wheatley governor
lionheart governor
bioshock governor
impulse governor
Alucard Hotplug driver
GPU:
Adreno boost
Adreno idler
I/O:
Improved deadline
improved cfq
bfq
sio
fiops
tripndroid
sioplus
zen
Virtual memory:
various optimizations
entropy:
some optimizations
tcp-algorithms:
bic
westwood
htcp
hstcp
vegas
scalable
lp
veno
yeah
illinois
Misc:
fsync toggle
Many more optimizations
Several wakelocks have been blocked
Added the ability to tweak the thermal throttle settings (be very careful with this)
Read the second and third posts on original thread for more info on the kernel settings, and features, and how to get better performance and battery life and stuff like that
Thanks to:
etc
Click to expand...
Click to collapse
Thanks.
Does this kernel has undervolting capability? Le max 2 has very weak battery.
infrag said:
@andr68rus please can we standardise on the lineageos naming system and both change our sources to suit?
Click to expand...
Click to collapse
Nice work, thanks I will use LOS naming system next build. I will repack kernel with my ramdisk and put link for < 05/09 RR-N.
PS. Where I can download kernel?
Hope this kernel gets fixed soon, you're doing great work on the Le Max 2, thanks for your contributions!
Also hopefully you and @andr68rus find the naming fix and that this kernel gets integrated into RR, AOKP, DU and the rest of the Nougat roms, I can see it being a great SoT fix for Nougat ROMs.
( for me this kernel is hopeless ((( my problem with camera on nougat roms seems unfixable for now (((
andr68rus said:
Nice work, thanks I will use LOS naming system next build. I will repack kernel with my ramdisk and put link for < 05/09 RR-N.
PS. Where I can download kernel?
Click to expand...
Click to collapse
Thanks.
I pulled the link as it didnt work on Cr3pts Unoffical LAOS cm14.1 either.
However it turns out he hasnt updated his libc shim name either so I've re-added the download link.
Wheres your new link so I can test on RR?
xuser_ said:
So, will this change make stock camera fully working?
Also, regarding signal reception
at my desk the signal is weak
any idea if we could make signal reception better,
as per my experience LOS based roms or Mokee feel like does not have stock like signal reception feature,
feels bit unstable(always trying disconnecting/connecting)...
which causes the main battery drainage(dual sim, both weak signals)
Click to expand...
Click to collapse
No it wont fix stock camera. I didnt imply that so...
As far as signal reception goes I dont have issues with reception.
I do see some stuff in the logs about disconnecting reconnecting and i'll probably have a look at it one of these days. Not sure IF I can do anything but I'll try.
Gnomchar said:
( for me this kernel is hopeless ((( my problem with camera on nougat roms seems unfixable for now (((
Click to expand...
Click to collapse
Whats your problem on Nougat roms?
I think I read something about focusing or something?
If so I have an idea but you will need to pull some logs while camera is semi working for you.
adb logcat > logcat.txt
adb shell dmesg > dmesg.txt
sky104hk said:
Tks for ur hardwork, hope u can fix this on the next update bro! I really want to use the kernel, or is there any way to fix the camera problem? Also the flashlight cannot turn on, currently im usingI andr68us's DU build
Click to expand...
Click to collapse
Flash andr68us's 'fixed' build. (just renamed a file basically)
His future builds should work with this.
This kernel fixes the TOUCHSCREEN FREEZING bug when playing large games by removing the CGROUPS.
Which also gives us back the RAM it ate (458mb total, now)
Same features with LahKeda's overclocked kernel.
1200mhz Overclock
Kernel Sampage Merging
zRAM
Governors
No bugs.
Source
Credits:
@psych.half for the source
@LahKeda for adding overclock and compiling
(no credit for me. I just found out cgroups is buggy but all the work was from them)
thx so much ive been waiting for this for so long
New Build
Increased zRAM from 92mb to 134mb
Properly enabled KSM (It was included in the previous one but it wasn't enabled by default)
Compressed into boot.img
Set the maximum frequency to 1200mhz by default
Set the minimum frequency to 600mhz by default
Set the governor to "ondemand" by default (If I set "performance", the frequency will only go to 1000mhz even though the script was 1200mhz. I don't know why that happens)
So which kernel is better?... Cm11's default one or this one?
Please provide the sources
RJinxed said:
Tested on SlimKat but it "should" work on cm11 since the source is the same. Try and report back if you can.
Click to expand...
Click to collapse
@RJinxed
Tried it on corpish's last cm 11 build and works fine..
Actually earlier I was using this kernel in slimkat:laugh:
Just bcz of few bug's!!! I reverted to cm 11
Anyway works on CM 11
Thanks again
New Build
Added 1250MHz overclock (no reboots, see uptime)
Enabled memory control cgroups (enabling cgroups fully was causing freeze in playing games so I tried using just the memory resource controller and it works without freezes, cheers)
P.S. Tell me if you guys want governors. I forgot to add it. Only performance is in this kernel.
Nevermind. Here is it. Same as above but with governors.
RJinxed said:
Nevermind. Here is it. Same as above but with governors.
Click to expand...
Click to collapse
Thanks mahn...
It works just fine:good:
Do you think u can upstream our kernel?
Just a thought :silly:
sm_adil said:
Thanks mahn...
It works just fine:good:
Do you think u can upstream our kernel?
Just a thought :silly:
Click to expand...
Click to collapse
To be honest, I don't know. All I do is follow lahkeda/corphish's commits in their github. I just learned to edit defconfigs and compile but aside from that, I don't really know what to do.
RJinxed said:
To be honest, I don't know. All I do is follow lahkeda/corphish's commits in their github. I just learned to edit defconfigs and compile but aside from that, I don't really know what to do.
Click to expand...
Click to collapse
Same here
I've never compiled kernel for star but for my other device I did
I'm happy to learn stuff :laugh:
Anyway I was never successful enough to upstream my kernel hope u'll be able to do it in future:fingers-crossed:
BTW thanks for the kernel
sm_adil said:
Thanks mahn...
It works just fine:good:
Do you think u can upstream our kernel?
Just a thought :silly:
Click to expand...
Click to collapse
upstream the kernel. OMG I tried but it's a nightmare, real nightmare
Hey buddy, I have installed CM 14.1 custom rom. Will this kernel work?
y2knarayan said:
Hey buddy, I have installed CM 14.1 custom rom. Will this kernel work?
Click to expand...
Click to collapse
No, this is only compatible for kitkat roms. Also, don't use cm14.1 yet since it's still really buggy.
RJinxed said:
No, this is only compatible for kitkat roms. Also, don't use cm14.1 yet since it's still really buggy.
Click to expand...
Click to collapse
Can u suggest the best custom rom for this phone?
EDITED: Freezes at 1.3GHz after over 30 hours. If you still wanna try it, I'll keep this here. This build has lowered voltages.
I don't know if I can find a way to get it to work but I'll try anyway.
Final Build
Lowered voltages (Battery life increased)
Updated lowmemorykiller driver (cherry picked from this source)
Unfortunately, 1300MHz was unstable no matter what. Tried different sources, adjusting voltages etc but it seems to be the limit for this device. Also ive noticed some weird artifacts whenever I use it (Which proves that it is unstable since in PC overclocking as well, the cue for unstable overclocking is artifacts)
TLDR; 1250MHz is the farthest we can have.
Deleted. I'm losing my mind.
Try this guys. 1292MHz, Hopefully this would be the last build, After almost 4 days constant, still no reboots.
Edit #1: DO NOT set the governor to ONDEMAND. Performance is perfectly stable but when I set the governor to ondemand, after a couple of hours it rebooted. I don't think this is coincidence with over 100 hours of uptime.
Edit #2: Reuploaded the kernel but this time, performance is the only governor option since it's the only stable one. If you want governors, download the 1250MHz version.
how to overclock
hey buddy,
I have a question, I have rooted my phone it is running android version 4.1.2 and i want to overclock my phone. Can i use this kernel in my existing os version or i have to install cm11 and then overclock it. Please tell me in detail, i am new in rooting and flashing and all that. Please explain in as much detail as possible. Hope a response from you.
Thank u
My model no. GT-S5282
This kernel is the result of a common work with @Leicxan. It can only be used on H990 and was successfully on single sim AND double sim variants. D.O.T.S. kernel is :
- Dirty Santa rooted
- Optimized
- Tweaked
- Stock based
Caution
Nor @Leicxan nor I are responsible for any damage caused to your phone. Any of the action you'll make to flash a kernel theorically voids your warranty. If don't accept any risk, then keep your stock phone
Content
- Based on v10g official LGE sources
- Compiled with UBERTC 7.x Linaro 7.2.1 (since V1.4)
- Dirty Santa root as implemented by @emdroidle
- CPU Governors : performance, powersave, userspace, ondemand, conservative, interactive, darkness, nightmare, zzmove, blu_active, elementalx, chill, dancedance. Default is interactive.
- I/O Schedulers : noop, deadline, cfq, fiops, sio, bfq, zen, maple. Default is zen.
- TCP congestion protocols : htcp, cubic, bic, reno, westwood. Default is westwood.
- Adreno idler
- Adrenoboost
- Exfat Support
- KCAL
- RCTD removed
- Wakelocks management
- Various small optimizations and tweaks
History
V1.0 [11/10] : original version
V1.1 [11/22] : CPU frequency hard limit (for battery drain improvement) and various minor fixes
V1.2 [11/27] : CPU frequency fix, exfat from samsung's open source module, LGE adaptive readahead
V1.3 [12/11] : Upstream Kernel to 3.18.86 thanks to @thirdzcee. Disabled LGE's rctd, ccmd and triton. Disabled some debug configuration. Note : Windows Defender can detect the archive as a Fuerboos trojan, this is a false positive.
V1.4 [01/04] : Fix for kernel crash when using pptp vpn. Upstream Kernel to 3.18.90.
Installation instructions
Follow the instructions provided by @emdroidle here : https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
At step 16, instead of typing fastboot reboot, just unplug the usb cable, remove battery, wait 5 sec, put the battery back and reboot the phone. This should limit the risk of static screen at reboot.
Once the kernel installed, update your phone to the latest KDZ for your region using KDZ Writer : https://forum.xda-developers.com/v20/development/tool-kdz-writer-t3649818
Known bugs
Some users reported issues with SD cards formated with exFat. This is not a general issue. The root cause is not clear (linked to the way the SD card is formated ?).
How to report a problem
It is very important to provide as many details as possible when you report a problem. It means providing :
- the model of your phone
- the version of the kernel and of the KDZ you updated to
- a precise description of the problem and of the circumstances
- logs (logcat & dmesg) : https://forum.xda-developers.com/showthread.php?t=2185929
Q&A
Before asking please :
- read the posts in this thread. The "Search Thread" box is your friend.
- have a look at @xdav20's H990DS Info Bank thread which is full of usefull information : https://forum.xda-developers.com/v20/how-to/h990ds-info-bank-t3703736"
Thanks
@emdroidle for his implementation of Bad Santa on H990
@USA-RedDragon for his werewolf kernel that was inspiring
Sources
https://github.com/guaibao1101/h990x-msm-3.18/tree/DOTS_v1.3
Downloads
Can we flash this over an existing kernel via TWRP if we have already rooted?
p7810456 said:
Can we flash this over an existing kernel via TWRP if we have already rooted?
Click to expand...
Click to collapse
Normally yes.. But if there is a problem, you'll have to restart all over, so make a backup of your phone, just in case..
It would be nice if this can be crossed over to H918.
First of all, just want to say thank you to @jahlex and @Leicxan for bringing the long awaited kernel with literally everything I could ask for to our devices.
Upon first install by flashing in TWRP, wiping dalvik/cache and rebooting, my phone goes to the LG screen, then black screens and I get a kernel crash screen that I've taken a photo of here
Any ideas what's causing it? My system version is in my signature. I'm really keen to get this working! For now I've restored my TWRP backup I did before flashing, back to 0.2.3b
Update: Even after the TWRP restore I was still getting the same problem. Immediately I thought it might be a Magisk problem as that's the only other thing I updated before rebooting. It appears I was correct. I used KDZWriter to re-flash the boot & system partitions of my phone (since Magisk modifies the boot image) and it immediately booted okay with my TWRP backup. Booted back into recovery, flashed the kernel as well as a previous Magisk version (14.0 not 14.2) and my other /system apps & mods, wiped cache, rebooted and sat on the LG screen for a while. Then booted into the OS okay. Glad it worked out and I'm keen to see how this kernel goes.
On a sidenote, do you have any plans to bring it to a more up to date version of the linux base kernel?
jahlex said:
Normally yes.. But if there is a problem, you'll have to restart all over, so make a backup of your phone, just in case..
Click to expand...
Click to collapse
This worked for me! Thanks a lot!
iDefalt said:
First of all, just want to say thank you to @jahlex and @Leicxan for bringing the long awaited kernel with literally everything I could ask for to our devices.
Upon first install by flashing in TWRP, wiping dalvik/cache and rebooting, my phone goes to the LG screen, then black screens and I get a kernel crash screen that I've taken a photo of here
Any ideas what's causing it? My system version is in my signature. I'm really keen to get this working! For now I've restored my TWRP backup I did before flashing, back to 0.2.3b
Update: Even after the TWRP restore I was still getting the same problem. Immediately I thought it might be a Magisk problem as that's the only other thing I updated before rebooting. It appears I was correct. I used KDZWriter to re-flash the boot & system partitions of my phone (since Magisk modifies the boot image) and it immediately booted okay with my TWRP backup. Booted back into recovery, flashed the kernel as well as a previous Magisk version (14.0 not 14.2) and my other /system apps & mods, wiped cache, rebooted and sat on the LG screen for a while. Then booted into the OS okay. Glad it worked out and I'm keen to see how this kernel goes.
On a sidenote, do you have any plans to bring it to a more up to date version of the linux base kernel?
Click to expand...
Click to collapse
Magisk 14.2 and 14.3 are beta version, I tried magisk 14.3 but my h990n always boot into bootloader interface..
So just stay with magisk 14, it doesn't have any issue.
For the Linux version, it will take tons of time to do this even we just upstream our kernel (from 3.18.31 to 3.18.79)
Sent from my OnePlus3T using XDA Labs
Leicxan said:
Magisk 14.2 and 14.3 are beta version, I tried magisk 14.3 but my h990n always boot into bootloader interface..
So just stay with magisk 14, it doesn't have any issue.
For the Linux version, it will take tons of time to do this even we just upstream our kernel (from 3.18.31 to 3.18.79)
Click to expand...
Click to collapse
Yeah I don't know why 14.0 prompted me to update to a beta version. I know 14.3 added something to do with supporting LG devices better, maybe that broke something. Otherwise I'm quite happy with how things are going ?
And yeah I'm somewhat familiar with how long kernel related things can take, it was more of a question if anything.
I've just installed it now, it works perfectly for now much more reactive i've impression Thank you!!
storm68 said:
It would be nice if this can be crossed over to H918.
Click to expand...
Click to collapse
That would be awesome!!!!!!
A million thanka for this for jahlex and lexican
Is the kernel in the downloads in the OP is the same version as this one : DirtySanta-h990-1.2-u721-v10g that was posted back in rooting thread
Or is it newer ?
storm68 said:
It would be nice if this can be crossed over to H918.
Click to expand...
Click to collapse
nymikey said:
That would be awesome!!!!!!
Click to expand...
Click to collapse
We only deal with H990 here guys. Thanks.
shouk_1987 said:
A million thanka for this for jahlex and lexican
Is the kernel in the downloads in the OP is the same version as this one : DirtySanta-h990-1.2-u721-v10g that was posted back in rooting thread
Or is it newer ?
Click to expand...
Click to collapse
This is major evolution of this kernel. DirtySanta-h990-1.2-u721-v10g was basically the stock v10g kernel with Dirty Santa root.
Before all, thank you so much guys, that's a great work
For some opinions i have many friends that buy h990ds last year and me too, we concluded if tha kernel was more optimized battery side was more effective than performances, and will be great that CPU and GPU clocks and voltages will be more unlocked if you can do that , thank you again.
great kernel thank you @jahlex :good: and @Leicxan :good: it works perfectly
zinou213 said:
if tha kernel was more optimized battery side was more effective than performances, and will be great that CPU and GPU clocks and voltages will be more unlocked if you can do that , thank you again.
Click to expand...
Click to collapse
They've already enabled some overcooked frequencies with this, as seen in their Github commits. If it's battery you're looking for, install the AKT Profiles from the thread, and then choose a balanced or battery saving profile. Since installing those and this kernel, I'm regularly seeing 5-7 hours of screen time.
On a side note @jahlex or @Leicxan if you're looking for a beta tester, feedback, or Guinea pig to help out (that isn't actually building the kernel, that's above my ability to simply modify individual files) I'd love to help wherever possible
Been doing the whole TWRP/Flashing/Kernel/ROM thing since I got my G3 way back in the day.
zinou213 said:
Before all, thank you so much guys, that's a great work
For some opinions i have many friends that buy h990ds last year and me too, we concluded if tha kernel was more optimized battery side was more effective than performances, and will be great that CPU and GPU clocks and voltages will be more unlocked if you can do that , thank you again.
Click to expand...
Click to collapse
As @iDefalt said, we already enabled higher max frequency / voltage for both CPU & GPU. We won't go higher because the result would be high risks of unstability and overheating. If you want performance and do not care about battery life, simply switch to performance governor for both CPU & GPU. We use interactive CPU governor by default because it is a good choice considering balance performance / battery life (nightmare & darkness are good choices too). You have plenty of apps to do that, example : https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor.
iDefalt said:
They've already enabled some overcooked frequencies with this, as seen in their Github commits. If it's battery you're looking for, install the AKT Profiles from the thread, and then choose a balanced or battery saving profile. Since installing those and this kernel, I'm regularly seeing 5-7 hours of screen time.
On a side note @jahlex or @Leicxan if you're looking for a beta tester, feedback, or Guinea pig to help out (that isn't actually building the kernel, that's above my ability to simply modify individual files) I'd love to help wherever possible
Been doing the whole TWRP/Flashing/Kernel/ROM thing since I got my G3 way back in the day.
Click to expand...
Click to collapse
OK buddy. We'll remember.
Thanks!!! And with KCAL, it's perfect! :victory:
Huge thanks guys! Everything works great, even video recording. Great work!!!
@jahlex @Leicxan
Thank you for the release. I will report back any noteworthy issues.
Please forgive me if the following comment may deemed as a thread hijacking. I would be happy to remove it on your request.
I have just started a new thread in time for H990DS users and others, with useful information and tutorials that would potentially answer the most commonly asked questions or the issues sooner or later you would run into.
Kcal is so nice to finally have, thank you c: