Is my Nexus 6P CPU throttling my app? - Nexus 6P Q&A, Help & Troubleshooting

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!

Related

WARNING!! Don't overclock GPU

I am running the siah kernel on my s3 and a few minutes ago I overclocked the GPU and I almost ''burned it''. The screen started flickering when running graphic heavy tasks, had to reboot twice, and thanks god it got back to it's normal behavior. This is what happens on the SIII, but it might happen the same on other devices, too.
Overclocking is always a risk isn't it? Keep to safe or stable clocks
maimutul said:
I am running the siah kernel on my s3 and a few minutes ago I overclocked the GPU and I almost ''burned it''. The screen started flickering when running graphic heavy tasks, had to reboot twice, and thanks god it got back to it's normal behavior. This is what happens on the SIII, but it might happen the same on other devices, too.
Click to expand...
Click to collapse
Overclocking will generate more heat, especially when it's running at the higher clocks you should always be careful when you overclock.
Well, when you push something to work at a higher clock speed than what was intended, do you expect magical things to happen?
Sent from my GT-I9300 using Tapatalk 2
Use stock kernel keep problems away...
Heat = bad
All heat and no cool makes gpu a dull boy
xD
Sent from my GT-I9300 using Tapatalk 2
that was a good movie..
Theshawty said:
Heat = bad
All heat and no cool makes gpu a pool of molten sillicone inside the phone
xD
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Fixed for you
maimutul said:
I am running the siah kernel on my s3 and a few minutes ago I overclocked the GPU and I almost ''burned it''. The screen started flickering when running graphic heavy tasks, had to reboot twice, and thanks god it got back to it's normal behavior. This is what happens on the SIII, but it might happen the same on other devices, too.
Click to expand...
Click to collapse
you must be joking right, we know overclocking is always risky, but overclocking to 800mhz is just stupidity in its best, be specific and try moderate overclocking and not abusive one.
Envoyé depuis mon GT-I9300 avec Tapatalk
I never had problems overclocking the CPU, so I thought I would be a good idea to try the GPU, too. I was lucky this time, I tested it with modern combat 4 and worked as usual.
Sent from my GT-N7100 using xda app-developers app
delsus said:
Fixed for you
Click to expand...
Click to collapse
Fair enough. :good:
Sent from my GT-I9300 using Tapatalk 2
I have no problem to overclock the CPU even been in 1800, but when it comes to GPU I can not accelerate to more than 533, when I select 640 the phone becomes to lagy and I can see some artifacts.
Enviado desde mi GT-I9300 usando Tapatalk 2
maimutul said:
I am running the siah kernel on my s3 and a few minutes ago I overclocked the GPU and I almost ''burned it''. The screen started flickering when running graphic heavy tasks, had to reboot twice, and thanks god it got back to it's normal behavior. This is what happens on the SIII, but it might happen the same on other devices, too.
Click to expand...
Click to collapse
Of course you will get artifacts if you going to oc gpu too much, because chip gets too hot, so you need to oc in small steps and see which frequency/voltages fits for your phone. Every phone is different.
The silicon is what defines what you can oc to. D
Different silicon quality that is
Sent from my GT-I9300 using Tapatalk 2
Theshawty said:
Heat = bad
All heat and no cool makes gpu a dull boy
xD
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
No, ANYTHING UNDER 65c is totally normal.
@OP, my GPU is overclocked to 700mhz, with a good undervolt, stable as a rock! Phones react differently to Overclocks. I can push my phone to 700mhz and 1.7ghz and it runs stable as hell - you maybe can't.
Considering the fact that the Mali 400 was designed to operate at a 275 target clock rate, I wouldn't be surprised if it craps out at more than twice the clock speed. Heck, the stock 440 mhz already surpasses this target clock by 50%
Sent from my GT-I9300 using Tapatalk 2
As someone that's been overclocking for over a decade, it slightly depresses me that overclocking today (on all systems and devices) is so easy that people that clearly have no idea what they are doing, the consequences of what they are doing or know what the solutions to the problems they encounter are able to jump right in and do it.
Everyone in this thread is talking about heat, despite the fact that the OP's, and a number of other peoples issues posted here are clearly not heat issues at all. The flickering and artifacts people are talking about is in 90% of the cases here caused by a GPU voltage that is insufficient for the current clock frequency. Your GPU won't overheat running your UI for example, nor will it have massively overheated by running a game for a few seconds. This is a voltage issue, not heat. Lower your GPU voltage at your lower clock speeds and you'll get exactly the same graphic issues, despite the fact you've made your GPU run cooler.
Also, for the record. Just because a chip is voltage limit, increasing it's voltage by X amount isn't guaranteed to fix it. Some chips will simply just not be capable of hitting a certain speed. Being voltage limited isn't an excuse to whack the voltage slider up, because that's definitely a quick way to a dead phone! If a given clock speed quickly gives you artifacts, try giving an extra 25-50mv. If there is no improvement I'd give up, as the gains start becoming impractical for the voltage levels required.
ballsofsteel said:
Considering the fact that the Mali 400 was designed to operate at a 275 target clock rate, I wouldn't be surprised if it craps out at more than twice the clock speed. Heck, the stock 440 mhz already surpasses this target clock by 50%
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
No it isn't. Arm's official website quotes upto 395MHz @ 65nm, and given that clockspeed headroom increases as process nodes decrease, getting 440+MHz at 40nm sounds exactly like what you'd expect. Given that many many many things can effect this, quoting theoretical design figures is largely useless anyway. It all comes down to what performance metrics the SoC designer is looking for, as you can easily exchange power consumption for performance and gain more clock speed.
darkbahamut said:
As someone that's been overclocking for over a decade, it slightly depresses me that overclocking today (on all systems and devices) is so easy that people that clearly have no idea what they are doing, the consequences of what they are doing or know what the solutions to the problems they encounter are able to jump right in and do it.
Everyone in this thread is talking about heat, despite the fact that the OP's, and a number of other peoples issues posted here are clearly not heat issues at all. The flickering and artifacts people are talking about is in 90% of the cases here caused by a GPU voltage that is insufficient for the current clock frequency. Your GPU won't overheat running your UI for example, nor will it have massively overheated by running a game for a few seconds. This is a voltage issue, not heat. Lower your GPU voltage at your lower clock speeds and you'll get exactly the same graphic issues, despite the fact you've made your GPU run cooler.
Also, for the record. Just because a chip is voltage limit, increasing it's voltage by X amount isn't guaranteed to fix it. Some chips will simply just not be capable of hitting a certain speed. Being voltage limited isn't an excuse to whack the voltage slider up, because that's definitely a quick way to a dead phone! If a given clock speed quickly gives you artifacts, try giving an extra 25-50mv. If there is no improvement I'd give up, as the gains start becoming impractical for the voltage levels required.
No it isn't. Arm's official website quotes upto 395MHz @ 65nm, and given that clockspeed headroom increases as process nodes decrease, getting 440+MHz at 40nm sounds exactly like what you'd expect. Given that many many many things can effect this, quoting theoretical design figures is largely useless anyway. It all comes down to what performance metrics the SoC designer is looking for, as you can easily exchange power consumption for performance and gain more clock speed.
Click to expand...
Click to collapse
:good::good::good::good::good: thumbs up to another person that know's what he is doing glad there are people out there that aren't N00BS I've been overclocking for 8 years so i know what i'm doing.
I clock my GPU to 640 MHz by most ,increases benchs but artifacts might appear and phone might crash,and have to reboot again by removing battery.
And by 640 MHz I mean min frequency(for a minute or two)
If max then 800 MHz works ok
sent fromXperia sT21i
Everything stock
i kill an s2 with overclocking so finish never again

[Q] Will overheating ever get fixed?

Will overheating ever get fixed? Pretty much all roms I've tried overheats soo much that the phone feels uncomfortable to hold. I'm not talking gaming only but by just simply browsing the Web easily heats up the phone to 40 degrees.
Is this happening to both 9500 and 9505? I own the 9500 octa version.
Use a custom kernel and underclock it so it doesn't overheat as much
I think the heat problem come when the phone release at first, and hard to fix.
You must be can imagine when a machine work, they will produce heat. How if that machine is powerful, and the machine case is thin, of course that machine will make the case hot. That's the case of SGS4 i9500 imo.
So if samsung (or we ?) want to fixed it, they'll have to shutdown few core when the core is really not needed. But if the phone is used to play heavy duty game, all core will be needed and the phone will be heated by the core.
ar216893 said:
I think the heat problem come when the phone release at first, and hard to fix.
You must be can imagine when a machine work, they will produce heat. How if that machine is powerful, and the machine case is thin, of course that machine will make the case hot. That's the case of SGS4 i9500 imo.
So if samsung (or we ?) want to fixed it, they'll have to shutdown few core when the core is really not needed. But if the phone is used to play heavy duty game, all core will be needed and the phone will be heated by the core.
Click to expand...
Click to collapse
I have a i9505 that's throttling in games, especially if I leave it in its official Samsung case. Is it possible to shut 1 or 2 cores completely off? I think it might be easier for the phone to maintain good performance if it's running with 2 higher clocked cores (due to less heat) versus 4 throttling cores.
Mushoz said:
I have a i9505 that's throttling in games, especially if I leave it in its official Samsung case. Is it possible to shut 1 or 2 cores completely off? I think it might be easier for the phone to maintain good performance if it's running with 2 higher clocked cores (due to less heat) versus 4 throttling cores.
Click to expand...
Click to collapse
Ah, so both brother from samsung galaxy s4 (i9500 & i9505) have the same heat issue.
I didn't know about shutting down the core completely off since I'm not a dev, and I'm new to android either.
Maybe few or alot devs out there already working that out. Me also keep searching for the fix those heat problem, but until now, what can I do is just underclock the phone, some people says by underclocking it (on my device i9500) can make only the little core work, but sometimes I feel the big core also work and make my device warm (I think about 37 -39 C)
I am lucky I have never faced this heating issue
Sent from my GT-I9500 using xda app-developers app
noufel said:
I am lucky I have never faced this heating issue
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Then u surely have a case and u never used a heavy app ...
AvelonTs said:
Then u surely have a case and u never used a heavy app ...
Click to expand...
Click to collapse
Actually this is my second s4 my previous one used to heat like crazy but this is much much better.
I play games like shadowgun,asphalt 8 nd most wanted etc those are heavy enuff apps.
Sent from my GT-I9500 using xda app-developers app
I have Android Revolution HD 3.0 and Ausdim kernel v15, its not getting as hot like it used to be.
Verstuurd van mijn GT-I9505
Undervolted and underclocked.. No more heating issues for me..

This phone is a scam.

I bought this phone because of the quad core 1.9Ghz processor, but as a matter of fact, this phone is a quad core 19ghz processor only for 5 or so minutes at a time, then it's just a 1.2Ghz quad core processor.
I don't know what's the reason for this, but I suspect overheating or Scamsung being shady and still cheating the benchmarks.
Anyway, try this: download Antutu Benchmark (or any other benchmark really) and run a full test: if the phone is "fresh" you'll get 29000 or so points. Good. Now run it again, you'll get less, and if you run it again, you'll get even less.
What do you think is the reason for this? This phone is unable to keep it's maximum frequency for more than 5 minutes at a time, and so it underclocks itself to 1.2Ghz (check it with CPU Z or anything, it will never go to 1.9 ever again after you get the lowered score in Antutu) and stays there for hours before it goes back to 1.9 again.
Check out these screenshots, and look at the time I ran the benchmarks. It only took 3 minutes to go from 29000 to 26000, then I ran it 2 more times and it went as low as 22000 with massive performance losses in 3D graphics (OpenGL test runs at around 30-40fps the first time then 15-24, basically half speed).
If this isn't a scam I don't know what it is. They should have advertised this as having a quad core mode for 5 minutes every now and then, or being a real quad core only in winter, because as a matter of fact it runs like a mid tier dual core most of the time. No wonder the UI lags like crazy all the time after you browse the internet a while or play a 3D game.
Sent from my Scamsung gaLAGsy S4.
This is not scam. This is **** done by samsung in 4.4.2 update. They enabled something called dynamic voltage and frequency scaling.
There is a xposed module to disable it.
See this thread for more info - http://forum.xda-developers.com/showthread.php?t=2674928
Sent from my GT-I9500 using XDA Premium 4 mobile app
maxsam4 said:
This is not scam. This is **** done by samsung in 4.4.2 update. They enabled something called dynamic voltage and frequency scaling.
There is a xposed module to disable it.
See this thread for more info - http://forum.xda-developers.com/showthread.php?t=2674928
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really now. I need to try this, because right now I'm MAD. I had a similar problem with the Xperia S that happened only when playing and charging at the same time, and you can't believe how angry I was at that.
Since I bought the phone just recently and it was already on KitKat, and I did some googling for i9505 and overheating and all sorts of related keywords and found nothing, I expected this behavior to be pretty much undiscovered. I'll try the exposed module and report back.
Anyway, since you need root, and mods, the phone is still a scam because the average user wil NEVER EVER figure this out on his own. It's advertised as a 1.9Ghz quad core when in reality it never runs at that speed.
I confirm that it was caused by the DVFS. What were they thinking when they implemented such a thing on the phone?
Facepalm.
MarkMRL said:
Really now. I need to try this, because right now I'm MAD. I had a similar problem with the Xperia S that happened only when playing and charging at the same time, and you can't believe how angry I was at that.
Since I bought the phone just recently and it was already on KitKat, and I did some googling for i9505 and overheating and all sorts of related keywords and found nothing, I expected this behavior to be pretty much undiscovered. I'll try the exposed module and report back.
Anyway, since you need root, and mods, the phone is still a scam because the average user wil NEVER EVER figure this out on his own. It's advertised as a 1.9Ghz quad core when in reality it never runs at that speed.
Click to expand...
Click to collapse
1.9 ghz is it's max speed which it does achieve for first few minutes when a game runs and hence it is not a scam. No mobile processor runs at it's max frequency 24/7 or else you would have to keep charging the phone every hour and the phone would probably die in a day due to overheating -_-
Samsung did this to increase battery life but the move backfired
The only way you can do something about is by rooting the mobile which infact will void ur warranty.
Press the thanks button if helped you
Sent from my GT-I9500 using XDA Premium 4 mobile app
maxsam4 said:
1.9 ghz is it's max speed which it does achieve for first few minutes when a game runs and hence it is not a scam. No mobile processor runs at it's max frequency 24/7 or else you would have to keep charging the phone every hour and the phone would probably die in a day due to overheating -_-
Samsung did this to increase battery life but the move backfired
The only way you can do something about is by rooting the mobile which infact will void ur warranty.
Press the thanks button if helped you
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It should run max speed when needed, of course it won't run at full speed all the times, but if it runs at 1200mhz when I'm running a game or the browser and it's lagging like crazy then there's a problem.
I already rooted, voided my warranty, tripped my know, and fixed this issue with the xposed module the other user recommended.
Bottom line, unless you void your warranty and install user made mods this phone is a scam, because as soon as it get slightly warm it underclocks like crazy causing lag and horrible performances. There should be lawsuits up the ass about this. Users shouldn't accept having their phone arbitrarily underclocked for no reason like this.
What a retard.
Sent from my SM-G900H using XDA Premium 4 mobile app
MarkMRL said:
It should run max speed when needed, of course it won't run at full speed all the times, but if it runs at 1200mhz when I'm running a game or the browser and it's lagging like crazy then there's a problem.
I already rooted, voided my warranty, tripped my know, and fixed this issue with the xposed module the other user recommended.
Bottom line, unless you void your warranty and install user made mods this phone is a scam, because as soon as it get slightly warm it underclocks like crazy causing lag and horrible performances. There should be lawsuits up the ass about this. Users shouldn't accept having their phone arbitrarily underclocked for no reason like this.
Click to expand...
Click to collapse
Sorry to say but I only play cards game so I am not any concerned or bored by this issue.
I bought this phone as a phone not as a playstation 9.
lolo9393 said:
Sorry to say but I only play cards game so I am not any concerned or bored by this issue.
I bought this phone as a phone not as a playstation 9.
Click to expand...
Click to collapse
You bought a 500 bucks, flagship, quad core, 1080p, multimedia focused smartphone to use as a "phone"? Maybe a Nokia 3310 and a deck of cards would have been a better investment for you.
MarkMRL said:
You bought a 500 bucks, flagship, quad core, 1080p, multimedia focused smartphone to use as a "phone"? Maybe a Nokia 3310 and a deck of cards would have been a better investment for you.
Click to expand...
Click to collapse
I got all that already from long ago but I wanted to test something more uptodate!!!!
I have decrease the cpu speed to 20 Mhz with success and my battery last more than expected with my old 3310.
I am happy.
Chjeers
PS: I paid 600 Euros not 500 bucks that's a difference!!!!!!
Just stop fighting. Everyone uses his mobile differently and has different needs/expectations -_-
Sent from my GT-I9500 using XDA Premium 4 mobile app

Honor 7 stutter while scrolling on some apps

I've had the Honor 7 for almost a month now and it's a great phone, I have noticed one or two issues in regards to lag though. If I am in a Skype call the Skype app shows noticeable lag when scrolling through contacts. Twitter also lags when scrolling through the twitter feed but once images have loaded it is smooth. Is anyone else having similar issues?
I'm not completely satisfied with the performance either. I think the cpu is being too reserved. It uses big.little which means its 2 quad core processors rather than a true octacore. They can't work together, its either the big or little that's running things.
In normal day to day tasks it will be using the little quad core a53 1.5ghz. This is a midrange chip and doesn't even run full speed scrolling through pages etc. In some situations I've noticed better performance on my Redmi 1s.
I'm feeling it a bit laggy too. Nexus 5 with custom rom(euphoria OS) was blazing fast with "worse" CPU.
Spyrek10 said:
I'm feeling it a bit laggy too. Nexus 5 with custom rom(euphoria OS) was blazing fast with "worse" CPU.
Click to expand...
Click to collapse
At least its not as bad as the z5 compact https://www.youtube.com/watch?v=6Om8LHKMwjU
In my opinion these big.little cpu's need to go. It puts low end cpu's to do every day tasks and the difference is noticeable. The only thing they are better at is benchmarking. My guess is chipmakers (ARM) failed this year. The best they could come up with is the a57 but it runs so hot and consumes so much power that putting it on its own was impossible. Hence the 'big.little' which would allow high benchmark scores but have most tasks run on the slower chip. Mediatek or a snapdragon 801/805 are better. I think Honor can improve things a bit in updates though.
Another weird issue is gmail crashing. For example when opening email from xda app just closes. Older versions and clearing app data didn't help.
Funny you mention the N5 as having just put Android M on it, it's flying and I was spending some time tonight playing around and wondering how it can be so quick at everything despite being so old (relatively speaking) and using very old SoC.
Doze has also made the battery much better, so while it's not as sexy as modern devices it is showing up more than just the Honor 7.
Of course, I'm using my H7 day to day and the N5 stays at home, but it's still impossible to ignore.
Sent from my Nexus 5 using Tapatalk
The lag doesn't really bother me since I don't use twitter on my phone much but I just found it odd since there's no lag when scrolling on YouTube wine there's a 1080p video playing. Maybe they'll fix it with updates (that will hopefully come out faster then we might expect lol)
I've faced lag in tapatalk & Google now widget consistently. This scroll stutter does come up quite frequently even in other apps
Sent from my PLK-UL00 using Tapatalk
Is anybody experience phone restart when using Google's indic keyboard?
anyone else notice how much more the play store lags after the update?

CPU Throttling - warranty?

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

Categories

Resources