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

[ROM][6.0][MARSHMALLOW][CM13] Official CyanogenMod 13 for LG G2 - G2 Original Android Development

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

Related

[ROM][4.3][JSS15J] CyanogenMod 10.2 Unofficial Nightly Builds

Unofficial CM 10.2 builds for Nexus 4
Hi all,
I decided to post my unofficial builds of CM10.2 for Nexus 4 after being asked by a few people in the CM10.1 Q&A and development threads, in order to consolidate questions and keep clutter down in those threads I decided it was best to make a thread specifically for these builds.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
How to install:
First time installing or coming from another 4.3 based ROM:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Wipe data/Factory reset
Flash the ROM
Flash Gapps
Reboot
Coming from a previous CM10.2 nightly:
Download the ROM
Reboot into recovery
Flash the ROM
Reboot
Coming from a previous CM10.1 nightly:
Download the ROM
Download a compatible 4.3 Gapps package (I have been using Banks gapps from here: http://forum.xda-developers.com/showthread.php?t=2012857)
Reboot into recovery
Flash the ROM
Flash Gapps
Reboot
Builds:
Built from official CM sources only, no cherry-picks, no changes, no additions. I will not be changing the official sources in any way so don't bother asking.
http://goo.im/devs/thracemerin/cm_builds/mako
Note: These builds are produced by my buildbot at 4am US Eastern time (build + upload takes approximately 90 minutes), the repo will be synced during the build process to ensure that the latest sources are used. The completed file size should be approximately 196MB, so if the latest download isn't it's not fully uploaded yet
Note 2: If the build fails for some reason, I will try to build one later in the day, but if I can't you may have to wait until the following day.
How to get root:
In order to get root access, you need to do the following:
Activate the Developer Settings by going to Settings->About Phone ant tap on the Build Number 7 times.
Go to Settings->Developer Options and change the Root Access to 'Apps and ADB'
You may also need to activate USB Debugging in Developer Options (some people say you do, others say you don't)
Note: If you have flashed a kernel that comes with it's own boot.img package it may not have the correct instructions to start the internal su daemon as a result root will stop working, at the moment the best way to fix this is to not use that kernel. If you absolutely have to use a custom kernel you may need to flash SuperSU for the moment or ask your kernel dev to support this feature.
Known Issues
None that I'm aware of, but keep in mind that these are pre-nightly builds and could contain bugs and/or non-working features at any time.
Thanks
Google
CyanogenMod

F.A.Q
Q: When will official builds start?
A: Soon
CyanogenMod Blog said:
“Who cares about the old, gimme 10.2!”
We have one last internal item on our checklist before we open the floodgates on CM 10.2 nightlies. We fell into an old habit in 10.1 and the settings menu became more cluttered than we would like, and at times confusing both in presentation and in code. We are working to resolve this before 10.2 nightlies begin, so the transition is less jarring than it would down the line. Expect the new layout to be in effect with the first nightlies. If all goes well, we are talking days, not weeks.
In the meantime, the majority of our 10.1 roster have transitioned to being 10.2 capable. This means for you at-home builders, things should be in a fairly good spot for your own personal builds. If you want to checkout all the stuff we’ve merged, click through the pages.
Click to expand...
Click to collapse
Q: What is SELinux?
A:
CyanogenMod Blog said:
What is SELinux?
The project’s official description reads “SELinux is a security enhancement to Linux which allows users and administrators more control over access control.”
SELinux is a set of Open sourced and peer reviewed changes to the core Android Software stack to help prevent apps from performing malicious activities. This is done by establishing a set of policies that act as mandatory access controls (MAC). Depending on the policy, it can do things such as prevent apps from running or accessing specific data, to preventing root access altogether.
SELinux has wide-scale adoption throughout the linux landscape, with Fedora, Red Hat and others incorporating policies to better the system security. The default policies are usually written per distribution, by their maintainers – we have begun this process for CyanogenMod.
We will be working on this policy creation in parallel to Google’s own policies for Android, which we believe will be released with the Android 4.3 source; effectively getting us ahead of the eventual 4.3 source release. As this process is open source, policy creation and suggestions will be handled via our gerrit instance.
What it’s not?
SELinux is not a backdoor for government agencies to spy on you. It is not PRISM, PROMIS, CARNIVORE, The Great Firewall or any other ominous Big Brother-like initiative.
Access Control Modes
By default, we will be shipping with SELinux capabilities enabled in the kernel, but in a Permissive mode. What this means is that your phone will behave exactly as it currently does, with no noticeable change to the user.
There are 3 modes in total, Enforcing, Permissive and Disabled. While in Enforcing mode, SELinux policies are enforced, preventing whatever causes a violation (ie su). Permissive mode logs policy violations, but does not prevent the activity that caused it. Disabled turns SELinux off.
We are using Permissive mode as our default so we can come up with sensible policies. If you submit a log for us to analyze (via JIRA) for SELinux policy improvements, the logged exceptions will be of high value.
This will be an ongoing process as we work to incorporate sensible policies for each device repo. As always our source is available on Github and patches will be peer reviewed via gerrit. For those more attuned to personal data security, you are welcome to watch and audit our efforts. For the rest of you, sit back and relax – no need for pitchforks.
Click to expand...
Click to collapse

Third

amazing mate, keep it up the good work!

Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?

Feedback
Nice man, thanks for this work, btw, the front cam is upside down.

floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
BaNkS only includes the essential Google Apps that are needed for the Google experience -- working sync services, the Play Store itself, and so on. He provides other Google Apps in the form of an add-on, a separate zip, for the keyboard/camera/etc. Basically, most of the Google Apps are now available to download from the store itself (Keep, Earth, Maps, Voice Search, Search and so on). That wasn't always the case, but still some are releasing a full Google Apps package with everything.
The minimalistic approach is obvious - only install what is necessary, manually get anything else yourself. That is why the banks package is small because it is not forcing other apps that people may or may not use since they could simply download it themselves if they wanted to. I assume the 200mb or more package is simply every single Google APK that comes with the official factory images.

lwkkazz said:
Nice man, thanks for this work, btw, the front cam is upside down.
Click to expand...
Click to collapse
Weird, doesn't seem to be for me.

floepie said:
Hey, thanks for the builds. Do you have any idea in your great widsom as to why the various Gapps packages vary in size to such a great extent?
First, we have Banks, which is extremely minimalist, at least when compared to official 10.1 Gapps.
Then, we have a 10.2 un-authored Gapps package, often linked in the CM discussion, which is about the size of the official 10.1 one, but seems to require Banks's photosphere add-on.
Lastly we have doomed's version which approaches a whopping 200 MBs.
What on earth can account for such varying sizes, and as the purist that I think you are, why do you use the minimalist Banks Gapps?
Click to expand...
Click to collapse
markd0wn basically covered it, but it also depends on what you want in your /system directory, most of the apps that used to come in Gapps packages are now available in the Play Store as stand alone packages so you can still get them if you want them and they get installed as user apps instead of system apps, not that it makes a tremendous difference, but for the most part they don't need to be in /system.

thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)

lwkkazz said:
It's ok now , Hey man, it is normal that the ROM occupy 4Gb of the memory? (I'm new to Nexus 4, I get my yesterday haha)
Click to expand...
Click to collapse
Android reserves around 4GB of the total space on the device. Yes, it is quite normal.
Glad I picked up the 16GB model.

thracemerin said:
Weird, doesn't seem to be for me.
Click to expand...
Click to collapse
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4

l.m.prowse said:
My front facing cam is upside down using focal, but in the stock app its fine
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Hmm....it's early for focal still, probably just an oddity.

@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.

markd0wn said:
@thracemerin, any way to know if the CM team are aware of the homescreen shortcut bug? maybe I should search JIRA for it... since I'm not sure they follow all threads here. Doesn't seem to happen to everyone though. Happens to me in every unofficial 10.2 build (gonna try yours now after full wipe). The only thing I'm changing is the number of homescreens from the default of 5 to less (for example 2). After that, it's very easy to reproduce - simply add a few apps from the drawer to the homescreen, also put some apps in folders, then reboot, and you'll see what I'm talking about (in case you don't already know). It also happens randomly without reboots, maybe when Trebuchet is refreshing itself or something, but reboot forces it to happen quicker.
Click to expand...
Click to collapse
I heard about it, but I always use Apex Launcher so it doesn't happen to me. I'm not sure they want you to put things for 10.2 on JIRA or not (probably not) but its a fairly serious thing, so you could try logging it, worst case they ignore it.

thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.

nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium

nighthawkca said:
thanks for posting this thracemerin. I've started my own builds (mostly for fun, to see if I could!), but I wanted to try some known good 4.2 builds before I flash one of my own. Your build and instructions are great. It's running smooth except for two things:
- I can't get my titanium backups to restore user apps, it just hangs at 0%. No big deal, I've just been installing from play store manually.
- Installing swype gives an error -24 . I did a clean install of your CM build, so data was wiped; there is nothing from nuance in data/data to wipe. This may or may not be related to the error with TiBu because it also was trying to install swype from a backup. I guess I'll play with the stock keyboard for a while.
thanks again.
Click to expand...
Click to collapse
Thanks to DJLamontagneIII for this:
Titanium backup Users
1. In tb go to menu>preferences>backup folder location
2. Navigate to storage/emulated/legacy
3. Select your Backup folder and Select "Use the current folder"
4. Then it will ask you to move backup to that folder.... Select that
5. Restart app and restore.
jpreichart said:
For the titanium backup problem, I switched the backup folder to the legacy selection in the preference menu and was then able to restore. Hope that helps
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Beat me to it

Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )

markd0wn said:
Another bug that I think is introduced in the 08-11 build is lockscreen slider shortcuts not saving (but if you changed them on a previous build and updated to 08-11, they'd probably be set up right).
I managed to save them anyway using a workaround. Basically setting them all as 'Empty' and hitting the save button won't do - you'd turn screen off/on and it will still have the default ones. What I did to 'fix' this is set each one to empty and tap save inbetween changing each one, then tap save again after they're all empty, then I tapped the icon that restores all to default, suddenly the 'default' is what I just set up (all empty), then hit save again, and voila, saved successfully. Could probably skip a few of those steps that I did as I'm sure one of them did the trick and the others were just me testing, but at least it works.
Another thing that confirms that they're changing something related to lockscreen shortcuts, is that after achieving this, the lockscreen is now stock-style-behavior. Before, when you set all shortcuts to empty, pressing and holding the lock icon would let you drag it to each spot that became empty but it still appeared as an "empty shortcut". Now, you don't see the spots where shortcuts would normally be, it's just all a circle.
(I'm reporting all of this just in case it helps someone )
Click to expand...
Click to collapse
They're doing a fairly significant reworking of the entire settings apk and all of the CyanogenMod settings, it's possible something got added/removed that broke this temporarily. I would expect that certain settings menus, etc... may be broken over the next little while before the official nightlies begin.

[ROM][5.{0,1}][AOSP][{Un,}Official] CM12.{0,1} (Lollipop)

CM12.{0,1} (Lollipop) official/unofficial builds for the Droid 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0/5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
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.
All 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.
These are WIP builds of porting CM12.{0,1} to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Last official build:
http://droid.cs.fau.de/cm-12.1/official/
Old manual builds:
http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2015-04-16:
Switched CM build-target, new nightlies will now be 12.1: http://review.cyanogenmod.org/#/c/94693/
2015-02-01:
No more unofficial builds! See: http://review.cyanogenmod.org/#/c/87596/
2015-01-28:
Mobile data fixes
Remaining com.android.phone crashes on VZW finally fixed (thanks @joojoobee666)
2015-01-24:
Fixed sw-keyboard popup when hw-keyboard is used (thanks @joojoobee666)
Fixed reboot to recovery
Fixed sepolicy for whisperd (dock service)
2015-01-22:
Fixed su-permissions
Crashes on Verizon most likely fixed, please report back
2015-01-20:
Fixed flashlight
2015-01-18:
SELinux updates.
This requires manual action for applications to continue being able to access their own files when upgrading from 2014-01-14 or 2014-01-15 (older versions are fine)!
Due to SELinux-bugs in 2014-01-1{4,5}, you have to relabel your data-partition on the first boot when upgrading from 2014-01-14/-15. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) and execute via an adb shell:
Code:
su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'
2015-01-1{4,5}:
More fixes for {,umts_}spyder
sepolicy updates
GSM fixes
notable CM changes: su integration fixed
2015-01-11:
Updated SELinux policies (mostly for spyder/umts_spyder)
Added kernel stability fixes
Video decoding fixes
2015-01-09:
Enabled SELinux enforcing
Add SELinux-policies for motorola services
Enable ro.telephony.get_imsi_from_sim on VZW devices (thanks @joojoobee666)
2015-01-02:
Sync CM changes
2014-12-23:
Fixed stock camera
2014-12-22:
Sync CM changes
Fix build due to P2P changes (fix pushed into CM)
Enabled security for adb (keys/not root by default)
2014-11-30:
Added APN fixes for CDMA/LTE
Enabled multiuser mode (might not work yet)
Last update for a couple of weeks
2014-11-27:
Fixed graphics glitches
2014-11-26:
Fixed HW video-decoding
Enabled doze mode (no pickup sensor in the devices!)
CM resync as always
2014-11-23:
Probably fixed mobile data on LTE
Fixed WiFi-tethering
2014-11-22:
Requires a recovery supporting SELinux
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data (at least on GSM/UMTS in Europe)
WiFi
WiFi-tethering
GPS
Camera
Playback of DRM-protected content (using Widevine from OnePlusOne)
What's not working:
Probably most everything else, including, but not limited to:
Some connectivity issues (should be solved now)
Data encryption
Gapps (CM-12.0):
Dhacker29 provides gapps for Lollipop:
http://d-h.st/YQG
http://d-h.st/jzr
http://droid.cs.fau.de/cm-12.0/gapps/ (Mirror)
Gapps (CM-12.1):
https://github.com/cgapps/vendor_google/releases/
Installation:
You need a new recovery supporting SELinux
An updated Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
To use this CM12.{0,1}-ROM on GSM-networks you should install Mentor.37's GSM patch
Source / Repositories:
maserati device-support: https://github.com/CyanogenMod/android_device_motorola_maserati
omap4-common device-support: https://github.com/CyanogenMod/android_device_motorola_omap4-common
omap4-common kernel: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common
local manifest to build cm-12 for the Droid 4: http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/local_manifest.xml
XDA:DevDB Information
CM 12.{0,1} on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2016-02-16

thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Once again, thank you so much for your efforts in keeping this device alive.

sharptv said:
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Click to expand...
Click to collapse
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Click to expand...
Click to collapse
No, data encryption is not enabled by default (and still doesn't even work for us).
Cheers,
Michael

Flipping sweet thanks y'all rock i love xda

Cast Screen
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!

G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)

gabhroo123 said:
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
Click to expand...
Click to collapse
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[

Shobai said:
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
Click to expand...
Click to collapse
assuming that cm11 is currently installed in your stock slot and you want to update to the new test safestrap by stargo:
uninstall the existing safestrap using the original safestrap, for instance, if the existing safestrap is 3.73, you should install safestrap 3.73 and uninstall the recovery.
DO NOT REBOOT YOUR PHONE IN THE PROCESS
after you have uninstalled the existing recovery, uninstall safestrap(3.73), and then install the new safestrap by stargo, and install the recovery.
your safestrap is now updated, and nothing will be wiped.
YOU MUST NOT REBOOT YOUR PHONE DURING THE PROCESS, you can only reboot after a recovery has been installed.
hope you find this useful

thelolotov said:
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Click to expand...
Click to collapse
It need some kernel changes... but it should work...original gnex have the same cpu/gpu and they make it work... @lucize was seeing that but i dont know what happend with that
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
By the way....thanks michael for your great work!...please make a donation link to send you some beer money!

Cheers, sharptv, much obliged =)

gabhroo123 said:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Click to expand...
Click to collapse
Yes, our GPU driver does not support WFD. And in contrast to the GNEX, Motorola added much stuff to our version, so it's not easy to sync it back with the upstream kernel. Last time I tried that, I ended up with a non-working display and couldn't figure out why...
Shobai said:
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Click to expand...
Click to collapse
Just boot to whatever you currently have installed in the stock slot. And I have to underline what @sharptv said, never reboot your phone in the process (it might work when you have the stock ROM in the stock slot, but it will surely break in every other case).
Cheers,
Michael

Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.

This App Camera work fine: https://play.google.com/store/apps/details?id=com.radcam.camera
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
sharptv said:
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
Click to expand...
Click to collapse
See this thread: http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
Download and install with recovery

I can confirm that at least on my phone that LTE is working. Great work .

flash these zips in recovery for root i got the from my nexus 7 root toolkit
HOPE IT WORKS FOR YOU :good::cyclops:

TheXG6HD said:
I can confirm that at least on my phone that LTE is working. Great work .
Click to expand...
Click to collapse
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael

stargo said:
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
Click to expand...
Click to collapse
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.

thelolotov said:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
Click to expand...
Click to collapse
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael

stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
LTE was working on first build, just took 10+ mins to connect then worked good.
Sent from my XT907 using Tapatalk

stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.

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

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

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

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

Fuq yeah! Great news!

D801 version working great.

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

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

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

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

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

Is the old random vibration bug exist ?

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

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

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

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

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

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

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

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

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

[ROM][AOSP][4.4/6.0/7.1] Unlegacy Android Project

The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22

GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.

Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?

Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining

Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?

Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.

Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...

radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.

Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!

pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.

Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"

Screeshots

Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks

Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:

Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?

Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.

@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~

Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.

mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...

Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?

[SM-T700] [KLIMTWIFI] All-in-one mirror of files for the Galaxy Tab S 8.4 Wi-Fi

Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.

CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...

prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror

CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.

prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.

CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?

prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews

CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..

prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!

CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...

prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.

Thank you kindly!

lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!

CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!

Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!

darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then

darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.

CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!

These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna

I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks

Database Develop

welcome