[Kernel] arrrghhh's kernel!

Search This thread
Holy crap!!!!! 1.89 ghz? 1.89 GIGGAHERTZ!!!!!


1-21-gigawatts-o.gif
 
Last edited:

interloper

Inactive Recognized Developer
Feb 17, 2008
644
420
El Paso
I concur 1.89 and gov at performance sticks for me. This phoq is running almost twice as fast as my evo 3d

Sent from my XT897 using xda app-developers app

Performance governor is designed to max the cpu at all times except sleep, which is why interactive, or another governor based on interactive is useful when OC'ing or UC'ing. The governor allows the processor to transition according to the settings. For those testing, have you tried switching governors then setting the min/max? Also, check us out on freenode #oudhitsquad for help and realtime testing.
 
  • Like
Reactions: tetrabyt

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
Holy crap. I just quadranted 4095. Nice sir.

If i could be the kind of d-bag that makes requests... I would love to see this become ex-tweaks enabled. I know you do this on your own time and I thank you for that. It would just be pretty sweet.

I don't know what ex-tweaks are, but I'll look into 'em. I'm kind of green to kernel development, so just getting my feet wet :)

Performance governor is designed to max the cpu at all times except sleep, which is why interactive, or another governor based on interactive is useful when OC'ing or UC'ing. The governor allows the processor to transition according to the settings. For those testing, have you tried switching governors then setting the min/max? Also, check us out on freenode #oudhitsquad for help and realtime testing.

Yea, I just wanted to see if it would stick at 1.89. If the max frequency truly was adjusting, then it would've done so under the performance gov as well...

I'm still not sure if there is an issue or not. I put it back to ondemand, and it hasn't adjusted the max freq on me at all - but my min keeps going back up to 384 for some reason. I know some said 96mhz causes issues in sleep, but I haven't had any issues so far...
 

shabbypenguin

Inactive Recognized Developer
May 30, 2010
4,895
5,361
36
system tuner to make changes to cpu for now, youll need to add in the proper hooks for setcpu etc etc. when i get situated at home from the cruise ill explain more :p
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
system tuner to make changes to cpu for now, youll need to add in the proper hooks for setcpu etc etc. when i get situated at home from the cruise ill explain more :p

Hrm. I wonder if all the OC apps I installed to verify were bashing heads.

I have NoFrills and System Tuner. NoFrills is set to reapply the config on boot, and System Tuner is really just there to "verify" - I don't use it to OC.

I am now able to go from 96mhz to 1.89ghz, reboot, and have it stick. Let me know if you guys are still having issues, I certainly might've missed something... :)
 

AvRS

Senior Member
Dec 21, 2009
4,328
2,574
Just so you know Extweaks is a kernel settings app by xan and gokhanmoral used by a lot on the S2. Think some people are just used to it so request it on all kernels ;)

Sent from my GT-I9100 using xda premium
 
  • Like
Reactions: arrrghhh

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
Just so you know Extweaks is a kernel settings app by xan and gokhanmoral used by a lot on the S2. Think some people are just used to it so request it on all kernels ;)

Sent from my GT-I9100 using xda premium

Ah, thanks. Probably not going to happen then lol.
 
I have noticed some issues with text input since i started using this kernel. There are times in both mms and in gtalk where it will not let me input text with the physical or virtual keyboard. Seems to be pretty frequent... i will try to pull a log for you next time i notice it... but i dont know if it will effect the term on my phone or not, so it may have to wait until i can do it from a computer...

I also applied the deodexer around the same time, so that might be an issue too- or, rather... they may not be compatible. Again, i will do a pastebin of a log dump as soon as it starts to do it when i am at my pc.

Sent from my XT897 using xda app-developers app
 

gtownswagga

Senior Member
Oct 27, 2010
72
18
Lickarock I'm having the exact same problem if I'm texting a lot at once. The screen starts to freeze then I wait bout 60 seconds and it unfreezes. I do not have the deoxer app. Its def the kernel I think

Sent from my XT897 using xda app-developers app
 
  • Like
Reactions: lickarock
Lickarock I'm having the exact same problem if I'm texting a lot at once. The screen starts to freeze then I wait bout 60 seconds and it unfreezes. I do not have the deoxer app. Its def the kernel I think

Sent from my XT897 using xda app-developers app

That will definitely help pinpoint whats up. Do you know how to run a logcat?
 

interloper

Inactive Recognized Developer
Feb 17, 2008
644
420
El Paso
I'm sure there's an app that will log CPU dynamics. Check to see if the idle is coming up slowly. Might be causing the stalling.

Sent from my Galaxy Nexus using xda app-developers app
 

gtownswagga

Senior Member
Oct 27, 2010
72
18
No I don't know how. Don't know much bout the dev part. I just test everything

Sent from my XT897 using xda app-developers app
 

interloper

Inactive Recognized Developer
Feb 17, 2008
644
420
El Paso
The best way we can help is for you to join us on IRC. Hit the link in my sig when you have time and look for arrrghhh on the HitSquad channel. We can walk you through the process. Cheers!

Sent from my Galaxy Nexus using xda app-developers app
 

arrrghhh

Inactive Recognized Developer
Feb 10, 2007
11,906
3,851
Hey guys, just got back from a 3-day camping trip...

Got to unwind a bit - but these posts are odd, I have been using this kernel for a while and no issues... At least not like the ones described. I'm still having intermittent success with over/underclocking settings, I think there's some different hooks needed for different apps.

More on that later. If anyone can get a logcat (or more importantly a dmesg) from the approximate time of the occurrence, that would be great. As interloper says, it would be easier to troubleshoot this over IRC ;)
 
Hey guys, just got back from a 3-day camping trip...

Got to unwind a bit - but these posts are odd, I have been using this kernel for a while and no issues... At least not like the ones described. I'm still having intermittent success with over/underclocking settings, I think there's some different hooks needed for different apps.

More on that later. If anyone can get a logcat (or more importantly a dmesg) from the approximate time of the occurrence, that would be great. As interloper says, it would be easier to troubleshoot this over IRC ;)

I shall hop on in as soon as i find the server and channel.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 84
    CM Kernels​

    Check the CM msm8960-common kernel tree for a list of commits, and if my kernel is up to date... IE last commit is from May 27th on their kernel tree, and my latest kernel says May 27th... then it's good for all nightlies until that changes! I am on the May 29th nightly, but there haven't been kernel changes since May 27th.

    I hope that makes sense!!

    Click to show archive:
    • May 1 2013 md5: 5811e7c6e0aa9bb8287ab915d87f92ac
      • (First CM10.1 kernel, "mirrors" what is in stock v0.18, while being built from nightly kernel with commits to May 1st 2013)
    • May 27 2013 md5: d19685034faad36f2f470ada4015f7fd
      • Updated to latest nightly, 3,400+ commits from upstream...
    • June 5 2013 md5: fd104559c984767e94caa3bec6199086
      • Updated to latest nightly, 3 commits missing
    • June 12 2013 md5: a7e10b0a2dd0f2df85636e2f40633d12
      • Updated to latest nightly, 92 commits missing
    • June 18 2013 md5: c78a219b6e8aae220be806f26b362a36
      • Updated to latest nightly,
    • June 19 2013 md5: 8a8942db94814e4aa796506337010ef7
      • Fixed OC/UC issue (was not being applied!)
      • Pulled one patch from razrqcom
    • June 22 2013 md5: bcfa0c4007f086af9a39e4ef30f3b0a5
      • Pulled latest patches from razrqcom
    • June 23 2013 md5: 45de92656debdad7058d880c97ed02e7
      • Added Wheatley governor
    • June 26 2013 md5: c212ebf42a76ab6c0eaef932f315ab49
      • Sync with razrqcom
    • June 29 2013 md5: f5e327fc05a12025efc6d6034684d972
      • Sync with razrqcom
    • July 1 2013 md5: 05be639758022c2d9c0f5e705c2ec64c
      • Sync with razrqcom
    • July 5 2013 md5: 938357c117eb15a31111cb4ea938a8f2
      • Sync with razrqcom, 33 commits behind
    • July 9 2013 md5: 4252149615150f54d6146bbc0cd6aa0a
      • Sync with razrqcom, 46 commits behind
    • July 14 2013 md5: cd506d469a63453e5478c6c52cf10ca0
      • Sync with razrqcom, 17 commits behind
    • July 15 2013 md5: 822280ed34b2f03124ce5d256338d3c3
      • Added frandom
    • July 24 2013 md5: d9b20ce4550d0c562b1794d4c574b0d8
      • Sync with razrqcom
    • July 30 2013 md5: b87008195370276e9dffd07e7232c464
      • Sync with razrqcom, 67 commits behind
    • August 4 2013
      • CM10.1 md5: 378485661c23bea3630b8e924debdce0
        • Sync with razrqcom, 85 commits behind
      • CM10.2 md5: 172b9290b2381846374e7d9348e20eb4
        • Sync with razrqcom, 85 commits behind
    • August 14 2013
      • CM10.1 md5: 037def6e81e5a3130ee56fe9025bd4a3
        • Sync with razrqcom, 36 commits behind
      • CM10.2 md5: d03285ebb52ca76b8007e2ac48cf9c5b
        • Sync with razrqcom, 36 commits behind
    • August 15 2013
      • CM10.1 md5: 2fec1735271490ae18fdfa659d54a48c
        • Sync with razrqcom, 52 commits behind
      • CM10.2 md5: 845005bc7c8f5e8ba44571800eb98327
        • Sync with razrqcom, 52 commits behind
    • August 21 2013
      • CM10.1 md5: 231afa21f16b0bc0849209089c28db9a
        • Sync with CM, 18 commits behind
      • CM10.2 md5: efb8f0ebd3cb6511fa773adb03ad24de
        • Sync with CM, 18 commits behind
    • August 31 2013
      • CM10.2 md5: 4e3ffab7ae18095f885e6ede6e961ee5
        • Sync with CM, 20 commits behind
    • September 8 2013
      • CM10.2 md5: 0a244f2098204608419c2ac76aca3ca9
        • Sync with CM, 184 commits behind
    • September 15 2013
      • CM10.1 md5: ac669007ff6f1526fdd571ac130d8cd9
        • Sync with CM, 316 commits behind
      • CM10.2 md5: b9de65f00b0ed42fc73f66d12533458d
        • Sync with CM, 112 commits behind
    • September 19 2013
      • CM10.2 md5: f3b4f54951778d1ce4ec48f998ad6e99
        • Sync with CM, 22 commits behind
    • September 29 2013
      • CM10.1 md5: 9b77d85f7c2197e176ba622bfdb864d4
        • Sync with CM, 52 commits behind
      • CM10.2 md5: e8f666bd347d750065d9d76a1ccadc38
        • Sync with CM, 30 commits behind
    • September 30 2013
      • CM10.1 md5: 1acd6515ec965c493956d348f65b89f2
        • Compile optimizations
        • Disabled touchscreen debugging
        • Syntax/compilation optimizations
        • Build flag optimizations
        • defconfig "branding" attempt
      • CM10.2 md5: c916f13e107352442d1ee380e3913ebf
        • Compile optimizations
        • Disabled touchscreen debugging
        • Syntax/compilation optimizations
        • Build flag optimizations
        • defconfig "branding" attempt
    • Oct 2 2013
      • CM10.1 md5: ebbe6eab777c963d0dcb625253e722cc
        • Enable performance & conservative governors
      • CM10.2 md5: b0d8ac2c5ee3ed45e17b4eaf739eae0b
        • Enable performance & conservative governors
    • Oct 2 2013 (#2)
      • CM10.1 md5: bec55ba211509b401615a1f93b6c9c59
        • Sync with CM (40 commits behind)
      • CM10.2 md5: 5fdfca396ef814dc1d5cab9d97a07a84
        • Sync with CM (40 commits behind)
    • Oct 7 2013
      • CM10.1 md5: a9d2095d469fcce0bafdb3fd38b81754
        • Sync with CM (15 commits behind)
      • CM10.2 md5: 66dd110b48d41af4bacbc57e8b67f65b
        • Sync with CM (15 commits behind)
    • Oct 15 2013
      • CM10.1 md5: 77557ab090738d915f4dae57eb2b0b8a
        • Sync with CM (40 commits behind)
      • CM10.2 md5: 920f0b12c471446859066d1c9862be3a
        • Sync with CM (40 commits behind)
    • Oct 23 2013
      • CM10.1 md5: 06371d2e1bd1b99cefcdfaa8ec5ba085
        • Sync with CM
      • CM10.2 md5: 8dada55939730750e1937f2567b69a75
        • Sync with CM
    • Nov 28 2013
      • CM11 md5: 88f46815029567af53f80490bc32946a
        • Sync with CM
    • Dec 2 2013
      • CM11 md5: d8988387ef47567682ac938aba27eb44
        • Sync with CM
    • Dec 28 2013
      • CM11 md5: ca95663c14fd024c1bba628936daa9a3
        • Sync with CM (3 commits behind)
    • Jan 31 2014
      • CM11 md5: a2d407bd14be860829b245f58aabe35d
        • Rebuild, needed ramdisk updates
        • Removed smoothass governor (causing build issues...)
    • Feb 21 2014
      • CM11 md5: 937fbfae56dba961d7bcc3576efbec0a
        • Rebuild, needed ramdisk updates
        • Removed smoothass governor, permanently (causing build issues...)
        • Sync with CM (6 commits behind)
    • Feb 27 2014
      • CM11 md5: c1e1915902ee08642d054c3d5f20a499
        • Sync with CM (1 commit behind)
    • Mar 4 2014
      • CM11 md5: b5f1f569cf570b8f107399bdcb0ce536
        • Sync with CM (3 commits behind)
    • Mar 9 2014
      • CM11 md5: 12d97c373f193034922d979bd1740300
        • Sync with CM (1 commit behind)
    • Mar 15 2014
      • CM11 md5: 2b853e5e5dc04fbc7f25fde94d3657e2
        • No kernel changes, only RAMdisk updates
    • Apr 3 2014
      • AnyKernel md5: 8ee557ab6d49f85d6bb75e2fad445ec3
        • Couple of updates from CM, plus first attempt at anykernel
    • Apr 29 2014
      • AnyKernel md5: bc6b87e1ddf854c17ee965936af042f6
        • Sync with CM
    • May 23 2014
      • AnyKernel md5: 9780a3ef6c05b6ad9b1f31a9a25e560e
        • Sync with CM
    • May 25 2014
      • AnyKernel md5: b1962f2606e6e1483402cf9ae732f6db
        • Built with "SaberMod" GCC 4.10 w/Graphite
    • Aug 2 2014
      • AnyKernel md5: 33fb138b8b681b7ad5a6f2fb79b5c5ca
        • Sync with CM
    • Oct 3 2014
      • AnyKernel md5: 40660b37ba6db8ada7bb4f2fb130d8ce
        • Sync with CM
    • Nov 15 2014
      • AnyKernel md5: 5d73fa287ee866825f52e504c9494b44
        • Sync with CM
    60
    Hey guys!

    As always, I take NO responsibility if you break your device. Overclocking too high can cause issues. I don't recommend overclocking more than what is provided!!!

    This is a fork of Sabbypenguin's source which is naturally a clone of the original Moto source.

    Here is my fork for stock. If you want CM10.1 (Or 10.2...), github source.

    Changelog is in second post. Wants/desires/etc in the third. Buglist is the 4th.

    The latest flashable zip is attached (0.11+ is for JellyBean 4.1.2) (Thanks Shabby for letting me kang the flashable zip :)) The changelog post will serve as an archive, as I put out more kernels ;).

    Note - if you want stock, look in the next post. If you want CM-based (10.1 & 10.2) look in post #5. Thanks!
    39
    Stock Kernels​
    Legend:
    ASA-36 (Original 4.0.4 ICS firmware)
    ASA-14 (Final 4.0.4 ICS firmware)
    FFW-5 (Latest 4.1.2 JB firmware)
    Click to show archive:
    • 0.01 ASA-36 md5: 0d5b898290d06c24d443895a14eea351
      • Built with Linaro (different toolchain)
    • 0.02 ASA-36 md5: c6bf695c00eed0aa0deb3a2e5cd150f9
      • Overclock CPU to 1.72ghz!
    • 0.03 ASA-36 md5: 517433cae48e0c138594f751d1cd5e05
      • Overclock CPU to 1.83ghz!
    • 0.04 ASA-36 md5: 09731a3af8068aebc3e23b952c7eb406
      • Overclock CPU to 1.89ghz and under to 96Mhz!
    • 0.05 ASA-36 md5: eb1ab7fbbfee7630a252b584e0ae4c84
      • GPU Overclock attempt #1... Didn't seem to make a big difference :/
    • 0.06 ASA-14 md5: 72a3f2bb0366be3e7a51019f32b27f60
      • Base kernel, sync from Moto's new source - kernel now plays nice with updated firmware (asa-14, etc)
    • 0.07 ASA-14 (redacted, issues)
      • Slight overclock, 1.62ghz
    • 0.08 ASA-14 md5: 66ed8fa671424b63e0c56c513d2e5b1b
      • More OC, 1.8ghz. Underclock to 192mhz.
    • 0.09 ASA-14 md5: 64274145336be3dce187eaee4018e328
      • Finally back to status quo on OC - 1.89ghz.
    • 0.10 ASA-14 md5: e0de88a6fa2aee5aac993b321e20ca54
      • Underclock to 96mhz
    • 0.11 FFW-5 md5: 1dcb35492b8f144fe9d9593decdda02c
      • Vanilla from Moto, for JB 4.1.2
    • 0.12 FFW-5 md5: 167613cdcd28751d1646c7134b8856bd
      • Underclock to 192mhz, Overclock to 1809mhz (couldn't quite hit 1.89ghz...)
    • 0.13 FFW-5 md5: 17cc47ef5aea7f9727fde73c60961fb0
      • Overclock to 1.89ghz reinstated
      • Fixes for over/underclock, hopefully will stick better in all apps
      • Added another step for GPU - slight overclock for GPU
    • 0.14 FFW-5 md5: 1584789c2f0638e24e46aa2a209f3ed8
      • Ability to change voltages!!! Under/overvolt to your heart's content!! (This can cause issues if you go crazy with it!)
    • 0.15 FFW-5 md5: 068a3bb9f95aea6d0cb7864561e3da0e
      • Added governors:
        • Lulzactive
        • lagfree
        • hotplug
        • smartassV2
    • 0.16 FFW-5 md5: 98026b0cafacf9363879203f0cbefd5d
      • Underclock to 96mhz (also added 144mhz step)
    • 0.17 FFW-5 md5: 1d5fafc639ad0a69ce63717b5467e0cd
      • Built with GCC 4.6 (was using 4.4.3 previously!)
    • 0.18 FFW-5 md5: 0c8ac7e8b7f057f762d69550183ada8e
      • Added schedulers:
        • SIO
        • ROW
        • BFQ
    • 0.19
      • FFW-5 md5: 7f188ae91c2ba73504bf2b49e281d982
      • ASA-14 Wifi Broken!! md5: 21391e4dbc805fb8e0089636e53be908
      • Added Wheatley governor
    22
    Wants/needs/desires/etc​

    • CPU Overclock - looks like ~1.7 maybe 1.8ghz is do-able... Done! to 1.89ghz currently. However, it doesn't seem to 'stick'? I do see it jumping around, not sure what would cause that... Analyzing... If you use NoFrills, it seems to stick. Also, would like to get the full potential out of the chip, should be able to hit 2.1ghz.
    • ROW scheduler - would like to try this, heard it helps quite a bit! Done in latest!
    • GPU Overclock - perhaps...?
    • Add more governors (Wheatley I've heard is good. Any requests?)
    • What else? :)
    18
    Buglist​

    • None that I know of... yet.

    (But I haven't really broken much either... yet ;))