yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PashaF:
I've successfully flashed the latest Kernel last night. However, I'm experiencing the following issues:

1. Sound over Bluetooth is distorted and produces hisses - something that was fixed before, I believe, as I've had it in earlier Kernels, but not in the 5/14.2

2. The dialer is FC whenever I click on the recents button. I was running Slim_AIO_gapps.4.4.2.build.4.6; then, upgraded to Slim_AIO_gapps.4.4.2.build.5.4, but it hasn't fixed any issues. I've cleared cache (phone and the dialer) to no avail.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
No issues here for either. The dialer is a random issue, the bluetooth could be a number of things. So far you're the only person to report an issue for either one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PashaF:
Thanks! I remember someone else was mentioning the bluetooth issue was related to voltage, but I can't find that post. The dialer FC is driving me nuts, as I can't see my call history! How can I troubleshoot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Everything is running awesomee but that's maybe cause I'm on 3.67 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
I too get a failed message when flashing on d2vzw. Something about permissions. Running C-Rom 6.6.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kronstedt:
I had the dialer FC issue many versions ago (maybe in early March) but it's long gone for me. You can download a new dialer from the Play store as a temp solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
I suggest 7zip to open the archive and remove the file instead of rezipping.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PashaF:
Thanks, I was thinking which one - any recommendations?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kronstedt:
I used Dialapp and recall liking it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
So I've essentially all but forgotten about that paper, whoops! I'll try to post the official final release later today-

BFQv4 and tweaked

up some voltages

Remove Frandom/Init.d

I told you all I wouldn't leave :) As of now there have been 0 reboot reports! Days of kernel work finally pays off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joachim123:
I wish I wasn't the first... Lol reboot reporting here. Twice today since flash. I double checked about phone and says the 5/30 kernel to make sure it didn't fail. I will try reflashing again and wiping cache and fix perms. First reboot was with default kernel settings with music playing through BT. second was after switching to intellidemand/bfq, airplane mode with WiFi on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I shouldn't have said a word! Post some logs and give some more info please so I can look into it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I can't believe I didn't think about that, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PashaF:
Thanks, I'll try it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Recovery ?

Sorry for the off topic, but since I messed with the different recoveries to get QK 5-30 to flash, I've got a problem. TWRP 2.7.0.0 is reinstalled but fails when trying to do a backup. I've just reflashed CWM touch and it is backing up fine. Before I try to flash back to TWRP, I'm thinking there may be old leftover TWRP folders that should be cleared. I have /TWRP on both internal and external. I'll delete them but was just wondering if there are any other places that TWRP might have left something that is conflicting with its new flash. Thanks.

EDIT: Problem fixed... Card was just getting too low on free space.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joachim123:
https://www.dropbox.com/s/hs14zn2neov2shr/last_kmsg.log here's the log before I have another. I'll have to reflash later, @ work ATM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] involuntaryqool:
Reboot as well. Only thing I had different was scheduler fiops. This reboot happened when trying to wake phone. Here's a log: https://www.dropbox.com/sh/7tnrl1uj3zq6pps/AAAylWdPhtoXDj599C9GuZbWa
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Hey man, focus on your paper. Don't worry about us. I'm sure we'll still be here when your paper is finished.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Well I used 7zip to delete the init.d folder and still would not flash on TWRP 2.7 for me. I'll wait till the next version is out and see if it will work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] garwynn:
Thread cleaned. Let's get back on topic please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Just had a reboot while browsing tumblr.

Last kernel log attached

https://www.dropbox.com/s/qsztynp049c112i/2014-05-30_14.36.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
What were the posts? Nobody saw anything or said anything negative.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit68:
Still no reboots or any issues. Havnt made many calls today which is where I normally see the reboots. Browsed a ton on LTE txted a lot and everything has been great. I'm using bfq and intelliactive

Thanks pwn for working on this. But do get that paper done your so close!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Had another reboot while using Snapchat. Log as above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
This really reminded me of Task650's AT&T AOKP thread lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Good! At least the reboots aren't from the same thing as before. It's probably something I accidentally overlooked, we'll see shortly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Got a random reboot while listening to Google Play Music.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] balrog558:
I had one reboot while watching YouTube. If it happens again I'll grab a log
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joachim123:
Two reboots within an hour. I had forgotten to reflash and wipe and fix perms until after the first listed here Both with airplane mode on, WiFi on, BT off. Plugged in charging AC.

First one, middle of watching YouTube:

https://www.dropbox.com/s/8bcqz7md1x0btux/last_kmsg - 2014-05-31_10.33 .log

Second, listing to music via Google Play Music, reboot shortly after turning screen on:

https://www.dropbox.com/s/frs2psgoawx36r2/last_kmsg-2014-05-31_10.58 .log

Edit: and another as I was in the middle of fixing a typo on this very post: https://www.dropbox.com/s/8s6execda8yw33u/last_kmsg - 2014-05-31_11.14 .log
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Yeah, what the hell? Why is a moderator interfering when nothing is wrong? Not. Cool. Dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Another user PM'd me and told me what happened. Some guy posted a ton since he wanted a direct link with none of the adgenie BS that popped up, then called us all some names.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Wow, that user doesn't understand how the internet works. :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Ah! That explains it, then. The things you miss when you're settling into a new home and don't follow the forums for a while. :) As Emily Litella said on SNL, "Never mind."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
What kind of names?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Derogatory term for homosexuals, because apparently 12 year old kids can get on XDA! Quantum doesn't discriminate :good:

On the other hand, the Gods of Android aren't looking too favorably on Quantum. That paper still isn't even started, tons of things to do around the house, and the relationship with Ms. Quantum has ended. I'll try to burden through everything and get something out finally, seeing as how the kernel is no longer giving us the dreaded universal and nonstop reboot error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Sorry to hear of your burdens pwn. I'll give the new kernel a go when the time comes. 5.30 didn't work for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Sorry to hear about Mrs Quantum... Sucks when relationships end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It might've been for the best, but it's always a bad time :(

It didn't work because you stepped out on me ;) Reflash an older QK and then the new one, or just delete the /etc folder in the kernel root!

Huge merges to CM today... I mean HUGE. Since my S3 is now demoted to my workhorse for media and junk I don't notice many real gains anymore... I'll have something new up soon!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Who's ready for the update?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidman23:
Can't wait!:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Dude, you should be in marketing. ;)

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Ahh the good ol' usual CM merge that messes tons of **** up. Apparently the new updates don't like anything about Quantum, as it gives a nonchanging kernel splash screen on boot. Oh well... back to everything else for a minute.

Someone punch me in the face next time I feel like doing a merge with CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Ouch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I hope this makes up for it :)

http://d-h.st/SQs

-BFQv7r4

-CM merge

-Fix some popping sounds

-Fix USB bug
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
So far, so good on d2vzw. Thanks!

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
After flashing the kernel, phone does not boot on the latest nightly 01/06
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
Where I can find the latest Nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
He means CM

https://download.cyanogenmod.org/?device=d2lte
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Awesome dude. last post please check op omfg. I'm running this kernel with aokp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
New kernel runs flawlessly on quantum 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Yep, nothing but butter. I'll post usage stats in a few hours
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
I've been off this kernel since the reboot issues a month or so ago. Installed last night and running very smooth, as usual!

Remind me - are there any additional tweaks that are suggested to make it run even better? I thought I remember some advanced Trickster settings or init.d tweaks.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
ah. back to the buttery battery saving performance I'm used to. Say what you want about the ROM (i think its fantastic) but the kernel is where the magic is at! And to boot the source code is there as well as commit logs for aspiring developers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeWjF:
Nothing but buttery smooth and deep sleep performance so far with 6/1 on Resurrection. My display also seems to "pop" a little more on this one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Glad everyone is liking the new builds! Any reboots can be attributed to our cutting edge toolchain... I may cut that back next release.

I'll be working on the ROM side tonight, gotta take my sister and her friends to the mall all day!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
I'm happy. Keep up the good work pwn. Looking forward to the new build.

......and thanks again, I've learned a ton since quantum began and met some good cats along the way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksd316:
I am using the latest slimkat and was using the 5/15 dkp kernel and was having WiFi wake locks like crazy. Installed quantum kernel 6/1, wake lock gone. Not sure if it's related, but thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] balrog558:
I installed the newest kernel and it doesn't seem to agree with my phone. It's been laggy as hell and caused a reboot when trying to unlock my phone. I attached a log if it works, I'm on vacation currently

https://docs.google.com/file/d/0B80LKx8WNqsuWXZtVC1VckstNTQ/edit?usp=docslist_api

Update I've re-download the kernel and it seems to be way snappier, so it seems I had a bad download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
three hrs post-flash of QK 6/1.

sweet quantum goodness.

ty for the build.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
Maybe that's my issue. Bad download. My phone boots, and can "hear" my phone working, but all I see is the "Gimme Pwncakes" splash screen. Lol. Trying again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] balrog558:
I spoke to soon about the bad download, not five minutes after I posted that I had another reboot while trying to exit Google search
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
The 6/1 kernel was running well on C-Rom, but then I put it in my car dock and it started having GPS issues. It would see my speed but not location. Both Waze and Google Navigation were jumping all over the place.

I toggled location, rebooted and tried again. It still couldn't find me, then froze and rebooted.

Didn't get to pull a log since I was driving. Flashed back to KT in the mean time. Looking forward to using Quantum when it smooths out.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
Me too. Apparently it's got something to do with the new tool chain Carbon is using. I can no longer Install ANY kernel on their 6/1/14 build now. Not a big deal, the entire system is running really well with above average battery life. The kernel is now updated to the 3.4.9.1 tool chain. Not sure about the Rom itself but I am believing they have made alot of changes by me not being able to get a kernel to not constantly show the splash screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
The newest kernel used to reboot alot on me until I undervolted it by 75.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Disregard my previous post. The GPS issues were build.prop related, not kernel related. However the reboot may be kernel related. I'll know more after driving tomorrow.

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
MD5 SUM Error

I trying to flash "QuantumKernel-6-1.zip" end always keep on getting MD5 Checksum error, even after I did check for match and it did match on windows computer, but somehow it wont flash. any assistance will be appreciated please.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lectron8:
wtf

I was pretty happy with KT kernel and Quantum 4.1. but I had to try this new kernel after such a long hiatus. Thinking I was totally safe with CW back up. It ran very smooth and great battery life but I kept getting reboots. I tried changing a few settings but finally decided I didn't have time for this and had to go back and to my dismay after restore my phone was all messed up. Unlike previous restores it seemed like a new install. eventually google backup restored much of my apps but I sure would like to know if CW is not reliable and if not what should I use. Tibu also helped.

Any ideas would be great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
use to be cwm diehard. decided to try twrp about three months ago. would never willing go back to cwm. twrp seems to have more options (or i'm getting a little smarter. lol)

is worth a try in my opinion. can always go back.

good luck. :)

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
I've experienced the same issue with any kernel built with the newer 4.91 tool chain. It's like it forever alters the system. I ended up wiping my internal sd and starting all over. But I too use CWM (Philz 6.41.6)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
PwnCakes - Any further thoughts on incorporating a Quantum Dark into your ROMS?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rhealeyogden:
Anyone else on 1.19 getting Play Store errors when trying to download? Haven't had any issues until I just dirty flashed this new update. Might just be a random outage. I can search apps just get errors when Downloading.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buckeyemike:
This was an issue on for me on 10.1 as well. This is really the only thing that keeps me on stock. I wish this would get sorted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
No issues here, do you have the latest gapps 08/13. Clear cache + dalvik after flashing rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rhealeyogden:
Fixed. Downgraded and cleared cache. All is working fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Quantum, bionic, gasps, supersu, wipe dalvik, reboot win.

Now if I hadn't cracked my glass this morning all would be perfect.

Loca or 3m is the question of the moment. Will probably go down the double sided sticky tape path first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
What's really annoying is that 10.0 didn't have these connection issues (at least I didn't have them). What changed between 10.0 and 10.1/10.2 that essentially kicked Bluetooth in the crotch like this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
I'm trying the Dandroid TW ROM at the moment. It is pretty snappy and keeps the TW functionality. I just set it up today for a trial and can't say anything about battery life etc but so far, so good. FYI

Pwncakes.....not stepping on your ROM. It's great........just wish the BT would work with Ford Sync........makes the wife unhappy......
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polsonov:
I've got a F 150 and have had zero issues with any pwncakes ROMs. I need BT as I do lots of calling to and from work. Kinda why I stuck with this rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Pwncakes can't fix the BT issues....it's a CM problem that has plagued them for a real long time, it's their job to fix it. I don't think Pwncakes appreciates you repping other ROM's in his thread :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
The Bluetooth issue is happening in certain devices, mine only had issues with CM 10 ...long time ago...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Didn't really mean it that way!! My apologies to Pwncakes!! I'll be back to this ROM! It works fine on my RAM uconnect. Just got to get one for the wife's phone.......so I test on mine first!! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Do any other people with Canadian s3's always need to remove the assert lines in the updater script in order to get a successful flash? I've been doing it to flash this ROM since it's initial release. Not a big deal but just wondering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scotteb:
No, check your bootloader, could be using an older one. check here and update as needed, should fix the problem. Check your recovery version first though and make sure you are on the latest one. Using GooManager to update recovery if needed.

No problems flashing here, with any rom on my I747M

here for modem http://xdaforums.com/showthread.php?t=1831898
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Just checked. I'm on TWRP 2.6.0.0 and have the latest bootloader MF1.

Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scotteb:
one last suggestion that i just remembered. There used to be 2 diff versions of TWRP, can and att. When I used to have the can version of TWRP i had those problems, switched to the ATT version and no problem since. All I did to change was edit the build.prop and changed d2can to d2att, reboot, fix permissions,reboot and they try to install TWRP through GOO again. It will say same version, just make the change if its not like that already and it should work for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buckeyemike:
What year? Mine is a 2009 and I had BT issues on my skyrocket w/CM10.1 that has kept me from flashing anything. That's the only thing I like about stock is that BT works and reconnects properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polsonov:
2009 FX4. I don't have nav though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's actually Googles fault, not CMs. Can't fix it unless they update 4.3 source
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
The issue lies with Philz. I know it has features but it is the least recommended recovery. Stick with TWRP if you really want features, CWM if you want everything to be as CM intends it to be.

The toolchain can't alter anything that essential and cause a whole bunch of issues, those will just come in form of reboots potentially... and miscalculated numbers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
OK wow, I did not know that. Thank you so much for your reply sir. Looks like I shall be making the switch for the first time ever to TWRP. THANK YOU! [emoji106][emoji2][emoji2][emoji2]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Just had a reboot while tapatalking.

Latest kernel.

https://www.dropbox.com/s/hegoyzvlgxzihd1/2014-06-02_09.26.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
I'm also using "CWM (Philz 6.41.6)" and have checksum MD5 errors after reading this I went and installe TWRP through GooManager, everything seemed OK, even I "Tap menu then hit Install OpenRecoveryScript." it did show my file name. but when I boot recovery it boots to "Philz" any help please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
This isn't the place for that question, but I don't know if PhilZ supports ORS or not. You can find a zip from somewhere on the Android Development forums!

Thank you! Your log has successfully helped me figure out the answer to something I've been wondering about for a while. I'll revert the commit that has caused that particular reboot for the next kernel!

Seriously, thanks again! Great outcomes like these are what happens when the whole community works together
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
Sorry about that wont happen again.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
For the record, PhilZ supports openrecoveryscript.

List of features can be found here:

http://xdaforums.com/showthread.php?t=2201860
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
And now I know :) I have always steered way clear of PhilZ for a long time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanKNugs:
Anyone have a link to an updated version of CM touch recovery in zip format for amateur install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Just made this for you. d2att only, latest cwm touch flashable zip. Took PhilZ script which is a simple package extract on the right partition and stripped the blah blah but kept the board check.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Edit it again to say you made it and I'll throw it up on the d-hst for everyone new if all is fine by you!

Oh yeah I forgot to mention that the new kernel supports F2FS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's nothing that identifies me or PhilZ and the script is clean of any extra junk (including process, so you can upload it wherever you want. d2att only =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Does PhilZ or TWRP support F2FS? Don't we need a recovery that does support it?

VZW SGSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
First reboot while using the Google dialer...... And yes, I was driving. Lol

https://www.dropbox.com/s/78kctcnna6vptbw/bugreport-2014-06-02-18-08-53.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
That 5MB txt file caused a reboot on my phone lmao