Database Develop

[ROM] ProTekk CM7 Builds - Build #19 Is Live! Thunderbolt Builds Are Live!

Requirements:
Build #8 and higher: Clockworkmod Recovery 3.0.0.7 or higher is REQUIRED!
You don't have 3.0.0.7 or higher installed I cannot help you out with any issues as these scripts do not play nicely with anything earlier than 3.0.0.7!
You have been warned!
How To Install:
Coming from another ROM or doing a clean install:
Step 1: NANDroid first!
Step 2: Do a full wipe! This means format everything!
Step 3: Flash desired build, wait for install to finish and reboot
Step 4: Enjoy!
Upgrading from nightly #X or ProTekk build #Y using build #8 or higher:
Step 1: NANDroid first!
Step 2: Flash desired build, Dalvik and cache will be wiped automatically!
Step 3: Enjoy!
Google Applications (GApps):
http://goo-inside.me/gapps/
CyanogenMod changelog & merges:
http://review.cyanogenmod.com/#q,status:merged,n,z
Stock Build Download Locations:
http://www.mediafire.com/cm7/inc
Experimental Build Download Locations: Abandoned for now until I have more time/help
http://www.mediafire.com/?8z38p1pgyag72
Experimental Builds With Custom Kernels:
Included kernels:
Incredikernel from 03/06/11
Invisiblek from 03/09/11
SavagedZen no SBC
Tiamat from 03/05/11
Please remember that they are experimental!
With these, ALWAYS wipe Dalvik and cache! No longer needed as it is auto wiped - Build #8 and higher!
Updates:
Experimental builds #8 & stock #8 released @ 00:14 AM EST 03/12/11
Experimental builds #7 & stock #7 released @ 7:30 AM EST 03/11/11
Experimental builds #6 released @ 1:05 PM EST 03/10/11
Experimental Build #5 With Custom Kernels released @ 1:33 PM EST 03/09/11
Build #5 released @ 10:12 AM EST 03/09/11
Build #4 released @ 2:50 PM EST 03/08/11
Build #3 released @ 9 AM EST 03/08/11
Build #2 released 03/06/11
Build #1 released 03/06/11
To-Do List:
Automatically wipe Dalvik and cache prior to installing. Abandoned for the moment. Working properly!
Credits:
CyanogenMod Team for the incredible ROM they've given us
Slayher for many many many fixes and guiding me here and there! Thanks!
Calkulin for his format script - Thank you!!!!!
NilsP for helping me out with the format script
Chad, Invisiblek, SavagedZen team, and Cayniarb for your amazing kernels
If I have forgotten anyone I'm sorry! Let me know and I'll give you credit!

Q: What is this?
A: This is something I have started doing since the buildbot has been on hiatus and I needed to feed my addiction to flashing the most recent build of CyanogenMod 7 I could get my hands on.
I started doing this for myself and saw that there was a pretty big demand for the newest updates possible so I said why not share it with everyone.
Nothing in my builds have been altered so don't worry. It is not a ROM I have customized. All I am simply doing is pulling the source every morning and compiling it.
Q: Wait, so this is the same as the CyanogenMod 7 nightly builds? Why rename it and make it?
A: Great question. Think about it this way. The CyanogenMod team builds nightly right? Well, lately it hasn't been nightly but more random. The advantage of building daily, for me and the people on the east coast, it is much better to have a new build readily available in the morning versus waiting all night for a release or no release at all and wasting time. I am not taking credit for the CyanogenMod team's work and I refuse to as I am simply pulling the source and compiling it. The renaming of my builds is to defer the confusion between the CyanogenMod nightly builds as my builds have nothing to do with how CyanogenMod builds and releases.
Q: Ok, so if I am having issue X,Y,Z who do I report it to?
A: If it is a known issue please post it in the RC 1.5 thread. If it is an issue that is not known and has started with one of my builds please report it here via a post or a PM and I will be more than happy to help out and see if I can fix it.
Q: Uh, if there are nightlies then why would I want to use your builds? Doesn't it make sense to use one of the nightlies?
A: Sure, you are more than free to use one of the official CyanogenMod nightlies! The reason why some use my builds is simply the fact that they want to have the newest updates and merges on their device! The buildbot does not always pump out a new nightly where as I always will be building and compiling every day. Also, the nightlies don't always include the newest merges because of the fact that merges can be push at any time.
Q: If you are building these daily what happens if updates are merged after you build?
A: Haha, I know this is sad but I don't have much of a life but I do have one! I keep on top of all the merges almost like clockwork! I normally check about every hour to see if there are any major updates and fixes. If a major fix is merged I will be pushing out another build as soon as I see that it has been merged! So no need to worry about having the newest build besides downloading it and installing it.
Q: Ok, so nightly #X is released, wouldn't it be the same as your build #Y?
A: This is a little harder to answer but I will make it simple. As I said before and as many have noticed, the buildbot doesn't always push a new build. For example, my builds #1 and #2 are the same as nightly #13. RC 2 and nightly #14 were released and both are just about the same from CyanogenMod. My build #3 includes the new merges after both of those have been built so mine would be newer. I will be working on a log that tracks the differences between the nightlies and my builds shortly.
Q: What's the deal with the kernels? Why are there the same number build but different names?
A: I have noticed that everyone has their own "go-to kernel" after they flash a ROM. I have collected the top 4 gingerbread kernels used and incorporated them into each build I do. There is the stock build which is nothing different than what the CyanogeMod team puts out, Incredikernel, Invisiblek, Tiamat, and SalvagedZen. You can choose whatever one you want to use. The purpose of this is to simplify the install process for the user so that there is no need to be flashing multiple zips just because you're updating to the newest build.
Q: I can't get CWM 3.0.0.x to update on my phone. I don't know what I'm doing wrong. Every time I go to recovery, it says i'm running 3.0.0.x
A: ROM Manager > Menu > Settings > Erase Recovery > Back > All ClockworkMod Recoveries > select 3.0.0.7 or higher
Any other questions? Please let me know and I will include them in this post!
------------------------------------------------------------------------------------------
I personally test out each build as I release them and if there is one posing serious issues I will pull it from my site!
I have successfully used the stock kernel, incredikernel, and Tiamat on my builds without issues.
All my builds will be online and ready to download no later than 10 AM eastern time! I try to get them out as quick as possible for you guys!
As a sidenote and fore more clarification, I am NOT taking credit for the fabulous work that the CyanogenMod team is doing! This is NOT a custom ROM I have edited or made! This is always going to be straight from the CyanogenMod team's source!
I will be doing this past RC 2 and if CyanogenMod 7 gets release as a stable build and solidified I will be building as long as there are updates merged!
Please enjoy it and happy crackflashing to all!

This is great, now I don't have to scroll through the other thread for your builds, thanks Protekk
Sent from my ADR6300 using XDA App

nerogold said:
This is great, now I don't have to scroll through the other thread for your builds, thanks Protekk
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not a problem! I aim to please!

So what are the "fixes" you mentioned in the other thread that you merged at 9AM? I am doing a fresh install of RC2 because I have been wanting to use one of these themes since RC1, but he doesn't update it for nightlys...
If the fixes aren't anything huge then I will try to stick with RC2 for atleast half a day

GatorsUF said:
So what are the "fixes" you mentioned in the other thread that you merged at 9AM? I am doing a fresh install of RC2 because I have been wanting to use one of these themes since RC1, but he doesn't update it for nightlys...
If the fixes aren't anything huge then I will try to stick with RC2 for atleast half a day
Click to expand...
Click to collapse
If you visit the link to the merged changelog, anything that is there before 9 AM easter time is in this build. This includes a major fix for people having bootloop issues with RC 2. My build #3 can be considered RC 2 + fixes.

So far build #3 seems to be working with the RC2 DTR!

That's good to hear Derrty!

No more SD card damaged with #3, thanks for compiling !!! Now I can decide if I want to try the new kernel from Chad.
The one thing I learned from all this is that it's good to have a backup SD card that has restores on it. That way when your SD card gets F#[email protected]#$ up, you can just put in your other SD card and your up and running.

I have a complete backup of the SD card on my pc

dspcap said:
No more SD card damaged with #3, thanks for compiling !!! Now I can decide if I want to try the new kernel from Chad.
The one thing I learned from all this is that it's good to have a backup SD card that has restores on it. That way when your SD card gets F#[email protected]#$ up, you can just put in your other SD card and your up and running.
Click to expand...
Click to collapse
yeah it is. but it sucks when you have 32gig card and 28gig's are used and you have only usb 1 with a 1.25mb transfer speed.... :'(

cd2573 said:
I have a complete backup of the SD card on my pc
Click to expand...
Click to collapse
but it changes constantly with your apps too. it would be very time conduming to do it everyday

Mozy has a new mobile app coming that will automatically backup your phone.... not sure how it will work, but quite interested.

v941726 said:
but it changes constantly with your apps too. it would be very time consuming to do it everyday
Click to expand...
Click to collapse
Take a look at rsync backup for Android. rsync is my favorite tool for backups since it only copies the changes to the files in question (even large files that are modified but largely the same - rsync only copies the changes). I use that app, combined with Tasker to automate a nightly backup of my sd card as well as instant backup of my dcim dir. when the camera app exits. Oh and to sync podcasts to my phone from my mac. If you're running linux or OSX you've got rsync native on your system (just be careful learning how to use it so you don't clobber any important files). If you're on windows, there are some implementations of rsync (here's one) but I've never tried 'em so I dunno how well they work...

Yeaaaaaa! No more damaged sdcard! Thanks dude!
Sent from my ADR6300 using XDA App

wildland said:
Take a look at rsync backup for Android. rsync is my favorite tool for backups since it only copies the changes to the files in question (even large files that are modified but largely the same - rsync only copies the changes). I use that app, combined with Tasker to automate a nightly backup of my sd card as well as instant backup of my dcim dir. when the camera app exits. Oh and to sync podcasts to my phone from my mac. If you're running linux or OSX you've got rsync native on your system (just be careful learning how to use it so you don't clobber any important files). If you're on windows, there are some implementations of rsync (here's one) but I've never tried 'em so I dunno how well they work...
Click to expand...
Click to collapse
thanks. i've been looking for something like that. using tasker and getting it to work the way you want is more of a chore sometimes though

ProTekk Build #4 on its way. Including the merges from this afternoon.

man you are not playing

cd2573 said:
man you are not playing
Click to expand...
Click to collapse
Not one bit. I'm staying true to my word. I promised the community this so I'm going to do it! Even though the woman is getting annoyed by this I'm still doing it
Update: ETA 10 minutes until completion and +5 for uploading. Get ready!
Update #2: Uploaded and ready on my site! Link is in the first post!
Mediafire link is up as well.

I love how fast these are coming.

[Patch] Incremental patch for updating from 2.6.35.7 to .14

As the title says this patch is for updating the Samsung sources from version 2.6.35.7 to 2.6.35.14. Might be useful for some kernel developers. I was stuck at bootloop after updating the initramfs.cpio with the updated modules, but this has nothing to do with the patch itself. If wanted I can also upload the original incremental patches.
I hope this gets integrated in some kernels soon (I heard others expermented with this as well), as it will fix the Android OS bug.
Regards,
Diewi

Diewi said:
As the title says this patch is for updating the Samsung sources from version 2.6.35.7 to 2.6.35.14. Might be useful for some kernel developers. I was stuck at bootloop after updating the initramfs.cpio with the updated modules, but this has nothing to do with the patch itself. If wanted I can also upload the original incremental patches.
I hope this gets integrated in some kernels soon (I heard others expermented with this as well), as it will fix the Android OS bug.
Regards,
Diewi
Click to expand...
Click to collapse
Hey man,
Thanks, I need this
You can teach me howto make patches for kernels?
How to patch up the kernel for example? You are just legend
Netchip

Hey netchip,
of course I can
First you need to run this command for every incremental patch:
BZIP compressed:
Code:
bzip2 -dc patch-2.6.35.X-Y.bz2 | patch -p1
uncompressed:
Code:
patch -p1 < patch-2.6.35.X-Y.patch
The X stands for the minor version you already have, Y for the one you want to patch to - usually Y = X + 1 for "official" patches.
After every application of a incremental patch you need to check weather a "hunk" failed. Normally, this happens if you get a warning about parts of the patch already being applied. You will recognize the failed parts by their ending: .rej. You'll need to check those files against the to-be-patched source file and maybe do some changes to it.
After you gone through all patches, unpack the unmodified kernel again and compare both directories with the following command:
Code:
diff -uNrB GT-N7000_Kernel_orig GT-N7000_Kernel > SGN_2.6.35.X-Z.patch
Then you'll get a patch that includes all the single ones.
BTW, I'm assuming you're in a UNIX environment.
(@all)
In order to apply the patch you can simply take the commands listed in the beginning of the post. The patch uploaded in the OP (.7-.14) is uncompressed.
I'll just attach the incremental patchset for completeness (bzip compressed patches)

Diewi said:
Hey netchip,
of course I can
First you need to run this command for every incremental patch:
BZIP compressed:
Code:
bzip2 -dc patch-2.6.35.X-Y.bz2 | patch -p1
uncompressed:
Code:
patch -p1 < patch-2.6.35.X-Y.patch
The X stands for the minor version you already have, Y for the one you want to patch to - usually Y = X + 1 for "official" patches.
After every application of a incremental patch you need to check weather a "hunk" failed. Normally, this happens if you get a warning about parts of the patch already being applied. You will recognize the failed parts by their ending: .rej. You'll need to check those files against the to-be-patched source file and maybe do some changes to it.
After you gone through all patches, unpack the unmodified kernel again and compare both directories with the following command:
Code:
diff -uNrB GT-N7000_Kernel_orig GT-N7000_Kernel > SGN_2.6.35.X-Z.patch
Then you'll get a patch that includes all the single ones.
BTW, I'm assuming you're in a UNIX environment.
(@all)
In order to apply the patch you can simply take the commands listed in the beginning of the post. The patch uploaded in the OP (.7-.14) in uncompressed.
I'll just attach the incremental patchset for completeness (bzip compressed patches)
Click to expand...
Click to collapse
Thanks for your answer
Where can I get normally the incremental patches?
Kernel.org?
Also, if you are interested in building a kernel with me, send me a PM, and I will answer
Sent from my GT-I9100

Yes, usually at kernel.org. But lately they are only hosting the latest incremental patch for the longterm support kernels (2.6.32 and 2.6.33). Also the latest incremental patches (up to 4 minor versions in the past) for the latest kernel.
These particular patches I found using google that directed to some outdated mirrors. I just needed to adapt the version numbers of the patch and search for this string.

While waiting for my Note, I just have downloaded kernel sources and my linux box is cross compiling the sources with the recommended toolchain (4.4.0) as I write this post
I just noticed that the process reports quite a few warnings...
When I have my Note, I will try a few things like undervolt (already located the bit of relevant code for this) and will add "interactive" CPU governor which is far better than the default "on demand" for interactivity.
If everything goes well, I will add this upgrade too
Edit:
right. Done. Waiting for the phone to test this first almost stock kernel
Code:
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready

Diewi said:
As the title says this patch is for updating the Samsung sources from version 2.6.35.7 to 2.6.35.14.
Click to expand...
Click to collapse
Have you tested the Patch? Which toolchain did you use for compiling the Note Kernel?
I have tried it the other way around: Take vanilla 2.6.35.14 sources and include the Samsung patches from 2.6.35.7. I found out, that Samsung uses a lot of Backports in his code. Also I had some problems with wrong applied fuzzy patches.
Meanwhile it works. Android OS is much lower with a 2.6.35.14 Kernel. But the battery lifetime is not much longer than before.
I had also some problems with the Runtime Powermanagement of USB Devices. I'm note sure if it was a problem of the patches or my compiler options. I have to test a little bit in the next days.

RiverSource said:
Have you tested the Patch? Which toolchain did you use for compiling the Note Kernel?
I have tried it the other way around: Take vanilla 2.6.35.14 sources and include the Samsung patches from 2.6.35.7. I found out, that Samsung uses a lot of Backports in his code. Also I had some problems with wrong applied fuzzy patches.
Meanwhile it works. Android OS is much lower with a 2.6.35.14 Kernel. But the battery lifetime is not much longer than before.
I had also some problems with the Runtime Powermanagement of USB Devices. I'm note sure if it was a problem of the patches or my compiler options. I have to test a little bit in the next days.
Click to expand...
Click to collapse
Dunno if it's making a huge difference, but your GCC is 4.5.4 whereas the recommended is 4.4.0
Code:
> cat Readme_Kernel.txt
################################################################################
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.0

No, the Toolchain makes no big difference. I hoped the newer Linaro one optimzes better, but at least with CF Bench there was no big difference between 4.4.0, 4.4.3 or 4.5.4 (the results where slightly better than with stock kernel, 13300 points in stead of 13000 with stock).

RiverSource said:
Have you tested the Patch? Which toolchain did you use for compiling the Note Kernel?
I have tried it the other way around: Take vanilla 2.6.35.14 sources and include the Samsung patches from 2.6.35.7. I found out, that Samsung uses a lot of Backports in his code. Also I had some problems with wrong applied fuzzy patches.
Meanwhile it works. Android OS is much lower with a 2.6.35.14 Kernel. But the battery lifetime is not much longer than before.
I had also some problems with the Runtime Powermanagement of USB Devices. I'm note sure if it was a problem of the patches or my compiler options. I have to test a little bit in the next days.
Click to expand...
Click to collapse
How did you have included samsung drivers in a vanilla kernel?
I know now how to patch up, but how works your way?

No, I didn't test the patch very well. I just compiled the kernel with the patches and added CF's initramfs.cpio (packed) to the zImage file. It did boot up, but wlan didn't work, as the modules in the initramfs were not compiled for this build. The "about" page showed the minor version ".14".
I used codesurgery version 2010.09.51 for this test.
@netchip:
I found a good guide how to extract the samsung specific patches in this thread (bottom of OP):
http://forum.xda-developers.com/showthread.php?t=784270
Maybe we see a 3.1 kernel soon

Diewi said:
No, I didn't test the patch very well. I just compiled the kernel with the patches and added CF's initramfs.cpio (packed) to the zImage file. It did boot up, but wlan didn't work, as the modules in the initramfs were not compiled for this build. The "about" page showed the minor version ".14".
I used codesurgery version 2010.09.51 for this test.
@netchip:
I found a good guide how to extract the samsung specific patches in this thread (bottom of OP):
http://forum.xda-developers.com/showthread.php?t=784270
Maybe we see a 3.1 kernel soon
Click to expand...
Click to collapse
You have a dump of vanilla 2.6.35.7?
Compare these, and you have the drivers, hmm I go try.

Or you could use the patched Samsung kernel (2.6.35.14) and compare this to the vanilla kernel. I'm absolutely not sure if this would bring any benefits, but I think that way the patches backported by Samsung would get filtered out.
Sent from my GT-N7000 using XDA App

Diewi said:
Or you could use the patched Samsung kernel (2.6.35.14) and compare this to the vanilla kernel. I'm absolutely not sure if this would bring any benefits, but I think that way the patches backported by Samsung would get filtered out.
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
That's also a good idea!

Thanks.
The patched vanilla kernel (.14) can be found here:
http://ftp.ua.postgresql.org/pub/linux/kernel/v2.6/longterm/v2.6.35/
The 2.6.35.7 vanilla kernel can be found directly on the ftp server of kernel.org

Diewi said:
Hey netchip,
of course I can
First you need to run this command for every incremental patch:
BZIP compressed:
Code:
bzip2 -dc patch-2.6.35.X-Y.bz2 | patch -p1
uncompressed:
Code:
patch -p1 < patch-2.6.35.X-Y.patch
The X stands for the minor version you already have, Y for the one you want to patch to - usually Y = X + 1 for "official" patches.
After every application of a incremental patch you need to check weather a "hunk" failed. Normally, this happens if you get a warning about parts of the patch already being applied. You will recognize the failed parts by their ending: .rej. You'll need to check those files against the to-be-patched source file and maybe do some changes to it.
After you gone through all patches, unpack the unmodified kernel again and compare both directories with the following command:
Code:
diff -uNrB GT-N7000_Kernel_orig GT-N7000_Kernel > SGN_2.6.35.X-Z.patch
Then you'll get a patch that includes all the single ones.
BTW, I'm assuming you're in a UNIX environment.
(@all)
In order to apply the patch you can simply take the commands listed in the beginning of the post. The patch uploaded in the OP (.7-.14) is uncompressed.
I'll just attach the incremental patchset for completeness (bzip compressed patches)
Click to expand...
Click to collapse
thanks!!
i'm build galaxy s2 kernel
i hope patch 2.6.35.7 to 2.6.35.14
no problem at use Incr_PatchSet_2.6.35.7-14.zip file?
and SGN_2.6.35.7-14.patch.zip better than Incr_PatchSet_2.6.35.7-14.zip?
(sorry my bad english)

As you are trying to apply the patch to a s2-kernel, I would advise you to use the original incremental patchset. You only need to go through the *.rej files and check weather the source needs a modification (see http://linuxhaven.de/dlhp/HOWTO/DE-Kernel-HOWTO-5.html). The all-in-one patch is made by a diff of the original and the patched Galaxy Note kernel, so you might miss something.

Diewi said:
As you are trying to apply the patch to a s2-kernel, I would advise you to use the original incremental patchset. You only need to go through the *.rej files and check weather the source needs a modification (see http://linuxhaven.de/dlhp/HOWTO/DE-Kernel-HOWTO-5.html). The all-in-one patch is made by a diff of the original and the patched Galaxy Note kernel, so you might miss something.
Click to expand...
Click to collapse
successful upgrade to 2.6.35.14
thanks

Dude... Will this work on Galaxy y ?? or this is device specific ????

Nachiket.Namjoshi said:
Dude... Will this work on Galaxy y ?? or this is device specific ????
Click to expand...
Click to collapse
No.
Sent from my GT-N7000 using Tapatalk 2

[ROM][6.0][jem] CM redux

I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.
Click to expand...
Click to collapse
READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:
doesn't work as a result of flashing this;
initiates a nuclear meltdown, or;
doesn't permit your alarm clock to function normally.
By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.
Click to expand...
Click to collapse
Downloads:
click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)
Features:
[*]Compiled with UBERTC 4.9
UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
based on CM13
more to come!
Known issues in post #2
Changelog in post #3
Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.
Credit where credit is due
@Hashcode, because we wouldn't have CM on our kindles at all without him.
@BuQQzz for some mentoring & advice
@transi1 for porting CM13 and providing some useful fixes for build errors
XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD
Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-29
Last Updated 2016-08-07

Known issues
Bugs affecting all CM13-based ROMs on the kindle
Screen artifacts when playing video from Snapchat, Vine, etc.
Audio chops in and out often
Other bugs currently afflicting the other CM13 ROMs for this device
Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
Play Store & Setup Wizard FCs
CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)

Changelog
08/07/2016
experimental backtracking to kernel 3.0.84+
July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
07/01/2016
doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
reverting from UBERTC toolchains to native CM/AOSP one
05/20/2016
defecting to BlissRoms-Devices GH for newest device config files
05/2016 security patches from AOSP, et al.
04/27/2016
refreshing CM sources & obtaining latest sources from transi1
04/09/2016
revert the 4/4 kernel reversion; back to 3.0.101(+)
carry in latest edits from transi1 to try to fix the camera
04/04/2016
revert to kernel 3.0.72+
first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
03/29/2016
initial build!

Roadmap
The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.
Layers/RRO theming support
Custom boot animation (or at least one scaled to the kindle's screen size)
Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
Publication of a custom .gapps-config file for use with opengapps packages

I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.

So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.

Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.

Some updates...
I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.

More updates...
It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:
I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.
Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.
Finally, some planned changes:
I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
Obvious name change in the ROM, mentioned earlier.
Replacing CM's theme engine with RRO(?)
CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.

Good version,thanks. But it often wifi reconnect , can it fix?

wizard_mini said:
Good version,thanks. But it often wifi reconnect , can it fix?
Click to expand...
Click to collapse
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?

monster1612 said:
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
Click to expand...
Click to collapse
It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time

Android system cost battery drain more than screen, is it normal?

wizard_mini said:
Android system cost battery drain more than screen, is it normal?
Click to expand...
Click to collapse
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.

I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?

wizard_mini said:
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
Click to expand...
Click to collapse
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.

sirp0p0 said:
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
Click to expand...
Click to collapse
It's a good solution,, I fix it, thanks

monster1612 said:
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
Click to expand...
Click to collapse
I use 4hours screen on and 7hours screen off cost 92% battery.

wizard_mini said:
I use 4hours screen on and 7hours screen off cost 92% battery.
Click to expand...
Click to collapse
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.

monster1612 said:
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
Click to expand...
Click to collapse
Thanks. I am expecting it!

[ROM][NIGHTLY][KK] Cyanogenmod 11 [ASB: August 2016]

Hi everyone,
I got my mako in apr 2013. Apparently, on cm12/13 it seems to be affeected by this bug. So, to clear any doubt about it, I wondered if downgrading to kitkat might help in general.
Even if the battery gain was to be dramatically high, security is my first corcern. The last
Android security bulletins (ASB) contain a lot of critical bugs; anyway from them I discovered that kitkat still get security updates from google and from CMxLog that someone still add to about page that cm11 is updated to respect the "MM YYYY ASB". I trust cyanogenmod in that.
So since I never tried to compile aosp and as this rom wasn't updated in a while, I synced cyanogenmod repos and I compiled it with the instructions on cyanogen wiki.
The rom is good and stable.
As you can see from the screenshot below, without gapps, with major instant messengers (whatsapp, telegram-foss with smart push disabled) and email push notifications (k9 mail), battery drain on idle is basically non-existent:
I wanted to share this build with you because I think this is an amazing community.
I plan to update this rom every time an ASB comes out (once in a month, as long as google keeps supporting kitkat).
Zio Guiduccio
NB: If you can't open Messages, flash first june rom, then august one.
26/08/2016
I made available a second build (FOSS) with some little differences. Here they are:
- Replaced Browser with getChromium app, because zero-day exploits in kitkat webviews (use only updated chromium!);
- Replaced Email with K9-mail, because kitkat webview and zero-day exploits;
- Removed Exchange2 because zero-day exploits (don't know alternatives othen than normal gmail);
- Added F-Droid;
- Added Offline Calendar, otherwise standard calendar is useless;
- Added Adaway;
- Added Document Viewer (many formats reader);
- Added Kolab Notes;
- Added Yaab (Minimum brightness on-demand).
Download
CM-11-20160820-GUIDUCCIO-FOSS-mako.zip
CM-11-20160820-GUIDUCCIO-mako.zip
CM-11-20160611-GUIDUCCIO-mako.zip

Just as you mentioned battery drain has lowered.
Thanks for ROM!

zio guiduccio said:
Hi everyone,
I got my phone in apr 2013. Apparently, on cm12/13 it seems to be affected by this bug. So, to clear any doubt, I wonder if downgrading to kitkat might help in general.
Even if the battery gain was to be dramatically high, security is my first corcern. The last
Android security bulletins (ASB) contain a lot of critical bugs; anyway from them I discovered that kitkat still get security updates from google and from CMxLog that someone still add to about page that cm11 is updated to respect the "MM YYYY ASB". I trust cyanogenmod in that.
So since I never tried to compile aosp and as this rom wasn't updated in a while, I synced cyanogenmod repos and I compiled it with the instructions on cyanogen wiki.
The rom is good and stable.
The only change I had to do was to replace these files
/system/framework/webview
/system/framework/webviewchromium.jar
/system/lib/libchromium_net.so
/system/lib/libwebviewchromium.so
/system/lib/libwebviewchromium_plat_support.so
with ones from cm-m12-official because logcat tells me that the webview i compiled goes segfault when I try to open messages in mms.apk, k9 mail and settings in rar and amaze. In general, the code is untouched.
As you can see from the screenshot below, without gapps, with major instant messengers (whatsapp, telegram foss with smart push disabled) and email push notifications (k9 mail), battery drain on idle is basically non-existent:
I wanted to share this build with you because I think this is an amazing community.
I plan to update this rom every time an ASB comes out (once in a month, as long as google keep supporting kitkat, which I hope is long).
Obviously, the ROM is updated to the latest android security bulletin of 1st june 2016.
Zio Guiduccio
Download
MD5SUM: 4B129774050768E8D21114D7816A8D56
CM-11-20160611-GUIDUCCIO-mako.zip
Click to expand...
Click to collapse
Hi,
Is there any chance you've updated this for the July ASB? Might give it a shot if you haven't
(And thank you, this is freaking awesome!)

Just a quick question, but can you download Pokemon GO from Play Store when using this ROM?

thegodsmustbecrazy said:
Hi,
Is there any chance you've updated this for the July ASB? Might give it a shot if you haven't
(And thank you, this is freaking awesome!)
Click to expand...
Click to collapse
Sorry. The day cyanogenmod mantainer approved the patches (31th july) I went away from home (and the building machine.) I will come back next week at minimum. I'll publish next build for 15th August at maximum.
EDIT: Still no july patches merged to cm11 branch.

espionage724 said:
Just a quick question, but can you download Pokemon GO from Play Store when using this ROM?
Click to expand...
Click to collapse
Can't see why non.

The rom has been updated to August 2016 ASB.

zio guiduccio said:
The rom has been updated to August 2016 ASB.
Click to expand...
Click to collapse
Thank you!
I'm running this with my n4 underclocked at 700mhz (might bump it up to 1ghz, but I haven't really noticed any crazy lag to speak of) and the battery life must be at least double! Freaking awesome if you ask me :good:

zio guiduccio said:
The rom has been updated to August 2016 ASB.
Click to expand...
Click to collapse
In your OP, you mention running this ROM "without gapps." Is the ROM designed to be run only in a state that is without any gapps package, or is it OK to use a gapps package if we want? I would use Open GApps for KK 4.4.

Of course you flash KK gapps.

[ROM][CM12.1][SEMI-OFFICIAL] CyanogenMod 12.1 (2016-10 Security Patch Level, Fixes)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 12.1 is a free, community built, aftermarket firmware distribution of Android 5.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
The following CyanogenMod 12.1 builds are based entirely on CyanogenMod code. Please refer to the official XDA thread for CM-12.1 on the LG G2 for basic information on installation and usage. It has the same requirements. It has many of the same limitations, except for those expressly listed updates listed in the Changes list below.
Why are you doing this, why do I want these builds?:
The last release of an OS from LG for the G2 was Lollipop. Since we need to use the proprietary binaries from LG to make our devices functional, and since CM-12.1 is based on Lollipop, the 12.1 release of CyanogenMod is regarded as the most stable for our device simply because they function natively at similar API levels.
Sadly, the LG G2 was one of the very first devices transitioned to the Marshmallow release of CM (CM-13.0) and it's never been quite the same since. The last official 12.1 nightly for most G2 devices is from November of 2015, and since then there have been many stabilizations to the CM-12.1 code base, as well as many security patches from Google. Therefore I thought it would be important to offer people the ability to run a more recent CM-12.1 nightly, rather than force them to transition to CM-13.0 in order to be up to date. And since CM-12.1 is not really changing, except for Google security level patches, I can make this offering once every few months without leaving people to far behind.
These builds are based entirely on CM source code. They are, for all intents and purposes, official CM-12.1 nightlies for the G2. I did make a few very small, but important changes that I thought most people would benefit from. Namely I backported the Snap camera from CM-13.0, as well as fixes to the IR Blaster permissions (so it'll work without having to switch to permissive mode) and changes to the volume that most people were constantly asking for. These builds are what CM-12.1 would have looked like had we waited a few months for CM-13.0 to become mature.
You should know that I built this originally for my mom and a friend of mine. I do not run this on a daily basis. You should consider support relatively non-existent, except for the help you get from the other people on the forums.
Changes since Official 2015-11-17 CM-12.1 Snapshot, About these builds:
Official CM-12.1 sources
Current as of 20161114
October 1, 2016 Android security patch level
CVE-2016-5195 (Dirty COW) kernel vulnerability fix (change 170897)
Integrated CM-13.0 Snap Camera w/ working HDR mode
IR Blaster fixes (build 2016-06-14 or newer, change 149554)
Audio volume adjustments from cm-13.0 (build 2016-06-14 or newer, change 149563)
I DO NOT give any guarantees on this working. PLEASE make a full backup before installing this zip. This rom comes with ABSOLUTELY NO SUPPORT (that's right, I don't really care if it works or not). That being said, I hope it works for you and you enjoy it
Downloads:
All features, unless otherwise noted, are cumulative. It is safe to assume that if a feature is added to a release, all subsequent releases likely have that feature.
Final Build 2016-11-14: October 1, 2016 Security Patch Level
These builds incorporate the latest security patches for Lollipop (CyanogenMod 12.1) as of October 14, 2016. They additionally incorporate a fix for the Dirty COW vulnerability. And since it seems the CM builds are over for CM-12.1, I ran a build for the ls980 as well. These are my final builds for this ROM. I will not be releasing any more after this.
d800: 1e2b77f689f1812e05cbc6cce5f0e0a6
d801: 9845a9bbef8a1721b8dd90e962ecfda9
d802: 16edad3b455bcb39f2ae5f20a3b04842
d803: f2f5602c080973417f065048d9f6d2ef
ls980: efc40e09538a483af2af1373b66b3ea2
vs980: 4f1379e03b62875f42b0599b8490f6e7
Please reference the above md5sums when verifying downloads from other sites.
Download 2016-11-14 for d800, d801, d802, d803, ls980 and vs980.​
Build 2016-08-19: August 1, 2016 Security Patch Level
These builds incorporate the latest security patches for Lollipop (CyanogenMod 12.1) as of August 19, 2016.
d800: c6161c397b4333010e1aa0bb799ebd11
d801: 94fc86c21677380cd68a2b8809133189
d802: 1633e4feb08ac3a003219153b70d1a63
d803: de0abb09091eff724f09db92bc3e782c
vs980: afce5b1e4e67ec7aafb5f16fb883d0d6
Please reference the above md5sums when verifying downloads from other sites.
Download 2016-08-19 for d800, d801, d802, d803 and vs980.​
Build 2016-06-14: June 1, 2016 Security Patch Level
These builds add proper IR Blaster sepolicy changes for properly working IR. They also add audio volume changes to increase the device volume output.
Note: Some builds list the build date as 2016-06-15. The builds are all identical, they take a little over an hour to run each one, and the date changed between builds. I did not update my sources between builds, they are NOT DIFFERENT AT ALL.
IMPORTANT NOTE: This build contains a modified and BOOSTED mixer_paths.xml file. Please be careful when upgrading to adjust volumes. I am not responsible if you blow your speaker. These changes were made to CM-13.0 (change: 138749) and have been backported. They are assumed safe.
Download 2016-06-14 for d800, d801, d802, d803, ls980 and vs980.​
Build 2016-03-28: March 1, 2016 Security Patch Level
The builds include the version of Snap included with CM-13.0. They also include a fix so HDR works with it (I don't believe my old Snap builds worked w/ HDR before).
Download 2016-03-28 for d800, d801, d802, d803 and vs980. No build was done for ls980 as it was still receiving CM-12.1 nightlies.​

Build Usage Notes:
I DO NOT give any guarantees on this working. PLEASE make a full backup before installing this zip. This rom comes with ABSOLUTELY NO SUPPORT (that's right, I don't really care if it works or not). That being said, I hope it works for you and you enjoy it
I'm so confused! The last official nightly was from Nov-2015, how in the world could this be current?!?:
The CyanogenMod devs didn't stop developing on version 12.1 when we were transitioned to 13.0. There was a period of months where a group of developers started transitioning existing features and developing new features on CM-13.0, while another group worked to continue to stabilize and maintain the existing CM-12.1 codebase. Sadly, we were one of the very first devices transitioned to 13.0 at the very beginning of the 13.0 development. Therefore we never received a particularly solid 12.1 build.
These builds represent a nightly build from the continually developed 12.1 code base. It has a large number of fixes that have occurred (and, at a very slow pace now, continue to occur) from November of 2015 to the present. Additionally this build has all the monthly security patches from google. These are incorporated by CM, not me. With the exception of the Sprint(US) model of the G2 (the LS980), these builds represent the most up-to-date official builds of CM-12.1 for the G2 you will find.
What are the requirements and/or procedure for installing this ROM?:
These CM-12.1 builds are essentially the same as the official and nightly CM-12.1 builds. Therefore the requirements are the same. Please visit the Official CM-12.1 XDA Thread for information on the requirements and procedure on installing this ROM.
NOTE: This is my own personal recommendation. I HIGHLY recommend following the advice from the CM-13.0 builds: if you can, if you have the chance, backup your device and copy that backup and your phone data to your computer, then completely wipe your device. Do a full stock update (KDZ, TOT, forced OTA's, whatever) to bring your device up to stock LG Lollipop. From there, root the device, do the auto-rec, update TWRP to the latest from blastagator, and then install this ROM and a compatible Gapps package. I personally believe putting your device on stock lollipop firmwares will give you the best possible experience on a Lollipop ROM. And whatever you do, DO NOT USE BOOTSTACKS!!!
Flashing over official CM-12.1:
As stated above, these builds are essentially the same as the official and nightly CM-12.1 builds. They aren't substantially different enough to cause compatibility problems. They are simply updated builds with a number of fixes, and the only real added package is the Snap from CM-13.0. You *should* be about to simply flash this over an existing official CM-12.1 build (which I recently did over a 7-8 month old build with no ill effect).
That being said, if in doubt, do the appropriate backups and start fresh from scratch, restoring app data as necessary. Often times a fresh install can solve a number of odd problems and lead to a smoother experience.
I have a newer nightly, I just want the Snap camera:
If you are currently on the Sprint LG G2 (The LS980) you are already on the official CM-12.1 track, and any future official nightlies will incorporate the IR and Volume patches from my 20160614 builds. Otherwise if you like the nightly you're on and you really just want the snap camera, you can download them here:
Download: Snap camera for CM-12.1 G2 Builds
These zip files should be installed via the recovery. They are also persistent, you won't need to flash them every time you update the ROM. You will only need to re-install whenever you do a clean reset of the device. I will try to upload a new build of Snap whenever I build new snapshots.
Note about Snap builds: Because the Snap settings aren't integrated into the ROM itself, I don't believe these Snap builds will have working HDR. I'm not sure, but if it doesn't work there's nothing really I can do about it.
Can I safely use the CM Updater?:
In a word: No. The only exception to that is if you are on the LS980 device. The recommended way to update these builds is by manually downloading them and flashing them from TWRP (or your chosen recovery).
The CM Updater downloads updates from CM's official build system. For most G2 devices CM Updater will offer you CM-13.0 builds to update to. If you try to update to a CM-13.0 release through the CM Updater from CM-12.1, your device will cease to work. Your best bet (and my recommendation) is to go into the updater (Settings -> About Phone -> System Updates) and setting the update type to "Manual". That will keep the device from checking for updates. Another option would be to re-install your gapps and set it to remove the CM Updater all together.
If you are on an LS980 device, the CM build system is providing you relatively up to date builds. You should be able to use CM Updater to safely update from one of my releases to a newer official CM nightly without any trouble. The only thing you will lose is the Snap camera. In this case I would recommend staying with the official nightly and simply installing the Snap camera separately as mentioned above.
My device seems to be heating up:
User @mwedo on the official thread had a similar problem (click here to see). He tracked it down to the "OK Google" Hotword detection. After disabling it his device things returned to normal. I don't know why this happens, and I doubt it'll get fixed in my lifetime since 12.1 is no longer on the support track for us. However, I am mentioning it here for those of you experiencing a similar problem. I have also updated the gapps-config attachment that I posted below to disable the default Hotword enrollment. Hopefully that'll save people some headache. The gapps-config keyword is "Hotword".
IMPORTANT: Gapps / OpenGapps and Snap Camera:
If you use a modern-ish Gapps package, it may recognize Snap as the default CM camera and remove it. You should modify your Gapps config so that it does NOT do that. If you need to modify Gapp's behavior, you can wipe the system partition (do NOT factory reset), and then fresh install your ROM and Gapps (with any gapps-config modifications you need). I am attaching the gapps-config.txt file I use in conjunction with OpenGapps "Stock" release. Keep in mind it removes the built in Gallery to be replaced by Google Photos.

Thank you so much bro ???
Sent from my LG-D802 using XDA-Developers mobile app

Fuq yeah! Great news!

D801 version working great.

Mother of god @dr4stic, what have you done regarding the kernel?? This is the most supreme caching I've ever seen! Wow! This build is blistering fast on my D802 and it's multitasking like a boss!
I've yet to see a single bit of lag or jerky transitions but... WOW! I'm totally speechless, sick.
Stunning build! Thank you, thank you, THANK YOU!!

Coming from stock rooted 4.4 will I just need to flash bootstack? If going from CM12.1 back to stock 4.4 what is the process then? Really want to test this ROM
Sent from my LG-D802

zizuka said:
Coming from stock rooted 4.4 will I just need to flash bootstack? If going from CM12.1 back to stock 4.4 what is the process then? Really want to test this ROM
Sent from my LG-D802
Click to expand...
Click to collapse
If you're willing to, I'd HIGHLY (and I've been meaning to list this in the second post... which btw you should read), I HIGHLY recommend taking your device up to stock Lollipop from LG. Do the TOT's, KDZ's, force OTA's, whatever you need to do to arrive at stock LG lollipop. Then root and autorec from there. And then update to the latest blastagator TWRP and install this rom and a suitable Gapps. That should give you the best experience. This is a Lollipop ROM and even though it will theoretically work with a KK firmwares, it'll likely be more solid on LP firmwares.
Also, bootstacks are the devil. They are a crutch, the devs that make them don't even like them. We had so much trouble with it on CM-13.0, the troubles only went away when people did full stock restores and then rooted instead of using bootstacks. I know you won't, but you should read the FAQ for CM-13.0.

dr4stic said:
If you're willing to, I'd HIGHLY (and I've been meaning to list this in the second post... which btw you should read), I HIGHLY recommend taking your device up to stock Lollipop from LG. Do the TOT's, KDZ's, force OTA's, whatever you need to do to arrive at stock LG lollipop. Then root and autorec from there. And then update to the latest blastagator TWRP and install this rom and a suitable Gapps.
Click to expand...
Click to collapse
That's exactly what I did on the second run. By second run I mean that at first try I just flashed this build over the CM13 to see, or to be precise - to hear, improvements in sound. Sound is great tho! It's loud and clear and it's a joy to blast some nice beats through my Sennheiser headphones. Then flashed it "for real".
However, back to the point... For the first time ever I decided to bother with all that boring stuff; KDZ flashed latest version for my IMEI, rooted, TWRPed (lol word) to the latest version (3.0.2.1 IIRC), wiped everything including the internal storage (just b/c I prefer OTG), rebooted back to TWRP, flashed this marvelous 12.1 build, flashed stock (open)Gapps with some heavy tweaks in config file (removed a ton of that, something like you did @dr4stic but with a couple apps more or should I say less), wiped everything (except the system) once again, rebooted and... it's running like a champ! It's literally the snappiest and smoothest experience I've ever seen on the G2 and even my ex G Flex 2 can't beat this fluidity. Plus there's that insane RAM management without bothering to flash different kernels. It's so good that multitasking is a breeze. Dat multitasking ?
I seriously can't recall if there is any ROM that wasn't giving me some serious frustrations because I'm a professional nitpicker. Your latest build is the first one to achieve that and just when I thought it couldn't get better - this stellar beauty popped here ?

mwedo said:
I seriously can't recall if there is any ROM that wasn't giving me some serious frustrations because I'm a professional nitpicker. Your latest build is the first one to achieve that and just when I thought it couldn't get better - this stellar beauty popped here
Click to expand...
Click to collapse
I'm certainly happy you guys are enjoying this build as much as you are. Rashed hates when I get into a discussion with him about how unstable cm-13 is on the device, and that if I really thought it was stable I'd put my mom's phone on it, which I haven't done yet. CM-13.0 is stable, but it's stable in the sense that the phone won't catch fire and it consistently has the same bugs it's always had. But CM-12.1 for our device is simply rock solid. And that has to do with the fact that the last release from LG was for LP and that's where our proprietery binaries are from.
Rashed once told me something interesting... in theory the G2 and G3 could likely use the same RIL's. That's a pretty big deal because the RIL is the thing I find buggiest about the CM-13 release for the G2, and LG finally released native marshmallow to the G3. Also, PsychoGame and I were able to get LG's kernel for the G3 to build and boot quite easily for the G2. The only reason we never really released it was because there were a couple showstoppers with bluetooth and the vibrator driver. Other than that, everything worked beautifully. I'm gonna talk to some other devs and see if I can get a crash course on porting a RIL. I'm not quite ready to abandon this device yet... I'm close, but not just yet.
I remember Rashed talking about how we were moving to marshmallow really early, and I was all excited (I missed being on early releases when I had my Nexus). I later regretted that we didn't stay on Lollipop a little longer.
As for these builds, I otherwise did nothing to the build. It's just pure unadulterated CM-12.1 with Snap built in. I guess they did a good job after all. I hope you guys enjoy!

Is the old random vibration bug exist ?

Ok, i think i will flash this rom during the week end. The only thing that prevented me to flash an AOSP build is the fact that the camera doesn't have the photosphere option. Does this snap camera has the photosphere option? However thank you very much for this build!

KpKi said:
Is the old random vibration bug exist ?
Click to expand...
Click to collapse
No more, bro
Sent from my LG-D802 using XDA-Developers mobile app

[email protected] said:
Ok, i think i will flash this rom during the week end. The only thing that prevented me to flash an AOSP build is the fact that the camera doesn't have the photosphere option. Does this snap camera has the photosphere option? However thank you very much for this build!
Click to expand...
Click to collapse
If you want photosphere, install the Google camera from the play store. It isn't difficult, and it seems a bit much to avoid AOSP just for that feature. Otherwise no, snap doesn't have photosphere natively, neither does the native AOSP camera. But Google's camera from the play store does.

I have paired this build with Lambda kernel Domino (stable) and everything is working as it should. Give it a try.
Thanks a lot @dr4stic for the build.

dr4stic said:
If you want photosphere, install the Google camera from the play store. It isn't difficult, and it seems a bit much to avoid AOSP just for that feature. Otherwise no, snap doesn't have photosphere natively, neither does the native AOSP camera. But Google's camera from the play store does.
Click to expand...
Click to collapse
Yes, i've tried to download the google camera but i can't find it anywhere in the playstore.... However thank you for your response and for the rom!

Best ROM so far but one bug it over heats
Sent from my LG-D800 using Tapatalk

lox2013 said:
Best ROM so far but one bug it over heats
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Yes this is my observation too .

lox2013 said:
Best ROM so far but one bug it over heats
Click to expand...
Click to collapse
KpKi said:
Yes this is my observation too .
Click to expand...
Click to collapse
Try disabling everything having to do with "OK Google" voice detection. On the official thread, someone discovered that the cause of his overheating was because of the "OK Google" detection. You can try turning that all off and seeing if it makes a difference.
Google (the App) -> Press Hamburger Menu -> Settings -> Voice -> "OK Google" detection
On that screen, make sure all switches are turned off. Then, for good measure, reboot.

Then the play store stops I don't know why
Sent from my LG-D800 using Tapatalk