[Nexus 6P General] phantom146:
[IMG="Rewriteup"]http://i.imgur.com/OJDxAYg.png[/IMG]​

To everyone complaining, I've heard you! ​

Glasscannon, is an interactive profile designed to provide smoothness and great UI performance without sacrificing battery life, or so I have planned. There have been a lot of hiccups lately which I and a handful of people are experiencing. I as the creator, is responsible on fixing this issues and providing a much better and more fluid glasscannon experience. Issues that are present should be addressed in here and will be mentioned and tackled one-by-one so that we will know what caused the problem. If you wanna test this new parameters out, please do follow the instructions and do not attempt to change them whatsoever because it will make the tests obsolete.​

​

The issues

I have compiled via pm, own experience and post related stuffs are mentioned below:

Slow wakeup coming from deepsleep/doze which sometimes leads to freezes on panic.

Slow application loading time as reported by some users, some even said that it crashes some apps.

Freezes, stutters and lags when changing from one app to another especially if there are a lot in the background.

Unintentional drops from both clusters even with high cpu load.

Bad idle drain.

A quick note from the issues provided above:

Slow wakeup from doze has been an issue not only by glasscannon or by other kernel profiles but also with the whole android system and SystemUI itself. It started appearing at Nougat update (Marshmallow rarely encountered this issue) and this has yet to be solved by google. Some discussions and proofs for these: Slow Wakeup from Doze - Nexus6p and Slow/Unresponsive wakeup from doze - Nexus5x. I however, would also blame the profile for increasing this load time, this is to be explained by "understanding kernel parameters" below.

Application loading times are all mostly user-based. Some apps are just poorly coded that the UI experience is downright bad. One for example is using SwiftKey Keyboard; there are a lot of freezes coming from this app and due to that I really suggest users to try Gboard. Users who experience stutters on updated apps are however special cases and cpu frequencies not putting small "boosts" to its cores and not recognizing loads coming from the applications are to be pointed at. Don't worry, I think I found the fix.

Idle battery drain is something I have never experienced from GC. People whom are experiencing this should check alarms, kernel wakelocks and partial wakelocks. A tool that can help you with these is: BetterBatteryStats. Also, the cpu would RARELY get to a high frequency on screen-off especially if you have a screen-off limiter. On the other hand, I might have not experienced this because I am managing partial wakelocks and alarms really well coming from my own experience so I still would like to know what the community would say.

FOUR VITAL KERNEL PARAMETERS explained:

There are four major parameters that I am looking at which in theory should fix the problems. Everyone should read this carefully and I hope you understand my explanation as to why and how it will change the way the device runs. Changing these values always has pros and cons so just a heads-up; read thoroughly.

timer_slack: probably the reason why there is some idle drain coming from glasscannon, and also the reasons why on some profiles your cat is sticking on high frequency too much. The thing is, setting timer_slack to a high frequency such as 380000 ensures faster UI experience because it will wait for 380ms before going back to "interactive" state which means it'll ramp down back from the highest frequency to a more "suitable" frequency based on timer_rate or cpu load computed at that time. However setting it too low such as -1 makes the highest frequency to ramp down as fast as barry allen. Setting it too low would cause some unstable things such as freezes and stutters because it'll contradict the cpu load computed at that time. To make things simpler: high timer_slack:

higher battery drain but smooth UI experience

, low timer_slack:

lower battery drain but slower UI experience.

This might also be the issue concerning the idle drain some people talk about. Finding the "best" spot in between the pros and cons is the one we should be aiming, please do see the beta test section below.

timer_rate: the one responsible for checking the cpu load. This thing is pretty self-explanatory; set it, to 60000 then it means every 60ms the kernel will check the load of the cpu and tell the cores to ramp up or down depending on how heavy the load is. Setting it high af would means it'll compute less often which UNFORTUNATELY with my tests should give you slower UI experience and stutters. Why? we all know that cpu loads are highly based on applications we are using. Accessing recents, going from this app to another changes the cpu load every ms.

Then higher timer_rate is good right?

NO, higher timer rate means it allows checking less and more often than not would not allow frequencies to ramp up. Let's say you are playing a CPU intensive game then all of a sudden you click on "home" then load another app. If you set it high, it'll work cpu frequency up with a much higher delay compared to a lower value, therefore not providing the "boost" we are all aiming for.

target_loads: the original glasscannon interactive parameters are pretty good tbh but this doesn't mean it's perfect. I will say this, it is coded to specifically NOT stay on the lowest frequency to avoid slow UI but there is one problem (look below)

above_hispeed_delay: the problem. Even though glasscannon had set target_loads lower than anything else, the delay caused by this parameter ensures a much slower ramp up and thus providing those stutters we are all avoiding. I find the values now are absurdly high and is a pain in my sexy butt. This should be fixed soon so please look at the test thread below.

These are my inputs so please read them. Below, you will see the beta test section where the four (4) values would be changed to correspond the issues and hopefully fix them soon. Once everything is looking good, I will post the FINAL update for glasscannon and hopefully the devs would still love the profile as much as I do.​

CREDITS:

[MENTION=5051294]frap129[/MENTION], [MENTION=6842057]The Flash[/MENTION], [MENTION=4684315]flar2[/MENTION], [MENTION=5893314]shadowstep[/MENTION], [MENTION=2489052]NYCHitman1[/MENTION], [MENTION=7494055]DEVILOPS 007[/MENTION], [MENTION=7575243]Bobbaloo[/MENTION], [MENTION=6262409]Mrcactuseater[/MENTION]