This thread was created to try to consolidate all the issues from Faux123's thread, since he started looking into the information I will quote some of his posts here.
I am trying to get to the bottom of this issue and see if we can get this resolved so we can get proper kernel support. Since currently Kernels that are available only appear to affect one CPU and its governor.
Below is a list of commands you can run from ADB and report the issue
(make sure to include the ROM, Kernel, and command output)
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_cur_freq
cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/online
cat /sys/devices/system/cpu/cpu1/online
----------------------------------------------------------------------
So here are some to the posts between me and Faux123 about the issue with further detail.
BrokenWall said:
So I installed your latest kernel on Senseless 1.3
Settings: MIN and MAX set to 1512Mhz with Performance gov
When running CF-Bench and letting it run I ran the following commands in an ADB Shell.
Code:
#cat /sys/devices/system/cpu/[COLOR="Red"][B]cpu0[/B][/COLOR]/cpufreq/scaling_cur_freq
1512000
#cat /sys/devices/system/cpu/[COLOR="Red"][B]cpu1[/B][/COLOR]/cpufreq/scaling_cur_freq
972000
#cat /sys/devices/system/cpu/[COLOR="Red"][B]cpu1[/B][/COLOR]/cpufreq/scaling_cur_freq
384000
#cat /sys/devices/system/cpu/[COLOR="Red"][B]cpu0[/B][/COLOR]/cpufreq/scaling_governor
performance
#cat /sys/devices/system/cpu/[COLOR="Red"][B]cpu1[/B][/COLOR]/cpufreq/scaling_governor
ondemand
Also you have to run a test that will stress both cores, because CPU1 doesn't show available unless under load, so benches like Quadrant don't even stress the second CPU
Click to expand...
Click to collapse
BrokenWall said:
The issue is that MSM8260 is not the same style Symmetric CPU that Tegra and SGSII use, instead the MSM8260 is a asymmetric multiprocessing unit. if you watch the CPU1 cur freq during benchmarking you will see that it will never hit the maximum speed of 1512Mhz
During linpack the score for multi-threaded goes up but it does not go in line with what should be possible at the proper speeds.
...
I have been testing this multiple times, I am not a developer nor do I claim to be. But I can tell you I know hardware, and I research the issues, and this issue is related to any kernel at the moment by ANY dev.
Click to expand...
Click to collapse
==================
Quote from Fuax123 after he looked into the issue.
faux123 said:
Ok, you are correct. I finally got my lazy ass off the chair and downloaded available snapdragon documentations online (I Hate qualcomm for making it so difficult to find any technical information regarding their chipsets). This is a quote from the document: "The 8x60 incorporates an asynchronous dual CPU core SMP (aSMP) micro-architecture"
I hate Qualcomm for trying to say their chipset is better than > SMP chipset yet they still use the acronym aSMP to confuse people What da heck is "asynchronous dual CPU core SMP", this is the absolute WORST BS marketing term....
Anyways, I am still blaming the OC apps (SetCPU, CPUMaster, OC Daemon etc) for not correctly set the CPU scaling properties for the 2nd CPU. Maybe all the authors for these apps were as confused as me by STUPID Qualcomm marketing terms and thought they were dealing with SMP but in fact, they were dealing with 2 separate independent CPUs on a single die. One can simply do:
Code:
echo smartass > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
to set the cpu1's scaling governor to the same governor as CPU0 so both cpus can operate using "similar" governors for better "synchronous" operations.
Maybe you should contact the authors for the OC apps and have them fix their apps I am not sure what needs to be fixed on the kernel side...
Click to expand...
Click to collapse
And the final note:
BrokenWall said:
So I tried this, you are unable to modify or create this file while CPU1 is asleep. Our problem is that the way the SoC is that no matter if you do it manually or with any overclock software, it will not affect CPU1 speeds.
We need to find a way for CPU1 to stay awake, or else we will just have a single fast core and a second core at default speeds..
I tried creating the files needed to set the CPU1 speed directly and it deleted them after the CPU went asleep.
Code:
while at idle on homescreen:
cat /sys/devices/system/cpu/cpu0/online = 1
cat /sys/devices/system/cpu/cpu1/online = 0
underload on CF-Bench:
cat /sys/devices/system/cpu/cpu0/online = 1
cat /sys/devices/system/cpu/cpu1/online = 1
after bench is over back on homescreen:
cat /sys/devices/system/cpu/cpu0/online = 1
cat /sys/devices/system/cpu/cpu1/online = 0
While the benchmark was running I was able to change the profile for the governor but was unable to manually overclock the CPU and even running any of the apps while the CPU1 was online still failed to set a speed.
I think it may be in fault to the software as well as HTC kernel drivers as well.
Click to expand...
Click to collapse
faux123 said:
I just read through kernel SMP and CPU Hot plugging. It seemed there might be a bug in CPU hot plugging for SMP operations (esp for such strange beast as the new aSMP snapdragons). Hot plugging support was originally designed as a fail safe for removing failed CPUs in a CPU farm, but recently, it has been used in SMP systems where they used the hot plugging capability to actively add/remove CPUs as means of power saving by talking an idling CPU "off line". According to Linux kernel documentation, the use of this feature for SMP power management was never intended and it is an on going experimental feature.
I briefly looked at the kernel cpufreq driver and saw nothing obvious. One way of resolving the cpu1's randomness with governors and scaling frequencies is to DISABLE the hot plug feature and just have cpu1 running at all times (idling is considered running) rather than declare cpu1 to be offline completely. The bug seemed to be when restoring the cpu1 back online, the governor and scaling frequencies are NOT restored properly (but from the kernel code, it looks fine the way the code was written. The kernel driver tried to restore the governor and frequencies from a saved data structure).
Click to expand...
Click to collapse
faux123 said:
It turned out it is not as easy to disable hotplug cpu from SMP. The kernel source has made some assumptions that if SMP is enabled, hotplug must be enabled. This has let to a few compilation errors. I am making edits to the kernel source to separate the 2 without breaking anything. Once I am able to cleanly separate them, I will make a test kernel with cpu hotplug disabled while SMP is running.
Click to expand...
Click to collapse
faux123 said:
I just read thru the entire MSM clocking / Power management code... Whew!
The aSMP dual core CPU is not as straight forward as the old single core CPU in terms of Overclocking. It is a lot more complicated than simple frequency edits and setting the max frequencies. The new AVS (adaptive-voltage scaling, Power management all try to mess with the clocking scheme). All current overclocking schemes for this CPU have bugs and issues including mine (kanged from cayniarb).
I will revert all existing OC technique from my source code and start from scratch!
BTW, all CPU overclocking utilities have issues with this aSMP CPU. They will screw up the CPU1's governor and min/max frequencies, essentially crippling your dual core CPU to having only CPU0 switching properly and the other core (CPU1) will be stuck @ 972 MHz max with random governor running.
My recommendation for now. DO NOT use any overclocking app (SetCPU, CPUMaster) until either either the kernel is patched correctly or the apps are updated to work with aSMP CPU's quirkiness. Also the only governor that is patched correctly to work with the new aSMP CPU is the OnDemand Governor, all other governors have not been patched properly including my newly patched SmartAss governor. Further patches are required for the other governors to function properly with this new STRANGE beast
Click to expand...
Click to collapse
So this is a thread to bring attention to all developers so we can try to get to the bottom of this. The reason is that I see people on the forums talking about benchmarks and this and that.
Goals is to see if we can get the second core to stay on. if not, see if we can at least get the second core to abide by the OC and Governor settings.
As of right now the best kernel to use is the HTC Stock kernel, since it uses Ondemand by default for both cores. Other governors haven't been patch for proper aSMP support.
you can see the performance possible in the following post: http://forum.xda-developers.com/showpost.php?p=16976335&postcount=28
This is very interesting reading!
You might be also interested in one entry in ramdisk init.pyramid.rc
service mpdecision /system/bin/mpdecision --no_sleep --avg_comp --single_core_while_panel_off
user root
disabled
mike1986. said:
This is very interesting reading!
You might be also interested in one entry in ramdisk init.pyramid.rc
service mpdecision /system/bin/mpdecision --no_sleep --avg_comp --single_core_while_panel_off
user root
disabled
Click to expand...
Click to collapse
Is this an option we can set outside of the RAMdisk and reboot? via ADB or terminal emulator?
BrokenWall said:
Is this an option we can set outside of the RAMdisk and reboot? via ADB or terminal emulator?
Click to expand...
Click to collapse
No, you need to change it in ramdisk and flash the whole boot.img otherwise if you remove --single_core_while_panel_off it will be back after reboot.
BTW --single_core_while_panel_off was added in the latest 1.45 update, in 1.35 it was only:
service mpdecision /system/bin/mpdecision --no_sleep --avg_comp
user root
disabled
mike1986. said:
No, you need to change it in ramdisk and flash the whole boot.img otherwise if you remove --single_core_while_panel_off it will be back after reboot.
BTW --single_core_while_panel_off was added in the latest 1.45 update, in 1.35 it was only:
service mpdecision /system/bin/mpdecision --no_sleep --avg_comp
user root
disabled
Click to expand...
Click to collapse
The problem that I have found on both 2.3.3 and 2.3.4 is that CPU1 turns off while idle at homescreen, not unless an application can stress both cores or the load gets heavy enough does CPU1 wake.
CF-Bench will bring CPU1 alive at the start of the bench and even register two cores, where the crappy Quadrant will only notice 1 core and will not always wake the second core.
And I noticed this problem with Faux123 Kernel, Unity Kernels (both 2.3.3 and 2.3.4 versions), and there was a third kernel that was affected. I am going to start checking other kernels. But it appears that all kernels based on HTC Source are setup this way and its over looked.
If someone could try building a test kernel with the listed changes it would be appreciated and I would be willing to test it and report the changes in this thread.
This is very interesting. I think with some research and a resolution this could greatly increase performance of the cpu and the battery. With both cores dividing the stress when needed and then only using one core while in idle or screen off could greatly improve battery life. I have a desk job and am always bored and testing things on my phone so I will be glad to test and return with any info I find. I'm subscribed.
I am so excited to see this issue get resolved cause I also noticed how CPU1 turns off all the time and it irritates me.
I'm a power user, so regardless of battery life I just want both my CPUs to always stay on at max freq.
mike1986. said:
No, you need to change it in ramdisk and flash the whole boot.img otherwise if you remove --single_core_while_panel_off it will be back after reboot.
BTW --single_core_while_panel_off was added in the latest 1.45 update, in 1.35 it was only:
service mpdecision /system/bin/mpdecision --no_sleep --avg_comp
user root
disabled
Click to expand...
Click to collapse
I'm glad you put your attention to this immediately Mike. Cause your ROM is already amazing anyway and I can't wait to see it work with new kernels using better dual-core support.
@ OP: I agree the best kernel is the stock one, unfortunately the 2.3.4 stock kernel has a major bug that screws up 3D gaming. So if one wants to play games, you need to use a custom kernel otherwise you will notice horrid graphic rendering (i.e. Cordy)
Like faux123 noted, ive been doing a lot to rewrite and clean up the acpuclock-8x60.c file -- the frequency/voltage tables in particular, but really large pieces of it as well. There are some interesting items in there and nearby (mach-msm .h files) that may prove helpful here -- can't think of them off the top of my head and im not able to look right now, but this is *definitely* something i want to help resolve.
Qualcomm was always up front (e.i. liked to brag) about theirs being the first (and currently only) asynchronous dual-core chip for ARM. I've kinda been afraid that this was the issue all along and really just tried avoiding looking for it...
Intel and AMD chips are all (or i think all) asynchronous, so there should be no shortage of code to look at for this (granted, not *exactly* what we want, but thats the fun, right?).
Please come find me on IRC and get me off my a$$ to work on this.
I am so super busy currently with my real work, I haven't looked at it since my last conversation with brokenwall. I have a new scheme of overclocking which is completely different from the current scheme and it is actually a lot simpler. I was burned out by XDA last weekend and still suffering the effects of it. I finally fixed the FAIL source issue from LG G2x's recent GB source release so my G2x users finally have a stable OC/UV kernel for their stock GB ROM.
Sensation is next in line for me to spend my time on... Don't rush me or ask me when it will be done because I don't know it myself. I have the new scheme pretty much mapped out in my head already, I just need to code it and test it. Again, when I need beta testers, I will ask for them, but until them I don't need volunteers yet....
faux123 said:
I am so super busy currently with my real work, I haven't looked at it since my last conversation with brokenwall. I have a new scheme of overclocking which is completely different from the current scheme and it is actually a lot simpler. I was burned out by XDA last weekend and still suffering the effects of it. I finally fixed the FAIL source issue from LG G2x's recent GB source release so my G2x users finally have a stable OC/UV kernel for their stock GB ROM.
Sensation is next in line for me to spend my time on... Don't rush me or ask me when it will be done because I don't know it myself. I have the new scheme pretty much mapped out in my head already, I just need to code it and test it. Again, when I need beta testers, I will ask for them, but until them I don't need volunteers yet....
Click to expand...
Click to collapse
In no way was this setup to rush you, I just didn't feel right pointing everyone to your thread for reference. So I felt we needed a single thread for this issue. Now we have a place where multiple devs can share the ideas and where people like myself can test and report back.
Thanks for this info! So its bad to use smartass like insert coin do it? Very interesting thread I hope we can fix that
Just ran the commands you mentioned this is my output I had to start many apps to get cpu 1 alive it was off the most time i am using the latest insertcoin ROM ... Is it better to not use smartass for next time ?
384000
1188000
1188000
smartass
1
384000
1188000
1188000
ondemand
1
Sent from my HTC Sensation Z710e using XDA Premium App
This is awesome to see! I really want to keep my sensation and was getting pretty frustrated with it. It's always good to see real collaboration in action. Thanks guys for all you do! I know TDJ was messing with this stuff too and we (him hacking/coding and me flashing and testing since he doesn't have this device) were testing out a few different iterations of the stock kernel with smartass etc. This has been a good read. Wish I could help in any other way besides offering up my device for your testing pleasure, but alas i am no dev just a power user haha.Thanks again folks
Sent from my HTC Pyramid
faux123 said:
I am so super busy currently with my real work, I haven't looked at it since my last conversation with brokenwall. I have a new scheme of overclocking which is completely different from the current scheme and it is actually a lot simpler. I was burned out by XDA last weekend and still suffering the effects of it. I finally fixed the FAIL source issue from LG G2x's recent GB source release so my G2x users finally have a stable OC/UV kernel for their stock GB ROM.
Sensation is next in line for me to spend my time on... Don't rush me or ask me when it will be done because I don't know it myself. I have the new scheme pretty much mapped out in my head already, I just need to code it and test it. Again, when I need beta testers, I will ask for them, but until them I don't need volunteers yet....
Click to expand...
Click to collapse
Thanks Faux, we're in good hands with you.
Wow. After actually running the cat commands, what you guys are saying finally makes sense to my non-coding brain. BrokenWall, I know you met some resistance in some of the dev threads on this issue, but just know that those of us who understand really appreciate that you're trying to spread the awareness.
Faux, Cayniarb and all of the devs who spend their spare time looking into stuff like this, thank you. We place our devices in your capable hands.
FiddleGoose said:
I am so excited to see this issue get resolved cause I also noticed how CPU1 turns off all the time and it irritates me.
I'm a power user, so regardless of battery life I just want both my CPUs to always stay on at max freq.
Click to expand...
Click to collapse
Lol. You can do nothing faster than anyone!
Sent from my HTC Sensation 4G using XDA Premium App
Great news..
And,
while at idle on homescreen:
cat /sys/devices/system/cpu/cpu0/online = 1
cat /sys/devices/system/cpu/cpu1/online = 0
underload on CF-Bench:
cat /sys/devices/system/cpu/cpu0/online = 1
cat /sys/devices/system/cpu/cpu1/online = 1
after bench is over back on homescreen:
cat /sys/devices/system/cpu/cpu0/online = 1
cat /sys/devices/system/cpu/cpu1/online = 0
Click to expand...
Click to collapse
When playing games,sometimes i felt laggy,so is it dual core when playing games?
faux123 said:
Sensation is next in line for me to spend my time on... Don't rush me or ask me when it will be done because I don't know it myself. I have the new scheme pretty much mapped out in my head already, I just need to code it and test it. Again, when I need beta testers, I will ask for them, but until them I don't need volunteers yet....
Click to expand...
Click to collapse
No rush faux... Take your time. We all know how busy you are and are Greatful you have plans in store for the Sensation.
I still run your BFS LV Kernal in my MT4G and it is fast as hell!! It will beet the sensation in Quadrant runs hands down every time. it will be nice to have both Cores OC/UV, but there is no need to rush, it will come soon enough.
Thanks for all you do for us faux, we appreciate it.
UPDATE
I was given a test kernel for 2.3.3 roms and got CPU0 and CPU1 to both run successfully through multiple benchmarks at 1890Mhz, scores were very nice and to give you an idea. Linpack Multithreaded scored a 97
Related
Read the thread before posting bugs or issues or questions
Table of contents:
Intro
Features/what this includes
Quirks of the kernel
Why it's labeled unstable
Disclaimer
Latest kernels
Methods of flashing
Benchmarks!
Instructions for using swap
Governor exlainations
Governor strategies
Recommended apps
Locating cpu% Eaters && other negative items towards battery life
FAQ!
Changelog
Stable/safe voltage kernels
Notes
Source
Credits
Old links, go here for other aosp roms with older video drivers & older builds
Intro: I'm scaryghoul
What this includes
It's scary!
Swap
Deadline I/o scheduler
Extreme undervolt
Overclocked & underclocked values
Sleepers disabled
Toast's new video drivers
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of toast's kernel)
Quirks of this kernel:
Sometimes when changing speeds with something like setcpu, they take a few seconds to actually clock to that speed, turning the screen on and off fixes it and clocks it right away though.
I would advise against using the speeds 66mhz->180mhz during real usage. It's a little laggy, but works =)
This doesn't work with sense based roms like mikshift, yes it needs to be said more than once
Why it's labeled unstable: So I don't get people poking me in the eyes with spoons if/when it freezes up. It actually works quite well, but since I heavily undervolted an undervolted kernel, it is bound to not be 100% stable(It is about 90% stable =P)
Disclaimer: What everyone else puts in kernel threads, about me not being responsible, ect.
Latest kernels
The voltages of the superUV will not work for everyone, if they don't work for you, then try the builds labeled stable
Recommended speeds 245-800mhz or 245-1ghz on scary governor && no setcpu profiles - I'll keep my current speeds in my signature.
Mirrors of kernels uploaded by VICODAN
Super SUV
http://www.mediafire.com/?47perl0d43n1nyr
Super Stable kernel
http://www.mediafire.com/?9qmtzuu35cpr8yz
Super Girly kernel
http://www.mediafire.com/?1s4z4y7bh78e04j
Methods of flashing
Joeykrim's "flashimage gui" app on the market using one of the zImage files from the zips. http://forum.xda-developers.com/showthread.php?t=1045797
Teamwin's "Kernel manager" app on the market. http://forum.xda-developers.com/showthread.php?t=1030500
Flashing via recovery using one of the zips here.
Benchmarks! - All done at 1.8ghz on cm7
Quadrant standard 1.1.7 - 3900 is the highest I've seen so far I believe.
Smartbench(2runs) - 2150/1850 - Mine were around there
Linpack(3runs) - 61, 63, 63 - These won't change much at all.
Instructions for using swap
For a swapfile do something like this.
dd if=/dev/zero of=$Swapfile bs=1048576 count=$Size
Where $Swapfile is the location of the file you want, and $Size is the amount of mb for swap you want to use.
Then type
mkswap $Path
swapon $Path
Replacing $Path/$Size with your own values of course, so if I wanted 20mb of swap I'd execute the commands
dd if=/dev/zero of=/sdcard/swapfile bs=1048576 count=20
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/smartass-governor-info ) - "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 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Governor strategies
Conservative - Upthreshold 85, downthreshold 60
Smartass - Sleep max 245760Hz, Ramp up at 384000Hz at a time, up threshold 90, downthreshold 60
Scary - Upthreshold 80, down threshold 45, sleep max 245760Hz, sleep min, 122880Hz
Recommended apps =)
Nofrills - App to manage I/O scheduler, clock speeds & governors.
Adw ex or go launcher ex
Colorize widgets - Great widgets to replace the lpp ones for those converting to other launchers.
AppMonster(pro or free) - Great backup utility, automatically backs up all apps.(I like it better than TB)
GPS Status - Great application for finding satalites near you and helping get a quick lock.
Any go dev team app - Great dev team, all their apps are worth looking at.
Frequently asked questions
Question: My phone is boot looping/not booting on the released suv, what do I do?
Answer: Your phone cannot handle the super undervolted values, you will need to flash the stable undervolted kernel or girly kernel
Question: My phone's graphics are running really lagishly, why is this happening? It worked fine on version 1.4 and before.
Answer: You are likely running an outdated version of your rom not supporting the new video drivers in version 1.5+, you will need to roll back to v1.4 and before
Question: My phone is running slow on the batterysave or scary governors, what do I do?
Answer: Set your minimum speed higher, those governors spend a lot of time at the lowest values
Question: My wifi/wifitether and other stuff is broken and wasn't before I flashed your kernel
Answer: READ THE BIG BOLD STATEMENT AT THE TOP OF THE THREAD THAT SAYS THIS IS NOT FOR SENSE
Question: How do I flash this?
Answer: You probably shouldn't be flashing a kernel labeled unstable if you don't know how
Question: I'm not getting the amazing battery life/benchmark scores that others are getting
Answer: Well, every device is different, so you may not be able to score as high as some others, but you should get close at least, and the battery completely depends on usage patterns
Question: My phone can't clock to 1.8ghz, or some of the other higher values but does fine on the lower ones
Answer: Every device is different and not all can handle the same speeds/voltages, you are probably better off staying away from the higher speeds, I enabled the speeds but hope that you all are mature enough to handle them
Locating cpu% eating applications.
When in ADB shell type the following
top |grep app
or if your rom supports it htop is much better(Without grep, so just "htop")
Then look for items with high amounts of cpu% while the phone is idle.
changelog:
Release1:
Swap support enabled
Unlocked 1.6-1.8ghz
Superundervolted
Release 2(1.1):
Unlocked 3 new underclock values
Took the undervolt farther.
Release 3(1.2):
Added hw3d
Release 4(1.3):
Removed interactive governor since it only causes trouble
Overall undervolt taken farther. May be unstable for some
Release5(1.4)
Disabled sleepers
Changed kernel name
Added an alternative voltage kernel
Release 6(1.5)
Cleaned up the source
Updated to toastcfh's new video drivers, greatly improved video performance and fixed a lot of issues with aosp video. - Thanks toast =D
Release 7(1.6)
Still cleaning up source
Addeed smartass governor && tweaked it, Down thresh: 70, up: 90
Added a real kernel name
Added lulz
Added two new clock speeds && modified voltage table
Tweaked conservative governor(Should be less erradict now, so scaling less==less power consumption==Yay =D)
Release 8(1.7)
Added Scarygov 0.5
Removed userspace governor
Release 9(1.7.2)
Tweaked scarygov to 0.6, removing a bug
Release 10(1.7.3)
Fixed a lag issue on scary governor by slightly optimizing the code.
Tweaked smartass.
Release 11(1.8)
Optimized scary governor's code
Safe voltage kernels && Stable kernels(come here if you can't handle the super undervolt
NEW VIDEO DRIVERS
1.8
ScaryKernel 1.8 stable http://dl.dropbox.com/u/15373824/ScaryKernel1.8safe.zip
Girly Kernel 1.8 stable http://dl.dropbox.com/u/15373824/GirlyKernel1.8safe.zip
1.7.3
ScaryKernel v1.7.3 stable http://dl.dropbox.com/u/15373824/ScaryKernel1.7.3Stable.zip
v1.7.2
ScaryKernel v1.7.2 safe uv http://dl.dropbox.com/u/15373824/Scarykernel1.7v2Safe.zip
v1.6
[UNTESTED]1.8Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/ScaryKernel1.6SafeJesusNoSleep.zip
v1.5
[UNTESTED]1.8Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/Scarykernel1.5StableJesus.zip
[UNTESTED]1.5Ghz safe voltage no sleepers http://dl.dropbox.com/u/15373824/Scarykernel1.5StableNoJesus.zip
OLD VIDEO DRIVERS(1.4) - For roms that don't support the new video drivers.
1.5Ghz safe voltage kernel no sleepers http://dl.dropbox.com/u/15373824/ScarykernelSafe1.5NoSleepers.zip
1.5ghz safe voltage kernel, sleepers enabled http://dl.dropbox.com/u/15373824/ScarykernelSafe1.5Sleepers.zip
1.8ghz safe voltage kernel, no sleepers http://dl.dropbox.com/u/15373824/ScarykernelSafe1.8NoSleepers.zip
1.8ghz safe voltage kernel, sleepers enabled http://dl.dropbox.com/u/15373824/ScarykernelSafe1.8Sleepers.zip
Notes:
Nothing for now.
Here is the source code for this build. I'll try to maintain it, I have a lot of kernel sources, but this will always be the latest release code, unless I state otherwise.
https://github.com/Scaryghoul
Credits: Toastcfh/bcnice20 - For 99.8% of their kernel source.
Dogejcr/Preludedrew - For helping me get my laptop setup for kernel compiling.
Testers - For flashing this even though it says unstable :-X
JoesephMother - For helping me unlock the new lower clock values && other kernel related matters =)
x99percent - I used his middle clock speeds between the 3xx->7xx values as a base(edited voltages) as well as used his smartass source.
I just got my shifty two days ago from having the heroc. It took me a full five minutes to root the sob. This kernel clocking it to 1.8ghz is sick. Good job!
On my Gingerbreaded Evo-Shifted Premium XDA App.
Nice work again scaryghoul. Quadrant scores are very reflective of real-world performance in this case.
Awesome numbers coming off this kernel.
Quadrant = 3104
SmartBench 2011 = 2095/1887
SmartBench numbers were incredible!!!!
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
crump84 said:
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
Click to expand...
Click to collapse
Just curious but what rom?
Sent from my PG06100 using XDA App
I used 1.5 SUV no sleepers and the responsiveness of the screen lags while scrolling in adw. I flashed back to the stock #29 on N#32 and the lag is gone
Sent from my PG06100 using XDA Premium App
CrashV2010 said:
I just got my shifty two days ago from having the heroc. It took me a full five minutes to root the sob. This kernel clocking it to 1.8ghz is sick. Good job!
On my Gingerbreaded Evo-Shifted Premium XDA App.
Click to expand...
Click to collapse
Glad you can handle it.
smoothtaste said:
Nice work again scaryghoul. Quadrant scores are very reflective of real-world performance in this case.
Click to expand...
Click to collapse
Thanks =O
jjb61 said:
Awesome numbers coming off this kernel.
Quadrant = 3104
SmartBench 2011 = 2095/1887
SmartBench numbers were incredible!!!!
Click to expand...
Click to collapse
Thanks for sharing here =)
crump84 said:
It was unstable for me.. 1.8 frozen my phone and it wouldn't even boot up when I tried 1.5
Click to expand...
Click to collapse
What rom and which kernel....
threeFiftyLi said:
I used 1.5 SUV no sleepers and the responsiveness of the screen lags while scrolling in adw. I flashed back to the stock #29 on N#32 and the lag is gone
Sent from my PG06100 using XDA Premium App
Click to expand...
Click to collapse
Interesting. Never had that issue, what range of speeds are you using?
JKILO said:
Just curious but what rom?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Scaryghoul said:
What rom and which kernel
Click to expand...
Click to collapse
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
crump84 said:
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
Click to expand...
Click to collapse
Kernels before 1.5 aren't meant for the newest Cm.
1.5+the testing ones with the New video drivers, are the ones meant for it.
Scaryghoul said:
Kernels before 1.5 aren't meant for the newest Cm.
1.5+the testing ones with the New video drivers, are the ones meant for it.
Click to expand...
Click to collapse
Well I guess that would explain why I was having issues..
crump84 said:
Well I guess that would explain why I was having issues..
Click to expand...
Click to collapse
Version 1.5+ is meant for cm7's nightlies from 31+.
When I first tried it, I felt a little lag but after I wiped it ran better than before.
Scaryghoul said:
Interesting. Never had that issue, what range of speeds are you using?
Click to expand...
Click to collapse
Stock default 245/1200.
I'll try to wipe and start fresh when I have time. I started Nightly #27 freshly wiped but haven't wiped since.
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Edit: flashed release 1.5 uv 1.8ghz and it was acting up as well, on release 1.4 @ 1.8 ghz and the phone is really smooth, very fast and very stable. On a side note my performance numbers blow compared to the cm7 numbers, 1400/1400 smart bench, 48 avg linpack and like 2k on quadrant.....?
Sent from my PG06100 using XDA App
threeFiftyLi said:
Stock default 245/1200.
I'll try to wipe and start fresh when I have time. I started Nightly #27 freshly wiped but haven't wiped since.
Click to expand...
Click to collapse
Okay.
DWake014 said:
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Try one of the earlier kernels then, there might be some sort of aosp framework change required to take use of the new video drivers, I can't confirm it without hearing from toastcfh but that's why I say v1.5+ is for cm7 nightly31+.
I may be completely wrong about it though.
DWake014 said:
Just flashed the 1.8 kernel with the new video drivers and its a little funky on the latest evervolv. My phone can do 1.8 stable but it is probably the video drivers acting up, gonna flash the uv kernel next
Edit: flashed release 1.5 uv 1.8ghz and it was acting up as well, on release 1.4 @ 1.8 ghz and the phone is really smooth, very fast and very stable. On a side note my performance numbers blow compared to the cm7 numbers, 1400/1400 smart bench, 48 avg linpack and like 2k on quadrant.....?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Edit for your edit.
Yes, as I just said I think there might be some sort of framework change required/recompile of evervolv to support the new drivers.
Are you sure the speeds are taking? As described in the quirks, it takes a few seconds to take a speed for some, and sometimes requires screen off/on. I usually don't benchmark until linpack hits 60+
crump84 said:
The latest Cyanogen build, tried both Release 3 1.5ghz and Release3 1.8ghz. I downloaded them last night, I may have to tried the newest release.
Click to expand...
Click to collapse
I thought that was the problem
Sent from my PG06100 using XDA App
Ran some more tests, this is on Evervolv with release 1.4. Set it on 1.8/1.8 performance and:
Linpack (12 runs): avg 61, few 62s
quadrant free ( 8 runs) : avg ~2600, high was 2900
smartbench (7 runs) : avg 1800/1800, high of 1800/1900
Scaryghoul said:
Okay.
Try one of the earlier kernels then, there might be some sort of aosp framework change required to take use of the new video drivers, I can't confirm it without hearing from toastcfh but that's why I say v1.5+ is for cm7 nightly31+.
I may be completely wrong about it though.
Edit for your edit.
Yes, as I just said I think there might be some sort of framework change required/recompile of evervolv to support the new drivers.
Are you sure the speeds are taking? As described in the quirks, it takes a few seconds to take a speed for some, and sometimes requires screen off/on. I usually don't benchmark until linpack hits 60+
Click to expand...
Click to collapse
I think you're right on Evervolv cause mine from yesterday works great but my testkern.a2 is crap on there.
Nice job on the undervolting. I couldnt even boot the newest one! As always, appreciate your help with all my n00b questions.
Toasted by Nightly.
DWake014 said:
Ran some more tests, this is on Evervolv with release 1.4. Set it on 1.8/1.8 performance and:
Linpack (12 runs): avg 61, few 62s
quadrant free ( 8 runs) : avg ~2600, high was 2900
smartbench (7 runs) : avg 1800/1800, high of 1800/1900
Click to expand...
Click to collapse
Thanks for sharing =D
smoothtaste said:
I think you're right on Evervolv cause mine from yesterday works great but my testkern.a2 is crap on there.
Nice job on the undervolting. I couldnt even boot the newest one! As always, appreciate your help with all my n00b questions.
Toasted by Nightly.
Click to expand...
Click to collapse
Thanks =)
---------------------------------------------------
1.6 is out for the unstable voltage.
I'll compile the stable ones later, already made the commits to the github for what I can remember I changed
Check the changelog people =D
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Link to bcnice20's 1.5ghz kernel: http://forum.xda-developers.com/showthread.php?t=941728
If that doesn't work, try flashing over his 1.8ghz kernel(This is what worked for me, bcnice, if you want me to take down this link just let me know.) - http://thebcblends.com/shift/kernels/Sense-1.8ghz-bfq-test1.zip
Table of contents:
Intro
Features/what this includes
Why it's labeled unstable
Disclaimer
Latest kernels
Instructions for using swap
Governor exlainations
Governor strategies
Recommended apps
Locating cpu% Eaters && other negative items towards battery life
FAQ!
Changelog
Stable/safe voltage kernels
Notes
Source
Credits
Intro: I'm scaryghoul.
What this includes
Swap
BFQ I/o scheduler
Extreme undervolt
Overclocked & underclocked values
HW3D enabled
Sleepers disabled
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of bcnice20's kernel)
Why it's labeled unstable: So I don't get people poking me in the eyes with spoons if/when it freezes up. It actually works quite well, but since I heavily undervolted an undervolted kernel, it is bound to not be 100% stable(It is about 90% stable =P)
Disclaimer: What everyone else puts in kernel threads, about me not being responsible, ect.
Latest kernels
The voltages of the superUV will not work for everyone, if they don't work for you, then try the builds labeled stable
Recommended speeds 245-800mhz or 245-1ghz on scary governor && no setcpu profiles
Scarykernel 1.8 suv - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Suv.zip
Scarykernel 1.8 stable undervolt - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Instructions for using swap
For a swapfile do something like this.
dd if=/dev/zero of=$Swapfile bs=1048576 count=$Size
Where $Swapfile is the location of the file you want, and $Size is the amount of mb for swap you want to use.
Then type
mkswap $Path
swapon $Path
Replacing $Path/$Size with your own values of course, so if I wanted 20mb of swap I'd execute the commands
dd if=/dev/zero of=/sdcard/swapfile bs=1048576 count=20
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/smartass-governor-info ) - "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 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Governor strategies
Conservative - Upthreshold 85, downthreshold 60
Smartass - Sleep max 245760Hz, Ramp up at 384000Hz at a time, up threshold 90, downthreshold 60
Scary - Upthreshold 80, down threshold 45, sleep max 245760Hz, sleep min, 122880Hz
Recommended apps =)
Zdbox - Great toolbox app, just don't let it run in your notifications bar, it's a cpu eater
Setcpu/Nofrills - Apps that help manage your cpu/profiles/ect.(I don't use them but they're pretty okay)
Perfect system or Elixer widgets - Widgets that monitor battery, current, cpu%, cpu speed, and more(Great for battery guru's)
Adw ex - Smoothest/fasted/lightest ratio in a launcher I've seen so far, and least cpu intensive(for me that's a big thing so the cpu scales less)
Colorize widgets - Great widgets to replace the lpp ones for those converting to other launchers.
AppMonster(pro or free) - Great backup utility, automatically backs up all apps.(I like it better than TB)
GPS Status - Great application for finding satalites near you and helping get a quick lock.
Any go dev team app - Great dev team, all their apps are worth looking at.
Frequently asked questions
Question: My phone is boot looping/not booting on the released suv, what do I do?
Answer: Your phone cannot handle the super undervolted values, you will need to flash the stable undervolted kernel
Question: My phone is running slow on the batterysave or scary governors, what do I do?
Answer: Set your minimum speed higher, those governors spend a lot of time at the lowest values
Question: How do I flash this?
Answer: You probably shouldn't be flashing one of my kernels if you don't know how(Mine are unstable =P)
Question: I'm not getting the amazing battery life/benchmark scores that others are getting
Answer: Well, every device is different, so you may not be able to score as high as some others, but you should get close at least, and the battery completely depends on usage patterns
Question: My phone can't clock to 1.8ghz, or some of the other higher values but does fine on the lower ones
Answer: Every device is different and not all can handle the same speeds/voltages, you are probably better off staying away from the higher speeds, I enabled the speeds but hope that you all are mature enough to handle them
Locating cpu% eating applications.
When in ADB shell type the following
top |grep app
Then look for items with high amounts of cpu% while the phone is idle.
Changelog
v1.8 - Initial kernel release for sense
Safe voltage kernels
v1.8
Scarykernel 1.8 stable - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Notes:
No I can't take the overclock any higher, I think everyone who's had a chance to take a crack at this source has tried, and going any higher seizes up after a few seconds.
Here is the source code for this build. I'll try to maintain it, I have a lot of kernel sources, but this will always be the latest release code, unless I state otherwise.
https://github.com/Scaryghoul
Credits: bcnice20 - For 99.8% of his kernel source.
Dogejcr/Preludedrew - For helping me get my laptop setup for kernel compiling.
Testers - For flashing this even though it says unstable :-X
JoesephMother - For helping me unlock the new lower clock values && other kernel related matters =)
x99percent - I used his middle clock speeds between the 3xx->7xx values as a base(edited voltages) as well as used his smartass source.
I see nobody else has chimed in on this kernel yet.. I will install Mikshift tomorrow and report my findings.
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Yeah both versions don't work on mine.
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
ozzie1p said:
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you flash over bcnice20's kernel?
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Thanks for clarifying that, I took down the links until we can get this working on several devices.
ozzie1p said:
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you try both of them over bcnice20's 1.5ghz? Not everyone can handle the suv one.
edit: Links back up! I need some testers to try the fix at the top.
Ya, I flashed right over the top of bc's. Ill try these new ones.
Sent from my PG06100 using Tapatalk
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
PaulB007 said:
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
Click to expand...
Click to collapse
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Scaryghoul said:
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Click to expand...
Click to collapse
Whats the suspected culprit?
ozzie1p said:
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
PaulB007 said:
Whats the suspected culprit?
Click to expand...
Click to collapse
I don't know so much for the freezes, but I believe that the booting has to do with me using my old voltages, and sense handling things differently than aosp >.<
I'll redo the voltage table later.
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
notsointeresting said:
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
Click to expand...
Click to collapse
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
Ah ok that sucks was really hoping for it but I understand thanks for the fast reply
Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
The ndk from google's web site has the toolchains needed to build gb kernel in it. The dl isn't terribly huge.
Sent from my PG06100 using XDA Premium App
What I have here is a VERY BETA kernel built from the latest LeeDrOiD git with some ondemand tweaks to make it a bit more responsive, as well as AXI Scaling, an undervolted bottom end at 122mhz, and with a topend of 2016mhz.
Many phones may not run at the full upper-end, but vddsys is implemented as in the LeeDrOiD kernel, so you may increase or lower the VDD by 25 for 20160000mhz to attempt to get it working.
Currently working on getting a github page up with this source. I'm running it on the Unity rom at the moment without issue. 2016mhz should only be used for benchmarks, and not 24/7.
Two way call recording is also included, as well as a startup script to run at 1843mhz ondemand at startup.
Changelog:
June24-Initial Release...Working on Cleanup.
GitHub Page: https://github.com/synergydev
Will work on marking changes shortly. It should also be of note that because my GF's phone seems stable at [email protected], I changed the voltage at 2016 to 1.5 on the git just because it seems my phone likes high voltages.
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
LorD ClockaN said:
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
Click to expand...
Click to collapse
I'm using 1.525V at 2016, however my DHD could never run the 1.9986 in your kernel without a voltage bump (could undervolt all the way up to 1.8 however though). In this kernel, I needed to up the AXI clock at 2016 to even get it to run, let alone benchmark continuously. I still haven't been able to get it to scale with a minimum under 300mhz.
This is why I recommend reducing the VDD at that speed by 25 if anyone's DHD can't run it.
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
synergye said:
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
Click to expand...
Click to collapse
+1 on that, but don't think you're more enthusiastic when talking about OC
We can argue about that the whole day
looking forward for your git!
I think 1.2G is enough..
@LorD ClockaN: if that's an sense kernel, you know what you have to do
Your 2016 MHz ASOP kernel coming soon?
with friendly greet
starbase64
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Tryng with virtuous sense 3 and it makes lag the sense but for the rest is quiet good
Edit: after some time the lags disappears and all is perfect now
where source code?
u canT post kernels on XDA without source code
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
tolis626 said:
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
Click to expand...
Click to collapse
Mine has voltage till 1.525 via vdd
Sent from Desire HD with CyanogenLordMod!!!
adwinp said:
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
Click to expand...
Click to collapse
really?
lol
Why do you explain to me?
m-deejay said:
really?
lol
Why do you explain to me?
Click to expand...
Click to collapse
Oohoo... Dev fight!! LOL
Sent from Desire HD with CyanogenLordMod!!!
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Lizzo said:
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Click to expand...
Click to collapse
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Ace42 said:
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Click to expand...
Click to collapse
uuuggghhhh... how do i raise the min b4 startup?
Lizzo said:
uuuggghhhh... how do i raise the min b4 startup?
Click to expand...
Click to collapse
echo 806400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
On adb you have to change the min freq while booting up. 800 might work. Or use 1305600 [1.3GHz].
This is madness, yes i know people will post no this is sparta, but seriously, anything over 2ghz i personally wouldn't test
adwinp said:
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Click to expand...
Click to collapse
PMSL Benchmarks mean fuk all tbh do not reflect real world peformance running at 1.8/1.9ghz stuff like Playstation emulator etc run far much smoother and with no slowdowns etc... newbs and benchmarks lol!
I am new to all this, first Android phone I have had and first time I have installed custom roms etc... Anyways I installed a new ROM and it has Daemon Controller installed but I don't have a clue how is all works so I want to know what are the best settings to have. Obviously I want better battery life and good performance. Current settings are:
Wake Min: 122000
Wake Max: 1152000
Wake Gov: ondemand
Sleep Min: 122000
Sleep Max: 384000
Sleep Gov: conservative.
My phone has Android 2.3.5 HTC Sense 3.0.
Thank you.
xPeterJx
Desire S Q&A
For all of your questions relating to the HTC Desire S
Seeing as you seem to have trouble reading and understanding basic english, this is where this should have been posted.
In seriousness though, use smartass or smartassv2 as it scales the cpu up and down when needed and when the phone demands the extra processing power. Maybe decrease the max wake speed to something around the 1Ghz point.
Google is also your best friend when asking these sort of questions as there is almost about 100+ posts on this throughout the forum.
zeekiz said:
Desire S Q&A
For all of your questions relating to the HTC Desire S
Seeing as you seem to have trouble reading and understanding basic english, this is where this should have been posted.
In seriousness though, use smartass or smartassv2 as it scales the cpu up and down when needed and when the phone demands the extra processing power. Maybe decrease the max wake speed to something around the 1Ghz point.
Google is also your best friend when asking these sort of questions as there is almost about 100+ posts on this throughout the forum.
Click to expand...
Click to collapse
So would you suggest removing Daemon Controller and using smartass(v2) instead?
I have looked on Google and I found posts regarding other phones not Desire S, but I'm not too sure what I'm looking for.
P.S. Don't think there was any need for 'Seeing as you seem to have trouble reading and understanding basic english, this is where this should have been posted.' But thanks for your advice.
xPeterJx said:
So would you suggest removing Daemon Controller and using smartass(v2) instead?
I have looked on Google and I found posts regarding other phones not Desire S, but I'm not too sure what I'm looking for.
P.S. Don't think there was any need for 'Seeing as you seem to have trouble reading and understanding basic english, this is where this should have been posted.' But thanks for your advice.
Click to expand...
Click to collapse
Is there an option to change the on-demand governor in oc controller? Because it should atleast give you a few options.
Also which ROM/Kernel are you using?
Also there was plenty of need for what I said, probably not as sarcastic and blunt as it was put, but it gets the point accross as this is a question thread. Also due to the more aggressive nature of said sentence the point has been reacted to, hence you have spent more than a split second thinking about it, hence next time you post a thread similar your memory may retain and regress on what I've said ;-).
But if you wanted it to be a general thread you could have sneakily read worded what you said, I'm not offering any "tasters" though.
zeekiz said:
Is there an option to change the on-demand governor in oc controller? Because it should atleast give you a few options.
Also which ROM/Kernel are you using?
Click to expand...
Click to collapse
Yes there's a few options: SavagedZen, Scary, virtuous, smartass, interactive, conservative, userspace, ondemand, performance.
Should I presume that the smartass setting is what you meant?
Rom: Saga3D V3 http://forum.xda-developers.com/showthread.php?t=1230029
Kernal: HYPERION-V1.2.
(If you think there is better ROMS or Kernals I'm open to suggestions, I'm sure I'll be able to find the appropriate thread with instructions how to install etc.)
ROMs:
As for ROMs I would highly recommend Lowveld's Endymion Sense 3.5 Runnymede Port for the HTC Desire S. The ROM is excellent in all aspects, and gives the user exactly what they need for their daily demands. Battery life is excellent, 18 hours 30% remaining. Lowveld, the developer frequently answers questions and is very active in the development of his ROM.
Installation?
If you have 4EXTRecovery (If not I highly recommend either downloading the free recovery control application, which will install it for free, or if you wish to assist the developer, 4EXT Recovery Control it has a lot of additional features and benefits.)
Perform a full wipe; system/data/boot/cache.
Format to EXT4 (If you aren't already).
Flash the zip.
OC Daemon
Virtuous = Smartassv2
I use Virtuous for both wake/sleep and 460800/1075200 min/max frequency. I used to use 245000, but I found occasionally when the phone would wake, it would lag a little on the GUI (but that was me personally, so I increased it from 245000 to 460800, without any real damage to battery life).
More information on the different governors.
RJackson said:
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
to.
Click to expand...
Click to collapse
FerretAD said:
As explained by MDJ:
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. No need for sleep profiles any more!
Click to expand...
Click to collapse
Information stolen from, http://forum.xda-developers.com/showthread.php?p=9277771#post9277771 information obtained by http://www.google.com.au/#sclient=p...,cf.osb&fp=be0328f6eeb3802d&biw=1920&bih=1060.
zeekiz said:
ROMs:
As for ROMs I would highly recommend Lowveld's Endymion Sense 3.5 Runnymede Port for the HTC Desire S. The ROM is excellent in all aspects, and gives the user exactly what they need for their daily demands. Battery life is excellent, 18 hours 30% remaining. Lowveld, the developer frequently answers questions and is very active in the development of his ROM.
Installation?
If you have 4EXTRecovery (If not I highly recommend either downloading the free recovery control application, which will install it for free, or if you wish to assist the developer, 4EXT Recovery Control it has a lot of additional features and benefits.)
Perform a full wipe; system/data/boot/cache.
Format to EXT4 (If you aren't already).
Flash the zip.
Click to expand...
Click to collapse
I really am stuck trying to format to EXT4, tried google'ing it but seriously I have not got a clue... Sorry if I seem stupid but really I just don't get it.
I really appreciate your help.
Thank you.
PJ
Have you got any recovery installed?
zeekiz said:
Have you got any recovery installed?
Click to expand...
Click to collapse
Yes I have.
4EXT recovery? Or clockwork?
I have clockwork.
Still got any ROM running on your phone?
Well I have just recovered to my old rom that came with the phone but I did put [Endymion V2.1|Sense 3.5|GB 2.3.5][Endymion kernel V1.1|OC|FFC on so can put it back if needs be?
Nah nah all good, just download that recovery control application that I posted in my previous post, you can use that application to easily "upgrade" clockwork mod to the 4EXT Recovery menu, which will add a lot more functionality to your recovery menu.
Wait did you put your stock ROM back on? Is it rooted? If it's not rooted, I think you have to do the previous steps in a rooted ROM like Endymion to ensure that it works properly.
I'll put the custom rom back on then but obviously I'd prefer to do it for free... lol. But I'll buy the control app if I need to?
The one I linked you to is free, there's just an optional paid applicatiob
Yeah thats my problem, how do I use the apk file? This is whats confusing me?
Use something like ES File Explorer to navigate to where the apk is located on your SDCard, then install it that way. Be sure to enable Unknown Sources in Settings > Applications.
gg .. my blanket just raped my phone by tearing off the screen protector -_-"
Actually .. do you know how to use adb at all?
No... Don't even know what that is tbh.
Damn .. just keep following what I'm saying ..
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
This looks great - especially excited about your custom governor! Thanks!!
Sent from my SCH-I535 using xda app-developers app
Glad we have another kernel dev. But do you plan on releasing a tw kernel? I run tw 98% of the time and would love to try it out. Thanks for your work regardless
PsiPhiDan said:
This looks great - especially excited about your custom governor! Thanks!!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
freelunch is absurdly simple, but does its job well. Let me know what you think. Happy flashing!
aypeeootrek said:
Glad we have another kernel dev. But do you plan on releasing a tw kernel? I run tw 98% of the time and would love to try it out. Thanks for your work regardless
Click to expand...
Click to collapse
I don't run TW, so I don't have any plans to release a TW kernel. If there's enough interest, I suppose I could get to work on one though.
Interesting. Looks cool man, will check it out
Sent from my SCH-I535 using Tapatalk 2
I'm excited to give this a shot!
Sent from my SCH-I535 using xda app-developers app
flashaholic commencing flash!
Anyone using trickster mod with this kernel?
Sent from my SCH-I535 using Tapatalk 2
Love this kernel! Freelunch is amazing
Sent from my SCH-I535 using xda premium
This kernel run pretty good!!
Sent from my SCH-I535 using xda app-developers app
masri1987 said:
Anyone using trickster mod with this kernel?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's the recommended tuner app, and plenty of people are using it (mostly on Sprint and AT&T). It shows some options that are completely bogus (like GPU governor), but I've added a few extras that only Trickster supports.
Thanks for the encouraging feedback, everyone! It's much appreciated. :good:
Kudos on this kernel. It has been perfect for me so far.
Running good on my d2usc! What scheduler do you recommend?
Sent from my SCH-R530U using Tapatalk 2
New 3.4 experimental builds are going up!
governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.
gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.
Edit: I forgot about you, trvbone. I don't have a preferred scheduler. I usually just use sio. I've never had a positive experience with ROW, but that might just be bad luck on my part.
More edit: I'm building a 3.0 kernel with trinity colors support and GCC 4.8.0 now. It should be up shortly.
decimalman said:
New 3.4 experimental builds are going up!
governors is building now, and has sio and zen. It'll eventually have a few new governors, but I haven't gotten everything ported yet.
gcc480 is up now, and is a test to make sure GCC 4.8.0 isn't causing any crazy bugs. It's also got sio and zen.
Edit: I forgot about you, trvbone. I don't have a preferred scheduler. I usually just use sio. I've never had a positive experience with ROW, but that might just be bad luck on my part.
Click to expand...
Click to collapse
I'm no noob when it comes to kernel lingo, but I'm not sure what the dif is here between the kernels listed as governors and gcc480. Are these two different kernels? I'm not aware of what gcc480 is I guess. Sorry until recently I was a dedicated lean kernel user and don't know all of the terminology since lk was pretty plain Jane.
I'm not a huge fan of row, but that's what I'm using right now cause it's quick just a little sketchy sometimes.
Sent from my SCH-R530U using Tapatalk 2
trvbone said:
I'm no noob when it comes to kernel lingo, but I'm not sure what the dif is here between the kernels listed as governors and gcc480. Are these two different kernels? I'm not aware of what gcc480 is I guess. Sorry until recently I was a dedicated lean kernel user and don't know all of the terminology since lk was pretty plain Jane.
I'm not a huge fan of row, but that's what I'm using right now cause it's quick just a little sketchy sometimes.
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
decimalman said:
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
Click to expand...
Click to collapse
Thanks for the expl I'll flash tomorrow morning and give it a whirl! Great job BTW. This is now my daily driver!
Sent from my SCH-R530U using Tapatalk 2
decimalman said:
I have a tendency to describe things in the least understandable way possible. Sorry about that.
Hopefully, there's no noticeable differences between the two builds. I think the gcc480 build might benchmark a bit better, but I haven't really compared. The only actual difference is which compiler I used to build the kernel, which probably doesn't matter for 99% of users.
The governors build is built with the same ol' Linaro nightly toolchains that I've been using, so I expect it to be pretty stable.
The gcc480 build uses a newer, fancier compiler: GCC 4.8.0. I've found at least one new bug with the new compiler (it's fixed in the uploaded builds, don't worry ). I'm not ready to call the gcc480 build stable since it's gotten so little testing, but it's been running great for me all day. I'd love to hear feedback from anyone who flashes it.
Eventually, most other kernels will switch to GCC 4.8.0 (probably once Linaro releases a full-featured build). I think gideonx (of BMS fame) is planning to switch sometime soon, and I would expect ktoonsez to switch pretty soon too.
Click to expand...
Click to collapse
Giving it a go now. Do you have any test methods you use to test the stability of a kernel other than the everyday use approach? Thanks for the support, looks sweet:good::good::good: