yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
So I've been experiencing a deal where KTweaker sets the clock speeds, governor, and scheduler 10 after boot like I want it to. However, after the phone goes to sleep and wake it the max MHz is set to stock. While the min is left the way I set it and governor too. I don't have anything else to control the CPU other than ROM control which I don't use. The way around it I found that will keep it at the max MHz is to set the permissions of the sys/devices/system/CPU/cpu0/cpufreq/scaling_max_freq -> rw-r-r. The weird thing is that its only the max is affected nothing else

LOGCAT

In order to make the log cat as small as possible I rebooted wait for ktweaker to set ran a quick stability test, put to sleep, woke, and ran again to confirm stock MHz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Also consider the longer computation times will mean you're staring at the screen being turned on for longer. Screen on time is what really destroys batteries!

Glad to see you're using cool tools!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
How's about sharing the most important piece of info??? Scheduler....governor???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
Cool tools is sweet! Thanks for the tip:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
Agree... Cool Tools is great :)

I believe my evaluation has been very fair, same setting, same amount of apps, same kernel.

Only thing unfair was that I was using AOKP(Jellybean) Task & Ktoonsez 9-8 on a Sunday, and I get way less emails and SMS than usual.

They are both great ROMs to use daily, I just got more battery life and less heat on the Sammy ROM...for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Perhaps Sunday is a "slow" day? There's no way a kernel can effect sms or emails :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
What he is saying is less drain on a sunday cus there is less network traffic which is a battery killer using wifi and LTE antenna. It is very noticable how wifi and LTE antenna effect battery, I get anywhere from 100-300 PM's and post notifications a day now and my idle battery has gone from one-third of a percent an hour to almost 1% an hour on heavy days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
I think you misunderstood me :) I'm not saying the kernel gives me slower emails and SMS or effecting them in anyway.

The main point is different ROM different battery life...for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
So I've run at OC 1998 max for almost two days now, and haven't had a random revert back to 1512 stock max yet. For me, seemed to only happen when set to 2106 max.

I had a lock-up on a level too one time when something went screwy in an app... mine got stuck on the 1998 level. The phone got pretty toasty!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I had my captivate in Haiti at 1.392 or something (stock 1.0) and my battery temp went all the way up to 48 C one day :0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
Lol my first captivate used to get really hot. I think the highest it was ever at was 54C once. I pulled the battery because I was afraid I would fry something.

Herp derp SGS3 Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
hahaha! 54?!?! I can't believe it survived!!

---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------

Thanks for taking the time to test different ROM's but like people have said to many variables. And keep in mind that this is the kernel thread, maybe post your results in the ROM dev thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EskimoRuler:
I didn't know about the binary update. I flashed the new 9-8 AOKP JB update over my existing 9-5. cleared cache, dalvik, fixed permissions. Rebooted twice. Went into SuperSU and it asked me to update the binarys, did that. Then flashed the kernel, cleared cache, dalvik, fixed permissions. booted up. opened SuperSU, everything looked good, then went into KTweaker, set my OC to 1.89, UC to 144. Dropped voltages by 75.

I then installed Cool Tool so I could watch to see if i'm going above 1.5 at all. its been about 20 mins and when i go back into KTweaker my settings are sticking and I see my phone hit 1.89 every now and then. So hopefully this worked

Edit: Update: My OC to 1.89 is sticking. I have even reboot twice since to make sure they got reapplied and everything is looking good so far!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] @Class:
Crackling audio

Hi,

This kernel results in crackling audio for me... Only happens with the popular Grooveshark application, but none the less it still happens when the CPU speed is < 800 Mhz, regardless of usage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
WHAT SOLVED MY RANDOM OC REVERT FROM 2106 TO 1512 MHz

I was running on cm10 for a while and never had issues with my max freq not sticking to 2106. However, I tried the latest AOKP rom (9/8) for a few day now and I have noticed that my max freq wasn't sticking at 2106. I had the min/max not matching window popping in ktweaker but the max never reverted back to 2106. So I went in ROM control under performance and I saw that it won't allow me to go over 1512Mhz. I decided to deny root access to ROM control and now my max freq never went back to 1512mhz since yesterday.

I'm using kt747 9-5b and cool tool to monitor my CPU

I hope this can help some others experiencing this issue!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Exactly this ^^^^ ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
this may be okay but does rom control need permission for other tasks at boot? denying it permission may not allow it to follow through with other tasks and options you selected in side of rom control..i was curious though. in aokp and cm..the built in cpu control even though not enabled for boot may be messing with some peoples cpu junk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
I was wondering this exact thing. Oh well. I'll just wait till it gets fixed. 1512mhz is still plenty fast for me. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
For me it didn't affect anything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
What is weird about that is that I never had kernel issues with cm10 just using the performance setting include in cm10 or with ktweaker.

I have noticed that performance setting of cm10 doesn't ask root access in superuser. Could this be causing the issue in aokp?

I'm not saying aokp isn't a great ROM but with this kernel, cm10 is more stable on my phone :( I loved the unicorn boot animation !!! Haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
At risk of being offtopic for those of us who are battery-obsessed, I stumbled across this and just finished my first day with this battery monitor. So far I'm loving it: https://play.google.com/store/apps/details?id=com.ijinshan.kbatterydoctor_en

I don't know the developer and am not otherwise on the take ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I just think they have toast messages turned off or are blocking them from appearing while doing the work. Both my app and performance settings app have to write the same place which requires root permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 9/10

1. Added "Fast Charge" (It has been recommend to only use it for DC charging and not for USB but can be used for USB but in VERY rare cases can cause damage to your USB port)

2. Brand new code to try and keep OCing locked and not revert

3. Updates to ondemand and pegasusq gov

4. Lots of CM10 commits

5. Linux patches.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I feel like a kid on Christmas everytime you post an update! Thank you ktoonsez
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
YES!! I love it whenever you post a new version of your kernel Ktoonsez I am going to flash it right now! I will post back! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
+1!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dante2512:
I see what you did under there... :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcorio:
I'm going to flash this new kernel but I think I got my oc to stick by opening superuser, updating binary, deleted root privileges to ktweaker. Opened ktweaker and granted root again. So far so good. But then again, might be fixed in this 9-10-12 update. Here goes....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks guys :D. We are now at 3,500 users of the kernel :D :good: :victory:. Thanks for all the support!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
Under where?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
your the **** Kt! !

thanks for your continued work dude
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
Amazing

Ktoonsez this new update looks very good so far, I tried changing different speeds and the device is sticking to it's speed, I tried rebooting my device and after reboot my phone is sticking to the speed I assign which I think is awesome, I pushed the phone to full OC and I did some benchmarking and the results are pretty beast! You are the man Ktoonsez :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stir fry a lot:
I'm one of those having the OC not sticking issue. I had a leaked version (v3) of the copy you just uploaded and Ktweaker would only FC on me. I am having the same FC issue (just a black screen) with this release. I've fix permissions and cleared app data but no dice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
will this JB rom work on Sammy stock latest leak? Has anyone tried and would like to share ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eLDuRo212:
Have you tried FULLY wiping your phone? That is so strange that the speeds are not sticking for you, I had a device that didn't want to take Ktoonsez kernel at all and I send my phone back to AT&T for warranty and they gave me a replacement and BOOM the new device took the kernel like a champ and also the speeds were sticking, so all phones are made differently bottom line it sucks but that is how it works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stir fry a lot:
Yeah, it wasn't sticking on Ariel either. I did a full cache, system, factory wipe before flashing my current (Wicked) rom. I'm very pleased with the kernel even @ 1.5GHz so if I have to stick with 9-5 at stock speed it's not really that big of a deal.

This seems to be working for me on 9-5 so far. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
I think this procedure is the cure for the OC revert to stock issue! So far, so good - I'm staying on version 9-5 for a day or two just to confirm. Good find!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
Just flashed the 9/10 kernel over the latest CM10 nightly and KTweaker does not appear to be playing well with the system. If I lock within KTweaker, then going into the performance tab under settings shows sometimes my OC frequency, other times 1.5GHz. If I don't lock within KTweaker then I can go into the performance tab under settings and set the max frequency there and it works. Sometimes it doesn't. CPU Spy shows that even sometimes when both the CM10 system performance setting shows 1.7GHz and KTweaker shows 1.7GHz it doesn't hit 1.7 ever, just tops out at 1.5.

Whew, hope that made sense. If there is any other info or anything else I can tell you about to assist in diagnosing this issue let me know, I will update with said info.

Thanks again for all your hard work!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
Looks good so far :) Love fast charging :):):)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
Dude. This isn't a ROM. This is a kernel. And yes the Sammy version of this kernel will work with stock ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wavrunrx:
ive just updated to the 9/10 kernel, stock sammy and am getting some major artifacting on text. icons also jitter around, as well as widgets. ive not changed anything on my phone for days, except for the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stir fry a lot:
Here's the fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tgamble160:
Just saw your write up on omgdroid. Congratulations man and great work on this kernel downloading latest now. Thanks for this

sent via galaxy s3 in boss mode @2.1ghz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man :D :good: :cyclops: ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
Thank you K. Just updated to 9/10. You are a gentleman and a scholar. The max MHz glitch is fixed. Loving your governor too!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks, I hope all that code I added kills the last of the issues with non-stickage :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
I think that I'm one of the people who had the most problems with the stickage, so I'll flash it and report back!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sweet, thanks goddess :D

Be sure to wipe cache, dalvik and do a fix permissions and while ur at it, wipe data for the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dante2512:
No. KT has a Sammy kernel and an AOSP Jelly bean kernel. However the latest stock leak is Sammy Jelly Bean, and so I highly doubt that it would jive. You can always nandroid and give it a whirl but don't expect it to work 100% of at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Did none of my suggestions work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Your suggestions ALWAYS WORK :good: :cyclops: ;) :silly: :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psloan:
How do you use the fast charge?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Under "Extras"

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
:o:o:o:o Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Turn the check mark on and then plug into a DC power source or USB on ur PC. Be sure to red the change log for a warning about USB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Any adverse affects you can think of that might occur if you enable it, and left it charging over night? Not going to melt my battery, cause a fire and burn my house down, will it?? :p

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Only what I stated in the Change Log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Woot, installed it and everything is sticking!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Backed up, wiped cache, dalvik and fixed permissions before and after flash but didn't wipe app data. So far it's working flawlessly on my WanamLite1.3 and all my settings were preserved. Of any issues, will clear data before reporting.

Bravo! 50 shades of awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ppluissz:
By the way if some one is still having problems with the overclocking just set on boot the script in the unit.id folder named oc_enable. You can do this with script manager from the play store
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcorio:
Installed per op, everything is perfect so far. Sticky oc. Thanks a million. Again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
I flashed 9/10 then wiped cache/dalvik, fixed permissions rebooted set overclocking. Rebooted. Settings didn't stick. Cleared ktweaker data, tried again, setting didn't stick. then Flashed 9/5b the same way, settings wouldn't stick so I cleared ktweaker data and now they stick. I didn't have the settings not sticking issue until the new 9/10. Is there something else I should do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tgamble160:
Did you hit set options on boot? I hit set options on boot set 5 second delay. And after reboot wait 5 srconds after seeing ktweaker has been givin root permissions message to display on screen then open ktweaker your settings should stick

sent via galaxy s3 in boss mode @2.1ghz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcorio:
Also, have you updated superuser binary then delete ktweaker root privileges? Try it if not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
I have been trying to solve an issue I have been having without much luck but I was able to narrow it down to only happening when I was using this kernel with aokp. Basically my vpn drops all ability to use data after about a min or two of use. The VPN stays connected but no data gets transferred. This only happens when I combine this kernel with aokp rom, when i run aokp with its stock kernel it works fine, when I run a stock rom with the kt747 kernel it also works fine. 100% of the time when using this kernel and task's rom it will happen. All that you need to do in order to test this is connect to a vpn and run a speed test, the internet will drop out before the speed test completes.

If anyone can shed some light on this I would really appreciate it, I love using this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aalh:
Well I thought I was gonna get some joy today....

9-10 gets through optimizing apps and almost finishes loading the screens

but it freezes and reboots within 10 sec of booting to lockscreen

this is much further than any KT747 since july has gotten on my phone

closer ktoonsez
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Love the update ktoonsez :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Your not flashing immediately after flashing a ROM are you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aalh:
no

running the latest Taskrom

been on it since release with the included kernel

I flashed 9-10 cleaned cache and dalvik, and fixed perms

and I get the boot cycle again (just later in the boot than earlier versions)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
I haven't updated supersu binary lately so I'll try that when I get home.

Options were set on boot. I usually do it immediately on boot but will try a delay when I get home as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EskimoRuler:
Thanks KT!! Running Yours and Tasks 9-8 AOKP JB Rom update with the 9-10 kernel and phone is working great. I was having the problem with the OC not sticking but after flashing it last night, clearing data for KTweaker and reapplying root privileges, it hasn't unstuck at all. Thanks for a great update!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stir fry a lot:
This worked for me on 9-5 until I reflashed 9-10 to pull a logcat. When I went back to 9-5 due to 9-10's Ktweaker FC'ing issues I was having this patch no longer worked. I'm now back on 9-10 and just have to push the .apk through root explorer everytime I reboot to get Ktweaker to work. However once I install it, it opens right up and my settings now stick at least.

edit: spoke too soon. Just tried to open KT and it's not opening again. My OC is sticking though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
That's unfortunate that your phone doesn't like this kernel :(

One more thing I would try is format system, data, cache, and I would backup and format /sdcard too, then reboot recovery, flash ROM, reboot, then try the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] expertzero1:
And is he install the right aosp jb kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stir fry a lot:
It's been the same issue after a couple fresh installs. I'm on the TW version. It's working great for the most part. Sometimes I have to reinstall KTweaker if I want to go in and make changes but my voltages are now sticking and everything else is working perfectly fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
Is anyone else having issues with this kernel on aokp when running a vpn connection?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 420SYN:
I finally got it to stick I think removing ktweaker from my supersu permissions and letting it reauthenticate fixed it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goojman:
Great kernel by the way. Just curious wut max frequency some people are using for screen off on Ktoonservative gov? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Ahh.. Thanks man. I feel the same. :D ;) :highfive: :cyclops: :victory: :angel:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Had super lag which 9-5b fixed. with this kernel on same settings, kt, or when i tried Pegasus, my phone would get hot when playing a graphic intensive game which would eventual close after 2 mins. Using cooltools I saw that it would get to 38c at its most.

Just putting it out there is all

I will play around with it more. Delete this and that and reinstall, wipe the wipeables and fix permissions. See what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
I usually use 384mhz for screen off.....

Only time I change it is when I play music via Bluetooth with my blincm2 motorcycle helmet thing.

I actually have to run default voltages when im using bkuetooth otherwise I get crackling but I'm Undervolted very low.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tgamble160:
I'm using ktoonservative max 2100 min 486 screen off max 486 still getting about 5500 on quadrant and as of right now I have 57% battery still and 9 hours with almost 3 hrs screen on time. Kernel is frickin awesome.

sent via galaxy s3 in boss mode @2.1ghz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Anyone seeing improved cell connection in 9/10 update? For the first time I got 4 bars in my basement where I usually have 0!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dssking:
Excuse my ignorance but Ktooservative? Ive installed the kernel and have Ktweaker.

I missed something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DRLyman:
It's one of the governors. It can be selected under CPU Governor in the KTweaker app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tgamble160:
That's all I got to say about that.

sent via galaxy s3 in boss mode @2.1ghz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tgamble160:
What else could you ask for on a phone like this?

sent via galaxy s3 in boss mode @2.1ghz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
ktoonsez,

Not sure what the code in v9-10 does, but above was definitely the fix for OC reverting back to stock max. I'm still on 9-5 and it hasn't gone back since. (maybe only the deleting and re-granting privileges alone was necessary.. don't know) It may be something good to put in the OP, unless your added code does the same thing.

thanks! on to 9-10!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
A bunch of kernel code to stop it from changing at the source. While that worked for you, Im sure it would not for some of the others, this new code will deny any ROM and or kernel call to change it except for KTweaker that has the magic password :D, LOL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] saldebot:
cant download from my phone, when i save file to pc. as it starts to download antivirus stops it. mirror ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tgamble160:
Gimme a minute I'm uploading to my dropbox now

sent via galaxy s3 in boss mode @2.1ghz

---------- Post added at 06:14 AM ---------- Previous post was at 06:13 AM ----------

http://db.tt/pxNcAkEU

Here ya go

sent via galaxy s3 in boss mode @2.1ghz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benburch9:
Fixes my OC not sticking, but not my voltage table for some reason...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
First time I broke 9k in the random number generator :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JB calhoun:
Thats normal ...kinda low
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juancaperez2000:
how much are you UV? nice battery life