Database Info

[KERNEL AOSP] Thalamus 2.6.35.14 mod

This kernel uses AOSP camera driver so it's most likely compatible only with Redux 2.0 (tested) and Oxygen (not tested)
Before you do anything- make a backup
It's my lame attempt (I'm a modder, not a dev) to get more battery life without loosing stability of original kernel.
Kernel is based on current thalamus 2.6.35.14 sources
What is changed (mod8):
-Vdd levels sysfs interface is back, this time seems to be stable
-default voltages for CPU clocks <700 MHz are lowered a bit- keep this in mind when playing with UV
-headphone volume boosted a little- needs to be tested
-more optimized compilation- kernel should use CPU in more efficient way (and kernel is 500 bytes smaller )
-big thanks to paul8944 for testing
What is changed (mod7):
-removed sysfs Vdd levels interface- it seems that it was responsible for instability and FC's in mod6
-USB transfer speed is higher (was ~800kB/s, now ~2MB/s for write operations)
What is changed (mod6):
-added sysfs Vdd levels interface- VDD_MIN is set to 800 mV, VDD_MAX to 1300 mV, step is 25 mV (this works fine with IncrediControl)
-available governors: ondemand, powersave, conservative, performance and smartassV2
-conservative governor is tweaked a little (should be a little less conservative)
-USB transfer speed tweak- needs testing
-other fixes
What is changed (mod5)
-lowered minimum cpu clock to 128 MHz
-more clock speeds are available up to 1113 MHz
-added smartass and smartassV2 governors
-tinyRCU replaced with preemtive tinyRCU
-enabled call recording (not tested)
-many other fixes and improvements mainly form ch33kybutt's and elevendroids' sources
Note about smartass governor- after longer period of inactivity you have to press Power button for about 2 seconds to wake up the phone
Installation:
-make a nandroid backup (just in case)
-put zip on SD card and flash in recovery, I suggest also wiping dalvik-cache (just in case)
Download:
thalamus 2.6.35.14 mod8
md5: E526C99D4326F5B11D02DB60FEFA169F
Previous versions:
thalamus 2.6.35.14 mod7 (description above), md5: 7AB623BCC5E28D9BC8A012EDD9E9BBC7
Mod6 is not available due to instability
thalamus 2.6.35.14 mod5 (description above), md5: 7DC3E94E56FD00C49FEB5C713033DE33
thalamus 2.6.35.14 mod4 (128 MHz min cpu clock, default governors set, non-preemptive TinyRCU) md5: E7DD4637D8838A6E1A64E763C8A4D549
Kernel sources available on Github

I'll give it a try, seems good. I have one question and one suggestion:
the question is: what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
and the suggestion is to add the syscf interface for being able to change the voltages. It could save some battery life if our Desire stands it (mine does even at 800 mV )

i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.

blackhawk_LA said:
what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
Click to expand...
Click to collapse
I was not satisfied with default cpu clock table
-128 MHz uses ~20 mA of current less than 245- it's about 10% saving for iddle not locked phone
-for me 691 MHz max clock is really enough for my needs, it was not available in stock version
-more speeds make governors able to better match cpu speed (and save some juice)
-there are some performance fans so why not enable also 1113?
soronk said:
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
Click to expand...
Click to collapse
Looking what caused this, I'm not sure if it's wlan driver or preemtive tinyRCU (not present in mod4)
Download temporarily removed
EDIT:
It was wlan driver.
Corrected, reuploaded package

gen_scheisskopf said:
EDIT:
It was wlan driver.
Corrected, reuploaded package
Click to expand...
Click to collapse
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium

soronk said:
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Me too.....
Sent from my HTC Desire using XDA App

Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?

Tones1971 said:
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Click to expand...
Click to collapse
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not

gen_scheisskopf said:
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
Click to expand...
Click to collapse
Yes it work! But without camera. MIUI needs the 720p camera drivers.

Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.

h_misc said:
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
Click to expand...
Click to collapse
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Sent from my HTC Desire using Tapatalk

gen_scheisskopf said:
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Click to expand...
Click to collapse
Too bad, with screen off laggy behaviour when raising the CPU-clock is exactly what I want.
With the conservative governor reaction to the power button is instant, smartass was really irritating me when pushing the power button the days I tried it.
I used setcpu with a screen off profile with conservative and ondemand with screen on (on gingervillain) which was just perfect.

I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.

blackhawk_LA said:
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
Click to expand...
Click to collapse
I use the FTP server with screen off, a script that functions as webserver to name two examples. So I need it to be possible for the CPU to be at more than minimal speed.

Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass

blackhawk_LA said:
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
Click to expand...
Click to collapse
You're probably right, but isn't tweaking for 1% battery saving part of the fun?

So which governors do you think should be in kernel? I don't want to include all available
Sent from my HTC Desire using Tapatalk

gen_scheisskopf said:
So which governors do you think should be in kernel? I don't want to include all available
Click to expand...
Click to collapse
The ones I like to use are ondemand and conservative.
You should include what you like off course

h_misc said:
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
Click to expand...
Click to collapse
I couldn't agree more
I think that the most used governors are conservative, ondemand, interactive and smartass (don't know about the new governos: smartass2 and others)
But for me, having ondemand it's enough

blackhawk_LA said:
But for me, having ondemand it's enough
Click to expand...
Click to collapse
Do you want a dedicated build?
So as for now governors will be ondemand, performance, conservative, powersave (even more conservative than conservative ) and smartass- more likely v2.
I plan to release mod6 when I'll implement SVS

[Q] Governors & I/O schedulers?

Please forgive me for asking, if this has already been answered. Question for the Devs... Will any future releases (kernel only, or ROM) include a wider selection of governors and i/o schedulers, or is this device limited to the ones already available for some reason?
Coming over from HTC Glacier and Doubleshot, there were more choices than I knew what to do with. This is my first Samsung device.
Not that I'm complaining, I've found a combination that works good for me. I just wanted to know.
By the way - you guys are doing some great work over here. I'm loving this phone. Thanks!

This would be done on the kernel level and it is certainly possible to add more options but doing so can make things less stable.
If there is something you think may work better you could ask a dev if implementing has been tried and what the result is otherwise the main kernel source is available on github and there are many guides to build yourself and test
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
This would be done on the kernel level and it is certainly possible to add more options but doing so can make things less stable.
If there is something you think may work better you could ask a dev if implementing has been tried and what the result is otherwise the main kernel source is available on github and there are many guides to build yourself and test
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm sure the devs have sound reasoning behind their choices. I was just curious to find out if it was something device specific, as opposed to dev preference. I don't know that I would go so far, as to tamper with the kernel source myself. I don't have those skills yet. I may look into that in the future. I'm always willing to learn.

jadrt09 said:
Please forgive me for asking, if this has already been answered. Question for the Devs... Will any future releases (kernel only, or ROM) include a wider selection of governors and i/o schedulers, or is this device limited to the ones already available for some reason?
Coming over from HTC Glacier and Doubleshot, there were more choices than I knew what to do with. This is my first Samsung device.
Not that I'm complaining, I've found a combination that works good for me. I just wanted to know.
By the way - you guys are doing some great work over here. I'm loving this phone. Thanks!
Click to expand...
Click to collapse
Hit the app store and grab CPU Tuner, you might find it's got what you need.

yohan4ws said:
Hit the app store and grab CPU Tuner, you might find it's got what you need.
Click to expand...
Click to collapse
Thanks, I'll check that one out but I believe that apps like that will only allow you to select from the governors and schedulers that are available in the kernel itself - not implement one that isn't there. I'd like to try out intellidemand, or smartassV2 with this device.
Right now, I'm using the interactive governor & sio. Then using SetCPU with profiles for screen-off, screen-on, and charging. This is kind of giving me the results I wanted. Sort of gives me an interactiveX, I guess? SetCPU doesn't show me both cores, so I really don't know. Also have tried Kernel Tuner and Trickster with mixed results.

jadrt09 said:
Thanks, I'll check that one out but I believe that apps like that will only allow you to select from the governors and schedulers that are available in the kernel itself - not implement one that isn't there. I'd like to try out intellidemand, or smartassV2 with this device.
Right now, I'm using the interactive governor & sio. Then using SetCPU with profiles for screen-off, screen-on, and charging. This is kind of giving me the results I wanted. Sort of gives me an interactiveX, I guess? SetCPU doesn't show me both cores, so I really don't know. Also have tried Kernel Tuner and Trickster with mixed results.
Click to expand...
Click to collapse
Just downloaded CPU Tuner. This appears to be a better alternative to the other ones I've tried. I can get what I want without trying to mess with the kernel. Gonna run the "Sophisticated" config + Performance profile for a while and see how it goes. Thanks! :good:

jadrt09 said:
Please forgive me for asking, if this has already been answered. Question for the Devs... Will any future releases (kernel only, or ROM) include a wider selection of governors and i/o schedulers, or is this device limited to the ones already available for some reason?
Coming over from HTC Glacier and Doubleshot, there were more choices than I knew what to do with. This is my first Samsung device.
Not that I'm complaining, I've found a combination that works good for me. I just wanted to know.
By the way - you guys are doing some great work over here. I'm loving this phone. Thanks!
Click to expand...
Click to collapse
my roms have more freedom of the kernel with this...current governors in my builds are: conservative, ondemand, userspace, powersave, interactive, and performance. Current I/O schedulers are noop, deadline, row, cfq, and sio. i will be exapanding on this soon but sio and interactive or sio and ondemand have given the bast stability for me.

REV3NT3CH said:
my roms have more freedom of the kernel with this...current governors in my builds are: conservative, ondemand, userspace, powersave, interactive, and performance. Current I/O schedulers are noop, deadline, row, cfq, and sio. i will be exapanding on this soon but sio and interactive or sio and ondemand have given the bast stability for me.
Click to expand...
Click to collapse
I've been running your Carbon ROM for a little while and I've been pretty pleased with it. I've settled on the interactive and sio combination but I wanted to have a little more control. Most of the time I just text and do a little web browsing, so I want to extend battery life. But I have access to a lot of wi-fi hotspots, so then I can plug in for some gaming or Netflix. It's nice to have the performance amped up then. I seemed to have good results with intellidemand and smartass variations on my other phones.
I appreciate your work, thanks!

jadrt09 said:
I've been running your Carbon ROM for a little while and I've been pretty pleased with it. I've settled on the interactive and sio combination but I wanted to have a little more control. Most of the time I just text and do a little web browsing, so I want to extend battery life. But I have access to a lot of wi-fi hotspots, so then I can plug in for some gaming or Netflix. It's nice to have the performance amped up then. I seemed to have good results with intellidemand and smartass variations on my other phones.
I appreciate your work, thanks!
Click to expand...
Click to collapse
your very welcome...as ive stated before i will be adding some more here soon. i have a couple of new rom builds im working on and an update to another...i definitely need to work on the kernel as ive done little patches here and there but nothing too big....think within the next few weeks ill do a big update to it and update all my roms with it

Perhaps you could release a flashable kernel for people on cm?
Sent from my SGH-T699 using Tapatalk

REV3NT3CH said:
my roms have more freedom of the kernel with this...current governors in my builds are: conservative, ondemand, userspace, powersave, interactive, and performance. Current I/O schedulers are noop, deadline, row, cfq, and sio. i will be exapanding on this soon but sio and interactive or sio and ondemand have given the bast stability for me.
Click to expand...
Click to collapse
Errr What advantages are there from sio over the other i/o schedulers. That's the only addition between your list and what we are currently enabling.

Magamo said:
Errr What advantages are there from sio over the other i/o schedulers. That's the only addition between your list and what we are currently enabling.
Click to expand...
Click to collapse
Simple I/O (sio) scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.

REV3NT3CH said:
Simple I/O (sio) scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
Click to expand...
Click to collapse
I notice a difference in performance when I change governors but I can't say that I notice a difference at all, when changing i/o schedulers. My understanding is that certain combinations are supposed to work better together. I just remember that devs of certain mods I've used had a preference for sio o over the others. Not sure why, but it worked, so I've stuck with it...

[KERNEL][SM-T520][TW][CM] LibidinosoSC kernel v2-Lots of Stuff

Hello.
Since kernel development is pretty non existent for picassowifi I compiled one.
Version 0.1:
Updated deadline IO scheduler (new default)
Activated a bunch of tcp congestion algorithms (westwood new default)
Tweaks in interactive. Added performance governor
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE set to 0 in config so wifi works without changing build prop.
Version 0.2:
Rebased to source for version T520UEUAND1 from may... Camera works!!
Version1.0: (
Grabbed a bunch of commits from here SkyHigh Galaxy Tab S Kernel
Features from there:
CPU
CPU max frequency A15 cores = 2100 MHz (stock/default = 1900 MHz)
CPU min frequency A7 cores = 200 MHz (stock/default = 500 MHz)
Multi-core power saving control (sched_mc_power_savings)
CPU VOLT
Voltage control for:
big cores
LITTLE cores​
GOV
CPU governor
interactive (default)
on-demand
userspace​
CPU governor tunables
MEMORY
I/O Schedulers
BFQ (default)
DEADLINE (tweaked)
CFQ
NOOP
FIOPS​
General IO tuneable
Int storage scheduler
Int storage read-ahead
Kernel SamePage Merging (KSM)
Pages to Scan
Scan delay interval​
Virtual memory tuneables
GPU
GPU max frequency = 667 MHz (stock/default = 480 MHz)
GPU min frequency = 100 MHz (stock/default = 177 MHz)
GPU voltage control
POWER SUSPEND
PowerSuspend
Autosleep_hook
Userspace_trigger
DisplayPanel_hook
[*]PowerSuspend State (onlt with Userspace_trigger)
Hybrid_hook (default)​
Dynamic management of dirty page writebacks
Adaptive VFS Cache Pressure on Suspend / Resume (1024 kB for 16 GB partition)
ADVANCED
Low Memory Killer (OOM LMK)
Management of not killable processes whitelist
system apps
user apps​
entropy
Gentle fair sleepers control
randomize_va_space control
THERMAL
CPU thermal control
GPU thermal control
Memory interface thermal control
AUDIO
* WolfsonMicro WM5102 sound control by AndreiLux
Mono output
HeadPhone equalizer settings
BATTERY
Unstable power detection
AC mains
Standard downstream port
Dedicated charging port
Charging downstream port
Accessory charger adapter
Miscellaneous charging
MHL power
Battery Scaling Calibration (fuel-gauge chip reset)
Click to expand...
Click to collapse
Most changes are the same... for more specific changes check my Github
flash in recovery
Make a backup before flashing.
FYI: I'm by no means a kernel developer, I'm just compiling because no one else is doing it

Reserved cause yeah

Just curious (and to help out others) - stock based, or CM?
Good work tho! Glad to see some kernel development

Stock based
Sent from my Nexus 5 using Tapatalk

Glad to hear this!
---------- Post added at 12:42 AM ---------- Previous post was at 12:30 AM ----------
Do you have the ability to make one for SM-P900?

canezila said:
Glad to hear this!
---------- Post added at 12:42 AM ---------- Previous post was at 12:30 AM ----------
Do you have the ability to make one for SM-P900?
Click to expand...
Click to collapse
Sorry but no...I don't have it and I don't have much time other than weekends
Enviado desde mi SM-T520 mediante Tapatalk

How about for the t320?

LibiSC said:
Hello.
Since kernel development is pretty non existent for picassowifi I compiled one.
Version 0.1:
Updated deadline IO scheduler (new default)
Activated a bunch of tcp congestion algorithms (westwood new default)
Tweaks in interactive. Added performance governor
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE set to 0 in config so wifi works without changing build prop.
to do:
check the thermal driver
check hotplug driver
port stuff from mainstream
bugs:
Samsung camera app force closing... I hate Samsung
boot.img attached. You can use flashify, adb or Odin to flash
Make a backup before flashing.
FYI: I'm by no means a kernel developer, I'm just compiling because no one else is doing it
Click to expand...
Click to collapse
Could u link any guide or the method you use for custom kernels?
The camera is a pain for both costom roms and kernels.

Just follow the txt that comes with the source... The problem is just with Samsung camera app.... Other camera apps work just fine
Sent from my Nexus 5 using Tapatalk

CodeIndia said:
Could u link any guide or the method you use for custom kernels?
The camera is a pain for both costom roms and kernels.
Click to expand...
Click to collapse
New version... Camera works!! test please

Which one of these is it?
bootTest.img
boot02.img
I tried boot02.img and it doesn't fix camera and makes chrome and play store crash.

Boot02...i think your room has to end in nd1
Sent from my Nexus 5 using Tapatalk

Shaheer said:
Which one of these is it?
bootTest.img
boot02.img
I tried boot02.img and it doesn't fix camera and makes chrome and play store crash.
Click to expand...
Click to collapse
^
Sent from my Nexus 5 using Tapatalk

LibiSC said:
Boot02...i think your room has to end in nd1
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh lol. I was trying it on my CM port. Trying to get camera to work on there but no luck so far.

Shaheer said:
Oh lol. I was trying it on my CM port. Trying to get camera to work on there but no luck so far.
Click to expand...
Click to collapse
Try using the binaries from a ...nd1 rom in your aosp or cm rom
Sent from my Nexus 5 using Tapatalk

LibiSC said:
Try using the binaries from a ...nd1 rom in your aosp or cm rom
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Camera binaries?

Also tried this boot2 on the cm ROM, but kept fc com.android.phone

Cryonic90 said:
Also tried this boot2 on the cm ROM, but kept fc com.android.phone
Click to expand...
Click to collapse
Same

Shaheer said:
Camera binaries?
Click to expand...
Click to collapse
Makes sense cause it's not for cm roms it's for stock roms...
With binaries I meant rom binaries and libs... AFAIK aosp needs proprietary libs
Sent from my Nexus 5 using Tapatalk

New version up... big jump to version 1.0... thanks @UpInTheAir for his work and all the people that collaborate with him.
Cpu max set 2000 mhz min set to 250 mhz
Gpu max set to 533 mhz min set to 100mhz
You can try make them go higher but it's pretty unstable from there.

[KERNEL][OP3/3T][LOS15.1][AOSPA][Synapse] White Wolf Kernel (30/11/2018)

[url=https://postimages.org/]
[/URL]​
This is a home of new re branded yarpiin kernel for Lineage OS based roms.
Would like to thank to all devs that work has been used to create this kernel.​
SO WE STARTING A LIST:
all CREDITS goes to:
@Grarak
@Mahdi786
@Lord Boeffla
@franciscofranco
@ Despair Factor
@ak
@ZaneZam
@varun.chitre15
@flar2
@arter97
@TheCrazyLex
@Sultanxda
@eng.stk
@neobuddy89
@Tkkg1994
@frap129
@jcadduono
@savoca
@yank-lu.555
@Dorimanx
@acuicultor
@Alucard24
@bbedward
@nathanchance
@Maxwen
@mostafaz
@joshuous
@faux123
@rainforce279
@Paranoid Android Team
and all others devs that make our lives easier.
Special thanx for @urgali , @Sungfive and @Duncan1982 for testing .
@Cybertron™ for new thread and signature images.
@Saber for his superb thread with all detailed kernel stuff.
Short Feature list:
Basic Governors plus:
Darkness, Nightmare, Alucard, Impulse, Blu Active
Overclocked both clusters
Adjustable thermal driver
Power Efficient Workqueues
State Notifier Driver
I/o schedulers: fiops, sio, zen, maple
Adrenoboost
Adreno Idler
Simple gpu algorithm
Backlight dimmer
Kacal control
Power Suspend driver
USB Fast Charge
Eagle DTS driver
Built in Busybox
Uses a simple free and user friendly application called Synapse by @AndreiLux for configuration purposes(slightly adding more functionality)
Synapse is included in zip and flashed by default as a system app.​
Synapse is based on new UKM - Lite version. It does contain less settings than standard version for less advanced users. For those who wish to use full power of Synapse additional UKM zip have to be flashed after Kernel. ​
UKM Full flashable zip download link​
https://www.androidfilehost.com/?w=files&flid=154993​
Flashing instructions
1. Flash in recovery no black magic
3. If missing tunables for governors set SElinux to permissive​
Compatibility list:
LOS Kernel have been tested with official Lineage OS 15.1
PA Test Kernel works with AOSPA and its based on Paranoid Android Kernel Source and all credits belong to Paranoid Android Team.
And Finaly Download Link:
WHITE WOLF LOS 15.1
https://www.androidfilehost.com/?w=files&flid=253747]
WHITE WOLF AOSPA test kernel (Paranoid Android )
https://www.androidfilehost.com/?w=files&flid=186508
LOS Source
https://github.com/yarpiin/White-Wolf-OP3-LOS
PA Source
https://github.com/yarpiin/White-Wolf-OP3-PA​
If You like my work buy me a beer ​https://www.paypal.me/yarpiin​
XDA:DevDB Information
White Wolf Kernel, Kernel for the OnePlus 3
Contributors
yarpiin
Source Code: https://github.com/yarpiin
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: WHITE.WOLF.OP3.XXX
Stable Release Date: 2017-05-30
Created 2016-12-22
Last Updated 2018-11-30

WHITE.WOLF.OP3.LOS.15.1 - Changelog
https://github.com/yarpiin/White-Wolf-OP3-LOS/blob/master/changelog.txt
WHITE.WOLF.OP3.PA - Changelog
[url]https://github.com/yarpiin/White-Wolf-OP3-PA/blob/nougat-mr2/changelog.txt[/URL]

Hall Of Fame
This is a list of people who contributed donations to this project or helped in it
Helpers​
- @urgali
- @Sungfive
- @Duncan1982
- @Cybertron™ - Thread and signature images
Donators​
- @urgali
- @A Sad Napkin
- @real76
- Unknown memeber named Amir
- @ctakah27
- SB
Thank you a lot !!!​
Signature Image Link​

thanks!
I am downloading

Thanks man 5 stars from me

Thanks ! Wait for OxygenOS Version
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Wow awesome thx. Running very nice with my suicide squad rom. Awesome fast and smooth. Your kernel has potential keep it up

Flashed to XenonHD.
Very smooth!

Great kernel.
Keep it up.

I build a kernel and thanks for posting source I see a few govs I will add to my list
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

ZeNiXxX said:
Wow awesome thx. Running very nice with my suicide squad rom. Awesome fast and smooth. Your kernel has potential keep it up
Click to expand...
Click to collapse
I'm bout flash on same.rom, lol

Uhh, something to play with on Nougat!
Good stuff

@yarpiin Have You plans to implement OC?

rafciowis1999 said:
@yarpiin Have You plans to implement OC?
Click to expand...
Click to collapse
Hi sorry but no or maybe no :silly: i was thinkin about it but im not a big fan of OC i can OC my PC ( actually higly OCed ) but not mobile chip i think we have enough of cpu power but maybe in future i will change my mind - just for now dont see any strong reason to do it
Sent from my ONEPLUS A3003 using XDA Labs

yarpiin said:
Hi sorry but no or maybe no :silly: i was thinkin about it but im not a big fan of OC i can OC my PC ( actually higly OCed ) but not mobile chip i think we have enough of cpu power but maybe in future i will change my mind - just for now dont see any strong reason to do it
Click to expand...
Click to collapse
Good reason.
I think OC will be good but not as default.
Backporting i/o schedulers and governors from newest linux will be great too (mostly cfq, deadline and interactive).

Only request would be sound controls if possible to add from ex kernel or wherever...? Running alacurd and hotplug and it's buttery smooth and awesome battery! Good job with this bro
---------- Post added at 12:33 AM ---------- Previous post was at 12:33 AM ----------
Will have any chance to make profiles for synapse?

yarpiin said:
Hi sorry but no or maybe no :silly: i was thinkin about it but im not a big fan of OC i can OC my PC ( actually higly OCed ) but not mobile chip i think we have enough of cpu power but maybe in future i will change my mind - just for now dont see any strong reason to do it
Sent from my ONEPLUS A3003 using XDA Labs
Click to expand...
Click to collapse
The only OC that is useful for this phone is upping the big cores to 2.26ghz and the little to 1.72ghz. The voltage stays the same so you get a minor speed bump but power draw is identical. This in turn gives slightly better battery life because the phone can go back to idle slightly quicker. Anything higher starts causing the phone to thermal throttle much quicker, well in my case that is.
Also, I see you have implemented hotplugging, as mentioned in many different kernel threads for multiple devices that use big.LITTLE (OP3, S6, etc.) This is uncessary and causes more battery drain while also reducing performance because these cores were designed to go idle when not in use consuming nearly zero energy. Hotplugging makes these cores jump between on and off all the time and lower and higher frequencies because of the way big.LITTLE works which causes massive microstutter and also much higher battery drain.
In the good old S6 days a couple devs tried to implement it but it never worked no matter what they tried. Sultan, one our devs here, makes an amazing custom kernel/ROM combination. He had implemented hotplugging when he first released the kernel but it turned out to not fully work properly and caused extra battery drain and microstutters. He removed it and it fixed all the issues.
Edit: haven't used the kernel yet because cm14.1 is a bugfest so this is just speculation, you could have added a little magic and it performs super well.

yung40oz84 said:
I'm bout flash on same.rom, lol
Click to expand...
Click to collapse
Suicide squad rom?

crzykiller said:
The only OC that is useful for this phone is upping the big cores to 2.26ghz and the little to 1.72ghz. The voltage stays the same so you get a minor speed bump but power draw is identical. This in turn gives slightly better battery life because the phone can go back to idle slightly quicker. Anything higher starts causing the phone to thermal throttle much quicker, well in my case that is.
Also, I see you have implemented hotplugging, as mentioned in many different kernel threads for multiple devices that use big.LITTLE (OP3, S6, etc.) This is uncessary and causes more battery drain while also reducing performance because these cores were designed to go idle when not in use consuming nearly zero energy. Hotplugging makes these cores jump between on and off all the time and lower and higher frequencies because of the way big.LITTLE works which causes massive microstutter and also much higher battery drain.
In the good old S6 days a couple devs tried to implement it but it never worked no matter what they tried. Sultan, one our devs here, makes an amazing custom kernel/ROM combination. He had implemented hotplugging when he first released the kernel but it turned out to not fully work properly and caused extra battery drain and microstutters. He removed it and it fixed all the issues.
Edit: haven't used the kernel yet because cm14.1 is a bugfest so this is just speculation, you could have added a little magic and it performs super well.
Click to expand...
Click to collapse
I don't believe the hotplug theory, I've used it with and without hotplug on this device and the 6P and when using hotplug it clearly saved battery, by a good shot too! You dint have to use it, that's why u can enable/disable, but I'm sure it saves battery as I've tested with it enabled and disabled two devices with the big.LITTLE setup. And honestly, besides one other kernel that is not in these threads, this is the best kernel I've used to date for the OP3, on CM that is, not stock. I've ran ex, boeffla, all CM kernels and as I mentioned one other not located in these threads and that one and this are damn good, they each have their benefits, and the hotplug def saved battery as I've already passed my regular SOT at 40 percent left. Of course I will test without, but with my previous tests on the 6P the hotplug continuously saved battery. Sometimes it mate cause stutter or slowness, but I have not noticed that on the OP3 as of yet, it hasn't slowed a thing down, and there are 2 hotplug options in this kernel, and the hotplug in the 6P was msm which is not one that's in this kernel. This has two other options, alacurd and autosmp.

OC - as i said if there are solid reasons then yes might think about it . But from theory higher frequency equals higher temp and faster thermal throttling
Hotplugging - never heard about theory that make hotplugging causing more battery drain than keeping all clusters/cores online it is a bit non sense for me. Anyway stock Qualcomm kernels are hotplugged using msm performance and core ctl . As i dont like them they been replaced by custom made hotplugging drivers that are optional you can activate and deactivate driver as you wish
CM14.1 - I was on official and now on RR and havent noticed any major bugs neither small ones , they are solid enough to be a daily drivers
Sent from my ONEPLUS A3003 using XDA Labs

governor

Hi all!
Do you think that op6 will nave eas governor?

CPU governor? Gonna have to wait for root and then probably quite a while after that to figure that one out.

It does have EAS. https://www.reddit.com/r/oneplus/comments/8lfo0z/oneplus_6_eas/
https://github.com/OnePlusOSS/andro...mmit/33513dc87bae9839853e94ea6433604a3bac4de0

what's so special about this governor

masri1987 said:
what's so special about this governor
Click to expand...
Click to collapse
It is the future..
I tried some roms on op3 with eas and i had very good result in battery life and smoothness..