Related
So I've gotten anywhere between 2.5 to 5.1 MFLOPS using various ROMS and have yet to be able to notice something incredibly different.
710...768...806 - What does it matter? What program other than Linpack shows a sizable difference? Sure, maybe things open quicker? What am I missing here?
I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS.
MFLOPS mean jack when there is little way to observe the difference.
Carreno43 said:
So I've gotten anywhere between 2.5 to 5.1 MFLOPS using various ROMS and have yet to be able to notice something incredibly different.
710...768...806 - What does it matter? What program other than Linpack shows a sizable difference? Sure, maybe things open quicker? What am I missing here?
I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS.
MFLOPS mean jack when there is little way to observe the difference.
Click to expand...
Click to collapse
Linpack MFLOPS - measures the floating point performance of your phone.
710...768...806 - refers to CPU frequencies
increasing the CPU frequency should equate to better general-case performance, including things opening quicker as you mention, but also other types of general snappiness like moving between screens and so forth.
"I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS." - This may have less to do with the performance of your phone and more to do with the emulator itself. Emulation is a surprisingly CPU intensive operation, especially if the emulater isn't well written. Rather than looking a ton into overclocking and JIT, etc, maybe you ought to look for a better piece of software.
Yea,
I've tested most emulators. Wish there was an Atari emulator!
Thanks for the response.
Carreno43 said:
Yea,
I've tested most emulators. Wish there was an Atari emulator!
Thanks for the response.
Click to expand...
Click to collapse
I have run roms with 5.1 MFLOPS and now am running a rom that gets 3. I can honestly say I see no difference.
Spencer_Moore said:
I have run roms with 5.1 MFLOPS and now am running a rom that gets 3. I can honestly say I see no difference.
Click to expand...
Click to collapse
I can see a difference... in battery life! Lolz
g00gl3 said:
I can see a difference... in battery life! Lolz
Click to expand...
Click to collapse
Haha Awesome
it looks like to me that everyone is look at the wrong things.
for example:
I am running a Tom that is getting on a average of 4.9 mflops.
I get smoother screen changes....
streaming videos online is so much faster compared to a 3.0 mflop rom. ...
tubetube and other....... websites.
to me everything I do is faster...
I.don't play game on my phone so I don't know how that is.... but everythng else I do is very much faster.
I love high mflop roms...
I have notice about mflops is that it matters about the kernal that u use.
Isn't it true that the MSM7201 in our phones is already overclocked to get to 528mhz as it is? I see a lot of different places saying Qualcomm chips in general are just not worth overclocking... and since our chip is factory overclocked to begin with... just seems like we're pushing the already-pushed here. But the way this board goes crazy for overclocking... it's contradictory. I don't know what to think, cause I've run Linpack myself and gotten ~4.9 with JIT + OC versus ~2.5 without... but I'm with the OP on this one... only difference I'm seeing is my battery draining faster and my phone getting physically hotter.
xatch said:
Isn't it true that the MSM7201 in our phones is already overclocked to get to 528mhz as it is? I see a lot of different places saying Qualcomm chips in general are just not worth overclocking... and since our chip is factory overclocked to begin with... just seems like we're pushing the already-pushed here. But the way this board goes crazy for overclocking... it's contradictory. I don't know what to think, cause I've run Linpack myself and gotten ~4.9 with JIT + OC versus ~2.5 without... but I'm with the OP on this one... only difference I'm seeing is my battery draining faster and my phone getting physically hotter.
Click to expand...
Click to collapse
I have OC and JIT and getting about 5.1 mflops and haven't had worse battery life or a hotter phone. It could be the battery I'm using but meh (got a replacement one that's 2000 mAh) but I got worse battery life on leak 2.1 than with the rom I'm using now that has OC, JIT, LWP, etc. I can go about 8 hours with heavy texting, moderate internet usage and my lwp's running and it only goes to about 65%
so OC and Jit don't make that big of a difference in gameplay?
Sent from my Eris using the XDA mobile application powered by Tapatalk
What the OP and all the respondents are noting is frankly quite typical of what happens when performance tuning focuses on a single benchmark: the results obtained are essentially meaningless for different kinds of activities on the same device.
That's because there's a whole chain of dependencies that are specific to a given task, any number of which could become the rate-limiting factor; and a different task on the device will have a different set of dependencies and therefore different rate-limiting behaviors.
For instance, let's take writing to an SD card as an example: there's really no way that OC'ing will speed that up in a measurable way - because the CPU isn't the rate limiting factor.
That Linpack benchmark measures floating-point performance using a software library (as the Eris has no hardware FP capability). Most of the apps on the phone do very little FP work at all. But, it's not a bad test of CPU speed, because it performs no I/O. It also may not be very memory bandwidth intensive, either (if the problems it works on stays in the uP cache and there are few page faults).
OTOH, a game emulator needs to write to the graphics display (at a minimum) and possibly also do read I/O from flash.
Different task, different results. Sometimes things can be improved by hardware or firmware; sometimes the software itself needs to be improved.
bftb0
im sorry, but could you just answer in plain english
Sent from my Eris using the XDA mobile application powered by Tapatalk
TheSonicEmerald said:
im sorry, but could you just answer in plain english
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Lima beans bad.
Pork good.
Slow phone bad.
Fast phone good.
bftb0
Thanks for my laugh of the day on that one.
What I'm trying to get at is -
I should be able to play, at the basic level, Sonic or Mario - Without issues.
At the very least
I prefer roms over market games any day (Sonic, Mario, Zelda, DK-Country) and it cripples the phone, at least in my view, that I cannot enjoy the fruits of old games.
Although, I was able to find some old Atari games - which, thankfully, work without stuttering.
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
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
zetsumeikuro said:
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
Click to expand...
Click to collapse
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
zetsumeikuro said:
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
Click to expand...
Click to collapse
Benchmarks do have a some good uses... while comparing different phone models with benchmarks can be iffy, it can give an overall insight, (things like graphics capabilities with very GPU extensive games) but in the end user experience and daily use are the real judges.
Where benchmarks can be of the most use, is when comparing changes to the same phone model.
E.G. Comparing performance impacts of AOSP vs Sense, overclocking and under-clocking, and de-sensing/bloat removal.
When used for these reasons, you can get a really good feel for how changes are affecting your device overall. Even then, benchmarks are not the be all end all, and user experience is still important. As you may introduce lag or other performance issues that do not show up in benchmarks.
Which temp root method are you using? Mine isn't staying rooted long enough for me to justify using setCPU at all...
The new version and the one that comes with the newest clean tool stays until reboot.
Marine6680 said:
The new version and the one that comes with the newest clean tool stays until reboot.
Click to expand...
Click to collapse
Thx for the info, guess I must still be using the outdated method. I'll run the latest version of Scott's Clean tool and give it a shot.
Izeltokatl said:
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Click to expand...
Click to collapse
Please let us know what settings you use that work for you.
I generally stay temprooted unless I'm going to be away from a charger for a bit and need BT (since you can't turn BT back on after temproot). I wouldn't have SetCPU autostart on boot (since it won't ever be able to get root access immediately after boot).
Meanwhile, I also set it to conservative and will see what that accomplishes.
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
This kernel apparently does work with SetCPU. I've confirmed using other cpu monitoring apps that the clock speed changes are capped.
I own 7 android phones, and have been rooting, overclocking, undervolting each and every single one of them (well one I still cant get rooted). I know when the cpu is under clocked and when it is not. Been doing these tweaks for 4 years now. If you use a tool like System Panel, at stock settings you can see the max cpu around 1500 on our little bad boy. When it peaks out the clock speed is shown. When you under clock it, then check again it won't go beyond the max cpu set in my testing I put a ceiling at 918mhz. System Panel reported full CPU usage (100%) at clock speed 918mhz. Typically with stock kernels, your absolutely right, changes to SetCPU do nothing at all to the real cpu. Which is confirmed, when I reboot and dont have root, if I attempt to use SetCPU and make the changes, System Panel reports 1500mhz (roughly) at full load regardless of what I set it to in SetCPU. If I did this to any of my other phones with stock kernels, you are correct it makes no difference as SystemPanel reports the stock max setting.
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Grnlantern79 said:
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my rezound.
Izeltokatl said:
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Click to expand...
Click to collapse
Or I would say, "half the fun is messing with the phone and trying to get it to do things it should have always been allowed to do...." Just sayin'.
Are you using the profiles at all? Im interested to know what seems to be working out the best for you.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
douger1957 said:
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
Click to expand...
Click to collapse
Linpack and Quadrant are not reliable benchmarks. TBH I don't take any of the benchmarks seriously, they are more for entertainment for me. But to each their own right?
Yeah some of the benchmark apps are a bit unreliable to say the least...
If I use one, I try to use ones that Anandtech uses. I trust them to find the better benchmark tools.
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 cleared my cache and dalvik cash and when I rebooted the phone the screen had a sorta checkerboard pattern on it...it straightened up when I rebooted again What would cause that?
Have you been overclocking your GPU?
If so reset it to 533mhz and never OC it again. Sounds like textbook GPU overclock failure.
DaRkL3AD3R said:
Have you been overclocking your GPU?
If so reset it to 533mhz and never OC it again. Sounds like textbook GPU overclock failure.
Click to expand...
Click to collapse
Why would it just now do it? Is it bad for it?
blackbass595 said:
Why would it just now do it? Is it bad for it?
Click to expand...
Click to collapse
Generally speaking any artifacts that arise shouldn't be permanent. However damage from overvolting can occur. I didn't play around with the GPU clock settings in the custom kernel so I don't know how much they overvolt it, but that is sure to cause problems if it does, in time.
Artifacts caused by overclocking the GPU, like that checkerboard pattern you saw, are usually temporary. But if you see artifacts like that then it's a sure sign that your OC is failing and you should fall back a notch, or just go back to default clock speed period.
I have years experiencing overclocking graphics cards and processors alike on my PC. Pretty obvious what happened here.
Right on man thanks...I have run antutu so many times that I know what the graphics score is and I can tell ANYONE reading this that over clocking the GPU does not speed the phone up. I'm back at 533 and still hit this on pegasus governor. This is what i hit with the gpu set at 620 (or whatever the next step is) That was the only thing I had changed in GPU. So take dark leaders advice and slow it back down...
Thanks for sharing this guys, I was getting this when playing some games, especially with modern combat 4. Just flashed the 29.1 (from 28/5g) and am going to leave everything at default for now to see how it runs.
Edit: Would ya look at that.... played again on stock settings with Perseus 29.1 and it runs like a dream! Not a single glitch, lag, or even the slightest artifact! Sometimes less is more!
Sent from my unlocked & underclocked Galaxy Note 2
Yep no problem guys.
CPU overclocking can have tangible gains for phone use. But GPU is pretty tight setup from stock, and pushing it harder won't really improve much of anything. In fact I only recommend overclocking desktop grade GPU's for benchmarking only, as it's impact on real world performance is so minimal that it isn't worth the extra needed voltage and the possibility of artifacting that you get with it.
So yeah definitely enjoy the phone at 1.8Ghz CPU and leave the GPU alone
Yes this is info that needs to be out there ...steve's post is yet more proof of concept here. ... Just linked a guy on kernel page here cause he's oc-ing GPU to 800...wow.
This is very good info indeed. I am currently at one level higher in gpu and after reading this thread its going back to 533. Planning on keeping this phone for the long haul.
Sent from my SCH-I605 using xda app-developers app
DaRkL3AD3R said:
Have you been overclocking your GPU?
If so reset it to 533mhz and never OC it again. Sounds like textbook GPU overclock failure.
Click to expand...
Click to collapse
blackbass595 said:
I cleared my cache and dalvik cash and when I rebooted the phone the screen had a sorta checkerboard pattern on it...it straightened up when I rebooted again What would cause that?
Click to expand...
Click to collapse
I know exactly what you're talking about and it is not limited to your model Samsung. It happened on my Galaxy Tab as well.
Actually, this is normal, even if not overclocked. It happened to me after clearing the caches like you did and I thought it was locked up, cause it sat there for a while and I kept trying reboots, thinking I was hosed. But this is a natural phenomenon!
When this happens, do not reboot! Instead, just put it down, go make a sandwich and come back. It will be booted! (screen may have turned off by then, as it normally would after a while after booting)!
Then reboot again and it should come up normally!
DaRkL3AD3R said:
Yep no problem guys.
CPU overclocking can have tangible gains for phone use. But GPU is pretty tight setup from stock, and pushing it harder won't really improve much of anything. In fact I only recommend overclocking desktop grade GPU's for benchmarking only, as it's impact on real world performance is so minimal that it isn't worth the extra needed voltage and the possibility of artifacting that you get with it.
So yeah definitely enjoy the phone at 1.8Ghz CPU and leave the GPU alone
Click to expand...
Click to collapse
My dual GTX570 cards that have been over volted and overclocked beg to differ. Noticeable gains in many games after doing so. Not just in the benchmarks. That is com pairing areas of very noticeable frame drops to where the from drops were less severe and kept from stuttering.
I do agree that the GPU on our phone does not need to be overclocked.
Sent from my SCH-I605 using xda app-developers app
I use to mess with gpu overclocking on my GNex and it would always get that glitchy stuff on the screen when I played games. I just never touch it now.
I OC'd both on the GNex and now the beast and have had no trouble at all. Speed freak! :laugh:
nosympathy said:
My dual GTX570 cards that have been over volted and overclocked beg to differ. Noticeable gains in many games after doing so. Not just in the benchmarks. That is com pairing areas of very noticeable frame drops to where the from drops were less severe and kept from stuttering.
I do agree that the GPU on our phone does not need to be overclocked.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I agree that the GPU doesn't need to be overclocked, although I did overclock mine from 533 MHz to 800 MHz.
My comment about the "Colored checkerboard screen after clearing the Dalv chache", when it's botting up again immediately after doing that, was only in reference to the fact that that happens on some Samsung devices immediately after clearing that cache and it starts to boot up, regardless of whether the CPU, or GPU has been overclocked or not and it just sits there for a while and will seem like it has locked up.
In reality, if you just let it do its thing; just put it down and walk away, eventually, it will finish booting and it will be fine. Then, once your Home Screen has finally come up again, you just reboot it one more time and it will boot as it normally boots, without the funky looking screen.
I guess this screen glitch is just what happens when it's rebuilding that cache, which I would assume it does when it boots again and I assume that's probably why the boot takes so long after clearing that cache.
In other words, my point was simply that all is well and there is no need for any concern. It just looks like there is.
But hang in tight and about 3-5 minutes later, you will have your device back again!