yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] hdeglide:
kernal switch

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[Verizon Samsung Galaxy S III] neyenlives:
On KTweaker widget, couple questions. What does the "S2W" option do? And what does the "R" in lower right corner do?
[Verizon Samsung Galaxy S III] yonith:
I honestly felt like my phone took longer to open apps which is strange since I remember someone saying that it's optimized for read. Anyway, I switched back to the default which is cfq. Loving this kernel.
[Verizon Samsung Galaxy S III] Div033:
So what governors are people liking on TouchWiz ROMs? When I was on cm10.1 I was using MSM-DCVS since Qualcomm made it but on TW it likes to hover at 1134 MHz far too much. Ktoonzservative seems nice but has a bit more lag than I'd like. Right now I'm rocking interactive since that's Google's preferred kernel and is plenty smooth, but I'm not expecting much in the way of battery life.

Also, KT I don't know if you're aware of this but intellidemand was having issues for me on 4.2. It caused the device to freeze up and reboot. Once I switched from that it was smooth sailing again.
[Verizon Samsung Galaxy S III] stev067:
First, I would like to say thanks so much for all your work on these kernels. I'm running the latest versions of the 4.2.1 AOSP KT747 on my SGS3 and my Nexus 10, with CM10.1 on each. Everything is great on the tablet, but for my phone, I find myself disabling HW overlays a lot. I don't know whether this is a kernel or ROM issue. I'm using stock voltages for now, until everything is stable enough to undervolt. Any suggestions would be appreciated! :good:
[Verizon Samsung Galaxy S III] yonith:
I use the ondemand as my governor and cfq as my i/o scheduler. It's what ktoon has as default when u install the kernel. I figure he probably leaves the best as default.
[Verizon Samsung Galaxy S III] luv2increase:
I think row is the main scheduler now.

---------- Post added at 12:27 AM ---------- Previous post was at 12:26 AM ----------

If you use mastamoon's latest unofficial, you will not need to disable HW overlays.
[Verizon Samsung Galaxy S III] PVLMTREE:
S2W = Swipe to Wake. The option is under the "Extra" menu.

R = Reset? That's what happen when I pressed it. LOL
[Verizon Samsung Galaxy S III] ktoonsez:
R = refresh the on screen values
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
That reminds me... I wanted to ask about the settings button in the voltages tab... When I click it... nothing happens... Is something supposed to happen?

GalaxyMOD spilled Ink on my MultiWindows
[Verizon Samsung Galaxy S III] ktoonsez:
Nothing is supposed to happen. It is the menu (for the popup when hitting the menu button) manifesting itself there. Never did figure out how to hide it.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Ok lol good to know

GalaxyMOD spilled Ink on my MultiWindows
[Verizon Samsung Galaxy S III] jamesd1085:
Hey...don't know if this has already been asked or not but was just wondering if anyone could answer...why is only one core being over clocked with this kernel?
[Verizon Samsung Galaxy S III] yonith:
Funny, cpu1 appears to be offline...always. This was using the ondemand cpu gov. Same seems to be happening on ktooncervative.
[Verizon Samsung Galaxy S III] yonith:
Other frequencies
[Verizon Samsung Galaxy S III] scorchedsky:
Same thing happening here on abyssplug, I wonder what's up?
[Verizon Samsung Galaxy S III] yonith:
Maybe it's the update that just came out a few days ago. Anyone have the prior kernel and willing to investigate?
[Verizon Samsung Galaxy S III] yonith:
Ok I can confirm that the last kernel did it too. Strange indeed since it felt so fast. Any thoughts Ktoon?
[Verizon Samsung Galaxy S III] jamesd1085:
Seems like lean kernel ocs both cores...but I have never been able to get settings to stick right...it causes some instability for me...love kt747 and hope this can be fixed
[Verizon Samsung Galaxy S III] oryanh:
I think its working right. I'm running the latest release, ktoonservative, and it ramps to my max of 1.8GHz just fine on both cores.

Also running slimbean 4.2.1 Beta2
[Verizon Samsung Galaxy S III] jamesd1085:
What are you using that shows both cores are being over clocked?
[Verizon Samsung Galaxy S III] oryanh:
PerfMon

https://play.google.com/store/apps/...tm_medium=organic&utm_term=play+store+perfmon
[Verizon Samsung Galaxy S III] jamesd1085:
Weird...I wonder which apps are working right...that one showed oc on both cores...but its the only app i have found that showed any activity on core 1...but the apps showed full overclock on leankernel with both cores...also got better benchmarks with leankernel even though it has lower max clock...i dont think both cores are being overclocked still even seeing this app
[Verizon Samsung Galaxy S III] oryanh:
Bizarre... I used Jiffy CPU monitor and System Tuner (3c)... Both show cores bouncing well above stock clock. Am I missing something? im going to do some more digging.

Which app are you using?.
[Verizon Samsung Galaxy S III] jamesd1085:
The main reason I noticed it was from vellamo benchmark but since I noticed it I have just downloaded random ones from play store...my main concern is if it is over clocking both why would I get better benchmarks with lean kernel at a max of 1900mhz than I do with kt747 at 2106 MHz? I have tried all I/o and governor combinations but still get better with lean kernel...

"All" i/o and governor combinations is an exaggerated statement...that shizz would take forever...lmao
[Verizon Samsung Galaxy S III] scorchedsky:
I was using System Tuner, but it seems like the problem is really with CPU1's frequency history. Since the S4 is asynchronous, System Tuner forgets the history of CPU1. It definitely overclocks though.
[Verizon Samsung Galaxy S III] Metfanant:
Because higher clock speeds DO NOT equate to better performance...my phone ALWAYS benchmarks higher at 1.6 or 1.7 than it does at 1.9 regardless of kernel...

sent from my VZW Galaxy S3 running SynergyROM
[Verizon Samsung Galaxy S III] luv2increase:
My phone benches at 2.1ghz undervolted than it does at anything less than 2.1ghz.

Your phone probably had an unstable overclock, hence the worse benchmarking performance.
[Verizon Samsung Galaxy S III] mbc663:
Makes sense...
[Verizon Samsung Galaxy S III] Metfanant:
Every phone is different...

what kind of benchmark scores are you seeing at 2.1?

My droid x back in the day would instantly lock up if I tried to run 1.2ghz...but at 1.15 I would out benchmark anyone I knew running 1.2

sent from my VZW Galaxy S3 running SynergyROM
[Verizon Samsung Galaxy S III] Stupifier:
I never really understand why people overclock this phone. All my apps open and run instantly without any overclock. Do you guys all just play ridiculous high-end games on your phones and therefore want the extra CPU speed? Because that is the only thing I can see benefiting from the overclock...and you are paying for it with battery life. Or are you just hunting for benchmark numbers?
[Verizon Samsung Galaxy S III] nnnnr14:
Everything isn't for every one dude if you don't like it don't criticize other people for wanting more out of their phones.
[Verizon Samsung Galaxy S III] Stupifier:
I'm only trying to find out if I'm missing something. I'm not criticizing anyone. I said "I never really understand why people overclock this phone." I posted because I felt I might not be understanding something....like another reason to overclock. Forgive me if it sounded like I was insulting anyone.
[Verizon Samsung Galaxy S III] oryanh:
No harm done. I think everyone agrees that the phone really doesn't "need" to be over-clocked. Its just the thought of it that's excites us. ...and the exception to the rule is if you can clock higher and still maintain the mV of the previous max clock then not only will battery be unaffected, you can save battery.
[Verizon Samsung Galaxy S III] Stupifier:
That last little nugget of info is exactly why I posted. I would more than gladly overclock if battery life is unaffected.
[Verizon Samsung Galaxy S III] omair2005:
i'm really liking smartassv2/row:good:

i know pegaususq was recc. in another thread.. going to test that later.

ktoonservative

abyssplug

ondemand

smartassv2

pegasusq

all on my test list..
[Verizon Samsung Galaxy S III] luv2increase:
If the phone didn't need to be overclocked, then the need for faster CPUs and GPUs in phones would be non-existent. That is obviously not the case.

Overclocking the GS3 makes a HUGE difference in real-world phone performance. Everything is snappier. There is less lag in CPU intensive apps like the weather channel and Google maps for instance.

I couldn't imagine running this phone at 1.5ghz all the time.
[Verizon Samsung Galaxy S III] prototype7:
For anyone who's interested, I found some info on the row scheduler

https://patchwork.kernel.org/patch/1274761/
[Verizon Samsung Galaxy S III] neyenlives:
Really? I've been doing this for years, I can't tell any difference between a stock and overclocked GS3.
[Verizon Samsung Galaxy S III] AegonTheDragon:
Yeah me neither.
[Verizon Samsung Galaxy S III] masri1987:
plz let us know

as for everyone else

i've been doing this since the OG droid days, and I have ONLY overclocked the OG droid.. never found any benefit overclocking anything else after that.
[Verizon Samsung Galaxy S III] oryanh:
Oh, come now... there's huge benefits... think about it... say you overclock from 1.5GHz to 2.1GHz. that's a 40% increase.

clock for clock, now reduce a typical 6 second task by 40% down to 3.6 seconds. Perform this task 23 times per day for 365 days you've saved a whopping 5.596 hours a year in lag!

not really. but that was fun...
[Verizon Samsung Galaxy S III] stev067:
I've been having trouble keeping my Juice Defender Ultimate running on this kernel (4.2.1 version). It seems to be working with the CM10.1 kernel, though. Any suggestions? The same thing is happening on my nexus 10 too.
[Verizon Samsung Galaxy S III] Stupifier:
You make a lot of assumptions in that statement. It is very unlikely CPU frequency vs Task processing time follows an entirely linear relationship... especially at the outer overclock frequency limits of a device. Also, a 6 second task on this phone..... I've yet to see one.

My point is the following -- even if overclocking does make tasks load faster, the difference is negligible considering this phone already loads today's apps nearly instantly. But hey, if I can safely overclock and keep my prior voltages, I guess I'd do it since there's no battery hit. I'd only be comparing an instant load vs another instant load though :/
[Verizon Samsung Galaxy S III] d1ez3:
I'm having both cpu's stay online with synergy r169. Had this issue with lean kernel too, but not the rom's ziggy kernel. I tried the debugging fix but both cpus still online. Anyone have a different solution? thanks
[Verizon Samsung Galaxy S III] mmalkin:
I use this kernel with the wheatley governor. Seems to work with Synergy 169.
[Verizon Samsung Galaxy S III] Metfanant:
You're making HUGE assumptions that just don't translate into real world performance...not even close

sent from my VZW Galaxy S3 running SynergyROM
[Verizon Samsung Galaxy S III] Neverender326:
Pretty sure he's joking. Lighten up people.
[Verizon Samsung Galaxy S III] tedkord:
You should read all the way to the bottom of his post.

---------- Post added at 09:49 AM ---------- Previous post was at 09:45 AM ----------

Just tried pegasuq with Beans v.9 and the phone would not wake. Had to pull the battery every time the screen timed out. Trying smartass v2 now. (it wakes at least)
[Verizon Samsung Galaxy S III] oryanh:
I should have all caps my "not really"
[Verizon Samsung Galaxy S III] olegfusion:
This is only one kernel I have good stable wifi working with any AOSP ROM in sgs3 vzw.
[Verizon Samsung Galaxy S III] Twisted politiks:
Has anybody else had an issue with their clock speeds locking up in them. I have been running ktoonservative with row/noop using 384min and 1512max. I have it set to throttle down to 384max while screen is off. The problem is that sometimes when I wake my phone, it is really slow. I will go into ktweaker and it will ask if I want to apply my saved min/max settings. Sometimes it works, but sometimes my CPU will be stuck at 96. The only way to fix it is either choosing a different governor, or a reboot. The only thing I can think of would be that I aso have ROM toolbox pro installed, though I haven't messed with the CPU aspect of that app as it doesn't work right. Any help would be greatly appreciated.

P.S. I am running the KT747 January 9th version of this kernel with liquidsmooth jelly bean 4.1.2 RC9

Sent from my SGS III baked with LiquidSmooth RC9
[Verizon Samsung Galaxy S III] dems86:
Really though, why don't people read the entire post first before replying, haha
[Verizon Samsung Galaxy S III] luv2increase:
It has been like this on 4.2. To get around it doing this, make sure "lock frequencies" is checked in general in ktweaker.
[Verizon Samsung Galaxy S III] Eyalkn:
I had this issue and lock frequencies didn't help. my issue was caused by a script inside the Rom (init.d) that was using mpdecision. Disable mpdecision and see it will happen again. Disable it by opening Terminal Emulator from the market and then type su (Then press enter) then in the new line type stop mpdecision (Then press enter).
[Verizon Samsung Galaxy S III] jamesd1085:
Just use a root browser like root explorer or something similar and navigate to system/etc/init.d and delete the tweak file or files causing you issues
[Verizon Samsung Galaxy S III] awmobjects:
Had to remove kernel was experiencing intermittent reboots
[Verizon Samsung Galaxy S III] SubliminalME:
4500 Quadrant. Not too shabby! My N7 is running round 6500, so not bad for missing 2 cores and a slower gpu. :)
[Verizon Samsung Galaxy S III] Josolanes:
No sods here with min set to 96 (confirmed dropping to 96 regularly with KTweaker)

Sent from my UNLOCKED ;) Verizon Galaxy S3
[Verizon Samsung Galaxy S III] codyvance:
Same here.. No SODs
[Verizon Samsung Galaxy S III] Haro912:
Strange thanks for the replies

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] mustbepbs:
This works with paranoid doesn't it?
[Verizon Samsung Galaxy S III] SubliminalME:
Definitely
[Verizon Samsung Galaxy S III] ktoonsez:
To anyone having SOD's at anything lower than stock (384 mhz), that means your phone can handle the underclock so you will be fine if you just dont UC.
[Verizon Samsung Galaxy S III] Haro912:
Ook. Running fine today at 192 thanks for the heads up. Would turning the voltage up help at all? Kinda defeats the purpose st the point though. :silly:

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] ktoonsez:
You want to find the lowest Mhz and lowest voltage that your phone will handle, so find the mhz that doesnt create any reboots, then start lowering voltage untill you have issues again, then bump it back up to the last known good voltage. Mine runs good at 192Mhz at 875 volts, any lower I get reboots during calls.
[Verizon Samsung Galaxy S III] Haro912:
Alright thanks for the help. New to kernel changes like that. Only ever messed with speed and governors.

Sent from a strange blue box hurtling through time and space.
[Verizon Samsung Galaxy S III] drbveb88:
Works beautifully!!!
[Verizon Samsung Galaxy S III] juancaperez2000:
Mine accept 96mhz at 845 volts using scary governor and i/o BFQ, amazing kernel, will see what you have in the future for us lol :P
[Verizon Samsung Galaxy S III] ali87va:
I'm having an issue with running this kernel with the aokp rom, boot loops and then freezes, doesn't matter if I do clean or dirty flash.....
[Verizon Samsung Galaxy S III] juancaperez2000:
which AOKP are you running xoomdev or BMC, also which release (date), im on BMC one no problems, reported here, i also tried with CM10 no problems neither
[Verizon Samsung Galaxy S III] ali87va:
8/26 build BMC.... I'm wiping dalvik and cache. I can't even install the latest 8/29 because it has this kernel implemented.
[Verizon Samsung Galaxy S III] juancaperez2000:
thats a really weird issue i never heard something like this, which recovery are you using, im on CWM 6.0.2 touch
[Verizon Samsung Galaxy S III] masri1987:
What's the governor and scheduler everyone running?
[Verizon Samsung Galaxy S III] ktoonsez:
If its the BMC I think you are talking about, he is using my kernel in the ROM already.
[Verizon Samsung Galaxy S III] ali87va:
I'm using cwm v 6.0.1.2

---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------

Yea that's what I'm saying, no offense to you but your kernel and my phone aren't seem to be liking each other lol.
[Verizon Samsung Galaxy S III] Twisted politiks:
I have tried both locking frequencies and

not, as that was my first guess.

I will give this a try and report back tomorrow with my results. Thanks form the quick reply :)

Sent from my SGS III baked with LiquidSmooth RC9
[Verizon Samsung Galaxy S III] luv2increase:
I tried this and it kept going to 1512mhz as my highest frequency, and I couldn't get 2106mhz to stick. Just went back to lock frequency and all is better again.
[Verizon Samsung Galaxy S III] airmaxx23:
So I installed a different kernel and still have the KTweaker and can't uninstall it, how do I remove it?

Edit: I just removed it from system/app.
[Verizon Samsung Galaxy S III] luv2increase:
Titanium backup
[Verizon Samsung Galaxy S III] Twisted politiks:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

This seems to have worked with no negative side effects.

On a side note, can somebody tell me what mpdecision is used for?

Sent from my SGS III baked with LiquidSmooth RC9
[Verizon Samsung Galaxy S III] stev067:
I switched from CM10.1 to liquidsmooth, and that fixed my Juice Defender issues. Now I'm getting audio crackling, which I'm certain is being caused by my voltages. I'm confused why the stock voltages would be too low though.. :confused:
[Verizon Samsung Galaxy S III] dems86:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Audio crackling sounds like a 4.2.1 issue, not a voltage issue.
[Verizon Samsung Galaxy S III] stev067:
My quick fix has been to raise the minimum frequency to 594. At that speed, the crackling is 100% eliminated. I just assumed I had the voltages too low for the steps below that, but idk...
[Verizon Samsung Galaxy S III] LinkinParkmetre:
Sorry for noob question, I searched the thread but couldn't find my answer.

Can I flash this on top of Slim Bean RC 1 ?

If yes, are there any special instructions?

Thanks a lot
[Verizon Samsung Galaxy S III] masri1987:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

If slim bean is AOSP then pick you're aosp version from kernel selection.
[Verizon Samsung Galaxy S III] luv2increase:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

FYI masri, slim is AOSP and 4.2.1 now.

ktoonz, you make the best kernels. Will you please build a newer kernel with the latest Linux kernel 3.0.59 and latest Linaro as well as the latest fixes?

I only use your kernels. I know my Verizon GS3 runs the best with only your kernels! Your kernels and Liquid ROM or mastamoon's CM10.1 unofficial builds are the best mix for performance, features and reliability.

I'd settle for no less.
[Verizon Samsung Galaxy S III] PsiPhiDan:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

I'm running ktoonz with the latest liquid smooth (beta 3). What suggestions do other 4.2 users have for optimizing battery life while not limiting performance of the ROM?

I'm currently using the ktoonservative governor with cfq scheduler, no profiles or voltage changes. I would like to see better battery life for sure.
[Verizon Samsung Galaxy S III] mbc663:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Http://xdaforums.comhtshowthread.php?t=2032956

[Team Kernelizers] {how to} JB and TPR roms
[Verizon Samsung Galaxy S III] PsiPhiDan:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

The link appears to be broken?
[Verizon Samsung Galaxy S III] Kelton Rivas:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

I second the broken link
[Verizon Samsung Galaxy S III] helobubba88:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Link works for me in Tapatalk.

Sent from my SGSIII
[Verizon Samsung Galaxy S III] prototype7:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Fixed the link (hopefully), not sure why it worked for me on Tapatalk...
[Verizon Samsung Galaxy S III] ktoonsez:
Im out of town for work, once i get off this crazy travel schedule and 18 hour work days I will update.
[Verizon Samsung Galaxy S III] stev067:
Just wanted to follow up on this, as I know it will be helpful for at least one person:

I had been using the stock voltages from the OP, because I just assumed that would be the most conservative approach for stability, (and I'm SO bad with the voltage sliders). As I said in my previous post, I was able to eliminate the audio snap/crackle/popping by raising the lower frequency limit to above 384. Tonight I tried re-lowering the frequency limit, and upping the low end voltages one at a time. The settings listed below are the lowest voltages that eliminate all but the occasional rice krispies sound on my device.

Stock_______________________My voltages

Mhz - mV_____________________Mhz - mV

384 - 925_____________________384 - 920

192 - 900_____________________192 - 915

144 - ???_____________________144 - 915

96 - ???_____________________ 96 - 915

As a side note, my device no longer freezes up while sleeping at 96MHz (ktoonservative).

:good: Edit: Wrong quote =)
[Verizon Samsung Galaxy S III] oriax123:
Hey guys alittle help here, Im running Cleanrom 5.6 and flashed the TW kernel then wiped cache, dalvik and fixed permissions but when it boots up it freezes then goes into a hotbootloop . Is there something I did wrong or know a fix? Thanks in advance!
[Verizon Samsung Galaxy S III] Schaweet:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

If running ktoonservative did you ensure you renamed qosmgr to qosmgr.bak as stated in the Op? You should get solid battery life after that.

Sent from my SGS3
[Verizon Samsung Galaxy S III] Twisted politiks:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Does this apply for people running 4.1.2 ROMs with ktoonservative?

Sent from my SGS III baked with LiquidSmooth RC9
[Verizon Samsung Galaxy S III] gsarnold:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Would assume not because OP only specifies that requirement for TW ROMs and I don't think TW is available in 4.2.1 yet. (is it?) . I just looked and I don't even have that file on my phone with cm10.1.
[Verizon Samsung Galaxy S III] osuron07:
Anyone having issue with bluetooth getting stuck when turning off? It turns on fine, audio was great through my headset, but when I went to disable bluetooth, it's just stuck at "Bluetooth is turning off.."
[Verizon Samsung Galaxy S III] Twisted politiks:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Thanks for the quick reply. I probably read that in the OP and forgotten it already. Sorry for the question that already had an answer :/.

Sent from my SGS III baked with LiquidSmooth RC9
[Verizon Samsung Galaxy S III] odub303:
Re: [KERNEL][VERIZON][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweak

Force close Bluetooth Share as a workaround for now.

Sent from my SCH-I535