With the dawn of the ICS ROMs behind us and now that we have all settled in a bit, I am interested in some of your parameters for overclocking and undervolting. I am mainly wanting these to put in my Battery Guide as some examples bc when I created the guide, the ICS ROMs were fledgling at best.
Mattymat brought this up in the Passion thread and the more I thought about it, the more some people are probably going to be wanting these. Plus I have already seen some people talk about random reboots and freezes and others asking about overclocking as well.
ICS runs well on its own at stock frequencies but there are those out there that want to push it a bit further. I could care less about Quadrant scores or benchmarks or YOUR battery life (especially with all the different batteries out there now).
What I want is voltages/frequencies with stability. Obviously every Vibrant is different. Also please list what ROM/kernel you are on as well.
Thanks to all
I use -50 across the range, normally i use frequencies set 200-1000 notice minimal lag, the improvement in user experience i get is minimal when I crank it further. Governor set to Conservative and Scheduler to SIO.
Currently i am using MP's latest subzero kernel found in the ICZen thread. Though i would also like to mention that this setting has worked on almost every ICS rom/kernel combo.
- Cheers
Overclocking (stable for my device) w/ Icy Glitch: 200mhz-1400mhz, 1400mhz step (1500mV), and 1200mhz step (1400mV), GlitchassV2.
It's stable, for me at least, and battery life isn't bad at all (8-9 hours).
Undervolting (stable for my device) w/ Icy Glitch: 100mhz - 1000mhz (-25mV w/ each step), GlitchassV2.
Definitely better battery life with this one (12-13 hours).
I notice that the lower frequencies (100mhz & 200mhz) have the same voltage (950mV), and when one gets undervolted and one doesn't (i.e 100mhz: 925mV; 200mhz: 950mV), videos get really choppy and unbearable to watch.
Sent from my SGH-T959 using XDA
Rom: ICS Passion v13
Kernel: Kiss v2.2 (Yum yum good #2)
Governer: SmartassV2
I am running -0mV on the two upper frequencies (they seem more sensitive to under volting) and -50mV across all other frequencies used. No problems encountered.
1200MHz : 1350mV
1000MHz : 1275mV
800MHz : 1150mV
400Mhz : 1000mV
200MHz : 900mV
100KHz : 900mV (not used but I lowered the voltage anyway)
Edit: upper frequencies do not like undervolting - experienced stutter on Angry Birds even at -25mV
Bump....I am going to be reworking the battery guide tonight or tomorrow and could use some more of theses, please
Related
So, I was wondering which would be the better to run on an OC kernal, SetCpu or Voltage Control. I'm using SetCpu (cause I paid for it lol) but notice that a lot of people talk about using Voltage Control instead of the later. Is this due to options, or is it simply because it's free? Any help is appreciated, and anybody that gives me a non-flaming serious response will get a thanks lol!
Running:
Trigger v2.7.2
Tigersblood v2 OC Kernal
(all statistics may change without notice lol!)
TXLunchbox said:
So, I was wondering which would be the better to run on an OC kernal, SetCpu or Voltage Control. I'm using SetCpu (cause I paid for it lol) but notice that a lot of people talk about using Voltage Control instead of the later. Is this due to options, or is it simply because it's free? Any help is appreciated, and anybody that gives me a non-flaming serious response will get a thanks lol!
Running:
Trigger v2.7.2
Tigersblood v2 OC Kernal
(all statistics may change without notice lol!)
Click to expand...
Click to collapse
I just installed Voltage Control 1 hour ago. So far I like it better than SetCpu which I also paid for it. Voltage Control has options to lower the votage in various steps. The voltages can be lowered without needing to overclock the CPU.
Installed it after installing Tigers Blood V2 kernel. But now I want to see how my battery life is undervolted and not overclocked.
I prefer voltage control but I also have the paid set cpu from before when I didn't know about voltage. Voltage let's you uv (undervolt) your frequencies to conserve some battery life.
Trigger + Tigerblood = Winning
Well it just depends on what your trying to do, in example, if you want to set profiles and Oc, I would use Setcpu, if your trying to undervolt your clock speed, and have Oc, I would use Voltage Control. I use both because I'm trying to Overclock, and have lower voltages
Wow guys! Thanks so much! This is really helpful info.
Bambam, what settings are you using with Tigers blood and Trigger?
Sent from my SGH-T959 using XDA Premium App
TXLunchbox said:
Wow guys! Thanks so much! This is really helpful info.
Bambam, what settings are you using with Tigers blood and Trigger?
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
My settings, this might not work for your phone, every phone is different. Battery life seems great so far.
100mhz -50 = 900mv
200mhz -50 = 900mv
400mhz -50 = 1000mv
800mhz -50 = 1150mv
1000mhz -50 = 1225mv
1200mhz -25 = 1275mv
Good luck.
I personally use SetCpu for OC because i've been using it since the Nexus One and i think its just the better app b/c of ease of use
Again guys (or gals), I really appreciate all the feedback. Thanks have been given appropriately as promised. Sorry about the delay. This has been the first day that I could get to my laptop lol!
One thing I have noticed is that when SetCpu is set to "performance" the phone has difficulty pulling up the multi-tasker when long pressing the home button. This is how I get to Task Manager to clear things up before running benchmarks, so it's somewhat of a big deal to me. I'm sure there are other ways around it. I know on the stock OS that there is a Task Manager widget, but that has seemed to have disappeared with the ROMs that I've ran.
GTOJim said:
My settings, this might not work for your phone, every phone is different. Battery life seems great so far.
100mhz -50 = 900mv
200mhz -50 = 900mv
400mhz -50 = 1000mv
800mhz -50 = 1150mv
1000mhz -50 = 1225mv
1200mhz -25 = 1275mv
Good luck.
Click to expand...
Click to collapse
Thanks for the info Jim, I'm really trying out different UV settings. I'm running just the standard right now cause other settings I've tried have caused me the SOD lol!
I don't know if this applies anymore but TW used to suggest the following setting when using SetCPU.
Conservative, do not set on boot-up. Minimum clock speed of 200mhz. Some phones would not wake up using the default of 100mz minimum. As I remember they advised against setting up any profiles.
Yeah, I've known about the no profiles thing. I think I've stuck to using Voltage Control as I haven't had nearly as much issues with it.
Hi everyone,
Like most people I've been trying to find that optimum balance between performance and battery life in my Aria. I'm running CM7.0.3 and the latest version of drowningchild's kernel. With that kernel I switched setCPU from ondemand to smartass, and I can already see the CPU spending most of it's time in either 400 or 480 MHz, but when playing a graphic intensive game it'll go up to 806 MHz and run great.
But, here's the problem. With things like less graphic intensive games, or playing videos, smartass doesn't want to scale up to a useful clock speed, and things get choppy. I switch back to ondemand and everything smoothes out again. I don't want to keep it in ondemand all the time though, because then it's spending half the time in 806 MHz and eating up battery unnecessarily.
So, is there a better governor option for me? Or maybe a way to "whitelist" apps within setCPU, to designate apps that always get the max clock speed?
tl;dr: smartass isn't that smart in certain situations. Is there a better way?
Check out the app "Tasker" in the market. It will allow you to reconfig the governors automatically based on a slew of complex conditions.
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
drowningchild said:
If you want smartass roll back to 7-5 of my kernel and it should be fixed as I tweaked it to jump around less in newer versions
I'm still messing around with the new kernel released & will add smartass very soon & hopefully optimized
Click to expand...
Click to collapse
Hey yea you're right, I didn't notice you had a new kernel out. I'm running 7-5 still but I'll upgrade once smartass is working in the new version.
I've been using "conservative" setting. Although when it initial opens a resource intensive app, its stutters a little, and then compensates by clocking up. I haven't had an issue where a game didnt want to run smooth (also at 806mhz).
I run on demand at 320/768. This to me seems to be a very good combo. The 320 min makes a noticeable difference in responsiveness without much sacrifice to battery. I've found the Max cpu setting doesn't make too much of a difference in most situations.
Sent from my cm7 Aria.
I have made a lot of searches and read a lot about battery calibration... and of course i know what the hell is kernel panic, its definition and its symptoms.
However I still have some confusions and I hope some of you may be able to solve them
Maybe some of them are noobie questions but I honestly sorry for that also this may help others who has these confusions too
My situation:
The system stats are shown in my signature.
on 5/9 I have flashed franco.Kernel v19.4 bfs and then started a lot of OC tests,
finally I was stable on stress test (SetCPU) 729mhz for 2 hours non-stop,
and also I used the phone stably for over 24 hours without reboot.
However I faced a problem which is related to Darktremor scripts.
I used 2 weeks to solve it and finally it is gone now.
I started battery calibration which is the final process before I use my phone normally in my daily lives.
But in these two days, my kernel panics after ~4 hours of usage of 729mhz max CPU frequency.
without the need of advice, surely i have downclocked to 710mhz max and its all good. but however i am super curious about why 729 becomes from stable to unstable before and after.
1) Does battery stats related to kernel panics in ANY extent? if yes, how?
Ignore all questions under 1 if the answer is No.
1.1) Does wiping battery stats before flashing a kernel helps you OC higher?
1.2) Does wiping battery stats before flashing a ROM helps you OC higher?
1.3) Does wiping battery stats (for calibration purposes) has possibilities to produce kernel panics?
2) Why is there a sudden drop of battery level (~4-5%) after kernel panics?
3) Is there any other possible causes of kernel panics BESIDES overclocking too high?
3.1) *2sd scripts?
3.2) ext4 barrier = 0?
3.3) inputting EXT4 data writeback?
(tune2fs -o journal_data_writeback /dev/block/mmcblk0p2)
4) Is SetCPU the problem?
Some says "dont use SetCPU when you can overclock using CM7 settings."
Is that true?
5) BESIDES the max speed, does it also depends on Governors?
Ignore powersave governor or others which forces the clock to the minimum frequencies.
So, is there any difference between setting the same maximum speed, different governors?
(for example) Would smartass gives a panic at 729mhz but ondemand doesnt?
6) Does the "change of frequencies" gives easier kernel panics?
Situation A: 729min, 729 max
Situation B: 480min, 729max
In situation B, the system makes the frequencies change due to load, means it may switch from 480 -> 600 -> 729 -> 710 -> 691 -> 480 etc.
so does this "change of frequencies" makes the kernel loads more and finally gets it to panic?
Thanks for your time reading and answering my questions!
Please just quote one of them if you would just like to answer one of the above
Thank you very much!
1) no.
2) It happens when u remove the battery and put it back.
3) There are some strange reports of kernel panic at 600Mhz which are weird. Sometimes Roms/kernel play a part(unknown).
4) it is because you can overclock in Cm7 settings menu, so no need to install another app such as SetCpu
5) Maybe, a governor who stays more on the highest frequencies i think are easy to panic because hardware can't handle it.
6) for me, i would say situation A would be easier to kernel panic, as it is constantly on the highest frequency and stressing your cpu too much that it can't handle it.
Since you get stable at 729mhz for 2h and panicked when 4h of use, that means the cpu can't handle 729mhz for above 4h.
@terratrix
thanks for your reply!! at least im not using my stupidity to wipe battery stats and trying to avoid kernel panics, lol.
@info update and conclusion after 1 more day of testing
And there, after some readings on the forum and the experiences myself, i think i have found the critical point already - QUESTION NO.5
Conclusion : kernel panics are related to governors, at least, our new amazing profiled one - SmartassV2!!
On the thread of Franco's .35 v1 kernel, there are some users reporting the panic issues faced with ONLY SmartassV2.
And me myself, has joined the party as well
Smartass(v1) has been my best bud all the time at 729mhz or even higher for more than 6 months. And when I left it and went to choose his next generation, my phone got a generation gap with Mr.V2, lol.
On my phone: (Franco.kernel 19.4bfs and no any reflash or stuffs between testings)
SmartassV2 ---
very unstable panics AND random shutdowns at random times
729mhz - sometimes 2 hours, sometimes 4 hours
710mhz - yeah I justnow kernel paniced with this also, you know how long after boot? 30minutes!!!
Why 30minutes? I suspect that it.is related to franco's network speed hack. I'm on EDGE data plan and because of Franco, I can enable HSDPA with 4x more speed.
On 710mhz, my phone was stable for over 8 hours with EDGE on (I intended to save battery), but after a reboot (manual one for some other purposes) I started to use (the hacked) HSDPA. After 30 minutes, panic. I remembered when I was at 729 on smartassv2 I panicked after 3 hours and at that time I was using HSDPA too.
Smartass (v1) ---
Well now I'm on smartass v1 at 729mhz stably typing this message. Funny huh...?
Results:
Franco's network speed hack
OR
3G network/HSDPA network
OR
Even just because of specific phone hardwares
IS NOT COMPATIBLE WITH THE ALMIGHTY SMARTASS-V2 GOVERNOR AND WOULD RESULT IN KERNEL PANICS AT THE FREQUENCIES WHERE THE PHONE CAN BE STABLE WITH OTHER COMMON GOVERNORS.
If I am wrong or you can confirm this by testing yourself, please let me know!!! thanks and hope I have provided some useful information
Goodnight and I'm going to continue working with my old friend smartass-v1 despite v2 has better profiling tweaks, lol
Sent from my LG-P500 using XDA Premium App
Dude, as i had mentioned earlier in franco's thread, that it had to do with the governors... cause i usually try and find out the cause of the issue myself before posting a bug..
SO all i tried were playing around with the performance settings... and i start off with changing the governors... the best targeted experimental ones are MINMAX (my personal fav), SMARTASS, SMOOTHASS (now removed but one AWESOME governor), and INTERACTIVE-X (rewritten by franco i guess).... About the frequencies... from what i have observed so far apart from reading stuffs is that, at 729 Mhz our optimus DOES pretty much stay stable even in the ****TIEST devices.. LOL i can say that cause we indians get the crappiest hardware of all... the point is... if you got a kernel panic at 729, it is most likely that you would get it again at 600 Mhz too cause its not overclock related..!!!
Bottom-line: Avoid SmartassV2 unless your phone is made of the finest hardware i.e. you can easily overclock it to 806 Mhz (ive seen some users using it at this frequency without any issues at all .. :O ) Use Smartass older or Minmax instead...!! And avoid overclocking above 729..!!!
P.s.: mine works fine even at 768 BTW....
We have to wait for Franco's next release for more smartass2 updates
Sent from my LG-P500
SmartassV2 is kind of strange, at least in my phone. I notice my battery draining faster while I use it, and it's probably because it stays in the max frequency longer for some reason, despite screen off. I use NoFrills for my CPU setting and it has the ability to view stats, and when I'm using V2 it stays longer at the max than at the min (65 vs 35%). The opposite is true for Smartass v1, which to me makes more sense because my phone stays at standby more often than being used.
As comparison data, my phone with smartass v1 can typically be OCed up to 787 MHz. 748 MHz on v2 is stable, but I haven't extensively tested higher freqs.
I have a Indian phone , smartass v2 oc to 768 stable xD
Sent from my LG-P500
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
loockzye said:
Hello there, I'm here to ask how some people overclock their xperia x10 so high example to 1190 mhz, my one is instantly booting when i switch to that frequency, how do they do it ? Im on jb rom by scritch 007 and jb ferakernel . Any advices ?
Click to expand...
Click to collapse
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Dr Goodvibes said:
To start with, no two XPERIA X10i are the same when it comes to the silicon in them.
The odd one or two may be able to sustain 1128MHz for benchmarking, but highly unlikely to be able to sustain that frequency for an extended time with a 'standard' load of user installed apps.
The XPERIA X10i is spec'd to be run stable and conservatively at 998MHz and there was no consideration for any frequency changes above that when designed.
However that does not stop most of us attempting to find the limits.
I tend to favour 1113MHz for my max daily frequency using SmartAssv2 governor, others may select something different.
I use SetCPU to change CPU frequencies, others prefer AnTuTu cpu master or some other overclocking application.
I use Link2SD on a secondary partition with a 32GB SanDisk UHS-I SDcard which gets away from the slow read/write of internal data storage.
build.prop 'tweaking' for optimisation goes a long way too.
The smart money is not overclocking, but on how low you can maintain the CPU (and thus battery life) when the screen is off and still be able to come out of deep sleep without 'hanging' the phone.
I have a screen-off CPU profile clocked at 576MHz-192MHz using SmartAssv2 to do that (work in progress).
Limiting applications that wake your phone when the screen is off it also a bonus.
CPU Governors and I/O scheduler information is a good start to understand what the CPU is attempting to do with different settings.
I have installed and run scritch007 CM10 JB ROM v5.0 (think it was at the time) with Amin Kernel and I seem to remember 1190Mhz was the raged edge of stability with AnTuTu v3 on my phone, so it doesn't surprise me a phone may not be able to clock at that speed using a CM10 JB ROM. See my AnTuTu v3 benchmark below used SmartAssV2 and noop I/O scheduler.
One should consider with the JB ROMs, the phone is doing a lot more (albeit a lot smarter) with the same amount of HW resources and even if you set the clock at 1190MHz and benchmark it, even before installing your own apps, there is still a lot of processes all completing for resources.
To get a better idea of the abilities of your phone, you may want to installed generic GB 2.3.3 and root it with an Overclocked Kernel to see if high clock rates of 1190MHz+ can be maintained without crashing the phone (WLOD - White light of death).
I can set 1128MHz on my phone without crashing it, but it always crashes on AnTuTu benchmark test at that frequency which is only about bragging rights at the end of the day anyway. I can't do anything constructive at these clock rates.
Installing JB ROMs and Kernels under rapid development with their own quirks on an X10i is probably not the most ideal why to gauge the stability of your phone when overclocked.
At the end of the day, it's more likely just luck of the draw if an XPERIA X10i can maintain 1190MHz+ clock frequencies and I'd say that 1190MHz+ is the exception and not the rule.
Click to expand...
Click to collapse
Thanks for your answer.
Hi there to all!!! I've been flashing various Android Roms for a few yrs now & really enjoy trying out new custom roms etc... Now i have a weird problem, Most customs Roms I have tried for my S3 i9300 are great & most 4.3 Roms come with a Custom Kernel such as Beoffla, GoogyMax, devil kernel & so on.... Now the problem is when leaving the CPU at defualt governer & settings everything is fine eg: min 200 & max 1400 but games lag now & again, When setting the CPU min & Max settings to 1400MHz, the results are much better but not for long, The CPU always drops to 800MHz when gaming as i notice the lagg, I've noticed this same thing with just about every kernel & rom ive tried wether its set to 1400 or even overclocked to 1500 or 1600max, I've also tried every trick to make them settings stick , like trickster mod etc, none seem to work for long, its like another system service is interfering with the settings or so.....im pulling my hair out to figure out what this is, I just want the CPU min & max to stay firmly at 1400Mhz or 1500 etc....without changing at all!!!
Any help or suggestions would be really appreciated.... FlashJunkie83
Sent from my NeatRom'ed Galaxy S3
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
~ RazorMC
RazorMC said:
CPU/GPU can under-perform if they get too hot from playing resource-intensive games or apps. Maybe this is the issue.
hey yea would make sense but when running rooted stock 4.1.2 with stock kernel, this doesnt happen at all, i can set performance governer in set cpu & it stays at 1400 Mhz throughout, also i would of thought a Cpu thats ment to run at 1400 would be fine to do so all the time as its ment to be able to... even with a little heat behind it... its still only doing what its ment to lol, i remember in the days of my s2, i could push the cpu to 1200mhz & it would happily stay there even tho it got hot lol, im really sure its a system thing that upsets the cpu frequency, other than that there must be a way to stop the cpu/gpu from under-performing with a little heat..... thanks for reply tho dude....
Sent from my NeatRom'ed S3 i-9300
Click to expand...
Click to collapse
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
RazorMC said:
@FlashJunkie83
- High temp will always cause freq throttling since this is how devices are designed. This over-rides whatever the max freq the cpu was designed to run on.
- try undervolting from the boefla config app (if you use the boefla kernel). I use -25mV with almost no difference to performance. Some users have gone on to -50mV but that gave me random freezes and massive lags sometimes.
- Test different governors. I mostly use the default pegasusq and it works well enough. Constantly high freq can affect the CPU in the long-term. So I use max freq of 800mhz and increase it to 1400mhz only when I play games.
- I'm not a fan of SetCPU. It's a great app but i find specific apps (like boeffla config) for kernels to be more precise.
- You can also try a different battery and borrow one from a friend to test it out. I had slight heating issues long ago and changing the battery reduced the heat for me somehow. It was not much, but it was enough for me to notice.
~ RazorMC
Click to expand...
Click to collapse
thanks mate will give it a go
sent from my NeatRom'ed S3 i9300
finally fiqured it out, it seems that cynogenmod has a diffrent approach to thermal throttling as ive flashed CM10.2.0 Android 4.3.1 along with Boeffla 2.1 for CM & the issue seems to have gone completely, have been running a performance test on games for best part of the day at 1600MHz with 4 enabled cores & just going back to normal settings for normal daily use, & not 1 issue with throttling, so now im very happy with the smoothness in games although its gets warm, but most high performance CPU's do anyways,So ive come to the conclusion that thermal throttling must be handled more by sammy roms it seems, but got the result i wanted in the end, thanks for all replies tho guys
Sent from my blazing S3 i9300 now running CM10.2.0