Related
I installed the webtop over hdmi mod on my Atrix and while testing it out, it got very warm in my hand. I opened the setcpu app and noticed that while overclocked to 1.3GHz, the CPU was running at 75C! I lowered it back down to the stock 1GHz and the temp slowly went down and settled at 63C.
It seems that while in webtop mode, the CPU is taxed at 100% all the time so I'm wondering if it's safe to stay overclocked when using webtop.
Everyone has different opinions of what is too hot around here.
IMO the cooler the better. IMI No Atrix should have a temp above 60c and I'm not even comfortable with above 50c either...
Sent from my MB860 using xda premium
I have experienced the same problem and worried that something may fry.... I have had mine overclocked at 1.45 using debian linux and all of a suddent he phone freezes and restarts.... Since it did it to me the second time I have kept my phone at 1Ghz... I am new at this so please don't beat me up too bad for being a noob... Just want to see if maybe undervolting it a little might help or hurt it?
Thanks in advance
Here are some tips I can offer
1.Try re-flashing your custom kernel and see if that fixes the web-top thing and over heating
Whenever the phone is plugged to the web-top it will naturally overheat so it's kinda expected remember now it's gotta work harder since its displaying on lap-dock or TV,but if you can cook an egg on it it might be too hot...lol
2.Set profile for temperature on setcpu so this way once you reach for example 100F your phone will clock down a little and so it might help the heat issue.You can set even more than one temp profile so this way when it reaches 96 it goes down a little then when it reaches 100 it will clock down a little more and such.
3.If that doesn't help,which in my situation it did.Flash a different kernel mayb it's just the one you're using that is causing funny stuff to happen.
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
I tried reflashing the kernel but it didn't change anything. I'm using Faux's 1.3GHz overclock kernel for Gingerbread (2.6.32.9). Is there something else I should be using?
sk8trix said:
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
Click to expand...
Click to collapse
Do what sktrix said in rest of his post.
I use the stopgap 1.0GHz kernel, and UV does lower temperatures. I would definitely try UV'ing a wee bit. You don't need to go crazy. I am using the following with great results for both temp and battery life:
-50
-50
-75
-75
-75
-100
-100
My setcpu profile clocks it back if I reach 60C, (I idle in the low to mid 30's). Under heavy load I reach around 52C max which is quite acceptable.
Now, granted I am not using Webtop, but the end result for UV should be the same. Lower temps and better battery life. You may also want to try just using 1.0GHz when on Webtop. The phone has more than enough power at this clock speed.
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
I know I'm straying from my correct forums here, however I have an LG Optimus 2X which like the Atrix, is a Tegra 2 CPU.
Our phones get VERY hot, I have had my CPU up to 86C before I decided to back off the stress test. CPUs are very good at handling high temperatures, and IMO you will see no ill effects from doing so, I am unsure of whether or not the Tegra 2 has thermal throttling/shut down, but in my experience they should be fine to around 80C.
The only issue I can forsee is the battery, batteries HATE high temperatures and it is awful for their life span, this is why your laptop batteries turn to crap after 1-2 years, even if low charge cycles, because they are always hot.
I would not be concerned about anything in the 70C realm, at all.
Alcapone263 said:
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
g2tegg said:
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
Click to expand...
Click to collapse
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
ericemir said:
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
Click to expand...
Click to collapse
It will still hang at 1.3ghz, though it's a known bug. I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick. Right now, the software that's out there is optimized to run on existing hardware w/o overclocks. I've run Shadowgun at 1.45ghz and didn't see any difference over the 1.0 enhanced.
Now, if we were trying to run games that were coded specifically or faster-paced chipsets then we'd need overclocking to catch up much like you would in the PC arena. That, however, is not happening in the cell phone market just yet.
treehumper said:
I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick.
Click to expand...
Click to collapse
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
cjrhoades said:
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
Bump.
Anyone?
cjrhoades said:
Bump.
Anyone?
Click to expand...
Click to collapse
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
CaelanT said:
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
Click to expand...
Click to collapse
I see... guess that explains why the phone doesn't really feel any faster when it's overclocked. I'll flash the 1GHz kernel then.
Thanks for the info.
Not sure if this is the same with phones but normally a CPU should stay at 40C idle and 50C load. Maximum would be 60C while benching or something.
If it goes above that I would definitely underclock/undervolt.
cjrhoades said:
what's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
also has other fixes besides overclocking you can go read them in the kernel threads
Just curious is most people who root/use custom ROMs overclock, and if so, what settings do you typically use in SetCPU?
I'm using a S2, rooted with latest Unnamed ROM and find myself contemplating if I should make any changes with SetCPU. Lots of options, and Unnamed has all the different governor options, etc. just really looking for some best practices that people who overclock often.
Would appreciate seeing what you consider to be stable overclock options that give a good boost without causing excessive heat/stability issues.
I'm coming at SetCPU with limited experience so I do appreciate any tips that might see rudimentary, or if there are better resources that teach about this I'd appreciate any links as would like to get a better technical understanding of all this. Thanks in advance.
I use No Frills CPU, and I just set it to 1.6 max/ondemand. Absolutely no heat issues or stability issues, so I just stuck with it. Battery life is good.
most maybe but only by a little bit. a good number of people underclock and undervolt their devices to try and get better battery life. to be honest, the newer phones dont need overclocking to handle the current apps and stuff. the older phones like the nexus one and older need overclocking tho. i leave my gs2 stock. what we really need is dual core support before OC becomes worth it on my phone. ymmv
I have never overclocked mine, phone runs smooth as butter at 1.2 so I don't see the need to go farther. Plus I like my battery lasting more than 24 hours...
I overclock my s2. im running unamed 1.3.0. I like run different speeds at different at different battery percents. 1.6 till 75% 1.4 till 50% 1.2 till 25% 1000 till 15% 800mhz till dead. i had some problems with 1.4 ghz but i tweeked the voltage and that did solved my problem. I'm at 50% battery with normal usage. display 1hr 25mn phone calls for 47min and android os for 56min. my phone doesn't get any hotter then it did before i overclocked. I just did it to say i did. It will prolly help a little unless you like emulators then it will help alot. i have to overclock my iconia a500 to 1.6 if i want to play n64 games.
I'm on UnNamed 1.3.1 with the latest entropy dd kernel and am very happy with the stock CPU speed
Sent from my Samsung GT-I9100
Hello! i am in the process of overclocking my thunderbolt in order to get better performance with the eternity rom, and i was wondering what you guys oc your phones to? and if you do, what program/setting do you use to do so? (i plan to use a script in init after have found suitable settings)
I, personally, find it pointless to OC the Thunderbolt. The phone is fast and smooth enough for me on the stock speed, plus the battery life is bad enough without adding more strain to it.
However, if you insist on OC'ing, 1.2GHz is a safe bet. Some people can get to 1.4GHz, but then you run into freezing and random reboots. Also remember that individual phones handle overclocking differently. Where one phone can run perfect at 1.4GHz, another might freeze instantly when going that high.
Good OC'ing programs include SetCPU, No Frills CPU, and ROM Toolbox.
I don't overclock. That being said i have OC'd my phone b4 i have had it up to 1.8 Ghz stable, but it doesnt seem to make anything run faster. I use the Thundershed version of CM7 and its super fast. I dont think it could get much faster. and without overclocking i get better battery life.
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
lacrosse1991 said:
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
Click to expand...
Click to collapse
Leankernel is tops. I use battsaver mode which is stock speed and undervolted. Smooth as butter on my phone.
Sent from my ADR6400L using xda premium
As by the title, I get a low score on CleanROM 3.7 based on ICS 4.0.3. My result is just 1700. I haven't found any benchmark result based on this rom but I know that stock should get at least 2400-2600.
Has anybody benchmarked on CleanROM?
Why does it matter? Bragging rights, or pissing contest?
Actually the score doesn't really matter but I've noticed a slowdown after flashing CleanROM.
Haven't noticed any lag at all.
Have you benchmarked quadrant? Also, the slowdown is more noticeable when scrolling menus and some heavy designed websites.
I don't know why people bother with Quadrant, it doesn't work correctly on dual-core phones anyway.
Actually don't really bother on it. But, as I said started to be doubtful of some lags compared to the stock rom and I used quadrant just to create an idea if this was really the case.
By the way. Ver 2.0 is optimized for multicore phones.
Quadrant is a terrible benchmark.
Use Antutu.
Tryied Antutu and got 3387. Checked a bit around and found that a score of 5000-6000 should be normal.
Ok, rerun antutu after restarting the phone and got around 6200. What really bothers me is that even after killing all task and running any benchmark, I notice that scores are usually noticeable lower than on a first run after restarting. And more important, the phone is slower. Seems like services are still running and using available resources.
I use Advanced Task Killer by the way.
AlbPCWar said:
I use Advanced Task Killer by the way.
Click to expand...
Click to collapse
Don't ever, ever, ever use task killers on anything past Froyo.
They harm the phone and do not do anything, it's all placebo that it does.
There's countless threads about it.
Delete it.
Done. Thank's for informing. Now I'm asking myself why they are still some of the most downloaded apps on the market when 90% of Android are on GB and up.
Because a friend of friend told them long ago to get it.
Sent from my ADR6425LVW using xda premium
Imo the only benches I care about are GPU benches. Quadrant is utter garbage, remove it and do yourself a favor. Nenamark 1 / Nenamark 2 for GPU benching is nice.
well, scrosler puts fastboot in his rom, which kills all running tasks that are not core.
Myself, I'll occasional open System panel app if the phone is acting up. Very occasionally.
On cleanrom I haven't noticed any slowdows.
I have sammy kernel installed, i tried all the included governors and schedulers, all of them OC'd at 1.9Ghz and i still don't get better Vellamo or GL benchmark results. Stock unrooted, i was able to get 2350 in vellamo, now OC'd to 1.9 i barely get 2100.
Has anybody else not seen any improvement while OCing and actually felt a decrease in performance??
not all CPUs are the same, yours might not be able to handle 1.9 try bumping it down a little. There are also a lot of variables in these crap if you ask me benchmark apps, just because you OC doesn't mean the scores will always go up. Just use it and see if it feels smoother to you or if it's sluggish
Well i'm able to go down to 1ghz and still get a very smooth experience...even the vellamo score was around 1800 for a 1/3 of the cpu
I'm really satisfied with the S4 Snapdragon, it barely heats up
Benchmarks mean nothing. My old atrix had better benchmarks than the gs3 (both stock) and that phone is half as fast as this one. Go by feel and day to day use. Not buy some random numbers that appear on your screen.
If it make you feel better I officially give your phone a bench mark of 999999!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2