Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
Don't overclock that high. 2419MHz at most. Overclocking too high will cause more heat and throttle earlier, only useful for a short benchmark such as HWBot Prime or Quadrant (Antutu takes longer and will overheat by the time it finishes). Trinity also supports up to 3014MHz, OP hasn't been updated.
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
You don't want to push the phone too much I think the Nexus 5 runs at 2.3 GHz. 2.7 MAY not be too bad but honestly, the phone runs pretty smooth as is. What benefits are you looking for from overclocking?
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
if you really wanted, the phone won't explode if you run it at 3015mhz either. the worst that will happen is that your phone won't be able to run that high, and will freeze and reboot.
and don't listen to all.. run your phone how YOU like. yes, it'll cause a little(not much) more heat, and will throttle a little earlier, but that's why people like me disable throttle, so that's a non issue. I run my phone at high CPU speeds all the time, and use 2880mhz high/300mhz low quite often. just because I feel like it, no other reason.
oh, I run trinity as well, and do all of Trinity's testing
MaLing15 said:
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
Click to expand...
Click to collapse
It's just what @jsgraphicart said. You're not really getting more out of your phone by overclocking. It's not going to run smoother, and most games don't lag anyway so they probably won't run better. I think most people just do it for benchmarks or just to check if it can run on a certain clockspeed.
Also what @simms22 said. You can do it if you want to, but simply because you want to because as far as I know there aren't really any benefits.
Back in my Palm Pre days, we used to overclock that thing to 1GHz. The default setting was 500MHz. I think it was even pushed to 1.2GHz. And it ran fine. But back then, you could tell the difference between a little lag at 500MHz and smoothness at 1GHz. With this phone and how Android has gotten smoother with every update, it's kind of hard to see any difference when overclocking. It will be smooth regardless.
oh, benefits, not really. a little more speed, yes. bit I would never call it a benefit, unless the speed difference was drastic, and its not.
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
bblzd said:
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
Click to expand...
Click to collapse
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Lethargy said:
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Click to expand...
Click to collapse
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
simms22 said:
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
Click to expand...
Click to collapse
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Lethargy said:
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Click to expand...
Click to collapse
on some devices??? on most devices! anyways, stability is overrated
LOL...no explosions on XDA allowed!
Related
Is overclocking and underclocking too many times bad? Because usually when i'm not playing a game or traveling I underclock it low to save battery and overclock it when im on constant use. Is it bad to do it too many times?
If it's overheating, YES, ITS BAD, STOP.
Overclocking and underclocking just speed up/down the cpu.
Overclocking: The faster a cpu goes, the more likely it'll glitch (Which will usually cause a freeze or reboot in Android) and the more power it takes (Which increases heat, can melt parts). There are serious risks to overclocking. Luckily, you're more likely to crash than melt something, and if that happens just reflash the rom to get back to a lower speed (Might have to wipe the phone, depends).
Underclocking: There are no bad side effects from underclocking except maybe having a really slow phone. The Sensation is already underclocked to 1.2GHz (from 1.5GHz). Underclocking uses less power and thus drains less battery. Android naturally underclocks when it's not used heavily and every time the screen is dimmed / off.
If you haven't read up on it, though, you shouldn't be messing with it. To answer your question directly, no, constantly speeding up and slowing down the cpu won't hurt it. It does that on its own all the time.
Like the person above me said, 1.5 GHz is native frequency for this CPU. So, it won't hurt the CPU as long as you don't go higher than that.
Swyped from my HTC Sensation
Thanks for that info about what the standard clock is for the Sensation (before HTC changed it).
Now I know I can clock it to 1500 and feel safe about it.
Oh no no not that I already normally set it to 1.7 ghz and its ok.
Thats not how I meant. Let me rephrase it. Is it dangerous to o/c u/c too many times back and forth?
kripwalk said:
Oh no no not that I already normally set it to 1.7 ghz and its ok.
Thats not how I meant. Let me rephrase it. Is it dangerous to o/c u/c too many times back and forth?
Click to expand...
Click to collapse
I got a bit off topic, I know, sorry. Android is always changing its own clock speed. When there are no apps in the foreground, the cpu is underclocked as low as it can go. When the screen turns on, the cpu gets overclocked a bit (and when you play a game, the cpu gets overclocked a lot). There's no harm at all, because Android already goes back and forth. A lot. Boot up SetCPU and just watch the current CPU and you'll see it varies in real time.
What you're doing just changes the min/max values. Change them all you want. It won't hurt anything.
Please excuse me for my ignorance, but I don't know much about these kinds of topics.
I wanted to know if anybody could be kind enough to explain the dangers and negatives of an overclocked CPU and an undervolted kernel?
I know their benefits because of some research I did, but I could never find a concrete answer explaining the negatives and dangers.
I've heard some horror stories of overheating handsets that get so hot that internal components fry, heard about damaged radios that need to be replaced, and loss of signal. But I'm not entirely sure if those instances are correlation instead of causation.
Any insight would be greatly appreciated. Thank you!
-Chris
Sent from my HTC Sensation 4G using XDA App
The general issue that applies to both modifications is that you are using the chips outside their specifications. Their whole behavior might no longer be as expected.
This is usually happening at such low level and in a so small range that it doesn't affect normal use.
Overclocking will definitely produce more heat. That's why people that overclock pcs to insane levels use non-standard cooling like dry ice or even liquid nitrogen.
As you can't change the way your phone will transport heat, there's only very limited room for overclocking.
The phone is designed to switch itself off if it gets too hot, however this is not something one should rely on.
Not sure about any specific risks of undervolting, but the general issues will definitely apply. Noone can guarantee for stuff to work as expected when you run components outside the specifications, as they were tested to run safe only inside the specs as supplied by the manufacturer.
It can cause permanent CPU damage which can lead to you bricking your phone, but the chances of that aren't that great. Usually if you undervolt too much, your phone will just reboot.
Stability is the biggest issue. It can put the components too far out of their comfort zone.
Unstable, unexpected behaviour and/or (in very strange cases drastically) reduced life expactancy. However, if you do undervolt your cpu, the only/main issue becomes unstable.
In my experience (lot of pc overclocking), you will notice when your material can't keep up with the settings and if you change it (back), no problems will occur.
aNYthing24 said:
It can cause permanent CPU damage which can lead to you bricking your phone, but the chances of that aren't that great. Usually if you undervolt too much, your phone will just reboot.
Click to expand...
Click to collapse
So would you say it's worth the risk to flash a ROM that has an overclocked CPU and undervolted kernel? I'm so scared to damage my device
Sent from my HTC Sensation 4G using XDA App
LPChris47 said:
So would you say it's worth the risk to flash a ROM that has an overclocked CPU and undervolted kernel? I'm so scared to damage my device
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Yes I would, in a way the lower voltage cancels out the higher voltage, and even produces less heat overall. There are no dangers of undervolting AFAIK, saving battery is good, although if you set the volt extremely low the phone will freeze up. Devs put the volt at a good level but most of the time you can lower it by a notch or increase it for no reason. If this phone ever gets 2GHz clock that would be a danger to run at, because the voltage would be insane.
How can I go about overclocking my droid charge? I am running TWEAKSTOCK 1.0 rom and was wondering how to overclock my charge?
I haven't seen any over clockable kernels so until then I don't think you can.
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Chitala383 said:
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
With the same kernel?
Well, if you actually searched, this would be clearly stated in many threads.
For GB overclocking, use Tegrak for now, until we can get an actual OC kernel up and running. I think Tegrak will work on the stock kernel as long as you're rooted, as it uses a module to modify the CPU frequency.
Sent from my SCH-I510 using xda premium
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
xdadevnube said:
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
BattsNotIncld said:
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
Click to expand...
Click to collapse
Take what I say with a grain of sand, I'm expressing my views without much scientific validation.
Keep in mind that overclocking is like icing on the cake. There are far more beneficial things like changing the scheduler to noop or deadline. Fugu tweaks and V-6 are highly recommended to improve responsiveness and improve your launcher resiliency. That said, I feel overclocking has its place and helps in many cases. I've noticed, in general, various tasks and some web-browsing will benefit from the increased clock speed. Some things don't ramp up the CPU very much and you won't notice much difference in that case.
I monitor my CPU usage with CPUNotify as well as OS Monitor.
I monitor the CPU temps with TempMonitor (it allows for a notifcation icon that shows the CPU temp.)
I use StabilityTest to check for overclock settings stability. The cool thing about Tegrak is that when you apply overclock settings on boot (paid version only) and you choose settings that crash the phone, the settings don't apply until most of the phone is already booted up, so you aren't stuck in an infinite boot loop of crashing fun. You should be able to simply change up the settings after they apply since the phone will be mostly idle by the time Tegrak settings are applied.
As for settings...
I use the Interactive X governor. I prefer this governor for its simplicity and ability to ramp up to high CPU clock speeds quickly. I enable the governor by typeing "su" and "ix enable" in Terminal Emulator when on Imoseyon's 4.0 kernel.
I change the "scaling min" to 200Mhz to avoid instability when CPU usage ramps down quickly.
Currently at CPU Level 0 I am at 1265mv Core Voltage, 1100mV (unchanged) Internal Voltage, and 1200 Mhz Frequency.
I don't actually change other CPU Levels.
Lately I've been just keeping at eye on temps so I haven't achieved my desired clock speed of a relatively low-voltage 1.4Ghz to 1.5Ghz.
Overclocking is very dependent on the particular sample you get. Some of us have "Golden Chips" and some of us have duds.
Your CPU should be totally safe at temps around 130 degrees F, although I suspect that it could even take higher sustained temps well above that if it needed. I don't actually know, this is speculation.
I like to keep my temps low in general, I rarely crack 100F with my current settings (weather is cool here.)
Overclocking computers is one of my hobbies, and its fun to dive into the phone side of things. I haven't been able to find a whole lot of information regarding overclocking the Hummingbird processor. People have overclocked to 1.6Ghz. Stability tests are essential to improve the reliability of your overclock. Die hards will run the tests for 24 hours to weeks in the computer realm. At least with computers its better understood how the stability test actually works. I run 24 hours of Orthos blend mode (Prime95) on each core.
With phones, its hard to say if it will truly be stable.
I test for an hour on the phone with StabilityTest and call it good. Hopefully in the future more information will come to light regarding how to properly overclock.
Remember, the other side of the coin is underclocking and undervolting. If you drop your voltage, you should see a nice increaes in battery life. If you drop your clocks, then you can drop your voltage even more. If you get your phone dialed in to where there isn't much background apps sucking juice- a phone that is UV/UC'ed should have excellent battery life.
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
kvswim said:
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
xdadevnube said:
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
Click to expand...
Click to collapse
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
kvswim said:
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
xdadevnube said:
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
Click to expand...
Click to collapse
Probably because no one has taken the time to write one. Not exactly in high demand. I knew of one "guide" but the site has been down for quite some time.
Of course there are noobs guides but nothing quite in depth. I suppose people don't write them because there are obvious limits set by the kernel dev, and anything beyond that requires someone who obviously knows what they're doing, which defeats they purpose of a guide.
Sent from my GT-P1000 using xda premium
Hello All,
I just got a LG Nexus 5 a couple months ago- I ran stock for the first several months and loved it, but wanted to take advantage of the services provided from custom ROMS and change-up the look of the stock google UI.
I made the mistake of not testing various things with the stock ROM and kernel for reference against the custom software I've installed- so I have no idea of how my phone was "running" before I changed it up. (Benchmark scores, CPU temp, Battery life, Battery Temp, ETC)
-so I have no idea if my phone was acting like this before I rooted.
TLTR-
In my FKU app I've enabled CPU temp monitoring and have noticed that this thing is running at rediculous temperatures:
39-43 Celsius when in pocket
45-55 When Browsing Web/Facebook/Snapchat
55-79 When playing 3D games (Giant Boulder of Death) or Benchmarking
THIS SEEMS DANGEROUS.
Apart from the slim chance of a small electrical fire igniting in my pocket whist on my way to get a burger, I'm concerned that my CPU is going to burn-out on me!
I've browsed these forums quite a bit and have seen (somewhat) similar threads about heat problems- but none pertaining to CPU overheating specifically.
I should probably add...
Currently Running:
Android 4.4.2
SlimKat 4.4.2 OFFICIAL-3080
Franco Kernel r37
Updated Bionic & Dalvik libraries
Has anyone experienced anything similar to whats going on with me?
These temps are fine. Your phone has a safety shut off at 99 and honestly there are some of is that turn thermal throttle off and hit that limit during benchmarks very regular. 79° isn't anything to worry about, your phone is fine. If it bothers you that much use FKU app to lower your temp for the thermal throttle but there's nothing to worry about here. Just ask @simms22
Sent from my Nexus 4 using XDA Premium 4 mobile app
I get around these temperature usually too. When on the wireless charger it overheated so I went back in kernel settings and put thermal throttling back to stock
If you're running a custom kernel I'd recommend keeping with stock thermal throttling.
Sent from my Nexus 5 using xda app-developers app
Hi,
Nothing dangerous, normal to have some heat with a quadcore CPU running at 2.26 Ghz, enclosed and without any hardware thermal cooling.
This temperature is "normal" while playing heavy games (3D games) or while benchmarking.
In any case there is a thermal protection, thermal throttling and in case of extreme heat: shutdown. This CPU can go at 100°C before shutdown so...
You can underclock or set different thermal settings with Franco kernel.
There is already a bunch of threads about that, even about CPU temp, read them closely.
yup, very normal. if those temps are too warm for you, use your phone in a freezer or just stop using the phone(just kidding). but yea, youre fine with nothing to worry about.
It should be noted that it'll actually start to automatically downclock itself after it hits 70C in order to maintain thermal integrity. Many, many phones do this, that's why long term benchmarks start off really fast, and then slow down.
If I remeber well ICs can work without any damage till 120 C
Tapatalk-kal küldve az én Nexus 5-el
Vincent Law said:
It should be noted that it'll actually start to automatically downclock itself after it hits 70C in order to maintain thermal integrity. Many, many phones do this, that's why long term benchmarks start off really fast, and then slow down.
Click to expand...
Click to collapse
I´m using kernel adiutor to prevend throttling. Before I did that indeed I´d get throttling behavour on the phone.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
simms22 said:
yup, very normal. if those temps are too warm for you, use your phone in a freezer or just stop using the phone(just kidding). but yea, youre fine with nothing to worry about.
Click to expand...
Click to collapse
Haha, not too warm for me - only wondering if it´s too warm for the phone.
I just got 17-18k on antutu. Stock rom,stock kernel. With elementalx kernel i can reach 27k but it is still bad for elemental x. What's wrong with my phone ? i flashed factory image again nothing changed also i just noticed when i underclock my cpu to 1.7 ghz i'm getting 28k on antutu.
Thermal throttle
Lethargy said:
Thermal throttle
Click to expand...
Click to collapse
Thanks for your answer.Is it normal ? I just bought this phone. So is this same for all other people ? One of my friends told me he got higher scores. If it isn't a general problem how i can prevent thermal throttle ?
msnnsm said:
Thanks for your answer.Is it normal ? I just bought this phone. So is this same for all other people ? One of my friends told me he got higher scores. If it isn't a general problem how i can prevent thermal throttle ?
Click to expand...
Click to collapse
By letting the phone cool down before the benchmark, or use a custom kernel which raises or disables it.
The other thing is to not care about benchmarks...
Lethargy said:
By letting the phone cool down before the benchmark, or use a custom kernel which raises or disables it.
Click to expand...
Click to collapse
I'm letting the phone cool down already. But it heats very fast during benchmark. I put it on fridge and i got 30k lol . Anyway there is nothing i can do.
Thanks for helping me :good:
msnnsm said:
I'm letting the phone cool down already. But it heats very fast during benchmark. I put it on fridge and i got 30k lol . Anyway there is nothing i can do.
Thanks for helping me :good:
Click to expand...
Click to collapse
Why do you care about benchmarks in the first place......
Putting your phone in the fridge, then getting an AMAZING score...does it make your day? Does showing it off make you happy? It's not what the phone is primarily designed for....it has much more useful functions, you know like internet, email, calling, gaming, photos...
More importantly...imagine benchmarks didn't exist for a moment. Did your phone actually feel slow before you did all these 'tests'??? Did you need to get 30k before you felt happy? Does a 'lower score' completely ruin the actual day to day user experience...
eddiehk6 said:
Why do you care about benchmarks in the first place......
Putting your phone in the fridge, then getting an AMAZING score...does it make your day? Does showing it off make you happy? It's not what the phone is primarily designed for....it has much more useful functions, you know like internet, email, calling, gaming, photos...
More importantly...imagine benchmarks didn't exist for a moment. Did your phone actually feel slow before you did all these 'tests'??? Did you need to get 30k before you felt happy? Does a 'lower score' completely ruin the actual day to day user experience...
Click to expand...
Click to collapse
Firstly i don't need to tell you why i'm trying to get higher score but i will because you're talking too agresively with me without reason.I don't care about score. If every nexus 5 would be the same and get just 15k score including mine i would accept my phone with 15k. But others phones get higher and there is something wrong with mine. It's getting hot more than others. So that's not like it should be.I hope you understood why i'm trying to fix it and sorry if my english isn't understandable.
No. Your phone isn't heating up more. You're starting when the device is already warm.
Lethargy said:
No. Your phone isn't heating up more. You're starting when the device is already warm.
Click to expand...
Click to collapse
I'm pretty sure i'm starting it when it's cold. I didn't touch it for 15 minutes isn't it enough ?
msnnsm said:
I'm pretty sure i'm starting it when it's cold. I didn't touch it for 15 minutes isn't it enough ?
Click to expand...
Click to collapse
At least use an app to look at CPU temp ._.
Lethargy said:
At least use an app to look at CPU temp ._.
Click to expand...
Click to collapse
Hmm you're right. Do you know a good one ? I got 28.8k now with elemental x kernel with "Undervolt" feature. To be honest i don't know how much is normal for a nexus 5 device with this kernel.
msnnsm said:
I don't care about score
Click to expand...
Click to collapse
Yes do you, that's why you opened the thread..
The post sounds aggressive, but it's really trying to change the way you think about scores in the first place..
But others phones get higher and there is something wrong with mine.
Click to expand...
Click to collapse
No, just because other people get highers 'scores' does not mean there is something wrong with your phone.
Before you started running 'tests', were you experiencing any actual issues?
It's getting hot more than others. So that's not like it should be.I hope you understood why i'm trying to fix it and sorry if my english isn't understandable.
Click to expand...
Click to collapse
If it's getting hot, is this because you're running unnecessary benchmarks...
Or any other activities which are causing it to get hot? This could be an app or hardware issue, both nothing to do with your benchmark. Are you comparing actual temperatures in degrees to identical phones doing exactly the same activities side by side, or does it just feel a bit warmer?
What I'm trying to say is your obsession with the score is causing you unnecessary stress...you are trying to fix something which does not need fixing.
So go back to the original thinking:
- Imagine scores don't exist
- Did the phone actually feel slow in day to day normal usage before you started running benchmarks?
Or:
- Stop running tests, forget about them
- Use the phone normally
- Enjoy using the phone again
Let...it...go...
eddiehk6 said:
Yes do you, that's why you opened the thread..
The post sounds aggressive, but it's really trying to change the way you think about scores in the first place..
No, just because other people get highers 'scores' does not mean there is something wrong with your phone.
Before you started running 'tests', were you experiencing any actual issues?
If it's getting hot, is this because you're running unnecessary benchmarks...
Or any other activities which are causing it to get hot? This could be an app or hardware issue, both nothing to do with your benchmark. Are you comparing actual temperatures in degrees to identical phones doing exactly the same activities side by side, or does it just feel a bit warmer?
What I'm trying to say is your obsession with the score is causing you unnecessary stress...you are trying to fix something which does not need fixing.
So go back to the original thinking:
- Imagine scores don't exist
- Did the phone actually feel slow in day to day normal usage before you started running benchmarks?
Or:
- Stop running tests, forget about them
- Use the phone normally
- Enjoy using the phone again
Let...it...go...
Click to expand...
Click to collapse
The first time run it i just wanted to see how my phone is powerful because i felt a little lag on asphalt 8 yesterday, so yes i wasn't expecting any issues but when i saw i got 17k i think that difference is just huge. I don't care if my device is same at gaming,multitasking with other nexus devices but benchmark makes me think it's not right.
In normal usage; yeah it is fast But I'm not sure my device is how it's supposed to be like this. But if you say it's normal and benchmark's not meaning anything i won't care. But there should be a reason all devices got different scores.
msnnsm said:
The first time run it i just wanted to see how my phone is powerful because i felt a little lag on asphalt 8 yesterday, so yes i wasn't expecting any issues but when i saw i got 17k i think that difference is just huge. I don't care if my device is same at gaming,multitasking with other nexus devices but benchmark makes me think it's not right.
Click to expand...
Click to collapse
So it is sort of only the benchmark which is making you think something is not right
You don't need a score to see how powerful your phone is. It will breeze through most tasks just fine. "A little lag" on a graphically intense game is to be expected sometimes.
Gaming -> High CPU load -> heat -> thermal throttle -> bit of lag
Laws of physics
In normal usage; yeah it is fast
Click to expand...
Click to collapse
This is the only real 'benchmark' which is actually important in normal day to day usage.
But I'm not sure my device is how it's supposed to be like this. But if you say it's normal and benchmark's not meaning anything i won't care. But there should be a reason all devices got different scores.
Click to expand...
Click to collapse
Yes there is a reason we all get different scores, the same reason we all get different battery life. There are many variables, not least temperature and thermal throttling.
We have different number of apps installed and running at any one time, things syncing, mods, scripts, ROMs, kernels, all different. No two CPUs and Nexus 5s are exactly identical either. So therefore you get different 'scores'. Even if you had two stock factory reset phones side by side running the same test, they'll get different scores.
And just because your score is lower, it doesnt necessarily mean that something is wrong, or that your phone is always slow. It is just a nominal number from an app at a particular point in time. It still feels fast, and is fast...
eddiehk6 said:
So it is sort of only the benchmark which is making you think something is not right
Even if you had two stock factory reset phones side by side running the same test, they'll get different scores.
Click to expand...
Click to collapse
It doesn't make any sense
And just because your score is lower, it doesnt necessarily mean that something is wrong, or that your phone is always slow. It is just a nominal number from an app at a particular point in time. It still feels fast, and is fast...
Click to expand...
Click to collapse
Okey, i trust you. Since i just bought phone and didn't test it much really i won't test it or try to improve it for now.
The way a phone works doesn't lend itself well to benchmarks. That's why manufacturers like Samsung have traditionally "cheated" on benchmarks by ensuring maximum clock speeds are used when they detect a bench marking application.
If you want to maximize your benchmark scores you simply need to disable thermal throttling (or increase its limit) and also use optimized Dalvik copied from another device.
rootSU said:
The other thing is to not care about benchmarks...
Click to expand...
Click to collapse
This. Thermal throttle is a way to keep your phone regulated into normal temperatures specified by the device manufacturer. However, it's generally safe to raise it a bit, mine is set to 85.
aw man, its too bad i wasnt around earlier