{
"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"
}
Base: N7100 KK Sources
Linux 3.0.31
Compiled using latest ArchiToolchain 5.2.0
ArchiDroid Optimizations
Using AnyKernel method (compatible with all ROMs for both AOSP and Samsung)
And many other awesome things I have no time to list
ArchiDroid Optimizations:
- Fully optimized for Samsung Galaxy S3 (-marm -march=armv7-a -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp)
- Compiled with O3 optimization level (-O3)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
Click to expand...
Click to collapse
Download
What to expect:
- Awesome stock battery life on AOSP ROMs (due to Samsung sources and not smdk4x12)
- Blazing fast (Deep advanced optimizations, Linaro toolchain, this is the beast)
- High compatibility (AnyKernel method, the kernel should work on all ROMs)
What to expect in future:
- You tell me
What to NOT expect:
- Many CPU or I/O governors # We don't need overhead, you can achieve nearly the same just by tweaking governor to your needs
- Features I don't like/need
- Dualboot (see above ^)
- F2FS (see above ^, however this one depends on kernel upstreaming, as f2fs is merged)
ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.
AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.
AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.
SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)
SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port
ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
Flashing instructions:
1. Make sure that you have stock kernel already flashed (the one which comes with your ROM), if you're running custom kernel already, reflash your ROM without wipe, this will also flash stock kernel. This is ultimately important, DON'T FLASH ARCHIKERNEL ON ANOTHER CUSTOM KERNEL, you may face various issues you've never seen before.
* This is because ArchiKernel uses AnyKernel method - it pulls ramdisk from your current kernel. If you brick your phone by flashing AK on top of custom kernel, you know who will be responsible for that.
2. Flash ArchiKernel zip.
3. Profit!
Updating instructions:
1. If you arleady have older ArchiKernel version flashed properly with above instructions, and changelog doesn't state otherwise, just flash the .zip with new version of AK.
2. No wipes, cleaning dalvik cache or anything else is required, flashing zip is enough.
3. Profit!
Bugs:
None known
XDA:DevDB Information
[EOL] [KERNEL] [AOSP/Samsung/Ports] [ArchiToolchain 5.2] [01/10/15] ArchiKernel V2.1, Kernel for the Samsung Galaxy S III I9300
Contributors
JustArchi, Moster2
Source Code: https://github.com/ArchiDroid/ArchiKernel
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-06-17
Last Updated 2015-11-12
Reserved
Reserved
Last one.
Great job! Amazing to see a dedicated thread for this beauty.
Will report the experience
V1 uploaded in download section on the top of the thread. It should work with all AOSP ROMs but you tell me if it does. Don't flash it on Sammy (yet). Let me know if I screwed up something, it's late .
will test on omni,thanks
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
coto39 said:
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
Click to expand...
Click to collapse
At some point I'll definitely consider adding ArchiKernel support in ArchiDroid app, but it won't come too fast.
However, you can still "tweak it' in various ways. SetCPU, TricksterMod and similar apps are only a few examples. Boeffla Sound Control app (not boeffla config) will work as well. But think twice if you want to do, as ArchiKernel is pretty damn tweaked right after booting.
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
beeeto said:
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
Click to expand...
Click to collapse
If you want to know my opinion - Current smdk4x12 source used in all AOSP kernels is a crap. Somebody screwed up something really hard, I looked at the sources and there are over 7 hundred of different files (comparing to Update13), half of the updates from Update11, Update12 are not even included, while Update13 is not included at all. Whole kernel is one big mess and I have no idea how it even boots. It contains so many merge derps and hacks/workarounds that it hurts. I didn't even want to fix it, too much work to do. I started from clean stable and battery friendly Update13 base.
After flashing first alpha version of my kernel I immediately noticed significantly improved battery life, same as on Sammy ROM. So now I have my perfect combo, ArchiDroid 2.X AOSP speed and ArchiKernel Sammy battery life. Whatever you say, I'm keeping this baby. I love this kernel.
Big credit goes to @Yank555 and @Lord Boeffla because they're true kernel developers, I've made my own kernel based mostly on their commits (but not only, I added my own part as well and I'll add more soon).
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Add it to the OP!
While not everyone actually reads even the first post, even fewer people would actually bother reading the whole first page.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
skim0322 said:
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If need be, but the stock kernel alone should be enough if you get hands on a .zip.
Awesome
Sent from my GT-I9300 using Tapatalk
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
May I ask for a flashable zip file of the stock kernel..Thanks.:good: I would like to try this
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
i am on archidroid 2.4.6 with boeffla kernel.u mean that i cannot flash your kernel over my current kernel?
Are cam bugs gone since you did not upstream it to the 3.101?
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
Related
SlimSaber n7000 Uber 4.8
Making SlimKat more faster and smoother
{
"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"
}
SlimSaber: Uber toolchain 4.8.4
SlimKernel: Uber toolchain 4.9.4
Disclaimer
I'm not responsible for any damages on your device.
After having a good response for some months in the i9100 thread, I decided to share this build since I also built for n7000.
My focus is to optimize the ROM in many areas and compiled it with custom toolchain Uber for more performance and smoothness.
I choose SlimRoms as a base because it is a lightweight and not a bloated ROM, but it still has rich features. Combined with some of CM features, I bake a ROM that has more useful features but still lightweight.
The ROM and the kernel are tested by me first before I make it available online. I could have overseen something during testing, please be understand.
Features summary
See here. Thanks a lot Harsha Raj!
Installation instructions
Coming from 4.1.x or 4.2.x or 4.3.x or another ROM to 4.4.x:
Flash a kitkat compatible recovery from here. A kernel is a recovery and a recovery is a kernel.
Reboot to recovery. Not to the system!
Full wipe: data, cache, dalvik cache.
Mount system and format system partition manually.
Flash the unofficial build.
Flash gapps from here. Please use the 'minimal' one since our system partition is not big enough to carry the 'full' one.
Coming from previous unofficial build:
Wipe cache and dalvik cache.
Flash the unofficial build.
No need to re-flash gapps. Gapps will be restored back automatically by backup tool during flashing.
Known Issues
Music player stops playing music from sdcard after some time. See here - Fixed since 20141221.
Occasional freezes if using governor other than ondemand. Use only ondemand for the time being.
F.A.Q
See second post.
Latest release
Latest 4.4.4: 20151021
Latest 4.4.3: 20140616
Latest 4.4.2: 20140604
Full Changelog
androidfilehost
Download
androidfilehost
Credits
SlimRoms - The SlimRom team
Uber toolchain - Cl3Kener
SlimSaber banner and signatures - kroz
Special Thanks
HardCorePawn - for his great work making the SlimKat available on n7000 device.
Dorimanx - for patches to disable sqlite fsync.
Sources
https://github.com/SlimSaber
How To Build
See this post
F.A.Q (Freaking Annoying Questions)
How to disable CellBroadcastReceiver
There are three possibilities to disable it:
Disable its setting: See here
Remove it: Settings - SlimCenter - SlimSizer - Delete CellBroadcastReceiver
Freeze it: Use Titanium Backup and freeze 'Mobile Broadcast'
Root doesn't work!
Enable 'Developer options'
Go to Settings -> About Phone
Tap on the Build Number 7 times
Go to Settings -> Developer options -> Root access
Choose 'Apps' or 'Apps and ADB'
How to set zzmoove profile
Available zzmoove profiles:
Default
Will set governor defaults
Yank Battery
A very good battery/performance balanced setting - DEV-NOTE: highly recommended! -
Yank Battery Extreme
Like yank battery but focus on battery saving
ZaneZam Battery
A more 'harsh' setting strictly focused on battery saving - DEV-NOTE: might give some lags! -
ZaneZam Battery Plus
NEW! reworked 'faster' battery setting - DEV-NOTE: recommended too! -
ZaneZam Moderate
NEW! setting based on 'ZaneZam Optimized' which has mainly (but not strictly only!) 2 cores online -
ZaneZam Optimized
Balanced setting with no focus in any direction - DEV-NOTE: relict from back in the days, even though some people still like it! -
ZaneZam Performance
All you can get from zzmoove in terms of performance but still has the fast - down scaling/hotplugging behaving
ZaneZam InZane
NEW! based on performance with new insane scaling active. a new experience!
ZaneZam Gaming
NEW! based on performance with scaling block enabled to avoid cpu overheating during gameplay
How to set the zzmoove profile:
Go to Settings - Advanced options - Performance - choose zzmoove governor
Press menu key and choose Governor Settings
Search for 'profile_number' and pick a number from above
Press 'Apply values' and eventually enable 'Apply on boot'
Only profile_number can be persisted, any other gov settings will be changed based on the chosen profile template.
* Media scanner eating my battery
* CPU stuck at 1.2 GHz
* Random music player stop
For media scanner problem, try this following solution first: http://forum.xda-developers.com/showthread.php?p=47868557, also see this.
At these problems could have the same root cause: The kitkat sdcard fuse daemon issue on the Exynos 4210 family of devices. There is no fix yet. See this thread for more information.
How to check corrupt partition
See here: http://forum.xda-developers.com/showpost.php?p=50264173&postcount=9137
I have excessive RILJ wakelocks
See here: http://forum.xda-developers.com/showpost.php?p=50227440&postcount=9049
and here: http://forum.xda-developers.com/showpost.php?p=50758124&postcount=9790
My recovery won't flash the 4.4 zip... aka "Status 7 error"... what do I do?
You need a kitkat compatible cwm. See installation instructions in 1st op
How to change DPI?
Currently, this feature hasn't been ported... so you'll need to install Texdroider DPI from the playstore... or edit /system/build.prop and change ro.sf.lcd_density to the desired value
Stuck at the Samsung logo
Follow this steps to get rid of the stuck and to have back your valuable data:
Go to recovery and make a twrp/cwm backup.
Do a full wipe + mount system + format system.
Flash the rom + gapps.
Reboot to rom and skip the setup wizard.
Go to recovery again and advance restore your data only.
Reboot.
My timezone is reset and it is wrong
See this workaround from rkoby13 or eskriminal here: http://forum.xda-developers.com/showpost.php?p=45572515&postcount=2668
What is the difference between these builds and the official builds?
Short version: It is unofficial nightly builds whereas official one is stable and weekly builds.
Long version: It is built using the same source (github) like the official one but with these following additional changes:
Compiled using SaberMod 4.8 & SaberMod 4.7 toolchain combo.
Contains some cherry-pick commits. See changelog for more details.
Faster? Smoother? Here are some responses from users: rkoby13, rkoby13, rkoby13, kroz, MarioFan1998, alkspo, vladimirheroj, bodzik155
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
Goodies
SlimKernel
These following kernels are only for testing purpose. If you don't know what it is, don't flash these:
SlimKernel_v4.2.22-n7000-signed.zip
KrozMod Collection
A theme collections by kroz, visit his thread here: http://forum.xda-developers.com/showthread.php?t=1960233
Signatures by kroz
SlimSaber
SaberMod SlimRoms
Download here: http://d-h.st/users/kroz/?fld_id=25717#files
Bootanimation by kroz
Download here: http://d-h.st/users/kroz/?fld_id=28876#files
More information about this bootanimation, see here: http://forum.xda-developers.com/showpost.php?p=47920976&postcount=5592
Bootanimation by thereald
Download here: http://forum.xda-developers.com/showthread.php?t=2499512
To follow the i9100 release:
From now on, if you want to use custom kernel, the kernel needs to support new mali r3p2.
SlimSaber-n7000-4.3.1-20131112.zip
Changes:
* Integrated r3p2 mali as default.
* Bunch of changes in framework av.
* Updated Contact, Mms and Phone with some fixes after some months no change at all.
* Some memory leak fixes in framework base.
* See changelog
Welcome to the Note, SlimSaber @fusionjack
Thanks for this SlimSaber.
Downloading:good:
Just tried it. it's quite responsive and snappy so far, since bangsti is left I really missed slim build with these customization and smoothness.
thanks.:good:
just added mirror on dev-host: http://d-h.st/users/fusionjack/?fld_id=28093#files
thanks for the feedback.
Altough I was very, VERY satisfied with my previous ROM, I decided to give a shot to SlimSaber Installed and restoring apps right now but I must say, that the first impression is like...
Vaiet said:
Altough I was very, VERY satisfied with my previous ROM, I decided to give a shot to SlimSaber Installed and restoring apps right now but I must say, that the first impression is like...
Click to expand...
Click to collapse
lol...i like dragon ball too. glad that you like this build.
fusionjack said:
lol...i like dragon ball too. glad that you like this build.
Click to expand...
Click to collapse
Dear sir... There we're times I have flashed a lot. And a lot I mean, that my wife was so angry, that she wanted to throw my phone through window I've seen some things, flashed only good and solid roms... But this one just blows my mind. I tought after crDroid, that there could be nothing better and now I know, how wrong I was Keep up the good work, because SlimSaber is just brilliant and amazing.
Vaiet said:
Dear sir... There we're times I have flashed a lot. And a lot I mean, that my wife was so angry, that she wanted to throw my phone through window I've seen some things, flashed only good and solid roms... But this one just blows my mind. I tought after crDroid, that there could be nothing better and now I know, how wrong I was Keep up the good work, because SlimSaber is just brilliant and amazing.
Click to expand...
Click to collapse
the same like my wife, lol...without i9100 community feedback & supports i'll never reach this state.
thanks for encouraging me to continue this build. :good:
don't forget to give slimbean also a credit too. they implemented some unique features that are used in many custom roms.
Holy crap this is absurdly smooth
Also it's the only 4.3 ROM I've seen that has a proper CRT effect
This is freaking amazing. Thank you sooo much :good:
thx @fusionjack, for new Funny Rom!
let's ride
LAKAME_MAN said:
Holy crap this is absurdly smooth
Also it's the only 4.3 ROM I've seen that has a proper CRT effect
This is freaking amazing. Thank you sooo much :good:
Click to expand...
Click to collapse
bently73 said:
thx @fusionjack, for new Funny Rom!
let's ride
Click to expand...
Click to collapse
your welcome and enjoy the rom.
Sent from my GT-I9100 using Tapatalk
fusionjack said:
your welcome and enjoy the rom.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Oh, I am enjoying it Right now I'm fighting with it to get my desired lockscreen from Candy Shop. Hope it will work (finally)
Thanks for the new slim build.I am long time user of slim bean.The only feature I am missing is HALO.Is there any chance of implementing it in your Rom?
Easy to Instal!
clean instal + rom + AromaSlimgapps + 220 Dpi
and now wait & seeeeeeee battery drain!
zee3241 said:
Thanks for the new slim build.I am long time user of slim bean.The only feature I am missing is HALO.Is there any chance of implementing it in your Rom?
Click to expand...
Click to collapse
unfortunately no.
Is it ok to dirty flash over orignal slimbean 4.3.1 ? Thanks
Edit:
Ok, i did it and it's working fine.
from my Note..
Moretz Kernel 0.2.2 - Galaxy Note 8.0 EditionGT-N5110 & GT-N5100
Features:
Linux 3.0.101
Frandom
Network speed enhancements
Dynamic read ahead
CPU OC to 1.8GHz
GPU OC to 533MHz
CPU Voltage Control (OV/UV)
Tuned ZZMoove CPU governor (removed all other governors)
Intelligent CPU core hot plugging
Touchboost control, set to 800MHz
ARM CPU topology
LCD frequency switching (40Hz on screen dim, 60Hz on active)
Intelligent GPU scaling (Mali GPU control)
Lots of other fixes/tweaks
Intelligent zipalign at boot (init.d)
Intelligent sql db optimization at boot (init.d)
So, what's so special here?
A few things actually. I grabbed various code bits from many well known developers and worked some of my own magic on this build. First, I bumped the kernel up to 3.0.101 (FINAL) form kernel.org as a base on top of the stock CM 11.0 kernel. Once I pushed all of the enhancements listed above, I focused on tuning ZZMoove to balance performance and battery. I believe I've succeeded in that realm, so all other governors have been removed. This is a flash and forget kernel package. That's what makes it special ... the users do not have to do any tuning, it works, and it works well.
Credits:
Faux123, Andy P, googyanas, psndna88, ryukuri, sbrissen, Cyanogenmod team and may others. Please let me know if I missed you.
Source Code:
https://bitbucket.org/carvsdriver/android_kernel_samsung_smdk4412 (Moretz-New Branch)
Standard Disclaimer:
By flashing this you hold the developer (car vs driver) and anyone else not responsible or liable for any damage to your device, up to and including hard bricking. Basically, there's no warranty - flash at your own risk.
This release is not affiliated to CyanogenMod or Cyanogen Inc. This is my own personal work with lots of kangs from others.
This was tested with CM-11 on a GT-N5110 device. Any other devices or ROMs may not work or exhibit poor behavior. That being said, I only support use of this kernel with CM-11 and the GT-N5110.
Requirements:
Device - Samsung GT-N5110
ROM - CyanogenMod 11.0
XDA:DevDB Information
Moretz Kernel - Galaxy Note 8 Edition (N5110 & N5100), Kernel for the Samsung Galaxy Note 8.0
Contributors
car vs driver, psndna88, faux123, googyanas, AndiP, sbrissen
Kernel Special Features: GPU/CPU OC, UV/OV, UKSM, HotPlug, ARM Topology, LCD Freq Scaling, Linux 3.0.101
Version Information
Status: Stable
Current Stable Version: 0.2A
Stable Release Date: 2014-03-21
Created 2014-03-21
Last Updated 2014-07-03
Change Log:
Moretz 0.2.2 -- Upstream CM11.0 Changes Merged -- 7.4.2014
98865a3: n_tty: Fix n_tty_write crash when echoing in raw mode
7735075: mc1n2: Allow swapping of microphone ADC channels
ed8b659: smdk4412: update sound soc and codecs
5e96596: d710: build stage2 initramfs into kernel
8a5d38c: Fix CVE-2014-3153
6922ae0: Merge "synaptics_s7301: add disabling keypad" into cm-11.0
daf9635: Merge "smdk4412: cypress-touchkey - add keydisabler" into cm-11.0
fd94358: n_tty: Fix n_tty_write crash when echoing in raw mode
969b384: mc1n2: Allow swapping of microphone ADC channels
eba4e20: smdk4412: update sound soc and codecs
Moretz 0.2.1 -- Upstream CM11.0 Changes Merged -- 4.8.2014
c0dce37: dm crypt: optionally support discard requests
15b6c83: dm table: share target argument parsing functions
1886fef: dm: ignore merge_bvec for snapshots when safe
2b791d9: dm: suppress endian warnings
Moretz 0.2a -- Initial Release -- 3.21.2014
Instructions:
1. Download the flashable zip
2. Reboot into recovery
3. Flash the zip
4. Reboot
5. Done
I like to make things simple. Let your device boot up and that's it. No configuration necessary. But, if you want to screw with the CPU governor and ZZMoove settings, I made that easy for you. Just edit the zzmoove file in your init.d directory with the settings you want and reboot.
Click to expand...
Click to collapse
Code:
[CENTER][SIZE="5"][COLOR="Magenta"][B]GT-N5110 Download link:[/B][/COLOR][/SIZE]
[url]http://d-h.st/Gkd[/url]
[B]Version[/B]: Moretz-0.2.2
[/CENTER]
Code:
[CENTER]
[SIZE="5"][B][COLOR="magenta"]GT-N5100 Download link:[/COLOR][/B][/SIZE]
[url]http://d-h.st/ZyZ[/url]
[B]Version[/B]: Moretz-0.2.2
[/center]
Just a couple more things ...
Please do not post mirrors, if one is needed just let me know and I'll post one.
Please leave a review on this project by clicking here.
If you like my work, feel free to buy me a beer or pack of guitar strings by donating.
Click to expand...
Click to collapse
[/CENTER]
How to properly report bugs:
When reporting a bug, you must provide me with some very specific information so that I am able to either reproduce the problem or diagnose it based on logs. If you cannot provide information that I need, I cannot attempt fix the issue.
If the device is crashing:
Please make a copy of your last_kmsg immediately after rebooting the device.
Please make a copy of your logcat for the subsequent reboot.
Attach both files to your bug report and specifically state exactly what happens (are there steps to reproduce it?).
In all cases, please provide a logcat of when the issue occurs or specifically describe what is happening and how you can reproduce the error.
If you have any current issues prior to flashing my kernel, don't expect me to fix them.
The more detail you provide, the more helpful your bug report will be for me.
Feature Requests:
I'll make this one easy, I don't do feature requests. I used to do that, it became a real pain in the ass to keep everyone happy and the project I was working on bug free. Put simply, I put this together to work specifically for me and then decided to share it here. If at some point I decide to add new features, then I'll release new versions to you.
car vs driver said:
Reserved just in case.
Click to expand...
Click to collapse
I'm looking into building my own kernel for the konawifi because I feel like we need more kernel options, so thank you for this awesome customized kernel.
ztotherad said:
I'm looking into building my own kernel for the konawifi because I feel like we need more kernel options, so thank you for this awesome customized kernel.
Click to expand...
Click to collapse
You're welcome, that's what this one is for. Makes the device scream and battery life is excellent.
Sent from my Nexus 5 using XDA Premium 4 mobile app
car vs driver said:
You're welcome, that's what this one is for. Makes the device scream and battery life is excellent.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
freakin' nice. definitely can't wait then! thanks again for your awesome gift to the Note 8.0 family.
is n5100 model will be supported in next future ?
messi2050 said:
is n5100 model will be supported in next future ?
Click to expand...
Click to collapse
Would you be willing to test? Only reason I didn't publish for n5100 is because I don't have one to verify that I didn't break anything.
I just have to update a few configs and run a new build, let me know.
as an owner of the n5100 I´ll be very interested in your work. so my first question - will this kernel work with probam 1.3.2? maybe I could test it
redukt said:
as an owner of the n5100 I´ll be very interested in your work. so my first question - will this kernel work with probam 1.3.2? maybe I could test it
Click to expand...
Click to collapse
I suppose it should, I did a quick check and looks like that ROM uses the same base 3.0.y kernel that CM 11.0 does. The partition scheme on the devices is the same too (both devices us /dev/block/mmcblk0p5 for the boot partition) ...
There's only one real way to find out though, someone has to flash it - worst case is that it doesn't boot up.
Go ahead and give this a rip and let me know how it goes. It's the same build as the OP with the 5100 defconfig updated to include the features that I added for the 5110.
Download:
REMOVED ... SEE OP FOR DOWNLOADS
MD5:
7864a8e5eb18321c2201cba314fc7a06
If it doesn't boot, just reflash your previous ROM - that'll replace this kernel with whatever one is included there.
Yeah, kernel runs nice So I`ll kept my device on standby, make a wow raid and check the battery stats
Thx for your hard work
Assuming all goes well, I'll update the op to state that both devices are supported and working.
Sent from my Nexus 5 using XDA Premium 4 mobile app
car vs driver said:
Would you be willing to test? Only reason I didn't publish for n5100 is because I don't have one to verify that I didn't break anything.
I just have to update a few configs and run a new build, let me know.
Click to expand...
Click to collapse
i'm using original rom 4.1.2 now so i can't test it sorry
3,5 h standby time loosing NOTHING in battery percentage - full 100% So I`ll check this tomorrow and report my results
edit: very nice
{
"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"
}
edit: bug: no 3g network :/
Hmmm ... no 3G? Y'know what, I think I know why. I'll post another build for you to test in a bit.
Edit: @redukt .... give this one a rip: <EDIT>SEE OP FOR DOWNLOADS.</EDIT>
car vs driver said:
give this one a rip:]
Click to expand...
Click to collapse
3G runs now
Many thanks for your quick reply
Excellent. I'm going to update the OP and support both devices then. Thanks for the quick turn around with testing, I appreciate it.
does anybody tested it on AOSB rom?
lolek2382 said:
does anybody tested it on AOSB rom?
Click to expand...
Click to collapse
yeppp, runs with AOSB 1.3.2
car vs driver said:
Hmmm ... no 3G? Y'know what, I think I know why. I'll post another build for you to test in a bit.
Edit: @redukt .... give this one a rip: <EDIT>SEE OP FOR DOWNLOADS.</EDIT>
Click to expand...
Click to collapse
3G is working on my N5100 did I download the updated file just install a few minutes ago oh thankyou for supporting our tab the the Devs on the the better
Info copied from original thread
{
"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"
}
I am NOT resposible for any damage done to your device, your neighbor, or any other things you like/hate.
Introduction:
This is my first kernel for any Android device. I created it because I want to get the best out of my device. It initially started with some optimizations regarding SaberMod 4.9 compatibility but I tought why not optimize it even more.
About:
This Kernel is based on the official CM12 kernel, therefore it should work with any Rom using the stock CM kernel too (Like Carbon and Liquid). I run it together with Carbon here, all tests I do will also be done using Carbon. The Kernels features will get more with time
Features and Commit History:
Check 2nd Post!
Installation Instruction:
THIS DOES ONLY WORK ON UNLOCKED BOOTLOADER!
When you're on CM/a CM based Rom:
Flash the zip file in recovery
When coming from Stock:
Flash the boot.img included in your ROMs zip file using fastboot. Flash a CM based Rom then and flash the Kernel zip file again as the Rom overrides the Kernel.
Download:
Alpha version for SGP611/SGP612/SGP621 with XZDualRecovery Integrated
In the attachments
+ Manually extact modules.zip to /system/lib/modules and set 644 perms
Official:
M5 Kernel (Release Versions)
https://dl.myself5.de
M5 Kernel (Test Versions)
https://testing.myself5.de
Thanks/Credits:
DooMLoRD (and therefore all guys he thanked listed below) - for a lot of Commits
FreeXperia Team (especially Jerpelea) - for too many things!
Kali- - to help get the correct dtbTool parameters for a bootable kernel
Faux123 - for lots of patches, you rock dude!
koush & all CyanogenMod maintainers - for too many things!
Dees_Troy & TeamWin - for their excellent work on TWRP Touch Recovery
Phil3759 - for his excellent work on PhilZ Touch Recovery
myfluxi - for a lot of great patches
flar2 - for a lot of great patches
dbolivar- toolchain fixes
FranciscoFranco - for Cortex-A15 optimizations, bunch of other things!
CarbonRom Team - for too many things!
vishal-android-freak - for too many things!
phaseburn - for being a good friend and helping me with almost everything !
sreinst1 - for too many things!
infected_ - for help with SM!
pec0ra - for fast_hotplug
AndroPlus - for too many things!
sparksco - for the SaberMod Toolchain
YoshiShaPow and Frap129 - for SaberNaro Toolchain
Team AOSPAL - for the Kernel Optimizations
Panic Brothers - for sponsoring me a Z3C!
My Big Brother Eric - for helping me keeping focused on Development!
My friends Silas and Max - for letting me use their servers and being awesome!
If I forgot you, please tell me.
Source Code: https://github.com/Myself5/android_kernel_sony_msm8974/tree/cm-12.1
XDA:DevDB Information
M5 Kernel, Kernel for the Sony Xperia Z3 Tablet Compact
Contributors
nos1609, Myself5, [NUT]
Source Code: https://github.com/nos1609/android_kernel_sony_msm8974/tree/cm-12.1
Kernel Special Features:
Version Information
Status: Alpha
Created 2016-01-09
Last Updated 2016-07-01
wow! Big thanks nos1609. I will test this soon! :good:
codfx said:
wow! Big thanks nos1609. I will test this soon! :good:
Click to expand...
Click to collapse
Don't forget the modules, there's a huge risk of bootloops if you forget them.
Meanwhile 24 hours of stable operation
nos1609 said:
Don't forget the modules, there's a huge risk of bootloops if you forget them.
Click to expand...
Click to collapse
I placed them in right place. So far so good with my usage.
Great work! Work flawless on SGP611
How come NFC doesn't work?
Can we have f2fs support please?
Also the latest version had only the TWRP instead of the XZ dual recovery, is this intentional?
hello thanks for your efforts with this kernel everything works but the wifi doesnt work, any suggestions regarding this, am using the 621 Lte version on a CM 12.1 nightly rom
thanks
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
codfx said:
I placed them in right place. So far so good with my usage.
Click to expand...
Click to collapse
hi sorry to ask a noob question but what do you do with the modules? you said you placed them in the right place, where is the right place?
eman2001 said:
hi sorry to ask a noob question but what do you do with the modules? you said you placed them in the right place, where is the right place?
Click to expand...
Click to collapse
extract the modules file and move all files to
Code:
/system/lib/modules
then set permission of all the files you moved to 644
V11.1 is coming
Hey folks
After various reports on different devices, we reverted our sound changes for the static noise with headsets. It seemed to cause more issues than it was fixing.
Z3TC specific note: Builds will be hosted on my server (dl.myself5.de) as nos asked me to do. I'll only build the kernel on my build system, nos is responsible for the kernel to work.
Therefore, our changelog for 11.1 is quite small.
Changelog:
Fix sound again by reverting the previous sound fixes
As always, the build progress can be seen here: http://myself5.de:12345/job/M5Kernel All Devices/
Is it possible to include the philz dual recovery instead of the FOTA one since that one has always caused time issues for me. Whenever I boot up the FOTA recovery the time on my tablet resets to 1970
can some1 provide further information on OC/UC and OV/UV, is there a app for it? can the gpu be OCed aswell?
can it be undervolted?
what about the other features? is tehre a big difference betzween the z3 compact PHONE kernel and the TAB? because the phone has some decent kernels
Chapsaai said:
can some1 provide further information on OC/UC and OV/UV, is there a app for it? can the gpu be OCed aswell?
can it be undervolted?
what about the other features? is tehre a big difference betzween the z3 compact PHONE kernel and the TAB? because the phone has some decent kernels
Click to expand...
Click to collapse
The phone does only have 2 CM custom kernels. Mine and the one from @someone755, my favorite kanging friend [emoji14] (Nah, jk, we're working together on things).
However. You can't flash the phones kernel on the tab, there WILL be issues.
Overclock and Undervolt can be done via Kernel Adiutor (which I recommend BTW). GPU can be overclocked (to 605MHz IIRC), however it can't be undervolted, there never was a port for MSM Kernels to undervolt GPU. Hope that answers your questions.
Sent from my E6653 using Tapatalk
thx 4 the reply, that made things clear,
is it possible that the 2 kernels you mentioned are also the only ones with OC features?
(sry 4 noob questions i just bough my z3t and i guess i am a little l8)
Chapsaai said:
thx 4 the reply, that made things clear,
is it possible that the 2 kernels you mentioned are also the only ones with OC features?
(sry 4 noob questions i just bough my z3t and i guess i am a little l8)
Click to expand...
Click to collapse
They are the only Overclockable kernels for usage with CM12.1/CM12.1 based Roms. There are afaik some other kernels for stock based ROMs, like AndroPlus Kernel, which support OCing too. Thats however not important, as you can't flash the Z3C kernels on the Z3TC.
Sent from my E6653 using Tapatalk
Myself5 said:
They are the only Overclockable kernels for usage with CM12.1/CM12.1 based Roms. There are afaik some other kernels for stock based ROMs, like AndroPlus Kernel, which support OCing too. Thats however not important, as you can't flash the Z3C kernels on the Z3TC.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
which makes your kernels the only kernels with oc so its like android m or oc kernel
Chapsaai said:
which makes your kernels the only kernels with oc so its like android m or oc kernel
Click to expand...
Click to collapse
Pretty much, yeah.
You just need someone to muster up the courage, strength, and, most importantly, the nerves of steel to deal with stock kernel sources. And Myself5 has no intention of doing that any time soon, and I've tried with the .264 kernel (that's stock Lollipop) but didn't get very far. (It works pretty well compared to what Androplus' last release was, if I'm honest. Just no MultiROM.)
For some reason these sources are really a pain to get working, which isn't helped in the slightest by the fact that Sony keeps spitting out new phones faster than Alin can update the kernel-copyleft branch. Meaning we don't even get the convenience of pulling our sources from GitHub -- No no no, we have to download a tarball for each individual kernel update. With no logs of what has changed since the last update, not knowing how it might affect performance or the patches we've already applied and made sure work well.
I'll try not to go near stock until the last stock Marshmallow kernel update is out. Then, I'll take the tarball and compile, so I don't have to mess around with figuring out which part of the code got changed. The issue with this approach, however, is the fact that when it does happen, Nougat will already be running on these devices (maybe? -- though if at all, it'll probably be in April, just like with Marshmallow this year, and Lollipop the year before).
Hope you can make heads or tails out of this.
EDIT: How the hell did I get to the Tablet Compact section? @Myself5 pls I can't keep track of all your threads. And to be honest I can barely keep track of my own, single thread. xD
Hi, please can you assist me? what roms are currently available that i can use with this kernel, also i dont get the adding the modules bit in the instructions, im new to kernels.
Thanks
xxiphxx said:
Hi, please can you assist me? what roms are currently available that i can use with this kernel, also i dont get the adding the modules bit in the instructions, im new to kernels.
Thanks
Click to expand...
Click to collapse
I guess this kernel only works in 5.1.1 custom Roms
could this kernel work with a lineageos version? I mean the 14.1 Version? i want the android 7 features AND overcloking :/
Hi!
I was looking through @laufersteppenwolf's kernel source and noticed it was compiled with -Os flag and an old toolchain. I decided to recompile it with graphite and -Ofast flags (the highest optimization level) and with a newer toolchain. Though the later failed (All builds with 4.9+ toolchains failed to boot on this device ) it still feels faster than the original build. I have also disabled some debugging options so that the kernel would fit in the boot partition in addition to some performance gain.
Features
Compiled with graphite and -Ofast flags (linaro 4.7.4)
Undervolted Wi-Fi, Vibration, LCD and Touch by 10% (Not sure if they're effective or not)
Disabled some debugging options
Added a lower charging current level (1700mA) to fast charge options (To reduce heating during charge but must be selected by user, Default is 1800)
Download
laufersteppenwolf said:
Hey guys
As you already might have read in either the CM11 dev thread or the Q&A section, I am working on a custom kernel for our T210(R) and T211. It's still in a pretty early stage, but the current build is fully stable, so I thought why not share it
As I'm pretty new to this community, a few words about myself: My (only) device I have been working on is the LG Optimus 4x HD, for which I also made a custom kernel (also named werewolf kernel, who would have thought of that ). Me and 2 other fellow RDs were able to "switch" many blobs with the ones from grouper, which fixed many, many issues we were facing in 4.4 with the stock 4.1 blobs. I am the official maintainer of namelessROM and vanir for the 4x HD, and am also compiling GummyROM, LegoROM, unofficial CM 11 (using grouper blobs) and SlimKat for the 4x HD on a nightly base. And as soon as we have a proper device tree for our tab, I'm sure I can port the Tab3 to all those ROMs
Now, enough chit chatting, let's talk about the kernel
It's based on @ketut.kumajaya's blackhawk kernel (thanks again, mate ) From v004 on we are based on official KitKat sources, with some additions such as:
Features:
Various network tweaks
Entropy tweaks
I/O speed improvements
cortex a9 and neon omtimizations
Added frandom
Tweaked vm dirty ratios
Dynamic read-ahead values
Added I/O schedulers: ROW, SIO, BFQ, FIOPS, V(R)
Optimized AES and SHA1 routines
Added CPU governors: Lionheart, Adaptive, Intellidemand, Hotplug, Hyper
Reduced RAM usage from logger
Updated lowmemkiller
Overclocked to 1.420 GHz by default
Disabled vsync for better 2D performance
Overclocked GPU up to 624MHz (default 416MHz)
Custom user voltage control (CPU)
Undervolted by default (-25mV)
S2W and DT2W (WIP)
Fast Charging
KSM
Bugs:
You tell me!
Installation:
Download the kernel from HERE
Reboot into recovery (recommended to make a nandroid)
Flash the kernel zip
Recommended to wipe /cache
Reboot and enjoy!
And remember to remove phservice if you want to change some CPU/GPU settings yourself
Notes:
See 2nd post
GPL:
Kernel sources
Kernel Modules (only for v001 - v003)
Used defconfig
Used build script
Thanks:
@ketut.kumajaya for the initial kernel base
@gr8nole for general help, info and testing
XDA:DevDB Information
Werewolf kernel SM-T210/T211, Kernel for the Samsung Galaxy Tab 3
Contributors
laufersteppenwolf
Kernel Special Features: Tuned for best possible performance
Version Information
Status: Stable
Created 2014-07-21
Last Updated 2015-05-25
Click to expand...
Click to collapse
XDA:DevDB Information
Recompiled Werewolf SM-T211, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
mat1371
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2018-08-23
Last Updated 2018-08-23
Reserved
Tweaking Guide
laufersteppenwolf said:
Since v002, we have an updated lowmemorykiller. It behaves a bit snappier than the old one, also with the default minfree values. However, in case you like to tweak your device a bit to make it even more snappy (like me ), I tweaked the minfree values a bit to slightly increase the free RAM without really affecting the multitasking experience. The script can be found in the attachment. All you need to do is to extract the script and place it in your /system/etc/init.d/ folder and that's it. The values will be automatically set on boot.
UV interface
The min possible voltage is 1000mV for now, and the max one is 1400mV. If you want me to lower the min voltage, please let me know.
Also, please note, that the voltage has to be changed in 12.5mV steps. If you apply for example 1110mV, it will be rounded down to 1100mV.
Fast Charge interface
The main interface is inside /sys/kernel/fast_charge/*
/sys/kernel/fast_charge/force_fast_charge (rw)
0 - disabled (default)
1 - use custom mA configured through the sysfs interface (see below)
/sys/kernel/fast_charge/ac_charge_level (rw)
rate at which to charge when on AC (1.8A to 2.3A)
/sys/kernel/fast_charge/usb_charge_level (rw)
rate at which to charge when on USB (0.5A to 1.0A)
/sys/kernel/fast_charge/failsafe (rw)
0 - disabled - allow anything up to 2.3A to be used as AC / USB custom current (USE WITH CAUTION!)
1 - enabled - behaviour as described above (default)
/sys/kernel/fast_charge/version (ro)
display fast charge version information
New kmsg layout
From v008 onwards the kmsg looks a tiny bit different. Instead of displaying the time since boot, it logs the actual time and date.
Now, you may ask yourself: "does that any good?" Sure it does. When you encounter an issue and grab a log, you can send it my way saying "the issue happened at 15:35". It is way harder to find out the exact time (in seconds) since the device booted, right?
Click to expand...
Click to collapse
mat1371 said:
Hi!
I was looking through @laufersteppenwolf's kernel source and noticed it was compiled with -Os flag and an old toolchain. I decided to recompile it with graphite and -Ofast flags (the highest optimization level) and with a newer toolchain. Though the later failed (All builds with 4.9+ toolchains failed to boot on this device ) it still feels faster than the original build. I have also disabled some debugging options so that the kernel would fit in the boot partition in addition to some performance gain.
Features
Compiled with graphite and -Ofast flags (linaro 4.7.4)
Undervolted Wi-Fi, Vibration, LCD and Touch by 10% (Not sure if they're effective or not)
Disabled some debugging options
Added a lower charging current level (1700mA) to fast charge options (To reduce heating during charge but must be selected by user, Default is 1800)
Download
XDA:DevDB Information
Recompiled Werewolf SM-T211, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
mat1371
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2018-08-23
Last Updated 2018-08-23
Click to expand...
Click to collapse
Great! Did you upload your source?
I had been working on it to compile with GCC 8, but haven't got enough time to complete the cherry picks
sscsps said:
Great! Did you upload your source?
I had been working on it to compile with GCC 8, but haven't got enough time to complete the cherry picks
Click to expand...
Click to collapse
It's on github but I didn't link to it cause it's messy. BTW There is no source code change aside from makefile and defconfig.
BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?
sscsps said:
BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?
Click to expand...
Click to collapse
Use https:// in download link.
adukale said:
Use https:// in download link.
Click to expand...
Click to collapse
Well, I've got it already, and https didn't quite help, her to use a VPN,
I'm suggesting the OP to upload somewhere else as well.
Thx alot, now it's time to download kitkat rom.
Keep it up sir ?
sscsps said:
BTW, that link is blocked in India, can you upload it somewhere else? and also, cna you provide link to your source?
Click to expand...
Click to collapse
Sorry for late reply, I'm busy with my thesis these days. I've attached the file to the post. Will send you a link to the source (GitHub) in your PV.
Great! Finally something new for T211/0. Love to see some movement here.
Tried installing on a T210 with TRWP but get an error message. Anyone any ideas?
Tried to attach the error but it won't let me... Error talks about asset failed getprop ro.product.device == lt023g etc
@Samw13
SM-T210 = lt02 wifi Tab
SM- T211 = lt02_3g Tab
So, i have deleted requirement in update-script file and kernel seems to work correctly on t210.
Here's link to edited kernel: https://www.upload.ee/files/10238882/kernel-SM-T210-werewolf-Ofast-UV.zip.html
{
"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"
}
Is it fully stable on SM-T211??. Is it the final version??
Hi,
@mat1371,
@lol28
Thank you for the kernel for T210R. Stable, overclocked to 1.42Ghz. I have an issue with the settings I make, they don't stick after reboot. I used kernel adiutor, EX kernel manager, Performance tweaker. I have busybox installed.
I've flashed Powerdaemon.disable.zip from Gr8nole, still the same.
Edit:
I've found Gr8nole's suggestion about deleting /system/bin/phservice. I deleted the file, rebooted, changed to governor to lionheart. It seemed to keep the settings.
Thanks!
Melina Reborn
Melina returns for AOSP Support
If you loved Melina Kernel, you will be happy to hear that Melina Reborn has been developed with new V30A sources (as of rel_r5, Melina is now using more stable sources), with all of the features and performance you loved from Melina Kernel, but now with AOSP support! I did have to disable F2FS, if it is requested, I will try to re-implement it, but AFAIK it was never used on our devices anyway. Aside from F2FS everything else is available. Or should be
Tested on HavocOS-v3.2 on a US997 with BL 21E. (Note: My SD Card slot is broken. I cannot test any SDCard related issues. No issues are foreseen, but if any SDCard related issues happen to arise, please report them in as much detail as possible (dmesg, logcat, etc), as I cannot test SDCard functionality myself.)
Note: There have been reports of missing functionality under Pixel Experience Pie. This may occur on all Pie ROMs, but this is yet unknown. Pie was not tested, so consider this an Android 10 Only kernel for now.
"bootloop" note: Your G6 may reboot itself once after flashing my kernel, before reaching the OS boot animation. Do not panic, this is normal. I believe it is part of the Magisk recovery. If the bootloop occurs more than 1 time, even if it makes it to the OS, please report it here.
Primary Features:
Can now charge while powered off (offline charging) (rel_r5)
clang compiled and optimized kernel with extended armv8-a attributes (rel_r5) (for real this time!)
WiFi Hotspot working with properly configured ROM (rel_r5) (including 5ghz)
USB disconnect issues should be fixed (rel_r5)
Charging issues should be fixed (rel_r5)
Enabled FM Radio (requires supported ROM which currently there is none because it is still in testing, but looking promising)
Switched to more stable kernel sources (rel_r5) (see github readme)
Optimized and DEBUG editions (rel_r4)
Even more debug routines reduced (rel_r4)
Updated CPU optimizations one more time (tune for Kyro) (rel_r4) (this actually failed silently that is why rel_r4 was terrible)
More adjustments to reduce (and hopefully remove) the chance of random reboots (rel_r4)
Updated to AnyKernel 3, allows retaining Magisk when flashing kernel (rel_r3)
Module-less Kernel (rel_r3)
Removed old exFAT driver in favor of new sdfat driver (rel_r3)
Significantly reduce debugging messages/routines for performance enhancements (rel_r2)
Cleaner Kernel code, fixed all compiler warnings (with ubertc 6.x) (rel_r2)
Optimize compiler flags with big.LITTLE optimizations (rel_r2)
Updated AnyKernel Installer to place modules where they should be (rel_r2)
Fixed crashes due to missing 32-bit support (rel_r1.1)
Added maple iosched, enabled tcp westwood congestion sched
New kernel defaults: iosched (now: maple, was: cfq), tcp (now: westwood, was: bic) (Note: These default values may be overridden by the ROM. Be sure to use something like kernel adiutor to verify and set the values as desired.)
Binary releases built with ubertc aarch64-linux-android-6.x
DriveDroid CD-ROM Emulation Support
zzmove and elementalx governors
Various other improvements
Removes /sbin/rctd and related service entry in init.lge.rc if detected (for Stock ROMs, untested)
Remove forceencrypt (for Stock ROMs, untested)
Open source compatible replacement for Tuxera exFAT driver (removed in rel_r3, superseded by sdfat)
The following features from the original Melina Kernel are no longer available due to issues:
Flash Friendly FS (F2FS) Support
Downloads
Note: The difference between optimized and DEBUG is that the optimized version of Melina Kernel has extra debugging removed, which may increase battery life and performance slightly, but at the cost of making it harder to fix problems. The DEBUG kernel is more like most other kernels that are based on LGE official code, where LGE left on a lot of debug routines that aren't needed once the ROM is functional. However, those wanting to help fix issues, or ROM developers working on their ROM may want this extra information. This is why Melina Reborn now offers both kernels as an option.
rel_r5
US997: Optimized - DEBUG
H870 Optimized - DEBUG
H872 Optimized - DEBUG
rel_r4
US997: Optimized - DEBUG
H870 Optimized - DEBUG
H872 Optimized - DEBUG
rel_r3
US997
H870
H872
rel_r2
US997
H870
H872
rel_r1.1
US997
H870
H872
Known Issues
Some users have been reporting "random" reboots with rel_r1.1 and rel_r2. It seems linked to spi8 (fingerprint) and spi12 (touchscreen). An attempt to address this was added to rel_r3.
Attribution
For a full list of credits, please see the Github sources below, and browse the commit log. I try to keep commits as authentic as possible (except my own which I rebase and amend alot lol).
@TheWolfSVK for his work on the V30A sources, as well as for his incredible Havoc ROM
@osm0sis for AnyKernel3
Everyone who used and helped test the original Melina Kernel
When reporting any issues please be as detailed as possible. At a minimum, include your model and bootloader version. Any logs would be appreciated but I know sometimes it's not possible to get them (check for /sys/fs/pstore/console-ramoops). Also try to explain with as much detail as possible what you were doing when the problem happened (What app was active (running and on screen)? Which apps were in the background? Are you rooted? etc)
Github Sources
ROM Developers: You may include this kernel in your ROM so long as you link back to this thread in your release thread. If you modify any of the kernel or config, please also change the name from melinareborn to melinamodified in arch/arm64/configs/melina_common_android_intree_subconfig. This kernel can now be used in-tree while building Android, without clang, although ubertc may be required, untested (I built with ubertc in the tree, see here how to add Melina to a lineage-based G6 device tree.)
clang in-tree building now works and the bluetooth issue was found and addressed (don't ask, it was silly)
{
"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"
}
Guess who's back! Guess who's back! Haha welcome back! I know you thought about the song! Anyways to the point. Does this support stock as well? Since it uses 30A sources does that mean it can't be used on stock 8.0? It's essentially a pie kennel right? I loved custom ROMs but on TMobile using a phone as phone is hard without volte, vowifi. Still would love you to updateTWRP. It would also be nice if be you did it for v20 too. Since it's been basically the same phone. Although everyone with g5 would get jealous then. Haha! :silly::good::highfive:
Vortell said:
Guess who's back! Guess who's back! Haha welcome back! I know you thought about the song! Anyways to the point. Does this support stock as well? Since it uses 30A sources does that mean it can't be used on stock 8.0? It's essentially a pie kennel right? I loved custom ROMs but on TMobile using a phone as phone is hard without volte, vowifi.:
Click to expand...
Click to collapse
Stock is untested, I could not stand 21E long enough. Though Melina rel_o2 worked well for the 10 minutes I tried to deal with Stock
Have you tried Havoks? I don't have those services to test. If you can snag some logcats on Havoks' Android 10 of you trying to use the services, I will look at it but no promises)
Vortell said:
Still would love you to updateTWRP.
Click to expand...
Click to collapse
TWRP is in planning, since my SD is broken I can't test backups until my USB OTG arrive, should be tomorrow, but I have plans this weekend, and still have to try to fix the issue, so unknown ETA for TWRP.
Vortell said:
It would also be nice if be you did it for v20 too. Since it's been basically the same phone. Although everyone with g5 would get jealous then. Haha! :silly::good::highfive:
Click to expand...
Click to collapse
Depends on how technically it is the same phone. If it has the same hardware, perhaps a device config could be made.
zefie said:
Depends on how technically it is the same phone. If it has the same hardware, perhaps a device config could be made.
Click to expand...
Click to collapse
Both are msm8996 hardware and there is souces for the rest in older trwp page I think. It was just a wish I didn't think you would actually do it.
Vortell said:
Both are msm8996 hardware and there is souces for the rest in older trwp page I think. It was just a wish I didn't think you would actually do it.
Click to expand...
Click to collapse
I mean, if EVERYTHING was the same (except a few unique traits, kinda like the differences between H870, H872 and US997) then it wouldn't really be a problem. But if it even has a different camera, it becomes complicated.
zefie said:
I mean, if EVERYTHING was the same (except a few unique traits, kinda like the differences between H870, H872 and US997) then it wouldn't really be a problem. But if it even has a different camera, it becomes complicated.
Click to expand...
Click to collapse
I see I though blobs were easy, but I have yet to build for Android. If you want to take a look. After this post I promise no more off topic posts.
Here's a link to a kernel kind of like yours for v20:
https://forum.xda-developers.com/v20/development/kernel-gamma-kernel-t394011
Here's modified for stock kernel:
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Here's Los 17.1 for it from x86cpu who is same person who builds los for LG G6:
https://forum.xda-developers.com/v20/development/rom-unofficial-lineageos-17-0-lg-v20-t4010893
Here's TWRP for it:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
One last thing do you want me to test this on stock 8.0 LG G6 us997? I swear if havoc had volte I would never use anything else. My favorite ROMs are havoc , aicp and crdroid. I had Samsung S5 and it had dozens of ROMs to try. My note 4 had probably a dozen. LG v20 has probably 10, but only 3 current ones.
Vortell said:
I see I though blobs were easy, but I have yet to build for Android. If you want to take a look. After this post I promise no more off topic posts.
Here's a link to a kernel kind of like yours for v20:
https://forum.xda-developers.com/v20/development/kernel-gamma-kernel-t394011
Here's modified for stock kernel:
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Here's Los 17.1 for it from x86cpu who is same person who builds los for LG G6:
https://forum.xda-developers.com/v20/development/rom-unofficial-lineageos-17-0-lg-v20-t4010893
Here's TWRP for it:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
One last thing do you want me to test this on stock 8.0 LG G6 us997? I swear if havoc had volte I would never use anything else. My favorite ROMs are havoc , aicp and crdroid. I had Samsung S5 and it had dozens of ROMs to try. My note 4 had probably a dozen. LG v20 has probably 10, but only 3 current ones.
Click to expand...
Click to collapse
I'll look into the other device when I get a chance, but I'll be honest its pretty low priority. You can try the kernel on stock. I did score 3 months of Mint Mobile free during their (special american footbal game that has a huge trademark liability on its name) special and apparently they support VoLTE. No promises but I will try to look into it, as I am also working with the developer of Havoc.
Also be on the lookout for rel_r2, r1/r1.1 was kinda rushed, but I am working to further optimize r2, beyond even what the original Melina Kernel had.
zefie said:
I'll look into the other device when I get a chance, but I'll be honest its pretty low priority.
Click to expand...
Click to collapse
Either way always love a extra developer on any phone i own. If you are saying you hope to get volte working on custom ROMs for the g6 that's more impressive and should be a higher priority. I'm almost giddy just thinking about being able to use custom ROM with volte. It would open it up for at least g5 and v20. Assuming you open source it.
Also u will give it a try on stock and let you know.
Hey guys,
On stock pie V30B bluetooth isn't working on my h870 with all modified kernels I tried. Any suggestions? Thank you.
I'm glad that you're back zefie ?
Hi there . it doesn't work for me with the V30B Stock rum either. is there a modified kernel for stock pie?
Rothrex93 said:
Hi there . it doesn't work for me with the V30B Stock rum either. is there a modified kernel for stock pie?
Click to expand...
Click to collapse
It isn't for STOCK Rom this kernel is for AOSP ROMS. Stock kernel has a lot proprietary stuff.
SkylineDiT said:
It isn't for STOCK Rom this kernel is for AOSP ROMS. Stock kernel has a lot proprietary stuff.
Click to expand...
Click to collapse
Sorry you misunderstood. my Stock V30B rom to want a modified kernel. Has anyone done this already?
Rothrex93 said:
Sorry you misunderstood. my Stock V30B rom to want a modified kernel. Has anyone done this already?
Click to expand...
Click to collapse
Sorry, this is for AOSP and there is no plans for a Melina for stock Pie. You can thank LGE for abandoning the US997 Unlocked variant for the fact that I cannot make a Pie Stock kernel
Testing Melina Reborn kernel rel2 on H870 bootloader 20J ROM: PixelExpierence 2019-08-23-2221 (PIE). BT works fine battery is good performace great. Not working: camera, flashlight, NFC, and fastcharging. Will try to test rel3
I am using rl3 with havocOS 3.2 without issues.
I noticed that my device isn't heating as much as it used to.
Battery life is better.
H870.
I agree the melina kernel installation in TWRP preserved all magisk, viper settings in Havoc 3.2 07.02. All works from NFC to kernel adiutor settings e.g. cpu governor zzmove (very quick and more energy safe than performance) - no more powersave which mantained my phone very cool even during games, but was very slow in starting apps. Now my phone is slightly warm all the time, but very quick and responsive. Thank you very much zefie!
Hello, Sir can i install it on H870 with Havoc 2.9 ( Pie) with magisk installed ?
kurogami555 said:
Hello, Sir can i install it on H870 with Havoc 2.9 ( Pie) with magisk installed ?
Click to expand...
Click to collapse
There have been reports of it not working with PE Pie, not sure about Havoc Pie. The kernel may only work on Android 10, not sure yet.. If you do try it, be sure it have a backup of your current kernel.
Vortell said:
Either way always love a extra developer on any phone i own. If you are saying you hope to get volte working on custom ROMs for the g6 that's more impressive and should be a higher priority. I'm almost giddy just thinking about being able to use custom ROM with volte. It would open it up for at least g5 and v20. Assuming you open source it.
Also u will give it a try on stock and let you know.
Click to expand...
Click to collapse
Three things
1) What is the device model code (us996?) for a kernel for you to test
2) it won't work on stock and probably only Android 10 ROMs, if at all lol
3) still no eta