Related
Please stay tuned
Reserved
I heard this kernel is one of great kernel in GNex forum.
I'll flash it right away
Sent from my Nexus S using Tapatalk 2
Cool, I love flashing new releases
A new challenger appears! I'll have to try this out sometime in the near future, but it will be hard to tear me away from Marmite.
Sent from my Nexus S using xda app-developers app
Does not boot.
using latest CM10 nightly
Brishen said:
Does not boot.
using latest CM10 nightly
Click to expand...
Click to collapse
No Custom IOCTL stuff I guess..
Sent from my Nexus S using Tapatalk 2
Op does not Specify weather this Kernel is for,
CM Based roms
AOSP Based roms
AOKP Based Roms
I Tried it on Latest Paranoid Android (CM Based) and it black screens.
Is now compatiable with AOSP ROMS Only. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23
Thank you for your sharing.
purian23 said:
Should be compatible with all ROMS out there. Same as it is on the Nexus. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23
Click to expand...
Click to collapse
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
This is 5.4 MB? Hmmm...need to see how it performs.
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.
anshumandash said:
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.
Click to expand...
Click to collapse
also no Crt Fix ..
Didnt work for me with a cm10.
raducux said:
Didnt work for me with a cm10.
Click to expand...
Click to collapse
will a cm10 version be available?
Its based on aosp source and was tested on crossbones ROM, I'll get the rest of you guys figureld out soon.
---------- Post added at 02:18 PM ---------- Previous post was at 01:22 PM ----------
Big Dog KMc said:
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
Click to expand...
Click to collapse
I understand, looks like CM requires a kernel patch for this http://review.cyanogenmod.org/#/c/23541/
I was unaware as it was tested on an aosp based rom
We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks
bbedward said:
We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks
Click to expand...
Click to collapse
Looks like I won't be trying this kernel, then.
Stay tunes for V2, thanks for the feedback from some of you. Added bigmem, voodoo color support, usb fast charge support, some more lowmemorykiller upstream updates, and also cifs+fuse FS support.
ScOULaris said:
Looks like I won't be trying this kernel, then.
Click to expand...
Click to collapse
We're offering this to the community with no expectations that you use it, but for those who do use it we want them to be completely satisfied.
If it doesn't work for you, then I encourage you to use something from one of the other great development teams out there.
I thought of a couple solutions: 1.) creating 2 kernel builds, 2.) creating a sysfs interface so CM users could flash an init script that'd enable the CM ioctl's. Basically it comes down to this - neither solution is up to my standards for now.
THIS OP IS OUTDATED! WIP!
Hello everybody!
You might or might not have already heard of MultiROM, THE multi-boot mod for the Nexus 7. I have recently found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot. I compiled iodak's v07 CM kernel and official CM kernel with the patch, choose one of them. I have noticed an approx. 3 sec. vibration at boot with iodak, that's why I have included official CM kernel too.
Finally you have to flash MultiROM.
Links
You can find everything at http://d-h.st/users/Adam77Root/?fld_id=22980#files.
MultiROM_TWRP_X3.zip: The modified TWRP recovery from latest sources with gordon0001's device-specific changes and MultiROM support.
CM_kernel_patched.zip and iodakX3_v07CM_patched.zip: Official and iodak CM kernels with Kexec-hardboot patch.
iodakX3_v07_patched.zip: iodak stock kernel with Kexec-hardboot patch.
MultiROM_P880_v12.zip: The actual MultiROM package. Contains the latest version of Trampoline (the init binary of the system) and MultiROM binaries with all the needed device-specific changes. Even Pong works pretty smooth.
x3_hardboot.diff: Kexec-hardboot patch for 3.1.10 kernel.
mrom_p880.patch: Device-specific changes for Trampoline and MultiROM.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions.
Known bugs
Reboot to recovery doesn't work.
USB tab doesn't do anything. This is because USB host mode (OTG) doesn't work on our device. Will reach out to kholk regarding this.
Sometimes in landscape mode, the default selected rom gets booted on the first touch. This is yet to be investigated.
Changelog
14 August 2013: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@mkasick for original Kexec-hardboot implementation
@iodak for his kernel
@gordon0001 for the device-specific TWRP modifications
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!
General use
Some notes and instructions regarding general use
For now, I have only provided patched 4.2.2 CM kernels. This means, you have to be on CM or CM-based rom with Android version 4.2.2. Don't try it with stock at the moment in any way. It won't work, but is on the to-do list. As Kexec-hardboot will reach out to devs, it will be supported in every rom ultimately.
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method.
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share the kernels between the same Android version (i.e. stock base->only stock rom can use shared kernel, 4.2 base->only 4.2 rom can use shared kernel, 4.3 base->only 4.3 rom can use shared kernel, etc.), but this is not the case with the Kexec method. Just keep in mind that for example even if your base rom is CM, for a stock secondary rom you have to flash a stock patched kernel.
The build
Some notes about the build
x3_hardboot.diff: This is the Kexec-hardboot patch for the 3.1.10 kernel. Since it is needed for target kernels as well, I would like to reach out in this post to @arararagi, @demetris_I, @iodak, @kholk, @laufersteppenwolf and @Pesach85 (in no particular order, this is how your threads are in order in Original Android Development forum right now). I and fellow users would be grateful if you could include the patch in the kernel so they can be used as both host and target kernels as well. UPDATE: It doesn't reserve one more megabyte before ram_console from now on.
mrom_p880.patch: This contains all the device-specific patches that are needed to get MultiROM booting and working on the P880. It is built on top of the latest git changes as of today. It also contains some comments about multiple devices compatibility, those are reminders for Tasssadar.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions. Needs to be put into TWRPdir/gui/devices/720x1280/res/. The recovery I have created is based on the latest MultiROM TWRP with @gordon0001's device-specific changes.
You can find links to the upstream MultiROM and MultiROM TWRP in the original thread.
Simply incredible!!! :thumbup:thanks a lot man. I always wanted to try dualboot
Sent from my LG-P880 using xda premium
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
tnx for your very nice work
how i can flash twrp ?
i want to flash it on cwm but i cant
edite : thats my fault i am so sorry
penguin449 said:
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Click to expand...
Click to collapse
If anybody won't be faster, I will provide it tomorrow.
laufersteppenwolf said:
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Take your time, rest and get better!
Sent from my LG-P880
Adam77Root said:
If anybody won't be faster, I will provide it tomorrow.
Sent from my LG-P880
Click to expand...
Click to collapse
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
penguin449 said:
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
Click to expand...
Click to collapse
I didn't get you wrong buddy. I have no problems with making a stock version, just didn't have time for that today.
Sent from my LG-P880
giantic hack
ohhh well the one big giantic hack is coming to our O4X! that`s very nice
thank you for this port and thank you for your fast work? tomorrow with stock and on saturday with android 4.3 ?
Donation sent
Whaaaaaattt?
Just were browsing N7 forum few days ago and saw MultiROM and thought "Ahh these lucky nexus guys, I wanna have it to! " and here we go hahahah
Sent from my OptimusX4HD using xda app-developers app
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Say Whut?
@Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Afro said:
Say Whut?
Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Click to expand...
Click to collapse
You can flash 10 different roms and play with them over your vacation. Thats what vacations are right?
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
JoinTheRealms said:
Donation sent
Click to expand...
Click to collapse
Thanks very much!
m.homauon said:
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Click to expand...
Click to collapse
You can't install to external SD. It could be modified to allow it, but there would be a huge performance decrease. Literally, roms would be lagging too much.
JoinTheRealms said:
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Click to expand...
Click to collapse
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Afro said:
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
Click to expand...
Click to collapse
Nah i couldnt get the twrp package to flash so im gonna try with fastboot. But the kernel works, i just swapped the ramdisk from Adam77roots patched kernel with iodak's stock kernel, it should work though
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Adam77Root said:
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Click to expand...
Click to collapse
My twrp failed to flash your twrp.zip package, most likely something on my end though, no one else has reported issues
Notice: Probably won't be keeping up with this much longer. CM has a slew of other commits, but I've only been including the two responsible for the discoloration...
Franco:
I've compiled franco's kernel with two cherrypicks from CM's github: c53fb6d134 and 07cbfb9a9c
These are required for recent nightlies of CM and its derivatives (caveat: if your rom specifically has commits reverted to not require such a workaround, then of course this isn't pertinent to you).
No changes to ramdisk or .config. Compiled using arm-linux-androideabi-4.7 from android ndk r9.
It should go without saying that you shouldn't flash this unless you understand what those commits are for and have a need for them. Those using the "colorfix" zip or otherwise reverting to an earlier liboverlay.so will find that method no longer "works" with newer builds (it spewed errors in dmesg nonstop when it worked).
IMPORTANT: Make sure you update to the new liboverlay.so if you're currently using the old one or you will have problems. Flash this on a rom that doesn't have the corresponding rom-side commits and you will of course have problems too (and I will laugh at you). As well, make sure to remove any addon.d script that you may have been using, if applicable. I don't know if there are multiple "colorfix" zips in circulation, but the one that I came across looks like it creates /system/addon.d/95-cm.sh. After deleting this file, you should be able upgrade/reflash the rom to bring liboverlay.so back up to date. Or if you're lazy/inept, wipe /system and reflash your rom+gapps.
Because of ramdisk customizations (incompatibilities) among roms/kernels, this zip will attempt to patch your existing ramdisk with franco's changes during flash. Things can obviously go wrong, so be ready.
4.4: 2013.11.29 1411ET: [franco-r195-cm-ziddey.zip]
4.4: 2013.11.25 0257ET: [franco-r194-cm-ziddey.zip]
4.3: 2013.10.26 2049ET r193: [JWR] [JSS/JLS]
-------------------------------------
Faux:
I built faux's kernel with the two commits as well.
4.4.1/4.4.2:
Faux: [030u-CM] [030m-CM]
4.4:
Faux: [029u-CM] [029m-CM]
4.3:
Faux: [028u-JSS] [028m-JSS] [028u-JWR] [028m-JWR]
Faux: [027u-JSS] [027m-JSS] [027u-JWR] [027m-JWR]
Note this is an "anykernel" and uses whatever the existing ramdisk is. If switching from Franco (or another kernel that includes a ramdisk), a "reset" kernel is recommended (reflash rom).
Built with arm-linux-androideabi-4.7, with bfd linker instead of gold.
Same as cm10_colorfix.zip?
Thanks alot! I will see if I can comment on any improvement in battery life or performance.
Sent from my Nexus 4 using Tapatalk
I don't think that these two patches will improve performance or battery life.
droidjam said:
I don't think that these two patches will improve performance or battery life.
Click to expand...
Click to collapse
But the use of incompatible library and the constant stream of errors caused by it may impact negatively on them.
Sent from my Nexus 4 using Tapatalk
Thanks alot for doing this.
Will be flashing this soon, all of @ziddey's mods have worked great!
Using this kernel for a while now. Working good if not better.
Thanks ziddey , for filling in such gaps whenever needed. That helps in keeping the ecosystem open to choices
Sent from my Nexus 4
Just flashed will test battery ect
Sent from my Nexus 4 using xda app-developers app
Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4
Thanks a lot, it works great! I hope you will keep this updated when Franco releases a new version.. I should definitely learn how to compile it by myself
Inviato dal mio Nexus 4 con Tapatalk 4
NUNsLAUGHTER92 said:
Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
link to kernel source for pac
ziddey said:
link to kernel source for pac
Click to expand...
Click to collapse
RoliSoft said:
According to this https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies dependency list, the complied kernel for mako is this: https://github.com/zyonee/android_kernel_google_msm
Click to expand...
Click to collapse
And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.
ziddey said:
And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.
Click to expand...
Click to collapse
I haven't been able to since I used the 10/9 nightly. If there haven't been any other changes then I don't know why it won't work. I wiped data before going to the nightly on the 16th and it would boot if I didn't flash a different kernel, but if I did then it'd stay on the boot animation forever. It does that for the 20th too, although I didn't wipe data before going to the nightly.
Sent from my Nexus 4 using Tapatalk 4
Thank you thank you thank you!
Stock camera wont start with this kernel for me on latest 2013-10-21 nightly for me.
Fine here. Referring to gallerygoogle and not gallery2
Sent from my phone. Please forgive typos and brevity.
build r192 is available on Franco's thread
http://forum.xda-developers.com/showpost.php?p=46663872&postcount=50533
Uh huh
Sent from my phone. Please forgive typos and brevity.
NEXT RELEASE: 27 AUGUST 2014 GMT+8 0900
With the introduction of so many kernels in the forums, every user just wants his/her phone to enjoy the crisp experience of their device. With ASKP, you get to enjoy the brilliant works of all developers into one small kernel. ASKP, is a modified kernel that merges many tweaks together, just like P.A.C.
ASKP is only run by me and pattyboi for now. Please bear with the slow speed of updates. I'm working on 3.4 for the Galaxy Nexus and also for you guys at the same time.
I promised before, ALL ROMS WILL BE SUPPORTED. But when I say ASKP is fully released. For now, I'll be releasing slowly. So please bear with me.
Supporting Devices:
LG G2
Samsung Galaxy Nexus
Variants of ASKP released for per-ROM basis statuses: http://forum.xda-developers.com/showpost.php?p=53569650&postcount=6
READ THIS FIRST
- There's always a name in each file right? The word at the end is the most important. And of course, make sure the model number is correct.
ONLY TWO WORDS ARE GIVEN FOR SIMPLICITY. STOCK and CAF.
- CAF kernels are for AOSP ROMs. A N/CAF (Non-CAF AOSP) Kernel will also be present upon full release of ASKP.
- ASKP has just started venturing into G2's development, please be patient if there is no support for your ROM yet.
- I am not responsible for any problems incurred on your device. This kernel is not fit to be a daily driver YET. Still in pre-alpha stage.
Changelog To Be Released after Alphas.
Downloads: http://forum.xda-developers.com/devdb/project/?id=4678#downloads
Savoca's Mirror: http://savoca.co/Amperific
Source: https://github.com/AmperificSuperKANG/G2-Kernel.git
Credits:
Everyone. From XDA.
As well as savoca for his awesome file transfer access to me.
Special Thanks to Dorimanx for the help in packing up the boot.img.
Based on: Dorimanx's Stock v20D Source. (Pulled from him as the internet connection I have is incapable of pushing a 1GB+ Source). This is a CLEAN LG Source.
I also want to thank him for his own build script, without it, I couldn't have built kernels as fast as before.
If you'd like to donate to me, Please do so, It'll be used for creating a tracker and an FTP site.
So you're buying yourself a beer. Heheh.
I really thank you!
Donors Hall of Fame:
- nope
XDA:DevDB Information
Amperific SuperKang Project, Kernel for the LG G2
Contributors
Amperific, Dorimanx, pattyboi
Kernel Special Features: Advanced Memory Hotplugging System
Version Information
Status: Testing
Created 2014-06-21
Last Updated 2014-06-21
XDA:DevDB Information
Amperific SuperKang Project, Kernel for the LG G2
Contributors
Amperific, Dorimanx, pattyboi
Kernel Special Features: Advanced Memory Hotplugging System
Version Information
Status: Alpha
Created 2014-06-21
Last Updated 2014-08-26
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
reas0n said:
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
Click to expand...
Click to collapse
I don't care. Like I said. I'm a welfare guy, EVERYONE GETS THEIR ASKP DESSERT.
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
reas0n said:
Nice! And the important advice for You right now: You REALLY SHOULD write which ROMs do You support and which G2 variants.
There are some ROMs based on dr87 sources like SlimKat, and Mahdi ROM itself, there is CarbonROM and PA which use other sources.
Aaand there is CM which didn't even get updated to KK sources, lol.
Click to expand...
Click to collapse
Amperific said:
I don't care. Like I said. I'm a welfare guy, EVERYONE GETS THEIR ASKP DESSERT.
Click to expand...
Click to collapse
NEO2598 said:
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
Click to expand...
Click to collapse
I think that this is for stock roms as its based on dori's sources.
Sent from my LG-D801 using Tapatalk
NEO2598 said:
For now, on wich ROMs will this work? I am a noob and don't know about sources and compatibilities...
Sent from my G2 running CloudyG3 on ART
Click to expand...
Click to collapse
You're using Cloudy's G3 eh. You're on luck. That's the first one.
Releases In order for Stock G2 and Ported G3 ROMs,
D802 (Released)
D800 (Released)
D801 (Released)
D803
VS980
LS980
After this,
Releases for All devices for Paranoid.
Then,
Releases for All devices for CM.
Also,
Releases for All devices under Mahdi's Sources.
Finally,
Releases for the next MOST requested ROM.
After this, expect features to fly in.
@nimrodsv Go ahead and ask him.
Guys, once again. THIS IS NOT A COPY OF DORIMANX.
I only copied his RAMDisk with his permission. Without it, I wouldn't be able to boot on the majority of ROMs.
The kernel source itself will be different from his indefinitely.
Wow, I am so lucky ☺
I will test it and let you know how is it. Thanks for replying.
Sent from my G2 running CloudyG3 on ART
Can't wait for the d800 PA release. Going to flip my ****.
Sent from my LG-D800 using XDA Premium 4 mobile app
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Sorry to say that, but for now it looks like the Dorimanx Kernel with other name
EDIT: not only STweaks. Governors, Hotplugs, etc, everything is the same, I think You should delete it for now. I think that STweaks can be used by everyone, but well, for now it looks like u copied his kernel and changed the name lol
reas0n said:
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Click to expand...
Click to collapse
Sigh. STweaks is from his ramdisk. And I'm reverting all his commits. by r5, Whatever I don't want won't be there.
Sent from my LG-D802 using Tapatalk
Please read up guides on what comes with a ramdisk and a zImage itself. A boot.img is made from a ramdisk and a zImage. Even though the STweaks app exists, it doesn't mean everything works. I don't have Intelli features inside. so use your eyes please. I'm trying to be kind and patient.
reas0n said:
@Amperific i flashed the kernel on CloudyG3 and I see that it has everything what @dorimanx kernel has... Also STweaks.
Sorry to say that, but for now it looks like the Dorimanx Kernel with other name
EDIT: not only STweaks. Governors, Hotplugs, etc, everything is the same, I think You should delete it for now. I think that STweaks can be used by everyone, but well, for now it looks like u copied his kernel and changed the name lol
Click to expand...
Click to collapse
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
YoungDaddy said:
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
Click to expand...
Click to collapse
Thank you.
But if you really don't appreciate my work, It's fine. I'll stop.
Not like I don't have other plans.
Anyways, Every development has its start. I admit. I have some dorimanx's commits. I'm reverting them currently till r5. Once we go past r5, I'll start working on pushing commits in.
If you see my development style in tuna, I do things part by part, in a systematic way.
YoungDaddy said:
Amp is a well known dev in the galaxy nexus forum (last that's where I know him and his work from) he's already stated he's using Dorimanx ram disk. So telling this guy to delete his thread is a **** move.
Sent from my LG-D800
Click to expand...
Click to collapse
You guys misunderstood me, meh. I didn't even say anything about the THREAD. It's the first one. The second one is, I just report to the dev what I see, I didn't say that it's a steal or anything, I just said that situation like that exists. Because i saw that there's everything like in dorimanx kernel, than maybe something went wrong with making the kernel.
Oh and about Intelli features, i see there are Intellidemand/Intelliactive govs, EcoMode, Intelli HotPlug, I REPORT it, REPORT, not ACCUSE.
Dang i hate misunderstandings. I appreciate every work and never want to make someone stop his work. Duh.
If dorimanx allowed to share everything with features he added like this now, then it's alright, I just reported in case he didn't allow it and You wouldn't see that or something.
So @Amperific keep going and sorry that u understood me wrong
Finally. We need more kernel devs. Thanks for joining the party!
Amperific said:
Thank you.
But if you really don't appreciate my work, It's fine. I'll stop.
Not like I don't have other plans.
Anyways, Every development has its start. I admit. I have some dorimanx's commits. I'm reverting them currently till r5. Once we go past r5, I'll start working on pushing commits in.
If you see my development style in tuna, I do things part by part, in a systematic way.
Click to expand...
Click to collapse
Keep on doing what you do bro. Can't wait to try some askp goodness on my d800 [emoji1]
Sent from my LG-D800
Sorry. Apologies from me too.
Next few builds,
- Mitigate commits that are not needed
- Bring in ASKP's tweaks
Sent from my LG-D802 using Tapatalk
Amperific, please don't stop your build. Coming from a gnex us users know your kernels are gold. I can't wait to try it out. I'm sure once non gnex users install the kernel they will see the magic. My request for you is a kernel that works with vanir on my d800. I'm a flashaholic so I jump from vanir, aicp, mahdi ect but just can't wait to try this bastard out??????
Sent from my LG-D800 using XDA Premium 4 mobile app
Guys before I sleep,
All Stock variants are up.
And I apologise about the CAF guide.
I briefly scanned through the source and realised that there are different variations of CAF. CMs, and etc. Even LG.
So all variations will be made available as well.
Nights
Do I need to go back on dalvik before flashing this kernel?
Currently i am on ART. If I stay on ART installation is the same? (wipe cache and dalvik then flash the kernel).
Thanks.
Sent from my G2 running CloudyG3 on ART
I was told that dalvik /ART is rom related not kernel
Sent from my VS980 4G using XDA Free mobile app
Featuring a new cpufreq interface, AbyssplugV2, intelliplug and a whole host of new additions that are not available in any other kernel for the x3.
Among them are updates only found in this kernel, saner defaults via config, better optimizations for the actual code and a rewritten version of devfreq.
It also have an updated baseband configuration and built in rather than to keep a module as it makes no sense to have a vital function as a module.
https://bitbucket.org/mourta/liquid_kernel_lge_p880-stable/
Kernel: http://www.mediafire.com/download/viy5a3dtaccd0gm/mourta-stable-08-23.zip
If there is a request for it i also have a ROM available based on grouper blobs, AD optimizations and a build around this kernel with a new dev tree.
For kernel install, it's anykernel, you can install it on any custom ROM, for stock and the lastest updates you will have to head over to Modaco and my original thread.
Note that this is a one time release, if you like it you'll have to head over to modaco to get updates.
it should be noted that the recommended settings is using intelliplug (you may need to use kernel tweaker or trickster mod for that if you're not running my ROM, and abyssplugv2, i also recommend ROW for a sheduler and Westwood for your congestion handling.
Note that you can now overclock to any frequency and it will feed the GPU chip with the needed volatage, this is great for cooking a roast beef but not for any practical use.
Quadrant scores are 8k and the last Antutu was at 16487, no overclocking but you won't reach that without using my ROM.
And with that... i'm done.
Thanks to the IODAK, Fransico, Adam77Root, Faux123 and others that provided code and/or input.
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
peppethustra said:
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
Click to expand...
Click to collapse
We'll see how this goes.
Thankfully i am in touch with a mod that will keep this drama free,
And for anyone wondering, peppethustra is head of my testing crew, you get stable releases because of them.
It should be noted that i'm still going to prefer the forum that greeted me over the one that shunned me from the get go, updates here will be sporadic at best but on time on the other forum.
It's great to see your work on XDA.Now everyone can experience your awesome work
P.S. you can find neccessary links in my signature
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
FunkyRasta said:
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
Click to expand...
Click to collapse
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
peppethustra said:
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
Click to expand...
Click to collapse
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
FunkyRasta said:
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
Click to expand...
Click to collapse
Outdated sources never are a good base for developing a fresh new kernel or ROM, if there is a new compatible code implementation ready to be merged into the code That's the first thing a good developer checks (and if you can, look at Mourta's bitbucket linked in the OP to view his commits, there will be all the principal news about new code implementations)
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
baxtex said:
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
Click to expand...
Click to collapse
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Okay will do.
How's the deep sleep ?
Written from my Optimus 4X powered by Omni 4.4
LGaljo said:
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Click to expand...
Click to collapse
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
peter_altherr said:
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
Click to expand...
Click to collapse
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
ottomanhero said:
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
Click to expand...
Click to collapse
+1
@peter_altherr And more important thing: have you at least wiped cache and dalvik before flashing the kernel? If yes, try wiping system partition too (no factory reset, you can leave /data partiton intact) then reflash ROM, gapps and kernel, and see how it goes..wait 3 or 4 minutes before trying to wake up device, after the first boot, and deep sleep would start without problems
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
baxtex said:
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
Click to expand...
Click to collapse
Wait for next version, great changes will come even about this issue
@peter_altherr you should unplug it from charger and try unplugged.
when charging cpu never reaching deepsleep.
@ whoever had freeze/sod problems with last kernel version: a new fixed release has been uploaded (it's a minor release: reverted GPU OC, which was causing the problem). Check official thread for the download link
my phone does not see SD card with 0902
and yes im 100% sure its kernel problem....recovery sees my sd, and so iodak kernel