I was just reading through this article, "Advanced Kernel Tweaks for the OnePlus 3" and was really surprised by the improvement in battery life and performance by just making a few tweaks in the kernel profiles.
While the battery and SOT for our kenzo is already at par with most of the other devices, thanks to the massive battery, but still the thought of implementing the tweaks and further increasing the battery and performance to another level just amazed me. In this article the OP is talking about increasing the SOT upto 14hrs on OnePlus 3 without any significant trade off with the performance, with its 3000mAh battery. So, guys just think what these tweaks can do to our device.
Now, I'm not being too much greedy here but guys let's just give this a try. We have enough people here on our forum for testing.
Since, I'm not much active here and don't know much about the devs involved in the development of our device, so I ask everyone to tag the devs from our Redmi Note 3 forums, in this thread, so that they can look into it and work on highly optimising the different kernel parameters to get the most out of this device.
This is just a humble request from my side, which will benefit a lot of users. Its not that I'm commanding or forcing the devs to do it. Its just a humble request and the devs are free to neglect it.
Thanks anyways, let's hope the devs look into it at further improve the device's performance to another level.
The biggest problem is Snapdragon 650 is 28nm processor and Snapdragon 820/821 is 14nm. 650 will need higher voltage, higher power consumption to reach the stability and performance.
IF Snapdragon 650 were made with 14nm processing, I assume Kenzo will have around 12hr+ SOT straight out the box.
Second is processor architecture, 820/821 based on Kyro cores (heavily modified version of Cortex-A72/A73 core if I'm right, correct me this). Even small cluster of 820/821 will have the same or better performance to big cluster (2xCortex-A72) on 650.
10hrs+ SOT on Kenzo has reached hardware limitation. Miracle may happen, but don't expect it. Developers still looking for the best way to save your battery without trading too much performance.
IMO, Radon Kenzo is the "TWEAKED KERNEL" you need.
OT: Battery life is the only reason why RMN4 (SD) use 625 instead of 652 as we expected. RMN4 SD gonna have little worse CPU performance than MTK variant in trade of better graphic performance. And maybe battery life, I assuming it will have 12hrs+ straight out the box.
The clusters (there use the same archicture but the frequences are different) of s820/821 are at the same frequences less performing than a72, else same in 14nm the consumption of battery is too big with only big cores because there are not efficient for small usage .. so Qualcomm used their own cores mixed to perform correctly and battery consumption correct... but it's really not perfect (Geekbench 4 show well that kryo 100 are really not fantastic...)
If you want a big sot with 650, put down the big cluster... and launch them only on some bigs apps...
14h with an OP3 I think it's near to impossible, same with kernel tweaks... I know a OP3 user and generally it's not more than 5H SOT....
@Archmage1809, @jordandroid64 = The project was initially started for Nexus 5x which had SD 808, a hexa-core processer with 2xA57 and 4xA53 cores. Also it was built on 20nm architcure technology. So, that means there's hope for us too, if what I understood it right.
Nexus 5x Kernel Tweaking
Related
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
buntybauva said:
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
Click to expand...
Click to collapse
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
DespairFactor said:
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
Click to expand...
Click to collapse
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
I am giving snapdragon battery guru a try, it's for Qualcomm processors. But I'm not very experienced in this stuff. I think it has helped but if someone with more experience wants to give it a try. Maybe they can shed some new light on this subject.
This is the result with on-demand governor settings when phone is idle. with stock kernel and stock frequencies.
Ondemand has always been my fvorite for all past phones. in op2 however it always reverts back to original after interactive. the best battery saver for any phone is swithching to 4.4.2. Azimg batteru life. unfortunately notpossble with op2
buntybauva said:
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
Click to expand...
Click to collapse
Being rooted alone will prevent OTA updates. You have to flash the full stock ROM when there's an update anyway which would overwrite the kernel.
Is it possible to get our 820 soc overclocked with a custom kernel so it can compare to 821 chip?
No stable custom kernel available so far
And you can compare soc on web
Leo7D said:
No stable custom kernel available so far
Click to expand...
Click to collapse
Link?
georgesalo said:
Link?
Click to expand...
Click to collapse
http://wccftech.com/snapdragon-821-vs-snapdragon-820/
http://www.techgrapple.com/apple-a10-sd-821-820/
http://www.trustedreviews.com/opinions/snapdragon-820-vs-snapdragon-810
Leo7D said:
No stable custom kernel available so far
And you can compare soc on web
Click to expand...
Click to collapse
I think he didn't want to compare but to overclock to make it faster.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Difference between 820 and 821 is pretty negligible. I very much doubt that you could find any meaningful difference between the two in real-life performance, given that few if any apps currently push these CPUs anywhere near their full capability. All you'd probably achieve by slightly overclocking is very marginal gains in synthetic benchmark scores at the cost of battery life and possibly stability. In fact, thermal throttling would probably make performance worse. IMHO it would be a pointless exercise.
Not seeing much advantage on SD821.
Is there anything to gain on SD821 the higher clocking in CPU and GPU doesnt seem to translate into actually advantage and seems more like an gimmick to sell SD820 in new clothing, but fair enough it is an solid chipset..
Have my X822 (the dark grey version) for an couple of weeks now and been filling it up, but it still delivers insanse scores from an 222US handset-
from today in Basemark X' a +43k score. (at household temperaure ' - overall not to shabby from an little over 200US-handset)
anyone got an up to date ranking on Basemark X. (nb in high sett. L2M getting an little under 37k)
but ewen the Pixel XL that should be an SD821 is clocked in SD820s values, and comming in at ofc. 35.598k (hence X822 : 43.001)
http://powerboard.basemark.com/filter?benchmark=10&page=1&categories=0&os=0,2
So on my thread for the Nexus 6P bootloop fix, @btvolta asked me this question:
btvolta said:
I am still on the previous modified ex kernel and my phone seems to run just the same as before my blod experience. How many cores are normally running if not for the blod issue?
Click to expand...
Click to collapse
He had a good question, as many other people were reporting that the 6P was running almost the same, if not even better, with only half the cores enabled.
Below is the reply I gave to him. I decided to post it into this thread, because I would like to know what you guys think about my theory about Qualcomm's chips, and even correct me if I'm wrong, as I would like to understand this situation as accurately as possible. (Although I do ask that those of you who do disagree with me, do it respectfully, and I will treat you the same)
XCnathan32 said:
So me typing this reply ended up in me going about a long rant about my theories about Qualcomm. Tl;Dr to your question: Stock 6P uses 8 cores, fixed 6P uses 4, Qualcomm 810 using 8 cores probably overheats so much, that it thermal throttles heavily, resulting in performance only slightly higher than the same processor, with 4 cores, that thermal throttle much less.
Trigger warning for anyone about to read this: I harshly bash on Qualcomm in this semi-angry rant, if you are a diehard Qualcomm fan, you should probably not read this.
On a stock Nexus 6P, 8 cores are enabled in ARMs big.LITTLE configuration. big.LITTLE is where there is a cluster of power efficient, slower cores to handle smaller tasks (in the 6P's case, 4 Cortex A53s running at 1.55GHz), and a cluster of more power hungry, high performance cores (for the 6P, 4 Cortex A57s running at 2GHz)
On a bootlooping 6P, a hardware malfunction related to the big cluster causes this bootloop, so this fix remedies the problem by disabling the high performance big cores.
The stock 6P is supposed to use the Cortex A57 cores and some of the Cortex A53 cores for foreground tasks. So you would think that a working phone should have double the performance of a phone with this fix, right? After all, it's using 4 more cores, and those cores are clocked almost 25% higher. The reason that (I think) performance is not noticeably affected, is because Qualcomm's Snapdragon 808/810 SoCs, are a horrible, rushed project, that could be designed better by a group of monkeys.
Even with 4 cores disabled, my phone can still thermal throttle (for those who don't know, thermal throttling is when CPU/GPU performance is intentionally limited by software to keep temperatures in check) when playing games, or even watching YouTube. The big cores run way hotter, and they thermal throttle insanely easily, see this graph here. In 30 seconds, the big cores are already to 1.8GHz (From 2GHz), in 60 seconds, the big cores are down to 1.4GHz, and in 3 minutes, 3 freaking minutes, the big cores are thermal throttled down to 850MHz, which is 235% slower than the advertised 2000MHz, and 182% slower than the little cores 1.55GHz.
So my guess is that the big cores thermal throttle so easily, and the high heat output of the big cores results on the little cores overheating, which results in the little cores being thermal throttled along with the big cores. So 4 cores that typically do not thermal throttle, are better than 8 which do. Either that, or when the big cores overheat, the device turns off the big cores and only uses the little cores, which is essentially this fix.
For those of you that think my description of the 808/810 was slightly (extremely) harsh, you're right. However, here's why I was so hard on them: I feel like Qualcomm rushed development of the 808 and 810 to get it to flagship devices. The 808 and 810 were also the first (and last) of it's processors to use the TSMC 20nm manufacturing process. So my guess would be that Qualcomm designed the processor based on that manufacturing process, and then after finding out about the poor thermals of their new chips, it was too late to redesign their chip, because they had to give it to manufacturers. After all, a "Flagship device" can't use a last gen processor. So the overheating chips were given to manufacturers just so their phone could look better on a spec sheet.
Also, Qualcomm VP McDonough said "The rumours are rubbish, there was not an overheating problem with the Snapdragon 810 in commercial devices"(source). However his response to heat issues and benchmarking problems in the early Flex 2 and One M9 was because they weren't final commercial versions of the devices. "Everything you're saying is fair. But we all build pre-released products to find bugs and do performance optimisation. So when pre-released hardware doesn't act like commercial hardware, it’s just part of the development process." In that context, performance optimisation most likely means "allow the devices to run hotter than they should before they throttle" (source) which results in problems later down the line (like maybe half of the cores failing, causing a record number of bootloops in devices?)
The whole reason I typed this rant, was to express my frustration at how Qualcomm (most likely) caused tens of thousands of people to have devices that performed worse than they should have performed on paper, and even result in broken devices. And I haven't seen many people blame Qualcomm for the bootlooping problem, and everyone blames Hauwei/LG/Google, while Qualcomm twiddles their thumbs and keeps ranking in money for their domination in the mobile SoC market. Now obviously, I'm not 100% sure that Qualcomm is to blame for the bootlooping problems, and no one will probably ever know who caused the problem. So this is just a theory that I have. But it is awfully suspicious how the same chip has had problems in multiple devices, even when different companies manufactured the devices.
Even if Qualcomm isn't to blame for the bootlooping problems, it is hard to deny that their chips have serious overheating issues. Samsung themselves basically admitted that the 810 had problems, as every single one of their Galaxy S devices (at least US models) have used a snapdragon processor, except for the galaxy S6, where Samsung opted to use their own Exynos processor instead of the 810, even on the US model.
Please feel free to reply and discuss/argue my points, as I would really like to hear what you guys think about my theory.
Click to expand...
Click to collapse
Well, if it's true what you're saying, Qualcomm is the bad guy here. It all points towards an overheating issue with the powercores, which are designed and made by them. However, I feel that the OEMs who purchase these SoCs from them should take responsibility for their choice to use them in their devices and step up. If this theory you have can be proven by extensive testing, a lawsuit should be fairly easy to win and Qualcomm should be forced to better their development and testing.
I may be jumping the gun a bit here, but seeing Qualcomm has a bit of a monopoly on the SoC market, we, the consumers should stop putting our trust in devices using their chipsets. I've had several devices with a Qualcomm chipset and every single one of them were crap. I've had a Samsung Galaxy S2 (which I hated because of the software Samsung put on that device) but the hardware (Exynos) was top notch at the time.
Ok, that's about all of my two cents. Thanks for the good read btw.
NeoS said:
Well, if it's true what you're saying, Qualcomm is the bad guy here. It all points towards an overheating issue with the powercores, which are designed and made by them. However, I feel that the OEMs who purchase these SoCs from them should take responsibility for their choice to use them in their devices and step up. If this theory you have can be proven by extensive testing, a lawsuit should be fairly easy to win and Qualcomm should be forced to better their development and testing.
I may be jumping the gun a bit here, but seeing Qualcomm has a bit of a monopoly on the SoC market, we, the consumers should stop putting our trust in devices using their chipsets. I've had several devices with a Qualcomm chipset and every single one of them were crap. I've had a Samsung Galaxy S2 (which I hated because of the software Samsung put on that device) but the hardware (Exynos) was top notch at the time.
Ok, that's about all of my two cents. Thanks for the good read btw.
Click to expand...
Click to collapse
Just happened to be Huawei was making the device and even though Huawei has their own in house chip but since Huawei brand was not really familiar to US, maybe Google is not convinced to market a Nexus brand with some Hi Silicon Kirin processor but they need to get another Nexus device out that year.
If just it was Samsung back then to make the Nexus device, maybe Google is ok with Samsung Exynos chip.
How great would the 6p be IF it could utilize the a57 cores? I'm using Franco Kernel, and he has it set up to barely use the big cores. I'm guessing mostly for battery savings of course, but on a 6p that thus far hasn't had the infamous battery meltdown, to have half of the cores (and the most powerful) cores sitting at lowest frequency for 95% of the time is kind of a shame. I'm willing to dust off my pitchfork
Can you guys say what is the maximum benchmark score for mido 4/64gb variant in latest software update I Mean miui 9 I got a score of 59k is it good?
meheboobalam1 said:
Can you guys say what is the maximum benchmark score for mido 4/64gb variant in latest software update I Mean miui 9 I got a score of 59k is it good?
Click to expand...
Click to collapse
Hm? Are you still that concern with benchmarks these days?
anyways, i got 64K+ on ViperOs, a good score but in Quadrant i got uninspiring results. (SD, 3GB version)
59K is good enough as long its perform well as day to day driver without any hiccup.
GabrielScott said:
Hm? Are you still that concern with benchmarks these days?
anyways, i got 64K+ on ViperOs, a good score but in Quadrant i got uninspiring results. (SD, 3GB version)
59K is good enough as long its perform well as day to day driver without any hiccup.
Click to expand...
Click to collapse
Using official stock ROM. Not a fan of custom ROM not anymore ultimately we will come back to stock ROM so why. Not modified stock ROM like Xiaomi.eu
65k on AEX without any modifications, 4/64gb variant.
64-65k on redmi note 4x (sd) 3/32, rom RR
Mine is 0 coz I dun care... Lol
aabenroi said:
Mine is 0 coz I dun care... Lol
Click to expand...
Click to collapse
Well, if I was going to use benchmarking apps, I would rather use Geekbench4 or PC Mark2.0.
DarthJabba9 said:
Well, if I was going to use benchmarking apps, I would rather use Geekbench4 or PC Mark2.0.
Click to expand...
Click to collapse
Whatever bench, I don't trust bench anymore...
The mtk for example score very high bench but real performance is so bad.
Those huawei kirin score very low bench score, but it plays games, especially psp and dolphin emulation way-way better than snapdragon and mtk that have better bench score.
aabenroi said:
Whatever bench, I don't trust bench anymore...
The mtk for example score very high bench but real performance is so bad.
Those huawei kirin score very low bench score, but it plays games, especially psp and dolphin emulation way-way better than snapdragon and mtk that have better bench score.
Click to expand...
Click to collapse
MTk is scoring high because it's faster but for short amounts of time because they overheat, after 10-15minutes of heavy usage like gaming it's reducing CPU/GPU frequency to reduce heat (thermal throttling), and then the performance is much worse.
Thats why benchmarks are useless, they are too short to show the real performance. For example Snapdragon 625 can keep the same performance for hours during heavy gaming without thermal throttling, because it's super power & thermal efficient.
aabenroi said:
Whatever bench, I don't trust bench anymore...
The mtk for example score very high bench but real performance is so bad.
Those huawei kirin score very low bench score, but it plays games, especially psp and dolphin emulation way-way better than snapdragon and mtk that have better bench score.
Click to expand...
Click to collapse
The secret is to look at single-core performance. Multi-core benchmarks are always very high on MTK because their chips usually have more cores than others. However, how many apps actually use all those cores? All that the extra cores do is to suck your battery.
k3lcior said:
MTk is scoring high because it's faster but for short amounts of time because they overheat, after 10-15minutes of heavy usage like gaming it's reducing CPU/GPU frequency to reduce heat (thermal throttling), and then the performance is much worse.
Thats why benchmarks are useless, they are too short to show the real performance. For example Snapdragon 625 can keep the same performance for hours during heavy gaming without thermal throttling, because it's super power & thermal efficient.
Click to expand...
Click to collapse
Yeah I agree,
Beside that, benchmark just measure raw power, big raw power is useless without good optimization.
Snapdragon n Kirin have lower raw power but easily beat mtk because they're way more optimized.
DarthJabba9 said:
The secret is to look at single-core performance. Multi-core benchmarks are always very high on MTK because their chips usually have more cores than others. However, how many apps actually use all those cores? All that the extra cores do is to suck your battery.
Click to expand...
Click to collapse
Nowdays, mtk score very high at single core as well... But it still sucks...
There's too much misinformation around and once I get my unit I will have about 28 days to decide if to keep it or skip this generation, I would like to use this thread to build evidence on how good or bad the international version of this device is, if Samsung scammed 90% of the world then they don't deserve our money.
I'm getting mixed feelings about this chip, In speed test G the 855 beats it by a huge margin, so most people went back spitting at it for being a badly optimized SoC.
Anandtech's Comparisons Show super disappointing scores for the S10 Exynos version, but many of the scores presented make no sense, with older hardware of the same OEM scoring better than the newest, I don't know how much to believe that review and I hope it is fake or badly executed, to my interest, my pre-order comes with the Exynos version and there's no way to have warranty on a 855 in the UK.
Then, the positive evidence we have is that it beats every other released phone on the market in battery usage, there's no such video about the 855 yet so we can't compare them, but that's all I found about the battery of this chip.
In a S10+ vs iPhone XS Max, the S10+ again Exynos beats the iPhone on almost every application, I didn't expect that to happen since it almost never happened, the apps are supposedly the same most of the time and they might as well have completely different algorithms to do the same task done superficially, but generally iOS apps are cleaner inside and their developers have higher standards of work, so how can Exynos be THAT much better?
From what I see the Exynos 9820 is not as what is perceived here on XDA....
Duncan1982 said:
From what I see the Exynos 9820 is not as what is perceived here on XDA....
Click to expand...
Click to collapse
And that's a demo unit with 6GB of ram, there are even higher benchmarks with real ones around:
https://browser.geekbench.com/v4/cpu/12211126
But everyone is dismissing Geekbench as "not reliable", and in a way it is not reliable since it doesn't demonstrate the effectiveness of a good scheduler, even the crappiest ones will be pushed to maximum performance once geekbench runs, we need more comparisons with other tools.
it is a solid fact that the Exynos is much faster than anything else in single core performance except the apple A12 and is much faster than the SD855 , while the SD855 is faster in multi core but no by much,
my only concern with the exynos is the stuttering and frame drops and the smoothness overall , i don't care about benchmarks really , and the S10 is ultra fast in launching apps already in both the exynos and SD855 , but the main concern as i mentioned is the smoothness which i think will be related to how the KERNEL will handle & is optimized and if was targeting performance or targeting efficiency only.