Database Develop

[ROM] Helly Bean [4.1.1] (8/17/12) - Vibrant - DerTeufel1980

Please note! Due to certain issues, as of 08/26 I have moved on to the official CM10. If time permits, I'll update this OP, but not making promises.
WARNING: This ROM probably still has intermittent emergency dialing issues. Do not use it for a daily driver when you're out or could need 911 or any emergency number. If you STILL choose to use it at those times, it's your own fault!
Let's get this out of the way:
This thread is for DEVELOPMENT! If you have non-development questions...which is just about everything that seems to show up anymore.....go to the following thread:
http://forum.xda-developers.com/showthread.php?p=28730705
From DerTeufel1980:
I want to present to you the Helly_Bean ROM. The following description is taken from the original thread over in the i9000 section. You can find his thread here:
http://forum.xda-developers.com/showthread.php?t=1775169
This ROM is not the official built of CM10 by Teamhacksung.
It is based on their source code, but with some modifications, to allow the use of /datadata partition
Click to expand...
Click to collapse
Many many thanks, to pawitp, FaultExeption, Jt1134 and all the other people who commit to gerrit. without these, this ROM wouldn't be possible
What's not working or known bugs?
[FIXED]- toggling the GPS repeatedly will reboot phone.
[FIXED]- mounting of external sd to pc (you can switch to mtp mode in recovery to "fix" this).
Click to expand...
Click to collapse
******************
Build 08/20 is showing as available. I don't recommend dl'ing it as its caused many to have baseband issues. I've contacted Der to look into this, which I'm sure he will when time permits.
(08/17)New build available.
This is md5 sum:
cd703c25d560ce4c3d33cbfcab724427
Changes:
- compiled from latest sources, but still using /datadata (going to be change probably soon)
- renamed the two navbar menus
- added Facebook sync (you have to install Facebook app before)
- added i9000b to supported devices
- (hopefully) fixed modem/baseband issue
- added possibility to install devil kernel apps to installer
- fixed mms for showcase
http://rootaxbox.no-ip.org/derteufel/Helly_Bean/rom/
Wipe not needed if flashing from a previous version, but is highly recommended. Be sure to flash the add-on also.
TF here.....I found, as often is the case, I had to flash the ROM and let it boot up, then go back in and flash the add-on. After that.....golden!
(08/15)New test build up now.
Why test build?
- Because I have added two new devices, for which I don't know if it is working well for them
- I have fixed the navbar not appearing, but now there a two menus in system which both are named the same. One is for enabling, the other for customization. I am working at integrating the two into one menu, but I did not get it yet.
- ffc support for Vibrant
Install process has not changed, but if you are coming from another ROM/kernel than mine, you should create a folder devil at your sdcard, place a file named device into it, and write your device name in it, valid names are:
i9000
cappy
vibrant
fascinate
mesmerize
showcase
users of mesmerize and showcase have to do this!
Other changes:
If devil app(s) are not installed, the menu is not displayed under system settings (many thanks to phillbring for coding me this).
md5sum is: 3b11a106529f10236d2e6139416bc346
http://rootaxbox.no-ip.org/derteufel/test/
Wipe not needed if flashing from a previous version, but is highly recommended. Be sure to flash the add-on also.
From TF: I love the Cid theme from Annex, but flashing his most recent version sent me into bootloops. I'm assuming he will update as soon as he has a chance.
(08/13) New instructions for flashing. Wipe not needed if flashing from a previous version, but is recommended. Be sure to flash the add-on also.
The files can be found at:
http://rootaxbox.no-ip.org/derteufel/Helly_Bean/
Install instructions:[/SIZE]
Coming from any other rom:
- make sure to have gingerbread bootloaders. (Remember, Google is your friend)
- wipe data/factory reset
- flash allinone.zip
- reboot recovery
- flash allinone.zip again
- flash Helly_Bean_AddOn or Helly_Bean inverted AddOn
coming from previous version:
- flash allinone.zip
- flash Helly_Bean_AddOn or Helly_Bean inverted AddOn
Attention: this is still a test. Don't flash it if you don't know what you are doing/how to get back!
For a new feature cherry-picked last night, go to settings --> system
*************************
You can find the official website for this project here (I don't maintain the site myself, if there is anything website related to ask, please use the contact info from the web site):
http://hellybean.site11.com/download.html
You'll find download links and faq on this site.
The usual back-up, complete wipe (if this is the first time flashing this ROM), flashing of files and fix permissions applies.
***********
One thing I noticed is that if you follow the normal flash procedure, it can bootloop, or at least appears as though it is. One way to fix that is to flash the ROM only and boot up you phone. Then go back into recovery and flash the add-on. That has worked every time it happened to me.
You can find the changelog here:
http://hellybean.site11.com/changelogg.html
For mirrors, please take a look at the thread. if you don't find any, just ask in the thread.
I really didn't want to mention this, but lack of experience by some members seems to require it:
If you are unsure of ANYTHING that goes with flashing a ROM, do research first. If you honestly can't find the answer, ask questions. We are not responsible for any action that happens to your phone.
Many thanks to:
- be18
- mkalter, who got the first running JB ROM
- elitemovil (who was the first who got gsm working)
- stratosk (from who's initramfs I could start build my first JB booting kernel)
- teamhacksung/pawitp for the ROM sources
- team nyx who always have good tips for me, if i get problems with my kernel
- SysTem-X for hosting
- Rootax for hosting
- RolluS for hosting
- many thanks also to the other people who have created mirrors
- if i have forgotten you, please PM me
If you consider a donation for this ROM and kernel, please follow this link:
donate to DerTeufel1980
________________________________
Now, from TFordham (you can just call me TF):
I've been using this ROM for some time now, and really happy with it. Personally, I think this is the best JB ROM out there. I find it very smooth, and for an early release, quite stable.
I do want to point out that I'm not a dev at all. The Helly Bean ROM is from DerTeufel1980 and his team. I put this up since his ROM is being mentioned in another ROM forum, but figured it might as well have its own home
Something else I want to be clear about is that I have no technical knowledge on creating ROMs, kernels or other things of this nature. I simply wanted to let other Vibrant owners know this ROM is out there. This fantastic XDA community is the place to ask, as there are plenty who know FAR more than I. In addition, DerTeufel1980 is active in this forum, ago if there are issues, he will help address them. While I appreciate the "thanks" button being hit, it is his comments in this thread that should be thanked.
Sent from my SGH-T959 using xda app-developers app

HellyBean 0801 is definitely the fastest JB ROM for the Vibrant because of the included Devil 1.1.0 kernel and the use of the faster datadata partition. All Vibrant users should donate to Derteufel1980 for his amazing kernel and now ROM support. He is the only ICS/JB kernel developer we have right now so we must treat him right.

How does this differ from the CM10 v8? Other than the kernel of course.

gunks said:
How does this differ from the CM10 v8? Other than the kernel of course.
Click to expand...
Click to collapse
Keeping in mind I'm far from the most tech savvy flasher out there, like I mentioned, I don't see a huge difference in most of the JB ROMs. I just happen to like this one a lot. Others may be able to get into far more detail on why it's good compared to other (or vice versa, for that matter, if they feel that's the case).
Sent from my SGH-T959 using xda app-developers app

More info here http://hellybean.site11.com/

hurtz777 said:
HellyBean 0801 is definitely the fastest JB ROM for the Vibrant because of the included Devil 1.1.0 kernel and the use of the faster datadata partition. All Vibrant users should donate to Derteufel1980 for his amazing kernel and now ROM support. He is the only ICS/JB kernel developer we have right now so we must treat him right.
Click to expand...
Click to collapse
There is no link to Devil 1.1.0. I can see a folder, but it is empty. I do see and know that Devil 1.0.4 works.

chadhoard said:
There is no link to Devil 1.1.0. I can see a folder, but it is empty. I do see and know that Devil 1.0.4 works.
Click to expand...
Click to collapse
The kernel is in the ROM...you don't need to flash it separately.
Sent from my SGH-T959 using xda app-developers app

TFordham said:
The kernel is in the ROM...you don't need to flash it separately.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Good to know!! Now, I flashed the ROM, Kernel 1.0.4, and add-ons yesterday. Can I just flash the ROM without wiping?

chadhoard said:
Good to know!! Now, I flashed the ROM, Kernel 1.0.4, and add-ons yesterday. Can I just flash the ROM without wiping?
Click to expand...
Click to collapse
Again, not a techy. Give it a try, just do a back-up first. I tend to always do a full wipe. Seems like ROMs just run better that way, IMO.
Sent from my SGH-T959 using xda app-developers app

TFordham said:
Again, not a techy. Give it a try, just do a back-up first. I tend to always do a full wipe. Seems like ROMs just run better that way, IMO.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Thanks!

Its nice too see an official home/thread for helly bean. Thanks to everyone involved!
Der Teufel nennt mich bruder.
drool on my chin from a mouth full of jellybeans....

Nice
So far so good. No problems at all. Just waiting 15 mins b4 I reboot and play with it. Why 15 mins cause files are still installing. Stay thirsty my friends.

shownuff said:
So far so good. No problems at all. Just wa 15 mins b4 I reboot and play with it. Why 15 mins cause files are still installing. Stay thirsty my friends.
Click to expand...
Click to collapse
Delete...I misunderstood what you were saying.

I think that DerTeufel has to be the OP.
Did you ask him before put this?
Are you able to answer questions about Kernel, ROM, Modems, UV, NL etc?
Update the proper content of our device?
This is why the "leader team" or the Dev has to be the OP.
Not trolling, just saying: If we want a better Topic it has to be created by DerTeufel.

Waldos said:
I think that DerTeufel has to be the OP.
Did you ask him before put this?
Are you able to answer questions about Kernel, ROM, Modems, UV, NL etc?
Update the proper content of our device?
This is why the "leader team" or the Dev has to be the OP.
Not trolling, just saying: If we want a better Topic it has to be created by DerTeufel.
Click to expand...
Click to collapse
Thanks for your concern. I've contacted him. If he wants anything changed, or even to have it closed, I'm sure he'll let me know.
Sent from my SGH-T959 using xda app-developers app

hurtz777 said:
HellyBean 0801 is definitely the fastest JB ROM for the Vibrant because of the included Devil 1.1.0 kernel and the use of the faster datadata partition. All Vibrant users should donate to Derteufel1980 for his amazing kernel and now ROM support. He is the only ICS/JB kernel developer we have right now so we must treat him right.
Click to expand...
Click to collapse
We have like 3 other devs with functional jb ROMs.
Sent from my SGH-T959 using xda app-developers app

This download. Is FRICKING SLOW.
Sent from my SGH-T959 using xda app-developers app

How's the battery life on this rom? Im getting amazing battery on CM10 Alpha Preview by FE with Devil 1.0.4 test3 JB kernel. I wanna know if this battery's any good before I switch.

Can someone quickly summarize how to get here from Stock? I had done it a long time ago to the ics roms and can't do it again... I"m missing some major step.
So far:
heimdall to stock
root update.zip
install rommanager and then cwm install and re-boot to flash update.zip -> cwm recovery.
Flash this rom
-> results in boot loop.
What am I missing?

spybld said:
Can someone quickly summarize how to get here from Stock? I had done it a long time ago to the ics roms and can't do it again... I"m missing some major step.
So far:
heimdall to stock
root update.zip
install rommanager and then cwm install and re-boot to flash update.zip -> cwm recovery.
Flash this rom
-> results in boot loop.
What am I missing?
Click to expand...
Click to collapse
My experience from going all the way back to stock is that I had to flash a Gingerbread ROM first, then wipe that and install a later ROM (ICS, JB).
Sent from my SGH-T959 using xda app-developers app

[Kernel][GPL][4.3 JS][August 6][a5] m_plus kernel for mako

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

[Kernels][4.3.1][Repacks]Repacked-Ramdisks[05.11.2013]

KERNEL REPACKS: Alternative to 'Any kernel'​
I am not resposible for any damages.. or anything tbh, i don't care about you, this disclaimer allows me to say that cuss, your doing this at your own risk, so do it right, or don't do it at all, if you don't know what your doing, then please, follow the tutorial for flashing..
Click to expand...
Click to collapse
So what are Re-Packed Kernels?
Re-Packed kernels are kernels with different ramdisks to the original Kernel, they use the same zimage but they use a different ramdisk, this means they have all the same features that is offered by the original kernels, such as clocks and governors and specific mentioned features. As the ramdisk changes for different Android versions in this case 4.3 to 4.3.1 and it stops incompatibilities. This will fix the android.phone fc's in the new nightlies and for the moment Vanir nightlies too. I intend to update them every significant update or every week, so i guess we can class them as weeklys as, i'll be releasing them weekly i suppose? I will also be updating the zimages as the origanal devs make their changes!​
How to Flash
Code:
[B]My Method (stupid but mine)[/B]
[I]
-Download Chosen Kernel
-Move to Root of SDcard/Internal Storage
-Reboot to Recovery
-Wipe Cache and Dalvik Cache
-Flash Kernel
-Fix Permissions
-Reboot
[/I]
[B]Most used method[/B]
[I]
-Download Chosen Kernel
-Move to Root of SDcard/Internal Storage
-Reboot to Recovery
-Flash Kernel
-Reboot
[/I]
Both methods will flash the kernel, disputes that i take pointless steps, however each to their own, but that's just a rough idea on how to flash the Kernel, for those of you who do not already know.
Downloadsss
Code:
[B][U]Cyanogenmod 10.2[/U][/B]
[URL="http://d-h.st/IFG"]IodakV8.5[/URL]
[URL="http://d-h.st/F3Z"]IodakV8[/URL]
[URL="http://d-h.st/8n1"]OptimusPrimeV2.7[/URL]
[URL="http://d-h.st/z3I"]OptimusPlay2.53[/URL]
[URL="http://d-h.st/Buu"]WWJBv008b[/URL]
[B][U]Vanir AOSP[/U][/B]
[URL="http://d-h.st/jUO"]IodakV8.5[/URL]
[URL="http://d-h.st/o06"]IodakV8[/URL]
[URL="http://d-h.st/u4c"]OptimusPlayV2.53[/URL]
[URL="http://d-h.st/M7Z"]OptimusPrimeV2.7[/URL]
[URL="http://d-h.st/I88"]WWJBv008b[/URL]
Changelog
Code:
[B]06.11.2013[/B]
[I]Updated a tutorial on flashing
Updated some info on what it is[/I]
[B]05.11.2013[/B]
[I]Updated Vanir Kernels, should be A-Ok now![/I]
[B]02.11.2013[/B]
[I]Updated to Ramdisk of CM10.2 01.11.2013 Nightly[/I]
[I]Added Vanir Kernels[/I]
[B]01.11.2013[/B]
[I]First Releases for 4.3.1[/I]
Credits:
@demitrius OP OP
@laufersteppenwolf OP
@iodak OP

Thank you for taking the time to do this, hope it results in less people posting the same question over and over again. I was waiting for a free night to learn how to do it myself actually but no rush now
One question though, do these offer any significant advantage over the Anykernel versions? Or any obvious disadvantages I'm missing?

Werewolf kernel not working with latest Vanir nightlies

spamcakes said:
Thank you for taking the time to do this, hope it results in less people posting the same question over and over again. I was waiting for a free night to learn how to do it myself actually but no rush now
One question though, do these offer any significant advantage over the Anykernel versions? Or any obvious disadvantages I'm missing?
Click to expand...
Click to collapse
Well what AnyKernel does is when you flash the .zip first it pulls the current bootimg out of the boot partition unpacks it, unpacks the bootimg from the .zip and moves the initrd(ramdisk) from the boot partition into the zip then repacks the bootimg and then proceeds the normal procedure of flashing a kernel.
What this means is it does what the OP has done automatically. The disadvantage to this, is you need the ROM you want to flash a kernel for to be already flashed before you flash the AnyKernel(in between flashing a rom and the following kernel you most likely need to reboot in order for the kernel contained in the ROM package to be flashed out of staging). Or else it will repack the wrong ramdisk. The OPs kernels dont need to worry about this.

Iodak v8 does also not work on vanir. Got com.android.phone fcs...

Might upload iodak 8,5 with ramdisk fixed?
Werewolfs don't work on Slimbean 2.1 either.

spamcakes said:
Thank you for taking the time to do this, hope it results in less people posting the same question over and over again. I was waiting for a free night to learn how to do it myself actually but no rush now
One question though, do these offer any significant advantage over the Anykernel versions? Or any obvious disadvantages I'm missing?
Click to expand...
Click to collapse
It doesn't require much teaching, its a simple task in it's self and works on windows! Look in my signature, i wrote the scripts to do it Go to that thread i think theres a short tutorial in it.. If not pm me and i'll write one up And these are just alternatives
ex0rt said:
Werewolf kernel not working with latest Vanir nightlies
Click to expand...
Click to collapse
Vanir uses a complete different ramdisk does it not? :s i said wait for the variants
JoinTheRealms said:
Well what AnyKernel does is when you flash the .zip first it pulls the current bootimg out of the boot partition unpacks it, unpacks the bootimg from the .zip and moves the initrd(ramdisk) from the boot partition into the zip then repacks the bootimg and then proceeds the normal procedure of flashing a kernel.
What this means is it does what the OP has done automatically. The disadvantage to this, is you need the ROM you want to flash a kernel for to be already flashed before you flash the AnyKernel(in between flashing a rom and the following kernel you most likely need to reboot in order for the kernel contained in the ROM package to be flashed out of staging). Or else it will repack the wrong ramdisk. The OPs kernels dont need to worry about this.
Click to expand...
Click to collapse
+1, great explanation!
Triads123 said:
Iodak v8 does also not work on vanir. Got com.android.phone fcs...
Click to expand...
Click to collapse
I still think Vanir has a different Ramdisk..
baxtex said:
Might upload iodak 8,5 with ramdisk fixed?
Werewolfs don't work on Slimbean 2.1 either.
Click to expand...
Click to collapse
I can't even find iodak 8.5 and i'm not sifting through ~130 pages tofind it either If you couldupload it here for me or give me a link that'd be great!
Well it would seem werewolfs is corrupt/i did something wrong (Highly doubt the second one of course) Will be reuploading all tonight with the ramdisk from the latest nightly..

https://www.dropbox.com/s/bene73b8qe5wz8l/iodakX3_v085CM-10.2.zip
Here you go iodak 8.5 without ramdisk repack!

So it'll work with todays cm 10.2 m1 ?
Sent from my LG-P880 using xda app-developers app

Iodak v8 = android.phone fc on cm10.2 latest
Sent from my smart frying pan (Tegra 3)

All Kernels Updated with Ramdisk from CM10.2 Nightly 01.11.2013! Also Added Iodak v8.5
Vanir coming later on, i'm gonna go eat my meatloaf now :3
Update#1: Optimus Prime was a weird zip, don't know what happened, link removed, reupload the correct zip in a minute
Update#2: Vanir Kernels Updated

WerewolfJB and iodakX3_v085 doesnt work for Vanir
android.phone fc

ex0rt said:
WerewolfJB and iodakX3_v085 doesnt work for Vanir
android.phone fc
Click to expand...
Click to collapse
Did you use the Vanir variation? Or the CM10.2 variation? Try both? I don't know? Where are you downloading vanir from? Did you wipe caches before install and fix permissions after???
Sent from my N7 2k13

penguin449 said:
Did you use the Vanir variation? Or the CM10.2 variation? Try both? I don't know? Where are you downloading vanir from? Did you wipe caches before install and fix permissions after???
Sent from my N7 2k13
Click to expand...
Click to collapse
I tried both, but vanir versions dont work on latest nightlies rom from vanir. Gonna try wipe cache, posting soon..
@update
Still not working..

ex0rt said:
I tried both, but vanir versions dont work on latest nightlies rom from vanir. Gonna try wipe cache, posting soon..
@update
Still not working..
Click to expand...
Click to collapse
What vanir nightlies? :s the only vanir I was aware of was last built in September and that's the ramdisk I used for them.. Post a link to night lies if we are getting them...
Sent from my LG-P880 using XDA Premium 4 mobile app

penguin449 said:
What vanir nightlies? :s the only vanir I was aware of was last built in September and that's the ramdisk I used for them.. Post a link to night lies if we are getting them...
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here you go:
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/p880/

For me also the New repacked Iodak Kernel does not work. Only the anykernel Iodak v8 work without any problems for me. By all the other Kernels i got everytime com.android.phone fcs..

Triads123 said:
For me also the New repacked Iodak Kernel does not work. Only the anykernel Iodak v8 work without any problems for me. By all the other Kernels i got everytime com.android.phone fcs..
Click to expand...
Click to collapse
+1, tested all 5 vanir repacks on 110113 nightly
Gesendet von meinem Optimus 4X HD mit Tapatalk 2

House.m.d said:
+1, tested all 5 vanir repacks on 110113 nightly
Gesendet von meinem Optimus 4X HD mit Tapatalk 2
Click to expand...
Click to collapse
My fault, was completely oblivious to official Vanir nightlies, update coming tonight cuss I have work now! Sorry, my noob mistake

House.m.d said:
+1, tested all 5 vanir repacks on 110113 nightly
Gesendet von meinem Optimus 4X HD mit Tapatalk 2
Click to expand...
Click to collapse
Doesnt work for me :/ guess I'll have to wait for new repacks

For CM11 users, here's how you can use AOSP(Non CAF) kernels on CM11

For those that want to use AOSP kernels on CM11, here's a zip to do it. The non CAF zip includes libs & the stock kernel(has init.d support) from the stock KOT49H build and the enable zip includes libs & stock kernel from CM11 1-9-14 build. It can be used on older builds of CM but CM does make changes to the kernel ramdisk every so often, so I can't guarantee it will work on all builds but it should work on the last couple of weeks builds.
The only catch is that you MUST use the kernel ramdisk from CM's kernel as there is stuff in there that is needed, so if you just flash a AOSP kernel that is built as a boot.img, while you will not have color issues, you will have FCs for theme manager, etc.
Now for those that want to know the specifics, these 4 libs are what control it
Code:
gralloc.default.so
gralloc.msm8960.so
hwcomposer.msm8960.so
liboverlay.so

thanks , this is what i need
great job

Awesome, works great, now I can use the ROM I wanted with the kernel I wanted
Sent from my Nexus 4 LTE 4G Telcel Mexico

Hi, if I understand correctly I need to flash the non caf zip then the non caf kernel zip ? Thanks
Sent from my Nexus 4 using XDA Premium 4 mobile app

@The Guy above me: I'd think so too, as long as it does not require it's own modified ramdisk (?). Not sure though. I'll test it when I have some time after the weekend. Interesting stuff. indeed. Finally acces to some more custom kernels on CM11.

accountabc said:
@The Guy above me: I'd think so too, as long as it does not require it's own modified ramdisk (?). Not sure though. I'll test it when I have some time after the weekend. Interesting stuff. indeed. Finally acces to some more custom kernels on CM11.
Click to expand...
Click to collapse
I flashed in that order and it works great with semaphore kernel
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 12:18 PM ---------- Previous post was at 12:16 PM ----------
@Calkulin it would be great if you could port that to the nexus 7 2013, it really lacks CM compatible kernels ...
Sent from my Nexus 7 using XDA Premium 4 mobile app

Thanks for the useful patch :good:
As for CM kernel ramdisk:
Calkulin said:
The only catch is that you MUST use the kernel ramdisk from CM's kernel as there is stuff in there that is needed, so if you just flash a AOSP kernel that is built as a boot.img, while you will not have color issues, you will have FCs for theme manager, etc.
Click to expand...
Click to collapse
How do we use the CM kernel ramdisk with a kernel that isn't a CM kernel?

We will need to get the zImage somehow. Is it the only way?

tykate said:
Thanks for the useful patch :good:
As for CM kernel ramdisk:
How do we use the CM kernel ramdisk with a kernel that isn't a CM kernel?
Click to expand...
Click to collapse
you could try using script to unpack bootimage
or kernel like faux, semaphore, ak, or kernel that use anykernel method, you just need to add that 4 file to zip, and add script to unpack that file in updater-script

Calkulin said:
Now for those that want to know the specifics, these 4 libs are what control it
Code:
gralloc.default.so
gralloc.msm8960.so
hwcomposer.msm8960.so
liboverlay.so
Click to expand...
Click to collapse
Nice, this works just perfectly fine. By chance, does someone also know about what are the specific changes in the source code?
Edit: don't mind. I've found a fix which has to be applied in kernel.

gpl | abyss kernel 5.10 | cm-14.x/cm-13.x

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