Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ
mzakharocsc said:
Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ
Click to expand...
Click to collapse
I'm sure you know this already, but there's a magisk module that does that already.
If I was to build a kernel I would try and definitely build something that has smoother performance or slightly better battery life.
Keep up the efforts. It is a shame there are no custom kernels for the phone...
Burt Squirtz said:
I'm sure you know this already, but there's a magisk module that does that already.
Click to expand...
Click to collapse
If you are talking about this: https://github.com/evdenis/selinux_permissive , then having tried it it did not work. On their own XDA thread, they state 'The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels'. Unless I am missing something here?
Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.
mzakharocsc said:
Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.
Click to expand...
Click to collapse
commenting that line will brake your image, we need llvm to make bootable kernel.
afaneh92 said:
commenting that line will brake your image, we need llvm to make bootable kernel.
Click to expand...
Click to collapse
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.
mzakharocsc said:
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.
Click to expand...
Click to collapse
By reading Makefile you can find it there.
afaneh92 said:
By reading Makefile you can find it there.
Click to expand...
Click to collapse
Yeah, I read the makefile. LLVM flag is supported there, but unset/unused by default, resulting in corrupt images. and you have to somehow know that you need to set it externally.
If someone build a good custom kernel wich improves battery and performance i will donate 100 usd
I want custom kernels too.
Would it be possible to make a bounty?
I'm interested in battery, hackability, booting time, stability and performance.
songoku1 said:
If someone build a good custom kernel wich improves battery and performance i will donate 100 usd
Click to expand...
Click to collapse
Are there some official XDA bounty program for this stuff?
timofonic said:
Are there some official XDA bounty program for this stuff?
Click to expand...
Click to collapse
Sadly no on my oneplus i use arter kernel and i absolutely lovibg it. Sadly for my s21u there isnt one :/
What's more important now is to stress samsung's opensource service to release the AUG4 kernel source
DaReDeViL said:
What's more important now is to stress samsung's opensource service to release the AUG4 kernel source
Click to expand...
Click to collapse
Already requested it.
interested in a custom kernel also, it's already a very good device but battery life needs to be better
afaneh92 said:
Already requested it.
Click to expand...
Click to collapse
Got it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
I will rebase my kernel soon
Ok
DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
Hope we will see a custom kernel soon
Any news?
Related
Hi everyone.
As you all know, Samsung distributes source code as tarballs which isn't the best way to redistribute kernel source code
git is the best modern way to work with Linux Kernel sources, designed by Linus himself in this purpose.
So, i made an organization on github for that.
https://github.com/sgs3
And yea, that means source code has been released, head on to http://opensource.samsung.com/
Kernel Sources :
https://github.com/sgs3/GT-I9300_Kernel
Branches :
master :- branch you should use(for developers), will contain fixes and more in the future (currently identical to stock_update4)
stock :- Kernel sources from GT-I9300_ICS_Opensource.zip, unmodified
stock_update1 :- Kernel sources from GT-I9300_ICS_Opensource_Update1.zip, unmodified
stock_update4 :- Kernel sources from GT-I9300_ICS_Opensource_Update4.zip, unmodified
If anyone wants to commit any fixes / anything else, fork and shoot a pull request
How to Build :
Get teh sauce:
Code:
git clone git://github.com/sgs3/GT-I9300_Kernel.git
cd GT-I9300_Kernel
git checkout master
Tell it to use our config:
Code:
make ARCH=arm CROSS_COMPILE=/path/to/toolchain m0_00_defconfig
Teh real build:
Code:
make CROSS_COMPILE=/path/to/toolchain
or
Code:
make -j `cat /proc/cpuinfo | grep "^processor" | wc -l` CROSS_COMPILE=/path/to/toolchain
The compiled kernel is arch/arm/boot/zImage
Was about to post this
Will start compiling and have a kernel up and running soon I hope. This time in contrast to the S2, it's time for serious developing.
Here's a direct link to the S3 files: http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-i9300
This is great news guys,
lets hope that we will also have a proper CWM recovery soon.
stickied
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
EDIT: this is the patch in question: http://git.kernel.org/?p=linux/kern...it;h=371a689f64b0da140c3bcd3f55305ffa1c3a58ef. Apparently Sammy took this out again in their sources (according to somebody else, I haven't had time to confirm yet, but I can see the boot partitions do *not* appear on my device), they may have bastardized it further ...
Chainfire said:
stickied
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
Click to expand...
Click to collapse
No CF-Root Kernels for the i9300?
Toss3 said:
No CF-Root Kernels for the i9300?
Click to expand...
Click to collapse
Well it's not needed as much due to the separate recovery, but if there's demand, I'll build CF-Root's... but those are based on Samsung binaries, not source.
Great! I'll go through this when I get the time.
Chainfire said:
Well it's not needed as much due to the separate recovery, but if there's demand, I'll build CF-Root's... but those are based on Samsung binaries, not source.
Click to expand...
Click to collapse
Of course I want a CF kernel
pglmro said:
Of course I want a CF kernel
Click to expand...
Click to collapse
I think everyone of us want a CF-Root-Kernel
Roughnecks said:
I think everyone of us want a CF-Root-Kernel
Click to expand...
Click to collapse
I don't really see the point why we should make that. I have flashed cwm with Odin and then the SuperSu cwm flashable zip available here on xda. Then installed busybox installer from the play store. Much easier to do as letting Cainfire always compile a cf-root kernel for us.
L
great seeing some a class developers here!!
thanks for opening this thread..
and good to know ya'll have a s3 aswell..
grtz!
Great news , hope to see some nice custom kernels soon!
Kernel dev's:
Please share your github if you start then
what?update#1 is already out?
Hope Samsung release a cleaner source this time
sakindia123 said:
what?update#1 is already out?
Hope Samsung release a cleaner source this time
Click to expand...
Click to collapse
Looks like they messed up the first zip, so the quick update
Only change i can see from stock to stock_update1 is the changing of file mode from 0755 to 0644
Samsung releases source code for the Galaxy S III
UPDATE 1 is out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Chainfire said:
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
Click to expand...
Click to collapse
They seem to have hacked it out pretty crudely (certainly the korg patch won't apply cleanly). No device here, can't really test this, but the attached patch should properly allocate any mmc boot partitions.
A couple more patches before I rm
No device here and no idea if I'll ever get one, but I thought I would post couple more cosmetic (yet instrumental) patches for your tree so that my last 15 minutes wouldn't be in vain.
#1: m0_00_defconfig: Run through menuconfig;disable GCC strict checking. Otherwise I get a lot of noise with codesourcery toolchains
#2: Add .gitignore files from korg trees.
Take care
Anyone else get compilation error due to SVN_REV variables in these Makefiles:
drivers/media/video/samsung/mali/Makefile
drivers/media/video/samsung/ump/Makefile
I comment out the lines and replaced them with
Code:
SVN_REV=:0000
I used 0000 because of the comment in the Makefile.
Now, it compiles without error (though untested since I don't own S III)
Nope ... didn't get those errors!
Lollipop kernel: this post Moto G 4G peregrine only
Mog shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock ROM (UK ONLY!)
Tesco GB 4.4.4 ROM mirror here May be useful to UK users who want to flash back and re-download the OTAs
Stock 5.1 Kernel zip
Thank user J0kker then download in the post below his
Final KitKat zip: this post
Source code: https://github.com/bedalus/moggy/
Toolchain: http://forum.xda-developers.com/showthread.php?t=2098133 4.9.3 a7 optimised version
Holy smoke.... it's bedalus!:highfive:
@hekomat Please do not swear on XDA.
From you friendly moderator, @Toledo_JAB
bout 2 sound like an jerk...but...can you build one for the falcon too?
thanks sooo much
Sorry for asking but what are the actual changes from the stock kernel?
CJMom said:
what are the actual changes from the stock kernel?
Click to expand...
Click to collapse
So far the only changes are using an up-to-date linaro toolchain, removal of some debug logging, and switching the IO scheduler to cfq.
I saw there was no option for peregrine users so I thought I'd make one. At the moment the repo is very clean. It would make a good jumping off point if any other devs want to fork it and add fun stuff. I personally prefer to keep it simple.
OldYellowBricks said:
can you build one for the falcon too?
Click to expand...
Click to collapse
There's already a few kernels for falcon. What is it you're hoping I'll offer?
bedalus said:
There's already a few kernels for falcon. What is it you're hoping I'll offer?
Click to expand...
Click to collapse
To have a stock kernel built with latest linaro? Currently trying to do it myself for falcon, but I've just encountered the Motorola module whitelisting (WTF?). Never seen that before on other devices...
knizmi said:
To have a stock kernel built with latest linaro? Currently trying to do it myself for falcon, but I've just encountered the Motorola module whitelisting (WTF?). Never seen that before on other devices...
Click to expand...
Click to collapse
I'll happily talk you through it. How far are you through?
Oh, and you probably forgot to strip your wlan.ko, it has well over 30 MB I am surprised it even loads on peregrine.
---------- Post added at 10:11 PM ---------- Previous post was at 10:06 PM ----------
bedalus said:
I'll happily talk you through it. How far are you through?
Click to expand...
Click to collapse
Everything is allright - the kernel boots and everything works fine, the only problem was that I couldn't get wlan.ko to load. I didn't know about the whitelist thing, though. You can imagine my face when I looked at dmesg.
I should have some more time in an hour or so, if don't get it running by morning, I will PM you. Thanks for the offer.
OK, I've done it by adding
Code:
chmod 0666 module_hashes
echo ee04251847ff70190bfec61b19802c19afe29a16 >> module_hashes
chmod 0400 module_hashes
to your repack-ramdisk.sh. Seems a little dirty, but works
The other modules will have the same problem I believe. Unless I want to add their SHA hashes the same way, what is the correct way to bypass/update that whitelist? You don't mess with that file anywhere in your build or install scripts. Gonna try deleting it, but you don't do that either...
knizmi said:
OK, I've done it by adding
Code:
chmod 0666 module_hashes
echo ee04251847ff70190bfec61b19802c19afe29a16 >> module_hashes
chmod 0400 module_hashes
to your repack-ramdisk.sh. Seems a little dirty, but works
The other modules will have the same problem I believe. Unless I want to add their SHA hashes the same way, what is the correct way to bypass/update that whitelist? You don't mess with that file anywhere in your build or install scripts. Gonna try deleting it, but you don't do that either...
Click to expand...
Click to collapse
I've seen your new falcon thread congratulations on making it work. Thanks for the credit.
To circumvent the whitelist, you need to disable it in the kernel config: see here
You're right about the module stripping. I tried doing it in the build script, but it was the wrong approach. This commit works. Thanks for reminding me! I've updated the download link. The zip is now less than 8MB, much better.
Love to see new stuff in our beloved 4G.
Downloading and testing it right now. Thank you.
I want to try this too.
I just need to flash it from recovery?
deleting caches is needed?
If I want to go back to stock kernel just flash boot.img from my stock firmware using mfastboot?
Thanks!
CJMom said:
I just need to flash it from recovery?
deleting caches is needed?
If I want to go back to stock kernel just flash boot.img from my stock firmware using mfastboot?
Click to expand...
Click to collapse
Yep, the zip is flashable in CWM or TWRP. Deleting caches is not needed.
To return to stock, like you say...
Code:
mfastboot flash boot boot.img
But the stock boot.img does not contain copies the kernel modules. If you intend to go back to stock, you'll need to back up the entire folder /system/lib/modules from a stock install before flashing my kernel.
Stock peregrine boot.img: http://d-h.st/yF6
bedalus said:
To circumvent the whitelist, you need to disable it in the kernel config: see here
Click to expand...
Click to collapse
Lol, how easy. Didn´t see that, thank you.
bedalus said:
To return to stock, like you say...
Code:
mfastboot flash boot boot.img
Actually, I'm not sure if the stock boot.img copies the kernel modules or not. If you intend to go back to stock, it would be a good idea to back up the entire folder /system/lib/modules from a stock install before flashing my kernel.
Stock peregrine boot.img: http://d-h.st/yF6
Click to expand...
Click to collapse
To return to stock you need both boot.img and modules. Flashing boot.img only will disable your wifi.
Flashed it and everything is OK.
Waiting for future updates and features
Hey bedalus,
Are you planning to make a CM11 version?
beeeto said:
Hey bedalus,
Are you planning to make a CM11 version?
Click to expand...
Click to collapse
No, at this time I'm planning to build what I need and share. I'm fairly sure I'll be sticking with stock 4.4.4
testing version 3: http://d-h.st/1Sn
- Got the download to just over 5MB by switching to XZ compression
- f2fs cherry-picks from torvalds git up to kernel v3.18
I consider f2fs the newest piece of the kernel, and the filesystem is always a bottleneck for system performance, being slow compared to everything else. It makes sense to apply as many improvements in this regard as possible.
The cherry-picks may have affected stability. It's always hard to tell with such a huge amount of code revision. I've seen one new bug where if there is an unexpected shutdown, this causes a kernel oops on the subsequent reboot right after the filesystem recovery. Then the following reboot works normally. No damage the to filesystem, just a null pointer dereference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOURCE
**Snapdragon™ is a registered trademark owned by Qualcomm Technologies Inc.
**Synapse™ is a registered trademark owned by @Andreilux
**(v1)Xcelerate Logo™ is created by @fareed_extreme
**(v2)Xcelerate Logo™ is created by @Sharan Narayan
XDA:DevDB Information
Xcelerate™ Custom Kernel, Kernel for the YU Yureka
Contributors
kairi_zeroblade, DooMLoRD, RohanAJoshi
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Production build 4
Stable Release Date: 2015-04-11
Created 2015-02-16
Last Updated 2015-04-11
Reserved
Short Credit list:
DooMLoRD for assisting in the compilation
Rohan Joshi, Prithvi Raju and Raj Gopi for testing
Cyanogen
ARM
Short Feature list:
Basic Governors(I won't add Ripoffs)
Built using my own GCC 4.9.x Toolchain(with fixes specifically Aimed at Cortex A53 erratas) built across the standards of Google's own Toolchain..
Simple and no fancy stuff..(more does not guarantee it's better)
Uses a simple free and user friendly application called Synapse by @AndreiLux for configuration purposes(slightly adding more functionality)
A few Notes:
Be advised that this kernel is best used "As is" i do want to prohibit the use of scripts that they say "enhances performance and battery" just use the kernel as it is..everything is managed automatically by the kernel and rest assured continuous innovations are en-route.
**Camera might be broke on OLDER CM11 and UNOFFICIAL BUILDS since this is built using the latest source from Cyanogen use this FIX
Compatibility list:
According to testers/users feedback the Kernel works on the FOLLOWING ROMS(tested)
CyanogenMod 11(Stable)
The list will grow as soon as Testers/Users can provide means and ways to make this compatible with everything..
Downloads
Grab latest Production builds here
Nice work mate :good:
BTW could have been much better if u could just left cm commits on git
so would have been easier for other devs to track earlier parent commit changes Rather than using : initial dump of Yureka source from CM snapshot 2-13-2015
Anyways no problems .....
Proud to be tester of this kernel..
working amazingly..
charging speed is double than before now..
also smoothness is awesome, thanks bro..
in call battery drain is dramatically reduced from 12% / hr to 6% / h..
will seek for further features..
does it shutdown cores when low usage ???
Not a fan of Custom Kernels, but...
but, yeah, but for the first time 'll be trying this (don't know why but I have this voice inside of me that's compelling me to try this out), hope everything goes well, will edit to share my experiences once I've used it for a couple of days, till then, thanks for this and appreciations for your efforts.
more governors please?
Thanks a lot! I had been waiting for this kind of a custom kernel!
hey, could you add smartassv2 governor to the kernel?
*downloading the kernel as i type*
Cheers!
:good: :good:
camera not working!!!!!!!!!!!!!!!!
sauravdante said:
camera not working!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Flash the updated kernel I have posted, it includes the libs, then flash xcelerate kernel, camera should work.
Op can add those libs.
No UCI support detected !
Damn ! OP enlighten me on this error when I try to open Synapse.
I'm rooted, I have the stock room that came with the cell, the ago had superuser permissions, but still I'm not able to get that app to work. Did a normal flash, booted into recovery, selected the zip that I downloaded and record again.
Googled for the error, found a post in which a guy having Xiaomi had the exact same problem, there you our someone suggested to flash normally, so that's kinda what I did, what m I missing ??
hkm93 said:
Damn ! OP enlighten me on this error when I try to open Synapse.
I'm rooted, I have the stock room that came with the cell, the ago had superuser permissions, but still I'm not able to get that app to work. Did a normal flash, booted into recovery, selected the zip that I downloaded and record again.
Googled for the error, found a post in which a guy having Xiaomi had the exact same problem, there you our someone suggested to flash normally, so that's kinda what I did, what m I missing ??
Click to expand...
Click to collapse
I am getting this. [emoji20]
hkm93 said:
Damn ! OP enlighten me on this error when I try to open Synapse.
I'm rooted, I have the stock room that came with the cell, the ago had superuser permissions, but still I'm not able to get that app to work. Did a normal flash, booted into recovery, selected the zip that I downloaded and record again.
Googled for the error, found a post in which a guy having Xiaomi had the exact same problem, there you our someone suggested to flash normally, so that's kinda what I did, what m I missing ??
Click to expand...
Click to collapse
Sudeep Duhoon said:
I am getting this. [emoji20]
Click to expand...
Click to collapse
Support for synapse is probably coming in the next builds..as I'm not familiar with the sysfs for the YU yet..I'm building this blind and with @RohanAJoshi only doing the tests for me.. rest assured its stable, fast and battery friendly..
EDIT:
I'm still looking for testers if someone is interested in hitting up to the task well you can find me on Hangouts via [email protected]
I am in pac man rom can i use this kernal?
proximity issue
Facing proximity issue after flashing this kernel.... Hope so this ll get fixed in upcoming builds nice work indeed
---------- Post added at 04:59 AM ---------- Previous post was at 04:55 AM ----------
Camera not working after flashing latest build
Been using for more than half a day. So far so good. thanks @kairi_zeroblade :good:
Testing your kernel on dumtara CM11 build.
Any possibilities of some custom governors that implement core hot plugging functionality ??
Error
satitrip said:
Click to expand...
Click to collapse
Dude, its already posted in the thread, Read first. Correct your image size, it covers my screen, seriously.
cm11 dumtara
I'm on cm 11 by dumtara. can I flash this kernel?
kairi_zeroblade said:
I'm still looking for testers if someone is interested in hitting up to the task well you can find me on Hangouts via [email protected]
Click to expand...
Click to collapse
I saw ur post regarding that, but I may not have mentioned this but I'm not so good in technical side of android. Being a java developer I never bothered about them but for the past few days I'm actually inclined towards learning android development too, say just as an additional hobby, and to my surprise it's Java too.
Now that I have already flashed the kernel, I can be of some use for sure, but conditions apply. I am not available all ( I can update you on a daily basis in between 10-11 pm IST, and on weekends if that's ok with you) the time and someone will have to guide me or provide info on what I'm supposed to do, coz I have no idea what needs to be done while testing a kernel.
Sudeep Duhoon said:
Flash the updated kernel I have posted, it includes the libs, then flash xcelerate kernel, camera should work.
Op can add those libs.
Click to expand...
Click to collapse
Thanks.. But which kernel should should I flash first and which one next.. Can you give download links pls.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
THIS DEVICE IS CURRENTLY A TESTING KERNEL AND MAY NOT WORK. BACKUP YOUR BOOT.IMG BEFOREHAND.
Click to expand...
Click to collapse
Features
Built on UBERnaro toolchain
High tickrate to avoid jitter
Lib optimisations
F2FS support
Click to expand...
Click to collapse
Installation instructions
* Flash via TWRP, or Franco Kernel Manager (needs testing for this device)
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is available at ftp://ftp.lasterhub.me.
Click to expand...
Click to collapse
FAQ
Tag me in XDA's Amazon.. oh wait. There's no group (yet?). Just PM me for now.
Click to expand...
Click to collapse
Special Thanks To
Code:
* MTK for being retarded
XDA:DevDB Information
Zest Kernel Projecc, Kernel for the Amazon Fire
Contributors
LazerL0rd, ggow, k4y0z
Source Code: https://gitlab.com/ZKP/ford
Kernel Special Features:
Version Information
Status: Testing
Created 2019-05-28
Last Updated 2019-05-29
LazerL0rd said:
Last Updated 2019-05-28
Click to expand...
Click to collapse
Nice.
May I ask for a little safety step to be added. Someone here is gonna not read and try to flash this on 'Austin'
And your anykernel.sh has device check set at NO. (do.devicecheck=0). Maybe better to make it (do.devicecheck=1)
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
newinnov said:
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
Click to expand...
Click to collapse
Austin or ford?
Rortiz2 said:
Austin or ford?
Click to expand...
Click to collapse
Ford 2015 it is
mrmazak said:
Nice.
May I ask for a little safety step to be added. Someone here is gonna not read and try to flash this on 'Austin'
And your anykernel.sh has device check set at NO. (do.devicecheck=0). Maybe better to make it (do.devicecheck=1)
Click to expand...
Click to collapse
Ah, yes. Weirdly some TWRPs react funnily to this command so on-release I always leave it off. Seems there's only one TWRP here tho. Thanks, will do :highfive:.
newinnov said:
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
Click to expand...
Click to collapse
The kernel seems to be pretty much correct, it's the flashing procedure that I'm uncertain of. It's the same base kernel @ggow uses with some building fixes and my additions. But yes, this is a development kernel until anyone can actually get it working with the patch.
LazerL0rd said:
The kernel seems to be pretty much correct, it's the flashing procedure that I'm uncertain of. It's the same base kernel @ggow uses with some building fixes and my additions. But yes, this is a development kernel until anyone can actually get it working with the patch.
Click to expand...
Click to collapse
I had a stock built kernel from unmodified Amazon source, and installed it with anykernel, before I discontinued the project. @ggow showed me up. Way up, by making his kernel free from that Amazon log feature.
Anyway anykernel flashes this device with the exploit no problem.
Think I had used anykernel 2 though. You have used 3.
I will look again, and see if I see any difference in the scripts.
EDIT:
I just tried to flash with the anykernel2 script i had used before. And result was bootlooping on the Amazon logo.
mrmazak said:
I had a stock built kernel from unmodified Amazon source, and installed it with anykernel, before I discontinued the project. @ggow showed me up. Way up, by making his kernel free from that Amazon log feature.
Anyway anykernel flashes this device with the exploit no problem.
Think I had used anykernel 2 though. You have used 3.
I will look again, and see if I see any difference in the scripts.
EDIT:
I just tried to flash with the anykernel2 script i had used before. And result was bootlooping on the Amazon logo.
Click to expand...
Click to collapse
I tried both AK2 and AK3 with osm0sis seeing no issues in my AK configuration, so it’s not that.
Yah, I think something was changed and some sort of check was added in. I think I tried dm-verity disabling too but I may be wrong. My kernel is available at https://lasterhub.me/zk.html for anyone to try though ( click menu then BETA before selecting as no release version was released yet ).
I can't get the link to work? This ded?
beynolds.rurt said:
I can't get the link to work? This ded?
Click to expand...
Click to collapse
Yes. This is dead. OP never followed up after he was told this did not work as claimed.
mrmazak said:
Yes. This is dead. OP never followed up after he was told this did not work as claimed.
Click to expand...
Click to collapse
Knew it was too good to be true
It's simple. I threw together this kernel out of necessity for micro lag fixes and better battery life.
Please expect only necessary updates.
If you have an issue, please provide a detailed report and please provide a logcat
Enjoy.
V-1.0.9 Zip download link = https://www.androidfilehost.com/?fid=4279422670115732041
V-1.0.9 Boot Image download link = https://www.androidfilehost.com/?fid=4279422670115732040
##################################
OP9R BUILD/ZIP only
OP9R-V-1.0.9-ZIP = https://androidfilehost.com/?fid=4279422670115732053
the boot.img is not pre-rooted. Please use the zip to remain rooted.
Kernel Source = https://github.com/APOPHIS9283/Singularity_Kernel
apophis9283 said:
It's simple. I threw together this kernel out of necessity for micro lag fixes and better battery life.
If you use Evolution-X this will break Fsync toggle as I opted for Dynamic Fsync instead. Past that you tell me.
Please do not expect a ton of updates.
If you have an issue, logcat or GTFO.
There is no Telegram link.
Enjoy.
Zip download link = https://www.androidfilehost.com/?fid=4279422670115706910
Boot Image download link = Coming soon.
Kernel Source = https://github.com/APOPHIS9283/Krieg_Kernel/commits/13
Click to expand...
Click to collapse
Been using this for a while and very happy with performance..
Works smooth like a criminal
Thanks for release.
Running on OOS 13.
I missed custom I/O schedules & TCP algorithms.
Great to see that you had set Zram compression to zstd algorithm.
Cannot wait to see your next release !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ty dev for the kernel. Kernel is fine overall but scrolling performance could be a bit better.
Which device is your evo_defconfig for ?
I'm new to kernel building, just wondering .
hightech316 said:
Which device is your evo_defconfig for ?
I'm new to kernel building, just wondering .
Click to expand...
Click to collapse
This was actually an idea I had using EvoX for OP8T.
efx7n said:
View attachment 5798177Ty dev for the kernel. Kernel is fine overall but scrolling performance could be a bit better.
Click to expand...
Click to collapse
Thats probably because I use 300HZ timer interrupt frequency which I have no issue bumping to 1000HZ which Ill drop tomorrow for you all, along with a few minor changes.
I have updated the kernel. Addressing issue brought forth in the comments.
My camera doesn't seem to work . Everything else is doing great!
OOS Cam and Open Cam .
Running latest OOS13 stock .
Attached log.
hightech316 said:
My camera doesn't seem to work . Everything else is doing great!
OOS Cam and Open Cam .
Running latest OOS13 stock .
Attached log.
Click to expand...
Click to collapse
I missed that you were running stock. I probably should've mentioned that. This was only meant for custom ROMs. I am truly sorry I overlooked saying that.
Can u please try to add support for 9r. Coz both 8t and 9r are the same. Just some minor changes ig.
apophis9283 said:
I missed that you were running stock. I probably should've mentioned that. This was only meant for custom ROMs. I am truly sorry I overlooked saying that.
Click to expand...
Click to collapse
No worries .
OnePlus released their OOS13 kernel .
GitHub - OnePlusOSS/android_kernel_oneplus_sm8250 at oneplus/sm8250_t_13.0.0_op8
Contribute to OnePlusOSS/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
How big of a pain would it be to take the blobs ( if that is even what is needed ? ) From that release onto yours ?
Or are they completely different and non compatible since one being AOSP and other OOS?
projektx said:
Can u please try to add support for 9r. Coz both 8t and 9r are the same. Just some minor changes ig.
Click to expand...
Click to collapse
This was based off EvoX's kernel. If they use it for the 9r as well it should work, but if it doesn't. Sure when I get time, I'll peek at it. The zip probably would fail but the boot.img would be fine. Just have a backup to flash if it fails.
Always nice when you pop in and bless us with some butter. Running great and thanks for your work as always
Does it work on OnePlus 8 Verizon (IN2019)? I am on Kaleidoscope Rom (Android 12).
Zombify01 said:
Does it work on OnePlus 8 Verizon (IN2019)? I am on Kaleidoscope Rom (Android 12).
Click to expand...
Click to collapse
Yes, I ran it on the IN2017 T-Mobile OnePlus 8 and it worked.
Unfortunately, I got rid of it because, as mentioned in the thread, FSync was replaced with Dynamic FSync. This prevents you from losing data if the screen is off, but not when it's on.
hammerhaigh said:
Yes, I ran it on the IN2017 T-Mobile OnePlus 8 and it worked.
Unfortunately, I got rid of it because, as mentioned in the thread, FSync was replaced with Dynamic FSync. This prevents you from losing data if the screen is off, but not when it's on.
Click to expand...
Click to collapse
EDIT: use the boot.img and not the zip, the zip enables dynamic fsync
Fsync is enabled always, it only syncs while screen off if you enable it. Dont touch dynamic fsync and it remains as fsync on as always.
Im also testing a twrp build I made for oos13 firmware a13, all partitions should mount. EROFS. I dont keep up with everyones work, I dont think theres a recovery yet that has that possibility but I could be wrong.
Must be on op8t f15 firmware with a rom that uses erofs. You should be able to mount all partitions. If you want to test, you can get with me on telegram. I am only using TG due to the nature of this.
Testing twrp
t.me
Also heres v-1.2 of the kernel boot.img only not pre-patched
apophis9283 said:
Must be on op8t f15 firmware with a rom that uses erofs. You should be able to mount all partitions. If you want to test, you can get with me on telegram. I am only using TG due to the nature of this.
Testing twrp
t.me
Also heres v-1.2 of the kernel boot.img only not pre-patched
Click to expand...
Click to collapse
Only OOS atm? Pretty sure the evoX filesystem isn't erofs.