[Kernel][5.x][carcosa-kernel][Stock kernel with cherry-picked features][2015/03/20] - Nexus 7 Android Development

1. Motivation/overview
This is a kernel for the 2012 Nexus 7 (grouper/tilapia) which sticks as closely as possible to the stock/released kernel sources, while incorporating the features I want from other popular alternative kernels. I've built it because my Nexus 7 3G (tilapia) has trouble with all of the non-stock kernels I've tried -- something causing USB resets in a tight loop. I rebuilt the stock kernel and started adding my favorite features in order to rule out what was causing the problem, but ended up with a kernel I preferred for day-to-day use.
You might like it, too.
Note that there is very little original content in this kernel: see the credits below and the github repository for the sources of the included features.
2. Features
IO Schedulers
bfq
row
SIO
CPU Governors
smartmax
wheatley
Misc
Build with -Os (optimize for size)
GPU overclock
Experimental: remove baseband_xmm_power wakelock
f2fs driver (see note in second post)
ntfs r/w (see note in second post)
CPU voltage control
Mount slave namespace workaround
CPU overclock (against my better judgement).
3. Instructions
This kernel is intended primarily for use with the stock ROM. The first releases (mr1 and a20) were built with a stock ramdisk, and will generally not work on other ROMs. Later releases use an AnyKernel updater and may work on other ROMs. I am only able/willing to test on stock, however, so non-stock users, use at your own risk (even more than usual).
To install, boot into your custom recovery of choice and install one of the zips below. Or use Flashify. Be sure to make a backup with your recovery first.
4. Warning and disclaimer
I am not responsible for any harm caused to you, your tablet, or the integrity of the space-time continuum by this kernel. In the words of the GNU Public License:
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
5. Downloads
Milestone releases:
mr1: carcosa-kernel-mr1.zip
Alpha releases:
a20: carcosa-kernel-a20.zip
Includes experimental patch removing baseband_xmm_power wakelock.
a22: carcosa-a22-anykernel.zip
Includes changes to governor defaults, ntfs r/w support, and the f2fs driver.
a23: carcosa-a23-anykernel.zip
Includes voltage control (undervolting) interface.
a25: carcosa-kernel-a25.zip carcosa-a25-anykernel.zip
Includes mount slave namespace workaround, CPU overclocking (against my better judgement)
a27: carcosa-a27-anykernel.zip
4.4.3 update
a28: carcosa-a28-anykernel.zip
Remove baseband_xmm_power wakelock again, rather than making it time out.
a29: carcosa-a29-anykernel.zip
Add configurable baseband_xmm_power wakelock timeout
a33: carcosa-a33-lp-anykernel.zip
Lollipop update; adds SIO IO scheduler.
a35: carcosa-a35-lp-anykernel.zip
Lollipop 5.1 update (still works with 5.0.2). Adds hardware acceleration for kernel encryption routines.
6. Source
Sources are on github, which is also your best source for changelogs.
7. Credits
This kernel contains precious little original work -- it builds on the stock kernel release and applies cherry-picked patches from various sources, principally M-Kernel (Metallice) Franco-kernel (Francisco Franco), and Oxydo (Sgt. Meow), but also Faux123, Ezekeel, Maxwen, and many others. My main contributions have been picking the things I wanted, and resolving the occasional hairy merge. I have attempted to maintain the original authorship information in my git logs as much as possible; I apologize for any cases where the attribution of a particular patch has been lost.

Notes
F2FS support
While this kernel (from a22 on) includes the f2fs driver, it does not include any of the ramdisk or init tweaks that you would need to use f2fs. This is because I am not in a position to test f2fs myself. That said, the a22 (and later) kernel installer will not disturb any changes you have already made to your ramdisk or ROM to support f2fs, so if you have already got f2fs working on your device, it should continue to work after installing this kernel. Don't forget to do a nand backup in your recovery before installing, though. Seriously.
NTFS R/W support
This kernel (from a22 on) includes RW support for NTFS. However, in KitKat, NTFS USB drives mounted with StickMount are not writable due to SELinux policy. To write to an NTFS USB drive, you need to (from a root shell) 'setenforce off', then 'setenforce on' when you're done using it. I do not recommend that you put SELinux in permissive mode permanently. It's there for a reason, and this is just a workaround for a policy error in KitKat. The SELinux SetEnforce Toggle app is a convenient way to turn it off and on for this.
Mount slave namespace workaround
Android apps that mount filesystems (e.g. CIFS, Lil'Debi's loopback fs), mount them in a private namespace that is not shared with other apps (as explained by mkasick). There is a rom-based workaround applied in CM-based roms, and probably many others, but not in stock. Instead, I am applying his kernel/ramdisk based workaround. If you are on stock and need this workaround, do not use the anykernel build; use the one with the full disk image.
Configurable baseband_xmm_power wakelock timeout
This is based on work by Sgt. Meow, with some tweaks. It is controlled by the module param /sys/modules/baseband_xmm_power/bb_timeout, which defaults to 10, and represents the time, in 10ths of a second, that the baseband_xmm_power wakelock should be acquired for before timing out. 0 will disable the wakelock completely as in earlier versions of carcosa-kernel. These semantics are not the same as those for the same parameter in Oxydo, so be aware.
-------------------------------------------------------------------------------------------------------
Camilla: You, sir, should unmask.
Stranger: Indeed?
Cassilda: Indeed, it's time. We all have laid aside disguise but you.
Stranger: I wear no mask.
Camilla: (Terrified, aside to Cassilda) No mask? No mask!
– from Act 1, Scene 2 of The King In Yellow

Kernel rocks! Thanks!

bjcrj said:
Kernel rocks! Thanks!
Click to expand...
Click to collapse
You're welcome. Are you using the milestone release or the alpha? And are you on grouper or tilapia? I want to know if the baseband_xmm_power hack is being tested by anyone besides me.

jfmcbrayer said:
You're welcome. Are you using the milestone release or the alpha? And are you on grouper or tilapia? I want to know if the baseband_xmm_power hack is being tested by anyone besides me.
Click to expand...
Click to collapse
I am using the alpha. I run a grouper rom on tilapia and didn't have any wake lock issues.

Hi, I'm using the newest CM Release and after flashing the kernel i got a com.android.phone has stopped error. I cleared the cache and the dalvik before restart.

gremlin89 said:
Hi, I'm using the newest CM Release and after flashing the kernel i got a com.android.phone has stopped error. I cleared the cache and the dalvik before restart.
Click to expand...
Click to collapse
The boot.img in the zips I've provided us built with a stock ramdisk, and CM needs its own ramdisk. Perhaps I could build an AnyKernel zip for non stock users.

bjcrj said:
Kernel rocks! Thanks!
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Nexus 7 using xda premium

Just flashed mr1 on bshiznit’s stock ROM earlier today. So far it's running nice and smooth. Nice work!
Sent from my Nexus 7 using Tapatalk

pjcanales said:
What ROM are you using?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Aospal

jfmcbrayer said:
The boot.img in the zips I've provided us built with a stock ramdisk, and CM needs its own ramdisk. Perhaps I could build an AnyKernel zip for non stock users.
Click to expand...
Click to collapse
Oh that would be really great. Is it easy to build such a rom?

gremlin89 said:
Oh that would be really great. Is it easy to build such a rom?
Click to expand...
Click to collapse
Not a ROM, just an updater zip. In principle, it should be easy. But somehow, I've never got it to work.

Thank you very much for your work! Without your kernel my battery was empty within one or two days due to the annoying wakelocks, now my N7 runs since 7 days and I still have 40%! Awesome!

sengst said:
Thank you very much for your work! Without your kernel my battery was empty within one or two days due to the annoying wakelocks, now my N7 runs since 7 days and I still have 40%! Awesome!
Click to expand...
Click to collapse
I'm glad to hear it. Am I correct in assuming that you have a tilapia device, and are running the alpha version of the kernel?

Just a question
What is the difference between Milestone and Alpha ? btw i am using nexus 7 wi-fi only model

jfmcbrayer said:
I'm glad to hear it. Am I correct in assuming that you have a tilapia device, and are running the alpha version of the kernel?
Click to expand...
Click to collapse
You are right: tilapia aosp and your a20 kernel.

ispukan said:
What is the difference between Milestone and Alpha ? btw i am using nexus 7 wi-fi only model
Click to expand...
Click to collapse
Currently, the difference is that the alpha disables the baseband_xmm_power wakelock, which some people perceive to be a major source of idle power drain on the 3g (tilapia) model.

jfmcbrayer said:
Currently, the difference is that the alpha disables the baseband_xmm_power wakelock, which some people perceive to be a major source of idle power drain on the 3g (tilapia) model.
Click to expand...
Click to collapse
So i can install what ever i want there is now difference for wifi only model ?

ispukan said:
So i can install what ever i want there is now difference for wifi only model ?
Click to expand...
Click to collapse
Right; you can run either on a Wi-Fi only (grouper) device, but the changes are only relevant to tilapia.

Hi, can I use this kernel on PA 4.1 beta on my tilapia? Currently using the Franco r77 kernel and still get massive baseband wakelocks! If this kernel doesn't work on the said ROM, how do I revert to the stock kernel? Using the FKA app and have a backup of stock kernel. Thanks
Sent from my Nexus 7 using XDA Premium HD app

Related

[KERNEL][4/11/12] TestyMeh ICS 1.0 - OC+SIO+Initd ICS, New Suspend Method, Added Veno

This kernel aims to improve performance, while still maximizing stability (and getting rid of reboots and SODs). It's working on all ROMs so far, so here it is for your approval. It can overclock to 1704Mhz, but doesn't override your user limit. I've added SIO and Init.d support and some various tweaks, and rebased to the newest source. Next is more cpu governors and general tweaks. Thanks to Roach for his commits from github, and guevor for new suspend code to imitate.
Some ROMs use a different build config, so Use The Right Version Below! Please Wipe Cache in CWM before flashing.
Update 4/11/12: Added test version of Veno, read about it at: http://www.ie.cuhk.edu.hk/fileadmin/staff_upload/soung/Journal/J3.pdf1.0 is up for All testers. Voodoo should be supported, please report. Wifi has been tested on Stock/ARHD/Revolver/Megatron/CNA/AOKP, but please test with other ROMs. I'm trying to compile one kernel for all ROMs, but EOS is still separate. Mega props to Guevor for the new suspend code. I'm trying to implement it without directly copying him though, so I need testers again. I will compile for other ROMs if necessary.
Update 4/7/12-2: 0.8 Added OC up to 1704mhz, Under/Overvolt support, made some changes to error handling for wifi stack, tweaked default voltages, and some stuff I can't remember right now. For testing, 0.8 downloads are in green. CIFS, TUN, and NTFS are cooked in, you should not need to load modules. There is a download link provided below for people who want the modules anyways.Personally tested on all ROMs listed, haven't had time to try Frozn.
Install with CWM or Rogue
Download 1.0(All ROMs, except EOS):http://db.tt/nNEbqufy
Download 1.0 With TCP_VENO(All ROMs, except EOS):http://db.tt/CqEqLMDQ
Download 1.0(EOS):http://db.tt/nnn4x9mN
Download 0.8(Stock/ARHD/Revolver/Megatron):http://db.tt/XyxW8WTK
Download 0.8(CNA/CM9Mar29/AOKP):http://db.tt/fiOXe16e
Download 0.8(EOS)http://db.tt/rcUAfPjz
Download 0.6 (Stock/ARHD/Revolver):http://db.tt/YDIInoKn
Download 0.6 (CNA, CM9, AOKP):http://db.tt/wdwPhWVt
Download 0.6 (EOS):http://db.tt/1yAOB7tq
Download 0.7 (Stock/ARHD/Revolver):http://db.tt/YsOdC3Tk
Download 0.7 (CNA, CM9, AOKP):http://db.tt/91iLDpKq
Download 0.7 (EOS):http://db.tt/HVY81MUQ
CIFS/NTFS Modules: http://dl.dropbox.com/u/21284412/modules.zip
You shouldn't need these, but I'll leave the link for old time's sake.
This is still beta. You must have balls to flash this(metaphorically speaking). Don't rip mine off if you have to reflash something else.
I had a couple requests for a donation link, so I'm posting one below. Feel free to buy me a beer if you want, but most of the work was done by the source code and people before me.
Click Here To Donate To My Delinquency
Github is at: https://github.com/msticninja/asus_kernel_tf101
Changelog:
Code:
1.0-Veno Add TCP_VENO as default ipv4 Congestion Control Method
1.0 Change suspend code to be closer to guevor's. Hopefully fix reboots again. Add post_boot exec for ARHD.
0.9 Change clk_disable_locked code to be closer to Nvidia source. Hopefully fix reboots.
0.8 Add BFQ, Over/Undervolt support, wifi patches, OC to 1704, etc.
0.7 Rebased off Asus March 29th Kernel Source. SIO/Init.d is now included in all kernels.
0.6 Fixed Wifi on CNA SIO Version(still getting the hang of using git branches, sorry)
0.5 Add Init.d support to ramdisk
0.4 Add SIO IO Scheduler
0.3 Add EOS Version
0.2 Add CNA/CM9/AOKP Version
0.1 Add OC and compile tweaks
Compatible with cyanogenmod?
psyk974 said:
Compatible with cyanogenmod?
Click to expand...
Click to collapse
Depends. Try it. The worst thing will be that the wifi doesn't work. I'm working on the bcmdhd version for people with AOSP roms, that may use the same driver.
Thx. I will try it !
Thank you , but can u chack if the dock 2xUSB (removable disk) is working?
Because on every OC ICS kernel that i tried so far on the tf101 , the dock USB stop working
psyk974 said:
Thx. I will try it !
Click to expand...
Click to collapse
Let me know what happens. If anything isn't right, give me as much detail as you can.
i9apps said:
Thank you , but can u chack if the dock 2xUSB (removable disk) is working?
Because on every OC ICS kernel that i tried so far on the tf101 , the dock USB stop working
Click to expand...
Click to collapse
Just checked with a couple of flash drives, works perfectly.
msticninja said:
Let me know what happens. If anything isn't right, give me as much detail as you can.
Click to expand...
Click to collapse
Okay ! I inform you
msticninja said:
I just compiled this from my github, which is forked from Roach's(He's working on EOS, so I'm filling in the void for now, with his permission). It's working beautifully for me on stock ROM and ARHD so far, so here it is for testing. It can overclock to 1600Mhz, but doesn't override your user limit. Blades' test kernel "meh" overrides the user limit once the screen is off, which makes my TF reboot constantly. That's really the only reason I compiled my own kernel, but I know other people have this issue, and Roach said he doesn't have time to compile and post it for us. Thanks to Roach of course, and Blades, because I used his "meh" updater-script (because I forgot which partition the kernel was supposed to be dd'ed to.)
Install with CWM, (or Rogue(untested though))
Download:http://db.tt/wKQ6ho2h
This is still beta. You must have balls to flash this(metaphorically speaking). Don't rip mine off if you have to reflash something else.
Going to bed now. Will respond to responding responders in morning. Seriously. Me So Tired.
P.S. @guevor Didn't mean to post this right after you merged Roach's fix, we must've been compiling at the same time, little did we know.
Click to expand...
Click to collapse
Dont forget the source or patches main rule !!!
Could you list the Core mV per frequency too please?
Jhinta said:
Dont forget the source or patches main rule !!!
Click to expand...
Click to collapse
Grrr...lack of sleep. I thought I did. Appended.
cspiby said:
Could you list the Core mV per frequency too please?
Click to expand...
Click to collapse
https://github.com/msticninja/asus_kernel_tf101/blob/d1da185880877e22c7881fe69d4cb650e7a84ba5/arch/arm/mach-tegra/tegra2_dvfs.c
Too sleepy to make a table out of it. I'll do it tomorrow if you can't figure it out from the source.
Just flashed the kernel , got a first reboot after 4 seconds
will try again now
i9apps said:
Just flashed the kernel , got a first reboot after 4 seconds
will try again now
Click to expand...
Click to collapse
Like I said, if you have issues, give as much info as possible. ROM, frequency settings, etc. I only have one TF to test on, so you'll have help me out.
initd support?
drakal said:
initd support?
Click to expand...
Click to collapse
Haven't had time yet, just made it for my own purposes originally. I'll put a new ramdisk together and repack tomorrow if someone else hasn't done it by then.
msticninja said:
Like I said, if you have issues, give as much info as possible. ROM, frequency settings, etc. I only have one TF to test on, so you'll have help me out.
Click to expand...
Click to collapse
I am running Revolver rom 1600 GHz and the kernel not working for me , the tf freeze or reboot, on the other kernels i manage to OC to 1.68Ghz stable
i9apps said:
I am running Revolver rom 1600 GHz and the kernel not working for me , the tf freeze or reboot, on the other kernels i manage to OC to 1.68Ghz stable
Click to expand...
Click to collapse
I haven't tested on Revolver. I didn't add init.d support yet, so it could be that. Can you run at lower frequencies without rebooting? Mine can't handle 1600 on any kernel, so I can't really troubleshoot that, but if it still reboots at 1000 or 1200, then it's probably a ROM incompatibility. We'll see if anyone else can test it on Revolver in the mean time.
Hi,
tested your kernel with CNA 1.5.5.3 sadly no wifi.
Now I'm back on stock
Greetings
Nice to see more kernels popping up
I would help you test it, but frankly Im not in the mood to troubleshoot (if needed) today
Been screaming at a PC all day that refused to work properly hehe

[KERNEL][ICS][07-04-12] AniDroid-Hardened-TF101 (2.6.39.4)

AniDroid-Hardened-TF101 Kernel​
Short Kernel information:​
AniDroid-Hardened Kernel is the first Hardened kernel for Android that uses GRSecurity subsystem to provide different useful Security functionality.
AniDroid-Hardened Kernel now is in early stage of developing but it's almost ready for using and testing on Asus Transformer TF101 and Google (Samsung) Nexus S devices ​
Provided Features:
Linux Kernel version 2.6.39.4
GRSecurity version 2.2.2 with different security features enabled by default (see GRSecurity Feature List for details)
EXT4, NTFS, CIFS support
init.d support
Compatible with any OTA-based and AOSP ICS Roms
1024 Kb ReadAhead support
Automatic Process Group Scheduling
-fstack-protector buffer overflow detection
GRSecurity Feature List:​
Kernel Memory Protection (restrict read/write access to /dev/kmem, /dev/mem, and /dev/port)
Active Exploits Protection (deter exploit bruteforcing, active kernel exploit response)
Role Based Access Control (RBAC)
Filesystem Advanced Protection (including advanced security for applications running in CHROOT environment)
Full Kernel Auditing (event logging for many kernel events)
Executable Protection (deter ptrace-based process snooping)
Network Protection (TCP/UDP blackhole and LAST_ACK DoS prevention)
Managing support via Sysctl Interface
CPU Frequence Scaling Governors:​
Ondemand (Default)
Interactive
Conservative
Powersave
Performance
IO Schedulers:​
CFQ (Default)
Noop
Deadline (tweaked for flash devices)
Simple IO (SIO)
Links:​
Current Kernel Binaries:
AniDroid-Hardened-TF101-Alpha1.zip
Other Kernel Binaries:
Old binaries on SourceForge
Kernel Source:
Will be available on GitHub soon..
Changelogs and issues info:​
Alpha 1 known issues:​
BCM4329 WiFi kernel module temporarely doesn't work
SU is temporarely cause "Permission denied"
WARNING!!!
AniDroid-Hardened-TF101 Kernel is still need testing!
So, you can flash and use this kernel at your oun risk! ​
Thanks to msticninja, guevor, eugene373, koush, ezekeel, supercurio, morfic, franciscofranco, sztupy, reddv1, byeonggonlee!!!
​
Great to see another kernel option. Awesome work, mate!
I'll give it a try.
hi!great to see new kernelz every week!after reading all the features in the nexus 3ad,i wonder if you'll put some of them un future in this tf's build...some of them i use every day on smartphones and are very Usefull..like touchwake,liveOC,BLX , fast charge and others..(fast charge especially)glad to test this kernel now,hoping that wifi works,anyway thanks for the hard work and keep it up in future release!i'll report how it goes...
sert00 said:
hi!great to see new kernelz every week!after reading all the features in the nexus 3ad,i wonder if you'll put some of them un future in this tf's build...some of them i use every day on smartphones and are very Usefull..like touchwake,liveOC,BLX , fast charge and others..(fast charge especially)glad to test this kernel now,hoping that wifi works,anyway thanks for the hard work and keep it up in future release!i'll report how it goes...
Click to expand...
Click to collapse
As far as I know, fast charge from a computer USB port isn't possible on the tf101 because it requires 12v to go into fast charge mode where a normal USB port only provides 5v.
Congrats on getting the kernel compiled with your changes. I'll post some fixes tomorrow that you might want to pull to your git. I have to be honest though, I don't really see the point of grsecurity on android. Do people actually get hacked?
noted but will flash when somebody got the balls to try...
Sent from my Transformer TF101 using xda premium
j3tt3 said:
noted but will flash when somebody got the balls to try...
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Never mind the balls, I don't see the point of flashing a kernel where wifi and SU (both quite critical in my opinion) don't work.
Basically, su won't work with GRSec because of the RBAC model. Another way needs to be found
Sent from my LT26i using XDA
K900 said:
Basically, su won't work with GRSec because of the RBAC model. Another way needs to be found
Sent from my LT26i using XDA
Click to expand...
Click to collapse
SU will work as privileged user can be allowed to run privileged operations useful for such apps as Titanium Backup and so on ..it's not GRSec issue - vanilla asus source have tha same issue for me.. it's either compiler or ramdisk problem..
novic_dev said:
SU will work as privileged user can be allowed to run privileged operations useful for such apps as Titanium Backup and so on ..it's not GRSec issue - vanilla asus source have tha same issue for me.. it's either compiler or ramdisk problem..
Click to expand...
Click to collapse
I meant that you need to either allow switching to root, which defeats the whole purpose of GRSec or use its own access controls, which needs to be done in apps.
Sent from my LT26i using XDA
K900 said:
I meant that you need to either allow switching to root, which defeats the whole purpose of GRSec or use its own access controls, which needs to be done in apps.
Sent from my LT26i using XDA
Click to expand...
Click to collapse
It will be an App
Sent from my Nexus S using xda premium

[Kernel] JB/ICS Kernels V2.57 Linaro 12-27-12 Flashable zip works with ANY ROM

First off, here is the github
https://github.com/pio-masaki/at100-kernel.git
Everything I do for this kernel is done there.
Now that's out of the way, here are some highlights:
Beginning of OC code (yes, an OC ICS kernel)
Added a slew of governors for your choosing
Added a couple i/o schedulers
Slight CFLAG tweaking
This is a work in progress!
If you have issues feel free to report, but this is my first ever kernel project, and it may take some time for me to address them!
Dos and Dont's in this thread:
No flaming, please. If someone asks a question thats been asked before, simply remind them and if you would, link the post or thread containing the answer. Replies like "Use search" don't help at all. Saying "Next time, use the search, the information is here" is of course what I would like to see. XDA will be better for this.
No ETAs! I can not, and will not, make any promises on when I can fix, build, or otherwise even think about this kernel, or any rom, period. Asking for ETAs, even politely, will either go unanswered, or reminded of this note.
Issue reporting: I always welcome issue reports, of course, however keep in mind, the point made above is also covering this, I may not have time to address an issue immediatly, though I will try to post back and acknowledge that I have seen the issue, or to ask further questions. Please include as much information as possible, settings for speed, governor, IO, profiles in use for screen off (which I advise against), cpu control app in use, etc. Dmesg would be nice as well, use pastebin, we don't want to see an 8K line post of a log
Changelog:
Experimental V0.1 10-02-12
First "release" for testing. This is internal build 8, and from this point on, will be labeled and numbered as releases, IE if this does ok, next will be Alpha 1, or experimental V0.2, etc.
Added OC code
Experimental V0.2 10-05.12
Second release for testing. Does now include the CODE for voltage control, but is not enabled yet. I didn't enable it to help prevent issues with instabilities from UV being confused with kernel issues. GPU OC is active, 320/400 MHz 2D/3D. Does not play well with ICS, CM10 use only.
Experimental V0.3 10-06-12
Rewrote alot of the upper end speed/voltage/timing code from 1.508 to 1.472, VT, haptic feedback fix? Proved unstable to the point of being unusable. Pulled.
Stable V0.4 10-06-12 "Caspar"
Reverted to V0.1 OC code after the disaster of V0.3. Left out voltage control code, implemented GPU OC as previous in V0.2, VT is enabled, possible haptic fix (not likely). Governors and IO schedulers should remain as before, min/max settings should remain as before. 1.5 is likely still broken.
Experimental V0.5e "Melchoir" 10-18-12 ICS only
All new CPU Speed tables, overall max is lowered from 1.5 which froze to 1.478, and more speeds in between. Those who used the Shiva Kernel will be familiar with the speed range. GPU OC is bumped up 20mhz in 2D/3D. SmartassV2 code added. The kernel has branched since V0.4 and is now a JB and an ICS specific design, one doesn't work for the other anymore, sorry to say. "Melchoir" is the ICS branch kernel, "Balthesaur" is the JB branch kernel which is included in the CM10/Kuroikaze builds.
"Melchoir" V2.4 ICS
Experimental support of CIFS and slight config changes to maybe improve kernel performance. Branch from "Caspar" and includes speeds, governors, IO schedulers and any previous bugs. 1.5Ghz is likely still broken.
"Balthesaur" V2.75 Linaro JB NON OC
Experimental fixes for ExFat corruption issues.
No CPU or GPU OC
Built with Linaro 4.7 toolchain with some optimizing tags turned on
Retains Governors and IO Schedulers from the OC version
Instructions
Download the zip from the link given below
Boot into CWM
Wipe cache
Wipe dalvik cache
Install from zip
Install the kernel zip
Reboot
First boot will take longer as the caches are being rebuilt
Let kernel settle for 10 minutes
Reboot
Let kernel settle for 5 minutes
Begin normal usage and setting up
System Tuner has been reported to work with great success.
Downloads
Experimental OC 1 | Mirror
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.2
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing. Only for CM10.
Experimental V0.3
*note* completely unstable, pulled.
Stable V0.4 "Caspar" ICS
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.5e "Melchoir" ICS
*note* does not boot. See change log for information. ICS only kernel. Please have V0.4 zip handy in case this kernel goes ballistic or doesn't boot, etc.
Experimental V2.4 "Melchoir" ICS
*note* likely retains the 1.5GHz lockup issue.
Balthesaur V2.75 Linaro No OC JB ONLY
Non OC kernel by request. Built with Linaro and current 2.75 source. For use with Jellybean ROMs only. Retains IO Schedulers and Governors, just no CPU or GPU overclock at all. Possibly includes fixes for exfat corruption (planned for U6, but may as well)
Revert kernel
Favum ICS kernel | Mirror
Use this in CWM, same as before, to restore the boot.img and modules for Favum ICS, it may work for other Official based ICS, may not, untested.
Notes and Updates
Mirrors added, V0.1 initial release
V0.2: GPU OC 320/400 MHz 2D/3D. Does not play well with ICS, use only with CM10.
Kernel naming and what they mean:
As the kernel development for Jellybean gained momentum, changes to the kernel source and drivers made the kernel no longer compatible with BOTH ICS and JB, so a new branch needed to be built, one for each android version.
Caspar = The trunk kernel, the first base which all other kernels are built from, contains the original OC settings, governors and schedulers, but not much else, pretty stock.
Melchoir = The First branch, this is for ICS only, and is slightly more updated then the JB kernel, but not by far, is pretty stale development wise while I work on the JB kernel.
Balthesaur = The second branch, this is for JB only, and is the more updated and recent and heavily developed kernel by far.
Each kernel release is still compatible with ANY ROM, however it MUST be of the proper android version, Meclchoir should be flashed only to ICS and Balthesaur should only be flashed to JB. Caspar, should you choose to use it, is ICS only as well.
Do not flash these to other android versions, including Honey Comb, they may boot but they will certainly not function correctly.
FAQ
Q: How does this work with any ROM?
A: Installs by taking apart the current boot image, replacing the kernel binary, repacking then reflashing the boot image, and copies the matching modules into your system/lib folder. It keeps the existing ramdisk, which is why it works in between both ICS and JB.
Q: Where did you get your source changes from?
A: Source changes are coming from ezTerry and Godmachine, with guidance from Godmachine. Changes by ezTerry may come from other places, however I can not verify that, and its from his github.
Q: Is this included in any ROM?
A: Yes, this kernel is included with my CM10 builds, including Kuroikaze-Thrive
Thanks go out to:
First off, godmachine / linux society! We've had our spats (rather, I've had mine) however his guidance made this possible.
ezTerry: for giving us the first modded Acer Iconia kernels, also basing some of this work on his work on ezT20 kernel.
Da-pharoah for as always encouraging my work and to try new things.
tybar over at thriveforums.org (he may also be here?) for his work on CM10 and supplying the initial source this began with.
The rest of the guys pitching in over there!
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
wigginst said:
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
Click to expand...
Click to collapse
That depends on the ROM being used so no, I hadn't planned on it. I probably could but its per ROM which is quite a few lol
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Was just thinking of a backup in case. Flashed it to favum and letting it settle right now.
Sent from my PG86100 using Tapatalk 2
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Could you make a revert for his darkside ROM? Sorry for being a pain
Sent from my AT100 using xda app-developers app
stevie13.xo said:
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Sent from my AT100 using xda app-developers app
Click to expand...
Click to collapse
Yeah unless something is different with the kernel binary as well, which I doubt, it shouldnt cause a problem.
As far as I know its the first kernel from source for ics so I don't think any issues will come up.
Edit: I'll try to get a revert zip up for dark side as well, the favum won't work, different ramdisk I think.
Sent from my Galaxy Nexus using Tapatalk 2
Are u saying I can use this kernel on my phone or some specific phone only?
ramoneC said:
Are u saying I can use this kernel on my phone or some specific phone only?
Click to expand...
Click to collapse
For the device this forum is for? In other words its for the Toshiba thrive 10" tablet. Flashing this on anything else can lead to no boots or even bricks. Its for any ROM, not device.
Sent from my Galaxy Nexus using Tapatalk 2
I nearly was going to brick my phone /: maybe not cos your updater-script might have been aborted but the main thing was I could not download it because of some sqlite error
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
ramoneC said:
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
Click to expand...
Click to collapse
Generally speaking, no. What device are you talking about?
Sent from my Galaxy Nexus using Tapatalk 2
old galaxy s5830 < wont matter if it bricked
ramoneC said:
old galaxy s5830 < wont matter if it bricked
Click to expand...
Click to collapse
This kernel won't flash let alone boot on that lol
Sent from my Galaxy Nexus using Tapatalk 2
I have decided to buy googles phone henceforth so I wont have to worry about updating
stevie13.xo said:
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Click to expand...
Click to collapse
Mirrors are up.

[KERNEL] [Samsung JB] Boeffla-kernel 5.3-beta7 <29-06-2014>

Boeffla Samsung Kernel by AndiP
Ported and compiled by Hbohd and P$T
For i9305​
Introduction
Note: The 4.x kernels are only for Samsung based 4.1.x roms!!! Do not install it on CM or AOSP based roms!!!
The 5.x kernels are only for Samsung based 4.3 roms!!! Also do not install it on CM or AOSP based roms!!!
After ausdim's contribution to porting variety of kernels to our phone, I am here to continue his work (he won't maintain it any longer because he simply doesn't own this phone now). Updates will be made as soon as Andi will push them to github.
Here is original thread of i9300 boeffla kernel - CLICK
Here is thread with boeffla ported by ausdim - CLICK
Info
Kernel is compiled using Linaro 4.9.1 with some required changes for our i9305:
No FM radio
No CMA_DMA
No flash and load in Boeffla App
New 'Hbohd preset' and 'PST preset' which are just our everyday use settings.
New 'Hbohd' and 'PST' equalizer preset - just our favorite.
Apart from that, everything is same as in i9300 version.
Please for any questions problems or anything else ask here and not on I9300 thread.
Credits
P$T (for helping hand with compiling and endless patience and time)
Ausdim (basing on his work and he always gives helping hand)
Yank (his endless patience and knowledge to help with any issue)
AndiP (for kernel base and another kind help)
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 CWM recovery and safely store your personal data before you flash a new kernel.
Source:
Here it is, github link! - CLICK
5.2 STABLE compiled with linaro 4.8.3 toolchain -->HERE
Newest version 5.3-beta7 compiled with linaro 4.9.1 toolchain (new ramdisk NE4) --> HERE
Camera bug info:
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solution:
1. Read this thread and follow steps --> click
2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my ported kernel
3. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Installed let see how it goes...
Good work
Tank's
Sent from my GT-I9305 using Tapatalk 2
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Thanks.
Do you have any link or something where we can read about zzmoove governor tunables? I was searching, and searching and nowhere have I found a good explanation of all parameters.
I should probably look into sources you just gave a link for, but I am too tired atm.
Edit:
Oh that wasn't link to sources, but it doesn't matter, there has to be one somewhere in Boeffla thread.
Sent from my GT-I9305 using Tapatalk 2
My 'sources' are only one file - defconfig. The rest is completely same as Andi's sources
And for any explanation of zzmoove configurables - there is some documentation, quite well explained: https://github.com/andip71/boeffla-...48257af1b13/drivers/cpufreq/cpufreq_zzmoove.c
Cheers
Thanks for the port.
Over night I find this one better on battery than the last port. See how it goes with a bit of heavy usage today.
Sent from my GT-I9305 using Tapatalk 2
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
kazoum said:
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
Click to expand...
Click to collapse
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Hbohd it will continue the port of the boeffla kernel since i moved to the i9505.
Also i see Andip make some changes to the boeffla sound driver so it will work better.
Thank's
After 1 day with new kernel I can say the battery improve are the best an till now. Great job
Sent from my GT-I9305 using Tapatalk 4 Beta
Nice.. good job man..
Sent from my GT-I9305
Hbohd said:
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Click to expand...
Click to collapse
Well, I'm sad that a developer leaves this phone, but it is awesome to know that Boeffla will continue to be ported to I9305! The best part is the frequent updates Thumbs up!
I'm gonna try your port and will say something later.
beta6
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
dyy said:
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
Click to expand...
Click to collapse
What if I told you...
Beta7 is better than beta6
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
kazoum said:
What if I told you...
Beta7 is better than beta6
Click to expand...
Click to collapse
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Sincerely, I haven't experienced any random distortions of sound, everything works great. Obviously, if you raise headphone or speaker volume too high, it may be distorted, but it is understandable.
Or did you want to mention the problem with distorted/freezing/stuttering audio on screen-off? That was discussed and it might be caused due to too low screen-off frequency or too high sampling_rate and sampling_rate_sleep_multiplier. If it's the problem, try to change to zzmoove-optimised as it has this values changed a little bit.
About Perseus' screen calibration settings... As for now, introducing such thing would require adding multiple scripts to support variety of configurations for it (in boeffla app), change app to stweaks (which is quite tough task) or wait for new app which will come in some time, made by Andi (and in my opinion, will let us easily configure what we want).
What's more, personally I liked these calibrated colours, however, original colours also seem good to me So nowadays, I do not need it, although I might look at it in my free time and see what can I achieve
dyy said:
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
The fact is, that ausdim released beta4 or 5, I don't remember exactly, and then was my release beta7. And we somehow skipped beta6, you are right! However if I were you, I wouldn't take zzmoove 0.5 as 'unstable'. It introduces a great deal of new configurables that, I suppose will be really beneficiant in the future (when we all will learn what they mean ).
Version 0.5 is ONLY unstable when you are changing governors frequently. Otherwise, it is really efficient and bettery-friendly one (same as 0.3). In addition, it's my beloved governor since its start
Furthermore, new betas always consist of other updates (like Linux kernel upstream to 3.0.82, fixes, optimizations) so it is always worth to use the newest one!
As for now, you may stay with your actual beta version or wait for next update. Andi is testing comparison between zzmoove 0.3 and 0.5 right now, so he haven't pushed any sources, therefore I can't release any new update We are all impatiently waiting for the results i think!
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
inzomnia said:
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Have the same problem, no matter the governor i choose.
I try zzmove battery and pegasusq boeffla battery saving
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
I had this issue with boeffla but only when i used rxtreme rom, i never have it with ripper rom!

[KERNEL][NOUGAT] AKLU Kernel

Praise God! The AKLU kernel has arrived on the Galaxy Note Edge in the flavor of NOUGAT!
NOTE: I highly recommend turning off THERMAL CORE CONTROL! Use THERMAL TEMPERATURE THROTTLE instead. Thermal core control has been known to cause random reboots on this kernel before when gaming or during heavy use. You can use Kernel Adiutor to adjust these settings.
TBLTE AKLU KERNEL for AOKP 7.1.2!
MAY work for other LineageOS based roms, e.g., RR, PAC,AOKP, LineageOS, etc.
Download:
http://www.mediafire.com/file/pcownjeat1o2oub/AKLU-TBLTE-AOKP-N-20170427_kexec.zip
TBLTE AKLU KERNEL for SLIM 7.1.1!
MAY work for other AOSP based roms, e.g., OmniRom, LiquidDark, SlimRoms, AOSP, etc.
Download:
http://www.mediafire.com/file/cl0ahc00zmxcai2/AKLU-TBLTE-SLIM-N-20170224.zip
Logs and features:
Modified TBLTE kernel. Modified by the Alaskalinuxuser.
https://thealaskalinuxuser.wordpress.com
20170427
- Updated kernel to include kexec hardboot for MultiRom support.
20170316
-Update for OMS support.
20170217
- Fix WiFi hot spot error for Nougat.
- Overclocked the GPU from 600MHz to 633MHz
- Overclocked the CPU from 2649MHz to 2688MHz
- Added governors: Bioshock, Lionheart, Nightmare, Darkness
- Removed input boost, use cpu boost instead
- Added I/O schedulers: FIOPS, ZEN
I haven't loaded up AOKP yet but this kernel is working beautifully with RR and the data fix. You rock man.
JeremySS said:
I haven't loaded up AOKP yet but this kernel is working beautifully with RR and the data fix. You rock man.
Click to expand...
Click to collapse
JeremySS,
Thank you for the kind words!
In theory it should work with any nougat rom based on LineageOS, but I have not proved that personally. Thanks for confirming that for RR and providing the feedback!
AlaskaLinuxUser said:
JeremySS,
Thank you for the kind words!
In theory it should work with any nougat rom based on LineageOS, but I have not proved that personally. Thanks for confirming that for RR and providing the feedback!
Click to expand...
Click to collapse
You do good work. Do you have a donate link?
JeremySS said:
You do good work. Do you have a donate link?
Click to expand...
Click to collapse
Thanks for the thought, but I do not accept donations. I just tinker for fun, and have my own rewards. Besides, guys like @Mickey387 did all the heavy lifting, I just try to put the device trees and vendor blobs to good use, with a few edits here and there. Glad to know that my work is appreciated, though.
The slim 7 aklu kernel appears to be slightly unstable at this time. Please use with caution.
EDIT: Updated the kernel and fixed a few bugs that I missed in the first build. SHOULD be better now. Please turn off thermal core control for best performance!
Also, if you flashed superSU in Slim to root it, you need to flash the kernel, then immidiately flash superSU, then reboot.
AlaskaLinuxUser said:
The slim 7 aklu kernel appears to be slightly unstable at this time. Please use with caution.
EDIT: Updated the kernel and fixed a few bugs that I missed in the first build. SHOULD be better now. Please turn off thermal core control for best performance!
Also, if you flashed superSU in Slim to root it, you need to flash the kernel, then immidiately flash superSU, then reboot.
Click to expand...
Click to collapse
Hi... help me pleeze make kernel fo me n915d. really I want to give him a second life on his rom
All works fine but no sim card
Imei and everything else is.
Now used ramkernel v5_n915d and note 7 port.
but I want to Aokp 7.1.1
Here's how to do kernel ram121
github.com/Ram121/RamKernel_N4/commit/360a66df3d38b298896bfd161a2db2812f7b1efa
Steem75 said:
Hi... help me pleeze make kernel fo me n915d. really I want to give him a second life on his rom
All works fine but no sim card
Imei and everything else is.
Now used ramkernel v5_n915d and note 7 port.
but I want to Aokp 7.1.1
Here's how to do kernel ram121
github.com/Ram121/RamKernel_N4/commit/360a66df3d38b298896bfd161a2db2812f7b1efa
Click to expand...
Click to collapse
Please compile kernel with this config....
I do not have now Linux,Mac_os
apq8084_sec_tblte_dcm_defconfig
Steem75 said:
Please compile kernel with this config....
I do not have now Linux,Mac_os
apq8084_sec_tblte_dcm_defconfig
here's another
apq8084_sec_tblte_dcm_defconfig
Click to expand...
Click to collapse
Steem75,
I am sorry, but at this time I do not have the resources to help you.
AlaskaLinuxUser said:
Steem75,
I am sorry, but at this time I do not have the resources to help you.
Click to expand...
Click to collapse
then help me with advice
I make zImage with gcc eabi 4.8. End only *****_DCM_Defconfig
Log -hastebin.com/gudipabona.coffeescript
but it is not boot my note edge . Maybe because I packed it in your boot.img?
Or because compiled with only one config?
Praise God! A new kernel update!
The AKLU kernel for the AOKP has been updated to include kexec hardboot for rmultirom support! See the OP for details!
I have noticed that many of these processors on the note4/edge are of a good bin.. Mine can run about 45mv off from stock.. Have you ever considered adding CPU Voltage control to help a bit with battery longivity? I do thank you for your excellent work, your rom's and kernels truly show that it is the programmer not the hardware that matters.... Godspeed....
afbcamaro said:
I have noticed that many of these processors on the note4/edge are of a good bin.. Mine can run about 45mv off from stock.. Have you ever considered adding CPU Voltage control to help a bit with battery longivity? I do thank you for your excellent work, your rom's and kernels truly show that it is the programmer not the hardware that matters.... Godspeed....
Click to expand...
Click to collapse
Thanks afbcamero, those are kind words.
On my MM kernels I did implement UV, but the way I did it in MM fails to pass in the N kernel. Not because it doesn't work, but rather that new build standards don't allow it. With the recent birth of my son, I have not had time yet to go back to it and figure out what was wrong yet. Are you familiar with kernel work? You could look at my github and my kernel source, perhaps you could show me where I went wrong?
If I can get passed that, I can implement the UV again. I also have the same problem for GPU voltage control, which I used to put on my MM kernels as well.
Perhaps when life slows down a bit, I can look back into it.
Sent from my unknown using XDA-Developers Legacy app
Oh I see, i honestly never looked at the structure of Nougat kernels. Any time I want to implement a change somebody does it better and beats me to the punch.. I will look at it just in case I see something..
On another note, these things however fun (development) not being trully important, may your family be blessed by the big guy.
Thanks! I'm always open to ideas on kernel improvement.
Sent from my unknown using XDA-Developers Legacy app
sim card not detected
Im on RR (7.1.2 micky387 build) but when i flashed the kernel, sim card isnt detected...anybody got the same issue? Any fix for that?
N915f on 6.0.1 modem
Ricationarli said:
Im on RR (7.1.2 micky387 build) but when i flashed the kernel, sim card isnt detected...anybody got the same issue? Any fix for that?
N915f on 6.0.1 modem
Click to expand...
Click to collapse
You could try the data fix zips in the 915t T-Mobile thread.
Sent from my LG-H811 using XDA-Developers Legacy app
AlaskaLinuxUser said:
You could try the data fix zips in the 915t T-Mobile thread.
Click to expand...
Click to collapse
Tried both, sadly didnt work
Ricationarli said:
Im on RR (7.1.2 micky387 build) but when i flashed the kernel, sim card isnt detected...anybody got the same issue? Any fix for that?
N915f on 6.0.1 modem
Click to expand...
Click to collapse
I had the same issue. No fix by me.
+1
Sent from my SM-N930F using XDA-Developers Legacy app

Categories

Resources