Hello guys just wanted you bring to your attention the Exceed Kernel built by @kairi_zeroblade for us Verizon users, check out the thread here:
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69474753
#######PLEASE FLASH KERNEL FROM INTERNAL STORAGE AND MAKE SURE THAT "SYSTEM" IS CHECKED UNDER "MOUNT" OPTIONS IN TWRP###########
#######All builds are based on the supersu 2.76 boot.img if you have supersu 2.78 and above, you will probably run into app permissions issues!!!##########
The Exceed 4F "V" varient is based on verizons latest PG2 kernel. It has been highly optimized by Kairi_zeroblade and includes:
All of the latest note 4 kernel sources so you have all of the most current fixes and optimizations from Samsung
Wakelock fixes
Exploit fixes
Ramdisk optimizations
GPU calibrations
It is compatible with note 7/s7 ports and stock TW Roms
Fully SELinux permissive(helps with installing viper4android and other mods)
And much more that I can't remember!
Kairi_zeroblade has all of the kernel settings pre tuned for amazing battery life and fast stable performace.
It is NOT recommended that you adjust the kernel settings EXCEPT for the ones available in Synapse.
Just flash and enjoy!
Do not forget to also flash the latest gpu drivers here:
https://drive.google.com/file/d/0B_3BNlXOVtO5bHp2MS12b291TjQ/view
These are based on the most current 805 adreno source (ph4 sprint I believe)
///////This kernel may give you the Volte and cloud (wifi calling) icons in the notification bar) see post 3 for my tip to disable Volte
Any questions or feedback, please post in the original Exceed thread^^^:good::good:
Side note........
///Kari_zeroblade does not like to add experimental features because they risk breaking the stability and battery life on the kernel. He keeps it simple and highly optimized. If there is a performance benefit you can be sure he will try to incorporate it though
Post#2 changelogs
Post#3 Volte icon
Post#4 UnderVolt/UnderAmp
######## BUILD 4M #######
2/2/17
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post70357447
Camera Improvements
Updated to the latest DPL2 source
SETCPU partially implemented(should give nice battery life improvements.)
Built in anykernel format so that should solve Supersu issues:good:
######## BUILD 4K ########
12/4/16
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69924893
New Nightlies guys!!
As promised I did bring a solution to the fts_wakelock and some security updates from Google..
Grab the test builds for your device here
#######PLEASE FLASH KERNEL FROM INTERNAL STORAGE AND MAKE SURE THAT "SYSTEM" IS CHECKED UNDER "MOUNT" OPTIONS IN TWRP BEFORE YOU FLASH###########
#######All builds are based on the supersu 2.76 boot.img if you have supersu 2.78 and above, you will probably run into app permissions issues!!!##########
Thank you, and for your issues, just attach a log on your post and we will see what we can do for you.. :good:
Another Thanks to those who helped me get my build laptop fixed.. Merry Christmas to you..
######## BUILD 4F ########
Kairi_zeroblade:
Grab it from here
FG = is for F and G variants
V = is for Verizon
T = is for TMobile version
P = is for Sprint version
As promised, these builds can now be flashed on both NOTE 7 ports floating around here and at the same time with STOCK rom's too..if you ever find any issues do report with logs..else as usual I don't give a damn..I don't know why you're using a stock source compiled kernel with nothing and yet scores are lower than usual stock samsung kernel and you're like an Angry Bird jumping happily, when you have this project to "help and improve" (just my 2 cents) which has shown great potential (and worth IMHO)..
I'm sure you're aware you only now have a handful of devs supporting your device and if in the process you loose them all due to users being disrespectful and uncooperative then its your loss and not ours..
F Variants wifi needs testing though the necessary measures to make it work are already in place and has been checked..
Some patches to fix some Exploits were already added in, same thing goes with some upstream fixes from Google and CAF..Ondemand crashing is also been fixed (in my case) as I have tried to replicate the issue and grabbed something to ponder on..
Again for those who are supporting the project, Thank you very much!!
######## BUILD 4E ########
http://forum.xda-developers.com/note-4/snapdragon-dev/kernel-xceed-t3344742/post69363834
kairi_zeroblade said:
This test is specifically for the Verizon Note 4 running stock MM (latest, I forgot the build..lol) as this uses the updated ramdisk from that OTA update..this build also uses the Verizon Samsung Config so this is the proper kernel for your variant..please make sure you are on the latest MM Bootloader and Baseband for things to properly work (though @joemill tested this out and he had no issues to report)..this build also incorporates important kernel updates from the DPH2 (if I remember it right!!) from the N910P (Sprint, which will be supported once I get the laptop fixed, thanks to @joemill again for the boot.img dump)..I'll also include a GPU driver update package from the same update..
Enough with the chit-chat let the games for Verizon begin..
Grab the build here..
and GPU Drivers here..
Thank you very much to those who take time to read and enjoy my posts..
Click to expand...
Click to collapse
The kernel is based on the latest Verizon build PG2 I believe. As long as your bootloader is unlocked and on PD1 PD3 or PG2 (any marshmallow Verizon bootloader) then this should work for you
If you are still on 5.1.1 lollipop follow this guide to upgrade:
http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727
This kernel was tested on the latest paulpizz rom release.
I personally do not use VoLTE or WiFi calling and have never activated them or set them up on my phone. I never had either the cloud icon or the VoLTE icon with Paulpizz kernel, or Oscar kernel. When I flashed exceed the VoLTE icon appeared even though it is not enabled in the settings, "advanced calling" section.
I BELIEVE that those icons appear from flashing a modified kernel, more specifically a selinux permissive kernel(since this is the only kernel I've found that is permissive). Jasmine rom 6 had the icons appear with its selinux permissive kernel so in version 7 he left the kernel selinux enforceing.
Since I do not use VoLTE I went to others.Xml in the system/csc folder and edited this line:
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE
To
<CscFeature_IMS_EnableVoLTE>FALSE</CscFeature_IMS_EnableVoLTE
Now the VoLTE icon is gone! and the 4glte icon is gray when connected to wifi instead of white all the time(I believe this means that 4glte radio is In a power save mode when not needed because you have a WiFi connection, also this improved my battery life quite a bit)
I personally would much prefer a kernel like exceed that has far better battery life and a selinux permissive kernel(so you can easy install vipers Android mods) even if it displays those icons.
I haven't had time to do anymore research but I would ask other verizon kernel developers(Paulpizz or Oscar since kari_zeroblade doesn't have a Verizon phone to test on) if there is a trick to remove those icons or if it is truly because the kernel is selinux permissive.
I would not mess around with any settings in kernel auditor or other kernel tweaking apps EXCEPT for synapse.
(Don't bother under clocking. The phone barely ever hits those top frequencys and when it does its better to complete the process fast and quick rather then hanging at a lower clock speed for a longer time. )
Undervolt and under amp in the synapse app can help your phone run cooler which will keep it from throttling cpu and gpu.
I personally run -45 uv and -12ua with zero issues in stability. If you undervolt you should always under amp to compensate for the drop in voltage. If you go to low your phone will just become unstable and probably lock up or reboot.
EVERY time you boot you will need to re apply those settings for safety.
Reserved~
The Synapse app days No UCI?
"Crack flashing is better than crack smoking"
Matthenson20 said:
The Synapse app days No UCI?
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Did you flash from your internal storage or external sd card? Also make sure that "system" is checked under the "mount" menu in TWRP
If it doesn't install then send us a twrp log after you make the attempt to flash the kerenl.
joemill said:
Did you flash from your internal storage or external sd card? Also make sure that "system" is checked under the "mount" menu in TWRP
If it doesn't install then send us a twrp log after you make the attempt to flash the kerenl.
Click to expand...
Click to collapse
Did all that, had synapse installed and did tweaks to voltages and amps, had a random reboot then synapse quit working
Will this work with N7 ports on? I'm running Chevy 2.7.3 build based on N5 port I believe
"Crack flashing is better than crack smoking"
Matthenson20 said:
Did all that, had synapse installed and did tweaks to voltages and amps, had a random reboot then synapse quit working
Will this work with N7 ports on? I'm running Chevy 2.7.3 build based on N5 port I believe
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
That's strange. The reboot could be because you under volt or under amp too much. How far did you adjust them?
It should work with all ports but you might be the first person to test on that rom my friend. L
joemill said:
That's strange. The reboot could be because you under volt or under amp too much. How far did you adjust them?
It should work with all ports but you might be the first person to test on that rom my friend. L
Click to expand...
Click to collapse
I'll retry, I went -40 and -12, I'll try 30 and 8
"Crack flashing is better than crack smoking"
Matthenson20 said:
I'll retry, I went -40 and -12, I'll try 30 and 8
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Every phone is going to be different, some may not undervolt at all, don't worry too much if it doesn't. It will not save very much battery life at all and will only make the phone run slightly cooler. The kernel should run really cool and have great battery life by default
joemill said:
Every phone is going to be different, some may not undervolt at all, don't worry too much if it doesn't. It will not save very much battery life at all and will only make the phone run slightly cooler. The kernel should run really cool and have great battery life by default
Click to expand...
Click to collapse
Yes probably my fault, saw a new kernel abs started foaming at the mouth lol, going to reflash tonight and give it a go, will report in 24 hrs and let thread know
"Crack flashing is better than crack smoking"
Matthenson20 said:
Yes probably my fault, saw a new kernel abs started foaming at the mouth lol, going to reflash tonight and give it a go, will report in 24 hrs and let thread know
"Crack flashing is better than crack smoking"
Click to expand...
Click to collapse
Haha I don't blame you. It's hard to resist the temptation to tweak. Just flash let it settle and enjoy
joemill said:
I.
Since I do not use VoLTE I went to others.Xml in the system/csc folder and edited this line:
<CscFeature_IMS_EnableVoLTE>TRUE</CscFeature_IMS_EnableVoLTE
To
<CscFeature_IMS_EnableVoLTE>FALSE</CscFeature_IMS_EnableVoLTE
Now the VoLTE icon is gone! and the 4glte icon is grayed out
Click to expand...
Click to collapse
I'm sorry for the off topic comment, but thank you for this fix. I've been looking for a way to gray out that 4g icon while connected to wifi for awhile. :good: @joemill
kevintm78 said:
I'm sorry for the off topic comment, but thank you for this fix. I've been looking for a way to gray out that 4g icon while connected to wifi for awhile. :good: @joemill
Click to expand...
Click to collapse
I think the battery life is better with it disabled too
Still a no go in Chevy's 2.7.3 build. Must be because it's a Note 5 port, Synapse app just says no UCI. I installed from phone memory with system mounted. Cleared caches and everything
"Crack flashing is better than crack smoking"
I have been using this kernel successfully for the last week on the Note4 Grace Note7 based ROM v2. It has not had any crashes, or problems that I have been able to notice. I have not tweaked any of the kernel settings in the synapse app.
I have not specifically paid attention to the battery life after flashing, as I have not underclocked yet.
Is there an undervolt and underclock baseline that all Note 4s should be safe to start at?
Thanks.
signupstuffid said:
I have been using this kernel successfully for the last week on the Note4 Grace Note7 based ROM v2. It has not had any crashes, or problems that I have been able to notice. I have not tweaked any of the kernel settings in the synapse app.
I have not specifically paid attention to the battery life after flashing, as I have not underclocked yet.
Is there an undervolt and underclock baseline that all Note 4s should be safe to start at?
Thanks.
Click to expand...
Click to collapse
Don't bother under clocking. The phone barely ever hits those top speeds and when it does its better to complete the process fast and quick rather then at a lower clock speed.
You can adjust the undervolt and under amp though, this will help your phone run a little cooler so it shouldn't throttle the cpu as quickly. It will not really help battery life though and you need to manually set it again after each boot.
Start with -45 under volt and -12 under amp (you need to under amp to compensate for the under volt) if the phone runs smooth (no lag or reboots for a few hours) then push it a little more.
You won't do any damage to the phone. If you push it too far it will just reboot and you'll be on default exceed settings.
I hope this isn't too dumb of a question, but I was wondering if I should flash the gpu drivers on my verizon Note 4. Thank you
dhplap said:
I hope this isn't too dumb of a question, but I was wondering if I should flash the gpu drivers on my verizon Note 4. Thank you
Click to expand...
Click to collapse
Yes they should work on all Note 4s. I run it on mine
Related
All benchmarks aside the N5 is in my opinion the best and the fastest
I've been trying to make it as fast as possible using different ROM / kernel / tweak combos.
Currently satisfied with Carbon ROM , Elemental X .34 , various build.prop tweaks , and custom sysctl / ram management tweaks using trickster mod & ROM toolbox pro.
Does anyone have any performance tweaks that can help me make my phone even faster ? Is there a way to use "fastboot" option like HTC devices ?
My fastest cold boot to lock screen time is 15.3seconds but I want shorter boot times xD
In using latest carbon ROM nightly, minimal gapps, dalvik opt zip. Latest GPU drivers.
Here are my build.prop tweaks :
debug.sf.nobootanimation=1
debug.composition.type=1
debug.egl.hw=1
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=300
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
ro.ril.fast.dormancy.rule=0
persist.sys.shutdown.mode=hibernate
ro.config.hw_quickpoweron=true
ro.max.fling_velocity=30000
ro.min.fling_velocity=20000
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
dalvik.vm.execution-mode=int:jit
ro.mot.eri.losalert.delay=1000
debug.sfbootcomplete=0
persist.sys.purgeable_assets=1
persist.sys.use.dithering=0
ro.wmt.blcr.enable=0
dalvik.vm.debug.alloc=0
Can anyone provide me with anymore ?
And so far the most free ram I've been able to come up with -.- on my old galaxy nexus with slim bean I had only 112mb being used but I forgot how I achieved that.
Removable apps :
All live wallpaper!
Live wallpaper picker
Com.lge.update
Update device
Calendar
Calendar storage
Sim toolkit
Voice+
Sound recorder
cLock widget
Certificate installer
Dev settings
DSP manager
Email
Exchange services
Face unlock
Picasa uploaded
Pico tts
Google tts
Google search
Stock launcher (you must have a replacement installed or bad things will happen >:])
VPN dialogs
TalkBack
Tags
Print spooler
AOSP any keyboard (must have a replacement!)
*list will be updated, I use ROM toolbox pro for all this stuff with the built in app manager. You can use any root explorer and go to /system/apps and manually delete or use titanium backup etc.
Your mileage may vary depending on what you use and what you don't. I've had 0 force closes with these removed!
I'd like to know your setups , and tips, and tweaks if any
im just curious, do you know what the build.prop lines that youre using do?
simms22 said:
im just curious, do you know what the build.prop lines that youre using do?
Click to expand...
Click to collapse
Some do nothing , some drain the battery, some actually force the GPU to do what's accessible via Dev settings. And others help my phone boot faster , stock boot time for me is 25seconds. Carbon boot time for me is 19seconds, with all the settings and stuff I've changed its now 15 seconds, some people call it placebo, but if you actually time it , and test them individually you can see effects whether negative or positive
simms22 said:
im just curious, do you know what the build.prop lines that youre using do?
Click to expand...
Click to collapse
Which BTW, is there anyways to implement a "hibernation" mode like the HTC fastboot option ? On the nexus 5 or other non HTC devices ...
Is your device stable at 3.0ghz? I can only get mine up too 2.88 without any random reboots. -.- I don't think a change of kernel will help would it ? I'll try trinity which is what you're using correct?
tadgerloks said:
Which BTW, is there anyways to implement a "hibernation" mode like the HTC fastboot option ? On the nexus 5 or other non HTC devices ...
Is your device stable at 3.0ghz? I can only get mine up too 2.88 without any random reboots. -.- I don't think a change of kernel will help would it ? I'll try trinity which is what you're using correct?
Click to expand...
Click to collapse
stable at 3014mhz, not quite. ill use it for several hours, then itll just lock up and reboot. try playing with your voltage at 3014mhz, mayne you can get your phone to run it. and yea. trinity is what i use
simms22 said:
stable at 3014mhz, not quite. ill use it for several hours, then itll just lock up and reboot. try playing with your voltage at 3014mhz, mayne you can get your phone to run it. and yea. trinity is what i use
Click to expand...
Click to collapse
Is yours on the stock voltage for that freq? Would you mind sharing the voltage if its not .
And my favorite prop tweaks are the min/max fling + window mngr because they make scrolling oh so smooth!
tadgerloks said:
Is yours on the stock voltage for that freq? Would you mind sharing the voltage if its not .
And my favorite prop tweaks are the min/max fling + window mngr because they make scrolling oh so smooth!
Click to expand...
Click to collapse
my voltage is at the default voltage for my phones binning. but i do play with it a occasionally. it can run fine within a small range at 301hz. its at 1150mV, 1140-1165mV is what itll range.
simms22 said:
my voltage is at the default voltage for my phones binning. but i do play with it a occasionally. it can run fine within a small range at 301hz. its at 1150mV, 1140-1165mV is what itll range.
Click to expand...
Click to collapse
Alright just got latest trinity , will test it for a few hours against elemental, rolling back to .29 due too boot times lol xD
tadgerloks said:
Alright just got latest trinity , will test it for a few hours against elemental, rolling back to .29 due too boot times lol xD
Click to expand...
Click to collapse
B10 is the latest trinity kernel
simms22 said:
B10 is the latest trinity kernel
Click to expand...
Click to collapse
Yes just flashed it, got nothing but fc's on carbon rom nightly 4/05 ... what roms is the trin kernel designed for.? Restoring backup right now as flashing elemental didn't save it... guessing trinity changed the ramdisk ?
tadgerloks said:
Yes just flashed it, got nothing but fc's on carbon rom nightly 4/05 ... what roms is the trin kernel designed for.? Restoring backup right now as flashing elemental didn't save it... guessing trinity changed the ramdisk ?
Click to expand...
Click to collapse
Search the trinity thread for a anykernel release of B10. I believe that release will work fine on carbon.
Sent from my Nexus 5 using Tapatalk
akash3656 said:
Search the trinity thread for a anykernel release of B10. I believe that release will work fine on carbon.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'll have to check the thread then , trinity B10 didn't work for me on Latest Carbon nightly , maybe I either roll back to a previous nightly or previous trinity build
Edit : just found the hybrid anykernel T5B10 build. Will give trinity another go with carbon and see how things pan out over the next few hours ?
tadgerloks said:
I'll have to check the thread then , trinity B10 didn't work for me on Latest Carbon nightly , maybe I either roll back to a previous nightly or previous trinity build
Edit : just found the hybrid anykernel T5B10 build. Will give trinity another go with carbon and see how things pan out over the next few hours ?
Click to expand...
Click to collapse
That's the one I'm talking about!
Sent from my Nexus 5 using Tapatalk
tadgerloks said:
Yes just flashed it, got nothing but fc's on carbon rom nightly 4/05 ... what roms is the trin kernel designed for.? Restoring backup right now as flashing elemental didn't save it... guessing trinity changed the ramdisk ?
Click to expand...
Click to collapse
not at all. try redownloading and reflashing.
simms22 said:
not at all. try redownloading and reflashing.
Click to expand...
Click to collapse
I tried the normal b10 again, same issues. Just finished flashing carbon and the hybrid version of b10, and I can confirm it's working! Carbon ROM has traces of both AoSP and CAF , so normal trinity b10 was causing problems. This one is working though I can say I'm really missing the "cooler colors" of elemental ...
tadgerloks said:
I tried the normal b10 again, same issues. Just finished flashing carbon and the hybrid version of b10, and I can confirm it's working! Carbon ROM has traces of both AoSP and CAF , so normal trinity b10 was causing problems. This one is working though I can say I'm really missing the "cooler colors" of elemental ...
Click to expand...
Click to collapse
ahh.. the caf thats why.
Hi,
I would say... delete all the additional lines on your build.prop (I mean the ones you added). Most of them does nothing at all or they are worse or have side effects. Search on Google for each line and see the first/second page and you will see for what device it is made for (and the date of the threads...) then you will understand. remember you are on Kit Kat, thes tweaks were good (at least) on Gingerbread, maybe ICS but that's all... There are also some threads about these lines, tested and examinated in Android code source.
You will have better results by tweaking the CPU governor and i/o scheduler you are using. VM settings are good too but you will need a few days of tests to see what is right or wrong.
I tested a lot of build.prop edits (and like you I added a bunch of them), like the ones you posted and other ones floating around on XDA in some threads in the General Android forum..., I always delete all these lines, there is always something wrong at some time.
Keep your build.prop clean (well one or two are useful, I speak mainly about all the "performance" tweaks like all the "debug about the GPU/dalvik...." lines, same thing for the scrolling tweaks )
You will see if you really tested that, at least, all is same as before even without all these tweaks in general UI. In fact, like you said, one line does the same thing as the "Disable HW overlays" in Developer options.
Even some "devs" add these lines in their roms..., but well, urban legends and placebo effects are "solid"...
Yeah some lines do nothing , and I will clean up my build.prop but I'm keeping a few lines , like fling velocities, power collapse, nobootanimation.
And yeah I know what you mean about them being outdated, had those exact lines since 4.0.3 on my vzw gnex especially then I noticed big differences in over all performance. Whether they apply now or not, just got used to it I guess.
Revised build.prop :
debug.sf.nobootanimation=1
windowsmgr.max_events_per_sec=300
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
ro.ril.fast.dormancy.rule=0
ro.max.fling_velocity=30000
ro.min.fling_velocity=20000
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.config.nocheckin=0
ro.mot.eri.losalert.delay=1000
Edit: reusing the quick power on line
Without it carbon booted in 20.3 seconds
With it carbon booted in 18seconds.
Will see if hibernate line has any effect. Or the sf.bootcomplete line (which is supposed to show lock faster) Little to no difference is still a difference after all !
My Nexus 5 boots in 10 seconds without any build.prop modifications
Hi all,
some of you know me from the other OnePlus (One and Two) or Samsung devices areas, where I provide my kernels already for more than two years to OnePlus One, OnePlus Two, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
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 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 !!
Important notes
]When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Make sure you flash the correct kernel version, depending on whether you really use Oxygen OS or a different OS !!!
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.
Saying that, the Boeffla-Sound app in Play Store is not designed to work on the OPX, neither was it developed by me, hence it will never work on the OPX ever. Boeffla-Config is the way to go here !!!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (quite outdated, as it is focused on S3 still).
Click here to learn about using the config app (quite outdated, as it is focused on S3 still).
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.
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 Oxygen OS 3.x.x kernel - Click here
Change log for Oxygen OS 2.x.x kernel - Click here
Features
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.2.29 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove, intelliactive, intellidemand, intellimm, wheatley, smartmax, smartmax_eps, slim, intellimm, pegasusq, nightmare, lionheart, impulse, ondemandplus, yankactive
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)
Notification LED control (fading, speed, brightness)
Boeffla-Sound engine (Headphones volume configurable currently)
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency and duration configurable, touch boost switch
CPU Overclocking up to 2.54 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support with fixed simple_ondemand0
Show GPU frequency usage per frequency in Boeffla-Config
KCAL color control driver
Swipe2wake gestures
Swipe2sleep gestures
Haptic feedback control
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
Kernel logger (dmesg) configurable
Charge rates for AC charger and USB 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, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
exFat opensource support
NTFS support (module) - read-only
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Multiple additional TCP congestion algorithms available
Swap supported
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 (no min cpu frequency reset, use Boeffla-Config to configure min frequencies only)
Integrated full busybox 1.24.2 (own compilation)
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)
Kexec hardboot patch for multirom usage (not supported, not fully working)
Google gcc 4.8 toolchain used for best stability
Always using latest Oxygen OS Initramfs
Always based on latest Oxygen OS kernel sources (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8974)
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 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
f2fs - it is known to cause various issues and compatibility problems
custom hotplugging algorithms
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 correct kernel depending on whether you are using Oxygen OS or another 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.2.29 or higher for the OnePlus X 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
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* 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:
http://kernel.boeffla.de/oneplusx/boeffla-kernel-oos/oos3xx/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
Great to have you here
Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!
Naman Bhalla said:
Welcome Andi !!! Gonna flash your kernel as soon as I get my OPX .... Will make profiles for it too
Welcome again !!!
Click to expand...
Click to collapse
Hehe, nice. I see you everywhere, isn't it?
Andi
sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance
Thanks a ton. Is CM support planned?
ihs0201 said:
sorry if i sound like a noob but if i have bluspark kernel already flashed, can i just flash this ontop of it? or do i have to restore a backup (of the opx before i flashed bluspark) and then flash this kernel? thanks in advance
Click to expand...
Click to collapse
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Lord Boeffla said:
Hehe, nice. I see you everywhere, isn't it?
Andi
Click to expand...
Click to collapse
hehe !! I try to help the community as much as possible...
---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------
RJDTWO said:
Thanks a ton. Is CM support planned?
Click to expand...
Click to collapse
I don't wanna post on behalf of Andi... But if you have been following Andi , he usually builds for CM once official builds roll out with everything working... For now, there is no official build, though almost everything is working now...
But Boeffla is in initial phase of development for OPX so I feel lord will focus more on Oos...
In short, don't expect a CM version till official nightlies start.
Naman Bhalla said:
You can flash on top of it as Boeffla kernel works on a different principle (Sorry.. I forgot what it is called... LOL... Maybe Andi can tell) .... But yeah, if issues come, flash stock and then the Boeffla (shouldn't happen though )
#HappyFlashing
Click to expand...
Click to collapse
Thanks for the quick reply
Nice to see boeffla kernel here. Was waiting for this after seeing a thread on oneplus forum. Is there a version for cm12/13 as well?
Edit: Never mind
Finally, I can't wait to flash it. You're the best, Andi, I'm proud I can say I designed your avatar, hahaha.
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp
Naman Bhalla said:
Which recovery did you use ? As can clearly be seen, this issue is from Updater-script .... So either you can delete that line from the script or best is to use another twrp
Click to expand...
Click to collapse
it is version twrp v.2.8.7.0, but i will try and update and then get back to you
ihs0201 said:
well i tried to install, and it gave me the error : your device is onyx. this zip is for ONE
i did install this zip: boeffla-kernel-4.0-beta1-OOS2xx-OnePlusX.recovery.zip
can anyone help/has the same problem
Click to expand...
Click to collapse
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.
dagger said:
You downloaded the wrong kernel ( you downloaded the OnePlus one variant) so don't flash it as it might brick your device.
Scroll a bit more down in the Web page till you find OnePlus X.
P.S. The website can be a bit confusing for newer members, so here you go.
http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx_download/Test/
Cheers.
Click to expand...
Click to collapse
no it was the opx variant, as the filename showed opx when i flashed it. thanks anyway, and yeah the website is a bit jumbled
but the problem was an old twrp version. updated it and the kernel flashed no problem . BTW i like ur icon pack, might try it
Can someone explain the difference between this kernel and blu-spark to us common people?
What do you take into consideration when deciding which one to use?
Hi Andi,
Good to have Boeffla kernel again!
The real deal just came to opx. Thanks, bro! Hope opx gets official cm so you can provide support for cm too, as I cannot live without cm.
Hey, it's been a while since my last (and failed) release, so let's see if you can help me on this one.
As you might have guessed, I have compiled our latest kernel, and this is my own version!
Right now, people have reported battery life improvements, I'd love to hear what you think!
Changelog
Code:
V2.0
* Enabled some CPU governors.
V2.1
* Updated KSM with uKSM.
* Added Thunderplug hotplugging driver.
* Added PMC and Smartmax CPU governors.
* Added Init.d support. (Make sure the file has the proper permissions)
V2.2
* Updated GPU drivers to be compatible with EMUI 4.1.
* Added Intelliplug hotplugging driver.
* Improved GPU performance.
Downloads
V2.2 (New): https://github.com/XePeleato/ALE-L21_ESAL/releases/tag/v2.2
Instructions
Download the .zip
Flash from recovery
Done!
You can get the source here: https://github.com/XePeleato/ALE-L21_ESAL/tree/v2?files=1 (v2 branch)
Guide
I am going to try to help you to decide what settings you should apply
First of all, I recommend to install Kernel Adiutor.
If you prefer battery life:
Start Kernel Adiutor:
Go to CPU in the drop-down menu and set as governors PMC or SmartmaxThen go to CPU hotplug and don't enable many cores, since more online cores means more power used. You can also set the Endurance level to Quad-core
If you prefer performance:
Start Kernel Adiutor:
Go to CPU in the drop-down menu and set as governors performance (will set the CPUs to their max frequency)/ondemand/interactiveThen go to CPU hotplug and make sure to lower the load threshold, having a low load threshold will make your phone use more cores (if you experience lag while playing, maybe it's set too low, so use a wise value, do your testing.)
To conclude, I just mentioned where the settings are and some example values, if you love to play games you won't use the same settings as someone that just likes to read emails and use Google Chrome, find the settings you are comfortable with, and don't forget to set Apply on boot!
Now some screenshots of AnTuTu and 3DMark with Performance governor and Esalv2.1:
http://imgur.com/a/iRDpD
As you can see, even 3DMark detects that my score is higher than the average, try to beat that with stock kernel!
I hope you enjoy it, and please, I'd love to hear your suggestions!
just a quick question if you dont mind : any way to flash it via twrp ? so in case that something goes wrong i can easily restore the old one with a backup .
Firicel69 said:
just a quick question if you dont mind : any way to flash it via twrp ? so in case that something goes wrong i can easily restore the old one with a backup .
Click to expand...
Click to collapse
I'll upload a flashable zip, but it shouldn't be a problem, if you take a backup of your Boot partition and restore it, it will overwrite the kernel.
thanks! i will try it and see how it goes.
Sim gets detected but stucks at the point of unlocking it.
waiting for comments on the kernel
VenityZ said:
Sim gets detected but stucks at the point of unlocking it.
Click to expand...
Click to collapse
I've noticed it too, it finally unlocks in my end, can you please check if it gets unlocked?
XePeleato
Tnx bro)
Great job.
Finally , I have the full root, before either he could not edit the folder systems
XePeleato said:
I've noticed it too, it finally unlocks in my end, can you please check if it gets unlocked?
Click to expand...
Click to collapse
I kept the screen active and it worked after 40s
Basic stuff works , so god for daily usage I guess. Is rep on github up to date of this kernel because I compiled it myself and nothing worked. I either think my toolchain is the problem.
---------- Post added at 03:18 PM ---------- Previous post was at 03:00 PM ----------
Also the governors do work , I don't know if all do but theres a noticeable performance change when chaging it. Over/Undercloking still doesnt work , but its not the kernels problem. The power genie of emui controls it.
VenityZ said:
I kept the screen active and it worked after 40s
Basic stuff works , so god for daily usage I guess. Is rep on github up to date of this kernel because I compiled it myself and nothing worked. I either think my toolchain is the problem.
Click to expand...
Click to collapse
Yes it is, the v2 branch, you'll need to edit build.sh to point it to your toolchain.
XePeleato said:
Yes it is, the v2 branch, you'll need to edit build.sh to point it to your toolchain.
Click to expand...
Click to collapse
Thanks I compiled the "v1" branche....
Wi-Fi, Bluetooth, NFC works.
I will test mobile data, GPS tomorrow.
"Bug": SIM unlock takes a lot more time than stock kernel.
Great work! May I ask what features are you going to add into? OTG maybe?
Anyway: Great! Keep it up!
EDIT:
How can I change governor? I'm looking for extra governos (PMC, Smartmax) in Kernel Auditor but I can't find them
LG*L70 said:
Wi-Fi, Bluetooth, NFC works.
I will test mobile data, GPS tomorrow.
"Bug": SIM unlock takes a lot more time than stock kernel.
Great work! May I ask what features are you going to add into? OTG maybe?
Anyway: Great! Keep it up!
EDIT:
How can I change governor? I'm looking for extra governos (PMC, Smartmax) in Kernel Auditor but I can't find them
Click to expand...
Click to collapse
Hi, can you find ondemand, interactive, powersave...? OTG is enabled, the problem is at the rom.
XePeleato said:
Hi, can you find ondemand, interactive, powersave...? OTG is enabled, the problem is at the rom.
Click to expand...
Click to collapse
Hi,
Yes, I can.
Thank you for the heads up about OTG, I didn't know that
XePeleato said:
I'll upload a flashable zip, but it shouldn't be a problem, if you take a backup of your Boot partition and restore it, it will overwrite the kernel.
Click to expand...
Click to collapse
I'd also appreciate flashable zip please
TheATHEiST said:
I'd also appreciate flashable zip please
Click to expand...
Click to collapse
Done! Check the OP, I added the link there.
XePeleato said:
Done! Check the OP, I added the link there.
Click to expand...
Click to collapse
Thanks :good:
Init.d support would be really nice xP
VenityZ said:
Init.d support would be really nice xP
Click to expand...
Click to collapse
It will be added on the next release!
Working fine for me. The Unlocking the SIM takes about 40 seconds. Governor's work. Thanks man, keep up the good work.
Thunderoar Kernel For SM-T113
(Tab 3 Lite 7.0 Wifi)
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, corrupted partition, nuclear disasters
* Please do some research before using this mod!
* YOU are choosing to make these modifications,
* If you point the finger at me for messing up your device, I will laugh at you.
Features:
Overclocked
Deferred Timer for KSM
USB Fast Charge
Arch Power
Frandom
Powersuspend for battery life/saving
QuickWakeup for battery life/saving
Dynamic Sync Control
Fsync control on/off
Voltage Tweak
NVS hibernate driver
Multicore Power Saving
Schedule workqueues on awake CPUs to save power
CPU Boost
Adaptive Low Memory Killer
Software CRC control toggle
Gentle Fair Sleepers toggle
and so on...
CPU Hotplug:
AutoSMP
Added CPU governors:
Sprdemand
Conservative
Ondemand
Userspace
Powersave
Interactive
Performance
and so on...
Planned Update
-nothing i guess (but u can suggest somethin to me that possible)
Bugs(s)
-No MORE BUG!
Custom kernel Installation:
Download the kernel from here
Choose the tar.md5 if flashing from odin
Choose the zip files if flashing from custom recovery
Choose the latest version
Odin Instruction:
Open any version of odin
Choose your tar.md5 file from AP Tab
And Start
Custom Recovery Instruction:
Reboot into recovery if usin zip files (recommended to make a nandroid)
Flash the kernel zip
Reboot and enjoy!
Stock kernel Installation:
Download the stock kernel from here
Enter recovery mode, choose install, choose install image,
and then go to the directory of your downloaded stock kernel
choose it and then check mark on the boot circle.
And then flash it
Notes:
20/12/2107
Kernel Update!!
Thunderoar-Kernel 5.0 Codenamed "Angel Beats!"
Fix all issues regarding MTP not working
and random reboot, is this a comeback? xD, i don't know xD
It appears that my kernel uses a lot more memory than i expected,
Possibily some problem with memory patch in the kernel source
The workaround for this problem is you have to increase your disksize
In the kernel adiutor, if it stays at 300mb, it will not enough and cause a problem
Which is stuck or complete crash of device. Recommended size is 500mb or more if
you encountered it again and set swappiness into 60
XDAevDB Information
Thunderoar Kernel, Kernel for the Samsung Galaxy Tab 3 7.0
Contributors
@Thunderoar
Credits:
@Osm0sis-For the Anykernel2
@stathis95194-For the stock kernel
Github:
Kernel source
Version Information
Status: Stable
Current Stable Version: Angel Beats! || 5.0
Stable Release Date: 2017-12-24
Created 2016-12-26
Last Updated 2017-12-24
Press the "Thanks" button if you appreciate my work or if i helped you
Changelog:
V5.0 Codenamed "Angel Beats!" (2017-12-24)
+Kernel upstream version 3.10.17->3.10.108
+Gpu update
+Fix MTP
+CPU Frequency change 200MHz upto 1.5GHz
+Entropy Update
+Multicore Power Saving
+CPU Boost
+Arch Power
+Power Suspend
+Quickwakeup
+Read-ahead set to 512kB
+Adaptive Low Memory Killer
+Software CRC control
+Gentle Fair Sleepers
+Fsync On/Off
+Built from scratch and fixed random reboot
+Dynamic Fsync
-Removed Obselete Cpu Governor
-Removed Obselete I/O Scheduler
-Removed UKSM and use normal KSM
V4.1.1 update (2017-7-5)
+Fix some devices not booting
+New CPU Hotplug: AutoSMP
V4.1 update (2017-7-3)
+Just another update for stability
V4.0 update (2017-7-3)
+No more Reboot or similar effect - Tested
+Linux kernel downgraded into 3.10.32 temporarily because rebuilt from scratch
+Auto cpu boost on input without predefined frequency
+UKSM(Ultra Kernel Samepage Merging)
+LZ4 Z-RAM - Faster Memory
+Asynchronous Fsync -Faster storage management
+USB Fast Charge are back
-Removed cpu governor: OndemandX, Zzmoove, Scary *Temporary*
V3.4 update (2017-6-22)
+The most stable kernel that i've ever built
+Linux Kernel 3.10.44
+No more frequent reboot or similar effect
+Bug fixes
V3.3 update (2017-6-17)
+Linux Kernel 3.10.40
+Properly fix the bug that mentioned on the v3.2 update and lower the risk of instability
+A bunch of cpu governor
*Hotplug
*Lionheart
*Reworked version of intelliactive
*Ondemandplus
*OndemandX
*Hyper
*Zzmoove
*Nightmare
*Wheatley
*Badass
*Scary
*All of them are properly functioning and tuned for compatibility
and if you want the hotplug features, use the hotplug governor provided
+Bug Fixes
-Adaptive cpu governor removed parmanently
V3.2 update (2017-6-8)
+Update: Linux Kernel 3.10.37
+Update: Using the latest Anykernel2 zip
+Update: Minimum frequency change into 254MHz and also voltage change for nice battery lasting
+Update: cpu-boost set to 765MHz and running for 3 seconds when touch detected
+Update: Set CFQ as default scheduler
+Fix: Bug that cause long running app either in the background or foreground to freeze/lagging/reboot etc.
+Fix: Bug that cause the device to reboot randomly
+Fix: Bug that cause the graphic being not working/properly lagging or some sort
+Fix: Bug that cause the device to reboot or freeze when standby
+Fix: Bug that causing the kernel to working improperly/lagging/rebooting/unstable after a while
+Bug fixes
V3.1 update (2017-5-7)
+CPU Frequency minimum change -> 384MHz
+Fix Frequency bug stuck at 768MHz
+Faster charging
V3.0 update (2017-5-7)
+Kernel version updated from 3.10.22 - > 3.10.26
+Using updated Anykernel zip
+Frequency: changed into 1600Mhz and minimum is 386Mhz
+GPU: function updated
+Deferred Timer working as it is
+LZ4 compression
+"Schedule workqueues on awake CPUs to save power" are back
+Remove conflict between Samsung touch booster and my CPU-Boost so you can actually set the amount you want
for boost
+Sync threshold for cpu-boost are not set
+I/O scheduler default to deadline
+Fsync are on by default
+TCP Congestion Algorithm set default to Westwood which is the fastest for network usage
+Additional TCP Congestion Algorithm are added
+Additional tweak to make the kernel faster
+Camera Fix!!!
+MTP Function (unconfirmed)
+A whole lot of bug fixes
-sprdemand governor
-Fastcharge (for now)
V2.8 update (2017-1-31)
+Frequency: changed into 1660Mhz and minimum is 580Mhz
+Cpu-boost: defined stable values
+Less OS tearing
+Fastcharge updated
+Audio functionality improved
+Voltage: change for low-power use
+Many bug fixes
+Selinux: updated
-Automatic Cpu Hotplug: removed for better stability but with little to no battery drainage but you still can deactivate the cores through Kernel Adiutor
-Sprdemand: removed
V2.6.1-MR1 update (2017-1-1)
*Note:This is maintenance release therefore some features may temporarily unavailable
Add: cpu-boost currently disabled but provided as an option
Add: voltage change
Add: frequency change from 386Mhz to 1600Mhz for more stable
FIx: serious bug that causing switching off mobile data make it freeze/crash
Fix: bug that causing the device freezing/crash throughout all my kernel update release
V2.6 (2016/12/27)
+Initial release
After flashing all apps start to crash.
Jimbus369 said:
After flashing all apps start to crash.
Click to expand...
Click to collapse
Quick note on the crashing apps.
T113XXU0APE2: Does not have this issue
T113XXU0APH5: When I use this ROM, than indeed everything goes bananas after booting up the tablet.
Before flashing the kernel I advice to disable all unnecessary services and with that I mean everything with Samsung in the name and also all of the google apps you don't use. It seems that com.google.process.gapps is causing a crash chain reaction so do disable this services as first. I'm using lucky Patcher for disabling services and for those who are unfamiliar with this my advice is to not uninstall an app but first disable it and later when you are satisfied you than may safely uninstall the unwanted app/service.
Bugs
Camera doesn't working
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Jimbus369 said:
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Click to expand...
Click to collapse
All the app?
Thunderoar said:
All the app?
Click to expand...
Click to collapse
Yes, all apps.
This is extremely exciting and can't wait to try it out!
Build T113XXU0APA5
Will let you know how it goes....
Wanted to ask (not that it's a huge deal) is there init.d support in this kernel?
If so do I need to do anything special to enable it?
Going to go ahead with it anyway and see what happens!
Thunderoar said:
* If you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Better start laughing, 'cause my finger's pointing directly at you! And also twitching slightly out of frustration!
....Nah, it's all good. :highfive: I screwed things up all on my own by getting flash-happy. :crying:
On the plus side: It worked GREAT! :highfive: Thanks so much for putting this together for us tiny-tab users, you did a great job.
Not only did Byron (my T113's name) run smoother and faster than I've seen yet (yay!), but suddenly Mounts2SD had no issues whatsoever. Up till now it's been a supreme struggle to get /sd-ext to mount properly, to be used properly, etc. etc. - but after flashing this kernel, on first boot boom, everything just worked. Without changing anything I'd already done.
Should have just left it the way it was, eh? But noooo, I had to go "try something else" and made a stupid mistake somewhere, and now no combination of ROM / kernel / nandroid backup (meticulously organized and annotated) is booting up. I even lost TWRP for a little bit.... As penance for my sin of wanting "more", I've gotta dig up Odin, go back to stock, and start from scratch.
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Not going to wait for an answer/s before moving ahead, but any response here will serve as documentation for myself and others in future!
(How don't we have a smiley for "pointing finger"? There's at least TWO in Unicode but I'm too lazy to go get it right now....)
PushyPhoenix said:
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
Click to expand...
Click to collapse
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
PushyPhoenix said:
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
The kernel is in the md5 file or in the zip file, named boot.img
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Click to expand...
Click to collapse
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
By the way, great to see development on this tablet. I am going to be testing this kernel in a personal build and see if I can squeeze as much out of it as I can get. So thank you dev.. Awesome work and greatly appreciated. : )
glockman4519 said:
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
Click to expand...
Click to collapse
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
Thunderoar said:
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
Click to expand...
Click to collapse
So I've run into a bit of a problem. Tried outFyrestone ROM and i love it, but it's based on PH5 firmware and doesn't play nice with your wonderful kernel. Which means my sd-ext is broken...
I know you're very busy (and I haven't a clue what kind of work is required), but wondered if you know when we can expect to see an update?
Thanks so much for all your hard work!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
I get it, it clutters things s bit. But I am one who like an organized setup anyways so adding more folders is common for me. It may not be everyone's cup of tea so to speak.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
It works for me and above all, works for TWRP.
Click to expand...
Click to collapse
First of all, sincere thanks for replying; this advice may help others as well
glockman4519 said:
PushyPhoenix said:
Ugh, adding another folder to the folder full of folders on my computer frightens me.
Click to expand...
Click to collapse
I get it, it clutters things s bit.
Click to expand...
Click to collapse
My apologies for not being more clear on what exactly 'frightens' me about this idea. There have been times when I've backed things up this way and couldn't get into them again because of the number of characters in the path and file name - they were just too long!
Mind you, this was tens of years ago on WinXP and it never occurred to me to try finding a fix.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
Click to expand...
Click to collapse
That's a fantastic system, very similar to the one I'm now using, and will add new folders as you've suggested. Hopefully reading this will benefit those who are new to this world so they don't wind up with folders full of mysterious files and untagged backups for various devices, that made perfect sense at the time. (Like the one folder for my first few devices, which now looks like gobbledygook....)
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Topic:
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Is there any lollipop/marsmallow/Nougat ä ROM that works in my T113 (Samsung tab 3 lite "7)? This device runs natively Android 4.4.4, but I Really need Android 5 or higher! Lollipop would do just fine.. I took a look at most popular custom roms to this device, but most were 4.x.x.. And nothing for t113! And all of those were to T221 or so, in the list they're were few supporting T110/T111, but now T113. Does those work in this T113? Isn't it just same device?
Please tell me if you have any idea of rom with Android 5 or newer that works in this T113!
It would be awesome to have Lollipop-Slimrom or Resurrection remix with Android 5/6/7..
Even Stock Lollipop would be adequate, android 4 lacks important features...
There's many roms to this device, but they are for T2XX or T110/T111... Does any of those run in t113?
I have already rooted this tablet and installed TWRP.
Thank you so much for help in advance! Any information that gets me closer to have Lollipop or newer is very very much appreciated!
Sincerely,
tatu-o aka. mlc
PushyPhoenix;[email protected] said:
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
1.Yep
2.The stock kernel is in the md5 file which is boot.img, the md5 file I mentioned is in the stock rom
I guess I double answered this question, my bad :silly:
PushyPhoenix said:
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Click to expand...
Click to collapse
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Thunderoar said:
I guess I double answered this question, my bad :silly:
Click to expand...
Click to collapse
Hahaa, thought it sounded familiar! No problem, better to get the answer multiple times than not get an answer at all.
---------- Post added 01-29-2017 at 12:01 AM ---------- Previous post was 01-28-2017 at 11:59 PM ----------
Thunderoar said:
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Click to expand...
Click to collapse
Good to know! I've had so many issues over the years, with spaces in filenames, that any renames for files like this get an underscore or dash instead of spaces. Helps in lots of other ways, too.
Hello!
I want to introduce my first custom kernel for the Essential PH-1. This is based of several sources, I cherry-picked commits to make improvements to the stock LOS kernel. I'm not a developer, but i really like to port stuff over .
Kernel is suitable for AOSP based ROMS such as RR/AICP/CARBON/LOS etc... If you want to request for specific features, let me know and i'll do my best to bring them over.
Special Features:
Updated to lastest LOS Stock Kernel
Added a few governors like: cultivation / impulse
added a few IO Schedulers: Maple
Kcal Color Control driver
USB Fast Charge - pending will be added in R2
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
a little Overclock - will be added in R2
Motorola Quickwake - Will be added in R2
and manny other small fixes (you can check the commits in the sources)
Download
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
Latest Release: SMF-Kernel R2
Known issues:
05.17.2018 - CPU Freq don't always stick, known issue caused by other drivers. Phone will eventually set your frequencies, dont' panic.
Installation:
Obviouly you have a Unlocked Bootloader since you're running a custom rom (make sure to never lock your bootloader in this state)
Boot into Bootloader (adb reboot Bootloader)
If you want to root flash the "Magisk" version of the kernel, it's been prerooted with the latest Magisk Beta available.
Code:
fastboot flash boot SMF-Kernel-R1-Magisk.img
reboot
If you want to manually root, first flash twrp, then from twrp flash the 'non magisk' version and after that flash the magisk zip.
Special Thanks to:
jcadduono
franciscofranco
bedalus
lord_boeffla
flar2
sultanxda
...and many others from whom i cherry pick commits... Sorry if I forgot to mention anyone!
XDA:DevDB Information
SMF-KERNEL, Kernel for the Essential Phone
Contributors
jimbo77
Source Code: https://github.com/Jimbo77/android_kernel_essential_msm8998
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R1
Stable Release Date: 2018-05-17
Created 2018-05-17
Last Updated 2018-05-17
Changelog 05.23.2018
Enabled Motorola QuickWake Driver - This will enable system to do checks or syncs without fully resuming the device, main objective is battery life.
Enabled Dynamic Sync Control by default
OverClock
USB Fast Charge to up 900ma (Original is 500ma)
Disabled Gentle Fair Sleepers
Enabled Boefla Wakelocks - Check the ammount of wakelocks you can block now!
Enabled Wireguard
Enabled several TCP Options - "Westwood" is enabled by default
Min/Max Brightness options is now configurable as well, to avoid the screen go too dim or to bright.
Somehow camera has been fixed! haha
Changelogs 05.17.218
Updated to lastest LOS Stock Kernel
Added a few governors like: cultivation / impulse
added a few IO Schedulers: Maple
Kcal Color Control driver
SafetyNet Patch (Bypass bootloader unlocked check)
Dynamic Fsync control
and manny other small fixes (you can check the commits in the sources)
Reserved
Looks awesome! I'll give it a try soon!
(For anyone wondering about overclocking the CPU, he committed some changes to the github that would apply this and it should appear in the next revision of the kernel.)
Just installed and so far it's buttery smooth.
WARpig5 said:
Just installed and so far it's buttery smooth.
Click to expand...
Click to collapse
I'm glad is running fine for you!
Good stuff, thanks for this! Could you tell me a little more about cultivation? I can't seem to find much information online about it
Also a request, if possible vibration level control would be super appreciated
pantherking said:
Good stuff, thanks for this! Could you tell me a little more about cultivation? I can't seem to find much information online about it
Also a request, if possible vibration level control would be super appreciated
Click to expand...
Click to collapse
I found Cultivation to be really great in terms of perfornance. It's a little bit agressive with the CPU so you get buttery smooth experience with Screen On but it may cost a few % on battery at the end of the day. The good thing is that it has specific tunables and you can set a low cpu freq for when the screen is off.
Specific details from its developer:
-based off of caf 4.4 commits
-uses per-pcu timers
-use state_notifier for screen off timer
option to set different timer rate when screen off
-improrted fastlane with threshold from blu_active
In regards of vibration control. It should be there. I'm using EX Kernel Manager and i can see the vibration option under "Miscellaneous"
jimbo77 said:
I'm glad is running fine for you!
Click to expand...
Click to collapse
Thanks for this. It's running amazing so far. Performance has been great and I'll see how battery life is, but so far it's great.
I can't wait for further updates. I really wanna see what Moto quickwake is haha
jimbo77 said:
In regards of vibration control. It should be there. I'm using EX Kernel Manager and i can see the vibration option under "Miscellaneous"
Click to expand...
Click to collapse
Thanks for the info on cultivation, I don't mind trading some battery life for butter so I'm using it now
For the vibration control, it doesn't actually work/stick. I've tried kernel auditor and EX Kernel Manager. To be fair, so far it has only worked on LOS and I think invisiblek may have rewritten the stock controller or something so no worries if it isn't a high priority haha
pantherking said:
Thanks for the info on cultivation, I don't mind trading some battery life for butter so I'm using it now
For the vibration control, it doesn't actually work/stick. I've tried kernel auditor and EX Kernel Manager. To be fair, so far it has only worked on LOS and I think invisiblek may have rewritten the stock controller or something so no worries if it isn't a high priority haha
Click to expand...
Click to collapse
I'll take a look at the latest commits but I've used the latest los kernel base so I'm not sure why is not sticking maybe it needs rom support too (not sure honestly) hahaha
I've been testing R2 since yesterday. Will update after y he weekend!
Just out of curiosity, was anything involving the camera done to this kernel? I am now able to record videos without the bug, on any of the affected ROMs, with this kernel.
stompysan said:
Just out of curiosity, was anything involving the camera done to this kernel? I am now able to record videos without the bug, on any of the affected ROMs, with this kernel.
Click to expand...
Click to collapse
Nothing related to camera. Are you sure it works with no issues?
What roms have you tested?
jimbo77 said:
Nothing related to camera. Are you sure it works with no issues?
What roms have you tested?
Click to expand...
Click to collapse
So far, AICP and LOS, both with Essential camera app and GCAM port, HD and 4K, 30 and 60 fps where applicable. Issues presented before flashing very consistently, and so far I have been unable to replicate after flashing this kernel.
stompysan said:
So far, AICP and LOS, both with Essential camera app and GCAM port, HD and 4K, 30 and 60 fps where applicable. Issues presented before flashing very consistently, and so far I have been unable to replicate after flashing this kernel.
Click to expand...
Click to collapse
Sp you were right. Honestly don't know what happened but I installed the latest RR (clean install) put R2 on top of it and bam recording works as you mentioned lol..
I guess it was a lucky strike!
after flashing the kernel with magisk, stuck on "AICP is starting"
is this normal?
update: the phone works but no magisk (pre root) after flashing the kernel.....
sinkoo1979 said:
after flashing the kernel with magisk, stuck on "AICP is starting"
is this normal?
update: the phone works but no magisk (pre root) after flashing the kernel.....
Click to expand...
Click to collapse
Hey!
Have you booted once and setup everything before flashing the prerooted image?
I've had that error but having all set and then flashing the image will get me rooted. Try to see if you can find magisk manager in the apps list from the settings if you do, reboot and there will be magisk
Double post... Sorry
jimbo77 said:
Hey!
Have you booted once and setup everything before flashing the prerooted image?
I've had that error but having all set and then flashing the image will get me rooted. Try to see if you can find magisk manager in the apps list from the settings if you do, reboot and there will be magisk
Click to expand...
Click to collapse
Thank you for the reply.
the phone was running AICP and I wanted root so I flash the kernel. I can't find the magisk manager or in the settings about magisk. I guess you have to clean install from the beginning to get the root. Thank you for the Kernel
sinkoo1979 said:
Thank you for the reply.
the phone was running AICP and I wanted root so I flash the kernel. I can't find the magisk manager or in the settings about magisk. I guess you have to clean install from the beginning to get the root. Thank you for the Kernel
Click to expand...
Click to collapse
Shouldn't. If you flashed the prerooted magisk image try downloading the magisk manager app manually from xda and see if magisk works