Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,741,979 Members 46,338 Now Online
XDA Developers Android and Mobile Development Forum

[SM-T320] [ROM] [4.4.4] [-O3] [Linaro] Source Build CyanogenMod 11 [Overclocked]

Tip us?
 
vikrant82
Old
#1  
Senior Member - OP
Thanks Meter 69
Posts: 153
Join Date: Dec 2010

 
DONATE TO ME
Default [SM-T320] [ROM] [4.4.4] [-O3] [Linaro] Source Build CyanogenMod 11 [Overclocked]

Build compiled from our CM branch sources with various optimizations.

V3.1 released

Time for some governors

V3.1 [Changelog] (Includes all previous versions)
- Removed Pegasusq
- Added Intelliactive and Intellidemand. So we have 3 new governors to play with now.
- Disabled thermal logging (They have been storming our logcats)

V3 [Changelog] (Includes V1 and V2 changes)
- Newer adreno libs (with video playback)
- Added governors - PEGASUSQ and InterativeX [After some testing - avoid pegasusq. Seems unstablish.]

Time for some overclocks.

V2 [Changelog] (Includes V1 changes)
- Stable GPU and CPU overclocks.
- Use newer linaro release - Linaro GCC 4.8.2014.03
- CPU overclocked to 2419.2 Mhz
- GPU overclocked up to 500Mhz

There are two V2 builds attached - One with 487.5Mhz and other with 500Mhz. I recommend 487.5 version.
There is also a standalone kernel from V2 build attached (GPU @500) but since it's using a different toolchain I am not sure it works with CM nightlies.

After lot of iterations and testing these overclocks seem to be stable over various benchmark suites. This is on a device which won't tolerate any overclock on beastmode kernel shared over other thread.

V1 [Changelog]
- Compiled with famous Linaro toolchain - (GCC 4.8.3)
- Some compiler optimizations e.g. Use O3 compilation flags instead of Os
- Picked some general compiler optimizations from JustArchi https://github.com/JustArchi/android_build/commit/0cf89401cc8092dda959b5746ec4899fda756cec)
- Some patches for GCC 4.8 compilation and ART compatibility.
- exFAT compiled with Os (it breaks with O3)
- Some mixer_paths patches (for higher audio) and button light fixes (to not glow on screen touch)

(For more details google about Linaro toolchain / O3 benefits)

Install ?
- Regular zip install
- Can install over existing nightlies (<= 2507)

Issues ?
- Some google play images (or rather icons) might be gibberish. Its a known issue with Linaro 4.8 toolchain. Nothing serious just cosmetic. Older playstore 4.7.x doesnt suffer from this issue. Bug item - https://bugs.launchpad.net/linaro/+bug/1332989

Next:
- Keep adding performance tweaks.
- Linaro 4.9 - Facing isses with adreno library crashes. Need to try with newer adreno libs.
- Feel free to point me to any more optimizations and we can try them here.

Branches(Github):
Coming soon.

Downloads


V1 - cm-11-20140716-Linaro-O3-mondrianwifi[1].zip
V2 (CPU 2419Mhz, GPU 487.5 MHz)- cm-11-20140725-Linaro-O3-OC-mondrianwifi.zip
V2 (CPU 2419Mhz, GPU 500Mhz) - cm-11-20140726-Linaro-O3-OC-mondrianwifi_GPU500.zip
V2 Kernel (CPU 2419Mhz, GPU 500Mhz) - cm-11-20140726-Kernel-Linaro-O3-OC-mondrianwifi.zip
V3 (CPU 2419Mhz, GPU 500Mhz) - V3-cm-11-20140727-Linaro-O3-OC-mondrianwifi.zip
V3 Kernel (CPU 2419Mhz, GPU 500Mhz) - cm-11-20140727-Kernel-Linaro-O3-OC-mondrianwifi.zip

V3.1 (CPU 2419Mhz, GPU 500Mhz) - V3.1-cm-11-20140729-Linaro-O3-OC-mondrianwifi.zip
V3.1 Kernel (CPU 2419Mhz, GPU 500Mhz) - V3.1-cm-11-20140728-Kernel-Linaro-O3-OC-mondrianwifi.zip

And here's 2457Mhz kernel for strong hearts.


XDA:DevDB Information
[SM-T320] [ROM] [4.4.4] [-O3] [Linaro] Source Build CyanogenMod 11 [Overclocked], ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4

Contributors
vikrant82
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod

Version Information
Status: Testing

Created 2014-07-17
Last Updated 2014-07-29
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2014-07-26-13-32-18.png
Views:	105
Size:	191.4 KB
ID:	2870958  
The Following 12 Users Say Thank You to vikrant82 For This Useful Post: [ Click to Expand ]
 
csjneek
Old
(Last edited by csjneek; 17th July 2014 at 04:11 PM.) Reason: sorry wrong link
#2  
Senior Member
Thanks Meter 2
Posts: 193
Join Date: Oct 2006
excellent!
I'll try it later.

I always flash PurePerformances™X mod after every nightlie and it feels somewhat faster after it. I did flashed it on all my devices.
Maybe you can insert it in your future builds.

Keep them coming !

LE: mod link fixed
Samsung Galaxy S3 I9305
Samsung Galaxy S4 I9505
Samsung Galaxy TabPro 8.4 T320
Pipo MaxM8
 
n64man
Old
#3  
Junior Member
Thanks Meter 21
Posts: 19
Join Date: Dec 2008
Thanks for this... Will give it a shot!
 
n64man
Old
#4  
Junior Member
Thanks Meter 21
Posts: 19
Join Date: Dec 2008
For anyone wanting to try this.. So far so good here. Hasn't been running long enough to make any major comparisons yet. Clean flashed, so not sure about dirty flashing.
 
csjneek
Old
#5  
Senior Member
Thanks Meter 2
Posts: 193
Join Date: Oct 2006
I installed it over nightly and it runs pretty well but the playstore icons bug is pretty bad.
For now I moved on to the next nightly but if you can fix that bug I will surely flash it again.
Samsung Galaxy S3 I9305
Samsung Galaxy S4 I9505
Samsung Galaxy TabPro 8.4 T320
Pipo MaxM8
 
vikrant82
Old
#6  
Senior Member - OP
Thanks Meter 69
Posts: 153
Join Date: Dec 2010

 
DONATE TO ME
Quote:
Originally Posted by csjneek View Post
I installed it over nightly and it runs pretty well but the playstore icons bug is pretty bad.
For now I moved on to the next nightly but if you can fix that bug I will surely flash it again.
Should be fixed with Linaro 4.9 (thats next). Trying out a few more optimizations for next build (expect to post one on weekend). Target is to beat benchmark scores from stock.
The Following User Says Thank You to vikrant82 For This Useful Post: [ Click to Expand ]
 
crpalmer
Old
#7  
Senior Member
Thanks Meter 1997
Posts: 1,520
Join Date: Mar 2011

 
DONATE TO ME
Quote:
Originally Posted by vikrant82 View Post
Should be fixed with Linaro 4.9 (thats next). Trying out a few more optimizations for next build (expect to post one on weekend). Target is to beat benchmark scores from stock.
Don't pay attention to benchmarks....

If you want to meet or beat stock, just turn off thermal throttling, enable all 4 cores and set performance as the governor. Make it a fair comparison...
The Following User Says Thank You to crpalmer For This Useful Post: [ Click to Expand ]
 
iamnotkurtcobain
Old
#8  
iamnotkurtcobain's Avatar
Senior Member
Thanks Meter 2279
Posts: 7,607
Join Date: Oct 2010
Finally a linaro build!! Keep up the great work! Could you modify the kernel too? Overclock cpu and gpu would be awesome...

Gesendet von meinem SM-T320 mit Tapatalk
 
vikrant82
Old
(Last edited by vikrant82; 20th July 2014 at 10:29 AM.)
#9  
Senior Member - OP
Thanks Meter 69
Posts: 153
Join Date: Dec 2010

 
DONATE TO ME
Quote:
Originally Posted by crpalmer View Post
Don't pay attention to benchmarks....

If you want to meet or beat stock, just turn off thermal throttling, enable all 4 cores and set performance as the governor. Make it a fair comparison...
@crpalmer

I suppose we are talking about /etc/thermal-engine-8974.conf, /etc/thermal-engine.conf (symlinked to thermal-engine-8960.conf) and /etc/thermald.conf (symlinked to thermal-8960.conf) on cm builds. They seem to be using different set of values from stock.

Can't we not use these values/files directly-from/similar-to stock builds ? As the thermal engine libs and binaries we are directly picking from stocks ?

Is stock too aggressive or CM too defensive ?

Also noticed that these linked files are broken as well. (no thermal-engine-8960.conf and thermal-8960.conf). Some build script issues ?
 
crpalmer
Old
#10  
Senior Member
Thanks Meter 1997
Posts: 1,520
Join Date: Mar 2011

 
DONATE TO ME
Quote:
Originally Posted by vikrant82 View Post
@crpalmer

I suppose we are talking about /etc/thermal-engine-8974.conf, /etc/thermal-engine.conf (symlinked to thermal-engine-8960.conf) and /etc/thermald.conf (symlinked to thermal-8960.conf) on cm builds. They seem to be using different set of values from stock.

Can't we not using these values/files directly-from/similar-to stock builds ? As the thermal engine libs and binaries we are directly picking from stocks ?

Is stock too aggressive or CM too defensive ?
I wasn't suggesting that you turn that off permanently, that's just what the stock ROM is most likely (automatically) doing when you run a benchmark. That's how you get a higher score, not how you have a better ROM...

My point being, don't worry about whether or not the scores are better, worry about the whole experience being better (which is very much is). On a phone of mine, CM was way more performant even though it scored less than half of stock's Quadrant score.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes