Related
So, nabbed an Asus Transformer TF101 off Craigslist for $225. With keyboard. Feeling good about that.
Next question for semi-geeky me. To leave a decent Ice Cream Sandwich -- the ASUS-approved version -- on the tablet or to venture into the unknown world of rooting and custom Jelly Bean ROMs? Sheesh. I tried to resist. But... just... could... NOT...
Did I mention I didn't have a Windows PC to make rooting a bit easier? That left me with the need to do it via an iMac. I've gone and lost that url, but think it is one of the pages on this site.
From there, how do I pick a ROM? All sorts of threads, all of 'em messy (at least to the noob in the room). So I noted EOS got a lot of uptalk and went that route. After more than few false starts (manually typing in command lines kept introducing unintentional HUMAN ERROR into the mix) I got lift-off.
Did I mention my wife owns a Nexus 7 (one of the nicest little bits of hardware/software I know of... no no, the Nexus, not her!! She's stellar, but I digress).
In light of the Nexus' buttery feel, I was hoping for similar from my Asus Transformer. Well, not quite. Maybe the dual vs quad core chip has something to do with that. But I do very much like my larger (10") screen vs. her 7" and the keyboard... and Jelly Bean seems pretty darn nice even on a dual core tegra chip. Still hoping for a little more butter as the EOS nightly people do their thing. (I thank and thank them!!)
Oh. EOS answered my next problem before I got to it. How to overclock? Right in the setup I can do it.... tried all sorts of settings there and ended up with backing it off to only 1.2 (from 1.0) ghz. Not a game-player, just a blogger. Downloaded all my favorite apps -- kindle reader, YouVersion Bible, Skype, and so on. Oh, and of course some board games so I can play 'em with my Dearling.
Last night EOS suddenly updates my gapps. Hmmm. No big change, except maybe things are slightly snappier?
Questions I still have:
I installed an older (I think) booter/recovery module (or whatever the heck it is called). "Team Rogue" "Rogue XM Recovery 1.5.0 (CWM-Based Recovery v5.0.2.8)"
This recovery does not let me write to my external SD card (or even read from it) but will write / read to a USB stick if I mount it of course via their menu. My question:
Is this the newest and best boot/recovery tool? And if not, how and to what tool should I upgrade/switch?
Really enjoying my toy.
I've come up with a few more questions of a semi-general nature... but perhaps overly technical. If wrongly posted here, please advise...
Why does the Tegra 2 chip in my TF101 apparently change speeds and therefore frequencies? Using the setup app in EOS's version of Jelly Bean, one can alter two frequency / speed settings -- minimum and maximum -- and I'm thinking that is one frequency per core?
The reason that matters is because I'm experiencing an occasional spontaneous reboot. My settings were at 216 MHz (minimum) and 1200 MHz (maximum). I'm in over my head at this point as far as knowing if the lower value in particular is too low.
Anyone else have any thoughts?
Thanks.
shonkin said:
I've come up with a few more questions of a semi-general nature... but perhaps overly technical. If wrongly posted here, please advise...
Why does the Tegra 2 chip in my TF101 apparently change speeds and therefore frequencies? Using the setup app in EOS's version of Jelly Bean, one can alter two frequency / speed settings -- minimum and maximum -- and I'm thinking that is one frequency per core?
The reason that matters is because I'm experiencing an occasional spontaneous reboot. My settings were at 216 MHz (minimum) and 1200 MHz (maximum). I'm in over my head at this point as far as knowing if the lower value in particular is too low.
Anyone else have any thoughts?
Thanks.
Click to expand...
Click to collapse
The 216mhz is the slowest speed your CPU will go on both cores. This could cause reboots if too low because the operating system crashes because it cannot get everything done it needs / wants to. Try to up it to 500 and play around with the value so you dont get reboots, low mhz is better for battery when in deep sleep etc but can become unstable.
The 1200 mhz could also cause reboots if too high, however I don't think that sounds high, some go as high as 1500 or 1600 so that is probably not the issue.
The mhz, either min or max, applies to both cores equally on tegra 2.
Your wife's nexus has 4 cores and a single ninja core for background activity, so on hers, you can set min and max for the 4 cores and the ninja core seperately.
Hope that helps!
gunswick said:
The 216mhz is the slowest speed your CPU will go on both cores. This could cause reboots if too low because the operating system crashes because it cannot get everything done it needs / wants to. Try to up it to 500 and play around with the value so you dont get reboots, low mhz is better for battery when in deep sleep etc but can become unstable.
The 1200 mhz could also cause reboots if too high, however I don't think that sounds high, some go as high as 1500 or 1600 so that is probably not the issue.
The mhz, either min or max, applies to both cores equally on tegra 2.
Your wife's nexus has 4 cores and a single ninja core for background activity, so on hers, you can set min and max for the 4 cores and the ninja core seperately.
Hope that helps!
Click to expand...
Click to collapse
The EOS (#79) Rom's latest update seems to have helped some... along with my using SETCPU (which may or may not be more effficient but was suggested to me by another poster here).
I'm running with the very low 216mhz still, but have upped the max all the way to 1600mhz. So far, no spontaneous reboots like before even when running angry bird, a browser, and other junk. I used an app (SETCPU) to create a battery charging profile that allows for the tablet to run between 1200 and 1600 when plugged in and charging. More to see if it worked than because I have any real need for it.... and it did work just fine.
But I appreciate the comment re 216 being really low. And if it does exhibit strange behavior again, I'll monkey with the low setting to see if it helps.
Does anyone who has looked at the kernel source know if we will be able to do RAM overclocking? We know from the whitepaper that playing games on the resolution that the N10 has will take 10+ gigabytes per second of bandwidth so a memory OC should be able to help out considerably, especially if overclocking the GPU as well.
Additionally, how come we never see an area in the tunables where we can tweak timings? All we ever see is voltage and frequency, but the memory has to have primary and subtimings as well, just like all regular computer memory. If someone could make the timings able to be modified we might be able to get some series bandwidth increases out of these.
Oh and one last thing, why dont we ever see memory voltage setting either? We have core, gpu, and video decoding core voltages but being able to tweak memory voltage would be a great addition too. We already know that the Exynos 5 dual uses low power 1.35v DDR3 memory. If Samsung's other LP 1.35v DDR3 chips are any indication, these things have MASSIVE overclock potential. I have seen people running them up over 2400MHz!
bump since we have device support now. Any kernels dev's want to look into the possibility of these things?
I too would be very interested in seeing some RAM overclocking/voltage tweaking; I believe it could open up a lot of potential
If a kernel gets developed that can accomplish this I'll go to the store and buy a n10 that very same day.
Right now I'll show patience and wait to read true reviews from actual users.
Sent from my Nexus 7 using Tapatalk 2
I'm not overclocking my device, in fact if anything i'll under volt it. If I could get a 3rd party accidental warranty, it would be a whole different story.
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've got a windows 8 razer edge pro in my house that I was attempting to get dying light to run on, and it seems the game doesn't like the base CPU speed(1.9GHz). Unfortunately, instead of letting me test and see for myself it enforces some minimum specs to even launch the main page, but I'm quite confident the game will run fine on the tablet, and would like to get the chance to fail for myself instead of being immediately shut down. Does anyone know of any method I can use to block or spoof a program's hardware check so I can test run the game?
not sure about spoofing hardware spec
sure you can run this game ok?
your CPU doesnt meet even the minimum requirements and your GPU isnt supported either. not played the game myself but read that this game doesnt run that well even on a decent pc.
from my experience of pc gaming, even the minimum requirements isnt enough for a enjoyable, playable experience
i agree though. Id prefer to test it and see for myself that its unplayable than the game just asuming the specs arent good enough.
I've heard it's pretty unoptimized CPU-wise, so I'm not entirely certain. However, I've been playing the game on my desktop, which is quite old. The benchmark scores on the desktop's Nvidia 450 GTS are roughly similar to the edge's mobile video card(about a 10% higher benchmark, but it runs very well without minimizing every setting), and both cards support DX11.
The CPU might be an issue, but it does support 3 GHz turbo, and is an i7. My desktop runs a similar generation i3 at 3.2GHz, which also has a similar benchmark to the 1.9GHz i7 in the tablet even without turbo, so I'm just tempted to test everything. I just find it unfortunate I'm being prevented from doing so, and became interested in the longterm ability to spoof past an application's checks. I'm a bit worried these mandatory checks may become more common.
I appreciate the reply, steam posts seem to be full of "Get better hardware lol" style replies instead of solutions.
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