yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hisroyalmooseness:
Solid for 3 hours. Disabled Focal and restarted. Camera working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
My boy pwncakes at it with a solid release, nice man!

:fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
If I flash this ROM can I comeback to official ROM?

Envoyé depuis mon SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
For some reason I can't download the ROM. Keep getting an error loading the page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Works fine on my desktop. Are you downloading from your phone?

ALSO

Flash this SU if you need to use Titanium Backup (TiBu) for restoring apps http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
i'll make a mirror (;

just incase it does go down. and for everyone also.

(; :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Where's a link for ROM? Or we just get 2 for gapps instead?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
rom and gapps are there? read, read, read! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Flash this SU if you need to use TiBu (or root access in general) http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip

Worked for me and credit to a user in the CM10 TMO thread for finding this fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
mirror for anyone having trouble downloading the file from the op, and for the sake of it. (;

https://mega.co.nz/#!DJsHzIZI!eqZwFwMjQAepkVPViBLeMWpxiRMoYg0_hdTVjZkOVCQ

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
(@OP, it might be a good idea to add this to the first post) There IS ROOT access. To enable root access, go to "settings>about phone" tap "build number" around 10 times. Then go back to settings, and tap on "developer options" and enable root access. BUT for TiBu, you will need to flash the superuser zip from a few posts above mine.

Edit: I will quote the post for less confusion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Yes from mobile. Had a feeling such is the case. Will download in the am. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Guess I'll have to try on PC cause all I see on phone is 2 gapps, cherrypicks and that mirror is useless on phone. I'll have to do it on a computer like a caveman lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
I just put my phone into Browser mode(using Chrome) and I'm downloading just fine. :)

EDIT: I'm also able to download thru the phone.

Maybe I'm misunderstanding the issue......
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
In app there's no ROM link. Have to use webview.

I'm retarded is the main problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickdoherty:
I'm running the 8/4 and camera is working great. I'm on a Canadian s3 if that matters.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
So am I and it isn't. That's also on a clean and a dirty flash. Very odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'm gonna fiddle around with the build today, debating on taking away the power collapse commit per Cyanogen's advising. Although it has been working without issue for us...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Hey Pwn thanks once again for these builds. Running 8/4 now.

I'm a member and Tester for Team VeNuM so I've had some practice testing and know my way around the device. If u should need another tester for future builds hit me up. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
So is everything in the Rom working except some funky camera issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yeah everything is completely working. Haven't had an issue yet!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zap12341:
So my camera is acting weird. When I go to the camera the camera is working fine except everything is black, but if I take a picture it comes out normal. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
Its been discussed several times its a know issue no fix unless you want to go to build 8/3 and have he battery drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Cool. Thanks for the quick response PwnCakes. Been looking around for something new to flash. Will probably check this out once the 8/5 release is sent out. Looking forward to checking this out. Appreciate your hard work. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickdoherty:
How old is your phone, mines only 2 months, maybe abit different hardware and you have focal disabled?

Sorry if I'm wasting form space or asking ?'s already asked. I just came from the desirehd and it seems over there that every phone has diff hardware even though they all have the same name.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DracoAzule:
Wifi doesn't work. Sorry but that in itself is a deal breaking bug for me as I can't be on mobile data all the time.

Will be keeping an eye on this however.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
You're the first person to complain about WiFi. I use it all day.

---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------

Mines 5 months. Focal is disabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'm currently building with the newest 3.4.56 kernel, gonna test it out without any cherry picks and then reintroduce the merges once I test it all out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DracoAzule:
Well I tried to do a factory data reset and redownload some of my apps that were force closing and that's when I started having wifi issues. Because it couldn't 'authenticate' when I tried to set my phone back up on my wifi network.

Also, when I tried to redownload said apps from Google Play I kept getting errors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] assaf.bm:
If you need anyone to test let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Did you go into WiFi settings and forget the network and try again? Some apps aren't 4.3 compatible yet. So the play store errors could be that at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caulton:
I'll do some testing as well:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
No WiFi issues here using it right now actually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
A buddy of mine had the same problem. His usb port died on him, but I think he took it back with CM 10.2 on it. He knows someone at the AT&T store though. LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
So far, the only issue I'm seeing is the camera black screen (I froze Focal). I get a black screen in the viewfinder, but it does take the picture properly. Considering that I barely use the camera anyhow, this is not that big a deal to me. Just FYI.

Everything else is working properly so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
1.25 ... this has become unpleasant. Bricked 3 times trying to get a stable configuration from a clean install. Up till 1.20 life was great but this last little push to 1.25 seems to have incurred a few quality issues. I don't know whether it's the CM base or the tweaks? I do know that I gave up on the CM nightlies prior to Quantum because the amount of bad code being checked in was too high. It's a shame CM doesn't have shorter release cycles that promote stable code quickly.

It seems like Pwncakes has put in a couple of all nighters trying to get from 1.20 to 1.25, building a new kernel and trying to integrate a significant number of features into the build. Too much? Too fast? The quality of the builds up to 1.20 has been what you would expect of a professional dev team rather than a hobbyist/student hacking in his spare time and have been very appreciated (clearly 200 pages and thousands of installs later).

I'm trying to be constructive but don't really understand where the challenge lies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaimesco12:
Too bad I can't flash it on T-Mobile s3. It always fails when I try to flash because it checks the build prop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
1.25 and Quantum kernel working great for me. Battery is excellent. Dirty flashed since 10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bountyman334:
This kernel works great for me and an on the tmo gs3 t999 running carbon 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krosa:
Is anyone having issues when taking a photo with the front camera? (any app), when I do my device reboots,

Clean flash, rom 1.25, kernel. 95

Is it cm related or is it me??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
The issue lies within CM code that I can't really change. A lot of commits they put out recently have been completely FUBAR. The only time you should see any bugs from tweaks is from the kernel, but even then that only affects QuantumKernel, not Quantum. I agree that 1.20 was probably the best, but MMS issues are what made me update the ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
1.25 Running really smooth here..currently testing new BMS kernel released yesterday..very smooth with the options I was looking for
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Do you recommend downgrading to lk3 bootloader or using newest mg2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
bootloaders, dont really change alot or even anything.... just use the latest mg2. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
For 1.20 does anyone know if there are issues/bugs/complaints with MMS from the CM source (nightly)? Seems logical that its possible to make the fix there and then carefully avoid any nightly source that causes issues, even skipping a CM release when problems are encountered. Back on Dorian's red pill (Cm7 atrix versions) I remember him having a similar overall approach. His number one goal always was 1)stability/usability 2)battery life 3)performance in that order. I'm not a dev obviously... So of course take these statements with a grain of salt of course. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
1.25 seems to be running well here along with the new kernel. Not sure about battery life as I haven't had it running long enough to fairly judge yet. However, I do have one issue to report. Bluetooth is working well but won't switch off. It'll go off for a second or two and then turn itself right back on unless I reboot. Is anyone else seeing this? Clean install on 1.25.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Edit

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
This was a issue previously.. I think back to 1.09 ? It was related to CM. I am not experiencing it with 1.19.

---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------

I think you can run it both ways... Without the kernel flash you will be running the stock CM one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Working on a new kernel update now... which basically just includes more overclock/underclocking!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TeflonMyk:
No issues with 1.25 for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corey103:
Tried this rom and flashed it. I love it. I installed it along side the Viper music effects and I've had no problems. The battery life is also very awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Anyone else having issues with WIFI turning off during deep sleep? I'm running newest build and Quantum Kernel, only change I've made to anything is i dropped minimum processor speed to 270.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I'm stable on 1.25 after 4 clean installs... Is there a way of getting linux to dump a log of what the os is choking on when it bricks? I'd love to be able to see why it's puking.

---------- Post added at 08:52 PM ---------- Previous post was at 08:44 PM ----------

... Rats... Hung again... Runs great till I reboot then soft bricked. Pain in the bum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I'm stable on 1.25 with stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
For all those having issues, raise your minimum voltages by about 50 mV. That should fix any problems until I can get something to work out later on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Reset voltages to stock... Scared to reboot. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'm just trying to narrow down the issue. I've removed UC, and the power collapse cherry pick to help retain some battery life, but hopefully it'll fix whatever reboots you guys are having. I'm gonna test it out some and then release it, or you guys can always check my d-h.st link ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I just did a clean install of 25/gapps/supersu with no additional software updates then rebooted immediately and straight to softbrick.

---------- Post added at 11:05 PM ---------- Previous post was at 10:55 PM ----------

I'm fubar... going to have to reset with odin and a stock rom and see if I can get back to some kind of consistent state.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well there's your issue... Don't flash SuperSU yet!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
QuantumKernel v0.99

Removed Underclock

Voltage fixes

Overclock raised to 1.8 Ghz

Power Collapse *reluctantly* kept in

FRandom module fixed

Added Smartmax (thanks aeppacher)

Attempting fixing up the kernel issues some people are having. WIPE CACHE/DALVIK

Please watch out when installing everything, I need reports only from 1.25 w/ .99 for now!

ANDDDD its down. Governors aren't working right for some reason. Gotta figure out what's actually going on here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] raymond26170:
Why not? I am not having any issues with SuperSU. 1.25 and .95kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
goin good so far with 1.25 nd 0.99 no lockups yet keeping fingers crossed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
I don't see .99 anywhere
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
I believe it was pulled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I pulled it because it went crazy whenever you activated a govenrmor besides interactive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
Oh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Thanks I missed that memo. 25 & .99 installed and rebooting normally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jndrad:
.99 ?

i dont see download for .99
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I have a working .99 that just doesn't have the overclock, and has the new 3.4.61 kernel. I'm just testing out battery life right now and making sure everything is stable... At least on my end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
.99b ;) ... Definitely running titanium backup before my next install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
QuantumKernelv0.99b

Kernel updated to 3.4.61

Voltage fixes

Power Collapse *reluctantly* kept in

FRandom module fixed

Added Smartmax (thanks aeppacher)

Attempting fixing up the kernel issues some people are having. WIPE CACHE/DALVIK

Try it out, should fix every issue present in the latest builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Flashing .99b to test it out. I don't really OC or UC much, if anything I prefer to UC for battery life but never OC. Is this with OC/UC removed completely? Or just UC? Or nothing?

You put out updates faster than I can fully get a charge cycle in! I like what I see though day-to-day, which is what matters to me. Still, best battery life would be my preference.

Also wanted to say I'm REALLY tempted to try AOKP with a custom kernel, but I'm sticking with this ROM for now cause I've never had problems with this ROM.

Will update when I flash.....95 to .99b

Update: Doesn't look like OC or UV was changed, maybe voltages but I still UV to 270MHz/1.35GH and drop all the frequencies by 50. Seems fine at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I have no restraint. Flashed without issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Hey PwnCakes, I was wondering, do you include any tweaks in Trickster to the interactive governer controls in a kernel flash? Cause I don't know what most of the settings mean and I was wondering if they were stock or your's.

Besides that do you do any tweaks in Trickster at all after you flash? I would assume so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Currently rocking Quantum v1.25 and kernel v0.95 (haven't upgraded to 0.99 yet). No issues so far. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
No tweaks for interactive, and all I do is switch off mpdecision, 384-1620, row, and 2048 read ahead. If you want to save some battery life, try pitting boost speed down to 810 MHz.

I'll be able to answer more in s little, its back to school time at work and I just finally got my break.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bountyman334:
Well try thanks...currently on carbon nighties 09/08 4.3

Gonna try on slim beta 5 in a few
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
.99b random rebooting like crazy on 1.25. Didn't tweak kernel at all. Wiped cache and dalvik. Flashed 1.25 and all good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I don't want to sound like a certain other developer on the forums, but I don't even get that problem! What is your lowest voltage when you use the stock kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ffwd4490:
Lol, made laugh. I'm not completely sure who you are referring to but,ya I think I do..... So glad I own the S3 now....

On a side note, I'm running 1.20 and at first it ran perfectly, but as the days go by the lockups and reboots have started to show up. Not that it's enough to cause me problems or anything, just putting it out there for you.

Keep it up , I for one love what you do :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Hopefully someone can help me out. Max frequency I can get on interactive / row with Trickster mod is 1512. Is there something I'm missing in order to get a higher frequency? Obviously there is so I'm hoping someone can point me in the right direction to make these changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhanamjay:
Looks like min setting 384 (CM's defaults) is missing processor's frequency settings and my phone's min @ 486. I guess that means more battery drain? Also noticed one or two reboots with 1.25 and 0.95. Although reboots stopped after changing min to 270. The same(0.95) settings in 0.99 as well. I am using "performance" in the settings app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
the only problem i was getting were lockups but that was 1.21 been on 1.25 for a full day nd its still goin strong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Hate to say it, but I was getting random reboots on kernel 0.99b, too. Quantum 1.25, minimum frequency 384 MHz, maximum 1620 MHz, SMARTASSH3 governor, nothing else modified. I've gone back to 0.95, which I've been using without incident. I have faith you'll get it right, though. ;)

(Hell, I'm not even up on which governor would be the best to use. I'm mainly looking for battery life. I don't play games other than Solitaire, and my phone usage is mostly calls, texts, blog reading via gReader, and forum reading via Tapatalk. Not exactly taxing stuff :), but I'd like to squeeze out as much battery life as possible while getting good performance. All of those governors confuse my widdle noggin...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
This might be of interest to you.

http://xdaforums.com/showthread.php?t=2031214
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Honestly the only differences between the kernels are the .61 update, and I bumped the voltages up, and fixed up frandom. The governor may have been the issue though, try out interactive or asswax instead. I use interactive myself and I notice I can get 1.5 hours of screen on without hitting 70% of use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Hmmm... okay, I'll give 0.99b another try, hopefully some time today when I have some spare time, and see about using one of the other governors. I do get a chuckle out of these names that others come up with for them. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
CPU Governers explained

I am in there with you. Just what does it all mean. Ran into this post earlier. I haven't had a chance to look at it. At first glance, it looks like it will answer our questions. http://xdaforums.com/showthread.php?t=2031214
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well if it gives you any issues let me know and shoot me a message, I think it may be an issue relating to standalone power collapse, as it seems to recently be starting random reboots on our chipsets for some reasons. I have personally never seen a reboot, but the revert of standalone power collapse can also increase performance, just might cut back on battery a little bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Well, I did a complete wipe and fresh install of Quantum 1.25 and kernel 0.99b, and while I didn't get reboots, I did get (A) the phone occasionally refusing to wake up when the screen was shut off, requiring a forced reboot (this also happened overnight while the phone was in my charging station, which drained my battery down to the mid-80% range); and (B) hanging during the boot animation, also requiring a reboot. This is a fresh install after data/cache/Dalvik wipes, no apps restored (it was happening during my "set things up the way I like them" phase), no other changes. So I re-flashed 1.25 and reluctantly went back to the dkp kernel (because my needs are pretty simple and the Freelunch governor is awesome on battery). Wish I had logcats and such for you, but since this is my only phone, I needed to get it back to working order ASAP. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Do you ever wipe system?! If that's not happening there's your issue. You can wipe system without losing all data as long as you flash a ROM on top of it.

There's also been some update to bluetooth that may fix those having issues in cars, but that requires a whole new ROM, and I don't really want to update unless I can make sure the kernel works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Honestly, I didn't wipe system because I've never had to wipe system, just like I didn't upgrade my bootloader until CM got a bug up their asses to require it because I never had to do it with any other Android device I've ever owned. As I've never had to do anything more than a data/cache/Dalvik wipe when flashing ROMs or kernels in the past, I think I can be forgiven for not thinking I needed to do it now. ;) But, I'll make a TWRP backup and try that next, though it'll have to wait until I get home because it's too time-consuming to sneak it under the radar at work. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
I had the same issues with my phone refusing to wake up on the last two quantum kernels. Before flashing the 1.25 update I did wipe /system. No issues at all with the stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well we asked for it and there it is. Seems like we got an update to mpdecision by porting it directly to the device kernel itself. I'll put out an update later tonight featuring the new mpdeciison, but it is also pretty new, so who knows what it will do in terms of stability and such.