Database Users

[ROM] UNOFFICIAL AOKP nightly builds

UNOFFICIAL AOKP Nightly Builds​
Since AOKP development has started picking up with their addition of their new Gerrit server, I've decided to release nightly builds for AOKP. These should be released every day anywhere from 6-9pm depending on when I get time to do it. Also, some days I might not get the time. However, it should be almost every day that a new build comes out.
All credits go toward the entire AOKP team for their efforts in making one of the most customizable builds out there right now. It is absolutely fantastic.
You can download it by sorting by date uploaded right here on my goo.im profile:
http://goo.im/devs/rohan/tenderloin/aokp_nightlies
Note: These downloads are provided untested. This might break your system so be sure to keep a backup handy. Nightly builds are usually more unstable than any other type of ROM, but if you want the latest features then use this. I do not take responsibility for anything that may happen to your system.
Another note: These downloads do not come with any sort of support. Do not ask for help in IRC for aokp if you are running these nightlies. They are not official and thus are not officially supported. So don't go and give roman and the other devs a headache
And another note: They don't come with gapps, download those separately from goo.im or some other source.
You should just be able to download and install the zip in CWM, then wipe caches. Reboot and enjoy. No other wiping is needed, only caches.
Right now I am building on my personal PC (I don't have a server) so I apologize if it takes a while to get builds up! My system isn't the fastest at making builds haha
I will be making these ROMs updateable via the goo.im app probably this weekend, I don't have much time right now to figure out how it works.
If you want to find out when I release the new nightly, follow me on twitter: http://twitter.com/rohanXm

Looking forward to it!

Is there a changelog like the CM nightlies?

What exactly is aokp?

Ventus_zx said:
What exactly is aokp?
Click to expand...
Click to collapse
http://knowmydroid.com/blog/what-is-aokp-rom-how-is-it-different-from-cm9

AOKP is pretty awesome. I run it on my Epic 4G and I agree it's more customizeable than CM9 and pretty solid in terms of reliability . Thanks for these Touchpad Nightlies Rohan! Installing it as we speak!

Nburnes said:
Is there a changelog like the CM nightlies?
Click to expand...
Click to collapse
You can find what was merged here:
http://gerrit.sudoservers.com:8080/#/q/status:merged,n,z
It will display some other device stuff, though most AOKP stuff from that gerrit is for the entire AOKP as a whole and not device specific.

Can I flash the cm nightly 120 dpi patch or will it break things?

rsalinas1 said:
Can I flash the cm nightly 120 dpi patch or will it break things?
Click to expand...
Click to collapse
The only "side effect" is that you cannot access the Trebuchet settings and your build.prop values will be different leading to some funky and wrong info in your About Tablet area of your settings.

rohan32 said:
The only "side effect" is that you cannot access the Trebuchet settings and your build.prop values will be different leading to some funky and wrong info in your About Tablet area of your settings.
Click to expand...
Click to collapse
I just changed it under general ui with rom control settings. Thanks though, its very smooth so far.

Anybody else get a System UI has closed error. Weird, hopefully it was a one time thing. Flashing the 4/20 now. Hopefully that fixes it, I did a full wipe and will wipe again
Sent from my aokp_tenderloin using XDA

SUPREME Mods v1.5
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel

BIGSimon said:
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
Click to expand...
Click to collapse
I would assume that the nighties don't use either of those things.

Nabobalis said:
I would assume that the nighties don't use either of those things.
Click to expand...
Click to collapse
OK thanks, just asked as both are by rohan32, will try with and without to see if any difference.

BIGSimon said:
Do I need to apply the SUPREME Mods v1.5 after flashing your rom or are they already applied also are you using your XENON kernel
Click to expand...
Click to collapse
Yup you need to reflash the Package and nope its the default Cyanogenmod Kernel.
This build is 100% AOKP "stock", as in its simply compiled from source with no changes.

rohan32 said:
Yup you need to reflash the Package and nope its the default Cyanogenmod Kernel.
This build is 100% AOKP "stock", as in its simply compiled from source with no changes.
Click to expand...
Click to collapse
The Supreme mods work fine but the xenon kernel broke my wifi (not had any wifi issues on any build) so back to cyanogen kernel and everything is working

The latest nightly (5/07) fixed my screen off/sound bug. All previous builds of AOKP had a muffled or distorted sound bug that appeared once I dimmed the screen while playing music. Bravo! I believe the fix came from the Classicnerd team, who once again prove they are contributing in remarkable ways. Bravo to them as well!

is this wifi driver included in the nightlys?
http://review.cyanogenmod.com/#/c/15570/

matteebee said:
The latest nightly (5/07) fixed my screen off/sound bug. All previous builds of AOKP had a muffled or distorted sound bug that appeared once I dimmed the screen while playing music. Bravo! I believe the fix came from the Classicnerd team, who once again prove they are contributing in remarkable ways. Bravo to them as well!
Click to expand...
Click to collapse
I tried both the 05/07 and 05/08 AOKP nightlies and the screen off/sound bug is still there just like any other ROM I have tried. Are you sure that you have the volume turned up enough?

can has new build?

[ROM] [FIND5] [4.2.2] [cfX-Toolchain 4.8.y+] codefireXperiment

This new Android distribution treats development differently than any other.
CLICK HERE FOR THE ROM, THREAD, CHANGELOG, AND DISCUSSION.
A post detailing our team and new developers from TeamEOS can be found in the OP linked.
ntroducing codefireXperiment for your device! This OP is going to stay slim and bloat free, just like codefireXperiment. No marketing buzzwords either. We take such confidence in the speed and performance of this distribution, we challenge you to find a faster and more stable one!
Here's a bit of info you may want on this project for how we do things differently:
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Enjoy, and thank you for choosing codefireXperiment
XDA:DevDB Information
[ROM] [AOSP] [4.2.2] [cfX-Toolchain 4.8.y+] codefireXperiment, ROM for the Oppo Find 5
Contributors
anders3408
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: JDQ39E-20130
Stable Release Date: 2013-08-11
Created 2013-09-04
Last Updated 2014-08-18

Nice team you assembled there, looking forward to trying it out. openpdroid patches failed for me, oh well, gotta get more experience with xprivacy anyway.
BTW, didn't see it on your site so far, featurelist somewhere(espacially in terms of the kernel in use)?

any screenshot

S.D.Richards said:
BTW, didn't see it on your site so far, featurelist somewhere(espacially in terms of the kernel in use)?
Click to expand...
Click to collapse
look at the Github link to the kernel source
Sent from my HTC One X+ using xda app-developers app

maxwen said:
look at the Github link to the kernel source
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
https://github.com/codefireXperimen.../arch/arm/configs/cyanogenmod_find5_defconfig
Hard looking through that looking for pieces if you don't know the specific CONFIG_xxx name.
Anyway, in a quick scroll through, I fell over some enabled (=y) USB OTG stuff - I was under the impression the device doesn't support it?

Nightly is blazing fast. Quickest boot times ever. Even the first boot was super fast.
Sent from my Find 5 using xda app-developers app

Sorry to ask, I probably missed it somewhere... is this AOSP based, or other? Max's kernel is going on this bad boy if I try it... unless... it's already in there

no idea what this is, but i will flash it and take a look

Pure aosp based. For now not as many features as the other codefirex, but things are being added. Kernel is cm based with a few changes from maxwen and faux123, thanks both. Credits thread will come up.
Sent from my Find 5 using XDA Premium HD app

charlatan01 said:
Sorry to ask, I probably missed it somewhere... is this AOSP based, or other? Max's kernel is going on this bad boy if I try it... unless... it's already in there
Click to expand...
Click to collapse
Not tested maxwen kernel on it but you should be ready to reflash then, not totally sure it will work. Early tests did bootloop on maxwen kernels.
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
Not tested maxwen kernel on it but you should be ready to reflash then, not totally sure it will work. Early tests did bootloop on maxwen kernels.
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks... I will hold off on flashing his kernel for the time being. It would be nice to get that working if possible.

charlatan01 said:
Thanks... I will hold off on flashing his kernel for the time being. It would be nice to get that working if possible.
Click to expand...
Click to collapse
Just tested, you should be able to boot maxwen kernel on cfxe, at least it does with cfxe ramdisk
test it out and tell how it wents

I do have some random reboots after +-10 minutes with this ROM. Can I provide you a logcat Anders?

anders3408 said:
Just tested, you should be able to boot maxwen kernel on cfxe, at least it does with cfxe ramdisk
test it out and tell how it wents
Click to expand...
Click to collapse
need to take a look at your ramdisk
if something special is required I can provide prebuilts with your ramdisk
Sent from my Find 5 using xda app-developers app

mavaee said:
I do have some random reboots after +-10 minutes with this ROM. Can I provide you a logcat Anders?
Click to expand...
Click to collapse
are you on the default kernel in this rom , and did a full wipe ?
Sure you can make a logcat , paste it via here
you can also submit a bug : here but please add log also
have not had a single random reboot at all, so its a bit wierd

anders3408 said:
are you on the default kernel in this rom , and did a full wipe ?
Sure you can make a logcat , paste it via here
you can also submit a bug : here but please add log also
have not had a single random reboot at all, so its a bit wierd
Click to expand...
Click to collapse
Yes I used the default kernel and coming from CM10.1 with a full wipe. I have to say I didn't experienced a reboot after all this afternoon so maybe it was just the ROM settling down.
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
Logcat:
http://logcat.scheffsblend.com/view?id=285002

mavaee said:
Yes I used the default kernel and coming from CM10.1 with a full wipe. I have to say I didn't experienced a reboot after all this afternoon so maybe it was just the ROM settling down.
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
Logcat:
http://logcat.scheffsblend.com/view?id=285002
Click to expand...
Click to collapse
What happens when you made that logcat? I'm not seeing any reboots? Hopefully you won't see such reboot again.
Sent from my Find 5 using XDA Premium HD app

Nice ROM.
Voice to text isn't functioning... I was going to try the app install from the Slim ROM site, but I know that doesn't work with the CM kernel. I know it works with Max's.
Anyway, other than that it's been stable for me. Wifi tethering worked, Battery seemed good for only running it 24 hrs or so.

charlatan01 said:
Nice ROM.
Voice to text isn't functioning... I was going to try the app install from the Slim ROM site, but I know that doesn't work with the CM kernel. I know it works with Max's.
Anyway, other than that it's been stable for me. Wifi tethering worked, Battery seemed good for only running it 24 hrs or so.
Click to expand...
Click to collapse
Its also using the CM's kernel. Can you send me a link to that app and I'll have a look.
Sent from my Find 5 using XDA Premium HD app

^ sure thing. Src install is found (thanks to the folks at Slim!) here

[Q] Building OmniRom from resources for i9100

OK, so I am not a dev.
And iam completely newbie
I saw some people saying that if you have aosp on your device it's much easier to port omnirom for your device
So can I use CyanogenMod 10.2 that is available for the i9100
To build omni
And is there any detailed instruction on how to build it !!
Sent from my GT-I9100 using Tapatalk 4

I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app

filllob said:
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.

Entropy512 said:
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Click to expand...
Click to collapse
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?

chasmodo said:
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
Click to expand...
Click to collapse
No, because it could still cause damage if flashing from an old "unsafe" kernel (see the first few CM10 builds as an example...). These are far rarer now than they used to be, but there are, believe it or not, occasionally people who are flashing stuff starting from TW ICS.
And CWM has tentacles throughout the CM source tree to get it to build. It requires too many hacks in too many places. TWRP is more standalone, the limitation being that on devices with standalone recovery, Dees_Troy always built using the "eng" variant instead of "userdebug".
There's a patch that allows for TWRP to build properly on userdebug using "make recoveryimage" but it fails to allow building of TWRP into unified-recovery devices like Sony pollux_windy/yuga. (Samsung requires even more hacks...)
Even the Sonys which are "sort of" working aren't ready for builds yet - for them to work they're dependent on the FOTAKernel trick Dees_Troy developed to allow for alternate recoveries to be put on a device.

Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.

aidfarh said:
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
Click to expand...
Click to collapse
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.

Entropy512 said:
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Click to expand...
Click to collapse
Is there anything I can do to help? Maybe if I can make it work on my device?

So the I9000 got a build of OmniRom, I thought it has also a unified kernel !!!

I was searching on Google today
and I suddenly found this
http://forum.xda-developers.com/showthread.php?t=2494127
that's an alpha build for I9100
it's using the CM10 kernel and it uses CWM not TWRP
Iam testing it right now

Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...

Entropy512 said:
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Click to expand...
Click to collapse
I built it for Note already
http://forum.xda-developers.com/showthread.php?t=2495930
Sent from my GT-N7000 using Tapatalk

Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I

AA1973 said:
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
Click to expand...
Click to collapse
Yeah I know. Entropy and me are looking for the error, but is not beeing easy to fix. Okey, will add in a few hours and release new one. And I correct you, except the latest version, I tried all versions I released and some others I didn't release. I always do but that day I needed phone for important family things and couldn't test
Also I went to release with a prebuilt TWRP 3.0.101 kernel but XplodWilD say me that this will get Semi-Official maybe, and only compiled non-touched ROMs will be released.
Sent from my GT-N7000 using Tapatalk

@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app

filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Click to expand...
Click to collapse
n7000 bringup would be easier, methinks.

filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ask some DEV to try and see if works
Enviado desde mi GT-N7000 mediante Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
chasmodo said:
n7000 bringup would be easier, methinks.
Click to expand...
Click to collapse
N7000 is gonna be up as soon as XplodWild get free and merge it and change something I said him. Idk why my Gerrit is not working. I am gonna install Ubunt 13.10 for clean and will set up all again for try if I can get Gerrit working again
Enviado desde mi GT-N7000 mediante Tapatalk

I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app

filllob said:
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If is legit what? I cannot understand you, sorry. You want to try, to compile...?

i am a noob to compiling etc, only followed cm instructions.
I want to know if the changes in the commit I mentioned can be applied to i9100 too, obviously with some adjustments, and if there is something more to do to compile omni for i9100
I hope I explained myself right( English is not my language)
Sent from my GT-I9100 using xda app-developers app

Contacting CM to update sources to KK

Hello friends.
As all of us see, LG released their KitKat sources long time ago. Our great developers like @dr87 @Savoca @houstonn and others made it with Their hard work to merge them so we have two stable / nearly stable roms: Mahdi and PA. But what with other roms? Most of the roms are based on CM, so they still have bugs.. During months, CM doesn't seem to have done ANYTHING.
So my question is, how about to send a message (or spam, in any way u name it) by all of us to CM, to the maintainer? We have official support, but in fact it's "support without support" in my opinion. Maybe after these messages they would finally start to do something, because it's like they forgot about G2...
Regards.
EDIT: so we have a way to contact => https://jira.cyanogenmod.org/secure/Dashboard.jspa
now we should make a well, polite message so everyone would copy it and drop there.
Another way it would be to ask the maintainer directly https://plus.google.com/+RicardoCerqueira
EDIT2: I gave a comment to Ricardo on Google+ here https://plus.google.com/+RicardoCerqueira/posts/4dc8kVBYuTq feel free to do it as well

The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.

I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Inviato dal mio LG-D802 utilizzando Tapatalk

Airidas said:
The best bet would be to create an improvement note at their so called "Bug Tracker" considering that they are doing this for free, this would be the most polite form.
Click to expand...
Click to collapse
could u give a link please? so we could prepare a message and then everyone would leave it there
vittogn said:
I support this initiative, but today be entirely honest M6 for me is almost bug free, fast and battery efficient.
Up to date sources is great, but if a rom is working well, I don't care if the sources are old!
Click to expand...
Click to collapse
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.

reas0n said:
could u give a link please? so we could prepare a message and then everyone would leave it there
I personally had CM for some time, and it never was so stable as Mahdi R1 which i have now. Besides that, a lot of roms like Carbon or Slim can't be simply updated from CM sources, so they still have bugs.
Click to expand...
Click to collapse
Here: jira.cyanogenmod.org

Thanks, so anyone is, i would say, good in kind speaking to prepare a message?
Oh and we could also use Google+ and ask the maintainer directly https://plus.google.com/+RicardoCerqueira

Replyed 2 times to posts in his google + account with message " When LG G2 is going to have updated KK sources? A lot of people are waiting for bug-free CM and CM-based 4.4 ROMs ". I hope that all you guys do the same.Cheers
Sent from my LG-D802 using XDA Premium 4 mobile app

Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:

dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
apparently theres a bit of confusion, there was some one nightly where the rotation wasnt working with the jb baseband, (im gussing on that nightly he used the kk source ) because flashing the kk baseband on that build fixed the rotation issue, but im not quiet aware of what the situation is ince im back on stock. anyways ill be swinging it on the latest nightly just to clarify my doubts. and im pretty sure they just want the maintainer to switch to kk source , btw nice to see you here hope your cooking something great for us

dr87 said:
Just to clarify, roms that are based on CM do not need CM to upgrade to 4.4.2 sources. The upgrade is done in the device tree / vendor files and kernel. The rom source does not need any changes and each rom maintainer for the G2 has the power to upgrade their rom to 4.4.2 G2 sources without CM doing anything, they just need to figure out the specific device tree bugs for each rom and fix them.
I am under the impression you think CM needs to upgrade in order for CM based roms to upgrade, feel free to correct me if I'm wrong :good:
Click to expand...
Click to collapse
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.

reas0n said:
Well, in the past I had some Android phones, and CyanogenMod was always first with upgrading everything, and then other developers were basing their ROMs on these updates. I mean, they updated everything, end other ROMs were updated fast. They're not giving support which they were giving in the past, that's all.
Click to expand...
Click to collapse
Did you get a response from Ricardo?

LenAsh said:
Did you get a response from Ricardo?
Click to expand...
Click to collapse
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..

reas0n said:
Nope, i saw i got some 1+ on my comment, i shared second comment today. nothing..
Click to expand...
Click to collapse
Oh

[KERNEL] Bacon Official Kernel source

The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.

Oh Gr8 news ! Hope we could get custom kernel on OPO soon
Sent from my One using XDA Premium 4 mobile app

I am hoping we get one soon also.
Sent from my One using Tapatalk

SferaDev said:
The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.
Click to expand...
Click to collapse
Mind putting together the flashable zip of the stock kernel so that users who go custom kernel flashing (Franco for now) can fall back to the stock kernel?

A flashable .zip would be great

@SferaDev Thanks for this, I will be using this to build a kernel for our devices

Gamma control is out:
0f98e789af8c12ce3687cbe4515b429aa1e031a3 video: mdss: Add predefined gamma selection

I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?

DrDaxxy said:
I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?
Click to expand...
Click to collapse
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...

SferaDev said:
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...
Click to expand...
Click to collapse
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?

DrDaxxy said:
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?
Click to expand...
Click to collapse
I haven't faced ANY kernel that doesn't work...

A flashable zip will be great! Can any expert help on this?