EVO 3D @ 1.8GHz!
HTC is taking far too long with their promised bootloader unlock! I got my hands on an EVO 3D and wrote a kernel module to overclock it (along with the Sensation, I think) with just temp root. I had no kernel sources or the ability to flash custom kernels, and you don't need to overclock your phone, either. This was all done with a Linux loadable kernel module.
EDIT: This is reported not to be working on the Sensation (or at least some Sensations) just yet. I'm investigating the issue, but don't have a Sensation on hand. It might have to do with the Sensation using an older kernel. I'll try to borrow one from a friend. If any devs are good at this sort of thing and want to take a crack the source of this module is at the bottom of the thread.
At 1782MHz (nearly 1.8GHz), a dual core Android phone is truly a force to be reckoned with. This module also gives you the flexibility to try to go even higher, or specify a lower overclock. See below for instructions and download. SetCPU has also been updated to support the EVO 3D and Sensation better. I'll be doing a technical writeup on how this was accomplished soon, as well as an explanation of the MSM 8x60 clock architecture for future kernel devs.
Disclaimer: Overclocking your phone is always a risk! Please know what you are doing before trying this. The kernel module is licensed under the GNU GPL and comes with no warranty. The relative safety of overclocking similar ARM processors to such speeds and voltages is generally known, but I can't be held responsible if you damage your phone with this hack.
Instructions:
Download the kernel module appropriate for your phone If you're not sure which one to download, check /proc/version and find the version string and then check the part that contains the localversion, which is right after 2.6.35.10 and looks like this: "gb7a86da" or "gcb1cf83"
Download: Latest EVO 3D OTA gcb1cf83: http://setcpu.com/files/8x60_oc.ko
T-Mobile HTC Sensation 4G gb7a86da: http://setcpu.com/files/8x60_oc_gb7a86da.ko
EVO 3D pre-OTA g93c03bf: http://setcpu.com/files/8x60_oc_g93c03bf.ko
Anyone good with a hex editor and your device hasn't been added: Just download the first link above and replace the "gcb1cf83" with whatever your version is - it's hacky, but it works. We can't build a "real" ko anyway, since we don't have kernel source.
(To add support for your EVO 3D/Sensation kernel, send me the kernel version string (cat /proc/version) and I'll upload a kernel with support).
1. Temp root the phone using fre3vo, and install everything you need to run root apps. If you lost temp root due to /system/bin/su becoming unlinked (root apps don't detect root anymore), do it again. Thanks #teamwin!
2. Decide which frequency and voltage you want. Frequencies have to be a multiple of 54MHz. For example, 1512MHz = 54MHz*24. Remember how much you have to multiply 54 by to get the frequency you want. For 1782MHz, as I reached, use 33 (54MHz*33 = 1782MHz).
3. Push the kernel module to your device: adb push 8x60_oc.ko /data/local/tmp/8x60_oc.ko
4. Use SetCPU (you must be 2.2.4 or above for proper MSM 8x60 support!) to set the max frequency to 432MHz and min to 384MHz.
6. Go back to the home screen, press the power button, and count to ten.
7. Load the kernel module with the following command, replacing the scpll_l_val with the value you got above and the vdd_uv with the voltage you want (in microvolts). Here is a valid command for around 1.8GHz: adb shell insmod /data/local/tmp/8x60_oc.ko scpll_l_val=33 vdd_uv=1375000
If you do not specify any parameters, the module defaults to 1512MHz and 1250000 uV! (scpll_l_val=28 vdd_uv=1250000) This should be safe for everybody, since that's the MSM 8x60's native speed (of the higher speed bin anyway ).
8. If it crashes right after you insmod the kernel, reboot and try again - the second core was likely still active. This doesn't necessarily mean your overclock settings were unstable.
9. Now go into SetCPU and it will autodetect the new max frequency. Set it and try it out. If your phone crashes at or after this point, the scpll_l_val and vdd_uv combination was not stable enough. Reboot and try another combination.
Note: the maximum scpll_l_val supported currently is 37 (1998MHz, or 2GHz!). Let me know if you actually managed to reach this with a semblance of stability, if you want to push for higher... Also, you can undo this mod just by rebooting.
Video:
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy! Of course, this would all have been easier if we were just given an unlocked bootloader. Please bother HTC about it! Yeah, we'll get it without them, but they have to keep their end of the deal.
Follow me on twitter: http://twitter.com/coolbho3k
Sources for the overclock module: http://dl.dropbox.com/u/36553/8x60_oc.tar.gz I'll be uploading it to my github soon. It's messy at the moment.
Nice
10Chars
Nice work.
Very Nice work. This is really all I ever root my phone for. I am assuming I can use this to underclock as well?
Anyways, thanks for the great work!
Sensation, T-Mobile USA
Linux version 2.6.35.10-gb7a86da ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri May 20 21:28:40 CST 2011
pastorbob said:
Very Nice work. This is really all I ever root my phone for. I am assuming I can use this to underclock as well?
Anyways, thanks for the great work!
Click to expand...
Click to collapse
The phone generally doesn't drop below 384MHz, and the minimum frequency is 192MHz, so you don't need the LKM to underclock, just SetCPU.
But the fact that su becomes unlinked after a while might prevent you from re-setting frequencies on-the-fly very much.
Inb4 someone asks for a Quadrant run <.<
coolbho3000 said:
The phone generally doesn't drop below 384MHz, and the minimum frequency is 192MHz, so you don't need the LKM to underclock, just SetCPU.
But the fact that su becomes unlinked after a while might prevent you from re-setting frequencies on-the-fly very much.
Click to expand...
Click to collapse
AH.... Gotcha. Well, I will be messing around with it. Thanks for the quick response. With my OG droid and g2 I would underclock and leave it basically at minimal speeds unless I was doing some gaming.
A simple reboot will send me back to stock speeds correct? If so, I think I could easily get two full days out of this phone if the low speeds will stick.
pastorbob said:
AH.... Gotcha. Well, I will be messing around with it. Thanks for the quick response. With my OG droid and g2 I would underclock and leave it basically at minimal speeds unless I was doing some gaming.
A simple reboot will send me back to stock speeds correct? If so, I think I could easily get two full days out of this phone if the low speeds will stick.
Click to expand...
Click to collapse
Yes, LKMs are not permanent. A reboot changes everything back.
I took default values at 1512MHz and seems to be running smooth, will let it sit at this rate and mess around later on.
You are the man!! left the values default and wow! what a difference in numbers. Linpack scores are 86 on dual thread, 54 on single thread, and my quadrant scores went from ~1900's to 2300-2400. Very impressive!
coolbho3000 said:
The phone generally doesn't drop below 384MHz, and the minimum frequency is 192MHz, so you don't need the LKM to underclock, just SetCPU.
But the fact that su becomes unlinked after a while might prevent you from re-setting frequencies on-the-fly very much.
Click to expand...
Click to collapse
does this have to be done with each reboot or will it "stick"?
edit: saw your post.
Try using "CF Bench". It's a dual core benchmark test. It usually comes in 2nd with gs2 coming in 1st.
Sent from my PG86100 using Tapatalk
.nice job man been waiting for this
Sent from my PG86100 using XDA App
DomSim said:
does this have to be done with each reboot or will it "stick"?
Click to expand...
Click to collapse
LKMs are totally in RAM, and are totally cleared upon reboot. Just like we can't have permanent root or an unlocked bootloader, we can't have permanent overclock.
empiricalis said:
Sensation, T-Mobile USA
Linux version 2.6.35.10-gb7a86da ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri May 20 21:28:40 CST 2011
Click to expand...
Click to collapse
My T-Mobile Sensation has this exact same kernel as well
Code:
# cat /proc/version
cat /proc/version
Linux version 2.6.35.10-gb7a86da ([email protected]) (gcc version 4.4.0 (GCC) )
#1 SMP PREEMPT Fri May 20 21:28:40 CST 2011
EDIT: I see that you have uploaded the module for Sensation, but there is a typo in the OP, you are missing an 'a'
This is the correct URL:
http://setcpu.com/files/8x60_oc_gb7a86da.ko
update! just scored 2730 on quad/ What is a good screen capture app?
Says file not found for the sensation kernel
Sent from my HTC Sensation 4G using XDA App
welrope said:
update! just scored 2730 on quad/ What is a good screen capture app?
Click to expand...
Click to collapse
Why do people insist on using an app.
ddms can do that. Unless you aren't at a computer. But to do this you have to be.
Sent from my PG86100 using XDA App
So does the performance governor lock both cores into that speed?
I got 2995 on quadrant, then my phone rebooted...
Related
After being a long time lurker here in XDA and having successfully fulfilled some requests on another thread, I thought I'd try to give something to the great community here.
You probably remember Ivan's kernels that provided the community with a version of intersectRaven's Hybrid AVS with 1113MHz overclocking. Unfortunately it looks like Ivan been very busy and is unable to update his kernels. So I have provided recent updates of intersectRaven's truly awesome kernels that includes the 1113MHz overclock for you all to enjoy. (I see this request a lot so maybe now intersectRaven won't be bothered by it again )
I absolutely take no creative credit in making these kernels as all I have done is used the open source code on intersectRaven's github and compiled it. The real credit goes to all the other coders here in this forum (cyan, pershoot, and especially intersectRaven).
When time permits, I'll try to update these kernels when improvements and/or bug fixes are made but I realistically only see myself updating these once or twice a week.
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions. Edit: Due to having virtually no free time, I don't think I can get fulfill requests in a timely manner... I'll try but I can't promise it. So sorry everyone -_-;
If you have the time and the will, I highly suggest you learn how to compile for yourself as I find it pretty fun and rewarding to make something for yourself. Guides and instructions can be found throughout the XDA forum and also on Cyanogen's wiki.
Before updating with these kernels, all I ask is that you make a nandroid backup in case something goes wrong.
Q & A:
-What's the difference between CFS and BFS?
See this short post for the difference between Completely Fair Scheduler and Brain F*** Scheduler. In summery, CFS is better for multitasking, BFS is better for user interactions (keyboard, homescreen swiping, etc).
-What's the difference between SVS and AVS?
Static Voltage Scaling will change the voltage based on a set table created by the kernel maker. Example: At a certain speed, say 245MHz, 925mV is feed into the CPU. At 998MHz, 1225mV is used.
Adaptive Voltage Scaling will change the voltage depending on temperature and CPU needs. Personally, AVS is running rock solid for me but I can't say for sure if it will be for everyone so SVS kernels will continue to be made available.
-What is this "No Audio Boost Version"?
Many of the custom kernels posted in this forum and the kernels used by default in the CM6 roms have this feature where it increases the loudness of the speakers during calls. Its been reported that some bluetooth headsets are overly sensitive to the increased loudness and some have reported that it distorts the audio quality even though volume has been lowered by the user. Due to an overwhelming request to make a kernel without this feature, I have included a separate set with each release that does not boost the volume.
-Can you make a higher overclock version of your kernel?
I was really against this because when I first tried to do this, my phone got really hot. But the requests kept on coming so I revisted this and possibly discovered a way to keep the temperature under control by limiting the max voltage to 1300mV. You'll find a 1190MHz version of my kernel here (Mirror Link).. Most users should be able to handle 1152MHz without any problems but some won't on 1190MHz. You'll know when your CPU can't handle a certain speed if you start to experience a sudden decrease in performance, lag, force closes, and spontaneous reboots. This won't be alievated unless more voltage is feed to the CPU but I'm not comfortable going beyond 1300mV. Now before you try these kernels out I gotta say this. I am not responsible if these kernels result in damaging your phone. Its purely for testing purposes and I really dont recommend using it as your everyday use kernel. If you do continue to use it, you should limit the max to 1113MHz or better yet 1075MHz (see previous question for the reason) if you care about battery life.
-I'm getting a black screen whenever I launch the camera app. Why? (720p related question)
The latest kernels with the 720p code only works with roms that has the 720p stock camera app and now the HTC camera app on Enomther's [ROM] as of 8/10/10. The latest cm6 nightly that has the 720p camera app as well as a few other roms out there that are based on cm6. You can try flashing charnsingh_online zip that contains the updated camera app if you don't want to use the nightly but I don't know for sure if his camera app is compatible with roms under RC2. Another alternative is to send in a request for a custom kernel and I'll make one for you without the 720p code.
2.6.38 kernels:
(Tested on Cyanogenmod 7 Nightlies)
Grab the kernels here: Mediafire
-Changes since 090311
-Set default sleep ideal freq to 128mhz for smartassV2 governor
-Bug fix for 1190MHz kernels, properly set max voltage to 1325mV
-Compiled HAVS 1190MHz kernels for those phone that can handle it
-Changes since 062411
Rebase source from IntersectRaven's Github
Highlights include:
-msm: Add support for voice call recording
-PM: Back off suspend if repeated attempts fail
-lib/sha1: use the git implementation of SHA-1
-arm: remove “optimized” SHA1 routines
-Fix AVS thread not being started.
-Added erasmux’s Smartass governor Version 2
-Changes since 062311
-Fixed ext4 partition support on sdcard.
-Changes since 052711
-Rebase to kernel version 2.6.38.8 from IntersectRaven's Github, with it 2 new governors (InteractiveX and SavageZen)
-Changes since 052611
-Rebased kernel source from intersectRaven's Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn't want to take a chance in WiFi not working for some.)
-Changes since 042111
-Rebased kernel source from intersectRaven’s Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn’t want to take a chance in WiFi not working for some.)
-Changes since 040911
-Bug fixes relating to USB file transfer speeds and addressed probable cause of WiFi problems for some.
____________________________________________________
If you want, you can buy me a drink (I like orange juice)
Have these kernels been tried and tested? Does the following work:
- Youtube
- Camcorder
- Googles
- Flash
- Unmounting sd card
- Wifi locations
and can you tell us more about the battery life by using this kernel?
p.s. Thanks for posting this btw...
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
Click to expand...
Click to collapse
Thats gr8...what about battery life? how do yo fare by using this kernel?
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Well....i like 800mV UV and OC, giving me the best balance between battery life and speed.
couldnt do an excact test on the time, but it lasts enough for my usage ^^
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
Click to expand...
Click to collapse
Glad you like it! You know it was partly you that made me want to start this thread.
great! i am really looking forward to it!
wildmonks said:
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
Glad you like it! You know it was partly you that made me want to start this thread.
Click to expand...
Click to collapse
"partly"
^^
xD
everything including goggles seems working on 800 bfs.. 41 linpacks.. cool
That was my result with linpack and this kernel!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
wildmonks said:
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions.
Click to expand...
Click to collapse
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
mardox said:
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
Click to expand...
Click to collapse
CFS: http://de.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
nazrin313 said:
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
Click to expand...
Click to collapse
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
hondaguy said:
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
Click to expand...
Click to collapse
Im gonna charge it to 100% then leave it whilst I sleep...Tommorow im gonna im actually gonna use it
from my own usage since installing Froyo here is what I have found from testing various kernels (Unplugged at 7am)
- Froyo Kernel: Lasted till 10pm ish (Display on > 3 hrs)
- Preshoot 33.4 kernel: lasted me till 3pm ish (Display on approx 2 hrs)
P.s:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
daveid said:
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
Click to expand...
Click to collapse
Here yah go:
2.6.33.5_AVS-925mV_CFS_NoAudBoost_v2_060210.zip
I think all those years of listening to loud music has affected my hearing so I need the audio boost
I tested it out and it seems audio levels are back to standard (noticeably lower) but let me know if it doesn't work or if there are any other problems with it.
Update: Doh! I found a bug that I introduced into this no audio boost version. Seems that I broke music playback O_O. I fixed it and updated the above link. Sorry to those that download the other version -_- . . .
Audioboost is so necessary, i cant use any kernels without!
RinTinTigger said:
That was my result with linpack and this kernel!
Click to expand...
Click to collapse
t0ol said:
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
Click to expand...
Click to collapse
nazrin313 said:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
Click to expand...
Click to collapse
Interesting observation you all are getting. Must be the combination of BFS and OC? But I would not be surprised if battery life suffers a little... But very cool nonetheless
I have successfully overclocked the new Samsung Galaxy S II to 1.504GHz. This speed is enough to allow it to achieve really high benchmark scores like over 4000 points in Quadrant! 1.5GHz is a 25% overclock and makes this fast phone even faster and snappier in day to day usage.
Instructions:
1. You'll need the latest version of odin3 and the USB drivers for Windows. jutley's post on debranding the phone has links to both: http://forum.xda-developers.com/showthread.php?t=1064894
2. Grab the kernel. It is a tar file for odin with the overclocked kernel and a initramfs with proper modules for the kernel: http://setcpu.com/files/galaxysii_oc_v1.tar
3. Reboot the phone into download mode using ADB:
adb reboot download
4. Flash the kernel using odin3 by placing the tar file in the PDA section and pressing "Start."
5. The phone will reboot automatically.
6. Use SuperOneClick to root your phone if you haven't already. ADB should have root access with this kernel so it'll just work.
7. Grab SetCPU and try 1.504GHz.
Source code (with relevant commit for the overclock. I also enabled the interactive governor in the config): https://github.com/coolbho3k/galaxysii_oc
I haven't gone crazy on the voltages - 1.504GHz is stable at 1375mV on my device. Depending on your device, there may be even more headroom. I've gotten speeds of up to 2GHz to boot with instability (my unstable 1.8GHz Linpack run is currently in the Linpack top 10), but at very high voltages and temperatures. Leave it up to other developers to give you higher/more dangerous frequencies and voltages. If you stress the CPU a ton the phone will become hot to touch (though it does to a certain extent even at stock frequencies - there is not much thermal insulation between the processor and your hands in such a thin phone).
Current features in this kernel: Added 1.504GHz overclocking step (default frequency is still 1.2GHz for safety - use SetCPU to safely raise the frequency) and relevant modifications, 800MHz sleep death fix, interactive governor, ro.secure = 0.
The usual disclaimers apply here. Only do this if you know what you're doing. Though the long term stability/reliability of similar overclocks on other Android based ARM devices is known, this software is provided with no warranty, and I can't be held responsible if you fry your device.
Video:
A 1.504MHz overclock:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...breaks over 4000 points in Quadrant:
...and almost 60 MFLOPS in Linpack:
Since Linpack and Quadrant aren't (sufficiently?) multithreaded, you won't see that much improvement over single core Cortex A8 devices at the same clock. But these are dual core phones!
Developers: keep in mind that the Galaxy S II source currently "fixes" voltages on this revision of the Exynos to be 25mV less than what is in the table. Upon boot, the driver will actually print the real voltages at each level (look for ASV voltage_table in the kernel log) if you don't know which chipset revision a particular phone has. The overclock itself is controlled in the s5pv310_apll_pms_table.
Enjoy!
Damn .........
This is when I really wish I had a SGS2. Can't wait till it comes to American shores, great work coolbho, see you on Engadget tomorrow..
OMG already? I was wondering when this would happen. God bless you man.
Wonderful work man. Can't get Odin to download on my home rig so I'll be playing around w/ this tomorrow at the office With overclocking already here and the inevitable kernel optimizations to come, this phone is truly going to be the beast everyone suspects.
Thanks man!
..and what about undervolting?
WOW, nice work
Thanks!
Holy crap, nice work! How much hotter is it getting in the back of the phone at 1.5ghz?
Sent from my GT-I9100 using Tapatalk
Very good job here mate. It's about time somebody attempted to overclock such a sweet phone.
I will flash this with Odin tonight.
Again, great job & thanks
Not bad eh?
rovex said:
Not bad eh?
Click to expand...
Click to collapse
how you getting that score im getting just above 4000
Haha well played
coolbho3000 said:
Current features in this kernel: Added 1.504GHz overclocking step (default frequency is still 1.2GHz for safety - use SetCPU to safely raise the frequency) and relevant modifications, 800MHz sleep death fix, interactive governor, ro.secure = 0.
Click to expand...
Click to collapse
What is the 800MHz sleep death fix?
Can someone run this overclock against AnTutu Benchmark as well please ....i find this a little more stable than quadrant.
Ty
S
Sent from my GT-I9100 using XDA App
Very impressive indeed. The only question that comes to mind is if there really is a need to squeeze out higher frequencies. The CPU isn't really a bottleneck on the SGS2, is it?
MrDeacon said:
Very impressive indeed. The only question that comes to mind is if there really is a need to squeeze out higher frequencies. The CPU isn't really a bottleneck on the SGS2, is it?
Click to expand...
Click to collapse
CPU is always a bottleneck for calculations. Probably not a bottleneck in most apps though.
My install went smoothly. Quadrant showed 4144, 3892, and then 4100. Im going to try running it throughout today and see what happens. Cant wait for this to mature.
WOW.! Flashing right this second.! You people are geniouses.!
Sent from my GT-I9100 using Tapatalk
just wanted to add
oh crap.. i just realized who posted this, its Mr. Overclock himself, the creator of SetCPU... woo we have a star in our mits!
Hey guys,
Ok the people who know about SetCpu and undevolting with it...
If I key in UV-values that go further than the slide-bar can take, i.e over -500mV,
does the undervolting actually go under the -500mV??
At the moment I've tried:
216mhz at -725mV [No hang when I run max and min cpu frequency at both 216Mhz]
456mhz at -650mV [No hang when I run max and min cpu frequency at both 456Mhz]
EDIT: I also ran the stress tests at said frequency settings and still no cpu hang or reboot.
I want to see if this goes further, but Im not sure if SetCpu is actually making the UV values go over -500mV.....
Cheers guys
current config: latest Blue Chronic rom, faux 2.1 kernel, carrier unlocked at&t atrix.
weaz_da_smel said:
Hey guys,
Ok the people who know about SetCpu and undevolting with it...
If I key in UV-values that go further than the slide-bar can take, i.e over -500mV,
does the undervolting actually go under the -500mV??
At the moment I've tried:
216mhz at -725mV [No hang when I run max and min cpu frequency at both 216Mhz]
456mhz at -650mV [No hang when I run max and min cpu frequency at both 456Mhz]
EDIT: I also ran the stress tests at said frequency settings and still no cpu hang or reboot.
I want to see if this goes further, but Im not sure if SetCpu is actually making the UV values go over -500mV.....
Cheers guys
current config: latest Blue Chronic rom, faux 2.1 kernel, carrier unlocked at&t atrix.
Click to expand...
Click to collapse
any jump more than 100mV between steps and it wont do the changes
The 100mV steps are the limiting factor if you use the higher frequencies which require relatively high voltage not to cause problems. What the OP might be curious about, and what I'm curious about is if I limit my phone to say 600MHz then I can set the voltage of all higher frequencies as low as I want because the phone will never use those frequencies, then I can try to find the true lower bound of the lower frequencies. The problem is I can set the lowest frequency to 0, keeping the 100mv steps, and the phone still runs fine (by limiting my phone to 216MHz), so there is some other rule in effect besides the 100mv between steps rule.
This is something that is limited by the chip itself but I guess that these rules would have to be written in the kernel, so I'm going to post over in the faux kernel thread.
Edit:
I don't have enough posts to post in the developer forum. Can someone copy the jist of my question over in the faux thread or somewhere else appropriate and with marginally high traffic? Thanks.
I have been thinking about undervolting as well and I was wondering if really does make that big of a difference like some people say? Do you really notice that it improves your batter life?
Atrix_Owner said:
I have been thinking about undervolting as well and I was wondering if really does make that big of a difference like some people say? Do you really notice that it improves your batter life?
Click to expand...
Click to collapse
The benefits of undervolting are lower power which leads to lower heat and longer battery life. I'm not sure if these power savings translate if the cpu is idle or in some type of sleep mode and the other problem is that all the other components are still using the same amount of power so the real savings might not be much if your phone is mostly idle.
But, my phone idles at 216Mhz and I have almost halved that voltage at that level so the best case scenario is that the cpu is using 1/4 the power it would normally.
I haven't done any testing but I do know there is some savings and we're all here cause we like to tweak things so you might as well undervolt cause it's pretty simple.
I would start with these levels:
1000 - 950mV
912 - 900
750 - 800
608 - 700
456 - 600
312 - 500
216 - 400
The only rule I know for undervolting is the 100mV between steps rule but I know there is some other rule at play as described in my previous post, but I don't know what it is. So really, I'm not sure if the voltages at the lower frequencies are actually being applied.
Hey thanks for the info. I don't know if I'm doing this correctly. After I undervolted, I clicked "set on boot" and rebooted my phone but I'm not sure if I did it right. For example, when you look at the "1000mhz", on the right it says "Max 1000mV" which is the default setting but shouldn't it be "925mV" because I subtracted -75mv? Look at this pic and tell me if it's like it should be.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ya, that's right. That max voltage I think is a misnomer I think it should say default voltage really and that's just there for reference. So, when your cpu is operating at 1000Mhz it is operating at 925mV, with your current setting, it doesn't vary.
If you want to try to push for lower voltages you just want to uncheck set on boot so you avoid getting into a reboot cycle. YMMV on what kind of undervolt will be stable. I gave you my numbers because I think my phone is not as stable as others since it can't handle the 1.45Ghz overclocking kernel.
My phone isn't overclocked btw and I'm using Faux123's enhanced stock kernel 1.0ghz. I will try to push the volts even lower and see how that goes. One thing that I can say for sure is that when I play GTAIII, my phone doesn't overheat as much as it used to so this defiantly fixed the overheating issue that I was having with almost any game.
my setcpu doesnt have voltages tab.. y?
borjok536 said:
my setcpu doesnt have voltages tab.. y?
Click to expand...
Click to collapse
B/c you're not using a custom kernel.
Sent from my CM7 Atrix 4G
mebster123 said:
The 100mV steps are the limiting factor if you use the higher frequencies which require relatively high voltage not to cause problems. What the OP might be curious about, and what I'm curious about is if I limit my phone to say 600MHz then I can set the voltage of all higher frequencies as low as I want because the phone will never use those frequencies, then I can try to find the true lower bound of the lower frequencies. The problem is I can set the lowest frequency to 0, keeping the 100mv steps, and the phone still runs fine (by limiting my phone to 216MHz), so there is some other rule in effect besides the 100mv between steps rule.
This is something that is limited by the chip itself but I guess that these rules would have to be written in the kernel, so I'm going to post over in the faux kernel thread.
Edit:
I don't have enough posts to post in the developer forum. Can someone copy the jist of my question over in the faux thread or somewhere else appropriate and with marginally high traffic? Thanks.
Click to expand...
Click to collapse
What I gathered from my own experience, experimenting and looking at code is the following:
The 100 mv limit between steps seems to be more of a nvidia guideline for best chip performance. It is not an actual limit in the software, no matter the values you input, they will be applied.
What is indeed limited (and so in the code) is the lowest possible undervolt. In faux's it is 750 mv and clemsyn's (was, not sure if still is) 650 mv.
If you push any voltage past that limit, it won't be applied. Try it for yourself.
Share your benchmark scores with xda - Antutu / GFXBench / Vellamo Metal / Basemark OS II
Stock Rom or not will be greatly appreciated. See attached vs. other current Verizon Android Phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This was stock ROM, reflashed via TOT about a month after I had the phone. Rooted, all LG/Verizon disableable stuff disabled in App Manager (before rooting).
Ok so I just got done setting up Vanir AOSP 4.4.4 ROM with all my apps. I haven't customized anything other than various appearance settings - I didn't mess with SetCPU, schedulers, DPI, etc. This was just me installing all my apps and setting up the notifications etc. the way I like them. This is my first run at an AOSP ROM on the G3. Here are the results.
(NOTE: I downloaded and ran all the same benchmarks as in the list above, with a reboot between each benchmark run. I have annotated the order in which I ran the benchmarks after their respective titles.)
Antutu (first):
Vellamo Metal (fourth):
Basemark OS II (second):
GFX Bench (third):
(NOTE: The phone was scorching hot at the end of this run; throttling might explain the lower scores?)
My phone with bloat turned off and running with the interactive governor and a hack to make throttling less aggressive.
Sent from my VS985 4G using Tapatalk
tech_head said:
My phone with bloat turned off and running with the interactive governor and a hack to make throttling less aggressive.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Dawn what is this hack you speak of?
Modifying thermal-engine-8974.conf to prevent throttling in an aggressive manner. There is a thread somewhere about it. I hacked it up self based on what I want my phone to do. As you can see from my previous post Antutu performance is right up there with the other flagships. The big reason why it still lags behind the S5 is 3d performance. Anyway I'm happy now that it doesn't throttle and I still get a days use.
Sent from my VS985 4G using Tapatalk
tech_head said:
Modifying thermal-engine-8974.conf to prevent throttling in an aggressive manner. There is a thread somewhere about it. I hacked it up self based on what I want my phone to do. As you can see from my previous post Antutu performance is right up there with the other flagships. The big reason why it still lags behind the S5 is 3d performance. Anyway I'm happy now that it doesn't throttle and I still get a days use.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
How'd you change governors if you are on the stock kernel?
Nothing in the stock kernel prevents it. I use ROM Toolbox (pro version) and you can tweak a bunch of performance parameters. LG doesn't lock the kernel down except for maximum clock speed. So you can't over clock but you can run a max 100% of the time. You will eventually hit thermal throttle, but you can do it.
Sent from my VS985 4G using Tapatalk
Here's my score with beans Rom and running skydragons kernel and no other tweaks to the kernel
sent from my stumped and bumped g3
Mine
pitbull8265 said:
View attachment 3054061
View attachment 3054062
Click to expand...
Click to collapse
Thank you, what is your current Rom / setup for these scores.
sent from my xda enhanced Android Device
[/ATTACH]
legend221 said:
Thank you, what is your current Rom / setup for these scores.
sent from my xda enhanced Android Device
Click to expand...
Click to collapse
View attachment 3054085
I did a lot of work tweaking the kernel, i/o scheduler and throttling response
Here is one using the latest Vanir Commotio Lollipop
pitbull8265 said:
[/ATTACH]
View attachment 3054085
I did a lot of work tweaking the kernel, i/o scheduler and throttling response
Click to expand...
Click to collapse
Do you mind posting details about how you have things setup?
jal3223 said:
Do you mind posting details about how you have things setup?
Click to expand...
Click to collapse
WOuld, but I am on a different setup now...
I set the governor to Interactive, read ahead buffer to 4096, cfq scheduler, Vegas Tcp Conjestion Control, max frequency 2457 minimum 300
I fine tuned the governor as well, but cant remember the settings, sorry
I am on Jasmine 4.0 running the latest Skydragon kernel. The trickster mod setup is the second pic- TCP setting is clipped off the top, its Westwood.
Broke 42k today with CM12 12/12.
In case anyone is wondering, using trickster mod the best governor is performance, not interactive, when it come to benchmarks specifically. Interactive is better for general use but performance will just always give you the optimal performance (get it) in a benchmark.
i did a benchmark with stock lil debloat and skydragon kernel , im no tech so i dont know much about these readings . im planing of switching to liquidsmooth rom
cap1tal1sm said:
Broke 42k today with CM12 12/12.
In case anyone is wondering, using trickster mod the best governor is performance, not interactive, when it come to benchmarks specifically. Interactive is better for general use but performance will just always give you the optimal performance (get it) in a benchmark.
Click to expand...
Click to collapse
Cool.. Screenshots for reference???
pitbull8265 said:
Cool.. Screenshots for reference???
Click to expand...
Click to collapse
You're just gonna have to trust me that I hit 42k xD didn't screenshot it.
I actually hit 40k with stock ROM by turning on performance governor, so it definitely helps with benchmarking.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all, its been a while LA went public, and thanks to you all, it received good responses. So I thought, it's time to revamp the intro.
First of all, like all other great(Linux) things, this kernel also falls under FSF's GPL(General Public License), which is probably the most comprehensive open source license till date. I just wanna quote two agreements from the license :
Code:
[SIZE="2"]15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.[/SIZE]
A few months ago, we've had a burst of mods and kernels, and some great kernels took birth on the occasion. They all offered great flexibility of customisations, and a whole lot of other features. They were great no doubt, however with great choices comes great confusion. So I thought to come up with a kernel which will include the bare minimum customisations and fit(as close as possible) to all type of users, giving a good balance between stability and performance. Which won't hesitate to go to the extreme limit when the situation demands, but will stay right in the middle in most others. And so, I decided to bring my own kernel, the LateAutumn.
It's probably pretty late, but it's probably the most beautiful till date.
I won't say anything more.
Try it, and say yourself.
Features :
CPU overclocked to 1.8GHz
GPU overclocked to 720MHz
Stock Lineage source (**requires confirmation from @nicknitewolf**)
SELinux permanently Permissive
Adreno Idler ( enabled by default )
Faux Sound Control 3
MSM Hotplug ( disabled by default )
Various wake gestures
- DoubleTap2Wake ( disabled by default )
- Sweep2Wake ( enabled by default )
- Sweep2Sleep ( enabled by default )
kexec-hardboot patched
Compatible with all N ROMs
Checkout the downloads tab for Version 5.1.1 Kettle!
XDA:DevDB Information
LateAutumn, Kernel for the Xiaomi Redmi 2
Contributors
iamsubhranil, ketut.kumajaya, ashish94, codeharuka, premaca
Source Code: https://github.com/iamsubhranil/android_kernel_wingtech_msm8916_lineage
Kernel Special Features: All overclock, Incredible balance
Version Information
Status: Stable
Current Stable Version: 5.1.1
Stable Release Date: 2017-02-06
Current Beta Version: 2.2.6
Beta Release Date: 2016-09-28
Created 2016-09-25
Last Updated 2017-02-06
Reserved
Version 2.0 Beta - 26/09/2016
Stock CM source
OC CPU to 1.8 GHz and OC GPU to 720 GHz
Version 2.2.6 Beta - 28/09/2016
Adreno Idler added
SELinux policy set to Permissive (permanently)
Added USB fast charge and enabled by default
Added more generalized flashing method
Version 2.3.2 Stable - 29/09/2016
SELinux is now Permanently Permissive
Added Mako Hotplug and set as default
Improved stability and performance largely by tweaking various parameters
This update however, disables MPDecision permanently from the first boot as a fail-safe. As long as the kernel stays, you're "forced" not to use MPDecision, as the tweaked balance between CPU-Hotplug will be lost and overall performance may decrease. You can however, enable MPDecision after renaming mpdecision.bak in /system/bin to mpdecision and flashing another kernel before next boot. If you still feel the need to use MPDecision, please vote above. Thank you for understanding.
Version 2.4 Stable - 03/10/2016
Added MSM hotplug and set as default
Add Westwood TCP/CA and set as default
Because a lot of people reporting lag after the Mako build, I encourage everyone to flash this build and report back. Thank you.
Version 2.5 Stable - 19/10/2016
Added FauxSound 3 and enabled by default
DT2W is still a WAP. Stay tuned.
Version 3.0 Stable - 20/10/2016
Added DT2W and enabled by default!
Latest CM updates
Version 4.0 Grey - 20/10/2016
LA is now N compatible
N build is up. Perfectly compatible with all N (CM) ROMs out there. This is the first CM custom kernel to support N out of the box. That means enjoy the versatility of N with the stability of LA.
But wait, did I just say "N build"? My bad. There's no "N build" as such because it is the same kernel that supports both N and M ROMs at the same time. It is your LA. Just ready for a new home, along with the old one.
From this build on, LA will contain a codename, preceding with the n-th letter, which will specifically be a late autumn or winter item, here n denotes the release number.
So what are you waiting for? Flash it now and leave your comments about how can the kernel be made specifically for you. It's my kernel, in your way.
Version 4.1 Heat - 29/11/2016
Latest CM updates
kexec-hardboot patch enabled
For all the people wanna know about this stuff, it is basically done for the sake of MultiROM. This process goes deep into low level access of RAM and memory, but at the bottom line, what it does is loads another kernel into RAM at runtime(kexec), initiates a full reboot(hardboot), and jumps to the new kernel code directly from the RAM in the next boot. For the people who aren't using MultiROM, no worries.
Version 4.2 Iceberg - 07/12/2016
Implemented KCAL support
Sorry for the long wait. Got studies and stuff. Thank you for your patience.
Version 5.0 JackFrost - 07/01/2017
Completely rebased to LineageOS source!
A very happy new year guys ! And what is the more perfect way to start a new year than with something completely fresh, completely new? LateAutumn is now completely rebased to LineageOS source, with a more cleaner build than ever. You'll get all the same degree of performance that this kernel has made you used to, along with a higher degree freedom, higher degree of stability, and the breeze of something completely new. Which means you have now more less reasons to worry about, more reasons to live. Work, play, refreshment? That's all this new year's about.
Version 5.1.1 Kettle - 06/02/2016
Compiled with Linaro 4.9 toolchain
Latest Lineage updates
The headphone jack may still be broken. Send logs, and I'm doing something about it.
Disable any "Apply on boot" parameters in apps like Kernel Adiutor and try the default settings first. If you're still not satisfied, go apply any parameters after boot.
For downloads, please check the downloads tab.
Before use, disable everything in Settings=>Developer options=>Hardware Accelerated Rendering
Reserved
I'm overwhelmed to see your responses, queries and feature requests. But hey, XDA already has three good places to do so.
For requesting a feature, use this template
For review, use this template
For submitting errors and more preferably bug reports, use this template
Sounds great,i test and report soon for sure,Greeetz!
Can't eagerly wait for this kernel btw ?
Sent from my 2014813 using Tapatalk
It will surely drain the battery in an hour and might heat up to much... But good to see an fully overclocked Gpu nd Processor... Would like to take benchmarks.... Good work
anandmore said:
@iamsubhranil, there is no download tab here.
Click to expand...
Click to collapse
My bad! Check out now.
Riyanx55tu said:
It will surely drain the battery in an hour and might heat up to much... But good to see an fully overclocked Gpu nd Processor... Would like to take benchmarks.... Good work
Click to expand...
Click to collapse
Sadly, none of this happening at my side. But can't wait to see the actual scenarios :fingers-crossed:
will you consider to build for MIUI 8 5.1 with F2FS support?
OrGiMaSu said:
will you consider to build for MIUI 8 5.1 with F2FS support?
Click to expand...
Click to collapse
Nice proposal. Will keep it in my to-do lists. But please don't ask for any ETAs.
Will you please consider doing a 1.4ghz oc build too? Like we have seen in berzerk kernel.
Thanks
deleted
X.lord said:
Will you please consider doing a 1.4ghz oc build too? Like we have seen in berzerk kernel.
Thanks
Click to expand...
Click to collapse
I can't see the point of it. It already has 1.8. One can easily limit that to 1.4 using any kernel app he wants. So no, i won't consider that.
Thanks for your efforts
Any recommended settings for battery life?
iamsubhranil said:
I can't see the point of it. It already has 1.8. One can easily limit that to 1.4 using any kernel app he wants. So no, i won't consider that.
Click to expand...
Click to collapse
Yes i know that was a dumb request to make but @Ashish94 maintained two seperate builds 1.4ghz and 1.8ghz so i just thought maybe you can do that too. Nevermind
Btw its great to see a new kernel for our device.
Saurabh_Umadikar said:
Thanks for your efforts
Any recommended settings for battery life?
Click to expand...
Click to collapse
First test and tell if there's any affects in battery life
I'll however, as i have said in the OP, include any modification that'll unleash the best without giving a ball of fire in our hands
Feature request: can you make this kernel permissive like berserk please? many of us out there having trouble with viper4droid and other things and after every reboot turning the enforcing to permessive is a pain. I am using your kernel underclocked to 1.4 ghz and 400 mhz, while turning it up to 1.7 ghz when heavy tasking, having no trouble/ battery issues.
To other folks, if you are having battery issues, underclock your device and use 1.8 when only needed.
Would like to wait for miui lp build!
I've been using this kernel for a few hours and its working very well.. everything seems nice and smooth:good:
a liittle bit more battery drain while doing intense tasks as compared to stock cm13 kernel, but hey its OC at 1.8ghz so nothing much to complain.. Just one thing to take care of, selinux enforcing is breaking sound mods as some sound mods require selinux set to permissive by default.
Good job dev.
Two questions. Have this kernel msm hotplug? No problem with playing songs with latest builds of CM?