Does anyone know of a way to hotplug or how to enable hotplugging for at least the ls997? The mk2000 v1.1 supposably does but its no where to be found. Is there another kernel that does this for this phone?
Searching has not been very helpful so far.
I even tried the commands, but no luck. I do not the core_ctl file that is mentioned a page or two back.
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330/page10
Mysticblaze347 said:
Does anyone know of a way to hotplug or how to enable hotplugging for at least the ls997? The mk2000 v1.1 supposably does but its no where to be found. Is there another kernel that does this for this phone?
Searching has not been very helpful so far.
I even tried the commands, but no luck. I do not the core_ctl file that is mentioned a page or two back.
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330/page10
Click to expand...
Click to collapse
From what I have read, hot plugging is no longer utilized on modern kernels due to the improvements in the interactive kernels
Sent from my LG-H910 using XDA Labs
cnjax said:
From what I have read, hot plugging is no longer utilized on modern kernels due to the improvements in the interactive kernels
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Seems like it would still be beneficial for battery for CPU's to auto shut off when not needed instead of all cores always running.
Related
"Stumbled" across this article
In my opinion one of the most informative!
http://www.acsyndicate.net/which-cpu-governor-should-you-go-with/
good read. thanks.
Shameless.
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Lol. Troublemaker!
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
What does that mean? lol
qbking77 said:
What does that mean? lol
Click to expand...
Click to collapse
i think because it was a team page it links to. that was my impression.
Sent from my SPH-D700 using xda premium
I was gonna post about this actually very informative. Now I'm using voltage control. What should I set for the I/o scheduler? I tried interactive governor and my phone almost locked up lol. Was using conservative. Just started using ondemand.
Sent from my SPH-D700 using XDA Premium App
Bump
Sent from my SPH-D700 using XDA Premium App
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
nubecoder said:
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
Click to expand...
Click to collapse
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Sent from my SPH-D700 using xda premium
JohnCorleone said:
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Click to expand...
Click to collapse
[The short answer]
If it's working for you, then it's not "bad". ;]
[The much longer than I had expected it to be, other info / opinions on Epic governor related issues, answer]
It's just that the Samsung phones don't have anywhere near the amount of steps as other devices do, and their handling of which step to jump to when asked for freq X is not that great (and becomes more of a problem when frequencies are disabled with tools like setCPU and Voltage Control).
The other big thing is that (in Samsung's code) there isn't any compliance to the cpufreq "scaling_min" setting, it simply uses a clip to make sure it's not below the lowest available freq (ie 100MHz) and doesn't care if it's below the scaling_min. Some phones handle the 100MHz better than others (and the original 100MHz is possibly "broken" when you look at it's divisors).
Note that some do kernels have some changes in place to force the compliance of the scaling_min setting. (I know Genocide does anyway.) (And mine does but it has yet to be released to the wild.)
There's some other things in play as well, like the DVFS lock that can be applied to force the frequency to be a "fixed" freq (as in won't change) or a "high_lock" which is basically "no lower than X".
For example, there is a DVFS lock used any time you touch the touch screen that will not allow the CPU to scale below 800MHz (lock token 6 IIRC). (The lock is lifted when you let go). And Samsung's conservative (IMO transitional) governor uses a fixed lock of 800MHz during sleep (suspend).
I've spent a lot of time trying to figure all of this out and to determine why Samsung's devices (specifically the Epic) simply don't play well with most governors.
I have worked out most of the bugs in my kernel (I wrote a function to handle getting the nearest requested frequency with disabled freqs in mind). But it's still not perfect.
I've considered going full force and adding tons of freqs to see how that works out, but that's a crap-ton of work, and my current goal is to release my kernel before official GB drops.
Hopefully will be over the next few days (but I've been saying that to myself for weeks now it seems).
=]
Can someone please explain to me why none of the kernel's have OC ability?// I think it's due to quad core overheating but I'm not sure and would really love an actual explanation.. Thanks
Sent from my Nexus 4 using xda premium
they all started with OC ability right at the beginning, then .. a good few number of people had HARDWARE bricked devices, that had a fault with the battery no longer being connected or something
they all had overclocking in common, since then , its been removed on most or all kernels
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
zephiK said:
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
italia0101 said:
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
Click to expand...
Click to collapse
Will I certainly don't need it. Would it be nice to have? Yeah but it isn't on the top of my priority list.
What he's saying about mpdecision is true. If you read the change log for Franco kernel he removed mpdecision and is working towards a open platform for kernels. So we should hopefully be seeing more goodies.
Sent from my Nexus 4 using xda premium
Is Faux's kernel the only one at present where you can properly UC all cores and disable cores as necessary?
Also, do any of the current Kernels include the MSM wakelock patches or has everyone reverted due to data drops?
Franco has a few wake lock fixes for sure. I don't believe faux does.
Sent from my Nexus 4 using Tapatalk 2
Why don't you ask in the kernel thread for the kernel you wish to use?
Sent from my Nexus 4 using xda premium
As far as I know you can also use bricked kernel and configure the settings using faux's app.
Sent from my Nexus 4 using Tapatalk 2
The thing I notice is this, the developers don't use use their own stuff they use each others stuff too. For example you might see some of fauxs features in bricked kernel and you might see some of bricked features in other kernels.
Post your results here. Also if you could say what CPU governor you are using, that would be great.
Running vanir with Jassy kernel oced at 1.9 ghz governor ondemand. Runs great so far
Sent from my Nexus 7 using xda app-developers app
Lol sorry here's a better pic without the volume bar
Sent from my Nexus 7 using xda app-developers app
talha746 said:
Post your results here. Also if you could say what CPU governor you are using, that would be great.
Click to expand...
Click to collapse
Personal opinion. I can tell you what I get with mine
http://forum.xda-developers.com/showthread.php?t=2393950
Not another thread like this again. Everyone's device will yield different results. We all use our devices differently. A particular ROM/kernel combo on my device will not yield the same results for someone else. There is no best ROM/kernel combo that is best for battery life. Try out a bunch and find what works for "you".
Sent with "flo"
I would like to know if someone that is running stock ROM with Stock kernel and rooted to check what the governor and governor settings are
So, I have an Amazon ads enabled G4 that I got from a friend. While using CPU-Z I noticed that, at least what the app shows, is that four cores are always on, and two more turn on as needed. While the four that are always on are clocked at 1.21 gHz... We'll call these four "battery efficient" cores, it seems the other two that turn on as needed are clocked at 1.44 gHz or the "power" cores. At least for me, there is a total of four "power" cores but the extra two never come on.
In an attempt to save battery, I turned on the android battery saver on. With this enabled, the "power" cores turn off and do not come on at all. The four "battery efficient" cores stay on and what a difference between battery saver enabled compared to battery saver disabled. I also noticed all of these eight cores to have a minimum speed of 806 MHz.
So, I've been able to achieve over 6 hrs of Screen On Time. I could only dream of when I used my Moto X Pure Edition. I'm trying to figure out why the 808 while based off A53s does not achieve said Screen On Time, while a far inferior processor is able to do this with no problem.
Obviously I cannot root the phone to check it myself. Anyone care to discuss?
Sent from my Moto G (4) using XDA-Developers mobile app
Wanted to see if anyone is willing to share stock governor settings.
Sent from my XT1575 using XDA-Developers mobile app
Just need stock governor settings, from anyone that has an unlocked bootloader and has been able to root this phone.
Sent from my XT1575 using XDA-Developers mobile app
I know it's extremely hard to figure out what the stock governor and its stock settings are, however, I was hoping since we have so many great minds here at XDA that thus would be an attainable request ???
Sent from my XT1575 using XDA-Developers mobile app
So, if you have a rooted moto G4, would be greatly appreciated if you share them stock governor setting and anything related to the kernel
Sent from my XT1575 using XDA-Developers mobile app
cerobles1 said:
So, if you have a rooted moto G4, would be greatly appreciated if you share them stock governor setting and anything related to the kernel
Click to expand...
Click to collapse
I'm not rooted and I can't load the app right now but can't you see the settings even though you can't change them on a non-rooted phone?
I've tried, but I have not found a way or an app that shows the actual governor parameters settings. It only shows what governor is being used. @Tel864 do you know something I don't???
Anyone else that has their g4 rooted please help.
Sent from my XT1575 using XDA-Developers Legacy app
cerobles1 said:
I've tried, but I have not found a way or an app that shows the actual governor parameters settings. It only shows what governor is being used. @Tel864 do you know something I don't???
Anyone else that has their g4 rooted please help.
Sent from my XT1575 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have the Amazon variant rooted and unlocked... what field in what app are you looking for? the Scaling Governer says "Unknown"
bigunwhistle said:
I have the Amazon variant rooted and unlocked... what field in what app are you looking for? the Scaling Governer says "Unknown"
Click to expand...
Click to collapse
@bigunwhistle what I'm referring to is any application that allows you to control the governor. Is it better to siwtch to PM in an attemp to not clutter the thread???