Does anybody else noticed the huge amount of batterry drain that goes on all day long. I got this phone for about half a year and I think it's worse than before. I'm not the only one with this problem, most of my family got this phone as well and are having the same problem.
In the screenshots you can see how it drained. The screenshots were made after a day of work where I barely used my phone. It seems like it won't get in the Android sleep or Doze.
{
"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 tried several things as hard restting my device and I tried ForceDoze, but all of this didn't work. What can I do?
Stock or custom ROM ?
I got mine yesterday, flashed LineageOS right then..
And I do find battery life extremely poor compared to my older Moto G first gen.
But this might not mean anything for your case though.
matmutant said:
Stock or custom ROM ?
I got mine yesterday, flashed LineageOS right then..
And I do find battery life extremely poor compared to my older Moto G first gen.
But this might not mean anything for your case though.
Click to expand...
Click to collapse
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.
Aaapiie said:
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.
Click to expand...
Click to collapse
As I didn't try stock rom for more than 5 minutes, I have no idea if it is better or worse on Lineage...
Only thing I can say is that I am very disappointed with the battery life, I could get 2 days on my old G where I can only get half one on this device with similar usage...
When I bought it (rushed buy as my G died), I didn't figure that doubling the screen res and and the CPU cores will cut by more than half the battery life with a only 35% bigger battery.
for your specific problem you might try to recalibrate your battery (cf : here)
Stock is not configured the best. It's running in performance mode and not running BigLittle configuration even tho we have slow cores and fast ones. Latest lineage has a BigLittle setup that will help a lot. Battery still not the best tho but way better for sure.
trotter2000 said:
Stock is not configured the best. It's running in performance mode and not running BigLittle configuration even tho we have slow cores and fast ones. Latest lineage has a BigLittle setup that will help a lot. Battery still not the best tho but way better for sure.
Click to expand...
Click to collapse
Are you sure msm8937 really supports big.LITTLE configuration? I can't find it anywhere :\
If I remember well (but I didn't follow SoC dev since msm8926), Qualcomm way of running CPUs was using MPdecision and such to shut down unneeded Cores and work on the minimum needed active cores, instead of having four or eight cores powered at anytime (and at blazing 900-1094MHz -_- )
matmutant said:
Are you sure msm8937 really supports big.LITTLE configuration? I can't find it anywhere :\
If I remember well (but I didn't follow SoC dev since msm8926), Qualcomm way of running CPUs was using MPdecision and such to shut down unneeded Cores and work on the minimum needed active cores, instead of having four or eight cores powered at anytime (and at blazing 900-1094MHz -_- )
Click to expand...
Click to collapse
Well it seems to be working OK. Kernel auditer is showing big.LITTLE. Updated 2 days ago self compiled lineageos. If you set powersave on big you get loads of deeps sleep on the cores. On stock there was never any deep sleep they was always running.
well, that's interesting,
I'll try to investigate a little [no pun intended] more, but at first sight, touching cpu0 freq affects the whole 4 core cluster (0 to 3)
Iv never had any problems with battery
As the screenshot shows - Iv been using my phone pretty much constantly the last 7 hours & Iv still got 7 hours left
So with constant Internet usage as well as spotify/pandora YouTube games etc I get at least 14 hours use out of this phone and normally longer - I only charge once a day
Iv always been using lineageos
TheFixItMan said:
Iv never had any problems with battery
As the screenshot shows - Iv been using my phone pretty much constantly the last 7 hours & Iv still got 7 hours left
So with constant Internet usage as well as spotify/pandora YouTube games etc I get at least 14 hours use out of this phone and normally longer - I only charge once a day
Iv always been using lineageos
Click to expand...
Click to collapse
could you please post a screenshot of cpuZ showing CPU freq when idle?
what I have here, and that looks quite strange to me :
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
960000 1094400 1209600 1248000 1344000 1401000
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_available_frequencies
768000 902400 998400 1094400
which looks to me that the High perf Cores are 0 to 3 and low power ones 4 to 7...
but 4 to 7 seem stuck at 1094400Hz and 0 to 3 are 960000Hz when idle
I would expect that the High perf cores should turn off when idle, and that the low power ones go down to 768000... which would save quite some juice... isn't it?
I'm using LineageOS 14.1 by @wzedlare (lineage-14.1-20171018-UNOFFICIAL-cedric.zip)
matmutant said:
could you please post a screenshot of cpuZ showing CPU freq when idle?
what I have here, and that looks quite strange to me :
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
960000 1094400 1209600 1248000 1344000 1401000
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_available_frequencies
768000 902400 998400 1094400
which looks to me that the High perf Cores are 0 to 3 and low power ones 4 to 7...
but 4 to 7 seem stuck at 1094400Hz and 0 to 3 are 960000Hz when idle
I would expect that the High perf cores should turn off when idle, and that the low power ones go down to 768000... which would save quite some juice... isn't it?
I'm using LineageOS 14.1 by @wzedlare (lineage-14.1-20171018-UNOFFICIAL-cedric.zip)
Click to expand...
Click to collapse
Here are some screenshots
The lowest frequency the kernel is set to run at is 960mhz
You would need a custom kernel to play with the scailing & min frequency
Add screenshot
TheFixItMan said:
Here are some screenshots
The lowest frequency the kernel is set to run at is 960mhz
You would need a custom kernel to play with the scailing & min frequency
Click to expand...
Click to collapse
I understand that the big are good to go with 960MHz as long as they should be off most of the time when idle,
But why the LITTLE cores are at 1GHz wen they could be much lower clocked when nothing is going on xD
from what I can see, it is possible to shutdown one or more core(s) manually :
Code:
echo 0 > /sys/devices/system/cpu/cpu3/online
So I hope we can implement some hotplug driver to save some battery life.
Aaapiie said:
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.
Click to expand...
Click to collapse
Could you please post a screenshot of cpuZ like I did?
I'd like to have an idea of the stock behavior
Sorry to hijack this thread BTW, but that might help more than it seems
matmutant said:
Could you please post a screenshot of cpuZ like I did?
I'd like to have an idea of the stock behavior
Sorry to hijack this thread BTW, but that might help more than it seems
Click to expand...
Click to collapse
No problem at all, thanks for your thoughts.
Here are some screenshots, hope this is what you are looking for (the cpu core values may vary).
At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...
matmutant said:
At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...
Click to expand...
Click to collapse
Sorry for the late response. But what do you mean? You mean the field in the bottom of cpuz? Cuz that is saying interactive
Aaapiie said:
Sorry for the late response. But what do you mean? You mean the field in the bottom of cpuz? Cuz that is saying interactive
Click to expand...
Click to collapse
cpuZ fails to detect the two different clusters and assumes core 1-7 are slave of core 0
If you are rooted, the app "Kernel Adiutor" can tell us more about this by looking at CPU menu, and governor for the LITTLE cluster
Or
Code:
cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
matmutant said:
At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...
Click to expand...
Click to collapse
matmutant said:
cpuZ fails to detect the two different clusters and assumes core 1-7 are slave of core 0
If you are rooted, the app "Kernel Adiutor" can tell us more about this by looking at CPU menu, and governor for the LITTLE cluster
Or
Code:
cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
Click to expand...
Click to collapse
I don't have root access. If I'm right I can run that command using an terminal app like Termux? If so see the result in attachment.
Edit: I think I'll try out lineage os tommorow or on Wednesday and I'll see what happens for the battery
Aaapiie said:
I don't have root access. If I'm right I can run that command using an terminal app like Termux? If so see the result in attachment.
Edit: I think I'll try out lineage os tommorow or on Wednesday and I'll see what happens for the battery
View attachment 4312018
Click to expand...
Click to collapse
At least the governor is properly configured for the 4-7 cluster on stock ROM (that's something that I was starting to doubt about...)
If you ever install LinageOS in the next days (but I hope it will be fixed before) you may need to force the governor of the cluster 4-7 by 'echoing' it to core 4 (of use Kernel Adiutor for that matter)
did you search for any service that could be running in the background all time?
matmutant said:
At least the governor is properly configured for the 4-7 cluster on stock ROM (that's something that I was starting to doubt about...)
If you ever install LinageOS in the next days (but I hope it will be fixed before) you may need to force the governor of the cluster 4-7 by 'echoing' it to core 4 (of use Kernel Adiutor for that matter)
did you search for any service that could be running in the background all time?
Click to expand...
Click to collapse
No I cannot point a finger to a specific app. I've done serveral factory resets, but no success with a clean reset.
Related
Nothing in this post should be considered gospel; These are simply conclusions I've drawn from testing. Everything written here could be (and probably is) very, very wrong!
Click to expand...
Click to collapse
YOU MUST BE ROOTED TO ATTEMPT ANYTHING IN THIS THREAD
I don't take full credit for this, someone posted information about the file I listen to but I can't for the life of me find the post. If someone locates it let me know so I can give credit where it's due!
Detecting the Companion Core
The 5th Core (Companion Core/Low Power - LP - Core) is invisible to the android system and cannot be controlled at the moment. However, the kernel can see the 5th core and can detect whether it's running or not.
This is a simple demonstration of this, nothing particularly interesting or useful yet!
Results with screen ON
{
"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"
}
Results with screen OFF
So yeah, this is why we get such great screen-off battery life!
I know pretty much everything written here is already known I just thought it would be nice to see some proof!
For those of you that want to try this out yourself, make a service that runs in the background that reads from: "/sys/kernel/cluster/active". It will be either "G" or "LP" (G meaning it's running from the normal cores, LP is the Low Power core.)
Interestingly, while the screen is on but nothing much is happening on the device it will constantly switch between G and LP (like in the first screenshot) but when doing CPU intensive tasks it runs as G constantly. When the screen is off, it never switches to G which is giving us the insane screen-off battery life.
Disabling 4 Cores and just running the LP Core!
NOTE: This may not be the case. The phone kinda gets a bit screwy and reports different things. I'm pretty sure this is just the throttle that happens when the CPU hits 90°c but I'm not sure (it's hard to make it hit 90°c!). If anyone knows what else it does please let me know!
WARNING: This can, and most probably will, crash your phone after a while. When running CM9 I even had to reflash the ROM (This hasn't happened on Android Revolution yet). Basically PLEASE make a backup and don't blame me if you mess anything up!
This is a strange one. If you navigate to "/sys/kernel/debug/cpu-tegra" there's a file called 'Throttling'. Changing this file to '1' makes the system throttle CPU usage drastically.
Interestingly though, it also makes the "sys/kernel/cluster/active" file report nothing but 'LP' even when doing tasks, indicating that it's running solely off the LP Core. However, I'm using TegraStats to monitor what's active and what isn't and when throttling is enabled it reports that 'cpu0' is also active, contrary to what the "sys/kernel/cluster/active" file says.
If you apply this mod you will instantly see why I think it's running soley off the LP Core: It makes the phone almost unusable and I wouldn't recommend doing it for any great length of time!
Another wierd thing is that TegraStats also reports that CPU1 activates at random points while the phone stays as slow as ever.
Of course, CPU1 could indeed be active and just throttled to a low clock speed (102mhz is pretty much the average when doing anything. It can go as high as 304 though) but it still doesn't explain the LP Core results.
So, if this is running off only the companion core, what does it mean? Well, you could ultimately gain massive battery improvements. The only problem is, the mod renders the phone unusable as it stands. The throttle would probably need to be modified from kernel source to not be quite as aggressive or something, so not useful at the moment but it has potential
I hope you found this interesting!
Reserved for future info!
Nothing to add, sorry, but very cool.
how to disable lp core.
i need to disable it completly. it has ****ty performance
or maybe you know how to change governor on that core or something with him
kragnegrozor said:
how to disable lp core.
i need to disable it completly. it has ****ty performance
or maybe you know how to change governor on that core or something with him
Click to expand...
Click to collapse
it's not good to disable the core because after that you wont have good standy battery life.....and what do you mean with it has bad performance?
man, newest update in youtube APP uses only 1 core, and this core is this sh****ty fifth one. in 720p films there are stuttering and other sh** sometimes. If you demand something powerful from phone at this time, other 4 cores are ON and video is playing smoothly.
Lolwut? The companion core should only be used once your screen is off or goes into deep sleep. Not for the main system to use or for playing YouTube videos.
Sent from my HTC One X using Tapatalk 2
Well done on bumping a 7 month old thread that obviously isn't relevant any more, guys...
so can somebody tell me how to disable it or change governor? it is for research
kragnegrozor said:
so can somebody tell me how to disable it or change governor? it is for research
Click to expand...
Click to collapse
Try System Tuner or any similar app.
kragnegrozor said:
so can somebody tell me how to disable it or change governor? it is for research
Click to expand...
Click to collapse
neuTrue said:
Try System Tuner or any similar app.
Click to expand...
Click to collapse
no app can disable it until a kernel dev can something do for it ...also nothing else can disable it ...try to search for example for youtube a fix that it will work better ...because the 5th core doesn't work in youtube or other ...youtube is stuttering because of other things not the 5th core
Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.
XxVcVxX said:
Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
No it doesn't.
Sent from my HTC One X using Tapatalk 2
Learn about the topology of tegra3 unit. Different core technology, Different performance.
Wysyłane z mojego HTC One X za pomocą Tapatalk 2
XxVcVxX said:
Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
it has only 500 mhz and it will be used for apps which wont take much or if the screen is off/deep sleep...it wont be used in apps like youtube and other ...
like messaging/sms app or e-mail or so
One-X-master said:
it has only 500 mhz and it will be used for apps which wont take much or if the screen is off/deep sleep...it wont be used in apps like youtube and other ...
like messaging/sms app or e-mail or so
Click to expand...
Click to collapse
It has the exact same performance.
It's still ARM Cortex A9, only manufactured with low power silicon. It doesn't scale well into high clock speeds so thus its limited to 500 MHz, but it still has the same performance at same frequency.
Sent from my faster than SGS3 HOX.
XxVcVxX said:
It has the exact same performance.
It's still ARM Cortex A9, only manufactured with low power silicon. It doesn't scale well into high clock speeds so thus its limited to 500 MHz, but it still has the same performance at same frequency.
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
yes but it it isn't working while apps like youtube I have no problems when i use youtube he also had to write which kernel he use because some of the custom kernels or the stock don't know what it was have problems in some apps also figuered that out i had also with a kernel problems in youtube in other no problems...but don't know which because i don't have the phone here because of the f*cking repair center...
i am using kernels
,doing some research about performance.
Just some observations for now
i am need to know how to disable it.
Got some knowledge from many other phones\kernels\roms
But here is tegra3 topology
kragnegrozor said:
i am using kernels
,doing some research about performance.
Just some observations for now
i am need to know how to disable it.
Got some knowledge from many other phones\kernels\roms
But here is tegra3 topology
Click to expand...
Click to collapse
you know that EVERY android build has kernels because without they can't work? i meant with stock kernel that's the kernel in the stock RUU/ rom and custom kernels were edited by devs like faux etc...you CAN'T disable it try to ask a kernel dev you can see them in original development thread but like i know it's impossible because the 5th is for android unvisible ^^
i am gonna think about that.
i am seen somewhere OCed 5th core. Gonna find where and ask in that kernel thread.
thanks
This doesn't represent real-world use. This is an extreme example of how long you can make the battery last by severely throttling the CPU!
I posted another thread about the method used to apply this mod (you can find it here) but I made this thread to concentrate purely on the side effect of it, which is insanely good battery life. Firstly, I'd just like to make this point clear: I would not recommend doing this mod. It makes your device get pretty screwy and renders it fairly unusable. It needs further development before it can be useful.
Yes, this mod gives you absolutely incredible battery life but it only does so by severely limiting the CPU speed and limiting the CPU to a single core (It might even just run off the companion core and nothing else. I've had conflicting results) which makes the phone insanely laggy. I believe, however, that this throttling could be made less aggressive and then toggled on and off at will. From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life (which is already pretty amazing). This isn't definite though and needs more tests
Anyway, less chit-chat, here are my results:
{
"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"
}
That's right, 12 hours and 35 minutes screen-on time!
It would probably last about 4 or 5 days if the screen was off!
ROM: Android Revolution HD
Kernel: stock ARHD kernel
Screen on lowest brightness
No other modifications (apart from the throttling mod)
"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone
SartoriXX said:
"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone
Click to expand...
Click to collapse
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Might aswell do that!
I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.
Meltus said:
I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.
Click to expand...
Click to collapse
I think it sounds awesome and happy to see people like you try to developing the power consumption!
Sent from my HTC One X using Tapatalk 2
sure beats my battery life with only 30 minutes screen on time
ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse
ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse
Comments like that are a complete waste, if they are on to something you should be more encouraging.
Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get
I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.
lamenramen said:
I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.
Click to expand...
Click to collapse
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA
Meltus said:
Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get
Click to expand...
Click to collapse
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium
Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.
punyategar said:
Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.
Click to expand...
Click to collapse
The hox has 5 cores, 4 main cores and 1 super low power core.
What this does is turn off the main cores and run on the super low power core which is great for battery life but it only goes to 500 MHz and in respect to CPUs is slower at processing stuff then almost all CPUs price you pay for power saving.
Sent from my HTC One X using xda premium
Applaud your investigations, so many Haters on this forum!
This phone has masses of potential for some awesome custom Roms (and even a decent official Rom if HTC ever sort themselves out!). Battery life pretty much whole day for me but improvements always welcome.
xchasa said:
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
He is probably talking screen-on time. 4-5 Hours screentime is great, unfortunately you do not fall under the average hours of screen-on time. The average time would be anywhere between 2 and a half to 3 and a half hours.
Which in my opinion is nothing special, admittedly, it does get me through a day but hey! I wouldn't mind having more screen-on time. If 4-5 hours screen on time was the average than you wouldn't see many if anyone complaining at all.
Good day!
treebill said:
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium
Click to expand...
Click to collapse
Ah, that makes more sense
So, were you able to get the 'throttle' file to stick to anything but '1'?
I noticed the throttle_table and tried to use a few of them but they all just defaulted to 1.
It's a shame the 'throttle_table' file isn't editable too, that would make modifying it so much easier!
My first test failed miserably I'm afraid, I forgot to turn off an alarm and it rang out for about 3 hours and then ran out of battery! I'll remember to turn off the alarm next time
Bloody good effort. Despite the idiotic comments from those who clearly haven't grasped the idea behind this, it's impressive homework.
Research like this can only help improve custom-ROM's, which is kinda the point of XDA Dev's, no?
I think some people should focus on the comments section of sites like Engadget, where their funny pictures will be much better suited.
In this thread we will discuss governors.
Primarily differences between ondemand and conservative based ones. This thread was created because ktoonsez made a hotpluging conservative governor. ... perhaps this needs explanation for the general community, that will imo prove the vast superiority of conservative based governors. First here is a link about governors in general it is sort of abridged but, covers allot of governors http://blog.g4team.com/?p=5519
As you can see it makes mention that most of these governors are similar to ondemand. So outlining the major differences. Ondemand scales to the highest frequency as soon as a load occurs. Conservative scales upward based on the frequency step variable which means for the most part will scale through every frequency to achieve the target load thresholds. What this practically means is ondemand is prone to wasting power on unneeded clock cycles. Ondemand also features something called a down differential, this variable determines how long the governor will remain at the given frequency before scaling down. Conservative does not have this, but instead relies on having a down threshold which insures that as soon as the load drops below a given variable it scales down as fast as the sampling rate allows. The result to this is a governor which attempts to keep the load level tolerable and save you battery! Now ! Ktoonservative Is that but in addition contains a hotpluging variable which determines when the second core comes online. The governor shuts the core off when it drops below the hotplug down threshold thus giving us a handle on the second performance factor in our CPUs behavior. While by default conservative is a poor performer it can be made to perform comparably to even performance governor. Here are some settings to discuss and start with. They are slightly less battery friendly under a load but very very well performing.
after realizing just everything mpdecision does i recommend turning it off for this govenor to work properly "stop mpdecision" in the terminal should do. it not only allows for things like benchmarks to lock frequency but generally will disturb these settings under a load, it will do something completely different. so when i turned it off i discovered the govenor behaving differently....more over exactly as you would expect this also meant with some ideas from mw86 that we dont really need touch booster. id recommend the first set of settings and use the last if you want mpdecision on. despite looking less aggressive for battery savings they usually will be with the absence of mpdecision
SAMPLING_RATE="15000"
UP_THRESHOLD="67"
DOWN_THRESHOLD="47"
FREQ_STEP="3"
SAMPLING_DOWN_FACTOR="1"
IGNORE_NICE_LOAD="0"
UP_THRESHOLD_HOTPLUG="85"
DOWN_THRESHOLD_HOTPLUG="33"
SAMPLING_RATE="40000"
UP_THRESHOLD="67"
DOWN_THRESHOLD="52"
FREQ_STEP="5"
SAMPLING_DOWN_FACTOR="1"
IGNORE_NICE_LOAD="0"
UP_THRESHOLD_HOTPLUG="68"
DOWN_THRESHOLD_HOTPLUG="40"
And here is the link for the kernel containing such http://forum.xda-developers.com/showthread.php?t=1800576
A further edit for jb builds most benchmarks are niced so you must turn off ignore nice load to test settings with them
Sent from my SPH-L710 using Tapatalk 2
The results
{
"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"
}
[/IMG]
Sent from my SPH-L710 using Tapatalk 2
Great post and discussion freecharlesmanson. I'm using your specs above and FREQ_STEP="5" I changed to 1, so it would be more like Lazy governor and save me extra power at the cost of a little lag since it must go through the full frequency scale instead of jumping to target frequency in a step or two. Watching cpu frequency in a graph shows this governor and your tweaks do great at being conservative but with power ready to be tapped. For frequency step at 1 im seeing stuff that ramped up in no time takes a half a sec more due to the frequency ladder it must climb... but I'm hoping it will mean it only uses high frequencies when its been under load for quite some time and not just from a basic background task I may care little about the speed in which its completed. Battery life is through the roof with this governor and Ktoonsez Kernel.
edit: if i set down threshold to 60 does it save more power without a lot of complications or does it cause large hiccups or uneeded frequency changing? would it be better to be near 50, stay at 45 or drop down under to 40-35? i was using your settings in other kernel thread but now using yours here and the rest as mentioned.
mw86 said:
Great post and discussion freecharlesmanson. I'm using your specs above and FREQ_STEP="5" I changed to 1, so it would be more like Lazy governor and save me extra power at the cost of a little lag since it must go through the full frequency scale instead of jumping to target frequency in a step or two. Watching cpu frequency in a graph shows this governor and your tweaks do great at being conservative but with power ready to be tapped. For frequency step at 1 im seeing stuff that ramped up in no time takes a half a sec more due to the frequency ladder it must climb... but I'm hoping it will mean it only uses high frequencies when its been under load for quite some time and not just from a basic background task I may care little about the speed in which its completed. Battery life is through the roof with this governor and Ktoonsez Kernel.
Click to expand...
Click to collapse
Yep if you can deal with the lag it will do the trick . You could try to slightly raise that number and just raise the up threshold and hot plug threshold allot like 85 up and 80 hotplug. Then raise the freq step to 2 or three maybe it might give a similar result by discouraging up scaling thru the demand end but would allow quicker scaling ever so slightly with less likelihood of jumping steps. By my math each freq step represents 4.3% total available scaling
Sent from my SPH-L710 using Tapatalk 2
Great work on this, appreciate you taking the time to explain it all!
Sent from my SPH-L710 using xda app-developers app
I can't stand any form of lag! Complete smoothness is the way to be
Sent from my SPH-L710
Lol if you're lagging using conservative with your shiny S4, you're doing it wrong.
I've used conservative exclusively over ondemand ever since root was achieved with my Epic4g which uses the 1ghz hummingbird processor and there's no lag...
I now use smartassv2...seems to give even faster performance and shuts things down quicker than conservative!
Sent from my SPH-D700 using xda app-developers app
A_Flying_Fox said:
Lol if you're lagging using conservative with your shiny S4, you're doing it wrong.
I've used conservative exclusively over ondemand ever since root was achieved with my Epic4g which uses the 1ghz hummingbird processor and there's no lag...
I now use smartassv2...seems to give even faster performance and shuts things down quicker than conservative!
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Smart ass is based on interactive my issue still falls with load regulation. Most of that it seems like it would race thru frequency more. Which may deliver good performance but if at all it would deliver the same but worse battery
This is how well it works for idle regulation and I should point out smart ass doesn't hotplug so in turn because it cannot regulate the second core most likely results in less efficient scaling and if the second core preempted scaling it offers more performance than scaling right off ,those screens are of it being used alittle before bed then alittle more after I woke up
Sent from my SPH-L710 using Tapatalk 2
Just applied values. So far so good. I was just curious, are you over clocking at all? Would it be safe to run this thing at 2106?
Sent from my SPH-L710 using xda app-developers app
drewmonge said:
Just applied values. So far so good. I was just curious, are you over clocking at all? Would it be safe to run this thing at 2106?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Rofl. Anything over 1.5 is a waste.
Sent from my SPH-L710
drewmonge said:
Just applied values. So far so good. I was just curious, are you over clocking at all? Would it be safe to run this thing at 2106?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Its a governer not voltage settings so I can't see why you'd have a problem
Sent from my SPH-L710 using Tapatalk 2
Custodian said:
Rofl. Anything over 1.5 is a waste.
Sent from my SPH-L710
Click to expand...
Click to collapse
Fantastical.
Sent from my SPH-L710 using xda app-developers app
Freecharles manson I was tinkering more and decided to go in a different direction. can you tell me how this would act theoretically? it seems to do good at no lag and saves power still.
SAMPLING_RATE="13500"
UP_THRESHOLD="49"
DOWN_THRESHOLD="23"
FREQ_STEP="1"
SAMPLING_DOWN_FACTOR="4"
IGNORE_NICE_LOAD="1"
UP_THRESHOLD_HOTPLUG="24"
i chose these because I have a theory on single core load vs dual core load in our multi core setup. Since the governor can be multicore aware... I was thinking about what that means.
dual core cpu 100% load = 1 core 100% and the other. dual core 50% load can mean 1 core is at 100% load and second core 0% or anything in between to 50% on both the cores which is still the same... 50% load of a dual core cpu. So lets just say a rouge app pegs at 100% load regardless of 2nd core status. If we set up threshold or hotplug above 50% it means the load to up the frequency or amount of cores activated must be over the load of having 1 core fully loaded to 100% to activate.. ie one at 100% and the other a little over or vise versa both cores loaded to 51% total atleast. So I want my up threshold for frequency at 50% area so if one core ever loads to 100% it adds a frequency step. At the same time I want my second core to activate not while idle but at any load under the upthreshold. So to still save power i want down threshold just under the load required to activate core 2. So 25% seems like a good number. it is equivalent to a 50%load on one core alone or a balance of 25% load over both cores. So down threshold 1 percent under that so unless load is above that it lowers frequency as needed.
so to make sure its easier for the thresholds to jump in at right time i dropped each measurement 1% so it wouldn't literally need 100% load single core to up the frequency. so thats why i went 49%, 24% and 23%. this way the cpu doesnt often stay at a full load unless needed but ramps up when things take a few to calculate and hopefully finish faster saving juice by using the closest matched speed needed. To save power the frequency step is minumum but by the way thresholds are set it will ramp it up very quickly to whats needed even under light loads. battery life hasnt been too bad set like this over the day.
any thoughts on this and if it will work how I am hoping? I'm not sure the direction i took this for my personal use but my goal is a Conservative on demand governor with good hotplugging and to be sure it doesnt use speeds which are overkill for the task nor underpowered either. lazy Ktoonservative
i played around with the values differently and didn't like having hot plug kick in after frequency increase. i figure as load increases from zero it will stay at lowest speed till 23% then at 24% core 2 will kick in and if that doesn't lower cpu load by time it reaches 49% load it will stay in dual core and go up one cpu step... if load doesnt drop it will continue to add speed and stay in dual core. but as soon as load drops below 49% speed will stay same and then core two will shut off at 24% and either finish the work load at that speed in single core, drop to lowest cpu speed in single core or as needed renenable core two to start process all over and therefore either finishing work load or ramping again while in dual core up in frequency till load once again drops into the threshold ranges.
Custodian and Freecharlesmanson i respect your info and would love to know how accurate this is. I am new to Android as of this year but not new to cpus so if you have advice or feedback for this discussion Id be very appreciative.
So my issue atm is with ES explorer scrolling. It's super choppy.... I'm exploring more values in hopes of finding a sweet spot. I can confirm that the choppiness doesn't exist on ICS but does on asop ROMs. So I'm trying to see what's up now.
Sent from my SPH-L710
mw86 said:
Freecharles manson I was tinkering more and decided to go in a different direction. can you tell me how this would act theoretically? it seems to do good at no lag and saves power still.
SAMPLING_RATE="13500"
UP_THRESHOLD="49"
DOWN_THRESHOLD="23"
FREQ_STEP="1"
SAMPLING_DOWN_FACTOR="4"
IGNORE_NICE_LOAD="1"
UP_THRESHOLD_HOTPLUG="24"
i chose these because I have a theory on single core load vs dual core load in our multi core setup. Since the governor can be multicore aware... I was thinking about what that means.
dual core cpu 100% load = 1 core 100% and the other. dual core 50% load can mean 1 core is at 100% load and second core 0% or anything in between to 50% on both the cores which is still the same... 50% load of a dual core cpu. So lets just say a rouge app pegs at 100% load regardless of 2nd core status. If we set up threshold or hotplug above 50% it means the load to up the frequency or amount of cores activated must be over the load of having 1 core fully loaded to 100% to activate.. ie one at 100% and the other a little over or vise versa both cores loaded to 51% total atleast. So I want my up threshold for frequency at 50% area so if one core ever loads to 100% it adds a frequency step. At the same time I want my second core to activate not while idle but at any load under the upthreshold. So to still save power i want down threshold just under the load required to activate core 2. So 25% seems like a good number. it is equivalent to a 50%load on one core alone or a balance of 25% load over both cores. So down threshold 1 percent under that so unless load is above that it lowers frequency as needed.
so to make sure its easier for the thresholds to jump in at right time i dropped each measurement 1% so it wouldn't literally need 100% load single core to up the frequency. so thats why i went 49%, 24% and 23%. this way the cpu doesnt often stay at a full load unless needed but ramps up when things take a few to calculate and hopefully finish faster saving juice by using the closest matched speed needed. To save power the frequency step is minumum but by the way thresholds are set it will ramp it up very quickly to whats needed even under light loads. battery life hasnt been too bad set like this over the day.
any thoughts on this and if it will work how I am hoping? I'm not sure the direction i took this for my personal use but my goal is a Conservative on demand governor with good hotplugging and to be sure it doesnt use speeds which are overkill for the task nor underpowered either. lazy Ktoonservative
i played around with the values differently and didn't like having hot plug kick in after frequency increase. i figure as load increases from zero it will stay at lowest speed till 23% then at 24% core 2 will kick in and if that doesn't lower cpu load by time it reaches 49% load it will stay in dual core and go up one cpu step... if load doesnt drop it will continue to add speed and stay in dual core. but as soon as load drops below 49% speed will stay same and then core two will shut off at 24% and either finish the work load at that speed in single core, drop to lowest cpu speed in single core or as needed renenable core two to start process all over and therefore either finishing work load or ramping again while in dual core up in frequency till load once again drops into the threshold ranges.
Custodian and Freecharlesmanson i respect your info and would love to know how accurate this is. I am new to Android as of this year but not new to cpus so if you have advice or feedback for this discussion Id be very appreciative.
Click to expand...
Click to collapse
Well I'll explain it this way despite the freq step being low the issue is it will aim to unload the first CPU at 49% which won't take much after that while it will rest eventually because it is still so low on hotplug the second core will be constantly on. The second core offers more performance but much much more battery then slightly increases clock rate the issue is balancing that because so often you either end up with the clock rate racing up wards or the core staying on. . Personally don't take a shot in the dark. Take settings you know work and work towards your idea incrementally recording the changes the CPU time states record I think though not allowing the CPU to shift a full state up will be to major detriment to performance. Per CPU freq state is 4.3% I have found over 80% on available cores causes stuttering . I gave the settings a spin looks like the second core is on a bit much so you'd want to balance that out. But test test test test and let me know
Sent from my SPH-L710 using Tapatalk 2
Custodian said:
So my issue atm is with ES explorer scrolling. It's super choppy.... I'm exploring more values in hopes of finding a sweet spot. I can confirm that the choppiness doesn't exist on ICS but does on asop ROMs. So I'm trying to see what's up now.
Sent from my SPH-L710
Click to expand...
Click to collapse
Running es right now no issues . Sense it exist only on aosp I'm gonna guess it wasn't governor related? Can you confirm the same results running a different governor?
Sent from my SPH-L710 using Tapatalk 2
freecharlesmanson said:
Running es right now no issues . Sense it exist only on aosp I'm gonna guess it wasn't governor related? Can you confirm the same results running a different governor?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
It's not gov related. Tested with performance, ondemand, conservative
Sent from my SPH-L710
---------- Post added at 04:25 AM ---------- Previous post was at 04:20 AM ----------
Meh dunno wtf going on. It's only with ES rxplore.
vm.swappiness = 0
Testing. Just cause. Lol.
Sent from my SPH-L710
Yeah phones don't benefit from swappiness but I'd leave a slight amount just in case you ever approach oom if you have it turned off and you ever hit oom it will kill random possibly important apps or just plain lockup
Unless you go oom though it makes no difference
Swappiness is set to 15% on my desktop and its only using 200kb arbitrarily I might add
Sent from my SPH-L710 using Tapatalk 2
freecharlesmanson said:
Well I'll explain it this way despite the freq step being low the issue is it will aim to unload the first CPU at 49% which won't take much after that while it will rest eventually because it is still so low on hotplug the second core will be constantly on. The second core offers more performance but much much more battery then slightly increases clock rate the issue is balancing that because so often you either end up with the clock rate racing up wards or the core staying on. . Personally don't take a shot in the dark. Take settings you know work and work towards your idea incrementally recording the changes the CPU time states record I think though not allowing the CPU to shift a full state up will be to major detriment to performance. Per CPU freq state is 4.3% I have found over 80% on available cores causes stuttering . I gave the settings a spin looks like the second core is on a bit much so you'd want to balance that out. But test test test test and let me know
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
okay great explanation. It was a good read I'll go back to drawing board test test test and post back with more theory and results when i've come up with something that is working good for me. I'll keep in mind I need Hotplug to not kick in as often nor have cpu frequency shoot up to max so its a balancing act. I appreciate your info thank you. I'm reading as much as i can find on more governors and their adjustments to get ideas from them too like you said to base off an existing one and modify from there.
mw86 said:
okay great explanation. It was a good read I'll go back to drawing board test test test and post back with more theory and results when i've come up with something that is working good for me. I'll keep in mind I need Hotplug to not kick in as often nor have cpu frequency shoot up to max so its a balancing act. I appreciate your info thank you. I'm reading as much as i can find on more governors and their adjustments to get ideas from them too like you said to base off an existing one and modify from there.
Click to expand...
Click to collapse
What you are shooting for is the opposite end of the stick so. Getting the same results off a diametrically opposed idea is awesome keep it up
Sent from my SPH-L710 using Tapatalk 2
Yesterday I bought a Huawei ascend p6 for my wife. Even when holding it in hand, I feel like its design. After a day of use, I feel quite disappointed in its performance. When running the game like candy crush, subway surf, ... I find it does not run smoothly, or say exactly shocked. I wondered if I run the game require higher configuration will how?
According to you, is caused by the configuration of the machine or the rom? Is there any way to solve this problem?
U can try to run it in performance mode.
Sent from my P6-U06 using Tapatalk 2
{
"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"
}
The performance mode just reduces the resolution...
try
try rooting and installing clockworkmod and then flash a rom or install cynogen mod or install game booster on playstore
good luck
hit the thanks button:cyclops:
savio_mascarenhas said:
try rooting and installing clockworkmod and then flash a rom or install cynogen mod or install game booster on playstore
good luck
hit the thanks button:cyclops:
Click to expand...
Click to collapse
there is no clockworkmod until now ...
But which firmware does your phne have?
B104 is not very smoothy, try the official B107 if it is ... good luck
i dont
i dont have a ascend p6 so try to flash a new rom but becareful if you need further help i can help you
hit the thanks button please
good luck tell me if you need help
i have a huawei idoes x5:highfive:
i am an android developer
:laugh:I come from china.now i am in ShenZhen.I have already competly made the customer recovery for Huawei P6.I will upload it soon .Hope you gays enjoy it.
zhenaguo said:
:laugh:I come from china.now i am in ShenZhen.I have already competly made the customer recovery for Huawei P6.I will upload it soon .Hope you gays enjoy it.
Click to expand...
Click to collapse
solve your problem
The cpu and GPU locked in a certain frequency power can be achieved not so serious and fluent game approach.
The first machine to ROOT then RE Manager to set inside the file!
1. Open sys-devices-system-cpu-cpu0-cpufreq-cpuinfo_block_freq, use a text editor to open, modify the value of 600,000 or 800,000 or 700,000 are cpu frequency is locked, save and exit after completion of editing,
2. Locate scaling_cpu_lock_nun, a method using phase inside the 0 modified to 4. It is locked cpu cores. Save and exit editing can! In power management policy settings in a super-power standby.
GPU in accordance with slim post to unlock! But I set 480000 360000.
Heat is also not so great to play the game is very smooth! Power consumption is not serious enough for everyday use heat is also better!
I charge 100% after setting the screen brightness is not open to the minimum WIFI playing whitewater boats two effects 30 minutes of high power consumption 23% is power! But look at the beep beep miles 720 miles to see 24 minutes of animation power at about 7%! Several times hovering at about 7%.
After rebooting modify things will revert to re-edit
zhenaguo said:
The cpu and GPU locked in a certain frequency power can be achieved not so serious and fluent game approach.
The first machine to ROOT then RE Manager to set inside the file!
1. Open sys-devices-system-cpu-cpu0-cpufreq-cpuinfo_block_freq, use a text editor to open, modify the value of 600,000 or 800,000 or 700,000 are cpu frequency is locked, save and exit after completion of editing,
2. Locate scaling_cpu_lock_nun, a method using phase inside the 0 modified to 4. It is locked cpu cores. Save and exit editing can! In power management policy settings in a super-power standby.
GPU in accordance with slim post to unlock! But I set 480000 360000.
Heat is also not so great to play the game is very smooth! Power consumption is not serious enough for everyday use heat is also better!
I charge 100% after setting the screen brightness is not open to the minimum WIFI playing whitewater boats two effects 30 minutes of high power consumption 23% is power! But look at the beep beep miles 720 miles to see 24 minutes of animation power at about 7%! Several times hovering at about 7%.
After rebooting modify things will revert to re-edit
Click to expand...
Click to collapse
Hi there, im not very code technical, From what I can see, have you made the phone not get as hot and gave it better proformance, the only thing thats putting me off buying this phone is that even though it has a snapdragon S4 pro it isnt as good as the Nexus 4 which is cheaper and that it gets way to hot ( someone had a screen shot of the phone getting so hot that asked to close apps )
Many thanks
JackHanAnLG said:
Hi there, im not very code technical, From what I can see, have you made the phone not get as hot and gave it better proformance, the only thing thats putting me off buying this phone is that even though it has a snapdragon S4 pro it isnt as good as the Nexus 4 which is cheaper and that it gets way to hot ( someone had a screen shot of the phone getting so hot that asked to close apps )
Many thanks
Click to expand...
Click to collapse
well... Based on what I know about this phone, the CPU is not a Snapdragon S4 pro but a K3V2E developed by Huawei itself. That might explains the performance issue. Huawei locked the CPU frequency and GPU frequency for power saving reasons, but it locked it too much.
beodenls said:
Yesterday I bought a Huawei ascend p6 for my wife. Even when holding it in hand, I feel like its design. After a day of use, I feel quite disappointed in its performance. When running the game like candy crush, subway surf, ... I find it does not run smoothly, or say exactly shocked. I wondered if I run the game require higher configuration will how?
According to you, is caused by the configuration of the machine or the rom? Is there any way to solve this problem?
Click to expand...
Click to collapse
Yes the solution is go to settings>power manager>select normal
Then go to manage apps>subway surfers>enable the perfomance mode
Hope this helps and tell the results
Sent from my HUAWEI P6-U06 using xda premium
yfnew said:
well... Based on what I know about this phone, the CPU is not a Snapdragon S4 pro but a K3V2E developed by Huawei itself. That might explains the performance issue. Huawei locked the CPU frequency and GPU frequency for power saving reasons, but it locked it too much.
Click to expand...
Click to collapse
No way! How could they lie? Do you think its a Cortex A7? I only ask because the battery life seems pretty good and as far as i know 1.5ghz is the max an A7 can go, also if the performance isnt great, that would be why?
JackHanAnLG said:
No way! How could they lie? Do you think its a Cortex A7? I only ask because the battery life seems pretty good and as far as i know 1.5ghz is the max an A7 can go, also if the performance isnt great, that would be why?
Click to expand...
Click to collapse
Yes, you are right ! The cpu's are cortex A7.
any idea what GPU it has? any info about it?
Immersion. 16, and we got Cortex A9, not 7
Sent from my HUAWEI P6-U06 using xda app-developers app
S34Qu4K3 said:
Immersion. 16, and we got Cortex A9, not 7
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
never heart of that gpu....
no one has any specs list about it?
yeah A9, gsmarena sayed it.
loooks like a cute phone
Hi
Im satisfied with my new P6, but honestly the battery life is very bad. My phone 's been 5 hours on battery, and has 50%. I have disabled Google services, wifi, gps and cleaned background apps. I dont even keep my screen brightness high !
I also get sometimes mobile data lost, i've 3g/h on statusbar, but data is not moving. Going to airplane mode and back makes it work again. This happens few times a day.
I have B106, the build which came with the phone. Should i update to B107 or something else? Im in Finland with Elisa / Saunalahti network and i've heard about connection issues on B107. Is it still better than 106, or is there some other build that i should try?
And have you any info about coming versions from Huawei? Thanks alot
We have in Germany by default B104 and the B107 is much better ... at the moment I have a beta B111 on my phone and that is still better than B107 ... I think there will be better roms soon.
Hope that there will be custom rom possible soon, the test possibility is much better then ...
Find out whats causing the drain. Go to settings-battery(asetukset-akku) and see if there is a program misbehaving. Stopwatch prevents the phone from going to deep sleep and therefore drains lots of power even when the screens off, other programs might do it aswell.
If you get 4-7 hours of screen on time id say that its pretty normal, although i do not play any games that consume loads of power. And i think browsing with wifi consumes less power than mobile data.
Ill try to take some battery stats with syncs, gps and google now on. So youll have something to compare with.
{
"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"
}
...Presents...
Helix Kernel
Features:
- Based on 2.28.617.8 HTC source code
- Various patches/fixes (look in source commits)
- Big cluster overclocked to 2.34GHz + GPU overclocked to 652MHz
- Sched tweaks (task migration tweaks that aim to achieve good performance while maintaining battery life)
Click to expand...
Click to collapse
AFTER INSTALLING:
Because pnpmgr overwrites some of my sched tweaks, 3 tuneables will have to be applied manually via EX Kernel Manager app.
You will have to go into the CPU section then scroll down and tap on "Advanced options" where you see some tunable options. Here is what you will have to change:
sched_upmigrate = 95
sched_upmigrate_min_nice = 0
sched_restrict_cluster_spill = 1
sched_downmigrate = 90
sched_small_wakee_task_load = 5
sched_big_waker_task_load = 30
sched_enable_thread_grouping = 1
AND MAKE SURE TO ENABLE APPLY ON BOOT OPTION AT THE TOP!
Additionally, this kernel works best with ivicask's pnpmgr mode on BALANCED MODE!
Click to expand...
Click to collapse
DOWNLOAD v001
MIRROR
I have not tested this on US variants of the HTC 10, nor on any AOSP-based ROMs so please make a backup of your boot.img before flashing!
SOURCE: https://github.com/ZeroInfinityXDA/HelixKernel_Nougat
Oh yeah, can't wait to get er done. And reserved.
Sent from my HTC 10 using Tapatalk
Whoop... Here we go..
Great kernel dude....
I have not tested this on other US variants of the HTC 10, so please make a backup before flashing!
Sent from my HTC 10 using XDA Labs
Here I go too
Subscribed to the thread already hahaha
Install has been great on US Unlocked variant for me, I'm on Viper 3.5.0 on the ATT network, and so far it's running good.
Sent from my HTC 10 using Tapatalk
HElix FTw whoop whoop
- Big cluster overclocked to 2.34GHz + GPU overclocked to 652MHz like the maximum freq of S821 chip
- Sched tweaks (task migration tweaks that aim to achieve good performance while maintaining battery life)
Click to expand...
Click to collapse
No further overclock on the small cores? Does it get unstable that fast?
And about the Scheduler tweaks, pnpmgr likes to take tasks off the big cores as soon as the phone gets a little bit too hot. Are your tweaks mainly for cold/light usage or work better when the phone is hot/throttling?
Haldi4803 said:
No further overclock on the small cores? Does it get unstable that fast?
And about the Scheduler tweaks, pnpmgr likes to take tasks off the big cores as soon as the phone gets a little bit too hot. Are your tweaks mainly for cold/light usage or work better when the phone is hot/throttling?
Click to expand...
Click to collapse
In order to conserve optimal temps and power consumption, imo the little cluster is best to be left alone and let it do its intended usage rather than be overclocked to 1.7GHz. During experimentation phase, overclocking little cluster to 2.1GHz will simply not get past the splash screen, my guess is that there isn't enough voltage to run it without making tweaks to the voltage table.
My sched tweaks is basically like this: more tasks with slightly higher priority are restricted for little cluster ONLY, meaning they will never be migrated to the big cluster (don't worry, these priority tasks should not be intensive anyway). Additionally, the little cluster has been tweaked to prevent being overloaded easily (lower the threshold for when a task will be spilled to the big cluster. Task migration is triggered faster when the little cluster is about to be overloaded and "spills" some tasks to the big cluster to handle. This should aim for good battery life on normal usage (more non intensive power tasks are strictly handled by little cluster) as well as good performance (tasks which are more intensive is faster spilled onto the big cluster to process, lessen the chance of the little cluster being overloaded before spill initiates.).
Using this with balanced mode pnpmgr tweaks is best, when the cpu gets warmer the pnpmgr will throttle the phone but seeing that the s820 can still perform pretty well under throttling there should be no major performance loss with my tweaks.
I've done gaming endurance tests which achieved a 1 hour endurance on Marvel Future Fight (medium graphics high performance setting in game), around 21-22% battery drain + temperatures were.capped at absolute 40C (sometimes even less!)
Sent from my HTC 10 using XDA Labs
My battery hasn't even had time to fully settle and battery life is surprising me, even with flashing and being in recovery some time today, and telegram running. Nice job @ZeroInfinity
Sent from my HTC 10 using Tapatalk
Flashed 10 mins ago on top if ice rom 2.4, made the 3 changes, must say, it seems very whizzy. Will test over the next few days, Thanks
Sent from my HTC 10 using XDA-Developers mobile app
Just wanted to say I got it booted and running on Verizon 10 on Viper ROM. Will report my experience as I usually run Elite kernel. Thank you for sharing.
nice to see you here with a kernel zero! On day 2 now. US T-Mobile variant running ICE, running great so far and great battery life. Will check back in later =P
Sooo... This just kind of happened. I would have removed some of the variables for better testing but the battery life caught me by surprise, so I have what I have.
Im going to post my battery life yesterday. I wasn't intentionally testing or I wouldn't have had so much extra stuff running. I was just shocked with the usage I had, how well it worked. I was on a road trip last night and streaming YouTube on 4G with the screen on playing HD video, because I don't pay for YouTube red or use the app that allows background play.
Like I said, this was with Google Maps running w/ GPS, Bluetooth connected to stereo, Pandora in background, and streaming YouTube on 4G for about 3 hours of the screen on time, and also had auxillary connected for YouTube streaming so I could use acoustix and boom sound.
Sent from my HTC 10 using Tapatalk
I had to restore the elite kernel, my signal was only showing 1x on Verizon.
LibertyMonger said:
I had to restore the elite kernel, my signal was only showing 1x on Verizon.
Click to expand...
Click to collapse
My signal only shows once. .
How many times do you want to see your signal?
p50kombi said:
My signal only shows once. .
How many times do you want to see your signal?
Click to expand...
Click to collapse
You shouldn't reply to posts you do not understand. Why not just ignore my post and move on? For clarification I am showing 1x on my status bar instead of 4g which means I lost my signal and data. It might be an issue with the Verizon 10's, we'll have to see from other Verizon users experience.
LibertyMonger said:
You shouldn't reply to posts you do not understand. Why not just ignore my post and move on? For clarification I am showing 1x on my status bar instead of 4g which means I lost my signal and data. It might be an issue with the Verizon 10's, we'll have to see from other Verizon users experience.
Click to expand...
Click to collapse
Hmm is it the same with Clean Slate kernel?
Mostafa Wael said:
Hmm is it the same with Clean Slate kernel?
Click to expand...
Click to collapse
not too sure if anything extra needs to be done to make it work on verizon variants, works on AT&T variants though.
Mostafa Wael said:
Hmm is it the same with Clean Slate kernel?
Click to expand...
Click to collapse
No works with Clean Slate but I mostly use elite kernel it seems to work best for me. It may have been just a fluke, I didn't have time to test today cause I was at work I just know I never have that problem, flashed this kernel last night and went to bed not noticing till after I got to work this morning. Hopefully someone else on Verizon can test.