yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
I was having a similar problem...I narrowed down to trickster mod sound control, removed app and it fixed it. However; I tested with other kernel like linaro 4.7 and it works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
So remove trickster mod and it'll be fixed? Ps. I haven't done anything to the sound control in trickster if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madhacker7:
I agree with your logic but I've found that if I clock/volt too low, my battery suffers. I suspect the reason is that operations are taking longer to complete for lack of MHz and I'm losing any battery economy because of it. The race to cpu idle is taking too long. Just my 2 cents.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
To pitch in, I was wondering why my phone overheats so easily and it was cause I set it at 192 before and that makes the CPU really hot (I don't think you'll want that)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hope you are enjoying the holidays. Can't wait for the next release based on cm stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
If your specific phone cannot idle at 192MHz, it will bounce the speed back up every time it tries to idle. That's where your heat is coming from. Not because a low idle is causing heat but because it just can't idle. Set it to default; some phones just can't handle what some others can. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
New build v6.6 is out.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
The voltage/frequencies table seems a little bit screwed up...

The lower frequency has the higher voltage... And in set cpu, the frequencies list starts with the lowest frequency instead of the higher one.

Also, after installing the 6.6 exp, I've got a few random reboot.

Am I the only one with those problems.

... OK after some testing, I looks like to be a problem with set cpu. I just got an update, and the problem was fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I'm getting reboots with 192 min after flashing 6.6, upping it to 384 seems to fix it. Which is weird cuz I've never had a problem running 192 min. Anyone else?

edit: uploaded my last_kmsg if its any help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I was going to edit my previous message with the same problem... My device always ran fine at 192...even 181 with other kernels. But now, impossible to run at this frequency...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Mine is running 192 MHz @ 775mv OK. Only thing I had happen out of the "norm" was my screen didn't come on one time and I had to hold the power to reboot manually... No issues besides that or since.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
That's what I'm getting. If I let it sit long enough it reboots eventually
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I also run 192 with no random reboots... ever, but had 2 right in a row with Lean 6.6, so went back to KT's kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Yeah, had another black SOD while trying to wake the phone from deep sleep last night on v6.6 exp.... Just went back to v6.5 until it's worked out. No big deal. :)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Guys, why don't you let op to update thread with new releases?)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
What??? He updated his release site with the new releases... So..... I'm confused with what the problem is???? :confused:

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sudeeps:
need guidance

Hi,

I'm new to android and all these custom things like kernel,ROMs etc. But I'm managed to root my phone and install cm10.1 nightly on my phone. Can someone please guide me to installing this kernel correctly as I tried flashing the zip in recovery but the kernel in about phone still says cm10. My phone is a galaxy s2 GT-i9100. Please guide me and sorry for such a noob question .

Thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
It hopefully failed to flash in recovery because this kernel is for the gs3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sudeeps:
Thanks. So can I get some help on any such kernel for GS2 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoopDoGG79:
I would go to the forum that corresponds with your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] umvagia0:
Boys, could one of you recommend what version of this kernel would work best with the latest CM 10.1 stable version? I was going to install the latest version of this kernel, but want to make sure there are no bugs.

Thanks in advance for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
If u look a page back, It seems the latest version breaks the ability to use 192 as your min. 384 works fine for me. If you want 192 flash 6.5.

Actually I just realized that not everyone uses the experimental version lol. 6.6 stable should be fine just note that 192 seems to be broken in 6.6exp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] umvagia0:
Thanks man, that's what I gathered...but wanted to be sure. My phone is my daily driver that I use for work as well, so I don't want to bugger it up. I'll flash 6.5, I usually set my min to 192.

Thanks again, can't wait to try this bad boy out!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Why you prefer exp over stable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
for your information, 6.6.2 is available.

but the problem with the 192MHz setting (black SOD or reboot) is still present.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v6.6.2 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
When using trickster mod to adjust kernel settings I see that MP-Decision service is ON by default. Does this kernel have its own hot plug service so I could turn mp-decision off or should I keep it on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
No, I think you need MP-Decision to hot-plug with Lean.

---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------

You can adjust both frequencies and voltages with the experimental (exp) version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jubei527:
How did you set yours to 192 or lower? my can only go as low as 384.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Its only in experimental version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jubei527:
I see. And thanks for the quick replyreply
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Thanks for your reply. Regarding frequencies and voltages, I can adjust them on regular release as well, just can't go to 192.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
It seems like everytime I swap batteries on my phone I lose my trickster mod settings does this happen to anybody?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Trickster mod settings aren't saved on boot unless you go in settings and specifically tell it to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
My bad. I had it set before but upgraded the kernel. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I am wondering this as well. Anybody know?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
LK doesn't have its own hotplug, so you have to use mpdecision. I've never had issues with mpdecision myself for it makes it hard to tweak the kernel settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Been out of town a few days, just wanted to say that I was still getting black screens when waking from deep sleep on v6.6.2 experimental. Still rocking v6.5 for stable 192 MHz.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v6.7 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog

Swiftks: let me know if you still have issues with 192mhz on v6.7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Yeah, still got black screen.... Was working well. But then turned screen off, and then immediately back on, and screen wouldn't turn back on.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
as soon as I enabled the 192mhz frequency, I got an instant reboot when the screen went off...

no other settings were changed for the kernel... all default.

here is the last_kmsg for this crash/reboot https://www.dropbox.com/s/yj20x3105ch8iw9/1373540529202.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Maybe try putting a bit more voltage for the 192Mhz step. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
no matter which voltage setting I use, it crashes...

I left it at the default setting (1150 if I remember correctly)... does not work.

my phone always worked at 875mv for 192 and 384mhz... works fine at this voltage and frequency with other kernel. works fine with v6.5 with those settings too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Ok I will fix this for 6.7exp2 this week. Probably one of the CA commits I merged in after 6.5.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
thanks for your work!

if you need more testing to be done on a d2att, do not hesitate to contact me...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
hey guys, i believe i took care of the 192mhz reboot issue for the exp builds. 6.7exp2 is up now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
yup!!! works fine now!

Thank you!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Parnic:
Hi Imoseyon,

Thanks for your work on this kernel. I've been using it on my Galaxy S3 (d2att with CM10.1.1) and getting great performance and battery life.

In v6.4, bluetooth audio works great. However, in every stable release since then, I frequently will only get audio out of the right channel when playing music in my car over bluetooth. Sometimes switching media players or songs will temporarily fix it, but it usually drops back to just the right channel when another song starts.

Am I missing a setting somewhere or should I just stick with 6.4 for the time being? I'd love to help debug/diagnose the problem if necessary :).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Are you on CM10.1.0 stable by any chance? That build had the right-channel audio glitch, regardless of kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Parnic:
I'm on 10.1.1 stable, but I also had the problem on 10.1.0 stable, yes. With CM 10.1.0, LK 6.4 played audio correctly and LK 6.5+ did not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Here's the related commit:

https://github.com/imoseyon/leanKernel-d2vzw/commit/768128501441cfdfd16b400e5c2b3560227c8a3b

Unfortunately CM slightly broke this in the ROM so audio gets broken in a different way if I remove this commit. ie. it's not perfect either way..

Edit: actually i uploaded a test build with that commit reverted if anyone wants to test: http://imoseyon.host4droid.com/s3/aosp/test_builds/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Parnic:
Thanks! I'm giving this a run today and will post back tomorrow with info on how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BTT8:
Why am I now getting permission denied when i type in lkconfig?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Same here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BTT8:
Figured it out.

Type "su lkconfig". Then "lkconfig again.

Edit. Btw, how are some of you guys able to decrease the frequency to 192? I'm using trickster mod and the least im seeing is 384mhz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Parnic:
This is working great for my use case :).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
1) First you just type "su" to grant terminal superuser command. Then "lkconfig".

2) if you're using TricksterMod, there's no need to use lkconfig command at all.

3) For 192 MHz, use the experimental builds.

;)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
1) totally forgot about su, shame on me

2) how do you set screen color temperature with trickster mod?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Most of the AOSP based ROMs for this device have a "device" section under Settings. Typically the option to change screen color temp is located there.... at least this is the case for Slim and Task's AOKP.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
CyanogenMod 10.1 Found this under System Settings - Device - Advanced - Screen - Screen Color Temperature. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] umvagia0:
Are any of the experimental builds really stable? I like the stable build a lot....the only downside is not being able to under clock to 192. This is my daily driver and don't want any issues so if I have to stay with the stable build I will.

Thoughts?

Thanks for any advice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
With stock settings, it's always stable. That's how I roll.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
The exp v2 is perfectly stable for me at the low freq. Stock settings with the stock governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
It's the same build with the added functionality of

you

being able to experiment with voltage and frequency settings. It runs perfectly on the latest CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
what's the difference between the gpu governor "simple" and "ondemand"? I mean I've never seen the "simple" governor on any other kernels, it's totally new for me. can somebody explain the new governor a little bit?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
you can still play a bit with voltage and frequency settings with the "standard" release.. but for the frequency, you can go lower with EXP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I was unaware it was added to this kernel? Its in BMS, it was created by faux the idea is to add tunables to the GPU governor like CPU governors. I'm not sure where those files are, I'm sure they can be found with a little searching.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
With kernel 6.7 when I rotate my phone the screen rotates on the wrong side.

If I go back to 6.6.2 it works fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
really weird... works fine on my device...

you might want to try the 6.7.1 version available in the test_builds folder (http://imoseyon.host4droid.com/s3/aosp/test_builds/#!/view=details/lang=fr/sort=na)... this is the one I'm using now for the past few days and it's working really fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Thanks a lot for your help.

You know what... When I was about to copy the 6.7.1 to my device I jsut noticed that my 6.7 kernel was the Sprint version instead of ATT :eek:

It's probably going to work fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Is it possible to install the vzw test versions on our Att phones?I always thought to avoid them
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
That kernel is different. DO NOT FLASH!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
What's wrong with the att versions? Vzw kernel will boot I've flashed them before. If anything there might be a minor bug. And of course flash at your own risk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Confirmed, I have flashed vzv kernels before as well. They worked. They felt kind of sluggish, but that was right when s3 switched to Linux 3.4, so I blame that. I understand urge to flash vzv kernel though because I see version 7 there )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BTT8:
I'm getting bootloops using the latest version of leankernal and CarbonRom. I thought switching over to this kernal from kt747's would solve this issue but it hasn't. I'm on d2tmo (s3).

My order to flashing:

Clean wipe>boot>reboot>Install leankernal>boot>redownload all my apps (via playstore, not TB)>reboot>bootloop.

Same issue with kt747, same issue with leankernal.

Using stock rom, I'll have no problems whatsoever though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I couldn't find the CarbonRom to see when it was updated last. Chances are there are newer commits in these latest kernels that won't work with an older ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v7.0 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
thank you for your work... works fine!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v7.1 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
7.1 working very nicely with Slim 7.8.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireforhire:
Where did you get 7.8?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
7.8 is now available on the Slim servers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
Great kernel!... Running pretty well here... Thanks for your work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Yes, the kernel is great. Love the minimalistic approach, where the main focus of development is to polish existing minimum rather than adding more and more functionality that has tendency to break.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
how to save battery life?

the leankernel has been running on my phone (task's aokp) for about 10 days. i never doubt its performance and graphic capability cuz the games runs super fast and super smoothly that i've never seen on the stock kernel.

what i really concern about is its battery life as long as its temperature. the kernel is causing huge battery drainage. yesterday when i was using my phone i was doing nothing else than tweeting and net browing, but after about 40 minites the battery drained from 84% to 65%, which i've also never seen before! so yesterday i let the phone uncharged and switched to the airplane mode and it was 55% before i went to bed, and today's morning i amazingly found the battery became 38% after 7 hours sleep! any idea?\

my cpu tuner is trickster mod and my settings are:

i/o scheduler: deadline

min cpu: 384000

max cpu: 1512000

governor: interactiveX

cpu governor: screen_off_maxfreq: 486000

multicore power saving: 1 (0 for disable to 2 for most aggresive)

temperature throttle: on

gpu governor: ondemand

gpu max: 480

mpu voltages: uv'd 50 for all steps

all the rest are stock

are there anything wrong with my settings? or should i just leave it all stock?

again, i really love the kernel for its great performance, but please can somebody help the battery life??

please help!!:crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Useless without a BetterBatteryStats log or similar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Get some app like better battery stats to see what is keeping your phone awake and possibly draining the battery.

I had a similar problem two days ago... And it wasn't the kernel fault... It was the phone app keeping the device on and cpu maxed out. After a reboot, it was solved... Today there is an update regarding ril in cyanogemmod nightly... Maybe this has something to follow either the problem that I had
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
really? a new update today available? great!!

i did tried to switch back to the stock kernel of task's rom. the battery seemed way better and with the stock kernel my phone could hang for a whole night within 5% battery drained, but the graphic performance is not as good as leankernel's either. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
If it is running fine on stock, try switching back to lean now. It should be fine. Your settings look good and you probably just had an app that went wild. Sometimes an app goes crazy and pegs out the CPU, but all that's needed is a reboot. Sometimes a re-flash in needed to fix things when they go screwy. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
what are very good settings to use for GOOD performance and GOOD battery life? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Try these settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Really, MPdecision and temp throttle On?

I posted my settings a few pages back I think.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
No hot plugging without MPdecision ON with this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Can you tell me ALL you're settings please. I looked a few pages back and haven't seen it... Lol.

---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------

I'm not on touchwiz... Im rocking Slim Bean! Sickkkk ROM. & I know swiftks is too. (; :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
I suck at looking. :( thank you!

The voltage "192" isn't there for the latest build so i i just used the "384" for my min.... lol. And for voltages, i just carried on from "384" down. (: :good: I'll test this out and report back.

---------- Post added 31st July 2013 at 12:07 AM ---------- Previous post was 30th July 2013 at 11:25 PM ----------

Also, i know that "192" is for experimental builds. (i read that...) :p

But i'll just stick to the latest v7.1. (; is that okay? :silly:

Read the post above to see what i did, because there is no "192" .. (:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
can undervolt help increase battery life? if not, what can undervolt do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Correct, that's the goal. But not all processors like it, some overheat on an under volt and cause worse battery life. Just have to try it on your device and see. Mine does well on the settings I posted, but when I use the 192 slot I get worse battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
so...any recommended "balace" settings available?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
I posted mine a page or 2 back...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
how's your battery life under your settings?

btw why there's an "mpdecision" option on your tricktermod but neither do i? is your trickstermod paid version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
EVERYONE, USE SWIFTKS KERNEL SETTINGS.

HOLLLYYY ****. IM ON SLIM BEAN & LEAN KERNEL WITH HIS SETTINGS. AND I'M HEAVY USING. WITH 50% LEFT WITH ABOUT 12 HRS ON BATTERY AND 2 HOURS OF ON-SCREEN TIME. ALMOST 3 HOURS. ENOUGH OF CAPS LOCK (;

I will post my battery life once it dies. if it does. (; :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
which app can I use to do that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Trickster MOD

https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] halodos:
So if frequency lock is on, does that mean it's either at the highest or lowest frequency with nothing in between? And this saves battery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
frequency lock will prevent other apps from modify the cpu speed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
No, it means that it locks-in the high and low frequencies to what you set them at. Sometimes they will change on their own if you don't use the freq lock. I like to set my high freq down to 1350 just to save a little battery without sacrificing any performance.... at least none that I can tell. If I don't use the freq lock the phone usually pushes it back up to 1500, since that is the default high freq. :)