The first time I made AdaMax was for the Chinese Galaxy S4 Duos GT-I9502. I ported Adam kernel and added more tweaks from other kernels like Persus, halaszk (5420). After several releases, I decidec to spread this kernel to more models. So I built the v8 for both Chinese and international GT-I9500. This thread it for hosting it.
This week, i successed compiling for the s4 with 5410 cpu. As we know GT-I9500, GT-I9502 and SCH-I959. They share almost same compiling configure and their own ramdisk. So I compile them together with almost same features.
At last, I have to make following declarations, AGAIN:
Take your own risk and responsibility on flashing this kernel. I am not responsibale for any loss of your hardware, software, data or warranty.
Read this OP from start to finish before flashing the packages or asking any questions. There is a Q&A section. Any questions already answered will be ignored by me and may be insulted by other members. So save your your keyboard, your time and your data traffic.
No ETAs.
Don't ask me to make this kernel for a specific rom. There are basically only two kinds of roms, AOSP and TouchWiz. So I compile for these two kinds with differnet SDK levels. If it dose not work on some rom, don't blame me and ask me to adapt the rom for it.
If you found a new version, but its download link is not directly showed in this OP, that means it is a version I don't think good enough to be a release. So take your own risk to use it. I will remember your feedback, try to make changes, but not respond with posts.
Thanks to a lot of people, I will add their names here... @wanam, [email protected], @Dees_Troy and Team Win, @AndreiLux
As my habit, I always put the download link first:
v15: https://github.com/maxfu/android_kernel_samsung_exynos5410/releases/tag/v15-9500
File name instruction:
touchwiz: for most used international GT-I9500 with exynos5410 cpu.
aosp: for AOSP KitKat 4.4 roms like CM, ramdisk comes from CM 11
kk442: kernel for KitKat 4.4.2
jb43: kernel for Jelly Bean 4.3
jb442: kernel for Jelly Bean 4.2.2
lite: live version is built with stock zImage and maxfour initrd. It has limited maxfour features. And sometimes selinux f**ks up the STweaks.
boot: system kernel package
recovery: recovery kernel package
kernel: system + recovery combined kernel package
*.tar/*.tar.md5: Odin package
*.zip: CWM/TWRP recovery package
example.1: boot-i9500-aosp kk442-v10f1tc.zip means a system kernel image CWM/TWRP flashable package for international I9500 with TouchWiz KitKat 4.4.2 roms.
example.2: kernel-i9500-aosp-kk442-v10f1tc.tar.md5 means a system recovery combined odin package for international I9500 with AOSP roms like CM.
Old versions:
v14: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v14/GT-I9500/
v13: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v13/GT-I9500/
v12: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v12/GT-I9500/
v11: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v11/GT-I9500/
v10f1: https://sourceforge.net/projects/maxfuacm/files/Kernel/MaxFour/v10f1/GT-I9500/
You can always go to the following addresses to see whether there is a new version:
https://github.com/maxfu/android_kernel_samsung_exynos5410/wiki
https://github.com/maxfu/android_kernel_samsung_exynos5410/releases
I open the issue section for the source code, you can report problems here. Please provide at least version aosp/touchwiz jb/kk.
https://github.com/maxfu/android_kernel_samsung_exynos5410/issues/new
The source code:
You can
git clone https://github.com/maxfu/android_kernel_samsung_exynos5410.git
git clone https://github.com/maxfu/initramfs_samsung_galaxy_s4.git
git clone https://github.com/maxfu/toolchains.git
use the build.sh for exynos in toolchains/script ro build the kernel.
you need to su before build the kernel cause the ramdisk belongs to root.
Since this is a side product of my kernel for GT-I9502 which is the phone I am currently using. I don't actually test this build for GT-I9500, so I really need feedback. And please backup your rom before using this.
Features:
Built with OSRC KK 4.4 source and ramdisk, now it should work on many 4.4 roms.
Contains most features from Adam kernel including Wolfson Audio Control. For I9502 which uses yamaha sound chip, Wolfson Audio Control will be hidden automatically since it does not work.
From v10, the kernel is renamed to MaxFour due to wamam's request.
Kernel + Recovery release at one time, recovery based on TWRP with EFS_GSM (for Chinese Duos devices) support.
Compiled with GCC 4.8 toolchain from Google NDK r9c.
Packed in LZMA format to make smaller images.
Native exfat support based on OSRC exfat source code.
UCI script for STweaks and may be others.
Unlocked some hidden CPU frequency: 2.0GHz, 1.9GHz, 1.8GHz, 1.7GHz, 800MHz, 700MHz for big cores; 1.3GHz, 1.2GHz, 400MHz,
300MHz, 200MHz for little cores. Frequencies over stock like 1.7GHz for big cores and 1.3G for little cores are implemented in tc*/overclock version.
Added more STweaks settings which are not included in Adam kernel, including CPU power management, Tools with reboot options, GPU settings, CPU governor.
Android logger is compiled as standanlone module, so user can disable it completely to save power.
Tc/overclock version contains Persus dvfs for GPU with 700MHz overclock, thanks to AndreaLux.
Built-in Seeder entropy generator to provide lag reduction although it is not significant as it was on Gingerbread.
Built-in busybox with auto-installation.
Optimize on ram.
Added several I/O Schedulers including ZEN and ROW.
Built-in dynamic eMMC read ahead
Built-in Asynchronous Fsync
Compiled with compile flag for Cortex-A15 and NEON
Disable KNOX and SELinux when booting, selinux will be set to permissive with the boot command line.
init.d support.
A lot of changes and fixes.
Disabled a lot of rarely used devices support.
PS:
*1. TC means turbocharged, so it is overclock
Change Log:
v15:
Rebuild with GT-I9502 CHN KK Opensource from OSRC.
Upgrade KSM (Kernel Samepage Merging) to uksm (Ultra KSM) which has Super quiet CPU usage, Ultra scan speed and High CPU efficiency.
Support init.d.
Lower CPU frequencies presented in previous versions, voltage options coming soon.
GPU tweak presented in previous versions.
STweaks cueerntly unsupported, coming soon.
mDNIe and Sound Control coming soon.
AOSP support coming soon.
v14:
Upgrade kernel to 3.4.10
Implement AES-ARM and SHA1-ARM crypto algorithm
Rollback selinux related script to v11
v13:
Rebuilt source tree from HNC6 source.
Most features kept
INT, MIF, MEMIO settings removed, these should not be touched
Should be much better than v12
Fixed video bug for AOSP, I think it is fixed
Upgraded AOSP initramfs, may fix the modem/signal problem
Set ro.secure and ro.adb.secure to 0
Camera lag? Less.
Upgraded busybox
v12:
I don't want to talk about it, this version is totally a rubbish
v11:
STweaks: Added Chinese UI, works on Chinese system, when the language is set to other ones, English UI will show. An templete is provided for more translations.
STweaks: Added boost mode in the Misc tab. The boost mode is found when the news of Samsung cheating on benchmark softwares came out. When a benchmark software is detacted running, the boost mode will be on to allow higher temprature and faster CPU scaling. Simply turn on this mode will not provide any visable change, it should be used with CPU, GPU, INT, MIF clock operations.
STweaks: Added control for Internal, Memory Interface and Memory I/O.
STweaks: Added a button to switch the USB mode to Mass Storage Mode, which is classical mode before GingerBread got out dated.
STweaks: Added a CPU wake lock switch.
STweaks: Added instructiuon of Sound Control being not available on models other than I9500.
STweaks: Added instruction of GPU voltage control being not available on non-tc versions.
Kernel: Added a odin mode. Now we can reboot to download mode with "adb reboot odin". The original commands still work.
v10f1:
initial build for XDA users.
Q&A:
I did not reserve a post for this section, so I will put the Q&A here in the OP.
Q: Which package should I use? A: boot is what you need. recovery is just a side product.
Q: Which version I should use? A: Please the "File name instruction" section in the OP, you will find the answer.
Q: Do I need to wipe the data after I flash? A: Well I don't think you need, but due to some report, wiping data can solve certain problems after flashing this kernel. So whatever you like, please backup data before you flash or wipe.
Q: Which rom does this kernel support? A: I can't tell, please refer to the File name instruction section, if you rom is not mentioned there, it is not supported?
Q: Does this support MIUI? A: Official MIUI is based on touchwiz 4.2.2. So please refer to Q2,3,4.
Q: There is no OC in tc version. A: In the init.rc there is a script limiting the CPU frequency to 1.6GHz, so you should use STweaks to unlock it. Please open /sys/devices/system/cpu/cpu0/cpufreq/UV_uV_table, if there is 2000 1900 1800 and 1700, then there is OC, just unlock it.
Q: Some app FC? A: Usually FCs are not due to the kernel, check the rom first, and settings etc, the kernel should be the last reason, cause it just provide the bridge between the system hal and hardware. Report the fc, I will take a look, but I can not say I can fix it.
Q: Battery life? A: It is due to your habit, just like driving a car, a Toyota Prius can use 10L gas if driven by somebody like Michael Schumacher. As my test, due to my habit with non tc version, it is better than stock.
Q: Do I need STweaks to run the kernel? A: The kernel can run without it, but with it you can have more options.
Q: STweaks shows "unextected error"? A: This situation usually happens at the first time STweaks starts, it is OK. Just go on using STweaks.
Q: STweaks FCs. A: Well this sometimes is due to the kernel, sometimes. Here is something you can do: Wipe the STweaks' data, remove /data/.maxfour and /data/.adamax, check the superuser software and give STweaks root access. And yes you need root access. At last, use normal version.
Q: Auto root? A: Use the CWM zip package. And I would take it out soon. Sometimes it breaks root.
Q: Not actually auto-root with v13? A: Yes, v13 will put a wizard like app which will lead you download SuperSU, only when your rom is not rooted.
Q: Conservative governor stock at certain frequency? A: Don't use it, only ondemand governor is optimized for 5410 with big.little cores.
Q: Can you add something? You must do something? Please do something? A: I take advice, but not demand. The reason is simple: I make this kernel due to my interests, not purchase orders. I am not funded for doing this. If the advice is good, I'd take it. If it is just a personal preference, I have to consider it.
Q: Got very low volume of sound? A: Use stweaks, I9500 has wolfson sound control.
Q: Video color is not correct, got blur faces. A: v13 should have this issue fixed.
Q: No internal storage access permission. A: I will make a workaroung later. For now, remount it with rw option through adb.
Q: Random reboot. A: Well, it exists, I admit. I don't know why. I will look for the reason.
Q: After flashing, the phone won't boot. A: Well, I can't guarantee that this kernel works everywhere. And please check if you are using the correct version.
Q: When is your next release? A: I don't know either.
Q: I flashed, it doesn't work. A: Well, it does not work. I don't know why cause it just don't work. I only answer information-rich questions. Questions like this is only a waster of your keyboard, your time and your data traffic. Please at least tell me which version and what rom you are using.
Q: Anything asked above. A: I will keep silence. Other people may insult for this.
Q: Why don't you answer/respond our questions? A: I am a employee, husband, father and son of someone other than XDA and you.
maxfu said:
The first time I make AdaMax is for the Chinese Galaxy S4 Duos GT-I9502. I ported Adam kernel and added more tweaks from other kernels like Persus, halaszk (5420). After several releases, I decidec to spread this kernel to more models. So I built the v8 for both Chinese and international GT-I9500. This thread it for hosting it.
Thanks to a lot of people, I will add their names here...
As my habit, I always put the download link first:
https://github.com/maxfu/android_kernel_samsung_galaxy_s4/releases/tag/9500v8
The uploading is still on going...
Features:
Based on OSRC GT-I9500 JB Opensource Update4 source tree.
Contains most features from Adam kernel, so this kernel is called Adam + Max.
Kernel + Recovery release at one time, recovery based on TWRP with EFS_GSM (for Chinese Duos devices) support.
Compiled with GCC 4.8 toolchain from Google NDK r9c.
Packed in LZMA format, smaller images.
Native exfat supportbased on OSRC exfat source code.
UCI script for STweaks and may be others.
Unlocked some hidden CPU frequency: 2.0GHz, 1.9GHz, 1.8GHz, 1.7GHz, 800MHz, 700MHz for big cores; 1.3GHz, 1.2GHz, 400MHz,
300MHz, 200MHz for little cores.
Frequencies over stock are implemented in overclock (tc/turbocharged) version.
Added more STweaks settings from Adam kernel, including CPU power management, Tools, CPU settings, CPU governor.
Logger module is compiled as standanlone module, so user can disable it completely to save powew.
Overclock (tc/turbocharged) version contains Persus dvfs for GPU with 700MHz overclock, thanks to AndreaLux.
Disabled a lot of rarely used devices support.
Built-in Seeder.
Built-in busybox with auto-installation.
Optimize on ram.
Added several I/O Schedulers including ZEN and ROW.
Built-in dynamic eMMC read ahead
Compiled with compile flag for Cortex-A15 and NEON
Disable KNOX and SELinux when booting
init.d support.
A lot of changes and fixes.
Click to expand...
Click to collapse
Most features of Adam & Perseus Kernel. Does this include the Wolfson Audio Control?
Paolonicus said:
Most features of Adam & Perseus Kernel. Does this include the Wolfson Audio Control?
Click to expand...
Click to collapse
I kept the feature, so it should show up in STweaks on I9500. I am using 9502 which does not have the feature so I can not test it. When I compile for 9500, sound control is enabled.
@maxfu Is this kernel for the 4.3 or 4.4.2?
a2441918 said:
@maxfu Is this kernel for the 4.3 or 4.4.2?
Click to expand...
Click to collapse
Sorry I did not directly mention. It is for 4.3 JellyBean.
maxfu said:
Sorry I did not directly mention. It is for 4.3 JellyBean.
Click to expand...
Click to collapse
Can you please mention it in the op please it's very confusing.
Thanks.
Sent from my GT-I9500 using Tapatalk
Will there be version for Kitkat?
This is something that prevents me from flashing the newer version of Android.
Paolonicus said:
This is something that prevents me from flashing the newer version of Android.
Click to expand...
Click to collapse
If Samsung releases the source code for 4.4, I will.
Paolonicus said:
This is something that prevents me from flashing the newer version of Android.
Click to expand...
Click to collapse
I have a good news for you. I found I9500XXUFNB1: GT-I9500_KK_Opensource.zip, so I will push it up in several days.
How about battery life and performance compared to stock kernel?
Sent from my GT-I9500 using XDA Premium 4 mobile app
snxxxxx said:
How about battery life and performance compared to stock kernel?
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well it is hard to say. If you use the normal version, it should be battery friendly. The tc version is overclocked. Due to my 3DMark result, the overclock version maxied out the First and Second stage tests.
maxfu said:
Well it is hard to say. If you use the normal version, it should be battery friendly. The tc version is overclocked. Due to my 3DMark result, the overclock version maxied out the First and Second stage tests.
Click to expand...
Click to collapse
If you can Make it AOSP support also
Thanks maxfu for the contribution...will try soon. You didn't mention about the screen color option from perseus kernel. Is it there?
Yesss at last some hope for 4.4 custom kernel!! Thank you Maxfu for continuing Wanam's legacy.
Wow!
maxfu said:
I have a good news for you. I found I9500XXUFNB1: GT-I9500_KK_Opensource.zip, so I will push it up in several days.
Click to expand...
Click to collapse
Sweet! Can't wait to try you kernel! Thanks a bunch!
For AOSP, I will try.
Sent from my GT-I9502 using xda app-developers app
great to see another addition to kennels for gt -9500. please also add support fir miui.
Sent from my GT-I9500 using Tapatalk
Some Proposals
1. Auto Install Stweaks
2. Clearly describe CPU Options which one for big cores and which for little cores
3. Don't lock GPU Frequency at 532MHz as i see by default ... maybe more relaxed 177-532 settings?
4. SELinux is set to Permissive by default ... maybe set as Disabled?
and maybe some very useful Insecure version please?
ro.secure=0
ro.adb.secure=0
(computer translation)
Hi, I already flashed Adam Kernel on my S4. Can I simply flash this Kernel on recovery or do I need to do something else?
Dnssuffix said:
Thanks maxfu for the contribution...will try soon. You didn't mention about the screen color option from perseus kernel. Is it there?
Click to expand...
Click to collapse
If it is in Adam kernel, then it is here. There is a screen tab in STweaks.
Related
Hi fellows!
As some of you have seen in Humberto's P1000L/N Gingerbread thread, I'm building a Gingerbread kernel for these devices.
At the beginning, I thought that I'll just port the Overcome kernel to ours devices and I'll never touch on these files again.
But it turns out that it shouldn't be like that. So, to avoid mess with Humberto's thread, I decided to begin a new one.
Here are the current features of my Kernel, which was initially based on Overcome v3.3.1 kernel:
Main Features of latest stable version (20111029)
Kernel 2.6.35.14
Lagfree governor
Smoothass governor
SmartassV2 governor
BFQ IO scheduler version 2 (revision 1)
Conservative, Ondemand, Performance, Powersave, and Userspace governors from 3.1 kernel tree
Built with 2011.03 toolchain
TV SUPPORT (P1000L only)! (it is available if you flash the recently leaked P1000L gingerbread version: http://forum.xda-developers.com/showpost.php?p=17993125&postcount=355)
10-points multitouch driver
File Systems support: RFS/EXT{2,3,4}
Overclock (@1.6GHz) with these steps: 1.6ghz, 1.5ghz, 1.4ghz, 1.3ghz, 1.2ghz, 1ghz, 800mhz, 600mhz, 400mhz, 200mhz, 100mhz
Undervoltage
Touchscreen Undervolted (from 3.3V to 2.1V)
RAM Undervolted (1.8V to 1.7V)
ADC Unvervolted (3.3V to 3.0V)
Voodoo Sound v10
Built in CIFS/TUN/SlowWork support
Stochastic Fair Blue (SFB) Network Scheduler
V(R) Schedule, but SIO set as default.
Autogroup Scheduler
Asynchronous I/O Enabled (AIO)
Backlight Notifications
Humberos' Initramfs 20111102
Features that needed to be test (I'll appreciate any help):
BLN has problems
I'll appreciate any help or feedback!!
Link for download the latest stable version:
http://www.mediafire.com/?9ug8n71vgc5ik7u
md5sum zImage
0fce8943c0b950c05e0d5163cf662460 zImage
Source code:
https://github.com/ronisbr/GT-P1000LN-GB-Kernel
I would like to thanks:
The Overcome project
jdkoreclipse
koxudaxi
Humberos
Thanks,
Ronan
Changelog
20111105 UNSTABLE (http://www.mediafire.com/?13g5330zs209qn1)
md5sum zImage
21248e6f24a54a99947b248c33cad7b2 zImage
This is an UNSTABLE kernel, and we are expecting some functionality breakage! Again, some patches that I applied hasn't been tested in any other GT kernel yet...
Use tiny-shmem instead of full shmem implementation
Tiny shmem is an alternative implementation of shmem filesystem that uses RAMFS code instead TMPFS. It should be suitable for small system which doesn't have swap and doesn't need the advanced features that the full implementation has, e.g. the size limit control. By removing these unnecessary features, tiny-shmem should increase the performance.
For Galaxy TAB, swap isn't used and size limit isn't a necessary feature, so tiny-shmem should work well.
But it is just my guess! I really need help to test it...
Many performance tweaks in low killer memory
It should make memory manager better.
Enable CPU-supported unaligned access
Enable the option CONFIG_ALLOW_CPU_ALIGNMENT, since the Galaxy Tab P1000 has a Cortex-A8 based CPU.
Advanced ARM processors, such as the Cortex series and ARMv7-based CPUS are capable of performing unaligned accesses for many types of memory accesses. Typically, using a cpu-based alignment fixup is faster than doing such a fixup in software. For best performance on advanced CPUs.
20111029 STABLE (http://www.mediafire.com/?9ug8n71vgc5ik7u)
This version was made stable on 05-Nov-2011, since there weren't any bug reports.
md5sum zImage
0fce8943c0b950c05e0d5163cf662460 zImage
At this point, I decided to add more aggressive updates in my kernel.
I have searched the others gingerbread kernels for devices like GT to verify if there is anything that can be used here.
Conclusion: I found tons of things that can make our experience and overall stability better.
For this first time, I just added some of them and I'm willing you to test it and report anything weird that you find.
Update initramfs from Humberto's kernel
Update initramfs from Humberto's kernel. It now has:
- CwM recovery v5.1.2.6
- New su binary v3.0
Thanks to Humberos
Erase memory pages when they are freed
Should improve memory handle.
Thanks to renaudallard.
net: wireless: bcm4329: compile wifi driver with Os flag
Add -Os GCC optimization flag to compile wifi driver.
This approach was used in Galaxy S kernel, so it should be fine
in GT-P1000 also.
Thanks to zachariasmaladroit.
ashmem improvements
ashmem: fix deadlock when system is low on memory
ashmem: Add cache flush routines to ashmem (zachariasmaladroit)
cpuidle: menu: fixed wrapping timers at 4.294 seconds
If everything goes fine, I'm planning to add more and more patches at each update.
This way, it would be much easier to track possible regressions.
20111026 (http://www.mediafire.com/?7fv630kp5bu15ev)
Using 2011.03 toolchain again
It turns out that the problems regarding random reboots with 2011.03 toolchain is being caused by samsung modemctl driver. For some reason, it isn't compatible with the newer toolchain, so the solution was avoid the driver building and use a binary version that was built with 2009q03 toolchain.
After this, the new kernel built with 2011.03 toolchain doesn't appear to have the random reboots and problems of the old version.
Thanks to alterbridge86 and chib_cr!
20111025 (http://www.mediafire.com/?931h2ev795faztf)
Revert to 2009q3 toolchain
When the kernel was built with 2011.03 toolchain, some users are having random reboots, e.g. when the USB was plugged the TAB rebooted.
Thanks chib_cr!
20111024 (http://www.mediafire.com/?o8be3gs8dfb609u)
I want to thanks alterbridge86 and the Overcome project. Basically, every change was taken from his tree.
Tweak IO schedulers for flash based devices
Should bring some improvements.
ARM: dma-mapping: free allocated page if unable to map (Russell King)
Should kill some process getting stuck and holding the CPU from entering deep sleep, which result in battery drain.
Update smartass governor to version 2 (erasmux)
New version of smartass governor.
Tweak touchscreen sensitivity
Touchscreen sensitivity is improved.
Add compatibility for 2011.03 toolchain
This kernel is being built with 2011.03 toolchain, which should bring some improvements.
Update BFQ IO scheduler to version 2 (revision 1)
Thanks to koxudaxi
20111006 (http://www.mediafire.com/?ahqucc9h5vwgo8j)
Don't check module magic (by Koxudaxi)
This fix some boot loop issues after build the kernel under certain conditions.
Set Kernel version to 2.6.35.14
It turns out that Overcome kernel has already applied all kernel's patches up to 2.6.35.14, so the correct version was set in Makefile.
20111005 (http://www.mediafire.com/?zm5t2w82feqtjuy)
Change RAM voltage from 1.8V to 1.7V
Fix BLN
Although, it still has issues.
Change ADC voltage from 3.3V to 3.0V
Change LCD voltage from 3.3V to 2.1V
10-points multitouch driver
samsung_modemctl is being built now
Overcome kernel is using a pre-built samsung_modemctl driver, because it is avoiding kernel to be built correctly. Here, this issue doesn't happen, so this change was reverted.
20110923 (http://www.mediafire.com/?2e0565sc1sgqmqr)
Update governors set from 3.1 kernel tree
The following governors were updated using Linux 3.1 kernel
tree:
Conservative
Ondemand
Performance
Powersave
Userspace
20110916 (http://www.mediafire.com/?98y1xe2hhu1mrtr)
Added lagfree governor
Thanks to jdkoreclipse.
Added smoothass governor
Thanks to jdkoreclipse.
20110909 (http://www.mediafire.com/?92d7sz9e7niuz2z)
Initial commit
Overcome Gingerbread Kernel v3.3.1 with Samsung's
P1000L/N Gingerbread Kernel patches.
Reserved......
Downloading...
I'll give it a try!
chib_cr said:
Downloading...
I'll give it a try!
Click to expand...
Click to collapse
Thanks
Tell me what do you think (remember it is a Gingerbread kernel for P1000L/N devices!).
I'm looking for feedback, specially about the new governors...
Works great!
Can't set clock to 1600 Mhz (freezes), but at 1500Mhz it scores 2505 on Quadrant!!
So far smoothass working well...
Tested for about 10 min, so can't tell you much...
BTW: I',m running stock 2.3.3
Install
How to install this file to tab?
Spyma said:
How to install this file to tab?
Click to expand...
Click to collapse
If you have a P1000L/N tab with Gingerbread, you just need to restart it in download mode, unzip the file, and flash with heimdall:
heimdall flash --kernel zImage
But BE CAREFUL, if you don't know what you are doing, you can brick your tab!
ok thanks.
Just for your information, I have just build a kernel with swap support.
To test it, I created a swap partition on my sdcard.
It is working. Although, I haven't seen any improvements...
When I open too many programs (like 8), android memory manager still force-kill the apps, while I'm expecting that the programs should be transfer to swap memory and, just when it is full, that a program should be force killed.
Well, if anyone wants, I can upload a kernel with swap support, but, at this time, I think it is useless...
Ronis_BR said:
If you have a P1000L/N tab
Click to expand...
Click to collapse
I tried to find out the different models and how they equate to one another but Google sends me to everything but which is which model. I have according to my devices "about" a GT-P1000. But, how do I know which model is the L or N? Just to give you more info, I am using the T-Mobile flavor with the modem swap program with Kratos currently flashed.
Hi fellow,
P1000L/N are latin model, if you are using Overcome Kratos with default kernel, you probably have a P1000 device and my kernel isn't compatible.
But you can check it under configurations / about ... (the last menu option), it should have as model number GT-P1000.
Thanks,
Ronan
Hi fellows!!
I have just tested the recently leaked gingerbread version with my kernel and everything is working flawlessly, including TV!
I'll post more details...
Ronan
Ronis_BR said:
Hi fellows!!
I have just tested the recently leaked gingerbread version with my kernel and everything is working flawlessly, including TV!
I'll post more details...
Ronan
Click to expand...
Click to collapse
A leaked GB version for L/N or just L?
If it has TV support I think it is for the L version. But which is the GB version? 2.3.3, 2.3.4 or 2.3.5?
If ti is something better than 2.3.4 I'll try it on my P1000N.
hi could you post de tv app?
davioxx said:
hi could you post de tv app?
Click to expand...
Click to collapse
Just the TV app won't work. You will need the entire ROM and P1000L model.
santroph said:
A leaked GB version for L/N or just L?
If it has TV support I think it is for the L version. But which is the GB version? 2.3.3, 2.3.4 or 2.3.5?
If ti is something better than 2.3.4 I'll try it on my P1000N.
Click to expand...
Click to collapse
No, it is 2.3.3. Basically, it is P1000N version with TV support Nothing more...
Which voltage settings are you guys using ?
Sent from my GT-P1000L using xda premium
Tks, Ronis. Running your kernel for a few days now, all good. Using smoothass, smartass and lagfree, up to 1300 stable, -50mV on 1300 and -25 on the rest.
Cheers.
- Tapatalk - SGT-P1000N - Overcome Kratos -
Running this kernel as well, no issues so far! Thanks!
Sent from my GT-P1000L using Tapatalk
Donning a new name in favour of the new delicious version of Android... Welcome to the ThunderKat Project!!
Heavily based of my Flaming Monkey kernel configurations and the stock AOSP kernel source, here's my standalone kernel for the Nexus 10. I will maintain this independently.
It will always remain close to the AOSP exynos kernel for manta (Nexus 10) with a few useful tweaks and additions, but will not have any OC/UV, colour controls and any advanced customisation options. It is a stable kernel and will not have frequent updates.
This kernel uses the AnyKernel method and is ROM independent. I have tested this on 4.4 (Stock & AOSP) based ROMs.
Features:
1. Linux Kernel 3.4.39.
2. Based on AOSP KitKat MR1 kernel source for exynos/manta.
3. Built using the Google ARM GCC 4.8 toolchain with -O3 CFLAGS & AFLAGS optimisations & ARM Cortex A15 build optimisations.
4. Enabled Conservative & Powersave CPU frequency governors (in addition to Interactive, Performance & Userspace). Interactive set as default.
5. Preserve correct sysfs permissions on governor change.
6. KSM (Kernel Samepage Merging) support.
7. NTFS, F2FS, EXT4 xattr (extended attributes) support.
8. Networked file systems support (NFS V3, NFS V4 & CIFS).
9. HIDRAW support (supports non-conformant HID devices).
10. Support for more input devices (keyboards, mice & joysticks) including Logitech Unifying devices.
11. Support for USB serial modems (PPPOE).
12. Support for multi-card readers (multi-lun devices). This allows you to mount multiple cards using a multi-card reader. May need an app like StickMount. (Credit @nvertigo67)
13. Removed SWAP support.
14. Removed some un-needed debugging.
15. Increased thermal throttle limits
16. Scalable CPU frequencies
Changelog [2014/08/24]:
1. Built using Graphite optimized GCC4.8 toolchain
2. Added ROW & SIO I/O schedulers
3. Set ROW as default I/O scheduler
4. Upstream F2FS changes
5. Miscellaneous I/O improvements
Changelog [2014/06/05]:
1. Update to AOSP 4.4.3 kernel source (kitkat-mr2)
2. Added F2FS filesystem support
Changelog [2013/12/15]:
1. Update to AOSP 4.4.1/4.4.2 kernel source (kitkat-mr1)
Changelog [2013/11/21]:
1. Initial release
Information:
1. Flash using a custom recovery (TWRP/CWM).
2. This kernel is ROM independent and uses the AnyKernel method. Hence it uses the current ramdisk. You may have issues if this is flashed after a kernel with a custom ramdisk. If so, reflash your ROM and then flash this kernel.
3. Needs an unlocked bootloader.
4. Make sure you have at least 50% battery charge before flashing this.
Download:
ThunderKatKernel-4.4.4-20140824 (AndroidFileHost)
ThunderKatKernel-4.4.4-20140824 (Goo.im)
Archive (4.4.x) - (AndroidFileHost)
Archive (4.4.x) - (Goo.im)
Archive (4.3.x) - Unsupported
Archive (4.2.x) - Unsupported
Source:
GitHub
Disclaimer:
While I have extensively tested this and even though it is heavily based on the AOSP kernel, you may encounter issues. I will try to help you, but I will not take any responsibility if anything goes wrong. Please exercise caution.
Credits:
Google, Samsung, CM, AOKP, PA, ktoonsez, morfic, franciscofranco, Goo.im, AndroidFileHost
Reserved. Just in case
craigacgomez said:
Reserved. Just in case
Click to expand...
Click to collapse
Very cool! I will be trying this tomorrow, will have time to play with it. Nice to see KSM in it.
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Wow, great news, thanks craig!
brGabriel said:
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Click to expand...
Click to collapse
Thanks...and yes, I will be renaming my ROM and kernel to something more... well, appealing... when I restart the ROM project...
Once I'm at 50% I'll be all over this like a rash
Sent from my Nexus 10 using xda premium
Great job, runs great! Only issue is it defaults to cfq scheduler on boot even when I have it set to run deadline.
More of a preference than an issue.
This kernel is really good, I was very impressed by your previous Rom and look forward to the new Rom you said will be released later in the year (hopefully!). Your hard work is much appreciated. Using your kernel with Carbon Rom right now and it seems very stable.
Sent from my Nexus 10 using XDA Premium HD app
Yep, snappy, snappy!
Sent from my Nexus 10 using Tapatalk HD
this kernel works best on my N10. no reboot, no SOD and no battery drain.
my tablet is 10 days up without a single problem or recharge! :good:
i hope it will be continued in the future!
Yes, I will continue supporting this kernel... though there will not be many updates... the aim to to remain close to AOSP, yet provide some useful tweaks and additions... I will be building a newer version soon (having problems with the cross compiler on my work laptop, else I would have done it today)...
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
teodor_ch said:
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
Click to expand...
Click to collapse
Yes, this will work fine on stock...and you can easily revert back using the boot.img from the factory images provided by Google...
Updated release in OP...
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
I just installed the kernel, very smooth, I was having shutdowns on Trinity latest and RootBox. Hopefully is not a ROM problem and this kernel fixes it, I really like RootBox.
Thanks for the awesome work and support.
Erik
situman said:
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
Click to expand...
Click to collapse
I have yet to incorporate the updated wifi and gpu kernel level drivers... I will be working on these soon...
Anyone here with sufficient kernel knowledge to merge the updated mali graphics drivers (http://malideveloper.arm.com/develo...n-source-mali-t6xx-gpu-kernel-device-drivers/)... There are a few updates that are beyond my kernel & C/C++ capabilities... like osk has been replaced by kbase... Please PM me if you can help!! Thanks!
Great work on this kernel! First time reaching 9 hours on screen time. Paired with Mr Robinson AOKP.
Hey Everyone,
I'm by no means a pro at kernel building but I've put lots of effort into these kernels so I thought I'd share them with you. The Uber kernel will always be updated to the latest Kernel version and will be overclocked to 1890 MHz or 1998 GHz (2 GHz) you decide which option you are willing to do. Unlike some of the other T-mobile Galaxy S II Hercules developers out there, I actually have a Galaxy S II and plan on having it until Summer 2014. This means that EVERY KERNEL I POST HAS BEEN TESTED AND IS WORKING although it might not be perfect (few things in life ever are).
Even though I don't post anything unless it works I still don't want to be liable for user errors. In other words, if you flash one of these Kernels your warranty is void and I AM NOT RESPONSIBLE for any data loss or bricked devices etc. A Clean install is ALWAYS recommended. That does not necessarily mean you can't install these kernels on you current build it just means that you might have problems if you do. Recently apps have been getting corrupted for whatever reason whether on Stock or AOSP and in most cases they cause RRs and SODs. If you find yourself in one of those situations a clean install is the easiest fix. If you want to try and save you apps then connect to you phone while in recovery using adb. Then type adb shell. Now once you are in that shell you can run this command to fix your apps "e2fsck -yfDC0 /dev/block/mmcblk0p25" it could take anywhere from a few minutes to an hour depending on the state of your apps.
[AOSP 4.4.x UBER KERNEL LINK]
UBER 4.1 - 1.89 GHz RELEASE for AOSP 4.4 KitKat
UBER 4.1 - 2 GHz RELEASE for AOSP 4.4 KitKat
All old Kernels can be found on Dev Host via this link (be careful you read file names and descriptions carefully if you choose to take a peek around) http://d-h.st/users/Cl3Kener/
Installation Instructions
**** IMPORTANT!!! USE TWRP 2.6.1.0+ for 4.4 kernels!!! Failure to do so may result in bootloops due to changes made to TWRP to accommodate SELinux in 4.4 ROMs (Links include flashable TWRP installation zips credits to meekrawb. Just flash them in your current recovery! ) ****
1. For best results a install these kernel after a fresh ROM install (although it still should work if you don't do that)
2. Reboot into recovery (MAKE SURE YOU USE THE RIGHT ONE!!! (See red print above))
3. Flash Kernel Zip
4. Reboot and let Settle for ~10 minutes
5. Install Trickster MOD from the App Store for access to all of the options.
6. Change the settings to something other than INTERACTIVE (Especially if you run it with BFQ it will give you the worst screen lag ever). Then enable "Set at Boot" and push the check mark button at the top right hand portion of the screen or else you will lose your configurations.
7. Enjoy!!!
Error Reporting
I am always open to hearing about your errors although just telling me something went wrong without giving me details does me absolutely no good. So here are my expectations if you do want to complain about something not working:
1. Please list the ROM you are using,
2. The IO scheduler you were using
3. The CPU governor you were using
4. The CPU frequency range (192/1080 etc)
5. What you have done to attempt to fix it.
6. If you were able to simulate it again using the same settings.
7. Anything else you think is applicable to the issue
I would also hope that you would consider trying some of the following things to fix your issue before you ever report it because most of these things will fix the problem without me even having to change a thing.
1) Fix file permissions using a program that does a thorough job. I recommend using the fix file permissions in ROM manager because it is the best I’ve seen. For the record, I don’t actually use ROM manager for anything other than fixing permissions. Please consider trying this first because it tends to fix most of the FC/RR/SOD errors you might have.
2) Make a backup and install a clean version of the ROM you are running and see if you are still experiencing those same errors. You may have corrupted files if you’ve been dirty flashing.
3) If that doesn’t solve it, redownload and reflash, maybe something got corrupted but it still managed to flash. This happens sometimes and I can cause you grief.
4) For advanced users pull a logcat. I know not everyone knows how to do this but you can learn if you check out this OP or other ones like it
SPECIAL THANKS TO:
Android88 - because he is awesome and encouraged me to create this thread!
Samsung - for the source code to build these Kernel (and for making the phone)
Ayysir - for his wonderful tutorial on making a bash script to build kernels and for helping me out all of the time with everything!
Elbermu - For Bringing Thermal and Sweep2Wake to Hercules and for the help!
Bmg002 - For his extensive work fixing/rewriting my init.d scripts
Gruntparty - For completely redoing/fixing the build.prop injector I use for my AOSP Kernels
I Am The Frost - For being my first and best tester on xda. He's debugged several issues in these kernels for me
UBER Kernel Repositories can be found at https://github.com/Cl3Kener/HERC-KERNELS and are properly labeled for your convenience (see the branches)
Informational Links
Here is a fantastic guide on "Innards" of Kernels
Optimizing Linaro Keychains
Building a Bash Script to make Kernels
JOIN MY GOOGLE COMMUNITY IF YOU WANT INSTANT UPDATES ON ANY OF ANDROID STUFF I DO.
Reserved!
XDA:DevDB Information
[KERNEL][AOSP 4.4.x][2GHz/1.89 GHz] UBER 4.1 | LINARO 4.7.4, a Kernel for the T-Mobile Samsung Galaxy S II
Contributors
Cl3Kener
Kernel Special Features:
Version Information
Status: Beta
Created 2013-12-02
Last Updated 2014-01-30
Changelogs
Changelogs
Changelog UBER 4.1 Release
- ONLY FOR ANDROID 4.4.2 CM 12/16 Nightlies and beyond!!!!
- Kernel Version 3.0.101 - Linaro 4.7.4 2013.12
- USB fastcharge
- MORE TCP Options "Veno as default
- Fsync toggle - disable for better performance but beware that if your phone crashes you will lose data.
- Overclocked CPU 1890 or 2GHz/ GPU 3D = 320 2D = 266
- IO Schedulers - cfq, bfq, row, noop, deadline, sio, vr, FIFO, and zen
- CPU Governors - intellidemand, interactivex, lazy, wheatley, smartass, badass, lionheart, minmax, fantasy, savagedzen, scary, HYPER and samsung.
- Frandom Lag Reducer
- Smaller sized kernel due to xz compression.
- CPU link - elbermu
- Sweep2wake - thanks dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- Thermal - thanks once again to dennis rassmann (@show-p1984) for his awesome code and elbermu for modifying it to fit this device!
- IO Booster
- CPU Power - Vincent Guittot
- Frontswap Support
- Google "Snappy" compression/decompression
- KGSL GPU Control - carvsdriver
Additional Info
Terminal commands to enable/change a kernel features if you are don't like kernel tuning apps
Fsync
To enable - echo 1 > /sys/module/sync/parameters/fsync_enabled
To disable - echo 0 > /sys/module/sync/parameters/fsync_enabled
USB Fast Charge
To enable - echo 1 > /sys/kernel/fast_charge/force_fast_charge
To disable - echo 0 > /sys/kernel/fast_charge/force_fast_charge
Set Thermal Values
Go to /sys/kernel/msm_thermal/conf/ in a root file browser and change the values
Set MPDecision Values
Go to /sys/kernel/msm_mpdecision/conf/ in root file browser and change the values
Disable CPU Link
echo 0 > /sys/kernel/cpu_gov_sync/force_cpu_gov_sync
Recommended CPU Govs by Category
For Performance
Performance Governor - Full OC
HYPER - full oc
Lionheart - full oc
For good battery life with decent performance use
Intellidemand
Interactivex
Ondemand
Samsung
Lazy
Moderately Conservative
Badass
Conservative
Wheatley (debatable could be in the above category)
Very Conservative
Powersave
SavageZen
not sufficient info? checkout out this op
Sweet! New kernel!
Sent from my SGH-M919 using Tapatalk
Sweet! Will try this out right now :good:
Flashed beautifully thanks @CI3kener
Sent from my SAMSUNG-SGH-T989 using Tapatalk
gotta love the uber, thank you kener
Sent from my SAMSUNG-SGH-T989
Thank You !
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
JNMM said:
Will this work on alpha 3??
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Yes ?
Sent from my SAMSUNG-SGH-T989 using Tapatalk
3 New Performance Boosters
Hey Everyone,
For those of you who haven't heard I've been using "Koding" as my new kernel build server. Space is very limited with my free account but if you'd like you can click here and signup to help me get more free space. You'll also find that you can learn how to code just about anything (java, html5, php, to name a few). Many developers and adding tutorials and sharing their projects so if you are interested in that stuff make sure to sign up!
I've made two nightlies this morning which need testing. For those of you who were around for my 4.3 you might recall that somewhere along the line there was suddenly a curious SD Card Mounting/Unmounting that would happen after unlocking the phone. I had made so many commits in such a short time frame that I was unsure which one caused the error. I've gone back and added my top three performance improving commits from the questionable series to see if any of these three commits caused the error (I certainly hope they did not, I really hope it was caused by the LZ4 compression and not the performance boosters). Let me know if you see any problems as you use these nightly kernels!!! Remember these are for 4.4 ONLY!!!
Here are the links!
UBER 1.89 GHz
UBER 2 GHz
Cheers!
Cl3Kener
just to let you know i have not been getting the sd card error on the 4.4 uber
Signed up on Koding maybe you can teach me a thing of two (^o^)
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Confirmed working on almites cm build
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
BETA2 For 12/16 CM Nightlies and Beyond
Hey Everyone!
Well Team Chopsticks finally got video working although from what I can tell all of the work was actually all done by our very own @bryan2894 who went and found the patches that fixed the video!!! Great work @bryan2894!!! Part of this video fix included the kernel so here is an updated kernel with the patch needed. This kernel will only have fixed video on CM 12/16 nightlies and beyond. I bet it might work with earlier but you might as well update if you are a CM user so what's the point?
Anyhow, enjoy the updates!
Cheers!
Cl3Kener
PS since I know someone will ask, This actually does work great with the 12-14 HellKat build since it also has working video because we grabbed the patches from CM before they were merged.
Sent from my SAMSUNG-SGH-T989
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
That stuff is nonsense. The latest TWRP in fact is much better for this phone and flashing this or any other ROM here IMHO. I tested both CWM and TWRP on more than one occasion and results were identical. For me TWRP is also much easier to get into when you have an issue with a new ROM booting and you need to get into recovery via the power & volume up buttons.
syan8182 said:
Question: for official CM 11 update, i am currently using recovery CWM 6.0.3.7, because CM officialssaid so or phone will run into problems. but this kernel requires TWRP, i am wondering can i update CM 11 nighlies with the given TWRP recovery?
Please advise. Thanks.
Click to expand...
Click to collapse
I've flashed CM11 (my builds) about 10 times in the last month and have been using TWRP 2.6.1.0 since Sept. without issue.
Just don't try to flash TWRP from within GooManager, either flash from recovery or use Odin (best).
Since the video recording is working now I moved to CM11 using the @Almite (Rom) and @Cl3Kener (Uber 2GHz kernel) and I can tel you this is solid Rock combination in performance and stability even those are still in Nightlies/Beta so thank you all for this amazing team work...
Is it possible to add the BLN notification (I know some don't like it but usually this the feature can be disabled)
Thanks
Overview:
This is a custom kernel based on Omni sources for our legendary i9000. This is only for 5.1.1/6.0.1 roms and no other version of android will be suppported
It works on any Omni based 5.1.1/6.0.1 rom.
>The zip you will download is flashable via recovery.
>> Use devil kernel manager or NStools to edit the kernel settings.
Features : - Multiple CPU governors (lulzactive, smartassV2, wheatley, lagfree, ondemandX)
- Tweaked smartassV2
- BFQ, Zen, VR & SIOPLUS I/O schedulers added
- Tweaked VR
- New TCP algorithms (westwood is default)
- Bigmem, up to 430mb
- CMA (MM only for now)
- Kernel compressed with XZ
- Compressed initramfs
- Dynamic page writeback
- Dynamic Fsync
- Custom ARM & INT voltages
- Voltages fixed for more stable OC
- Selectable GPU OC (not working properly for now)
- Fast charge
- BLX
- Live OC
- FULL O3 optimisations
- Call volume hack
- Touchwake
- BLN
- Zram
- Swap / Zram optimisations
- LMK tweaks
- SLQB memory allocator
- NEON optimized crypto routines
- Voodoo color
- SquashFS support (module)
- EXfat support (module)
- 720p patched bigmem libs
- Built from the latest Omni source
- Built using custom Cortex-A8 optimized UBERTC 5.3 toolchain of @Cl3Kener
Todo:- Backport more things from higher linux versions and fix remaining conflicts ...
- Fix GPU OC ... Well we have live OC, not worth the time i guess.
- Make CGROUP_TIMER_SLACK work
- GPU driver to DDK [email protected]
- Make a better (and more fancy) updater script
- Fixing the remaining issues [...]
What I wont do : - Enable TV out
- Upgrade linux version
- Add useless CPU governors or I/O schedulers
- make your phone as fast as a i9500
Please use it at your own risk! I am not responsible for any damage that may occur to your device.
Download :
Latest android 5.1.1 kernel :
Kernel_ION.zip MD5 : 2060f96fbffc98a1f2fae9108066b69a
http://www50.zippyshare.com/v/zVr8YvZ4/file.html
Latest android 6.0.1 kernel :
Kernel_CMAEXP.zip MD5 : 236f89a961b559c666a1c064aaccd728
http://www43.zippyshare.com/v/Yxm6WDuA/file.html
Old versions :
https://mega.nz/#F!3x5VTbiQ!87aMOGoDBuQZmiELhKlUkQ
Thanks:
@humberos
@DerTeufel1980
@kasper_h
@Alberto96
@Ezekeel
@xc-racer99, for his help on setting up my Github
@(°_o)
Anyone else who helped me
Source Code:
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries
Custom built UBERTC with A8 optimisations : https://bitbucket.org/Coldwindofnowhere/
XDA:DevDB Information
Omni kernel, Kernel for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99
Version Information
Status: Beta
Created 2015-10-02
Last Updated 2016-03-06
>If you like my work, hitting the thanks button won't hurt you<
good luck
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61937705
Gesendet von meinem SM-G900F mit Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Coldwindofnowhere said:
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Click to expand...
Click to collapse
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
falconscrest123 said:
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
Click to expand...
Click to collapse
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
falconscrest123 said:
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
Click to expand...
Click to collapse
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
431mb ram possible??
xc-racer99 said:
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
Click to expand...
Click to collapse
Im not sure either because i have all govenors mentioned above while i can tweak everyone of them using kernel aditor apk and plus i can also toggle fast charge which wasnt present in omni rom for the vibrant. I have uploaded some screenshots and it is from code rom.
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
Sure, i'll set a github soon, but trust me there are only minimal changes to the origianl code (even if adding liveOC seems harder since i only got build errors xD).
Btw i won't build anything this week, i'm busy with exams.
Github is up !
Coldwindofnowhere said:
Could someone help me to setup my github please ? (PM me)
Click to expand...
Click to collapse
Check your PM, let me know if you need more help.
Hey.
I tested it on 5.0.2 . stuck on bootanimation. Better mention that its for 5.1.1 .
Can you add support or please tweak it for 5.0.2
Now iam using RR lp 5.0.2
I removed some apps. And it have the same apps like omni. Its works faster than ever. Working theme engine. Only removed music and added apollo.
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
falconscrest123 said:
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
Click to expand...
Click to collapse
That's weird, i haven't changed anything concerning the audio in the kernel. You're using it on a vibrant right ? This might be the problem. I'm gonna try to reproduce this bug on my i9000 and see ....
Edit: try this http://www42.zippyshare.com/v/aZ6XgBlE/file.html
DO NOT FLASH, IT DOESN'T WORK (except if you want to give me a log or if you're really curious)
Any feedback on the vibrant version ?
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
The kernel didnt even flash no errors nothing whenever i flashed via twrp it would instantaneously reboot to recovery. Thanks again for atleast trying to fix the issue.
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
Bro. Can you add fast charge and the governers in omni kernal 5.0.2. Please
Thanks
*** This kernel is now end-of-life, not supported and developed anymore !!! ***
Hi all,
some of you know me from the other OnePlus or Samsung devices areas, where I provide my kernels already for more than three years to OnePlus 3, 2, one and X, 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, good existing kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
To add: An open beta (aka community build) is NOT an official build supported here. If you use a community build and have issues, don't complain or even report. I am not merging any kernel changes from open betas into my kernels !!
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
This kernel is ONLY compatible to OxygenOs stock, nothing else !!!
If you are using a custom rom that bases on OxygenOs, it might work. However, if it does not work, do not expect me to do tweak to make the kernel running with your favorite rom. I would not do it - my one and only reference is OxygenOs stock.
It is not supposed to be compatible to CM, HydrogenOS etc.
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Installation
Read the install instructions in the support section on the Boeffla Site.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (outdated at the moment).
Click here to learn about using the config app (outdated at the moment).
I will refuse to give support if you do any undervolting/overclocking and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for OxygenOS 4.x.x kernel - Click here
Change log for OxygenOS 3.x.x kernel - Click here
Known issues
none
Features
Note: This kernel only runs on OOS 3.x.x for the OnePlus 3T - nothing else !!!
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.4.21 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Dash charging fully supported
The two CPU clusters (big and little cpu) can be configured completely separate in terms of min/max frequencies, governors and CPU core profiles
Additional governors: Impulse, zzmoove, elementalx, conservative, ondemand, blu_active
Additional schedulers: fiops, bfq, sio, sioplus, fifo, vr, tripndroid, zen, maple
No CPU overclocking and voltage interface, no GPU overclocking and voltage interface
USB charge rate bumped up to 900 mA
Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time)
Boeffla touchkey LED control (LEDs fully off, LED on screen touch, configurable duration)
CPU core profiles to restrict number of CPU cores being used (the OP3 does not hotplug based on load)
Notification LED control (effect + speed for blinking/fading, brightness for continuous notification like battery charging etc.)
Boeffla-Sound engine: Headphone volume and speaker volume (only lowering volumes for speaker)
Dynamic FSync (activated if screen on, deactived if screen off), configurable
Input boost frequencies and duration configurable per CPU cluster, input boost switch
Show CPU frequency usage per CPU and frequency in Boeffla-Config
Show GPU frequency usage per frequency in Boeffla-Config
KCal V2 Color control
Display backlight limits configurable (to avoid display brightness gets too low in some situations)
Display backlight dimmer
Swipe2wake gestures
Control haptic feedback of gestures (except fingerprint)
Haptic feedback intensity control
Swipe2sleep gestures
Boeffla generic wakelock blocker V1.1.0 (documentation)
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (only when data volume is formated with ext4, stock default is f2fs)
Kernel logger (dmesg) configurable
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Many additional TCP congestion algorithms available
Entropy values configurable
Hardware touch keys are locked as long as screen is in use (touched) for better usability
Swap supported
Doze mode switchable
Verifiedbootstage flag remove to avoid triggering safetynet
Various minor kernel tweaks
Doze mode configurable in Boeffla-Config
Full selinux strict support (switchable to permissive on demand)
Show speedbin information (PVS level) in Boeffla-Config app
init.d support (in /system/etc/init.d - set correct permissions!)
Entropies configurable
Automatic EFS backup
Integrated full busybox 1.27.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
Security patches included, which are not in the official repo
Google gcc 4.9 toolchain (64 bit) used for best stability
Always based on latest OOS kernel sources (https://github.com/OnePlusOSS/androi...neplus_msm8996)
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the kernel only if you are running a compatible rom !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
You need at least version 2.4.21 or higher for the OnePlus 3T 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
* Osm0sis
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change log:
OOS4
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos4xx/changelog.htm
OOS3
http://kernel.boeffla.de/oneplus3t/boeffla-kernel-oos/oos3xx/changelog.htm
--- Reserved 2 ---
Here we go!
First beta is online for you guys.
As always, find everything on www.boeffla.de
And just to stress it again: It is the VERY FIRST beta, so expect bugs!
Have fund
Andi
nice! downloading right now!
so happy to see you again andi! your kernel was simply the best on my galaxy S5 and I missed your affords in my S7!
so happy flashing to everyone!
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again, and I think Boeffla provides the best support of all. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
PS: I was probably the first person to like and subscribe to this thread. (within 5 minutes of thread creation)
Edit: Flashable stock kernels? Perfect, thank you @Lord Boeffla ! Does it revert any custom kernel to stock kernel?
Been with Boeffla since S3 and via OPO this will be my third phone with the kernel.
Thanks!
Skickat från min ONEPLUS A3003 via Tapatalk
knpk13 said:
After jumping from kernel to kernel (since there are many more kernel devs here than on the OP2) with various minor niggles, finally back to the one I feel fits my needs best. This release brings me relief, as now I don't have to go kernel hopping again. No bugs so far, multirom boot menu works, everything runs great.
Out of curiosity, is the kernel systemless? (Can I revert to stock by just flashing stock boot.img from latest ROM zip?) I ask because flashing the entire stock ROM takes a long time, and the TWRP loading time is also long.
Click to expand...
Click to collapse
This is not possible on OOS in a clean way.
The kernel comes with modules which are placed in /system/lib/modules too.
So only flashing stock boot.img would not replace the kernel modules by stock ones. So it is only a "half-good" solution.
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi
knpk13 said:
Also, ext4 tweaks is not hidden for me and is enabled when a profile is reset to default settings. I'm on the default filesystems. (f2fs data, ext4 everything else)
Should I leave ext4 tweaks on or off?
Click to expand...
Click to collapse
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
EDIT: Just tried it - cannot replicate that. Maybe your /data partition is indeed formatted in ext4???
(you can check by firing the following command in a terminal: mount | grep data)
Andi
Lord Boeffla said:
This is something I might need to correct in the app then. Leave them off, there is no ext4 anymore on /data volue with stock OOS (but the f**inkg f2fs).
I will look into that over the next days then.
Andi
Click to expand...
Click to collapse
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off automatically every time, so I guess it's working fine. Yes I'm sure I'm on f2fs.
knpk13 said:
I reopened the app, and ext4 tweaks was off. But when I click on reset profile settings, it turns on. But on reopening again, it turns off, so I guess it's working fine.
Click to expand...
Click to collapse
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I love ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi
Ok guys, evening hours here in Germany.
I am off for today. If you have any questions, you can also move over and read in the OP3 thread. The devices are - concerning my kernel - 99,99% the same.
So you would most probably find all answers to your questions already there.
Tomorrow I will catch up again.
Andi
Lord Boeffla said:
Yep, and also means, your data partition is not formatted with f2fs (my op3t came with /data on f2fs)... lucky you. I live ext4 much more, I even consider reformatting /data with ext4 soon, hehe.
Andi
Click to expand...
Click to collapse
I'm sure I'm on f2fs. Even TWRP says I'm on f2fs. 3T comes stock with f2fs. This is the output of mount | grep data, but since I'm using magisk I think the output has many partitions and I can't make sense of it.
I think the ext4 tweaks toggle is working fine since it reverts to off automatically when the app is restarted. Thanks!
Here is the output: https://hastebin.com/iwokiramek.hs
Welcome to the 3t Lord Boeffla.. Enjoyed having your kernels and support on the s5 when I was running that phone.. Look forward to the same here..
Sent from my ONEPLUS A3000 using Tapatalk
Lord Boeffla said:
But, as most of the time, I have a solution for you
Look here: http://boeffla.de/index.php/downloads/downloads-general
Flashable stock kernels for the 3T, which also include the modules.
Guess this is what you need.
Andi
Click to expand...
Click to collapse
nice, been waiting for this since day one. :good:
So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
inzaghi75 said:
So it is not oos 4.0.0 compatible
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
No. OOS 4 has not yet been officially released and no kernel source has been released.
christmas is here since andi is our santa.
welcome to the 3T world.
loyalists like me have been waiting for you perhaps since the device was launched.
glad OnePlus and XDA did such an awesome thing to distribute devices to devs.
been following your work for a while now.
your kernel turned my OpO into a beast.
just flashed onto my 3T.
will report issues as and when(and if) I can find them.
cheers
Glad to see you here Andy!
finally you will develope on 3T:good:
Glad to see you here Andi:victory:
I use your kernel since Galaxy S3, also flashed it on my opo and my wife's opt.
:good: Now the kernel it's running very well on my new op3t.