{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~~A custom kernel for (most) V20 variants~~
Swan2000 is an android kernel based on the very latest Qualcomm 4.4 CAF sources for MSM8998 (which is also compatible with MSM8996), aiming to bring new features and updates over official kernels, and also improve LGE MSM8996 devices with some extra tuning, fixing and additional features tailored specifically for their performance characteristics and feature sets, while trying to maximize the battery life and responsiveness of those devices at the same time.
Its name comes from a merge between Swankernel(@AShiningRay) and mk2000(@askermk2000), as they were the main heads behind this kernel's development.
__Disclaimers__First and foremost: DO NOT bother official LineageOS threads with bugs if you're using this kernel, only bug reports with logs pointing to the official kernel will receive support there!!!
Now for the usual XDA disclaimer:
We are not responsible for bricked devices, dead SD cards, tactical nukes being set up (with the V20 you never know), alien invasions, google spying on you, or you getting fired because the alarm app failed after you removed all traces of google services from your phone so that google couldn't spy on you.
YOU are choosing to make these modifications, and if you point the finger at us for somehow messing up your device despite YOU being the one explicitly making these modifications, we will laugh at you.
DO NOT expect support on official ROM threads if you are running this kernel. Also don't try to hide it because we will know, and we will also laugh at you.
Your warranty is most likely void at this point anyway, but nevertheless, it is now definitely void if you tamper with any part of your device / software.
Click to expand...
Click to collapse
__Which V20 variants/models does this kernel support?__
The kernel currently supports the following V20 variants:
H910 / H915
H918
H990(DS / TR)
LS997
US996
US996D(Dirtysanta)
VS995
Those seem to cover every rootable variant thus far, but additional variants can be added in case a breakthrough happens on F800 for example.
__What does this kernel intend to achieve?__
The main goal here is to have a kernel that not only has extra features and improvements, but is also clean and concise, having only features that are truly needed from a kernel that will run alongside a Android 12.1-based ROMs and beyond.
This kernel does have a battery life bias, but will still scale up to maximum performance when needed. Gaming variants basically mean that the kernel comes overclocked by default, no additional tweaking is needed.
__Does it have any features over official?__
Yes, quite a few. The kernel is divided into two variants and their respective gaming modes, here are the features all variants have over Lineage's 4.4 kernel:
GPU and CPU/Cache Undervolt for better power efficiency on load.
Almost no unnecessary debug flags on the kernel for better kernel performance.
USB Fast Charge.
KCAL Control (although not really needed for LOS, other custom roms might surface with the need for this)
Multiple cherry-picks from different msm8996 sources with fixes and improvements to the kernel.
Built with newer GCC toolchains (GCC 12) with optimized inlining and other compiler optimizations for 8996
Updated LZ4 libraries for faster ZRAM
Cryptographic function optimizations, slightly improving the phone's performance when calculating hashes and so on.
The Extreme variant really only has one extra feature over the Safe variant, that being:
Stronger Undervolts (i'm talking about borderline unstable undervolts here, so i really recommend that you flash the Safe variant first).
The "Gaming" versions are basically overclocked variants of Safe and Extreme, which means they also only differ in undervolt levels.
__Are there any bugs?__
As of now, the only actual kernel bug the V20 and G5 have comes down to their insanely over-engineered USB ports. You can't use them as a MacBook by plugging a fully powered hub into them like you could in 3.18 yet.
__Download & Installation__
The folders containing each kernel variant can be found here (use Ctrl+F to search for your phone model and kernel variant, there's just too many versions to neatly organize in folders and such as it would take too much time):
GITHUB KERNEL RELEASES
To install the kernel, it's the standard procedure:
Download the kernel you want for your device
Place it into the phone's storage
Boot into recovery, select it and then flash
Wipe Dalvik Cache (optional, you only need to wipe it if you face random Force Closes, but it is a good practice anyway)
Reboot.
Use AIDA64, go into the "Android" tab and look for "Kernel Version", where it should show "4.4.302-Swan2K-...".
Enjoy the experience!
As usual, we do not take responsibility if you fail to make backups before flashing this kernel, you have been warned!
__Changelog__
Spoiler: Changes done in recent versions:
*********** Swan2000 V0.1-BETA8+ ***********Small release with BCL tweaks for all devices, some msm8998 merges and minor hotspot fixes for G6.
_________________________________________
*********** Swan2000 V0.1-BETA8 [First Release] ***********This one is pretty straightforward: Basically lineage's kernel with all the features and improvements listed above, plus a few additional tweaks that would take too much space to note.
__Closing notes__
If you have any suggestion or idea that can possibly improve the kernel, do not hesitate to share, i will try to implement it when time allows it. If there are any problems that only happen on this version of the kernel, submit a log and i'll try to look at it.
I'll say it again: Please DO NOT bother official Lineage with bugs if you're running this kernel, only lineage's official kernel is supported over there.
___________________________________
The kernel's source code can be found here. It is also shared between G5 and G6!
And last but not least, special thanks to those that helped this major revamp on LGE_8996 become a reality by developing, testing, and even helping things indirectly, the dev community on all three phones had to come together for this:
@xxseva44
@npjohnson
@askermk2000
@thewolfsvk
@ROMSG
@bernardobas
@VortexHD
@Michele_Catella
And many, many others
Reserved.
Might need an additional post at the top later.
First of all thanks! To everyone involved, you guys rock!
A little tangent (bear with me for a while, please)
I had an OP3 before this V20, and like some "developers toy's" received a good attention for some time that phased out and was replaced by many more quickly than his predecessors in my opinion.
Besides SultanXDA Lineage 14 that he customized the kernel+ROM (achieving 6h screen time with ease), the thing that had me impressed was EAS and was beautifully implemented by mcdachpappe in this kernel. That really was responsive and also have some endurance. Other device that I still have it's my LG G4 and the devs ported so many kernels (I used blu_active most of all), but I didn't have the time needed to tweak.
After that detour, I would like to know: (no pressure, complains, just curiosity from my part)
1) EAS it's still relevant? Did you have any plans to implement it? Since the OP3 "has the same msm8996" could it be ported or benefit from this governor?
2) I noticed that you have on this kernel the "basic" governors : interactive, conservative, ondemand, userspace, powersave, performance. Do you consider other addition? Or it's an unnecessary problem?
3) I would love to not need any app than necessary, but to reduce some "image retention" there are many posts to help mitigate this issue, but the configuration it's for some app and trying to replicate in the system settings won't have near the results. Do you have any suggestion?
4) Any recommendations for applications to adjust the kernel? I used many moons ago the Kernel Audtor but the most close replacement that I'm aware it's the SmartPack-Kernel Manager?
5) A feature that always intrigue me in some Sony devices was the ability from stock to limit/manage the battery, "setting a max capacity" to stop charging at determined percentage, theoretically "extending" the life-span. How demanding, and it would benefit our devices this feature?
6) You mention the USB issue. Right now I don't have any hub and would be a nice thing in the future to plug an ethernet cable, be able to use a mouse + keyboard in some situation, and technically the V20 has HDMI out. But in this new kernel the problem comes only to being able to charge with any hub or I didn't get properly what the exact problem was?
7) The "only bug" on my H990DS that I encountered so far it's when I installed the SmartPack-Kernel Manager and in the "Overall Statistics" the CPU temperature are "-4.0°C" (I didn't install this app before with the stock kernel because I didn't needed this app). So how to properly report it?
I can't believe how much more responsive the device is, looks like magic!
dextructor said:
First of all thanks! To everyone involved, you guys rock!
A little tangent (bare with me for a while, please)
...
Click to expand...
Click to collapse
1 - No, not really. While EAS was included in this kernel's earlier versions, we opted to drop it from both official and Swan2000 when shipping lineage. EAS just doesn't bring that many benefits, if any, to msm8996 and 8998 devices when the device sources are already well tuned. And that's what we saw by going back to HMP: No significant perf/power difference on V20, G5 or G6, although the results favored HMP a bit since EAS boosted too much.
2 - No other CPU governor additions are planned, interactive can be configured to do pretty much everything you need (our device trees on lineage already have it pretty balanced), and if you can use conservative if a inherent battery life bias is needed.
3 - Lineage 19.1 has LiveDisplay support by default(Settings->Display->Color->LiveDisplay), not needing any kernel additions on that front. Those guides use KCAL control, which is there on the kernel in case other custom roms show up without LiveDisplay. Personally i use a LiveDisplay Color Calibration profile of 94%R, 90%G, 92%B to nearly eliminate image retention on mine, though that's because my display has a green tint ever since i bought it, might not be the same for you. Intensity and contrast values don't seem to affect retention that much so it's up to you.
4 - SmartPack is pretty much the continuation of Kernel Adiutor in case you really need a kernel manager.
5 - It is possible to do that, but requires ROM integration and can also be buggy sometimes (my Xiaomi Mido has that feature on its custom rom and sometimes it simply doesn't charge if i enable the battery limit and it hits the threshold, only charging again after a cold reboot). Since the V20 has a user-replaceable battery, that's not a big deal.
6 - The bug is not on the usb features themselves. HDMI support is perfect, as is OTG, mouse and keyboard as well (and i also think ethernet). The problem arises when fully powered hubs come into play: The phone simply refuses to charge at the same time it's in Host/OTG mode because we didn't fully figure out USB-PD on the new kernel just yet, and as a result powered hubs don't work, though you can still use simpler hubs that don't need additional power, or charge the phone. Since the V20 and G5 are pretty much the only 8996 devices on 4.4 that have this fully-featured usb port, it's hard to conceptualize a fix that doesn't break something else.
7 - SmartPack reporting incorrect cpu temps has always happened in 4.4. Apparently it's a bug in the app because AIDA64 doesn't suffer from the same issue, nor does CPUFloat (although CPUFloat does seem to invert GPU and CPU temps in some roms). I guess that's because there aren't that many Snapdragon 82x devices running 4.4 so most apps focus on 3.18's sensor configuration.
AShiningRay said:
1 - ...No significant perf/power difference on V20, G5 or G6, although the results favored HMP a bit since EAS boosted too much.
2 - No other CPU governor additions are planned
Click to expand...
Click to collapse
Beautifully explained, much more than I needed, and very well tuned.
AShiningRay said:
3 - Lineage 19.1 has LiveDisplay support by default(Settings->Display->Color->LiveDisplay), not needing any kernel additions on that front
Click to expand...
Click to collapse
I was aware, but thanks for the reminder, and your settings. When I was using the OP3 in the beginning I disliked very much the punchy color calibration that was used until they released "sRGB" profile that I used ever since (I guess that I couldn't have a Samsung device with their saturated profiles). And I tried to replicate some of the configs but the values don't match if you don't try to calculate. For example I liked this config that I copied from this video description and give me an very soft and neutral color spectrum (too bland for some, and with more time I would search for how to improve it):
Red 256 | Green 241 | Blue 226
Minimum RGB Value 0 | Saturation Intensity 12 | Screen Hue 0
Screen Value 128 | Screen Contrast 128
The color values are really straightforward, but "Minimum RGB"? The "Saturation Intensity" it's separated in 2 distinct values like "Saturation" and "Intensity"? Do you understand the difference?
AShiningRay said:
4 - SmartPack is pretty much the continuation of Kernel Adiutor in case you really need a kernel manager.
5 - requires ROM integration and can also be buggy sometimes
Click to expand...
Click to collapse
Clear enough, it was just as a suggestion.
AShiningRay said:
6 - The phone simply refuses to charge at the same time it's in Host/OTG mode because we didn't fully figure out USB-PD on the new kernel just yet
Click to expand...
Click to collapse
No problem, I was just mention because my ex-wife had a Pixel XL and I bought to her this USB Hub (UCN 3273) and everything worked (except HDMI because Google intentionally disable HDMI out just to sell more Chromecasts) including PD charging. It was used with ethernet (because a real gigabit connection beats many wifi speeds and consistency, and spots with bad coverage) and even an external USB mic to make video-calls (that without powering the HUB won't work). OK if this features could come to the device, until then no need to rush.
AShiningRay said:
7 - has always happened in 4.4
Click to expand...
Click to collapse
Ok, I didn't know. It's better to know than make trouble unnecessarily.
I remember reading about low volume on audio recording and decided to test on both OP3 and H990DS with Audio Recorder (M4a +48kHz +256kbps + stereo settings). Both devices recording the same initial 20s dialogue from this video at the same distance from the speaker of my computer but very different results.
I even analyzed in Audacity on the computer and it was indeed not only much lower, but was mono instead of stereo.
How can I help you guys properly identify this problem?
Thanks again!
dextructor said:
The color values are really straightforward, but "Minimum RGB"? The "Saturation Intensity" it's separated in 2 distinct values like "Saturation" and "Intensity"? Do you understand the difference?
Click to expand...
Click to collapse
Minimum RGB is pretty useless, it was supposed to deal with the black levels (in essence, how dark should the darkest pixels be on the screen) but never seen it do anything useful on any of my phones, OLED or not.
As for Saturation and Intensity being separated... "Saturation Intensity" is just "Saturation" on LiveDisplay, while "Intensity" on LiveDisplay is the same as "Screen Value", which dictates the overall brightness of the screen's pixels (just don't go too far on this one, or else you'll get overblown whites, also balance it with contrast and you get a nifty max brightness boost for free).
dextructor said:
No problem, I was just mention because my ex-wife had a Pixel XL and I bought to her this USB Hub (UCN 3273) and everything worked (except HDMI because Google intentionally disable HDMI out just to sell more Chromecasts) including PD charging. It was used with ethernet (because a real gigabit connection beats many wifi speeds and consistency, and spots with bad coverage) and even an external USB mic to make video-calls (that without powering the HUB won't work). OK if this features could come to the device, until then no need to rush.
Click to expand...
Click to collapse
It might come at some point since we really want to fix every major hardware feature of all three phones, though it's one of the peskiest issues to deal with on the kernel side since we have 5 or 6 usb drivers that communicate with each other.
dextructor said:
I remember reading about low volume on audio recording and decided to test on both OP3 and H990DS with Audio Recorder (M4a +48kHz +256kbps + stereo settings). Both devices recording the same initial 20s dialogue from this video at the same distance from the speaker of my computer but very different results.
I even analyzed in Audacity on the computer and it was indeed not only much lower, but was mono instead of stereo.
How can I help you guys properly identify this problem?
Thanks again!
Click to expand...
Click to collapse
AFAIK that's a known problem on AOSP roms as a whole (happens in 3.18, happens in 4.4, not kernel-side), mics on V20 and others just don't work as intended compared to stock. It's on the list of things we're gonna look at, but it's not a priority right now because we're trying to sort out Bluetooth in order to bring Lineage 20 in.
Once we start debugging the mics, i'll see if i can get one of our rom-side devs to approach you with more info if you're still available by then. Thanks!
AShiningRay said:
Once we start debugging the mics, i'll see if i can get one of our rom-side devs to approach you with more info if you're still available by then. Thanks!
Click to expand...
Click to collapse
No problems, you guys are really good at improving/fixing this devices. And I'll be here if I can help in anyway.
Very good explanations, really good knowledge on this thread. Thanks!
dextructor said:
No problems, you guys are really good at improving/fixing this devices. And I'll be here if I can help in anyway.
Very good explanations, really good knowledge on this thread. Thanks!
Click to expand...
Click to collapse
Yea in regards to the mic level, this has been a known issue on the v20. However i was not aware of it recording in mono, that is very odd. The level issue is mixer path related, but the mono recording, i'm not too sure. I will admit, it may be a while until this issue is fixed as we're heading into los 20 and getting that ready. But this will definetly get looked at. Could you grab logs of when you record? I wand to see what the audio hal is doing and how it sets up for recording.
xxseva44 said:
Could you grab logs of when you record? I wand to see what the audio hal is doing and how it sets up for recording.
Click to expand...
Click to collapse
Since I couldn't download the latest build because the page error 502, I clean flash 2023-04-23 build and only install the Magisk so I could get an dmesg and the Recorder app mentioned before.
Have 2 sets of archives, the stock kernel and the Swan2000 with logcat and dmesg.
If I can provide more help, please just ask.
What's the significance of H830, H850, H870?
andruyd said:
What's the significance of H830, H850, H870?
Click to expand...
Click to collapse
Those are G5 and G6 models. This kernel supports all three LGE_8996 phones, we just separated the threads for each of them.
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
@xxseva44
Was the logs that I send any useful to help diagnose the audio recording issues?
Thank you all!
dextructor said:
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
Click to expand...
Click to collapse
BCL is enabled by default on all 4.4 builds since it's nowhere near as aggressive as 3.18, but you can disable it from userspace but it requires root... though i don't really recommend doing that.
dextructor said:
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
@xxseva44
Was the logs that I send any useful to help diagnose the audio recording issues?
Thank you all!
Click to expand...
Click to collapse
Ah yea, so far i haven't found anything odd. If possible, can you reboot, record something and then send the logs right after? It'll help with locating the issue if that's all that audio did the entire time the device was on.
AShiningRay said:
BCL is enabled by default on all 4.4 builds
Click to expand...
Click to collapse
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
xxseva44 said:
If possible, can you reboot, record something and then send the logs right after? It'll help with locating the issue if that's all that audio did the entire time the device was on.
Click to expand...
Click to collapse
I'm sorry, but I didn't fully understand what you requested me. So let's recapitulate:
1) Reboot
2) Record
3) Log (Only logcat or with dmesg as well)?
Little off-topic: I noticed a strange behavior last night, when for the first time I tried to record an video with GCam (if you/anyone have another version, build to suggest, I'll be grateful) and no audio at all. So I opened the stock Camera and the audio was loud and clear. And with the stock audio recorder was also very low volume as with the other app.
Are those things even remotely related?
Thanks!
dextructor said:
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
Click to expand...
Click to collapse
Yes
dextructor said:
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
I'm sorry, but I didn't fully understand what you requested me. So let's recapitulate:
1) Reboot
2) Record
3) Log (Only logcat or with dmesg as well)?
Little off-topic: I noticed a strange behavior last night, when for the first time I tried to record an video with GCam (if you/anyone have another version, build to suggest, I'll be grateful) and no audio at all. So I opened the stock Camera and the audio was loud and clear. And with the stock audio recorder was also very low volume as with the other app.
Are those things even remotely related?
Thanks!
Click to expand...
Click to collapse
All logs, grab them via adb right after running the recording. As for the wonky audio levels in different apps, yes they are related. Something does not seem to be right in terms of the mixer levels so I'll need you to log all the apps that behave weird so i know what routes to look at.
So far so good. I've only had one random reboot and that was on the Safe kernel. I'm now on the Extreme kernel and no issues so far. My H990 definitely doesn't get as warm compared to the stock kernel and it still looks and feels snappy.
xxseva44 said:
I'll need you to log all the apps that behave weird so i know what routes to look at.
Click to expand...
Click to collapse
Ok I'll do probably today or tomorrow and post it later.
Since I don't play any games anymore on my phone since Clash Royale many, many years ago, the most intensive thing that I do it's occasionally video-calling via Telegram FOSS. But let me tell about my history with this V20 H990DS
I bought this device used, and the seller said that the battery needed to be replaced, and randomly it gave me green-screen reboot messages when below 30% and the thermals wasn't great because it was the end of summer here in Brazil. Since everywhere that I searched about buying new LG batteries anyone tells that it's hard to find a real original and reliable I decided to try this one from Aliexpress, and also ordered some copper shims (0.5mm and 0.6mm) to put thermal paste and improve things. And a 128GB SDcard since it was cheap now (compared to years ago... I tested with H2testw and it works perfectly)
So the battery arrived first, and even before it arrived I installed the Lineage 19 and with the new 4.X Kernel it almost never gave me more green-screen reboots, but few random reboots when below 35%.
With Lineage 18 + SwanKernel Extreme gave the most stable scenario but only one time I did try to video-call with Telegram and it went stable, but slow (probably due underclock, maybe?)
But last Friday using the new battery I tried to video-call through Telegram some relatives that live abroad, and with only 5 minutes of calling it rebooted and was warm-ish? So the copper shims arrived early that week and I decided to do the thermal mod this week.
With the 0.6mm it pressed the LCD giving a darker spot, so I decided to replace with the 0.5mm, put new thermal paste and try again... So no dark spot on the screen.
I installed Telegram on other computer and tried to call and test the V20, but it still reboots after some time, but the strange thing it never reaches 62 or higher.
I tried the CPU Throttling Test to test the thermals and it barely reaches 60 with the Extreme+Gaming or with only Extreme as well.
So after all of this, I remember that H990DS have the reputation for drawing a lot of power:
1) Even a "compatible non OEM" battery can't provide what this device demands in terms of power consumption?
2) Having a dual-sim gives me freedom in terms of separate personal-work calls etc and not having to carry 2 phones. Could a dual sim card adapter could be a better approach?
3) There's a chance that this H990DS motherboard it's problematic/defective somehow and replacing with another H990DS would fix things (or even a H990 non-DS with that dual-sim adapter)?
4) The random reboots could give some useful information somehow for you devs? And how the best way to collect it?
5) Are video-calling that demanding, even if it don't reach the same temperatures that the pure CPU stress?
6) Any tips, suggestions?
Thanks!
PS: @xxseva44 sorry I couldn't give you the logs, but the instability/problems here are taking much more time that I initially planned.
Related
After being a long time lurker here in XDA and having successfully fulfilled some requests on another thread, I thought I'd try to give something to the great community here.
You probably remember Ivan's kernels that provided the community with a version of intersectRaven's Hybrid AVS with 1113MHz overclocking. Unfortunately it looks like Ivan been very busy and is unable to update his kernels. So I have provided recent updates of intersectRaven's truly awesome kernels that includes the 1113MHz overclock for you all to enjoy. (I see this request a lot so maybe now intersectRaven won't be bothered by it again )
I absolutely take no creative credit in making these kernels as all I have done is used the open source code on intersectRaven's github and compiled it. The real credit goes to all the other coders here in this forum (cyan, pershoot, and especially intersectRaven).
When time permits, I'll try to update these kernels when improvements and/or bug fixes are made but I realistically only see myself updating these once or twice a week.
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions. Edit: Due to having virtually no free time, I don't think I can get fulfill requests in a timely manner... I'll try but I can't promise it. So sorry everyone -_-;
If you have the time and the will, I highly suggest you learn how to compile for yourself as I find it pretty fun and rewarding to make something for yourself. Guides and instructions can be found throughout the XDA forum and also on Cyanogen's wiki.
Before updating with these kernels, all I ask is that you make a nandroid backup in case something goes wrong.
Q & A:
-What's the difference between CFS and BFS?
See this short post for the difference between Completely Fair Scheduler and Brain F*** Scheduler. In summery, CFS is better for multitasking, BFS is better for user interactions (keyboard, homescreen swiping, etc).
-What's the difference between SVS and AVS?
Static Voltage Scaling will change the voltage based on a set table created by the kernel maker. Example: At a certain speed, say 245MHz, 925mV is feed into the CPU. At 998MHz, 1225mV is used.
Adaptive Voltage Scaling will change the voltage depending on temperature and CPU needs. Personally, AVS is running rock solid for me but I can't say for sure if it will be for everyone so SVS kernels will continue to be made available.
-What is this "No Audio Boost Version"?
Many of the custom kernels posted in this forum and the kernels used by default in the CM6 roms have this feature where it increases the loudness of the speakers during calls. Its been reported that some bluetooth headsets are overly sensitive to the increased loudness and some have reported that it distorts the audio quality even though volume has been lowered by the user. Due to an overwhelming request to make a kernel without this feature, I have included a separate set with each release that does not boost the volume.
-Can you make a higher overclock version of your kernel?
I was really against this because when I first tried to do this, my phone got really hot. But the requests kept on coming so I revisted this and possibly discovered a way to keep the temperature under control by limiting the max voltage to 1300mV. You'll find a 1190MHz version of my kernel here (Mirror Link).. Most users should be able to handle 1152MHz without any problems but some won't on 1190MHz. You'll know when your CPU can't handle a certain speed if you start to experience a sudden decrease in performance, lag, force closes, and spontaneous reboots. This won't be alievated unless more voltage is feed to the CPU but I'm not comfortable going beyond 1300mV. Now before you try these kernels out I gotta say this. I am not responsible if these kernels result in damaging your phone. Its purely for testing purposes and I really dont recommend using it as your everyday use kernel. If you do continue to use it, you should limit the max to 1113MHz or better yet 1075MHz (see previous question for the reason) if you care about battery life.
-I'm getting a black screen whenever I launch the camera app. Why? (720p related question)
The latest kernels with the 720p code only works with roms that has the 720p stock camera app and now the HTC camera app on Enomther's [ROM] as of 8/10/10. The latest cm6 nightly that has the 720p camera app as well as a few other roms out there that are based on cm6. You can try flashing charnsingh_online zip that contains the updated camera app if you don't want to use the nightly but I don't know for sure if his camera app is compatible with roms under RC2. Another alternative is to send in a request for a custom kernel and I'll make one for you without the 720p code.
2.6.38 kernels:
(Tested on Cyanogenmod 7 Nightlies)
Grab the kernels here: Mediafire
-Changes since 090311
-Set default sleep ideal freq to 128mhz for smartassV2 governor
-Bug fix for 1190MHz kernels, properly set max voltage to 1325mV
-Compiled HAVS 1190MHz kernels for those phone that can handle it
-Changes since 062411
Rebase source from IntersectRaven's Github
Highlights include:
-msm: Add support for voice call recording
-PM: Back off suspend if repeated attempts fail
-lib/sha1: use the git implementation of SHA-1
-arm: remove “optimized” SHA1 routines
-Fix AVS thread not being started.
-Added erasmux’s Smartass governor Version 2
-Changes since 062311
-Fixed ext4 partition support on sdcard.
-Changes since 052711
-Rebase to kernel version 2.6.38.8 from IntersectRaven's Github, with it 2 new governors (InteractiveX and SavageZen)
-Changes since 052611
-Rebased kernel source from intersectRaven's Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn't want to take a chance in WiFi not working for some.)
-Changes since 042111
-Rebased kernel source from intersectRaven’s Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn’t want to take a chance in WiFi not working for some.)
-Changes since 040911
-Bug fixes relating to USB file transfer speeds and addressed probable cause of WiFi problems for some.
____________________________________________________
If you want, you can buy me a drink (I like orange juice)
Have these kernels been tried and tested? Does the following work:
- Youtube
- Camcorder
- Googles
- Flash
- Unmounting sd card
- Wifi locations
and can you tell us more about the battery life by using this kernel?
p.s. Thanks for posting this btw...
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
Click to expand...
Click to collapse
Thats gr8...what about battery life? how do yo fare by using this kernel?
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Well....i like 800mV UV and OC, giving me the best balance between battery life and speed.
couldnt do an excact test on the time, but it lasts enough for my usage ^^
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
Click to expand...
Click to collapse
Glad you like it! You know it was partly you that made me want to start this thread.
great! i am really looking forward to it!
wildmonks said:
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
Glad you like it! You know it was partly you that made me want to start this thread.
Click to expand...
Click to collapse
"partly"
^^
xD
everything including goggles seems working on 800 bfs.. 41 linpacks.. cool
That was my result with linpack and this kernel!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
wildmonks said:
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions.
Click to expand...
Click to collapse
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
mardox said:
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
Click to expand...
Click to collapse
CFS: http://de.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
nazrin313 said:
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
Click to expand...
Click to collapse
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
hondaguy said:
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
Click to expand...
Click to collapse
Im gonna charge it to 100% then leave it whilst I sleep...Tommorow im gonna im actually gonna use it
from my own usage since installing Froyo here is what I have found from testing various kernels (Unplugged at 7am)
- Froyo Kernel: Lasted till 10pm ish (Display on > 3 hrs)
- Preshoot 33.4 kernel: lasted me till 3pm ish (Display on approx 2 hrs)
P.s:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
daveid said:
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
Click to expand...
Click to collapse
Here yah go:
2.6.33.5_AVS-925mV_CFS_NoAudBoost_v2_060210.zip
I think all those years of listening to loud music has affected my hearing so I need the audio boost
I tested it out and it seems audio levels are back to standard (noticeably lower) but let me know if it doesn't work or if there are any other problems with it.
Update: Doh! I found a bug that I introduced into this no audio boost version. Seems that I broke music playback O_O. I fixed it and updated the above link. Sorry to those that download the other version -_- . . .
Audioboost is so necessary, i cant use any kernels without!
RinTinTigger said:
That was my result with linpack and this kernel!
Click to expand...
Click to collapse
t0ol said:
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
Click to expand...
Click to collapse
nazrin313 said:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
Click to expand...
Click to collapse
Interesting observation you all are getting. Must be the combination of BFS and OC? But I would not be surprised if battery life suffers a little... But very cool nonetheless
Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
Latest Kernel Here
20130625_10XX:
- updated with fix for more recent 4.1.2 Sense ROMs (should fix camera issue)
*unsure if this becomes incompatible with older 4.1.2 Sense ROMs though
20130602_07XX:
- NTFS support
- compiled using 4.8 linaro compiler
- improved workqueue queueing
- sleeper improvements
- responsiveness patches to the frequency controllers
20130531_09XX:
- fixed earpiece volume during calls
20130528_17XX:
- more optimizations (see GitHub)
20130527_18XX:
- more ARM implementations (see GitHub)
20130527_10XX:
- ARM implementations of kernel algorithms (see GitHub)
20130527_09XX:
- compiler optimization flags
20130526_22XX:
- initial version
- uses Linaro compiler
You can find my kernels at:
intersectRaven's Kernels
GitHub is at:
intersectRaven's GitHub
FAQ or something like that:
1.) Camera doesn't work!
- Try this fix from Golv here. This usually occurs on older ROMs.
*Latest 20130625_10XX version should solve this without flashing older camera libs.
Reserved 2
Reserved 3
Nice to see ir taking interest in the One. Truly a great dev
Sent from my Nexus 4 using Tapatalk 4 Beta
Uhhh nice to see you here
intersectRaven said:
Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
Click to expand...
Click to collapse
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
m0nz said:
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
Click to expand...
Click to collapse
Should have put a qualifier there huh? Anyways, it's pointless from a no tweaking perspective since undervolting may not work for some chips and could cause more trouble (random restarts and the like) than it's worth. It's fun for a tweaker (like when I did something like that for the N1) but not for someone who's the flash and forget type. :fingers-crossed:
Thanks
P.S you missing the ":" on the http link
Really glad to have you here iR. Missed your kernels from my nexus one days with those hybrid AVS kernels.
Camera is buggy
Sent from my HTC One using xda app-developers app
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The camera will problably need som librarys, like most other kernels, I think. There is a zip for this in other threads (couldn't find it right away)
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What is the problem exactly? Also, is this a custom Sense ROM or stock Sense? Just mentioning that it is buggy doesn't actually help me solve it since there are no bugs in my phone.
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Intersect my man. Nice to see u in the HTC one forums!
Sent from my HTC One using xda app-developers app
Camera troubles
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
chourmovs said:
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Can you try the link posted below by Maikeu and get back to us whether it fixes the issue?
Maikeu Locatelli said:
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
Click to expand...
Click to collapse
Posted this in the second post here for future reference.
HI, after fashing this kernel , i cannot hear any sound from call dial ,
008325 said:
HI, after fashing this kernel , i cannot hear any sound from call dial ,
Click to expand...
Click to collapse
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
intersectRaven said:
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
Click to expand...
Click to collapse
Thank you very much i really like this kernel , smooth , cold , save battery
Hi all.
Compatibility:
It should work on any rom by following this logic:
Builds (starting with r1) are Android 6.0.1 Marshmallow only.
Builds (starting with r17) are Android 7.0 Nougat only.
Builds (starting with r28 up to r37) are Android 7.1.1 Nougat only.
Builds from r38 up to r44 are for Android 7.1.2 Nougat
Builds from r45 up to r48 are for Android 8.0.0 Oreo.
Builds from r49 are for Android 8.1.0 Oreo.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from Franco Kernel Updater app
Features:
1 - Legendary battery life
2 - Flash & forget
3 - Typical interfaces like display adjustments, sound control, vibration control, and all that boring stuff
4 - Bypasses the verified boot flag for Android Pay compatibility (root still breaks Android Pay but that's your own problem)
5 - Idle power consumption reduced to the absolute minimum (if you have wakelocks from 3rd party apps you're obviously on your own)
6 - Support for FKUpdater's Performance Profiles
7 - Magical support, I'm here every day, checking posts almost hourly, ready to help anytime (well, unless you fail to read the OP, which contains most info you need)
8 - Seemless integration with my app FKUpdater
9 - No crap placebo patches, or "magical" optimizations
10 - Probably more, check my github for all the details - the code speaks for itself
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/bullhead
Follow me on the interwebs
Google+
Twitter
Google+ FK community
https://plus.google.com/u/0/communities/117966512071636110546
Kernel Manager for Franco Kernel demo
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Current r1 is not yet complete, I think it only lacks sound control, but it's pretty much done.
Took me a little while to find the right balance, this little bastard lags easily, but this Kernel is pretty much a "clone" of FK for the 6P so I'm sure you'll have some fun with improved battery life.
FKUpdater will be updated tomorrow to support this Kernel and the final r1 release will also be out.
Any feedback about UI responsiveness and anything else that comes to mind, now's your chance to talk.
Two things to note though, EIS video stabilisation is enabled automatically with FK, just check your Camera app and you'll see it, and FK ships with a slightly cooler display colour temperature, and a very slight saturation boost.
I wasn't supposed to work on this device because I didn't want to shell out 450 euros for a device I wouldn't use outside Kernel/app development, but in the end I did it for you.
Enjoy it & you're ducking welcome.
Thanks much buddy. Will have to try it asap
Thank you! Been looking forward to this.
Sent from my Nexus 5X using Tapatalk
My wife's 5x can barely keep up with her usage, anxious to see you work some magic. Thanks much!
Yes! Thank you Franco!
Thank you!!!
FKupdater full version crashes when i go to settings
@franciscofranco : Thanks a ton for bringing the support to 5X...Flashed and working good with Cleancore + Cata...Will test the setup for the day...video EIS option is set...so thats cool...also suddenly the new cool color calibration seems different...Nice work
Nice one - Thanks! made a few donations through your kernel app the other day to help pay for the device - I'm away from my computer for a couple of days so no flashing for now but will do asap! ?
Sent from my Nexus 5X
Thank you so much @franciscofranco 1st time being able to use your kernel and i can say I'm so ducking excited!!!
Sent from my Nexus 5X using Tapatalk
FINALLY!!! The Franco Kernel has come back toooo my nexus!!!
Thank you!!!
Thanks, great work
Sent from my Nexus 5X using Tapatalk
I think maybe we should limit the number of "Thank posts" on this thread and just press "Thanks" as and where necessary to show HOW MUCH we REALLY appreciate this Kernel coming to the Nexus 5X. Otherwise it will quickly fill up with Thankyou's instead of the real nitty gritty.
That would be very counterproductive indeed !
Just a thought....
Let the party begin :d:d:d
So far it's working great I am just wondering why all 4 cores goes max frequency after the touch? I checked and only first core should go to max frequency but all are going instead to this frequency when checking with system monitor.
awesomeness! thx
Oh yeah, welcome back man! I saw your android vs. iphone rant the other day, and respect you even more for that! Never be afraid to voice your own opinion, more power to you sir!
Back on topic, looking forward to try your newest kernel!
franciscofranco said:
and FK ships with a slightly cooler display colour temperature, and a very slight .
Click to expand...
Click to collapse
Out of curiosity, do you have the exact values of what was changed? Just so I can reverse it if I prefer the warmer temperature?
Installed this kernel and bought the app as a story to the dev. But paid version of the app crashes on opening setting. This is just for information. I am pretty sure the app will be updated soon.
Below you will find a couple of kernels that I put together for various roms and purposes. Most of these will be included into my other builds, but I thought that I would share them here as well, in case they are useful on any other roms. You are welcome to use and abuse these kernels or the source code for any purpose that you see fit!
It all started over a year ago when I wanted to add some governors to a kernel, and it didn't work very well. However, praise God, I learned a lot of things and was able to add the governors in! From there I played around with various sources and have put together some developer kernels as well (including kexec and other tools). None of my work is purely original, I typically beg or borrow from other kernel developers by looking at their source. Please feel free to use any of the materials here if it will help you in any way (including adding it to a different rom).
Feel free to comment if you have tried them on another rom, successful or not, or to leave feedback on these kernels as well. These can be flashed on any tblte variant of phone, but I have only personally tested them on tbltetmo. They should work on any tbltexx phone as well, and maybe others.
This is, however, specifically not for TW roms. This is for AOSP/CM etc., based roms.
Post #2: Thanks
Post #3: Marshmallow kernels
Post #4: Change logs
Source: https://github.com/alaskalinuxuser
Post created: 10/26/16
Last updated: 12/22/16
The big thanks!
As with any project, it starts somewhere, and while I want to give God the glory for my work, I also want to thank a few other people who helped me (directly or indirectly) along the way:
@OldDroid
@Mickey387
@deadman96385
The Emotroid Team
For AOKP 6.0.1, may also work with PAC and CM.
Download:
http://www.mediafire.com/file/zodtgo623rkj09f/AKLU-AOKP-M-TBLTE-intelliplug-20161222.zip
For PACROMS 6.0.1, may also work with AOKP and CM.
Download:
http://www.mediafire.com/file/bafiwx8epkiqteb/AKLU-PAC-M-TBLTE-intelliplug-20161222.zip
For SLIMROMS 6.0.1, may also work with LS.
Download:
http://www.mediafire.com/file/bb5ns8nq4ybt376/AKLU-SLIM-M-TBLTE-intelliplug-20161222.zip
Features:
- CPU over clocked to 2688 MHz.
- GPU over clocked to 633 MHz.
- Intelli_plug by @faux123!
- Bioshock, Darkness, Nightmare, and Lionheart Governors!
- CPU boost, DVSF input boost disabled so you can use CPU boost for input.
OLD KERNELS:
https://www.mediafire.com/download/3hdl2bl4j3eqbdw
https://www.mediafire.com/download/waz9bklaj808o90
https://www.mediafire.com/download/nh1oa058qdqa708
PAC/AOKP 6.0 baseline:
http://www.mediafire.com/file/h9b68aaon1yvr11/aokp_pac-mm-kernel-baseline.zip
Slim 6.0 baseline:
http://www.mediafire.com/file/bt4qw03m8jko53a/slim-mm-kernel-baseline.zip
Developer kernel for AOKP and PAC ROM:
https://www.mediafire.com/download/6q16143xjmf6hje
Features:
- Kexec enabled
- Modules enabled
- CPU over clocked to 2688 MHz.
- GPU over clocked to 633 MHz.
- Bioshock, Darkness, Nightmare, and Lionheart Governors!
- CPU boost, DVSF input boost disabled so you can use CPU boost for input.
- DANGEROUS! USE WITH CAUTION!
Notes:
May require a clean flash over fresh ROM. I have had trouble where I also needed to wipe coach after flashing. ATAGS is enabled. This kernel is potentially a security risk, but may allow you to play with multirom or other multiple boot options.
Change Log:
20161222
+ Added Intelli_plug by @faux123!
20161116
+ Over clocked CPU to 2688 MHz.
+ Over clocked GPU to 633 MHz.
20161115
+ Added the Bioshock Governor.
+ Added the Lionheart Governor.
+ Added the Nightmare Governor.
+ Added the Darkness Governor.
- Removed FIOPS I/O Scheduler.
- Removed ZEN I/O Scheduler.
Removed extra I/O schedulers due to recurrence of the random reboots.
20161114
+ Added ZEN and FIOPS I/O Schedulers.
20161109
+ Disabled DVSF INPUT BOOST, which locked the CPU at 1267 MHz when you touch the screen or use the SPEN. Now you can use CPU boost in Kernel Aduitor to select the amount of boost you want when input is detected (or not to boost at all).
+ Started over from the ground up to get rid of the random reboot problem.
Keep in mind:
Just something to keep in mind, these kernel features (more as they are added) are not always enabled by default. You will need tools like the Kernel Adiutor app to control, enable, or use these features.
Any are welcome to chime in on thoughts, requests, and settings! Be sure to stay tuned, more will be added regularly!
I am aware of kernel vulnerability CVE-2016-5195 "Dirty C0W" and am working on implementing a fix to secure these kernels from that vulnerability. If you need information about it, you can read up on it here:
https://github.com/dirtycow/dirtycow.github.io/wiki/VulnerabilityDetails
AlaskaLinuxUser said:
I am aware of kernel vulnerability CVE-2016-5195 "Dirty C0W" and am working on implementing a fix to secure these kernels from that vulnerability. If you need information about it, you can read up on it here:
https://github.com/dirtycow/dirtycow.github.io/wiki/VulnerabilityDetails
Click to expand...
Click to collapse
U could share the kernel buiding lol I've been trying so hard to find files for gpu/cpu can u point me to those? Also how would I turn zimage into a boot.img..... the android kitchen thing is a little confusing
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
beany23 said:
U could share the kernel buiding lol I've been trying so hard to find files for gpu/cpu can u point me to those? Also how would I turn zimage into a boot.img..... the android kitchen thing is a little confusing
Click to expand...
Click to collapse
Beany23,
I can put together a little how to if you would like, I like working on kernels, it is a great learning experience, and it is fun. I over clocked my kernel on my phone, and am testing stability right now. The oc is small, but I made no increase in voltage or amperage, so it is a free boost. I plan to post it tomorrow. Working on kernels is really a lot of fun.
Aaren11 said:
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
Click to expand...
Click to collapse
Aaren11,
Yes, I agree. I have disabled the boost in my testing, but then could not get the kernel to boot. The kernel I am working with has many of Mickey378's fingerprints on it, so I am sorting some of those out. Then I can delve more into those. For instance, when I run " make mrproper " it looks for /home/mickey/android...... And errors, so I am trimming his work while maintaining the great work he did to actually make it function for AOSP ROMs. I also am experimenting with other kernel sources like OldDroid's and others. Keeping in mind that only Mickey had a 100% fully functional ROM.
I do want to say though, I couldn't agree more, the mandatory touch boost is a pain. It should be adjustable, but it doesn't take when we set it.
But, work is progressing. One step at a time.
Sent from my unknown using XDA-Developers mobile app
I would love to try the kexec-hardboot kernel if you'd be kind enough to share. Multirom on this dying device would be nothing short of a miracle.
Sent from my unknown using XDA-Developers mobile app
AlaskaLinuxUser said:
Beany23,
I can put together a little how to if you would like, I like working on kernels, it is a great learning experience, and it is fun. I over clocked my kernel on my phone, and am testing stability right now. The oc is small, but I made no increase in voltage or amperage, so it is a free boost. I plan to post it tomorrow. Working on kernels is really a lot of fun.
Aaren11,
Yes, I agree. I have disabled the boost in my testing, but then could not get the kernel to boot. The kernel I am working with has many of Mickey378's fingerprints on it, so I am sorting some of those out. Then I can delve more into those. For instance, when I run " make mrproper " it looks for /home/mickey/android...... And errors, so I am trimming his work while maintaining the great work he did to actually make it function for AOSP ROMs. I also am experimenting with other kernel sources like OldDroid's and others. Keeping in mind that only Mickey had a 100% fully functional ROM.
I do want to say though, I couldn't agree more, the mandatory touch boost is a pain. It should be adjustable, but it doesn't take when we set it.
But, work is progressing. One step at a time.
Sent from my unknown using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes plz the would be awesome!!!
Aaren11 said:
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
Click to expand...
Click to collapse
Just a quick comment, mpdescision is actually a really big battery saver, unless you use a hotplugging governor. You can check this for yourself:
Enable mpd, enable nightmare, turn on caffeine or set screen to stay on 5 minutes. Watch the screen. Open KA and watch the CPU settings screen. The CPU will drop to one core at 300 MHz and pretty much stay there.
Then, disable mpd, now watch the CPU screen, you will see 3 or 4 cores on at all times.
In my other kernels for other Samsung phones, I always leave mpd on, and I can still over/under clock/volt. So I intend to leave mpd, but I do agree we need to ditch the mandatory touch boost, especially for just having the spen out.
Sent from my unknown using XDA-Developers mobile app
New kernel is up!
Hi all! Praise God, another successful kernel build. This time is just some very light CPU overclocking without any negative battery drain! See main posts for details and downloads!
20161027
+CPU overclocked to 2688 MHz without increasing voltage or amperage. (+39 MHz)
See commit here: https://github.com/alaskalinuxuser/...mmit/9bb23d0d9cc805bf7e1b8e3fe829fcbb0542af31
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AlaskaLinuxUser said:
Just a quick comment, mpdescision is actually a really big battery saver, unless you use a hotplugging governor. You can check this for yourself:
XDA-Developers mobile app
Click to expand...
Click to collapse
Errr...Alaska? I wasn't contending that mpdescision (a hotplug) is somehow less energy effcient than NO HOTPLUG. But it is one of the least effcient ones out there. Espceially when over or underclocking. Because Mpdesicion will override anything other than the stock clocks.
Also unless you disabled it, Nightmare does it's own hotplugging.
Aaren11 said:
Errr...Alaska? I wasn't contending that mpdescision (a hotplug) is somehow less energy effcient than NO HOTPLUG. But it is one of the least effcient ones out there. Espceially when over or underclocking. Because Mpdesicion will override anything other than the stock clocks.
Also unless you disabled it, Nightmare does it's own hotplugging.
Click to expand...
Click to collapse
"Nightmare
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery. In addition to the SoD is a prevention because it usually does not hotplug."
http://ajgupta.github.io/android/2015/01/28/CPU-and-GPU-governors/
As you can see from my previous posts, if you disable mpd in KA, then you can watch the CPU cores. Nightmare will not turn them off except in rare instances on my phone with the screen on. That is one of the principle differences between Nightmare and PegasusQ.
Also, mpd is currently accepting my overclock input in the kernel. So mpd doesn't always have to cause problems with over/under frequencies, I am no expert, but I believe this stems from how the table is built.
In either event, there are a lot of really great hotplugging options, on that we agree. Now, less you think I am being facetious, I actually quite enjoy your input and discussion, so please don't take this as anything other than great discussion. The great thing about Android/Linux/kernels is that they are like ice cream, with so many flavors, everyone is bound to find one they like, or a combination that they think is the best, and there will always be a difference of opinion.
I also still have a lot to learn on the subject myself.
beany23 said:
Yes plz the would be awesome!!!
Click to expand...
Click to collapse
Beany23,
Still a work in progress, but for what it's worth, here is the guide:
http://forum.xda-developers.com/note-edge/general/guide-build-aosp-roms-kernels-note-edge-t3488840
AlaskaLinuxUser said:
Beany23,
Still a work in progress, but for what it's worth, here is the guide:
http://forum.xda-developers.com/note-edge/general/guide-build-aosp-roms-kernels-note-edge-t3488840
Click to expand...
Click to collapse
Can u tell me where the files are regarding cpu/gpu? And one more thing....I'm so glad someone has some love for this device lol great work and keep on keepin!
AlaskaLinuxUser said:
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery. In addition to the SoD is a prevention because it usually does not hotplug.".
Click to expand...
Click to collapse
Dammit, I misread that very same passage. Ah well thanks for the correction.
AlaskaLinuxUser said:
Also, mpd is currently accepting my overclock input in the kernel. So mpd doesn't always have to cause problems with over/under frequencies, I am no expert, but I believe this stems from how the table is built..
Click to expand...
Click to collapse
That's definatley good news. On TW, any kernel with interactive would allow mpdescision to bump the clocks to stock values. Disabling mpdescision could make your under or overclock stick,but then you'd have no hotplugging.
AlaskaLinuxUser said:
I actually quite enjoy your input and discussion, so please don't take this as anything other than great discussion. The great thing about Android/Linux/kernels is that they are like ice cream, with so many flavors, everyone is bound to find one they like, or a combination that they think is the best, and there will always be a difference of opinion.
Click to expand...
Click to collapse
Likewise, I'm honestly beyond grateful someone finally started making non-TW ROMS and kernels for this device, and I'm always interested for a good Android discussion. Especially when it drives progress like this.
beany23 said:
Can u tell me where the files are regarding cpu/gpu? And one more thing....I'm so glad someone has some love for this device lol great work and keep on keepin!
Click to expand...
Click to collapse
The CPU Governor files are in the drivers/cpufreq/ folder, and all start with cpufreq_{DRIVERNAME.c}.
E.G. Nightmare = cpufreq_nightmare.c
You can read about it in more detail on Post #8 of the guide.
AlaskaLinuxUser said:
The CPU Governor files are in the drivers/cpufreq/ folder, and all start with cpufreq_{DRIVERNAME.c}.
E.G. Nightmare = cpufreq_nightmare.c
You can read about it in more detail on Post #8 of the guide.
Click to expand...
Click to collapse
I meant the frequency tables lol
Introduction
Hello everyone! Some of you might recognize me from the Xthermal Fast Charge thread, where I had earlier created and posted unified zips for modifying the stock thermal config file on the Nexus 6P, combining the work of two different mods, namely CTTMod and Xthermal Fast Charge Mod.
Since I was earlier maintaining my unified zips in the Xthermal Fast Charge Mod thread, I have now decided to create a separate thread for them since there is still interest and I don't want to unnecessarily clutter somebody else's thread. Let's get straight to it then!
Detailed Information
CTTMod - Thread Link
When CTTMod was initially released, it changed certain values in Nexus 6P's stock thermal file to raise the temperatures at which the phone would start to use thermal throttling. This change led to an increased overall performance and the phone could be used for a longer period of time without any crippling of performance due to thermal throttling, at the cost of heat. Therefore, after using this mod, the phone would feel slightly warmer as compared to how it would've felt if this mod had not been used, but with higher sustained performance.
Xthermal Fast Charge Mod - Thread Link
When Xthermal Fast Charge Mod was initially released, it also changed certain values in Nexus 6P's stock thermal file to raise the temperatures which prevented the charging current to exceed a certain value (usually ~1500 mAh to 1700 mAh) even though the stock OEM charger was capable of delivering a current upto 3000 mAh. This change led to an increased average current drawn (~2600 mAh to 2800 mAh), thereby leading to a decrease in the time taken by the phone to charge, again, at the cost of heat. Thus, a faster fast charge.
Unified Thermal Mod
Since both the base mods target the same stock thermal file, they can't be used together and using one would override the changes done by the other. In other words, one can only use CTTMod or the Xthermal Fast Charge Mod, exclusively. My unified thermal mod provides a workaround for this by taking the best from both of the above mentioned mods and combining their changes into one file, packaged into a Magisk module/TWRP flashable zip, so that one can take the advantage of both, increased performance due to an increase in thermal throttling temperature limits as well as a faster fast charge.
Compatibility
Device(s)
Nexus 6P
ROM(s)
All ROMs
Android Version(s)
Android Marshmallow 6.x.x
Android Nougat 7.x.x
Android Oreo 8.x.x
Android Pie 9.x.x
Android Q 10.x.x
Download
Direct Link
Important Read-Me Points
Installation/Uninstallation
In case you wish to install the modified libraries directly in the system partition and not as a Magisk module, then add "sysover" (without the quotes) to the zip name and flash it via TWRP.
The zip will abort the installation if you try to flash it on any other device except the Nexus 6P and if you aren't running Android Marshmallow, Nougat, Oreo, Pie or Q.
The zip auto-detects your Android version and installs the correct modified thermal configuration file automatically.
To uninstall the mod, just reflash the zip via TWRP and it will undo any changes it did (whether installed as a Magisk module or directly in the system partition).
General
The mod only works with the stock OEM charger. If you're using a third party charger (irrespective of the fact whether it supports Qualcomm QuickCharge or any other fast charge capability) this mod won't work.
The lower your battery percentage is, the faster your phone will charge, i.e. as the battery charge percentage increases, the current drawn by the phone will decrease. This is stock behaviour.
The mod doesn't change the USB charge current. That is controlled by the kernel.
Regarding the thermal driver, it is preferred that you enable msm_thermal and disable core_control for effective results. However, if doing that causes issues for you (for example, cores don't come online automatically after going offline while using msm_thermal), then disable msm_thermal and enable core_control via a kernel tuning app, like EX Kernel Manager.
If possible, avoid playing games/use performance heavy apps while the phone is charging. Doing so won't cause any issues, but it is preferred not to do so while the phone is on charge.
Disclaimers
I am not the original developer of the base mods used, i.e. CTTMod and Xthermal Fast Charge Mod. I merely combined the two since they couldn't be used together. I take no credit for the original work. Please direct all your thanks and/or donations towards @Robshr and @ravinder0003, the original developers of the mods.
You are doing this at your own risk. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you are unsure of how to go about something.
Thanks To
@Robshr, for his work on the original CTTMod
@ravinder0003, for his work on the original Xthermal Fast Charge Mod
@Zackptg5, for Unity Installer and all the work he's ever done for the community
@topjohnwu, for Magisk and all the work he's ever done for the community
All of you guys for viewing this thread and using the mod
Changelog
v1.0 - Initial release for Magisk v14.0
v1.1 - Updated to include changes from CTTMod's latest release for Android 8.x Oreo
v2.0 - Update for Magisk v15.0
v3.0 - Update for Magisk v17.0
v4.0 - Updated the zip base to the Unity Installer template
v5.0 - Added support for Android 10, updated the base template to Unity v4.4 and EOL update
OP Information
Thread Update Information
Created: September 15, 2017
Last Updated: September 29, 2019
Source Code
GitHub
@shadowstep
So you are here...
Nice mods work great
phantom146 said:
@shadowstep
So you are here...
Click to expand...
Click to collapse
Haha! I'm actually still there, but decided to keep this going even though I don't have the device anymore, but have a few testers who are available to help, so why not!
adame09 said:
Nice mods work great
Click to expand...
Click to collapse
Thank you!
Thanks for this mod! Working great on Oreo (superXE Rom with ElementalX).
Working perfect here too. Thank you
Sent from my Nexus 6P using Tapatalk
@shadowstep I would really love to try this but unfortunately, I live in a tropical country where we have above normal temperatures. The external temperature is hot enough, and if I did this, I'm risking global warming with my angler
phantom146 said:
@shadowstep I would really love to try this but unfortunately, I live in a tropical country where we have above normal temperatures. The external temperature is hot enough, and if I did this, I'm risking global warming with my angler
Click to expand...
Click to collapse
Haha, come on now, I'm not far from the Philippines (I'm in India) and I gave it a shot. Jokes apart, I know what you mean man. For us, in summers especially, this might not be the best mod to use on a daily basis, more so if the usage is heavy. In winters, however, it's a different story entirely, and I found this mod really helpful.
shadowstep said:
Haha, come on now, I'm not far from the Philippines (I'm in India) and I gave it a shot. Jokes apart, I know what you mean man. For us, in summers especially, this might not be the best mod to use on a daily basis, more so if the usage is heavy. In winters, however, it's a different story entirely, and I found this mod really helpful.
Click to expand...
Click to collapse
Back at you, we don't have winter :laugh:
Right now i'm not gonna bake my already half-baked phone and almost dying battery. I'd stay off of thermal mod for now but im really eager to try cttmod out.
phantom146 said:
Back at you, we don't have winter :laugh:
Right now i'm not gonna bake my already half-baked phone and almost dying battery. I'd stay off of thermal mod for now but im really eager to try cttmod out.
Click to expand...
Click to collapse
Haha, oh we do, chilly ones!
Also, you might want to consider a battery replacement if you plan on keeping your 6P for some time. I got it done from the Huawei Service Centre in my area, and the original one didn't cost a bomb at all. After the change, my SOT started averaging 4.5-5 hours (up from 2.5-3 hours).
shadowstep said:
Haha, oh we do, chilly ones!
Also, you might want to consider a battery replacement if you plan on keeping your 6P for some time. I got it done from the Huawei Service Centre in my area, and the original one didn't cost a bomb at all. After the change, my SOT started averaging 4.5-5 hours (up from 2.5-3 hours).
Click to expand...
Click to collapse
Yeah i've really considerd replacing it and I've heard its quite cheap. Though last april or so I've heard somebody talking about battery replacement on PH and huawei said that they're running out of "stock" with angler. So I guess I better check it out. I might not be buying anyreplacement sooner or later but I have plans next yr to buy the OP6 or Pixel 2.
phantom146 said:
Yeah i've really considerd replacing it and I've heard its quite cheap. Though last april or so I've heard somebody talking about battery replacement on PH and huawei said that they're running out of "stock" with angler. So I guess I better check it out. I might not be buying anyreplacement sooner or later but I have plans next yr to buy the OP6 or Pixel 2.
Click to expand...
Click to collapse
Yep, like I said before, it's not expensive, so if you manage to get your hands on one, definitely go for a replacement. Hopefully, some are still available and not out of stock. Also, I'm not too keen on Pixels anymore, seeing how comparatively difficult it is for developers to get stuff working on it + they cost a bomb! That's why I went for OnePlus 5. Had Google stuck with the Nexus line-up, I would've never bought anything else to be honest, but well..
shadowstep said:
Yep, like I said before, it's not expensive, so if you manage to get your hands on one, definitely go for a replacement. Hopefully, some are still available and not out of stock. Also, I'm not too keen on Pixels anymore, seeing how comparatively difficult it is for developers to get stuff working on it + they cost a bomb! That's why I went for OnePlus 5. Had Google stuck with the Nexus line-up, I would've never bought anything else to be honest, but well..
Click to expand...
Click to collapse
Yep if only they continued nexus, I'm gonna be fanboy on nexus forever lol. Well im interested at nokia right now as well as android one, hope they get a good community tho
I'm on oreo stock rom but using Elemental kernel, which versión should I use? The Overclocked one or the stock frecuency kernel?
phantom146 said:
Yep if only they continued nexus, I'm gonna be fanboy on nexus forever lol. Well im interested at nokia right now as well as android one, hope they get a good community tho
Click to expand...
Click to collapse
Me too! :highfive: Coming to Nokia, they're definitely upping their game, but I'm not sure about the developer backing it will get vis-à-vis OnePlus; the latter has the best developer backing after Google. Android one is relatively new, so let's see where does it go. The new Mi A1 could be start of something great.
jsecruzvalencia said:
I'm on oreo stock rom but using Elemental kernel, which versión should I use? The Overclocked one or the stock frecuency kernel?
Click to expand...
Click to collapse
If while flashing the kernel, you selected the overclocked frequencies for your cores, then use the overclocked oreo variant of the mod. If you didn't make any changes in the frequency screen/aren't sure if you're overclocked or not, just use the normal oreo variant and you should be good.
I notice higher temperatures as expected.
Actually my N6P reached 44.5C, are we fine?
I am talking about battery temperature
Actually I just answered my question, flashing Oreo stock throttling .zip
Thanks for the mod, no offence.
Have fun, George.
How to know if my kernel is overclocked or not? I am using Flash kernel v2.5
teohguangli said:
How to know if my kernel is overclocked or not? I am using Flash kernel v2.5
Click to expand...
Click to collapse
Not overclocked.
Pipiou211 said:
I notice higher temperatures as expected.
Actually my N6P reached 44.5C, are we fine?
I am talking about battery temperature
Actually I just answered my question, flashing Oreo stock throttling .zip
Thanks for the mod, no offence.
Have fun, George.
Click to expand...
Click to collapse
Yes, that is expected, because the mod increases performance at the cost of heat, so temperatures will be slightly higher as compared to stock. It's been mentioned in the OP as well.
Also, no offence taken, at all. Feel free to use/not use the mod, whatever you feel comfortable with. Thanks for stopping by!
teohguangli said:
How to know if my kernel is overclocked or not? I am using Flash kernel v2.5
Click to expand...
Click to collapse
You can use a kernel manager app like EXKM or Kernel Adiutor to check that. If the maximum CPU frequencies for the little and big cluster are 1708 MHz and 2054 MHz, respectively, then you're running an overclocked kernel. However, if they are 1555 MHz and 1958 MHz, respectively, then you're running a non-overclocked/stock frequency kernel.
I know asking for ETA isn't allowed but could you do a fast charge only version for Oreo? I really dislike the thermal mod but would love to have the fast charge one