yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Great sports programs, horrible everything else
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
I've tried to reproduce the bluetooth issues that have been mentioned. So far I can't find a device that I can't pair.

Works great through my soundbar. Listened to a couple of hours of music through the Play Music app.

As tempted as I am to flash some of the other new 4.4 roms. I just cant bring myself to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lectron8:
I came from Quantum v3 I just did backup, then system format, then cache wipe then dalvik wipe, then flash rom, then flash the newest pa gapps. I have had no problems, everything works. I am using i747 AT&T good luck. Do backup first

I forgot to say thanks to pwncakes193

His work is amazing and his site is so friendly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
I don't think pairing or one-time usage is the real issue if you read our posts...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Yesterday I nandroid my Quantum and flashed the latest slim kat weekly with spec gapps to see if it would work. It did and I played with it for a while then restored Quantum. Why mess with perfection!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
I did. Didnt think I had to repeat your post verbatim for mine to be valid. I retract, No bluetooth issues here....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXshur1kenXx:
Just wanted to say running v3.05 and 12/15 Kernel is excellent. Only 3pct drain overnight (8 hours). Everything is buttery smooth. Great job [MENTION=1683096]PwnCakes193[/MENTION]!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hotrod60:
So just out of curiosity when will we expect to see the new kitkat lockscreen? If at all. And does anyone know of a way to get it otherwise?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Just wanted to doublecheck, but it is not advisable to flash these if on stock rooted TW 4.3, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
If by this you mean the arrow on the bottom and the camera button then it only shows up if you turn on the navigation bar(under navigation in settings)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hotrod60:
Awesome. Im not finding that option in settings though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Has anyone else noticed massive battery drain when using nova launcher?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmah10:
just dirty flashed 3.05 with banks gapps standard 4.4.2, everything seems to be working just fine so far
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Flashing through recovery is okay. It's downgrading to an earlier version of TW via Odin that will brick your phone (thanks to 4.3's bootloader). As long as what you flash doesn't contain a bootloader (and no custom ROM that I'm aware of has one), you should be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PashaF:
Move to SD Option

Why the option of moving Apps to SD card is not available on this ROM? None of the 'movable' applications have that button in setting, nor am I able to use any of the 3rd party apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tj_ona:
New update is BUTTERY!

gimme dem cakes 4.4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bazinga_:
In the new release I saw few hung up..I had to take the battery out But battery life is amazing.

I didn't even reinstall gapps, just flashed rom after clearing caches.

It's a zerolemon extended battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddurandd:
Google Wallet

Has anyone been able to get Tap and Pay to work with this ROM? It seems to go through the set up fine for me but nothing happens when I tap the machine with my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Bump
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcnutty:
Google Glass doesn't pair for me, but my Jawbone ERA does...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXshur1kenXx:
Damn if I knew I would've tried to tap to pay earlier. I might be able to test it tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Is the Quantum Kernel going to eventually have overclocking capabilities? Just wondering for future references.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BretR574:
Same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
I am curious as to what you are doing for which it is not 'fast enough?'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
I had issues with it also. It worked from my N7 and also my G2 (running CM11 on it and tap to pay works flawlessly every time), but never my SIII. Kind of wondering if it's a bug in the NFC chip that's present in the SIII.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I like tweaking on everything like with KT, but he doesn't keep up with updates like PWN does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
I just noticed this as well. Bluetooth says it is connected but my truck is a long, long way away. I unpaired, cleared data on Bluetooth share, deleted my phone from my truck then paired again. It connects and works fine. When I turn off my truck the phone still says it's paired and won't reconnect no matter what I try. Strange. I did a clean flash of V3 before flashing V3.05. I guess it's back to a full wipe and clean flash of V3.05 to see if it fixes the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I've been having issues connecting to bluetooth and had FCs on bluetooth sharing. I've gone into Bluetooth Share under settings->apps and force stopped the app a couple of times, that seems to make it work. This is on a clean flash of v3.05
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BretR574:
I too was having issues with my BT. Did this same thing, now they connect. Also a clean flash to v3.05.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
I tried the force stop - > clear data process a few times. Bluetooth works for a bit then the problems start showing up. Since you are seeing similar issues after a clean flash I think I'll skip the grief of doing that and will live with the connection issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kwikrat:
The same thing happened to me. I figured out what was causing my issue. I purchased the 3300mAH stock size battery from eBay that was all the rage on this thread a few weeks ago. In my excitement I didn't realize that these batteries don't have NFC enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xXshur1kenXx:
Well at least now we know where your error lies :D I know personally tap to pay has worked for me from day one, I just haven't used it recently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thegame3202:
Yes, it works temporarily SOMETIMES. Pwn said he was having the same issue and was looking into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
So is everyone having Bluetooth problems then?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poetikal:
Yup, for the majority of us. It connects to my car, but still has a persistent pausing and un-pausing issue. Then BT will FC, not recognizing my car stereo... kinda frustrates me, thus having to resort listening to FM radio. :eek:

So, you're not the only one. :)

Also, not sure if this build (Quantum), or CM for that matter, has AVRCP or MAP capabilities.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spasch:
My bluetooth works great. 1 time only. Each time after that my car stereo tries to reconnect it tries to load 2 "unknown" devices. Then I have to force the connection. My obd2 adapters however work consistently. It's been the same on every kit-kat version of quantum for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Dude...you don't know what you're talking about I'm sorry for coming off as harsh but really.

Look at the source code that CyanogenMod is releasing onto GitHub. This is what quantum and quantum kernel are based off of and heavily dependant on, and KT kernel also takes from it if it would make a difference, enough to warrant an update. Check the latest KT release, look at all the commits between then and now. 99% are core, app or device-specific and are NOT part of the kernel. The kernel source doesn't even care about these commits. It doesn't bat an eye. Why? Because building the kernel only includes a certain list of files, and most of them stay untouched for so long even if the ROM is being updated daily.

Even if there have been any kernel commits between then and now, what do they do? Is it significant? Doubtful, otherwise KT would push it. If not, leaving a post and asking for it is all it takes, I did it once and he uploaded the next day.

Changing a typo, a voltage increase or a misplaced clock speed change that affects one SPECIFIC governor and IO combo, with one SPECIFIC setting tweaked to a SPECIFIC value that causes this problem (aka: most people have not and will not ever experience this hypothetical issue) is not worthy of syncing the sources, building the kernel, uploading it and posting it and updating the OP with its impressive change log! KT has, I believe, already applied every bit of proprietary work to the kernel that you'll see on it, the actual ktweaker app is perfection, so he has nothing left to do other than sync and release kernel updates that actually make a difference that the CM team or Linux push out. (Actually, for example, current latest build is Linux xxx 71, current is xxx.72, released hours after the kernel was posted. Still not a big enough change IMO.) No point in updating just for the sake of updating and having a build date closer to the present (Pwn dude I am NOT accusing you of this, in fact I'd be delighted to see double the amount of builds! The ROM is exponentially getting better, more stable, snappy, and its battery longevity improved with every build, thanks in part to your effort and dedication, and also to the CM team)

KT has a GS4. Its his main device. He doesn't use a GS3 throughout the day like we do nor have reason to visit this part of xda! I have nothing but gratitude that he decides to still support a legacy device with the infrequent, honestly unnecessary (the kernel works right now. It will for the rest of kk's lifespan) updates that cost this dedicated, OVERWORKED (like, real work. with a real paycheck and a boss. not xda...just a hobby) man his time and energy that could otherwise be spent elsewhere! Rant over
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
Well said.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
http://xdaforums.com/showpost.php?p=48591917&postcount=13660

well speak of the GAD DAMN DEVIL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Alot of that is misinformation in a way. Things change a ton over the course of the day, and the current right now is .74. You'd be surprised at what actually changes. The kernel won't work the entirety of KitKat's lifespan, and is shown already due to the fact that 3 major changes rendered some kernels useless.

The issue is that most users use nightlies, and some require some parts of the kernel to be updated. Running anything other than what's supposed to be on it at the time can and will cause issues. The latest update he just pushed out is the same that was in 12.15, just all the

CM stuff they had to merge in, although I don't know what he means by it working on ROMs past 12/16 only, that's not an issue as we can see with Quantum 3.05.

The skinny of it- run whatever you want to run. Updating things sometimes work, it's sometimes doesn't. If we use that logic that you used above on everything, then why install new versions of anything? We're testers here. Our main goal is to debug and figure out what issues are, while aiming to make a perfect experience. That requires updating constantly, as we can see when 4.3 came out especially.

Also, I'm working on a new release. So yeah. :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Some of this I didn't know, thanks. But I didn't want my message to be taken as "why update anything ever" - kt accepts bug reports they just don't pop up (from what I've seen). ROM's are much more fickle than kernels because of the sheer amount of code and features that are made to work in conjunction together, so I assume it's more of a challenge to keep it neat, minimal and tidy with a full ROM than it is a kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcnutty:
What I noticed was that it kept attempting to connect to a device that was no longer in range. I had to connect back to that device, then manually disconnect to fix it. Then I was able to get Glasses connected back up fine, but I had to manually disconnect when I was done to keep bluetooth working for my other devices.

Flashed back to 3.0 and no longer have issues. Definitely a bad implementation of new bluetooth features or whatever CM was trying to do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I rolled back to v3 to resolve the Bluetooth issues as well. Hopefully they are fixed soon, but for now v3 was plenty stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
Avrcp Rollin in soon?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Bout to roll out 3.1 No changelog for a little bit but LOTS of changes, especially kernel side. I have some Bluetooth fixes for car units as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] allrockedout:
Woo update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Woo-hoo first to download!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Woot! I'll try it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Just got the rom notification and ready to download

And this new update can flashed over v3.05

---------- Post added at 02:01 AM ---------- Previous post was at 01:59 AM ----------

Where the download on the op all see is the v3.05
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
http://d-h.st/xXn
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
Dude you are a boss at rolling out updates. I'm a first time dev and I'm still learning a lot but if you ever need any help I can try and do what I can.

---------- Post added at 11:30 PM ---------- Previous post was at 11:18 PM ----------

Just flashed 3.1 and everything working as usual. Will report any bugs I come across.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
where is the link 3.1¿?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
amf66 posted the link two post before your post.

http://d-h.st/xXn
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
haha ok thanks XD...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarKnight6969:
When you say "flashed over" do you mean we don't have to do any extra wipe aside from cache and dalvik? Or is it recommended to do at least a dirty wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brokeddid It:
Clean flashed 3.1 and have no signal bar, and in about phone no baseband is showing and when tabbing status, bounces right back to about phone screen. Restored nan and got everything back, did a dirty flash over that and signal and baseband dissapeared . Redownloaded, verified md5, clean flashed , still no difference. Nan back to v3.05

Update- clean flashed again, no signal, flashed K's kernel and all is good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeusakatkm:
Is there a way in this rom to switch to only 2g networks?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
Same problem i cant switch to 2g or 3g only
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
Wat the change log in v3.1?

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk now Free
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duffman14:
There is not one right this moment
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
What type of i747 are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Similar situation, but dirty flashed, with PA gapps, my phone calls out, but can't hear the other party when the phone is answered. Also, SOD last night same as happened with 3.05 Restored to V3 with 12/11kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonathanh221999:
No baseband problems here on I747M running v3.1. Strange...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
As in if you have a previous version of a rom IE v3.05 and a update comes out like v3.1 sometimes you can just do like you said wipe cache and dalvik, and not have to wipe user data and have to go through full set up.

So has anyone did a dirty flash? or just better to do a full complete wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Dirty flashed and no signal on first boot. Battery pull and all is good. Sometimes the simple things work best ;)

Bluetooth seems to be working better after re-establishing the connection to my H720. Open the boom, close the boom, icon goes white, icon goes gray, connects, disconnects, lather, rinse, repeat... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Also has anyone notice any real difference coming form v3.05 to v3.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Let's see, my post just before yours stated that bluetooth seems to work. I'd say that's a REAL difference...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
ha didnt even notice your post..must have been posting at the same time(twilight zone crazy :eek:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Thanks for the info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Dirty Fashed. No. Problems so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
LOL, I think you're right!

Only thing I've noticed in the last few releases is with Poweramp, at least once in every song I will get a short buzz, like a game-show-wrong-answer buzz, whether on USB (dock) or wired. I'll have to do some more experimentation...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Yikes, this is starting to look like my mic and speaker are both dead... cleaning, reflashing V3.0, and praying....

EDIT: Flashed CM, still not working.. then remembered the 'pull the battery trick.' Yep, that did it! Restoring Quantum now then will update to 3.5 <sigh>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RonG21:
Well, the opening splash screen now reads 4.4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
You ever think about including Trinity color in your kernel? It really makes the phone look a lot better!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
Searching this thread for Trinity...

http://xdaforums.com/showpost.php?p=46010204&postcount=2717
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] I.R.Chevy:
Just did a complete wipe, and clean flash of 3.05, Used Banks core gapps, and am running Ktoonz latest.

Rom is running buttery smooth, super stable and ridiculously efficient on battery. However i noticed this morning that i am not getting any audio on notifications. The phone will vibrate, and the led flashes like normal. But doesnt make a peep.... Really dont want to reflash as i just finished restoring everything and getting everything where i want it, if anyone has any insight it would be greatly appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Check in sound options that your notification isn't set as "unknown" I get that sometimes. Pick a new one and you'll be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
Does it do it for all notifications or only certain ones? If all check your settings for sound. Go to settings>sound and check the default notification sound. Also click volumes and see if ringtones and notifications are linked and if not check the notification slider. If neither of them then it might be an app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
dirty flashed and when it was done booting, lost google+ and some other gapps. i thought my last backup was my first quantum flash but it was all the way back to jermaines roms! :o meh can always benefit from a clean flash, so going to do so now. 3.1 here we go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Had no volume this morning long story short pulled and replaced battery fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
That's hilarious cause I use the H710 :p me and you share these weird audio issues. Glad to know it won't **** out on me during my 3 hour plus drive home.

I'll have a change log up tonight. It's move out day here so I gotta get goin', sorry y'all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gregthomas129:
Same here... dirty flashed and it broke gapps and the screen would not time out and go off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hytran:
LOL I've got an H710 sitting in a drawer somewhere. And an H700 from way back in my Moto Triplets modding days...

Good news is, there were no glitches using wired headphones and Poweramp so far this morning. Will check the dock audio on the drive home and also my Moto S805s when I get home.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
I agree with the comment above, often times for some reason audio will get saved as "unknown" and since the software doesn't associate "unknown" with any audio files there will be no sound. This happens a lot to me when I use the 3rd party app ZEDGE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
After you Dirty Flash you need to Re-flash your gapps package...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
flashed 3.05 dirty cause that's how I like it (except system was wiped, always with lots o changes and a new gapps entirely) - everything was fine EXCEPT for some reason my phone shows 1% battery all the time....I have an extended battery, so I tried both of my stock ones and nothing. Tried deleting batterystats.bin, nothing.

Hopefully this update will sort it out.

---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------

Why? Just set from your phone, it's like asking him to add your favorite playstore app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
Yup, Found the Advanced Settings menu, and Set the Color to Cold.. Now its Beautiful again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Wrong sir...if you read the PA 0day thread, it clearly states

[B]Is it necessary to reinstall GApps and/or addon modules EVERY time I update my ROM?[/B]
If your ROM supports addon.d backup functionality (most ROM's do - including PA), it's not necessary to install GApps with each ROM update - as long as you don't manually wipe the System partition. The backup script will backup your installed GApps (or Addon modules) and restore them after your ROM has been updated. However, it is a good idea to install an updated GApps from time to time as functionality may be added or improvements made.

That being said, however, I still follow the same list when updating Quantum (Unless its from 4.3 -> 4.4, then its a clean one):

NANDroid if I don't have a recent one

Wipe Dalvik, Cache and System

Flash Quantum v3.xx

Flash modular-mini-gapps

Flash KT747 Kernel

(optional) Flash SuperSu (I no longer do this cause the app remains and I just navigate to it upon boot and install the binary, it will need to be rebooted but I also can flash xPosed and viper and get it all done in a single reboot.

---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------

Good thinkin' :)

Always baffles me that people ask questions without checking EVERY possible even REMOTELY related setting category....okay it's obviously not in network,.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Actually, I've found that if you use SPEC-Gapps, you really do need to reinstall - it contains an additional set of optimization scripts that will be in conflict with the ROM if you don't.