Been a while since my last post
is there any modified Kernel for the Tab ? I've seen a Galaxy S runs like a fart on youtube " 1.6 Ghz "
my question is : is this kernel adjustable for the tab ? is there a running project in XDA to make this happen ?
thanks a lot
I have compiled both the AOSP (Android Open Source Project) and the Samsung Galaxy Tab open-source code, but I'm happy with JM6 so far, and I guess I am not brave enough to flash self-compiled critical components, I had enough problems with just self-compiled apps
flashed self compiled kernel resulted in panic
I flashed a the open source basekernel with the galaxy patch from samsung and got no joy. Nothing but kernel panic. Fortunately I was able to flash the original zImage back. Any insight on configuration parameters to use. I just did a stock make.
How did you load the system.img and data.img out from AOSP? I've compiled and can't figure out how to load the images.
Thanks
Im actually going to wprk on making a kernel oc'd just need a few tips ive done linux kernels before but the difference is i dobt have the source does anyone have the source to sprints firmware?
Sent from my SPH-P100 using XDA App
If anyone actually releases a stable 1.5GHz or higher kernel, I'll definitely donate $50 for the work, and I'm sure others will too.
I note that:
- some kernel devs ship only a bare kernel which gets packaged up with the existing ramdisk
- some kernel devs ship a full boot partition image (kernel + ramdisk)
- some kernel devs do one or the other of the above PLUS mods to the /system mount point
(e.g. /system/etc/init.d scripts)
- other tweaks (any of them in /sdcard or /data?)
So, what I'm wondering is what kind of protocols users that frequently jump from kernel to kernel are using to avoid configuration ambiguities and collisions. It seems like if you choose some random ROM, flashing a full boot partition image possibly breaks dev mods in the ramdisk. And flashing kernel alfter kernel that writes startup scripts to /system/etc/init.d probably piles up a random collection of potentially mis-matched or conflicting scripts. (One dev's S99 might be another's S80).
Seems like at a minimum you would need to re-flash /system from a backup or the original ROM in preparation for a kernel flash if you had previously flashed some other kernel (that was not the original shipped with the ROM).
I realize there is that kernel flash clelanup script thread - do folks really use it? It seems like the developer would have to be constantly inspecting new kernel releases across all developers to make sure the cleanup script is actually deleting/reverting the right stuff. That seems like a big job and hard to keep it up-to-date.
Anyway - just curious.
Personally after having tried several kernel I found one that suits me and I do not change.
Of all the available kernels for N7, i try and stick to lean or motley as most of the ROMs out there work well with these two...i personally have not found kernel related issues while flashing when compared to Franco or faux...
I always prefer to wipe the grouper completely when a stable version of the ROM of my choice is released ...
Sent from my Nexus 7 using Tapatalk HD
༼ つ ◕_◕ ༽つIn the name of our great lord Helix!༼ つ ◕_◕ ༽つ
Kerneller, a flashable Zip template for ramdisk modifications
Google what a kerneller is
Many of you have no doubt heard of osm0sis' Anykernel2 and previously koush's Anykernel. Kerneller is an alternative designed solely around Sony's Xperia lineup, taking into account the 'recovery-inside-ramdisk' situation we've found ourselves in. However, the script should also support other devices such as Nexus. (I say should because I can only test on the Xperia devices I own -- if anyone could help test, I would be very grateful!)
And with the release of Android 5.0 Lollipop, users have been facing a dilemma: To download a permissive or enforcing version of the kernel? Kerneller fixes that issue by combining the two in a single zip using a slightly modified version of keycheck, allowing the user to choose what will be installed at the time of flashing.
Source: https://github.com/someone755/kerneller
Any questions, tips, or comments are welcome!
Credits & Thanks: All authors of the included binaries. osm0sis for AnyKernel2 and porting the binaries. koush for the original AnyKernel concept. Everyone who helped test. Myself5 for the inspiration and oshmoun for the help.
XDA:DevDB Information
Kerneller, Tool/Utility for the OEM Cross Device Development
Contributors
someone755
Version Information
Status: Stable
Created 2015-12-26
Last Updated 2015-12-31
This is something, i was expecting.
Thank you very much.
Black_Eyes said:
This is something, i was expecting.
Thank you very much.
Click to expand...
Click to collapse
I'm glad you like it but I can't say that's the reaction I was expecting lol. Please do let me know if anything bothers you though.
Just by the way, I moved the thing into its own repo and added a small script to compress and sign it. Cheers!
work for lock or un lock？thank you
xsj said:
work for lock or un lock？thank you
Click to expand...
Click to collapse
I'm sorry to say I don't understand the question. This script cannot lock or unlock anything.
It modifies the boot sector of your device. For that to be possible in the first place, you need an unlocked bootloader.
thank you，Im lockbootloader now，and that's what I want to know
Sorry for noob question,but where to download?Cant find the link.Want to try this on my m2 aqua.
mariosenta said:
Sorry for noob question,but where to download?Cant find the link.Want to try this on my m2 aqua.
Click to expand...
Click to collapse
Your best bet would be using 'git clone', though you can also just download the whole repo as a zip file (here, if you're having trouble finding it). Note though that the packing script won't work in Windows unless you have a *nix shell emulator (such as Cygwin or win-bash)!
You can still zip the thing together yourself using 7zip or WinRAR, however it will not be a signed zip (so some recoveries -- like Cyanogen Recovery -- may refuse to flash it, but you could use the bash script to figure out what you have to do in Windows to sign your new zip).
If you do eventually get it to run, I'd be very glad if you could send me the recovery.log of the flash via PM!
TouchWiz?
This tool works on touchwiz Lollipop 5.1.1 Roms or not?
Stock kernel is Enforcing and I tried various methods to make it permissive, nothing works
Pavan l said:
This tool works on touchwiz Lollipop 5.1.1 Roms or not?
Stock kernel is Enforcing and I tried various methods to make it permissive, nothing works
Click to expand...
Click to collapse
I don't know if your device's boot image is assembled using mkbootimg (like Nexus devices). If so, you may be able to.
But you'll need to pack the device tree binary and zImage into the zip (just use unpackbootimg).
So, I'm very confused, I usually build boot.imgs right out of the AOSP source code... how could I leverage this?
HaoZeke said:
So, I'm very confused, I usually build boot.imgs right out of the AOSP source code... how could I leverage this?
Click to expand...
Click to collapse
It's not really meant for people who compile ROMs, but more for kernel devs or testers who only compile the kernel.
Instead of always having to extract the ramdisk from boot images (whenever the ramdisk changes, which we kernel people can't know and check for every single kernel, nor do we care) and then using mkbootimg (meaning you have to release one boot image for every ramdisk you need to support, i.e. if you want to support ROMs with vastly different ramdisk implementations, where mixing ramdisks would cause a bootloop).
With this, you go around the problem. Compile the kernel outside of the ROM tree (which takes a few minutes vs several hours that compiling the entire ROM can take), grab the zImage-dtb (or adjust the script to use zImage + dt.img), and package the thing together. (There are options to also include kernel modules in the zip, and scripts that will compress and sign the zip for you.)
The highlight of this project used to be being able to switch Selinux status when flashing the zip, instead of adding androidboot.selinux=permissive for each boot image, and then uploading two images. Nowadays compatibility of this switch with various devices and Android versions is questionable (I can't test personally because of how limited Xperia devices have become recently -- the 3.10 kernel does not work with enforcing selinux), but the core idea of using it to avoid having to create boot images is still alive and kicking.
I am trying to build a custom kernel for my redmi 2 running on Nexus Experience. I found there kernel source at their github page in nx_kernel_xiaomi_msm8916 . It's the only kernel referring to XIAOMI so I think it is the right one.
I am really new to kernel building. I read some tutorials on the web and tried building one for the stock miui rom but it didn't work out.
So before I start re-building the kernel for Nexus Experience I had some questions. I wanted to add the support for external wifi adapters based on RTL8188CUS. I found the option to enable it. My question is that , By just enabling that feature will my phone just start supporting the adapter out of the box or do I have to add some Modules to it.
And the last question, After I compile the kernel I get this zImage file. I put this file in the anyKernel.zip but I found that I also have to add the wlan.ko file and I couldn't find it....
I really need some help here.
I am trying to build the latest OOS 13 kernel .
The source I am working with is https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_t_13.0.0_op8
In the past , i've built for Samsung and Lenovo devices , although I am unsure of a few things with our oneplus8t
Which defconfig file should I be using? as I do not see a kebab config within the root directory of android_kernel_oneplus_sm8250 or arch/arm64/configs/
Google has helped , but not too much material on building OOS kernels
What is the difference between a OOS kernel and AOSP kernel ? Would I be able to take a commit from AOSP and apply to my OOS ?
Appreciate any insight , and hope to be able to release a kernel soon!
SOLUTION
Backed up my boot.img with ex-kernel manager . Brought the boot.img to my build folder. Extracted defconfig with extract-ikconfig
Hey Dude I'm on oos11..i wanna compile a new kernel..which debconf to use.. the one in the vendors or what? Kona-perf.debconf?
Please help me which debconf to use for OnePlus 8
@hightech316 any luck on building the custom kernel yet?