Database Develop

[Q] Overclocking the Tab

Hey does someone know the overclock configuration that was posted on the Overcome page once? I'm running on Overcome 4.1 with the belonging Kernel which allows me to get to 1.6ghz (theoretically) and I'd like to overclock to 1.2ghz.
I'd be very grateful if you could help me
Edit: I found this http://forum.xda-developers.com/showthread.php?t=1036020 but does this guide also apply to Overcome 4.1?

Just use Voltage Control or SetCPU. It's really not that hard at all. Just be careful with your voltages-overvolting will eat your battery more but may allow you to reach higher frequencies, and undervolting may get you better battery life but may make your tab unstable.
As a reference, I have my Tab running at 100-1.4 with smartassv2 and stock voltages on the Overcome 4.0 kernel.
Sent from my SCH-I510 using xda premium

thanks ;-) but which sheduler do you use?
for those who also have problems with overclocking and for
the newbies (like me =-D) I found this page which describes the usage of shedulers
and governors http://forum.xda-developers.com/showthread.php?p=19846297

IO Scheduler: CFQ
Governor: Smartassv2
At least that's what I use on my phone. I just left everything alone on my tab.
Sent from my SCH-I510 using xda premium

thanks, you helped me a lot ;-)
I'm using Voltage Control on 1.3ghz with stock voltages on smartassv2 and deadline and it runs pretty stable

Thanks, useful tip for me too.

I use SetCPU
OC max 1.3GHz, min 100MHz
-75mV from 100Mhz --> 1.0GHz and then -50 from 1.0GHz to 1.3GHz
PLUS various profiles to set max to 800MHz whilst screen off etc etc

that's exactly the same that I did =-D=-D=-D

That's pretty much what I have. OP, sorry I couldn't answer your PM, my tab is currently bricked and I haven't had the chance to recover it.
Sent from my SCH-I510 using xda premium

yea I have time =-D that's not so important, just make sure your tab runs again ;-)

phlooke said:
I use SetCPU
OC max 1.3GHz, min 100MHz
-75mV from 100Mhz --> 1.0GHz and then -50 from 1.0GHz to 1.3GHz
PLUS various profiles to set max to 800MHz whilst screen off etc etc
Click to expand...
Click to collapse
This is what worked for me as well, just don't check"set at boot" option till you've tried that speed for a few days and you config proves stable.

Joe Blough said:
This is what worked for me as well, just don't check"set at boot" option till you've tried that speed for a few days and you config proves stable.
Click to expand...
Click to collapse
Haha, I did check that option when I foolishly set the OC max to 1.6GHz
...I was just able to uninstall between one of the many lopping reboots
Anyway all, sorted now. In fact I have reverted to stock voltage for 1GHz up to 1.3GHz because playing Trial Xtreme2 would cause a reboot when I'd exited the game - seem's all ok now *touches wood*

[Kernel] MetalliKernel CM9-HWA a6 [150-1380mhz] [384mhz GPU] [7/5 - Feature List]

This kernel is built for and from codeworkx's CM9 with hardware acceleration.
Again this is for codeworkx's cm9.
One more time, this is for codeworkx's cyanogenmod 9.
Finally, this is for cm9 and cm9 only!
Don't let the "alpha" title fool you into thinking it's not stable... it is... It's only alpha because it's still in the "testing" phase.
Works on the P31XX. I don't know about other models.
FEATURES/CHANGES
Overclockable to 1.38GHz
Underclockable to 150MHz
GPU overclocked to 384MHz (highest possible without bottlenecking and battery waste)
Tuned OnDemand Governor (recommended)
Interactive Governor with time view concept (learns from your use and adjust parameters accordingly)
Wheatley Governor (optimized use of C4 state)
Hotplug Governor (turns of one of the cpus to save power when load is very low)
Pegasusq Governor (A better version of Hotplug, but experimental and not designed for our devices)
SIO scheduler for speed/performance with flash storage
Linaro Toolchain
Linaro optimizations and patches
Linaro makefile compiler flags
Makefile Optimizations to boost performance
Optimized CRC32
Optimized ARM RWSEM algorithm
Tiler Memory increased to 32MB (linaro)
Other Tiler patches/tweaks to improve 2D gpu performance
SLQB allocator
lib/string use glibc version for speed
lib/memcopy use glibc version for speed
lib/sha1: use the git implementation of SHA-1 and removed ARM sha1 routines
I/O backport from 3.2 linux kernel for less dirty throttling
Tweak CPUIDLE to enter deep sleep faster thus saving battery
LowMemoryKiller backported from 3.4 kernel
Disable GENTLE_FAIR_SLEEPERS for improved performance
Allow Deep Sleep to occur when media decoder is active allowing the cpu to shut off when playing music or video.
Allow MPU logic to power down when in deep sleep to save power.
Increased default readahead value to 1024KB for faster sdcard reads
A lot of stuff I probably forgot I did.
Also includes a ridiculous amount of bugfixes, patches, and tweaks that can found on my github commit log.
***Read Me***
DO NOT, UNDER ANY CIRCUMSTANCE, USE SETCPU PROFILES OF ANY KIND OR ANYTHING SIMILAR WITH THIS DEVICE. Things like screen off max frequency, temperature throttling, and others are already built in to the OMAP architecture. Using ANY profiles will ONLY lead to problems, instabilities, and battery drain.
***************
Let me know how it "feels" especially by default without overclocking or underclocking. Also I'd be interested in how the battery treats you. Thanks!
DOWNLOAD
a1 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a1.zip
a2 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a2.zip - Changes to: Wifi, GPU, Low Memory Killer, others
a3 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a3.zip - Changes to: ondemand, interactive, add wheatley, add pegasusq, deep idle, compiler flags, SDcard read, others
a4 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a4.zip - Changes to: Compiler flags, CPUidle, RCU, others.
a5 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a5.zip - reverts and bugfixes, use 10.1 ramdisk in 10.1 version
a6 - http://goo.im/devs/Metallice/Tab2/MetalliKernel_CM9_a6.zip - CLASSIFIED change, NEED feedback on speed, slowness, smoothness, and lag compared to stock and a5. Reverted some revets. Reverted changes to RCU to fix SODs. Graphics. For 10.1 fixed overclocking.
If you would like to overclock but your device can't handle it... and are willing to suffer through extreme battery drain to try this - Link
Thanks go out to - CodeworkX, Ezekeel, Francisco Franco, Imoseyon, Faux123, Fugumod, Sonicxml, Texas Instruments, Samsung, Google, and all the others I probably forgot about. Sorry!
Source
https://github.com/Metallice
______________________________________________________________________________________________________________________
So, I'm a broke college student without a job this summer - instead taking extra classes and studying like crazy for the MCAT. If you like my work and want to thank me, feel free to buy a coffee or an energy drink so I can continue to stay up late studying and working on Android stuff (or help me pay for med school ). I don't want to have to choose! Thanks and I appreciate your support!

I like this format, just like Trinity kernel. Much less placebo for added things. Like, "zOmg, linaro made my phone fly! Thanks for including it, it rocks!!!!!" With the things being changed kept hidden, I'd LOVE for you to release a couple builds, with different compile dates, without changing a thing, but telling people you did. Watch the placebo roll in, ha

Thank god you released this. Seriously the only thing this ROM was missing was a little OC. You guys are really making this purchase (Getting the GTab 2) a really good idea!
Sent from my GT-P3113 using Tapatalk 2

Will this kernel work on p3100 becaise all i see around here all the custom roms and kernels are for p3113 so please just confirm the models on whicj it would be flashable.
Thanx
Sent from my GT-P3100 using Tapatalk 2

tapan15in said:
Will this kernel work on p3100 becaise all i see around here all the custom roms and kernels are for p3113 so please just confirm the models on whicj it would be flashable.
Thanx
Sent from my GT-P3100 using Tapatalk 2
Click to expand...
Click to collapse
I don't know. I have no way of testing.
Sent from my GT-P3113 using xda premium

Oh yeah. You da man!

Just flashed... will give updates on how it is running.. so far so good!!
Sent from my GT-P3113 using xda app-developers app

cannt wait for this, thank u so much
I will tell my feeling about this after I flashed it
Sent from my GT-P3110 using Tapatalk 2

Runs smooth and stable at 1380mhz on my 3113. Thank you for your hard work! On a related note, what governor do you recommend? In your experience, does using hotplug actually save battery?

yes it is working with 3100. great job.

Flashed this on my P3110, and it bricked it NOT.
Thanks for this. Waiting to see what more you will add to the kernel.
Cheers.

I've got a question. Does the tab 2 not have a CPU temp Senser?
Sent from my GT-P3113 using xda premium

Been using this since last night and so far no RR or SOD's. Everything is running smooth without any errors, glitches, etc. Great work, as always, Metallice!
---------- Post added at 11:37 AM ---------- Previous post was at 11:37 AM ----------
Kidney Poker said:
I've got a question. Does the tab 2 not have a CPU temp Senser?
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
I don't know, but wander why you would ask?

miketoasty said:
Been using this since last night and so far no RR or SOD's. Everything is running smooth without any errors, glitches, etc. Great work, as always, Metallice!
---------- Post added at 11:37 AM ---------- Previous post was at 11:37 AM ----------
I don't know, but wander why you would ask?
Click to expand...
Click to collapse
CPU controllers have a temp read out. I like having one. I know most apps pull the info from kernel. Was trying to find out if we have the hardware built in and the kernel isn't passing info or if the hardware is just not there.
Sent from my GT-P3113 using xda premium

Maybe it's just my tablet, but I can't get any clock speed greater than stock to work. Tried it on this kernel and one I did myself.

Kidney Poker said:
I've got a question. Does the tab 2 not have a CPU temp Senser?
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
Yeah the omap does. Not sure if I turned it on or not. If its on you can get the temp from dmesg I believe.
Sent from my Galaxy Nexus using xda premium

imnuts said:
Maybe it's just my tablet, but I can't get any clock speed greater than stock to work. Tried it on this kernel and one I did myself.
Click to expand...
Click to collapse
I can try adding a 1.1ghz slot?
Sent from my Galaxy Nexus using xda premium

Kidney Poker said:
CPU controllers have a temp read out. I like having one. I know most apps pull the info from kernel. Was trying to find out if we have the hardware built in and the kernel isn't passing info or if the hardware is just not there.
Sent from my GT-P3113 using xda premium
Click to expand...
Click to collapse
Most apps actually pull their info from the battery temp and are unreliable.
Sent from my Galaxy Nexus using xda premium

nphil said:
Runs smooth and stable at 1380mhz on my 3113. Thank you for your hard work! On a related note, what governor do you recommend? In your experience, does using hotplug actually save battery?
Click to expand...
Click to collapse
OnDemand. I don't bother with hot plug as I don't see any benefit. If you do a lot of non interactive activities like reading or music it may be helpful, but I would try the 200mhz min before I try hot plug.
Sent from my Galaxy Nexus using xda premium

Have you flashed on cm9 or stock rom??
Sent from my GT-P3100 using Tapatalk 2

how i configure CastagnaKernel OV for have max performance

how i configure CastagnaKernel OV for have max performance without trasform in cheese my cpu? what the governor? the i/o scheduler and the processor mhz?
Sorry for my bad english,but i am an ignorant

OV? Over-volt? do you mean OC? Overclock or UV? Undervolt
smartassV2/SIO (personal favourites)
245mhz/1800mhz (so default settings)
And I think you can better post this in the topic itself, and you will never turn your cpu into cheese, i once ran a benchmark at 2.016Ghz, and it just turned off

broodplank1337 said:
OV? Over-volt? do you mean OC? Overclock or UV? Undervolt
smartassV2/SIO (personal favourites)
245mhz/1800mhz (so default settings)
And I think you can better post this in the topic itself, and you will never turn your cpu into cheese, i once ran a benchmark at 2.016Ghz, and it just turned off
Click to expand...
Click to collapse
I remembered the cranium kernel at 2016 mhz..it became really hot...
Ondemand( little bit tweaked) 368 1804 sio...that s perfect
Q.D.E.

It would be better if you post this on kernel's thread I think there is no need to made a new post about that and sorry but and I'm not trying to be disrespectful. however you can use smartassv2 245-1800mhz that's a good choice.
Sent from my GT-I9001 using xda premium

the combination of default: lulzactive + sio is very performant (CFS version)
or you can try the governor lagfree
if you want the best reactivity using the BFS kernel version,
but is less multitasking

[KERNEL][4.4][KK] franco.Kernel.Plus r203 RC3 (03/15) | discontinued

franco.Kernel +
*Discontinued*
These are my personal franco.Kernel builds with some modifications, explained below.
Things I want to achieve with this mod:
- more battery life
- same more performance as stock
- smooth ui / games
- less heat
Highlights:
Advanced Dynamic Scaling:
The interactive governor will now use different values for up_threshold, timer_rate and min_sample_time for every cpu_core and gpu_idle state. If the gpu is busy, the governor will use values for more performance and if it is idle, it will use conservative settings.
The current values, feel free to suggest other.
Code:
/* up_threshold, timer_rate, min_sample_time */
static unsigned int interactive_val[GPU_STATE][ACTIVE_CORES][TUNABLES] =
{{
/* gpu idle */
{100, 40000, 10000},
{100, 40000, 20000},
{100, 40000, 30000},
{100, 40000, 40000}
},{
/* gpu busy */
{90, 20000, 40000},
{90, 20000, 40000},
{95, 20000, 60000},
{95, 20000, 80000}
}};
Dynamic Touchboost:
The touch boost is only active if something is rendered on the screen, that means the boost will pause as long as there is no movement, but it will resume when it is actually necessary. It will double the actual cpu load and calculate the frequency, the maximum is input_boost_freq. This aggressive calculation offers a smooth ui, but it can also save battery, because you will often don't need input_boost_freq when the screen is touched.
New Hotplug Solution:
Instead of linking core0 to core2 and core1 to core3, all cores a controlled separately. This should prevent an excessive hopping up and downwards. The load is calculated with all active cores to get the performance we actually need.
After some time (if 2 core touchboost is active) and not touching the screen, only 1 core will stay online to save a bit more battery.
It will use different up and down thresholds for each gpu_idle and cpu core state.
Code:
/* down threshold, up threshold */
static unsigned int hotplug_val[GPU_STATE][ACTIVE_CORES][TUNABLES] =
{{
/* gpu idle */
{0, 70},
{40, 80},
{50, 90},
{60, 100}
},{
/* gpu busy */
{0, 60},
{30, 60},
{30, 65},
{40, 100}
}};
https://github.com/reborn90/mako/blob/nightlies-4.3/arch/arm/kernel/mako_hotplug.c
Smooth thermal throttling:
When the temperature hits the threshold, the frequencies won't be limited immediately but scaled down step by step to prevent lagspikes from jumping between 1,5 and 1GHz (if the current temperature allows it). This mod is absolutely not made for benchmarks because my solution is as agressive as the original one. There are other good kernels to melt your device.
https://github.com/reborn90/mako/blob/nightlies-4.3/drivers/thermal/msm_thermal.c
Recommended settings (default):
thermal threshold: 65
Hotplug:
high load: 60
low load: 30
cores on touch: 2
Interactive governor:
dynamic_scaling: true
input_boost_freq: 1134MHz
input_boost_freq_duration: 1500
Interactive gpu governor:
up_threshold: 60
down_threshold: 25
Per app settings tipp:
Set input_boost_freq to the lowest frequency for games.
Github:
https://github.com/reborn90/mako/tree/nightlies-4.4
MD5
bbe66dc7ac213081f423eb0435495ad6 franco.Kernel.Plus-r193-1110-JSS.zip
8c2428486e1b0492e494ebd6252e83ed franco.Kernel.Plus-r193-1110-JSS-CAF.zip
d674f49b81586a342be73b315dc30af3 franco.Kernel.Plus-r193-1110-JWR.zip
9a1300d5103cfa4d26ed0c7fce0b2b4e franco.Kernel.Plus-r194-1121-KRT.zip
a06c7609c9b79c36cedd933f6ea57ae5 franco.Kernel.Plus-r194-1127-KRT.zip
3e53f4bda0d3ae8716187bc8bd7a3f18 franco.Kernel.Plus-r198-1209.zip
eec2e964e417d76105b13cf3f700056b franco.Kernel.Plus-r200-0101.zip
ca227545fb5efe75c05836041f396e98 franco.Kernel.Plus-r203-0124.zip
Hit thanks if you like it.
Buy Franco's app or just a coffee for me.
I'm testing all my builds and use them daily, but I am not responsible for any kind of damage on your device.
Which version should I choose?
- JWR for stock 4.3
- JSS for JLS roms
- JSS-CAF for cm 10.2
- builds >= r194 are for Android 4.4 Kitkat (KRT)
- builds >= r198 are for Android 4.4.1 and 4.4.2 Kitkat (KOT)
- KRT is compatible with KOT and vice versa
- cm 11 is not compatible
r203 RC1 (02/04): http://forum.xda-developers.com/showpost.php?p=50079790&postcount=835
r203 RC2 (02/09): http://forum.xda-developers.com/showpost.php?p=50189367&postcount=848
r203 RC3 (03/15): http://forum.xda-developers.com/showpost.php?p=51109943&postcount=890
The recommended settings above are not made for the release candidates.
Recommended ROM: AOSPA PARANOIDANDROID 4.0

Current changelog:
based on r203
- updated franco's interactive gpu governor
- lowered threshold for 4th cpu core
- added (modified) generic touchboost driver from franco
- updated FauxSound to version 3.2
regular changelog:
http://192.241.177.15/Nexus4/4.4/appfiles/changelog.xml
Old changelogs:
Code:
[U](01/01)[/U]
based on r200
- new dynamic hotplug values
- awesome row io scheduler improvements
[U](12/09)[/U]
based on r198
- 4.4.1 update
- hotplug and interactive gov update
- dynamic io_is_busy decision
- fix for wrong load calculation while the device is throttled
[U](11/27)[/U]
based on r194
- (re)added FauxSound and FauxSpeaker
[U](11/21)[/U]
based on r194
- Kitkat update
- quick fix: I forgot to disable some debug logs, sry!
[U](11/10)[/U]
based on r193
- new dynamic touchboost
- hotplug speed is now based on gpu_idle
[U](10/28)[/U]
based on r193
- MultiROM is activated now
- hotplug tweaks
[U](10/15)[/U]
based on r191
- reverted interactive governor
[U](10/13)[/U]
based on r191 (test release)
- new interactive governor, not fully optimized jet
- phone wakeup tweaks, again
[U](10/03) [/U]
based on r188
- fixed a bug which caused way too high gpu frequencies
- tweaked hotplugging at wakeup a bit
- more conservative hotplug values (+20) if gpu_idle and dynamic_scaling are true
[U](9/23) [/U]
based on r184
- only upstream merge
[U](9/16) [/U]
based on r183
- reimplemented gpu_idle detection with interactive gpu governor
- merging and syncing
- raised min voltage to 650
[U](9/12) [/U]
based on r182
- Advanced Dynamic Scaling
- touchboost tweaks
- touchboost duration reduced to 1500ms
- much better gaming performance
- FauxSound
[U](8/04) [/U]
based on r182
- Interactive: removed unused hispeed freq
- no ondemand for now, needs way too much battery
[U](8/31) [/U]
based on r178
- Smart Touchboost added
- instant touchboost without waiting for governor
- touchboost duration raised to 2sec
- better performance for low end games (Doodle Jump)
- little bugfixes
[U](8/24) [/U]
based on r178
- enabled wakelock stats
[U](8/20) [/U]
based on r176
- new hotplug driver
- new thermal throttling
- correct load calculation while throttled
- interactive gov: new dynamic tunables
- gpu driver: new average load calculation
- new frequencies 270MHz and 162MHz
- lower minimum voltages 600mV
- instant touchboost when unlocking the device

1st one to drop and say thanks a lot

Any deadlock issues?
Sent from my Nexus 4 using xda app-developers app

Deggy said:
Any deadlock issues?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Same as the original ones.

Deggy said:
Any deadlock issues?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Only on jss I think..!
Inviato dal mio Nexus 4 usando Tapatalk 4

Module support is enabled?
Enviado desde mi Nexus 4 usando Tapatalk 4

ironjon said:
Module support is enabled?
Enviado desde mi Nexus 4 usando Tapatalk 4
Click to expand...
Click to collapse
Same as Franco or, if I have to do that, not jet.

Are kernel wake lock stats available as well ?
Sent from my Nexus 4

joshuab227 said:
Are kernel wake lock stats available as well ?
Sent from my Nexus 4
Click to expand...
Click to collapse
good idea, I will readd them

Awesome. More toys!
And I like what the first thing said, more battery life. Still searching for the ROM that can give me 8 hours SOT.

KiD3991 said:
Still searching for the ROM that can give me 8 hours SOT.
Click to expand...
Click to collapse
HAHA!! Aren't we all!!
At 162mhz the lowest I could UV is 650. So remove set at both if you wish to try lower
Sent from my Paranoid Nexus 4

BoOsT said:
HAHA!! Aren't we all!!
At 162mhz the lowest I could UV is 650. So remove set at both if you wish to try lower
Sent from my Paranoid Nexus 4
Click to expand...
Click to collapse
You mean 192mhz?
Eh, since my CPU binning is at nominal only, I dare not UV more than 100 though.
And afaik, UV excessively does not actually help save battery, instead it uses more power. Somebody made a test, its somewhere in XDA.
I can reach 7 hour SOT in 4.2.2, I just lost that screenshot somewhere, in 4.3 I have yet to find it(5 hour SOT is not hard).

Shows 162. Undervolting your device reduces the power the processor receives to only what it needs to run. If you don't suffer any I'll effects in performance I don't see how u would lose battery. However, I'm a try it and see how it works kinda guy.
Sent from my Paranoid Nexus 4

Is this working with touch control? Modules enabled?
Sent from my Nexus 4 using xda app-developers app

thanks for your great job! I have tried the kernel and my phone runned smoothly! :laugh:

Same here... Working great!
Sent from my \m/ Nexus 4
PA + Franco

KiD3991 said:
You mean 192mhz?
Eh, since my CPU binning is at nominal only, I dare not UV more than 100 though.
And afaik, UV excessively does not actually help save battery, instead it uses more power. Somebody made a test, its somewhere in XDA.
I can reach 7 hour SOT in 4.2.2, I just lost that screenshot somewhere, in 4.3 I have yet to find it(5 hour SOT is not hard).
Click to expand...
Click to collapse
Does UV excessively not actually help save battery? I am interest in this. Could you please give me the link you montioned? Thanks a lot!

edians said:
Does UV excessively not actually help save battery? I am interest in this. Could you please give me the link you montioned? Thanks a lot!
Click to expand...
Click to collapse
It doesn't... It helps other things like heat which would help your battery health and lifespan on the long run..
Sent from my \m/ Nexus 7
PA + Franco

Luigiesin said:
It doesn't... It helps other things like heat which would help your battery health and lifespan on the long run..
Sent from my \m/ Nexus 7
PA + Franco
Click to expand...
Click to collapse
This guy is right.
It keeps heat down, but might result in higher battery consumption in some cases.

[KERNEL][4.4.2][WIP][SGP311/312]UnleaZhed XTZ Kernel v0.2

Hello! This is my first kernel, The UnleaZhed XTZ Kernel. I'm a noob in developing a kernel, so some bugs may be found in this kernel and I may not be able to fix them! One more important thing, this kernel uses the sources from some developers and I'm here to present my greatest thanks to everyone of them!
FLASH AT YOUR OWN RISK!!​
UnleaZhed XTZ Kernel
Requirements:
4.4.2 Xperia Tablet Z Wi-Fi version (SGP311/312)
Unlocked bootloader
Fastboot driver installed computer
Features:
CPU overclock up to 1836MHz
CPU UV by 100 default
CPU UV control
GPU overclock up to 450MHz (due to some bandwidth problem)
Use auto CPU hotplug instead of MP-Decision
Some minor things
!!recovery has resolution problem ATM!!
Click to expand...
Click to collapse
Installation:
1. Make your Tablet Z in fastboot mode
2. On your computer, open cmd and navigate to the location of kernel
3. Type "fastboot flash boot Kernel_name.img
4. Type "fastboot reboot"
5. Enjoy!
Downloads:
UnleaZhed XTZ v0.1
UnleaZhed XTZ v0.1.1
UnleaZhed XTZ v0.2
Credit:
DoomLoRD
thalamus
Sony
Faux123
Source:
My Github

Nice try but do you have any plans for an aosp kernel?i like overclock and the extra features but it is too tough to say goodbye to pac rom

pangiotis24 said:
Nice try but do you have any plans for an aosp kernel?i like overclock and the extra features but it is too tough to say goodbye to pac rom
Click to expand...
Click to collapse
Will do but it may be done in the next month, Thanks for your suggestion.

First of all THANK YOU for spending your time on this and sharing your result with us!
Just flashed the kernel! Good news...nothing is bricked
CPU Spy Plus indeed shows 1836 Mhz used! I did´t do anything for that.
You might re-think this. Using 1512Mhz instead by default and let the users choose that high speed CPU mode themselves as it may not be stable on all devices.
That 324Mhz added is a huge step...there is no step in between possible?
What about voltages. Did you modify anything? Is the voltage raised to achieve the high cpu frequency? Please post some more information about what happens here...
In fact I´m just running Antutu to see general stability on my device.
VERY BAD score. Before your kenel there were 20300 points. Now with OC only 19746.
=====================================================================
EDIT: Just recognized.... several questions are being answered by Antutu CPU Master.
1512 IS USED by default!
1620Mhz and 1728 Mhz are there to choose and of course finally the 1836Mhz.
Scaling is interactive by default (changed to my fav ondemand)
I/O Scheduler is cfq by default (changed to my fav noop)
Antutu Score @ 1836Mhz: 16077Mhz ???
Lower than without OC? Needs retesting (14230 point when setting max to 1836Mhz and Min to 1512Mhz(!!!???)...maybe the benchmark is wrong...Will give it some time to see if I myself feel a speedup.
After Restart Antutu Score ends up @ 19761 points...not bad. but clearyl not enough looking at the massice OC done. REBOOT! Tab just rebooted! So 1836Mhz is not stable at mine! Trying 1728Mhz now instead.
18139 points....this kernel lacks some serious power if we can believe the scores of antutu. This is a V0.1 so nothing to worry too soon. You´ll make it find it´s power
Switched back to kernel from pulser_g2 (http://forum.xda-developers.com/showthread.php?t=2444452) and 19908 points without any OC! You may look into it.
But please answer the other questiones I wasn´t able to clear myself.
Greetings
Rodger

DJ-Tumor said:
First of all THANK YOU for spending your time on this and sharing your result with us!
Just flashed the kernel! Good news...nothing is bricked
CPU Spy Plus indeed shows 1836 Mhz used! I did´t do anything for that.
You might re-think this. Using 1512Mhz instead by default and let the users choose that high speed CPU mode themselves as it may not be stable on all devices.
That 324Mhz added is a huge step...there is no step in between possible?
What about voltages. Did you modify anything? Is the voltage raised to achieve the high cpu frequency? Please post some more information about what happens here...
In fact I´m just running Antutu to see general stability on my device.
VERY BAD score. Before your kenel there were 20300 points. Now with OC only 19746.
=====================================================================
EDIT: Just recognized.... several questions are being answered by Antutu CPU Master.
1512 IS USED by default!
1620Mhz and 1728 Mhz are there to choose and of course finally the 1836Mhz.
Scaling is interactive by default (changed to my fav ondemand)
I/O Scheduler is cfq by default (changed to my fav noop)
Antutu Score @ 1836Mhz: 16077Mhz ???
Lower than without OC? Needs retesting (14230 point when setting max to 1836Mhz and Min to 1512Mhz(!!!???)...maybe the benchmark is wrong...Will give it some time to see if I myself feel a speedup.
After Restart Antutu Score ends up @ 19761 points...not bad. but clearyl not enough looking at the massice OC done. REBOOT! Tab just rebooted! So 1836Mhz is not stable at mine! Trying 1728Mhz now instead.
18139 points....this kernel lacks some serious power if we can believe the scores of antutu. This is a V0.1 so nothing to worry too soon. You´ll make it find it´s power
Switched back to kernel from pulser_g2 (http://forum.xda-developers.com/showthread.php?t=2444452) and 19908 points without any OC! You may look into it.
But please answer the other questiones I wasn´t able to clear myself.
Greetings
Rodger
Click to expand...
Click to collapse
Sorry for my late,
I've tested Antutu with 1512MHz and 1836MHz. For my Tablet Z, I got ~20000 (1512MHz) and ~23000 (1836MHz).
My Tablet Z has fast binning CPU. Can you please tell me which binning your CPU is? Thank you!

hard to tell...did taht thing in Terminal emulator....it tells me "1".
Not fast or slow or anything...

DJ-Tumor said:
First of all THANK YOU for spending your time on this and sharing your result with us!
Just flashed the kernel! Good news...nothing is bricked
CPU Spy Plus indeed shows 1836 Mhz used! I did´t do anything for that.
You might re-think this. Using 1512Mhz instead by default and let the users choose that high speed CPU mode themselves as it may not be stable on all devices.
That 324Mhz added is a huge step...there is no step in between possible?
What about voltages. Did you modify anything? Is the voltage raised to achieve the high cpu frequency? Please post some more information about what happens here...
In fact I´m just running Antutu to see general stability on my device.
VERY BAD score. Before your kenel there were 20300 points. Now with OC only 19746.
=====================================================================
EDIT: Just recognized.... several questions are being answered by Antutu CPU Master.
1512 IS USED by default!
1620Mhz and 1728 Mhz are there to choose and of course finally the 1836Mhz.
Scaling is interactive by default (changed to my fav ondemand)
I/O Scheduler is cfq by default (changed to my fav noop)
Antutu Score @ 1836Mhz: 16077Mhz ???
Lower than without OC? Needs retesting (14230 point when setting max to 1836Mhz and Min to 1512Mhz(!!!???)...maybe the benchmark is wrong...Will give it some time to see if I myself feel a speedup.
After Restart Antutu Score ends up @ 19761 points...not bad. but clearyl not enough looking at the massice OC done. REBOOT! Tab just rebooted! So 1836Mhz is not stable at mine! Trying 1728Mhz now instead.
18139 points....this kernel lacks some serious power if we can believe the scores of antutu. This is a V0.1 so nothing to worry too soon. You´ll make it find it´s power
Switched back to kernel from pulser_g2 (http://forum.xda-developers.com/showthread.php?t=2444452) and 19908 points without any OC! You may look into it.
But please answer the other questiones I wasn´t able to clear myself.
Greetings
Rodger
Click to expand...
Click to collapse
How is the battery life?
Sent from my SGP311 using XDA Premium 4 mobile app

Destroyedbeauty said:
How is the battery life?
Sent from my SGP311 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don´t know....after the disastrous performance of the first release I of course switched back to stock.
Now there is the new version which does not cut performance in stock mode.
I´ll OC now to 1728 Mhz and see how it performs with that....battery life is not really good with stock so if you are already asking...FORGET ABOUT alternative kernels not optimized for battery.
That is why I don´t use CM oder AOKP on my Note1. I just eats the battery for breakfast....
OK OC just seemed to scale...20300 points (ca. 19300 at stock speed)...trying 1836 Mhz now.
17389 points....clear drawback....possibly because my device seems to have a bad CPU from what I´ve learned....wanted to use the 17xx Mhz anyway....oops....device just rebooted....my device just isn´t capable of the max cpu setting. :crying:
Anyway the working 1728 Mhz working is great news!
Will give it further testing...

I have two APQ8064 devices, Nexus 4 and Tablet Z. Nexus 4 is 0 (slow), it will reboot sometimes even on [email protected], the Antutu would force close and red light of death would happen if you ignore it and attempt to run again. While my Tablet Z is 2 (fast), this can run at [email protected] and got 23XXX in Antutu.
I don't have an idea which frequency can the 1 (nominal) APQ8064 clock at, but I think [email protected] will be OK. Also, keep eyes on the CPU float-point section in Antutu. At 1512Mhz, it is around 2000. At 1836MHz, it is around 2200. If this drop lower, just pull up the voltage BUT NOT TOO MUCH!!!
Sent from my SGP312 using xda app-developers app

Raising voltage is not an option to me. But anyway...which app do you use for that on tablet Z?
What App do you use for cou control?
I use No-frills. Do you change "interactive" and or "cfq"?
Numbers right after reboot and stopping some unused apps...just stock apps running...
2729 / 930 / 1112 / 1050 / 511 / 927 / 1436 / 5278 / 696 / 600
>>> 15269 points @ stock !!!
switching back to stock....

DJ-Tumor said:
Raising voltage is not an option to me. But anyway...which app do you use for that on tablet Z?
What App do you use for cou control?
I use No-frills. Do you change "interactive" and or "cfq"?
Click to expand...
Click to collapse
I would like to know this as well. Also, how do you check to see which processor you have? (0,1,2; slow, nominal, fast)
Sent from my Xperia Tablet Z

Spartoi said:
I would like to know this as well. Also, how do check to see which processor you have? (0,1,2; slow, nominal, fast)
Sent from my Xperia Tablet Z
Click to expand...
Click to collapse
What is the terminal command to find out? I also considered custom retelling to add some processing oomph. On a per app basis, but reading this... Stock SGP311 on 4.2.2 is chugging fine just north of 20000 points on Antutu. Can we compare Versions? Mine is 3.3.1. I faintly recall reading they mixed up some benchmarking internals because some corporations found loopholes to cheat / inflate scores on new to market devices, maybe that's the discrepancy there?
Another wild thought, could there maybe be, aside from different CPU Models, different kinds of cache / memory scattered through the devices? Would not be the first time a sub par. Cache/Memory bottleneck severely strangled a nominally and factually quicker CPU into much lower overall results. Much depends on weighting within Antutu

Man, what happened with your kernel? We need some stock kernels for 4.3
Sent from my SGP312 using XDA Premium 4 mobile app