yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
No, probably not till Monday. I'll do one first thing Monday morning if I can.

Haven't heard anybody report if the fix actually squashed the bug yet.
[Verizon Samsung Galaxy S III] Cosis_94:
Just yesterday my screen began turning on without any prompt. No notifications or anything else going on that I think would cause this. It would just turn on and show the lock screen. Happened both when plugged in and when not plugged in.

Today I did a complete wipe and reinstalled the 10/29 build, didn't add any additional apps yet, but the screen in still turning on for what appears to me to be no good reason.

Does anyone have any ideas about what could be causing this? Any help is appreciated.
[Verizon Samsung Galaxy S III] mastamoon:
Try freezing the ROMdB Dev Tool app and reboot.
[Verizon Samsung Galaxy S III] Cosis_94:
Wow - thanks so much for the quick reply Masta!!

I've restored my backup and tried your suggestion. It's been over an hour and I have not had the screen turn on unexpectedly. This appears to have solved my problem.
[Verizon Samsung Galaxy S III] Hybridnoob:
Any chance of you putting out another build today?
[Verizon Samsung Galaxy S III] mastamoon:
Yah, had a bit of work to do when I got back into the office on Monday, then was off Tuesday for election day. Ill get a build out today.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks! Have you figured out which phone you're moving to yet? I'm guessing your time is running very short with this phone.
[Verizon Samsung Galaxy S III] mastamoon:
Waiting to fondle a Nexus 6... if not that, im not sure. Maybe the Droid Turbo, but not on VZW.. the Moto Maxx if it hits Tmo/Att. Basically a 5.2" Nexus 6.
[Verizon Samsung Galaxy S III] dmginc:
Not on VZW because of the locked down bootloader?
[Verizon Samsung Galaxy S III] mastamoon:
Yah.. I mean another carrier isnt guaranteed to have an unlocked bootloader either but, either way I wont be buying on release day so will be able to see before buying.
[Verizon Samsung Galaxy S III] dmginc:
Stay on Verizon! Don't leave me :'''( I'm eyeing the Turbo as well.
[Verizon Samsung Galaxy S III] mastamoon:
Really with the Turbo/Maxx didnt have painted on capactive buttons... really dont like those. Love the ones the sgs3 has.
[Verizon Samsung Galaxy S III] thelangosta:
I bought a used HTC one m8 that is already unlocked, rooted and converted to Google play edition. I'm learning a whole new language on those forums what with s-off, RUU, etc. The camera is weak but oh those front facing speakers are great. I can't stop watching music videos and stuff off the Red bull app. No more vzw for me in another week or so. On vzw the turbo is probably the best. It might be the best phone period.
[Verizon Samsung Galaxy S III] dmginc:
I actually just wiped my phone and installed today's build and am having my screen turn on randomly too.
[Verizon Samsung Galaxy S III] mastamoon:
Freeze the RomDB app. Mine went away. Something must be up with the service. I noticed the rom details were missing when I opened it.
[Verizon Samsung Galaxy S III] dmginc:
The camera also seems to be having major issues now too.
[Verizon Samsung Galaxy S III] mastamoon:
I just took a bunch of pictures on today's build, what issues are you seeing?
[Verizon Samsung Galaxy S III] dmginc:
Keeps crashing, and then will do the whole "Can't connect to camera" thing.
[Verizon Samsung Galaxy S III] mastamoon:
Gonna need a log of the crash if its still happening. Download syslog from market. Reboot, make cam crash, load syslog, take log.. post or email to "my-xda-username"@gmail.com.
[Verizon Samsung Galaxy S III] Perseus:
Did you do a factory Reset before testing camera ? Restoring Apps' data or dirty flash sometimes does that. If unchecked, you'd have to go back to Stock to Reload Camera drivers. So try a reset first.
[Verizon Samsung Galaxy S III] dmginc:
Just sent it.

---------- Post added at 09:24 AM ---------- Previous post was at 09:24 AM ----------

I never restore from backup. I just did a clean install of his latest build.
[Verizon Samsung Galaxy S III] mastamoon:
New build uploaded.. for everybody that had to freeze that RomDb app.

http://mastamoon.truelinux.net/ROMs...cm-11-20141106-UNOFFICIAL-mastamoon-d2lte.zip
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Now your welcome message pops up every 3 minutes instead of the screen just turning on automatically. Lol. Just freeze the app again until you can sort this out? Anyone else having the same issue? Thanks
[Verizon Samsung Galaxy S III] dmginc:
Did you get that camera log of mine, Masta? Was it helpful at all?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I got it and handed it off to our device maintainer. At this point in cm11 IDK if many resources will be put into 4.4.4. Guess we will see if the issue carries over. But like I said, I'm not having camera issues and it doesn't seem to be a overly prevalent issue here on the forums.
[Verizon Samsung Galaxy S III] mastamoon:
I talked with the RomDB guys and they said they found a few issues after I emailed them and think they squashed it. But it was going to take 24 hours or so to fully roll out.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Kewl. Thanks for looking into it. ?
[Verizon Samsung Galaxy S III] dmginc:
Just did another clean install and still having the same issue :/
[Verizon Samsung Galaxy S III] twistedillutions:
I want to add reboot to recovery. Wen i i press and hold power button. Is there away to add it?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Settings>Developer Options>Advanced Reboot then select Advanced Reboot. [emoji1] Enjoy
[Verizon Samsung Galaxy S III] mastamoon:
The issue with the ROMdB app seems to be fixed. Ive had it enabled for a day and no wakeup issues to be seen. No multiple messages either.
[Verizon Samsung Galaxy S III] twistedillutions:
What could be causing my fone to run slow? Opening settings browser apps etc?? Could it be cuz multi core is at 0 or (see attachment) animation is at 1.0
[Verizon Samsung Galaxy S III] NoCrAppleHere:
[MENTION=2963287]mastamoon[/MENTION] after latest build install, phone boots and Com.Android.Phone force closes. Nothing works. I reverted back to 11/10 version. Anyone else have issues?
[Verizon Samsung Galaxy S III] mastamoon:
I installed it before pushing.. no force closes. Hmm.
[Verizon Samsung Galaxy S III] Darryl Henley:
Exact same problem. com.phone.android closes. rolled back to 11/10
[Verizon Samsung Galaxy S III] mastamoon:
Hmm. What steps did you use to install? I dirty flashed, nothing wiped.
[Verizon Samsung Galaxy S III] Darryl Henley:
boot recovery, install rom, clear cache, clear dalvik, reboot.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'having trouble with tapatalk and even Xda isn't running properly now. Okay, I dirty flashed and I always wipe the caches. I'm using Nova Prime. Anything I can send you to help troubleshoot for me & Henley? Thanks
[Verizon Samsung Galaxy S III] Darryl Henley:
did the same install again and 11/12 is working, strange.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'll give it another try and report back. Thanks ?

---------- Post added at 06:25 PM ---------- Previous post was at 05:43 PM ----------

Okay, I'm good now too. Only thing I did was re-download the rom from the link in the OP instead of from the Dev Tool. Odd but all systems go now, so ???

Thanks [emoji1]
[Verizon Samsung Galaxy S III] Darryl Henley:
com.android.phone started closing again. gonna try to troubleshoot it.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Sorry to hear that. Hopefully you remedy it and hopefully it doesn't happen to me. Lol. Keep us posted.
[Verizon Samsung Galaxy S III] Darryl Henley:
[MENTION=2963287]mastamoon[/MENTION]

Attached Logcat for com.android.phone stopping.
[Verizon Samsung Galaxy S III] mastamoon:
Wonder if this is causing it.

http://review.cyanogenmod.org/#/c/76616/

Not sure why I don't have the issue though. Has anybody noticed when going back to an older build if the get an sms message soon after?
[Verizon Samsung Galaxy S III] Darryl Henley:
I don't get an SMS, but looking at the Logcat it says "Unable to start service Intent { act=org.codeaurora.ims.IImsService } U=0: not found"

Edit: masta you right, looks like they already logged a bug on this problem.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Guys, can I ask then why I haven't had this happen to me or is this inevitable?
[Verizon Samsung Galaxy S III] Darryl Henley:
idk, i'm back to 11/10 for now.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Tried 11/13 build and same problems for me as with the 11/12 build. Anyone else? Henley, still having issues? Thanks
[Verizon Samsung Galaxy S III] mastamoon:
Maybe you should try wiping dialer data before installing? You have tried installing without wiping caches m stuff right?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Will try that now. Ty
[Verizon Samsung Galaxy S III] Darryl Henley:
11/13 working, right now. 11/12 went bad after a few hours yesterday, wait and see.

---------- Post added at 04:16 PM ---------- Previous post was at 04:08 PM ----------

com.android.phone is stopping again. when the screen is locked, I don't get the message. as soon as the screen is unlocked the message starts.

I am using Nova Launcher, i wonder if that could be a problem.
[Verizon Samsung Galaxy S III] mastamoon:
I'm using nova also.

Could one of you guys try official?

Tomorrow will likely be my last build of cm11. Hate to end it on a bad note but cm12 is developing quickly and I wanna check it out.
[Verizon Samsung Galaxy S III] Darryl Henley:
Tried clearing phone data before install. I think that made it worse. Phone got very hot before I could shut it down.

Thanks for you help.
[Verizon Samsung Galaxy S III] mastamoon:
Doh. Maybe wipe phone data, reboot, make sure phone data is rebuilt by loading phone, reboot to recovery, flash.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I wiped the Dialer, as hou said, and didn't wipe any caches, so far so good. Sorry to see you're moving on bc this was fun. Lol. I'm hoping the project to get the debloated stock rom for KK to load works out. I'm really a TW kinda guy. [emoji12] [emoji1]

Did you try clearing the dialers data and not wiping any caches? That worked for me so far. [emoji106] I'm using Nova also, btw.
[Verizon Samsung Galaxy S III] Casper34:
For what its worth, I'm all good. Text, mms, data, wifi, no fc.
[Verizon Samsung Galaxy S III] Darryl Henley:
That worked... Thanks.

I have always wiped the cache when installing, seemed kinda weird not to.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
My dawg [MENTION=4538493]prdog1[/MENTION] would have your head if you didn't wipe when I was on [MENTION=3074508]old&slow[/MENTION] 4.3 mostly stock rom. Pure blasphemy [emoji13] lol. Just glad we are all running well now. [emoji106]
[Verizon Samsung Galaxy S III] tylerch:
I'm having some trouble with sending MMS in hangouts on the 11/12 and 11/13 build. Upon further inspection of my system API settings everything seemed correct. But then I realized that the API settings in Hangouts are all incorrect (metropcs is the default APN, all the other APNs are for Sprint). I tried manually entering the Verizon APN, but when I saved the setting the APN disappeared.

Does anyone know how to fix this issue in Hangouts.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I think there is an ongoing issue for some with Hangouts and mms. I've personally never had an issue with it bc I use Handsent. Others with an issue tried Handsent and reported it worked then. Sorry I don't have any other insight.
[Verizon Samsung Galaxy S III] tylerch:
Ah yes, after doing some searching on the Hangouts support forum I found that this is an ongoing issue.

https://productforums.google.com/forum/m/#!topic/hangouts/5IH9ywBFjYw

Bummer... I love hangouts.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'm sure they'll figure it out soon. I use Hangouts the old way, not for texts & love my Handsent. Lol.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'm having issues again, outta the blue, Com.Android.Phone starts FCing again and this time it was really rapid. I was lucky to get into recovery.

What can I do to help this or you? Thanks
[Verizon Samsung Galaxy S III] mastamoon:
One of you folks is going to either try official or do a nandroid backup and install clean. If this was wide spread I think we would have heard more about it.. something in your setup must be conflicting...:confused:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Flashing Official will cause me to lose anything? I have a Nand but it's a few weeks old that's no problem though. I had reported before too that my phone turns off and reboots auto from time to time, seems to be when I'm typing something and then I get a noti. Any idea what that might be?
[Verizon Samsung Galaxy S III] mastamoon:
Flashing official wont cause you to loose anything. My builds are very close to official. I just want to make sure its not one of my ''''tweaks''' causing the problem. But if it were, i would think everybody would be suffering so Im thinking it something device specific.

I would still like for somebody to do a nandroid, wipe, install and see if it persists. If it does, its my rom, if it doesnt, its something out of my control.

Do you crashy guys use Xposed Framework or have any other sort of 'hacks' installed?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
No, no xposed or anything here. Just your Rom. I'll try Official now and see what's up. Ty

---------- Post added at 08:49 AM ---------- Previous post was at 08:42 AM ----------

@mastamoon either build 11/12 or 11/13 good? https://download.cyanogenmod.org/get/jenkins/90512/cm-11-20141113-NIGHTLY-d2lte.zip this one okay? Or? Thanks
[Verizon Samsung Galaxy S III] mastamoon:
12 would probably match closer to my build right now.. would reduce the risk of installing something that was fixed overnight between my build and nightly.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Got it, 11/12 it is. [emoji106]

---------- Post added at 08:58 AM ---------- Previous post was at 08:53 AM ----------

Spoke too soon, lol, only 11 13 14 nightly's. Only 12 was a Snapshot. Which way do I go now, kind sir? I'm on CM official download website, unless there is a official nightly 12 elsewhere, idk. Ty
[Verizon Samsung Galaxy S III] mastamoon:
Try 13 I suppose..
[Verizon Samsung Galaxy S III] Darryl Henley:
Thanks for all your help. I will stay with 11/10 until cm12.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Will do

---------- Post added at 09:37 AM ---------- Previous post was at 09:17 AM ----------

It loaded no problem, no FC, and it's fine right now. We'll see how the rest of the day goes, as you know, the FC did show up later too. Thanks again
[Verizon Samsung Galaxy S III] aromig:
Fwiw, I'm currently running PAC ROM and have been experiencing the exact same com.android.phone issue on all builds after 11/10. Clean install made no difference. On a dirty flash it would work for a while, but seemed to start up when shutting off wifi and trying to use data.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Okay, so I just reverted back to 11/10. Phone became unresponsive and kept going in and out of screen lock. Wallpaper kept changing too, if that means anything. Lol. There was no FC of Com.Android.Phone though this time but nonetheless, phone was not working.
[Verizon Samsung Galaxy S III] mastamoon:
:(

I cant suggest anything but a clean install at this point. Just back up your 11/10 build... Wipe and install fresh. If no fc's its something odd with your setup.. if it FC's its the build. Like I said, if this was a global issue, there would be a lot more talk about this here and in the official thread likely. Sorry man.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
No worries. I'll clean install. Hopefully that helps. Thanks again.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Okay, wiped all and clean installed 11/13 and still com.phone force closes. I use TWRP, could that be it? I have always used TWRP, as I prefer it to Philz, but maybe that is it? Very interesting issue here. We shall overcome though. LOL. :D Thanks for help.
[Verizon Samsung Galaxy S III] mastamoon:
Last test would be to install the latest nightly clean and see if it happens.

Unless you just started using TWRP, I dont think that should be an issue. I personally use Philz and like you know, dont have a problem. Something you can feel free to try if you like.

Unfortunately I just ran my last build and am uploading it now. If it happens on official you'll have to sit tight till they fix it up. If it doesn't happen on official then just keep running my last working build or move on to the official nightlies form here on out.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Okay, gotcha. Thanks again.:good:
[Verizon Samsung Galaxy S III] Perseus:
Sounds like Sluggish or Overloaded governor/Scheduler. Phone Running low on Ram perhaps ?

Here's what I'd do. Clean install from whatever Recovery. (Don't think the issue is Recovery). After flashing don't install anything else or restore anything. Just install Trickster Mod and change governor to OnDemand and ROW Scheduler. reboot.

Next, In BBS, check to see if there's a Alarm by com.internal.phone for DATA-STALL. If so, post the count of that alarm after 2 hours of sitting idle.
[Verizon Samsung Galaxy S III] Casper34:
[MENTION=2963287]mastamoon[/MENTION], looks like the issues are on PAC also.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I figured it had to do with official and not something I did since I really havent changed my build in weeks. Odd only some are getting hit though.
[Verizon Samsung Galaxy S III] Casper34:
For a change, I'm good! Although I have NOT updated the last 2 builds.
[Verizon Samsung Galaxy S III] ef-civic:
I'm ready to try CM12!
[Verizon Samsung Galaxy S III] SilentNN:
I just installed the official 10/19 build, coming from some old build from around January or so. MMS isn't working for me on the unified build, and I saw an old post saying that it still works on Masta's build, so I'm hopping on over here.

According to the first post, I should be on MF1 and NE1. According to my 'About Phone,' my baseband right now is ML1, and I'm not sure what modem I installed back then. My question is how I should proceed. I remember back then the new firmware would cause a permanently locked bootloader, so I'm going to be extra cautious.

Am I supposed to just download the firmware and modem linked in the first post, and flash them from recovery (I'm using TWRP, PhilZ gave me problems back then)?
[Verizon Samsung Galaxy S III] NoCrAppleHere:
You want to flash the NE1 modem. That doesn't do anything to the bootloader. They say NE1 only affected Canadian roaming but I see a difference locally from the ML1 modem. I usually wipe dalvik and cache. TWRP is what I use and never had an issue. I will say that I am on the 11/10 build still because me, and some others, had issues with the builds after 11/10. Didn't happen to all of us, so feel free to try the builds after 11/10. Lastly, Mastamoon has said he has stopped updating builds here and has moved to CM 12. GOOD LUCK [emoji106]
[Verizon Samsung Galaxy S III] mastamoon:
..... Im just gonna put this here... NO SUPPORT, NO BUGREPORTS, FLASH AT YOUR OWN RISK, etc.........

CM12 for D2VZW ... http://mastamoon.truelinux.net/ROMs/CM12.x/cm-12-20141124-UNOFFICIAL-d2vzw.zip

CM12 for D2VZW MD5: fd5f134c81b775676e31295ee0a96be7 (http://mastamoon.truelinux.net/ROMs/CM12.x/cm-12-20141124-UNOFFICIAL-d2vzw.zip.md5sum)

Unofficial GAPPS: http://mastamoon.truelinux.net/gapps/gapps-lp-20141107-signed.zip

Root: http://download.chainfire.eu/630/SuperSU/BETA-SuperSU-v2.27.zip

Full data/system wipe necessary.. Believe you have to install gapps with every reflash.

What works: almost everything

Whats derpy: Camera--- reportedly (https://play.google.com/store/apps/details?id=net.sourceforge.opencamera) works ok for pictures, video is still derped.

Enjoy. And remember... Use at your own risk, no support, etc....
[Verizon Samsung Galaxy S III] kidhudi:
Thanks so much masta
[Verizon Samsung Galaxy S III] Casper34:
Thanks for this, but........

Im gonna wait till I see some feedback, so please be sure to post some with screenshots! Thanks!

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] mastamoon:
Ive been using cm12 as a daily driver for almost 2 weeks. It really good.

Still a bunch of features missing and stuff, but its fast and stable. If you need a camera to survive, I wouldn't rely on it though.
[Verizon Samsung Galaxy S III] Casper34:
Well I don't rely on my camera but....

I don't want to miss pics like this.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] ef-civic:
Installed at 12 today. Everything seems good. Keyboard swiping doesnt work like before. All downloaded apps work like they should.

Thanks for posting this masta. Good work as always
[Verizon Samsung Galaxy S III] ugachris:
Does the camera work? I'm a little worried after Masta's comment. I'd love some Lollipop.
[Verizon Samsung Galaxy S III] ef-civic:
Seems to OK. I took a few pictures, no video though
[Verizon Samsung Galaxy S III] TokedUp:
Yes! THANK YOU MASTA!!!!!!!!!!!!!
[Verizon Samsung Galaxy S III] kidhudi:
edit.. i am impatient .. so far so good

PS...... even better than i expected

masta rules
[Verizon Samsung Galaxy S III] TokedUp:
Can't get root access. What do I have to do?
[Verizon Samsung Galaxy S III] Casper34:
I see a few people have jumped right in...... 2 simple questions....

1) is there a separate thread for CM12 yet for our phones?

2) can you switch back to CM11 with no issues?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] LLStarks:
Root is lost but can be reapplied. Mobile data does not work. Camera is crash prone.
[Verizon Samsung Galaxy S III] TokedUp:
Got root access! Mobile data works great for me, make sure to switch it from Global to LTE. Everything works so far, this ROM is absolutely amazing! Haven't had an issue yet. Gonna test Camera tomorrow.
[Verizon Samsung Galaxy S III] mastamoon:
For root, flash http://download.chainfire.eu/630/SuperSU/BETA-SuperSU-v2.27.zip
[Verizon Samsung Galaxy S III] jehelmer:
Same here... I can't believe how well it is running!
[Verizon Samsung Galaxy S III] TokedUp:
[MENTION=2963287]mastamoon[/MENTION] cannot thank you enough! Im gonna donate to you on Friday when I get paid. If this is an early/alpha/whatever u wanna call it build then CM12 official is gonna be the best Rom ive ever ran on my S3. Im so excited about this new unofficial version I couldnt sleep last night, kept waking up to turn my screen on to see the new lock screen. It so smooth already, I cant wait for the Official version.

Here is what I found so far. These are not bug reports or complaints just letting the guys on the fence know whats up:

Battery saver option doesn't turn on (who cares). Battery seems the same as any other Rom I have run. Had great stand by time last night. 8 hours of sleep only lost 4%.

Can't attach photo from inside Google Messenger app for MMS, have to attach from Gallery itself then it works fine. MMS does WORK.

Location icon is always showing in my status bar. Dont know if thats the way it is in 5.0 or maybe its always searching. I dunno.

Camera is borked. Google Camera from Play Store won't even open. Tried the OPO camera just in case, no go. So like Masta said, if u need Camera dont flash this yet. Im sure we can find a work around for this eventually. Im gonna see what can find today.

Happy flashing everyone and happy holidays to [MENTION=2963287]mastamoon[/MENTION] and everyone else. XMAS came early for me!

---------- Post added at 10:32 AM ---------- Previous post was at 10:13 AM ----------

Already found a work around for the Camera!!!!!!!!!!!!!!!!!!!!! download Open Camera from Play Store! Camera works 100%, free, no ads. Video doesnt work.

YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!
[Verizon Samsung Galaxy S III] defTwitch:
so when you switch'n for real Masta

Masta... gonna make the official CM12 switch in time and start adding a little flavor...

or you still think'n you're moving on from the S3 and not worth the effort?