Hello !
After long weeks of searching the answer and solution to my problem, I am exhausted. So I would like to ask the biggest Android community for help
Well, I know it's not new, but I have problem with my S7 Edge (Exynos) performance
I experience FPS drops in almost every game I play. As for games it's not that irritating, but recently I have bought Gear VR and while having this thing so close to your eyes, you see every frame skipping.
Apps for checking the CPU throttling shows that after 5-10 minutes the 4 bigger cores slow down to about 50% of their full speed. It leads to ~30% performance slow down.
I tried every solution that doesn't require root access and warranty void. For example: disabling certain packages and services (Game Launcher, Game optimization service); different settings in Game Tuner; performance mode; factory reset etc. Nothing works.
Does this kind of problems can be repaired on warranty? I know that in order to fix this you can change kernel setting, cpu governor etc but ofc they don't do that in Samsung Service Center. Is it possible for them to replace the main board and cpu with Snapdragon one?
I would not like to root my device because I didn't want to lose my 3 years warranty and I am using a lot of applications that may not work with a root.
Thank you in advance for all your replies
Did you try the game performance mode? As the "performance mode" is just screen resolution and brightness. The game mode is the real performance mode where the temps throttling is relaxed and higher clock speeds allowed(you can also edit the profile to set the resolution manually to wqhd). You can also try to set the resolution to full hd and see how it goes (tho for VR it won't be cool, but for the test it won't hurt). Also if the phone is new, it will need atleast 10 days to settle and become faster, smoother, better. Apply updates if they are pending too.
Otherwise you can't do much without root, but even then you are limited to what you can achieve so be careful + samsung have a fuse into the chip that burns out when you root the phone, it's not possible to hide the intervention and they can deny warranty for that reason (and often do so).
high_voltage said:
Did you try the game performance mode? As the "performance mode" is just screen resolution and brightness. The game mode is the real performance mode where the temps throttling is relaxed and higher clock speeds allowed(you can also edit the profile to set the resolution manually to wqhd). You can also try to set the resolution to full hd and see how it goes (tho for VR it won't be cool, but for the test it won't hurt). Also if the phone is new, it will need atleast 10 days to settle and become faster, smoother, better. Apply updates if they are pending too.
Otherwise you can't do much without root, but even then you are limited to what you can achieve so be careful + samsung have a fuse into the chip that burns out when you root the phone, it's not possible to hide the intervention and they can deny warranty for that reason (and often do so).
Click to expand...
Click to collapse
Thank you for your reply
Yes, I've tried "game mode" but there is no difference. Changing resolution to Full HD helps for a while, but the Gear VR software doesn't work properly on anything other than WQHD. It just doesn't scale properly and you are unable to see whole content.
I'm just wondering whether every S7 Edge has problems like mine. I understand throttling after 20-30 minutes of intensive gameplay, but ~40% slow down after 3-5 minutes seems strange, especially because phone doesn't even get warm.
emsitek said:
Thank you for your reply
Yes, I've tried "game mode" but there is no difference. Changing resolution to Full HD helps for a while, but the Gear VR software doesn't work properly on anything other than WQHD. It just doesn't scale properly and you are unable to see whole content.
I'm just wondering whether every S7 Edge has problems like mine. I understand throttling after 20-30 minutes of intensive gameplay, but ~40% slow down after 3-5 minutes seems strange, especially because phone doesn't even get warm.
Click to expand...
Click to collapse
Hard to tell, got the phone, but no vr... :/
Otherwise I don't have problems with gaming, the game mode smooths a little the already fluid gaming(but then again, the game I play mostly is vainglory and that game runs great on htc m8 that is almost 4 years old). You are talking about some more massive performance drop. Many phones start to throttle early and throttle hard, samsung is one of them for sure (they want the phone cold).
@hamdir can you lend a hand on that one? You are tons more experience with VR than me.
high_voltage said:
Hard to tell, got the phone, but no vr... :/
Otherwise I don't have problems with gaming, the game mode smooths a little the already fluid gaming(but then again, the game I play mostly is vainglory and that game runs great on htc m8 that is almost 4 years old). You are talking about some more massive performance drop. Many phones start to throttle early and throttle hard, samsung is one of them for sure (they want the phone cold).
@hamdir can you lend a hand on that one? You are tons more experience with VR than me.
Click to expand...
Click to collapse
Well, there is an app called CPU Throttling Test on Google Play. I would be really thankful if you give me information how your phone behave in this app. Mine throttles hard after 3-8 minutes. Clock speed of the better cores goes down to about 1.6GHz each. Sometimes even below 1.5GHz.
emsitek said:
Well, there is an app called CPU Throttling Test on Google Play. I would be really thankful if you give me information how your phone behave in this app. Mine throttles hard after 3-8 minutes. Clock speed of the better cores goes down to about 1.6GHz each. Sometimes even below 1.5GHz.
Click to expand...
Click to collapse
From a cold phone, 1.9GHz almost right away(I guess the highest freq is only for burst load, like app launching) and kept for 8 minutes then drop to 1.57GHz on the big cores. So I think it's in line with your result.
high_voltage said:
From a cold phone, 1.9GHz almost right away(I guess the highest freq is only for burst load, like app launching) and kept for 8 minutes then drop to 1.57GHz on the big cores. So I think it's in line with your result.
Click to expand...
Click to collapse
Yeah, that would be it. Thank you for your time. So it seems to be normal, I hope I'll get used to it somehow
I also wrote an email to Oculus, maybe they heard sth about this issue and know a fix for frames skipping.
The notorious feature known as DVFS is the likely culprit. Some forum members suggest it throttles the GPU and CPU to improve benchmark results or otherwise to protect the device. I've noticed it can lock-up and end up overheating the device but that's just an anecdote.
You can try forcing the app to run at a lower resolution which Samsung's Game Tuner does for some games, or find other solutions for unrooted devices like capping CPU frequency for a smoother experience.
nexidus said:
The notorious feature known as DVFS is the likely culprit. Some forum members suggest it throttles the GPU and CPU to improve benchmark results or otherwise to protect the device. I've noticed it can lock-up and end up overheating the device but that's just an anecdote.
You can try forcing the app to run at a lower resolution which Samsung's Game Tuner does for some games, or find other solutions for unrooted devices like capping CPU frequency for a smoother experience.
Click to expand...
Click to collapse
Almost all the phones are tweaked to use max freq only on single core load and app startup (burst). If their power management detect heavy load on all cores, it will automatically scale down to lower freq state to prevent heat building up fast. In reality in our case this is 1.87GHz for all big cores + the small ones (higher if only the big cluster is used, leaving the small cores off). The first actual thermal throttling level is 1.56-1.57GHz at around 8 minutes mark. Games would take a lot longer and in my observation as the phone is big and none will use 8 cores at the same time - there will be no throttling, just power management and stable fps. His case is different tho, VR is really a heavy one on the CPU.
As for DVFS (and extended to samsung power management, every manufacturer has it's own management) - it's there for a reason, to use your phone without major slowdowns due to heat and to be cold in touch, i.e. better for use. You can always change the behaviour via custom kernel, but you can't get more performance without heating the phone to the point of hardware throttling or uncomfortable to hold. Actually as you said - the right way if modify is to cap to lower freq and try to command the phone to keep them. This would still lead to a lot of heat, but will take some time to build up (and it will look smoother, tho with lower fps). OC is pointless for speed gains, will work only for burst loads. UV is not effective too as nowdays the SOC's are heavily binned for optimal settings from the factory.
Disable throttlinf dvfs exynos
Check how disable it . My youtube channel URLGAMEPLAY
Related
Do you?
Do you keep it overckocked for a longer period, permanently, or just when/while you need it? How much (exact frequencies would be cool) I'm thinking of OCing mine (both CPU and GPU) since some games like NOVA 3 lag on occasions but not sure how safe/advisable it is.
Sent from my Nexus 7 using Tapatalk HD
I don't think it's needed. I've heard that OC won't help much with gaming, but you can definitely try
I don't yet - I might later. My N7 is still less than a month old.
The device manufacturers (e.g. Asus in this case) have motivations to "not leave anything on the table" when it comes to performance. So, you have to ask yourself - why would they purposely configure things to go slowly?
After all, they need to compete with other handset/tablet manufacturers, who are each in turn free to go out and buy the exact same Tegra SoC (processor) from Nvidia.
At the same time, they know that they will manufacture millions of units, and they want to hold down their product outgoing defect levels and in-the-field product reliability problems to an acceptable level. If they don't keep malfunctions and product infant mortality down to a fraction of a percent, they will suffer huge brand name erosion problems. And that will affect not only sales of the current product, but future products too.
That means that they have to choose a conservative set of operating points which will work for 99+ % of all customer units manufactured across all temperature, voltage, and clock speed ranges. (BTW, Note that Asus didn't write the kernel EDP & thermal protection code - Nvidia did; that suggests that all the device manufacturers take their operating envelope from Nvidia; they really don't even want to know where Nvidia got their numbers)
Some folks take this to mean that the vast majority of units sold can operate safely at higher speeds, higher temperatures, or lower voltages, given that the "as shipped" configuration will allow "weak" or "slow" units to operate correctly.
But look, it's not as if amateurs - hacking kernels in their spare time - have better informed opinions or data about what will work or won't work well across all units. Simply put, they don't know what the statistical test properties of processors coming from the foundry are - and certainly can't tell you what the results will be for an individual unit. They are usually smart folks - but operating completely in the dark in regards to those matters.
About the only thing which can be said in a general way is that as you progressively increase the clock speed, or progressively weaken the thermal regulation, or progressively decrease the cpu core voltage stepping, your chances of having a problem with any given unit (yours) increase. A "problem" might be (1) logic errors which lead to immediate system crashes or hangs, (2) logic errors (in data paths) that lead to data corruption without a crash or (3) permanent hardware failure (usually because of thermal excursions).
Is that "safe"?
Depends on your definition of "safe". If you only use the device for entertainment purposes, "safe" might mean "the hardware won't burn up in the next 2-3 years". Look over in any of the kernel threads - you'll see folks who are not too alarmed about their device freezing or spontaneously rebooting. (They don't like it, but it doesn't stop them from flashing dev kernels).
If you are using the device for work or professional purposes - for instance generating or editing work product - then "safe" might mean "my files on the device or files transiting to and from the cloud won't get corrupted", or "I don't want a spontaneous kernel crash of the device to cascade into a bricked device and unrecoverable files". For this person, the risks are quite a bit higher.
No doubt some tool will come in here and say "I've been overclocking to X Ghz for months now without a problem!" - as if that were somehow a proof of how somebody else's device will behave. It may well be completely true - but a demonstration on a single device says absolutely nothing about how someone else's device will behave. Even Nvidia can't do that.
There's a lot of pretty wild stuff going on in some of the dev kernels. The data that exists as a form of positive validation for these kernels is a handful of people saying "my device didn't crash". That's pretty far removed from the rigorous testing performed by Nvidia (98+% fault path coverage on statistically significant samples of devices over temperature, voltage, and frequency on multi-million dollar test equipment.)
good luck!
PS My phone has it's Fmax OC'ed by 40% from the factory value for more than 2 years. That's not a proof of anything really - just to point out that I'm not anti-OC'ing. Just trying to say - nobody can provide you any assurances that things will go swimmingly on your device at a given operating point. It's up to you to decide whether you should regard it as "risky".
Wow thanks for your educational response, I learned something. Great post! I will see if I will over clock it or not since I can play with no problems at all, it is just that it hics up when there is too much stuff around. Thanks again!
Sent from my Nexus 7 using Tapatalk HD
With the proper kernel its really not needed. Havent really seen any difference,aside from benchmark scores(which can be achieved without oc'ing)
Sent from my Nexus 7 using XDA Premium HD app
Yes, I run mine at 1.6 peak.
I've come to the Android world from the iOS world - the world of the iPhone, the iPad, etc.
One thing they're all brilliant at is responsive UI. The UI, when you tap it, responds. Android, prior to 4.1, didn't.
Android, with 4.1 and 4.2, does. Mostly.
You can still do better. I'm running an undervolted, overclocked M-Kernel, with TouchDemand governor, pushing to 2 G-cores on touch events.
It's nice and buttery, and renders complex PDF files far faster than stock when the cores peak at 1.6.
I can't run sustained at 1.6 under full load - it thermal throttles with 4 cores at 100% load. But I can get the peak performance for burst demands like page rendering, and I'm still quite efficient on battery.
There's no downside to running at higher frequencies as long as you're below stock voltages. Less heat, more performance.
If you start pushing the voltages past spec, yeah, you're likely into "shortening the lifespan." But if you can clock it up, and keep the voltages less than the stock kernel, there's really not much downside. And the upside is improved page rendering, improved PDF rendering, etc.
Gaming performance isn't boosted that much as most games aren't CPU bound. That said, I don't game. So... *shrug*.
Bitweasil said:
I can't run sustained at 1.6 under full load - it thermal throttles with 4 cores at 100% load.
Click to expand...
Click to collapse
@Bitweasil
Kinda curious about something (OP, allow me a slight thread-jack!).
in an adb shell, run this loop:
# cd /sys/kernel/debug/tegra_thermal
# while [ 1 ] ; do
> sleep 1
> cat temp_tj
> done
and then run your "full load".
What temperature rise and peak temperature do you see? Are you really hitting the 95C throttle, or are you using a kernel where that is altered?
I can generate (w/ a mutli-threaded native proggy, 6 threads running tight integer loops) only about a 25C rise, and since the "TJ" in mine idles around 40C, I get nowhere near the default throttle temp. But I am using a stock kernel, so it immediately backs off to 1.2 Ghz when multicore comes on line.
Same sort of thing with Antutu or OpenGL benchmark suites (the latter of which runs for 12 minutes) - I barely crack 60C with the stock kernel.
?
bftb0
The kernel I'm using throttles around 70C.
I can't hit that at 1200 or 1300 - just above that I can exceed the temps.
I certainly haven't seen 95C.
M-Kernel throttles down to 1400 above 70C, which will occasionally get above 70C at 1400, but not by much.
Bitweasil said:
The kernel I'm using throttles around 70C.
I can't hit that at 1200 or 1300 - just above that I can exceed the temps.
I certainly haven't seen 95C.
M-Kernel throttles down to 1400 above 70C, which will occasionally get above 70C at 1400, but not by much.
Click to expand...
Click to collapse
Thanks. Any particular workload that does this, or is the throttle pretty easy to hit with arbitrary long-running loads?
Odp: Do you overclock your N7?
I'll never OC a quadcore phone/tablet, I'm not stupid. This is enough for me.
Sent from my BMW E32 using XDA App
I've over clocked my phone, but not my N7. I've got a Galaxy Ace with a single core 800MHz processor OC'd to 900+. The N7 with its quad core 1.3GHz is more than enough for doing what I need it to do. Using franco.Kernel and everything is smooth and lag-free. No need for me to overclock
Sent From My Awesome AOSPA3.+/franco.Kernel Powered Nexus 7 With XDA Premium
Impossible to do so can't even get root but did manage to unlock the bootloader
Sent from my Nexus 7 using xda app-developers app
CuttyCZ said:
I don't think it's needed. I've heard that OC won't help much with gaming, but you can definitely try
Click to expand...
Click to collapse
I'm not a big OC'er, but I do see a difference in some games when I OC the GPU. It really depends on the game and what is the performance bottleneck. If the app is not Kernel bound than an OC won't make much difference. Must games are I/O and GPU bound.
Sent from my N7 using XDA Premium
Dirty AOKP 3.5 <&> m-kernel+ a34(t.10)
I've overclocked all of my devices since my first HTC hero. I really don't see a big deal with hardware life.
I know that this n7 runs games better at 1.6ghz than at 1.3ghz.
First thing I do when I get a new device is swap recovery and install aokp with the latest and greatest development kernel. Isn't that why all this great development exists? For us to make our devices better and faster? I think so. I'd recommend aokp and m-kernel to every nexus 7 owner. I wish more people would try non-stock.
scottx . said:
I've overclocked all of my devices since my first HTC hero. I really don't see a big deal with hardware life.
I know that this n7 runs games better at 1.6ghz than at 1.3ghz.
First thing I do when I get a new device is swap recovery and install aokp with the latest and greatest development kernel. Isn't that why all this great development exists? For us to make our devices better and faster? I think so. I'd recommend aokp and m-kernel to every nexus 7 owner. I wish more people would try non-stock.
Click to expand...
Click to collapse
Do you mean the pub builds of AOKP? Or Dirty AOKP
Ty
bftb0 said:
Thanks. Any particular workload that does this, or is the throttle pretty easy to hit with arbitrary long-running loads?
Click to expand...
Click to collapse
Stability Test will do it reliably. Other workloads don't tend to run long enough to trigger it that I've seen.
And why is a quadcore magically "not to be overclocked"? Single threaded performance is still a major bottleneck.
Bitweasil said:
Stability Test will do it reliably. Other workloads don't tend to run long enough to trigger it that I've seen.
And why is a quadcore magically "not to be overclocked"? Single threaded performance is still a major bottleneck.
Click to expand...
Click to collapse
Hi Bitweasil,
I fooled around a little more with my horrid little threaded cpu-blaster code. Combined simultaneously with something gpu-intensive such as the OpenGL ES benchmark (which runs for 10-12 minutes), I observed peak temps (Tj) of about 83C with the stock kernel. That's a ridiculous load, though. I can go back and repeat the test, but from 40C it probably takes several minutes to get there. No complaints about anything in the kernel logs other than the EDP down-clocking, but that happens just as soon as the second cpu comes on line, irrespective of temperature. With either of the CPU-only or GPU-only stressors, the highest I saw was a little over 70C. (But, I don't live in the tropics!)
To your question - I don't think there is much risk of immediate hardware damage, so long as bugs don't creep into throttling code, or kernel bugs don't cause a flaw that prevents the throttling or down-clocking code from being serviced while the device is running in a "performance" condition. And long-term reliability problems will be no worse if the cumulative temperature excursions of the device are not higher than what than what they would be using stock configurations.
The reason that core voltages are stepped up at higher clock rates (& more cores online) is to preserve both logic and timing closure margins across *all possible paths* in the processor. More cores running means that the power rails inside the SoC package are noisier - so logic levels are a bit more uncertain, and faster clocking means there is less time available per clock for logic levels to stabilize before data gets latched.
Well, Nvidia has reasons for setting their envelope the way they do - not because of device damage considerations, but because they expect to have a pretty small fraction of devices that will experience timing faults *anywhere along millions of logic paths* under all reasonable operating conditions. Reducing the margin, whether by undervolting at high frequencies, or increasing max frequencies, or allowing more cores to run at peak frequencies will certainly increase the fraction of devices that experience logic failures along at least one path (out of millions!). Whether or not OC'ing will work correctly on an individual device can not be predicted in advance; the only thing that Nvidia can estimate is a statistical quantity - about what percent of devices will experience logic faults under a given operating conditon.
Different users will have different tolerance for faults. A gamer might have very high tolerance for random reboots, lockups, file system corruption, et cetera. Different story if you are composing a long email to your boss under deadline and your unit suddenly turns upside down.
No doubt there (theoretically) exists an overclocking implementation where 50% of all devices would have a logic failure within (say) 1 day of operation. That kind of situation would be readily detected in a small number of forum reports. But what about if it were a 95%/5% situation? One out of twenty dudes report a problem, and it is dismissed with some crazy recommendation such as "have you tried re-flashing your ROM?". And fault probability accumulates with time, especially when the testing loads have very poor path coverage. 5% failure over one day will be higher over a 30 day period - potentially much higher.
That's the crux of the matter. Processor companies spend as much as 50% of their per-device engineering budgets on test development. In some cases they actually design & build a second companion processor (that rivals the complexity of the first!) whose only function is to act as a test engine for the processor that will be shipped. Achieving decent test coverage is a non-trivial problem, and it is generally attacked with extremely disciplined testing over temperature/voltage/frequency with statistically significant numbers of devices - using test-vector sets (& internal test generators) that are known to provide a high level of path coverage. The data that comes from random ad-hoc reports on forums from dudes running random applications in an undisciplined way on their OC'ed units is simply not comparable. (Even "stressor" apps have very poor path coverage).
But, as I said, different folks have different tolerance for risk. Random data corruption is acceptable if the unit in question has nothing on it of value.
I poked my head in the M-kernel thread the other day; I thought I saw a reference to "two units fried" (possibly even one belonging to the dev?). I assume you are following that thread ... did I misinterpret that?
cheers
I don't disagree.
But, I'd argue that the stock speeds/voltages/etc are designed for the 120% case - they're supposed to work for about 120% of shipped chips. In other words, regardless of conditions, the stock clocks/voltages need to be reliable, with a nice margin on top.
Statistically, most of the chips will be much better than this, and that's the headroom overclocking plays in.
I totally agree that you eventually will get some logic errors, somewhere, at some point. But there's a lot of headroom in most devices/chips before you get to that point.
My use cases are heavily bursty. I'll do complex PDF rendering on the CPU for a second or two, then it goes back to sleep while I read the page. For this type of use, I'm quite comfortable with having pushed clocks hard. For sustained gaming, I'd run it lower, though I don't really game.
I'm on an SM-N910W8 Canadian Note 4, running 5.1.1 stock rooted w/xposed.
I've been kinda disappointed with this thing's performance in games - despite the supposed extra power, it's not getting much better framerates than my old S3, and I have to put nearly all 3D games in medium or low graphics just to get 30fps. Games like Modern Combat 5 and Xcom:EW are so choppy (15-20fps) they're basically unplayable.
I installed a very old program called SetCPU and tried changing the CPU governor to "performance" which forces max clock, and suddenly my framerates nearly doubled! Every game was performing as I expected this hardware would be capable of! But I got worried that I might be hurting the CPU because it was working harder than designed, so I turned it off.
And then I saw a little tickbox in my Wanam Xposed module called "Disable DVFS". After reading about it, it sounds like DVFS is the thermal throttling feature of the CPU, to slow down the clock if it gets too hot. Everyone is saying you should disable this for increased performance. But then that makes me wonder, why did Samsung include it in the first place? Surely you WANT the CPU to downclock if it gets too hot, don't you? Wouldn't disabling DVFS risk overheating and damaging the CPU? And if not, if it's perfectly safe to disable it, and there's absolutely no bad side, then why the hell did Samsung enable it in the first place?
Hey guys. I bought the Nexus 6P this week at the same time I finished my new app Face Jacker. The app is quite intensive on the CPU - as it's a camera app and I'm manipulating the pixels from the camera every frame, but something is just not quite right when ran on the Nexus 6P.
I created and tested the app using the Samsung S5 on lolipop which runs the snapdragon 801 cpu. It runs seriously smooth on the S5. I later tested the app on the S7 edge since it was running marshmallow -- again no issues there, app ran silky smooth just like the S5 just as I expected.
Now heres the weird part, I load the app up on the Nexus 6P same day I buy it. The face jacking runs smooth for around half a second before the fps drops from around 28 to 7. Both the nexus 6p and S5 are using the same resolution when running the face jack.
I'm trying to figure out what's causing this serious knock in fps after the first half second... The only thing I can think of is the CPU being throttled. I checked the temps but they around 46 on full load of the app - but this wouldn't be enough to throttle, would it?
The clock speed of one of the cores in the 6P is obviously fast enough to run the algorithm every frame (as it runs fine for first half second) but it takes a serious nose dive for some reason I can't explain.
Does anyone know anything special about the snapdragon 810 cpu? I've read that it can be a beast of a cpu performance wise - but I don't understand why it would run so slower to an older cpu.
Sorry for rambling on, just really stumped with this one and I don't know where to even start to debug this.
I can't post a link to the app since I've just registered to XDA - but if you want to find it, please search Face Jacker in the playstore - it's the one with the purple icon.
commanderprompt said:
Hey guys. I bought the Nexus 6P this week at the same time I finished my new app Face Jacker. The app is quite intensive on the CPU - as it's a camera app and I'm manipulating the pixels from the camera every frame, but something is just not quite right when ran on the Nexus 6P.
I created and tested the app using the Samsung S5 on lolipop which runs the snapdragon 801 cpu. It runs seriously smooth on the S5. I later tested the app on the S7 edge since it was running marshmallow -- again no issues there, app ran silky smooth just like the S5 just as I expected.
Now heres the weird part, I load the app up on the Nexus 6P same day I buy it. The face jacking runs smooth for around half a second before the fps drops from around 28 to 7. Both the nexus 6p and S5 are using the same resolution when running the face jack.
I'm trying to figure out what's causing this serious knock in fps after the first half second... The only thing I can think of is the CPU being throttled. I checked the temps but they around 46 on full load of the app - but this wouldn't be enough to throttle, would it?
The clock speed of one of the cores in the 6P is obviously fast enough to run the algorithm every frame (as it runs fine for first half second) but it takes a serious nose dive for some reason I can't explain.
Does anyone know anything special about the snapdragon 810 cpu? I've read that it can be a beast of a cpu performance wise - but I don't understand why it would run so slower to an older cpu.
Sorry for rambling on, just really stumped with this one and I don't know where to even start to debug this.
I can't post a link to the app since I've just registered to XDA - but if you want to find it, please search Face Jacker in the playstore - it's the one with the purple icon.
Click to expand...
Click to collapse
It's most likely throttling. From my experience 46°C would easily be enough for the CPU to start throttling back, and even dropping cores completely, in order to control the heat that's generated by this chipset.
Heisenberg said:
It's most likely throttling. From my experience 46°C would easily be enough for the CPU to start throttling back, and even dropping cores completely, in order to control the heat that's generated by this chipset.
Click to expand...
Click to collapse
Thanks Heisenberg. Didn't realise that 46°C would be enough to cause throttling.
So before I start changing my algorithm - is there any way to bypass this throttling? I read somewhere that Marshmallow causes the throttle -- is this correct?
It's quite frustrating as the device gets warmer using other less intensive apps!
commanderprompt said:
Thanks Heisenberg. Didn't realise that 46°C would be enough to cause throttling.
So before I start changing my algorithm - is there any way to bypass this throttling? I read somewhere that Marshmallow causes the throttle -- is this correct?
It's quite frustrating as the device gets warmer using other less intensive apps!
Click to expand...
Click to collapse
It isn't isolated to a specific Android version (it happens on this phonon LP and M), it is specific to the Snapdragon 810 chipset though. The throttling occurs at a kernel level so to change it you'd need root access and a kernel tweaking app to stop throttling from occurring. Or you could build a kernel that doesn't throttle. But that would need to happen on each device, so it isn't a realistic option for getting the app to work properly.
Heisenberg said:
It isn't isolated to a specific Android version (it happens on this phonon LP and M), it is specific to the Snapdragon 810 chipset though. The throttling occurs at a kernel level so to change it you'd need root access and a kernel tweaking app to stop throttling from occurring. Or you could build a kernel that doesn't throttle. But that would need to happen on each device, so it isn't a realistic option for getting the app to work properly.
Click to expand...
Click to collapse
Cheers Heisenburg. Reckon I gotta either offload to the GPU or change the algorithm altogether!
Hello guys..
I have this phone which has a quite good Specs..Though when I install a game, there's some lag
I'm running on Nougat 7.0, I've installed asphalt 8 and there's a lot of lag in the main menu, but that doesn't matter cause I deleted it
now I've installed PUBG Mobile and it's a very exciting game and I'm running on the lowest graphics and I have free ram and space But it lags a lot. I've tried this game on Galaxy A5 2017 on medium (balanced) Graphics and It runs like a charm.
Is there anything I can do to make the game on my device faster with no lag? And why does the game lags anyway on my device which has 3GB Ram?
It's not the RAM that matters but also the GPU. A 2016 uses Mali-T720 while A 2017 is Mali-T830, thats the difference.
I suggest you use Game Tuner from Samsung and adjust the resolution to 55-80%
OK, the hardware is different, but other than that...
A 2016 (info from A5 but should be close) That GPU should be enough to fit the first game on high (maybe outdated), and the second on low (untested). For context, the CPU/GPU is like a motor, running at various speeds, 'weights it is carrying', and power required to maintain that speed (the heat output also scales with this). Some are simply better than others. The Game Tuner's HW performance (CPU) isn't or wasn't available. The customfrequencymanagerservice lowers the CPU/GPU speed for games, also increasing the battery life and lowering the heat. Search the logcat for "limitGPUFreq" "limitCPUFreq" "SIOP_ARM_MAX" (not the tag, but the content). Other than that, the CPU cluster 0/CPU cluster 1/GPU lowers its own speed at 86c (not bidirectional). Optionally, at the cost of heat and battery life, downgrade the game tuner and game optimizing service to whichever version has the apps category feature. Then select the app, then non-game. Lower the resolution to the default 75%. A limit is still there but not as much as before, and looks more like thermal throttling. If rooted, the max speed can be customized in /sys/power/cpufreq_max_limit for the CPU, and /sys/class/misc/mali0/device/dvfs_max_lock for the GPU. Set permissions to 644 to maintain the max speed (until the CPU/GPU lowers itself). Watch the temperatures. If it's too hot, reduce the limit. Maybe an alternative to root is debloating but the speed can't be lowered if needed.
Temperature sensors are here:
/sys/class/hwmon/hwmon0/device/temperature
/sys/class/power_supply/battery/batt_temp
/sys/class/power_supply/battery/chg_temp
/sys/class/thermal/thermal_zone0/cdev0/type
/sys/class/thermal/thermal_zone1/cdev0/type
/sys/class/thermal/thermal_zone2/cdev0/type
/sys/class/thermal/thermal_zone0/temp
/sys/class/thermal/thermal_zone1/temp
/sys/class/thermal/thermal_zone2/temp
etc.
A 2017
The customfrequencymanagerservice applies to the CPU, up to 1794Mhz (HW performance). May lower with what looks like thermal throttling.
Does not apply to the GPU, which throttles itself somewhere around 76c from 962MHz to 845MHz.
Yep. Been playing PUBG Mobile on my A5 2016 on LOW graphics and HIGH frame rate (fps setting) for around one month and it does NOT lag. Although the transitions in UI of main menu is not as fast but the gameplay is super smooth and does not lag. Maybe it's because of your phone slowdown over time (I just factory reset my phone 6 months ago) or because the A7 has more pixels to push so it is more taxing on the GPU.
Bryan48765 said:
OK, the hardware is different, but other than that...
A 2016 (info from A5 but should be close) That GPU should be enough to fit the first game on high (maybe outdated), and the second on low (untested). For context, the CPU/GPU is like a motor, running at various speeds, 'weights it is carrying', and power required to maintain that speed (the heat output also scales with this). Some are simply better than others. The Game Tuner's HW performance (CPU) isn't or wasn't available. The customfrequencymanagerservice lowers the CPU/GPU speed for games, also increasing the battery life and lowering the heat. Search the logcat for "limitGPUFreq" "limitCPUFreq" "SIOP_ARM_MAX" (not the tag, but the content). Other than that, the CPU cluster 0/CPU cluster 1/GPU lowers its own speed at 86c (not bidirectional). Optionally, at the cost of heat and battery life, downgrade the game tuner and game optimizing service to whichever version has the apps category feature. Then select the app, then non-game. Lower the resolution to the default 75%. A limit is still there but not as much as before, and looks more like thermal throttling. If rooted, the max speed can be customized in /sys/power/cpufreq_max_limit for the CPU, and /sys/class/misc/mali0/device/dvfs_max_lock for the GPU. Set permissions to 644 to maintain the max speed (until the CPU/GPU lowers itself). Watch the temperatures. If it's too hot, reduce the limit. Maybe an alternative to root is debloating but the speed can't be lowered if needed.
Temperature sensors are here:
/sys/class/hwmon/hwmon0/device/temperature
/sys/class/power_supply/battery/batt_temp
/sys/class/power_supply/battery/chg_temp
/sys/class/thermal/thermal_zone0/cdev0/type
/sys/class/thermal/thermal_zone1/cdev0/type
/sys/class/thermal/thermal_zone2/cdev0/type
/sys/class/thermal/thermal_zone0/temp
/sys/class/thermal/thermal_zone1/temp
/sys/class/thermal/thermal_zone2/temp
etc.
A 2017
The customfrequencymanagerservice applies to the CPU, up to 1794Mhz (HW performance). May lower with what looks like thermal throttling.
Does not apply to the GPU, which throttles itself somewhere around 76c from 962MHz to 845MHz.
Click to expand...
Click to collapse
I tried to set a game to a *non game* but game tuner doesnt let you switch anymore between them
I have A3 2016 and playing 20fps in game. ( Medium fps setting). If i select high frame rate my phone is heating much then my display doesn't work stable its sensitivity sucks when phone heats. It's not lagging to the last 3 circle. But if i see an enemy my device lags a lot and my fps drops 5-10 so i died more times bcz of the fps drop. Gameplay is best in Lineage Os 15.1 but it has overheating issue so display sucks when device is overheated.
bamcam92 said:
I tried to set a game to a *non game* but game tuner doesnt let you switch anymore between them
Click to expand...
Click to collapse
Downgrade. I have Game Tuner 3.3.03 & Game Optimizing Service 1.1.89.0, and it's there.
Edit: Game Tools 1.2.48.3, Game Launcher 3.1.00.5.
Bryan48765 said:
Downgrade. I have Game Tuner 3.3.03 & Game Optimizing Service 1.1.89.0, and it's there.
Click to expand...
Click to collapse
I have the option, but when i click apply it goes back to normal, doesnt remove the games from the category
bamcam92 said:
I have the option, but when i click apply it goes back to normal, doesnt remove the games from the category
Click to expand...
Click to collapse
The game optimizing service was downgraded? Reset (data for that app?)? The auto updates in the Samsung Store are forbidden? Else, maybe downgrade it further...
Bryan48765 said:
The game optimizing service was downgraded? Reset (data for that app?)? The auto updates in the Samsung Store are forbidden? Else, maybe downgrade it further...
Click to expand...
Click to collapse
Yes it was. App unistalled multiple times. Samsung store removed entirely. Downgraded already to the lowest. The point is that some time ago i was able to do that, now it just wont work
I've been playing PUBG Mobile for a while now and wanted to ask you how you find the performance on our Samsung S8.
When I had Android Nougat it really sucked (a problem that shouldn't happen, because of the great potential of our phone). However, now that I have Android Oreo I can play normally and without problems, but I still find that I should run better because I have seen it installed in cell phones of lower capacity and have more fluidity.
Someone who plays it and knows some trick to get 100% potential out of our S8?.
Translated with www.DeepL.com/Translator
check what's running in the background that may cause hickup, look out for memory usage
I have an S8+ with the google wiz rom (It erased about 300 apps and has some optimizations) and I still feeling that my phone doesn't run the game as fluid as it should be
mine S8+ still has nugget. haven't received update yet. all the other apps and games run fine except PUBG, it freezes then restarts.
Mine s8 doesn't support hdr graphics and ultra frame rates in pubg
Hello
I have an s8 with custom pie ( hades rom ), max setting are hd and high fram rate, while rooting and removing all bloatware etc...
Just download gfx tools there is a paid and free version, i played it on smooth graphics 60 fps no lag at all, remember that internet speed plays a big role.
Hi, I know this is super late but what I've found about gaming on the s8 is that there is absolutely nothing that will affect the performance of the phone or your experience of the game more than thermal throttling. I tried for weeks to fix my lag problems with all kinds of kernel tweaks, network teaks, getting rid of background processes and trying to keep my ram free and was totally stumped until I realized just how much my cpu was being supressed by thermal throttling. Download GameBench to get an overlay of your in game frames per second (you should be able to get a constant 60 fps no problem until the throttling sets in) and get Simple System Monitor to monitor your thermal sensors and cpu frequencies. You should start to see an immediate correlation between your fps drops and your and clock speeds and temperatures. If your phone is rooted you can use Kernel Adiutor to set your cpu govoner to performance (it just locks your cpu at max clockspeed). This will make the throtting very easy to see in simple system monitor because you can see how your max clock speed is gradually stepped down as thermal engine overrides the govoner.
Now for the fix. If your S8 is a exynos you are a lucky b***ard and you can probably find a software solution for disabling thermal throttling like with a custom kernel or by editing a few system files. If your stuck with a locked bootloader like I am on the snapdragon s8 than the only solution is to actually keep your phone cool while gaming. I use ice packs wrapped in a paper towel. They only last about 30-40 mins so you may need several ice packs and keep them in rotation. Whatever cooling solution you use just make sure its not too extreme or too sudden as rapid changes in temperature are not great for electronics. That's why I use a paper towel as a bit of a buffer between the phone and the ice pack. Works great for me and I maintain 60 fps all game.