{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is unfortunate, it is not even hot so I don't know what's up.
Sent from my LG-E970 using xda premium
There is the temp as says setCPU
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Tim4 said:
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Click to expand...
Click to collapse
I am unsure if this is just over caution on their part of if this is something we need to be worried about... honesty even yours at 39c is not that hot 102 F which for a computer is whatever... but I thought this chip was supposed to run cooler and everything being the new architecture.
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
gafalas said:
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
Click to expand...
Click to collapse
You are right on point. I have seen it drop (I believe to 1180) when running a bunch of benchmarks. The manufacturer sets the heat threshold at a very safe level. Kernel devs are usually able to safely bump that up another 10 to 15 degrees. I am one of the lucky ones that got the variant 3 of the international One X. Variant 3 was the strongest version and I ran all 4 cores at 1600 with 51 minimum. Faux usually figures out how to uncap and raise the throttle temperature... but he's on a N4. I am going to keep an eye on the kernel threads there and see how far they push things. Chainfire's "PerfMod" app is perfect to watch this while running different apps
Sent from my LG-E970 using Xparent ICS Tapatalk 2
Related
I would like to stress test and I don't really know anything about it.
I am using SetCPU and went into settings and selected Stress Test. Then I got a box saying: "Stress test running... Device maybe unresponsive. Press back to end."
Does this mean it's unresponsive to the stress test or that it's unresponsive to other actions? Because if I hit back right away it's like nothing happened, but when I waited a little bit and hit back I got a test result.
So if it is actually running the test, how long should I let it run? Does it stop on its own?
What app does anyone recommend for stress testing?
I'm assuming you're testing an overclock? If so, it's pretty much the same if you were to run say prime95 on your computer. Set cpu will probably be running your cpu at max load. If it is unstable your phone will lock up or reboot, if one of those occur your overclock is unstable. Also what clock speed are you using?
I haven't actually OCd this kernel yet, it's at 384/1512 On Demand. I've been trying to figure out settings for better battery life but that hasn't happened so now I thought I'd try out OC and see how it works on my set up. Was just checking out the test to see how it works.
If you're still on GB a lot of people have random reboots once a day or so if you do 1.8 ghz. Seems our chipset can't handle anything over at 1.7 atm, this could be incorrect though. Could just be some software issue that hopefully be resolved once kernel source is released for ICS. Honestly if you're having issues with battery life just go for the extended. I'm on ICS and run 1.7 all day and have pretty heavy usage. I used my phone quite a bit in this 24 hour period as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it plausible to get the Rezound OC'd to 2.0ghz you think?
I remember on my OG Droid almost everyone could OC'd to 1.0ghz, but once you got past that it was hit or miss. Some people could do 1.25ghz, other people couldn't do above 1.0ghz so they'd get random rebooting issues. I can't remember what determined this, but it was some hardware that was in the phone that was slightly different amongst each other.
Meticode said:
Is it plausible to get the Rezound OC'd to 2.0ghz you think?
I remember on my OG Droid almost everyone could OC'd to 1.0ghz, but once you got past that it was hit or miss. Some people could do 1.25ghz, other people couldn't do above 1.0ghz so they'd get random rebooting issues. I can't remember what determined this, but it was some hardware that was in the phone that was slightly different amongst each other.
Click to expand...
Click to collapse
They say the max you can clock this chipset is 1.99 ghz. But a lot of people are having issues w/ 1.8ghz on GB roms, random daily reboots. Could just be hardware limitation, or the kernel code. Most are stable at 1.7 ish.
So how long are you supposed to run the stress test? Does it stop on its own? Is there a better app to use for it?
feralicious said:
So how long are you supposed to run the stress test? Does it stop on its own? Is there a better app to use for it?
Click to expand...
Click to collapse
StabilityTest by Intostudios is also a pretty decent app. I've ran it for as much as 2-3 hours, I'm sure there have been some that have run it as much as 24. I know I like to run Prime95 on my home PC for 24 hours to ensure any OC is stable. Few hours, 24 hours.. The choice is yours. I'm pretty sure any unstable oc or underclocking will cause a random reboot within 10-15 minutes w/ that app.
Has anyone else found the device gets really hot randomly without doing anything task intensive?
My latest battery temp went up to 45 degrees Celsius (113 fahrenheit).
Please shed any light on the matter!
After 15 mins of Dead Space, my SGS3 feels a little bit warmer than normal.
Also the same on HSPA+ and heavy browsing.
But 45 is way better than the 63 of HOX, maybe it's normal, maybe not.
Do some more testing, what app did you use to see the temperature?
I can test my phone and come back to this thread with results.
I have the Problem to but the temprature was up to 54 °C. I dont know why. The Phose is going hot only by surfing. The first days it be cold. After 5 Days it will be war/hot. The battery is going fast down too. The Benchmarks are bad too, antutu e.g. 3 to 5 thousand points. After Buying 12 thousand. Energy-Safemode is deactivated. The CPU Frequency is up to 800 Mhz not 1.4 Ghz.
And today....all is going fine. Its cold, the Benchmarks are high and the CPU ist 1.4 Ghz......
Very curious
and yes, my english is bad
What ROM are you on? Do you have any weird apps that run in the background?
Definitely sounds like overheating problems. Phone gets too hot, CPU scales down, standard procedure... Never happened to me.
Load the newest ROM for your area,do a full wipe, don't install many apps, check it for a day or two.
If the same happens, take it back for replacement.
pinguin1987 said:
I have the Problem to but the temprature was up to 54 °C. I dont know why. The Phose is going hot only by surfing. The first days it be cold. After 5 Days it will be war/hot. The battery is going fast down too. The Benchmarks are bad too, antutu e.g. 3 to 5 thousand points. After Buying 12 thousand. Energy-Safemode is deactivated. The CPU Frequency is up to 800 Mhz not 1.4 Ghz.
And today....all is going fine. Its cold, the Benchmarks are high and the CPU ist 1.4 Ghz......
Very curious
and yes, my english is bad
Click to expand...
Click to collapse
Thanks, i look the next days. if the phone going hot i make a full reset. The ROM is the original Rom from Samsung. Nothing changed.
On bad reception any sync app can cause overhit.
Dude we got 4 cores !
What do you expect
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks
Hi all,
Thanks for the the replies.
The ROM - is the the original I haven't rooted (I hope that's what you mean...I'm a noob at this)
I have got rid of that horrible touchwiz with apex launcher but that about the only thing that I've done (apart from install a few apps)
As the last guy said "we've got 4 cores dude" haha.
Just seems to get pretty hot had it up to 47 degree. Toasty! but haven't noticed anything drastically wrong with the battery life.
Piece out all. Thanks for all the help!
I don't seem to suffer from this but having said that I haven't used the phone to watch a movie yet or anything like that so o don't know.
Battery going down is only normal when its hot.
sent with SGS3
Well, if it gets hot while on stand-by or out of the blue, take it back.
My phone idles at 27-33c with normal use. After 15mins of NOVA 3 gameplay it goes up to 45c and feels a bit warm.
If your phone gets hot with 3G and browsing or recording video and such, 47c is totally normal, especially if you consider 4 cores and no cooling whatsoever. 47c is nowhere near to toasty though
I hope I helped you.
pow001 said:
Hi all,
Thanks for the the replies.
The ROM - is the the original I haven't rooted (I hope that's what you mean...I'm a noob at this)
I have got rid of that horrible touchwiz with apex launcher but that about the only thing that I've done (apart from install a few apps)
As the last guy said "we've got 4 cores dude" haha.
Just seems to get pretty hot had it up to 47 degree. Toasty! but haven't noticed anything drastically wrong with the battery life.
Piece out all. Thanks for all the help!
Click to expand...
Click to collapse
Wha the **** is up with that? I'm actually raging right now.
I play any game for 5 minutes or so, and when I quit it the phone has it's performance basically halved. It goes like this: Run Quadrant Standard -> get 3300 points -> play 3D game for 5 minutes -> game slows down noticeably -> close game ->run quadrant again -> get a score of 1600.
What's up with this crap? It's so insanely aggravating. I restored my phone from PCC and it still happens. The only way to get it running decently again after it starts crawling is to reboot it.
Seriously, I've had it with this piece of crap of a phone. I think this **** crossed the line, I'm selling it.
Hrm i think it's when ur phone get hot and decrease it max cpu frequency to about 800mhz! So try some custom rom or kernels might fix the problem!
Sent from my LT26i using xda premium
I've experienced the same issue! U once it's laggy try to check out ur cpu frequency!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what i get!
Sent from my LT26i using xda premium
I don't have that visible underclocking under CPU Master. Mine always says 1500 as max frequency. It looks like you set it to 800 manually.
But anyway, I think it's related to overheating because I noticed that if I let it sit for a while after running a game performance goes up again.
Anyway, I don't give a crap about what's causing it. A phone should NOT overheat from normal use. Ok, it's summer and it's hot, but seriously, I've had it with this phone.
I can't deal with this. I'll just sell it and go back to my trusty ol' Xperia Ray on Gingerbread.
MarkMRL said:
I don't have that visible underclocking under CPU Master. Mine always says 1500 as max frequency. It looks like you set it to 800 manually.
But anyway, I think it's related to overheating because I noticed that if I let it sit for a while after running a game performance goes up again.
Anyway, I don't give a crap about what's causing it. A phone should NOT overheat from normal use. Ok, it's summer and it's hot, but seriously, I've had it with this phone.
I can't deal with this. I'll just sell it and go back to my trusty ol' Xperia Ray on Gingerbread.
Click to expand...
Click to collapse
All high power phones have problems with overheating and becoming slow. Install a custom kernel and undervolt it, that should help. Also using a custom rom and kernel has reduced my heat problem a lot.
Of course your xperia ray doesn't have issues because it is slow. A dual core in a phone is going to heat up.
I have played shadowgun for 30 minutes without any slowdown.
MarkMRL said:
I don't have that visible underclocking under CPU Master. Mine always says 1500 as max frequency. It looks like you set it to 800 manually.
But anyway, I think it's related to overheating because I noticed that if I let it sit for a while after running a game performance goes up again.
Anyway, I don't give a crap about what's causing it. A phone should NOT overheat from normal use. Ok, it's summer and it's hot, but seriously, I've had it with this phone.
I can't deal with this. I'll just sell it and go back to my trusty ol' Xperia Ray on Gingerbread.
Click to expand...
Click to collapse
No i didn't i even overclocked! I'm not that noob to decreased the cpu frquency! It's decreased automatically! I'm looking for the cause of this too!
Sent from my LT26i using xda premium
Now i realised that the decreased of maximum cpu frequency is only happen when i play temple run brave! What's wrong with the app or the phone!
Sent from my LT26i using xda premium
i m using cm7 stable rom on my p500........with overclocking min 480/max729 ,governor-performance,scheduler-cfg.....
is there any effect of overclocking on battery life or performance on mobile?
more performance but lower battery life.
Mmm ok I have some questions, what is a normal overclock to improve battery life but without sacrificing a lot of performance.
And the other way around, an overclock that improves some performance without sacrificing too much battery.
What are the "optimal" values of an overclock (Without making the phone unstable)
I would just overclock until you get phone instability or you go as far as you can for the current kernel (I'm on AOKP 4.0.4 and it's 787 max which is what I'm at).
Battery life doesn't get affected that much because it's mostly drain when playing games where it ramps up to the max clock speed, at which point you're draining a lot of battery anyways.
Koraboros said:
I would just overclock until you get phone instability or you go as far as you can for the current kernel (I'm on AOKP 4.0.4 and it's 787 max which is what I'm at).
Battery life doesn't get affected that much because it's mostly drain when playing games where it ramps up to the max clock speed, at which point you're draining a lot of battery anyways.
Click to expand...
Click to collapse
Thanks, I also have AOKP so I'm going to work around it a bit, how can I test stability?
Go to Rom Control.. Performance.
Remember to UNCHECK " Set at boot" option.. so that if anything happens.. it can return to default value after a reboot.
If random reboots or white screen appears or phone hangs.. its not stable.
I'll rephrase my question, what type of test can I do to ensure I have a stable overclock. I don't want to find my phone turned off out of the blue and maybe missed an alarm or what not. Thanks anyhow for the tips
Just do general usage. If it works fine for 2 weeks at a specific clock, it's likely to be okay.
kibaruk said:
I'll rephrase my question, what type of test can I do to ensure I have a stable overclock. I don't want to find my phone turned off out of the blue and maybe missed an alarm or what not. Thanks anyhow for the tips
Click to expand...
Click to collapse
You will only know by using. The CPU manufacturers label a chip ancertain speed because it fails a test at the next level. That means that some chips can handle faster than others. They are guaranteed to be stable at the rated speed.
There is no formula
Sent from my LG-P500 using xda app-developers app
Thank you everyone who helped me in here
Overclocking kills lifespan of processor...
Dwars said:
Overclocking kills lifespan of processor...
Click to expand...
Click to collapse
Not necessarily. Voltage and heat are usually what kills electrical components. Since our device can't change voltage for the CPU, that point is irrelevant. However, heat is a factor but AFAIK the heat from overclocking doesn't increase that much for this device, unlike something like PC CPUs so that's fine as well.
Koraboros said:
Not necessarily. Voltage and heat are usually what kills electrical components. Since our device can't change voltage for the CPU, that point is irrelevant. However, heat is a factor but AFAIK the heat from overclocking doesn't increase that much for this device, unlike something like PC CPUs so that's fine as well.
Click to expand...
Click to collapse
No, you can damage it. If it heats up, then:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I open an app like the play store or chrome in the screenshots and get 100% load for 10 seconds or more. I noticed this behavior on different roms and kernels/governors.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's only 51% maxed out would be BOTH CPUs at 100% so really your concern is?
Sent from my Nexus 10 using XDA Premium HD app
Because it's a waste of energy.
reborn90, sorry for the off topic question but what are those system widgets (CPU, Disk I/O .. etc)?
Perfmon its the app
Sent from my Nexus 10 using xda app-developers app
reborn90 said:
Because it's a waste of energy.
Click to expand...
Click to collapse
Without accounting for exactly what the CPU is doing you really can't make this assertion.
Me neither, that's why I ask. It just looks buggy when the cpu starts scaling to max frequency (for a long time) because a new app is started.
reborn90 said:
Me neither, that's why I ask. It just looks buggy when the cpu starts scaling to max frequency (for a long time) because a new app is started.
Click to expand...
Click to collapse
Try a different governor, or maybe increase/decrease the refresh rate of your resource monitor? (BTW, scaling to max speed on load is actually better for battery life in some cases, as the task energy required can be sometimes be lower when you burn more juice but complete a given task in a shorter period of time).
The cpu (core) load shoud be independent from the governor, apart from the current frequency of course. I still have the feeling that it is some kind of "phantom load" but actually I have no idea. I switched from an ASOP rom to CM10.1 and I haven't seen the problem yet. :fingers-crossed:
reborn90 said:
The cpu (core) load shoud be independent from the governor, apart from the current frequency of course.
Click to expand...
Click to collapse
Its true that load wouldnt be caused by the governor, but the governor you run does affect how load is handled and whether there averages more or less load on the system. By running at a higher speed the system load is decreased because the processor is going through its tasks much faster. If the governor is keeping the speed lower while doing a task then the system load will be much higher because the CPU cant complete things as fast. So load and governor are linked together, but it is the tasks being run that cause any of the load in the first place.
Since the problem hasnt come back since switching to CM10.1 it was probably something in the system that got bugged and caused this behavior.
Yes I agree, but in this particular case I have maximal frequency and core load. It's much better now with cm10.1. :good: