yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
No need for permission changing, it should stay.

If you want this to last between reboots, just create a shell file with the echo command and place it in your init.d so it runs on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
I see you still hard at work Ed. Newest release working awesome on my Pops s3. Thanks.

ATT S4 Rooted. Beastin.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.4.y Build 2013-05-12 - http://www.droidhype.com/kernel/34

Remember to go hug your mom, grandma, aunts, etc. today. Happy Mother's Day to all that celebrate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Thanks a lot for the awesomeness ;)

Deviant Xone + BMS = Amazing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Voltage

Okay, I've likely got a stupid question that I'll probably get flamed for, but, eh, the burned hand teaches best... this is the kernel I always use. Most times, I have no problems. However, I have a Rev. 0 processor that is a bit finicky with the voltage. I have no problems with CM's stock kernel but this one offers much more in the way of performance for me. How would I go about matching the voltage of the latest CM kernel to this? Is there anywhere someone could direct me to find the voltages from CM's kernel so I can apply them to this one? Maybe I'm way off base. Who knows. Any help would be great, though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
https://github.com/CyanogenMod/andr...ob/cm-10.1/arch/arm/mach-msm/acpuclock-8960.c

That's where the tables are for CM. However, on CM you will boot at a minimum of 1150mV. So in your favorite app, set everything that is below 1150 to 1150 and you have the adjusted CM values. BMS undervolts and removes that vmin, so it boots at 975.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Thank you so much! I appreciate the feedback and all of your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Nothing runs better than this kernel on my phone. Thanks for sharing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Is there any way to make trinity colors stick after a reboot? I have to manually set it every time I turn my phone on again. I'm using the 5/11 CM nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Are you running today's BMS release?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Yes, 5/12
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
It's sticking for me on my CM nightly :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
Sticking for me on Task 5/9.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Just started sticking for me after about 10 reboots, let's hope it stays this way :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evostevo1:
I can not get trinity colors to stick for the life of me. I'm running most current liquid smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Probably would just need to set a start up script to set it on boot (init.d) to get around this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evostevo1:
Other than that so far so good. Nice work. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
What are Trinity colors? Sorry I just flashed this kernel last night
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
It's a modification that changes the way your screen displays colors. You'll probably notice more blues and a "cooler" display than stock. The strength of the effect is variable across devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
For sure dude the blue is a lot brighter, how do I tweak it though. I can't seem to find the setting for the Trinity color.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Search a few pages back. Gideon posted a how to. I'm not knowledgeable on the matter as I don't use this kernel. I was just offering what I knew about trinity colors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Hey gid how's it going? Bro I've been getting random reboots on the newest update. I get it Like once a day. Tried to save last_kmsg.txt but for some reason it won't let me but I'm attaching whatever I got to save.

http://db.tt/LzI4qBIh

Deviant Xone + BMS = Amazing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I'll need a last_kmsg to see what's happening :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
Running this with new Liquidsmooth official release (5/18) running great, on pace for about 4.5 hours screen time using interactiv and row, stock voltages, Thanks for this, I look forward to your next update :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evostevo1:
Took the words out of my mouth :) great kernel development.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgoe:
Which one are you using 3.0 or 3.4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
Liquid smooth uses 3.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.4.y Build 2013-05-19 - http://www.droidhype.com/kernel/34/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Thanks for the update bro! No random reboots so far. :beer::thumbup:

Deviant Xone + BMS = Amazing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ingram10:
This kernel with slim bean 4.2.2 is nuts, 18 hours 3:30 hours on screen time 70 minutes talk time haven't really tried anything else since this gives me good results
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
With this version, I am having trouble reconnecting to bluetooth. Previous version had no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
What rom are you on? Some CM nightlies recently are seeing BT connection problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
Same as before - Carbon 1.7. I haven't made any change to the ROM, between the previous and current kernel version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] darkstar765:
GideonX may I ask what governor and scheduler you use and if you do any under volting or any other mods? Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Only thing I can suggest is un-pair, wipe bt data, re-pair.

Int/fifo, hispeed at 810000. No other mods :)

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
I think I found a ROM bug. After wiping BT data, I am able to connect with the bluetooth as a new device. But if I switch BT off in the ROM, and switch it back on, the previous BT pairing and the friendly name returns, which doesn't connect to the bluetooth device. Not sure why this wasn't happening in the previous kernel. Thanks for the advice though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Any frandom users in here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I prefer snake oil to repair the tissue from my battle scars. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Legit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
I'm sorry but I have a n00b? What is Int/fifo?

Thanks

LiQuidSmooth & BMS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wujiku:
Intellidemand / fifo scheduler
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Interactive governor, fifo scheduler ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
What Walter White said :)

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeygee23:
Same issue here...have to force close and clear data.

---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------

Can you guys share some settings you've had good experience with battery life wise?

Much appreciated.

---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------

Can you guys share some settings you've had good experience with battery life wise?

Much appreciated.

---------- Post added at 10:31 PM ---------- Previous post was at 10:24 PM ----------

Can you guys share some settings you've had good experience with battery life wise?

Much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Try those Gideon posted last page. Interactive/FiFO with hispeed_freq set to 810.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeygee23:
Did it! Thanks for reply.

To All: my bad posting reply three times!

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

1836 & 192?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
192/1512 has worked just fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
I'm still new at android OS, what's different about an frandom kernel module than BMS kernel?

LiquidSmooth & BMS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Its a replacement randomness generator

Here's an article touching on the subject

http://hackaday.com/2013/01/04/is-entropy-slowing-down-your-android-device/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
I had a random reboot today during a phone call. I'm on the new build,update 5/19 3.4y BMS kernel, here are two Catlogs. Thanks for this great kernel:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikea29:
Uh oh!

I flashed this kernel and now when it boots up, it goes to the Samsung screen for 1 second and goes off completely. I made sure to get a kernel that has an earlier release date than the rom im on...dont know how to fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Which rom are you on and which kernel did you flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Flash your rom again, then go into settings, about phone. What does it say under kernel?

What rom are you on and when was it released?

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikea29:
Im on Liquid Smooth 4.2.2 v2.4 and I flashed the BMS...I think I flashed the 3.0 version though by accident. Ive got no choice really but to flash back to stock through Odin....phone wont even boot up...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Need a last_kmsg

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Power down

Volume up + home + power, release when white Sammy splash screen comes on.

Did that bring you into recovery? If so, just reflash your rom and reboot and you'll be back in LiquidSmooth.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikea29:
It worked. thanks! Should I even try to flash the 3.4 kernel? The only reason I was doing it was to get rid of the screen flicker issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
How do I get that? last_kmsg? Sorry still a n00b:confused:

LiquidSmooth & BMS Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
3.4 will work with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
There should be a file in /proc/ called last_kmsg

That's the one :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Go for it

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
What's your email &I'll send over the last_kmsg log. Can't post it from my phone sorry.

LiquidSmooth & BMS Kernel

---------- Post added at 11:38 PM ---------- Previous post was at 11:28 PM ----------

Is there away to share this from my phone? Can't figure out how to post it with out my PC.

LiquidSmooth & BMS Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
you can log in to xda on your browser and attach it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsyl:
Flash liquid on recovery again and you'll have a working kernel till you download 3.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikea29:
OK, I downloaded the 3.4 version (Im on LiquidSmooth 4.2.2 v2.4) and tried to install through cwm, but it keeps saying installation aborted. Do you think its just a bad download?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
I would down load goo manager then in stall TWRP through goo manager. It will over write the CWM files. Also re-download the file.

LiquidSmooth & BMS Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I'm running BMS on Slim 5.7 for now and I'm trying to adjust the sampling rate down on Wheatley... It won't budge from 50000, which seems a bit high to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Couple more hours till mid-night aka Monday... *ahem ahem* ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
It's memorial day weekend, might be late this week :D

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReasonablyRooted:
Enjoy your weekend, Gideon... We're just addicts. Don't mind us. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.4.y Test Build 2013-05-27 - http://goo.gl/VTNJi

Folks with BT issues, please try this test build for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Well, I'm having zero issues on mine, using this kernel with Liquid Smooth, but I'm happy to try the test build - I guess I'm the 'control!' :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
The BT reconnection issue is gone with this build. But once in a while BT refuses to switch off. When that happens, doing an FC of BTShare disables the BT, and after that everything is back to normal.

Is it safe to continue to be on the test build?

Thanks :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Yup, should be okay to keep using it. This will likely be the release for this week.

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

sephk - grab this one, it has another CAF update in it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
edit- downloaded the correct file BMS_34_d2att_d2tmo_20130528.zip. trying it now.

BTW: why was the 192 slot removed? I have noticed that using 192 as the lowest slot gives better battery life.

Sent Using Galaxy S3 AT&T - Carbon 1.7 - XDA App
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
Is there a link for the BMS freedom zip?

LiquidSmooth v2.5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Tested both over time, didn't see that much difference. I didn't like the low base clock I was using for 192, it wasn't right.

It's on the page at the top and in the build changelog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
Ok, I will use it at 384 and report back in a few days.

BTW: if I am on ondemand/row, then using Navigation (GPS ON) makes the device extremely sluggish. I switched to wheatly/row, and with that it was ok, but not perfect. I did ask about this issue, but doesn't look like anyone else has faced it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
I'm doing a lot of traveling this week; my usual issue is that the GPS causes overheating/rebooting. I will try a few difference options - wheatly, interactive, ondemand, etc and see what I can find...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
GPS has always gotten my S3 hot as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
GPS is a bi$ch lol

Deviant Xone + BMS = Amazing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
One more question, if you don't mind... sometimes I see msm_otg kernel wakelock (thru better battery stats), draining the battery. If I reboot, then it goes away. I tried researching on the topic, but didn't find a good answer. Some say that it may be because of bad USB cable. I tried many cables that I use with other devices as well, and it still happens with all of them. Others just say that it is a problem that originated with samsung base sources.

Do you know what this is about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
That wakelock was fixed a while back, not sure why it popped up for you :confused:

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
Yes, it still appears, even after today's kernel update. Are there any logs I can share from my device, that might help troubleshoot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I got that too, and not just on your kernel. It's very rare though and it's not necessarily triggered like in the past where you rebooted while plugged in then unplugged. I haven't yet figured out how to summon it to my will.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
I think that's my trigger, rebooted while plugged in then unplugged. Good to know that I am not alone.:highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That one was fixed a while ago though, it might be related but I doubt it's those exact steps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReasonablyRooted:
Bluetooth fixed for me. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
About to flash this baby again even though it's illegal to flash babies ;) lol

Deviant Xone + BMS = Amazing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Gid, can you tell me what this means? and what I might notice from a bad low base clock on my phone?

And is this an across the board for all S3 kernels, or just something going on with yours? I see like a couple of hours extra time with 189 or 192 over 384 as far as I can tell, and don't think that any problems arise from it on my phone... but perhaps I just don't know what to look for???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
In a nutshell, I changed pll8 (base clock) to match 192. The slot was indeed using 192, but at the same time dropped it for all that used pll8 (cpu, gpu, etc). So it worked, but at a slight performance hit for everything else.

Anyhow, performance should be a bit better with this switch back I think ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Unless you are applying custom voltages manually, the default voltages are the same for several of the lower clocks, which means battery savings are either extremely minute or totally placebo. That's my understanding anyway.

Sent from Bananaphone v2.0 (Final)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's more complicated than that though, there's always the clock frequency itself. 192 < 384 (hint hint, based on hertz ;)). Extremely minute sums it up though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Right, the changes are pretty small.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Right, there's the multiplier to contend with, but we're talking fractions of mV. I used to spend hours tweaking my undervolting to find stable... And so not worth it.

Running crossbreeder just for fun, kinda interesting so far. Nothing concrete though.

Sent from Bananaphone v2.0 (Final)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
The changes in power consumption can be small in certain situations, like when the screen is on, because screen power will dominate the equation. But when considering just the processor power consumption frequency and voltage are the main components. When listening to music with the screen off I have found significantly lower power drain using a lower clock speed.

On my way to work this morning I was listening to a podcast and lost over 4% in less than 20 minutes while running at 384mhz. I switched to kt747 kernel and set my min to 81mhz and under the same conditions lost barely 1% over 20 minutes even with both running at the same voltage.

CPU frequency and power consumption are directly related and the difference can be very significant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Switching kernels is a sure fire way to blur the lines of scientific testing. Use the same kernel, (KT747) but change the clock back to 384Mhz and test.

For that matters, the same podcast should be used for both tests. Difference in bitrate is directly correlated to power usage.

---------- Post added at 09:47 AM ---------- Previous post was at 09:44 AM ----------

I agree with you and have had the same conclusions. Undervolting on phones is very difficult, there's very little room, the chips are already pretty well optimized for battery saving. Which is unlike a lot of computer CPUs where you can save a lot from undervolting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
BT working fine...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I agree and was a little hasty in my conclusion. Changing kernels, or simply rebooting my phone could have played a bigger role in my battery drain than the clock speed.

I'm in the process of testing again, but this time changing only the minimum clock speed to rule out any other influences. I'll report back later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks for taking the time. The S3 is a beastly phone, but it sure drains its battery quickly. Every % counts haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I wanted to post a quick followup here. I did some battery drain testing yesterday. I played locally downloaded podcast at 1.25x speed using presto. This puts a very consistent load on the CPU, but it remains low enough to stay at the minimum frequency most of the time. I did my best to not touch my phone for a full hour and just let the podcast play in the background with my screen off. I started using 378mhz minimum, played for an hour and then repeated the test using 135mhz. Voltages were the same (975mv) for both tests because my phone does not tolerate undervolting. I set a custom reference with BBS at the start and took screenshots after an hour. Unfortunately I needed my phone for something else about 50 minutes into the 135mhz test, so it got cut slightly short.

Results:

378mhz = 3.8% / hour

135mhz = 4.8%* / hour

*Had the 135mhz test been allowed to continue for the full hour, I estimate that the result would have been identical to 378 due to the way BBS calculates these numbers. It simply divides the % lost by the time. Due to the limited resolution of the battery monitor everything is rounded to the nearest whole %. Both test resulted in 4% loss, but the extra 13 minutes of time makes the calculated % drain/hour look lower in the first test.

I plan on repeating the tests again and including 192mhz. But at this point I'm confident in saying that 135mhz offers no real battery savings over 378mhz for this type of usage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Is it safe to say most of you are using Trickster now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Sometimes testing things yourself is the way to go. Nothing beats that sort of certitude. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If I need to change CPU related things, yes. Rarely do need to, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Thanks. I really don't change anything. Usually use interavtive/cfq. I don't know or understand any of this stuff enough to start changing settings like some of you do lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Yup :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
And honestly, there's very little advantage to touching every governor tunables or similar in BMS. They're pretty well set for a good battery/performance ratio. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Thanks. I installed Trickster just to see what its all about. Started looking at all the options and then exited out lol. Too confusing. I changed nothing.

Also, Thanks Gid..this is my go-to Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Default everything should work just fine, enjoy :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Glad to hear that! thank you again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
Going to flash the 5/28 build tomorrow, [MENTION=227136]Gideon[/MENTION] I'll send you an email if I experience any problems, if that's cool. This is my goto kernel as well. Thanks bro

I plan on leaving everything at the default settings to, unless other wise directed..

LiquidSmooth v2.5 & LK 3.4.47
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Sure thing

Sent from my SCH-I535