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.
Related
XS ICS
The original 3.0 custom kernel for the Incredible S
Disclaimer: Please read before continuing
This is a 3.0.x kernel, which means it is for ICS ROM's only.
You use this kernel and it's available settings at your own risk. I accept no responsibility for your phone, or anything that happens to it while using the feature. Although it has the ability to overclock to 2.0GHz, this may shorten the life of your device.
Click to expand...
Click to collapse
The aim of this kernel is to be the most feature rich kernel available for the Incredible S. The kernel is the engine of your phone, and I want to include support for everything! If there is something you need and it isn't here, let me know and I will do my best to add it. XDA is a community, and lots of the work in this kernel has been discovered / and created by a wide range of people, all of whom this would not be possible. It is pretty impossible to name all of the people to thank, but know this is the result of a whole community, and my gratitude goes out to everyone who has contributed to this site!
Sources available in my github
Latest Version: v2.2 Attached To Post
Released 29/08/12
Features
- Based of HTC Sources, patched all the way up to 3.0.42
- CPU Table The CPU table has been optimised to include the following freqs:
----------245MHz, 368MHz, 768MHz, 806MHz, 1024MHz, 1.2GHz, 1.4GHz, 1.5GHz, 1.7GHz, 1.8GHz, 1.9GHz & 2.0GHz
- Available CPU Governors Smartass v2, Lionheart, Conservative, Performance, On demand, lulzactive, scary, intellidemand, LagFree, Lazy & SavagedZen
- Available CPU Schedulers Simple I/O, Deadline, CFQ, Noop, BFQ & V(R)
- Available File Systems EXT3, EXT4, CIFS, NTFS (with UTF-8)
- Default Settings On Demand governor @ 245-1024MHz, Simple I/O scheduler
- Improved tolerance for low strength Wi-Fi
- Sweep2Wake
- DeepSleep enabled
- VDD Interface
Known Bugs
Please report any bugs you find, and I will endeavour to fix them
- There are several issues when using with IceColdSandwich, the camera will be very glitchy and the keyboard will be too large to fit on-screen
Planned Features
If it's in this list, please don't ask for it, I am aware and will be adding it when I can
- USB OTG Support
- USB Host
- 2-Way Call Recording
Don't forget to thanks this post if you like my work! Donations are not requested or expected, but are greatly appreciated
Click to expand...
Click to collapse
Changelog
29/08/12 - XS ICS v2.2
- Patched up to 3.0.42 (thanks to cjoliver)
- VDD Interface added
- Added 6 new governors: lulzactive, scary, intellidemand, LagFree, Lazy & SavagedZen
29/08/12 - XS ICS v2.1
The only way is up!
- Sweep2Wake fixed and fully implemented!
- USB OTG implemented (needs testing)
- Force unknown cable to be treated as A/C (should help with in-car chargers)
- Wi-Fi module issues should now be resolved
28/08/202 - XS ICS v2.0
Things can only get better...
- Switched to Koush's AnyKernel for maximum ROM compatibility (thanks to tpbklake for the suggestion)
- Patched up to 3.0.41 (big thanks to amidabuddha and mdeejay!)
- Added sweep2wake disabled by default, see below to enable, needs testing (thanks to show-p1984 for the functionality and coolexe for the patch to Amtel)
- Add BFQ v4 and V(R) I/O Schedulers (SIO still default)
- Wi-Fi PM = Fast
- Improved tolerance for low strength Wi-Fi
- Added extra values to CPU table (courtesy of amidabuddha)
24/08/202 - XS ICS v1.0
We're back baby!
- Inital Release
Click to expand...
Click to collapse
Instructions for S-OFF Users
Simply flash XS-ICSvX.X.zip in your favourite recovery!
Instructions for manual flashing (HTCDev.com unlocked S-ON Users)
Thanks to MrToastbrot for instructions
Step 1: Download the XS-Kernel.zip, then open the Zip on your computer and extract the file mkbootimg.sh in "kernel"
Step 2: Open mkbootimg.sh in a texteditor like notepad++ or notepad, then edit the following in line 3:
Code:
output /tmp/newboot.img
to
Code:
output /sdcard/newboot.img
Step 3: Save your edited file and place it back in your zip, copy your modified zip to your phone-sdcard and install it in the recovery. Then reboot your phone and connect it to pc and take the newboot.img from the root of the sdcard.
Step 4: Now reboot your phone into bootloader and flash it via fastboot flash boot newboot.img
Step 5: Once you phone has booted, mount the system as r/w using something like ES file explorer or Root explorer, then type the following:
Code:
adb push bcm4329.ko /system/lib/modules
Set permissions to rw-r--r--, reboot and enjoy!
Sweep2Wake: Q&A
Q: How do I disable / enable the feature?
A: Two options
Change the value in the file /sys/android_touch/sweep2wake to either 0 for disabled, 1 for enabled and 2 for enabled with backlight. This will be reset upon rebooting.
If your ROM supports init.d scripts, then flash the zip to enable or disable, this will stick over a reboot.
Q: It keeps taking screenshots when I lock the screen!?
A: This is due to an incompatibility with this feature and the native screenshot in Sense. TO stop the screen shots, you need to edit your build.prop and change the property ro.htc.framework.screencapture to false, and then reboot.
l0st.prophet said:
- 2-Way Recording
Click to expand...
Click to collapse
I'm using the miui v4 with nik's kernel and that function already work!
I'm wrong assuming it's already coded?
BTW good work!
Nice post, fast work. I'll have a play first chance I get. Thank you.
Nice. Downloading right now. Making a backup right now since I was thinking of flashing this new Google Now ZIP as well.
Also does this mean we can get CWM 6.0+? IIRC, one of the requisites for it was a ICS kernel to be able to compile it. Correct me if I'm wrong.
Which ROMs is it support?
MIUI will work whit this kernel?
Sent from my Incredible S using xda app-developers app
I have an S-OFF Vivo, so how do I flash this? Do I just install the zip from CWM?
I'm currently on IceColdSandwich, so what's the difference between the kernel used in that and this kernel?
Forgive my noobness but how is the file size only 100kb?
I have only test on MIUI v4, but it should work with any ROM, I would like some feedback if there are any ROM's it doesn't work with.
There is now a flashable zip on the first post, I made a proper schoolboy error when I first uploaded it, that is now fixed
l0st.prophet said:
I have only test on MIUI v4, but it should work with any ROM, I would like some feedback if there are any ROM's it doesn't work with.
There is now a flashable zip on the first post, I made a proper schoolboy error when I first uploaded it, that is now fixed
Click to expand...
Click to collapse
Thanks sir, great work!
Sent from my Incredible S using xda app-developers app
TheDareDevil said:
I have an S-OFF Vivo, so how do I flash this? Do I just install the zip from CWM?
I'm currently on IceColdSandwich, so what's the difference between the kernel used in that and this kernel?
Forgive my noobness but how is the file size only 100kb?
Click to expand...
Click to collapse
This is just a new kernel, that is why it is so small.
Did you read the OP and the second post? The instructions can be found there.
TheDareDevil said:
I have an S-OFF Vivo, so how do I flash this? Do I just install the zip from CWM?
I'm currently on IceColdSandwich, so what's the difference between the kernel used in that and this kernel?
Forgive my noobness but how is the file size only 100kb?
Click to expand...
Click to collapse
There is now a proper zip you can flash, check the second post for instructions.
The kernel in Ice Cold Sandwich is a Gingerbread kernel (2.6.x) which was modified to work with ICS (rather awesomely by Kaijura I might add). This kernel is built from the latest 3.0 sources.
Oh sweet! How did you manage to do it so fast?
One last question, none of my data will be lost right?
TheDareDevil said:
Oh sweet! How did you manage to do it so fast?
One last question, none of my data will be lost right?
Click to expand...
Click to collapse
I have been waiting for this since the OTA dropped
No data will be lost, but I would backup in case there is an issue with your install.
l0st.prophet said:
There is now a proper zip you can flash, check the second post for instructions.
The kernel in Ice Cold Sandwich is a Gingerbread kernel (2.6.x) which was modified to work with ICS (rather awesomely by Kaijura I might add). This kernel is built from the latest 3.0 sources.
Click to expand...
Click to collapse
Working smooth like butter on IceColdSandwich 8.4,one change is that my keyboard is larger
Sent from my Incredible S using xda premium
Awesome work!! I'm on miui v4 and Wi-Fi is working great but I ain't getting my mobile data working am I missing something?
I just flashed the zip. And I'm s-off.
Sent from my HTC Incredible S using xda app-developers app
Works great! Thanks a lot!)
Great work man!!!
I think that you can delete 1.7GHz, 1.8GHz, 1.9GHz & 2.0GHz
Because they are unstable
ragzdincs said:
Working smooth like butter on IceColdSandwich 8.4,one change is that my keyboard is larger
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Shouldn't affect anything like that, can you flash back the original boot.img to confim it goes away?
lundberg512 said:
Awesome work!! I'm on miui v4 and Wi-Fi is working great but I ain't getting my mobile data working am I missing something?
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Mobile data works fine for me, again shouldn't be affected by the kernel. I know MIUI has some issue with data anyway, check the thread in general to see how to fix that, but if that doesn't work, let me know.
Alex-stroev said:
Great work man!!!
I think that you can delete 1.7GHz, 1.8GHz, 1.9GHz & 2.0GHz
Because they are unstable
Click to expand...
Click to collapse
Different chips are more resiliant. I used to have one that could sustain 1.8GHz with no problem, but I sent it for repair as the screen got smashed, they sent a replacement and this one can't go over 1.5GHz without crashing instantly, the option is there for anyone who wants it though.
IceColdSandwich 8.3: looks good, only broke camera and rotate buttons, but I expected it
Edit: doesn't work gps and bluetooth, IceColdSandwich either has a lot of hacks, or would need it
Working fine here. Now to see how high of a OC I'm willing to work with hehe.
Introduction
Hello dear developers and android hackers,
On this thread, I will share with you a project I am developing as I am learning kernel programming / hacking. This kernel is based on Sony kernel sources with some enhancements for battery saving and performance.
Click to expand...
Click to collapse
Features
Based on Sony 23.5.A.0.570 kernel sources
Compiled with linaro GCC 4.9.1 toolchain, -O3
Governors : interactive, ondemand, performance, conservative, smartassV2, intellidemand2 and intelliactive.
Fast hotplug
CPU overclock up to 2.8 GHz Thank's to Faux123 and DooMLoRD
Changed GPU frequency table to 27 - 657 MHz Thank's to Myself5
Sony RIC disabled
Undervolt
TWRP recovery included, fota partition support
Breathing notification light thank's to glocklee
Force Fast Charge
KCAL Advanced color control Thank's to savoca
Click to expand...
Click to collapse
Installation instructions
Code:
Use this kernel at you own risk !
I am not responsible for any damage or problem.
Flash the zip via recovery
Reboot
Click to expand...
Click to collapse
Download
Please read FAQ and second post if you have any issue
Recovery flashable zip :
Abricot kernel v8.1.zip
mirror
Kernel Source :
Kernel
Ramdisk
Click to expand...
Click to collapse
Changelog
Abricot kernel v8.1 : 12.05.16
Disable RIC at kernel level (Fixes partition mounting in recovery)
Add KCAL Advanced color control Thank's to savoca
Abricot kernel v8 : 10.05.16
Based on Sony sources 23.5.A.0.570
Updated TWRP to version 3.0.2-0
Abricot kernel v7 : 01.04.15
Updated to Lollipop kernel sources 23.1.A.0.690
Update TWRP to 2.8.5.0
Add Force Fast Charge
Removed splash screen
Abricot kernel v6 : 24.12.14
Fix default freq not applying for all cores at boot
Fix -O3 compiler optimization
Fast hotplug : plug in cores in descending order
Abricot kernel v5 : 15.12.14
Increase voltage of higher frequency for better stability
Add support for displaying the number of tasks running
Add VR, SIO and FIFO schedulers
Add lagfree governor
Update TWRP to 2.8.1.0
Fix scaling_max_freq permissions
Set default frequency to 2.3GHz
Abricot kernel v4 : 11.12.14
Add CPU overclock up to 2.8 GHz (Thank's to Faux123 and DooMLoRD)
Change GPU frequency table to 27 - 657 MHz (Thank's to Myself5)
Disable Sony RIC
Remove msm_mpdecision
Set qcom mpdecision as default
Abricot kernel v3 : 07.12.14
First public release
Check my github to see all the changes.
Click to expand...
Click to collapse
FAQ
Q : With what ROM can I use this kernel ?
A : With any ROM based on Sony stock Marshmallow
Q : Your kernel isn't working / My phone isn't booting anymore
A : Read this whole post once more, search for your problem in thread and report it if you haven't found a solution.
Q : Can I install this kernel on locked bootloader ?
A : No ! This kernel is only for unlocked bootloader.
Q : Does this kernel include recovery ?
A : Yes ! You can access by pressing buttons when the led is lighting. Volume down to go to TWRP and Volume up to load recovery from FOTA..
Q : What are mpdecision and fast hotplug ?
A : This is what manage your cpu cores and decide which core will be online. Fast hotplug is a brand new hotplug that I wrote. See next post for more information
Click to expand...
Click to collapse
Thanks To/Credits
* Sony for their sources and device
* @DooMLoRD
* @thewadegeek for his Tutorial
* @show-p1984 for his mpdecision
* @glocklee for his breating notification mod
* @Envious_Data for his help and links
* @dssmex
* @Androguide.fr for Pimp my Z1
* bbedward
* Erasmux
* faux123
* The xda community for making me discover android and for answering so many of my questions
* Google for kernel sources and its search engine
* Apple for making expensive phone so that I never bought one of theirs
Click to expand...
Click to collapse
Please let me know per pm if there is any mistake or misspelled word in this thread. Automatic correction does a great job but since english isn't my mother thongue I'm pretty sure I made mistakes.
XDA:DevDB Information
Abricot kernel, Kernel for the Sony Xperia Z2
Contributors
pec0ra
Source Code: https://github.com/pec0ra/abricot
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-07
Last Updated 2016-05-20
About Fast hotplug
Motivation
I wasn't convinced by show-p's msm_mpdecision nor faux123's intelli_plug ( I don't even talk about qcom mpdecision ). I also wanted to start working on a bigger programming project to learn more about kernel developing so I decided to write my own hotplug.
Main features
I tried to make fast hotplug the lightest possible, so that it consumes the less resources possible when it is not needed (mainly at idle). One of the second goals was to make it customizable.
How to use
Deactivate qcom mpdecision (Pimp my Z1 will do this automatically when you choose fast hotplug)
Activate fast_hotplug
Code:
adb shell "echo 1 > /sys/module/fast_hotplug/parameters/fast_hotplug_enabled"
Tune it to your liking
How to configure
Unfortunately, there isn't yet any user friendly application to configure fast hotplug. The only way to configure it is to manually edit the module files with adb or a file editor.
I modified Pimp my Z1 to be compatible with fast hotplug. You can find the modified version at post 12
You can also find all the parameters at
Code:
/sys/module/fast_hotplug/parameters/
and edit them with adb command
Code:
adb shell "echo [COLOR="Navy"]<value>[/COLOR] > /sys/module/fast_hotplug/parameters/[COLOR="Navy"]<variable_name>[/COLOR]"
You can configure the following parameters :
fast_hotplug_enabled : 0 for disabled, 1 for enabled
boost_duration : Duration of boost in ms when screen is touched
threshold_to_boost : Instead of automatically pluging in cores on touch, fast hotplug checks that the load is above this threshold. This avoid cores coming online when reading file or website.
max_cpu_on : Maximum number of online cpu when screen is on
min_cpu_on : Minimum number of online cpu when screen is on
idle_threshold : Threshold under which fast_hotplug will remain almost idle and won't perform any check. This applies when only 1 core is online
plug_in_core_X_threshold : with X between 1 and 3. This is the threshold to plug in coreX.
plug_in_core_X_delay : This is the number of fast_hotplug cycles (see refresh_rate) to skip before pluging in coreX.
plug_out_core_X_threshold : Like plug_in_core_X_threshold but to plug out.
plug_out_core_X_delay
refresh_rate : Time in ms between fast hotplugs checks
screen_off_singlecore : 1 for activated, 0 for deactivated; Allows only one core to be online when screen is off.
If you are using linux, you can easily change the configuration with this small program : https://github.com/pec0ra/fast_hotplug_controller
You will probably want to create init.d script to make your configuration stay after reboot. If enough users want it, I can create an example of script.
Bugs / stability
Due to some conflicts with qcom mpdecision, it is possible that you encounter some bugs / reboots when both are enabled.
Configuration doesn't stick after reboots
Help needed
If you are a java developer (or want to learn ) and want to help in developing an app (or editing an already existing one) to control the hotplug, please send me a pm
Please tell me your impression, your custom configuration and / or your recommendation so that I can make it better in future releases.
Good luck.
Will try as soon as I can. :good:
Welcome! :good:
pec0ra said:
Help needed
If you are a java developer (or want to learn ) and want to help in developing an app (or editing an already existing one) to control the hotplug, please send me a pm
Click to expand...
Click to collapse
Regarding this, there is already an app out there that is FOSS, licensed under the GPLv2 license, looks sexy and should be easy to modify. It's called Pimp My Z1, I think it offers pretty much everything you want.
Other than that, cool that you're developing something new, I'll give it a shot!
Edit:
You may want to disable Sony's RIC it prevents you from writing to /system. This should help you.
I can't seen to get notification breath effect,i didn't do the mpdecision step,so could this make the diference?
Is this kernel compatible with franco kernel apps?
Sent from my D6503 using XDA Free mobile app
B1nny said:
Regarding this, there is already an app out there that is FOSS, licensed under the GPLv2 license, looks sexy and should be easy to modify. It's called Pimp My Z1, I think it offers pretty much everything you want.
Other than that, cool that you're developing something new, I'll give it a shot!
Edit:
You may want to disable Sony's RIC it prevents you from writing to /system. This should help you.
Click to expand...
Click to collapse
Thank you for the link
I'll see if I can do something with this app when I have more time (I've never made any android app).
Disabling ric is a good idea I'll do this for next version.
FrosteezBR said:
I can't seen to get notification breath effect,i didn't do the mpdecision step,so could this make the diference?
Click to expand...
Click to collapse
No, mpdecision won't affect it. Have you tried it on YadliKernel ? Did it work for all the notifications ? It seems like on abricot kernel they work for most of the notifications but not for sms.
vendetta718 said:
Is this kernel compatible with franco kernel apps?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
It is probably compatible (I didn't tried it) but you will probably not be able to change most of the configurations since they are not implemented in my kernel. Some configuration from my kernel (like fast hotplug) are also not implemented in the app so you can't change them from there.
pec0ra said:
Thank you for the link
I'll see if I can do something with this app when I have more time (I've never made any android app).
Disabling ric is a good idea I'll do this for next version.
No, mpdecision won't affect it. Have you tried it on YadliKernel ? Did it work for all the notifications ? It seems like on abricot kernel they work for most of the notifications but not for sms.
It is probably compatible (I didn't tried it) but you will probably not be able to change most of the configurations since they are not implemented in my kernel. Some configuration from my kernel (like fast hotplug) are also not implemented in the app so you can't change them from there.
Click to expand...
Click to collapse
i try with facebook,whatsapp,messaging and gmail
with a led tester its the same blink as stock
would i send you a dsmeg or anything?
FrosteezBR said:
i try with facebook,whatsapp,messaging and gmail
with a led tester its the same blink as stock
would i send you a dsmeg or anything?
Click to expand...
Click to collapse
There's no printing in the mod I think so dmesg would be useless. I'll try again with WhatsApp. Have you tried it on other kernels? Was it working ?
Edit : ok, maybe there is an error... In this case dmesg could be useful. If you have time you can send it, yes.
And I reconfirm that it works for telegram
Hey, can someone show us the notification mod?
Pimp my Z1
As @B1nny suggested, I tried editing Pimp my Z1 to add fast hotplug support. Everything seems to work and I even added some tweaks for a better support for our Z2 ( some default values were not really compatible with our device ). There are probably bugs for configurations other than fast hotplug. If I have time, I will fix them but for now, please use another app to set your frequencies / governors / voltage or live with the bugs. If you have questions about the app, you could also take a look at the official thread to see if it is already there or maybe just to give the dev a thanks.
I'll probably make a pull request to @Androguide.fr with the changes but until then you can use my own build linked to this post. If you already have the app installed, you will have to uninstall it first because signature is different.
You can see the full source and the changes on my github : https://github.com/pec0ra/Pimp_my_Z1
Special thanks to @Androguide.fr for his great app and to @B1nny for his link
@pec0ra
Good news to have a new kernel dev for our beloved Z2 !
However, I've tried to flash your kernel, the flashing process seems to work correctly but actually I stay stuck to the last doomlord advanced stock kernel. Any suggestion ?
nreuge said:
@pec0ra
Good news to have a new kernel dev for our beloved Z2 !
However, I've tried to flash your kernel, the flashing process seems to work correctly but actually I stay stuck to the last doomlord advanced stock kernel. Any suggestion ?
Click to expand...
Click to collapse
You should try to extract the .elf from the zip and flash it via fastboot
Code:
fastboot flash boot <name>.elf
Anyone else experiencing the same issue ? Maybe I did something wrong in my zip.
pec0ra said:
You should try to extract the .elf from the zip and flash it via fastboot
Code:
fastboot flash boot <name>.elf
Anyone else experiencing the same issue ? Maybe I did something wrong in my zip.
Click to expand...
Click to collapse
I think you mean the .img file instead of .elf.
Other than that, the kernel works fine for me. I did manually flash it via fastboot. (because I prefer to flash it via fastboot)
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
B1nny said:
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
Click to expand...
Click to collapse
I was going to post the same thing
Waiting for confirmation...
B1nny said:
I think you mean the .img file instead of .elf.
Other than that, the kernel works fine for me. I did manually flash it via fastboot. (because I prefer to flash it via fastboot)
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
Click to expand...
Click to collapse
Thank you
Yes, I meant .img. It seems like it'll take some time to get used to this new device. The kernel destination you pointed out is probably the issue, yes. And that's probably the notification problem too. Seems like the kernel never got flashed so it's logical that notification mod doesn't work...
I'll change this tomorrow morning
Maybe someone can test it until then.
pec0ra said:
Thank you
Yes, I meant .img. It seems like it'll take some time to get used to this new device. The kernel destination you pointed out is probably the issue, yes. And that's probably the notification problem too. Seems like the kernel never got flashed so it's logical that notification mod doesn't work...
I'll change this tomorrow morning
Maybe someone can test it until then.
Click to expand...
Click to collapse
Yes, this was indeed the issue, I've just succesfully flashed your kernel changing "Kernel" to "boot" in the script.
Now testing
I can't rename mpdecision.. I tried with root explorer and root browser
sh4d1t0 said:
I can't rename mpdecision.. I tried with root explorer and root browser
Click to expand...
Click to collapse
That's due to Sony's RIC being enabled by default. If you look at my previous post where I mention it there is a command you can run in ADB to temporarily disable it, not ideal but it will help you rename the file.
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.
Veno Kernel for Huawei HI6250 devices
Note: I'm waiting for Huawei to release new kernel sources with Nougat, until then I'll focus on fixing any bugs people find. New features will come with Linux 4.1.
The goalTo provide better battery life and more smoothness to your everyday experience, but without sacrificing one in the name of the other (so no +smooth/-battery tweaks and vice versa).
Maybe some extra features? I don't know, I hate unnecessary bloat that provides nothing to everyday user (or even developer).
Okay, so what's in?
Based on latest Huawei VNS sources from January 2017
Turns out newest sources are unstable, I rebased the kernel on 2016 release
Patched to 3.10.105 upstream
Built using Linaro 6.3 toolchain
DM Verity disabled
UKSM 0.1.2.6 (backported from Linux 4.0)
BFQ I/O scheduler
ROW I/O scheduler
Thunderplug hotplugging driver*
Dynamic Fsync
AnyKernel2 package! Compatible with any ROM except stock newer than B336.
For full list of changes see here.
* - Thunderplug is out for now, as it made the device unstable
Installation
Make sure you have TWRP installed
Create backup of your current boot
Flash the zip package (it will modify your boot instead of flashing entire boot.img)
Reboot and enjoy! Look below for how to use additional features
THAT'S A LOT OF CHANGES, BUT I HAVE NO IDEA WHAT I'M READINGA quick ELI5 then:
Patched to 3.10.105 upstream
Newer source = less bugs and better kernel in general.
Built using Linaro 6.3 toolchain
Kernel has extra ARM optimizations and phone is faster/has better battery life.
DM Verity disabled
Big brother won't know that you have fiddled with root.
UKSM
More free RAM and less CPU load, so MORE RAM, PERFORMANCE AND BATTERY LIFE.
BFQ I/O scheduler
ROW I/O scheduler Schedulers
With default settings phone will run smoothly even when you're playing FLAC music, compressing 10 archives of 5GB of music and banging your gf (I can't actually know that)
Dynamic Fsync
When you're using the phone, it cares more about your smooth experience than writing data to disk, so the system seems more responsive.
AnyKernel2 package
Can install on top of anything, Huawei is upgrading to kernel 4.1 with EMUI5 though, so flashing might be going backwards (this is 3.10), at least until they release new sources.
DOWNLOAD AND SOURCE
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Source code:
https://github.com/Avsky/kernel_hi6250_vns (unstable sources)
https://github.com/Avsky/android_kernel_huawei_hi6250_nem
Latest release: 2017-05-22
Download: https://www.androidfilehost.com/?w=files&flid=161384
20170406
Rebased on older, more stable Huawei sources (from 2016, everything else is the same)
Removed some of the debugging stuff from the kernel
Enabled Huawei hotplugging driver (it appears to only control big cores tho?)
20170405
UKSM patched to v0.1.2.6 again
Enabled/Disabled a lot of stuff in defconfig
Disabled mostly debugging stuff, which should result in slightly faster kernel.
Enabled a lot of USB drivers (so most stuff should work with Host Mode, if anyone ever uses that)
Enabled some missing Huawei code from older kernel sources, which I believe caused lowmem killer to go haywire, causing heavy apps to randomly close (I tested this one a bit, apps like Snapchat seem to no longer close, can never be sure)
20170404 - BUGFIX attempt
Rolled UKSM back to v0.1.2.3, should help with apps closing without any error
20170330
Removed Thunderplug, as it was causing freezes and bootloops (Huawei HMP doesn't like to have cores offline apparently), system should be stable now
Hotplugging will most likely return, with different driver or when Huawei releases 4.1 kernel sources.
My birthday release, yay, have a stable kernel everyone
20170329
Fix multiple lcd_notify calls
Protect against some hotplug race conditions
Run Thunderplug in per-core mode by default (gotta save the energy!)
Dynamic Fsync (ported to lcd_notify)
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
20170325
Initial release
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
RazOne said:
Works with LineageOS 14.1?
---------- Post added at 10:11 AM ---------- Previous post was at 10:10 AM ----------
Or nougat not supported?
Click to expand...
Click to collapse
Yes, I'm running it on LOS 14.1 right now.
If somebody could test it on stock and EMUI5 ROMs (just for the heck of it, keep backup) I'd be grateful.
Sent from my VNS-L21 using Tapatalk
Installed succesfully on L31 running Resurrection Remix nougat. I will try for a few days and report back feedback
Will try it on EMUI 5 as soon as I have time.. very happy to see our device is getting devs' attention, keep up the good work!
Good afternoon. Your modification will work on EMUI 4 ?
thank you
upd.: on EMUI 4 it worked
http://cs5-1.4pda.to/9967169/Screenshot_2017-03-26-14-54-33.png?e28279d161430a29fd16f793d314a066
Hello
I have tested on vns-l31c636b361 (nougat), it does not start blocking your device is booting now ....
(I think I forgot the root)
I will re-try with but I get it with dload c636b170.
New try, l31c636b170 (emui 4) + twrp meticulus, ok :good:
Flashed it more than a day ago, working great on LineageOS 14 (VNS-L31), yet to find any issues...
Wat does it really do haha? Saw "whats in" but dont really know what that means hahaha.
Are you planning to add other CPU/ GPU governors?
uspy said:
Are you planning to add other CPU/ GPU governors?
Click to expand...
Click to collapse
It's something I'd like to do at some point, but there are very few governors which are properly adapted to octacore devices and none so far worked out of the box with Huawei kernel. I'm keeping my eye mostly on ElementalX and Impulse, but they'll need changes to even compile.
For now stick with interactive, next release with thunderplug enabled by default will bring better battery life.
Sent from my VNS-L21 using Tapatalk
It's really nice to hear that you are working on it. Thanks for your reply.
20170329 release
New release is out! Note that I wasn't running on a new build for very long, so issues might still surface, keep a watch on this thread.
Changes:
Fix multiple lcd_notify calls
lcd_notifier call was implemented in wrong section of Huawei LCD driver, oops.
Protect against some hotplug race conditions
Stability fixes mostly, based on ThunderZap kernels.
Run Thunderplug in per-core mode by default (gotta save the energy!)
Due to how scheduling works in Huawei kernel, it might keep one or two big cores up after heavy load, but should be fine once the screen is turned off.
Dynamic Fsync (ported to lcd_notify)
I moved Dynamic Fsync (thanks faux123) to lcd_notify to avoid kernel bloat from powersuspend or earlysuspend (which are not present in the kernel).
Fixes to backported UKSM (possibly fixes binder errors, apps not opening until reboot)
My derp in commiting changes might have caused critical fail in Android Binder, which resulted in random reboots and new apps not opening. Tell me if anyone encounters it.
Overall this release should bring much better battery life and smoothness to the system (mostly thanks to dyn fsync).
Download: https://www.androidfilehost.com/?fid=673368273298943375
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk. I also have systemless xposed installed, maybe there's a conflict?
zgomot said:
Settings crash, dialer crashes when dialing any number after flashing latest release.
Anyway to unflash, or fix this? I didn't do a twrp backup prior to this, but I did do a cache/dalvik wipe after flashing.
Will a factory reset fix this? Or maybe just wipe /system in twrp?
I'm running stock b170 on vnsl21, meticulus twrp, rooted with magisk.
Click to expand...
Click to collapse
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Avsky0 said:
Ask someone for stock boot.img or extract it from huawei image.
Also logs, I need logs.
Click to expand...
Click to collapse
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
edit: I was just about to instal catlog to provide logs, while going for another round of dalvik/cache wipe and guess what - it seems everything is ok now. Will keep you posted if any issues arise.
zgomot said:
So then, would a fastboot flash boot boot.img work to uninstall the kernel?
Click to expand...
Click to collapse
Yes, that's how you flash kernel images. Also keep backup next time.
Sent from my VNS-L21 using Tapatalk
Also a question if I may. Would this kernel provide any benefits over the stock one if I don't install Kernel Adiutor and change any of the settings - basically just flash it and forget it?
edit: 2 questions if you could be so kind as to indulge me.
Does this modify haptic feedback? As it seems to me - either that or I'm crazy - that keyboard haptic feedback is different after flashing this. It's weaker and a little strange (?), however, navbar haptic feedback and other vibrations seem to be the same as with the stock kernel.
Thanks for your time
further edit for feedback: The fingerprint sensor is a bit iffy now. It's considerably slower sometimes, and generally slower and doesn't always vibrate on unlock, like 9/10 times it doesn't vibrate.
I flashed today's build and I noticed that only one core was active, and I can't turn on more than 4 cores so I can basically use 2 little and 2 big cores. Is this as it should be expected?