[Kernel] arrrghhh's kernel!

arrrghhh · Sep 18, 2012

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!

arrrghhh · Sep 18, 2012

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.19
- FFW-5 md5: 7f188ae91c2ba73504bf2b49e281d982
- ASA-14 Wifi Broken!! md5: 21391e4dbc805fb8e0089636e53be908
- Added Wheatley governor

arrrghhh · Sep 18, 2012

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?

arrrghhh · Sep 18, 2012

Buglist

None that I know of... yet.

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

)

arrrghhh · Sep 18, 2012

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

fallnSaint · Sep 18, 2012

Nice! Will be hitting this up when I get home.

Sent from my XT897 using xda premium

Plancy · Sep 18, 2012

Thanks arrrghhh and Shabby!

Flashing now

Clocks don't stick with ROM Toolbox Pro or System Tuner.. Have not tried any others but these should work... Has always been this way though

OGL framerate seems to be locked at 57, I would love to see an unlock(to like 58

)

I'm willing to be a tester.

tetrabyt · Sep 19, 2012

Gonna give it a shot.. Brb

Holy $hit... Running smooth so far.

Sent from my XT897 using xda premium

arrrghhh · Sep 19, 2012

Plancy said:
Thanks arrrghhh and Shabby! Flashing now

Clocks don't stick with ROM Toolbox Pro or System Tuner.. Have not tried any others but these should work... Has always been this way though

OGL framerate seems to be locked at 57, I would love to see an unlock(to like 58 )

I'm willing to be a tester.

So... overclock doesn't stick after a reboot or what? I'm not following, sorry. I've just been rebooting when I flash a new kernel lol.

I've been able to squeeze 1.89ghz out of the proc, but I haven't touched 2d/3d... It's on the wishlist

. Still messing with OC, seems we should be able to hit 2.1. I also have some underclocking commits so you can set it lower than 384 or whatever the default lowest is

.

tetrabyt · Sep 19, 2012

Plancy is correct. Clock doesn't stick at max frequency. Tried setcpu, antutu cpu master pro and rom toolbox.

Sent from my XT897 using xda premium

arrrghhh · Sep 19, 2012

tetrabyt said:
Plancy is correct. Clock doesn't stick at max frequency. Tried setcpu, antutu cpu master pro and rom toolbox.

Yea, I see what you mean... Doesn't really make sense. I'm looking into it.

Meanwhile 0.04 is up with 1.89 max and 96 min. The new min should be pretty good battery savings (I hope) :good:

Plancy · Sep 19, 2012

Clocks seem to be over the place(settings just won't stick even after boot and min will go back to 384 or max will scale back down or up.. just random), it's just not really reliable at all for me except at stock, but again has always been this way.....

arrrghhh said:
Yea, I see what you mean... Doesn't really make sense. I'm looking into it.

Meanwhile 0.04 is up with 1.89 max and 96 min. The new min should be pretty good battery savings (I hope) :good:

On the OG Evo this would cause phone sleep issues, but I'll test it :good:. Thanks!

2.1GHZ woudl be insane....

---------- Post added at 03:57 AM ---------- Previous post was at 03:32 AM ----------

arrrghhh · Sep 19, 2012

Plancy said:
Weird... I get stuck at yellow Sprint boot screen... can't boot into CWM and fastboot drivers cannot be found by my computers...

looks like its bricked i guess...**** Im not covered by insurance and I need my phone tomorrow please help

Can't boot into CWM...? What does it do!? That's not good, I was going to suggest flashing an older kernel back, but... if you can't get into reco...

I've only been testing this on TWRP, but I don't see how the recovery matters... It's all the same really. I've been stuck at the 'unlocked bootloader' screen several times playing with these kernels and have always been able to get back to TWRP...

Edit - hop on IRC, I guess on #oudhitsquad...

Plancy · Sep 19, 2012

arrrghhh said:
Can't boot into CWM...? What does it do!? That's not good, I was going to suggest flashing an older kernel back, but... if you can't get into reco...

I've only been testing this on TWRP, but I don't see how the recovery matters... It's all the same really. I've been stuck at the 'unlocked bootloader' screen several times playing with these kernels and have always been able to get back to TWRP...

Edit - hop on IRC, I guess on #oudhitsquad...

Thanks a lot for jumping in quick, I just remembered I had reformatted my system a while back and lost the drivers I installed when I unlocked the bootloader... found those installed them and I was able to reflash CWM and restore my Nandroid backup(just finish this second)..

Gonna try to see what caused this(I had flash a kernel, powermenu, and custom reboot menu at the same time . . lol).

arrrghhh · Sep 19, 2012

Plancy said:
Thanks a lot for jumping in quick, I just remembered I had reformatted my system a while back and lost the drivers I installed when I unlocked the bootloader... found those installed them and I was able to reflash CWM and restore my Nandroid backup(just finish this second).. Gonna try to see what caused this(I had flash a kernel, powermenu, and custom reboot menu at the same time . . lol).

LOL

Well, at least it's OK... whew.

Plancy · Sep 19, 2012

arrrghhh said:
LOL

Well, at least it's OK... whew.

I'm okay for now.. lol

arrrghhh · Sep 19, 2012

So I don't know if it's the NoFrills app or what but my max freq isn't going nutso anymore.

Also, if I set the clock to 1.89 ghz and governor to performance, it sticks at 1.89ghz...

So, I don't know where to go with this guys. Let me know if anyone finds anything useful. dmesg didn't seem to provide any wisdom, and Moto provided a kernel that explodes dmesg on boot. It fills the buffer with so much garbage I can never see the first boot... Wraps the buffer too quickly.

gtownswagga · Sep 19, 2012

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

arrrghhh · Sep 20, 2012

So I tried applying this GPU OC... and it didn't really seem to help. I did 10 samples each of the AnTuTu 3D test and the averages were almost identical.

I'll release the kernel, but I don't really see any tangible benefit from the change. Let me know if you guys find something better/different to do for this GPU OC. Thanks!

Plancy · Sep 20, 2012

arrrghhh said:
So I tried applying this GPU OC... and it didn't really seem to help. I did 10 samples each of the AnTuTu 3D test and the averages were almost identical.

I'll release the kernel, but I don't really see any tangible benefit from the change. Let me know if you guys find something better/different to do for this GPU OC. Thanks!

Maybe there's a real FPS cap?

[Kernel] arrrghhh's kernel!

Inactive Recognized Developer

Inactive Recognized Developer

Inactive Recognized Developer

Inactive Recognized Developer

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Similar threads

Top Liked Posts