yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
I think I've narrowed down my sod problems to the intellidemand governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I managed to hang phone by texting and taking 2 pictures using focal. If I take the pics first and then attach it works fine. This version is nicer than. 20 best Rom yet. THANKS AGAIN
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
Focal never works for me I remove it right away after everyflash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Has anyone found the best kernel for battery life? I've tried SmartassH3 and asswax, but I haven't found the best one yet...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rob_z11:
I am using all the settings that ops have recommended, and using conservative as the governor.

Pretty decent battery life I don't have to have the blazing speed and screen changes as long as battery goes all day and wife is happy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
i'll post a zip with the newest update that you guys should all flash. It brings you to the latest firmware and modem, so that I can narrow down these crashes. I'm working on an update as we speak, and it's even faster than 1.5 due to one simple cherry pick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jbusyy:
1.5 is working awesome for me (i have only used 1.2 since the other versions were buggy for me).

No SOD and amazing speed. Battery is the best I have ever had on any rom hands down. Phone has been off charge for 14 hours, 2.25 hours screen time, with bluetooth streaming - I'm still at 38%!!

I'm under volting by 35, MP decision off, touch booster off (not sure if that matters since MP is off), using wheatly governor.

I may try SmartAss3 and Badass, but Wheatly has been pretty good. Normally I used Intellidemand.

The only issue I had was sound (notification/ringer) disappeared once, but after i played a Mp3 is came back.

Thanks Pwn!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dc5ftw:
Awesome!! Is it gonna be just the update or the whole Rom?? I haven't flash 1.5 yet so I might as well hold out for the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Will we still need to flash this zip even if we did the 4.1.2 OTA before flashing this ROM? :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Nope! That's why you aren't seeing any reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Oh, silly me :p thought that was because of the rom...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
I'm on MG2 but since it's gonna be faster. Gonna update. (:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
I can't wait.. Good job pwn
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
1.6 is up!

First BTW at the download. (;

Tapatalk IMG quality sucks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
. Mmm 1.6....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
Just waiting on release notes :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
He updated the boot loader and modem. And he added a cherry pick that will make the device FASTER and last longer. I think. (:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dc5ftw:
No you ain't first with that damn Texas dial up connection!!! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Confused Face? Lol. Didn't get the joke. (; Texas has sh*t connection though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Mostly a boring yet incredibly speedy update. MAKE SURE TO DOWNLOAD THE FIRMWARE UPDATE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dc5ftw:
Lol my wife is about to go in labor and I'm on xda about to flash the update. Omg better get off xda now lololol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
1.35... No custom governorz

---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------

... Ignore that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
DevHost is Slow. Lmao.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Mostly a boring yet incredibly speedy update. MAKE SURE TO DOWNLOAD THE FIRMWARE UPDATE.

I'd warn people before you have blindly have them flashing bootloaders. D2ATT PHONES ONLY ALSO. NO CANADA OR T-MOBILE!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
Lol probably a good move to get off xda. Best of luck man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
If I have to tell people who are in the ATT forum not to flash a bootloader for an ATT phone, they should start reading the rules first. I can handle newbies up until a certain point, randomly installing things is akin to installing an anti virus from some guy in Israel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Just putting it out there. Just so that guy can't say he didn't know. Getting ready to clean flash in a few.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Rogers

I747m (canada) Rogers is not significantly different from d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Would it be bad to ask in what case it's necessary to flash firmware update? Just all AT&T do it, it's not going to hurt anybody?

I only ask cause I've been on 4.1.2 ROM's, 4.3's etc, with no trouble to my knowledge. (Other than custom kernels not liking my phone) :D

PS. And I'm on MG2 modem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Strobe in torch actually works in 1.6 :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rob_z11:
Pretty sweet looking update. Icons are crispier and looking very smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
WOW THAT UPDATE HARD BRICKED MY PHONE 747 M!!!!!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
No complaints
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxSTEROIDxX:
What update? the 1.6 or the bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Boot loader. DO NOT FLASH THE BOOTLOADER IF YOU DONT HAVE THE I747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well unless you flashed the bootloader then you shouldn't have ran into any sort of hard bricking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxSTEROIDxX:
How do you flash the bootloader? download to sd card and then?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Download to SDCard flash like a regular zip and flash ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxSTEROIDxX:
bootloader first then rom then gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Yeah. (: WIPE before installing. Clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxSTEROIDxX:
Awesome!! "thanks" button has been hit!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I already upgraded to the UCGMD2 bootloader and modem some time ago, so I'm assuming that I don't have to flash the one you provided, yes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Yes sir!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
That's what I thought, but it's always best to make sure. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Unless you did it directly through AT&T's OTA then no, you don't. This also flashes the latest firmware for the radios and such.

If you flashed a 4.1.2 zip then you didn't get the firmware, if you went through OTA, then you got it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxSTEROIDxX:
just updated and this thing is very fast!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Huh, I used a method here to flashed the whole update in Odin, I installed 1.6 without the bootloader update and everything seems to be working fine. Thanks for a great rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Flashing through Odin is the same as OTA essentially. So you're all good!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Alright for some reason I started doubting, even though I knew there was no problem.. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
The newest firmware helps stop the power collapse timeouts. At least that's my assumption for now, we'll see how it fares with 1.6!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Does Instagram video recording still freeze and reboots?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update. So this latest release, your focus is towards battery or performance? Some time back, your focus was towards the battery on the cost of performance which I love to have on my mobile. Recently your focus seems to have moved towards OC/UV which not all mobile can handle efficiently. So just wanted to check on your current focus area
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
woke up, did a clean flash and now my phone is bricked

no sign of life not even the little viabrate.

i will have to send it into repairs i guess...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dankaren:
Hold down the power button for 10 seconds or pull the battery. It's not bricked!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
i did everything, even put a new battery in. i have been bricked before so i know what its like, and this is it sadly :(

i have a warranty that covers all physical and internal damage so i will be fine, ill just be away from the forums for a little while when i am on the loner phone they give me :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rhealeyogden:
Just a heads up for all the i747m users. You can safely flash 1.6 however you can not flash any new firmware versions for the d2att. That will cause the brick.

I747m running 1.6 here. Dirty flashing since the start with no issues. Great performance and battery. Keep up the great work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joshuagalipeau:
there was my problem... :( :( :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Reinstall "stock rom" with Odin and start again. Nothing done that can't be undone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's still on battery, but adding in everything else is just like adding extras. You can choose to use it or not. People having issues are actually related to the battery life tweaks, not the performance issues.

Whoever can run 1.5 and up and couldn't run a kernel messed up in their end, it's just about the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
question have anyone tried using a theme yet ??????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] casianm:
[MENTION=358715]RobertFontaine[/MENTION], by "stock rom" you mean the i747M stock correct?

How can I Odin if the phone doesn't turn on? i747M user here and got bricked coz of the modem I believe.

TIA!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
You mean a Theme Chooser theme? I use 'em all the time. In fact, I use a set which I created for CM10.x that I simply haven't gotten around to doing anything with; there's always something new to tweak with them!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Running Cobalt Crimson just fine!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
battery

no matter what version i run or what rom i use i never get more than around 3 hours screen on lol. Where would i be seeing better performance? when im NOT using the phone? i always wonder how some people get 20 hours on battery. im guessing their screen is on for maybe 20 minutes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
ohok thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polsonov:
My phone can't handle the power collapse. Always needs a battery pull after a deep sleep. Any suggestions? Stuck using dkp kernel for the time being.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Pull battery ... Put it back in

remove USB cable if plugged in.

3 finger salute power, home, down arrow.

Current stock modem/rom is mvldmf1 for i747m. Google is your friend.

Pm me as this is getting off topic and there are many many unblinking threads already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
what i did was follow the op setting, change governor to wheatley and change the max to 1512 was getting lockups on 1620 phone been in deep sleep for about half hr now.

---------- Post added at 04:32 PM ---------- Previous post was at 04:04 PM ----------

can someone point me to some good themes, i tried the Reborn theme but got a booth loop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wiltron:
Also a hard brick after the firmware update..

You can't state it's for lack of reading, because the forum is titled AT&T, Rogers, Bell, Telus Samsung Galaxy S III.

I also don't see in your OP, or in the latest 1.6 release posts, anywhere that states it's NOT for Rogers, or specifically state anywhere that it's for AT&T only..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
I use Betterbean Blue and I like it. It blacks out a bunch of apps, and doesn't add any unnecessary crap to the look of the device. The dev has a bunch of other colors to choose from if you don't like blue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
thxz:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jbusyy:
Hmm, so dont update 1.6 if I have a Rogers S3? If it is bicking devices, shouldn't this info be in the OP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for your response. What will be your suggested settings(governor, rom) for best battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
1.6 runs fine on Rogers s3. Installing the att modem in the US bootloader is not.

There is a minimum bit of reading required before you start pissing with your phone's roms
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
The "d2att" didn't give that away? The forum title is irrelevant. If you have been flashing firmware for Rogers, then you would know that any firmware that isn't labeled as "i747M" is not going to be compatible for your device. Period. Also, it does state at the very bottom of the first post "Quantum for d2att". The ROM itself DOES work with the i747M devices, but the firmware has to be for the same device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wiltron:
The OP's signature states that.

For anyone with signatures turned off, or users browsing from mobile sites, Tapatalk, etc, that hides signatures, the information is not shown.

d2att is nearly the same as the Rogers version, and to date any d2att version of CWM 9, 10 and up have all worked flawlessly, along with all other rom's I've tried previously. Task650, Paranoidandroid, Paranoidkangdroid, MUIU or whatever it's called, Slimbean...the list goes on..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jbusyy:
The problem is that the OP says "download and install this" without any notice that it should be for ATT devices only, or even a description of what it is. D2att doesnt give anythign away because all roms that I have seen are always labelled d2att, which work on Rogers perfectly.

My point is any ATT only addons/flashes should be specifically labelled, to avoid bricking issues people have now. We are in the S3 forum for all i747's, not just ATT devices.

I'm not trying to be a troll here, just voicing a concern.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
You're missing the point and confusing firmware with ROM. Firmware updates are hardware specific. In other words, if you come across a firmware update and it says "i747" and not "i747M", then don't flash it. You'll soft brick the device and only Odin'ing back to stock will rescue it.

You are trying to blame the ROM when it isn't the ROM or the dev's fault. It's the fact that you flashed a firmware that wasn't meant for your device and you did it without looking closely at the file name. That's the issue here; not what is in the OP or not. If you aren't checking files, MD5 sums, etc before flashing, that's on you, not on the ROM or the dev. We all do this at our own risk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
If you really are hard bricked. Probably not. Google is still your friend. The att bootloader is still bootstrapping the same hardware. Modem software is what hangs it so is usually a soft brick.

If it is a hard brick you can still mount with a linux vm and flash rather than needing a jag. I've burned att modems to my 747m a few times and was always soft bricked.

Google.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
I will repeat myself; if you are flashing a firmware update AND NOT checking the file name for said firmware update and verifying that it is for your device, that's on YOU. Not on the dev. The firmware update in question is named "I747_UCDMG2_Firmware_Modem.zip". If you aren't seeing i747M there, it's not for a Rogers/Telus device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wiltron:
Actually, this is the dev's fault.. Look at post #2254, or the attached picture of the same post if you don't want to search through the previous posts. All it says is "DOWNLOAD AND FLASH THIS". No where does it state that it's only for the ATT Variant, when it's posted in the global i747x forum.

If a rom is compatible with d2att and I747 and I747M models, and the developer states in big bold red caps "download and install this", then everyone is going too. Especially since all previous releases have worked fine and mostly flawlessly (aside from software/battery issues and what not).

It's on the developer to state "this shouldn't be flashed on I747M devices"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
Yup. Saw that. I, unlike you, looked at the file name first and know that my device is an i747 and not an i747M. I also double checked the radio thread here: http://xdaforums.com/showthread.php?t=1831898 to verify that the firmware update is compatible with my device and what the latest is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jbusyy:
Wiltron, Agreed. All the OP needs is a disclaimer the file is only for ATT. i'm sure 99% of people would agree with that, except dotnetguyaz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wiltron:
I'm not the only one here who is having this issue though..

The OP can't really expect users to have that level of scrutiny when it comes to flashing a ROM.

It would be like asking for a criminal background check on a girlscout who comes to your door to sell you cookies..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
good + not-so-good

1.6 + new firmware working well. V. preliminary battery life observation: Quite good compared to what I've mentioned here before.

---

I still have the issue mentioned long ago, when the dinosaurs roamed the earth. I can't reboot w/o going into recovery, backing up data, wiping data, and restoring data, or some combo of that where data gets wiped. Without that, rebooting will just hang in the reboot (bunny) splash screen.

I think this must be a cm10.2 thing. I have old 10.1 backups which will reboot fine.

I've never seen anything else like this. Google yields quite a few posts from various sites with similar symptoms, but none exactly the same.

Of course, maybe my phone has decided that cm10.2 is to be resisted.

I mention this for the record, and of course on the off chance that someone may know something about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
Well, then everyone should be researching BEFORE flashing anything to their device. Seriously, does no one take into account that these are literally hundreds of dollars worth of electronics in your hand? Would you just throw some liquid gunk in your gas tank because your mechanic said "QUICK! Pour this bottle of liquid into your tank!!!" without at least reading the label on the bottle first?

The responsibility is yours to ensure that you are flashing the correct files for your device.

---------- Post added at 10:19 AM ---------- Previous post was at 10:14 AM ----------

It's been like this for years and a MAJOR aggravation for us devs that do this with our free time. You can't be bothered to look at the file name is not my fault. That's on you. The file name clearly states that it is for AT&T only (i747 versus i747M).

The OP shouldn't have to expect anything. He should be able to put out a ROM knowing the the users are experienced enough to research what they are doing. He's doing this in his spare time and for free. Because you want a disclaimer and can't put in the same level of effort is a paltry excuse in my opinion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Maybe so, but why are you so adamant that PwnCakes adding a simple "only flash this on I747 devices, it will brick I747M devices" is the coming of the Apocalypse? What is wrong with accounting for human error and taking a simple, one-sentence precaution? Any developer worth his salt does that. Now, if a user reads something like that and still flashes it and bricks their phone, then they deserve to be read the riot act (as would anyone who refuses to read simple instructions and does something they shouldn't), but this wasn't done, so some slack should be cut. Copping a Typical XDA Obnoxious Member attitude isn't necessary (I know of one thread that's filled with those types, including the ROM developer himself, which is why I'll never use anything he makes).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Think op should post the usual xda rules on bricks, wars which may erupt after flashing the rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wiltron:
If that's true, then why has no one thought to change it? Why has XDA not separated AT&T into it's own forum, separate from the M users? Why have the obviously frustered development members not *****ed and complained to XDA that users are yelling and screaming at them for bricking their devices because i747 is amalgamated in with the i747m users?

Why did Samsung code their device short-name to have ATT in it, for a different carrier, when they're apparently completely different?

Why has a google search of "hardware difference between i747 and i747m" given me thousands of results stating there is no difference other than carrier designation, and the hardware is the same (omitting the 9300 from results as that actually is hardware independent)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jbusyy:
Thank you. Mistakes can happen from both dev and user. The key is to have clear communciations / disclaimers / labels to minimize them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x0ne215:
Guys, relax, it's not that serious. Just be careful next time.

I've stayed on 1.20 simply for all the issues on the newer builds, is 1.6 stable? Forgive me for asking something that's most likely already been answered, but I've had some pretty bad food poisoning the past week or so and cbf to go looking through posts right now, especially with the ranting.

Thanks in advance :).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
For me Yes, no more SOD's haven't had any other things come up. Sleeps and Wakes well with no issues. No FC, random reboots of the sorts. Still early but looking and acting better than 1.5. For me atleast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wiltron:
For Rogers, and other i747M users who flashed the wrong modem

Fix is found here: http://xdaforums.com/showthread.php?t=2369125

It's a long, drawn out process, and I'm in the process of doing it myself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
For me (currently on 1.5), I've noticed slightly degraded battery life since moving throughout the various versons. It peaked at v1.20, I think, but 1.5 has been a bit of a disappointment (all things relative, because this ROM is kick-ass for battery life overall!).

Is 1.6 a step forward or backward from 1.2x through 1.5?

Since 1.35(?) I've been running PwnCakes' own settings based on his post a dozen pages ago. Usage of the phone hasn't really changed one way or another.