Related
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock so I have no choice to but to stay on stock kernel. I have no ext3/ext4 partition on my SD card in case you ask.
Current ROM: TB Fusion 1.1.2
Radio: 12.54.60.25U_26.09.04.11_M2
Any idea what should I do to solve this issue?
golokipok said:
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock
Click to expand...
Click to collapse
uoooo this is sooo dangerous for your handset... u can "smoke" it...
Any idea what should I do to solve this issue?
Click to expand...
Click to collapse
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
SERGI.3210 said:
uoooo this is sooo dangerous for your handset... u can "smoke" it...
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
Click to expand...
Click to collapse
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ). Is there any effect if I'm using smartass profile on those kernels I've mentioned?
golokipok said:
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ).
i hope that the processor works or not works (don´t crashes a little bit...)
but the reason of your freezes maybe (almost sure) because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
golokipok said:
there any effect if I'm using smartass profile on those kernels I've mentioned?
Click to expand...
Click to collapse
it´s possible, take this explanation, read and judge by yourself what´s the better cpu governor...
smartass (Best explanation i've found paraphrases to: based on interactive, but better.)
----
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
Click to expand...
Click to collapse
Thanks for the info
SERGI.3210 said:
because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
Click to expand...
Click to collapse
You have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Anyway, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
golokipok said:
have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Click to expand...
Click to collapse
you only should do a good over/underclock & set the correct cpu governor for your daily use....
well, you know ho is @MDeeJaay? the developer of MDJ kernels and roms...
he explained smartass with this words:
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245.
golokipok said:
, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
Click to expand...
Click to collapse
no, no buddy... i only show the max speed nothing more... i set my cpu concretly like this;
CPU GOVERNOR:interactive
MAX SPEED:1113 MHZ
MIN SPEED:245 MHZ
PROFILE: screen off; 245 MHZ max.
245 MHZ min.
in adition i´m going to modify my syg LOL
haha..thanks again. I'm gonna try playing with the frequencies to see which will suit me
i hope someone can make a stable 1.8ghz kernel without the freeze
IT´S POSSIBLE but i don´t want to try it LOL
i love a lot my DHD
Welcome to decimalman's kernel playground!
As the name suggests, dkp is a hodgepodge of features and tweaks that I wanted to play with. It should get excellent battery life without feeling sluggish. It doesn't come with its own tuner app, so pick your favorite. Personally, I like Trickster MOD and Kernel Adiutor, so I go out of my way to make things work in them. Most other apps should work, too.
Features:
Overclocking up to 2.1 GHz, but you'll need to increase your voltages to get there (if you can get there at all)
Underclocking down to 54 MHz, with stability improvements
Undervolting compatible with most apps
Fast charge without unplugging first
Glorious animations for the notification and softkey LEDs
Well-integrated erandom means you don't need CrossBreeder or Seeder (recent AOSP builds use ISAAC instead)
freelunch and tierservative governors for optimal battery life without sacrificing responsiveness
Automatic mpdecision and auto-hotplug are only enabled when needed
Adjustable minimum voltage for stability on finicky processors
Optimized UKSM to free up some extra memory
Code optimizations for size and speed
Compiler optimizations (-O3, LTO, and more) because faster is better
Donors: Thanks, everyone! Your generosity is much appreciated. :good:
drpenguino, 0xScott, vmancini3 (twice! :good, Ch4m3l30n, rompnit, Mystique, ryandubbz, techdog, ElwOOd_CbGp, ScOULaris, ZipAddict
Remember:
Nandroid!
last_kmsg and/or logcat or it didn't happen.
Other kernels have their own threads or forums. Discuss them there.
Image dumps (settings, battery life, whatever) belong inside [HIDE][/HIDE] (that's HIDE, if you're on the mobile app) tags.
Be silly. We're here to have fun.
Installation:
Reboot to recovery. I recommend that one recovery...you know, the one that flashes zips? I forget what it's called.
Flash dkp. Optionally, rename and flash dkp-vmin-XXX.zip (see below).
Reboot.
Undervolting:
Undervolting on dkp is more complex than other kernels. Some processors get unstable at lower voltages, so (like the stock kernel) dkp keeps the processor voltage above 1150 mV by default. I refer to this limit as the minimum voltage. In order to undervolt, you'll need to lower the minimum voltage: if you use Trickster MOD or Kernel Adiutor, just disable "Override Minimum Voltage", otherwise rename dkp-vmin-XXX.zip to e.g. dkp-vmin-600.zip (which would apply a 600 mV minimum voltage) and flash it. If this causes instability (crashes, audio/video glitches, etc.), try using dkp-vmin-XXX.zip to apply a higher minimum voltage (somewhere between 950 and 1050 mV seems to work well for most people).
Downloads:
MediaFire:
All Downloads
dkp-vmin-XXX.zip
Solidfiles (Make sure you have an adblocker!):
All Downloads
dkp-vmin-XXX.zip
Source: I'm always happy to see my code used, so cherry-pick away. I'll even put together feature patches if you ask nicely.
Bugs:
Let me know.
Stable changelog:
3/3/13: Initial release for d2spr. Didn't get around to making threads for other carriers.
4/8/13 (3.0):
FauxSound support
Strip more useless stuff
A few bonus optimizations
4/8/13 (3.4):
Port everything except erandom from 3.0
Enhance cpufreq for easier configuration
4/24/13 (3.4):
Bugfixes: better support for tuner apps, fixed potential SOD bugs, automatic mpdecision fixups, etc.
Lots of CM/CAF/Linux updates
Working AssWax governor
Trinity colors support
sio, zen I/O schedulers
erandom is back!
Built with a super-fancy Linaro GCC 4.8.1-dev compiler toolchain for maximum -O3 goodness
Probably lots more, but there's hundreds of commits to sort through...
5/29/13 (3.4):
Bugfixes: better overclocking support, better hwrng support, etc.
Updates: new CM updates, Linux 3.4.47, updated FauxSound driver, added invisiblek's new panel colors interface
Automatic auto-hotplug
New optimizations, including link-time optimization and an updated GNU+Linaro GCC 4.8.1-dev toolchain
6/14/13 (3.4):
Bugfixes: fix several critical bugs in the 5/29 release.
9/7/13 (3.4):
Fixes for OC, UV, auto-hotplug.
A few new optimizations.
Synced up with CM.
9/20/13 (TW):
Ported everything from AOSP to TW.
9/20/13 (4.3):
Merged 4.3 from CM into the existing 4.2 code.
Current experimental branches:
Nothing interesting at the moment.
Goodies:
dkp doesn't come with its own splash screen. However, the dkp installer (i.e. the install zip) is smarter than you think, and can apply a custom splash screen for you. Here's how:
Create a folder on your internal storage named "dkp"
Copy a PNG image into the directory, and rename it "splash.png". Alternatively, copy an RLE image (i.e. from a flashable custom splash screen zip) and rename it "splash.rle". Ideally, the image should be roughly 1280x720 to begin with, since it won't be resized.
The image will be used as your splash screen whenever you flash dkp. Reflash to apply initially.
mikedavis120 has put together a how-to video that covers tweaking dkp for optimal battery life. If you're new to dkp, take a look! He also put together a zipped collection of apps that will come in handy while tuning dkp. It also includes a flashable zip, "dkp-debug_v1.zip". After flashing it, running
Code:
su
dkp
from a terminal emulator will collect lots of useful debug information that will make it much easier for me to track down the issue you're having. :good: mikedavis120 recommends installing SuperSU (included in the zip) instead of what's included in you ROM.
sysfs:
It's possible to adjust all the settings available in dkp without using apps. Because they show up as files, settings can be adjusted with file managers, terminal emulators, adb and initscripts. Here's the most interesting files inside sysfs:
/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors (not available on newer AOSP builds): display tint (0 = very red, 2 = default, 4 = trinity colors)
/sys/class/misc/gammacontrol (only available on newer AOSP builds): various color controls. See this post for details on enabling Trinity colors on builds that use these controls.
/sys/devices/system/cpu/cpu<N>/cpufreq/UV_mV_table: voltage table
/sys/devices/system/cpu/cpu<N>/cpufreq/scaling_...: scaling_governor is the governor, scaling_min_freq and scaling_max_freq are the minimum and maximum frequencies, scaling_available_governors and scaling_available_frequencies show the available governors and frequencies
/sys/kernel/dkp/force_fast_charge: fast charge
/sys/kernel/dkp/link_core_settings: when linked (the default), frequency settings and some governors are automatically copied to the other core
/sys/kernel/dkp/vmin: minimum processor voltage in mV
/sys/kernel/mm/uksm/run: activate UKSM
auto-hotplug tuners:
These show up in the governor settings for any governor that doesn't do its own hotplugging. They only take effect when using auto-hotplug, so you'll probably need to disable mpdecision in Trickster.
hotplug_intpulse: when set to 1, automatically turns core 2 on whenever the screen/buttons/whatever is pressed. Default is 0.
hotplug_sampling_periods: number of samples to use for average number of running tasks. Default is 15.
hotplug_sampling_rate: number of 'jiffies' (currently 1 jiffy = 10 ms) between each sample of running tasks. Default is 20 (0.2 sec).
hotplug_enable_one_threshold: the average number of running tasks required to turn core 2 on, multiplied by 100. Default is 125 (1.25 tasks on average).
hotplug_disable_one_threshold: the average number of running tasks required to keep core 2 on, multiplied by 100. Default is 250 (2.5 tasks on average).
freelunch/nanolunch tuners:
freelunch and nanolunch aren't materially based on other governors, so their configuration is quite different than other governors. There's lots of tuners, since I haven't really decided on an ideal tuning. I encourage experimentation! I'll explain a bit of how these governors work before actually listing the tuners.
Generally speaking, there are two modes: in "normal" mode, sampling is done occasionally and frequency is generally increased slowly; in "interactive" mode, sampling is done much more quickly, and frequency increases much more quickly. "Interactive" mode ends after several samples of very low usage. The idea of a "hispeed" frequency is used in lots of governors, and it refers to the frequency that the CPU will jump to when more CPU usage is needed; generally, it's a generous estimate of how much CPU will be needed. Here, the hispeed frequency is adjusted on-the-fly, increasing when more CPU is needed and gradually decreasing when the CPU is idle. In "interactive" mode, the hispeed frequency is kept fairly high so that everything will feel snappy.
Hotplugging is taken care of in the least complicated (and in my opinion, most reasonable) way possible: if core 1 is using lots of CPU, and there are several tasks running (in other words, if it's likely that core 2 will have something to do), core 2 is turned on; if either core isn't doing much except using power, core 2 is turned off.
sampling_rate: the usual
hotplug_up_cycles: number of consecutive heavily-loaded samples before core 2 is turned on
hotplug_down_cycles: number of consecutive lightly-loaded samples before core 2 is turned off
hotplug_up_load: number of running tasks required to bring core 2 online
hotplug_up_usage: number of used CPU cycles (in thousands per second) required to bring core 2 online
hotplug_down_usage: number of used CPU cycles (in thousands per second) required on both cores to keep core 2 online
overestimate_khz: number of CPU cycles to overshoot usage by in "normal" mode
hispeed_thresh: if CPU usage is within this many cycles (in thousands per second) of the maximum frequency, frequency will be increased to the hispeed frequency. Generally, hispeed is pretty low in "normal" mode, and fairly high in "interactive" mode.
hispeed_decrease: when the CPU is sitting idle, the hispeed frequency is decreased by this amount each sample (this isn't ideal, but it works)
interaction_hispeed: the initial hispeed frequency when switching to "interactive" mode
interaction_return_cycles: number of consecutive lightly-loaded samples before returning to "normal" mode
interaction_return_usage: number of used CPU cycles (in thousands per second) required to stay in "interactive" mode
interaction_panic (nanolunch only): when set to 1, allows aggressively jumping past the current hispeed frequency under some circumstances
interaction_sampling_rate/overestimate_khz: equivalent to the "normal" versions of the tuners, these take effect in "interactive" mode
Just loaded it on pa 3.15
Sent from my SAMSUNG-SGH-I747 using xda premium
It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app
rmead01 said:
It doesn't say that it has morfic colors, but looks like it does. Gonna give it a whirl
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It doesn't, but I'll merge it and put out a test build.
decimalman said:
It doesn't, but I'll merge it and put out a test build.
Click to expand...
Click to collapse
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app
rmead01 said:
Is it possible they are left over from a previous kernel? Because I can def tell the difference usually and seems like it does.
Either way, advise when its updated. This governor seems solid so far.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae
Thnx for this kernel
decimalman said:
dkp is based off clean CM source, so it shouldn't have been merged already.
I've got test builds compiling now, and the 3.4 builds will be up shortly. Flashing the trinity-colors test build and this zip will enable trinity colors. You can toggle it with
Code:
su
echo X >/sys/class/mdnie/mdnie/trinity_colors
where X is 0 to disable or 1 to enable.
Edit: and sorry for taking so long to respond.
Edit 2: 3.4 builds are up. http://d-h.st/7Ae
Click to expand...
Click to collapse
Maybe I was just seeing things, had just watched jurassic park in 3d.
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
rmead01 said:
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
+1 on these questions
Sent from my AT&T Samsung Galaxy S III
rmead01 said:
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
Click to expand...
Click to collapse
Answered my own problem. I installed trickster as mentioned in OP and all voltage settings stick no problem with no issues.
rmead01 said:
New "test" build flashed as well as the file to enable it. Thanks for the addition. It's very hard to go back to normal once you've been smurfed depending on your display.
Only issue i'm having ATM is the ability to change the voltage table. My phone doesn't handle undervolting as well and i run a minimum of 950 baseline, if not 975. One of my normal apps wasn't able to set the voltage at all. I'm trying to use performance control which I don't like. It crashes trying to set the voltage on boot but at least I can go in and manually set the values on boot and they stick.
One last question, since this is your kernel, what scheduler do you recommend pairs well to freelunch? What would you use for performance and what would you use for batt?
Click to expand...
Click to collapse
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this into 3.0 and 3.4, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).
decimalman said:
Personally, I don't like trinity colors, but I definitely understand the appeal. I merged this in, so it'll be standard from here on. I'll add a link to the enabler zip in the OP as well.
What app would you normally use? I'll try to support it, since I already provide several voltage interfaces. I didn't realize performance control was crashing (I'm not a fan either, so I only lightly tested). I recently installed Trickster and liked it, so I've been going out of my way to support it. It's also really easy to write support for, so that's a bonus for me.
As for schedulers, I'm not fussy. I've never exhaustively tested performance and battery life, so I don't have a preference and usually run noop or deadline. However, I've had nothing but bad results with ROW (phone never deep sleeps, and I haven't looked into why).
Click to expand...
Click to collapse
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that figured out I removed kernel tuner. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point. just as an example, some governors would be better for screen on/off and tasker could switch these to edge out battery life.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both governor and voltage adjustments well. i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.
rmead01 said:
good to know. Trickster mod works fine and you mention it in the OP and it's at no cost in the play store. I wouldn't worry.
I was using an app called kernel tuner because some others would only set 1 core to the governor and not both. I checked that trickster does indeed set both cores to freelunch so once that was made it was no problem. Kernel Tuner also has the options for profiles which can be toggled in tasker for varies states. freelunch so far hasn't needed any changing so not worried about it at this point.
The voltage app i was using is simply called voltage control. Kernel tuner doesn't do a nice job of voltage changes. But since trickster does both well, i'm using that with no problems now.
Thanks for the morfic, having a way to toggle it works well for people. it's as simple as a script so there's that.
Click to expand...
Click to collapse
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Edit: I think I've got Voltage Control fixed. I should be able to get Kernel Tuner working without too much work. I haven't even looked into Performance Control yet.
decimalman said:
I meant to test Voltage Control but Google wasn't letting me download anything. It's a common app, so I'll try to get it working regardless. Kernel Tuner doesn't currently work well with freelunch, and tends to hang when it's trying to read settings in the CPU screen. Otherwise, it's a nice app. I didn't realize it had Tasker support (I use Llama).
I've added a few extra bits to the cpufreq core, so governors that need to be set on both cores (like freelunch) will automatically apply to both cores regardless of what app is used. cpufreq will even enable and disable mpdecision depending on whether a hotplugging governor is running (though Trickster won't show that it's disabled).
I owe ktoonsez for the toggleable trinity colors. I slightly rewrote his patch, but it's still largely his code. It's my policy that anything that not all users will want should be optional and easily configurable.
Click to expand...
Click to collapse
well good job so far. batt life has been top notch. minimal drain in use and my over night idle drain was only a few %. I have things setup to disable wifi when sleep and also turn off mobile data when wifi is connected. A bit over the top but every bit helps.
:good::highfive:
I know I've been grilling you today but...
Kind of curious what the new tunables do. I haven't touched anything since it's working so well but there is always that part of me that wonders what adjust parameters will do. Is there any kind of reference for this governor that could indicate that type of info?
Does your kernel support faux sound app?
stevehkim said:
Does your kernel support faux sound app?
Click to expand...
Click to collapse
Yes. 3.0 and 3.4 both have support.
As for tuneables, I've been meaning to post a writeup but haven't gotten around to it. You're not the first to ask about it.
Sent from my SPH-L710 using xda app-developers app
This is a fantastic Kernel! The battery life has been outstanding so far. Thank you for your amazing work!
Hi i have ARHD on my phone with the XM Kernel. I was slightly suprised in the Trickster MOD app, the max clock speed is 1.3ghz. Yes i know i can OC to 1.5 but im not sure what is setting this. When i had ARHD installed with stock kernel it was showing 1.3 as default. I assume that was set by the ROM. But i installed this kernel and still has 1.3 as the default.
Also the default govenor settings for the gaming one has the boost_freq set at 1300000, which is 1.3ghz, that can be changed to 1.5 also. But surely the boost freq would be the max freq no matter if you move the slider to 1.5 in the basic controls? But i would be suprised that the gaming govenor would underclock the cpu, surely for gaming you would want the phone maxed out?
Is this expected with the XM Kernel and the ARHD? And if so, is there any things i can change in the govenor settings to make sure it performs at absolute max?
It's kernel related; Xmisters' kernels since 188 have a hard cap(1.3Ghz) by default, but using trickster mod, or another o/c apk, you can raise it to the stock 1.5Ghz(tick 'set on boot' to ensure it stays at 1.5) The best settings are trial and error, tbh, I use touchdemand/sio though smartmax seems to be the best balance.
Thanks for the answer. i can change it to 1.5 easy enough, but if you look in the govenor control, the boost_freq is is set to 1300000. If i left it at that, would it prevent the cpu from going up to 1.5?
Danw20 said:
Thanks for the answer. i can change it to 1.5 easy enough, but if you look in the govenor control, the boost_freq is is set to 1300000. If i left it at that, would it prevent the cpu from going up to 1.5?
Click to expand...
Click to collapse
you have sleep (lowest CPU can go), ideal freq(the speed the CPU aims for while awake), touch poke (when you touch the screen), boost (what it boosts too to prevent lag) and max (CPU flat out)
Setting the boost to 1.3 will still allow the could to run at full speed.
Sent from my HTC One X using xda app-developers app
That makes sense, cheers. So its probably a good idea to leave it as it is then.
Here is a kernel Houstonn and I have been working on. It's based on Faux123 kernel for nexus 4, however, it has evolved into a "buffet" kernel. I keep choosing what i believe is the better interface / way of doing things in a choice of various way or what could give us better battery / performance. I'm trying to maintain a certain balance.
This version is for geehrc (Sprint/Internationnal) with the 13mp. If you have the 8mp phone (E973/E971/E970), use that thread : http://forum.xda-developers.com/showthread.php?t=2229742
I won't link to Faux123 kernel in the nexus 4 for the simple reason that 99% of the people don't read and on these 99% of people, a few will end up flashing nexus 4 kernel which mostly flash by partition number and not by partition name thus hard bricking their device.
Reason to at least try it :
CPU voltage table
Intellidemand and Wheatley governor added
All the block I/O scheduler
TCP Westwood algorithm
Faux123 sounds interface
Faux123 gamma interface (color control)
Newest Prima (wifi) driver.
In-kernel thermal watching
Msm_mpdecision (In-kernel OpenSource MPDecision)
Frandom module loaded at boot.
Thanks :
Houstonn
Faux123
Show-P1984
FranciscoFranco
Shelnutt2
XpLoDWilD
Thracky
Synergye
Exit_only
All the downloads will be here :
Use the geehrc version.
http://ribs.bbqdroid.org/houcha
My source are there :
https://github.com/chadouming/smoocha
Reserved post.
thanks chad and team.
first Impression is very nice.
great work
Nice work,as usual.
Will dl.right now
Sent from LG E975 pwd by CM 10.1
FransicoFranco Drivers
Thanks for making this kernel, it is much appreciated. I'm wondering where to get/enable the generic hotplug driver and the sound driver by FransicoFranco. Thanks.
I have a sprint lgog and I tried running the eos 4.2.2 ROM for a few days. The battery life was pretty bad compared to the lifeless ROM so I restored back to that. Anyways, will this kernel improve the battery life?
bowhunt2005 said:
I have a sprint lgog and I tried running the eos 4.2.2 ROM for a few days. The battery life was pretty bad compared to the lifeless ROM so I restored back to that. Anyways, will this kernel improve the battery life?
Click to expand...
Click to collapse
Try it and you will see. I am not giving comment on battery life.
On another note, Version ending with fs have faux sound instead of franciscofranco sounds interface
bowhunt2005 said:
I have a sprint lgog and I tried running the eos 4.2.2 ROM for a few days. The battery life was pretty bad compared to the lifeless ROM so I restored back to that. Anyways, will this kernel improve the battery life?
Click to expand...
Click to collapse
I've managed to get pretty comparable (not 100% sure) battery life on AOSP compared to Stock Roms. Not to speak for the developer but yes this will increase your battery life. The only thing is that there is a lot you can tweak which will have an effect on your battery life. This is what i do.
Turn mpdecision off. MPdecision is a hotplug driver made by qualcomm that can be disabled in AOSP. As of now its always active on stock roms. I'm still trying to figure out where to get the Francisco Franco hotplug drivers, which are prefered.
Underclock your cpu/gpu - I like to keep my max at 1026mhz and my gpu at 200mhz. I don't notice any significant lag.
Undervolt your cpu
Use a intellidemand/tune your on demand governor
Obviously wake locks come into play as well. I like to use better battery stats to see whats keep my stuff awake.
Finally keep your mobile data off when your not using it
Sorry if I'm just telling you stuff you know, just trying to be informative.
shuwoo said:
I've managed to get pretty comparable (not 100% sure) battery life on AOSP compared to Stock Roms. Not to speak for the developer but yes this will increase your battery life. The only thing is that there is a lot you can tweak which will have an effect on your battery life. This is what i do.
Turn mpdecision off. MPdecision is a hotplug driver made by qualcomm that can be disabled in AOSP. As of now its always active on stock roms. I'm still trying to figure out where to get the Francisco Franco hotplug drivers, which are prefered.
Underclock your cpu/gpu - I like to keep my max at 1026mhz and my gpu at 200mhz. I don't notice any significant lag.
Undervolt your cpu
Use a intellidemand/tune your on demand governor
Obviously wake locks come into play as well. I like to use better battery stats to see whats keep my stuff awake.
Finally keep your mobile data off when your not using it
Sorry if I'm just telling you stuff you know, just trying to be informative.
Click to expand...
Click to collapse
No more mpdecision. Msm_mpdecision in this kernel is different. It's opensource, in-kernel and doesnt force you to 1026mhz minimum freq,
chadouming said:
No more mpdecision. Msm_mpdecision in this kernel is different. It's opensource, in-kernel and doesnt force you to 1026mhz minimum freq,
Click to expand...
Click to collapse
sweet. I was using fauxclock to control my cpu. I am a little confused on msm_mpdecision
is msm_mpdecision the generic hotplug driver by FranciscoFranco?
Is there a more appropriate app than fauxclock to use?
If I disable mpdecision in fauxclock, does that automatically enable msm_mpdecision?
shuwoo said:
sweet. I was using fauxclock to control my cpu. I am a little confused on msm_mpdecision
is msm_mpdecision the generic hotplug driver by FranciscoFranco?
Is there a more appropriate app than fauxclock to use?
If I disable mpdecision in fauxclock, does that automatically enable msm_mpdecision?
Click to expand...
Click to collapse
Nope, msm_mpdecision is not franciscofranco hotplug drivers. I had franco driver before and it lagged too much. Also, there is no mpdecision at all. I remove the executable on installation of houcha. Seems as fast as mpdecision without the locking the minimum freq to 1026Mhz.
chadouming said:
Nope, msm_mpdecision is not franciscofranco hotplug drivers. I had franco driver before and it lagged too much. Also, there is no mpdecision at all. I remove the executable on installation of houcha. Seems as fast as mpdecision without the locking the minimum freq to 1026Mhz.
Click to expand...
Click to collapse
cool, just for some feedback I feel that there definitely is a difference in my processor states when I enable/disable mpdecision in fauxclock.
When it's enabled, the first core sits at 384mhz until i touch the screen, then the first two cores jump to 1026mhz or 1516mhz.
When I disable it my first core sits at 384mhz and jumps up to 700-1100mhz when I touch my screen, the other cores stay quiet.
In both circumstances I'm using Intellidemand governor.
As long as I'm bugging you, My gpu frequencies are a bit wonky. It goes to 400mhz on boot. When I lower it to 128mhz it will sit at 128mhz and not jump up no matter what max frequency or governor I reset it to.
shuwoo said:
cool, just for some feedback I feel that there definitely is a difference in my processor states when I enable/disable mpdecision in fauxclock.
When it's enabled, the first core sits at 384mhz until i touch the screen, then the first two cores jump to 1026mhz or 1516mhz.
When I disable it my first core sits at 384mhz and jumps up to 700-1100mhz when I touch my screen, the other cores stay quiet.
In both circumstances I'm using Intellidemand governor.
As long as I'm bugging you, My gpu frequencies are a bit wonky. It goes to 400mhz on boot. When I lower it to 128mhz it will sit at 128mhz and not jump up no matter what max frequency or governor I reset it to.
Click to expand...
Click to collapse
Try downloading the newest version. fs version have faux sounds, others have franco sounds. I believe faux app read gpu freq incorrectly. If you swipe tab (which is gpu demanding compared to stay to same tab) you will see the gpu freq actually lower.
Is voodoo sound a hardware issue, or can it be added to a kernel?
Sent from my LG-LS970 using xda app-developers app
saramon said:
Is voodoo sound a hardware issue, or can it be added to a kernel?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
No voodoo sounds for that hardware.
Lg optimus G on sprint. Thanks for the kernel! I'm getting a bit of screen flickering on latest cm 4/22, disabling WH overlays fixes the issue.
Sent from my LG-LS970 using Tapatalk 2
Everything is running smooth on the latest AT&T CM10.1 from Shelnnut, however my phone had an SoD due to notification light.
Known bug.it's been talked on canadian thread and i think on at&t and sprint too...
Sent from LG E975 pwd by CM 10.1
Thanks a ton for this, my battery life has improved quite impressively!
Request/Suggestion:
add gallimaufry governor
I'm not sure what sounds to use, does anyone want to explain the differences? (I'm using faux right now but considering trying out franco since I use the franco updater app to control everything)
i've been using this phone for about 2 years now and recently moved (about a few months ago) to using a custom rom (crdroid 7.1.2). it was running smooth and cool until day the clockspeed decided to lock itself at 2000 MHz (checked using cpu-z). I do not know if this is normal but the phone's temperature goes up to 36C on idle. i thought the problem was with the Lspeed app (+custom kernel) so i uninstalled it but it didn't work. I also factory resetting it, but still not luck. will updating the firmware resolve my issue? if not, what other available solutions are there?
have you thought about flashing the stock kernel ?
Fytdyh said:
have you thought about flashing the stock kernel ?
Click to expand...
Click to collapse
I have, but it still gets hot
do you use a case ? does your phone goes over 45 degrees celsius when charging ?
Fytdyh said:
do you use a case ? does your phone goes over 45 degrees celsius when charging ?
Click to expand...
Click to collapse
I do use a case, but hasn't been this hot before recently, and it does tend to hit 40C when charging
topsecretasian said:
I do use a case, but hasn't been this hot before recently, and it does tend to hit 40C when charging
Click to expand...
Click to collapse
If you are using Fast Charging, that heating is entirely normal (happens to me too)
But heating during idle is not normal. Try changing CPU governor to something else. (like schedutil or powersave)
Canny1913 said:
If you are using Fast Charging, that heating is entirely normal (happens to me too)
But heating during idle is not normal. Try changing CPU governor to something else. (like schedutil or powersave)
Click to expand...
Click to collapse
Do you know how to change cpu governor? I tried doing it last night but didn't find a whole lot of information. Schedutil seems to just set it all the way to 2ghz, so I want to change it to powersave
topsecretasian said:
Do you know how to change cpu governor? I tried doing it last night but didn't find a whole lot of information. Schedutil seems to just set it all the way to 2ghz, so I want to change it to powersave
Click to expand...
Click to collapse
use Rootify, select the CPU tab located at the top then change it.
The app sometimes gets stuck at Loading screen though.
Canny1913 said:
use Rootify, select the CPU tab located at the top then change it.
The app sometimes gets stuck at Loading screen though.
Click to expand...
Click to collapse
ok so it does work when i change the cpu govenor, but the only option that actually works is 'powersave' (as well as 'userspace'). all the other ones still sets it to 2GHz. 'userspace' seems to have a somewhat of an improvement but it's only setting everything to a constant value. is there a way have it set to balanced mode?
topsecretasian said:
ok so it does work when i change the cpu govenor, but the only option that actually works is 'powersave' (as well as 'userspace'). all the other ones still sets it to 2GHz. 'userspace' seems to have a somewhat of an improvement but it's only setting everything to a constant value. is there a way have it set to balanced mode?
Click to expand...
Click to collapse
powersave forces the processor to work in the lowest frequency availible, thus consuming less power.
userspace allows the app to set the CPU frequency whatever it wants. This isn't supposed to be used in Android since changing CPU speed thorough an app is super uncommon.
Others like ondemand normally keep the power low but starts using the higher frequencies if a processor intensive app is launched.
You can learn which governors do what in this post so you can set the most suitable one for you.
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com
Canny1913 said:
powersave forces the processor to work in the lowest frequency availible, thus consuming less power.
userspace allows the app to set the CPU frequency whatever it wants. This isn't supposed to be used in Android since changing CPU speed thorough an app is super uncommon.
Others like ondemand normally keep the power low but starts using the higher frequencies if a processor intensive app is launched.
You can learn which governors do what in this post so you can set the most suitable one for you.
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com
Click to expand...
Click to collapse
I see. Well I guess it does work as a solution.
Thanks for the help!