yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
I've been getting reboots, too... I thought that leaving KT was gonna be the end of reboots Dx voltages are fine and everything

Sent from my Quantum-powered SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Does anyone else get lag when using the intelliactive governor and trying to return to the home screen or bring up the recent apps menu?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Peterbluez:
I'm using the intelliactive and haven't noticed any lag. In fact I was think earlier how amazingly smooth my phone returns home and goes to the app switcher.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
This ROM is great! Thanks for the hard work!

That being said, GPS is pretty sketchy at best! I'm sure 95% of you can turn GPS on and its fine. But I am not a normal GPS user, I use my GPS 8-10 hours a day if not more. I would have to say it is on target about 60% of the time, maybe. One of the main things is I have to disable and enable GPS from the pulldown before it actually starts working, meaning it will find a place and zoom into your approximate location, but when you start moving it just sits there, until I turn the GPS off and on. I have to do that about 80% of the time.

I don't really post until I have exhausted all the things I can think of. I have reformatted many, many times, cleared caches, etc. I have not restored ANY apps! I have the paid version of TB, but I chose to do a fresh start with no restore, so there should be nothing interfering!

I also use Faster Fix, and GPS Status. I can watch GPS status while I have a destination set in maps, and it says 0/0 for Satellites, until I toggle GPS.

Don't really know what else to do but buy a Garmin. But that would slow me down, as the app from my company links right to the Navigation, so adding addresses is cake.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Did you restore to a stock ROM to get GPS working correctly and then reinstall this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
There are pages way back where users were experiencing serious signal and LTE drops due to some of the d2lte builds. I suspect that your GPS issues might be caused by an earlier build of some cm Variant ROM. The solution for some was to restore to a stock TW ROM, boot to get a solid gps lock, flash correct bootloader and modem, then instal Quantum.

I know its not an answer but will hopefully give you a perspective you may not have considered.

And yes, it is an Awesome ROM!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
The only other ROM I have used was Slimbean/Kat. I came to Quantum because of the random reboots Slim was having and wouldn't admit it was a problem. (Guessing its because they are getting too main stream to care tbh)

Also, I thought you couldn't flash to an older bootloader after kitkat? Could be wrong as I think I read that a while back.

Thanks for the fast reply btw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
You don't have to change your bootloader to flash back to stock, it's separate from the ROM. And there is no kitkat bootloader yet since we haven't received the official update.. There's a "restore to stock" thread if you wanna try it out. If you haven't taken the ota to 4.3 ever I would advise you to use the 4.1.2 thread because otherwise (as you know) you won't be able to rollback your bootloader anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
@PwnCakes193

Notification sound issues again after a clean flash of 3.66 :(. It was working fine until I turned my phone on mute in the sound menu then turned it to normal and raised the ringtone linked with the notifications.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
yes, depending how you go back back to stock you may not have to flash the bootloader and modems. since I am

not

on mjb, the way I restored to stock was from this thread:

http://xdaforums.com/show....php?t=2363882

this route did require bootloader to be updated to flash quantum.

Yes, it is confusing and I do not intend to endanger anyone's device.

to follow up my camera question earlier: I have not broken the camera yet 3.66 with 3.27 kernel. I handed my neighbor my phone to see if she could break it like she had hers. She could not. So, we proceeded to set her sgh-i747 up with 3.66 and the latest kernel. she immediately was able to get the camera go all wonky. it was on Sd storage and happened following the video camera. she opted to roll back to V3 (4.3) till CM is able to stabilize the camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
That is a 404 error page :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
http://xdaforums.com/showthread.php?t=2363882

odd, sorry bout that

edit- clicked on it and it went there, but there does not seem to be a difference in the link......huh!?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
Yea I noticed! Intranets are mazing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kronstedt:
Have you tried this? Was having the same issues as you and this fix worked for me.

http://xdaforums.com/showthread.php?t=2201668
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] munraf:
So long and thanks for all the fish

Pwn, I've had my S3 for about a year and a half. Your ROM and kernel is by far the best I have had on this phone. Your commitment to updates and willingness to help is second to none. I ordered an HTC One M8 today from AT&T and I can only wish you and this community the best. If you choose the M8 for your new phone I only hope to see you over there. Good luck in everything you do. Thank you again for making the S3 the best phone I have used in a long time. Here's to pwn.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akitten007:
If I may get off topic for one moment, what made you jump the Samsung ship? I've been debating between the S5 and the M8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] munraf:
I had such high hopes for the S5 and I don't think it came near to what it could have been. To me, physical interaction with the phone is very important. In the end, I still have to touch the phone to use it. I didn't care for the faux leather of the S5. I wanted something that screamed flagship. I also didn't want AMOLED anymore. I use my phone for maps and traffic on my 40 mile commute (each way) and after a while the google search bar within maps actually got sort of burned into my screen.

I also like the overall design of the One more. Just a subjective preference. The boomsound speakers, FM radio, and IR blaster will also be nice features to have.

I wanted to get the S5, I really did. But to me, the updates to the phone felt more like feature updates. Any flagship will be fast, at least out of the box. So that was a non issue. But really Samsung? A half-hearted attempt at a fingerprint scanner and a heartrate monitor? Don't sell me features, sell me the phone. I'll probably wind up putting a custom ROM onto any phone I get anyway, so these aren't selling points by any means.

Something stood out to me about the One. I had two HTC phones years ago, the Tilt, and TouchPro. Both were great in their era, and I have high hopes for the One.

The only issue is the camera, but at the end of the day I don't expect DSLR quality. I pretty much just view my phone pictures on my phone anyway. If I want fantastic images I'll lug around my Canon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
Thank you bud, I am not completely sure if that worked or not, but I will find out tomorrow.

Also, I am not understanding this whole 4.3 don't flash or you're bricked deal. I am on Quantum right now, so it says I am on 4.4.2, so does this mean I cannot go back to stock? So many threads about it all, I think I'm more confused than when I started.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's not about the rom, it's about the bootloader.

If you have the MJB bootloader (MK5 for i747m), you cannot downgrade to an earlier bootloader.

Stock TouchWiz roms via ODIN and even some stock TouchWiz recovery flashable roms include an earlier bootloader and that's what will throw you in a brick.

That's all there is to it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akitten007:
Thanks a lot for your input. Hope you enjoy your new phone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Looks like the Gods at CM have been taking look at the Gits around here, they brought in some changes for a nice speed boost, and the fix for the smart dock! They also now committed our old trouble causing touch-screen firmware. This may cause issues for users in the future, we'll see when I build tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shekinahsmoke:
woo hoo!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
Download Links are dead for me, anyone else?

EDIT: Back up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Think I found the fix, here is how:

1. Go to sound settings

2. Press volumes

3. Uncheck link ringtones and notifications, you'll then see the notification volume come up on a really low setting

4. Move it up and make sure ringtones is loud enough too

5. Should be fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Peterbluez:
I attempted to install Quantum 3.66 last night on my wife's phone which has TWRP recovery installed. I'm at work now and am not completely sure of the error I received, but it failed to install 3.66. Is there a problem with using TWRP for Quantum? She does have the dreaded MJB bootloader, but as I understand it, that shouldn't cause any problems. I'm able to get in and out of the recovery without any issue.

I had this related problem - I made sure back up in TWRP before I attempted to flash, but then when I recover the phone isn't able to load up. it just hangs at the AT&T splash screen. FWIW - I used the same copy of Quantum on my I747 and it worked beautifully.

Sorry if this has already been covered, I looked all over the place on this thread and didn't find what I was looking for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I feel exactly as you do. I wish Pwn would build for the HTC One(M7 or M8).:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Make sure you have the latest TWRP (v2.7.0.0). If you do, get the full error message. You can copy the recovery log in TWRP by going to advanced then copy log to SD option. Upload that here. :)

As for your second question, what are you doing exactly? You made a backup in TWRP and try to restore it, but when you do it hangs on the boot animation? Once again, was TWRP up to date?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aex90832:
Clean flashed 3.66 with 3-26 kernel... lots of random rebooting...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
The same friend who helped me with the D2VZW side might get a M8. So we'll see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Peterbluez:
I'm certain its not up to date. I guess I'll just grab the latest TWRP image and Odin that bad boy in and give it another whirl. I just wanted to make sure that TWRP can work.

As for the nandroid - that's exactly what I did. Backed up, then went to restore and it hangs at the AT&T boot animation. May also be a problem with a dated version of TWRP. I'll check it out this evening and will revisit the issue if that doesn't fix it.

Thanks again Polo, you're a real mensch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
TWRP definitely works. My S3 never was in contact of any form of CWM. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corey103:
I've fixed the one problem I've had with this build, but there's a small bug or something. I've noticed my charging is much slower than the last build. Funny enough though, the discharge isn't too bad. I think it discharged about twenty five percent on an eight hour idle. Any tips or suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] munraf:
Well damn, now my hopes are up. Thanks Pwn... Fingers crossed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Sorry- just catching up from the road. My bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://www.coindesk.com/mining-malware-infects-mobile-market-via-google-play-apps/

Just to scare you and stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Check the Facebook page for the latest kernel. Yeah. I went there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't see anything newer than 3/26. Also might be a good idea to put the link to FB page in OP. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I posted it as myself, whoops. I'll fix that soonish. and I'll fix the OP soonish. Class time now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah ok. I see the little part of your post but if I want to see more I have to login. And I closed my FB account after getting tired of baby pictures, quotes on wallpapers with doves and invites to Candy Crush.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
[MENTION=2044079]Nardholio[/MENTION] with the new TS firmware I have another wave of no response touchscreeens. They turn on, but aren't responsive to touch. I'll find you soon and give you more relevant information, but I have class for the day. I uploaded source just before I left.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matrioux:
New Kernel (3/28) wont boot past the "gimme pwncakes" screen for me. I will look back through the last couple pages as I know some have had this happen in the past.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update, was about to flash. You saved me couple of hours.. Think we have to wait until this is fixed by pwn
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Me too. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brokeddid It:
3-28 Booted up just fine here with 3.66. TWRP 2.6.3.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Hmm...I'll try. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matrioux:
My setting too, Originally I had kernel 3/26 and got stuck on boot screen after installing kernel 3/28. I then tried re-installing 3.66 with new kernel and got stuck again. Finally just reverted to 3.66 and all is well. If others get success with 3/28 I'll try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Yup same issue. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brokeddid It:
I had success with wiping cache, dalvik, flash kernel, wipe cache and dalvik again before rebooting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I'm gonna let that one go to the official cm nightlies. I'm not convinced this isn't caused by something else
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
Thanks for that! But after 6 hours of messing around with it last night it's doing the exact same thing as before. Pretty frustrating.

Went to completely stock, fired it up, let it lock, then came back to this. Same boat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
3/28 kernel would not let me boot, had to go back to my restore of 3.66 & 3/26 kernel.

Reboots seem to happen mainly when I do something with SMS. I use ChompSMS if that helps. I know Pwn said he'd get that fixed so I'll wait till then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Those who have reboots, are you on the latest boot loader? That may be the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I got not reboot and I'm not on the latest bootloader here, if it helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aex90832:
So I747UCUEMJB is the preferred bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well not a reboot, but a non-responsive touch screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yesterday morning with 3/26 my alarm clock woke me up at 7 as usual but I couldn't touch the screen to turn it off. I kept trying in my slumber but nothing would work, I turned off the screen then back on then it worked just fine. Could be related? I put it off as a simple bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Everything works here, touchscreen and everything. Wiped cache and dalvik after 3/28. I'm on the MK5 bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
We'll find out soon. Any kernel that has done a merge with CM is now having some no-boot users. Let's wait and see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Just a random guess but is it possible certain model numbers are having the issue? Like all SGH-I747M's?

---------- Post added at 01:12 PM ---------- Previous post was at 01:09 PM ----------

Yup, I747MVLUEMK5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
No because that's what I have and nothing is wrong here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It could, but definitely not i747m. Got that, and all is working. :p

Edit: Got ninja'ed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
dont know if is helpful/relevant, but have UCDMG2 bootloader (which i believe was an OTA update from UCDLK3), am clean flashed on 3.66 with 3-26 and have had no probs. except for screen-on when i turn phone face up (resolved by disabling XLockY in XBlast Tools (Xposed). thanks all for great support.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Please say it isn't so......
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Just installed on mine with the same bootloader. No issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
MJ2 and MJB are near identical, minus the knox, as stated before. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
True.

But I seem to be one of those unable to run the new kernel, or what I understand to be the kernel with the touchscreen updates. Seems the successful installs are on the latest bootloader (mjb and mk5). I will wait and see as pwn suggests.........
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Haven't tried 3/28 on my side, so if you're talking about that one, you might not be alone. 3/26 runs well with interactive and my settings. dynamic_fsync off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I'm going to light a candle.:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brokeddid It:
Running ATT w/MJ2 boot, 3.66 and 3-28 with no booting, touch screen , or reboot problems. Everything working great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
Oh that makes me happy. I'll keep trying then
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
Same exact setup for me and long boot with no touch response.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matrioux:
I just upgraded from MG2 to the MJ2 bootloader, and I got the long boot / no touchscreen response issue, going back to 3.66 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
+1

Tried a bunch of installs. No wipe/wipe and format everything....... No dice
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit68:
I'm on latest boot loader and had both black screens and reboots. Reboots all happened during calls. Im on 3.66 and was on 3/26 kernel so I downgraded to 3/21 before I had the issues and I've only had 1 black screen.

---------- Post added at 04:02 PM ---------- Previous post was at 04:00 PM ----------

After my black screen I noticed I was on interactive so I changed it to intelliactive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wyelkins:
Is the 0328 kernel working? I am on 0326 with no problems on d2spr.

Is there a link for 0328? I saw something about Facebook.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ksd316:
I too have been pondering about the M8. All of your points are very valid, and may have swayed me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
http://techcrunch.com/2014/03/26/ifixit-confirms-why-the-htc-one-m8-ships-with-a-stellar-warranty/

Im not ready to jump ship yet, but it is tempting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
3/28 kernel works for me, but I'm on the mjb bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Working for me on mj2 bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aircooledbusses:
hate to ask for hand holding, but what process have you used for your successful install?

I have:

format system, wiped cashe flashed rom, su, gapps wiped cach - no luck

done just a cache and davlik, flashed kernel (with and without a wiping of the cache/dalvik) no luck

factory reset, format system and installed rom and su (gapps)- no luck

formatted data (phone wipe) factory reset, format data- rom su - no boot

...............
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
I'm afraid I won't be much help. I was on 3.65 with 3-26 kernel.

I wiped system, cache and dalvik and installed 3.66. Ran it for a while, then just flashed 3-28 kernel dirty. I haven't had a problem with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
Installed 3.66 today, and didn't realize that the phone was asking for my SIM card. No sounds from my ringtones or notifications, although they're there. I'm assuming that the "no sounds" and the "no SIM" are related. Does anyone have a fix for this?:confused:

P.S. I've taken out the SIM, checked it, and replaced it several times.:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Try this for the sounds issue:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
No go. I still believe that the SIM and the sound are linked. Thanks for trying.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Hey pwn... just in case you get BORED sometime... have you seen anything about f2fs format for the data partition? We're messing around with it on the asus tf700 tablet thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I can totally do it, but it has a lot of bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
Been getting more than a few reboots on 3.66 and 3/26... updated to 3/28 with a cache/dalvik cache wipe, so far so good, touchscreen works fine and I booted up fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
I have been debating the same phones. I do like the looks of the m8 but I always put an Incipio NGP case on all my phones so the feel of it loses some importance.

I also really like the water resistance and the hardware keys of the s5 so I have the max amount of screen at all times. Lastly it seems like galaxy phones have more custom ROM support.

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
3/28 just sits on the Pwncakes screen, won't boot. On 3.66
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
So is it the touchscreen firmware?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
This is what happens every time it gets committed. Ktoonsez apparently has it as well and it didn't boot for a small number of users. Given the issue that it's the ROM I'm gonna try it again and see if it works. I went through my kernel source and it doesn't seem like anything would affect it besides Decimalman's light stuff.

I'm using the latest binary in the anykernel interface, and the users who won't have it boot for them have seemed to have all been on MJ2 or previous for bootloader. Some people also have it boot but it's just unresponsive.

[MENTION=4258784]MJPollard[/MENTION] thanks you as well for fixing the media dock as well, blackburn and I have been chomping down through the GCC warnings and issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Send some of that **** to gerrit ;p Also send a revert up to gerrit if you want, I'm going to have to revert the commit if I can't figure out what is wrong (I'm hoping it's something easy to update, like recovery version)