Database Develop

[KERNEL] 2.6.38.8-incredikernel-12/08/2011

12/08/2011
Added an ICS branch.
08/15/2011
Support for voice call recording.
Adjusted voltage range to 700min 1375max. Good luck have fun.
07/06/2011
Fast charge USB
Patch to increase performance of a function often used in the kernel (memcpy)
http://www.incredikernel.com
If you would like incredikernel to keep improving, please turn off adblock for the domain. It is greatly appreciated.
06/27/2011
Fix for devices that use newer touch controllers
Read this: http://forum.xda-developers.com/showpost.php?p=15132827&postcount=3626
Get it at http://www.incredikernel.com
06/19/2011
2.6.38.8
Everything from the 4/19 release
A bunch of changes to fix smartass (I think finally)
Simple sysfs interface to enable/disable audio boost
http://www.incredikernel.com
12/23/2010 - Sense
incrediblec-MR3-2.6.32-g9a2fc16 base
Patched up to 2.6.32.27
OC up to 1.1136ghz
Screen on minimum 245mhz
Screen off 128/384
HAVS/UV
Improved smartass scaling (likes lower frequencies more) - default
BFQ I/O scheduler
Tiny RCU
CFS scheduler tweaks
GPU+
SD card speed fix
TUN + CIFS modules
ext4
Updated yaffs2/atmel touch/wifi
3/5 Multitouch support - NOTE: Some devices only support 2 touches
http://www.incredikernel.com
Use the +25v zip if you have stability issues
I recommend you don't change governors and don't set any profiles. Let smartass do its thing as it takes care of sleep.
If multitouch is not working, you may be able to get it to work by following this:
http://forum.xda-developers.com/showpost.php?p=10231055&postcount=1104
InrediControl:
https://play.google.com/store/apps/details?id=com.incredicontrol
IncrediControl AdFree key:
https://play.google.com/store/apps/details?id=com.incredicontrolAF
Fastcharge widget:
https://play.google.com/store/apps/details?id=com.incredicontrol.fastchargewidget
Because of many requests to add this:

chad0989 said:
Since I haven't seen a kernel from the latest HTC source I decided to cook one up. Scored 1529 on quadrant vs a best of 1306 with the stock HTC source. No overclocking or undervolting. May toy with that later.
incrediblec-MR3-2.6.32-g9a2fc16 base
BFS318 task scheduler
BFQ I/O schedular
GPU+
SD card speed fix
All cpu governors enabled
Screen off set minimum 245 max 384
http://www.multiupload.com/4X1BETLBZ0
Enjoy
Click to expand...
Click to collapse
looks nice, would you mind if i included this in my rom?

Can you mod a kernel for cm6
Its already made just add more features? ????
Sent from my ADR6300 using XDA App

I would imagine there's a few guys working on this? Good work getting it out first.
Gonna give it a go!

Question, is the original kernel BFS or did you add that in? Just curious as I really like the UI smoothness of the stock .17 and I have absolutely 0 knowledge of linux besides what i've picked up from reading xda.
Thanks so much for cookin this up, smells good!

scottylove said:
Question, is the original kernel BFS or did you add that in? Just curious as I really like the UI smoothness of the stock .17 and I have absolutely 0 knowledge of linux besides what i've picked up from reading xda.
Thanks so much for cookin this up, smells good!
Click to expand...
Click to collapse
lol htc wouldnt cook in the bfs scheduler

chad,
would you actually mnd whipping up a cfs version? i find that cfs is much more stable than bfs

sweet dling now ...ty
edit- holy benchmarks!
Sent from my ADR6300 using XDA App

Thanks Chad! Just flashed it.

I just flashed it. What is GPU+ anyway?

DopeShiziot said:
looks nice, would you mind if i included this in my rom?
Click to expand...
Click to collapse
Go for it.
DopeShiziot said:
chad,
would you actually mnd whipping up a cfs version? i find that cfs is much more stable than bfs
Click to expand...
Click to collapse
Did you have issues with this kernel? BFS really should be better suited for phones where a smooth UI is important.
Here's a little reading material:
http://www.google.com/url?sa=t&sour...qsCyDw&usg=AFQjCNG7ORB_chlUiype8OJZES-5bHzSjA
alexdeluxe said:
I just flashed it. What is GPU+ anyway?
Click to expand...
Click to collapse
Its a patch for sense kernels that increases 2d and 3d performance.
http://forum.xda-developers.com/showthread.php?t=825304

chad0989 said:
Go for it.
Did you have issues with this kernel? BFS really should be better suited for phones where a smooth UI is important.
Here's a little reading material:
http://www.google.com/url?sa=t&sour...qsCyDw&usg=AFQjCNG7ORB_chlUiype8OJZES-5bHzSjA
Click to expand...
Click to collapse
thanks!
and no, i havent had issues, but in the past ive found cfs to be much more stable and reliable.

Make this for aosp please. Ziggy stopped doing them, King's had some issues, and Koush's test doesn't have all the governors enabled.

Source needed
Please post or link your source changes. It is required under the GPL. Thanks for your cooperation.

overground said:
Please post or link your source changes. It is required under the GPL. Thanks for your cooperation.
Click to expand...
Click to collapse
is that by chance why the kings kernels were removed? j/w

DopeShiziot said:
is that by chance why the kings kernels were removed? j/w
Click to expand...
Click to collapse
You guessed it.

overground said:
Please post or link your source changes. It is required under the GPL. Thanks for your cooperation.
Click to expand...
Click to collapse
There you go.

i wonder why when i ask any if its possible for cm6
i always get ignored????

anybody have good resullts? battery life? about to flash, just curious?
thanks

DS36 said:
i wonder why when i ask any if its possible for cm6
i always get ignored????
Click to expand...
Click to collapse
What did you need done?

[KERNEL][AOSP][2.6.32.26] - Savage-Kernel-Inc v1 ! [HAVS+CFS+SBC!!] UPDATED 1/06!

I am proud to announce Savage-Kernel to the xda forms. Currently in beta testing we worked from the latest invisiblek kernel newly undervolted, HAVS with the SBC mod.
JUST FOR @PonsAsinorem:::::: DISCLAIMER!!!! IM NOT RESPONSIBLE FOR BRICKING YOUR PHONE... EVEN THOUGH THE KERNEL CANNOT BRICK A ROOTED PHONE UNLESS YOU FLASH A BAD RECOVERY..... DON'T MODIFY THE UPDATER-SCRIPT TO FLASH THIS TO YOUR RECOVERY!!!!!! .... ALL CHANGES TO THIS KERNEL STILL MEET THE MINIMUM SPECS OF THE INC.... UNLESS YOU OVERCLOCK... WHICH IS UNDERVOLTED... WHICH IS RUNNING AT THE STOCK VOLTAGE AND SHOULDN'T HARM YOUR PHONE ANYWAY.
SENSE BASED ROMS NOT SUPPORTED THIS IS FOR AOSP ROM'S ONLY
So far the Kernel works great in conservative governor. which all the devs prefer.
Devs:
jsseidel1 (co-creator)
luisrcastillo (co-creator)
ms79723 (SBC mod updates)
lithid-cm (contributer. Updater-script guru)
Credits:
invisiblek--> base kernel!!
ms79723 --> the SBC mod.
netarchy --> smartass gov
intersectRaven --> HAVS
(credits are given to the dev's where we got some code from, may no be original designer)
CFS Builds:
Alpha1 : Click Here to download
Stable v1 : Click Here to download
BFS Builds:
Follow the github on twitter @evokernelsrc
If you like our kernel and want to support us... donate (no obligation)

Change log
Code:
[B]Alpha 1[/B]
Undervolted to 925
HAVS implemented configured for conservative
smartass added for fans
SBC Mod added (trickle Charging)
Enabled OC to 1.19 and stable
conservative governor tweaks
HAVS tweaks
smartass governor tweaks
voltage tweaks
BFS360 (latest version) and CFS VERSION!!!
Added SBC v7
BFS tweaks to ondemand gov
tweaks to interactive gov
bad ass CFS tweaks!!!!!
aggressive swap drop
misc tweaks
[B]Stable v1[/B]
SBC v7 ported from Evo (better battery life, this is a HTC mod so doesnt matter that it came from Evo)

FAQ's
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!

jsseidel1 said:
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
Click to expand...
Click to collapse
What kind of battery life are you getting with this? I know results vary, but just curious.
Sent from my ADR6300 using XDA App

excited to try this

jsseidel1 said:
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
Click to expand...
Click to collapse
How did you determine that conservative is the most power-friendly?

I would post a disclaimer about the SBC mod.
Sent from my ADR6300 using Tapatalk

Am I missing the link here or has it not been posted yet? I'm excited to test.

Guys, SBC *really* isn't good for the battery. Li-Ion batteries aren't designed to use trickle charging. IMO this will kill the batteries faster and isn't worth the extra charging.

waiting to try this... dont think it will hurt my battery in the short run... who keeps phones longer than 2 years anways?

True. I've gotten better battery life off of it, but I feel like my MIUI build recently has been getting worse due to the SBC mod.

Works on gingerbread roms?
Sent from my ADR6300 using XDA App

If it's AOSP, it should, but sometimes I've gotten weird reactions using kernels that are claimed to work on all AOSP ROMs (Kingx Kernel + MIUI = no-no. Also, MIUI + Hydra = no-no).
Point being, we should probably get this clarified. I've seen instances where people have lost touchscreen functionality (though usually that's due to a failure to wipe cache/dalvik) among other issues. Until we field test this on GB ROMs or until the OP states that it works on them, we should probably refrain from flashing it over a GB ROM. You can do it if you want, I'm in no way trying to make you turn away from it; I'm just saying take it with a grain of salt.
Plus there's the SBC issue to worry about; trickle-charging has negatively affected the battery performance of my MIUI ROM, so I'm going to switch kernels whenever I go back to it. Better charging in the short run < not needing to buy new batteries in the long run (and therefore saving money).

link??????

*sigh*...
Ok, clearly I need to start citing the comments I make. Here you go:
http://forum.xda-developers.com/showthread.php?t=885476&page=25
The first post on this last page pretty much sums it up (actually, read 23-25 to sum up the main issues, it also has links to OTHER posts talking about the issues), but if you want other chronological examples of touchscreen failure or other issues you can read examples from pages 2, 5, and some places past page 15. SBC is bad news on its own, and adding overclocking to it just makes it worse. Again, you can use the kernel if you want, I'm not gonna stop you, I'm just saying that there have BEEN problems with it on other AOSP ROMs. MIUI seems to take pretty well to SBC in terms of battery, as I've seen; but, it's been getting worse as of late. UltimateDroid had a touchscreen failure (page 5) in v1; I don't believe that's been fixed yet, but feel free to correct me. MIUI had a touchscreen failure in v2 (though I think there might have been a bad flash involved, because I flashed SBC to my MIUI 12.24 at the time and it worked fine), cited page 23. Need I go on? Lol.
Point is (I've said that a lot, I know) that it does damage, multiple AOSP ROMs are getting touchscreen failure, and there's more harm than good that comes out of it.

Read: http://www.ziggy471.com/2011/01/02/overcharging-batteries/

That's a good link also. It's actually in the thread I posted, but its equally as important if not more important than my post. Good job man XD
Sent from my HTC Incredible running Carbonite Red 1.5.

Ok you all need to relax. SBC does not over charge your battery. The trickle charging is essentially the battery staying at 100% while on the charger. Lithium ion batteries have tech built into them to protect from over charging and such. SBC just means when you take it off the charger it will really be at 100%. You can't over charge aanyway. This kernel allows you to overclock but it doesn't force it. You need to choose overclocking yourself in setcpu. ... and 90% of the kernels in this forum have SBC they just either don't say it or they call it the battery fix. You can see it in their gits. On the evo forums we just call it SBC. Ill be posting the kernel today. If you don't want to use it. Then don't. It was just requested that I port my evo kernel over to the Inc. So I am.
Sent from my PC36100 using XDA App

gmichaelow said:
How did you determine that conservative is the most power-friendly?
Click to expand...
Click to collapse
Conservative by nature is more power friendly as it only ramps up the processor as requested then brings it right back down to your min.
The way we have set our Governor is to optimize the Conservative Governor to get the most speed stability and battery life out of your phone.
I just got a config from one of your rom dev's to build the kernel so this should be posted by tomorrow.

I for one appreciate what you are doing. There is nothing wrong with having a variety of kernels to choose from. If you disagree with what this dev is doing, then use another kernel. We don't need to be running them off.
Sent from my ADR6300 using XDA App

I9300 (Int) 4.4 Custom Kernels for Omni Nighties

First things first: this is not a "best kernel thread", so please avoid asking or stating in that direction. This is all about spotting what custom kernels are compatible with Omni (for now) Nighties, and what has been your experience with them so far.
In my case, I've tried both Yank's (1.6g-beta2) and Boeffla (beta 1a) and they are working flawlessly. At the moment I'm using Boeffla just cause I find it easier to toy with different configurations and Yank's can only be tweaked from aroma. And in my personal experience, I've found that using ART instead of dalvik, it feels like I'm having a smoother experience (with a bit more battery drain, I must admit). But like I said, this is only how those kernels work on my device and that doesn't mean it will happen exactly the same way in your's and how you'd feel about them.
Any other kernels have been tested and are working in Omni 4.4 nighties?

fermasia said:
First things first: this is not a "best kernel thread", so please avoid asking or stating in that direction. This is all about spotting what custom kernels are compatible with Omni (for now) Nighties, and what has been your experience with them so far.
In my case, I've tried both Yank's (1.6g-beta2) and Boeffla (beta 1a) and they are working flawlessly. At the moment I'm using Boeffla just cause I find it easier to toy with different configurations and Yank's can only be tweaked from aroma. And in my personal experience, I've found that using ART instead of dalvik, it feels like I'm having a smoother experience (with a bit more battery drain, I must admit). But like I said, this is only how those kernels work on my device and that doesn't mean it will happen exactly the same way in your's and how you'd feel about them.
Any other kernels have been tested and are working in Omni 4.4 nighties?
Click to expand...
Click to collapse
I follow you, I would install dual boot with a custom stock 4.3 (Android Revolution HD) and an android 4.4 rom (OmniROM).
I could create dual boot between 4.1/4.2/4.3/4.4(only CM11) roms with excellent Googy-Max Kernel... but nothing to do with OmniROM 4.4 due to recovery or kernel incompatibility.
---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------
Ah, I found Devil2 Kernel http://forum.xda-developers.com/showthread.php?t=2528624 that supports Omni 4.4... and dual booting

Never been a huge fan of dualbooting but since I'm planning to stay with Omni until we reach a estable build... I wouldn't mind giving stock 4.3 a spin.
Has anyone tried out Devil and Omni already?
Sent from my GT-I9300 using XDA Premium 4 mobile app

Just as an FYI with regards to custom kernels.
Just like with CM - Anyone can submit code to a kernel repository through gerrit for review. So if you're running something other than the official kernel, ask yourself:
1) What is the alternate kernel maintainer hiding? If their change is so good, why shouldn't it be the default, and why haven't they submitted their change to gerrit for review?
2) If they did submit a patch it was rejected - ask yourself why? Code review is public so you can find the reasons given for any patch being negatively reviewed (assuming the kernel maintainer even bothered to submit it).

Entropy512 said:
Just as an FYI with regards to custom kernels.
Just like with CM - Anyone can submit code to a kernel repository through gerrit for review. So if you're running something other than the official kernel, ask yourself:
1) What is the alternate kernel maintainer hiding? If their change is so good, why shouldn't it be the default, and why haven't they submitted their change to gerrit for review?
2) If they did submit a patch it was rejected - ask yourself why? Code review is public so you can find the reasons given for any patch being negatively reviewed (assuming the kernel maintainer even bothered to submit it).
Click to expand...
Click to collapse
I´m not much more than a resourceful noob, I must admit. But even when your line of thoughts seems very logical, I wonder if there could be any other reasons for kernel maintainers like Lord Boeffla or Yank555 to remain aside from main ROM projects. Both of them have been around for long now, and I've experienced with their work in my device a lot, with no harm at all (I can't guarantee results for other people, just talking about my experience).
I guess custom kernels give you the chance to adjust your kernel to your own needs. Some people would be ok about sacrificing some performance to obtain a better battery result, or would like to have the freedom to choose the governor that best suits you, for instance. Isn't customization and freedom the whole thing about custom ROMS and GPL?
As for me, I go for customs kernels seeking a better balance between performance and battery life. The way I use my phone, I won't last a full day with original kernels. But I must admit that if I had an app to tweak Omni's original kernel myself, I'd do it (I don't got the knowledge to dev my own kernel, thought).

Entropy512 said:
Just as an FYI with regards to custom kernels.
Just like with CM - Anyone can submit code to a kernel repository through gerrit for review. So if you're running something other than the official kernel, ask yourself:
1) What is the alternate kernel maintainer hiding? If their change is so good, why shouldn't it be the default, and why haven't they submitted their change to gerrit for review?
2) If they did submit a patch it was rejected - ask yourself why? Code review is public so you can find the reasons given for any patch being negatively reviewed (assuming the kernel maintainer even bothered to submit it).
Click to expand...
Click to collapse
Would you like to impelement CPU and GPU overclock?
Would you like to implement CPU and GPU undervolt?
Would you like to implement WIP governors like zzmoove?
I aksed only three questions from at least a few more, and I'm wondering if you could answer "yes" to at least one. Making custom kernel or custom rom is a great thing because we can push device to the limits, while doing so shouldn't be suggested neither implemented in any official kernel.

JustArchi said:
Would you like to impelement CPU and GPU overclock?
Would you like to implement CPU and GPU undervolt?
Would you like to implement WIP governors like zzmoove?
I aksed only three questions from at least a few more, and I'm wondering if you could answer "yes" to at least one. Making custom kernel or custom rom is a great thing because we can push device to the limits, while doing so shouldn't be suggested neither implemented in any official kernel.
Click to expand...
Click to collapse
Voltage control/overclock - The stability issues these cause isn't worth it. Especially undervolting - at best it saves 3-4% on CPU core power savings, which is only 1-2% of system power even when the cores are at full tilt.
Alternate governors - These will have to, of course, go through review as to whether they have a valid reason for existing. 90% of alternate governors out there achieve nothing that can't be achieved merely by tuning the defaults of existing ones. Many of them are 100% marketing bull**** - Lionheart being the most blatant example. (Lionheart is nothing more than conservative with the minimum polling rate limit properly fixed...)

Entropy512 said:
Voltage control/overclock - The stability issues these cause isn't worth it. Especially undervolting - at best it saves 3-4% on CPU core power savings, which is only 1-2% of system power even when the cores are at full tilt.
Alternate governors - These will have to, of course, go through review as to whether they have a valid reason for existing. 90% of alternate governors out there achieve nothing that can't be achieved merely by tuning the defaults of existing ones. Many of them are 100% marketing bull**** - Lionheart being the most blatant example. (Lionheart is nothing more than conservative with the minimum polling rate limit properly fixed...)
Click to expand...
Click to collapse
Of course you're right but if we're talking about gaming then in long-run uV can actually benefit users a bit more that 3-4%.
The most interesting thing is OC. It's always nice to have a bit more power than usual if you're using it only for a short time. This way you get real performance boost when it's needed, for example when CPU is doing a longer task. Nobody gets hurt if CPU will work at let's say 1.6 GHz instead of 1.4 for a few seconds.
I understand what you're trying to say and I totally agree with you. Most of the changes could be and should be contributed to the base but still most of the devs (including me) wouldn't contribute non-universal device-specific changes.

[Kernel] Deported / Stockish: Issues, Reports, & Configuration

This is the support thread for the T-Mobile / U.S. Cellular variant of the StarKissed Note 4 kernel.
This kernel currently supports all North American carriers through the use of specialized release packages that will detect your device version and make appropriate adjustments.
Kernel Development Thread:
http://forum.xda-developers.com/showthread.php?t=2915824
Direct installation available via Flashify (for root users) - Android Apps on Google Play
Heimdall with the S5 patch is needed to flash from a computer. Odin cannot flash this kernel.
Additional information for T-Mobile / U.S. Cellular variant:
Potentially Unavailable:
Potentially Unsafe:
Incomplete / Inactive:

Courtesy of the Sprint thread:
egodriver07 said:
OK, I've tried everything, time to ask for help. I've used quite a few kernel tuning apps, including your own, and no matter what i try, my settings won't restore on boot for one, and two, no matter what I set my min/max CPU to it will randomly jump back up to 1728 Min and 2803 Max and change my governor to interatcive. I'll notice my battery draining quicker, that's when I catch it and adjust it down. What am I doing wrong?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse

Misterjunky said:
Hi twistedumbrella
I have a question.
Is there any benefit whatsoever in flashing any custom
kernels if the user never plans to modify or change any
of the default settings in the custom kernel?
If it's beneficial to flash a custom kernel without changing
any of the kernel's default settings what are the benefits?
Thanks!
Click to expand...
Click to collapse
The advantage to a custom kernel is the updated code. Even if defaults are left as is, they are not necessarily stock features. Stock kernels are only released with firmware updates, so a lot of the Linux updates can take a long time to arrive. Sometimes the carrier or manufacturer may not even perform Linux or upstream updates, only what it took to match any system changes.
Custom kernels often include additional battery saving or performance updates from the community. These updates may never be officially submitted. These updates may also be too specialized for the "general" kernel most manufacturers maintain, so they are intentionally bypassed.
Configuration is personal preference based on intended use. There is no benefit to using defaults other than lack of desire to customize. The defaults are generally what will be just enough of a starting point for everyone to easily tweak it to their desires, not necessarily what is best.
I configure my defaults based on averages. Some use what they consider the best overall setup for typical usage. Some aim for a specific usage scenario. I have to reconfigure the settings when I install because the defaults don't fit how I use the device (testing games for class projects).
It really is about finding what works for you even by trial and error.

On boot.tmo.11-08-2014_22.12.img
Can't change clock freq values at all. max and min stays at 1.498 GHz at all times.

Same issue is there a way to fix or should I just revert to an older kernel

seriousneo said:
On boot.tmo.11-08-2014_22.12.img
Can't change clock freq values at all. max and min stays at 1.498 GHz at all times.
Click to expand...
Click to collapse
nique0201 said:
Same issue is there a way to fix or should I just revert to an older kernel
Click to expand...
Click to collapse
It's being fixed. It was an issue with the defaults for umbrella_core. Temporary solution is to change governors.

Its stuck for me with every governor...... Just reverted... Anyway this kernel doesn't have BFQ... What's the next best scheduler for HD video recording.. Or are any if the included schedulers based off bfq? I just want to assign it as my SD cards scheduler because that's where I record everything .

nique0201 said:
Its stuck for me with every governor...... Just reverted... Anyway this kernel doesn't have BFQ... What's the next best scheduler for HD video recording.. Or are any if the included schedulers based off bfq? I just want to assign it as my SD cards scheduler because that's where I record everything .
Click to expand...
Click to collapse
CFQ is the closest. I forget if that was already built in. If not, row.

I will second Confirm the stuck govs and clock issue I get 1.4 low and 2.6 high and nothing changes no matter what app I use, also had 2 uncommanded reboot with screen off. Rolled back to previous one.

Compusmurf said:
I will second Confirm the stuck govs and clock issue I get 1.4 low and 2.6 high and nothing changes no matter what app I use, also had 2 uncommanded reboot with screen off. Rolled back to previous one.
Click to expand...
Click to collapse
Confirmations aren't needed when issues are already being addressed. If you are worried nothing is being done, here is a summary of my morning:
32bc62f89416ca66c6ad5c7d1c369540da47edfa
hardlimit: Clearer comparison to base definitions
9bdd4cf3fc402ab31867b262369cfeb581a3110f
Build: Cleanup .orig files when initiating builds
614697abf3ac21bfe1682ec5e0c67f545af1ea35
Linux 3.10.1
7411a44bf9e63e1a678461f9489a7b82b12c831b
Linux 3.10.2
5a0a353611bf3c225c0b8dbc31d1753f49d2b03a
Linux 3.10.3
daa76fd53838d19e54870e0490f044ee1d2b77f2
Linux 3.10.4
604d95229a2fe25533228e003d9221aadb5bf18f
Linux 3.10.5
668f731fd1dad78a2fbd7f3965bee42624782acb
cpufreq: Fixes for Linux 3.10.5, hardlimit

I'm testing the fixes now. There will be a slight delay because Sunday is a recurring project deadline for my degree, but something will be available later on

Lol, not worried at all. Your time and your life come first. Glad with your school project. College can be rough

Compusmurf said:
Lol, not worried at all. Your time and your life come first. Glad with your school project. College can be rough
Click to expand...
Click to collapse
It's just a lot of busy work. Since it's online, we have to record presentations, record an explanation of all our changes, demonstrate the code in action, talk about plans, etc.
After all that I have to question why I had to submit an outline, repo, and binary. It's not like they're going to read the book when they can watch the movie instead.
Pushing an update now that appears to have resolved the issue. It was not the governors at all. Like any other frequency or screen issue thus far, it was hardlimit

I understand completely. I have an IT degree and been working in IT professionally since 1987. It has served me well so far.

After a lot of digging for where something is setting 1497600 (1.49) because the one place I had has long since been removed, I came across:
Code:
#define MIN_TOUCH_LOW_LIMIT 1497600
in cpufreq.h which is part of the stock kernel code. This is used to make sure that when the screen is being used, the CPU ramps up enough to make sure touch is smooth. That is NOT something I added into the kernel. Hardlimit added the capability to adjust these values, but they are still being set by waking the phone.
Anyway, the point is that I am doing what I can to resolve them getting "stuck" on this value, but the purpose of this post is to say that it may still be a "favored" value, but that is just how Samsung intended it.

custom kernel
WHY does this kernel go makes my cpu only go from 1497 MHz to 2457 MHz???
Even if I change the frequency of the cpu to max 2.8 GHz and min 268 MHz, it stays from 1497 and 2457MHz.

y11ohan said:
WHY does this kernel go makes my cpu only go from 1497 MHz to 2457 MHz???
Even if I change the frequency of the cpu to max 2.8 GHz and min 268 MHz, it stays from 1497 and 2457MHz.
Click to expand...
Click to collapse
It hates you. It obviously isn't any of the huge discussion in the main development thread or this one if you still had to ask, so that's the only other answer I can come up with.

-_-
twistedumbrella said:
It hates you. It obviously isn't any of the huge discussion in the main development thread or this one if you still had to ask, so that's the only other answer I can come up with.
Click to expand...
Click to collapse
Omg just LOL so sorry :/

y11ohan said:
Omg just LOL so sorry :/
Click to expand...
Click to collapse
It hates me as well.Lmao
Sent from my SM-N910T using XDA Free mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:05 PM ----------
Can anyone confirm if the stock builds are working better than the deported builds. Thanks In advance!!!
Sent from my SM-N910T using XDA Free mobile app

xda23 said:
It hates me as well.Lmao
Sent from my SM-N910T using XDA Free mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:05 PM ----------
Can anyone confirm if the stock builds are working better than the deported builds. Thanks In advance!!!
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Ouch. That is like "can anyone verify this developer is worthless?"
Anyway, there is an untested update being pushed. The untested part should fix the frequency issue. It's untested because the change is swapping two lines. High was getting written to low and low to high. The result was everything reading invalid and defaulting to mid.

[KERNEL][TWRP][TW][G/N96XX][Q] / [LOS17] White Wolf Kernel (01/03/2021)

This is a home of White Wolf Kernel for OneUI and Los/AOSP based roms.
Would like to thank to all devs that work has been used to create this kernel.
Al Credits belong to devs listed below
@farovitus - ELS
@AndreiLux
@Lord Boeffla
@franciscofranco
@ Despair Factor
@ak
@flar2
@arter97
@TheCrazyLex
@Sultanxda
@eng.stk
@osm0sis
@neobuddy89
@Tkkg1994
@frap129
@jcadduono
@yank-lu.555
@dorimanx
@acuicultor
@Alucard24
@ZeroInfinity
@morogoku
@nathanchance
@mostafaz
@joshuous
@faux123
@djb77
@Eamo5
@remilia15
@jesec
@synt4x93
@DEVILOPS 007
@abtekk
@osm0sis - AnyKernel
and all others devs that make our lives easier.
Special thanx for @urgali , @Sungfive and @Duncan1982 .
@Cybertron™ for thread and signature images.
@Saber for his superb thread with all detailed kernel stuff.
Short Feature list:
Always based on latest Linux Stable
Governors:
Schedutil, ShedutiliX
Custom Frequencies:
Gpu - 598MHz
Additional drivers:
- Power Efficient Workqueues
- apk launch and touch boost - from Sultanxda
- Wake Gestures from flar2
Flashing instructions
1. Flash in recovery no black magic
WARNING
Always flash on stock kernel.
Compatibility list:
Kernels have been tested with ROMs below:
- official Ultimate Pie ROM all credits to @rifek4
- official TeamExyKings LightROM all credits to @yash92duster.
- LOS Kernel have been tested with unofficial LOS 17
Telegram Support Group​
https://t.me/joinchat/DNkhGFMc-o5FP9qSwz-4og​
Downloads:​
https://mega.nz/folder/IkdUVQ5D#9mgIsnTS6GnBEAHZSx7QAA​
TWRP With f2fs support​
https://www.androidfilehost.com/?w=files&flid=294117​
Kernel Source​
https://github.com/yarpiin/White-Wolf-Uni-LOS
https://github.com/yarpiin/White-Wolf-Uni-OneUI
Twrp Source​
https://github.com/yarpiin/android_device_samsung
https://github.com/yarpiin/android_kernel_samsung_universal9810
If You like my work - hit thanx button or buy me a beer
https://www.paypal.me/yarpiin​
XDA:DevDB Information
White Wolf Kernel, Kernel for the Samsung Galaxy S9
Contributors
yarpiin
Source Code: https://github.com/yarpiin/White-Wolf-SGS9-TW
Kernel Special Features:
Version Information
Status: Testing
Created 2018-11-13
Last Updated 2020-11-11​

Changelog:
OneUI Based kernels
https://github.com/yarpiin/White-Wolf-Uni-OneUI/blob/master/changelog.txt
LOS 17
https://github.com/yarpiin/White-Wolf-Uni-LOS/blob/master/changelog.txt

Set of rules for flashaholics by @flar2 .
Great guide how to avoid problems when flashing .
https://elementalx.org/ten-rules-for-flashaholics/
Please read and follow.

TWRP Usage Guide
Make sure your kernel support f2fs file system
1.Flash patched TWRP by yarpiin
2.MAKE BACKUP( Problems with restoring backups are solved now, but just in case)
3.Go to Wipe > Advanced wipe select Data and Change File System to F2FS, you can do the same to Cache ( Not recommended )
4.Restore backup of your data
5.Reboot & enjoy
Troubleshoot
It might happen that package extract error will occure when flashing the rom (or any updater-script based zip) . In this case just restart instalator and all should be fine.
Follow these steps or you will loose your data.

reserved

Glad to see you here!

ExtentedByte said:
Glad to see you here!
Click to expand...
Click to collapse
Had massive problems with rhread opening . Xda became so slow and tricky.
Sent from my Galaxy S9+ using XDA Labs

yarpiin said:
Had massive problems with rhread opening . Xda became so slow and tricky.
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
Been there lol. Great to see more development for the device. Welcome and congratulations on release

rifek4 said:
Wow, great to see new kernel! Keep it up, gonna follow you and try it!
Clean duplicaded threads in S9+ Review and S9+ ROMs&kernels section. Just keep one thread here so in S9 / S9+ Cross section where are all kernels and ROMs
Yeah, it's since years like that... You must be used to that Now you will be know Always after click "send thread" go to check section where you opening thread because your page seems to be stuck while adding but in real the thread is opened there and added correctly...
P.S.
Polacy przejmują S9 sekcje xD
Click to expand...
Click to collapse
Duplicated threads are @Xda Fault . Didnt had a clue that they have been created as I had bad gateway and xda server couldnt phrase request messages qhen created . It has been reported to xda .
I will get them removed
Btw im not newbie at xda
Sent from my Galaxy S9+ using XDA Labs

wow didnt had idea that so many multiple threads has been created have requested removal
Sent from my Galaxy S9+ using XDA Labs

Deleted

Great performance!

rifek4 said:
I didn't tell that you're newbie I'm just letting you know that adding threads working like that since 1 year or something... I released S7 ROM then and was same like is now, nothing changed since then
Click to expand...
Click to collapse
no offence m8 :laugh: never had any problems with any of my 4 threads
Sent from my Galaxy S9+ using XDA Labs

Thanks! Using it right now, keep it up.

rifek4 said:
So you're really lucky bcz 99% users has it... And you also had it if you made XXX dupliaced themes
Click to expand...
Click to collapse
Looks like last of my threads been started 2 years ago , but never faced any issue with it.
Ohh well **** happens
Sent from my Galaxy S9+ using XDA Labs

Better battery life with this kernel. Standby drain is much better, even with gaming with pubg with high fps

Hi there, just had an opportunity to delve through the source. Very impressive work and well done, without a doubt this will influence future releases of Endurance! Would also like to quickly address something I noted, as my kernel was heavily influenced by Andrei's work.
Your commit utilising Andrei's EAS values are outdated and following the BRE5 source drop have since been updated in the exynos9810.dtsi.
Have a good day, and thanks for giving me some more stuff to play with for future releases!

Eamo5 said:
Hi there, just had an opportunity to delve through the source. Very impressive work and well done, without a doubt this will influence future releases of Endurance! Would also like to quickly address something I noted, as my kernel was heavily influenced by Andrei's work.
Your commit utilising Andrei's EAS values are outdated and following the BRE5 source drop have since been updated in the exynos9810.dtsi.
Have a good day, and thanks for giving me some more stuff to play with for future releases!
Click to expand...
Click to collapse
Thank you for that . Will revert it then. Yea shame that Andrei stop working on it . Have read his article. This is my first exynos device so it was a nice point of start.
One thing that i noticed withs flars OC that frequencies are going to max value 2.7MHz just at ceratin ocxasions and i think that not all cores at the same time . I decided to use that commit to find out how it does work. When disable Exynos hotplug and OC big xluster to anything above 2324MHz device crashes under the load . So to make it bir snappier i jave kept Andreis max frequencies but also raise min as 850Mhz is the highest one with same voltage as the stock lowest.
Sent from my Galaxy S9+ using XDA Labs

yarpiin said:
Thank you for that . Will revert it then. Yea shame that Andrei stop working on it . Have read his article. This is my first exynos device so it was a nice point of start.
One thing that i noticed withs flars OC that frequencies are going to max value 2.7MHz just at ceratin ocxasions and i think that not all cores at the same time . I decided to use that commit to find out how it does work. When disable Exynos hotplug and OC big xluster to anything above 2324MHz device crashes under the load . So to make it bir snappier i jave kept Andreis max frequencies but also raise min as 850Mhz is the highest one with same voltage as the stock lowest.
Click to expand...
Click to collapse
I agree, truly great work accomplished by Andrei. it is a shame, albeit his merging in of the 16ms PELT was IMO the best thing to happen to this device yet.
Yep that's the nature of hotplugging. I eventually decided to maintain hotplugging and the max quad freq of 1794MHz to conserve battery. I've found hotplugging just to give insanely good Geekbench scores and not much more, likely due to the very very rare usage of those frequencies in realistic workloads. No noticeable regression in performance using 1794MHz quad in regards to user experience when using 16ms PELT.
I use 2002MHz on my OC build as I find it the best balance of performance and battery for the device. 2314 is too much of a battery regression with quad frequencies for me to justify the performance boost.

Eamo5 said:
I agree, truly great work accomplished by Andrei. it is a shame, albeit his merging in of the 16ms PELT was IMO the best thing to happen to this device yet.
Yep that's the nature of hotplugging. I eventually decided to maintain hotplugging and the max quad freq of 1794MHz to conserve battery. I've found hotplugging just to give insanely good Geekbench scores and not much more, likely due to the very very rare usage of those frequencies in realistic workloads. No noticeable regression in performance using 1794MHz quad in regards to user experience when using 16ms PELT.
I use 2002MHz on my OC build as I find it the best balance of performance and battery for the device. 2314 is too much of a battery regression with quad frequencies for me to justify the performance boost.
Click to expand...
Click to collapse
I will agree but after weeks of testing I havent found 2314MHz has a massive impact in the battery
Nature of hotplug in exynos is totaly different than snapdragon and one that I jsed to . Trus hotplugging is actualy offlining not needed cpus in my meaning.
Sent from my Galaxy S9+ using XDA Labs