Related
So I'd been using JIT on my Evil Eris ROM (and I'd used it with a few others) and I was getting scores of 5.1~ mflops. Here are some things I noticed.
While I had first enabled JIT it was glitch free. I can safely say at this point that any "speed increase" I'd noticed was likely placebo or at least admissible.
JIT is amazing, but it's amazing for Froyo. The way a JIT compiler works is that it precompiles information into code that is more easily read, causing slight lag to begin and increasing overall performance. The thing they had to do with froyo is optimize just about everything to stop the lag and to make JIT worthwhile.
The other reason is that despite removing sense and eventually using the Universal JIT and basically doing everything to make it stable JIT began to show problems. It was absolutely stable for a very long time but if I left my phone on for a few days or I started installing new programs/ a new launcher it would get glitchy and laggy. This likely goes back to what I said about JIT really being much better for Froyo. It came to the point that I felt slower than before I rooted.
Now that I'm not on JIT I can also overclock higher. Before I was limited to 768mhz and if I went over it was an instant crash. Now with JIT removed I'm up to 787, I can do 806 but it only lasts a few minutes before it freezes up but it's proof to the concept that I can overclock much higher. I get consistently 3.4~ mflops.
I do realize that I while on JIT I got a large increase in mflops but in my experience I am performing better without it. I think that when Froyo ROM's come out JIT will be much better implemented.
tl;dr: JIT ended up causing lag, I can overclock higher without it, I'm just as fast/faster without it.
note: For something like a game JIT may help you much more than just scrolling around since the game will be precompiled and then run more smoothly but in my experience (with Zenonia mostly) there was no improvement and occasionally I would in fact lag more.
Just thought I should say this to everyone.
Kind a sounds like steroids, ya you get muscle and look cool but there are side effects
Yeah and JIT was made for Froyo, not for the other ones. Froyo was heavily optimized, they spent a ton of time just making everything work as well as possible so that the JIT wouldn't actually be detrimental. So while JIT does increase MFLOPS and performance it can cause a lot of bugs and slow downs because it's trying to compile information that isn't optimized for it.
Hm. I think I'll try disabling JIT for a while too. I might prefer the quicker load time over any supposed increase in performance. I haven't had much buggy behavior, but I have had some restarts and wonder if they're caused by JIT or just overclocking in general.
I've found overclocking surprisingly stable without JIT. It's incredible that I can overclock to 806mhz now with glitches and 787 is absolutely stable...
Looking back I realize now that JIT had slowly degraded, I started off overclocking without it to 787 and as I turned it on it began to get very glitchy with 787, eventually freezing immediately with it. I wouldn't be surprised if the restarts you're having are due to JIT in combination with overclocking.
good post +1.
the devs don't say anything about this in their threads, thats if they even know it or have experienced it themselves so i'm not blaming anyone.
good to know so i can at least eval it for myself. thanks.
I think JIT might have been interfering with my Swype. Maybe it's doing too much "just in time" compiling and not enough "ahead of time" compiling. But anyway, yesterday I switched back and forth several times between using JIT and not using JIT, but didn't change anything else, and I definitely noticed that Swype was more responsive without JIT. With JIT enabled, I kept having to retype things because my tracing path would skip over parts; it was choppy. Without JIT it's smooth as silk and therefore accurate again.
I think a lot of the problem is that apps also aren't made to use JIT yet, all of the developers made apps for non-JIT phones first... you see a LOT of problems in phones that have background apps (setcpu, autokillers, etc) when they have JIT enabled. I think anyone who read up on JIT when it was announced will see mentions of the google dev's saying "We really really streamlined the phone to make use of the JIT".... obviously they're remarking that JIT without streamlining and "light" OS is a bit of a waste. JIT on my Froyo ROM (CM6) is very much more stable. If anyone's interested I did some benchmarks for JIT here:
http://forum.xda-developers.com/showthread.php?t=726038
Found this in the Hero forums, and it obviously applies to the Eris as well:
illogic6 said:
http://forum.cyanogenmod.com/topic/880-jit-wont-make-your-phone-super-fast/page__p__7910?#entry7910
Notice this portion of the post: "CPU intensive tasks get faster, but at the cost of RAM."
The way Darchstar explains it is that our phones cannot sacrifice that RAM once our phones have been bogged down with installed apps. He doesn't plan to include JIT by default when CM 6 goes final for HeroC and that's why.
Click to expand...
Click to collapse
Yes well you can decrease or increase the amount of RAM that JIT will use (heap size) and increase stability or decrease it. I understand why it's default off, it makes sense especially since a lot of programs aren't made to use it *cough pandora cough*
I'm running Cyanogenmod 6 froyo, did you test the effects of turning on and off JIT on this ROM?
Yes, like I said JIT was literally made for Froyo ROMs, and you can quite clearly see that when you hear the devs who created it talk about it in google conferences and such, they had to do a lot to get JIT to work well without creating huge slowdown. Compilers are almost ALWAYS a bad idea because of their nature and because if information isn't made for the compiler it ends up doing more harm than good.
Froyo is streamlined to work with JIT without causing slowdown so I would highly recommend using the JIT compiler with Froyo.
Hungry Man said:
Yes, like I said JIT was literally made for Froyo ROMs, and you can quite clearly see that when you hear the devs who created it talk about it in google conferences and such, they had to do a lot to get JIT to work well without creating huge slowdown. Compilers are almost ALWAYS a bad idea because of their nature and because if information isn't made for the compiler it ends up doing more harm than good.
Froyo is streamlined to work with JIT without causing slowdown so I would highly recommend using the JIT compiler with Froyo.
Click to expand...
Click to collapse
What about the Compcahe? Idk what it even does ahah
I turned JIT and surface dithering off. Phone runs smooth and no force closes.
surgeon0214 said:
What about the Compcahe? Idk what it even does ahah
Click to expand...
Click to collapse
Compcache can speed some things up. I enabled it on a SenseUI ROM a while ago and had TERRIBLE, crashing results until I turned it off, at random.
I can confirm that JIT's make Swype crash sometimes. I can do a 100 fast-swype word experiment (which, I do a lot of 'texting', so this experiment happens every day), on days I have JIT on, Swype randomly disappears. (it is set to restart itself after 5.0 seconds, so don't worry). With JIT off, it only does its normal random crashing (when I accidentally hit the Swype key while it's thinking of what words I just swyped, for example -- just the known crash bugs).
JIT day was yesterday, for example (I'm experimenting with JITs because of this thread) - and Swype crashed more than 10 times (I stopped counting by the time I was at the bar for two hours, -- don't drink and swype!)
Non-JIT day was today, and Swype has not crashed 1 time (despite writing a few very long emails in a passenger seat and some serious texting).
Monday is a JIT day, and I'm pretty confident based on my findings, that these have a huge impact on Swype.
I'm just using SenseUI for the weekend (for reliability/etc, because I'm 'On Call' for work), but if my findings prove my theory WRONG, I'll edit this post and note that.
But in general, yes, I agree, JITs mess with Swype. Not to a point of usability, but to a point that, the late person might think Swype is unreliable (unknowingly).
Compcache is your processor compressing the information that is stored in your RAM to increase the total amount of RAM that you can use per program. This can increase performance by letting your programs use more RAM but it can also decrease performance by increasing the time that the CPU has to work on compression. For the Eris I don't suggest Compcache unless you're overclocking to at least 710mhz and if you're on a Froyo ROM I don't suggest it at all since you should have plenty of RAM already.
What VM Heap Size are you using pkopalek? Smaller heap sizes are more unstable, you may find swype is more stable at 24m if you're at 12 or 16. 24m is the point where sense becomes stable (sorta) with JIT.
Hey all,
I come from an extensive background in OC'ing my own systems, pushing them to the extreme for noticeable performance increases. The one thing I know though, is that it does add wear and tear on the components, and shortens their lifespan. Is overclocking the Vibrant really worth it? I'm not sure if, with a ROM like Axura 2.2.5.7 which is blazing fast already, an extra 100 or 200 mHz is really worth the risk/performance.
What do you all say?
howetechnical said:
Hey all,
I come from an extensive background in OC'ing my own systems, pushing them to the extreme for noticeable performance increases. The one thing I know though, is that it does add wear and tear on the components, and shortens their lifespan. Is overclocking the Vibrant really worth it? I'm not sure if, with a ROM like Axura 2.2.5.7 which is blazing fast already, an extra 100 or 200 mHz is really worth the risk/performance.
What do you all say?
Click to expand...
Click to collapse
the only reason i OC is basically just so i can tell myself that i am OCing. If that makes ANY sense. its basically just my phone OCD.
to answer your question, even though you kind of already answered it yourself: the only reason you would actually NEED to OC is if you game a lot on your phone, if you do a lot of multitasking, or if you have a lot of data transfering going on (which i do). other than that, our processor is pretty powerful, and can handle 95% of what is thrown at it.
With that said, since youve indicated that you are satisifed with your phones performance, i would say the only thing you should definately do is install a lagfix (if you havnt already). if you dont need to OC, do your battery/hardware a favor, and dont.....unless you have phone OCD like myself.
PS - not to ramble on, but there was actually a 2-day period where i actually wasnt OCed and i didnt know it (i guess my app reset itself or something). i remember saying to myself during that time that my phone phone seemed a little laggy and much slower than usual....then once i discovered that my OC wasnt applied, it made sense. but keep in mind, i have my phone doing a lotttttt of things constantly, so OCing may not have the effect on lighter users that it does on myself. pretty crazy what a .2 ghz difference makes
Like above stated, OC is only needed if you do some intensive task on your phone. In addition, most of the Overclocking Kernels are targeted at a broad audience, what I meant by that is the developer bumps up the voltage enough so that only a small amount of people experience crashes. However, user generally have no control over the voltage themselves and any increase in voltage is bad for electronic components. (exception being some of Eugene's kernels which allows UV by user).
I don't, its not needed. I like my battery life.
Sent from my SGH-T959 using XDA App
I dont usually oc unless I am near a power source. last night i tried the Dow kernals and wow my phone was dead within ours even while in standby. Imo thats just nuts. Even while Oc'd it shouldnt die that way.
What I am looking for is a kernal thats compatible with nero v3 that will maintain battery life aslong as I dont oc.
I have seen this post http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28&page=1 on Eugenes forum but non of the info makes sense. The one that does make sense has a older modem than the one I am using.
I guess I am use to the hd2 in which I would underclock to maintain decent battery life and use profiles. It doesnt seem like this cpu likes the profiles. amirite?
I would OC no question if we could get a UV kernel with good battery life like we did with Eclair. I won't do it with Froyo because of the terrible battery on i9000 kernels.
Sent from my SGH-T959 using XDA App
What TopShelf10 said is correct. Basically the trade off is this.... faster kernel.......quicker battery drain. That is the trade off. I have used oc kernels ...I do not use the phone for games, so EVERY thing I do on the phone the oc is not necessary. That statement is true for 95% of us.
BUT, that said, there is some cool macho feeling you get when your phone is in overdrive, just like my car, 350 hp but I live on an island that only allows 25mph speed limit...still, it doesn't change that feeling of awesomeness I get when I start the engine
I had nothing but issues with each and every OC ROM I tried. App alarm, pandora, slacker, ect. It was always something. My phone would actually get random freezes so it made the phone feel slower. Voodoo or OCLF on the other hand work wonders.
is it worth it?
well, here were the trades i had with dow14:
going from 13-14mflops to 18-19mflops in linpack (yeah, it's a benchmark, but it's hard to otherwise convey how the oc directly translated to the phone being extremely fast otherwise).
battery life went from easily going 22+ hours between charges to going 6-8 hours between charges.
however, with the core 1.2 oc i had great battery life and performance. so i assume (and have gathered from reading people more knowledgeable than me) the battery downside is due to it being a i9000 kernel. so hopefully/eventually we will get source for the vibrant 2.2 kernel and get an oc kernel with similar performance but much better battery life.
and until i flashed nero v3 and using voodoo, i kept super io and dow14 kernels on my phone so i could flash the oc if i wanted the performance or flash super io for battery life/day to day.
Hey guys, this thing poped up a while ago over at the Galaxy S forums
http://forum.xda-developers.com/showthread.php?t=981125
its suppose to increase overall smoothness of the phone in general, no porting was required to go on to basically all the other galaxy s and works for most of the froyo Roms. This is not suppose to change the benchmark scores in anyway, so the increase/decrease is most likely due to something else
Flashing the update.zip WILL NOT WORK, you have to use the alternative method which is replacing the files with root explorer, or something similar.
So it seems we have a mixed bag of results, if you actually applied the tweak (properly), please please vote if it works for you or not.
and of course, i take absolutely no credit for the work
Interesting post. I just backed up those two files:
/system/bin/app_process
/system/bin/system_server
...and then installed it through xRecovery. It seems to work fine. I mean, the bootanimation is still there, and nothing seems to crash (except Angry Birds for some reason, but I think that was already happening before I installed this). I can't say whether or not it's had a big effect though. Scrolling though the app drawer (in ADWLauncher EX) seems pretty smooth, as does scrolling in Root Explorer. I'll have to try it longer.
Thanks!
Edit: Wait, I don't think it installed properly. I checked the filesizes and they're still the originals. I'll try it again. Hold on.
hmmm no noticeable change but it did seem to boost my linpack
could be placebo but it does seem slightly smoother, like maybe it maxes your fps or something along those lines
Yup, not very noticeable but seem to increase my quadrant 10%. Still need to test more.
But, install in xrecovery, file date still 2008, file size fixed with new install. Anybody, have same issue?
Sent from my X10i using XDA App
Yup, installing it through xRecovery does nothing. It doesn't give an error, but it doesn't copy the files either. I managed to install the files properly using adb through xRecovery. I tried though adb while the phone was booted normally, but it couldn't overwrite the files because they were in use.
After installing, it works, but same story as above. I can't tell if it's better or worse. Quadrant scores about the same (~1300 for me) and Linpack scores around 34 (instead of 30 normally). The Linpack score could be because I had just rebooted though.
BTW, this is on FreeX10 beta 4.
Yup, just applied it (using Root Explorer) on CM 6.1.3 V4.4, after reading your post.. Killed boot-animation (to show its there), and doesn't seem to harm anything besides that. Hard to tell the difference, but maybe less laggy (I use Go Launcher (as cube) and LOTS of widgets) and apps loading slightly faster/ smoother.. Think I'll keep it!
Thank you for pointing, and thanks to nikademus! )
I'm on cm6.1.3 4.5.7, my x10 run at maximum 600mhz (setcpu) to save power. It's seem better speed. Just keep it, at least it's not harmful
Sent from my X10i using XDA App
Can anyone confirm if it actually does something really noticeable? Like maybe making the arc launcher a bit less laggy in Wolfbreak's rom??
abdurahman said:
Can anyone confirm if it actually does something really noticeable? Like maybe making the arc launcher a bit less laggy in Wolfbreak's rom??
Click to expand...
Click to collapse
it does definitely seem to improve scores at least, like stated though you need to use root explorer to move the files into the system/bin/ folder yourself. flashing the zip doesn't work
abdurahman said:
Can anyone confirm if it actually does something really noticeable? Like maybe making the arc launcher a bit less laggy in Wolfbreak's rom??
Click to expand...
Click to collapse
How noticeable does it really need to be? I love the Go Launcher because HS can be configured as rotating cube (a bit like my Linux with Compiz), but it had begone to feel a little laggy and now its perfectly smooth again.. Good enough for me!
thats weird, i don't think its suppose to raise any scores. But i guess on a different device it might have different effects.
FWIR what its suppose to do is raise the FPS across the phone and hold it constant.
Just in case imma backup using nandroid then ill install these two files and see what they do!
Sent from my X10a using XDA App
killed boot animation which i dont care.
and seems a bit smoother as far as scrolling goes.
so i'd say it did some good and no harm as of now.
I did test quadrant with 1ghz and confirmed not increase my quadrant. But during 3d test fps go up and down unlike before. Xrecovery intallation worked for me, it's kill my bootanimation too.
Sent from my X10i using XDA App
Does it really kill boot animation. But I like the cyanogen animation. Does it replace it with something else?
Also do I have to do anything with that Meta file?
Is it possible to reinstall the boot animation or is it impossible with this mod?
abdurahman said:
Is it possible to reinstall the boot animation or is it impossible with this mod?
Click to expand...
Click to collapse
I installed it using root explorer earlier and a can't see much difference to be fair...
The fps do seem a lil more consistent
And no I looked on the galaxy s thread and couldnt find anything to do with replacing it correct me if I'm wrong mate
Sent from my Arcified CM 6 X10i using XDA Premium App
I replaced both of the files by Root Explorer also made a backup.
Then set my cpu speed to (Performance) max 576Mhz min 245.
Phone performance - maintain (scrolling smoother) but manage to save me more battery.
Can't tell the performance for gaming as I'm not a big fans of games.
But it did make my x10i smooth, and save battery!
Edit : Angrybirds running smooth
If you look closely enough, the X10 drops frames severely with this tweak applied. To see what I mean, keep a close eye on the GFX benchmarks in Quadrant, you will notice it drops frames after every 5-8 seconds.
I tested it on Angry Birds too, it drops frames - you just have to watch closely and you will see it. I don't know if it has affected my Quadrant score 'coz I never benchmarked it before replacing the files, and with these 2 files replaced, my score is 1329.
Edit : I'm on Wolfbreak's CM 6.1.3 [2.2.1] v4.4 with MattedBlues theme applied. If neither of you experience dropped frames, it might as well be the theme or the ROM, not sure.
I have been messing with Antutu CPU and SetCPU just to see how well each is working. (never installed at the same time)
Been using System Tuner Pro and System Panel to watch the CPU.
With no CPU app installed, STP shows that the 2nd core is "offline" and SP shows no activity at all on the 2nd core either.
With Antutu CPU installed the 2nd core shows offline/no activity as well.
When SetCPU is installed, the 2nd core shows activity.
Sometimes it scales even with the 1st core and sometimes not. It scales both higher and lower than the 1st core, I am guessing the OS is issuing separate threads to each core and each thread's demands dictates the load of the individual cores.
I know that the 2 cores can scale Independent of each other, the 2nd core does not need to scale with the 1st core like some other current CPUs.
So what is going on to cause this? Is the kernel set to only use one core by default? I never seen any load for the 2nd core, even when running a graphically intensive game, and checking the load history.
And why does the 2nd core start working when SetCPU is installed? What does it change that Antutu does not? Seems we can get much better performance if SetCPU really does enable the 2nd core over what is default in the kernel.
So anyone have any thoughts on this?
Edit:
Antutu bench shows no improvement.
Glbench... Need to test more.
Linpack... Stock it shows an avg score of 48 and when using multithread option avg score of 43.
When SetCPU is installed, the scores are 48 and 75 respectfully.
I'm not 100% sure but I think I read somewhere that this is normal.The 2nd core remains inactive until it is actually needed.
the problem is that gingerbread is not designed to utilize a multi-core cpu. if you want to see both cores operational you'll have to move up to ics... that and i think they are still working out the bugs in that.
voxigenboy said:
the problem is that gingerbread is not designed to utilize a multi-core cpu. if you want to see both cores operational you'll have to move up to ics... that and i think they are still working out the bugs in that.
Click to expand...
Click to collapse
I am running scott's ICS cleanROM...
There is definatly no second core activity, but there is after installing and using SetCPU.
Funny, I was just going to ask about the second core. I have been keeping an eye on it in System Panel. Never shows any activity.. Seems inactive... Even when I checked history while running N64oid... I was surprised to see that emulator wasn't utilizing the second core. Although the emulator does run very well, it could definitely benefit from additional core..ks this all because of Gingerbread? It would seem like an app should be able to make use out of it... After all, it was shipped this way.
Marine6680 said:
I am running scott's ICS cleanROM...
There is definatly no second core activity, but there is after installing and using SetCPU.
Click to expand...
Click to collapse
that being the case it can be dependent on the build/settings. the setcpu thing makes sense due to the nature of the app. even then, depending on rom/kernal, setcpu allows not only for under/overclocking but also voltage control.
voxigenboy said:
that being the case it can be dependent on the build/settings. the setcpu thing makes sense due to the nature of the app. even then, depending on rom/kernal, setcpu allows not only for under/overclocking but also voltage control.
Click to expand...
Click to collapse
Antutu cpu doesn't cause any activity in the second core, only setcpu. Seems both would work the same.
I don't play with these apps very often, but because some of the kernels jump around, I tried CPU tweaker. It shows both cores, and temp, and load. You might check it out just for fun. It seems to show both kernels, and their frequencies. I wish I could be of more help, but this is my first dual core.
Sent from my ADR6425LVW using Tapatalk
If u want them both on, remove the mdprecision file, or copy it and move it out of the folder, or just rename it, and then reboot and the second core will be on. I usually copy mine to the system folder and rename the original by adding .bak onto the end
I think its located in /system/bin
It does making a difference having them both on, battery life will be a little less but not much. But it goes faster during app switching and such.. it gives it an edge I think. I leave my second core standard on demand, because its fast enough for me like that and battery life is a little better.
Edit: also, generally my phone benches a little higher with both cores active, instead of the stock way and the second one being on demand. Anyway. Try it, xD
Edit 2: Oh also, if you want to revert back, place the mdpresicion file back in the /system/bin folder and reboot. I assumed that was self explanatory, but just in case lulz
I guess its never safe to assume though
I would think leaving it offline unless it's actually needed is a smarter bet unless you're a benchmark whore.
platinumrims said:
If u want them both on, remove the mdprecision file, or copy it and move it out of the folder, or just rename it, and then reboot and the second core will be on. I usually copy mine to the system folder and rename the original by adding .bak onto the end
I think its located in /system/bin
It does making a difference having them both on, battery life will be a little less but not much. But it goes faster during app switching and such.. it gives it an edge I think. I leave my second core standard on demand, because its fast enough for me like that and battery life is a little better.
Edit: also, generally my phone benches a little higher with both cores active, instead of the stock way and the second one being on demand. Anyway. Try it, xD
Click to expand...
Click to collapse
how do you change the settings of both cores separately as in leave one core ON DEMAND and the second on INTERACTIVE..is there an app that can do that or is that something done on a different level.
platinumrims said:
If u want them both on, remove the mdprecision file, or copy it and move it out of the folder, or just rename it, and then reboot and the second core will be on. I usually copy mine to the system folder and rename the original by adding .bak onto the end
I think its located in /system/bin
It does making a difference having them both on, battery life will be a little less but not much. But it goes faster during app switching and such.. it gives it an edge I think. I leave my second core standard on demand, because its fast enough for me like that and battery life is a little better.
Edit: also, generally my phone benches a little higher with both cores active, instead of the stock way and the second one being on demand. Anyway. Try it, xD
Click to expand...
Click to collapse
Mm I've actually scored higher w/ benches w/ leaving the file intact. 6,500 on Antutu on ics and 5,800 - 5,900 w/ the file renamed/removed. But tbh I could care less about benches since they mean jack to me, I'll play around with this and see the batterylife/performance.
jonathan413 said:
how do you change the settings of both cores separately as in leave one core ON DEMAND and the second on INTERACTIVE..is there an app that can do that or is that something done on a different level.
Click to expand...
Click to collapse
Lol maybe u can do that eventually with ICS but I'm not aware of a way to do that now though. That would be pretty sweet though.
zetsumeikuro said:
Mm I've actually scored higher w/ benches w/ leaving the file intact. 6,500 on Antutu on ics and 5,800 - 5,900 w/ the file renamed/removed. But tbh I could care less about benches since they mean jack to me, I'll play around with this and see the batterylife/performance.
Click to expand...
Click to collapse
Yea, I'm not saying it was always higher but they were usually. I definitely had some that were lower too though. I never tested that with ICS either. Only GB. But I did notice that UI interactions were a little snappier for the most part
That's why Benchmarks are silly
platinumrims said:
If u want them both on, remove the mdprecision file, or copy it and move it out of the folder, or just rename it, and then reboot and the second core will be on. I usually copy mine to the system folder and rename the original by adding .bak onto the end
I think its located in /system/bin
It does making a difference having them both on, battery life will be a little less but not much. But it goes faster during app switching and such.. it gives it an edge I think. I leave my second core standard on demand, because its fast enough for me like that and battery life is a little better.
Edit: also, generally my phone benches a little higher with both cores active, instead of the stock way and the second one being on demand. Anyway. Try it, xD
Edit 2: Oh also, if you want to revert back, place the mdpresicion file back in the /system/bin folder and reboot. I assumed that was self explanatory, but just in case lulz
I guess its never safe to assume though
Click to expand...
Click to collapse
Are you talking about mdprecision or mpdecision?
bbeaulieu said:
Are you talking about mdprecision or mpdecision?
Click to expand...
Click to collapse
I'd,edit my posts but that's just too funny
I just found it odd that even in ICS the second core was offline when ICS is supposed to be optimized for dual core.
It wasn't that it came on sometimes under very heavy load... it just never comes on.
And like I said, SetCPU is the only way I have found that enables the second core.
Hopefully people with more knowledge about this than I can figure out what is actually going on.
platinumrims said:
I'd,edit my posts but that's just too funny
Click to expand...
Click to collapse
lol i just wanted to make sure
Maybe only the Gnex is designed in a way to use ICS' dual core optimizations until actual OEM releases of ICS come out where it somehow enables it.
-Sent from my Droid 2-
Marine6680 said:
I just found it odd that even in ICS the second core was offline when ICS is supposed to be optimized for dual core.
It wasn't that it came on sometimes under very heavy load... it just never comes on.
And like I said, SetCPU is the only way I have found that enables the second core.
Hopefully people with more knowledge about this than I can figure out what is actually going on.
Click to expand...
Click to collapse
How do you mean enable it via setcpu?
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.