Hi, sorry for posting this thread as I don't have a Galaxy S Advance, only Ace II, but planning to buy Galaxy S Advance next two weeks and will flash JB via Odin. Anyway, a few number of people are experiencing lags after updating to JB. In GB, we used to modify the egl.cfg and remove the line "0 0 android" and that leaves only the line "0 1 mali". In Ace 2 and Galaxy S Advance GB firmware, there is no "0 0 android" line and by default uses the Mali GPU as the default renderer for 2d and 3d operations. Anyone tried modifying the egl.cfg file? Or atleast tick the "Force 2D GPU Rendering" in the development section in settings and see if there is any difference? Thanks!
EDIT: here's a screenshot of the egl.cfg:LINK
EDIT: the screenshot I posted "was" from the I9070 JB firmware and I "saw" that there was a "0 0 android" line on the egl.cfg. GB firmware doesn't have that line and I didn't know why Sammy added CPU rendering on their JB firmware for SGSA...
kevincaja said:
Hi, sorry for posting this thread as I don't have a Galaxy S Advance, only Ace II, but planning to buy Galaxy S Advance next two weeks and will flash JB via Odin. Anyway, a few number of people are experiencing lags after updating to JB. In GB, we used to modify the egl.cfg and remove the line "0 0 android" and that leaves only the line "0 1 mali". In Ace 2 and Galaxy S Advance GB firmware, there is no "0 0 android" line and by default uses the Mali GPU as the default renderer for 2d and 3d operations. Anyone tried modifying the egl.cfg file? Or atleast tick the "Force 2D GPU Rendering" in the development section in settings and see if there is any difference? Thanks!
EDIT: here's a screenshot of the egl.cfg:LINK
Click to expand...
Click to collapse
Why would you even want that? The mali 400 is powerful enough to handle 2d as well as 3d rendering!
That forcing the cpu to render was used in old adreno gpus which were not efficient. Later this method was busted and declared fake ( removing that lines) .!!
Sent from my GT-I9070 using xda premium
Shaaan said:
Why would you even want that? The mali 400 is powerful enough to handle 2d as well as 3d rendering!
That forcing the cpu to render was used in old adreno gpus which were not efficient. Later this method was busted and declared fake ( removing that lines) .!!
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
You didn't get me do you? I said, by default the CPU rendering was enabled on the SGSA JB firmware, what I mean is a few users are experiencing LAG on games and UI, now since your a developer and I know you rooted you galaxy s advance, please do check your egl.cfg and you'll see that you have that "0 0 android" line...
I'm suggesting SGSA users with JB to test and remove the "0 0 android" line and see if that makes any difference or not to the UI and games.
EDIT: I didn't know why Sammy added that "0 0 android" on the egl.cfg on JB firmware for SGSA. But in gingerbread you'll only see "0 1 mali".
kevincaja said:
You didn't get me do you? I said, by default the CPU rendering was enabled on the SGSA JB firmware, what I mean is a few users are experiencing LAG on games and UI, now since your a developer and I know you rooted you galaxy s advance, please do check your egl.cfg and you'll see that you have that "0 0 android" line...
I'm suggesting SGSA users with JB to test and remove the "0 0 android" line and see if that makes any difference or not to the UI and games.
EDIT: I didn't know why Sammy added that "0 0 android" on the egl.cfg on JB firmware for SGSA. But in gingerbread you'll only see "0 1 mali".
Click to expand...
Click to collapse
Removing those lines might just force the device to render via cpu. It might even cause a device boot loop.
And how in the world is cpu rendering better than the mali 400?
As far as the lag is concerned, it is present for some time. Few hours max. Even i had it initially. It goes away as you configure the device!
Sent from my GT-I9070 using xda premium
Shaaan said:
Removing those lines might just force the device to render via cpu. It might even cause a device boot loop.
And how in the world is cpu rendering better than the mali 400?
As far as the lag is concerned, it is present for some time. Few hours max. Even i had it initially. It goes away as you configure the device!
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
"And how in the world is cpu rendering better than the mali 400?"
did I ever say something like that?
"Removing those lines might just force the device to render via cpu"
wait removing "0 0 android" line will force CPU rendering? seriously?
EDIT: I was only asking for people/devs or some users to remove "0 0 android" and test if their will be a difference? As Sammy added that line to the egl.cfg by default to the JB firmware for SGSA.
SOURCE; https://groups.google.com/forum/?fromgroups=#!topic/android-platform/ra4_l5_m90E
egl.cfg is located in file-system's relevant subdirectory on your emulator or device;
"0 0 android" show that your system uses software render;
If there is a GPU on your device, "0 1 vendor" should be added, example: "0 1 mali200"
If there is a "0 0 android" it uses software render.
I will try it, if it cause bootloops, am i able to change it back?
yooouuri said:
SOURCE; https://groups.google.com/forum/?fromgroups=#!topic/android-platform/ra4_l5_m90E
egl.cfg is located in file-system's relevant subdirectory on your emulator or device;
"0 0 android" show that your system uses software render;
If there is a GPU on your device, "0 1 vendor" should be added, example: "0 1 mali200"
If there is a "0 0 android" it uses software render.
I will try it, if it cause bootloops, am i able to change it back?
Click to expand...
Click to collapse
incase of bootloops just reflash the JB firmware via Odin again, data and settings are not lost, though you need to re-apply root again.
I wonder why Sammy decided to enable CPU rendering on their JB firmware for SGSA...
Anyway, you can also tick "Force 2D GPU rendering" on the development section on settings just to be on the safe side and run some benchmarks it that makes any difference on UI and games. Thanks!
yooouuri said:
SOURCE; https://groups.google.com/forum/?fromgroups=#!topic/android-platform/ra4_l5_m90E
egl.cfg is located in file-system's relevant subdirectory on your emulator or device;
"0 0 android" show that your system uses software render;
If there is a GPU on your device, "0 1 vendor" should be added, example: "0 1 mali200"
If there is a "0 0 android" it uses software render.
I will try it, if it cause bootloops, am i able to change it back?
Click to expand...
Click to collapse
Isn't it how its written there?
Code:
0 0 android
0 1 mali
shut_down said:
Isn't it how its written there?
Code:
0 0 android
0 1 mali
Click to expand...
Click to collapse
it means CPU rendering is enabled,
removing the "0 0 android" line disables CPU rendering.
EDIT: that setting basically disables hardware rendering and substitute software rendering. The reason is why?
CPU rendering enabled:
Code:
0 0 android
0 1 mali
CPU rendering disabled:
Code:
0 1 mali
or
Code:
1 1 android
0 1 mali
kevincaja said:
incase of bootloops just reflash the JB firmware via Odin again, data and settings are not lost, though you need to re-apply root again.
I wonder why Sammy decided to enable CPU rendering on their JB firmware for SGSA...
Anyway, you can also tick "Force 2D GPU rendering" on the development section on settings just to be on the safe side and run some benchmarks it that makes any difference on UI and games. Thanks!
Click to expand...
Click to collapse
So basically you are asking why sammy enabled cpu rendering ?
Check the build.prop
Shaaan said:
So basically you are asking why sammy enabled cpu rendering ?
Check the build.prop
Click to expand...
Click to collapse
In the build.prop i add the line; video.accelerate.hw=1
Antutu score increast and i have no lag in the UI anymore.
debug.sf.hw=1
GPU render UI
XianHuen said:
debug.sf.hw=1
GPU render UI
Click to expand...
Click to collapse
that exist in gingerbread for the SGSA too, which doesn't make sense since the gingerbread rom for the galaxy s advance has only 0 1 mali in the egl.cfg...
but there is something below that line related to EGL called "debug.hwui.render_dirty_regions", which has a value of false.
any ideas why it is in JB for SGSA?
last time I saw that line in build.prop was to solved the blurred notification icons...
EDIT: here's the link about the debug.hwui.render_dirty_regions": LINK
Code:
Turn on to only refresh the parts of the screen that need updating.
When turned on the property defined by
RENDER_DIRTY_REGIONS_PROPERTY must also have the value "true".
65
66 public static final boolean RENDER_DIRTY_REGIONS = true;
System property used to enable or disable dirty regions invalidation.
This property is only queried if RENDER_DIRTY_REGIONS is true.
The default value of this property is assumed to be true.
Possible values: "true", to enable partial invalidates "false",
to disable partial invalidates
76
77 static final String RENDER_DIRTY_REGIONS_PROPERTY = "debug.hwui.render_dirty_regions";
# debug.sf.hw=0 Use b2r2 as compositor in SurfaceFlinger
# debug.sf.hw=1 Use Mali as compositor in SurfaceFlinger
debug.sf.hw=1
# Android defaults EGL preserved swap behaviour
# This gives bad performace for deferred renderers
# such as Mali.
debug.hwui.render_dirty_regions=false
Sent from my GT-I9070 using xda app-developers app
frapeti said:
# debug.sf.hw=0 Use b2r2 as compositor in SurfaceFlinger
# debug.sf.hw=1 Use Mali as compositor in SurfaceFlinger
debug.sf.hw=1
# Android defaults EGL preserved swap behaviour
# This gives bad performace for deferred renderers
# such as Mali.
debug.hwui.render_dirty_regions=false
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
still doesn't make sense since, that was already included in the gingerbread ROM of the samsung galaxy s advance, and it has no "0 0 android" line in the egl.cfg file...
anyway, has anyone tried removing the line "0 0 android" in the egl.cfg from the JellyBean ROM for Galaxy S Advance?
*facepalm* Enable it or not , it's your choice .
I didn't notice any performance reduction/increase be it enabling or disabling .
I would like to tell you that a GPU is always better at graphics than a CPU , especially something like Mali .
Sent from a Motorola Defy
Apps that are build to use GPU rendering won't even use CPU rendering right?
Isn't that the whole reason behind Project Butter, to let the GPU do the job.
Older apps that didn't properly implement GPU rendering will will need CPU rendering and will sometimes benefit from the 'Force 2D GPU Rendering' in the developer options.
Apps still pick what rendering they need, unless it's overwritten with the Force GPU rendering tickbox.
Some apps (example: AndroidVNC) won't even work properly with forced GPU rendering so this isn't option you wan't to set as default.
Anyway, after setting up JB on the i9070 it runs smoother then it did ever before on GB.
CallMeVentus said:
*facepalm* Enable it or not , it's your choice .
I didn't notice any performance reduction/increase be it enabling or disabling .
I would like to tell you that a GPU is always better at graphics than a CPU , especially something like Mali .
Sent from a Motorola Defy
Click to expand...
Click to collapse
I know GPU is better than CPU but why did samsung let the CPU as the default renderer JB? instead of making the Mali GPU as the default renderer?
cause the JB firmware in SGSA you'll see that line 0 0 android above the 0 1 Mali which causes android to use the CPU as the default renderer.
in the GB firmware, Mali GPU is the default renderer! and you'll see that the CPU renderer is disabled and will only be called IF NEEDED!
I'm only asking WHY? I'm not saying anything about which better! I'm not a noob seriously!
kevincaja said:
I know GPU is better than CPU but why did samsung let the CPU as the default renderer JB? instead of making the Mali GPU as the default renderer?
cause the JB firmware in SGSA you'll see that line 0 0 android above the 0 1 Mali which causes android to use the CPU as the default renderer.
in the GB firmware, Mali GPU is the default renderer! and you'll see that the CPU renderer is disabled and will only be called IF NEEDED!
I'm only asking WHY? I'm not saying anything about which better! I'm not a noob seriously!
Click to expand...
Click to collapse
Maybe this is having something with that? After checking that my phone is a lot smoother.
{
"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"
}
shut_down said:
Maybe this is having something with that? After checking that my phone is a lot smoother.
View attachment 1635253
Click to expand...
Click to collapse
Finally! Thanks! so its now confirmed that we can force or disable CPU rendering, the only weird thing is why Samsung set the CPU as default renderer...
so i can assume that it is safe to remove "0 0 android" on the egl.cfg file...
Related
{
"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"
}
SysTune
Optimize under the hood of your system!
** Root Rights required!!! **
This is a system tuning and tweaking tool for advanced users with root access. It allows you to change various system settings to optimize your system.
This is my very first App on the Market. I am open for feedback and try at my best to solve any requests if possible.
It is very advised to properly inform yourself about those settings as i do not take any responsability for any damamge to your device.
NEW FEATURE
Changing priority of processes allows you to prevent lagging or other issues e.g. when a back ground process slow down your phone or you forground app has struggles to do its fluently.
See Help Tab for more informations before using this feature! More Informations and a small Guide will be available in the second or third post in the next days.
Note: The background service for monitoring processes to renice them causes no increased battery drain!
Features:
Changing min/max CPU frequency
Changing cpu governor
Changing advanced governor settings
Voltage Control (SVS and HAVS supported)
Block device settings like IO-Scheduler
Kernel (Scheduler) Tweaks
VM Tweaks
Changing priorities of active processes (renice)
Apply on Boot
Mulit-Core / -CPU support
Realtime CPU Clock Speed and "Time in State"-View of each Core/CPU
Save and load settings individually for each tab (press Menu).
Multi-Core/-CPU supporting CPU Stress Test (New)
Safe Mode ( see in-app Help for Informations )
..... more to come!
NOTE: The availability of the features depends on your system. E.g. if your installed kernel does not provide access to VDD Levels voltage control than it won't be available.
After installation take your time and read the informations on the Help-Tab.
Download on Market
************************************************
If somethings is not working as expected on your device
please post here or email me so that i can fix it for you!
I don't own every device out there
************************************************
The zip file for toggling Safe Mode that can be saved on your SD Card via the button in SysTune can also be found here attached to this post.
Thanks to...
Grzesiek Baran for the new Market Feature Image and his Status Bar Icons!
"The Unknown Noob" aka Daniel S. for his Status Bar Icons!
Download User Settings
This is a section with user contributed settings files for SysTune. Anyone can submit their settings via attachment to a post.
Though i beg to follow some basic rules:
Tell which device, rom (version) and Kernel used
IMPORTANT: Date (and optinal a version number) of your settings. So we now if there was a modification meanwhile!
Short but clear explenation why you use this values
What you did to come to the conclusion to use them
[OPTIONAL] What you changed over the default values of your rom/kernel. (note which were the default values before the change!)
Please follow the rules to make it easier for others to judge if your settings are usefull for them.
A user's settings for CM 10.1 for DHD rom:
Device: Desire HD, Rom: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series - nightly from 20.02.2013
Date: Feb., 20, 2013
No renicing used anymore
Using stock clocks and ondemand governor.
Ondemand Governor settings
Misc settings
A user's settings:
Device: Desire HD, Rom: SCI MIUI 1.11.25v1.0, Kernel: lordmod 8.5 cfs
Date: Nov., 30, 2011
Smoother and more battery friendly then default values.
I am using several benchmark apps to test different aspects. Also i am testing overall daily usage. For reliable tests i have some things i repeat to see how the impact of changes of the settings is. Benchmarks used are: NenaMark 2, An3DBenchXL, Quadrant (not very good though), AnTuTu, TAP Benchmark (for internal flash memory), SD Tools (for sd card).
CPU Settings: ondemand
Governor settings
Misc settings
For BFS kernel version use set rr_interval=2 in the misc tab under kernel settings. But for my Rom i stick to CFS currently.
Renice Settings
Some general tips:
The priorities influence the behaviour when two processes that want to do some work at the same time. It influences which process will get more cpu time, thus it may cause lags for the lower priority process.
So in general the default priority of 0 is the one you should keep for most of the processes. But there are some processes that maybe you are not using all the time, but when you want them to use you want them fast and lag free.An example for this is the "phone" process but also the systemui process can improve the behaviour of your GUI in general.
On the other side there are processes that need to do some work in the background. Such process could slow down or cause lags on your currently used app / foreground process. An example for this is the media scanner "android.process.media". Think of reducing its priority to prevent slowing down other things. You won't care if the media scan in the background would need a minute longer to finish if you get a more fluent foreground app
I also got user reports for apps like media players that since they increased their priority now work flawless.
A User's Renice Settings 12 Dec. 2011 (see used rom etc. above!)
Notess:
I increased the the priority for processes that need to respond fast when they actually are needed, like the phone process.
I also increased the priority of my keyoard app to improve its pop upp in some seldom but annoying situations. If you use more than one keyboard app just set an increased value of all of them. As you never will use two at the same time you do not need to decrease the priority of one of them
Beside of other stuff i also increased the priority of my used launcher, adw ex. Add your launcher or replace my entry with one for your launcher. I think com.android.launcher is the process name for the standard launcher. But as you are using it you can see its process in the list of the "add" dialog.
strange, where has the reply of user sergeybrin gone?
anyway, am open for suggestions and reports of issues. if anybody has tried it found that something is not working for their phone i would be thankfull to know what so i am able to fix that.
Optimal settings for LordMod 7.2BFS kernel
Hi a user thanks for the great app.
I'm on Alienmod's CM7 (nightly 208) with LordMod's 7.2BFS kernel and was wondering what the optimum settings are in the "Governor" tab?
I looked at your MIUI thread and saw that you have:
suspend_freq @ 614400
down_differential @ 15
sampling_down_factor @ 50
ignore_nice_load @ 0
up_threshold @ 85
powersave_bias @ 50
sampling_rate @ 80,000
io_is_busy @ 1
so I am using these settings and everything seems ok.. (im using ondemandX 230400min and 1152000max).
Are these settings ok to use for my ROM or are there better settings?
Also i'm currently -50mV undervolted.
Thanks!!
this are still the settings i use and i think they pretty much optimal for aosp roms for the dhd. edit: except that my max fre is 1075MHz
regarding undervolting: carefull and you should only undervolt one freq at a time then test that extesively (e.g. by setting min and max freq to it and running something stressing the cpu for a longer time).
in general it is only needed to undervolt the freqs close to your set max freq as undervolting only makes a significant difference on consumption if there is high load. and on high load your phone switches to higher freqs
p.s. glad you are happy with the app.
I recently discovered due to a nice customer that despite googles license code documentation the licensing server do not provide validation timeout infos. hence some customers may observed that the app failed licensing on connection issues.
Google documentation on this claimed it should work as i expected but it doesn't. Hence i just fixed this now myself and want to apologise for any issues caused by this. I will improve this further in the near future.
Great App
thank you!
@all: There are many roms out there with broken busybox installations. i already have some workaround built in to handle that. i just discovered that one of my workaround had a typo. so if someone tried the app and saw it not working as it should it probably got fixed with the most recent update to 1.2.6.
i would like to see why some people are cancelling the purchase as it is already possible to see exactly what it does on the screen shots. If something is not working as it should i can't fix it without feedback. too many roms and devices out there to have them all and being able to test against.
I've tested unsuccessfully on the tmo g2x running EaglesBlood latest (cm7 based) and the dragon kernal. By testing I mean the drop downs for CPU Max and min show a thin white bar with nothing selectable.
Edit: tested with another kernal, and my guess is they don't support your method for accessing the processors... but I've been wrong before.
thank you for the feedback. But i need the info provided by the feedback button. Please use the feedback button on the help tab to collect some information and send it via email.
if you do not want to send me an email you canstill use that button. it will collect some infos and save them on your sdcard as "systune.inf". cancel the email that opens up. the file will still remain on your sdcard.
attach it here to your next post (maybe you need to rename its extension to .txt). without that info there is nothing i could do.
p.s. you can look into that file to verify that nothing confidential is collected. it is plain text.
EDIT: i saw your edit. does this mean with the other kernel it worked? basically your guessing seems right. but the thing is that my method to acces this values is the ONLY one possible. it is done through the kernel exported values in the sysfs. this is basically the only way to access kernel values at runtime. this custom kernel(s) you are using are either not exporting these stuff or they are doing wrong (by convention).
in the latter case at least i could do a workaround to compensate for their wrong placement of the stuff.
The Load Settings dialog box is not working on BlackIce, same problem as I had on Hydr0g3nmod before. Box just displays Cancel and nowhere to select a file to load. Not critical but would be nice to have. Probably due to the super dark theme. Thanks!
Sent from my Desire HD using Tapatalk
cold y verify that it is indeed only due to the theme? i mean try pressing in the middle of the box where normally the entry of a file to load is located and see if it loads.
if it is just a theme issue, dark text on dark background, then you should inform paradoxx or alienmind about this as this is a bug on their rom. i am simpy using system default theme.
usefull for them to know is that the items to load are listed in a ListView using "android.R.layout.simple_list_item_1" for the items. With these infos they should be able to fix their theme.
p.s. new version with new features coming very soon.
a user said:
cold y verify that it is indeed only due to the theme? i mean try pressing in the middle of the box where normally the entry of a file to load is located and see if it loads.
if it is just a theme issue, dark text on dark background, then you should inform paradoxx or alienmind about this as this is a bug on their rom. i am simpy using system default theme.
usefull for them to know is that the items to load are listed in a ListView using "android.R.layout.simple_list_item_1" for the items. With these infos they should be able to fix their theme.
p.s. new version with new features coming very soon.
Click to expand...
Click to collapse
Thanks, no luck in finding the hidden dialog box but no big deal.I'll wait until the BlackIce theme fix is done, or who knows perhaps I'll be back on sci miui by then
Sent from my Desire HD using Tapatalk
New version with new features available.
Now it supports various kernel tweaks (cfs scheduler tweaks) and vm tweaks. You can find them in the Misc Tab. Also saving/loading is now available for the Misc Tab.
Hi my8,
Do you think that it could be useful to discuss our findings about the tuning of some parameters here or in another section?
Thanks for your VERY useful app.
normally i would say this should be in a device specific thread. but because i wont be allowed to open up a systune thread in each device subforum i think we could do it here.
so feel free to be the first.
as basic rules i think one should always include infos about device/rom/kernel to make the post actually usefull.
new version 1.3.2:
added tunable paramter for BFS kernels in the Kernel settings section under the Misc tab.
a user said:
normally i would say this should be in a device specific thread. but because i wont be allowed to open up a systune thread in each device subforum i think we could do it here.
so feel free to be the first.
as basic rules i think one should always include infos about device/rom/kernel to make the post actually usefull.
Click to expand...
Click to collapse
Ok thanks for that and also for v1.3.2.
I think also that here could be a good place for the discussion of some of the tunable parameters via systune app. Indeed, I think that there should be no such big difference from ROM to ROM (but probably more from device to device...).
This offers also the possibility to give (and get) some information about the parameters that are tunable via Systune.
Among the different group of parameters, due to personal interest, I want to focus on scheduler ones (CFS and now BFS (since v1.3.2)).
And first of all, some theory, because before tuning anything, it is EXTREEMELY IMPORTANT TO UNDERSTAND the meaning of these parameters: here below is a partial copy of http://doc.opensuse.org/products/opensuse/openSUSE/opensuse-tuning/cha.tuning.taskscheduler.html about CFS in opensuse distribution.
NB: I am not an expert in Android, but IMHO I thing that even if Android runs on linux, it must be a lot of difference between running a phone and a desktop. It is why, it is interesting to have this kind of discussion here.
The comment are personal and are there just to start the discussion....
My phone is a HTC Desire HD, with blackIce ROM with LordMod UE kernel v8 CFS.
sched_child_runs_first
A freshly forked child runs before the parent continues execution. Setting this parameter to 1 is beneficial for an application in which the child performs an execution after fork. For example make -j<NO_CPUS> performs better when sched_child_runs_first is turned off. The default value is 0.
OK default value seems logical for me.
sched_compat_yield
Enables the aggressive yield behavior of the old 0(1) scheduler. Java applications that use synchronization extensively perform better with this value set to 1. Only use it when you see a drop in performance. The default value is 0.
OK default value seems logical for me, but Dalvik being a Java VM, 1 could also be logical ?????
Expect applications that depend on the sched_yield() syscall behavior to perform better with the value set to 1.
sched_migration_cost
Amount of time after the last execution that a task is considered to be “cache hot” in migration decisions. A “hot” task is less likely to be migrated, so increasing this variable reduces task migrations. The default value is 500000 (ns).
If the CPU idle time is higher than expected when there are runnable processes, try reducing this value. If tasks bounce between CPUs or nodes too often, try increasing it.
In case of single core processor, IMHO I think that this value must be set high....
sched_latency_ns
Targeted preemption latency for CPU bound tasks. Increasing this variable increases a CPU bound task's timeslice. A task's timeslice is its weighted fair share of the scheduling period:
timeslice = scheduling period * (task's weight/total weight of tasks in the run queue)
The task's weight depends on the task's nice level and the scheduling policy. Minimum task weight for a SCHED_OTHER task is 15, corresponding to nice 19. The maximum task weight is 88761, corresponding to nice -20.
Timeslices become smaller as the load increases. When the number of runnable tasks exceeds sched_latency_ns/sched_min_granularity_ns, the slice becomes number_of_running_tasks * sched_min_granularity_ns. Prior to that, the slice is equal to sched_latency_ns.
This value also specifies the maximum amount of time during which a sleeping task is considered to be running for entitlement calculations. Increasing this variable increases the amount of time a waking task may consume before being preempted, thus increasing scheduler latency for CPU bound tasks. The default value is 20000000 (ns).
For a phone running with a processor > 1GHz I thing that 5000000 is a good value (to be discussed further)
sched_min_granularity_ns
Minimal preemption granularity for CPU bound tasks. See sched_latency_ns for details. The default value is 4000000 (ns).
Same as above with a suggested value of 1000000
sched_wakeup_granularity_ns
The wake-up preemption granularity. Increasing this variable reduces wake-up preemption, reducing disturbance of compute bound tasks. Lowering it improves wake-up latency and throughput for latency critical tasks, particularly when a short duty cycle load component must compete with CPU bound components. The default value is 5000000 (ns).
Same as above with a suggested value of 1000000
sched_nr_migrate
Controls how many tasks can be moved across processors through migration software interrupts (softirq). If a large number of tasks is created by SCHED_OTHER policy, they will all be run on the same processor. The default value is 32. Increasing this value gives a performance boost to large SCHED_OTHER threads at the expense of increased latencies for real-time tasks.
IMHO must be sed = 0 for single core processor....
[To be continued later.....]
I know this article already but good you posted it here.
Based on my understanding an tests i have the following suggestions:
Sched_compat_yield set to 0 seems to improve performance. Note this is not a java virtual machine. This is only based on my tests
Sched_latency_ns : I recently am testing very low values. Currently using 390000 and 130000 for the two granularity parameters.
It seems smoother without losing raw throughoutput performance.
Regarding the migration parameters.... we are running a single core device. hence I think it simply doesn't matter what values we have set there as no task will ever switch the CPU it is bound to.
But a test if set to 0 can reduce some overhead could be a worth try.
Sent from my HTC Desire HD using XDA App
a user said:
I know this article already but good you posted it here.
Based on my understanding an tests i have the following suggestions:
Sched_compat_yield set to 0 seems to improve performance. Note this is not a java virtual machine. This is only based on my tests
Sched_latency_ns : I recently am testing very low values. Currently using 390000 and 130000 for the two granularity parameters.
It seems smoother without losing raw throughoutput performance.
Regarding the migration parameters.... we are running a single core device. hence I think it simply doesn't matter what values we have set there as no task will ever switch the CPU it is bound to.
But a test if set to 0 can reduce some overhead could be a worth try.
Sent from my HTC Desire HD using XDA App
Click to expand...
Click to collapse
Ok and thanks for your answer even if I don't totally agree with your proposal.
Indeed, I think that going down to so small value could be a little bit risky in term of CPU load and throughput for processor bounded task (I know that they are quite unimportant in a phone). Nevertheless, I am now testing Sched_latency_ns 1000000 and 250000 for the two granularity parameters...
Now some words about BFS ( Brain **** Scheduler) introduced recently by M. Kolivas (see article here: http://ck.kolivas.org/patches/bfs/sched-BFS.txt).
"It was designed to be forward looking only, make the most of lower spec machines, and not scale to massive hardware. ie it is a desktop orientated scheduler, with extremely low latencies for excellent interactivity by design rather than "calculated", with rigid fairness, nice priority distribution and extreme scalability within normal load levels."
Here the only tunable parameter is rr_interval that is roughly equivalent to the latency [in ms]. The default value = 6 [ms] that seems ok for me (possible values 1 -> 1000).
[to be continued...]
ok, nothing seemed to be making the touchscreen responsive with the ICS beta n its derivatives.
except one thing just did.
i changed the sampling rate from 200000(2 lak) to 20000 (20 hazar), n of course i had to change the up-threshold so i changed that to 95 (i did all these in rom-toolbox's kernel tweaks settings)
now everything is super-responsive (app startups, physical buttons, onscreen buttons, switching, yo name it) N while you are just lets say reading stuff on the screen, the cpu is generally at its lowest
what that means is : both responsiveness and higher battery.
please comment.
UPDATE : check the 7th post on this forum for more tweaks for snappy app launching n switching here http://forum.xda-developers.com/showthread.php?t=1570374#post24186676
UPDATE : ADDITIONAL TWEAK (more battery life) : in rom-toolbox change powersave bias to 35 (in rom toolbox) : saves a lot more battery by preventing the cpu from rushing to full-frequency while you are doing simple tasks like flicking the screen.
UPDATE : 3/31/12 : an interesting observation about "force gpu" 's causing poor performance on my post here : http://forum.xda-developers.com/showthread.php?t=1570374&page=2#post24266342
UPDATE : 4/7/12 : want even more battery life n smoothness?
add these to your build.prop save , reboot into recovery, clean dalvik-cache and /cache partition then reboot into system. things should be faster. and oh, underclock it.
ro.kernel.android.checkjni=0
dalvik.vm.execution-mode=int:jit
ro.ril.disable.power.collapse=0
ro.mot.buttonlight.timeout=1
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
you can also do a semi-odex using titanium backup's integrate system dalvik into rom thing, but then you won't be able to change any file in the rom (like applying patches, mods etc until you've either done undo integration thing in titanium backup or just used adb shell to delete *.odex from /system/apps n rebooted)
UPDATE : 4/28/12 : if you are using a derivative of the .562 ICS then you can change the kernel tweaks/sysctl settings to dirty_ratio = 80 dirty_background_ratio = 20 and vfs_cache_pressure = 20 to get snappy app startups up_threshold and powersave_bias can both be set to 90 and select ignore_nice_load. if you use lots of apps then raise the dirty background ratio and dirty ratio both by 15 points and reduce vfs_cache_pressure by 15 for low cpu usage while the apps are running. i've noticed that many of the custom roms have started getting my tweaks or similars preincluded , plus the official ics is much better than icsbeta in memory management. and oh, use arcknight kernel. its super awesome for both features and battery life. i switch my governor to interactivex or smartassv2 when i am recording using the 14mbps camcorder mod, and then back.
the android backup & restore under person in settings should be turned off. it takes a lot of cpu, battery, data n memory. its aweful.
if this works for you, press the thanks button.
How can this be done?
Duvel999 said:
How can this be done?
Click to expand...
Click to collapse
i used rom toolbox pro, its free version is available here - https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
anything else that can edit sysctl.conf (e.g. https://play.google.com/store/apps/details?id=com.jrummy.sysctl.config and https://play.google.com/store/apps/details?id=scd.atools ) will also work.
Gonna try it
system seems to be a bit snappier
thx mate
thnx mate.
for snappy app switching i discovered another bunch of settings
in rom toolbox's kernel tweaks under performance, change min free kbytes to [CORRECTION]8192[not 8096] (or [UPDATE] 6144 - whichever one you like), dirty ratio to 95, dirty background ratio to 70 and vfs cache pressure to 5 (n of course check the apply on boot option)
let me know how you like this additional tweak
UPDATE: some observations ; high dirty ratio causes lower cpu usage n faster app-switching, low dirty background ratio causes faster app startups but uses too much cpu, vfs cache pressure above 5 or 10 causes high cpu usage n lags. (i use lots of apps)
UPDATE #2 FURTHER IMPROVEMENTS (fast all around with acceptable cpu usage, super app switching, n decently fast launcher without sacrificing cpu-speed n battery life)
Kernel Tweaks :
reduce dirty background ratio to 50
check the OOM kill allocating task (if your device crashes after this, uncheck this, it may kill the android system n android os processes as well in some cases)
Auto Memory Manager :
foreground 6
visible 8
secondary 32
hidden 40
content 48
empty 120
Thnks
[white10char]
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
perhaps kickass kernel script
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
check the 98kickasskernelizer (i'd find the respective values - especially min-free n change them in the script itself), there are two other not so popular scripts out there too that you may be using.
please share with us whatever was causing the overriding of rom toolbox's (or sysctl etc)'s settings.
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
hansip87 said:
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
Click to expand...
Click to collapse
the benchmarks dont tell you about usability. better responsiveness is due to faster cpu response to situations.
antutu's benchmark tests for continuous high performance (battery hogging w/lags) while running just one app.
my settings are for giving great experience (touch, app switching and app launching as well)
think of it as antutu being a mr. universe test, while mine are a gymnastics olympics tournament.
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
darth5zaft said:
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
Click to expand...
Click to collapse
thank you.
i just posted another slight tweak for higher battery life. its in the first post.
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
Could it be that these settings are conflicting with Supercharger?
Sent from my LT15i (Xperia arc) on KA ICSony
hootnath said:
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
Click to expand...
Click to collapse
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
estuardo4 said:
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
Click to expand...
Click to collapse
i found another interesting thing today.
the force GPU for 3d in the settings -> developer options actually uses a lot of the cpu and causes lags. i turned it off and have instead done the following
Get rid of CPU rendering:
Navigate to /system/lib/egl/
Open the file named "egl.cfg"
Delete the first line. It should say "0 0 android" or something similar
Go back into the egl folder and delete libGLES_android.so
What this does is remove the entire soft-rendering pathway from the OS.
source : http://www.ifans.com/forums/threads/ics-performance-tweaks.369959/ ;
now, i have changed the powersave bias in teh romtoolbox's kernel tweaks to 95 instead of {correcton}35{not]95. the cpu is spending more time @ 122mhz and deep sleep now without lags (which means more battery)
if this thing works for you, please press thanks.
Recently an app was launched in Google Play that puts different settings to our Tegra CPU.It's called Tegra Overclock : https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImNvbS50ZWdyYW92ZXJjbG9jayJd
This app maybe can fix the problem with the brightness cutter problem that many of us who uses 100% brightness have :
{
"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 ll run some tests by myself but i would like from all you that can afford to buy this app to run some tests and post your results
The questions that must be answered are the following :
1) The CPU temperature or the Battery temperature makes the brightness cutter to popup ?
2) In which temperature limit does the brightness cutter pop up and lower our brightness to 87% ?
3) Which settings of the Tegra Overclock app can raise up the the default temperature limit to a higher level ?
4) Do these settings produce lags in light or heavy use?
Please run some tests by yourselves as i am going to do and give feedback.This is a very annoying thing in both the Optimus 4X and G phones for all of us who want to have brightness set at 100% all the time.
PS : I know that there is a trick to make the limit higher by doing this http://forum.xda-developers.com/showthread.php?t=2187017 but it's not a permanent solution as it's changing the files of Tegra Thermal to default values in every restart of the phone.
ipred said:
Recently an app was launched in Google Play that puts different settings to our Tegra CPU.It's called Tegra Overclock : https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImNvbS50ZWdyYW92ZXJjbG9jayJd
This app maybe can fix the problem with the brightness cutter problem that many of us who uses 100% brightness have :
I ll run some tests by myself but i would like from all you that can afford to buy this app to run some tests and post your results
The questions that must be answered are the following :
1) The CPU temperature or the Battery temperature makes the brightness cutter to popup ?
2) In which temperature limit does the brightness cutter pop up and lower our brightness to 87% ?
3) Which settings of the Tegra Overclock app can raise up the the default temperature limit to a higher level ?
4) Do these settings produce lags in light or heavy use?
Please run some tests by yourselves as i am going to do and give feedback.This is a very annoying thing in both the Optimus 4X and G phones for all of us who want to have brightness set at 100% all the time.
PS : I know that there is a trick to make the limit higher by doing this http://forum.xda-developers.com/showthread.php?t=2187017 but it's not a permanent solution as it's changing the files of Tegra Thermal to default values in every restart of the phone.
Click to expand...
Click to collapse
Tegra overclock can set thermal values at boot, but these only affect CPU speed, the smartdimmer can't be disabled either I tried and the screen goes all messed up
Sent from my rooted P880
Thank you for your feedback.I spoke to the developer of the app and he is near to find a solution without degrading the performance of the system.
I just wanted to post this here, but @ipred was faster I wanted to ask if anyone has tried this app? Does it really work - I mean, can you control how many CPU cores are fired up at boot ? Can you save some battery with it ?
What are you experience with it?
JAsko_san said:
I just wanted to post this here, but @ipred was faster I wanted to ask if anyone has tried this app? Does it really work - I mean, can you control how many CPU cores are fired up at boot ? Can you save some battery with it ?
What are you experience with it?
Click to expand...
Click to collapse
Yes it works perfectly fine. Im able to adjust GPU clocks (only to what the kernel allows, or it freezes and reboots). I can also force a number of CPUs online so they are constantly being used. Im not so sure of thermal guard though. But all in all I find this app useful for when I want to boost performance in games; it helps.
I have bought and used this app an it works pretty good, once you get the hang of it. The depiction of the changes you made isn't very well showed, but otherwise in my case at least - running stock rom, rooted - I can successfully set CPU speed, force some or all cores online or even use the companion core exclusively, plus I can also increase/decrease GPU speed and SD access speed. All in all, I'm now satisfied with the purchase. The problems, ipred, keeps facing with screen dimming are unknown to me, because I set screen at 40% brightness and so I've never noticed high enough temperatures that impose limitations on screen brightness or performance.
In my O4X (rooted unlocked) wirh stock kernel (and rom) i think even if i change gpu clock, actually doesn't change...i'll try with other kernels (eternity one because is the only one usable with stock rom)
Inviato dal mio LG-P880
Rufo3 said:
In my O4X (rooted unlocked) wirh stock kernel (and rom) i think even if i change gpu clock, actually doesn't change...i'll try with other kernels (eternity one because is the only one usable with stock rom)
Inviato dal mio LG-P880
Click to expand...
Click to collapse
I believe this is because your GPU has not been unlinked from the CPU, meaning your GPU clocks are dependent on CPU clocks. The settings don't stay because the clocks are constantly changing.
Ddoubled123 said:
I believe this is because your GPU has not been unlinked from the CPU, meaning your GPU clocks are dependent on CPU clocks. The settings don't stay because the clocks are constantly changing.
Click to expand...
Click to collapse
No, tegra overclock unlinks, well actually it forces the value. Because of limitations in the kernel no frequency above 416mhz will stick, however on cm10.1 @laufersteppenwolf built a kernel that can do the HTC one x default of 520mhz
Sent from my rooted P880
Ddoubled123 said:
I believe this is because your GPU has not been unlinked from the CPU, meaning your GPU clocks are dependent on CPU clocks. The settings don't stay because the clocks are constantly changing.
Click to expand...
Click to collapse
Yeah i think it too...but too sokve this problem i need a custom kernel right?
Inviato dal mio LG-P880
@non4 said:
No, tegra overclock unlinks, well actually it forces the value. Because of limitations in the kernel no frequency above 416mhz will stick, however on cm10.1 @laufersteppenwolf built a kernel that can do the HTC one x default of 520mhz
Sent from my rooted P880
Click to expand...
Click to collapse
So, does tegra overclock make the GPU independent by forcing the values rather than using tweaks?
Just need this to be clarified.
Ddoubled123 said:
So, does tegra overclock make the GPU independent by forcing the values rather than using tweaks?
Just need this to be clarified.
Click to expand...
Click to collapse
easy said: yes
it executes two commands, one that unlinks the GPU from the CPU and the other one that echos the desired clock speeds to the right GPU parameters.
ipred said:
Recently an app was launched in Google Play that puts different settings to our Tegra CPU.It's called Tegra Overclock : https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImNvbS50ZWdyYW92ZXJjbG9jayJd
This app maybe can fix the problem with the brightness cutter problem that many of us who uses 100% brightness have :
I ll run some tests by myself but i would like from all you that can afford to buy this app to run some tests and post your results
The questions that must be answered are the following :
1) The CPU temperature or the Battery temperature makes the brightness cutter to popup ?
2) In which temperature limit does the brightness cutter pop up and lower our brightness to 87% ?
3) Which settings of the Tegra Overclock app can raise up the the default temperature limit to a higher level ?
4) Do these settings produce lags in light or heavy use?
Please run some tests by yourselves as i am going to do and give feedback.This is a very annoying thing in both the Optimus 4X and G phones for all of us who want to have brightness set at 100% all the time.
PS : I know that there is a trick to make the limit higher by doing this http://forum.xda-developers.com/showthread.php?t=2187017 but it's not a permanent solution as it's changing the files of Tegra Thermal to default values in every restart of the phone.
Click to expand...
Click to collapse
I think you can edit the framework.res.apk to set the stock values higher or lower but dont gamble with it if u dont know exactly what u are doing! To edit them use a tool like virtuos ten studio! You can find it here on xda..
Have a nice day at all
Sent from my LG-P880 using XDA Premium HD app
Thanks for your answer but i will wait till Monday as the Tegra Overclock developers answered me this today :
"Alright we have completed the brightness cutter solution module and can upload the update as soon as we make it ready to set on boot BUT we are afraid of piracy as this patch is important one and we saw a hell lot of piracy last week of our app, that's why we reported to you that the patch is ready and we are working on google licensing service. We should be able to upload by Monday if the Piracy protection gets implemented soon"
The update came today and in the release notes it says :
"V1.5.2 MUST CLEAR DATA OR FIRST UNINSTALL APPLICATION AND THEN INSTALL THE UPDATE
***An attempt to eliminate the Brightness problem found in Optimus 4X and G devices. Please refer to EXTRA section of app"
The problem is that i cannot get into EXTRA.Every time i hit the button EXTRA the app is crashing.Before the update i uninstalled and reinstall the app as the notes say.I made a report to the developer and hope that he 'll fix it today.
ipred said:
The update came today and in the release notes it says :
"V1.5.2 MUST CLEAR DATA OR FIRST UNINSTALL APPLICATION AND THEN INSTALL THE UPDATE
***An attempt to eliminate the Brightness problem found in Optimus 4X and G devices. Please refer to EXTRA section of app"
The problem is that i cannot get into EXTRA.Every time i hit the button EXTRA the app is crashing.Before the update i uninstalled and reinstall the app as the notes say.I made a report to the developer and hope that he 'll fix it today.
Click to expand...
Click to collapse
Its been updated and now works, only issue is even if you disable the control you can't adjust brightness via normal setting anymore. But they're going to fix that too
Sent from my rooted P880
1.5.4 is the last update published today and unfortunately it does not resolve the brightness cutter problem at least on my phone.
I really can't understand why LG put this brightness cutter ! Would it be more convenient to have included an advice message "Please lower the brightness..." and let users decide instead of lower down the brightness automatically ???? And secondly , why 44 Celsius for CPU and 34 Celsius for the battery are considered so high temperatures????
I wish in the future that a developer will find the source of this brightness cutter activity and remove it, or disable it or shut it off !!!
Is there someone available ( rooted of course ) to execute a command that according to the developers of Tegra Overclock has a lot of chances to disable the brightness cutter? I personally don't have time these days to run tests.
If yes please contact by email ( [email protected] ) the developer of Tegra Overclock ,Rohit Joshi, to tell you the steps.:good:
Finally the problem with the brightness cutter is solved !!! The developers of the Tegra Overclock application managed to create a patch that disallow the cutter to come up.
All you have to do is to download the updated ( 21.06.2013 ) Tegra Oveclock app from Google Play, open it, go to Εxtras, check the box Patch Brightness Cutter LG (ONLY ) and reboot ! The solution is permanent!
For rooted users only.
Many thanks and respect to the developers οf Tegra Overclock
ipred said:
Finally the problem with the brightness cutter is solved !!! The developers of the Tegra Overclock application managed to create a patch that disallow the cutter to come up.
All you have to do is to download the updated ( 21.06.2013 ) Tegra Oveclock app from Google Play, open it, go to Εxtras, check the box Patch Brightness Cutter LG (ONLY ) and reboot ! The solution is permanent!
For rooted users only.
Many thanks and respect to the developers οf Tegra Overclock
Click to expand...
Click to collapse
It does not work on stock ROM and kernel. (v1.5.7)
Have you tested the new functionality before writing this post?
/// JellyBeanX-kernel ///
DISCLAIMER
Me, XDA-Developers.com and anyone else doesn't take any repsonsibilty for damages on your device!
Rooting your device will void your warranty!
Don't play with settings you aren't familiar with, you could burn your device!!
Click to expand...
Click to collapse
READ THIS: READ BEFORE YOU ASK and HELP TO KEEP THIS THREAD MORE CLEAN! BUT ALSO BETTER ASK ONCE MORE BEFORE YOU MESS UP YOUR PHONE! If you find something missing in this OP/FAQ, please PM me and I will add it. Thank you!
This is a custom kernel mostly based on Motorola's 3.0.8 Hybrid Kernel which was initiated first by the STS-Dev-Team (Hashcode, Dhacker).
I created this kernel for my main goal: BATTERY LIFE! Like many other custom kernels this one also supports several performance related features like OVERCLOCKING, UNDERVOLTUNG, GPU CONTROL, CPU OPTIONS, RAM TWEAKS, etc etc... But my main goal was not to bring up a kernel which is fast as hell - I want to bring up a kernel that is fast + a long lasting battery! Many custom kernels are also very fast but they don't save battery. JBX-Kernel is supposed to push your device to great speed while being on low power settings. I hope you enjoy it!
If you want to support me and my work just leave me a beer.
You can find the FAQ at the bottom of this post!
LATEST CHANGES
FULL HD Video Recording is working now!!! See Downloads section below!
--> DETAILED CHANGELOG JBX-kernel Hybrid 4.4 <--
Kernel Guide by Placca 1.8!!
Check the FAQ section at the bottom of this post to download it! It will make many things easier for you and help you to understand the kernel and its features!
FEATURES
JBX-Kernel Hybrid
Battery Friend toggle (a battery friendly mode)
Intelli-Plug (Kernel side replacement for msm MPDecisions) by Faux123 + patches by me (no hotplugging when screen is ON)
Dynamic Hotplug: Second core will be turned off ONLY while screen is off - independent from selected governor. (Not needed when using Intelli-Plug)
Optimized OPP Table for smooth CPU scaling
Frequencies: 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1300
Modifed Smartreflex driver (Custom Sensor for detecting n-Value).
Smartreflex Tuning Interface: Set min/max calibrated voltage
Overclocking using Live OC (mine runs stable at a maximum frequency of 1,498ghz!)
hwmod, uart, IRQs - cleanups from pre-kexec config to safe power
CPU: lower voltages for CORE and IVA. Give CORE the abbility to scale up to higher voltage if needed
Added IVA_NITROSB
Dynamic fsync control: FSYNC interval is dynamic depending on screen state (SCREEN OFF: synchronous, SCREEN ON: asynchronous)
HTC's Asynchronous Fsync port - read explanation below*
Dynamic page-writeback: Page writeback interval is dynamic depending on screen state.
Frandom v2
JRCU / Tiny RCU (currently JRCU in use)
Raised voltage limits for mpu a bit
Raised the temperature limits from 64c* to 74c* (degrees)
optimized CRC32 algorithm (better code generation)
RW Readahead dynamically depending on storage device (automatic detection of the best value)
zRAM support
GPU has 4 scaling steps and OC to 384mhz (Base freq: 102 mhz --> 154 mhz, 307 mhz, 384 mhz)
GPU C4 states / GPU Control (Governors, Frequencies)
Multicore Power Saving Mode Control
ARCH Dependant Power feature
Gamma Control
Front Buffer Delay Control (draw in x msecs on early suspend)
Screen/Display: Modified OMAPDSS for sharpness and lightning colors
OMAPDSS: Added variable clock rate and OPP - allows the screen to scale down power and voltage
lowmemkiller: Heavy modified for R/W Speed and efficient performance
ZCACHE, ZSMALLOC, XVMALLOC backported from 3.4, 3.7 and 3.10 (ZCACHE currently not in use)
Custom Voltage Support
IO-Schedulers: SIOPlus, Fifo, Row, VR, Noop, Deadline, CFQ, BFQ
ROW Scheduler is heavily tweaked to be the fastest scheduler ever!
CPU: More Governors
Deep Idle
ARM Topology
Many improvements in overall OMAP PM
SELinux permissive
GREAT performance!
battery life!
Support for Trickster Mod Kernel Control App (Download from Gplay)
*]Too much stuff to list here. See "Sources" below and check my Github
* HTC's Asynchronous Fsync and Dynamic Fsync:
Asynchronous fsync (called "afsync" or "async fsync") from HTC is ported into this kernel. By default it's enabled and dynamic fsync is disabled (and as well it isn't needed anymore). But just to test a little bit around to see which one of both features is the better one - for battery & performance. But currently Tricktser Mod doesn't support a toggle for afsync, so I had to find another way to use Trckster. Finally I did it like this:
The dynamic fsync toggle in Trickster Mod is now serving both functions - the dynamic fsync AND the asynchronous fsync! How? By default Dynamic Fsync is disabled, and Afsync is enabled. If you now enable Dynamic fsync using the toggle, Afsync will be automatically disabled, so both functions are not conflicting each other - and this way we have a working toggle for both of them.
CAUTION
This is a work in progress! Some of the current features are still not in final stat. If you are facing issues report back here and DON'T spam the threads of the rom you're using!
Be careful with some settings such like Voltage and Overclocking!!! If you aren't experienced with these things, dont play with 'em!
Click to expand...
Click to collapse
REQUIREMENTS
NOTE: This will NOT work on Stock(-based) Roms!!
Rooted device
Must use a Kexec Rom (CM, AOKP, AOSP)
Recovery (BMM, SS)
REMOVE any kernel modules you used before
DEACTIVATE ANY CPU tweaks, onboot settings etc otherwise your phone may not boot!
CAUTION: The kernel needs a clean setup related to CPU tweaks / Settings, etc...Keep your device as clean as possible regarding to Tweaks, CPU special settings, etc. The Kernel brings its own CPU settings and after you can boot it succesfully, you can set it like you want!
This kernel may not work on all roms! Check and report.
TO DO LIST
- Fix bugs
INSTRUCTIONS
NOTE: CLICK here for a detailled Installation Guide (about the Aroma Installer, the features to select and more)
Download zip file from below
Reboot into recovery
Flash the kernel (BMM users: DON'T use the "Flash Kernel" Option! This is a usual zip file!)
Reboot
Download Trickster Mod App from Gplay! Read the FAQ to learn about playing with kernel features!
Enjoy!
NOTE: For updates you can use the built-in OTA UpdateMe App!
DOWNLOAD
NOTE:
Only for Android 4.4!
JBX-Kernel 3.0.8 Version:
2.x == > Android 4.4
JBX-Kernel 3.0.31 Versions:
3.x == > Android 4.4
TEST BUILDs
Test builds are potential prerelease builds which need some more testing before pushing to all users.
CAUTION: Should be stable mostly! But use at your own risk though!!
---> TEST BUILDS [CF] <---
XPERIMENTAL BUILDs
These builds include features without promises to work.
CAUTION: There is no promise that these version are stable/working/whatever! Use at your own risk!!
---> XPERIMENTAL Builds [Dev-Host] <---
---> XPERIMENTAL Builds [CF] <---
Click to expand...
Click to collapse
Something went wrong?
If you think you have set wrong "on-boot-values" in Trickster Mod flash this:
TRICKSTER RESET: http://dtrailer.de/kernel/trickster_reset.zip
FAQ
CAUTION: This FAQ and the whole OP, additional informations about Governors, IO Schedulers and detailed informations about the usage of Trickster Mod and this kernel can be viewed in the awesome Kernel Guide by Placca!
Kernel Guide 1.8
PDF: http://www.mediafire.com/download/7zaddcmvtxfk9ry/JBX+Kernel+Guide_v1.8.pdf
CHM: http://www.mediafire.com/download/g3ck1bf1k3a3j38/JBX+Kernel+Guide_v1.8.chm
CLICK THE BUTTON BELOW TO OPEN THE FAQ!
Please check the following points if you don't know how to use the features of the kernel or you are facing any kind of issues.
INDEX
1. Kernel Features
1.1 Smartreflex (Turn ON/OFF, adjust min/max range)
1.2 Live OC (Realtime Overclocking)
1.3 Custom Voltage (EMIF)
1.4 GPU Overclock & GPU Governor (UPDATED)
1.5 Gamma Control
1.6 Battery Friend
1.7 Suspend Governor (CURRENTLY DISABLED)
1.8 IVA Overclock
1.9 DPLL Cascading
1.10 HDMI toggle
1.11 Intelli-Plug
2. Issues
1.1 How can I change the smartreflex minimum/maximum voltage
What is Smartreflex?
SR is compareable with an CPU governor but not for scaling frequencies but for voltages. That means SR has a fixed range of voltage (min/max) and calculates the optimal voltage for each CPU frequency. In example on light use of the CPU it scales down to lower voltage - on heavy use it can sclae to higher voltage. This is an efficient system to save power! Compared to EMIF which uses the hardcoded voltages it saves more power because it's variable. EMIF cannot vary between the values.
This interface has a hardcoded range of 830mV min to 1450mV max. Usually there is no need to adjust these values but irt can be usefull in example when using high overclocked frequencies above 1,5ghz! Usually SR cannot handle frequencies above 1,5ghz and I have hardcoded the maximum range of 1,45mV which should allow SR to handle it. In prior times the users had to turn off SR when OCing above 1,5ghz which causes the CPU to eat more power. But you can try around and report your results.
CAUTION: Don't raise the maximum SR voltage too high! It can burn your board = no phone anymore! I recommend to not use higher values than 1490mV! As already mentioned: THe default value should be enough!
ANd also: USUALLY THERE IS NO NEED TO CHANGE ANYTHING ON SR! IF YOU DON'T KNOW WHAT YOU'RE DOING, PLEASE LEAVE IT ALONE!
Ok, now let's see how to do this:
Turn ON/OFF SR
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. You can toggle ON/OFF SR for each component (IVA, CORE, MPU)
Usually I recommend to keep SR ON because it saves power! But in some cases when overclocking the CPU (MPU) the device could freeze - whether you OCed too much or SR couldn't handle the frequency! In this case you can try to raise the vmax value of SR a little bit (CAREFULLY!) and try again. If it sitll freezes and you're sure that you didn't OC too much, turn SR OFF at least for MPU!
Maximum Voltage
Currently there is no app which supports the feature of adjusting the SR vmax value, because I wrote this feature some days ago.
But in the next Trickster Mod version this option will be supported!
example:
# To read the current vmax value. Replace XXX with one of the following:
sc_core - for core max sr voltage
sr_iva - for iva max sr voltage
sr_mpu - for mpu max sr voltage (mpu is most related for CPU scaling)
cat /sys/kernel/debug/smartreflex/XXX/vmax
# You will get an output, e.g. for mpu = 1450000 (1450mV)
# To set a new value, do the following command (replace XXX with a value like above - BE CAREFUL! USUALLY THE DEFAULT VALUE ENOUGH AND YOU CAN LEAVE IT UNTOUCHED!)
echo XXX > /sys/kernel/debug/smartreflex/XXX/vmax
Minimum Voltage
It's easy because Trickster Mod supports it!
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. Below each SR component (IVA, CORE, MPU) there is displayed a value (usually 830 default) which means this is the lowest scalable voltage for this component. You can try to decrease this value for the case you want to UV a bit more - or raise it a bit for the case you think that the set range is too low and causes freezes on your device.
1.2 How do I use Live OC (Live OVerclock)?
This feature allows you to overclock the CPU in realtime. It works with a multiplier value set by the user. The default multplier value is "100", which means: No OC! If you want to raise the OC frerquency, just raise this value step by step.
FOr my device the maximum working OC value is "111" which means the maximum frequency is running at 1498mhz!
NOTE: Keep in mind that you tunr Smartreflex OFF for higher freqs than 1500mhz - or raise the maximum SR voltage range for "MPU" a little bit and test if it works.
Ok, how to use Live oC in action:
Open Trickster Mod App and swipe to the tab "Specific". There you will find something like this:
Code:
MPU OC [100]
DON'T TOUCH THE "CORE OC" SECTION, IT WILL CAUSE FREEZES!
Now slowly increase the value "100" to something higher, e.g. "105". Tap the hook in the right upper corner to confirm. To see your new set of frequencies you can now whether close and restart Trickster Mod or just use any monitoring app like Cool Tool which will show your frequencies in real time. That's it!
CAUTION: You can damage your phone forever!!!! This feature allows you to set very high frequencies (also up to 2,0ghz...) - That DOESN'T mean that your phone can run these frequencies!
If your phone freezes or crashes you have probably set too high OC - or your voltage is too low.
1.3 How do I use Custom Voltage (EMIF)?
NOTE: This only adjusts the fixed voltage! When you have Smartreflex ON it can still vary! You have to see the bigger picture: This voltage value sets the "middle point" for voltages. Smartreflex is still able to increase or decrease the voltage. When Smartreflex is OFF the CPU will stay on this voltage you set here and probably eats also more power.
How does EMIF works together with Smartreflex:
Code:
-------
| CPU |
-------
|
------------------ ------------------
|Voltage 1015 mV | ---->| SMARTREFLEX ON| = 1015mV +/- "vmax"/"vmin"
------------------ -------------------
|
--------------------
|SMARTREFLEX OFF| ----> 1015mV FIXED! No changes!
-------------------
Thi smeans if you change the voltage for a scaling step (OPP) while SR is ON, SR will adjust the voltage from this value, means: mV-Value +/- SR vmin/vmax. WHen SR is OFF it will stay on this mV as a fixed value.
How to adjust the voltage?
Well, this feature can be used with all generic apps which are supporting voltage settings. But we are prepared well, you can adjust voltages also with the "Trickster Mod App".
When you open the app, head to the tab "Specific" and below the "Live OC Section" you will find your voltage table, which looks like this:
Code:
<-->
1200 [1398]
1000 [1388]
900 [1371]
...
..
..
Now just tap the arrows in the right upper above the first voltage value and just type or tap (per direction) a value, e.g. "-25". To apply it, confirm by tapping the hook in the right upper corner of your screen. That's it, your new voltage values are now set and applied. And also mind here: If your phone freezes you porbably have set it too low.
CAUTION: NEVER SET HIGHER VOLTAGE THAN 1490mv here!!!!! Or you might damage your phone FOREVER!
This voltage is not the same like Smartreflex! But it's still voltage! Just be carefull!!
1.4 How can I use GPU OC and GPU Governor?
GPU Overclock doesn't work like Live OC! You cannot really set custom frequencies for the GPU, but you can select and set the maximum frequency from a hardcoded range!
For the GPU there are the following available frequencies:
154mhz (FIXED!)
307mhz
384mhz
416mhz
The minimum frequency of 154 is FIXED! This means you cannot change it because the GPU needs a minimum speed to run with. But the kernel allows you to select the maximum speed. This can be usefull for playing games and also for saving power . In example when not playing games you don't need the GPU to run at 416mhz! Set it to 307mhz in this case and save power.
When you open Trcikster Mod and head to the "specific section tab", you will find "GPU MAX FREQUENCY" and it's currently set maximum frequency. Tap on it to select your preferred one:
- 154 Mhz
- 307 MHz
- 384 MHz
That's it. The new setting will be your new maximum GPU frequency.
Below there's another option called "GPU Governor". Just tap on it and select your prefered one.
NOTE: If you want to track current GPU frequencies and watch governor's behavior, just switch to Trickster's "Informations" - Tab and watch the frequencies clock.
1.5 How can I use Gamma Control?
What is gamma? The gamma setting sets the color range for the screen. You can compare it to the contrast. We all know that the touchscreen eats most of the power compaerd to all other components in a smartphone! A lower brightness causes less power consumption and a lower gamma or contrast range alos helps a little bit to save power.
In this kernel you can choose from a range of "5 - 10" while "5" is very bright while "10" is very dark. The default setting is "5" BUT CAUTION: Trickster Mod will display a range of "0" to "10" and the default setting will be shown as "0". This is caused by the fact that this feature was ported from the Gnex device where you can choose from a higher range. The only sideeffect is that the values "0" - "5" won't show any difference.
How to set the gamma value?
Well, once again open Trickster Mod and swipe to the tab on the right end. Just select your preferred value by using the slider.
Alternately you can use sysfs by terminal or adb:
OMAP Gamma interface:
echo i > /sys/devices/platform/omapdss/manager0/gamma
Replace i with 0-10 of your choice.
1.6 What is "Battery Friend and how to use it?
Battery Friend is a simple toggle (ON/OFF) which sets your device into a battery friendly mode without the need to play with all settings in Trickster Mod /sysfs until you find a good setting. In fact it does the job for you.
What does it affect?
NOTE: Doesn't lock anyx frequencies anymore!
locks dynamic Fsync enabled
locks Fsync disabled
Doesn't allow any OC (Live OC will not have any effect, Core OC is not allowed in this kernel)
Increases the dirty ratio interval to 90% (starts working at this value)
Enables Dynamic Hotplug: This doesn't allow hotplugging during device is active - and it will always turn CPU1 OFF during suspend! It also prevents from conflicts when user uses a hotplug governor (which isn't a good idea though) - but hotplug governors are causing higher battery drain!
Dynamic Page-writeback always enabled
How to toggle Battery Friend:
For now the only way is via terminal, adb shell or root explorer (text editor)
For terminal and adb:
Code:
echo 1 > sys/kernel/battery_friend/battery_friend_active /* Enable */
echo 0 > sys/kernel/battery_friend/battery_friend_active /* Disable */
For Root Explorer
Open Root Explorer
Navigate to sys/kernel/battery_friend/
Open "battery_friend_active" with Text Editor
Change "0" to "1" and safe the file to enable
Change "1" to "0" and safe the file to disable
1.7 Suspend Governor Control (CURRENTLY DISABLED)
Suspend Governor Control is a kernel module written by me. You can use it to set your preferred Screen-Off-governor.
For now it's only supported by sysfs (Trickster Mod will support all my current and upcoming features as soon as it gets updated with its new UI mode!
How to set suspend governor
Open a terminal or use adb shell
Code:
su
echo "x" > /sys/kernel/suspend_gov/suspend_gov
Replace x with one of these values:
0 = Ondemand
1 = Ktoonservative
2 = Conservative
3 = OndemandX
NOTE: No matter what governor you use for suspend mode, if Battery Friend is enabled the second core will be turned off during suspend!
1.8 IVA Overclock
What is IVA OC?
IVA OPPs are controlling the CPU load for sound events. It could be useful (in some cases) when you get sound related laggs. Just set the maximum frequency to highspeed. This will allow more CPU power for sound events but also will cause higher battery consumption.
How to use IVA OC?
If you want to check the current IVA frequency. Just type in Terminal or ADB:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/iva_clock
You will get an output like this:
Code:
132 Mhz
2. You can whether enable IVA highspeed: 130 - 430 Mhz ["1"] or enable IVA normal speed: 130 - 332 Mhz ["0"]
320 Mhz max: echo "0" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
430 Mhz max: echo "1" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
1.9 DPLL Cascading
DPLL: Davis–Putnam–Logemann–Loveland (DPLL) algorithm
To get more info about this please see wiki
But to sum it up shortly: It helps to use/stream media (music) in a low power mode.
NOTE: DPLL Cascading will be available to be switched easily via Trickster Mod App soon!
How to switch DPLL?
DPLL is ENABLED by default!
Open Trickster Mod -> Speicific Tab --> DPLL (soon)
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/dpll/dpll_active
Turn on:
Code:
echo 1 > /sys/kernel/dpll/dpll_active
1.10 HDMI toggle
Some users are facing a RAZR-sepcific problem: HDMI cable is detected, even though there is no cable plugged!
Therefor I included a toggle to switch HDMI wether ON or OFF. Additinally there's an init.d script included within the AROMA Installer you can select during the installation of JBX-Kernel.
To enable/disable HDMI on-the-fy:
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/hdmi/hdmi_active
Turn on:
Code:
echo 1 > /sys/kernel/hdmi/hdmi_active
1.11 Intelli-Plug
For intelli-plug hotplugging is now only allowed when the device enters sleep.
To enable hotplugging universally just change the value of the following entry whether to 1 (on) or 0 (off):
Code:
sys/module/intelli-plug/parameters/int_hotplug
2. If anyone has the following issues:
Issue
Media Process FC
No SD-Card in File Explorer
My CPU Settings (frequencies, etc) won't be saved (it sets itself back to Kernel default after screen off)
My phone freezes/reboots always when I try to set options in Trickster Mod
The device is lagging very hard
Solution
Media FC: Open App settings, head to "Download Manager" and "Media Storage" and hit the "delete data" button. Reboot. Now it shouldn't give any FCs anymore and after a little bit of waiting it will find all Media (Pictures, Videos, etc..)
No SD-Card: Reboot into recovery, go to "Mounts & Storage", tick "mount int" or "mount ext".
USB: Make sure the screen is ON while plugging the cable in.
CPU Settings: This is a bug which cannot be solved at the moment. Temporary solution: In Trickster Mod just activate the "Frequency Lock" and your settings will persist.
Trickster Mod:: Open App settings, Trickster Mod and select "uninstal updates". Now it should work.
Crashes, Freezes, lagging, something doesn't work, etc
There are too many reasons which could cause crashes! So here is a checklist for you to look for. Check each point and try the following workaround:
- Your rom has CPU tweaks (e.g. Kernel modules, init.d folder, etc)
- You have set custom CPU settings (e.g. custom frequencies with apps like No-Frills CPU Control, Set-CPU, Antutu, etc...)
- You have undervolted too low
- You have overclocked too high
- You have applied higher "Core OC" value in Trickster Mod App
- You are running any other kernel tweaks which are regarding to the CPU and/or performance (e.g. Kernel modules by Whirleyes eventually set by init.d, etc..)
- After setting some settings (e.g. in Trickster Mod) your device doesn't boot anymore
- adb doesn't work / shows only "device offline"
- You are facing hard lagging
If any point here matches your setting, please revert from it:
- Remove any CPU init.d script from /System/etc/init.d
- Uninstall any CPU controling app (e.g. Set-CPU, No-Frills, etc..)
- Remove all extra kernel modules from system/lib/modules (e.g. cpu_control.ko, cpufreq_smartass2.ko, etc..)
- Unset any custom settings from any other kernel / CPU - tweaking app which is NOT Trickster Mod
- Maybe your governor causes issues. Hotplug is know for bugs at the moment...I'm going to fix it..
- NEVER set your CPU Settings (e.g. in Trickster Mod App) on boot!!!! - before you aren't sure that your settings are safe!!!
- You may flash the kernel again after reverting related settings
- to make adb work / show device online, download latest SDK platform-tools and confirm access on device (4.2 security feature of Android)
- Don't use any task killers, memory killers, seeder apps! They may conflict with the kernel/Rom settings.
If none of these suggestions work for you your rom may be incompatible. Please report it here that I can add the rom to the list of imcompatible roms
If you have any issue, please read this:
First check:
- is it really a kernel issue?
- did I see this bug with the roms original kernel?
- what are the people in the rom thread saying?
- what are the people in the kernel thread saying?
- can I find this issue on a bug list?
- how about my settings? Is it my fault it crashed?
- can I find something useful in the kernel FAQ?
- Is it maybe a well known issue and can be solved
withing seconds? Just like wifical.sh?
- Where to repeat that issue? Rom or kernel?
I know it's sometimes difficult to track the issues, and we can't know for sure if it's caused by the rom or by the kernel, but if you try at least to get some information you might find an answer sometimes. If you are able to understand logs, you may report whatever you find.
All this helps to keep the threads more clear. Thank you.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DONATE
If you like my work and want to support me, I'd enjoy a little beer or coffee. You can find my beer mug below my username
SOURCE
JBX-Kernel 4.4
CREDITS
Shurribbk - Co-Development
Kholk & [mbm] - Kexec inital Release
Hashcode & Dhacker - Making Kexec stable and initiating compatible kernels
Motorola - 3.0.8 Kernel Source
Surdu_Petru - Sharing Knowledge and helping with problems
nithubhaskar - Hints and answering my questions
Ezekeel, Imoseyon - Custom Voltage, Live OC, Temp Control, Gamma Control Source Code
faux123 - Some features, like Intelli-Plug, Intellidemand, Intelliactive
bigeyes0x0 - Trickster Mod App
Team Trickster - Great support and adding new features from my suggestions
Placca - Awesome kernel guide
RandomPooka - for special testing and support
- reserved -
Hey guys, welocme to JBX-Kernel for Targa! This is the first initial release and needs to be tested! Please give me some feedback if it boots and how it works for you. It comes with built-in OTA Updater and many extra stuff. Just check it out.
Keep in mind that this release will only work on 4.4 builds! Currently I don't have the time for others. Also you should use a newer build with Full HD Cam support! When using this kernel with older 4.4 builds your camera won't work.
Oh cool, i happy Someone help you with targa kernel ?
Maksim_ka said:
Oh cool, i happy Someone help you with targa kernel ?
Click to expand...
Click to collapse
Nope.. But it doesn't matter. Currently I have a problem with paying my server, and as long as I am able to build I wanted to release the Targa Kernel. The only difference seems to be in the CMD-line (Targa doesn't have a utags partition), so I just had to switch this line and build it with CM11 Targa sources to get the right ramdisk and modules. The whole source is the same like RAZR kernel.
I test it, and dont see weighty differences with RAZR kernel, have same bugs, display backlights don't turn on sometimes. I think you can talk with Hush about it, he can help.
Maksim_ka said:
I test it, and dont see weighty differences with RAZR kernel, have same bugs, display backlights don't turn on sometimes. I think you can talk with Hush about it, he can help.
Click to expand...
Click to collapse
You mean Hashcode? I am in static contact with him. But thx
What do you mean with "backlight doesn't turn on sometimes" ? I don't see this problem on RAZR... But sometimes you need to be a little patient when you want to wake it up. That's because of things like "DEEP IDLE" and others which keep the device in "deeper" sleep mode. It can take 1 or 2 seconds until you will see the lights - but it will turn on for sure. Maybe you're talking about something else? What bugs else exactly?
dtrail1 said:
You mean Hashcode? I am in static contact with him. But thx
What do you mean with "backlight doesn't turn on sometimes" ? I don't see this problem on RAZR... But sometimes you need to be a little patient when you want to wake it up. That's because of things like "DEEP IDLE" and others which keep the device in "deeper" sleep mode. It can take 1 or 2 seconds until you will see the lights - but it will turn on for sure. Maybe you're talking about something else? What bugs else exactly?
Click to expand...
Click to collapse
Yep, i mean Hashcode.
It will happened if use proximity sensor when calling, and sometimes when wake up phone. Backlight don't turn on generally, help only reboot. And it don't happened if change frequency to 300-1xxx. I think if you change minimal frequency to 300mhz it gone.
Maksim_ka said:
Yep, i mean Hashcode.
It will happened if use proximity sensor when calling, and sometimes when wake up phone. Backlight don't turn on generally, help only reboot. And it don't happened if change frequency to 300-1xxx. I think if you change minimal frequency to 300mhz it gone.
Click to expand...
Click to collapse
Well that's not an issue, but a well known phenomen. Some devices cannot handle 100 MHz (depends on silicon, each one is different). The min frequency is 300 by default, and the battery friend min frequency is 200 by default. Just check your settings in trickster mod.
Gesendet von meinem XT910 mit Tapatalk 4
I'm able to boot the kernel but cannot get radio. Any ideas?
Sent from my XT875 using Tapatalk
BZguy06 said:
I'm able to boot the kernel but cannot get radio. Any ideas?
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
Not yet. I need more informations from other users. Any feedback here????
Just try the today's OTA (soon). I forgot to update device tree sources in yesterday's builds.
Because I had a weird drain myself on yesterday's RAZR kernel (not very much, but noticable)
EDIT: I got a workaround for the RADIO issue - if it's actually an issue Wait for the OTA.
I was only able to get radio working on your 1-08 build of the kernel for rzr. Ever since then I haven't been able to get it to come up.
Edit: I went ahead and installed your 1-21 update and its better. It eventually connects to LTE but only holds it for 30 secs and then drops with no radio. Thanks for the help in advance.
Sent from my XT875 using Tapatalk
BZguy06 said:
I was only able to get radio working on your 1-08 build of the kernel for rzr. Ever since then I haven't been able to get it to come up.
Edit: I went ahead and installed your 1-21 update and its better. It eventually connects to LTE but only holds it for 30 secs and then drops with no radio. Thanks for the help in advance.
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
Please download the latest build from same links again (any mirror, I overwrote it). It should have fixed radio now. But you have to replace your build.prop with that one from your rom or open it and remove all additions made by JBX. The easiest way is to flash the rom again, then flash jbx.
I went ahead and redownloaded and reinstalled and I'm still getting the same thing. Attached is my "phone info" screen. And under "select preferred network" my only option is unknown
{
"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 XT875 using Tapatalk
Just flashed latest 1/21 JBX with cm 1/20. Have lte. Haven't played with settings yet. Need to read the faq first. Thanks void time buddy.
Sent from my XT875 using Tapatalk 2
BZguy06 said:
I went ahead and redownloaded and reinstalled and I'm still getting the same thing. Attached is my "phone info" screen. And under "select preferred network" my only option is unknownView attachment 2530635
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
So, have you reset your build.prop before as I said above?
Btw: just open it in a text editor (I.e. With root Explorer), scroll down until you see "dtrail - build.prop additions". Delete everything below that line. Now reboot and flash jbx (after downloaded again).
Gesendet von meinem XT910 mit Tapatalk 4
dtrail1 said:
So, have you reset your build.prop before as I said above?
Btw: just open it in a text editor (I.e. With root Explorer), scroll down until you see "dtrail - build.prop additions". Delete everything below that line. Now reboot and flash jbx (after downloaded again).
Gesendet von meinem XT910 mit Tapatalk 4
Click to expand...
Click to collapse
Yes. I went ahead and wiped system and data, installed cm11 1-20, and then installed the 1-21JBX targa kernel
Sent from my XT875 using Tapatalk
BZguy06 said:
Yes. I went ahead and wiped system and data, installed cm11 1-20, and then installed the 1-21JBX targa kernel
Sent from my XT875 using Tapatalk
Click to expand...
Click to collapse
Just flash the latest jb radio and don't change band in settings.
P.S. targa don't have BMM
Maksim_ka said:
Just flash the latest jb radio and don't change band in settings.
P.S. targa don't have BMM
Click to expand...
Click to collapse
I have the latest JB radio (CDMA_N_05.22.00R LTEDC_U_09.1D.00). My radio works fine using the stock CM11 kernel. I really wanna try out dtrails' work.
(PnP&Thermals tweak)battery saving and better performance for m8 100% working[ 11/8]
I'm not the dev
1st of all thanks to @ivicask for making this awesome tweak
Original thread :> http://forum.xda-developers.com/htc-10/development/pnpthermals-tweak-customized-profiles-t3411860
This is the better battery saving and performance tweaks ever I face best battery life after flashing this tweaks
This tweak originally for m10 and it's available on venum hub and m10 development thread i was tested this and it's work perfectly on m8 without any issues so I decided to bring to m8 users
bugs
Sorry no bugs
change logs
[*]
8.11.2016
v19:Fixed CPU dosnt drop to lowest speed for some users/kernels
- Merged v18 balanced changes into performance profile
working on cm 14.1 and old or gpe base rom and aosp,lyrs
22.09.2016
v18Balanced changes only)
- Adjusted CPU scheduler load distributions and frequencies in order to fix some stutters,
but also to save power while phone is idle with screen ON (drops to lower frequencies faster)
- Fixed weird HTC bug where task migration gets stuck in loop and cause phone to heat up for no reason
- (thermal file)Make it a bit cooler on higher loads
- Minor fine tuning here and there..
29.08.2016
v17: Prevent cores going offline if running Android auto (fixes lag on screen off)
[*]- (Balanced)Tweaked 15+ various governor and boost settings for even more power savings
[*]- (Balanced)Added more appps for CPU limiting profiles
[*]- Allow 4 threads for oat proces if PlayStore in focus(faster app install)
[*]23.08.2016
[*]v16:Merged latest HTCs changes realted to PokemonGo thermals
[*]- Removed 50 -> 60 fps boost on touch on performance profile(60fps locked now)
[*]- Forced 60 fps for YouTube and Google videos on balanced profile
[*]- Tweaked thermal file on balanced profile for better performance
[*]07.08.2016
[*]v15:Balanced and Performance profile update
[*]- Fine tuned values
[*]- Big cores go offline during screen off for Performance profile
[*]- Tweaked low memory killer values on both profiles,
[*] prevents often app reloading, which is waste of time and battery.
[*]04.08.2016
[*]v14:Balanced and Performance profile update
[*]- Implemented dynamic swappiness
[*]- Default swappiness reduced from 60 to 30 (less writes to nand)
[*]- During app launch or touching screen event swappiness is reduced to 0
[*]- During screen off swappiness is set to default 60 so it can do its job when we are not using phone
[*]- Increased dirty_ratio to reduce even more writing to nand
[*]- Overall goal is to reduce I/O on NAND while using phone and in that way improve performance,
[*] but also improve battery by better utilizing the 4gb RAM that this device has.
[*]- Added more apps for CPU limiting profiles(balanced only)
[*]v13:
[*]-Merged with changes from 1.9x base
[*](Mostly fine tuning battery saving for various video chat programs)
[*]v12:Balanced profile changes
[*]- Added more commonly used apps for lower power CPU profiles
[*]- More fine tuning
[*]v11:
[*]- Fine tuned balanced profile to prefer a bit more battery life
[*]- Cleaned up aroma installer (wont create unnecessary Venom folders for non-Venom users)
[*]v10:Balanced profile rebuild
[*]- Merged and fine tuned/adjusted thermal configuration from performance profile
[*]- Should improve responsiveness and fix stuttering on some apps that happend before
[*]- changed around 100+ lines of code, lazy to write full changelog
[*]v9:TEST balanced profile update
[*]- Big cores will now go fully offline during screen off and while in Extreme powersaver
[*]- Lowered screen refresh rate while in Extreme powersaver(even more saving)
[*]- Max GPU speed limited to 214MHZ while in Extreme powersaver
[*]- Max GPU speed limited to 510MHZ while in powersaver
[*]- Reduced app launch boost MIN frequencies speeds to 1.3gz for all cores.
[*]v8: complete rebuild of performance profile
[*] - Added extra 560mhz frequency step between 630 and 510 for GPU throttling
[*] - Added 5 additional throttling steps for each CPU cluster per temperature
[*] - Prevent big cores dropping to 1.3ghz too soon which drops FPS in games.
[*] - Prevent killing one big CPU core too soon, instead 2 will run at half migration performance.
[*] - Everything fine tuned and balanced, 10+ FPS boost in most games compared to stock
[*]v7
[*]- 1.8x base compatibility update
[*]v6
[*]-Removed battery saving profile as balanced does such good job, both smoothness and performance!
[*]v5
[*]-Many changes to balanced profile
[*]-Lowered app launch Max CPU speed locking to more reasonable levels(Still ramps up to max if load demands)
[*]-Reduced input boost duration a bit
[*]-Governor will now drop CPU to lower speeds faster
[*]-Added more apps to lower CPU speed profiles.
[*]v4
[*]-Aroma installer fixes
[*]-BatterySaving profile fine tuning
[*] Quote:
[*]This addon is designed to save some extra battery, and reduce heat.Magic is done in 2 files:
[*]1:Thermal-engine is tweaked in order to provide much better sustained performance and cooler phone, without big impact on performance.
[*]2np file is another key component, its HTCs CPU/GPU/EMMC/MODEM and many more control engine.Here many tweaks where done, but gonna quickly list some of the important ones:
[*]-Per app control, automatically suspends 2 BIG cores, and runs on 2 low power ones, it also limits the GPU speed to lowest.This will do only for some most commonly used apps, like Sense Prism, Nova launcher, Apex, other HTC apps, various chat programs(hangouts, facebook, messanger, whatsap etc), YouTube and some more.. as those apps dont require a lot power.
[*]-Screen off is set to 2 low power cores for nice standby times
[*]-Power saver is tweaked to actually save some power and not just lower screen brightness
[*]-Extreme powersaver is also tweaked down to save even more power
[*]-Input boost frequencies are also lowered (CPU ramps up moment you touch screen)
[*]-And alot of other minor tweakups..
[*]Also its recommended not to change anything CPU/GPU related in any other apps, like EX and just let this files do the job for you.
[*]If for some reason you dont like this mod or have any problems with it, installer includes revert to stock option
[*]
[*]Compatibility
[*]All 1,8x and 1.9x based roms and kernels(even stock).
[*]Not compatible with 1.5 or below bases (will cause random crashes), use Version v8 for older 1.5x and 1.2x bases
.work
Only on sense based rom like srom ,viper,sky dragon and other cm,aosp,gpe lyrs
[*]Download
[*]Version v19
https://drive.google.com/file/d/0B8deuP4KW_MgOUdjZGI2dGttZmM/view?usp=drivesdk
install
[*]
[*]1 Put file into internal or external SD card
[*]2 goto twrp recovery
[*]3 chose file and hit install
[*]4 reboot system and enjoy your phone's new battery life
[*]5 if twrp offer you to install superSU do not install
[*]Screenshots
[*]
{
"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"
}
. . .
Flashed and testing, thanks[emoji106]
Inviato dal mio HTC One M8 utilizzando Tapatalk
kalel77 said:
Flashed and testing, thanks[emoji106]
Inviato dal mio HTC One M8 utilizzando Tapatalk
Click to expand...
Click to collapse
Welcome
Woot!This cant possible work good, M8 pnp is totally different and works with on-demand governor with cores hotpluging while htc 10 works with interactive, not to mention all the settings i did in PnP are tuned to snapdragon 820 cores and memory management of that device (4gb).
Alo thermal file may not work properly and cause device to overheat(may)
.
You should verify what governor is currently active, i think its just broken and reverting to some default kernel or system settings.
BTW, M8 CPU management is already amazing so i never did special pnp mod for it.
ivicask said:
Woot!This cant possible work good, M8 pnp is totally different and works with on-demand governor with cores hotpluging, not to mention all the settings i did in PnP are tuned to snapdragon 820 cores and memory management of that device (4gb).
Alo thermal file may not work properly and cause device to overheat(may)
.
You should verify what governor is currently active, i think its just broken and reverting to some default kernel or system settings.
BTW, M8 CPU management is already amazing so i never did special pnp mod for it.
Click to expand...
Click to collapse
I tested and all working gud mybe bcoz of m10 port and no heat issues unfortunately I have less heating issues now than before BTW nothing broken or reverted to and it's so smoothie thanks for ur effort
ivicask said:
woot!this cant possible work good, m8 pnp is totally different and works with on-demand governor with cores hotpluging while htc 10 works with interactive, not to mention all the settings i did in pnp are tuned to snapdragon 820 cores and memory management of that device (4gb).
Alo thermal file may not work properly and cause device to overheat(may)
.
You should verify what governor is currently active, i think its just broken and reverting to some default kernel or system settings.
Btw, m8 cpu management is already amazing so i never did special pnp mod for it.
Click to expand...
Click to collapse
Well the Developer Knows Best, because he did it and he know what exactly he did, so can be placebo or even if its work some parts will some parts not like u know HTC 10 have different Hardware specs.
My Other question related to the HTC BUG is do anybdy found a Solution Tweak for the well know HTC BUG mostly all M8 M9 Devices after the MM update suck on the Battery the phone die at 20% 20+ something % and losing all settings when start from scratch its frustrating bug Ive tryed 100 Different kind of Calibration nothing help me out to fix this problem. sometimes Die at 25% battery Sometimes die at 10% battery without a warning!
tsalta said:
Well the Developer Knows Best, because he did it and he know what exactly he did, so can be placebo or even if its work some parts will some parts not like u know HTC 10 have different Hardware specs.
My Other question related to the HTC BUG is do anybdy found a Solution Tweak for the well know HTC BUG mostly all M8 M9 Devices after the MM update suck on the Battery the phone die at 20% 20+ something % and losing all settings when start from scratch its frustrating bug Ive tryed 100 Different kind of Calibration nothing help me out to fix this problem. sometimes Die at 25% battery Sometimes die at 10% battery without a warning!
Click to expand...
Click to collapse
Well this is a Battery problem not a bug I had same problem before i replaced battery so I think u have to change battery once
sayad1 said:
Well this is a Battery problem not a bug I had same problem before i replaced battery so I think u have to change battery once
Click to expand...
Click to collapse
Well i was thinking the same way untill i realize this heppand imideately after flashing MM and after this found out hundred of people with M8 as well M9 have absolutely the same issue stright after the MM update so this cant be co incident also i did chek my battery with several tools its in good health.
thats why i think its a HTC Bug.
tsalta said:
Well i was thinking the same way untill i realize this heppand imideately after flashing MM and after this found out hundred of people with M8 as well M9 have absolutely the same issue stright after the MM update so this cant be co incident also i did chek my battery with several tools its in good health.
thats why i think its a HTC Bug.
Click to expand...
Click to collapse
Did you replace battery I think u have to do if you believe trust me in my honest opinion it's battery problem my brother have same phone and he did same way like me so once u have to do . Before replacing battery I did all possible thing but nothing helped like celebration and more but finally get success on battery replacement
tsalta said:
Well the Developer Knows Best, because he did it and he know what exactly he did, so can be placebo or even if its work some parts will some parts not like u know HTC 10 have different Hardware specs.
My Other question related to the HTC BUG is do anybdy found a Solution Tweak for the well know HTC BUG mostly all M8 M9 Devices after the MM update suck on the Battery the phone die at 20% 20+ something % and losing all settings when start from scratch its frustrating bug Ive tryed 100 Different kind of Calibration nothing help me out to fix this problem. sometimes Die at 25% battery Sometimes die at 10% battery without a warning!
Click to expand...
Click to collapse
Only way you can try calibrate battery is by draining it fully until you can't even turn it on back via power button, than plug charger and leave it turned off while it charges to full. If it doesn't help its bad battery, as my sisters M8 works just fine with latest android and shuts down on around 1%..
GPE
Any chance of this coming to GPE roms?
sayad1 said:
View attachment 3912178
Click to expand...
Click to collapse
Hmm.
Sent from my HTC6525LVW using Tapatalk
Yap! Confirmed made mine faster ??
TIA @sayad1 and @ivicask ?
Can someone give me outputs of this shell commands while running this mod, also mention if your on stock or custom kernel.
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu2/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/class/kgsl/kgsl-3d0/gpu_available_frequencies
cat /sys/devices/system/cpu/cpu2/sched_budget
cat /sys/devices/system/cpu/cpu0/sched_budget
cat /sys/module/lowmemorykiller/parameters/minfree
cat /proc/sys/kernel/sched_upmigrate
cat /sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads
cat /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
cat /sys/class/mmc_host/mmc0/clk_scaling/enable
cat /sys/power/pnpmgr/apps/activity_trigger
We need this on GPE please
ivicask said:
Can someone give me outputs of this shell commands while running this mod, also mention if your on stock or custom kernel.
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu2/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/class/kgsl/kgsl-3d0/gpu_available_frequencies
cat /sys/devices/system/cpu/cpu2/sched_budget
cat /sys/devices/system/cpu/cpu0/sched_budget
cat /sys/module/lowmemorykiller/parameters/minfree
cat /proc/sys/kernel/sched_upmigrate
cat /sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads
cat /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
cat /sys/class/mmc_host/mmc0/clk_scaling/enable
cat /sys/power/pnpmgr/apps/activity_trigger
Click to expand...
Click to collapse
@ivicask
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor <
ondemand
system/cpu/cpu0/cpufreq/scaling_available_frequencies <
268800 300000 422400 652800 729600 883200 960000 1036800 1190400 1267200 1497600 1574400 1728000 1958400 2265600 2457600
system/cpu/cpu2/cpufreq/scaling_available_frequencies <
/system/bin/sh: cat: /sys/devices/system/cpu/cpu2/cpufreq/scaling_available_frequencies: No such file or directory
system/cpu/cpu0/cpufreq/scaling_available_governors <
tripndroid smartassV2 lagfree dancedance intellidemand wheatley adaptive intelliactive interactive conservative ondemand userspace powersave lionheart performance
cat /sys/class/kgsl/kgsl-3d0/gpu_available_frequencies <
600000000 578000000 462400000 389000000 330000000 200000000 100000000
cat /sys/devices/system/cpu/cpu2/sched_budget <
/system/bin/sh: cat: /sys/devices/system/cpu/cpu2/sched_budget: No such file or directory
at /sys/devices/system/cpu/cpu0/sched_budget <
/system/bin/sh: cat: /sys/devices/system/cpu/cpu0/sched_budget: No such file or directory
at /sys/module/lowmemorykiller/parameters/minfree <
10240,15360,22528,35840,49152,67584
[email protected]_m8:/ $ cat /proc/sys/kernel/sched_upmigrate
/system/bin/sh: cat: /proc/sys/kernel/sched_upmigrate: No such file or directory
stem/cpu/cpu2/cpufreq/interactive/target_loads <
/system/bin/sh: cat: /sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads: No such file or directory
stem/cpu/cpu0/cpufreq/interactive/target_loads <
/system/bin/sh: cat: /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads: No such file or directory
cat /sys/class/mmc_host/mmc0/clk_scaling/enable <
0
cat /sys/power/pnpmgr/apps/activity_trigger <
I am on ElementalX Repack 7.00.11
ivicask said:
Can someone give me outputs of this shell commands while running this mod, also mention if your on stock or custom kernel.
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu2/cpufreq/scaling_available_frequencies
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/class/kgsl/kgsl-3d0/gpu_available_frequencies
cat /sys/devices/system/cpu/cpu2/sched_budget
cat /sys/devices/system/cpu/cpu0/sched_budget
cat /sys/module/lowmemorykiller/parameters/minfree
cat /proc/sys/kernel/sched_upmigrate
cat /sys/devices/system/cpu/cpu2/cpufreq/interactive/target_loads
cat /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
cat /sys/class/mmc_host/mmc0/clk_scaling/enable
cat /sys/power/pnpmgr/apps/activity_trigger
Click to expand...
Click to collapse
R u going to do some changes for m8 hope ?
As expected, flashing HTC10 PNP breaks PNP and almost none of my settings are active, it still runs ondemand while entire htc10 pnp is coded to work with interactive...
I dont feel like taking sisters M8 to work on this, its not even rooted... or bootloader unlocked..
And as i said, i find M8 governor already perfectly fine coded HTC side..
confirmed working great on jw 5.4.0 A9 port.. battery lasted longer
thanks a lot..waiting for Blur Os new stable port