TruWhite MOD for Overload Kernel by RandomDelta
I have put together my settings for extracting the best performance with minimal effect on battery life from our Le eco Le 2. I have calibrated the display to true paper white colors and increased saturation to emulate AMOLED displays. Some of you may not like that so you can turn down the color saturation. While changing Voltage settings, please note that not all processors are built the same and yours might not be able to withstand the overclock. If for some reason there are random freezes, Just lower the voltage by 5mv after rebooting. The color profile has been extracted from Le eco vivid color mode EUI 5.9 with boosted color saturation . Not all displays are created equal so the color profile may not be perfect for you. Just adjust RGB by ±5 to get what works best for you. Word of caution, while playing games the phone can get pretty warm. If it concerns you, lower the throttle temperature and Temperature limit under thermal at the cost of some performance. Screen on time is 8 hrs at 50% brightness and 6 hrs at 100% brightness. I recommend 90% for optimum usage. Download the attached zip and adjust settings as in the pictures. Performance Is up by 20% from stock settings and battery usage is 5%less than stock settings. Performance test screenshot is also attached.
Hope you like it . Do comment on how you like it
Suggestions and Requests are welcome.
XDA DevDB Information
TruWhite MOD for Overload Kernel by RandomDelta, Device Specific for the LeEco Le 2 (x52X)
Credits
renjian- for making Overload Kernel
RandomDelta - For Custom Settings and optimizations.
If you don't have Overload Kernel, you can download your preferred version from the link given below
https://androidfilehost.com/?w=files&flid=283143
Instructions
1. Download and flash preferred version of Overload Kernel in Twrp
2. Install Kernel Adiutor and give it Root privileges
3. Download and extract image files from the zip file for corresponding Overload Kernel Version in this post.
4. Compare settings in screenshot images in zip to the settings in Kernel Adiutor and set them to values mentioned in the screen shots. Set them to be applied on Boot. Wait for a few seconds and the new settings will have applied .
Notes:
1. Distribution of TruWhite Mod files directly is not allowed. You are requested to drop a link to this page on the thread you wish to.
2. This is not a flashable zip
3. .json files will be made available on request. Using the .Json file you can import it in kernel Adiutor (donate version),set that to apply on boot and hence apply the customizations in a single click rather than having to fiddle with various settings.
Donation
If you like my work, you can donate me a cup of coffee.
UPI: [email protected]
Changelog
v1.0
1.Smoother I/O performance than stock
2.Increased CPU and GPU performance than stock
3. Fine tuned color profile for a more color accurate vibrant display leading to a more enjoyable media playback experience and Better visibility of small targets in competitive games.
4.Tuned CPU voltages to further increase performance with minimal effect on battery
5. Thermals tuned for delivering maximum performance without thermal throttling .
6. Optimized Memory manager for multi-tasking
7. LKT is not recommended
8. Optimized only for Overload Kernel v4.14
v1.1
1. Increased I/O performance
2.Changed screen color calibration to reduce eye strain
3.Now compatible with LKT
4.Optimized for Overload Kernel v4.14 and v4.15
v1.2
1. Optimized for Overload Kernel v4.19
2. Optimized battery life further.
3. LKT balanced or battery mode suggested as add on.
4.Reduced I/O lag
5. Removed Performance test screenshot
6.Also applicable to Overload Kernel v4.17, v4.18 and v4.20
v1.3
1. Optimized for Overload Kernel v4.21
2. Improved Standby time
3. Improved peak performance by upto 7%
4. Changed screen color calibration to fix oversaturated yellows
5. I/O operations are now less battery intensive
6. Improved Network Performance for faster downloads
7. Optimized thermal performance further
8. Also applicable to Overload Kernel v4.22
9. Color Profile and Thermal calibration is no longer optimised on devices running June 2019 patch or newer due to updated libs.
v1.4
1. Fixed Color Profile and Thermal profile for optimum performance.
2.Tuned Kcal to be slightly warm to reduce eye fatigue.
3. Color Calibration based on Redmi Note 7 Pro Increased Contrast (Cool) display profile.
4.Improved Standby time significantly.
5. Reduced idle battery drain
6. Increased GPU performance while gaming.
7.Tuned Cpu Voltages to prioritise performance under heavy load and battery under light load.
8. Unable to fix I/O lag. Still looking into how to solve it. Help is appreciated. Virtual Memory needs to be tweaked further.
9. Optimized for Overload Kernel v4.23
This project has been abandoned as Overload Kernel is no longer being updated
Version information
Status : Stable
Current Stable Version : v1.4
Latest Version :v1.4
Final Version :v1.4
Created 25-01-2019
Last Updated 28-07-2019
Reserved
Can this for 4.15?
How about gaming?
Its good or nah?
Restian Rony said:
Can this for 4.15?
How about gaming?
Its good or nah?
Click to expand...
Click to collapse
Every Version of kernel is different from each other and features pop up and disappear with updates. So certain customizations mentioned in this guide may not be available in a different kernel version. Also, optimum values tend to differ from kernel version to version. So yeah, it'll work in v4.15 but you might not get the best results.
It's good for gaming coz you get a 20% performance boost over stock. You can improve performance further by changing CPU and GPU governers to Performance, increasing minimum CPU and GPU speed, increasing minimum number of big cores online and increasing the temperature limits but it will adversely affect your thermals and battery life.
RandomDelta said:
Every Version of kernel is different from each other and features pop up and disappear with updates. So certain customizations mentioned in this guide may not be available in a different kernel version. Also, optimum values tend to differ from kernel version to version. So yeah, it'll work in v4.15 but you might not get the best results.
It's good for gaming coz you get a 20% performance boost over stock. You can improve performance further by changing CPU and GPU governers to Performance, increasing minimum CPU mad GPU speed, increasing minimum number of big cores online and increasing the temperature limits but it will adversely affect your thermals and battery life.
Click to expand...
Click to collapse
Wow thanks mate
Love u ?
Update
V1.1 now available.
Will release performance biased mod shortly. Hope you all like it
I can not find the core control setting screen (the one attached)
Why not share the .json profile file directly?
danyel980 said:
I can not find the core control setting screen (the one attached)
Why not share the .json profile file directly?
Click to expand...
Click to collapse
Are you on Overload kernel v4.14. Please ensure that you are. Even if I share the Json file, that setting won't be applied because that setting doesn't exist for the kernel you are on. So it's pointless. Plus to apply the Json file, you need to have the pro version of Kernel Adiutor , which most of us don't. If you want the Json file, it's linked below.
It's the v1.1 Balanced profile
RandomDelta said:
Are you on Overload kernel v4.14. Please ensure that you are. Even if I share the Json file, that setting won't be applied because that setting doesn't exist for the kernel you are on. So it's pointless. Plus to apply the Json file, you need to have the pro version of Kernel Adiutor , which most of us don't. If you want the Json file, it's linked below.
It's the v1.1 Balanced profile
Click to expand...
Click to collapse
yes, I'm overloaded 4.14 but I can not find the screen in question.
thanks for the .json file, even if you say in effect it does not make much sense unless you can apply the whole configuration. I would like to understand why I do not find the setting, however
danyel980 said:
yes, I'm overloaded 4.14 but I can not find the screen in question.
thanks for the .json file, even if you say in effect it does not make much sense unless you can apply the whole configuration. I would like to understand why I do not find the setting, however
Click to expand...
Click to collapse
Maybe there was some error during the flashing process. You should redownload the kernel And flash it again. It should solve the issue.
Custom settings for Overload Kernel v4.19 has been released
Settings for v4.20 are the same as for v4.19. So I'm not reposting.
Settings for v4.21 will be released soon.
Thanks for the great work
Waiting for v21 TIA
TruWhite MOD v1.3 for overload kernel v4.21 has been released!
I will not be releasing performance biased mod because in my opinion the battery trade off associated is not worth the tiny performance gain.
RandomDelta said:
TruWhite MOD v1.3 for overload kernel v4.21 has been released!
I will not be releasing performance biased mod because in my opinion the battery trade off associated is not worth the tiny performance gain.
Click to expand...
Click to collapse
After downloading and flashing Ol 4.21, it is showing 4.20 of 17th Feb..... What to do?
MpS005 said:
After downloading and flashing Ol 4.21, it is showing 4.20 of 17th Feb..... What to do?
Click to expand...
Click to collapse
Don't worry . You are on v4.21. Renjian forgot to update the build release key description.
RandomDelta said:
Don't worry . You are on v4.21. Renjian forgot to update the build release key description.
Click to expand...
Click to collapse
but my last option for max frequencies for big cpu is 1478mhz. There's no 1800mhz or around it
MpS005 said:
but my last option for max frequencies for big cpu is 1478mhz. There's no 1800mhz or around it
Click to expand...
Click to collapse
It's for little CPU. You might be confused. Little CPU max out at 1478mhz in v4.21. Send screenshots . I might be able to help
RandomDelta said:
It's for little CPU. You might be confused. Little CPU max out at 1478mhz in v4.21. Send screenshots . I might be able to help
Click to expand...
Click to collapse
I sorted out. It was showing wrong info. It was showing 1478mhz in big and 1843mhz in small. LOL. I force stopped app and rebooted phone. Then, it was correct.....Wait for results now:fingers-crossed:
Related
motley kernel for the Nexus 7 and Jellybean
Disclaimer: You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!
ROM devs/cooks: If you want to use this kernel in your ROM, I am fine with that, but please include a "thanks" and a link back to this thread. Thanks!
Requirements (please read carefully and visit the other dev threads as necessary)
You must be unlocked and rooted.
You must have custom recovery installed (CWM or TWRP) to install the kernel.
Busybox is required for init.d support.
Do a backup using custom recovery (CWM or TWR) so you can restore your boot.img and ROM if necessary!
Have your ROM zip in /sdcard so you can restore your ROM if necessary.
System Tuner is recommended for tuning the CPU, especially for voltage control.
Main Features
GPL compliant - source is kept up to date at github.com and released at the time the kernel is released to the public for all builds. Ask other devs to do the same!
Asus\Nvidia\Google Linux 3.1.10 base. All stock features are supported (camera, OTG, NFC etc.)
OC to 1.6GHz (optional)
Voltage control - be careful to not save the setting on boot until you are 100% sure!
GPU OC from 416 to 520MHz (default is 446, adjust as you wish up to 520MHz)
Dynamic EDP - allows EDP to remain enabled (safer), but with an added simple temperature throttle switch (based on Asus Prime)
Compiler optimizations (-O2) - using Linaro 4.7 ARM toolchain
I/O schedulers - row (default), SIO, V(R), CFQ, NOOP, and deadline
TCP Congestion Control - default cubic + several different algos to choose from.
ZRAM - must be enabled by a script
Governors - Interactive (default), Performance, OnDemand, PowerSave, Conservative
initramfs - insecure (your ROM must have busybox)
CIFS/UTF8, NFS, NTFS r/w, TUN - built-in, no need for any kernel modules
fsync sysfs enable/disable switch (defaults to fsync enabled)
kexec with hardboot (for supporting Linux/MultiROM)
Many other misc patches and tweaks (see github link below)
Install:
Check the requirements above!
Flash the zip using custom recovery (no need to wipe anything)
See post 2 for performance tweaks and more info
build #249 for Jellybean 4.2.2 - WiFi and 3G 2013-02-24
Added ability to change GPU clock speed at runtime (referenced franco, morific, and metallice git repos)
Added row io scheduler and set as default (Tatyana Brokhman)
Added TCP Congestion Control, several different algos to choose from. Default is cubic (stock).
Added optimized ARM RWSEM (Ezekeel)
Input patch (Henrik Rydberg)
View attachment motley_anykernel_N7_build_249.zip
build #247 for Jellybean 4.2.2 - WiFi and 3G 2013-02-17
Merged 4.2.2 patches
Updated Linaro toolchain to 2012.12
View attachment motley_422_nexus7_anykernel_build_247_446GPU.zip
build #246 for Jellybean 4.2.1 - WiFi and 3G
kexec\MultiROM support
Download from here since I posted in the MultiROM thread
build #244 for Jellybean 4.2 - WiFi and 3G - Recommended for WiFi and 3G on 4.2.x
446 GPU build (stock + 30MHz). Let's see if this fixes touchscreen issues for those having them. My theory is that after the GPU heats up, this starts to affect touchscreen behavior on some devices. This is likely what happened to me on build 234 when I was testing. The GPU definitely gets hot on this device even with normal usage at 484+. At 446 this doesn't happen. IMHO, we are reducing the life of the device by overheating the GPU repeatedly. My Antutu scores actually tested higher after I flashed the 446 build.
Supports Android Jellybean 4.2.x
Reverted some commits from 233
Removed KSM from config, no ROM is using this AFAIK
Panel clock reduced to match Nvida cardhu sources (74180000). Having the panel clock cranked up fakes out scores on some benchmark tests, but adds no real value.
View attachment motley_nexus7_anykernel_build_244_446GPU.zip
Previous builds and release notes
build #234 for Jellybean 4.2 - First properly working 3G build
Supports Android Jellybean 4.2.x
Only change - added CONFIG_USB_NET_RAW_IP=y to hopefully address any issues with 3G (reported working by DiamondBack)
View attachment motley_nexus7_anykernel_build_234_484GPU.zip
build #233 for Jellybean 4.2 - if you don't have issues with GPU OC @484, this build may work well for you.
Supports Android Jellybean 4.2.x
Updated to latest Linaro toolchain 2012.10.22 and tweaked some compiler options.
Should support 3G as I have merged the Google patches, but I have not tested this.
Removed WiFi PM_FAST toggle as I see no need for this (PM_MAX for better battery is already the default in stock)
Stopped logging temp warnings until lit gets to 65C near the EDP throttle limit.
Quad-core tweaks - referenced showp1984's bricked grouper kernel source
See github for other minor details.
View attachment motley_nexus7_anykernel_build_233_484GPU.zip
build #232 - Recommended for WiFi on 4.1.2
Added support for Android Jellybean 4.1.2
Updated to latest Linaro toolchain 2012.10.22.
View attachment motley_nexus7_anykernel_build_232_484GPU.zip (GPU OC 484MHz)
stable v1.1.1 - builds #218-220 - Recommended for WiFi on 4.1.0 or 4.1.1
Supports Android Jellybean 4.1.1 or 4.1.0
DVFS tweaks and drop top cpu frequency to 1600, not much is lost and it should now be stable for everyone I hope. We pushed the envelope to 1.7 and 1.624 and now we are back to real world sensible decisions. My Nenamark2 520 GPU scores actually went up.
Dynamic EDP temp adjusted from 67 to 68C to catch temp notifier quicker when cooling back down.
Other miscellaneous patches
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
View attachment motley_anykernel_nexus7_1.1.1_NoGPUOC_build_220.zip (GPU stock 416GHz)
View attachment motley_anykernel_nexus7_1.1.1_GPU484_build_219.zip (GPU OC 484MHz)
View attachment motley_anykernel_nexus7_1.1.1_GPU520_build_218.zip (GPU OC 520MHz)
alpha v1.1.0 - builds #213-215
Added fsync sysfs enable/disable switch (thanks Ezekeel). fsync is still enabled by default. For more info and how to disable, see post 2.
Experimental: now forging speedo id 4 and process id 2 so that EDP limits are slightly raised and it narrows everyone down to a common DVFS record for everyone. Raised Dynanic EDP governor to 67C (from 60C) to give a little more room before edp is allowed to enable.
Minor cpu voltage table tweaks aiming for slightly better battery for those that don't undervolt.
Lowered the cold offsets from 50 to 25 for the top 4 cpu voltage slots. This will give folks a little more breathing room when undervolting and may help cold performance a bit if your voltages are lowered close to their lower limit.
Deadline i/o scheduler (morfic's secret 1:1 sauce that I remember back from my Iconia A500 days!). SIO is still the default, but we can try it out and see what we think.
OnDemand really wasn't usable in it's stock state since it was so laggy, so I have made some tweaks to the tuneables and it seems to be better now for those that want to give it a spin. Interactive is still the default governor.
cpu transtition latency lowered - fairly certain that it only affects OnDemand governor and not Interactive (reference morfic and http://permalink.gmane.org/gmane.linux.ports.tegra/1649)
Reverted most of the adjustments to the tegra 3 algorirthim for bringing cpus online and offline. I think it livened it up, but at the expense of battery.
Added kernel config option BCMDHD_WIFI_PM (thanks Ezekeel). See post 2 on how to enable it (not recommended unless you have music steaming issues when the screen is off). Not yet tested.
Other miscellaneous tweaks
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
View attachment motley_anykernel_nexus7_1.1.0_NoGPUOC_build_214.zip (GPU stock 416GHz)
View attachment motley_anykernel_nexus7_1.1.0_GPU484_build_213.zip (GPU OC 484MHz)
View attachment motley_anykernel_nexus7_1.1.0_GPU520_build_215.zip (GPU OC 520MHz)
stable v1.0.12 - builds #175-177
Changed highest frequency back to 1.624GHz and core voltage back to 1200mV. After experimenting with higher core voltages and 1.7GHz probing our limitations, it just doesn't seem right on this tablet. Why fry the butter?
CPU voltage is capped at 1237, so don't set it higher than that if tuning.
Refresh rate now adjusted with GPU OC clock at compile time. Higher FPS should be realized at 484 and 520 for most (thanks to clemsyn for sharing his research and findings)
Adjustments to the tegra 3 algorirthim for bring cpus online and offline, especially for the OC frequencies.
Fixed GPU clock compile time switch. Removed 500MHz choice.
Set cpu frequency policy to 1.3GHz on startup. This should help with heat build-up on startup and users where the highest OC clock rate is not desired.
Lowest brightness setting set back to stock since several users were requesting it (18 back to 13).
Minor adjustment to the interactive governor to make it slightly more responsive when demands increase.
PowerHAL change so it doesn't mess with a couple other interactive governor tunables on init.
All frequencies throughout the power range should be used in a more balanced manner.
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
View attachment motley_anykernel_nexus7_1.0.12_NoGPUOC_build_177.zip (GPU stock 416GHz)
View attachment motley_anykernel_nexus7_1.0.12_GPU484_build_176.zip (GPU OC 484MHz)
View attachment motley_anykernel_nexus7_1.0.12_GPU520_build_175.zip (GPU OC 520MHz)
alpha v1.0.11 - builds #126-128
Changed highest frequency from 1.624 to 1.7GHz
Increased core voltage for the highest frequency to 1250mV. This should bring some increased stability at the highest two overclock frequencies (thanks to clemsyn and Pinoyto for their help)
Tweaked DVFS table for the GPU. It should now scale a bit better and still bring the same performance and the top end.
Lowest brightness setting increased from 13 to 18 (thanks to clemsyn). Lets give this a try and we can increase it further if need be. The brightness levels can be tweaked on the ROM side as well in the N7 device tree, at least when you build from scratch, so we don't want to be too limiting here.
PowerHAL fix now included /vendor/lib/how/power.grouper.so (thanks to imoseyon). See this post to see the code I changed.
(Removed download links since many were reporting random reboots. I think v1.0.12 is better anyhow)
stable v1.0.10 - build #110/111
CPU frequecies back to 1400, 1500, 1600, and 1624 (leaving the new highest setting)
DVFS table tweaks
Frequency table fix fix for 1624 (thanks to Clemsyn for bringing to my attention!)
Only stock and 484MHz GPU OC version - code switch is still there for those that want to compile and experiment. Moving beyond 484 doesn't show any benefit. My best Nenamark2 score 62.7 was achieved on 484MHz.
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
experimental v1.0.9 - builds #102-105
CPU OC to 1.624GHz - higher end CPU frequencies are now at 1408, 1504, 1600, and 1624 (old 1400, 1500, 1600, N/A)
DVFS table tweaks - Just in case, please note and then unset your saved voltage control settings before using the new version.
GPU versions stock, 484, 500 and 520MHz builds for testing
Added a GPU OC kernel config choice switch to allow compile time selection of GPU speed (446, 484, 500, or 520MHz).
NTFS r/w enabled
PegasusQ governor no longer built in, but code remains if we want to look further into when time allows.
Reduce some temp reporting kernel log spam until the temp gets a little higher
stable v1.0.8 - build #77/78
Added PegasusQ governor - experimental only, not enabled by default (thanks Samsung SGSIII source and gokhanmoral for tweaks)
Revert "HACK: block fbearlysuspend to not break androids crt-off animation"
Added LulzActive governor, but not built-in due to issues.
stable v1.0.7 - build #70/71
Voltage Control tweak - let's ignore the highest freq slot for show and
save since it shows 1.6GHz twice in the voltage table in System Tuner.
We are are only allowing 1200mV for 1.6, so the top slot is not
currently used. See my notes in post 2 about voltage control.
cpu-tegra: let's skip the temporary downclock and kernel log spam if the
custom Dynamic EDP throttle is not currently enabled.
ARM/VFP compiler optimization
compilation: fix annoying and serious warnings (thanks faux123!)
video: tegra: host: Fix error case memory leaks
When a submit fails, the related nvhost_job is not freed. Add an
explicit free. Also, 3D is mapping the save buffer, but it is not
unmapped (Nvidia)
mm: Ensure pte and pmd stores ordering (Nvidia)
Get rid of some more kernel log spam.
HACK: block fbearlysuspend to not break androids crt-off animation
(thanks codeworx, drewis (repo) and aaronpoweruser for pointing it out). This is untested (by me), but this may help with ROMs that
have this functionality (AOKP etc.)
cpu-tegra3: modified the hot-plug governor down_delay to be 1s
instead of 2s
stable v1.0.6 - build #47/48
GPU clock increased to 484MHz - Nenamark2 scores of 61+
More compiler optimizations (-fmodulo-sched, -fmodulo-sched-allow-regmoves, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-vectorize, -floop-interchange, -floop-strip-mine, -floop-block, -mfpu=neon )
Now using Koush's AnyKernel delivery method. Uses your existing ramdisk so you can easily use with any ROM.
stable v1.0.5 - build #39
Honor your max frequency fix - no more spikes
alpha v1.0.4 - build #38
Fixes units that can't OC (process_id = 3)
Linaro 4.7.1 toolchain -O2 (2012-06-25)
Increased panel clock rate - increases fps without further GPU clock Nenamark2 scores 59.6 best score so far for Nexus 7
ramdisk added back in boot 1.3GHz, but device still spikes to max allowed CPU freq sometimes (see update below, will be fixed in 1.0.5)
Minor clock and voltage adjustments - should run a bit cooler and use less battery.
Added GPU OC compile switch in case we want a non-OC GPU build.
Added some VPN/networking capabilities for those that need it (L2TP, IP_GRE_DEMUX,INET_AH, INET_XFRM_MODE_BEET)
Some unnecessary debugging options turned off. Should save kernel RAM usage.
Some say it made wifi signal stronger again for them, but I never had any issues. Might be the toolchain and its effect on the broadcom driver. Reports that it is better are fine with me!
alpha v1.0.3 - build #17
UV support, minor voltage adjustments
V(R) i/o scheduler added
ramdisk removed custom init.rc line...hope this will fix the stock units that weren't booting!
alpha v1.0.2 - build #6
Mild GPU OC from 416 to 446MHz - baby steps...its been rock solid so far. NenaMark 2 scores are up from 55 to 57.2fps. A future release may have two versions, one with GPU OC and one without.
Upgraded toolchain to GCC v4.6.3 optimized google version by ezterry, see http://forum.xda-developers.com/showthread.php?t=1686310)
alpha v1.0.1 - build #4
Limit frequency to 1.3GHz on boot. It can then be OC'ed from there. This should make it safer for those that can't OC or don't want to.
Changes to allow OC for Process ID's 0 and 1. Theoretically, these should be earlier release versions like IO and earlier.
alpha v1.0.0 - build #1
This initial alpha release is working well on a Nexus 7 16GB (Speedo ID 7/Process ID 2) on JB 4.1.1. There are no open issues that I know about. Looking for some advanced users and testers to give some feedback, and then we can hopefully make it even better!
Thanks to:
fordwolden - for his generous donation of a Nexus 7
Google and Asus for releasing a nice, open, and inexpensive tablet for the masses.
drewis (Andrew Sutherland) - for the base kernel on github
paulobrien - thanks for the CWM touch recovery
birdman and FadedLite for their Unlock\Rooting instructions
clemsyn for his ideas and insight
Git repo:
https://github.com/motley-git/Kernel-Nexus7
{
"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"
}
(http://www.gnu.org/copyleft/gpl.html)
More info
last_kmsg
Please provide the dmesg output or last_kmsg if you experience any issues (random reboot or crashes) that you think are attributed to the kernel. I ask that you please test with the default/stock kernel first for your rom before you blame the issues on this kernel. Wait for the tab to reboot, or if it doesn't wait long enough so you can capture a good log. If you place this on your /sdcard, it will be easy to capture. Boot into recovery, flash this zip, and then flash a known kernel that works. Then reboot, and go grab the last_kmsg in /sdcard.
View attachment LastKMESG.zip (thanks go to CekMTL, I always keep this handy since you gave it to me!)
Voltage Control
What is voltage control?
It is simply allowing for the cpu voltage to be changed on the fly for each frequency step. CPU voltage is typically lowered (undervolting) for certain frequency steps to conserve power. For an overclocked device, some devices need more juice to be stable than others. Voltage control allows others not to pay this penalty and they can lower the voltage as they see fit for their device and usage needs.
Is undervolting safe?
If the lowered voltage values you enter are stable for the tablet, then absolutely it is safe.
What are the benefits?
Better battery life and less heat
Additional Info on voltage control
Only System Tuner is displaying the DVFS table frequency labels correctly and I recommend that you use this if you want to play with voltage control. SetCPU is showing the scaling frequencies when it displays them in the UI, some of which are for the LP core. This is not correct and is misleading, so it is best not to use it for this kernel.
Since the tools available only allow for tweaking one DVFS table (the high powered G cores), voltage control is not currently possible for the LP core. It is not needed anyhow IMO and setting it too low could result in SOD. There is more battery saving to be had with the G cores anyhow if you are into this sort of tweaking.
The frequencies shown may have two values for one frequency. This is how it came with the factory kernel as well and I have only tweaked the top end of the DVFS table. It may seem weird, but this gives us direct access to the DVFS table. I would recommend keeping it as a staircase, just like Nvidia has it even though some frequencies are listed twice.
The freqs shown in the System Tuner display will match the DVFS table for the cpu_process_id for your tablet (seen in the kernel log at startup). All tablets won't display the same frequencies. There are at least two maybe three or four variants we have found so far for the Nexus 7 with Tegra 3 SoC #7.
Also, some may not know, but the tegra3 kernel also has automatic UV using a "cold" zone in where 50mV undervolting is done automatically when the cpu is cool. Take this into consideration when playing around.
GPU OC
Valid max GPU frequency is 416 - 520 MHz. If you try higher or lower clock speeds, it will fail and remain unchanged.
Examples:
Code:
echo 484 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Code:
echo 520 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Performance Tweaks
These are a couple of tweaks that many are using for faster benchmarks and better battery performance. Google it and decide for yourself if you like the risk or not. I recommend that you do a full backup in recovery and regularly backup your /data partion or cloud sync if you enable these options. Will many run them daily as I now do, there is some additional risk. These can be added to scripts and automated via init.d or other apps/tools that support them.
To disable fsync for better battery and better disk i/o performance:
Code:
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
To enable fsync for better data integrity (default)
Code:
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
Faster disk i/o - remount /data partition with noauto_da_alloc option (google it, better battery, less data integrity)
Code:
mount -o remount,noauto_da_alloc /data /data
TCP Congestion Control Algorithms
Only one can be set at a time, so only add one of the lines to your script. Here are some examples:
Code:
echo "reno" > /proc/sys/net/ipv4/tcp_congestion_control
echo "veno" > /proc/sys/net/ipv4/tcp_congestion_control
echo "vegas" > /proc/sys/net/ipv4/tcp_congestion_control
echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control
zRAM
What is zRAM?
This is a mainline kernel feature for Compressed RAM block device support (CONFIG_ZRAM)
http://en.wikipedia.org/wiki/ZRam
Like many of the other tweaks done in the Android world, ZRAM is another one of them that is controversial, probably because people only think in terms of immediate performance they can measure easily with benchmarks etc. *Here is my take...think I will add this to the Q&A section as well.
But, will it make my device faster? Will I score higher on benchmarks?
It depends, but for normal usage, the answer is no. zRAM is most useful for those that are configuring Android to be a true multitasking workhorse. For example, if I enable zRAM, open an bunch of apps at one time, and actually start to work towards depleting the memory of the system. *For example, say I open system tuner, a browser with several tabs, a word processing app, a game, and perhaps a picture viewing app or a movie. If I don't formally close out of each one by hitting back and just begin switching between apps and the home screen, you will see zRAM start showing benefits.*
If you tweak the Android memory and swappiness settings, this can also be useful in this type of environment.
How do I know it is initialized and working?
You can type "free" from an command line and see the swap space.
Also, you can look at the disksize to see if it is initialized
cat /sys/block/zram0/disksize
To see how much it is being used in your environment, you can look at the output from:
cat /sys/block/zram0/num_writes
cat /sys/block/zram0/num_reads
So, unless you have a heavy workload as stated above, then it won't be of a lot of use for normal Android users.
How do I enable zram?
It must be enabled by a script. Some ROMs may support activating it. If you need to do it yourself you have two choices.
1) Save this to a file and run the script from terminal, Script Manager or System Tuner.
2) Or better yet, save this to a file called 90zram (or whatever you prefer) in /system/etc/init.d and automate it (The ROM's ramdisk needs to supports init.d)
Code:
#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984
echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";
if [ ! -e /sys/block/zram0/disksize ] ; then
echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
echo "[90ZRAM]: Is this a ZRAM kernel?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
#find busybox in /system
bblocation=$(find /system/ -name 'busybox')
if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
echo "[90ZRAM]: busybox found in:" $bblocation;
echo "[90ZRAM]: Setting ZRAM disksize.";
echo $((100*1024*1024)) > /sys/block/zram0/disksize
echo "[90ZRAM]: Starting ZRAM...";
bblocation=${bblocation%/*}
cd $bblocation
./busybox mkswap /dev/block/zram0
./busybox swapon /dev/block/zram0
echo "[90ZRAM]: ZRAM activated.";
else
echo "[90ZRAM]: ERROR! busybox not found!";
echo "[90ZRAM]: Is busybox installed? Symlinks set?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
fi
fi
Flashed with CWR and it doesn't boot past the Google screen Is there something special I need to do?
*Edit*
I am on the new 4.1.1 "D" or whatever but right now I'm using the Atlantis "1.5" kernel and it works so I donno.
Thanks for another addition to the nexus 7 kernel community, love having different kernels to try.
Clienterror said:
Flashed with CWR and it doesn't boot past the Google screen Is there something special I need to do?
*Edit*
I am on the new 4.1.1 "D" or whatever but right now I'm using the Atlantis "1.5" kernel and it works so I donno.
Click to expand...
Click to collapse
Thx, please grab the dmesg output while booting or last_kmsg if you can. Working fine here, but this why I put it out as an alpha. Even if you boot off another kernel, if you can send a dmesg captured right after boot, that would help so I can see your SoC/Process ID numbers. There are two lines written just after boot with the info. On the Prime, we had different CPUs in some models, but it may just be a voltage issue. I have run Antutu and Quadrant several times without issues though. Not sure about the D update...I I have 4.1.1.
Edit: Version 1.0.1 released, please test again and leave feedback when you can. Please let me know when you received your tab. Is it an early IO version? If this doesn't do it, I most likely will need to increase voltages a bit. Hopefully I won't have to do this so we can keep battery life at it's best.
oh s^&*, you developing here also. oh yeah! glad to see you here buddy. so you have your nexus 7 already? now that i see you here also, i will be unlocking my nexus 7, once it arrives, sooner than i thought. welcome aboard...glad to see familiar faces around here
I had the same issue. Couldn't pass the boot screen after flashing. On 4.1.1 latest update as of July 15th
Sobai said:
I had the same issue. Couldn't pass the boot screen after flashing. On 4.1.1 latest update as of July 15th
Click to expand...
Click to collapse
Thanks, I am dying to take a look at a log to see how I am so lucky to have it working! I've added LastKMSG.zip to the OP. If someone with a booting problem can do the following, I would really appreciate it:
1) Put LastKMSG.zip on your /sdcard along with the newest kernel zip
2) Flash the kernel zip
3) Wait for it to boot, give it a few seconds and then hold power down to reboot if it doesn't do it on its own.
4) Go back into recovery and flash LastKMSG.zip
5) Flash another booting kernel or your current rom to recover.
6) Boot and retrieve the file /sdcard/last_kmsg
7) Attach the log here or PM me with a dropbox link or whatever.
Thanks!
Just got some good news from a gentleman that didn't have enough posts to share with us here yet, so he PM'ed me and said that I can share the details of his experience.
First report was more of the same, sounded familiar, more bad news...
Flashed your kernel and couldn't boot pasted Google screen. Restarted in to boot and couldn't get into recovery. Was stock rooted on the latest 4.11. Went back to stock. Looking forward to trying again, now I'm on Modaco's latest. I'll let you know how it goes.
Next report was good using the latest version in the OP. Not sure, but this may help others.
Thanks! This kernel is fantastic! Makes this thing a real beast! Sorry I didn't give you the info you asked for! I got it Thursday from GameStop. The problems may have stemmed from the fact that I updated to 4.11 , rooted then side updated the newest little update and then ran a su zip to regain root (Paul o' Brian ROM) . I was also on his first cwm and then updated to his new one after I started from scratch. Loaded up his new ROM, rebooted then applied your 2nd kernel and this thing is hitting 15626 in CF benches!
Not sure what is going on, but I can't explain it. It may be my 2nd version of the kernel that fixes it, but I am not sure since I haven't seen a log yet. I suppose something may be jacked up with the early versions of recovery or roms, but the I was using the the same early versions when I tested just fine....maybe folks are losing recovery and don't realize it? I did the second step to keep recovery that is now automated in r2. If anyone has any ideas, let me know.
New version released
New version released...see OP. GPU OC to 446MHz (up from stock 416)
Looking for more feedback
_motley said:
New version released...see OP. GPU OC to 446MHz (up from stock 416)
Looking for more feedback
View attachment 1204164
Click to expand...
Click to collapse
Just out of curiously, would you ever try 520mhz for the gpu, to try to get it to t30 speeds? Or maybe would you consider some kind of app interface like extweeks for the galaxy s2 & s3 to control the GPU clock speed and maybe voltages instead of different kernels. As I would personally love to get the GPU to about 460-500mhz Anyway when I get my n7 (hopefully in a day or two) I can't wait to try this out (I am spoilt by the much more powerful 440mhz mali-400mp in the s3, so I would love to try to narrow the power difference between the devices GPU wise)
Nice man! The new versions fixed everything boots great! Now if we can just figure out how to make the Overclock stick after you turn the screen on/off. I'm not sure how to tell if the GPU OC is sticking.
Sent from my Nexus 7 using xda app-developers app
danielsf said:
Just out of curiously, would you ever try 520mhz for the gpu, to try to get it to t30 speeds? Or maybe would you consider some kind of app interface like extweeks for the galaxy s2 & s3 to control the GPU clock speed and maybe voltages instead of different kernels. As I would personally love to get the GPU to about 460-500mhz Anyway when I get my n7 (hopefully in a day or two) I can't wait to try this out (I am spoilt by the much more powerful 440mhz mali-400mp in the s3, so I would love to try to narrow the power difference between the devices GPU wise)
Click to expand...
Click to collapse
Sure, we may push the GPU OC version a bit, but I always like to walk before we run to see how things go. I would like to monitor heat output, battery usage etc. and then move forward in steps. I am very happy with it right now, but dynamic configuration would also be cool. Let me know what you think once you have it hand.
Clienterror said:
Nice man! The new versions fixed everything boots great! Now if we can just figure out how to make the Overclock stick after you turn the screen on/off. I'm not sure how to tell if the GPU OC is sticking.
Click to expand...
Click to collapse
Awesome, glad to hear it! I don't think I see this issue with the OC sticking after you turn the screen off/on, but I will do more checking after work today.
_motley said:
Awesome, glad to hear it! I don't think I see this issue with the OC sticking after you turn the screen off/on, but I will do more checking after work today.
Click to expand...
Click to collapse
Thanks a ton! Yea if you go into setcpu and make it 1.6 then turn the screen off then on (unlock) set CPU slider still shows 1.6 but if you read under that the smaller text says its actually set at.1.3 again. It seems to be a problem with the Atlantis kernel also something to do with hardcoded CPU freqs I think. Oh I wanted 5k soooo bad rofl got this twice rofl.
Sent from my Nexus 7 using xda app-developers app
Clienterror said:
Thanks a ton! Yea if you go into setcpu and make it 1.6 then turn the screen off then on (unlock) set CPU slider still shows 1.6 but if you read under that the smaller text says its actually set at.1.3 again. It seems to be a problem with the Atlantis kernel also something to do with hardcoded CPU freqs I think. Oh I wanted 5k soooo bad rofl got this twice rofl.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've just made profiles that automatically set the clock to 1.5 when the screen turns on again and back to 1.5 when the screen turns off.
Edit*
Just tried the newest version and it failed to boot. Got stuck at the Google Logo. Here is the last_kmsg. Hopefully it helps
(had to put a .txt extension on it btw. Uploader wont let me upload w/o extension)
The Nexus 7 GPU is better than the Transformer Prime due to the faster RAM, so more bandwidth? If I'm correct? Thats why we see a higher Nenamark score at a lower clock?
This kernel looks very promising, excellent work! How much "play" have you had with upping the voltages, before the battery quits? On my TF, I can only go so far before the battery cannot provide enough juice, and it freezes on me. It would be interesting to know for people who want to OC really high. Does anything above 1.6 GHZ actually boot (heat and battery drainage aside)? It would be nice to OC up to 2.0 GHZ, if only for a proof-of concept. Finally, what are the temps you are getting on the higher clocks? It sounds like overheating may start becoming a real issue, and I was just curious.
The ram disk version rendered my tablet unbootable had to flash the Atlantis kernel from fast boot to get it back up and running.
Sent from my Nexus 7 using Tapatalk 2
Good work there, I would suggest adding Smartassv2 as well since it has been a good choice for many dev
I for the life of me can't get this kernel to OC. Tried System Tuner, Setcpu etc. Max only reads 1300mhz nothing shows higher beyond 1300. I have no clue what the deal is. I've tried wiping also. Even tried Atlantis' kernel. on his, it won't allow me to set anything. Max shows 0 and Min shows zero. I am running Pauls Modaco Jr3 and even tried it on EOS' new release. I'm beginning to wonder if its something diff internally. Anyone have any guesses?Also showing root as setcpu requests superuser permissions.
This is what my device shows
Board: grouper
Product: nakasi
Model: Nexus 7
Device: grouper
Build: JRO03D (Modaco Custom ROM Jr3)
google/nakasi/grouper:4.1.1/JRO03D?402395:user/release-keys
Manufacturer:asus
Brand:google
CPU ABI: armeabi-v7a
Kernel
Linux version 3.1.10-motley+([email protected]) (gcc version 4.6.3 (GCC)) #6 SMP
PREEMPT Tue Jul 17 00:52:59 EDT 2012
{
"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"
}
This only works on Gingerbread, not anything else. We are still working on finding alternative tweaks for ICS and JBThis is a MOD to boost the performance of the Adreno 205 GPU in the Xperia Play. (This mod should also work on other Adreno devices (Adreno 205+) and whilst some people have had some success I cannot confirm which devices other than the Play it works with)
This mod is a joint collaboration/venture of me and CosmicDan. However, as of version 0.2 CosmicDan has unfortunately left the Xperia 2011 range for better things. I wish him every success in the future.
CosmicDan was able to find a variant of the 'adreno_config.txt' file that contains settings that should work on our device. Since finding this we have found numerous combinations of settings that increase the performance of our chips. See below.
What does it do?
The configuration file consists of multiple options, each which do their very own unique 'tweaking' to the way the GPU performs. One of the most notable options we are using is 'triJuice', an explanation of which is below:
If our phones were to have their own driver application, what this would be doing is essentially moving the 'Quality/Performance' slider towards 'Performance'. This tells the GPU to concentrate on 'Performance' rather than 'Quality'.
See CosmicDan's explanation here:
It's common graphics stuff and the same for PC's, we have told the GPU to put a focus on performance instead of quality. But the quality is not sacrificed much, it's barely noticeable. Maybe some games will look not so well, you'll have to test and see.
It's like we've lowered effect and texture detail on a system-wide level, allowing the CPU and GPU to give more time to work on geometry and frame updates and such. Useful because many games don't have settings for graphics quality.
Click to expand...
Click to collapse
Another notable option is 'forceAutoTextureCompression'. This saves RAM and makes texture rendering faster, but the actual loading of the game might be a tiny bit slower - however once it's loaded it will have faster rendering.
A list of possible settings for this configuration file are below (For detailed descriptions please see attached)
Post 3 lists which settings tend to increase or reduce performance, I will not give instructions on how to modify this however if you to intend on making your own config file please use Post 3 as a guide.
Code:
; Performance Analysis
performance=normal
disableExtraSwapBlit=0
ignoreGLFlush=0
; Binning
binning=hw
forceGuardband=0
guardbandValue=0
forceGmemSize=0
gmemSize=0
veboSetting=0
veboSetting=0
numBins_weight=80
numGroups_weight=20
; Logging
log.resolves=0
log.pm4=0
log.pm4mem=0
log.shaders=0
log.sc_dev=0
log.sc_dev_shader_name=sc_dev_dump.txt
log.cffdump=0
log.cffdump_with_ifh=0
log.cffdump_no_memzero=0
log.dumpx=0
log.primitives=0
; Debugging
waitForIdleAfterDraw=0
waitForIdleOnSubmit=0
disableSwapTsIdle=0
clockGating=off
useSafeMode=0
redirectDebugMessages=0
forceChipId=Default
; Primitive Conversion.
convertTristrips=default
convertTrifans=default
convertLineloops=default
shader_sub.write=0
shader_sub.read=0
shader_sub.trivialfs=0
; Features and Performance
facenessCulling=default
vboDataAlignment=natural
enableOptimizedTextureUpdates=1
enableOptimizedVboUpdates=1
forceAutoTextureCompression=1
triJuice=1
enableInlineConstantUpdates=1
enableMemoryPool=1
enableFastClears=1
ditherSafeFastClears=0
shadowGmemInAppBuffers=1
textureTiling=0
preserveZStencilOnSwap=0
allowDepthExport=0
untileDynamicTextures=1
fullSurfaceDynamicUpdatePath=1
useGpuTilingHints=1
; MultiSampling Antialiasing (MSAA)
MSAASmoothing=Normal
MSAABufferAllocation=never
forceMSAAMode=0
MSAAMode=0
VAESEnable=0
VAESGenericError=0
VAESFailNth=0
VAESDoNotFailFirstN=0
VAESRandomSeed=0
VAESFailPercent=0
; 2D Settings
2D.HwBlt=1
2D.eglSwapMode=noidle
2D.forceEglSwapInterval=0
2D.eglSwapInterval=0
; LEIA Features
leiaEnableLrzWrites=0
leiaEnableLrzExpansion=0
leiaExportColorForLrzUnresolve=0
leiaEnableFastLrzUnresolves=0
; Oxili settings.
oxiliDisableLazyUpdates=0
oxiliDisableChunkedUpdates=0
oxiliForceShaderDirectUpdates=0
oxiliForceConstantDirectUpdates=0
oxiliForceIstoreCacheMode=1
oxiliForceCstoreSingleBuffer=0
oxiliForceShaderSingleContext=0
oxiliForceSuperthreadMode=1
oxiliForceVsSingleThread=0
oxiliForceFsSingleThread=0
oxiliForceSingleSp=0
oxiliSkipClears=0
oxiliForceSysmemRender=1
; Other settings
FPSCap=60
allowFloatFBOs=1
suppressTimestampInterrupts=0
GPUIdleTimeout=off
GPUIdleTimeoutMsec=0
Please ignore the values of the above settings unless otherwise stated. The majority of these are stock/default values for our device.
Downloads - Official repository
AdrenoBooster v0.7
AdrenoBooster v0.6
AdrenoBooster v0.5 - Quality Edition
AdrenoBooster v0.4.1 - Battery Edition
AdrenoBooster v0.3 - Minimal Edition - This version will give you the best performance - stability ratio. Whilst the other versions may give you better performance but in some rare instances lower quality/artifacts, this version should give you the best of both worlds.
AdrenoBooster v0.1
AdrenoBooster v0.2
Instructions
Download and copy the ZIP to SD Card. Then flash using CWM.
NOTE: Please ensure you reboot your device after the first boot post-installation of the mod or it will not be active.
Requirements
Init.d support
Root
Any Gingerbread ROM
Screenshots
IMPORTANT!! - Please ensure you thank 'CosmicDan' as well for this fantastic mod. A huge portion of the work has been done by him!
(See 5th post if you would like to 'Thank' him)
Troubleshooting
First, give yourself another reboot - Just in case!
If it still doesn't seem to be working for you, check to see if the files have copied to your device. Check the following locations for the following files with any file manager with Root support.
/system/etc/init.d - Filename: 93adreno
/system/etc - Filename: adreno_config.txt
You should also see adreno_config.txt in the following location if the init.d script is working correctly: /data/local/tmp
If this file is not in this location then chances are you do not have init.d support.
Black screen on boot? See here: http://forum.xda-developers.com/showpost.php?p=40013461&postcount=377
Extras
You can assist with the testing of some of these settings by doing the following:
Open a new text file in a standard text editor (Notepad++ or Notepad for Windows)
Choose values from the above post to put into your configuration file. (Use the attached adreno_config.txt file as an indication of what setting does what)
Save this new file as 'adreno_config.txt'
Copy this text file to your phones SD Card.
Open your File Manager on your phone (I use ES File Explorer)
Prepare adreno_config.txt on your SD Card for copying
Navigate to /Data/local/tmp and paste the file there
Reboot.
Please be aware that if you have any cleaner init.d scripts this will NOT work, as when you reboot /data/local/tmp will be deleted.
Devs/Chefs/Tinkerers
If you would like to add this to your ROM please simply drop a short request in this thread or PM.
After which, please ensure proper credit is given.
Current Antutu Highscore
(With the benefits of this mod) - By CrypticRook
Manually Uninstalling the Mod
Navigate to the following locations and remove the files.
/system/etc/init.d - Filename: 93adreno
/system/etc - Filename: adreno_config.txt
/data/local/tmp - Filename: adreno_config.txt
Tested Settings
Untested:
preserveZStencilOnSwap - enabling might improve performance at the increased risk of visual artifacts
Dangerous:
facenessCulling - Turning on causes crash on boot
FPSCap - setting to anything other than 0 (even to 60 or 100) causes unstable 2D rendering
2D.eglSwapMode=interrupt - Causes unstable/looping 2D rendering. Applications fail to initialize.
fullSurfaceDynamicUpdatePath - reduces 3D performance by around 10%.
Performance Boosts:
forceAutoTextureCompression - Turning this on seems to help a LOT with 3D performance. Might increase load times by a a tiny amount.
triJuice - setting it to the max value of 3 increases particle/shader/lighting performance a LOT with a minor loss in quality
forceMSAAMode - enabling this will force no anti-aliasing as long as MSAAMode is left at 0. Could increase performance on some things but make them look very chunky
2D.HwBlt - Enabling this should enhance GPU hardware acceleration in gingerbread. It says default is enabled but I've set it to 1 anyway.
oxiliForceVsSingleThread=1 - Must be enabled with oxiliForceFsSingleThread=1 for performance increase. Prolonged usage has negative impact (Needs more testing).
oxiliForceFsSingleThread=1 - Must be enabled with oxiliForceSingleSp=1 for performance increase. Prolonged usage has negative impact (Needs more testing).
oxiliForceSingleSp=1 - Must be enabled with oxiliForceVsSingleThread=1 for performance increase. Prolonged usage has negative impact (Needs more testing).
clockGating - Turning this on might save power consumption (Currently being tested more to confirm). However there is no performance drop by having this enabled
Seemed to hurt performance: (I did not test these much, could do with more tests one-by-one)
leiaEnableLrzExpansion - enabling might.... do something.
leiaEnableFastLrzUnresolves - enabling might improve performance
oxiliDisableChunkedUpdates - enabling might improve performance
oxiliForceShaderDirectUpdates - enabling might improve performance
oxiliForceConstantDirectUpdates - enabling might improve or reduce performance
oxiliForceShaderSingleContext - enabling might improve performance at cost of quality
oxiliForceSuperthreadMode - enabling might improve performance or reduce it. Probably conflicts with above one.
suppressTimestampInterrupts - enabling might improve or reduce performance
Null/No Difference - These options made no effect on performance from their default settings
shadowGmemInAppBuffers - no effect on performance or quality
Great! Really looking forward to seeing what you can do
Thanks for letting me know you opened a topic
I've been doing some research and here's what ideas I've found so far:
clockGating - Turning this on might save power consumption. Will need to test if it has a performance hit.
facenessCulling - Turning on causes crash on boot
forceAutoTextureCompression - Turning this on MIGHT save RAM and/or MIGHT increase load times/CPU usage.
triJuice - raising this value might increase performance but decrease quality of mipmapping.
shadowGmemInAppBuffers - disabling might improve performance but break some things
preserveZStencilOnSwap - enabling might improve performance at the increased risk of visual artifacts
fullSurfaceDynamicUpdatePath - enabling might improve performance at the increased risk of visual artifacts
forceMSAAMode - enabling this will force no anti-aliasing as long as MSAAMode is left at 0. Could increase performance on some things but make them look very chunky
2D.HwBlt - Enabling this might enhance GPU hardware acceleration in gingerbread. It says default is enabled but I've set it to 1 anyway.
2D.eglSwapMode - changing to interrupt mode might.... do something. LETS TRY IT!
leiaEnableLrzExpansion - enabling might.... do something.
leiaEnableFastLrzUnresolves - enabling might improve performance
oxiliDisableChunkedUpdates - enabling might improve performance
oxiliForceShaderDirectUpdates - enabling might improve performance
oxiliForceConstantDirectUpdates - enabling might improve or reduce performance
oxiliForceShaderSingleContext - enabling might improve performance at cost of quality
oxiliForceSuperthreadMode - enabling might improve performance or reduce it. Probably conflicts with above one.
oxiliForceVsSingleThread - enabling might improve or reduce performance
oxiliForceFsSingleThread - enabling might improve or reduce performance
oxiliForceSingleSp - enabling might improve or reduce performance
FPSCap - setting to 30 or 60 might help with all-round performance and reduce lag spikes. Maybe.
suppressTimestampInterrupts - enabling might improve or reduce performance
Right, that's a lot of things for me to try one by one. If anyone else wants to, go for it. Just remember it could completely break your boot
Re: [WIP] Adreno Configuration Settings [Improved Performance?]
I did lol.. In the adreno thread xD
Ill make it more clear next time.
I've just tried a few things... Managed to make Antutu crash lot. Just finally completed a full benchmark but then the OS died. Going well so far. Cya in about 7 hours!
Edit: it looks like you can copy it to data/local/temp and the settings will apply for next boot. After which it is then removed from the directory. Which for me makes things a bit easier!
Sent from my R800i using xda app-developers app
Oh by the way, copying the config file to /system/lib/egl/ definitely does nothing. I tested by setting FPS cap to 5, no effect. File needs to be at /data/local/tmp/ - it does *not* get wiped on reboot so its OK.
EDIT: THe file isn't removed from /data/local/tmp/ for me =\ maybe you have an init.d script that erases it or something.
Re: [WIP] Adreno Configuration Settings [Improved Performance?]
Possibly. Ill check.
Btw, I just managed 13fps on the OpenGL ES2.0 test on Antutu. It was hilarious, so many artifacts... But it passed it!
...Until it died on the SD card test. If you use Antutu I suggest doing custom tests and taking SD out. Or reducing OCs. I think my 1.6ghz may be the problem.
Or perhaps we should use stock clock a to base our tests on?
Edit: seems like almost every setting you try also kills the bootanimation lol
Sent from my R800i using xda app-developers app
Spizzy01 said:
Possibly. Ill check.
Btw, I just managed 13fps on the OpenGL ES2.0 test on Antutu. It was hilarious, so many artifacts... But it passed it!
...Until it died on the SD card test. If you use Antutu I suggest doing custom tests and taking SD out. Or reducing OCs. I think my 1.6ghz may be the problem.
Or perhaps we should use stock clock a to base our tests on?
Edit: seems like almost every setting you try also kills the bootanimation lol
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
I can't get past the 2D/sprite test in Antutu (the little Androids) it freezes at the end lol. Boot animation was always OK for me....
Yeah, using a stock clock would be a good idea. But I'm on 1.4 ghz anyway because that's what I've always used and always been stable on.
EDIT: I think setting FPSCap to 60 was the reason for Antutu freezing on 2d test.
EDIT2: You are using LuPuS GB kernel right? Because Turbo Kernel has backported KGSL drivers, so that's probably why we not only have different performance scores but may have different results with these configs.
---------- Post added at 01:24 PM ---------- Previous post was at 01:13 PM ----------
DUDE! New Gingerbread record!
/data/local/tmp/adreno_config.txt:
Code:
facenessCulling=off
forceAutoTextureCompression=1
triJuice=3
2D.HwBlt=1
CosmicDan said:
I can't get past the 2D/sprite test in Antutu (the little Androids) it freezes at the end lol. Boot animation was always OK for me....
Yeah, using a stock clock would be a good idea. But I'm on 1.4 ghz anyway because that's what I've always used and always been stable on.
EDIT: I think setting FPSCap to 60 was the reason for Antutu freezing on 2d test.
EDIT2: You are using LuPuS GB kernel right? Because Turbo Kernel has backported KGSL drivers, so that's probably why we not only have different performance scores but may have different results with these configs.
---------- Post added at 01:24 PM ---------- Previous post was at 01:13 PM ----------
DUDE! New Gingerbread record!
/data/local/tmp/adreno_config.txt:
Code:
facenessCulling=off
forceAutoTextureCompression=1
triJuice=3
2D.HwBlt=1
Click to expand...
Click to collapse
OMFG! LEGEND!
Gonna test on mine and report back ASAP. Gimme 10 - 20 mins, depending on when I can get a free sec @ work. Lol. xD
Edit: Unable to replicate your score at the moment. Getting stock scores, most likely something to do with those pesky init.d scripts. Deleting now and will report back shortly
In the next turbo kernel release I'll make the kernel do a symlink from /data/local/tmp/adreno_config.txt to /system/etc/adreno_config.txt (it will be linked before init starts so will apply straight away), that way we can include modified config with ROM's.
You could just make an init.d script do the same thing, but then the ROM will need to be rebooted again (because adreno driver is already loaded).
CosmicDan said:
In the next turbo kernel release I'll make the kernel do a symlink from /data/local/tmp/adreno_config.txt to /system/etc/adreno_config.txt (it will be linked before init starts so will apply straight away), that way we can include modified config with ROM's.
You could just make an init.d script do the same thing, but then the ROM will need to be rebooted again (because adreno driver is already loaded).
Click to expand...
Click to collapse
I think I'll include an init.d script with my ROM, so that in the event someone isn't using your Kernel it will still work as intended.
...At least, after a reboot.
Doing Antutu now btw, ITS CRAZY FAST OMG. About to give you results. UNO MOMENTO!
OMFG!
This actually brought a tear to my eye... Lmfao... XD
Spizzy01 said:
I think I'll include an init.d script with my ROM, so that in the event someone isn't using your Kernel it will still work as intended.
...At least, after a reboot.
Doing Antutu now btw, ITS CRAZY FAST OMG. About to give you results. UNO MOMENTO!
Click to expand...
Click to collapse
Yeah I realized that too, already done it for Turbo UI Classic (which is uploading now). This should work:
/system/etc/init.d/93adreno:
Code:
#!/system/bin/sh
#
if [ ! -h /data/local/tmp/adreno_config.txt ] then
ln -s /system/etc/adreno_config.txt /data/local/tmp/adreno_config.txt
fi
EDIT:Woohoo! Play broke the 7000 mark
Now I wonder how Jellybean on Turbo Kernel performs.... maybe closer to 8000 lol! And the visual quality of the orc fight 3D test looked OK for you yeah?
CosmicDan said:
Yeah I realized that too, already done it for Turbo UI Classic (which is uploading now). This should work:
/system/etc/init.d/93adreno:
Code:
#!/system/bin/sh
#
if [ ! -h /data/local/tmp/adreno_config.txt ] then
ln -s /system/etc/adreno_config.txt /data/local/tmp/adreno_config.txt
fi
Will be good to know if the results on LuPuS GB kernel are worse, better or the same with this config.
Click to expand...
Click to collapse
My test was done on LuPuS GB.
Sorry - I moved back from your Kernel last night. =x
Thank's for the script. I'll add it to v0.5 Aurora now. xD
Edit: Agreed. JellyBean should have crazy scores... Right, I'm gonna test a few of the other configs. From that list you've done, can you 'tick' off which you have already checked please? Just so I can continue where you left off at.
Orc fight looked perfectly fine. If it were a HD movie I'd say it had a low bit-rate, but it's not... So I have no idea what to call it, but it does look ever so slightly more grainy. But this is barely noticeable at all.
I looked in /data/local/tmp/ and there was no adreno_config.txt I'm using joka wild any ideas did I have to do something before hand using LuPuS v6 480p I'm very interested because I use this a a gaming device as I have a nexus 4
Spizzy01 said:
My test was done on LuPuS GB.
Sorry - I moved back from your Kernel last night. =x
Thank's for the script. I'll add it to v0.5 Aurora now. xD
Edit: Agreed. JellyBean should have crazy scores... Right, I'm gonna test a few of the other configs. From that list you've done, can you 'tick' off which you have already checked please? Just so I can continue where you left off at.
Click to expand...
Click to collapse
I edited my last post since you uploaded results
That's OK, I'll still win the record by being first to test Turbo UI (JB) score lolz
EDIT: OK, I'll edit that list.
extremetempz said:
I looked in /data/local/tmp/ and there was no adreno_config.txt I'm using joka wild any ideas did I have to do something before hand using LuPuS v6 480p I'm very interested because I use this a a gaming device as I have a nexus 4
Click to expand...
Click to collapse
You need to move the file there yourself.
See attached.
Move the file to /Data/Local/tmp and reboot. Ensure you have no init.d scripts that clear cache or tmp though, as it will not work.
OK here's what my data is.
Untested:
clockGating - Turning this on might save power consumption. Will need to test if it has a performance hit.
shadowGmemInAppBuffers - disabling might improve performance but break some things
preserveZStencilOnSwap - enabling might improve performance at the increased risk of visual artifacts
fullSurfaceDynamicUpdatePath - enabling might improve performance at the increased risk of visual artifacts
oxiliForceVsSingleThread - enabling might improve or reduce performance
oxiliForceFsSingleThread - enabling might improve or reduce performance
oxiliForceSingleSp - enabling might improve or reduce performance
Dangerous:
facenessCulling - Turning on causes crash on boot
FPSCap - setting to anything other than 0 (even to 60 or 100) causes unstable 2D rendering
Performance Boosts:
forceAutoTextureCompression - Turning this on seems to help a LOT with 3D performance. Might increase load times by a a tiny amount.
triJuice - setting it to the max value of 3 increases particle/shader/lighting performance a LOT with a minor loss in quality
forceMSAAMode - enabling this will force no anti-aliasing as long as MSAAMode is left at 0. Could increase performance on some things but make them look very chunky
2D.HwBlt - Enabling this should enhance GPU hardware acceleration in gingerbread. It says default is enabled but I've set it to 1 anyway.
Seemed to hurt performance: (I did not test these much, could do with more tests one-by-one)
2D.eglSwapMode - changing to interrupt mode might.... do something. LETS TRY IT!
leiaEnableLrzExpansion - enabling might.... do something.
leiaEnableFastLrzUnresolves - enabling might improve performance
oxiliDisableChunkedUpdates - enabling might improve performance
oxiliForceShaderDirectUpdates - enabling might improve performance
oxiliForceConstantDirectUpdates - enabling might improve or reduce performance
oxiliForceShaderSingleContext - enabling might improve performance at cost of quality
oxiliForceSuperthreadMode - enabling might improve performance or reduce it. Probably conflicts with above one.
suppressTimestampInterrupts - enabling might improve or reduce performance
I made a quick Update ZIP to flash the mod/script and updated the first few posts.
You have been fully credited of course in the updater_script
Gonna look into other settings now.
Edit: I'm not sure I like the new Mediafire layout :|
hello to all, i noticed that my redmi note 3 pro KATE ( i am on globerom 8.1.1.0 stable) has the minimum clock for big cluster, setted at 883mhz , and little cluster 691mhz BUT i can select on kernel adiutor the min freq of 400/ 400 mhz.
QUESTION 1 about freqNow i am with L speed app , and applied battery profile, but i don't understand why it does not automatically set the value to the MINIMUM POSSIBLE. Is there a reason?
Is there any CON to set the minimum cloto to cpu at 400mhz? i don't understand why xiaomi.eu and globerom modders did not set this freq to lowest possible, is it maube harmfull for the device?
should i have to set it by myself in kernel adiutor app? please help me to use this app, i just suppose i must apply 400mh setting, THEN choose to apply to boot ( there is a toggle).
What if i set at 400 and NOT toggle it?
QUESTION 2 about differences L speed and gov tuner flashable zip.I am sorry to admit that i'm not such skilled into android development and i have difficulties to understand terms like init.d or script meanings.....
For what i know i found pre installedon globerom the gov-tuner project zip file, then i discovered that that optimizations to the GOVERNOR, are also incorporated in another app called L speed. so i uninstalled gov tuner in this way:
1) entered into console, and entered the letter to disable gov tuner. ok,
2)then rebooted into recovery and flashed the zip for uninstaller.
DELETED! and i can say with that mod my battery life was really good almost perfect.
then i installed L speed, but still being a nice app with lots of features and explanatiions for EACH of them, i just setted overall provile to BATTERY, and cheched some other tweaks....EXCLUDING THE ONES that are described as battery wasting.
Then i asked to officiial thread if i have to reboot to apply, they said no... but it's PREFERABLE. OK I REBOOT.
by now i have worse battery life ( much worse) and i can't understand why.
I tested with console if gov tuner is still present, but NO. so there shoudn't be any conflict at all
sorry....if this 2nd question is THE BIGGEST ONE, but i really need to read someone suggestion and a simple explanation to understand if it's better l speed or gov tuner to me.
L speed seems very much powerful and can mod much more things... but is it safe? maybe there are so much options and i choosed 1 or 2 too much, and now i see bad battery life. but it's nearly impossible what is the option that causes me this.
And last important thing.... is it the same thing to implement these script or optimizations at the boot (i think gov tuner do it so) or after the boot like do L speed? ( i noticed into app a setting to choose 10 seconds after boot to apply scripts, in fact i see after each boot a notification about these applied scritps)
Hello,
sorry I can only answer question 1 since I dont use Lspeed.
Set it to 400MhZ Dude!
Doesnt harm your device, its still not laggy or anything.
Set apply on boot option and you`ll be golden.
RN3 has awesome battery life just stock. If you want more, install skynet. (was on xda, moved to google+)
There is even a guide somewhere out there for setting it to 400Mhz.
Cheers mate
*** This kernel is now end-of-life and not supported nor actively developed anymore !!! ***
Hi all,
some of you know me from the other OnePlus or Samsung devices areas, where I provide my kernels already for more than five years to OnePlus 5, 3T, 3, 2, one and X, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Now I own a OnePlus 5T device and decided to port my kernels also to this device.
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other, good existing kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
To add: A community build is NOT an official build supported here. If you use a community build and have issues, don't complain or even report.
Important notes
Read first, especially when you are new to my kernels:
http://wiki.boeffla.de
Boeffla-Kernel uses the anykernel concept = Flash stock kernel of rom first !
This kernel is ONLY compatible to OxygenOs stock, nothing else !!!
If you are using a custom rom that bases on OxygenOs, it might work. However, if it does not work, do not expect me to do tweak to make the kernel running with your favorite rom. I would not do it - my one and only reference is OxygenOs stock.
It is not supposed to be compatible to CM, HydrogenOS etc.
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Important: Manually disable battery optimisation for Boeffla-Config app in the rom settings (battery -> battery-optimisation)
Installation
Read the install instructions in the support section on the Boeffla Site.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (outdated at the moment).
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting/overclocking and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting change log...)
Change log for OxygenOS 5.x.x kernel - Click here
Change log for OxygenOS 4.x.x kernel - Click here
Known issues
none known
Features
Note: This kernel only runs on OOS 4.x.x for the OnePlus 5T - nothing else !!!
Important: Manually disable battery optimisation for Boeffla-Config app in the rom settings (battery -> battery-optimisation)
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.5.10 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Dash charging fully supported
The two CPU clusters (big and little cpu) can be configured completely separate in terms of min/max frequencies, governors and CPU core profiles
Additional governors: zzmoove, blu_active, impulse, cultivation
Additional schedulers: fiops, bfq, sio, sioplus, fifo, vr, tripndroid, maple, zen
Underclocking CPU and GPU supported
No CPU and GPU overclocking (not planned too)
No CPU and GPU voltage interfaces (not planned too)
GPU boost implemented (4 levels)
CPU core profiles to restrict number of CPU cores being used (the OP5T does not hotplug based on load)
USB charge rate bumped up to 900 mA
Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time)
Notification LED control (effect + speed for blinking/fading, brightness for continuous notification like battery charging etc.)
Boeffla-Sound engine V1 (headphone volume control, earpiece control in calls, microphone gain control in calls)
Dynamic FSync (activated if screen on, deactived if screen off), configurable
Input boost frequencies and duration configurable per CPU cluster, input boost switch
Show CPU frequency usage per CPU and frequency in Boeffla-Config
Show current CPU core frequencies in realtime (note: other apps than Boeffla-Config will likely display wrong information on offline cores as they are not up-to-date yet)
Show GPU frequency usage per frequency in Boeffla-Config
KCal V2 Color control
Display backlight limits configurable (to avoid display brightness gets too low in some situations)
Display backlight dimmer
Swipe2wake gestures
Boeffla generic wakelock blocker
Control haptic feedback of gestures (except fingerprint)
Haptic feedback intensity control (from 0 to 25, with 25 being 100%)
Swipe2sleep gestures
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
Kernel logger (dmesg) configurable
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS read-only support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Many additional TCP congestion algorithms available
Entropy values configurable
Swap supported
Wireguard supported
Various kernel tweaks
Doze mode configurable in Boeffla-Config
Full selinux strict support (switchable to permissive on demand)
Show speedbin information (PVS level) in Boeffla-Config app
init.d support (in /system/etc/init.d - set correct permissions!)
Automatic EFS backup
Fully supports OOS device encryption, but does not force it
Integrated full busybox 1.27.2 (own compilation)
Compatible with systemless root
Safetynet: verifiedbootstate + additional flags removed
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Google gcc 4.9 toolchain (64 bit) used for best stability
Always based on latest OOS kernel sources (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8998)
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the kernel only if you are running a compatible rom !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app Boeffla-Config V2 from the downloads section on www.boeffla.de.
You need at least version 2.5.10 or higher for the OnePlus 5T Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* eng.st
* flar2
* arter97
* Grarak
* Entropy512
* Faux
* FranciscoFranco
* Ak
* Osm0sis
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change log:
OOS4
http://kernel.boeffla.de/oneplus5t/boeffla-kernel-oos/oos4xx/changelog.htm
--- Reserved ---
WHAT MAKES YOU THINK I WILL MAKE A KERNEL FOR ONE PLUS 5 T ?????
Sendt fra min SM-N950F med Tapatalk
Thread opened.
First beta version has just been released - 1.0-beta1.
Feature list, see OP.
Have fun
Andi
Is it compatible with open beta 2 ?
Awesome.. Was waiting for your Kernel
zebasketteur said:
Is it compatible with open beta 2 ?
Click to expand...
Click to collapse
I would assume not, as in title is says OOS 4
---------- Post added at 02:42 PM ---------- Previous post was at 02:05 PM ----------
Just flashed, seems that the max brightness is lower, with the display backlight settings unchanged. Apart from that all seems to be good.
Nice to see you here! I have use your kernels starting with Samsung S3 and after that many many devices and always being good!
zebasketteur said:
Is it compatible with open beta 2 ?
Click to expand...
Click to collapse
This is very clearly stated in the opening post.
No.
Hetex said:
[/COLOR]Just flashed, seems that the max brightness is lower, with the display backlight settings unchanged. Apart from that all seems to be good.
Click to expand...
Click to collapse
This is not changed by me. As long as you do not play in the app with the settings, this is 1:1 as in stock kernel.
Anyone else? I mean, nothing is impossible of course.
Andi
Lord Boeffla said:
This is not changed by me. As long as you do not play in the app with the settings, this is 1:1 as in stock kernel.
Anyone else? I mean, nothing is impossible of course.
Andi
Click to expand...
Click to collapse
Not sure if it is the same problem but in the first release of elementalX kernal, whether the brightness dimmer was enabled or not the brightness at maximum was half of what it should have been.
Thanks.
Lord Boeffla said:
This is not changed by me. As long as you do not play in the app with the settings, this is 1:1 as in stock kernel.
Anyone else? I mean, nothing is impossible of course.
Andi
Click to expand...
Click to collapse
You have to revert THIS exact commit in order to fix that (not working anymore on OP5T)
Welcome to OP5T mate btw :highfive:
Cheers'
Hello Boeffla
Hetex said:
Not sure if it is the same problem but in the first release of elementalX kernal, whether the brightness dimmer was enabled or not the brightness at maximum was half of what it should have been.
Thanks.
Click to expand...
Click to collapse
Good hint. Will check in that direction when more people are sure this brightness thingy is real.
Update: Analysis started...
Andi
Lord Boeffla said:
Good hint. Will check in that direction when more people are sure this brightness thingy is real.
Update: Analysis started...
Andi
Click to expand...
Click to collapse
Ok, issue analyzed, confirmed to be a bug.
Bug is fixed and beta2 already compiling. Stay tuned. And thanks for the report.
(BTW it was not the brightness dimmer but a changed brightness range sent by the rom to the kernel, so the min/max limiter was cutting too early)
Thanks
Andi
AndroidGX said:
You have to revert THIS exact commit in order to fix that (not working anymore on OP5T)
Welcome to OP5T mate btw :highfive:
Cheers'
Click to expand...
Click to collapse
Thanks. Sorry, did not see your post as I was busy analyzing.
Well... reverting a commit and losing the functionality is not the option when I can fix it, eh? :fingers-crossed:
And so I did.
MrTalon4 said:
Hello Boeffla
Click to expand...
Click to collapse
Hello MrTalon4
Andi
Hi all,
small bugfix update is out:
Version 1.0-beta2
18.01.2018
Fix: Backlight limit implementation adjusted to OP5T (display could never reach maximum brightness before)
Enjoy
Andi
Welcome,it is nice to see you here ..waiting one for oreo
marko94 said:
Welcome,it is nice to see you here ..waiting one for oreo
Click to expand...
Click to collapse
Yeah. But not before it gets out of open beta, not before it is released officially.
... my golden rule for a long time.
Andi
Welcome to the 5T-Zone
Is it possible to have WireGuard implementation for your new 5T kernel (at some point in the near future) ?
Edit:
I just rechecked the OP, already there. Too cool
I would love to get the battery life profiles from the custom kernels but I don't want to install them and would like to relay to the stock kernel of my rom which is RR. For reasons that I want to avoid bugs and would want to stay updated all the time.
I found spectrum which exactly what will solve my problem but the problem is that it doesn't support the stock kernel of RR.
Stock kernel of RR support "Kernel Adiutor". Kernel Adiutor give you various useful settings.
In my opinion the first is change voltage of your CPU (for each speed).
i Undervolt all Little cores:
(Warning each cpu need different settings, this setting can not work for you)
400 and 691 mhz with 695mv
806mhz 745mv
1017mhz 825mv
1190mhz 880mv
1305mhz 915mv
1382mhz 935mv
1401mhz 940mv
1440mhz 950mv
Big cores DISABLED. (i dont have lags with this settings... i play Clash Royale and use social apps, if you need it enable)
In GPU (i dont play games except Clash Royale)
133mhz min
432mhz max
Down differential 75
Iddle wait 7
Workload 10
For test speed/voltage you need to set same min and max speed and disable de Big Cores. (Or set max speed "X"mhz and use performance governor)
low voltage
use Antutu for test or other similar app.
if work low voltage again
test
if work repeat if not raise the voltage 5 or 10 mv and test again.
DONT USE "APPLY ON BOOT" when you try different voltages.
when you have your profile save this and here in profile menu you can set it at startup (you need to be sure of your phone stability with this settings).
Equally i recommend Agni kernel 13... i use before RR oreo and now AEX oreo and im happy with this kernel, zero problems, all fine.
in this forum other users try with VULMAX but i prefer my settings in manual and not with profile (i dont know the changes in each profile). https://forum.xda-developers.com/redmi-note-3/themes/xgh-t3701825
You can enable ForceDoze with patch https://forum.xda-developers.com/redmi-note-3/themes/universalforcedoze-deepsleep-googledns-t3770350
With ForceDoze you may have problems with sync of message apps or with clock update (you can fix it in your battery settings> optimized apps)
How often does AGNI gets updated?
drckml said:
How often does AGNI gets updated?
Click to expand...
Click to collapse
i dont know but is really good for me.
Equally if you like stock kernels may use RR stock kernel + Kernel Adiutor without problems.
link of agni kernel: https://forum.xda-developers.com/re...nel-24-09-2016-agni-puremiui-mm-v1-4-t3468042
last update 2018-06-28
I tried Vulmax and the battery config and it made my phone really fast, literally as in the animations of closing and opening of apps became way too fast. I think Kernel Auditor would be better for me.
drckml said:
I tried Vulmax and the battery config and it made my phone really fast, literally as in the animations of closing and opening of apps became way too fast. I think Kernel Auditor would be better for me.
Click to expand...
Click to collapse
you can change animation speed from the developer options in the settings.. disabling animation saves a bit battery thats y it is disabled