I have the highest score listed at 3300. What I'm asking is for people to start downloading AnTuTu Benchmark and running benchmarks while overclocked at 1.152 GHz, see if the score reaches over mine. I want do some research about our phones, but the more scores that are in, the easier and faster ill be able to compile my findings, and come up with something to further increase performance.
sent from my SGH-T839 (Sidekick 4G) running Glorious Overdose V3.0.3.
Benchmarks are bull****. Each value will come up differently depending on what is going on in the background and how Android chose to throttle the CPU while the benchmark was running...
Beyond that...
Overclocking this device is a known source of instability and most devices will crash under heavy load.
Also, I expect the heat will eventually cause issues when using GPS.
Any device is only as good as the weakest link and you are not increasing the speed of the memory, GPU, or the busses on the board.
What you are doing is increasing the heat inside the case above what the heatsinks are designed to handle and causing timing/sync issues.
There have been times in the past that a manufacturer saved money by producing a large amount of one chip and used it in many devices. In that kind of situation, the chip was sometimes "underclocked" and put in budget devices. I can assure you that is not the case with the Sidekick 4g.
Overclocking is an interesting idea in a large PC because there is plenty of room and accessories available. This device is not a PC.
Sorry, didn't see your reply sooner, been busy with the ROM and general life crap. But yes, too fast and you lag, but with the right overclock, you won't get too hot, but a notice a fair amount of increase. Though yes, I only overclock when need be due to increased battery drain. Regardless, I'm doing limit testing for stability purposes, speed purposes, and because I may attempt at one point to see what I can do about coworking 2.3 at the very least before switching over to the G2. After college starts, I won't be on here much at all.
sent from my SGH-T839 (Sidekick 4G) running Glorious Overdose V3.0.3.
Related
So after reading nearly 5 hours and spending my time in the wee hours of morning, I finally did all the "stable" mods for the phone... If you haven't been reading, make sure you guys check out the stuff in the development forum.
After all modifications, I was able to get 2701 points in quadrant benchmark. What mods did I do?
-i9000 eclair flash (JM5)
http://forum.xda-developers.com/showthread.php?t=734871
-Alternative mimocans lag fix
(one click installer http://forum.xda-developers.com/showthread.php?t=749495)
-One click root (googled it for i9000)
-Overclock kernel 1.0Ghz to 1.2Ghz
(http://forum.xda-developers.com/showthread.php?t=746343)
This stuff really does help out your phone folks. Bench it now with quadrant, then take a peak at the other stuff and make magic happen. If anyone needs any additional help setting up their captivate, I'm more than happy to help.
I agree those fixes help speed a lot. But the quadrant score is meaningless. the speed hack creates an io loopback. The loopback just tells quadrant what it wants to hear.
Does your BT work on the european ROM. For me all people hear is a gargeled mess on there end?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Can you post the results of these tests:
Neocore
Linpack
CPU Benchmark
I keep hearing about this quadrant, does it actually improve real world performance? Or is just for the sake of scores?
jhego said:
I keep hearing about this quadrant, does it actually improve real world performance? Or is just for the sake of scores?
Click to expand...
Click to collapse
Quadrant is just benchmarking software that takes the cpu, gpu and memory read/write speeds into account. It runs a series of tests and spits a score number out at the end, so you can compare your device to others (like comparing boner sizes, but less gay).
It doesn't actually do anything to speed up the device though.
modest_mandroid said:
Quadrant is just benchmarking software that takes the cpu, gpu and memory read/write speeds into account. It runs a series of tests and spits a score number out at the end, so you can compare your device to others (like comparing boner sizes, but less gay).
It doesn't actually do anything to speed up the device though.
Click to expand...
Click to collapse
This is correct and to be honest there is way to much weight in the I/O tests. That is the only reason that the stock Droid X bests the Gal X. It has more weight than cpu and gpu so you can't put to much into those scores. They really don't mean anything more than bragging rights. What I am interested in is real world usage.
Real world use with the hack provides amazing speed gains opening and switching apps. Io heavy apps are very much improved while open too. It's finally as fast as the iphone.
Whats your battery life like after the overclock?
The score ended up getting lower and lower every time i used quadrant. 2701 is the highest I was able to get so far, but that's with a fresh install of the rom and all the stuff before I started loading on apps. Everytime I ran the benchmark, I of course killed the apps beforehand.
The battery life is the same- to be honest. This is me comparing a rooted stock ROM to the somewhat fresh install of the eclair i9000. The phone is very snappy. I came from an iPhone 4 and one of the biggest eye sores to me was the less-fluidness of changing programs, response to buttons (homescreen-back button) and pinch to zoom. After all these changes, it's a whole different story. Browsing is very appealing, especially since pinch to zoom isn't jagged or slow. The smoothness of this functionality is on par to an iPhone. And there is no waiting when I press the home button or back button.
True, maybe these numbers aren't considerably accurate (as far as the lag fix and EXT2) but at least it shows raw computing capability in it's current state... meaning, the usage of a virtual EXT2. Never the less, the phone is still all around faster, even if it isn't exactly the proper way of going about it.
The only problem I've seen so far is that it likes to randomly shut off. Won't respond to anything unless if I soft reset it. I haven't really found what causes it, since the consistency of it happening goes about in a non set pattern.
I didn't see any real world increase .. so I reverted back in about 4 hours.... I'd rather have the memory than a number that don't transfer to real world speeds...
I use the phone overclocked and non overclock and i cant seem to notice a difference at all in the phones preformance. At stock speeds it is just as fast as overclocked. There doesnt seem any difference in noticable speed of overclocking to me. Do any of you notice a difference.
i see a difference on some of the more laggy roms but it is small. think about it, the most you can see is a posible 20% at 1200mhz and with cpu scaling it isn't that often it usses 1200. although that is significant you still have the same memory bandwidth and file read/write speeds. the responsiveness difference in the kernel has more to do with available ram and kernel hz. as well as aggressiveness in cpu throttling.
overclocking is more for benchmarks and bragging rights. it's for those that need to tweak and whatever or those that need to say theres is better. i can turn the phone down to 600mhz on the old 2.1 kernels that had that step added in before i could notice and it still wasnt laggy much beyond the normal touchwiz. even 400 was usable.
now if the phone is older and the os and apps push the boundries of its capabilities by all means overclock to keep up with the times. otherwise it is preference for your own personal reasons. i do it to test what the phone is capable of. but i often have it disabled.
there is power locked away in these phones that we havent seen yet, the 3d processor can run opengl at framerates better than older laptops i have used and after all these months no other manufacturer has felt the need to compete with it. some open gl benchmarks are fully twice as high as a droid 2/x and 20% better than the newest htc phones running qualcom chips and even the motorolas are considered to have a power gpu. it is a great gaming platform as is and the gpu is stable at 11% overclock, some phones at 25% overclock and maybe beyond. if you flash a custom rom that doesnt lag and do the whole ext4 or jfs conversion you should be happy with the performance of the phone untill your contract is up and maybe beyond. the technology is accelerating faster than the software.
after honeycomb and dualcore platforms hit the shelves then the software that will take advantage of our hidden power will start to roll out. at this time too many android phones are running at 500-600 mhz with little opengl capability, even the popular 1ghz snapdragon phones like the evo as well as they benchmark cant run 3d applications very well and there popularity is holding up software devlopment is some way. there isnt much money in apps that only run on the top 5% of the phones out there. we will have to wait till the droid2/x galaxy s and g2 and mt4g are the norm and there are faster platforms available before we see great differences in overclocking. maybe honeycomb or whatever comes after that will use some opengl in the ui or something, who knows.
Dani897 said:
i see a difference on some of the more laggy roms but it is small. think about it, the most you can see is a posible 20% at 1200mhz and with cpu scaling it isn't that often it usses 1200. although that is significant you still have the same memory bandwidth and file read/write speeds. the responsiveness difference in the kernel has more to do with available ram and kernel hz. as well as aggressiveness in cpu throttling.
overclocking is more for benchmarks and bragging rights. it's for those that need to tweak and whatever or those that need to say theres is better. i can turn the phone down to 600mhz on the old 2.1 kernels that had that step added in before i could notice and it still wasnt laggy much beyond the normal touchwiz. even 400 was usable.
now if the phone is older and the os and apps push the boundries of its capabilities by all means overclock to keep up with the times. otherwise it is preference for your own personal reasons. i do it to test what the phone is capable of. but i often have it disabled.
there is power locked away in these phones that we havent seen yet, the 3d processor can run opengl at framerates better than older laptops i have used and after all these months no other manufacturer has felt the need to compete with it. some open gl benchmarks are fully twice as high as a droid 2/x and 20% better than the newest htc phones running qualcom chips and even the motorolas are considered to have a power gpu. it is a great gaming platform as is and the gpu is stable at 11% overclock, some phones at 25% overclock and maybe beyond. if you flash a custom rom that doesnt lag and do the whole ext4 or jfs conversion you should be happy with the performance of the phone untill your contract is up and maybe beyond. the technology is accelerating faster than the software.
after honeycomb and dualcore platforms hit the shelves then the software that will take advantage of our hidden power will start to roll out. at this time too many android phones are running at 500-600 mhz with little opengl capability, even the popular 1ghz snapdragon phones like the evo as well as they benchmark cant run 3d applications very well and there popularity is holding up software devlopment is some way. there isnt much money in apps that only run on the top 5% of the phones out there. we will have to wait till the droid2/x galaxy s and g2 and mt4g are the norm and there are faster platforms available before we see great differences in overclocking. maybe honeycomb or whatever comes after that will use some opengl in the ui or something, who knows.
Click to expand...
Click to collapse
agreed
overclocking seems pretty pointless at this point other than bragging rights
the only situation i can see it being handy are game emulators
Don't forget HQ flash streams on the browser, like some on justin.tv. My personal experience was that at 1 ghz it was a little bit choppy, and according to the rom as well, somewhere between 1.2 and 1.4 it becomes really smooth. Though if I used skyfire to watch it is smooth at stock speed, but some quality is lost in the optimization.
Am I the only one that thinks there is a difference at this? I also think the performance on heavy flash web pages improves when I use oc.
I have not seen any real difference in other than flash performance though... But I was kind of expecting this since in my desktop I had to use oc for it to work smoother as well.
I read a lot about undervolting on here and i think i have an idea about what it does but i may be way off, and im sure each device is different. in pimp my cpu there are multiple options, and while this sounds newbish i think this should be explained to folks in some more detail.
this is what im assuming.
undervolting allows for less power consumption.
UV on higher OC levels controls power spikes to the CPU?
what is a safe level to UV and at what frequencies specific to the G2x
i am reading up on this, to get a better idea. http://www.android.net/forum/android-rooting/58117-droid-x-guide-undervolting-guide.html
Here's my understanding of the whole undervolting thing..
In order to maintain stable operation across devices with varying production quality (not all chips are created equal), manufactures use voltage levels higher than necessary for most devices. They cater to the least common denominator. But most phones will still operate reliably at a lower voltage. By undervolting you can extend your battery life and ward off chip killing heat. This all becomes even more important when overclocking. When you overclock your device you increase the power usages (those extra megahertz aren't without cost). This increases both the drain on your battery and the heat produced by your CPU. Undervolting helps to offset both issues.
As for the proper undervolting levels...that will vary with the tolerance of each individual device. But I'm sure someone can provide some general guidelines...sorry I haven't undervolted the g2x yet and don't want to steer you wrong.
Hope this helped...
Good info. I dropped mine .25 on each higher level. So ill see how it goes
G2x with CM7 and faux kernel
what confuses me on this topic is the "it's different for each device" phrase that I keep reading. Is this in reference to the rom/kernel that is being used or is it specific to apps installed/how the phone is used.. or is it a combo of both?
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware. So I don't quite get this "it's different for each device" thing..
schmit said:
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware.
Click to expand...
Click to collapse
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
i think you mean this.
cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.
eagle1967 said:
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.
Click to expand...
Click to collapse
Nice...that was much better than my explanation.
cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
lol. dude, I'm in the g2x forum.. not the "whatever phone ya wanna talk about" forum. I was referring to the g2x's having the same hardware, lol.
Thanks to the other guy for the awesome explanation
How can I go about overclocking my droid charge? I am running TWEAKSTOCK 1.0 rom and was wondering how to overclock my charge?
I haven't seen any over clockable kernels so until then I don't think you can.
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Chitala383 said:
Download tegrak overclock from the market if u want to overclock. I'm running mine at 1.2 and undervolted and it works great.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
With the same kernel?
Well, if you actually searched, this would be clearly stated in many threads.
For GB overclocking, use Tegrak for now, until we can get an actual OC kernel up and running. I think Tegrak will work on the stock kernel as long as you're rooted, as it uses a module to modify the CPU frequency.
Sent from my SCH-I510 using xda premium
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
xdadevnube said:
Another tegrak user here. I paid for the ultimate version for undervolt and start on boot
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
BattsNotIncld said:
Are there noticeable improvements with overclocking/undervolting?
Also what settings do you use?
Click to expand...
Click to collapse
Take what I say with a grain of sand, I'm expressing my views without much scientific validation.
Keep in mind that overclocking is like icing on the cake. There are far more beneficial things like changing the scheduler to noop or deadline. Fugu tweaks and V-6 are highly recommended to improve responsiveness and improve your launcher resiliency. That said, I feel overclocking has its place and helps in many cases. I've noticed, in general, various tasks and some web-browsing will benefit from the increased clock speed. Some things don't ramp up the CPU very much and you won't notice much difference in that case.
I monitor my CPU usage with CPUNotify as well as OS Monitor.
I monitor the CPU temps with TempMonitor (it allows for a notifcation icon that shows the CPU temp.)
I use StabilityTest to check for overclock settings stability. The cool thing about Tegrak is that when you apply overclock settings on boot (paid version only) and you choose settings that crash the phone, the settings don't apply until most of the phone is already booted up, so you aren't stuck in an infinite boot loop of crashing fun. You should be able to simply change up the settings after they apply since the phone will be mostly idle by the time Tegrak settings are applied.
As for settings...
I use the Interactive X governor. I prefer this governor for its simplicity and ability to ramp up to high CPU clock speeds quickly. I enable the governor by typeing "su" and "ix enable" in Terminal Emulator when on Imoseyon's 4.0 kernel.
I change the "scaling min" to 200Mhz to avoid instability when CPU usage ramps down quickly.
Currently at CPU Level 0 I am at 1265mv Core Voltage, 1100mV (unchanged) Internal Voltage, and 1200 Mhz Frequency.
I don't actually change other CPU Levels.
Lately I've been just keeping at eye on temps so I haven't achieved my desired clock speed of a relatively low-voltage 1.4Ghz to 1.5Ghz.
Overclocking is very dependent on the particular sample you get. Some of us have "Golden Chips" and some of us have duds.
Your CPU should be totally safe at temps around 130 degrees F, although I suspect that it could even take higher sustained temps well above that if it needed. I don't actually know, this is speculation.
I like to keep my temps low in general, I rarely crack 100F with my current settings (weather is cool here.)
Overclocking computers is one of my hobbies, and its fun to dive into the phone side of things. I haven't been able to find a whole lot of information regarding overclocking the Hummingbird processor. People have overclocked to 1.6Ghz. Stability tests are essential to improve the reliability of your overclock. Die hards will run the tests for 24 hours to weeks in the computer realm. At least with computers its better understood how the stability test actually works. I run 24 hours of Orthos blend mode (Prime95) on each core.
With phones, its hard to say if it will truly be stable.
I test for an hour on the phone with StabilityTest and call it good. Hopefully in the future more information will come to light regarding how to properly overclock.
Remember, the other side of the coin is underclocking and undervolting. If you drop your voltage, you should see a nice increaes in battery life. If you drop your clocks, then you can drop your voltage even more. If you get your phone dialed in to where there isn't much background apps sucking juice- a phone that is UV/UC'ed should have excellent battery life.
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
kvswim said:
Does anyone else read noop as nope?
What's the difference between internal and CPU voltage?
Also, I hope you know that Orthos does not scale well across multiple cores. You are essentially relying on Task Manager to put the load on different cores.Orthos was originally made with dual cores in mind.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
xdadevnube said:
Apparently little is known in the public domain about Internal voltage. I have been unable to find good information regarding Internal voltage. Knowing little about the architecture of the SOC, I suspect it is a voltage that controls different parts of the SOC hub. I suspect that you could say its synonymous with a computer motherboard's voltage (although there are several.)
I find it interesting that, as far as I can tell, few people have increased Internal voltage much even though they may achieve a clock speed of 1.6GHz by increasing CPU voltage.
In any case, I have heard reports of instability by going to low, as would be expected. I haven't found the need to increase Internal voltage yet.
P.S. You can run an instance of Prime95 on each "core" or one instance of Orthos per two "cores" and still be able to test stability reliably. You have to set Core affinity, and I usually set it so that each core and hyperthreaded core each get an instance of Orthos. In this case, each core's usage will be 100%.
Click to expand...
Click to collapse
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
kvswim said:
Internal SOC voltage...maybe akin to northbridge or southbridge voltage? When OCing a computer you have to keep the northbridge within a nominal voltage of the CPU frequency (if that makes sense). Too much of a discrepancy makes the computer unstable. Increasing the southbridge voltage increases the memory overclocking stability with large amounts of RAM, and obviously, when you overclock a processor you are also overclocking memory.
Maybe we could ask the developer? Although he is Korean and we may not be able to get our point across.
For stability testing on PCs I recommend OCCT. Scales well over Multiple cores and also allows GPU and power supply stability testing.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
xdadevnube said:
Well, I have heard of slight Internal Voltage increases being necessary for high overclocks on Hummingbird. I have heard dropping it causes major instability. I would guess that it doesn't need to be modified for modest overclocks.
I did quite a bit of web searching trying to find conclusive guides or overclocking results for Humminbird to no avail.
I use ATI Tool for checking GPUs, but OCCT may be better. It seems OCCT has improved a fair bit, I may use it.
Click to expand...
Click to collapse
Probably because no one has taken the time to write one. Not exactly in high demand. I knew of one "guide" but the site has been down for quite some time.
Of course there are noobs guides but nothing quite in depth. I suppose people don't write them because there are obvious limits set by the kernel dev, and anything beyond that requires someone who obviously knows what they're doing, which defeats they purpose of a guide.
Sent from my GT-P1000 using xda premium
I'm struggling to get my head around this drastic difference in speed.
Stock ROM on linpack scores about 100Mflops on single thread, and 200Mflops on multi thread similar to this video at 2:50 http://www.youtube.com/watch?v=Zh5quKyypw8
However since flashing CM10 my linpack scores have more than halved! I never get over 80Mflops now on multi thread, and rarely over 40Mflops on single thread. Also in quadrant it shows my cpu scoring really low, but my RAM scoring very high. I was wondering if my the ROMs are effecting my processor speeds?
I am about to go back to the stock ROM to see if linpack scores shoot back up!
If you don't notice a difference who cares about benchmark scores?
Sent from my HTC VLE_U using xda app-developers app
Well I do agree with what you are saying, and it still seems very fast. But I used it for less than a day on the stock ROM, so I don't really have anything to compare it to.
I am wondering more if these benchmarks are giving false readings, or if they are actually picking up on some poor processor optimisations, which whilst may not be noticeable day to day, could have a greater impact on CPU hungry tasks such as making and restoring large backups etc.
But benchmarks for the sake of benchmarks I agree are pointless.
RichardW1992 said:
Well I do agree with what you are saying, and it still seems very fast. But I used it for less than a day on the stock ROM, so I don't really have anything to compare it to.
I am wondering more if these benchmarks are giving false readings, or if they are actually picking up on some poor processor optimisations, which whilst may not be noticeable day to day, could have a greater impact on CPU hungry tasks such as making and restoring large backups etc.
But benchmarks for the sake of benchmarks I agree are pointless.
Click to expand...
Click to collapse
I pretty much stopped using custom roms that aren't based on official sense based roms because of low benchmark numbers, questionable battery life and terrible camera support.
HTC has most if not all drivers for the hardware closed source, so developers are trying their best but I just use the stock ROM
RichardW1992 said:
Well I do agree with what you are saying, and it still seems very fast. But I used it for less than a day on the stock ROM, so I don't really have anything to compare it to.
I am wondering more if these benchmarks are giving false readings, or if they are actually picking up on some poor processor optimisations, which whilst may not be noticeable day to day, could have a greater impact on CPU hungry tasks such as making and restoring large backups etc.
But benchmarks for the sake of benchmarks I agree are pointless.
Click to expand...
Click to collapse
Your not getting false readings... That's just how it is.. Bench marks don't mean anything... Cm will always have a lower score than stock but is just as fast.. If your worried about scores flash a ROM based on sense ota...
Sent from my HTC One S using xda premium