yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] johnb380:
Ya its [MENTION=4647521]PsychoGame[/MENTION] that wrote it but in the comments he writes...

"Patch Set 1:

I'm aware this commit removes LGE's CONFIG_LGE_DEVFREQ_DFPS code from mdss_mdp_overlay.c but we don't define CONFIG_LGE_DEVFREQ_DFPS anyway in CM's kernel config. If it's preferable to keep this function intact I can rewrite it a littlebit to set #define MIN_REFRESH_RATE 30 to 38 when CONFIG_LGE_DEVFREQ_DFPS is used in our device configuration. At least it's running on my device without any problems but it's what others prefer."

Jan Jasper de Kroon

Patch Set 1: Code-Review+1 If there are no objections this is ready to be merged, so any objections against it?

Feb 8 11:36 AM

Ethan Chen

Patch Set 1: It's not worth it to keep LGE code if it's not enabled anyway.

Feb 8 1:03 PM

Jan Jasper de Kroon

Patch Set 1: Code-Review+2 Verified+1

Feb 8 4:29 PM

Jan Jasper de Kroon

Patch Set 2: Patch Set 1 was rebased

Feb 8 4:29 PM

Gerrit Code Review

Change has been successfully rebased as 6becf53c10e38c6aba816cea6e4a6e0c96c854da by Jan Jasper de Kroon

Feb 8 4:29 PM

But it seems its not acting correct even tho the default max is supposed to be defined by the individual panels max fps. I don't think it's working right personally. I doubt its supposed to run at 60 fps but maybe it needs 38 fps or 40 fps and its running at 30 fps most of the time. I think it needs to be defined to run at 38 fps like he says in the comment. He says he can re write it a lil bit so it'll do that so maybe he can try to do that and see if it makes a difference. Maybe the way he's writing it makes it run slower instead.of it forcing it to the max 38 fps?
[G2 Original Android Development] dr4stic:
I talked to [MENTION=4647521]PsychoGame[/MENTION] and I picked out this patch because it seemed to have to do with framerate. Ultimately we need to find a way to query some framerate values to see some before/after's for that big group of patches. Or who knows. Maybe the new nightly will make a difference and this had nothing to do with any of the patches.

That being said it's 3:45 AM my time. Sleep time.
[G2 Original Android Development] GalaxyGusta:
So wait what do you suggest? Update to the latest nightly today? Cuz I only do it once a week or so.. Pr revert to the nightly I was on before which worked perfectly
[G2 Original Android Development] zpanoz:
Weird gapps booting problem. Phone stuck!

Before I start I have to say that I am new to rooting. I used this method to root my phone and everything went great. I have a huge problem after updating to the latest nightly. I installed yesterday cm 13 nighlty 20160204 and everything went smoothly. However I couldn't install the latest TWRP (2.8.7.3) so I have 2.8.6.1. This morning I downloaded the latest 20160210 nightly through my phone under cyanogenmod updates and I updated. My LG G2 went into TWRP and performed an update. Everything looked fine after booting into cm I keep getting these meassages that google services and basically every google related app is not working. The phone keeps throwing to me these messages and I can't do anything. I tried to boot into recoverey but I can't. The phone just boots into CM. What to do? Please someone help!!!

I can bring down the notifications screen and if I press the settings button I can see that the settings screen open on the background. I can also accept calls but I can't do anything else.
[G2 Original Android Development] sparklekid:
I'm having the same issues and unfortunately, preferred network type, regardless of what I select reverts to "Global"
[G2 Original Android Development] GyGu:
I asked the same question
[G2 Original Android Development] speebman:
looks like you need to re-flash GAPPS

download the latest GAPPS and flash it via recovery, do a low wipe (delvike cache) and reboot

danny
[G2 Original Android Development] chaynx:
Is there any way to get Ambient Display working on this Rom?
[G2 Original Android Development] runekock:
[MENTION=7272736]zpanoz[/MENTION]

Entering recovery by the key-combination should still work. Unfortunately, there are different keys depending on model and bootloader. On my d802 with the last kitkat bootloader it is:

1) Turn phone off by holding power button for around 20 seconds

2) Press and hold power and vol down

3) When LG logo appears, immediately release keys, and press and hold vol up and vol down.

4) Say yes to factory reset

You may have to try a number of times to get the timing right.

Or if you have enabled adb in CM, you could use that from your computer to reboot to recovery.
[G2 Original Android Development] JoseAQP:
Try to boot in recovery by enabling advanced mode in developer options, then boot and reinstall gapps, that happened to me yesterday.

Enviado desde mi LG-D802 mediante Tapatalk
[G2 Original Android Development] dr4stic:
Well, if you want to help test, then yes, that's what I'm suggesting :) I may not see the same issues you do. I may be looking at refresh rate instead of frame rate. If you guys notice the problem, it's be helpful to get feedback from you on a newer nightly.

You know twrp has a feature that lets you backup your entire installation. Just do that. I usually wipe cache and dalvik before a backup to make it smaller. If you don't like the result, then just restore.
[G2 Original Android Development] GalaxyGusta:
Why, does the latest nightly changed stuff that address the issue?

I have no problem updating today I'll do it and reply
[G2 Original Android Development] dr4stic:
Dunno... hoping for luck I suppose :)

This could very well have been completely unrelated to any changes made to our device specifically. A bug like that, someone would've noticed and maybe fixed it in a following nightly. I guess I'm just hoping this was the case.

Thanks for your help!
[G2 Original Android Development] GyGu:
[MENTION=2096805]dr4stic[/MENTION] I'm the last nightly and did not notice any difference in the animations.

I did a clean install, maybe it's because of that.
[G2 Original Android Development] dr4stic:
I don't understand. Did you not see a difference from the 20160210 nightly and are thus seeing a slow down, or do you not see a difference from < 20160207 nightly and everything looks normal? That changes the meaning of your next statement :)

If you do a clean install (assuming that you're on the right bootstack, etc... which you likely are), then there's nothing left to an issue. It'd be something within CM. Are you saying there IS or IS NOT an issue after you clean install?

EDIT: Forget it... I see it now. I thought a 20160211 nightly had been built, but it wasn't. So you updated to the latest nightly and the animations look normal to you....
[G2 Original Android Development] GyGu:
[MENTION=2096805]dr4stic[/MENTION] yes, I did not see anything different in nightly (20160210). (slow animations) I think there is no problem with a clean installation.
[G2 Original Android Development] dr4stic:
Thanks [MENTION=5909419]GyGu[/MENTION]

[MENTION=4489397]GalaxyGusta[/MENTION] and [MENTION=3556013]johnb380[/MENTION] ... would you mind terribly doing a full backup of your devices and then doing a factory data reset (just wiping user data, not storage)? Then go through the motions of setting up your device minimally to see if you still see the slow down? It may be that your issue is just an upgrade artifact...

If you still see the issue, chime in with your device model (well, GalaxyGusta anyway... I believe johnb380 has a d801).
[G2 Original Android Development] GyGu:
[MENTION=2096805]dr4stic[/MENTION] but in any case I will expect my girlfriend to get home, she has a G2 with the 20160207 version and then will compare between the two nightly
[G2 Original Android Development] dr4stic:
That's actually fairly perfect! I love A/B testing. I also played with "FPS Meter" from the play store. I turned it on for the home screen app (in my case listed as "Google App") and watched the numbers as I scrolled and stuff.
[G2 Original Android Development] johnb380:
I'm on a clean flash of the d801 2.10 nightly with [MENTION=4647521]PsychoGame[/MENTION]s 2.05 beta kernel already but it seems to have leveled out. So I guess maybe it is a lag issue instead of a fps issue. Maybe it's a kernel problem since we are on the 2.05 kernel while every other device is on 2.10 nightly kernel. I'm just guessing now just wondering if that could be it. Cuz my phone felt much faster on the 2.07 nightly but I'm prolly just nit picking now.

So to summarize I'd say the problem hasn't went away but might not have been what we thought. It just seems like my phone is just slower period not just animations and such.
[G2 Original Android Development] dr4stic:
Oh! that's right... you aren't even on a new kernel because of the bootloop issue. Yeah, I think you might need to hold off till you have a working kernel again.

Just out of curiousity, what does a 20160210 nightly with the 20160210 kernel I made you feel like? You said that one worked right? I'd like you not to use it regularly, but did you see any of the mentioned slowdowns you talked about.
[G2 Original Android Development] johnb380:
I don't think I did to be honest and but I wasn't on it long as u said not to use it long so I made sure it booted and ran it for long enough to check Tapatalk/xda and then I clean flashed the 2.10 nightly 2.10 open gapps and the 2.05 beta kernel and that's what I've been on since. There hasn't been a new build posted yet today so it'll prolly be around 7 pm est.

While I got u here do u think I should try to flash the new build when it comes out without the beta kernel and see what happens? Or should I just flash the kernel also to be safe?

Edit2:

Is there anyway you could make me a reg 2.10 nightly kernel with the bad commits removed? If not I understand. Thanks either way man.
[G2 Original Android Development] GyGu:
Ok [MENTION=2096805]dr4stic[/MENTION] I made the comparison between the two (LG G2 D802) and there is no any difference in slow animations.

In fact, even seems faster in nightly 20160210, but that's me to say because everything is basically the same, in neither are installed kernel.
[G2 Original Android Development] chewdaniel:
on D802..... didn't notice any kind of slowdowns too...... downloaded a FPS Test app and it shows an avg of 55
[G2 Original Android Development] GalaxyGusta:
guys its definitely slower.. check i notice it the most when unlocking my device when it uses the patter security when the animation accrues after you successfully unlock the animation is slower compared to what i had in the 02/02 build i saw it straight away after booting up

also when slide the quick toggles its really looking like 30FPS

also when scrolling through the settings app I can also notice the slowdown its like you can see the frames compared to 60FPS which we had before..

another animation I can notice it is when the app slides down when closing it. you can tell its a bit slower and not as smooth

btw you can only see it if your looking for it... i see only cuz i saw the pattern animation being slow and then started seeing the other places where its slower

oh and [MENTION=2096805]dr4stic[/MENTION] i have a D802
[G2 Original Android Development] dr4stic:
I don't think you have to keep clean flashing (which I'm assuming you mean factory wiping and restoring apps and app data). You just have to flash a kernel. You don't even have to really wipe dalvik or cache, the kernel boots before any of that matter. I think the only reason it's suggested/recommended is for completeness. If the kernel comes with accompanying apps (like some 3rd party ones do) then that's a different story, and even then usually handled well without having to wipe anything... but [MENTION=4647521]PsychoGame[/MENTION]'s kernels aren't like that.

My understanding of the problem is cursory at best and I believe the fix is going to be reverting all of those crypto patches from the device. That's a lot of patches and I'm not sure I trust me to reverse them in the right order. I could try, but honestly, I don't believe there's gonna be any real difference to [MENTION=4647521]PsychoGame[/MENTION]'s 02.05 kernel if I were to do that. The kernel hardly changes. There's only 2 more changes related to special cases of gapless playback for compressed offload which we have turned off. So for all intents and purposes, you're just asking me to rebuild that 20160205 kernel (also a 20160207 kernel).

EDIT: Looks like the change is here... lemme see about building you a replacement kernel. http://review.cyanogenmod.org/#/c/132462/

EDIT2: That looks like it's more of a last ditch effort patch that won't get merged... Still, I'll build you a kernel with it.
[G2 Original Android Development] dr4stic:
OK... do me a favor and do a clean install tonight when the new nightly comes out. That means factory wiping. Make sure to do full backups like I mentioned before so that you can restore afterwards. I went crazy with a similar bug on 12.1 and it turned out that all I needed was a good factory reset and then everything was right as rain. I think something probably got shuffled in the Settings databases that didn't get updates handled properly... it happens... and sometimes it'll just slow down a system. For me it made Facebook, Gmail, and other seemingly unrelated apps unbearable in usage.
[G2 Original Android Development] GyGu:
I have two smartphones LG G2 D802, one of them with the latest nightly and another with nightly Day 02/07 and there is no difference.
[G2 Original Android Development] GalaxyGusta:
I don't know man I can see it.. Try using the 2/2 build on one device and the 10th on another one..

But it's not like super bad and I'm sure I'll get used to it but it's noticeable..

Did your check on the areas I mentioned?
[G2 Original Android Development] AssassinGEO:
Guys a little question I would like to get answer to, so please read if you mind, it's a simple question.

I always had one little or big problem with CM ROMs starting from Lollipop... pulling down quick toggles animation was always dropping FPS. I flashed CM12.1 and then CM13 and on CM13 it was like a disaster... much worse than CM12.1, almost felt like a phone from 2010 with a weak GPU. Stock Kitkat and Lollipop ROMs are normally smooth for me, also CM ROMs are actually smooth too but it's only THAT area that has that baaad FPS drop. Is it me or it happens with you too? Maybe you guys don't mind it? When on landscape mode, it drops down very smooth, it can do it smoothly in portrait too but RARELY, most of the times it drops FPS and it annoys me too much, always fearing to do it just to not see that FPS drop. Is it only me?
[G2 Original Android Development] dr4stic:
I think that's just a "you" occurrence. I've never seen a difference in behavior like that. Sorry.

Could it be that your touch screen is losing sensitivity in portrait mode?
[G2 Original Android Development] AssassinGEO:
Nah, not a sensivity thing (I suppose?), it's just a bad FPS. Sometimes it can get smoother, just a little but noticeable, then it goes back to that again. What I noticed tho is that phone is getting smoother everyday, but not with toggles tho, bu still I guess my last hope would be on patience. Gotta let it run for week or two.
[G2 Original Android Development] dr4stic:
Here's a thought... Do you run Facebook Messenger? If you do, do you have chat heads enabled? I've seen chat heads do weird things on my aunt's bacon (oneplus one) with cm. Even with the chat head hidden, it still occupied an upper corner of the screen and made it seem like the screen was unresponsive... The solution was to fully disable chat heads.
[G2 Original Android Development] AssassinGEO:
Thanks for thought. Unfortunately no, that's absolutely not the case, tested. Guess the device freaked out after too many flashing, so performance degraded and the phone needs a rest. Just wanted to know if it's only me. Thanks for the answers!
[G2 Original Android Development] dr4stic:
Ha! I get up to 59 when scrolling through settings! I win ;)

Yeah, I just booted a build from an hour ago and it seems very snappy on the UI.
[G2 Original Android Development] chewdaniel:
[MENTION=4489397]GalaxyGusta[/MENTION] D802 here as well, did whatever you mentioned while running FPS Meter .... everything seems fine.... perhaps you might wanna try a clean flash

[MENTION=2096805]dr4stic[/MENTION] i was running "FPS Test" :p but since you mentioned "FPS Meter", my Settings went up to 61 hehe
[G2 Original Android Development] Totalrapture:
I've just been trying to flash from recovery; I've been following the instructions on CM's website. I'm not sure exactly what a bootstack is tbh; I've been in the iPhone scene for the passed couple of years and can't remember all that has been done to the phone. Is there a guid I could use to reset it back to stock?
[G2 Original Android Development] xtract1:
did they add call recording in the lastt nightly?
[G2 Original Android Development] dr4stic:
OK. I'm not sure how much you read on the first page in this thread, but you really need to read post #1 and #2... TO COMPLETION.

The WiKi entries on CM's site for this device are HORRENDOUSLY out of date (and, incidentally I got the access today to go ahead and update them :) woohoo!)

As for resetting to stock, you'll have to search XDA and the net. However I highly recommend that. If you can get your phone updated properly to stock lollipop, you can root from there and you won't have to update any bootstack.
[G2 Original Android Development] joeben1:
I reported this problem a few days ago and I think I find an easier way to reproduce, maybe somebody else can confirm.

- phone is connected to my local provider congstar (t-mobile)

- open "network operators" in "mobile network settings"

- wait until scan finish

- select manually your provider again

- phone starts (tries) to connect

result:

- message displayed "Can't connect to this network at the moment. Try again later."

- network is disconnected and does not reconnect

When I perform a network scan now, it finishes without any results.

I can't manually choose a network provider, even if it's my provider.
[G2 Original Android Development] AsM0DeUz:
I just upgraded from 02052016 nightly to 02122016 but now my phone keeps rebooting on the LG logo. I tried to downgrade to 02102016 I downloaded as the same time as the 02102016 but same problem. I had to return to 02052016 to get it running. I made a factory reset without success...

Has something changed between these versions requiring any special steps to perform to upgrade?

Regards

Envoyé de mon Nexus 7 en utilisant Tapatalk
[G2 Original Android Development] vztmi:
I have the same issue. I also noticed it a few weeks ago when travelling abroad.

I had to manually choose a provider because the automatic selection didn't work. (This is an issue with my provider which is unrelated to d802 or cm13).

I never succeeded to use my phone there.

Now I confirm that I can't manually choose my provider even here when automatic selection works.
[G2 Original Android Development] Toomkee:
I managed to brick my internal speakers on my lg d802 after upgrading from 02102016 to 02122016. anyone with me with the same?
[G2 Original Android Development] chewdaniel:
just for the heck of it i'm gonna go back to stock LP and start over and hopefully be able to use the lg-devs bootstacks :p

edit: ok for some dumb reason flashtool failed..... not gonna venture further :p
[G2 Original Android Development] sunekosuri:
I got that also on the 20160205 Nightly with Psychos Kernel 20160205

When I select"choose my provider automatically" afterwards, then it registers to network again and all is working.
[G2 Original Android Development] sapsa:
I have wifi alway on and "Keep Wi-Fi on during sleep: Always"

Even so I dont get any notification and when i turn screen on then I see that wifi has connected, and thats the only time I get notification.

Is there a way (in Android 6.0) to make this work better ? I would love to have my smartphone check for notification via wifi like once,twince in one hour.

If not native is there something that wont burn my battery in one day that work like I expect it to work (schedule checks, low memory/battery footprint) ?
[G2 Original Android Development] tzizim:
help!!

hello!

i did the update and then my gapps crash and the phone stuck on these warning.

qustions:

everytime i update via the settings ive got to enter recovery and install gappas all over again?

help!!!!!!

i cant enter recovery mode,

i press both vol down and power, relese with lg apper, and then press again but still no recovery is up just the phone whith the google crash.

need your help good people!!
[G2 Original Android Development] hbxde:
It looked like it was bricked by the last update .. i just had to push the power key for a very long time to solve the *boot loop* i guess.
[G2 Original Android Development] niubboxp:
Sorry but i did not understood if all the lastes problems i read is related to lastes nighly or some kind of combo with criptography and/or newer twrp
[G2 Original Android Development] tnvu1:
The last good nightly for me (d801) was cm-13.0-20120207
[G2 Original Android Development] chaynx:
Im currently on 20160210 and i'm having a huge battery drain (50% left 47min of SoT).

Are there any fixes?

Can I just install a more stable nightly (like 20160207) without wiping everything?
[G2 Original Android Development] tzizim:
if anyone care, i solve the problem with press billion time on "ok" google app crash, and then force recovery with adb via pc..

but! every update will i need to install gappas again????
[G2 Original Android Development] johnb380:
You guys have to tell the variant number (d801 for me) when reporting a bug. Every variant has different commits going into their builds. So if you want help you need to tell

-Variant number (d801,d802,etc.)

-Nightly version you started on

-Nightly version you flashed to

-How did you flash (clean flash or dirty)

-Gapps version and date

-Anything else that was flashed like a kernel or xposed

-And any other info that is important!

Also try to wipe system, data, cache, and dalvik cache first before reporting because a clean flash is a big help sometimes it solves all your problems!

The more info you give the better.

You can't just say O man I flashed this ROM and now my phone is bricked Help Me!

That isn't going to help you or anyone else.
[G2 Original Android Development] dr4stic:
If you can tot (or kdz) back to stock LP, you won't need a bootstack after you root. Your phone should be in the perfect place to accept cm-13.0. All you need then is new twrp, cm, and gapps.

I also think that anyone using this phone should probably learn 2 things: how to get into recovery from a cold and warm boot, and how to tot/kdz back to stock. I saved PDF's on the procedures as well as downloaded all the necessary files. Have since done it a number of times on my phone.
[G2 Original Android Development] chewdaniel:
i thought i'd give it a try since my journey to CM12.1 was a weird one that resulted in me having to use some hybrid bootstack (droidth's one) which included some weird cust.img that has some overlay files in them..... oh well.... thought if i'd do it all over from stock LP i can use either use the official bootstack or nothing at all...... somehow it couldn't detect my phone so i didn't wanna go further. let's leave that for another day :p

can't tot cos can't seem to find the proper files that i need. hmmmm

btw....

with CM12.1 i could use the lg-devs, danielstuart, and droidth's bootstacks.... all of them work.... but for some reason with CM13 only droidth's one works. the other 2 gives me a black screen :/ any ideas?