Hello guys,
When using Quadrant and looking at System Information under CPU it says "Cores 1". I tried the same app with Sensation One S and there is shows "Cores 2".
Is there something wrong with one of the cores on my Sensation, or is the app showing something wrong?
What ROM and Kernel are you using?
You could have a Kernel that's not utilizing the 2nd core, thus Quardrant wouldn't recgnize it's there.
Skipjacks said:
What ROM and Kernel are you using?
You could have a Kernel that's not utilizing the 2nd core, thus Quardrant wouldn't recgnize it's there.
Click to expand...
Click to collapse
I'm on stuck ROM 4.0.3.
Both cores on my phone show up on quadrant. Maybe your version needs updated?
Kevc44485 said:
Both cores on my phone show up on quadrant. Maybe your version needs updated?
Click to expand...
Click to collapse
I'm using version 2.0. Even tried to un-install and re-install.
Something is going on here. This morning when I ran the benchmark I got a score of about
2700 with both cores. Now when I run a benchmark I get a score of about 2200 with only one core showing up. Something is definitely wrong.
I'm only getting around 2200 every time. And it shows 1 core only every time...
EDIT:
If I restart my phone (no fast boot) go to System Information then it shows 2 cores.
If I do a Full Benchmark and after that go to System Information again, than it shows 1 core only.
{
"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"
}
There´s nothing wrong with Quadrant showing sometimes 1 core and sometimes 2 cores.
The second core on the Sensation is deactivated, and reactivated when certain thresholds are reached on system load.
Not running on "performance"?!
You guys need to get some sort of app like SetCPU or similar and set your Governor to: Performance THEN do any benchmarks...oh, and of course close any programs running in the background and etc...
Also may want to tweak it up to 1.5 or 1.7 (currently on 1.7) and govern it to be OnDemand or Intellidemand and it'll only crank it up when you need it most.
---------- Post added at 01:29 AM ---------- Previous post was at 01:19 AM ----------
Consistently over 3000 (avg. 3200)...probably could be higher with a different Kernel and stuff but using one that saves on the juice.
NEW version just released:
What's in this version:
v2.1 changes:
Fixed detection of CPU cores on HTC Sensation
Restored the result browser
Related
Hey all,
Any ideas why ROM Toolbox Pro's CPU Control center would not be working on this device? I am running ASUS stock JB ROM, unlocked and rooted with NvFlash access. I have never seen this issue before, even on my TF101. See attached screenshot for what I am talking about.
{
"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"
}
Not only do the sliders and Governor return to this state after setting and returning (attempting to set the max to 1700 [I know there's not much of a purpose, but you will see why in a second] and the Governor to performance), the max GHz seems to be maxed out at 1500 which is very odd.
I tried looking for a kernel that supported overclocking but didn't find any, anyone know if I am just flat out missing something?
Sent from my unlocked Transformer Infinity
I_EAT_BABIES said:
Hey all,
Any ideas why ROM Toolbox Pro's CPU Control center would not be working on this device? I am running ASUS stock JB ROM, unlocked and rooted with NvFlash access. I have never seen this issue before, even on my TF101. See attached screenshot for what I am talking about.
View attachment 1408051
Not only do the sliders and Governor return to this state after setting and returning (attempting to set the max to 1700 [I know there's not much of a purpose, but you will see why in a second] and the Governor to performance), the max GHz seems to be maxed out at 1500 which is very odd.
I tried looking for a kernel that supported overclocking but didn't find any, anyone know if I am just flat out missing something?
Sent from my unlocked Transformer Infinity
Click to expand...
Click to collapse
I have tried a few CPU control apps and most of them are not working too well with JB on tf700. The only one I found that works is SetCPU, it recorded my max/ min and governor perfectly. (1700max and 50min), both settings are working well. Currently, there is no kernel that supported Over clocking.
What do people have for UV settings on CM9 and what tool are they using to set the levels?
Thanks
I use System Tuner Pro. It's worth every penny. Try the free version first. IMO it's the best app for the money. It's actually not showing the value change when you hit the -12.5mv button but if you go back to the home screen then go back to STP it does show the change. I'm running a yet to be released kernel and just haven't had time to look at it yet. I'm UV'd by 100mv across the board. All phones act differently to UV'ing so start with small steps and make sure set on boot is turned off until you find a stable range.
Everyone's phone responds differently to oc/uv. Here are the minimum settings I can use without crashing my phone.
{
"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"
}
I believe cm9 comes with jefe kernel, someone correct me if I'm wrong, which is already undervolted 25mv versus stock. So a 100mv undervolt is technically a 125mv UV.
TrenchKato said:
Everyone's phone responds differently to oc/uv. Here are the minimum settings I can use without crashing my phone.
Click to expand...
Click to collapse
100mhz to 600mhz are stable for you that low? I thought my phone was liked UVing but your phone loves it. lol
hechoen said:
100mhz to 600mhz are stable for you that low? I thought my phone was liked UVing but your phone loves it. lol
Click to expand...
Click to collapse
Yup everything runs fine. I wanted at least -100 on the top end. Lol I must be greedy.
I'm using the following:
1200 1275 -75
1100 1200 -125
1000 1175 -125
0900 1125 -125
0800 1075 -150
0600 1000 -200
0400 0925 -150
0200 0825 -175
0100 0825 -150
That's as low as I can go with everything staying stable. I CAN drop them by 25... but sometimes it will crash. I generally stick with 1100-200 since I don't really need the extra bit of 1200 and it's a major battery bump.
Thanks for the info everyone
Thanks for the information everyone.
Hello all,
I'm hoping someone can help me figure out what exactly is causing these issues as I've tried all sorts and I can't figure it out.
I'm getting battery drain via android OS (kworker process according to BBS) and I don't know what's causing it. I've attached some screen shots to highlight the problem;
{
"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"
}
As you can see my phone isn't even awake according to the battery summary screen.
Does anyone know what could be causing this? Or how I can figure out what (app?) is using the kworker process?
I've restored my phone to stock, clean flashed mahdi and installed an earlier version of AK kernel (v068) that I know for certain I didn't have these issues on. However, I'm still getting the issue on a setup I know for certain I wasn't having any issues on a couple of weeks ago.
I've also tried restoring a nandroid from a few weeks ago that I know for certain didn't have any issues (I keep a backlog of 5 previous nandroids each time I update my kernel etc to try and ensure I always have 1 stable version) but I'm still getting the issue on that too.
Thanks for any advice/suggestions.
Anyone? It's driving me crazy! Haha
I'm still getting decent battery life despite this process error, it's just before this I was averaging 0.2% per hour while idle, I'm now averaging 0.6%
Should I be looking for an app as a culprit or is it the kernel/rom or something else completely? I'm guessing it's not the kernel/rom as I've ran this setup before without issues, but what I have managed to find on the kworker process online is that it's kernel related. :s
Just for information for anyone who finds this thread after having similar issues, I've solved it, I still have some kworker CPU time but that's to be expected - its MUCH lower than it was in the screenshots above.
One of or all of the following reduced my kworker process CPU times to a reasonable amount.
Set Wifi Ip address to static rather than dhcp on home network
Changed CPU governor from smartmax to intellimm (ak kernel)
Disabled all services in "Google play services" containing "location.reporting"
Powered by Bacon
Hi guys. Can you post your antutu benchmarks here from 1st run 2nd and third consequently. I get 170k, 120k, and 110k in performance mode. Do you guys have these scores?
My results have varied from 105k to 155k ...
169k, exynos variant
{
"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 SM-G950F using XDA-Developers Legacy app
1: 171k (first seperate one)
3 each after each other:
2: 174k
3: 173k
4: 174k
177k on all 3 runs
three times in a row over 180k
Sent from my SM-G950F using XDA-Developers Legacy app
1. 170717 S8 exynos
2. 16981 S8 exynos
3. 171001 S8 exynos
172k to 173k
All stock. Non root. S8 exynos.
Which is the best settings mode to run benchmark (game mode, balanced...)?
high performance mod
Sent from my SM-G950F using XDA-Developers Legacy app
173k
stock non root Exynos.
Jesse Kernel 176k
gilad215 said:
Jesse Kernel 176k
Click to expand...
Click to collapse
175K Exynos
...
berkut_g said:
My results have varied from 105k to 155k ...
Click to expand...
Click to collapse
it's crap score for a s8 a s7 will do 139000 so ....Romanian s8's are a crap
I did have experience with this phones from the past
did had a s7 rom only problems switch to s7 xef france no problems
Europe east only untested phone for countries like (ro,bg,ukraine, checz)
Easy 188k on Singapore's S8 with a Bin 1 CPU... LOL
No settings modified.
kennyggg said:
Hi guys. Can you post your antutu benchmarks here from 1st run 2nd and third consequently. I get 170k, 120k, and 110k in performance mode. Do you guys have these scores?
Click to expand...
Click to collapse
Yes i get 172k on 1st run after root and renovate ice rom
Menoobone said:
185k on Singapore's S8 with a Bin 1 CPU... LOL
Click to expand...
Click to collapse
actually the lower binning doesnt mean the bad 1, it gv more power to cpu and your cpu could perform better with more power.
PS: cpu binning process is based on batch, samsung not going to test it 1 by 1, maybe yours is a good cpu with lower binning batch and get more power, perform better. LOL
Here is the definitive solution for those suffering from low SOT and battery drain after updating to Android 10
a) 30 min video playback on mxplayer (720p movie)
{
"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"
}
b)20 min web browsing on chrome (news articles and embedded media playback)
c)20 min web browsing on Opera mini(scrolling through forum)
So the real culprit for low SOT is poorly optimised/developed app (in my case opera mini)
--Conclusion--
1)Android 10.3.0 kernel does have reduced 'target load' (hope it might get restored to stock 90% in 10.3.1){as evidenced by checking kernel perameters and behaviour along with terminal emulator for ram usage_under root}
2)Some apps are getting released unoptimized for Android 10,they are exploiting poorly designed or rather I would say performance tuned kernels and are draining battery.
3)Battery optimization of OnePlus software won't work for such an app coz whenever it runs,either in foreground or background it will drain battery
--Solution--
1)Install an app which shows cpu states {the one I used is Ex kernel manager,it's a paid app and i use it to tweak kernel whenever i decide to root my phone,but there are free apps on playstore that offer battery stats functionality for free,download one and make sure the stats shown are that of Gold(big cluster) 825Mhz - 2803Mhz and not Silver(little cluster)}
2)Run the apps you regularly use one after another for atleast 20 min and check cpu stats before and after.
3)You will find app making cpu to run at 2.8Ghz,stop using it and find an alternative,if you can't avoid using it then hope either the app's or oneplus's next update fixes it.
Agreed, as we discussed in another thread. Since then i've seen multiple people talk about the stock kernel shooting up to high frequencies way too fast.
Wouldn't reducing the target load via EX Kernel Manager be possible ? I don't remember if the stock kernel exposes these settings in the app.