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

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

{
"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

Related

[MOD] tabletUI on AOSP/CM10.1/CM10.2 - Auto-Patcher >>UPDATE: AOSP 4.3 supported!!<<

[MOD] tabletUI on AOSP/CM10.1/CM10.2 - Auto-Patcher >>UPDATE: AOSP 4.3 supported!!<<
tabletUI for ANY DEVICE running AOSP, CM10.1, or CM10.2
{
"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"
}
Check out post 2 for way more screenshots!
All you need is to get the latest version of the Auto-Patcher.(or ApG)
Linux/Mac: Check out mateorod's thread for instructions on getting the auto-patcher set up and how to use it.
Windows: Check Kobik77's post on ApG and download the latest version of ApG, which puts everything you need to make these patches together for you automatically!
Once you have that all set up just run your favourite AOSP, CM or SlimBean rom through the auto-patcher, patching for tabletUI. Auto-patcher will automatically detect your rom type and use the appropriate patches. It really could not be any easier!
(In ApG if you must set the rom type then use AOSP for Slim)
Make A Backup Before Trying Any Of These Mods! I will not be responsible for your data loss.
The Auto-Patcher will produce an update.zip and a restore.zip. I recommend moving both to your device before flashing.
Flash the produced update.zip in recovery and reboot.
Enjoy the tabletUI goodness!
If you do experience any issues, or your device bootloops, or you just want to go back to the way things were before applying the tabletUI mod, boot into recovery and flash the restore.zip. This will replace ALL of the original rom files and you should be able to boot up normally.

Confirmed Devices (Roms):
Nexus 7 - 2013 (AOSP/CM)
Nexus 10 (AOSP/CM)
Nexus 7 (CM)
Galaxy Tab 2 (AOSP/CM/SLIM)
Asus Transformer TF101 (CM)
Nook Color (CM)
Motorola Xoom (CM) - Thanks LQQKS!
Acer Iconia A500 (CM) - Thanks rsriram22!
Galaxy Grand Duos GT-I9082 (CM) - Thanks @karipari95! (who says setting dpi to 160 perfects the tablet look!)
If you have just patched a new device, not on this list let me know so I can add it!Known Issues:
This mod is going away from what android has been moving toward for a few months so there are a few issues with some android features. I personally think that the gains outweigh the losses in this, but depending on your device usage YMMV.
Multi-User: If you use multiple users on your device then this mod is probably not going to work well for you. In tests it seems that any user will get the notifications for all users. They can't be clicked but they do come through and can be seen.
Encryption: I have had a report that enabling Security/Encrypt tablet in conjunction with tabletUI mod will lead to a boot loop.
Notifications: Most notifications will work fine, however certain ones will not be seen:
Storage related notifications may not be seen. For instance the popup to enable mass storage when you plug into your computer.
Persistent Alarm Notification will not be seen when you have the alarm set.
Preferences: Sometimes certain options in Settings (having to do with appearance) will either no longer be present, or will have no effect when changed.
Launcher/Apps: On devices with smaller screens and lower resolutions the default launcher may not look very good after applying tabletUI mods. I recommend using a custom launcher from the play store, like Nova/Holo, which let you customize appearances. Also some apps may appear a little odd, or be missing content. This only affects small, low-res screens and is minimal.(see Youtube: missing/squished "Like"/"Subscribe" buttons)
Bugs/Requests:
If you have to report a failed attempt at patching a rom please include as much detail as you can, including the log from auto-patcher (full log please, not copy/paste of terminal output) and the rom and device you are trying to patch for (link to thread/source appreciated)
Please do not report failures for roms other than those stated as working in this thread; currently AOSP, CM10.1, and SlimBean.
Please do not post requests for support for roms which are not currently supported.
Be aware that some roms which are called "AOSP/AOSP based" are actually heavily modified by their developer already and these patches may fail in that case.
If you need to report an issue with some function that worked on your device before flashing the tabletUI mod but isn't working after, a log of the failure can be very helpful in coming to a solution, and is appreciated. Please check the Known Issues above before reporting.
Thanks/Credits
mateorod & pastime1971 for the amazingly versatile Auto-Patcher!
kobik77 for ApG which really makes the Auto-Patcher accessible for everyone!
barrmulio for all his work on tabletUI!
All the happy, willing testers: brGabriel, 138, 19cam92, dlumberg, astro_75, rraaka, tuxafgmur, and anyone else I am forgetting! Without you...:crying:!
All the awesome, talented developers on XDA that bring us these great roms for our devices! Thanks to each and every one of you for helping make this community what it is!
All my fellow tabletUI fans out there, who don't want to accept an awkward user interface!
Anyone else who has slipped my mind at the moment, and anyone who has ever contributed anything to XDA you're great too!:highfive:

Screenshots:
Galaxy Tab 2 7.0: CM10.1 (for more see here)
Galaxy Tab 2 7.0: SlimBean
Galaxy Tab 2 10.1: CM10.1 (for more see here)
Nexus 10: CM10.1
Nexus 10: AOSP
Asus Transformer TF101: CM10.1

one more just in case

Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss

i9apps said:
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
Click to expand...
Click to collapse
That's because there aren't patches for Team EOS roms. Right now your choices are either AOSP, CM10.1, or Slim.

"Recent Apps" style?
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".

SGH-i200 said:
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
Click to expand...
Click to collapse
Thank you for the report. I guess to be honest I don't really think of this as an "issue" but I guess that you are right. At best it is still a shortcoming in acheiving what you would expect as tabletUI. I will have to see if I can get it to look like in Honeycomb, where it was a column view, pushed to the left of the screen. That is the way that you mean, right?

@SGH-i200
I think that I got it all sorted out the way you would like. I will try to include this fix in the auto-patcher the next time I update the tabletUI patches. It does look better this way, thanks for the push!

Awesome work Caldair!

Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.

Didgesteve said:
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Click to expand...
Click to collapse
Sorry, I don't know anything about that. I saw your post at the auto-patcher main thread as well and I think you have the wrong impression. This thread is meant to be for discussion of the tabletUI mod part of the auto-patcher. Your question would be better in the main thread, and trust me, those guys are way smarter than me anyway.

Updates were just pulled into auto-patcher. ApG users can try the newest patches right now, otherwise you could pull from Mateor/auto-patcher on github or wait for the next auto-patcher release.
Huge thanks to tuxafgmur for all the work he did on streamlining these patches!:good::good:
These changes help reduce the extra load that tabletUI seems to put on the gpu!
Also fixed the 'latest' symlink in the CM patch so you should be able to use multiple auto-patcher mods together with tabletUI (ie. pdroid)
And I changed the appearance of the recent apps panel so it is more similar to the old style tablet recent apps (similar to the pictures I posted a couple posts back), hope you like it!

hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG

LQQKS said:
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
Click to expand...
Click to collapse
From the look of your log I think there is something wrong with your ApG installation.
I have never used ApG, as I don't use windows, so unfortunately I can't really be very helpful with this issue. But the patcher really should be working for that rom.
Maybe you could try completely removing ApG and starting fresh, that may help. I hope!

OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/

LQQKS said:
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
Click to expand...
Click to collapse
Glad to hear it!
And don't worry we all fall victim to the simplest mistakes. They are never simple until you find the solution, and they are usually the most frustrating to solve!
Thanks for sharing your success:highfive: I will add the Xoom to confirmed devices!

@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Edit: Well I got my feedback... and it was not good:crying: To make matters worse I have since read in one of the EOS threads that bigrushdog is working on bringing tabletUI back into these roms anyway, so I am just going to leave this for now. You EOS users should have your tabletUI back before you know it anyway!
ATTACHMENTS REMOVED.

Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.

Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.

drewski_1 said:
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Click to expand...
Click to collapse
Gatak said:
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
Click to expand...
Click to collapse
Thanks to you both for testing this! I am sorry that it failed so miserably and you had to wipe and reinstall.
For now I will take a closer look at the patches themselves and the sources. There is definitely more going on in EOS roms than other AOSP/based roms, especially in SystemUI.apk.
Gatak, I would have said your issue could have been caused by the fact that you tried to flash the update over a newer build than the modded files came from, but since drewski_1 had the same exact issue I think the patches are probably not right.
Drewski_1, I am assuming that you did flash the update on a wingray model and that you were running the corresponding build of the rom, dated 2013-05-04. If that is not the case, and you are also using a newer (or older) build, please let me know.
These patches can really screw up when used on different nightly (or weekly or whatever the build frequency is for EOS) builds than they were based on. Devs can change a lot in a week, and these patches contain important core files.
Thanks again to you both, I really want to get EOS working. I see how many downloads there are of these roms from goo.im, just for these 2 devices, so I know a lot of people would benefit from this.

[DEV][ROM][5.0.2][CM12] Lollipop for LG-P500

To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel

...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.

ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:

Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.

Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk

This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...

D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk

Wut? ART isn't compatible with ARMv6, AFAIK.

Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk

CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:

You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/

Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app

xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo

CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.

It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse

Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip

xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno

Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not

Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.

xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk

[ROM][6.0][MARSHMALLOW][CM13] Official CyanogenMod 13 for LG G2

Less official CM13 G2 information
Unofficial CM13 on LG G2 FAQ
The following FAQ is from me, the OP, and not from any CM officials or the device devs. I hope you all find it helpful.
What are the common problems? I'm pretty stupid and hate reading...
Users who don't seem to read: Please read the entire FAQ and don't pollute the thread with common questions. Use the "Search Thread" box at the top of the thread to look for your issue or issues like it.
Google apps force closing after an update: This is related to your choice of recovery, please read the recovery section.
WiFi disconnect while sleeping/screen off: This is not a G2 specific issue or even a CM specific issue. It's an Android issue. See: https://code.google.com/p/android/issues/detail?id=196035. Please do not pollute the forums with questions about it, at present there is no fix.
Which bootstack is recommended: None! No bootstack is recommended. Please read the section on best install method and then bootstacks to understand why you shouldn't do this.
Is it stable? I'm worried about trying new things...
Is it stable? Yes. I think it's as stable as a nightly can get. And that could change from night to night, so maybe watch the thread for a day or two and see what people are saying about the releases before installing them.
If you're worried about installing it for fear of, you know... whatever. Then don't install it. This isn't the place where I'm gonna convince you to try it. That's your decision. There's risk to everything. Understand and own the risk.
What is required for CM on the G2? What should my device have?
The required bootloader (aboot) for CM13 on the LG G2 is the KitKat (KK) bootloader. CM13 will fail to install otherwise. The minimum required bootstack (radios, laf, and other firmwares) is a KitKat (KK) bootstack, however a Lollipop (LP) bootstack will work and is preferred. CM-13.0 is bumped and thus does not require loki compatibility.
In order to have a successful update procedure, you will need a recovery that honors sepolicy. Please read the question on the recovery for further details and recommendations.
What is the best install method? Where do I start from?
The best starting point for installing this ROM is from an LG Stock Lollipop installation. While you could in fact install a Lollipop G2 bootstack and then install CM-13.0 on top of that, there's a good chance that it might fail or not work entirely well for you.
If you don't know or remember the history of ROMs on your phone, you may be much better off doing a full KDZ or TOT re-installation of LG Stock on your phone and take it all the way to Lollipop. Then proceed to root and autorec from there, upgrade your recovery and install CM. If you do this you will not require a bootstack and won't run the risks associated with installing one. Doing this sort of installation is beyond the scope of this thread. There are different files and starting points for each device. You will have to search for what works for you.
What about a bootstack? Should I use that if I don't want to update? What if I simply can't?
The recommended course of action is detailed above: return your phone to stock lollipop and then proceed to root your device and run autorec to install a recovery. If for whatever reason you simply cannot do that, whether it's because you can't or just won't, then the bootstack options are available. HOWEVER, this has led to problems for many people and is NOT recommended, not even by the devs that created them.
The bootstacks were created as a crutch for those unwilling or unable to upgrade their phones via kdz/tot or OTA methods. They update several key internal partitions for firmwares and keys and what not to bring the phone up to a base lollipop hardware standard. Not all are replaced, and the bootstacks don't do as good a job as LG's OTA's. This is why they can be problematic.
Issues: If you are absolutely set on installing a bootstack, the lg-devs recommend the lg-devs lollipop bootstack. However some people encounter problems with this as it creates a situation where the phone boots to a black screen and getting to recovery is difficult. If that's the case, you can consider installing Daniel Stuart's hybrid CAF bootstacks (or download direct from his GitHub). His bootstacks aren't recommended by the lg-devs, but they do seem to solve the issue of the black screen after boot.
A bootstack with loki support is not required for CM-13.0 to function. It is also not recommended unless you absolutely know you need it on your device. A bump-compatible bootstack is all that's necessary.
NOTE: The d803 never had an official stock Lollipop release and thus doesn't have an lg-devs LP bootstack. If your device is on a KK bootstack it should work fine, or you could use Daniel Stuart's bootstack which offers a hack to put lollipop firmwares on the d803.
IMPORTANT: If you install any of these bootstacks you run the REAL RISK of BRICKING YOUR DEVICE. Neither I, the G2 CM contributors, nor the CyanogenMod developers are responsible for anything you do to your device. Please proceed with caution before proceeding and have an understanding of what is necessary to recover your phone in case things go horribly wrong.
Which Recovery?
You need a recovery that honors sepolicy. Without that you will see Google applications force close after a CM update, and the only seeming way to fix it is to re-flash your chosen gapps. This is not a problem with a recovery that honors sepolicy properly.
The recommended recovery is Blastagator's TWRP, version 2.8.7.3 or newer. Older versions (2.8.7.1 or older) do not honor sepolicy. The CyanogenMod Recovery also works properly, and has for some time. However it is feature starved and lacks useful/advanced functions like backups or a file manager.
Do I need to install anything else? What is a Gapps?
CyanogenMod can be used standalone. However if you want things like Google's Play Store, Google Calendar Sync, and other Google services, you'll want to install a gapps zip package alongside CyanogenMod. I personally use OpenGapps but have also used SlimGapps in the past. For CM13 on the LG G2, you need a gapps for the ARM architecture and Android 6.0 (Marshmallow). Please read the entry about camera problems as it may affect your choice of Gapps.
Also, look at the FAQ entry for the recovery if you have FC issues.
In what order do I install this all?
The following is MY recommendation. It isn't necessarily law, but it works well for me. This assumes you have a custom recovery and have already booted into it. If you can't get that far, this is not the place for you to learn how. Please search XDA and look around for the relevant threads.
Suggested install order (the more emphasis I add to words, the more I want you to pay attention to them). One last tidbit of important information... The order chosen below was deliberate. I wouldn't recommend changing the order unless you know what you're doing. Here you go:
Recommended: Disconnect anything connected to your USB port, then boot into your recovery
Optional: Upgrade your recovery to the latest version
Install latest recovery zip file (Read recovery section for recommendations)
Reboot Recovery
Recommended: Do a full ROM backup, then copy the backup (and possibly your internal storage files) to your PC. The remaining steps have the potential to be destructive.
Optional, NOT Recommended: Install selected bootstack if deemed necessary
Read disclaimer above in the bootstacks section and make sure you know what you're doing
Re-read aforementioned disclaimer
Install bootstack of your choice
Reboot Recovery
Recommended: If coming from another ROM or CM 12.1, do a factory reset. CM will fail to install over another ROM's user data
Recommended: Wipe the system partition
Install the CyanogenMod zip
Optional: Install your chosen gapps package
Reboot your device and wait for first boot to complete
Need Root?
To enable the built in root on CyanogenMod you must enable Developer Options first. Go to Settings -> About phone and repeatedly press Build number until you are told you have enabled development settings. Then go to Settings -> Developer options, find the Root access option and change it to suit your needs.
My understanding about SuperSU is that it does not easily work with CM. The current "stable" version won't work and will likely cause a bootloop. Unless you've done quite a bit of research and know what you're doing, your best bet would be to stay away from SuperSU for this ROM.
Is OTG working? I can't see my attached device!
The OTG, to my knowledge (and personal experience), works. If you get a notification when you attach your OTG peripheral to your device, then OTG is working.
The PROBLEM is that Marshmallow (Android 6.0) does things differently with attached storage. Locations are all different from the way they were on previous versions of Android (Lollipop and earlier) and mount points are now auto-generated. Your chosen file manager must have been updated to work with the new 6.0 scheme. Not all of them have been.
For example, I just attached an OTG sdcard reader with an SD card inserted, and the storage was mounted at /mnt/media_rw/7E7B-0812
Helpful tip: An option is to go into the CM FileManager, navigate to /mnt/media_rw (or to your OTG device), press the Actions triplet menu in the lower left side and choose "Add to bookmarks." This should place the location into the bookmarks (when you press the hamburger menu or swipe in from the left) for easier access.
My camera doesn't seem to work!!!
We are limited to the proprietary camera libraries from LG for the G2. The latest of these is for Lollipop. That means any cameras that depend on the new Marshmallow API's to operate will fail to work properly (if at all) on our devices. A major example of this is the Nexus edition of the Google Camera. Sadly, this camera is included in many "Stock" editions of Gapps (including the popular OpenGapps distribution). To complicate matters, the "Stock" edition of these Gapps packages remove the stock AOSP/CM camera. AND because the camera is basically named for the Google Camera from the Play Store, you can't install the Play Store edition. Basically, you are stuck with a non-working camera as your only option unless you install something 3rd party.
To fix this problem you'll need to instruct your Gapps to avoid installing the "Stock" Google Camera. This will leave the AOSP/CM camera in place and allow you to install the Google Camera from the Play Store. Both of these options are preferable to the non-working Nexus edition of the Google Camera. The process is detailed in this post: http://forum.xda-developers.com/showpost.php?p=64666238&postcount=501
What about this Snap camera I've heard about?
The "Snap" camera is actually the SnapDragon camera from Qualcomm. It's optimized for qualcomm chipsets and so is faster and generally better on our hardware than other cameras. As of nightly 20160112 it is now built into the system as the default camera. You'll want read and follow the instructions in the above entry "My camera doesn't seem to work!!!" to make sure your Gapps doesn't replace it.
Bugs, I think I genuinely have them. What should I do?
Whine. Just whine and whine, no one will be annoyed at all. Actually, many people will be annoyed and there's a good chance I'll make fun of you.
The first thing you should actually do is to search this FAQ. Please read all the entries to make sure they really don't apply to you. Reading never killed anyone. If that doesn't turn up an answer, use the "Search this thread" box up at the top of the page and see if you can locate posts like yours on this thread. You may very well have a bug that others have solved, but please be mindful not to ask questions that have already been answered. Having to repeatedly answer the same questions over and over again is also rather annoying. If you really haven't found anything, then ask a question. Genuine bug reports are not uncommon and I'd like to see a little bit of a discussion before an official bug report goes in.
Finally, If you really think you have genuine bug, be it in CM generally or on the G2 specifically, you'll want to proceed to posting an official bug report on CyanogenMod's Jira. For more information on that, please read this handy post I made on how to post to Jira. Once you've done all of that, post a link to your bug report on this thread so we can all follow it.
My question isn't here... Should I private message you to ask?
No! I won't be answering any questions that are sent to me privately, UNLESS I have a previous relationship with you (if you are reading this and wondering if that means you... it probably doesn't mean you). The best you can hope for in a response is sarcasm and mockery. Ask your technical questions here, or search the thread. Or search XDA, because there are many problems that are not G2 specific. Hell, there are plenty of issues that aren't even CM specific. Google, or that search box up there... they are your friends.
Is there anyone I should thank?
Well, for me, its the people on this forum that answer questions for everyone else. Believe it or not, there are people reading this thread that DO NOT BOTHER TO READ THIS FAQ. They won't even search the thread to see if their issue has been discussed (ad nauseam) before. Yeah, they're annoying, they repeat questions, and some times they are just plain disrespectful. Usually my first instinct is to make fun of them and be as unhelpful as I can be. But I wait, and these aforementioned saints swoop in and provide help. So thank you helpful forum people. I do really appreciate it

Cm 13 for 800 and 802 are not released yet. OP - please present info about prerequisites like which bootloader or bootstack to install before.

Radac Stunghthumz said:
Cm 13 for 800 and 802 are not released yet. OP - please present info about prerequisites like which bootloader or bootstack to install before.
Click to expand...
Click to collapse
I supposed you missed the part of the post at the bottom that says it's a work in progress. The binaries for 13 were already run for the day, I figure I have till tomorrow morning before the d800 and 802 (and 803) nightlies show up and thus have to have a more complete post. Thanks for your patience.

dr4stic said:
I supposed you missed the part of the post at the bottom that says it's a work in progress. The binaries for 13 were already run for the day, I figure I have till tomorrow morning before the d800 and 802 (and 803) nightlies show up and thus have to have a more complete post. Thanks for your patience.
Click to expand...
Click to collapse
Woo hoo. Eagerly waiting. Great work CM team.
Sent from my LG-D800 using Tapatalk

epapsiou said:
Woo hoo. Eagerly waiting. Great work CM team.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Looks like I was wrong... builds are up.

Radac Stunghthumz said:
Cm 13 for 800 and 802 are not released yet. OP - please present info about prerequisites like which bootloader or bootstack to install before.
Click to expand...
Click to collapse
it's up now for D802
d802
Date Added: 2015-12-06 00:49:07
nightly Download: cm-13.0-20151206-NIGHTLY-d802.zip (296.43 MB)
sha1: 3dd09b76c4efa6eb8375162e7b2676286b68a268
Download: cm-13.0-20151206-NIGHTLY-d802-recovery.img
sha1: 45a62f3c17e922054cf18b624ab6d1b49c7c0ed9 2015-12-06 00:49:07
Click to expand...
Click to collapse
dr4stic said:
Looks like I was wrong... builds are up.
Click to expand...
Click to collapse
Thanks Mate!

OK Google voice search not working from Homescreen and OTG still broken apart from in TWRP.
Apart from that all looks good
Sent from my LG-D802 using Tapatalk

Treboeth said:
OK Google voice search not working from Homescreen and OTG still broken apart from in TWRP.
Click to expand...
Click to collapse
OK Google works for me on the home screen. Have you tried initiating it once by pressing on the mic icon? with 6.0's new permission model, Google's search app needs mic access permission before it can do anything. Maybe that's the key?
Tested OTG and adding it to the list of not working things

If I install Apex launcher OK works from the Home screen but doesn't work with Trebuchet.
Tried initiating but no go.
Clean install ie complete format in TWRP d802.
Edit.
Wiped and reinstalled works OK now [emoji4]
Sent from my LG-D802 using Tapatalk

@dr4stic
LTE cannot be disabled to the list of bugs?

chewdaniel said:
@dr4stic
LTE cannot be disabled to the list of bugs?
Click to expand...
Click to collapse
You are right... though it's an explainable bug, seems related to using the LP libril. Unlikely to be fixed, sadly

Great to see official cm13 ☺
Is anyone else getting slow charging?

Am getting a black screen after LG logo appears momentarily at bootup. D802 with lg-dev's 30d Bump LP bootloader already installed.
Have gone back to CM12.1 after returning to recovery via long-pressing PWR + VOL- buttons.
Anyone knows how to get CM13 to boot up properly in my situation? Thanks.

kaninabu said:
Am getting a black screen after LG logo appears momentarily at bootup. D802 with lg-dev's 30d Bump LP bootloader already installed.
Have gone back to CM12.1 after returning to recovery via long-pressing PWR + VOL- buttons.
Anyone knows how to get CM13 to boot up properly in my situation? Thanks.
Click to expand...
Click to collapse
Same issue here on D802.
I made a complete clean install (Wiped cache, dalvik, system & data) but CM13 won't boot.
After LG Logo it's only a black screen. I waited for about 20 minutes. But nothing happened :-/
I tried also to install it with an without Gapps, but made no difference. ROM just won't boot.
I'm back on 12.1 also for now

C--Mon said:
Same issue here on D802.
I made a complete clean install (Wipe cache. dalvik system & data) but CM13 won't boot.
After LG Logo it's only a black screen. I waited for abaout 20 minutes. But nothing happened :-/
Click to expand...
Click to collapse
Found the fix. I tried restoring just the working Boot partition from the working CM12.1 backup in TWRP after installing CM13 zip, and now it progresses to the CM boot animation. Seems like the 12-06 D802 CM13 zip messes up the Boot partition?
EDIT: Stuck at CM boot animation for 10min - back to CM12.1 for now.

Same here.. after installing CM13 on previous CM12.1 only LG logo and then black screen.
I used CAF bootstack and everything is ok on my D802.. CM13 boots.
http://danielstuart.tk/d80x.html
Dirty flash on previous CM12.1 works too..

brrrrm said:
Same here.. after installing CM13 on previous CM12.1 only LG logo and then black screen.
I used CAF bootstack and everything is ok on my D802.. CM13 boots.
http://danielstuart.tk/d80x.html
Dirty flash on previous CM12.1 works too..
Click to expand...
Click to collapse
Confirmed this works. Have progressed into "Android is starting..." screen using this method. Suggest that this info should be added to the first few posts.

Thanks, It realy works after flashing CAF Bootstack from Daniel Stuart

What gapps did you use? And what package?
Enviado desde mi LG-D802 mediante Tapatalk

[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!

[XZ][F8331/2] AOSP Pie builds [Stable] [Updates]

New build up at sx.ix5.org, use version 2018-10-30.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
XDA:DevDB Information
AOSP Pie based on Sony Open Devices Project, ROM for the Sony Xperia XZ
Contributors
local__hero, fastbooking, oshmoun
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2018-11-09
Last Updated 2019-05-17

Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
Don't make me ask you for logs every time!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!

---
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
---

In 9.11
1. Everything still works
2. Charging with plugged at screen off works
3. On gcam portrait mode and night photo gives purple glitched image
And phone seems to be faster.

Bug: 9.11 with oem v2- Clean install
- Hotspot not working
- Phone call issue - Mic and speaker not working, cannot hear anything or say anything << Listed in the bug
- Top speaker not working
Still testing.

An update
Yes, we know calling is kinda broken right now on both oem versions. Yes, we know you have problems with dualsim devices because you didn't flash the dualsim patcher. Yes, battery life isn't very good because we are testing out some increased CPU frequencies so video doesn't stutter. (you can go back to the 11-05 build which has the old CPU freqs and compare).
We're aware of a lot of these issues, and they are all tracked in the current buglist (see post #2).
Development happens mostly in the Sony open devices program, with a few heroic volunteers contributing. Right now, a lot of work is being done to get the current flagships(think XZ2, XZ3) to a semi-stable state, but work for our device is done as well.
You can check progress in the sonyxperiadev repos. E.g. recently, some changes to the telephony HAL integration have been made, see the common device repo.
Why is it taking so long to fix all this?
Sony buys many of their processors from Qualcomm. Lots of stuff in phones is proprietary and covered in patents, and you can only get the source code if you sign an NDA. So even if Sony wanted to, they could not release the source for a lot of things.
See all the files with the name "qti" in them? That's Qualcomm Technologies, Inc. See all the repos named something like "qcom-something-something"? That's Qualcomm.
When there's a problem, we have to report it to Sony, who report it to Qualcomm. This takes time already. And don't forget Qualcomm has suppliers as well, and so on and so on. The same is true for other parts, e.g. the Wi-Fi chips are from Broadcom.
Then, support for hardware stuff is on many levels. A lot of low-level drivers that are driving the hardware are on the /odm partition(the one that the oemv1/v2 blobs get flashed to). Then there is work to be done tweaking the actual hardware abstraction layer(HAL) interfaces that work with these driver blobs. Then there are kernel drivers that can go wrong and mess up. Then it can be a problem somewhere higher up in the Android frameworks. Lots of detective work.
If new blobs from Qualcomm come out, Sony itself needs to do some testing, and then releases a new oem version. It won't just magically work, we need to tweak the SODP vendor side as well. It could be as easy as changing a version to a newer one, but it could also be a lot harder. The sonyxperiadev crew knows what's needed to integrate these new blobs, but it still takes time and testing.
Qualcomm provide the a lot of the source code to work with their hardware and blobs from the higher-level Android side in their CodeAurora forum (CAF) repositories. The relevant changes then get merged into the sonyxperiadev repos and we can test if it works(or if something new is broken...).
For more info, read the Android documentation on hardware etc.
The chip in our phone, the MSM8996, is quite old already(even the SDM845 in the XZ2/3 is already quite old in processor standards). We can be luck that Qualcomm still provides support. But it's not a priority to them, they want to sell new
ones of course. That is also a reason updates can take longer.
Regarding full forced-reboot crashes:
Sadly, as of now, for some people the "/sys/fs/pstore" folder does not get populated after a crash. This is important to diagnose what happened.
You can apply this patch to force a kernel panic on every reboot, but I would recommend that you do
so only if you know what you are doing.
Regarding battery life:
Please install BetterBatteryStats
and find out what is draining the battery.
This could really help us out! But first, make sure you are not running any GApps, because the Google Mobile Services are a massive pile of battery drain.
If you absolutely have to use GApps, please run only the "pico" GApps version!
---
About the posts here:
Like 90% of posts here and in the old thread are full of people who just plain refuse to read, asking how to install or demanding someone help them out with something that has already been answered time and time again. This makes it extremely annoying for the us who have to scroll through pages of useless stuff to find the genuine bug reports. You do realize this site is literally named "xda-developers", right? If you're unclear on the concept, please read this: https://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
"This doesn't work!" - "This thing crashes!" - That gives us almost no clue what is happening. We need logs, or we can't do anything about it. I have only one phone, and I only use the stock ROM. There are a lot of nice testers who send others and me helpful bug reports, with detailed explanations in what circumstances it occured, with proper logs.
With that info, the Sony open devices team and us can actually look into issues.
So please, if something doesn't work AND we are not aware of it yet, post it to the bug list (not here!) and attach a link to a log that you uploaded, e.g. to a service like hastebin.com.
nhicko95 said:
how is battery life?
Click to expand...
Click to collapse
Test it out, please. And don't forget to report the diagnosed battery stats.
DarkPrinciple said:
I should be able to get to 12 lunch with my battery being more than 50%
Click to expand...
Click to collapse
I've tweaked for more performance right now, but you can use 11-05 to get old CPU freqs. Also, please help hunt down what is draining the battery, it's most likely too many held wakelocks, but it could be any number of things.
bihslk said:
So what is the latest and best working version of this rom?
Click to expand...
Click to collapse
It's literally in the first post.
bihslk said:
Rom is pretty OK but really annoying top speaker bug. Only lower one works.
Click to expand...
Click to collapse
That is already in the bug list. Please read the bug list before posting.

Update 2018-11-16
Some new developments are happening.
Oem binaries version 3 are out. This should give improved power management. The SODP team has also worked on getting audio handling during calls to work. A big thanks to oshmoun for his work on the audio manager. This change was introduced on the 11-15 build. The issue of no call audio when a bluetooth headset is connected is still present as of now.
Changed IRQ handling (PR by Angelo/"kholk"). This should give better battery life and maybe faster wakeup from deep sleep. But could also lead to instabilities and crashes. Send logs & pstore, see post #2. This change was introduced on the 11-15 build.
Testing kernel 4.9.137 i in progress (we are currently on .103). This means stability and security enhancements from upstream linux. Thanks to Nathan Chance who opened this pull request..
But some of those upstream changes might be incompatible with our Sony kernel, so we have to test that. Send logs & pstore, see post #2. This change was introduced in the 11-16 build. If the 11-15 and 11-16 builds are unstable, revert to an older one. But please be brave and run them for at least a day to get us logs of potential crashes.
---
optixperiaa said:
I am always confused about "flash latest stock ftf" part about roms as a newbie.. if we flash sony's ftf how can we flash rom ? isnt it overwrite ?
Click to expand...
Click to collapse
Your phone software is made up of many layers. The ROMs like omni or this AOSP-based one only modify your /system and /boot partitions.
But when you update your stock firmware via flashtool, you also update your phone modem firmware, your qnovo charging controller firmware, your lower-level bootloaders etc. That is why we instruct you to update to the latest stock firmware. You could theoretically skip flashing /system in flashtool(because it will get overwritten anyway, as you've already discovered) and directly flash a custom ROM afterwards.
When you're coming from omni, there is no need to flash stock firmware again in between, because your other partitions stay the same. Just a new /oem is needed.

viori said:
flash omni_kagura-2018-11-20_UNOFFICIAL_TESTBUILD-2
Click to expand...
Click to collapse
Again, please keep this thread about development for AOSP. The omni builds are not meant for you.
If you have trouble installing then simply don't use it.
DO NOT POST HERE FOR HELP OR YOU WILL BE REPORTED. Read everything before posting.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332

The OP has requested that you do not post questions in this thread, please use the thread he states in the OP to do that.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
Click to expand...
Click to collapse
Thanks
Thread cleaned

General update
Newer builds will have selinux set to "enforcing". Most denials should have been fixed or are irrelevant. If you encounter any problems, selinux-related or anything else, please report them to the Sony bugtracker or - even better - submit a pull request to the selinux-policy repo.
Update 1: vendor blobs aren't binderized correctly atm, so no network. You can set selinux back to permissive to fix most issues atm.
The Wi-Fi hotspot has been fixed thanks to oshmoun. In newer builds, it should be using less battery.
Next thing we're going to tackle is deep sleep and battery drain. Big pain point and one of the last blockers, apart from the camera and bluetooth in-call audio.
You might have noticed that the omnirom device trees have been updated to 9.0. Nightly testing builds work fine, but they have the same issues as the AOSP-based ones.
Work is also under way to get a Pie-based TWRP recovery stable, with support for FDE encryption(this means that you will be able to back up your encrypted installations). Mounting /userdata works, but the builds are not ready for public release yet.

Update
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.

local__hero said:
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
Click to expand...
Click to collapse
Great job.
I already built a custom Pie kernel about a week ago to gain better performance but the charging bug was driving me insane :crying:
I guess now's the time to go back to the mighty Pie and try building a nice and hopefully stable Marrow Kernel.
Cheers

Finally a new build is out!

I can't pass safety net on latest build.
Any ideas what should I use ?
Since modules for spoofing fingerprint simply don't work.
I tried universal safety net fix but with no avail.

V 12.15
Charging working fine. But i have problem with camera, photos are very dark.

Sometimes touch screen not working and i need to switch the screen and on again.

ov2rey said:
Sometimes touch screen not working and i need to switch the screen and on again.
Click to expand...
Click to collapse
Disable Dt2w

oem v4 is out

DahakePL said:
Disable Dt2w
Click to expand...
Click to collapse
Thank you It's work!
Layns said:
oem v4 is out
Click to expand...
Click to collapse
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/

ov2rey said:
Thank you It's work!
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
Click to expand...
Click to collapse
I tried it works fine but the camera sucks and the sound is bad, the screen opening with double tap is running slow, the charge is a little quick

Database Develop

welcome