[UNOFFICIAL] CM-compatible franco/faux kernels - Nexus 4 Android Development

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.

Related

[KERNEL] {ADA} *NEW AOSP* v3.0.51 ZenSERIES v2 *BreakingGround* {Jelly Bean} [KERNEL]

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.

[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

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.

[KERNEL] Amperific SuperKang Project | r3 | 3.4.0 | [27-8-2014]

​
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

Mahdi-Rom Unofficial/Un-maintained builds

Alright folks.
As users of Mahdi-Rom have noticed, Dr87 has been awhile on updates. From reading people say he's stated that he's ceased development for the G2 until Android L drops. Given that, I've began working on my on builds of this rom as well as major modfiications to his base kernel based on Dorimanx's Stock kernel. I had tried Bart452's and the audio patch never worked quite right in all apps. It's also lacking hardware acceleration for video on this rom for some reason.
ALL FILES POSTED HERE ARE "AS-IS". THEY SHOULD ALL BE CONSIDERED EXPERIMENTAL.
I don't plan on providing support, adding devices, changing features. These will simply be builds of the ROM based off of a repo sync ... Nothing more, Nothing Less. These are being made based on the Mahdi 4.4.3-CAF repo source. This may or may not be the correct one, but it boots and seems to work on my device. This then gets the sources from Dr87's upgrade guide added in. lunched as VS980 (my device) and the OTApackage made.
If anyone has any tips/recommendations for better places to pull the source from (if there's a more appropriate one).... OR if there a better place to pull individual portions of the ROM from in the manifest, I'm all ears.
As far as my kernel modifications, I'll just be calling it "SimpleKernel+". I may end up talking to Dorimanx to get his blessing to keep the name, as I don't want to steal his credit or work, but also don't want to cause confusion either. This may take some time to start releasing builds of. For the time being, I've just mass-reverted some of one of Bart452's old ports of Dorimanx's kernel. I would only release for the VS980, as thats my device. But it's pretty quick to build for the others and repack them.
I don't want to sound rude or anything like that. But for the people that don't bother reading... I'm not a dev, I'm not maintaining this, I'm not coding for it. So posting feature requests and such will most likely go ignored.
I'm syncing sources and building. For the kernel, I'm picking commits and building. Most all commits to the kernel will probably come from Dorimanx's repo. I just don't feel right keeping the name when I'm not taking *all* his commits, as I'm going to avoid things for sound and video.
All coding has been done by Dr87 and Dorimanx and all the people they thank in their threads.
Links:
Rom:
a18dbeadb32b0e398116de5f5571af20 mahdi_vs980-20OCT2014.zip
Kernels: Github for this Dori Port
307cbb08c7c4f4a733b3223d38280546 Dorimanx-v7.8-d800-kernel-Nexus_Sound.zip
09e66f4ee8f27b14bc818dae6f957696 Dorimanx-v7.8-d801-kernel-Nexus_Sound.zip
434eeaee1ea4a040d6f3fbff0fcf7d71 Dorimanx-v7.8-d802-kernel-Nexus_Sound.zip
a89518e7eae55bc1285e628f0b93f3b7 Dorimanx-v7.8-d803-kernel-Nexus_Sound.zip
3a798dfdff9d916c07b256edc587c629 Dorimanx-v7.8-ls980-kernel-Nexus_Sound.zip
32e8b3e929104741cd5589dcea4e68d0 Dorimanx-v7.8-vs980-kernel-Nexus_Sound.zip
Also, for anyone curious. This should work with fauxsound as it has his mods in it, the STweaks app that's included actually has a volume boost bit in it. Also, cf.Lumen 2.40 *will* work with this rom/kernel combo. You just need to prevent it from updating, as newer version do not work with it.
Known issues :
Kernel Video playback doesn't use hardware modes. This prevents using Netflix. I'll investigate into this.
Some proximity issues.
*saved*
Awesome going to try this out
Sent from my LG-D800 using Tapatalk
Well, this is exciting!
Sent from my LG-VS980 using Tapatalk 2
why does the ROM .zip name include vs980? we download that one appropriate kernel?
MarioMoPho said:
why does the ROM .zip name include vs980? we download that one appropriate kernel?
Click to expand...
Click to collapse
Sorry, I left it out of the op..
You NEED to flash the associated patch still from the official thread.
I build these for my device, hence the name. I only share them because, why not....
Sent from my LG-VS980 using XDA Free mobile app
Yoinx said:
Sorry, I left it out of the op..
You NEED to flash the associated patch still from the official thread.
I build these for my device, hence the name. I only share them because, why not....
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Been running on d803 flawlessly since you first posted it, even dirty flashed over d87s last build. Thanks for putting out builds while Dr seems fairly busy which I fully understand as I built and maintained on the i717 for 2 years.
Yoinx said:
*saved*
Click to expand...
Click to collapse
Same here, going to try this one!
Thanks.
For some odd reason I couldn't get 4g data to connect for the vs980 ...maybe bad download idk...I did full wipe and flashed 2 separate times and no go either time...anyone else have the same issue?
Nugg14 said:
For some odd reason I couldn't get 4g data to connect for the vs980 ...maybe bad download idk...I did full wipe and flashed 2 separate times and no go either time...anyone else have the same issue?
Click to expand...
Click to collapse
Did you flush dr87's patch from his thread? That step is still required.
Works on my vs980 but I know someone else reported similar
Sent from my LG-VS980 using XDA Free mobile app
Yoinx said:
Did you flush dr87's patch from his thread? That step is still required.
Works on my vs980 but I know someone else reported similar
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
I did not...Duh....LOL Thanks again
Thanks for this. I havent been on AOSP for a while since Mahdi wasnt getting updated. You rock!!!
Great, THX! On Ls980 until all well.
Has DSB been merged?
Commits:-
Change I3bc7102b: https://gerrit.paranoidandroid.co/4787
Change Id2b105df: https://gerrit.paranoidandroid.co/4788
varund7726 said:
Has DSB been merged?
Commits:-
Change I3bc7102b: https://gerrit.paranoidandroid.co/4787
Change Id2b105df: https://gerrit.paranoidandroid.co/4788
Click to expand...
Click to collapse
Does the official mahdi thread state it has been?
Lawlrus said:
Does the official mahdi thread state it has been?
Click to expand...
Click to collapse
Nope.but these are the unofficial builds so im guessing they will be merged soon
varund7726 said:
Nope.but these are the unofficial builds so im guessing they will be merged soon
Click to expand...
Click to collapse
Why would they? Per my op, I'm only syncing Mahdi repos and building with no modifications. They're unofficial because they agent built by Mahdi. They're unmaintained because I'm not going fixes, changes, or anything of the like. These are only up for people that don't build themselves.
Sent from my LG-VS980 using XDA Free mobile app
Seems 720p YouTube doesn't work for me. Anyone else? Or is this the same as the Netflix issue?
Yoinx said:
Why would they? Per my op, I'm only syncing Mahdi repos and building with no modifications. They're unofficial because they agent built by Mahdi. They're unmaintained because I'm not going fixes, changes, or anything of the like. These are only up for people that don't build themselves.
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Wait a minute, YOU EXPECT PEOPLE TO READ THE OP? SHAME ON YOU..... THATS PREPOSTEROUS!
/sarcasm
Ok, so after spending the last 4 or 5 days trying to shoe-horn Dorimanx's commits in on Dr87's base... through picks, rebases, reverts... etc... I gave up.
What this means, is that I'm abandoning trying to port his kernel to aosp. What I'll be doing is picking various things to improve the kernel, largely from faux123 on nexus5. This should give us a lot of benefit, with minimal issues. I'll also likely pull the nexus tree for mahdi, which i'd bet is what dr87 was building off of... given the similarity in the devices...

Categories

Resources