yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SotYPL:
I finally switched from SlimKat 7.0 to cm12.1 nightly. It's my first LP rom for S3 ever. Couple ot things after 2 days of using:

1. bluetooth is not working correctly for first call after phone reboot. It connects to my car just fine but when I try to make outgoing call it just tries and drop after couple of seconds. Same thing with first incoming call. Phone is ringing but it does not pass the call to bluetooth. After first failed try any other calls are working fine, both incoming and outgoing. ALso I don't longer need to use SoundAbout because ringer is ringing using phone speaker when connected to the car and on SlimKat 7.0 it went to bluetooth audio device not phone device so when my car's radio was not switched to bluetooth as input auiod I could not hear ringer at all. SoundAbout was able to fix that.

2. battery statistics are not working correctly. Right now after around 18 hours on battery it shows that K9 Mail used 19% of battery and 1h 10min of screen on time used only 3% and that is obviously not true.

3. Cerberus app reboots the phone when trying to take picture using front camera. Taking one with rear camera works fine. I found that this was and issue with CM10 and was fixed in CM11. It seems that is back with CM12.

4. This is probably feature not bug but it makes no sense for me. When using secure lock screen (pattern) you can pull down notification drawer and use toggle switches. So you can turn off wifi or bluetooth with screen locked.

5. I hate that now you have to first swipe up to show pattern for unlocking phone.

6. new LP notifications on lock screen are big step back. I can't use dashclock anymore and it worked a way lot better.

7. problems with call voulme. Sometimes when I answer or make a call call volume is set for highest level even that level indicator shows it at the lowest or almost the lowest. I have to press volume up and down couple of times to get it set correctly. But that I think was always a problem with any CM based roms even back in my Samsung Fascinate era.

edit:

8. I just got complete lost of signal on my way home. It showed no carrier and incoming calls could not get trough but I could make outgoind call just fine. Data was also not available. I had to reboot and it found network just fine.
[Verizon Samsung Galaxy S III] :
A logcat would be most appreciated.
[Verizon Samsung Galaxy S III] DubleJayJ:
Battery life has been absolutely abysmal for me for the past few months, looking to fork out the $140 for early termination soon and buy an iPhone 6 Plus*ducks in cover*. But on a serious note, I hope the official CM12.1 nightlies will change my mind
[Verizon Samsung Galaxy S III] yorkwar:
Hi guys, official 5/3 nightly is out. Gonna to have a try.

I'm on official 4/30 nightly now. Is it a good idea to utilize the built-in CM updater?

OK. Got it. It's just a downloader. You still need recovery program to flash the ROM. So ..., a desktop downloader may be a better choice.
[Verizon Samsung Galaxy S III] KaffeDisco:
How did 5/3 work for you? Things were working *okay* on 4-30, but once I flashed 5/3, I couldn't turn on Bluetooth anymore and I seemed to lose MMS (even after flashing Mastamoon's stock VZW APN). I went back to my 4/30 backup and Bluetooth/MMS are working fine - I'll stick to that for a couple more nightlies, probably, unless somebody has an idea what I screwed up if anything :)
[Verizon Samsung Galaxy S III] Master Cylinder:
Some earlier builds by users in this thread have been nearly flawless. Rave results. You could try this one from 4/19 from [MENTION=3124924]timedroid[/MENTION], which I'm using: https://mega.co.nz/#!UddTEITI!nfe5E9ZhtRS_cmyga8EESl-Ab23GmZPAE9Z_iZfwqwA

Or this one by the OP of this thread, who uses ATT and can't test, so I don't know what the results have been - you would have to look through the thread to see. https://androidfilehost.com/?fid=23991606952593950

There might be a couple of others. You can see what the results of the cm nightlies have been here as well since they only started on 4/30.

I have had the best battery results ever on LP after the builds settled out, but I use Greenify. Maybe a new battery would be cheaper?
[Verizon Samsung Galaxy S III] DubleJayJ:
About 5-6 months ago I switched out my battery with my brothers(who also has an S3 but is back on stock VZW 4.2 I think) and he gets really nice battery and after I changed batteries I still had terrible battery and he continued to get good battery life.
[Verizon Samsung Galaxy S III] yorkwar:
I'm not on Verizon Carrier and not using these features. Sorry.

BTW: 5/4 is out. Maybe, try that.
[Verizon Samsung Galaxy S III] Master Cylinder:
Time to call an Exorcist! :p
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 05/04

GApp: PA-Micro

Just installed this nightly build. Working: wifi, bluetooth, MMS, built-in camera. No bootup issue. Going to let it run its course for the week.
[Verizon Samsung Galaxy S III] jbleach:
I installed TWRP and gave the latest nightly 5/4 a try but got the same results. I'm going to look into doing a full wipe of the SD cards and see how that goes.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I've never had to do a full wipe of my externalSD card. I have, however, done an Advance Wipe and also wiped the Internal Storage.
[Verizon Samsung Galaxy S III] jbleach:
yep I tried wiping the Internal Storage but it didn't change anything. I'm at a loss - not really sure what else to try.
[Verizon Samsung Galaxy S III] slick_shoes:
running the latest nightly 5/4 with 0 issues, then again never really had many issues to begin with
[Verizon Samsung Galaxy S III] Master Cylinder:
Hmmm.... It's a conundrum for sure. I was thinking about doing the same thing, playing around with doing an rsync (YES! if you adb root while it's booted it's there and seems to work! Won't work when not booted, at least there's an error.) with adb ppp over usb (give it a try) to see how I can preserve everything (with extended attributes) I did an adb pull on /sdcard/Android and it cut out 1/6 of the way through, and ownership was all off (not hard to fix.)

However, I've been able to fresh install Alliance ROM, masta's 3/19, timedroid's 4/19 and Invisiblek's 4/21 and boot in the last couple of days, but not these others. Sumpin's off somewharz.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Anyone trying 5/5 yet? I got no rotate at all no matter what I do. I rebooted, I adjusted the settings and still no rotate. Also, I noticed in the rotation settings one option is missing, idr what it was before though. Lol.

Anyway, anyone have the same issue? Thanks.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Yes...no auto rotate here either.
[Verizon Samsung Galaxy S III] jonny30bass:
Where is the link for the latest nightly? The link in the op says "empty".
[Verizon Samsung Galaxy S III] NoCrAppleHere:
http://www.cmxlog.com/12.1/d2vzw/ These are the downloads and below are the changelogs.

It's empty bc those links weren't for nighties, they were for InvisibleK's builds. Enjoy. ?

---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------

How do we tell whomever is doing the nightlies at CM or we just wait? Never did that before, just messed in Xda forever. Lol.
[Verizon Samsung Galaxy S III] ffeingol:
I'd think the Cyanogenmod forums wold be a good start: http://forum.cyanogenmod.org/forum/863-samsung-galaxy-s-iii-cdma-d2cri-d2mtr-d2spr-d2usc-d2vzw/
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Saw that yesterday but wasn't sure if I could post right away or if anyone could join. Didn't look further than my nose, very lazy these days. Lol. ?

---------- Post added at 08:41 AM ---------- Previous post was at 08:05 AM ----------

New (at least to me) silent mode W/ ALARM, I'm loving and never before did the CM Updater ever work for me, does now, but that's bc InvisibleK's builds weren't nightlies by CM nor did he have the update tool like Mastamoon did.

This is so badass, how many times can the GS3 reinvent itself? Idk but never count it as DEAD, that's for sure. ????
[Verizon Samsung Galaxy S III] JumperPunk:
Auto rotate is working fine for me on 05/05 official nightly. I still have all 4 options for rotation (0, 90, 180, and 270), although I didn't actually try them.

EDIT:

Also, the (stock, built in) camera works out of the box for the first time in a while for me.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Did you dirty flash? I realize what is missing, the option to rotate or not rotate the lockscreen. I'm gonna flash it again, see what happens.

Ok, 5/5 and 5/4 no autorotate at all. [MENTION=4085339]JumperPunk[/MENTION] are you using Nova Prime by any chance?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 05/04

Settings/Display & Lights/Rotation -- make sure you toggle the switch to ON (if you want it). After that, the check-boxes will become available.
[Verizon Samsung Galaxy S III] JumperPunk:
Clean flash. If by 'Nova Prime' you mean the launcher, no. I am using Apex (the free version). That shouldn't change what you see in the settings, though. I don't see an option to toggle lockscreen rotation. It is just disabled.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I've gone back to 5/4 & 4/30, no rotate at all. It won't come back. Smh.
[Verizon Samsung Galaxy S III] SotYPL:
5/4 nightly and another issue with bluetooth. When I end the call by pressing end call button on steering wheel car display shows that call was ended but actual call is still active and I can still hear sound trough car's speakers. I have to end call from phone display.

---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------

How do I take logcat after reboot? There is nothing in the log from before boot.
[Verizon Samsung Galaxy S III] jbleach:
One difference I've noticed between the ROMs I can flash (timedroid 4/19 & Invisiblek 4/21) and the ones that bootloop (new nightlies, etc) is that the successful flashes don't display the white "updating apps" box. They just display the blue cyanogen guy for a while and then go straight into the CM setup screens. Not sure why the difference.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Hmm... I'm pretty sure that box came up for me, but it flashed fine. But I cleared cache and such after the initial flash and GAPPs flash, I read somewhere to do that. Maybe the install scripts of the successful flashes clears it automatically after the initial flash?

Just a thought, no evidence to back it up :D
[Verizon Samsung Galaxy S III] Master Cylinder:
I always get the "updating apps" box when flashing dirty or clean, LP or KK or TW. The ROM has to optimize the apps for the runtime, whatever it is, is my own uneducated understanding. However, the number of apps displayed is usually off if it ain't gonna boot all of the way.

I've had a couple of the recent cm nightlies boot all the way through with the correct number of apps "optimized" and display that it's finishing boot and maybe "starting android" or something, then it's rebooting again. I'll pull a log on the next one but it seems like a problem that only a couple are having, though I haven't looked over on the cm forum yet, or the other cm threads. (Which could tell us a lot!)

I am having a different problem (?) with my recovery - I did a backup this morning and it was dated 1969-12-31 and so were many of the folders it restored. :mad:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Going all the way back to 4/30 brought back autorotate. It's weird though bc it didn't come back asap, it was awhile after the phone booted up after flashing back to 4/30. I'm gonna clean flash 5/5 later, see if that makes a diff.
[Verizon Samsung Galaxy S III] KaffeDisco:
I'm on 5/4 and it's better than the 5/3 that I was using before - Bluetooth works and connects. I've found that my Pebble eventually disconnects for some reason though, so I have to reconnect it every so often if I notice I'm not getting a text message on it - maybe every couple of hours or so? Sometimes it asks for a brand new pairing code, too. I did get the thing this afternoon where Bluetooth turned off and wouldn't turn on again, but it was just that one time and I couldn't duplicate it.

Autorotate on 5/4 seems to be working fine for me.
[Verizon Samsung Galaxy S III] brandonb0013:
bootloop after "android is starting"

i did a clean wipe, and installed cm 12.1 and lp gapps, everything went well until it went through the "optimizing apps" screen, then it says "finishing boot" and the screen will get janky, then it reboots and does it again. it doesnt always have to optimize the apps though. it seems odd. i cant get into recovery, but can get to download mode. i flashed a twrp 2.7.0.0.tar file (the one i have used a while) but still cant get to recovery. any suggestions? thanks guys

edit: tried flashing twrp 2.8.6.0 (latest, also the one i installed prior to flashing cm 12.1). before i flashed it, it had 106 apps to optimize. after i flashed (to 2.8.6.0) it only has 93 to optimize now
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Ok, could be a bad rom dl or gapps dl. Use the gapps in the op. Nightlies are up now at the Cm website, new one for 5/7 is up. I'd re-download both, get to twrp, wipe everything and try a fresh install again. Unless you wiped everything in cache and Dalvik, the optimized app count may not be exactly the same. Good luck
[Verizon Samsung Galaxy S III] brandonb0013:
thanks, i managed to get into recovery after trying a few more times, restored a nandroid. gonna download the newest cm12.1. ( i was tryign 5/4 cuz i heard good things about that one) and i found a different gapps to try
[Verizon Samsung Galaxy S III] NoCrAppleHere:
http://www.cmxlog.com/12.1/d2vzw/ is a link to the change logs for all the nightlies. I had lost autorotate I think with 5/4 but after a clean install, I was good. I haven't had any issues with any nigtlies themselves yet, as the autorotate was my bad due to a dirty flash or some gremlins. Glad it's working now. Have fun!!!
[Verizon Samsung Galaxy S III] brandonb0013:
thank you a lot for the quick reply. i didnt think i would get one at this time of night
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'm nocturnal, lucky for u ???
[Verizon Samsung Galaxy S III] brandonb0013:
well i tried 5/7 and the g-apps-L-4-21-15 and same exact issue. im restoring my nandroid. gonna call it a night. maybe i need to format my sd card? but idk why that would be because i have my files on the internal storage. i guess if anyone has a clue, thatd be great. thanks again.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Yeah, idk, one of the fine more qualified dudes will take a look and call you in the morning. Sorry I couldn't be more help.
[Verizon Samsung Galaxy S III] Master Cylinder:
Unfortunately, this is the same problem a few of us have been having and the solution hasn't been found yet (though I'm still working on it when I have time.) If this is your first LP then there is one that will probably boot, and it's the one I'm still using until I get this figured out, and frankly is pretty flawless. It's from one of the user's around here [MENTION=3124924]timedroid[/MENTION] who built his own, from 4/19. See if this works, with whatever gapps you want.: https://mega.co.nz/#!UddTEITI!nfe5E9ZhtRS_cmyga8EESl-Ab23GmZPAE9Z_iZfwqwA

I used these gapps from [MENTION=4112553]dhacker29[/MENTION] : http://fs1.d-h.st/download/00171/BX7Q/gapps-lpmr1-20150503-signed.zip

Choose the second link to avoid some Dev-Host nonsense. Or, download from my dropbox here: https://www.dropbox.com/s/czmvet9acncp0aa/gapps-lpmr1-20150503-signed.zip?dl=0

EDIT: When I say I'm still working on it, I ain't no dev, I just have some hunches and I ain't givin' up, dang it!:cowboy:
[Verizon Samsung Galaxy S III] :
I'll create you a special eng build (with adb automatically enabled) so you can pull some logs for me. I'll do that when I get home tonight.
[Verizon Samsung Galaxy S III] brandonb0013:
Ok. I just downloaded the one you gave in the previous post before you posted this lol. But I'll wait for your special build since I won't be doing it until tonight. Idk much about how to go about getting your logs and sending them, so you'll want to explain that part in relative detail. :) thanks.
[Verizon Samsung Galaxy S III] Master Cylinder:
Here is a logcat from a dirty install of 5/7 over [MENTION=3124924]timedroid[/MENTION]'s 4/19 build that won't boot (the 4/19 build boots, but not the dirty flash, like all of the others,) since a clean install won't produce a logcat at this time... or boot for some of us. [MENTION=3124924]timedroid[/MENTION] saves the day again!):good:

https://www.dropbox.com/s/61bxeezy2p6d0pg/logcat-cm121_5-07-15dirty.zip?dl=0

Thanks for doing this!!!:highfive:

---------- Post added at 01:39 PM ---------- Previous post was at 01:07 PM ----------

I'd be happy to run the logcat on the build you put out ... a fresh install.

---------- Post added at 01:45 PM ---------- Previous post was at 01:39 PM ----------

Not sure who you were referring to but I put a link to a good working LP build. [MENTION=2044079]Nardholio[/MENTION] is talking about a build to get a logcat from, one that most likely won't boot all the way since that's the issue, but you can get a log out of it if you install Android SDK and use adb logcat > filename.txt in that directory (after starting the daemon by typing adb devices in that directory - make sure your device ID is listed) OR maybe his will log the boot automatically?
[Verizon Samsung Galaxy S III] brandonb0013:
So I'll try flashing the latest cm 12.1 and use him special build and hopefully it'll log everything automatically because Idk how to use adb. Sorry I'm a noob when it comes to anything but the simple flashing a ROM.
[Verizon Samsung Galaxy S III] Master Cylinder:
Just to be clear: if none of that works (I'll bet $1,000 it won't) then use this one https://mega.co.nz/#!UddTEITI!nfe5E9...ZPAE9Z_iZfwqwA IT WILL WORK!! :)
[Verizon Samsung Galaxy S III] brandonb0013:
Coool. Lol. That's a gapps?
[Verizon Samsung Galaxy S III] Master Cylinder:
somehow repeated, and deleted.
[Verizon Samsung Galaxy S III] brandonb0013:
okay, idk if im confident in trying the one with the logging enabled unless it does it on its own and is simple to send. otherwise i will probably skip that. id love to help, but i cant risk bricking this phone is all.
[Verizon Samsung Galaxy S III] Master Cylinder:
No. That's a 4/19 LP 5.1 build. Here's some gapps: https://www.dropbox.com/s/czmvet9acn...igned.zip?dl=0

EDIT: By the way, if I'm wrong and you can boot a recent cm nightly, then I can only pay you in Quatloos.
[Verizon Samsung Galaxy S III] brandonb0013:
ive heard Quatloos are gaining some worth now days. i hope you're wrong! i will attempt these roms and what not after i study for my math exam for the next 4 hours. hopefully everything will work perfectly! but ...ya know. this is real life
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh::laugh:

Install 4/19 = Live Long and Prosper!

(At least until we can get this other little problem solved...)
[Verizon Samsung Galaxy S III] :
Can you send me a "cat /proc/kmsg" log too?
[Verizon Samsung Galaxy S III] brandonb0013:
when i go to the site, it says i need a decryption key?
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah, give me a few...

Well dang! That link was good this morning, and for the last couple of weeks. I have it and just uploaded it to my dbox: https://www.dropbox.com/s/qao0qnr84cjlsq4/cm-12.1-20150419-UNOFFICIAL-d2vzw.zip?dl=0
[Verizon Samsung Galaxy S III] Master Cylinder:
Here is it, such as it is. I ran it while it was booting, and it optimized about 30% more apps than I have!?

https://www.dropbox.com/s/ps5u73kc0kwb846/proc-kmsg.txt.zip?dl=0

That's from dirty flashing 5/7 over 4/19.
[Verizon Samsung Galaxy S III] :
There's not much to go on in these logs :/ Are you running the latest firmware for your phone?
[Verizon Samsung Galaxy S III] Master Cylinder:
TWRP 2.8.4.0. I could upgrade it to 2.8.6.0 - it works, just was a little flaky - had trouble unlocking the screen. How do you want me to get that /proc/kmsg data? I just did a cat /proc/kmsg >> file.txt from a shell when it started booting. There seems to be times when I got kicked out and/or the /proc/kmsg data was purged and started over again, though I might not know what I'm talking about.

If there's another way you want me to do it let me know.
[Verizon Samsung Galaxy S III] :
I meant in terms of bootloader chain/modem. The way you pulled the logs was fine.
[Verizon Samsung Galaxy S III] Master Cylinder:
I did flash Philz TWRP Multiboot, which is based on 2.8.3.0 but it shut down the phone whilst doing a backup, so I put on 2.8.6.0 which was a mistake because it requires updating from 2.8.4.0. It was after all of this that I started having this problem, though it is probably just coincidental - I ain't smart enough to know.

---------- Post added at 09:00 PM ---------- Previous post was at 08:55 PM ----------

I'm on the VRBMF1 bootloader (I think, I'm restoring now. Maybe it's MB1?) and the NE1 modem. My bootchain is the one I used to unlock the phone: VRALEC I may have my terms mixed up. When I get it booted I'll tell more.
[Verizon Samsung Galaxy S III] :
TWRP has a file manager, right? Can you do one more experiment for me? Copy the /system/cameradata folder from a build that works, and put it on your sdcard. Flash a build that doesn't work, and then delete the same folder from /system and then copy the folder back. You may have to go into the mount options and ask it to mount system before the file manager will see it.
[Verizon Samsung Galaxy S III] Master Cylinder:
Will do.

---------- Post added at 09:20 PM ---------- Previous post was at 09:03 PM ----------

I replaced /system/cameradata but it didn't boot. I knew it was trouble when it reported "Optimizing xx of 94 apps" when there should be like 144.

I looked into a recent nandroid log and found these 2 things. Maybe I need to flash the bootloader? That's one thing I haven't tried...

ro.bootloader=I535VRALE6

...

ro.build.description=d2vzw-user 4.1.2 JZO54K I535VRBMF1 release-keys
[Verizon Samsung Galaxy S III] :
You could try. You should be on MF1 firmware, NE1 modem http://www.invisiblek.org/firmware/d2/
[Verizon Samsung Galaxy S III] Master Cylinder:
As far as I know that's what I'm on, but I'll have a looksee after it get's booted and then go ahead and reflash it anyway. It's gotta be something like that since it's only a few people who are having this problem. Most seem to boot nightlies fine.

---------- Post added at 10:28 PM ---------- Previous post was at 09:30 PM ----------

I don't know. It is looking like I'm on VRALE6, which would be a real kick in the head... Nothin' ever came up till a certain point in the ROMs development. Am flashing bootloader and modem (again on the modem) now (after all of my self-righteous lectures to others to be on the right bootloader!) and then I'll fresh install latest nightly and we'll see.

EDIT: Well, I've been under a Jedi Mind Control!

Flashing the MF1 firmware and the NE1 modem, (need to reboot to see partitions again. With TWRP, it says phone is now no longer rooted and would I like to install SuperSU - I did. Maybe I didn't need to if I was going to install a pre-rooted ROM?) then clean flashing 5/8 with the 5/3 wiki.cyanogenmod.org gapps and ... @*%$#! ... it works. (Insert non-existent "Doh!" emoji here.)

I'm glad I'm not limber enough for my foot to reach my head ... I am gonna work on it, though. :eek::cyclops:

Looks like people having this kind of trouble need to flash those even if they think they already have.
[Verizon Samsung Galaxy S III] brandonb0013:
So I flashed this and gapps and now have LP! Thanks a ton! But as of now,I don't have root? Is there a setting like I think my C-Rom 6.3 I had to allow root access to apps.

Edit: forgot about the developer secret menu thing. found the root access
[Verizon Samsung Galaxy S III] jbleach:
<facepalm> wow. </facepalm> I too thought I already had the MF1 firmware but apparently I did not. Flashed MF1 and then reflashed NE1 modem. Then flashed the 05/08 Nightly and it installed/booted flawlessly.

Major thank yous to everyone who pitched in with advice and help for us stragglers. :eek: