yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] EternalFlame:
R17 setup revamped, enjoy :)

CPU:

min: 422MHz

MSM Limiter: Off

Sync Threshold: 2457 MHz

Min Input Interval : 100ms

CPU Boost Frequency (0-3): 2457 MHz

Migration Load Threshold: 0

Wake up Boost: On

Arch Power: Enabled

HOTPLUG:

Profile: Disabled

CPU Boosted: 4

Min CPU's Online: 4

Suspend Defer Time: 0

Defer Sampling: 0 ms

Boost Lock: 1 ms

I/O:

Read-Ahead size: 2048 KB

RQ Affinity: Disabled

NR Requests: 512

GPU:

GPU min Frequency: 578 MHz

GPU max Frequency: 657 MHz

Memory:

Z-RAM: 512MB
[G3 Android Development] xocomaox:
422MHz minimum? Why?
[G3 Android Development] EternalFlame:
Because minimum frequency's are used while idling/screen is off, so if you have background processes running, they run with this frequency, ergo, everything gets faster processed, it also takes less time to crank up to the maximum frequency's when you wake up your device.

Its all about speed and total smoothness dude, haven't faced any battery deficiency's tho if you are worried about that, but this is not a "battery saving setup" anyhow ;) [MENTION=1154141]xocomaox[/MENTION]
[G3 Android Development] xocomaox:
Understood, but I have not noticed any slowness with background apps or other things with a 300MHz minimum. I was just thinking why bother with anything higher than 300MHz? But if that's your experience, there's no reason to change it from what you have.
[G3 Android Development] closee91:
How do I reset synapse to default values then implement your profile? EVERY time I change kernel values with synapse it cause SODs idk what I'm doing wrong...
[G3 Android Development] schwem:
Same here. I had to uninstall synapse and reboot, then go back to using kernel adiutor. Only way I could get the lag and sod's to stop. Weird that synapse causes this for both of us.
[G3 Android Development] closee91:
I think its weird too. On my d851 default kernel settings work fine. If I use synapse and change things then my phone SOD and I have to battery pull. Same with you?
[G3 Android Development] schwem:
Yup, same here but on vs985. I also tried it with R18 but it was worse. I can change whatever I want with kernel adiutor without any issues though. That really doesn't make any sense.
[G3 Android Development] closee91:
That's what I'm saying lol. It makes no sense. I've always heard synapse was the superior app. Did you check any logs after the sod?

---------- Post added at 03:14 PM ---------- Previous post was at 03:01 PM ----------

It did it even when switching to kernel auditor. Does anyone have an answer for this? Its really annoying not being able to change anything with the kernel
[G3 Android Development] schwem:
Now that I can't help you with because I can change whatever I want with kernel adiutor and not have issues.

No I haven't getten a log as I was at work the last time I tried synapse so I had to get my phone working asap.
[G3 Android Development] EternalFlame:
Try this dude:

How to reset:

- tools > clear synapse data > restart device = stock values

How to apply:

- Move .tgz file to your Internal storage > Synapse > saved_profiles

- Profile > Profiles > choose .tgz file > press "check-mark" and not "X"

- Synapse will restart and then press "X"

- Check all values and if you have to change something press "check-mark"

Works for me every time and i had the same issues as you with Kernel Adiutor after some days that's why i switched to Synapse lol :<
[G3 Android Development] closee91:
I'm clean flashing my phone again tonight. I'll try what you said and report back. The *new* r17 profile you posted. Will it be play to use with r18 or do you recommend r17. Thanks man!
[G3 Android Development] EternalFlame:
Haven't tested it on R18 yet but you can give it a shot if you want.

No problem and good luck dude :)

[MENTION=1924380]xocomao[/MENTION]

Cool but remember i am still experimenting with this stuff bro so if you figure something out let me know ;)
[G3 Android Development] xlxcrossing:
I'm unfamiliar with the setting in which the first core runs at specified governer and the other 3 run in conservative mode.
[G3 Android Development] xVermicide:
Edit: I solved my power and volume button failure by taking the phone apart and resettling the power button.
[G3 Android Development] Meneldur:
Well, I always experienced bootstuck moments when fiddling with modules and changes in Xposed. Using Greenify and Text Aide only for months without problems. Added Download Status hack (working for everyone) and the issue is back, hard to pinpoint.

Xposed is a jewel but it has its issues still at least for me.

Mnldr/D855/CM12.1
[G3 Android Development] maximusmullivan:
Could be a hardware issue

Sent from my Nexus 7 2013
[G3 Android Development] corywf:
I choose the .tgz file and hit the check-mark but Synapse didn't restart. I then hit "restore profile" and Synapse restarted. I hit the X after that and all the settings were set correctly.
[G3 Android Development] EternalFlame:
Yep yep yep, my bad, thx !
[G3 Android Development] gmetz:
Still having the black screen after lg logo during boot. This is happening only when charger is connected and phone temp is around 75c (this is the temp is see in twrp). When I get this black screen the only thing I can do is to pull out the battery in order to get out of this state.

Currently I'm making sure not to have the charger connected while rebooting.
[G3 Android Development] EternalFlame:
edit: whoops uploaded the wrong one :silly:

__

**update, tested with R18 only**

CPU:

min: 345 MHz

Arch Power: Off

HOTPLUG:

Intelli Hotplug Driver: Disabled

Msm Hotplug Driver: Enabled

min: 4

max: 4

boost: 4

Screen Off: 2

Boost Lock: 1ms

Down Lock Duration: 3500ms

History Size: 1

Fast Lane Load: 0

Offline Load: Disabled

I/O:

Read-ahead size: 1024 KB

I/O Scheduler: FIOPS

Software CRC Control: Disabled

NR Requests: 1024

Memory:

Z-RAM: 100 MB
[G3 Android Development] mrgian:
Do this profile work in f400k?
[G3 Android Development] EternalFlame:
Can only test on D855, so i don´t know :(
[G3 Android Development] m1trand1r:
Try and tell others :)
[G3 Android Development] EternalFlame:
Yeah, you could also try my new "beta" profile. [MENTION=4547843]mrgian[/MENTION]

If it works well, i can add the device Model-name to my post.

Cheers :)
[G3 Android Development] 777jon:
New Update!

R19

* Linux 3.4.109

* Update to latest CM Kernel

* Merged KCAL driver updates

* Merged zzmoove updates by DEV

* Merged alucard hotplug updates by DEV

* Cleaned cpufreq governor code

* Interactive governor updates

* Full changes: https://github.com/777jon/g3_kernel/commits/lp-release

Enjoy :)
[G3 Android Development] Psycho_Crazy:
Downloading! Keep doing that awesome work.

Enviado de meu LG-D855 usando Tapatalk
[G3 Android Development] mrgian:
What app are you using? I have Synapse installed but it says like this..

Any idea what's the problem of the app?
[G3 Android Development] ilooze:
Did you flashed UKM_Synapse.zip?
[G3 Android Development] mrgian:
I did not, forgot to do it. I was on Nebula then shifted to 777. Right now im using Kernel Aditor and its working fine.
[G3 Android Development] brolic925t:
Wowww. Idk how much better this kernal could get... On 18 I was running on zzmoove at 2.4 with msm hotplug and simple GPU gov at 578 with multicore power saving off. Now I'm running on zzmoove at 1.9 with alucard(was really laggy in 18 but is now fixed) and multi core power saving ON with the same nexus smoothness. 6p comes out tomorrow and I don't think I'm getting it anymore as they don't have SD, removable batt, LCD display or ois for cam. And those bezels are rediculous. I'm set till the g5 comes out. Ty once again jon

Edit: went back to msm hotplug. Still think its the best
[G3 Android Development] DominatingSystem:
What download manager [MENTION=4794976]777jon[/MENTION] use? (see picture of his post)
[G3 Android Development] blmvxer:
BFQv7r9 is out also if you wanna patch for the next day update. I'm about to patch it with my x86/64 kernel.
[G3 Android Development] xocomaox:
Thank you for all the hard work you put in to make us happy with custom, tweakable kernels!

I do have a question for you.

The CM kernel seems to have the proximity sensor functionality broken while the screen is off for the vs985. I cannot verify other G3 variants as I do not own them. I've heard people with other variants claim that it works fine for them, but I'm not very reassured.

When the proximity sensor is covered, the screen should never turn on when you double-tap. If you hit the power button while the sensor is covered, the screen will turn on for a second but immediately turn off. This have never worked correctly since I've been flashing AOSP/CM based firmwares and kernels. This was actually verified in the CM forums by a helpful member. I've had two different vs985's and both have acted this way. Since everyone seems to be pulling from CM, I figured that was the root of the issue.

Do you know enough about kernels and that low level hardware functionality to look into why this doesn't work? I'm not getting much response from the CM team.
[G3 Android Development] closee91:
where's the .zip? I thought the ukm was built in
[G3 Android Development] iksander:
Thank you!

It runs like a Nexus device now.
[G3 Android Development] kr3g3r:
Running amazing with these settings… R18 was a nightmare for me… so far so good with R19 and this set up
[G3 Android Development] EternalFlame:
Thanks for the feedback guys i really dig it ;)

[MENTION=4794976]777jon[/MENTION]

R19 feels to have improved a lot, i luv it, big thanks to you Sir :good: :victory:

Made some little changes in my setup tho (no need for update if all works well for you, nevertheless, i recommend to disable Z-RAM because its just a battery killer without benefits.)

Change log:

CPU:

Min Input Interval : 100ms

I/O:

I/O Scheduler: noop

MMC Clock Scaling Control: On

NR Requests: 512

Memory:

Z-RAM: 0 MB = Disabled

Misc:

TCP: Westwood = (10mbit+ speed in my case)

I checked it out with this App

How to test: Run net speed tests with each protocol at least 3 times to compare the average.

As always, Enjoy :)
[G3 Android Development] :
Because it is not even coded. CM and roms based on it do not check proximity sensor readings after receiving an event from lpwg_notify on g3...

When they tried to enable it, it broke the DT2W.

That is the main commit for it.
[G3 Android Development] xocomaox:
Ah, thanks so much for the information! I was afraid it would come down to a lack of talent. :(
[G3 Android Development] closee91:
[MENTION=4794976]777jon[/MENTION] does not have a lack of talent ?
[G3 Android Development] schwem:
[MENTION=4794976]777jon[/MENTION] loving the latest (R19) build for my vs985. One small (not sure if it's an issue or....) feature. The sweep to sleep setting in this build is super touchy and functions in any app on any screen. Say I'm scrolling homescreens. Sweep to sleep kicks in even if only swiping an inch or so. It didn't do it in any other build but I notice myself putting the screen to sleep alot of the time. Any reason for this? Or anyone else experiencing it?
[G3 Android Development] abezzilla99:
Hey just wondering if there were any settings in this kernel to lower screen power consumption. I am not sure if any exist but thought I should ask some people with better knowledge on kernels/kernel tweaks. :)
[G3 Android Development] Psycho_Crazy:
Using your profile... Let's see how good it is for me.

Thanks for sharing
[G3 Android Development] xocomaox:
Stop sweeping from the nav bar, lol.
[G3 Android Development] Slothboy:
Bench mark results with r19 kernel and settings
[G3 Android Development] schwem:
Funny but not even close to the navbar. I can scroll side to side anywhere on the screen and it does it. Mostly only when scrolling to the right but it happens literally anywhere on the screen.
[G3 Android Development] xocomaox:
That is very strange, and probably not acting correctly. I've found that if you disable that option in the kernel editor of your choice, it still doesn't disable it. Have you tried turning it off?
[G3 Android Development] schwem:
Just tried turning it off with kernel adiutor and it still swipes to sleep but I just tried reflashing it and clearing cache and the problem is gone for now. Weird. Not sure what was going on there but hopefully it stays this way. Swiping the navbar still puts it to sleep but it doesn't do it on the rest of the screen now. Thanks for the suggestions.
[G3 Android Development] xocomaox:
I've never seen that before, especially from the other areas of the screen! I guess a cache clear probably did the trick...
[G3 Android Development] schwem:
I've never seen it either and man was it frustrating. Every swipe over one inch long like switching homescreens or swiping the keyboard letters to make a word would shut the screen off. Weirdest thing I've ever seen. It's now working as it should but it was extremely frustrating. Oh well, it's gone now and hopefully it's gone for good.
[G3 Android Development] pikachukaki:
Is there any other settings for this kernel....cause with the settings on OP its very laggy sometimes and drains a bit fast.....
[G3 Android Development] goatlaw:
4000+ posts and you are not able to use the search function? Respect !
[G3 Android Development] pikachukaki:
4000 posts and you couldn't just answer... Respect
[G3 Android Development] goatlaw:
You do realize you sound absolutely premature + you clutter the Developer thread to death with your nonsense.

Please stop it and use the freaking search bar (or Google "how to use a search bar") for more information.

Feel free to delete this post @ XDA Mods - Thanks.
[G3 Android Development] brolic925t:
Nvm all is good. Made some edits to your setup (to save more battery) thank you for this. BTW is max suspend frequency max screen off clock speed? And does msm limiter have to be checked to apply the speed I chose?
[G3 Android Development] EternalFlame:
No problem you´re welcome dude.

Yes, Suspend Max Frequency = Screen Off Frequency, for that you have to enable MSM Limiter.

Cheers :)

edit: funny that you mention it tho, i just made an "setup update" with this particular option enabled (i´m using jon´s default values: 1728 MHz / Suspend Time: 10)

Let´s see how it works out.

As always, enjoy and happy testing but please check those Values once in a while just to be sure everything is correctly applied as it should ;)
[G3 Android Development] closee91:
yayyyy a new [MENTION=6149253]gr3ud[/MENTION] profile ? :good:
[G3 Android Development] Psycho_Crazy:
I got no lucky with [MENTION=6149253]gr3ud[/MENTION] settings...battery drain more fast, more heat and slow antutu :(

Thanks for sharring anyway.

@

My own profile are attached here...if anyone want to test.

Sorry , my english is not so good:silly:
[G3 Android Development] EternalFlame:
Hehe, i hope you like it, but i wasn't that delighted somehow so i made some changes again, also, i disabled that "battery saving/off screen frequency/MSM Limiter feature" because it made my phone somehow laggy, don´t ask me why, but as you all know that is absolutely not acceptable for me, so back to pure performance, woooo :p

Well, sad to hear bruh, maybe "v3" feeds your needs but I would not rely on Antutu scores only because i come from a Moto 4G and it was smooth as hell after i tweaked the * out of it, but it scored waaaay under the "default" score tho, since then i don't believe Antutu or any of those benchmarks anymore, despite that if you're having serious heating issues i recommend some thermal paste or the "copper shim mod", believe me you wont regret it.

Cheers.

--

Change log:

MSM Limiter: Disabled

Boost interval: 5000 ms

Input Boost interval: 5000 ms

Load Based Syncs: ON

Migration Load Threshold: 1

Frequency Throttle Temperature: 80c

Read-ahead Size: 1024 KB

I/O scheduler: row

GPU min Frequency: 27 MHz

Drop Caches: ON

KSM: ON
[G3 Android Development] Psycho_Crazy:
Antutu is just a parameter for me... I don't believe to.

My profile solve my heat problem, now when I browsing the web the temp still 45°.

Thanks
[G3 Android Development] osama bhatti0:
Hey i just read a comment below he said it crashed on resurrection and reply came that resurrection is cm this is for aosp. Can't i use it in CM12.
[G3 Android Development] schwem:
This works for CM based roms as well. I use it on AICP which is entirely based off CM.
[G3 Android Development] fmehdi:
Back to 777 Kernel :laugh:

im testing now R19 on my d855 16go
[G3 Android Development] kr3g3r:


I just started using synapse… do I flash your .zip file?
[G3 Android Development] Psycho_Crazy:
No! Extract the gz file on to profiles folder, after that open synapse, navigate to profiles settings and restore the gz profile.

Yes, i now...my english is very poor.
[G3 Android Development] brolic925t:
[emoji30] [emoji30]
[G3 Android Development] EternalFlame:
Just in case you haven't figured it out yet ;)

- Move .tgz file to your Internal storage > Synapse > saved_profiles

- Profile > Profiles > choose .tgz file > press "check-mark" and not "X" > choose "restore profile"

- Synapse will restart and then press "X"

- Check all values and if you have to change something press "check-mark"

Cheers man !
[G3 Android Development] Psycho_Crazy:
I'm on last build and my phone overheating when download using wifi. Sometimes the phone power off due high temp.

Enviado de meu LG-D855 usando Tapatalk
[G3 Android Development] EternalFlame:
Hmm, i´m facing some weird behavior since yesterday with R19, after rebooting the device i get a "JSON configuration parsing failure", after another reboot it works as always.

Solution (worked for me) :

- boot into recovery

- wipe Caches

- reboot device
[G3 Android Development] Eun-Hjzjined:
I get it as well. I just clear synapse cache (from app info) and then it works... Until it decides not to again.

4 8 15 16 23 42
[G3 Android Development] Ferretx:
Hey bro, trying out you're R19 beta profile, running like butter :D
[G3 Android Development] mikekoke:
Hello everyone I put the kernel a few days ago but when I change the frequency settings and go from kernel Adiutor these are lost, how can I solve?
[G3 Android Development] kniffo80:
I think, u have to use Synapse ...
[G3 Android Development] kniffo80:
Nope. Also Synapse doesnt stick :(
[G3 Android Development] fuson1979:
Did make sure to set SElinux to permissive, if you have disregard. If it's a dirty flash, that has caused it for me, clean flash was the only thing that worked for me, beyond that not sure what else if could be.
[G3 Android Development] fuson1979:
Ok did ask the searching that I can on this thread, and can't seem to find the right answer, just switched over to resurrection remix to check it out, and kind am to figure out if this kernel will work with that rom or not, it's cm based so I assume that it should work, just don't want to ruin my phone by guessing, any info is appreciated thanks in advance
[G3 Android Development] Tech_Savvy:
yes this will make it fly :)!!
[G3 Android Development] fuson1979:
Thanks, was hoping it would, been using this kernel on euphoria for a few months, didn't want to move on without it.
[G3 Android Development] Meneldur:
I love this kernel. Made CM12.1 fly on my G3.

But caused BSODs, dunno why since there were no last_kmsg, once per day.

Are there antagonist settings I shouldn't activate simultaneously? Tried many governors and schedulers, all hotplugs (only one per try), used boost to 1497 MHz and 500 ms minimum and very aggressive LMK (as now with CM kernel).

Mnldr/D855/CM12.1
[G3 Android Development] 777jon:
New Update!

R20

* Update to latest CM Kernel

* Add alucard, darkness, and nightmare governors

* Replace cpu-boost with alucard touch boost

* Enforce stock max frequency on boot

* Upgrade msm limiter to version 3.8

* Merged SELinux updates

* Merged msm: vidc updates

* Merged tcp_cubic, vfs, proc, and uid_cputime updates

* Full changes: https://github.com/777jon/g3_kernel/commits/lp-release

In this update, I added alucard, darkness, and nightmare governors by Alucard24. Replaced old cpu-boost driver with new and super fast alucard touch boost. I also upgraded msm limiter and fixed the issue when frequency goes above stock limit on boot.

Thanks for your support! Enjoy :)
[G3 Android Development] yanowman:
Could anyone shine some light on the effectiveness of the new governors?

alucard, darkness, and nightmare governors
[G3 Android Development] 777jon:
Here's a fantastic guide to CPU Governors to read:

http://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
[G3 Android Development] Slothboy:
Alucard seems promising thanks to that explanation, in theory that governor with the alucard hotplug should be a perfect combo!
[G3 Android Development] brolic925t:
Mmm zzzmove n alucard with msmhotplug ?
[G3 Android Development] i_pk_pjers_i:
Oh my god, thank you so much for a new Kernel! Your work is absolutely amazing.

I can't wait for a new Gr3ud profile, maybe Gr3ud can try out the new governor with the new hotplug.
[G3 Android Development] akaHardison:
The best kernel I have used since Feb.Thank you so much.
[G3 Android Development] EternalFlame:
So, here we go, R20 setup is ready.

I was pretty busy the last weeks tho, so its more like a small update, alucard rocks BTW, thanks [MENTION=249210]Jon777[/MENTION] :good:

And as always, enjoy :)

Change log:

Debug Mask: OFF

CPU Governor(0-3): alucard

Boost Lock: 5000ms

Down Lock Duration: 5000ms

History Size: 1

Fast Lane Load:0

Offline Load: 0

Suspend Defer Time: 0

I/O Scheduler: Zen

No Merges: All

NR Requests: 128

WIFI Scan Interval: 300 sec

SELinux Status: Permissive
[G3 Android Development] metalgearhathaway:
I'm with you there, my tests on alucard governor with alucard hotplug are proving to be great combination! Only difference in our configurations is that I prefer noop to zen.

Happy days :beer:
[G3 Android Development] EternalFlame:
Nice man, i´m still with Msm hotplug tho because i wanted to play with the alucard hotplug driver values later this week, so, this update is basically R19v4 :p

Anyhow, are you using stock values or did you change something with alucard hotplug mate ? Oh and i just switched back to zen for a better multitasking performance ;)

Cheers :cool:

edit:

Okay, i made an alucard setup for those who want to try it, performance-wise i could not find any big differences for now, both hotplugs (msm / alucard) feel very smooth to me, guess its a "battery-thingy" now?

Nevertheless, happy testing :)

Change log:

Msm Hotplug: Disabled

Alucard Hotplug: Enabled

Hotplug Suspend: Enabled

min CPUs: 4

max Cores Limit: 4

max Cores Limit Sleep: 2

Frequency 1_1 - 4_0 : 2457 MHz
[G3 Android Development] Slothboy:
I think what you get with the alucard hotplug is a bit more control over when CPUs come online or ramp up, and what it takes for them to do so load percentage wise, this might take a lot of time to think through for our G3's like optimimal frequencies for each percentage of load, but there we go :)
[G3 Android Development] metalgearhathaway:
The only changes I make with the hotplug configuration is to allow 2 cores to be enabled during off screen action.

I had not considered io multitasking performance, do you notice a specific difference when using zen in these scenarios then? :good:
[G3 Android Development] StDevious:
Do I need to flash this profile on top of the kernel in recovery or is there another method to this?
[G3 Android Development] i_pk_pjers_i:
You extract it then copy the file to your saved_profiles folder on your sdcard under your Synapse folder.
[G3 Android Development] StDevious:
I see, I looked up Play Store and assume I need to install the Synapse app for this? Is there any way to use the Kernel Adiutor app with this?
[G3 Android Development] i_pk_pjers_i:
No idea, everyone just uses Synapse when they are using Gr3ud's profiles.
[G3 Android Development] xaoup:
will thid work on the flyme os port for G3? i tgink its cm based.
[G3 Android Development] m1trand1r:
You should make Synapse profiles thread ...