Current version (10/16):
ROM: Stock JZO54K (with Superuser.apk, su and busybox, H icon (hsdpa) added)
Kernel: Stock 3.0.31 (with bln, voodoosound, bigmem, crtoff, ondemand governor with powerhal added)
Download: JZO54K-H-3.0.31-4-bln-voodoosound-bigmem-crtoff-powerhal-gbc75230.zip
MD5: 5748f7c5d057a22bababed926fcb6dfb
Previous version (10/12):
ROM: Stock JZO54K (with Superuser.apk, su and busybox, H icon (hsdpa) added)
Kernel: Stock 3.0.31 (with bln, voodoosound, bigmem, crtoff, ondemand governor with powerhal added, overclocked (1200 MHz))
Download: JZO54K-H-3.0.31-3-bln-voodoosound-bigmem-crtoff-powerhal-ge526cb0.zip
MD5: 76eb87e602b776a890fce451252a99b3
Previous version (09/25):
ROM: Stock JRO03L (with Superuser.apk, su and busybox, H icon (hsdpa) added)
Kernel: Stock 3.0.31 (with bln, voodoosound, bigmem, crtoff, ondemand governor with powerhal added)
Download: JRO03L-H-3.0.31-2-bln-voodoosound-bigmem-crtoff-powerhal-g43514b5.zip
MD5: adc984fc1c5a9b1a351fdb2492660e17
Previous version (08/26):
ROM: Stock JRO03L (with Superuser.apk, su and busybox added)
Kernel: Stock 3.0.31 (with bln, voodoosound, bigmem, crtoff, interactive governor with input boost added)
Download: JRO03L-3.0.31-1-bln-voodoosound-bigmem-crtoff-gb419404.zip
MD5: fde683f315e73821e9eb09bc65e51377
Resources:
See post #7
nice work will try .
So all the trolling in the AOSP thread was because of this? LOL.
By the way, be GPL compliant and post the source for your kernel (or give the links for the patches & config or mention where they come from - basically we need to have enough information to build a similar zImage).
DELETED: I stand corrected.
apatal said:
WTF is this?! Another clean AOSP ROM? How is it different from knzo's ROM? And couldn't you even think of a different title? If you're doing this just to spite him, this isn't the right way to do it. State clearly in your OP why this ROM deserves another thread or I will report it to the mods. Enough garbage in the NS forum already.
Click to expand...
Click to collapse
this is from JRO03L OTA ...is not AOSP... that i understand from title ...
Knzo rom Is from AOSP
leap_ahead said:
this is from JRO03L OTA ...is not AOSP... that i understand from title ...
Knzo rom Is from AOSP
Click to expand...
Click to collapse
Hmmm... I still don't buy it, but ok, I'll delete my comment now. Thanks.
I still suggest he thinks of a different title for the thread, without the percentage, just to avoid confusion.
knzo said:
So all the trolling in the AOSP thread was because of this? LOL.
By the way, be GPL compliant and post the source for your kernel (or give the links for the patches & config or mention where they come from - basically we need to have enough information to build a similar zImage).
Click to expand...
Click to collapse
All information was already given in the OP to reproduce this ROM. But here you go:
Android 4.0.4 (IMM76D) Factory Image - https://dl.google.com/dl/android/aosp/soju-imm76d-factory-ca4ae9ee.tgz
Android 4.1.1 (JRO03L) OTA Update - http://android.clients.google.com/packages/ota/google_crespo/gR7DDnLp.zip
Superuser.apk, su - http://androidsu.com/superuser/
Busybox - https://play.google.com/store/apps/details?id=stericson.busybox
Linux Kernel 3.0.31 - https://android.googlesource.com/kernel/samsung.git
Patches for BLN, Voodoo Sound, Bigmem, CRT-Off etc. - e.g.: https://github.com/thalamus/android-kernel
Dumped with romdump: http://android.podtwo.com/romdump/
New boot.img produced with scripts from: https://github.com/koush/AnyKernel
FloHimself said:
Don't hesitate, go ahead.
Click to expand...
Click to collapse
Is this the OTA that was released in Australia that I've read about in some threads? I've only encountered the JRO03E OTA so far...well, until now, that is.
apatal said:
Is this the OTA that was released in Australia that I've read about in some threads? I've only encountered the JRO03E OTA so far...well, until now, that is.
Click to expand...
Click to collapse
Yes, correct.
FloHimself said:
Yes, correct.
Click to expand...
Click to collapse
Aaaahhh. OK. Now it's clear. I should have read more carefully. My apologies. Glad to see people are coming out with clean alternatives like this. Too many kangs and cherry-pickers floating around.
EDIT: Ooohh nice. It's deodexed. My daily driver is another stock deodexed ROM, a JRO03E OTA. Might give this a whirl when I have the time. Thanks.
apatal said:
EDIT: Ooohh nice. It's deodexed. My daily driver is another stock deodexed ROM, a JRO03E OTA. Might give this a whirl when I have the time. Thanks.
Click to expand...
Click to collapse
No, it's still odexed, i.e. all .odex files are present as preferred by google.
FloHimself said:
No, it's still odexed, i.e. all .odex files are present as preferred by google.
Click to expand...
Click to collapse
Got it. 99.99% it is.
if coming from knzo ROM, do I have to wipe anything before installing your ROM?
plz give us deodexed version too
edit : the latest ota stock repack with deodex, root and busybox is always essential for the forum
Very nice rom, new daily
Sent from my Nexus S using xda premium
Can this ROM be used with other kernels? Its seem faster than the E ota.
Sent from my Nexus S using Tapatalk 2
Is there really a need to install custom kernel? It runs superb on stock
Sent from my Nexus S using xda premium
Well i am a fan morfics kernel with the colors he uses makes the display way better than stock
Sent from my Nexus S using Tapatalk 2
TG2708 said:
Well i am a fan morfics kernel with the colors he uses makes the display way better than stock
Click to expand...
Click to collapse
Yes I'm using a custom kernel with it and it runs great. Always make a nandroid backup first if you're not confident about flashing anything...and flash at your own risk.
Sent from my NexuS
luv stock..1 request. can somebody add restart menu? then its done for me
Related
Hello everyone,
I'm are proud to bring you the latest rooted kernels based on samsung stock kernels that you may find in ROMs by Samsung.
Why should i use this kernel?
My kernels are uber-minimal modification of stock kernel used only for rooting (no custom recovery is installed). So the kernel it's like stock just rooted, and there is small chance (or any chance) that it will be detected as modified by service center at the first look
Please find latest of kernels listed below:
*NEW* ROOTED! I9300XXELLB - Jelly Bean (4.1.2) - CL: 748978 - B.Date: 26.12.2012 - Download HERE!
[[size=-2]uname: Linux version 3.0.31-748978 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Wed Dec 26 15:40:05 KST 2012[/size]]
Instructions:
1. Flash tar file of choosen kernel using Odin
2. Profit!
What's included in this kernel
- Base image of kernel is 100% pure stock by samsung
- adbd in insecure mode (so adb shell will be automatically connected with root priviliges)
Nothing more, nothing less - Enjoy!
If you like my modifications, support me with even a little donation for a beer -> Click to donate!
WARNING: Flashing this kernel will pop-up your custom binary counter! (as when rooting )
Enjoy!
wanna ask, this kernel have sds fix or not?
SDS fix is not in kernel but bootloader and yes, this version (if you will flash full rom) have new bootloader with fixes.
Adam
http://forum.xda-developers.com/showthread.php?t=2091045
from above link, i think the fixes is from kernel.. iinm, the ella firmware has the fix.. not sure from bootloader or kernel..
that's why i ask about this, to know whether ellb = ella in terms of sds fix..
AdamLange said:
SDS fix is not in kernel but bootloader and yes, this version (if you will flash full rom) have new bootloader with fixes.
Adam
Click to expand...
Click to collapse
No it's not.
Also LLB is not latest kernel.
Also this is in the wrong forum.
AndreiLux said:
No it's not.
Also LLB is not latest kernel.
Also this is in the wrong forum.
Click to expand...
Click to collapse
Why then?
Not A not C... LLB??? Strange, bardzo.
AndreiLux said:
No it's not.
Also LLB is not latest kernel.
Also this is in the wrong forum.
Click to expand...
Click to collapse
1. post some more info instead of trolling.
2. its latest in this thread not overall, i never told that this is latest from Samsung
3. REally? its I9300, its ORIGINAL (kernel is not compiled its just stock modded, so its original.)
Something else?
Adam
sebarkh said:
Why then?
Not A not C... LLB??? Strange, bardzo.
Click to expand...
Click to collapse
i will add more soon (pozniej ;>)
Adam
Personally I always thought original means ORIGINALly YOURs (you are the author, not copied), not original Samsung....
But. .. maybe mistaken. ..
Variety makes this forum better anyway. ..
Kernel base is 100% oryginal, its not recompiled or compiled from sources, so in that meaning its 100% STOCK KERNEL.
Insecure kernels have modded adbd and other settings needed to run is as root in INITRAMFS of kernel.
This make it ROOTED STOCK KERNEL 100%
AdamLange said:
SDS fix is not in kernel but bootloader and yes, this version (if you will flash full rom) have new bootloader with fixes.
Adam
Click to expand...
Click to collapse
After reading page after page on this form every one is saying the sd fix is in the kernel. How come your saying it's in the bootloader? Also what do you mean (if you flash full rom) What rom? Its a kernel in your op.
Sent from my GT-I9300 using xda premium
Noone confirmed it isnt. I can't also confirm it is or not. This is not thread about it. Move along
Adam
AdamLange said:
Noone confirmed it isnt. I can't also confirm it is or not. This is not thread about it. Move along
Adam
Click to expand...
Click to collapse
You boldly said that the bootloader had the fix. Now you don't know if it has or not. And your a developer of an original kernel. Move along
Sent from my GT-I9300 using xda premium
AdamLange said:
1. post some more info instead of trolling.
Click to expand...
Click to collapse
There's two massive threads in the general section with enough information, I'm not here to educate you myself, I just pointed it out. We don't need developers coming in and doing false statements as there's enough misinformation on the topic, you already confused some users here.
AdamLange said:
2. its latest in this thread not overall, i never told that this is latest from Samsung
Click to expand...
Click to collapse
Uhm..
I'm are proud to bring you the latest rooted kernels based on samsung stock kernels that you may find in ROMs by Samsung.
Click to expand...
Click to collapse
Actually that is exactly what you've told... Rephrase your English otherwhise.
AdamLange said:
3. REally? its I9300, its ORIGINAL (kernel is not compiled its just stock modded, so its original.)
Click to expand...
Click to collapse
You're mixing up the meaning of original, this section if for original works in the meaning they are made by users (Compiled kernel/ROM/program), not original in the sense as the manufacturer delivers them. It's written in the sticky in the development forum or in the portal post. Repacking kernels isn't original development. Read.
AdamLange said:
Noone confirmed it isnt. I can't also confirm it is or not. This is not thread about it. Move along
Click to expand...
Click to collapse
Actually yes it is confirmed it's in the kernel because we have the kernel code and patch regarding the issue.
Something else?
Sorry for misleading, i didnt noticed the topic with patch, i cant track everyhing.
this thread is about insecure kernel mod not a patch for death of SGS, so please no more offtopic here.
Insecure kernels are stock base (zImage is not modified) kernel with modded initramfs, where STOCK means no "tweaks" in kernel code was made. All insecure kernels works like this so i dont see a point of bashing me for saying its STOCK cause base of kernel is.
I asked mod to clean the thread.
A
And I've said it's not an original work as how you wrote in big capital letters claiming it is. Why are you replying to me about what a (insecure) stock kernel is?
AdamLange said:
I asked mod to clean the thread.
Click to expand...
Click to collapse
Why? It's a development discussion. You can't just go ask a moderator to delete things every time because somebody else is correcting you. That's bothering and abusing moderators.
it is original work. its modded initram by me , base is stock. if you dont like it, dont use it. if you dont like my reference to stock, then dont like it, i dont care.
I asked to clean the thread because you are not discussing, just attacking my work.
I have moved the thread to the Development Forum.
Can the arguments stop now please?
Keep it on topic or leave the thread alone.
Mark.
m_plus kernel for Nexus 4 (mako)!
Hi All,
In an attempt to reduce the confusion related to the two versions of 4.3, I have decided to split my m_plus thread into 3 versions, a version for 4.2 (the previous thread: http://forum.xda-developers.com/showthread.php?t=2256887), a version for 4.3 JS AOSP builds (this one) and a version for 4.3 JW builds (not yet up, but will be in the future).
Disclaimer: As usual, I am not responsible for anything that may or may not happen to your device as a result of using this kernel or any other flashable zips posted by me in this thread.
Kernel Features:
Based on the latest Google Source for 4.3
Built with the Linaro 4.7.3 toolchain (2013.07)
insecure ramdisk (ro.recure=0, ro.debuggable=1)
init.d support (by flashing the full ramdisk, requires busybox installed to /system/xbin)
Undervolting support (down to 600mV)
Gamma Control support (motley, faux and franco interfaces available)
Faux Sound Control support including poweramp
dynamic fsync
simple GPU governor
Builds:
Sources: https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_43_exp_JS
Warning: These builds are for 4.3 builds beginning with the letters JS only, if you flash it on a JW based build you will have all sorts of strange graphical issues.
Personal Request: If you plan to make unofficial builds with features not included in the builds posted by me, please don't link them in the thread, all this does is result in confusion especially if someone has a problem with something you have added, it is much easier for me to provide support if I know that everyone in the thread is running the same builds I am. If you want to make a kernel with these features, feel free to start another thread so that they can be discussed and supported as appropriate.
http://goo.im/devs/thracemerin/mako/m_plus_43/JS_builds/alphas
Latest:
Alpha 5:
Flashable (anykernel): m_plus_43_alpha_5JS.zip
Note: if you need the full ramdisk for init.d support/insecure ramdisk, flash the ramdisk package alpha 4 first.
What's Added:
USB force fast charge
Enable Krait Retention
Various patches and enhancements from CAF
Previous:
Alpha 4:
Note: The anykernel version doesn't include init.d support and insecure ramdisk unless your ROM already has it, if you were on alpha 3 you will retain it.
Note 2: If you flash the ramdisk version on CM, the built-in superuser will stop working, CM includes init.d support anyway.
Flashable (ramdisk included): m_plus_43_alpha_4JS_ramdisk.zip
Flashable (anykernel): m_plus_43_alpha_4JS.zip
What's Included:
all the stuff listed in kernel features
freezer patches by Colin Cross
Thanks:
Google
LG
Qualcomm/CodeAurora
CyanogenMod
_motley
faux123
show-p1984
franciscofranco
stratosk
anyone else I failed to mention (if you feel as though you deserved to be thanked by name, please PM me)
Reserved
PowerHAL Fix:
There is an issue in the stock AOSP powerHAL where the mpdecision touch boost requests are being sent to the wrong socket, as a result there will be unexpectedly poor UI performance. Show-p1984 fixed this problem in his Stockified AOSP build and I pulled the powerHAL and made it flashable for everyone. Just flash it in recovery and reboot, if you want to go back to the stock one just dirty flash your ROM. This shouldn't cause any problems on any ROM even if it has the fix already cooked in, but if it does you can just dirty flash your ROM to remove it. Thanks to show-p1984 for the fix.
43_powerhal_fix.zip MD5: c7cebad04b5f71d067df1a45c6e538f7
One More for Science!
Just flashed. I was losing wifi connection with semaphore when phone went into deep sleep. Ill report back. :good:
do you have to be rooted in order for init.d to work?
keda said:
do you have to be rooted in order for init.d to work?
Click to expand...
Click to collapse
Yep, need to have busybox installed too.
First of all, thanks for your work.
I want to make sure I understand the procedure correctly.
If I use CM10.2, I flash "m_plus_43_alpha_4JS.zip" to maintain the built in superuser.
init.d will still work, cause cm already supports it.
Right now I am on Alpha3 with SuperSU 1.51. So to update to alpha4 I can simply flash over.
If I want to go back to the built in superuser I have to reflash CM, then flash alpha4 via zip.
Is this correct?
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
AcmE85 said:
First of all, thanks for your work.
I want to make sure I understand the procedure correctly.
If I use CM10.2, I flash "m_plus_43_alpha_4JS.zip" to maintain the built in superuser.
init.d will still work, cause cm already supports it.
Right now I am on Alpha3 with SuperSU 1.51. So to update to alpha4 I can simply flash over.
If I want to go back to the built in superuser I have to reflash CM, then flash alpha4 via zip.
Is this correct?
Click to expand...
Click to collapse
Dirty flash CM, then flash A4 should do it, that's what I did and it worked.
ScumDroid said:
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
Click to expand...
Click to collapse
Strange, it's working fine for me now.
Thanks, just wanted to reply. Works as you said.
After the first boot I had some strange behaviour,
min cpu clock did not go below 1,026 ghz and GPU Clock did not go above 200 mhz.
A restart fixed it, incase somebody notices similar behaviour.
AcmE85 said:
Thanks, just wanted to reply. Works as you said.
After the first boot I had some strange behaviour,
min cpu clock did not go below 1,026 ghz and GPU Clock did not go above 200 mhz.
A restart fixed it, incase somebody notices similar behaviour.
Click to expand...
Click to collapse
Weird, I didn't notice that.
thracemerin said:
Strange, it's working fine for me now.
Click to expand...
Click to collapse
Mabye its an app i have installed. Kernel is flying btw, nice work.
Is it just me or the option to give location eve with wifi off is ****ing with repeaters... I have two access points in my house and when the option was on the wifi keep disconnecting... Maybe cause In some parts I can have signal from both access points... So weird
Sent from my Nexus 4 using xda app-developers app
ScumDroid said:
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
Click to expand...
Click to collapse
+1 for this. i am also having same problem.
yash295 said:
+1 for this. i am also having same problem.
Click to expand...
Click to collapse
What ROM are you using?
thracemerin said:
What ROM are you using?
Click to expand...
Click to collapse
Cm 10.2 unofficial nightly.
Sent from my Nexus 4 using Tapatalk 4 Beta
yash295 said:
Cm 10.2 unofficial nightly.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
hmm...working perfectly for me, CM10.2 unofficial and this kernel.
thracemerin said:
hmm...working perfectly for me, CM10.2 unofficial and this kernel.
Click to expand...
Click to collapse
Oh yeah cm might be the problem. Sorry for the inconvenience
Sent from my Nexus 4 using Tapatalk 4 Beta
First of all, many thanks to Kasper_h for all your work.
This is a mod of Mackay's Kernel 3.0, designed to work with the offical CM10 stable. I've seen various posts about CM not working, so I put this mod togther to get a fully working CM10 based ROM based on the offical CM10 stable.
The advantages of CM10 over CM10.1
Video recording works
Skype Video Calling works
Barcode Scanning apps work
Burst mode camera apps work
Apps2SD works
Bluetooth File transfer (send/receive) works
GPS works
The disadvantages of CM10 over CM10.1
Code base is obsolete, so no more fixes/updates/features etc
Feels slightly less fluid/responsive than Mackays Rom
Feels slightly less stable than Mackays Rom
This has the standard CM10 ramdisk, modified to include Kasper_h's GPS Fix, along with Mackay's Kernel 3.0 zimage (unmodified).
See Kasper_H's original thread here: http://forum.xda-developers.com/showthread.php?t=2153164
Kasper_h's kernel source here: https://github.com/kasperhettinga/lge-kernel-sniper
Get the CM10 stable from here: http://get.cm/?device=p970
Get the Google apps for 4.1.x from here: http://goo.im/gapps
How to Install
1. Reboot to recovery
2. Wipe data/factory reset
3. Install CM10 stable
4. Install Gapps for 4.1.x
5. Install P970-MackayKernel-3.0-Mod-for-CM10-GPS-Fix (attached to this post)
6. Reboot
Issues
1. In about phone, kernel version is shown as unavailable, but shows correctly in CPUSpy
2. If you enable Kernel Same Page Merging (in settings/Performance/Memory) it will cause occasional reboots/screen locks.
3. Very occasional vibration lock, lasting 30-40 seconds, so just wait if that happens. To avoid, disable Vibrate on Touch in settings/sound
4. Video recording with the CM10 camera crashes (still photo and gallery is fine), download Ucam Ultra https://play.google.com/store/apps/details?id=com.ucamera.ucam&hl=en for issue free video recording
Enjoy
Edit: Updated Mackay Kernel to 3.1
Edited 26/8/13: Updated Mackay Kernel to 3.2
Edited 28/10/13: Uploaded Mackey Kernel 1.9, which seems to fix the random rebooting bug, vibration bug and fixes a couple of games that didn't work on the 3.2 Kernel
It's not working on CM10.1? Could be fixed in that case?
Thanks for your work.
Mexickano said:
It's not working on CM10.1? Could be fixed in that case?
Thanks for your work.
Click to expand...
Click to collapse
Use Mackay ROM, it has this kernel included, or get the kernel from Mackay's thread. It will work with CM10.1.
The kernel in this thread has been modified for CM10.
Kernel 3.1 came out with fixes on vsync.Saves battery and improving performance
Sent from my LG-P970 using Tapatalk 4
TMinh said:
Use Mackay ROM, it has this kernel included, or get the kernel from Mackay's thread. It will work with CM10.1.
The kernel in this thread has been modified for CM10.
Click to expand...
Click to collapse
Kernel from Mackay's ROM have this
The advantages of CM10 over CM10.1
Video recording works
Skype Video Calling works
Barcode Scanning apps work
Burst mode camera apps work
Apps2SD works
Bluetooth File transfer (send/receive) works
GPS works
Click to expand...
Click to collapse
anyway thanks for make it more clear.
Question : cpu governor & i/o schedule in ur kasper_h's kernel mod have same original mackay kernel 3.0.8x ??
Sent from my LG-P970 using Tapatalk 2
jobzsparrow said:
Question : cpu governor & i/o schedule in ur kasper_h's kernel mod have same original mackay kernel 3.0.8x ??
Click to expand...
Click to collapse
Yes, its the same kernel, its the ramdisk that's diferent in this mod.
using with Kernel same page still not found problem (2.)
Sent from my LG-P970 using Tapatalk 2
@jason600 can you update the kernel to the latest one ( v3.1 ) ? Thanks :highfive:
DaemonOnx said:
@jason600 can you update the kernel to the latest one ( v3.1 ) ? Thanks :highfive:
Click to expand...
Click to collapse
Currenty testing 3.1 at the moment, as long as I don't find any serious issues, I'll upload it tomorrow.
Edit: Updated to Mackay Kernel 3.1, see attachment in first post.
yo!! good work , i'm installing
ps. this mod have got grant from kasper_h ?
Sent from my LG-P970 using Tapatalk 2
jobzsparrow said:
yo!! good work , i'm installing
ps. this mod have got grant from kasper_h ?
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean did I ask kasper_h for permission before doing this mod? Then the answer is no. Kasper_h has stated in the mackay thread he would not do a CM10 version, because of this I considered it would be ok provided it was fully credited to him, which I have done.
If kasper_h is unhappy with this mod for any reason, I'll take it down at once.
jason600 said:
Do you mean did I ask kasper_h for permission before doing this mod? Then the answer is no. Kasper_h has stated in the mackay thread he would not do a CM10 version, because of this I considered it would be ok provided it was fully credited to him, which I have done.
If kasper_h is unhappy with this mod for any reason, I'll take it down at once.
Click to expand...
Click to collapse
Let me answer this one myself, easiest I guess
As I have said in my own thread, I am perfectly happy with people using my work. That is what opensource is about: people improving each-others work And as said in the quoted post, I also said that I will not work on a CM10 version of the kernel, but that I am happy to support others who want to port the kernel to CM10.
kasper_h said:
Let me answer this one myself, easiest I guess
As I have said in my own thread, I am perfectly happy with people using my work. That is what opensource is about: people improving each-others work And as said in the quoted post, I also said that I will not work on a CM10 version of the kernel, but that I am happy to support others who want to port the kernel to CM10.
Click to expand...
Click to collapse
Thanks for that kasper, and my apologies for not asking beforehand, which with hindsight, I should of done.
both pretty Developers :thumbup:
Sent from my LG-P970 using Tapatalk 2
kasper_h said:
Let me answer this one myself, easiest I guess
As I have said in my own thread, I am perfectly happy with people using my work. That is what opensource is about: people improving each-others work And as said in the quoted post, I also said that I will not work on a CM10 version of the kernel, but that I am happy to support others who want to port the kernel to CM10.
Click to expand...
Click to collapse
Kasper Hettinga(Apologies if spelt incorrectly)You are a good man,You should have applied for Recognized Developer if not Contributer.You totally deserve it for the magical works you have done.If I could I would have bought you a sack of coffee beanz.Good man.
Sent from my LG-P970 using Tapatalk 4
---------- Post added at 11:06 PM ---------- Previous post was at 11:03 PM ----------
Please fix the KSM bug as I want/need to use that feature ,thanks
Sent from my LG-P970 using Tapatalk 4
BlackPie said:
Kasper Hettinga(Apologies if spelt incorrectly)You are a good man,You should have applied for Recognized Developer if not Contributer.You totally deserve it for the magical works you have done.If I could I would have bought you a sack of coffee beanz.Good man.
Sent from my LG-P970 using Tapatalk 4
Click to expand...
Click to collapse
If you look closely you see that it says "Recognised Developer" under his name :silly:
RomWiz said:
If you look closely you see that it says "Recognised Developer" under his name :silly:
Click to expand...
Click to collapse
Oh.I must have missed that
Sent from my LG-P970 using Tapatalk 4
BlackPie said:
Please fix the KSM bug as I want/need to use that feature ,thanks
Click to expand...
Click to collapse
Firstly, KSM works, but the bug might cause occasional reboots (maybe once per day)
Secondly, although Kernel Samepage Merging helps reduce ram usage, the effect is not that dramatic.
If you having memory problems, try the following:
1. Disable JIT. No noticable performance drop and each running process uses a few less mb's of ram. With lots of running apps, this adds up. To disable JIT, add the following line to your build.prop:
Code:
dalvik.vm.execution-mode=int:fast
2. Install Greenify https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en and hibernate apps that run in the background.
3. Install a 200mb swap file on the system partition (much faster than the sd card). You'll be able to load virtally any game/large app. Download Turbo Boost http://forum.xda-developers.com/showthread.php?t=2145133 and extract it on your pc. For a 200mb swap on system copy the file from TURBO BOOST MOD v3.02-AROMA\swap\system\200\etc\init.d\98swap_system_v300 and put it in /etc/init.d on your phone, then reboot. The swap file is created automatically.
4. Install V6 Supercharger http://forum.xda-developers.com/showthread.php?t=991276
Version 3.1 doesn't boot for me, while 3.0 does just fine.
*** This KERNEL ONLY SUPPORTS SAMSUNG TW ICS 4.0.4 ROMs (STOCK and CUSTOM). DOES NOT WORK IN CM or AOSP!!! ***
*** The Kernel is based on TW JB source which is safe ***
*** Still, I take no responsibility if the provided KERNELs causes any problem to your phone, you are warned! ***
Hello all,
I have been using all newer versions of rom for our "ancient but wonderful" G-Note. Still not quite happy and I missed the feeling of light and fast of the old ICS rom. The stock is not good enough, while the custom kernels most got pulled down and none supported trim, causing rom to slowdown after some time used.
So decided to make a custom ICS rom and kernel for myself. After many many testings with ICS kernel sources without feeling satisfied, I re-based to JB kernel source and wow! What a nice surprise. The combination made my Note flight!.
I feel extremely happy with it, my Note feel like a new device. So I share here with you:
Forest_ICS-Revival_TW-rom
Forest_ICS-Revival_kernel
KERNEL CHANGELOGS:
Kernel-V3:
- 1600 MHz OC CPU option, stock GPU
- Compile using uber toolchain
Kernel_V2:
- Reverse to stock CPU ang GPU
- Fix video recording
- improve battery life
Kernel_V1:
- GPU 3 steps (133-267-400)
- Enable OC CPU to 1600 (default). Allow to customize CPU voltage.
- PhilZ Touch recovery
- Exfat native support
- Trim support
- Various tweaks from Speedmod kernel
My favorite kernel governors and schedulers combination: SmartassV2+Vir or PegasusQ+Row
ROM FEATURES:
- Based on stock TW ICS 4.0.4: LR8
- Almost as stock. Removed lots of bloats apks.
- Add 14 toggles
- Call recording.
The room is extremely fast and responsive. It handle heavy games (such as Golfstar) like a breeze and also battery friendly. :good::good::good::good::good:
Downloads:
Forest_ICS-Revival_kernel_V3
Forest_ICS-Revival_kernel_V2
Forest_ICS-Revival_kernel_V1
Forest_ICS-Revival_TW-rom
I have benefited from many wonderful developers here at XDA:
Credits and Thanks to:
- @hardcore
- @Crimeofheart
- @maxfu
- @Philz
- @Chenglu
- @Lanchon
- @GeeckoDev
- @bauner
- @dsixda
- @archi
- @criskelo
- @Robbie Hood
- @dr.ketan
- others...
Kernel source: my Github
@forest1971 thanks for hanging on to the old note. Any development for this device is always appreciated.
Btw could u develop a kernel for cm13. Most of the n7000 users use cm13 and a new kernel would a useful addition. Afterall u r the only kernel developer left apart from bauner. Cheers
daneal2u said:
@forest1971 thanks for hanging on to the old note. Any development for this device is always appreciated.
Btw could u develop a kernel for cm13. Most of the n7000 users use cm13 and a new kernel would a useful addition. Afterall u r the only kernel developer left apart from bauner. Cheers
Click to expand...
Click to collapse
Probably when the rom is off Beta stage....
forest1971 said:
Probably when the rom is off Beta stage....
Click to expand...
Click to collapse
Thanks. But just so u know, the rom is stable to use with a few bugs here and there. Most of us users here have it as our daily driver. Hope to see ur kernel soon!
Thx for your effort
any chance of telling us the steps on installing the said files thank you
Exorcist74 said:
any chance of telling us the steps on installing the said files thank you
Click to expand...
Click to collapse
Reboot to a custom recovery.wipe data and then flash the rom.
If you are om an ics rom, then flash the kernel would be enough.
I will add the instruction later.
Sent from my GT-N7000 using Tapatalk 2
Is there Interactive governor in there? What are the frequency steps for the kernel? I might try this if I can find the TW roms.
AutumQueen92 said:
Is there Interactive governor in there? What are the frequency steps for the kernel? I might try this if I can find the TW roms.
Click to expand...
Click to collapse
Its not in the current kernel version.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
Its not in the current kernel version.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Oh okay then. I used it and realised the home button isn't working.
Sent from my Xperia C3 using XDA Labs
On which version of Android is based this ROM? It is stable or beta?
Thank y
AutumQueen92 said:
Oh okay then. I used it and realised the home button isn't working.
Sent from my Xperia C3 using XDA Labs
Click to expand...
Click to collapse
Can you elaborate please?
I have no problem with home button.
pickmod said:
On which version of Android is based this ROM? It is stable or beta?
Thank y
Click to expand...
Click to collapse
As shown in the title and OP, the rom is essentially a stock TW ICS 4.0.4 (LR8). I remove some bloatware apk and added few mods.
The main improvement is in the kernel.
forest1971 said:
Can you elaborate please?
I have no problem with home button.
Click to expand...
Click to collapse
The home button just won't respond. Short press and long press won't do amything, not even a phone restart.
Sent from my Xperia C3 using XDA Labs
AutumQueen92 said:
The home button just won't respond. Short press and long press won't do amything, not even a phone restart.
Sent from my Xperia C3 using XDA Labs
Click to expand...
Click to collapse
I mean you flash rom only or kernel only to another rom? did you make a lean install or dirty flash...? should make clean install and see how it goes.
forest1971 said:
I mean you flash rom only or kernel only to another rom? did you make a lean install or dirty flash...? should make clean install and see how it goes.
Click to expand...
Click to collapse
It was a clean install. Full wipe of data and cache, then install. Though I didn't do a factory reset and another cache wipe before reboot, could that be it?
Sent from my Xperia C3 using XDA Labs
AutumQueen92 said:
It was a clean install. Full wipe of data and cache, then install. Though I didn't do a factory reset and another cache wipe before reboot, could that be it?
Sent from my Xperia C3 using XDA Labs
Click to expand...
Click to collapse
It could be. clean install requires wipe data/factory reset.
forest1971 said:
It could be. clean install requires wipe data/factory reset.
Click to expand...
Click to collapse
Did a reflash, factory reset and cache wipe. Still nothing, since nobody reported anything it's probably a hardware thing but on Nightowl it works fine >.>
AutumQueen92 said:
Did a reflash, factory reset and cache wipe. Still nothing, since nobody reported anything it's probably a hardware thing but on Nightowl it works fine >.>
Click to expand...
Click to collapse
It's strange. There are a few dozens download so far, so I hope others will report.
In the mean time can you post a screening shot of the setting/about phone? I would like to make sure kernel version is correct one.
forest1971 said:
It's strange. There are a few dozens download so far, so I hope others will report.
In the mean time can you post a screening shot of the setting/about phone? I would like to make sure kernel version is correct one.
Click to expand...
Click to collapse
Baseband: DXLS8
Kernel version:
Code:
3.0.31-1103517_ICS_Revival_V1_OC
[email protected] #35
SMP PREEMPT Sun Feb 7 17:51:14 ICT 2016
Build number: Forest_ICS_Revival
Hi titan people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x and maybe 6.x.x roms like CyanogenMod and any other AOSP based rom.
Source links lead to my falcon source because they share the same source
How does one achieve such a compromise?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- reduce/increase speed of timers (depends on what type of function)
- etc. (most are not easy to explain)
This kernel is built with Linaro GCC 4.9.4 that is optimized for Cortex A7 processors.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
Personally, I do feel the performance difference. It is easier to notice the difference with lower level specs like ours.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest build
BasketBuild
Source:
GitHub
I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
XDA:DevDB Information
abyss kernel for aosp roms, Kernel for the Moto G 2014
Contributors
YoshiShaPow, arter97, flar2, Christopher83, Cl3Kener, frap129
Source Code: https://github.com/abyss-kernels/falcon
Kernel Special Features:
Version Information
Status: Nightly
Created 2016-05-14
Last Updated 2016-12-09
Main Patches and Features:
- KCAL Control Driver
- kexec hardboot patch for Multirom
- USB Force Fast Charge
- Abyss Optimizations (compiler)
- disabled debugging for more performance throughout
- lots of patches for better performance here and there... too many to list
How to install:
Download kernel from Basketbuild
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss kernel to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out well and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
First
I'll test
Do you have any preferred settings to tweak the kernel or does it come tweaked out of the box? Thank you.
Ashok Menon 101 said:
Do you have any preferred settings to tweak the kernel or does it come tweaked out of the box? Thank you.
Click to expand...
Click to collapse
Everything is good to go after flashing. The most you could do is increase the Read-ahead size to 258kB or 384kB but there's really no point; it won't do much.
YoshiShaPow said:
Everything is good to go after flashing. The most you could do is increase the Read-ahead size to 258kB or 384kB but there's really no point; it won't do much.
Click to expand...
Click to collapse
Alright, thank you.
Which ROM do you think is the best for this btw? No offence to anyone. I understand that egg-caf goes with everything but which do you prefer? Thank you.
Ashok Menon 101 said:
Alright, thank you.
Which ROM do you think is the best for this btw? No offence to anyone. I understand that egg-caf goes with everything but which do you prefer? Thank you.
Click to expand...
Click to collapse
My current setup is Exodus 6.0 and egg-caf kernel. Sometimes I forget that I'm using a phone (Moto G 2013) that costs less than $200 USD.
New build with modified values; it should improve multitasking performance.
egg-caf-titan-nightly-20160515.zip
YoshiShaPow said:
..... I do not mind if there's some non-development/off-topic discussion here, just no discussion about other works that is nowhere near related to mine.
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread. ......
Click to expand...
Click to collapse
As you kindly allow some non-development/off-topic discussion I´d like to ask a question about kernel flashing.
You write in your installing explanation
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
It´s a thing I often heard before. As an example: When I´m coming from a different kernel (I flashed a custom rom and then changed the kernel) and want to go back to the "stock" one why isn´t it enough to unzip my custom rom and flash the boot.img inside?
Where is the difference to dirty flash the whole rom?
Thx in advance.
Wolfcity said:
As you kindly allow some non-development/off-topic discussion I´d like to ask a question about kernel flashing.
You write in your installing explanation
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
It´s a thing I often heard before. As an example: When I´m coming from a different kernel (I flashed a custom rom and then changed the kernel) and want to go back to the "stock" one why isn´t it enough to unzip my custom rom and flash the boot.img inside?
Where is the difference to dirty flash the whole rom?
Thx in advance.
Click to expand...
Click to collapse
Your question is not even close to what I mean when I say off-topic :highfive: (it is on-topic). Some kernel developers add scripts, patches, ramdisk modifications, etc in their zips to tune different types of values. The easiest way to get rid of all of that is by dirty flashing the rom, which replaces the /system partition and ramdisk with fresh ones from the dirty flash.
YoshiShaPow said:
Your question is not even close to what I mean when I say off-topic :highfive: (it is on-topic). Some kernel developers add scripts, patches, ramdisk modifications, etc in their zips to tune different types of values. The easiest way to get rid of all of that is by dirty flashing the rom, which replaces the /system partition and ramdisk with fresh ones from the dirty flash.
Click to expand...
Click to collapse
Thx for your fast reply and good to know that my question was on topic.[emoji6] Some devs are very delicate when someone hijacks their thread.
Your answer declares the other files, that can be found in some flashable zip kernels.
Is there something to pay attention of when dirty flashing the same ROM again? Ok,don't wipe data is a clear thing but I think of unmounting partitions etc to don't mess up.
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
Thx for your fast reply and good to know that my question was on topic.[emoji6] Some devs are very delicate when someone hijacks their thread.
Your answer declares the other files, that can be found in some flashable zip kernels.
Is there something to pay attention of when dirty flashing the same ROM again? Ok,don't wipe data is a clear thing but I think of unmounting partitions etc to don't mess up.
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
The Roms updater script will mount the partitions it needs. Just make sure after flashing that you wipe cache and dalvik/art cache. Most gapps have a backup script that prevent it from being removed during dirty flashes. If your gapps are retained, you know you've done it correctly.
YoshiShaPow said:
The Roms updater script will mount the partitions it needs. Just make sure after flashing that you wipe cache and dalvik/art cache. Most gapps have a backup script that prevent it from being removed during dirty flashes. If your gapps are retained, you know you've done it correctly.
Click to expand...
Click to collapse
If someone (a friend oft mine or my cat, not me!) [emoji41] has deleted this backup script because he thought he doesn't need it anymore I think he has to flash gapps again too?
Thx for making things more clear and reminding me not to delete files flippantly.
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
If someone (a friend oft mine or my cat, not me!) [emoji41] has deleted this backup script because he thought he doesn't need it anymore I think he has to flash gapps again too?
Thx for making things more clear and reminding me not to delete files flippantly.
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you will need to flash gapps again. Make sure that if you still have the backup script to not reflash gapps because I've had conflicts with that before. Not very fun.
YoshiShaPow said:
New build with modified values; it should improve multitasking performance.
egg-caf-titan-nightly-20160515.zip
Click to expand...
Click to collapse
always good to test the new features! downloading :laugh: :victory:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
DeluxeMark said:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well you should choose:
Decipher: stable,enough features, battery.
Egg: Stable, no extra features, performance.
Performance is much better with egg than decipher.
But in terms of battery, decipher is the clear winner.
I've been using the egg kernel for a few days now with cm13 and it's good enough for me.
Performance is really good. I don't really care about the battery as I always have a charger with me always so I don't really mind.
Overall, egg kernel is pretty good.
DeluxeMark said:
Answer me a question, why should change decipher kernel for egg-caf kernel?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
How about you answer me this.
OP said:
Also, please refrain from comparing works here; it really kills the spirit of development. Go do that in some other thread.
Click to expand...
Click to collapse
How does one get people to not do something in a thread? Back in the older days, that would be by writing something boldly in the OP. Guess that does not work anymore.
Honestly, you can do whatever the heck you want anywhere else, just not in my thread where I have my posting guidelines set.
Edit: also, I clearly state what is different in my kernel from others in the OP
It was just a question,not a comparison
Sent from my Moto G 2014 using XDA-Developers mobile app