yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Yup. Granted this isn't with much usage at all, but I streamed Pandora, then saw a movie, and this is how it was afterwards. Came from a full charge.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Damn you just killed my Screenshot lol

Ps just had my first sod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Thats what im talkin bout Ryan!

Xoned out on BMS baby.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
What are these settings? I just did a clean flash of the latest nightly. Are you using the 3.4 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] antharr:
I am quite impressed with this kernel. Again, this isn't with much use but still awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
is that with the EASTER 3.4 or the TESTERS1 3.4 ?

thks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] antharr:
This is the latest 3.0 version downloaded from the link in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
ah ok thks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Don't worry guys, the new update will blow everyone's mind!

---------- Post added at 01:29 AM ---------- Previous post was at 01:27 AM ----------

Wait till the next built, everyone will get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Gid if u ever need any other testers im decently qualified haha ;) and i like the bleeding edge. If its not broken its no fun;)

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Pm me your email, I'll add you to the list.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.4.y Build 2013-04-07 - http://www.droidhype.com/kernel/34/

- Merged latest CM upstream, lots of it

- Removed asswax and smartass2

- Some voltage tweaks

- Removed dynamic fsync

- Removed a few Makefile optimizations

- Tuned conservative and dancedance gov for performance

- Tuned interactive gov for battery saving, thx rmead01

- Removed lower CPU steppings

- L2 transition adjustments

- Vmin lowered slightly

- Removed GPU overclock, back to stock 400
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Thanks Gid. Been using your kernel for a while now - it's awesome. With the tweaks you've been making, what would you recommend for a good balance between battery and performance? I've been using interactive/row.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Stay right there with that combo, it'll get better with this release.

Your username and avatar combination are quite amusing ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Just switched from underwear and my 3d performance dropped dramatically. Like quadrant shows 15fps during the corridor. Are you guys getting this? Tried wheatly and dancedance. Also very noticeable in beach buggy blitz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
not at all... im doing just fine on the latest release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
You on aokp? 17 fps on dna, 30 or so during corridor sequence.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Do you plan on building a 3.0 version with these changes? I know this is not your priority obviously but I went back to CM10 March 17th nightly because I got a few little hiccups on the 3.4 ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
can anyone on 3.4 version try using the adb function on there computers with the phone plugged in to see if it mounts

try adb remount and see what u get.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I was having problems on the 3/31 version with adb saying device not connected. Haven't tried the new nightly yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I've never used adb so I'm no help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
For adb connection problems, refer to this CM post on their G+.

https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.0 doesn't need these changes, it's working as it supposed to. These changes are meant for 3.4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I guess most of these changes are use configurable.

The gov. tunables are always adjustable, but why the removal of the smaller steppings though? Did they prove to be unstable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Yup, it may return in the future.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Hey, the kernel so far is proving excellent. Is there a way for me to oc the gpu myself though? Like i mentioned before, i am noticing 2d and 3d graphics took a major hit on this lady release for me. Didn't do it on earlier releases or underwear. Just want to see if it makes a diff. Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Quadrant running as expected here. Wheatley at 1512/1512.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Really weird. I just did a full system wipe and internal storage wipe. Installed aokp, then this kernel. My scores are with wheatly and zen 1836 and 486. I'll mess around some.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Wouldn't let me edit post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Well, I've reverted to underwear and solved the issue. Definitely prefer your kernel but it hates me for some reason this release. I'll check back next release unless there is something i can do to figure out out. Let me know if you think of anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Any chance of a vibration intensity user adjustment? This things knocking my socks off so far Gideon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
I'm curious to know if this problem is only for me or if others are experiencing it, too. I've tested to make sure that I'm almost certain it is kernel related, and not ROM related.

My problem is that I think the FauxSound plugin(?) is causing audio glitches. The glitch that I experience is a very audible "click" at an indeterminate amount of time: it might be after 5 seconds, 20 seconds, or even 3 minutes. It happens randomly, but it's extremely loud. It's as loud as though somebody were to flick your earbud extremely hard; it's equally as discomforting, too.

I tested this with 3 JB 4.2 ROMs (Task650 AOKP, ParanoidKANGdroid, stock Rogers JB 4.2) and 3.0 kernels. For each non-stock kernel (BMS, Task), I tried testing 2 with FauxSound and 2 without FauxSound (these kernels were older); I only had the chance to test 1 stock Samsung kernel.

During testing, the audio glitch would only happen with kernels that had the FauxSound plugin. It never happened with kernels that didn't have the FauxSound plugin, or the stock Samsung kernel. I also found that with kernel 3.0 the audio glitch was a softer click than the one in the 3.4 kernels with FauxSound (using EASTER and latest 3.4).

Is this something others have experienced before? Is there a way to disable the FauxSound plugin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I've never experienced this issue with any kernel, faux or not. Sorry :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Same as what Mead said, never had the popping issue. I'm currently using the faux sound app myself with great success.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
Try to increase your voltages. I used to have this problem and it was made worse by enabling an equalizer, like DSP manager. I had to increase my minimum voltage to 950mv to get it to stop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Anyone here using SetCPU and if so are "profiles" working for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Alright I'll give this a try.

Originally here are my lower CPU voltages:

384MHz - 900mV

432MHz - 925mV

484MHz - 925mV

and everyting else was 950mV or higher.

I've changed 3 three voltages to 950. Thanks. I don't use the DSP Manager at all, though. We'll see how it goes from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I was running my lowest voltages at 975 for stability reason. if 950 doesn't work give that a shot.

---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------

They used to work when i used that app, but It turned out that that app was only applying your governor changes to 1 core and both of them. Download kernel tweaker (i think?) from the play store.

You can set up profiles but you have to use Tasker to have them change under variables. Worked very well though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illmatic24:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

mmm smoothass I like the sound of that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Any chance of allowing 192MHz for a bottom step?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Death&co:
Loving this kernel paired up with Liquid Smooooth. Having pretty outstanding battery life :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Having amazing battery life today, think I found some good setting figured id share since they work so well for me

Interactive/row

Interactive tweaks:

hispeed freq: 918000

min sample time: 50000

timer rate: 40000

Max freq capped to 1350

Also 100% lag free. Very impressed with this kernel also I can't live without the colors anymore lol I tried lk yesterday and it looked all nasty yellow :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Same here. The yellow stands out badly now that I'm used to this... The kernel is also worth keeping anyway since it's so darn good! Just wish he'd give us 192.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

+1 192 would be icing on the cake
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

That hispeed_freq at 918 will be good for battery.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

I'll add 192 in the next release.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PMDColeslaw:
Where do you set the interactive tweaks? can it be done using the built in performance settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Either echo it via terminal emulator or use an app like trickstermod. The built in performance rom settings feature doesn't have this option if I remember correctly.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

There are a few apps in the play store: Setcpu, trickster mod, system tuner are some of the more popular ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
wwaaaawhoooo! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

this kernel is the only one besides kt's which I can use an app like trickster mod to get my frequencies to stay still and not revert..very nice so far..I'm liking row and interactive..

thanks for your work gideonx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Could you give me an idea about the other interactive parameters? I could only find information about a few in the threads on XDA.

Namely these: target loads, above hispeed delay, timer slack, boost

What does the governor use to determine when to go above hispeed freq? I noticed some but not much time spent at max freq.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Hrmmmmm

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
why Hmmmmm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

looks as though the min clock speed in the pic is 192mhz

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illmatic24:
Clearly he said "Hrmmmmm" and not "Hmmmmm". geez
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thehavock18:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

I LOLed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illmatic24:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-02-20]

Edit: woops wrong thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Thanks not sure why but doesn't seem like profiles are working. My first time trying profiles so was just curious

EDIT: Scratch all that. Its working. And as usual it was my fault. Missed one little check box. Thanks though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Depending how you are using them it's hard to tell. I only ever used screen off profiles. So I couldn't really tell what govnr was running when the screen was off.

Using the other app in tasker I knew what was going on. I would set the task to run and put up a notification when it was complete. I'd let my phone sit for 30 seconds (I had a few seconds delay because I didn't want things changing so quickly if I was a accidental screen on/off) and when i checked the notification would be there meaning the code had executed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Got the new update. So far running good and its much smoother now! Haven't had any hiccups since this morning. :fingers-crossed:

As always, big thanks to the team and off course Gid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Bms and deviant xone. Not a single freeze sod or reboot today.

Xoned out on BMS baby.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Still have 43% battery left. Interactive/row. 384-1566.

Xoned out on BMS baby.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
Is there a reason you don't go down to 192?

Sent from my AT&T Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Hope that might shed light on your question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
What polobunny said, but even if the steps were there my battery life suffers when going below 384 mhz. When the phone is asleep it's quicker to finish tasks at 384 than at 192 mhz. hence why MY battery life suffers. Could be different for others. I'm now testing my theory on UV. I noticed heavy UV causes more drain as well but need another couple of days to test before I come to that conclusion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's something I've learned on the Nexus S. UV doesn't save battery very much and even can make you drain faster.

Two big things come into play, and a smaller one:

1) Race to idle

The faster the task is processed, the faster your phone returns to idle/deep sleep. Deep sleep is the state you want your phone to spend the most time in when you're not touching it. You'll get the best savings if you can eliminate most wakelocks that stop your phone from going to deep sleep.

2) Error correction

Too high UV will make your phone unstable. This doesn't necessarily manifest instantly, or ever at all, but it will affect your phone. All time spent with an unstable CPU is either corrupting your data or making error correction work hard. This is also valid for unstable overclock, RAM that corrupts data, error writing to flash storage and so on.

3) Most efficient state

There's always a sweetpoint where your phone CPU is the most efficient, where frequency is high enough tasks will proceed relatively quickly but voltage necessary for that state isn't too high. This frequency is usually not the highest, nor the lowest, but rather one in the middle or one near the lowest. This differs from phone to phone, architecture and type of processing needing to be done (different type of calculations need different type of work and some architectures are more efficient at it). It's a smaller gain compared to the others, but it's not negligible if you're able to find it.

Now it gets confusing when you add in governor and their tunables, different IO schedulers and different kernel branches, but that's part of the fun. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
can't wait for the next build. So far things are great on the latest nightly for cm10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Are you having issues using kernel tuner setting voltages?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Yep... Does not set voltages

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Talking to dev right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
The dev of the app or kernel?

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
For the app, in which he said it should be fixed in the next release!:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
The Easter build of 3.0.y is boss, dudes. I get less than 0.5% per hour idle drain, which is like a 50% improvement over stock AOSP kernel.

Good job, dev, and thanks!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Any mods or tweaks over the BMS kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Just wanted to say that my issue with the audio "clicks" has been partially resolved by upping the voltage.

I upped all my minimum voltages to 950mV. Now, rather than very loud hard "clicks" they are replaced by silent "hisses". I don't mind this much, as it won't cause damage to my ears or my monitors and headphones. I'm still on the hunt for a solution that gets rid of this audio glitch entirely, but at least now I won't go deaf from this loud "click".

Thanks again to whomever suggested this solution!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Next release is actually going to raise it to 975 min. I think that's been the sweet spot for stability and undervolting according to the testers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewzta:
Installed the latest 3.4 on Rootbox, receiving System UI crashes on bootup.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Try this one - http://goo.gl/9IW0h
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
That system ui crash isn't due to the kernel. It's rom related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewzta:
GideonX - Thanks tried the new one, still got them on bootup. Lock screen wallpaper loads but not the homescreen one.

stevehkim - Haven't had issues until I flashed this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] House M.D.:
try to fix the permissions. otherwise, restore your backup that you did before flashing this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Or if you didn't do a backup, reflash the rom on top without wiping anything. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Are you coming from another kernel? Any left over scripts possibly causing problems?

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
Its the rom. I just switched from Rootbox because of those crashes. System ui is the one I got as well. I had 3 different kernels. Each time the problem was fixed for like a few hours then it came back. My friend had same issue in stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Like I said its the rom. Hows the kernel gonna give aystem ui crashes?

ATT SGS3 dipped in Smooth Liquid. Asswaxed by BMS.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deviatorz:
There are a few apps that FC on itself like doubletwist Alarm and Play. I reinstalled doubletwist and it seemed to work but after a while when I go to change settings it would FC again. Should I try a different kernel? From what I'm reading I should install the BMS 3.0 kernel and not the 3.4 version? I am using the stable release right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
That depends on your rom whether or not to use 3.0 or 3.4.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You're using CM10.1? Update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deviatorz:
I am using JB 2.1 Official right now. I see that it has 3.4.38 leankernel on it but a few posts back said that was kind of experimental and I should use a 3.0 kernel if I want to change?

I'm not sure if this post is directed at me. No I am not on CM10.1.

Edit: Another question I had is: is there a way to save all the settings from the customizations I've made from a custom ROM? For example, if I tweeked the lockscreen or pie controls, or Quicksettings, is there a way to save these? What I usually do when I upgrade ROMs is titanium backup all my user apps and their respective data and restore them. I never save system apps and settings as I heard reinstalling them in an updated ROM causes problems. Do you guys just re-customize everytime?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Decided to release a day early, enjoy :)

3.4.y Build 2013-04-13 - http://www.droidhype.com/kernel/34/

- Merged latest CM updates as of today

- Updated to latest (and last) version of Linaro 4.7 toolchain (next build should be on 4.8)

- Added some more -O3 optimizations

- Re-added 192Mhz slot

- Tweaked interactive for better performance and battery. Try the default settings and drop your hispeed_freq to around 810 or so. Insane.

- Raised vmin to 975

- Implement quick calibration (Credit BMc08GT)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lessthanzach:
Sweet, I'll check back in a bit. Site isn't showing it yet. Hopefully this build fixes my 3d performance.

Edit : spoke too soon. Site is updated now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Man o man you guys are in for a treat on this build. It is freakin awesome!

ATT SGS3 dipped in Smooth Liquid. Asswaxed by BMS.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
Trying 810/192 interactive/row, running smooth for now :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Try 192/1512, but limit hispeed_freq to 810. Nice balance of power when you need it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
How do i limit hispeed?

---------- Post added at 12:31 AM ---------- Previous post was at 12:24 AM ----------

Its set ay 1134000 right now in setcpu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Try lowering that to 810 and see how it feels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
It reverts back to defaut after reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Try using trickster mod from playstore. Its free and much easier to use. And the ui is a plus.

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Hrm, not sure. May be set by your rom on boot via script or setcpu not setting it on boot. I used trickstermod, it sets on boot for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
In tricksters Instead of 1134000 i put 810000 or 810?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
810000
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
Nm loll its in the dropdown choices and its 810000 :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Thanks GideonX, just flashed the newest build. Will update about the battery stats by tomo. :beer: