yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] lakyljuk:
Updated settings you posted about quick battery mode and ondemand governor - this is what you changed from your previous settings you posted a few pages back? These cpu governor tunable frequencies should we set as you mentioned earlier and plus change governor to ondemand and set new minimum? Thanks.
[G2 Original Android Development] migueldbr:
these are a whole new settings. Those i posted a while back were an adaptation to our device from a guide that was made for the Nexus 5x using interactive governor (and it may lack some adjustements since i am not an expert).

These settings where you change battery mode to quick and governor to ondemand are a completely different situation. If you made those changes i posted earlier regarding interactive governor, just untick the apply settings on boot and reboot and all configs will go back to normal. Then you can proceed to edit the new settings. I am still experimenting with this stuff, but the ondemand based config seems to be the best for me at least.

It is important that you set battery mode to quick before every other new change, because if you dont set the min frequency back to 300mhz, on quick mode you will have a min freq of 1190mhz which will drain a lot of battery
[G2 Original Android Development] desiresiscool:
I was able to fix without going back to stock by flashing hybrid bootstacks, thanks for advice anyway
[G2 Original Android Development] alexx_kidd:
would you be kind enough to share your configurations with us?
[G2 Original Android Development] lakyljuk:
Hi, thanks for a quick reply. I tried previous settings and after two days I got feeling it saved some battery life while maintaining performance. Those new settings are aimed to the same goal to save battery or to increase performance while keep battery the same? Thanks.
[G2 Original Android Development] migueldbr:
the previous settings(based on interactive) were trying exactly that, to retain performance while saving some battery, because unlike ondemand, interactive was tuned to perform @ selected frequencies (i mentioned them in the config) and keeping the tasks smooth at those frequencies, unlike ondemand, which has a tendency of going to higher frequencies and then go back to idle frequency.

So, to sum it up, the new ondemand config will maybe give you a little better performance at the cost of some minor battery life (but i need to keep testing the config to be 100% sure).

If you feel like the interactive governor settings retained performance while saving some battery then you should probably stay on them. Or try this new config and see what you think=p
[G2 Original Android Development] wuinder:
Thank you for the answer, i want to help for make better rom for the lg g2 reporting issues..

i want to say that another problem is with the WIFI in mode sleep, the wifi is off when the phone is suspended 10 minutes or more, but i have in advanced options "keep WIFI ON during sleep" in ALWAYS. the app like bbm is not connected in suspended mode for me, then another app like whatsapp dont work in mode sleep because the wifi turn off .. when the phone is awake bbm is connected again. have a good day
[G2 Original Android Development] suresh86:
I have been following this thread for quite a some time and i want to install it over stock kitkat on my Canadian G2.

However, few issues have kept me from installing custom ROM's on every phone i had (Galaxy S2, Xperia SP, Galaxy S3). The issues are Screen quality, audio volume and camera quality. Other stock features are more or less available through apps but these things are very important for day to day usage. CM13 audio volume is so low compared to stock that i sometimes miss calls even if its on loudest. I dont know why CM team isn't working on this one or maybe they don't know the issues with small user base like G2 has compared to other popular phones. I realise there are other mods or tweaks to help with the issues BUT they should have been a non-issue from out of the box. Anyway Kudos to the developers for keeping the G2 alive and i might jump ship any day. Great phone, great battery, great screen to body ratio.
[G2 Original Android Development] Andysuarez:
Hi dr4stic, i'm testing the zips but the two zips gave me fc google services bug.
[G2 Original Android Development] dr4stic:
That bug is usually the result of using an old recovery. Are you using blastagator's twrp version 2.8.7.3 or newer as detailed in the FAQ at the head of this thread? Or CM's recovery? Re-install your gapps from recovery and it should be fine.
[G2 Original Android Development] BlushMaq:
How to make charging led glow only when screen is "off"; it stays on even when screen is on and phone is connected to a power source?
[G2 Original Android Development] Andysuarez:
[MENTION=2096805]dr4stic[/MENTION] I was in twrp 2.8.7.3, then update to the latest 3.0.0.4 the 2 zips work fine.
[G2 Original Android Development] dr4stic:
what do you mean they work fine... with regard to the SIM issue? They both work with regard to your SIM issue? That shouldn't be. The .1 build was straight CM, didn't include anything interesting. The .2 build is the different one. The .1 should fail like the others....
[G2 Original Android Development] Andysuarez:
Yes, the 2 zips works well in baseband, 3g, calls, lte. Don't have the sim bug.
[G2 Original Android Development] RXG9:
Hi, I have a LG G2 T-Mobile version. (D801) I am running the newest nightly cm-13.0-20160218-NIGHTLY-d801.zip and opengapps pico from 2/17/2016 I'm having the WiFi issue, sometimes the WiFi will stop working all together and then it will disconnect, then reconnect by itself, and starts working again. Also in general the WiFi performance isin't as good as stock kitkat. I noticed this when using the speedtest by ookla app

My home connection is 80mbps. On stock kitkat rom d801 on 2.4ghz frequency I hit 40mbps on 5ghz frequency I hit 80mbps.

On CM13 on the 2.4ghz frequency it ranges a lot, sometimes I hit 10mbps, sometimes 33mbps or sometimes somewhere in between. It fluctuates a lot. Same issue on 5ghz frequency, i can hit 10mbps all the way up to 50mbps, most of the time it's around 25-35mbps.

The only other problem is low speaker volume, but I fixed that by flashing this. http://xdaforums.com/lg-g2/development-d802/mod-volume-booster-lp-mm-roms-t3313610

Everything else is working so far. At least what I can tell from playing around with it for a few hours.

Just wanted to tell you about this problem.

Thanks for all your hard-work on this ROM.
[G2 Original Android Development] dr4stic:
*sigh* ... thanks. That means my builds are... "funny". Now I need to figure out why it's different.

Thank you for testing and reporting back :)
[G2 Original Android Development] ChrisStokes:
This is my first post ever. Very new to rooting phones. I have the tmobile lg g2 lollipop 5.1.1 build and its the worst. Ever since the update my battery has went down the drain ten fold. And i know it's the google os that's draining my battery. I used GSam Battery Monitor which detects what uses the battery over the span of time. And it's mainly the screen and google os.

So I'm gonna root my phone and hopefully add the new CyanMod Marshmellow to my phone. I just need help on the recovery part.

All I need to do is download the latest release and recovery files. Download twrp as a recovery manager. And what else?
[G2 Original Android Development] filipelq:
Fast charge won't work in my D801. Ampere says 300mA and it's seems real as it takes a long time to charge.
[G2 Original Android Development] johnb380:
May i say Welcome to XDA!

My first bit of advice is that you... Read the first post aka OP aka Original Post of this thread actually the first couple posts are very informative. And then read it again. Lol. Seriously it has all the info you need as a new XDA member or LG G2 ROM flasher for CM13! It will break down the process very well and it will show you where to get everything you need to get to a booting CM13 on your system. It also has probably any questions you'll encounter and the answers for said questions in the Frequently Asked Questions section or F.A.Q.

Also I suggest you learn how to search the thread with the search feature because it can be a life saver and a time saver also. But what you should do now is go to the bottom of this page and click the page number 1 and start reading and learning. Also to help you and anyone trying to answer your questions try to post your variant number for example D801, D802, D800, etc. When posting here as it helps determine what advice to give sometimes since all the GSM variants kinda share this thread and some variants have different bootstacks like a hybrid one and the processes and things may be different for your variant then mine which is a D801.

Congratulations and Good Luck. Have fun and be careful to follow steps 1 by 1. And after searching don't be scared to ask your questions. Have a good night.

PS- CM13 is definitely a big jump up from stock lollipop in terms of battery life and performance at least in my opinion it is.
[G2 Original Android Development] dan3840:
Out the problem with WiFi disconnecting all the time , the ROM is perfect hope the problem is fixed /:
[G2 Original Android Development] shriom_manerker:
I've read that twrp 3.0 requires KitKat bootloader.. Is it true ? Or was it just some random thing off the internet ? I can just directly upgrade it from 2.8.7.3 right ? Currently running that with the custom cm13 made by dr4atic (the first zip with most cm bugs fixed (music,network), since they're pushed to official cm, I thought now would be a good the to clean flash to those builds.
[G2 Original Android Development] dr4stic:
If you successfully ran any build of mine on CM-13.0, then you're good to upgrade. I don't believe the bootloader requirements changed between runs. If anything I believe the asserts on the installer will keep it from installing on the wrong bootstack.
[G2 Original Android Development] shriom_manerker:
oh i wasnt aware theres a check for wrong bootstack , thanks a billion :) just flashed the twrp 3.0 on my d802, just for fun ill try a dirty flash from your build to the 18-20-2016 build from cm followed by gapps, if it goes well ill report back , i know there are a hell lot of changes but im wiling to takethe risk, most others might be like me who waited for a daily driver build , ill report back if its success ful and ill edit this post with that information :)

again i thank you a lot on this dr4stic, without you we wouldnt be this ahead right now ,cheers :)

Edit- great news, I dirty flashed with no issues at all, everything is just fine ;) I still wouldn't recoend this though .
[G2 Original Android Development] johnb380:
Go into wifi settings and change to either 2.4ghz or 5.0ghz and it won't disconnect anymore while screen is on.
[G2 Original Android Development] shriom_manerker:
did anyone manage to add more "live lockscreen" ?, right now theres only "colors" that just randomly fade colors on the lockscreen. im not able to find any apks or flashable zips to add more types like those showcased by cm earlier. id love to see cityscape working on my device to be frank. it looked amazing in the video. so if anyone found any apps , do get back to me .
[G2 Original Android Development] duy_ng:
Hello everybody. I am thinking about flashing this rom. How is the camera quality in comparison to stock camera? Thanks in advance!

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Original Android Development] johnb380:
I think we have to wait for people to make some apks.
[G2 Original Android Development] GalaxyGusta:
Guys is there a fix for whatsapp voice notes issue?

The recording is very distorted and low volume
[G2 Original Android Development] desiresiscool:
How long can you leave to do a dirty flash between nightly builds. Is two weeks to much
[G2 Original Android Development] nihil39:
Change the lines in /system/build.prop as shown in the code box (minimal sed syntax knowledge required), or just flash the attached zip from your favorite recovery.

#!/tmp/busybox sh sed -i 's/ro.qc.sdk.audio.fluencetype=fluence/#ro.qc.sdk.audio.fluencetype=fluence/' /system/build.prop sed -i 's/persist.audio.fluence.audiorec=true/persist.audio.fluence.voicerec=false/' /system/build.prop sed -i 's/persist.audio.dualmic.config=endfire/persist.audio.fluence.speaker=false/' /system/build.prop
[G2 Original Android Development] GalaxyGusta:
Thanks will try!

just a question im sure this wont survive a cm update is there a way to make it survive it?
[G2 Original Android Development] nihil39:
Let me know if it works, tested on Resurrection Remix 5.6.3 (CM Based) on a d802 32GB

I don't know, I guess the developers should permanently modify the d802 build.prop file with those values, it's up to them. Meanwhile just keep the zip file in your phone memory and flash it after an update, this is a workaround for me: I don't flash ROMs often.
[G2 Original Android Development] proyatzu:
With this fix quality of recording is SAME as stock roms? Its important to me cause im a singer and i often send singing voice notes on whatzapp. LoL.
[G2 Original Android Development] migueldbr:
Ok guys, after a lot of testing, I came to the conclusion that no matter how I tweak cpu settings and governor, I always have stutters while browsing. My best configuration so far is kinda like the one I posted a few posts back:

- switch battery mode to quick

- change governor to ondemand with kernel adiutor

- switch min freq from 1190 back to 300mhz

- set kernel adutor to apply settings on boot

This eliminates some stutters but it's not enough for a smooth browsing experience. The only way to achieve that is to use an adblocker. The Javascript ads on Android completely **** up the browsing experience with lots of stutters (like the androidpolice.com webpage). Using this configuration with an adblocker (like adaway) keeps the rom flying!

I won't be experimenting with settings anymore, because the only place where there was significant lag so far was on the browser(without adblocking). I'm still testing battery life with this settings, but so far I don't notice much difference, maybe some minor drain compared to completely stock settings (but no lag at all)

Edit: just one more thing, using adaway to block ads, if you are seeing that when you are on mobile data ads aren't blocked, you need to go into apn settings and remove the proxy from the apn.
[G2 Original Android Development] nihil39:
Well, I didn't test thoroughly stock recording, but this fix is worth a trying.
[G2 Original Android Development] saarxee:
If have new nightly version I can flash that on dirty flash?

I need to reinstall the gapps and audio fix mode?
[G2 Original Android Development] x_justin:
What browser? I am using R browser as it's optimised for snapdragon (based on Chromium)

---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------

Thanks. Can you explain what it changes?
[G2 Original Android Development] migueldbr:
That browser already has a built-in ad blocker so you don't need an extra adblocker. I use chrome (without adblocking built in). I don't like to use those alternative browsers like caf browser and rsbrowser because they are always a few versions behind and as far as I know they are not open source
[G2 Original Android Development] sutty86:
Followed this to a Tee, Black screen of Death!
[G2 Original Android Development] berlen:
I have one issue: when opening an e-mail (gmail) from its notification, I get a force close of android system. Does anyone have the same problem? I flashed mini opengapps.

thanks
[G2 Original Android Development] elvi92:
Is possibile to add in the navbar a button to lower and raise the navigation bar, as in lg stock rom?
[G2 Original Android Development] lakyljuk:
Using this settings and Adaway. Everything is lightning fast and very good battery time. After one day (2,5 h sot) I got still 70% battery, usually it was around 50. I know it is too soon to decide, but so far I like it a lot. I am not gaming, just browsing on Wi-Fi and mobile data, sms, calls, some videos played, etc.
[G2 Original Android Development] norbigazda98:
Unfortunately, it didn't work for me at all :(

I can't watch a Top Gear episode online without at least 4 or 5 times having to reload the video. Fortunately, it resumes from where it stopped but still...
[G2 Original Android Development] johnb380:
R u sure its not your router? Mine has never done that but maybe once a day it disconnected then I picked 5ghz and it never does now.

Did you try a clean flash recently? Maybe try that other than that idk what else can help.
[G2 Original Android Development] norbigazda98:
It might be my router, i don't know. I should check it with another, I know. I will try that sooner or later.

No, my latest clean flash was about 6 feb, I dirty-flashed the one released on 12 feb and now the one from today, 19 feb.

I could pick 5 GHz but my mom's old XPERIA Tipo doesn't work with it. We have this stupid T-Home router because of the ****ty ADSL and telephone connection so I don't think that it is capable of working at 2.4 and 5 GHz at the same time.
[G2 Original Android Development] belgianrebel:
Had the same bootstack error,

Then went back to stock lollipop and rooted. Installed recovery with autorec app, then upgraded recovery to 3.0.0. Then wiped system and cache flashed rom and pico gapps and everything worked like a charm.
[G2 Original Android Development] x_justin:
Are you u using the built in kernel or that from PsychoGame? I was using Psychogame's kernel and I had about the same results, but now on stock CM (also stock settings), the battery drains even if I leave my phone. It's 50% after one day, screen on time only 50 minutes. It's sleeping nice btw, so that's not the problem.
[G2 Original Android Development] lakyljuk:
I am using pure CM13 all the time, no kernels, xposed or anything, just AdAway and tweaked governor via Aduitor.
[G2 Original Android Development] dr4stic:
Guys... everyone... understand this.

The published kernel binaries from [MENTION=4647521]PsychoGame[/MENTION] are THE SAME CM KERNEL. Except that we needed to test new CAF patches before submitting them to CM. So you guys were being beta testers for Alpha CM kernels. The patches were accepted. Therefore PsychoGame's kernel = CM kernel. The ONLY difference is the crypto stuff that was added and then disabled because it was crashing some devices at boot. Thats it. There are no other differences. The kernel HARDLY EVER CHANGES.

Here's a task for everyone. Go to http://cmxlog.com/13/d800/ (or whatever variant you have). Go to the settings and choose to hide translations (translations updates are huge and automated a you shouldn't care about them). The part at the end of the change (the green text in parenthesis, or blue if you're on the dark theme), those are the names of the packages used by all roms and affected by the specific change. If that text is red instead of green (or green instead of blue on the dark theme), that means it's a package specific to our platform (usually qualcomm stuff, kernel or device repos). I dare you... go looking for red lines for the package "android_kernel_lge_msm8974" ... That's all the changes for our kernel. There aren't many, right?

Or better yet, go to this link (also linked on the OP): All merged G2 Kernel Changes for cm-13.0
[G2 Original Android Development] x_justin:
I knew about that, I thought the CAF patches were more then about the crypto stuff (and that is true as I can see but not nothing which should affect battery / performance if I am right). That's why I thought it could make a difference to use that kernel. Thanks for the explanation.:good:
[G2 Original Android Development] dr4stic:
Oh, heh... yeah. We have a CAF kernel. The patches weren't feature additions so much as they were upstream updates for stuff we use.
[G2 Original Android Development] dan3840:
Changed the frequency but not forward... This problem only occurs with the ROM based on Android 6.0.1 believe the problem is not my router are many people with the same problem. For those who enjoy playing online this is terrible
[G2 Original Android Development] crabilld:
Weird. Could you expand on where you had the problem? What steps did work for you? I did this multiple times and hit some bumps before I found something that worked. Also, the Black screen of Death was my starting point, so all is not lost!
[G2 Original Android Development] sutty86:
Thanks for helping out

Well i managed to get back on to my recovery and now back on cloudy2.2

I followed yourd instructions ,used same files,flashed different 6.0 gapps packages

Each time has ended in the black screen
[G2 Original Android Development] crabilld:
Which step didn't work... step 6? That's the major one to get past. So you completely wiped your phone and reverted to stock Kitkat, then successfully rooted on stock, installed Autorec, and eventually got onto Blastagator's recovery, correct? I only had problems flashing the new bootstack when I was on a Jellybean bootloader, and every time I did so (many times!) I ended up with the black screen of death. The key was starting fresh with Kitkat stock with the Kitkat bootloader, then flashing the bootstack and it finally worked. Once I flashed the bootstack without getting the black screen of death, I was home free. If you successfully flashed the bootstack and reached the screen of death on step 7 (when installing the new rom), then you're experiencing a different problem than me.
[G2 Original Android Development] johnb380:
You aren't trying to flash super su are you? If so then don't CM has built in superuser and SuperSU doesn't work and won't allow this to boot.
[G2 Original Android Development] dr4stic:
No... no no... please no.

[MENTION=2453251]sutty86[/MENTION] ... If you're reverting to stock... full stock.... Just upgrade your phone to Lollipop. Go all the way. I know the resources for the d800 aren't as good as for the d801 or d802, but they exist. I know because that's what I have.

It should be known that the following will erase your phone's storage completely and revert it to a factory state.

Whenever I do this, I use this guide to flash I found to flash d80020c as my starting point. Then I use this guide as a base to flash the OTA's to move to d80020y and finally d80030f.

Rooting each flash along the way with only Stump root and the SuperSU app for the first two systems (let supersu update the root binary WITHOUT rebooting to recovery. Don't use autorec, no TWRP installation) so I can force the OTA's. I don't think you'll actually have to root 20y coming from a rooted 20c come to think about it...

Finally once you've got up to Lollipop (30F) root with the LG Lollipop one click root (it's a pain, probably fail at first, keep trying at it, it'll work), use the lollipop autorec (available in the play store) to install TWRP. Then update twrp to 2.8.7.3....

Now you're ready for CM. All you need is the Gapps and CM. That's it. Nothing more.

NO BOOTSTACKS. I HATE THE BOOTSTACKS. THEY ARE A CRUTCH TO BE USED BY LAZY PEOPLE WHO WON'T, OR FOR WHATEVER REASON CAN'T, UPGRADE THEIR OWN DEVICES TO LG STOCK PARTITIONS.

Your device is perfect now as it is. A perfect snowflake...
[G2 Original Android Development] desiresiscool:
Try flashing hybrid bootstacks if you still have recovery, I had issue as you and that fixed for me
[G2 Original Android Development] DS-1:
I had the same problem. I solved installing hybrid bootstacks.

Is it necessary to use hybrid bootstacks to avoid black screen issue?
[G2 Original Android Development] idhem59:
So, if we have a Lollipop Stock Rom with Root and TWRP, we can directly flash CM13 ? On a D802.
[G2 Original Android Development] dr4stic:
YES. Absolutely.

The bootstacks were only ever created for people coming from JB or earlier as a means to make life easier for them. But it doesn't seem like that's actually made life better for people. I don't personally have the problem with the black screen, so I don't know how to test. I'd love to get someone that gets this issue regularly to just go to full stock lollipop, root/autorec and install without ANY bootstacks and see if that makes a difference. I'm sure it does.