yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It'd a sporatic issue. I have a build of 3.46 I'm running right now but I gotta wait to release it until I get back from work. Anybody here a workplace lawyer or wants to help me file some discrimination?!

3.46 is running pretty nicely though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
https://plus.google.com/117962666888533781522/posts/XjY8QuGEinY Felt like this was going to be a problem. I want my LTE!.. clean flash back to an old build or something? Restored a backup and it won't come back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Will the FC some people are experiencing at first boot be resolved?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
What happened at work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
I'm not a lawyer, but I'm sure you won't have trouble finding one for that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Can anyone comment on the quality of this battery.

http://www.ebay.ca/itm/Samsung-Galaxy-S3-SIII-i9300-Replacement-Extended-Battery-4200-mAh-W-Back-Case-/380843590257?pt=US_Cell_Phone_PDA_Batteries&hash=item58ac0c0271&_uhb=1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Ok I need to find out how to do a dirty flash apparently. If I want to go from 3.4 to 3.45. Can someone explain this process? Please. All I've ever done is comepletely clean installs hoping for the best results going this route. The phone app crashing is the first time I've ever had a problem flashing the Quantum rom. Anyway if someone could give me an idea as to how to do a dirty flash I'd appreciate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Do a clean, complete install of 3.4 with gapps and all. Then flash 3.45 and gapps with only wiping cache and dalvik. I went completely dirty, just flashed everything without wipes....lol...running perfectly here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
Pretty straightforward. I go to recovery, install, wipe cache/dalvik, reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Wow, I'm stunned at this. I've gone down 23% in less than 2 hours with 14 min of screen on, and WiFi turned off. I have no idea what's going on. Several reboots, turning on airplane mode and taking out battery did nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Unless there is no case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Thanks guys flashed 3.45 dirty and everything thus far is running perfectly. Of course I'm not driving the 30 miles or so to the nearest area with LTE until tomorrow will test it then. Again thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
FWIW, I'm 10 hours into my 12 hour tour of duty (shift) at the lovely Hines VA IT Center and I've had solid LTE all day on 3.45.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnknownTroll1:
Someone please help me out here? Why do I periodically lose my cellular connection? Also I can't seem to get LTE even though I have great coverage where I live.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
+1 same here. it started happening after I tried the LTE toggle and now sometimes even though it's showing signal I can't call anyone, it goes through and says "can't reach the person at this time". I did a clean install again and didn't mess with the toggle and that seems to have fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnknownTroll1:
So are you referring to the quick tile toggle? I mean I get LTE sometimes but very rare.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swimguy14:
To the people above me , are you sure you have the latest bootloader/baseband version?

sent from my pimpin gs3 running slim kat w/ktoonz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Ok for me I lose connection regardless either in LTE, WCDMA or GSM. Every so often I would drop and and it would go to H+ or 3G or E back to LTE and does that cycle all day.

If I set up the phone to use only GSM (E) it's probably the most stable. but even then after 20-30mins it will drop and try to re-connect.

I am on MJB baseband. I am in Los Angeles so I rarely get this type of coverage unless I am in the mountains or underground parking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Yeah the quick settings toggle but really that just means I didn't mess with any of the network settings and I think it's okay now. Maybe switch your APN? Shot in the dark but the phone might've switched to a weird one after flashing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] UnknownTroll1:
I have no idea...Never messed with any of that stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
I'm on mg2, same as pwn from what I understand. I don't want to update though to mjb or whatever it's called because then I can't use the flashable stock restore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
NOBODY EVER FLASH TO MJB YOU ARE LOSING IF YOU FLASH TO IT FROM MG2 OR ANYTHING ELSE!!!!!!!!

Flashing from 3.36 to 3.45 very excited.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Also, mine went back to dropping in and out of signal and being weird with outgoing calls
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sewermike:
can you please make the text bigger... :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
MJ2 bootloader, MJB modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sewermike:
This is to accompany Berrymans previous post...

CANADIANS REMEMBER.....

THE SAME THING APPLIES AS ABOVE IF YOU FLASH TO THE MK5 BOOTLOADER.

YOU CANNOT ROLL BACK TO MF1 !!!!!

:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LiquidT:
Hey pwn.

I sent you a question via pm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allrockedout:
This is a cm issue eventually will be fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shirsch:
Steve Spencer sent in a commit for LTE that CM approved and merged. Hopefully that will clear up some of the problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
I have lots of fc issues with camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Reboot when that happens. It's getting hung up, should be fixed soonish.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Got back into recovery, and i'm running rom3.4, kernel 2/19. That was a close call. Thought i bricked it for sure.:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
The only times you can actually brick it are when you remove battery while flashing or flash a wrong ROM (not for galaxy s3) or when you toss your phone into fire. Or if you use it to hurt cats. Definitely.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Spraying your phone with water/acid will also do that, or if you use it as a baseball might brick it too xP

Sent from my Quantum-powered SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
I think using it as a wheel chalk would qualify as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
LTE issue fixed on 3.45 with 2/22 kernel! Thanks Pwn that was driving me bananas.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
This is unrelated but how do you get group messaging to work? Everyone's messages are just being sent as a separate text to me instead of within the group. I think I'm just being dumb but if anyone that has it working could just pm me that'd be cool, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
SMS app settings > Group messaging
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] |flyte|:
Not for me.

Cleaned flashed 3.4 then dirty flashed 3.45 and I don't have lte. Running MK5 boot loader and modem.

Edit:

just had to give it a few minutes... now lte works!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neo.:
I flashed the ROM and I get a LOT of FC's (com.android.phone) has stopped and No network! Why is this happening? :eek: and how can I fix it?

I read somewhere that I need to do dirty flash to 3.4 (But can't seem to find link) Please help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
You need to perform a clean flash of 3.4 and then a dirty flash to 3.45
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Tried that, and it didn't work. Back to 3.4, & 2/19.:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
So about that 3.46 build

pwn.... Lol you tease
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Well did the dirty flash from 3.4 to 3.5. Lol not only did I not get LTE, all I could get was edge. So it's back to 3.4 for now. Waiting for 3.46.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
There's something weird going on. I have my 3.46 and my friend who finally switched back to AOSP is running it as well with no issues. But there's some kernel stuff that is breaking everything down. I'm gonna look into it today!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ROBERTGARCIAREYES:
sorry for the noob question

but how do i made a dirty flas?

do i have to flash the new 3.45 over 3.40 without wiping anything?

thanks for reading
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] megaz221:
I just flash 3.45 over 3.4 without wiping system data. After installing 3.45 wipe the cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Have no cell service at the college.. Booo backups borked too. Maybe I have to go further back on a clean install
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
If 3.4 works for you then stick with that. I'll revert the phone stuff for the next build. About to head out to work to go and put an end to this 7 month long 5 hour a week BS. Discrimination ain't cool, kids.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -oH-mr_rogers:
im getting process.phone crashes every time i boot then the shell reboots, i cant get to my home screen.

ive done a factory reset and reflash 3.45 and its still happening.. thoughts?

im going to try and flash 3.4 or carbon and see if it still happnens
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Just go back to 3.4 for now and wait until he gets things fixed again. Some phones got lucky with 3.45 but most of us won't be able to use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LabiaSlayer:
I had to go to Mobile Networks->Network Operators and try all three AT&T networks before I got my phone working normally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -oH-mr_rogers:
i just switched to carbon for the time being, i thought i had 3.4 still on my phone but i dont so im on carbon for the time being everything works now though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
O.K. I finally got 3.5, and 2.22 to work and play together. What i had to do was delete SlideLock. Figure that one out! Camera and LTE work great, too. As Frehley would say...I'm back in the New York groove.:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BretR574:
If you want 3.4, it's at this link: http://d-h.st/77T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaspah:
My phone has been fairly consistently losing cellular network connection briefly for a few seconds on the latest 3.45 update. Not sure what's up with this...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
This is a known bug but it doesn't have much to do with anything Pwn's doing as much as it is with the current CM11 nightly's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
3.5?? That version isn't out. Do you mean 3.45?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Right. 3.45:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neo.:
I understood this.

1) But I can't find link to 3.4 (All I can see is v2 and v3) but can someone direct me to 3.4 link?

Please help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BretR574:
It's here: http://d-h.st/77T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neo.:
Thank'd you!

How do I dirty flash? I have 3.45 running right now.

Flash 3.4 first then I just flash 3.45 over 3.4 without wiping system data. After installing 3.45 wipe the cache.

Is this all? Can you please direct me to exact steps? (Reason behind is that people are having problems, Just wanted to make sure before I flash)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BretR574:
This is what I did and am good on 3.45:

1. Reboot into recovery.

2. Back up your current install.

3. Clean install 3.4 by a) wipe data/factory reset. b) wipe cache partition. c) wipe dalvik cache. Install the 3.4 zip file.

4. Install the gapps.zip

5. Reboot system. After it boots, reboot into recovery.

6. Install the 3.45 zip. wipe dalvik cache.

7. Reboot system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Please delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
So the recent merge in CM has caused my kernel to be completely and utterly broken. I have absolutely what to even do with it past here. I tried reverting almost everything I could but nothing has resulted in a successful boot.

On top of all that my Virtual Machine won't even boot so I lost all progress within working on the latest kernel as well, along with the ROM. I'm going to work on getting everything back together, but the amount of frustration with the CM stuff is almost enough to drive me away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
I know it would be a lot more work on your end but ever consider basing it off pure aosp and cherry pick what is needed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jakers1991:
I tried installing quantum kernel 2.22 and it says installation aborted and it says (bad) and I redownloaded it several times and still the same I don't know what's going on please help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
I've never developed a ROM so this statement may be really crazy but is it possible developing it off AOSP might be less work in the end then waiting for CM to mess up the kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It would end up being a lot more work porting everything over. It would be a large project :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangtastic:
FWIW I switch to slimkat to try out their kernel and rom and this week's build fixed everything for me and I am getting great battery life for the first time in a while. All defaults. You might consider checking their kernel code. Don't know how far off from cm it is but may give you some ideas... Just a thought anyways. Not at buttery as your kernel used to perform. All my signal issues and bt are resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neo.:
Thank you so much!

One last thing, I am able to find GAPPS for CM 10.2.x but not CM 11( 4.4.2) Can you please link me to your gapps download?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BretR574:
Here's what I use: http://xdaforums.com/showthread.php?t=2397942
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Things are not looking good. Nothing is working, all hope is lost. Closing up shop and saving myself some headache for now. I'll upload 3.46 and then we'll see from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bogdaryl:
Thanks for all the hard work you've put in. Outta curiosity is 3.46 running smoothly and are there any special instructions for this ie should we dirty flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Take some time off. You deserve it. I hope that you come back. You do excellent work.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Oh gosh, that's not good :( hopefully CM's commits manage to fix what's wrong, or whatever wonky thing that's going on manages to fix. Thanks a ton for everything you've done so far, this ROM/kernel is absolutely AMAZING and I have never had better battery life and performance than I have had so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
I find things come to me after I cool down lol. The recent changes cm made I noticed could be bad news and I guess I was right.

3.4 does not work for me, 3.45 loses any signal to the phone after awhile and even going back as far as 3.25 clean install with 1.27 kernel won't give me back my LTE, backup or clean install.

I think I have to roll back to stock 4.3 with a full format/wipe/factory reset. I'm going to read up a lot first.. I don't even know if I can flash 4.3 stock again over the previous 4.3 stock backup that has phone privider FC, which happened after I disabled knox or something. GAHH maybe a stock gapps flash after restore of 4.3 backup will work in that department.

After today with WiFi constantly turning on and cell signal lost I need to try something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Its the end of the world.

A sign of The Apocalypse.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
RUN!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Oh my lord. You guys can all send your thanks to decimalman....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
<.< sarcasm or gratitude >.> *Hoping for good news lol*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Pwn works alot with decimalman, and has done do in the past, so based on that, I'm going with gratitude thinking that he has helped pwn get over a major hurdle or two (or numerous hurdles). :D:thumbup:

P.S. Pwn likes to tease sometimes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
The dots throw me off lol I'm ready to smash this LTE out of the park!

Restored a backup of my 4.3 stock.. the backup before that I'm not sure if its post installation 4.3 or 4.1.1 lol Wish I really made a note of that. Anyway the LTE worked there so here's hoping for the best. And for pwn as well ;)

EDIT: LTE after stock 4.3 backup restore then back to 4.4.2 backup 3.25 works. phew.

LOSING MY HEAD RUN!... <--sarcasm.

For future note, I know, and I appreciate Decimals hard work, same goes for everyone else who would pwn be making this rom for if not us. Thanks pwn.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neo.:
Thanks everyone for helping me out! I have managed to successfully run the ROM and Kernel! (Both latest)

However, I used to run CM 11 kernel (Original kernel mentioned in the CM 11 thread). I have installed ROM and Quantum Kernel.

I have a problem, my phone keeps charging but the charging does NOT increase. It's been 1 hour and my phone just charged 1%.

I have changed charging cable as well (I am using OFFICIAL samsung cable). This is wierd. Anyone had a similar experience? Any solutions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
doo doo doo... nothing to see around here... at least not here

More things coming tomorrow :)

All praise decimalman again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I like the sound of that! Man, Mondays really do suck...

ALL PRAISE PWNCAKES AND DECIMALMAN
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
*hint*hint* I only said around here *hint*hint*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I get it :D I wonder how long it'll take for most people to find it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neo.:
Can someone help me out? Does someone have an issue with slow charging? now it's 15% (been charging for 2 hours) (Should I reflash my kernel? should I wike cache/dalvik if i do?)

Any help would be really appreciated! I thank the developer of this ROM/Kernel for your work!

Regards
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Oh, whatever....

I mean, I feel like this is the best thing to happen today so I just had to put it up instead of tomorrow along with the release. Decimalman is our savior, and his kernels are works of intricacy.

This kernel caused me hours of pain, sweat, and tears. I was gonna wait until this weekend to look at it, but eff that, stable kernel branch! The speed increase is incredibly noticeable, the toolchain I was using was just wrong I guess. Tell me how it is!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Check the cable and port you are using, and disable and mess with fast charge if need be! Also check voltages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
ITS. SO. SMOOTH. MUST BE THE TEARS :p lol Thanks for all your super hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Can you actually tell a difference between this and the last version? I feel like there's less latency if that makes sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neo.:
Thanks [MENTION=1683096]PwnCakes193[/MENTION]. Do we need to clear cache/dalvik if we wish to upgrade?

Thanks for the super Kernel upgrade. You've put alot of effort. I will donate you few bucks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It depends, kernel never touches cache/dalvik but sometimes new stuff can cause issues. In case of new wifi drivers, clear that cache!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
It definitely feels snappier and all animations and scrolling feel smoother as well. After a cache and dalvik wipe, I'm happy to report that voltages are where they should be, and are no longer set to max :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Wait are you SERIOUS?!?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Oh you had me going there, you big silly brute! I've been running kt for a couple days to fix BT 'stutters' but can't wait to try your kernel tomorrow. Get some rest, my good fellow.

Sent from my 747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
:( Upon reboot, voltages reverted to max... Sorry for the huge letdown, oddest thing was, they stuck at first boot...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
I switched from kt747 back to the 2/25 quantum kernel. Runs great! I've grown accustomed to using the ktoonservative governor. What would be a good one to take its place?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allrockedout:
Smooth smooth smooth, well a little laggy at first boot, but after super user gets all its permissions. Smooth smooth
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FirstROMQuantum:
I once was unable to charge my S3 via wall charger. I just used a different charger + usb cable and now it's all good. So I'm assuming my old samsung charger died.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Default check your voltages, set them to stock and go by my voltages in my battery guide for reference to lowest values. (Probably not stable enough for you. but maybe add 50mV to what I have set. 300Mhz gpu on simple or stock if you play games is fine.

Now.. I'm going to try flash some stuff since I got the LTE back :) There's a LTE bug wall though, I don't want to hit that again.. :(3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FirstROMQuantum:
What's wrong with v3.45? Or was it just the kernal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
When you get something so put together as Quantum you tend to forget how and why you ever had to fix things. Restore stock 4.3 fixed LTE.

Flashed 3.25 - Clean install

Flashed 2.25 Quantum kernel - wipe cache/dalvik

put my usual voltages in, current ones were undecided as usual just stock by trickster mod donate version.

Correction - went back to 1.5ghz as its only +25mV more than 1.3 for me. 300mhz gpu simple.

Very smmooooth and quick as pwn mentioned. This is nice :D

Idle is great! Very snappy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Just loaded the 2.25 kernel, don't really 'feel' a difference... Signal still drops in and out.

It is what it is. As long no major hiccups I am good :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
You had me scared for a second, bruv xP hopefully this will fix my signal issues.

Sent from my Quantum-powered SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
This won't, an updated ROM will. That's coming later today!