Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.mobile.android > #55491 > unrolled thread

GeekBench4 Score Went Down Post Setting Up Phone?

Started by"(PeteCresswell)" <x@y.Invalid>
First post2018-09-03 14:35 -0400
Last post2018-09-07 11:19 -0400
Articles 5 — 3 participants

Back to article view | Back to comp.mobile.android


Contents

  GeekBench4 Score Went Down Post Setting Up Phone? "(PeteCresswell)" <x@y.Invalid> - 2018-09-03 14:35 -0400
    Re: GeekBench4 Score Went Down Post Setting Up Phone? VanguardLH <V@nguard.LH> - 2018-09-03 14:59 -0500
      Re: GeekBench4 Score Went Down Post Setting Up Phone? "(PeteCresswell)" <x@y.Invalid> - 2018-09-07 11:16 -0400
    Re: GeekBench4 Score Went Down Post Setting Up Phone? Anssi Saari <as@sci.fi> - 2018-09-04 12:06 +0300
      Re: GeekBench4 Score Went Down Post Setting Up Phone? "(PeteCresswell)" <x@y.Invalid> - 2018-09-07 11:19 -0400

#55491 — GeekBench4 Score Went Down Post Setting Up Phone?

From"(PeteCresswell)" <x@y.Invalid>
Date2018-09-03 14:35 -0400
SubjectGeekBench4 Score Went Down Post Setting Up Phone?
Message-ID<5fvqodhrfiff17lr36vc3920bm9ob0trgq@4ax.com>
New Note 4 (N950U1).

Out of the box, GeekBench gave it 7999 on the "Compute"/"RenderScript" test.

After a few days of setting it up, it's down to 7500.

Are there any typical causes of something like this?

As soon as I find out how, I intend to root the device in hopes of getting
it back up to 7999 (NoBloat et al...)  or, at least, keep it from falling
further.

??
-- 
Pete Cresswell

[toc] | [next] | [standalone]


#55493

FromVanguardLH <V@nguard.LH>
Date2018-09-03 14:59 -0500
Message-ID<cmquwh2r9uom.dlg@v.nguard.lh>
In reply to#55491
PeteCresswell wrote:

> New Note 4 (N950U1). 
> 
> Out of the box, GeekBench gave it 7999 on the "Compute/RenderScript"
> test. After a few days of setting it up, it's down to 7500. Are there
> any typical causes of something like this?

Did you restart the phone and NOT use any apps before running the
benchmark?

Many apps run as services or restartable processes: you can kill them
using an app but they'll reappear.  Since they are in memory and
running, they'll consume resources.

I use Droid Optimizer to kill backgrounded processes; however, as
mentioned, some will reappear.  It has a whitelist which is handy but I
need to have it show system processes: I want Hangouts Dialer to keep
running to take/make wi-fi based calls and it shows as a regular app but
its parent program, Hangouts, only appears as a system app, and if I
have Droid Optimizer kill Hangouts then the Hangouts Dialer won't work.

What does "a few days of setting up" mean?  That you installed lots of
apps?  Use something like Droid Optimizer or similar to see what is left
running in the background that shows both user and system apps.  Android
doesn't unload apps when you supposedly exit or close them but instead
leaves them running in the background.  You could have service or
restartable apps running in the background along with any recently used
apps also running in the background.  

Benchmarks aren't comparable when the load on the OS isn't comparable.
The clean phone got a better benchmark than a dirty phone.  That's no
surprise.

> As soon as I find out how, I intend to root the device in hopes of
> getting it back up to 7999 (NoBloat et al...)  or, at least, keep it
> from falling further.

Wow, you're going to risk rooting a new phone (with someone else's code)
along with voiding its warranty?  I'd do that with a cheap smartphone
(under $200) but I'd wait until the warranty expires before committing
brain surgery on a $700-$900 smartphone.  

[toc] | [prev] | [next] | [standalone]


#55600

From"(PeteCresswell)" <x@y.Invalid>
Date2018-09-07 11:16 -0400
Message-ID<od55pdpeqabuu1ar7cn4b1tteevs4nudpl@4ax.com>
In reply to#55493
Per VanguardLH:
>What does "a few days of setting up" mean?  That you installed lots of
>apps?

Yes... 

And I will start fooling around with the utilities you suggest.

Also, even so I close all apps and reboot the phone between GeekBench4 runs,
I see substantial (like 7377 vs 6742) diffs with runs only a few minutes
apart.
-- 
Pete Cresswell

[toc] | [prev] | [next] | [standalone]


#55523

FromAnssi Saari <as@sci.fi>
Date2018-09-04 12:06 +0300
Message-ID<vg3zhwxskbe.fsf@coffee.modeemi.fi>
In reply to#55491
"(PeteCresswell)" <x@y.Invalid> writes:

> New Note 4 (N950U1).
>
> Out of the box, GeekBench gave it 7999 on the "Compute"/"RenderScript" test.
>
> After a few days of setting it up, it's down to 7500.
>
> Are there any typical causes of something like this?

Typically phones slow down to produce less heat as they heat up since
you can't exactly speed up the fan for more cooling in a phone.  So
maybe your phone started warmer when you got the lower result?

[toc] | [prev] | [next] | [standalone]


#55601

From"(PeteCresswell)" <x@y.Invalid>
Date2018-09-07 11:19 -0400
Message-ID<0k55pddkj86lm49v6k9019fmobgei2r8jc@4ax.com>
In reply to#55523
Per Anssi Saari:
>Typically phones slow down to produce less heat as they heat up since
>you can't exactly speed up the fan for more cooling in a phone.  So
>maybe your phone started warmer when you got the lower result?

That's a good one.

Next thing I'll try running a test, letting it sit turned fully off for an
hour, and then running another test.

Thought about putting it in the freezer or 'fridge, but that seems like
tempting fate...

Maybe I need to find a utility that tells me the CPU temp and include that in
my results.
-- 
Pete Cresswell

[toc] | [prev] | [standalone]


Back to top | Article view | comp.mobile.android


csiph-web