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
Related
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.
Hello there,
I'm looking for a way to mount nfs shares of my NAS and (debian wheezy) server in the filesystem for access of my media files.
I thought for long that it would be the most natural thing to do for my (linux based) mobile devices in a linux server environment, but it seems I'm far off.
So far I have been unable to mount these nfs shares of mine to the Nexus 7 (grouper) device running a Carbon ROM 4.4.2 Nightly Build from march this year (CARBON...20140302-0433.zip) with CifsManager, most likely due to its lack of kernel support (version 3.1.10--g90cc2cb1 bigshotrob...).
May one of you recommend a kernel that supports nfs, cifs and utf-8 for this build? I restrain from updating it as it is running smoothly and without problems (Remember? Never change a...) and I don't like to invest much time for the reconfiguration and other related stuff.
I know there is M-Kernel (http://forum.xda-developers.com/showthread.php?t=2168787) out there that claims to have exactly the requested support and compliance to the CarbonROM series. But I'm unable to sort out what version of the kernel would match my build of the ROM.
I understand that the most actual release is for versions 4.4.4, but the changelog and >200 posts I've browsed do give no hint which release was compiled for 4.4.2 ROMs.
Please note, I would ask directly in that respective thread in the development section if I could, but owing to the (imho pretty stupid) 10 post restriction of newcomers I am unable to post there.
Edit: Not necessary anymore, got my postings ...
Accordingly, my second question would be, if someone with more than 10 posts would be so kind and ask the following questions for me in the given thread?
Namely:
What version of the kernel would fit my 4.4.2 CarbonROM Build and where could I obtain it?
Does anyone had success to mount nfs shares with it (or cifs, if not) ?
Edit end
That and any alternative ways/hints to get nfs going would be highly appreciated!
Thank you very much,
Nix
Specs Summary:
Nexus 7 2012 Wifi only
Carbon ROM 4.4.2 Nightly Build (CARBON...20140302-0433.zip)
Kernel 3.1.10--g90cc2cb1 bigshotrob...
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Edit
http://vp-zp.com/snuzzo/kernels/grouper/
Forgot my link lol
Snuzzo said:
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Click to expand...
Click to collapse
Thank you for the reply snuzzo,
would you mind to give some details where to learn more of its features and where to find it?
Then I'll have a look at it.
EDIT:
Thanks for the link! But exactly what version do I have download for my Carbon ROM build above, if I'd decide to use it that is?
Presumably .../kitkat/Funky...??
BTW, are there some feature lists or such things? I'll probably browse the forum a bit, I suppose?
Cheers, Nix
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run. You will want 1.6.2 or 1.6.1.
Snuzzo said:
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run.
Click to expand...
Click to collapse
Sounds great, although most of it are books with seven seals for me
What about nfs support? And its definitely for 4.4.2 based ROMs?
Thx again,
Nix
Yes to both. It has NFS and CIFS support.
And v.1.6 is the one you'd suggest?
Nixblicker said:
And v.1.6 is the one you'd suggest?
Click to expand...
Click to collapse
Yes.
Snuzzo said:
Yes.
Click to expand...
Click to collapse
One more question, please - do I have to activate or load those modules manually or will they be loaded at bootup by default?
Where may I find them to insmod/modprobe them manually, if not?
Thanks for the help once more,
Cheerio,
Nix
They will load by default.
This is a personal build of TWRP with F2FS support(proper way) based off 2.8.1.0 branch from Omnirom(recovery) which I butchered and added F2FS..
This was tested with CM11 way back last year..I just posted it for the heck of sharing it since I have not seen the same idea/achievement here on M7 forums..and seems this phone needs a "refresh"(in a good way)..
Now whats F2FS?? Googling can give you trivial INFO yet you can start your way here
This Files system developed by Samsung Developers lean towards a much less noisier, less workloads, and a faster throughput File System that can substitute EXT4 in the near future(they already use it)..extensively if you rely heavy on Benchmarks it has been put to the test by some Devs here on XDA like this one
Now enough with the chit-chat..on this TWRP build I only converted /DATA as F2FS..now you might be wondering why?? Answer is because its the most actively used partition on your phone..System apps use it to store settings/info/etc...Framework uses it too for caching and storage...Extensively your Apps(the ones you install) use it as well..so there completely no point converting the whole phone to F2FS which in the latter can just cause you more issues when you want to return to stock..
This only works on AOSP based ROMs(i tried it on CM11) though you'll need a kernel with F2FS support baked in for things to work properly.. (Who wants me to build one? I know for sure you don't..)
DO NOT TRY ON SENSE(You have been warned) Tried it once well it boots up but you'll end up on a security windows and you might not get out if it..OR you may be able to boot it up but you cannot install apps(happened to me twice and no Dice on installing anything)..well you're free to play with it so who knows who might get a lucky pick on getting this working on HTC Sense ROM's, but for now I'll safely say/advise to use on AOSP ROMS only..
Download here
**I won't be liable for any damage on your phone..you are on your own here..
**This project does not come with a warranty..
XDA:DevDB Information
Recovery with F2FS, Tool/Utility for the HTC One
Contributors
kairi_zeroblade
Version Information
Status: Stable
Stable Release Date: 2015-02-05
Created 2015-02-05
Last Updated 2015-02-05
༼ つ ◕_◕ ༽つ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 see installation instructions for a ROM (which is the Android OS, right?) and I see references to a kernel as well. What is the difference? Am I supposed to install both at the same time, or does the ROM carry the kernel, or how does it work?
Android is similar to mainstream linux operating systems in that the ROM is like the OS portion of a linux distro.
the Kernel is the portion that interfaces between the OS and the hardware.
Pretty much all Roms (there may be exceptions but I cant think of any) come prepackaged with a kernel as well.
so installing the ROM will install the kernel automatically and has the benefit of installing the kernel the developer intended.
There are separate Kernels available that have specific features you may prefer. (overclocking for CPU/GPU, specific modules loaded for emulation if running a linux distro within android etc.)
to install them you would install the rom (And its default kernel) then flash the kernel of your preference over it.
If you are just starting out I would just install the Rom and its default kernel unless you have a very specific use case.
hopefully that helps
There are often more pieces as well due to proprietary code:
ROM - the OS itself often either based on AOSP, the manufacturer software or Lineage (or a mix)
Kernel - refers to the open source linux kernel that controls hardware that it supports.
Firmware - includes manufacturer proprietary code for hardware that is not open source.
Modem - includes proprietary code for modem hardware.
it breaks down further but generally you will start with a stick manufacturer installation including all parts.
then you can flash a custom rom and kernel (Usally as a complete package)
Modem and firmware updates would still come from the manufacturer. (Most roms will tell you if a specific firmware or modem is needed, the modem usually doesnt matter as much anymore but in the early years it was important)
Thanks for the information!