yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joe777G:
HDMI output through the new Samsung 11 pin MHL adapter is broken on this ROM. It worked well under TW so it isn't the adapter. The TV is receiving some kind of signal because it goes from a blue screen with no input to an empty black screen after I plug in the MHL adapter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
he's asking for a comprehensive explanation of how cwm clears its data compared to stock tw. Not what is necessary to flash the Rom....I think

Edit: see below
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
when directions say to wipe data, it traditionally means to only do it within cwm, NOT the factory data reset found in the running android os settings section
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Task is my new hero.

Coming from an AOKP Captivate, I thought I was doomed to wait months for a proper release on my new phone.

For any Rogers users who have lost LTE since the 7.15.2012 release, the fix is just to add the Rogers LTE APN.

Here's the info:

APN - ltemobile.apn

Proxy - <not set>

Port - <not set>

Username- <Not set>

Passwors - <not set>

Server < not set>

MMSC - http://mms.gprs.rogers.com

MMS - proxy 10.128.1.69

MMS - Port 80

MMS protocol - Wap 2.0

MCC - 302

MNC - 720

Aythentication type - < not set>

APN type - either "*" or "internet + mms"

(Stolen from here.)

P.S. First ever post in a dev forum. w00t!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JusFig:
My bad
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
Romz running great Task..wanted to just wish you,Toonz & everybody a very Happy Thanksgiving!:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Dude, Thanksgiving was like a month ago. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
In Canada yes, but in US it's tomorrow :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I use a generic pair from Newegg.com that work great with music and phone, mic and all.:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merog:
HAPPY THANKSGIVING everybody!

And of course we give special thanks to Mr. Task for his awesome rom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
AT&T SGS3 Marble White

ParanoidKangDroid 1.4 ROM

KT747 11/13 kernel OC'ed & UV'ed

Medical Marijuana Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
This is a great example of don't. Just don't. Read the OP, and keep reminding yourself this is not a chat room. Silence is the best answer most of the time.

Happy Thanksgiving in the US, good luck everybody else :D My hovercraft is full of eels...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bigjim1488:
Look at you all johnny on the spot. I am just splitting the already split hairs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nuwayman:
Happy Thanksgiving everyone! @task. Hope you and your family have a great holiday!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Haha did you just contradict yourself there....

Shutting up now..

AT&T SGS3 Marble White

ParanoidKangDroid 1.4 ROM

KT747 11/13 kernel OC'ed & UV'ed

Medical Marijuana Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Happy thanksgiving task650

"Lead me, follow me, or get out of my way. "
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wiltron:
Fantastic ROM - My newest daily driver ROM for my GS3 747M on Rogers

Fresh install after full wipe and all that fun stuff - even wiped battery stats just to be sure :P

Seems front (home?) button doesn't wake up the screen, have to press it 2-3 times before it finally realizes that I want it to turn on - possible "black wake screen" bug you "hopefully fixed"? What do you need from me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jirv311:
Task would probably say he needs some search from you. This is a known "feature". :D

Sent from my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Believe it may have been kernel related for black screen problem, which KT is working on in his thread. Task is aware of the home button not waking the phone always and stated that it may be due to sleep cycles. Wasn't even that far back in the thread. Since this is the last 4.1.2 build, most of the information on "bugs" and fixes has been gone over for your reading pleasure.

Thanks KT and Task for your work and those that have aided during my reading of the thread and the OP. :)

Happy Thanksgiving to those in the US or abroad that are celebrating.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tbird57:
I believe this is normal(not for sure),complaints the phone was waking up in their pockets...this is the safety net for that not happening....

PS you can use the on/off button to wake the device up immediately.... :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This ^^^^^^^ made my day. ;) :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merog:
Go to setting > Rom Control > Performance and change your governor to intellidemand/deadline.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Task, happy t\Thanksgiving to you and your family. Hope you get to spend some good time with your little one... Not so little any more:D

and happy Thanksgiving to everybody else that celebrates it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thanks everyone. Happy Thanksgiving to you guys. Do this today. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
happy thanksgiving everyone! safe travel

-AT&T SGS3-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] teague:
Happy Thanksgiving!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
Im gonna try this out.. Hope it works cuz the home button working would be my dream come true lol. Happy Holidays folks!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Sorry, Danny, this won't affect the home button.

Intellidemand/deadline is a temporary measure to reduce the number of black screen wakeups.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Up your minimum voltage and see if that works for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
I give thanks for this amazing ROM and the dev who puts in so much of his time to make it awesome. Happy Thanksgiving task650!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Guys, just noticed something. I installed the ktoonsez kernel and it got rid of the bass over bluetooth problem. I guess the fix is because that kernel changes the bluetooth drivers. Just thought you should know!

EDIT: NVM see below
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I've merged any changes that are in that kernel into the kernel that I package into this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Yeah, came here to edit my post, because after disconnect and reconnect, bass was gone. Sorry, false alarm!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
I have had super weird headphone problems recently. My S3 headphones, the Mic doesn't work ever. My S1 headphone Mic works great. My third party set Mic doesn't work either. I'm also having issues with notification sounds breaking playback and it not resuming, (music stops for a text and doesn't automatically resume) even with headset button press, or the notification sound doesn't play at all if other media is on. Navigation sound plays simultaneously with media sometimes. I assume that's a channel issue.

I've done a couple complete total wipes and formats and the problem persists. 3 media players, one audio book player. My temp sort-of fix is to use headset button control (app) but it doesn't always work. (It auto answers the phone after 4 seconds and remaps button presses.)

I believe the issue is the headset Mic not getting turned on sometimes. I also generally can't increase or decrease volume with the screen off unless the headset has those controls, but randomly I can.

This isn't me complaining, just sharing data. I have a headset or aux-line in several hours a day for work, so I'm kind of all over it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I too use an aux line for about 85% of my day whether in the car or at work. Volume quiets down as it should when notifications come in and volume resumes when it should also. Navigation works fine for me too. Not sure why some have the issues. I tested with my Samsung headphones w/mic and they seemed to work flawlessly yesterday. Some also reported that they work fine. So all in all I'm quite unsure why a few people might be having these issues. I can't seem to replicate myself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
No problem man. I feel like it may have something to do with governor/scheduler too, I'm also way more likely to get black screen wake-up If I'm playing media too. Debating whether or not I care enough to re-wipe or just wait till next update. I'm on noop/pegasus in case anyone cares because that's where the battery sweet spot is for me.

Edit: oh snap I forgot I have voltage control not set on boot. That means I've been on cfq / on-demand for a couple days. Fixing that now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merog:
I found a bug with the latest rom, it made me eat so much turkey that I am about to explode. Once I can move again, I think I will revert back to the previous version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JusFig:
Hey Task, was wondering what governor/scheduler you're using (wanted to see if the headphones work under your settings) Thanks for the great ROM and hope you had a great Thanksgiving!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I believe that's a kernel issue. Please post it in the proper thread.;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Coblica427:
Just an update on the bug regarding trouble waking up from sleep.

I'm using governor smartassv2 and cfq io scheduler. I upped the minimum frequency to 486. The aforementioned configuration has yielded great results so far, not a single problem getting the screen to wake up. I'm more convinced it was the minimum frequency bump that has fixed the screen wake issue, not so much the governor/scheduler. Worth a shot if you're still having trouble.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
because i can. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aquethys:
Dayum. Drooling. Nice ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
Im curious to know what the changes are between 4.1 and 4.2 :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Curiosity can be killed by Google. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MColletti12:
Oh task, you tease...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
dayum i can smell fresh butter in the morning!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nexii:
I thought butter was with 4.1 jellybeans. You know pregnant Google....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wickidmasshole:
I have to work today. But the 4.2 teaser keeps my future bright.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] derberts:
I can confirm my stock headset works fine as well as another aftermarket headset - mic and all controls.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aalh:
Hurry up and flash 11/18 so Task will release the next one :laugh::good::eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merog:
Damn! What a teaser. lol

Is there gonna be a black Friday version? j/k most likely not.

Task, I know you dont like when people ask about ETA. But now that you have had a chance to take a look at 4.2, do you think it is gonna be days, weeks or months before you release the first one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
There you go....day off task ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merog:
He deserves to take a day off ;) At least on black friday to digest all that turkey ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
years
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
I was gonna say I hope it takes at least weeks. Or possibly months. Tend to like things done right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
If task and kt post it its done right :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
Do you find you have to do a lot of extra work to refine 4.2 to your liking? Or is the integration pretty easy thus far?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
its not easy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbmd:
Take your time like always I am sure it will be great!! My thanks are to you and kt.

sent from Task & KT JB AOKP ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moedin:
I picture task working away, underwear et all, at 4.2 like a Dr Jekyl genius!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tbird57:
LOL this should get the answer award of the year... :good: :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roughneckboren:
I like to picture my task as the lead Singer of lynard skyward with a band of angels behind him.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A Ham Sandwich:
I'd rather get the stability, reliability, and well-roundedness of what we've come to expect of the most recent 4.1.2 efforts by task in the 4.2 releases than have him pump out something not-as-awesome just to change the version number and appease The Horde. Which I'm sure is the plan. I'm looking forward to it and I'm glad I have the 11.18 release to keep my phone working as well as it does in the meantime.

That said, I'm still gonna be checking back on this thread oh... at least 10 times a day LOL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moedin:
I like to picture my Task coding in a tuxedo tshirt because its a formal tuxedo so it says im professional and classy, but its a tshirt, so it also says im here to party!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merog:
No problem task, take your time. We are gonna stand right here and wait patently for you to finish the job and release it when you think it is ready.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
You can stand all you want I'm gonna grab me a couch and lay down. It will be fun reading all the posts about 'hey task how's 4.2 coming along, and do u like it'

Bwahahah.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BaconStep:
I like to picture task as a ninja fighting off evil samurai
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
I like to picture my Task as a little baby Jesus in his manger coding Android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
This being a CM10 hybrid, aren't we essentially waiting for that team to deliver cm10 with 4.2, for these guys to work from
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Nope. This is built fully from AOKP source, which is completely different from CM source. Not sure what you're playing at...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) This isnt a CM10 Hybrid. Not sure where you're getting your information from. This is built from Google source and AOKP Team does use some CM10 code.

2.) I have source right in front of me. I don't need to wait for anyone. I've already got 4.2 AOKP built and running on my Nexus 10. I didn't wait for anyone. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
Thx for the clarification, I interpreted the second sentence of the OP as indication of a dependency.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
interpretations are funny sometimes. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frankrocks:
This seems to be MY only issue... when receiving picture texts it covers a section of the message... leading me to be unable to read the message.

Other than that.. awesome ROM :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Actually, that means you have two issues - the one you listed, and a complete inability to search a thread :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
Even if you take years I'm sure it will be well before Samsung. I expect 2014/2015 release of 4.2 if they don't scrap the S3 and move onto the S4 by then. That's why we the customer need people like you to keep our device current since most are locked in a 2/3 year contract, but thankfully i get yearly upgrades.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mspayde:
Don't care, it doesn't matter, but thank you for AOKP and all of your hard ass work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baddison:
Thanks for all the hard work. For me - this ROM is perfect! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] merog:
Sweet! Very happy to hear that. That means you are close :) Hopefully S3 is your next target ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] |flyte|:
Feel free to cut a 4.2 build for your loyal tab 10.1 followers....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Don't worry I have the same problem and I tried searching for the solution and I couldn't find it. Just gotta live with it I guess. I tried searching for "sms" and "text message" and read the hundreds of posts with those words in them. Tried clearing app cache and data with no luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
I feel like Task can say anything, and 3-5 people will hit the thanks button on it :D

---------- Post added at 05:33 PM ---------- Previous post was at 05:30 PM ----------

haha.. good point Task! lol.. time to figure this 4.2 out :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mr. Janderson:
Sir that's because yours is an MMS issue, the solution has been posted several times in this thread.

Go to APN Settings, and change:

Authentication Type: None
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Thanks for the help even though I didn't complain or ask for help. In light of your post I searched again using "apn" and "mms" as keywords and still couldn't find the problem I have. All the solutions I found involved problems with receiving mms texts. Just sayin'..... I DID try at least :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You were mislead. You were correct earlier about waiting for a fix. There isn't one yet. I think some are using 3rd party apps from the play store for now. You could do that if it is a huge issue fo you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Just tested turn-by-turn nav with bluetooth connected in the car and volume was very low, could barely hear the directions. I tried lowering then bringing the volume back up, muting it, shutting off the music, etc. Nothing did it. Anybody else experience this? Any fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Task650! How often do you go out in Portland?

I'll buy you a beer.

Dubstep Tuesday at the crown room!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I live and work in Portland. So I guess I go out here everyday. ;)

P.S- I don't drink. Last time i did was years and years ago and i ended up in prison for 4 years. Done with that sh$t. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kamandor:
For anyone with the MMS bug where the picture overlaps on the text message, just flash the MMS.apk from the 10/21 build, I've uploaded it here: https://www.dropbox.com/s/etrvtw7b0t6cogd/Mms.apk

Cheers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're probably around the 10th person to post this. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Respect
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
This falls under the category of 'no bass A2DP'.

Temporary workaround is to connect Bluetooth, then dial a call (any number - I use my voicemail).

End the call before it connects, and Bluetooth audio will return with proper volume.

I've found that this workaround sticks for quite some time.

For example, last night I hooked up A2DP and had to use the workaround to get proper audio. I then turned off Bluetooth and watched Skyfall (which was disappointing). Upon returning to my car, Bluetooth audio worked properly as soon as I connected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
Officially calling BS on this post.

...skyfall was great! :)

-AT (mobile)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madseven:
Thanks! That is awesome to hear:good:

---------- Post added at 03:08 PM ---------- Previous post was at 03:03 PM ----------

aaawwwweee but you lose the theme ability:crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yep. Most people just post unsupported things before thinking about the consequences and how it could and will break things in the current releases. Not to mention it causes issues and more work for me in this thread. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
I tried that, multiple times, and volume didn't come back up. Music is fine though after call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scarfacecjm:
The only issue I found are the random reboots. Except for that everything works perfect for me!

Gracias!

Galaxy S3 @ AOKP 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thats on your end. I don't have random reboots. you need to figure out what you're doing or what you have on your device thats causing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drock212:
Only time I get reboots is during long periods of gaming. That's literally the only time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
Same here, I get constant reboots when gaming, the battery gets very hot, then it reboots. I tried underclocking the phone, same result. I don't really mind, cuz it's rare I play 3d games on my phone, mostly on my N7

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Try an undervolt

AT&T SGS3 Marble White

ParanoidKangDroid 1.4 ROM

KT747 11/13 OC'ed & UV'ed

Medical Marijuana Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crystol:
Toggling tablet mode under UI options send the device into an infinite boot loop. Tried twice--both clean installs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flip3d:
I get a reboot when I watch youtube videos longer than 20 min. Like right in the middle of the vid it restarts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
I get a reboot when I long press the power button and hit reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
Happened to me as well. Also happened when I tried paranoidkang.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twanskys204:
Nice display pic shacker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ima.monstaaa:
I rarely encounter the black screen on wake issue regardless of what governor/scheduler I use. I think it has more to do with the phones hardware, more specifically the CPU. As a lot of PC geeks will tell you, not all silicone is equal. Some CPUs may perform better than one made in the same batch. That being said I think I've had the black screen twice in the last two weeks of using only this ROM. I got it twice in one day and reflashed and set to intellidemand just to see if it would solve it and found I get incredible battery life on that governor (I'm currently at 53% on 11hrs), so I kept using it. As I said though regardless of the governor it hasn't been an ongoing issue for me, which makes me think its going to yield different steps for each phone to solve the issue entirely.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slackercow:
do you have any proof/reasoning besides "all cpus are different"? more likely there are other apps/options/software that is affecting the screen not turning on. my soft-buttons light up and i can unlock the phone, the screen just doesn't turn on.

anyway, chalking up something like this to possible differences in CPUs makes no sense.