plz share you values of stweak app for better performance and battery life.if possible share ss
plz share you values of stweak app for better performance and battery life.if possible share ss
plz share you values of stweak app for better performance and battery life.if possible share ss
You could start with undervolting.
I could go as far as -100mV (for each frequency step) without the phone crashing. So I'd say -75/-100 should be good for everyone. Less heat, a bit less power consumption.
That's both for the CPU and GPU. The GPU might work even at lower voltages, but I haven't tried that yet.
Alternatively, if anyone has a better voltage table (perhaps for ABB, too?), feel free to share it
Sent from hyperspace
^ Just don't push it to far...
For cpu I've set 200-1600 Mhz limit, with 3 step down (3rd value below defaults) uv for each freq.
For gpu, freq's are default with 1 value below default for each one frequency.
Nothing else touched. Test in progress.... So far no problems.
Battery (in standby) draining like 1-2% for 6h over night (data/gps on, sync on...).
Sometimes it connects to the USB while charging. So slow charging.
Sometimes it connects to the USB while charging. So slow charging.
Or bad cable. I have probably 5-6 cables and only couple of them work perfectly with N2. On others it can discharge faster while it's charging...N2 is so picky.
Have been testing 4.3 PA and really miss Perseus' color calibration.
Andrei really should make a color calibration app independent of kernels and put it on the playstore for GS3 and Note 2 owners.
I know a lot of people that would buy it to support, I'd be one of the first ones.
I can support stock kernels with an app but I don't care for bothering updating it for each kernel version out there. Ask your resident kernel guy to just pull my changes (If he gives a crap).It relies on the mdnie interface that Andrei modified in the kernel. So it would still require a custom kernel!
Sent from my GT-N7100 using Tapatalk 4
I can support stock kernels with an app but I don't care for bothering updating it for each kernel version out there. Ask your resident kernel guy to just pull my changes (If he gives a crap).
Will flashing this kernel solve my charging issues? I'm using a power bank and i'm not getting the full 2Amps the power bank promised. Damn.
Probably.
Flash the kernel. Open STweaks. Slide to the "POWER" tab. Tick "Ignore unstable power" and "Ignore safety margin".
You should be good.
Doing that did not help me at all with the problem of cables. The cables that suck... well... they still suck, regardless of the unstable power ignore or whatever... Perhaps those cables were REALLY bad, although I find that hard to believe. Others did see a big improvement, though, so give it a shot.
Guess the chip that controlls the input current is just too smart
What rom are you using with this kernel? I'm waiting for my monoprice gold plated cable to arrive, if that doesnt work, i'll flash this. ugh.
Get your head out of your ass, it's not about disagreeing or not, it's about the facts/content you disagree on. You're don't have immunity to criticism and neither do I so don't get upset when you are being called out on something.I'll do that. And I'll be sure you get a pm when I do. Also, you won't have to worry about your device rebooting anymore.
Have a nice day folks. Sorry for disagreeing with the almighty god
The point of undervolting is that it is a disadvantage free method of gaining power efficiency, and it can bring down the dynamic power usage on the SoC down, from, let's pull it out of my ass, 20% by the best estimates from what I have measured over the last year. If you have instabilities then it is your fault in your methodology because you are undervolting too much. We are merely eliminating a manufacturers safety margin by undervolting.Some of these frequencies are set almost -100mv. Processors nowadays are becoming very efficient on power and are absolutely DWARFED by the amount of power your display, radios, and other hw uses. My own personal opinion is to look at other power consumers such as the aforementioned before playing with hw that in the grand scheme of things is not your biggest power consumer culprit, yet is vital to system stability.
No the sampling rate is not when the CPU is polled for load, it's the periods between which the governor does DVFS decisions, load is merely a statistic of the reverse of how much time the CPU is in idle.SAMPLING RATE: 28000 - just to be clear, the sampling rate is the interval of spacing between CPU being polled for load. Use this as you see fit, the small the interval, the more it checks for pending tasks to be executed. I have found great success and performance (and accuracy and decreased latency) with 20000-15000. Battery will not suffer anything noticeable to the end user.
Same thing, again, absolute nonsense as with the CPU voltages above. Internal voltage especially can bring power gains, albeit it is much less than the CPU, but it is a free gain.honestly, I really don't see the need to mess with this either. More potential instability for a minimal gain in battery when analyzed against your main thieves of your voltage - display, radios.
Deadline is alright, but noop just means that you are turning scheduling off. It doesn't bring you any performance gains at all, you are better off using an IOPS and latency designed scheduler like ROW or FIOPS (I'll bring that back when I have time), again, Deadline is ok, and SIO is a compromise of everything.dealine and noop will give you the best performance on these devices in real time, data speeds are also increased significantly with these two IO schedulers.
Maintenance, logging???!!! These are tasks that do not even remotely task the CPU even at 200MHz with any significant load, any single process out there running in the background can be done at 200MHz, it is more power efficient and you are not even aware of it.Also, if i may add this... I would recommend bumping the min frequency to something like 500MHz for the CPU. Reason being is simple - smaller tasks (maintenance, logging, etc) can be handled with ease without causing unnecessary CPU ramping.
So you see how that whole last paragraph of yours is just nonsense and that last phrase is really something one might take out of a PR article. Your settings you suggested were not given more thought.THIS is performance without battery life taking a hit - making your system AGGRESSIVE YET EFFICIENT, not hindering and crippling it to not do what it is programmed to do. Efficiency. "Less is more" as you see thrown around in the Linux world can also be thought of as more is less if you think in terms of more thought, tuning, and logic is less power consumed by your device.
Yes please do deliver your kernel, because I want to see more nonsense delivered with an attitude. We already have a large amount of clueless developers on this site. The problem isn't that they're unskilled or do not know the technical details, everybody was like that including me; It's that they think they are doing some sort of meaningful change without giving the effort of thinking or dwelling into the topic more than 2 minutes. People are suffering from a severe case of the Dunning-Kruger effect (I was so happy when I found out there's a name to that attitude).I'll do that. And I'll be sure you get a pm when I do. Also, you won't have to worry about your device rebooting anymore.