This kernel is just as stable as CM's which is very important to me, but it's also got a lot of improvements on top of that.
Installation instructions: flash zip from recovery. That's all.
Only flash on jewel running AOSP Lollipop ROMs with the new partition layout, though I've heard that the kernel still works (for now) with KitKat AOSP ROMs as well.
Do not download the source and try to flash it. See post 2 for download link.
Source: https://github.com/Colonel-Corn/android_kernel_htc_msm8960.git
Yeah I'm really that cheesy.
Instructions for flashing: It's pretty simple, really. No tricks. Flash it just like you would the ROM. Do it after flashing the ROM though.
Below are the basics. I'll add detail later and give credit where it's due (though that information can be found in the commits too).
Features added already
Sweep2Wake
SweepUp2Wake
Double tap to wake
Force fast charge
Voltage control (with overclock support)
MP Decision
CPU Governors
wheatley
pegasusq
intellidemand
intelliactive
lagfree
badass
smartmax
interactive
conservative
ondemand
userspace
powersave
ondemand
performance
GPU Governors
performance
ondemand
simple
interactive
conservative
IO Schedulers
noop
deadline
row
cfq
bfq
sio
fiops
zen
TCP Congestion Control
cubic
reno
Optimizations
LZ4 Compression-Decompression
-Wstrict-aliasing=3
Features on deck
Sweep2Sleep
Optimizations
Considering adding -f-strict-aliasing if the situation is all gain. Not willing to sacrifice stability or features for it.
IO Schedulers
none on deck
CPU Governors - None - Lots added already. Let me know what others you'd like to see though!
GPU Governors - None - I haven't experimented with them much myself, so give me your list.
TCP Congestion Control- None - Give me your list.
Current issues
Though the kernel is at least as stable as CM's (as as of this writing), there are some bugs in a few features.
HTC Logo feature references need to be removed as it isn't part of the touchscreen on the Jewel. Those features will never work on this device.
Not loving this S2W implementation. It's got features in the code that won't work on jewel, but it's written in such a way that I can't easily remove the extra items without breaking either the feature or the build. Would prefer to use the version implemented in Bubba kernel, but its dependent on powersuspend, which doesn't want to boot after the WiFi driver updates were made by CM.
Credits: @javelinanddart - His Frosted Kernel is great, and I'd love to get it working on Jewel. Unfortunately I can't seem to compile it from his source, so I've cherry-picked a ton of commits from him. I'm going to keep picking one commit at a time and making fixes as I go. My hope is that I'll be able to find the offending lines of code in Frosted, that Jewel doesn't like, and hopefully get those changes incorporated into Frosted. @faux123 for putting together some of the most amazing features together. Guys like him who create features and write original code are really the ones who deserve the credit. All I'm really doing is an advanced cut & paste job, then crossing my fingers and hoping like hell I can get their work to function on our device. @intervigilium - Has spent a ton of time on msm8960 kernel in particular. He seems to author more of the commits I cherry-pick than anyone else.
@captain throwback - Not sure where to begin. If it weren't for him, this device may have died a long time ago. It hasn't been his daily-driver in close to a year, but he continues to maintain the device anyway. He's also been tremendous with coming back to help users with problems. @showp1984 - Has authored tons of lines of original code and new features. @rmbq - Whose Bubba Kernel made me appreciate just how much can be done with a kernel and is 90% of the reason I started Half-Popped. He didn't just cherry-pick his way there either. His commits include some really impressive original feature code.
@everyone else in the development community - A few of my commits in the beginning did not properly maintain authorship. For that, I am very sorry. I'm still really new to this and didn't know how to, or understand the importance of, maintaining proper authorship of the work of others. While I was totally ignorant about how rude this is, and it was only a handful of commits out of hundreds, proper credit should have been given. I'd love to know how to correct this, but I honestly don't know how.
https://www.androidfilehost.com/?w=files&flid=26515
3/1 - Added MP-Decision
2/28 - Added voltage control & overclocking
This folder on AFH has been set to restricted.
goliath714 said:
This folder on AFH has been set to restricted.
Click to expand...
Click to collapse
Thanks for letting me know. It's fixed now.
New build posted.
https://www.androidfilehost.com/?fid=95916177934535260
The big change is in getting voltage control fixed. I've also added OC support.
This was compiled with SaberMod 4.8 though, which is not as good as what I've used in the past. I'll be changing it soon enough though.
Let me know if you have any trouble. All you have to do is flash the zip.
Last night I decided to adjust my kernel governor settings.
Deep sleep - 73%
384 - 19%
The remaining 8% is all over frequency-wise and is about the amount of time I spent using the phone.
Quadrant score of 6126 running BeanStalk. OC frequency 1728000 with top end voltage at 1275000. Low end voltage is set at 850000 for 384000 frequency. No reboots yet. Am considering coding the low end frequency limit to 194000 since I'm having no stability issues so far.
I'm providing this as a baseline for comparison for you and for future reference for myself. If you're having bad battery drain issues, I can post my governor configuration if you'd like.
I'm pretty proud of what I've done with this, but I'm thrilled to discover that a much more skilled developer is working on a kernel for Jewel. I can't wait until it's ready.
SELinux PERMISSIVE mode kernel
This is otherwise identical to the 3-1-2015-3 kernel.
This disables Enforcing mode (kind of obvious). With enforcing mode enabled, every app is restricted to playing in its own sandbox. In permissive mode, an app can play in its own sandbox, but also play in all of the other sandboxes too. This was only created to get around issues with installing Xposed. I wouldn't recommend running SELinux in permissive mode. You've been warned.
I'm having trouble installing this. Installing the zip, TWRP says: "Updating partition details ... ... done. Failed". I've downloaded the file a few times. There's no md5 to verify. I've also tried flashing with different ROMS, but no luck. What am I doing wrong?
7357 said:
I'm having trouble installing this. Installing the zip, TWRP says: "Updating partition details ... ... done. Failed". I've downloaded the file a few times. There's no md5 to verify. I've also tried flashing with different ROMS, but no luck. What am I doing wrong?
Click to expand...
Click to collapse
What twrp are you on? Hboot?
There won't ever be an md5 with the kernel, but I've made over 100 kernel zip files using this method and never once had a failure. I'm eager to get more info so that I can help you.
fizbanrapper said:
What twrp are you on? Hboot?
There won't ever be an md5 with the kernel, but I've made over 100 kernel zip files using this method and never once had a failure. I'm eager to get more info so that I can help you.
Click to expand...
Click to collapse
(Details in my sig) Hboot 2.10. TWRP 2.8.5.0 CPTB. S-Off. File: android_kernel_htc_msm8960-cm-11.0.zip
The reason I mention the md5 is to verify that the file didn't corrupt during download. I've never had a corrupted download, but you never know.
7357 said:
(Details in my sig) Hboot 2.10. TWRP 2.8.5.0 CPTB. S-Off. File: android_kernel_htc_msm8960-cm-11.0.zip
The reason I mention the md5 is to verify that the file didn't corrupt during download. I've never had a corrupted download, but you never know.
Click to expand...
Click to collapse
I'm perplexed. Did I post a link to a zip file with that title? How many megs is your file?
It kind of looks to me like you downloaded the whole source from post #1 as a zip somehow and are now trying flash the whole repository to your phone.
fizbanrapper said:
I'm perplexed. Did I post a link to a zip file with that title? How many megs is your file?
It kind of looks to me like you downloaded the whole source from post #1 as a zip somehow and are now trying flash the whole repository to your phone.
Click to expand...
Click to collapse
I downloaded the zip from the link in post 1. I see that the file from post 6 is different, so I'll give that one a go.
https://www.androidfilehost.com/?fid=95916177934539829
3/10/15 - PERMISSIVE
UC to 192000, OC to 1836000 - be careful with the kernel settings when OC this high. I've had no issues yet, but 1.83 vs 1.5 is not an insignificant difference.
A word of advice on the permissive kernel. Use a program that manages your SELinux policy. Set it to Enforcing, and applied upon boot. The device will start the boot process in permissive mode, which is when xposed is loading, then it will change back to Enforcing at the end of boot. There are still security concerns, but we've limited the risk to just part of the boot sequence.
No reboots with the UC last night. 68% deep sleep, and 19% at 194000. Woke right away this morning with dt2w.
Dt2w and sw2w can be disabled if you're using trickster mod. You will see a boost in battery life. Not an option for me though, since my power button is dying.
Might not have this device much longer because of it. The day will soon come when I won't be able be able to break out of a bootloop and with the simulated battery pull (hold down power button for 10 seconds).
No idea what to replace it with though. I really like the idea of having a ton of custom ROM and kernel options like with the Nexus line, but I really enjoy the challenge and learning experience that comes with compiling. It's been worth developing for Jewel because there are so few of us who are doing anything for the device, so I feel like I've actually contributed something. I see the download numbers though and realize that I'm now contributing to a very small group of people. The nexus line has no need for me as a wannabe developer though, since there are many highly skilled devs already.
I'll fix the defaults later, but the voltages for the OC frequencies are set too high. Change them to max of 1250000 and you shouldn't have any problems OC to 1836000 frequency. I OC for smoother performance with normal use. If you're overclocking and playing games, that much sustained heat could be a problem.
If there is any interest, I can easily build a kernel without the sweep and tap to wake features. This would be useful for anyone who wants to trade in those features in exchange for better battery life, but doesn't have an app on their device that can disable them.
Lol. I just found tap to wake last night. I'm such a mo mo.
Thanks for the kernel, man. Digging it so far.
fizbanrapper said:
If there is any interest, I can easily build a kernel without the sweep and tap to wake features. This would be useful for anyone who wants to trade in those features in exchange for better battery life, but doesn't have an app on their device that can disable them.
Click to expand...
Click to collapse
That would be awesome if you could make a kernel like that. I don't really use sw2w or tap to wake.
jcruz942 said:
That would be awesome if you could make a kernel like that. I don't really use sw2w or tap to wake.
Click to expand...
Click to collapse
You're in luck. I saw your post right as I was finalizing some other improvements.
https://www.androidfilehost.com/?fid=95916177934540722
I built this kernel with d2w & s2w, but they're disabled by default. Those features wont drain your battery now, unless you specifically enable them. In retrospect, that's probably what I should have done in the first place.
I've cherry-picked memory improvements, thermal improvements, and set SELinux back to enforcing. If someone wants me to make an updated permissive kernel, just ask. It takes all of a minute for me to change that setting.
I also rolled back the voltages to 1250000 on the higher OC frequencies. You can push it higher if you'd like, but not by default. Still keeping OC at 1836000 max.
Related
TKSGB KERNEL HAS BEEN RENAMED TO KGB KERNEL!
NEW THREAD HERE
PLEASE DISREGARD THE REST OF THIS POST
----------------------------------------------------------------------------------------------------------------------------
There aren't very many tweaks in yet but it should be stable again and a lot of ext4 and lowmemkiller lag issues should be gone! Here's an incomplete list of features.
Voodoo: Lagfix and sound. No color for now
CPU governors: The same ondemand, ondemandX, interactive, interactiveX, smartassv2 and ondemandX as default
I/O schedulers: The same cfq, bfqv2r1, sio, deadline, vr and deadline as default with the last three being optimized for flash
jhash3, OC/UV, BLNv9, 3rd-party batteries, boot animations
LED flashlight, CIFS and TUN
zram
User-adjustable in-call audio boost, no boost by default!
Preliminary dock audio support, need more feedback
Autogroups and Tiny RCU removed pending performance evaluation
How to adjust in-call audio and zram
Run callboost or zram from a root prompt (AS ROOT). To manually tweak zram size or call boost volumes, look in /etc/init.d/ for the startup scripts they drop after enabling. The filenames are 05zram and 91callboost.
Recommended settings for callboost are 1 or 2, 0, 0, and 0 or 1. zram is 12.5% of available RAM by default.
The zram script crashes when enabling if there isn't enough RAM free. Don't run zram enable unless you're sure you have enough RAM on hand, such as right after a fresh reboot.
How to use dock audio
Preliminary testing (thanks ACLakey even if you do have a Mesmerize ) indicates it does something right. I have no way to know if it's doing something wrong or even if it doesn't work at all so give me feedback.
How to use your phone as an access point
Get the latest Wireless Tether for Android (3.0b6 last I checked), and set mode to Samsung softap in the settings. It won't be peer-to-peer and WPA2 encryption will work.
"STABLE" DEVBUILD 1027
CWM zip: http://www.mediafire.com/?tjsadn6v0cocqy6
Odin: http://www.mediafire.com/?redm61dt4uwjpt2
Oh, and just because...
"BLEEDINGEDGE" DEVBUILD 1116
CWM zip: http://www.mediafire.com/?mg78n9a77sje6e4
Changelog: Drivers/kernel settings from EI20, except for the dpram driver which is still from EH09. Removed carrier hotspot tracking code in init.rc (doesn't make hotspot tracker directories in /system), ARM and memory and RCU updates/tweaks, changes to scripts in ramdisk.
Still pretty untested
P.S. Don't confuse one for the other, thanks
Please excuse the mess below.
----------------------------------------------------------------------------------------------------------------------------
Kernel is alpha and untested for the most part, and I cannot guarantee stability or robustness of features. Still, I've been using it every day for a few weeks now, and it's pretty stable for me. It should work on most EH09-based ROMs out there, including PowerWashed, GeeWiz and TSM Resurrection, just to name the ones I know as I am a Fascinate user. It works with Mesmerize and Showcase too, I'm given to understand, with the proper ROM tweaks (which I don't claim to know anything about).
FEATURES
Voodoo: Lagfix, Sound v10, and Color v2. Use with Voodoo Control.
CPU governors: conservative, performance, ondemand, ondemandX, interactive, interactiveX (ondemandX as default)
I/O schedulers: Noop, CFQ, BFQv2-r1, SIO, V(R), Deadline (deadline as default). The last 3 are optimized for use with flash memory.
Autogroups, jhash3, Tiny RCU for responsiveness.
OC/UV up to 1.7GHz, with Voltage Control/Pimp My CPU.
Third-party battery support allows use and charging of aftermarket batteries and batteries for other Galaxy S phones.
No hotspot monitoring with the WiFi driver from the i9000.
In-call audio boost: Higher volumes and mic gain settings. Works OK as of 10/18.
CIFS and TUN included in base kernel. UTF-8 native language support was already there.
BackLightNotifications v9 with a ported touchkey driver from the i9000. Automatic installation of the proper liblights. Use BLN Control and/or Blinky to get down to business.
Bootanimations: Works with /data/local/bootanimation.zip, /system/media/bootanimation.zip, or /system/media/sanim.zip. Automatic installation of the proper bootanimation binary.
LED flashlight: The camera LED makes a surprisingly good flashlight. Activate with any of a number of flashlight apps from the Android Market.
zram from Linux 3 (credit imoseyon). Open up a terminal and run "zram" to get started. By default "zram enable" will use 12.5% of total RAM as an LZO-compressed ramdisk and set up swap space on that. Don't run the script unless you have at least 50MB or so of RAM free. To change the size of the zram, edit the relevant line in /etc/init.d/05zram (it's in bytes, do your own math) and reboot.
Other standard features: init.d support, adb shell gives you a root prompt
Various behind-the-scenes tweaks: A growing list of ARM and Samsung kernel/driver patches for hardware errata and Linux kernel patches to enhance interactivity
CHANGELOG
For complete changes refer to github.
Code:
[size=4][B]1018[/B][/size] Most changes on this one are behind the scenes.
[b]In-Call volume boost changes[/b] +12dB at earpiece only & mic gain boosts
[b]Update interactiveX and ondemandX CPU governors[/b]
[b]ondemandX as default[/b] i'm pretty sure this is a backport from linux 3 too
[b]Use CodeSourcery 2010q1 toolchain[/b] bad Linaro, bad!
[b]zram backport[/b] and add zram script to initramfs
[b]Memory tweaks[/b] optimize memcpy functions, tweak lowmemorykiller
[b]Bugfixes[/b] to autogroups and a couple other things
[b]initramfs changes[/b] probably falls under bugfixes actually
[size=4][B]1012[/B][/size]
[b]In-Call volume boost changes[/b]
[b]dvfs lock fixed[/b], no more pegging CPU at 1440MHz with bluetooth
[b]lowmemkiller settings[/b] changed in init.rc
[size=4][B]1010[/B][/size]
[b]In-Call Volume boost[/b] numbers were chosen arbitrarily, need detailed feedback
[b]Autogroups, [strike]Tiny Preempt RCU[/strike][/b] woopz
[b]Bootanimation support[/b] install required binary on boot
[b]Add ondemandX CPU governor[/b]
[b]ondemand as default[/b] interactiveX pegs the CPU high on hw video playback
[b]optimize sio and vr[/b] for flash devices
[b]Voodoo Color fix[/b] no more green tint at low brightness
[b]More tweaks[/b] ARM, Samsung, buildflags; see github
[size=4][b]1006[/b][/size]
[b]Third-party battery support[/b] apparently works fine as of 10/10
[size=4][b]1005[/b][/size]
[b]BackLight Notifications[/b], neldar-flavored, finally!
[b]Installs liblights on boot[/b]
[b]deadline scheduler[/b] tweaked for flash memory
[b]interactiveX governor is default[/b]
[size=4][b]0927[/b][/size]
[b]Initial release[/b]
KNOWN ISSUES/TO-DO LIST
Dock audio: I've almost got this merged but have no dock and no way to test.
Lots more tweaks and testing. I know it isn't fully polished and some things could use cleanup and updating. There is also a veritable sea of tweaks out there that I haven't even started parsing through.
Autorooting, autoinstall of busybox, bash, nano, and a bunch of obnoxious init.d scripts
Recovery with crazy rainbow colors and logos, etc.
TKS does not yet come with CWM. The version most of you are using is probably the blue ClockworkMod Recovery 3.0.2.8x by I believe times_infinity. It's pretty compatible with my kernel with a couple of minor bugs. Mirrors: http://www.mediafire.com/?91cq99066cwph4d http://www.multiupload.com/QEP9U2MC2G
CWM-FLASHABLE ZIPS
NEW 1018 http://www.mediafire.com/?07nero2764ktcn4 http://www.multiupload.com/V81P3FNJOD
1012: http://www.multiupload.com/JFLEF7U7EH
1010: http://www.mediafire.com/?9f58oks4a988a7o http://www.multiupload.com/PDXE2U08IG
1006: http://www.mediafire.com/?ev1g554de7ab9g0 http://www.multiupload.com/KB7833E0E4
1005: http://www.mediafire.com/?em8md8yxq7o61ny http://www.multiupload.com/EHJFAPYW51
0927: http://www.mediafire.com/?76ea7izaqc3e7a2 http://www.multiupload.com/O1HRXNCQQW
ODIN TARS
NEW 1018: http://www.mediafire.com/?didta4h7vk0uh8p http://www.multiupload.com/EXS2REYBAI
1012: http://www.multiupload.com/W8VZQGA3AG
1010: http://www.mediafire.com/?2tiiwoeav61ha0f http://www.multiupload.com/4XORWQIQIZ
1006: http://www.mediafire.com/?p9u3ow2mw70n26c http://www.multiupload.com/58XYU7OF86
1005: http://www.mediafire.com/?5ojvasq4lurvxnp http://www.multiupload.com/4W2GPSZHU7
0927: http://www.mediafire.com/?rqwe26c1pi4766r http://www.multiupload.com/JST3N8AAIP
GITHUB
All I do is kang other people's work, get it?
https://github.com/kangtastic
Also where you can see the full changelogs.
THANKS
imoseyon: Merged Voodoo Lagfix by hand. Also, he and the next two guys and I are like the only ones doing anything with the TW GB kernel on this phone.
ccampos784: Merged Voodoo Sound, and some other dev work before I forked his branch.
djp952: Ported the i9000's Wi-Fi driver and killed VZ's hotspot monitoring dead. It wasn't the only thing he ported from the i9000 to get EH09 building. And on that note...
The Samsung Galaxy S i9000: It is truly the gift that keeps on giving. Comparing good work i9000 people have done on the i9000 and CM7 repos with the EH09 code makes broken things work again, period.
TeamSbrissenMod & Supporters: The TSM-Resurrection ROM got me to try EH09, but they've done lots of great work over the last year.
jt1134: Got me started with cross-compiling my first kernel, and he is responsible for most of the innovation on this phone.
Other "historically important" people: adrynalyne, imnuts, SirGatez, nemesis2all, navenedrob etc.
IRC people too numerous to list and random people too numerous to list from whom I have taken all sorts of ideas and code that ended up in this kernel
DISCLAIMER
I am not a developer and the sole reason I started was so that I could be happier with the kernel I use on my own phone. If something does not get added or fixed, you are welcome to do it yourself.
I take no responsibility for exploding phones, voided warranties, missed appointments, dead babies and the like which are claimed to be related to your decision to use my kernel in any way. You're in the "development forum."
That said, feel free to leave useful feedback and suggestions. For bug reports, link logcats and dmesg output. And enjoy!
INFORMATION REGARDING OC/UV VALUES
The default values in the Samsung source are as follows:
1000MHz arm_volt=1275mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1100mV
400MHz arm_volt=1050mV int_volt=1100mV
200MHz arm_volt=950mV int_volt=1100mV
100MHz arm_volt=950mV int_volt=1000mV
arm_volt_max=1350mV int_volt_max=1250mV
Of these the values that everyone talks about are the arm_volt values. arm_volt is what is modified by Voltage Control, Pimp My CPU, etc. int_volt is a secondary line that is not reported or directly adjustable by the user. The Glitch kernel plays around with int_volt for their different "leakage" versions, demonstrating that int_volt, too, plays a significant role in max overclock, but this isn't a concern of mine at the moment.
arm_volt_max is set to 1350mV which would then be the theoretical "overvolting limit". In this example you could overvolt 1000MHz by up to +75mV before running into driver limits.
Here are the default values in TKS.
1700MHz arm_volt=1500mV int_volt=1250mV
1600MHz arm_volt=1500mV int_volt=1250mV
1500MHz arm_volt=1500mV int_volt=1225mV
1440MHz arm_volt=1500mV int_volt=1200mV
1400MHz arm_volt=1450mV int_volt=1175mV
1300MHz arm_volt=1400mV int_volt=1150mV
1200MHz arm_volt=1350mV int_volt=1125mV
1000MHz arm_volt=1250mV int_volt=1100mV
800MHz arm_volt=1200mV int_volt=1050mV
400MHz arm_volt=1050mV int_volt=1050mV
200MHz arm_volt=950mV int_volt=1050mV
100MHz arm_volt=950mV int_volt=1050mV
arm_volt_max=1500mV int_volt_max=1250mV
Let's look at 100-1000MHz first. At 1000MHz there is a slight -25mV arm_volt undervolt (or just plain old undervolt) as well as a -50mV drop in int_volt for all frequencies <1000MHz. In other words, for stock frequencies there is already an undervolt built right in that you should take into account.
At higher clock settings the values are essentially best guesses at the proper settings for that speed, refined by community experience, so talking about a "proper" undervolt level is a little bit inaccurate. Note that voltage is maxed out at 1440MHz and above, but the secondary int_volt values keep increasing. The effect is a ramping up of total power supplied with increasing clockspeed, as it should be.
So I wouldn't be at all surprised to see 100-1000MHz benefitting from a couple +25mV boosts compared to "the settings I used to use on my old kernel" here and there and I'd pay attention to differences between the default voltages, especially 1200MHz+, of the old and new kernels. With different defaults, seemingly different undervolt settings could translate into the exact same amount of mV supplied.
awesome man...great to see eh09 finally getting some kernel love
hopefully once imoseyen gets his i500 from someone sending it, u can get some more help as well
(if u bet bln working ill reactive my fascinate for awhile lol)
I can give feedback about what DOES work despite being in alpha stage:
Voodoo color is working (personally, I like to go "punchy" on gamma hack)
OC is stable at least to 1400 for me with default noop/interactive, and with 100mhz state disabled (I could only go up to 1200 on MIUI without immediate instability on Glitch)
My phone is quite stable (so far) on this kernel, more so than what you'd expect on an alpha release
I'm glad you posted your own thread for this kernel comeradesven
Another Fascinating post by my XDA app...
This kernel is what I've been looking for
With a battery fix and in-call volume fix, I think I'll have a permanent GB solution! I'm hard of hearing and most of these GB kernels just don't cut it for me. CM7 (MTD) works, but Slacker caching doesn't work because of the file system. Slacker says tough s**t, we're not supporting it. So here we are. I'll put this on my spare Fassy and test it out today.
I'm also hard of hearing, but in-call isn't too, too bad for me on speakerphone... Media volume, on the other hand... IDK if media volume has anything to do with this kernel or if it's an EH09 issue...
Another Fascinating post by my XDA app...
Does this kernel use the Nexus S color source like on Glitch's kernel?
FDro said:
Does this kernel use the Nexus S color source like on Glitch's kernel?
Click to expand...
Click to collapse
If you're talking about mDNIe values, then no. I tried adding some new values earlier and it didn't work. It does have a ported Nexus S framebuffer driver like all Voodoo Color kernels AFAIK.
Awsome work sir!!
which one is better... voltage control or pimpmycpu?
now i use voltage control oc up to 1400 with uv 50 all way down. so far run smooth.
i use noop and ondemand, if i use conservative then phone get lag
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
djblu said:
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
will this eventually have a -100uv kernel. i've the best battery life using pbj kernels with that setup. hope this gets it too. will switch kernels once all the kinks get worked out.
thx for your efforts.
mgrimmenator said:
will this eventually have a -100uv kernel.
Click to expand...
Click to collapse
Voltage Control = roll your own undervolt
The only real missing feature is BLN.
Can't seem to get it to download on my fiancee's phone.
Just flashed 9-27 through cwm and flashlight confirmed working. Awesome job
sent from my SCH-I500 PWGB 2. 0b3 voodoo , shot v7
Does this kernel support non OEM batteries?
Idea: RAM optimization, if feasible
Another Fascinating post by my XDA app...
So far this kernel is working out great for me. Loving voodoo color. Makes me wish I waited on buying that Thunderbolt off eBay. The cwm file didnt work for me (probably a bad download, stayed on bootanimation for WAY too long, lagging the animation) so I used the Odin version instead. Booted instantly. Many thanks for putting this together.
Sent from my SCH-I500 using Tapatalk
Originally Posted by djblu
I purchased SetCPU originally, can I use it instead?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
IIRC the answer to that for this variety of overclock code is as follows.
Short answer: No
Long answer: Maybe but you might/probably will have problems
Click to expand...
Click to collapse
Thanks for the clarification. next question:
how do keep from getting stuck in boot loop? Do I need to reflash my recovery immediately after flashinging the kernal?
Sent from my SCH-I500 using xda premium
AIC Kernelfor LG G Pad 8.3 V500
Compatible with v500 STOCK BASED LG 4.4.2 roms ONLY! The "gamma improvement only" is available for other ROM's in the installer
This was just a private build that seems to have gained some demand to help with the v500 gamma issue. I have been running it the past week and it seems stable enough to share to other v500 users. I'm not a developer, I build and update TWRP for the Nabi tablets, have shared a few windows bat files, have a VB.net app to automate various mods to the Nabi's, and a lot of research of nvflash/APX nand formatting for the Nabi's. My only previous kernel builds were for the HP Touchpad for private use, and my Ubuntu computer. Basically taking what real developers have done and trying to make it work for my own use.
EDIT 5/11/14: I put the gamma improvement fix in just a stock kernel with no other changes, and the changes to CM11 kernel. There are 2 CM kernel version depending on which LG ROM you installed CM over to deal with the dimming issue at boot. Those are available in the new all in one installer.
Disclaimer:
Experimental. Use this at your own risk.
Please Please Please make a full backup of your tablet.
Base:
The starting source is V50020B from LG
Compiled with arm-eabi-4.7
Added features:
Initial
Improved gamma. Using default linear LUT (from 1.8-2.0 to 2.2-2.3 on my screen)
Default overclock from 1.72 to 1.78Ghz (no voltage increase)
Default underclock to 162 Mhz
Sysfs Voltage Table added for undervolting
Allow GPU to manually increase freq from 400Mhz to 487Mhz
Add GPU boost to GPU on demand governor
Add Faux Display interface (gamma control seems broken)
Add NTFS support(untested)
Add SIO Scheduler
Add FIOPS Scheduler
Optimize memcopy, string and square root functions
Add Intelliactive Governor
Download:
BETA: http://nabtabhacks.com/downloads/AICbeta2.zip Very stable but haven't got enough feedback to make it official. See changes here http://forum.xda-developers.com/showpost.php?p=54482330&postcount=229
Installer for all gamma improvement kernels, tested by numerous members(AIC, stock, and CM) http://nabtabhacks.com/downloads.htm
Installer AIC Kernel: http://nabtabhacks.com/downloads.htm
Uninstaller, returns to stock 20B: http://nabtabhacks.com/downloads.htm
Install:
Reboot to recovery(TWRP)
Make a backup, just do it
Install AIC_kernel_flashable.zip
Wipe caches/dalvik if you see fit
Reboot
Source:
AIC: https://github.com/aicjofs/android_kernel_lge_v500
Stock with gamma only: https://github.com/aicjofs/android_kernel_lge_v500_stock
CM: https://github.com/aicjofs/android_kernel_lge_v500_cm
Credits
I need to give some specific acknowledgement to "oubeichen" for sharing his kernel tree, and sharing of information. Also to id10terror's install script was the easiest to use as a template.
Woohoooo, Finally some gamma correction love. Flashing now
ROM: LG-V500_KOT49I.V50020B_US_Stock-BB-Rooted
Working much smoother with your kernel, thank you for sharing!
Tested it yesterday and it made a subtle but noticeable difference to whiteness and brightness. Thanks again
Sent from my LG-V500 using XDA Free mobile app
Am really eager to try! Thx a million times @op!
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
xyojimbox said:
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct
Sent from my LG-V500 using XDA Free mobile app
tested with LRS ROM (stock based ) , working perfectly!
many thanks!
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
bloommax said:
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
I have been using the kernel all day and it's working great! Thanks!
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
sleekmason said:
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
Click to expand...
Click to collapse
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
vimesUK said:
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
Click to expand...
Click to collapse
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
Have you looked at the install script I use for the 510? You have the ability to change ramdisk files on the fly using sed (easiest language I could find), by opening the device ramdisk, insert one liner, close ramdisk, combine into boot.IMG.
I have a couple of simple changes for allowing tethering, and values that I couldn't make without it! This part of it may work for you!
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
I kept auto brightness disabled. It does not work well for 4.4.2. You may replicate the brightness issue with the following procedure: 1) reboot the tablet; 2) when adjusting the brightness slider, you will find 0% is very (too) bright, and the entire range is high; 3) after sleeping and waking, the brightness is much dimmer, and the entire range from 0% to 100% is lower in brightness. It seems a procedure during wake modified the range of brightness settings.
Sent from my LG-V500 using Tapatalk
Run with stock kernel 20B. I will test urs by now
Well after having to do a complete reinstall due to another issue, I tried this kernel. Man I've only used it for a few hours but color me highly impressed :good: My gamma is almost perfect and it seems noticeably faster and smoother.
Really great job and thanks.
How is the battery life?
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
In my ignorance I was not aware of what could implicate the brightness values and range on this tablet. Having only just bought it, and upgraded to KK right away, I was not aware of how JB performed, in that respect. Prior to your kernel I was using the Screen Adjuster app as a sort of fix to compensate for the comparative (to my other tablets and phones) lackluster screen performance of the tablet. With the SlimKat ROM I was experiencing, but might have overcome them, some dimming issues which I did not understand.
Since restoring the stock KK backup and using your modified kernel I no longer need the screen adjuster app and things do seem to have improved.
Hi all,
some of you know me from the Samsung devices area, where I provide my kernels already for more than two years to Galaxy S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.).
Maybe you also know me from my OnePlus One kernels I added in winter last year to my portfolio.
Finally I got a Samsung Galaxy S5 afew weeks ago and decided to port my kernel also to this device. This is a sponsored device, so I want to say a big thank you to the people that made it possible, namely the ones in the German Smartphone Forum www.hubo.in !!!
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).
For the CM Boeffla-Kernel, please go HERE.
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Compatibility
Important: This kernel is only meant to be compatible with official Samsung stock firmware 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 !!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting 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.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for Android 5.0 kernels: KLICK HERE
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove (Note: not considered stable at the moment, you might face reboots!!!), intelliactive, intellidemand, wheatley, smartmax, slim, intellimm, nightmare, lionheart, pegasusq
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Wake up gestures implemented (double-tap-to-wake, swipe to wake)
Boeffla-Sound engine (Headphones and speaker volume configurable)
Configurable vnswap
zSwap configured fix to Samsung stock value of 1280 MB
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency configurable, touch boost switch
CPU Overclocking up to 2.84 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support
Show GPU frequency usage per frequency in Boeffla-Config
Color control to adjust RGB color space + inverted mode
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported (default is off)
Android logger (logcat) configurable
Kernel logger (dmesg) configurable
Charge rates for AC charger, USB and wireless charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, Important: make sure you unchecked option "Mount namespace separation" in SuperSU settings; do not mount inside /data or /storage)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Swap supported (but not recommended, zSwap used already)
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Automatic EFS backup
Full support for mpdecision for best compatibility and smoothness
(Important: use Boeffla-Config to configure min/max CPU frequencies + governors + schedulers only - or explicitely allow other apps/processes to overwrite this in Boeffla-Config settings, but expect weird side effects)
Integrated full busybox 1.23.1 (own compilation)
Auto-Root by kernel possible by request
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Google gcc 4.8 toolchain used for best stability
Initramfs of latest Samsung firmware
Based on latest Samsung sources
Kernel runs with SELinux enforcing by default, just as Samsung stock kernel for S5 - but can be configured to work in permissive mode in Boeffla-Config settings
Knox and Samsung rom security warnings removed
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
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 Galaxy S5 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
f2fs - it is known to cause various issues and compatibility problems
a CAF based kernel
anykernel method to use the ramdisk of the installed rom
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 correct kernel depending on whether you are on Samsung Stock, CM12 or CM11 !!!
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.1.72 or higher for the Galaxy S5 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
* Yank555
* ktoonsez
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Entropy512
* Faux
* Ak
... 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 logs:
Android MM 6.0.1
http://kernel.boeffla.de/sgs5/boeffla-kernel/mm60/changelog.htm
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
yeahh, dr andi so glad to see you here ..
You can also submit g900h variant? I can a beta tester
MOKIAAA said:
yeahh, dr andi so glad to see you here ..
You can also submit g900h variant? I can a beta tester
Click to expand...
Click to collapse
I am sorry, nothing changed in my attitude and golden rules over the past years.
No device, no kernel.
Apart from that, I need to stop adding new kernels now, it just gets too many already. And once I realize quality does drop, I have to stop.
Andi
Thank you,Andi
Thanks to @Lord Boeffla, finally today you've released your awesome kernel. Of course I saw @ZaneZam thanks to you too and I know we might have another version will be compiled and supported. Nice
Hi all,
Great kernel
Works very fine
Check this out...
Thanxxxx to the Lord for the hard work in the last week's
It's hard to access root rights on my device with Stock Deodexed Prerooted Rom. I've flashed Update-SuperSu 2.46 in TWRP, but RootChecker checked with no Root installed on device
ghoster76 said:
It's hard to access root rights on my device with Stock Deodexed Prerooted Rom. I've flashed Update-SuperSu 2.46 in TWRP, but RootChecker checked with no Root installed on device
Click to expand...
Click to collapse
Not a problem with Samsung Stock BOB7 firmware.
Andi
Hey Lord,
thanks for your awesome work! I really liked your kernel for the S3, even better you're now developing for the S5.
Immer weiter so men Jung!
Grüße aus Köln
Lord Boeffla said:
Not a problem with Samsung Stock BOB7 firmware.
Andi
Click to expand...
Click to collapse
I'm using BOC7 , and reflashing again
Thanks a lot Lord! Used to love it on my S3
Best configuration for battery-performance?
works great on BOC7.
Thank
borjaag said:
Thanks a lot Lord! Used to love it on my S3
Best configuration for battery-performance?
Click to expand...
Click to collapse
We need you guys to find that out, the S5 is not my daily-usage phone. So all I get is quite hypotethical at the moment.
Andi
Andi, forgive me, does it work on ANG7?
Never mind, Lollipop upwards
Looks good so far on XtreStoLite!
I'm just wondering if you are planing to add full sound configuration options?
Your sound implementation options allowed superb sound on S3 and I guess I'm not the only one missing it on S5
Looking forward to next versions!
f0xy said:
Andi, forgive me, does it work on ANG7?
Never mind, Lollipop upwards
Click to expand...
Click to collapse
See OP, first line. Clear "maybe"... I tested against BOB7 only as I cannot install 10 different roms. But you will tell us?
MewCore said:
Looks good so far on XtreStoLite!
I'm just wondering if you are planing to add full sound configuration options?
Your sound implementation options allowed superb sound on S3 and I guess I'm not the only one missing it on S5
Looking forward to next versions!
Click to expand...
Click to collapse
Would love to. But it is a completely different sound chip used in the S5, compared to the S3.
And it seems there is no way to get hold of any documentation for it (wdc9230), which would allow us dev to explore more of the chips capabilities.
If you saw a kernel providing more sound options, I am happy to get the information about it and checking if it can be ported. Then we would even know what the audio hub can do and what not...
Or someone can get Qualcomm to hand me over the documentation of their audio hub, then also more is possible. But many devs for sure have tried that in the past years already, so I am not very optimistic.
Andi
Battery friendly seems so good for daily usage at the moment, but Battery Saving with zzmoove / battery yank seems pretty lags. Hope it be implemented some next versions.
I'm Running BOC7
ghoster76 said:
Battery friendly seems so good for daily usage at the moment, but Battery Saving with zzmoove / battery yank seems pretty lags. Hope it be implemented some next versions.
I'm Running BOC7
Click to expand...
Click to collapse
Yes, it lags. And it is a hardly battery focussed preset, so it must lag.
That is why you have the choice.
Andi
*** 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
This is the first project I've shared on XDA, though I've maintained it for personal use for a while and posted some prior incarnations on Google+. Hope you enjoy it!
Features:
December 2018 security patch
open source: kernel, anykernel
forked from Franco Kernel
merged Linux Stable 3.10.108
Compiled with Linaro 4.9 and CopperheadOS's Hardened Clang
I/O Schedulers: noop (default), cfq, deadline, fiops, row, zen, maple, sioplus
TCP algorithms: Bic, Cubic, Htcp, Hybla, Vegas, veno, Westwood (default), Reno
FK Features: disabled verified boot flag for Android Pay (root still breaks), support for FKUpdater performance profiles, support for FKUpdater App (not verified as I don't use the app myself), KCAL tweaks in init script.
Reduced wifi wakelocks and wakelock period
Removed possible bluetooth memory leak
KCAL color control support
KCAL brought to Linux guidelines
Spectrum Profile Support: dozens of profiles from around the web included in source code
Touchboost disabled in spectrum profile
Filesystem Support: F2FS, vFAT, EXT4, NTFS
MSM hotplug driver (disabled by default, but toggle included in source code)
Fingerprint boost from Electron Kernel
Wireguard support
Power Efficient Workqueues
State Notifier
Tickless System / Idle
Gentle Fair Sleepers
Hima hotplug driver (see 2018-09 release notes)
Wake Gestures (partial, see 2018-09 release notes)
Many security / hardening features from CopperheadOS (see 2018-12 release notes)
Downloads:
Oreo, 8.1 (Stable / Final): angler-kernel-20181221.zip
Pie, 9.0 (Testing Builds): pie-testing-aosip-20190130.zip, pie-testing-statixos-20190130.zip
Installation:
Boot to TWRP, backup (boot, system, data)
Wipe Dalvik / ART Cache and Cache
Flash the kernel.zip
Wipe Dalvik / ART Cache and Cache
Reboot and enjoy
Note: Sometimes rebooting directly from TWRP results in a boot freeze at the Google splash screen. Just power off and boot up again.
Battery Life / Performance Tests:
Spectrum: Battery: Total Drain: 6.8%/h, Sleep Drain: 4.96%/h, 11% SOT, 17.8 Hour Test (tested version - kernel 20180728, battery v1.3 profile)
Spectrum: Balance: Total Drain: 9.7%/h, Sleep Drain: 6.6%/h, 12% SOT, 19 Hour Test (tested version - kernel 20180728, balance v1.2 profile)
Older Version: June 2018
Thanks:
@osm0sis / AnyKernel2
@nathanchance / Flash Kernel and many guides
@franciscofranco / Franco Kernel
@frap129 / Electron Kernel
@flar2 / ElementalX Kernel
@Adi Shakthi / God's Kernel
@zx2c4 / Wireguard
@phantom146
PS: I'm on Telegram now too!
Profile: @savagezen
Discussion for this kernel: @sz_kernel_angler
Want to stay even more up to date?
Install the IFTTT app
Get notifications for testing releases - Applet Link
Get notifications for source code releases - Applet Link
Changelog:
v20181221 Release Notes
v20181124 Release Notes
v20180910 Release Notes
v20180808 Release Notes
v20180728b - fixed spaces in localversion resulting in kernel name not showing in Settings app.
v20180728 Release Notes
Bugs:
Boot Loop / Freeze on Android 9.0 Oreo.
FAQ:
Need Help / Want to Help? Join the my Telegram Channel: @sz_kernel_angler
Is this kernel compatible with Android Pie (9.0)? It should work out of the box, however several users have reported boot freezes / loops on Pie. I haven't had a chance to test it fully in Pie and am still on Oreo myself. If you run into issues, try running with SELinux as permissive or reach out on Telegram.
Nice, gonna give this a run. Kudos for adding detailed instructions on your site.
Nice, was hoping for new kernel a long time
I would like to suggest the "Hima Hotplug" for your kernel, it is so fluid and great on battery life (experience from sphinx kernel for bullhead)
Pump Ac7i0n said:
Nice, gonna give this a run. Kudos for adding detailed instructions on your site.
Click to expand...
Click to collapse
You're welcome. It is as much for me to remember how to do stuff in the future with other devices as anything else. Glad others can benefit from it as well.
eurochild said:
Nice, was hoping for new kernel a long time
I would like to suggest the "Hima Hotplug" for your kernel, it is so fluid and great on battery life (experience from sphinx kernel for bullhead)
Click to expand...
Click to collapse
Thanks for the suggestion. Browsing source code now...
savagezen said:
You're welcome. It is as much for me to remember how to do stuff in the future with other devices as anything else. Glad others can benefit from it as well.
Thanks for the suggestion. Browsing source code now...
Click to expand...
Click to collapse
just wanted to say solid first public kernel. super smooth
Thank you for the new kernel,so far so good
Smooth so far, great job.
though is it just me or does the Settings app display "Unavailable" under Kernel version? EX Kernel Manager displays the kernel version just fine.
Maybe it has something to do with the presence of spaces in the kernel version name?
aureljared said:
Smooth so far, great job.
though is it just me or does the Settings app display "Unavailable" under Kernel version? EX Kernel Manager displays the kernel version just fine.
Maybe it has something to do with the presence of spaces in the kernel version name?
Click to expand...
Click to collapse
I see the same under about phone.
aureljared said:
Smooth so far, great job.
though is it just me or does the Settings app display "Unavailable" under Kernel version? EX Kernel Manager displays the kernel version just fine.
Maybe it has something to do with the presence of spaces in the kernel version name?
Click to expand...
Click to collapse
Lawlrus said:
I see the same under about phone.
Click to expand...
Click to collapse
same here, nothing so important. if you click on it it shows the kernel info (atleast that is what happens on aosip rom)
eurochild said:
same here, nothing so important. if you click on it it shows the kernel info (atleast that is what happens on aosip rom)
Click to expand...
Click to collapse
Yeah I agree, it is, by no means, a deal-breaker. I just wanted to point it out for newcomers because I sure had a grand time panicking over whether or not the installation went through.
Currently using this kernel with ABC rom, so far the best kernel ever, very smooth and good heat output
aureljared said:
Yeah I agree, it is, by no means, a deal-breaker. I just wanted to point it out for newcomers because I sure had a grand time panicking over whether or not the installation went through.
Click to expand...
Click to collapse
eurochild said:
same here, nothing so important. if you click on it it shows the kernel info (atleast that is what happens on aosip rom)
Click to expand...
Click to collapse
This does work on AOSiP. Stock ROM (and maybe others) it does not appear after tapping on "Kernel Version" in settings. As noted, third party apps like EX Kernel Manager and Kernel Auditor seem to display the kernel version correctly.
There are, in fact, spaces in LOCALVERSION in the config file. I'll add this under bugs in the second post and update when it's fixed.
PS: Glad you guys are enjoying it and to hear it runs smooth and cool! Usage stats for the 'battery' spectrum profile are in the updated OP. Testing the 'balance' profile now.
UPDATE 8/1: The 'kernel version' issues has been fixed. Notation is in second post and download link has been updated in OP.
This kernel kicks ass! Seriously, great work. One of my major complaints with the 6P was its over heating and then thermal throttling. I just didn't play certain games because of it. Now, after flashing this kernel it runs smooth and cool and games work again. Unreal. Truly love the way the phone works now. Not bad for battery life either but it's not my primary any more.
galakanokis said:
This kernel kicks ass! Seriously, great work. One of my major complaints with the 6P was its over heating and then thermal throttling. I just didn't play certain games because of it. Now, after flashing this kernel it runs smooth and cool and games work again. Unreal. Truly love the way the phone works now. Not bad for battery life either but it's not my primary any more.
Click to expand...
Click to collapse
Good to hear! Did you use the Gaming spectrum profile? I'm don't use my phone for games so I didn't test that outside of synthetic benchmarks. Also, the Battery spectrum profile should give pretty good battery life as it's very conservative.
Spoiler: I'm working on maybe adding the chill or relaxed governors to test as well.
No profiles, just default settings. I usually run a week or two on default before I mess around just so I can tell the difference in the tweaks.
I might play around but this phone is just for messing about now, picked up the Essential on the Prime deal and quite like it so the 6P is not a daily driver.
Gotcha. FYI the balanced profile is enabled by default.
savagezen said:
Gotcha. FYI the balanced profile is enabled by default.
Click to expand...
Click to collapse
Do you happen to have the link somewhere?
dirtyreturn said:
Do you happen to have the link somewhere?
Click to expand...
Click to collapse
All the profiles are in my AnyKernel repo on GitHub. There are a total of 30 profiles from around the web even though the Spectrum App only uses those numbered 0, 1, 2, and 3. I include my built kernel zImage-dtb in the AnyKernel repo so that you can clone it yourself and apply a different profile "manually" if you like. Just change the number in ramdisk/init.spectrum.sh, zip it up, and flash it.
Code:
if [ ! -f /data/property/persist.spectrum.profile ]; then
setprop persist.spectrum.profile 0 # change this number
fi
Note, if you use this method, and later select a profile from the Spectrum App, the Spectrum App choice will override the initial one, including after reboot -- because it applies the settings once the user space is reached.
@savagezen thanks! Also, kernel link?? I must be missing it.. Is it in the OP?
Sent from my PH-1 using Tapatalk