yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] vPro97:
Hello again and thanks for reading my report.

Yes, I've tried switching from dalvik to ART and vice versa without much luck. Before going to sleep, I figured that the screen would become responsive again if you wait 5-10 seconds. For some odd reason, this issue mainly occurs when browsing phonearena.com. I'll try to give it more time to see what might be the issue - it might be an app or a setting that's interfering with the kernel (settings).

I'm anxious to try R22 :)

Thanks a lot for your great work so far.
[G2 Android Development] RenderBroken:
I will try browsing the same to see if I can reproduce. Thanks!
[G2 Android Development] vPro97:
You are an amazing person!
[G2 Android Development] RenderBroken:
Don't tell everyone! Jeez, they will expect that out of me all the time! Lol thank bro. I truly do this because I love learning and sharing knowledge.
[G2 Android Development] jriv:
Switched to blackbird kernel with latest Ls rom not happy with battery coming from ur r21 thinking of going back was trying to wait until r22 but only getting 3hrs sot with blackbird was getting over 4hrs with r21
[G2 Android Development] vPro97:
Tbh Render kernel R21 has been fantastic in terms of battery life. Currently at 52% with 3h SOT and 12 hours of usage. I'd say that's pretty impressive.
[G2 Android Development] RenderBroken:
Thanks Gents! I have to agree. REV3N and I are friends and we chat in Hangouts all the time. we both have different views about our kernels and thats great! Its cool to bounce ideas off someone who doesn't think exactly like you do. So in saying that, I had seen some few people say that they get better battery life with his kernel but I don't see how. essentially when you drop the shade or touch the screen, almost every core gets onlined which could be less lag but more battery life is taken. I know right now mine will stay at 1 core til needed otherwise and I am going to bump that to 2 to reduce any micro stutter. I have been testing and I have been pretty happy with the results with negligible loss to battery life. So it is good to see others agree and I am not going crazy.

Apparently LG has completely hacked their way through the touch drivers so nothing is going right. I do have a question that I would love for others to chime in on. Right now it takes me 5 taps to turn on the phone. How does it work for you all? Also I am going to put DT2W work to the side to hen finish up and polish R22.
[G2 Android Development] bleached45:
I know for me DT2W is all over the place. But it works better than the back button (this is on AICP, I don't remember how mahdi differed). Sometimes I get it in 2, sometimes I don't and if I press a third time it vibrates (which means the touch is felt but display doesn't turn on). Usually if I tap a little slower though it turns on after 2. Or after a second after 2 taps.
[G2 Android Development] blacklight1025:
It takes me 2 taps most of the time. It takes 4-6 sometimes right after a charge session.
[G2 Android Development] Matze060906:
I was running R21 with the previous build of liquid smooth. I tapped alway 3 times to wake the phone and it worked ever time. Now I'm running latest ls with latest b1ackb1rd kernel. I need only 2 taps to wake the phone. Rev3nt3ch had built in an option to set dt2w via trickster mod. I set it to 2, this means dt2w works anywhere on the complete display.

Hope you will release r22 soon, can't wait to test it. It's pretty good, that we all have a choice between 2 awesome kernels.
[G2 Android Development] mazroui:
Back to Aosp after a trip back to stock for some HD videos. 2 taps running v21 here with alegen rom .. All good except for battery life.. Need more tweaks or maybe new version will give us more ☺ anyways best of luck with the progress
[G2 Android Development] vPro97:
To be honest whether DT2W takes 2 or four taps is not a major problem as long as the phone sleeps like a baby which it does. I often have to double tap, pause, then double tap again for the screen to wake up but it was never much better on stock roms so I don't mind.

It's going to be great to have another core online - I recall dr87 saying that it was better to have 2 cores online always than having the second core hotplugging all the time. I have also experienced microstutter when browsing Facebook or 9gag in Chrome but those kernels which were smooth and fluid never lasted me a full day with 40 percent left.

It's going to be interesting how R22 turns out to be.
[G2 Android Development] Formhault:
[MENTION=5438598]RenderBroken[/MENTION]

Perhaps you could make the touch boost tunable from Synapse in future builds? So we can change things like how many cores get activates and at what frequency they are boosted at etc.
[G2 Android Development] :
Hi, I'm new today to this kernel. Seems great so far. :D Only thing that concerns me is the temp settings. Some of those temperatures seem scarily high! Can anyone explain the thermal settings a bit more clearly? I don't want the temperature higher than 78° ever. Thank you.
[G2 Android Development] fleeting_dreams:
Render posted a screenshot of temperature settings a few pages back.
[G2 Android Development] :
Thanks I saw that. Still too high for me though. Think I've sussed it now. Cheers. ;)
[G2 Android Development] RenderBroken:
The ability to do so is already there. So the hotplug decides how many cores are boosted. So look there for that and I believe at the bottom there are the actual "Boost" parameters. Right now it is set so when a core is hotplugged it will start a that certain freq instead of starting at 300MHz. There are numerous different settings you can tweak to get the performance you are looking for. Sorry I am not more descriptive, I am still testing and Synapse is borked in my test build becasue I am changing things around a bit. I will be changing up the default settings for R22 to allow for better performance while using the phone but same battery savings when not.

What settings would you use?
[G2 Android Development] :
I've set it like this. Shutdown is at 80° Seems OK so far, done stress test and monitoring freq and temperature with perfmon and cool tool. My fear is screen damage. I believe these settings will be ideal for my usage. Might install real racing and see how these settings go with that. Thanks for your work with this kernel. I've always used dorimanx but he doesn't compile for aosp and I'm not partial to stock LG.

Edit: Well I would install real racing, seems its not compatible with my device. May be dpi issue.
[G2 Android Development] crnkoj:
Using r21 with stock settings and some uv and uc and a rather old Mahdi rom (8/17 or so) and dt2w always works on 2 taps
[G2 Android Development] RenderBroken:
Putting in some last minute touches. . .

I have enabled Power Effecient Workqueues. This should help increase batterylife. I even added an option to Synapse to enalbe/disable it. If you want battery leave it enabled, if you want more performance disable it but keep in mind I have been using it in my own test builds and have seen 0 impact on performance and a gain towards battery. Your milage will vary. Merged in some upstream changes to PM. This should also help with batterylife. New list of governors:

HYPER

Intelliactive

Bacon (Simplified Interactive / New default / battery friendly)

Conservative

OndemandPlus

Ondemand

Powersave

Performance

You now have the options you need to setup whatever profile you want in Synapse. Soon I will be asking for each others profiles. I will send instructions on how to upload them. The gist is you setup your settings in Synapse and there is a profile tab that you can save your settings. It creates a file that could then be uploaded. I WILL include user created profiles in my kernel and WILL give credit to the User. Still I have Final say but I can add many profiles. I am excited about this prospect. When I was on the S2 there was something similar called STweaks and it had profiles there too and I loved how just changing said profiles could either give me major battery or performance.

Of course there are NUMEROUS more changes that I have made since the last release but will name them at a later time or take a look at my kk-rebuild branch. Which will be merged into Master when I release and will make it easier for those of you who like to build this kernel themselves. I will keep it so Master is complete and when you build it there will be no errors in doing so.
[G2 Android Development] Matze060906:
Still waiting for release. No optimax? [emoji20]

Hope bacon will be a good alternative...
[G2 Android Development] RenderBroken:
I am glad you said something, it should be in the list as well. MAy just have to re-enable it on my end. Its already in my source.
[G2 Android Development] :
I have used bacon on bart452's aosp dorimanx kernel. It was very good although my personal favourite is alucards governor. Look forward to next version of this kernel now though. R21 has been flawless on my d802 with the above thermal settings and uv 15mv. Very happy customer thank you. [emoji2]
[G2 Android Development] RenderBroken:
Yea I even have the thermal settings lowered in my test build as well so in the next build they will be tweaked lower just a bit.
[G2 Android Development] vPro97:
Render, may I (we) ask for darkness/alucard governor? For me those two are conservative but extremely responsive and fine tuned governors.
[G2 Android Development] RenderBroken:
Maybe . . .

I can at least give them a shot and see if they fit in the grand scheme of this kernel
[G2 Android Development] jriv:
+1 alucard is and awesome governor for our phone works really good when I was running g3 rom
[G2 Android Development] RenderBroken:
I am building now. I am also trying to rebuild my Defconfigs to allow me to have better control over what I can add or remove from the kernel itself. This way i can start disabling loggers that are not needed for example. I was able to add in Optimax but not the others that were asked for. I started the process though. There will need to be more done to make those governors work with my kernel so it will have to wait for now. I will slowly be building from this point forward.
[G2 Android Development] Matze060906:
Hope I can test as soon as I can. I must send my phone to a repair service, my phone falls down from the table and the display is broken. Hope I will get it back soon...
[G2 Android Development] RenderBroken:
UHG, sorry to hear. . . that is why I immediately bought the Ballistics drop case that is good for 5 feet. lol I drop my phone ALL THE TIME! This has been the best case I have ever had and has saved my a lot of money. Hope you get it back asap.
[G2 Android Development] Matze060906:
I have a bumper case from cruzerlite. I had put the phone out of it to clean it. Then my son (1,5 years old) drops it from the table...
[G2 Android Development] RenderBroken:
I really think you guys will like the smoothness and battery life of this next build! Also reworked Synapse a bit. Removed useless stuff and added a couple things.
[G2 Android Development] :
I have my profile ready for sharing when you're ready.
[G2 Android Development] RenderBroken:
Sweet! Just create a post noting the main differences you have made and the name for it. Then just upload it with the post.

I will soon post instructions on gathering the profile. Right now I have had to completely restructure Synapse and corresponding folders so the profile will no longer work but I can still have you send it to me to be recreated.

Synapse opens a whole new world for this kernel, next would be to start coding a system for creating scheduled tasks (cron jobs) then we can setup fstrim and other utilities to keep our phones in tip top shape! Just wait. . .
[G2 Android Development] :
Sounds great! I'll keep tweaking with this version and send you a profile when the new build is released.
[G2 Android Development] vPro97:
[MENTION=5438598]RenderBroken[/MENTION].

I have been waiting for R22 for days now. I have rarely been this excited to try a new kernel. I. CAN'T. WAIT! =D

Thanks for being so open to suggestions!
[G2 Android Development] RenderBroken:
Guys I am so close!!!! I am ready but noticed the MISC tab in synapse is not showing for some reason! Lol I can't have that in a release! I am headed home and will see if I can fix, if not I will release without.
[G2 Android Development] jriv:
Ugh the wait is killing me what do u recomend for battery ive been using ondemand I feel its better battery than ondemandplus
[G2 Android Development] RenderBroken:
I know. . . I could release but I am expecting to have a fix soon for the last piece holding up release. Ondemand is a classic for battery with little performance loss
[G2 Android Development] RenderBroken:
I have started uploading the Non-OC builds. I will build the OC ones tomorrow. Also I will update OP with all new changes and such tomorrow as well. I still have not fixed the missing tab in synapse but it is not an important one and I know yall have been waiting patiently.
[G2 Android Development] allan1229:
Running really good so far. Thanks for the hard work
[G2 Android Development] :
Seems super smooth so far. Will report back in a couple of days.
[G2 Android Development] vPro97:
Wow, you've really put the kernel in another league with the R22 release.

Underclocking to 96 Mhz, more governors, better settings - just wow!

Since your kernel is one of the few that supports GRAM and allows the GPU to go all the way down to 27 Mhz, I'm expecting amazing battery life!!

I'm sorry to let you know that I'm having still having the "hanging" issue in Chrome. I have now tried giving the foreground app some more memory to work with and upped the value from 10 MB to 128MB. Let's see how that goes.
[G2 Android Development] RenderBroken:
Are you having the issue with the same website, Phone Arena?
[G2 Android Development] vPro97:
Yes bro. It's mainly just that site. I haven't encountered any issues since I changed the memory limit so we'll see.
[G2 Android Development] 1ceb0x:
I am curious... how did you come up with the conclusion that this kernel uses GRAM?
[G2 Android Development] RenderBroken:
Starting OC Builds now. Just remember this will not happen every single build but I will do it on select builds when I feel like it. I know there are some of you that want OC. Here you go. I will be experimenting with it as well. Such as, instead of onlining 2 cores on touch (Boost) I would take it back down to just 1 core but let it ramp up fast. Maybe 1 core at 2.5 or more GHz will perform as well as 2 cores online at 1.2Ghz but with better battery. I am always curious to explorer and I will give it a shot. Those of you who want OC can do the same and report back in the thread. Bare with me for now, I Will need to do a little clean up of my source and Defconfigs I use before pushing to Git. I will do so today. So to recap R22, There are a huge number of additions:

Updated to Linux 3.4.104

Underclocking!

Overclocking (For Select Builds ONLY)

Optimized Memory Utilities from Motorola ported over to msm8974 by Neobuddy89

Added Govs: Optimax, HYPER, Bacon (Default)

Updated Fast Charge to 1.3 to give more control to the user, thanks to Dorimanx (Still need to do more work)

PM Subsystem Update from 3.5 Upstream changes

Enabled Power Efficient Workqueues by default now. (Better Battery)

Numerous changes to certain files to better power savings through the use of macros cpu_relaxed_read_short and cpu_relaxed_read

Sound Control updated to 3.5 and Support by Synapse!

Lower Temp Thresholds to allow for cooler phone.
[G2 Android Development] vPro97:
Has anybody noticed an abnormal standby battery drain? BBS is showing that the phone is entering deep sleep as it should and there's no rogue app running .
[G2 Android Development] Formhault:
GRAM still isn't functional on AOSP, is it? :(
[G2 Android Development] vPro97:
It's pretty simple. If a kernel supports GRAM the GPU will idle at 27 MHz instead of 200 MHz.
[G2 Android Development] RenderBroken:
Like what kind of numbers you getting?

My understanding is its enabled by default and is just part of the panels source code. Not something that the kernel actually dictates.
[G2 Android Development] :
+1 Thought it might just be me. Going to give it a couple of charge cycles and see if it settles. To give an idea I got home from work yesterday with r21 and had 72% battery left. Today with r22 and similar (maybe slightly less) usage I have 31% left.
[G2 Android Development] vPro97:
Have a look. It used to be quite a bit better =)
[G2 Android Development] RenderBroken:
Thanks, I will take a look to see what may be the cause, I do know that I have the number of cpus boosted changed to 2 in R22 instead of 1 in R21. But that would only effect while screen is on. The issue really seems to be Standby right? I may have to revert some upstream changes. Still I was planning on releasing R23 soon after R22. I wanted to see what everyone thought of the newer changes and adjust accordingly. thanks for the report!
[G2 Android Development] vPro97:
My results on r21
[G2 Android Development] :
This could be part of the problem possibly. Seems excessive to me?
[G2 Android Development] RenderBroken:
Ahhgg, I found the issue. Need to remove a couple nefarious changes that were made last minute. I will rebuild and release R23 tonight. It will not be a whole lot different from R22 except with proper sleep/battery drain and a few fixes in Synapse. Maybe I will tweak a little more, who knows lol. Just wanted to give a heads up. Now I am debating on whether or not to leave R22 up.
[G2 Android Development] ckyy:
Had 3 reboots within 6? hours of flashing r22 on LS 10/10 for D802. Twice while watching a video and once while waking the phone up. Can't provide last_kmsg because it's empty for some reason.
[G2 Android Development] RenderBroken:
Might be related to the battery drain issue. the devices cannot suspend properly. Still I have not had any reboots but thanks for reporting. Also I use LS as well but I have the D800. Any other changes you have made from the Default settings?
[G2 Android Development] ckyy:
Yep.

Governor : Ondemand

Multicore Powersaving : Aggressive

Max CPUs screen off : 1

I've forgot to mention that they were hot reboots.
[G2 Android Development] RenderBroken:
So like, no LG Logo?
[G2 Android Development] hotbbq:
I am attempting to tweak the interactive governor in Synapse and I see some strange values for some of the fields. For instance, above_hispeed_delay looks like

20000 1400000:40000 1700000:20000

I was expecting a single number here. Others include check_fast_target_loads and target_loads. Any ideas?
[G2 Android Development] vPro97:
Also, I'd like to say that I haven't had any of these "unresponsive screen" problems since allowing more memory to the foreground app. The general performance has also improved. Maybe 128 mb is overkill but it's doing its job.
[G2 Android Development] RenderBroken:
OK I think I found the cause for this too. . . Another last minute change I made yesterday so it will be reverted as well. Thanks for your help.

So I am using a merged version of Interactive that merges Interactive and Interactive PRO that had come out for a short time. That is where:

check_fast_target_loads and target_load

Comes from. Also the other sysfs entry is tuned so that the delay value changes as the frequency changes so:

20000 (Default Value)

Freq = 1400000 sets selay to >40000

Freq = 1700000 Sets delay to >20000

The above values just make the governor more relaxed in lower freqs and more responsive when in higher freq. Makes it not just jump to high speed freq all the time. Lets the governor do its job.

Interactive and governors based off of it have this ability so you can tweak it to your liking as well. I have it tweaked for more battery than performance right now.

Hey if it works for you thats all that matters right? lol
[G2 Android Development] Formhault:
That's awesome.

And... has anyone tested it? Just curious what the outcome might be :silly:
[G2 Android Development] RenderBroken:
Newest Test build is running great. No more hot reboots. This was caused by a commit dealing with L2 Cache. Since removed I have had not issues and phone actually goes into deep sleep. So I will continue to test. Also I am updating the Wifi Driver for R23. Might as well add some more goodness other than just fixes.
[G2 Android Development] RenderBroken:
Lol guess I have been too busy to notice just how bad battery was in r22. It's much much better. . .
[G2 Android Development] RenderBroken:
You had a Sleep of Death? Or just a Reboot? What is your Device Variant and Rom you were using?

What is your Device Variant and Rom you were using?

I really need last_kmsg's from you guys. Best way to get them to me is to use Syslog from the play store. After the reboot just open it up and iit will create the log in need. Thanks guys!
[G2 Android Development] Raagh:
Guys if you re using latest mahdi be careful. Latest builds had report reboots on stock kernel and settings. So could not be render kernel.
[G2 Android Development] simon_lefisch:
What build do you speak of? Yesterday's build was like that. Dr just released another build today but haven't heard any reports of reboots.
[G2 Android Development] Raagh:
Yeah taking about 7/7 or 7/8 sorry. I rolled back to 6/28 that was stable.now im downlading 7/9
[G2 Android Development] RenderBroken:
Building test builds now with modified hotplug driver. IF you want to try it out feel free. All I ask is if you are going to test it out and want to post about it. Please clearly state FIRST, what version you are talking about. Thanks :)
[G2 Android Development] Raagh:
Can you explain me what re the modifications and whats the idea behind the changes?
[G2 Android Development] RenderBroken:
Mainly its just a test of the hotplug driver that has been modified to go down to 1 core while idle. Thats mainly it though there has been more work done for R3. Some other Subsections that I have been working on.
[G2 Android Development] Raagh:
Thanks ll test it an report
[G2 Android Development] insomniakAD:
I have a D800 on Mahdi 6/28 release. I didn't know about Syslog I'll give it a shot. This is the first time I've ever reported so sorry for noobiness :silly: I'll get you a last_kmsg next time!
[G2 Android Development] RenderBroken:
Its fine, you gotta learn sometime so its no biggie. Thanks for your help!
[G2 Android Development] RenderBroken:
Uploading now . . . So far test seem good.
[G2 Android Development] hoquangthaiholy:
Hi, RenderBroken. I have a plan to build a cm11 version for F320L (because it does not have yet). But what different is between AOSP kernel and CM kernel? Can you explain to me? Thanks
[G2 Android Development] Raagh:
The test ll be on your mediafire account?
[G2 Android Development] RenderBroken:
Yes, in the Beta folder.
[G2 Android Development] RenderBroken:
Im sorry but I cannot begin to tell you all of the differences between the two on the G2. I have noticed Numerous changes that have to be made. I would just fork CM's kernel. Is there not an official build for your phone? If so then you should be able to fork their kernel and then just build using the correct defconfig.
[G2 Android Development] hoquangthaiholy:
I have some problems about proprietary files between G2 variant. So complicated. :(