yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] GalaticStryder:
Thank you, I appreciate that.

You can use it on enforcing just fine, although setting enforcing on nougat will break many important frameworks. Setting SELinux to enforcing on marshmallow works just fine and it's a major plus to get it enforcing.

People usually say that SELinux sucks and should be disabled, Linux is self-protect (audit + iptables) on kernel-space but user-space is usually not so safe if you turn it (SELinux) down to permissive. If a given process gets root access (su) on permissive SELinux, it would be able to trigger everything, on enforcing it would need to explicitly be allowed to access that "something" it is programmed to. It's not big of a deal but just another layer of protection.

There are a plenty of sources to get info about SELinux, I personally recommend the Gentoo and Red Hat resources for most Linux Kernel related documentation.

Concerning to the 2nd question, totally. The next release of the Kernel is yet more balanced the current ones, you'll basically not need root if you don't want to tweak the Kernel settings and just enjoy the stability and performance mix that doesn't compromise battery drain nor heat.
[G2 Android Development] VzQzZ:
Thanks for the quick reply and that detailed explanation. I'm currently on AICP Nougat, but will come back to your latest AOSPA. I always come back. haha So no "breaking things" kind of problem on MM. Good.

Great news about next release! Really looking forward to it! But take your time, no need to rush and I won't bother you asking for ETA. It's ready when it's ready. Till then I'll be on your combo: AOSPA + Infinito Beta 5 :)

PS: Just for curiosity.. I see that you use Portuguese names on kernel builds. Are you Brazilian too? ?
[G2 Android Development] android extreme:
[MENTION=6175749]GalaticStryder[/MENTION] i brought to you some log, one concern a "normal" black screen of death but the second one is strange: i've connected my g2 to a car audio system and it started to reboot(and for reboot i mean that the phone remain on boot animation) until i removed the cable. I'm on aicp beta nougat(maybe could ne a ROM fault). I've Aldo another questionon the aicp nougat(bit the dame happen on aicp MM) the setting of virtual machine after the flash of the kernel seems completely messer up(for example dirty ratio goes to 90% instead of 20 and cache pressure is lowered to 20). This is an issue on ROM si de right or your kernel isn't completely compatibile with aicp ROM series?
[G2 Android Development] GalaticStryder:
Out of topic...

Sure, I live in Porto Alegre as of now. It's hard to tell you what is gonna happen in this country/city, I've stopped reading the news lately: One person gets murdered each 9 minutes in Brazil.

Returning back to the topic, I've pushed an experimental build to

Drive

for

testing

on nougat.

This is the last experimental before BETA 6 that I'll probably compile today and upload tomorrow. I've delayed the release to pick up the latest 3.4.113 Kernel update and other miscellaneous changes that are back.

If you flash this (D802/5/6), go ahead and test the new guts:

- Enable KSM and monitor the stats, should be pretty solid as it's 3.4.y KSM + backports.

# Set it to start running
echo 1 > /sys/kernel/mm/ksm/run
# Monitor the main stats after some hours of usage
cat /sys/kernel/mm/ksm/full_scans
cat /sys/kernel/mm/ksm/pages_shared
cat /sys/kernel/mm/ksm/pages_volatile

The logs didn't help much, I'd bet (almost sure) that the sound issues are related to ROM's HAL (audio for MSM8974 isn't supported so we're just "forcing it to work" with older drivers) plus some property set by whatever sound mod you might be using messing everything up.

The VM values I did see someone with the same issue some time ago... I have no idea, maybe the ROM has its own init for setting those values and my script didn't take effect and vice-versa?

I'll take a look at those problems. I didn't have these issues on 6.0 in AOSPA neither CyanogenMod, all fine with CarKit BT and even on cable.

OBS.: Take a look at those sysfs paths and see if they match the stock values.

cat /proc/sys/vm/dirty_expire_centisecs # Default: 200
cat /proc/sys/vm/dirty_ratio # Default: 20
cat /proc/sys/vm/dirty_background_ratio # Default: 5
cat /proc/sys/vm/swappiness # Default: 50
cat /proc/sys/vm/vfs_cache_pressure # # Default: 100
[G2 Android Development] VzQzZ:
I don't have any logs to provide right now, but I can second that. I had some "black screen of death" issues on Beta 5 MM. Using AOSPA + Infinito Beta 5. Happened one time and then started to happen like every 3 hours. I'm going back to that combo in a few minutes and will try to grab some logs if it happens again.

About the other issue, I honestly don't even what that means haha. Might been occurred too, but I guess my ignorance is too high to confirm that ?
[G2 Android Development] android extreme:
My value are:

-vfs cache pressure=20

-dirty ratio=90

-swappiness=0

Yeah the reboot would be probably caused by the ARISE sound mod that i was using, so i think that at least for now we shouldn't use any sound mod on nougat rom with your kernel right? Or there are some mod that can be used?
[G2 Android Development] GalaticStryder:
Sound mods are terrible, it's a bunch of libs and more mess. I use BiQuads and ULL Kernel feature to get a much better audio controller.

You can mod your mixer paths to get ULL using my AOSPA ones: audio_policy.conf / mixer_paths.xml.

I'll push my BiQuad changes to it as well and set ULL by default.
[G2 Android Development] szabyka95:
Do you plan releasing AOSPA 7.1 alpha/experimental release? What CFW are you using currently?
[G2 Android Development] Dimberr:
plus.google.com/104157733403056482149/posts/aCij94a9ERm
[G2 Android Development] ytgbg:
[MENTION=6175749]GalaticStryder[/MENTION]

Is the latest build 7.1 compatible? Probably not, as 7.1 is big change, but I am planning to test AICP 7.1, but I don't want to use any rom without your kernel mate...
[G2 Android Development] GalaticStryder:
There's no MSM8974 support on nougat, you're running marshmallow HALs with backports on the Kernel to make it work.

Any version of Lambda kernel nougat will fit any 7.x, it's magical.

Please flash the latest experimental if you can.
[G2 Android Development] Floodland:
Excellent! Biquads seems to be what I was looking for quite some time. I will start playing with it now.

Now, just a though, who was the motherf... which designed mixer_paths syntax?!

Depending on the line you need to specify 0,1 or ON,OFF or true,false for boolean values, and variety of different syntax for number values (numbers written with letters, numbers, numbers and letters mixed). Damn, someone really messed up there...

Thank you very much for your work!
[G2 Android Development] ceikokitkat:
Reboot on latest experimental (N176) on AICP 12.1 (Android 7.1) while installing app from google play.

P.S. My /data and /cache partitions are on f2fs, maybe this is problem.
[G2 Android Development] Davido_96:
Where d802?
[G2 Android Development] errikosd:
Oh sweet Moses.

Your answer is just at the end of the post you quoted.
[G2 Android Development] aleasto:
Differences with the last experimental? Working great anyways on d802
[G2 Android Development] GalaticStryder:
See commits from Oct 30, 2016.
[G2 Android Development] VzQzZ:
Thanks for the new beta, GalaticStryder. Will test it ASAP.

I don't mean to bother you, but I got some questions..

I see on the changelog that you included that "ULL" thing that you mentioned on that previously post about sound mods. Is it activated by default or do we have to enable it? Also, did you include that "BiQuads" thing too? To be honest, I didn't understand how to use it.

*If* you have the time for it, could you please elaborate a noob friendly guide about how to use it?

I'm avoiding sounds mods since you mentioned the mess they make. But hell, how I miss them ? My Philips SHE9000 died last Friday and I picked a JBL T100A since it's cheaper and actually was kind of expensive to me right now. Like you said before, Brazil is passing through hard times.. Rio de Janeiro now is like "Hell de Janeiro". People just elected Mayor a fanatic religious.. I just can't wait to leave.
[G2 Android Development] D4rkpr1nc3:
Touch Boost

Everytime i touch the screen the cpu0 go ti 1190mhz, how i can disable touch bost or reduce MHz? It drain a lot of battery
[G2 Android Development] GalaticStryder:
Open the .zip file and edit the following entry in ramdisk/sbin/lambda-post_boot.sh:

############################
# CPU Input Boost
#
echo "[Lambda] Burning CPU input boost values" | tee /dev/kmsg
echo "1190400 1497600" > /sys/kernel/cpu_input_boost/ib_freqs
echo "1400" > /sys/kernel/cpu_input_boost/ib_duration_ms
echo "[Lambda] Enabling CPU input boost driver" | tee /dev/kmsg
echo "1" > /sys/kernel/cpu_input_boost/enabled

I'd recommend lowering those values to something around:

echo "400" > /sys/kernel/cpu_input_boost/ib_duration_ms
echo "422400 729600" > /sys/kernel/cpu_input_boost/ib_freqs

Don't disable the driver, it's not needed.
[G2 Android Development] ytgbg:
[MENTION=6175749]GalaticStryder[/MENTION]

Beta 6 Nougat report: D802 on latest CM 14.1 - not a single problem. Everything works and my D802 is not flying, it is skyrocketing!

And to confirm my suspicions for amazing the performance boost on latest Beta 6: I managed 1090 single core points on Geekbench (more than One Plus 2).

Now, if only there is clean AOSP 7.1 build for D802 to get completely satisfied with my android experience...

I can not imagine if you get your hands on One Plus 3 :))))))))))
[G2 Android Development] ig_df:
Nice feedback about the latest beta 6. Waiting on LS980 for M.
[G2 Android Development] GalaticStryder:
I'm waiting for next CAF source drop for 7.1, there's no point in doing anything on 7.0 anymore. I'd argue that AOSP has got stupid on those releases, I see no point in creating a 7.1 branch if the main 7.0 was still on the first releases. That's what happened on marshmallow as well with 6.0 and 6.0.1.

This is how it works on Android:

Internal branches of AOSP developers -> AOSP review -> AOSP mainstream -> AOSP release -> CAF internal branches -> CAF release -> Ordinary developer

The confusion gets bigger when branches get "tracked over":

e.g.:

Android N 7.0 (r1) ------------------> (r2) ----> (r3) -----> (r4)---------->(r5)----------->(r6).............................................-> Android N 7.0 (r26)
Android N 7.0 (r1) ---------------------------------------------------------------> Android N 7.1 (preview) --------> Android N 7.1 (r1) ------> Android N 7.1 (r2)

This makes forces developers to rebase and push everything they had previously to the top of the new release. You don't need to guess too much to understand what happens and what forces devices to be discontinued.

Updating the Kernel and hacking the code usually works but it's yet one more HACK that will lead to another problem, that can lead to another issue...

This is just a general panorama of AOSP, sum this with CAF mess (huge mess) together the hacks to accomplish a working "ROM" on all CyangenMod devices (mess here too) and you've got a recipe for an issue pumper.

Concerning to the Kernel, I need to consider that it has got quite so powerful with the latest KSM with swap + zram on lz4. On marshmallow I forgot to reduce the number of compression streams to two as in nougat, I'll remember to do that in the next release to avoid this overhead caused by this memory sugar equation.
[G2 Android Development] ytgbg:
Thanks for clarification mate. AOSP development sounds quite complicated and difficult and this is making me appreciate devs' work even more.

Yeah, it does make sense to wait for 7.1 as it seems with all that 7.0-7.1 mess there is no point on doing double work.

By the way Synapse is working and I am messing with it right now and testing it...
[G2 Android Development] PtSp:
Question what's the difference between pure stable and domino kernel?

Actually asking if there's any changelog
[G2 Android Development] Uechy:
Offtopic but what theme are you using on zsh and on kde? :p
[G2 Android Development] GalaticStryder:
Anything Linux isn't off topic for me.

I'm using zsh with oh-my-zsh manager and setting dracula as my main theme.

I've also created a fish shell variant of dracula that I use on my SUSE laptop.

As far as KDE, I'm using some mix of the default Breeze Dark theme and colors with La Capitaine icons to remember my OSX user times.

Previously I was using midna-dark theme but it no longer applies to latest KDE, I plan to forward port it as well.

It's irrelevant, anyone using those old Kernel versions might wanna upgrade to Infinito.
[G2 Android Development] PtSp:
Just did. N9 testing.

Why oc the soc to 2.8ghz? What's the goal here? Overheat?

Enviado do meu LG-D802 através de Tapatalk
[G2 Android Development] hitmancho:
Hello,

first I want to say that you kernel is awesome as far as speed and battery life are concerned. I'm running Beta 6 on my D802 on the latest BlissRom. I have undervolted it quite a bit on the most used frequencies and it has not crashed so far. But I have a strange issue. I've left the crash recovery option ON in Synapse and as far as I was able to understand it it's only supposed to restore stock values if you reset your phone 2 minutes after you set new things in Synapse. But the problem is the app constantly gives me the message that it couldn't restore settings on boot, even though hours have passed since I touched any settings in it. It happens on reboots and power off/on. Is this a bug or am I misunderstanding something?
[G2 Android Development] ulihh:
Hi, I think the reboot loops are wifi related. You can check this when you turn off your wifi on your router or walk out of the range while bootlooping. I also had bootloops just like you with all infinito kernels after N2. It seems they stopped when I removed my wifi network on my phone's wifi settings and re-entered the credentials once again. Well, I have to say "it seems" because I fixed it yesterday and I learned that one day is too short for good results.

I'm running CM13 nightly 20161015 on a d802 with kernel IB6M. Good luck!
[G2 Android Development] GalaticStryder:
I'm stepping on this issue, I've got some logs from users. The issue seems to be triggered from ipv4, I'm not sure if they come from nougat Kernel patches or from bcmdhd suspend. I can't get much since I'm not affected somehow.

The last log I got from this was related to sqlite3 rendering. I'm aware of this and will be looking closely after next release since the Kernel is now settled.
[G2 Android Development] 4r44444:
I had multiple Restarts here here log

https://drive.google.com/file/d/0B5zPrCJoNwCDT2V6UVhNbGs3cEE/view?usp=sharing

CM 14.1 Unoffical D802
[G2 Android Development] GalaticStryder:
Just another one coming from clatd - which sums up to be coming from ipv4 or bcmdhd. Please test flashing the Kernel on airplane mode. You can get rid of airplane mode after it boots - if it does.
[G2 Android Development] 4r44444:
Tested it flashing in airplane mode, device booted but still restarting from time to time.

Here is log after first restart after flash in airplane mode: https://drive.google.com/file/d/0B5zPrCJoNwCDOTZ3RGZaRUxOMGM/view?usp=sharing
[G2 Android Development] blakeatl:
When you say flash in airplane mode, what do you mean exactly? Is there an option in recovery to choose airplane mode or you enable airplane mode before rebooting to recovery?
[G2 Android Development] android extreme:
[MENTION=6175749]GalaticStryder[/MENTION] i've two log for you: the first one(in order of time) regard a system freeze(navbar and statusbar disappear and i can't even see the power menù), the second one regards a reboot after MTP connection to linux ubuntu 16.04(but this also happened on windows 10, unfortunately i can't provide the log for that one). All of this happened on Aicp 12.1 01/11 with lambda infinito beta 6 on a clean flash
[G2 Android Development] princenoob:
I really want to upgrade to infinito but there are no Beta 6 MM builds for f320 :(
[G2 Android Development] matteo0026:
Is there a system of notifications can arrive without keeping awake phone? I got only 40% ca. of the time in deep sleep because i receive a lot of notifications, expecially from telegram. This isn't a problem that i got only with this kernel, but with all. Maybe deep sleep can't have an exception when i receive notifications? I don't know if you can understand the problem.

This problem i have with all versions of rom and android 7.x doens't gave me more juice as i thinked it can be
[G2 Android Development] kevin6554321:
Beta N6 for d802 Nougat has the worst battery life ever I've seen in a kernel. It gets 3hrs of SOT at maximum.
[G2 Android Development] android extreme:
Matteo i think that a system like the one you describe is impossible. Android OS wake up every determinate amout of time to check if there is something to do(internal task, notification and so on...)if it doesn't wake up it can't recieve any notification. All that you can do is try to raise the time between the check(should be an app on the play store to do that)
[G2 Android Development] matteo0026:
I know this, but i think it can be optimizated this... Then if phone check if there is something to sync every a determinate time, it syncs and returns deep sleep... And it isn't that the system...
[G2 Android Development] android extreme:
Yeah i made a mistake i should have said "the app keep awake the system", did you tried to go in setting>privacy>privacy guard and manage the single permission of any app(especially the one that drain the most of your battery)?

Try to deny location permission keep awake and run in backgroung, just to start
[G2 Android Development] matteo0026:
Then i don't receive messages... Otherwise i can use greenify, amplify, appops and naptime for get more juice... And while i use phone i would like that there's less consumption... Removing the little heat that it's generate everytime.
[G2 Android Development] android extreme:
If you remove the localization and keep awake you will recive the notification the notification without an excessive battery consumption. Furthermore if you have installed also facebook i would advice you to uninstall it
[G2 Android Development] Punraz_:
I'm on kernel Beta N D802 with CyanogenMod 14.1 . I installed synapse and there stand no uci support detected
[G2 Android Development] matteo0026:
Telegram doesn't use localization... Anyway... I must get better consumption awake too... Without removing performance
[G2 Android Development] GalaticStryder:
Placeholder for BETA 7...

Hello, everyone.

I've been playing with the Kernel values for three days after receiving some PMs about BETA 6 being a little bit "too killer". Let's say that the new feature (UKM) with the default settings isn't that optimized for mobile devices and thus will need tweaks.

I'm compiling the next BETA 7 right now as a hotfix for that and to establish many new default values for all hotplugs and another new hotplug that you might know from dorimanx Kernel which is AutoSMP, it gives plenty of battery and simplicity on plugging the cores - no bugs so far. This hotplug isn't the same as the one dorimanx ships but based off it with some little updates from neobuddy.

Here's a hotfix for KSM:

echo "1000" > /sys/kernel/mm/ksm/sleep_millisecs

Add this to lambda-post_boot.sh file withing the zip or at runtime in your phone.

I've attached some of the updates in BETA 7. UKM was also updated but still has some odd features.
[G2 Android Development] hitmancho:
I can't restore Synapse profiles. I get this error but a .tgz file still gets created in the app's folder. I have given it Storage permissions, yet there is nothing in either restore option. Does this have anything to do with the kernel or is it a Synapse problem?
[G2 Android Development] GalaticStryder:
Profile -> Config.

Synapse uses profile for something else (not sure what) and config for Kernel settings. Press export current config to actually save the Kernel configuration.
[G2 Android Development] love4k21:
Is it possible to turn it off by Synapse or somehow?

I know dorimanx disabled it cause because it was like making 50mb free and wasn't worth.
[G2 Android Development] GalaticStryder:
It's gonna be replaced by UKSM, the way it's tuned right now won't affect performance.

You can disable with:

echo "0" > /sys/kernel/mm/ksm/run
[G2 Android Development] matteo0026:
[MENTION=6175749]GalaticStryder[/MENTION] can you tell me what do you think about what i told some posts ago about deep sleep? If there are some tweaks or hacks or other for optimizating syncing and deep sleep process...

In beta 7 will be removed the random reboots about clatd issues?

In the kernel version 3.4.113 is there a changelog from 3.4.112?
[G2 Android Development] GalaticStryder:
Depends on what you're targeting, I'd tell you to disable fsync, ksm and set your CPU governor to interactive - it's tweaked to save more battery by default than impulse.

Set your hotplugging mechanism to autosmp, it is simpler but functionality and savings are quite good.

I'm working on the N5 bcmdhd (Wi-Fi/BT) with some cleanup for the LG G2 for testing. I'll probably start another release name to accomplish the new changes and you'll be able to grab the first BETAs pretty soon to test what is messed up and what has got fixed.

So far this release is quite stable getting into consideration the amount of code and features it packs up and the security fixes we bundle.

At the regular user perspective of view it doesn't feel "all that", but if you start looking at source code and change after change, it's a something...

I've listed three issues to fix in the next releases:

- BSOD in some wake-up conditions, probably due to "racy" drivers
- Lockdown in ipv4 probably due to some changes in bcmdhd that doesn't seem to settle down on +6.0 clatd
- Updated F2FS has some issues on 3.4.y, planning to upgrade to newer versions of it

Since 3.4.y is now EOL, don't expect more than what we have now in terms of features, they'll just be polished across the future...

It gives me a break to invest time on other things like a decent app on my free time and AOSPA releases - people will eventually downgrade to marshmallow one day and others running stock will probably try it as well.

3.4.112 ~> 3.4.113 commits were pushed on Oct 28, 2016.

IB7M release uploading... The placeholder will be updated.
[G2 Android Development] ig_df:
Hi. Can you explain me please, why every new version of your kernel we need one week for other models, like ls980.
[G2 Android Development] matteo0026:
Ok thanks. My target anyway was the optimisation of deep sleep, but don't remember to syncing apps notifications, too, for the standby juice saving.
[G2 Android Development] 4r44444:
Thanks for the Update! One little question: Is your Kernel working best without changing anything or I must set things manually?
[G2 Android Development] GalaticStryder:
What concerns you the best, I always like when users play around with hotplugs and feedback... The only hotplug I don't endorse for now is blu_plug, not doing fine.
[G2 Android Development] 4r44444:
And BETA 7 release name say its for marshmallow, working on nougat too?
[G2 Android Development] ytgbg:
The new MSM with Fastlane is the best hotplug I ever used in terms of performance and using this combined with Impulse my G2 is just a pure speed monster.

Still Synapse is tricky, I think you mentioned something about considering implementing S-Tweaks like Dorimanx, or I am wrong on that?
[G2 Android Development] khanjui:
Not sure. Probably not.
[G2 Android Development] ytgbg:
Don't flash MM Kernel build on Nougat!!!

Wait for Beta 7 for Nougat to upload!

I guess that the internet speed of GalaticStryder is not very fast and we have to wait for all Nougat Beta 7 releases to upload.