yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] GalaticStryder:
Dropped an experimental build on Drive for D802. It has the upcoming blu_plug set as default tweaked for battery friendly workloads, interactive governor tuning for balanced scenarios instead of impulse out of the box and GCC 6.1 as compiler.

Download: https://drive.google.com/drive/mobile/folders/0B0kZ4DVPwVcMTnVLOU53ZWFHaDA?usp=sharing#list

Feel free to test it, smooth and battery friendly for me :crank:
[G2 Android Development] berezker:
I was wondering, isn't impulse better in both performance and battery life than interactive?

I've pretty much tried half of the governors for a day each and I've found impulse to be the most stable and battery friendly ones.

Interactive is good but I think it's kinda slow.

Why did you make interactive the default governor now?

And thank you for your hard work.
[G2 Android Development] Floodland:
Damn, blu_plug is active and I still see Cpus being plugged without significant load. Blu sometimes does plug 2 additional cores instead (bricked used to plug just a single cpu without need). Are there other conditions that can plug CPUs without evaluating current load? Seems like something else force the driver to wake cpus spite their algorithm:

Cpu 0 is idling at 300mhz, and additional core(s) are awaken, all remain at 300 with no visible load for a second or so, and then turned off again. When blu is active, sometimes I see 3 cpus standing at 300mhz for a second, then two, and few ms later one again. Sometimes this repeats few times, for few seconds and then start acting as intended.

The unneeded CPUs plugs seems to be less frequent with this last build, but it is still there...
[G2 Android Development] berezker:
So, I've just flashed this and noticed something.

Most of the time, two cores are active

Is this something the new hotplug is supposed to be or just a "bug"?
[G2 Android Development] cucumber42:
how to fix the cpu spikes

I noticed the cpu1 spiking a couple of days ago, so I forced myself to learn about governors and hotplugs. I initially tried to cheat and just raise the idle frequency, to a modest 652800; it did keep cpu1 from flickering, but I had 2 hard crashes. I figured out the impulse governor is just aggressive on increasing the frequency, and this in turn causes the hotplug to turn on more cores when not necessary. I found out that with this governor, the msm_mpdecision hotplug nwns settings were too aggressive. After a couple days of testing, I found the following nwns settings work better, 15,0,26,22,32,21,0,20. These setting will of course only matter if you are using the current impulse governor and mpdecision hotplug. I've had great success with battery and performance even playing games.

If you don't know how to do this, just create a shell script with this:

echo "15" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_0

echo "0" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_1

echo "26" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_2

echo "22" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_3

echo "32" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_4

echo "21" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_5

echo "0" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_6

echo "20" > /sys/kernel/msm_mpdecision/conf/nwns_threshold_7
[G2 Android Development] sas_sas:
On to my Custom AOSP rom 'AOSP-OMS-6.0.1-20160821-d802-jenkins.zip' I flashed with 'Lambda-infinito- beta- N1 2016 Aug29' but after Synapse installed "No UCI support detected" message received..

As far as I know Lambda kernels is supposed to support Synapse, right?
[G2 Android Development] burak.dunal:
Firstly thanks for your great job! But i have a qoestion for you [MENTION=6175749]GalaticStryder[/MENTION]

How can i found d802 09/21 build? Not in the beta builds or stable builds. Thank you.
[G2 Android Development] GalaticStryder:
Profiling, I'm reworking the Synapse files from scratch and making it way much more simple to use and understand. I'll put a profile selector with three or four main settings out-of-the-box with tuning from governors up to CFS scheduler parameters.

It means that a given governor will be pre-optimized (it actually is as far as the latest experimental) for a given profile, since impulse has many code from interactive having both on performance mode almost forces the user to redo the tuning manually.

The new way makes it simpler for the ordinary person, just switching the governor will make the device change from water to wine when he wants to.

Interactive was not slow, it was just not well optimized - now it's a great battery oriented governor that doesn't produce any UI lag even turning on adreno idler with GPU at 200MHz default clock. That's enough for most users, if not changing the profile will make the phone turn into beast mote at will.

Well, the blu_plug is still under development and this was the objective of the build, though it was coded to be even more plugger of cores. After some changes:

https://github.com/GalaticStryder/kernel_lge_msm8974/commits/lambda/arch/arm/mach-msm/blu_plug.c

It's now a little bit better, though this hotplug shines on medium usage, the idle moments aren't detected properly in the code and it's probably not going to be the use real case due to input boost and other background iterations like compression of memory etc.

Read above, this is for testing only. The default hotplug is neither bricked nor blu, they are meant to be used as presets for performance and medium usage respectively.

Thanks for sharing your preset, I'll put those values into testing and see how they work.

Close the app, open again. UKM will be removed and introduced as per ramdisk instead so there might be some changes like I said earlier to avoid and maybe fix those Synapse issues.

The new download spot is at Github: https://github.com/GalaticStryder/kernel_lge_msm8974/releases
[G2 Android Development] Hiyaslalabs:
Random freeze. Anyone experienced it? Pretty annoying as I need to turn off and restart the device.
[G2 Android Development] Litendria:
I got random reboot problem two or three times a day. It's happening randomly, i can't say a any exact time.

That problem happened on the N9 kernel too.

I'm using PA 6.0.3 and Lambda-Infinito-Marshmallow-Beta-N4-D802-09222016
[G2 Android Development] rabies876:
No issues. Just perfect.
[G2 Android Development] GalaticStryder:
New interactive tuning and scaling after some hours of usage.

CPU temperature as if we had cryogenic cooling in the back. (Take it as hint Moto Mods).

OBS: I said previously that I was willing to buy a new device... Well, I decided to pick up something good for a little bit cheaper like an F320 from AliExpress cause it has all the guts and I can keep the development going. If anyone has one of those as a backup phone in good conditions I'd be interested. I'm waiting for the LOCA glue to attach the panel and digitizer on the D802 but it's not like having another one just in case.

Could you print your last_kmsg in here? I suspect of one change actually...
[G2 Android Development] berezker:
Sorry for asking many questions

By that, do you mean the latest experimental where you introduced blu hot plug?

Or an upcoming release?
[G2 Android Development] Hiyaslalabs:
Guess you live in a very cold country. My battery and CPU temp is 33 and 48 celsius respectively. That is normal no gaming only chrome open. And may battery is brand new. D802 user here.
[G2 Android Development] DvineLord:
will speaker gain stick next beta? im using N4 on d800 and speaker gain wont stick. i tried fauxsound, kernel adiutor-mod, and synapse all switch back to default.
[G2 Android Development] Litendria:
Here, thanks for work. :)
[G2 Android Development] burak.dunal:
Same problem here. And headphones gain is buggy too
[G2 Android Development] GalaticStryder:
No, it won't. I've said earlier that Faux Sound needs to be written to use our LGE open source code in driver instead of the proprietary one that Faux created, dorimanx has already done that and added a locking function to it. I can't code this in UKM just yet so it might be done for the next release name only.

I wanna make STweaks default to tweak the kernel and Synapse as monitor as he does...

The proprietary app works good for now, the Synapse control is the one you may avoid using because it's written for the old driver on N4.
[G2 Android Development] burak.dunal:
I use faux driver but not stick. Anyway I will wait next release. Stweak would be great if you can! Thank you for quick reply. :good:
[G2 Android Development] ulihh:
I get bootloops with the new kernels on cm-13 nightlys when I re-enter my home wifi network. All I can see is an exclamation mark on the wifi symbol for more than the usual 3-4 seconds and then the LG logo from the reboot. From there on the bootloop continues until I flash an older kernel. It's a d802. Combinations that I have tested are cm-13.0-20160923-NIGHTLY-d802 with Lambda-Infinito-Marshmallow-Beta-N4-D802-09222016 and cm-13.0-20160927-NIGHTLY-d802 with Lambda-Infinito-Marshmallow-Experimental-N103-HOTPLUG-D802-09252016. Wifi at work is ok. With Infinito-Beta-N2 everything is ok on cm-13 nightly.
[G2 Android Development] _FroX_:
All stable and perfect with underclock 1958Mhz and undervolt -20mV (-30mV isn't stable, some reboots/poweroff) with impulse governor.

D802
[G2 Android Development] berezker:
Did you use kernel auditor ?

I do and I undervolted 60 mV on all frequencies

Everything is stable and great
[G2 Android Development] aleasto:
Welcome to the silicon lottery
[G2 Android Development] ytgbg:
[MENTION=6175749]GalaticStryder[/MENTION]

Hi mate, you mentioned that the latest beta should work on Android 7.0 Nougat. Did I got this right?
[G2 Android Development] GalaticStryder:
Officially not but I already have a working kernel locally for upcoming N releases based off CAF tress.
[G2 Android Development] johndoe-xda:
Any suggestions on how to tune audio quality with Lambda-Infinito-Marshmallow-Beta-N4-D802-09222016? I have on of those G2s with the hiss/distortion noise bug.
[G2 Android Development] ytgbg:
If you want I can test it on AOSP 7.0 to see what's up :)
[G2 Android Development] ulihh:
After I discovered that I can stop the endless bootloop by simply turning off the wifi network (or walking out of its range), I took a closer look with logcat. I noticed that my d802 connected to my 2nd wifi network just before the bootloop. My 2nd wifi network is on an internet connection with a huge packet loss on the line (> 20%). I forgot to remove the credentials some weeks ago. Now it connects to my 1st wifi network and it's ok. No more bootlooping. But I still wonder if the bootloop could be related to packet loss... :confused:
[G2 Android Development] android extreme:
After a reboot on aicp 21/09 with latest lambda experimental i just opened synapse and i found that every option has failed in red. However after another reboot everything returned normal. [MENTION=6175749]GalaticStryder[/MENTION] i don't know if this is a bug or not but i thought that was worth of your attention maybe is something important
[G2 Android Development] GalaticStryder:
The only way to know for sure would be a dmesg during the 2nd. router approaching, that would trigger the broadcom kernel driver to connect and show some warning or error if it had failed.

The RMNET driver has got a missed change from BETA 4 that might possibly lead to this scenario. Anyway, thanks for the input.

I'm getting rid of UKM, in nougat things will be quite different as I'm writing the json files from scratch and putting the old code on top of osmosis synapse injector that works great on nougat. There's some more spice in his code too.
[G2 Android Development] Dimberr:
I got wifi bootloop too. Hope this helps

N9 https://drive.google.com/file/d/0B6bhwaJeLmumbk1lVkdvT1dsWFk/view?usp=drivesdk

Beta 4 https://drive.google.com/file/d/0B6bhwaJeLmumUFEtMENjUXlSQzg/view?usp=drivesdk
[G2 Android Development] cucumber42:
With Beta4, every time the screen is touched, catlog shows these two errors:

E/ANDR-PERF-MPCTL(2019): PERFLOCK Failed to connect to socket: errno=111 (Connection refused)

E/QCOM PowerHAL(2019): Failed to acquire lock.

Not sure if this is having any effect on performance. Also I'm hoping you get the f2fs fix in the next kernel. Thanks!
[G2 Android Development] GalaticStryder:
I'll take a look at it, probably I've updated the code and some API got broken. If your SELinux is enforcing it might be related to it since it needs a perfd entry to work properly.

type_transition perfd mpctl_data_file:sock_file mpctl_socket;

As far as F2FS, I'm backporting some changes from the official testing branches to avoid the issue on dirty pages, it's not precision math in this case and might take some time...
[G2 Android Development] android extreme:
Reboot after connecting the phone to the pc(windows 10) in mtp mode
[G2 Android Development] GalaticStryder:
Thanks, I'm aware of this issue for some users. Doesn't seem to be reproducible on Arch Linux though. You can fix that by installing Arch Linux :crank:

I'll look into it, there are some priorities first related to AOSPA7 and our ultimate kernel presence on nougat.
[G2 Android Development] android extreme:
Galaticstryder it's funny because i've installed on my pc in dual boot ubuntu but still can't use it because my mouse doesn't want to work ;)
[G2 Android Development] orti-otto:
Junior MemberThanks: 5

Since i installed a new nightly 20161019 + Hipnose beta N8 i have problems mit Google Play Framework and wakelocks.

Every morning after unplugging from circuit, i get the wakekock Icing. After reboot Icing ist gone.

After that i get 20-30 minutes wakelock over the day *net_scheduler*.
[G2 Android Development] Floodland:
I got random Google services wakelocks from time to time (specially after reboots), but I do not think it is kernel related, but the same old crappy messy Google spyware infected services.

It happened to me with, any kernel, ROM, architecture and Android version since I remember.

net_scheduler in particular is used by anything which have an android account (from WhatsApp to Facebook and anything listed under settings/accounts). That one depends on your apps.

There are multiple threads open with different approaches on how to improve the google apps situation ( disabling specific services is the one works best to me), but IMHO, the root cause is Google sloppy bloated development.
[G2 Android Development] GalaticStryder:
The ultimate combo, now in N!

Hi, guys. I've been quite so busy bringing AOSPA up with patches for our CAF backend project to run on MSM8974 devices this week.

I've refactored the kernel with some new updates. I'll be pushing a BETA 5 today for marshmallow with the same changes we have in nougat, as I said I've unified the marshmallow and nougat on the same source code. Probably will be dropping the kernel for the dudes willing to try it with nougat by the end of the day for D802.

All the HALs, blobs and patches for CAF pure builds - not CM - are alive at my Github.

Thanks, CyanogenMod team and especially invisiblek for bringing the initial patches for the LG G3 and LG G2.
[G2 Android Development] armivzla:
Waiting for beta 5 for MM in the d800, thanks for development!
[G2 Android Development] ytgbg:
Great to hear!

I am one of those that are waiting to test in on N!

Just a question, If I got this right, D802 N build will be only for the AOSP based roms and will not work on CM based N roms, is that correct?
[G2 Android Development] chenweifei:
Waiting for beta 5 for MM in the d802, thanks for development!
[G2 Android Development] Dev Dezigns:
it's already awesome and kicking off strongly ,, thank you for sure
[G2 Android Development] GalaticStryder:
We only have CAF device trees on the LG G2 - the last AOSP device tree we had was in CM12.0 that used Nexus 5 bits as base.

So it means the kernel will work unconditionally on any ROM as before. I'm trying to make Lambda work as is on AOSPA, let's see how far I can get.
[G2 Android Development] TnK8iD:
Anyone can share a download's link? I can't find any beta on gthub. Thanks
[G2 Android Development] khanjui:
Probably there is no download link, you should wait for release or compile it yourself.
[G2 Android Development] quangtuyen88:
anyone try complie the kernel from source on github ?? I try complie but the size of kernel is 3M << 12M ( beta)... or did i miss something ???
[G2 Android Development] thtkidsvm:
Same here I get a 2mb kernel. It seems like it's missing a lot. I know that in the terminal it shows there's no zimage, and someone where it had a make error that ends at waiting for unfinished jobs.
[G2 Android Development] neolithicera:
I see that you are using the d801. Whats the latest Infinito build that has worked for you? I've tried them all and Beta 1 worked but was reasonably laggy all the rest crashed after a few minutes up. I'm on the CM13 8/20 snapshot. I'm currenty using hipnose beta 4 because its stable.

Thanks
[G2 Android Development] thtkidsvm:
Infinito beta 4 worked smooth for me but I i kept getting random reboots. The most stable is hipnose beta n4 and infinito beta n1. I'm using the cm13 9/28 nightly.
[G2 Android Development] neolithicera:
Did you notice any lagging on infinito beta 1? I'm temped to try that again.
[G2 Android Development] thtkidsvm:
It didn't lag for me but it depends on which beta 1 you have. There was an edited one that fixed the gpu being stuck at 200mhz, that's the one I have and it doesn't give any problems. I just wanted to use impulse as my CPU governor that's why I use hipnose beta 4.
[G2 Android Development] neolithicera:
Could you re upload this Kernel? The link isn't working for me.

Thanks
[G2 Android Development] zizuka:
There are way too many builds, too many download sites, its confusing to tell what is what.
[G2 Android Development] Hiyaslalabs:
I never got reboots since I tweaked it to my best battery profile with the latest kernel. Cpu0 to max 1728 the rest 1267. Max gpu 320. Cpu global voltage still 0. I'm gaining at least 4 hours sot from full to 20% with regular usage like sms fb YouTube chrome. No gaming though.
[G2 Android Development] neolithicera:
Are you talking about the d801? And which infinito build?
[G2 Android Development] Hiyaslalabs:
D802. Sept 22 infinito beta. Trickle charge it when it gets 100% and you'll be able to use the device for 24 hours with regular usage having at least 10% bar the end of the day. :D
[G2 Android Development] errikosd:
Those were personal builds, I do not have them anymore, sorry.
[G2 Android Development] neolithicera:
Alright thanks. What build are you using right now? I'm attempting to use infinito beta 4 however it seems to be getting less and less stable until it just bootloops.
[G2 Android Development] errikosd:
Now I use CM13 with CM13 kernel, as I don't have much time to tinker around with my phone. It's stable and gets the job done. I am waiting for AOSPA Nougat, though! :fingers-crossed:
[G2 Android Development] neolithicera:
Same here! I really want to try a nougat ROM however there aren't any builds for the d801:(
[G2 Android Development] Punraz_:
Whats the difference between pure and incremental builds?
[G2 Android Development] totofe69:
Just a stupid question... Does it works on N rom ?
[G2 Android Development] android extreme:
[MENTION=6175749]GalaticStryder[/MENTION] sorry for the question but i'm not able to find it: where did you release the beta 5 marshmallow build?
[G2 Android Development] love4k21:
I guess the builds are compiling right now, so just wait till it's finish :)
[G2 Android Development] aleasto:
Well, cannot say much more than 'It booted' so far ;) Latest cr-droid, d802
[G2 Android Development] GalaticStryder:
I've tested locally on my D802 on CM14 three days ago, it was expected to boot though. Now, I've kept only the sources for AOSPA since CM14 has got booting, I was building it since CAF released the LA.UM source code and Rashed started the staging bring up. Also, since all the patches I have to push to CM are on device layers I don't need their whole repo resting on my HDD anymore.

I'm doing the best I can to resurrect the MSM8974 but it's hard since CAF decided to abandon it on marshmallow.
[G2 Android Development] kkandy:
I always get in a bootloop after flashing an update. Tried CM13 from the 10th with Beta 5 now and its still the same as N9, Beta 4 or whatever. I tried bootstack stuff, which doesnt work, SuperSU + Bump & no SuperSU at all. Is there something I need to flash aswell?
[G2 Android Development] love4k21:
Try to turn off WiFi. I have the same problem if WiFi is on or I turn it on after device booted.

I don't know why but in synapse I always get the message that UCI is missing. So tomorrow I will do a clean flash from cm13 snapshot and try to get a dmsg or last ksmg or whatever you need to fix it
[G2 Android Development] kkandy:
Yeah, doesn't reboot now. How do I activate WiFi now without getting it to bootloop again?
[G2 Android Development] rabies876:
Running smooth. Report back in a few days
[G2 Android Development] GalaticStryder:
It was intended to target nougat only at this time, I'd recommend you to downgrade when I push the release for marshmallow.

Here's a tip:

- If the zip file contains nougat on it, you should not flash it marshmallow.

- The tag IB5N stands for Infinito BETA 5 for Nougat.

This first one was backwards compatible but the next ones may not be such, so pay attention to the names of the files. I'll definitely need to update the OP to contain that so people don't get confused.

I'll compile the rest of the variants right now and push the proper marshmallow one too.
[G2 Android Development] totofe69:
Flashed beta 5 on lastest crdroid nougat build and no issue no reboot. Everything works well. In testing
[G2 Android Development] Litendria:
Is camera working?
[G2 Android Development] totofe69:
No. I have tested several camera apps but they are not able to access to camera hardware. Waiting for camera fix. Bt, ir, WiFi, data are working well
[G2 Android Development] ytgbg:
[MENTION=6175749]GalaticStryder[/MENTION]

Maybe a stupid question, but anyway: Is it possible the Nougat camera problems be related on kernel level or has something to do with the kernel or they are drivers related?

Off-topic: I see you push a lot of camera Nougat commits to the AOSPA gerrit... Any progress on camera on AOSPA 7.0? I am curious as AOSPA 6.0.3 was the best ever camera experience on any non-stock rom and actually pretty close to LG stock camera...
[G2 Android Development] GalaticStryder:
I actually made a huge progress on it but there are a few things to be mitigated yet. Those patches are at the framework level, what happens is that the camera code isn't backwards compatible, instead it is divided by APIs. The current on development API is called Camera3 or HAL3, all the changes in the framework that are made now focus on this one, making it more secure and better but breaking the previous APIs that we use on Camera2/HAL2 and obviously in HAL1 - the most simple one.

On my testing, the camera is launching and focusing but it force closes when capturing/recording starts.

I've backported some of what we had on marshmallow to nougat: https://github.com/GalaticStryder/packages_apps_SnapdragonCamera/commits/nougat-caf

The time I have I'm spending on audio and it's worth but I can't get BT sound at my laptop or headphone, I'd like to know if CM and its "forks" have it working on the LG G2 but I don't feel like downloading just to test that.

What I know is that I was using most HAL changes from them for the audio some days ago (before starting to polish it) and it wasn't working as well.

OBS: The proper marshmallow release is this one: https://github.com/GalaticStryder/kernel_lge_msm8974/releases/tag/IB5M

Afaik, I don't get it why people were downloading nougat builds for marshmallow, it's dangerous to do that. Post #1755 has the advice on how to pick the right version, always check the tags and zip name.