I just decided to benchmark my s6 with antutu and I am only getting a score of 45413 points. How can it score such a low point? I have seen people getting scores up to 70000.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
albysajan said:
I just decided to benchmark my s6 with antutu and I am only getting a score of 45413 points. How can it score such a low point? I have seen people getting scores up to 70000.
Click to expand...
Click to collapse
caues :
-your phone was warm/hot
-your phone was on charging
-there were lot of background apps running
-you are probably running 32 bit version of antutu
-you are on power saving mode
bhavstech said:
caues :
-your phone was warm/hot
-your phone was on charging
-there were lot of background apps running
-you are probably running 32 bit version of antutu
-you are on power saving mode
Click to expand...
Click to collapse
I guess it was due to the fact that my phone was charging at 18%.
I have some issues to
Those benchmark addicts are everywhere lol.
No. 1 reason is that your phone is hot.
The rest follows.
Getting in loved too much with benchmark scores. You're device is one of the most powerful smartphone in the market right now, don't worry
Shots fired ... fast charge gets your phone so f... hot. I did benchmark when my phone was so cold, to eleminate throtling possibilities
Related
yesterday I got a slow phone when my battery was blow 10%. Is this a feature of Android that it work slower for saving the battery?
My unlock swipe code was very slow and I rebooted my phone and after that anything work just fine.
How can I solve this if the problem coms angain???
lonelobo0070 said:
yesterday I got a slow phone when my battery was blow 10%. Is this a feature of Android that it work slower for saving the battery?
My unlock swipe code was very slow and I rebooted my phone and after that anything work just fine.
How can I solve this if the problem coms angain???
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can you solve it?
Don't let your battery get below 10%?
The system is designed so that when the battery gets too low it turns off a lot of stuff so that the device will last for longer to do what it was actually made for - be a phone.
SimonTS said:
How can you solve it?
Don't let your battery get below 10%?
The system is designed so that when the battery gets too low it turns off a lot of stuff so that the device will last for longer to do what it was actually made for - be a phone.
Click to expand...
Click to collapse
Indeed often the cpu is slowed down to which would cause lag.
But yes the best thing to stop it would be to keep your phone charged
Sent from my GT-N7000 using xda premium
I recently bought a Nexus S from someone. It runs okay though sometimes I feel a bit of lag.
Currently it's running AOKP milestone 4.1.2. I run the Quadrant Standard and got very low scores, both with stock and custom ROMs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this a cause for concern? Moreover, can anybody guide me what's causing this?
ahmadmalik88 said:
I recently bought a Nexus S from someone. It runs okay though sometimes I feel a bit of lag.
Currently it's running AOKP milestone 4.1.2. I run the Quadrant Standard and got very low scores, both with stock and custom ROMs.
Is this a cause for concern? Moreover, can anybody guide me what's causing this?
Click to expand...
Click to collapse
Try to wipe everything and start fresh.
I started afresh when I bought it. Unlocked the bootloader and wiped the data and all. But I guess I'll try again.
Meanwhile, any other guesses?
IF you look at your benchmark and compare it with Nexus s then look at the Blue cpu and The red mem - then you find your nexus ok - I Think you have to move your apps to your sd Card - smile
Sent from my Nexus S using xda app-developers app
Ok so moving the apps to SD card did give me a better score but the I/O and 2D scores are still relatively very low.
Below is first Quadrant Standard test I did after official update...WOW!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC VLE_U using Xparent Skyblue Tapatalk 2
i'm somewhat of an idiot to this quadrant speak...can you explain, to the lay person, what this means?
Jimmmycrackcorn said:
i'm somewhat of an idiot to this quadrant speak...can you explain, to the lay person, what this means?
Click to expand...
Click to collapse
Quadrant is just an app that benchmarks your phone. Or simply put runs a series of tests on your phone to determine how fast your phone can perform tasks. It tests GPU, CPU and how efficient your phones ram is along with other things. It will then provide a score for how well your device has performed the tasks. The higher the score the better.
i get also scores >6400 (stock), whereas my friends (stock) galaxy S3 gets only 5800. I kow benchmark scores does not really say anthing about everyday-use-performance but also in this area i prefer to use the One S and can say it is indeed more fluid than S3. we can say the One S is the best phone <4,5" ..
HTC did a well done job in releasing such a powerful phone which does not have sizes of tablets but a comfortable easy to handle 4.3" screen. I hope they release Sense 5 soon, and i am waiting for the successor of One S with same dimensions but higher pixel density and higher battery-capacity.
I'm on Twisted Kernel OC'd at 1.9GHz and I'm only getting a 4k score. When I was on ViperOneS, I had a 5.8k score or something. Not fair :x
when it comes to benchmarks, for me stock was always the one with most points. does not say anything about overall performance tough
Since I see so much Ignorant in the Battery thread, I like to point out (rant) some things..
1. A person 6 hour of Screen On Time usage is different from person to person.
2. Temperature can have a great affect on battery life.
3. Signal strength can have a great affect on battery life.
So with that in mind, I suggest everyone try to do a PC Mark bench, it is fair and give people a much better idea of what of what they should be getting. To do this test here are the few settings you need to set
1. BRIGHTNESS AT 23-25% (EYEBALL IT)
2. Wifi on
3. do not disable Mobile data or sync
4. Clear all RAM before start
below are the CONTROL numbers from a stock rom (pictures are from greenbot.com)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Below is my stat, using arter kernel and foreverloco rom. (I DO UNDERVOLT MY KERNEL)
Is this ok? Running skyhigh 2.1 and darthstalker v4 rom. A57 cores @ 2.4ghz and gpu @ 852mhz with a -75mv uv all accross the board.
I ll post my battery result as soon as i can, meanwhile here s my previous battery result i got a few days ago... http://forum.xda-developers.com/showthread.php?p=63851201
Here s my pcmark battery score too. I started it from 90% after already using the phone for a whole hour (sot of about 1h6mins)
ran pcmark again with skyhigh 2.3 ...running at 2.4ghz a57...
Hello,
Is my Geekbench score okay or something is wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quite under the expected range. Did you perform it at ambient temperature, or used a heavy-load app stressing the chip just before running the test?
I remember my first one gave similar results, I then ran an other one and it was more accurate to the chip advertised performances.
Jaxom84 said:
Quite under the expected range. Did you perform it at ambient temperature, or used a heavy-load app stressing the chip just before running the test?
I remember my first one gave similar results, I then ran an other one and it was more accurate to the chip advertised performances.
Click to expand...
Click to collapse
I tried to run it after a while and it performs much better now, I don't know what caused it, before first test I was using Chrome nothing much...
hiMLASTAR7 said:
I tried to run it after a while and it performs much better now, I don't know what caused it, before first test I was using Chrome nothing much...
Click to expand...
Click to collapse
When you look at your screenshot, it seems the CPU is also focusing on how energy is spent (energy_aware), which could also explain the first results. The device can understand how you use it and adapt the power usage depending on what you "teach" it. So nothing to worry about.
Also, the Android 13 Beta is showing some improvements for Exynos versions of the device, so expect it to run even better with time.
Here are my current results with the Android 13 Beta 1 on my Exynos 2200, so you can see the little improvement.
Android 13 one ui 5 beta exynos 2200