yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] schwem:
I have mine set about the same aside from screen value I have set at 135. Not sure how much difference it makes. I do love the way the colors pop and how dark the blacks are now. I'm not sure why LG toned the screen on this thing down so much. It really looks great like this.
[G3 Android Development] Alukrad:
Settings are close to same for DU stock values.
[G3 Android Development] schwem:
Anyone using this kernel running AICP? I updated to the latest nightly on my VS985 and flashed this kernel and I'm getting crazy bsod's when the phone gets even remotely warm. I've set all values back to stock and the same occurs. No OC, no undervolting nothing and I'm getting lockups that result in a battery pull in order to recover. It's happened 6 times or more in the last 2 days and it's driving me nuts. I need to let the phone fully cool before I start it back up or it'll black screen freeze on me right after boot. Not sure why It's happening all of a sudden. I've tried clean flashing the rom and kernel. I tried flashing the rom clean and setting it up then flashing the kernel afterwards and I get the same results. It's starting to freak me out! Any ideas?
[G3 Android Development] Koont:
Did you boot up AICP then flash the kernel? Try that. Had issues myself until I flashed in that order.
[G3 Android Development] schwem:
Yes, that's actually what my longwinded explaination states. I clean flashed the rom. Set it up and used for a while and then flashed the kernel. I've tried that twice now. I also tried flashing with the rom but it wouldn't even make it through the app optimization without completely freezing up.
[G3 Android Development] Alukrad:
Switch ROMs lol. Dirty Unicorns is the best for D851. Trust me on this one, you'll never use another ROM again.

---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------

DU developer for D851 and VS985 is the same guy. His builds are rock solid and about ad bulletproof as it gets
[G3 Android Development] schwem:
Actually I've tried it for my vs985 and it's pretty buggy. I know the tester for the vs985 builds for DU and he even told me it's pretty buggy right now. There no bugs in AICP and it's my favorite rom. No chance I'm going back to DU. It's an awesome rom but AICP has the same features without the bugs. I'll just try a newer nightly and see what happens.
[G3 Android Development] Alukrad:
not sure how long ago you're talking about but all across the board DU has had the least problems with all the G3 variants and feature wise AICP doesn't even scratch the surface. I know also that DU was the only ROM that never got the proximity issue everyone else was having.

---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------

The only time I've ever heard of anyone having any issues with DU on the G3 is if they don't perform an advanced wipe of the system data cache and dalvik after the factory wipe which I know most people don't do nor most people realize how important it is to do when flashing a new ROM
[G3 Android Development] schwem:
Yeah dude, I'm not retarted! I don't flash a rom without a full wipe. I also don't like DU. My rom of choice is AICP. Nothin changin that. No biggie. I'm gonna try a newer build. I also found for some reason when I restored data and apps, Kernel adiutor was keeping my settings from before which was using alucard governors and hotplug which for some reason seems to have been the problem because now with interactive govs and msm descision hotplug it's getting warm and not givin black screens. Looks like I need to just quit restoring data from Google. All is well and I'm running MY FAVORITE ROM without issue! Thanks for the suggestion though but I don't like DU.
[G3 Android Development] Alukrad:
Damn, hostile. Maybe you should try deleting KA folder to clear all settings, that usually works, luckily I've never ran into that problem. I guess i should feel relieved I've never ran into your issues.
[G3 Android Development] hunting_:
everything work fine I'm on d850
[G3 Android Development] schwem:
Not hostile. Just happy with the rom I run and can't stand when people suggest to change roms. It's not the rom. I figured out the problem. KA is retarted and you're right. I deleted the folder, cleared everything involved with KA and we're good now. It was KA not the kernel or rom.
[G3 Android Development] Alukrad:
Whoa man lol. "Can't stand" is too intense of feels imho. No need to raise the heat around here. It might wreck your LCD ;)
[G3 Android Development] hean_burak:
It is really problem while optimizing apps. When you flash something via twrp, shut phone down. Wait it to cool down then boot and let it optimize. Hope it will work that way. Or you can try to flash kernel after apps' optimizing finished.

And for normal use, you can enable "intellithermal" and its "kernel control" via kernel adiutor (thermal).
[G3 Android Development] schwem:
Haha, darnit! This is why I hate typing. What comes out is never what or how you intend it to. My point was is that it's not rom related, never was and usually never is. The G3 kernel is a pile of crap but we're lucky we have devs like the one who builds this one to improve upon it. However, if you wind up changing something in the kernel and are unsure of what may result, you wind up borking something. I did though change everything back to stock values and I tried clean flashing both the rom and kernel and seperately I might add. I was just unaware of the fact that Google had restored my settings from when I changed the govs and hotplug to alucard. Not sure why those settings stuck even though I changed back to stock values before wiping and reflashing everything. Kind of strange how it did that. Do you have any idea though why using alucard results in bsod's for me? Is there something else I need to enable or change to get it to work? I used to use alucard govs and hotplug on my G2 and on my G3 with Nebula kernel without issue. Maybe this dev changed something that I need to enable or change in order for it to work property? Also, what are you using for thermal settings? Do you enable core control and if so what do you set for throttling and shutting down cores? Maybe that is my issue as I turned those values down to 80°c. Just curious. Also, I didn't mean any disrespect or hostility as you put it. It seems I never type the way I would normally talk to people. I am always respectful to others as I don't want others disrespecting myself or my family. I have a wife and 2 kids. I'm not the kind of guy to get people riled up. Anyways, thanks for not lashing out too bad. I wasn't trying to be crass, I just can never get my point across through typing as there is no emotional involvement in text as there would be in face to face interaction. Thanks again.
[G3 Android Development] Alukrad:
I actually have my thermal controls off because I have CTT Mod installed to keep my system at cooler temps. Maybe you can try doing that as well since as far as I know some BSOD's for our phone is caused by crap thermal limit controller. Also I do suggest using CTT Mod highly for better battery life and wayyyyyy lower temps

edit: It's 90Â° out where I am right now and my temps have been holding out at 70Â° even in this blister heat. All hail CTT XD

edit2: Also all my values are stock other than I underclocked to 2.2ghz and changed my I/O for internal to tripndroid which is my standard setup
[G3 Android Development] schwem:
Cool, I think I'll check out ctt mod. Also, I notice under cpu in KA you have msm limiter. Is that device specific or is there a way to enable it because it doesn't show up in KA for me.
[G3 Android Development] Alukrad:
We should be on the same build using aCC and MSM Limiter came with it. What build date is your KA atm?
[G3 Android Development] schwem:
I'm on acc 1.4 and the latest KA from Playstore. No updates are available for it.
[G3 Android Development] Windforce0511:
If you find a way to get rid of mentioned scroll lag, please reply me.
[G3 Android Development] Alukrad:
that's the issue right there. Don't use play store KA. Use this instead

http://xdaforums.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549/page30
[G3 Android Development] schwem:
Bonus! That's much better! Thanks a million. :good:
[G3 Android Development] Alukrad:
No prob :)
[G3 Android Development] hunting_:
Plz which color profile you use ? And setting also plz share :) Thanku
[G3 Android Development] Alukrad:
it's just KA darkmode theme. It's in the settings lol
[G3 Android Development] hunting_:
Lolz ask about kernal setting color profile and kernal setting like cup and many more[emoji14]
[G3 Android Development] marcdw:
Recommended color settings were just posted a couple pages back.

Applied them on my primary PAC LP ROM (using another kernel of course) and it's a different world now.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] hunting_:
Plz anyone help me about kernel setting ? Device hot so much what cup or governor setting and hottplug setting and voltage what is the best setting use this kernel Thanks
[G3 Android Development] souler456:
Ok, since the kernel I always use isn't updated yet, and I just updated my ROM, I just tried this kernel, and aside from GPU stucking up on high levels, it's pretty good so far...

BUT my favorite governor, which is Intellidemand is not available, so I hope the dev could add it on the next release.

For a meantime, I "tried" adapting my settings from my intellidemand setup to this kernel's Slim governor, and want to share it here for some criticisms. Also, since the guy above me wants for a full KA profile, here's my setup:

CPU Tab Setup

Max Frequency: 2256mhz

Min Frequency: 300mhz

Suspend Max Frequency: 1497mhz

CPU Governor: Slim

Mulitcore Power Saving: Enabled

Scheduled Workqueues: Toggled ON

Interval: 0ms

Sync Threshold: 1267mhz

Interval: 0ms

Input Boost Frequency: 1267mhz

CPU Governor Tunables

down_differential: 5

gboost: 1

(make "gboost: 0" if you're not playing games or not always on graphic-intensive situations)

input_event_min_freq: 1497600,1190400,1190400,1190400

input_event_timeout: 250

optimal_freq: 1497600

sampling_rate: 60000

sync_freq: 1267200

two_phase_freq: 1497600,1497600,1497600,1497600

ui_sampling_rate: 40000

up_threshold: 80

up_threshold_any_cpu_load: 90

up_threshold_multi_core: 90

CPU Voltage

Make it -50 to -60 for the Global Offset. I use -50 personally.

CPU Hotplug

Intelliplug: Enabled

CPUs Boosted: 1

Min CPU Online: 1

Thermal

Core Control: Disabled

Intellithermal: Enabled

Frequency Throttle Temperature: 75C

GPU

Max Frequency: 578mhz (though it stucks at 657mhz on my side. Just gave you the ideal one.)

Laziness: 6

Ramp Threshold: 3

Adreno Idler: Enabled

Down Differential: 25

Idle Wait: 30

Screen

R - 242

G - 247

B - 256

Min RGB Value - 35

Saturation: 38

Screen Hue - 12

Screen Value - 128

Screen Contrast - 132

Originally, I use Per Core Control, but I am not sure what values to input since there's no intellidemand. And as I backread, most of the guys here use Alucard as their main hotplug, so... Gonna try that as well...

And now... Gonna bookmark this one...

:D :) ;) :good:
[G3 Android Development] Taracair:
Settings don't stick... Any ideas why? I am using the newest modded KA.
[G3 Android Development] levider:
You must toggle on "apply on boot"

And toggle off MPDecision in CPU Hot plug :)
[G3 Android Development] Taracair:
That's what I have set. Occasionally settings are going back to interactive CPU governor, and so on.
[G3 Android Development] hean_burak:
Install normal (play store) KA, change governor to something else. Then you can use KA mod.
[G3 Android Development] MaddMaxx636:
I dont know if this is kernel or KA mod related. The set on boot settings are made arent working. Some to most settings are just setting to kernel defaults.
[G3 Android Development] djdeeles:
V1.5 is up. It's like a maintenance release but it's a little tuned.

v1.5-- 04.05.2016

- Linux 3.4.112

- Slimport fixes

- Kernel HZ 300

- Merges from CM

- A little tuned for better battery & performance
[G3 Android Development] marcdw:
That was the case with KA-Mod v7. That issue should not be there anymore. It's up to v9 now.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5

---------- Post added at 08:39 PM ---------- Previous post was at 08:36 PM ----------

Same applies. You using latest version? No reports of this with new version yet in its thread.

I'm still on v6 but will try v9 later.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] MaddMaxx636:
Yeah i am using the V1.4 of the kernel but never knew there was a V9 of KA mod. Where would i get that since i didnt see that when i checked the thread.
[G3 Android Development] marcdw:
If running KA mod v6+ it will notify you of an update. It will also download and install from the app. Otherwise download the latest from the op below. The download will be named app-release.apk I believe.

The dev is looking for feedback on the latest version, too.

http://xdaforums.com/showthread.php?t=3333549

Kernel Adiutor-Mod (Formerly Singularity Kernel Adiutor)

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] hunting_:
Thanks for this great kernel work awesome with RR
[G3 Android Development] v.konvict:
Well got the the cpu at 1.7 and the screen color set to what was posted here a couple of pages back. This kernel is awesome with rr rmx
[G3 Android Development] hunting_:
Anyone help me I want add Amoled Style colour setting value
[G3 Android Development] edoardotavecchio:
what about state notifier toggle bug in KA Mod? I haven't understood yet if it's kernel related (state notifier doesn't work) or ka related (ka can't set state notifier on, or just graphic glitch)
[G3 Android Development] v.konvict:
Few pages back
[G3 Android Development] brolic925t:
Latest update is really smooth! Good job
[G3 Android Development] souler456:
Modded KA executes the enabling of State Notifier command, which is this:

echo Y > /sys/module/state_notifier/parameters/enabled

But if you navigate the directory in our device, the "enabled" file is missing. This is why it can't be toggled whatsover.

Ask this kernel's dev if the command is right, cause if it's wrong, this is an error of Modded KA's side, thus, have to be reported through Modded KA's dev (which is [MENTION=4231562]Yoinx[/MENTION]). But if the command is right, this is an error of this kernel's dev. I don't know who's who, so... Just gonna leave this for rightful judgement...

:D :) ;) :good:
[G3 Android Development] jochem86:
Amazing screen... unbelievable that this isnt the standard for out phone. i guess you can have some minor differences but this should be the standard.

1.5 kernel is awsome, great that we can use KA now with the mod, on the Unofficial Bliss rom works like a charm... it had already the modded KA init so a perfect match!
[G3 Android Development] denf666:
many reboots with d855 and acc v1.5 on DU
[G3 Android Development] djdeeles:
I explained this in my previous posts. State notifier is always enabled. But some of govs & hotplugs not using it.

It's KA problem that not checking /sys/module/state_notifier/parameters/enabled is there or not. It's always display that option
[G3 Android Development] :
I don't have the bandwidth right now to dig through kernel source on github...

What do you have in that directory?

If you could do the following and past the output, it might shed some light on if the enable sysfs node was just renamed to something else. If it's not, I may just have to do a specific check for the enabled node instead of how I'm doing it now (making assumptions that the file will exist apparently).

for file in /sys/module/state_notifier/parameters/*; do echo {file##*/} && cat {file##*/}; done
[G3 Android Development] souler456:
So for short, it is enabled at default and can NOT be forced to be disabled, yes?

And how about your tackle for the GPU stucking at 657mhz? Do you have any leads so far? This could be a show-breaker for your kernel, but other than that, it's quite a firm kernel.

:D :) ;) :good:

---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------

Im on mobile, but this screenshot could be sufficient enough, I guess...

:D :) ;) :good:
[G3 Android Development] :
Yeah, I had posted before the OP had replied (well, didn't look at the next page anyway).

Looks like the OP removed the enable/disable feature or didn't pick it up from people that added it. Personally, I'm not a huge fan of being able to disable state_notifier... there's really no reason to. That feature actually came from a pull request that someone had submitted. I've already fixed it in my app, so next time I release it won't show if the enabled node isn't there.

*edit*

Actually, here's a microupdate to fix that issue. So now it won't show if the enable node doesn't exist.

http://xdaforums.com/showpost.php?p=66713904&postcount=310
[G3 Android Development] EternalFlame:
Try to get some logs bud, flashed v1.5 on latest official DU 10.2 for d855 and it´s working flawlessly for me.
[G3 Android Development] eric93se:
I'm pretty sure I brought this issue up a while back. What I do is disable 'simple gpu algorithm' and enable 'adreno idler'. The gpu with then idle down to 27MHz. I'm sure we'll save some battery life if this gets fixed.

Overall still an awesome kernel!
[G3 Android Development] aheeejd:
I just read through this entire thread, glad it was just 37 pages. I've learned allot from all of you, thank you very much. Thank you dev for this, I'm running latest RR on ls990 & am really liking the kernel. Normally I'll flash a kernel & just change governor, under volt, over clock etc, now I've played with some different features thanks to some of you, good experience. Looking forward to the growth of this kernel & the thread & the input within. I used to try & keep up somewhat with nebula but way over my head. This seems slower passed lol. Thanks again guys. Enjoying crispy colors wahooooo.
[G3 Android Development] schwem:
Did you push an update? Mine just said update version 9 or something like that. I accepted and updated either way.
[G3 Android Development] :
Great work on this kernel so far. As previously posted by many, the only bugaboo is the GPU freqs sticking. I've noticed that they set on boot and stick(using modded KA) until the screen gets turned off and back on again. In catlog I get this error re GPU: ThermalEngine E[GPU_MON} ACTION: GPU - [GPU_MON} Setting GPU[0] to 578000000

I don't have any thermal settings applied with KA, I have my GPU set to 462mhz, and this on a clean flash of Tesla MM 3/22 build. I don't know if it helps or not, but a log is attached.
[G3 Android Development] JDogg1329:
Yeah I had the same thing on AICP rom.
[G3 Android Development] ins5736:
VS985. I've lost gps with 1.5 and noticed significant drop in battery life. Reverting to 1.4.
[G3 Android Development] :
[MENTION=3585838]djdeeles[/MENTION] (Sorry. I'm not sure how to properly mention someone on XDA yet.[Yay, I did it!]) May you please add the ability to disable software CRC as it adds 30% (I forgot the percentage but it should be close to 30% or so) overhead? Disabling it gives us better performance. Also, for Fsync, must the toggle be enabled or disabled for better system performance? I really don't care about losing data at possible crashing or shutting down of my G3 as I backup my data anyway. :P

---------- Post added at 03:24 AM ---------- Previous post was at 03:21 AM ----------

Try the settings [MENTION=5075251]souler456[/MENTION] posted a couple of settings back.
[G3 Android Development] souler456:
If you have faith in your kernel setup that it will not auto-reboot your device while using it, then disabling fsync is a go. It's disabled on my side, by the way...

:D :) ;) :good:
[G3 Android Development] :
Thank you! I was always confused whether the toggle for Fsync had to be enabled or disabled for that extra performance.
[G3 Android Development] souler456:
Oh. Almost forgot. Disabling fsync will also affect data loss of apps that "unfortunately" force closes on their own due to crashes and OOM situations that forces LMK values to equate wether the app would be forcefully close. So you have to be VERY confident on your kernel setup.

:D :) ;) :good:
[G3 Android Development] :
I didn't know about that. Backed up my app data with Titanium backup. Thanks for the heads up! Say, what read ahead value do you use for internal (Tripndroid) and external (Zen) storage?
[G3 Android Development] petenoni:
DU 10.2 no reboots.
[G3 Android Development] souler456:
well, for i/o scheduler, I use a tweaked SIO for internal storage that has a 1024kB for read-ahead, then tripndroid for external storage that has a 512kB for a read-ahead, since all my multimedias and iso files for emulations are on the external sd...

:D :) ;) :good:
[G3 Android Development] takis:
Can we have wake gestures?
[G3 Android Development] takis:
The cm sound fix doesnt fully fix your problem ... Are you talking about that one or something yours?
[G3 Android Development] Abdelrahman Adel Ahmed:
Do you can tell me if you are using 30B sources in this kernel or not especially in dispaly drivers ( or whay ever you call the thing that control it xD ) ?

because every kernel with 30B have stock like colors which is washed out but old kernel for CM from lollipops Builds CM12 to CM13 untill MM 30B got released was having Great Colors
[G3 Android Development] djdeeles:
I'm using new cm sources so 0B have stock like colors.

New build is up.

Change log is at op post.
[G3 Android Development] amir-kia:
Hi

What is fast charge means in this kernel ?

It cause faster time for charging by fast chargers? Or it is usb fast charge ? I use samsung fast charger and in stock mm rom it charge 15min faster time .by this kernel my phone will charge faster ? Or change nothing ?
[G3 Android Development] Ltilt2:
Que?
[G3 Android Development] djdeeles:
Both of them it includes usb fast charge & rises ac charge current.
[G3 Android Development] huzefaonline:
so far so good for D850. will let the kernel settle in for a couple of day and then report.
[G3 Android Development] Duckscreen:
is anyone try this on stock?

is headphone jack working?

thank you.
[G3 Android Development] Roi007leaf:
Works great so far! Can you add thermal?
[G3 Android Development] Duckscreen:
Report from stock

i know this kernel for AOSP

SD card is corrupted

windows 10 not recognize

kernel is very good stable

everything working except SD card and when plug into windows

Report from AOSP

no problem at all that stock have
[G3 Android Development] djdeeles:
Currently notn plan. But I'll think about it.

BTW stock thermal works well in thermal modded device. No overheating or performance loss.

Stock settings of my kernel
[G3 Android Development] :
Ok so i played for a bit with the first initial release of the kernel, it was mostly working on Fulmics after 3days the phone started acting up and reboots by itself i haven't done anything to say it was some app or else, anyway might try the newest release on RR

good luck
[G3 Android Development] sachs:
KCal maybe?
[G3 Android Development] takis:
Got you something to work on... Check the bug where the phone can not boot while turned off and connected to charger... Its one of the remaining cm bugs...:cool:
[G3 Android Development] djdeeles:
[MENTION=5883369]takis[/MENTION] yes that drives me crazy too :)
[G3 Android Development] takis:
Will you work on it? Very irritating lol
[G3 Android Development] noypitoits:
is it just me? not booting on F400L running on the latest RR rom. after the LG logo the screen turns black then nothing. flashed & restored my BOOT back up using twrp 3.0 by [MENTION=2756494]chuyennho184[/MENTION]
[G3 Android Development] ivoh95:
Not booting on d851, twrp multirom recovery, cm13 nightly. Black screen after lg logo. Its nice to have a kernel that should work with cm13, as nebula does not.
[G3 Android Development] djdeeles:
I cant test these cuz i dont have these devices. I'll try to fix them(d851,F400L).

Currently d855, d850 working without problems. I need more testers and feedbacks.