yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] macpro88:
kjndvasfnawoienfcla

too early.

lesson learned.

back into recovery.

must have been stuck back in my Moto device days haha

thanks guys, thank you so much!

:victory:
[Verizon Samsung Galaxy S III] luis86dr:
Happens to the best of us lol. Glad you figured it out.
[Verizon Samsung Galaxy S III] tprophit:
So had a reboot, first in weeks....using the additional -25 UV discussed yesterday. Happened while simultaneously downloading an app update from play store and receiving a SMS. What was weird is, after reboot, my settings, battery stats were all off. Time off battery, talk time, screen on time were all understated.

Thoughts?

Thank you.
[Verizon Samsung Galaxy S III] mw86:
Go back to where you were +25mv back. Just charge your battery all the way to full and unplug and your battery stats are fixed, Task650 taught me there is no need for wiping battery stats or bothering with any other sort of fix. Charge full and you are fixed. How did that call time work out with a lower screen off max?
[Verizon Samsung Galaxy S III] fawkiPhone:
Was the /system/bin/gosmgr rename fixed withbtheblast build? 4/11. I'm not seeing it with es file manager
[Verizon Samsung Galaxy S III] tprophit:
Thanks, will do. Seemed to work out well, no issues with actual calls. Part of time I was on old screen off MHz, with it disabled during calls, and part of the time I was on the additional -25, so not a full comparison. Will keep posted.
[Verizon Samsung Galaxy S III] Androideka5:
Ok, if anybody has a solution I'd be eternally grateful, because this is starting to piss me off. I really want AOKP, but I need KT747. But each time I flash AOKP (the latest milestone and the last couple builds) and then flash the kernel in the latest TWRP, it boots up but the screen will not turn on. I'll get notifications and the soft keys light up but no screen. I even tried both 4/11 and 4/19, same effect >.<
[Verizon Samsung Galaxy S III] Recon0212:
+1

Having the exact same issue.
[Verizon Samsung Galaxy S III] Addiso:
Nevermind.
[Verizon Samsung Galaxy S III] juancaperez2000:
i running Millestone 1 with ktoonz 4/11 with out issues then try AOKP nightly with 04/19 (because is the ones that is supposed to flash) and boot perfect

PS: i move back to Millestone because battery drain but others than that is running perfect)
[Verizon Samsung Galaxy S III] Recon0212:
Did Milestone 1 work with 4/19 for you?
[Verizon Samsung Galaxy S III] juancaperez2000:
no, because version 04/19 got the lates CM commints so only roms that was created after 04/19 can use it, thats why only works on the latest AOKP official nightly
[Verizon Samsung Galaxy S III] Androideka5:
Milestone 1 or MR1 Milestone 1?
[Verizon Samsung Galaxy S III] juancaperez2000:
MR1 Milestone 1
[Verizon Samsung Galaxy S III] gseyffert:
Seems this kernel becomes very unstable when OC'd to 1809, I had hot reboots like no one's business. Moved it down to 1674 and runnin' smoothly! For what it's worth, I'm running the 4/20 build of LiquidSmooth.
[Verizon Samsung Galaxy S III] tihsllub:
That's sad. I can get mine to run all day at 1809.

Sent from my.........
[Verizon Samsung Galaxy S III] brandoncarlson33:
me too no probs on 1809 or 1890 i had it on row and performance while i had it set to both:laugh:
[Verizon Samsung Galaxy S III] masri1987:
What's everyone's setup on latest AOSP?

Does smartassh3 get stuck on max MHz?
[Verizon Samsung Galaxy S III] axne1:
This is true! I am Able to OC to 1700. 1800 sent my device into a rage reboot cycle... Liquid 4/20 + KT 4/19... Man I wish I could go ham and crank it up in the 2100's :)

EC Nationals

Wisconsin State Champs 2012
[Verizon Samsung Galaxy S III] masri1987:
If anyone is able to get smartassh3 stable lemme know
[Verizon Samsung Galaxy S III] tihsllub:
Ktoonservative cfq 189-1026

Sent from my.........
[Verizon Samsung Galaxy S III] DroidHam:
Tried both aosp versions on parakangdroid and neither will boot??!?!
[Verizon Samsung Galaxy S III] mw86:
Sounds like you overheated. Performance gov is not good for over clock values like that. If you hit 100c for split sec thats why it **** off to prevent hardware failure. If you were plugged in or had 3g in use for extended period of time it likely raised or battery temp to 34-37C and cpu too high

which is often not reached as easilt unplugged and under extended internet use even unplugged can bring battery that high. If cpu under full load like Antutu if you did more than one run you could end up reaching thermal shutdown just the same even unplugged. I strongly advise you to keep track of temps in realtime when deciding how to set an overclock.

Another suggestion is make sure your thermal protection is working as that would also help prevent this some... In Extras Thermal Control
[Verizon Samsung Galaxy S III] gseyffert:
Oh well that makes sense! Especially since I use an otterbox defender case. Would of been nice to have the feature on my phone in January... I burnt out my first S3 over clocking to 1890!!
[Verizon Samsung Galaxy S III] mw86:
Looking at your battery stats looks like the second changes had better battery life as its not as steep a curve towards the end of that run.
[Verizon Samsung Galaxy S III] DroidHam:
Actually all 3 AOSP versions won't boot on ParaKANGdroid

Isn't that an AOSP ROM? What's the problem?
[Verizon Samsung Galaxy S III] tprophit:
Yes, but also I had more calls late in that run too. But, the reboot this morning talked me into reverting back to -50 UV.

Thank you.
[Verizon Samsung Galaxy S III] Androideka5:
Mine won't boot in latest CM 10.1 or AOKP, I can't figure it out. It's making me really mad
[Verizon Samsung Galaxy S III] ktoonsez:
You need to use my 4/19 release to use newest CM10.1 and AOKP
[Verizon Samsung Galaxy S III] masri1987:
yo ktoons wassup with smartassh3, is it messed up? seems to stay stuck on max, but only after i exist the ktweaker app,
[Verizon Samsung Galaxy S III] ktoonsez:
Yes, still is, nobody has worked on settings to try and tame it, I already spent hours and got sick of it since my gov is the best anyway, lol. :p ;) :victory: :silly: :cool:
[Verizon Samsung Galaxy S III] brandoncarlson33:
My batt results with the 4/19 kernel and 4/20 liquid ROM with kernelizers pegusisq-zen.bin mod

Just thought I would throw this out there thanks for an awesome kernel!
[Verizon Samsung Galaxy S III] ktoonsez:
Excellent, wanna see something INSANE!!!!!!!!!!!! Go here, this is no joke:

http://xdaforums.com/showpost.php?p=40640316&postcount=4132
[Verizon Samsung Galaxy S III] NightxFall:
My level of do want is so high right now.
[Verizon Samsung Galaxy S III] Androideka5:
Perhaps I'm being a huge noob, who knows, but is not called KT747-AOSP-JB-MR1-3.4-VZW-04-19-2013.zip?
[Verizon Samsung Galaxy S III] masri1987:
wtf, i never get battery results like those, it's been a while.
[Verizon Samsung Galaxy S III] brandoncarlson33:
thats awesome!!!!

---------- Post added at 12:22 AM ---------- Previous post was at 12:00 AM ----------

i tried to find the peoples rom for i535 seems to be non existent
[Verizon Samsung Galaxy S III] Addiso:
Someone can't look through android development lol

But I'm feeling nice so here ya go

http://xdaforums.com/showthread.php?p=39977014
[Verizon Samsung Galaxy S III] brandoncarlson33:
thanks man prob didn't find it cause its not 4.2.2 and tw at that don't care for tw but thanks again
[Verizon Samsung Galaxy S III] ddurandSGS3:
psh, thats nothin ktoonz

here you go.

beans rom, your kernel from a few months ago.

best battery life i ever got.

i am running a 2200 mah batter. i took the screenshot with 5% left for that reason.
[Verizon Samsung Galaxy S III] ktoonsez:
Excellent!!!!!!!!!!!!! :good: :highfive:
[Verizon Samsung Galaxy S III] TheDriller:
Oh no, we got it. Its a port though

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] tprophit:
Here's the latest. Keep in mind, I spent about an hour in a weak signal area, which drained about 15% of the battery, and, was asleep for 7 hours, so not using phone. Still, much improved ...

Apparently image uploading not working ..
[Verizon Samsung Galaxy S III] masri1987:
Decimalman fixed asswax to work Properly..

http://xdaforums.com/showthread.php?t=2226894
[Verizon Samsung Galaxy S III] Äptiva:
So just a question. I've been running KT747 for the Cricket S3 for a few weeks now. Loving it and so do the rest of the guys with Cricket S3. I've noticed something though.

On TW roms with stock and OC kernels, most games play great. GTAVC for example. However on AOSP roms, they don't play for crap. Again GTAVC... I'm just wondering if this has something to do with Freedreno drivers being used now and if anyone with d2vzw versions have experienced this too? I'm just trying to see if it's something to do with CM kernel source mainly or if possibly something with KT747.

Great job KT. We Cricket guys love this kernel something serious

Sent from my Kanged 1.8GHz Cricket S3
[Verizon Samsung Galaxy S III] Neverendingxsin:
Bad signal will do that to you
[Verizon Samsung Galaxy S III] ktoonsez:
Absolutely, I was stuck in goobersville PA for a job a few months back and I lost between 10-12% an hour all day everyday :(
[Verizon Samsung Galaxy S III] luis86dr:
Yeah, network signal plays a huge roll when it comes to battery life. Makes me jealous of TMO and Sprints network, as they aren't as power hungry as ATTs and Verizons LTE 4g networks.

Guess it's the price we pay for fast data speeds.
[Verizon Samsung Galaxy S III] Droid316:
Should probably erase or black out your phone number.

[©Sent from my Samsung Galaxy S3 Verizon 4G LTE Powered by ZeroLemon 7000mah Extended Battery!!©]
[Verizon Samsung Galaxy S III] tihsllub:
I'm working on a job right under a cell tower. So I'm too close to it to get a signal from it. On top of that I am pretty triangulated with 2 other towers. So I hop from 3g to nothing all day and between the two other cell towers. It kills my battery. 8 hours and down to 23%. I have decided to start turning off the radio when I'm at this job.

Sent from my.........
[Verizon Samsung Galaxy S III] STLRamsFan1k:
So far so good. Installed on CleanRom 6. Was not getting any boot animation because of my previous custom boot animation install so I flashed the bootanimation4U mod and it came right up.
[Verizon Samsung Galaxy S III] m-cat:
Quick question, I am on a 4.2.2 Rom that currently has a 3.0 kernel. Can I flash a 3.4 kernel and be ok?
[Verizon Samsung Galaxy S III] TheDriller:
Short answer is no

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] PoLoMoTo:
Well he can flash it all he wants, whether it boots or not is a different story XD
[Verizon Samsung Galaxy S III] TheDriller:
Lol... True story

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] m-cat:
I ask because I tried it with another kernel and caused my device to brick. I wasn't sure if it was the fact that it was a 3.4 kernel or that there was something wrong with the DL.
[Verizon Samsung Galaxy S III] Androideka5:
Even if you have a 3.4 Rom it won't work if it's not new enough. For example the AOKP MR1 Milestone won't work with the KT 4/19 release
[Verizon Samsung Galaxy S III] m-cat:
So is there some guide for people like me that didn't realize there were compatibility issues? Because going through the unbricking process really sucks. Haha
[Verizon Samsung Galaxy S III] zeus33:
Basics:

3.0 and 3.4 kernels are not interchangeable. A 3.0 ROM needs a 3.0 kernel and vice versa.

Also, there were some changes on 4-19, so ROMs from before that date have to use a kernel from before that date and ROMs from after that date need a kernel from after.
[Verizon Samsung Galaxy S III] brandoncarlson33:
Always read your threads, (it helps)
[Verizon Samsung Galaxy S III] Addiso:
It's pretty much in every rom and kernel thread, your not that special to receive a guide do your research you made the effort to root and mod your device, now give the effort to do your thing.
[Verizon Samsung Galaxy S III] DvdOwens:
Compatible with AOKP latest nightlies ?

I'm about to flash a AOKP Unofficial nightly ( 4/26) is the 4/19 kernel compatible ?
[Verizon Samsung Galaxy S III] ktoonsez:
Yes
[Verizon Samsung Galaxy S III] DvdOwens:
Thanks big dog.

Your 4/11 release of Carbon 4/20 worked well. I can't wait to report back with more great news.
[Verizon Samsung Galaxy S III] axne1:
I used to swear by Franco's Kernel. Now I swear by this one! Well done!
[Verizon Samsung Galaxy S III] jamesino:
Is there a place where I can download the latest v3.4 version before the 4/19 update?
[Verizon Samsung Galaxy S III] ktoonsez:
Change Log 4.26.2013

1. BRAND NEW BOOT SPLASH IMAGE THANKS TO TASK650

2. Linux 3.4.42

3. A few updates from CM so its up to date

4. Fixed issue with KTweaker not setting lower temps on KThermal screen

5. Thats about it.........

ENJOY :good:
[Verizon Samsung Galaxy S III] mike216:
Insane kernel as usual! Love the boot screen. I'm definitely a believer!
[Verizon Samsung Galaxy S III] tbgreen89:
What are you guys all using for Governor and Scheduler to get the best all around performance and battery life, that's stable?
[Verizon Samsung Galaxy S III] masri1987:
nice ktoons, had a feeling something was about to drop. and i agree with the post above, been having a hard time finding a good combo lately
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks guys, you can always find my latest settings in Post #3 in my ATT thread, here:

http://xdaforums.com/showpost.php?p=28399842&postcount=3
[Verizon Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 4.27.2013

1. BRAND NEW BOOT SPLASH IMAGE THANKS TO TASK650

2. Linux 3.4.42

3. A few updates from CM so its up to date

4. Fixed issue with KTweaker not setting lower temps on KThermal screen

5. Fixed asswax thanks for implementation DecimalMan

6. Fixed smartassH3

7. Thats about it.........

ENJOY :good:
[Verizon Samsung Galaxy S III] masri1987:
Wow double update
[Verizon Samsung Galaxy S III] ktoonsez:
Yep, 2nd was for all the guys wanting those 2 govs working :D :good:
[Verizon Samsung Galaxy S III] unboostedzc:
getting a solid backlit black screen and hang right after new kt boot logo in both 4/26 & 27 builds. flashing back to 4/10 resolves the issue. running paranoidkangdroid 2.32 with 3.4 kernel
[Verizon Samsung Galaxy S III] ktoonsez:
Yep, thats normal when your on a really OLD ROM. You need to be on a ROM with the CM patches from 4/19
[Verizon Samsung Galaxy S III] unboostedzc:
cool thanks kt. were there any releases between 4/11 and 4/26 I missed?
[Verizon Samsung Galaxy S III] TheDriller:
TW updated yet?

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] ktoonsez:
Nevermind, wrong thread.
[Verizon Samsung Galaxy S III] m-cat:
Not so much, nothing against our awesome Ktoonzes, but while he has a section for 3.0 and 3.4 it's not really explained that the release date of your Rom dictates the kernel used.

Anyways not trying to start an argument on the thread, I just needed clarity that many OP did not give. I would daresay that I'm not the only experienced android user to not understand these compatibility issues.

Again thank you ktoonz for you work and your constant updates!!! You and your kernel are AWESOME!
[Verizon Samsung Galaxy S III] TheDriller:
Huh?:confused:

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] Hybridnoob:
I think a lot of people get upset because they spent a decent amount of time reading this thread to learn what you are asking for. Reading 10 or so pages back would probably answer most, if not all of your questions.
[Verizon Samsung Galaxy S III] ktoonsez:
I thought I was on the Sprint thread. Only new thing I got for TW is MD4 for Sprint, if you want I can compile for Verizon and u can try? Not sure it will work, but hopefully it will.
[Verizon Samsung Galaxy S III] TheDriller:
Most definitely sir. I am your test bunny lol

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] m-cat:
I guess I didn't make it back that far in the thread in my quest for answers.
[Verizon Samsung Galaxy S III] ktoonsez:
Building and will send you a link in a PM :good:
[Verizon Samsung Galaxy S III] ktoonsez:
PM with test kernel sent about an hour ago, hope everything is going good.
[Verizon Samsung Galaxy S III] jamesino:
I don't think m-cat did anything wrong. While we may be following the development thread closely and have made notes of where certain crucial posts lay, for someone who is just trying this kernel out for the first time, it's not immediately obvious that they need to go x pages back in order to find this information.

Many people in other threads have also fallen victim to the same miscommunication. Again it wasn't explicitly obvious that CM modified their code for the 4/19 releases, especially for someone who may not be as technologically competent as yourselves.
[Verizon Samsung Galaxy S III] brandoncarlson33:
Love the new splash screen another awesome update KT keep kickin a**
[Verizon Samsung Galaxy S III] zeus33:
There is one from 4/19 (that includes the changes), but that won't work with your ROM either unless you upgrade to a ROM from the 19th or newer. If you do upgrade to a ROM from the 19th or newer, you can use the newer kernels, 4/19, 4/26, etc.
[Verizon Samsung Galaxy S III] Prowelder:
So I did a clean install with the new kernel on slim bean and now there is no ktweaker app. Maybe I missed something but I wiped and fixed permissions. I even went into root explorer and extracted and installed the ktweaker apk and still won't show up in app drawer. Any ideas what I might have done wrong ?

Wow. So never mind everyone. Forgot to enable it through app manager again. All is well. Thanks ktoonsez for the best kernel around!!
[Verizon Samsung Galaxy S III] mike216:
Amazing colors and speed on the current release and yesterday's nightly from liquid! You certainly have gotten the Colors to look cool without adding to much blue. It's always GREATLY APPRECIATED when seeing how the colors were originally after flashing a rom.
[Verizon Samsung Galaxy S III] soapinmouth:
Are you planning on still updating your 3.0 kernel? Carbon rom is back to 3.0 and you seemed to be the only one maintaining a 3.0 kernel.
[Verizon Samsung Galaxy S III] axne1:
Mike I couldn't have said it better myself. The colors are perfect! Ktoonz thanks for the link to your personal settings. I'm getting great performance, stability, and battery. :D
[Verizon Samsung Galaxy S III] Azuma73:
Link me please!?!? Thanks!!
[Verizon Samsung Galaxy S III] mbc663:
From his AT&T thread
[Verizon Samsung Galaxy S III] jamesino:
Would the phone run smoother if for regular navigation through the UI, the CPU was at 1134 Mhz, the clock rate that Project Butter was designed to use? Or would the phone be smoother if it ran at a higher clock rate such as the max stock rate of 1512 Mhz?
[Verizon Samsung Galaxy S III] mbc663:
Everyone's phone is different. What do u have to lose by trying exactly?
[Verizon Samsung Galaxy S III] ktoonsez:
Anyone want to test this test build I made with MD4 updates in it for Touchwiz????? You must know enough to get your self out of a jam in case it boot loops and or doesnt boot at all.
[Verizon Samsung Galaxy S III] jamesino:
Well I don't exactly know how to set it up. I noticed that when I flashed the newest KT 4/27 onto 4/27 Carbon, it uses the 1134 Mhz state for navigating through the UI. But when I flashed the same KT 4/27 onto the 4/20 Carbon, it uses only the max 1512 state for navigating through the UI.

If I want to use the 1134 Mhz for navigating the UI while on the 4/20 Carbon, the only thing I can think of would be to lower my max clock rate to 1134, which will have negative performance consequences when I am doing something that is more intensive than just navigating through the UI.

Both times, the phone was on Interactive/Row. I suppose the latter situation is more in line with what Interactive is supposed to do right? Jump up to Max frequency and jump back to Min again after the timer runs out.
[Verizon Samsung Galaxy S III] droidhunger:
Deleted, asked a dumb question which was answered few pages back, sorry for the mistake
[Verizon Samsung Galaxy S III] phillysdon04:
I just flashed this on my Verizon S3 running CM10.1 4/27 nightly. I haven't had any problems so thanks for your hard work!
[Verizon Samsung Galaxy S III] Addiso:
I'll give it a whirl.
[Verizon Samsung Galaxy S III] burbank:
I must be missing something. The OP advertises a 4-27 version of this awesome kernel. But the download links download a 4-11 version. Can someone point me to the 4-27 version?

(I'm running 'Jelly Beans' Build 15 on an SIII)
[Verizon Samsung Galaxy S III] prototype7:
http://xdaforums.com/showthread.php?p=40760863
[Verizon Samsung Galaxy S III] countryfolk07:
That's AOSP. he's on TW. Beans build 15
[Verizon Samsung Galaxy S III] ktoonsez:
PM sent
[Verizon Samsung Galaxy S III] prototype7:
Missed that, sorry. The AOSP kernel is getting more frequent updates, 4-11 is the latest TW version apart from this test build afaik
[Verizon Samsung Galaxy S III] burbank:
Yes please.
[Verizon Samsung Galaxy S III] ktoonsez:
PM sent, hopefully someone will get back to me
[Verizon Samsung Galaxy S III] countryfolk07:
I'll give it a whirl. Please. Running your 4/11 now
[Verizon Samsung Galaxy S III] goblue13579:
Boots blank screen on 3.4 based kernels

I have tried the KT747 3.4 builds for as long as they've been coming out, and every time it shows the samsung bootloader flash, then the kernel splash, and then just stays blank. Do I need to do more than a cache/dalvik wipe to get on 3.4? Does it matter that I have one of the first round of s3s made? Any help would be appreciated, thanks.
[Verizon Samsung Galaxy S III] Addiso:
Running smoothly :beer:
[Verizon Samsung Galaxy S III] ktoonsez:
Finally got a hold of someone and it is working great so dont need anymore testing, it is full 4.1.2 with MD4 from Sammy's latest code update and working like a champ according to luis86dr
[Verizon Samsung Galaxy S III] ktoonsez:
You need to do a factory reset and format /system for good measure.
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks for the feedback :highfive: :good:
[Verizon Samsung Galaxy S III] luis86dr:
Definitely running great, booted up fine. My Ktoonservative / Row backup restored fine with all my adjustments. Running smooth as always. :good: :highfive:
[Verizon Samsung Galaxy S III] Addiso:
Running that as well on the test one :thumbup:
[Verizon Samsung Galaxy S III] pimpmaneaton:
Will you be posting this updated version or just through pm atm. If only through pm I would like to give it a run.
[Verizon Samsung Galaxy S III] ktoonsez:
Here you go guys :D :good: :highfive:

http://www.mediafire.com/download.php?1c8wd2llay8sai9
[Verizon Samsung Galaxy S III] Droid316:
Changes please :) :) :)

[©Sent from my Samsung Galaxy S3 Verizon 4G LTE Powered by ZeroLemon 7000mah Extended Battery!!©]
[Verizon Samsung Galaxy S III] Droid316:
My battery stats using 4-11 kernel TW on zerolemon 7000mah

[©Sent from my Samsung Galaxy S3 Verizon 4G LTE Powered by ZeroLemon 7000mah Extended Battery!!©]
[Verizon Samsung Galaxy S III] ktoonsez:
Change Log 4.28.2013

MD4 update that include:

1. Camera

2. Display drivers for UI

3. Memory functions

4. Wireless

5. USB

6. Video drivers for video playback

7. mmc/block/ssd

8. Sound drivers
[Verizon Samsung Galaxy S III] Droid316:
This can be flashed on a non md4 Rom then?

[©Sent from my Samsung Galaxy S3 Verizon 4G LTE Powered by ZeroLemon 7000mah Extended Battery!!©]
[Verizon Samsung Galaxy S III] ktoonsez:
Yes, that how I made it and thats what the testing was for.
[Verizon Samsung Galaxy S III] Droid316:
Thank you sir

[©Sent from my Samsung Galaxy S3 Verizon 4G LTE Powered by ZeroLemon 7000mah Extended Battery!!©]
[Verizon Samsung Galaxy S III] thornev:
What is an "MD4" ROM? IS that as in VRBMD4, a leak from VZW?
[Verizon Samsung Galaxy S III] countryfolk07:
It's a sprint official/port for VZW. :thumbup:
[Verizon Samsung Galaxy S III] JLow0214:
So been using this kernel since I got my s3 but now that I'm running 3.4 aosp kernel my phone locks up when I try to oc past 1809 I used to be able to run 2109 with no problems. Anyone experiencing this or know of a way I could possibly fix this? I want my phone to be lightning fast again

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2